BNC 7000 Series Programmer Manual - Manual (Page 18)

18
:STATus
:SYSTem
:TRIGger
The purpose of the TRIGger block is to provide an instrument with synchronization capability
with external events. The TRIGger block is appears in the SCPI tree as TRIGger, ARM,
INITiate, and ABORt subsystems.
:UNIT
All SERIES 7000 SCPI commands, except the :ABORt command, have one or more subcommands
(keywords) associated with them to further define the instrument function to be controlled. The
subcommand keywords may also have one or more associated subcommands (keywords). Each
subcommand level adds another layer to the command tree. The command keyword and its
associated subcommand keywords form a portion of the command tree called a command subsystem.
4.5 Status System Programming
The SERIES 7000 implements the status byte register, the Service Request Enable Register, the
Standard Event Status Register, and the Standard Event Status Enable Register.
The SERIES 7000 status system consists of the following SCPI-defined status reporting structures:
• The Instrument Summary Status Byte
• The Standard Event Status Group
• The Operation Status Group
• The Questionable Status Group
The following paragraphs describe the registers that make up a status group and explain the status
information that each status group provides.
4.6 Status Registers
In general, a status group consists of a condition register, a transition filter, an event register, and an
enable register. Each component is briefly described in the following paragraphs.
Condition Register
The condition register is continuously updated to reflect the current status of the SERIES 7000. There
is no latching or buffering for this register, it is updated in real time. Reading the contents of a
condition register does not change its contents.
Transition Filter
Berkeley Nucleonics Corporation 2955 Kerner Blvd., San Rafael, CA 94901
Phone: 415-453-9955, Fax: 415-453-9956, Email: [email protected], Web: www.berkeleynucleonics.com