Teststand callback sequential model

[Rodéric]

Hello everyone,

I'm looking for some documentation related to TestStand sequential model callbacks, I need to know when each callback is launched. I'd like to get this info for Application manager and Engine callbacks.

Also, I'd like to know how to detect when an execution ends to trigger an event in my HMI (LabVIEW)

Best regards,

[~jiggawax~]

You can look at your process model and see when all the model callbacks are being called.  Just open the process model in the Sequence Editor.  It is just a sequence file.  Engine callbacks are trickier because they occur when a specific event occurs.

https://www.ni.com/en/support/documentation/supplemental/07/using-callbacks-in-ni-teststand.html

https://www.ni.com/docs/en-US/bundle/teststand/page/callback-sequences.html

Also look in the TestStand Reference Manual found in your TestStand documentation folder.

In regards to your HMI.  Is this something you created yourself or are you customizing the User Interfaces that ship with TestStand?  Or is this something you want to execute once the Execution is completed.  Does it have to happen upon completion or near the end of completion.  Because you could just override the Process Cleanup callback which occurs close to the end.

[Rodéric]

Thanks for the answer, I customized the full featured interface, I'm now editing a sequence from my HMI, I can skipp steps, and choose how many times each step executes. but if I edit the sequence several times, I get reference leak problems (files are not released properly) so I have to close the file reference after the sequence executed (only in that "editor mode" I also have a production mode and a separated maintenance mode) maybe it is not the best way to do what I'm trying to do but it does the trick if I call my release reference VI manually. So I want to trigger that subVI I was planing on using the EndExecution Callback (I can add it wiring the application manager to the register for event method) and overiding it to add a user event within LabVIEW that will trigger my subVI