Specifications

ManualsBrandsArtisan Technology Group ManualsKitchen AppliancesHP E1368A/69A/70A

Artisan Technology Group is your source for quality

new and certied-used/pre-owned equipment

• FAST SHIPPING AND

DELIVERY

• TENS OF THOUSANDS OF

IN-STOCK ITEMS

• EQUIPMENT DEMOS

• HUNDREDS OF

MANUFACTURERS

SUPPORTED

• LEASING/MONTHLY

RENTALS

• ITAR CERTIFIED

SECURE ASSET SOLUTIONS

SERVICE CENTER REPAIRS

Experienced engineers and technicians on staff

at our full-service, in-house repair center

WE BUY USED EQUIPMENT

Sell your excess, underutilized, and idle used equipment

We also offer credit for buy-backs and trade-ins

www.artisantg.com/WeBuyEquipment

REMOTE INSPECTION

Remotely inspect equipment before purchasing with

our interactive website at www.instraview.com

LOOKING FOR MORE INFORMATION?

Visit us on the web at www.artisantg.com for more

information on price quotations, drivers, technical

specications, manuals, and documentation

View

Instra

Summary of content (285 pages)

PAGE 1
Artisan Technology Group is your source for quality new and certified-used/pre-owned equipment • FAST SHIPPING AND DELIVERY • TENS OF THOUSANDS OF IN-STOCK ITEMS • EQUIPMENT DEMOS • HUNDREDS OF MANUFACTURERS SUPPORTED • LEASING/MONTHLY RENTALS • ITAR CERTIFIED SECURE ASSET SOLUTIONS SERVICE CENTER REPAIRS Experienced engineers and technicians on staff at our full-service, in-house repair center WE BUY USED EQUIPMENT Sell your excess, underutilized, and idle used equipment We also offer credit for buy-back
PAGE 2
Contents HP E1406A Command Module User’s Manual Warranty . . . . . . . . . . WARNINGS . . . . . . . . Safety Symbols . . . . . . Declaration of Conformity . Reader Comment Sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 3
Interrupt Line Allocation . . . . . . . . . . . . . User-Defined Interrupt Line Allocation Table Starting System Operation . . . . . . . . . . . . . VXI SYSFAIL* Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 54 60 60 Chapter 3. Using the Display Terminal Interface . . . . . . . . . . . . . . . . . . . . . . . 61 About This Chapter . . .
PAGE 4
Status System Programming Examples . . Handling SRQs . . . . . . . . . . . . Using Message Available (MAV) Bits Using a Service Request (SRQ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 111 112 114 Chapter 5. HP E1406A Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . 119 About This Chapter . . . . . . . . .
PAGE 5
:RDISk:CREate? . . . . . . . . . . :UPLoad[:MADDress]? . . . . . . . :UPLoad:SADDress? . . . . . . . . OUTPut . . . . . . . . . . . . . . . . . :ECLTrg :IMMediate . . . . . . :ECLTrg:LEVel [:IMMediate] . :ECLTrg:LEVel [:IMMediate]? :ECLTrg:SOURce . . . . . . . :ECLTrg :SOURce? . . . . . . :ECLTrg[:STATe] . . . . . . . :ECLTrg[:STATe]? . . . . . . . :EXTernal:IMMediate . . . . . . . :EXTernal:LEVel [:IMMediate] . . :EXTernal:LEVel [:IMMediate]? . . :EXTernal:SOURce . . . . . . . . .
PAGE 6
SYSTem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . :COMMunicate:GPIB:ADDRess? . . . . . . . . . . . . . . . . . . :COMMunicate :SERial[n]:… . . . . . . . . . . . . . . . . . . . . :COMMunicate :SERial[n]:CONTrol :DTR . . . . . . . . . . . . . :COMMunicate :SERial[n]:CONTrol :DTR? . . . . . . . . . . . . :COMMunicate :SERial[n]:CONTrol :RTS . . . . . . . . . . . . . :COMMunicate :SERial[n]:CONTrol :RTS? . . . . . . . . . . . . . :COMMunicate :SERial[n][:RECeive] :BAUD . . . . . . . .
PAGE 7
:CONFigure :INFormation:ALL? . . . . . . :CONFigure:ITABle . . . . . . . . . . . . . :CONFigure:ITABle? . . . . . . . . . . . . . :CONFigure :LADDress? . . . . . . . . . . . :CONFigure :LADDress :MEXTender? . . . :CONFigure :MEXTender :ECLTrg . . . :CONFigure :MEXTender :INTerrupt . . :CONFigure :MEXTender :TTLTrg . . . :CONFigure:MTABle . . . . . . . . . . . . :CONFigure:MTABle? . . . . . . . . . . . . :CONFigure:NUMBer? . . . . . . . . . . . . :CONFigure:NUMBer :MEXTender? . . . . :QUERy? . . . .
PAGE 8
*OPC? . . . . . . . . . . . . . . . . . . . . . . . . . *PMC . . . . . . . . . . . . . . . . . . . . . . . . . *PSC . . . . . . . . . . . . . . . . . . . . . *PSC? . . . . . . . . . . . . . . . . . . . . . . . . . *RMC . . . . . . . . . . . . . . . . *RST . . . . . . . . . . . . . . . . . . . . . . . . . *SRE . . . . . . . . . . . . . . . . . . . . . *SRE? . . . . . . . . . . . . . . . . . . . . . . . . . *STB? . . . . . . . . . . . . . . . . . . . . . . . . . *TST? . . . . . . .
PAGE 9
Appendix C. HP E1406A Command Module A16 Address Space . . . . . . . . . . . . . . 259 About This Appendix Register Addressing . The Base Address Register Offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259 260 260 260 Appendix D.
PAGE 10
Certification Hewlett-Packard Company certifies that this product met its published specifications at the time of shipment from the factory. HewlettPackard further certifies that its calibration measurements are traceable to the United States National Institute of Standards and Technology (formerly National Bureau of Standards), to the extent allowed by that organization’s calibration facility, and to the calibration facilities of other International Standards Organization members.
PAGE 11
Documentation History All Editions and Updates of this manual and their creation date are listed below. The first Edition of the manual is Edition 1. The Edition number increments by 1 whenever the manual is revised. Updates, which are issued between Editions, contain replacement pages to correct or add additional information to the current Edition of the manual. Whenever a new Edition is created, it will contain all of the Update information for the previous Edition.
PAGE 12
Declaration of Conformity according to ISO/IEC Guide 22 and EN 45014 Manufacturer’s Name: Hewlett-Packard Company Loveland Manufacturing Center Manufacturer’s Address: 815 14th Street S.W. Loveland, Colorado 80537 declares, that the product: Product Name: HP-IB Command Module Model Number: E1406A Product Options: All conforms to the following Product Specifications: Safety: IEC 1010-1 (1990) Incl. Amend 1 (1992)/EN61010-1 (1993) CSA C22.2 #1010.
PAGE 13
Notes 12 HP E1406A User’s Manual Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.
PAGE 14
Please fold and tape for mailing Reader Comment Sheet HP E1406A User’s Manual Edition 4 You can help us improve our manuals by sharing your comments and suggestions. In appreciation of your time, we will enter you in a quarterly drawing for a Hewlett-Packard Palmtop Personal Computer (U.S. government employees cannot participate in the drawing).
PAGE 15
14 HP E1406A User’s Manual Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.
PAGE 16
Chapter 1 HP E1406A Command Module Overview About This Chapter This chapter contains WARNINGS and CAUTIONS, a functional and physical overview of the HP E1406A Command Module, and instructions on installing the command module in a mainframe. Chapter contents are as follows: • • • • • • Warnings and Cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using HP VIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command Module Functional Description . . . . . . . . . .
PAGE 17
Command Module Functional Description The HP E1406A Command Module is the foundation of a VXIbus system (see Figure 1-1). Though its role in a VXIbus system is largely transparent (for example, the user need not program its functions) it provides the following key functions: • Translates SCPI (Standard Commands for Programmable Instruments) commands for HP register-based instruments. • Provides the VXIbus slot 0 and resource manager capabilities.
PAGE 18
Command Module Physical Description The HP E1406A Command Module occupies one C-size mainframe slot. The faceplate has annunciators, clock and trigger connectors, interface ports, and extraction levers that are described below. Faceplate Annunciators There are four annunciators on the HP E1406A faceplate which show the following: Failed Shows that the command module has failed its power-on self-test or has stopped working at some point in time.
PAGE 19
Faceplate CLK10 and Trigger Connectors 18 There are four signal connectors on the HP E1406A faceplate which function as follows: Clk In This SMB connector allows an external 10 MHz clock to function as the system’s slot 0 CLK10 resource. This is a high impedance input with an input range from ± 40 mV to ± 42.5 V. Clk Out This SMB connector allows the internal slot 0 CLK10 resource to be routed to other VXIbus mainframes. This output is a TTL level output and drives 50 Ω.
PAGE 20
Installing the Command Module in a Mainframe Refer to Figure 1-3 to install the HP E1406A Command Module in a C-size mainframe. Set the extraction levers out. Slide the HP E1406A into any slot until the backplane connectors touch. Seat the command module into the mainframe by pushing in the extraction levers. Tighten the top and bottom screws to secure the command module to the mainframe. NOTE: The extraction levers will not seat the backplane connectors on older VXIbus mainframes.
PAGE 21
Command Module Memory The HP E1406A comes from the factory equipped with 512 KB of RAM and 1.25 MB of Flash ROM. HP E1406A Option 010 provides 1.75 MB of Flash ROM and 1 MB of RAM. For applications which do not require shared RAM, the non-volatile RAM can be configured to a full 2 MB if the extra 512 KB of RAM and 512 KB of Flash ROM has been installed.
PAGE 22
Chapter 2 Configuring the HP E1406A Command Module About This Chapter One purpose of the HP E1406A is to provide the resource manager function required by VXIbus systems. This chapter describes the resource manager’s function and shows you how to modify the configuration process with user tables you download into non-volatile user RAM. All of these functions require the Flash ROMS Run/Load switch be set to "Run". The main sections of this chapter include: • • • • • • • • System Configuration Sequence .
PAGE 23
The following sections describe each step of the configuration sequence. Included are examples on how to change the sequence using configuration tables stored in non-volatile user RAM. Note Refer to the C-Size VXIbus Systems Configuration Guide for information on configuring the HP E1406A Command Module as the resource manager. Modules Configured Statically and Dynamically Statically configured modules are plug-in modules whose logical addresses are set with logical address switches.
PAGE 24
User-Defined Dynamic Configuration If your system contains instruments comprised of multiple modules that must have successive logical addresses, then the modules must be statically configured using their logical address switches, or be dynamically configured with the user-defined dynamic configuration table. The dynamic configuration table covered in this section allows you to override the default configuration process by assigning logical addresses as you choose.
PAGE 25
• Slot Number (1 - 12) is the mainframe slot the module to be assigned an address is installed in. Field is one byte. • Slot 0 Laddr is the logical address of the slot 0 device. This is 0 (zero) in mainframe #1 but will be different in any additional mainframes. Field is one byte. • Laddr (1 - 254) is the logical address to which the module in Slot Number is set. Field is one byte. • Block Size (1 - 128) is the number of devices in an address block.
PAGE 26
Example: Dynamically Configuring a Module The following program dynamically sets the logical address of the HP E1412A 61⁄2-Digit Multimeter in slot 6 to 32. The program notes each of the steps used to create and load the table. To dynamically configure the multimeter, its logical address must be set to 255 using the logical address switches. Chapter 2 10 20 !Assign an I/O path and allocate a variable to store dynamic configuration !data to be downloaded to the command module.
PAGE 27
Comments • Errors associated with dynamic configurations are: ERROR 1: FAILED DEVICE This error occurs when a dynamically configured device at logical address 255 failed during its power-on sequence. ERROR 4: DC DEVICE ADDRESS BLOCK TOO BIG This error occurs when the block size specified in the table is greater than 127. ERROR 7: DC DEVICE MOVE FAILED This error occurs when a dynamically configured device was not set to the logical address specified, possibly due to a hardware failure on the module.
PAGE 28
Setting VXI-MXI Configuration During configuration, if an MXI extender device is present the resource manager will attempt to assign logical addresses and memory according to the rules listed below. You can override these rules by creating a user-defined extender table. This table will be ignored if there are no MXI extender devices present. Logical Address Configuration The following rules and recommendations apply to assigning logical addresses.
PAGE 29
Default Logical Address Assignments The resource manager will attempt to assign logical addresses to dynamically configured devices according to the following rules: • The window for a local extender will be set outward to the minimum possible size to include all of the logical addresses found on all of its descendant busses. This includes all stand alone devices and all remote extenders that are descendants of the local extender.
PAGE 30
A16/A24/A32 Address Window Configuration The following rules and recommendations apply to assigning A16/A24/A32 logical addresses. Refer to the HP E1482B VXI-MXI Bus Extender User’s Manual for a more detailed discussion of how to assign logical addresses. • Systems with multiple VMEbus devices should be configured so that the VMEbus devices in mainframes whose remote extenders have the highest logical addresses should also have the highest logical addresses.
PAGE 31
• VMEbus reserved memory must be placed in locations that will not interfere with windows previously configured. The only way the resource manager can know the location(s) of VMEbus memory is for you to provide this information in the user-defined memory table (see “ A24/A32 Address Mapping” on page 44 for more details).
PAGE 32
Utility Register Configuration The default Utility Register configuration is shown in Table 2-2. Since the resource manager may have to reboot during the system configuration process (for example, to download a driver) the Utility Register is not a part of the extender table. This will help ensure that the SYSRESET signal will propagate throughout the system during a reboot so that all of the cards will receive a hard reset.
PAGE 33
Table Format The user-defined extender table consists of a two byte header followed by the required number of extender records. The first byte of the header is a table Valid Flag (1 = valid) and the second byte specifies the number of records in the table. Table 2-3.
PAGE 34
Determining the Table Size The user-defined extender table has a one word header and each of the 12 fields is also one word. The amount of RAM allocated with DIAGnostic:NRAM:CREate is specified in bytes. Since one word is two bytes, the amount of RAM to allocate is computed as: 2 + 24(N) where N is the number of modules to be configured.
PAGE 35
Example: User-Defined Extender Table This example shows a single interconnect bus with a local extender at logical address 63 in the root mainframe and a remote extender at logical address 64 in the secondary mainframe.
PAGE 36
Chapter 2 10 20 !Assign an I/O path and allocate a variable to store MXI configuration !data to be downloaded to the command module. 30 ASSIGN @E1406 TO 70900;EOL CHR$(10) END 40 INTEGER MXI_config(1:25) 50 60 70 ! !Allocate a segment of non-volatile user RAM on the command !module to store the user-defined MXI table (1 module). 80 OUTPUT @E1406;"DIAG:NRAM:CRE 50" 90 100 110 ! !Restart the system instrument to allocate the user RAM. Wait for the !restart to complete before continuing.
PAGE 37
Comments • The following errors are associated with the extender table or indicate that you may need to create an extender table: ERROR 50: EXTENDER NOT SLOT 0 DEVICE This error occurs when a remote VXIbus extender in a remote mainframe is not in slot 0 of its mainframe. The resource manager expects all remote VXIbus extenders to be installed in slot 0 of their mainframe.
PAGE 38
ERROR 57: INVALID UDEF LADD WINDOW This error occurs when a user-defined logical address window violates the VXI-6 Specification (has an invalid base or size). You should redefine your extender table with correct values. ERROR 58: INVALID UDEF A16 WINDOW This error occurs when a user-defined A16 window violates the VXI-6 Specification (has an invalid base or size). You should redefine your extender table with correct values.
PAGE 39
Setting Commander/Servant Hierarchies In a VXIbus system, a commander is a plug-in module which controls other plug-in modules. “ Control” can be a commander such as the HP E1406A Command Module translating SCPI commands, and/or serving as the HP-IB interface for (servant) modules within its servant area. During the configuration sequence, the resource manager assigns servant modules to a commander module based on the servants’ logical addresses and the commander’s servant area.
PAGE 40
User-Defined Commander/Servant Hierarchies Note The User-Defined Commander/Servant Hierarchy Table In some systems you may need to assign a servant to a commander that is outside the commander’s servant area. In other systems, it may be necessary to change a module’s secondary HP-IB address, or assign secondary addresses to modules whose logical addresses are not instrument identifiers. These tasks can be accomplished with the user-defined commander/servant hierarchy table described in this section.
PAGE 41
Table Format The format of the commander/servant hierarchy table is shown in Table 2-5. Table 2-5. Commander/Servant Hierarchy Table Format Valid Flag/ Number of Modules Laddr Cmdr Laddr Sec Addr Laddr Cmdr Laddr Sec Addr • • • Laddr Cmdr Laddr Sec Addr The table parameters are: • Valid Flag (1/0) 1 indicates the table is valid and the modules should be configured accordingly. 0 (zero) will cause an error message (Error 38).
PAGE 42
Data Format Data can be sent to the commander/servant hierarchy table in any convenient format, as long as the binary data is preserved. This can be accomplished using DIAGnostic:PEEK? and DIAGnostic:POKE, by reading the data into a variable in the computer and then downloading the data to the table using the Arbitrary Block Program Data format, and so forth.
PAGE 43
Example: Assigning a Secondary HP-IB Address 42 The following program assigns secondary HP-IB address 01 to the HP E1411B 51⁄2-Digit Multimeter at logical address 25. The program notes each of the steps used to create and load the table. 10 20 !Assign an I/O path and allocate a variable to store commander/servant !hierarchy data to be downloaded to the command module.
PAGE 44
Comments • The following errors are associated with the commander/servant hierarchy table: ERROR 12: INVALID UDEF COMMANDER LADD This error occurs when the user-defined commander logical address specified in the table (Cmdr Laddr) is not a valid commander. Either the commander does not exist, or it is not a message-based device. ERROR 14: INVALID UDEF SECONDARY ADDRESS This error occurs when the user-defined secondary address (Sec Addr) is invalid in the commander/servant hierarchy table.
PAGE 45
A24/A32 Address Mapping During the configuration sequence, the resource manager reads each VXIbus device’s ID Register to determine if the device requires a block of A24 or A32 addresses. Figure 2-2 shows the address mapping concept. Figure 2-2. A24/A32 Address Mapping Concept A24/A32 Address Allocation The resource manager allocates A24 and A32 addresses as follows: • The top and bottom 2 MB of A24 addresses are used by the command module for its own RAM and ROM.
PAGE 46
• A24 address space is 16 MB and A32 address space is 4 GB. The command module does not have A32 address lines and cannot access A32 address space. However, it will allocate A32 address space for devices which can access it. A32 memory allocation is similar to A24 memory allocation. • A32 address space is 0000000016 through FFFFFFFF16. Allocating Address Space for VMEbus Devices The resource manager (command module) has no way to determine when VMEbus devices have been installed in the system.
PAGE 47
Sequence Display 1 Testing ROM Testing 512 KB RAM Passed Testing CPU CPU Self Test Passed Non-volatile Ram Contents Lost HP-IB address: 09 Talk/Listen command module ladd = 0 command module servant area = 255 Explanation The HP E1406A operating system performs a series of self-tests and clears its volatile RAM. The command module’s HP-IB address, logical address, and servant area (based on the switch settings) are reported.
PAGE 48
Sequence Display Explanation 1 Testing ROM Testing 512 KB RAM Passed Testing CPU CPU Self Test Passed Non-volatile Ram Contents Lost HP-IB address: 09 Talk/Listen command module ladd = 0 command module servant area = 255 The HP E1406A operating system performs a series of self-tests and clears its volatile RAM. The command module’s HP-IB address, logical address, and servant area (based on the switch settings) are reported.
PAGE 49
Reserving A24/A32 Address Space As previously mentioned, the resource manager cannot determine when VME devices have been installed in the system. To prevent the resource manager from allocating A24/A32 addresses intended for VME devices to VXIbus devices, the address allocation table is used. The A24/A32 address allocation table is also used to assign different addresses to VXIbus devices other than those (default) addresses assigned by the resource manager during power-on.
PAGE 50
The table parameters are: • Valid Flag (0/1) 1 (one) indicates the table is valid and the addresses reserved accordingly. 0 (zero) will cause an error message (Error 43). Valid Flag is part of the table header and is represented by the upper eight bits of the header word. • Number of Records is the number of address records in the table. You must have one record for each VMEbus or VXIbus device for which memory is reserved.
PAGE 51
Data Format The Table Header CAUTION 50 Data can be sent to the A24/A32 address allocation table in any convenient format, as long as the binary data is preserved. This can be accomplished using DIAGnostic:PEEK? and DIAGnostic:POKE, by reading the data into a variable in the computer and then downloading the data to the table using the Arbitrary Block Program Data format, and so forth.
PAGE 52
Example: Reserving A24 Addresses for a VMEbus Device The following program reserves a block of A24 addresses for a VMEbus device. The program assumes the device has been configured with a starting A24 address of 30000016 and a size of 8000016. Again, this procedure is used when you want to reserve a specific block of A24/A32 addresses for a VMEbus device, or when you want to assign addresses to a VXIbus device that are different from those assigned by the resource manager.
PAGE 53
Comments • To download the base address and memory size (line 270) they must each be specified as two 16-bit words (line 250).
PAGE 54
ERROR 44: INVALID UDEF MEM TABLE DATA This error occurs when an invalid logical address is specified in the A24/A32 address allocation table. • The A24/A32 addresses reserved by the A24/A32 address allocation table are reserved within the system until DIAGnostic:BOOT:COLD or VXI:CONFigure:MTABle 0 is executed. Interrupt Line Allocation In a VXIbus system, communication and coordination between a commander module and its servant module(s) is often achieved using the VXIbus backplane interrupt lines.
PAGE 55
Note the following regarding interrupt line allocation: • There are seven VXIbus backplane interrupt lines. As the resource manager, the HP E1406A Command Module assigns itself interrupt line 1 (default). Additional interrupt lines (up to all seven) can be assigned to the command module using the interrupt line allocation table. Interrupt lines not assigned to programmable handlers remain unassigned. • Many Hewlett-Packard modules have interrupt line 1 as their factory setting.
PAGE 56
Table Format The format of the interrupt line table is shown in Table 2-7. Table 2-7. Interrupt Line Allocation Table Format Table Format Data Record Format Valid Flag/ Number of Records Intr Line Data Record #1 Handler Laddr Data Record #2 Number of Interrupters • Intr #1 Laddr • Intr #2 Laddr Data Record #7 Intr M Laddr The table parameters are: • Valid Flag (1/0) 1 (one) indicates the table is valid and the modules should be configured accordingly.
PAGE 57
Determining the Table Size The interrupt line allocation table has a one word header and each data record contains three words, plus one word for each programmable interrupter logical address specified. The amount of RAM allocated with DIAGnostic:NRAM:CREate is specified in bytes.
PAGE 58
The table header is sent as a single 16-bit word which must contain the Valid Flag and the number of data records. For a valid table, the header is 256 plus the number of data records. For example, to indicate a valid table with one data record, the header is 257 (256 + 1 = 257). CAUTION Example: Assigning an Interrupt Line When downloading data into the interrupt line allocation table, DIAGnostic:DOWNload does not determine if the table is large enough to store the data.
PAGE 59
Comments 10 20 !Assign an I/O path and allocate a variable to store interrupt line !data to be downloaded to the command module. 30 ASSIGN @E1406 TO 70900;EOL 40 INTEGER Intr_line(1:7) 50 60 70 ! !Allocate a segment of non-volatile user RAM on the command module !to store the interrupt line table (2 data records, no interrupters). 80 OUTPUT @E1406;"DIAG:NRAM:CRE 14" CHR$(10) END 90 100 110 ! !Restart the system instrument to define the user RAM.
PAGE 60
• In this program, the command module at logical address 64 has a primary HP-IB address of 08. It has a servant pointer setting of 32, thus its servant area is from logical address 65 to logical address 96. If the HP E1411B multimeter has a logical address of 80, its secondary HP-IB address is 10. Thus, when programming this multimeter, its HP-IB address is: OUTPUT 70810;".... When programming this command module, its HP-IB address is: OUTPUT 70800;"...
PAGE 61
Starting System Operation The resource manager completes the configuration sequence by issuing the "Begin Normal Operation" (BNO) command to all top level commanders and to each of its direct message based servants. BNO is not sent to register based modules. The module receiving BNO responds by writing its status to the Data Low Register which is read by the resource manager. More information on BNO and on the Data Low Register can be found in the VXIbus System Specification.
PAGE 62
Chapter 3 Using the Display Terminal Interface About This Chapter This chapter shows you how to use the HP E1406A Command Module’s display terminal interface to operate instruments in a C-Size mainframe when the Flash ROMS Run/Load switch is set to its "Run" position. The instruments (including the System instrument) are disabled when the Flash ROMS Run/Load switch is in the "Load" position.
PAGE 63
Terminal Interface Features Figure 3-1 shows a typical terminal interface display with its function labels across the bottom of the screen. The first five function keys (f1 through f5) select instrument menu choices. Function keys f6 through f8 provide menu control and access to utility functions. The tutorials in this chapter show how to use most of the menu control and utility function keys. See “ General Key Descriptions” on page 77 for a complete description of each of these key functions.
PAGE 64
When you select an instrument, you are assigning the terminal interface to that instrument. This means that any menu operations, commands executed or recalled, errors displayed, and so forth pertain only to that instrument. Terminal interface operation of an instrument is independent from other instruments and independent from the remote operation of the instrument. To operate another instrument from the terminal interface, you must select that instrument.
PAGE 65
Display Terminal Menu Tutorial Following the power-on sequence or a system reset, the screen shows the Select an instrument menu (see Figure 3-2). This menu allows you to select one of the instruments listed. Note: Typical instruments are shown. Actual choices depend on installed instruments. Figure 3-2. "Select an Instrument" Menu Figure 3-2 shows the Select an Instrument menu when the Flash ROMS Run/Load switch on the front of the HP E1406A Command Module is set to "Run".
PAGE 66
• In addition to the instrument menu keys, CLR_INST, RST_INST and SEL_INST are helpful when operating instruments. These and other utility keys are accessed by pressing the UTILS key (see Figure 3-3). Refer to “ General Key Descriptions” on page 77 for information on the RCL_.... keys in this menu. – CLR_INST clears the instrument’s terminal interface input and output buffers (remote buffers are not cleared) and returns to the top level of the instrument menu.
PAGE 67
Typical HP-IB address: +9 SCPI command used: SYST:COMM:GPIB:ADDR? Figure 3-4. Reading the Command Module HP-IB Address 66 Using the Display Terminal Interface Chapter 3 Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.
PAGE 68
For information on a single instrument, enter its logical address and press RETURN. For information on all instruments, enter a single space and press RETURN. (in this case, 8 was entered) Logical address of selected device Instrument name HP-IB secondary address Note: See page 189 for a description of each field of instrument information. Figure 3-5.
PAGE 69
Note: Configuration of the HP E1406A RS-232 port is covered in the C-Size VXIbus Systems Configuration Guide. Figure 3-6. Configuring the Command Module RS-232 Port 68 Using the Display Terminal Interface Chapter 3 Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.
PAGE 70
SCPI command used: VXI:REC SCPI command used: VXI:SEND , ""[,] Figure 3-7. Programming Message-Based Devices Chapter 3 Using the Display Terminal Interface Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.
PAGE 71
SCPI command used: SYST:TIME , , SCPI command used: SYST:DATE , , Figure 3-8. Setting the System Clock and Calendar 70 Using the Display Terminal Interface Chapter 3 Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.
PAGE 72
Note: The RESET selection in this menu is equivalent to executing DIAG:BOOT, which has the same effect as cycling the mainframe power. Pressing RST_INST from the System instrument menu is equivalent to sending the *RST command to the System instrument. Figure 3-9. Resetting the System Chapter 3 Using the Display Terminal Interface Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.
PAGE 73
Using the Loader Instrument The Loader instrument appears on the Select an instrument menu when the Flash ROMS Run/Load switch on the front of the HP E1406A Command Module is set to "Load".
PAGE 74
Switchbox instrument at logical address 32 (secondary address is 04) SCPI command used: OPEN SCPI command used: CLOSE Enter channel number and press RETURN (for example, 102 for channel #2 on card #1) Figure 3-10. Opening and Closing Channels Press f2 to advance to the next channel in the scan list (that is, to trigger the instrument) Enter channel list and press RETURN (for example, 100:115 to scan channels 00 to 15 on card #1) Figure 3-11.
PAGE 75
Enter card number and press RETURN Enter card number and press RETURN SCPI command used: SYST:CPON SCPI command used: SYST:CTYP Enter card number and press RETURN SCPI command used: SYST:CDES Figure 3-12. Displaying Card Type and Description or Resetting Card 74 Using the Display Terminal Interface Chapter 3 Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.
PAGE 76
Monitor Mode Note Monitor mode displays the status of an instrument while it is being controlled from remote. Monitor mode is useful for debugging programs. You can place an instrument in monitor mode using terminal interface menus, or by executing the DISP:MON:STAT ON command from the terminal interface or by remote. Pressing most terminal interface keys will automatically exit monitor mode and return to the instrument menu.
PAGE 77
Table 3-1 shows the status annunciators that may appear in the bottom line of the screen in monitor mode. Some instruments also have device-specific annunciators (see your specific module user’s manual for more information). Table 3-1. Monitor Mode Display Annunciators Annunciator Reading Error Messages Description mon The instrument is in monitor mode. busy The instrument is executing a command. err An error has occurred (see “Reading Error Messages” below). srq A service request has occurred.
PAGE 78
Editing the Terminal Display Note The screen editing keys (shown on page 78) allow you to edit user-entered data or commands. When editing, the screen is in insert mode. That is, typed characters will be inserted into the string at the present cursor position. The key labels shown are found on all HP terminals (except HP terminals supporting ANSI terminal protocol). See “ Using Supported Terminals” on page 79 for equivalent key functions on your terminal.
PAGE 79
RCL_MENU Recalls the last SCPI command generated by a menu operation. For example, reading the time using the menus (SYSTEM, TIME, READ) generates and executes the SYST:TIME? SCPI command. A recalled command can be executed by pressing the Return key. You can edit a recalled command before you execute it. Instrument Control Keys RST_INST CLR_INST Resets only the selected instrument (equivalent of executing *RST).
PAGE 80
Using Supported Terminals The display terminal interface supports several popular terminal brands and models. This chapter will show you how to access all of the terminal interface functions described previously using your supported terminal. The Supported Terminals The following list names the supported terminals and shows where to go for more information. If your terminal is not named in this list, see “ Using Other Terminals” on page 82.
PAGE 81
Selecting VT100 Mode VT220 Key Map Note To use the HP 700/22 in VT100 mode, press the Set-Up key and set the following configuration: Fields Value Terminal Mode EM100, 7 bit Ctrls Columns 80 EM100 ID EM100 Inhibit Auto Wrap YES The function keys that are normally labeled f6 through f14 are now labeled: Because the HP 700/22 keyboard has nine function keys in the center of the keyboard, f4 is mapped twice.
PAGE 82
Selecting VT220 Mode Using the WYSE WY-30 To use the HP 700/22 in VT220 mode, press the Set-Up key and set the following configuration: Fields Value Terminal Mode EM200, 7 bit Ctrls Columns 80 EM100 ID EM220 Inhibit Auto Wrap YES With the WYSE WY-30 terminal, some functions of the display terminal interface have been assigned to keys with other labels. Use this keyboard map to help locate these functions.
PAGE 83
Using Other Terminals This section discusses using terminals which are not on the Supported Terminals list. Primarily this section is to help you use terminals which do not provide programmable soft keys (function keys). Without this capability, a terminal cannot access the display terminal interface’s menus. Instead, the terminal interface provides a set of terminal interface commands which allow you to select instruments by name or logical address.
PAGE 84
4. If you see only the Select an instrument prompt without the Select an instrument menu labels, your terminal did not return a recognized ID.
PAGE 85
Table 3-2.
PAGE 86
Control Sequences for Terminal Interface Functions The terminal interface provides the keyboard control sequences listed in Table 3-3. These can be thought of as keyboard short-cuts for compatible terminals (those which provide menu capability). Only those functions in the table marked with * (asterisk) operate for “ UNKNOWN” terminal types (those which do not support menus). An “ UNKNOWN” terminal type has very limited editing capability.
PAGE 87
In Case of Difficulty Problem: Error -113 undefined header error occurs after entering data in response to a menu prompt. Problem Cause/Solution: For some commands used by the menus, the data entered is appended to a command header. For example, if you enter "1" as the port number for a digital I/O module, the command used is DIG:HAND1:MODE NONE where HAND1 indicates the port number. If your entry was invalid or incorrect, error -113 occurs.
PAGE 88
System Instrument/Switchbox Menus This section contains charts showing the structure and content for the HP E1406A Command Module’s System instrument and switchbox terminal interface instrument menus. The SCPI commands used and descriptions of menu-controlled instrument operations are also included in the charts. You may want to refer to these charts as examples for other instrument menus. See the appropriate instrument user’s manual for menus specific to that instrument.
PAGE 89
System Instrument Menu Menu Levels and Content Level 1 SYSTEM Level 2 CONFIG? Level 3 Level 4 Level 5 Level 6 User Entry LADDS Displays logical addresses of mainframe instruments. VXI:CONF:DLIS? Displays information about the device at the specified logical address. (Refer to the Command Reference for details). SYST:COMM:GPIB:ADDR? Displays HP-IB address. card number SYST:COMM:SER[ n]:BAUD? Read current baud rate.
PAGE 90
System Instrument Menu Menu Levels and Content Level 1 Level 2 Level 3 Level 4 Level 5 Level 6 User Entry Command(s) Used Description (Continued from previous page) CONTROL DTR SET RTS DEBUG SYST:COMM:SER[ n]:CONT:DTR? Read current setting for DTR line. ON card number SYST:COMM:SER[n]:CONT:DTR ON Set DTR line to static +V. OFF card number SYST:COMM:SER[n]:CONT:DTR OFF Set DTR line to static -V. IBFULL card number SYST:COMM:SER[n]:CONT:DTR IBF Set DTR for hardware handshaking.
PAGE 91
System Instrument Menu Menu Levels and Content Level 1 Level 2 Level 3 Level 4 Level 5 Level 6 User Entry Command(s) Used Description (Continued from previous page) TIME READ SET DATE READ SET RESET time date SYST:TIME? Read the current system clock. SYST:TIME Set the system clock. SYST:DATE? Read the current system calendar. SYST:DATE Set the system calendar. DIAG:BOOT Resets mainframe using the configuration stored in non-volatile memory.
PAGE 92
Switchbox Menu Menu Levels and Content Level 1 SWITCH Level 2 Level 3 MONITOR User Entry card number ‡ or AUTO Command(s) Used Description DISP:MON:CARD ;STAT ON Monitor instrument operations. OPEN channel list † OPEN (@channel_list) Open channel(s). CLOSE channel list † CLOS (@channel_list) Close channel(s). channel list † TRIG:SOUR HOLD;:SCAN ;:INIT Set up channels to scan. SCAN SET_UP STEP channel list † TRIG Step to next channel in scan list.
PAGE 93
Scanning Voltmeter Menu Menu Levels and Content Level 1 VOLTMTR Level 2 Level 3 Level 4 User Entry Command(s) Used Description MONITOR channel list † or 0 for auto DISP:MON:CHAN ;STAT ON Monitor instrument operations. VDC channel list † MEAS:VOLT:DC? Measure DC voltage on each channel. VAC channel list † MEAS:VOLT:AC? Measure AC voltage on each channel.
PAGE 94
Scanning Voltmeter Menu Menu Levels and Content Level 1 Level 2 Level 3 Level 4 User Entry Command(s) Used Description (Continued from previous page) UNSTRN DIAG CARD TEST channel list † MEAS:STR:UNST? Measure bridge unstrained. COMPRES channel list † MEAS:STR:QCOM? Compression shunt diagnostic. TENSION channel list † MEAS:STR:QTEN? Tension shunt diagnostic. TYPE? card number ‡ SYST:CTYP? Displays module ID information.
PAGE 95
HP E1326B/E1411B 51⁄2-Digit Multimeter (Stand-Alone) Menu Menu Levels and Content Level 1 Level 2 VOLTMTR MONITOR DISP:MON:STAT ON Display instrument operations. VDC MEAS:VOLT:DC? Measure DC volts. VAC MEAS:VOLT:AC? Measure AC volts. OHM MEAS:FRES? Measure 4-wire ohms. TEMP Level 3 THERMIS RTD TEST Level 4 User Entry Command(s) Used Description 2252 MEAS:TEMP? FTH,2252 Measure °C of 2252Ω thermistor (4-wire measurement).
PAGE 96
HP E1328A 4-Channel D/A Converter Menu Menu Levels and Content Level 1 D/A Level 2 MONITOR Level 3 Level 4 User Entry Description CHAN1 DISP:MON:CHAN 1;STAT ON Monitor instrument operations on channel 1. CHAN2 DISP:MON:CHAN 2;STAT ON Monitor instrument operations on channel 2. CHAN3 DISP:MON:CHAN 3;STAT ON Monitor instrument operations on channel 3. CHAN4 DISP:MON:CHAN 4;STAT ON Monitor instrument operations on channel 4.
PAGE 97
HP E1330A/B Quad 8-Bit Digital Input/Output Menu Menu Levels and Content Level 1 DIG_I/O Level 2 MONITOR READ Level 3 User Entry Command(s) Used Description PORT0 DISP:MON:CHAN 0;STAT ON Monitor instrument operations on port 0. PORT1 DISP:MON:CHAN 1;STAT ON Monitor instrument operations on port 1. PORT2 DISP:MON:CHAN 2;STAT ON Monitor instrument operations on port 2. PORT3 DISP:MON:CHAN 3;STAT ON Monitor instrument operations on port 3.
PAGE 98
HP E1332A 4-Channel Counter/Totalizer Menu Menu Levels and Content Level 1 COUNTER Level 2 MONITOR Level 3 Level 4 Level 5 User Entry DISP:MON:CHAN 1;STAT ON Monitor instrument operations on channel 1. CHAN2 DISP:MON:CHAN 2;STAT ON Monitor instrument operations on channel 2. CHAN3 DISP:MON:CHAN 3;STAT ON Monitor instrument operations on channel 3. CHAN4 DISP:MON:CHAN 4;STAT ON Monitor instrument operations on channel 4.
PAGE 99
HP E1332A 4-Channel Counter/Totalizer Menu Menu Levels and Content Level 1 Level 2 Level 3 Level 4 Level 5 User Entry Command(s) Used Description (Continued from previous page) TIMEINT POS_PW NEG_PW UDCOUNT CHAN1 TRIG:SOUR IMM;:MEAS1:TINT? Time interval measurement on channel 1. CHAN3 TRIG:SOUR IMM;:MEAS3:TINT? Time interval measurement on channel 3. CHAN2 TRIG:SOUR IMM;:MEAS2:PWID? Positive pulse width measurement on channel 2.
PAGE 100
HP E1333A 3-Channel Universal Counter Menu Menu Levels and Content Level 1 Level 2 COUNTER MONITOR INPUT Level 3 Level 4 Command(s) Used Description DISP:MON:CHAN 1;STAT ON Monitor instrument operations on channel 1. CHAN2 DISP:MON:CHAN 2;STAT ON Monitor instrument operations on channel 2. CHAN3 DISP:MON:CHAN 3;STAT ON Monitor instrument operation on channel 3. AUTO DISP:MON:CHAN AUTO;STAT ON Monitor instrument operations on active channel.
PAGE 101
HP E1333A 3-Channel Universal Counter Menu Menu Levels and Content Level 1 Level 2 Level 3 Level 4 Level 5 User Entry Command(s) Used Description (Continued from previous page) TIMEINT POS_PW NEG_PW RATIO TOTALIZ CHAN1 TRIG:SOUR IMM;:MEAS1:TINT? Time interval measurement on channel 1. CHAN2 TRIG:SOUR IMM;:MEAS2:TINT? Time interval measurement on channel 2. CHAN1 TRIG:SOUR IMM;:MEAS1:PWID? Positive pulse width measurement on channel 1.
PAGE 102
Chapter 4 Triggering and System Status About This Chapter This chapter covers the use of the ECLTRG and TTLTRG* VXI backplane trigger lines and the HP E1406A Command Module’s Trig In and Trig Out ports. Also covered is the structure of the status system used by Hewlett-Packard VXI instruments. The main sections of this chapter include: • Using VXI Backplane Trigger Lines and Ports. . . . . . . . . . . Page 101 • Programming the Status System . . . . . . . . . . . . . . . . . . . . . .
PAGE 103
Programming the Trigger Lines and the Trigger Ports Note The programming sequence used to set up the trigger lines and trigger ports is shown in Figure 4-2. Detailed information on the commands used can be found in Chapter 5 of this manual. In the following commands, is 0 or 1 when selecting a ECLTRG trigger line, and 0 to 7 when selecting a TTLTRG* trigger line. Commands in square brackets ([ ]) are implied commands and are, therefore, optional.
PAGE 104
Setting the Trigger Source Once the trigger line or the Trig Out port has been enabled, the source which drives the trigger line can be specified. The commands used are: OUTPut:ECLTrg:SOURce INT | EXT | NONE Selects ECL trigger source. OUTPut:TTLTrg:SOURce INT | EXT | NONE Selects TTL trigger source. OUTPut:EXTernal:SOURce INT | ECLTrg | TTLTrg | NONE Selects Trig Out port source. When the trigger source is INT, the trigger level is set using the OUTPut...
PAGE 105
Programming the Status System This section discusses the structure of the Standard Commands for Programmable Instruments (SCPI) STATus system and how to program the Status Registers. An important feature of SCPI instruments is that they all implement Status Registers in the same way. The status system is explained in the following sections: • General Status Register Model This section explains how Status Registers are structured in SCPI instruments.
PAGE 106
Transition Filter The Transition Filter specifies which types of bit state changes in the Condition Register will set corresponding bits in the Event Register. Transition Filter bits may be set for positive transitions (PTR), negative transitions (NTR), or both. Positive means a condition bit changes from 0 to 1. Negative means a condition bit changes from 1 to 0. Transition Filters are read-write, and are unaffected by *CLS (clear status) or queries.
PAGE 107
Required Status Groups All SCPI instruments must implement a minimum set of status groups. Some instruments contain additional status groups, consistent with the general status register model. The minimum required status system is shown in Figure 4-5. Figure 4-5. Minimum Required Status Register System The Standard Operation Status and Questionable Data Groups are 16-bits wide, while Status Byte and Standard Event Groups are only 8-bits wide.
PAGE 108
Status Byte Group As Figure 4-6 indicates, the Status Byte is used to summarize information from all the other status groups. The Status Byte differs from the other groups in the way you read it and how its summary bit is processed. Figure 4-6. Status Byte Register The Status Byte can be read using either the *STB? common command or by doing a SICL ireadstb function call. The ireadstb function reads the Status Byte from the device specified.
PAGE 109
The meaning of each bit in the Status Byte is explained in the following table. Table 4-1.
PAGE 110
Standard Operation Status Group The Standard Operation Status Group provides information about the state of the measurement systems in an instrument. This status group is accessed through the STATus subsystem. Standard Operation Status includes a Condition Register, Event Register, and an Enable Register. As a beginner, you will rarely need to use this group. Figure 4-8 illustrates the structure of Standard Operation Status. Figure 4-8.
PAGE 111
Questionable Data Group The Questionable Data Status Group provides information about the quality of instrument output and measurement data. Questionable Data is accessed through the STATus subsystem. As a beginner, you will rarely need to use this status group. Figure 4-9 illustrates the structure of Questionable Data. Figure 4-9. Questionable Data Status Group 110 Triggering and System Status Chapter 4 Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.
PAGE 112
Status System Programming Examples This section contains two example programs that use the status system and common commands to monitor when data is available from an instrument and when an error has occurred. Both programming examples are written in C and use the Standard Instrument Control Library (SICL) for I/O operations. The example programs use SCPI (Standard Commands for Programmable Instruments) commands to communicate with the status system.
PAGE 113
Using Message Available (MAV) Bits Message Available (MAV) bits can be used to determine when data is available. The following example program sets up an SRQ handler to be called when there is data in the output queue. The program then prompts for SCPI commands. If the SCPI command results in data in the output queue (such as a query command), then the SRQ handler is called and the data is printed.
PAGE 114
/* message is available so read in the result. */ iscanf( id, "%t", buf); printf("%s", buf); } } void main(){ INST id; char addr[80]; char cmd[255]; int opc; int idx; printf("This program provides an interactive environment for SCPI \n"); printf("compatible instruments. \n\n"); printf("Enter the SICL address of the instrument to open.
PAGE 115
break; } }/* while - there are commands to send */ /* remove the handler */ ionsrq( id, 0); /* close the session */ printf("\nClosing Instrument at %s\n", addr); iclose(id); } Using a Service Request (SRQ) A Service Request (SRQ) can be used to detect errors. The following example program sets up an SRQ handler to be called when SCPI errors are detected using the Standard Event Status Register. The program then prompts for SCPI commands.
PAGE 116
Example Program /* The following program provides an interactive command line interface */ /* to send SCPI commands to SCPI compatible instruments. */ /* This utilizes the MAV bit of the Status Byte in order to determine if */ /* the instrument is returning any output. It also automatically */ /* displays any error conditions that may result by querying the Standard */ /* Event Status Register. */ #include #include
PAGE 117
/* an error occurred, read the error queue to get the error */ errnum = -1; while( errnum != 0) { ipromptf( id, "SYST:ERR?\n", "%d,%t", &errnum, errmsg); if( errnum != 0) printf("%d,%s", errnum, errmsg); } } } } void main() { INST id; char addr[80]; char cmd[255]; int opc; int idx; printf("This program provides an interactive environment for SCPI \n"); printf("compatible instruments. \n\n"); printf("Enter the SICL address of the instrument to open.
PAGE 118
/* send command */ iprintf(id, "%s\n", cmd); /* check cmd for a ’?’, if found assume it is a query */ for(idx=0; idx
PAGE 119
Notes 118 Triggering and System Status Chapter 4 Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.
PAGE 120
Chapter 5 HP E1406A Command Reference About This Chapter This chapter describes the Standard Commands for Programmable Instruments (SCPI) command set and the IEEE 488.2 Common Commands for the System instrument and the Loader instrument. The System instrument is part of the HP E1406A Command Module’s internal control processor and is, therefore, always present in the command module.
PAGE 121
The following example shows part of a typical subsystem: [ROUTe:] CLOSe SCAN MODE? [ROUTe:] is the root command, CLOSe and SCAN are second level commands with parameters, and :MODE? is a third level command. [ROUTe:] is also an implied command and is, therefore, optional.
PAGE 122
Variable Command Syntax Some commands have what appears to be a variable syntax. For example: DIAG:INT:SETup[n]? and SYST:COMM:SERial[n]:BAUD? In these commands, the "n" is replaced by a number. No space is left between the command and the number because the number is not a parameter. The number is part of the command syntax. The purpose of this notation is to save a great deal of space in the command reference. In the case of …SETup[n], [n] could range from 1 through 7.
PAGE 123
The “Comments” section within the Command Reference will state whether a numeric parameter can also be specified in hex (#H7B), octal (#Q173), and/or binary (#B1111011). • Optional Parameters are parameters shown within square brackets ([ ]), and are optional. (Note that the brackets are not part of the command, and are not sent to the instrument.) If you do not specify a value for an optional parameter, the instrument chooses a default value. For example, consider the ARM:COUNt? [] command.
PAGE 124
DIAGnostic The DIAGnostic subsystem allows control over the System instrument’s internal processor system (:BOOT and :INTerrupt), access to the Loader instrument, allocation and contents of user RAM and disc volume RAM (:NRAM and :RDISk), and allocation of the built-in serial interface (DIAG:COMM:SER[0]:OWN).
PAGE 125
:RDISk :ADDRess? :CREate | MIN | MAX :CREate? [MIN | MAX] :UPLoad [:MADDress]?
, SADDress?
, :BOOT:COLD DIAGnostic:BOOT:COLD causes the System instrument to restart (reboot). Configurations stored in non-volatile memory and RS-232 configurations are reset to their default states: • DRAM, NRAM, and RDISk memory segments are cleared.
PAGE 126
:BOOT[:WARM] Comments DIAGnostic:BOOT[:WARM] causes the System instrument to restart (reboot) using the current configuration stored in non-volatile memory. The effect is the same as cycling power. • The System instrument goes through its power-up self tests. • The Non-volatile system state is used for configuration wherever applicable. • DRAM, NRAM, and RDISk memory segments remain intact.
PAGE 127
:COMMunicate :SERial[0][:OWNer]? Comments Example :COMMunicate :SERial[n]:STORe Comments DIAGnostic:COMMunicate:SERial[0][:OWNer]? returns the current "owner" of the built-in serial interface. The values returned will be; SYST, IBAS, or NONE. • Related Commands: DIAG:COMM:SER[0][:OWN] Determine Which Instrument has the Serial Interface DIAG:COMM:SER? Note that 0 (zero) and :OWNer are implied. enter statement Statement returns the string SYST, IBAS, or NONE.
PAGE 128
:DOWNload:CHECked [:MADDress] DIAGnostic:DOWNload:CHECked[:MADDress]
, writes data into a non-volatile user RAM segment starting at address using error correction. The user RAM segment is allocated by the DIAG:NRAM:CREate or DIAG:DRAM:CREate command.
PAGE 129
Byte Format Each byte sent with this command is expected to be in the following format: Bit # 7 Control Bit 6 5 4 3 Check Bits 2 1 0 Data Bits – Control Bit is used to indicate the serial driver information such as clear, reset, or end of transmission. This bit is ignored by the regular 488.2 driver. The control bit should be one for regular data. – Check Bits are used to detect and correct a single bit error. The control bit is not included in the check.
PAGE 130
:DOWNload:CHECked :SADDress DIAGnostic:DOWNload:CHECked:SADDress
, writes data to Non-volatile user RAM at a single address specified by address using error correction. It can also write to devices with registers in the A16 address space.
PAGE 131
Byte Format Each byte sent with this command is expected to be in the following format: Bit # 7 Control Bit 6 5 4 3 Check Bits 2 1 0 Data Bits – Control Bit is used to indicate the serial driver information such as clear, reset, or end of transmission. This bit is ignored by the regular 488.2 driver. The control bit should be one for regular data. – Check Bits are used to detect and correct a single bit error. The control bit is not included in the check.
PAGE 132
:DOWNload [:MADDress] DIAGnostic:DOWNload[:MADDress]
, writes data into a Non-volatile user RAM segment starting at address. The user RAM segment is allocated by the DIAG:NRAM:CREate command.
PAGE 133
Example :DOWNload :SADDress Load Dynamic Configuration Information into an Allocated RAM Segment DIAG:NRAM:CRE 6 Allocate a segment of user RAM. DIAG:BOOT:WARM Reboot system to complete allocation. DIAG:NRAM:ADDR? Query starting address. enter value to variable X Get starting address into X. DIAG:DOWN ,table data Download table data. VXI:CONF:DCTAB Link configuration table to configuration algorithm. DIAG:BOOT:WARM Reboot to set new configuration.
PAGE 134
Example Download Data to a Single Address Location This program downloads an array with the data 1, 2, 3, 4, 5 to register 32 on a device with logical address 40 in VXIbus A16 address space. DIM Dnld_data(1:5) Dimension controller array. DATA 1,2,3,4,5 READ Dnld_data(*) Load data into controller array. OUTPUT "DIAG:DOWN:SADD #H1FCA20,#210"; This line is sent without termination. Send Dnld_data as 16-bit words :DRAM:AVAilable? Comments Terminate after last word with EOI or LF and EOI.
PAGE 135
:DRAM:CREate DIAGnostic:DRAM:CREate , creates a Non-volatile RAM area for loading instrument drivers. DIAG:DRAM:CREate 0 removes the RAM segment when the system is rebooted. Parameters Comments Parameter Name Parameter Type Range of Values Default Units numeric 0 to available RAM or MIN | MAX none numeric 0 to available RAM or MIN | MAX | DEF none • is the number of bytes to be allocated to DRAM use. A size of zero will remove the DRAM segment.
PAGE 136
:DRIVer:INSTall DIAGnostic:DRIVer:INSTall makes the drivers downloaded to Flash ROM available (installs them) by creating the driver index table. Comments • You cannot download any additional drivers into Flash ROM after you have executed this command. To download any new drivers you must recreate the Flash ROM driver area with the DIAG:FROM:CREate command. This will erase any drivers you have already downloaded, which will then have to be reloaded.
PAGE 137
:DRIVer:LOAD DIAGnostic:DRIVer:LOAD loads the instrument driver contained in the driver_block into a previously created DRAM segment. Parameters Comments Parameter Name Parameter Type Range of Values arbitrary block program data See “Parameter Types” on page 121 Default Units none • driver_block is the actual binary driver data to be transferred. • Related Commands: DIAG:DRAM:AVAilable?, DIAG:DRAM:CREate, DIAG:DRIVer:LIST...
PAGE 138
:FROM:AVAilable? DIAGnostic:FROM:AVAilable? returns the amount of Flash ROM remaining to hold new device drivers. This is the amount of Flash ROM in the segment minus any previously loaded drivers and overhead. Comments • DIAG:FROM:AVAilable? returns zero if you have not created a valid flash driver area using DIAG:FROM:CREate while the system is in “ LOAD” mode.
PAGE 139
:FROM:SIZE? DIAGnostic:FROM:SIZE? returns the amount of Flash ROM available to be used as Flash ROM driver area. This command does not take into account the size of the driver index table, checksum field, and so forth.
PAGE 140
:INTerrupt:PRIority[n] Comments DIAGnostic:INTerrupt:PRIority[n] gives a priority level to the VXI interrupt line specified by [n]. Parameter Name Parameter Type Range of Values Default Units [n] numeric 1 through 7 1 numeric 1-7 | MIN | MAX | DEF none • The priority of an interrupt line determines which line will be acknowledged first when more than one line is interrupting. • For level, lower values have lower priority (level 1 is a lower priority than level 2).
PAGE 141
:INTerrupt:RESPonse? DIAGnostic:INTerrupt:RESPonse? returns the interrupt acknowledge response (STATUS/ID word) from the highest priority VXI interrupt line. • The value returned is the response from the interrupt acknowledge cycle Comments (STATUS/ID word) of a device interrupting on one of the interrupt lines set up with the DIAG:INT:SETup[n] command. • Bits 0 through 7 of the STATUS/ID word are the interrupting device’s logical address. Bits 8 through 15 are Cause/Status bits.
PAGE 142
:INTerrupt:SETup[n] DIAGnostic:INTerrupt:SETup[n] specifies that an interrupt on VXI backplane interrupt line [n] will be serviced by the System instrument service routine (DIAGnostic:INTerrupt commands) rather than the operating system service routine. Parameters Comments Parameter Name Parameter Type Range of Values Default Units [n] numeric 1 through 7 1 boolean 0 | 1 | OFF | ON none • SETup1 through SETup7 specifies the VXI interrupt lines 1 through 7.
PAGE 143
• Related Commands: DIAG:INTerrupt:SETup[n], DIAG:INTerrupt:PRIority[n], DIAG:INTerrupt:ACTivate, DIAG:INTerrupt:RESPonse? Example Determine Interrupt Setup for Line 4 DIAG:INT:SET4? enter statement :NRAM:ADDRess? Comments Statement returns 0 or 1. DIAGnostic:NRAM:ADDRess? returns the starting address of the Non-volatile user RAM segment allocated using DIAG:NRAM:CREate. • DIAG:NRAM:CREate does not allocate the RAM segment until after a subsequent reboot.
PAGE 144
Example Allocate a 15 Kbyte User Non-Volatile RAM Segment DIAG:NRAM:CREate 15360 :NRAM:CREate? Comments Allocate 15 Kbyte segment of user RAM. DIAGnostic:NRAM:CREate? [MIN | MAX] returns the current or allowable (MIN | MAX) size of the user Non-volatile RAM segment. • DIAG:NRAM:CREate does not allocate driver RAM until a subsequent reboot. To get accurate results, execute DIAG:NRAM:CREate? after the reboot.
PAGE 145
:POKE DIAGnostic:POKE
,, writes data (number of bits given by width) starting at address. Parameters Comments Parameter Name Parameter Type Range of Values Default Units
numeric 0 to 16,777,215 (#HFFFFFF) none numeric 8 | 16 | 32 none numeric 8 to 32-bit integer none •
specifies a location within the range of the control processor’s addressing capability.
PAGE 146
:RDISk:CREate DIAGnostic:RDISk:CREate allocates memory for a RAM disc volume. The RAM disc volume is defined for use only by the IBASIC option. Parameters Comments Parameter Name Parameter Type Range of Values Default Units numeric 0 to available RAM or MIN | MAX none • The RAM disc segment will only be created after the System instrument has been rebooted (cycle power or execute DIAG:BOOT).
PAGE 147
:UPLoad[:MADDress]? DIAGnostic:UPLoad[:MADDress]?
, returns the number of bytes specified by byte_count, starting at address. Parameters Comments Parameter Name Parameter Type Range of Values Default Units
numeric 0 to 16,777,215 (#HFFFFFE) none numeric 0 to (999,999,998) none •
may be specified in decimal, hex (#H), octal (#Q), or binary (#B) formats. • UPLoad is done by word (16-bit) access so address and byte_count must be even.
PAGE 148
:UPLoad:SADDress? DIAGnostic:UPLoad:SADDress?
, returns the number of bytes specified by byte_count at address. Parameters Comments Parameter Name Parameter Type Range of Values Default Units
numeric 0 to 16,777,215 (#HFFFFFE) none numeric 0 to (999,999,998) none •
may be specified in decimal, hex (#H), octal (#Q), or binary (#B) formats. • UPLoad is done by word (16-bit) access so address and byte_count must be even.
PAGE 149
OUTPut The OUTPut subsystem controls the output of pulses and levels to the ECLTrg and TTLTrg* trigger buses as well as the command module’s front panel Trig Out connector. Signals connected to the front panel Trig In connector can also operate the ECLTrg and TTLTrg* trigger buses. Note Subsystem Syntax 148 The HP E1406A Command Module’s TTLTrg trigger lines and Trig Out port use "low true" or negative logic. When a trigger level is set (for example, OUTPut:EXTernal:LEVel 1), a low voltage is present.
PAGE 150
:ECLTrg :IMMediate Comments OUTPut:ECLTrg:IMMediate causes a pulse to appear on the specified ECL Trigger line. • ECLTrg represents either ECLTrg0 or ECLTrg1. • OUTPut:ECLTrg:STATe must be ON and OUTPut:ECLTrg:SOURce must be set to INT or NONE in order to issue an immediate pulse. A "settings conflict" error is generated if :STATe is not ON.
PAGE 151
:ECLTrg:LEVel [:IMMediate]? OUTPut:ECLTrg:LEVel[:IMMediate]? returns the current logic level of the selected ECLTrg trigger line. • ECLTrg represents either ECLTrg0 or ECLTrg1. Example :ECLTrg:SOURce Determine Current State of ECLTrg1 OUTP:ECLT1:LEV? Ask for level. enter statement Return state of trigger line. OUTPut:ECLTrg:SOURce selects which source will drive the selected trigger line.
PAGE 152
:ECLTrg[:STATe] OUTPut:ECLTrg[:STATe] enables configuration (for example, source and level) of the specified trigger line. Parameters Comments Parameter Name Parameter Type Range of Values Default Units numeric 0 or 1 N/A boolean 0 | 1 | OFF | ON none • When a trigger line is asserted (OUTP:ECLTrg:LEVel 1), it remains asserted when :STATe OFF is set. Setting :STATe ON again de-asserts the line by setting the source to NONE.
PAGE 153
:EXTernal:LEVel [:IMMediate] OUTPut:EXTernal:LEVel[:IMMediate] sets the Trig Out port to a logic level of 0 or 1. Parameters Comments Parameter Name Parameter Type Range of Values Default Units boolean 0 | 1 | OFF | ON none • OUTP:EXTernal:STATe must be ON. • OUTP:EXTernal:SOURce must be INTernal. • Once the level of the Trig Out port is set to logic level 1, it remains set if OUTP:EXTernal:STATe OFF is set.
PAGE 154
• Related Commands: OUTP:EXTernal[:STATe], OUTP:EXTernal:LEVel[:IMMediate] • *RST Condition: OUTP:EXTernal:SOURce NONE Example Select TTLTrg0* to Drive the Trig Out Port OUTP:EXT:SOUR TTLT0 :EXTernal:SOURce? OUTPut:EXTernal:SOURce? queries for the source currently driving the Trig Out port. Comments • Querying the source with :STATe OFF returns NONE, regardless of the actual source setting.
PAGE 155
:TTLTrg :IMMediate Comments OUTPut:TTLTrg:IMMediate causes a pulse to appear on the specified TTL trigger line. • TTLTrg represents TTLTrg0 through TTLTrg7. • OUTP:TTLTrg:STATe must be ON and OUTP:TTLTrg:SOURce must be set to INT or NONE in order to issue an immediate pulse. An error message is generated if :STATe is not ON.
PAGE 156
:TTLTrg:LEVel [:IMMediate]? Comments Example :TTLTrg:SOURce OUTPut:TTLTrg:LEVel[:IMMediate]? returns the current logic level of the selected TTLTrg* trigger line specified by n 0 through 7. • TTLTrg represents TTLTrg0 through TTLTrg7. Determine Current State of TTLTrg1* OUTP:TTLT1:LEV? Ask for level. enter statement Return state of trigger line. OUTPut:TTLTrg:SOURce selects which source will drive the selected trigger line.
PAGE 157
:TTLTrg[:STATe] OUTPut:TTLTrg[:STATe] controls whether the System instrument may drive the specified trigger line. Parameters Comments Parameter Name Parameter Type Range of Values Default Units numeric 0 through 7 N/A boolean 0 | 1 | OFF | ON none • OUTP:TTLTrg:STATe must be ON in order to specify a trigger source, issue a pulse, or set a trigger level. • OUTP:TTLTrg:STATe must be ON for the source to drive the trigger line.
PAGE 158
PROGram The PROGram subsystem allows you to write an operating system into the command module Flash ROM, to read data from the Flash ROM, or to delete the contents of the Flash ROM. PROG:DEFine? and PROG:DEFine:CHECked? are valid in SYSTEM or LOAD mode. The other PROGram commands listed are active ONLY in LOAD mode. Subsystem Syntax [:SELected]:DEFine PROGram [:SELected] :DEFine :CHECked :CHECked? :DEFine? :DELete PROGram[:SELected]:DEFine writes the operating system into Flash ROM.
PAGE 159
[:SELected]:DEFine :CHECked PROGram[:SELected]:DEFine:CHECked writes the operating system into Flash ROM over an RS-232 line. Parameters Comments Parameter Name Parameter Type arbitrary block program data Range of Values Default Units See comments below. none • This command returns an error if executed from the System instrument. • Arbitrary Block Program Data parameters are used to transfer blocks of data in the form of bytes.
PAGE 160
Byte Format Each byte sent with this command is expected to be in the following format: Bit # 7 Control Bit 6 5 4 3 Check Bits 2 1 0 Data Bits – Control Bit is used to indicate the serial driver information such as clear, reset, or end of transmission. This bit is ignored by the regular 488.2 driver. The control bit should be one for regular data. – Check Bits are used to detect and correct a single bit error. The control bit is not included in the check.
PAGE 161
[:SELected]:DEFine :CHECked? Comments PROGram[:SELected]:DEFine:CHECked? reads data from Flash ROM over an RS-232 line. • This command returns a definite length arbitrary block of data in the same format used to send data over RS-232. [:SELected]:DEFine? Comments PROGram[:SELected]:DEFine? reads data from the Flash ROM. • This command returns the operating system program loaded in Flash ROM as a definite length arbitrary block.
PAGE 162
STATus The STATus subsystem commands access the Condition, Event, and Enable Registers in the Operation Status Group and the Questionable Data Group.
PAGE 163
:OPERation:ENABle STATus:OPERation:ENABle sets an enable mask to allow events monitored by the Condition Register and recorded in the Event Register, to send a Summary bit to the Status Byte Register (bit 7). Parameters Comments Parameter Name Parameter Type Range of Values Default Units numeric 256 none • Bit 8 in the Condition Register is used by the System instrument (command module) to indicate when an interrupt set up by the DIAG:INTerrupt commands has been acknowledged.
PAGE 164
:OPERation[:EVENt]? Comments STATus:OPERation[:EVENt]? returns which bits in the Event Register (Operation Status Group) are set. The Event Register indicates when there has been a positive transition in the Condition Register. • Bit 8 in the Condition Register is used by the System instrument (command module) to indicate when an interrupt set up by the DIAG:INTerrupt commands has been acknowledged. • Bit 8 in the Event Register generally is the only bit which is used.
PAGE 165
:OPERation :PTRansition STATus:OPERation:PTRansition sets the positive transition Comments • See STATus:OPERation:NTRansition for parameters and mask. For each bit unmasked, a 0-to-1 transition of that bit in the associated Condition Register will set the same bit in the associated Event Register. comments.
PAGE 166
:QUEStionable :ENABle STATus:QUEStionable:ENABle sets an enable mask to allow events monitored by the Condition Register and recorded in the Event Register, to send a summary bit to the Status Byte Register (bit 7). Parameters Comments Parameter Name Parameter Type Range of Values Default Units numeric 256 none • When the summary bit is sent, it sets bit 7 in the Status Byte Register.
PAGE 167
:QUEStionable :NTRansition STATus:QUEStionable:NTRansition sets the negative transition mask. For each bit unmasked, a 1-to-0 transition of that bit in the associated Condition Register will set the same bit in the associated Event Register. Parameters Parameter Name Parameter Type numeric or non-decimal numeric Range of Values Default Units 0 through +32767 none The non-decimal numeric forms are the #H, #Q, or #B formats specified by IEEE-488.2.
PAGE 168
SYSTem The SYSTem command subsystem for the System instrument provides for: • Control and access of the System instrument’s real time clock/calendar (SYST:TIME, SYST:TIME?, SYST:DATE, SYST:DATE?). • Access to the System instrument’s error queue (SYST:ERRor?). • Configuring the communication ports (HP-IB and serial).
PAGE 169
:COMMunicate:GPIB :ADDRess? Comments SYSTem:COMMunicate:GPIB:ADDRess? returns the HP E1406A Command Module’s primary HP-IB address. • The HP E1406A Command Module (primary) HP-IB address is set using switches on the module. Example :COMMunicate … :SERial[n]:… Comments Read the Primary HP-IB Address SYST:COMM:GPIB:ADDR? Read the HP-IB address. enter statement Enter the HP-IB address.
PAGE 170
:COMMunicate :SERial[n]:CONTrol :DTR SYSTem:COMMunicate:SERial[n]:CONTrol:DTR controls the behavior of the Data Terminal Ready output line. DTR can be set to a static state (ON | OFF), can operate as a modem control line (STANdard), or can be used as a hardware handshake line (IBFull).
PAGE 171
:COMMunicate :SERial[n]:CONTrol :RTS SYSTem:COMMunicate:SERial[n]:CONTrol:RTS controls the behavior of the Request To Send output line. RTS can be set to a static state (ON | OFF), can operate as a modem control line (STANdard), or can be used as a hardware handshake line (IBFull).
PAGE 172
:COMMunicate :SERial[n][:RECeive] :BAUD SYSTem:COMMunicate:SERial[n][:RECeive]:BAUD sets the baud rate for the serial port. Parameters Comments Parameter Name Parameter Type numeric Range of Values Default Units 300 | 1200 | 2400 | 4800 | 9600 | 19200 | MIN | MAX none • Attempting to set baud_rate to other than those values shown will result in an Error -222, "Data out of range". • DIAG:BOOT:COLD will set BAUD to 9600. • *RST condition: No change.
PAGE 173
:COMMunicate :SERial[n][:RECeive] :BITS SYSTem:COMMunicate:SERial[n][:RECeive]:BITS sets the number of bits to be used to transmit and receive data. Parameters Comments Parameter Name Parameter Type Range of Values Default Units numeric 7 | 8 | MIN | MAX none • Attempting to set bits to other than those values shown will result in an Error -222, "Data out of range".
PAGE 174
:COMMunicate :SERial[n][:RECeive] :PACE[:PROTocol] SYSTem:COMMunicate:SERial[n][:RECeive]:PACE[:PROTocol] enables or disables receive pacing (XON/XOFF) protocol. Parameters Comments Parameter Name Parameter Type Range of Values Default Units discrete XON | NONE none • While …PROT is XON, the serial interface will send XOFF when the buffer reaches the …STOP threshold, and XON when the buffer reaches the …STARt threshold. • For an HP E1324A, AUTO is always ON.
PAGE 175
:COMMunicate :SERial[n][:RECeive] :PACE:THReshold :STARt SYSTem:COMMunicate:SERial[n][:RECeive]:PACE:THReshold:STARt configures the input buffer level at which the specified interface may send the XON character (ASCII 1116), assert the DTR line, and/or assert the RTS line.
PAGE 176
:COMMunicate :SERial[n][:RECeive] :PACE:THReshold :STOP SYSTem:COMMunicate:SERial[n][:RECeive]:PACE:THReshold:STOP configures the input buffer level at which the specified interface may send the XOFF character (ASCII 1316), de-assert the DTR line, and/or de-assert the RTS line.
PAGE 177
:COMMunicate :SERial[n][:RECeive] :PARity SYSTem:COMMunicate:SERial[n][:RECeive]:PARity configures the type of parity to be checked for received data, and generated for transmitted data. Parameters Comments Parameter Name Parameter Type Range of Values Default Units discrete EVEN | ODD | ZERO | ONE | NONE none • Attempting to set type to other than the values shown results in Error -222, "Data out of range".
PAGE 178
• Related Commands: SYST:COMM:SER[n][:REC]:PAR:CHEC 1 | 0 | ON | OFF, SYST:COMM:SER[n][:REC]:BITS 7 | 8, SYST:COMM:SER[n][:REC]:SBIT 1 | 2, • *RST Condition: No change. Example :COMMunicate :SERial[n][:RECeive] :PARity? Example :COMMunicate :SERial[n][:RECeive] :PARity:CHECk Set Parity Check/Generation to ODD SYST:COMM:SER0:PAR ODD Set parity type. SYST:COMM:SER0:PAR:CHEC ON Enable parity check/generation.
PAGE 179
:COMMunicate :SERial[n][:RECeive] :PARity:CHECk? Example SYSTem:COMMunicate:SERial[n][:RECeive]:PARity:CHECk? returns the state of parity checking. Query Parity Checking SYST:COMM:SER0:PAR:CHEC? enter statement :COMMunicate :SERial[n][:RECeive] :SBITs Statement enters 0 or 1. SYSTem:COMMunicate:SERial[n][:RECeive]:SBITs sets the number of stop bits to be used to transmit and receive data.
PAGE 180
:COMMunicate :SERial[n][:RECeive] :SBITs? SYSTem:COMMunicate:SERial[n][:RECeive]:SBITs? [MIN | MAX] returns: – The current stop bit setting if no parameter is sent. – The maximum allowable setting if MAX is sent. – The minimum allowable setting if MIN is sent. Example :COMMunicate :SERial[n]:TRANsmit :AUTO Query the Current Stop Bit Configuration SYST:COMM:SER0:SBITs? :REC is implied. enter statement Statement enters 1 or 2.
PAGE 181
:COMMunicate :SERial[n]:TRANsmit :PACE[:PROTocol] SYSTem:COMMunicate:SERial[n]:TRANsmit:PACE[:PROTocol] enables or disables the transmit pacing (XON/XOFF) protocol. Parameters Comments Parameter Name Parameter Type Range of Values Default Units discrete XON | NONE none • For an HP E1324A, AUTO is always ON. In this case, …TRAN:PACE will also set …[RECeive]:PACE.
PAGE 182
:DATE SYSTem:DATE ,, sets the command module’s internal calendar. Parameters Comments Parameter Name Parameter Type Range of Values Default Units numeric Must round to 1980 to 2079. none numeric Must round to 1 to 12. none numeric Must round to 1 through last day of month. none • The upper limit on the day parameter is dependent on the month parameter and may be dependent on the year parameter in the case of a leap year.
PAGE 183
:ERRor? SYSTem:ERRor? queries the system’s error queue. The response format is: ,"". Comments • As system errors are detected, they are placed in the System instrument error queue. The error queue is first in, first out. This means that if several error messages are waiting in the queue, each SYST:ERR? query will return the oldest error message, and that message will be deleted from the queue.
PAGE 184
:TIME? SYSTem:TIME? [MAX | MIN,MAX | MIN,MAX | MIN] returns: When no parameter is sent: the current system time is in the form +HH,+MM,+SS, where HH can be 0 through 23 hours, MM can be 0 through 59 minutes, and SS can be 0 through 60 seconds. When parameters are sent: the minimum or maximum allowable values for each of the three parameters are returned. The parameter count must be three. Example :VERSion? Query the System Time SYST:TIME? Ask for current time.
PAGE 185
VXI The VXI command subsystem provides for: – Determining the number, type, and logical address of the devices (instruments) installed in the C-size mainframe. – Direct access to VXIbus A16 registers within devices installed in the mainframe. – Sending commands using the word serial protocol. – Access to message-based devices from an RS-232 terminal.
PAGE 186
:COMMand ,[,] :COMMand? ,[,[,]] [:MESSage] ,""[,] :WRITe ,, :WSProtocol :COMMand :AHLine , :AILine , :AMControl :ANO :ANY :BAVailable :BNO :BREQuest :CEVent , :CLR :CLOCk :CRESponse :ENO :GDEVice :ICOMmander :RDEVice
PAGE 187
:RPRotocol? :RSARea? :RSTB? :SLModid? , (0-127) :SUModid? , (0-63) :RESPonse? :CONFigure:CTABle VXI:CONFigure:CTABle
links a user-defined commander/ servant hierarchy table to the command module (resource manager) processor. The command module must be the acting resource manager in order for the table to be implemented.
PAGE 188
:CONFigure:CTABle? Example :CONFigure:DCTable VXI:CONFigure:CTABle? returns the starting address of the user’s commander/servant hierarchy table. Query Address of the Commander/Servant Hierarchy Table VXI:CONF:CTABle? Ask for address. enter statement Return address. VXI:CONFigure:DCTable
links a user-defined dynamic configuration table to the command module (resource manager) processor. The command module must be the acting resource manager in order for the table to be implemented.
PAGE 189
:CONFigure:DCTable? VXI:CONFigure:DCTable? returns the starting address of the user’s dynamic configuration table. Example :CONFigure :DLADdress? Comments Query Address of Dynamic Configuration Table VXI:CONF:DCTable? Ask for address. enter statement Return address. VXI:CONFigure:DLADdress? returns a comma (,) separated decimal numeric list of device logical addresses currently installed in the mainframe.
PAGE 190
:CONFigure:DLISt? VXI:CONFigure:DLISt? [] returns information about the device specified by logical_addr. Response data is in the form: n1, n2, n3, n4, n5, n6, c1, c2, c3, c4, c5, s1, s2, s3, s4 Where the fields above are defined as: n fields c fields s fields Indicate numeric data response fields. Indicate character data response fields. Indicate string data response fields. n1 Device’s Logical Address. A number from 0 to 255. n2 Commander’s Logical Address.
PAGE 191
Parameters Comments Parameter Name Parameter Type Range of Values Default Units numeric 0 to 255 (or nothing) none • When logical_addr is not specified, VXI:CONF:DLIS? returns information for each of the devices installed, separated by semicolons (;). If the command module is not the resource manager, it returns information on only the devices in its servant area.
PAGE 192
:CONFigure:ETABle VXI:CONFigure:ETABle
links a user-defined extender table to the command module (resource manager) processor. The command module must be the acting resource manager in order for the table to be implemented.
PAGE 193
:CONFigure :HIERarchy? Comments VXI:CONFigure:HIERarchy? returns current hierarchy configuration information about the selected logical address. The individual fields of the response are comma separated. If the information about the selected logical address is not available from the destination device (that is, the requested device is not in the mainframe or the command module’s servant area) then Error -224, "Illegal parameter value" will be set and no response data will be sent.
PAGE 194
• Related Commands: VXI:SELect, VXI:CONF:HIERarchy:ALL?, VXI:CONF:LADDress? :CONFigure :HIERarchy:ALL? Comments VXI:CONFigure:HIERarchy:ALL? returns the configuration information about all logical addresses in the mainframe, or the devices in the command module’s servant area if the command module is not the resource manager. The information is returned in the order specified in the response to VXI:CONF:LADDress?.
PAGE 195
A24 memory offset: An integer between -1 and 16777215 inclusive. Indicates the base address for any A24 registers which are present on the device. -1 indicates that the device has no A24 memory. A32 memory offset: An integer between -1 and 4294967295 inclusive. Indicates the base address for any A32 registers which are present on the device. -1 indicates that the device has no A32 memory. A16 memory size: An integer between -1 and 65535 inclusive.
PAGE 196
:CONFigure :INFormation:ALL? Comments VXI:CONFigure:INFormation:ALL? returns the static information about all logical addresses. The information is returned in the order specified in the response to VXI:CONF:LADDress?. The information about multiple logical addresses will be semicolon (;) separated and follow the IEEE 488.2 response message format. Individual fields of the output are comma (,) separated.
PAGE 197
:CONFigure:ITABle? VXI:CONFigure:ITABle? returns the starting address of the user’s interrupt line allocation table. Example :CONFigure :LADDress? Comments 196 Query Address of Interrupt Line Allocation Table VXI:CONF:ITABle? Ask for address. enter statement Return address. VXI:CONFigure:LADDress? returns a comma (,) separated list of logical addresses of devices in the mainframe, or a list of devices in the command module’s servant area if the command module is not the resource manager.
PAGE 198
:CONFigure :MEXTender :ECLTrg VXI:CONFigure:MEXTender:ECLTrg is used to configure the selected mainframe extender to direct the ECL trigger specified by . Parameters Comments Parameter Name Parameter Type Range of Values Default Units numeric 0 or 1 none discrete IN | OUT | NONE none • Select the logical address of the extender to access with the VXI:SELect command.
PAGE 199
:CONFigure :MEXTender :INTerrupt VXI:CONFigure:MEXTender:INTerrupt is used to configure the selected mainframe extender to direct the interrupt line specified by . Parameters Comments Parameter Name Parameter Type Range of Values Default Units numeric 0 or 1 none discrete IN | OUT | NONE none • Select the logical address of the extender to access with VXI:SELect.
PAGE 200
:CONFigure :MEXTender :TTLTrg VXI:CONFigure:MEXTender:TTLTrg is used configure the selected mainframe extender to direct the TTL trigger specified by . Parameters Comments Parameter Name Parameter Type Range of Values Default Units numeric 0 through 1 none discrete IN | OUT | NONE none • Select the logical address of the extender to access with VXI:SELect.
PAGE 201
:CONFigure:MTABle VXI:CONFigure:MTABle
links a user-defined A24/A32 address allocation table to the command module (resource manager) processor. The command module must be the acting resource manager in order for the table to be implemented.
PAGE 202
:CONFigure:MTABle? VXI:CONFigure:MTABle? returns the starting address of the user’s A24/A32 address allocation table. Example :CONFigure:NUMBer? Query Address of A24/A32 Address Allocation Table VXI:CONF:MTABle? Ask for address. enter statement Return address. VXI:CONFigure:NUMBer? returns the number of devices in the system when it is issued to a resource manager. This is an integer between 1 and 256 inclusive.
PAGE 203
Example :READ? Read the Data Low Register of Device at Logical Address 72 VXI:QUERY? 72 Query value of Data Low Register. enter statement Input 16-bit value. VXI:READ? , allows access to the entire 64-byte A16 register address space for the device specified by logical_addr. Since the VXIbus system is byte-addressed, while the registers are 16-bits wide, registers are specified by even addresses only.
PAGE 204
:RECeive[:MESSage]? VXI:RECeive[:MESSage]? [,] receives a message from the message-based device at logical_addr. Parameters Comments Parameter Name Parameter Type Range of Values Default Units numeric Must round to 0 through 255. none discrete/numeric END | LF | CRLF | none • A message ends when the condition specified by the end_of _msg parameter is met.
PAGE 205
:REGister:READ? VXI:REGister:READ? returns the contents of the specified 16-bit register at the selected logical address as an integer (see VXI:SELect). Parameters Comments Parameter Name Parameter Type numeric Default Units Range of Values Even numbers from 0 to 62 or register name (see below).
PAGE 206
Example Read from a Register on the Currently Selected Device VXI:READ? ICON :REGister:WRITe Read from the Interrupt Control Register of the currently selected device. VXI:REGister:WRITe , writes data to the specified 16-bit register at the selected logical address (see VXI:SELect). Parameters Comments Parameter Name Parameter Type numeric Even numbers from 0 to 62 or register name (see below).
PAGE 207
:RESet VXI:RESet performs a soft reset of the device at logical_addr. Parameters Comments Parameter Name Parameter Type Range of Values Default Units numeric Must round to 0 through 255. none • VXI:RESet sets the Sysfail Inhibit bit in the device’s Control Register, then sets the Reset bit, waits 100µs, then clears Reset. When the device has passed its self-test, Sysfail Inhibit is cleared. If the device fails during the reset (does not assert "Passes" within 4.
PAGE 208
:ROUTe:ECLTrg VXI:ROUTe:ECLTrg configures the routing of the ECL trigger line specified by for all mainframe extenders in the system. Parameters Comments Parameter Name Parameter Type Range of Values Default Units numeric 0 or 1 none • The routing is set so the device selected by the VXI:SELect command can source the trigger line and all other devices in the system may monitor that trigger line. • Some mainframe extender devices do not support some trigger lines.
PAGE 209
:ROUTe:TTLTrg VXI:ROUTe:TTLTrg configures the routing of the TTL trigger line specified by for all mainframe extenders in the system. Parameters Comments Parameter Name Parameter Type Range of Values Default Units numeric 0 through 7 none • The routing is set so the device selected by the VXI:SELect command can source the trigger line and all other devices in the system may monitor that trigger line. • Some mainframe extender devices do not support some trigger lines.
PAGE 210
:SELect? :SEND:COMMand VXI:SELect? returns the logical address which will be used by many subsequent commands in the VXI subsystem. If no logical address has been selected, this query will return -1. VXI:SEND:COMMand ,[,] sends the specified word serial command (and optional data) to logical_addr. Parameters Parameter Name Parameter Type Range of Values Default Units numeric Must round to 0 through 255.
PAGE 211
:SEND:COMMand? VXI:SEND:COMMand ,[,[,]] sends the specified word serial command (and optional dataN values) using the word-serial protocol, to the module at logical_addr. It then waits for and returns a 16-bit response value. Parameters Parameter Name Parameter Type Range of Values Default Units numeric Must round to 0 through 255. none The command field and any required data fields are specified in the following table.
PAGE 212
Comments • and may be specified in decimal, hex (#H), octal (#Q), or binary (#B) formats. • VXI:SEND:COMMand uses the Word Serial Transfer Protocol. This protocol is described in the VXIbus System Specification Manual. • VXI:SEND:COMMand? is recommended for use with devices conforming to VXIbus Specifications, revision 1.3 or later. • This command has been retained for compatibility with existing programs.
PAGE 213
Example :WRITe Send a Message to a Message-Based Device at Logical Address 16 VXI:SEND 16,"MEAS:VOLT:DC?" Send command to message-based multimeter (last by is sent with END bit set). VXI:REC? 16 Retrieve voltage measurement. VXI:WRITe , , allows access to the entire 64-byte A16 register address space for the device specified by logical_addr.
PAGE 214
:WSProtocol :COMMand:command :command VXI:WSProtocol:COMMand:command is a series of commands which sends the specified Word Serial Command to the address set using the VXI:SELect command and continues without waiting for a response. The response to this command can be read with the VXI:WSProtocol:RESPonse? command. The following table lists the available commands and their parameters (if any). parameter1 parameter2 :AHLine (1-7) (0-7) Assign Handler Line.
PAGE 215
Comments • byte, cmd_word, event_number, hand_id, int_id, line_number, logical_address, modid, and response_mask may be specified in decimal, hex (#H), octal (#Q), or binary (#B) formats. • end_bit selects whether the END bit is set in the command. • top_level selects whether the Top_level bit is set in the command. • enable selects whether the Enable bit is set in the command.
PAGE 216
:WSProtocol:QUERy :command? :command VXI:WSProtocol:QUERy:command? is a series of commands which sends the specified Word Serial Command to the address set using the VXI:SELect command and waits for a response. The returned value is the response to the command and is an integer. The following table lists the available commands and their parameters (if any). Description parameter1 parameter2 :AHLine? (1-7) (0-7) Assign Handler Line.
PAGE 217
Common Command Reference This section describes the IEEE-488.2 common commands that can be used to program instruments in the mainframe. Commands are listed alphabetically (the following table shows the common commands listed by functional group). Examples are shown when the command has parameters or returns a response; otherwise the command string is as shown in the headings in this section. For additional information on any common commands, refer to the IEEE Standard 488.2-1987. IEEE 488.
PAGE 218
*CLS *DMC , Clear Status Command clears all status registers (Standard Event Status Register, Standard Operation Event Status Register, Questionable Data Event Register) and the error queue for an instrument. This clears the corresponding summary bits (bits 3, 5, and 7) and the instrument-specific bits (bits 0, 1, and 2) in the Status Byte Register.
PAGE 219
*ESE? Standard Event Status Enable Query returns the weighted sum of all enabled (unmasked) bits in the Standard Event Status Register. Example *ESR? 10 OUTPUT 70900;"*ESE?" Send status enable query. 20 ENTER 70900;A Place response in variable. 30 PRINT A Print response. 40 END Standard Event Status Register Query returns the weighted sum of all set bits in the Standard Event Status Register. After reading the register, *ESR? clears the register.
PAGE 220
The *IDN? command returns the following command string for the HP E1406A System instrument (Flash ROMS Run/Load switch is in the "Run" position): HEWLETT-PACKARD,E1406A,0,A,01.00 This command will return the following string for the HP E1406A Loader instrument (Flash ROMS Run/Load switch is in the "Load" position): HEWLETT-PACKARD,LOADER,0,A,01.00 Note Example The revision will vary with the revision of the downloaded operating system installed in the system.
PAGE 221
Note The System instrument no longer implements the *LRN? command. Attempting to have the System instrument execute this command will generate Error -113, "Undefined header". *OPC Operation Complete causes an instrument to set bit 0 (Operation Complete Message) in the Standard Event Status Register when all pending operations have been completed.
PAGE 222
*RMC Remove Individual Macro Command purges an individual macro identified by the name_string parameter. Example OUTPUT 70900;"*RMC ’LIST’" *RST Remove macro command from *DMC example. Reset Resets an instrument as follows: – Sets the instrument to a known state (usually the power-on state). – Aborts all pending operations. – Disables the *OPC and *OPC? modes. *RST does not affect: – The state of the HP-IB interface. – The HP-IB address. – The output queue.
PAGE 223
*STB? Comments Status Byte Register Query returns the weighted sum of all set bits in the Status Byte Register. Refer to Chapter 4 in this manual for more information on the Status Byte Register. You can read the Status Byte Register using either the *STB? command or an HP-IB serial poll (IEEE 488.1 message). Both methods return the weighted sum of all set bits in the register. The difference between the two methods is that *STB? does not clear bit 6 (Service Request); serial poll does clear bit 6.
PAGE 224
HP-IB Message Reference This section describes IEEE-488.1 defined messages and their affect on instruments installed in the mainframe. The examples shown are specifically for HP 9000 Series 200/300 computers using BASIC language. Although any IEEE-488 controller can send these messages, the syntax may be different from that shown here. Device Clear (DCL) or Selected Device Clear (SDC) DCL clears all instruments in the command module servant area. SDC clears a specific instrument.
PAGE 225
Group Execute Trigger (GET) Executing a group execute trigger will trigger an instrument assuming the following conditions are true: – The instrument’s trigger source is set to Bus (TRIG:SOUR BUS command), – The instrument is in the Wait-for-Trigger state, and; – The instrument is addressed to listen (can be done by sending any command, the REMOTE 709ss (ss = secondary address) command, or with the LISTEN command).
PAGE 226
Remote Sets the HP-IB remote enable line (REN) true which places an instrument in the remote state. • The REMOTE 709ss (ss = secondary address) command places the Comments instrument in the remote state. The REMOTE 7 command, does not, by itself, place the instrument in the remote state. After sending the REMOTE 7 command, the instrument will only go into the remote state when it receives its listen address. • In most cases, you will only need the REMOTE command after using the LOCAL command.
PAGE 227
SCPI Commands Quick Reference The following table summarizes SCPI commands for the HP E1406A Command Module System Instrument and Loader Instrument. The "Mode" column shows the active mode(s) for the command. SCPI Commands Quick Reference Command Mode: R = active in RUN mode Mode Description L = active in LOAD mode DIAGnostic :BOOT :COLD R/L Restarts System processor, clears stored configurations. [:WARM] R/L Same as cycling power.
PAGE 228
SCPI Commands Quick Reference Command Mode: R = active in RUN mode :CHECked Mode Description L = active in LOAD mode R/L Loads the instrument driver contained in the specified driver_block into a previously created DRAM segment or Flash ROM area using error correction. R/L Returns the amount of Flash ROM remaining to hold new device drivers. :CREate L Creates a driver area in Flash ROM for the specified number of drivers.
PAGE 229
SCPI Commands Quick Reference Command Mode: R = active in RUN mode Mode Description L = active in LOAD mode :EXTernal :IMMediate R Generate pulse on command module "Trig Out" port. :LEVel [:IMMediate] |0|1|OFF|ON R Sets the output level of the "Trig Out" port. [:IMMediate]? R Returns the output level of the "Trig Out" port. R Sets the source which drives the "Trig Out" port. :SOURce |INT|TTLT|ECLT|NONE :SOURce? R Returns the source driving the "Trig Out" port.
PAGE 230
SCPI Commands Quick Reference Command Mode: R = active in RUN mode Mode Description L = active in LOAD mode :ENABle? R/L Returns value of enable mask in Questionable Status Group. [:EVENt]? R/L Returns value of the bit set in the Event Register (Questionable Status Group). :NTRansition R/L Sets the negative transition mask. :PTRansition R/L Sets the positive transition mask. R/L Returns command module primary HP-IB address.
PAGE 231
SCPI Commands Quick Reference Command Mode: R = active in RUN mode Mode Description L = active in LOAD mode :DATE ,, R/L Sets system calendar. :DATE? [MIN|MAX,MIN|MAX,MIN|MAX] R/L Returns current date or MIN|MAX allowable values. :ERRor? R/L Returns oldest error message in Error Queue. :TIME ,, R/L Sets the system clock. :TIME? [MIN|MAX,MIN|MAX,MIN|MAX] R/L Returns current time or MIN|MAX allowable values.
PAGE 232
SCPI Commands Quick Reference Command Mode: R = active in RUN mode Mode Description L = active in LOAD mode :MTABle? R Query A24/A32 address allocation table starting address. :NUMber? R Gets the number of devices in the system when issued to a resource manager. Generates an error if received by a device other than the resource manager. R Gets the number of mainframe extenders in the system when issued to a resource manager.
PAGE 233
SCPI Commands Quick Reference Command Mode: 232 R = active in RUN mode Mode Description L = active in LOAD mode :AILine , R Assigns an interrupter line to the logical address set using VXI:SEL. A line number of 0 means the handler is to be disconnected. :AMControl R Sends an Asynchronous Mode Control command to the logical address set using VXI:SEL. :ANO R Sends an Abort Normal Operation command to the logical address set using VXI:SEL.
PAGE 234
SCPI Commands Quick Reference Command Mode: R = active in RUN mode Mode Description L = active in LOAD mode :SLOCk R Sends the Set Lock command to the logical address set using VXI:SEL. :SUModid , (0-63) R Sends a Set Upper MODID command to the logical address set using VXI:SEL. :TRIGger R Sends a Trigger command to the logical address set using VXI:SEL.
PAGE 235
SCPI Commands Quick Reference Command Mode: R = active in RUN mode Description L = active in LOAD mode :RPERror? R Sends a Read Protocol Error command to the logical address set using VXI:SEL and waits for a response. :RPRotocol? R Sends a Read Protocol command to the logical address set using VXI:SEL and waits for a response. :RSARea? R Sends a Read Servant Area command to the logical address set using VXI:SEL and waits for a response.
PAGE 236
Common Commands Quick Reference The following table summarizes IEEE 488.2 common (*) commands for the HP E1406A Command Module. All common commands are available in RUN mode and LOAD mode. IEEE 488.2 Common Commands Quick Reference Category Command Title All IEEE 488.2 Common Commands are available in RUN mode and LOAD mode.
PAGE 237
Notes 236 HP E1406A Command Reference Chapter 5 Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.
PAGE 238
Appendix A HP E1406A Specifications and General Information Device Type Real Time Clock This module returns 01416 as the device type in response to a VXI:CONF:DLIS? query if the HP E1406A is set up as a slot zero device and 11416 if the HP E1406A is set up as a non-slot zero device. Accuracy: 0.005% of elapsed time since last set. Temperature coefficient: 0.001% to 0.012% of time since last set (per °C change in temperature). Resolution: 1.
PAGE 239
Power Requirements Cooling Requirements DC Volts DC Current Dynamic Current +5 3.2A 0.32A +12V 0.01A 0.01A -12V 0.01A 0.01A -5.2V 0.4A 0.04A -2V 0.01A 0.01A +24V 0.03A 0.003A For 10 °C rise 1.5 liters/second 0.4mm H2O SCPI Conformance Information The HP E1406A conforms to SCPI-1994.0. The following tables list all the SCPI confirmed and non-SCPI commands that the HP E1406A can execute.
PAGE 240
Table A-1. Switchbox SCPI-1994.0 Confirmed Commands ABORt ARM :COUNt INITiate :CONTinuous [:IMMediate] OUTPut :ECLTrg [:STATe] :TTLTrg [:STATe] [ROUTe:] CLOSe CLOSe? OPEN OPEN? SCAN STATus :OPERation :CONDition? :ENABle :ENABle? [:EVENt]? :PRESet :QUEStionable :CONDition? :ENABle :ENABle? [:EVENt]? SYSTem :CPON :CTYPe? :ERRor? :VERSion? TRIGger [:IMMediate] :SOURce :SLOPe Table A-2.
PAGE 241
Multimeter Commands The following tables apply to the HP E1326A/B multimeters. Table A-3. Multimeter SCPI-1994.
PAGE 242
Table A-4.
PAGE 243
Counter Commands The following tables apply to the HP E1332A 4-Channel Counter/Totalizer and the HP E1333A 3-Channel Universal Counter. Table A-5. HP E1332A SCPI-1994.
PAGE 244
Table A-7. HP E1333A SCPI-1994.
PAGE 245
D/A Converter Commands The following tables apply to the HP E1328A 4-Channel D/A Converter. Table A-9. HP E1328A SCPI-1994.0 Confirmed Commands CALibration [:STATe] [:STATe]? SYSTem :ERRor? :VERSion? STATus :QUEStionable :CONDition? :ENABle :ENABle? [:EVENt]? :OPERation :CONDition? :ENABle :ENABle? [:EVENt]? Table A-10.
PAGE 246
Table A-12.
PAGE 247
System Instrument Commands Table A-13. System Instrument SCPI-1994.
PAGE 248
Table A-14.
PAGE 249
Notes 248 HP E1406A Specifications and General Information Appendix A Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.
PAGE 250
Appendix B HP E1406A Error Messages Using This Appendix This appendix shows how to read an instrument’s error queue, discusses the types of command language-related error messages, and provides a table of all of the System Instrument’s error messages and their probable causes. • Reading an Instrument’s Error Queue . . . . . . . . . . . . . . . . . . Page 249 • Error Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Page 250 • Startup Error Messages and Warnings . . . . . .
PAGE 251
Error Types Negative error numbers are language-related and categorized as shown in Table B-1. Positive error numbers are instrument specific and for the System instrument are summarized in Table B-2. For other instruments, refer to their own user’s manual for a description of error messages. Table B-1.
PAGE 252
Query Errors A query error indicates a problem has occurred in the instrument’s output queue. When a query error occurs, it sets the Query Error bit (bit 2) in the Standard Event Status Register. Query errors can be caused by the following: • An attempt was made to read the instrument’s output queue when no output was present or pending. • Data in the instrument’s output queue has been lost for some reason. Table B-2.
PAGE 253
Table B-2. Error Messages and Causes (continued) Error Messages and Causes Code 252 Message Cause –410 Query interrupted Data is not read from the output buffer before another command is executed. –420 Query unterminated Command which generates data not able to finish executing due to a multimeter configuration error. –430 Query deadlocked Command execution cannot continue since the mainframe’s command input, and data output buffers are full. Clearing the instrument restores control.
PAGE 254
Table B-2. Error Messages and Causes (continued) Error Messages and Causes Code Appendix B Message Cause +2116 Invalid servant area The logical address plus servant area of a commander is greater than 255 or greater than that of a superior commander within this tree. +2117 Slot 0 functions disabled A command module is in slot 0 but slot 0 switches are in the disabled position. +2118 Invalid commander logical address A device does not have a valid commander.
PAGE 255
Table B-2. Error Messages and Causes (continued) Error Messages and Causes Code 254 Message Cause +2142 Invalid UDEF INTR table The interrupter table valid flag is not 1. +2143 Invalid UDEF MEM table The valid flag in the memory table is not set to 1. +2144 Invalid UDEF MEM table data An invalid logical address is specified in the memory table.
PAGE 256
Table B-2. Error Messages and Causes (continued) Error Messages and Causes Code Message Cause +2166 INTX card not installed The INTX daughter card on the VXI-MXI module is not installed or is not functioning correctly. +2167 Config warning, Flash ROM driver contents lost The contents of the Flash ROM driver area have been corrupted. +2201 Unexpected interrupt from message based card A message based card interrupted when an interrupt service routine has not been set up.
PAGE 257
Table B-3. Start-Up Error Messages and Warnings (continued) Start-Up Error Messages and Warnings Code 256 Message Cause 10 Config error 10, Insufficient system memory Too many instruments installed for the amount of RAM installed in the mainframe. Cannot configure instruments. Only the system instrument is started. 11 Config error 11, Invalid instrument address A device’s logical address is not a multiple of 8 and the device is not part of a combined instrument.
PAGE 258
Table B-3. Start-Up Error Messages and Warnings (continued) Start-Up Error Messages and Warnings Code Appendix B Message Cause 36 Duplicate UDEF memory LADD A logical address is specified more than once in the memory table. This does not apply to VME devices (address = -1). 37 Invalid UDEF CNFG table 38 Invalid UDEF CNFG table data There are more than 254 entries in the commander/servant hierarchy table. 39 Invalid UDEF DC table The valid flag in the dynamic configuration table is not set to 1.
PAGE 259
Table B-3. Start-Up Error Messages and Warnings (continued) Start-Up Error Messages and Warnings Code 258 Message Cause 62 Invalid UDEF extender table data 63 Unsupported UDEF TTL trigger There is an extender table TTL trigger entry for a device which does not support TTL triggers. 64 Unsupported UDEF ECL trigger There is an extender table ECL trigger entry for a device which does not support ECL triggers.
PAGE 260
Appendix C HP E1406A Command Module A16 Address Space About This Appendix Many Hewlett-Packard VXIbus devices are register-based devices which do not support the VXIbus word serial protocol. When an SCPI command is sent to a register-based device, the HP E1406A Command Module parses the command and programs the device at the register level. Register-based programming is a series of reads and writes directly to the device registers. This increases throughput since it eliminates command parsing.
PAGE 261
Register Addressing Register addresses for register-based devices are located in the upper 25% of VXI A16 address space. Every VXI device (up to 256 devices per Command Module) is allocated a 64 byte block of addresses. A device may or may not use the entire block of addresses. Figure C-1 shows the location of A16 address space in the HP E1406A Command Module.
PAGE 262
Appendix D Sending Binary Data Over RS-232 About This Appendix This appendix describes the procedure for sending pure binary data over an RS-232 interface. The formatting described is used in the DIAG:DOWN:CHEC[:MADD], DIAG:DOWN:CHEC:SADD, and DIAG:DRIV:LOAD:CHEC commands. This appendix contains the following main sections. • Formatting Binary Data for RS-232 Transmission . . . . . . . . . Page 261 • Sending Binary Data Over RS-232 . . . . . . . . . . . . . . . . . . . .
PAGE 263
Table D-1. Correction Codes for RS-232 Transmission 262 Data Value Correction Code Byte in Hex Byte in Decimal 0 0 8016 128 1 7 F116 241 2 6 E216 226 3 1 9316 147 4 5 D416 212 5 2 A516 165 6 3 B616 182 7 4 C716 199 8 3 B816 184 9 4 C916 201 10 5 DA16 218 11 2 AB16 171 12 6 EC16 236 13 1 9D16 157 14 0 8E16 142 15 7 FF16 255 Sending Binary Data Over RS-232 Appendix D Artisan Technology Group - Quality Instrumentation ...
PAGE 264
Sending Binary Data Over RS-232 The RS-232 interface differs from the HP-IB interface in that there is no device addressing built into the interface definition. Device addressing must be done on top of the RS-232 functions. This addressing is done through the same mechanism as the terminal-based front panel, and must be done either by the transfer program or manually before starting the transfer program.
PAGE 265
Once the block header has been sent, the actual data is sent. Since the buffer size of the System instrument RS-232 Interface is limited to 79 bytes, the buffer must be flushed (passed to an instrument parser) before it reaches 79 bytes. This can be done by sending a carriage return. The first carriage return should be included in the binary file after the buffer header. Sending it before this would result in the parser determining that there are not enough parameters and producing an error condition.
PAGE 266
Index HP E1406A Command Module User’s Manual *CLS, 105, 217 *DMC, 217 *EMC, 217 *EMC?, 217 *ESE, 108, 114, 217 *ESE?, 106, 108, 218 *ESR?, 108, 218 *GMC?, 218 *IDN?, 218 *LMC?, 219 *LRN?, 219 *OPC, 220 *OPC?, 220 *PMC, 220 *PSC, 220 *PSC?, 220 *RMC, 221 *RST, 105, 221 *SRE, 108, 114, 163, 165, 221 *SRE?, 108, 221 *STB?, 107 - 108, 111 - 112, 114, 222 difference from ireadstb, 107 *TST?, 222 *WAI, 222 A A16 address space, 260 A16/A24/A32 Configuration logical addresses, default, 29 logical addresses, setti
PAGE 267
Base address, 260 Battery backed functions, 20 lifetime expected, 20, 237 Baud Rate query setting, 171 setting, 171 Begin Normal Operation (BNO) Command, 60 Binary Data formatting, 261 sending, 263 - 264 Bits check bits, 128, 130, 159 condition bits, 105 control bits, 128, 130, 159 data bits, 128, 130, 159 device-specific error bit, 250 enable register, 164 error bit, 250 execution error bits, 250 master state summary (MSS), 111 message available (MAV), 112 - 117 parity bits, 176 - 177 query error bit, 251
PAGE 268
downloading data into, 41 errors associated with, 43 linking command module processor, 186 query starting address, 187 table format, 40 Commands abbreviated (SCPI), 120 Begin Normal Operation (BNO), 60 Common (*) Commands, 217 - 222 DIAGnostic subsystem, 123 - 147 executing from terminal interface, 76 HP E1328A menu, 95 HP E1330A/B menu, 96 HP E1332A menu, 97 HP E1333A menu, 99 implied (SCPI), 120 ionsrq, 111 - 112, 114 ireadstb, 107, 111 - 112, 114 iscanf, 112, 114 linking other commands, 122 multimeter me
PAGE 269
reading, 104, 161, 164 standard operation status group, 109 unmasking bit, 163 - 164, 166 Configuration A16/A24/A32 logical address, 29 A24/A32 addresses, 44 - 45, 48 - 51 commander/servant hierarchies, 38 - 39 dynamic configuration, 23 - 26 dynamically configured modules, 22 ECL Trigger register, 30 interrupt line allocation, 53 - 59 interrupt register, 30 INTX interrupt register, 30 logical addresses, 27 - 29 resource manager, with extenders, 47 resource manager, without extenders, 46 statically configure
PAGE 270
Delete Char Key, 78, 85 Delete Line Key, 85 Deleting data from Flash ROM, 160 Descriptions A24/A32 addresses, 44 annunciators, 17 CLK10 connectors, 18 command parameters (SCPI), 121 commander, 38 commands, types of, 119 common (*) commands, 119, 216 dynamically configured modules, 22 extraction levers, 18 functional, 16 HP-IB port, 18 interrupt line allocation, 53 keys (terminal interface), 77 physical, 17 reset button, 18 RS-232 port, 18 run/load switch, 18 SCPI command format, 119 statically configured mo
PAGE 271
DRAM loading instrument driver into, 136 querying drivers in table, 135 DRAM:AVAilable?, 133 DRAM:CREate, 134 DRAM:CREate?, 134 DRIVer:INSTall, 135 DRIVer:LIST :FROM?, 135 :RAM?, 135 :ROM?, 135 DRIVer:LIST?, 135 DRIVer:LOAD, 136 DRIVer:LOAD:CHECked, 136 Drivers available in Flash ROM, 135 creating area for loading, 134 creating Flash ROM driver area, 137 downloading a driver block, 136 listing, 135 loading into DRAM, 136 query number in Flash ROM, 137 query number loaded, 134 DTR See Data Terminal Ready (DT
PAGE 272
query errors, 251 start-up errors, 255 - 258 types of, 250 ESC Key, 64 *ESE, 108, 114, 217 *ESE?, 106, 108, 218 *ESR?, 108, 218 Event Register, 162 - 166 clearing, 111, 218 description, 105 *ESE common command, 217 query set bits, 163, 165 query state, 108, 218 query unmasked bit, 162, 165, 218 reading, 163, 165 reading mask, 162, 165 standard event status group, 108 standard operation status group, 109 unmasking bit, 162 Example Programs assigning an interrupt line, 57 - 58 assigning secondary HP-IB addres
PAGE 273
G General Key Descriptions, 77 GET (Group Execute Trigger), 224 Get Macro Query, 218 *GMC?, 218 Go To Local (GTL), 223 Group Execute Trigger (GET), 224 GTL (Go To Local), 223 H Handling SRQs, 111 - 112 Hierarchy Configuration, 192 - 193 HP E1324A EEROM lifetime, 126 specifying interface card number, 126 storing serial communication settings, 168 HP E1326A/B confirmed SCPI commands, 240 non-SCPI commands, 241 HP E1328A confirmed SCPI commands, 244 menu levels and content, 95 non-SCPI commands, 244 HP E1330A
PAGE 274
line, VXIbus backplane, 54, 138 line, VXIbus backplane, priority level, 139 line, VXIbus backplane, query interrupt acknowledge response, 140 line, VXIbus backplane, query interrupt handling, 141 line, VXIbus backplane, query priority level, 139 line, VXIbus backplane, specifying service routine, 141 register configuration, 30 INTerrupt:ACTivate, 138 INTerrupt:PRIority, 139 INTerrupt:PRIority?, 139 INTerrupt:RESPonse?, 140 INTerrupt:SETup, 141 INTerrupt:SETup?, 141 INTX Interrupt Register configuration, 30
PAGE 275
query, modules installed, 189 - 190, 237 query, modules logical address, 196, 209 query, number of devices, 201 query, number of modules installed, 190 query, static information, 193, 195 Master State Summary (MSS), 107, 111 bit, 111 Memory A16/A24/A32, 29 A24/A32 address mapping, 44 - 45 command module, 20, 237 downloading extender table into, 35 reset configuration, 124 specifications, 237 VMEbus reserved memory location, 30 VXIbus device, 29 windows, user defined, 31 windows, user-defined, 31 Menu contro
PAGE 276
RS-232, 18 trig out, 102 trigger, 102 - 103 Positive error numbers, 250 transitions (PTR), 105 transitions (PTR), setting mask, 164, 166 Power Requirements, 238 Power-on Status Clear Command, 220 Power-on Status Clear Query, 220 PRESet, 164 PROGram Subsystem PROG[:SELected]:DEFine, 157 PROG[:SELected]:DEFine:CHECked, 158 - 159 PROG[:SELected]:DEFine:CHECked?, 160 PROG[:SELected]:DEFine?, 160 PROG[:SELected]:DELete, 160 Programming message-based instruments, 63 status registers, 104 status system, 104 status
PAGE 277
event register state, 108, 218 event register unmasked bits, 162, 165, 218 External Trigger, driving source, 153 External Trigger, logic level, 152 External Trigger, state, 153 Flash ROM drivers in FROM, 135 hierarchy configuration, 192 - 193 input buffer size, 174 - 175 interrupt acknowledge response, 140 interrupt handling, 141 interrupt priority level, 139 logical addresses, 196, 209 modules installed, 189 - 190, 237 modules logical address, 188 non-volatile RAM, areas, 134 non-volatile RAM, current or a
PAGE 278
condition register, 104, 109, 161 - 166 data low register, 53, 60, 201, 215 device register, 260 ECL Trigger register, 30 enable register, 105, 108 - 109, 164, 217 event register, 105, 108 - 109, 111, 162 - 166, 217 event register, clearing, 218 event register, query set bits, 163, 165 event register, query state, 108, 218 event register, query unmasked bits, 162, 165, 218 event register, reading, 163, 165 event register, reading mask, 162, 165 interrupt register, 30 offset, 260 reading A16 address space, 2
PAGE 279
lower case letters, 120 multimeter, 240 numeric parameters, 121 optional parameters, 122 OUTPut commands, 149 - 156 parameter types, 121 PROGram commands, 157 - 160 query version of SCPI, 183 quick reference, 226 reference, 122 separator, 120 square brackets, 120, 122 STATus commands, 161 - 166 subsystem, example of, 119 switchbox, 239 SYST:ERR?, 255 SYSTem commands, 168 - 183 system instrument, 246 upper case letters, 120 VXI commands, 184 - 215 word serial commands, 213 - 215 SDC (Selected Device Clear),
PAGE 280
operation status group, 106, 109 Start of Line Key, 85 Start-up Error Messages, 255 - 258 Starting System Operation, 60 Static electricity, 15 information, 193, 195 Statically Configured Modules, 22 logical address, 22 Status byte, bits, 108 byte, enable registers, 108 byte, group, 106 - 107 byte, query register, 222 byte, reading, 107, 111 byte, register, 108, 162, 165 byte, summary bit, 107 enable register command, 217 enable register query, 218 event register query, 218 group, description of, 104 group,
PAGE 281
SYST:COMM:SER[:REC]:PAR?, 177 SYST:COMM:SER[:REC]:SBIT, 178 SYST:COMM:SER[:REC]:SBIT?, 179 SYST:COMM:SER:TRAN:AUTO, 179 SYST:COMM:SER:TRAN:AUTO?, 179 SYST:COMM:SER:TRAN:PACE[:PROT], 180 SYST:COMM:SER:TRAN:PACE[:PROT]?, 180 SYST:DATE, 181 SYST:DATE?, 181 SYST:ERR?, 182, 249, 255 SYST:TIME, 182 SYST:TIME?, 183 SYST:VERS?, 183 extender table, example of, 34 extender table, linking command module processor, 191 extender table, query starting address, 191 extender table, table record, 32 extender table, table s
PAGE 282
unsupported terminals, 82 using terminals without menus, 83 Terminals HP 700/22, 79 - 81 supported, 79 testing for compatibility, 82 unsupported, 82 using without menus, 83 WYSE WY-30, 81 TIME, 182 TIME?, 183 Transition Filter, 105 Transmit Pacing Mode, 179 query state of receive, 179 Transmit Pacing Protocol enabling/disabling, 180 query current setting, 180 Trig In, 18 connector driving ECL Trigger, 150 connector driving TTL Trigger, 155 Trig Out, 18 enabling, 102 port, enabling configuration, 153 port, l
PAGE 283
service request (SRQ), 114 SRQ to detect errors, 114 supported terminals, 79 switchbox menu, 72 system instrument menu, 65 terminals without menus, 83 unsupported terminals, 82 Utility Register Configuration, 31 UTILS Key, 65 V Variable SCPI Command Syntax, 121 VERSion?, 183 VMEbus address space, 45 allocating address space, 45 interrupt lines, 54 logical addresses, 29 reserved memory location, 30 reserving A24/A32 address space, 48 reserving A24/A32 addresses, 48 - 51 VT100 key map, 79 mode, 80 VT220 key
PAGE 284
WRITe, 212 Writing data to non-volatile RAM, 127 - 132 into Flash ROM, 157 into Flash ROM, over RS-232 line, 158 - 159 to a device register, 260 to registers, 205, 212 WSProtocol:COMMand, 213 WSProtocol:MESSage:RECeive?, 214 WSProtocol:MESSage:SEND, 214 WSProtocol:QUERy?, 215 WSProtocol:RESPonse?, 215 WYSE WY-30 Key Map, 81 X XON/XOFF Protocol, 173, 180 HP E1406A Command Module User’s Manual Index Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.
PAGE 285
Artisan Technology Group is your source for quality new and certified-used/pre-owned equipment • FAST SHIPPING AND DELIVERY • TENS OF THOUSANDS OF IN-STOCK ITEMS • EQUIPMENT DEMOS • HUNDREDS OF MANUFACTURERS SUPPORTED • LEASING/MONTHLY RENTALS • ITAR CERTIFIED SECURE ASSET SOLUTIONS SERVICE CENTER REPAIRS Experienced engineers and technicians on staff at our full-service, in-house repair center WE BUY USED EQUIPMENT Sell your excess, underutilized, and idle used equipment We also offer credit for buy-back