3
53210A Measurements
Same Subsystem
commands can also be sent in a single string. The first command references the
root node, and subsequent commands separated by semicolons, are referenced to
the same level as the previous command. As an example, the command sequence
representing the
CALC2:TRAN:HIST:STAT ON
CALC2:TRAN:HIST:POIN 15
CALC2:TRAN:HIST:RANG:AUTO ON
CALC2:TRAN:HIST:RANGe:AUTO:COUNt 300
can be sent in a string as:
CALC2:TRAN:HIST:STAT ON;POIN 15;RANG:AUTO ON;AUTO:COUN 300
Separate Command Lines or Strings?
rather than in separate command lines can eliminate "settings conflict" errors.
When sent on separate lines, the counter checks for errors as each command
(line) is parsed. When sent as a string, the entire string is parsed before error
conditions are checked.
Linking IEEE 488-2 Common Commands and SCPI Commands
In a command string containing both IEEE 488.2 common commands (e.g.
*WAI
separated from the SCPI commands by a semicolon (;). An example is shown in
the following string:
CALC:STAT ON;AVER:STAT ON;:INIT;*WAI;:CALC:AVER:AVER?
Information on the SCPI programming conventions is also included in the
NOTE
Programmer's Reference.
88
For commands that share the same subsystem, multiple
CALCulate2
,
) and SCPI instrument commands, the common commands are
*OPC?
subsystem:
Sending commands in a single string
Keysight 53210A User's Guide
,
*RST