The LabVIEW bindings allow you to control Bricks and Bricklets from your LabVIEW programs. The ZIP file for the bindings contains:
The LabVIEW bindings are based on the C# bindings. Since version 2.0.0 the C# bindings are CLS compliant. This allows to use them with all .NET compatible languages, such as LabVIEW's .NET support.
To make the bindings work LabVIEW has to be able to find the Tinkerforge.dll. Depending on your LabVIEW and Windows version you either need to use the Tinkerforge.dll from the net20 or the net40 folder. Try the NET 2.0 version first. If LabVIEW reports error code 1386 "The specified .NET class is not available in LabVIEW." then you need to use the NET 4.0 version instead.
If you open an example then LabVIEW will search for the Tinkerforge.dll and ask you if it could not find it. You can avoid this search and ask procedure by putting the Tinkerforge.dll in a folder known to LabVIEW. The easiest option is the vi.lib folder of your LabVIEW installation:
C:\Program Files\National Instruments\LabVIEW 2013\vi.lib\
Then LabVIEW will find the Tinkerforge.dll automatically and does not ask for your support. But LabVIEW might warn that Tinkerforge.dll was loaded from a different folder. This warning can be ignored.
To test a LabVIEW example Brick Daemon and Brick Viewer have to be installed first. Brick Daemon acts as a proxy between the USB interface of the Bricks and the API bindings. Brick Viewer connects to Brick Daemon and helps to figure out basic information about the connected Bricks and Bricklets.
As an example let's run the configuration example for the Stepper Brick. For this we copy the Example Configuration.vi file from the examples/Brick/Stepper/ folder into a new folder:
example_project/
-> Example Configuration.vi
If you did not copy the bindings to the vi.lib folder of your LabVIEW installation then the Tinkerforge.dll file has to be copied to the example_project/ folder as well before the example can be opened in LabVIEW:
example_project/
-> Tinkerforge.dll
-> Example Configuration.vi
In the example host and port specify at which network address the Stepper Brick can be found. If it is connected locally to USB then localhost and 4223 is correct. The uid value has to be changed to the UID of the connected Stepper Brick, which you can figure out using Brick Viewer.
Now you're ready to test this example.
Links to the API reference for the IP Connection, Bricks and Bricklets as well as the examples from the ZIP file of the bindings are listed in the following table. Further project descriptions can be found in the Starter Kits section.