![background image](http://html.mh-extra.com/html/keithley/6430/6430_instruction-manual_661765272.webp)
13-14
Remote Operations
Single command messages
The above command structure has three levels. The
fi
rst level is made up of the root
command (:STATus) and serves as a path. The second level is made up of another path
(:OPERation) and a command (:PRESet). The third path is made up of one command for the
:OPERation path. The three commands in this structure can be executed by sending three
separate program messages as follows:
:stat:oper:enab <NRf>
:stat:oper:enab?
:stat:pres
In each of the above program messages, the path pointer starts at the root command (:stat)
and moves down the command levels until the command is executed.
Multiple command messages
You can send multiple command messages in the same program message as long as they are
separated by semicolons (;). The following is an example showing two commands in one pro-
gram message:
:stat:oper:enab <NRf>; :stat:oper:enab?
When the above is sent, the
fi
rst command word is recognized as the root command (:stat).
When the next colon is detected, the path pointer moves down to the next command level and
executes the command. When the path pointer sees the colon after the semicolon (;), it resets
back to the root level and starts over.
Commands that are on the same command level can be executed without having to retype
the entire command path. Example:
:stat:oper:enab <NRf>; enab?
After the
fi
rst command (:enab) is executed, the path pointer is at the third command level in
the structure. Since :enab? is also on the third level, it can be typed in without repeating the
entire path name. Notice that the leading colon for :enab? is not included in the program mes-
sage. If a colon were included, the path pointer would reset to the root level and expect a root
command. Since :enab? is not a root command, an error would occur.
Command path rules
•
Each new program message must begin with the root command, unless it is optional
(e.g., [:SENSe]). If the root is optional, simply treat a command word on the next level
as the root. For fastest operation, do not send optional data.
•
The colon (:) at the beginning of a program message is optional and need not be used.
Note that eliminating the
fi
rst colon will result in fastest operation. Example:
•
:stat:pres = stat:pres
•
When the path pointer detects a colon (:) it moves down to the next command level. An
exception is when the path pointer detects a semicolon (;), which is used to separate
commands within the program message (see next rule).
Summary of Contents for 6430
Page 26: ......
Page 32: ......
Page 78: ...2 14 Connections ...
Page 98: ...3 20 Basic Source Measure Operation ...
Page 138: ...5 30 Source Measure Concepts ...
Page 156: ...6 18 Range Digits Speed and Filters ...
Page 168: ...7 12 Relative and Math ...
Page 176: ...8 8 Data Store ...
Page 202: ...9 26 Sweep Operation ...
Page 248: ...11 22 Limit Testing ...
Page 310: ...16 6 SCPI Signal Oriented Measurement Commands ...
Page 418: ...17 108 SCPI Command Reference ...
Page 450: ...18 32 Performance Verification ...
Page 477: ...A Specifications ...
Page 489: ...B StatusandErrorMessages ...
Page 498: ...B 10 Status and Error Messages ...
Page 499: ...C DataFlow ...
Page 503: ...D IEEE 488BusOverview ...
Page 518: ...D 16 IEEE 488 Bus Overview ...
Page 519: ...E IEEE 488andSCPI ConformanceInformation ...
Page 523: ...F MeasurementConsiderations ...
Page 539: ...G GPIB488 1Protocol ...
Page 557: ......