10-27-2008 07:23 PM
Hi,
When I use the run vi asynchronously step from the sequence file load callback, the callback hangs and the main sequence will not run. I have unchecked the wait for execution to complete box but this does not work. I would like my vi to open when the sequence file is opened and close when the file is closed, currently my vi opens and closes with each uut and this is not ideal. Does anyone have any suggestions?
Thankyou
Michael
10-28-2008 07:40 AM
Hi,
What TestStand and LabVIEW versions are you using?
Regards
RAy Farmer
10-28-2008 09:41 AM
Hi,
I am using LabVIEW 8.2 and TestStand 4.01. I pass a reference to the VI i am opening, and use this with the TestStand get/set property value vi's. I was wondering if my problem is because the SequenceFileOpen callback is an engine callback? Would the reference passed in to the VI be valid in the main sequence?
Thanks
Michael
10-29-2008 01:49 AM
Hi,
The possible problem is that the SequenceFileLoad is not in the same execution and wants to finish but can not because you have open references. You need to release any references which probably is not going to help you. Can you not put your VI both the UUT loop?
Regards
Ray Farmer
10-29-2008 05:30 AM
Hi
The only reason for wanting to open the VI with the sequence file is for aesthetics. Teststand is running in a Labview UI at the bottom half of the screen and the test VI occupies the top half of the screen. At the moment the test VI opens and closes with each UUT, it would be desirable for it to stay open until the sequence file is closed (the end of the batch). I can see what you mean about open references, and without using global or shared variables to communicate with the VI, I do not think it is possible.
Regards,
Michael