Program event process, About the program event process, Program event process 373 – MTS Series 793 Application User Manual
Page 373
![background image](/manuals/568035/373/background.png)
Program Event Process
MTS MultiPurpose TestWare®
Event Process Descriptions
373
Program Event Process
About the Program Event Process
The Program Event process is typically used to trigger other processes in
response to a change in the test state.
There are seven test states that can generate a trigger and/or done signal in the
Program Event process:
•
Running—the state in which the procedure is controlling the machine and
playing out a waveform.
•
Entering Hold—the transition state between Running and Holding.
•
Holding—the state in which the test is suspended (the actuator is not
moving), but the test can be continued by clicking the Run button.
Note
This process sees a “paused” state in the same way that it sees a
Holding state. That is, as the run indicator on the Station Controls panel
blinks while “paused,” this process will see the following sequence of
transitions: Running>Entering Hold>Holding>Exiting Hold>Running.
•
Exiting Hold—the transition state between Holding and Running. It will
typically complement what is done in the Entering Hold state.
•
Entering Stopped—the transition state between Running/Holding and
Stopped.
•
Stopped—the Stopped state. Once in this state, the actuators are fully
stopped. If appropriate, the test can be continued by clicking the Run
button, but it will not start up by itself.
Note
The only MPT command process that will run during a Stopped state is
the Digital Output process.
•
Exiting Stopped—the transition state between Stopped and Running. It
typically complements what is done in the Entering Stopped state.
Behavior with Stopped
and Holding states
Most processes stop or suspend themselves when MPT enters a Stopped or
Holding state. When a Program Event process detects one of these states, the
process that is triggered will typically see that MPT is stopped or holding and
refuse to do anything. Because it is common to use a Program Event process to
trigger a Digital Output process that turns off an external device when the test is
stopped, the Digital Output process is designed to function in a Stopped or
Holding state.