ni.com is currently experiencing slowness/issues due to ongoing maintenance.

Support teams are actively working on the soonest resolution.

NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

problem with undefined sub VI's in TestStand

I am running Test Stand 1.0 with LabView 6i and I am experiencing a problem with undefined sub VI's. The test sequence will load the main VI's it calls correctly, and warn me if one of the main VI's it calls is undefined, but if a sub VI in that main VI is not found, it will crash the sequence, giving the error "unable to execute step" on the error dialog, BUT IT WILL NEVER ASK ME TO FIND THE MISSING SUB VI.
I have checked the box in the test editor under Configure > Station Options > Preferences "prompt to find files", but it doesn't prompt me if it can't find a sub VI. Why won't the system tell me if it can't find a sub VI, but yet it warns me if it can't find a main VI it calls directly.
0 Kudos
Message 1 of 2
(2,833 Views)
This one got answered by Richard Mahoney on the TestExec listserver - here's his answer below

From: "Mahoney, Richard C"
Subject: Re: problem with undefined sub VI's in TestStand

David,
I think Test Stand does not even Look for the SUB VI's. It sees that the
top level VI is unexecutable (Broken arrow) and the seq crashes. All of the
Top
level VI's have to be executable in order to be kicked off by Teststand.
I think the option you are referring to is to find the top Level VI, not
SubVI's.
You have to make sure all of your Top Level VI's are 'executable' prior to
running the sequence. Any other people care to verify / clarify this?
Hope this helps

Rick Mahoney
Equipment Test Design
Lockheed Martin Corp

NE&SS Syracuse

Sash.
// it takes almost no time to rate an answer Smiley Wink
0 Kudos
Message 2 of 2
(2,833 Views)