Controlling Test Sequence Flow from inside the ProcessModelPostStepFailure Engine Callback

[SercoSteve]

Hi Sacha

Thanks for the zip, unfortunately we are running TS 3.1 here, cant open TS 3.5 Files

Regards

Steve

[SachaE]

oops - forgot - and Ray's post reminded me - that used to be the case about jumping backwards, but you can change the step group as in the attached new example.

Sorry - I'd better look at 3.5 a bit more closely in the future!!!!

Sacha Emery
National Instruments (UK)

[SercoSteve]

Hi Sacha

Still TS 3.5

Steve

[SachaE]

Timing is everything - here it is for 3.1

Sacha Emery
National Instruments (UK)

[SachaE]

Just realised - you could more generic by referring to Parameters.Step rather than the Runstate.CallingStep

Good luck

Sacha Emery

National Instruments (UK)

[RayFarmer]

Hi,

Sacha hopeful has answered any outstand questions.

But just to add, you can check the SequenceName in the Callback by using NameOf(RunState.Caller.RunState.Sequence) and this will return the name of the Sequence as a string eg "MainSequence".

Hope this helps.

Regards

Ray Farmer

[SercoSteve]

Thanks guys

Everything is good in the land TestStand 3.1

Thanks for all your efforts

Steve

[kevmi2ca]

Can anyone help me with this??

I need to do the exact thing, retry failed tests using the ProcessModelPostStepFailure Callback, but it's not working.

The strange thing, it runs fine if I run it from the TestStand environment, but when launch using my OI, it will not retry the step. It's like the RunState.Caller...StepIndex is not working properly. Doesn't make sense to me. One note, my sequence(s) are built dynamically, but they run just like a normal sequence.

Thanks a lot.

[kevmi2ca]

Actual, it doesn't work from Teststand environment either. I think I've been staring at it all too long.

Again, any help is appreciated.

[kevmi2ca]

Found the problem!

If "Step Failure Causes Sequence Failure" is checked, the "Retry" does not work.