SequenceFileUnload in TestStand 4.0 Parallel Model

[ToddK]

Has anyone experienced a problem when updating to TestStand 4.0 with the SequenceFileLoad and SequenceFileUnload callbacks?  I’m using the parallel process model configured for 8 threads and in earlier versions of TestStand have had no problems placing my hardware initialization steps in the SequenceFileLoad callback and the cleanup steps that release hardware references, in the SequenceFileUnload.   It seems very random that sometimes when I close my sequence, the Unload steps are executed.  Sometimes they only run if I select File->Unload All Modules or close TestStand. 

Is there a flag in TestStand that I can use to trigger the Unload steps or possibly a better place in the parallel model to place my hardware cleanup?  I don’t want to release and have to reinitialize hardware references with each loop so any cleanup steps will need to be done once after all parallel threads are finished.

[~jiggawax~]

Most of the time people do this in the Process Setup Callback and Process Cleanup Callback.  Those are process model callbacks that you can override from your client sequence.  They are probably better to use than the engine callbacks (SequenceFileUnload and SequenceFileLoad).  They get executed before and after the looping respectively.

If you open the process model you'll see where they get called.  Process Setup Callback is in the Setup step group and Process Cleanup Callback is in the Cleanup step group.

Regards,