Page 1 Mainframes E1300B and E1301B User’s Manual Copyright © Agilent Technologies, Inc., 1989, 1990, 1991, 2006 Manual Part Number: E1300-90005 Microfiche Part Number: E1300-99005 75000 SERIES B Printed: February 2006 Edition 3 Printed in U.S.A. E 0206...
Page 3 Warranty This Agilent Technologies product is warranted against defects in materials and workmanship for a period of three years from date of shipment. Duration and conditions of warranty for this product may be superseded when the product is integrated into (becomes a part of) other Agilent products.
Page 4: Safety Symbols
REMOVE POWER and do not use the product until safe operation can be verified by service-trained personnel. If necessary, return the product to an Agilent Technologies Sales and Serv- ice Office for service and repair to ensure that safety features are maintained.
Page 5 Low Voltage Directive 73/23/EEC and the EMC Directive 89/336/EEC and carries the "CE" marking accordingly. May 7, 2001 European contact: Your local Agilent Technologies Sales and Service Office or Agilent Technologies GmbH, Department HQ-TRE, Herrenberger Straße 130, D-71034 Böblingen, Germany (FAX +49-7031-14-3143).
Page 6 This guide also contains introductory programming information and examples. Agilent E1300B/E1301B Mainframe User’s Manual. Contains programming information for the mainframe, front panel operation information (for the Agilent E1301B mainframe), and general programming information for instruments installed in the mainframe.
Page 7 Related Documents Agilent Instrument BASIC User’s Handbook. Includes three books: Agilent Instrument BASIC Programming Techniques , Agilent Instrument BASIC Interfacing Techniques, and Agilent Instrument BASIC Language Reference. Using Agilent Instrument BASIC with the E1405. Contains information on the version of Agilent Instrument Basic which can be installed in ROM in your E1405B Command Module.
Page 8: About This Manual
Manual Content Chapter 1: Getting Started Chapter 2: Using the Front Panel Chapter 3: Using the Display Terminal Interface Chapter 4: Using the Mainframe Chapter 5: Downloading Device Drivers Chapter 6: Controlling Instruments using GPIB Chapter 7: Command Reference Appendix A: Specification Appendix B: Error Messages Appendix C: Connecting &...
Page 9: Table Of Contents
1. Getting Started Using This Chapter ........1-1 Mainframe Description .
Page 10 Using Supported Terminals ....... . 3-16 The Supported Terminals ....... . 3-16 Using the HP 700/22 .
Page 11 The Service Request Bit ....... . . 6-5 Clearing the Service Request Enable Register ....6-5 Standard Event Status Register .
Page 12 *SRE < mask> *SRE? ......... . . 7-71 *STB? .
Page 13 C. Connecting and Configuring a Display Terminal Using this Appendix ........C-1 Overview .
Page 14: Table Of
6 - Table of Contents...
Page 15: Getting Started
Introductory Programming Examples ....1-4 The Agilent E1301B mainframe contains a front panel keyboard and display; the Agilent E1300B has no keyboard or display. Otherwise, there is no conceptual difference between the two mainframes. Both models provide a terminal based user interface (Display Terminal Interface) through the built-in, or optional plug-in serial interfaces.
Page 16 GPIB Trig Out: Allows an instrument to output a negative-going pulse to indicate the occurrence of some event such as closing a channel on a Switchbox Instrument. The signal levels are standard TTL (0V to 5V). This pulse can be used to synchronize external equipment to the instrument (see Chapter 5 for examples).
Page 17: Instrument Definition
Instrument Definition SCPI-compatible plug-in modules installed in the mainframe are treated as independent instruments each having a unique secondary GPIB address. As shown in Figure 1-3, each instrument is assigned a dedicated error queue, input and output buffers, status registers and, if applicable, dedicated mainframe memory space for readings or data.
Page 18: Instrument Logical Addresses
GPIB. (The System Instrument’s secondary address is 00 and is the only address that cannot be changed). An unassigned module in an E1300B/E1301B Mainframe is one that does not have a logical address that is a multiple of 8 (8, 16, 24...240) and is not part of a Scanning Voltmeter or Switchbox configuration.
Page 19 Example: Reading the Time Example: Setting the Time Example: Reading the Date Example: Setting the Date This program reads and prints the time from the System Instrument’s internal clock. The computer used in the example is an Agilent Series 200/300 computer with Agilent BASIC as the program language.
Page 20 Getting Started...
Page 21: Using The Front Panel
Using this Chapter Front Panel Features 2-Line X 40 Character Display Agilent Using the Front Panel This chapter shows you how to use the Agilent E1301B Mainframe’s front panel keyboard and display to operate instruments in the mainframe. It contains the following sections: Front Panel Features .
Page 22: Using Menus
Using Menus A 60-Second Menu Tutorial 2-2 Using the Front Panel You can access a System Instrument menu and a variety of other instrument menus (depending on installed instruments) from the front panel. These menus incorporate the most used functions but do not provide access to all of the instrument commands.
Page 23: Using The System Instrument Menu
Press Prev Menu to return to the previous menu within an instrument menu or escape from an input prompt. Press Select Instr to return to the Select an Instrument menu. Note that when you leave an instrument and return later, you return to the same menu location you were when you left.
Page 24 How to Reset the System GPIB Note: The RESET menu selection is equivalent to the DIAG:BOOT command which has the same effect as cycling power to the mainframe. Pressing Reset Instr from the System Instrument menu is equivalent to executing the *RST command which resets the System Instrument. How to Display Logical Addresses or Instrument Information GPIB 2-4 Using the Front Panel...
Page 25: Using The Other Instrument Menus
Using the Other The instrument menus allow you to access the most-used instrument functions or to monitor an instrument (monitor mode) while it is being controlled from Instrument Menus remote. We’ll use the Switchbox menu to show you how to use the instrument menus.
Page 26 How to Open/Close Channels How to Scan Channels 2-6 Using the Front Panel...
Page 27 How to Display Monitor Type, Description, or Reset Module How to Select Monitor Mode Using the Front Panel 2-7...
Page 28: Monitor Mode
Monitor Mode Note Reading Error Messages 2-8 Using the Front Panel 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 front panel menus, or by executing the DISP:MON:STAT ON command from the front panel or by remote.
Page 29: Executing Commands
Executing Commands Editing From the front panel, you can type and execute IEEE 488.2 Common Commands and SCPI Commands for the instrument presently selected by the Select an instrument menu. (However, you cannot execute a command when the display is requesting that you input information.) This is particularly useful for accessing functions not available in an instrument’s menu.
Page 30: Key Descriptions
Key Descriptions Menu Keys Display Control & Editing Keys 2-10 Using the Front Panel This section explains the function of each of the front panel’s dedicated keys. If a key is not functional in a particular situation, pressing that key does nothing except to cause a beep.
Page 31: Instrument Control Keys
the cursor to the beginning of the line. Pressing CTRL followed by the left arrow key moves the cursor 4 character spaces to the left. Erases the character at the present cursor position (for user-entered data only). Erases the character to the left of the cursor (for user-entered data only). (Clear-to-end key.) Erases all characters from the present cursor position to the end of the input line (for user-entered data only).
Page 32: In Case Of Difficulty
In Case of Difficulty Problem: Error -113 undefined header error occurs after entering data in response to a menu prompt. Following the power-on sequence or system reset the display shows: Configuration errors. Select SYSTEM Press any key to continue_ The display shows: "instrument in local lockout". Menus seem to work but nothing happens when I reach the bottom level or try to execute a command.
Page 33: Instrument Menus
Instrument Menus This section contains charts showing the structure and content for all front panel instrument menus. Also shown in the charts are the SCPI or Common Commands used and descriptions of menu-controlled instrument operations. This section contains the following charts: System Instrument Menu.
Page 34 2-14 Using the Display Terminal Interface...
Page 35 Using the Display Terminal Interface 2-15...
Page 36 2-16 Using the Display Terminal Interface...
Page 37 Notes Using the Front Panel 2-17...
Page 38 2-18 Using the Display Terminal Interface...
Page 39 Using the Display Terminal Interface 2-19...
Page 40 2-20 Using the Display Terminal Interface...
Page 41 Using the Display Terminal Interface 2-21...
Page 42 2-22 Using the Display Terminal Interface...
Page 43 Notes Using the Front Panel 2-23...
Page 44 2-24 Using the Display Terminal Interface...
Page 45 Using the Display Terminal Interface 2-25...
Page 46 2-26 Using the Display Terminal Interface...
Page 47 Using the Display Terminal Interface 2-27...
Page 48 Notes 2-28 Using the Front Panel...
Page 49: Using The Display Terminal Interface
Using the Display Terminal Interface Using this Chapter Note This chapter shows you how to use the Agilent E1300B and Agilent E1301B Mainframes’ Display Terminal Interface (terminal interface) to operate instruments in the mainframe. The terminal interface uses the built-in RS-232 and/or the optional Agilent E1324A Datacomm Module to provide all of the features of the Agilent E1301B’s front panel, plus comfortable keyboard...
Page 50: Terminal Interface Features
Terminal Interface Features Notes: 3-2 Using the Display Terminal Interface Figure 3-2 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.
Page 51: Using Menus
Using Menus Note: Typical instruments shown. Actual choices depend on installed instrument A 60-Second Menu Tutorial A System Instrument menu and a variety of other instrument menus (depending on installed instruments) are available from the terminal interface. These menus incorporate the most used functions but do not provide access to the complete functionality of an instrument.
Page 52 3-4 Using the Display Terminal Interface If you make an incorrect entry in response to an input prompt, the bottom line of the Text Output Area will show an error message. When this happens, just select that menu choice again (f1 - f5 keys), re-type the correct information, and press Return.
Page 53: Using The System Instrument Menu
Using the System The System Instrument menu allows you to: Instrument Menu How to Set or Read the System GPIB Address SCPI command used: SYST:COMM:GPIB:ADDR? Set or read the system GPIB address Reset (reboot) the mainframe Display the logical addresses of installed instruments Display information about installed instruments Enter new GPIB address, press Return (range= 1 through 30)
Page 54 How to Reset the System Press f1 to Reset Note: The RESET menu selection is equivalent to executing the DIAG:BOOT command which has the same effect as cycling the mainframe’s power. Pressing RST_INST from the System Instrument menu is the equivalent to sending the * RST command to the System Instrument.
Page 55 How to Display Logical Addresses and Instrument Information Logical address of selected device Note: For a description of each field of the instrument information, see VXI:CONF:DLIS? in the SCPI Command Reference section. Enter device’s logical address and press Return for individual instrument information, or just enter one space and Return, for information on all intruments.
Page 56: Using The Other Instrument Menus
Using the Other Instrument Menus Selecting the Switchbox Note 3-8 Using the Display Terminal Interface The instrument menus allow you to access the most-used instrument functions or to monitor an instrument (monitor mode) while it is being controlled from remote. We’ll use the Switchbox menu to show you how to use the instrument menus.
Page 57 How to Open/Close Channels SCPI command used: OPEN < channel_list> Enter Channel List and press Return (e.g., 100:115 to scan channels 00 to 15 on cardd # 1) Switchbox instrument at logical address 32 (secondary address = 04) Enter Channel List and press Return (e.g., 102 for channel 2 on card # 1) How to Scan Channels Press f2 to advance to the next channel in...
Page 58 How to Display Module Type , Description, or Reset Module Enter Card Number and press Return SCPI command used: SYST:CTYP? < card_number> 3-10 Using the Display Terminal Interface Enter Card Number and press Return SCPI command used: SYST:CPON < card_number> Enter Card Number and press Return SCPI command used: SYST:CDES? <...
Page 59: Monitor Mode
How to Select Monitor Mode Enter Card Number or type AUTO and press Return SCPI commands used: DISP:MON:CARD < card_number> DISP:MON:STAT ON Monitor Mode 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.
Page 60 Note Reading Error Messages 3-12 Using the Display Terminal Interface Enabling monitor mode slows instrument operations. If the timing or speed of instrument operations is critical (such as making multimeter readings at a precise time interval), you should not use monitor mode. Table 3-1 shows the status annunciators that may appear in the bottom line of the screen in monitor mode.
Page 61: Executing Commands
Executing Commands Editing Note From the terminal interface, you can type and execute IEEE 488.2 Common Commands and SCPI Commands for the instrument presently selected by the Select an instrument menu. (However, you cannot execute a command when the screen is requesting that you input information.) This is particularly useful for accessing functions not available in an instrument’s menu.
Page 62: General Key Descriptions
General Key Descriptions Menu and Menu Control Keys through UTILS SEL_INST PRV_MENU MORE UTILS RCL_PREV UTILS RCL_NEXT UTILS RCL_MENU Editing Keys 3-14 Using the Display Terminal Interface This section explains the function of each of the terminal interface’s menu, menu control, and editing keys.
Page 63: Instrument Control Keys
Erases the character to the left of the cursor (for user-entered data only). (Clear-to-end key.) Erases all characters from the present cursor position to the end of the input line (for user-entered data only). Selects the upper-case alphabetic characters or the character shown on the top half of a key.
Page 64: Using Supported Terminals
Using Supported Terminals The Supported Terminals 3-16 Using the Display Terminal Interface 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 following list names the supported terminals and shows where to go for more information.
Page 65: Using The Hp 700/22
Using the HP 700/22 The HP 700/22 terminal emulates the DEC Some functions of the Display Terminal Interface have been mapped into keys with other labels. A keyboard map is provided for each of the emulation models. Use these keyboard maps to help locate the terminal interface functions. ®...
Page 66 ® VT220 Key Map Note ® Selecting VT220 Mode 3-18 Using the Display Terminal Interface 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 The symbols shown in the upper left corner of key each are now mapped with the function labeled in the center of each key.
Page 67: Using Other Terminals
Using the WYSE WY-30 Using Other Terminals 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. The symbols shown in the upper left corner of key each are now mapped with the function labeled in the center of each key.
Page 68: What "Not Supported" Means
What “Not Supported” Means Testing Terminals for Compatibility NOTE 3-20 Using the Display Terminal Interface Strictly speaking, a terminal is not supported if it has not been rigorously tested with the Display Terminal Interface. There are several HP terminals which may be compatible with the terminal interface.
Page 69: Using A Terminal Without Menus
Using a Terminal You can still control instruments installed in your mainframe without using the terminal interface menus. In this case you will send Common Commands and Without Menus SCPI commands to your instruments by typing them on your terminal keyboard, or through a computer interface.
Page 70 Returning to the “Select an Instrument” Prompt Control Sequences for Terminal Interface Functions 3-22 Using the Display Terminal Interface To get a list of the logical addresses used in your mainframe, send the SCPI command VXI:CONF:DLAD? to the System Instrument. Then to determine what instrument is at each logical address, send the command VXI:CONF:DLIS? n for each logical address in the list (where n is a logical address).
Page 71: In Case Of Difficulty
In Case of Difficulty Problem: Error -113 undefined header error occurs after entering data in response to a menu prompt. Following the power-on sequence or system reset the display shows: Configuration errors. Select SYSTEM Press any key to continue_ The display shows: "instrument in local lockout". Menus seem to work but nothing happens when I reach the bottom level or try to execute a command.
Page 72 Notes 3-24 Using the Display Terminal Interface...
Page 73: Instrument Menus
Instrument Menus This section contains charts showing the structure and content for all terminal interface instrument menus. Also shown in the charts are the SCPI or Common Commands used and descriptions of menu-controlled instrument operations. This section contains the following charts: System Instrument Menu.
Page 74 3-26 Using the Display Terminal Interface...
Page 75 Using the Display Terminal Interface 3-27...
Page 76 3-28 Using the Display Terminal Interface...
Page 77 Notes Using the Display Terminal Interface 3-29...
Page 78 3-30 Using the Display Terminal Interface...
Page 79 Using the Display Terminal Interface 3-31...
Page 80 3-32 Using the Display Terminal Interface...
Page 81 Using the Display Terminal Interface 3-33...
Page 82 3-34 Using the Display Terminal Interface...
Page 83 Notes Using the Display Terminal Interface 3-35...
Page 84 3-36 Using the Display Terminal Interface...
Page 85 Using the Display Terminal Interface 3-37...
Page 86 3-38 Using the Display Terminal Interface...
Page 87 Using the Display Terminal Interface 3-39...
Page 88 Notes 3-40 Using the Display Terminal Interface...
Page 89: Using The Mainframe
Using this Chapter Using the Pacer Using the Mainframe This chapter shows how to use the mainframe’s Pacer function, how to change the primary GPIB address, and how to synchronize internal and external instruments using the mainframe’s Event In and Trigger Out ports. This chapter also discusses how mainframe memory is used by installed instruments.
Page 90 Pacer Trigger States Using the Mainframe SOUR:PULS:COUN sets the number of Pacer cycles. Specify from 1 to 8388607 cycles or specify INF for a continuous output. SOUR:PULS:PER sets the period of each Pacer cycle. You can specify periods from 500ns to 8.3 seconds. TRIG:SOUR sets the trigger source.
Page 91: Changing The Primary Gpib Address
Changing the Primary GPIB Address Synchronizing Internal and External Instruments Figure 4-2. Pacer Trigger States You can set the mainframe’s primary GPIB address to any integer value between 0 and 30. The address is set to 9 at the factory. (See Chapter 2 for instructions on setting/reading the GPIB address from the front panel.) The following command sets the mainframe’s primary GPIB address to 12.
Page 92 Using the Mainframe Example: Synchronizing an Internal Instrument to an External Instrument This example uses the mainframe’s Trig Out and Event In ports to synchronize an external multimeter to a multiplexer installed in the mainframe. Connections are shown in Figure 4-3. The multimeter’s Voltmeter Complete port outputs a pulse whenever the multimeter has finished a reading.
Page 93 multimeter to an internal multiplexer. Connections are shown in Figure 4-4. This method synchronizes the computer to the instruments and relies on the computer to enter each reading and advance to the next channel in the scan list. The sequence of operation is: 1.
Page 94: Mainframe Data Memory
Figure 4-4. Synchronizing Internal/External Instruments and Computer Mainframe Data Memory Using Mainframe Data Memory Using the Mainframe When power is applied or the system rebooted (DIAG:BOOT command), mainframe memory is automatically configured to provide a predefined amount of memory for any installed instruments that require memory space. For example, each multimeter instrument within the mainframe is allocated enough memory to store 100 readings.
Page 95: Non-Volatile User Memory
Non-Volatile User Memory Allocating a User Memory Segment Note: IBASIC Users Locating the NRAM segment Example: Storing and Retrieving Data From Mainframe Memory. This example shows how to use mainframe memory to store 15 readings made using an Agilent E1326A Multimeter. After the readings are stored, they are retrieved by the computer and displayed.
Page 96 Using the Mainframe address. You will then know the starting address , and (from the NRAM:CRE < size> command) the length of the NRAM segment. Example: Allocating an NRAM segment and locating it. This example shows how to allocate a small 128 byte NRAM segment. In addition, it shows how to determine the starting address of that segment.
Page 97: Using :Download And :Upload? To Access Data
Using :DOWNload and :UPload? to Access Data Caution Data Formats for :DOWNload The command DIAG:DOWNload < address> ,< data_block> is used to store data into the NRAM segment. The command DIAG:UPLoad? < address> ,< byte_count> is used to retrieve data from the NRAM segment.
Page 98 4-10 Using the Mainframe Example: Storing and Retrieving data using DOWNload and UPLoad. define variables for DOWNload and UPLoad 90 DIM Chars$[64],Chars_back$[80] 100 INTEGER Words(1:16),Bytes(1:32),Words_back(1:16), Bytes_back(1:32) create string of characters 110 Chars$= "1234567890123456789012345678901234567890 123456789012345678901234" create array of 16 bit data words 120 FOR I= 1 TO 16 Words(I)= 32700+ I 140 NEXT I...
Page 99: About This Chapter
About this Chapter What You Will Need Downloading Device Drivers This chapter describes the procedure for using downloadable device drivers with the Agilent E1405 Command Module. This functionality was added so that SCPI capability for new register based devices could be added to the Command Module without having to update an internal set of ROMs.
Page 100 GPIB bus GPIB bus GPIB bus GPIB Figure 5-1. Driver and Documentation Usage 5-2 Downloading Device Drivers...
Page 101: Memory Configuration
Memory Configuration NOTE Example Before attempting to download any device drivers you should understand how memory is affected when you specify a size for one or more types of RAM. There are three types of RAM that you can allocate in the mainframe: RAM disk (RDISK) Non-volatile RAM (NRAM) Driver RAM (DRAM)
Page 102: Download Program Configuration
Download Program Configuration Editing the Configuration File 5-4 Downloading Device Drivers If you will not be using the default configurations for downloading, you will need to edit the configuration file to match your system configuration. If the default values shown below are correct for your setup, you can proceed to the appropriate downloading instructions.
Page 103 specify a file name here, the driver downloader will log to the screen and to the specified file. DRIVER FILE = specifies the driver file or files to download. The default is to download all device driver files found in the directory specified by DIRECTORY = .
Page 104: Downloading Drivers In Ms-Dos Systems
Downloading Drivers in MS-DOS Systems WARNING 5-6 Downloading Device Drivers The device driver download program VXIDLD.EXE provided on the disk with the driver files for use with an RS-232 interface must be run from MS-DOS. It will set up the the required device driver memory and any other memory partitions defined in the configuration file, reboot the system, and download the device driver.
Page 105: Downloading Drivers In Gpib Systems With Ibasic
Downloading Drivers in GPIB Systems with IBASIC NOTE NOTE The device driver download program AUTOST provided on the disk with the driver files for use with GPIB must be run from IBASIC (Instrument Basic). It will set up the the required device driver memory and any other memory partitions defined in the configuration file, reboot the system, and download the device driver.
Page 106: Downloading Drivers In Gpib Systems With Basic
Downloading Drivers in GPIB Systems with BASIC 5-8 Downloading Device Drivers The device driver download program VXIDLD_GET provided on the disk with the driver files for use with GPIB must be run from an BASIC other than IBASIC. It will set up the the required device driver memory and any other memory partitions defined in the configuration file, reboot the system, and download the device driver.
Page 107: Downloading Multiple Drivers
Downloading Multiple Drivers Checking Driver Status The driver downloader software automatically checks for the existence of other drivers when it is run. If there are device drivers present, it will abort the process and inform you that you must first clear the other device drivers out of the mainframe and then download all of the required drivers at once.
Page 108: Manually Downloading A Driverdown Manual
Manually Downloading a Driverdown manual Preparing Memory for Manual Downloading NOTE WARNING 5-10 Downloading Device Drivers Download programs are supplied for use with the system setups described earlier in this chapter. If you have a system setup that does not allow the use of one of the supplied download programs (for instance, if you are using a Macintosh®...
Page 109: Manually Downloading Over Gpib
Manually Downloading Over GPIB Manually Downloading Over RS-232 Transmission Format Manually downloading a driver over GPIB is fairly straightforward. This discussion assumes that the downloadable device driver has been supplied by Agilent. Drivers supplied by Agilent are formatted so that you just need to transfer the driver to command module memory.
Page 110 NOTE Pacing the Data 5-12 Downloading Device Drivers If you are going to use any other setting, you must set up the appropriate settings in the System Instrument using the following commands COMM:SER[n]:REC:BAUD < rate> COMM:SER[n]:REC:SBITS < bits> DIAG:COMM STOR Because the special formatting for binary files uses all 8 bits, the number of data bits must be set to 8 and parity checking must remain OFF for the driver files to transfer properly.
Page 111 NOTE CAUTION Transmitting Using a COPY Command NOTE handshake mode is enabled, the System Instrument will not transmit characters when either the CTS (Clear to Send) or the DSR (Data Set Ready) lines are not asserted. This acts to pace the System Instrument output. The E1405 Command Module RS-232 interface is implemented as a DTE (Data Terminating Equipment).
Page 112 Transmitting Using a CAT Command Transmitting Using Custom Software Check Driver Status 5-14 Downloading Device Drivers On HP-UX systems you can use the cat command to transfer the device driver. The appropriate device file must exist. All shell commands are assumed to be executed from either the /bin/sh or /bin/ksh shell.
Page 113 Figure 5-3. Manually Downloading a Device Driver Downloading Device Drivers 5-15...
Page 114 5-16 Downloading Device Drivers...
Page 115: Controlling Instruments Using Gpib
Controlling Instruments Using GPIB About this Chapter Note Programming Hints This chapter shows how to control instruments in the mainframe from an external computer using IEEE 488.2 Common Commands and the GPIB interface. This includes how to monitor instrument status, interrupt the computer, and synchronize one or more instruments to an external computer.
Page 116: Status System Structure
Status System Structure NOTE 6-2 Controlling Instruments Using GPIB The instrument status structure monitors important events for an instrument such as when an error occurs or when a reading is available. All instruments have the following status groups and registers within those groups: Status Byte Status Group –...
Page 117: The Status Byte Register
The Status Byte As shown in Figure 4-1, the Status Byte register is the highest-level register in the status structure. This register contains bits which summarize information Register from the other status groups. NOTE The bits in the other status group registers must be specifically enabled to be reported in the Status Byte register.
Page 118: Reading The Status Byte Register
Reading the Status Byte Register 6-4 Controlling Instruments Using GPIB Table 4-1 shows each of the Status Byte register bits and describes the event that will set each bit. Table 4-1. Status Byte Register Decimal Number Weight Description Instrument Specific (not used by most instruments) Instrument Specific (not used by most instruments) Instrument Specific (not used by most instruments) Questionable Data Status Group Summary Bit.
Page 119: Service Request Enable Register
The following program reads the system instrument’s Status Byte register using the GPIB Serial Poll command. Service Request The Service Request Enable register is used to "unmask" bits in the Status Byte register. When an unmasked Status Byte register bit is set to ’1’, a service Enable Register request is sent to the computer over GPIB.
Page 120: Standard Event Status Register
Standard Event Status Register NOTE Unmasking Standard Event Status Bits 6-6 Controlling Instruments Using GPIB The Standard Event Status Register in the Standard Event status group monitors the instrument status events shown in Table 4-2. When one of these events occurs, it sets a corresponding bit in the Standard Event Status Register. The Standard Event Status Register bits are not reported in the Status Byte Register unless unmasked by the Standard Event Status Enable Register.
Page 121: Reading The Standard Event Status Enable Register Mask
Reading the Standard Event Status Enable Register Mask Reading the Standard Event Status Register Operation Status Group NOTE unmasked, an GPIB service request (SRQ) will be generated. ("Interrupting the External Computer", later in this chapter contains an example program which demonstrates this sequence).
Page 122: Reading The Condition Register
Reading the Condition Register Unmasking the Operation Event Register Bits 6-8 Controlling Instruments Using GPIB Table 4-3. Operation Status Group - Condition Register Decimal Number Weight Description Calibrating Settling Ranging Sweeping Measuring Waiting for TRG Waiting for ARM Correcting Interrupt acknowledged (System Instrument) 9-12 Instrument Dependent 13-14...
Page 123: Clearing The Operation Event Register Bits
Clearing the Operation Event Register Bits Using the Operation Status Group Registers NOTE Bits in the Operation Status Group Event register which are set can be determined with the command: STATus:OPERation:EVENt? This command returns the decimal weighted sum of the set bit(s). Bits in the Operation Status Group Event register are cleared with the command: STATus:OPERation:EVENt?
Page 124: Clearing Status
Clearing Status Interrupting an External Computer NOTE 6-10 Controlling Instruments Using GPIB SUB Intr_resp B= SPOLL(70900) OUTPUT 70900; "STAT:OPER:EVEN?" ENTER 70900; E OUTPUT 70900; "DIAG:INTR:RESP?" ENTER 70900; R SUBEND The *CLS command clears all status registers (Standard Event Status Register, Standard Operation Status Event Register, Questionable Data Status Event Register) and the error queue for an instrument.
Page 125 Example: Interrupting when an Error Occurs This program shows how to interrupt an external computer whenever an error occurs for the instrument being programmed which, in this example, is a multimeter at secondary address 03. 10 OPTION BASE 1 20 ON INTR 7 CALL Errmsg !When SRQ occurs on interface 7, call subprogram 30 ENABLE INTR 7;2 !Enable SRQ interrupt, interface 7...
Page 126: Synchronizing An External Computer And Instruments
Synchronizing an External Computer and Instruments 6-12 Controlling Instruments Using GPIB The *OPC? and *OPC commands (operation complete commands) allow you to maintain synchronization between an external computer and an instrument. The *OPC? query places an ASCII character 1 into the instrument’s output queue when all pending instrument operations are finished.
Page 127 Example: Synchronizing an External Computer and Two Instruments using the * OPC command. This example uses the *OPC command and serial poll to synchronize an external computer and two instruments (DAC at secondary address 09; Scanning Voltmeter at secondary address 03). The advantage to using this method over *OPC? query method is that the computer can do other operations while it is waiting for the instrument(s) to complete operations.
Page 128 6-14 Controlling Instruments Using GPIB...
Page 129: System Instrument Command Reference
System Instrument Command Reference About This Chapter Command Types Common Command Format SCPI Command Format This chapter describes the Standard Commands for Programmable Instruments (SCPI) command set and the IEEE 488.2 Common Commands for the System Instrument. The System Instrument is part of the Agilent E1300/E1301 Mainframe’s internal control processor and is therefore always present in a Mainframe.
Page 130 Command Separator Abbreviated Commands Implied Commands Variable Command Syntax Parameters 7-2 System Instrument Command Reference A colon (:) always separates one command from the next lower level command as shown below: ROUTe:SCAN:MODE? Colons separate the root command from the second level command (ROUTe:SCAN) and the second level from the third level (SCAN:MODE?).
Page 131: Linking Commands
Optional Parameters. Parameters shown within square brackets ([ ]) are optional parameters. (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? [<...
Page 132: Scpi Command Reference
ABORt SCPI Command Reference ABORt Subsystem Syntax Comments Example 7-4 System Instrument Command Reference This section describes the SCPI commands for the System Instrument. Commands are listed alphabetically by subsystem and also within each subsystem. A command guide is printed in the top margin of each page. The guide indicates the first command listed on that page.
Page 133: Diagnostic
DIAGnostic Subsystem Syntax The DIAGnostic subsystem allows control over the System Instrument’s internal processor system (:BOOT, and :INTerrupt), the allocation and contents of User RAM, and, disc volume RAM (:NRAM, and :RDISk), and allocation of the built-in serial interface (:COMM:SER:OWNer). DIAGnostic :BOOT :COLD...
Page 134 DIAGnostic:BOOT:COLD :BOOT:COLD NOTE Comments Example 7-6 System Instrument Command Reference DIAGnostic:BOOT:COLD causes the System Instrument to restart (re-boot). Configurations stored in non-volatile memory and RS-232 configurations are reset to their default states: DRAM, NRAM, and RDISk memory segments are cleared Serial Interface parameters set to: –...
Page 135 :BOOT[:WARM] DIAGnostic:BOOT[:WARM] causes the System Instrument to restart (re-boot) using the current configuration stored in non-volatile memory. The effect is the same as cycling power. Comments Example Booting the System Instrument (warm) :COMMunicate DIAGnostic:COMMunicate:SERial[0][:OWNer] < owner > Allocates the built-in serial interface to the System Instrument, the optional IBASIC :SERial[0][:OWNer] interpreter, or to neither.
Page 136 DIAGnostic:COMMunicate :SERial[0][:OWNer]? :COMMunicate :SERial[0][:OWNer]? Comments Example :COMMunicate :SERial[n]:STORe Comments Example 7-8 System Instrument Command Reference 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: DIAGnostic:SERial[:OWNer] Determine which instrument has the serial interface. DIAG:COMM:SER? enter statement DIAGnostic:COMMunicate:SERial[n]:STORe Stores the serial...
Page 137 :DOWNload:CHECked DIAGnostic:CHECked:DOWNload[:MADDress] < address> ,< data> writes data into a non-volatile User RAM segment starting at address using error [:MADDress] correction. The User RAM segment is allocated by the DIAG:NRAM:CREate or DIAG:DRAM:CREate command. Parameters Comments DIAGnostic :DOWNload:CHECked [:MADDress] Parameter Parameter Name Type address...
Page 138 DIAGnostic:DOWNload:CHECked [:MADDress] Byte Format 7-10 System Instrument Command Reference Each byte sent with this command is expected to be in the following format: Bit # Control Bit Check Bits Control Bit is used to indicate the serial driver information such as clear, reset, or end of transmission.
Page 139 :DOWNload:CHECked DIAGnostic:CHECked:DOWNload:SADDress < address> ,< data> writes data to non-volatile User RAM at a single address specified by address using error :SADDress correction. It can also write to devices with registers in the A16 address space. Parameters Comments DIAGnostic :DOWNload:CHECked :SADDress Parameter Parameter Name...
Page 140 DIAGnostic:DOWNload:CHECked :SADDress Byte Format 7-12 System Instrument Command Reference Each byte sent with this command is expected to be in the following format: Bit # Control Bit Check Bits Control Bit is used to indicate the serial driver information such as clear, reset, or end of transmission.
Page 141 :DOWNload DIAGnostic:DOWNload[:MADDress] < address> ,< data> writes data into a non-volatile User RAM segment starting at address. The User RAM segment is [:MADDress] allocated by the DIAG:NRAM:CREate command. Parameters Parameter Name address data Comments CAUTION: Be certain that all of the data you download will be contained entirely within the allocated NRAM segment.
Page 142 DIAGnostic:DOWNload:SADDress Example :DOWNload:SADDress Parameters Comments 7-14 System Instrument Command Reference Loading Dynamic Configuration information into an allocated RAM segment. DIAG:NRAM:CRE 6 DIAG:BOOT:WARM DIAG:NRAM:ADDR? enter value to variable X DIAG:DOWN < value of X> ,table data download table data VXI:CONF:DCTAB < value of X> DIAG:BOOT:WARM DIAGnostic:DOWNload:SADDress <...
Page 143 Example Downloading 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. :DRAM:AVAilable? DIAGnostic:DRAM:AVAilable? Returns the amount of RAM remaining (available) in the DRAM (Driver RAM) segment, which is the amount of RAM in the segment minus any previously loaded drivers.
Page 144 DIAGnostic:DRAM:CREate :DRAM:CREate Parameters Comments Example :DRAM:CREate? 7-16 System Instrument Command Reference DIAGnostic:DRAM:CREate < size> < num_drivers> creates a non-volatile RAM area for loading instrument drivers. DIAGnostic:DRAM:CREate 0 removes the RAM segment when the system is re-booted. Parameter Parameter Name Type size numeric num_drivers...
Page 145 :DRIVer:LOAD DIAGnostic:DRIVer:LOAD < driver_block> loads the instrument driver contained in the driver_block into a previously created DRAM segment. < driver_block> Parameters Parameter Name driver_block Comments driver_block is the actual binary driver data to be transferred. Related Commands:DIAG:DRAM:AVAilable?, DIAG:DRAM:CREate, DIAG:DRIVer:LIST...?. Example Download a driver block.
Page 146 DIAGnostic:DRIVer :LIST[:type]? :DRIVer :LIST[:type]? Parameters Comments Example Example 7-18 System Instrument Command Reference DIAGnostic:DRIVer:LIST[:type]? lists all drivers from the specified table found on the system. If no parameter is specified, all driver tables are searched and the data from each driver table is separated from the others by a semicolon. Parameter Parameter Name...
Page 147 :INTerrupt:ACTivate DIAGnostic:INTerrupt:ACTivate < mode> enables an interrupt on the VXI backplane interrupt line specified by DIAG:INT:SET[n] to be acknowledged. Parameters Comments Example Enable an Interrupt Acknowledgement on Line 2. :INTerrupt:SETup[n] DIAGnostic:INTerrupt:SETup[n] < mode> 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.
Page 148 DIAGnostic:INTerrupt:SETup[n]? Example :INTerrupt:SETup[n]? Comments Example 7-20 System Instrument Command Reference ON or 1 specify that interrupt handling is to be set up for the specified interrupt line. OFF or 0 indicate that interrupt handling of the specified line is to be done by the operating system. Related Commands: DIAG:INT:ACT, DIAG:INT:PRIority[n], DIAG:INT:RESP? *RST Condition: DIAG:INT:SETup[n] OFF (for all lines)
Page 149 :INTerrupt:PRIority[n] Parameters Comments Example :INTerrupt:PRIority[n]? Comments Example DIAGnostic:INTerrupt:PRIority[n] [< level> ] gives a priority level to the VXI interrupt line specified by [n] in Parameter Parameter Name Type level numeric The priority of an interrupt line determines which line will be acknowledged first in the event that more than one line is interrupting.
Page 150 DIAGnostic:INTerrupt:RESPonse? :INTerrupt:RESPonse? Comments Example 7-22 System Instrument Command Reference 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 (STATUS/ID word) of a device interrupting on one of the interrupt lines set up with the DIAG:INT:SET[n] command.
Page 151 :NRAM:ADDRess? DIAGnostic:NRAM:ADDRess? Returns the starting address of the non-volatile User RAM segment allocated using DIAG:NRAM:CREate. Comments Example Determine address of the most recently created User RAM segment :NRAM:CREate DIAGnostic:NRAM:CREate < size> allocates a segment of non-volatile User RAM for a user-defined table. Parameters Parameter Comments...
Page 152 DIAGnostic:NRAM:CREate? :NRAM:CREate? Comments Example :PEEK? Parameters Comments Example 7-24 System Instrument Command Reference DIAGnostic:NRAM:CREate? [MIN | MAX] Returns the current or allowable (MIN | MAX) size of the User non-volatile RAM segment. DIAG:NRAM:CRE does not allocate driver RAM until a subsequent re-boot.
Page 153 :POKE DIAGnostic:POKE < address> ,< width> ,< data> writes data (number of bits given by width) starting at address. Parameters Parameter Name address width Comments Example Store byte in User non-volatile RAM :RDISk:ADDress? DIAGnostic:RDISk:ADDress? Returns the starting address of the RAM disc volume previously defined with the DIAG:RDISk:CREate command.
Page 154 DIAGnostic:RDISk:CREate :RDISk:CREate Parameters Comments Example :RDISk:CREate? Comments Example 7-26 System Instrument Command Reference DIAGnostic:RDISk:CREate < size> Allocates memory for a RAM disc volume. The RAM disc volume is defined for use only by the IBASIC option. Parameter Parameter Name Type size numeric The RAM disc segment will only be created after the System Instrument...
Page 155 :UPLoad[:MADDress]? Parameters Comments Example DIAGnostic:UPLoad[:MADDress]? < address> ,< byte_count> Returns the number of bytes specified by byte_count, starting at address. Parameter Parameter Name Type address numeric byte_count numeric Address may be specified in decimal, hex (# H), octal (# Q), or binary (# B) formats.
Page 156 DIAGnostic:UPload:SADDress? :UPload:SADDress? Parameters Comments Example 7-28 System Instrument Command Reference DIAGnostic:UPLoad:SADDress? < address> ,< byte_count> Returns the number of bytes specified by byte_count, at address. Parameter Parameter Name Type address numeric byte_count numeric Address may be specified in decimal, hex (# H), octal (# Q), or binary (# B) formats.
Page 157: Initiate
INITiate Subsystem Syntax [:IMMediate] Comments Example The INITiate command subsystem controls the initiation of the trigger system for one or more trigger cycles. INITiate enables while ABORt disables the trigger system. The TRIGger command subsystem controls the behavior of the trigger system while it is enabled.
Page 158: [Source]
[SOURce]:PULSe:COUNt [SOURce] Subsystem Syntax :PULSe:COUNt Parameters Comments Example :PULSe:COUNt? Example 7-30 System Instrument Command Reference The System Instrument contains a Pacer which produces TTL level pulses. The SOURCE command subsystem controls the number and period of these pulses. The output of the Pacer is available at the rear-panel BNC connector labeled “Pacer Out”.
Page 159 :PULSe:PERiod SOURce:PULSe:PERiod < period> sets the period of the pulse(s) to be generated by the Pacer. Parameters Parameter Name pweiod Comments The resolution of period is 500E-9 seconds. The Pacer waveform is a square wave with the output high for the first half of the period, and low for the final half.
Page 160: Status
STATus :OPERation :CONDition? STATus Subsystem Syntax :OPERation :CONDition? Comments Example :OPERation:ENABle < event> Parameters Comments 7-32 System Instrument Command Reference The STATus subsystem commands access the condition, event, and enable registers in the Operation Status group and the Questionable Data group. STATus :OPERation :CONDition?
Page 161 Example Unmasking bit 8 in the Event Register :OPERation:ENABle? STATus:OPER:ENABle? returns which bits in the event register (standard operation status group) are unmasked. Comments Example Reading the Event Register Mask :OPERation[:EVENt]? STATus:OPER:EVENt? returns which bits in the event register (standard operation status group) are set.
Page 162 STATus :PRESet Example :PRESet Example :QUESTionable 7-34 System Instrument Command Reference Reading the Event Register STAT:OPER:EVEN? enter statement STATus:PRESet sets each bit in the enable register (standard operation status group) to ’0’. Presetting the Enable Register STAT:PRES The STATus:QUEStionable commands are supported by the system instrument, however, they are not used by the System Instrument.
Page 163: System
SYSTem Subsystem Syntax :BEEPer[:IMMediate] Example The SYSTEM command subsystem for the System Instrument provides for: Configuration of the RS-232 interface 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:ERR?). Configuring the communication ports (GPIB and serial).
Page 164 SYSTem:COMMunicate :GPIB:ADDRess :COMMunicate :GPIB:ADDRess Parameters Comments Example :COMMunicate :GPIB:ADDRess? Example :COMMunicate :SERial[n]: Comments 7-36 System Instrument Command Reference SYSTem:COMMunicate:GPIB:ADDRess < address> sets the primary address of the Instrument’s GPIB port. Parameter Parameter Name Type address numeric The value of < address> is effective after the System Instrument has received a <...
Page 165 Example Setting baud rate for plug-in card 2. :COMMunicate SYSTem:COMMunicate:SERial[n]:CONTrol:DTR < dtr_cntrl> controls the behavior of the Data Terminal Ready output line. DTR can be set to a static :SERial[n] :CONTrol state (ON | OFF), can operate as a modem control line (STANDard), or can be :DTR used as a hardware handshake line (IBFull).
Page 166 SYSTem:COMMunicate :SERial[n] :CONTrol :DTR? :COMMunicate :SERial[n] :CONTrol :DTR? Example :COMMunicate :SERial[n] :CONTrol :RTS Parameters Comments Example 7-38 System Instrument Command Reference SYSTem:COMMunicate:SERial[n]:CONTrol:DTR? returns the current setting for DTR line control. Checking the setting of DTR control. SYST:COMM:SER0:CONT:DTR? enter statement SYSTem:COMMunicate:SERial[n]:CONTrol:RTS < Rts_cntrl> controls the behavior of the Request To Send output line.
Page 167 :COMMunicate SYSTem:COMMunicate:SERial[n]:CONTrol:RTS? returns the current setting for RTS line control. :SERial[n] :CONTrol :RTS? Example Checking the setting of RTS control. :COMMunicate SYSTem:COMMunicate:SERial[n][:RECeive]:BAUD < baud_rate> Sets the baud rate for the serial port. :SERial[n] [:RECeive] :BAUD Parameters Comments Example Setting the baud rate to 1200. :COMMunicate SYSTem:COMMunicate:SERial[n][:RECeive]:BAUD? [MIN | MAX] returns: :SERial[n] [:RECeive]...
Page 168 SYSTem:COMMunicate :SERial[n] [:RECeive] :BITS :COMMunicate :SERial[n] [:RECeive] :BITS Parameters Comments Example :COMMunicate :SERial[n] [:RECeive] :BITS? Example 7-40 System Instrument Command Reference SYSTem:COMMunicate:SERial[n][:RECeive]:BITS < bits> Sets the number of bits to be used to transmit and receive data. Parameter Parameter Name Type bits numeric...
Page 169 :COMMunicate SYSTem:COMMunicate:SERial[n][:RECeive]:PACE[:PROTocol] < protocol> enables or disables receive pacing (XON/XOFF) protocol. :SERial[n] [:RECeive] :PACE [:PROTocol] Parameters Comments Example Enabling XON/XOFF handshaking. :COMMunicate SYSTem:COMMunicate:SERial[n][:RECeive]:PACE[:PROTocol]? returns the current receive pacing protocol. :SERial[n] [:RECeive] :PACE [:PROTocol]? Example See if XON/XOFF protocol is enabled. SYSTem :COMMunicate :SERial[n] [:RECeive] :PACE [:PROTocol] Parameter Parameter...
Page 170 SYSTem:COMMunicate :SERial[n] [:RECeive] :PACE :THReshold :STARt :COMMunicate :SERial[n] [:RECeive] :PACE :THReshold :STARt Parameters Comments Example :COMMunicate :SERial[n] [:RECeive] :PACE :THReshold :STARt? Comments Example 7-42 System Instrument Command Reference SYSTem:COMMunicate:SERial[n][:RECeive]:PACE:THReshold:STARt < char_count> configures the input buffer level at which the specified interface may send the XON character (ASCII 11 the RTS line.
Page 171 SYSTem :COMMunicate :SERial[n] [:RECeive] :PACE :THReshold :STOP :COMMunicate SYSTem:COMMunicate:SERial[n][:RECeive]:PACE:THReshold:STOP < char_count> configures the input buffer level at which the specified interface :SERial[n] [:RECeive] may send the XOFF character (ASCII 13 :PACE :THReshold de-assert the RTS line. :STOP Parameters Comments Example Set interface to send XOFF when input buffer contains 80 characters.
Page 172 SYSTem:COMMunicate :SERial[n] [:RECeive] :PARity :CHECk :COMMunicate :SERial[n] [:RECeive] :PARity :CHECk Parameters Comments Example :COMMunicate :SERial[n] [:RECeive] :PARity :CHECk? Example :COMMunicate: SERial[n] [:RECeive] :PARity [:TYPE] Parameters Comments 7-44 System Instrument Command Reference SYSTem:COMMunicate:SERial[n][:RECeive]:PARity:CHECk < check_cntrl> controls whether or not the parity bit in received serial data frames will be considered significant.
Page 173 SYSTem :COMMunicate: SERial[n] [:RECeive] :PARity [:TYPE] The following table defines each value of type: Value EVEN ZERO NONE While this command operates independently of either the SBITs commands, there are two combinations which are disallowed because of their data frame bit width. The following table shows the possible combinations: BITS Received parity will not be checked unless...
Page 174 SYSTem:COMMunicate :SERial[n] [:RECeive] :PARity [:TYPE]? :COMMunicate :SERial[n] [:RECeive] :PARity [:TYPE]? Example :COMMunicate :SERial[n] [:RECeive] :SBITs Parameters Comments Example 7-46 System Instrument Command Reference SYSTem:COMMunicate:SERial[n][:RECeive]:PARity[:TYPE]? returns the type of parity checked and generated. What type of parity checking is set? SYST:COMM:SER0:PAR? enter statement SYSTem:COMMunicate:SERial[n][:RECeive]:SBITs <...
Page 175 :COMMunicate SYSTem:COMMunicate:SERial[n][:RECeive]:SBITs? [MIN | MAX] returns: :SERial[n] [:RECeive] :SBITs? Example Querying the current stop bit configuration. :COMMunicate SYSTem:COMMunicate:SERial[n]:TRANsmit:AUTO < auto_cntrl> when ON, sets the transmit pacing mode to be the same as that set for receive pacing. :SERial[n] :TRANsmit When OFF, the transmit pacing mode may be set independently of the receive :AUTO pacing mode.
Page 176 SYSTem:COMMunicate :SERial[n]:TRANsmit :PACE [:PROTocol] :COMMunicate :SERial[n]:TRANsmit :PACE [:PROTocol] Parameters Comments Example :COMMunicate :SERial[n] :TRANsmit :PACE [:PROTocol]? Example :DATE Parameters Comments 7-48 System Instrument Command Reference SYSTem:COMMunicate:SERial[n]:TRANsmit:PACE[:PROTocol] < protocol> enables or disables the transmit pacing (XON/XOFF) protocol. Parameter Parameter Name Type protocol discrete For an Agilent E1324A, AUTO is always ON.
Page 177 Related Commands: SYST:TIME, SYST:TIME?, SYST:DATE? *RST Condition: *RST does not change the setting of the calendar. Example Setting the system Date SYST:DATE 1991,09,08 :DATE? SYSTem:DATE? [MIN| MAX,MIN| MAX,MIN| MAX] returns: When no parameter is sent: the current system date in the form + YYYY,+ MM,+ DD, where YYYY can be the year 1980 through 2079, MM can be the month 1 through 12, and DD can be the day 1 through 31.
Page 178 SYSTem:TIME :TIME Parameters Comments Example :TIME? Example :VERSion? Comments Example 7-50 System Instrument Command Reference SYSTem:TIME < hour> ,< minute> ,< second> sets the E1300/E1301 mainframe’s internal clock. Parameter Parameter Name Type hour numeric minute numeric second numeric Related Commands: SYST:DATE, SYST:DATE?, SYST:TIME? *RST Condition: *RST does not change the Command Module’s real time clock.
Page 179: Trigger
TRIGger Subsystem Syntax :DELay Parameters Comments Example :DELay? Example The TRIGger command subsystem controls the behavior of the trigger system once it is initiated (see INITiate command subsystem). The trigger command subsystem controls: The delay between trigger and first Pacer pulse (TRIG:DELay) An immediate software trigger (TRIG:IMM) The source of the trigger (TRIG:SOUR BUS| EXT| HOLD| IMM) TRIGger...
Page 180 TRIGger[:IMMediate] [:IMMediate] Comments Example :SLOPe Parameters Comments :SLOPe? :SOURce Parameters 7-52 System Instrument Command Reference TRIGger:IMMediate will cause a trigger cycle to occur immediately, provided that the trigger system has been initiated (INITiate). Related Commands: ABORt, INITiate *RST Condition: This command is an event and has no *RST condition. Triggering the Pacer.
Page 181 Comments The following table explains the possible choices. Parameter Value EXTernal HOLD IMMediate While an instrument which uses the "Event In" signal has EXT set, no other instrument which uses the "Event In" signal may set EXT, or an error 1500 "External trigger source already allocated" will result. While TRIG:SOUR is IMM, you need only INITiate the trigger system to start the Pacer.
Page 182: Vxi
VXI:CONFigure :DLADdress? Subsystem Syntax :CONFigure :DLADdress? Comments Example 7-54 System Instrument Command Reference The VXI command subsystem provides for: Determining the number, type, and logical address of the devices (instruments) installed in the E1300/E1301 mainframe. Direct access to VXIbus A16 registers within devices installed in the Mainframe.
Page 183 :CONFigure:DLISt? VXI:CONF:DLIS? [< logical_addr> ] returns information about the device specified by logical_addr. Response data is in the form: Where the fields above are defined as: n1, n2, n3, n4, n5, n6, c1, c2, c3, c4, c5, s1, s2, s3, s4 n fields Indicate numeric data response fields.
Page 184 VXI:CONFigure :DNUMber? Parameters Comments Example :CONFigure :DNUMber? Comments Example 7-56 System Instrument Command Reference Parameter Parameter Name Type logical_addr numeric 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 185 :CONFigure VXI:CONF:HIER? Returns current hierarchy configuration information about the selected logical address. The individual fields of the response are comma :HIERarchy? separated. If the information about the selected logical address is not available from the destination device (i.e., the requested device is not in the mainframe) then Error -224 ("parameter error") will be set and no response data will be sent.
Page 186 VXI:CONFigure :HIERarchy:ALL? :CONFigure :HIERarchy:ALL? NOTE Comments :CONFigure :INFormation? 7-58 System Instrument Command Reference Cards which are part of a combined instrument such as a switchbox or scanning voltmeter always return the same manufacturer’s comments as the first card in the instrument. Information in the other fields correspond to the card for which the Logical Address was specified.
Page 187 registers) which are present on the device. -1 indicates that the device has no A16 memory. 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.
Page 188 VXI:CONFigure :INFormation:ALL? :CONFigure :INFormation:ALL? Comments :CONFigure :LADDress? Comments :CONFigure :NUMBer? Comments :READ? Parameters Comments 7-60 System Instrument Command Reference VXI:CONF:INF:ALL? Returns the static information about all logical addresses. The information is returned in the order specified in the response to VXI:CONF:LADD?.
Page 189 Related Commands: VXI:WRITE, VXI:REG:READ? Example Read from one of a device’s configuration registers :REGister:READ? VXI:REG:READ? < register> returns the contents of the specified 16 bit register at the selected logical address as an integer (see VXI:SELect). The register is specified as the byte address of the desired register or optionally as the register name.
Page 190 VXI:REGister:WRITe :REGister:WRITe Parameters Comments Example Reset? Comments 7-62 System Instrument Command Reference VXI:REG:WRITe? < register> ,< data> writes to the specified 16 bit register at the selected logical address (see VXI:SELect). The data is a 16 bit value specified as a numeric value in the range of -32768 to 32767 or 0 to 65535. The register is specified as the byte address of the desired register or optionally as the register name.
Page 191 :SELect VXI:SELect < logical_addr> specifies the logical address which is to be used by many subsequent commands in the VXI subsystem. Parameters Parameter Name logical_addr Comments The *RST default value for logical_addr is that no logical address is selected (i.e., -1). All other commands which require a logical address to be selected will respond with Error -221 ("settings conflict") if no logical address is selected.
Page 192 VXI:WRITe :WRITe Parameters Comments Example 7-64 System Instrument Command Reference VXI:WRITe < logical_addr> ,< register_addr> ,< data> 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 193: Common Command Reference
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 by command groups in the summary table below, and alphabetically in the rest of this section. 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.
Page 194: Cls
* CLS * DMC < > , name_string < > command_block Example * EMC < > enable * EMC? * ESE < mask> Example 7-66 System Instrument Command Reference Clear Status Command. The *CLS 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.
Page 195: Ese
* ESE? Example * ESR? Example * GMC? < > name_string Example Standard Event Status Enable Query. Returns the weighted sum of all enabled (unmasked) bits in the Standard Event Status Register. 10 OUTPUT 70900;"* ESE?" 20 ENTER 70900;A 30 PRINT A 40 END Standard Event Status Register Query.
Page 196: Idn
Firmware Revision (returns 0 if not available) The *IDN? command returns the following command string for the E1301B: AGILENT,E1301B,0,A,07.00 This command will return the following string for the E1300B: AGILENT,E1300B,0,A,07.00 The revision will vary with the revision of the ROM installed in the system. This is the only indication of which version of ROM is in the box.
Page 197: Opc
NOTE The System Instrument no longer implements the *LRN? command. Attempting to have the System Instrument execute this command will generate an 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 198: Rcl < State Number
* RCL < state number> Example * RMC < > name_string Example * RST * SAV < state number> Example * SRE < mask> Example 7-70 System Instrument Command Reference Recall stored state. Recalls a stored state from memory and configures the instrument to that state.
Page 199: Sre
* SRE? Status Register Enable Query. Returns the weighted sum of all enabled (unmasked) events (those enabled to assert SRQ) in the Status Byte Register. Example 10 OUTPUT 70900;"* SRE?" 20 ENTER 70900;A 30 PRINT A 40 END * STB? Status Byte Register Query.
Page 200: Gpib Message Reference
REMOTE 709ss (ss = secondary address) command, or with the LISTEN command). For instruments in an Agilent E1300B/E1301B Mainframe, only one instrument at a time can be programmed to respond to GET. This is because only one instrument can be addressed to listen at any one time.
Page 201: Device Clear (Dcl) Or Selected Device Clear (Sdc)
Device Clear (DCL) or Selected Device Clear (SDC) Examples Local Lockout (LLO) Comments Examples DCL clears all instruments in the mainframe. SDC clears a specific instrument. The purpose of DCL or SDC is to prepare one or more instruments to receive and execute commands (usually *RST).
Page 202: Remote
Remote Comments Examples Serial Poll (SPOLL) Comments Examples 7-74 System Instrument Command Reference Sets the GPIB remote enable line (REN) true which places an instrument in the remote state. The REMOTE 709ss (ss = secondary address) command places the instrument in the remote state. The REMOTE 7 command, does not, by itself, place the instrument in the remote state.
Page 203: Command Quick Reference
Command Quick Reference Command ABORt [IMMediate] DIAGnostic :BOOT :COLD [:WARM] :COMMunicate :SERial[0] [:OWNer] [SYSTem| IBASic| NONE] [:OWNer]? :SERial[n] :STORe :DOWNload :CHECked [:MADDress] :SADDress [:MADDress] < address> , < data> :SADDress < address> , < data> :DRAM :AVAilable? :CREate < size> ,< num_drivers> :DRIVer :LOAD <...
Page 204: Command Description
System Instrument Command :NRAM :ADDRess? :CREate < size> | MIN| MAX :CREate? [MIN| MAX] :PEEK? < address> | MIN| MAX,< width> :POKE < address> | MIN| MAX,< width> ,< data> :RDISk :ADDRess? :CREate < size> | MIN| MAX :CREate? [MIN| MAX] :UPLoad [:MADDress]? <...
Page 205 Command SYSTem :BEEPer [:IMMediate] :COMMunicate :GPIB :ADDRess :ADDRess? :SERial[n] :CONTrol :DTR ON| OFF| STANdard| IBFull :DTR? :RTS ON| OFF| STANdard| IBFull :RTS? [:RECeive] :BAUD < baud_rate> | MIN| MAX :BAUD? [MIN| MAX] :BITS 7| 8| MIN| MAX :BITS? [MIN| MAX] :PACE [:PROTocol] XON| NONE [:PROTocol]?
Page 206 System Instrument Command TRIGger :DELay < numeric value> :DELAy? [MIN| MAX] [:IMMediate] :SLOPe [NEGATIVE] :SLOPe? :SOURce EXTernal| IMMediate| BUS| HOLD :SOURce? :CONFigure :DeviceLADd? :DeviceLISt? :DeviceNUMber? :INFormation :ALL? :HIERarchy :ALL? :NUMber? :LADDress? :READ? < logical_addr> ,< register_num> :REGister :READ? < numeric_value| < reg_name> :WRITe <...
Page 207 IEEE 488.2 Comman Commands Quick Reference Category Command *IDN? General *RST *TST? Instrument Status *CLS *ESE < mask> *ESE? *ESR? *PSC < flag> *PSC? *SRE < mask> *SRE? *STB? *DMC < Macros name> ,< cmd_data> *EMC < enable> *EMC? *GMC? < name>...
Page 208 7–80 Command Quick Reference...
Page 209: Specifications
Mainframe Specifications Pacer (50% duty cycle): Real-time Clock: Trigger Input: Non-volatile added memory storage lifetime: Slots: EMC, RFI, Safety: Programmable intervals: 500 nsec to 8.389 sec with 500 nsec resolution. Accuracy: First pulse after trigger: 0.01% of programmed time + 600 to 850 nsec. Additional pulses: 0.01% of programmed time Number of pulses: 1 through 8388607 or continous.
Page 210: Size
3 A @ 115 Vac 1.5 A @ 230 Vac Consumption: E1300B (empty) 27 W, 52 VA E1301B (empty) 31 W, 57 VA Any combination of Agilent Series B modules can be powered and cooled by the Agilent 75000 Series B mainframe. Configuration using non-Agilent modules (e.g., VME modules) should be checked to assure the power consumption does...
Page 211: Scpi Conformance Information
SCPI Conformance Information Switchbox Configuration The Agilent E1300/1301B conforms to SCPI-1990.0 In documentation produced prior to June 1990, these SCPI commands are labeled as TMSL commands. The following tables list all the SCPI conforming, approved, and non-SCPI commands that the E1300/1301B can execute. Individual commands may not execute without having the proper plug-in module installed in the E1300/ 13301B.
Page 212: Multimeter Commands
Multimeter Commands A-4 Specifications The following tables apply to the Agilent E1326A and E1326B. Table A-3. Multimeter SCPI-1990.0 Confirmed Commands ABORt CALibration :Z ERO :AUTO :AUTO? :VALue CONFigure :FRESistance :RESistance :TEMPerature :VOLTage [:DC] CONFigure? FETCh? FORMat [:DATA] INITiate [:IMMediate] MEASure :FRESistance? :RESistance? :TEMPerature?
Page 213 Table A-5. Multimeter Non-SCPI Commands CALibration :LFRequency :LFRequency? :STRain CONFigure :STRain :QUARter :HBENding :HPOisson :FBENding :FPOisson :FBPoisson :QTENsion :QCOMpression :UNSTrained DISPlay :MONitor :CHANnel :CHANnel? [:STATe] [:STATe]? MEASure :STRain :QUARter? :HBENding? :HPOisson? :FBENding? :FPOisson? :FBPoisson? :QTENsion? :QCOMpression? :UNSTrained? MEMory :VME :ADDRess :ADDRess? :SIZ E :SIZ E?
Page 214: Counter Commands
Counter Commands A-6 Specifications The following tables apply to the Agilent E1332A 4 Chanel Counter/Totalizer and the Agilent E1333A 3 Channel Universal Counter. Table A-6. Agilent E1332A SCPI-1990.0 Confirmed Commands ABORt CONFigure :FREQuency :PERiod :PWIDth :NWIDth CONFigure? FETCh? FORMat [:DATA] INITiate [:IMMediate] INPut...
Page 215 Table A-8. Agilent E1333A SCPI-1990.0 Confirmed Commands ABORt FETCh? CONFigure :FREQuency :PERiod :PWIDth :NWIDth CONFigure? FORMat [:DATA] INITiate [:IMMediate] INPut :ATTenuation :ATTenuation? :COUPling :COUPling? :FILTer [:LPASs] [:STATe] [:STATe]? :IMPedance :IMPedance? MEASure :FREQuency? :PERiod? :PWIDth? :NWIDth? Table A-9. Agilent E1333A Non-SCPI Commands CONF[<...
Page 216: D/A Converter Commands
D/A Converter Commands A-8 Specifications The following tables apply to the Agilent E1328A 4 Channel D/A Converter. Table A-10. Agilent E1328A SCPI-1990.0 Confirmed Commands CALibration :STATe :STATe? SYSTem :ERRor? :VERSion? Table A-11. Agilent E1328A Non-SCPI Commands CALibration :VOLTage :CURRent DISPlay :MONitor :CHANnel :CHANnel?
Page 217: Digital I/O Commands
Digital I/O Commands The following tables apply to the Agilent E1330A Quad 8-bit Digital I/O Module. Table A-12. Agilent E1330A SCPI-1990.0 Confirmed Commands STATus :QUEStionable :CONDition? [:EVENt]? :ENABle :ENABle? :OPERation :CONDition? [:EVENt]? :ENABle :ENABle? :PREset Table A-13. Agilent E1330A Non-SCPI Commands DISPlay :MONitor [:STATe]...
Page 218: System Instrument Commands
System Instrument Commands A-10 Specifications Table A-14. System Instrument SCPI-1990.0 Confirmed Commands ABORt INITiate [:IMMediate] [SOURce] :PULSe :COUNt :COUNt? :PERiod :PERiod? STATus :QUEStionable :CONDition? [:EVENt]? :ENABle :ENABle? :OPERation :CONDition? [:EVENt]? :ENABle :ENABle? :PREset TRIGger [:IMMediate] :SOURce :SOURce? :SLOPe :SLOPe? Table A-15. System Instrument SCPI-1991.0 Confirmed Commands SYSTem :COMMunicate :SERial...
Page 219 Table A-17. System Instrument Non-SCPI Commands DIAGnostic :AUTstart :AUTostart? :CHECksum :COMMunicate :SERial [:OWNer] [:OWNer]? :BOOT :COLD [:WARM] :UPLoad? :DOWNload :INTerrupt :ACT :SETup(n) :SETup(n)? :PRIority(n) :PRIority(n)? :WAIT? :JSR :CALL :DRIVer :LOAD :LISt? :DRAM :CREate :CREate? :AVAilable? :NRAM :CREate :CREate? :AVAilable? :RDISK :CREate :CREate? :ADDRess?
Page 220 A-12 Specifications...
Page 221: Error Messages
Using This Appendix Reading an Instrument’s Error Queue Example: Reading the Error Queue 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 222: Error Types
Error Types Command Errors Execution Errors Device-Specific Errors Query Errors B-2 Error Messages Negative error numbers are language-related and categorized as shown below. 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.
Page 223 Table B-2. Error Messages and Causes Error Messages and Causes Code Message -101 Invalid character - 102 Syntax error - 103 Invalid separator - 104 Data type error - 108 Parameter not allowed - 109 Missing parameter - 113 Undefined header - 123 Numeric overflow - 128...
Page 224 B-4 Error Messages Error Messages and Causes Code Message 2110 Config error 10, Insufficient system memory 2111 Config error 11, Invalid instrument address 2113 Config error 13, Logical address or IACK switch set wrong 2129 Config warning, Sysfail detected 2130 Config error 30, Pseudo instrument logical address unavailable...
Page 225: Start-Up Error Messages
Agilent E1300B with a terminal connected to the Display Terminal Interface (built-in RS-232 only), you can read these errors on the front panel or terminal. If you have an Agilent E1300B and no terminal, then you must access this error information by sending the VXI:CONF:DLIS? command over GPIB. We...
Page 226 B-6 Error Messages...
Page 227: Connecting And Configuring A Display Terminal
Using this Appendix Overview Connecting a Terminal to the Mainframe Connecting and Configuring a This appendix shows you how to configure the mainframe and a supported terminal to operate with the Display Terminal Interface. Using the Display Terminal Interface is discussed in Chapter 3. Overview .
Page 228: Connecting A Terminal To The Mainframe
Agilent Agilent E1300B/E1301B Mainframe Agilent 10833A, B or C to Connect to GPIB Agilent Agilent E1300B/E1301B Mainframe Agilent Agilent Agilent E1300B/E1301B Mainframe Agilent 24542H Agilent 24542H Figure C–1 Connecting a Terminal to the Mainframe C-2 Connecting and Configuring a Display Terminal...
Page 229: Configuring A Terminal For The Mainframe
Configuring a Terminal for the Mainframe Starting with Default Mainframe Settings Restoring the Default Configuration Note Configuring the Terminal We’ll first set the terminal’s serial communication parameters to match the mainframe’s default settings. If the mainframe is new and its factory default values are still set, the terminal will be ready to use.
Page 230: Trying It
Trying it Configuring the Mainframe with Menus C-4 Connecting and Configuring a Display Terminal Turn on the mainframe while watching the terminal’s display. After the mainframe finishes its self-test, the terminal should display "Select an instrument". If not, the mainframe’s communication parameters are not set to the default values.
Page 231 How to Use the Serial Interface Menus Press READ to find out the current setting Enter Card Number press Return (0 for built-in, 1-7 for a plug-in) Read the BAUD rate Press SET to change the current setting Each SET Menu will have two or more choices Enter Card Number press Return (0 for built-in, 1-7 for a plug-in)
Page 232 How to Store the Serial Interface Configuration Enter Card Number press Return. Card Number 0 for built-in stores settings into non_volatile RAM. Card Number 1-7 for Agilent E1324A stores settings into its on- board EEROM) C-6 Connecting and Configuring a Display Terminal...
Page 233: Sending Binary Data Over
Sending Binary Data Over RS-232 About this Appendix Formatting Binary Data for RS-232 Transmission 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.
Page 234 Sending Binary Data Over RS-232 Setting Up the Mainframe D-2 Sending Binary Data Over RS-232 Table D-1. Correction Codes for RS-232 Transmission Data Value Correction Code The RS-232 interface differs from the GPIB interface in that there is no device addressing built into the interface definition.
Page 235 3. Send "SI SYSTEM" and a carriage return to get the attention of the System Instrument. 4. Send < CTRL-C> to clear the system. 5. Send "*RST" and a carriage return to put the System Instrument in a known state. The program must then send the binary data.
Page 236: Sending Binary Data Over
D-4 Sending Binary Data Over RS-232...
Page 237 Index 3-Channel Universal Counter Menu (front panel), 2-26 - 2-27 Menu (terminal interface), 3-38 - 3-39 4-Channel Counter/Totalizer Menu (front panel), 2-24 - 2-25 Menu (terminal interface), 3-36 - 3-37 4-Channel D/A Converter Menu (front panel), 2-21 Menu (terminal interface), 3-33 5 1/2 Digit Multimeter Menu (front panel), 2-20 Menu (terminal interface), 3-32...
Page 238 *SAV, 7-70 *SRE, 7-70 *SRE?, 7-71 *STB?, 7-71 *TRG, 7-71 *TST?, 7-71 *WAI, 7-71 Common Commands functional groupings, 7-65 COMMunicate:GPIB :ADDRess, 7-36 :ADDRess?, 7-36 COMMunicate:SERial[0] :OWNer, 7-7 :OWNer?, 7-8 COMMunicate:SERial[n] :CONTrol:DTR, 7-37 :CONTrol:DTR?, 7-38 :CONTrol:RTS, 7-38 :CONTrol:RTS?, 7-39 :RECeive:BAUD, 7-39 :RECeive:BAUD?, 7-39 :RECeive:BITS, 7-40 :RECeive:BITS?, 7-40...
Page 239 DIAG:PEEK?, 7-24 DIAG:POKE, 7-25 DIAG:RDIS:ADD?, 7-25 DIAG:RDIS:CRE, 7-26 DIAG:RDIS:CRE?, 7-26 DIAG:UPL:SADD?, 7-28 DIAG:UPL[:MADD]?, 7-27 DRIV:LIST:ROM?, 7-18 DRIV:LIST?, 7-18 DIAGnostic:DRIVer:LIST:RAM?, 7-18 DIAGnostic:DRIVer:LIST:ROM?, 7-18 DIAGnostic:DRIVer:LIST?, 7-18 Display instrument information (terminal interface), 3-5 control/editing keys (front panel), 2-10 instrument information (front panel), 2-3 instrument logical addresses (front panel), 2-3 instrument logical addresses (terminal interface), 3-5 module type &...
Page 240 Files:VXIDLD.CFG, 5-4 Format Common Command, 7-1 SCPI Command, 7-1 Front panel features, 2-1 menu tutorial, 2-2 menus, 2-2 GET (group execute trigger), 7-72 Go to local (GTL), 7-72 Group execute trigger (GET), 7-72 GTL (go to local), 7-72 Hints, programming, 6-1 How to display instrument information (front panel), 2-3 display instrument information (terminal interface), 3-5...
Page 241 tutorial, 2-2 Menu (terminal interface) 3-Channel Universal Counter, 3-38 - 3-39 4-Channel Counter/Totalizer, 3-36 - 3-37 Quad 8-Bit Digital Input/Output, 3-34 4-Channel D/A Converter, 3-33 5 1/2 Digit Multimeter, 3-32 control keys, 3-14 instrument, 3-25 keys, 3-14 Scanning Voltmeter, 3-30 - 3-31 Switchbox, 3-28 System Instrument, 3-26 - 3-27 tutorial, 3-3...
Page 242 SA, terminal interface command, 3-21 Scan channels (front panel), 2-5 Switchbox, terminal interface, 3-8 Scanning Voltmeter Menu (front panel), 2-18 - 2-19 Voltmeter Menu (terminal interface), 3-30 - 3-31 SCPI Commands, 7-1 Format, 7-1 Reference, 7-4 SDC (selected device clear), 7-73 Secondary addresses, instrument, 1-4 SELect, 7-63 Select Address command (terminal interface), 3-21...
Page 243 SYST:COMM:SER[n]:REC:PACE:THR:STOP, 7-43 SYST:COMM:SER[n]:REC:PACE:THR:STOP?, 7-43 SYST:COMM:SER[n]:REC:PAR:CHEC, 7-44 SYST:COMM:SER[n]:REC:PAR:CHEC?, 7-44 SYST:COMM:SER[n]:REC:PAR[:TYPE?], 7-46 SYST:COMM:SER[n]:REC:SBIT, 7-46 SYST:COMM:SER[n]:REC:SBIT?, 7-47 SYST:COMM:SER[n]:TRAN:AUTO, 7-47 SYST:COMM:SER[n]:TRAN:AUTO?, 7-47 SYST:COMM:SER[n]:TRAN:PACE:PROT, 7-48 SYST:COMM:SER[n]:TRAN:PACE:PROT?, 7-48 SYST:COMM:SERial[n]:CONT:RTS, 7-38 SYST:DATE, 7-48 SYST:DATE?, 7-49 SYST:ERRor?, 7-49 SYST:TIME, 7-50 SYST:TIME?, 7-50 SYST:VERS?, 7-50 Terminal configuring, C-1 - C-5 connecting, C-1 - C-5 Terminal interface commands, 3-19...
Page 244 Index-8...

This manual is also suitable for:

E1301b 75000 series b

Agilent Technologies E1300B User Manual

Getting Started

Using the Front Panel

Using the Display Terminal Interface

Using the Mainframe

Downloading Device Drivers

Controlling Instruments Using GPIB

System Instrument Command Reference

Specifications

Error Messages

Connecting and Configuring a Display Terminal

Sending Binary Data over

Quick Links

Related Manuals for Agilent Technologies E1300B

Summary of Contents for Agilent Technologies E1300B

This manual is also suitable for:

Table of Contents