Programming instructions
Table Of Contents
- Contents
- Title Page
- Chapter 1 Introduction to Programming
- Chapter 2 Programming Getting Started
- Chapter 3 Programming over HP-IB
- Chapter 4 Programming over RS-232-C
- Chapter 5 Programming and Documentation Conventions
- Chapter 6 Status Reporting
- Figure 6-1. Status Reporting Overview Block Diagram
- Table 6-1. Status Reporting Bit Definition
- Status Reporting Data Structures
- Status Byte Register (SBR)
- Service Request Enable Register (SRER)
- Trigger Event Register (TRG)
- Standard Event Status Register (SESR)
- Standard Event Status Enable Register (SESER)
- User Event Register (UER)
- Local Event Register (LCL)
- Operation Status Register (OPR)
- Limit Test Event Register (LTER)
- Mask Test Event Register (MTER)
- Histogram Event Register (HER)
- Arm Event Register (ARM)
- Error Queue
- Output Queue
- Message Queue
- Key Queue
- Clearing Registers and Queues
- Figure 6-3. Status Reporting Decision Chart
- Chapter 7 Installing and Using the Programmer's Reference
- Chapter 8 Programmer’s Quick Reference
- Warranty
- Index
The Command Tree
The command tree shows all of the commands and the relationships of the
commands to each other. The IEEE 488.2 common commands are not listed
as part of the command tree because they do not affect the position of the
parser within the tree. When a program message terminator (<NL>,
linefeed-ASCII decimal 10) or a leading colon (:) is sent to the instrument,
the parser is set to the “root” of the command tree.
Command Types
The commands for this instrument can be placed into three types:
•
Common commands
•
Root level commands
•
Subsystem commands
Common Commands The common commands are the commands
defined by IEEE 488.2. These commands control some functions that are
common to all IEEE 488.2 instruments.
Common commands are independent of the tree, and do not affect the
position of the parser within the tree. These commands differ from root level
commands in that root level commands place the parser back at the root of
the command tree.
Example:
*RST
Root Level Commands The root level commands control many of the
basic functions of the instrument. These commands reside at the root of
the command tree. Root level commands are always parsable if they
occur at the beginning of a program message, or are preceded by a colon.
Example:
:AUTOSCALE
Programming and Documentation Conventions
The Command Tree
5-6