User's Manual
Table Of Contents
- 45 Dual Display Multimeter
- 1. Introduction
- 2. Getting Started
- 3. Operating the Meter From the Front Panel
- 4. Applications
- 5. Operating the Meter Using the Computer Interface
- Introduction
- Preparing the Meter for Operations via the RS-232 Interface
- Preparing the Meter to be Operated via IEEE-488 Interface
- Getting Started With An Installation Test
- How the Meter Processes Input
- How the Meter Processes Output
- Triggering Output
- Service Requests (IEEE-488 Only and Status Registers
- Computer Interface Command Set
- IEEE-488 Capabilities and Common Commands
- Function Commands and Queries
- Function Modifier Commands and Queries
- Range and Measurement Rate Commands and Queries
- Measurement Queries
- Compare Commands and Queries
- Trigger Configuration Commands
- Miscellaneous Commands and Queries
- RS-232 Remote/Local Configurations
- Sample Program Using the RS-232 Computer Interface
- Sample Programs Using the IEEE-488 Computer Interface
- 6. Maintenance
- Appendices

45
Users Manual
18. The size of the resource description, if the *RDT command or *RDT? query are
implemented, Sections 10.30 and 10.31.
The *RDT and *RAT? commands are not implemented.
19. A description of the states affected by *RST (Section 10.32), *LRN? (Section 10.17),
*RCL (Section 10.29), and *SAY (Section 10.33).
*LRN.2, *RCL, and *SAT are not implemented. *RST restores the meter to the state
assumed at power-up (using the stored configuration), except for those items
specifically forbidden by the *RST command definition.
20. A description of the scope of the self-test performed by the *TST? query, Section
10.38.
*TST? performs the tests listed under "*TAT?" in Table 5-8 of the Users Manual.
The meter reverts to the stored configuration after performing these tests.
21. A description of additional status data structures used in the device’s status reporting,
Section 11.
There are no additional data structures.
22. For each command, a statement describing whether is overlapped or sequential.
All commands are sequential; none are overlapped.
23. For each command, the device documentation shall specify the functional criteria that
are met when an operation complete message is generated in response to that
command, Section 12.8.3.
Operation complete is generated when the command is parsed. Note that MEAS?,
MEAS1?, and MEAS2? prevent the parser from continuing until all requested
measurements have completed. (This includes any time waiting for the trigger). The
VAL, VAL2?, and VAL2? queries will also wait for trigger if the needed display
measurements have never been done