03-12-2024 02:25 AM
03-12-2024 03:20 AM
@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
03-12-2024 03:36 AM
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.
regards
06-10-2024 09:02 AM
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
06-11-2024 06:53 AM
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!