TestStand does not TestStand does not continue after vi terminates with error

[finistere21]

I ran into the strangest thing the other day, i have a vi written in 8.6.1 that i've sequenced in teststand 4.1.1 it works great, unless i pass out an error. then teststand doesn't seem to realize the vi has terminated, the error i'm passing out is custom, cluster contains a error code 5000, boolean value of true, and a string stating that it was unable to connect. let me see if i can attach it, it's made to be sequenced, so you may have to modify the inputs a bit to get the vi working right.... thanks for any feedback. you will need both vi's as one is embedded in the other.

Kris

[RayFarmer]

Hi,

You have to actually connect the error to the error out!

 

Regards

Ray Farmer

Message Edited by Ray Farmer on 08-13-2009 09:09 PM

[finistere21]

Yeah, sorry i did try that, among other options for passing one error out or all, nothing seems to work...

I did try it again after your suggestion for a sanity check, to no avail. the thing that gets me is that it works fine when there's no error.. grrrr.

[RayFarmer]

Hi,

Can you post an example sequence file that uses this VI which highlight the problem.

Regards

Ray Farmer

[finistere21]

odd, i think i know what the problem is just not how to fix it. i pulled the sub-sequence out to attach it here, modified it to work alone, and problem solved. let me explain a little more on this test...

I'm using a vi as a GUI that gets pull up in a main sequence, using a notifier i pass the test (sub-sequence) name out from the GUI to teststand, once teststand is notified of the change, it runs the specified sequence. as the problem manifests it's self in a subsequence, i don't think that the error is getting passed from the sub to the main. any ideas? thanks again.

Kris