Modifying Engine Callbacks

TestStand 2019 Help

Edition Date: May 2019

Part Number: 370052AA-01

»View Product Info
Download Help (Windows Only)

The TestStand Engine invokes a set of Engine callbacks at specific points during execution. TestStand defines the set of Engine callbacks and the callback names because the engine controls the execution of steps and the loading and unloading of sequence files.

Use Engine callbacks to configure TestStand to call certain sequences at various points during a test, including before and after the execution of individual steps, before and after interactive executions, after loading a sequence file, or before unloading a sequence file.

TestStand categorizes Engine callbacks according to the file in which the callback appears. You can define Engine callbacks in sequence files, process model files, and in StationCallbacks.seq in the <TestStand Public>\Components\Callbacks\Station directory.

Note Note  TestStand does not predefine any Station Engine callbacks in StationCallbacks.seq in the <TestStand>\Components\Callbacks\Station directory but might in a future version of TestStand.

TestStand invokes Engine callbacks in normal sequence files only when executing steps in the sequence file or when loading or unloading the sequence file. TestStand invokes Engine callbacks in process model files when executing steps in the model file, steps in sequences the model calls, and steps in any nested calls to subsequences. TestStand invokes Engine callbacks in StationCallbacks.seq when TestStand executes steps on the test station.

You can use Engine callbacks in the following ways:

  • Use the SequenceFileLoad callback to ensure that you configure external resources the sequence file uses only once before you execute the sequence. Usually, you initialize devices a sequence requires by creating steps in the Setup step group for the sequence. However, when you call the sequence repeatedly, you can move the Setup steps into a SequenceFileLoad callback for the subsequence file so that the steps run only when the sequence file loads.
  • Use the StationPreStep and StationPostStep callbacks to accumulate statistics on all steps that execute on the test station. You can inspect the name and types of steps that accumulate data on specific steps.

See Also

Caveats for Using Engine Callbacks

Overriding PreBatch and PostBatch Model Callbacks (Example)

Overriding PreUUT and PostUUT Batch Model Callbacks (Example)

Overriding PreUUT and PostUUT Parallel Model Callbacks (Example)

WAS THIS ARTICLE HELPFUL?

Not Helpful