SequenceFilePostStepFailure and execution

[Zuc_Lab]

Good Morning,

I do not know if anyone has ever encountered this issue but I’m trying to understand better how TestStand execute. In my sequence I have a call to some VIs which have as a labviewIOcontrol parameter (task_in and task_out parameters) to exchange within the sequence to control the Digital and Analogical Tasks of an USB-6211. Sometimes the Task seems not to be managed well and the VI goes in an exception error. By doing so the following Pass/Fail step will fail since no IO is managed. I don’t get why for these failed steps the SequenceFilePostStepFailure seems not to be called. In that Callback I send some further data to the database and those data aren’t present in it. Why does it happens?

Is there anyone that can suggest me how to observe or further analyse the matter? Just an hint to understand what can be my next move since I have finished the Ideas.

Best regards,

Zuc

[Oli_Wachno]

Neither PTT_On.vi nor PTT_Off.vi have an Error Out. TestStand simply doesn't know an error has occured!

[Zuc_Lab]

Sorry for the stupid question, but if i have a pass/fail step between the calls of the PTT_TaskOn and the PTT_TaskOff sequences and it is failed, will the SequenceFilePostStepFailure will be not executed even if the step has failed as a result?

[Oli_Wachno]

Sorry, mistake was on my side.... I read Error instead of Failure 😞

---

@Zuc_Lab wrote:

Sorry for the stupid question, but if i have a pass/fail step between the calls of the PTT_TaskOn and the PTT_TaskOff sequences and it is failed, will the SequenceFilePostStepFailure will be not executed even if the step has failed as a result?

---

The  SequenceFilePostStepFailure is not executed if a RunTime Error has occured:

https://www.ni.com/docs/de-DE/bundle/teststand/page/step-execution.html

See Action 18.

Having said that: Errors during testing don't mean, that DUTs are "bad", it just means that something has happened, that wouldn't allow for a complete test. That's why the seq result is Error and noch Passed/Failed.

[Zuc_Lab]

So if i get it right since a step has generated an error, for the sequence is useless to save the result of the following steps since the status of the whole sequence will be error for sure. I mean this is what i can infer from here https://www.ni.com/docs/en-US/bundle/teststand/page/run-time-errors.html?srsltid=AfmBOophEL_mqbCQmMy... also because for the sequence it will jump to the clenup section. So since my sequences are short, with no clean up section since they only call a VI can be the solution to manage the Errors in some way with SequenceFilePostStepFailure? Do you have any advice on how to manage an error of unknown DAQmx task in that callback sequence?

Thank you for the help!

Best Regards,

Zuc

[Oli_Wachno]

Failures are handeled with SequenceFilePostStepFailure, whereas

(Runtime) Errors are handled with SequenceFilePostStepRuntimeError

exmples can be found at %teststandpublic%\Examples\Fundamentals\Overriding Engine Callbacks

E.g. you could check for certain error codes....