Download Print this page

HP 8935 Programmer's Manual

Cdma cellular/pcs base station test set

page of 492

/ 492
Contents
Table of Contents
Bookmarks

Advertisement

Quick Links

Download this manual

HP 8935 CDMA Cellular/PCS Base Station Test Set

This document, part number E6380-90018, is a preliminary manual.

Updates will be available six months from the date of this manual. If you would like an updated version when it

becomes available, please send us the following information:

Name_______________________________________________________________________JobTitle_______________________

Company__________________________________ Address_____________________________________________

Phone______________________________________E-mail_________________________________________________________

This document is on (circle one): CD-ROM

E-Mail: karen_otto@hp.com

Fax: HP 8935 Updates, Karen Otto, 509-921-3700

Snail Mail: HP 8935 Updates, Karen Otto, Hewlett-Packard Company, 24001E. Mission Avenue, Liberty La,

WA, 99019

www.valuetronics.com

Programmer's Guide

Firmware Version: A.01.00 and above

HP Part Number E6380-90018

Revision A

Printed in U.S.A.

November 1997

PRELIMINARY

Paper

© Copyright 1997 Hewlett-Packard Company

Main Menu

Table of Contents

Advertisement

Chapters

Need help?

Need help?

Do you have a question about the 8935 and is the answer not in the manual?

Questions and answers

Summary of Contents for HP 8935

Page 1 This document is on (circle one): CD-ROM Paper E-Mail: karen_otto@hp.com Fax: HP 8935 Updates, Karen Otto, 509-921-3700 Snail Mail: HP 8935 Updates, Karen Otto, Hewlett-Packard Company, 24001E. Mission Avenue, Liberty La, WA, 99019 © Copyright 1997 Hewlett-Packard Company Main Menu...
Page 2 Notice Information contained in this document is subject to change without notice. All Rights Reserved. Reproduction, adaptation, or translation without prior written permission is prohibited, except as allowed under the copyright laws. This material may be reproduced by or for the U.S. Government pursuant to the Copyright License under the clause at DFARS 52.227-7013 (APR 1988).
Page 3: Manufacturer's Declaration
Manufacturer’s Declaration This statement is provided to comply with the requirements of the German Sound Emission Directive, from 18 January 1991. This product has a sound pressure emission (at the operator position) < 70 dB(A). Sound Pressure Lp < 70 dB(A). At Operator Position.
Page 4 Safety GENERAL This product and related documentation must be reviewed for familiarization with safety markings and instructions before operation. This product has been designed and tested in accordance with IEC Publication 1010, "Safety Requirements for Electronic Measuring Apparatus," and has been supplied in a safe condition. This instruction documentation contains information and warnings which must be followed by the user to ensure safe operation and to maintain the product in a safe condition.
Page 5 • Do not use extension cord to connect this product to power receptacle. Attention-ne pas utiliser de rallonge pour raccorder le detecteur-disjoncteur a la prise de courant. • Replace cordset only with HP 8120 series. Attention - Remplacer uniquement par un cordon amovible numero 8120.
Page 6 The opening of covers or removal of parts is likely to expose dangerous voltages. Disconnect the product from all voltage sources while it is being opened. Adjustments described in the manual are performed with power supplied to the instrument while protective covers are removed.
Page 7 Product Markings CE - the CE mark is a registered trademark of the European Community. A CE mark accompanied by a year indicated the year the design was proven. CSA - the CSA mark is a registered trademark of the Canadian Standards Association.
Page 8: Warranty
For warranty service or repair, this product must be returned to a service facility designated by HP. Buyer shall prepay shipping charges to HP and HP shall pay shipping charges, duties, and taxes for products returned to HP from another country.
Page 9 ASSISTANCE Maintenance Agreements Product maintenance agreements and other customer assistance agreements are available for Hewlett-Packard products. For any assistance, contact your nearest Hewlett-Packard Sales and Service Office. Main Menu www.valuetronics.com...
Page 10: Regional Sales Offices
Regional Sales Offices IMPORTANT Regional Sales and Service Offices Eastern USA Eastern USA Midwestern USA Sales Office Sales Office Sales and Service Hewlett-Packard Company Hewlett-Packard Company Hewlett-Packard Company 2101 Gather Rd. 2101 Gather Rd. 5201 Tollview Drive Rockville, MD 20850 Rockville, MD 20850 Rolling Meadows, IL 60008 Tel: (301) 258-2000...
Page 11 Asia Japan International Sales Branch Headquarters Sales and Service Sales and Service Sales and Service Hewlett-Packard Asia Ltd. Yokogawa-Hewlett-Packard Ltd. Hewlett-Packard S.A. 22-30/F Peregrine Tower 3-29-21, Takaido-Higashi 39 Rue Veyrot Lippo Center Suginami-Ku, Tokyo 168 P.O. Box 365 89 Queensway, Central Telephone: 81 3 3331-6111 1217 Meyrin 1 Hong Kong...
Page 12 Main Menu www.valuetronics.com...
Page 13: Table Of Contents
HP BASIC ‘ON TIMEOUT’ Example Program ....50 HP BASIC ‘MAV’ Example Program ......54 HP-IB Command Guidelines Sequential and Overlapped Commands .
Page 14 Text Only HP-IB Errors ........455...
Page 15 Contents Numbered HP-IB Error Descriptions ......457 Main Menu www.valuetronics.com...
Page 16 Contents Main Menu www.valuetronics.com...
Page 17: In This Manual
In This Manual This manual explains how to use the HP 8935 to manually test a CDMA Base Station. What is Discussed This Manual This document presents a step-by-step approach to CDMA base station testing using the Test Set, including what you need to know before you can start testing.
Page 18 Which Document is The following documents are part of the HP 8935 document set. Use the Required? table to help you decide which document you need. Table 1 Document Navigation Document Part Number Usage CDMA Application E6380-90016 Use this manual for basic CDMA measurements Guide and for getting started with the Test Set.
Page 19: Using Hp-Ib
Using HP-IB Main Menu www.valuetronics.com...
Page 20: Overview Of The Test Set
Test Set’s functions can be automatically controlled through application programs running on the built-in IBASIC Controller or on an external controller connected through HP-IB. Developing programs for the Test Set is simplified if the programmer has a basic understanding of how the Test Set operates. An overview of the Test Set’s operation is best presented in terms of how information...
Page 21: Manual Control Mode
An HP-IB/RS-232/Parallel Printer interface is located in the Test Set. In Manual Control mode this provides the capability of connecting an external HP-IB, serial, or parallel printer to the Test Set so that display screens can be printed. Chapter 1 PRELIMINARY Main Menu www.valuetronics.com...
Page 22 IBASIC Controller when an IBASIC program is running. These include the serial interface ports at select codes 9, 10, and 11, the HP-IB interface at select code 7, the parallel printer interface ports at select codes 15 and 16, and the display. In Manual...
Page 23 , for communicating with the internal figure 1-2 instruments of the Test Set. This HP-IB interface is only available to the IBASIC Controller. There is no external connector for this HP-IB interface. No external instruments may be added to this HP-IB interface.
Page 24 Using HP-IB Overview of the Test Set Writing programs for the Test Set One of the design goals for automatic control of the Test Set was that it operate the same way programmatically as it does manually. This is a key point to remember when developing programs for the Test Set.
Page 25 Using HP-IB Overview of the Test Set Figure 1-1 Manual Control Mode Chapter 1 PRELIMINARY Main Menu www.valuetronics.com...
Page 26 Using HP-IB Overview of the Test Set Figure 1-2 Internal Automatic Control Mode Chapter 1 PRELIMINARY Main Menu www.valuetronics.com...
Page 27: Getting Started
• An external controller, connected to the external HP-IB, can remotely control the Test Set. • An HP-IB printer, connected to the external HP-IB, can be used to print test results and full screen images. HP-IB Information Provided in This Manual What Is Explained •...
Page 28 1. Refer to the Tutorial Description of the Hewlett-Packard Interface Bus (HP P/N 5952-0156) for detailed information on HP-IB theory and operation. 2. Refer to the HP Instrument BASIC Users Handbook (HP P/N E2083-90005) for more information on the IBASIC Version 2.0 language.
Page 29 OFF, the measurement will not be available. Attempting to read from a measurement field that is not in the ON state will cause HP-IB Error:−420 Query UNTERMINATED. 5. If the trigger mode has been changed, trigger a reading.
Page 30 Using HP-IB Getting Started The following example program illustrates how to make settings and then take a reading from the Test Set. This setup takes a reading from the spectrum analyzer marker after tuning it to the RF generator’s output frequency.
Page 31 AF Anl In field to FM or AM Demod. • Guideline #3. The syntax diagrams in show chapter 5, "HP-IB Command Dictionary," where single quotes are needed and where spaces are needed. Example OUTPUT 714;"DISP<space>AFAN" OUTPUT 714;"AFAN:DEMP<space>’Off’" Improper use of single quotes and spaces will cause, HP-IB Error:−103 Invalid Separator...
Page 32: Control Annunciators
Guideline #4. When making settings to fields that can be turned OFF with the STATe ON/OFF command (refer to the Chapter 5, "HP-IB Command ), make sure the STATe is ON if the program uses that Dictionary" field. Note that if the STATe is OFF, just setting a numeric value in the field will not change the STATe to ON.
Page 33 Refer to for further information. "Passing Control" on page 337 3. If an HP-IB printer is or will be connected to the Test Set’s HP-IB connector then, a. access the PRINT CONFIGURE screen. b. select one of the supported HP-IB printer models using the Model field.
Page 34 Using the HP-IB with the Test Set’s built-in IBASIC Controller The Test Set has two HP-IB interfaces, an internal-only HP-IB at select code 8 and an external HP-IB at select code 7. The HP-IB at select code 8 is only available to the built-in IBASIC Controller and is used exclusively for communication between the IBASIC Controller and the Test Set.
Page 35 Command Dictionary" The bus address 714 used in the following BASIC language examples assumes an HP-IB interface at select code 7, and a Test Set HP-IB address of 14. All examples assume an external controller is being used. To Change a Field’s Setting over HP-IB 1.
Page 36 Using HP-IB Getting Started When querying measurements or settings through HP-IB, the Test Set NOTE always returns numeric values in HP-IB Units or Attribute Units, regardless of the current Display Units setting. Refer to "HP-IB Units for further (UNITs)" on page 68 "Attribute Units (AUNits)"...
Page 37: Remote Operation
Remote Operation Remote Operation The Test Set can be operated remotely through the Hewlett-Packard Interface Bus (HP-IB). Except as otherwise noted, the Test Set complies with the IEEE 488.1-1987 and IEEE 488.2-1987 Standards. Bus compatibility, programming and data formats are described in the following sections.
Page 38: Remote Capabilities
Using HP-IB Remote Operation Remote Capabilities Conformance to the IEEE 488.1-1987 Standard For all IEEE 488.1 functions implemented, the Test Set adheres to the rules and procedures as outlined in that Standard. Conformance to the IEEE 488.2-1987 Standard For all IEEE 488.2 functions implemented, the Test Set adheres to the rules and procedures as outlined in that Standard with the exception of the *OPC Common Command.
Page 39: Addressing
I/O CONFIGURE screen. To set the HP-IB bus address; select the I/O CONFIGURE screen and position the cursor next to the HP-IB Adrs field. The address can be set from decimal 0 to 30 using the numeric DATA keys, or by pushing and then rotating the Cursor Control knob.
Page 40: Ieee 488.1 Remote Interface Message Capabilities
Using HP-IB IEEE 488.1 Remote Interface Message Capabilities IEEE 488.1 Remote Interface Message Capabilities The remote interface message capabilities of the Test Set and the associated IEEE 488.1 messages and control lines are listed in table 1 Chapter 1 PRELIMINARY Main Menu www.valuetronics.com...
Page 41 Using HP-IB IEEE 488.1 Remote Interface Message Capabilities Table 1 Test Set IEEE 488.1 Interface Message Capability IEEE 488.1 Message Type Implemented Response Message Data All front-panel functions, except those listed in table 1-2 on 36, are page programmable. The...
Page 42 Using HP-IB IEEE 488.1 Remote Interface Message Capabilities IEEE 488.1 Message Type Implemented Response Message Local The Test Set returns to local mode (full front-panel control) when either the Go To Local (GTL) bus command is received, the front-panel LOCAL key is pressed or the REN line goes false.
Page 43 Using HP-IB IEEE 488.1 Remote Interface Message Capabilities IEEE 488.1 Message Type Implemented Response Message Service Request The Test Set sets the Service Request (SRQ) bus line true if any of the enabled conditions in the Status Byte Register, as defined by...
Page 44 Using HP-IB IEEE 488.1 Remote Interface Message Capabilities IEEE 488.1 Message Type Implemented Response Message Clear This message clears the Input Buffer and Output Queue, clears any commands in process, puts the Test Set into the Operation Complete idle state...
Page 45 Using HP-IB IEEE 488.1 Remote Interface Message Capabilities IEEE 488.1 Message Type Implemented Response Message Trigger If in remote programming mode and addressed to listen, the Test Set makes a triggered measurement following the trigger conditions currently in effect in the instrument.
Page 46: Remote/Local Modes
Using HP-IB Remote/Local Modes Remote/Local Modes Remote Mode In Remote mode all front-panel keys are disabled (except for the LOCAL key, POWER switch, Volume control and Squelch control). The LOCAL key is only disabled by the Local Lockout bus command. When in Remote mode and addressed to Listen the Test Set responds to the Data, Remote, Local, Clear (SDC), and Trigger messages.
Page 47: Local To Remote Transitions
If the HP-IB trigger mode is :RETR REP then a new measurement cycle is started and measurement results will be available for all active measurements when valid results have been obtained.
Page 48: Clear Lockout/Set Local
Using HP-IB Remote/Local Modes Local Lockout The Local Lockout mode disables the front-panel LOCAL key and allows return to Local mode only by commands from the System Controller (Clear Lockout/Set Local message). When a data transmission to the Test Set is interrupted, which can happen if the LOCAL key is pressed, the data being transmitted may be lost.
Page 49 Methods For Reading Measurement Results Main Menu www.valuetronics.com...
Page 50: Methods For Reading Measurement Results Background
This situation can be avoided entirely by: 1. sending a Selected Device Clear (SDC) interface message to put the Test Set’s HP-IB subsystem into a known state. 2. sending a command to terminate the requested measurement cycle. These commands issued in this order will allow the control program to regain control of the Test Set.
Page 51 Methods For Reading Measurement Results Background The following programs demonstrate a recommended technique for querying and entering data from the Test Set. This technique will prevent the Test Set from getting into a ‘hung’ state such that power must be cycled on the Test Set to regain manual or programmatic control.
Page 52: Hp Basic 'On Timeout' Example Program
The following example program demonstrates a recommended technique which can be utilized in situations where a measurement result timeout value of 32.767 seconds or less is adequate. In the HP RMB language, the timeout parameter for the ON TIMEOUT command has a maximum value of 32.767 seconds.
Page 53 Methods For Reading Measurement Results HP BASIC ‘ON TIMEOUT’ Example Program Timeout Example COM /Io_names/ INTEGER Inst_addr,Bus_addr CLEAR SCREEN Inst_addr=714 Bus_addr=7 CLEAR Inst_addr OUTPUT Inst_addr;"TRIG:ABORT" OUTPUT Inst_addr;"*RST" OUTPUT Inst_addr;"DISP RFAN" 100 ! Execute a call to the Measure function with a request to measure RF 110 ! power.
Page 54 TIMEOUT) to ensure that the Measure function will not be exited until it is finished. Set up a timeout for any I/O activity on the HP-IB. This will allow the function to recover if the bus hangs for any reason.
Page 55 Methods For Reading Measurement Results HP BASIC ‘ON TIMEOUT’ Example Program Program Line Comments Number Command the Test Set to abort the currently executing measurement cycle. Set the trigger mode back to repetitive retriggering. Setting the Test Set back to repetitive retriggering will be implementation dependent.
Page 56: Hp Basic 'Mav' Example Program
Queue. A polling loop is used to query the Status byte. The timeout duration for returning the measurement result is handled by the polling loop. An HP-IB interface activity timeout is also set up to handle time-outs resulting from problems with the HP-IB interface.
Page 57 Methods For Reading Measurement Results HP BASIC ‘MAV’ Example Program MAV Example COM /Io_names/ INTEGER Inst_addr,Bus_addr CLEAR SCREEN Inst_addr=714 Bus_addr=7 CLEAR Inst_addr OUTPUT Inst_addr;"TRIG:ABORT" OUTPUT Inst_addr;"*RST" OUTPUT Inst_addr;"DISP RFAN" 100 ! Execute a call to the Measure function with a request to measure RF 110 ! power.
Page 58 TIMEOUT) to ensure that the Measure function will not be exited until it is finished. Set up a 5 second timeout for any I/O activity on the HP-IB. This will allow the function to recover if the bus hangs for any reason. The length of the timeout will be implementation dependent.
Page 59 Set up a timeout for any I/O activity on the HP-IB while the control program is trying to regain control of the Test Set. This will allow the function to gracefully stop program execution if the control program cannot regain control of the Test Set.
Page 60 Methods For Reading Measurement Results HP BASIC ‘MAV’ Example Program Chapter 2 PRELIMINARY Main Menu www.valuetronics.com...
Page 61: Hp-Ib Command Guidelines
HP-IB Command Guidelines Main Menu www.valuetronics.com...
Page 62: Sequential And Overlapped Commands
The process of executing a command can be divided into three steps: 1. Command is accepted from HP-IB and checked for proper structure and parameters. 2. Commands is sent to instrument hardware.
Page 63: Guidelines For Operation
Guidelines for Operation Guidelines for Operation The following topics discuss rules and guidelines for controlling the Test Set through HP-IB. Command Names All command names of more than four characters have an alternate abbreviated form using only upper case letters and, in some cases, a single numeral.
Page 64: Command Punctuation
HP-IB commands use the same hierarchy. The colon (:) is used to separate the different levels of the command hierarchy.
Page 65 Multiple commands can be output from one program line by separating the commands with a semicolon (;). The semicolon tells the Test Set’s HP-IB command parser to back up one level of hierarchy and accept the next command at the same level as the previous command.
Page 66 MHz…). When operating the Test Set manually, the units-of-measure can be easily changed to display measurement results and field settings in the most convenient format. HP-IB operation is similar to manual operation in that the units-of-measure used to display numeric data can be programmatically changed to the most convenient form.
Page 67 HP-IB Command Guidelines Guidelines for Operation Display Units (DUNits) Display Units are the units-of-measure used by the Test Set to display numeric data (field settings and measurement results) on the front-panel CRT display. For example, the RF Generator’s frequency can be displayed in Hz, kHz, MHz and GHz. Similarly, the measured TX Frequency can be displayed in Hz, kHz, MHz and GHz.
Page 68 HP-IB Command Guidelines Guidelines for Operation :MEAS:RFR:POW:DUN MV µV :RFG:AMPL:DUN µV dBµV :RFG:AMPL:DUN DBµV :MEAS:RFR:POW:DUN W :MEAS:RFR:POW:DUN MW :MEAS:RFR:POW:DUN DBM :MEAS:AFR:DISTN:DUN DB :MEAS:AFR:DISTN:DUN PCT :DEC:FGEN:GATE:DUN S :DEC:FGEN:GATE:DUN MS Reading Back Display Units Setting. Use the Display Units query command, DUNits?, to read back the current Display Units setting. For...
Page 69 HP-IB Command Guidelines Guidelines for Operation • When querying a field’s setting or measurement result through HP-IB, the Test Set always returns numeric values in HP-IB Units or Attribute Units, regardless of the field’s current Display Units setting. • The Display Units for a field’s setting or measurement result can be set to any valid unit-of-measure, regardless of the field’s HP-IB...
Page 70 (field settings and measurement results) through HP-IB, and the default units-of-measure for receiving numeric data (field settings and measurement results) through HP-IB. Changing HP-IB Units has no affect on the Display Units or Attribute Units settings. lists the HP-IB Units used in the Test Set.
Page 71 Frequency Error HZ or PPM For example, the following BASIC language program statements change the HP-IB Units for the TX Power measurement from W to dBm: Example OUTPUT 714;"MEAS:RFR:POW:UNIT DBM" Reading-Back HP-IB Units. Use the UNITs? command to read back the current HP-IB Units setting for a measurement or instrument setup field.
Page 72 Test Set. For example, if the command RFG:FREQ 900 is sent through HP-IB, the Test Set will interpret the data as 900 Hz, since HZ is the HP-IB Unit for frequency. This would result in an Input value out of range error.
Page 73 HP-IB Command Guidelines Guidelines for Operation Parameter Unit of Measure Relative Level decibels (DB) or percent (PCT) Marker Position Division (DIV) FM Modulation Hertz (HZ) AM Modulation Percent (PCT) Default Data Function Values. The majority of measurements made with the Test Set can be made using the Data Functions: REF SET, METER, AVG, HI LIMIT and LO LIMIT.
Page 74 • the power is cycled on the Test Set • the front-panel PRESET key is selected • the *RST Common Command is received through HP-IB Changing Attribute Units. The AUNits command can be used to change the Attribute Units setting for selected measurements. Only the Attribute Units for power and relative level measurements can be changed.
Page 75 3. set the Attribute Units to DB 4. then query the value of each Data Function The units of measure for the returned values will be DB. Display Units and HP-IB Units are not affected when changing Attribute Units. Example !Reset the Test Set OUTPUT 714;"*RST"...
Page 76 Guidelines for Attribute Units. • When setting the value of measurement functions REFerence, METer, HLIMit and LLIMit through HP-IB, a non–Attribute Unit unit-of-measure must be specified in the command string, otherwise the current Attribute Unit is assumed by the Test Set.
Page 77 HP-IB Units settings. Numeric values are expressed in scientific notation. For example, if the REF SET measurement function is displayed as 25% on the Test Set, the value returned through HP-IB is × +2.50000000E+001 (2.5 ). Converting the returned value to a format other than scientific notation must be done programmatically.
Page 78: Sample Hp-Ib Program
1. Use exclamation marks (!) to comment-out lines 440, 450, and 460 (these commands not supported in IBASIC). 2. Change line 70 to Bus = 8 (internal HP-IB select code = 8). Example 10 ! This program generates an FM carrier, measures and displays the 20 !deviation, and draws the modulation waveform from the 30 !oscilloscope to the CRT display.
Page 79 60 GCLEAR !Clear graphics display. 70 Bus=7 ! Interface select code of HP-IB interface 80 Dut=100*Bus+14 ! Default Test Set HP-IB address is 14 90 CLEAR Bus! Good practice to clear the bus 100 CLEAR SCREEN ! Clear the CRT 110 OUTPUT Dut;"*RST"...
Page 80 HP-IB Command Guidelines Guidelines for Operation 440 ! comment them out for IBASIC (Test Set stand-alone) control. 450 ! 460 PLOTTER IS CRT,"98627A" 470 !Your display may have a different specifier. 480 GRAPHICS ON!Enable graphics to plot the waveform. 490 WINDOW 0,399,0,179...
Page 81 HP-IB Command List Main Menu www.valuetronics.com...
Page 82 :AFANalyzer subsystem ........112 :AIN <string>...
Page 83 :AM <real number> :AM? ........... . . 122 :DESTination <string>...
Page 84 :DATA?........... . 134 :FRAMe:COUNt <integer>,<real number>...
Page 85 :TRIGger:DARM ......... . . 145 :CGENerator subsystem .
Page 86 :PRINt:ADDress <integer> :PRINt:ADDress? ......... . . 155 :PRINt:LINes | LINE <integer>...
Page 87 :SPOR10:FCONtrol? | SPORT10:FCONtrol? :SPOR10:FLOW | SPORT10:FLOW <string> :SPOR10:FLOW? | SPORT10:FLOW? ......165 :SPOR10:SIN | SPORT10:SIN <string> :SPOR10:SIN? | SPORT10:SIN? :SPOR10:SINPut | SPORT10:SINPut <string>...
Page 88 :AFRequency:ACLevel?........176 :AFRequency:AM <measurement command>...
Page 89 :CDANalyzer:ERRor:FREQuency <measurement command> :CDANalyzer:ERRor:FREQuency? ......190 :CDANalyzer:MARKer:LEVel <measurement command> :CDANalyzer:MARKer:LEVel? ....... . 190 :CDANalyzer:MARKer:PHASe <measurement command>...
Page 90 :SCALe:TIME? ..........206 :SCALe:NADC <integer>...
Page 91 :SAVE <integer or string>........220 :SAVE:LIST? .
Page 92 :CFRequency? ..........230 :CONTrol <string>...
Page 93 :COMMunicate[:EVENt?]:PTRansition :COMMunicate[:EVENt?]:PTRansition? ......241 :HARD1:CONDition? ........241 :HARD1:ENABle :HARD1:ENABle? .
Page 94 :IBASic:ENABle?..........247 :IBASic[:EVENt?]:NTRansition :IBASic[:EVENt?]:NTRansition? .
Page 95 :SPEC:STRing? ..........254 :TRIGger subsystem .
Page 96 Main Menu www.valuetronics.com...
Page 97: Hp-Ib Command Dictionary
HP-IB Command Dictionary This is the HP-IB command dictionary. It contains syntax and guidelines for the HP-IB commands available in the Test Set. Main Menu www.valuetronics.com...
Page 98: Notice
HP-IB Command Dictionary Notice Notice Permission to use, copy, and distribute this template is hereby granted, provided that the above copyright notice appears in all copies and that both that copyright notice and this permission notice appear in supporting hardcopy and online documentation. All other rights reserved.
Page 99: Using This Dictionary
Using This Dictionary Using This Dictionary This dictionary is arranged according to HP-IB subsystem. Each subsystem contains syntax for a specific set of functions within the Test Set. With the online version of this document, you can cut and paste the syntax for use in your programs.
Page 100: Afanalyzer Subsystem
HP-IB Command Dictionary :AFANalyzer subsystem :AFANalyzer subsystem :AIN <string> :AIN? :AIN sets/queries the input state of the Audio In Lo connector. Syntax :AFAN:AIN ‘Gnd’ ‘Float’ ‘600 to Hi’ :AFAN:AIN? Screen/field equivalent :AIN sets the Audio In Lo field on the AF Analyzer screen.
Page 101: Demphasis:gain
HP-IB Command Dictionary :AFANalyzer subsystem :DEMPhasis:GAIN <string> :DEMPhasis:GAIN? :DEMP:GAIN sets/queries the AF Analyzer amplifier gain. Syntax :DEMP:GAIN ‘0 dB’ ‘10 dB’ ‘20 dB’ ‘30 dB’ :DEMP:GAIN? Screen/field equivalent :DEMP:GAIN sets the DE-Emp Gain field on the AF Analyzer screen. :DETector <string>...

