Device documentation requirements


The following information relates to the compliance with the IEEE 488.2-1987 standard.

(1) IEEE 488.1 interface functions


This device does not feature a GP-IB interface.


(2) Operation with a device address other than 0 through 30


Because this device does not feature a GP-IB interface, address settings are not available.


(3) Timing of changed device address recognition


Similar to reason given for (2) above, address settings are not available.


(4) Device settings at power on


The settings are basically backed up.

Contents

Initial value

Command

Channel (index) and pointer (offset) by :MEMory:POINt

Random

:MEMory:POINt CH$,A

Display update setting by :DISPlay:UPDAte

TRUE

:DISPlay:UPDAte A$

Standard event status register (SESR)

128

-

Event status register 0 (ESR0)

0

-



(5) List of message exchange options


(a) Capacity and operation of the input buffer
The input buffer consists of a 1024-byte ring buffer. When the buffer is filled to capacity, additional commands will be ignored.


(b) Which queries return more than one <RESPONSE MESSAGE UNIT>
No queries return multiple response messages.


(c) Which queries generate a response when parsed
All queries produce responses when syntax checking is performed.


(d) Which queries generate a response when read
No queries produce response messages at the instant they are read by the controller.


(e) Which commands are coupled
There are no relevant commands.


(6) Summary of functional elements for use when constructing device specific commands, and whether compound commands or program headers can be used:


The instrument uses following functions.


(7) Buffer capacity limitations for block data


Block data is not used.


(8) Summary of program data elements used in expressions, and deepest nesting level allowable 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


Response syntax is detailed in "Details"


(10) Transmission congestion relating to device-to-device messages which do not conform to the general principles for basic response messages


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


This appears in "Standard Commands"


(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.
When using the "*DDT" command, the maximum length of block used in a trigger macro definition


The "*DDT" command is not used.


(15) Existence/nonexistence of macro command.
When a macro command is being executed, the maximum length of macro label, the maximum length of block for defining a macro, and how echoing is managed when expanding a macro


Macros are not used.


(16) For queries related to identification, explanation of the response to the "*IDN?" query


This is detailed in "Query Device ID"


(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 "*PUD?" query are not used, and there is no user data storage area.


(18) Resources when the "RDT" command and the "RDT?" query are being used


The "*RDT" command and "*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 resets the instrument to its initial state.


(20) Scope of the self-testing executedas a result of the "TST?" query


Checks the internal ROM and RAMs.


(21) Additional organization of the status data used in a device status report


This is detailed in "The status byte and event registers".


(22)Whether commands are overlap or sequential type


All the commands are sequential except for the ":ABORT" command.
An ":ABORT" command is executed instantly as soon as it is received.


(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.