MTS Multipurpose Elite - Manual (Page 74)

Description Item
Note:
This option is available only if you have
specified a single-channel Profile or Cycle
activity.
Selects the channel to which the compensation
ranges apply. Compensation ranges must be Channels
entered for each channel used by the Profile or
Cycle activity.
Specifies the upper range value and associated
units of compensation matrix for the selected
channel. Upper Range
Specifies the lower range value and associated
units of compensation matrix for the selected
channel. Lower Range
Specifies the difference between the commanded
peak and the actual peak achieved that you want
the application to detect. Missed-Peaks
Reference
Shows the total number of missed peaks (also
stored in the log file). This value is saved as part Missed-Peaks
Counter
of the run-time state of the process (in the mps
file), and can be restored accordingly.
6.2.11.3.0 General Profile Syntax Requirements
Review the following profile syntax requirements before you create a profile:
• You must separate profile entries with a space or a tab (when using a text editor).
• Profiles should be saved with a “.blk” extension so the default file filter in MPE recognizes them.
• Blank lines between rows may be inserted to improve readability.
• The profile must start with the header data definition, then with channel and command data definitions for
each succeeding channel defined in the profile. (Header data, Channel 1 data, Channel 1 command data,
Channel 2 data, Channel 2 command data, and so forth.)
• Keywords are not case-sensitive.
• Do not leave a space between the keyword and the equals sign (=). However, you can insert a space after
the equals sign to improve readability.
• Use header keywords (FileType, Date, and so on) only once.
• Use channel keywords (level, frequency, and so on) only once for each channel definition.
6.2.11.4.0 Header Data Syntax
The following is an example of proper header data syntax:
74 Multipurpose Elite Test Design Guide
6.0 Creating Advanced Tests