Fluke Calibration 5730A, Руководство оператора, Страница: 141 / 260

Remote Commands and Syntax
Commands
6
6-7
Sequential and Overlapped Commands
Commands executed immediately as they are encountered in the data stream are called
sequential commands. Commands that begin execution, but are completed some time
later are called overlapped commands, because they can be overlapped by later
commands. Headings under each command description in Tables 6-5 and 6-6 define
whether the command is sequential or overlapped. Because the 5730A Calibrator queues
and executes overlapped commands in a multitasking way,
*OPC
,
*OPC?
, and
*WAI
are
useful to detect completion of overlapped commands. (See the full descriptions of
*OPC
,
*OPC?
, and
*WAI
in Table 6-5 for more information.)
Commands Ignored When Not in Remote
The 5730A Calibrator can receive and execute most commands in either local or remote
state. Commands that change the state of the Calibrator are prevented from executing
unless the Calibrator is in the remote state. At the end of each command description in
Tables 6-5 and 6-6 it is noted if the command is ignored if the Calibrator is not in the
remote state. When the command description says, “ignored when not in remote,” it
means that if sent to the Calibrator in the local state, the command will not work, and
logs a fault into the fault queue. (Or it returns the fault message if in serial remote
terminal mode.)
To put the Calibrator in remote, send the REMOTE command (described in Table 6-6) to
the Calibrator. Refer to “Remote/Local State Transitions” for more information.
Commands that Require the Calibration Security Passcode
The subsequent commands do not work unless preceded by the
CAL_SECURE OFF,
<passcode>, CLOCK, CAL_STORE, CAL_RNG STORE, CAL_WBFLAT
STORE, CAL_WBGAIN STORE, *PUD
, and
RPT_STR
. Attempting to use any of
these commands without doing so logs a fault into the fault queue. (Or it returns the fault
message if in remote terminal mode.)
Long Term Commands
Remote commands that take a relatively long time to execute are identified as such in
Table 6-5, which follows the command summary in Table 6-4. If a command that
produces a change in 5730A Calibrator state (for example any “OPER” command) is
received during the execution of a long-term command, for example,
CAL_CHK
, the
command is ignored and a device-dependent fault occurs. (Bit 3 in the Event Status
Register is set to 1 if enabled, and the fault code for the fault is available to be read from
the fault queue. See the
FAULT?
and
EXPLAIN?
commands for more information.)