MTS Multipurpose Elite - Manual (Page 99)

Comments MPE Activity or
Term MPT Process or
Term
To replicate the MPT single process in MP, the designer must
create one runtime control, three activities and tie them together
with one variable.
These are equivalent, except for the trigger continuously mode. Peak-Valley
Change Detector Peak/Valley Change
Detector
These are equivalent, except for the trigger continuously mode. State Change
Detection Program Event
These activities cover similar functionality: triggering periodically
based on calendar date, day of the week, or time. However, the
approach to specifying this information is different. Periodic Time
Event Activity Periodic Time Event
These are equivalent, except that MPT gives the test designer
flexibility on whether or not to log a message and its severity. Break Detection Failure Detector
MPE always logs a message with the severity level of
Informational.
In MPT, several event processes can trigger and remain active
to trigger again. MPE does not have an equivalent concept. The Program Event,
Digital Input,
test designer must use a While Loop to get equivalent
functionality. Operator Event,
Peak/Valley Change
Detector, Periodic
Time Event
8.8.0 External Control
Comments MPE Activity or
Term MPT Process or
Term
Functionally equivalent. MPT specifies a single pulse width for all
outputs. MPE allows a separate pulse width for each output. Set Digital Output Digital Output
MPT supports ramp temperature and wait for soak time. MPE does
not support these processes. Temperature channels can be ramped Not available Temperature
Control
using the normal Ramp activity. The soak time can be implemented
using variables and certain activities.
Multipurpose Elite Test Design Guide 99
8.0 Appendix A: MPE for MPT Users