NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

VI works in LV, but not in TS

Solved!
Go to solution

Oli_Wachno_0-1710228332294.png

 

0 Kudos
Message 11 of 15
(273 Views)

@Scott_Richardson wrote:

Do you know how the VI talks to the hardware, i.e. is there a DLL it calls,


My VI uses several sub-VIs provided by Picotech.
Both LV DLLs and Picotech DLLs are used in these sub-VIs.

I have downloaded the LV files here:
https://github.com/picotech/picosdk-ni-labview-examples/tree/master/ps2000
https://github.com/picotech/picosdk-ni-labview-shared

The DLLs are provided by Pico directly as an SDK.
I have installed the current 32bit SDK 10.7.26

 

regards

0 Kudos
Message 12 of 15
(268 Views)

Hi Oli,

The initialisation connection is also not used in the example VIs provided by Pico.
According to the help, the port does not necessarily have to be connected.

CookieBrezel_0-1710232156386.png

regards

 

0 Kudos
Message 13 of 15
(262 Views)
Solution
Accepted by topic author CookieBrezel

Hello everyone,
I have now found the solution to my problem (with the help of a Labview tutor).
The problem was not, as many suspected, with the VI, but with the call in Teststand.
After I adjusted the corresponding parameter, the VI call worked without any problems.

 

Load Option: Load dynamically
(in addition to Unload Option)

 

Perhaps this information will help with similar problems

 

Many thanks for your help

 

Greetings
Markus

Message 14 of 15
(146 Views)

Hi Markus,

 

Just a remark from my side: using dynamic load/unload, the VI gets loaded and unloaded on each call. This leads to flushing the feedback nodes back to data default values.

 

So "the problem" is actually the VI, using the load option is a workaround

 

Thanks for sharing the solution 🙂 Glad you are up and running with this!

 

 

0 Kudos
Message 15 of 15
(128 Views)