9.10 Device Compliance Statement
165
9
8. Summary of program data elements used in
expressions, and deepest nesting level allow-
able in sub-expressions, including syntax
restrictions imposed by the device.
Sub-expressions are not used. Character data and decimal
data are the only program data elements used.
9. Response syntax for queries
See: "9.7 Message Reference" (p. 122)
10.Transmission congestion relating to device-to-
device messages which do not conform to the
general principles for basic response mes-
sages
There are no device to device messages.
11.Response capacity for block data
Block data does not appear in responses.
12.Summary of standard commands and queries
used
See: "9.6 Message List" (p. 116)
13.Device state after a calibration query has been
completed without any problem
The “CAL?” query is not used.
14.Existence/nonexistence of “DDT” command
The “DDT” command is not used.
15.Existence/nonexistence of macro command
Macros are not used.
16.For queries related to identification, explana-
tion of the response to the “IDN?” query
See: "Standard Commands" (p. 123)
17.Capacity of the user data storage area
reserved for when the “PUD” command and
the “PUD?” query are being executed
The “PUD” command and the “PUD?” query are not used.
Further, there is no user data storage area.
18.Resources when the “RDT” command and
the “RDT?” query are being used
The “RDT” command and the “RDT?” query are not used.
Further, there is no user data storage area.
19.Conditions which are influenced when “RST”,
“LRN?”, “RCL?”, and “SAV” are used
“LRN?”, “RCL?”, and “SAV” are not used. The “RST”
command returns the unit to its initial state.
See: "Standard Commands" (p. 123),
"Initialization Items" (p. 114)
20.Scope of the self-testing executed as a result
of the “TST?” query
See: " Standard Commands";"TST?" (p. 123)
21.Additional organization of the status data used
in a device status report
See: "Event Registers" (p. 111)
22.Whether commands are overlap or sequential
type
All the commands are sequential commands.
23.Criterion relating to the functions required at
the instant that the termination message is
produced, as a response to each command
Termination occurs when the command has been parsed.
The :READ? query finishes when the measurement data is
received.