Remote Operation Getting Started Guide
Command syntax and format requirements
Transport Module, DMC, MSAM, and 5800 Remote Operation
5
:SENSE:DATA? cstatus:physical:signal
Setup and action values
are
case-sensitive.
:SENSe:PAYLoad:BERT:PATTern ALL_ONES
Correct
:SENSe:PAYLoad:BERT:PATTern all_ones
Incorrect
Sockets and
messages
All remote control communications are socket-based TCP/IP. Any message passed via
remote control must be terminated with a newline character ("\n") as shown (or ENTER in
direct entry mode).
:INITiate\n
Without the following \n, a message may be interpreted incorrectly or cause an error condi-
tion.
Issuing multiple
commands
You can issue multiple commands on a single line by separating each of the commands
using a semicolon. The following examples show correct and incorrect presentation of the
multiple commands.
:INITiate; :SYSTem:ERRor:NEXT?\n
Correct
:INITiate :SYSTem:ERRor:NEXT?\n
Incorrect
Serial command
processing
The remote control system processes commands sequentially in the order they are
received. It does not process multiple commands simultaneously. If a command is sent
while another command is still being processed, the second command will not be
processed until the first command has been fully executed.
Short-form v. Long-
form commands
Commands may be abbreviated using the short form (the capital letters in the command).
Each word in the command may be either the long or short-form.
If long-form is used, the entire word must be specified; "partial" long-form is not recognized.
The following examples show the complete long-form version followed by various, short-
form versions of the same command. The final example shows an example of "partial" long-
form that is not acceptable.
:SENSe:DATA? CSTatus:PHYSical:SIGNal
Correct
:SENSe:DATA? CST:PHYS:SIGN
Correct
:SENS:DATA? CSTatus:PHYS:SIGNal
Correct
:SENS:DATA? CST:PHYS:SIGN
Correct
:SENS:DATA? CST:PHYS:SIGNa
Incorrect
