NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Teststand 3.5 Error -17306 on step NI_Flow_End and crash after some of them


Hello everybody,

i've got a problem with Teststand 3.5 running long time tests. The test is using the BatchModel and model callbacks.
I added the callback "ProcessModelPostStepRuntimeError" to log errors and a added sequence called "TesterHealth" to check the peripheric equipment in case of RunTimeErrors.
Since the "ProcessModelPostStepRuntimeError" is in, i get runtime error like this:


End caused RunTimeError.  Error Code: -17306 Msg: Unknown variable or property name ''

 

but only from sequences in the model.
The whole thing keeps on running until 6 entries have occured, then Teststand crashs either with "R6025 Pure Virtual Function Call" or
a -17502 Exception of a "Goto" step in the model.

This doesn't happen, if i remove the "ProcessModelPostStepRuntimeError" and place a "SequenceFilePostStepRuntimeError" in each file instead.

Has anyone an idea, what's wrong?

Best regards,
Thomas

0 Kudos
Message 1 of 5
(3,769 Views)

Do you have a flow control end step for a foreach loop at the end of a sequence. There is a known issue related to that. The workaround is adding a label step to the end of the sequence so that the flow control end step is not the last step. I'm not sure if this is the issue you are seeing. There are potentially other reasons why you could get these errors. Let us know if you had such a foreach loop and if adding a label step to the end of the sequence fixes the problem.

 

See this forum post for more information:

http://forums.ni.com/t5/NI-TestStand/TestStand-crashes-by-for-each-loop/m-p/989898#M26030

 

 

Hope this helps,

-Doug

0 Kudos
Message 2 of 5
(3,761 Views)

Hello Doug,

 

hmm, the error appeared at two locations. Both are "ForEach" loops. the first one was an "end" followed by the next "if". At the second location is - as you said - the "End" the last step of the sequence. I placed at both locations a label after the "End" and will report if it helped.

 

Thanks so far

Thomas

 

0 Kudos
Message 3 of 5
(3,749 Views)

No, didn't work.I still get the RTE on "END". But this time it didn't crash, but it hanged with the "TestUUTs" execution. Unfortunally could not break or debug, because was in Operator Interface as "Operator". Could only terminate it. 😞

I now replaced the ForEach by a Goto with precondition as in Teststand 1.0

 

Regards

Thomas

0 Kudos
Message 4 of 5
(3,674 Views)

A label step after the foreach End step should fix the problem if it's the same as the known issue. It is likely not the same problem then. What type of things are you doing foreach on? Can you reproduce this in a simple case?

 

Thanks for any info,

-Doug

0 Kudos
Message 5 of 5
(3,667 Views)