Page 1 Programmer’s Guide Agilent Technologies E4406A VSA Series Transmitter Tester Manufacturing Part Number: E4406-90135 Printed in USA February 2000 © Copyright 1999 - 2000 Agilent Technologies, Inc.
Page 2 The information contained in this document is subject to change without notice. Agilent Technologies makes no warranty of any kind with regard to this material, including but not limited to, the implied warranties of merchantability and ﬁtness for a particular purpose. Agilent...
Page 3 Agilent Technologies from another country. Agilent Technologies warrants that its software and ﬁrmware designated by Agilent Technologies for use with an instrument will execute its programming instructions when properly installed on that instrument. Agilent Technologies does not warrant that the operation of the instrument, or software, or ﬁrmware will be uninterrupted or...
Page 5: Table Of Contents
Contents 1. Preparing for Use What’s in This Chapter?............14 www.agilent.com/ﬁnd/vsa .
Page 6 Contents Handshake and Baud Rate ...........67 Character Format Parameters.
Page 7 Contents Reset ..............142 Save .
Page 8 Contents Select the Source for Calibration ..........170 Select the Source State for Calibration .
Page 9 Contents Delete a File............. . 208 READ Subsystem .
Page 10 Contents Questionable Power Condition ..........276 Questionable Power Enable .
Page 11 Contents Error Queues ............. . 298 Front Panel Error Messages.
Page 12 Contents...
Page 13: Preparing For Use
Preparing for Use This instrument uses the Standard Commands for Programmable Instruments (SCPI) programming language. For information on writing SCPI commands see “SCPI Language Basics” on page...
Page 14: What's In This Chapter
Get the latest listing of SCPI commands for this instrument at the above web location. Look under technical support information. Digital Communications Measurements Information Additional measurement application information is available through your local Agilent Technologies sales and service ofﬁce. Some application notes are listed below: Agilent Part Description...
Page 15: Programming The Transmitter Tester
Preparing for Use Programming the Transmitter Tester Programming the Transmitter Tester The E4406A VSA Series Transmitter Tester has several different measurement modes. The measurement commands that are available to you change, depending on which mode is selected. Use INSTrument:SELect to select the desired mode.
Page 16 Preparing for Use Programming the Transmitter Tester Table 1-1 Available Modes and Measurements Modes Measurement Keywords W-CDMA - Option BAF • ACP - adjacent channel power ratio measurement • CDPower - code domain power measurement • CHPower - channel power measurement •...
Page 17: Installing Optional Measurement Personalities
Preparing for Use Installing Optional Measurement Personalities Installing Optional Measurement Personalities When you Install a measurement personality, you follow a two step process. 1. The measurement personality ﬁrmware must be installed into the instrument. (See the supplied installation instructions.) 2. A license key number must be entered which enables the measurement personality to run.
Page 18: License Key Numbers
Preparing for Use Installing Optional Measurement Personalities Option column of the table below. Option Available Personality Options GSM with EDGE, measurement personality cdmaOne measurement personality NADC, PDC measurement personalities iDEN measurement personality W-CDMA measurement personality cdma2000 measurement personality a. As of the print date of this measurement guide. License Key Numbers The measurement personality you have purchased with your instrument has been installed and enabled at the factory.
Page 19: Installing A License Key Number
Please enter your license key numbers in the box provided below for future reference. If you should lose your license key number, call your nearest Agilent Technologies service or sales ofﬁce for assistance. License Key Numbers for Instrument with Serial # ________...
Page 20: Using The Uninstall Key
Preparing for Use Installing Optional Measurement Personalities 3. Press the key after you have entered the active license Install Now key number and the personality option. When pressed, a message may appear in the function area of the display which reads, “Insert disk and power cycle the instrument”.
Page 21: Writing Your First Program
Preparing for Use Writing Your First Program Writing Your First Program When the instrument has been connected to a computer, the computer can be used to send instrument instructions to make fast, repeatable measurements. A variety of different programming languages, computer types, and interface buses can be used for this process.
Page 22: File Naming Rules
Preparing for Use Writing Your First Program single-sweep mode (INITiate:CONTinuous OFF) before setting other instrument functions. • Select the instrument mode with INST:SELect. Set the mode setup for things like your desired communications standard, channel frequency and triggering. • Use the MEASure group of commands, described in Chapter 5 , “Language Reference”.
Page 23 Preparing for Use Writing Your First Program Description Character hyphen braces at sign ‘ single quotation mark ’ apostrophe parenthesis a. No other characters are valid. • They cannot contain spaces, commas, backslashes, or periods (except the period that separates the name from the extension). •...
Page 24: Cables For Connecting To Rs-232
Preparing for Use Cables for Connecting to RS-232 Cables for Connecting to RS-232 There are a variety of cables and adapters available for connecting to PCs, and printers. Several of these are documented in the following wiring diagrams. You need to ﬁnd out what connections your equipment uses to identify the cables and/or adapters that you will need.
Page 25 Preparing for Use Cables for Connecting to RS-232 Figure 1-2 HP/Agilent F1047-80002 Cable F1047-80002 Instrument Cable Male Female Female Male ca86a Figure 1-3 HP/Agilent 24542G/H Cable 24542G/H Instrument Cable DB25 DB25 24542H Male Female Female Male DB25 DB25 24542G Male Female Male Female...
Page 26 Preparing for Use Cables for Connecting to RS-232 Figure 1-5 HP/Agilent 13242G Cable 13242G Instrument Cable PC/Printer Shield SRTS SRTS DB25 DB25 DB25 DB25 Female Male Male Female ca84a Figure 1-6 HP/Agilent 24542M Modem Cable 24542M Instrument Modem Cable Modem DB25 DB25 Male...
Page 27 Preparing for Use Cables for Connecting to RS-232 Figure 1-7 HP/Agilent C2913A/C2914A Cable Instrument C2913A/C2914A DB25 DB25 DB25 DB25 Female Male Female Male DB25 DB25 DB25 DB25 Female Male Male Female ca89a Figure 1-8 Mouse Adapter (typical) Typical Mouse Instrument Adapter DB25 DB25...
Page 28 Preparing for Use Cables for Connecting to RS-232 Figure 1-9 HP/Agilent 24542U Cable with 5181-6641 Adapter 24542U 5181-6641 Instrument Cable Adapter (Black) DB25 DB25 Male Female Female Male Female Male ca811a Figure 1-10 HP/Agilent 24542U Cable with 5181-6640 Adapter 24542U 5181-6640 Instrument Cable...
Page 29 Preparing for Use Cables for Connecting to RS-232 Figure 1-12 HP/Agilent 24542U Cable with 5181-6639 Adapter 24542U 5181-6639 Instrument Cable Adapter (Black) Modem Male Female Female Male Male Female ca814a Figure 1-13 HP/Agilent F1047-80002 Cable with 5181-6641 Adapter F1047-80002 5181-6641 Instrument Cable Adapter (Black)
Page 30 Preparing for Use Cables for Connecting to RS-232 Figure 1-15 HP/Agilent F1047-80002 Cable with 5181-6642 Adapter F1047-80002 5181-6642 Instrument Cable Adapter (Gray) Modem DB25 DB25 Male Female Female Male Male Female ca817a Figure 1-16 HP/Agilent F1047-80002 Cable with 5181-6639 Adapter F1047-80002 5181-6639 Instrument...
Page 31: Connecting To A Lan Server
Preparing for Use Connecting to a LAN Server Connecting to a LAN Server Connect a cable to the standard LAN connector on the rear panel of the instrument. The LAN can then be used several different ways: • To ftp ﬁles from the instrument •...
Page 32 Preparing for Use Connecting to a LAN Server Chapter 1...
Page 33: Programming Fundamentals
Programming Fundamentals...
Page 34 Programming Fundamentals • “SCPI Language Basics” on page 35 • “Using the Instrument Status Registers” on page 42 • “C Programming Examples using VTL” on page 57 • “Overview of the GPIB Bus” on page 65 • “Overview of the RS-232 Bus” on page 67 •...
Page 35: Scpi Language Basics
IEEE Standard 488.2-1987, IEEE Standard Codes, Formats, Protocols and Comment Commands for Use with ANSI/IEEE Std488.1-1987. New York, NY, 1998. There is also a book available from Agilent Technologies, SCPI—Standard Commands for Programmable Instruments, 1998. Creating Valid Commands Commands are not case sensitive and there are often many different ways of writing a particular command.
Page 36: Command Key Words And Syntax
Programming Fundamentals SCPI Language Basics Command Syntax Sample Valid Commands The last command below returns different MEASure:SPECtrum[n]? results then the command above it. The number [<freq>[,<level>[,<freq(span)>]]] 3, in the command, causes this. See the command description for more information. • MEAS:SPEC? •...
Page 37: Special Characters In Commands
Programming Fundamentals SCPI Language Basics Special Characters in Commands Special Meaning Example Character A vertical stroke between Command: parameters indicates TRIG:SOURCE EXT|INT|LINE alternative choices. The The choices are ext, int, and effect of the command is line. different depending on TRIG:SOURCE INT which parameter is is one possible command...
Page 38 Programming Fundamentals SCPI Language Basics values of 0 or 1 are commonly used in the command instead of OFF or ON, and queries of the parameter always return a numeric value of 0 or 1. Key Word The parameter key words that are allowed for a particular command are deﬁned in the command description and are separated with a vertical slash.
Page 39 Programming Fundamentals SCPI Language Basics optional units. The default units are dBm. Acceptable units include: DBM, DBMV, W. <rel_power> <rel_ampl> A relative power parameter is a positive rational number followed by optional units. The default units are dB. Acceptable units include: DB. <angle>...
Page 40: Putting Multiple Commands On The Same Line
Programming Fundamentals SCPI Language Basics format (bytes/point), either 8 (for real 64), or 4 (for real 32). If you’re using real 64, then there are 1540 points in the block. Putting Multiple Commands on the Same Line Multiple commands can be written on the same line, reducing your code space requirement.
Page 41 Programming Fundamentals SCPI Language Basics Bad Command Good Command FREQ 30MHz;ATT 20dBm FREQ 30MHz;POW:ATT 20dBm The ATT command is in the same (SENSE) subsystem as FREQ, but executing the FREQ command puts you back at the SENSE level. You must specify POWER to get to the ATT command.
Page 42: Using The Instrument Status Registers
Programming Fundamentals Using the Instrument Status Registers Using the Instrument Status Registers You can determine the state of certain instrument hardware and ﬁrmware events and conditions by programming the status register system. The Figure on page 49 shows all the instrument status registers and their hierarchy.
Page 43: What Are The Status Registers
Programming Fundamentals Using the Instrument Status Registers What are the Status Registers? The status system is comprised of multiple registers which are arranged in a hierarchical order. The lower-level status registers propagate their data to the higher-level registers in the data structures by means of summary bits.
Page 44 Programming Fundamentals Using the Instrument Status Registers *ESE, *ESE? (event status enable) sets and queries the bits in the enable register part of the standard event status register. *ESR? (event status register) queries and clears the event register part of the standard event status register. *OPC, *OPC? (operation complete) sets the standard event status register to monitor the completion of all commands.
Page 45: Why Would You Use The Status Registers
Programming Fundamentals Using the Instrument Status Registers Why Would You Use the Status Registers? Your program often needs to be able to detect and manage error conditions or changes in instrument status. There are two methods you can use to programmatically access the information in status registers: •...
Page 46 Programming Fundamentals Using the Instrument Status Registers instrument will monitor that particular bit. If the bit becomes true in the event register, it will stay set until the event register is cleared. Querying the event register allows you to detect that this condition occurred even if the condition no longer exists.
Page 47: Using A Status Register
Programming Fundamentals Using the Instrument Status Registers Using a Status Register Each bit in a register is represented by a numerical value based on its location. See Figure 2-1 below. This number is sent with the command, to enable a particular bit. If you want to enable more than one bit, you would send the sum of all the bits that you are interested in.
Page 48 Programming Fundamentals Using the Instrument Status Registers Generating a Service Request To use the SRQ method, you must understand how service requests are generated. Bit 6 of the status byte register is the request service (RQS) bit. The RQS bit is set whenever something (that it has been conﬁgured to report using *SRE) changes.
Page 49: Overall Status Register System
Programming Fundamentals Using the Instrument Status Registers Overall Status Register System Chapter 2...
Page 50: Status Byte Register
Programming Fundamentals Using the Instrument Status Registers Status Byte Register The RQS bit is read and reset by a serial poll. MSS (the same bit position) is read, non-destructively by the *STB? command. If you serial poll bit 6 it is read as RQS, but if you send *STB it reads bit 6 as MSS. For more information refer to IEEE 488.2 standards, section 11.
Page 51 Programming Fundamentals Using the Instrument Status Registers Description 0, 1 These bits are always set to 0. A 1 in this bit position indicates that the SCPI error queue is not empty. The SCPI error queue contains at least one error message. A 1 in this bit position indicates that the data questionable summary bit has been set.
Page 52 Programming Fundamentals Using the Instrument Status Registers In addition to the status byte register, the status byte group also contains the service request enable register. This register lets you choose which bits in the status byte register will trigger a service request.
Page 53: Standard Event Status Register
Programming Fundamentals Using the Instrument Status Registers Standard Event Status Register The standard event status register contains the following bits: Chapter 2...
Page 54 Programming Fundamentals Using the Instrument Status Registers Description A 1 in this bit position indicates that all pending operations were completed following execution of the *OPC command. This bit is always set to 0. (The instrument does not request control.) A 1 in this bit position indicates that a query error has occurred.
Page 55 Programming Fundamentals Using the Instrument Status Registers will set the summary bit (bit 5 of the status byte register) to 1. Send the *ESE <number> command where <number> is the sum of the decimal values of the bits you want to enable. For example, to enable bit 7 and bit 6 so that whenever either of those bits is set to 1, the standard event status summary bit of the status byte register will be set to 1, send the command *ESE 192 (128 + 64).
Page 56: Operation And Questionable Status Registers
Programming Fundamentals Using the Instrument Status Registers Operation and Questionable Status Registers The operation and questionable status registers are registers that monitor the overall instrument condition. They are accessed with the STATus:OPERation and STATus:QUEStionable commands in the STATus command subsystem. Operation Status Register The operation status register monitors the current instrument measurement state.
Page 57: C Programming Examples Using Vtl
Programming Fundamentals C Programming Examples using VTL C Programming Examples using VTL The programming examples that are provided are written using the C programming language and the HP/Agilent VTL (VISA transition library). This section includes some basic information about programming in the C language. Refer to your C programming language documentation for more details.
Page 58: Linking To Vtl Libraries
Programming Fundamentals C Programming Examples using VTL for the device identiﬁcation (*IDN?). The viScanf call is then used to read the results. This function must be used to close each session. When viClose you close a device session, all data structures that had been allocated for the session will be de-allocated.
Page 59: Example Program
Programming Fundamentals C Programming Examples using VTL 2. Click on the Directories button to set the include ﬁle path. 3. Select Include Files from the Show Directories For list box. 4. Click on the Add button and type in the following: C:\VXIPNP\WIN95\INCLUDE 5.
Page 60: Including The Visa Declarations File
Programming Fundamentals C Programming Examples using VTL /*idn.c - program filename */ #include "visa.h" #include <stdio.h> void main () /*Open session to GPIB device at address 18 */ ViOpenDefaultRM (&defaultRM); ViOpen (defaultRM, “GPIB0::18::INSTR”, VI_NULL, VI_NULL, &vi); /*Initialize device */ viPrintf (vi, “*RST\n”); /*Send an *IDN? string to the device */ printf (vi, “*IDN?\n”);...
Page 61: Device Sessions
Programming Fundamentals C Programming Examples using VTL resource manager session must be opened before any other session can be opened. • A device session is used to communicate with a device on an interface. A device session must be opened for each device you will be using.
Page 62: Addressing A Session
Programming Fundamentals C Programming Examples using VTL sesn This is a session returned from the viOpenDefaultRM function that identiﬁes the resource manager session. rsrcName This is a unique symbolic name of the device (device address). accessMode This parameter is not used for VTL. Use VI_NULL. timeout This parameter is not used for VTL.
Page 63 Programming Fundamentals C Programming Examples using VTL illustrates the format of the rsrcName for the different interface types: Interface Syntax VXI [board]::VXI logical address[::INSTR] GPIB-VXI GPIB-VXI [board]::VXI logical address[::INSTR] GPIB GPIB [board]::primary address[::secondary address][::INSTR] The following describes the parameters used above: board This optional parameter is used if you have more than one interface of the same type.
Page 64: Closing A Session
Programming Fundamentals C Programming Examples using VTL viOpenDefaultRM (&defaultRM); viOpen (defaultRM, “GPIB0::23::INSTR”, VI_NULL,VI_NULL,&vi); viClose(vi); viClose (defaultRM); Closing a Session The viClose function must be used to close each session. You can close the speciﬁc device session, which will free all data structures that had been allocated for the session.
Page 65: Overview Of The Gpib Bus
Programming Fundamentals Overview of the GPIB Bus Overview of the GPIB Bus GPIB Instrument Nomenclature An instrument that is part of an GPIB network is categorized as a listener, talker, or controller, depending on its current function in the network. Listener A listener is a device capable of receiving data or commands from other instruments.
Page 66 Programming Fundamentals Overview of the GPIB Bus causing an instrument to return to local control with a fully enabled front panel (sometimes called: local, resume). • A clear function that causes all GPIB instruments, or addressed instruments, to assume a cleared condition. The deﬁnition of clear is unique for each instrument (sometimes called: clear, reset, control, send).
Page 67: Overview Of The Rs-232 Bus
Programming Fundamentals Overview of the RS-232 Bus Overview of the RS-232 Bus This feature is not implemented. Serial interface programming techniques are similar to most general I/O applications. Refer to your programming language documentation for information on how to initiate the card and verify the status. Due to the asynchronous nature of serial I/O operations, special care must be exercised to ensure that data is not lost by sending to another device before the device is ready to receive.
Page 68: Modem Line Handshaking
Programming Fundamentals Overview of the RS-232 Bus • Stop Bits: One stop bit is included with each character. Modem Line Handshaking To use modem line handshaking for data transfer you would consider the following tasks: 1. Set Data Terminal Ready and Request-to-Send modem lines to active state.
Page 69: Using The Lan To Control The Analyzer
Programming Fundamentals Using the LAN to Control the Analyzer Using the LAN to Control the Analyzer • “The Standard UNIX FTP Command:” on page 69 • “Using Telnet to Send Commands” on page 72 • “Using Socket LAN to Send Commands” on page 76 •...
Page 70 Programming Fundamentals Using the LAN to Control the Analyzer The following options are supported: disables expansion of shell metacharacters in ﬁle and directory names disables prompts during multiple-ﬁle operations disables automatic log-in enables verbose output speciﬁes a new DataSocketBufferSize server-host the name or address of the remote host. Table lists the available user commands.
Page 71 Programming Fundamentals Using the LAN to Control the Analyzer Table 2-1 ftp Commands Command Description quit Closes the connection to the host and exits ftp. Chapter 2...
Page 72: Using Telnet To Send Commands
Programming Fundamentals Using the LAN to Control the Analyzer Using Telnet to Send Commands Using telnet to send commands to your analyzer works in a similar way to communicating over GPIB. You establish a connection with the analyzer, and then send or receive information using SCPI commands. If you need to control the GPIB using “device clear”...
Page 73 Programming Fundamentals Using the LAN to Control the Analyzer and a command prompt. The instrument is now ready to accept your SCPI commands. As you type SCPI commands, query results appear on the next line. When you are done, break the telnet connection using the escape character (in this case Ctrl ]), and type quit.
Page 74 Programming Fundamentals Using the LAN to Control the Analyzer Figure 2-2 Example telnet Session If your telnet connection is in a mode called "line-by-line," there is no NOTE local echo. This means you will not be able to see the characters you are typing on your computer's display until after you press the Enter key.
Page 75 Programming Fundamentals Using the LAN to Control the Analyzer is no local echo. This means you will not be able to see the characters you are typing on your computer's display until after you press the Enter key. To remedy this, you need to change your telnet connection to “character-by-character”...
Page 76: Using Socket Lan To Send Commands
Programming Fundamentals Using the LAN to Control the Analyzer Using Socket LAN to Send Commands Your analyzer implements a sockets Applications Programming Interface (API) compatible with Berkeley sockets, Winsock, and other standard sockets APIs. You can write programs using sockets to control your analyzer by sending SCPI commands to a socket connection you create in your program.
Page 77: Using Sicl Lan To Control The Analyzer
Programming Fundamentals Using the LAN to Control the Analyzer Using SICL LAN to Control the Analyzer SICL LAN is a LAN protocol using the Standard Instrument Control Library (SICL). It provides control of your analyzer over the LAN, using a variety of computing platforms, I/O interfaces, and operating systems. With SICL LAN, you control your remote analyzer over the LAN with the same methods you use for a local analyzer connected directly to the controller with the GPIB.
Page 78 Programming Fundamentals Using the LAN to Control the Analyzer Collecting SICL LAN Set-up Information Before you set up your analyzer as a SICL LAN server, you will need to collect some information about your VISA/SICL LAN client application. The “value” of the following parameters can be found from the front panel keys.
Page 79 Programming Fundamentals Using the LAN to Control the Analyzer These descriptions assume a LAN connection between your computer and network analyzer. They are not written for the GPIB to LAN gateway. 1. Install VISA revision G.02.02 or higher. 2. Run I/O conﬁguration. 3.
Page 80 Programming Fundamentals Using the LAN to Control the Analyzer Figure 2-3 I/O|Instrument Manager Menu 2. Add a new GPIB device with an address of 7XX, where XX is the GPIB device address from your analyzer. Figure 2-4 Adding Your Analyzer as an VEE Device Chapter 2...
Page 81 Programming Fundamentals Using the LAN to Control the Analyzer To send SCPI commands to the analyzer, select I/O|Instrument Manager, and the GPIB device just added. Select Direct I/O. You can now type SCPI commands in the command window, and they are sent over the LAN to your analyzer.
Page 82 Programming Fundamentals Using the LAN to Control the Analyzer Controlling Your Analyzer with SICL LAN and HP/Agilent BASIC for Windows Before you can use HP/Agilent BASIC for Windows with SICL LAN, you need to set up VISA/SICL LAN I/O drivers for use with your BASIC applications.
Page 83 Programming Fundamentals Using the LAN to Control the Analyzer Consult your BASIC documentation to learn how to load the SICL driver for BASIC. After the SICL driver is loaded, you control your analyzer using commands such as the following: OUTPUT 718; “*IDN?” ENTER 718;...
Page 84: Using Hp/Agilent Vee Over Socket Lan
Programming Fundamentals Using the LAN to Control the Analyzer Using HP/Agilent VEE Over Socket LAN To control your analyzer via socket LAN using VEE, click on the VEE menu titled "I/O." Then select "To/From Socket" and position the I/O object box on the screen. Fill in the following ﬁelds: Connect Port: 5025 Host Name:...
Page 85: Using A Java™ Applet Over Socket Lan
Programming Fundamentals Using the LAN to Control the Analyzer Using a Java™ Applet Over Socket LAN The example program “Using Java Programming Over Socket LAN” on page 126 demonstrates simple socket programming with Java. It is written in Java programming language, and will compile with Java compilers versions 1.0 and above.
Page 86: General Lan Troubleshooting
Programming Fundamentals Using the LAN to Control the Analyzer General LAN Troubleshooting • “Troubleshooting the Initial Connection” on page 86 • “Common Problems After You’ve Made the Connection” on page 87 • “Pinging the Analyzer from Your Computer or Workstation” on page •...
Page 87 Programming Fundamentals Using the LAN to Control the Analyzer — /etc/services PCs: — dependent network ﬁles If you know or suspect that something has changed on your network, consult with your network administrator. Timeout Errors Timeout errors such as "Device Timeout," "File Timeout,"...
Page 88 Programming Fundamentals Using the LAN to Control the Analyzer — Make sure the internet (IP) Address of the analyzer is set up correctly in the LAN port setup menu. (Press System, Conﬁg I/O, IP Address — If the analyzer and the computer are on different networks or subnets, make sure the gateway address and subnet mask values are set correctly.
Page 89 Programming Fundamentals Using the LAN to Control the Analyzer always get a new copy of the analyzer’s screen image. If all else fails • Contact your network administrator. • If you still cannot solve the problem, contact an Agilent Service Center for repair information.
Page 90 Programming Fundamentals Using the LAN to Control the Analyzer No Response No packets received indicates no response from a ping. If there is no response, try typing in the IP address with the ping command, instead of using the hostname. Check that the typed address matches the IP address assigned in the System, Conﬁg I/O menu, then check the other addresses in the menu.
Page 91 Programming Fundamentals Using the LAN to Control the Analyzer The number of packets to send before ending ping (1-(2 -1)). count If count is not speciﬁed, ping sends packets until interrupted. EIA/TIA 568B Wiring Information Table 2-2 Straight-Through Cable (Unshielded-twisted-pair (UTP) cable with RJ-45 connectors) Standard, Straight-Through Wiring (each end) Signal Name...
Page 92 Some commercially-available cross-over cables do not implement the NOTE cross-over wiring required for your analyzer. Please refer to Table above, and verify all connections before using cables not made by Agilent Technologies. Figure 2-7 Cross-Over Patch Cable Wiring (cross-over end) Chapter 2...
Page 93: Programming Examples
Programming Examples...
Page 94: Types Of Examples
HP/Agilent VISA transition library. The VISA transition library must be installed and the GPIB card conﬁgured. These examples are available on the Agilent Technologies E4406A documentation CD-ROM. They are also available at the URL http://www.agilent.com/find/vsa The section “C Programming Examples using VTL”...
Page 95: Using Markers
Programming Examples Using Markers Using Markers This C programming example (HPE4406Markers.c): • uses the VISA library for input/output, opens a session to a GP-IB device at address 18 and presets the instrument. • sets the input to the internal 50 MHz reference source and tunes the instrument to the signal.
Page 96: Example
Programming Examples Using Markers Example: #include <stdio.h> #include <stdlib.h> #include <stdmath.h> #include "visa.h" void main () /*program variables*/ ViSession defaultRM, viVSA; ViStatus viStatus = 0; double dPeakPower = 0; double dNoiseMarker = 0; double dResult= 0; long lComplete = 0; /*open session to GPIB device at address 18 */ viStatus=viOpenDefaultRM (&defaultRM);...
Page 97 Programming Examples Using Markers viPrintf(viVSA, "CALC:SPEC:MARK1:MAX\n"); /*query the 50 MHz signal amplitude*/ viPrintf(viVSA, "CALC:SPEC:MARK1:Y?\n"); /*get the 50 MHz signal amplitude*/ viScanf (viVSA,"%lf",&dPeakPower); /*assign marker 2 to the average trace of the spectrum*/ viPrintf(viVSA, "CALC:SPEC:MARK2:TRAC ASP\n"); /*assign the marker function NOISE to marker 2 */ viPrintf(viVSA, "CALC:SPEC:MARK2:FUNC NOISE\n");...
Page 98: Saving Binary Trace Data In An Ascii File
Programming Examples Saving Binary Trace Data in an ASCII File Saving Binary Trace Data in an ASCII File This C programming example (HPE4406Trace.c): • uses the VISA library for input/output, opens a session to a GP-IB device at address 18 and presets the instrument. •...
Page 99 Programming Examples Saving Binary Trace Data in an ASCII File long lNumberPoints = 0; long lNumberBytes = 0; long lComplete = 0; unsigned long lBytesRetrieved; ViReal64 adTraceArray[10240]; /*open session to GPIB device at address 18 */ viStatus=viOpenDefaultRM (&defaultRM); viStatus=viOpen (defaultRM, "GPIB0::18::INSTR", VI_NULL,VI_NULL, &viVSA);...
Page 100 Programming Examples Saving Binary Trace Data in an ASCII File /*get trace header data, in this case we know it's 6 bytes*/ viRead (viVSA,(ViBuf)sTraceBuffer,6,&lBytesRetrieved); /*Extract the number of bytes from the trace header*/ memcpy(sBufferInfo,sTraceBuffer+2,4); lNumberBytes = atoi(sBufferInfo); /*calculate the number of points given the number of bytes in the trace - REAL 64 binary format means each number is represented by 8 bytes*/ lNumberPoints = lNumberBytes/8;...
Page 101: Saving Ascii Trace Data In An Ascii File
Programming Examples Saving ASCII Trace Data in an ASCII File Saving ASCII Trace Data in an ASCII File This C programming example (HPE4406TraceASCII.c): • uses the VISA library for input/output, opens a session to a GP-IB device at address 18 and presets the instrument. •...
Page 102 Programming Examples Saving ASCII Trace Data in an ASCII File /* Reset device */ viPrintf(viVSA, "*RST\n"); /*set the input port to the internal 50MHz reference source*/ viPrintf(viVSA, "SENS:FEED AREF\n"); /*zoom the spectrum display*/ viPrintf(viVSA, "DISP:FORM:ZOOM1\n"); /*tune the instrument to 50MHz*/ viPrintf(viVSA, "SENS:FREQ:CENT 50E6\n");...
Page 103 Programming Examples Saving ASCII Trace Data in an ASCII File of the trace data"); fclose(fTraceFile); /*print message to the standard output*/ printf("The spectrum information was saved to C:\\HPE4406ATraceASCII.txt file\n\n"); /* close session */ viClose (viVSA); viClose (defaultRM); Chapter 3...
Page 104: Saving And Recalling Instrument State Data
Programming Examples Saving and Recalling Instrument State Data Saving and Recalling Instrument State Data This C programming example (HPE4406State.c): • uses the VISA library for input/output, opens a session to a GP-IB device at address 18 and presets the instrument •...
Page 105 Programming Examples Saving and Recalling Instrument State Data /*reset the instrument */ viPrintf(viVSA, "*RST\n"); /*set the input port to the internal 50Mhz reference source*/ viPrintf(viVSA, "SENS:FEED AREF\n"); /*zoom the spectrum display*/ viPrintf(viVSA, "DISP:FORM:ZOOM1\n"); /*tune the instrument to 50MHZ*/ viPrintf(viVSA, "SENS:FREQ:CENT 50E6\n"); /*change the resolution bandwidth*/ viPrintf(viVSA, "SENS:SPEC:BAND:RES 100E3\n");...
Page 106 Programming Examples Saving and Recalling Instrument State Data printf("Notice the abscence of the signal on the display\n"); printf("Press any key to recall the saved state\a\n\t\t------------------------"); /*wait for any key to be pressed*/ getch(); /*recall the state saved in register 10*/ viPrintf(viVSA, "*RCL 10\n");...
Page 107: Performing Alignments And Getting Pass/Fail Results
Programming Examples Performing Alignments and Getting Pass/Fail Results Performing Alignments and Getting Pass/Fail Results This C programming example (HPE4406Align.c): • uses the VISA library for input/output, opens a session to a GP-IB device at address 18 and presets the instrument •...
Page 108 Programming Examples Performing Alignments and Getting Pass/Fail Results /*check for alignement success*/ viScanf (viVSA,"%d",&lCalStatus); /*alignement succeeds if query result is zero(0)*/ if (!lCalStatus) /*print success message to standard output*/ printf("The instrument auto-alignement was successful!\n\n"); else /*print failure message to standard output*/ printf("The instrument auto-alignement was not successful!\n\n");...
Page 109: Using C Programming Over Socket Lan
Programming Examples Using C Programming Over Socket LAN Using C Programming Over Socket LAN This is a C programming example (socketio.c) that demonstrates simple socket programming. It is written in C, and compiles in the HP-UX UNIX environment, or the WIN32 environment. It is portable to other UNIX environments with only minor changes.
Page 110 Programming Examples Using C Programming Over Socket LAN * Query X and Y values of marker 1 and marker 2 (assumes they are on): lanio my4406 'calc:spec:mark1:x?;y?; :calc:spec:mark2:x?;y?' Check for errors (gets one error): lanio my4406 'syst:err?' Send a list of commands from a file, and number them: cat scpi_cmds | lanio -n my4406 **************************************************************************** This program compiles and runs under...
Page 111 Programming Examples Using C Programming Over Socket LAN ifndef _WINSOCKAPI_ include <winsock.h> // BSD-style socket functions endif #else /* UNIX with BSD sockets */ include <sys/socket.h> /* for connect and socket*/ include <netinet/in.h> /* for sockaddr_in include <netdb.h> /* for gethostbyname define SOCKET_ERROR (-1) define INVALID_SOCKET (-1) typedef...
Page 112 Programming Examples Using C Programming Over Socket LAN wVersionRequested = MAKEWORD(1, 1); wVersionRequested = MAKEWORD(2, 0); err = WSAStartup(wVersionRequested, &wsaData); if (err != 0) { /* Tell the user that we couldn't find a useable */ /* winsock.dll. fprintf(stderr, "Cannot initialize Winsock 1.1.\n"); return -1;...
Page 113 Programming Examples Using C Programming Over Socket LAN if (hostPtr == NULL) fprintf(stderr,"unable to resolve hostname '%s'\n", hostname); return INVALID_SOCKET; /*******************/ /* create a socket */ /*******************/ s = socket(AF_INET, SOCK_STREAM, 0); if (s == INVALID_SOCKET) fprintf(stderr,"unable to create socket to '%s': %s\n", hostname, strerror(errno));...
Page 114 Programming Examples Using C Programming Over Socket LAN /* fprintf(stderr, "Sending \"%s\".\n", command); if (strchr(command, '\n') == NULL) { fprintf(stderr, "Warning: missing newline on command %s.\n", command); count = send(sock, command, strlen(command), 0); if (count == SOCKET_ERROR) { return COMMAND_ERROR; return NO_CMD_ERROR;...
Page 115 Programming Examples Using C Programming Over Socket LAN /*********************************************************************** * Simpler UNIX version, using file I/O. recv() version works too. * This demonstrates how to use file I/O on sockets, in UNIX. ***********************************************************************/ FILE * instFile; instFile = fdopen(sock, "r+"); if (instFile == NULL) fprintf(stderr, "Unable to create FILE * structure : %s\n", strerror(errno));...
Page 116 Programming Examples Using C Programming Over Socket LAN ********************************************************/ count = recv(sock, tmp_buf, 1, 0); /* read 1 char */ ch = tmp_buf[0]; if ((count < 1) || (ch == EOF) || (ch == '\n')) *result = '\0'; /* null terminate result for ascii */ return 0;...
Page 117 Programming Examples Using C Programming Over Socket LAN char junk; count = recv(sock, &junk, 1, 0); else /* indefinite block ... dump til we can an extra line feed */ if (recv_line(sock, result, maxLength) == NULL) break; if (strlen(result)==1 && *result == '\n') break; resultBytes += strlen(result);...
Page 118 Programming Examples Using C Programming Over Socket LAN /****************************************************************** * Typical result_str: -221,"Settings conflict; Frequency span reduced." +0,"No error" * Don't bother decoding. ******************************************************************/ if (strncmp(result_str, "+0,", 3) == 0) { /* Matched +0,"No error" */ break; puts(result_str); } while (1); /*************************************************************************** >...
Page 119 Programming Examples Using C Programming Over Socket LAN q = 1 ; return q ; /*************************************************************************** > $Function: main$ * $Description: Read command line arguments, and talk to analyzer. Send query results to stdout. $ * $Return: (int) . . . non-zero if an error occurs ***************************************************************************/ int main(int argc, char *argv[]) SOCKET instSock;...
Page 120 Programming Examples Using C Programming Over Socket LAN if (optind < argc) while (optind < argc) { /* <hostname> <command> provided; only one command string */ strcat(command, argv[optind++]); if (optind < argc) { strcat(command, " "); } else { strcat(command, "\n"); else /* Only <hostname>...
Page 121 Programming Examples Using C Programming Over Socket LAN if ( isQuery(command) ) long bufBytes; bufBytes = queryInstrument(instSock, command, charBuf, INPUT_BUF_SIZE); if (!quiet) fwrite(charBuf, bufBytes, 1, stdout); fwrite("\n", 1, 1, stdout) ; fflush(stdout); else commandInstrument(instSock, command); else /* read a line from <stdin> */ while ( gets(charBuf) != NULL ) if ( !strlen(charBuf) ) continue ;...
Page 122 Programming Examples Using C Programming Over Socket LAN fwrite(" ", 2, 1, stdout) ; fwrite(charBuf + strlen(charBuf)+1, bufBytes, 1, stdout); fwrite("\n", 1, 1, stdout) ; fflush(stdout); else commandInstrument(instSock, charBuf); if (number) number++; if (show_errs) { showErrors(instSock); #ifdef WINSOCK closesocket(instSock); close_winsock(); #else close(instSock);...
Page 123: Using C Programming Over Socket Lan (Windows Nt)
Programming Examples Using C Programming Over Socket LAN (Windows NT) Using C Programming Over Socket LAN (Windows NT) This is a C programming example (getopt.c) that demonstrates simple socket programming. It is written in C, and compiles in the Windows NT environment.
Page 124 Programming Examples Using C Programming Over Socket LAN (Windows NT) ***************************************************************************/ #include <stdio.h> /* For NULL, EOF */ #include <string.h> /* For strchr() */ char *optarg; /* Global argument pointer. */ optind = 0; /* Global argv index. */ static char *scan = NULL;...
Page 125 Programming Examples Using C Programming Over Socket LAN (Windows NT) return(c); Chapter 3...
Page 126: Using Java Programming Over Socket Lan
Programming Examples Using Java Programming Over Socket LAN Using Java Programming Over Socket LAN This is a Java programming example (ScpiDemo.java) that demonstrates simple socket programming with Java. It is written in Java programming language, and will compile with Java compilers versions 1.0 and above.
Page 127 Programming Examples Using Java Programming Over Socket LAN scpiCommand.setFont(font); scpiResponse.appendText("SCPI Demo Program: Response messages\n"); scpiResponse.appendText("--------------------------------------------\n"); // This routine is called whenever the applet is actived public void start() { // Open the sockets if not already opened sck.OpenSockets(); // Start a response thread StartResponseThread(true);...
Page 128 Programming Examples Using Java Programming Over Socket LAN responseThread = null; // Response thread running public void run() { String str = ""; // Initialize str to null // Clear the error queue before starting the thread // in case if there's any error messages from the previous actions while ( str.indexOf("No error") == -1 ) { sck.ScpiWriteLine("syst:err?");...
Page 129 Programming Examples Using Java Programming Over Socket LAN Socks class is responsible for open/close/read/write operations from the predefined socket ports. For this example program, the only port used is 5025 for the SCPI port. class Socks extends java.applet.Applet { // Socket Info // To add a new socket, add a constant here, change MAX_NUM_OF_SOCKETS // then, edit the constructor for the new socket.
Page 130 Programming Examples Using Java Programming Over Socket LAN sockOut[i] = new PrintStream(sock[i].getOutputStream()); if ( (sock[i] != null) && (sockIn[i] != null) && (sockOut[i] != null) ) { sockOpen[i] = true; catch (IOException e) { System.out.println("Sock, Open Error "+e.getMessage()); // Close the socket(s) if opened public void CloseSocket(int s) try { if ( sockOpen[s] == true ) {...
Page 131 Programming Examples Using Java Programming Over Socket LAN if ( SockOpen(SCPI) ) { sockOut[SCPI].println(command); sockOut[SCPI].flush(); // Read an ASCII string, terminated with carriage return from SCPI socket public String ScpiReadLine() try { if ( SockOpen(SCPI) ) { return sockIn[SCPI].readLine(); catch (IOException e) { System.out.println("Scpi Read Line Error "+e.getMessage());...
Page 132 Programming Examples Using Java Programming Over Socket LAN Chapter 3...
Page 133: Programming Command Cross References
Programming Command Cross References...
Page 134: Functional Sort Of Scpi Commands
Programming Command Cross References Functional Sort of SCPI Commands Functional Sort of SCPI Commands Function SCPI Command Subsystems Remarks Averaging SENSe:<measurement>:AVERage Bandwidth SENSe:<measurement>:BWIDth Calibration CALibration Channel: SENSe:CHANnel setting Commands: SYSTem:HELP:HEADers Lists only the commands in listing of all the current selected mode. Data format FORMat:DATA Data types include ASCII...
Page 135 Programming Command Cross References Functional Sort of SCPI Commands Function SCPI Command Subsystems Remarks Input/Output/ INPut:IMPedance Conﬁguration SYSTem:CONFigure SYStem:COMMunicate Markers CALCulate:<measurement>:MARKer: Not all measurements: 1. have markers available 2. have all the documented markers, or all the marker functions. Measurements: ABORt control INITiate:IMMediate...
Page 136 Programming Command Cross References Functional Sort of SCPI Commands Function SCPI Command Subsystems Remarks Preset SYSTem:PRESet: Printing HCOPy: SYSTem:COMMunicate Reference DISPlay:WINDow:TRACe level Save/Recall: DISPlay:IMAGe: display images HCOPy:IMMediate: Save/Recall: *SAV instrument *RCL states Save/Recall: MEASure:<measurement>[n]? Descriptions of the traces trace data FETCh:<measurement>[n]? available for each FORMat:DATA...
Page 137: Language Reference
Language Reference This chapter includes the commands that are common to all of the instrument modes. It also contains the commands unique to the basic and service modes. For commands speciﬁc to a measurement mode, like the GSM personality, look in the GSM Programming Commands chapter.
Page 138: Scpi Command Subsystems
Language Reference SCPI Command Subsystems SCPI Command Subsystems IEEE common commands on page 139 ABORt commands on page 144 CALCulate commands on page 145 CALibration commands on page 159 CONFigure commands on page 172 DISPlay commands on page 173 FETCh commands on page 178 FORMat commands on page 179...
Page 139: Ieee Common Commands
Language Reference IEEE Common Commands IEEE Common Commands These commands are speciﬁed in IEEE Standard 488.2-1992, IEEE Standard Codes, Formats, Protocols and Common Commands for Use with ANSI/IEEE Std 488.1-1987. New York, NY, 1992. Calibration Query *CAL? Performs a full alignment and returns a number indicating the success of the alignment.
Page 140: Standard Event Status Register Query
Language Reference IEEE Common Commands Standard Event Status Register Query *ESR? Queries and clears the standard event status event register. (This is a destructive read.) Range: Integer, 0 to 255 Identiﬁcation Query *IDN? Returns an instrument identiﬁcation information string to GPIB. The string will contain the model number, serial number and ﬁrmware revision.
Page 141: Instrument State Query
Language Reference IEEE Common Commands Instrument State Query *LRN? Returns current instrument state data in a block of deﬁned length. The information is in a machine readable format only. Sending the query returns the following format: SYST:SET #NMMM<state_data> The following example is a response to *LRN? The actual sizes will vary depending on the instrument state data size.
Page 142: Recall
Language Reference IEEE Common Commands Recall *RCL <register> This command recalls the instrument state from the speciﬁed instrument memory register. Range: registers are an integer, 0 to 19 Front Panel Access: File, Recall State Reset *RST This command presets the instrument to a factory deﬁned condition that is appropriate for remote programming operation.
Page 143: Read Status Byte Query
Language Reference IEEE Common Commands Read Status Byte Query *STB? Returns the value of the status byte register without erasing its contents. Remarks: See *CLS Trigger *TRG The desired measurement has been selected and is waiting. The command causes the system to exit this “waiting” state and go to the “initiated”...
Page 144: Abort Subsystem
Language Reference ABORt Subsystem ABORt Subsystem Abort :ABORt Stops any sweep or measurement in progress and resets the sweep or trigger system. A measurement refers to any of the measurements found in the menu. MEASURE If INITiate:CONTinuous is off (single measure), then INITiate:IMMediate will start a new single measurement.
Page 145: Calculate Subsystem
Language Reference CALCulate Subsystem CALCulate Subsystem This subsystem is used to perform post-acquisition data processing. In effect, the collection of new data triggers the CALCulate subsystem. In this instrument, the primary functions in this subsystem are markers and limits. Adjacent Channel Power—Limit Test :CALCulate:ACP:LIMit:STATe OFF|ON|0|1 :CALCulate:ACP:LIMit:STATe? Turn limit test on or off.
Page 146: Calculate/Compress Trace Data Query
Language Reference CALCulate Subsystem Calculate/Compress Trace Data Query :CALCulate:DATA[n]:COMPress? MAXimum|MEAN|MINimum|RMS|SAMPle|SDEViation|CFIT {,<soffset>}{,<length>}{,<roffset>} Returns the designated trace data for the currently selected measurement. The command can be used with sub-opcodes (n) for measurement results that are trace data. See the following table. This command is used to compress/decimate a long trace to extract the desired data and only return to the computer the necessary data.
Page 147 Language Reference CALCulate Subsystem FORMat:DATA command and can return binary or ascii data. History: Added in revision A.03.00 and later Markers Measurement Available Traces Available? ACP - adjacent channel power no traces no markers (Basic, cdmaOne, cdma2000, W-CDMA, iDEN, NADC, PDC modes) BER - bit error rate no traces no markers...
Page 148 Language Reference CALCulate Subsystem Markers Measurement Available Traces Available? ORFSpectrum - output RF spectrum RFEModulation no markers (n=2) (GSM mode) RFESwitching (n=3) PFERror - phase and frequency error PERRor (n=2) (GSM mode) PFERror (n=3) RFENvelope (n=4) PSTatistic - power statistics CCDF MEASured (n=2) (cdma2000, W-CDMA modes) GAUSsian (n=3)
Page 149: Calculate Peaks Of Trace Data
Language Reference CALCulate Subsystem a. The n number indicates the sub-opcode that corresponds to this trace. Detailed descriptions of the trace data can be found in the MEASure subsystem documentation by looking up the sub-opcode for the appropriate measurement. Calculate Peaks of Trace Data :CALCulate:DATA[n]:PEAKs? <threshold>,<excursion>[,AMPLitude|FREQuency|TIME] Returns a list of peaks for the designated trace data n for the currently...
Page 150: Calculate:markers Subsystem
Language Reference CALCulate Subsystem 100 are ignored. Remarks: This command uses the data setting speciﬁed by the FORMat:DATA command and can return real 32-bit, real 64-bit, or ASCII data. The default data format is ASCII. History: Added in revision A.03.00 and later CALCulate:MARKers Subsystem Markers can be put on your displayed measurement data to supply information about speciﬁc points on the data.
Page 151 Language Reference CALCulate Subsystem Example: Suppose you are using the Spectrum measurement. To position marker 2 at the maximum peak value, of the trace that marker 2 is currently on, the command is: :CALCulate:SPECtrum:MARKer2:MAXimum You must make sure that the measurement is completed before trying to query the marker value.
Page 152 Language Reference CALCulate Subsystem Remarks: The keyword for the current measurement must be speciﬁed in the command. (Some examples include: SPECtrum, WAVeform) Front Panel Access: Marker, Marker Function Marker Function Result :CALCulate:<measurement>:MARKer[1]|2|3|4:FUNCtion:RESult? Quires the result of the currently active marker function. The measurement must be completed before querying the marker.A particular measurement may not have all the types of markers available.
Page 153 Language Reference CALCulate Subsystem Marker Peak (Minimum) Search :CALCulate:<measurement>:MARKer[1]|2|3|4:MINimum Places the selected marker on the lowest point on the trace that is assigned to that particular marker number. The marker must have already been assigned to a trace. Use :CALCulate:<measurement>:MARKer[1]|2|3|4:TRACe to assign a marker to a particular trace.
Page 154 Language Reference CALCulate Subsystem Marker On/Off :CALCulate:<measurement>:MARKer[1]|2|3|4[:STATe] OFF|ON|0|1 :CALCulate:<measurement>:MARKer[1]|2|3|4[:STATe]? Turns the selected marker on or off. The marker must have already been assigned to a trace. Use :CALCulate:<measurement>:MARKer[1]|2|3|4:TRACe to assign a marker to a particular trace. Example: CALC:SPEC:MARK2: on Remarks: The keyword for the current measurement must be speciﬁed in the command.
Page 155 Language Reference CALCulate Subsystem Markers Measurement Available Traces Available? ACP - adjacent channel power no traces no markers (Basic, cdmaOne, cdma2000, W-CDMA, iDEN, NADC, PDC modes) BER - bit error rate no traces no markers (iDEN mode) CDPower - code domain power POWer (n=2) (cdmaOne mode) TIMing (n=3)
Page 156 Language Reference CALCulate Subsystem Markers Measurement Available Traces Available? PFERror - phase and frequency error PERRor (n=2) (GSM mode) PFERror (n=3) RFENvelope (n=4) PSTatistic - power statistics CCDF MEASured (n=2) (cdma2000, W-CDMA modes) GAUSian (n=3) REFerence (n=4) PVTime - power versus time RFENvelope (n=2) (GSM, Service modes) UMASK (n=3)
Page 157 Language Reference CALCulate Subsystem Marker X Value :CALCulate:<measurement>:MARKer[1]|2|3|4:X <param> :CALCulate:<measurement>:MARKer[1]|2|3|4:X? Position the designated marker on its assigned trace at the speciﬁed X value. The parameter value is in X-axis units (which is often frequency or time). The marker must have already been assigned to a trace. Use :CALCulate:<measurement>:MARKer[1]|2|3|4:TRACe to assign a marker to a particular trace.
Page 158 Language Reference CALCulate Subsystem Marker X Position :CALCulate:<measurement>:MARKer[1]|2|3|4:X:POSition <integer> :CALCulate:<measurement>:MARKer[1]|2|3|4:X:POSition? Position the designated marker on its assigned trace at the speciﬁed X position. A trace is composed of a variable number of measurement points. This number changes depending on the current measurement conditions.
Page 159: Calibration Subsystem
Language Reference CALibration Subsystem CALibration Subsystem These commands control the self-alignment and self-diagnostic processes. Calibration Abort :CALibration:ABORt Abort any alignment in progress. The query stops any other processing until the abort is complete. Front Panel Access: , when alignment is in progress Align the ADC Auto-range Threshold :CALibration:ADC:ARANge :CALibration:ADC:ARANge?
Page 160: Align The Adc Offset
Language Reference CALibration Subsystem Align the ADC Offset :CALibration:ADC:OFFSet :CALibration:ADC:OFFSet? Align the six ADC offset DACs. This same alignment is run as part of the CAL:ALL routine. Front Panel Access: System, Alignments, Align subsystem, Align ADC Align the ADC RAM Gain :CALibration:ADCRam:GAIN :CALibration:ADCRam:GAIN? Align the gain of the six ADC RAM pages.
Page 161: Automatic Alignment
Language Reference CALibration Subsystem Automatic Alignment :CALibration:AUTO OFF|ALERT|ON :CALibration:AUTO? Turns the automatic alignment routines on and off. When turned on, they are run once every 24 hours, or if the ambient temperature changes by 3 degrees. If the alignment is turned off, the instrument may drift out of speciﬁcation.
Page 162: Calibration Display Detail
Language Reference CALibration Subsystem Calibration Display Detail :CALibration:DISPlay:LEVel OFF|LOW|HIGH :CALibration:DISPlay:LEVel? Controls the amount of detail shown on the display while the alignment routines are running. The routines run faster if they are off, so they do not have to update the display. Off - displays no trace points Low - displays every 10th trace High - displays every trace trace...
Page 163: Auto Adjust The Internal 10 Mhz Frequency Reference
Language Reference CALibration Subsystem Auto Adjust the Internal 10 MHz Frequency Reference :CALibration:FREQuency:REFerence:AADJust Auto adjustment of the internal frequency reference (10 MHz timebase). . Remarks: You must be in the Service mode to use this command. Use INSTrument:SELect. Requires the current measurement to be timebase frequency.
Page 164: Calibrate The Nominal System Gain
Language Reference CALibration Subsystem Calibrate the Nominal System Gain :CALibration:GAIN:CSYStem :CALibration:GAIN:CSYStem? Calculate the current system gain correction for nominal settings. That is, with 10 dB attenuation, 500 MHz center frequency, 0 dB IF gain and the preﬁlter off. Front Panel Access: System, Alignments, Align Subsystem, IF Align the IF...
Page 165: Load The Factory Default Calibration Constants
Language Reference CALibration Subsystem Load the Factory Default Calibration Constants :CALibration:LOAD:DEFault Load the factory default alignment data, ignoring the effect of any alignments already done. Front Panel Access: System, Alignments, Restore Align Defaults Align the Wide LC Preﬁlter :CALibration:PFILter:LCWide :CALibration:PFILter:LCWide? Align the wide LC preﬁlter.
Page 166: Align The Narrow Crystal Prefilter
Language Reference CALibration Subsystem Align the Narrow Crystal Preﬁlter :CALibration:PFILter:XTALNarrow :CALibration:PFILter:XTALNarrow? Align the narrow crystal preﬁlter. (2.5 kHz to 20 kHz) Remarks: A valid service password needs to be entered prior to sending the command. Front Panel Access: Enter service password and press System, Diagnostics Adjust the Level of the 321.4 MHz Alignment Signal :CALibration:REF321...
Page 167: Internal 50 Mhz Amplitude Reference Alignment Control
Language Reference CALibration Subsystem Remarks: You must be in the Service mode to use this command. Use INSTrument:SELect. A valid service password needs to be entered prior to sending this command. Front Panel Access: System Alignments, Align subsystem Align 50 MHz Reference Internal 50 MHz Amplitude Reference Alignment Control...
Page 168: Enter Interactive Mode For Internal 50 Mhz Amplitude Reference Alignment
Language Reference CALibration Subsystem Enter Interactive Mode for Internal 50 MHz Amplitude Reference Alignment :CALibration:REF50:ENTer Turns on the interactive mode for alignment of the internal 50 MHz amplitude reference signal. Use CAL:REF50:ANOW to do the alignment and CAL:REF50:EXIT to exit the interactive mode. Remarks: You must be in the Service mode to use this command.
Page 169: Query The Alc Dac Value For The 50 Mhz Amplitude Reference
Language Reference CALibration Subsystem Front Panel Access: System Alignments, Align subsystem Align 50 MHz Reference Query the ALC DAC Value for the 50 MHz Amplitude Reference :CALibration:REF50:LAST:ALCDac? Query returns the last value of the ALC DAC of the 50 MHz reference alignment.
Page 170: Select The Source For Calibration
Language Reference CALibration Subsystem Select the Source for Calibration :CALibration:SOURce INTernal|EXTernal :CALibration:SOURce? Controls the source of the 50 MHz alignment signal. When it is set to INT, the 50MHz alignment signal is routed through internal circuitry to the analyzers RF input and the front panel RF INPUT connector is disconnected.
Page 171: Align The Trigger Interpolator
Language Reference CALibration Subsystem Align the Trigger Interpolator :CALibration:TRIGger:INTerp :CALibration:TRIGger:INTerp? Align the partial sample trigger interpolator. This same alignment is run as part of the CAL:ALL routine. Front Panel Access: System Alignments, Align subsystem Align 50 MHz Reference Calibration Wait :CALibration:WAIT Waits until any alignment procedure that is underway is completed.
Page 172: Configure Subsystem
Language Reference CONFigure Subsystem CONFigure Subsystem :CONFigure:<measurement> The CONFigure commands are used with several other commands and are documented in the section on the “MEASure Group of Commands” on page 187. Chapter 5...
Page 173: Display Subsystem
Language Reference DISPlay Subsystem DISPlay Subsystem The DISPlay controls the selection and presentation of textual, graphical, and TRACe information. Within a DISPlay, information may be separated into individual WINDows. Display Annotation Title Data :DISPlay:ANNotation:TITLe:DATA <string> :DISPlay:ANNotation:TITLe:DATA? Enters the text that will be displayed in the user title area of the display.
Page 174: Select Display Format
Language Reference DISPlay Subsystem Select Display Format :DISPlay:FORMat:ZOOM Selects the viewing format that displays only one window of the current measurement data (the current active window). Use DISP:FORM:TILE to return the display to multiple windows. Front Panel Access: Zoom Spectrum - Y-Axis Reference Level :DISPlay:SPECtrum[n]:WINDow[m]:TRACe:Y[:SCALe]:RLEVel <power>...
Page 175 Language Reference DISPlay Subsystem about sub-opcodes. Factory Preset and *RST: Range: The valid traces and their sub-opcodes are dependent upon the selected measurement. See the following table. The trace name assignment is independent of the window number. Remarks: To use this command, the appropriate mode should be selected with INSTrument:SELect.
Page 176 Language Reference DISPlay Subsystem Markers Measurement Available Traces Available? EVM - error vector magnitude EVM (n=2) (NADC, PDC modes) MERRor (n=3) PERRor (n=4) EVMQpsk - QPSK error vector EVM (n=2) magnitude MERRor (n=3) (cdma2000, W-CDMA modes) PERRor (n=4) OBW - occupied bandwidth no traces no markers (iDEN, PDC modes)
Page 177: Waveform - Y-Axis Reference Level
Language Reference DISPlay Subsystem Markers Measurement Available Traces Available? SPECtrum - (frequency domain) RFENvelope (n=2) for Service mode (all modes) IQ (n=3) SPECtrum (n=4) ASPectrum (n=7) WAVEform - (time domain) RFENvelope (n=2) (all modes) IQ (n=8) a. The n number indicates the sub-opcode that corresponds to this trace.
Page 178: Fetch Subsystem
Language Reference FETCh Subsystem FETCh Subsystem :FETCh:<measurement>[n]? The FETCh? commands are used with several other commands and are documented in the section on the “MEASure Group of Commands” on page 187. Chapter 5...
Page 179: Format Subsystem
Language Reference FORMat Subsystem FORMat Subsystem The FORMat subsystem sets a data format for transferring numeric and array information. Byte Order :FORMat:BORDer NORMal|SWAPped :FORMat:BORDer? Selects the binary data byte order for data output. It controls whether binary data is transferred in normal or swapped mode. Factory Preset and *RST: Normal...
Page 180 Language Reference FORMat Subsystem Real,32 (or 64) - Binary 32-bit, or 64-bit, real values in amplitude units. Transfers of real data are done in a binary block format. The block of data starts with a header that indicates how many additional data points are following in the block.
Page 181: Hcopy Subsystem
Language Reference HCOPy Subsystem HCOPy Subsystem The HCOPy subsystem controls the setup of plotting and printing to an external device. Print a Hard Copy :HCOPy[:IMMediate] The entire screen is output. Front Panel Access: Print Screen Dump Query :HCOPy:SDUMp:DATA? [GIF|XWD] The query returns the current screen image as a ﬁle. If the optional ﬁle type is not speciﬁed it returns GIF type graphic data.
Page 182: Initiate Subsystem
Language Reference INITiate Subsystem INITiate Subsystem The INITiate subsystem is used to control the initiation of the trigger. Refer to the TRIGger and ABORt subsystems for related commands. Continuous or Single Measurements :INITiate:CONTinuous OFF|ON|0|1 :INITiate:CONTinuous? Selects whether the trigger system is continuously initiated or not. This corresponds to continuous measurement or single measurement operation.
Page 183: Restart The Measurement
Language Reference INITiate Subsystem Restart the Measurement :INITiate:RESTart Restarts the current measurement regardless of its current operating state. It is equivalent to: INITiate[:IMMediate] (for single measurement mode) ABort (for continuous measurement mode) Front Panel Access: Restart Meas Control, Restart Chapter 5...
Page 184: Input Subsystem
Language Reference INPut Subsystem INPut Subsystem The INPut subsystem controls the characteristics of all the instrument input ports. Input Impedance for IQ Input :INPut:IMPedance:IQ 50|600 :INPut:IMPedance:IQ? Select the impedance for the baseband I/Q input. Factory Preset and *RST: 50 Ohm Front Panel Access: Input, I/Q Input Z...
Page 185: Instrument Subsystem
Language Reference INSTrument Subsystem INSTrument Subsystem This subsystem includes commands for querying and selecting instrument measurement (personality option) modes. Catalog Query :INSTrument:CATalog[:FULL]? Returns a comma separated list of strings which contains the names of all installed applications. If the optional FULL keyword is speciﬁed, each name is followed by its associated instrument number, also comma-separated.
Page 186: Select Application
Language Reference INSTrument Subsystem Select Application :INSTrument[:SELect] BASIC|SERVICE|CDMA|GSM :INSTrument[:SELect]? Select the measurement application. The actual available choices depends upon which applications (modes) are installed in the instrument. Once the instrument mode is selected, only the commands that are valid for that mode can be executed. SYSTem:HELP:HEADers? provides a list of the valid commands.
Page 187: Measure Group Of Commands
Language Reference MEASure Group of Commands MEASure Group of Commands This group includes commands used to make measurements and return results. The different commands can be used to provide ﬁne control of the overall measurement process. Most measurements should be done in single measurement mode, rather than doing the measurement continuously.
Page 188: Configure Commands
Language Reference MEASure Group of Commands If you need to change some of the measurement parameters from the factory default settings you can set up the measurement with the CONFigure command. Use the commands in the SENSe:<measurement> and CALCulate:<measurement> subsystems to change the settings.
Page 189: Fetch Commands
Language Reference MEASure Group of Commands Fetch Commands :FETCh:<measurement>[n]? This command puts valid data into the output buffer, but does not initiate data acquisition. Use the INITiate[:IMMediate] command to acquire data before you use the FETCh command. You can only fetch results from the measurement that is currently selected.
Page 190: Adjacent Channel Power Ratio (Acp) Measurement
Language Reference MEASure Group of Commands Adjacent Channel Power Ratio (ACP) Measurement This measures the total rms power in the speciﬁed channel and in 5 offset channels. You must be in Basic, cdmaOne, cdma2000, W-CDMA, iDEN, NADC or PDC mode to use these commands. Use INSTrument:SELect to set the mode.
Page 191 Language Reference MEASure Group of Commands Measurement Results Returned Type Returns 13 comma-separated scalar results, in the following speciﬁed order: or n=1 Center freq – relative power (dB) iDEN Center freq – absolute power (dBm) mode Lower offset freq – relative power (dB) Lower offset freq–...
Page 192 Language Reference MEASure Group of Commands Measurement Results Returned Type Returns 10 comma-separated scalar values of the pass/fail (1=passed, or 0=failed) results determined by testing the NADC and absolute power of the offset frequencies: PDC mode Negative offset frequency(1) absolute power Positive offset frequency(1) absolute power .
Page 193 Language Reference MEASure Group of Commands Measurement Results Returned Type Power spectral Returns 11 comma-separated scalar values (in dBm/Hz) density corresponding to the power spectral density histogram display. Basic, reference The values are returned in ascending frequency order: cdmaOne, cdma2000, Negative offset frequency(5) Negative offset frequency(4) W-CDMA...
Page 194 Language Reference MEASure Group of Commands Measurement Results Returned Type Total power Returns 12 comma-separated scalar values (in dBm) of the reference absolute power of the center and the offset frequencies: Basic, cdmaOne, Center frequency cdma2000, Center frequency Negative offset frequency(1) W-CDMA Positive offset frequency(1) mode...
Page 195 Language Reference MEASure Group of Commands Measurement Results Returned Type Power spectral Returns 12 comma-separated scalar values (power spectral density density in dB) of the power relative to the carrier at the center Basic, reference and offset frequencies: cdmaOne, cdma2000, Center frequency Center frequency W-CDMA...
Page 196 Language Reference MEASure Group of Commands Measurement Results Returned Type Total power Returns 12 comma-separated scalar values of the pass/fail reference (1=passed, or 0=failed) results determined by testing the power Basic, limit relative to the center frequency (measured as total power cdmaOne, spectral in dB): cdma2000,...
Page 197: 50 Mhz Amplitude Reference Measurement
Language Reference MEASure Group of Commands 50 MHz Amplitude Reference Measurement This aligns the internal 50 MHz reference signal to an external reference signal that you supply. You must be in the Service mode to use these commands. Use INSTrument:SELect to set the mode. The general functionality of CONFigure, FETCh, MEASure, and READ are described at the beginning of this section.
Page 198: Channel Power Measurement
Language Reference MEASure Group of Commands Channel Power Measurement This measures the total rms power in a speciﬁed integration bandwidth. You must be in the Basic, cdmaOne mode to use these commands. Use INSTrument:SELect to set the mode. The general functionality of CONFigure, FETCh, MEASure, and READ are described at the beginning of this section.
Page 199: Power Vs. Time Measurement [Vsa-G,S Esa-G]
Language Reference MEASure Group of Commands Power vs. Time Measurement [VSA-G,S ESA-G] This measures the average power during the “useful part” of the burst comparing the power ramp to required timing mask. You must be in GSM or Service mode to use these commands. Use INSTrument:SELect to set the mode.
Page 200 Language Reference MEASure Group of Commands Results Returned not speciﬁed or Returns the following comma-separated scalar results: 1. Sample time is a ﬂoating point number that represents the time between samples when using the trace queries (n=0,2,etc.). 2. Power single burst is the mean power (in dBm) across the useful part of the selected burst in the most recently acquired data, or in the last data acquired at the end of a set of averages.
Page 201: Sensor Measurement
Language Reference MEASure Group of Commands Sensor Measurement This checks the output of three sensors in the RF and IF circuitry. You must be in the Service mode to use these commands. Use INSTrument:SELect to set the mode. The general functionality of CONFigure, FETCh, MEASure, and READ are described at the beginning of this section.
Page 202: Spectrum (Frequency Domain) Measurement
Language Reference MEASure Group of Commands Spectrum (Frequency Domain) Measurement This measures the amplitude of your input signal with respect to the frequency. It provides spectrum analysis capability using FFT (fast Fourier transform) measurement techniques. You must select the appropriate mode using INSTrument:SELect, to use these commands. The general functionality of CONFigure, FETCh, MEASure, and READ are described at the beginning of this section.
Page 203 Language Reference MEASure Group of Commands Results Returned not speciﬁed or Returns the following comma-separated scalar results: 1. FFT peak is the FFT peak amplitude. 2. FFT frequency is the FFT frequency of the peak amplitude. 3. FFT points is the Number of points in the FFT spectrum. 4.
Page 204: Timebase Frequency Measurement
Language Reference MEASure Group of Commands Timebase Frequency Measurement The general functionality of CONFigure, FETCh, MEASure, and READ are described at the beginning of this section. See the SENSe:TBFRequency commands for more measurement related commands. You must be in the Service mode to use these commands. Use INSTrument:SELect to set the mode.
Page 205: Waveform (Time Domain) Measurement
Language Reference MEASure Group of Commands Waveform (Time Domain) Measurement This measures the power in your input signal with respect to time and is equivalent to zero-span operation in a traditional spectrum analyzer. You must select the appropriate mode using INSTrument:SELect, to use these commands.
Page 206 Language Reference MEASure Group of Commands Results Returned not speciﬁed or Returns the following comma-separated scalar results: 1. Sample time is a ﬂoating point number representing the time between samples when using the trace queries (n=0,2,etc). 2. Mean power is the mean power (in dBm). This is either the power across the entire trace, or the power between markers if the markers are enabled.
Page 207: Memory Subsystem
Language Reference MEMory Subsystem MEMory Subsystem The purpose of the MEMory subsystem is to manage instrument memory. This speciﬁcally excludes memory used for mass storage which is deﬁned in the MMEMory Subsystem. Install Application :MEMory:INSTall:APPLication <filename> Installs the speciﬁed application from an external drive to the instrument.
Page 208: Mmemory Subsystem
Language Reference MMEMory Subsystem MMEMory Subsystem The purpose of the MMEMory subsystem is to provide access to mass storage devices such as internal or external disk drives. Any part of memory that is treated as a device will be in the MMEMory subsystem. If mass storage is not speciﬁed in the ﬁlename, the default mass storage speciﬁed in the MSIS command will be used.
Page 209: Read Subsystem
Language Reference READ Subsystem READ Subsystem :READ:<measurement>[n]? The READ? commands are used with several other commands and are documented in the section on the “MEASure Group of Commands” on page 187. Chapter 5...
Page 210: Sense Subsystem
Language Reference SENSe Subsystem SENSe Subsystem Sets the instrument state parameters so that you can measure the input signal. Adjacent Channel Power Measurement Commands for querying the adjacent channel power measurement results and for setting to the default values are found in the “MEASure Group of Commands”...
Page 211 Language Reference SENSe Subsystem Adjacent Channel Power—Averaging Termination Control [:SENSe]:ACP:AVERage:TCONtrol EXPonential|REPeat [:SENSe]:ACP:AVERage:TCONtrol? Select the type of termination control used for averaging. This determines the averaging action after the speciﬁed number of data acquisitions (average count) is reached. Exponential – Each successive data acquisition after the average count is reached, is exponentially weighted and combined with the existing average.
Page 212 Language Reference SENSe Subsystem Adjacent Channel Power—Channel Integration BW Basic, iDEN mode [:SENSe]:ACP:BANDwidth|BWIDth:INTegration <freq> [:SENSe]:ACP:BANDwidth|BWIDth:INTegration? cdmaOne, cdma2000, W-CMDA mode [:SENSe]:ACP:BANDwidth|BWIDth[n]:INTegration[n] <freq> [:SENSe]:ACP:BANDwidth|BWIDth[n]:INTegration[n]? Set the Integration bandwidth that will be used for the main (carrier) channel. Offset[n] n=1 is base station and 2 is mobiles. The default is base station (1).
Page 213 Language Reference SENSe Subsystem Default Unit: Remarks: With measurement type set at (TPR) total power reference, 1.40 MHz is sometimes used. Using 1.23 MHz will give a power that is very nearly identical to the 1.40 MHz value, and using 1.23 MHz will also yield the correct power spectral density with measurement type set at (PSD) reference.
Page 214 Language Reference SENSe Subsystem Adjacent Channel Power—Reference Channel FFT Segments State [:SENSe]:ACP:FFTSegment:AUTO OFF|ON|0|1 [:SENSe]:ACP:FFTSegment:AUTO? The automatic mode selects the optimum number of FFT segments to measure the reference channel (carrier), while making the fastest possible measurement. Factory Preset and *RST: Remarks: You must be in Basic mode to use this command.
Page 215 Language Reference SENSe Subsystem cdmaOne mode n=1 is cellular bands and 2 is pcs bands. The default is cellular. cdma2000 mode n=1 is SR1, 2 is SR3 DS, and 3 is SR3 MC. The default is SR1 (1). W-CDMA mode n=1 is ARIB, 2 is 3GPP, and 3 is Trial. The default is ARIB (1).
Page 216 Language Reference SENSe Subsystem Adjacent Channel Power—Type of Offset Averaging [:SENSe]:ACP:OFFSet:LIST:AVERage:TYPE LOG|MAXimum|MINimum|RMS|SCALar [:SENSe]:ACP:OFFSet:LIST:AVERage:TYPE? Selects the type of averaging to be used for the measurement at each offset. You can turn off (not use) speciﬁc offsets with the SENS:ACP:OFFSet:LIST:STATe command. Factory Preset and *RST: Mode Offset A...
Page 217 Language Reference SENSe Subsystem List[n] cdmaOne mode n=1 is cellular bands and 2 is pcs bands. The default is cellular. cdma2000 mode n=1 is SR1, 2 is SR3 DS, and 3 is SR3 MC. The default is SR1 (1). W-CDMA mode n=1 is ARIB, 2 is 3GPP, and 3 is Trial. The default is ARIB (1).
Page 218 Language Reference SENSe Subsystem Adjacent Channel Power—FFT Segments [:SENSe]:ACP:OFFSet:LIST:FFTSegment <integer>,<integer>,<integer>,<integer>,<integer> [:SENSe]:ACP:OFFSet:LIST:FFTSegment? Selects the number of FFT segments used in making the measurement. In automatic mode the measurement optimizes the number of FFT segments required for the shortest measurement time. The minimum number of segments required to make a measurement is set by your desired measurement bandwidth.
Page 219 Language Reference SENSe Subsystem Adjacent Channel Power—Deﬁne Offset Frequency List iDEN mode [:SENSe]:ACP:OFFSet[:FREQuency] <f_offset> [:SENSe]:ACP:OFFSet[:FREQuency]? Basic mode [:SENSe]:ACP:OFFSet:LIST[:FREQuency] <f_offset>,<f_offset>,<f_offset>,<f_offset>,<f_offset> [:SENSe]:ACP:OFFSet:LIST[:FREQuency]? cdmaOne, cdma2000, W-CDMA mode [:SENSe]:ACP:OFFSet[n]:LIST[n][:FREQuency] <f_offset>,<f_offset>,<f_offset>,<f_offset>,<f_offset> [:SENSe]:ACP:OFFSet[n]:LIST[n][:FREQuency]? Deﬁne the custom set of offset frequencies at which the switching transient spectrum part of the ACP measurement will be made. The list contains ﬁve (5) entries for offset frequencies.
Page 220 Language Reference SENSe Subsystem Mode Variant Offset A Offset B Offset C Offset D Offset E iDEN 25 kHz Basic 750 kHz 1.98 MHz 0 Hz 0 Hz 0 Hz cdmaOne BS cellular 750 kHz 1.98 MHz 0 Hz 0 Hz 0 Hz BS pcs 885 kHz...
Page 221 Language Reference SENSe Subsystem Adjacent Channel Power—Number of Measured Points [:SENSe]:ACP:OFFSet:LIST:POINts <integer>,<integer>,<integer>,<integer>,<integer> [:SENSe]:ACP:OFFSet:LIST:POINts? Selects the number of data points. The automatic mode chooses the optimum number of points for the fastest measurement time with acceptable repeatability. The minimum number of points that could be used is determined by the sweep time and the sampling rate.
Page 222 Language Reference SENSe Subsystem Adjacent Channel Power—Automatic Measurement Points [:SENSe]:ACP:OFFSet:LIST:POINts:AUTO OFF|ON|0|1, OFF|ON|0|1, OFF|ON|0|1, OFF|ON|0|1, OFF|ON|0|1 [:SENSe]:ACP:OFFSet:LIST:POINts:AUTO? Automatically selects the number of points for the optimum measurement speed. Factory Preset and *RST: Mode Offset A Offset B Offset C Offset D Offset E Basic Remarks:...
Page 223 Language Reference SENSe Subsystem the carrier channel. Selecting negative attenuation means that you want less attenuation used. For example, if the measurement must use 20 dB of attenuation for the carrier measurement and you want to use 12 dB less attenuation for the ﬁrst offset, you would send the value −12 dB.
Page 224 Language Reference SENSe Subsystem The query returns ﬁve (5) real numbers that are the current amplitude test limits, relative to the carrier, for each offset. Offset[n] n=1 is base station and 2 is mobiles. The default is base station (1). List[n] cdmaOne mode n=1 is cellular bands and 2 is pcs bands.
Page 225 Language Reference SENSe Subsystem Adjacent Channel Power—Amplitude Limits Relative to the Power Spectral Density iDEN mode [:SENSe]:ACP:OFFSet:RPSDensity <rel_power> [:SENSe]:ACP:OFFSet:RPSDensity? Basic mode [:SENSe]:ACP:OFFSet:LIST:RPSDensity <rel_powr>,<rel_powr>,<rel_powr>,<rel_powr>,<rel_powr> [:SENSe]:ACP:OFFSet:LIST:RPSDensity? cdmaOne, cdma2000, W-CDMA mode [:SENSe]:ACP:OFFSet[n]:LIST[n]:RPSDensity <rel_powr>,<rel_powr>,<rel_powr>,<rel_powr>,<rel_powr> [:SENSe]:ACP:OFFSet[n]:LIST[n]:RPSDensity? Sets the amplitude levels to test against for any custom offsets. This amplitude level is relative to the power spectral density.
Page 226 Language Reference SENSe Subsystem Mode Variant Offset A Offset B Offset C Offset D Offset E iDEN 0 dB −28.87 dB −43.87 dB Basic 0 dB 0 dB 0 dB −28.87 dB −43.87 dB cdmaOne BS cellular 0 dB 0 dB 0 dB −28.87 dB 0 dB...
Page 227 Language Reference SENSe Subsystem Adjacent Channel Power—Control Offset Frequency List Basic mode [:SENSe]:ACP:OFFSet:LIST:STATe OFF|ON|0|1, OFF|ON|0|1, OFF|ON|0|1, OFF|ON|0|1, OFF|ON|0|1 [:SENSe]:ACP:OFFSet:LIST:STATe? cdmaOne, cdma2000, W-CDMA mode [:SENSe]:ACP:OFFSet[n]:LIST[n]:STATe OFF|ON|0|1, OFF|ON|0|1, OFF|ON|0|1, OFF|ON|0|1, OFF|ON|0|1 [:SENSe]:ACP:OFFSet[n]:LIST[n]:STATe? Selects whether testing is to be done at the custom offset frequencies. The measured powers are tested against the absolute values deﬁned with ACP:OFFS[n]:LIST[n]:ABS, or the relative values deﬁned with ACP:OFFS[n]:LIST[n]:RPSD and ACP:OFFS[n]:LIST[n]:RCAR.
Page 228 Language Reference SENSe Subsystem Adjacent Channel Power—Sweep Time [:SENSe]:ACP:OFFSet:LIST:SWEep:TIME <seconds>,<seconds>,<seconds>,<seconds>,<seconds> [:SENSe]:ACP:OFFSet:LIST:SWEep:TIME? Selects a speciﬁc sweep time. If you increase the sweep time, you increase the length of the time data captured and the number of points measured. You might need to specify a speciﬁc sweep speed to accommodate a speciﬁc condition in your transmitter.
Page 229 Language Reference SENSe Subsystem Mode Offset A Offset B Offset C Offset D Offset E Basic Remarks: You must be in Basic mode to use this command. Use INSTrument:SELect to set the mode. History: Revision A.03.00 or later Adjacent Channel Power—Deﬁne Type of Offset Frequency List iDEN mode [:SENSe]:ACP:OFFSet:TEST ABSolute|AND|RELative|OR [:SENSe]:ACP:OFFSet:TEST?
Page 230 Language Reference SENSe Subsystem W-CDMA mode n=1 is ARIB, 2 is 3GPP, and 3 is Trial. The default is ARIB (1). The types of testing that can be done for each offset include: • And - Test both the absolute power measurement and the power relative to the carrier.
Page 231 Language Reference SENSe Subsystem You can increase the length of the measured time record (capture more of the burst) by increasing the number of points, but the measurement will take longer. Use [:SENSe]:ACP:OFFSet:LIST:POINts to set the number of points used for measuring the offset channels. Factory Preset and *RST: 1024...
Page 232 Language Reference SENSe Subsystem History: Revision A.03.27 or later Adjacent Channel Power—Sweep Time [:SENSe]:ACP:SWEep:TIME <seconds> [:SENSe]:ACP:SWEep:TIME? Selects a speciﬁc sweep time used to measure the reference (carrier) channel. If you increase the sweep time, you increase the length of the time data captured and the number of points measured.
Page 233 Language Reference SENSe Subsystem Adjacent Channel Power—Trigger Source [:SENSe]:ACP:TRIGger:SOURce EXTernal[1]|EXTernal2|FRAMe|IF|IMMediate|RFBurst [:SENSe]:ACP:TRIGger:SOURce? Select the trigger source used to control the data acquisitions. External 1 – front panel external trigger input External 2 – rear panel external trigger input Frame – internal frame trigger from front panel input IF –...
Page 234 Language Reference SENSe Subsystem Adjacent Channel Power—Power Reference [:SENSe]:ACP:TYPE TPRef|PSDRef [:SENSe]:ACP:TYPE? Selects the measurement type. This allows you to make absolute and relative power measurements of either total power, or the power normalized to the measurement bandwidth. Total Power Reference - the total power is used as the power reference Power Spectral Density Reference - the power spectral density is used as the power reference...
Page 235: Channel Power Measurement
Language Reference SENSe Subsystem Channel Power Measurement Commands for querying the channel power measurement results and for setting to the default values are found in the “MEASure Group of Commands” on page 187. The equivalent front panel keys for the parameters described in the following commands, are found under the key, after the measurement has been selected...
Page 236 Language Reference SENSe Subsystem Channel Power—Averaging Termination Control [:SENSe]:CHPower:AVERage:TCONtrol EXPonential|REPeat [:SENSe]:CHPower:AVERage:TCONtrol? Select the type of termination control used for the averaging function. This determines the averaging action after the speciﬁed number of data acquisitions (average count) is reached. Exponential - Each successive data acquisition after the average count is reached, is exponentially weighted and combined with the existing average.
Page 237 Language Reference SENSe Subsystem Channel Power—Span [:SENSe]:CHPower:FREQuency:SPAN <freq> [:SENSe]:CHPower:FREQuency:SPAN? Set the frequency span that will be used. Factory Preset and *RST: 2 MHz for Basic, cdma2000, SR1 of cdma2000 5 MHz for SR3 of cdma2000 6 MHz for W-CDMA Range: 1 kHz to 10 MHz Default Unit: Remarks:...
Page 238 Language Reference SENSe Subsystem Channel Power—Data Points Auto [:SENSe]:CHPower:POINts:AUTO OFF|ON|0|1 [:SENSe]:CHPower:POINts:AUTO? Select auto or manual control of the data points. This is an advanced control that normally does not need to be changed. Setting this to a value other than the factory default, may cause invalid measurement results.
Page 239 Language Reference SENSe Subsystem Channel Power—Sweep Time [:SENSe]:CHPower:SWEep:TIME:AUTO OFF|ON|0|1 [:SENSe]:CHPower:SWEep:TIME:AUTO? Selects the automatic sweep time, optimizing the measurement. Factory Preset and *RST: Remarks: You must be in Basic, cdmaOne mode to use this command. Use INSTrument:SELect to set the mode. History: Version A.03.00 and later Channel Power—Trigger Source...
Page 240: Correction For Base Station Rf Port External Attenuation
Language Reference SENSe Subsystem Correction for Base Station RF Port External Attenuation [:SENSe]:CORRection:BS[:RF]:LOSS <rel_power> [:SENSe]:CORRection:BS[:RF]:LOSS? Set the correction equal to the external attenuation used when measuring base stations. Factory Preset and *RST: 0 dB Range: 0 to 100 dB for cdmaOne −50 to 50 dB for Basic, iDEN, NADC or PDC Default Unit: Remarks:...
Page 241: Center Frequency Step Size Automatic
Language Reference SENSe Subsystem and *RST: 1.00 GHz 942.6 MHz for GSM 806 MHz for iDEN Range: 1 kHz to 4.321 GHz Default Unit: Front Panel Access: FREQUENCY/Channel, Center Freq Center Frequency Step Size Automatic [:SENSe]:FREQuency:CENTer:STEP:AUTO OFF|ON|0|1 [:SENSe]:FREQuency:CENTer:STEP:AUTO? Speciﬁes whether the step size is set automatically based on the span. Factory Preset and *RST: History:...
Page 242: Rf Port Input Attenuation
Language Reference SENSe Subsystem RF Port Input Attenuation [:SENSe]:POWer[:RF]:ATTenuation <rel_power> [:SENSe]:POWer[:RF]:ATTenuation? Set the RF input attenuator. This value is set at its auto value if input attenuation is set to auto. Factory Preset and *RST: 0 dB 12.0 dB for iDEN Range: 0 to 40 dB Default Unit:...
Page 243: Power Vs. Time (Burst Power) Measurement
Language Reference SENSe Subsystem Power vs. Time (Burst Power) Measurement Commands for querying the power versus time measurement results and for setting to the default values are found in the “MEASure Group of Commands” on page 187. The equivalent front panel keys for the parameters described in the following commands, are found under the key, after the measurement has been selected...
Page 244 Language Reference SENSe Subsystem Power vs. Time—Averaging Mode [:SENSe]:PVTime:AVERage:TCONtrol EXPonential|REPeat [:SENSe]:PVTime:AVERage:TCONtrol? Select the type of termination control used for the averaging function. This speciﬁes the averaging action after the speciﬁed number of bursts (average count) is reached. Exponential - Each successive data acquisition after the average count is reached, is exponentially weighted and combined with the existing average.
Page 245 Language Reference SENSe Subsystem Power vs. Time—Resolution BW [VSA-G,S, ESA-G] [:SENSe]:PVTime:BANDwidth|BWIDth[:RESolution] <freq> [:SENSe]:PVTime:BANDwidth|BWIDth[:RESolution]? Set the resolution BW. This is an advanced control that normally does not need to be changed. Setting this to a value other than the factory default, may cause invalid measurement results. Factory Preset and *RST: 500 kHz...
Page 246 Language Reference SENSe Subsystem Power vs. Time—Sweep Time [:SENSe]:PVTime:SWEep:TIME <integer> [:SENSe]:PVTime:SWEep:TIME? Set the number of slots which are used in each data acquisition. Each slot is approximately equal to 570 ms. The measurement is made for a small additional amount of time (about 130 µs) in order to view the burst edges.
Page 247: Reference Oscillator External Frequency
Language Reference SENSe Subsystem Reference Oscillator External Frequency [:SENSe]:ROSCillator:EXTernal:FREQuency <frequency> [:SENSe]:ROSCillator:EXTernal:FREQuency? Set to the frequency of the external reference oscillator being supplied to the instrument. Switch to the external reference with ROSC:SOUR. Option oscillator commands, if applicable, are found as SENSe:OPTion:ROSCillator.
Page 248: Reference Oscillator Source
Language Reference SENSe Subsystem Reference Oscillator Source [:SENSe]:ROSCillator:SOURce INTernal|EXTernal [:SENSe]:ROSCillator:SOURce? Select the reference oscillator (time base) source. Use ROSC:EXT:FREQ to tell the instrument the frequency of the external reference. Option oscillator commands, if applicable, are found as SENSe:OPTion:ROSCillator. (ESA?) Internal - uses internal 50 MHz reference signal External - uses the signal at the rear panel external reference input port.
Page 249: Spectrum (Frequency-Domain) Measurement
Language Reference SENSe Subsystem Spectrum (Frequency-Domain) Measurement Commands for querying the spectrum measurement results and for setting to the default values are found in the “MEASure Group of Commands” on page 187. The equivalent front panel keys for the parameters described in the following commands, are found under the key, after the measurement has been Meas Setup...
Page 250 Language Reference SENSe Subsystem Spectrum—ADC Range [:SENSe]:SPECtrum:ADC:RANGe AUTO|APEak|APLock|M6|P0|P6|P12|P18|P24| [:SENSe]:SPECtrum:ADC:RANGe? Select the range for the gain-ranging that is done in front of the ADC. This is an advanced control that normally does not need to be changed. Auto peak ranging is the default for this measurement. If you are measuring a CW signal please see the description below.
Page 251 Language Reference SENSe Subsystem Spectrum—Average Clear [:SENSe]:SPECtrum:AVERage:CLEAr The average data is cleared and the average counter is reset. Remarks: To use this command, the appropriate mode should be selected with INSTrument:SELect. Spectrum—Number of Averages [:SENSe]:SPECtrum:AVERage:COUNt <integer> [:SENSe]:SPECtrum:AVERage:COUNt? Set the number of ‘sweeps’ that will be averaged. After the speciﬁed number of ‘sweeps’...
Page 252 Language Reference SENSe Subsystem Spectrum—Averaging Mode [:SENSe]:SPECtrum:AVERage:TCONtrol EXPonential|REPeat [:SENSe]:SPECtrum:AVERage:TCONtrol? Select the type of termination control used for the averaging function. This determines the averaging action after the speciﬁed number of ‘sweeps’ (average count) is reached. Exponential - Each successive data acquisition after the average count is reached, is exponentially weighted and combined with the existing average.
Page 253 Language Reference SENSe Subsystem Spectrum—Pre-ADC Bandpass Filter [:SENSe]:SPECtrum:BANDwidth|BWIDth:PADC OFF|ON|0|1 [:SENSe]:SPECtrum:BANDwidth|BWIDth:PADC? Turn the pre-ADC bandpass ﬁlter on or off. This is an advanced control that normally does not need to be changed. Remarks: To use this command, the appropriate mode should be selected with INSTrument:SELect.
Page 254 Language Reference SENSe Subsystem Spectrum—Pre-FFT BW Filter Type [:SENSe]:SPECtrum:BANDwidth|BWIDth:PFFT:TYPE FLAT|GAUSsian [:SENSe]:SPECtrum:BANDwidth|BWIDth:PFFT:TYPE? Select the type of pre-FFT ﬁlter that is used. This is an advanced control that normally does not need to be changed. Flat top- a ﬁlter with a ﬂat amplitude response, which provides the best amplitude accuracy.
Page 255 Language Reference SENSe Subsystem Spectrum—Resolution BW Auto [:SENSe]:SPECtrum:BANDwidth|BWIDth[:RESolution]:AUTO OFF|ON|0|1 [:SENSe]:SPECtrum:BANDwidth|BWIDth[:RESolution]:AUTO? Select auto or manual control of the resolution BW. The automatic mode couples the resolution bandwidth setting to the frequency span. Factory Preset and *RST: Off, for iDEN mode Remarks: To use this command, the appropriate mode should be selected with INSTrument:SELect.
Page 256 Language Reference SENSe Subsystem Spectrum—FFT Length [:SENSe]:SPECtrum:FFT:LENGth <integer> [:SENSe]:SPECtrum:FFT:LENGth? Set the FFT length. This value is only used if length control is set to manual. The value must be greater than or equal to the window length value. Any amount greater than the window length is implemented by zero-padding.
Page 257 Language Reference SENSe Subsystem Spectrum—Window Delay [:SENSe]:SPECtrum:FFT:WINDow:DELay <real> [:SENSe]:SPECtrum:FFT:WINDow:DELay? Set the FFT window delay to move the FFT window from its nominal position of being centered within the time capture. This function is not available from the front panel. It is an advanced control that normally does not need to be changed.
Page 258 Language Reference SENSe Subsystem Spectrum—FFT Window [:SENSe]:SPECtrum:FFT:WINDow[:TYPE] BH4Tap|BLACkman|FLATtop|GAUSsian|HAMMing|HANNing|KB70|KB90 |KB110|UNIForm [:SENSe]:SPECtrum:FFT:WINDow[:TYPE]? Select the FFT window type. BH4Tap - Blackman Harris with 4 taps Blackman - Blackman Flat Top - ﬂat top, the default (for high amplitude accuracy) Gaussian - Gaussian with alpha of 3.5 Hamming - Hamming Hanning - Hanning KB70, 90, and 110 - Kaiser Bessel with sidelobes at −70, −90, or −110...
Page 259 Language Reference SENSe Subsystem Spectrum—Sweep (Acquisition) Time [:SENSe]:SPECtrum:SWEep:TIME <time> [:SENSe]:SPECtrum:SWEep:TIME? Set the sweep (measurement acquisition) time. It is used to specify the length of the time capture record. If the speciﬁed value is less than the capture time required for the speciﬁed span and resolution bandwidth, the value is ignored.
Page 260 Language Reference SENSe Subsystem Spectrum—Trigger Source [:SENSe]:SPECtrum:TRIGger:SOURce EXTernal[1]|EXTernal 2|FRAMe|IF|LINE|IMMediate|RFBurst [:SENSe]:SPECtrum:TRIGger:SOURce? Select the trigger source used to control the data acquisitions. External 1 - front panel external trigger input External 2 - rear panel external trigger input Frame - internal frame timer from front panel input IF - internal IF envelope (video) trigger Line - internal line trigger Immediate - the next data acquisition is immediately taken (also...
Page 261: Waveform (Time-Domain) Measurement
Language Reference SENSe Subsystem Waveform (Time-Domain) Measurement Commands for querying the waveform measurement results and for setting to the default values are found in the “MEASure Group of Commands” on page 187. The equivalent front panel keys for the parameters described in the following commands, are found under the key, after the measurement has Meas Setup...
Page 262 Language Reference SENSe Subsystem Waveform—ADC Range [:SENSe]:WAVeform:ADC:RANGe AUTO|APEak|APLock|GROund|M6|P0|P6|P12|P18|P24| [:SENSe]:WAVeform:ADC:RANGe? Select the range for the gain-ranging that is done in front of the ADC. This is an Advanced control that normally does not need to be changed. Auto - automatic range Auto Peak - automatically peak the range Auto Peak Lock - automatically peak lock the range Ground - ground...
Page 263 Language Reference SENSe Subsystem Waveform—Averaging Mode [:SENSe]:WAVeform:AVERage:TCONtrol EXPonential|REPeat [:SENSe]:WAVeform:AVERage:TCONtrol? Select the type of termination control used for the averaging function. This determines the averaging action after the speciﬁed number of ‘sweeps’ (average count) is reached. Exponential - Each successive data acquisition after the average count is reached, is exponentially weighted and combined with the existing average.
Page 264 Language Reference SENSe Subsystem Waveform—Resolution BW [:SENSe]:WAVeform:BANDwidth|BWIDth[:RESolution] <freq> [:SENSe]:WAVeform:BANDwidth|BWIDth[:RESolution]? Set the resolution bandwidth. This value is ignored if the function is auto-coupled. Factory Preset and *RST: 100 kHz, for NADC, PDC, cdma2000, W-CDMA, basic, service mode 500 kHz, for GSM mode 2 MHz.
Page 265 Language Reference SENSe Subsystem Decimation of Waveform Display [:SENSe]:WAVeform:DECimate[:FACTor] <integer> [:SENSe]:WAVeform:DECimate[:FACTor]? Set the amount of data decimation done by the hardware and/or the ﬁrmware. For example, if 4 is selected, three out of every four data points will be thrown away. So every 4th data point will be kept. Factory Preset and *RST: Range:...
Page 266 Language Reference SENSe Subsystem Waveform—Trigger Source [:SENSe]:WAVeform:TRIGger:SOURce EXTernal[1]| EXTernal2|FRAMe|IF|IMMediate|LINE|RFBurst [:SENSe]:WAVeform:TRIGger:SOURce? Select the trigger source used to control the data acquisitions. External 1 - front panel external trigger input External 2 - rear panel external trigger input Frame - internal frame timer from front panel input IF - internal IF envelope (video) trigger Immediate - the next data acquisition is immediately taken (also called free run)
Page 267: Status Subsystem
Language Reference STATus Subsystem STATus Subsystem The STATus subsystem controls the SCPI-deﬁned status-reporting structures. Operation Condition Query :STATus:OPERation:CONDition? This query returns the decimal value of the sum of the bits in the Status Operation Condition register. The data in this register is continuously updated and reﬂects the NOTE current conditions.
Page 268: Operation Event Query
Language Reference STATus Subsystem Operation Event Query :STATus:OPERation[:EVENt]? This query returns the decimal value of the sum of the bits in the Operation Event register. The register requires that the equivalent PTR or NTR ﬁlters be set NOTE before a condition register bit can set a bit in the event register. The data in this register is latched until it is queried.
Page 269: Questionable Calibration Condition
Language Reference STATus Subsystem Questionable Calibration Condition :STATus:QUEStionable:CALibration:CONDition? This query returns the decimal value of the sum of the bits in the Questionable Calibration Condition register. The data in this register is continuously updated and reﬂects the NOTE current conditions. Questionable Calibration Enable :STATus:QUEStionable:CALibration:ENABle <number>...
Page 270: Questionable Calibration Negative Transition
Language Reference STATus Subsystem Questionable Calibration Negative Transition :STATus:QUEStionable:CALibration:NTRansition <number> :STATus:QUEStionable:CALibration:NTRansition? This command determines what bits in the Questionable Calibration Condition register will set the corresponding bit in the Questionable Calibration Event register when that bit has a negative transition (1 to 0).
Page 271: Questionable Enable
Language Reference STATus Subsystem Questionable Enable :STATus:QUEStionable:ENABle <number> :STATus:QUEStionable:ENABle? This command determines what bits in the Questionable Condition Register will set bits in the Questionable Event register, which also sets the Questionable Status Summary bit (bit3) in the Status Byte Register.
Page 272: Questionable Frequency Enable
Language Reference STATus Subsystem Questionable Frequency Enable :STATus:QUEStionable:FREQuency:ENABle <number> :STATus:QUEStionable:FREQuency:ENABle? This command determines what bits in the Questionable Frequency Condition Register will set bits in the Questionable Frequency Event register, which also sets the Frequency Summary bit (bit 5) in the Questionable Register.
Page 273: Questionable Frequency Positive Transition
Language Reference STATus Subsystem Questionable Frequency Positive Transition :STATus:QUEStionable:FREQuency:PTRansition <number> :STATus:QUEStionable:FREQuency:PTRansition? This command determines what bits in the Questionable Frequency Condition register will set the corresponding bit in the Questionable Frequency Event register when that bit has a negative transition (1 to 0).
Page 274: Questionable Integrity Event Query
Language Reference STATus Subsystem Questionable Integrity Event Query :STATus:QUEStionable:INTegrity[:EVENt]? This query returns the decimal value of the sum of the bits in the Questionable Integrity Event register. The register requires that the equivalent PTR or NTR ﬁlters be set NOTE before a condition register bit can set a bit in the event register.
Page 275: Questionable Integrity Signal Condition
Language Reference STATus Subsystem Questionable Integrity Signal Condition :STATus:QUEStionable:INTegrity:SIGNal:CONDition? This query returns the decimal value of the sum of the bits in the Questionable Integrity Signal Condition register. The data in this register is continuously updated and reﬂects the NOTE current conditions.
Page 276: Questionable Integrity Signal Positive Transition
Language Reference STATus Subsystem Factory Preset and *RST: 0, factory default. (The user setting is persistant.) Range: 0 to 32767 Questionable Integrity Signal Positive Transition :STATus:QUEStionable:INTegrity:SIGNal:PTRansition <number> :STATus:QUEStionable:INTegrity:SIGNal:PTRansition? This command determines what bits in the Questionable Integrity Signal Condition register will set the corresponding bit in the Questionable Integrity Signal Event register when that bit has a negative transition (1 to 0).
Page 277: Questionable Power Enable
Language Reference STATus Subsystem Questionable Power Enable :STATus:QUEStionable:POWer:ENABle <number> :STATus:QUEStionable:POWer:ENABle? This command determines what bits in the Questionable Power Condition Register will set bits in the Questionable Power Event register, which also sets the Power Summary bit (bit 3) in the Questionable Register.
Page 278: Questionable Power Positive Transition
Language Reference STATus Subsystem Questionable Power Positive Transition :STATus:QUEStionable:POWer:PTRansition <number> :STATus:QUEStionable:POWer:PTRansition?> This command determines what bits in the Questionable Power Condition register will set the corresponding bit in the Questionable Power Event register when that bit has a negative transition (1 to 0). The variable <number>...
Page 279: Questionable Temperature Enable
Language Reference STATus Subsystem Questionable Temperature Enable :STATus:QUEStionable:TEMPerature:ENABle <number> :STATus:QUEStionable:TEMPerature:ENABle? This command determines what bits in the Questionable Temperature Condition Register will set bits in the Questionable Temperature Event register, which also sets the Temperature Summary bit (bit 4) in the Questionable Register.
Page 280: Questionable Temperature Positive Transition
Language Reference STATus Subsystem Questionable Temperature Positive Transition :STATus:QUEStionable:TEMPerature:PTRansition <number> :STATus:QUEStionable:TEMPerature:PTRansition? This command determines what bits in the Questionable Temperature Condition register will set the corresponding bit in the Questionable Temperature Event register when that bit has a negative transition (1 to 0).
Page 281: System Subsystem
Language Reference SYSTem Subsystem SYSTem Subsystem This subsystem is used to set the controls and parameters associated with the overall system communication. These are functions that are not related to instrument performance. Examples include functions for performing general housekeeping and functions related to setting global conﬁgurations.
Page 282: Hardware Configuration Query
Language Reference SYSTem Subsystem Hardware Conﬁguration Query :SYSTem:CONFigure:DEFault Resets all instrument functions to the factory defaults, including the persistent functions. Persistent functions are system settings, such as I/O bus addresses and preset preferences, that stay at their current settings even through instrument power-on. Table 5-1 Factory Defaults for persistent Functions Function...
Page 283: Error Information Query
Language Reference SYSTem Subsystem Error Information Query :SYSTem:ERRor[:NEXT]? This command queries the earliest entry to the error queue and then deletes that entry. *CLS clears the entire error queue. Front Panel Access: System, Show Errors Exit Main Firmware for Upgrade :SYSTem:EXIT Exit the main ﬁrmware to allow the ﬁrmware to be upgraded.
Page 284: License Key For Installing New Applications
Language Reference SYSTem Subsystem License Key for Installing New Applications :SYSTem:LKEY <“option”>,<“license key”> :SYSTem:LKEY? <“option”> Enter the license key required for installing the speciﬁed new application (mode). The query returns a string that contains the license key for a speciﬁed application that is already installed in the instrument.
Page 285: Service Password
Language Reference SYSTem Subsystem Service Password :SYSTem:PASSword[:CENable]<string> Enables access to the service functions by means of the password. Front Panel Access: System, More, More, Service Preset :SYSTem:PRESet Returns the instrument to a set of deﬁned conditions. This command does not change any persistent parameters. Front Panel Access: Preset...
Page 286: Adjust Time
Language Reference SYSTem Subsystem Adjust Time :SYSTem:TIME:ADJust <seconds> Adjust the time by the positive or negative value entered, within the allowed range. Range: Larger than you should ever need Example: SYST:TIME:ADJ 3600 will advance the time one hour. SYST:TIME:ADJ -86400 will back the date up one day, without changing the time of day (minutes or seconds).
Page 287: Trigger Subsystem
Language Reference TRIGger Subsystem TRIGger Subsystem The Trigger Subsystem is used to set the controls and parameters associated with triggering the data acquisitions. Other trigger-related commands are found in the INITiate and ABORt subsystems. The trigger parameters are global within the selected Mode. The Trigger Source selection is local to each measurement, so there is a separate Trigger Source command for each measurement, which is in the SENSe subsystem.
Page 288: Automatic Trigger Time
Language Reference TRIGger Subsystem Automatic Trigger Time :TRIGger[:SEQuence]:AUTO[:TIME] <number> :TRIGger[:SEQuence]:AUTO[:TIME]? The instrument will take a data acquisition immediately upon receiving a signal from the selected trigger source. If no trigger signal is received by the end of the time speciﬁed in this command, a data acquisition is taken anyway.
Page 289: Front Panel External Trigger Level
Language Reference TRIGger Subsystem Front Panel External Trigger Level :TRIGger[:SEQuence]:EXTernal[1]:LEVel <level> :TRIGger[:SEQuence]:EXTernal[1]:LEVel? Set the trigger level when using the front panel external trigger input. Factory Preset and *RST: 2.0 V −5.0 to +5.0 V Range: Default Unit: volts Front Panel Access: Mode Setup, Trigger, Ext Front, Level Front Panel External Trigger Slope...
Page 290: Rear Panel External Trigger Level
Language Reference TRIGger Subsystem Rear Panel External Trigger Level :TRIGger[:SEQuence]:EXTernal2:LEVel <level> :TRIGger[:SEQuence]:EXTernal2:LEVel? Set the trigger level when using the rear panel external trigger input. Factory Preset and *RST: 2.0 V −5.0 to +5.0 V Range: Default Unit: volts Front Panel Access: Mode Setup, Trigger, Ext Rear, Level Rear Panel External Trigger Slope...
Page 291: Frame Trigger Period
Language Reference TRIGger Subsystem Frame Trigger Period :TRIGger[:SEQuence]:FRAMe:PERiod <time> :TRIGger[:SEQuence]:FRAMe:PERiod? Set the frame period that you want when using the external frame timer trigger. If the trafﬁc rate is changed, the value of the frame period is initialized to the preset value. Factory Preset 250 µs for Basic, cdmaOne and *RST:...
Page 292: Frame Trigger Syncronization Offset
Language Reference TRIGger Subsystem Frame Trigger Syncronization Offset :TRIGger[:SEQuence]:FRAMe:SYNCmode:ADJust <time> Lets you adjust the frame triggering with respect to the external trigger input that you are using. Factory Preset and *RST: 0 to 10 s Range: 33 ns to 559 ms for cdma2000, W-CDMA Default Unit: seconds Remarks:...
Page 293: Video (If) Trigger Delay
Language Reference TRIGger Subsystem Video (IF) Trigger Delay :TRIGger[:SEQuence]:IF:DELay <time> :TRIGger[:SEQuence]:IF:DELay? Set the trigger delay when using the IF (video) trigger (after the Resolution BW ﬁlter). Factory Preset and *RST: −500 ms to 500 ms Range: −100 ms to 500 ms for cdma2000, W-CDMA Default Unit: seconds Front Panel...
Page 294: Video (If) Trigger Slope
Language Reference TRIGger Subsystem Video (IF) Trigger Slope :TRIGger[:SEQuence]:IF:SLOPe POSitive|NEGative :TRIGger[:SEQuence]:IF:SLOPe? Sets the trigger slope when using the IF (video) trigger. Factory Preset and *RST: Positive Front Panel Access: Mode Setup, Trigger, Video (IF Envlp), Slope RF Burst Trigger Delay :TRIGger[:SEQuence]:RFBurst:DELay <time>...
Page 295: Rf Burst Trigger Level
Language Reference TRIGger Subsystem RF Burst Trigger Level :TRIGger[:SEQuence]:RFBurst:LEVel <percent> :TRIGger[:SEQuence]:RFBurst:LEVel? Set the trigger level when using the RF Burst (wideband) Trigger. The value is relative to the peak of the signal. RF Burst is also known as RF Envelope. Factory Preset −6.0 dB and *RST:...
Page 296 Language Reference TRIGger Subsystem Chapter 5...
Page 297: Error Messages
Error Messages...
Page 298: Error Queues
Error Messages Error Queues Error Queues If an error condition occurs in the instrument, it may be reported to both the history error queue (front panel display) and the SCPI error queue (remote interface). These two queues are viewed and managed separately.
Page 299 Error Messages Error Queues annunciator will appear only if the external reference has been activated by the user. ESec (even second clock) - The green ESec annunciator indicates that the external even second clock has been selected as the sync type and a sync signal is present at the even second input (rear panel Trigger In), and the measurement is using it as the demodulation sync type.
Page 300 Error Messages Error Queues parentheses) show the number of times the error has occurred since the queue was last cleared. Chapter 6...
Page 301: Scpi Remote Interface Error Messages
Error Messages Error Queues SCPI Remote Interface Error Messages Remote Error Queue This queue is constructed in a linear ﬁrst-in/ﬁrst-out fashion. It can hold up to 30 error messages. As errors and events are detected, they are placed in the queue. Unlike the history error queue, errors in this queue are not overwritten by the latest incoming error messages.
Page 302: Clearing The Error Queue
Error Messages Error Queues Clearing the Error Queue The error queue will only be cleared upon: • power up • receipt of a *CLS command • reading the last error from the queue No Error When all the errors have been read from the queue, further error queries will return: (0) No error This message indicates that the error queue contains no errors.
Page 303: Error Message Descriptions
Error Messages Error Message Descriptions Error Message Descriptions Messages with No Numbers Unnumbered messages are for operator information only and do not appear in any error queue. Description Acquiring Data... A warning used when the data acquisition time is long enough to be noticeable.
Page 304: Query Error Messages
Error Messages Error Message Descriptions A warning used when the hardware settling time is long enough to be noticeable. Sync is RF ampl (not Training Seq). Bits not accurate. Query Error Messages [−499 to −400] An error number in the range [−499 to −400] indicates the instrument has found a problem when trying to respond to a SCPI query.
Page 305 Error Messages Error Message Descriptions 6.3 has occurred. Chapter 6...
Page 306: Device-Specific Error Messages
Error Messages Error Message Descriptions Device-Speciﬁc Error Messages [−399 to −300] An error number in the range [−399 to −300] indicates that the instrument has detected an error where some device operations did not properly complete, possibly due to an abnormal hardware or ﬁrmware condition.
Page 307 Error Messages Error Message Descriptions (-321) Out of memory Indicates that an internal operation needed more memory than was available. If this occurs during a memory catalog display, it means the system did not have enough free RAM to prepare the catalog.
Page 308: Execution Error Messages
Error Messages Error Message Descriptions Execution Error Messages [−299 to −200] An error number in the range [−299 to −200] indicates that an error has been detected during instrument execution. The occurrence of any error in this class will cause the execution error bit (bit 4) in the event status register to be set.
Page 309 Error Messages Error Message Descriptions (-284) Program currently running Indicates that certain operation related to programs may be illegal while the program is running (for example, deleting a running program may be illegal). (-283) Illegal variable name Indicates that an attempt was made to reference a nonexistent variable.
Page 310 Error Messages Error Message Descriptions (-274) Macro parameter error Indicates that the macro deﬁnition improperly used a macro parameter place holder (see IEEE 488.2, 10.7.3). (-273) Illegal macro label Indicates that the macro label deﬁned in the *DMC command was a legal string syntax, but could not be accepted by the device (see IEEE 488.2, 10.7.3 and 10.7.6.2) (for example, the label was too long, the same as a common command header, or contained invalid...
Page 311 The instrument is likely not functioning properly. Report this error to the nearest Agilent Technologies Sales and Service ofﬁce. Refer to the Sales and Service Ofﬁce table in the user’s guide for your instrument.
Page 312 Error Messages Error Message Descriptions (-233) Invalid version Indicates that a legal program data element was parsed but could not be executed because the version of the data is incorrect to the device. This particular error is used when ﬁle or block data elements are recognized by the instrument, but cannot be executed for reasons of version incompatibility (for example, a non-supported ﬁle version or a non-supported instrument version).
Page 313 Error Messages Error Message Descriptions (-221) Settings conflict Indicates that a legal program data element was parsed but could not be executed due to the current device state (see IEEE 488.2 11.5.1.1.5). (-220) Parameter error Indicates that a program data element related error has occurred.
Page 314 Error Messages Error Message Descriptions (-201) Invalid while in local Indicates that a command is not executable while the device is in local mode due to a hard local control (see IEEE 488.2, 5.6.1.5) (for example, a device with a rotary switch receives a message which would change the switch’s state, but the device is in local, so the message cannot be executed).
Page 315: Command Error Messages
Error Messages Error Message Descriptions Command Error Messages [−199 to −100] An error number in the range [−199 to −100] indicates that an IEEE 488.2 syntax error has been detected by the instrument’s parser. The occurrence of any error in this class will cause the command error bit (bit 5) in the event status register to be set.
Page 316 Error Messages Error Message Descriptions This error also occurs if a command is executed that is not valid for the current selected instrument mode. Use INSTrument:SELect to change the mode. (-170) Expression data error This error is generated when parsing an expression data element.
Page 317 Error Messages Error Message Descriptions (-141) Invalid character data Either the character data element contains an invalid character or the particular element received is not valid for the header. (-140) Character data error This error is generated when parsing a character data element.
Page 318 Error Messages Error Message Descriptions (-120) Numeric data error This error is generated when parsing a data element which appears to be numeric, including non-decimal numeric types. This particular error message is used if the device cannot detect a more speciﬁc error. (-114) Header suffix out of range The value of a header sufﬁx attached to a program...
Page 319 Error Messages Error Message Descriptions (-105) GET not allowed A Group Execute Trigger was received within a program message (see IEEE 488.2, 7.7). Correct the GPIB controller program so that the GET does not occur within a line of GPIB program code. (-104) Data type error The parser recognized a data element that is not...
Page 320: Instrument-Specific Error Messages
Error Messages Error Message Descriptions Instrument-Speciﬁc Error Messages [positive numbers] Some instrument-speciﬁc error messages use the existing negative or “generic” SCPI error numbers with the addition of device-dependent or instrument-speciﬁc information following the semicolon in the error message. A positive error number indicates that the instrument has detected an error within the GPIB system, within the instrument ﬁrmware or hardware, during the transfer of block data, or during calibration.
Page 321 Error Messages Error Message Descriptions Analog IF sample rate osc unlocked The 30 MHz sample rate oscillator on the A12 analog IF assembly is unlocked. Even second clock failing The even second clock is unlocked. No application file Catalog incomplete Application not licensed License key “word”...
Page 322 Error Messages Error Message Descriptions (16) Input Overload Decrease max total power in input. Excessive input power has been detected which will cause the ADC to clip the signal. Reduce the signal level, change the attenuator/max total power setting (under menu), or press if the Input...
Page 323 Error Messages Error Message Descriptions (26) Oven temp low The oven-controlled crystal oscillator is not at the desired operating temperature. (27) Alignment Needed The Auto Align routine needs to be run. At least 24 hours has passed since the last full alignment, or the temperature has changed 6°...
Page 324: Gsm-Specific Error Messages
Error Messages Error Message Descriptions GSM-Speciﬁc Error Messages [100 to 199] An error number in the range [100 to 199] indicates the instrument has detected an error relating to the GSM personality. GSM-Speciﬁc Error Message Descriptions (Number) Description (100) Not enough data to fit into GSM mask An attempt to position a GSM trace into the mask, when not enough data was present.
Page 325 Error Messages Error Message Descriptions (110) Sync word not found In a GSM measurement using demodulation, the training sequence code (sync word) could not be found. (111) Signal too noisy In a GSM measurement, indicates that a burst could not be found in a signal that appears noisy. (112) Incorrect trigger holdoff - set to 0 sec (113)
Page 326: Cdma-Specific Error Messages
Error Messages Error Message Descriptions CDMA-Speciﬁc Error Messages [200 to 299] An error number in the range [200 to 299] indicates the instrument has detected an error relating to the CDMA personality. CDMA-Speciﬁc Error Message Descriptions (Number) Description (200) Signal near noise floor - Power accuracy degraded (201) Signal exceeds maximum allowable power -...
Page 327: Nadc-Specific Error Messages
Error Messages Error Message Descriptions NADC-Speciﬁc Error Messages [300 to 399] An error number in the range [300 to 399] indicates the instrument has detected an error relating to the NADC personality. NADC-Speciﬁc Error Message Descriptions (Number) Description (300) Sync word not found In an EVM measurement, the sync word is not found and the synchronization cannot be established when is selected in the...
Page 328: Pdc-Specific Error Messages
Error Messages Error Message Descriptions PDC-Speciﬁc Error Messages [400 to 499] An error number in the range [400 to 499] indicates the instrument has detected an error relating to the PDC personality. PDC-Speciﬁc Error Message Descriptions (Number) Description (400) Sync word not found In an EVM measurement, the sync word is not found and the synchronization cannot be established when is selected in the...
Page 329 Index Symbols SPECtrum basic mode commands WAVeform BASIC programming *CLS adjacent channel power binary data order *ESE measurement burst trigger *ESR? level *SRE adjacent channel power ratio *STB? measurement See also ACPR LAN cable Numerics adjust timebase frequency bus conﬁguration 10 MHz reference adjustment adjustment byte order of data...
Page 330 Index trigger interpolation continuous measurement dithering the ADC calibration commands continuous vs. single domain name calibration condition register measurement mode control measurement commands CDMA echo, lack of measurements available controling via LAN enable register remove the mode controller service request understanding measurements correction error...
Page 331 Index external reference GSM installation instrument states External Reference error GSM measurement programming example annunciator instrument status external trigger monitoring delay monitoring status monitoring hardware status level host identiﬁcation query slope instrument-speciﬁc errors HP 13242G Cable positive numbers HP 24542G/H Cable integrity condition register HP 24542M Cable factory default for persistent...
Page 332 Index loading an measurements available in application/personality different modes packet errors local echo, lack of measurment, programming one packing LRN, IEEE command SPECtrum memory available parsing block data output memory commands data output, identifying block memory, instrument commands size markers pass/fail test assigning them to traces minimum value of trace data...
Page 333 Index reference selection for calibration parameters Java using multiple commands socket LAN reference, selecting internal valid commands programming register sensors, temperature command syntax calibration condition serial bus commands for desired functions frequency condition serial number, query service mode creating a simple program integrity condition measurements available example using C language...
Page 334 Index enable register time standard event status byte setting enable and read time domain measurement event status byte enable and read, timebase frequency accuracy VEE programing socket LAN measurement view commands timeout errors VISA library standard event status register, timing control IEEE command title display start measurement...

Agilent Technologies E4406A VSA Series Programmer's Manual

1 Preparing for Use

2 Programming Fundamentals

3 Programming Examples

4 Programming Command Cross References

5 Language Reference

6 Error Messages

Quick Links

Related Manuals for Agilent Technologies E4406A VSA Series

Summary of Contents for Agilent Technologies E4406A VSA Series