MTS Series 793 - Manual (Page 467)

• The prefix and the parameter must be separated by a space.
• If the parameter name contains a space (for example, parameter set 2), it must be enclosed in quotation
marks.
Decorator-based command line example
Use the following example as a reference when you create your decorator-based command line.
Assume you want to start Station Manager with the following command-line options:
• Configuration file name = test.cfg
• Parameter set name = parm set 1
• Interlock chain = 1
• Restore views = saved
• User access level = tuning
• Password = Tuning (case-sensitive)
The decorator-based command line should look like this:
C:\tsiis\ntbin\Stmgr.exe /St test.cfg /Par “parm set 1” /I 1 /V saved /U tuning /Pas Tuning
Keep in mind:
• There must be a space between the original command line entry and your first prefix.
• Each parameter must be preceded by the correct prefix.
• If the parameter name contains a space, the parameter name must be enclosed in quotation marks.
• Password is the only parameter that is case-sensitive.
Precedence-Based Command Line Format
The precedence-based command line format does not require prefixes. This format is simpler, however,
parameters must be listed in a specific order.
When you are creating a precedence-based command line, keep in mind:
• Parameters must be defined in the proper order.
• The parameters must be separated by a space.
• You do not have to define all parameters, but if you want to specify a parameter that is recognized later
in the order, you have to define all of the preceding parameters.
• If the parameter name contains a space (for example, parm set 2), it must be enclosed in quotation marks.
Command-line parameter order
In a shortcut command line, options are recognized in the following order:
Station Manager
1. Configuration file name
MTS Series 793 Control Software 467
Command Line Shortcuts