Record Results from sequence call inside of SequenceFilePostStepFailure Callback

[Jaws8you]

Test Stand 3.1

When a step fails I use SequenceFilePostStepFailure Callback.

In there I have prompt:

1. Continue

2. Terminate

3. Terminate (thus calling a power down sequence file)

Problem is that when Option 3 is used. There are no results recorded from that sequence call because it was invoked from the Callback.

How do I force record results when that sequence file is called?

[Doiron]

Hi Jaws8you,

It appears as if this thread has some great information on passing parameters from callback sequences: http://forums.ni.com/ni/board/message?board.id=330&thread.id=19398

Check that out and let me know if you have any questions.

[Doiron]

Hello Jaws8you,

After looking into this issue further, it appears as if the link I posted has some great information but is not an exact fit for your particular situation.

Because results from sequence callbacks will not populate in the report, we need to make sure and have any results we would like included in the main sequence.

In your case we are just going to put the sequence call in the "Clean Up" tab, which will report the data, and is good programming practice.

So to fix this problem, let's go ahead and try this:

1.) Change the variable "Locals.ButtonPressed" to FileGlobals.ButtonPressed in the locations that you have it so far

2.) "Cut" the "Call Main Power Down" sequence call from the "SequenceFilePostStepFailure" step, and copy it to the "CleanUp Tab" of "Main Sequence"

Basically, that should be it. What this will do now is run the "Call Main Power Down" sequence when button 3 is pressed and skip this step whenever button 1 or 2 is pressed. The result is then published in the report.

This should work out the best for you, thanks for posting and have an awesome day!

[Jaws8you]

The only problem with that is that I wouldn't call it instantly. It will call it after the entire sequence has ran.

This is almost what I want but not quite.

So if the operator selects Terminate and Call power down, it would have to run the entire sequence then run clean up. Sometimes if there is more then one failure it may give the operator a false sense that the 3rd buttton doesn't do anything.

Thanks for the follow up response.

[Doiron]

Good Morning Jaws8you,

It looks like what we could do here is make a top level sequence file that calls the sequence you are using currently but take any steps you would like to after the randomsequence call and put them after the call in the top level sequence.

This should prevent the unacceptable behaviour you are seeing.