Installation of LaBunaPera

  1. If you are not affiliated with WIS, go away and return only after you have discussed your rights to use LaBunaPera at all. Most links on this page work only inside the Institute, anyway.
  2. Get and install LabVIEW (LV). The current version of LaBunaPera is saved for LV 2014, but former versions have been ported back even to LV 8.0, and are archived and available on demand. The base installation package including NI device drivers should be sufficient, unless special features are needed for some specific (OhPera) instrument driver. As known, users within the Faculty of Physics and the Faculty of Chemistry of WIS can have Labview installed free of charge, since the Faculty is paying for the campus license.
    It is possible, but hasn't been tested so far, that LaBunaPera would run just on the free LV runtime engine, which can be downloaded from NI.
  3. Get the latest version of LaBunaPera and of the OhPera instrument drivers from the respective git repositories.
    If you are familiar with git, you can clone the first in the path of your choice, and the second within the LaBunaPera directory.
    If you are not, or if you're not interested in the mutation history (bet you aren't) just get the zipped packages. Uncompress them in a disk location of your choice. The second package should unpack as a subdirectory OhPeraDrivers/ (not OhPeraDrivers.git/; rename it) which sits at the same level of the file
  4. (optional, but why shouldn't you): Get and install LuaVIEW. The latest LaBunaPera can run without it, but of course you lose the nice scripting feature.
    As for which version of LuaVIEW: so far LaBunaPera has been tested only with older versions of LuaVIEW, up to 1.2.2. A link to an archived version of it is reported in the
    LaBunaPera repository site. Version 1.2.2 runs on windows, Linux and Mac, but only on 32bit LabVIEW. (A version 1.2.2 for LV prior to 8.5 is even archived).
    As of January 2016, a new version 2.0 is available, which supports only windows 32 and 64bit, and has a tighter license enforcement. The preferred way to get this one, is via the VI Package Manager, which is actually bundled in the installation of recent LabVIEW versions.
    Otherwise, the home site of LuaVIEW is Installation instructions, as well as a lot of excellent documentation about LuaVIEW are on the same site.
    A system-wide installation of LuaVIEW (perhaps in <user.lib> in the LabVIEW installation directory) is preferrable, but another convenient place where to install the LuaVIEW package is just inside the LaBunaPera directory; thus LaBunaPera will find all the necessary LuaVIEW subVIs at once.
  5. LuaVIEW 1.2.2 and earlier requires an additional installation step: the VI <LuaVIEW>/Install must be run once, choosing the operating system used. Failing to do so, LaBunaPera won't run because of missing VIs. Here <LuaVIEW> denotes the installation directory chosen.
  6. LaBunaPera is run from the entry VI, from within the project LaBunaPera.lvproj, to be opened first (this might slightly change in future: a built application might be provided; launching from outside the project will default to lua disabled).
    The first time it is launched, LabView will probably perform a long search and eventually ask for the location of some luaview VIs. To avoid that this happens at every opening, save all files when exiting LabView. A mass compile (from the LabView menu Tools/Advanced) of the <LuaVIEW> directory and of the installation directory can help.


Old LaBunaPera versions, and use with old LV:

Page last modified on