Page 1 Programming Guide HP 83751A/B and HP 83752A/B Synthesized Sweeper...
Page 2 Supersedes: October 1994 Master set: 83750-90002 Printed in USA March 1997 Serial Numbers. This manual applies directly to instruments with serial prel% 3447A and below. This manual also applies to firmware revision 2.0 and above. For Grmware revisions below 2.0 contact your nearest Hewlett-Packard service center for a firmware upgrade.
Page 3 Certification Hewlett-Packard Company certifies that this product met its published further certifies that its calibration measurements are traceable to the United States National Institute of Standards and Technology, to the extent allowed by the Institute’s calibration facility, and to the calibration facilities of other International Standards Organization members.
Page 4 Warranty This Hewlett-Packard instrument product is warranted against defects in material and workmanship for a period of one year from date of shipment. During the warranty period, Hewlett-Packard Company will, at its option, either repair or replace products which prove to be defective. For warranty service or repair, this product must be returned to a service facility designated by Hewlett-Packard.
Page 5 Assistance Product maintenance agreements and other customer assistance agreements are available for Hewlett-Packard products. Fbr any assistance, contact your nearest Hewlett-Packard Sales and service...
Page 6 Safety Notes The following safety notes are used throughout this manual. Familiarize yourself with each of the notes and its meaning before operating this instrument. The caution note denotes a hazard. It calls attention to a procedure which, C A U T I O N if not correctly performed or adhered to, could result in damage to or destruction of the instrument.
Page 7 General Safety Considerations Before this instrument is switched on, make sure it has been properly W A R N I N G grounded through the protective conductor of the ac power cable to a socket outlet provided with protective earth contact. Any interruption of the protective (grounding) conductor, inside or outside the instrument, or disconnection of the protective earth terminal can result in personal injury.
Page 8 How to Use This Guide This guide uses the following conventions. This represents a key physically located on the instrument. This indicates a “softkey, II a key whose label is determined Sof tkey by the instrument’s firmware. Screen Text This indicates text displayed on the instrument’s screen.
Page 9: Table Of Contents
Contents 1. Getting Started Programming HP-IB General Information ....Interconnecting Cables ......
Page 10 ..1-19 Forgiving Listening and Precise Talking ....Types of Commands Subsystem Command Trees ... . . 1-21 .
Page 11 ..Use of the Command Tables HP-IB Check, Example Program 1 ..Program Comments ... . .
Page 12 Related Documents ....Programming Commands Command Syntax ....
Page 13 Query Syntax ....2-14 2-14 ..2-15 CALibration:PMETer:FLATness:INITiate? CALibration:PMETer:FLATness:NEXT? ..2-15 ....Correction Subsystem 2-16 .
Page 14 FREQuency[:CW]:AUTO and ... 2-27 FREQuency[:FIXed]:AUTO 2-27 ....Query Syntax ....2-28 FREQuency:MANual Query Syntax .
Page 15 2-44 Output Subsystem ..2-44 ..2-44 Query Syntax ..2-44 OUTPut:IMPedance? . . . 2-45 ..Power Subsystem 2-45 POWer:ALC:CFACtor .
Page 16 Query Syntax ....2-55 ....2-56 Query Syntax .
Page 17 2-6’7 Query Syntax ....2-68 ....2-68 Query Syntax ....SWEep:TIME .
Page 18 ..... . . Abort 3-24 Interface Function Codes ....3-25 ..HP 83750 Series Status Byte Descriptions 3-26...
Page 19 Error Messages ....The Error/Event Queue ....Error numbers .
Page 20 ....2-64 2-2. HP 83750 SCPI Sweep Mode Programming Table ..2-71 2-3. Sweeper Key Codes ....
Page 21: Getting Started Programming
Getting Started Programming...
Page 22 Any instrument having HP-II3 capability can be interfaced to the sweeper, including non-HP instruments that have “GPIB,” “IEEE-488, ’ “ANSI MCl. 1,” or ‘IEC-625” capability (these are common generic terms for HP-E!; all are portion of the manual specifically describes interfacing the sweeper to a computer.
Page 23: Hp-Ib General Information
HP-IB timing cycles. Instrument Addresses Each in.stnunent in an HP-IB network must have a unique address, an integer ranging in value from 0 to 30. The default address for the sweeper is 19, but this can be changed using the (m) [m) keys or rear panel switch.
Page 24: Hp-Ib Instrument Nomenclature
Getting Started Programming HP-IB General Information An HP-IB instrument is categorized as a ‘listener, n “talker, * or “controller, n depending on its current function in the network. Listener A listener is a device capable of receiving data or commands from other instruments.
Page 25: Hp-Ib Command Statements
Consider the following explanations as a starting point, but for detailed information consult the BASIC language reference manual, the I/O programming guide, and the HP-IB manual for the particular computer used. Syntax drawings accompany each statement: All items enclosed by a circle or oval are computer specific terms that must be entered exactly as described;...
Page 27: Remote
HP-II3 instruments for remote operation (although nothing appears to happen to the instruments until they are addressed to which affects the HP-B instrument located at address 19, or which effects four instruments that have addresses 19, 21, 26, and 15.
Page 28: Locallockout
Getting Started Programming HP-IB General Information Local Lockout Local Lockout can be used in conjunction with REMOTE to disable the front panel (LOCAL) key. With the (ml key disabled, only the controller (or a hard reset by the POWER switch) can restore local control. The syntax is:...
Page 30 Getting Started Programming HP-IB General Information output Output is used to send function commands and data commands from the controller to the addressed instrument. The syntax is: where USING is a secondary command that formats the output in a particular way, such as a binary or ASCII representation of numbers.
Page 32 Getting Started Programming Enter Enter is the complement of OUTPUT, and is used to transfer data from the addressed instrument to the controller. The syntax is: ENTER is always used in conjunction with OUTPUT, such as: OUTPUT 719; ‘I . . . programming codes . . . ” ENTER 719;...
Page 33: Related Statements Used By Some Computers
ASCII CR (carriage return), comma, or semicolon might cause a false termination. Suppression of the EOI causes the computer to accept all bit patterns as data, not conunands, and relies on the HP-IB EOI (end or identify) line for correct end-of-data termination.
Page 34: Getting Started With Scpi
Getting Started with SCPI This section of chapter 1 describes the use of the Standard Commands for Programmable Instruments language (SCPl). This section explains how to use SCPI commands in general. The instrument command summary in Chapter 5 lists the specific commands available in the instrument. This section presents only the basics of SCPI.
Page 35: Definitions Of Terms
An instrument is any device that implements SCPI. Most instruments are electronic measurement or stimulus devices, but this is not a requirement. Similarly, most instruments use an HP-D3 interface for communication. The same concepts apply regardless of the instrument function or the type of interface used.
Page 36: Standard Notation
For example, <new line> represents the ASCII character with the decimal value 10. Siruilarly, <‘END> means that EOI is asserted on the HP-II3 interface. Words in angle brackets have much more rigidly defined meaning than words used in ordinary text. For example, this section uses the word “message”...
Page 37: Command Examples
<new line>. If you are using simple OUTPUT statements in HP BASIC, this is taken care of for you. In HP BASIC, you type: OUTPUT Source;“:FREQuency:CW?”...
Page 38: Essentials For Beginners
Essentials for Beginners This subsection discusses elementary concepts critical to &st-time users of SCPI. Read and understand this subsection before going on to another. This subsection includes the following topics: These paragraphs introduce the basic types Program and Response of messages sent between instruments and Messages controllers.
Page 39: Program And Response Messages
Getting Started Programming Essentials for Beginners Program and Response Messages To understand how your instrument and controller communicate using SCPI, you must understand the concepts of program and response messages. instrument. Conversely, response messages are the formatted data sent from the instrument to the controller.
Page 40 Getting Started Programming Essentials for Beginners set of conunands that roughly corresponds to a functional block inside the instrument. For example, the POWer subsystem contains commands for power generation, while the STAT subsystem contains commands for accessing status registers. : MEAS : VOLT? Figure l-l.
Page 41: Subsystem Command Trees
Getting Started Programming Essentials for Beginners Subsystem Command Trees The Command Tree Most programming tasks involve subsystem commands. SCPI uses a Structure hierarchical structure for subsystem commands similar to the file systems on most computers. In SCPI, this command structure is called a command r o o t l e v e l 1 level...
Page 42 Getting Started Programming Essentials for Beginners l RxwrOnandReset After power is cycled or after *RST, the current path is set to the root. A message terminator, such as a <new line> character, sets the current path to the root. Many progr amming languages have output statements that send message terminators automatically.
Page 43 Getting Started Programming Essentials for Beginners R S e t s c u r r e n t p a t h t o R O O T change current path Figure l-3. Proper Use of the Colon and Semicolon Figure l-3 shows examples of how to use the colon and semicolon to navigate efficiently through the command tree.
Page 44: Subsystem Command Tables
Getting Started Programming Essentials for Beginners Subsystem Command ‘Ihbles These paragraphs introduce a more complete, compact way of documenting subsystems using a tabular format. The command table contains more information than just the command hierarchy shown in a graphical tree. In particular, these tables list command parameters for each command and response data formats for queries.
Page 45: Reading The Command Table
Getting Started Programming Essentials for Beginners Table 1-l. Command Table Command Parameters Parameter state Reading the Command Note the three columns in the command table labeled Command, Parameters, Table and parameter Type. Commands closest to the root level are at the top of the table.
Page 46: More About Commands
Getting Started Programming Essentials for Beginners More About Commands Query and Event Because you can query any value that you can set, the query form of each Commands command is not shown explicitly in the command tables. For example, the presence of the sweeper : SWEep : DWELl command implies that a : SWEep : DUELl? also exists.
Page 47: Program Message Examples
Getting Started Programming Essentials for Beginners Program Message Examples The following parts of the sweeper SCPI command set will be used to demonstrate how to create complete SCPI program messages: : FRF.Quency : POWER Example 1 The command is correct and will not cause errors. It is equivalent to sending: Example 2 This command results in a command error.
Page 48: Example 3
Getting Started Programming Essentials for Beginners Example 3 This command results in a command error. The F’REQ:CW portion of the command is missing a leading colon. The path level is dropped at each colon until it is in the F’REQ:h3UI.T subsystem. So when the F’REQ:CW command is sent, it causes confusion because no such node occurs in the reset to the root.
Page 49: Parameter Types
Getting Started Programming Essentials for Beginners Parameter Types As you saw m the example command table for SWEep, there are several types of parameters. The parameter type indicates what kind of values are valid instrument settings. The most commonly used parameter types are numeric, extended numeric, discrete, and Boolean.
Page 50: Extended Numeric Parameters
Getting Staned Programming Essentials for Beginners Extended Numeric Most measurement related subsystems use IZZWKJ& numeric parameters to Parameters specify physical quantities. Extended numeric parameters accept all numeric parameter values and other special values as well. AU extended numeric parameters accept MAXimum and MINimum as values. Other special values, such as UP and DOWN may be available as documented in the instrument’s command summary.
Page 51: Discrete Parameters
Getting Started Programming Essentials for Beginners Discrete Parameters Use discrete parameters to program settings that have a finite number of values. Discrete parameters use mnemonics represent each valid setting. They have a long and a short form, like command mnemonics. You can use mixed upper and lower case letters for discrete parameters.
Page 52: Reading Instrument Errors
Getting Staned Programming Essentials for Beginners Reading Instrument Errors When debugging a program, you may want to know if an instrument error has occurred. Some instruments can display error messages on their front panels. If your instrument cannot do this, you can put the following code segment in your program to read and display error messages.
Page 53: Example Program
Essentials for Beginners Exarnple Programs The following is an example program using SCPI compatible instruments. The example is written in HP BASIC. This example is a stimulus and response application. It uses a source and counter to test a voltage controlled oscillator.
Page 54 Getting Started Programming Essentials for Beginners 100 ! CLEAR @Stimulus CLEAR @Response 130 ! OUTPUT QStimulus;"*RST" OUTPUT OResponse;"*RST" 160 ! PRINT "Voltage Controlled Oscillator Test" PRINT 190 ! PRINT "Source Used . .." OUTPUT OStimulus;"*IDN?" ENTER QStimulus;Id$ PRINT Id$ PRINT 250 ! PRINT "Counter Used .
Page 55: Program Comments
ENTERs, you can overwrite data in the instrument Output Queue and generate instrument errors. 470 to 480: Disconnect output terminals of the instruments from the unit under test, and end the program. All HP BASIC programs must have END as the last statement of the main program.
Page 56: Details Of Commands And Responses
Details of Commands and Responses This subsection describes the syntax of SCPI commands and responses. It provides many examples of the data types used for conkand parameters and response data. The following topics are explained: Program Message These paragraphs explain how to properly construct the messages you send from the computer to Syntax instruments.
Page 57: Program Message Syntax
<new line> <-END> as the program message terminator. The word <-END> means that EOI is asserted on the HP-D3 interface at the same time the preceding data byte is sent. Most progmmming languages send these terminators automatically. For example, if you use the HP BASIC OUTPUT statement, <new line> is automatically sent after your last data byte.
Page 58: Scpi Subsystem Command Syntax
Getting Started Programming Details of Commands and Responses SCPI Subsystem Command Syntax NOTE Figure I-7. SCPI Simplified Subsystem Command Syntax As Figure l-7 shows, there must be a <space> between the last command mnemonic and the first parameter in a subsystem command. This is one of the few places in SCPI where <space>...
Page 59: Common Command Syntax
Getting Started Programming Details of Commands and Responses Common Command Syntax mnemonic SP - w h i t e s p a c e , A S C I I c h a r a c t e r s 0,0 t o 9,0 a n d 11,0 t o 32,0 Figure 1-8.
Page 60: Response Message Syntax
Getting Started Programming Details of Commands and Responses Response Message Syntax Figure l-9. Simplified Response Message Syntax Response messages can contain both commas and semicolons as separators. When a single query command returns multiple values, a comma separates each data item. When multiple queries are sent in the same message, the groups of data items corresponding to each query are separated by a semicolon.
Page 61: Scpi Data Types
Getting Started Programming Details of Commands and Responses SCPI Data Types These paragraphs explain the data types available for parameters and response data. They list the types available and present examples for each type. SCPI defines different data formats for use in program messages and response messages.
Page 62: Parameter Types
Getting Started Programming Details of Commands and Responses dictionary generally contains information about data types for individual commands. The following paragraphs explain each parameter and response data type in more detail. Parameter Types Numeric Parameters Numeric parameters are used in both subsystem commands and common commands.
Page 63: Extended Numeric Parameters
Getting Started Programming Details of Commands and Responses Extended Numeric Most measurement related subsystems use extended numeric parameters to specify physical quantities. Ez.Zen&& numeric parameters accept all numeric Parameters parameter values and other special values as well. All extended numeric parameters accept MAX&m and MINimum as values.
Page 64: Discrete Parameters
Getting Programming Started Details of Commands and Responses Discrete Parameters Use discrete pcz?-ameters to program settings that have a finite number of values. Discrete parameters use mnemonics to represent each valid setting. They have a long and a short form, just like command mnemonics. You can used mixed upper and lower case letters for discrete parameters.
Page 65: Response Data Types
Getting Started Programming Details of Commands and Responses Response Data Types Real Response Data A large portion of all measurement data are formatted as real response data. Real response data are decimal numbers in either lixed decimal notation or scientific notation. In general, you do not need to worry about the rules for formatting real data, or whether fixed decimal or scientific notation is used.
Page 66: Discrete Response Data
Getting Programming Started Details of Commands and Responses Discrete Response Data mnemonic, in all upper case letters. Examples of discrete response data: level intemullly level using an t?te@valpozve?-mder * String Response Data string parameters. The main difference is that string response data use only double quotes as delimiters, rather than single quotes.
Page 67: Programming Typical Measurements
“Program Comments” paragraphs to follow the programmed activity. The HP-E3 select code is assumed to be preset to 7. All example programs in this section expect the sweeper’s HP-lB address to be decimal 19.
Page 68 Getting Started Programming Programming Typical Measurements Use of the Command T&bles In ‘lkble 1-3, notice that a new column titled “Allowed Values” has been added to the command table. This column lists the specific values or range of values allowed for each parameter. A vertical bar (I) separates values in a list ‘from which you must choose one value.
Page 69 Getting Started Programming Programming Typical Measurements Table l-3. Sample Sweeper Commands Command Parameter Type Allowed Values Parameters discrete to Cal extended numeric Up to 801 freq- correction pairs center freq extended numeric specified freq range or MAXimum~MlNimum~UP~DOWN CW freq extended numeric specified freq range or MAXimumIMlNimumIUPIOOWN coupled to...
Page 70 Getting Started Programming Programming Typical Measurements Table l-3. Sample Sweeper Commands (continued) Allowed lfalues Command Parameters Parameter Type extended numeric Boolean output level extended numeric RF on/off Boolean discrete extended numeric sweep time Boolean time switch extended numeric time...
Page 71: Hp-Ib Check, Example Program 1
HP-IB Check, Example Program 1 This lkst program verify that the HP-I5 connections and interface are functional. Connect a controller to the sweeper via an HP-IB cable. Clear and reset the controller and type in the following program: ABORT 7 LOCAL Source CLEAR Source REMOTE Source PRINT “The source should now be in REMOTE.
Page 72: Local Lockout Demonstration, Example Program 2
Getting Programming Started Programming Typical Measurements Local Lockout Demonstration, Example Program 2 When the sweeperis inREMOTEmode, all the frontpanelkeys are disabled except the LOCAL key But, when the LOClAL LOCKOUT commandis set on thebus, eventheL0CALkeyi.s disabled. TheLOCAL command, instruments to frontpanelcontrol. Continue example program 1.
Page 73: Program Comments
Note that the sweeper @ZiT) key produces the same resuh as programming LOCAL 719 or LOCAL 7. Be careful because the LOCAL 7 command places all instruments on the HP-IB in the local state as opposed to just the sweeper.
Page 74: Setting Up A Typical Sweep, Example Program 3
Getting Staned Programming Programming Typical Measurements Setting Up A Typical Sweep, Example Program 3 frequency range, sweep time, power level, and marker frequencies for a test measurement. This program sets up the sweeper for a general purpose situation. The instrument is the same as in program 1. Clear and reset the controller and type in the following program: LOCAL 7 CLEAR Source...
Page 75: Program Comments
Assign the source’s HP-IB address to a variable. 20 to 50: Abort any HP-IR activity and initialize the HP-IB interface. Set the source to its initial state for programming. The *RST state is not the same as the PRESET state. For complete details of the instrument state at *RST, see “SCPI Command...
Page 76: Queries, Example Program 4
PRINT "Minimum source CW frequency is : ";A/I.E+6;"MHz" OUTPUT Source;*'FREQ:START?;STOP?" ENTER Source;X,Y PRINT "Swept frequency limits :" PRINT " Start ";X/I.E+6;"MHz" PRINT ” Stop “;Y/I.E+6;“MHz” Run the program. Assign the source’s HP-lB address to a variable. Program Comments Abort any HP-IB activity and initialize the HP-IB interface.
Page 77 Getting Stat-ted Programming Programming Typical Measurements Clear the computer’s display. Set the source to its initial state for programming. Setup the source power level using a compound message. Query the value of the source’s CW frequency. 100: Enter the query response into the variable ‘F’. The response always is returned in fundamental units, Hz in the case of frequency.
Page 78: Saving And Recalling States, Example Program 5
Getting Started Programming Programming Typical Measurements Saving and Recalling States, Example Program 5 When atypical sweep, like example program 3, is setup, the complete front panel state maybe saved for later use in non-volatile memories called registers 1 through 9. This canbe done remotely as apart ofaprogram. Clear and reset the controller and type in the following program: ABORT 7 LOCAL 7...
Page 79: Program Comments
1 0 : Assign the source’s HP-IB address to a variable. 20 to 50: Abort any HP-IB activity and initialize the HP-IB interface. Clear the computer’s display. Setup the source for a sweeping state. Note the combination of several commands into a single message. This single line is equivalent to the following lines : OUTPUT Source ;...
Page 80: Looping And Synchronization, Example Program 6
Getting Started Programming Programming Typical Measurements Looping and Synchronization, Example Program 6 Clear andresetthe controllerandtype in the following program: ABORT 7 LOCAL 7 CLEAR Source REMOTE Source OUTPUT Source;"*RST" OUTPUT Source;"POWER:LEVEL -1 DBM; STATE ON" OUTPUT Source;'WEEP:TIME 1" OUTPUT Source;“*OPC?" 120 ENTER Source;X 130 REPEAT DISP "Enter number of sweeps to take :...
Page 81: Program Comments
Programming Typical Measurements Program Comments 1 0 : Assign the source’s HP-IB address to a variable. Abort any HP-IB activity and initialize the HP-IB interface. 20 to 50: Clear the computer’s display. Set the source to its initial state for programming.
Page 82: Using The *Wa1 Command, Example Program 7
Getting Started Programming Programming Typical Measurements Using the *WA1 Command, Example Program 7 The following example illustrates the use of the *WAI command to cause the sweeper to perform a synchronous sweep. ABORT 7 LOCAL 7 CLEAR Source REMOTE Source OUTPUT Source;...
Page 83 Send another *WM to the source. Although the *WAT command causes EXECUTION of commands to held off, it has no effect on the transfer of commands over the HP-II% The commands continue to be accepted by the source and are buffered until they can be executed.
Page 84: Using The User Flatness Correction Commands
Using the User Flatness Correction Commands, Example Program 8 The following program interrogates the sweeper and an HP 437B power meter for frequency and power information respectively. The sweeper is programmed to sweep from 2 to 20 GHz, with frequency-correction pairs every 100 MHz and 0 dBm leveled output power.
Page 85 Getting Started Programming Programming Typical Measurements IF Error-flag THEN BEEP CLEAR SCREEN PRINT "ERROR:METER DID NOT COMPLETE ZEROING OPERATION!" ELSE FOR I=1 TO N NEXT I OUTPUT OSource;"CORR:FLAT ";B$ ! OUTPUT QSource;"POW:STAT ON" OUTPUT @Source;"CAL:PMET:FLAT:INIT? USER" ENTER OSource;Freq WHILE Freq>O OUTPUT QSource;"CAL:PMET:FLAT:NEXT? ";VAL$(Power);"DBM"...
Page 86 Getting Started Programming Programming Typical Measurements WHILE Zeroing AND NOT Finished Attempts=Attempts+l IF Attrmpts>Max-attempts THEN Zeroing=0 IF BIT(Meter-stat,l) THEN Finished=1 WAIT 1 END WHILE OUTPUT QSource;"Pow:stat on" IF NOT Zeroing THEN ELSE END IF DEF FNRead-meter(QMeter,Freq) OUTPUT @Meter;"SEOEN" OUTPUT OMeter;"FR"&Freq$&"GZ"i OUTPUT QMeter"'TR2"...
Page 87 Getting Started Programming Programming Typical Measurements 1010 UNTIL Flips>=3 1020 1030 RETURN Power 1040 1050 FNEND...
Page 88: Programming The Status System
Register Model structured in SCPI instruments. It also contains an example of how bits in the various registers change with different input conditions. These paragraphs describe how the status system works in HP 83750 the HP 83750 Series synthesized sweepers. Series Status Register Model 1-68...
Page 89: General Status Register Model
Getting Started Programming Programming the Status System General Status Register Model The generalized status register model shown in Figure l-10 is the building block of the SCPI status system. This model consists of a condition register, a transition kilter, an event register and an enable register. A of these registers is called a status group.
Page 90: Transition Filter
Getting Staned Programming Programming the Status System Transition Filter The b-an.sitionfZtw specifies which types of bit state changes in the condition register will set corresponding bits in the event register. Transition filter bits may be set for positive transitions (RR), negative transitions (NTR), or both.
Page 91: An Example Sequence
Getting Started Programming Programming the Status System An Example Sequence 1-11 illustrates the response of a single bit position in a typical status group for various settings. The changing state of the condition in question is shown at the bottom of the ligure. A small binary table shows the state of the chosen bit in each status register at the selected times Tl to T5.
Page 92: Hp 83750 Series Status Register Model
The synthesized sweeper status register system consists of the Status Byte group and three other status groups that provide input to the Status Byte group. The hierarchy of the HP 83750 status register system is shown in Figure 1-12. The following paragraphs explain the information that is provided by each status group.
Page 93 Getting Started Programming Programming the Status System IEEE 488.2 (to which the Synthesize Sweeper conforms) further defined the Status Byte bit positions, specifically bits 4 and 5. In addition, it defines more commands that ahow the user to access the Status Byte and associated data structures.
Page 94: The Standard Event Status Group
Getting Started Programming Programming the Status System The Standard Event Status The Standard Event Status group is used to determine the specific event that Status Group set bit 5 in the Status Byte. The Standard Event group consists of the Standard Event Status register (an Event register) and the Standard Event Status Enable register.
Page 95: The Standard Operation Status Group
Getting Started Programming Programming the Status System The Standard Operation The Standard Operation status group is used to determine the specific Status Group condition that set bit 7 in the Status Byte. The Standard Operation status group consists of the Operation Condition register, Operation Negative Transition register, Operation Positive Transition register, Operation Event register, and Operation Event Enable register.
Page 96: The Questionable Data Status Group
Getting Started Programming Programming the Status System The Questionable Data The Questionable Data status group is used to determine the specific Status Group condition that set bit 3 in the Status Byte. The Questionable Data status group consists of the Questionable Condition register, Questionable Negative Transition register, Questionable Positive Transition register, Questionable Event register, and Questionable Event Enable register.
Page 97 Getting Started Programming Programming the Status System Status Register System In the following example, the Status Register System is programmed to set Programming Example bit 6 of the status byte (the SRQ bit) high after the synthesized sweeper hardware has settled. Bit 6 is monitored and, unce it is set high, the controller prints “HARDWARE IS SETTLED”...
Page 98 Getting Started Programming Programming the Status System S T A N D A R D E V E N T S T A T U S G R O U P E V E N T R E G I S T ENABLE REGIST STATUS BYTE REG I ST...
Page 99 Getting Started Programming Programming the Status System S T A N D A R D O P E R A T I O N S T A T U S G R O U P N E G I rl rl rl rl rl EVENT REGIST ENABLE REGIST STAT :OPER: ENAS...
Page 100: Programming The Trigger System
Programming the Trigger System This section discusses a trigger model used in SCPI instruments. Trigger system topics are explained in the following paragraphs: Generalized Trigger This paragraph explains the structure and components Model of the trigger model used in SCPI instruments. Trigger Command These paragraphs provide condensed definitions for the Definitions...
Page 101 Getting Started Programming Programming the Trigger System Idle E X T >- B U S + Initiate Figure I-13. The TRIG Trigger Configuration 1-81...
Page 102: Description Of Triggering In Sweepers
Getting Started Programming Programming the Trigger System Description of Triggering in Sweepers The sweepers follow the SCPI model of triggering. It is a layered model with the structure shown in F’igure 1-14. I D L E S T A T E 4 S W E E P I N I T I A T E D WAITING FOR THE T R I G G E R S I G N A L...
Page 103: Advanced Trigger Configurations
This is the external trigger input jack. A positive transition on this jack constitutes a TRUE signal. This signal is the HP-IB <get> (Group Execute Trigger) message or a *TRG command. When a TRUE signal is found, the sweep is actually started. The act of producing the sweep in some cases involves the use of trigger signals.
Page 104: Trigger Keyword Definitions
Sending *RST sets SOURce to IMMediate. The most commonly used sources are: The event detector is satisfied by either Group Execute Trigger (<GET>) or a *TRG command. <GET> is a low level in HP BASIC. An external signal connector is selected as the source. events are Qualified generated automatically.
Page 105: Related Documents
Hewlett-Packard Company 1987. This HP BASIC manual contains a good non-technical description of the HP-IB (IEEE 488.1) interface in chapter 12, “The HP-IB Interface. n Subsequent revisions of HP BASIC may use a slightly different title for this manual or...
Page 106 Getting Staned Programming Related Documents chapter. This manual is the best reference on instrument I/O for HP BASIC programmers. Company, 1987 This book provides a thorough overview of HP-U3 basics for the HP-U3 system designer, programmer, or user. To obtain a copy of either of these documents, contact the Hewlett-Packard representative listed in...
Page 107: Programming Commands
Programming Commands...
Page 108 Programming Commands This chapter contains information on all the programming commands used by the sweeper.
Page 109: Command Syntax
Command Syntax Following the heading for each progr amming command entry is a syntax statement showing the proper syntax for the command. An example syntax statement is shown below: Syntax statements read from left to right. In the above example, the of the statement with no separating space.
Page 110: Ieee 488.2 Common Commands
IEEE 488.2 Common Commands Common commands are generally not measurement related, but are used to manage macros, status registers, synchronization, and data storage. All common commands begin with an asterisk. The common commands are defined by IEEE 488.2 *CLS (Clear Status Command) Clear the status byte, the Data Questionable Event Register, the Standard Event Status Register, the Standard Operation Status register and any other registers that are summarized in the Status Byte.
Page 111: Emc (Enable Macros Command)
Programming Commands IEEE 488.2 Common Commands * EMC (Enable Macros Command) Allows the programmer to query whether the macros are enabled. A return value of 0 indicates that the macros are disabled. A return value of 1 indicates that the macros axe enabled. Sets and queries the Standard Event Status Enable Register.
Page 112: Gmc? (Get Macro Contents Query)
Returns the current definition of the macro. * IDN? (Identification Query) Outputs an identifying string to the HP-IB. The response for the sweeper will be “HEWLETT-PACKARD,83750A,2415AOOl23,REV A.O1.OO” where the actual model number, serial number and firmware revision will be substituted *LMC? (List Macro Query) Returns the currently defined macro labels.
Page 113: Opc (Operation Complete Command)
Programming Commands IEEE 488.2 Common Commands *OPC (Operation Complete Command) Operation complete command. The sweeper will set bit 0 in the Standard Event Status Register when all pending operations have finished. In CW mode, this is deEned as RF settled. In an analog swept mode, this is defined as the beginning of a new sweep.
Page 114: Pmc (Purge Macros Command)
Programming Commands IEEE 488.2 Common Commands *PMC (Purge Macros Command) Deletes all macros that have been previously deEned using the *DMC command. *PSC (Power-On Status Clear Command) This command controls the automatic power-on clearing of the Service Request Enable Register and the Standard Event Status Enable Register. Setting the power-on-clear flag TRUE causes the registers to be cleared at power-on, thus preventing the device from requesting service.
Page 115: Rcl (Recall Command)
Programming Commands IEEE 488.2 Common Commands *RCL (Recall Command) The instrument state is recalled from the specified memory register. Range is 1 through 9. *RMC (Remove Macro Command) Deletes a single macro. The instrument is set to a pre-detied condition. These conditions are explained under each command.
Page 116: Sre (Service Request Enable Command)
Programming Commands IEEE 488.2 Common Commands *SRE (Service Request Enable Command) Query Syntax Sets and queries the value of the Service Request Enable Register. *STB? (Read Status Byte Query) Queries the status byte. This is non-destructive. Performs the same function as the Group Execute Trigger command defined by IEEE 488.1.
Page 117: Tst? (Self-Test Query)
Programming Commands IEEE 488.2 Common Commands *TST? (Self-Test Query) A full self-test is performed , without data logging or looping, and returns one of the following error codes : 0 = Passed (no tests failed and at least one test passed) 1 = Failed (one or more tests failed) 2 = Skipped (alI tests are skipped or can’t do - doubtful ) 3 = Can’t Do (all tests are can’t do - highly unlikely)
Page 118: Subsystem Commands
Subsystem Commands Subsystem commands include alI measurement functions and some general purpose functions. Subsystem commands are distinguished by the colon used between keywords, as in POWer:SLOPe. Each subsystem is a set of commands that roughly corresponds to a functional block inside the instrument.
Page 119: Am:source
Programming Commands Subsystem Commands AM:SOURce AM : SOURce { EXTernal } AM : SOURce? This sets and queries the AM modulation source. This is always EX’lbnal. 2 - 1 3...
Page 120: Calibration Subsystem
Calibration Subsystem CALibration:PEAKing CALibration:PEAKing[:EXECute] Peaking is used to obtain the maximum available power and spectral purity; and the best pulse and FM envelopes at a given frequency. for a CW frequency. ln general - 1 is returned if there is a problem. CALibration:PMETer:FLATness:INITiate? CALibration:PMETer:FLATness:INITiate? USER Initiates the user flatness calibration.
Page 121: Calibration:pmeter:flatness:next
Programming Commands Calibration Subsystem CALibration:PMETer:FLATness:NEXT? <num>[lvl suffix] The parameter is the measured power that is currently being produced by the sweeper. The user is to supply this parameter after measuring the power using his/her own power meter. The query response will be issued after the sweeper has processed the supplied parameter and has settled on the next point to be measured.
Page 122 Programming Commands Calibration Subsystem CALibration:SECurity:CODE CALibration:SECurity:CODE COldPasswd> <NewPasswd> Changes the current password to a new one. The password must be five numerical digits and may not start with zero (0). Alphabetic and special characters are allowed. The command is sent once; you do not verify it by sending the command a second time.
Page 123: Correction Subsystem
Correction Subsystem CORRection:FLATness:FREQ suffix]. . .) Query Syntax Sets and queries an array of up to frequency-correction elements. This correction information will be used to create a correction array that will be added to the internal calibration array. The array can be of arbitrary spacing. At every instantaneous frequency linear interpolation is used to determine an amplitude correction.
Page 124: Correction:flatness:ampl
Programming Commands Correction Subsystem CORRection:FLATness:AMPL CORRection:FLATness:AMPL? Sets and queries an array of up to 801 amplitude correction elements. This correction information will be used to create a correction array that will be added to the internal calibration array. This array is used in conjunction with CORR:FLAT:FREQ on a one to one basis.
Page 125: Correction[:State]
Programming Commands Correction Subsystem Query Syntax CORRection[:STATe]? Sets and queries the switch on the users ALC correction system. This switch prevents the User Correction data from being added to the internal *RST value is OFF’. CORRection:VOLTs:SCALe CORRection:VOLTs:SCALe? Sets and queries the rear panel “V/GHZ” scaling factor. 2-19...
Page 126: Query Syntax
Programming Commands Correction Subsystem CORRection:VOLTs:OFFSet CORRection:VOLTs:OFFSet? Sets and queries the rear panel “V/GHZ” offset factor. 2-20...
Page 127: Diagnostic Subsystem
Diagnostic Subsystem This returns a small string (that is, < 1 kbytes) of device specilic characters that, when sent back to the sweeper, will restore the instrument state with the exception of user ALC arrays. User Ale arrays will be zeroed out. Note that this implies that the command to redigest the string is included in the query response to DIAG:LRNS? Since we use SYST:SET <huge data block>...
Page 128: Diagnostic:test:fulltest:report
Programming Commands Diagnostic Subsystem DIAGnostic:TEST:FULLtest:REPort? This query command will return the status of the fulltest or failure data on the failed test most likely to have caused additional failures. Status = NOTRUN PASSED Fail Data Format = <name> <status> <minValue> <actualData> <maxValue> N O T E If any individual test is not run then will be returned regardless of other failures.
Page 129: Display Subsystem
Display Subsystem Query Syntax DISPlay[:STATe]? Sets and queries the display ON/OFF switch. Once State is set OFF, only an *RST or SYST:PRES can set it back to ON. *RST value is 1. 2-23...
Page 130: Fm Subsystem
FM Subsystem FM:COUPling Query Syntax Sets and queries the FM input coupling mode. *RST value is set to DC. FM: STATe FM :STATe ONlOFFlllO FM : STATe? Sets and queries the FM state. This command will turn frequency modulation on or off. 2-24...
Page 131: Fm:sensitivity
Programming Commands FM Subsystem FM: SENSitivity FM:SENSitivity <-20)-6> <MHz/V> FM:SENSitivity? Sets and queries the FM Sensitivity. This allows only two different settings: either -20 MHzN or -6 MHz/V. The unit will return in term of Hz/V which also is the SPCI default unit. *RST value is set to -20 MHz/V.
Page 132: Query Syntax
Frequency Subsystem Sets and queries the center frequency. Any two frequency setting headers (STARt, STOP, CENT&-, or SPAN) may be sent in a single message and the resulting sweep will be what was requested. The order in the message will not make any difference in the tial result. When a message has been completed, coupling equations will be used to fix the unset parameters to the correct values.
Page 133 Programming Commands Frequency Subsystem Example 1 Present state: START=5 GHZ STOP=6 GHZ) an error results since stop was bumped the jinal sweep is OK though (10 to 12) Example 2 Present state: START=5 GHZ STOP=6 GHZ) NO error generated, START unchanged still no error Present state: START=5 GHZ STOP=6 GHZ) Example 3...
Page 134 Programming Commands Frequency Subsystem Sets and queries the CW frequency. This does not change the sweptkw mode switch. *RST value is (MAX + MIN)/2 See FREQ:CENTER for more information. FREQuency[:CW]:AUTO and FREQuency[:FIXed]:AUTO Query Syntax Couples the CW frequency to the center frequency. Explicitly setting a value for FREQ:CW set FREQ: CW AUTO to OFF.
Page 135 Programming Commands Frequency Subsystem suffix] Sets and queries the MANual frequency. This controls the output frequency in swept manual mode (FREQ:MODE SWJ3ep and SWEEP:MODE MANUAL). The limits are START and STOP *RST value is the same as FREQ:CENTER. See FREQ:CENTER for more information.
Page 136 Programming Commands Frequency Subsystem FREQuency:MODE Sets and queries the switch that selects either swept, CW or swept CW operation. The output frequency is controlled by FREQ:CW. The output frequency is controlled by the STARTSTOP, CENTER, SPAN, MAN commands (and the SWE: subsystem). swcw Sweep generator is active, but only the value of FREQ:CW is used.
Page 137 Programming Commands Frequency Subsystem FREQuency:MULTiplier <num>lMAXimumlMINimum FREQuency:MULTiplier? [MAXimumlMINimum] Sets and queries the frequency multiplier. <num> will be rounded to the nearest integer. This function changes mapping of frequency parameters on input to and output from the sweeper. Changing this does not affect the output frequency of the instrument, only the displayed parameters and query responses.
Page 138: Query Syntax
Programming Commands Frequency Subsystem FREQuency:OFFSet FREQuency:OFFSet <num>lMAXimumlMINimum FREQuency:OFFSet? [MAXimumIMINimum] Sets and queries the frequency offset. This function changes mapping of frequency parameters on input to and output from the sweeper. Changing this does not affect the output frequency of the instrument, only the displayed parameters and query responses.
Page 139 Programming Commands Frequency Subsystem FREQuency:SPAN? [MAXimumlMINimum] Sets and queries the frequency span. See F'REQ:CENTER for more information. FREQuency:STARt <num>[freq suffix] lMAXimumlMINilUPlDOWN FREQuency:STARt? [MAXimumlMINimum] Sets andqueriesthe START Frequency. See FREQ:CENTER formore information. 2-33...
Page 140 Programming Commands Frequency Subsystem FREQuency:STEP[:INCRement] This sets and queries the frequency step size to be used for any node in the FREQ: tree that allows UP and DOWN as parameters. *RST setting is automatically calculated from SPAN. FREQuency:STOP FREQuency:STOP <num>[freq suffix]lMAXimumlMINimum~UPlDOWN FREQuency:STOP? [MAXimumIMINimum] Sets and queries the STOP Frequency.
Page 141 Triggering in the Sweeper Figure 2-l. Instrument Trigger Model 2-35...
Page 142 Programming Commands Triggering in the Sweeper The process of sweeping involves all three of these states. The IDLE state is where it all begins. The IDLE state is left when the sweep becomes initiated. This can happen on a continuous basis (lNIT:CONT ON) or on demand (INIT:CONT OFF).
Page 143 Programming Commands Triggering in the Sweeper INITiate:CONTinuous Query Syntax INITiate:CONTinuous? Sets and queries the state of the CONTINUOUS initiation switch. This is more commonly known as SINGLE or CONTINUOUS sweep, but this is how all triggered SCPI instruments will be initiated. This does not affect a sweep in progress.
Page 144 Marker Subsystem Usage of the <n> in MARKER headers A single digit may be appended to any of the MARKER headers, as shown in the commands. This specifies which of the 10 markers (0 to 9) is being altered. ln some cases, the function is global to all 10 markers and is not really something that is an attribute of a single marker, such as amplitude markers.
Page 145 Programming Commands Marker Subsystem MARKer[n]:AOFF This turns all the markers to OFF at once. While [n] may be used, there is really only a single switch to turn all the markers off. This also turns marker delta mode to OFF if it was ON. This also turns M l->M2 SWEEP mode to OFF if it was ON.
Page 146: Frequency[:Cw[:Fixed]
Programming Commands Marker Subsystem MARKer[n]:FREQuency MARKer[n]:FREQuency Cnum>[freq suffix]lMAXimumiMINimum MARKer[n]:FREQuency? [MAXimumIMINimum] Sets and queries the specified marker frequency (marker number one is the default if [n] is not spemed). The value is interpreted differently based on the value of MARKer[n]:MODE. MARKer[n] :MODE How the frequency of the marker is determined.
Page 147 Programming Commands Marker Subsystem MARKer[n]:MODE MARKer[n]:MODE FREQuencylDELTa This sets and queries the mode of the specified marker. While [n] may be used, there is really only a single switch to set all the markers to either FREQuency mode or to DELTa mode. Setting one marker to DEL% turns all other MARKer[n]:MODEs to DEL% and the same for setting one marker to FREQuency mode.
Page 148 Programming Commands Marker Subsystem MARKer[n]:REFerence MARKer[n]:REFerence MARKer[n]:REFerence? This sets and queries which marker is the reference marker for use in the for all the markers. MARKerl:REFerence 5; and MARKer:REFerence <n> is turned on and cannot be turned off if the marker’s current mode is DELZa mode.
Page 149 Programming Commands Marker Subsystem MARKer[n] [:STATe] This sets and queries the state of the spetied marker. Marker number one is the defaulted if [n] is not specified. The spetied Marker cannot be turned off if it is the DELTA Reference Marker and Marker DELTA Mode is on.
Page 150 Memory Subsystem MEMory:RAM:INITialize[:ALL] This command clears and initializes the entire content of RAM to all zeros. This clears all of the save/recall registers. The number of times that memory is cleared and the RAMS are set to zeros is set by SYSTem:SECurity:COUNt conditions.
Page 151 Output Subsystem Sets and queries the output state, also known as RF ON/OFF *RST value is OFF. OUTPut:IMPedance? Queries the output impedance: nominally 50 ohms. This is never set able, but only conligurable from the calibration constants. 2-45...
Page 152 Power Subsystem Any place where dBm is accepted as a sufhx, any level suflix will also be accepted. ln the absence of a suflix, the units will be assumed to be determined by the setting of UNIT:POW. POWer:ALC:CFACtor POWer:ALC:CFACtor? [MINimumlMAXimum] Sets and queries the coupling factor to be used when POWer:ALC[:SOURce] is set to DIODe or PMETer.
Page 153: Query Syntax
Programming Commands Power Subsystem POWer:ALC[:STATe] POWer:ALC[:STATe]? Sets and queries the state switch of the ALC. The positions are : normal ALC operation open loop ALC mode When ON, the POWER can be programmed in fundamental units as selected by the UNIT:POWer command. When OFF, the POWER is no longer calibrated in absolute units and is set in units of dR of arbitrary modulator setting.
Page 154 Programming Commands Power Subsystem POWer:ATTenuation:AUTO ONlOFFlllO Query Syntax POWer:ATTenuation:AUTO? Sets and queries the state of the RF attenuator coupling switch. Programming a specified attenuation sets POWer:AT%nuation:AUTO OFF. insures that the amplitude level of the ALC is kept within optimal the attenuator setting is set to the value of POW:ATT and left there.
Page 155 Programming Commands Power Subsystem POWer:CENTer POWer:CENTer <num> [Iv1 suffix]lMAXimumlMINimum[UF’lDOWN POWer:CENTer? [MAXimumlMINimum] Sets and queries the center power for power sweep. Default units (and units for query response) are determined by UNIT:POWer. The coupling equations for power sweep are exactly analogous to those for FREQ sweep.
Page 156 Programming Commands Power Subsystem POWer[:LEVel] suffix] IMAXimumlMINimum~UPlDOWN Sets and queries the output level. Default units (and units for query response) are determined by UNIT:POWer. MAXimum and MINimum levels refer to the leveling mode at the time the command is sent. For instance: will have different effects than *RST value is 0 dBm.
Page 157 Programming Commands Power Subsystem POWer:OFFSet Sets and queries the power offset. This function changes mapping of absolute power parameters on input to and output from the sweeper. Changing this does not affect the output power of the instrument, only the displayed parameters and query responses.
Page 158 Programming Commands Power Subsystem POWer:SLOPe Query Syntax Sets and queries the RF slope setting (dB per Hz). FREQ:MODE Rotates around 0 Hz. *RST value is 0. Sets and queries the power slope state. *RST value is 0. 2-52...
Page 159 Programming Commands Power Subsystem POWer:SPAN The coupling equations for power sweep are exactly analogous to those for FREQ sweep. Power sweep is allowed to be negative though, unlike frequency sweeps. See FREQ:CENT for a description. See POWer:LEVel for an explanation of MAXIMIN. *RST value is 0.
Page 160 Programming Commands Power Subsystem Sets and queries the output power ONJOFF state. *RST value is OFF. POWer:STEP[:INCRement] POWer:STEP[:INCRement]? [MAXimumIMINimum] This command sets and queries the power step size to be used for any node in the POWer: tree that allows UP and DOWN as parameters. *RST setting is 1.0 d.B.
Page 161 Programming Commands Power Subsystem POWer:STOP Set and queries the ending power for a power sweep. Default units (and units for query response) are determined by UNIT:POWer. The coupling equations for power sweep are exactly analogous to those for FREQ sweep. Power sweep is allowed to be negative though, unlike Freq sweeps.
Page 162 Pulse Subsystem Since FREQuency and PERiod are inversely related, if both are sent in the same message, only the last one will be applied. lf WlDth and either without error if the resulting pulse is possible. PULSe:PERiod PULSe:PERiod <num>[time suffix]IMAXimumIMINimum PULSe:PERiod? [MAXimumlMINimum] Sets and queries the period of the internal pulse generator.
Page 163 Programming Commands Pulse Subsystem PULSe:FREQuency Query Syntax PULSe:FREQuency? [MAXimumlMINimum] Sets and queries the frequency of the internal pulse generator. This is always the reciprocal of the period. *RST value is 500 KHz. PULSe:WIDTh <num>[time suffix]lMAXimumlMINimum PULSe:WIDTh? [MAXimumlMINimum] Sets and queries the width of the internal pulse generator. *RST value is 1 ps.
Page 164 Programming Commands Pulse Subsystem Sets and queries the source for the pulse modulation control signal. internal pulse generator 27.777 kHz square wave. This is used with scaler analyzers. 1.0 KHz square wave. *RST value is IWkmal. PULM:STATe ONlOFFlllO PULM:STATe? Sets and queries the state of pulse modulation. *RST value is OFF’.
Page 165 Programming Commands Pulse Subsystem Sets and queries the reference oscillator selection switch. The command to set the switch will cause ROSC:SOUFkAUTO OFF to be done also. *RST value is automatically determined. Set and queries the automatic reference selection switch. *RST value is 1. 2 - 5 9...
Page 166 Status Subsystem Queries the Standard Operation Condition register. Sets and queries the Standard Operation enable register. The STATus:PRESet value is 0. *RST does not affect this register. STATus:OPERation[:EVENt]? Queries the Standard Operation Event Register. This is a destructive read. 2 - 6 0...
Page 167 Programming Commands Status Subsystem STATus:OPERation:NTRansition STATus:OPERation:NTRansition <mm> STATus:OPERation:NTRansition? Sets and queries the Standard Operation Negative transition Clter. The STATus:PRESet value is 0. *RST has no effect. Query Syntax STATus:OPERation:PTRansition? Sets and queries the Standard Operation positive transition flter. After STATus:PRESet, all used bits are set to 1’s. *RST has no effect.
Page 168 Programming Commands Status Subsystem STATUS:PRESet This command presets the following enable and transition registers: is set to all 0’s. is set to all 0’s. all bits that are used are set to 1’s. Unused bits remain 0’s. STATus:QUEStionable:CONDition? Queries the Data Questionable Condition Register. STATus:QUEStionable:ENABle? Query Syntax Sets and queries the Data Questionable SRQ ENABle register.
Page 169 Programming Commands Status Subsystem STATus:QUEStionable[:EVENt]? Queries the Data Questionable Event Register. This is a destructive read. STATus:QUEStionable:NTRansition STATus:QUEStionable:NTRansition STATus:QUEStionable:NTRansition? Query Syntax Sets and queries the Negative TRansition titer for the Data Questionable Status register. The STATus:PRESet value is 0. *RST has no effect. 2-63...
Page 170 Programming Commands Status Subsystem STATus:QUEStionable:PTRansition Query Syntax STATus:QUEStionable:PTRansition? Sets and queries the Positive TRansition flter for the Data Questionable Status register. set to After STATus:PRESet, all used bits are *RST has no effect. 2-64...
Page 171 Sweep Subsystem Table 2-1. Interactions between Dwell, Sweep Time, and Points. Interaction No coupling between SWEep:DWELl, SWEep:TIME and SWEep:POINts. No coupling between SWEep:DWELl, SWEep:TIME and SWEep:POINts. SWEep:TIME is always made minimum with the restriction from 10 ms lower limit, SWEep:TIME:LLIM feature and When SWEEP:TIME or SWEEP:POINts are changed, SWEep:DWELI - ISWEep:TIME I Both conditions above apply.
Page 172 Programming Commands Sweep Subsystem Query Syntax Sets and queries the amount of time in seconds that the sweeper will dwell at each step after reporting a Source Settled SRQ and pulsing the “Trigger Out” line low. This one value will be used at each step when in the SWE:TRIG:SOUR IMM mode of a stepped sweep.
Page 173 Programming Commands Sweep Subsystem SWEep:POINts SWEep:POINts <num>lMAXimumlMINimum SWEep:POINts? [MAXimumlMINimum] Sets and queries the number of points in a step sweep. When STEP = SPAN/(POINTS-1). SPAN is normally an independent variable but will be changed to STEP * (POINTS- 1) if both of these parameters are changed in the same message.
Page 174 Programming Commands Sweep Subsystem SWEep:POWer:STEP SWEep:POWer:STEP <num>[lev suffix]lMAXimumlMINimum SWEep:POWer:STEP? [MAXimumlMINimum] Sets and queries the size of each power step. :STEP is governed by the equation: STEP = POWER SPAN/(POlNTS- 1). POWER SPAN/STEP + 1 and a Parameter Bumped execution error will be reported. POWER STEP = SPAN/(POlNTS- 1) SPAN is normally an independent variable but will be changed to STEP * (POINTS-l)
Page 175 Programming Commands Sweep Subsystem SWEep[:FREQuency]:STEP SWEep[:FREQuency]:STEP <num>[freq suffix]lMAXimumlMINimum SWEep[:FREQuency]:STEP? [MAXimumIMINimum] Sets and queries the size of each frequency step. :STEP is governed by the equation: STEP = SPAN/(POlNTS- 1) SPAN/STEP+ 1 and a Parameter Bumped execution error will be reported. lf SPAN or POINTS are changed then: STEP = SPANJPOINTS- 1) The above creates a coupling with SWEEPTIME also.
Page 176 Programming Commands Sweep Subsystem SWEep:TIME SWEep:TIME <num>[time suffix]lMAXimumlMINimum SWEep:TIME? [MAXimumlMINimum] Sets and queries the current sweep time. Dwell can be coupled to equation: DWELl = SWEEPTIME/POlNTS Changing either SWEEPTIME or POINTS will cause DWELl to be recalculated but will not cause an error. lf you attempt to change DWELJ then :AUTO will be set to OFF.
Page 177 Programming Commands Sweep Subsystem SWEep:TIME:AUTO SWEep:TIME:AUTO ONlOFFlllO SWEep:TIME:AUTO? Sets and queries the automatic sweep time switch. The value of sweep time will be AUTOmatically to SWEep:TIME? Will remain a current setting unless bumped upward by other features. SWEep:TIME:LLIMit SWEep:TIME:LLIMit <num>[time suffix]lMAXimum SWEep:TIME:LLIMit? [MAXimumlMINimum] Sets and queries the lower sweep time limit.
Page 178 Programming Commands Sweep Subsystem Table 2-2. HP 83750 SCPI Sweep Mode Programming Table Mode Description of HP 83750 Sweep Sweep Condition P O W : S W E : :GEN CW Non-swept ignored ignored ANALOG Analog Freq Sweep ANALOG Manual Analog Freq Sweep...
Page 179 Programming Commands Sweep Subsystem SWEep:GENeration SWEep:GENeration STEPpedIANALog SWEep:GENeration? Sets and queries the type of sweep to be generated: an analog sweep or a digitally stepped sweep. In either case, all of the other sweep subsystem functions apply such as MANual, AUTO, INITiate:CONTinuous ONIOFF, etc. *RST is ANALog.
Page 180 Programming Commands Sweep Subsystem SWEep:MANual[:RELative] Sets and queries a percent of sweep to go to and lock. This command will have no effect unless SWEep:MODE is set to MANual *RST value is 0.50. SWEep:MANual:POINt SWEep:MANual:POINt <mm> Sets and queries the position of manual sweep in terms of number of sweep:points.
Page 181 Programming Commands Sweep Subsystem SWEep:MARKer:STATe Sets and queries the state of marker sweep. When this state is ON, the frequency sweep limits are taken to be from position of marker 1 to position of marker 2. If marker 1 was previously set to be greater than marker 2, their values will be permanently interchanged so that the instrument sweeps up in frequency.
Page 182 Each new frequency point is stepped to automatically, after waiting the specified DWELl time. Wait for a <GET> or *TRG over the HP-II3 before advancing to the next frequency in the sweep. Wait for a signal to be received on the external connector.
Page 183 System Subsystem SYSTem:ALTernate SYSTem:ALTernate <num>lMAXimumlMINimum SYSTem:ALTernate? [MAX~~~~IMIN~JUD] Sets and queries the save/recall register number with which to alternate the foreground state of the instrument with. *RST value is 1. SYSTem:ALTemate:STATe SYSTem:ALTernate:STATe ONlOFFIlIO SYSTem:ALTernate:STATe? Sets and queries the state of the Alternate State function. 2 - 7 7...
Page 184 This command changes the GPIB’s (General Purpose interface Bus) address. Allowable values are 0 through 30. SYSTem:COMMunicate:PMETer:ADDRess SYSTem:COMMunicate:PMETer:ADDRess <num> Query Syntax Sets and queries the HP-IB address to be used for the power meter during sweeper calibration routines. Allowable values are 0 through 30.
Page 185 Programming Commands System Subsystem SYSTem:COMMunicate:PMETer:TYPE? Sets and queries the mode type of power meter expected over the HP-IB to be used for the power meter during sweeper calibration routines. SYSTem:ERRor? Returns the next message in the error queue. The format of the response is <error number>,<error string)
Page 186 Programming Commands System Subsystem SYSTem:KEY[:CODE] SYSTem:KEY[:CODE]? This accomplishes the equivalentofpressing afrontpanelkey specified by the <num> code. The query form returns the key code ofthelastpressed ! Push front panel keys remotely OUTPUT 719;"SYSTEM:KEY:CODE 23" OUTPUT 719;"SYSTEM:KEY:CODE 47" OUTPUT 719;"SYSTEM:KEY:CODE 56" OUTPUT 719;"SYSTEM:KEY:CODE 49" OUTPUT 719;"SYSTEM:KEY:CODE 34"...
Page 187 Programming Commands System Subsystem Table 2-3. Sweeper Key Codes Key Name Key Name Code Code Instrument State Keys Power Keys (POWERLEVEL) (POWER/SWEEP) Entry Keys Marker Keys Modulation Keys Frequency Keys Sweep Keys 2 - 8 1...
Page 188 Programming Commands System Subsystem SYSTem:KEY:DISable SAVE The SAVJ3 key grouping is disabled. This also disables the SAVE STATE feature (Save Lock). SYSTem:KEY:DISable? SAVE Returns 1 if the save key is disabled, otherwise it returns 0. SYSTem:KEY:ENABle SYSTem:KEY:ENABle? SAVE Returns 0 if save key is disable, otherwise 1. SYSTem:KEY:ENABle SAVE This unlocks the SAVE registers.
Page 189 SYSTem:LANGuage “SCPI” SYSTem:LANGuage? This command causes the instrument to perform a language switch to another language system. TMSL is an alias for SCPI. For HP 8360 Series compatibility, the unquoted forms are also accepted, however, queries are always quoted. SYSTem:PRESet[:EXECute] This command sets the instrument state to either a factory or user defined state depending on the setting of SYSTem:PRESet:TYPE.
Page 190 Programming Commands System Subsystem SYSTem:PRESet:TYPE SYSTem:PRESet:TYPE FACTorylUSER Query Syntax This command sets and queries the type of preset to execute when the values to a specified state of the instrument that the user has saved with SYSTem:PRESet:SAVE. SYSTem:SECurity:CLEar SYSTem:SECurity:CLEa This command clears and initializes the entire content of RAM to all zeros. This clears all of the save/recall registers.
Page 191 Annunciators, such as SWEEP and CW, are blanked. This function cannot be executed when the instrument is connected to an HP 8757 or when the instrument is speaking 8350 compatibility language. 2-85...
Page 192: System:version
Programming Commands System Subsystem SYSTem:VERSion? This query returns a formatted numeric value corresponding to the SCPI version number for which the instrument complies. The response shall have the form YYYY.V. The Ys represent the year version (for example, 1990) and the V represents an approved revision number for that year.
Page 193: Trigger Subsystem
Trigger Subsystem TRIGger[:IMMediate] This command causes the trigger event to occur regardless of other settings in the subsystem. This event does not affect any other settings in this subsystem. This command has no effect unless the instrument is in the Wait for TRIG state.
Page 194: Trigger:source
The command sets and queries the source of the trigger event. The various settings have the following meanings. The trigger signal is always true. The trigger source is the group execute trigger from HP-IB. A trigger will occur when either a <GET>, or a *TRG command is received.
Page 195: Tsweep
Programming Commands Trigger Subsystem This is a convenience command that does the equivalent of By combing TSW with *WAI, *OPC and *OPC?, the functionality of “single sweep” (S2) and “take sweep” (TS) can be achieved. ‘lb get something similar to the old TS command, use TSW,*WAI to cause the parsing of commands to wait until the sweep is restarted and completed.
Page 197: Introduction
Data The HP 83750 Series of synthesized sweepers also accepts HP-IB com- mands in the same language as used by the HP 8350B sweep oscillator and HP 83500 Series plug-ins. This language is selected by the SCPI command “SYSTem: LANGuage COMPatible,” or from the front pan- el, SHIFT SPECIAL 15 ENTER.
Page 198 The HP-IB program code sequence typically mirrors that of the local N O T E front panel keystroke sequence. Function Codes (Prefix Activate) Function codes are typically 2 to 4 character mnemonics. For a func- tion that has a numeric value associated with it, passing the function code only will enable and activate the function for further data entry.
Page 199: Numeric Terminators
ASCII characters Line Feed or Next Line (LF or NL, decimal lo), semicolon (‘;‘, decimal 59), or comma (‘,‘, decimal when this is done the HP 8350B assumes the numeric value is in the fundamental units of Hz, seconds, or dB, depending on the active function.
Page 200: Instrument Preset
Power Sweep/Slope: set to 0 dB FM Sensitivity: -6 MHz/V Power Step Size: set to default value (1 dB) Instrument Preset does not affect Storage Registers, HP-IB address, or Service Request Mask Output Data The sweeper has several output modes that allow the user to learn and interrogate the present instrument state.
Page 201: Learn String
The program codes and syntax to enable each function are shown in Table 1. The Learn String, Mode String, and Status functions send a Data message consisting of a string of 8-bit binary bytes. These mes- sages are terminated by asserting the EOI signal in parallel with the last byte of the message to be sent.
Page 202: Mode String
Mode String Selected with the “OM” program code, the sweeper outputs a Mode String of 8 bytes in length. This binary data string describes presently active functions. The information passed includes only the active functions with no numeric values included. Use the Active or Interrogate Function if numeric values are desired.
Page 203 BYTE 1 (continued) Front Panel Key Codes Numeric Byte Value...
Page 204 BYTE 1 (continued) Numeric Byte Value Front Panel Key Codes 3 - 8...
Page 205 Current Active Function Code Numeric Byte Value 3 - 9...
Page 206 BYTE 3 Definition Definition BYTE 5 Definition 3 - 1 0...
Page 207 BYTE 5 (continued) Bits Definition BYTE 6 Definition Bits BYTE 7 Definition/Function Bit(s) 3 - 1 1...
Page 208 BYTE 8 Definition If the command “EMl” is sent to the 83570, (Default/PRESET condi- NOTE tion is EMO), the mode string will be 14 bytes long instead of the stan- dard 8 bytes, and will contain information about all 10 markers instead of just markers 1-5.
Page 209: Interrogate Function
contains the number of the Delta reference Marker. BYTE 10 Marker On/Off status BYTE 11-l 4: Bit Number BYTE 12 BYTE 13 Marker Numbers bit= 1 (Marker on) Interrogate Function Selected with the “OP” program code and the program code for the function to be interrogated, the sweeper will output the present nu- meric value of the selected function.
Page 210: Status
“CS” (Clear Status Byte) program code. Trigger The sweeper responds to HP-D3 Commands Group Execute Trigger (GET) and Selective Device Trigger (SDT) when it is in the SINGLE SWEEP mode. Receipt of either command causes the 83750 Series to start a sweep if the sweep had been previously reset;...
Page 211 Table 1. Input Programming Codes (1 of 8) NUMERIC VALUE PROGRAM CODE FUNCTION NUMERIC PREFIX SCALE RANGE FORMAT ACTIVATE SWEEP LIhliTS/hlODE START start/stop sweep Sweeper Center Frequency Frequency Limits SHCW OFFSET Frequency Offset VERNIER Frequency Vernier DISPLAY SHFB Display Of&et OFFSET DISPLAY 1-36...
Page 212 Table 1. input Programming Codes (2 of 8) NUMERIC VALUE PROGRAM CODE MODE/ FUNCTION NUMERIC PREFIX SUFFIX SCALE RANGE ACTIVATE FORMAT FREQUENCY MARKERS Sweeper Turn On and Set Frequency Marker Frequency* Limits Frequency Marker* where: Marker l-2 Sweep MARKER SWE 3 - 1 6...
Page 213 SCALE RANGE SUFFIX ACTIVATE FORMAT SWEEP TRIGGER TYPE Sweep Trigger Mode MANUAL SWEEP sweep Type MODULATION/BLANKING This command is accepted by the HP 85750 series but no action is performed because the function does not exist. 3 - 1 7...
Page 214 NUMERIC MODIFIERS SUFFIX SCALE RANGE ACTIVATE FORMAT Setting Frequency Step INSTRUMENT STATE This command is accepted by the HP 85750 serk but no action is performed because the fumtion does not exist. commands for this purpose. 3 - 1 8...
Page 215 PROGRAM CODE MODE/ FUNCTION NUMERIC MODIFIERS RANGE SCALE ACTIVATE FORMAT SPECIAL HP-IB FUNCTIONS OUTPUT STATUS BYTES S E R V I C E R E Q U E S T RM MASK REQUEST Status Bytes and EXTENDED STATUS RE Service Requests...
Page 216 Limits Set ALC Power Level ALC CONTROL Without Using the Attenuator see Plug-in Power Slope Mode *This command is accepted by the HP 85750 series but no action is performed because the function does not E 3 - 2 0...
Page 217 Table 1. Input Programming Codes (7 of 8) PROGRAM CODE NUMERIC VALUE FUNCTION NUMERIC SUFFIX SCALE RANGE ACTIVATE FORMAT RF Power Amplitude Markers *This commend is accepti ?d 3-21...
Page 218: Clear
Lockout (LLO) command has not been executed, the 83750 Series can also be set to Local by pressing the LOCAL key. In Local, the front panel is active but the instrument will still respond to HP-II3 pro- gramming codes.
Page 219: Service Request
Service Request The sweeper can initiate a Service Request (SRQ) whenever one of the following conditions exists: Error in syntax End of sweep Change in Extended Status Byte bit(s) Front panel key pressed Further information can be obtained by conducting a Serial Poll or by executing the Output Status command, both of which access Status Byte information.
Page 220: Status Byte
Status Byte The sweeper responds to a Serial Poll by sending its status byte as in- dicated in Table 2. The Extended Status Bytes are available but must be accessed via the Output Status command. When Bit 6 (Request Service) of the Status Byte is true (one), an SRQ has occurred. See Service Request for the conditions causing a Service request.
Page 221 Interface Function Codes Acceptor Handshake-full capability Basic Talker- Serial Poll capability Basic Listener- Unaddressed if MLA Service Request-full capability Remote Local-complete capability Parallel Poll-no capability Device Clear-full capability Device Trigger-full capability Controller- no capability Source Handshake-full capability Driver Electronics-open collector...
Page 222 Failed Unleveled SECOND EXTENDED STATUS BYTE (#3) DECIMAL VALUE F U N C - N/A The Second Extended Status Byte is always zero. It is output for com- N O T E patibility with the HP 8350 Sweep Oscillators. 3-26...
Page 223 Error Messages...
Page 224 If an error condition occurs in the sweeper, it will always be reported to both the front panel and HP-lB error queues. These two queues are viewed and managed separately. The Ihnsc] key is used to view the contents of the front panel error queue.
Page 225 The queue query message is a request for the next entry from the instrument’s error/event queue. This queue contains an integer in the range [ -32768, 32767 1. Negative error numbers are reserved by the SCPI standard and defined first in this document. Positive error numbers are instrument-dependent.
Page 226: Error Messages :Error? System:error
Error Messages The Error/Event Queue As errors and events are detected, they are placed in a queue. This queue is first in, lirst out. If the queue overflows, the last error/event in the queue is replaced with error -350 “Queue overflow” Any time the queue overflows, the least recent errors remain in the queue, and the most recent error/event is discarded.
Page 227: Error Numbers
Error Messages Error numbers The system-deIined error/event numbers are chosen on an enumerated (“ 1 of N”) basis. The SCPI-defined error/event numbers and the <error description> portions of the ERRor query response are listed here. The first error/event described in each class (for example, -100, -200, -300, -400) is a “generic” error.
Page 228: Scpi Error Messages
Out of Range” is the error message. When the [MSG) key is pressed, the error message is displayed in the leftmost display. The entire message is returned by the HP-lB query “SYSTem:ERRor?” . The error message contains the following parts:...
Page 229 Error Messages SCPI Error Message - The SCPI error message is Data out of range in the example. Detailed Description - All information after the semicolon (;) is a detailed description of what exactly caused the error. In the example, Test Patch Value Out of Range tells you that the user has entered a Self-Test Patch with upper or lower limit values greater than allowed.
Page 230: Command Error
Error Messages Command Error An <error/event number> in the range [ - 199, - 100 ] indicates that an IEEE 488.2 syntax error has been detected by the instrument’s parser. The occurrence of any error in this class shall cause the command error bit (bit 5) in the event status register (IEEE 488.2, section 11.5.1) to be set.
Page 231 -105 A Group Execute Trigger was received within a program message (see IEEE 488.2, 7.7). Correct the HP-IS controller program so that the group execute trigger does not occur within a line of HP-IB program code. -108 Parameter not allowed More parameters were received than expected for the header;...
Page 232 Error Messages -109 Missing parameter Fewer parameters were received than required for the header; for example, the *EMC common command requires one parameter, so receiving *EMC is not allowed. -110 Command header error) An error was detected in the header. This error message should be used when the device cannot detect the more specific errors described for errors - 111 through - 119.
Page 233 Error Messages Exponent too large The magnitude of the exponent was larger than 32000 (see IEEE 488.2, 7.7.2.4.1). -124 Too many digits The mantissa of a decimal numeric data element contained more than 255 digits excluding leading zeros (see IEEE 488.2, 7.7.2.4.1). Numeric data not allowed A legal numeric data element was received, but the device does not accept one in this position for the header.
Page 234 Error Messages -144 Character data too long The character data element contains more than twelve characters (see IEEE 488.2, 7.7.1.4). Character data not allowed A legal character data element was encountered where prohibited by the device. -150 String data error This error, as well as errors - 151 through - 159, are generated when parsing a string data element.
Page 235 Error Messages -170 Expression error This error, as well as errors -171 through -179, are generated when parsing an expression data element. This particular error message should be used if the device cannot detect a more specihc error. -171 Invalid expression The expression data element was invalid (see IEEE 488.2, 7.7.7.2);...
Page 236: Execution Error
Error Messages Execution Error An <error/event number> in the range [ -299, -200 ] indicates that an error has been detected by the instrument’s execution control block. The occurrence of any error in this class shall cause the execution error bit (bit 4) in the event status register (IEEE 488.2, section ll.S.
Page 237 Error Messages Error Error Description [description/explanation/examples] Number -200 Execution error This is the generic syntax error for devices that cannot detect more -201 Invalid while in local Indicates that a command is not executable while the device is in local due to a hard local control (see IEEE 488.2, 5.6.1.5); for example, a device with a rotary switch receives a message which would change the switches state, but the device is in local so the message cannot be executed.
Page 238 Error Messages - 2 1 4 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 239 Error Messages -226 Lists not same length. Attempted to use LIST structure having individual LIST’s of unequal lengths. -230 Data corrupt or stale Possibly invalid data; new reading started but not completed since last access. -231 Data questionable Indicates that measurement accuracy is suspect. -240 Hardware error Indicates that a legal program command or query could not...
Page 240 Error Messages -270 Macro error Indicates that a macro-related execution error occurred. This error message should be used when the device cannot detect the more specific errors described for errors -271 through -279. -271 Macro syntax error Indicates that a syntactically legal macro program data sequence, according to IEEE 488.2,10.7.2, could not be executed due to a syntax error within the macro definition (see IEEE 488.2, 10.7.6.3.) -272...
Page 241 Error Messages -276 Macro recursion error Indicates that a syntactically legal macro program data sequence could not be executed because the device found it to be recursive (see IEEE 488.2, 10.7.6.6). -277 Macro redefinition not allowed Indicates that a syntactically legal macro label in the *DMC command could not be executed because the macro label was already defined (see IEEE 488.2, 10.7.6.4).
Page 242: Device-Specific Error
Error Messages Device-Specific Error An <error/event number> in the range [ -399, -300 ] or [ 1, 32767 ] indicates that the instrument has detected an error which is not a command error, a query error, or an execution error; some device operations did not properly complete, possibly due to an abnormal hardware or firmware condition.
Page 243 Error Messages Error Description [description/explanation/examples] Error Number Device-specific error -300 This is the generic device dependent error for devices that cannot detect more specific errors. This code indicates only that a Device-Dependent Error as defined in IEEE 488.2, 11.5.1.1.6 has occurred.
Page 244: Query Error
Error Messages Query Error An <error/event number> in the range [ -499, -4001 indicates that the output queue control of the instrument has detected a problem with the message exchange protocol described in IEEE 488.2, chapter 6. The occurrence of any error in this class shall cause the query error bit (bit 2) in the event status register (IEEE 488.2, section 11.5.1) to be set.
Page 245 Error Messages Messages Error Error Description [description/explanation/examples] Number -400 Query error This is the generic query error for devices that cannot detect more specific errors. This code indicates only that a Query Error as -410 Query INTERRUPTED Indicates that a condition causing an INTERRUPTED Query error occurred (see IEEE 488.2, 6.3.2.3);...
Page 246: Instrument Specific Error Messages
Error Messages Instrument Specific Error Messages Block Transfer Errors Sent (101)’ For a specific calibration array, the HP-IB controller has sent more array elements than needed by the array definition. -161, “Invalid block data;Incorrect Number Of Calibration Array 1 0 2 Elements (102)”...
Page 247 -310, “System error;Comma.nd Send Error-No HP-IB Devices Found (204)” Indicates that during a Flatness Calibration, the instrument was sending a command to an HP-IB device, but could not find it. Flatness Calibration is aborted. -310, “System error;Cannot Find Power Meter On HP-IB Bus (205)”...
Page 248 Marker Allowed (301)” Indicates that one of the commands “Cl”, “C2”, “C3”, or “C4” were detected while the instrument was using the HP 8350 compatible language. These commands are accepted but no action is taken because the instrument does not have this feature.
Page 249 -178, “Expression data not allowed;SHM2, SHMS: No Counter Interface (310)” Indicates that the commands “SHM2” or “SHM3” were detected while the instrument was using the HP 8350 compatible language. These commands are accepted but no action is taken because the instrument does not have this feature.
Page 250 -178, “Expression data not allowed;SHSS: No Default Step Sizes Allowed (311)” Indicates that the command “SHSS” was detected while the instrument was using the HP 8350 compatible language. These commands are accepted but no action is taken because the instrument does not have this feature.
Page 251: Diagnostics And Self-Test Errors
Error Messages Diagnostics and Self-Test Errors 4 0 1 -300, “Device specific error;Test Patch Table Overflow (401)” Indicates that a Self-Test Patch was requested for storage in EEPROM Patch Table, but the table already has the maximum allowed (50). -300, “Device specific error;Illegal Test Patch Name (402)” Indicates that an illegal Self-Test Patch <name>...
Page 252 Error Messages -330, “Self-test failedSelf Test Patch ‘lhble Locked (406)” Indicates that segment 7 of the CPU board DIP switch is closed, prohibiting modifkation of the test patch table. Switch 7 must be in the open position to allow mod&&ion. -330, “Self-test failed;Instrument Bus Error Occurred (407)”...
Page 253 Error Messages -330, “Self-test failed;ROM Checksum Error (HIGH BYTE) (413)” Indicates that after the instrument is up and running, a series of power on self-tests have been run and error correction code checking has found that FLASH ROM has a high byte error. -330, “Self-test failed;Boot-ROM Checksum Error (LOW BYTE) (414)”...
Page 254 Error Messages -330, “Self-test failed;Power Up Calibration Corrupted: Default Used (420)” Indicates that after the instrument is up and running, a series of power on self-tests have been run and error correction code checking has found that contents of one of the calibration arrays were found corrupted.
Page 255: Hardware Configuration Errors
Error Messages Internal Hardware Errors -300, “Device specific error;V/GHz DAC Out Of Range (501)” -211, “Trigger ignored;Trigger Immediate Ignored (502)” -211, “Trigger ignored;Sweep Trigger Immediate Ignored (503)” -213, “Init ignored;Init Immediate Ignored (504)” -211, “Trigger ignored;Group Execute Trigger or *TRG Ignored (505)”...
Page 256: Calibration Routine Errors
Frequency zero can only be executed when the instrument is in stand alone mode. When the instrument is connected to an HP 8757 or when the instrument is speaking 8350 compatibility language, frequency zero cannot be implemented. If the user attempts to implement frequency zero in these modes, an error message will be generated.
Page 257 Error Messages No sufhciently wide YTF pass band was found in the initial phase of the peaking algorithm. peaking algorithm failed (705)” For unspecified reasons the later “fine peak” phase of the peaking algorithm failed. -300, “Device specific error;SAF Tracking Failure (706)” The SAF tracking algorithm failed for unspetied reasons.
Page 258 Error Messages -300, “Entered Password does not match the Security The user is trying to change the calibration security password and the verified password is incorrect as it does not match the system security password. The user is trying to change the calibration security password and the new password is not a 5-digit numerical entry.
Page 259 Error Messages Miscellaneous Hardware Dependent Errors -221, “Setting conflict;FNCW: Instrument Not In CW Mode (901)” Alt Sweep Mode (902)” When using the Alternate Sweep feature, the attenuator settings must be the same. This prevents the attenuator from being continuously switched between two different attenuation values. Rejected (903)”...
Page 260 Error Messages 9 0 5 -300, “Device specific error;Bad Checksum in MM Head (905)” The error condition occurs when the checksum test fails on the mm-wave source module NOVRAM. If the error occurs at power up or instrument preset, instrument will revert back to stand-alone mode.
Page 261: Scpi Conformance Information
SCPI Conformance Information...
Page 262 SCPI Conformance Information This chapter contains information pertaining to SCPI conformance.
Page 263 SCPI Conformance The sweeper uses the SCPI language for HP-B communication. The SCPI commands and queries that the sweeper understands are listed and described individually in Chapter 2, ‘Pro gmnming Commands. ’ Table 5-l lists all of the commands and queries that the sweeper understands and their status;...
Page 265 Table 5-1. SCPI Conformance (continued) Programming Command status ABORT Not part of the present SCPI 1992.0 definition Not pan of the present SCPI 1992.0 definition Not part of the present SCPI 1992.0 definition Not part of the present SCPI 1992.0 definition Not part of the present SCPI 1992.0 definition Not part of the present SCPI 1992.0 definition Not part of the present SCPI 1992.0 definition...
Page 266 Table 5-1. SCPI Conformance (continued) Programming Command Status Not part of the present SCPI 1992.0 definition Not part of the present SCPI 1992.0 definition Not part of the present SCPI 1992.0 definition Not part of the present SCPI 1992.0 definition 5 - 6...
Page 267 Table 5-l. SCPI Conformance (continued) Programming Command Status MARKer [nlAMPLitudel?l MARKer In] AOR Not part of the present SCPI 1992.0 definition MARKer [t-r] :FREQUENCYI?l Not part of the present SCPI 1992.0 definition MARKer [nl :MODEf?l MARKer In] :REARENCEI?I Not part of the present SCPI 1992.0 definition Not part of the present SCPI 1992.0 definition Not part of the present SCPI 1992.0 definition Not part of the present SCPI 1992.0 definition...
Page 268 Table 5-l. SCPI Conformance (continued) Programming Command Status Not Dart of the oresent SCPI 1992.0 definition Not part of the present SCPI 1992.0 definition Not Dart of the oresent SCPI 1992.0 definition...
Page 269 Table 5-1. SCPI Conformance (continued) Programming Command Status Not part of the present SCPI 1992.0 definition Not part of the present SCPI 1992.0 definition Not part of the present SCPI 1992.0 definition Not part of the present SCPI 1992.0 definition Not part of the present SCPI 1992.0 definition Not part of the present SCPI 1992.0 definition Not part of the present SCPI 1992.0 definition...
Page 270 Table 5-l. SCPI Conformance (continued) Proarammina Command Not part of the present SCPI 1992.0 definition Not oan of the oresent SCPI 1992.0 definition SYSTem:ERRor? Not part of the present SCPI 1992.0 definition Not oart of the oresent SCPI 1992.0 definition SYSTem:PRESet SYSTem:PRESet [:EXECutel Not part of the present SCPI 1992.0 definition...
Page 271: Index
Index...
Page 272 Index command defined, 1-84 abort statement, 1-6 angle brackets, l-16 in general status register model, 1-69 summary bit in general status register model, l-70 Boolean parameters discussed in detail, 1-44 explained briefly, I-31 brackets, angle, l-16 trigger source defined, 1-84 clear statement, 1-9 colon examples using, l-23...
Page 273 status, 2-59 subsystem, 1-19, l-20, 2-12 sweep, 2-64 syntax, 2-3 syntax overview, l-38, l-39 system, 2-76 trigger, 2-34, 2-86 command statements, fundamentals, l-5 command tables how to read, l-25 how to use, l-24 command trees defined, l-21 how to change paths, l-21 how to read, l-21 using efficiently, 1-23 commas...
Page 274 in general status register model, 1-69 FND, l-16 enter statement, l-12 error/event queue, 4-3 error message action required, 4-6 detailed description, 4-6 manual error number, 4-6 SCPI error message, 4-6 SCPI error number, 4-6 error message format, 4-6 error numbers, 4-4 errors permanent, 4-2 event commands, l-26...
Page 275 3-9 front panel key codes, 3-6 learn string, 3-5 mode string description, 3-6 replacement, 3-l to HP 83750 Series syntax, 3-15 HP 83750 Series to HP 8350B syntax, 3-15 HP-IB technical standard, l-85 HP-IB check, exampIe program, I-51...
Page 276 1-16 use as a program message terminator, l-17 use as a response message terminator, l-17 with HP BASIC OUTPUT statements, l-37 new Iine[new Iine] use as a program message terminator, 1-37 no errors, 4-5...
Page 277 2-45 precise talking, l-19, l-41 program and response messages, l-13 program example flatness correction, l-64 HP-IB check, l-51 looping and synchronization, l-60 queries and response data, l-55 setting up a sweep, l-54 synchronous sweep, l-62 program examples, l-47-67...
Page 278 1-69 enable register, l-70 event register, I-70 example sequence, l-7 1 general model, l-69 HP 83750 model, l-72 transition titer, l-70 status register structure, SCPI, l-78 status register system programming example, l-77 status system overview, l-68...
Page 279 sweep, example program, 1-54 synchronization, example program, l-60 synchronous sweep, example program, 1-62 syntax diagrams commands, l-38, l-39 message terminators, l-37 program message, l-37 response message, l-40 syntax drawings, l-5 synthesized sweeper status groups, l-72 system commands, 2-76 proper use of, l-22 terminators program message, I-17, 1-37 program messageuse in examples, l-17...

This manual is also suitable for:

83751b 83752a 83752b

HP 83751A Programming Manual

Section 1

Section 2

Quick Links

Chapters

Related Manuals for HP 83751A

Summary of Contents for HP 83751A

This manual is also suitable for:

Table of Contents