Page 102: Detector:pklocation
HP-IB Command Dictionary :AFANalyzer subsystem :DETector:PKLocation <string> :DETector:PKLocation? :DET:PKL sets/queries the signal source for the peak detector measurements. Syntax :AFAN:DET:PKL ‘Filters’ ‘De-Emp’ :AFAN:DET:PKL? Screen/field equivalent :DET:PKL controls the PK Det To field in the AF ANALYZER screen. :DETector:SETTling <string> :DETector:SETTling? :DET:SETT sets/queries the settling time for audio measurements.

Page 103: Filt1 | Filter1
HP-IB Command Dictionary :AFANalyzer subsystem :FILT1 | FILTER1 <string> :FILT1? | FILTER1? These commands set/query the audio filter 1 selection. Syntax :AFAN:FILT1 ‘<20Hz HPF’ '50HZ HPF' '300Hz HPF' 'Optional Filter specifiers if installed' :AFAN:FILT1? Screen/field equivalent Filter 1 field is found on the AF Analyzerscreen :FILT2 | FILTER2 <string>...

Page 104: Gtime
HP-IB Command Dictionary :AFANalyzer subsystem :GTIMe <real number> :GTIMe? This command sets the gate time (how long the AF counter samples the input signal) for the audio frequency counter. This command follows the “Real Number Setting Syntax” on page 210, but does not contain the :STATe command.

Page 105: Input:gain
HP-IB Command Dictionary :AFANalyzer subsystem :INPut:GAIN <string> :INPut:GAIN? These commands set/query the input gain setting for the audio analyzer. Syntax :AFAN:INP:GAIN ‘0 dB’ ‘20 dB’ ‘40 dB’ :AFAN:INP:GAIN Screen/field equivalent Input Gain field is found on the AF Analyzerscreen. :SMPoint <string>...

Page 106: Notch:gain
HP-IB Command Dictionary :AFANalyzer subsystem :NOTCh:GAIN <string> :NOTCh:GAIN? These commands set/query the gain of the AF Analyzer’s notch filter amplifier (used for making SINAD measurements). Syntax :AFAN:NOTC:GAIN ‘0 dB’ ‘10 dB’ ‘20 dB’ ‘30 dB’ ‘40 dB’ :AFAN:NOTC:GAIN? Screen/field equivalent The Notch Gain field is found on the AF Analyzerscreen.

Page 107: Ranging
HP-IB Command Dictionary :AFANalyzer subsystem :RANGing <string> :RANGing? These commands set/query the gain control mode of the AF Analyzer’s notch filter amplifier (used for making SINAD measurements). Syntax :AFAN:RANG ‘Auto’ ‘Hold’ :AFAN:RANG? Screen/field equivalent The Notch Gain field is found on the AF Analyzerscreen.

Page 108: Speaker:volume
HP-IB Command Dictionary :AFANalyzer subsystem :SPEaker:VOLume <string> :SPEaker:VOLume? These commands set/query the speaker volume, which is controlled by VOLUME knob when “Pot” is selected. Syntax :AFAN:SPE:VOL ‘Pot’ ‘Off’ :AFAN:SPE:VOL Screen/field equivalent TheSpeaker Vol field is found on the AF Analyzer screen.

Page 109: Afg1 | Afgenerator1 Subsystem
HP-IB Command Dictionary :AFG1 | AFGENERATOR1 subsystem :AFG1 | AFGENERATOR1 subsystem :AM <real number> :AM? This command follows the “Real Number Setting Syntax” on page 210. Syntax :AFG1:AM <real number> :AFG1:AM? !returns the value of the amplitude modulation Screen/field equivalent :DESTination <string>...
Page 110: Frequency
HP-IB Command Dictionary :AFG1 | AFGENERATOR1 subsystem :FREQuency <real number> :FREQuency? This command follows the “Real Number Setting Syntax” on page 210, not including the :STAT command. Syntax :AFG1:FREQ <real number> :AFG1:FREQ Screen/field equivalent :OUTPut <real number> :OUTPut? This command follows the “Real Number Setting Syntax”...

Page 111: Afg2 | Afgenerator2 Subsystem
HP-IB Command Dictionary :AFG2 | AFGENERATOR2 subsystem :AFG2 | AFGENERATOR2 subsystem :AM <real number> :AM? This command follows the “Real Number Setting Syntax” on page 210. Syntax :AFG2:AM <real number> :AFG2:AM? !returns the value of the amplitude modulation Screen/field equivalent :DESTination <string>...
Page 112: Frequency
HP-IB Command Dictionary :AFG2 | AFGENERATOR2 subsystem :FREQuency <real number> :FREQuency? This command follows the “Real Number Setting Syntax” on page 210, not including the :STAT command. Syntax :AFG2:FREQ <real number> :AFG2:FREQ Screen/field equivalent :OUTPut <real number> :OUTPut? This command follows the “Real Number Setting Syntax”...

Page 113: Canalyzer Subsystem
HP-IB Command Dictionary :CANalyzer subsystem :CANalyzer subsystem The :CANalyzer subsystem controls functions unique to the CDMA Analyzer screen. :ARM :ARM arms the measurements based on the type of measurement (single or continuous), qualifying events, and triggering events. To put the CDMA Analyzer in Single triggering mode, use the :TRIG:MODE:RETR Single command.
Page 114: Auto:power:gain
HP-IB Command Dictionary :CANalyzer subsystem :AUTO:POWer:GAIN? :AUTO:POWer:GAIN? returns the gain setting. The value and mode of the gain are set by the commands :POW:GAIN and :POW:GAIN:MODE. This query is valid only while measuring Average Power. Syntax :CAN:AUTO:POW:GAIN? Screen/field equivalent This queries the Pwr Gain field of the CDMA Analyzer screen while measuring Average Power.
Page 115: Direction
HP-IB Command Dictionary :CANalyzer subsystem :DIRection <string> :DIRection? :DIR controls the direction of the CDMA analyzer. This command is only valid when the Test Set is in the Frequency mode (see ":CONFigure subsystem" on page 137 for the :RFDisplay command to set the mode).

Page 116: Event:trigger
HP-IB Command Dictionary :CANalyzer subsystem :EVENt:TRIGger <string> :EVENt:TRIGger? :EVEN:TRIG sets/queries the Trigger setting of the CDMA Analyzer screen. Syntax :CAN:EVEN:TRIG ‘27 ms’ ‘20 ms’ ‘80 ms’ ‘2 s’ ‘Delay’ ‘Immed’ :CAN:EVEN:TRIG? Example :CAN:EVEN:TRIG ‘Delay’ !sets the trigger to run after the delay has...

Page 117: Mode
HP-IB Command Dictionary :CANalyzer subsystem :MODE <string> :MODE? :MODE sets/queries the measurement displayed in the upper left corner of the display. Syntax :CAN:MODE ‘Avg Pwr’ ‘Rho’ ‘EVM’ ‘Chan Pwr’ :CAN:MODE? Screen/field equivalent :MODE sets the measurement in the upper left corner of the display.

Page 118: Path:gain:mode
HP-IB Command Dictionary :CANalyzer subsystem :PATH:GAIN:MODE <string> :PATH:GAIN:MODE? :PATH:GAIN:MODE sets/queries the mode of the Gain field, allowing you to choose between automatic gain or fixed gain (Hold).This command is replaced by the :CAN:POW:GAIN:MODE command when Average Power is selected. Syntax :CAN:PATH:GAIN:MODE ‘Auto’...

Page 119: Power:gain
HP-IB Command Dictionary :CANalyzer subsystem :POWer:GAIN <string> :POWer:GAIN? :POW:GAIN sets/queries the gain of the CDMA Analyzer. This command valid only when Average Power is selected. Otherwise, it is replaced by the :CAN:PATH:GAIN command. Syntax :CAN:POW:GAIN ‘0 dB’ ‘6 dB’ ‘12 dB’...

Page 120: Power:gain:mode
HP-IB Command Dictionary :CANalyzer subsystem :POWer:GAIN:MODE <string> :POWer:GAIN:MODE? :POW:GAIN:MODE sets/queries the mode of the Pwr Gain field, allowing you to choose between automatic gain or fixed gain (Hold).This command is valid only when Average Power is selected. Otherwise, it is replaced by the :CAN:PATH:GAIN:MODE command.

Page 121: Power:zero:mode
HP-IB Command Dictionary :CANalyzer subsystem :POWer:ZERO:MODE <string> :POWer:ZERO:MODE? :POW:ZERO:MODE controls whether the power meter is automatically zeroed or if the zero function must be manually activated. Syntax :CAN:POW:ZERO:MODE ‘Auto’ ‘Manual’ :CAN:POW:ZERO:MODE? Screen/field equivalent :POW:ZERO:MODE controls the Auto Zero field in the CDMA Analyzer screen.

Page 122: Special
HP-IB Command Dictionary :CANalyzer subsystem :SPECial <string> :SPECial? :SPEC controls the phase of the I and Q signals are analyzed by the Test Set. Syntax :CAN:SPEC ‘Normal’ !set for IS-95 standard rotation ‘Inverted’ :CAN:SPEC? Screen/field equivalent :SPEC controls the setting of the Anl Special field of the CDMA Analyzer.

Page 123: Cbuffer Subsystem
HP-IB Command Dictionary :CBUFfer subsystem :CBUFfer subsystem :CBUF controls the CDMA Data Buffer. This system allows you to send CDMA data through the CDMA Generator. You can send all zeroes, external data via the DATA IN connector, Random data, or data supplied via HP-IB.
Page 124: Frame:start ,
:FRAM:STAR is used with the Start Frame field of the CDMA Generator screen. :FRAMe:LOAD <integer>,<real number> :FRAMe:LOAD? :FRAM:LOAD loads the data into the HP-IB buffer. This command uses “Multiple Real Number Setting Syntax” on page 192, but without the :DUNits and :UNITs commands.

Page 125: State
HP-IB Command Dictionary :CBUFfer subsystem :STATe <string> :STATe? :STAT controls the mode of the data buffer. Syntax :CBUF:STAT ‘Idle’ ‘Send’ :CBUF:STAT? Screen/field equivalent :STAT is used with the Data Source field of the CDMA Generator screen. Chapter 5 PRELIMINARY Main Menu...

Page 126: Ccommon Subsystem
HP-IB Command Dictionary :CCOMmon subsystem :CCOMmon subsystem :PATH <string> :PATH? :PATH sets/queries RF Path of the CDMA Generator. Syntax :CCOM:PATH ‘Bypass’ ‘IQ’ :CCOM:PATH? Screen/field equivalent :PATH is used with the CW RF Path field of the CDMA Generator screen. Chapter 5 PRELIMINARY Main Menu www.valuetronics.com...
Page 127: Cdanalyzer Subsystem
HP-IB Command Dictionary :CDANalyzer subsystem :CDANalyzer subsystem :CDAN controls the Code Domain Analyzer. :CONTrol <string> :CONTrol? :CONT sets/queries the menu display of the Code Domain Analyzer. Syntax :CDAN:CONT ‘Main’ ‘Marker’ ‘Trigger’ ‘Aux’ ‘Gain’ ‘Refs’ ‘FP Setup’ :CDAN:CONT? Screen/field equivalent :CONT is used with the Control field of the Code Domain Analyzer screen.
Page 128: Event:qualifier
HP-IB Command Dictionary :CDANalyzer subsystem :EVENt:QUALifier <string> :EVENt:QUALifier? :EVEN:QUAL sets the qualifying event for the trigger. The qualifying event is the event that must occur before a trigger is accepted. The trigger event is set by the :EVEN:TRIG command. Syntax :CDAN:EVEN:QUAL ‘None’...

Page 129: Event:trigger:delay :Event:trigger:delay
HP-IB Command Dictionary :CDANalyzer subsystem :EVENt:TRIGger:DELay <real number> :EVENt:TRIGger:DELay? :EVEN:TRIG:DEL sets the delay value of the trigger. This command follows the “Real Number Setting Syntax” on page 210, but does not contain the :DUNits, :UNITs, or :STATe commands. Syntax :CDAN:EVEN:TRIG:DEL <real number> !values from 20 us to 10 s...
Page 130: Measure
HP-IB Command Dictionary :CDANalyzer subsystem :MEASure <string> :MEASure? :MEAS sets/queries the measurement performed in the Code Domain Analyzer screen. Syntax :CDAN:MEAS ‘Power’ ‘Fast Pwr’ ‘Timing’ ‘Phase’ :CDAN:MEAS? Screen/field equivalent :MEAS is used with the Measurement field of the Code Domain Analyzer screen.

Page 131: Fpower:toffset
HP-IB Command Dictionary :CDANalyzer subsystem :FPOWer:TOFFset <real number> :FPOWer:TOFFset? :FPOW:TOFF sets/queries the Time Offset for the Fast Power measurement. :FPOW:TOFF can be either entered with this command, or it can be transferred via the :FPOW:TOFF:TRAN command. This number can be entered in microseconds only.

Page 132: Path:gain
HP-IB Command Dictionary :CDANalyzer subsystem :PATH:GAIN <real number> :PATH:GAIN? :PATH:GAIN sets the Gain in the Gain menu of the Code Domain Analyzer screen. Syntax :CDAN:PATH:GAIN <real number> !values from 0 to 36 dB :CDAN:PATH:GAIN? Screen/field equivalent :PATH:GAIN is used with the GAIN field in the Gain menu of the Code Domain Analyzer screen.

Page 133: Scale:phase
HP-IB Command Dictionary :CDANalyzer subsystem :SCALe:PHASe <string> :SCALe:PHASe? :SCAL:PHAS sets/queries the phase portion of the scale that is used when measuring Phase in the Code Domain Analyzer screen. Syntax :CDAN:SCAL:PHAS ‘1 mRad’ ‘2 mRad’ ‘5 mRad’ ‘10 mRad’ ‘20 mRad’...

Page 134: Scale:time
Phase measurements. Walsh channels that have power levels below the threshold are not displayed in the Timing and Phase displays. Querying these measurements for Walsh Channels that are below the threshold level using HP-IB will return a default value of 9e99. Syntax :CDAN:THRS <real number>...

Page 135: Trigger:arm
HP-IB Command Dictionary :CDANalyzer subsystem :TRIGger:ARM :TRIGger:DARM :TRIG:ARM and :TRIG:DARM arm and disarm the measurements in the Code Domain Analyzer screen. This command does not affect Continuous measurement. To put the Code Domain Analyzer in Single triggering mode, use the :TRIG:MODE:RETR Single command. For Continuous triggering, use :TRIG:MODE:RETR Continuous.
Page 136: Cgenerator Subsystem
HP-IB Command Dictionary :CGENerator subsystem :CGENerator subsystem :CONTrol <string> :CONTrol? :CONT defines the CDMA Generator’s mode. It defines the type for data being sent. Syntax :CGEN:CONT ‘Data’ ‘Eb/No’ ‘Noise’ :CGEN:CONT? Screen/field equivalent :CONT is used with the Gen Mode field of the CDMA Generator screen.
Page 137: Data:rate
HP-IB Command Dictionary :CGENerator subsystem :DATA:RATE <string> :DATA:RATE? :DATA:RATE sets the data transfer rate for data from the :DATA:SOUR command. Syntax :CGEN:DATA:RATE ‘14.4 Kbps’ ‘9.6 Kbps’ :CGEN:DATA:RATE? Screen/field equivalent :DATA:RATE is used with the Data Rate field of the CDMA Generator screen.

