When I run Two *.VI in Labview I can connect to Labjack from these two, but when I build these to *.exe files I cant connect from both. I can connect from one but even if I stop this .exe file, I cant connect to the other one? Can it depend on the DLL? How can I solve this problem? Is there a way to close the connection?
.png%3Fitok=PHGBxf6M "EEV Blog Reviews LabJack T7-Pro & Software Tools")
.jpg%3Fitok=B1YcuDFK)
.png%3Fitok=Ybt-OlgU "LabJack + JEDI One Can Create a Powerful Distributed DAQ Ecosystem")
When you are running .vi files in LabVIEW there is one instance of the UD library running and you are able to do some pretty funky device sharing things between *.vis. When you build each of your vis as *.exes and run them that way, each *.exe has its own instance of the UD library running and you need to pay attention to how many connections you have to a LabJack device.
Assuming you are using a U3, you can only have one application using the device at a time. Our T-Series devices offer more connectivity options (primarily Ethernet), which will allow you to have additional programs running and communicating with the device.
Your application can close device connections by calling the UD library's "Close" function or use the "LJUD_Close.vi".