Hioki 3332 - 11.2 Standard Specifications

191
────────────────────────────────────────────────────
8.8 Device Compliance Statement
────────────────────────────────────────────────────
(9) Response syntax for queries
Response syntax is detailed in "Command Reference".
(10) Transmission congestion relating to device-to-device messages which do
not
conform to the general principles for basic response messages
It is possible to output with talk only function. Message format is described
in Section 8.7.6, "Printing Example."
(11) Response capacity for block data
Block data does not appear in responses.
(12) Summary of standard commands and queries used
This appears in Section 8.5, "Command Summary."
(13) Device state after a calibration query has been completed without any
problem
The "
*
CAL?" command is not used.
(14) Whether any "
*
DDT" commands are used:
The "
*
DDT" command is not used.
(15) Whether any macro commands are used:
Macros are not used.
(16) For queries related to identification, explanation of the response tothe
"
*
IDN?" query
This is detailed in "Command Reference".
(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.
(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 3332 to its initial state. (Refer to "Standard Commands", and
"Initialization").
(20) Scope of the self-testing executed as a result of the "
*
TST?" query
This is detailed in "Standard Commands".
(21) Additional organization of the status data used in a device status report
This is detailed in "Event Registers".
(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 "MEASure?"
query, when and only when there is no effective data, terminates when
effective data has been produced. The "
*
TRG" command terminates the
moment that measured data has been obtained.