Quantcast
Channel: LabVIEW topics
Viewing all articles
Browse latest Browse all 69116

Anyone know why the vi niFgen Allocate Waveform.vi causes a second instance of LabVIEW to open in Windows

$
0
0

I have a large scale ATE written in LabVIEW 2011, using TestStand 2010 SP1 as the test executive that works just fine until the test sequence ends. For some reason when I close the completed executions from the Sequence Editor, a second instance of LabVIEW that gets launched when this vi executes stops responding, and I have to kill all LabVIEW processes to be able to run another execution.

 

I can't figure out why this vi is causing a second instance of LabVIEW to start, much less why it causes LabVIEW to hang.

 

Any ideas? I've included a screen capture of the implementation being used (the vi between the two breakpoints is when this second instance of LabVIEW launches)


Viewing all articles
Browse latest Browse all 69116

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>