Page 138: Eqfilter
HP-IB Command Dictionary :CGENerator subsystem :EQFilter <string> :EQFilter? :EQF sets/queries the setting of the Equalization Filter. This command is used when you want to override the automatic setting (filter is applied for forward link signals, and bypassed for reverse link signals).

Page 139: Configure Subsystem
:BADD sets the HP-IB address for the Test Set. This command follows “Integer Number Setting Syntax”. Syntax :CONF:BADD <integer> !valid from 0 to 30 :CONF:BADD? Screen/field equivalent :BADD is used with the HP-IB Adrs field of the I/O Configure screen. Chapter 5 PRELIMINARY Main Menu www.valuetronics.com...
Page 140: Beeper
:CONF:DISP:MESS Screen/field equivalent :DISP:MESS is used with the Display User Messages field of the Instrument Configure screen. :BMODe <string> :BMODe? :BMOD sets/queries the HP-IB control mode. Syntax :CONF:BMOD ‘Control’ ‘Talk&Lstn’ :CONF:BMOD? Screen/field equivalent :BMOD is used with the Mode field of the I/O Configure screen.

Page 141: Date
HP-IB Command Dictionary :CONFigure subsystem :DATE <integer> :DATE? :DATE sets/queries the date set within the Test Set. This command uses the “Integer Number Setting Syntax”. Syntax :CONF:DATE <integer> !Use MMDDYY format :CONF:DATE? Screen/field equivalent :DATE is used with the Date field of the Instrument Configure screen.

Page 142: Knob
HP-IB Command Dictionary :CONFigure subsystem :KNOB <string> :KNOB? :KNOB is an HP-IB command which is the equivalent of the pressing the knob. Syntax :CONF:KNOB ‘On’ ‘Off’ :CONF:KNOB? Screen/field equivalent :KNOB has no field associated with this command.. :NOTChmode <string> :NOTChmode? :NOTC sets/queries the coupling between the AF Generator 1 and a notch filter.

Page 143: Oflevel:mode
HP-IB Command Dictionary :CONFigure subsystem :OFLevel:MODE <string> :OFLevel:MODE? :OFL:MODE sets/queries the RF Level Offset, and is typically used to compensate for path loss between the Test Set and the Base Station. Syntax :CONF:OFL:MODE ‘On’ ‘Off’ :CONF:OFL:MODE? Screen/field equivalent :OFL:MODE is used with the RF Level Offset field of the Instrument Configure screen.

Page 144: Oflevel:duplex
HP-IB Command Dictionary :CONFigure subsystem :OFLevel:DUPlex <real number> :OFL:DUP sets/queries the path loss from the Duplex Out connector to the Device Under Test. This correction is applied when the RF Level Offset field is set to “On”. This command uses the “Real Number Setting...

Page 145: Oflevel:rfinout
HP-IB Command Dictionary :CONFigure subsystem :OFLevel:RFINout <real number> :OFL:RFIN sets/queries the path loss from the RF In/Out connector to the Device Under Test. This correction is applied when the RF Level Offset field is set to “On”. This command uses the “Real Number Setting...

Page 146: Operation:auto
:OPER:AUTO and :OPER:HOLD are used with the Range Hold field of the Configure screen. :PRINt:ADDress <integer> :PRINt:ADDress? :PRIN:ADD sets/queries the printer address used when “HP-IB” is selected in the Printer Port field. This command uses the “Integer Number Setting Syntax”.
Page 147: Print:destination | Ports :Print:destination? | Ports
:PRINt:DESTination? | PORTs? :PRIN:DEST sets/queries the port setting for the Printer Port field. This command controls the ports available from the keypad (Serial 9, HP-IB, and Parallel 15) . The :PRIN:DEST command is equivalent to the :PRIN:PORT command. Syntax :CONF:PRIN:DEST ‘Serial 9’...
Page 148: Print:ffend
HP-IB Command Dictionary :CONFigure subsystem :PRINt:FFENd <string> :PRINt:FFENd? :PRIN:FFEN sets/queries the Form Feed (FF at End) field, which determines if there will be a form feed at the end of printing. Syntax :CONF:PRIN:FFEN ‘Yes’ ‘No’ :CONF:PRIN:FFEN? Screen/field equivalent :PRIN:FFEN is used with the FF at End field of the Print Configure screen.

Page 149: Print:printer | :Print:hpmodel | :Print:hpmo :Print:printer? | :Print:hpmodel? | :Print:hpmo
HP-IB Command Dictionary :CONFigure subsystem :PRINt:PRINter | :PRINt:HPModel | :PRINt:HPMO <string> :PRINt:PRINter? | :PRINt:HPModel? | :PRINt:HPMO? :PRIN:PRIN sets the type of printer chosen for printing. Syntax :CONF:PRIN:PRIN ‘ThinkJet’ ‘QuietJet’ ‘PaintJet’ ‘DeskJet’ ‘LaserJet’ ‘Epson FX-80’ ‘Epson LX-850’ :CONF:PRIN:PRIN? Screen/field equivalent :PRIN:PRIN is used with the Model field of the Print Configure screen.
Page 150: Reference:input:external :Reference:input:external
HP-IB Command Dictionary :CONFigure subsystem :REFerence:INPut:EXTernal <string> :REFerence:INPut:EXTernal? :REF:INP:EXT sets/queries the frequency of an External Reference signal. This must be used in conjunction with the :REF:INP:SEL command. Syntax :REF:INP:EXT ‘1 MHz’ ‘2 MHz’ ‘5 MHz’ ‘10 MHz’ ‘15 MHz’ ‘1X Chip’...
Page 151: Spselect
HP-IB Command Dictionary :CONFigure subsystem :SPSelect <string> :SPSelect? :SPS sets/queries the selected serial port for configuration purposes. It defines which port’s configuration settings are displayed on the I/O CONFIGURE screen. Syntax :CONF:SPS ‘Serial 9’ ‘Serial 10’ ‘Serial 11’ :CONF:SPS? Screen/field equivalent :SPS is used with the Serial Port field of the I/O Configure screen.

Page 152: Spor9:Baud | Sport9:Baud :Spor9:Baud? | Sport9:Baud
HP-IB Command Dictionary :CONFigure subsystem :SPOR9:BAUD | SPORT9:BAUD <string> :SPOR9:BAUD? | SPORT9:BAUD? :SPOR9:BAUD sets/queries the baud rate of the Serial Port 9. Syntax :CONF:SPOR9:BAUD ‘ 150’ ‘300’ ‘600‘ ‘1200‘ ‘2400‘ ‘4800‘ ‘9600‘ ‘19200‘ :CONF:SPOR9:BAUD? Screen/field equivalent :SPOR9:BAUD is used with the Serial Baud field of the I/O CONFIGURE screen.
Page 153: Spor9:Data | Sport9:Data
HP-IB Command Dictionary :CONFigure subsystem :SPOR9:DATA | SPORT9:DATA <string> :SPOR9:DATA? | SPORT9:DATA? :SPOR9:DATA sets/queries the number of data bits per data word sent over the Serial port 9. Syntax :CONF:SPOR9:DATA ‘7 bits’ ‘8 bits’ :CONF:SPOR9:DATA? Screen/field equivalent :SPOR9:DATA is used with the Data Length field of the I/O CONFIGURE screen.

Page 154: Spor9:Fcontrol | Sport9:Fcontrol
HP-IB Command Dictionary :CONFigure subsystem :SPOR9:FCONtrol | SPORT9:FCONtrol <string> :SPOR9:FCONtrol? | SPORT9:FCONtrol? :SPOR9:FLOW | SPORT9:FLOW <string> :SPOR9:FLOW? | SPORT9:FLOW? :SPOR9:FCON sets/queries the flow control to set the pace of serial communications for the Serial Port 9. Syntax :CONF:SPOR9:FCON ‘Xon/Xoff’ ‘None’...

Page 155: Spor9:Ibecho | Sport9:Ibecho
HP-IB Command Dictionary :CONFigure subsystem :SPOR9:IBECho | SPORT9:IBECho <string> :SPOR9:IBECho? | SPORT9:IBECho? :SPOR9:IBEC sets/queries the screen and error message echoing from IBSIC. Syntax :CONF:SPOR9:IBEC ‘On’ ‘Off’ :CONF:SPOR9:IBEC Screen/field equivalent :SPOR9:IBEC is used with the IBASIC Echo field of the I/O CONFIGURE screen.

Page 156: Spor9:Status:modem
HP-IB Command Dictionary :CONFigure subsystem :SPOR9:STATus:MODem? :SPOR9:MOD? queries the Modem status register. Syntax :CONF:SPOR9:STAT:MOD? Screen/field equivalent No screen/field equivalent. :SPOR10:BAUD | SPORT10:BAUD <string> :SPOR10:BAUD? | SPORT10:BAUD? :SPOR10:BAUD sets/queries the baud rate of the Serial Port 10. Syntax :CONF:SPOR10:BAUD ‘ 150’...
Page 157: Spor10:Parity | Sport10:Parity :Spor10:Parity? | Sport10:Parity
HP-IB Command Dictionary :CONFigure subsystem :SPOR10:PARity | SPORT10:PARity <string> :SPOR10:PARity? | SPORT10:PARity? :SPOR10:PARity sets/queries the parity of the Serial Port 10. Syntax :CONF:SPOR10:PAR ‘None’ 'Odd' 'Even' 'Always 1' 'Always 0' :CONF:SPOR10:PAR? Screen/field equivalent :SPOR10:PAR is used with the Parity field of the I/O CONFIGURE screen.
Page 158: Spor10:Stop | Sport10:Stop
HP-IB Command Dictionary :CONFigure subsystem :SPOR10:STOP | SPORT10:STOP <string> :SPOR10:STOP? | SPORT10:STOP? SPOR10:STOP sets/queries the number of stop bits used for serial communication over the Serial Port 10. Syntax :CONF:SPOR10:STOP ‘1 bit’ ‘2 bits’ :CONF:SPOR10:STOP? Screen/field equivalent :SPOR10:STOP is used with the Stop Length field of the I/O CONFIGURE screen.

Page 159: Spor10:Sin | Sport10:Sin :Spor10:Sin? | Sport10:Sin
HP-IB Command Dictionary :CONFigure subsystem :SPOR10:SIN | SPORT10:SIN <string> :SPOR10:SIN? | SPORT10:SIN? :SPOR10:SINPut | SPORT10:SINPut <string> :SPOR10:SINPut? | SPORT10:SINPut? :SPOR10:SIN sets/queries the destination of data characters received by the Test Set via the Serial Port 10. Syntax :CONF:SPOR10:SIN ‘Inst’ ‘IBASIC’...
Page 160: Spor10:Iecho | Sport10:Iecho :Spor10:Iecho? | Sport10:Iecho
HP-IB Command Dictionary :CONFigure subsystem :SPOR10:IECHo | SPORT10:IECHo <string> :SPOR10:IECHo? | SPORT10:IECHo? :SPOR10:IECH sets/queries the character and screen echoing (instrument echo) when using an external ASCII RS-232 terminal or computer to enter or edit the IBASIC program. Syntax :CONF:SPOR10:IECH ‘On’...
Page 161: Spor11:Baud | Sport11:Baud
HP-IB Command Dictionary :CONFigure subsystem :SPOR11:BAUD | SPORT11:BAUD <string> :SPOR11:BAUD? | SPORT11:BAUD? :SPOR11:BAUD sets/queries the baud rate of the Serial Port 11. Syntax :CONF:SPOR11:BAUD ‘ 150’ ‘300’ ‘600‘ ‘1200‘ ‘2400‘ ‘4800‘ ‘9600‘ ‘19200‘ :CONF:SPOR11:BAUD? Screen/field equivalent :SPOR11:BAUD is used with the Serial Baud field of the I/O CONFIGURE screen.

Page 162: Spor11:Data | Sport11:Data
HP-IB Command Dictionary :CONFigure subsystem :SPOR11:DATA | SPORT11:DATA <string> :SPOR11:DATA? | SPORT11:DATA? :SPOR11:DATA sets/queries the number of data bits per data word sent over the Serial port 11. Syntax :CONF:SPOR11:DATA ‘7 bits’ ‘8 bits’ :CONF:SPOR11:DATA? Screen/field equivalent :SPOR11:DATA is used with the Data Length field of the I/O CONFIGURE screen.

Page 163: Spor11:Fcontrol | Sport11:Fcontrol
HP-IB Command Dictionary :CONFigure subsystem :SPOR11:FCONtrol | SPORT11:FCONtrol <string> :SPOR11:FCONtrol? | SPORT11:FCONtrol? :SPOR11:FLOW | SPORT11:FLOW <string> :SPOR11:FLOW? | SPORT11:FLOW? :SPOR11:FCON sets/queries the flow control to set the pace of serial communications for the Serial Port 11. Syntax :CONF:SPOR11:FCON ‘Xon/Xoff’ ‘None’...

Page 164: Spor11:Ibecho | Sport11:Ibecho :Spor11:Ibecho? | Sport11:Ibecho
HP-IB Command Dictionary :CONFigure subsystem :SPOR11:IBECho | SPORT11:IBECho <string> :SPOR11:IBECho? | SPORT11:IBECho? :SPOR11:IBEC sets/queries the screen and error message echoing from IBASIC. Syntax :CONF:SPOR11:IBEC ‘On’ ‘Off’ :CONF:SPOR11:IBEC Screen/field equivalent :SPOR11:IBEC is used with the IBASIC Echo field of the I/O CONFIGURE screen.
Page 165: Spor11:Status:modem
HP-IB Command Dictionary :CONFigure subsystem :SPOR11:STATus:MODem? :SPOR11:MOD? queries the Modem status register. Syntax :CONF:SPOR11:STAT:MOD? Screen/field equivalent No screen/field equivalent. :TBASE:CDMA <string> :TBASE:CDMA? :TBASE:CDMA sets/queries the optional time base used for CDMA. This commands allows you to select either an external or internal timebase.
Page 166: Time
HP-IB Command Dictionary :CONFigure subsystem :TIME <real number> :TIME? :TIME sets/queries the time of day. This command uses the “Real Number Setting Syntax”, without the :STAT, :DUN, :INCR, or :UNITs command. Syntax :CONF:TIME <real number> !hh.mm where hh is hours, mm is...

