07-13-2023 05:11 AM
Why is this "stop" code not in your blue vi ?
It already had the Sequence Context as an input.
Using the STOP function is for sure not the way to do it.
07-13-2023 06:28 AM
All the code is in one "step vi" (a vi call in a step in teststand)
The vi "script" (the blue one) is the one that i want to kill if i request an abort command in testsand.
The vi in blue execute somme commands included in a script, it could be very short action and...very long....and wait action.
there is no while loop in this vi juts case action so no stop condition.
If there is a better clean way to force a vi (and his subvi ) to stop executing i'm interested !
07-13-2023 07:08 AM
Hi vincent,
@vincent69 wrote:
The vi "script" (the blue one) is the one that i want to kill if i request an abort command in testsand.
The vi in blue execute somme commands included in a script, it could be very short action and...very long....and wait action.
there is no while loop in this vi juts case action so no stop condition.
Are those "somme commands" 3rd party executables? Or are these other subVIs/LabVIEW functions?
What is a "very long action"?
How long is that "wait action" and how is it performed?
You cannot stop 3rd party executables by calling the LabVIEW Stop function…
07-13-2023 07:15 AM
Hello, thank you for the reactivity that's very cool !
It's only a VI who call sub vi. there is no other code frome another environnement or source (i will have the problems later in the project with a DLL call !)
It's a vi who send visa instruction to some device, some test can wait a trigger more than 30s.
There is also wait action (made juste by the wait vi of ni) that can be set to 0 until 60s