2.1. Installation - Microsoft Windows¶
The setup file will install Labber to the default Microsoft Windows installation directory, as well as create folders for storing data and local driver files in the user’s home directory. The default directories for local files can be set in the Preferences window, see Section PrefsFolder).
After installation, the Instrument Server, Log Browser and Measurement programs can be started by clicking the corresponding file from the Windows start menu. Note that the Log Browser and Measurement programs can be opened from within the Instrument Server, so it is usually sufficient to start just the server program.
2.1.1. Microsoft Windows - Troubleshooting¶
Depending on security settings, some virus scanners may prohibit Labber from being installed or run on you computer. If you’re experiencing difficulties installing or running the program, try to temporarily disable the virus scanner.
Some Microsoft Windows distributions lack a few support files needed by
the program to run correctly. If the program won’t start, download and
install the redistributable support files for Microsoft Visual C++ from
on “Download” and select the file
2.1.2. Microsoft Windows - Defender SmartScreen warnings¶
On certain Windows distributions, a dialog may pop up when installing Labber stating that the applications is unrecognized and hasn’t been screened by Microsoft. To install Labber, you need to override the dialog by clicking on “More info”, and then click on the “Run anyway”-button.
2.2. Installation - Mac OS X¶
On Macintosh OS X, open up the installer disk image (.dmg-file) and drag the Labber folder to the Applications folder. The Labber folder contains the Instrument Server, Log Browser and Measurement applications, as well as driver files and a few example scripts. To start one of the programs, double-click the corresponding app file.
If the program fail to open due to OS X’s restrictions to only allow apps from the Apple App store, open the Mac’s System Preferences window, select Security & Privacy, go to the “General” pane and set “Allow apps downloaded from” to “Anywhere”. If you don’t want to lift the restrictions completely, the settings in Security & Privacy can be set to “Mac App Store and identified developers”. In this case, the user needs to open each of the Labber apps once by right-clicking the app icon, holding down the alt/option or the control key on the keyboard, then clicking open. This will instruct OS X that these apps are allowed to run. The operation needs to be performed once for all three apps, to make sure that the apps will be able to call each other.
2.2.1. MacOS 10.15 Catalina and newer¶
Starting with MacOS 10.15 Catalina, Apple removed the option to allow installation of apps from unregistered software developers. We are currently in the process of getting approval from Apple for Labber, but in the meantime, it is still possible to run Labber by overriding the settings for each of the subcomponents used by the software. When opening the Instrument server the first time, MacOS will show a dialog informing that the app “cannot be opened because the developer cannot be verified”. When the dialog shows up, leave it open and launch the MacOS System Preferences window, select Security & Privacy, and go to the “General” pane. Next, click “Cancel” in the warning dialog. At this point, a text message and a “Open Anyway” button will pop up in the Security & Privacy window, which can be used to override the warning.
Next, there will be a similar warning for opening Python, and a similar technique (click “Cancel”, then click “Open Anyway” in the Preferences window) can be used to override the warning. Unfortunately, the procedure needs to be repeated for each of the Python packages used by Labber (approximately 10-15 in total), and you may need to quit and restart the Instrument server a few times to make sure all packages are accepted. Once all packages have been accepted, Labber will start as usual when launching the application subsequently.
2.3. Installation - Linux¶
On Linux, open up the debian package file (.deb-file) to install Labber. This will install Labber to the folder /usr/share/Labber, as well as create folders for storing data and local driver files in the user’s home directory. The default directories for local files can be set in the Preferences window, see Section PrefsFolder).
After installation, the Instrument Server, Log Browser and
Measurement programs can be started by opening a terminal and typing
labber-measurement at the prompt. If you are running a desktop
manager, there will also be launcher icon available for the three
programs. Note that the Log Browser and Measurement programs can be
opened from within the Instrument Server, so it is usually sufficient
to start just the server program.
2.4. VISA distribution¶
To communicate with instruments over the VISA protocol, a VISA
distribution needs to be installed on the computer. A VISA distribution
can be downloaded from National Instruments, see
2.5. Network and firewall settings¶
The Instrument Server, Log Browser and Measurement programs communicate using TCP/IP, which makes it possible to perform measurements involving instruments connected to different computers, even on different networks. The default settings assign TCP port 9406 for server/client communication and TCP port 9407 for sending internal notifications between the program parts. If you want to perform measurements in a multi-computer network and firewall is enabled on your system, the firewall must be configured to allow traffic on these ports. The port numbers can be changed in case they are occupied on your system (see Chapter Prefs).
2.6. Program folders¶
In addition to the folders with executables the program uses a few extra folder locations, as listed below.
2.6.1. Data folder¶
The program needs a folder for saving the measured data. By default, this folder is set to “<User home directory>/Labber/Data”, but it can be changed at any time from the Preferences window (see Section PrefsFolder).
2.6.2. Instrument drivers¶
The program has two separate folders for storing instrument drivers, one main folder (called “Instrument drivers” in the Preferences window) and one local folder (called “Local drivers” in the Preferences). The main driver folder resides in the same folder location as the executables, and should not be altered in a typical setup. The local driver folder is set to “<User home directory>/Labber/Drivers”, but its location can be changed in the Preferences.
When creating a new instrument driver, the driver definition file should always be placed in the “Local drivers” folder. This allows the user’s own drivers to be kept separately from the drivers provided with Labber, and it also prevents drivers written by users from being deleted when updating the Labber program to a newer version. See Section Drivers for more information on creating instrument drivers.