Page 167: Display Subsystem
HP-IB Command Dictionary :DISPlay subsystem :DISPlay subsystem The :DISPlay subsystem controls the display of screens. A screen must be displayed before a measurement from that screen can be made. :DISPlay :DISPlay? :DISP sets/queries which screen is displayed. Syntax :DISP AFANalyzer !AF Analyzer screen...
Page 168 HP-IB Command Dictionary :DISPlay subsystem TSPec !TESTS PassFail Limits CGENerator !CDMA Generator !locks the display REMote :DISP? !returns the name of the screen being displayed Chapter 5 PRELIMINARY Main Menu www.valuetronics.com...
Page 169: Integer Number Setting Syntax
HP-IB Command Dictionary Integer Number Setting Syntax Integer Number Setting Syntax This syntax is for setting values of commands which require integer values. It is to be used with commands which call for the Integer Number Setting Syntax. An example of a command that requires the Integer Setting Syntax is the :RFANalyzer:RFCHannel command (see ":RFANalyzer subsystem"...
Page 170: Measure Subsystem
HP-IB Command Dictionary :MEASure subsystem :MEASure subsystem The MEAS subsystem has a set of commands unique to this subsystem. These are the <measurement command> set. They control features of the Test Set such as setting measurement limits, units and the meters.
Page 171: Afrequency:am
HP-IB Command Dictionary :MEASure subsystem :AFRequency:AM <measurement command> :AFRequency:AM? :AFR:AM controls/reads the AM depth of modulation measurement. Syntax :MEAS:AFR:AM <meas cmd> !see "Number Measurement Syntax" on page 193 :MEAS:AFR:AM? !returns real value Example :MEAS:AFR:AM:METer ON !displays the measurement in the meter...

Page 172: Afrequency:dcam
HP-IB Command Dictionary :MEASure subsystem :AFRequency:DCAM <measurement command> :AFRequency:DCAM? :AFR:DCAM controls/reads the DC AM measurement. To use this measurement, you must have the DC Level measurement selected (see :MEAS:AFR:SEL on page 173), and be using AM demodulation or modulation (see :AFAN:INP on page 102).

Page 173: Afrequency:dcvolts
HP-IB Command Dictionary :MEASure subsystem :AFRequency:DCVolts <measurement command> :AFRequency:DCVolts? :AFR:DCV controls/queries the DC Voltmeter. To use this measurement, you must have the DC Level measurement selected (see :MEAS:AFR:SEL on page 173), and have selected one of the following audio sources: SSB Demod, Audio In, Ext Mod, or Audio Out (see...

Page 174: Afrequency:fm
HP-IB Command Dictionary :MEASure subsystem :AFRequency:FM <measurement command> :AFRequency:FM? :AFR:FM controls/queries the FM Deviation measurement. This measurement is active when FM Mod or FM Demod is selected by using the :AFAN:INP command (see page 102) and SNR is not selected by the...

Page 175: Afrequency:select
HP-IB Command Dictionary :MEASure subsystem :AFRequency:SELect <measurement command> :AFRequency:SELect? :AFR:SEL controls/queries which measurement is displayed in the AF ANALYZER and RF ANALYZER screens. Syntax :MEAS:AFR:SEL ‘SINAD’ ‘Distn’ ‘SNR’ ‘AF Freq’ ‘DC Level’ :MEAS:AFR:SEL ! returns the presently selected measurement (string)

Page 176: Afrequency:snr
HP-IB Command Dictionary :MEASure subsystem :AFRequency:SNR <measurement command> :AFRequency:SNR? :AFR:SNR controls/queries the SNR measurement. SNR must first be selected using the :MEAS:AFR:SEL ‘SNR’ command (see page 173). Syntax :MEAS:AFR:SNR <meas cmd> !controls the SNR command :MEAS:AFR:SNR? !returns the measurement’s value...

Page 177: Canalyzer:adc:rhoadc:level
HP-IB Command Dictionary :MEASure subsystem :CANalyzer:ADC:RHOadc:LEVel <measurement command> :CANalyzer:ADC:RHOadc:LEVel? :ADC:RHO:LEV controls/queries the ADC for the Rho measurement. The ADC is a measure of how close the actual input signal is to the maximum input level. This measurement uses the Number Measurement Syntax, but does not use the Meter command from this syntax.

Page 178: Canalyzer:adc:tpoweradc:level :Canalyzer:adc:tpoweradc:level
HP-IB Command Dictionary :MEASure subsystem :CANalyzer:ADC:TPOWeradc:LEVel <measurement command> :CANalyzer:ADC:TPOWeradc:LEVel? :ADC:TPOW:LEV controls/queries the ADC for the Channel Power measurement. The ADC is a measure of how close the actual input signal is to the maximum input level. This measurement uses the Number Measurement Syntax, but does not use the Meter command from this syntax.
Page 179: Canalyzer:error:frequency :Canalyzer:error:frequency
HP-IB Command Dictionary :MEASure subsystem :CANalyzer:ERRor:FREQuency <measurement command> :CANalyzer:ERRor:FREQuency? :CAN:ERR:FREQ controls/queries the Frequency Error measurement. This measurement uses the Number Measurement Syntax, but does not use the Meter command from this syntax. Syntax :MEAS:CAN:ERR:FREQ <meas cmd> !see "Number Measurement Syntax" on page 193...
Page 180: Canalyzer:error:phase :Canalyzer:error:phase
HP-IB Command Dictionary :MEASure subsystem :CANalyzer:ERRor:PHASe <measurement command> :CANalyzer:ERRor:PHASe? :CAN:ERR:PHAS controls/queries the Phase Error measurement. This measurement uses the Number Measurement Syntax, but does not use the Meter command from this syntax. Syntax :MEAS:CAN:ERR:PHAS <meas cmd> !see "Number Measurement Syntax" on page 193...
Page 181: Canalyzer:power:avg
HP-IB Command Dictionary :MEASure subsystem :CANalyzer:POWer:AVG <measurement command> :CANalyzer:POWer:AVG? :CAN:POW:AVG control/queries the Average Power measurement. This measurement uses the Number Measurement Syntax, but does not use the Meter command from this syntax. Syntax :MEAS:CAN:POW:AVG <meas cmd> !see "Number Measurement Syntax" on page 193...

Page 182: Canalyzer:rho
HP-IB Command Dictionary :MEASure subsystem :CANalyzer:RHO <measurement command> :CANalyzer:RHO? :CAN:RHO controls/queries the Rho measurement. This measurement uses the Number Measurement Syntax, but does not use the Meter command from this syntax. Syntax :MEAS:CAN:RHO <meas cmd> !see "Number Measurement Syntax" on...

Page 183: Cdanalyzer:adc
HP-IB Command Dictionary :MEASure subsystem :CDANalyzer:ADC <measurement command> :CDANalyzer:ADC? :CDAN:ADC controls/queries the ADC measurement in the Code Domain Analyzer. This measurement uses the Number Measurement Syntax, but does not use the Meter command from this syntax. Syntax :MEAS:CDAN:ADC <meas cmd>...

Page 184: Cdanalyzer:error:frequency :Cdanalyzer:error:frequency
HP-IB Command Dictionary :MEASure subsystem :CDANalyzer:ERRor:FREQuency <measurement command> :CDANalyzer:ERRor:FREQuency? :CDAN:CARR:FEED controls/queries the Carrier Feedthrough measurement on the Code Domain Analyzer. This measurement uses the Number Measurement Syntax, but does not use the Meter command from this syntax. Syntax :MEAS:CDAN:ERR:FREQ <meas cmd>...
Page 185: Cdanalyzer:marker:phase :Cdanalyzer:marker:phase
HP-IB Command Dictionary :MEASure subsystem :CDANalyzer:MARKer:PHASe <measurement command> :CDANalyzer:MARKer:PHASe? :CDAN:MARK:PHAS controls/queries the Marker Phase of the Code Domain Analyzer.This measurement is made relative to the value at Walsh Code 0. This measurement uses the Number Measurement Syntax, but does not use the Meter command from this syntax.
Page 186: Cdanalyzer:time:offset :Cdanalyzer:time:offset
HP-IB Command Dictionary :MEASure subsystem :CDANalyzer:TIME:OFFSet <measurement command> :CDANalyzer:TIME:OFFSet? :CDAN:TIME:OFFS controls/queries the Time Offset measurement of the Code Domain Analyzer. This measurement uses the Number Measurement Syntax, but does not use the Meter command from this syntax. Syntax :MEAS:CDAN:TIME:OFFS <meas cmd>...
Page 187: Cdanalyzer:trace:toffset
HP-IB Command Dictionary :MEASure subsystem :CDANalyzer:TRACe:TOFFset? :CDAN:TRAC:TOFF controls/queries the timing in the trace points in the Code Domain Analyzer. The measurement returns 64 values (in seconds), one for each point. This measurement uses the Number Measurement Syntax, but does not use the Meter command from this syntax.
Page 188: Oscilloscope:marker:level:am :Oscilloscope:marker:level:am
HP-IB Command Dictionary :MEASure subsystem :OSCilloscope:MARKer:LEVel:AM <measurement command> :OSCilloscope:MARKer:LEVel:AM? :OSC:MARK:LEV:AM controls/queries the AM depth of modulation at the Oscilloscope’s marker position. This measurement uses the Number Measurement Syntax, but does not use the Meter command from this syntax. Syntax :MEAS:OSC:MARK:LEV:AM <meas cmd>...
Page 189: Oscilloscope:marker:level:volts :Oscilloscope:marker:level:volts
HP-IB Command Dictionary :MEASure subsystem :OSCilloscope:MARKer:LEVel:VOLTs <measurement command> :OSCilloscope:MARKer:LEVel:VOLTs? :OSC:MARK:LEV:VOLT controls/queries the FM deviation at the Oscilloscope’s marker position. This measurement uses the Number Measurement Syntax, but does not use the Meter command from this syntax. Syntax :MEAS:OSC:MARK:LEV:VOLT <meas cmd>...
Page 190: Oscilloscope:trace
HP-IB Command Dictionary :MEASure subsystem :OSCilloscope:TRACe? :OSC:TRAC returns an array of 417 real values, corresponding to points on the Oscilloscope display. 0 corresponds to the first value (left side of trace display) and 416 is the last value (right side of the trace display).
Page 191: Rfrequency:frequency:error :Rfrequency:frequency:error
HP-IB Command Dictionary :MEASure subsystem :RFRequency:FREQuency:ERRor <measurement command> :RFRequency:FREQuency:ERRor? :RFR:FREQ:ABS controls/queries the RF frequency error. Syntax :RFR:FREQ:ERR <meas syntax> !see "Number Measurement Syntax" on page 193 :RFR:FREQ:ERR? Screen/field equivalent :RFR:FREQ:ERR reads the Freq Error measurement field on the RF ANALYZER screen.
Page 192: Sanalyzer:marker:frequency :Sanalyzer:marker:frequency
HP-IB Command Dictionary :MEASure subsystem :SANalyzer:MARKer:FREQuency <measurement command> :SANalyzer:MARKer:FREQuency? :SAN:MARK:FREQ controls/queries the frequency at the current marker position of the Spectrum Analyzer. This measurement uses the Number Measurement Syntax, but does not use the Meter command from this syntax. Syntax :MEAS:SAN:MARK:FREQ <meas cmd>...
Page 193: Sanalyzer:trace
HP-IB Command Dictionary :MEASure subsystem :SANalyzer:TRACe? :SAN:TRAC returns an array of 417 real values, corresponding to points on the Spectrum Analyzer display. 0 corresponds to the first value (left side of trace display) and 416 is the last value (right side of the trace display).
Page 194: Multiple Real Number Setting Syntax
:Previous Syntax? <integer_value> !returns the value of the position :Previous Syntax:DUNits <integer_value>,<display unit_of_measure> !sets the units :Previous Syntax:DUNits? <integer_value> !returns the display units :Previous Syntax:UNits <integer_value>,<HP-IB unit_of_measure> :Previous Syntax:UNits? <integer_value> !Displays the HP-IB units :Previous Syntax:INCRement <integer_value>,<incr_value>[display unit_of_measure] !increments the present value :Previous Syntax:INCRement <integer_value>,UP|DOWN :Previous Syntax:INCRement? <integer_value>...
Page 195: Number Measurement Syntax
This syntax is typically used with subsystems like the :MEASure subsystem/ Syntax :Previous Syntax:AUNits <HP-IB units> !sets the HP-IB units :Previous Syntax:AUNits !returns the HP-IB units :Previous Syntax:AVERage[:VALue] <real_value> !sets the number of averages :Previous Syntax:AVERage? !returns the number of averages...
Page 196 :Previous Syntax:REFerence:STATe 0|OFF !sets state of the reference :Previous Syntax:REFerence:STATe? !returns 1 or 0 :Previous Syntax:STATe 1|ON :Previous Syntax:STATe 0|OFF :Previous Syntax:STATe? ! returns 1 or 0 :Previous Syntax:UNits <HP-IB unit_of_measure> !sets the HP-IB units :Previous Syntax:UNits? !returns the HP-IB units Chapter 5 PRELIMINARY Main Menu...
Page 197 HP-IB Command Dictionary Number Measurement Syntax Examples :RFAN:FREQ 850.35MHz !sets the frequency to 850.35 MHz :RFAN:FREQ? !returns the frequency :RFAN:FREQ:DUNits GHz !changes the units to GigaHertz :RFAN:FREQ:INCR 3.5MHz !increments frequency by 3.5 MHz :RFAN:FREQ:INCR? !returns the increment value :RFAN:FREQ:MULT !multiplies the current frequency by 10...
Page 198: Oscilloscope Subsystem
HP-IB Command Dictionary :OSCilloscope subsystem :OSCilloscope subsystem :CONTrol :CONTrol? :CONT selects/queries the Oscilloscope menus. Syntax :OSC:CONT ‘Main’ ‘Trigger’ ‘Marker’ :OSC:CONT? Example :OSC:CONT ‘Trigger’ !displays the Trigger menu of the Oscilloscope Screen/field equivalent :CONT is used with the menu field of the OSCILLOSCOPE screen.
Page 199: Marker:ppeak
HP-IB Command Dictionary :OSCilloscope subsystem :MARKer:PPEak :MARK:PPE moves the marker to the maximum value of the average level of the display. This command has no query. Syntax :OSC:MARK:PPE !moves the marker to the maximum Screen/field equivalent :OSC:MARK:PPE is used with the Marker To field of the OSCILLOSCOPE screen.
Page 200: Scale:time
HP-IB Command Dictionary :OSCilloscope subsystem :SCALe:TIME <string> :SCALe:TIME? :SCAL:TIME selects/queries the horizontal sweep time per division. Syntax :OSC:SCAL:TIME ‘200 ms’ '100 ms' '50 ms' '20 ms' '10 ms' '5 ms' '2 ms' '1 ms' '500 us' '200 us' '100 us'...

Page 201: Scale:nadc
HP-IB Command Dictionary :OSCilloscope subsystem :SCALe:NADC <integer> :SCALe:NADC? This command uses the “Integer Number Setting Syntax”, without the :STAT command. Syntax :OSC:SCAL:NADC <integer> :OSC:SCAL:NADC? Example :OSC:SCAL:NADC !displays the measurement Screen/field equivalent :SCAL:NADC is used with the menu field of the OSCILLOSCOPE screen.

Page 202: Scale:vertical:am
HP-IB Command Dictionary :OSCilloscope subsystem :SCALe:VERTical:AM <string> :SCALe:VERTical:AM? :SCAL:VERT:AM sets/queries the vertical axis Amplitude per division when AM Modulation or AM Demodulation are selected in the AF Anl Input field (AF Analyzer screen). Syntax :OSC:SCAL:VERT:AM ’50%’ ’20%’ ’10%’ ’5%’ ’2%’...

Page 203: Scale:vertical:fm
HP-IB Command Dictionary :OSCilloscope subsystem :SCALe:VERTical:FM <string> :SCALe:VERTical:FM? :SCAL:VERT:FM sets/queries the vertical axis Amplitude per division when FM Modulation or FM Demodulation are selected in the AF Anl Input field (AF Analyzer screen). Syntax :OSC:SCAL:VERT:FM ’50 kHz’ ’20 kHz’ ’10 kHz’...

Page 204: Scale:vertical:offset
HP-IB Command Dictionary :OSCilloscope subsystem :SCALe:VERTical:OFFSet <real number> :SCALe:VERTical:OFFSet? :SCAL:VERT:OFFS sets/queries the vertical scale (DC) offset of the vertical axis of the oscilloscope display. This moves the signal up to four divisions up or down with respect to the Oscilloscope’s fixed center line.

Page 205: Scale:vertical:volts
HP-IB Command Dictionary :OSCilloscope subsystem :SCALe:VERTical:VOLTs <string> :SCALe:VERTical:VOLTs? :SCAL:VERT:VOLT sets/queries the vertical scale of the Oscilloscope display when Audio In is selected in the AF Anl screen. This command is valid when the AF Anl Input field in the AF Anl screen is set to anything except FM Mod, FM Demod, AM Mod, or AM Demod.

Page 206: Trigger:level
HP-IB Command Dictionary :OSCilloscope subsystem :TRIGger:LEVel <real number> :TRIGger:LEVel? :TRIG:LEV sets/queries the level of the Oscilloscope’s trigger. This command uses the “Real Number Setting Syntax”, without the :STAT, :DUN, :UNIT, :INCR:MODE, :INCR:DUN, commands. Syntax :OSC:TRIG:LEV <real> !values :OSC:TRIG:LEV? !returns the level Example :OSC:TRIG:LEV 0.4 !sets the level to 0.4 V...

Page 207: Trigger:delay
HP-IB Command Dictionary :OSCilloscope subsystem :TRIGger:DELay <real number> :TRIGger:DELay? :TRIG:DEL sets/queries the trigger delay. Positive values delay the trigger, negative values apply a pre-trigger function to each measurement. This command uses the “Real Number Setting Syntax”, without the :STAT, :DUN, :UNIT, :INCR:MODE, :INCR:DUN, commands.

Page 208: Trigger:reset
HP-IB Command Dictionary :OSCilloscope subsystem :TRIGger:RESet :RESet triggers a measurement in the Oscilloscope. Syntax :OSC:TRIG:RES !triggers the Oscilloscope Screen/field equivalent :TRIG:RESet is used with the Reset field of the OSCILLOSCOPE screen. :TRIGger:SENSe <string> :TRIGger:SENSe? :TRIG:SENS sets/queries the desired edge of the trigger. ‘Pos’ triggers the measurement on the positive-going edge of the input signal.
Page 209: Trigger:type
HP-IB Command Dictionary :OSCilloscope subsystem :TRIGger:TYPE <string> :TRIGger:TYPE? :TRIG:TYPE sets/queries how the trigger level is set. ‘Auto’ triggers a measurement if a triggering signal is not detected within approximately 50 ms of the last trigger. ‘Norm’ requires a specific triggering signal before triggering.

Page 210: Program Subsystem
HP-IB Command Dictionary :PROGram subsystem :PROGram subsystem The Program subsystem provides a set of commands which allow an external controller to generate and control an IBASIC program within the Test Set. These commands have no equivalent fields or screens. [:SELected]:DEFine <program data>...
Page 211: [:Selected]:Number (,)
HP-IB Command Dictionary :PROGram subsystem [:SELected]:NUMBer <variable>(,<nvalues>) [:SELected]:NUMBer? :SEL:NUMB sets/queries the value of numeric variables or arrays in the IBASIC program currently loaded in the Test Set. Syntax :PROG:SEL:NUMB <variable>,<nvalues> :PROG:NUMB <variable>,<nvalues> !equivalent command [:SELected]:STRing <variable>(,<nvalues>) [:SELected]:STRing? :SEL:STR sets/queries the value of string variables or arrays in the...
Page 212: Real Number Setting Syntax
:Previous Syntax? !returns the value :Previous Syntax:DUNits <display unit_of_measure> !sets the units :Previous Syntax:DUNits? !returns the display units :Previous Syntax:UNits <HP-IB unit_of_measure> :Previous Syntax:UNits? !Displays the HP-IB units :Previous Syntax:INCRement <incr_value>[display unit_of_measure] !increments the present value :Previous Syntax:INCRement? !returns the increment value...
Page 213 HP-IB Command Dictionary Real Number Setting Syntax :RFAN:FREQ:MULT !multiplies the current frequency by 10 :RFAN:FREQ:MULT !multiplies the current frequency by 10 !Note that :STAT is not valid for :RFAN:FREQ Chapter 5 PRELIMINARY Main Menu www.valuetronics.com...
Page 214: [:Register] Subsystem
HP-IB Command Dictionary [:REGister] subsystem [:REGister] subsystem Register Subsystem contains the Save/Recall commands used in the Save/Recall registers. :CLEar <integer or string> :CLE clears the register defined by the integer value or string argument. Syntax :CLE ‘<string>’ !clears the register named ‘string’...
Page 215: Recall
HP-IB Command Dictionary [:REGister] subsystem :RECall <integer or string> :REC recalls the register defined by the integer value or string argument Syntax :REC ‘<string>’ !recalls the register named ‘string’ :REC ‘<integer value>’ !recalls the numbered register :REG:REC ‘<string>’ !equivalent command...

Page 216: Save:list
HP-IB Command Dictionary [:REGister] subsystem :SAVE:LIST? :SAVE:LIST? lists the Save/Recall registers that have been named Syntax :REG:SAVE:LIST? :SAVE:LIST? !equivalent command Screen/field equivalent :SAVE:LIST? has no equivalent field. Chapter 5 PRELIMINARY Main Menu www.valuetronics.com...
Page 217: Rfanalyzer Subsystem
HP-IB Command Dictionary :RFANalyzer subsystem :RFANalyzer subsystem :ATTenuator <string> :ATTenuator? :ATT sets/queries the amount of input attenuation in the path of the selected input port. :CONF:ATT:MODE ‘Hold’ overrides this command. Syntax :RFAN:ATT ‘40 dB’ ‘20 dB’ ‘0 dB’ RFAN:ATT? Screen/field equivalent :ATT corresponds to the Input Atten field on the INST CONFIGURE, RF ANALYZER, and SPECTRUM ANALYZER screens.
Page 218: Frequency
HP-IB Command Dictionary :RFANalyzer subsystem :FREQuency <real number> :FREQuency? :FREQ sets/queries the tune frequency for the RF Analyzer. This command requires that the RF Display field be set to FREQ (Configure screen). This command uses the “Real Number Setting Syntax”, without the :STAT command.

Page 219: Ifbw
HP-IB Command Dictionary :RFANalyzer subsystem :IFBW <string> :IFBW? :IFBW sets/queries the IF filter bandwidth. Syntax :RFAN:IFBW ‘15 kHz’ ‘230 kHz’ :RFAN:IFBW? Screen/field equivalent :IFBW controls the IF Filter field on the RF ANALYZER screen. :INPut <string> :INPut? :INPut sets/queries the RF Input Port.

Page 220: Pmeasurement:zero
HP-IB Command Dictionary :RFANalyzer subsystem :PMEasurement:ZERO This command zeroes the TX power measurement. Syntax :RFAN:PME:ZERO Screen/field equivalent :PME:ZERO is equivalent to the TX Pwr Zero field on the RF ANALYZER screen. :SENSitivity <string> :SENSitivity? :SENS sets/queries the RF Input sensitivity.
Page 221: Rfgenerator Subsystem
HP-IB Command Dictionary :RFGenerator subsystem :RFGenerator subsystem The RF Generator subsystem controls the functions of the RF GENERATOR screen. :ATTenuator <string> :ATTenuator? :ATT sets/queries the Attenuator Hold function. Syntax :RFG:ATT ‘On’ ‘Off’ :RFG:ATT? Screen/field equivalent :ATT controls the Atten Hold field on the RF GENERATOR screen.
Page 222: Fm:coupling
HP-IB Command Dictionary :RFGenerator subsystem :FM:COUPling <string> :FM:COUPling? :FM:COUP sets/queries the coupling between the Modulation Input port and the RF Generator’s FM modulator. Syntax :RFG:FM:COUP ‘AC’ ‘DC’ :RFG:FM:COUP? Screen/field equivalent :FM:COUP controls the FM Coupling field on the RF GENERATOR screen.

Page 223: Modulation:aout
HP-IB Command Dictionary :RFGenerator subsystem :MODulation:AOUT <string> :MODulation:AOUT? :MOD:AOUT sets/queries the coupling between the demodulated audio and the Audio Out Port. Syntax :RFG:MOD:AOUT ‘AC’ ‘DC’ :RFG:MOD:AOUT? Screen/field equivalent :MOD:AOUT controls the Audio Out field on the RF GENERATOR screen. :MODulation:EXTernal:AM <real number>...

Page 224: Modulation:external:destination
HP-IB Command Dictionary :RFGenerator subsystem :MODulation:EXTernal:DESTination <string> :MODulation:EXTernal:DESTination? :MOD:EXT:DEST sets/queries the type of modulation applied to the RF Generator. This command works with :MOD:EXT:AM and :MOD:EXT:FM to set the level of modulation used. Syntax :MOD:EXT:DEST ‘AM (/Vpk)’ ‘FM (/Vpk)’ :MOD:EXT:DEST?

Page 225: Output
HP-IB Command Dictionary :RFGenerator subsystem :OUTPut <string> :OUTPut? :OUTP sets/queries the RF Output Port. Syntax :RFG:OUTP ‘RF Out’ ‘Dupl’ :RFG:OUTP? Screen/field equivalent :OUTP controls the Output Port field on the RF GENERATOR and SPECTRUM ANALYZER screens. Chapter 5 PRELIMINARY Main Menu...

Page 226: Sanalyzer Subsystem
HP-IB Command Dictionary :SANalyzer subsystem :SANalyzer subsystem :ATTenuator <string> :ATTenuator? :ATT sets/queries the attenuator setting for the input port. Syntax :SAN:ATT ‘40 dB’ ‘20 dB’ ‘0 dB’ :SAN:ATT? Screen/field equivalent :ATT controls the Input Atten field on the SPECTRUM ANALYZER screen.
Page 227: Cfrequency
HP-IB Command Dictionary :SANalyzer subsystem :CFRequency <real number> :CFRequency? :CFR sets/queries the center frequency of the spectrum analyzer’s display. This command uses the “Real Number Setting Syntax”, without the :STAT command. Syntax :SAN:CFR <real number> :SAN:CFR? Screen/field equivalent :CFR controls the Center Freq field on the SPECTRUM ANALYZER screen.

Page 228: Display:scale
HP-IB Command Dictionary :SANalyzer subsystem :DISPlay:SCALe <string> :DISPlay:SCALe :DISP:SCAL sets/queries the vertical scale of the spectrum analyzer display. Syntax :SAN:DISP:SCAL ‘1 dB/div’ ‘2 dB/div’ ‘10 dB/div’ :SAN:DISP:SCAL? Screen/field equivalent :DISP:SCAL controls the scale field on the SPECTRUM ANALYZER screen. :INPut <string>...

Page 229: Marker:npeak
HP-IB Command Dictionary :SANalyzer subsystem :MARKer:NPEak :MARK:NPE moves the marker to the next peak of the spectrum analyzer display. Syntax :SAN:MARK:NPE :SAN:MARK:NPE? Screen/field equivalent :MARK:NPE controls the Marker To field on the Marker menu of the SPECTRUM ANALYZER screen. :MARKer:EXCursion <integer number>...
Page 230: Marker:peak
HP-IB Command Dictionary :SANalyzer subsystem :MARKer:PEAK :MARK:PEAK moves the marker to the highest peak of the signals on the spectrum analyzer display. Syntax :SAN:MARK:PEAK Screen/field equivalent :MARK:PEAK controls the Peak field in the Marker menu of the SPECTRUM ANALYZER screen.
Page 231: Rfgenerator
HP-IB Command Dictionary :SANalyzer subsystem :RFGenerator <string> :RFGenerator? :RFG selects between the fixed frequency generator and the tracking generator. Syntax :SAN:RFG ‘Track’ ‘Fixed’ :SAN:RFG? Screen/field equivalent :RFG controls an unnamed field in the RF Gen menu of the SPECTRUM ANALYZER screen.

Page 232: Tgenerator:amplitude :Tgenerator:amplitude
HP-IB Command Dictionary :SANalyzer subsystem :TGENerator:AMPLitude <real number> :TGENerator:AMPLitude? :TGEN:AMPL sets/queries the amplitude of the tracking generator. This command uses the “Real Number Setting Syntax”. Syntax :SAN:TGEN:AMPL <real> :SAN:TGEN:AMPL? Screen/field equivalent :TGEN:AMPL controls the Amplitude field of the Tracking Generator of the SPECTRUM ANALYZER screen.
Page 233: Tgenerator:sweep
HP-IB Command Dictionary :SANalyzer subsystem :TGENerator:SWEep <string> :TGENerator:SWEep? :TGEN:SWE set/queries the sweep type of the tracking generator. Syntax :SAN:TGEN:SWE ‘Norm’ ‘Invert’ :SAN:TGEN:SWE? Screen/field equivalent :TGEN:SWE controls the Sweep field in the Tracking Generator menu of the SPECTRUM ANALYZER screen. :TRACe:MHOLd <string>...

Page 234: Trace:normalize
HP-IB Command Dictionary :SANalyzer subsystem :TRACe:NORMalize <string> :TRACe:NORMalize? :TRAC:NORM sets/queries the type of display. Syntax :SAN:TRAC:NORM ‘A Only’ ‘A-B’ :SAN:TRAC:NORM? Screen/field equivalent :TRAC:NORM controls the Normalize field in the tracking generator of the SPECTRUM ANALYZER screen. :TRACe:SAVE :TRAC:SAVE stores the present trace on the spectrum analyzer display.

Page 235: Status
HP-IB Command Dictionary :STATus :STATus The STATus subsystem controls many of the modes of the Test Set, including the states.These commands do not correspond to fields in specific screens. :PRESet :PRES presets the Test Set. Syntax :STAT:PRES :CALibration:CONDition? :CAL:COND returns the state of the Calibration.
Page 236: Calibration:ntransition :Calibration:ntransition
HP-IB Command Dictionary :STATus :CALibration:NTRansition :CALibration:NTRansition? :CAL:NTR returns the state of the negative transition of the calibration. This query returns an integer value. Syntax :STAT:CAL:NTR :STAT:CAL:NTR? :CALibration[:EVENt?]:PTRansition :CALibration[:EVENt?]:PTRansition? :CAL:PTR returns the state of the positive transition of the calibration. This query returns an integer value.
Page 237: Communicate[:Event?]:Ntransition
HP-IB Command Dictionary :STATus :COMMunicate[:EVENt?]:NTRansition :COMMunicate[:EVENt?]:NTRansition? This query returns an integer value. Syntax :STAT:COMM:NTR :STAT:COMM:NTR? :COMMunicate[:EVENt?]:PTRansition :COMMunicate[:EVENt?]:PTRansition? This query returns an integer value. Syntax :STAT:COMM:PTR :STAT:COMM:PTR? :HARD1:CONDition? Status reporting for hardware. This query returns an integer value. Syntax :STATHARD1:COND? :HARD1:ENABle :HARD1:ENABle? This query returns an integer value.
Page 238: Hard1[:Event?]:Ptransition :Hard1[:Event?]:Ptransition
HP-IB Command Dictionary :STATus :HARD1[:EVENt?]:PTRansition :HARD1[:EVENt?]:PTRansition? This query returns an integer value. Syntax :STAT:HARD1:PTR :STAT:HARD1:PTR? :HARD2:CONDition? This query returns an integer value. Syntax :STAT:HARD2:COND :STAT:HARD2:COND? :HARD2:ENABle :HARD2:ENABle? This query returns an integer value. Syntax :STAT:HARD2:ENAB :STAT:HARD2:ENAB? :HARD2[:EVENt?]:NTRansition :HARD2[:EVENt?]:NTRansition? This query returns an integer value.
Page 239: Operation:condition
HP-IB Command Dictionary :STATus :OPERation:CONDition? This query returns an integer value. Syntax :STAT:OPER:COND? :OPERation:ENABle :OPERation:ENABle? This query returns an integer value. Syntax :STAT:OPER:ENAB :STAT:OPER:ENAB? :OPERation[:EVENt?]:NTRansition :OPERation[:EVENt?]:NTRansition? This query returns an integer value. Syntax :STAT:OPER:NTR :STAT:OPER:NTR? :OPERation[:EVENt?]:PTRansition :OPERation[:EVENt?]:PTRansition? This query returns an integer value.
Page 240: Calibrating:enable :Calibrating:enable
HP-IB Command Dictionary :STATus :CALibrating:ENABle :CALibrating:ENABle? This query returns an integer value. Syntax :STAT:CAL:ENAB :STAT:CAL:ENAB :CALibrating[:EVENt?]:NTRansition :CALibrating[:EVENt?]:NTRansition? This query returns an integer value. Syntax :STAT:CAL:NTR :STAT:CAL:NTR? :CALibrating[:EVENt?]:PTRansition :CALibrating[:EVENt?]:PTRansition? This query returns an integer value. Syntax :STAT:CAL:PTR :STAT:CAL:PTR? :QUEStionable:CONDition? This query returns an integer value.
Page 241: Questionable[:Event?]:Ntransition :Questionable[:Event?]:Ntransition
HP-IB Command Dictionary :STATus :QUEStionable[:EVENt?]:NTRansition :QUEStionable[:EVENt?]:NTRansition? This query returns an integer value. Syntax :STAT:QUES:NTR :STAT:QUES:NTR? :QUEStionable[:EVENt?]:PTRansition :QUEStionable[:EVENt?]:PTRansition? This query returns an integer value. Syntax :STAT:QUES:PTR :STAT:QUES:PTR? :MEASuring:CONDition? This query returns an integer value. Syntax :STAT:MEAS:COND? :MEASuring:ENABle :MEASuring:ENABle? This query returns an integer value.
Page 242: Measuring[:Event?]:Ptransition :Measuring[:Event?]:Ptransition
HP-IB Command Dictionary :STATus :MEASuring[:EVENt?]:PTRansition :MEASuring[:EVENt?]:PTRansition? This query returns an integer value. Syntax :STAT:MEAS:PTR :STAT:MEAS:PTR? :CDMA1:CONDition? This query returns an integer value. Syntax :STAT:CDMA1:COND? :CDMA1:ENABle :CDMA1:ENABle? This query returns an integer value. Syntax :STAT:CDMA1:ENAB :STAT:CDMA1:ENAB? :CDMA1[:EVENt?]:NTRansition :CDMA1[:EVENt?]:NTRansition? This query returns an integer value.
Page 243: Ibasic:condition
HP-IB Command Dictionary :STATus :IBASic:CONDition? This query returns an integer value. Syntax :STAT:IBAS:COND? :IBASic:ENABle :IBASic:ENABle? This query returns an integer value. Syntax :STAT:IBAS:ENAB :STAT:IBAS:ENAB? :IBASic[:EVENt?]:NTRansition :IBASic[:EVENt?]:NTRansition? This query returns an integer value. Syntax :STAT:IBAS:NTR :STAT:IBAS:NTR? :IBASic[:EVENt?]:PTRansition :IBASic[:EVENt?]:PTRansition? This query returns an integer value.
Page 244: System
HP-IB Command Dictionary :SYSTem :SYSTem [:ERRor?] Returns an integer followed by quoted string. Syntax :SYST:ERR? Chapter 5 PRELIMINARY Main Menu www.valuetronics.com...
Page 245: Tests Subsystem
HP-IB Command Dictionary :TESTs Subsystem :TESTs Subsystem :COMMENT1 | COMM1 <character data> :COMMENT1? | COMM1? Allows a comment to be entered. Allowed character set: ABCDEFGHIJKLMNOPQRSTUVWXYZ_012 3456789 abcdefghijklmnopqrstuvwxyz !”#$%&’()*+,-./:;<=>?@[\]^’{|}~ Syntax :TEST:COMM1 ‘char text’ ! 50 characters max :TEST:COMM1? :COMMENT2 | COMM2 :COMMENT2? | COMM2? Allows a comment to be entered.
Page 246: Configure | Cnfg
HP-IB Command Dictionary :TESTs Subsystem :CONFigure | CNFG <integer_value>,<character_data>,<character_data>, <integer_value>,<character_data> :CONFigure? | CNFG? :CONF allows you to configure external devices. Syntax :TEST:CONF <integer>,’<string>’,’<string>’,<integer>,’<string>’ :TEST:CONF? <integer> !returns unquoted string, 5 elements ! separated by commas :EXECution:DESTination <string> :EXECution:DESTination? :EXEC:DEST sets/queries the destination of the output, either the display or the printer.
Page 247: Execution:heading2 | Head2 :Execution:heading2? | Head2
HP-IB Command Dictionary :TESTs Subsystem :EXECution:HEADING2 | HEAD2 <string> :EXECution:HEADING2? | HEAD2? Provides a heading. Syntax :TEST:EXEC:HEAD2 ‘<string>’ :TEST:EXEC:HEAD2? :EXECution:RESults <string> :EXECution:RESults? :EXEC:RES sets/queries how to receive results from your program. Syntax :TEST:EXEC:RES ‘All’ ‘Failures’ :TEST:EXEC:RES? :EXECution:RUN <string> :EXECution:RUN? :EXEC:RUN sets/queries how to run the program.
Page 248: Library
HP-IB Command Dictionary :TESTs Subsystem :LIBRary? Returns an unquoted string. Syntax :TEST:LIBR? :PARameter[:NUMBer] <integer>,<real> :PARameter[:NUMBer?] :PAR sets/queries numerical parameters. Syntax :TEST:PAR <integer>,<real> :TEST:PAR? :PARameter:STRing <string>,<real> :PARameter:STRing? :PAR sets/queries string parameters. Syntax :TEST:PAR:STR ‘<string>’,<real> :TEST:PAR:STR? :PROCedure:AUTostart <string> :PROCedure:AUTostart? :PROC:AUT sets/queries the autostart feature of the Test Set.
Page 249: Procedure:location
HP-IB Command Dictionary :TESTs Subsystem :PROCedure:LOCation <string> :PROCedure:LOCation? :PROC:LOC defines the location of the procedure. Syntax :TEST:PROC:LOC ‘RAM’ ‘ROM’ Card’ :TEST:PROC:LOC? :PROCedure:NAME <character data> :PROCedure:NAME? Name of the procedure. Valid characters: ABCDEFGHIJKLMNOPQRSTUVWXYZ_0123456789 Syntax :TEST:PROC:NAME ‘<char>’ ! 10 characters max :TEST:PROC:NAME? :PROCedure:RUN Runs the named procedure.

Page 250: Seqnumber[:Number] ,
HP-IB Command Dictionary :TESTs Subsystem :SEQNumber[:NUMBer] <integer>,<string> :SEQNumber[:NUMBer?] Sequence Number. Valid characters: 0123456789,YN Syntax :TEST:SEQN <integer>,‘<string>’ !max 249 characters :TEST:SEQN? :SPEC[:NUMBer] <integer>,<real>,<real>,<string> :SPEC[:NUMBer?] Spec. Syntax :TEST:SPEC <integer>,<real>,<real>,’Upper’ ‘Lower’ ‘Both’ ‘None’ :TEST:SPEC? :SPEC:STRing <real>,<real>,<string> :SPEC:STRing? :SPEC:STR. Syntax :TEST:SPEC:STR <real>,<real>,’Upper’ ‘Lower’ ‘Both’...

Page 251: Trigger Subsystem
HP-IB Command Dictionary :TRIGger subsystem :TRIGger subsystem The Trigger subsystem contains commands for triggering measurements. :ABORt :ABOR ends a measurement cycle in progress. Syntax :TRIG:ABOR [:IMMediate] Triggers all active measurements in progress. Syntax :TRIG :MODE:RETRigger :MODE:RETRigger? :MODE:RETR sets/queries the retriggering setting.
Page 252 HP-IB Command Dictionary :TRIGger subsystem Chapter 5 PRELIMINARY Main Menu www.valuetronics.com...
Page 253: Ieee Common Commands
IEEE Common Commands This chapter describes IEEE 488.2 common commands. Main Menu www.valuetronics.com...
Page 254: Ieee 488.2 Common Commands
IEEE 488.2 Common Commands The IEEE 488.2 Standard defines a set of common commands which provide for uniform communication between devices on the HP-IB. These commands are common to all instruments which comply with the IEEE 488.2 Standard. These commands control some of the basic instrument functions, such as instrument identification, instrument reset, and instrument status reporting.
Page 255 IEEE Common Commands Common Command Descriptions Common Command Descriptions *IDN? (Identification Query) The *IDN? query causes a device to send its identification information over the bus. The Test Set responds to the *IDN? command by placing its identification information, in ASCII format, into the Output Queue. The response data is obtained by reading the Output Queue into a string variable of length 72.
Page 256: Common Command Descriptions
IEEE Common Commands Common Command Descriptions *OPT? (Option Identification Query) The *OPT? command tells the Test Set to identify any reportable device options install in the unit. The Test Set responds to the *OPT? command by placing information which describes any reportable installed options into the Output Queue.
Page 257 IEEE Common Commands Common Command Descriptions • The HP-IB interface is not reset (any pending Service Request is not cleared). • All Enable registers are unaffected: Service Request, Standard Event, Communicate, Hardware #1, Hardware #2, Operation, Calibration, and Questionable Data/Signal.
Page 258 IEEE Common Commands Common Command Descriptions *OPC (Operation Complete) The *OPC command allows for synchronization between the Test Set and an external controller. The *OPC command causes the Test Set to set bit 0, Operation Complete, in the Standard Event Status Register to the TRUE, logic 1, state when the Test Set completes all pending operations.
Page 259 IEEE Common Commands Common Command Descriptions 150 ! This interrupt service routine is not complete. "HP-IB Service Requests" on page 317 160 ! Refer to the 170 ! complete information. 180 SUBEND The program enables bit 0 in the Standard Event Status Enable...
Page 260 Reading the response to the *OPC? query has the penalty that both the NOTE HP-IB bus and the Active Controller handshake are in temporary holdoff state while the Active Controller waits to read the *OPC? query response from the Test Set.
Page 261 MAV bit in the Status Byte register is set to the TRUE, logic 1, state. After the service request is detected the application program can take appropriate action. Refer to the "HP-IB Service Requests" on page 317 for further information. Example BASIC program .
Page 262 IEEE Common Commands Common Command Descriptions *WAI (Wait To Complete) The *WAI command stops the Test Set from executing any further commands or queries until all commands or queries preceding the *WAI command have completed. Example BASIC statement Example OUTPUT 714;"DISP RFG;RFG:OUTP ’Dupl’;*WAI;AMPL 0 dBm" The Test Set contains signal generation and signal measurement NOTE instrumentation.
Page 263 *ESR? command. page 270 *SRE (Service Request Enable) The Test Set responds to the *SRE command. "HP-IB Service Requests" on for a detailed explanation of the *SRE command. page 317 *SRE? (Service Request Enable Query) The Test Set responds to the *SRE? command.
Page 264 IEEE Common Commands Common Command Descriptions *RCL (Recall Instrument State) The *RCL command restores the state of the Test Set from a file previously stored in battery-backed internal memory, on a memory card, on a RAM disk, or on an external disk. The *RCL command is followed by a decimal number in the range of 0 to 99 which indicates which Test Set SAVE/RECALL file to recall.
Page 265 Triggering Measurements This chapter gives you information about triggering your measurements. This includes the following topics: • "Arming Hardware-Triggered Measurements" on page 262 • "Default Trigger Mode" on page 258 • "Local/Remote Triggering Changes" on page 259 • "Measurement Pacing" on page 262 •...
Page 266: Triggering Measurements Triggering Measurements
A Trigger Event is analogous to telling the Test Set to “start the measurement now.” There are three commands that can be used to issue a Trigger Event to the Test Set through HP-IB: • A Group Execute Trigger Command (GET) as defined by IEEE 488.1-1987...
Page 267: Trigger Modes
Triggering Measurements Triggering Measurements Trigger Modes The Trigger Mode is defined by two parameters: retriggering and settling. Retriggering Retriggering refers to what a measurement does once it has completed a measurement cycle. There are two options: 1. Single retriggering causes the measurement cycle to stop once a valid measurement result has been obtained.
Page 268 This is true for both retriggering modes. This has the consequence that both the HP-IB bus and the Active Controller handshake are in a temporary holdoff state while the Active Controller waits to read the measurement result from the Test Set.
Page 269: Trigger Commands
If the HP-IB trigger mode is :RETR REP then a new measurement cycle is started and measurement results will be available for all active measurements when valid results have been obtained.
Page 270 :ABORt The :ABORt command tells the Test Set to stop a currently executing measurement cycle and get ready for a new HP-IB command. If for any reason a valid measurement cannot be made, this command allows the control program to terminate the requested measurement and regain control of the Test Set.
Page 271 Throughput" on page 264 throughput. 1. Range hold all auto-ranging and auto-tuning functions and set ranges and frequency through HP-IB. This avoids autoranging/autotuning delays. 2. Use REPetitive RETRiggering. This avoids Trigger Event processing delays.
Page 272 This is true for both retriggering modes. This has the consequence that both the HP-IB bus and the Active Controller handshake are in a temporary holdoff state while the Active Controller waits to read the measurement result from the Test Set.
Page 273: Advanced Operations
Advanced Operations Main Menu www.valuetronics.com...
Page 274: Increasing Measurement Throughput
Advanced Operations Increasing Measurement Throughput Increasing Measurement Throughput Measurement throughput is defined as the number of measurements made per unit of time. When operating the Test Set in the Internal or External Automatic Control Mode, measurement throughput is influenced by measurement speed, measurement setup time, and execution speed of the control program.
Page 275 Advanced Operations Increasing Measurement Throughput In the control program, select Gain Control, Hold (default is Auto), and make the settings recorded in manual mode. When the control program runs, the signal levels into the Test Set need to remain relatively constant since autoranging has been disabled.
Page 276 Execution speed of the control program is defined as the time required to execute a given number of program lines. Each time the HP-IB is accessed, a given amount of time is required to configure the devices on the bus for data transfer. Every time a BASIC or IBASIC OUTPUT or ENTER statement is executed this bus configuration time is incurred.
Page 277 ;: (semicolon colon) separator. The ; (semicolon) Separator. The ; (semicolon) separator tells the Test Set’s HP-IB command parser to back up one level of command hierarchy and accept the next command at the same level as the previous command.
Page 278 Increasing Measurement Throughput The ;: (semicolon-colon) Separator.. The ;: (semicolon-colon) separator tells the Test Set’s HP-IB command parser that the next command is at the top level of the command hierarchy. This allows commands from different instruments to be output on one command line.
Page 279 This queries the lock/unlock state of the Test Set’s display screen. Locking and unlocking the Test Set’s display screen is an External NOTE Automatic Control mode, HP-IB only function and cannot be done through the Test Set’s front panel. SPECial:DISPlay 'LOCKED'|'UNLOCKED' must not be invoked from the Test Set’s built-in IBASIC Controller.
Page 280: Status Reporting
Request message (SRQ) by enabling the associated bit in the Service Request Enable Register. When an enabled condition exists, the Test Set sends the Service Request message (SRQ) on the HP-IB bus and reports that it has requested service by setting the Request Service (RQS) bit in the Status Byte Register to the TRUE, logic 1, state.
Page 281 Status Register Group Summary Message Bits Status Byte Register 1 Service Request Enable Register Enabled Summary Message Service Request Generation Function Request Service Message Service Request Interface Message ch4drw01.ds4 HP 8920 Status Reporting Structure Chapter 8 PRELIMINARY Main Menu www.valuetronics.com...
Page 282: Status Byte Register
Operation Status Register Group Request Service Message Standard Event Status Register Output Queue Questionable Data/Signal Register Group Unused in HP 8920 Hardware Status Register #2 Group Hardware Status Register #1 Group Read by Serial Poll ESB MAV Status Byte Register...
Page 283 Advanced Operations Status Reporting Table 8-1 Status Byte Register Bit Assignments Binary Condition Comment Number Weighting Operation Status Register Group 1= one or more of the enabled Summary Message events have occurred since the last reading or clearing of the Event Register Request Service (RQS) when 1= Test Set has requested service...
Page 284 Advanced Operations Status Reporting Reading with a Serial Poll The contents of the Status Byte Register can be read by a serial poll from the Active Controller in response to some device on the bus sending the Service Request (SRQ) message. When read with a serial poll, bit 6 in the Status Byte Register represents the Request Service (RQS) condition.
Page 285 Advanced Operations Status Reporting Example BASIC program to read Status Byte with *STB command Example 10 INTEGER Stat_byte_reg,Stat_byte,Mstr_sum_msg 20 OUTPUT 714;"*STB?" 30 ENTER 714;Stat_byte_reg 40 Stat_byte=BINAND(Stat_byte_reg,191) !mask out the MSS bit 50 PRINT Stat_byte 60 Mstr_sum_msg=BINAND(Stat_byte_reg,64) !mask out the Stat Byte 70 PRINT Mstr_sum_msg 80 END Example...
Page 286: Status Register Structure Overview
Advanced Operations Status Reporting Status Register Structure Overview The structure of the register groups used in the Test Set is based upon the status data structures outlined in the IEEE 488 and SCPI 1994.0 Standards. There are two types of status data structures used in the Test Set: status registers and status queues.
Page 287 Status Register Group. Condition Register. A condition is a Test Set state that is either TRUE or FALSE (an HP-IB command error has occurred or an HP-IB command error has not occurred). Each bit in a Condition Register is assigned to a particular Test Set state.
Page 288 Advanced Operations Status Reporting Event Register. . The Event Register captures bit-state transitions in the Condition Register as defined by the Transition Filters. Each bit in the Event Register corresponds to a bit in the Condition Register, or if there is no Condition Register/Transition Filter combination, each bit corresponds to a specific condition in the Test Set.
Page 289: Status Queue Model
Advanced Operations Status Reporting Status Reporting Structure Operation. In general the status reporting structure described on the previous pages is used as follows: • Determine which conditions, as defined by their bit positions in the Condition Register, should cause the Summary Message to be set TRUE if they occur.
Page 290 Advanced Operations Status Reporting Figure 8-4 Status Data Structure - Queue Mode data data data data data data ch4drw04.drw Queue Summary Message Bit Queue Empty = "0" Queue Not - Empty = "1" Status Register Group Contents shows the Status Register Groups in the Test Set. The Figure 8-5 contents of each Status Register Group is explained in the following sections.
Page 291 Advanced Operations Status Reporting Figure 8-5 Test Set Status Register Groups Communicate Status Register Group Hardware Status Register #1 Group Hardware Status Register #2 Group Calibration Status Register Group Questionable Data/Signal Register Group Status Byte Register Group Output Queue data data Standard Event Status Register Group...
Page 292: Operation Status Register Group
Advanced Operations Status Reporting Operation Status Register Group The Operation Status Register Group contains information about the state of the measurement systems in the Test Set. This status group is accessed using the STATus commands. The Operation Status Register Group uses 16-bit registers and includes a Condition Register, Transition Filters, an Event Register, an Enable Register, and a Summary Message.
Page 293 Unused in the Test Set Accessing the Operation Status Register Group’s Registers The following sections show the syntax and give programming examples, using the HP BASIC programming language, for the STATus commands used to access the Operation Status Register Group’s registers.
Page 294 Advanced Operations Status Reporting Reading the Condition Register. Syntax STATus:OPERation:CONDition? Example OUTPUT 714;"STAT:OPER:COND?" ENTER 714;Register_value Reading the Transition Filters. Syntax STATus:OPERation:PTRansition? STATus:OPERation:NTRansition? Example OUTPUT 714;"STAT:OPER:PTR?" ENTER 714;Register_value Writing the Transition Filters. Syntax STATus:OPERation:PTRansition <integer> STATus:OPERation:NTRansition <integer> Example OUTPUT 714;"STAT:OPER:PTR 256" Reading the Event Register.
Page 295: Standard Event Status Register Group
Advanced Operations Status Reporting ENTER 714;Register_value Writing the Enable Register. Syntax STATus:OPERation:ENABle <integer> Example OUTPUT 714;"STAT:OPER:ENAB 256" Clearing the Enable Register. The ENABLE register is cleared by writing to it with an integer value of zero. Standard Event Status Register Group The Standard Event Status Register Group is a specific implementation of the status register model described in the Status Register Structure Overview section.
Page 296 Advanced Operations Status Reporting Figure 8-7 Standard Event Status Register Group *ESR? *ESE <integer> *ESE? Event Summary Bit (ESB) (to bit 5 of Status Byte Register) ch4drw7.drw Event Enable Register Register Chapter 8 PRELIMINARY Main Menu www.valuetronics.com...
Page 297 Advanced Operations Status Reporting Table 8-2 Standard Event Status Register Bit Assignments Binary Condition Comment Number Weighting 32879 Always 0 Reserved by IEEE 488.2 16384 Always 0 Reserved by IEEE 488.2 8192 Always 0 Reserved by IEEE 488.2 4096 Always 0 Reserved by IEEE 488.2 2048 Always 0...
Page 298 Advanced Operations Status Reporting Binary Condition Comment Number Weighting Execution Error 1 = The Test Set detected an error while trying to execute a command. The following events cause an execution error: • A <PROGRAM DATA> element received in a command is outside the legal range for the Test Set or is inconsistent with...
Page 299 Accessing the Standard Event Status Register Group’s Registers The following sections show the syntax and give programming examples (using the HP BASIC programming language) for the Common Commands used to access the Standard Event Status Register Group’s registers. Chapter 8 PRELIMINARY Main Menu www.valuetronics.com...
Page 300 Advanced Operations Status Reporting Reading the Event Register. Syntax *ESR? Example OUTPUT 714;"*ESR?" ENTER 714;Register_value The *ESR? query allows the programmer to determine the current contents (bit pattern) of the Standard Event Status Register. The Test Set responds to the *ESR? query by placing the binary-weighted decimal value of the Standard Event Status Register bit pattern into the Output Queue.
Page 301 Advanced Operations Status Reporting pattern will be a positive integer in the range of 0 to 255. The response data is obtained by reading the Output Queue into a numeric variable, integer or real. Example BASIC program 10 INTEGER Std_evn_enab_rg 20 OUTPUT 714;"ESE?"...
Page 302: Output Queue Group
0 to 255. Sending a negative number or a number greater than 255 causes an HP-IB Error: -222 Data out of range. Clearing the Enable Register. The ENABLE register is cleared by writing to it with an integer value of zero.
Page 303 Advanced Operations Status Reporting Figure 8-8 Output Queue Group Last Data Byte Last Data Byte Entered to be Read Next Data Byte Entered First Data Byte First Data Byte Entered to be Read Output Queue Message Available ( MAV ) (to bit 4 of Status Byte Register) Queue Empty = "0"...
Page 304: Error Message Queue Group
(as is the case with some Signaling Decoder measurements). Care should be exercised when reading the Output Queue since the HP-IB bus will, by design, wait until the data is available before processing further bus messages. Reading the Output Queue.
Page 305 Advanced Operations Status Reporting Figure 8-9 Error Message Queue Group Last Message Last Message Entered to be Read SYSTem: ERRor? Next Message Entered First Message First Message Entered to be Read Error Message Queue Chapter 8 PRELIMINARY Main Menu www.valuetronics.com...
Page 306: Questionable Data/Signal Register Group
Advanced Operations Status Reporting Accessing the Error Message Queue A message appears in the Error Message Queue any time bit 2, 3, 4, or 5 of the Standard Event Status register is asserted. Each message consists of a signed error number, followed by a comma separator, followed by an error description string in double quotes.
Page 307 Advanced Operations Status Reporting Figure 8-10 Questionable Data/Signal Register Group :STATus: QUEStionable: CONDition ? :PTRansition <integer> :STATus: QUEStionable :NTRansition <integer> :STATus: QUEStionable: EVENt ? :STATus: QUEStionable: ENABle <integer> Summary Message Bit (to bit 3 of Status Byte Register) ch4drw10.drw Condition Transition Event Enable...
Page 308 Advanced Operations Status Reporting Table 8-4 Questionable Data/Signal Register Group, Condition Register Bit Assignments Binary Bit Number Condition Comment Weighting 32768 Not Used (Always Defined by SCPI Version 1994.0 16384 Unused in Test 8192 Unused in Test 4096 Unused in Test 2048 Unused in Test 1024...
Page 309 Accessing the Questionable Data/Signal Register Group’s Registers The following sections show the syntax and give programming examples (using the HP BASIC programming language) for the STATus commands used to access the Questionable Data/Signal Register Group’s registers. Reading the Condition Register.
Page 310: Calibration Status Register Group
Advanced Operations Status Reporting Reading the Enable Register. Syntax STATus:QUEStionable:ENABle? Example OUTPUT 714;"STAT:QUES:ENAB?" ENTER 714;Register_value Writing the Enable Register. Syntax STATus:QUEStionable:ENABle <integer> Example OUTPUT 714;"STAT:QUES:ENAB 256" Clearing the Enable Register. The ENABLE register is cleared by writing to it with an integer value of zero.
Page 311 Advanced Operations Status Reporting Figure 8-11 Calibration Status Register Group :STATus: CALibration: CONDition ? :PTRansition <integer> :STATus: CALibration :NTRansition <integer> :STATus: CALibration: EVENt ? :STATus: CALibration: ENABle <integer> Summary Message Bit (to bit 8 of Questionable Data/Signal Register Group Condition Register ch4drw11.drw Condition Transition...
Page 312 Advanced Operations Status Reporting Table 8-5 Calibration Status Register Group, Condition Register Bit Assignments Binary Condition Comment Number Weighting 32768 Not Used (Always 0) Defined by SCPI Version 1994.0 16384 Unused in Test Set 8192 Unused in Test Set 4096 Unused in Test Set 2048 Unused in Test Set...
Page 313 Accessing the Calibration Status Register Group’s Registers The following sections show the syntax and give programming examples (using the HP BASIC programming language) for the STATus commands used to access the Calibration Status Register Group’s registers. Reading the Condition Register.
Page 314 Advanced Operations Status Reporting Syntax. Clearing the Event Register. The EVENT register is cleared whenever it is queried or whenever the Common Command *CLS is sent to the Test Set. Reading the Enable Register. Syntax STATus:CALibration:ENABle? Example OUTPUT 714;"STAT:CAL:ENAB?" ENTER 714;Register_value Writing the Enable Register.
Page 315 Advanced Operations Status Reporting Figure 8-12 Hardware Status Register #2 Group :STATus: HARDware2: CONDition ? :PTRansition <integer> :STATus: HARDware2 :NTRansition <integer> :STATus: HARDware2: EVENt ? :STATus: HARDware2: ENABle <integer> Summary Message (to bit 1 of Status Byte Register) ch4drw12.drw Condition Transition Event Enable...
Page 316 Advanced Operations Status Reporting Table 8-6 Hardware Status Register Group #2, Condition Register Bit Assignments Binary Condition Comment Number Weighting 32768 Not Used (Always 0) Defined by SCPI Version 1994.0 16384 Unused in Test Set 8192 Unused in Test Set 4096 Unused in Test Set 2048...
Page 317 Accessing the Hardware Status Register #2 Group’s Registers The following sections show the syntax and give programming examples (using the HP BASIC programming language) for the STATus commands used to access the Hardware Status Register #2 Group’s registers. Reading the Condition Register.
Page 318 Advanced Operations Status Reporting Writing the Transition Filters. Syntax STATus:HARDware2:PTRansition <integer> STATus:HARDware2:NTRansition <integer> Example OUTPUT 714;"STAT:HARD2:PTR 256" Reading the Event Register. Syntax STATus:HARDware2:EVENt? Example OUTPUT 714;"STAT:HARD2:EVEN?" ENTER 714;Register_value Clearing the Event Register. The EVENT register is cleared whenever it is queried or whenever the Common Command *CLS is sent to the Test Set.
Page 319 Advanced Operations Status Reporting Hardware Status Register #1 Group The Hardware Status Register #1 Group contains information about the Test Set’s hardware. This status group is accessed using the STATus commands. The Hardware Status Register #1 Group uses 16-bit registers and includes a Condition Register, Transition Filters, an Event Register, an Enable Register, and a Summary Message.
Page 320 Advanced Operations Status Reporting Table 8-7 Hardware Status Register Group #1, Condition Register Bit Assignments Binary Condition Comment Number Weighting 32768 Not Used (Always 0) Defined by SCPI Version 1994.0 16384 Radio Interface Card Interrupt #2 Tripped 8192 Radio Interface Card Interrupt #1 Tripped 4096...
Page 321 Accessing the Hardware Status Register #1 Group’s Registers The following sections show the syntax and give programming examples (using the HP BASIC programming language) for the STATus commands used to access the Hardware Status Register #1 Group’s registers. Reading the Condition Register.
Page 322 Advanced Operations Status Reporting Reading the Event Register. Syntax STATus:HARDware1:EVENt? Example OUTPUT 714;"STAT:HARD1:EVEN?" ENTER 714;Register_value Clearing the Event Register. The EVENT register is cleared whenever it is queried or whenever the Common Command *CLS is sent to the Test Set. Reading the Enable Register.
Page 323 Advanced Operations Status Reporting Figure 8-14 Communicate Status Register Group :STATus: COMMunicate: CONDition ? :PTRansition <integer> :STATus: COMMunicate :NTRansition <integer> :STATus: COMMunicate: EVENt ? :STATus: COMMunicate: ENABle <integer> Summary Message Bit (to bit 6 of Hardware Status Register Group #1 Condition Register) ch4drw14.drw Condition Transition...
Page 324 Accessing the Communicate Status Register Group’s Registers The following sections show the syntax and give programming examples (using the HP BASIC programming language) for the STATus commands used to access the Communicate Status Register Group’s registers. Reading the Condition Register.
Page 325 Advanced Operations Status Reporting Example OUTPUT 714;"STAT:COMM:COND?" ENTER 714;Register_value Reading the Transition Filters. Syntax STATus:COMMunicate:PTRansition? STATus:COMMunicate:NTRansition? Example OUTPUT 714;"STAT:COMM:PTR?" ENTER 714;Register_value Writing the Transition Filters. Syntax STATus:COMMunicate:PTRansition <integer> STATus:COMMunicate:NTRansition <integer> Example OUTPUT 714;"STAT:COMM:PTR 256" Reading the Event Register. Syntax STATus:COMMunicate:EVENt? Example OUTPUT 714;"STAT:COMM:EVEN?"...
Page 326 Advanced Operations Status Reporting Writing the Enable Register. Syntax STATus:COMMunicate:ENABle <integer> Example OUTPUT 714;"STAT:COMM:ENAB 256" Clearing the Enable Register. The ENABLE register is cleared by writing to it with an integer value of zero. Chapter 8 PRELIMINARY Main Menu www.valuetronics.com...
Page 327: Hp-Ib Service Requests
Advanced Operations HP-IB Service Requests HP-IB Service Requests The Test Set is capable of generating a “service request” when it requires the Active Controller to take action. Service requests are generally made after the Test Set has completed a task (such as making a measurement) or when an error condition exists (such as an internal self-calibration has failed).
Page 328: Service Request Enable Register
Request Enable Register. When an enabled service request condition exists, the Test Set sends the Service Request message (SRQ) on the HP-IB bus and reports that it has requested service by setting the Request Service (RQS) bit in the Status Byte register to the TRUE, logic 1, state.
Page 329 Advanced Operations HP-IB Service Requests Figure 8-15 Service Request Enable Register - - - Summary Message Bits - - - read by Serial Poll Service Request Status Byte Registe ESB MAV Status Byte Register Generation read by *STB? & &...
Page 330 Register allows the programmer to select which condition(s), as defined by bits 0-5 and 7 of the Status Byte Register, will generate a Service Request on the HP-IB bus. The Test Set always ignores bit 6 (binary weight 64) of the bit pattern set by the *SRE command.
Page 331 0 to 255. Sending a negative number or a number greater than 255 causes an HP-IB Error: -222 Data out of range. Clearing the Service Request Enable Register The Service Request Enable Register is cleared by sending the *SRE Common Command with a decimal value of zero.
Page 332 Example BASIC Program to Set Up and Service an SRQ Interrupt The following HP BASIC program was written for an HP 9000 Series 300 Controller and a Test Set. The program assumes that the Test Set is the only instrument on the bus. The program sets up an interrupt from the Standard Event Status Register Group, the Calibration Status Register Group, and the Hardware Status Register #1 Group.
Page 333 Advanced Operations HP-IB Service Requests Condition register conditions which will set the Summary Message TRUE if they occur: Bit 4: TX Auto-zero failed decimal value = 2^4 = 16 Bit 3: Voltmeter Self-cal failed decimal value = 2^3 = 8...
Page 334 ! 6) Enable interrupts on select code 7: 1060 The interface mask is set to a value of 2 which enables interrupts on 1070 the HP-IB bus when the SRQ line is asserted. 1080 1090 ENABLE INTR 7;2 1100 1110...
Page 335 Advanced Operations HP-IB Service Requests 1630OUTPUT Inst_address;"STAT:CAL:EVEN?" 1640ENTER Inst_address;Event_reg 1650RETURN 1660 !1670 Srvice_hard1:! 1680 ! This routine would determine which bit(s) in the Hardware Status 1690 ! Register #1 Group Event Register are TRUE, logic 1, and take 1700 ! appropriate action.
Page 336: Instrument Initialization
Test Set to a known state. With over 22 instruments utilizing greater than 25 screens containing hundreds of fields which can be programmed through the HP-IB bus, a hard copy list of the default condition for every field in every instrument screen would be cumbersome.
Page 337 3. *RST IEEE 488.2 Common Command 4. Device Clear (DCL) HP-IB Bus Command 5. Selected Device Clear (SDC) HP-IB Bus Command 6. Interface Clear (IFC) HP-IB Bus Command When the Test Set is initialized some fields are “restored” (put back to their default state), some fields are “maintained”...
Page 338: Power-On Reset
Advanced Operations Instrument Initialization Power-On Reset The Power-On Reset is accomplished by applying or cycling AC/DC power to the Test Set. For the CONFIGURE, PRINT CONFIGURE, TESTS (Execution Conditions), TESTS (Printer Setup) and I/O CONFIGURE screens, table lists the fields which are restored/initialized when the Test Set 8-11 AC/DC power is cycled.
Page 339 Advanced Operations Instrument Initialization TESTS TESTS Instrument PRINTER (Execution (Printer CONFIGURE CONFIGURE Conditions) Setup) CONFIGURE Screen Fields Screen Fields Screen Fields Screen Fields RF Level Offset RF In/Out Duplex Out Antenna In The Power-On Reset condition in the Test Set was specifically designed to configure the instruments for manual testing of an FM radio.
Page 340 Advanced Operations Instrument Initialization • Calibration data is not affected. • The HP-IB interface is reset (any pending Service Request is cleared.) • The contents of the RAM memory are unaffected. • The Test Set’s display screen is in the UNLOCKED state.
Page 341 (*OPC?) is cleared. • The Test Set’s display screen is in the UNLOCKED state. • The Power-up self-test diagnostics are not performed. • The HP-IB interface is not reset (any pending Service Request is not cleared.) Chapter 8 PRELIMINARY Main Menu...
Page 342 • The contents of the RAM memory are unaffected. *RST IEEE 488.2 Common Command The *RST Reset is accomplished by sending the *RST Common Command to the Test Set through the HP-IB bus. For the CONFIGURE, PRINT CONFIGURE, TESTS (Execution Conditions), TESTS (Printer Setup) and I/O CONFIGURE screens,...
Page 343 Advanced Operations Instrument Initialization TESTS TESTS PRINT CONFIGURE (Execution (Printer CONFIGURE Screen Fields Conditions) Setup) CONFIGURE Screen Fields Screen Fields Screen Fields Range Hold Test Procedure run mode: Auto All Continuous Notch Coupl None RF Display Freq RF Chan Std MS AMPS User Def Base Freq...
Page 344 • The Power-up self-test diagnostics are not performed. • The Contents of the SAVE/RECALL registers are not affected. • Calibration data is not affected. • The HP-IB interface is not reset (any pending Service Request is not cleared). • All Enable registers are unaffected: Service Request, Standard Event, Communicate, Hardware #1, Hardware #2, Operation, Calibration, and Questionable Data/Signal.
Page 345 Other operational characteristics are also affected by the DCL bus command as follows: • The Power-up self-test diagnostics are not performed. • The HP-IB interface is not reset (any pending Service Request is not cleared) • Measurement triggering is not affected.
Page 346 Other operational characteristics are also affected by the IFC bus command as follows: • The Power-up self-test diagnostics are not performed. • The HP-IB interface is not reset (any pending Service Request is not cleared). • The Contents of the SAVE/RECALL registers are not affected.
Page 347: Passing Control
Controller. The structure of the HP-IB bus allows for more than one Controller to be connected to the bus at the same time. As a means of ensuring that...
Page 348: Configuring The Test Set As The System Controller
1. whenever the Test Set needs to control any device connected to the HP-IB bus, such as an external disk drive, an external printer, or an external instrument 2. whenever a screen image is printed to an external HP-IB printer 3.
Page 349: Passing Control Back To Another Controller
Advanced Operations Passing Control outlined in the IEEE 488.1 and 488.2 Standards is language/controller specific. Refer to the appropriate language/controller documentation for specific implementations. Before passing control to the Test Set the Active Controller should send the Test Set the address to use when passing control back. This is accomplished using the *PCB Common Command.
Page 350: Requesting Control Using Ibasic
The Test Set will pass control back to another Controller when the IBASIC PASS CONTROL command is issued while an IBASIC program is running on the built-in IBASIC Controller. Refer to the HP Instrument BASIC User’s Handbook for a complete description of the IBASIC PASS CONTROL command.
Page 351 HP 9000 Series 300 Workstation as the external controller connected to the Test Set through the HP-IB bus. Further, it assumes that the HP-IB interface in the HP 9000 Controller is set to the default select code of 7 and address of 21.
Page 352 Test Set. The example is based upon having an HP 9000 Series 300 Workstation as the external controller connected to the Test Set through the HP-IB bus. Further, it is based on the assumption that the HP-IB interface in the HP 9000 Controller is set to the default select code of 7 and address of 21.
Page 353 Advanced Operations Passing Control OUTPUT Inst_address;"*CLS" OUTPUT Inst_address;"*ESE 2" OUTPUT Inst_address;"*SRE 32" ! Load the desired program into the Test Set from Memory Card 305 OUTPUT Inst_address;"DISP TIB” ! Display the IBASIC screen OUTPUT Inst_address;"PROG:EXEC 'DISP """&"Loading program."&"""'" OUTPUT Inst_address;"PROG:EXEC 'GET """&Prog_name$&"""'" OUTPUT Inst_address;"PROG:EXEC 'DISP """&""&"""'"...
Page 354 Advanced Operations Passing Control Pwr_suply_addrs=26 OUTPUT Internal_hpib;"*RST" CLEAR SCREEN PRINTER IS CRT EXECUTE ("REQUEST_CONTROL") 190 Try_again: ON ERROR GOTO Not_actve_cntrl DISP "WAITING TO GET CONTROL" 220 OUTPUT External_hpib;"" !If OUTPUT successful then Active Controller !If OUTPUT not successful then not Active Controller DISP "TEST SET NOW ACTIVE CONTROLLER."...
Page 355: Memory Cards/Mass Storage
Test Set’s mass storage devices. They are not intended to be a comprehensive description of the IBASIC mass storage commands and procedures. For detailed information on IBASIC commands, refer to the HP Instrument BASIC User’s Handbook. Main Menu...
Page 356: Default File System
The Test Set’s default file system is the Logical Interchange Format (LIF) System. The LIF file system is used by Hewlett-Packard BASIC on the HP 9000 Series 200/300 Workstations. See "LIF File Naming for further information on the LIF file system.
Page 357: Mass Storage Device Overview
Memory Cards/Mass Storage Mass Storage Device Overview Mass Storage Device Overview As shown in , the Test Set has both internal and figure 9-1 on page 348 external mass storage devices. There are five types of mass storage devices in the Test Set: 1.
Page 358 HP - IB I/O :, 7XX, n XX = 0 to 30 n=0,1 Front Panel Memory Card Slot HP - IB Rear Panel HP - IB LIF CS80 3 1/2" Drive :INTERNAL, 4 9122, 9133/4 ROM or SRAM card 9153, 9154 ch5drw1.drw...
Page 359 Memory Cards/Mass Storage Mass Storage Device Overview RAM Disk Mass Storage Overview Mass Mass Mass Supported Physical Storage Media Storage Storage File Location Volume Type Name Type System(s) Specifier RAM Disk Non-volatil Test Set’s ":MEMORY LIF, DOS internal ,0,unit random memory number"...
Page 360 Memory Cards/Mass Storage Mass Storage Device Overview Table 9-2 ROM Disk Mass Storage Overview Mass Mass Mass Supported Physical Storage Media Storage Storage File Location Volume Type Name Type System(s) Specifier ROM Disk Read-only Test Set ":MEMORY memory internal ,0,4" memory board Typical Uses...
Page 361 Memory Cards/Mass Storage Mass Storage Device Overview Comments • Low capacity • Contents retained by on-card lithium battery • Contents lost if on-card battery removed while card not in Test Set Memory Card slot • Recommended as primary mass storage device for program and data storage ROM Card Mass Storage Overview Mass...
Page 362: Default Mass Storage Locations
RAM with the SERVICE screen’s RAM Initialize function The mass storage location for the built-in IBASIC Controller can be changed using the MASS STORAGE IS command. Refer to the HP Instrument BASIC Users Handbook for further information on the MASS STORAGE IS command.
Page 363: Tests Subsystem
Storage Is command. The mass storage volume specifier for the desired mass storage location is appended to the Mass Storage Is command. Refer to the HP Instrument BASIC User’s Handbook for further information regarding the Mass Storage Is command. For example, to change the default mass storage location to RAM Disk unit 2, execute the following command: Mass Storage Is ":MEMORY,0,2"...
Page 364: Mass Storage Access
• The TESTS (Main Menu) screen using the Select Procedure Location: and Select Procedure Filename: fields. Only procedure files shipped with HP 11807 software or procedure files created using the TESTS (Save/Delete Procedure) screen of the TESTS Subsystem can be accessed using these fields. When created, procedure file names are prefixed with a lower case p (pFM_TEST).
Page 365: Dos And Lif File System Considerations
File Naming Conventions LIF File Naming Conventions The LIF file system is used by Hewlett-Packard BASIC on the HP 9000 Series 200/300 Workstations. It is a flat file system, which means that it has no subdirectories. The LIF file system allows up to 10-character file names which are case sensitive.
Page 366: Test Set File Naming Conventions
Memory Cards/Mass Storage DOS and LIF File System Considerations Test Set File Naming Conventions The Test Set’s TESTS Subsystem uses the following file naming conventions: • The c prefix is used to indicate a code file and is automatically prefixed onto the file name when the program code file is stored for use by the TESTS susbsystem.
Page 367: Potential File Name Conflicts
Memory Cards/Mass Storage DOS and LIF File System Considerations Potential File Name Conflicts Unexpected file operation can occur if proper consideration is not given to the different file system naming conventions and the Test Set file entry field width. • A full DOS file name is 12 characters (8 character file name + . + 3 character extension).
Page 368: File Naming Recommendations
Memory Cards/Mass Storage DOS and LIF File System Considerations • When storing files to mass storage from either the TESTS Subsystem (procedure, code, or library files) or the Save/Recall register subsystem, the Test Set puts the prefix character (c, p, l, _) onto the file name, making the file name 1 character longer than that displayed in the file name entry field.
Page 369: Test Set File Types
Formatted d Media Media SAVE ASCII STORE HP-UX Files that have been stored using the SAVE command must be retrieved using the GET command: Example SAVE "FM_TEST:,704,1" GET "FM_TEST:,704,1" Files that have been stored using the STORE command must be...
Page 370 Memory Cards/Mass Storage DOS and LIF File System Considerations TESTS Subsystem DOS File Restrictions The Test Set uses IBASIC revision 1.0. The IBASIC 1.0 file system cannot distinguish between DOS files that have been “SAVEd” and those that were “STOREd.” As shown in , SAVE and table 9-4 on page 359 STORE both produce a file type DOS.
Page 371: Using The Rom Disk
Memory Cards/Mass Storage Using the ROM Disk Using the ROM Disk The Test Set comes with several Test Procedures stored on the internal ROM disk. These Test procedures provide instrument diagnostic utilities, periodic calibration utilities, memory management utilities, a variety of general purpose utilities, and several IBASIC demonstration programs.
Page 372: Using Memory Cards
SRAM memory cards require a battery to maintain stored information. Table 9-5 Memory Card Part Numbers Part Memory Type Number 32 kilobytes SRAM HP 85700A 128 kilobytes HP 85701A 128 kilobytes SRAM HP 85702A 256 kilobytes HP 85703A 256 kilobytes...
Page 373: Setting The Write-Protect Switch
Memory Cards/Mass Storage Using Memory Cards Figure 9-2 Inserting a Memory Card Setting the Write-Protect Switch The SRAM memory card’s write-protect switch lets the user secure its contents from being overwritten or erased. The switch has two positions (see figure 9-3 •...
Page 374: The Memory Card Battery
1 year at 25 C. To retain data, the battery should be replaced annually. SRAM Card Battery Part Numbers - CR2016 or HP 1420-0383 Replacing the Battery 1. Turn the Test Set on and insert the memory card. An inserted memory card takes power from the Test Set, preventing the card’s...
Page 375: Memory Card Mass Storage Volume Specifier
Memory Cards/Mass Storage Using Memory Cards 4. Re-insert the battery holder into the memory card. 5. Remove the memory card from the Test Set. Replacing the Memory Card’s Battery WARNING Do not mutilate, puncture, or dispose of batteries in fire. The batteries can burst or explode, releasing hazardous chemicals.
Page 376 • SRAM: used for Save/Recall and data storage • Flash ROM: used when upgrading firmware • OTP (One Time Programmable): used for HP software Flash ROM cannot be used for collecting data and Save/Recall. Data cannot be loaded on Flash RAM and OTP cards with the Test Set’s memory card slot.
Page 377: Backing Up Procedure And Library Files
This program does not make backup copies of TESTS Subsystem’s code files, or copy any type of file to OTP memory cards. The COPY_PL procedure is designed for use with HP 11807 software to make backup copies of Hewlett-Packard supplied TESTS Subsystem’s Procedure and Library files or user-generated TESTS Subsystem’s...
Page 378: Copying Files Using Ibasic Commands
Memory Cards/Mass Storage Copying Files Using IBASIC Commands Copying Files Using IBASIC Commands Files can be copied from one mass storage device to another using the IBASIC COPY command. For example, to copy a file from a memory card to the left drive of an external dual-disk drive with a mass storage volume specifier of ":,702,0", execute the following IBASIC command from the TESTS (IBASIC Controller) command line: Example...
Page 379 NOTE unexpected results. For example, using the volume copy form to copy the contents of a 64 Kbyte SRAM card to an external HP-IB 630-KByte floppy disk will result in the external floppy disk having a capacity of only 64 Kbyte when the volume copy is finished. Furthermore all files on the floppy disk before the volume copy was executed will be lost and are not recoverable.
Page 380: Using Ram Disk
Memory Cards/Mass Storage Using RAM Disk Using RAM Disk RAM Disk is a section of the Test Set’s internal RAM memory that has been set aside for use as a mass storage device. RAM Disk acts much the same as an external disk drive; that is, program and data files can be stored, re-stored, erased, and retrieved from the RAM Disk.
Page 381: Initializing Ram Disks
Memory Cards/Mass Storage Using RAM Disk Initializing RAM Disks Each RAM Disk unit must be initialized before it can be used. Unit 0 can be initialized using the RAM_MNG procedure stored on internal ROM Disk. Volumes 1, 2, and 3 must be initialized from the TESTS (IBASIC Controller) screen.
Page 382 Memory Cards/Mass Storage Using RAM Disk Chapter 9 PRELIMINARY Main Menu www.valuetronics.com...
Page 383 IBASIC Controller Main Menu www.valuetronics.com...
Page 384: Ibasic Controller Introduction
IBASIC. Using this programming language it is possible to develop programs which use the Test Set’s instruments to automatically test a variety of radios. Software is available from Hewlett-Packard, the HP 11807 series, for testing the major radio systems currently in use today.
Page 385: The Ibasic Controller Screen
IBASIC Controller The IBASIC Controller Screen The IBASIC Controller Screen The Test Set has a dedicated screen for interfacing with the built-in IBASIC controller. This is the TESTS (IBASIC Controller) screen as shown in . This screen is accessed as follows: figure 10-1 •...
Page 386 IBASIC Controller The IBASIC Controller Screen The vertical rectangle at the top right side is the softkey label area. The five highlighted areas within the softkey label area correspond to the five special function keys on the front panel of the Test Set. IBASIC programs can assign tables to these keys and control program execution by using ON KEY interrupts.
Page 387: Important Notes For Program Development
TESTS Subsystem. Programs written for the TESTS Subsystem require the creation of supporting Library, Procedure, and Code files, and must be written using a specific program structure. The HP 11807A Radio Test Software packages are examples of this type of program. Refer to the "Writing Programs For the TESTS Subsystem"...
Page 388: Program Development
IBASIC Controller Program Development Program Development There are three recommended approaches for developing IBASIC programs. They are outlined in and discussed in more detail figure 10-2 later in this chapter. Since the Test Set only has the rotary knob and numeric keypad for data/character entry, developing programs on the Test Set alone is not recommended.
Page 389 Develop on Test Set Language Computer using screen Develop in Word external to Test Set "EDIT" mode Processor on PC Connect HP-IB cable to Run program in Download into Test Set and run IBASIC Test Set over program from environment...
Page 390: Interfacing To The Ibasic Controller Using Serial Ports
IBASIC Controller Interfacing to the IBASIC Controller using Serial Ports Interfacing to the IBASIC Controller using Serial Ports This section describes how to interconnect the Test Set to an external PC or terminal using the Test Set’s serial I/O ports. Program development methods #2 and #3 use PC’s or terminals connected to the Test Set through the Test Set’s serial I/O ports.
Page 391 IBASIC Controller Interfacing to the IBASIC Controller using Serial Ports Reason for Two Serial Ports A typical application uses serial port 10 to send and receive data to and from a DUT and uses serial port 9 to print or log test results to a serial printer or PC.
Page 392 10-4 on page 384 your own cables. RJ-11 cables and adapters can be wired several ways. If you buy a cable or adapter other than the HP parts listed in table 10-1 verify the connections for the pins indicated, before connecting the cables to the Test Set.
Page 393 IBASIC Controller Interfacing to the IBASIC Controller using Serial Ports Figure 10-3 Available HP RS-232 Serial Cables and Adapters 2 Meter Cable 6-pin RJ-11 Female 15 Meter Cable (in back of adapter) 25-pin 9-pin DB-9 6-pin RJ-11 DB-25 6-pin RJ-11...
Page 394 IBASIC Controller Interfacing to the IBASIC Controller using Serial Ports Figure 10-4 Connecting the Test Set Serial Port to a PC or Terminal ch6drw4.drw Table 10-2 Port 9 or Port 10 serial cable connections RJ-11 Signal DB-9 pins pins Transmit/A ddress 10 Transmit/A ddress 9...
Page 395 IBASIC Controller Interfacing to the IBASIC Controller using Serial Ports Serial Port 9 Configuration and the following paragraphs describe how to Table 10-3 on page 386 configure Serial Port 9 for communications with an external PC or terminal. Implications of the various choices are discussed. 1.
Page 396: Receive And Transmit Pacing
IBASIC Controller Interfacing to the IBASIC Controller using Serial Ports Receive and Transmit Pacing When receiving characters into the IBASIC Command Line field, the Test Set’s microprocessor responds to each entry and no buffering is required. Therefore, when using your PC or terminal to send characters to the IBASIC Command Line field, it is permissible to set Rcv Pace and Xmt Pace to None.
Page 397 IBASIC Controller Interfacing to the IBASIC Controller using Serial Ports PC Configuration To prepare for IBASIC program development, the external PC or terminal must be configured to operate with the Test Set. This configuration includes • Hardware • Terminal Emulator Software PC Serial Port Configuration Refer to for connection details.
Page 398 IBASIC Controller Interfacing to the IBASIC Controller using Serial Ports Setting Up Microsoft Windows Terminal on your PC (Windows Version 3.1) . 1. Start the Terminal program in Windows. 2. From the Terminal Menu select Settings then Emulation. 3. Select DEC VT-100 (ANSI) 4.
Page 399 IBASIC Controller Interfacing to the IBASIC Controller using Serial Ports • Stop Bits: 1 • Parity: None • Flow Control: Xon/Xoff • Connector: Com1 (be sure to match your current setup) • Parity Check: Off • Carrier Detect: Off Setting Up ProComm Revision 2.4.3 on your PC . ProComm is a general purpose telecommunications software package for PC’s with MS-DOS.
Page 400 IBASIC Controller Interfacing to the IBASIC Controller using Serial Ports 6. Enter the number 1 for MODEM SETUP. 7. Enter the number 1 for the Modem init string. 8. Press Enter to set a null string. 9. Press Esc to exit MODEM SETUP back to the SETUP MENU. 10.Enter the number 2 for TERMINAL SETUP.
Page 401 Setting Up HP AdvanceLink (HP 68333F Version B.02.00) on your PC. HP AdvanceLink is a software program which allows PCs to be used as an alphanumeric or graphics terminal. It can also automate terminal and file-transfer functions. The version described will work with PCs with the MS-DOS or PC-DOS operating systems.
Page 402 IBASIC Controller Interfacing to the IBASIC Controller using Serial Ports 5. Press REMOTE CONFIG (to set up the Serial port you selected above in Remote To). • Baud Rate: 9600 • Parity/DataBits: None/8 • Enq Ack: NO • Asterisk: OFF •...
Page 403: Terminal Configuration
DB-25 (male) connector. Set the terminal for DEC VT-100 ANSI emulation. Many ASCII terminals will also function properly. To set up the terminal, use the field settings found in the HP AdvanceLink terminal emulator section found earlier in this chapter.
Page 404: Choosing Your Development Method
Method 1 Using a BASIC language computer (either an HP technical computer or a PC running BASIC with HP-IB) is the best method for developing any size program. This is because the program can be debugged directly on the external computer before downloading the program into the Test Set.
Page 405 IBASIC Controller Choosing Your Development Method Method 2 If a BASIC language computer is not available, program development can be done directly on the Test Set using the IBASIC EDIT mode. A PC connected to the Test Set through RS-232, as described earlier in this chapter, is used as the CRT and keyboard for the internal controller.
Page 406: Computer
Method #1. Program Development on an External BASIC Language Computer Method #1. Program Development on an External BASIC Language Computer Figure 10-6 Connecting IBASIC Language Computers to the Test Set HP-IB HP 200/300 Series Controller Connect to HP-IB connector on rear panel Test Set HP-IB Personal Computer,...
Page 407: Configuring The Test Set's Hp-Ib Interface
Test Set, resulting in either an Interface Status Error or “lock up” of the HP-IB. Refer to "Passing Control" on page 337 3. Set the HP-IB Adrs field to the desired address for the Test Set. The default value is 14. Compatible BASIC Language Computers...
Page 408: Program Development Procedure
PC must be configured to operate with the Test Set. You will need: • an HP 82341B/C interface card (the HP 82335 card does not support Windows NT) • a licensed version with security key of HP BASIC for Windows. You can get the latest files from ftp://hpislsup.lvld.hp.com/pub/pc/index.html.
Page 409 HP-IB. For example, to setup the Test Set’s RF Generator use the OUTPUT command with the Test Set’s HP-IB address. If the select code of the HP-IB card in the external BASIC language computer is 7 and the address of the Test Set is 14 the address following the OUTPUT command would be 714.
Page 410: Downloading Programs To The Test Set Through Hp-Ib
• Defines the address in Test Set RAM where the downloaded program will be stored. 3. LIST #714 • Causes all program lines to transfer over HP-IB to the Test Set which is at address 714. 4. OUTPUT 714;" "END •...
Page 411 In the following program the external BASIC language controller is a PC running TransEra HT BASIC. The file is stored to the C:\HTB386 directory. If the external BASIC language controller is an HP 9000 Series 200/300 Workstation, modify the mass storage volume specifier appropriately.
Page 412 IBASIC Controller Method #1. Program Development on an External BASIC Language Computer DISP "Transfer complete." LOCAL Addr Chapter 10 PRELIMINARY Main Menu www.valuetronics.com...
Page 413: Method #2. Developing Programs On The Test Set Using The Ibasic Edit Mode
IBASIC Controller Method #2. Developing Programs on the Test Set Using the IBASIC EDIT Mode Method #2. Developing Programs on the Test Set Using the IBASIC EDIT Mode If a BASIC language computer is not available, program development can be done directly on the Test Set using the IBASIC EDIT mode. A terminal or PC connected to the Test Set through RS-232 is used as the CRT and keyboard for the Test Set’s built-in IBASIC controller.
Page 414: Entering And Exiting The Ibasic Edit Mode
IBASIC Controller Method #2. Developing Programs on the Test Set Using the IBASIC EDIT Mode To Access the IBASIC Command Line Field 1. Position the cursor on the screen’s upper left. This is the IBASIC Command Line field. 2. The IBASIC Command Line field does not have a title like other fields in the Test Set;...
Page 415: Setting Up Function Keys In Hp Advancelink
Also, scrolling a program works best when the Terminal window display is maximized). Setting Up Function Keys in HP AdvanceLink • From the Main (highest level) screen, set up the 8 softkeys as follows: 1.
Page 416: Setting Up Function Keys In Procomm
IBASIC Controller Method #2. Developing Programs on the Test Set Using the IBASIC EDIT Mode Setting Up Function Keys in ProComm ProComm does not have function keys. However, escape sequences can be assigned to number keys 0 through 9 by using the Keyboard Macro function.
Page 417: Method #3. Developing Programs Using Word Processor On A Pc (Least Preferred)
IBASIC Controller Method #3. Developing Programs Using Word Processor on a PC (Least Preferred) Method #3. Developing Programs Using Word Processor on a PC (Least Preferred) The third method of IBASIC program development is to write the program using a word processor on a PC, save it as an ASCII file, and then download it into the Test Set through the serial port.
Page 418: Writing Lines Of Ibasic Code On A Word Processor
IBASIC Controller Method #3. Developing Programs Using Word Processor on a PC (Least Preferred) Writing Lines of IBASIC Code on a Word Processor When writing IBASIC programs, follow these steps to ensure that the Test Set will accept the code when it is downloaded. 1.
Page 419 IBASIC Controller Method #3. Developing Programs Using Word Processor on a PC (Least Preferred) 2. Select the Terminal application in the Accessories Group. Set it up as described in earlier in this chapter. 3. Select the following: • Settings Text Transfers Flow Control: Line at a Time Delay Between Lines: 25/10 Sec Word Wrap...
Page 420 IBASIC Controller Method #3. Developing Programs Using Word Processor on a PC (Least Preferred) For longer programs (greater than 100 lines), transferring the ASCII text file directly into the IBASIC program memory through the RS-232 serial port is too time consuming. To speed the process up, it is necessary to transfer the program using a two step process.
Page 421 IBASIC Controller Method #3. Developing Programs Using Word Processor on a PC (Least Preferred) 240 Purge_it:SUB Purge_it!Purges File_name on card COM /File_name/ File_name$ OFF ERROR PURGE File_name$&":INTERNAL" SUBEND 290 Code:SUB Code(File_name$,In$) ON ERROR CALL Purge_it !Branches if CREATE statement returns error CREATE ASCII File_name$&":INTERNAL",650 !Creates file on card...
Page 422 IBASIC Controller Method #3. Developing Programs Using Word Processor on a PC (Least Preferred) Sending ASCII Text Files Over RS-232 With Windows Terminal Set up the Windows Terminal emulator software on the PC as covered "Setting Up Microsoft Windows Terminal on your PC (Windows Version 3.1)" on .
Page 423 IBASIC Controller Method #3. Developing Programs Using Word Processor on a PC (Least Preferred) Sending ASCII Text Files over RS-232 with ProComm Communications Software Set up the ProComm terminal emulator software on the PC as covered . On the Test "Setting Up ProComm Revision 2.4.3 on your PC"...
Page 424 IBASIC Controller Method #3. Developing Programs Using Word Processor on a PC (Least Preferred) 17.Before running the transferred program, execute a SCRATCH command on the IBASIC Command Line line to remove the ASCII_DN download program from Test Set memory. 18.Next, execute a GET TEMP_CODE command on the IBASIC Command Line.
Page 425: Uploading Programs From The Test Set To A Pc
2. The PC must receive the data through its serial port and direct the data to a file on disk. This can be done by a terminal emulator program such as Windows Terminal, ProComm, or HP AdvanceLink. This requires having the serial port connection established as outlined in "Interfacing to the IBASIC Controller using Serial Ports"...
Page 426: Serial I/O From Ibasic Programs
Serial Port 10 settings are adjustable only with IBASIC commands. There is no screen for Serial Port 10 settings. For more information, see which gives the Chapter 5, "HP-IB Command Dictionary" command syntax for Serial Port 9 and 10. Chapter 10 PRELIMINARY Main Menu...
Page 427 IBASIC Controller Serial I/O from IBASIC Programs Example IBASIC Program Using Serial Port 10 The following program illustrates I/O to both serial ports. The program sends a prompt message to a terminal connected to Serial Port 9 and waits for a response from the user at the terminal. When the response is received from the terminal connected to Serial Port 9, a series of ASCII characters are sent out Serial Port 10.
Page 428: Serial Port 10 Information
IBASIC Controller Serial I/O from IBASIC Programs Serial Port 10 Information Serial Port 10 is sometimes called Serial Port B in Test Set documentation and programs. The default Serial Port 10 settings are the same as Serial Port 9. They 1.
Page 429: Program Subsystem
IBASIC Controller PROGram Subsystem PROGram Subsystem Introduction The PROGram Subsystem provides a set of commands which allow an external controller to generate and control an IBASIC program within the Test Set. The PROGram Subsystem in the Test Set is a limited implementation of the PROGram Subsystem defined in the Standard Commands for Programmable Instruments (SCPI) Standard.
Page 430: Test Set Program Subsystem
IBASIC Controller PROGram Subsystem Test Set PROGram Subsystem The Test Set was designed to store only one IBASIC program in RAM memory at any given time. The PROGram Subsystem commands, as implemented in the Test Set, operate differently than described in the SCPI Standard.
Page 431 IBASIC Controller PROGram Subsystem • :EXPLicit:MALLocate • :EXPLicit:MALLocate? • :EXPLicit:NUMBer • :EXPLicit:NUMBer? • :EXPLicit:STATe • :EXPLicit:STATe? • :EXPLicit:STRing • :EXPLicit:STRing? • :EXPLicit:WAIT Sending the Test Set any of the unsupported SCPI PROGram NOTE Subsystem commands can result in unexpected and/or erroneous operation of IBASIC.
Page 432: Program Subsystem Commands
When a PROGram Subsystem command is sent to the Test Set through NOTE HP-IB from an external controller the Test Set is put into REMOTE mode. The Test Set must be put in LOCAL mode to use the front-panel keys or to use the serial ports to input data into the IBASIC Command line.
Page 433 IBASIC Controller PROGram Subsystem To download an IBASIC program, any currently resident IBASIC program must first be deleted using the :DELete:ALL command. Attempting to download a new IBASIC program while an IBASIC program is currently resident causes IBASIC Error: -282 Illegal program name. It is possible for the PROGram Subsystem to think that there is an NOTE IBASIC program resident in the Test Set when, in actuality, there is...
Page 434 IBASIC Controller PROGram Subsystem Example BASIC program to download an IBASIC program to Test Set 10 OUTPUT 714;"PROG:DEL:ALL"!Delete current program 20 OUTPUT 714;"PROG:DEF #0"!Create program, send header 30 OUTPUT 714;"10 FOR J = 1 TO 10"!1st prog line 40 OUTPUT 714;"20 DISP J"!2nd prog line 50 OUTPUT 714;"30 BEEP"!3rd prog line 60 OUTPUT 714;"40 NEXT J"!4th prog line 70 OUTPUT 714;"50 END"END!Send END message at end of last line...
Page 435 IBASIC Controller PROGram Subsystem • The data starts with a header which begins with a “#”, followed by a single non-zero digit in the range 1-9 which specifies the number of digits in the following count field, followed by a series of digits in the range of 0-9 which gives the number of data bytes being sent, followed by the number of data bytes specified by the count field.
Page 436 IBASIC Controller PROGram Subsystem :DELete:ALL. The :DELete:ALL command is used to delete an IBASIC program in the Test Set. If the IBASIC program in the Test Set is in the RUN state, an IBASIC Error: -284 Program currently running error is generated and the program is not deleted. Syntax PROGram[:SELected]:DELete:ALL Example...
Page 437 (<var_name> not enclosed in quotes) will generate the following error: HP-IB Error: -112 Program mnemonic too long. If an attempt is made to set the value of a numeric variable or array and no IBASIC program is in the Test Set an IBASIC Error: -282 Illegal program name is generated.
Page 438 The examples which follow represent the capabilities of HP Rocky Mountain BASIC programming language running on an HP 9000/300 Series Controller.
Page 439 IBASIC Controller PROGram Subsystem Example querying the value of a simple variable OUTPUT 714;"PROGram:SELected:NUMBer? Variable" ENTER 714;Value OUTPUT 714;"PROG:NUMB? Variable" ENTER 714;Value This example assumes that the variable named Value in the ENTER statement is the same type as the variable named Variable in the IBASIC program. Example querying the value of a one dimensional array [Array(5)] with 6 elements OUTPUT 714;"PROGram:SELected:NUMBer? Array"...
Page 440 Effect of STATe Commands Desired Current State of IBASIC Program State of IBASIC Program (STATe PAUSED command RUNNING STOPPED sent to Test Set) HP-IB RUNNING RUNNING Error: -221 Settings conflict CONT HP-IB RUNNING HP-IB Error: -221 Error: -221 Settings Settings...
Page 441 Attempting to send a <var_name> longer than 12 characters as character data (<var_name> not enclosed in quotes) will generate the following error: HP-IB Error: -112 Program mnemonic too long. If the programmer wishes to append the IBASIC “$” string identifier NOTE onto the string variable name, the string variable name must be sent as string data, that is enclosed in quotes.
Page 442 (<var_name> enclosed in quotes). For example, OUTPUT 714;"PROG:STR? ’Var_name’". Attempting to send a <var_name> longer than 12 characters as character data (<var_name> not enclosed in quotes) will generate the following error: HP-IB Error: -112 Program mnemonic too long Chapter 10 PRELIMINARY Main Menu www.valuetronics.com...
Page 443 Test Set into the external controller will depend upon the programming language used in the external controller. The examples which follow represent the capabilities of HP Rocky Mountain BASIC programming language running on an HP 9000/300 Series Controller. Example of querying the value of a simple string variable OUTPUT 714;"PROGram:SELected:STRing? Variable"...
Page 444 HP-IB input buffer before the IBASIC program is PAUSED or STOPPED, the HP-IB bus will appear to be locked up. This is due to the fact that the HP-IB bus and the external controller will be in a temporary holdoff state while waiting for the HP-IB input buffer to empty.
Page 445 IBASIC program is either STOPPED or PAUSED. This is due to the fact that the HP-IB bus and the external controller will be in a temporary holdoff state while waiting for the Test Set to put a 1 into the Output queue to satisfy the :WAIT? query command.
Page 446: Using The Execute Command
When a PROGram Subsystem command is sent to the Test Set through NOTE HP-IB from an external controller the Test Set is put into REMOTE mode. The Test Set must be put in LOCAL mode to use the front panel keys or to use the serial ports to input data into the IBASIC Command line.
Page 447 IBASIC Controller PROGram Subsystem Entering a new IBASIC program line IBASIC program lines can be entered directly into the Test Set’s RAM memory, one line at a time, from an external controller using the PROGram:EXECute command as follows: Example PROG:EXEC ’<new program line number/program line>’ where <new program line number/program line>...
Page 448 Test Set. This procedure assumes the Test Set’s HP-IB address is set to 14. The example also assumes the external controller is an HP 9000 Series 300 Controller. 1. Access the Test Set’s TESTS (IBASIC Controller) screen.
Page 449 20 DIM Prog_line$[200] !Holds longest program line in Test Set 30 DIM File_name$[10] !Holds the name of file to store IBASIC program 40 Addr=714 !Test Set HP-IB address 50 LINPUT "Enter name of file to store IBASIC program in:",File_name$ 60 OUTPUT Addr;"PROG:DEF?"...
Page 450 IBASIC Controller PROGram Subsystem 210 ASSIGN @File TO * !Close the file 220 END Saving an IBASIC Program To A Memory Card The following procedure can be used to save an IBASIC program from the IBASIC Controller’s RAM memory to a memory card inserted into the front panel of the Test Set.
Page 451: The Tests Subsystem
The Test Set’s automated user-interface was designed using this approach. Hewlett-Packard has developed software specifically designed to run on the Test Set. The HP 11807 Radio Test Software provides the user with a library of industry standard tests. All radio specific information has been removed from the software.
Page 452: Tests Subsystem File Descriptions
IBASIC Code file that can reside either on the Memory card, on an external disk drive connected to the HP-IB port of the Test Set, or in an internal RAM disk. The name of this file is preceded by a lower case c in the Test Set.
Page 453 IBASIC Controller The TESTS Subsystem A Library is required to use the user-interface screen functions of the TESTS Subsystem. If the program is simple enough that there is no need for user-input, or if all the user-input is simple enough to be accomplished with INPUT statements, a [NO LIB] option is available.
Page 454: Tests Subsystem Screens
IBASIC Controller The TESTS Subsystem TESTS Subsystem Screens The TESTS Subsystem uses several screens to create, select, and copy files, and to run tests. The Main TESTS Subsystem Screen Refer to figure 10-8 The TESTS (Main Menu) screen is accessed by pressing the front panel TESTS key.
Page 455 (audio load impedance, audio power, power supply voltage). • The External Devices screen identifies all connected HP-IB equipped instruments and their HP-IB addresses. • The Save/Delete Procedure screen is used to save or delete Procedures.
Page 456 IBASIC Controller The TESTS Subsystem Chapter 10 PRELIMINARY Main Menu www.valuetronics.com...
Page 457: Error Messages
Error Messages Main Menu www.valuetronics.com...
Page 458: General Information About Error Messages
Positive Numbered Error Messages Positive numbered error messages are generally associated with IBASIC. Refer to the HP Instrument BASIC User’s Handbook for information on IBASIC error messages. Positive numbered error messages take the form:...
Page 459: Ibasic Error Messages
IBASIC Error Messages are associated with IBASIC operation. IBASIC error messages can have both positive and negative numbers. Refer to the HP Instrument BASIC User’s Handbook for information on positive numbered error messages. Refer to the HP-IB Error Messages section of the Programmer’s Guide for information on negative numbered error...
Page 460: Text Only Error Messages
Error Messages General Information About Error Messages HP-IB Error Messages HP-IB Error Messages are associated with HP-IB operation. Refer to the Programmers Guide for information on HP-IB error messages. HP-IB error messages take the form: HP-IB Error: -XX HP-IB Error For example: HP-IB Error: -410 Query INTERRUPTED.
Page 461: The Message Display
Other messages are only displayed when the error first occurs; they are removed when a key is pressed or the knob is turned, or when an HP-IB command is received. Many of the messages are displayed on the ERROR MESSAGE screen until the instrument is turned off.
Page 462 Error Messages General Information About Error Messages Text Only Error Messages Operation errors generally occur when you try to do something the Test Set was not designed to do. Most messages tell you what to do to correct the problem, (turn something off, reduce a field’s value, press a certain key,…and so forth).
Page 463 Error Messages General Information About Error Messages • Cal file checksum incorrect - initializing file. This error usually occurs after changing the Test Set’s firmware ROM’s. It is not a problem in that instance, but should not re-appear during subsequent operation of the Test Set. •...
Page 464: Hp-Ib Errors
Error Messages HP-IB Errors HP-IB Errors Most HP-IB errors occur when the control program attempts to query a measurement that is not currently available, or tries to access an instrument connected to the external HP-IB without configuring the Test Set as the System Controller. When diagnosing the cause of an error condition check for these conditions first.
Page 465: Text Only Hp-Ib Errors
HP-IB Error: Register does not exist. The following list contains a subset of the Test Set’s text only HP-IB error messages. These messages represent error conditions which may require explanation in addition to the error message text.
Page 466 346 for more details. HP-IB Error: HP-IB Units cause invalid conversion of attr. This error is generated when trying to change Attribute Units and one of the Data Function values is set to zero. If this error is encountered the programmer must change the Data Function settings to values that can be converted to the new units_of_measure.
Page 467 • controlling the Test Set with a program running on an external controller • using the Test Set manually to print to an external HP-IB printer • using the Test Set manually to access procedure/library/code files stored on an external HP-IB disk HP-IB Parser.
Page 468 Error Messages Numbered HP-IB Error Descriptions − ;AMPL − Error Data type error The parser recognized a data element different than one allowed. For example, numeric or string data was expected but block data was encountered. − Error GET not allowed A Group Execute Trigger was received within a program message (see IEEE 488.2, 7.7).
Page 469 Error Messages Numbered HP-IB Error Descriptions − Error Header suffix out of range Indicates that a nonheader character has been encountered in what the parser expects is a header element. − Error Numeric data error − − This error, as well as errors...
Page 470 Error Messages Numbered HP-IB Error Descriptions − Error Suffix not allowed A suffix was encountered after a numeric element which does not allow suffixes. − Error Character data error − − This error, as well as errors 141 through 148, are generated when parsing a character data element.
Page 471 Error Messages Numbered HP-IB Error Descriptions − Error Block data error − − This error, as well as errors 161 through 168, are generated when parsing a block data element. − Error Invalid block data A block data element was expected, but was invalid for some reason (see IEEE 488.2 7.7.6.2).
Page 472 Error Messages Numbered HP-IB Error Descriptions Indicates that the program message unit sequence, sent with a *DDT or *DMC command, is syntactically invalid (see . − Error Macro parameter error Indicates that a command inside the macro definition had the wrong number or type of parameters.
Page 473 Error Messages Numbered HP-IB Error Descriptions − Error Trigger deadlock Indicates that the trigger source for the initiation of a measurement is set to GET and subsequent measurement query is received. The measurement cannot be started until a GET is received, but the GET would cause an INTERRUPTED error.
Page 474 Error Messages Numbered HP-IB Error Descriptions − Error Data questionable Indicates that measurement accuracy is suspect. − Error Hardware error Indicates that a legal program command or query could not be executed because of a hardware problem in the device.
Page 475 Error Messages Numbered HP-IB Error Descriptions − Error File name not found Indicates that a legal program command or query could not be executed because the file name on the device media was not found. For example, an attempt was made to read or copy a nonexistent file.
Page 476 Error Messages Numbered HP-IB Error Descriptions − Error Illegal macro label Indicates that the macro label defined 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 header syntax.
Page 477 Error Messages Numbered HP-IB Error Descriptions − Error Illegal program name The name used to reference a program was invalid. For example, redefining an existing program, deleting a nonexistent program, or in general, referencing a nonexistent program. − Error Illegal variable name An attempt was made to reference a nonexistent variable in a program.
Page 478 Error Messages Numbered HP-IB Error Descriptions Indicates that nonvolatile calibration data used by the *CAL? command has been lost. − Error Save/recall memory lost Indicates that the nonvolatile data saved by the *SAV command has been lost. − Error Configuration memory lost Indicates that nonvolatile configuration data saved by the device has been lost.
Page 479 Error Messages Numbered HP-IB Error Descriptions This message usually appears when trying to access a measurement that is not active. For example, you cannot query the DTMF Decoder measurements from the DUPLEX TEST screen, or query the TX Frequency measurement when the TX Freq Error measurement is displayed.
Page 480 Error Messages Numbered HP-IB Error Descriptions Indicates that an attempt was made to send an order type Mobile Station Control Message (that is - order a change in power level, put the mobile station in maintenance mode, or send an alert message to the mobile station) when the Call Processing Subsystem was not in the Connect state.
Page 481 Error Messages Numbered HP-IB Error Descriptions Indicates that the simulated Base Station’s internal timer expired before receiving a response from the mobile station during a registration attempt. The internal timer is set to 20 seconds when the Register state is entered.
Page 482 Error Messages Numbered HP-IB Error Descriptions − Error 1313 Timeout occurred while in Maintenance state. Indicates that the simulated Base Station’s internal timer expired before the mobile station was taken out of the maintenance state. The internal timer is set to 20 seconds when the maintenance order is sent to the mobile station.
Page 483 Active Controller Battery ‘.PGM’ files when capability required memory card ‘.PRC’ files Active Measurement part numbers ‘_’ files AdvanceLink (HP 68333F Version replacing ‘c’ files B.02.00) terminal emulator ‘l’ files ‘n’ files Annunciators ‘p’ files Arming measurements ASCII Text Files...
Page 484 Default file system accessing the error message condition register bit Display queue assignments locking display screen via Error messages Call Processing Subsystem HP-IB types of error messages, described Display Units error messages Code files DOS file names operation Common Commands...
Page 485 Increasing measurement speed LIF file names Hierarchical File System (HFS) (see Increasing naming files Measurement Speed) storing code files HP 8920A Memory Card Part Instrument Initialization (see File types Numbers Instrument Initialization) Files HP 8920B Memory Card Part backing up...
Page 486 Control) querying ON/OFF state Remote Interface Message turning ON and OFF Capabilities Instrument Initialization SRQ (see Service Requests) Device Clear (DCL) HP-IB Bus IEEE 488.2 Command Common Commands Front panel PRESET key Common Commands CLS Interface Clear (IFC) HP-IB Bus...
Page 487 Index Selected Device Clear (SDC) HP-IB Bus Command keys Library files Internal Automatic Control Mode front panel backing up LIF file names LIF file system initializing media for lock up HP-IB bus Index Main Menu www.valuetronics.com...
Page 488 ROM card requesting control from IBASIC ROM Disk Condition Register bit selecting assignments SRAM card OTP Memory card AdvanceLink (HP 68333F write protecting Output Queue Group Version B.02.00) terminal Mass storage locations accessing the output queue emulator default values Overlapped Commands Microsoft®...
Page 489 Index Questionable Data/Signal RAM Disk Save/Recall Registers Register Group initializing default mass storage locations accessing registers contained in using RAM_MNG Sequential Commands condition register bit RJ-11 jack Serial Port assignments ROM Disk cables/adapters for using configuration ROM Memory card input buffer length receive/transmit pacing select code 10 select code 9...
Page 490 Group (see Operation file system StatusRegister Group) file types Output Queue Group (see HP-IB units - changing Output Queue Group) HP-IB units - definition Questionable Data/Signal HP-IB units - guidelines Register Group (see HP-IB units - querying QuestionableData/Signal IEEE 488.1 Interface Function...
Page 491 Index Uploading programs from Test Volume copy Wildcards Set to external controller Word processor Uploading programs from Test configuring for program Set to PC development Uploading programs to Test Set transferring programs to Test writing lines of IBASIC code Write-protect switch Index Main Menu www.valuetronics.com...
Page 492 Index Xon/Xoff Index Main Menu www.valuetronics.com...