Termination does not appear as fail sequence

[Rafi2003]

Hi,

I have I a subsequence than include some Action type step.  The step set a local variable.  Based on that variable I decide whether to continue or to terminate.

In the event of termination, the process is indeed terminated, but when I look at the report generated by TestStand, the subsequence have a Pass mark.

Is this normal?  I would have expected to see Fail or Termination....  How do I fixe this problem to show a fail sequence?

Thanks

Rafi

[j_dodek]

Hi Rafi

Your are right !! (I have tested it under TS4.0) After six years of Teststand programming i assumed that it should work as you descripe !
It seems I am wrong !?

I have wirtten a wrapper in the EngineCallback SequenceFilePostResultListEntry to filter TerminationState an add this feature to the report.

Greetings from the lake of Constance, Germany

Juergen

[RayFarmer]

Hi,

It returns a "Terminated" status in TestStand 2.0. So something has changed in the later versions.

Regards

Ray

[dug9000]

This is fixed in TestStand 4.0.1. It now returns a "Terminated" status for the sequence call.

[RayFarmer]

Hi,

I ran Juergen example in TS 4 and it indeed showed Passed for the SequenceCall (by the way I delete the Callback).

When I ran my example it showed Terminated.

The Different being, in Juergen example he used ThisContext.Execution.Terminate() to force the terminate.

In my example I used the Post Action of the step to force the Terminate.

But as dug points out its been fixed in 4.01.

Regards

Ray

[j_dodek]

Hi, Ray

Thanks for your tests. I have also tried with PostAction now. But the result is still the same.

How have you done this ?

By the way as Dug said in TS 4.0.1 it is fixed.

What do you think about updating to the newest version ?

I am concernd when i received a letter from NI about latest DAQmx problem

(infocode rda4a4) and this affects TS 4.0.1 and CVI 8.5

Greetings

Juergen

[RayFarmer]

Hi,

Do you mean this

http://digital.ni.com/public.nsf/allkb/28637F55A85EAD64862573A900008D3B 

If you are using DAQmx then I think the concern is getting a working DAQmx without corrupting the rest of your system.

I dont think there is a problem with upgrading to TestStand 4.0.1, it would depend where you are in your developement cycle.

I would check out the release notes before proceding.

And of course backup your work before upgrading so you have a stake in the ground to go back to.

Regards

Ray

[Josh_W]

j_dodek,

You can download TestStand 4.0.1 here.  This evaluation software does not include DAQmx, so you will not be affected by the troublesome behavior described in the letter you received.

Or if you received the TestStand 4.0.1 disks, if you don't install the included driver CDs you will not be affected.

[RayFarmer]

Hi Juergen,

Nothing is setting RunState.SequenceFailed = True.

I added the line RunState.SequenceFailed = True both the Terminate() in the Post Expression of your Forced Terminate Step of your MySequence and it then made the SequnceCall step in MainSequence to be Failed.

Regards

Ray

[Rafi2003]

Hi Ray

I added this line and it works great

Thanks a lot

Rafi