Keysight Technologies P Series Programming Manual

Keysight Technologies P Series Programming Manual

Modular power meter
Hide thumbs Also See for P Series:
Table of Contents

Advertisement

Quick Links

Keysight N8262A P-Series
Modular Power Meter
Programming
Guide

Advertisement

Table of Contents
loading
Need help?

Need help?

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

Questions and answers

Subscribe to Our Youtube Channel

Summary of Contents for Keysight Technologies P Series

  • Page 1 Keysight N8262A P-Series Modular Power Meter Programming Guide...
  • Page 2: Safety Information

    EXPRESS OR IMPLIED, WITH REGARD agreement and written consent from customarily provided to the public. TO THIS MANUAL AND ANY Keysight Technologies as governed by Accordingly, Keysight provides the INFORMATION CONTAINED HEREIN, United States and international Software to U.S. government INCLUDING BUT NOT LIMITED TO THE copyright laws.
  • Page 3: General Warranty

    General Warranty The material contained in this document is provided “as is,” and is subject to being changed, without notice, in future editions. Further, to the maximum extent permitted by applicable law, Keysight disclaims all warranties, either express or implied with regard to this manual and any information contained herein, including but not limited to the implied warranties of merchantability and fitness for a particular purpose.
  • Page 4: Equipment Operation

    Equipment Operation Warnings and Cautions This guide uses warnings and cautions to denote hazards. A WARNING notice denotes a hazard. It calls attention to an operating WARNING procedure, practice, or the like that, if not correctly performed or adhered to, could result in personal injury or loss of life.
  • Page 5: General Safety Considerations

    Failure to comply with these precautions or with specific warnings elsewhere in this manual violates safety standards of design, manufacture, and intended use of the instrument. Keysight Technologies, Inc. assumes no liability for the customer’s failure to comply with these requirements.
  • Page 6 THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK. Keysight N8262A Programming Guide...
  • Page 7: Table Of Contents

    Table of Contents General Warranty ......... . . 3 Restricted Rights Legend .
  • Page 8 Range ..........86 Setting Offsets .
  • Page 9 Using “*” Commands ........110 Syntax Conventions .
  • Page 10 CONFigure[1]|2|3|4[:SCALar][:POWer:AC]:DIFFerence: RELative [<expected_value>[,<resolution>[,<source list>]]] ..139 Syntax ..........139 Parameters .
  • Page 11 FETCh[1]|2|3|4[:SCALar][:POWer:AC]:DIFFerence: RELative? [<expected_value>[,<resolution>[,<source list>]]] ..152 Syntax ..........152 Parameters .
  • Page 12 Parameters ......... . . 163 Example .
  • Page 13: Ue>[,[,]]] Syntax Parameters Example

    ue>[,<resolution>[,<source list>]]] ......176 Syntax ..........176 Parameters .
  • Page 14 Example ..........194 Reset Condition .
  • Page 15 Reset Condition ........205 Query .
  • Page 16 CALCulate[1]|2|3|4:RELative[:MAGNitude]:AUTO <boolean>|ONCE . . 218 Syntax ..........218 Example .
  • Page 17 Query Example .........233 Error Messages .
  • Page 18 Example ..........246 Reset Condition .
  • Page 19 Query ..........261 Query Example .
  • Page 20 FORMat Subsystem FORMat Subsystem ........276 FORMat[:READings]:BORDer <character_data>...
  • Page 21 Example ..........293 Error Messages .
  • Page 22 Syntax ..........306 Parameters .
  • Page 23 Syntax ..........317 Parameters .
  • Page 24 Example ..........325 Reset Condition .
  • Page 25 10 SENSe Subsystem [SENSe] Subsystem ........343 [SENSe[1]]|SENSe2:AVERage Commands .
  • Page 26 Example ..........358 Reset Condition .
  • Page 27 Example ..........370 Reset Condition .
  • Page 28 [SENSe[1]]|SENSe2:CORRection:GAIN2 Commands ... . . 380 [SENSe[1]]|SENSe2:CORRection:GAIN2:STATe <boolean> ..381 Syntax ..........381 Example .
  • Page 29 Example ..........391 Reset Condition .
  • Page 30 [SENSe[1]]|SENSe2:TRACe Commands ......401 [SENSe[1]]|SENSe2:TRACe:OFFSet:TIME <numeric_value> ..402 Syntax ..........402 Parameters .
  • Page 31 Example ..........411 Reset Condition .
  • Page 32 Syntax ..........423 :ENABle <NRf>|<non-decimal numeric>...
  • Page 33 STATus:QUEStionable ........439 Syntax ..........439 STATus:QUEStionable:CALibration[:SUMMary] .
  • Page 34 Syntax ..........454 Parameters .
  • Page 35 SYSTem:DISPlay:BMP ........461 Syntax ..........461 Example .
  • Page 36 13 TRACe Subsystem TRACe Subsystem ........538 TRACe[1]|2[:DATA]? <character_data>...
  • Page 37 Syntax ..........550 Example .
  • Page 38 Example ..........559 Error Messages .
  • Page 39 Syntax ..........573 Example .
  • Page 40 Reset Condition ........584 Query .
  • Page 41 Syntax ..........594 Example .
  • Page 42 Query ..........604 Query Example .
  • Page 43 Syntax ..........618 Example .
  • Page 44 Parameters ......... . . 628 Query .
  • Page 45 Error Messages ........637 SERVice:SENSor[1]|2:POWer:PEAK:MAXimum? .
  • Page 46 Query ..........645 SERVice:VERSion:PROCessor <character_data>...
  • Page 47 *OPT? ..........661 Syntax .
  • Page 48 Keysight N8262A Programming Guide...
  • Page 49 List of Figures Figure 1-1 Frequency dependent offset tables ....78 Figure 1-2 Typical averaged readings on 8480 Series sensors . .85 Figure 1-3 Averaging range hysteresis .
  • Page 50 THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK. Keysight N8262A Programming Guide...
  • Page 51: List Of Tables

    List of Tables Table 1-1 MEASure? and CONFigure preset states ...61 Table 1-2 Possibilities of the defaulted source list parameter . .66 Table 1-3 Range of values for window limits .
  • Page 52 Table 12-10 CDMAone: Power meter presets for secondary channel sensors ....... . . 490 Table 12-11 cdma2000: Power meter presets .
  • Page 53 Table 12-32 1xeV-DO: Power meter presets ....515 Table 12-33 1 exV-DO: Power meter presets: Window/Measurement settings ....... . .516 Table 12-34 1exV-DO: Power meter presets for secondary channel sensors...
  • Page 54 THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK. Keysight N8262A Programming Guide...
  • Page 55 Keysight N8262A P-Series Modular Power Meter Programming Guide Power Meter Remote Operation Introduction Configuring the Remote Interface Zeroing and Calibrating the P-Series Power Sensor Making Measurement Using Frequency Dependent Offset Tables Setting the Range, Resolution and Averaging Range Setting Offsets Setting Measurement Limits Getting the Best Speed Performance How Measurements are Calculated...
  • Page 56: Power Meter Remote Operation Introduction

    Power Meter Remote Operation Introduction This chapter describes the parameters which configure the power meter and help you determine settings to optimize performance. It contains the following sections: – “Configuring the Remote Interface” on page 57. – “Zeroing and Calibrating the P-Series Power Sensor” on page 59.
  • Page 57: Configuring The Remote Interface

    For more information on configuring the remote interface connectivity, refer to NOTE the Keysight Technologies USB/LAN/GPIB Interfaces Connectivity Guide. If you have installed the IO Libraries Suite, you can access the Connectivity Guide via the Keysight IO Libraries Control icon. Alternatively, you can access the Connectivity Guide via the web at www.keysight.com/find/connectivity.
  • Page 58 Power Meter Remote Operation – Domain Name -SYSTem:COMMunicate:LAN:DNAMe – Hostname -SYSTem:COMMunicate:LAN:HNAMe – Restart Networkk -SYSTem:COMMunicate:LAN:RESTart The character_data values for the IP address, Subnet Mask, and Default Gateway can range between 0.0.0.0 and 255.255.255.255. If you configure an invalid IP Address or an IP address that is used by another NOTE device or host, an error message is generated.
  • Page 59: Zeroing And Calibrating The P-Series Power Sensor

    Power Meter Remote Operation Zeroing and Calibrating the P-Series Power Sensor P-Series wideband power sensor’s do not need manual calibration and zero routines performed. These are performed without removing the power sensor from the source. Zeroing Zeroing adjusts the power meter’s specified channel for a zero power reading. The command CALibration[1]|2:ZERO:AUTO [ONCE|ON|OFF|0|1] causes the power meter to perform its zeroing routine on the specified channel when enabled.
  • Page 60 Power Meter Remote Operation Calibration Sequence This feature allows you to perform a complete calibration sequence with a single query. The query is: CALibration[1|2][:ALL]? The query assumes that the power sensor is connected to the power reference oscillator. It turns the power reference oscillator on, then after calibrating, returns the power reference oscillator to the same state it was in prior to the command being received.
  • Page 61: Making Measurement

    Power Meter Remote Operation Making Measurement The MEASure? and CONFigure commands provide a straight-forward method to program the power meter for measurements. You can select the measurement’s expected power level, resolution and with the N8262A the measurement type (that is single channel, difference or ratio measurements) all in one command. The power meter automatically presets other measurement parameters to default values as shown in Table 1-1...
  • Page 62: Using Measure

    Power Meter Remote Operation Using MEASure? The simplest way to program the power meter for measurements is by using the MEASure? query. However, this command does not offer much flexibility. When you execute the command, the power meter selects the best settings for the requested configuration and immediately performs the measurement.
  • Page 63 Power Meter Remote Operation Example 2 - Specifying the Source List Parameter The MEASure command has three optional parameters, an expected power value, a resolution and a source list. These parameters must be entered in the specified order. If parameters are omitted, they default from the right. The parameter DEFault is used as a place holder.
  • Page 64 Power Meter Remote Operation Example 4 - Specifying the Resolution Parameter The previous examples detailed the use of the expected value and source list parameters. The resolution parameter is used to set the resolution of the specified window. This parameter does not affect the resolution of the data, however it does affect the auto averaging setting (refer to Figure 1-2).
  • Page 65 Power Meter Remote Operation Example 6 - Making a Ratio Measurement The following command is performed on the N8262A. It queries the upper window to make a ratio measurement of Channel A/B. The expected power and resolution parameters are defaulted, leaving them at their current settings. specifies the relationship of the specifies window channels in the ratio...
  • Page 66 Power Meter Remote Operation Table 1-2 Possibilities of the defaulted source list parameter Command Current Window Setup Measurement Upper Window: MEAS1[:POW][AC]? Any Other Any Other Lower Window: MEAS2[:POW][AC]? Any Other Upper Window: MEAS1:POW:AC:RAT Any Other Lower Window: MEAS2:POW:AC:RAT Any Other Upper Window: MEAS1:POW:AC:DIFF? Any Other...
  • Page 67: Using The Configure Command

    Power Meter Remote Operation Using the CONFigure Command When you execute this command, the power meter presets the optimum settings for the requested configuration (like the MEASure? query). However, the measurement is not automatically started and you can change measurement parameters before making measurements.
  • Page 68 Power Meter Remote Operation Example 1 - The Simplest Method The following program segments show the simplest method of querying the upper and lower window’s measurement results respectively. Using READ? Reset instrument *RST Configure upper window -defaults to a Channel A measurement CONF1 Take upper window (Channel A) measurement READ1?
  • Page 69 Power Meter Remote Operation The following examples use the source list parameter to specify the measurement channel as Channel A. The expected power and resolution parameters are defaulted, leaving them at their current settings. The measurement is carried out on the upper window. Although the READ? and FETCh? queries have three optional parameters it is not necessary to define them as shown in these examples.
  • Page 70 Power Meter Remote Operation The following example uses the expected value parameter to specify a value of –50 dBm. This selects the power meter’s lower range (refer to “Range” on page 86 for details of the range breaks). The resolution parameter is defaulted, leaving it at its current setting.
  • Page 71 Power Meter Remote Operation Some fine tuning of measurements can be carried out using the CONFigure command and INITiate and FETCh? commands. For example, in the above program segment some fine tuning can be carried out by setting the filter length to 1024 and the trigger delay off.
  • Page 72 Power Meter Remote Operation Using READ? Aborts Channel A ABOR1 Configures the upper window to make a measurement CONF1 DEF,3 using the current setting of the expected power and source list and a resolution setting of 3 Takes the upper window’s measurement. This is Channel A READ1? or B measurement depending on current window setup.
  • Page 73 Power Meter Remote Operation Some fine tuning of the above program segment can be carried out for example, by setting the trigger delay off. 1 ABOR1 2 CONF1 DEF,3 3 TRIG1:DEL:AUTO OFF 4 INIT1:IMM 5 FETC1? DEF,3 Example 5 - Making a Difference Measurement The following program segment can be carried out on the N8262A.
  • Page 74 Power Meter Remote Operation Using INITiate and FETCh? ABOR1 ABOR2 CONF2:POW:AC:DIFF DEF,DEF,(@1),(@2) SENS1:AVER:COUN 1024 SENS2:AVER:COUN 1024 TRIG1:DEL:AUTO OFF TRIG2:DEL:AUTO OFF INIT1:IMM INIT2:IMM FETC2:POW:AC:DIFF? FETC2:POW:AC:DIFF? DEF,DEF,(@2),(@1) (A second FETCh? query is sent to make a Channel B -Channel A measurement using the current measurement data).
  • Page 75: Using The Lower Level Commands

    Power Meter Remote Operation Using INITiate and FETCh? ABOR1 ABOR2 CONF2:POW:AC:RAT DEF,DEF,(@1),(@2) SENS1:AVER:COUN 512 SENS2:AVER:COUN 256 INIT1:IMM INIT2:IMM FETC2:POW:AC:RAT? FETC2:POW:AC:RAT? DEF,DEF,(@2),(@1) (A second FETCh? query is sent to make a Channel B -Channel A measurement using the current measurement data.) Using the Lower Level Commands An alternative method of making measurements is to use the lower level commands to set up the expected range and resolution.
  • Page 76 Power Meter Remote Operation Example The following example sets the expected power value to –50 dBm and the resolution setting to 3 using the lower level commands. The measurement is a single Channel A measurement carried out on the lower window. Aborts Channel A ABOR1 CALC2:MATH:EXPR "(SENS1)"...
  • Page 77: Using Frequency Dependent Offset Tables

    Power Meter Remote Operation Using Frequency Dependent Offset Tables This section describes how to use frequency dependent offset tables. These tables give you the ability to compensate for frequency effects in your test setup. Overview If the [SENSe[1]]|SENSe2:CORRection:CSET2:STATe command is OFF, the frequency dependent offset tables are not used.
  • Page 78: Figure 1-1 Frequency Dependent Offset Tables

    Power Meter Remote Operation TABLE 10 TABLE 1 TABLE N FREQ OFFSET FREQ OFFSET FREQ OFFSET FREQ OFFSET FREQ FREQ OFFSET OFFSET OFFSET FREQ OFFSET FREQ FREQ OFFSET OFFSET = Frequency Dependent Offset TABLE SELECTED FREQ OFFSET FREQ OFFSET Frequency dependent Frequency of the signal you want offset used to make to measure...
  • Page 79: Editing Frequency Dependent Offset Tables

    Power Meter Remote Operation Editing Frequency Dependent Offset Tables It is not possible to create any additional frequency dependent offset tables. However, the 10 existing tables can be edited using the MEMory subsystem. To do this: 1 Select one of the existing tables using: MEMory:TABle:SELect <string>...
  • Page 80 Power Meter Remote Operation The legal frequency suffix multipliers are any of the IEEE suffix multipliers, for NOTE example, KHZ, MHZ, and GHZ. If no units are specified the power meter assumes the data is Hz. PCT is the only legal unit for offset factors and can be omitted. The frequency and offset data must be within range.
  • Page 81 Power Meter Remote Operation – <string>,<type>,<size> The <string>, <type> and <size> are all character data. The <type> is always TABL. The <size> is displayed in bytes. For example, a sample of the response may look like: 560,8020,“Offset_1,TABL,220”,”Offset_2,TABL,340” ..Naming Frequency Dependent Offset Tables To rename a frequency dependent offset table use: MEMory:TABLe:MOVE <string>,<string>...
  • Page 82: Selecting A Frequency Dependent Offset Table

    Power Meter Remote Operation Modifying Data If you need to modify the frequency and offset factor data stored in a frequency dependent offset table you need to resend the complete data lists. If you have retained the original data in a program, edit the program and resend the data.
  • Page 83 Power Meter Remote Operation SENSe1:FREQuency 500KHZ INITiate1:IMMediate FETCh1? READ? Example ABORt1 CONFigure1:POWer:AC DEF,2,(@1) SENS1:CORR:CSET2:SEL "Offset1" SENS1:CORR:CSET2:STAT ON SENSe1:FREQuency 500KHZ READ1? If the measurement frequency does not correspond directly to a frequency in the NOTE frequency dependent offset table, the power meter calculates the offset using linear interpolation.
  • Page 84: Setting The Range, Resolution And Averaging

    Power Meter Remote Operation Setting the Range, Resolution and Averaging This section provides an overview of setting the range, resolution and averaging. For more detailed information about these features, refer to the individual commands in Chapter 10, "SENSe Subsystem". Resolution You can set the window’s resolution using the following command: DISPlay[:WINDow[1]|2][:NUMeric[1]|2] :RESolution <numeric_value>...
  • Page 85: Auto Averaging Mode

    Power Meter Remote Operation Auto Averaging Mode To enable and disable auto filter mode, use the following command: [SENSe[1]]|SENSe2:AVERage:COUNt:AUTO <boolean> When the auto filter mode is enabled, the power meter automatically sets the number of readings averaged together to satisfy the filtering requirements for most power measurements.
  • Page 86: Filter Length

    Power Meter Remote Operation Figure 1-3 Illustrates part of the power sensor dynamic range hysteresis. Range Hysteresis 9.5 dB 10.5 dB Minimum Sensor Power Minimum Sensor Power + 10 dB Figure 1-3 Averaging range hysteresis Filter Length You specify the filter length using the following command: [SENSe[1]]|SENSe2:AVERage:COUNt <numeric_value>...
  • Page 87 Power Meter Remote Operation Setting the Range To set the range manually use the following command: [SENSe[1]]|SENSe2:POWer:AC:RANGe <numeric_value> If the <numeric_value> is set to: – 0, the sensor’s lower range is selected. (For example, this range is –70 to –13.5 dBm for the E4412A power sensor.) –...
  • Page 88: Setting Offsets

    Power Meter Remote Operation Setting Offsets Channel Offsets The power meter can be configured to compensate for signal loss or gain in your test setup (for example, to compensate for the loss of a 10 dB attenuator). You use the SENSe command subsystem to configure the power meter. Gain and loss correction are a coupled system.
  • Page 89 Power Meter Remote Operation A dBm 10 –     - - - - - - - - - - - - - - - - - - - - - -     – B dBm 10 –...
  • Page 90: Figure 1-4 Limits Checking Application

    Power Meter Remote Operation Setting Measurement Limits You can configure the power meter to detect when a measurement is outside of a predefined upper and/or lower limit value. Limits are window or measurement display line based and can be applied to power, ratio or difference measurements.
  • Page 91: Figure 1-5 Limits Checking Results

    Power Meter Remote Operation Amplitude Fail +10 dBm +4 dBm Fail Frequency Figure 1-5 Limits checking results The range of values that can be set for the upper and lower limits and the default values depends on the measurement units in the currently measurement line - see Table 1-3.
  • Page 92: Checking For Limit Failures

    Power Meter Remote Operation Table 1-3 Range of values for window limits Window Defaul t Units Maximum Minimum Maximum Minimum +200 dB – 60 dB – 180 dB 120 dB – – +230 dBm 90 dBm 150 dBm 90 dBm 999.9 X% 100.0 a% 100.0 M%...
  • Page 93: Using Status

    Power Meter Remote Operation If TRIGger:DELay:AUTO is set to ON, then the number of failures returned by NOTE SENSe:LIMit:FCOunt? or CALCulate[1|2]:LIMit:FCOunt? is affected by the current filter settings. Using STATus You can use the STATus subsystem to generate an SRQ to interrupt your program when a limit failure occurs.
  • Page 94: Getting The Best Speed Performance

    Power Meter Remote Operation Getting the Best Speed Performance This section discusses the factors that influence the speed of operation (number of readings/sec) of a P-Series modular power meter. The following factors are those which have the greatest effect upon measurement speed (in no particular order): –...
  • Page 95: Table 1-4 Model Of Sensor And Measurement Rates

    Power Meter Remote Operation Sensor Different measurement rates are achievable depending on the sensor type being used, as shown in Table 1-4: Table 1-4 Model of sensor and measurement rates Sensor Measurement Rate NORMal DOUBle FAST 8480 Series 20 reading/s 40 reading/s E-Series E4410 and E9300 50 ms...
  • Page 96 Power Meter Remote Operation A trigger event can be any of the following: NOTE – The input signal meeting the trigger level criteria. – Auto-level triggering being used. – A TRIGger GET or *TRG command being sent. – An external TTL level trigger being detected. Trigger with Delay This can be achieved using the same sequences above (apart from the second) with TRIG:DEL:AUTO set to ON.
  • Page 97: Output Format

    Power Meter Remote Operation Output Format The power meter has two output formats for measurement results: ASCii and REAL. These formats are selected using the FORMat command. When FORMat is set to REAL, the returned result is in IEEE 754 floating-point format (note that the byte order can be changed using FORMat:BORDer) plus <LF>...
  • Page 98: Fast Mode

    Power Meter Remote Operation Fast Mode In the highest speed setting, the limiting factor tends to be the speed of the controller being used to retrieve results from the power meter, and to a certain extent, the volume of remote traffic. The latter can be reduced using the FORMat REAL command to return results in binary format.
  • Page 99: Figure 1-6 How Measurement Are Calculated

    Power Meter Remote Operation How Measurements are Calculated Figure 1-6 details how measurements are calculated. It shows the order in which the various power meter functions are implemented in the measurement calculation. WINDow1 WINDow2 TRACe:DATA? “TRACe1” TRACe:DATA? FORMat “TRACe2” CALCulate1 :LIM :FEED Limits...
  • Page 100: Status Reporting

    Power Meter Remote Operation Status Reporting Status reporting is used to monitor the power meter to determine when events have occurred. Status reporting is accomplished by configuring and reading status registers. The power meter has the following main registers: – Status Register –...
  • Page 101: Figure 1-7 Generalized Status Register Model

    Power Meter Remote Operation Condition Transition Event Enable Register Filter Register Register Bit 0 Bit 1 Summary Bit 2 Bit 3 Figure 1-7 Generalized status register model When a status group is implemented in an instrument, it always contains all of the component registers.
  • Page 102: Figure 1-8 Typical Status Register Bit Changes

    Power Meter Remote Operation Enable Register The enable register specifies the bits in the event register that can generate a summary bit. The instrument logically ANDs corresponding bits in the event and enable registers and ORs all the resulting bits to obtain a summary bit. Enable registers are read-write.
  • Page 103: How To Use Register

    Power Meter Remote Operation How to Use Register The polling method is used to access the information in status groups when: – your language/development environment does not support SRQ interrupts. – you want to write a simple, single purpose program and do not want to add the complexity of setting an SRQ handler.
  • Page 104: Table 1-5 Bit Definitions - Device Status Register

    Power Meter Remote Operation Device Status Register The device status register set contains bits which give device dependent information. The following bits in these registers are used by the power meter: Table 1-5 Bit definitions - Device status register Bit Number Decimal Weight Definition Not used...
  • Page 105: Using The Operation Complete Commands

    Power Meter Remote Operation Using the Operation Complete Commands The *OPC? and *OPC commands allow you to maintain synchronization between the computer and the power meter. The *OPC? query command places an ASCII character 1 into the power meter’s output queue when all pending power meter commands are complete.
  • Page 106: Saving And Recalling Power Meter Configurations

    Power Meter Remote Operation Saving and Recalling Power Meter Configurations To reduce repeated programming, up to ten power meter configurations can be stored in the power meter’s non-volatile memory. The error list, remote addresses, sensor calibration table data, zeroing and calibration information are not stored. How to Save and Recall a Configuration Power meter configurations are saved and recalled with the following commands: *SAV <NRf>...
  • Page 107: Using Device Clear To Halt Measurements

    Power Meter Remote Operation Using Device Clear to Halt Measurements Device clear is an IEEE-488 low-level bus message which can be used to halt measurements in progress. Different programming languages and IEEE-488 interface cards provide access to this capability through their own unique commands.
  • Page 108: Figure 1-9 Hierarchical Structure Of Scpi

    Power Meter Remote Operation An Introduction to the SCPI Language Standard Commands for Programmable Instruments (SCPI) defines how you communicate with an instrument from a bus controller. The SCPI language uses a hierarchical structure similar to the file systems used by many bus controllers. The command tree is organized with root-level commands (also called subsystems) positioned at the top, with multiple levels below each root-level command.
  • Page 109: Using A Semicolon

    Power Meter Remote Operation Using a Semicolon (;) Use a semicolon to separate two commands within the same command string. The semicolon does not change the present path specified. For example, the following two statements are equivalent. Note that in the first statement the first colon is optional but the third is compulsory.
  • Page 110: Syntax Conventions

    Power Meter Remote Operation If you send two query commands without reading the response from the first, NOTE then attempt to read the second response, you may receive some data from the first response followed by the complete second response. To avoid this, do not send a query command without reading the response.
  • Page 111: Figure 1-10 Format Of

    Power Meter Remote Operation SCPI Data Types The SCPI language defines different data formats for use in program messages and response messages. Instruments are flexible listeners and can accept commands and parameters in various formats. However, SCPI instruments are precise talkers. This means that SCPI instruments always respond to a particular query in a predefined, rigid format.
  • Page 112 Power Meter Remote Operation <NAN> Definition Not a number (NAN) is represented as 9.91 E37. Not a number is defined in IEEE 754. <non-decimal numeric> Definition Throughout this document <non-decimal numeric> is used to represent numeric information in bases other than ten (that is, hexadecimal, octal and binary). The following syntax diagram shows the standard for these three data structures.
  • Page 113: Figure 1-11 Format Of

    Power Meter Remote Operation <digit> Figure 1-11 Format of <non-decimal numeric> Refer to section 7.7.4.1 of IEEE 488.2 for further details. <NRf> Definition Throughout this document <NRf> is used to denote a flexible numeric representation. For example: +200; –56; +9.9E36. Refer to section 7.7.2.1 of IEEE 488.2 for further details.
  • Page 114: Figure 1-12 Format Of

    Power Meter Remote Operation <NR1> Definition Throughout this document <NR1> numeric response data is defined as: digit Figure 1-12 Format of <NR1> For example: – 146 – +146 – –12345 Refer to section 8.7.2 of IEEE 488.2 for further details. <NR2>...
  • Page 115: Figure 1-14 Format Of

    Power Meter Remote Operation <NR3> Definition Throughout this document <NR3> numeric response data is defined as: digit digit digit Figure 1-14 Format of <NR3> For example: – 1.23E+6 – 123.4E-54 – –1234.567E+90 Refer to section 8.7.4 of IEEE 488.2 for further details. <numeric_value>...
  • Page 116: Figure 1-15 Format Of

    Power Meter Remote Operation The format is defined as: Program Data <inserted > <non-single quote char> " " <inserted > " " <non-double quote char> Response Data " " <inserted > " " <non-double quote char> Figure 1-15 Format of <string> Input Message Terminators Program messages sent to a SCPI instrument must terminate with a <newline>...
  • Page 117: Scpi Compliance Information

    Power Meter Remote Operation SCPI Compliance Information The power meter complies with the rules and regulations of the present version of SCPI (Standard Commands for Programmable Instruments). You can determine the SCPI version with which the power meter’s is in compliance by sending the SYSTem:VERSion? command from the remote interface.
  • Page 118 Power Meter Remote Operation SYSTem:COMMunicate:LAN:CURRent:DNAMe? SYSTem:COMMunicate:LAN:CURRent:SMASk? SYSTem:COMMunicate:LAN:ADDRess SYSTem:COMMunicate:LAN:DGATeway SYSTem:COMMunicate:LAN:DHCP SYSTem:COMMunicate:LAN:HNAMe SYSTem:COMMunicate:LAN:RESTart SYSTem:COMMunicate:LAN:SMASk SYSTem:LOCal SYSTem:REMote SYSTem:RWLock UNIT[1|2]:POWer:RATio Keysight N8262A Programming Guide...
  • Page 119: Summary Of Commands

    Power Meter Remote Operation Summary of Commands For detail of each SCPI (Standard Commands for Programmable Instruments) command available to program the power meter, refer to later chapters for more details on each command. In different subsystems the numeric suffix of program mnemonics can represent either a channel selection or a window selection.
  • Page 120: Making Measurements On Wireless Communication Standards

    Power Meter Remote Operation Making Measurements on Wireless Communication Standards The following sections describe typical measurements you may want to make. They are also described, for soft front panel operation, in the User’s Guide. The optimum method of measuring these Wireless Communication Standards is to use the SYSTem:PRESet <character_data>...
  • Page 121: Starting A Preset Example

    Power Meter Remote Operation Starting a Preset Example 10 *CLS !Clears error queue 20 *RST !Resets meter settings to their default states 30 :SYST:ERR? <read string> !The system error query should !return “0: No Error” 40 SERV:SENS:TYPE? !The sensor type query should return one !of the following:N1921A|N1922A The GSM setup is only valid !with these sensors 50 SYSTem:PRESet “GSM900”...
  • Page 122 Power Meter Remote Operation THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK. Keysight N8262A Programming Guide...
  • Page 123 Keysight N8262A P-Series Modular Power Meter Programming Guide MEASurement Commands MEASurement Commands CONFigure[1] |2|3|4? CONFigure [1] |2|3|4 Commands CONFigure[1]|2|3|4[:SCALar][:POWer:AC] [<expected_value>[,<resolution>[,<source list>]]] CONFigure[1]|2|3|4[:SCALar][:POWer:AC]:RELative [<expected_value>[,<resolution>[,<source list>]]] CONFigure[1]|2|3|4[:SCALar][:POWer:AC]:DIFFerence [<expected_value>[,<resolution>[,<source list>]]] CONFigure[1]|2|3|4[:SCALar][:POWer:AC]:DIFFerence: RELative [<expected_value>[,<resolution>[,<source list>]]] CONFigure[1]|2|3|4[:SCALar][:POWer:AC]:RATio [<expected_value>[,<resolution>[,<source list>]]] CONFigure[1]|2|3|4[:SCALar][:POWer:AC]:RATio: RELative[<expected_value>[,<resolution>[,<source list>]]] FETCh[1]|2|3|4 Queries FETCh[1]|2|3|4[:SCALar][:POWer:AC]? [<expected_value>[,<resolution>[,<source list>]]] FETCh[1]|2|3|4[:SCALar][:POWer:AC]:RELative? [<expected_value>[,<resolution>[,<source list>]]]...
  • Page 124 MEASurement Commands READ[1]|2|3|4[:SCALar][:POWer:AC]? [<expected_value>[,<resolution>[,<source list>]]] READ[1]|2|3|4[:SCALar][:POWer:AC]:RELative? [<expected_value>[,<resolution>[,<source list>]]] READ[1]|2|3|4[:SCALar][:POWer:AC]:DIFFerence? [<expected_value>[,<resolution>[,<source list>]]] READ[1]|2|3|4[:SCALar][:POWer:AC]:DIFFerence: RELative? [<expected_value>[,<resolution>[,<source list>]]] READ[1]|2|3|4[:SCALar][:POWer:AC]:RATio? [<expected_value>[,<resolution>[,<source list>]]] READ[1]|2|3|4[:SCALar][:POWer:AC]:RATio:RELative? [<expected_value>[,<resolution>[,<source list>]]] MEASure[1]|2|3|4 Commands MEASure[1]|2|3|4[:SCALar][:POWer:AC]? [<expected_value>[,<resolution>[,<source list>]]] MEASure[1]|2|3|4[:SCALar][:POWer:AC]:RELative? [<expected_value>[,<resolution>[,<source list>]]] MEASure[1]|2|3|4[:SCALar][:POWer:AC]:DIFFerence? [<expected_value>[,<resolution>[,<source list>]]] MEASure[1]|2|3|4[:SCALar][:POWer:AC]:DIFFerence: RELative? [<expected_value>[,<resolution>[,<source list>]]] MEASure[1]|2|3|4[:SCALar][:POWer:AC]:RATio? [<expected_value>[,<resolution>[,<source list>]]] MEASure[1]|2|3|4[:SCALar][:POWer:AC]:RATio:RELative? [<expected_value>[,<resolution>[,<source list>]]] This chapter explains how to use the MEASure group of instructions to acquire data using a set of high level instructions.
  • Page 125 MEASurement Commands MEASurement Commands Measurement commands are high level commands used to acquire data. They enable you to trade interchangeability against fine control of the measurement process. Measurement Descriptions Command Provides the simplest way to program a power meter for measurements. MEASure? is a compound MEASure? command which is equivalent to an ABORT followed by a CONFigure and a READ?.
  • Page 126: Figure 2-1 Measurement Display Configure Block Window

    MEASurement Commands CONfigure1? upper window/upper measurement CONFigure3? upper window/lower measurement CONFigure2? lower window/upper measurement CONFigure4? lower window/lower measurement Figure 2-1 Measurement display CONFigure block window Optional Parameters CONFigure, FETCh?, READ? and MEASure? have the following three optional parameters: – An expected power value –...
  • Page 127 MEASurement Commands Resolution The <resolution> parameter sets the resolution of the specified window. This parameter does not affect the resolution of the remote data but it does affect the auto averaging setting. Where a channel is set up in both the upper and lower window and the <resolution>...
  • Page 128 MEASurement Commands Keyword Parameter Form Notes Page [no query] page 141 :RATio [<expected_value> [,<resolution>[,<source list>]]] [no query] page 143 :RELative [<expected_value> [,<resolution>[,<source list>]]] [non-SCPI] FETCh[1]|2|3|4 [:SCALar] [query only] page 146 [:POWer:AC]? [<expected_value> [,<resolution>[,<source list>]]] [query only] page 148 :RELative? [<expected_value> [non-SCPI] [,<resolution>[,<source list>]]] [query only]...
  • Page 129 MEASurement Commands Keyword Parameter Form Notes Page [query only] page 169 :RELative? [<expected_value> [,<resolution>[,<source list>]]] [non-SCPI] MEASure[1]|2|3|4 [:SCALar] [query only] page 172 [:POWer:AC]? [<expected_value> [,<resolution>[,<source list>]]] [query only] page 174 :RELative? [<expected_value> [non-SCPI] [,<resolution>[,<source list>]]] [query only] page 176 :DIFFerence? [<expected_value>...
  • Page 130: Configure[1] |2|3|4

    MEASurement Commands CONFigure[1] |2|3|4? This query returns the present configuration of the specified window/ measurement. Syntax CONF The string returned depends on the setting of the CALCulate:MATH and CALCulate:RELative:STATe commands. The configuration is returned as a quoted string in the following format: “<function>...
  • Page 131: Example

    MEASurement Commands CALCulate:RELative: CALCulate:MATH Function <source list> STATe :POW:AC:RAT (@2),(@1) (SENSe2/SENSe1) :POW:AC:RAT:REL (@1),(@2) (SENSe1/SENSe2) :POW:AC:RAT:REL (@2),(@1) (SENSe2/SENSe1) POW:AC:RAT (@1),(@1) (SENSe1/SENSe1) POW:AC:RAT (@2),(@2) (SENSe2/SENSe2) POW:AC:RAT:REL (@1),(@1) (SENSe1/SENSe1) POW:AC:RAT:REL (@2),(@2) (SENSe2/SENSe2) <expected_value> returns the expected value sent by the last CONFigure command or +20 dBm by default. Note that when the display is showing dual windows this value is meaningless.
  • Page 132: Configure [1] |2|3|4 Commands

    MEASurement Commands CONFigure [1] |2|3|4 Commands The CONFigure commands are used on the specified window/measurement to set: – The expected power level being measured. – The resolution of the window/measurement. – The channel(s) on which the measurement is to be made. The CONFigure commands do not make the power measurement after setting the configuration.
  • Page 133 MEASurement Commands CONFigure[1]|2|3|4[:SCALar][:POWer:AC] [<expected_value>[,<resolution>[,<source list>]]] This command is used on the specified window/measurement to set: – The expected power level of the measurement. – The resolution of the window/measurement. – The channel on which the measurement will be made. Syntax CONF :SCAL :POW...
  • Page 134 MEASurement Commands Item Description/Defaul t Range of Values resolution A numeric value for the resolution. If unspecified the current 1 to 4 resolution setting is used. 1.0, 0.1, 0.01, 0.001 source list The channel which the command is implemented on. (@1) If unspecified the current window setup is used.
  • Page 135 MEASurement Commands CONFigure[1]|2|3|4[:SCALar][:POWer:AC]:RELative [<expected_value>[,<resolution>[,<source list>]]] This command sets the measurement function, range and resolution of the specified window. It sets the measurement function to single channel with relative mode on. The relative value used is that set by the CALCulate:RELative: MAGNitude:AUTO command.
  • Page 136 MEASurement Commands Item Description/Defaul t Range of Values 1 to 4 A numeric value for the resolution. If unspecified the current resolution 1.0, 0.1, 0.01, 0.001 resolution setting is used. The channel which the command is implemented on. (@1) If unspecified the current window setup is used. However, (@2) source list if the window shows a ratio or difference measurement, the...
  • Page 137 MEASurement Commands CONFigure[1]|2|3|4[:SCALar][:POWer:AC]:DIFFerence [<expected_value>[,<resolution>[,<source list>]]] This command sets the measurement function and resolution of the specified window. It sets the measurement function to difference with relative mode off. Syntax CONF :DIFF :POW :SCAL expected_value Space resolution source list Parameters Refer to “Optional Parameters”...
  • Page 138: Example

    MEASurement Commands Example This command configures the lower window/ CONF2:DIFF DEF,1,(@2),(@1) upper measurement to make a difference measurement of Channel B -Channel A, using the current sensor range and a resolution of 1 on both channels. Keysight N8262A Programming Guide...
  • Page 139: Relative [[,[,]]]

    MEASurement Commands CONFigure[1]|2|3|4[:SCALar][:POWer:AC]:DIFFerence: RELative [<expected_value>[,<resolution>[,<source list>]]] This command sets the measurement function, range and resolution of the specified window. It sets the measurement function to difference with relative mode on. The relative value used is set by the CALCulate:RELative:MAGNitude:AUTO command. Syntax CONF :REL...
  • Page 140: Example

    MEASurement Commands [a] The mnemonic DEF means DEFault. This is not equivalent to the DEFault parameter used in the command sub-systems. The parameters must be entered in the specified order. If parameters are omitted, they default from the right. The parameter DEFault is used as a place holder. Specifying DEF leaves teh parameter value unchanged.
  • Page 141 MEASurement Commands CONFigure[1]|2|3|4[:SCALar][:POWer:AC]:RATio [<expected_value>[,<resolution>[,<source list>]]] This command sets the measurement function, range and resolution of the specified window. It sets the measurement function to ratio with relative mode off. Syntax CONF :RAT :POW :SCAL expected_value Space resolution source list Parameters Refer to “Optional Parameters”...
  • Page 142 MEASurement Commands Example This command configures the upper window/ CONF1:RAT DEF,4,(@1),(@2) upper measurement to make a ratio measurement of Channel A over Channel B, using the current sensor range and a resolution setting of 4 on both channels. Keysight N8262A Programming Guide...
  • Page 143: Configure[1]|2|3|4[:Scalar][:Power:ac]:Ratio Relative[[,[,]]]

    MEASurement Commands CONFigure[1]|2|3|4[:SCALar][:POWer:AC]:RATio: RELative[<expected_value>[,<resolution>[,<source list>]]] This command sets the measurement function, range and resolution of the specified window. It sets the measurement function to ratio with relative mode on. The relative value used is that set by the CALCulate:RELative:MAGNitude:AUTO command. Syntax :RAT :REL...
  • Page 144 MEASurement Commands [a] The mnemonic DEF means DEFault. This is not equivalent to the DEFault parameter used in the command sub-systems. The parameters must be entered in the specified order. If parameters are omitted, they default from the right. The parameter DEFault is used as a place holder. Specifying DEF leaves the parameter value unchanged.
  • Page 145: Fetch[1]|2|3|4 Queries

    MEASurement Commands FETCh[1]|2|3|4 Queries The FETCh? queries set the specified window’s measurement function. This can be set to either single channel, difference or ratio measurements, with relative mode either off or on. They then recalculate the measurement and place the result on the bus.
  • Page 146: Fetch[1]|2|3|4[:Scalar][:Power:ac]? [[,[,]]]

    MEASurement Commands FETCh[1]|2|3|4[:SCALar][:POWer:AC]? [<expected_value>[,<resolution>[,<source list>]]] This command sets the specified window’s measurement function to single channel with relative mode off, recalculates the measurement and places the result on the bus. The result is a power based measurement and is expressed in the units defined by UNIT[1]|2|3|4:POWer.
  • Page 147: Example

    MEASurement Commands Item Description/Defaul t Range of Values resolution A numeric value for the resolution. If it is unspecified the 1 to 4 current resolution setting is used. If a value is entered it should 1.0, 0.1, 0.01, 0.001 correspond to the current resolution setting otherwise an error occurs.
  • Page 148 MEASurement Commands FETCh[1]|2|3|4[:SCALar][:POWer:AC]:RELative? [<expected_value>[,<resolution>[,<source list>]]] This command sets the specified window’s measurement function to single channel with relative mode on, recalculates the measurement and places the results on the bus. The result is a ratio based measurement and is expressed in the units defined by UNIT[1]|2|3|4:POWer:RATio.
  • Page 149 MEASurement Commands Item Description/Defaul t Range of Values resolution A numeric value for the resolution. If it is unspecified the current 1 to 4 resolution setting is used. If a value is entered it should 1.0, 0.1, 0.01, 0.001 correspond to the current resolution setting otherwise an error [[a] occurs.
  • Page 150 MEASurement Commands FETCh[1]|2|3|4[:SCALar][:POWer:AC]:DIFFerence? [<expected_value>[,<resolution>[,<source list>]]] This command sets the specified window’s measurement function to power difference with relative mode off, recalculates the measurement and places the results on the bus. The result is a power based measurement and is expressed in the units defined by UNIT[1]|2|3|4:POWer.
  • Page 151 MEASurement Commands Item Description/Defaul t Range of Values resolution A numeric value for the resolution. If it is unspecified the 1 to 4 current resolution setting is used. If a value is entered it 1.0, 0.1, 0.01, 0.001 should correspond to the current resolution setting otherwise an error occurs.
  • Page 152: Relative? [[,[,]]]

    MEASurement Commands FETCh[1]|2|3|4[:SCALar][:POWer:AC]:DIFFerence: RELative? [<expected_value>[,<resolution>[,<source list>]]] This command sets the specified window’s measurement function to power difference with relative mode on, recalculates the measurement and places the results on the bus. The result is a ratio based measurement and is expressed in the units defined by UNIT[1]|2|3|4:POWer:RATio.
  • Page 153: Example

    MEASurement Commands Item Description/Defaul t Range of Values resolution A numeric value for the resolution. If it is unspecified the 1 to 4 current resolution setting is used. If a value is entered it 1.0, 0.1, 0.01, 0.001 should correspond to the current resolution setting otherwise an error occurs.
  • Page 154 MEASurement Commands FETCh[1]|2|3|4[:SCALar][:POWer:AC]:RATio? [<expected_value>[,<resolution>[,<source list>]]] This command sets the specified window’s measurement function to power ratio with relative mode off, recalculates the measurement and places the results on the bus. The result is a ratio based measurement and is expressed in the units defined by UNIT[1]|2|3|4:POWer:RATio.
  • Page 155 MEASurement Commands Item Description/Defaul t Range of Values resolution A numeric value for the resolution. If it is unspecified the 1 to 4 current resolution setting is used. If a value is entered it 1.0, 0.1, 0.01, 0.001 should correspond to the current resolution setting otherwise an error occurs.
  • Page 156: Fetch[1]|2|3|4[:Scalar][:Power:ac]:Ratio:relative? [[,[,]]]

    MEASurement Commands FETCh[1]|2|3|4[:SCALar][:POWer:AC]:RATio:RELative? [<expected_value>[,<resolution>[,<source list>]]] This command sets the specified window’s measurement function to power ratio with relative mode on, recalculates the measurement and places the results on the bus. The result is a ratio based measurement and is expressed in the units defined by UNIT[1]|2|3|4:POWer:RATio.
  • Page 157 MEASurement Commands Item Description/Defaul t Range of Values resolution A numeric value for the resolution. If it is unspecified the 1 to 4 current resolution setting is used. If a value is entered it should 1.0, 0.1, 0.01, 0.001 correspond to the current resolution setting otherwise an error occurs.
  • Page 158: Read[1]|2|3|4 Commands

    MEASurement Commands READ[1]|2|3|4 Commands The READ? commands are most commonly used with the CONFigure command to cause a new power measurement to be taken and the result returned to the output buffer. The format of the result is set by FORM[:READ][:DATA]. Refer to Chapter 6, “FORMat Subsystem,”...
  • Page 159 MEASurement Commands READ[1]|2|3|4[:SCALar][:POWer:AC]? [<expected_value>[,<resolution>[,<source list>]]] This command sets the specified window’s measurement function to single channel with relative mode off, aborts then initiates the specified channel, calculates the measurement result and places the result on the bus. The result is a power based measurement and is expressed in the units defined by UNIT[1]|2|3|4:POWer.
  • Page 160: Example

    MEASurement Commands Item Description/Defaul t Range of Values expected_value The expected power level parameter can be set to DEF or a Sensor dependent (for the expected power level) numeric value. If a value is entered it should correspond to that set by CONFigure otherwise an error occurs. resolution A numeric value for the resolution.
  • Page 161 MEASurement Commands READ[1]|2|3|4[:SCALar][:POWer:AC]:RELative? [<expected_value>[,<resolution>[,<source list>]]] This command sets the specified window’s measurement function to single channel with relative mode on, aborts then initiates the specified channel, calculates the measurement result and places the result on the bus. The result is a ratio based measurement and is expressed in the units defined by UNIT[1]|2|3|4:POWer:RATio.
  • Page 162 MEASurement Commands Item Description/Defaul t Range of Values expected_value The expected power level parameter can be set to DEF or a Sensor dependent (for the expected power level) numeric value. If a value is entered it should correspond to that set by CONFigure otherwise an error occurs. resolution A numeric value for the resolution.
  • Page 163 MEASurement Commands READ[1]|2|3|4[:SCALar][:POWer:AC]:DIFFerence? [<expected_value>[,<resolution>[,<source list>]]] This command sets the specified window’s measurement function to difference mode with relative mode off, aborts then initiates both Channel A and B, calculates the difference measurement result and places the result on the bus. The result is a power based measurement and is expressed in the units defined by UNIT[1]|2|3|4:POWer.
  • Page 164: Example

    MEASurement Commands Item Description/Defaul t Range of Values expected_value The power meter ignores the numeric value entered in this Sensor dependent (for the expected power parameter. Any value entered is treated like DEF. level) resolution A numeric value for the resolution. If it is unspecified the current 1 to 4 resolution setting is used.
  • Page 165 MEASurement Commands READ[1]|2|3|4[:SCALar][:POWer:AC]:DIFFerence: RELative? [<expected_value>[,<resolution>[,<source list>]]] This command sets the specified window’s measurement function to difference mode with relative mode on, aborts then initiates both Channel A and B, calculates the difference measurement result and places the result on the bus. The result is a ratio based measurement and is expressed in the units defined by UNIT[1]|2|3|4:POWer:RATio.
  • Page 166 MEASurement Commands Item Description/Defaul t Range of Values expected_value The power meter ignores the numeric value entered in this Sensor dependent (for the expected power parameter. Any value entered is treated like DEF. level) resolution A numeric value for the resolution. If it is unspecified the current 1 to 4 resolution setting is used.
  • Page 167: Read[1]|2|3|4[:Scalar][:Power:ac]:Ratio? [[,[,]]]

    MEASurement Commands READ[1]|2|3|4[:SCALar][:POWer:AC]:RATio? [<expected_value>[,<resolution>[,<source list>]]] This command sets the specified window’s measurement function to ratio mode with relative mode off, aborts then initiates both Channel A and B, calculates the ratio measurement result and places the result on the bus. The result is a ratio based measurement and is expressed in the units defined by UNIT[1]|2|3|4:POWer:RATio.
  • Page 168 MEASurement Commands Item Description/Defaul t Range of Values expected_value The power meter ignores the numeric value entered in this Sensor dependent (for the expected power parameter. Any value entered is treated like DEF. level) resolution A numeric value for the resolution. If it is unspecified the current 1 to 4 resolution setting is used.
  • Page 169: Read[1]|2|3|4[:Scalar][:Power:ac]:Ratio:relative? [[,[,]]]

    MEASurement Commands READ[1]|2|3|4[:SCALar][:POWer:AC]:RATio:RELative? [<expected_value>[,<resolution>[,<source list>]]] This command sets the specified window’s measurement function to ratio mode with relative mode on, aborts then initiates both Channel A and B, calculates the ratio measurement result using the new sensor data and places the result on the bus.
  • Page 170: Example

    MEASurement Commands Item Description/Defaul t Range of Values expected_value The power meter ignores the numeric value entered in this Sensor dependent (for the expected power parameter. Any value entered is treated like DEF. level) resolution A numeric value for the resolution. If it is unspecified the current 1 to 4 resolution setting is used.
  • Page 171: Measure[1]|2|3|4 Commands

    MEASurement Commands MEASure[1]|2|3|4 Commands The MEASure? commands configure the power meter to perform a power measurement with the given measurement function, relative mode setting, range and resolution then makes the measurement. The format of the result is set by FORM[:READ][:DATA]. Refer to Chapter 6, “FORMat Subsystem,”...
  • Page 172: Measure[1]|2|3|4[:Scalar][:Power:ac]? [[,[,]]]

    MEASurement Commands MEASure[1]|2|3|4[:SCALar][:POWer:AC]? [<expected_value>[,<resolution>[,<source list>]]] This command sets the specified window’s measurement function to single channel with relative mode off, aborts, configures the window then initiates Channel A or B, calculates the measurement result and places the result on the bus.
  • Page 173 MEASurement Commands [a] The mnemonic DEF means DEFault. This is not equivalent to the DEFault parameter used in the command sub-systems. The parameters must be entered in the specified order. If parameters are omitted, they default from the right. The parameter DEFault is used as a place holder. Specifying DEF leaves the parameter value unchanged.
  • Page 174 MEASurement Commands MEASure[1]|2|3|4[:SCALar][:POWer:AC]:RELative? [<expected_value>[,<resolution>[,<source list>]]] This command sets the specified window’s measurement function to single channel with relative mode on, aborts, configures then initiates the specified channel, calculates the measurement result and places the result on the bus. The result is a ratio based measurement and is expressed in the units defined by UNIT[1]|2|3|4:POWer:RATio.
  • Page 175 MEASurement Commands Item Description/Defaul t Range of Values resolution A numeric value for the resolution. If unspecified the current 1 to 4 resolution setting is used. 1.0, 0.1, 0.01, 0.001 source list The channel which the command is implemented on. (@1) If unspecified the current window setup is used.
  • Page 176: Syntax

    MEASurement Commands MEASure[1]|2|3|4[:SCALar][:POWer:AC]:DIFFerence? [<expected_value>[,<resolution>[,<source list>]]] This command sets the specified window’s measurement function to difference mode with relative mode off, aborts, configures then initiates both Channel A and B, calculates the difference measurement result and places the result on the bus. The result is a power based measurement and is expressed in the units defined by UNIT[1]|2|3|4:POWer.
  • Page 177 MEASurement Commands Item Description/Defaul t Range of Values resolution A numeric value for the resolution. If unspecified the current 1 to 4 resolution setting is used. 1.0, 0.1, 0.01, 0.001 source list This channel list specifies the channels used to calculate the (@1),(@2) difference.
  • Page 178: Measure[1]|2|3|4[:Scalar][:Power:ac]:Difference: Relative? [[,[,]]]

    MEASurement Commands MEASure[1]|2|3|4[:SCALar][:POWer:AC]:DIFFerence: RELative? [<expected_value>[,<resolution>[,<source list>]]] This command sets the specified window’s measurement function to difference mode with relative mode on, aborts, configures then initiates both Channel A and B, calculates the difference measurement result and places the result on the bus. The result is a ratio based measurement and is expressed in the units defined by UNIT[1]|2|3|4:POWer:RATio.
  • Page 179: Example

    MEASurement Commands Item Description/Defaul t Range of Values resolution A numeric value for the resolution. If unspecified the current 1 to 4 resolution setting is used. 1.0, 0.1, 0.01, 0.001 source list This channel list specifies the channels used to calculate the (@1),(@2) difference.
  • Page 180: Measure[1]|2|3|4[:Scalar][:Power:ac]:Ratio? [[,[,]]]

    MEASurement Commands MEASure[1]|2|3|4[:SCALar][:POWer:AC]:RATio? [<expected_value>[,<resolution>[,<source list>]]] This command sets the specified window’s measurement function to ratio mode with relative mode off, aborts, configures then initiates both Channel A and B, calculates the ratio measurement result and places the result on the bus. The result is a ratio based measurement and is expressed in the units defined by UNIT[1]|2|3|4:POWer:RATio.
  • Page 181: Example

    MEASurement Commands Item Description/Defaul t Range of Values resolution A numeric value for the resolution. If unspecified the current 1 to 4 resolution setting is used. 1.0, 0.1, 0.01, 0.001 source list This channel list specifies the channels used to calculate the (@1),(@2) difference.
  • Page 182: Measure[1]|2|3|4[:Scalar][:Power:ac]:Ratio:relative

    MEASurement Commands MEASure[1]|2|3|4[:SCALar][:POWer:AC]:RATio:RELative? [<expected_value>[,<resolution>[,<source list>]]] This command sets the specified window’s measurement function to ratio mode with relative mode on, aborts, configures then initiates both Channel A and B, calculates the ratio measurement and places the result on the bus. The result is a ratio based measurement and is expressed in the units defined by UNIT[1]|2|3|4:POWer:RATio.
  • Page 183: Example

    MEASurement Commands Item Description/Defaul t Range of Values 1 to 4 A numeric value for the resolution. If unspecified the current resolution 1.0, 0.1, 0.01, 0.001 resolution setting is used. This channel list specifies the channels used to calculate the (@1),(@2) difference.
  • Page 184 MEASurement Commands THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK. Keysight N8262A Programming Guide...
  • Page 185 Keysight N8262A P-Series Modular Power Meter Programming Guide CALCulate Subsystem CALCulate Subsystem CALCulate[1]|2|3|4:FEED[1]|2 <string> CALCulate[1]|2|3|4:GAIN Commands CALCulate[1]|2|3|4:GAIN[:MAGNitude] <numeric_value> CALCulate[1]|2|3|4:GAIN:STATe <boolean> CALCulate[1]|2|3|4:LIMit Commands CALCulate[1]|2|3|4:LIMit:CLEar:AUTo <boolean>|ONCE CALCulate[1]|2|3|4:LIMit:CLEar[:IMMediate] CALCulate[1]|2|3|4:LIMit:FAIL? CALCulate[1]|2|3|4:LIMit:FCOunt? CALCulate[1]|2|3|4:LIMit:LOWer[:DATA] <numeric_value> CALCulate[1]|2|3|4:LIMit:UPPer[:DATA] <numeric_value> CALCulate[1]|2|3|4:LIMit:STATe <boolean> CALCulate[1]|2|3|4:MATH Commands CALCulate[1]|2|3|4:MATH[:EXPRession] <string> CALCulate[1]|2|3|4:MATH[:EXPRession]:CATalog? CALCulate[1]|2|3|4:PHOLd:CLEar CALCulate[1]|2|3|4:RELative Commands CALCulate[1]|2|3|4:RELative[:MAGNitude]:AUTO <boolean>|ONCE CALCulate[1]|2|3|4:RELative:STATe <boolean>...
  • Page 186: Calculate Subsystem

    CALCulate Subsystem CALCulate Subsystem The CALCulate subsystem performs post acquisition data processing. Functions in the SENSe subsystem are related to data acquisition, while the CALCulate subsystem operates on the data acquired by a SENSe function. There are four independent CALCulate blocks in the power meter: two for each window, as shown in Figure 3-1.
  • Page 187: Figure 3-2 Calculate Block

    CALCulate Subsystem CALCulate Block SENSe1: :FEED :MATH Input from Peak or Avg SENSe1 FEED1 block “A” | “B” “A-A” | “A/A” “B-B” | “B/B” :REL :GAIN SENSe2: Input from “A-B” | “A/B” Peak or Avg FEED2 SENSe2 block “B-A” | “B/A” Figure 3-2 CALCulate block Keysight N8262A Programming Guide...
  • Page 188 CALCulate Subsystem Keyword Parameter Form Notes Page CALCulate[1]|2|3|4 page 189 :FEED[1]|2 <data_handle> :GAIN page 193 [:MAGNitude] <numeric_value> page 195 :STATe <boolean> :LIMit :CLEar page 198 :AUTO <boolean>|ONCE page 200 [:IMMediate] [query only] page 201 :FAIL? [query only] page 202 :FCOunt? :LOWer page 204 [:DATA]...
  • Page 189: Calculate[1]|2|3|4:Feed[1]|2

    CALCulate Subsystem CALCulate[1]|2|3|4:FEED[1]|2 <string> This command sets the input measurement mode to be fed to the specified input on the CALC block. It is applied to the measurement after the CALC:MATH:EXPR command has been used to specify which channel the feed is taken from. Measurement modes are coupled for combination measurements (for example, ratio measurements).
  • Page 190: Parameters

    CALCulate Subsystem Parameters Item Description Range of Values string The input measurement type to be fed to the specific input on the CALC block: “POW:PEAK” – PEAK: peak power “POW:PTAV” “POW:AVER” – PTAV: peak to average – AVER: average Values may be followed by ON SWEEP[1]|2|3|4 where the numeric specifies the gate to be used for the feed.
  • Page 191: Query

    CALCulate Subsystem Query CALCulate[1]|2|3|4:FEED[1]2? The query returns the current value of the string. Query Example This command queries the current setting of CALC1:FEED2? the data_handle on FEED2 of the upper window/upper measurement. Error Message – If the command is used when no sensor is attached, error –241 “Hardware missing”...
  • Page 192: Calculate[1]|2|3|4:Gain Commands

    CALCulate Subsystem CALCulate[1]|2|3|4:GAIN Commands These commands are used to enter and enable a display offset on the specified window/measurement. The display offset is applied to the measurement signal after any math calculation. The following commands are detailed in this section: CALCulate[1]|2|3|4:GAIN[:MAGNitude] <numeric value>...
  • Page 193: Calculate[1]|2|3|4:Gain[:Magnitude]

    CALCulate Subsystem CALCulate[1]|2|3|4:GAIN[:MAGNitude] <numeric_value> This command is used to enter a value for the display offset on the specified window/measurement. The display offset is applied to the measurement signal after any math calculation. Entering a value using this command automatically turns the CALCulate[1]|2|3|4:GAIN:STATe command to ON.
  • Page 194 CALCulate Subsystem Example This command enters a display offset of CALC2:GAIN 20 20 dB to the lower window/lower measurement. Reset Condition On reset, the display offset is set to 0 dB (DEF). Query CALCulate[1]|2|3|4:GAIN[:MAGNitude]? [MIN|MAX] The query returns the current setting of the display offset or the value associated with MIN and MAX.
  • Page 195: Calculate[1]|2|3|4:Gain:state

    CALCulate Subsystem CALCulate[1]|2|3|4:GAIN:STATe <boolean> This command is used on the specified window/measurement to enable and disable the display offset set by the CALCulate[1]|2|3|4:GAIN[:MAGNitude] command. Syntax Space :STAT 0|OFF CALC :GAIN 1|ON Example This command enables the display offset for CALC2:GAIN:STAT 1 the lower window/upper measurement.
  • Page 196 CALCulate Subsystem Query Example This command queries whether the display CALC1:GAIN:STAT? offset in the upper window/upper measurement is on or off. Error Message If CALCulate[1]|2|3|4:GAIN:STATe is set to ON while SENSe:SPEed is set to 200, error –221, “Settings Conflict” occurs. Keysight N8262A Programming Guide...
  • Page 197: Calculate[1]|2|3|4:Limit Commands

    CALCulate Subsystem CALCulate[1]|2|3|4:LIMit Commands These commands set the limits on both the upper and lower windows/ measurements enabling you to: – Set upper and lower level limits – Query if there has been a failure – Count the number of failures –...
  • Page 198: Calculate[1]|2|3|4:Limit:clear:auto |Once

    CALCulate Subsystem CALCulate[1]|2|3|4:LIMit:CLEar:AUTo <boolean>|ONCE This command controls when the FCO (fail counter) is cleared of any limit failures. The FCO is used to determine the results returned by the CALCulate[1]|2|3|4:LIMit:FAIL? query. – If ON is specified, the FCO is set to 0 each time a measurement is: –...
  • Page 199: Example

    CALCulate Subsystem Example This command switches on automatic CALC1:LIM:CLE:AUTO 1 clearing of the FCO for the upper window/ upper measurement. Reset Condition On reset, both windows and their measurements are set to ON. Query CALCulate[1]|2|3|4:LIMit:CLEar:AUTO? The query command enters a 1 or 0 into the output buffer indicating whether limit failures are cleared automatically when a new measurement is initiated on the specified window section.
  • Page 200: Calculate[1]|2|3|4:Limit:clear[:Immediate]

    CALCulate Subsystem CALCulate[1]|2|3|4:LIMit:CLEar[:IMMediate] This command immediately clears the FCO (fail counter) of any limit failures for the specified window. The FCO is used to determine the results returned by the CALCulate[1]|2|3|4:LIMit:FAIL? query. Syntax :CLE :IMM :LIM CALC Example This command clears the FCO for the lower CALC2:LIM:CLE:IMM window/upper measurement.
  • Page 201: Calculate[1]|2|3|4:Limit:fail

    CALCulate Subsystem CALCulate[1]|2|3|4:LIMit:FAIL? This query enters a 1 or 0 into the output buffer indicating whether there have been any limit failures for the specified window. A limit failure is defined as CALC[1]|2|3|4:LIMit:FCO? being non-zero. The FCO (fail counter) can be zeroed using the CALC[1]|2|3|4:LIMit:CLEar command.
  • Page 202: Calculate[1]|2|3|4:Limit:fcount

    CALCulate Subsystem CALCulate[1]|2|3|4:LIMit:FCOunt? This query returns the total number of limit failures for the specified window/ measurement. If the appropriate STATe commands are set to ON, each time a measurement is initiated on the specified window/measurement and the result is outside the limits, the counter is incremented by one.
  • Page 203: Syntax

    CALCulate Subsystem Syntax :LIM :FCO CALC Example This command queries the number of limit CALC1:LIM:FCO? failures on the upper window/upper measurement. Reset Condition On reset, the counter is set to zero for both measurements of the upper and lower windows. Keysight N8262A Programming Guide...
  • Page 204: Calculate[1]|2|3|4:Limit:lower[:Data]

    CALCulate Subsystem CALCulate[1]|2|3|4:LIMit:LOWer[:DATA] <numeric_value> This command enters a value for the lower test limit for the specified window/ measurement used in the CALCulate[1]|2|3|4:LIMit:FAIL? test. The units used are dependent on the current setting of UNIT:POWer and CALCulate:RELative:STATe as shown in Table 3-1.
  • Page 205: Parameters

    CALCulate Subsystem Parameters Item Description/Defaul t Range of Values numeric_value A numeric value for the lower test limit: –150 to +230 dBm or – DEF: the default is –90.00 dBm or –90 db –180 to +200 dB – MIN: –150 dBm or –180 dB –...
  • Page 206: Calculate[1]|2|3|4:Limit:upper[:Data]

    CALCulate Subsystem CALCulate[1]|2|3|4:LIMit:UPPer[:DATA] <numeric_value> This command enters a value for the upper test limit for the specified window/ measurement used in the CALCulate[1]|2|3|4:LIMit:FAIL? test. The units used are dependent on the current setting of UNIT:POWer and CALCulate:RELative:STATe as shown in Table 3-2.
  • Page 207 CALCulate Subsystem Parameters Item Description/Defaul t Range of Values numeric_value A numeric value for the lower test limit: –150 to +230 dBm or – DEF: the default is –90.00 dBm or –90 db –180 to +200 dB – MIN: –150 dBm or –180 dB –...
  • Page 208: Query Example

    CALCulate Subsystem Query Example This command queries the setting of the CALC2:LIM:UPP:DATA? upper limit for the lower window/upper measurement. The query returns the current setting of the upper limit or the values associated with MIN and MAX for the specified window/measurement. Keysight N8262A Programming Guide...
  • Page 209: Calculate[1]|2|3|4:Limit:state

    CALCulate Subsystem CALCulate[1]|2|3|4:LIMit:STATe <boolean> This command enables/disables the test limits for the specified window. Syntax Space 0|OFF :LIM :STAT CALC 1|ON Example This command enables the limit checking CALC2:LIM:STAT 1 function for the lower window upper measurement. Reset Condition On reset, limit checking is disabled. Query CALCulate[1]|2|3|4:LIMit:STATe? The query enters 1 or 0 into the output buffer indicating the status of the limits...
  • Page 210 CALCulate Subsystem Query Example This command queries whether the limit CALC1:LIM:STAT? checking function for the upper window/ upper measurement is on or off. Error Message If CALCulate[1|2|3|4]:LIMit:STATe is set to ON while [SENSe[1]]|SENSe2:SPEed is set to 200, error –221, “Settings Conflict” occurs. Keysight N8262A Programming Guide...
  • Page 211: Calculate[1]|2|3|4:Math Commands

    CALCulate Subsystem CALCulate[1]|2|3|4:MATH Commands These commands define and carry out the following mathematical transformations on SENSe data: – Single channel – Difference – Ratio The following commands are detailed in this section: CALCulate[1]|2|3|4:MATH[:EXPRession] <string> CALCulate[1]|2|3|4:MATH[:EXPRession]:CATalog? Keysight N8262A Programming Guide...
  • Page 212: Calculate[1]|2|3|4:Math[:Expression]

    CALCulate Subsystem CALCulate[1]|2|3|4:MATH[:EXPRession] <string> This command sets the specified window/measurement to a single channel, difference or ratio measurement. The command may result in a change to the measurement mode set by CALC:FEED <string>. The following sequence of commands provides an example: 1 SENS2:DET:FUN=AVERage 2 CALC:MATH “(SENS1)”...
  • Page 213: Parameters

    CALCulate Subsystem Parameters Item Description/Defaul t Range of Values string A single string value detailing the measurement type: “(SENS1)” – The default is SENS1 if the upper window is selected, or “(SENS2)” SENS2 if the lower window is selected. “(SENS1–SENS1)” “(SENS2–SENS2)”...
  • Page 214: Query

    CALCulate Subsystem Query CALCulate[1]|2|3|4:MATH[:EXPRession]? The query returns the current math measurement setting on the specified window. Query Example This command queries the current setting of CALC1:MATH? the math expression on the upper window/ upper measurement. Error Messages – If <string> is not set to “(SENS1)” or “(SENS2)” while SENS1:SPEEd or SENS2:SPEEd is set to 200, error –221, “Settings Conflict”...
  • Page 215: Calculate[1]|2|3|4:Math[:Expression]:Catalog

    CALCulate Subsystem CALCulate[1]|2|3|4:MATH[:EXPRession]:CATalog? This query lists all the defined expressions. The response is a list of comma separated strings. Each string contains an expression. – The string is: "(SENS1)","(SENS2)","(SENS1/SENS2)", "(SENS2/SENS1)","(SENS1–SENS2)","(SENS2–SENS1)" "(SENS1–SENS1)","(SENS2–SENS2)","(SENS1/SENS1)", "(SENS2/SENS2)" Syntax :CAT :EXPR :MATH CALC Example This command lists all the defined math CALC1:MATH:CAT? expressions.
  • Page 216: Calculate[1]|2|3|4:Phold:clear

    CALCulate Subsystem CALCulate[1]|2|3|4:PHOLd:CLEar This command clears the peak hold value for a specified CALC block so that a new peak hold value can be set. Clearing the peak hold value for a specified CALC block may affect the peak hold NOTE value of other CALC blocks, depending on the CALC channel set up (set by CALC:MATH:EXPR).
  • Page 217: Calculate[1]|2|3|4:Relative Commands

    CALCulate Subsystem CALCulate[1]|2|3|4:RELative Commands These commands compare the measurement signal to a reference value. Within the CALCulate block the relative value is applied to the measurement signal after any math calculations and display offsets have been applied. The commands described in this section: CALCulate[1]|2|3|4:RELative[:MAGNitude]:AUTO <boolean>|ONCE CALCulate[1]|2|3|4:RELative:STATe <boolean>...
  • Page 218: Calculate[1]|2|3|4:Relative[:Magnitude]:Auto |Once

    CALCulate Subsystem CALCulate[1]|2|3|4:RELative[:MAGNitude]:AUTO <boolean>|ONCE This command sets the reference value to be used in the relative measurement. Within the CALCulate block the relative value is applied to the measurement signal after any math calculations and display offsets have been applied. The value should be set to ONCE to set the reference value to be used in relative measurements.
  • Page 219: Example

    CALCulate Subsystem Example This command sets a reference value to be CALC1:REL:AUTO ONCE used in the relative measurement on the upper window/upper measurement. Query CALCulate[1]|2|3|4:RELative[:MAGNitude]:AUTO? The query always returns OFF. Error Message – If CALCulate:RELative[:MAGNitude]:AUTO is set to ONCE while SENSe:SPEed is set to 200, error –221, “Settings Conflict”...
  • Page 220: Calculate[1]|2|3|4:Relative:state

    CALCulate Subsystem CALCulate[1]|2|3|4:RELative:STATe <boolean> This command enables/disables relative mode. If the command is: – disabled, the measurement signal remains unchanged. – enabled, the current relative value set by CALCulate:RELative:MAGnitude:AUTO is applied to the measurement signal. Syntax Space :REL :STAT 0|OFF CALC 1|ON Example...
  • Page 221: Query Example

    CALCulate Subsystem Query Example This command queries whether relative CALC1:REL:STAT? mode is off or on for the upper window/upper measurement. Error Message If CALCulate:RELative:STATe is set to ON while SENSe:SPEed is set to 200, error –221, “Settings Conflict” occurs. Keysight N8262A Programming Guide...
  • Page 222 CALCulate Subsystem THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK. Keysight N8262A Programming Guide...
  • Page 223 Keysight N8262A P-Series Modular Power Meter Programming Guide CALibration Subsystem CALibration Subsystem CALibration[1]|2[:ALL] CALibration[1]|2[:ALL]? CALibration[1]|2:AUTO [ONCE|ON|OFF|0|1] CALibration[1]|2:RCALibration <boolean> CALibration[1]|2:RCFactor <numeric_value> CALibration[1]|2:ZERO:AUTO [ONCE|ON|OFF|0|1] CALibration[1]|2:ZERO:NORMal:AUTO <boolean> This chapter explains how the CALibration command subsystem is used to zero and calibrate the power meter.
  • Page 224: Calibration Subsystem

    CALibration Subsystem CALibration Subsystem The CALibration command subsystem is used to zero and calibrate the power meter. It is also used to set the reference calibration factor for the power sensor which is being used. The numeric suffix of the CALibration command refers to a specific channel: –...
  • Page 225 CALibration Subsystem Keyword Parameter Form Notes Page CALibration[1]|2 [event; no query] page 226 [:ALL] [event;query] page 228 [:ALL]? page 230 :AUTO <boolean>|ONCE page 232 :RCALibration <boolean> [non-SCPI] page 234 :RCFactor <numeric_value> :ZERO page 237 :AUTO <boolean>|ONCE :NORMal page 239 :AUTO <boolean>...
  • Page 226: Calibration[1]|2[:All]

    CALibration Subsystem CALibration[1]|2[:ALL] This command is identical to CALibration[1]|2[:ALL]?, however, unlike the NOTE query it does not provide a response to indicate whether the calibration has been successful or not. This command causes the power meter to perform a calibration sequence on the specified channel.
  • Page 227: Syntax

    CALibration Subsystem Syntax :ALL Example This command causes the power meter to CAL1:ALL perform a calibration sequence on Channel A. Error Messages – If the calibration was not carried out successfully the error –231, “Data Questionable; CAL ERROR” occurs. The error message will specify which channel failed calibration.
  • Page 228 CALibration Subsystem CALibration[1]|2[:ALL]? This query is identical to CALibration[1]|2[:ALL], however, unlike the NOTE command, it provides a response to indicate whether the calibration has been successful or not. This query causes the power meter to perform a calibration sequence on the specified channel.
  • Page 229 CALibration Subsystem Syntax :ALL Query Example This command causes the power meter to CAL1:ALL? perform a calibration sequence on Channel A and return a result. Error Messages – If the calibration was not carried out successfully the error –231, “Data Questionable;...
  • Page 230: Calibration[1]|2:Auto [Once|On|Off|0|1]

    CALibration Subsystem CALibration[1]|2:AUTO [ONCE|ON|OFF|0|1] This command calibrates the specified channel when enabled. The command assumes that an 8480 or E-Series power sensor is connected to a 1 mW reference signal. 1|ON can only be used with a P-Series sensor. When 1|ON is enabled the ±...
  • Page 231: Syntax

    CALibration Subsystem Syntax Space 0|OFF :AUTO 1|ON ONCE Example This command causes the power meter to CAL1:AUTO ONCE perform a calibration on Channel A. Reset Condition On reset, automatic calibration is disabled. Query CALibration[1]|2:AUTO? The query always returns a value of 0. Error Messages –...
  • Page 232: Calibration[1]|2:Rcalibration

    CALibration Subsystem CALibration[1]|2:RCALibration <boolean> This command enables and disables the zero/cal lockout facility. With the lockout facility enabled the power meter is stopped from making measurements until the connected sensor has been zeroed and calibrated. Syntax Space 0|OFF :RCAL 1|ON Example This command enables the zero/cal lockout CAL1:RCAL 1...
  • Page 233: Query Example

    CALibration Subsystem Query Example This command queries whether or not the CAL1:RCAL? zero/cal lockout facility is enabled for Channel A. Error Messages When CAL[1]|2:RCAL is ON and the sensor currently connected to the appropriate channel (A or B) has not been zeroed and calibrated, then any SCPI command which would normally return a measurement result (for example, FETC?, READ?, MEAS? etc) does not return a result and generates the error –230, “Data corrupt or stale;...
  • Page 234: Calibration[1]|2:Rcfactor

    CALibration Subsystem CALibration[1]|2:RCFactor <numeric_value> This command is used with 8480 Series power sensors to set the reference calibration factor of the specified channel. Reference calibration factors can also be set using sensor calibration tables. The power meter uses the most recently set reference calibration factor.
  • Page 235 CALibration Subsystem Syntax Space numeric_value :RCF Space Parameters Item Description/Defaul t Range of Values numeric_value A numeric value: 1.0 to 150.0 PCT – DEF: the default is 100 % – MIN: 1 % – MAX:150 % Example This command enters a reference calibration CAL1:RCF 98 factor of 98 % to Channel A.
  • Page 236: Query

    CALibration Subsystem Query CALibration[1]|2:RCFactor? [MIN|MAX] The query returns the current setting of the reference calibration factor or the values associated with MIN and MAX. Query Example This command queries the reference CAL2:RCF? calibration factor of Channel B. Error Messages If this command is used when a P-Series or E-Series power sensor is connected the error –241, “Hardware missing”...
  • Page 237: Calibration[1]|2:Zero:auto [Once|On|Off|0|1]

    CALibration Subsystem CALibration[1]|2:ZERO:AUTO [ONCE|ON|OFF|0|1] This command causes the power meter to perform its zeroing routine on the specified channel when enabled. This adjusts the power meter for a zero power reading with no power supplied to the power sensor. 1|ON can only be used with a P-Series sensor. When 1|ON is enabled the the zero is maintained by a combination of on-the-fly zero measurements and temperature compensation.
  • Page 238 CALibration Subsystem Query CALibration[1]|2:ZERO:AUTO? The query always returns a value of 0. Error Messages – If this command is set to ON and an 8480 Series or E-Series power sensor is connected the error –241, “Hardware missing” occurs. – If zeroing was not carried out successfully the error –231, “Data Questionable; ZERO ERROR”...
  • Page 239: Calibration[1]|2:Zero:normal:auto

    CALibration Subsystem CALibration[1]|2:ZERO:NORMal:AUTO <boolean> This command can only be used to zero a P-Series sensor. The P-Series sensor only has a NORMAL path. NOTE The command causes the power meter to perform its zeroing routine, on the specified channel, when ONCE is selected. This adjusts the power meter for a zero power reading with no power supplied to the power sensor.
  • Page 240: Query

    CALibration Subsystem Query CALibration[1]|2:ZERO:NORMal:AUTO? The query always returns a value of 0. Error Messages – If zeroing was not carried out successfully the error –231, “Data Questionable; ZERO ERROR” occurs. The error message will specify which channel failed zeroing. – If this command is set to ON the error –224, “Illegal parameter value” occurs. –...
  • Page 241 Keysight N8262A P-Series Modular Power Meter Programming Guide DISPlay Subsystem DISPlay Subsystem DISPlay:ENABle <boolean> DISPlay:SCReen:FORMat <character_data> DISPlay[:WINDow[1]|2] Commands DISPlay[:WINDow[1]|2]:ANALog Commands DISPlay[:WINDow[1]|2]:ANALog:LOWer <numeric_value> DISPlay[:WINDow[1]|2]:ANALog:UPPer <numeric_value> DISPlay[:WINDow[1]|2]:FORMat <character_data> DISPlay[:WINDow[1]|2]:METer Commands DISPlay[:WINDow[1]|2]:METer:LOWer <numeric_value> DISPlay[:WINDow[1]|2]:METer:UPPer <numeric_value> DISPlay[:WINDow[1]|2][:NUMeric[1]|2]:RESolution <numeric_value> DISPlay[:WINDow[1]|2]:SELect[1]|2 DISPlay[:WINDow[1]|2][:STATe] <boolean> DISPlay[:WINDow[1]|2]:TRACe:FEED <character_data> This chapter explains how the DISPlay subsystem is used to control the selection and presentation of the windows used on the power meter’s display.
  • Page 242 DISPlay Subsystem DISPlay Subsystem The DISPlay subsystem is used to control the selection and presentation of the windows used on the power meter’s soft front panel display. Keyword Parameter Form Notes Page DISPlay page 243 :ENABle <boolean> :SCReen page 245 :FORMat <character_data>...
  • Page 243: Display:enable

    DISPlay Subsystem DISPlay:ENABle <boolean> This command is used to enable and disable the display. At power-up the display is always enabled. Syntax Space DISP 0|OFF :ENAB 1|ON Example This command disables the display. DISP:ENAB 0 Reset Condition On reset, the display is enabled. Query DISPlay:ENABle? The query returns a 1 or 0 into the output buffer.
  • Page 244: Query Example

    DISPlay Subsystem Query Example This command queries whether the DISP:ENAB? display is on or off. Keysight N8262A Programming Guide...
  • Page 245: Display:screen:format

    DISPlay Subsystem DISPlay:SCReen:FORMat <character_data> This command sets the display format. Syntax Space DISP character_data :SCR :FORM Parameters Item Description/Defaul t Range of Values character_data Sets the display format: WIND – WINDowed: the windowed format provides two display windows. Each window can display two measurements. FSCR –...
  • Page 246: Example

    DISPlay Subsystem Example This command sets the display format to full DISP:SCReen:FORM FSCR screen. Reset Condition On reset, the display format is WIND. Query DISPlay:SCReen:FORMat? The query returns WIND, EXP or FSCR. . Query Example This command queries the display format. DISP:SCR:FORM? Keysight N8262A Programming Guide...
  • Page 247: Display[:Window[1]|2] Commands

    DISPlay Subsystem DISPlay[:WINDow[1]|2] Commands These commands control various characteristics of the display windows. WINDow1 and WINDow2 represent the upper and lower windows respectively. The following commands are detailed in this section: DISPlay[:WINDow[1]|2]:ANALog:LOWer <numeric_value> DISPlay[:WINDow[1]|2]:ANALog:UPPer <numeric_value> DISPlay[:WINDow[1]|2]:FORMat <character_data> DISPlay[:WINDow[1]|2]:METer:LOWer <numeric_value> DISPlay[:WINDow[1]|2]:METer:UPPer <numeric_value> DISPlay[:WINDow[1]|2][NUMeric[1|2]]:RESolution <numeric_value>...
  • Page 248: Display[:Window[1]|2]:Analog Commands

    DISPlay Subsystem DISPlay[:WINDow[1]|2]:ANALog Commands These commands control the upper and lower scale limits of the analog meter. The following commands are detailed in this section: DISPlay[:WINDow[1]|2]:ANALog:LOWer <numeric_value> DISPlay[:WINDow[1]|2]:ANALog:UPPer <numeric_value> Keysight N8262A Programming Guide...
  • Page 249: Table 5-1 Measurement Units

    DISPlay Subsystem DISPlay[:WINDow[1]|2]:ANALog:LOWer <numeric_value> This command sets the analog meter lower scale limit. This command has the same purpose as DISPlay[:WINDow[1]|2]:METer:LOWer NOTE <numeric_value>. The units used are dependent on the current setting of UNIT:POWer and CALCulate:RELative:STATe as shown in Table 5-1.
  • Page 250: Syntax

    DISPlay Subsystem Syntax Space numeric_value DISP :WIND :ANAL :LOW Space Parameters Item Description/Defaul t Range of Values numeric_value A numeric value for the analog meter lower scale limit: –150 to 230 dBm – DEF: the default is –70 dBm – MIN: –150 dBm –...
  • Page 251: Reset Condition

    DISPlay Subsystem Reset Condition On reset, the value is set to –70 dBm for both windows. Query DISPlay:[WINDow[1]|2]:ANALog:LOW? [MIN|MAX] The query returns the current setting of the analog meter’s lower scale limit, or the value associated with MIN or MAX. The format of the response is <NR3>. The units in which the results are returned are determined by the current setting of UNIT:POWer and CALCulate:RELative:STATe as shown in Table...
  • Page 252: Display[:Window[1]|2]:Analog:upper

    DISPlay Subsystem DISPlay[:WINDow[1]|2]:ANALog:UPPer <numeric_value> This command sets the analog meter upper scale limit. This command has the same purpose as DISPlay[:WINDow[1]|2]:METer:UPPer NOTE <numeric_value>. The units used are dependent on the current setting of UNIT:POWer and CALCulate:RELative:STATe as shown in Table 5-2.
  • Page 253 DISPlay Subsystem Syntax Space numeric_value DISP :ANAL :UPP :WIND Space Parameters Item Description/Defaul t Range of Values numeric_value A numeric value for the analog meter upper scale limit: –150 to 230 dBm – DEF: the default is 20 dBm – MIN: –150 dBm –...
  • Page 254 DISPlay Subsystem Reset Condition On reset, the upper scale limit is set to 20 dBm. Query DISPlay:[WINDow[1]|2]:ANALog:UPPer? [MIN|MAX] The query returns the current setting of the analog meter’s upper scale limit, or the value associated with MIN or MAX. The format of the response is <NR3>. The units in which the results are returned are determined by the current setting of UNIT:POWer and CALCulate:RELative:STATe as shown in Table...
  • Page 255: Display[:Window[1]|2]:Format

    DISPlay Subsystem DISPlay[:WINDow[1]|2]:FORMat <character_data> This command selects the format of the selected window. Syntax Space DISP character_data :WIND :FORM Keysight N8262A Programming Guide...
  • Page 256: Digital Display

    DISPlay Subsystem Parameters Item Description/Defaul t Range of Values character_data Sets the window format: DIGital – DIGital: sets the window display to digital. This setting is ANALog the same as SNUMeric. SNUMeric – ANALog: sets the window display to analog using the DNUMeric currently SELected measurement.
  • Page 257: Query

    DISPlay Subsystem Query DISPlay:[WINDow[1]|2]:FORMat? The query returns the current format of the selected window. Query Example This command queries the current format of DISP:FORM? the upper window. Error Messages – If the command is set to TRACe and the selected channel from which TRACe is taken has no sensor connected or has on a sensor other than a P-Series power sensor connected, error –241, “Hardware missing”...
  • Page 258: Display[:Window[1]|2]:Meter Commands

    DISPlay Subsystem DISPlay[:WINDow[1]|2]:METer Commands These commands control the upper and lower scale limits of the analog meter. The following commands are detailed in this section: DISPlay[:WINDow[1]|2]:METer:LOWer <numeric_value> DISPlay[:WINDow[1]|2]:METer:UPPer <numeric_value> Keysight N8262A Programming Guide...
  • Page 259: Table 5-3 Measurement Units

    DISPlay Subsystem DISPlay[:WINDow[1]|2]:METer:LOWer <numeric_value> This command sets the analog meter lower scale limit. This command has the same purpose as DISPlay[:WINDow[1]|2]:ANALog:LOWer NOTE <numeric_value>. The units used are dependent on the current setting of UNIT:POWer and CALCulate:RELative:STATe as shown in Table 5-3.
  • Page 260: Syntax

    DISPlay Subsystem Syntax Space numeric_value DISP :MET :LOW :WIND Space Parameters Item Description/Defaul t Range of Values numeric_value A numeric value for the analog meter lower scale limit: –150 to 230 dBm – DEF: the default is 20 dBm – MIN: –150 dBm –...
  • Page 261: Reset Condition

    DISPlay Subsystem Reset Condition On reset, the lower scale limit is set to –70 dBm. Query DISPlay[:WINDow[1]|2]:METer:LOWer? [MIN|MAX] The query returns the current setting of the analog meter’s lower scale limit or the value associated with MIN and MAX. The format of the response is <NR3>. The units in which the results are returned is dependent on the current setting of UNIT:POWer and CALCulate:RELative:STATe as shown in Table...
  • Page 262: Display[:Window[1]|2]:Meter:upper

    DISPlay Subsystem DISPlay[:WINDow[1]|2]:METer:UPPer <numeric_value> This command sets the analog meter upper scale limit. This command has the same purpose as DISPlay[:WINDow[1]|2]:ANALog:UPPer NOTE <numeric_value>. The units used are dependent on the current setting of UNIT:POWer and CALCulate:RELative:STATe as shown in Table 5-4.
  • Page 263 DISPlay Subsystem Syntax Space numeric_value DISP :WIND :MET :UPP Space Parameters Item Description/Defaul t Range of Values numeric_value A numeric value for the analog meter upper scale limit: –150 to 230 dBm – DEF: the default is 20 dBm – MIN: –150 dBm –...
  • Page 264 DISPlay Subsystem Reset Condition On reset, the upper scale limit is set to 20 dBm. Query DISPlay[:WINDow[1]|2]:METer:UPPer? [MIN|MAX] The query returns the current setting of the analog meter’s upper scale limit or the value associated with MIN and MAX. The format of the response is <NR3>. The units in which the results are returned is dependent on the current setting of UNIT:POWer and CALCulate:RELative:STATe as shown in the previous table.
  • Page 265: Display[:Window[1]|2][:Numeric[1]|2]:Resolution

    DISPlay Subsystem DISPlay[:WINDow[1]|2][:NUMeric[1]|2]:RESolution <numeric_value> This command sets the resolution of the measurement result in the specified window. Syntax Space numeric_value DISP :NUM :WIND :RES Space Parameters Item Description/Defaul t Range of Values numeric_value A numeric value for the window resolution: 1 to 4 –...
  • Page 266: Example

    DISPlay Subsystem Example This command sets the lower window’s DISP:WIND2:RES 4 resolution to four significant digits if the measurement result is linear, or to 0.001 if the measurement result is logarithmic. Reset Condition On reset, the resolution is set to 3. Query DISPlay[:WINDow[1]|2]:RESolution? [MIN|MAX] The query returns the current setting of the window’s resolution or the value...
  • Page 267: Display[:Window[1]|2]:Select[1]|2

    DISPlay Subsystem DISPlay[:WINDow[1]|2]:SELect[1]|2 This command is used to select a specific measurement within a specific window. If the second numeric value is not sent, the upper measurement of the relevant window is selected. This command is used to specify which measurement is used for the analog, trace, or single numeric display.
  • Page 268: Query

    DISPlay Subsystem Query DISPlay[:WINDow[1]|2]:SELect[1]|2? The query enters a 1 or 0 into the output buffer indicating whether the window specified is currently selected. – 1 is returned if the specified window is selected – 0 is returned if the specified window is not selected Query Example This command queries whether or not the DISP:SEL1?
  • Page 269: Display[:Window[1]|2][:State]

    DISPlay Subsystem DISPlay[:WINDow[1]|2][:STATe] <boolean> This command enables/disables the upper or lower window (WINDow1 and WINDow2 respectively) so that the display shows a single window only. The displayed window is presented in expanded format, showing a single measurement only: either the single measurement that was shown on the window, or the currently selected measurement, if two measurements had been shown.
  • Page 270 DISPlay Subsystem Query DISPlay[:WINDow[1]|2]:STATe? This enters a 1 or 0 in the output buffer indicating the selected window. – 1 is returned if the window is enabled – 0 is returned if the window is disabled Query Example This command queries whether or not the DISP:WIND2:STAT? lower window is displayed.
  • Page 271: Display[:Window[1]|2]:Trace:feed

    DISPlay Subsystem DISPlay[:WINDow[1]|2]:TRACe:FEED <character_data> This command selects which channel’s trace is displayed in the specified window. Keysight N8262A Programming Guide...
  • Page 272: Syntax

    DISPlay Subsystem Syntax Space character_data :TRAC DISP :WIND :FEED Parameters Item Description/Defaul t Range of Values character_data Identifies which channel’s trace is displayed. “SENS1” “SENS2” – SENS1: Channel A – SENS2: Channel B Example DISP:WIND2:TRAC:FEED “SENS1” This command selects Channel A’s trace to be displayed in the lower window.
  • Page 273: Reset Condition

    DISPlay Subsystem Reset Condition On reset, the value is set to: – Upper window: SENS1 – Lower window (dual channel only): SENS2 Query DISPlay:[WINDow[1]|2]:TRACe:FEED? The query returns the channel of the trace currently displayed in the specified window. Query Example This command queries the channel of the DISP:WIND2:TRAC:FEED? trace currently displayed in the lower...
  • Page 274 DISPlay Subsystem THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK. Keysight N8262A Programming Guide...
  • Page 275 Keysight N8262A P-Series Modular Power Meter Programming Guide FORMat Subsystem FORMat Subsystem FORMat[:READings]:BORDer <character_data> FORMat[:READings][:DATA] <character_data> This chapter explains how the FORMat subsystem is used to set a data format for transferring numeric information.
  • Page 276: Format Subsystem

    FORMat Subsystem FORMat Subsystem The FORMat subsystem sets a data format for transferring numeric information. This data format is used only for response data by commands that are affected by the FORMat subsystem. The queries affected are: – FETCh? – READ? –...
  • Page 277: Format[:Readings]:Border

    FORMat Subsystem FORMat[:READings]:BORDer <character_data> This command controls whether the binary data is transferred in normal or swapped Byte ORDer. It is only used when FORMat[:READings][:DATA] is set to REAL. Syntax Space character_data FORM :READ :BORD Parameters Item Description/Defaul t Range of Values character_data Byte order of binary data transfer: NORMal...
  • Page 278: Query

    FORMat Subsystem Query FORMat[:READings]:BORDer? The query returns the current setting of the byte order. The format of the response is NORMalor SWAPped.. Query Example This command queries the current byte order FORM:BORD? setting. Keysight N8262A Programming Guide...
  • Page 279: Format[:Readings][:Data]

    FORMat Subsystem FORMat[:READings][:DATA] <character_data> This command sets the data format for transferring numeric information to either ASCii or REAL: – When the format type is ASCii, numeric data is output as ASCII bytes in the <NR3> format. – When the format type is REAL, numeric data is output as IEEE 754 64 bit floating point numbers in a definite length block.
  • Page 280: Example

    FORMat Subsystem Example This command sets the format to REAL. FORM REAL Reset Condition On reset, the format is set to ASCii. Query FORMat[:READings][:DATA]? The query returns the current setting of format: either ASCii or REAL. Query Example This command queries the current format FORM? setting.
  • Page 281 Keysight N8262A P-Series Modular Power Meter Programming Guide MEMory Subsystem MEMory Subsystem MEMory:CATalog Commands MEMory:CATalog[:ALL]? MEMory:CATalog:STATe? MEMory:CATalog:TABLe? MEMory:CLEar Commands MEMory:CLEar[:NAME] <character_data> MEMory:CLEar:TABle MEMory:FREE Commands MEMory:FREE[:ALL]? MEMory:FREE:STATe? MEMory:FREE:TABLe? MEMory:NSTates? MEMory:STATe Commands MEMory:STATe:CATalog? MEMory:STATe:DEFine <character_data>,<numeric_value> MEMory:TABLe Commands MEMory:TABLe:FREQuency <numeric_value>{,<numeric_value>} MEMory:TABLe:FREQuency:POINts? MEMory:TABLe:GAIN[:MAGNitude] <numeric_value>{,<numeric_value>} MEMory:TABLe:GAIN[:MAGNitude]:POINts? MEMory:TABLe:MOVE <character_data>,<character_data>...
  • Page 282 MEMory Subsystem MEMory Subsystem The MEMory command subsystem is used to: – Edit and review sensor calibration tables (8480 Series sensors only) – Store sensor calibration tables (8480 Series sensors only) – Edit and review sensor frequency dependent offset tables –...
  • Page 283 MEMory Subsystem Keyword Parameter Form Notes Page [query only] page 298 :TABLe? [query only] page 299 :NSTates? :STATe [query only] page 301 :CATalog? [non-SCPI] page 302 :DEFine <character_data> [,<numeric_value>] :TABLe page 305 :FREQuency <numeric_value> [,<numeric_value>] [query only] page 308 :POINts? :GAIN [non-SCPI] page 309...
  • Page 284: Memory:catalog Commands

    MEMory Subsystem MEMory:CATalog Commands These commands are used to query information on the current contents of a power meter’s: – Sensor calibration tables (8480 Series sensors only) – Frequency dependent offset tables – Save/recall registers The following commands are detailed in this section: MEMory:CATalog[:ALL]? MEMory:CATalog:STATe? MEMory:CATalog:TABLe?
  • Page 285: Memory:catalog[:All]

    The power meter is shipped with a set of predefined sensor calibration tables. The data in these sensor calibration tables is based on statistical averages for a range of Keysight Technologies power sensors. These tables can be edited. The predefined data is listed in your User’s Guide. These power sensors and table...
  • Page 286: Syntax

    MEMory Subsystem Table 7-1 8480 Series power sensor tables Table Power Sensor Table Name None DEFAULT 8481A 8481A 8482A, 8482B, 8482H 8482A 8483A 8483A 8481D 8481D 8485A 8485A R8486A R8486A Q8486A Q8486A R8486D R8486D 8487A 8487A [a] There are also ten sensor calibration tables named CUSTOM_0 through CUSTOM_9 and ten frequency dependent offset tables named CUSTOM _A through CUSTOM _J which do not contain any data when the power meter is shipped from the factory.
  • Page 287: Memory:catalog:state

    MEMory Subsystem MEMory:CATalog:STATe? This command is used to list the save/recall registers. The power meter returns the data in the form of two numeric parameters and as many strings as there are save/recall registers. <numeric_value>,<numeric_value>{,<string>} – The first numeric parameter indicates the amount of memory, in bytes, used for the storage of registers.
  • Page 288: Memory:catalog:table

    The power meter is shipped with a set of predefined sensor calibration tables. The data in these sensor calibration tables is based on statistical averages for a range of Keysight Technologies power sensors. These tables can be edited. The predefined data is listed in your User’s Guide. These power sensors and table...
  • Page 289 MEMory Subsystem Table 7-2 8480 Series power sensor tables Table Power Sensor Table Name None DEFAULT 8481A 8481A 8482A, 8482B, 8482H 8482A 8483A 8483A 8481D 8481D 8485A 8485A R8486A R8486A Q8486A Q8486A R8486D R8486D 8487A 8487A [a] Default is a sensor calibration table in which the reference calibration factor and calibration factors are 100%. This sensor calibration table can be used during the performance testing of the power meter There are also ten sensor calibration tables named CUSTOM_0 through CUSTOM_9 and ten frequency dependent offset tables named CUSTOM_A...
  • Page 290 MEMory Subsystem Syntax :CAT :TABL Example This command queries the list of stored MEM:CAT:TABL? tables. Keysight N8262A Programming Guide...
  • Page 291: Memory:clear Commands

    MEMory Subsystem MEMory:CLEar Commands These commands are used to remove the contents stored in the sensor calibration tables (8480 Series sensors only), frequency dependent offset tables and save/ recall registers. This subsystem removes the data contents but does not affect the name of the associated table or save/recall register.
  • Page 292: Memory:clear[:Name]

    MEMory Subsystem MEMory:CLEar[:NAME] <character_data> This command clears the contents of a specified sensor calibration table (8480 Series sensors only), frequency dependent offset table, or save/recall register. Although the table remains, a MEMory:TABLe:FREQuency|GAIN:POINts? query returns a 0 as there are no contents in the table. For sensor calibration tables and frequency dependent offset tables, this command is an alternative form of the MEMory:CLEar:TABLE command, the only difference being the method in which the table is selected.
  • Page 293: Syntax

    MEMory Subsystem Syntax character_data Space :CLE :NAME Parameters Item Description/Defaul t Range of Values character_data Contains an existing table name or save/recall Any existing table name or save/recall register. register. Example This command clears the contents of sensor MEM:CLE "8485A" calibration table 8485A.
  • Page 294: Memory:clear:table

    MEMory Subsystem MEMory:CLEar:TABle This command is used to clear the contents of the table currently selected using MEMory:TABLe:SELect. Although the table remains, a MEMory:TABLe:FREQuency|GAIN:POINts? query returns a 0 as the table contents are empty. This command is an alternative form of the MEMory:CLEar[:NAME] command. The difference is the method in which the table is selected.
  • Page 295: Memory:free Commands

    MEMory Subsystem MEMory:FREE Commands These commands are used to return information on the amount of free memory space available for sensor calibration tables (8480 Series sensors only), frequency dependent offset tables, and save/recall registers. The following commands are described in this section: MEMory:FREE[:ALL]? MEMory:FREE:STATe? MEMory:FREE:TABLe?
  • Page 296: Memory:free[:All]

    MEMory Subsystem MEMory:FREE[:ALL]? This query returns the amount of memory free for sensor calibration tables (8480 Series sensors only), frequency dependent offset tables, and save/recall registers. The format of the response is: <bytes_available>,<bytes_in_use> Syntax :FREE :ALL Example This command queries the amount of free MEM:FREE? memory in total.
  • Page 297: Memory:free:state

    MEMory Subsystem MEMory:FREE:STATe? This query returns the amount of memory free for save/recall registers. The format of the response is: <bytes_available>,<bytes_in_use> Syntax :FREE :STAT Example This command queries the amount of free MEM:FREE:STAT? memory for save/recall registers. Keysight N8262A Programming Guide...
  • Page 298: Memory:free:table

    MEMory Subsystem MEMory:FREE:TABLe? This query returns the amount of memory free for sensor calibration tables (8480 Series sensors only) and frequency dependent offset tables. The format of the response is: <bytes_available>,<bytes_in_use> Syntax :FREE :TABL Example This command queries the amount of free MEM:FREE:TABL? memory for tables.
  • Page 299: Memory:nstates

    MEMory Subsystem MEMory:NSTates? This query returns the number of registers that are available for save/recall. As there are ten registers this query always returns ten. Syntax :NST Example This command queries the number of MEM:NST? registers available for save/recall. Keysight N8262A Programming Guide...
  • Page 300: Memory:state Commands

    MEMory Subsystem MEMory:STATe Commands These commands are used to query and define register names. The following commands are described in this section: MEMory:STATe:CATalog? MEMory:STATe:DEFine Keysight N8262A Programming Guide...
  • Page 301: Memory:state:catalog

    MEMory Subsystem MEMory:STATe:CATalog? This query returns a list of the save/recall register names in ascending order of register number. The format of the response is: <string>,<string>,..,<string> Syntax :STAT :CAT Example This command queries the register names. MEM:STAT:CAT? Keysight N8262A Programming Guide...
  • Page 302: Memory:state:define ,

    MEMory Subsystem MEMory:STATe:DEFine <character_data>,<numeric_value> This command is used to associate a name with a save/recall register number. Syntax character_data Space numeric_value :DEF :STAT Space character_data Parameters Item Description/Defaul t Range of Values character_data Details the register name. A maximum of 12 characters can be A to Z (uppercase) used.
  • Page 303: Query Example

    MEMory Subsystem Query Example This command queries the register number MEM:STAT:DEF? "SETUP1" of SETUP1. Error Messages – If the register number is out of range, error –222, “Data out of range” occurs. – If the name is invalid, error –224, “Illegal parameter value” occurs. –...
  • Page 304: Memory:table Commands

    MEMory Subsystem MEMory:TABLe Commands These commands are used to define a sensor calibration table (8480 Series sensors only) or a frequency dependent offset table, and to write to and read data from it. The following commands are described in this section: MEMory:TABLe:FREQuency <numeric_value>{,<numeric_value>} MEMory:TABLe:FREQuency:POINts? MEMory:TABLe:GAIN[:MAGNitude]...
  • Page 305: Memory:table:frequency {,}

    MEMory Subsystem MEMory:TABLe:FREQuency <numeric_value>{,<numeric_value>} This command is used to enter frequency data into the current selected table. Any previous frequency list is cleared before the new frequency list is stored. The frequencies must be entered in ascending order. Entries in the frequency lists correspond as shown in Table 7-3 with entries in the calibration/offset factor lists.
  • Page 306: Syntax

    MEMory Subsystem For sensosr calibration tables (8480 Series sensors only), the number of frequency points must be one less than the number of calibration factor points. This is verified when the sensor calibration table is selected using SENSe:CORRection:CSET:SELect <string>. Ensure that the frequency points you use cover the frequency range of the signals that you want to measure.
  • Page 307: Example

    MEMory Subsystem Example This command enters frequencies of 200 kHz MEM:TABL:FREQ 200kHz,600kHz and 600 kHz into the currently selected table. Query MEMory:TABLe:FREQuency? The query returns a list of frequency points for the table currently selected. The frequencies are returned in Hz. Query Example This command queries the frequency points MEM:TABL:FREQ?
  • Page 308: Memory:table:frequency:points

    MEMory Subsystem MEMory:TABLe:FREQuency:POINts? This query returns the number of frequency points for the table currently selected. The response format is <NRf>. If no frequency values have been set, this command returns 0. If no table is selected, this command returns NAN. Syntax :TABL :FREQ...
  • Page 309: Table 7-4 Frequency And Calibration/Offset Factor List

    MEMory Subsystem MEMory:TABLe:GAIN[:MAGNitude] <numeric_value>{,<numeric_value>} This command is used to enter calibration factors into the sensor calibration table (8480 Series sensors only) or offsets into the frequency dependent offset table, currently selected using MEMory:TABLe:SELect. Any previous calibration factor list, or offset list is cleared before the new calibration factors/offsets are stored. A maximum of 81 parameters for sensor calibration tables and 80 parameters for frequency dependent offset tables can be sent with this command.
  • Page 310 MEMory Subsystem Syntax Space :GAIN numeric_value :TABL :MAGN Parameters Item Description/Defaul t Range of Values numeric_value A numeric value for the calibration/ offset factors. The units 1.0 to 150.0 are PCT. Example This command enters a reference calibration MEM:TABL:SEL "Sensor_1" factor of 97 % and calibration factors of 99.5 MEM:TABL:GAIN 97,99.5,97.4 % and 97.4 % into the sensor calibration...
  • Page 311: Query Example

    MEMory Subsystem Query Example This command queries the calibration factor/ MEM:TABL:GAIN? offset in the current table. Error Messages – If more than 81 calibration factors for sensor calibration tables, or 80 offsets for frequency dependent offset tables are in the list, error –108, “Parameter not allowed”...
  • Page 312: Memory:table:gain[:Magnitude]:Points

    MEMory Subsystem MEMory:TABLe:GAIN[:MAGNitude]:POINts? This query is used to return the number of calibration factor/offset points for the currently selected table. If the currently selected table is a sensor calibration table (8480 Series sensors only), the reference calibration factor is included If no values have been set, 0 is returned.
  • Page 313: Memory:table:move ,

    MEMory Subsystem MEMory:TABLe:MOVE <character_data>,<character_data> This command is used to rename a sensor calibration table (8480 Series Sensors only) or a frequency dependent offset table. Syntax character_data Space character_data :MOVE :TABL Parameters Item Description/Defaul t Range of Values character_data Contains the existing table name. existing table name (1st parameter) character_data...
  • Page 314: Memory:table:select

    MEMory Subsystem MEMory:TABLe:SELect <character_data> This command is used to activate either a sensor calibration table (8480 Series sensors only), or a frequency dependent offset table. A table must be activated before any operation can be performed on it. Syntax character_data Space :TABL :SEL...
  • Page 315: Output Subsystem

    Keysight N8262A P-Series Modular Power Meter Programming Guide OUTPut Subsystem OUTPut Subsystem OUTPut:RECorder[1]|2:FEED <data_handle> OUTPut:RECorder[1]|2:LIMit:LOWer <numeric_value> OUTPut:RECorder[1]|2:LIMit:UPPer <numeric_value> OUTPut:RECorder[1]|2:STATe <boolean> OUTPut:ROSCillator[:STATe] <boolean> OUTPut:TRIGger[:STATe] <boolean> This chapter explains how the OUTPut command subsystem is used to switch the POWER REF output on and off.
  • Page 316 OUTPut Subsystem OUTPut Subsystem The OUTPut command subsystem is used to control the trigger output, switch on and off the POWER REF output, and controls the recorder output. Keyword Parameter Form Notes Page OUTPut :RECorder[1]|2 page 317 :FEED <data_handle> :LIMit page 319 :LOWer <numeric_value>...
  • Page 317: Output:recorder[1]|2:Feed

    OUTPut Subsystem OUTPut:RECorder[1]|2:FEED <data_handle> This command specifies which measurement is sent to the recorder output specified by the numeric value following RECorder, RECorder1 and RECorder2. Syntax Space data_handle OUTP :REC :FEED Parameters Item Description/Defaul t Range of Values data_handle The CALC block specifying the measurement to be sent to “CALC1”...
  • Page 318: Query

    OUTPut Subsystem Query OUTPut:RECorder[1]|2:FEED? The query command returns the current value of data_handle. Query Example This command queries the value of OUTP:REC2:FEED? data_handle for recorder output 2. Keysight N8262A Programming Guide...
  • Page 319: Output:recorder[1]|2:Limit:lower

    OUTPut Subsystem OUTPut:RECorder[1]|2:LIMit:LOWer <numeric_value> This command sets the minimum scaling value for the specified recorder output. The units used are dependent on the units currently set for the CALC block specified in OUTPut:RECorder[1]|2:FEED <data_handle>. Syntax Space numeric_value :LOW :LIM OUTP :REC Parameters Item...
  • Page 320 OUTPut Subsystem Query OUTPut:RECorder[1]|2:LIMit:LOWer? The query command returns the minimum scaling value. Query Example This command returns the minimum scaling OUTP:REC:LIM:LOW? value for the specified recorder output. Keysight N8262A Programming Guide...
  • Page 321: Output:recorder[1]|2:Limit:upper

    OUTPut Subsystem OUTPut:RECorder[1]|2:LIMit:UPPer <numeric_value> This command sets the maximum scaling value for the specified recorder output. The units used are dependent on the units currently set for the CALC block specified in OUTPut:RECorder[1]|2:FEED <data_handle>. Syntax numeric_value Space :LIM :UPP OUTP :REC Parameters Item...
  • Page 322 OUTPut Subsystem Query OUTPut:RECorder[1]|2:LIMit:UPPer? The query command returns the maximum scaling value. Query Example This command returns the maximum scaling OUTP:REC:LIM:UPP? value for the specified recorder output. Keysight N8262A Programming Guide...
  • Page 323: Output:recorder[1]|2:State

    OUTPut Subsystem OUTPut:RECorder[1]|2:STATe <boolean> This command enables or disables the specified recorder output. Syntax Space :STAT 0|OFF OUTP :REC 1|ON Example This command enables the specified OUTP:REC1:STAT 1 recorder output. Reset Condition On reset, the recorder output is OFF. Query OUTPut:RECorder[1]|2:STATe? The query command enters a 1 or 0 into the output buffer indicating whether or not the specified recorder is switched on.
  • Page 324: Output:roscillator[:State]

    OUTPut Subsystem OUTPut:ROSCillator[:STATe] <boolean> This command enables/disables the POWER REF output. Syntax Space OUTP :ROSC :STAT 0|OFF 1|ON Example This command enables the POWER REF OUTP:ROSC:STAT 1) output. Reset Condition On reset, the POWER REF output is disabled. Query OUTPut:ROSCillator[:STATe]? The query command enters a 1 or 0 into the output buffer indicating whether or not the POWER REF is enabled.
  • Page 325: Output:trigger[:State]

    OUTPut Subsystem OUTPut:TRIGger[:STATe] <boolean> This command enables/disables the trigger output signal. Syntax Space OUTP :STAT :TRIG 0|OFF 1|ON Example This command enables the trigger output OUTP:TRIG:STAT 1 signal. Reset Condition On reset, the trigger output signal is disabled. Query OUTPut:TRIGger[:STATe]? The query command enters a 1 or 0 into the output buffer indicating whether or not the trigger output signal is enabled/disabled.
  • Page 326 OUTPut Subsystem THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK. Keysight N8262A Programming Guide...
  • Page 327 Keysight N8262A P-Series Modular Power Meter Programming Guide PSTatistic Subsystem PSTatistic[1]|2:CCDF:DATa? PSTatistic[1]|2:CCDF:DATa:MAX <numeric_value> PSTatistic[1]|2:CCDF:POWer? <numeric_value> PSTatistic[1]|2:CCDF:PROBability? <numeric_value> PSTatistic[1]|2:CCDF:TABle? Chapter 9 explains how the PSTatistic command subsystem is used to configure the settings of Complementary Cumulative Distribution Function (CCDF).
  • Page 328: Pstatistic Subsystem

    PSTatistic Subsystem PSTatistic Subsystem The PSTatistic subsystem is used to configure the settings of Complementary Cumulative Distribution Function (CCDF). Keyword Parameter Form Notes Page PSTatistic[1]|2 :CCDF [query only] page 329 :DATa? page 331 :MAX <numeric_value> [query only] page 333 :POWer? <numeric_value>...
  • Page 329: Pstatistic[1]|2:Ccdf:data

    PSTatistic Subsystem PSTatistic[1]|2:CCDF:DATa? This command is used to return 501 probability values in % at different power level within certain range, starts from 0 dB till the predefined maximum power level. The maximum power level can be set by using this command: NOTE PSTatistic[1]|2:CCDF:DATa:MAX <numeric_value>...
  • Page 330: Error Messages

    PSTatistic Subsystem Error Messages – If no power sensor is connected, error –241 "Hardware missing" occurs. – If sensor/s connected are not P-Series sensors, error –241 "Hardware missing" occurs. – If measurement speed setting is FAST, error –221 "Settings conflict" occurs. –...
  • Page 331: Pstatistic[1]|2:Ccdf:data:max

    PSTatistic Subsystem PSTatistic[1]|2:CCDF:DATa:MAX <numeric_value> This command is used to set the maximum value of X-axis CCDF trace. Syntax :CCDF :DAT numeric_value :MAX Parameters Item Description/Defaul t Range of Values numeric_value X-axis CCDF trace maximum value in dB. 5.00 to 50.00 –...
  • Page 332: Query

    PSTatistic Subsystem Query PSTatistic[1]|2:CCDF:DATa:MAX? The query returns the X-axis CCDF trace maximum value. Query Example This command queries the maximum value of PST1:CCDF:DAT:MAX? X-axis CCDF trace for Channel A. Error Messages – If the parameter set is less than 5.0, error –222 "Data out of range; value clipped to lower limit"...
  • Page 333: Pstatistic[1]|2:Ccdf:power?

    PSTatistic Subsystem PSTatistic[1]|2:CCDF:POWer? <numeric_value> This command is used to return the power level at the specified probability. This command is only applicable when P-Series sensors are present and the NOTE following conditions are met: – Free run acquisition mode is selected –...
  • Page 334 PSTatistic Subsystem Error Messages – If no power sensor is connected, error –241 "Hardware missing" occurs. – If sensor/sensors connected are not P-Series sensors, error –241 "Hardware missing" occurs. – If measurement speed setting is FAST, error –221 "Settings conflict" occurs. –...
  • Page 335: Pstatistic[1]|2:Ccdf:probability?

    PSTatistic Subsystem PSTatistic[1]|2:CCDF:PROBability? <numeric_value> This command is used to return the probability at the specified power level. This command is only applicable when P-Series sensors are present and the NOTE following conditions are met: – Free run acquisition mode is selected –...
  • Page 336: Example

    PSTatistic Subsystem Example This command queries the probability at the PST1:CCDF:PROB? 50 power level of 50dB for Channel A. Error Messages – If no power sensor is connected, error –241 "Hardware missing" occurs. – If sensor/sensors connected are not P-Series sensors, error –241 "Hardware missing"...
  • Page 337: Pstatistic[1]|2:Ccdf:table

    PSTatistic Subsystem PSTatistic[1]|2:CCDF:TABle? This command is used to return the data in CCDF table, average input power, probability at the average input power, peak to average power ratio and sample count. This command will return 10 scalar results in the following order: NOTE 1 Average input power (in dBm) 2 Probability at the average input power (in %)
  • Page 338: Syntax

    PSTatistic Subsystem Syntax :CCDF :TAB Example This command returns the data in CCDF table: PST:CCDF:TAB? average input power, probabilty at the average input power, power level at various predefined probability steps (10 %, 1 %, 0.1 %, 0.01 %, 0.001 % and 0.0001 %), peak to average power ratio and sample count for Channel A.
  • Page 339: Error Messages

    PSTatistic Subsystem Error Messages – If no power sensor is connected, error –241 "Hardware missing" occurs. – If sensor/sensors connected are not P-Series sensors, error –241 "Hardware missing" occurs. – If measurement speed setting is FAST, error –221 "Settings conflict" occurs. –...
  • Page 340 PSTatistic Subsystem THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK. Keysight N8262A Programming Guide...
  • Page 341 Keysight N8262A P-Series Modular Power Meter Programming Guide SENSe Subsystem [SENSe] Subsystem [SENSe[1]]|SENSe2:AVERage Commands [SENSe[1]]|SENSe2:AVERage:COUNt <numeric_value> [SENSe[1]]|SENSe2:AVERage:COUNt:AUTO <boolean> [SENSe[1]]|SENSe2:AVERage:SDETect <boolean> [SENSe[1]]|SENSe2:AVERage[:STATe] <boolean> [SENSe[1]]|SENSe2:AVERage2 Commands [SENSe[1]]|SENSe2:AVERage2:COUNt <numeric_value> [SENSe[1]]|SENSe2:AVERage2[:STATe] <boolean> [SENSe[1]]|SENSe2:BANDwidth|BWIDth:VIDeo <character_data> [SENSe[1]]|SENSe2:CORRection Commands [SENSe[1]]|SENSe2:CORRection:CFACtor|GAIN[1][:INPut] [:MAGNitude] <numeric_value> [SENSe[1]]|SENSe2:CORRection:CSET[1]|CSET2 Commands [SENSe[1]]|SENSe2:CORRection:CSET[1]|CSET2[:SELect] <string> [SENSe[1]]|SENSe2:CORRection:CSET[1]|CSET2:STATe <boolean> [SENSe[1]]|SENSe2:CORRection:DCYCle|GAIN3 Commands [SENSe[1]]|SENSe2:CORRection:DCYCle|GAIN3[:INPut] [:MAGNitude] <numeric_value>...
  • Page 342 SENSe Subsystem [SENSe[1]]|SENSe2:POWer:AC:RANGe:AUTO <boolean> [SENSe[1]]|SENSe2:SWEep[1]|2|3|4 Commands [SENSe[1]]|SENSe2:SWEep[1]|2|3|4:OFFSet:TIME <numeric_value> [SENSe[1]]|SENSe2:SWEep[1]|2|3|4:TIME <numeric_value> [SENSe[1]]|SENSe2:TEMPerature? [SENSe[1]]|SENSe2:TRACe Commands [SENSe[1]]|SENSe2:TRACe:OFFSet:TIME <numeric_value> [SENSe[1]]|SENSe2:TRACe:TIME <numeric_value> [SENSe[1]]|SENSe2:TRACe:UNIT <character_data> [SENSe[1]]|SENSe2:V2P ATYPe|DTYPe SENSe[1]|2:TRACe:LIMit:LOWer <numeric_value> SENSe[1]|2:TRACe:LIMit:UPPer <numeric_value> SENSe[1]|2:TRACe:X:SCALe:PDIV <numeric_value> SENSe[1]|2:TRACe:Y:SCALe:PDIV <numeric_value> This chapter explains how the SENSe command subsystem directly affects device specific settings used to make measurements.
  • Page 343: Sense] Subsystem

    SENSe Subsystem [SENSe] Subsystem The SENSe command subsystem directly affects device specific settings used to make measurements. The SENSe subsystem is optional since this is the primary function of the power meter. The high level command CONFigure uses the SENSe commands to prepare the p ower meter for making measurements.
  • Page 344 SENSe Subsystem Keyword Parameter Form Notes Page :CSET[1]|CSET2 page 369 [:SELect] <string> page 371 :STATe <boolean> [non-SCPI] :DCYCle|GAIN3 [:INPut] page 374 [:MAGNitude] <numeric_value> page 377 :STATe <boolean> :FDOFfset|GAIN4 [:INPut] [query only] page 379 [:MAGNitude] :GAIN2 page 381 :STATe <boolean> [:INPut] page 383 [:MAGNitude] <numeric_value>...
  • Page 345 SENSe Subsystem Keyword Parameter Form Notes Page :OFFSet page 402 :TIME <numeric_value> page 404 :TIME <numeric_value> page 406 :UNIT <character_data> [non-SCPI] page 408 :V2P ATYPe|DTYPe SENSe[1]|2 :TRACe :LIMit page 410 :LOWer <numeric_value> page 412 :UPPer <numeric_value> :SCALe page 414 :PDIV <numeric_value>...
  • Page 346 SENSe Subsystem [SENSe[1]]|SENSe2:AVERage Commands These commands control the measurement averaging which is used to improve measurement accuracy. They combine successive measurements to produce a new composite result. The following commands are detailed in this section: [SENSe[1]]|SENSe2:AVERage:COUNt <numeric_value> [SENSe[1]]|SENSe2:AVERage:COUNt:AUTO <boolean> [SENSe[1]]|SENSe2:AVERage:SDETect <boolean> [SENSe[1]]|SENSe2:AVERage[:STATe] <boolean>...
  • Page 347 SENSe Subsystem [SENSe[1]]|SENSe2:AVERage:COUNt <numeric_value> This command is used to enter a value for the filter length. If [SENSe[1]]|SENSe2:AVERage:COUNt:AUTO is set to ON then entering a value for the filter length automatically sets it to OFF. Increasing the value of filter length increases measurement accuracy but also increases the time taken to make a power measurement.
  • Page 348: Syntax

    SENSe Subsystem Syntax Space :COUN numeric_value SENS AVER SENS2 Space Parameters Item Description/Defaul t Range of Values numeric_value A numeric value defining the filter length. 1 to 1024 DEF: the default value is 4 MIN: 1 MAX: 1024 Example This command enters a filter length of 400 AVER:COUN 400 for Channel A.
  • Page 349: Query

    SENSe Subsystem Query AVERage:COUNt? [MIN|MAX] The query returns the current setting of the filter length or the values associated with MIN and MAX. The format of the response is <NR1>. Query Example This command queries the filter length for AVER:COUN? Channel A.
  • Page 350: Figure 10-1 Example Of Averaged Readings

    SENSe Subsystem [SENSe[1]]|SENSe2:AVERage:COUNt:AUTO <boolean> This command enables and disables automatic averaging. ONCE has no affect on the power meter. When the auto filter mode is enabled, the power meter automatically sets the number of readings averaged together to satisfy the averaging requirements for most power measurements.
  • Page 351 SENSe Subsystem For most applications, automatic filter length selection NOTE ([SENSe[1]]|SENSe2:AVERage:COUNt:AUTO ON) is the best mode of operation. However, manual filter length selection ([SENSe[1]]|SENSe2:AVERage:COUNt <numeric_value>) is useful in applications requiring either high resolution or fast settling times, where signal variations rather than measurement noise need filtering, or when approximate results are needed quickly.
  • Page 352: Query Example

    SENSe Subsystem Query Example This command queries whether automatic filter AVER:COUN:AUTO? length selection is on or off for Channel A. Error Messages If [SENSe[1]]|SENSe2:AVERage:COUNt:AUTO is set to ON while [SENSe[1]]|SENSe2:SPEed is set to 200, the error –221, “Settings Conflict” occurs. However, automatic averaging is enabled but the [SENSe[1]]|SENSe2:AVERage:STATe command is not automatically set ON.
  • Page 353 SENSe Subsystem [SENSe[1]]|SENSe2:AVERage:SDETect <boolean> This command enables and disables step detection. In AUTO filter mode, the average of the last four values entered into the filter is compared to the average of the entire filter. If the difference between the two averages is greater than 12.5%, the digital filter is cleared.
  • Page 354: Syntax

    SENSe Subsystem Syntax Space SENS :SDET 0|OFF AVER 1|ON SENS2 Example This command disables step detection. SENS:AVER:SDET OFF Reset Condition On reset, step detection is enabled. Query [SENSe[1]]|SENSe2:AVERage:SDETect? The query enters a 1 or 0 into the output buffer indicating the status of step detection.
  • Page 355 SENSe Subsystem [SENSe[1]]|SENSe2:AVERage[:STATe] <boolean> This command is used to enable and disable averaging. Syntax Space SENS AVER :STAT 0|OFF 1|ON SENS2 Example This command enables averaging on AVER 1 Channel A. Reset Condition On reset, averaging is OFF. Query [SENSe[1]]|SENSe2:AVERage[:STATe]? The query enters a 1 or 0 into the output buffer indicating the status of averaging.
  • Page 356 SENSe Subsystem Query Example This command queries whether averaging is SENS2:AVER? on or off for Channel B. Error Messages If [SENSe[1]]|SENSe2:AVERage:STATe is set to ON while [SENSe[1]]|SENSe2:SPEed is set to 200, the error –221, “Settings Conflict” occurs. Keysight N8262A Programming Guide...
  • Page 357 SENSe Subsystem [SENSe[1]]|SENSe2:AVERage2 Commands These commands control video averaging, which is used to improve measurement accuracy, for the P-Series power sensor. They combine successive measurements to produce a new composite result. If the command is used when a sensor other than a P-Series power sensor is NOTE connected, error –241, “Hardware missing”...
  • Page 358 SENSe Subsystem [SENSe[1]]|SENSe2:AVERage2:COUNt <numeric_value> This command is used to enter the video filter length for the P-Series sensor. Video filtering is applied to the traces. Successive traces are combined to reduce noise without affecting the dynamic characteristic of the signal. Syntax Space SENS...
  • Page 359: Query

    SENSe Subsystem Query AVERage2:COUNt? The query returns the current setting of the video filter length. The format of the response is <NR1>. Query Example This command queries the video filter length AVER2:COUN? for Channel A. Error Messages – If the command is used when a sensor other than a P-Series power sensor is connected, error –241, “Hardware missing”...
  • Page 360 SENSe Subsystem [SENSe[1]]|SENSe2:AVERage2[:STATe] <boolean> This command is used to enable and disable video averaging for the P-Series sensor. Syntax Space SENS AVER2 :STAT 0|OFF 1|ON SENS2 Example This command enables video averaging on AVER2 1 Channel A. Reset Condition On reset, averaging is enabled. Query [SENSe[1]]|SENSe2:AVERage2[:STATe]? The query enters a 1 or 0 into the output buffer indicating the status of averaging.
  • Page 361: Query Example

    SENSe Subsystem Query Example This command queries whether averaging is SENS2:AVER2? on or off for Channel B. Error Messages – If the command is used when a sensor other than a P-Series power sensor is connected, error –241, “Hardware missing” occurs Keysight N8262A Programming Guide...
  • Page 362 SENSe Subsystem [SENSe[1]]|SENSe2:BANDwidth|BWIDth:VIDeo <character_data> This command sets the sensor bandwidth on a P-Series sensor. Syntax Space character_data SENS BAND :VID BWID SENS2 Parameters Item Description/Defaul t Range of Values character_data Defines the sensor bandwidth. HIGH MEDium Example This command sets sensor bandwidth to SENSe1:BAND:VID HIGH high for Channel A.
  • Page 363 SENSe Subsystem Query [SENSe[1]]|SENSe2:BANDwidth|BWIDth:VIDeo? The query returns the current sensor bandwidth setting. Query Example This command queries the current sensor SENS2:BAND:VID? bandwidth setting for Channel B. Error Messages – If the command is used when a sensor other than a P-Series power sensor is connected, error –241, “Hardware missing”...
  • Page 364 SENSe Subsystem [SENSe[1]]|SENSe2:CORRection Commands These commands provide for changes to be applied to the measurement result. They are used to enter duty cycle values, calibration factors and other external gains and losses. The following commands are detailed in this section: [SENSe[1]]|SENSe2:CORRection:CFACtor|GAIN[1][:INPut] [:MAGNitude] <numeric_value>...
  • Page 365 SENSe Subsystem [SENSe[1]]|SENSe2:CORRection:CFACtor|GAIN[1][:INPut] [:MAGNitude] <numeric_value> This command is used to enter a gain correction value for the calibration factor. The power meter corrects every measurement by this factor to compensate for the gain. Either CFACtor and GAIN1 can be used in the command—both have an identical result.
  • Page 366: Parameters

    SENSe Subsystem Parameters Item Description/Defaul t Range of Values numeric_value A numeric value. 1 to 150 PCT (for CFACtor and GAIN1) – DEF: the default value is 100 % – MIN: 1 % – MAX: 150 % [a] For example, a gain of 60 % corresponds to a multiplier of 0.6 and a gain of 150 % corresponds to a multiplier of 1.5. Example This command sets a gain correction of SENS2:CORR:GAIN1...
  • Page 367: Query Example

    SENSe Subsystem Query Example This command queries the current CORR:GAIN1? calibration factor setting for Channel A. Error Messages The SENSe[1]]|SENSe2:CORRection:CFACtor|GAIN1 command can be used for the 8480 Series Power Sensor when no sensor calibration table has been set up. If a sensor calibration table is selected the error –221, “Settings Conflict”...
  • Page 368 SENSe Subsystem [SENSe[1]]|SENSe2:CORRection:CSET[1]|CSET2 Commands These commands are used to select the active sensor calibration table (using CSET1) and the active frequency dependent offset table (using CSET2). If any of the CSET1 commands are used when a P-Series or E-Series power NOTE sensor is connected, the error –241, “Hardware missing”...
  • Page 369 SENSe Subsystem [SENSe[1]]|SENSe2:CORRection:CSET[1]|CSET2[:SELect] <string> This command enters the name of the sensor calibration table or frequency dependent offset table which is to be used. The CSET1 command selects the sensor calibration table and the CSET2 command selects the frequency dependent offset table.
  • Page 370: Example

    SENSe Subsystem Example This command enters the name of the sensor CORR:CSET1 ‘PW1’ calibration table which is to be used on Channel A. Reset Condition On reset the selected table is not affected. Query [SENSe[1]]|SENSe2:CORRection:CSET[1]|CSET2:[SELect]? The name of the selected table is returned as a quoted string. If no table is selected an empty string is returned.
  • Page 371 SENSe Subsystem [SENSe[1]]|SENSe2:CORRection:CSET[1]|CSET2:STATe <boolean> This command is to enable and disable the use of the currently active sensor calibration table (CSET1) or frequency dependent offset table (CSET2). When a table has been selected and enabled, the calibration factors/offsets stored in it can be used by specifying the required frequency using the [SENSe[1]]|SENSe2:FREQuency command.
  • Page 372: Query

    SENSe Subsystem Query [SENSe[1]]|SENSe2:CORRection:CSET[1]|CSET2:STATe? The query returns a 1 or 0 into the output buffer indicating whether a table is enabled or disabled. – 1 is returned when the table is enabled – 0 is returned when the table is disabled Query Example This command queries whether there is SENS2:CORR:CSET1:STAT?
  • Page 373 SENSe Subsystem [SENSe[1]]|SENSe2:CORRection:DCYCle|GAIN3 Commands These commands control the pulse power measurement feature of the power meter. The following commands are detailed in this section: [SENSe[1]]|SENSe2:CORRection:DCYCle|GAIN3[:INPut] [:MAGNitude] <numeric_value> [SENSe[1]]|SENSe2:CORRection:DCYCle|GAIN3:STATe <boolean> You can use either DCYCLe or GAIN3 in these commands, both do the same. NOTE Using GAIN3 complies with the SCPI standard whereas DCYCle does not, but may make your program more understandable.
  • Page 374 SENSe Subsystem [SENSe[1]]|SENSe2:CORRection:DCYCle|GAIN3[:INPut] [:MAGNitude] <numeric_value> This command is used to set the duty cycle for the pulse power measurement feature of the power meter. Pulse power measurements average out any deviations in the pulse, such as, overshoot or ringing. The result returned for a pulse power measurement is a mathematical representation of the pulse power rather than an actual measurement.
  • Page 375: Syntax

    SENSe Subsystem Syntax SENS CORR :DCYC :INP :MAGN :GAIN3 SENS2 Space numeric_value Space Parameters Item Description/Defaul t Range of Values numeric_value A numeric value for the duty cycle. 0.001 to 99.999 PCT – DEF: the default value is 1 % –...
  • Page 376: Reset Condition

    SENSe Subsystem Reset Condition On reset, the duty cycle is set to 1 % (DEF). Query [SENSe[1]]|SENSe2:CORRection:DCYCle|GAIN3[:INPut][:MAGNitude]? [MIN|MAX] The query returns the current setting of the duty cycle or the values associated with MIN and MAX. Query Example This command queries the current setting of CORR:GAIN3? the duty cycle for Channel A.
  • Page 377 SENSe Subsystem [SENSe[1]]|SENSe2:CORRection:DCYCle|GAIN3:STATe <boolean> This command is used to enable and disable the pulse power measurement feature. The [SENSe[1]]|SENSe2:CORRection:DCYCle|GAIN3 command should be used to enter the duty cycle of the signal you want to measure. Syntax SENS :DCYC :STAT Space CORR 0|OFF :GAIN3...
  • Page 378: Query Example

    SENSe Subsystem Query Example This command queries whether the pulse CORR:GAIN3:STAT? measurement feature is on or off. Error Messages – If [SENSe[1]]|SENSe2:CORRection:DCYCle:STATus is set to ON while [SENSe[1]]|SENSe2:SPEed is set to 200, the error –221, “Settings Conflict” occurs. – If this command is used when an P-Series or E-Series Power Sensor is connected, the error –310, “System error;Dty Cyc may impair accuracy with ECP sensor”...
  • Page 379 SENSe Subsystem [SENSe[1]]|SENSe2:CORRection:FDOFfset|GAIN4[:INPut] [:MAGNitude]? This command is used to return the frequency dependent offset currently being applied. Syntax SENS :GAIN4 CORR :INP :MAG :FDOFfset SENS2 Example This command queries the current frequency CORR:GAIN4? dependent offset being applied to Channel A. Reset Condition On reset, the frequency dependent offset is not affected.
  • Page 380 SENSe Subsystem [SENSe[1]]|SENSe2:CORRection:GAIN2 Commands These commands provide a simple correction to a measurement for an external gain/loss. The following commands are detailed in this section: [SENSe[1]]|SENSe2:CORRection:GAIN2:STATe <boolean> [SENSe[1]]|SENSe2:CORRection:GAIN2[:INPut][:MAGNitude] <numeric_value> Keysight N8262A Programming Guide...
  • Page 381 SENSe Subsystem [SENSe[1]]|SENSe2:CORRection:GAIN2:STATe <boolean> This command is used to enable/disable a channel offset for the power meter setup. The [SENSe[1]]|SENSe2:CORRection:GAIN2[:INPut][:MAGNitude] command is used to enter the loss/gain value. Syntax Space SENS CORR :GAIN2 :STAT 0|OFF 1|ON SENS2 Example This command enables a channel offset on CORR:GAIN2:STAT ON Channel A.
  • Page 382: Query Example

    SENSe Subsystem Query Example This command queries whether or not there CORR:GAIN2:STAT? is a channel offset applied to Channel A. Error Messages If [SENSe[1]]|SENSe2:CORRection:GAIN2:STATe is set to ON while [SENSe[1]]|SENSe2:SPEed is set to 200, the error –221, “Settings Conflict” occurs. Keysight N8262A Programming Guide...
  • Page 383 SENSe Subsystem [SENSe[1]]|SENSe2:CORRection:GAIN2[:INPut][:MAGNitude] <numeric_value> This command is used to enter a channel offset value for the power meter setup, for example cable loss. The power meter then corrects every measurement by this factor to compensate for the gain/loss. Entering a value for GAIN2 using this command automatically turns the [SENSe[1]]|SENSe2:CORRection:GAIN2:STATe command to ON.
  • Page 384: Parameters

    SENSe Subsystem Parameters Item Description/Defaul t Range of Values numeric_value A numeric value: –100 to +100 dB – DEF: the default is 0.00 dB – MIN: –100 dB – MAX: +100 dB Example This command sets a channel offset of 50 dB CORR:GAIN2 50 for Channel A.
  • Page 385 SENSe Subsystem Query Example This command queries the current setting of CORR:GAIN2? the channel offset on Channel A. Error Messages – If a loss/gain correction value is entered using [SENSe[1]]|SENSe2:CORRection:GAIN2[:INPut][:MAGNitude] while [SENSe[1]]|SENSe2:SPEed is set to 200, the error –221, “Settings Conflict” occurs.
  • Page 386 SENSe Subsystem [SENSe[1]]|SENSe2:FREQuency[:CW|:FIXed] <numeric_value> This command is used to enter a frequency. If the frequency does not correspond directly to a frequency in the sensor calibration table, the power meter calculates the calibration factor using linear interpolation. For 8480 Series Power Sensor the power meter uses linear interpolation to calculate the calibration factor for the frequency entered if [SENSe[1]]|SENSe2:CORRection:CSET:STATe is ON.
  • Page 387 SENSe Subsystem Parameters Item Description/Defaul t Range of Values numeric_value A numeric value for the frequency: 1 kHz to 1000.0 Ghz – DEF: the default value is 50 MHz – MIN: 1 kHz – MAX: 1000.0 GHz The default units are Hz. [a] The following measurement units can be used: –...
  • Page 388 SENSe Subsystem [SENSe[1]]|SENSe2:MRATe <character_data> This command sets the measurement speed on the selected channel. When a channel is set to FAST, the following couplings occur: Command Status [SENSe[1]]|SENSe2:AVERage:STATe [SENSe[1]]|SENSe2:CORRection:DCYCle:STATe [SENSe[1]]|SENSe2:CORRection:GAIN2:STATe CALCulate[1|2|3|4]:GAIN:STATe CALCulate[1|2|3|4]:RELative:STATe CALCulate1|3:MATH:EXPRession “(SENSe1)” CALCulate2|4:MATH:EXPRession “(SENSe2)” [a] This change only occurs on the channel specified in the SENSe:MRATe command. When the specified channel is changed from FAST to NORMal or DOUBle, the settings that were in place when FAST was entered are restored.
  • Page 389 SENSe Subsystem Syntax numeric_value MRAT Space SENS SENS2 Parameters Item Description/Defaul t Range of Values character_data A numeric value for the measurement speed: NORMal – NORMal: 20 readings/second DOUBle – DOUBle: 40 readings/second FAST – FAST: up to 1000 readings/second The default is NORMal.
  • Page 390: Query Example

    SENSe Subsystem Query Example This command queries the current speed MRAT? setting for Channel A. Error Messages – If <character_data> is not set to NORMal, DOUBle or FAST, error –224 “Illegal parameter value” occurs. – If a P-Series or an E-Series Power Sensor is not connected and <character_data>...
  • Page 391 SENSe Subsystem [SENSe[1]]|SENSe2:POWer:AC:RANGe <numeric_value> This command is only valid when used with an E-Series Power Sensor. Its purpose is to select one of two power ranges. – If 0 is selected, the power sensor’s lower range is selected – If 1 is selected, the power sensor’s upper range is selected Setting a range with this command automatically switches [SENSe[1]]|SENSe2:POWer:AC:RANGe:AUTO to OFF.
  • Page 392 SENSe Subsystem Query Example This command queries the current setting of POW:AC:RANG? the power sensor range. Error Messages This command is used with the E-Series Power Sensor. If one is not connected the error –241, “Hardware missing” occurs. Keysight N8262A Programming Guide...
  • Page 393 SENSe Subsystem [SENSe[1]]|SENSe2:POWer:AC:RANGe:AUTO <boolean> This command is only valid when used with an E-Series Power Sensor. Its purpose is to enable and disable autoranging. When autoranging is ON, the power meter selects the best measuring range for the measurement. When autoranging is set to OFF, the power meter remains in the currently set range.
  • Page 394: Query

    SENSe Subsystem Query [SENSe[1]]|SENSe2:POWer:AC:RANGe:AUTO? The query enters a 1 or 0 into the output buffer indicating the status of autoranging. – 1 is returned when autoranging is enabled – 0 is returned when autoranging is disabled Query Example This command queries whether auto ranging POW:AC:RANG:AUTO? is on or off.
  • Page 395 SENSe Subsystem [SENSe[1]]|SENSe2:SWEep[1]|2|3|4 Commands These commands set offset time and time gate length as illustrated in the following diagram: Post-Trigger Pre- Trigger With no trace: internally calculated time With no Time gate length: trace: SENSe:SWEep:TIME internally calculated time Incoming signal from sensor Trigger Delay...
  • Page 396 SENSe Subsystem [SENSe[1]]|SENSe2:SWEep[1]|2|3|4:OFFSet:TIME <numeric_value> This command sets the delay between the delayed trigger point and the start of the time-gated period (the offset time) for a P-Series sensor set to NORMal mode. . Syntax :OFFS Space SENS :TIME numeric_value SENS2 Parameters Item Description/Defaul t...
  • Page 397: Example

    SENSe Subsystem Example This command sets the delay to 0.001 SENS2:SWE3:OFFS:TIME 0.001 seconds. Reset Condition On reset, the value is set to 0 seconds. Query SENSe[1]]|SENSe2:SWEep[1]|2|3|4:OFFSet:TIME? The query returns the current delay between the trigger point and the start of the time-gated period.
  • Page 398 SENSe Subsystem [SENSe[1]]|SENSe2:SWEep[1]|2|3|4:TIME <numeric_value> This command sets the length of the time-gated period (time-gate length) for time-gated measurements for the P-Series sensors which are set to NORMal mode. Syntax : TIME Space SENS numeric_value SENS2 Parameters Item Description/Defaul t Range of Values numeric_value The length of the time gated period in seconds.
  • Page 399: Reset Condition

    SENSe Subsystem Reset Condition On reset, gate 1 is set to 100 µs and other gates to 0 s. Query SENSe[1]]|SENSe2:SWEep[1]|2|3|4:TIME? The query returns the current length of the time-gated period. Query Example This command queries the length of the SENS2:SWE2:TIME? time-gated period for Channel B and gate 2.
  • Page 400 SENSe Subsystem [SENSe[1]]|SENSe2:TEMPerature? This this command to returns the P-Series power sensor's temperature in degrees Celsius. Syntax SENS : TEMP SENS2 Parameters Item Description/Defaul t Range of Values numeric_value A numeric value defining sensor's temperature in degrees –50 to 100 Celsius.
  • Page 401 SENSe Subsystem [SENSe[1]]|SENSe2:TRACe Commands These commands are used to set: – The upper and lower limits for the trace display – The delay between the delayed trigger point and the start of the trace – The duration of the trace –...
  • Page 402 SENSe Subsystem [SENSe[1]]|SENSe2:TRACe:OFFSet:TIME <numeric_value> This command sets the delay between the delayed trigger point and the start of the trace for P-Series sensors are set to NORMal mode. Syntax TRAC :OFFS Space SENS :TIME numeric_value SENS2 Parameters Item Description/Defaul t Range of Values numeric_value The length of the delay in seconds.
  • Page 403: Reset Condition

    SENSe Subsystem Reset Condition On reset, the delay is set to 0 seconds. Query SENSe[1]]|SENSe2:TRACe:OFFSet:TIME? The query returns the current delay between the delayed trigger point and the start of the trace. Query Example This command queries the current delay SENS:TRAC:OFFS:TIME? between the delayed trigger point and the start of the trace for Channel A.
  • Page 404 SENSe Subsystem [SENSe[1]]|SENSe2:TRACe:TIME <numeric_value> This command sets the duration of the trace for a P-Series sensor set to NORMal mode. Syntax Space numeric_value TRAC :TIME SENS SENS2 Parameters Item Description/Defaul t Range of Values numeric_value The duration of the trace in seconds. 10 µs to 1 second –...
  • Page 405 SENSe Subsystem Reset Condition On reset, the duration is set to 100 µs. Query SENSe[1]]|SENSe2:TRACe:TIME? The query returns the current duration of the trace. Query Example This command queries the current duration SENS2:TRAC:TIME? of the trace. Error Messages – If the command is used when a sensor other than a P-Series power sensor is connected, error –241, “Hardware missing”...
  • Page 406 SENSe Subsystem [SENSe[1]]|SENSe2:TRACe:UNIT <character_data> This command sets the units for the trace for the specified channel. Syntax Space SENS :UNIT character_data :TRAC Parameters Item Description/Defaul t Range of Values character_data – DBM: dBm – W: Watts Example This command sets the trace units for SENS2:TRAC:UNIT W Channel B to Watts.
  • Page 407: Query

    SENSe Subsystem Query [SENSe[1]]|SENSe2:TRACe:UNIT? The query command returns the current value of character_data. Query Example This command queries the current trace SENS2:TRAC:UNIT? units for Channel B. Keysight N8262A Programming Guide...
  • Page 408 SENSe Subsystem [SENSe[1]]|SENSe2:V2P ATYPe|DTYPe This command is used to select the type of linearity correction that is applied to the channel sensors being used. For most 8480 Series sensors the correct (A type or D type) linearity correction table is automatically selected. However, for the V8486A and W8486A sensors the automatic selection must be overridden and the D type (diode) correction selected.
  • Page 409: Query Example

    SENSe Subsystem Query Example This command queries which linearity SENS:V2P? correction type is currently being used on Channel A. Error Messages If no sensor is connected or the sensor is not an A type, the error –241, “Hardware missing” occurs. Keysight N8262A Programming Guide...
  • Page 410: Sense[1]|2:Trace:limit:lower

    SENSe Subsystem SENSe[1]|2:TRACe:LIMit:LOWer <numeric_value> This command sets the lower scale limit of the trace for the specified channel. The units used are dependent on the current setting of SENS:TRAC:UNIT as shown Table 10-1. Table 10-1 Measurement units Units: Units: SENS:TRAC:UNIT SENS:TRAC:LIM:LOW The trace lower scale limit is maintained at a lower power than the upper scale NOTE...
  • Page 411: Parameters

    SENSe Subsystem Parameters Item Description/Defaul t Range of Values numeric_value A numeric value for the trace lower scale limit. –150 to 230 dBm – DEF: the default is 20 dBm – MIN: –150 dBm – MAX: 230 dBm Example This command sets the trace lower scale SENS2:TRAC:LIM:LOW 10 limit to 10 dBm for Channel B.
  • Page 412: Sense[1]|2:Trace:limit:upper

    SENSe Subsystem SENSe[1]|2:TRACe:LIMit:UPPer <numeric_value> This command sets the upper scale limit of the trace for the specified channel. The units used are dependent on the current setting of SENS:TRAC:UNIT as shown Table 10-2. Table 10-2 Measurement units Units: Units: SENS:TRAC:UNIT SENS:TRAC:LIM:UPP The trace lower scale limit is maintained at a lower power than the upper scale NOTE...
  • Page 413 SENSe Subsystem Parameters Item Description/Defaul t Range of Values numeric_value A numeric value for the trace lower scale limit. –150 to 230 dBm – DEF: the default is 20 dBm – MIN: –150 dBm – MAX: 230 dBm Example This command sets the trace upper scale SENS:TRAC:LIM:UPP 100 limit to 100 dBm for Channel A.
  • Page 414: Sense[1]|2:Trace:x:scale:pdiv

    SENSe Subsystem SENSe[1]|2:TRACe:X:SCALe:PDIV <numeric_value> This command is used to set the X Scale value (per division) for the selected trace. This command is only applicable when N192x sensor is present and trigger NOTE acquisition mode is selected. Syntax numeric_value Space SENS :TRAC :PDIV...
  • Page 415: Reset Condition

    SENSe Subsystem Reset Condition On reset, X Start = 0 s; X Scale = 10 µs. Query SENSe[1]|2:TRACe:X:SCALe:PDIV? The query returns the current scale setting of X-axis in numerical value. Query Example This command queries the Channel A current SENS:TRAC:X:SCAL:PDIV? X-axis scale setting in numerical value.
  • Page 416: Sense[1]|2:Trace:y:scale:pdiv

    SENSe Subsystem SENSe[1]|2:TRACe:Y:SCALe:PDIV <numeric_value> This command is used to set the Y Scale value (per division) for the selected trace. The Y Scale value set by this SCPI command is dependant on the current Y-axis unit, which can be set using SENS:TRAC:UNIT command. This command is only applicable when N192x sensor is present and trigger NOTE acquisition mode is selected.
  • Page 417: Example

    SENSe Subsystem Example This command sets the Channel A Y Scale SENS:TRAC:Y:SCAL:PDIV 0.002 value to 0.002 step. This command sets the Channel B Y Scale SENS2:TRAC:Y:SCAL:PDIV 0.05 value to 0.05 step. Reset Condition On reset, Y Max = 20 dBm; Y Scale = 7 dB. Query SENSe[1]|2:TRACe:Y:SCALe:PDIV? The query returns the current scale setting of Y-axis in numerical value.
  • Page 418 SENSe Subsystem THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK. Keysight N8262A Programming Guide...
  • Page 419 Keysight N8262A P-Series Modular Power Meter Programming Guide STATus Subsystem STATus Subsystem Status Register Set Commands Device Status Register Sets Operation Register Sets STATus:OPERation STATus:OPERation:CALibrating[:SUMMary] STATus:OPERation:LLFail[:SUMMary] STATus:OPERation:MEASuring[:SUMMary] STATus:OPERation:SENSe[:SUMMary] STATus:OPERation:TRIGger[:SUMMary] STATus:OPERation:ULFail[:SUMMary] STATus:PRESet Questionable Register Sets STATus:QUEStionable STATus:QUEStionable:CALibration[:SUMMary] STATus:QUEStionable:POWer[:SUMMary] This chapter explains how the STATus command subsystem enables you to examine the status of the power meter by monitoring the “Device Status Register”, “Operation Status Register”...
  • Page 420: Table 11-1 Commands And Events Affecting Status Register

    STATus Subsystem STATus Subsystem The STATus command subsystem enables you to examine the status of the power meter by monitoring the following status registers: – Device status register – Operation status register – Questionable status register The contents of these and other registers in the power meter are determined by one or more status registers.
  • Page 421: Examples

    STATus Subsystem (page 420) STATus:DEVice (page 430) STATus:OPERation STATus:OPERation:CALibrating[:SUMMary] (page 431) STATus:OPERation:LLFail[:SUMMary] (page 432) STATus:OPERation:MEASuring[:SUMMary] (page 433) STATus:OPERation:SENSe[:SUMMary] (page 434) STATus:OPERation:TRIGger[:SUMMary] (page 435) STATus:OPERation:ULFail[:SUMMary] (page 436) STATus:QUEStionable (page 437) STATus:QUEStionable (page 439) STATus:QUEStionable:CALibration[:SUMMary] (page 440) STATus:QUEStionable:POWer[:SUMMary] (page 441) Examples – To use the :CONDition? command to examine the STATus:DEVice register: STATus:DEVice:CONDition? –...
  • Page 422: Status Register Set Commands

    STATus Subsystem Status Register Set Commands This section describes the five status register set commands. Each can be used to examine all of the eleven status registers listed on page 421. To apply a command to a specific register, prefix the command with the name of the appropriate register.
  • Page 423: Event]

    STATus Subsystem [:EVENt]? This query returns a 16 bit decimal-weighted number representing the bits set in the Event Register of the SCPI Register Set you require to control. The format of the return is <NR1> in the range of 0 to 32767 (2 –1).
  • Page 424: Parameters

    STATus Subsystem Parameters Type Description Range of Values The value used to set the Enable Register. 0 to 2 –1 non-decimal numeric Query :ENABle? The query returns a 15 bit decimal-weighted number representing the contents of the Enable Register of the SCPI Register Set being queried. The format of the return is <NR1>...
  • Page 425: Syntax

    STATus Subsystem Syntax space :NTR non-decimal numeric Parameters Type Description Range of Values The value used to set the NTR Register. 0 to 2 –1 non-decimal numeric Query :NTRansition? The query returns a 15 bit decimal-weighted number representing the contents of the Negative Transition Register of the SCPI register set being queried.
  • Page 426 STATus Subsystem Syntax space :PTR non-decimal numeric Parameters Type Description Range of Values The value used to set the PTR Register. 0 to 2 –1 non-decimal numeric Query :PTRansition? The query returns a 15 bit decimal-weighted number representing the contents of the Positive Transition Register of the SCPI register set being queried.
  • Page 427: Device Status Register Sets

    STATus Subsystem Device Status Register Sets The status registers contain information which give device status information. The contents of the individual registers of these register sets may be accessed by appending the commands listed in “Status Register Set Commands”. The following command descriptions detail the SCPI register you require to control but do not detail the register set commands.
  • Page 428 STATus Subsystem – STATus:DEVice:NTRansition is 1, then STATus:DEVice:EVENt? is set when a power sensor is disconnected. – STATus:DEVice:PTRansition is 1, then STATus:DEVice:EVENt? is set when a power sensor is connected. Querying STATus:DEVice:EVENt? clears the STATus:DEVice:EVENt? register. NOTE The Channel A and B sensor error bits (3 and 4) are set to: –...
  • Page 429: Operation Register Sets

    STATus Subsystem Operation Register Sets The following registers contain information which is part of the power meter’s normal operation. The contents of the individual registers of these register sets may be accessed by appending the commands listed in “Status Register Set Commands”.
  • Page 430: Status:operation

    STATus Subsystem STATus:OPERation The operation status register set contains conditions which are a part of the operation of the power meter as a whole. The following bits in these registers are used by the power meter: Bit Number Decimal Weight Definition CALibrating Summary Self Test Started...
  • Page 431: Status:operation:calibrating[:Summary]

    STATus Subsystem STATus:OPERation:CALibrating[:SUMMary] The operation status calibrating summary register set contains information on the calibrating status of the power meter. The following bits in these registers are used by the power meter: Bit Number Decimal Weight Definition Not used Channel A CALibrating Status Channel B CALibrating Status 3-15 Not used...
  • Page 432: Status:operation:llfail[:Summary]

    STATus Subsystem STATus:OPERation:LLFail[:SUMMary] The operation status lower limit fail summary register set contains information on the lower limit fail status of the power meter. The following bits in these registers are used by the power meter: Bit Number Decimal Weight Definition Not used Channel A LLFail Status...
  • Page 433: Status:operation:measuring[:Summary]

    STATus Subsystem STATus:OPERation:MEASuring[:SUMMary] The operation status measuring summary register set contains information on the measuring status of the power meter. The following bits in these registers are used by the power meter: Bit Number Decimal Weight Definition Not used Channel A MEASuring Status Channel B MEASuring Status 3-15 Not used...
  • Page 434: Status:operation:sense[:Summary]

    STATus Subsystem STATus:OPERation:SENSe[:SUMMary] The operation status sense summary register set contains information on the status of the power sensors. The following bits in these registers are used by the power meter: Bit Number Decimal Weight Definition Not used Channel A SENSe Status Channel B SENSe Status 3-15 Not used...
  • Page 435: Status:operation:trigger[:Summary]

    STATus Subsystem STATus:OPERation:TRIGger[:SUMMary] The operation status trigger summary register set contains information on the trigger status of the power meter. The following bits in these registers are used by the power meter: Bit Number Decimal Weight Definition Not used Channel A TRIGger Status Channel B TRIGger Status 3-15 Not used...
  • Page 436: Status:operation:ulfail[:Summary]

    STATus Subsystem STATus:OPERation:ULFail[:SUMMary] The operation status upper limit fail summary register set contains information on the upper limit fail status of the power meter. The following bits in these registers are used by the power meter: Bit Number Decimal Weight Definition Not used Channel A ULFail Status...
  • Page 437: Status:preset

    STATus Subsystem STATus:PRESet PRESet sets a number of the status registers to their preset values as shown below - all other registers are unaffected. Bit 15 is always 0. Register Fil ter/Enable PRESet Value OPERational ENABle all zeros all ones all zeros QUEStionable ENABle...
  • Page 438: Questionable Register Sets

    STATus Subsystem Questionable Register Sets The questionable register sets contain information which gives an indication of the quality of the data produced by the power meter. The contents of the individual registers in these register sets may be accessed by appending the commands listed in “Status Register Set Commands”.
  • Page 439: Status:questionable

    STATus Subsystem STATus:QUEStionable The questionable register set contains bits that indicate the quality of various aspects of signals processed by the power meter. The following bits in these registers are used by the power meter: Bit Number Decimal Weight Definition 0 to 2 Not used POWer Summary...
  • Page 440: Status:questionable:calibration[:Summary]

    STATus Subsystem STATus:QUEStionable:CALibration[:SUMMary] The questionable calibration summary register set contains bits which give an indication of the quality of the data produced by the power meter due to its calibration status. The following bits in these registers are used by the power meter: Bit Number Decimal Weight Definition...
  • Page 441: Status:questionable:power[:Summary]

    STATus Subsystem STATus:QUEStionable:POWer[:SUMMary] The questionable power summary register set contain bits that indicate the quality of the power data being acquired by the power meter. The following bits in these registers shall be used by the power meter: Bit Number Decimal Weight Definition Not used...
  • Page 442: Syntax

    STATus Subsystem – Channel A requires zeroing Bit 6 is set when the following condition occurs: – Channel B requires zeroing These bits are cleared when no errors or events are detected by the power meter during a measurement covering the causes given for it to set. Syntax :POW :SUMM...
  • Page 443 STATus Subsystem Logical OR Logical OR Logical OR Logical OR Logical OR Logical OR Logical OR Logical OR Logical OR Logical OR Logical OR Logical OR Logical OR Keysight N8262A Programming Guide...
  • Page 444 STATus Subsystem THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK. Keysight N8262A Programming Guide...
  • Page 445 Keysight N8262A P-Series Modular Power Meter Programming Guide SYSTem Subsystem SYSTem Subsystem SYSTem:COMMunicate:LAN:AIP[:STATe] <boolean> SYSTem:COMMunicate:LAN:CURRent:ADDRess? SYSTem:COMMunicate:LAN:CURRent:DGATeway? SYSTem:COMMunicate:LAN:CURRent:DNAMe? SYSTem:COMMunicate:LAN:CURRent:SMASk? SYSTem:COMMunicate:LAN:ADDRess <character_data> SYSTem:COMMunicate:LAN:DGATeway <character_data> SYSTem:COMMunicate:LAN:DHCP[:STATe] <boolean> SYSTem:COMMunicate:LAN:DNAMe <character_data> SYSTem:COMMunicate:LAN:HNAMe <character_data> SYSTem:COMMunicate:LAN:MAC? SYSTem:COMMunicate:LAN:RESTart SYSTem:COMMunicate:LAN:SMASk <character_data> SYSTem:DISPlay:BMP SYSTem:ERRor? SYSTem:HELP:HEADers? SYSTem:PERSona:MANufacturer <character_data> SYSTem:PERSona:MANufacturer:DEFault SYSTem:PRESet <character_data> SYSTem:VERSion? This chapter explains how to use the SYSTem command subsystem to return error numbers and messages from the power meter, preset the power meter, set the...
  • Page 446 SYSTem Subsystem SYSTem Subsystem The SYStem command subsystem is used to: – Return error numbers and messages from the power meter – Preset the power meter – Set the LAN address – Set the command language – Query the SCPI version Keyword Parameter Form Notes...
  • Page 447 SYSTem Subsystem Keyword Parameter Form Notes Page page 460 :SMASk <character_data> :DISPLAY [query only] page 461 :BMP? page 462 :ERRor :HELP [query only] page 469 :HEADers? :PERSona: page 470 MANufacturer <character_data> page 472 :DEFault [event; no query] page 473 :PRESet <character_data>...
  • Page 448: System:communicate:lan:aip[:State]

    SYSTem Subsystem SYSTem:COMMunicate:LAN:AIP[:STATe] <boolean> This command enables the AutoIP protocol to dynamically assign the IP address when connecting to the power meter in an isolated (non-site) LAN network (for example, laptop to power meter). Syntax Space 0|OFF :AIP :STAT :COMM :LAN SYST 1|ON...
  • Page 449: System:communicate:lan:current:address

    SYSTem Subsystem SYSTem:COMMunicate:LAN:CURRent:ADDRess? This command returns the current setting of the IP address in use by the power meter. If DHCP or AutoIP are enabled and successful, then one of these IP address NOTE modes assigns the IP address, otherwise it is the static IP address. Syntax :COMM :LAN...
  • Page 450: System:communicate:lan:current:dgateway

    SYSTem Subsystem SYSTem:COMMunicate:LAN:CURRent:DGATeway? This command returns the current setting of the LAN IP router/gateway address in use by the power meter. If DHCP or AutoIP are enabled and successful, then one of these IP address NOTE modes assigns the LAN IP router/gateway address, otherwise it is the static LAN IP router/gateway address Syntax SYST...
  • Page 451: System:communicate:lan:current:dname

    SYSTem Subsystem SYSTem:COMMunicate:LAN:CURRent:DNAMe? This command returns the current setting of the LAN domain name in use by the power meter. If DHCP or AutoIP are successfully enabled, then one of these IP address modes NOTE assign the LAN domain name, otherwise it is the static LAN domain name. Syntax :COMM :LAN...
  • Page 452: System:communicate:lan:current:smask

    SYSTem Subsystem SYSTem:COMMunicate:LAN:CURRent:SMASk? This command returns the current setting of the LAN subnet mask in use by the power meter. If DHCP or AutoIP are successfully enabled, then one of these IP address modes NOTE assign the LAN subnet mask, otherwise it is the static LAN subnet mask. Syntax :COMM :LAN...
  • Page 453: System:communicate:lan:address

    SYSTem Subsystem SYSTem:COMMunicate:LAN:ADDRess <character_data> This command sets the LAN (IP) address of the power meter. Syntax character_data SYST Space :COMM :LAN :ADDR Parameters Item Description Range of Values character_data Numeric character values for the address. Up to 15 0 to 225 (no embedded spaces) characters, formatted as follows: A.B.C.D where A, B, C, D = 0 to 225 Example...
  • Page 454: System:communicate:lan:dgateway

    SYSTem Subsystem SYSTem:COMMunicate:LAN:DGATeway <character_data> This command sets the LAN IP router/gateway address for the power meter. Syntax Space character_data SYST :COMM :LAN :DGAT Parameters Item Description Range of Values character_data Numeric character values for the address. Up to 15 0 to 225 (no embedded spaces) characters, formatted as follows: A.B.C.D where A, B, C, D = 0 to 225 Example...
  • Page 455: System:communicate:lan:dhcp[:State]

    SYSTem Subsystem SYSTem:COMMunicate:LAN:DHCP[:STATe] <boolean> This command enables the dynamic host configuration protocol. Syntax Space 0|OFF :DHCP :STAT SYST :COMM :LAN 1|ON Example This command enables the DHCP. SYST:COMM:LAN:DHCP ON Query SYSTem:COMMunicate:LAN:DHCP? – 1 is returned if DHCP is enabled – 0 is returned if DHCP is disabled Query Example This command queries the state of the DHCP.
  • Page 456: System:communicate:lan:dname

    SYSTem Subsystem SYSTem:COMMunicate:LAN:DNAMe <character_data> This command sets the domain name for the power meter. Syntax Space :DNAM SYST :COMM :LAN character_data Parameters Item Description Range of Values character_data Character values of up to 16 characters Maximum of 16 characters Example This command sets the hostname to SYST:COMM:LAN:DNAM myco.com.
  • Page 457: System:communicate:lan:hname

    SYSTem Subsystem SYSTem:COMMunicate:LAN:HNAMe <character_data> This command sets the hostname for the power meter. The factory default setting of hostname is in this format: K - + prod uct number + - + suffix 5 d igits of serial number For example, K-N8262A-00204 Syntax Space character_data...
  • Page 458: System:communicate:lan:mac

    SYSTem Subsystem SYSTem:COMMunicate:LAN:MAC? This query returns the LAN MAC address. Syntax :COMM :LAN SYST :MAC Example This command queries the current MAC SYST:COMM:LAN:MAC? address. Keysight N8262A Programming Guide...
  • Page 459: System:communicate:lan:restart

    SYSTem Subsystem SYSTem:COMMunicate:LAN:RESTart This command restarts the power meter's network stack; any LAN configuration changes can only take effect after this is performed. Syntax :COMM :LAN :REST SYST Example This command restarts the LAN network with SYST:COMM:LAN:REST new configuration. Keysight N8262A Programming Guide...
  • Page 460: System:communicate:lan:smask

    SYSTem Subsystem SYSTem:COMMunicate:LAN:SMASk <character_data> This command sets the subnet mask of the power meter. Syntax Space character_data :SMAS SYST :COMM :LAN Parameters Item Description Range of Values character_data Numeric character values for the address. Up to 15 0 to 225 (no embedded spaces) characters, formatted as follows: A.B.C.D where A, B, C, D = 0 to 225 Example...
  • Page 461: System:display:bmp

    SYSTem Subsystem SYSTem:DISPlay:BMP This command returns the display image in bitmap format. This command is limited to a maximum of five image returns per second. It is not recommended to use this command in Fast Mode, as it slows down the NOTE measurement rate.
  • Page 462: System:error

    SYSTem Subsystem SYSTem:ERRor? This query returns error numbers and messages from the power meter’s error queue. When an error is generated by the power meter, it stores an error number and corresponding message in the error queue. One error is removed from the error queue each time this command is executed.
  • Page 463: System Subsystem

    SYSTem Subsystem Error Message List –101 Invalid character An invalid character was found in the command string. You may have inserted a character such as #, $, or % in the command header or within a parameter. For example, LIM:LOW O#. –102 Syntax error Invalid syntax was found in the command string.
  • Page 464 SYSTem Subsystem –123 Exponent too large A numeric parameter was found whose exponent was larger than 32,000. For example, SENS:COUN 1E34000. –124 Too many digits A numeric parameter was found whose mantissa contained more than 255 digits, excluding leading zeros. –128 Numeric data not allowed A numeric value was received within a command which does not accept a numeric value.
  • Page 465 SYSTem Subsystem –168 Block data not allowed A legal block data element was encountered but not allowed by the power meter at this point. For example SYST:LANG #15FETC?. –178 Expression data not allowed A legal expression data was encountered but not allowed by the power meter at this point. For example SYST:LANG (5+2).
  • Page 466 SYSTem Subsystem –226 Lists not same length This occurs when SENSe:CORRection:CSET[1]|CSET2:STATe is set to ON and the frequency and calibration/offset lists do not correspond in length. –230 Data corrupt or stale;Please calibrate Channel B When CAL[1|2]:RCAL is set to ON and the sensor currently connected to Channel B has not been calibrated, then any command which would normally return a measurement result (for example FETC?, READ?, or MEAS?) will generate this error message.
  • Page 467 SYSTem Subsystem –231 Data questionable;ZERO ERROR ChB Power meter zeroing failed on Channel B. The most likely cause is attempting to zero when some power signal is being applied to the power sensor. –241 Hardware missing The power meter is unable to execute the command because either no power sensor is connected or it expects an E-Series power sensor and one is not connected.
  • Page 468 SYSTem Subsystem –330 Self-test Failed;Measurement Channel B Fault –330 Self-test Failed;Calibrator Fault Refer to “Calibrator” on page 104 if you require a description of the calibrator test. –330 Self-test Failed;ROM Check Failed –330 Self-test Failed;RAM Check Failed –330 Self-test Failed;Display Assy. Fault Refer to “Display”...
  • Page 469: Figure 12-1 Ieee 488.2 Arbitrary Block Program Data Format

    SYSTem Subsystem SYSTem:HELP:HEADers? This query returns a list of all SCPI commands supported by the instrument. Data is returned in IEEE 488.2 arbitrary block program data format as shown in Figure 12-1 below. #xyyy..yddd....ddd<LF> The number of data bytes (d) Line feed character contained in the block.
  • Page 470: System:persona:manufacturer

    SYSTem:PERSona:MANufacturer <character_data> This command only accepts two non-case sensitive strings “Agilent Technologies” and “Keysight Technologies”. A power cycle or reboot is required for the changes in the instrument’s manufacturer string to take effect and to be recognized in the Keysight Connection Expert. The string will remain for the subsequent power cycle or reboot.
  • Page 471: Query

    SYSTem Subsystem Query SYSTem:PERSona:MANufacturer? The query returns the manufacturer string that was set. Query Example Queries the manufacturer string that was set. SYST:PERS:MAN? Error Message If <character_data> is not set to “Agilent Technologies” or “Keysight Technologies”, error –158, “String data not allowed” occurs. Keysight N8262A Programming Guide...
  • Page 472: System:persona:manufacturer:default

    SYSTem Subsystem SYSTem:PERSona:MANufacturer:DEFault This command sets the instrument’s manufacturer to “Keysight Technologies” which is the default manufacturer setting. Syntax SYST :PERS :MAN :DEF Example This command sets the instrument’s manufacturer SYST:PERS:MAN:DEF string to “Keysight Technologies” which is the default manufacturer setting.
  • Page 473: System:preset

    SYSTem Subsystem SYSTem:PRESet <character_data> This command presets the power meter to values appropriate for measuring the communications format specified by <character_data>. The power meter is preset to default values if no value or the value DEFault is supplied. DEFault settings apply to both *RST and to SYSTem:PREset DEFault unless NOTE stated otherwise.
  • Page 474: Syntax

    SYSTem Subsystem Syntax Space character_data SYST :PRES Parameters Item Description Range of Values character_data A communications format which determines the preset DEFault values. Refer to Table 12-1 through to Table 12-49 for the GSM900 preset values for each format. EDGE NADC BLUetooth CDMAone...
  • Page 475: Example

    SYSTem Subsystem Example This command presets the power meter with SYST:PRES DEF default values. The same default values are set when the parameter is omitted. Error messages – If a non-E-Series power sensor is connected, the command can be used to set the power meter to Default settings.
  • Page 476: Preset Values

    SYSTem Subsystem Preset Values DEFault Table 12-1 shows the power meter presets when <character_data> is set to DEFault or omitted. Values are shown for all SCPI commands: Table 12-1 DEFault: Power meter presets Command Setting Comments “POW:AVER” Select average measurement type CALC[1]|2|3|4:FEED[1]|2 0.000 dB Display offset value...
  • Page 477: Table 12-1 Default: Power Meter Presets

    SYSTem Subsystem Table 12-1 DEFault: Power meter presets (continued) Command Setting Comments –70.000 dBm Analog meter lower limit DISP[:WIND[1]|2]:MET:LOW +20.000 dBm Analog meter upper limit DISP[:WIND[1]|2]:MET:UPP Window resolution DISP[:WIND[1]|2|][:NUM[1]|2]:RES upper window Window selected DISP[:WIND[1]|2]:SEL[1]|2 Both windows enabled on display DISP[:WIND[1]|2][:STAT] Maximum power SENSe[1]|2:TRAC:LIM:UPP Minimum power...
  • Page 478 SYSTem Subsystem Table 12-1 DEFault: Power meter presets (continued) Command Setting Comments [SENS[1]]|SENS2:CORR:CSET[1]|CSET2:STAT not affected Sensor calibration table disabled 1.000 % Duty cycle factor [SENS[1]]|SENS2:CORR:DCYC|GAIN3 [:INP][:MAGN] Duty cycle correction disabled [SENS[1]]|SENS2:CORR:DCYC|GAIN3:STAT not affected Return frequency dependent offset [SENS[1]]|SENS2:CORR:FDOF|GAIN4 [:INP][:MAGN] Channel offset disabled [SENS[1]]|SENS2:CORR:GAIN2:STAT 0.0 dB Enter channel offset value...
  • Page 479 SYSTem Subsystem Table 12-1 DEFault: Power meter presets (continued) Command Setting Comments 0 dB Power level TRIG[:SEQ]:LEV Enable automatic setting of trigger level TRIG[:SEQ]:LEV:AUTO Trigger event recognized on rising edge TRIG[:SEQ]:SLOP Trigger events for measurement cycle TRIG[:SEQ[1]|2]:COUN Enable settling time delay TRIG[:SEQ[1]|2]:DEL:AUTO Trigger source set up TRIG[:SEQ[1]|2]:SOUR...
  • Page 480 SYSTem Subsystem GSM900 Table 12-2 shows the power meter presets when <character_data> is set to GSM900. The GSM900 set-up provides the following: – Average power measurement in one GSM timeslot – Trace display showing “on” timeslot A GSM900 measurement is started by detecting the rising edge of a GSM RF burst—for example the burst emitted by a GSM mobile—using the internal RF level trigger.
  • Page 481: Table 12-2 Gsm900: Power Meter Presets

    SYSTem Subsystem Table 12-2 GSM900: Power meter presets (continued) Command Setting Comments –15 dBm Power level TRIG[:SEQ]:LEV Trigger event recognized on the rising TRIG[:SEQ]:SLOP edge of a signal 20 µs Delay between recognition of trigger event TRIG[:SEQ]:DEL and start of a measurement 4275 µs Trigger holdoff TRIG[:SEQ]:HOLD...
  • Page 482: Table 12-3 Gsm900: Power Meter Presets: Window/Measurement

    SYSTem Subsystem Table 12-3 GSM900: Power meter presets: Window/Measurement settings Function Setting Single Channel Dual Channel Display setup Upper window Channel A trace Primary channel trace Lower window LU single numeric Table 12-4 Window/measurement setup Upper window/upper measurement (UU) Feed Measurement Upper window/lower measurement (UL) Feed...
  • Page 483 SYSTem Subsystem Table 12-4 GSM900: Power meter presets for secondary channel sensors (continued) Function Secondary Channel Sensor No Sensor Non P-Series P-Series Lower window/lower measurement (LL) Feed Secondary channel Gate1 secondary channel (Channel B) Measurement [a] For further information refer to “Primary and Secondary Channels”...
  • Page 484: Table 12-5 Edge: Power Meter Presets

    SYSTem Subsystem Table 12-5 EDGE: Power meter presets Command Setting Comments Frequency +900.000 MHz Frequency setting [SENS[1]]|SENS2:FREQ[:CW|:FIX] Sensor measurement mode NORM Measurement mode [SENS[1]]|SENS2:DET:FUNC Sensor video bandwidth setup N1921/2A: LOW Sensor video bandwidth [SENS[1]]|SENS2:BAND|BWID:VID Gate Setup [SENS[1]]|SENS2:SWE[1]|2|3|4:OFF:TIME Gate 1: 20 µs Delay between trigger point and time gated Gates 2 - 4: 0 period.
  • Page 485: Table 12-6 Edge: Power Meter Presets: Window/Measurement

    SYSTem Subsystem Table 12-5 EDGE: Power meter presets (continued) Command Setting Comments Averaging Averaging On [SENSe[1]]|SENSe2:AVER[:STATe] Averaging set to 64 [SENSe[1]]|SENSe2:AVER:COUN Step detection Step detection enabled [SENSe[1]]|SENS2:AVER:SDET Trace setup +20 dBm Maximum power SENSe[1]|2:TRAC:LIM:UPP –35 dBm Minimum power SENSe[1]|2:TRAC:LIM:LOW –40 µs Delay between delayed trigger point and [SENS[1]]|SENS2:TRAC:OFFS:TIME the start of the trace...
  • Page 486 SYSTem Subsystem Table 12-6 EDGE: Power meter presets: Window/Measurement settings (continued) Function Setting Single Channel Dual Channel Measurement Upper window/lower measurement (UL) Feed Measurement Lower window/upper measurement (LU) Feed Gate 1 Channel A Gate 1 primary channel Measurement Lower window/lower measurement (LL) Feed Gate 1 Channel A Table 12-7...
  • Page 487 SYSTem Subsystem CDMAone The cdmaOne set-up provides: – Average power in an IS-95 cdmaOne signal (bandwidth is less than 1.5 MHz). – Peak power and peak-to-average ratio of the signal over a defined, statistically valid number of samples. The reading is continuously refreshed. This gives an indication of how cdmaOne channel loading affects peak power and power distribution.
  • Page 488: Table 12-8 Cdmaone: Power Meter Presets

    SYSTem Subsystem Table 12-8 CDMAone: Power meter presets (continued) Command Setting Comments Trigger setup INT1 Trigger source set up and acquisition TRIG[:SEQ[1]|2]:SOUR mode continuous triggering INIT:CONT Enable automatic setting of the trigger TRIG[:SEQ]:LEV:AUTO level AUTO Automatic Power level TRIG[:SEQ]:LEV Trigger event recognized on the rising TRIG[:SEQ]:SLOP edge of a signal Delay between recognition of trigger event...
  • Page 489: Table 12-9 Cdmaone: Power Meter Presets: Window/Measurement Settings

    SYSTem Subsystem Table 12-9 CDMAone: Power meter presets: Window/Measurement settings Function Setting Single Channel Dual Channel Display setup Upper window UU single numeric Table 12-10 Lower window Dual numeric Table 12-10 Window/measurement setup Upper window/upper measurement (UU) Feed Gate 1 Channel A Gate 1 primary channel Measurement Upper window/lower measurement (UL)
  • Page 490 SYSTem Subsystem Table 12-10 CDMAone: Power meter presets for secondary channel sensors Function Secondary Channel Sensor No Sensor Non P-Series Sensor P-Series Sensor Display setup Upper window UU single numeric Dual numeric Dual numeric Lower window Dual numeric Dual numeric Dual numeric Upper window/lower measurement (UL) Gate 1 primary channel...
  • Page 491 SYSTem Subsystem CDMA2000 The cdma2000 set-up provides: – Average power in a cdma2000 signal (bandwidth <=5 MHz). – Peak power and peak-to-average ratio of the signal over a defined, statistically valid number of samples. The reading is continuously refreshed. This indicates how cdma2000 channel loading affects peak power and power distribution.
  • Page 492: Table 12-11 Cdma2000: Power Meter Presets

    SYSTem Subsystem Table 12-11 cdma2000: Power meter presets (continued) Command Setting Comments INT1 Trigger source set up and acquisition TRIG[:SEQ[1]|2]:SOUR mode continuous triggering INIT:CONT Enable automatic setting of the trigger TRIG[:SEQ]:LEV:AUTO level AUTO Automatic Power level TRIG[:SEQ]:LEV Trigger event recognized on the rising TRIG[:SEQ]:SLOP edge of a signal Delay between recognition of trigger event...
  • Page 493 SYSTem Subsystem Table 12-12 cdma2000: Power meter presets: Window/Measurement settings (continued) Function Setting Single Channel Dual Channel Feed Gate 1 Channel A Gate 1 primary channel Measurement Upper window/lower measurement (UL) Feed Measurement Lower window/upper measurement (LU) Feed Gate 1 Channel A Gate 1 primary channel Measurement Peak...
  • Page 494 SYSTem Subsystem Table 12-13 cdma2000: Power meter presets for secondary channel sensors Secondary Channel Sensor Function No Sensor Non P-series Sensor P-seriesSensor Display setup Upper window UU single numeric Dual numeric Dual numeric Lower window Dual numeric Dual numeric Dual numeric Upper window/lower measurement (UL) Feed Gate 1 primary channel...
  • Page 495 SYSTem Subsystem W-CDMA The W-CDMA set-up provides: – Average power in a W-CDMA signal (bandwidth <=5 MHz) – Peak power and peak-to-average ratio of the signal over a defined, statistically valid number of samples. The reading is continuously refreshed. This indicates how W-CDMA channel loading affects peak power and power distribution.
  • Page 496: Table 12-14 W-Cdma: Power Meter Presets

    SYSTem Subsystem Table 12-14 W-CDMA: Power meter presets (continued) Command Setting Comments INT1 Trigger source set up and acquisition TRIG[:SEQ[1]|2]:SOUR mode continuous triggering INIT:CONT Enable automatic setting of the trigger TRIG[:SEQ]:LEV:AUTO level AUTO Automatic Power level TRIG[:SEQ]:LEV Trigger event recognized on the rising TRIG[:SEQ]:SLOP edge of a signal Delay between recognition of trigger event...
  • Page 497 SYSTem Subsystem Table 12-15 W-CDMA: Power meter presets: Window/Measurement settings (continued) Function Setting Single Channel Dual Channel Measurement Upper window/lower measurement (UL) Feed Table 12-16 Measurement Table 12-16 Lower window/upper measurement (LU) Feed Gate 1 Channel A Table 12-16 Measurement Peak Table 12-16 Lower window/lower measurement (LL)
  • Page 498 SYSTem Subsystem Table 12-16 W-CDMA: Power meter presets for secondary channel sensors Function Secondary Channel Sensor No Sensor Non P-Series Sensor P-Series Sensor Display setup Upper window UU single numeric Dual numeric Dual numeric Lower window Dual numeric Dual numeric Dual numeric Upper window/lower measurement (UL) Feed...
  • Page 499 SYSTem Subsystem BLUetooth The Bluetooth set-up provides: – Average power in a Bluetooth DH1 data burst. – Peak power in the same burst – Display of RF pulse in one timeslot The measurement is started by detecting the Bluetooth RF burst using the internal RF level trigger.
  • Page 500: Table 12-17 Bluetooth: Power Meter Presets

    SYSTem Subsystem Table 12-17 BLUetooth: Power meter presets (continued) Command Setting Comments –15 dBm Power level TRIG[:SEQ]:LEV Trigger event recognized on the rising TRIG[:SEQ]:SLOP edge of a signal Delay between recognition of trigger event TRIG[:SEQ]:DEL and start of a measurement 650 µs Trigger holdoff TRIG[:SEQ]:HOLD...
  • Page 501 SYSTem Subsystem Table 12-18 BLUetooth: Power meter presets: Window/Measurement settings Function Setting Single Channel Dual Channel Display setup Upper window Channel A trace Primary channel trace Lower window Dual numeric Table 12-19 Window/measurement setup Upper window/upper measurement (UU) Feed Measurement Upper window/lower measurement (UL) Feed Measurement...
  • Page 502 SYSTem Subsystem Table 12-19 BLUetooth: Power meter presets for secondary channel sensors Function Secondary Channel Sensor No Sensor Non P-Series Sensor P-Series Sensor Display setup Lower window Dual numeric Dual numeric Dual numeric Lower window/lower measurement (LL) Feed Gate 1 primary channel1 Secondary channel Gate1 secondary channel (Channel B)
  • Page 503: Table 12-20 Mpca: Power Meter Presets

    SYSTem Subsystem Table 12-20 MPCA: Power meter presets (continued) Command Setting Comments Gate 1: 10 ms Length of time gated period for time gated [SENS[1]]|SENS2:SWE[1]|2|3|4:TIME Gates 2 - 4: 0 measurements. Trigger setup INT1 Trigger source set up and acquisition TRIG[:SEQ[1]|2]:SOUR mode continuous triggering INIT:CONT...
  • Page 504 SYSTem Subsystem Table 12-21 MPCA: Power meter presets: Window/Measurement settings (continued) Function Setting Single Channel Dual Channel Window/measurement setup Upper window/upper measurement (UU) Feed Gate 1 Channel A Gate 1 primary channel Measurement Upper window/lower measurement (UL) Feed Table 12-2 Measurement Table 12-22 Lower window/upper measurement (LU)
  • Page 505 SYSTem Subsystem Table 12-22 MCPA: Power meter presets for secondary channel sensors (continued) Function Secondary Channel Sensor No Sensor Non P-Series Sensor P-Series Sensor Measurement Peak Peak Lower window/upper measurement (LU) Gate1 secondary channel Feed Gate 1 primary channel Gate 1 primary channel (Channel B) Measurement Peak...
  • Page 506: Table 12-23 Radar: Power Meter Presets

    SYSTem Subsystem Table 12-23 RADAR: Power meter presets (continued) Command Setting Comments [SENS[1]]|SENS2:SWE[1]|2|3|4:OFF:TIME Gate 1: 0 Delay between trigger point and time Gate 2: 0 gated period. Gate 3: 750 ns Gate 4: 0 Gate 1: 1.0 µs Length of time gated period for time gated [SENS[1]]|SENS2:SWE[1]|2|3|4:TIME Gate 2: 250 ns measurements.
  • Page 507: Table 12-24 Radar: Power Meter Presets: Window/Measurement Settings

    SYSTem Subsystem Table 12-24 RADAR: Power meter presets: Window/Measurement settings Function Setting Single Channel Dual Channel Display setup Upper window Channel A trace Table 12-25 Lower window Dual numeric Dual numeric Window/measurement setup Upper window/upper measurement (UU) Feed Gate 1 Channel A Table 12-25 Measurement Pk-to-Avg...
  • Page 508 SYSTem Subsystem Table 12-25 RADAR: Power meter presets for secondary channel sensors Function Secondary Channel Sensor No Sensor Non P-Series Sensor P-Series Sensor Display setup Upper window Primary Channel Trace Dual numeric Dual numeric Lower window Dual numeric Dual numeric Dual numeric Upper window/upper measurement (UU) Feed...
  • Page 509: Table 12-26 802.11A And Hiperlan2: Power Meter Presets

    SYSTem Subsystem Table 12-26 802.11a and HiperLan2: Power meter presets Command Setting Comments Frequency +5200.000 MHz Frequency setting [SENS[1]]|SENS2:FREQ[:CW|:FIX] Sensor measurement mode NORM Measurement mode [SENS[1]]|SENS2:DET:FUNC Sensor video bandwidth setup N1921/2A: HIGH Sensor video bandwidth [SENS[1]]|SENS2:BAND|BWID:VID Gate Setup Gate 1: 0 Delay between trigger point and time [SENS[1]]|SENS2:SWE[1]|2|3|4:OFF:TIME Gates 2 - 4: 0...
  • Page 510: Table 12-27 802.11A And Hiperlan2: Power Meter Presets: Window/Measurement Settings

    SYSTem Subsystem Table 12-27 802.11a and HiperLan2: Power meter presets: Window/Measurement settings Function Setting Single Channel Dual Channel Display setup Upper window UU Single Numeric UU Single Numeric Lower window Dual numeric Table 12-28 Window/measurement setup Upper window/upper measurement (UU) Feed Gate 1 Channel A Gate 1 primary channel...
  • Page 511: Table 12-28 802.11A And Hiperlan2: Power Meter Presets For Secondary Channel Sensors

    SYSTem Subsystem Table 12-28 802.11a and HiperLan2: Power meter presets for secondary channel sensors Function Secondary Channel Sensor No Sensor Non P-Series Sensor P-Series Sensor Display setup Upper window UU Single numeric Dual numeric Dual numeric Lower window Dual numeric Dual numeric Dual numeric Upper window/lower measurement (UL)
  • Page 512: Table 12-29 802.11B/G: Power Meter Presets

    SYSTem Subsystem Table 12-29 802.11b/g: Power meter presets Command Setting Comments Frequency +2.400 GHz Frequency setting [SENS[1]]|SENS2:FREQ[:CW|:FIX] Sensor measurement mode NORM Measurement mode [SENS[1]]|SENS2:DET:FUNC Sensor video bandwidth setup N1921/2A: HIGH Sensor video bandwidth [SENS[1]]|SENS2:BAND|BWID:VID Gate Setup Gate 1: 0 Delay between trigger point and time [SENS[1]]|SENS2:SWE[1]|2|3|4:OFF:TIME Gates 2 - 4: 0 gated period.
  • Page 513 SYSTem Subsystem [a] The Range setting in Table 12-9 is only applicable for E-Series power sensor. Table 12-30 802.11b/g: Power meter presets: Window/Measurement settings Function Setting Single Channel Dual Channel Display setup Upper window UU Single Numeric UU Single Numeric Lower window Dual numeric Table 12-31...
  • Page 514: Table 12-31 802.11B/G: Power Meter Presets For Secondary Channel Sensors

    SYSTem Subsystem Table 12-31 802.11b/g: Power meter presets for secondary channel sensors Function Secondary Channel Sensor No Sensor Non P-Series Sensor P-Series Sensor Display setup Upper window UU Single numeric Dual numeric Dual numeric Lower window Dual numeric Dual numeric Dual numeric Upper window/lower measurement (UL) Feed...
  • Page 515: Table 12-32 1Xev-Do: Power Meter Presets

    SYSTem Subsystem Table 12-32 1xeV-DO: Power meter presets Command Setting Comments Frequency +1900.000 MHz Frequency setting [SENS[1]]|SENS2:FREQ[:CW|:FIX] Sensor measurement mode NORM Measurement mode [SENS[1]]|SENS2:DET:FUNC Sensor video bandwidth setup N1921/2A: LOW Sensor video bandwidth [SENS[1]]|SENS2:BAND|BWID:VID Gate Setup Gate 1: 10 µs Delay between trigger point and time [SENS[1]]|SENS2:SWE[1]|2|3|4:OFF:TIME Gates 2 - 4: 0...
  • Page 516: Table 12-33 1 Exv-Do: Power Meter Presets: Window/Measurement

    SYSTem Subsystem Table 12-32 1xeV-DO: Power meter presets (continued) Command Setting Comments Trace setup – Delay between delayed trigger point and 40 µs [SENS[1]]|SENS2:TRAC:OFFS:TIME the start of the trace <numeric_value> 1 ms Length of the trace [SENS[1]]|SENS2:TRAC:TIME <numeric_value> [a] The Range setting in Table 12-32 is only applicable for E-Series power sensor.
  • Page 517 SYSTem Subsystem Table 12-33 1 exV-DO: Power meter presets: Window/Measurement settings Function Setting Single Channel Dual Channel Feed Gate 1 Channel A Table 12-34 Measurement Pk-to-Avg Table 12-34 [a] For further information refer to “Primary and Secondary Channels” on page 473. Keysight N8262A Programming Guide...
  • Page 518 SYSTem Subsystem Table 12-34 1exV-DO: Power meter presets for secondary channel sensors Function Secondary Channel Sensor No Sensor Non P-Series Sensor P-Series Sensor Display setup Lower window Dual numeric Dual numeric Dual numeric Lower window/lower measurement (LL) Feed Gate 1 primary channel Secondary channel Gate1 secondary channel (Channel B)
  • Page 519: Table 12-35 1Exv-Dv: Power Meter Presets

    SYSTem Subsystem Table 12-35 1exV-DV: Power meter presets (continued) Command Setting Comments Gate 1: 810 µs Length of time gated period for time gated [SENS[1]]|SENS2:SWE[1]|2|3|4:TIME Gates 2 - 4: 0 measurements. Trigger setup INT1 Trigger source set up and acquisition TRIG[:SEQ[1]|2]:SOUR mode continuous triggering INIT:CONT...
  • Page 520: Table 12-36 1Xev-Dv: Power Meter Presets: Window/Measurement

    SYSTem Subsystem Table 12-36 1xeV-DV: Power meter presets: Window/Measurement settings Function Setting Single Channel Dual Channel Display setup Upper window Channel A trace Primary channel trace Lower window Dual numeric Table 12-37 Window/measurement setup Upper window/upper measurement (UU) Feed Measurement Upper window/lower measurement (UL) Feed Measurement...
  • Page 521 SYSTem Subsystem Table 12-37 1xeV-DV: Power meter presets for secondary channel sensors Function Secondary Channel Sensor No Sensor Non P-Series Sensor P-Series Sensor Display setup Lower window Dual numeric Dual numeric Dual numeric Lower window/lower measurement (LL) Feed Gate 1 primary channel Secondary channel Gate 1 secondary channel (Channel B)
  • Page 522: Table 12-38 Td-Scdma: Power Meter Presets

    SYSTem Subsystem Table 12-38 TD-SCDMA: Power meter presets (continued) Command Setting Comments Gate 1: 810 µs Length of time gated period for time gated [SENS[1]]|SENS2:SWE[1]|2|3|4:TIME Gates 2 - 4: 0 measurements. Trigger setup INT1 TRIG[:SEQ[1]|2]:SOUR Trigger source set up and acquisition mode continuous triggering INIT:CONT Enable automatic setting of the trigger...
  • Page 523 SYSTem Subsystem Table 12-39 TD-SCDMA: Power meter presets: Window/Measurement settings Function Setting Single Channel Dual Channel Display setup Upper window Channel A trace Primary channel trace Lower window Dual numeric Table 12-40 Window/measurement setup Upper window/upper measurement (UU) Feed Measurement Upper window/lower measurement (UL) Feed Measurement...
  • Page 524: Figure 12-2 A Trace Display Of The Active Timeslots

    SYSTem Subsystem Table 12-40 TD-SCDMA: Power meter presets: Window/Measurement settings Function Secondary Channel Sensor No Sensor Non P-Series Sensor P-Series Sensor Display setup Lower window Dual numeric Dual numeric Dual numeric Lower window/lower measurement (LL) Feed Gate 1 primary channel Secondary channel Gate1 secondary channel (Channel B)
  • Page 525: Table 12-41 Nadc: Power Meter Presets

    SYSTem Subsystem The following table shows the power meter presets when <character_data> is set to NADC. Commands not listed are preset according to their DEFault values (for further information refer to Table 12-1): Table 12-41 NADC: Power meter presets Command Setting Comments Frequency...
  • Page 526: Table 12-42 Nadc: Power Meter Presets: Window/Measurement

    SYSTem Subsystem Table 12-41 NADC: Power meter presets (continued) Command Setting Comments Auto range off [SENS[1]]|SENS2:POW:AC:RANG:AUTO UPPER Range set to upper [SENS[1]]|SENS2:POW:AC:RANG Step detection Step detection enabled [SENSe[1]]|SENS2:AVER:SDET Trace setup +20 dBm Maximum power SENSe[1]|2:TRAC:LIM:UPP -35 dBm Minimum power SENSe[1]|2:TRAC:LIM:LOW -0.2 ms Delay between delayed trigger point and [SENS[1]]|SENS2:TRAC:OFFS:TIME...
  • Page 527 SYSTem Subsystem Table 12-42 NADC: Power meter presets: Window/Measurement settings (continued) Function Setting Single Channel Dual Channel Measurement Lower window/upper measurement (LU) Feed Gate 1 Channel A Gate 1 primary channel Measurement Lower window/lower measurement (LL) Feed Gate 2 Channel A Table 12-43 Measurement Table 12-43...
  • Page 528 SYSTem Subsystem iDEN The iDEN set-up provides: – Average power in one iDEN training and data pulse – Peak-to-average one iDEN training and data pulse – Average power in a 90ms iDEN frame The measurement is started by detecting the iDEN training burst—for example the burst emitted by a mobile—using the internal RF level trigger.
  • Page 529: Table 12-44 Iden: Power Meter Presets

    SYSTem Subsystem Table 12-44 iDEN: Power meter presets (continued) Command Setting Comments Trigger setup INT1 TRIG[:SEQ[1]|2]:SOUR Trigger source set up and acquisition mode continuous triggering INIT:CONT Disable automatic setting of the trigger TRIG[:SEQ]:LEV:AUTO level -15 dBm Automatic Power level TRIG[:SEQ]:LEV Trigger event recognized on the rising TRIG[:SEQ]:SLOP edge of a signal...
  • Page 530: Table 12-45 Iden: Power Meter Presets: Window/Measurement Settings

    SYSTem Subsystem [a] The Range setting in Table 12-44 is only applicable for E-Series power sensor. Table 12-45 iDEN: Power meter presets: Window/Measurement settings Function Setting Single Channel Dual Channel Display setup Upper window UU single numeric Table 12-46 Lower window Dual numeric Table 12-46 Window/measurement setup...
  • Page 531 SYSTem Subsystem Table 12-46 iDEN: Power meter presets for secondary channel sensors Function Secondary Channel Sensor No Sensor Non P-Series Sensor P-Series Sensor Display setup Upper window UU single numeric Dual numeric Dual numeric Lower window Dual numeric Dual numeric Dual numeric Upper window/lower measurement (UL) Feed...
  • Page 532: Table 12-47 Dvb: Power Meter Presets

    SYSTem Subsystem The following table shows the power meter presets when <character_data> is set to DVB. Commands not listed are preset according to their DEFault values (for further information refer to Table 12-1). Table 12-47 DVB: Power meter presets Command Setting Comments Frequency...
  • Page 533: Table 12-48 Dvb: Power Meter Presets: Window/Measurement Settings

    SYSTem Subsystem Table 12-47 DVB: Power meter presets (continued) Command Setting Comments Range Auto range off [SENS[1]]|SENS2:POW:AC:RANG:AUTO UPPER Range set to upper [SENS[1]]|SENS2:POW:AC:RANG Step detection Step detection enabled [SENSe[1]]|SENS2:AVER:SDET [a] The Range setting in Table 12-47 is only applicable for E-Series power sensor. Table 12-48 DVB: Power meter presets: Window/Measurement settings Function...
  • Page 534 SYSTem Subsystem Table 12-48 DVB: Power meter presets: Window/Measurement settings (continued) Function Setting Single Channel Dual Channel Feed Gate 2 Channel A Table 12-49 Measurement Table 12-49 [a] For further information refer to “Primary and Secondary Channels” on page 473. Table 12-49 DVB: Power meter presets for secondary channel sensors Function...
  • Page 535: System:version

    SYSTem Subsystem SYSTem:VERSion? This query returns the version of SCPI used in the power meter. The response is in the form of XXXX.Y, where XXXX is the year and Y is the version number. Syntax :VERS SYST Example This command queries which version of SCPI SYST:VERS? is used in the power meter.
  • Page 536 SYSTem Subsystem THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK. Keysight N8262A Programming Guide...
  • Page 537 Keysight N8262A P-Series Modular Power Meter Programming Guide TRACe Subsystem TRACe Subsystem TRACe[1]|2[:DATA]? <character_data> TRACe[1]|2:DEFine:DURation:REFerence<numeric_value> TRACe[1]|2:DEFine:TRANsition:REFerence <numeric_value>, <numeric_value> TRACe[1]|2:MEASurement:INSTant:REFerence? <numeric_value> TRACe[1]|2:MEASurement:PULSe[1]|...|10:DURation? TRACe[1]|2:MEASurement:PULSe[1]|...|10:PERiod? TRACe[1]|2:MEASurement:PULSe[1]|...|10:SEParation? TRACe[1]|2:MEASurement:TRANsition[1]|...|10:NEGative:DURation? TRACe[1]|2:MEASurement:TRANsition[1]|...|10:NEGative:OCCurrence? TRACe[1]|2:MEASurement:TRANsition[1]|...|10:POSitive:DURation? TRACe[1]|2:MEASurement:TRANsition[1]|...|10:POSitive:OCCurrence? TRACe[1]|2:MEASurement:REFerence? <numeric_value> TRACe[1]|2:STATe <boolean> TRACe[1]|2:UNIT <character_data> This chapter explains how to use the TRACe command subsystem to configure and read back the measured power trace.
  • Page 538: Trace Subsystem

    TRACe Subsystem TRACe Subsystem The TRACe subsystem is used to: – Specify the type of trace to be captured. – Enable/disable trace capture. – Specify the trace units. There are two pre-defined TRACE blocks: – TRACe1: associated with Channel A –...
  • Page 539 TRACe Subsystem Keyword Parameter Form Notes Page [query only] page 554 :DURation? [query only] page 555 :OCCurrence? :POSitive [query only] page 556 :DURation? [query only] page 557 :OCCurrence? [query only] page 558 :REFerence? <numeric_value> page 560 :STATe <boolean> page 562 :UNIT <character_data>...
  • Page 540: Trace[1]|2[:Data]?

    TRACe Subsystem TRACe[1]|2[:DATA]? <character_data> This query returns trace data from the specified channel. The trace resolution is determined by <character_data>. Data is returned in IEEE 488.2 arbitrary block program data format as follows: #xyyy..yddd....ddd<LF> The number of data bytes (d) Line feed character contained in the block.
  • Page 541: Parameters

    TRACe Subsystem Parameters Item Description/Defaul t Range of Values character_data – HRESolution: high resolution. The complete capture buffer at the internal HRES sample rate. The number of points in this trace is not fixed, as it is affected by the MRES SENS:TRACe:TIMe setting.
  • Page 542: Trace[1]|2:Define:duration:reference

    TRACe Subsystem TRACe[1]|2:DEFine:DURation:REFerence<numeric_value> This command defines the reference levels to be used in the calculation of pulse durations. This allows pulse duration measurements between non-standard reference levels. This is a configuration command independent of the sensors. Syntax Space :DUR :REF numeric_value TRAC :DEF...
  • Page 543: Example

    TRACe Subsystem Example This command sets trace 1 pulse duration TRAC1:DEF:DUR:REF 25 measurements to look for the 25 % reference levels. This command sets trace 1 pulse duration TRAC1:DEF:DUR:REF DEF measurements to look for the 50 % reference levels. Reset condition On reset, the reference level will become 50 %, which is the default value (DEF).
  • Page 544: Trace[1]|2:Define:transition:reference

    TRACe Subsystem TRACe[1]|2:DEFine:TRANsition:REFerence <numeric_value>, <numeric_value> This command defines the reference levels to be used in the calculation of transition durations and occurrences. This allows transition measurements between non-standard reference levels and it is a configuration command that independent of sensors. Syntax TRAC numeric_value...
  • Page 545: Example

    TRACe Subsystem Example This command sets trace 1 transition TRAC1:DEF:TRAN:REF 1,18 measurements to look for the 1 % and 81 % reference levels. This command sets trace 1 transition TRAC1:DEF:TRAN:REF DEF,DEF measuremetns to look for the 10 % and 90 % reference levels.
  • Page 546: Trace[1]|2:Measurement:instant:reference?

    TRACe Subsystem TRACe[1]|2:MEASurement:INSTant:REFerence? <numeric_value> This command returns the time instant at which the power waveform intersects the reference level supplied as the command parameter. This allows the time instant used to calculate the pulse parameters to be found. It also allows calculation of transition between non-standard reference levels.
  • Page 547 TRACe Subsystem Example This command return the time instant for TRAC1:MEAS:INST:REF? 25 trace 1 when the power transitioned through 25 % reference level. Error Messages – If P-Series power sensor is not present, the error –241, “Hardware Missing” occurs. Keysight N8262A Programming Guide...
  • Page 548: Trace[1]|2:Measurement:pulse[1]|...|10:Duration

    TRACe Subsystem TRACe[1]|2:MEASurement:PULSe[1]|...|10:DURation? This command returns the difference between a pulse and next transition occurrence instants. As power pulses are by definition positive pulses, the pulse duration is the time difference between positive and negative transitions of one pulse. Algorithm If the first transition in the trace is positive, then PULSe:DURation = time the first negative transition occurs -time the first positive...
  • Page 549: Error Messages

    TRACe Subsystem Error Messages – If a P-Series sensor is not connected, error –241, “Hardware missing” occurs. – If a P-Series sensor is connected and Free Run trigger acquisition is selected, error –221, “Settings conflict” occurs. TIf you attempt to measure a pulse out of the range of the capture, for example, NOTE measure the 5th pulse and there are only 4 pulses displayed, the power meter returns #0##9.91E37 as the result.
  • Page 550: Trace[1]|2:Measurement:pulse[1]|...|10:Period

    TRACe Subsystem TRACe[1]|2:MEASurement:PULSe[1]|...|10:PERiod? This command returns the pulse period. This is the time difference between two consecutive transition occurrences of the same polarity. The period is equal to the sum of the pulse separation and the pulse duration. Algorithm If the first transition in the trace is positive, then PULSe:PERiod = time the second positive transition occurrence -time the first positive transition occurs...
  • Page 551 TRACe Subsystem Error Messages – If a P-Series sensor is not connected, error –241, “Hardware missing” occurs. – If a P-Series sensor is connected and Free Run trigger acquisition is selected, error –221, “Settings conflict” occurs. TIf you attempt to measure a pulse out of the range of the capture, for example, NOTE measure the 5th pulse and there are only 4 pulses displayed, the power meter returns #0##9.91E37 as the result.
  • Page 552: Trace[1]|2:Measurement:pulse[1]|...|10:Separation

    TRACe Subsystem TRACe[1]|2:MEASurement:PULSe[1]|...|10:SEParation? This command returns the time difference of the n and (n+1) pulses found on a trace. As power pulses are by definition positive pulses, the pulse separation is the time difference between negative transition of one pulse and the positive transition of the next pulse.
  • Page 553 TRACe Subsystem Error Messages – If a P-Series sensor is not connected, error –241, “Hardware missing” occurs. – If a P-Series sensor is connected and Free Run trigger acquisition is selected, error –221, “Settings conflict” occurs. TIf you attempt to measure a pulse out of the range of the capture, for example, NOTE measure the 5th pulse and there are only 4 pulses displayed, the power meter returns #0##9.91E37 as the result.
  • Page 554: Trace[1]|2:Measurement:transition[1]|...|10:Negative:duration

    TRACe Subsystem TRACe[1]|2:MEASurement:TRANsition[1]|...|10:NEGative:DURation? This command returns the n negative transition duration found on a trace. Syntax :TRAN TRAC :MEAS :NEG :DUR 2|...|10 Reset Condition On reset, this parameter is not affected. Example This command returns the 8th negative TRAC:MEAS:TRAN8:NEG:DUR? transition duration found on trace 1. Error Messages –...
  • Page 555: Syntax

    TRACe Subsystem TRACe[1]|2:MEASurement:TRANsition[1]|...|10:NEGative:OCCurrence? This command returns the position, relative to the trigger instant, of the n occurrence of a negative transition found on a trace. Syntax :TRAN TRAC :MEAS :NEG :OCC 2|...|10 Reset Condition On reset, this parameter is not affected. Example This command returns the position, relative to TRAC2:MEAS:TRAN7:NEG:OCC?
  • Page 556: Trace[1]|2:Measurement:transition[1]|...|10:Positive:duration

    TRACe Subsystem TRACe[1]|2:MEASurement:TRANsition[1]|...|10:POSitive:DURation? This command returns the n positive transition duration found on a trace. Syntax TRAC :MEAS :TRAN :POS :DUR 2|...|10 Reset Condition On reset, this parameter is not affected. Example This command returns the 10th positive TRAC:MEAS:TRAN10:POS:DUR? transition duration found on trace 1. Error Messages –...
  • Page 557: Syntax

    TRACe Subsystem TRACe[1]|2:MEASurement:TRANsition[1]|...|10:POSitive:OCCurrence? This command returns the position, relative to the trigger instant, of the n occurrence of a positive transition found on a trace. Syntax :TRAN TRAC :MEAS :POS :OCC 2|...|10 Reset Condition On reset, this parameter is not affected. Example This command returns the position, relative TRAC2:MEAS:TRAN:POS:OCC?
  • Page 558: Trace[1]|2:Measurement:reference?

    TRACe Subsystem TRACe[1]|2:MEASurement:REFerence? <numeric_value> This command is used to find the reference power level. This provides the reference power level to calculate the pulse parameters. Commonly used reference levels are 0 %, 10 %, 50 %, 90 %, and 100 %. You can set the reference level to measure overshoot at 125 % and undershoot at –25 %.
  • Page 559: Example

    TRACe Subsystem Example This command returns the high state TRAC2:MEAS:REF? 100 power for trace 2. Error Messages – If a P-Series sensor is not connected, error –241, “Hardware missing” occurs. – If a P-Series sensor is connected and Free Run trigger acquisition is selected, error –221, “Settings conflict”...
  • Page 560: Trace[1]|2:State

    TRACe Subsystem TRACe[1]|2:STATe <boolean> This command enables or disables trace capture for the specified channel. Syntax Space 0|OFF TRAC :STAT 1|ON Example This command enables trace capture for TRAC2:STAT 1 Channel B. Reset Condition On reset trace capture is set to OFF. Query TRACe[1]|2:STATe? The query command enters a 1 or 0 into the output buffer indicating whether or...
  • Page 561: Query Example

    TRACe Subsystem Query Example This command queries the current state TRAC1:STAT? of trace capture for Channel A. Error Messages – If a P-Series sensor is not connected, error –241, “Hardware missing” occurs. Keysight N8262A Programming Guide...
  • Page 562: Trace[1]|2:Unit

    TRACe Subsystem TRACe[1]|2:UNIT <character_data> This command sets the units for the trace for the specified channel This command is included for compatibility purposes only. It has the same NOTE purpose as [SENSe[1]]|SENSe2:TRACe:UNIT <character_data>, which should be the preferred command. Syntax TRAC Space :UNIT...
  • Page 563: Reset Condition

    TRACe Subsystem Reset Condition On reset the units are set to dBm. Query TRACe[1]|2:UNIT? The query command returns the current value of character_data. Query Example This command queries the current trace TRAC2:UNIT? units for Channel B. Keysight N8262A Programming Guide...
  • Page 564 TRACe Subsystem THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK. Keysight N8262A Programming Guide...
  • Page 565: Trigger Subsystem

    Keysight N8262A P-Series Modular Power Meter Programming Guide TRIGger Subsystem TRIGger Subsystem ABORt[1]|2] INITiate Commands INITiate[1]|2:CONTinuous <boolean> INITiate[1]|2[:IMMediate] INITiate:CONTinuous:ALL <boolean> INITiate:CONTinuous:SEQuence[1]|2 <boolean> INITiate[:IMMediate]:ALL INITiate[:IMMediate]:SEQuence[1]|2 TRIGger Commands TRIGger[1]|2:DELay:AUTO <boolean> TRIGger[1]|2[:IMMediate] TRIGger[1]|2:SOURce BUS|EXTernal|HOLD|IMMediate|INTernal[[1]|2] TRIGger[:SEQuence]:DELay <numeric_value> TRIGger[:SEQuence]:HOLDoff <numeric_value> TRIGger[:SEQuence]:HYSTeresis <numeric_value> TRIGger[:SEQuence]:LEVel <numeric_value> TRIGger[:SEQuence]:LEVel:AUTO <boolean> TRIGger[:SEQuence]:SLOPe <character_data>...
  • Page 566 TRIGger Subsystem TRIGger Subsystem The TRIGger subsystem is used to synchronize device actions with events. It includes the ABORt, INITiate and TRIGger commands. These are all at the root level in the command hierarchy but they are grouped here because of their close functional relationship.
  • Page 567 TRIGger Subsystem Keyword Parameter Form Notes Page page 590 :HYSTeresis <numeric_value> page 592 :LEVel <numeric_value> page 594 :AUTO <boolean> page 596 :SLOPe <character_data> [:SEQuence[1]|2] page 597 :COUNt <numeric_value> :DELay page 599 :AUTO <boolean> [no query] page 601 :IMMediate page 602 :SOURce BUS|EXTernal|HOLD| IMMediate|INTernal[[1]|2]...
  • Page 568: Abort[1]|2]

    TRIGger Subsystem ABORt[1]|2] This command removes the specified channel from the wait for trigger state and places it in the idle state. It does not affect any other settings of the trigger system. When the INITiate command is sent, the trigger system responds as it did before ABORt was executed.
  • Page 569: Initiate Commands

    TRIGger Subsystem INITiate Commands Initiate commands allow you to place the power meter in the wait for trigger state. The INITiate commands are overlapped, that is, the power meter can continue parsing and executing subsequent commands while initiated. Note that the pending operation flag is set, when the power meter enters an idle state and the flag is cleared when it re-enters the idle state.
  • Page 570: Initiate[1]|2:Continuous

    TRIGger Subsystem INITiate[1]|2:CONTinuous <boolean> This command sets the power meter for either a single trigger cycle or continuous trigger cycles. A trigger cycle means that the power meter exits the wait for trigger state and starts a measurement. When entering local mode, if TRIGger[:SEQuence[1]|2]:SOURce is set to INT[[1]|2] or EXT, INITiate:CONTinuous is not changed.
  • Page 571: Example

    TRIGger Subsystem Example This command places Channel B in the wait INIT2:CONT ON for trigger state. Reset Condition On reset (*RST), this command is set to OFF. On preset (SYSTem:PRESet) and instrument power-up, when entering local mode, if TRIGger[:SEQuence[1]|2]:SOURce is set to INT[[1]|2] or EXT, INITiate:CONTinuous is not changed.
  • Page 572: Initiate[1]|2[:Immediate]

    TRIGger Subsystem INITiate[1]|2[:IMMediate] This command sets the power meter in the wait for trigger state. When a trigger is received, the measurement is taken and the result placed in the power meter memory. If TRIGger:SOURce is set to IMMediate the measurement begins as soon as INITiate:IMMediate is executed.
  • Page 573: Initiate:continuous:all

    TRIGger Subsystem INITiate:CONTinuous:ALL <boolean> Sets all trigger sequences to be continuously initiated. If INITiate:CONTinuous:ALL is set to: – ON, trigger sequences are set to be continuously initiated – OFF, trigger sequences are not set to be continuously initiated Syntax Space INIT :CONT :ALL...
  • Page 574: Query

    TRIGger Subsystem Query INITiate:CONTinuous:ALL? The query enters a 1 or 0 into the output buffer. – 1 is returned when trigger sequences are set to be continuous – 0 is returned when trigger sequences are not set to be continuous Query Example This command queries whether both INIT:CONT:ALL?
  • Page 575: Initiate:continuous:sequence[1]|2

    TRIGger Subsystem INITiate:CONTinuous:SEQuence[1]|2 <boolean> This command sets the power meter for either a single trigger cycle or continuous trigger cycles. A trigger cycle means that the power meter exits the wait for trigger state and starts a measurement. When entering local mode, INITiate:CONTinuous is set to ON.
  • Page 576: Reset Condition

    TRIGger Subsystem Reset Condition On reset (*RST), this command is disabled. On preset (SYSTem:PRESet) and instrument power-up, this command is enabled. Query INITiate[1]|2:CONTinuous:SEQuence? The query enters a 1 or 0 into the output buffer. – 1 is returned when there is continuous triggering –...
  • Page 577: Initiate[:Immediate]:All

    TRIGger Subsystem INITiate[:IMMediate]:ALL This command initiates all trigger sequences. Syntax :IMM :ALL INIT Example This command initiates all trigger INIT:IMM:ALL sequences. Error Messages If the power meter is not in the idle state or INITiate:CONTinuous is ON, error –213, “INIT ignored” occurs. Keysight N8262A Programming Guide...
  • Page 578: Initiate[:Immediate]:Sequence[1]|2

    TRIGger Subsystem INITiate[:IMMediate]:SEQuence[1]|2 This command sets the power meter in the wait for trigger state. When a trigger is received, the measurement is taken and the result placed in the power meter memory. If TRIGger:SOURce is set to IMMediate the measurement begins as soon as INITiate:IMMediate is executed.
  • Page 579: Trigger Commands

    TRIGger Subsystem TRIGger Commands TRIGger commands control the behavior of the trigger system. The following commands are described in this section: TRIGger[1]|2:DELay:AUTO <boolean> TRIGger[1]|2:SOURce BUS|IMMediate|HOLD TRIGger[1]|2[:IMMediate] TRIGger[:SEQuence]:DELay <numeric_value> TRIGger[:SEQuence]:HOLDoff <numeric_value> TRIGger[:SEQuence]:HYSTeresis <numeric_value> TRIGger[:SEQuence]:LEVel <numeric_value> TRIGger[:SEQuence]:LEVel:AUTO <boolean> TRIGger[:SEQuence]:SLOPe <character_data> TRIGger[:SEQuence[1]|2]:COUNt <numeric_value> TRIGger[:SEQuence[1]|2]:DELay:AUTO <boolean>...
  • Page 580: Trigger[1]|2:Delay:auto

    TRIGger Subsystem TRIGger[1]|2:DELay:AUTO <boolean> This command is used to determine whether or not there is a settling-time delay before a measurement is made. When this command is set to: – ON, the power meter inserts a settling-time delay before taking the requested measurement.
  • Page 581: Example

    TRIGger Subsystem Example This command enables a delay on Channel A. TRIG:DEL:AUTO ON Reset Condition On reset, TRIGger:DELay:AUTO is set to ON. Query TRIGger:DELay:AUTO? The query enters a 1 or 0 into the output buffer indicating the status of TRIGger:DELay:AUTO. –...
  • Page 582: Trigger[1]|2[:Immediate]

    TRIGger Subsystem TRIGger[1]|2[:IMMediate] This command causes a trigger to occur immediately, provided the specified channel is in the wait for trigger state. When this command is executed, the measurement result is stored in the power meter’s memory. Use FETCh? to place the measurement result in the output buffer.
  • Page 583: Syntax

    TRIGger Subsystem TRIGger[1]|2:SOURce BUS|EXTernal|HOLD|IMMediate|INTernal[[1]|2] This command configures the trigger system to respond to the specified source. This command only selects the trigger source. Use the INITiate command to place the power meter in the wait for trigger state. This command has been included for compatibility purposes. It has the same NOTE purpose as TRIGger[:SEQuence[1]|2]:SOURce BUS|EXTernal|HOLD|IMMediate|INTernal[[1]|2] which should be used in...
  • Page 584: Parameters

    TRIGger Subsystem Parameters Item Description/Defaul t Range of Values source – Available trigger sources: – BUS: the trigger source is the group execute trigger <GET> bus command, a *TRG EXTernal common command or the TRIGGER:IMMediate SCPI command. HOLDIMMediate INTernal[[1]|2] – EXTernal: the trigger source is the trigger input in the front panel. –...
  • Page 585: Query

    TRIGger Subsystem Query TRIGger:SOURce? The query returns the current trigger source, either IMM, BUS or HOLD. Query Example This command queries Channel A’s trigger TRIG:SOUR? source. Error Messages – If the master is changed to IMM, BUS or HOLD, error –221 “Settings Conflict” occurs.
  • Page 586: Trigger[:Sequence]:Delay

    TRIGger Subsystem TRIGger[:SEQuence]:DELay <numeric_value> This command sets the delay between the recognition of a trigger event and the start of a measurement. Syntax numeric_value Space TRIG :SEQ :DEL Parameters Item Description/Defaul t Range of Values numeric_value The delay between the recognition of a trigger event and –1 to 1 second the start of the measurement.
  • Page 587: Example

    TRIGger Subsystem Example This command sets a delay of 1 ms for TRIG:SEQ:DEL 0.001 Channel A. Reset Condition On reset, the trigger delay is set to 0 seconds. Query TRIGger[:SEQuence]:DELay? The query returns the current setting of the trigger delay. Query Example This command queries the trigger delay of TRIG:SEQ:DEL?
  • Page 588: Trigger[:Sequence]:Holdoff

    TRIGger Subsystem TRIGger[:SEQuence]:HOLDoff <numeric_value> This command sets the trigger holdoff in seconds. Syntax numeric_value :HOLD Space TRIG :SEQ Parameters Item Description/Defaul t Range of Values numeric_value The trigger holdoff in seconds. 1 µs to 0.4 seconds – DEF: the default value is 1 µs –...
  • Page 589 TRIGger Subsystem Example This command sets the trigger holdoff to 100 TRIG:SEQ1:HOLD 0.1 ms for Channel A. Reset Condition On reset the trigger holdoff is set to 1 µs. Query TRIGger[:SEQuence]:HOLDoff? The query returns the current trigger holdoff setting. Query Example This command queries the trigger holdoff TRIG:SEQ:HOLD? setting for Channel A.
  • Page 590: Trigger[:Sequence]:Hysteresis

    TRIGger Subsystem TRIGger[:SEQuence]:HYSTeresis <numeric_value> This command sets: – How far a signal must fall below TRIG:LEVel before a rising edge can be detected. – How far a signal must rise above TRIG:LEVel before a falling edge can be detected. Syntax TRIG :SEQ :HYST...
  • Page 591 TRIGger Subsystem Example This command sets the value to TRIG:SEQ:HYST 0.1 2 dB for Channel A. Reset Condition On reset the value is set to 0 dB. Query TRIGger[:SEQuence]:HYSTeresis? The query returns the current value in dB. Query Example This command queries the value for Channel A. TRIG:SEQ:HYST? Keysight N8262A Programming Guide...
  • Page 592: Trigger[:Sequence]:Level

    TRIGger Subsystem TRIGger[:SEQuence]:LEVel <numeric_value> This command sets the power level at which a trigger event is recognized. Syntax :LEV Space TRIG :SEQ numeric_value Parameters Item Description/Defaul t Range of Values numeric_value The power level at which a trigger event is recognized. –40 to 20 dBm –...
  • Page 593: Query

    TRIGger Subsystem Query TRIGger[:SEQuence]:LEVel? The query returns the current power level setting. Query Example This command queries the power level TRIG:SEQ1:LEV? setting for Channel A. Keysight N8262A Programming Guide...
  • Page 594: Trigger[:Sequence]:Level:auto

    TRIGger Subsystem TRIGger[:SEQuence]:LEVel:AUTO <boolean> This command enables/disables automatic setting of the trigger level. When this command is set to: – ON, automatic setting of the trigger level is enabled. – OFF, automatic setting of the trigger level is disabled. – ONCE, automatic setting of the trigger level is enabled for one trigger event only.
  • Page 595 TRIGger Subsystem Query TRIGger[:SEQuence]:LEVel:AUTO? The query enters a 1 or 0 into the output buffer indicating the status of TRIGger[:SEQuence]:LEVel:AUTO. – 1 is returned when it is ON – 0 is returned when it is OFF Query Example This command queries the setting for TRIG:SEQ:LEV:AUTO? Channel A.
  • Page 596: Trigger[:Sequence]:Slope

    TRIGger Subsystem TRIGger[:SEQuence]:SLOPe <character_data> This command specifies whether a trigger event is recognized on the rising or falling edge of a signal. Syntax character_data Space TRIG :SEQ :SLOP Parameters Item Description/Defaul t Range of Values character_data How a trigger event is recognized: POSitive –...
  • Page 597: Trigger[:Sequence[1]|2]:Count

    TRIGger Subsystem TRIGger[:SEQuence[1]|2]:COUNt <numeric_value> This command controls the path of the trigger subsystem in the upward traverse of the wait for trigger state. COUNt loops through the event detection/ measurement cycle are performed. That is, COUNt measurements are performed in response to COUNt trigger events.
  • Page 598: Example

    TRIGger Subsystem Example This command sets the number of triggered TRIG:SEQ1:COUN 10 events to 10 for the Channel A measurement cycle. Reset Condition On reset, the value is set to 1. Query TRIGger[1]|2[:SEQuence[1]|2]:COUNt? The query returns the current setting of trigger events for a specified channel. Query Example This command queries the number of TRIG:SEQ2:COUN?
  • Page 599: Trigger[:Sequence[1]|2]:Delay:auto

    TRIGger Subsystem TRIGger[:SEQuence[1]|2]:DELay:AUTO <boolean> This command is used to determine whether or not there is a settling-time delay before a measurement is made. When this command is set to: – ON, the power meter inserts a settling-time delay before taking the requested measurement and for subsequent measurements.
  • Page 600: Example

    TRIGger Subsystem Example This command enables a delay on Channel A. TRIG:SEQ:DEL:AUTO ON Reset Condition On reset, TRIGger:DELay:AUTO is set to ON. Query TRIGger:DELay:AUTO? The query enters a 1 or 0 into the output buffer indicating the status of TRIGger:DELay:AUTO. –...
  • Page 601: Trigger[:Sequence[1]|2]:Immediate

    TRIGger Subsystem TRIGger[:SEQuence[1]|2]:IMMediate This command provides a one time over-ride of the normal process of the downward path through the wait for trigger state. It causes the immediate exit of the event detection layer if the trigger system is in this layer when the command is received.
  • Page 602 TRIGger Subsystem TRIGger[:SEQuence[1]|2]:SOURce BUS|EXTernal|HOLD|IMMediate|INTernal[[1]|2] This command configures the trigger system to respond to the specified source. This command only selects the trigger source. Use the INITiate command to place the power meter in the wait for trigger state. This command has the same purpose as TRIGger[1]|2:SOURce NOTE BUS|EXTernal|HOLD|IMMediate|INTernal[[1]|2].
  • Page 603: Parameters

    TRIGger Subsystem Parameters Item Description/Defaul t Range of Values source – Available trigger sources: – BUS: the trigger source is the group execute trigger <GET> bus command, a *TRG EXTernal common command or the TRIGGER:IMMediate SCPI command. HOLD IMMediate – EXTernal: the trigger source is the trigger input in the front panel. INTernal[[1]|2] –...
  • Page 604: Query

    TRIGger Subsystem Query TRIGger[:SEQuence[1]|2]:SOURce? The query returns the current trigger source. Query Example This command queries the current trigger TRIG:SEQ1:SOUR? source for Channel A. Error Messages – If the master is changed to IMM, BUS or HOLD, error –221 “Settings Conflict” occurs.
  • Page 605: Unit Subsystem

    Keysight N8262A P-Series Modular Power Meter Programming Guide UNIT Subsystem UNIT Subsystem UNIT[1]|2|3|4:POWer <amplitude_unit> UNIT[1]|2|3|4:POWer:RATio <ratio_unit> This chapter explains how the UNIT command subsystem is used to set the power meter measurement units to Watts and % (linear), or dBm and dB (logarithmic).
  • Page 606: Figure 15-1 Measurement Display Unit Block Window

    UNIT Subsystem UNIT Subsystem The UNIT command subsystem: – Sets power measurement units to dBm or Watts. – Sets measurement ratio units to dB or % (linear). Both UNIT commands have a numeric suffix which determines which window/ measurement is set: UNIT1 upper window/upper measurement UNIT3...
  • Page 607: Unit[1]|2|3|4:Power

    UNIT Subsystem UNIT[1]|2|3|4:POWer <amplitude_unit> This command sets the power measurement units for a specified window/ measurement. The power suffix set by UNIT:POWer is used for any command which accepts a numeric value in more than one unit – UNIT1:POWer sets the power measurement units for the upper window/upper measurement.
  • Page 608 UNIT Subsystem Parameters Item Description/Defaul t Range of Values amplitude_unit The measurement unit. – The default unit is dBm Example This command sets the power measurement UNIT1:POW DBM units for the upper window/upper measurement. Reset Condition On reset, all windows/measurements are set to DBM. Query UNIT[1]|2|3|4:POWer? The query returns the current setting of the power measurement units.
  • Page 609: Unit[1]|2|3|4:Power:ratio

    UNIT Subsystem UNIT[1]|2|3|4:POWer:RATio <ratio_unit> This command sets the window/measurement ratio units. – UNIT1:POWer:RATio sets the ratio measurement units for the upper window/ upper measurement. – UNIT2:POWer:RATio sets the ratio measurement units for the lower window/ upper measurement. – UNIT3:POWer:RATio sets the ratio measurement units for the upper window/ lower measurement.
  • Page 610: Example

    UNIT Subsystem Example This command sets the ratio measurement UNIT1:POW:RAT DB units for the upper window/upper measurement. Reset Condition On reset, the value is set to DB. Query UNIT[1]|2|3|4]:POWer:RATio? The query returns the current setting of the ratio measurement units. Query Example This command queries which ratio UNIT2:POW:RAT?
  • Page 611: Service Subsystem

    Keysight N8262A P-Series Modular Power Meter Programming Guide SERVice Subsystem SERVice Subsystem SERVice:BIST:CALibrator <boolean> SERVice:BIST:CW[1]|2:LINearity SERVice:BIST:CW[1]|2:LINearity:PERRor? SERVice:BIST:CW[1]|2:ZSET:NUMber? SERVice:BIST:PEAK[1]|2:LINearity <numeric_value> SERVice:BIST:PEAK[1]|2:LINearity:PERRor? SERVice:BIST:PEAK[1]|2:ZSET SERVice:BIST:PEAK[1]|2:ZSET:NUMber? SERVice:BIST:TBASe:STATe SERVice:BIST:TBASe:STATe <boolean> SERVice:BIST:TRIGger:TEST? SERVice:CALibrator:ADJ:COUR <numeric_value> SERVice:CALibrator:ADJ:FINE <numeric_value> SERVice:LAN:PHOStname SERVice:SECure:ERASe SERVice:SENSor[1]|2:CDATe? SERVice:SENSor[1]|2:CPLace? SERVice:SENSor[1]|2:FREQuency:MAXimum? SERVice:SENSor[1]|2:FREQuency:MINimum? SERVice:SENSor[1]|2:PCALfactor <cal_factor_data> SERVice:SENSor[1]|2:POWer:AVERage:MAXimum? SERVice:SENSor[1]|2:POWer:PEAK:MAXimum? SERVice:SENSor[1]|2:POWer:USABle:MAXimum? SERVice:SENSor[1]|2:POWer:USABle:MINimum? SERVice:SENSor[1]|2:RADC?
  • Page 612 SERVice Subsystem SERVice:SENSor[1]|2:TYPE? SERVice:SNUMber <character_data> SERVice:VERSion:PROCessor <character_data> SERVice:VERSion:SYSTem <character_data> This chapter explains how the SERVice command subsystem is used to obtain and set information useful for servicing the power meter. Keysight N8262A Programming Guide...
  • Page 613 SERVice Subsystem SERVice Subsystem The SERVice command subsystem is used to load information such as the power meter processor board revision version and obtain information such as the serial number of the current sensor(s) being used. Keyword Parameter Form Notes Page SERVice :BIST...
  • Page 614 SERVice Subsystem Keyword Parameter Form Notes Page page 629 :PHOStname :SECure page 630 :ERASe :SENSor[1]|2 page 631 :CALFactor <cal_factor_data> [query only] page 631 :CDATe? [query only] page 632 :CPLace? :FREQuency [query only] page 633 :MAXimum? [query only] page 634 :MINimum? page 635 :PCALfactor <cal_factor_data>...
  • Page 615: Service:bist:calibrator

    SERVice Subsystem SERVice:BIST:CALibrator <boolean> This command enables/disables the calibrator self-test during power-up. It can be used to disable the self-test if it incorrectly indicates a failure. If a load, for example, a sensor, is connected to the calibrator port this could cause the self-test to fail. Also, if it fails the self-test, a Pop-up is displayed for 5 seconds, stating -If Ref Calibrator test fails disconnect any load attached to it and re-try test.
  • Page 616: Service:bist:cw[1]|2:Linearity

    SERVice Subsystem SERVice:BIST:CW[1]|2:LINearity This command initiates the CW linearity test. Syntax SERV :BIST :LIN Example This command enables the CW linearity test. SERV:BIST:CW:LIN Keysight N8262A Programming Guide...
  • Page 617: Service:bist:cw[1]|2:Linearity:perror

    SERVice Subsystem SERVice:BIST:CW[1]|2:LINearity:PERRor? This command returns the worst case error in the CW linearity test. Syntax SERV :BIST :LIN :PERR Example This command queries the worst case error SERV:BIST:CW:LIN:PERR? in the CW linearity test. Keysight N8262A Programming Guide...
  • Page 618: Service:bist:cw[1]|2:Zset:number

    SERVice Subsystem SERVice:BIST:CW[1]|2:ZSET:NUMber? This command returns the worst case error in the CW Zero test invoked by "SERVice:BIST:PEAK[1 2]:Z SET" Syntax SERV :BIST :ZSET :NUM Example This command queries the worst case error SERV:BIST:CW:ZSET:NUM? in the CW zero test. Keysight N8262A Programming Guide...
  • Page 619: Service:bist:peak[1]|2:Linearity

    SERVice Subsystem SERVice:BIST:PEAK[1]|2:LINearity <numeric_value> This command initiates the PEAK linearity test. Syntax numeric_value Space SERV :BIST :PEAK :LIN Parameters Item Description/Defaul t Range of Values Numeric_value Define the number of samples taken for results, default:0 0 to 8000 Example This command sets the number of samples SERV:BIST:PEAK:LIN 8000 of the PEAK linearity test to be 8000.
  • Page 620: Service:bist:peak[1]|2:Linearity:perror

    SERVice Subsystem SERVice:BIST:PEAK[1]|2:LINearity:PERRor? This command returns the PEAK linearity worst case error. Syntax SERV :BIST :PEAK :LIN :PERR Example This commands queries the PEAK linearity SERV:BIST:PEAK:LIN PERR? worst case error. Keysight N8262A Programming Guide...
  • Page 621: Service:bist:peak[1]|2:Zset

    SERVice Subsystem SERVice:BIST:PEAK[1]|2:ZSET This command initiates the zero set and noise test for both peak and CW for a channel. Syntax SERV :BIST :PEAK :ZSET Example This command enables the zero set and SERV:BIST:PEAK1:ZSET noise test for Channel A. Keysight N8262A Programming Guide...
  • Page 622: Service:bist:peak[1]|2:Zset:number

    SERVice Subsystem SERVice:BIST:PEAK[1]|2:ZSET:NUMber? This command returns the worst case error in the PEAK zero test invoked by "SERVice:BIST:PEAK[1 2]:ZSET" Syntax SERV :BIST :PEAK :ZSET :NUM Example This command queries the worst case error SERV:BIST:PEAK:ZSET:NUM? in the PEAK zero test. Keysight N8262A Programming Guide...
  • Page 623: Service:bist:tbase:state

    SERVice Subsystem SERVice:BIST:TBASe:STATe This command toggles the 10 MHz timebase out of the trigger outport. Syntax SERV :BIST :TBAS :STAT Example This command toggles the timebase out of SERV:BIST:TBAS:STAT the trigger outport. Keysight N8262A Programming Guide...
  • Page 624: Service:bist:tbase:state

    SERVice Subsystem SERVice:BIST:TBASe:STATe <boolean> This command sends a 10 MHz time base signal to the front panel trig out for testing purposes. This command overrides the OUTPut:TRIGger[:STATe] command. NOTE For example, if OUTPut:TRIGger[:STATe] is ON and the command SERV:BIST:TBAS ON is sent, this command overrides the Trigger state and sets it to OFF.
  • Page 625: Reset Condition

    SERVice Subsystem Reset Condition On reset, the signal is disabled. Query SERVice:BIST:TBASe:STAT? The query enters a 1 or 0 into the output buffer indicating the status of the 10 MHz time base testing. – 1 is returned when the signal is enabled –...
  • Page 626: Service:bist:trigger:test

    SERVice Subsystem SERVice:BIST:TRIGger:TEST? This command queries trigger in and out. – 1 is returned if the test passes – 0 is returned if the test fails Before running this command, the front panel trigger out must be jumpered to NOTE the front panel trigger in.
  • Page 627: Service:calibrator:adj:cour

    SERVice Subsystem SERVice:CALibrator:ADJ:COUR <numeric_value> This command adjust the 1 mW calibrator output in coarse scale. Syntax numeric_value Space SERV :CAL :ADJ :COUR Parameters Item Description/Defaul t Range of Values Numeric_value Adjust the 1 mW Power Reference Level Increment Coarse by 1. 0 to 1023 (Unsigned Int 16) Query The query returns the Reference Calibrator SERV:CAL:ADJ:COUR?
  • Page 628: Service:calibrator:adj:fine

    SERVice Subsystem SERVice:CALibrator:ADJ:FINE <numeric_value> This command adjust the 1 mW calibrator output in fine scale. Syntax space numeric_value :ADJ SERV :CAL :FINE Parameters Item Description/Defaul t Range of Values Numeric_value Adjust the 1 mW Power Reference Level Increment Fine by 1. 0 to 1023 (Unsigned Int 16) Query The query returns the Reference Calibrator SERV:CAL:ADJ:FINE?
  • Page 629: Service:lan:phostname

    SERVice Subsystem SERVice:LAN:PHOStname This command preset the LAN hostname to its default value. It requires the serial number to be set-up. Syntax SERV :LAN :PHOS Example The command presets the LAN hostname to SERV:LAN:PHOS its default value. Keysight N8262A Programming Guide...
  • Page 630: Service:secure:erase

    SERVice:SECure:ERASe This command erases the P-Series modular power meter’s memory, for example, before you return it to keysight Technologies for repair or calibration, of all data stored in it. The memory data erased, includes the save/recall states and power on last states.
  • Page 631: Service:sensor[1]|2:Cdate

    SERVice Subsystem SERVice:SENSor[1]|2:CDATe? This query returns the calibration date in E-Series sensors. Calibration date information is stored in the sensor’s EEPROM. Syntax SERV :SENS :CDAT Example This query returns the calibration date of the SERV:SENS2:CDATe? E-Series sensor connected to Channel B. Error Messages –...
  • Page 632: Service:sensor[1]|2:Cplace

    SERVice Subsystem SERVice:SENSor[1]|2:CPLace? This query returns the calibration place in E-Series sensors. Calibration place information is stored in the sensor’s EEPROM. Syntax SERV :SENS :CPL Example This query returns the place of calibration of SERV:SENS2:CPL? the E-Series sensor connected to Channel B. Error Messages –...
  • Page 633: Service:sensor[1]|2:Frequency:maximum

    SERVice Subsystem SERVice:SENSor[1]|2:FREQuency:MAXimum? This query returns the maximum frequency that can be measured by the currently connected sensor. It is applicable to E-Series sensors only. Maximum frequency information is stored in the sensor’s EEPROM. Syntax SERV :SENS :FREQ :MAX Example This query returns the maximum frequency SERV:SENS2:FREQ:MAX? that can be measured by the E-Series sensor...
  • Page 634: Service:sensor[1]|2:Frequency:minimum

    SERVice Subsystem SERVice:SENSor[1]|2:FREQuency:MINimum? This query returns the minimum frequency that can be measured by the currently connected sensor. It is applicable to E-Series sensors only. Minimum frequency information is stored in the sensor’s EEPROM. Syntax SERV :SENS :FREQ :MIN Example This query returns the minimum frequency SERV:SENS1:FREQ:MIN? that can be measured by the E-Series sensor...
  • Page 635: Service:sensor[1]|2:Pcalfactor

    SERVice Subsystem SERVice:SENSor[1]|2:PCALfactor <cal_factor_data> This command writes calibration factor data to, or reads calibration factor data from, the currently connected sensor. The whole calibration factor block must be written at once as a checksum is generated. The new block must not be larger than the existing block.
  • Page 636: Query Example

    SERVice Subsystem Query Example SERV:SENS:PCAL? This command returns the peak path calibration factor block for Channel A. Error Messages – If no power sensor is connected, error –241 “Hardware missing” occurs. – If INIT:CONT is not set to OFF, error –221, “Settings conflict” occurs. Keysight N8262A Programming Guide...
  • Page 637: Service:sensor[1]|2:Power:average:maximum

    SERVice Subsystem SERVice:SENSor[1]|2:POWer:AVERage:MAXimum? This query returns the maximum average power that can be measured by the currently connected sensor. It is applicable to E-Series sensors only. Maximum average power information is stored in the sensor’s EEPROM. Syntax SERV :SENS :POW :AVER :MAX Example...
  • Page 638: Service:sensor[1]|2:Power:peak:maximum

    SERVice Subsystem SERVice:SENSor[1]|2:POWer:PEAK:MAXimum? This query returns the maximum peak power that can be measured by the currently connected sensor. It is applicable to E-Series sensors only. Maximum peak power information is stored in the sensor’s EEPROM. Syntax SERV :SENS :POW :PEAK :MAX Example...
  • Page 639: Service:sensor[1]|2:Power:usable:maximum

    SERVice Subsystem SERVice:SENSor[1]|2:POWer:USABle:MAXimum? This query returns the maximum power that can be accurately measured by the currently connected sensor. It is applicable to E-Series sensors only. Maximum power information is stored in the sensor’s EEPROM. Syntax SERV :SENS :POW :USAB :MAX Example This query returns the maximum power that...
  • Page 640: Service:sensor[1]|2:Power:usable:minimum

    SERVice Subsystem SERVice:SENSor[1]|2:POWer:USABle:MINimum? This query returns the minimum power that can be accurately measured by the currently connected sensor. It is applicable to E-Series sensors only. Maximum power information is stored in the sensor’s EEPROM. Syntax SERV :POW :SENS :USAB :MIN Example This query returns the minimum power that...
  • Page 641: Service:sensor[1]|2:Radc

    SERVice Subsystem SERVice:SENSor[1]|2:RADC? This query returns a new raw uncorrected measurement in volts, as a 32 bit signed integer. Syntax SERV :SENS :RADC Example This query returns a new raw uncorrected SERV:SENS2:RADC? measurement for the sensor connected to Channel B. Error Messages –...
  • Page 642: Service:sensor[1]|2:Snumber

    SERVice Subsystem SERVice:SENSor[1]|2:SNUMber? This query returns the serial number for E-Series sensors. Serial number information is stored in the sensor’s EEPROM. Syntax SERV :SENS :SNUM Example This query returns the serial number of the SERV:SENS2:SNUM? E-Series sensor connected to Channel B. Error Messages –...
  • Page 643: Service:sensor[1]|2:Tnumber

    SERVice Subsystem SERVice:SENSor[1]|2:TNUMber? This query returns the tracking number for E-Series sensors. Tracking number information is stored in the sensor’s EEPROM. Syntax SERV :SENS :TNUM Example This query returns the serial number of the SERV:SENS2:TNUM? E-Series sensor connected to Channel B. Error Messages –...
  • Page 644: Service:sensor[1]|2:Type

    SERVice Subsystem SERVice:SENSor[1]|2:TYPE? This query identifies the sensor type connected to the power meter input channel(s). For Keysight 8480 Series sensors, either “A”, “B”, “D”, or “H” is returned. For E-Series sensors, the model number stored in EEPROM is returned Syntax SERV :SENS...
  • Page 645: Service:snumber

    SERVice Subsystem SERVice:SNUMber <character_data> This command loads the power meter with a serial number in the form GB12345678 or US12345678. Syntax Space character_data SERV :SNUM Parameters Item Description/Defaul t Range of Values character_data Details the power meter serial number in the form A to Z (uppercase) GB12345678 or US12345678.
  • Page 646: Service:version:processor

    SERVice Subsystem SERVice:VERSion:PROCessor <character_data> This command loads the power meter with the processor board revision version. Syntax Space character_data :VERS :PROC SERV Parameters Item Description/Defaul t Range of Values character_data Details the processor board revision version. A maximum A to Z (uppercase) of 20 characters can be used.
  • Page 647: Service:version:system

    SERVice Subsystem SERVice:VERSion:SYSTem <character_data> This command loads the power meter with the system version number. Syntax Space character_data SERV :VERS :SYST Parameters Item Description/Defaul t Range of Values character_data Details the system version number. A maximum of 20 A to Z (uppercase) characters can be used.
  • Page 648 SERVice Subsystem Keysight N8262A Programming Guide...
  • Page 649 SERVice Subsystem Keysight N8262A Programming Guide...
  • Page 650 SERVice Subsystem THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK. Keysight N8262A Programming Guide...
  • Page 651 Keysight N8262A P-Series Modular Power Meter Programming Guide IEEE 488.2 Command Reference SCPI Compliance Information *CLS *DDT <arbitrary block program data>|<string program data> *ESE <NRf> *ESR? *IDN? *OPC *OPT? *RCL <NRf> *RST *SAV <NRf> *SRE <NRf> *STB? *TRG *TST? *WAI This chapter contains information about the IEEE 488.2 Common Commands that the power meter supports.
  • Page 652 IEEE 488.2 Command Reference SCPI Compliance Information This chapter contains information about the SCPI Common (*) Commands that the power meter supports. It also describes the GPIB Universal Command statements which form the nucleus of GPIB programming; they are understood by all instruments in the network.
  • Page 653: Syntax

    IEEE 488.2 Command Reference *CLS The *CLS (CLear Status) command clears the status data structures. The SCPI registers (Questionable Status, Operation Status and all the other SCPI registers), the Standard Event Status Register, the Status Byte, and the Error/Event Queue are all cleared.
  • Page 654: Ddt |

    IEEE 488.2 Command Reference *DDT <arbitrary block program data>|<string program data> The *DDT (Define Device Trigger) command determines the power meter’s response to a GET (Group Execute Trigger) message or *TRG common command. This command effectively turns GET and *TRG into queries, with the measured power being returned.
  • Page 655: Reset Condition

    IEEE 488.2 Command Reference Examples of <string program data> are: – "FETCh1?", "FETCh?" and "TRIG1;FETC1" Reset Condition On reset, the <action> field of *DDT is set to *TRG. Query *DDT? The query returns the action which is performed on receipt of a GET or *TRG. This is returned as a <definite length arbitrary block response data>...
  • Page 656: Table 17-1 *Ese Mapping

    IEEE 488.2 Command Reference *ESE <NRf> The *ESE (Event Status Enable) <NRf> command sets the Standard Event Status Enable Register. This register contains a mask value for the bits to be enabled in the Standard Event Status Register. A 1 in the Enable Register enables the corresponding bit in the Status Register, a 0 disables the bit.
  • Page 657: Parameters

    IEEE 488.2 Command Reference Parameters Type Description/Defaul t Range of Values A value used to set the Standard Event Status Enable Register. 0 - 255 Query *ESE? The query returns the current contents of the Standard Event Status Enable Register. The format of the return is <NR1> in the range of 0 to 255. Keysight N8262A Programming Guide...
  • Page 658: Table 17-2 *Esr? Mapping

    IEEE 488.2 Command Reference *ESR? The *ESR? query returns the contents of the Standard Event Status Register then clears it. The format of the return is <NR1> in the range of 0 to 255. Table 17-2 shows the contents of this register. Table 17-2 *ESR? Mapping Weight...
  • Page 659: Syntax

    IEEE 488.2 Command Reference *IDN? The *IDN? query allows the power meter to identify itself. The string returned is either: Keysight Technologies,N8262A,<serial number>,A1.XX.YY Keysight Technologies,N8262A,<serial number>,A2.XX.YY where: – <serial number> uniquely identifies each power meter. – A1.XX.YY and A2.XX.YY represents the firmware revision with XX and YY representing the major and minor revisions respectively.
  • Page 660 IEEE 488.2 Command Reference *OPC The *OPC (OPeration Complete) command causes the power meter to set the operation complete bit in the Standard Event Status Register when all pending device operations have completed. Syntax *OPC Query *OPC? The query places an ASCII 1 in the output queue when all pending device operations have completed.
  • Page 661: Syntax

    IEEE 488.2 Command Reference *OPT? The *OPT? query reports the options installed in the power meter and returns: – " " empty string for a standard instrument. – "003" for an option 003 instrument. Syntax *OPT Keysight N8262A Programming Guide...
  • Page 662 IEEE 488.2 Command Reference *RCL <NRf> The *RCL <NRf> (ReCaLl) command restores the state of the power meter from the specified save/recall register. An instrument setup must have been stored previously in the specified register. Syntax Space *RCL Parameters Type Description/Defaul t Range of Values The number of the register to be recalled.
  • Page 663 IEEE 488.2 Command Reference *RST The *RST (ReSeT) command places the power meter in a known state. Refer to “SYSTem:PRESet <character_data>” on page 473 for information on reset values. Syntax *RST Keysight N8262A Programming Guide...
  • Page 664 IEEE 488.2 Command Reference *SAV <NRf> The *SAV <NRf> (SAVe) command stores the current state of the power meter in the specified register. Syntax Space *SAV Parameters Item Description/Defaul t Range of Values The number of the register that the current state of the power meter is 1 - 10 to be saved to.
  • Page 665: Table 17-3 *Sre Mapping

    IEEE 488.2 Command Reference *SRE <NRf> The *SRE <NRf> command sets the Service Request Enable register bits. This register contains a mask value for the bits to be enabled in the Status Byte Register. A 1 in the Enable Register enables the corresponding bit in the Status Byte Register;...
  • Page 666: Parameters

    IEEE 488.2 Command Reference Parameters Type Description/Defaul t Range of Values A value used to set the Service Request Enable Register. 0 - 255 Query *SRE? The query returns the contents of bits 0 to 5 and bit 7 of the Service Request Enable Register.
  • Page 667: Table 17-4 *Stb? Mapping

    IEEE 488.2 Command Reference *STB? The *STB? (STatus Byte) query returns bit 0 to 5 and bit 7 of the power meter’s status byte and returns the Master Summary Status (MSS) as bit 6. The MSS is the inclusive OR of the bitwise combination (excluding bit 6) of the Status Byte and the Service Request Enable registers.
  • Page 668: Syntax

    IEEE 488.2 Command Reference Syntax *STB Keysight N8262A Programming Guide...
  • Page 669 IEEE 488.2 Command Reference *TRG The *TRG (TRiGger) command triggers all channels that are in the wait for trigger state. It has the same effect as Group Execute Trigger (GET). Using the *DDT command may change the function of the *TRG command. Syntax *TRG Error Message...
  • Page 670 IEEE 488.2 Command Reference *TST? The *TST? (TeST) query causes the power meter to perform the self test. The test takes approximately 30 seconds. The result of the test is placed in the output queue. – 0 is returned if the test passes –...
  • Page 671 IEEE 488.2 Command Reference *WAI The *WAI (WAIt) command causes the power meter to wait until either: – All pending operations are complete – The device clear command is received – Power is cycled before executing any subsequent commands or queries. Syntax *WAI Keysight N8262A Programming Guide...
  • Page 672 IEEE 488.2 Command Reference THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK. Keysight N8262A Programming Guide...
  • Page 673 This information is subject to change without notice. Always refer to the Keysight website for the latest revision. © Keysight Technologies 2007–2019 Edition 6, May 10, 2019 Printed in Malaysia *N8262-90008* N8262-90008 www.keysight.com...

This manual is also suitable for:

N8262a

Table of Contents