Agilent Technologies N1911A Programming Guide

Agilent

N1911A/1912A

P-Series Power

Meters

Programming Guide

Agilent Technologies

© Agilent Technologies, Inc. 2006–2014

No part of this manual may be reproduced in any form or by any means (including electronic storage and retrieval or translation into a foreign language) without prior agreement and written consent from Agilent

Technologies, Inc. as governed by United

States and international copyright laws.

Manual Part Number

N1912-90008

Edition

Twelfth Edition, July 1, 2014

Printed in Malaysia

Agilent Technologies, Inc.

5301 Stevens Creek Blvd.

Santa Clara, CA 95052 USA

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, Agilent 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. Agilent shall not be liable for errors or for incidental or consequential damages in connection with the furnishing, use, or performance of this document or of any information contained herein. Should

Agilent and the user have a separate written agreement with warranty terms covering the material in this document that conflict with these terms, the warranty terms in the separate agreement shall control.

Technology Licenses

The hardware and/or software described in this document are furnished under a license and may be used or copied only in accordance with the terms of such license.

Restricted Rights Legend

U.S. Government Restricted Rights. Software and technical data rights granted to the federal government include only those rights customarily provided to end user customers. Agilent provides this customary commercial license in Software and technical data pursuant to FAR 12.211 (Technical

Data) and 12.212 (Computer Software) and, for the Department of Defense, DFARS

252.227-7015 (Technical Data - Commercial

Items) and DFARS 227.7202-3 (Rights in

Commercial Computer Software or Computer Software Documentation).

Safety Notices

C A U T I O N

A CAUTION notice denotes a hazard. It calls attention to an operating procedure, practice, or the like that, if not correctly performed or adhered to, could result in damage to the product or loss of important data. Do not proceed beyond a

CAUTION notice until the indicated conditions are fully understood and met.

WA R N I N G

A WARNING notice denotes a hazard. It calls attention to an operating procedure, practice, or the like that, if not correctly performed or adhered to, could result in personal injury or death. Do not proceed beyond a WARNING notice until the indicated conditions are fully understood and met.

N1911A/1912A P-Series Power Meters Program-

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, Agilent 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. Agilent shall not be liable for errors or for incidental or consequential damages in connection with the furnishing, use, or performance of this document or any information contained herein. Should Agilent and the user have a separate written agreement with warranty terms covering the material in this document that conflict with these terms, the warranty terms in the separate agreement shall control. Duration and conditions of warranty for this product may be superseded when the product is integrated into

(becomes a part of) other Agilent products. During the warranty period,

Agilent will, at its option, either repair or replace products which prove to be defective. The warranty period begins on the date of delivery or on the date of installation if installed by Agilent.

Restricted Rights Legend

The Software and Documentation have been developed entirely at private expense. They are delivered and licensed as “commercial computer software” as defined in DFARS 252.227-7013 (Oct 1988), DFARS

252.211-7015 (May 1991), or DFARS 252.227-7014 (Jun 1995), as a

“commercial item” as defined in FAR 2.101(a), or as “restricted computer software” as defined in FAR 52.227-19 (Jun 1987) (or any equivalent agency regulation or contract clause), whichever is applicable. You have only those rights provided for such Software and Documentation by the applicable FAR or DFARS clause or the Agilent standard software agreement for the product involved.

N1911A/1912A P-Series Power Meters Programming Guide iii

Equipment Operation

Warnings and Cautions

This guide uses warnings and cautions to denote hazards.

WA R N I N G

A WARNING notice denotes a hazard. It calls attention to an operating procedure, practice, or the like that, if not correctly performed or adhered to, could result in personal injury or loss of life. Do not proceed beyond a WARNING notice until the indicated conditions are fully understood and met.

C A U T I O N

A CAUTION notice denotes a hazard. It calls attention to an operating procedure, practice, or the like that, if not correctly performed or adhered to, could result in damage to the product or loss of important data. Do not proceed beyond a CAUTION notice until the indicated conditions are fully understood and met.

Personal Safety Considerations

This is a Safety Class I product (provided with a protective earthing ground incorporated in the power cord). The mains plug shall only be inserted in a socket outlet provided with a protective earth contact. Any interruption of the protective conductor, inside or outside the instrument, is likely to make the instrument dangerous. Intentional interruption is prohibited. If this instrument is not used as specified, the protection provided by the equipment could be impaired. This instrument must be used in a normal condition (in which all means of protection are intact) only.

No operator serviceable parts inside. Refer servicing to qualified personnel. To prevent electrical shock, do not remove covers. For continued protection against fire hazard, replace the line fuse(s) only with fuses of the same type and rating (for example, normal blow, time delay, etc.). The use of other fuses or material is prohibited.

iv N1911A/1912A P-Series Power Meters Programming Guide

General Safety Considerations

The following general safety precautions must be observed during all phases of operation of this instrument. 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. Agilent Technologies, Inc. assumes no liability for the customer’s failure to comply with these requirements.

WA R N I N G

• Before this instrument is switched on, make sure it has been properly grounded through the protective conductor of the ac power cable to a socket outlet provided with protective earth contact. Any interruption of the protective (grounding) conductor, inside or outside the instrument, or disconnection of the protective earth terminal can result in personal injury.

C A U T I O N

• Any adjustments or service procedures that require operation of the instrument with protective covers removed should be performed only by trained service personnel.

User Environment

This instrument is designed for indoor use only.

N1911A/1912A P-Series Power Meters Programming Guide v

In This Guide… vi

1

Power Meter Remote Operation

Chapter 1 describes the parameters that configure the power meter and helps you determine settings to optimize performance.

2

MEASurement Commands

Chapter 2 explains how to use the MEASure group of instructions to acquire data using a set of high level instructions.

3

CALCulate Subsystem

Chapter 3 explains how the CALCulate subsystem is used to perform post acquisition data processing.

4

CALibration Subsystem

Chapter 4 explains how the CALibration command subsystem is used to zero and calibrate the power meter.

5

DISPlay Subsystem

Chapter 5 explains how the DISPlay subsystem is used to control the selection and presentation of the windows used on the power meter’s display.

6

FORMat Subsystem

Chapter 6 explains how the FORMat subsystem is used to set a data format for transferring numeric information.

7

MEMory Subsystem

Chapter 7 explains how the MEMory command subsystem is used to create, edit and review sensor calibration tables.

8

OUTPut Subsystem

Chapter 8 explains how the OUTput command subsystem is used to switch the POWER REF output on and off.

9

PSTatistic Subsystem

Chapter 9 explains how the PSTatistic command subsystem is used to configure the settings of Complementary Cumulative

Distribution Function (CCDF), both in table and trace format.

10

SENSe Subsystem

Chapter 10 explains how the SENSe command subsystem directly affects device specific settings that are used to make measurements.

11

STATus Subsystem

Chapter 11 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” and the “Questionable Status Register”.

N1911A/1912A P-Series Power Meters Programming Guide

12

SYSTem Subsystem

Chapter 12 explains how the SYSTem command subsystem is used to return error numbers and messages from the power meter, preset the power meter, set the remote address, and query the SCPI version.

13

TRACe Subsystem

Chapter 13 explains how the TRACe command subsystem is used to configure and read back the measured power trace.

14

TRIGger Subsystem

Chapter 14 explains how the TRIGger command subsystem is used to synchronize device actions with events.

15

UNIT Subsystem

Chapter 15 explains how the UNIT command subsystem is used to set the power meter measurement units to Watts and % (linear), or dBm and dB (logarithmic).

16

SERVice Subsystem

Chapter 16 explains how the SERVice command subsystem is used to obtain and set information useful for servicing the power meter.

17

IEEE 488.2 Command Reference

Chapter 17 contains information about the IEEE488.2 Common Commands that the power meter supports.

A

Calibration Factor Block Layout

Appendix A contains information on the calibration factor block layout for E4410 Series, E9300 Series, E9320

Series and N8480 Series sensors (excluding Option CFT).

N1911A/1912A P-Series Power Meters Programming Guide vii

THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK.

viii N1911A/1912A P-Series Power Meters Programming Guide

Contents

Notices ii

General Warranty iii

Restricted Rights Legend iii

Equipment Operation iv

General Safety Considerations v

User Environment v

In This Guide… vi

1


Introduction 5

Configuring the Remote Interface 6

• Interface Selection 6

• GPIB Address 6

• LAN Configuration 7

• USB Configuration 8

Zeroing and Calibrating the P-Series Power Sensor 9

• Zeroing 9

• Calibration 9

Making Measurement 11

• Using MEASure?

12

• Using the CONFigure Command 17

• Using the Lower Level Commands 26

Using Frequency Dependent Offset Tables 27

• Overview 27

• Editing Frequency Dependent Offset Tables 29

• Selecting a Frequency Dependent Offset Table 32

• Enabling a Frequency Dependent Offset Table 32

• Making the Measurement 32

Setting the Range, Resolution and Averaging 34

• Resolution 34

• Averaging 34

• Auto Averaging Mode 35

• Filter Length 36

• Range 37

N1911A/1912A P-Series Power Meters Programming Guide ix

x

Setting Offsets 38

• Channel Offsets 38

• Display Offsets 38

Setting Measurement Limits 40

• Setting Limits 40

• Checking for Limit Failures 42

• Using STATus 43

Getting the Best Speed Performance 44

• Measurement Rate 44

• Sensor 45

• Trigger Mode 45

• Output Format 47

• Units 47

• Command Used 47

• Fast Mode 48

How Measurements are Calculated 49

Status Reporting 50

• The General Status Register Model 50

• How to Use Register 53

• The Condition Polling Method 53

• The SRQ Method 54

• Device Status Register 65

• Using the Operation Complete Commands 67

Saving and Recalling Power Meter Configurations 69

• How to Save and Recall a Configuration 69

Using Device Clear to Halt Measurements 70

An Introduction to the SCPI Language 71

• Mnemonic Forms 71

• Using a Colon (:) 71

• Using a Semicolon (;) 72

• Using a Comma (,) 72

• Using Whitespace 72

• Using “?” Commands 72

• Using “*” Commands 73

• Syntax Conventions 73


• Syntax Diagram Conventions 73

• SCPI Data Types 74

• Input Message Terminators 79

SCPI Compliance Information 81

Summary of Commands 83

Making Measurements on Wireless Communication Standards 84

• Starting a Preset Example 85

2


MEASurement Commands 89

CONFigure[1] |2|3|4?

94

CONFigure [1] |2|3|4 Commands 97

CONFigure[1]|2|3|4[:SCALar][:POWer:AC] [<expected_value>[,<resolution>[,<source list>]]] 98

CONFigure[1]|2|3|4[:SCALar][:POWer:AC]:RELative [<expected_value>[,<resolution>[,<source list>]]] 100

CONFigure[1]|2|3|4[:SCALar][:POWer:AC]:DIFFerence [<expected_value>[,<resolution>[,<source list>]]] 102

CONFigure[1]|2|3|4[:SCALar][:POWer:AC]:DIFFerence: RELative

[<expected_value>[,<resolution>[,<source list>]]] 104

CONFigure[1]|2|3|4[:SCALar][:POWer:AC]:RATio [<expected_value>[,<resolution>[,<source list>]]] 106

CONFigure[1]|2|3|4[:SCALar][:POWer:AC]:RATio: RELative[<expected_value>[,<resolution>[,<source list>]]] 108

FETCh[1]|2|3|4 Queries 110

FETCh[1]|2|3|4[:SCALar][:POWer:AC]? [<expected_value>[,<resolution>[,<source list>]]] 111

FETCh[1]|2|3|4[:SCALar][:POWer:AC]:RELative? [<expected_value>[,<resolution>[,<source list>]]] 113

FETCh[1]|2|3|4[:SCALar][:POWer:AC]:DIFFerence? [<expected_value>[,<resolution>[,<source list>]]] 116

FETCh[1]|2|3|4[:SCALar][:POWer:AC]:DIFFerence: RELative?


FETCh[1]|2|3|4[:SCALar][:POWer:AC]:RATio? [<expected_value>[,<resolution>[,<source list>]]] 122

FETCh[1]|2|3|4[:SCALar][:POWer:AC]:RATio:RELative? [<expected_value>[,<resolution>[,<source list>]]] 125

READ[1]|2|3|4 Commands 128

READ[1]|2|3|4[:SCALar][:POWer:AC]? [<expected_value>[,<resolution>[,<source list>]]] 129

N1911A/1912A P-Series Power Meters Programming Guide xi

xii

READ[1]|2|3|4[:SCALar][:POWer:AC]:RELative? [<expected_value>[,<resolution>[,<source list>]]] 132

READ[1]|2|3|4[:SCALar][:POWer:AC]:DIFFerence? [<expected_value>[,<resolution>[,<source list>]]] 135

READ[1]|2|3|4[:SCALar][:POWer:AC]:DIFFerence: RELative?


READ[1]|2|3|4[:SCALar][:POWer:AC]:RATio? [<expected_value>[,<resolution>[,<source list>]]] 141

READ[1]|2|3|4[:SCALar][:POWer:AC]:RATio:RELative? [<expected_value>[,<resolution>[,<source list>]]] 144

MEASure[1]|2|3|4 Commands 147

MEASure[1]|2|3|4[:SCALar][:POWer:AC]? [<expected_value>[,<resolution>[,<source list>]]] 148

MEASure[1]|2|3|4[:SCALar][:POWer:AC]:RELative? [<expected_value>[,<resolution>[,<source list>]]] 150

MEASure[1]|2|3|4[:SCALar][:POWer:AC]:DIFFerence? [<expected_value>[,<resolution>[,<source list>]]] 152

MEASure[1]|2|3|4[:SCALar][:POWer:AC]:DIFFerence: RELative?


MEASure[1]|2|3|4[:SCALar][:POWer:AC]:RATio? [<expected_value>[,<resolution>[,<source list>]]] 156

MEASure[1]|2|3|4[:SCALar][:POWer:AC]:RATio:RELative? [<expected_value>[,<resolution>[,<source list>]]] 158

3


CALCulate Subsystem 162

CALCulate[1]|2|3|4:FEED[1]|2 <string> 165

CALCulate[1]|2|3|4:GAIN Commands 168

CALCulate[1]|2|3|4:GAIN[:MAGNitude] <numeric_value> 169

CALCulate[1]|2|3|4:GAIN:STATe <boolean> 171

CALCulate[1]|2|3|4:LIMit Commands 173

CALCulate[1]|2|3|4:LIMit:CLEar:AUTo <boolean>|ONCE 174

CALCulate[1]|2|3|4:LIMit:CLEar[:IMMediate] 176

CALCulate[1]|2|3|4:LIMit:FAIL?

177

CALCulate[1]|2|3|4:LIMit:FCOunt?

178

CALCulate[1]|2|3|4:LIMit:LOWer[:DATA] <numeric_value> 180

CALCulate[1]|2|3|4:LIMit:UPPer[:DATA] <numeric_value> 183

CALCulate[1]|2|3|4:LIMit:STATe <boolean> 186


CALCulate[1]|2|3|4:MATH Commands 188

CALCulate[1]|2|3|4:MATH[:EXPRession] <string> 189

CALCulate[1]|2|3|4:MATH[:EXPRession]:CATalog?

192

CALCulate[1]|2|3|4:PHOLd:CLEar 193

CALCulate[1]|2|3|4:RELative Commands 194

CALCulate[1]|2|3|4:RELative[:MAGNitude]:AUTO <boolean>|ONCE 195

CALCulate[1]|2|3|4:RELative:STATe <boolean> 197

4


CALibration Subsystem 200

CALibration[1]|2[:ALL] 202

CALibration[1]|2[:ALL]?

204

CALibration[1]|2:AUTO [ONCE|ON|OFF|0|1] 206

CALibration[1]|2:RCALibration <boolean> 209

CALibration[1]|2:RCFactor <numeric_value> 211

CALibration[1]|2:ZERO:AUTO [ONCE|ON|OFF|0|1] 213

CALibration[1]|2:ZERO:NORMal:AUTO <boolean> 215

5


DISPlay Subsystem 218

DISPlay:ENABle <boolean> 219

DISPlay:SCReen:FORMat <character_data> 221

DISPlay[:WINDow[1]|2] Commands 223

DISPlay[:WINDow[1]|2]:ANALog Commands 224

DISPlay[:WINDow[1]|2]:ANALog:LOWer <numeric_value> 225

DISPlay[:WINDow[1]|2]:ANALog:UPPer <numeric_value> 228

DISPlay[:WINDow[1]|2]:FORMat <character_data> 231

DISPlay[:WINDow[1]|2]:METer Commands 234

DISPlay[:WINDow[1]|2]:METer:LOWer <numeric_value> 235

DISPlay[:WINDow[1]|2]:METer:UPPer <numeric_value> 238

DISPlay[:WINDow[1]|2][:NUMeric[1]|2]:RESolution <numeric_value> 241

DISPlay[:WINDow[1]|2]:SELect[1]|2 243

DISPlay[:WINDow[1]|2]:STATe <boolean> 245

DISPlay[:WINDow[1]|2]:TRACe:FEED <character_data> 247

N1911A/1912A P-Series Power Meters Programming Guide xiii

xiv

6


FORMat Subsystem 250

FORMat[:READings]:BORDer <character_data> 251

FORMat[:READings][:DATA] <character_data> 253

7


MEMory Subsystem 256

MEMory:CATalog Commands 258

MEMory:CATalog[:ALL]?

259

MEMory:CATalog:STATe?

261

MEMory:CATalog:TABLe?

262

MEMory:CLEar Commands 265

MEMory:CLEar[:NAME] <character_data> 266

MEMory:CLEar:TABLe 268

MEMory:FREE Commands 269

MEMory:FREE[:ALL]?

270

MEMory:FREE:STATe?

271

MEMory:FREE:TABLe?

272

MEMory:NSTates?

273

MEMory:STATe Commands 274

MEMory:STATe:CATalog?

275

MEMory:STATe:DEFine <character_data>,<numeric_value> 276

MEMory:TABLe Commands 278

MEMory:TABLe:FREQuency <numeric_value>{,<numeric_value>} 279

MEMory:TABLe:FREQuency:POINts?

283

MEMory:TABLe:GAIN[:MAGNitude] <numeric_value>{,<numeric_value>} 284

MEMory:TABLe:GAIN[:MAGNitude]:POINts?

287

MEMory:TABLe:MOVE <character_data>,<character_data> 288

MEMory:TABLe:SELect <character_data> 290

8


OUTPut Subsystem 292

OUTPut:RECorder[1]|2:FEED <data_handle> 293

OUTPut:RECorder[1]|2:LIMit:LOWer <numeric_value> 295

OUTPut:RECorder[1]|2:LIMit:UPPer <numeric_value> 297


OUTPut:RECorder[1]|2:STATe <boolean> 299

OUTPut:ROSCillator[:STATe] <boolean> 301

OUTPut:TRIGger[:STATe] <boolean> 303

9


PSTatistic Subsystem 307

PSTatistic:CCDF:GAUSsian[:STATe] <boolean> 309

PSTatistic:CCDF:GAUSsian:MARKer[1]|2[:SET] 311

PSTatistic:CCDF:MARKer:DELta?

313

PSTatistic:CCDF:MARKer[1]|2:DATa?

315

PSTatistic:CCDF:MARKer[1]|2:X <numeric_value> 317

PSTatistic:CCDF:MARKer[1]|2:Y <numeric_value> 319

PSTatistic:CCDF:REFerence:DATa?

321

PSTatistic:CCDF:REFerence[:STATe] <boolean> 323

PSTatistic:CCDF:REFerence:MARKer[1]|2[:SET] 325

PSTatistic:CCDF:REFerence:POWer:AVERage?

327

PSTatistic:CCDF:REFerence:POWer:PEAK?

328

PSTatistic:CCDF:REFerence:POWer:PTAVerage?

329

PSTatistic[1]|2:CCDF:CONTinuous <boolean> 330

PSTatistic[1]|2:CCDF:COUNt <numeric_value> 332

PSTatistic[1]|2:CCDF:DATa?

334

PSTatistic[1]|2:CCDF:DATa:MAX <numeric_value> 336

PSTatistic[1]|2:CCDF:POWer? <numeric_value> 338

PSTatistic[1]|2:CCDF:PROBability? <numeric_value> 340

PSTatistic[1]|2:CCDF:STORe:REFerence 342

PSTatistic[1]|2:CCDF:TABle?

344

PSTatistic[1]|2:CCDF:TRACe[:STATe] <boolean> 347

PSTatistic[1]|2:CCDF:TRACe:MARKer[1]|2[:SET] 349

PSTatistic[1]|2:CCDF:TRACe:POWer:AVERage?

351

PSTatistic[1]|2:CCDF:TRACe:POWer:PEAK?

353

PSTatistic[1]|2:CCDF:TRACe:POWer:PTAVerage?

355

10

SENSe Subsystem

[SENSe] Subsystem 359

[SENSe[1]]|SENSe2:AVERage Commands 362

N1911A/1912A P-Series Power Meters Programming Guide xv

xvi

[SENSe[1]]|SENSe2:AVERage:COUNt <numeric_value> 363

[SENSe[1]]|SENSe2:AVERage:COUNt:AUTO <boolean> 366

[SENSe[1]]|SENSe2:AVERage:SDETect <boolean> 369

[SENSe[1]]|SENSe2:AVERage[:STATe] <boolean> 371

[SENSe[1]]|SENSe2:AVERage2 Commands 373

[SENSe[1]]|SENSe2:AVERage2:COUNt <numeric_value> 374

[SENSe[1]]|SENSe2:AVERage2[:STATe] <boolean> 376

[SENSe[1]]|SENSe2:BANDwidth|BWIDth:VIDeo <character_data> 378

[SENSe[1]]|SENSe2:BUFFer:COUNt <numeric_value> 381

[SENSe[1]]|SENSe2:BUFFer:MTYPe <string> 384

[SENSe[1]]|SENSe2:CORRection Commands 387

[SENSe[1]]|SENSe2:CORRection:CFACtor|GAIN[1][:INPut][:MAGNitude] <numeric_value> 388

[SENSe[1]]|SENSe2:CORRection:CSET[1]|CSET2 Commands 391

[SENSe[1]]|SENSe2:CORRection:CSET[1]|CSET2[:SELect] <string> 392

[SENSe[1]]|SENSe2:CORRection:CSET[1]|CSET2:STATe <boolean> 395

[SENSe[1]]|SENSe2:CORRection:DCYCle|GAIN3 Commands 397

[SENSe[1]]|SENSe2:CORRection:DCYCle|GAIN3[:INPut] [:MAGNitude] <numeric_value> 398

[SENSe[1]]|SENSe2:CORRection:DCYCle|GAIN3:STATe <boolean> 401

[SENSe[1]]|SENSe2:CORRection:FDOFfset|GAIN4[:INPut][:MAGNitude]?

403

[SENSe[1]]|SENSe2:CORRection:GAIN2 Commands 404

[SENSe[1]]|SENSe2:CORRection:GAIN2:STATe <boolean> 405

[SENSe[1]]|SENSe2:CORRection:GAIN2[:INPut] [:MAGNitude] <numeric_value> 407

[SENSe[1]]|SENSe2:DETector:FUNCtion <character_data> 410

[SENSe[1]]|SENSe2:FREQuency[:CW|:FIXed] <numeric_value> 412

[SENSe[1]]|SENSe2:FREQuency[:CW|:FIXed]:STARt <numeric_value> 415

[SENSe[1]]|SENSe2:FREQuency[:CW|:FIXEd]:STEP <numeric_value> 418

[SENSe[1]]|SENSe2:FREQuency[:CW|:FIXed]:STOP <numeric_value> 422

[SENSe[1]]|SENSe2:MRATe <character_data> 425

[SENSe[1]]|SENSe2:POWer:AC:RANGe <numeric_value> 428

[SENSe[1]]|SENSe2:POWer:AC:RANGe:AUTO <boolean> 430

[SENSe[1]]|SENSe2:SWEep[1]|2|3|4 Commands 432

[SENSe[1]]|SENSe2:SWEep[1]|2|3|4:AUTO <character_data> 433

[SENSe[1]]|SENSe2:SWEep[1]|2|3|4:AUTO:REF1|REF2 <numeric_value> 436

[SENSe[1]]|SENSe2:SWEep[1]|2|3|4:OFFSet:TIME <numeric_value> 438

[SENSe[1]]|SENSe2:SWEep[1]|2|3|4:TIME <numeric_value> 440


[SENSe[1]]|SENSe2:TEMPerature?

442

[SENSe[1]]|SENSe2:TRACe Commands 444

[SENSe[1]]|SENSe2:TRACe:OFFSet:TIME <numeric_value> 445

[SENSe[1]]|SENSe2:TRACe:TIME <numeric_value> 447

[SENSe[1]]|SENSe2:TRACe:UNIT <character_data> 449

[SENSe[1]]|SENSe2:V2P ATYPe|DTYPe 451

SENSe[1]|2:TRACe:AUToscale 453

SENSe[1]|2:TRACe:LIMit:LOWer <numeric_value> 455

SENSe[1]|2:TRACe:LIMit:UPPer <numeric_value> 458

SENSe[1]|2:TRACe:X:SCALe:PDIV <numeric_value> 461

SENSe[1]|2:TRACe:Y:SCALe:PDIV <numeric_value> 463

11


STATus Subsystem 466

Status Register Set Commands 468

Device Status Register Sets 473

Operation Register Sets 475

STATus:OPERation 476

STATus:OPERation:CALibrating[:SUMMary] 477

STATus:OPERation:LLFail[:SUMMary] 478

STATus:OPERation:MEASuring[:SUMMary] 479

STATus:OPERation:SENSe[:SUMMary] 480

STATus:OPERation:TRIGger[:SUMMary] 481

STATus:OPERation:ULFail[:SUMMary] 482

STATus:PRESet 483

Questionable Register Sets 484

STATus:QUEStionable 485

STATus:QUEStionable:CALibration[:SUMMary] 486

STATus:QUEStionable:POWer[:SUMMary] 487

12


SYSTem Subsystem 492

SYSTem:COMMunicate:GPIB[:SELF]:ADDRess <numeric_value> 494

SYSTem:COMMunicate:LAN:AIP[:STATe] <boolean> 496

SYSTem:COMMunicate:LAN:CURRent:ADDRess?

497

N1911A/1912A P-Series Power Meters Programming Guide xvii

SYSTem:COMMunicate:LAN:CURRent:DGATeway?

498

SYSTem:COMMunicate:LAN:CURRent:DNAMe?

499

SYSTem:COMMunicate:LAN:CURRent:SMASk?

500

SYSTem:COMMunicate:LAN:ADDRess <character_data> 501

SYSTem:COMMunicate:LAN:DGATeway <character_data> 503

SYSTem:COMMunicate:LAN:DHCP[:STATe] <boolean> 505

SYSTem:COMMunicate:LAN:DNAMe <character_data> 506

SYSTem:COMMunicate:LAN:HNAMe <character_data> 508

SYSTem:COMMunicate:LAN:MAC?

510

SYSTem:COMMunicate:LAN:RESTart 511

SYSTem:COMMunicate:LAN:SMASk <character_data> 512

SYSTem:DISPlay:BMP 514

SYSTem:ERRor?

515

SYSTem:HELP:HEADers?

523

SYSTem:LOCal 525

SYSTem:PRESet <character_data> 526

SYSTem:REMote 605

SYSTem:RWLock 606

SYSTem:VERSion?

607

13

TRACe Subsystem

TRACe Subsystem 610

TRACe[1]|2[:DATA]? <character_data> 612

TRACe[1]|2:DEFine:DURation:REFerence<numeric_value> 614

TRACe[1]|2:DEFine:TRANsition:REFerence <numeric_value>, <numeric_value> 616

TRACe[1]|2:MEASurement:INSTant:REFerence? <numeric_value> 618

TRACe[1]|2:MEASurement:PULSe[1]|...|10:DCYCle?

620

TRACe[1]|2:MEASurement:PULSe[1]|...|10:DURation?

622

TRACe[1]|2:MEASurement:PULSe[1]|...|10:PERiod?

624

TRACe[1]|2:MEASurement:PULSe[1]|...|10:SEParation?

626

TRACe[1]|2:MEASurement:TRANsition[1]|...|10:NEGative:DURation?

628

TRACe[1]|2:MEASurement:TRANsition[1]|...|10:NEGative:OCCurrence?

630

TRACe[1]|2:MEASurement:TRANsition[1]|...|10:POSitive:DURation?

632

TRACe[1]|2:MEASurement:TRANsition[1]|...|10:POSitive:OCCurrence?

634

TRACe[1]|2:MEASurement:REFerence? <numeric_value> 636

xviii N1911A/1912A P-Series Power Meters Programming Guide

TRACe[1]|2:STATe <boolean> 638

TRACe[1]|2:UNIT <character_data> 640

14


TRIGger Subsystem 644

ABORt[1]|2] 646

INITiate Commands 647

INITiate[1]|2:CONTinuous <boolean> 648

INITiate[1]|2[:IMMediate] 651

INITiate:CONTinuous:ALL <boolean> 652

INITiate:CONTinuous:SEQuence[1]|2 <boolean> 654

INITiate[:IMMediate]:ALL 656

INITiate[:IMMediate]:SEQuence[1]|2 657

TRIGger Commands 658

TRIGger[1]|2:DELay:AUTO <boolean> 659

TRIGger[1]|2[:IMMediate] 661

TRIGger[1]|2:SOURce BUS|EXTernal|HOLD|IMMediate|INTernal[[1]|2] 662

TRIGger[:SEQuence]:DELay <numeric_value> 665

TRIGger[:SEQuence]:HOLDoff <numeric_value> 667

TRIGger[:SEQuence]:HYSTeresis <numeric_value> 669

TRIGger[:SEQuence]:LEVel <numeric_value> 671

TRIGger[:SEQuence]:LEVel:AUTO <boolean> 673

TRIGger[:SEQuence]:SLOPe <character_data> 675

TRIGger[:SEQuence[1]|2]:COUNt <numeric_value> 677

TRIGger[:SEQuence[1]|2]:DELay:AUTO <boolean> 680

TRIGger[:SEQuence[1]|2]:IMMediate 682

TRIGger[:SEQuence[1]|2]:SOURce BUS|EXTernal|HOLD|IMMediate|INTernal[[1]|2] 683

15

UNIT Subsystem

UNIT Subsystem 688

UNIT[1]|2|3|4:POWer <amplitude_unit> 689

UNIT[1]|2|3|4:POWer:RATio <ratio_unit> 691

16


SERVice Subsystem 695

N1911A/1912A P-Series Power Meters Programming Guide xix

xx

SERVice:BIST:CALibrator <boolean> 697

SERVice:BIST:CW[1]|2:LINearity 699

SERVice:BIST:CW[1]|2:LINearity:PERRor?

700

SERVice:BIST:CW[1]|2:ZSET:NUMber?

701

SERVice:BIST:PEAK[1]|2:LINearity <numeric_value> 702

SERVice:BIST:PEAK[1]|2:LINearity:PERRor?

703

SERVice:BIST:PEAK[1]|2:ZSET 704

SERVice:BIST:PEAK[1]|2:ZSET:NUMber?

705

SERVice:BIST:TBASe:STATe 706

SERVice:BIST:TBASe:STATe <boolean> 707

SERVice:BIST:TRIGger:TEST?

709

SERVice:CALibrator:ADJ:COUR <numeric_value> 710

SERVice:CALibrator:ADJ:FINE <numeric_value> 711

SERVice:LAN:PHOStname 712

SERVice:OPTion <character_data> 713

SERVice:SECure:ERASe 715

SERVice:SENSor[1]|2:CALFactor <cal_factor_data> 716

SERVice:SENSor[1]|2:CDATe?

718

SERVice:SENSor[1]|2:CORRections:STATe <boolean> 719

SERVice:SENSor[1]|2:CPLace?

721

SERVice:SENSor[1]|2:FREQuency:MAXimum?

722

SERVice:SENSor[1]|2:FREQuency:MINimum?

723

SERVice:SENSor[1]|2:PCALfactor <cal_factor_data> 724

SERVice:SENSor[1]|2:POWer:AVERage:MAXimum?

726

SERVice:SENSor[1]|2:POWer:PEAK:MAXimum?

727

SERVice:SENSor[1]|2:POWer:USABle:MAXimum?

728

SERVice:SENSor[1]|2:POWer:USABle:MINimum?

729

SERVice:SENSor[1]|2:RADC?

730

SERVice:SENSor[1]|2:SNUMber?

731

SERVice:SENSor[1]|2:TNUMber?

732

SERVice:SENSor[1]|2:TYPE?

733

SERVice:SNUMber <character_data> 734

SERVice:VERSion:PROCessor <character_data> 735

SERVice:VERSion:SYSTem <character_data> 736


17



*CLS 739

*DDT <arbitrary block program data>|<string program data> 740

*ESE <NRf> 742

*ESR?

744

*IDN?

745

*OPC 746

*OPT?

747

*RCL <NRf> 748

*RST 749

*SAV <NRf> 750

*SRE <NRf> 751

*STB?

753

*TRG 755

*TST?

756

*WAI 757

GPIB Universal Commands 758

Appendix A


Calibration Factor Block Layout A-2

Appendix B

Measurement Polling Example

Measurement Polling Example using VEE program B-2

N1911A/1912A P-Series Power Meters Programming Guide xxi


xxii N1911A/1912A P-Series Power Meters Programming Guide

List of Figures

Figure B-1-1 Frequency Dependent Offset Tables 28

Figure B-1-2 Typical Averaged Readings on 8480 Series Sensors 35

Figure B-1-3 Averaging Range Hysteresis 36

Figure B-1-4 Limits Checking Application 40

Figure B-1-5 Limits Checking Results 41

Figure B-1-6 How Measurement are Calculated 49

Figure B-1-7 Generalized Status Register Model 51

Figure B-1-8 Typical Status Register Bit Changes 52

Figure B-1-9 Status System 58

Figure B-1-10 Hierarchical structure of SCPI 71

Figure B-1-11 Format of <character_data> 74

Figure B-1-12 Format of <non-decimal numeric> 76

Figure B-1-13 Format of <NR1> 77



Figure B-1-16 Format of <string> 79

Figure B-2-17 Measurement Display CALCulate Block Window 90

Figure B-3-18 Measurement Display CALCulate Block Window 162

Figure B-3-19 CALCulate Block 163

Figure B-10-20 Example of Averaged Readings 366

Figure B-12-21 IEEE 488.2 Arbitrary Block Program Data Format 523

Figure B-12-22 A Trace Display Of The Active Timeslots 577

Figure B-15-23 Measurement Display UNIT Block Window 688

Figure B-16 Example of VEE program used in measurement polling 773

N1911A/1912A P-Series Power Meters Programming Guide xxiii


xxiv N1911A/1912A P-Series Power Meters Programming Guide

List of Tables

Table 1-1 MEASure? and CONFigure Preset States 11

Table 1-2 Possibilities of the defaulted source list parameter 16

Table 1-3 Range of Values for Window Limits 42

Table 1-4 Model of Sensor and Measurement Rates 45

Table 1-5 Bit Definitions - Status Byte Register 59

Table 1-6 Bit Definitions - Standard Event Register 60

Table 1-7 Bit Definitions - Questionable Status Registers 62

Table 1-8 Bit change conditions for Questionable Status Register 62

Table 1-9 Bit Definitions - Operation Status 63

Table 1-10 Bit change conditions for Operation Status 64

Table 1-11 Bit Definitions - Device Status Register 65

Table 1-12 Bit change conditions for Device Status Register 66

Table 3-13 Measurement Units 180






Table 7-19 8480 Series Power Sensor Tables 260

Table 7-20 8480 Series Power Sensor Tables 263

Table 7-21 Frequency and Calibration/Offset Factor List 280

Table 7-22 Frequency and Calibration/Offset Factor List 284



Table 11-25 Commands and events affecting Status Register 466

Table 12-26 DEFault: Power Meter Presets 529

Table 12-27 GSM900: Power Meter Presets 533

Table 12-28 GSM900: Power Meter Presets: Window/Measurement Settings 534

Table 12-29 GSM900: Power Meter Presets For Secondary Channel Sensors 535

Table 12-30 EDGE: Power Meter Presets 536

Table 12-31 EDGE: Power Meter Presets: Window/Measurement Settings 538

Table 12-32 EDGE: Power Meter Presets For Secondary Channel Sensors 538

Table 12-33 CDMAone: Power Meter Presets 540

Table 12-34 CDMAone: Power Meter Presets: Window/Measurement Settings 541

N1911A/1912A P-Series Power Meters Programming Guide xxv

xxvi

Table 12-35 CDMAone: Power Meter Presets For Secondary Channel Sensors 542

Table 12-36 cdma2000: Power Meter Presets 544

Table 12-37 cdma2000: Power Meter Presets: Window/Measurement Settings 545

Table 12-38 cdma2000: Power Meter Presets For Secondary Channel Sensors 546

Table 12-39 W-CDMA: Power Meter Presets 548

Table 12-40 W-CDMA: Power Meter Presets: Window/Measurement Settings 549

Table 12-41 W-CDMA: Power Meter Presets For Secondary Channel Sensors 550

Table 12-42 BLUetooth: Power Meter Presets 552

Table 12-43 BLUetooth: Power Meter Presets: Window/Measurement Settings 553

Table 12-44 BLUetooth: Power Meter Presets For Secondary Channel Sensors 554

Table 12-45 MPCA: Power Meter Presets 555

Table 12-46 MPCA: Power Meter Presets: Window/Measurement Settings 556

Table 12-47 MCPA: Power Meter Presets For Secondary Channel Sensors 557

Table 12-48 RADAR: Power Meter Presets 558

Table 12-49 RADAR: Power Meter Presets: Window/Measurement Settings 559

Table 12-50 RADAR: Power Meter Presets For Secondary Channel Sensors 560

Table 12-51 802.11a and HiperLan2: Power Meter Presets 562

Table 12-52 802.11a and HiperLan2: Power Meter Presets: Window/Measurement Settings 563

Table 12-53 802.11a and HiperLan2: Power Meter Presets For Secondary Channel Sensors 564

Table 12-54 802.11b/g: Power Meter Presets 565

Table 12-55 802.11b/g: Power Meter Presets: Window/Measurement Settings 566

Table 12-56 802.11b/g: Power Meter Presets For Secondary Channel Sensors 567

Table 12-57 1xeV-DO: Power Meter Presets 568

Table 12-58 1exV-DO: Power Meter Presets: Window/Measurement Settings 569

Table 12-59 1exV-DO: Power Meter Presets For Secondary Channel Sensors 570

Table 12-60 1exV-DV: Power Meter Presets 571

Table 12-61 1xeV-DV: Power Meter Presets: Window/Measurement Settings 572

Table 12-62 1xeV-DV: Power Meter Presets For Secondary Channel Sensors 573

Table 12-63 TD-SCDMA: Power Meter Presets 574

Table 12-64 TD-SCDMA: Power Meter Presets: Window/Measurement Settings 575

Table 12-65 TD-SCDMA: Power Meter Presets: Window/Measurement Settings 576

Table 12-66 NADC: Power Meter Presets 577

Table 12-67 NADC: Power Meter Presets: Window/Measurement Settings 579

Table 12-68 NADC: Power Meter Presets For Secondary Channel Sensors 579

Table 12-69 iDEN: Power Meter Presets 581


Table 12-70 iDEN: Power Meter Presets: Window/Measurement Settings 583

Table 12-71 iDEN: Power Meter Presets For Secondary Channel Sensors 583

Table 12-72 DVB: Power Meter Presets 585

Table 12-73 DVB: Power Meter Presets: Window/Measurement Settings 586

Table 12-74 DVB: Power Meter Presets For Secondary Channel Sensors 587

Table 12-75 WiMAX: Power Meter Presets 588

Table 12-76 WiMAX: Power Meter Presets: Window/Measurement Settings 589

Table 12-77 WiMAX: Power Meter Presets For Secondary Channel Sensors 590

Table 12-78 DME: Power Meter Presets 591

Table 12-79 DME: Power Meter Presets: Window/Measurement Settings 592

Table 12-80 DME: Power Meter Presets For Secondary Channel Sensors 593

Table 12-81 DME-PRT: Power Meter Presets 595

Table 12-82 DME-PRT: Power Meter Presets: Window/Measurement Settings 596

Table 12-83 DME-PRT: Power Meter Presets For Secondary Channel Sensors 597

Table 12-84 HSPDA: Power Meter Presets 599

Table 12-85 HSPDA: Power Meter Presets: Window/Measurement Settings 600

Table 12-86 HSDPA: Power Meter Presets For Secondary Channel Sensors 601

Table 12-87 LTE: Power Meter Presets 602

Table 12-88 LTE: Power Meter Presets: Window/Measurement Settings 603

Table 12-89 LTE: Power Meter Presets For Secondary Channel Sensors 604

Table 17-90 *ESE Mapping 742

Table 17-91 *ESR? Mapping 744

Table 17-92 *SRE Mapping 751

Table 17-93 *STB? Mapping 753

Table 17-94 PPD Mapping 759

Table 17-95 PPE Mapping 760

Table A-96 Calibration Factor Block Layout: E4410 Series Sensors A-2



N1911A/1912A P-Series Power Meters Programming Guide xxvii


xxviii N1911A/1912A P-Series Power Meters Programming Guide

N1911A/1912A P-Series Power Meters


1


Introduction 5


•

Interface Selection 6

•

GPIB Address 6

•

LAN Configuration 7

•

USB Configuration 8

Zeroing and Calibrating the P-Series Power Sensor 9

•

Zeroing 9

•

Calibration 9

Making Measurement 11

•

Using MEASure?

12

•

Using the CONFigure Command 17

•

Using the Lower Level Commands 26

Using Frequency Dependent Offset Tables 27

•

Overview 27

•

Editing Frequency Dependent Offset Tables 29

•

Selecting a Frequency Dependent Offset Table 32

•

Enabling a Frequency Dependent Offset Table 32

•

Making the Measurement 32

Setting the Range, Resolution and Averaging 34

•

Resolution 34

•

Averaging 34

•

Auto Averaging Mode 35

•

Filter Length 36

Range 37


1

1 Power Meter Remote Operation


•

Interface Selection 6

•

GPIB Address 6

•

LAN Configuration 7

Setting Offsets 38

•

Channel Offsets 38

•

Display Offsets 38

Setting Measurement Limits 40

•

Setting Limits 40

•

Checking for Limit Failures 42

•

Using STATus 43

Getting the Best Speed Performance 44

•

Measurement Rate 44

•

Sensor 45

•

Trigger Mode 45

•

Output Format 47

•

Units 47

•

Command Used 47

•

Fast Mode 48

How Measurements are Calculated 49

2 N1911A/1912A P-Series Power Meters Programming Guide

Power Meter Remote Operation 1

Status Reporting 50

•

The General Status Register Model 50

•

How to Use Register 53

•

The Condition Polling Method 53

•

The SRQ Method 54

•

Device Status Register 65

•

Using the Operation Complete Commands 67

Saving and Recalling Power Meter Configurations 69

•

How to Save and Recall a Configuration 69

Using Device Clear to Halt Measurements 70

An Introduction to the SCPI Language 71

•

Mnemonic Forms 71

•

Using a Colon (:) 71

•

Using a Semicolon (;) 72

•

Using a Comma (,) 72

•

Using Whitespace 72

•

Using “?” Commands 72

•

Using “*” Commands 73

•

Syntax Conventions 73

•

Syntax Diagram Conventions 73

•

SCPI Data Types 74

•

Input Message Terminators 79


Summary of Commands 83

N1911A/1912A P-Series Power Meters Programming Guide 3


Making Measurements on Wireless Communication Standards 84

•

Starting a Preset Example 85

This chapter describes the parameters that configure the power meter and helps you determine settings to optimize performance.



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 6.

•

“Zeroing and Calibrating the P- Series Power Sensor” on page 9.

•

“Making Measurement” on page 11.

•

“Using Frequency Dependent Offset Tables” on page 27.

•

“Setting the Range, Resolution and Averaging” on page 34.

•

“Setting Offsets” on page 38.

•

“Setting Measurement Limits” on page 40.

•

“Getting the Best Speed Performance” on page 44.

•

“How Measurements are Calculated” on page 49.

•

“Status Reporting” on page 50.

•

“Saving and Recalling Power Meter Configurations” on page 69.

•

“Using Device Clear to Halt Measurements” on page 70.

•

“An Introduction to the SCPI Language” on page 71.

•

“SCPI Compliance Information” on page 81.

•

“Summary of Commands” on page 83.

•

“Making Measurements on Wireless Communication Standards” on page 84.


6


Configuring the Remote Interface

This section briefly describes how to configure the GPIB, LAN and USB remote interfaces.

N O T E

For more information on configuring the remote interface connectivity, refer to the Agilent

Technologies USB/LAN/GPIB Interfaces Connectivity Guide. If you have installed the IO

Libraries Suite, you can access the Connectivity Guide via the Agilent IO Libraries Control icon. Alternatively, you can access the Connectivity Guide via the Web at www.agilent.com/find/connectivity.

N O T E

Interface Selection

You can choose to control the power meter remotely using the GPIB, LAN or USB interfaces.

For information on selecting and configuring the remote interface manually from the front panel, refer to the P- Series Power Meters

Installation Guide.

It is expected that most users will use the front panel keys to set up the remote interfaces.

The remote interface commands are provided for completeness (for the front panel operation).

GPIB Address

Each device on the GPIB (IEEE- 488) interface must have a unique address. You can set the power meter’s address to any value between 0 and 30. The power meter is shipped with a default address set to 13. The

GPIB address is stored in non- volatile memory, and does not change when the power meter is switched off, or after a remote interface reset.

Your GPIB bus controller has its own address. Avoid using the bus controller’s address for any instrument on the interface bus. Agilent

Technologies controllers generally use address 21.



For information on setting the GPIB address manually from the front panel, refer to the P- Series Power Meters Installation Guide.

• To set the GPIB address from the remote interface use the:

SYSTem:COMMunicate:GPIB:ADDRess

command.

• To query the GPIB address from the remote interface use the:

SYSTem:COMMunicate:GPIB:ADDRess?

query.

LAN Configuration

The power meter has three LAN operating modes:

• Dynamic IP (Dynamic Host Configuration Protocol or DHCP)

• Auto IP (Local PC Control or isolated (non- site) LAN)

• Static IP (Manual mode)

These three modes can be set up from the front panel. For front panel operation refer to the P- Series Power Meter Installation Guide.

Configuring the LAN Remotely

To automatically configure the LAN settings, enable DHCP operation using the SYSTem:COMMunicate:LAN:DHCP[:STATe] command.

In this Dynamic IP mode the IP Address, Subnet Mask, and Default

Gateway values are obtained from a DHCP server. Using this Dynamic IP mode does not require a detailed knowledge of your network configuration.

The IP Address, Subnet Mask, Default Gateway, and Host settings can be changed manually or remotely. To individually specify the LAN settings, use the following commands:

• IP Address - SYSTem:COMMuniucate:LAN:ADDRess

• Subnet Mask - SYSTem:COMMunicate:LAN:SMASk

• Default Gateway - SYSTem:COMMunicate:LAN:DGATeway

• Domain Name - SYSTem:COMMunicate:LAN:DNAMe


8


N O T E

•

Hostname - SYSTem:COMMunicate:LAN:HNAMe

•

Restart Network - 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 device or host, an error message is generated. This error can be read by using the SYSTem:ERRor? command.

The LAN setting values are stored in non- volatile memory and are not part of the save- recall function.

N O T E

USB Configuration

The USB interface requires no front panel or remote configuration.

The USB address cannot be changed - it is set at the factory and is unique for each power meter.

For further information about the USB configuration refer to the P-Series Power Meters

Installation Guide.

N O T E

Before connecting the USB cable, make sure that I/O software is installed on your computer.

N O T E

For more information about Agilent IO Libraries software refer to the Connectivity Guide.

If you have installed other I/O Software, refer to documentation that accompanies the software .



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. 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 zero on- the- fly for measurements and temperature compensation.

Zeroing of the power meter happens automatically:

• When a 5 o

C change in temperature occurs

• When you change the power sensor

• Every 24 hours

• Prior to measuring low level signals. For example, 10 dB above the lowest specified power for your power sensor.

Calibration

The command used to calibrate the power meter is:

CALibration[1|2]:AUTO ONCE

It is recommended that you zero the power meter before calibrating.



N O T E

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. The calibration sequence consists of:

1 Zeroing the power meter (CALibration[1|2]:ZERO:AUTO ONCE)

2 Calibrating the power meter (CALibration[1|2]:AUTO ONCE)

The query enters a number into the output buffer when the sequence is complete. If the result is 0 the sequence was successful. If the result is 1 the sequence failed. Refer to

“CALibration[1]|2[:ALL]?” on page 204 for

further information.

The CALibration[1|2][:ALL] command is identical to the

CALibration[1|2][:ALL]? query except that no number is returned to indicate the outcome of the sequence. You can examine the Questionable Status Register or the error

queue to discover if the sequence has passed or failed. Refer to “Status Reporting” on page 50 for further information.



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 N1912A 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 below

.

Table 1-1 MEASure? and CONFigure Preset States

Command

Trigger source

(TRIGger:SOURce)

Filter

(SENSe:AVERage:COUNt:AUTO)

Filter state(SENSe:AVERage:STATe)

Trigger cycle

(INITiate:CONTinuous)

TriggerDelay

(TRIGger:DELay:AUTO)

MEASure? and CONFigure Setting

Immediate

On

On

Off

On

An alternative method to program the power meter is to use the lower level commands. The advantage of using the lower level commands over the CONFigure command is that they give you more precise control of the

power meter. As shown in Table 1- 1 , the CONFigure command presets

various states in the power meter. It may be likely that you do not want

to preset these states. Refer to “Using the Lower Level Commands” on page 26 for further information.



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. You cannot change any settings (other than the expected power value, resolution and with the N1912A the measurement type) before the measurement is taken. This means you cannot fine tune the measurement, for example, you cannot change the filter length. To make more flexible and accurate measurements use the CONFIGure command.

The measurement results are sent to the output buffer. MEASure? is a compound command which is equivalent to an ABORT, followed by a

CONFigure , followed by a READ?.

MEASure? Examples

The following commands show a few examples of how to use the

MEASure?

query to make a measurement. It is advisable to read through these examples in order as they become increasingly more detailed. These examples configure the power meter for a measurement (as described in each individual example), automatically place the power meter in the

“wait- for- trigger” state, internally trigger the power meter to take one reading, and then sends the reading to the output buffer.

These examples give an overview of the MEASure? query. For further information on the MEASure? commands refer to the section

“MEASure[1]|2|3|4 Commands” on page 147.

Example 1 - The Simplest Method

The following commands show the simplest method of making single channel (for example A or B) measurements. Using MEAS1? results in an upper window measurement, and MEAS2? in a lower window measurement.

The channel associated with the window can be set using the source list parameter (see

“Example 2 - Specifying the Source List Parameter”

), or



N O T E defaults as in this example (see

“Agilent N1912A Only” on page 15).

specifies window

MEAS1?

MEAS2?

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.

The following example uses 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.

specifies window specifies channel

MEAS1? DEF,DEF,(@1)

The operation of the MEAS1? command when the source list parameter is defaulted is described in the note

“Agilent N1912A Only” on page 15.

For the N1911A it is not necessary to specify a channel as only one channel is available.

Example 3 - Specifying the Expected Power Parameter

The previous example details the three optional parameters which can be used with the MEASure? command. The first optional parameter is used to enter an expected power value. Entering this parameter is only relevant if you are using an E- Series power sensor or N8480 Series power sensor

(excluding Option CFT). The value entered determines which of the power sensor’s two ranges is used for the measurement. If the current setting of the power sensor’s range is no longer valid for the new measurement, specifying the expected power value decreases the time taken to obtain a result.



The following example uses the expected value parameter to specify a value of –50 dBm. This selects the power sensor’s lower range (refer to

“Range” on page 37 for details of the range breaks). The resolution

parameter is defaulted, leaving it at its current setting. The source list parameter specifies a Channel B measurement. The measurement is displayed on the lower window.

specifies expected power value specifies window

MEAS2? -50,DEF,(@2) specifies channel

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 ).

Since the filter length used for a channel with auto- averaging enabled is dependent on the window resolution setting, a conflict arises when a given channel is set up in both windows and the resolution settings are different. In this case, the higher resolution setting is used to determine the filter length.

The following example uses the resolution parameter to specify a resolution setting of 3. This setting represents 3 significant digits if the measurement suffix is W or %, and 0.01 dB if the suffix is dB or dBm.

Refer to Chapter 2 , “MEASurement Commands”on page 87, for further details

on the resolution parameter. The expected power and source list parameters are defaulted in the example. The expected power value remains unchanged at its current setting. The source list parameter defaults as described in the note

“Agilent N1912A Only” on page 15. Note

that as the source list parameter is the last specified parameter you do not have to specify DEF. The measurement is carried out on the upper window.

specifies window specifies resolution setting

MEAS1? DEF,3



Example 5 - Making a Difference Measurement

The following command is performed on the N1912A. It queries the lower window to make a difference measurement of Channel B - Channel A. The expected power and resolution parameters are defaulted, leaving them at their current settings.

specifies window specifies between which channels the difference is calculated

MEAS2:POW:AC:DIFF? DEF,DEF,(@2),(@1)

Channel B - A

Example 6 - Making a Ratio Measurement

The following command is performed on the N1912A. 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 window specifies the relationship of the channels in the ratio

MEAS1:POW:AC:RAT? DEF,DEF,(@1),(@2)

Channel A / B

N O T E

Agilent N1912A Only

The operation of the MEASure? command when the source list parameter is defaulted depends on the current setup of the window concerned (for example, A, B, A/B, A-B etc.) and on the particular command used (for example, MEAS[:POW][:AC]? and

MEAS:POW:AC:RAT?

).

This means that when the source list parameter is defaulted, there are a number of possibilities.



Table 1-2 Possibilities of the defaulted source list parameter

Command

MEAS1[:POW][AC]?

MEAS2[:POW][AC]?

MEAS1:POW:AC:RAT

MEAS2:POW:AC:RAT

MEAS1:POW:AC:DIFF?

MEAS2:POW:AC:DIFF?

Current Window Setup

Upper Window:

Any Other

Lower Window:

Upper Window:

Lower Window:

Upper Window:

Lower Window:

A

B

Any Other

A

B

Any Other

A/B

B/A

Any Other

A/B

B/A

Any Other

A-B

B-A

Any Other

A-B

B-A

Any Other

Measurement

A-B

B-A

A-B

A-B

A/B

A/B

B/A

A/B

B-A

A-B

A

A

A

B

B

B

A/B

B/A



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. This allows you to change the power meter’s configuration from the preset conditions.

The power meter offers a variety of low- level commands in the SENSe,

CALCulate , and TRIGger subsystems. For example, if you want to change the averaging use the [SENSe[1]]|SENSe2:AVERage:COUNt command.

Use the INITiate or READ? query to initiate the measurement.

Using READ?

CONFigure does not take the measurement. One method of obtaining a result is to use the READ? query. The READ? query takes the measurement using the parameters set by the CONFigure command then sends the reading to the output buffer. Using the READ? query obtains new data.

Using INITiate and FETCh?

CONFigure

does not take the measurement. One method of obtaining the result is to use the INITiate and FETCh? commands. The INITiate command causes the measurement to be taken. The FETCh? query retrieves a reading when the measurement is complete, and sends the reading to the output buffer. FETCh? can be used to display the measurement results in a number of different formats (for example, A/B and B/A) without taking fresh data for each measurement.

CONFigure Examples

The following program segments show how to use the commands READ?,

INITiate and FETCh? and CONFigure to make measurements.

It is advisable to read through these examples in order as they become increasingly more detailed.

These examples give an overview of the CONFigure command. For further information on the CONFigure commands refer to

Chapter 2 ,

“MEASurement Commands”.



18

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?

*RST

CONF1

READ1?

Reset instrument

Configure upper window - defaults to a Channel A measurement

Take upper window (Channel A) measurement

*RST

CONF2

READ2?

Reset instrument

Configure lower window - defaults to a Channel A (N1911A),

Channel B (N1912A) measurement

Take lower window measurement (Channel A on N1911A, B on N1912A)


*RST

CONF1

INIT1?

FETC1?

Reset instrument

Configure upper window - defaults to a Channel A measurement

Causes Channel A to make a measurement

Retrieves the upper window’s measurement

For the N1911A only:

*RST

CONF2

INIT1

FETC2?

Reset instrument

Configure lower window - N1911A defaults to Channel A


Retrieves the lower window’s measurement

For the N1912A only:

*RST

CONF2

INIT2?

Reset instrument

Configure lower window

Causes Channel B to make a measurement



N O T E

FETC2?


Example 2 - Specifying the Source List Parameter

The CONFigure and READ? commands have 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.

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. If they are defined they must be identical to those defined in the CONFigure command otherwise an error occurs.

For the N1911A it is not necessary to specify a channel as only one channel is available.

Using READ?

ABOR1

CONF1 DEF,DEF,(@1)

READ1?

Aborts Channel A

Configures the upper window to make a

Channel A measurement using the current expected power and resolution settings

Takes the upper window’s measurement




ABOR1

CONF1 DEF,DEF,(@1)

INIT1

FETC1? DEF,DEF,(@1)

Aborts Channel A


Channel A measurement using the current expected power and resolution settings



Example 3 - Specifying the Expected Power Parameter

The previous example details the three optional parameters which can be used with the CONFigure and READ? commands. The first optional parameter is used to enter an expected power value. Entering this parameter is only relevant if you are using an E- Series power sensor or

N8480 Series power sensor (excluding Option CFT). The value entered determines which of the power sensor’s two ranges is used for the measurement. If the current setting of the power sensor’s range is no longer valid for the new measurement, specifying the expected power value decreases the time taken to obtain a result.

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 37 for details of the range breaks). The resolution

parameter is defaulted, leaving it at its current setting. The source list parameter specifies a Channel B measurement. The measurement is carried out on the upper window.



Using READ?

ABOR2

CONF1 -50,DEF,(@2)

READ1?

Aborts Channel B


Channel B measurement using an expected power of –50 dBm and the current resolution setting

Takes the upper window’s measurement

Some fine tuning of measurements can be performed using the CONFigure and READ? commands. For example, in the above program segment some fine tuning can be performed by setting the filter length to 1024 and the trigger delay off.

1 ABOR2

2 CONF1 -50,DEF,(@2)

3 SENS2:AVER:COUN 1024

4 TRIG2:DEL:AUTO OFF

5 READ1?


ABOR2

CONF1 -50,DEF,(@2)

INIT2

Aborts Channel B


Channel B measurement using an expected power of –50 dBm and the current resolution setting

Causes Channel B to make a measurement

FETC1? -50,DEF,(@2) Retrieves the upper window’s measurement

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


1 Power Meter Remote Operation setting the filter length to 1024 and the trigger delay off.

1 ABOR2

2 CONF1 -50,DEF,(@2)

3 SENS2:AVER:COUN 1024


5 INIT2

6 FETC1? -50,DEF,(@2)

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 on page 35

).

Since the filter length used for a channel with auto- averaging enabled is dependent on the window resolution setting, a conflict arises when a given channel is set up in both windows and the resolution settings are different. In this case, the higher resolution setting is used to determine the filter length.

The following example uses the resolution parameter to specify a resolution setting of 3. This setting represents 3 significant digits if the measurement suffix is W or %, and 0.01 dB if the suffix is dB or dBm (for further details on the resolution parameter refer to the commands in

Chapter 2 , “MEASurement Commands”). Also, in this example the

expected power and source list parameters are defaulted. The expected power value is left unchanged at its current setting. The source list parameter is defaulted as described in the note

“Agilent N1912A Only” on page 15. Note that as the source list parameter is the last specified

parameter you do not have to specify DEF.



Using READ?

ABOR1

CONF1 DEF,3

READ1?

Aborts Channel A

Configures the upper window to make a measurement 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 or B measurement depending on current window setup.

Some fine tuning of the above program segment can be carried out for example, by setting the trigger delay off. The following program segment assumes that Channel A is currently being measured on the upper window.

1 ABOR1

2 CONF1 DEF,3


4 READ1?


The following program segment assumes that Channel A is currently being measured on the upper window.

ABOR1

CONF1 DEF,3

INIT1

FETC1? DEF,3

Aborts Channel A

Configures the upper window to make a measurement using the current setting of the expected power and source list and a resolution setting of 3



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




4 INIT1:IMM

5 FETC1? DEF,3

Example 5 - Making a Difference Measurement

The following program segment can be carried out on the N1912A. It queries the lower window to make a difference measurement of

Channel A - Channel B. The expected power level and resolution parameters are defaulted, leaving them at their current settings. Some fine tuning of the measurement is carried out by setting the averaging, and the trigger delay to off.

Using READ?

ABOR1

ABOR2

CONF2:POW:AC:DIFF DEF,DEF,(@1),(@2)

SENS1:AVER:COUN 1024


TRIG1:DEL:AUTO OFF

TRIG2:DEL:AUTO OFF

READ2:POW:AC:DIFF?

READ2:POW:AC:DIFF? DEF,DEF,(@2),(@1)

(A second READ? query is sent to make a Channel B - Channel A measurement using fresh measurement data).


ABOR1

ABOR2

CONF2:POW:AC:DIFF DEF,DEF,(@1),(@2)



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).

Example 6 - Making a Ratio Measurement

The following program segment can be carried out on the N1912A. It queries the lower window to make a ratio measurement of Channel A/B.

The expected power level and resolution parameters are defaulted, leaving them at their current settings. Some fine tuning of the measurement is carried out by setting the averaging.

Using READ?

ABOR1

ABOR2

CONF2:POW:AC:RAT DEF,DEF,(@1),(@2)

SENS1:AVER:COUN 512

SENS2:AVER:COUN 256

READ2:POW:AC:RAT?

READ2:POW:AC:RAT? DEF,DEF,(@2),(@1)

(A second READ? query is sent to make a Channel B - Channel A ratio measurement using fresh measurement data.)


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. This can be done using the following commands:

[SENSe[1]]|SENSe2:POWER:AC:RANGe

DISPlay[:WINDow[1|2]]:RESolution

The measurement type can be set using the following commands in the

CALCulate subsystem:

CALCulate[1|2]:MATH[:EXPRession]

CALCulate[1|2]:RELative[:MAGNitude]

The advantage of using the lower level commands over the CONFigure command is that they give you more precise control of the power meter.

As shown in

Table 1- 1

the CONFigure command presets various states in the power meter. It may be likely that you do not want to preset these states.

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.

ABOR1

CALC2:MATH:EXPR

"(SENS1)"

SENS1:POW:AC:RANGE 0

Aborts Channel A

Displays Channel A on lower window

DISP:WIND2:RES 3

INIT1

FETC2?

Sets lower range (E- Series sensors and

N8480 Series sensors (excluding Option

CFT) only)

Sets the lower window’s resolution to setting

3





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. When

[SENSe[1]]|SENSe2:CORRection:CSET2:STATe is ON, the frequency dependent offset tables are used, providing you with a quick and convenient method of compensating for your external test setup over a range of frequencies. Note that when selected, frequency dependent offset correction is IN ADDITION to any correction applied for sensor frequency response. The power meter is capable of storing 10 frequency dependent offset tables of 80 frequency points each.

To use frequency dependent offset tables you:

1 Edit a frequency dependent offset table if necessary.

2 Select the frequency dependent offset table.

3 Enable the frequency dependent offset table.

4 Zero and calibrate the power meter.

If you are using an 8480 Series sensors or N8480 Series sensor with

Option CFT, the reference calibration factor used during the calibration must be entered manually.

5 Specify the frequency of the signal you want to measure. The required offset is automatically set by the power meter from the frequency dependent offset table.

6 Make the measurement.

Figure 1- 1 illustrates how frequency dependent offset tables operate.



TABLE 1

FREQ

1

FREQ

.

.

.

.

.

.

.

.

.

.

.

2

FREQ

80

OFFSET

1

OFFSET

.

.

.

.

.

.

.

.

.

2

.

.

OFFSET

80

OFFSET = Frequency Dependent Offset

TABLE N

FREQ

1

FREQ

.

.

.

.

.

.

.

.

.

.

.

2

FREQ

80

OFFSET

1

OFFSET

.

.

.

.

.

.

.

.

.

.

.

2

OFFSET

80

TABLE SELECTED

Frequency of the signal you want to measure

FREQ

1

FREQ

2

.

.

.

.

.

.

.

.

.

.

.

FREQ

80

OFFSET

1

OFFSET

2

.

.

.

.

.

.

.

.

.

.

.

OFFSET

80

Figure 1-1 Frequency Dependent Offset Tables

TABLE 10

FREQ

1

FREQ

.

.

.

.

.

.

.

.

.

.

.

2

FREQ

80

OFFSET

1

OFFSET

.

.

.

.

.

.

.

.

.

2

.

.

OFFSET

80

Frequency dependent offset used to make

Measurement. Calculated by the power meter using linear interpolation.



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>

For information on naming frequency dependent offset tables see

“Naming Frequency Dependent Offset Tables” on page 31. For

information on the current names which you can select refer to

“Listing the Frequency Dependent Offset Table Names” on page 30.

2 Enter the frequency data using:

MEMory:TABle:FREQuency <numeric_value> {,<numeric_value>}

3 Enter the offset factors as shown in the table below using:

MEMory:TABle:GAIN <numeric_value> {,<numeric_value>}

Frequency

Frequency 1

Frequency 2

"

Frequency n

Offset

Offset 1

Offset 2

"

Offset n

4 If required, rename the frequency dependent offset table using:

MEMory:TABLe:MOVE <string> ,<string>. The first <string> parameter identifies the existing table name, and the second identifies the new table name.



30

N O T E

The legal frequency suffix multipliers are any of the IEEE suffix multipliers, for 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. Refer to the individual commands in

Chapter 4

for their specified ranges.

Any offset values entered into the table should exclude the effect of the sensor.

Characterization of the test setup independently of the sensor allows the same table to be used with any sensor.

Ensure that the frequency points you use cover the frequency range of the signals you want to measure. If you measure a signal with a frequency outside the frequency range defined in the frequency dependent offset table, then the power meter uses the highest or lowest frequency point in the table to calculate the offset.

To make subsequent editing of a frequency dependent offset table simpler, it is recommended that you retain a copy of your data in a program.

Listing the Frequency Dependent Offset Table Names

To list the frequency dependent offset tables currently stored in the power meter, use the following command:


Note that all tables are listed; including sensor calibration tables.

The power meter returns the data in the form of two numeric parameters and a string list representing all stored tables.

•

<numeric_value>,<numeric_value>{,<string>}

The first numeric parameter indicates the amount of memory, in bytes, used for storage of tables. The second parameter indicates the memory, in bytes, available for tables.

Each string parameter returned indicates the name, type and size of a stored frequency dependent offset table:

•

<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>

The first <string> parameter identifies the existing table name, and the second identifies the new table name.

The following rules apply to frequency dependent offset table names:

1 Table names use a maximum of 12 characters.

2 All characters must be upper or lower case alphabetic characters, or numeric (0- 9), or an underscore (_).

No spaces are allowed in the name.

Reviewing Table Data

To review the data stored in a frequency dependent offset table, use the following commands:

MEMory:TABLe:SELect "Offset1"

Select the sensor calibration table named “Offset1”.

MEMory:TABLe:SELect?

Query command which returns the name of the currently selected table.

MEMory:TABLe:FREQuency:POINTs?

Query command which returns the number of stored frequency points.

MEMory:TABLe:FREQuency?

Query command which returns the frequencies stored in the frequency dependent offset table (in Hz).

MEMory:TABLe:GAIN[:MAGNitude]:POINTs?

Query command which returns the number of offset factor points stored in the frequency dependent offset table.

MEMory:TABLe:GAIN[:MAGNitude]?

Query command which returns the offset factors stored in the frequency dependent offset table.

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.

Selecting a Frequency Dependent Offset Table

After you have created the frequency dependent offset table, you can select it using the following command:

[SENSe[1]]|SENSe2:CORRection:CSET2[:SELect] <string>

To find out which frequency dependent offset table is currently selected, use the query:

[SENSe[1]]|SENSe2:CORRection:CSET2[:SELect]?

32

Enabling a Frequency Dependent Offset Table

To enable the frequency dependent offset table, use the following command:

[SENSe[1]]|SENSe2:CORRection:CSET2:STATe ON

If you set [SENSe[1]]|SENSe2:CORRection:CSET2:STATe to ON and no frequency dependent offset table is selected error –221, “Settings conflict” occurs.

Making the Measurement

To make the power measurement, set the power meter for the frequency of the signal you want to measure. The power meter automatically sets the calibration factor. Use either the INITiate, FETCh? or the READ? query to initiate the measurement as shown in the following program segments:

INITiate Example

ABORt1

CONFigure1:POWer:AC DEF,1,(@1)

SENS1:CORR:CSET2:SEL "Offset1"



N O T E

SENS1:CORR:CSET2:STAT ON

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 frequency dependent offset table, the power meter calculates the offset using linear interpolation.

If you enter a frequency outside the frequency range defined in the frequency dependent offset table, then the power meter uses the highest or lowest frequency point in the table to set the offset.

To find out the value of the offset being used by the power meter to make a measurement, use the query command:

SENSe:CORRection:GAIN4|FDOFfset[:INPut][MAGNITUDE]?

The response may be an interpolated value.



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>

There are four levels of resolution available (1 through 4).

When the measurement suffix is W or % this parameter represents the number of significant digits. When the measurement suffix is dB or dBM,

1 through 4 represents 1, 0.1, 0.01, and 0.001 dB respectively.

Refer to the :RESolution command on

page 241 for further information.

Averaging

The power meter has a digital filter to average power readings. The number of readings averaged can range from 1 to 1024. This filter is used to reduce noise, obtain the desired resolution and to reduce the jitter in the measurement results. However, the time to take the measurement is increased. You can select the filter length or you can set the power meter to auto filter mode. To enable and disable averaging use the following command:

[SENSe[1]]|SENSe2:AVERage[:STATe] <boolean>



N O T E

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. The number of readings averaged together depends on the resolution and the power level currently

being measured. Figure 1- 2

lists the number of readings averaged for each range and resolution when the power meter is in auto filter mode.

Figure 1-2 applies to 8480 Series

only.

Minimum Sensor Power

10 dB

10 dB

10 dB

1

8

1

1

Resolution Setting

2

8

1

1

3

128

10 dB 1 1 1

1 1

Maximum Sensor Power

Figure 1-2 Typical Averaged Readings on 8480 Series Sensors

1

16

2

4

128

8

256

32

16

Figure 1- 3 illustrates part of the power sensor dynamic range hysteresis.



Range Hysteresis

Minimum Sensor Power

Figure 1-3 Averaging Range Hysteresis

9.5 dB 10.5 dB

Minimum Sensor Power + 10 dB

Filter Length

You specify the filter length using the following command:

[SENSe[1]]|SENSe2:AVERage:COUNt <numeric_value>

The range of values for the filter length is 1 to 1024. Specifying this command disables automatic filter length selection. Increasing the value of the filter length reduces measurement noise. However, the time to take the measurement is increased.



Range

The power meter has no internal ranges which can be set. The only ranges that can be set are those of the E- Series power sensor and N8480 Series power sensors (excluding Option CFT). With an E- Series power sensor or

N8480 Series power sensors (excluding Option CFT), the range can be set either automatically or manually. Use autoranging when you are not sure of the power level you will be measuring.

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.)

• 1, the sensor’s upper range is selected. (For example, this range is

–14.5 to +20 dBm for the E4412A power sensor.)

For details on the range limits of other E- Series power sensor and N8480

Series power sensor (excluding Option CFT), refer to the appropriate power sensor manual.

For further information on this command refer to

page 428 .

To enable autoranging use the following command:

[SENSe[1]]|SENSe2:POWer:AC:RANGe:AUTO ON

Use autoranging when you are not sure of the power level you will be measuring.



Setting Offsets

N O T E

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. This means that a gain set by [SENSe[1]]|SENSe2:CORRection:GAIN2 is represented in the [SENSe[1]]|SENSe2:CORRection:LOSS2? command. If you enter an offset value the state is automatically enabled. However it can be enabled and disabled using either the

[SENSe[1]]|SENSe2:CORRection:GAIN2:STATe or

[SENSe[1]]|SENSe2:CORRection:LOSS2:STATe commands.

LOSS2 is coupled to GAIN2 by the equation Loss unit

=

Gain

when the default is linear, and Gain = – Loss when the default is logarithmic.

You can only use LOSS2 and GAIN2 for external losses and gains. LOSS1 and GAIN1 are specifically for calibration factors.

38

Display Offsets

Display offset values can be entered using the

CALCulate[1|2]:GAIN[:MAGNitude] command.

CALCulate[1|2]:GAIN:STATe must be set to ON to enable the offset value. If you enter an offset value the state is automatically enabled. This

offset is applied after any math calculations (refer to Figure 1- 6 on page 49).

Example

The following example program, in HP Basic, details how to use the channel and display offsets on an N1912A making a Channel A/B ratio measurement.



The final result is:

⎛

⎝

⎛

⎝

A dBm

B dBm

–

–

10

10

⎞ 20 ⎞

⎠ dB

10 !Create I/O path name

20 ASSIGN @POWER TO 713

30 !Clear the power meter’s interface

40 CLEAR @POWER

50 !Set the power meter to a known state

60 OUTPUT @POWER;"*RST"

70 !Configure the Power Meter to make the measurement

80 OUTPUT @Power;"CONF:POW:AC:RAT 20DBM,2,(@1),(@2)"

90 !Set the measurement units to dBm

100 OUTPUT @POWER;"UNIT:POW DBM"

110 !Set the power meter for channel offsets of -10 dB

120 OUTPUT @POWER;"SENS1:CORR:GAIN2 -10"

130 OUTPUT @POWER;"SENS2:CORR:GAIN2 -10"

140 !Enable the gain correction

150 OUTPUT @POWER;"SENS:CORR:GAIN2:STATe ON"

160 OUTPUT @POWER;"SENS2:CORR:GAIN2:STATe ON"

170 !Set the power meter for a display offset of -20 dB

180 OUTPUT @POWER;"CALC1:GAIN -20 DB"

190 PRINT "MAKING THE MEASUREMENT"

200 !Initiate the measurement

210 OUTPUT @Power;"INIT1:IMM"

220 OUTPUT @Power;"INIT2:IMM"

230 ! ... and get the result

240 OUTPUT @Power;"FETC:POW:AC:RAT? 20DBM,2,(@1),(@2)"

250 ENTER @Power;Reading

260 !

270 PRINT "The measurement result is ";Reading;"dB."

280 END

For further information on channel offsets refer to

page 403

. For further

information on display offsets refer to page 168 .



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.

Setting Limits

The power meter can be configured to verify the power being measured against an upper and/or lower limit value. The range of values that can be set for lower and upper limits is –150.00 dBm to +230.00 dBm. The default upper limit is +90.00 dBm and the default lower limit is

–90.00 dBm.

A typical application for this feature is shown in Figure 1- 4 .

Power Meter

Swept Source

Device

Under Test

OUT IN OUT

CHANNEL A

INPUT

Figure 1-4 Limits Checking Application



Amplitude

+10 dBm o o o

Fail o o o

+4 dBm o

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 .



Table 1-3 Range of Values for Window Limits

Window

Units dB dBm

%

W

Maximum

+200 dB

+230 dBm

999.9 X%

100.000 XW

Minimum

– 180 dB

– 150 dBm

100.0 a%

1.000 aW

Maximum

60 dB

90 dBm

100.0 M%

1.000 MW

Default

Minimum

– 120 dB

– 90 dBm

100.0 p%

1.000 pW

Checking for Limit Failures

There are two ways to check for limit failures:

1 Use the SENSe:LIMit:FAIL? and SENSe:LIMit:FCOunt? commands for channel limits or the

CALCulate[1|2]:LIMit:FAIL?

and the

CALCulate[1|2]:LIMit:FCOunt?

for window limits

2 Use the STATus command subsystem

Using SENSe and CALCulate

Using SENSe to check the channel limit failures in

Figure 1- 5

would return the following results:

SENSe:LIMit:FAIL?

SENSe:LIMit:FCOunt?

Returns 1 if there has been 1 or more limit failures or 0 if there have been no limit failures. In this case 1 is returned.

Returns the total number of limit failures, in this case 2.

Use the equivalent CALCulate commands for checking window limit failures.



N O T E

If TRIGger:DELay:AUTO is set to ON, then the number of failures returned by

SENSe:LIMit:FCOunt? or CALCulate[1|2]:LIMit:FCOunt? is affected by the current filter settings.

Using STATus

If using GPIB, you can use the STATus subsystem to generate an SRQ to interrupt your program when a limit failure occurs. This is a more efficient method than using SENSe or CALCulate, since you do not need to check the limit failures after every power measurement.

Refer to “Status Reporting” on page 50 and

“STATus Subsystem” on page 465 for further information.



Getting the Best Speed Performance

This section discusses the factors that influence the speed of operation

(number of readings/sec) of a P- Series power meter.

The following factors are those which have the greatest effect upon measurement speed (in no particular order):

• The selected measurement rate, i.e. NORMal, DOUBle, FAST.

• The sensor being used.

• The trigger mode (for example, free run, trigger with delay etc.).

• The output format: ASCii or REAL.

• The units used for the measurement.

• The command used to take a measurement.

In addition, in FAST mode there are other influences which are described in

“Fast Mode” on page 48.

The following paragraphs give a brief description of the above factors and how they are controlled from SCPI.

Measurement Rate

There are three possible speed settings NORMal, DOUBle and FAST. These are set using the SENSe:MRATe command and can be applied to each channel independently (N1912A only).

In NORMal and DOUBle modes, full instrument functionality is available and these settings can be used with all sensors. FAST mode is only available for the P- Series and E- Series sensors. Also, in FAST mode averaging, limits and ratio/difference math functions are disabled.

Refer to “Specifications” in the P- Series Power Meters User’s Guide to see the influence of these speed settings on the accuracy and noise performance of the power meter.



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

8480 Series and N8480 Series

E-Series E4410 and E9300

E-Series E9320,

AVERage only mode

E-Series E9320,

NORMal mode

Measurement Rate

NORMal

20 reading/s

50 ms

20 reading/s

50 ms

20 reading/s

50 ms

20 reading/s

DOUBle

40 reading/s

25 ms

40 reading/s

25 ms

40 reading/s

25 ms

40 reading/s

FAST

NA

Up to 400

Up to 400

Up to 1000

Up to 1500

20 reading/s 40 reading/s

Trigger Mode

The power meter has a very flexible triggering system. For simplicity, it can be described as having three modes:

• Free Run : When a channel is in Free Run, it continuously takes measurements on this channel. A channel is in free run when

INITiate:CONTinuous is set to ON and TRIGger:SOURce is set to

IMMediate .

• Triggered Free Run: When a channel is in Triggered Free Run

Continuous Trigger, it takes a new measurement each time a trigger event is detected. A channel is in Triggered Free Run Continuous

Trigger when INITiate:CONTinuous is set to ON and TRIGger:SOURce is not set to IMMediate.



N O T E

• Single Shot: When a channel is in Single Shot, it takes a new measurement when a trigger event is detected and then returns to the idle state. A channel is in Single Shot when INITiate:CONTinuous is set to OFF. Note that a measurement can take several INT/EXT triggers depending on the filter settings. Refer to

“TRIGger[1]|2:DELay:AUTO

<boolean>” on page 659 for further information.

A trigger event can be any of the following:

• 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. Also, the MEAS? command operates in trigger with delay mode.

In trigger with delay mode, a measurement is not completed until the power meter filter is full. In this way, the reading returned is guaranteed to be settled. In all other modes, the result returned is simply the current result from the filter and may or may not be settled. This depends on the current length of the filter and the number of readings that have been taken since a change in power level.

With trigger with delay enabled, the measurement speed can be calculated roughly using the following equation:

readings/sec = speed (as set by SENSe:SPEed) / filter length

For example, with a filter length of 4 and SENS:SPE set to 20, approximately 5 readings/sec is calculated by the power meter.

Typically, free run mode provides the best speed performance from the power meter (especially in 200 readings/sec mode).



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> as an end sentinel of the block.

The REAL format is likely to be required only for FAST mode as it reduces the amount of bus traffic.

Units

The power meter can output results in either linear or log units. The internal units are linear, therefore optimal performance is achieved when the results output are also in linear units (since the overhead of performing a log function is removed).

Command Used

In Free Run mode, FETCh? must be used to return a result.

In other trigger modes, there are a number of commands which can be used, for example, MEASure?, READ?, FETCh? Note that the MEAS? and

READ? commands are compound commands—they perform a combination of other lower level commands. Typically, the best speed performance is achieved using the low level commands directly.

Trigger Count

To get the fastest measurement speed the a TRIG:COUNT must be set to return multiple measurements for each FETCh command. For average only measurements a count of 4 is required, however, 10 is recommended. In normal mode (peak measurements) a count of 50 is required to attain

1000 readings per second.



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. The former is a combination of two factors:

• the hardware platform being used

• the programming environment being used



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.

TRACe:DATA?

“TRACe1”

TRACe:DATA?

“TRACe2”

WINDow1

WINDow2

FORMat

SENSe1

:BAND:VID (B/W)

:AVER2 (video averaging)

Sensor

Video

Filter

Data

Selection

Freq.

Corr.

Filter Offset

Duty

Cycle

:SPEed

:POW:AC:RANG

:POW:AC:RANG:AUTO:DIR

:DET:FUNC

:FREQ

:CORR:CFAC

:CORR:CSET

:SWEep:TIME:GATE:DELay

:SWEep:TIME:GATE:LENGth

:AVER[1]

:CORR:DCYC

:CORR:GAIN2

:CORR:LOSS2

SENSe2

:BAND:VID (B/W)

:AVER2 (video averaging)

Sensor

Video

Filter

Data

Selection

Freq.

Corr.

Filter Offset

Duty

Cycle

:SPEed

:POW:AC:RANG

:POW:AC:RANG:AUTO:DIR

:DET:FUNC

:FREQ

:CORR:CFAC

:CORR:CSET

:SWEep:TIME:GATE:DELay

:SWEep:TIME:GATE:LENGth

:AVER[1]

:CORR:DCYC

:CORR:GAIN2

:CORR:LOSS2

TRIGger

CALCulate1

:FEED

Switch

Switch

CALCulate4

:FEED

Switch

Switch

Maths

:MATH

Offset

:GAIN

:LIM

Relative

Limits

:REL

UNIT1

Conversion

:POW

CALCulate3

:FEED

Switch

Switch

Maths

:MATH

Offset

:GAIN

:LIM

Relative

Limits

:REL

UNIT3

Conversion

:POW

CALCulate2

:FEED

Switch

Switch

Maths

:MATH

Offset

:GAIN

:LIM

Relative

Limits

:REL

UNIT2

Conversion

:POW

Maths

:MATH

Offset

:GAIN

Relative

Limits

:REL

:LIM

UNIT4

Conversion

:POW

Switch

Switch

Switch

Switch

MEAS?

READ?

FETC?

CONF

DISPlay

[WINDow[1]]

Upper Meas

:NUMeric[1]:RESolution

Lower Meas

:NUMeric2:RESolution

:FORMat

:METer

:SELect [1]|2

WINDow2

Upper Meas

:NUMeric[1]:RESolution

Lower Meas

:NUMeric2:RESolution

:FORMat

:METer

:SELect [1]|2

:CONTrast

:ENABle

:FORMat

Figure 1-6 How Measurement are Calculated

The MEASure commands in this figure can be replaced with the FETCh? and READ? commands.

All references to Channel B in the above diagram refer to the N1912A only.

N O T E



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

• Standard Event Register

• Operation Status Register

• Questionable Status Register

• Device Status Register

There are other registers that exist “behind” the main registers, and are described later in this chapter.

Status and Standard Event registers are read using the IEEE- 488.2 common commands.

Operation and Questionable Status registers are read using the SCPI

STATus command subsystem.

The General Status Register Model

The generalized status register model shown in

Figure 1- 7

is the building block of the SCPI status system. This model consists of a condition register, a transition filter, an event register and an enable register. A set of these registers is called a status group.



Bit 0

Bit 1

Bit 2

Bit 3

0

1

2

Condition

Register

Transition

Filter

Event

Register

Enable

Register

Summary

Bit

Figure 1-7 Generalized Status Register Model

When a status group is implemented in an instrument, it always contains all of the component registers. However, there is not always a corresponding command to read or write to every register.

Condition Register

The condition register continuously monitors the hardware and firmware status of the power meter. There is no latching or buffering for this register, it is updated in real time. Condition registers are read- only.

Transition Filter

The transition filter specifies which types of bit state changes in the condition registers and set corresponding bits in the event register.

Transition filter bits may be set for positive transitions (PTR), negative transitions (NTR), or both. Transition filters are read- write. They are unaffected by *CLS or queries. After STATus:PRESet the NTR register is set to 0 and all bits of the PTR are set to 1.

Event Register

The event register latches transition events from the condition register as specified by the transition filter. Bits in the event register are latched and on setting they remain set until cleared by a query or a *CLS. Also on setting, an event bit is no longer affected by condition changes. It remains set until the event register is cleared; either when you read the register or when you send the *CLS (clear status) command. Event registers are read- only.



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. Querying an enable register does not affect it.

An Example Sequence

Figure 1- 8 illustrates the response of a single bit position in a typical status group for various settings. The changing state of the condition in question is shown at the bottom of the figure. A small binary table shows the state of the chosen bit in each status register at the selected times T1 to T5.

A

B

C

D

0 0

0 1

1 0

1 1

0

1

1

0

Condition

1

0

0 0

0

0

0 0

0 0 0

0 0 0

1

1

1

1

0

0

1

1

0

0

1

0

1

1

1

0

0

1 0

0

* T1 T2 * T3

* marks when event register is read

Figure 1-8 Typical Status Register Bit Changes

0

0

0

0

0 0

0 1

0 0

0 1

0

1

0

0

T4 *

0

0

0

0 0 0

0

0

0 0

0

0

T5



How to Use Register

There are two methods to access the information in status groups:

• the polling method, or

• the service request (SRQ) method. (GPIB mode only)

Use the polling method 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.

Use the SRQ method when you:

• need time critical notification of changes.

• are monitoring more than one device which supports SRQ interrupts.

• need to have the controller do something else while it is waiting.

• cannot afford the performance penalty inherent to polling.

The Condition Polling Method

In this polling method, the power meter has a passive role. It only informs the controller that conditions have changed when the controller asks.

When you monitor a condition with the polling method, you must:

1 Determine which register contains the bit that monitors the condition.

2 Send the unique query that reads that register.

3 Examine the bit to see if the condition has changed.

The polling method works well if you do not need to know about the changes the moment they occur. The SRQ method is more effective if you must know immediately when a condition changes. Detecting an immediate change in a condition using the polling method requires your program to continuously read the registers at very short intervals. This is not particularly efficient and there is a possibility that an event may be missed.



For example on measurement polling, refer to

Figure B- 16 on page B- 2.

N O T E

The SRQ Method

When a bit of the Status Register is set and has been enabled to assert

SRQ (*SRE command), the power meter sets the GPIB SRQ line true. This interrupt can be used to interrupt your program, suspending its current operation, and find out what service the power meter requires. Refer to your computer and language manuals for information on how to program the computer to respond to the interrupt.

To allow any of the Status Register bits to set the SRQ line true, you must enable the appropriate bit(s) with the *SRE command. For example, if your application requires an interrupt whenever a message is available in the output queue (Status Register bit 4, decimal weight 16). To enable bit

4 to assert SRQ, use the command *SRE 16.

You can determine which bits are enabled in the Status Register using *SRE?. This command returns the decimal weighted sum of all the bits.

Procedure

• Send a bus device clear message

• Clear the event registers with the *CLS (clear status) command

• Set the *ESE (standard event register) and *SRE (status byte register) enable masks

• Enable your bus controller’s IEEE- 488 SRQ interrupt

Examples

The following two examples are written in HP BASIC and illustrate possible uses for SRQ. In both cases, it is assumed that the power meter has been zeroed and calibrated.



Example 1:

10 ! Program to generate an SRQ when a channel A sensor

20 ! connect or disconnect occurs

30 !

50 ON ON INTR 7 GOTO Srq_i! Define service request handler

60 CLEAR @Pm ! Selective device clear

70 OUTPUT @Pm;”*CLS;*RST” ! Clear registers and resetmeter

80 !

90 ! Configure the device status register so that a sensor

100 ! connect or disconnect on channel A will cause an SRQ.

110 !

120 OUTPUT @Pm;”STAT:DEV:ENAB 2”

130 OUTPUT @Pm;”STAT:DEV:NTR 2”

140 OUTPUT @Pm;”STAT:DEV:PTR 2”

150 OUTPUT @Pm;”*SRE 2”

160 !

170 ENABLE INTR 7;2 ! Enable an SRQ to cause an interrupt

180 LOOP ! Idle loop

190 ! Forever

200 END LOOP

210 !

220 ! When a SRQ is detected, the following routine will service it.

230 !

240 Srq_i: !

250 St=SPOLL(@Pm) ! Serial Poll (reads status byte)

260 IF BIT(St,1)=1 THEN ! Device status reg bit set ?

270 OUTPUT @Pm;”STAT:DEV:EVEN?” ! Yes , read register

280 ENTER @Pm;Event ! (this also clears it)

290 OUTPUT @Pm;”STAT:DEV:COND?”

300 ENTER @Pm;Cond

310 IF Cond=0 THEN

320 PRINT “Sensor disconnected”

330 ELSE

340 PRINT “Sensor connected”

350 END IF

360 END IF

370 GOTO 170 ! Return to idle loop



56

380 END

Example 2:

10 ! Program to generate an SRQ when an over limit

20 ! condition occurs.

30 !

40 ASSIGN @Pm TO 713 ! Power meter GPIB address

50 ON INTR 7 GOTO Srq_i ! Define service request handler

60 CLEAR @Pm ! Selective device clear

70 OUTPUT @Pm;”*CLS” ! Clear registers

80 OUTPUT @Pm;”SYST:PRES” ! Preset meter

90 !

100 ! Set upper limit to 2dBm and configure the operation status

110 ! so that an over limit condition will cause an SRQ.

120 !

130 OUTPUT @Pm;”CALC:LIM:UPP 2DBM”

140 OUTPUT @Pm;”CALC:LIM:STAT ON”

150 OUTPUT @Pm;”STAT:OPER:PTR 4096”

160 OUTPUT @Pm;”STAT:OPER:ENAB 4096”

170 OUTPUT @Pm;”*SRE 128”

180 !

190 ENABLE INTR 7;2 ! Enable an SRQ to cause an interrupt

200 LOOP ! Idle loop

210 ! Forever

220 END LOOP

230 !

240 ! When a SRQ is detected, the following routine will service it.

250 !

260 Srq_i: !

270 St=SPOLL(@Pm) ! Serial Poll (reads status byte)

280 IF BIT(St,7)=1 THEN ! Operation status bit set?

290 OUTPUT @Pm;”STAT:OPER?”! Yes , read register

300 ENTER @Pm;Oper ! (this also clears it)

310 OUTPUT @Pm;”STAT:OPER:ULF?”

320 ENTER @Pm;Ulf

330 IF Ulf=2 THEN PRINT “Over limit detected”

340 END IF

350 GOTO 190 ! Return to idle loop



360 END

Status Registers

The Status System in the power meter is shown in Figure 1- 9 . The

Operation Status and Questionable Status groups are 16 bits wide, while the Status Byte and Standard Event groups are 8 bits wide. In all 16- bit groups, the most significant bit (bit 15) is not used and is always set to 0.



58

Device Status

Condition Event Enable

Questionable Status

Error/Event Queue

Condition Event

Output Queue

Enable

0

1

2

QUE

MAV

ESB

RQS/MSS

OPR

*STB?

Status Byte

0

1

2

QUE

MAV

ESB

X

OPR

*SRE

Standard Event

Event

*ESR

Enable

*ESE

Operation Status

Condition Event Enable

Figure 1-9 Status System



The Status Byte Summary Register

The status byte summary register reports conditions from other status registers. Query data waiting in the power meter’s output buffer is immediately reported through the “message available” bit (bit 4). Clearing an event register clears the corresponding bits in the status byte summary register. Reading all messages in the output buffer, including any pending queries, clears the message available bit.

Table 1-5 Bit Definitions - Status Byte Register

0

1

Bit Number Decimal

Weight

1

2

6

7

4

5

2

3

4

8

16

32

64

128

Definition

Not Used (Always set to 0)

Device Status Register summary bit.

One or more bits are set in the Device Status Register (bits must be “enabled” in enable register)

Error/Event Queue

Questionable Status Register summary bit.

One or more bits are set in the Questionable Status Register

(bits must be “enabled” in enable register).

Data Available

Data is available in the power meter’s output buffer.

Standard Event

One or more bits are set in the Standard Event register (bits must be “enabled” in enable register).

Request Service

The power meter is requesting service (serial poll).

Operation Status Register summary bit.

One or more bits are set in the Operation Status Register (bits must be “enabled” in enable register).

Particular bits in the status byte register are cleared when:

• The standard event, Questionable status, operation status and device status are queried.

• The error/event queue becomes empty.

• The output queue becomes empty.



The status byte enable register (SRE, service request enable) is cleared when you:

• cycle the instrument power.

• execute a *SRE 0 command.

Using *STB? to Read the Status Byte

The *STB? (status byte query) command is similar to a serial poll except it is processed like any other power meter command. The *STB? command returns the same result as an IEEE- 488 serial poll except that the request service bit (bit 6) is not cleared if a serial poll has occurred. The *STB? command is not handled automatically by the IEEE- 488 bus interface hardware and the command is executed only after previous commands have completed. Using the *STB? command does not clear the status byte summary register.

The Standard Event Register

The standard event register reports the following types of instrument events: power- on detected, command and syntax errors, command execution errors, self- test or calibration errors, query errors, or when an overlapped command completes following a *OPC command. Any or all of these conditions can be reported in the standard event summary bit through the enable register. You must write a decimal value using the

*ESE (event status enable) command to set the enable register mask.

Table 1-6 Bit Definitions - Standard Event Register

1

2

Bit

Number

0

2

4

Decimal

Value

1

Definition

Operation Complete

All overlapped commands following an *OPC command have been completed.

Not Used. (Always set to 0.)

Query Error

A query error occurred, refer to error numbers 410 to 440 in the user’s guide.



Bit

Number

3 8

Decimal

Value

Definition

4 16

5 32

6 64

7 128

A device error occurred, refer to error numbers 310 to 350 in the user’s guide.

An execution error occurred, refer to error numbers 211 to 241 in the user’s guide.

A command syntax error occurred, refer to error numbers 101 to

161 in the user’s guide.

Power On

Power has been turned off and on since the last time the event register was read or cleared.

The standard event register is cleared when you:

• send a *CLS (clear status) command.

• query the event register using the *ESR? (event status register) command.

The standard event enable register is cleared when you:

• cycle the instrument power.

• execute a *ESE 0 command.

Questionable Status Register

The questionable status register provides information about the quality of the power meter’s measurement results. Any or all of these conditions can be reported in the questionable data summary bit through the enable register. You must write a value using the STATus:QUEStionable:ENABle command to set the enable register mask.

The questionable status model is shown in the pullout at the end of this chapter.

The following bits in these registers are used by the power meter.



Table 1-7 Bit Definitions - Questionable Status Registers

Bit

Number

0 to 2

3

4 to 7

8

9

10 to 14

15

Decimal

Weight

-

-

8

-

-

256

512

Definition

Not used

POWer Summary

Not used

CALibration Summary

Power On Self Test

Not Used

Not used (always 0)

The condition bits are set and cleared under the following conditions:

Table 1-8 Bit change conditions for Questionable Status Register

Bit

Number

3

Meaning

POWer

Summary

EVENts Causing Bit Changes

This is a summary bit for the Questionable POWer Register.

• SET:

Error –230, “Data corrupt or stale”

Error –231, “Data questionable;Input Overload”

Error –231, “Data questionable;Input Overload ChA”

*

Error –231, “Data questionable;Input Overload ChB”

*

Error –231, “Data questionable;PLEASE ZERO”

Error –231, “Data questionable;PLEASE ZERO ChA”

*

Error –231, “Data questionable;PLEASE ZERO ChB”

*

Error –231, ”Data questionable;Lower window log error”

*

Error –231, ”Data questionable;Upper window log error”

*

• CLEARED: When no errors are detected by the power meter during a measurement covering the causes given for it to set.



Bit

Number

8

Meaning EVENts Causing Bit Changes

9

* N1912A only

CALibration

Summary

Power On Self

Test

This is a summary bit for the Questionable CALibration

Register.

• SET:

These may be caused by

CALibration[1|2]:ZERO:AUTO ONCE or

CALibration[1|2]:AUTO ONCE or

CALibration[1|2][:ALL] or

CALibration[1|2][:ALL]?

.

Error –231, “Data questionable; ZERO ERROR”

Error –231, “Data questionable; ZERO ERROR ChA”

*

Error –231, “Data questionable; ZERO ERROR ChB”

*

Error –231, “Data questionable; CAL ERROR”

Error –231, “Data questionable; CAL ERROR ChA”

*

Error –231, “Data questionable; CAL ERROR ChB”

*

• CLEARED: When any of the commands listed above succeed and no errors are placed on the error queue.

• SET: This bit is set when the power on self test fails.

• CLEARED: When the power on self test passes.

Operation Status

The Operation Status group monitors conditions in the power meter’s measurement process.

The Operation status model is shown in the pullout at the end of this chapter.

The following bits in these registers are used by the power meter:

Table 1-9 Bit Definitions - Operation Status


Weight

0

1 - 3 -

1

Definition

CALibrating Summary

Not used



64


Weight

4

5

6 - 9

10

11

12

13 to 14

15

16

-

32

-

1024

2048

-

4096

Definition

MEASuring Summary

Waiting for TRIGger Summary

Not used

SENSe Summary

Lower Limit Fail Summary

Upper Limit Fail Summary

Not used

Not used (always 0)

4

5

10


Table 1-10 Bit change conditions for Operation Status

Bit

Number

0

Meaning

CALibrating

MEASuring

Waiting for

TRIGger

SENSe


This is a summary bit for the Operation CALibrating Register.

• SET: At beginning of zeroing (CALibration:ZERO:AUTO ONCE) and at the beginning of calibration (CALibration:AUTO ONCE). Also for the compound command/query CALibration[:ALL]?, this bit is set when sensor zeroing begins.

• CLEARED: At the end of zeroing or calibration.

This is a summary bit for the Operation MEASuring Register.

• SET: When the power meter is taking a measurement.

• CLEARED: When the measurement is finished.

This is a summary bit for the Operation TRIGger Register.

• SET: When the power meter enters the “wait for trigger” state.

• CLEARED: When the power meter enters the “idle” state.

This is a summary bit for the Operation SENSe Register.

• SET: When the power meter is reading data from the power sensor’s EEPROM.

• CLEARED: When the power meter is not reading data from the power sensor’s

EEPROM.



Bit

Number

11

Meaning

Lower Limit

Fail

12 Upper Limit

Fail


This is a summary bit for the Lower Limit Fail Register.

• SET: If a measurement is made and either a channel or window lower limit test fails.

• CLEARED: If a measurement is made and the lower limit test is not enabled or the test is enabled and passes.

This is a summary bit for the Upper Limit Fail Register.

• SET: If a measurement is made and either a channel or window upper limit test fails.

• CLEARED: If a measurement is made and the upper limit test is not enabled or the test is enabled and passes.

Device Status Register

The device status register set contains bits which give device dependent information.


Table 1-11 Bit Definitions - Device Status Register

Bit

Number

5

6

3

4

14

0

1

2

* N1912A only

Decimal

Weight

-

2

4

8

16

32

64

16384

Definition

Not used

Channel A sensor connected

Channel B sensor connected

*

Channel A sensor error

Channel B sensor error

*

Channel A sensor Front/Rear

Channel B sensor Front/Rear

*

Front Panel key press




Table 1-12 Bit change conditions for Device Status Register

Bit

Number

1

2

3

4

5

6

14

Meaning


Channel B sensor connected

Channel A error

Channel B error

Channel A

Front/Rear

Channel B

Front/Rear

Front Panel

Key Press


• SET: When a power sensor is connected to the Channel A input.

• CLEARED: When no power sensor is connected to the

Channel A input.

• SET: When a power sensor is connected to the Channel B input.

• CLEARED: When no power sensor is connected to the

Channel B input.

• SET: If the power sensor EEPROM on Channel A has failed or if there are power sensors connected to both the rear and front panel Channel A connectors.

• CLEARED: In every other condition.

• SET: If the power sensor EEPROM on Channel B has failed or if there are power sensors connected to both the rear and front panel Channel B connectors.

• CLEARED: In every other condition.

• SET: If a power sensor is connected to the Channel A rear panel.

• CLEARED: If a power sensor is connected to the Channel A front panel.

• SET: If a power sensor is connected to the Channel B rear panel.

• CLEARED: If a power sensor is connected to the Channel B front panel.

This is an event, and DOES NOT set the condition register. The bit is set in the event register which is cleared when read. Note that the transition registers are of no use for this bit.



N O T E

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. If your program reads this response before continuing program execution, you can ensure synchronization between one or more instruments and the computer.

The *OPC command sets bit 0 (Operation Complete) in the Standard Event

Status Register when all pending power meter operations are complete. By enabling this bit to be reflected in the Status Register, you can ensure synchronization using the GPIB serial poll.

For LAN and USB use the *STB? command. See “Using *STB? to Read the Status

Byte” on page 60.

Procedure

• Send a device clear message to clear the power meter’s output buffer.

• Clear the event registers with the *CLS (clear status) command.

• Enable operation complete using the *ESE 1 command (standard event register).

• Send the *OPC? (operation complete query) command and enter the result to assure synchronization.

• Send your programming command string, and place the *OPC

(operation complete) command as the last command.

• Send the *STB? (status byte query) command to poll the register. This command does not clear the status byte summary register.

In GPIB mode only you can use a serial poll to check to see when bit

5 (standard event) is set in the status byte summary register. You could also configure the power meter for an SRQ interrupt by sending *SRE

32 (status byte enable register, bit 5).

Examples

This example program uses the *OPC? command to determine when the


1 Power Meter Remote Operation power meter has finished calibrating.

CAL:AUTO ONCE

*OPC?

MEAS:POW:AC?

This example GPIB program, in HP Basic, uses the *OPC command and serial poll to determine when the power meter has finished calibrating.

The advantage to using this method over the *OPC? command is that the computer can perform other operations while it is waiting for the power meter to finish calibrating.

10 ASSIGN @Power TO 713

20 OUTPUT @Power;“*CLS”

30 OUTPUT @Power;“*ESE 1”

40 OUTPUT @Power;“CAL:AUTO ONCE;*OPC”

50 WHILE NOT BIT(SPOLL(@Power),5)

60 !(Computer carries out other operations here)

70 END WHILE

80 OUTPUT @Power;“MEAS:POW:AC?”

90 ENTER @Power;Result

100 PRINT Result

110 END



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>

*RCL <NRf>

The range of values for <NRf> in the above commands is 1 to 10.

Example Program

10 ASSIGN @POWER TO 713

20 !Configure the power meter

30 OUTPUT @POWER;“UNIT:POW W”

40 OUTPUT @POWER;“SENS:CORR:LOSS2 -10”

50 OUTPUT @POWER;“SENS:CORR:LOSS2:STAT ON”

60 !Save the configuration

70 OUTPUT @POWER;“*SAV 5”

80 PRINT “Configuration Saved”

90 !Now reset the power meter

100 OUTPUT @POWER;“*RST”

110 ! Recall the configuration

120 OUTPUT @POWER;”*RCL 5”

130 PRINT “Configuration Recalled”

140 PRINT “Save and Recall complete”

150 END



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. The status registers, the error queue, and all configuration states are left unchanged when a device clear message is received. Device clear performs the following actions.

• All measurements in progress are aborted.

• The power meter returns to the trigger “idle state”.

• The power meter’s input and output buffers are cleared.

• The power meter is prepared to accept a new command string.

For interfaces the that do not support a low-level device clear, use the ABORt command.

N O T E



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. You must specify the complete path to execute the individual lower- level commands.

“A” Subsystem “B” Subsystem “C” Subsystem

:D :E :F :G :H :I :J :K :L=:C:L

:M

Figure 1-10 Hierarchical structure of SCPI

:N=:B:H:N

Mnemonic Forms

Each keyword has both a long and a short form. A standard notation is used to differentiate the short form keyword from the long form keyword.

The long form of the keyword is shown, with the short form portion shown in uppercase characters, and the rest of the keyword shown in lowercase characters. For example, the short form of TRIGger is TRIG.

Using a Colon (:)

When a colon is the first character of a command keyword, it indicates that the next command mnemonic is a root- level command. When a colon is inserted between two command mnemonics, the colon moves the path


1 Power Meter Remote Operation down one level in the present path (for the specified root- level command) of the command tree. You must separate command mnemonics from each other using a colon. You can omit the leading colon if the command is the first of a new program line.

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.

:DISP:FORM DIG;:DISP:RES 2

:DISP:FORM DIG;RES 2

Using a Comma (,)

If a command requires more than one parameter, you must separate adjacent parameters using a comma.

Using Whitespace

You must use whitespace characters, [tab], or [space] to separate a parameter from a command keyword. Whitespace characters are generally ignored only in parameter lists.

Using “?” Commands

The bus controller may send commands at any time, but a SCPI instrument may only send responses when specifically instructed to do so.

Only query commands (commands that end with a “?”) instruct the instrument to send a response message. Queries return either measured values or internal instrument settings.



N O T E

If you send two query commands without reading the response from the first, 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. When you cannot avoid this situation, send a device clear before sending the second query command.

Using “*” Commands

Commands starting with a “*” are called common commands. They are required to perform the identical function for all instruments that are compliant with the IEEE- 488.2 interface standard. The “*” commands are used to control reset, self- test, and status operations in the power meter.

Syntax Conventions

Throughout this guide, the following conventions are used for SCPI command syntax.

• Square brackets ([]) indicate optional keywords or parameters.

• Braces ({}) enclose one or more parameters that may be included zero or more times.

• Triangle brackets (<>) indicate that you must substitute a value for the enclosed parameter.

• Bars (|) can be read as “or” and are used to separate alternative parameter options.

Syntax Diagram Conventions

• Solid lines represent the recommended path.

• Ovals enclose command mnemonics. The command mnemonic must be entered exactly as shown.



• Dotted lines indicate an optional path for by passing secondary keywords.

• Arrows and curved intersections indicate command path direction.

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.

<boolean> Definition

Throughout this document <boolean> is used to represent ON|OFF|<NRf>. boolean parameters have a value of 0 or 1 and are unitless. ON corresponds to 1 and OFF corresponds to 0.

On input, an <NRf> is rounded to an integer. A nonzero result is interpreted as 1.

Queries always return a 1 or 0, never ON or OFF.

<character_data> Definition

Throughout this document <character_data> is used to represent character data, that is, A - Z, a - z, 0 - 9 and _ (underscore). For example:

START and R6_5F. The format is defined as:

<upper-case

alpha>

<upper-case

alpha>

<digit>

Figure 1-11 Format of <character_data>



<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. For examples, #HA2F, #ha4e, #Q62, #q15, #B01011.



76

H/h

A/a

B/b

C/c

D/d

E/e

F/f

<digit>

# Q/q 3

2

4

5

6

7

0

1

B/b

0

1

Figure 1-12 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.

<NR1> Definition

Throughout this document <NR1> numeric response data is defined as :

+ digit

Figure 1-13 Format of <NR1>

For example:

• 146

• +146

• –12345

Refer to section 8.7.2 of IEEE 488.2 for further details.


Throughout this document <NR2> numeric response data is defined as:

+ digit digit


For example:

• 12.3

• +1.2345

• –0.123





Throughout this document <NR3> numeric response data is defined as:

+ digit digit

+

E digit


For example:

• 1.23E+6

• 123.4E- 54

• –1234.567E+90


<numeric_value> Definition

Throughout this document the decimal numeric element is abbreviated to

<numeric_value> . For example, <NRf>, MINimum, MAXimum, DEFault or

Not A Number (NAN).

<string> Definition

Throughout this document <string> is used to represent 7- bit ASCII characters.



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-16 Format of <string>

Input Message Terminators

Program messages sent to a SCPI instrument must terminate with a

<newline> character. The IEEE.488 EOI (end or identify) signal is interpreted as a <newline> character and may also be used to terminate a message in place of the <newline> character. A <carriage return> followed by a <newline> is also accepted. Many programming languages allow you


1 Power Meter Remote Operation to specify a message terminator character or EOI state to be automatically sent with each bus transaction. Message termination always sets the current path back to the root- level.



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.

The following commands are device- specific to the power meter. They are not included in the 1999.0 version of the SCPI standard. However, these commands are designed with the SCPI format in mind and they follow all of the syntax rules of the standard.

CALibration[1|2]:RCALibration

CALibration[1|2]:RCFactor

DISPlay[:WINDow[1|2]]:FORMat

DISPlay[:WINDow[1|2]]:METer:LOWer

DISPlay[:WINDow[1|2]]:METer:UPPer

DISPlay[:WINDow[1|2]]:RESolution

DISPlay[:WINDow[1|2]]:SELect

MEMory:CLEar[:NAME]

MEMory:TABLe:SELect

MEMory:STATe:DEFine

MEMory:TABLe:GAIN[:MAGNitude]

MEMory:TABLe:GAIN:POINts?

MEMory:TABLe:MOVE

[SENSe[1]]|SENSe2:AVERage:SDETect

[SENSe[1]]|SENSe2:CORRection:CFACtor

[SENSe[1]]|SENSe2:CORRection:DCYCle

[SENSe[1]]|SENSe2:CORRection:FDOFfset

[SENSe[1]]|SENSe2:SPEed

[SENSe[1]]|SENSe2:POWer:AC:RANGe

SERVice:SENSor[1|2]:CDATE?

SERVice:SENSor[1|2]:CPLace?

SERVice:SENSor[1|2]:SNUMber?

SERVice:SENSor[1|2]:TYPE?

SYSTem:COMMunicate:LAN:AIP







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



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.

N O T E

This Guide details the commands available for both the N1911A and the N1912A power meters. As the N1911A is a single channel power meter only Channel A can be selected.

Where instances of channel selection are detailed in this document they are only relevant for the N1912A.

In different subsystems the numeric suffix of program mnemonics can represent either a channel selection or a window selection. Refer to the appropriate command description to verify the meaning of the numeric suffix.

With commands that require you to specify a channel, Channel A is represented by a 1 and Channel B by a 2. If you omit the channel number,

Channel A is assumed.

With commands that require you to specify a window, the upper window is represented by a 1 and the lower window by a 2. If you omit the window number, the upper window is assumed.

All the commands listed also have queries unless otherwise stated in the

“Notes” column.



Making Measurements on Wireless Communication Standards

The following sections describe typical measurements you may want to make. They are also described, for 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> command and use one of the following values.

• GSM900 - See

“GSM900” on page 533

for greater detail.

• EDGE - See

“EDGE” on page 536 for greater detail.

• CDMAone - See

“CDMAone” on page 540 for greater detail.

• CDMA2000 - See

“CDMA2000” on page 544 for greater detail.

• WCDMA - See

“W- CDMA” on page 548 for greater detail.

• BLUetooth - See

“BLUetooth” on page 552 for greater detail.

• MCPa - See

“MCPA” on page 555 for greater detail.

• RADar - See

“RADAR” on page 558 for greater detail.

• WL802DOT11A - See

“802.11a and HiperLan2” on page 562 for greater

detail.

• WL802DOT11B - See

“892.11b/g” on page 565 for greater detail.

• XEVDO - See

“1xeV- DO” on page 568 for greater detail.

• XEVDV - See

“1xeV- DV” on page 571 for greater detail.

• TDSCdma - See

“TD- SCDMA” on page 574 for greater detail.

• NADC - See

“NADC” on page 577 for greater detail.

• IDEN - See

“iDEN” on page 581 for greater detail.

• DVB - See

“DVB” on page 585 for greater detail.

• HIPERLAN2 - See

“802.11a and HiperLan2” on page 562 for greater

detail.



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:E9321A|E9322A|E9323A|E9325A|E9326A|E9327A|

!N1921A|N1922A The GSM setup is only valid with these !sensors

50 SYSTem:PRESet “GSM900”







2


MEASurement Commands 89

CONFigure[1] |2|3|4?

94

CONFigure [1] |2|3|4 Commands 97

CONFigure[1]|2|3|4[:SCALar][:POWer:AC]


CONFigure[1]|2|3|4[:SCALar][:POWer:AC]:RELative


CONFigure[1]|2|3|4[:SCALar][:POWer:AC]:DIFFerence


CONFigure[1]|2|3|4[:SCALar][:POWer:AC]:DIFFerence: RELative


CONFigure[1]|2|3|4[:SCALar][:POWer:AC]:RATio


CONFigure[1]|2|3|4[:SCALar][:POWer:AC]:RATio:

RELative[<expected_value>[,<resolution>[,<source list>]]] 108

FETCh[1]|2|3|4 Queries 110

FETCh[1]|2|3|4[:SCALar][:POWer:AC]?


FETCh[1]|2|3|4[:SCALar][:POWer:AC]:RELative?


FETCh[1]|2|3|4[:SCALar][:POWer:AC]:DIFFerence?


FETCh[1]|2|3|4[:SCALar][:POWer:AC]:DIFFerence: RELative?


FETCh[1]|2|3|4[:SCALar][:POWer:AC]:RATio?


FETCh[1]|2|3|4[:SCALar][:POWer:AC]:RATio:RELative?


READ[1]|2|3|4 Commands 128


87

2 MEASurement Commands

READ[1]|2|3|4[:SCALar][:POWer:AC]?


READ[1]|2|3|4[:SCALar][:POWer:AC]:RELative?


READ[1]|2|3|4[:SCALar][:POWer:AC]:DIFFerence?


READ[1]|2|3|4[:SCALar][:POWer:AC]:DIFFerence: RELative?


READ[1]|2|3|4[:SCALar][:POWer:AC]:RATio?


READ[1]|2|3|4[:SCALar][:POWer:AC]:RATio:RELative?


MEASure[1]|2|3|4 Commands 147

MEASure[1]|2|3|4[:SCALar][:POWer:AC]?


MEASure[1]|2|3|4[:SCALar][:POWer:AC]:RELative?


MEASure[1]|2|3|4[:SCALar][:POWer:AC]:DIFFerence?


MEASure[1]|2|3|4[:SCALar][:POWer:AC]:DIFFerence: RELative?


MEASure[1]|2|3|4[:SCALar][:POWer:AC]:RATio?


MEASure[1]|2|3|4[:SCALar][:POWer:AC]:RATio:RELative?


This chapter explains how to use the MEASure group of instructions to acquire data using a set of high level instructions.


MEASurement Commands 2


Measurement commands are high level commands used to acquire data.

They enable you to trade interchangeability against fine control of the measurement process.

Measurement

Command

Descriptions

MEASure?

CONFigure

READ?

FETCh?

Provides the simplest way to program a power meter for measurements.

MEASure?

is a compound command which is equivalent to an ABORT followed by a CONFigure and a READ?. It does not enable much flexibility or control over measurement settings.

Used to change the power meter’s configuration values. CONFigure must then be followed by another command which takes the measurement—for example, a READ? followed by a FETCh?.

Takes a measurement using parameters previously set up using either

CONFigure or lower level commands. READ? is equivalent to an ABORt followed by an INITiate1 (which performs the data acquisition) and a

FETCh?

Retrieves measurements taken by INITiate

*

.

* INITiate is described in

Chapter 14 , “TRIGger Subsystem,” on page 643.

The CONFigure, FETCh?, READ? and MEASure? commands all have a numeric suffix which refers to a specific window/measurement.

Figure 2- 17

shown an example of the configuration returned result windows.



CONfigure1?

upper window/upper measurement

CONFigure3?

upper window/lower measurement

CONFigure2?

lower window/upper measurement

CONFigure4?

lower window/lower measurement

Figure 2-17 Measurement Display CALCulate Block Window

Optional Parameters

CONFigure , FETCh?, READ? and MEASure? have the following three optional parameters:

• An expected power value

• A resolution

• A source list

Expected Power Value

An <expected_value> parameter is only required if you are using an

E- Series power sensor or N8480 Series power sensor (excluding Option

CFT). It has no effect on P- Series power sensor, 8480 Series power sensor or N8480 Series power sensor with Option CFT. The value entered determines which of the power sensor’s two ranges is used for the measurement. If the current setting of the power sensor’s range is no longer valid for the new measurement, specifying the expected power value decreases the time taken to obtain a result.



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> parameter settings for these windows are different, the highest resolution setting is taken to calculate the averaging. If you are making a ratio or difference measurement the <resolution> parameters are applied to both channels.

Source List

The <source list> parameter is used to define:

• What channels the measurements will be made on, for a dual channel measurement.

• Whether the calculation is A- B or B- A, for a dual channel difference measurement.

• Whether the calculation is A/B or B/A, for a ratio measurement.

Entering a <source list> is only required if you are using an N1912A.

As the N1911A has a single channel only, the source list can only be

Channel A.

The following commands are described in this chapter:

Notes

[query only]

Page

page 94

Keyword

CONFigure[1]|2|3|4?

CONFigure[1]|2|3|4

[:SCALar]

[:POWer:AC]

Parameter Form

:RELative

:DIFFerence

:RELative

[<expected_value>

[,<resolution>[,<source list>]]]

[<expected_value>


[<expected_value>


[<expected_value>


[no query]

[no query]

[non-SCPI]

[no query]

[non-SCPI]

[no query]

[non-SCPI]

page 98

page 100

page 102

page 104



92

Keyword

:RATio

:RELative

Parameter Form

[<expected_value>


[<expected_value>


Notes

[no query]

[no query]

[non-SCPI]

FETCh[1]|2|3|4

[:SCALar]

[:POWer:AC]?

:RELative?

[<expected_value>


[<expected_value>


:DIFFerence?

[<expected_value>


:RELative?

[<expected_value>


:RATio?

[<expected_value>


:RELative?

[<expected_value>


[query only]

[query only]

[non-SCPI]

[query only]

[non-SCPI]

[query only]

[non-SCPI]

[query only]

[query only]

[non-SCPI]

READ[1]|2|3|4

[:SCALar]

[:POWer:AC]?

:RELative?

[<expected_value>


[<expected_value>


:DIFFerence?

[<expected_value>


:RELative?

[<expected_value>


:RATio?

[<expected_value>


[query only]

[query only]

[non-SCPI]

[query only]

[non-SCPI]

[query only]

[non-SCPI]

[query only]

Page

page 106

page 108

page 111

page 113

page 116

page 119

page 122

page 125

page 129

page 132

page 135

page 138

page 141



Keyword Parameter Form

:RELative?

[<expected_value>


MEASure[1]|2|3|4

[:SCALar]

[:POWer:AC]?

:RELative?

[<expected_value>


[<expected_value>


:DIFFerence?

[<expected_value>


:RELative?

[<expected_value>


:RATio?

[<expected_value>


:RELative?

[<expected_value>


Notes

[query only]

[non-SCPI]

[query only]

[query only]

[non-SCPI]

[query only]

[non-SCPI]

[query only]

[non-SCPI]

[query only]

[query only]

[non-SCPI]

Page

page 144

page 148

page 150

page 152

page 154

page 156

page 158



CONFigure[1] |2|3|4?

This query returns the present configuration of the specified window/measurement.

Syntax

CONF 1

2

3

4

?

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> <expected_value>,<resolution>,<source list>”

CALCulate:MATH

(SENSe1)

(SENSe2)

*

(SENSe1)

(SENSe2)

*

(SENSe1 - SENSe2)

*

(SENSe2 - SENSe1)

*

(SENSe1 - SENSe2)

*

(SENSe2 - SENSe1)

*

(SENSe1 - SENSe1)

(SENSe2 - SENSe2)

*

(SENSe1 - SENSe1)

ON

OFF

OFF

ON

CALCulate:RE

Lative:

STATe

OFF

OFF

ON

ON

OFF

OFF

ON

Function <source list>

:POW:AC (@1)

:POW:AC (@2)

:POW:AC:REL

:POW:AC:REL

(@1)

(@2)

:POW:AC:DIFF (@1),(@2)

:POW:AC:DIFF (@2),(@1)

:POW:AC:DIFF:REL (@1),(@2)

:POW:AC:DIFF:REL

:POW:AC:DIFF

:POW:AC:DIFF

:POW:AC:DIFF:REL

(@2),(@1)

(@1),(@1)

(@2),(@2)

(@1),(@1)



CALCulate:MATH

(SENSe2 - SENSe2)

*

(SENSe2 / SENSe1)

*

(SENSe2 / SENSe1)

*

(SENSe1 / SENSe2)

*

(SENSe2 / SENSe1)

*

(SENSe1/SENSe1)

(SENSe2/SENSe2)

*

(SENSe1/SENSe1)

(SENSe2/SENSe2)

*

OFF

OFF

ON

ON

CALCulate:RE

Lative:

STATe

ON

OFF

OFF

ON

ON

Function <source list>

:POW:AC:DIFF:REL (@2),(@2)

:POW:AC:RAT (@1),(@2)

:POW:AC:RAT (@2),(@1)

:POW:AC:RAT:REL (@1),(@2)

:POW:AC:RAT:REL (@2),(@1)

POW:AC:RAT

POW:AC:RAT

POW:AC:RAT:REL

POW:AC:RAT:REL

(@1),(@1)

(@2),(@2)

(@1),(@1)

(@2),(@2)

* N1912A only.

<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.

The <resolution> returned is the same as the value returned by

DISPlay:WINDow:RESolution?

. The format of the return is <NR1> in the range 1 through 4.

Example

CONF2?

This command queries the current configuration of the lower window/upper measurement.

Reset Condition

On reset:

The command function is set to :POWer:AC.



The expected power level is set to +20 dBm.

The resolution is set to 3.

The source list on the N1911A is set to Channel A on both windows and their measurements.

The source list on the N1912A is set to Channel A for the upper measurement on both windows and Channel B for the lower measurement on both windows.



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. Use READ?, or alternatively use INITiate followed by a FETCh? to make the measurement.

The CONFigure command also applies the following defaults to the channel(s) which are in the specified window (the channel(s) in the window are specified in the <source list> parameter):

Default Settings

INITiate:CONTinuous OFF

TRIGger:SOURce IMMediate

TRIGger:DELay:AUTO ON

SENSE:AVERage:COUNt:AUTO ON

SENSE:AVERage:STATe ON

Description

Sets the power meter to make one trigger cycle when INITiate is sent.

When TRIG:SOUR is set to BUS or HOLD, sets the power meter to make the measurement immediately a trigger is received.

Enables automatic delay before making the measurement.

Enables automatic filter length selection.

Enables averaging.



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.

CONF

2

3

4

1

Syntax

:SCAL

Space

:POW :AC expected_value

DEF

, resolution

DEF

, source list

98

Parameters

Refer to “Optional Parameters” on page 90 for additional details on the

parameters in this command.

Item expected_value resolution

Description/Default

A numeric value for the expected power level. The units of measurement are dBm and W. The default units are defined by

UNIT:POWer .

A numeric value for the resolution. If unspecified the current resolution setting is used.

Range of Values

Sensor dependent.

DEF

1

1 to 4

2

1.0, 0.1, 0.01, 0.001

DEF

1



Item source list


The channel which the command is implemented on.

If unspecified the current window setup is used. However, on the N1912A, if the window shows a ratio or difference measurement, the upper window defaults to

Channel A and the lower window to Channel

B.

Range of Values

(@1)

(@2)

3

1

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.

2

When the measurement result is linear this parameter represents the number of significant digits. When the measurement result is logarithmic 1 to 4 represents of 1, 0.1, 0.01 and 0.001 respectively.

3

N1912A only.

Example

CONF1:POW:AC DEF,2,(@1) This command configures the upper window/upper measurement to measure the power of Channel A, using the current sensor range and a resolution setting of 2.



CONFigure[1]|2|3|4[:SCALar][:POWer:AC]:RELative


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.

CONF 1

2

3

4

Syntax

:SCAL

Space


DEF

:REL

, resolution

DEF

, source list

Parameters



Item expected_value

(for the expected power level) resolution


A numeric value for the expected power level. The units of measurement are dBm and W. The default units are defined by

UNIT:POWer .


Range of Values sensor dependent

DEF

1

1 to 4

2

1.0, 0.1, 0.01, 0.001

DEF

1



Item source list



If unspecified the current window setup is used. However, on the N1912A, if the window shows a ratio or difference measurement, the upper window defaults to Channel A and the lower window to Channel B.

Range of Values

(@1)

(@2)

3

1



2


3

N1912A only.

Example

CONF2:REL -50DBM,3,(@1) This command configures the lower window/upper measurement to measure the relative power of Channel A, using an expected power level of –50 dBm and a resolution setting of 3.



CONFigure[1]|2|3|4[:SCALar][:POWer:AC]:DIFFerence


This command sets the measurement function and resolution of the specified window. It sets the measurement function to difference with relative mode off.

CONF

2

3

4

1

Syntax

:SCAL

Space


DEF

:DIFF

, resolution

DEF

, source list

Parameters



Item expected_value



The power meter ignores the numeric value entered in this parameter. Any value entered is treated like DEF.



DEF

1

1 to 4

2

1.0, 0.1, 0.01, 0.001

DEF

1



Item source list


This channel list specifies between which channels the difference is calculated.

If unspecified and the current window setup is a difference measurement then this difference setup is used, otherwise it defaults to Channel A-B (N1912A) or A-A

(N1911A).

Range of Values

(@1),(@2)

3

(@2),(@1)

3

(@1),(@1)

(@2),(@2)

3

1


DEF leaves teh parameter value unchanged.

2

When the measurement result is linear this parameter represents the number of significant digits. When the measurement result is logarithmic 1 to 4 represents a resolution of 1, 0.1, 0.01 and 0.001 respectively.

3

N1912A only.

Example

CONF2:DIFF DEF,1,(@2),(@1) This command configures the lower window/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.



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


CONF

1

2

3

4

Syntax

:SCAL

Space


DEF

:DIFF :REL

, resolution

DEF

, source list

Parameters



Item expected_value






DEF

1

1 to 4

2

1.0, 0.1, 0.01, 0.001

DEF

1



Item source list


This channel list specifies the channels used to calculate the difference.

If unspecified and the current window setup is a difference measurement then this difference setup is used, otherwise it defaults to Channel A-B (N1912A) or A-A

(N1911A).

Range of Values

(@1),(@2)

3

(@2),(@1)

3

(@1),(@1)

(@2),(@2)

3

1



2


3

N1912A only.

Example

CONF1:DIFF:REL DEF,1,(@1),

(@2)

This command configures the upper window/upper measurement to make a difference measurement of

Channel A - Channel B with relative mode on, using the current sensor range and a resolution of 1 on both channels.



CONFigure[1]|2|3|4[:SCALar][:POWer:AC]:RATio


This command sets the measurement function, range and resolution of the specified window. It sets the measurement function to ratio with relative mode off.

CONF 1

2

3

4

Syntax

:SCAL

Space


DEF

:RAT

, resolution

DEF

, source list

Parameters



Item expected_value






DEF

1

1 to 4

2

1.0, 0.1, 0.01, 0.001

DEF

1



Item source list


This channel list specifies the channels used to calculate the ratio. If unspecified and the current window setup is a ratio measurement then this ratio setup is used, otherwise it defaults to Channel

A/B (N1912A) or A/A (N1911A).

Range of Values

(@1),(@2)

3

(@2),(@1)

3

(@1),(@1)

(@2),(@2)

3

1



2


3

N1912A only.

Example

CONF1:RAT DEF,4,(@1),(@2) This command configures the upper window/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.



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


CONF

2

3

4

1

Syntax

:SCAL

Space


DEF

:RAT :REL

, resolution

DEF

, source list

Parameters



Item expected_value






DEF

1

1 to 4

2

1.0, 0.1, 0.01, 0.001

DEF

1



Item source list


This channel list specifies the channels used to calculate the ratio.

If unspecified and the current window setup is a ratio measurement then this ratio setup is used, otherwise it defaults to Channel A/B (N1912A) or A/A

(N1911A).

Range of Values

(@1),(@2)

3

(@2),(@1)

3

(@1),(@1)

(@2),(@2)

3

1



2


3

N1912A only.

Example

CONF1:RAT:REL

DEF,1,(@1),(@2)

This command configures the upper window/upper measurement to make a ratio measurement of Channel A over

Channel B with relative mode on, using the current sensor range and a resolution setting of 1 on both channels.



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. The format of the result is set by

FORM[:READ][:DATA]

. Refer to Chapter 6 , “FORMat Subsystem,” on page

249 for further information.

The query returns a measurement result when it is valid. The measurement result is invalid under the following conditions:

• When *RST is executed.

• Whenever a measurement is initiated.

• When any SENSe parameter, such as frequency, is changed.

If data is invalid, the FETCh? query is not completed until all data becomes valid. The exceptions to this are, if the power meter is in the idle state and the data is invalid, or the power meter has been reconfigured as defined above and no new measurement has been initiated. In such cases, the FETCh? routine generates the error –230, “Data corrupt or stale” and no result is returned. A common cause for this error is receiving a FETCh? after a *RST. If the expected value and resolution parameters are not the same as those that were used to collect the data, error –221, “Settings conflict” occurs.

N O T E

When TRIG:SOUR is INT1, INT2 or EXT and a new acquisition has been initiated (using the

INIT command for example), FETCH? waits until the trigger takes place before executing. If triger conditions are not satisfied - when the trigger level differs greatly from the signal level for example - this can give the impression that the power meter has hung.

To unlock the power meter and adjust trigger settings, an SDC (Selected Device Clear) GPIB

Command must be performed. This is equivalent to “EXECUTE CLEAR” in Agilent VEE.



FETCh[1]|2|3|4[:SCALar][:POWer:AC]?


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.

FETC

2

3

4

1

Syntax

:SCAL

Space


DEF

?

, resolution

DEF

, source list

Parameters



Item expected_value

(for the expected power level)


The expected power level parameter can be set to DEF or a numeric value. If a value is entered it should correspond to that set by

CONFigure otherwise an error occurs. The units of measurement are dBm and W. The default units are defined by UNIT:POWer.


DEF

1



112

Item resolution source list


A numeric value for the resolution. If it is unspecified the current resolution setting is used. If a value is entered it should correspond to the current resolution setting otherwise an error occurs.

The channel which the command is implemented on. If unspecified the current window setup is used. However, on the

N1912A, if the window shows a ratio or difference measurement, the upper window defaults to Channel A and the lower window to Channel B.

Range of Values

1 to 4

2

1.0, 0.1, 0.01, 0.001

DEF

1

(@1)

(@2) (N1912A only)

1



2


Example

FETC2:POW:AC?

This command queries the lower window/upper measurement result.

Error Messages

• If the last measurement is not valid error –230, “Data corrupt or stale” occurs. A measurement is valid after it has been initiated. It becomes invalid when either a reset occurs or any measurement parameter, for example frequency, is changed.

• If the expected_value and resolution parameters are not the same as the current expected value and resolution setting on the specified window, error –221, “Settings conflict” occurs.



FETCh[1]|2|3|4[:SCALar][:POWer:AC]:RELative?


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. The relative value used is that set by the


FETC 1

2

3

4

Syntax

:SCAL

Space


DEF

:REL ?

, resolution

DEF

, source list

Parameters



Item expected_value



The expected power level parameter can be set to DEF or a numeric value. If a value is entered it should correspond to that set by CONFigure otherwise an error occurs. The units of measurement are dBm and W. The default units are defined by UNIT:POWer.


DEF

1



114




The channel which the command is implemented on. If unspecified the current window setup is used. However, on the N1912A, if the window shows a ratio or difference measurement, the upper window defaults to Channel A and the lower window to Channel B.

Range of Values

1 to 4

2

1.0, 0.1, 0.01, 0.001

DEF

1

(@1)

(@2) (N1912A only)

1



2


Example

FETC1:REL? DEF,2,(@2) This command queries the upper window/upper measurement relative measurement of Channel B, using the current sensor range and a resolution setting of 2.

Error Messages

• If the last measurement is not valid error –230, “Data corrupt or stale” occurs. A measurement is valid after it has been initiated. It becomes invalid when either a reset occurs or any measurement parameter, for example frequency, is changed.



• If the expected_value and resolution parameters are not the same as the current expected value and resolution settings on the specified window, error –221, “Settings conflict” occurs.



FETCh[1]|2|3|4[:SCALar][:POWer:AC]:DIFFerence?


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.

FETC 1

2

3

4

Syntax

:SCAL

Space


DEF

:DIFF ?

, resolution

DEF

, source list

Parameters



Item expected_value


Description/Default Range of Values

The expected power level parameter can be set to

DEF or a numeric value. If a value is entered it should correspond to that set by CONFigure otherwise an error occurs.The units of measurement are dBm and W. The default units are defined by UNIT:POWer.

sensor dependent

DEF

1







If unspecified and the current window setup is a difference measurement then this difference setup is used, otherwise it defaults to Channel A-B

(N1912A) or A-A (N1911A).

1 to 4

2

1.0, 0.1, 0.01, 0.001

DEF

1

(@1),(@2)

3

(@2),(@1)

3

(@1),(@1)

(@2),(@2)

3

1



2


3

N1912A only.

Example

FETC2:DIFF?

This command queries the difference measurement on the lower window/lower measurement.

Error Messages

• If the last measurement on either channel is not valid error –230,

“Data corrupt or stale” occurs. A measurement is valid after it has been initiated. It becomes invalid when either a reset occurs or any measurement parameter, for example frequency, is changed.






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. The relative value used is that set by the


FETC

1

2

3

4

Syntax

:SCAL

Space


DEF

:DIFF :REL ?

, resolution

DEF

, source list

Parameters



Item expected_value




CONFigure otherwise an error occurs.The units of measurement are dBm and W. The default units are defined by UNIT:POWer.


DEF

1



120





If unspecified and the current window setup is a difference measurement then this difference setup is used, otherwise it defaults to Channel

A-B (N1912A) or A-A (N1911A).

1 to 4

2

1.0, 0.1, 0.01, 0.001

DEF

1

(@1),(@2)

3

(@2),(@1)

3

(@1),(@1)

(@2),(@2)

3

1



2


3

N1912A only.

Example

FETC1:DIFF:REL? DEF,3,(@2)

,(@1)

This command queries the upper window/upper measurement relative difference measurement of

Channel B - Channel A, using the current sensor range and a resolution setting of 3 on both channels.

Error Messages








FETCh[1]|2|3|4[:SCALar][:POWer:AC]:RATio?


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.

FETC 1

2

3

4

Syntax

:SCAL

Space


DEF

:RAT ?

, resolution

DEF

, source list

Parameters



Item expected_value



The expected power level parameter can be set to

DEF or a numeric value. If a value is entered it should correspond to that set by CONFigure otherwise an error occurs.The units of measurement are dBm and W. The default units are defined by UNIT:POWer.

sensor dependent

DEF

1







If unspecified and the current window setup is a ratio measurement then this ratio setup is used, otherwise it defaults to Channel A/B (N1912A) or

A/A (N1911A).

1 to 4

2

1.0, 0.1, 0.01, 0.001

DEF

1

(@1),(@2)

3

(@2),(@1)

3

(@1),(@1)

(@2),(@2)

3

1



2


3

N1912A only.



Example

FETC2:RAT? DEF,1,(@1),(@2) This command queries the lower window/upper measurement ratio measurement of Channel A over Channel B, using the current sensor range and a resolution of 1 on both channels.

Error Messages






FETCh[1]|2|3|4[:SCALar][:POWer:AC]:RATio:RELative?


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. The relative value used is that set by the


FETC

1

2

3

4

Syntax

:SCAL

Space


DEF

:RAT :REL ?

, resolution

DEF

, source list

Parameters



Item expected_value



The expected power level parameter can be set to DEF or a numeric value. If a value is entered it should correspond to that set by CONFigure otherwise an error occurs.The units of measurement are dBm and W. The default units are defined by UNIT:POWer.

sensor dependent

DEF

1



126





If unspecified and the current window setup is a ratio measurement then this ratio setup is used, otherwise it defaults to Channel A/B

(N1912A) or A/A (N1911A).

1 to 4

2

1.0, 0.1, 0.01, 0.001

DEF

1

(@1),(@2)

3

(@2),(@1)

3

(@1),(@1)

(@2),(@2)

3

1



2


3

N1912A only.

Example

FETC:RAT:REL?

This command queries the relative ratio measurement on the upper window/upper measurement.

Error Messages








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,” on page

249 for further information.

• For the N1911A the READ? query is equivalent to:

ABORt

INITiate

FETCh?

• For the N1912A carrying out a single channel measurement the READ? queries are equivalent to:

ABORt1

INITiate1

FETCh1?

or

ABORt2

INITiate2

FETCh2?

• For the N1912A carrying out a difference measurement the

READ:DIFFerence?

queries are equivalent to:

ABORt1 and

ABORt2

INITiate1

INITiate2

FETCh:DIFFerence?

• For the N1912A carrying out a ratio measurement the READ:RATio? queries are equivalent to:

ABORt1

ABORt2

INITiate1

INITiate2

FETCh:RATio?



READ[1]|2|3|4[:SCALar][:POWer:AC]?


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.

N O T E

INITiate:CONTinuous must be set to OFF, otherwise error –213, “INIT ignored” occurs. If TRIGger:SOURce is set to BUS, error –214, “Trigger deadlock” occurs.

READ 1

2

3

4

Syntax

:SCAL

Space


DEF

?

, resolution

DEF

, source list

Parameters


parameters in this command

.

Item expected_value




CONFigure otherwise an error occurs.


DEF

1



130





If unspecified the current window setup is used. However, on the N1912A, if the window shows a ratio or difference measurement, the upper window defaults to

Channel A and the lower window to Channel

B.

Range of Values

1 to 4

2

1.0, 0.1, 0.01, 0.001

DEF

1

(@1)

(@2) (N1912A only)

1



2


Example

READ2:POW:AC?

This command queries the lower window/upper measurement.

Error Messages

• INITiate:CONTinuous must be set to OFF, otherwise error –213, “INIT ignored” occurs.

• If TRIGger:SOURce is set to BUS or HOLD, error –214, “Trigger deadlock” occurs.



• If the expected value and resolution parameters are not the same as the current expected value and resolution settings on the specified window, error –221, “Settings conflict” occurs.



READ[1]|2|3|4[:SCALar][:POWer:AC]:RELative?


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. The relative value used is that set by the CALCulate:RELative:MAGNitude:AUTO command.

N O T E

INITiate:CONTinuous must be set to OFF, otherwise error –213, “INIT ignored” occurs. If TRIGger:SOURce is set to BUS, error –214, “Trigger deadlock” occurs.

READ 1

2

3

4

Syntax

:SCAL

Space


DEF

:REL ?

, resolution

DEF

, source list



Parameters



Item expected_value

(for the expected power level) resolution source list



CONFigure otherwise an error occurs.





DEF

1

1 to 4

2

1.0, 0.1, 0.01, 0.001

DEF

1

(@1)

(@2) (N1912A only)

1



2




Example

READ1:REL? DEF,1,(@2) This command queries the upper window/upper measurement relative measurement of Channel B, using the current sensor range and a resolution of

1.

Error Messages

• INITiate:CONTinuous must be set to OFF, otherwise error –213, “INIT ignored” occurs.

• If TRIGger:SOURce is set to BUS or HOLD, error –214, “Trigger deadlock” occurs.

• If the expected value and resolution parameters are not the same as the current expected value and resolution settings on the specified window, error –221, “Settings conflict” occurs.



READ[1]|2|3|4[:SCALar][:POWer:AC]:DIFFerence?


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.

N O T E

INITiate:CONTinuous must be set to OFF on both channels, otherwise error –213,

“INIT ignored” occurs. If TRIGger:SOURce is set to BUS on either channel, error –214,

“Trigger deadlock” occurs.

READ

1

2

3

4

Syntax

:SCAL

Space


DEF

:DIFF ?

, resolution

DEF

, source list

Parameters



Item expected_value





DEF

1



136



A numeric value for the resolution. If it is unspecified the current resolution setting is used.

If a value is entered it should correspond to the current resolution setting otherwise an error occurs.



A-B (N1912A) or A-A (N1911A).

Range of Values

1 to 4

2

1.0, 0.1, 0.01, 0.001

DEF

1

(@1),(@2)

3

(@2),(@1)

3

(@1),(@1)

(@2),(@2)

3

1



2


3

N1912A only.

Example

READ2:DIFF?

This command queries difference measurement on the lower window/upper measurement.

Error Messages

• INITiate:CONTinuous must be set to OFF on both channels, otherwise error –213, “INIT ignored” occurs.

• If TRIGger:SOURce is set to BUS or HOLD on either channel, error –214,




• If the resolution parameter is not the same as the current resolution setting on the specified window, error –221, “Settings conflict” occurs.



READ[1]|2|3|4[:SCALar][:POWer:AC]:DIFFerence:


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. The relative value used is that set by the


N O T E

IINITiate:CONTinuous must be set to OFF on both channels, otherwise error –213,



READ 1

2

3

4

Syntax

:SCAL

Space


DEF

:DIFF :REL ?

, resolution

DEF

, source list



Parameters



Item expected_value








A-B (N1912A) or A-A (N1911A).


DEF

1

1 to 4

2

1.0, 0.1, 0.01, 0.001

DEF

1

(@1),(@2)

3

(@2),(@1)

3

(@1),(@1)

(@2),(@2)

3

1



2


3

N1912A only.



Example

READ1:DIFF:REL? DEF,4,(@2),(@1) This command queries the upper window/upper measurement relative difference measurement of


Error Messages


• If TRIGger:SOURce is set to BUS or HOLD on either channel, error

–214, “Trigger deadlock” occurs.




READ[1]|2|3|4[:SCALar][:POWer:AC]:RATio?


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.

N O T E

INITiate:CON Tinuous must be set to OFF on both channels, otherwise error –213, “INIT ignored” occurs. If TRIGger:SOURce is set to BUS on either channel, error –214, “Trigger deadlock” occurs.

READ 1

2

3

4

Syntax

:SCAL

Space


DEF

:RAT ?

, resolution

DEF

, source list

Parameters



Item expected_value





DEF

1



142







A/A (N1911A).

Range of Values

1 to 4

2

1.0, 0.1, 0.01, 0.001

DEF

1

(@1),(@2)

3

(@2),(@1)

3

(@1),(@1)

(@2),(@2)

3

1



2


3

N1912A only.

Example

READ2:RAT? DEF,1,(@1),(@2) This command queries the lower window/upper measurement ratio measurement of Channel A over

Channel B, using the current sensor range and a resolution of 1 on both channels.

Error Messages









READ[1]|2|3|4[:SCALar][:POWer:AC]:RATio:RELative?


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. The result is a ratio based measurement and is expressed in the units defined by UNIT[1]|2|3|4:POWer:RATio. The relative value used is that set by the


N O T E

IINITiate:CONTinuous must be set to OFF on both channels, otherwise error –213,



READ 1

2

3

4

Syntax

:SCAL

Space


DEF

:RAT :REL ?

, resolution

DEF

, source list



Parameters



Item expected_value








A/A (N1911A).


DEF

1

1 to 4

2

1.0, 0.1, 0.01, 0.001

DEF

1

(@1),(@2)

3

(@2),(@1)

3

(@1),(@1)

(@2),(@2)

3

1



2


3

N1912A only.



Example

READ:RAT:REL?


Error Messages







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,” on page 249 for further information.

MEASure?

is a compound command which is equivalent to:

• For the N1911A the MEASure? query is equivalent to:

ABORt

CONFigure

READ?

• For the N1912A carrying out a single channel measurement the

MEASure?


ABORt1

CONFigure

READ1?

or

ABORt2

CONFigure

READ2?

• For the N1912A carrying out a difference measurement the

READ:DIFFerence?


ABORt1

ABORt2

CONFigure:DIFFerence

READ:DIFFerence?

• For the N1912A carrying out a ratio measurement the READ:RATio? queries are equivalent to:

ABORt1

ABORt2

CONFigure:RATio

READ:RATio?



MEASure[1]|2|3|4[:SCALar][:POWer:AC]?


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.

MEAS 1

2

3

4

Syntax

:SCAL

Space


DEF

?

, resolution

DEF

, source list

148

Parameters



Item expected_value



A numeric value for the expected power level.

The units of measurement are dBm and W.

The default units are defined by

UNIT:POWer .



DEF

1

1 to 4

2

1.0, 0.1, 0.01, 0.001

DEF

1



Item source list




Range of Values

(@1)

(@2) (N1912A only)

1



2


Example

MEAS2:POW:AC?

-70DBM,1,(@1)

This command queries the lower window/upper measurement of

Channel A, using an expected power level of - 70 dBm and a resolution setting of 1.



MEASure[1]|2|3|4[:SCALar][:POWer:AC]:RELative?


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. The relative value used is that set by the CALCulate:RELative:MAGNitude:AUTO command.

MEAS 1

2

3

4

Syntax

:SCAL

Space


DEF

:REL ?

, resolution

DEF

, source list

150

Parameters



Item expected_value



A numeric value for the expected power level.

The units of measurement are dBm and W. The default units are defined by UNIT:POWer.



DEF

1

1 to 4

2

1.0, 0.1, 0.01, 0.001

DEF

1



Item source list



If unspecified the current window setup is used.

However, on the N1912A, if the window shows a ratio or difference measurement, the upper window defaults to Channel A and the lower window to Channel B.

Range of Values

(@1)

(@2) (N1912A only)

1



2


Example

MEAS1:REL? -50DBM,2,(@2) This command queries the upper window/upper measurement relative measurement of Channel B, using an expected power level of –50 dBm and a resolution setting of 2.



MEASure[1]|2|3|4[:SCALar][:POWer:AC]:DIFFerence?


This command applies to the N1912A power meter only, as it needs two measurement channels to make sense.

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.

MEAS

1

2

3

4

Syntax

:SCAL

Space


DEF

:DIFF ?

, resolution

DEF

, source list

152

Parameters



Item expected_value





DEF

1








A-B (N1912A) or A-A (N1911A).

Range of Values

1 to 4

2

1.0, 0.1, 0.01, 0.001

DEF

1

(@1),(@2)

3

(@2),(@1)

3

(@1),(@1)

(@2),(@2)

3

1



2


3

N1912A only.

Example

MEAS2:DIFF?

This command queries the difference measurement on the lower window/upper measurement.



MEASure[1]|2|3|4[:SCALar][:POWer:AC]:DIFFerence:


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. The relative value used is that set by the


MEAS 1

2

3

4

Syntax

:SCAL

Space


DEF

:DIFF :REL ?

, resolution

DEF

, source list

154

Parameters



Item expected_value






DEF

1

1 to 4

2

1.0, 0.1, 0.01, 0.001

DEF

1



Item source list




A-B (N1912A) or A-A (N1911A).

Range of Values

(@1),(@2)

3

(@2),(@1)

3

(@1),(@1)

(@2),(@2)

3

1



2


3

N1912A only.

Example

MEAS1:DIFF:REL? DEF,3,(@2)

,(@1)

This command queries the upper window/upper measurement relative difference measurement of




MEASure[1]|2|3|4[:SCALar][:POWer:AC]:RATio?


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.

MEAS 1

2

3

4

Syntax

:SCAL

Space


DEF

:RAT ?

, resolution

DEF

, source list

156

Parameters


parameters in this command

.

Item expected_value






DEF

1

1 to 4

2

1.0, 0.1, 0.01, 0.001

DEF

1



Item source list



If unspecified and the current window setup is a ratio measurement then this ratio setup is used, otherwise it defaults to Channel A/B

(N1912A) or A/A (N1911A).

Range of Values

(@1),(@2)

3

(@2),(@1)

3

(@1),(@1)

(@2),(@2)

3

1



2


3

N1912A only.

Example

MEAS2:RAT? DEF,1,(@1),(@2) This command queries the lower window/upper measurement ratio measurement of Channel A over

Channel B, using the current sensor range and a resolution of 1 on both channels.



MEASure[1]|2|3|4[:SCALar][:POWer:AC]:RATio:RELative?


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. The relative value used is that set by the CALCulate:RELative:MAGNitude:AUTO command.

MEAS 1

2

3

4

Syntax

:SCAL

Space


DEF

:RAT :REL ?

, resolution

DEF

, source list

158

Parameters



Item expected_value






DEF

1

1 to 4

2

1.0, 0.1, 0.01, 0.001

DEF

1



Item source list



If unspecified and the current window setup is a ratio measurement then this ratio setup is used, otherwise it defaults to Channel A/B (N1912A) or A/A (N1911A).

Range of Values

(@1),(@2)

3

(@2),(@1)

3

(@1),(@1)

(@2),(@2)

3

1



2


3

N1912A only.

Example

MEAS:RAT:REL?








3


CALCulate Subsystem 162

CALCulate[1]|2|3|4:FEED[1]|2 <string> 165

CALCulate[1]|2|3|4:GAIN Commands 168

CALCulate[1]|2|3|4:GAIN[:MAGNitude] <numeric_value> 169

CALCulate[1]|2|3|4:GAIN:STATe <boolean> 171

CALCulate[1]|2|3|4:LIMit Commands 173

CALCulate[1]|2|3|4:LIMit:CLEar:AUTo <boolean>|ONCE 174

CALCulate[1]|2|3|4:LIMit:CLEar[:IMMediate] 176


177


178

CALCulate[1]|2|3|4:LIMit:LOWer[:DATA] <numeric_value> 180

CALCulate[1]|2|3|4:LIMit:UPPer[:DATA] <numeric_value> 183

CALCulate[1]|2|3|4:LIMit:STATe <boolean> 186

CALCulate[1]|2|3|4:MATH Commands 188

CALCulate[1]|2|3|4:MATH[:EXPRession] <string> 189


192

CALCulate[1]|2|3|4:PHOLd:CLEar 193

CALCulate[1]|2|3|4:RELative Commands 194

CALCulate[1]|2|3|4:RELative[:MAGNitude]:AUTO

<boolean>|ONCE 195

CALCulate[1]|2|3|4:RELative:STATe <boolean> 197

This chapter explains how the CALCulate subsystem is used to perform post acquisition data processing.


161

3 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- 18 . The numeric suffix of the

CALCulate command determines which CALCulate block is used and where the measurement result is displayed.

CALC1 upper window/upper measurement

CALC3 upper window/lower measurement

CALC2 lower window/upper measurement

CALC4 lower window/lower measurement

Figure 3-18 Measurement Display CALCulate Block Window

Data from both SENSe blocks may feed any or all of the CALCulate blocks via the MATH command. Figure 3- 18 details where the commands are applied with in the CALCulate block.


CALCulate Subsystem 3

Peak or Avg

SENSe1:

Input from

SENSe1 block

Peak or Avg

SENSe2

:

Input from

SENSe2 block

(N1912A only)

Figure 3-19 CALCulate Block

CALCulate Block

:FEED

A

FEED1

FEED2

:MATH

B

“A” | “B”

“A-A” | “A/A”

“B-B” | “B/B”

“A-B” | “A/B”

“B-A” | “B/A”

:GAIN

:REL



Keyword

CALCulate[1]|2|3|4

:FEED[1]|2

:GAIN

[:MAGNitude]

:STATe

:LIMit

:CLEar

:AUTO

[:IMMediate]

:FAIL?

:FCOunt?

:LOWer

[:DATA]

:UPPer

[:DATA]

:MATH

:STATe

[:EXPRession]

:CATalog?

:PHOLd

:CLEar

:RELative

[:MAGNitude]

:AUTO

:STATe

Parameter Form

<data_handle>

<numeric_value>

<boolean>

<boolean>|ONCE

[query only]

[query only]

<numeric_value>

<numeric_value>

<boolean>

<string>

[query only]

[no query]

<boolean>|ONCE

<boolean>

Notes Page

page 165

page 169

page 171

page 174

page 176

page 177

page 178

page 180

page 183

page 186

page 189

page 192

page 193

page 195

page 197



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). For example, if one feed is changed to

PTAV , the other is automatically changed to PTAV.

Under certain circumstances the measurement mode is changed by the

CALC:MATH:EXPR command. Refer to

“CALCulate[1]|2|3|4:MATH[:EXPRession] <string>” on page 189 for further

information.

Syntax

CALC 1

2

3

4

:FEED 1

2

Space string

?



Parameters

Item string

Description

The input measurement type to be fed to the specific input on the CALC block:

• PEAK : peak power

• PTAV : peak to average

• AVER : average

• MIN : minimum power

Values may be followed by ON SWEEP[1]|2|3|4 where the numeric specifies the gate to be used for the feed. For example: “POW:PEAK ON SWEEP2”.

If ON SWEEP[1]|2|3|4 is not supplied, the gate used is left unchanged.

A feed of “” (empty string) disables the CALC block and switches off that display line.

Range of Values

“POW:PEAK”

“POW:PTAV”

“POW:AVER”

“POW:MIN”

Example

CALC3:FEED2 “POW:AVER ON

SWEEP2”

This command selects the input for FEED2 of CALC block CALC3 to be average power, using gate 2. The channel from which the feed is taken is determined by

CALC:MATH:EXPR ..

Reset Condition

On reset, data_handle is set to :POW:AVER .


Query

CALCulate[1]|2|3|4:FEED[1]2?

The query returns the current value of the string.


Query Example

CALC1:FEED2?

This command queries the current setting of 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” occurs.

• If <string> contains ON SWEEP[1]|2|3|4 and the feed’s TRIG:SOUR is not INT or EXT (for single channel power meters) or INT1, INT2 or EXT

(for dual channel power meters), error –221 “Settings conflict” occurs.

• If the command changes the measurement mode to PEAK or PTAV when a sensor other than a P- Series or E9320 power sensor is connected or a P- Series or E9320 Sensor is connected and set to AVERage mode rather than NORMal mode, error –221, “Settings Conflict” occurs.



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>

CALCulate[1]|2|3|4:GAIN:STATe <boolean>



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.

Syntax

CALC 1

2

3

4

:GAIN :MAGN Space

?

numeric_value

DEF

MIN

MAX

Space MIN

MAX

Parameters

Item numeric_value


A numeric value for the display offset:

• DEF : the default value is 0 dB

• MIN : –100.000 dB

• MAX : +100.000 dB

Range of Values

–100.000 to +100.000 dB

DEF

MIN

MAX



Example

CALC2:GAIN 20 This command enters a display offset of

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.

Query Example

CALC1:GAIN?

This command queries the current setting of the display offset on the upper window/upper measurement.

Error Message

If CALCulate[1]|2|3|4:GAIN[:MAGNitude] is set to ON while

SENSe:SPEed is set to 200, error –221, “Settings Conflict” occurs.



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

CALC 1

2

3

4

:GAIN :STAT Space

?

0|OFF

1|ON

Example

CALC2:GAIN:STAT 1 This command enables the display offset for the lower window/ upper measurement.

Reset Condition

On reset, the gain is disabled.

Query

CALCulate[1]|2|3|4:GAIN:STATe?

The query enters a 1 or 0 into the output buffer indicating the status of the display offset.

• 1 is returned when the display offset feature is enabled



• 0 is returned when the display offset feature is disabled

Query Example

CALC1:GAIN:STAT?

This command queries whether the display 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.



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

• Clear the counter


CALCulate[1]|2|3|4:LIMit:CLEar:AUTo <boolean>

CALCulate[1]|2|3|4:LIMit:CLEar[IMMediate]



CALCulate[1]|2|3|4:LIMit:LOWer[:DATA]

CALCulate[1]|2|3|4:LIMit:UPPer[:DATA]

CALCulate[1]|2|3|4:LIMit:STATe <boolean>



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


query.

• If ON is specified, the FCO is set to 0 each time a measurement is:

• Initiated using INITiate[:IMMediate]

• Initiated using INITiate:CONTinuous ON

• Measured using MEASure?

• Read using READ?

• If OFF is specified, the FCO is not cleared by the above commands.

• If ONCE is specified, the FCO is cleared only after the first initialization then starts accumulating any limit failures.

Syntax

CALC 1

2

3

4

:LIM :CLE :AUTO Space 0|OFF

1|ON

ONCE

?



Example

CALC1:LIM:CLE:AUTO 1 This command switches on automatic 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.

• 1 is entered into the output buffer when limit failures are cleared automatically when a new measurement is initiated.

• 0 is entered into the output buffer when limit failures are not cleared automatically when a new measurement is initiated.

In the case where limit failures are cleared once, when a query occurs a 1 is entered into the output buffer if no measurement is initiated. If a measurement is initiated then 0 is entered.

Query Example

CALC1:LIM:CLE:AUTO?

This command queries when the FCO is cleared for the upper window/upper measurement.



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

CALC 1

2

3

4

:LIM :CLE :IMM

Example

CALC2:LIM:CLE:IMM This command clears the FCO for the lower window/upper measurement.



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 nonzero. The FCO (fail counter) can be zeroed using the CALC[1]|2|3|4:LIMit:CLEar command.

• 1 is returned when one or more limit failures have occurred

• 0 is returned when no limit failures have occurred

Syntax

CALC 1

2

3

4

:LIM :FAIL ?

Example

CALC1:LIM:FAIL?

This command queries if there have been any limit failures on the upper window/upper measurement.

Reset Condition

On reset, the buffer is set to zero for both upper and lower window measurements.



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.

If the measured value is equal to a limit, this is a limit pass.

The counter is reset to zero by any of the following commands:

• *RST

• CALCulate[1]|2|3|4:LIMit:CLEar:IMMediate

• CALCulate[1]|2|3|4:LIMit:CLEar:AUTO ON

When CALCulate[1]|2|3|4:LIMit:CLEar:AUTO is set to ON, the counter is set to zero each time a measurement is:

• measured using MEASure?

• read using READ?

• initiated using:

• INITiate[:IMMediate] or,

• INITiate:CONTinuous ON

When CALCulate[1]|2|3|4:LIMit:CLEar:AUTO is set to ONCE, the counter is set to zero the first time a measurement is:

• measured using MEASure?

• read using READ?

• initiated using:

• INITiate[:IMMediate] or,

• INITiate:CONTinuous ON

The maximum number of errors is 2

16

–1. If more than 2

16

–1 errors are detected the counter returns to zero.



Syntax

CALC 1

2

3

4

:LIM :FCO ?

Example

CALC1:LIM:FCO?

This command queries the number of limit 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.



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- 13 .

When the measured value is less than the value specified in

CALCulate[1]|2|3|4:LIMit:LOWer[:DATA] ,


reports a fail. When the measured value is greater than or equal to the limit, a fail is not reported.

Table 3-13 Measurement Units

Measurement Mode Measurement Type

Single Channel

Ratio

Difference

Avg, Pk

Pk–Avg

Avg, Pk, Pk–Avg

Avg, Pk

Pk–Avg

CALC:REL:STAT OFF

Linear

Watt

%

%

Watt

%

Log dBm dB dB dBm dB

CALC:REL:STAT ON

Linear

%

%

%

%

%

Log dB dB dB dB dB

CALC

Syntax

1

2

3

4

:LIM :LOW :DATA Space

?

numeric_value

DEF

MIN

MAX

Space MIN

MAX



Parameters

Item numeric_value


A numeric value for the lower test limit:

• DEF : the default is –90.00 dBm or

–90 db

• MIN : –150 dBm or –180 dB

• MAX : +230 dBm or +200 dB

Range of Values

–150 to +230 dBm or

–180 to +200 dB

DEF

MIN

MAX

Example

CALC2:LIM:LOW:DATA 0.1

This command enters a lower limit for the lower window/upper measurement depending on the window’s units as follows: dBm = 0.1 dBm

W = 100 mW dB = 0.1 dB

% = 0.1 %

Reset Condition

On reset, both measurements of the upper and lower windows are set to

–90.00 dBm or –90 dB (DEF).

Query

CALCulate[1]|2|3|4:LIMit:LOWer[:DATA]? [MIN|MAX]

The query returns the current setting of the lower limit or the values associated with MIN and MAX for the specified window.



Query Example

CALC2:LIM:LOW:DATA?

This command queries the lower limit set for the lower window upper measurement.



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- 14 .

When the measured power is greater than the value specified in

CALCulate[1]|2|3|4:LIMit:UPPer[:DATA] ,


reports a fail. When the measured level is less than or equal to the limit, a fail is not reported.



Single Channel

Ratio

Difference

Avg, Pk

Pk–Avg

Avg, Pk, Pk–Avg

Avg, Pk

Pk–Avg


Linear

Watt

%

%

Watt

%



Linear

%

%

%

%

%

Log dB dB dB dB dB

CALC

Syntax

1

2

3

4

:LIM :UPP :DATA Space

?

numeric_value

DEF

MIN

MAX

Space MIN

MAX



Parameters

Item numeric_value


A numeric value for the lower test limit:

• DEF : the default is –90.00 dBm or

–90 db

• MIN : –150 dBm or –180 dB

• MAX : +230 dBm or +200 dB

Range of Values

–150 to +230 dBm or

–180 to +200 dB

DEF

MIN

MAX

Example

CALC2:LIM:UPP:DATA 5 This command enters an upper limit for the lower window/upper measurement depending on the window’s units as follows: dBm = 5 dBm

W = 5 W dB = 5 dB

% = 5 %

Reset Condition

On reset, both channels are set to +90.00 dBm or +90 dB.

Query

CALCulate[1]|2|3|4:LIMit:UPPer[:DATA]? [MIN|MAX]



Query Example

CALC2:LIM:UPP:DATA?

This command queries the setting of the 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.



CALCulate[1]|2|3|4:LIMit:STATe <boolean>

This command enables/disables the test limits for the specified window.

Syntax

CALC 1

2

3

4

:LIM :STAT Space

?

0|OFF

1|ON

186

Example

CALC2:LIM:STAT 1 This command enables the limit checking 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 testing feature for the specified window/measurement.

• 1 is returned when limits testing is enabled

• 0 is returned when limits testing is disabled



Query Example

CALC1:LIM:STAT?

This command queries whether the limit 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.



CALCulate[1]|2|3|4:MATH Commands

These commands define and carry out the following mathematical transformations on SENSe data:

• Single channel

• Difference

• Ratio


CALCulate[1]|2|3|4:MATH[:EXPRession] <string>




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)”

3 CALC:FEED1 “POW:PEAK”

4 CALC:MATH “(SENS2)”

The FEED1 measurement mode, set in step 3, is made invalid by step 4 and automatically changed to “POW:AVER”

.

Syntax

CALC 1

2

3

4

:MATH :EXPR Space

?

string



Parameters

Item string


A single string value detailing the measurement type:

• For the Agilent N1911A the default is

SENS1 .

• For the Agilent N1912A the default is

SENS1 if the upper window is selected, or

SENS2 if the lower window is selected.

Range of Values

“(SENS1)”

1

“(SENS2)”

1,2

“(SENS1–SENS1)”

1,3


1,2,3

“(SENS1/SENS1)”

1

“(SENS2/SENS2)”

1,2


1,2,3


1,2,3

“(SENS1/SENS2)”

1,2

“(SENS2/SENS1)”

1,2

1

Quotes are mandatory. Either single or double quotes may be used.

2

N1912A only.

3

The mathematical operation will be performed in linear scale.

190

Example

CALC2:MATH “(SENS2/SENS1)” This command sets the lower window/upper measurement to make a

Channel B/A ratio measurement.

Reset Condition

On reset, the Agilent N1911A upper and lower window measurements are set to Channel A ("(SENS1)"). On the N1912A the upper window measurements are set to Channel A ("(SENS1)") and the lower window measurements to Channel B ("(SENS2)").



Query

CALCulate[1]|2|3|4:MATH[:EXPRession]?

The query returns the current math measurement setting on the specified window.

Query Example

CALC1:MATH?

This command queries the current setting of the math expression on the upper window/upper measurement.

Error Messages

• For the single channel N1911A power meter: if <string> is not set to

“(SENS1)” while SENSe:SPEed is set to 200, error –221, “Settings

Conflict” occurs.

• For the dual channel N1912A power meter: if <string> is not set to

“(SENS1)” or “(SENS2)” while SENS1:SPEEd or SENS2:SPEEd is set to

200, error –221, “Settings Conflict” occurs.



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.

•

For the N1911A the string is:

“(SENS1)”, “(SENS1–SENS1)”, “(SENS1/SENS1)”

•

For the N1912A the string is:

"(SENS1)","(SENS2)","(SENS1/SENS2)",

"(SENS2/SENS1)","(SENS1–SENS2)","(SENS2–SENS1)"

"(SENS1–SENS1)","(SENS2–SENS2)","(SENS1/SENS1)",

"(SENS2/SENS2)"

Syntax

CALC 1

2

3

4

:MATH :EXPR :CAT ?

Example

CALC1:MATH:CAT?

This command lists all the defined math expressions.



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.

N O T E

Clearing the peak hold value for a specified CALC block may affect the peak hold value of other CALC blocks, depending on the CALC channel set up (set by CALC:MATH:EXPR).

Syntax

CALC 1

2

3

4

:PHOL :CLE

Example

CALC2:PHOLd:CLEar This command clears the peak hold value for CALC2.

Error Messages

• If no power sensor is connected, error –241 “Hardware missing” occurs.

• If a sensor, other than an P- Series or E9320 power sensor, is connected, error –241 “Hardware missing” occurs.

• If SENS:DET:FUNC is set to AVER or TRIG:SOUR is set to INT1, INT2 or

EXT , error –221 “Settings conflict” occurs.



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>



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. Selecting ONCE sets the reference value to that of the measurement signal after any math calculations and display offsets have been applied. After the reference value has been set the command returns to OFF. Setting this command to ONCE turns the

CALCulate[1]|2|3|4:RELative:STATe command to ON.

If 0|OFF is selected, no reference value is applied to the measurement signal. There is no situation in which you would want to send this command with OFF. OFF is only available because it is required for the query response.

If 1|ON is selected, it causes error –224, “Illegal parameter value” to occur.

Syntax

CALC 1

2

3

4

:REL :MAGN :AUTO Space 1|ON

0|OFF

?

ONCE



Example

CALC1:REL:AUTO ONCE This command sets a reference value to be 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” occurs.

• If the value is set to ON error –224, “Illegal parameter value” occurs.



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

CALC 1

2

3

4

:REL :STAT Space 0|OFF

?

1|ON

Example

CALC1:REL:STAT OFF This command disables the relative mode on the upper window/upper measurement.

Reset Condition

On reset, relative mode is disabled.

Query

CALCulate[1]|2|3|4:RELative:STATe?



The query returns a 1 or 0 into the output buffer.

• 1 is returned when relative mode is enabled

• 0 is returned when relative mode is disabled

Query Example

CALC1:REL:STAT?

This command queries whether relative 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.




4


CALibration Subsystem 200

CALibration[1]|2[:ALL] 202

CALibration[1]|2[:ALL]?

204

CALibration[1]|2:AUTO [ONCE|ON|OFF|0|1] 206

CALibration[1]|2:RCALibration <boolean> 209

CALibration[1]|2:RCFactor <numeric_value> 211

CALibration[1]|2:ZERO:AUTO [ONCE|ON|OFF|0|1] 213

CALibration[1]|2:ZERO:NORMal:AUTO <boolean> 215

This chapter explains how the CALibration command subsystem is used to zero and calibrate the power meter.


199

4 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:

• CALibration1 represents Channel A

• CALibration2 represent Channel B

This command does not apply to the single channel N1911A power meter and results in the error “Header suffix out of range.”

Zeroing and calibration of the power meter is recommended:

• When a 5 o

C change in temperature occurs

• When you change the power sensor

• Every 24 hours

• Prior to measuring low level signals. For example, 10 dB above the lowest specified power for your sensor.

The following CALibration commands are overlapped commands:

• CAL:ALL

• CAL:AUTO

• CAL:ZERO:AUTO

An overlapped command allows the instrument to continue parsing and executing subsequent commands while it is still executing.


CALibration Subsystem 4

Keyword

CALibration[1]|2

[:ALL]

[:ALL]?

:AUTO

:RCALibration

:RCFactor

:ZERO

:AUTO

:NORMal

:AUTO

Parameter Form Notes

[event; no query]

[event;query]

<boolean>|ONCE

<boolean>

<numeric_value> [non-SCPI]

<boolean>|ONCE

<boolean>

Page

page 202

page 204

page 206

page 209

page 211

page 213

page 215



CALibration[1]|2[:ALL]

N O T E

This command is identical to CALibration[1]|2[:ALL]?, however, unlike the 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. The command assumes that the power sensor is connected to the POWER REF output. The calibration sequence consists of:

1 Zeroing the power meter (CALibration:ZERO:AUTO ONCE), and

2 Calibrating the power meter (CALibration:AUTO ONCE).

For 8480 Series power sensors and N8480 Series power sensors with

Option CFT, the reference calibration factor used during this calibration can be derived from either an active sensor calibration table or the value entered using CALibration:RCFactor. The actual value used is the one which was most recently set. That is, a value entered using

CALibration:RCFactor is overridden if a sensor calibration table is subsequently selected and enabled. Conversely, CALibration:RCFactor overrides any reference calibration factor previously set from a sensor calibration table. To determine the currently set reference calibration factor use CALibration:RCFactor?.

E- Series power sensors and N8480 Series power sensors (excluding Option

CFT) have their sensor calibration tables stored in EEPROM which means that the reference calibration factor is automatically downloaded by the power meter .



Syntax

CAL 1

2

:ALL

Example

CAL1:ALL This command causes the power meter to 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. If you are using an N1912A the error message specifies which channel failed calibration.

• If zeroing was not carried out successfully the error –231, “Data

Questionable; ZERO ERROR” occurs. If you are using an N1912A the error message specifies which channel failed calibration.

• If there is no sensor connected, the error –241, “Hardware Missing” occurs.



CALibration[1]|2[:ALL]?

N O T E

This query is identical to CALibration[1]|2[:ALL], however, unlike the 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. The query assumes that the power sensor is connected to the POWER REF output. The calibration sequence consists of:

1 Zeroing the power meter (CALibration:ZERO:AUTO ONCE), and

2 Calibrating the power meter (CALibration:AUTO ONCE).

When the calibration sequence is completed, 0 or 1 is entered into the output buffer to indicate if the sequence was successful. If the result is:

• 0, the calibration has passed

• 1, the calibration has failed

For the 8480 and N8480 Series power sensors with Option CFT the reference calibration factor used during this calibration can be derived from either an active sensor calibration table or the value entered using

CALibration:RCFactor . The actual value used is the one which was most recently set. That is, a value entered using CALibration:RCFactor is overridden if a sensor calibration table is subsequently selected and enabled. Conversely, CALibration:RCFactor overrides any reference calibration factor previously set from a sensor calibration table. To determine the currently set reference calibration factor use

CALibration:RCFactor?

.

The E- Series power sensors and N8480 Series power sensors (excluding

Option CFT) have their sensor calibration tables stored in EEPROM which means that the reference calibration factor is automatically downloaded by the power meter.



Syntax

CAL 1

2

:ALL ?

Query Example

CAL1:ALL?

This command causes the power meter to perform a calibration sequence on

Channel A and return a result.

Error Messages




Questionable; ZERO ERROR” occurs. If you are using an N1912A the error message specifies which channel failed calibration.

•

If there is no sensor connected, the error –241, “Hardware Missing” occurs.



CALibration[1]|2:AUTO [ONCE|ON|OFF|0|1]

N O T E

This command calibrates the specified channel when enabled. The command assumes that an 8480, E- Series or N8480 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 calibration is updated if the meter’s or sensor’s temperature changes by

±

5 o

C or the time since last calibration is greater then 1000 minutes.

The 0|OFF parameter is only required for the query response and is ignored in the command.

The E- Series power sensors and N8480 Series power sensors (excluding

Option CFT) have their sensor calibration tables stored in EEPROM which means that the reference calibration factor is automatically downloaded by the power meter.

For 8480 Series power sensors and N8480 Series power sensors with

Option CFT, the reference calibration factor used during this calibration can be obtained from an active sensor calibration table or the value entered using CALibration:RCFactor. The actual value used is the one which was most recently set. For example, a value entered using

CALibration:RCFactor is overridden if a sensor calibration table is subsequently selected and enabled and CALibration:RCFactor overrides any reference calibration factor previously set from a sensor calibration table. To determine the current reference calibration factor, use

CALibration:RCFactor?

.

If the power meter is using an 8480, E-Series or N8480 Series power sensor it should be zeroed before calibration using the CALibration:ZERO:AUTO ONCE command.


Syntax

CAL 1

2

:AUTO Space

?

0|OFF

1|ON

ONCE


Example

CAL1:AUTO ONCE This command causes the power meter to perform a calibration on Channel A.

N O T E

Reset Condition

On reset, automatic calibration is disabled.

If the command is set to ON when a N1920 is connected, auto cal is enabled.

Query

CALibration[1]|2:AUTO?

The query always returns a value of 0.

Error Messages

• If this command is set to ON and an 8480 Series, E- Series, N8480 or



P- Series power sensor is connected the error –241, “Hardware missing” occurs.




• If this command is set to ON and TRIGger[SEQuence[1]|2]:COUNt is set to a value >1, the error –221, “Setting conflict” occurs.

• If this command is set to ON (for dual channel, at either measurement channel) when a P- Series power sensor is connected (for dual channel, at either measurement channel) and is in the wait- for- trigger state for external trigger buffering, the error –224, “Illegal parameter value” occurs.



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

CAL 1

2

:RCAL Space

?

0|OFF

1|ON

Example

CAL1:RCAL 1 This command enables the zero/cal lockout facility on Channel A.

Reset Condition

On reset, the state of the zero/cal lockout is unaffected.

Query

CALibration[1]|2:RCALibration?

The query enters a 1 or 0 into the output buffer indicating whether zero/cal lockout is enabled or disabled.

• 1 is returned if zero/cal lockout is enabled

• 0 is returned if zero/cal lockout is disabled



Query Example

CAL1:RCAL?

This command queries whether or not the 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; Please zero and Cal.”

After the sensor has been zeroed and calibrated the return measurement results commands function normally.



CALibration[1]|2:RCFactor <numeric_value>

This command is used with 8480 Series power sensors or N8480 Series power sensors with Option CFT 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.

Syntax

CAL 1

2

:RCF Space

?

numeric_value

DEF

MIN

MAX

Space MIN

MAX

Parameters

Item numeric_value


A numeric value:

• DEF : the default is 100 %

• MIN : 1 %

• MAX :150 %

Range of Values

1.0 to 150.0 PCT

DEF

MIN

MAX



Example

CAL1:RCF 98 This command enters a reference calibration factor of 98 % to Channel A.

Reset Condition

On reset, the reference calibration factor is set to 100 %.

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

CAL2:RCF?

This command queries the reference calibration factor of Channel B.

Error Messages

If this command is used when a P- Series, E- Series or N8480 Series power sensors (excluding Option CFT) is connected the error –241, “Hardware missing” occurs.



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.

The 0|OFF parameter is only required for the query response and is ignored in the command.

Except when using a P- Series sensor, this command assumes that a power sensor is not connected to a power source.

Syntax

CAL 1

2

:ZERO :AUTO Space 0|OFF

1|OFF

?

ONCE

Example

CAL2:ZERO:AUTO ONCE This command causes the power meter to perform a zeroing routine on Channel B.

Reset Condition

On reset, automatic zeroing is disabled.



Query

CALibration[1]|2:ZERO:AUTO?


Error Messages

• If this command is set to ON and an 8480 Series, E- Series or N8480

Series power sensor is connected the error –241, “Hardware missing” occurs.


Questionable; ZERO ERROR” occurs. If you are using an N1912A, the error message specifies which channel failed zeroing.


• If this command is set to ON and TRIGger[:SEQuence[1]|2]:COUNt setting is more than 1, the error –221, “Setting conflict” occurs.



CALibration[1]|2:ZERO:NORMal:AUTO <boolean>

This command provides a quick way of zeroing the NORMAL path of an

E9320 Series sensor. The average only path is unaffected. This command can only be used to zero an E9320 Series sensor and a P- Series sensor.

N O T E

The P-Series sensor only has a NORMAL path. Hence, the reason this E9320 Series sensor command is allowed to function.

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.

The 0|OFF parameter is only required for the query response and is ignored in the command. If 1|ON is selected on an E9320 Series sensor, it causes the error –224, “Illegal parameter value” to occur.

Except when using a P- Series sensor, this command assumes that the

E9320 Series sensor is not connected to a power source.

Syntax

CAL 1

2

:ZERO :NORM :AUTO Space 0|OFF

?

ONCE

Example

CAL2:ZERO:NORM:AUTO ONCE This command causes the power meter to perform a zeroing routine on Channel B.



Reset Condition

On reset, automatic zeroing is disabled.

Query

CALibration[1]|2:ZERO:NORMal:AUTO?


Error Messages


Questionable; ZERO ERROR” occurs. If you are using a dual channel power meter, the error message specifies which channel failed zeroing.

• If this command is set to ON the error –224, “Illegal parameter value” occurs.

• If there is no sensor connected, or if a sensor other than an E9320 or

P- Series is connected, the error –241, “Hardware missing” occurs.

• If an E9320 sensor is connected and is not in NORMAL mode, the error –221 “Settings conflict” occurs.




5


DISPlay Subsystem 218

DISPlay:ENABle <boolean> 219

DISPlay:SCReen:FORMat <character_data> 221

DISPlay[:WINDow[1]|2] Commands 223

DISPlay[:WINDow[1]|2]:ANALog Commands 224

DISPlay[:WINDow[1]|2]:ANALog:LOWer <numeric_value> 225

DISPlay[:WINDow[1]|2]:ANALog:UPPer <numeric_value> 228

DISPlay[:WINDow[1]|2]:FORMat <character_data> 231

DISPlay[:WINDow[1]|2]:METer Commands 234

DISPlay[:WINDow[1]|2]:METer:LOWer <numeric_value> 235

DISPlay[:WINDow[1]|2]:METer:UPPer <numeric_value> 238

DISPlay[:WINDow[1]|2][:NUMeric[1]|2]:RESolution

<numeric_value> 241

DISPlay[:WINDow[1]|2]:SELect[1]|2 243

DISPlay[:WINDow[1]|2]:STATe <boolean> 245

DISPlay[:WINDow[1]|2]:TRACe:FEED <character_data> 247

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.


217

5 DISPlay Subsystem


The DISPlay subsystem is used to control the selection and presentation of the windows used on the power meter’s display.

Parameter Form Notes Page Keyword

DISPlay

:ENABle

:SCReen

:FORMat

[:WINDow[1]|2]

:ANALog

:LOWer

:UPPer

:FORMat

:METer

:LOWer

:UPPer

[:NUMeric[1]|2]

:RESolution

:SELect[1]|2

[:STATe]

:TRACe

:FEED

<boolean>

<character_data>

<numeric_value>

<numeric_value>

<character_data> [non-SCPI]

<numeric_value>

<numeric_value>

[non-SCPI]

[non-SCPI]

<numeric_value>

<boolean>

<character_data>

page 219

page 221

page 225

page 228

page 231

page 235

page 238

page 241

page 243

page 245

page 247


DISPlay Subsystem 5

DISPlay:ENABle <boolean>

This command is used to enable and disable the display. At power- up the display is always enabled.

Syntax

DISP :ENAB Space 0|OFF

?

1|ON

Example

DISP:ENAB 0 This command disables the display.

Reset Condition

On reset, the display is enabled.

Query

DISPlay:ENABle?

The query returns a 1 or 0 into the output buffer.

• 1 is returned when the display is enabled

• 0 is returned when the display is disabled



Query Example

DISP:ENAB?

This command queries whether the display is on or off.



DISPlay:SCReen:FORMat <character_data>

This command sets the display format.

Syntax

DISP :SCR :FORM Space character_data

?

Parameters

Item character_data


Sets the display format:

• WINDowed : the windowed format provides two display windows. Each window can display two measurements.

• EXPanded : the expanded format provides one display window which can display a single measurement. The EXP display format provides access to softkeys.

• FSCReen : the full screen format provides one display window which can display a single measurement. The FSCR display format does not provide access to softkeys.

Range of Values

WIND

EXP

FSCR



Example

DISP:SCReen:FORM FSCR This command sets the display format to full screen.

Reset Condition

On reset, the display format is WIND.

Query

DISPlay:SCReen:FORMat?

The query returns WIND, EXP or FSCR.

.

Query Example

DISP:SCR:FORM?

This command queries the display format.



DISPlay[:WINDow[1]|2] Commands

These commands control various characteristics of the display windows.

WINDow1 and WINDow2 represent the upper and lower windows respectively.


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>

DISPlay[:WINDow[1]|2]:SELect[1]|2

DISPlay[:WINDow[1]|2][:STATe] <boolean>

DISPlay[:WINDow[1]|2]:TRACe:FEED <character_data>



DISPlay[:WINDow[1]|2]:ANALog Commands

These commands control the upper and lower scale limits of the analog meter.


DISPlay[:WINDow[1]|2]:ANALog:LOWer <numeric_value>

DISPlay[:WINDow[1]|2]:ANALog:UPPer <numeric_value>



DISPlay[:WINDow[1]|2]:ANALog:LOWer <numeric_value>

This command sets the analog meter lower scale limit.

N O T E

This command has the same purpose as DISPlay[:WINDow[1]|2]:METer:LOWer

<numeric_value> .

Single Channel

Ratio

Difference

The units used are dependent on the current setting of UNIT:POWer and

CALCulate:RELative:STATe as shown in Table 5- 15 .



Avg, Pk

Pk–Avg

Avg, Pk, Pk–Avg

Avg, Pk

Pk–Avg


Linear

Watt

%

%

Watt

%



Linear

%

%

%

%

%

Log dB dB dB dB dB



DISP

Syntax

:WIND 1

2

:ANAL :LOW Space

?

numeric_value

DEF

MIN

MAX

Space MIN

MAX

Parameters

Item numeric_value


A numeric value for the analog meter lower scale limit:

• DEF : the default is –70 dBm

• MIN : –150 dBm

• MAX : 230 dBm

Units used are determined by the current setting of UNIT:POWer and

CALCulate:RELative:STATe as shown in Table 5-15 .

Range of Values

–150 to 230 dBm

DEF

MIN

MAX

Example

DISP:WIND1:ANAL:LOW –50 This command sets the upper window’s analog meter lower scale limit to –50 dBm.



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 5- 15 .

Query Example

DISP:WIND1:ANAL:LOW?

This command queries the lower scale limit set on the analog meter in the upper window.



DISPlay[:WINDow[1]|2]:ANALog:UPPer <numeric_value>

This command sets the analog meter upper scale limit.

N O T E

This command has the same purpose as DISPlay[:WINDow[1]|2]:METer:UPPer

<numeric_value> .

Single Channel

Ratio

Difference


CALCulate:RELative:STATe as shown in

Table 5- 16 .



Avg, Pk

Pk–Avg

Avg, Pk, Pk–Avg

Avg, Pk

Pk–Avg


Linear

Watt

%

%

Watt

%



Linear

%

%

%

%

%

Log dB dB dB dB dB



DISP

Syntax

:WIND 1

2

:ANAL :UPP Space

?

numeric_value

DEF

MIN

MAX

Space MIN

MAX

Parameters

Item numeric_value


A numeric value for the analog meter upper scale limit:

• DEF : the default is 20 dBm

• MIN : –150 dBm

• MAX: 230 dBm



Table 5-16 .

Range of Values

–150 to 230 dBm

DEF

MIN

MAX

Example

DISP:WIND2:ANAL:UPP 50 This command sets the lower window’s analog meter upper scale limit to 50 dBm.



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 5- 16 .

Query Example

DISP:WIND2:ANAL:UPP?

This command queries the upper scale limit set on the analog meter in the lower window.



DISPlay[:WINDow[1]|2]:FORMat <character_data>

This command selects the format of the selected window.

Syntax

DISP :WIND

2

1 :FORM Space character_data

?

N O T E

• This command has the same purpose as

DISPlay[:WINDow[1]|2]:ANALog:LOWer <numeric_value> .

• This command does not allow the setting set to TRACe when either measurement channel (for dual channel) is configured to initiate external trigger buffering.



Parameters

Item character_data


Sets the window format:

• DIGital : sets the window display to digital. This setting is the same as

SNUMeric.

• ANALog : sets the window display to analog using the currently SELected measurement.

• SNUMeric : sets the window display to single numeric. The currently SELected measurement is displayed. This setting is the same as DIGital.

• DNUMeric : sets the window display to dual numeric.

• TRACe : trace display using the currently

SELected measurement. Used to determine the channel from which the trace is taken.

• CTRAce : sets the display to expanded

CCDF window.

• CTABle : sets the window display to

CCDF table.

Range of Values

DIGital

ANALog

SNUMeric

DNUMeric

TRACe

CTRAce

CTABle

232

Example

DISP:WIND2:FORM DIG This command sets the lower window to a digital display.

Reset Condition

On reset, the N1911A power meter upper window is DIGital and the lower window ANALog. For the N1912A power meter, the defaults for the


DISPlay Subsystem 5 upper and lower windows are DIGital.

Query

DISPlay:[WINDow[1]|2]:FORMat?

The query returns the current format of the selected window.

Query Example

DISP:FORM?

This command queries the current format of 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 or E9320 power sensor connected, error –241, “Hardware missing” occurs.

• If the command is set to TRACe and the selected channel has a

P- Series or E9320 power sensor connected in AVERage measurement mode, the error –221, “Settings conflict” occurs.

• If the command is set to TRACe ( for dual channel, at either measurement channel) when the P- Series or E9320 sensor is connected in normal mo de and SENse:BUFFer:COUNt or

SENse:FREQuency:STEP is more than 1, error –221, “Settings conflict” occurs.



DISPlay[:WINDow[1]|2]:METer Commands

These commands control the upper and lower scale limits of the analog meter.


DISPlay[:WINDow[1]|2]:METer:LOWer <numeric_value>

DISPlay[:WINDow[1]|2]:METer:UPPer <numeric_value>



DISPlay[:WINDow[1]|2]:METer:LOWer <numeric_value>

This command sets the analog meter lower scale limit.

N O T E

This command has the same purpose as DISPlay[:WINDow[1]|2]:ANALog:LOWer

<numeric_value> .


Single Channel

Ratio

Difference



Table 5- 17 .


Avg, Pk

Pk–Avg

Avg, Pk, Pk–Avg

Avg, Pk

Pk–Avg


Linear

Watt

%

%

Watt

%



Linear

%

%

%

%

%

Log dB dB dB dB dB



DISP

Syntax

:WIND

2

1 :MET :LOW Space

?

numeric_value

DEF

MIN

MAX

Space MIN

MAX

Parameters

Item numeric_value


A numeric value for the analog meter lower scale limit:


• MIN : –150 dBm

• MAX : 230 dBm

The default units are defined by

UNIT:POWer and

CALCulate:RELative:STATe .

Range of Values

–150 to 230 dBm

DEF

MIN

MAX

Example

DISP:WIND2:MET:LOW 10 This command sets the lower window’s analog meter lower scale limit.



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


Table 5- 17 .

Query Example

DISP:MET:LOW?

This command queries the lower scale limit set on the analog meter in the upper window.



DISPlay[:WINDow[1]|2]:METer:UPPer <numeric_value>

This command sets the analog meter upper scale limit.

N O T E

This command has the same purpose as DISPlay[:WINDow[1]|2]:ANALog:UPPer

<numeric_value> .

Single Channel

Ratio

Difference



Table 5- 18 .



Avg, Pk

Pk–Avg

Avg, Pk, Pk–Avg

Avg, Pk

Pk–Avg


Linear

Watt

%

%

Watt

%



Linear

%

%

%

%

%

Log dB dB dB dB dB



DISP

Syntax

:WIND

2

1 :MET :UPP Space

?

numeric_value

DEF

MIN

MAX

Space MIN

MAX

Parameters

Item numeric_value


A numeric value for the analog meter upper scale limit:


• MIN : –150 dBm

• MAX : 230 dBm



Table 5-18 .

Range of Values

–150 to 230 dBm

DEF

MIN

MAX

Example

DISP:WIND2:MET:UPP 20 This command sets the lower window’s analog meter upper scale limit.



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.

Query Example

DISP:WIND2:MET:UPP?

This command queries the upper scale limit set on the analog meter in the lower window.



DISPlay[:WINDow[1]|2][:NUMeric[1]|2]:RESolution

<numeric_value>

This command sets the resolution of the measurement result in the specified window.

DISP

Syntax

:WIND 1

2

:NUM 1

2

:RES Space

?

numeric_value

DEF

MIN

MAX

Space MIN

MAX

Parameters

Item numeric_value


A numeric value for the window resolution:

• DEF : 3

• MIN : 1

• MAX : 4

Range of Values

1 to 4

DEF

MIN

MAX



Example

DISP:WIND2:RES 4 This command sets the lower window’s 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 associated with MIN and MAX. The format of the response is <NR1>.

Query Example

DISP:WINDow1:NUMber2RES?

This command queries the resolution setting of the upper window/lower measurement.



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.

Syntax

DISP :WIND

2

1 :SEL 1

2

?

Example

DISP:WIND2:SEL1 This command selects the upper measurement in the lower window.

Reset Condition

On reset, the upper window upper measurement is selected.

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

DISP:SEL1?

This command queries whether or not the upper measurement in the upper window is selected.



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.

Syntax

DISP :WIND

2

1 :STAT Space 0|OFF

?

1|ON

Examples

DISP:WIND2:STAT OFF

DISP:WIND2:STAT ON

This command disables the lower window.

The upper window in shown in expanded format, displaying its currently selected measurement.

This command enables the lower window so that a dual window display is once more provided.

Reset Condition

On reset, both windows are enabled.



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

DISP:WIND2:STAT?

This command queries whether or not the lower window is displayed.



DISPlay[:WINDow[1]|2]:TRACe:FEED <character_data>

This command selects which channel’s trace is displayed in the specified window.

DISP

Syntax

:WIND 1

2

:TRAC :FEED Space character_data

Parameters

Item character_data


Identifies which channel’s trace is displayed.

• SENS1 : Channel A

• SENS2 : Channel B

Range of Values

“SENS1”

“SENS2”

Example

DISP:WIND2:TRAC:FEED

“SENS1”

This command selects Channel A’s trace to be displayed in the lower window.

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

DISP:WIND2:TRAC:FEED?

This command queries the channel of the trace currently displayed in the lower window.




6


FORMat Subsystem 250

FORMat[:READings]:BORDer <character_data> 251

FORMat[:READings][:DATA] <character_data> 253

This chapter explains how the FORMat subsystem is used to set a data format for transferring numeric information.


249

6 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?

• MEASure?

For the N1912A power meter the same FORMat is used on both channels.


FORMat

[:READings]

:BORDer

[:DATA]

<character_data>

<character_data>

page 251

page 253


FORMat Subsystem 6

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

FORM :READ :BORD Space

?

character_data

Parameters

Item character_data


Byte order of binary data transfer:

• NORMal

• SWAPped

Range of Values

NORMal

SWAPped

Example

FORM:BORD SWAP This command sets the byte order to swapped.

Reset Condition

On reset, this value is set to NORMal.



Query

FORMat[:READings]:BORDer?

The query returns the current setting of the byte order. The format of the response is NORMalor SWAPped..

Query Example

FORM:BORD?

This command queries the current byte order setting.


FORMat Subsystem 6

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. The result is an 8 byte block per number. Each complete block is terminated by a line feed character.

For the N1912A power meter the same FORMat is used on both channels.

FORMat data formatting is not affected by TRACe subsystem data formatting.

N O T E

Syntax

FORM :READ :DATA Space

?

character_data

Parameters

Item character_data


Data format for transferring data:

• ASCii

• REAL

Range of Values

ASCii

REAL



Example

FORM REAL This command sets the format to 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

FORM?

This command queries the current format setting.




7


MEMory Subsystem 256

MEMory:CATalog Commands 258


259


261


262

MEMory:CLEar Commands 265

MEMory:CLEar[:NAME] <character_data> 266

MEMory:CLEar:TABLe 268

MEMory:FREE Commands 269

MEMory:FREE[:ALL]?

270

MEMory:FREE:STATe?

271

MEMory:FREE:TABLe?

272

MEMory:NSTates?

273

MEMory:STATe Commands 274


275

MEMory:STATe:DEFine <character_data>,<numeric_value> 276

MEMory:TABLe Commands 278

MEMory:TABLe:FREQuency <numeric_value>{,<numeric_value>} 279


283


<numeric_value>{,<numeric_value>} 284


287

MEMory:TABLe:MOVE <character_data>,<character_data> 288

MEMory:TABLe:SELect <character_data> 290

This chapter explains how the MEMory command subsystem is used to create, edit and review sensor calibration tables.


255

7 MEMory Subsystem


N O T E

The MEMory command subsystem is used to:

• Edit and review sensor calibration tables (8480 Series sensors and

N8480 Series sensors with Option CFT only)

• Store sensor calibration tables (8480 Series sensors and N8480 Series sensors with Option CFT only)

• Edit and review sensor frequency dependent offset tables

• Store sensor frequency dependent offset tables

• Edit and review sensor save/recall registers

Stored tables remain in the power meter’s memory during power down.

The power meter is capable of storing 20 sensor calibration tables and 10 frequency dependent offset tables of 80 frequency points each.

The MEMory subsystem is not used for E-Series, N8480 Series (excluding Option CFT) and

P-Series power sensors calibration tables. These are automatically downloaded to the power meter and cannot be reviewed or edited.

Keyword

MEMory

:CATalog

[:ALL]?

:STATe?

:TABLe?

:CLEar

[:NAME]

:TABLe

:FREE

[:ALL]?

:STATe?

:TABLe?

Parameter Form Notes Page

<character_data>

[query only]

[query only]

[query only]

[no query],

[non-SCPI]

[no query]

[query only]

[query only]

[query only]

page 259

page 261

page 262

page 266

page 268

page 270

page 271

page 272


MEMory Subsystem 7

Keyword

:NSTates?

:STATe

:CATalog?

:DEFine

Parameter Form

<character_data>

[,<numeric_value>]

Notes

[query only]

[query only]

[non-SCPI]

:TABLe

:FREQuency <numeric_value>

[,<numeric_value>]

:POINts?

:GAIN

[:MAGNitude]

:MOVE

:SELect

[query only]

:POINts?

<numeric_value>

[,<numeric_value>]

[non-SCPI]

<character_data>,

<character_data>

<character_data>

[query only],

[non-SCPI]

[no query],

[non-SCPI]

[no query],

[non-SCPI]

Page

page 273

page 275

page 276

page 279

page 283

page 284

page 287

page 288

page 290



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 and N8480 Series sensors with Option CFT only)

• Frequency dependent offset tables

• Save/recall registers







MEMory:CATalog[:ALL]?

This command lists stored sensor calibration tables (8480 Series sensors and N8480 Series Sensors with Option CFT only), frequency dependent offset tables and save/recall registers.

The power meter returns the data in the form of two numeric parameters and as many strings as there are stored tables and save/recall registers:


• The first numeric parameter indicates the amount of memory, in bytes, used for the storage of tables and registers.

• The second numeric parameter indicates the memory, in bytes, available for the storage of tables and registers.

• Each string parameter returned indicates the name, type and size of a stored table or save/recall register:

• <string>, <type>, <size>

• <string> indicates the name of the table or save/recall register.

• <type> indicates TABL for sensor calibration and frequency dependent offset tables, or STAT for a save/recall register.

• <size> indicates the size of the table or save/recall register in bytes.

A sample of a response may look like the following:

1178,26230,"DEFAULT,TABL,14","8481A,TABL,116",

"8482A,TABL,74",..........."State0,STAT,1619",

"State1,STAT,1619","State2,STAT,1619" ...........

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 Agilent Technologies power sensors. These tables can be edited. The predefined data is listed in your user’s guide. These power sensors and table numbers are listed in

Table 7- 19

.

N O T E

Predefined sensor calibration table is not applicable for N8480 Series power sensors with

Option CFT. Therefore you are required to create a new sensor calibration table for the sensors when a sensor calibration table is needed.



Table 7-19 8480 Series Power Sensor Tables

Table

0

6

7

4

5

8

9

1

2

3

Power Sensor

None

8481A

8482A, 8482B, 8482H

8483A

8481D

8485A

R8486A

Q8486A

R8486D

8487A

Table Name

DEFAULT

*

8481A

8482A

8483A

8481D

8485A

R8486A

Q8486A

R8486D

8487A

*

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.

Syntax

MEM :CAT :ALL ?

Example

MEM:CAT?

This command queries the list of tables and save/recall registers.



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.


• The first numeric parameter indicates the amount of memory, in bytes, used for the storage of registers.

• The second parameter indicates the memory, in bytes, available for the storage of registers.

• Each string parameter returned indicates the name, type and size of a save/recall register:

• <string>,<type>,<size>

• <string> indicates the name of the save/recall register.

• <type> indicates STAT for save/recall register.

• <size> indicates the size of the save/recall register in bytes.

For example, a sample of a response may look like:

0,16190,"State0,STAT,0","State1,STAT,0" .........

Syntax

MEM :CAT :STAT ?

Example

MEM:CAT:STAT?

This command queries the list of save/recall registers.



MEMory:CATalog:TABLe?

This command is used to list the stored sensor calibration (8480 Series sensors and N8480 Series sensors with Option CFT only) and frequency dependent offset tables.

The power meter returns the data in the form of two numeric parameters and as many strings as there are stored tables.


• The first numeric parameter indicates the amount of memory, in bytes, used for the storage of tables.

• The second parameter indicates the memory, in bytes, available for the storage of tables.

• Each string parameter returned indicates the name, type and size of a stored table:

• <string>,<type>,<size>

• <string> indicates the name of the table.

• <type> indicates TABL for a table.

• <size> indicates the size of the table in bytes.

For example, a sample of a response may look like:

1178,10040,"DEFAULT,TABL,14","8481A,TABL,116",

"8482A,TABL,74","8483A,TABL,62"...........

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 Agilent Technologies power sensors. These tables can be edited. The predefined data is listed in your user’s guide. These power sensors and table numbers are listed in Table 7- 20 .

N O T E





Table 7-20 8480 Series Power Sensor Tables

Table

0

6

7

4

5

8

9

1

2

3

Power Sensor

None

8481A

8482A, 8482B, 8482H

8483A

8481D

8485A

R8486A

Q8486A

R8486D

8487A

Table Name

DEFAULT

1

8481A

8482A

8483A

8481D

8485A

R8486A

Q8486A

R8486D

8487A

1

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 through CUSTOM_J which do not contain any data when the power meter is shipped from the factory.



Syntax

MEM :CAT :TABL ?

Example

MEM:CAT:TABL?

This command queries the list of stored tables.



MEMory:CLEar Commands

These commands are used to remove the contents stored in the sensor calibration tables (8480 Series sensors and N8480 Series sensors with

Option CFT 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.


MEMory:CLEar:[NAME] <character_data>

MEMory:CLEar:TABLe

The contents cleared using these commands are non-recoverable.

N O T E



MEMory:CLEar[:NAME] <character_data>

This command clears the contents of a specified sensor calibration table

(8480 Series sensors and N8480 Series sensors with Option CFT 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.

The contents cleared using this command are non-recoverable.

N O T E



Syntax

MEM :CLE :NAME Space character_data

Parameters

Item character_data


Contains an existing table name or save/recall register.

Range of Values

Any existing table name or save/recall register.

Example

MEM:CLE "8485A" This command clears the contents of sensor calibration table 8485A.

Error Messages

If the table or save/recall register name does not exist, error –224, “Illegal parameter value” occurs.



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.

The contents cleared using this command are non-recoverable.

N O T E

Syntax

MEM :CLE :TABL

Example

MEM:CLE:TABL This command clears the contents of the currently selected table.

Error Message

If no table is selected, error –221, “Settings conflict” occurs.



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 and N8480 Series sensors with Option CFT 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?



MEMory:FREE[:ALL]?

This query returns the amount of memory free for sensor calibration tables (8480 Series sensors and N8480 Series sensors with Option CFT only), frequency dependent offset tables, and save/recall registers. The format of the response is:

<bytes_available>,<bytes_in_use>

Syntax

MEM :FREE :ALL ?

Example

MEM:FREE?

This command queries the amount of free memory in total.



MEMory:FREE:STATe?

This query returns the amount of memory free for save/recall registers.

The format of the response is:


Syntax

MEM :FREE :STAT ?

Example

MEM:FREE:STAT?

This command queries the amount of free memory for save/recall registers.



MEMory:FREE:TABLe?

This query returns the amount of memory free for sensor calibration tables (8480 Series sensors and N8480 Series sensors with Option CFT only) and frequency dependent offset tables. The format of the response is:


Syntax

MEM :FREE :TABL ?

Example

MEM:FREE:TABL?

This command queries the amount of free memory for tables.



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

MEM :NST ?

Example

MEM:NST?

This command queries the number of registers available for save/recall.



MEMory:STATe Commands

These commands are used to query and define register names.



MEMory:STATe:DEFine



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

MEM :STAT :CAT ?

Example

MEM:STAT:CAT?

This command queries the register names.



MEMory:STATe:DEFine <character_data>,<numeric_value>

This command is used to associate a name with a save/recall register number.

MEM

Syntax

:STAT :DEF Space character_data

?

Space

, numeric_value character_data

276

Parameters

Item character_data


Details the register name. A maximum of 12 characters can be used.

numeric_value A numeric value (<NRf>) for the register number.

Range of Values

A to Z (uppercase) a to z (lowercase)

0-9

_ (underscore)

0 to 9

Example

MEM:STAT:DEF "SETUP1",4 This command names register 4 SETUP1.

Query

MEMory:STATe:DEFine? <string>

The query returns the register number for the given register name.



Query Example

MEM:STAT:DEF? "SETUP1" This command queries the register number 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.

• If a register or sensor calibration table with the same name already exists, error –257, “File name error” occurs (command only).



MEMory:TABLe Commands

These commands are used to define a sensor calibration table (8480 Series sensors and N8480 Series sensors with Option CFT only) or a frequency dependent offset table, and to write to and read data from it.


MEMory:TABLe:FREQuency <numeric_value>{,<numeric_value>}



<numeric_value>{,<numeric_value>}


MEMory:TABLe:MOVE <character_data>,<character_data>

MEMory:TABLe:SELect <character_data>



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- 21 with entries in the

calibration/offset factor lists.

N O T E

N O T E

For sensor calibration tables only, the first calibration factor entered using the

MEMory:TABLe:GAIN command is used as the reference calibration factor.





Table 7-21 Frequency and Calibration/Offset Factor List

Table

0

6

7

4

5

8

9

1

2

3

Power Sensor

None

8481A

8482A, 8482B, 8482H

8483A

8481D

8485A

R8486A

Q8486A

R8486D

8487A

Table Name

DEFAULT

1

8481A

8482A

8483A

8481D

8485A

R8486A

Q8486A

R8486D

8487A

1

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.

For sensosr calibration tables (8480 Series sensors and N8480 Series sensors with Option CFT 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. If you measure a signal with a frequency outside the frequency range defined in the table, then the power meter uses the highest or lowest point in the table to calculate the calibration factor/offset.

Depending on available memory, the power meter is capable of storing 20 sensor calibration tables and 10 frequency dependent offset tables, each containing 80 points.



Syntax

MEM :TABL :FREQ Space

, numeric_value

?

Parameters

Item numeric_value


A numeric value for the frequency. The default units are Hz.

Range of Values

1 kHz to 1000.0 GHz

1,2

1

The following measurement units can be used:

Hz kHz (10

3

)

MHz (10

6

)

GHz (10

9

)

2

All frequencies are truncated to a multiple of 1 kHz.



Example

MEM:TABL:FREQ

200kHz,600kHz

This command enters frequencies of 200 kHz 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

MEM:TABL:FREQ?

This command queries the frequency points in the currently selected table.

Error Messages

• If more than 80 frequencies are in the list, error –108, “Parameter not allowed” occurs.

• If the frequencies are not entered in ascending order, error –220,

“Parameter error;Frequency list must be in ascending order” occurs.

• If a table has not been specified using the MEMory:TABLe:SELect command, the data cannot be entered into the table and error –221,

“Settings conflict” occurs.

• If a frequency is sent which is outside of the allowed frequency range, error –222, “Data out of range” occurs.



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

MEM :TABL :FREQ :POIN ?

Example

MEM:TABL:FREQ:POIN?

This command queries the number of frequency points in the current table.



MEMory:TABLe:GAIN[:MAGNitude]

<numeric_value>{,<numeric_value>}

This command is used to enter calibration factors into the sensor calibration table (8480 Series sensors and N8480 Series sensors with

Option CFT 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. For sensor calibration tables only, the first parameter is the reference calibration factor, each subsequent parameter is a calibration factor point in the sensor calibration table.

Entries in the frequency lists correspond as shown in Table 7- 22

with entries in the calibration/offset factor lists.

Table 7-22 Frequency and Calibration/Offset Factor List

Frequency

-

Frequency 1

"

Frequency 80

Calibration Factor/Offset

Reference Calibration Factor

(For Sensor Calibration Tables)

Calibration Factor/Offset 1

"

Calibration Factor/Offset 80

For sensor calibration tables the number of frequency points must be one less than the number of calibration factor data points. This is verified when the sensor calibration table is selected using

SENSe:CORRection:CSET1:SELect <string> .



Syntax

MEM :TABL :GAIN :MAGN Space

, numeric_value

?

Parameters

Item numeric_value


A numeric value for the calibration/ offset factors. The units are PCT.

Range of Values

1.0 to 150.0

Example

MEM:TABL:SEL "Sensor_1"

MEM:TABL:GAIN 97,99.5,97.4

This command enters a reference calibration factor of 97 % and calibration factors of 99.5 % and 97.4 % into the sensor calibration table.

Query

MEMory:TABLe:GAIN[:MAGNitude]?

The query returns a list of calibration factor/offset points for the currently selected table.



Query Example

MEM:TABL:GAIN?

This command queries the calibration factor/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” occurs.

• If a table is not specified using the MEMory:TABLe:SELect command, the data cannot be entered and error –221, “Settings conflict” occurs.

• If any of the calibration/offset factors are outside of the allowed range, error –222, “Data out of range” occurs.



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 and N8480 Series sensors with

Option CFT only), the reference calibration factor is included

If no values have been set, 0 is returned. If no table is selected, NAN is returned.

Syntax

MEM :TABL :GAIN :MAGN :POIN ?

Example

MEM:TABL:GAIN:POIN?

This command queries the number of calibration factor/offset points in the current table.



MEMory:TABLe:MOVE <character_data>,<character_data>

This command is used to rename a sensor calibration table (8480 Series sensors and N8480 Series sensors with Option CFT only) or a frequency dependent offset table.

MEM

Syntax

:TABL :MOVE Space character_data

, character_data

Parameters

Item character_data

1st parameter) character_data(2nd parameter)


Contains the existing table name.

Range of Values existing table name

Details the new table name. A maximum of

12 characters can be used.


0 - 9

_ (underscore)

Example

MEM:TABL:MOVE

"tab1","tab1a"

This command renames a table named tab1 to tab1a.



Error Messages

• If either table name is invalid, error –224, “Illegal parameter value” occurs.

• If the first parameter does not match an existing table name, error

–256, “File name not found” occurs.

• If the second parameter matches an existing table name or save/recall register, error –257, “File name error” occurs.



MEMory:TABLe:SELect <character_data>

This command is used to activate either a sensor calibration table (8480

Series sensors and N8480 Series sensors with Option CFT only), or a frequency dependent offset table. A table must be activated before any operation can be performed on it.

Syntax

MEM :TABL :SEL Space

?

character_data

Parameters

Item character_data


Details the new table name. A maximum of

12 characters can be used.

Range of Values


0 - 9

_ (underscore)

290

Example

MEM:TABL:SEL "Sensor1" This command selects a sensor calibration table named “Sensor1”.

Query

MEMory:TABLe:SELect?

The query returns the name of the currently selected table.




8


OUTPut Subsystem 292

OUTPut:RECorder[1]|2:FEED <data_handle> 293

OUTPut:RECorder[1]|2:LIMit:LOWer <numeric_value> 295

OUTPut:RECorder[1]|2:LIMit:UPPer <numeric_value> 297

OUTPut:RECorder[1]|2:STATe <boolean> 299

OUTPut:ROSCillator[:STATe] <boolean> 301

OUTPut:TRIGger[:STATe] <boolean> 303

This chapter explains how the OUTput command subsystem is used to switch the POWER REF output on and off.


291

8 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.


OUTPut

:RECorder[1]|2

:FEED

:LIMit

:LOWer

:UPPer

:STATe

:ROSCillator

[:STATe]

:TRIGger

[:STATe]

<data_handle>

<numeric_value>

<numeric_value>

<boolean>

<boolean>

<boolean>

page 293

page 295

page 297

page 299

page 301

page 303


OUTPut Subsystem 8

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 applies to both single and dual channel power meters. RECorder2 applies to dual channel power meters only.

Syntax

OUTP :REC 1

2

:FEED Space data_handle

?

Parameters

Item data_handle


The CALC block specifying the measurement to be sent to the recorder output.

Range of Values

“CALC1” or “CALC”

“CALC2”

“CALC3”

“CALC4”

Example

OUTP:REC2:FEED “CALC1” This command sends the CALC1 measurement to recorder output 2.

Reset Condition

On reset, data_handle is set to its previous value.



Query

OUTPut:RECorder[1]|2:FEED?

The query command returns the current value of data_handle.

Query Example

OUTP:REC2:FEED?

This command queries the value of data_handle for recorder output 2.



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>.

OUTP

Syntax

:REC 1

2

:LIM :LOW Space numeric_value

?

Parameters

Item numeric_value


A numeric value for the minimum scaling value. The units used—dBm, W or %—are dependent on the units currently set for the

CALC block specified in

OUTPut:RECorder[1]|2:FEED

<data_handle> .

Range of Values

–150 to +230 dBm

1 aW to 100 XW

0 % to 999 %

Example

OUTP:REC:LIM:LOW –90 This command sets the minimum scaling value to –90.

Reset Condition

On reset, the minimum scaling value is set to –150 dBm.



Query

OUTPut:RECorder[1]|2:LIMit:LOWer?

The query command returns the minimum scaling value.

Query Example

OUTP:REC:LIM:LOW?

This command returns the minimum scaling value for the specified recorder output.



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>.

OUTP

Syntax

:REC :UPP 1

2

:LIM Space numeric_value

?

Parameters

Item numeric_value


A numeric value for the minimum scaling value. The units used—dBm, W or %—are dependent on the units currently set for the

CALC block specified in

OUTPut:RECorder[1]|2:FEED

<data_handle> .

Range of Values

–150 to +230 dBm

1 aW to 100 XW

0 % to 999 %

Example

OUTP:REC:LIM:UPP 10 This command sets the maximum scaling value to 10.

Reset Condition

On reset, the maximum scaling value is set to +20 dBm.



Query

OUTPut:RECorder[1]|2:LIMit:UPPer?

The query command returns the maximum scaling value.

Query Example

OUTP:REC:LIM:UPP?

This command returns the maximum scaling value for the specified recorder output.



OUTPut:RECorder[1]|2:STATe <boolean>

This command enables or disables the specified recorder output.

Syntax

OUTP :REC 1

2

:STAT Space

?

0|OFF

1|ON

Example

OUTP:REC1:STAT 1 This command enables the specified 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.

• 1 is returned when the recorder output is switched ON

• 0 is returned when the recorder output is switched OFF



Query Example

OUTP:REC2:STAT?

This command queries the status of the recorder output.



OUTPut:ROSCillator[:STATe] <boolean>

This command enables or disables the POWER REF output.

Syntax

OUTP :ROSC :STAT Space 0|OFF

?

1|ON

Example

OUTP:ROSC:STAT 1 This command enables the POWER REF 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.

• 1 is returned when the POWER REF output is enabled

• 0 is returned when the POWER REF output is disabled



Query Example

OUTP:ROSC?

This command queries the status of the

POWER REF output.



OUTPut:TRIGger[:STATe] <boolean>

This command enables or disables the trigger output signal.

When sensor is in triggered average measurement mode, the trigger output signal will only be asserted after the measurement has settled.

N O T E

This command is also applicable when used with 8480, N8480, E4410, E9300 or E9320 sensor (Average mode only).

Syntax

OUTP :TRIG :STAT Space 0|OFF

?

1|ON

Example

OUTP:TRIG:STAT 1 This command enables the trigger output 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 or disabled.

• 1 is returned when the trigger output signal is enabled

• 0 is returned when the trigger output signal is disabled

Query Example

OUTP:TRIG:STAT?

This command queries the status of the trigger output signal.

Error Messages

• If 8480, N8480, E4410, E9300 or E9320 sensor is connected and the trigger source is not set to external, error –221 “Settings conflict” occurs.




9


PSTatistic Subsystem 307

PSTatistic:CCDF:GAUSsian[:STATe] <boolean> 309

PSTatistic:CCDF:GAUSsian:MARKer[1]|2[:SET] 311

PSTatistic:CCDF:MARKer:DELta?

313

PSTatistic:CCDF:MARKer[1]|2:DATa?

315

PSTatistic:CCDF:MARKer[1]|2:X <numeric_value> 317

PSTatistic:CCDF:MARKer[1]|2:Y <numeric_value> 319

PSTatistic:CCDF:REFerence:DATa?

321

PSTatistic:CCDF:REFerence[:STATe] <boolean> 323

PSTatistic:CCDF:REFerence:MARKer[1]|2[:SET] 325

PSTatistic:CCDF:REFerence:POWer:AVERage?

327

PSTatistic:CCDF:REFerence:POWer:PEAK?

328

PSTatistic:CCDF:REFerence:POWer:PTAVerage?

329

PSTatistic[1]|2:CCDF:CONTinuous <boolean> 330

PSTatistic[1]|2:CCDF:COUNt <numeric_value> 332

PSTatistic[1]|2:CCDF:DATa?

334

PSTatistic[1]|2:CCDF:DATa:MAX <numeric_value> 336

PSTatistic[1]|2:CCDF:POWer? <numeric_value> 338

PSTatistic[1]|2:CCDF:PROBability? <numeric_value> 340

PSTatistic[1]|2:CCDF:STORe:REFerence 342

PSTatistic[1]|2:CCDF:TABle?

344

PSTatistic[1]|2:CCDF:TRACe[:STATe] <boolean> 347

PSTatistic[1]|2:CCDF:TRACe:MARKer[1]|2[:SET] 349

PSTatistic[1]|2:CCDF:TRACe:POWer:AVERage?

351

PSTatistic[1]|2:CCDF:TRACe:POWer:PEAK?

353

PSTatistic[1]|2:CCDF:TRACe:POWer:PTAVerage?

355


305

9 PSTatistic Subsystem

Chapter 17 explains how the PSTatistic command subsystem is used to configure the settings of Complementary Cumulative Distribution Function

(CCDF), both in table and trace format.


PSTatistic Subsystem 9


The PSTatistic subsystem is used to configure the settings of

Complementary Cumulative Distribution Function (CCDF), both in table and trace format.


PSTatistic

:CCDF

:GAUSsian

[:STATe]

:MARKer[1]|2

[:SET]

:MARKer

:DELta?

:MARKer[1]|2

:DATa?

:X

:Y

:Reference

:DATa?

[:STATe]

:MARKer[1]|2

[:SET]

:POWer

:AVERage?

:PEAK?

:PTAVerage?

<boolean>

<numeric_value>

<numeric_value>

<boolean>

[query only]

[query only]

[query only]

[query only]

[query only]

[query only]

page 309

page 311

page 313

page 315

page 317

page 319

page 321

page 323

page 325

page 327

page 328

page 329

PSTatistic[1]|2

:CCDF

:CONTinuous

:COUNt

<boolean>

<numeric_value>

page 330

page 332



Keyword

:DATa?

:MAX

:POWer?

:PROBability?

:STORe

:REFerence

:TABle?

:TRACe

[:STATe]

:MARKer[1]|2

[:SET]

:POWer

:AVERage?

:PEAK?

:PTAVerage?

Parameter Form

<numeric_value>

<numeric_value>

<numeric_value>

<boolean>

Notes

[query only]

[query only]

[query only]

[query only]

[query only]

[query only]

[query only]

Page

page 334

page 336

page 338

page 340

page 342

page 344

page 347

page 349

page 351

page 353

page 355



PSTatistic:CCDF:GAUSsian[:STATe] <boolean>

This command is used to turn on or off the Gaussian trace and it is independent of the channels attached.

N O T E

This command is only applicable when P-Series sensors are present and the following conditions are met:

• Free-run acquisition mode is selected

• NORMal or DOUBle measurement speed setting is chosen

• Expanded window is enabled (not full CCDF screen window)

Syntax

PST :CCDF :GAUS :STAT Space

?

0|OFF

1|ON

Example

PST:CCDF:GAUS ON

PST:CCDF:GAUS OFF

Reset Conditions

On reset, the Gaussian trace will be cleared (OFF).


This command turns on the Gaussian trace.

This command turns off the Gaussian trace.

309


Query

PSTatistic:CCDF:GAUSsian[:STATe]?

The query enters a 1 or 0 into the output buffer indicating the status of

Gaussian trace.

• 1 is returned when the Gaussian trace is turned on

• 0 is returned when the Gaussian trace is turned off

Query Example

PST:CCDF:GAUS?

This command queries the state of the

Gaussian trace.

Error Messages

• If command is executed in other window besides expanded CCDF window, error –221 "Settings conflict: Requires CCDF expanded window" occurs.



PSTatistic:CCDF:GAUSsian:MARKer[1]|2[:SET]

This command is used to set the markers on Gaussian trace. The markers will be set only if the trace is present and visible. According to the selections made, the markers will become active on the screen.

N O T E





Syntax

PST :CCDF :GAUS :MARK 1

2

:SET

Example

PST:CCDF:GAUS:MARK This command sets marker 1 on the

Gaussian trace.

Reset Condition

On reset, the marker is set on the next visible trace according to the sequence Channel A, Channel B, Reference or Gaussian.



Error Messages


• If command is executed when the specific trace is not visible , error

–221 "Settings conflict:Trace Not Present" occurs. Check with the command PST:CCDF:GAUS? to check if the trace is enabled.



PSTatistic:CCDF:MARKer:DELta?

This command is used to retrieve power and probability difference between marker 2 and marker 1 at any trace the marker is positioned.

N O T E




Algorithm

Delta = Marker 2 Value - Marker 1 Value where

Delta is the power difference and probability difference

Syntax

PST :CCDF :MARK :DEL ?



Example

PST:CCDF:MARK:DEL?

This command returns the power and probability difference between marker 2 and marker 1.

Reset Condition

On reset, the marker 1 and marker 2 will be set back to their default positions.

Error Messages

• If command is executed in other window besides CCDF window, error

–221 “Settings conflict: Requires CCDF window” occurs.



PSTatistic:CCDF:MARKer[1]|2:DATa?

This command is used to retrieve the power and probability values at the current marker position at any trace the marker is positioned.

N O T E




Syntax

PST :CCDF :MARK 1

2

:DAT ?

Example

PST:CCDF:MARK1:DAT?

This command returns the power and probability values at marker 1.

Reset Condition




Error Messages





PSTatistic:CCDF:MARKer[1]|2:X <numeric_value>

N O T E

This command is used to set the current marker X- axis position at the selected trace.





Syntax

PST :CCDF :MARK 1

2

: X Space numeric_value

Parameters

Item numeric_value


The current marker X-axis position

1

.

• Maximum Value: 50 dB. The value will be set to 0 if negative value is inserted.

Range of Values

< 50

1

The marker will be placed at the point nearest to the specified X-axis position if that particular X value is not available.



Example

PST:CCDF:MARK1:X 20 This command sets marker 1 to the position where the X- axis is 20 dB.

Reset Condition


Error Messages



• If the requested X position is more than max dB then error –220

"Parameter error" occurs.

• If invalid parameter choice has been used then error –224 “Illegal parameter value” occurs.



PSTatistic:CCDF:MARKer[1]|2:Y <numeric_value>

This command is used to set the current marker Y- axis position at the selected trace.

N O T E




Syntax

PST :CCDF :MARK 1

2

:Y Space numeric_value

Parameter

Item numeric_value


The current marker Y-axis position

1

.

• Minimum Value: 0 %

• Maximum Value: 100 %

Range of Values

0 to 100

1

The marker will be placed at the point nearest to the specified Y-axis position if that particular Y value is not available.



Example

PST:CCDF:MARK1:Y 20 This command sets marker 1 to the position where the Y- axis is 20 %.

Reset Condition


Error Messages



• If the requested Y position is more than 100 or less than 0 then error

–220 "Parameter error" occurs.

• If invalid parameter choice has been used then error –224 “Illegal parameter value” occurs.



PSTatistic:CCDF:REFerence:DATa?

This command is used to retrieve the reference trace data and it is independent of the channel attached. The reference trace data will be returned only if there is a reference trace saved.

N O T E

N O T E




The reference trace data returned in the format as shown below:

• The reference trace data maximum X-axis value in dB

• 501 points of the reference trace data

Syntax

PST :CCDF :REF :DAT ?

Example

PST:CCDF:REF:DAT?

This command returns the previously saved reference trace data.

Reset Condition

On reset, the trace will be cleared.



Error Messages


–221 "Settings conflict: Requires CCDF window" occurs.

• If there was no previously saved trace, error –221 "Settings conflict: No reference trace saved" occurs. Please check the status of saved reference trace using command PST:CCDF:STOR:REF?.



PSTatistic:CCDF:REFerence[:STATe] <boolean>

This command is used to turn on or off the reference trace and it is independent of the channel attached.

N O T E





Syntax

PST :CCDF :REF :STAT Space 0|OFF

?

1|ON

Example

PST:CCDF:REF ON

PST:CCDF:REF OFF

This command turns on the previously saved reference trace.

This command turns off the previously saved reference trace.

Reset Condition

On reset, the reference trace will be cleared.



Query

PSTatistic:CCDF:REFerence[:STATe]?

The query enters a 1 or 0 into the output buffer indicating the status of the reference trace stored.

• 1 is returned when the previously stored reference trace is turned on

• 0 is returned when the previously stored reference trace is turned off

Query Example

PST:CCDF:REF?

This command queries whether the reference trace is turned on or off.

Error Messages





PSTatistic:CCDF:REFerence:MARKer[1]|2[:SET]

This command is used to set the marker on the reference trace. The markers will be set only if the trace is present and visible. According to the selections made, the markers will become active on the screen.

N O T E





Syntax

PST :CCDF :REF :MARK 1

2

:SET

Example

PST:CCDF:REF:MARK1 This command sets marker 1 on the reference trace.

Reset Condition

On reset, the marker will be set on the next visible trace according to the sequence of Channel A, Channel B, Reference or Gaussian.



Error Messages



- 221 "Settings conflict: Trace Not Present" occurs. Check with the command PST:CCDF:REF? to check if the trace is enabled.




PSTatistic:CCDF:REFerence:POWer:AVERage?

This command is used to retrieve average power data of the saved reference trace.

N O T E




Syntax

PST :CCDF :REF :POW :AVER ?

Example

PST:CCDF:REF:POW:AVER?

This command returns the average power value of the reference trace.

Error Messages






PSTatistic:CCDF:REFerence:POWer:PEAK?

This command is used to retrieve the peak power data of the saved reference trace.

N O T E




Syntax

PST :CCDF :REF :POW :PEAK ?

Example

PST:CCDF:REF:POW:PEAK?

This command returns the peak power value of the saved reference trace.

Error Messages






PSTatistic:CCDF:REFerence:POWer:PTAVerage?

This command is used to retrieve peak to average data of the saved reference trace.

N O T E




Syntax

PST :CCDF :REF :POW :PTAV ?

Example

PST:CCDF:REF:POW:PTAV?

This command returns the peak to average power of the saved reference trace.

Error Messages






PSTatistic[1]|2:CCDF:CONTinuous <boolean>

This command is used to turn on or off the CCDF Continuous Refresh mode for Channel A or Channel B.

N O T E

This command is only applicable when P-Series sensor is present and free-run acquisition mode is selected. If P-Series sensor is used by the adjacent channel in a dual channel setup, the same setting will be applied for free-run acquisition mode.

Syntax

PST 1

2

:CCDF :CONT Space

?

0|OFF

1|ON

Example

PST1:CCDF:CONT ON

PST2:CCDF:CONT OFF

This command turns on the CCDF

Continuous Refresh mode for Channel A.

This command turns off the CCDF

Continuous Refresh mode for Channel B and the Single Refresh mode is on.

Reset Condition

On reset, the CCDF Continuous Refresh mode will be turned on.



Query

PStatistic[1]|2:CCDF CONTinuous?

The query enters 1 or 0 into the output buffer indicating the status of the

CCDF Continuous Refresh mode.

• 1 is returned when the CCDF Continuous Refresh mode is enabled

• 0 is returned when the CCDF Continuous Refresh mode is disabled (or

CCDF Single Refresh mode is enabled)

Query Example

PST1:CCDF:CONT?

This command queries whether the CCDF

Continuous Refresh mode is on or off for

Channel A.

Error Messages

• If no sensor or wrong sensor is connected to the channel, error –241

"Hardware missing" occurs.

• If channel is not in free- run acquisition mode, error –221 "Settings conflict" occurs.



PSTatistic[1]|2:CCDF:COUNt <numeric_value>

This command is used to set CCDF cummulative counts for Channel A or

Channel B. The increment step for the cummulative counts is 100 M.

N O T E

This command is only applicable when P-Series sensor is present and free-run acquisition mode is selected. If P-Series sensor is used by the adjacent channel in a dual channel setup, the same setting will be applied for free-run acquisition mode.

Syntax

PST 1

2

:CCDF :COUN Space

?

numeric_value

Parameters

Item numeric_value


The CCDF cummulative counts in numeric value.

• Minimum value: 100 M

• Maximum value: 10 G

Range of Values

100 M to 10 G

Example

PST1:CCDF:COUN 1.2G

This command sets the CCDF cummulative counts for Channel A to 1.2

G.



Reset Condition

On reset, the CCDF cummulative counts will be set to the default value,

100 M samples.

Query

PSTatistic[1]|2:CCDF:COUNt?

The query returns the current numeric value of the CCDF cummulative count for the respective channel selected.

Query Example

PST1:CCDF:COUN?

This command queries the numeric value of CCDF cummulative counts for Channel

A.

Error Messages



• If channel is not in free- run acquisition mode, error –221 "Settings conflict" occurs.

• If user inputs a count that is lesser than 100 M or greater than 10 G, error –222 "Data out of range" occurs. Any input count that is within range will be normalized and round down to the nearest 100 M.



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.

N O T E

The maximum power level can be set by using this command:

PSTatistic[1]|2:CCDF:DATa:MAX <numeric_value>

By default, the maximum value is 50 dB.

The power interval between each reading (probability value) is determined by the defined maximum power level divided by 500.

N O T E


• Free run acquisition mode is selected


Syntax

PST 1

2

:CCDF :DAT ?

Example

PST1:CCDF:DAT?

This command returns 501 probability values in % at different power levels within certain range (from 0 dB to maximum power level defined).



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.

• If the acquisition mode is in continuous triggering or triggering source is set to either INT1, INTl2, or EXT, error –221 "Settings conflict" occurs.



PSTatistic[1]|2:CCDF:DATa:MAX <numeric_value>

This command is used to set the maximum value of X- axis CCDF trace.

Syntax

PST

1

2

:CCDF :DAT :MAX numeric_value

?

Parameters

Item numeric_value


X-axis CCDF trace maximum value in dB.

• Minimum value: 5.00 dB

• Maximum value: 50.00 dB

Range of Values

5.00 to 50.00

Example

PST1:CCDF:DAT:MAX 10 This command sets the maximum value of

X- axis CCDF trace to 10 dB.

Reset Condition

On reset, the maximum value for CCDF trace X- axis is set to 50 dB.



Query

PSTatistic[1]|2:CCDF:DATa:MAX?

The query returns the X- axis CCDF trace maximum value.

Query Example

PST1:CCDF:DAT:MAX?

This command queries the maximum value of 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" occurs.

• If the parameter set is more than 50.0, error –222 "Data out of range; value clipped to upper limit" occurs.



PSTatistic[1]|2:CCDF:POWer? <numeric_value>

N O T E

This command is used to return the power level at the specified probability.




Syntax

PST 1

2

:CCDF :POW ?

space numeric_value

Parameters

Item numeric_value


The probability at the queried power.

• Maximum value: 0 %

• Minimum value: 100 %

Range of Values

0.0 to 100

Example

PST1:CCDF:POW? 30 This command queries the power level at probability of 30 %.



Error Messages


• If sensor/sensors connected are not P- Series sensors, error –241



• If the acquisition mode is in continuous triggering or triggering source is set to either INT1, INT2, or EXT, error –221 "Setting conflict" occurs.

• If the parameter specified is less than 0.0 or more than 100.0, error

–220 "Parameter error" occurs.

• If no parameter is specified, error –109 "Missing parameter" occurs.



PSTatistic[1]|2:CCDF:PROBability? <numeric_value>

N O T E

This command is used to return the probability at the specified power level.




Syntax

PST 1

2

:CCDF :PROB ?

space numeric_value

Parameters

Item numeric_value


The power level at the queried probability.

• Maximum value: 50.00 dB

• Minimum value: 0.00 dB

Range of Values

0.00 to 50.0



Example

PST1:CCDF:PROB? 50 This command queries the probability at the power level of 50dB for Channel A.

Error Messages





• If the acquisition mode is in continuous triggering or triggering source is set to either INT1, INT2, or EXT, error –221 "Setting conflict" occurs.

• If the parameter specified is less than 0.0 or more than 50.0, error –220

"Parameter error" occurs.

• If no parameter is specified, error –109 "Missing parameter" occurs.



PSTatistic[1]|2:CCDF:STORe:REFerence

This command is used to store Channel A or Channel B as a reference trace for CCDF graph window.

The trace will be saved as reference trace in volatile RAM.

N O T E

N O T E





Syntax

PST 1

2

:CCDF :STOR :REF

Example

PST:CCDF:STOR:REF

PST2:CCDF:STOR:REF

This command saves the Channel A trace as reference trace.

This command saves the Channel B trace as reference trace.



Reset Condition

On reset, the previously saved reference trace will be cleared.

Query

PSTatistic[1]|2:CCDF:STORe:REFerence?

The query enters a 1 or 0 into the output buffer indicating the status of the CCDF reference.

• 1 is returned when there is a saved reference trace

• 0 is returned when there is no saved reference trace

Query Eample

PST:CCDF:STOR:REF?

This command queries whether there is saved reference trace or not.

Error Messages






• If the acquisition mode is in continuous triggering or triggering source is set to either INT1, INT2, or EXT, error –221 "Settings conflict" occurs.



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.

N O T E

This command will return 10 scalar results in the following order:

1 Average input power (in dBm)

2 Probability at the average input power (in %)

3 Power level (power to average power ratio) that has 10 % of the power (in dB)

4 Power level (power to average power ratio) that has 1 % of the power (in dB)

5 Power level (power to average power ratio) that has 0.1 % of the power (in dB)




9 Peak to average power ratio (in dB)

10 Sample count

N O T E






Syntax

PST 1

2

:CCDF :TAB ?

Example

PST:CCDF:TAB?

PST2:CCDF:TAB?

This command returns the data in CCDF table: 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.

This command returns the data in CCDF table: 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 B.

N O T E

The sample count will always be returned as 100 million samples (100,000,000).



Error Messages








PSTatistic[1]|2:CCDF:TRACe[:STATe] <boolean>

This command is used to turn on or off Channel A or Channel B trace.

N O T E





Syntax

PST 1

2

:CCDF :TRAC :STAT Space

?

0|OFF

1|ON

Example

PST:CCDF:TRAC ON

PST2:CCDF:TRAC OFF

This command turns on Channel A trace.

This command turns off Channel B trace.

Reset Condition

On reset, the trace of the physically connected channel will be shown.



Query

PSTatistic[1]|2:CCDF:TRACe:[:STATe]?

The query enters a 1 or 0 into the output buffer indicating the status of the displayed CCDF trace.

• 1 is returned when there is a trace displayed on the CCDF screen window

• 0 is returned when there is no trace displayed on the CCDF screen window

Query Example

PST:CCDF:TRAC?

This command queries whether there is a trace displayed or not on the CCDF screen window.

Error Messages







PSTatistic[1]|2:CCDF:TRACe:MARKer[1]|2[:SET]

This command is used to set the marker on Channel A or Channel B trace. The markers will be set only if the trace is present and visible.

According to the selections made, the markers will become active on the screen.

N O T E





Syntax

PST 1

2

:CCDF :TRAC :MARK

1

2

:SET

Example

PST:CCDF:TRAC:MARK

PST2:CCDF:TRAC:MARK2

This command sets the marker1 on

Channel A.

This command sets the marker2 on

Channel B.

Reset Condition

On reset, the marker will be set on the next visible trace according to the sequence Channel A, Channel B, Reference or Gaussian.



Error Messages



–221 "Settings conflict:Trace Not Present" occurs. Use the command

PST:CCDF:TRAC?

to check if the trace is enabled.



PSTatistic[1]|2:CCDF:TRACe:POWer:AVERage?

N O T E

This command is used to retrieve average power value of Channel A or

Channel B trace.




Syntax

PST

1

2

:CCDF :TRAC :POW :AVER ?

Example

PST:CCDF:TRAC:POW:AVER?

This command returns the average power value for Channel A trace.

Error Messages





• If command executed in other window besides CCDF window, error







PSTatistic[1]|2:CCDF:TRACe:POWer:PEAK?

This command is used to retrieve peak power value of Channel A or

Channel B trace.

N O T E




Syntax

PST 1

2

:CCDF :TRAC :POW :PEAK ?

Example

PST:CCDF:TRAC:POW:PEAK?

This command returns the peak power value of Channel A trace.

Error Messages





• If command executed in other window besides CCDF window, error







PSTatistic[1]|2:CCDF:TRACe:POWer:PTAVerage?

This command is used to retrieve peak to average power value of Channel

A or Channel B trace.

N O T E




Syntax

PST 1

2

:CCDF :TRAC :POW :PTAV ?

Example

PST:CCDF:TRAC:POW:PTAV?

This command returns the peak to average power value of Channel A trace.

Error Messages













10

SENSe Subsystem

[SENSe] Subsystem 359

[SENSe[1]]|SENSe2:AVERage Commands 362

[SENSe[1]]|SENSe2:AVERage:COUNt <numeric_value> 363

[SENSe[1]]|SENSe2:AVERage:COUNt:AUTO <boolean> 366

[SENSe[1]]|SENSe2:AVERage:SDETect <boolean> 369

[SENSe[1]]|SENSe2:AVERage[:STATe] <boolean> 371

[SENSe[1]]|SENSe2:AVERage2 Commands 373

[SENSe[1]]|SENSe2:AVERage2:COUNt <numeric_value> 374

[SENSe[1]]|SENSe2:AVERage2[:STATe] <boolean> 376

[SENSe[1]]|SENSe2:BANDwidth|BWIDth:VIDeo <character_data> 378

[SENSe[1]]|SENSe2:BUFFer:COUNt <numeric_value> 381

[SENSe[1]]|SENSe2:BUFFer:MTYPe <string> 384

[SENSe[1]]|SENSe2:CORRection Commands 387

[SENSe[1]]|SENSe2:CORRection:CFACtor|GAIN[1][:INPut][:MAGNitude]

<numeric_value> 388

[SENSe[1]]|SENSe2:CORRection:CSET[1]|CSET2 Commands 391

[SENSe[1]]|SENSe2:CORRection:CSET[1]|CSET2[:SELect] <string> 392

[SENSe[1]]|SENSe2:CORRection:CSET[1]|CSET2:STATe <boolean> 395

[SENSe[1]]|SENSe2:CORRection:DCYCle|GAIN3 Commands 397

[SENSe[1]]|SENSe2:CORRection:DCYCle|GAIN3[:INPut] [:MAGNitude]

<numeric_value> 398

[SENSe[1]]|SENSe2:CORRection:DCYCle|GAIN3:STATe <boolean> 401

[SENSe[1]]|SENSe2:CORRection:FDOFfset|GAIN4[:INPut][:MAGNitude]?

403

[SENSe[1]]|SENSe2:CORRection:GAIN2 Commands 404

[SENSe[1]]|SENSe2:CORRection:GAIN2:STATe <boolean> 405

[SENSe[1]]|SENSe2:CORRection:GAIN2[:INPut] [:MAGNitude]

<numeric_value> 407

[SENSe[1]]|SENSe2:DETector:FUNCtion <character_data> 410


357

10 SENSe Subsystem

[SENSe[1]]|SENSe2:FREQuency[:CW|:FIXed] <numeric_value> 412

[SENSe[1]]|SENSe2:FREQuency[:CW|:FIXed]:STARt

<numeric_value> 415

[SENSe[1]]|SENSe2:FREQuency[:CW|:FIXEd]:STEP

<numeric_value> 418

[SENSe[1]]|SENSe2:FREQuency[:CW|:FIXed]:STOP

<numeric_value> 422

[SENSe[1]]|SENSe2:MRATe <character_data> 425

[SENSe[1]]|SENSe2:POWer:AC:RANGe <numeric_value> 428

[SENSe[1]]|SENSe2:POWer:AC:RANGe:AUTO <boolean> 430

[SENSe[1]]|SENSe2:SWEep[1]|2|3|4 Commands 432

[SENSe[1]]|SENSe2:SWEep[1]|2|3|4:AUTO <character_data> 433

[SENSe[1]]|SENSe2:SWEep[1]|2|3|4:AUTO:REF1|REF2

<numeric_value> 436

[SENSe[1]]|SENSe2:SWEep[1]|2|3|4:OFFSet:TIME

<numeric_value> 438

[SENSe[1]]|SENSe2:SWEep[1]|2|3|4:TIME <numeric_value> 440

[SENSe[1]]|SENSe2:TEMPerature?

442

[SENSe[1]]|SENSe2:TRACe Commands 444

[SENSe[1]]|SENSe2:TRACe:OFFSet:TIME <numeric_value> 445

[SENSe[1]]|SENSe2:TRACe:TIME <numeric_value> 447

[SENSe[1]]|SENSe2:TRACe:UNIT <character_data> 449

[SENSe[1]]|SENSe2:V2P ATYPe|DTYPe 451

SENSe[1]|2:TRACe:AUToscale 453

SENSe[1]|2:TRACe:LIMit:LOWer <numeric_value> 455

SENSe[1]|2:TRACe:LIMit:UPPer <numeric_value> 458

SENSe[1]|2:TRACe:X:SCALe:PDIV <numeric_value> 461

SENSe[1]|2:TRACe:Y:SCALe:PDIV <numeric_value> 463

This chapter explains how the SENSe command subsystem directly affects device specific settings used to make measurements.


SENSe Subsystem 10

[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. At a lower level SENSe enables you to change the following parameters: RANGe, FREQuency, LOSS, CFACator|GAIN1

(calibration factor), GAIN2 (channel offset), DCYCle (duty cycle) and

AVERage , without completely re- configuring the power meter.

The SENSe command subsystem also allows you to select the measurement speed, a sensor calibration table, and a frequency dependent offset table.

The numeric suffix of the SENSe program mnemonic in the SENSe commands refers to a channel, that is SENSe1 and SENSe2 represent

Channel A and Channel B respectively.

N O T E

If you are using the single channel N1911A power meter the SENSe2 commands are irrelevant and cause the error “Header suffix out of range.”

Keyword

[SENSe[1]]|SENSe2

:AVERage

:COUNt

:AUTO

:SDETect

[:STATe]

:AVERage2

:COUNt

[:STATe]

:BANDwidth|BWIDth

:VIDeo

Parameter Form

<numeric_value>

<boolean>

<boolean>

<boolean>

<numeric_value>

<boolean>

<character_data>


Notes Page

[non-SCPI]

page 363

page 366

page 369

page 371

page 374

page 376

page 378

359


Keyword

:BUFFer

:COUNt

:CORRection

:CFACtor|GAIN[1]

[:INPut]

[:MAGNitude]

:CSET[1]|CSET2

[:SELect]

:STATe

:DCYCle|GAIN3

[:INPut]

[:MAGNitude]

:STATe

:FDOFfset|GAIN4

[:INPut]

[:MAGNitude]

:GAIN2

:STATe

[:INPut]

[:MAGNitude]

:DETector

:FUNCtion

:FREQuency

[:CW|FIXed]

[:CW]

:STARt

:STEP

:STOP

:MRATe

Parameter Form

<numeric_value>

<numeric_value>

<string>

<boolean>

<numeric_value>

<boolean>

<boolean>

<numeric_value>

<character_data>

<numeric_value>

Notes

[non-SCPI]

[non-SCPI]

[query only]

<numeric_value><unit> [non-SCPI]

<numeric_value> [non-SCPI]

<numeric_value><unit> [non-SCPI]

<character_data>

Page

page 381

page 388

page 392

page 395

page 398

page 401

page 403

page 405

page 407

page 410

page 412

page 415

page 418

page 422

page 425



Keyword

:POWer

:AC

:RANGe

:AUTO

:SWEep[1]|2|3|4

:Auto

:Auto

:REF1|REF2

:OFFSet

:TIME

:TIME

:TEMPerature?

:TRACe

:V2P

:OFFSet

:TIME

:TIME

:UNIT

SENSe[1]|2

:TRACe

:AUToscale

:LIMit

:LOWer

:UPPer

:X

:SCALe

:PDIV

:Y

:SCALe

:PDIV

Parameter Form

<numeric_value>

<boolean>

<character_data>

<numeric_value>

<numeric_value>

<numeric_value>

<numeric_value>

<numeric_value>

<character_data>

ATYPe|DTYPe

<numeric_value>

<numeric_value>

<numeric_value>

<numeric_value>


Notes Page

[non-SCPI]

page 428

page 430

page 433

page 436

[query only]

page 438

page 440

page 442

[non-SCPI]

page 445

page 447

page 449

page 451

page 453

page 455

page 458

page 461

page 463

361


[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.


[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: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.


[SENSe[1]]|SENSe2:AVERage:STATe command to ON.

N O T E

For most applications, automatic filter length selection

([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.



Syntax

SENS 1

SENS2

: AVER :COUN Space

?

numeric_value

DEF

MIN

MAX

Space MIN

MAX

Parameters

Item numeric_value


A numeric value defining the filter length.

DEF : the default value is 4

MIN : 1

MAX : 1024

Range of Values

1 to 1024

DEF

MIN

MAX

Example

AVER:COUN 400 This command enters a filter length of 400 for Channel A.

Reset Condition

On reset, the filter length is set to 4.



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

AVER:COUN?

This command queries the filter length for

Channel A.

Error Messages

If a filter length value is entered using

[SENSe[1]]|SENSe2:AVERage:COUNt while [SENSe[1]]|SENSe2:SPEed is set to 200, the error –221, “Settings Conflict” occurs. However, the filter length value is set but the [SENSe[1]]|SENSe2:AVERage:STATe command is not automatically set ON.



[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. The number of readings averaged together depends on the resolution and the power level in which the power meter is currently operating.

Figure 10- 20 is an example of the

averaged number of readings for each range and resolution when the power meter is in auto measurement average mode and using a P- Series or E932XX power sensor.

Setting this command to ON automatically sets the

[SENSe[1]]|SENSe2:AVERage:STATe

command to ON.

366

Maximum Sensor Power 1

Resolution Setting

2 3

1 1 1

4

8

10 dB

10 dB

10 dB

1

1

1

1

1

1

1

2

16

16

32

256

10 dB

Minimum Sensor Power

Figure 10-20Example of Averaged Readings

1 8 128 128

If [SENSe[1]]|SENSe2:AVERage:COUNt:AUTO is set to OFF, the filter length is set by the [SENSe[1]]|SENSe2:AVERage:COUNt command. Using the [SENSe[1]]|SENSe2:AVERage:COUNt command disables automatic averaging.

Auto averaging is enabled by the MEASure:POWer:AC? and



N O T E

CONFigure:POWer:AC? commands.

For most applications, automatic filter length selection

([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.

Syntax

SENS 1

SENS2

: AVER :COUN :AUTO Space 0|OFF

?

1|ON

ONCE

Example

AVER:COUN:AUTO OFF This command disables automatic filter length selection for Channel A.

Reset Condition

On reset, automatic averaging is enabled.

Query

[SENSe[1]]|SENSe2:AVERage:COUNt:AUTO?



The query enters a 1 or 0 into the output buffer indicating whether automatic filter length is enabled or disabled.

• 1 is returned when automatic filter length is enabled

• 0 is returned when automatic filter length is disabled

Query Example

AVER:COUN:AUTO?

This command queries whether automatic filter 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.



[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. The filter then starts storing new measurement values. This feature shortens the filter time when the input power changes substantially. for the filter output to get to its final value. Note that this result appears to settle faster, although true settling to the final value is unaffected.

N O T E

Step detection is automatically disabled when TRIG:DEL:AUTO is ON and the trigger mode is set to free run.

Under this circumstances the value of SENS:AVER:SDET is ignored. Note also that

SENS:AVER:SDET is not set by the instrument (that is, SENS:AVER:SDET retains its current setting which may indicate that step detection is ON).

N O T E

With certain pulsing signals step detect may operate on the pulses, preventing the final average being completed and making the results unstable. Under these conditions SDET should be set to OFF.

Syntax

SENS

SENS2

1 : AVER :SDET Space

?

0|OFF

1|ON



Example

SENS:AVER:SDET OFF This command disables step detection.

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.

• 1 is returned when step detection is enabled

• 0 is returned when step detection is disabled

Query Example

SENS:AVER:SDET?

This command queries whether step detection is on or off.



[SENSe[1]]|SENSe2:AVERage[:STATe] <boolean>

This command is used to enable and disable averaging.

Syntax

SENS

SENS2

1 : AVER :STAT Space

?

0|OFF

1|ON

Example

AVER 1 This command enables averaging on

Channel A.

Reset Condition

On reset, averaging is ON.

Query

[SENSe[1]]|SENSe2:AVERage[:STATe]?

The query enters a 1 or 0 into the output buffer indicating the status of averaging.

• 1 is returned when averaging is enabled

• 0 is returned when averaging is disabled



Query Example

SENS2:AVER?

This command queries whether averaging is on or off for Channel B.

Error Messages

• If [SENSe[1]]|SENSe2:AVERage:STATe is set to ON while


Conflict” occurs.

• If [SENSe[1]]|SENSe2:AVERage:STATe is set to ON when a N1920 or

E9320 power sensor is connected in AVERage measurement mode and is in the wait- for- trigger state for external trigger buffering, the error

–221, “Settings Conflict” occurs.



[SENSe[1]]|SENSe2:AVERage2 Commands

These commands control video averaging, which is used to improve measurement accuracy, for the P- Series and E- Series E9320 power sensor.

They combine successive measurements to produce a new composite result.

N O T E

If the command is used when a sensor other than a P-Series or E9320 power sensor is connected, error –241, “Hardware missing” occurs.

If the commands in this section are used when an E9320 sensor is connected and set to

AVERage mode rather than NORMal mode, the error –221, “Settings Conflict” occurs.


[SENSe[1]]|SENSe2:AVERage2:COUNt <numeric_value>

[SENSe[1]]|SENSe2:AVERage2[:STATe] <boolean>



[SENSe[1]]|SENSe2:AVERage2:COUNt <numeric_value>

This command is used to enter the video filter length for the P- Series and

E9320 sensor. Video filtering is applied to the traces. Successive traces are combined to reduce noise without affecting the dynamic characteristic of the signal.

Syntax

SENS 1

SENS2

: AVER2 :COUN Space

?

numeric_value

DEF

Parameters

Item numeric_value


A numeric value defining the filter length.

• DEF : the default value is 4.

1

This is only implemented in powers of 2 (2 n

).

Range of Values

1 to 256

1

DEF

Example

AVER2:COUN 16 This command enters a video filter length of 16 for Channel A.



Reset Condition

On reset, the filter length is set to 4.

Query

AVERage2:COUNt?

The query returns the current setting of the video filter length. The format of the response is <NR1>.

Query Example

AVER2:COUN?

This command queries the video filter length for Channel A.

Error Messages

• If the command is used when a sensor other than a P- Series or E9320 power sensor is connected, error –241, “Hardware missing” occurs

•

If the command is used when an E9320 sensor is connected and set to

AVERage mode rather than NORMal mode, the error –221, “Settings

Conflict” occurs.



[SENSe[1]]|SENSe2:AVERage2[:STATe] <boolean>

This command is used to enable and disable video averaging for the

P- Series or E9320 sensor.

Syntax

SENS

SENS2

1 : AVER2 :STAT Space

?

0|OFF

1|ON

Example

AVER2 1 This command enables video averaging on 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.

• 1 is returned when averaging is enabled.

• 0 is returned when averaging is disabled.



Query Example

SENS2:AVER2?

This command queries whether averaging is on or off for Channel B.

Error Messages


• If the command is used when an E9320 sensor is connected and set to


Conflict” occurs.



[SENSe[1]]|SENSe2:BANDwidth|BWIDth:VIDeo

<character_data>

This command sets the sensor bandwidth on a P- Series or an E9320

Series sensor.

Syntax

SENS 1

SENS2

: BAND

BWID

:VID Space character_data

?

378

Parameters

Item character_data


Defines the sensor bandwidth.

Range of Values

HIGH

MEDium

LOW

OFF

Values for HIGH, MEDIUM, LOW and OFF are sensor dependant as shown in the following table:

Sensor

E9321A

E9325A

E9322A

E9326A

E9323A

E9327A

Video Bandwidth Settings

LOW

30 kHz

MEDium

100 kHz

100 kHZ

300 kHz

300 kHz

1.5 MHz

HIGH

300 kHz

1.5 MHz

5 MHz

OFF

300 kHz

1

1.5 MHz

1

5 MHz

1



Sensor

N1920A

N1921A

1

At 3.0 dB roll off point.

Video Bandwidth Settings

LOW

5 MHz

MEDium

15 MHz

Example

SENSe1:BAND:VID HIGH

HIGH

30 MHz

OFF

30 MHz

This command sets sensor bandwidth to high for Channel A.

Reset Condition

On reset, sensor bandwidth is set to OFF.

Query

[SENSe[1]]|SENSe2:BANDwidth|BWIDth:VIDeo?

The query returns the current sensor bandwidth setting.

Query Example

SENS2:BAND:VID?

This command queries the current sensor bandwidth setting for Channel B.



N O T E

Error Messages


• If the command is used when a P- Series or an E9320 sensor is connected and set to AVERage mode rather than NORMal mode, the error –221, “Settings Conflict” occurs.

Selection of video bandwidth to LOW, MED or HIGH implements digital signal processing to ensure a flat bandwidth up to the frequency shown, bandwidths are flat to ±0.1 dB. In the

OFF state no corrections are applied and the response has a slow roll-off.



[SENSe[1]]|SENSe2:BUFFer:COUNt <numeric_value>

This command sets the buffer size for average or peak measurement. It must be used in conjunction with external trigger.

It can only be set when frequency sweep is disabled (FREQ:STEP 0).

Otherwise, this parameter will be automatically overwritten by frequency sweep step. If trace display is turned on, the measurement window will be restored to single numeric or analog depends on the number of measurement channel.

N O T E

This command is only applicable when used with 8480, N8480, E4410, E9300, E9320 or

N1920 power sensors (average or peak).

Syntax

SENS

SENS2

1

: FREQ :COUN Space numeric_value

?

Parameters

Item numeric_value

Description

A numeric value for buffer size.

Range of Values

1 to 2048



Example

BUFF:COUN 100 This command sets the average or peak measurement buffer size to 100 for

Channel A.

Query

[SENSe[1]]|SENSe2:BUFFer:COUNt?

This query is used to retrieve the average or peak measurement buffer size.

Query Example

BUFF:COUN?

This query returns the average or peak measurement buffer size for Channel A.

382

On Reset

On *RST, the value is set to 1.

Error Messages

• If no sensor or wrong sensor is connected to the channel, error –241,


• If E4410, N8480, E9300, E9320 or N1920 sensor is connected but acquisition mode is in free run, error –221, “Setting conflict. Invalid acquisition mode” occurs.

• If frequency sweep step is nonzero, error –221, “Settings conflict.

Frequency sweep enabled. Buffer count overidden” occurs.



• If parameter is set lower than 1, error –222 “Data out of range; value clipped to lower limit” occurs.

• If parameter is set higher than 2048, error –222 “Data out of range; value clipped to upper limit” occurs.



[SENSe[1]]|SENSe2:BUFFer:MTYPe <string>

This command sets the measurement type to be returned from the buffer.

It can only be used in conjunction with external trigger.

This command is only applicable when connecting E9320 or N1920 sensor in peak mode.

N O T E

Syntax

SENS 1

2

3

4

: FREQ :MTYPe Space string

?

SENS2

Parameters

Item string

Description

The input measurement type to be fed to the specific input on the SENSe block:

• PEAK: peak power

• PTAV: peak to average

• AVER: average

• MIN: minimum power

Range of Values

“PEAK”

“PTAV”

“AVER”

“MIN”



Example

BUFF:MTYP AVER This command sets the measurement type to average for Channel A.

Query

[SENSe[1]]|SENSe2:BUFFer:MTYP?

This query is used to retrieve measurement type settings.

Query Example

BUFF:MTYP?

This query returns the measurement type to average for Channel A.

On Reset

On *RST, the value is set to AVER

Error Messages



• If E9320 or N1920 sensor is connected but acquisition mode is in free run, error –221, “Setting conflict. Invalid acquisition mode” occurs.

• If E9320 or N1920 sensor is connected but sensor mode is average, error –221, “Setting conflict. Invalid acquisition mode” occurs.

• If E9320 or N1920 sensor is connected but trigger source is not external, error- 221 “Setting conflict. Invalid acquisition mode” occurs.



• If parameter set is a string but it is invalid, error- 224 “Illegal parameter value” occurs.



[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.


[SENSe[1]]|SENSe2:CORRection:CFACtor|GAIN[1][:INPut]

[:MAGNitude] <numeric_value>

[SENSe[1]]|SENSe2:CORRection:CSET[1]|CSET2

[:SELect] <string>

[SENSe[1]]|SENSe2:CORRection:CSET[1]|CSET2:STATe <boolean>

[SENSe[1]]|SENSe2:CORRection:DCYCle|GAIN3[:INPut]


[SENSe[1]]|SENSe2:CORRection:DCYCle|GAIN3:STATe <boolean>

[SENSe[1]]|SENSe2:CORRection:FDOFfset|GAIN4[:INPut]

[:MAGNitude]?

[SENSe[1]]|SENSe2:CORRection:LOSS2[:INPut][:MAGNitude]

<numeric_value>

[SENSe[1]]|SENSe2:CORRection:LOSS2:STATe <boolean>



[SENSe[1]]|SENSe2:CORRection:CFACtor|GAIN[1][:INPut][:M

AGNitude] <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. Using GAIN1 complies with the SCPI standard, whereas

CFACtor does not—this may make your program easier to understand.

SENS

Syntax

1 :

SENS2

CORR :GAIN 1 :INP :MAGN

:CFAC

Space

?

numeric_value

DEF

MIN

MAX

Space MIN

MAX



Parameters

Item Description/Default

A numeric value.

numeric_value

( for CFACtor and

GAIN1)

• DEF : the default value is 100 %

• MIN : 1 %

• MAX : 150 %

Range of Values

1 to 150 PCT

1

DEF

MIN

MAX

1

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

SENS2:CORR:GAIN1 This command sets a gain correction of

100% for Channel B.

Reset Condition

On reset, CFACtor|GAIN1 is set to 100 %.

Query

[SENSe[1]]|SENSe2:CORRection:CFACtor|GAIN[1][:INPut]

[:MAGNitude]? [MIN|MAX]

The query returns the current gain correction setting or the values associated with MIN and MAX.



Query Example

CORR:GAIN1?

This command queries the current 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” occurs.



[SENSe[1]]|SENSe2:CORRection:CSET[1]|CSET2 Commands

N O T E

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, N8480 Series (excluding Option

CFT) or E-Series power sensor is connected, the error –241, “Hardware missing” occurs.


[SENSe[1]]|SENSe2:CORRection:CSET[1]|CSET2[:SELect] <string>

[SENSe[1]]|SENSe2:CORRection:CSET[1]|CSET2:STATe <boolean>



[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. The calibration factor is interpolated from the table using the setting for [SENSe[1]]|SENSe2:FREQuency.

N O T E

SENS

SENS2

If [SENSe[1]]|SENSe2:CORRection:CSET[1]|CSET2:STATe is set to OFF, the selected sensor calibration table or frequency offset table is not being used.

1

Syntax

: CORR :CSET

:CSET2

1 :SEL Space

?

string

Parameters

Item string


String data representing a sensor calibration table, or frequency dependent offset table name.

Range of Values

Any existing table name

(Existing table names can be listed using

MEMory:CATalog:TABle?

).



Example

CORR:CSET1 ‘PW1’ This command enters the name of the sensor 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 .

Query Example

CORR:CSET1?

This command queries the sensor calibration table currently used for

Channel A.

Error Messages

• If <string> is not valid, error –224, “Illegal parameter value” occurs.

• If a table called <string> does not exist, error –256, “File name not found” occurs.

• When a sensor calibration table is selected, the power meter verifies that the number of calibration points defined is one more than the number of frequency points defined. When a frequency dependent


10 SENSe Subsystem offset table is selected, the power meter verifies that the number of offset points defined is equal to the number of frequency points defined. If this is not the case, error –226, “Lists not the same length” occurs.

• If the CSET1 command is used when a P- Series or an E- Series power sensor is connected the error –241, “Hardware missing” occurs.



[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.

When the CSET1 command is set to ON, the reference calibration factor is taken from the sensor calibration table and is used during calibration.

SENS

SENS2

Syntax

1 : CORR :CSET

:CSET2

1 :STAT Space

?

0|OFF

1|ON

Example

CORR:CSET1:STAT 1 This command enables the use of the currently active sensor calibration table for Channel A.

Reset Condition

On reset, the sensor calibration table and frequency dependent offset table are not affected.



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

SENS2:CORR:CSET1:STAT?

This command queries whether there is currently an active sensor calibration table for Channel B.

Error Messages

• If you attempt to set this command to ON and no table has been selected using

[SENSe[1]]|SENSe2:CORRection:CSET[1]|CSET2:[SELect] then error

–221, “Settings conflict” occurs and

[SENSe[1]]|SENSe2:CORRection:CSET[1]|CSET2:STATe remains OFF.

• If the CSET1 command is used when a P- Series, N8480 Series

(excluding Option CFT) or an E- Series power sensor is connected, the error –241 “Hardware missing” occurs.



[SENSe[1]]|SENSe2:CORRection:DCYCle|GAIN3 Commands

These commands control the pulse power measurement feature of the power meter.




[SENSe[1]]|SENSe2:CORRection:DCYCle|GAIN3:STATe <boolean>

N O T E

You can use either DCYCLe or GAIN3 in these commands, both do the same. Using

GAIN3 complies with the SCPI standard whereas DCYCle does not, but may make your program more understandable.



[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. The power meter measures the average power in the pulsed input signal and then divides the result by the duty cycle value to obtain a pulse power reading.


[SENSe[1]]|SENSe2:CORRection:DCYCle|GAIN3:STATe

command to ON.

N O T E

Pulse measurements are not recommended using E-Series power sensors at power levels above –20 dBm.

Pulse power averages out any deviations in the pulse such as overshoot or ringing. Hence, it is called pulse power and not peak power or peak pulse power.

In order to ensure accurate pulse power readings, the input signal must be pulsed with a rectangular pulse. Other pulse shapes (such as triangle, chirp or Gaussian) cause incorrect results.

The pulse power on/off ratio must be much greater than the duty cycle ratio.



Syntax

SENS 1

SENS2

: CORR :DCYC

:GAIN3

:INP :MAGN

Space

?

numeric_value

DEF

MIN

MAX

Space MIN

MAX

Parameters

Item numeric_value


A numeric value for the duty cycle.

• DEF : the default value is 1 %

• MIN : 0.001 %

• MAX : 99.999 %

The units are PCT, and are optional.

Example

CORR:DCYC 90PCT

Range of Values

0.001 to 99.999 PCT

DEF

MIN

MAX

This command sets a duty cycle of 90 % for

Channel A.



Reset Condition

On reset, the duty cycle is set to 1 % (DEF).

Query


[:MAGNitude]? [MIN|MAX]

The query returns the current setting of the duty cycle or the values associated with MIN and MAX.

Query Example

CORR:GAIN3?

This command queries the current setting of the duty cycle for Channel A.

400

Error Messages

• If a duty cycle value is entered using

[SENSe[1]]|SENSe2:CORRection:DCYCle|GAIN3 while


Conflict” occurs. However, the duty cycle value is set but the

[SENSe[1]]|SENSe2:CORRection:DCYCle|GAIN3:STATe command is not automatically set ON.

• If this command is used when an E4412A/E4413A power sensor is connected, the error –310, “System error;Dty Cyc may impair accuracy with ECP sensor” occurs. If you are using a dual channel power meter the error message specifies the channel.

• If this command is used when a E9320 Series power sensor is set to

NORMal mode, the error –221, “Settings Conflict” occurs.

• If this command is used when a P- Series power sensor is connected, the error –241, “Hardware missing” occurs.



[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 1

SENS2

: CORR :DCYC

:GAIN3

:STAT Space

?

0|OFF

1|ON

Example

CORR:DCYC:STAT 1 This command enables the pulse measurement feature on Channel A.

Reset Condition

On reset, the pulse power measurement feature is disabled.

Query

[SENSe[1]]|SENSe2:CORRection:DCYCle|GAIN3:STATe?

The query enters a 1 or 0 into the output buffer indicating the status of the pulse power measurement feature.



• 1 is returned when the pulse power measurement feature is enabled

• 0 is returned when the pulse power measurement feature is disabled

Query Example

CORR:GAIN3:STAT?

This command queries whether the pulse measurement feature is on or off.

Error Messages

• If [SENSe[1]]|SENSe2:CORRection:DCYCle:STATus is set to ON while


Conflict” occurs.

• If this command is used when an E4412A/E4413A power sensor is connected, the error –310, “System error;Dty Cyc may impair accuracy with ECP sensor” occurs. If you are using a dual channel power meter the error message specifies the channel.

• If this command is used when a E9320 power sensor is set to NORMal mode, the error –221, “Settings Conflict” occurs.

• If this command is used when a P- Series power sensor is connected, the error –241, “Settings Conflict” occurs.



[SENSe[1]]|SENSe2:CORRection:FDOFfset|GAIN4[:INPut][:MA

GNitude]?

This command is used to return the frequency dependent offset currently being applied.

SENS

Syntax

1 :

SENS2

CORR :GAIN4

:FDOFfset

:INP :MAG ?

Example

CORR:GAIN4?

This command queries the current frequency dependent offset being applied to Channel A.

Reset Condition

On reset, the frequency dependent offset is not affected.



[SENSe[1]]|SENSe2:CORRection:GAIN2 Commands

These commands provide a simple correction to a measurement for an external gain/loss.


[SENSe[1]]|SENSe2:CORRection:GAIN2:STATe <boolean>

[SENSe[1]]|SENSe2:CORRection:GAIN2[:INPut][:MAGNitude]

<numeric_value>



[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

SENS 1

SENS2

: CORR :GAIN2 :STAT Space

?

0|OFF

1|ON

Example

CORR:GAIN2:STAT ON This command enables a channel offset on

Channel A.

Reset Condition

On reset, channel offsets are disabled.



Query

[SENSe[1]]|SENSe2:CORRection:GAIN2:STATe?

The query enters 1 or 0 into the output buffer indicating the status of the channel offsets.

• 1 is returned if a channel offset is enabled

• 0 is returned if a channel offset is disabled

Query Example

CORR:GAIN2:STAT?

This command queries whether or not there is a channel offset applied to

Channel A.

Error Messages

If [SENSe[1]]|SENSe2:CORRection:GAIN2:STATe is set to ON while


Conflict” occurs.



[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.

Syntax

SENS 1

SENS2

: CORR :GAIN2 :INP :MAGN

Space

?

numeric_value

DEF

MIN

MAX

Space MIN

MAX



Parameters

Item numeric_value


A numeric value:

• DEF : the default is 0.00 dB

• MIN : –100 dB

• MAX : +100 dB

Example

CORR:GAIN2 50

Range of Values

–100 to +100 dB

DEF

MIN

MAX

This command sets a channel offset of

50 dB for Channel A.

Reset Condition

On reset, GAIN2 is set to 0.00 dB.

Query

[SENSe[1]]|SENSe2:CORRection:GAIN2[:INPut][:MAGNitude]?

[MIN|MAX]

The query returns the current setting of the channel offset or the values associated with MIN and MAX.



Query Example

CORR:GAIN2?

This command queries the current setting of 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


Conflict” occurs. However, the correction value is set but the

[SENSe[1]]|SENSe2:CORRection:GAIN2:STATe command is not automatically set ON.

• The SENSe[1]]|SENSe2:CORRection:GAIN2[:INPut][:MAGNitude] command can be used for the 8480 Series power sensor when no sensor calibration table has been set up.



[SENSe[1]]|SENSe2:DETector:FUNCtion <character_data>

This command sets the measurement mode for the E9320 and N1920 sensor either to average or peak sensor mode.

Syntax

SENS 1

SENS2

: DET : FUNC Space character_data

?

410

Parameters

Item character_data


Defines the measurement mode:

• AVERage : sets the E9320 and P-Series sensor to average only mode.

• NORMal : sets the E9320 and P-Series sensor to normal mode.

Range of Values

AVERage

1

NORMal

2

1

When measurement mode is set to average:

• If TRIG:SOUR is set to INT1, INT2 or EXT, it is set automatically to IMM.

• INIT:CONT is set automatically to ON.

• SENS:AVER2:STAT is set automatically to OFF.

• CALC:FEED is set automatically to “POW:AVG” for all CALC blocks using the specified channel in their CALC:MATH:EXPR.

2

When measurement mode is set to NORMal:

SENS:CORR:DCYC:STAT is set automatically to OFF.



Example

SENS1:DET:FUNC NORM This command sets the sensor to peak mode for Channel A.

Reset Condition

On reset, the mode is set to NORMal .

Query

[SENSe[1]]|SENSe2:DETector:FUNCtion?

The query returns the current sensor mode setting.

Query Example

SENS:DET:FUNC?

This command queries the current sensor mode setting for Channel A.

Error Messages

• If the command is used when a non E9320 or N1920 sensor is connected, the error –241, “Hardware missing” occurs.



[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. For P- Series and

E- Series power sensor, the appropriate corrections are applied for the frequency selected, dependant on the calibration data stored in the sensor’s EEPROM.

Syntax

SENS 1

SENS2

: FREQ :CW

:FIX

Space

?

numeric_value

DEF

MIN

MAX

Space MIN

MAX



Parameters

Item numeric_value


A numeric value for the frequency:

• DEF : the default value is 50 MHz

• MIN : 1 kHz

• MAX : 1000.0 GHz

The default units are Hz.

1


• Hz

• kHz (10

3

)

• MHz (10

6

)

• GHz (10

9

)

Example

FREQ 500kHz

Range of Values

1 kHz to 1000.0 Ghz

1

DEF

MIN

MAX

This command enters a Channel A

frequency of 500 kHz.

Reset Condition

On reset, the frequency is set to 50 MHz (DEF).

Query

[SENSe[1]]|SENSe2:FREQuency[:CW|:FIXed]? [MIN|MAX]

The query returns the current frequency setting or the values associated with MIN and MAX. The units in which the results are returned are Hz.



Query Example

SENS2:FREQ?

This command queries the Channel B frequency setting.



[SENSe[1]]|SENSe2:FREQuency[:CW|:FIXed]:STARt

<numeric_value>

This command sets the start frequency of average or peak frequency sweep. It must be used in conjunction with external trigger.

If frequency sweep is disabled (frequency sweep step set to 0), start frequency will be set but will not take effect.

N O T E

This command is only applicable when used with E4410, N8480 (excluding Option CFT),

E9300. E9320 or N1920 sensor.

N O T E

SENS:FREQ:STAR , SENS:FREQ:STOP and SENS:FREQ:STEP are allowed to be set in any desirable sequence.

When frequency sweep mode is configured with frequency step size within its allowable range, 1 to 2048, the following applies:

• If frequency stop point is greater than frequency start point, the frequency range will be swept in an ascending order.

• If frequency stop point is less than frequency start point, the frequency range will be swept in a descending order.

• If frequency stop point and frequency start point are equal, it is the same as power sweep mode.



SENS

SENS2

1

Syntax

: FREQ :CW

:FIX

:STAR Space

?

numeric_value

DEF

MIN

MAX

Space MIN

MAX

Parameters

Item numeric_value

Description

A numeric value for the start frequency:


• MIN : 1 kHz

• MAX : 1000.0 GHz


Range of Values

1 kHz to 1000.0 Ghz

1

DEF

MIN

MAX

1


• Hz

• kHz (10

3

)

• MHz (10

6

)

• GHz (10

9

)


Example

FREQ:STAR 1 MHz


This command sets frequency sweep to start at 1 MHz for Channel A.

Query

[SENSe[1]]|SENSe2:FREQuency[:CW|:FIXed]:STARt?

This query is used to retrieve start frequency (average or peak).

Frequency returned is in Hz.

Query Example

FREQ:STAR?

This query returns the start frequency of frequency sweep in Hz for Channel A.

On Reset

On *RST, the value is set to 50 MHz.

Error Messages



• If parameter set is lower than 1 kHz, error –222, “Data out of range; value clipped to lower limit” occurs.

• If parameter set is higher than 1000 GHz, error –222, “Data out of range; value clipped to upper limit” occurs.



[SENSe[1]]|SENSe2:FREQuency[:CW|:FIXEd]:STEP

<numeric_value>

This command sets the number of steps in average or peak frequency sweep. It must be used in conjunction with external trigger.

The frequency sweep range will be equally divided by the frequency step.

If trace display is turned on, the measurement window will be restored to single numeric or analog depends on the number of measurement channel.

N O T E

Determine the Right Step to be Set

Number of frequency step can be calculated using equation below:

Step = f stop

– f start

+ Interval

Interval where,

Step = Number of frequency step f start

= Frequency sweep’s start point f stop

= Frequency sweep’s stop point

Interval = Frequency step size

Example

When f start

= 1 GHz and f stop

= 5 GHz with given interval of 0.5 GHz, the Step should be set to

Step = f stop

– f start

+ Interval

Interval

= 5 GHz – 1 GHz + 0.5 GHz

0.5 GHz

= 9



N O T E

N O T E

This command is only applicable when used with E4410, N8480 (excluding Option CFT),

E9300, E9320 or N1920 sensor.


Frequency step size calculated will be rounded to the nearest kHz with the minimum size of

1 kHz. When frequency range is less than frequency sweep step, the remaining steps will be repeated with the last frequency point.

SENS

SENS2

1

Syntax

: FREQ :CW

:FIX

:STEP Space

?

numeric_value

DEF

MIN

MAX

Space MIN

MAX

Parameters

Item numeric_value

Description

A numeric value for number of step in the average trigger frequency sweep:

• DEF : the default value is 0

• MIN : 0

• MAX : 2048

Range of Values

0 to 2048

DEF

MIN

MAX



Example

FREQ:STEP 10 This command sets frequency sweep with

10 steps for Channel A.

Query

[SENSe[1]]|SENSe2:FREQuency[:CW|:FIXed]:STEP?

This query is used to retrieve the number of steps in average or peak frequency sweep.

Query Example

FREQ:STEP?

This query returns the number of steps in frequency sweep for Channel A.

On Reset

On *RST, the value is set to 0.

Error Messages



• If E4410, N8480 (excluding Option CFT), E9300, E9320 or N1920 sensor is connected but acquisition mode is in free run, error –221, “Setting conflict. Invalid acquisition mode” occurs.

• If parameter set is lower than 0, error –222, “Data out of range; value clipped to lower limit” occurs.



• If parameter set is higher than 2048, error –222, “Data out of range; value clipped to upper limit” occurs.



[SENSe[1]]|SENSe2:FREQuency[:CW|:FIXed]:STOP

<numeric_value>

This command sets the stop frequency of average or peak frequency sweep. It must be used in conjunction with external trigger.

If frequency sweep is disabled (frequency sweep step set to 0), stop frequency will be set but will not take effect.

N O T E

This command is only applicable when used with E4410, N8480 (exclduing Option CFT),

E9300, E9320 or N1920 sensor.

N O T E


When frequency sweep mode is configured with frequency step size within its allowable range, 1 to 2048, the following applies:

• If frequency stop point is greater than frequency start point, the frequency range will be sweep in an ascending order.

• If frequency stop point is less than frequency start point, the frequency range will be sweep in a descending order.

• If frequency stop point and frequency start point are equal, it is the same as power sweep mode.



SENS

SENS2

1

Syntax

: FREQ :CW

:FIX

:STOP Space

?

numeric_value

DEF

MIN

MAX

Space MIN

MAX

Parameters

Item numeric_value

Description

A numeric value for stop frequency:


• MIN : 1 kHz

• MAX : 1000.0 GHz


1


• Hz

• kHz (10

3

)

• MHz (10

6

)

• GHz (10

9

)

Range of Values

1 kHz to 1000.0 GHz

1

DEF

MIN

MAX



Example

FREQ:STOP 1MHz This command sets frequency sweep to stop at 1 MHz for Channel A.

Query

[SENSe[1]]|SENSe2:FREQuency[:CW|:FIXed]:STOP?

This query is used to retrieve stop frequency of the average or peak frequency sweep. Frequency returned is in Hz.

Query Example

FREQ:STOP?

This query returns the stop frequency of frequency sweep in Hz for Channel A.

On Reset

On *RST, the value is set to 50 MHz.

Error Messages



• If parameter set is lower than 1 kHz, error –222, “Data out of range; value clipped to lower limit” occurs.

• If parameter set is higher than 1000 GHz, error –222, “Data out of range; value clipped to upper limit” occurs.



[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

[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

CALCulate2|4:MATH:EXPRession

Status

OFF

1

OFF

1

OFF

1

OFF

2

OFF

2

“(SENSe1)”

“(SENSe2)”

3

1

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.

2

This change occurs when either channel is set to FAST. When both channels are changed from

FAST to NORMal or DOUBle, the settings that were in place when FAST was entered are restored.

3

Applicable to the N1912A dual channel power meter only.



Syntax

SENS

SENS2

1 : MRAT Space numeric_value

?

426

Parameters

Item character_data


A numeric value for the measurement speed:

• NORMal : 20 readings/second

• DOUBle : 40 readings/second

• FAST: up to 1000 readings/second

The default is NORMal.

Range of Values

NORMal

1

DOUBle

1

FAST

1

When a channel is set to NORMal or DOUBle, TRIG:COUNt is set automatically to 1.

Example

MRAT DOUBle This command sets the Channel A speed to

40 readings/second.

Reset Condition

On reset, the speed is set to NORMal.



Query

[SENSe[1]]|SENSe2:MRAT?

The query returns the current speed setting, either NORMal, DOUBle or

FAST .

Query Example

MRAT?

This command queries the current speed 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> is set to FAST, error –241 “Hardware missing” occurs.



[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.

Syntax

SENS 1

SENS2

: POW :AC :RANG Space

?

numeric_value

428

Example

POW:AC:RANG 0 This command sets the power sensor to it’s lower range.

Reset Condition

On reset, the upper range is selected.

Query

[SENSe[1]]|SENSe2:POWer:AC:RANGe?

The query enters a 1 or 0 into the output buffer indicating the status of the power sensor’s range.



• 1 is returned when the upper range is selected

• 0 is returned when the lower range is selected

Query Example

POW:AC:RANG?

This command queries the current setting of the power sensor range.

N O T E

Error Messages

This command is used with the E- Series power sensor. If one is not connected the error –241, “Hardware missing” occurs.

For E-Series power sensor (E9320), the auto ranging feature will be disabled when normal and trigger modes are selected.



[SENSe[1]]|SENSe2:POWer:AC:RANGe:AUTO <boolean>

This command is only valid when used with an E- Series power sensor or

N8480 Series power sensor (excluding Option CFT). 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.

The [SENSe[1]]|SENSe2:POWer:AC:RANGe command disables autoranging.

If INITiate:CONTinuous is set to ON and TRIGger:SOURce is set to

IMMediate , the range tracks the input power if

[SENSe[1]]|SENSe2:POWer:AC:RANGe:AUTO is ON.

If the power meter is not making measurements then autoranging only occurs when the power meter is triggered.

N O T E

For E9320 power sensor, only UPPER and LOWER ranges are available in Normal and

Triggered modes.

SENS

Syntax

1 :

SENS2

POW :AC :RANG :AUTO Space 0|OFF

?

1|ON

Example

POW:AC:RANG:AUTO 0 This command disables autoranging.



Reset Condition

On reset, autoranging is enabled.

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

POW:AC:RANG:AUTO?

This command queries whether auto ranging is on or off.

Error Messages

• If this command is set to OFF when there is not an E- Series power sensor or N8480 Series power sensor (excluding Option CFT) connected, the error –241, “Hardware missing” occurs.

• If this command is set to ON when E9320 power sensor is in Normal and Triggered modes, the error - 221, “Setting conflicts” occurs.



[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

With no trace: internally calculated time

Pre-

Trigger

With no trace: internally calculated time

Time gate length:

SENSe:SWEep:TIME

432

N O T E

Incoming signal from sensor

Trigger

Delay

TRIG:DEL

Trigger

Point

Defined using:

TRIG:LEVel

TRIG:SLOPe

TRIG:HYSTeresis

Delayed

Trigger

Point

Offset time:

SENSe:SWEep:OFFSet:TIME

Data Collection Time

Offset time and time gate length values can be set for up to four measurement gates per channel. Measurement gate number is defined by the numeric value following the SWEep component of the command.

These commands can only be used with P-Series and E9320 sensors. The E9320 sensor must be set to NORMal mode.


[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:SWEep[1]|2|3|4:AUTO

<character_data>

This command is used to trigger Auto Gating and turning on or off the

Perpetual Gating for the selected gate.

N O T E

This command is only applicable when N192x or E932x sensor is present and trigger acquisition mode is selected.

Syntax

SENS

SENS2

1 : SWE 1

2

3

4

:AUTO Space OFF

ON

ONCE

?

Parameters

Item character_data


The status of Auto Gating and Perpetual

Gating.

ONCE: To turn on Auto Gating

ON/OFF: To turn on/off Perpetual Gating

Range of Values

OFF

ON

ONCE



Example

SENS:SWE2:AUTO ON

SENS2:SWE3:AUTO OFF

SENS2:SWE4:AUTO ONCE

This command turns on Channel A Gate 2

Perpetual Gating.

This command turns off Channel B Gate 3

Perpetual Gating.

This command triggers Auto Gating for

Channel B Gate 4.

Reset Condition

On reset, Perpetual Gating will be disabled.

Query

[SENSe[1]]|SENSe2:SWEep[1]|2|3|4:AUTO?

The query returns the current setting of perpetual gating(0 or 1).

• 1 is returned if the perpetual gating is turned on

• 0 is returned if the perpetual gating is turned off

Query Example

SENS2:SWE:AUTO?

The query returns the current setting of

Perpetual Gating for Gate 1 Channel B.



Error Messages



• If channel is not in trigger acquisition mode, error –221 "Settings conflict" occurs.

• If Auto Gate fails, error –221 "Settings conflict; Auto Once failed" occurs.



[SENSe[1]]|SENSe2:SWEep[1]|2|3|4:AUTO:REF1|REF2

<numeric_value>

This command is used to set the Reference 1 and 2 of the selected gate for Auto Gating Marker.

N O T E


SENS

SENS2

1

Syntax

: SWE 1

2

3

4

:AUTO :REF1

:REF2

Space numeric_value

?

Parameters

Item numeric_value


The values of Auto Gating Marker References 1 and 2 for the selected gate.

The combined value of REF1 and REF2 can not exceed 99.9 %.

Range of Values

0.0 to 99.9



Example

SENS1:SWE1:AUTO:REF1 10.0

This command sets the Channel A Auto

Gating Marker Reference 1 to 10 % for

Gate 1.

SENS2:SWE2:AUTO:REF2 40.0

This command sets the Channel B Auto

Gating Marker Reference 2 to 40% for

Gate 2.

Query

[SENSe[1]]|SENSe2:SWEep[1]|2|3|4:AUTO:REF1|REF2?

The query returns the current setting of Auto Gating Marker Reference 1 or 2 for the selected gate in numerical value.

Query Example

SENS1:SWE2:AUTO:REF1?

The query returns the current Gate 2

Reference 1 value of Auto Gating Marker.

Error Messages




• If limits of the values keyed in are exceeded, error –222 "Data out of range; upper (or lower) limit exceeded; no change" occurs.



[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 or a

E9320 sensors set to NORMal mode. To set an E9320 sensor to NORMal

mode, refer to the command “[SENSe[1]]|SENSe2:DETector:FUNCtion

<character_data>” on page 410.

Syntax

SENS 1 : SWE

SENS2

1

2

3

4

:OFFS :TIME Space numeric_value

DEF

?

Parameters

Item numeric_value


The delay between the trigger point and the start of the time-gated period.

• DEF : the default value is 0 seconds

Units are resolved to 1 ns.

Range of Values

–1 to 1 second

DEF



Example

SENS2:SWE3:OFFS:TIME 0.001

This command sets the delay to 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.

Query Example

SENS2:SWE2:OFFS:TIME?

The query returns the current delay between the trigger point and the start of the time- gated period for Channel B and gate 2.

Error Messages

If the command is used when a sensor other than a P- Series or E9320 power sensor is connected, error –241, “Hardware missing” occurs



Conflict” occurs.



[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 and E9320 sensors which are set to NORMal mode. To set an E9320 sensor to NORMal mode, refer to the command

“[SENSe[1]]|SENSe2:DETector:FUNCtion


Syntax

SENS

SENS2

1 : SWE 1

2

3

4

: TIME Space numeric_value

DEF

?

Parameters

Item numeric_value


The length of the time gated period in seconds.

• DEF : the default value is 100 µs


Range of Values

0 to 1 second

DEF

Example

SENS2:SWE3:TIME 0.001

This command sets the length to 0.001 seconds.



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

SENS2:SWE2:TIME?

This command queries the length of the time- gated period for Channel B and gate

2.

Error Messages


• If the command is used when an E9320 sensor is connected and set to


Conflict” occurs.



[SENSe[1]]|SENSe2:TEMPerature?

This this command to returns the P- Series power sensor's temperature in degrees Celsius.

Syntax

SENS

SENS2

1 : : TEMP ?

Parameters

Item numeric_value


A numeric value defining sensor's temperature in degrees Celsius.

Range of Values

–50 to 100

Example

SENS2:TEMP?

This command returns the current sensor temperature found on Channel B.

Reset Condition

On reset, this parameter is not affected.



Error Messages

• If a P- Series sensor is not connected, error –241, “Hardware missing” occurs.



[SENSe[1]]|SENSe2:TRACe Commands

N O T E

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

• The trace units.

These commands can only be used with P-Series and E9320 sensors. The E9320 sensor must be set to NORMal mode.


[SENSe[1]]|SENSe2:TRACe:LIMit:LOWer <numeric_value>

[SENSe[1]]|SENSe2:TRACe:LIMit:UPPer <numeric_value>

[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:TRACe:OFFSet:TIME <numeric_value>

This command sets the delay between the delayed trigger point and the start of the trace for P- Series or E9320 sensors are set to NORMal mode.

To set an E9320 sensor to NORMal mode, refer to the command

“[SENSe[1]]|SENSe2:DETector:FUNCtion <character_data>” on page 410.

Syntax

SENS 1 : TRAC :OFFS

SENS2

:TIME Space numeric_value

DEF

?

Parameters

Item numeric_value


The length of the delay in seconds.



Range of Values

–1 to 1 second

DEF

Example

SENS:TRAC:OFFS:TIME 0.05

This command sets the delay to 0.05 seconds.



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

SENS:TRAC:OFFS:TIME?

This command queries the current delay between the delayed trigger point and the start of the trace for Channel A.

Error Messages


•



Conflict” occurs.



[SENSe[1]]|SENSe2:TRACe:TIME <numeric_value>

This command sets the duration of the trace for a P- Series sensor and a

E9320 sensors set to NORMal mode. To set the E9320 sensor to NORMal

mode, refer to the command “[SENSe[1]]|SENSe2:DETector:FUNCtion


Syntax

SENS

SENS2

1 : TRAC :TIME Space numeric_value

DEF

?

Parameters

Item numeric_value


The duration of the trace in seconds.

• DEF : the default value is 100 µs.


Example

SENS2:TRAC:TIME 0.5

Range of Values

20 ns to 1 s

DEF

This command sets the duration of the trace to 0.5 seconds for Channel B.



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

SENS2:TRAC:TIME?

This command queries the current duration of the trace.

Error Messages


•



Conflict” occurs.



[SENSe[1]]|SENSe2:TRACe:UNIT <character_data>

This command sets the units for the trace for the specified channel.

Syntax

SENS 1

2

:TRAC :UNIT Space character_data

?

Parameters

Item character_data


• DBM: dBm

• W: Watts

Range of Values

DBM

W

Example

SENS2:TRAC:UNIT W This command sets the trace units for

Channel B to Watts.

Reset Condition

On reset the units are set to dBm.



Query

[SENSe[1]]|SENSe2:TRACe:UNIT?

The query command returns the current value of character_data.

Query Example

SENS2:TRAC:UNIT?

This command queries the current trace units for Channel B.



[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, D type (diode) correction is selected and the automatic selection must be overridden.

This command is only applicable for V8486A and W8486A sensors.

N O T E

Syntax

SENS

SENS2

1 : V2P Space

?

ATYP

DTYP

Example

SENS2:V2P DTYP This command selects the D type linearity correction to be applied to Channel B.

Reset Condition

On reset, the linearity correction is set for A type.



Query

[SENSe[1]]|SENSe2:V2P?

The query returns the current type of linearity correction being displayed on the screen.

Query Example

SENS:V2P?

This command queries which linearity 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,




SENSe[1]|2:TRACe:AUToscale

This command will automatically scale the trace capture to between 50 % to 100 % of the Y scale (power axis) and between 20 % to 50 % of the X scale (time axis) with the triggering edge aligned to the center of the trace.

N O T E

This feature will only work with modulated signal exceeding –15 dBm in amplitude. Most of the pulse and amplitude modulated signals are autoscalable. Upon successful autoscaling, trigger parameters such as trigger source, trigger mode, trigger level, trigger delay and trigger holdoff as well as default gate 1 parameters will be overwritten by this function. If autoscaling is performed on a slave cross-triggered channel, the targeted channel will be automatically changed to master. It will also turn on the continuous triggering mode upon completion. Perpetual gating function will also be disabled after autoscaling.

N O T E


Syntax

SENS

2

1 :TRAC

AUT



Example

SENS:TRAC:AUT

SENS2:TRAC:AUT

This command triggers the Auto Scaling for Channel A.

This command triggers the Auto Scaling for Channel B.

Reset Condition

On reset, X Start = 0 s, X Scale = 10 ms, Y Max = 20 dBm, Y Scale = 7 dB.

Error Messages






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 in Table 10- 23 .

Table 10-23Measurement Units

Units:

SENS:TRAC:UNIT dBm

W

Units:

SENS:TRAC:LIM:LOW dBm

W

N O T E

The trace lower scale limit is maintained at a lower power than the upper scale limit which is adjusted to be slightly greater than the lower scale limit if necessary. Refer to

“SENSe[1]|2:TRACe:LIMit:UPPer <numeric_value>” on page 458 for further information

on setting the trace upper scale limit.

:SENS

Syntax

1

2

:TRAC :LIM :LOW Space

?

numeric_value

DEF

MIN

MAX

Space MIN

MAX



Parameters

Item numeric_value


A numeric value for the trace lower scale limit.


• MIN : –150 dBm

• MAX : 230 dBm

Range of Values

–150 to 230 dBm

DEF

MIN

MAX

Example

SENS2:TRAC:LIM:LOW 10 This command sets the trace lower scale limit to 10 dBm for Channel B.

Reset Condition

On reset, the value is set to –50 dBm.

Query

SENSe[1]|2:TRACe:LIMit:LOWer [MIN|MAX]

The query returns the current setting of the trace lower scale limit or the value associated with MIN or MAX. The format of the response is <NR3>.



Query Example

SENSe:TRAC:LIM:LOW?

This command queries the trace lower scale limit of Channel A.



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 in

Table 10- 24

.

Table 10-24Measurement Units

Units:

SENS:TRAC:UNIT dBm

W

Units:

SENS:TRAC:LIM:UPP dBm

W

N O T E

The trace lower scale limit is maintained at a lower power than the upper scale limit which is adjusted to be slightly greater than the lower scale limit if necessary. Refer to

“SENSe[1]|2:TRACe:LIMit:LOWer <numeric_value>” on page 455 for further information

on setting the trace lower scale limit.

:SENS

Syntax

1

2

:TRAC :LIM :UPP Space

?

numeric_value

DEF

MIN

MAX

Space MIN

MAX



Parameters

Item numeric_value


A numeric value for the trace lower scale limit.


• MIN : –150 dBm

• MAX : 230 dBm

Range of Values

–150 to 230 dBm

DEF

MIN

MAX

Example

SENS:TRAC:LIM:UPP 100 This command sets the trace upper scale limit to 100 dBm for Channel A.

Reset Condition

On reset, the value is set to DEF.

Query

SENSe[1]|2:TRACe:LIMit:LOWer [MIN|MAX]

The query returns the current setting of the trace upper scale limit or the value associated with MIN or MAX. The format of the response is <NR3>.



Query Example

SENS:TRAC:LIM:UPP?

This command queries the trace upper scale limit of Channel A.



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.

N O T E


SENS

Syntax

1 :TRAC

2

:X :SCAL

:PDIV Space numeric_value

?

Parameters

Item numeric_value


The numeric value for X-axis scale.

Range of Values

2 ns to 0.1 s

Example

SENS:TRAC:X:SCAL:PDIV 0.02

This command sets the X Scale value of

Channel A to 0.02 step.

SENS2:TRAC:X:SCAL:PDIV

0.05

This command sets the X Scale value of

Channel B to 0.05 step.



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

SENS:TRAC:X:SCAL:PDIV?

This command queries the Channel A current X- axis scale setting in numerical value.

Error Messages







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.

N O T E


SENS

Syntax

1 :TRAC

2

:Y :SCAL :PDIV Space numeric_value

?

Parameters

Item numeric_value


The numeric value for Y-axis scale.

Range of Values

0.001 dB to10 dB

1 nWatt to10 MWatt



Example

SENS:TRAC:Y:SCAL:PDIV

0.002

SENS2:TRAC:Y:SCAL:PDIV

0.05

This command sets the Channel A Y Scale value to 0.002 step.

This command sets the Channel B Y Scale value to 0.05 step.

464

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.

Query Example

SENS:TRAC:Y:SCAL:PDIV?

This command queries the Channel A current Y- axis scale setting in numerical value.

Error Messages








11


STATus Subsystem 466

Status Register Set Commands 468

Device Status Register Sets 473

Operation Register Sets 475

STATus:OPERation 476

STATus:OPERation:CALibrating[:SUMMary] 477

STATus:OPERation:LLFail[:SUMMary] 478

STATus:OPERation:MEASuring[:SUMMary] 479

STATus:OPERation:SENSe[:SUMMary] 480

STATus:OPERation:TRIGger[:SUMMary] 481

STATus:OPERation:ULFail[:SUMMary] 482

STATus:PRESet 483

Questionable Register Sets 484

STATus:QUEStionable 485

STATus:QUEStionable:CALibration[:SUMMary] 486

STATus:QUEStionable:POWer[:SUMMary] 487

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” and the “Questionable Status

Register”.


465

11 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.

Table 11- 25

summarizes the effects of various commands and events on these status registers:

Table 11-25Commands and events affecting Status Register

Status Register

SCPI Transition Filters (NTR and PTR registers)

SCPI Enable Registers

SCPI Event Registers

SCPI Error/Event Queue enable

SCPI Error/Event Queue

IEEE488.2 Registers ESE SRE

IEEE488.2 Registers SESR STB

*RST none none none none none none none

*CLS none none clear none clear none clear

Power On STATus:

PRESet preset preset clear preset clear clear clear preset preset none preset none none none

The contents of the status registers are examined using the following status register set commands:

:CONDition?

:ENABle <NRf>|<non-decimal numeric>

[:EVENt?]

:NTRansition <NRf>|<non-decimal numeric>

:PTRansition <NRf>|<non-decimal numeric>

Each of these can be used to examine any of the following eleven status registers:


STATus Subsystem 11

STATus:DEVice (

page 473

)

STATus:OPERation

( page 476 )

STATus:OPERation:CALibrating[:SUMMary] (

page 477

)

STATus:OPERation:LLFail[:SUMMary] (

page 478

)

STATus:OPERation:MEASuring[:SUMMary]

( page 479

)

STATus:OPERation:SENSe[:SUMMary] (

page 480 )

STATus:OPERation:TRIGger[:SUMMary]

( page 481 )

STATus:OPERation:ULFail[:SUMMary] (

page 482

)

STATus:PRESet (

page 483

)

STATus:QUEStionable

( page 485 )

STATus:QUEStionable:CALibration[:SUMMary] (

page 486

)

STATus:QUEStionable:POWer[:SUMMary] (

page 487

)

Examples

• To use the :CONDition? command to examine the STATus:DEVice register:

STATus:DEVice:CONDition?

• To use the :NTRansition command to examine the

STATus:OPERation:SENSe[:SUMMary] register:

STATus:OPERation:SENSe[:SUMMary]:NTRansition

This chapter describes the status register set commands and the status registers which they are used to examine.



Status Register Set Commands

Keyword

:CONDition?

:ENABle

[:EVENt?]

:NTRansition

:PTRansition

This section describes the five status register set commands. Each can be

used to examine all of the eleven status registers listed on page 467

.

To apply a command to a specific register, prefix the command with the name of the appropriate register. For example, to apply the :ENABle command to the STATus:QUEStionable register, use the following command:

STATus:QUEStionable:ENABle

The Status Register Set commands detailed in this section are:

Parameter Form

<NRf>|<non-decimal numeric>



Notes

[query only]

[query only]

Page

page 468

page 469 page 469

page 470

page 471

:CONDition?

This query returns a 16 bit decimal- weighted number representing the bits set in the Condition 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

15

–1). The contents of the Condition Register remain unchanged after it is read.

Syntax

:COND ?



N O T E

[: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

15

–1). This query clears all bits in the register to 0.

The [:EVENt]? is the default command if the STATus SCPI are not accompanied by any of the Status Register Set commands (:COND, :ENAB, :NTR and :PTR).

Syntax

:EVEN ?

:ENABle <NRf>|<non-decimal numeric>

This command sets the Enable Register of the particular SCPI Register Set you require to control. The parameter value, when rounded to an integer and expressed in base 2 has its first 15 bits written into the Enable

Register of the SCPI Register Set concerned. The last bit (bit 15) is always set to 0.

Syntax

:ENAB space NRf

?

non-decimal numeric



Parameters

Type

NRf non-decimal numeric

Description

The value used to set the

Enable Register.

Range of Values

0 to 2

16

–1

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> in the range of 0 to 32767 (2

15

–1).

:NTRansition <NRf>|<non-decimal numeric>

This command sets the Negative Transition Register of the SCPI Register

Set you require to control. The parameter value, when rounded to an integer and expressed in base 2 has its first 15 bits written into the

Negative Transition Register of the SCPI Register Set concerned. The last bit (bit 15) is always set to 0.



Syntax

:NTR space

?


Parameters

Type


Description

The value used to set the NTR

Register.

Range of Values

0 to 2

16

–1

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. The format of the return is <NR1> in the range of 0 to 32767

(2

15

–1).

:PTRansition <NRf>|<non-decimal numeric>

This command is used to set the Positive Transition Register of the SCPI

Register Set you require to control. The first 15 bits of the input parameter are written into the Positive Transition Register of the SCPI

Register Set concerned. The last bit (bit 15) is always set to 0.



Syntax

:PTR space

?


Parameters

Type


Description

The value used to set the

PTR Register.

Range of Values

0 to 2

16

–1

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. The format of the return is <NR1> in the range of 0 to 32767

(2

15

–1).



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.

The one device status register set is:

STATus:DEVice:



Weight

0

1

2

3

4

7-15

14

15

-

2

4

-

8

16

-

16384

Definition

Not used


Channel B sensor connected (N1912A only)

Channel A sensor error

Channel B sensor error (N1912A only)

Not used

Front Panel key press

Bit 15 always 0

The Channel A and B sensor connected bits (bits 1 and 2), when queried with the STATus:DEVice:CONDition? query are set to:

• 1, when a power sensor is connected

• 0, when no power sensor is connected

The Channel A and B sensor connected bits (bits 1 and 2), when queried with the STATus:DEVice:EVENt? query indicate whether a power sensor has been connected or disconnected depending on the state of the corresponding bits of STATus:DEVice:NTRansition and

STATus:DEVice:PTRansition . If the corresponding bit in:

• STATus:DEVice:NTRansition is 1, then STATus:DEVice:EVENt? is



N O T E 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.

The Channel A and B sensor error bits (3 and 4) are set to:

• 1, if the P- Series, N8480 Series or E- Series power sensor EEPROM has failed or if there are power sensors connected to both the rear and front panel connectors.

• 0, for every other condition.

The Front Panel key press bit (bit 14), when queried with the

STATus:DEVice:EVENt?

query indicates whether any front panel keys have been pressed since power up or since you last queried the device status register. This bit ignores the :NTRansition, and :PTRansition registers and a :CONDition? query always returns a 0.



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”

.

The following command descriptions detail the SCPI register you require to control but do not detail the Register Set commands.

The seven Operation Register Sets are:

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]

Further information on these register sets is provided on the following pages.



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 Definition

0

1 - 3

4

5

6 - 9

10

11

12

13 to 15

Decimal

Weight

1

-

16

-

32

1024

2048

-

4096

CALibrating Summary

Not used

MEASuring Summary

Waiting for TRIGger Summary

Not used

SENSe Summary

Lower Limit Fail Summary

Upper Limit Fail Summary

Not used (bit 15 always 0)

Syntax

STAT :OPER



STATus:OPERation:CALibrating[:SUMMary]

The operation status calibrating summary register set contains information on the calibrating status of the power meter.


Definition Bit Number Decimal

Weight

0

1

2

3-15

-

-

2

4

Not used

Channel A CALibrating Status

Channel B CALibrating Status (N1912A only)

Not used

These bits are set at the beginning of zeroing (CALibration:ZERO:AUTO

ONCE ) and at the beginning of calibration (CALibration:AUTO ONCE). Also for the compound command/query CALibration[:ALL]?, this bit is set at the beginning of the calibration sequence.

These bits are cleared at the end of zeroing or calibration.

Syntax

STAT :OPER :CAL :SUMM



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.


Definition Bit

Number

0

1

2

5

6

3

4

7-15

Decimal

Weight

8

16

32

64

-

-

2

4

Not used

Channel A LLFail Status

Channel B LLFail Status (N1912A only)

Upper window LLFail Status

Lower widow LLFail Status

Upper window lower measurement LLFail Status

Lower window lower measurement LLFail Status

Not used

The appropriate bits are set if a channel lower limit test fails or a window lower limit test fails.

These bits are cleared if a measurement is made and the test is enabled and passes.

Syntax

STAT :OPER :LLF :SUMM



STATus:OPERation:MEASuring[:SUMMary]

The operation status measuring summary register set contains information on the measuring status of the power meter.



Weight

0

1

2

3-15

-

-

2

4

Not used

Channel A MEASuring Status

Channel B MEASuring Status (N1912A only)

Not used

These bits are set when the power meter is taking a measurement.

These bits are cleared when the measurement is finished.

Syntax

STAT :OPER :MEAS :SUMM



STATus:OPERation:SENSe[:SUMMary]

The operation status sense summary register set contains information on the status of the power sensors.



Weight

0

1

2

3-15

-

-

2

4

Not used

Channel A SENSe Status

Channel B SENSe Status (N1912A only)

Not used

These bits are set when the power meter is reading data from the

E- Series power sensor or N8480 Series power sensor EEPROM.

These bits are cleared when the power meter is not reading data from the

E- Series power sensor or N8480 Series power sensor EEPROM.

Syntax

STAT :OPER :SENS :SUMM



STATus:OPERation:TRIGger[:SUMMary]

The operation status trigger summary register set contains information on the trigger status of the power meter.



Weight

0

1

2

3-15

-

-

2

4

Not used

Channel A TRIGger Status

Channel B TRIGger Status (N1912A only)

Not used

Syntax

STAT :OPER :TRIG :SUMM



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.


Definition Bit

Number

0

1

2

5

6

3

4

7-15

Decimal

Weight

-

8

16

32

64

-

2

4

Not used

Channel A ULFail Status

Channel B ULFail Status (N1912A only)

Upper window ULFail Status

Lower window ULFail Status

Upper window lower measurement LLFail Status

Lower window lower measurement LLFail Status

Not used

The appropriate bits are set if a channel upper limit test fails or a window upper limit test fails.

These bits are cleared if a measurement is made and the test is enabled and passes.

Syntax

STAT :OPER :ULF :SUMM



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

OPERational

QUEStionable

All Others

Filter/Enable

ENABle

PTR

NTR

ENABle

PTR

NTR

ENABle

PTR

NTR

PRESet Value all zeros all ones all zeros all zeros all ones all zeros all ones

all ones

all zeros

Syntax

STAT :PRES



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”

.

The following command descriptions detail the SCPI register you require to control but do not detail the register set commands.

The three questionable register sets are:

STATus:QUEStionable

STATus:QUEStionable:CALibration[:SUMMary]

STATus:QUEStionable:POWer[:SUMMary]



STATus:QUEStionable

The questionable register set contains bits that indicate the quality of various aspects of signals processed by the power meter.



Weight

0 to 2

3

4 to 7

8

9

10 to 15

-

-

8

-

256

512

Not used

POWer Summary

Not used

CALibration Summary

Power On Self Test

Not Used (bit 15 always 0)

Bit 3 is set by the logical OR outputs of the

STATus:QUEStionable:POWer:SUMMary register set.

Bit 8 is set by the logical OR outputs of the

STATus:QUEStionable:CALibration:SUMMary register set.

Bit 9 is set if power- on self- test fails, and cleared if it passes.

Syntax

STAT :QUES



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.


Definition Bit

Number

0

1

2

3-15

-

-

2

4

Decimal

Weight

Not used

Summary of Channel A CALibration

Summary of Channel B CALibration (N1912A only)

Not used

These bits are set by the following:

• Error –231, “Data questionable; CH<A|B>:ZERO ERROR”

• Error –231, “Data questionable; CAL ERROR”

• Error –231, “Data questionable; CAL ERROR ChA”

• Error –231, “Data questionable; CAL ERROR ChB”

These bits are cleared when any of the three commands listed above succeed and no errors are placed on the error queue.

Syntax

STAT :QUES :CAL :SUMM



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:

Definition

5

6

3

4

7

8

0

1

2


Weight

8

16

32

64

-

2

4

128

256

Not used

Channel A Power

Channel B Power (N1912A only)

Upper Window Power

Lower Window Power

Channel A Please Zero

Channel B Please Zero (N1912A only)

Upper Window Lower Measurement Power

Lower Window Lower Measurement Power

Bit 1 is set when any of the following errors occur:

• Error –231, “Data questionable;Input Overload”

• Error –231, “Data questionable;Input Overload ChA” (N1912A only)

Bit 2 is set when the following error occurs:

• Error –231, “Data questionable;Input Overload ChB” (N1912A only)

Bits 3 is set when the following error occurs:

• Error –230, “Data corrupt or stale”

• Error –231, “Data questionable;Upper window log error”

Bit 4 is set when the following error occurs:

• Error –230, “Data corrupt or stale”

• Error –231, “Data questionable;Lower window log error”

Bit 5 is set when the following condition occurs:



• Channel A requires zeroing

Bit 6 is set when the following condition occurs (N1912A only):

• 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

STAT :QUES :POW :SUMM



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







12


SYSTem Subsystem 492

SYSTem:COMMunicate:GPIB[:SELF]:ADDRess <numeric_value> 494

SYSTem:COMMunicate:LAN:AIP[:STATe] <boolean> 496


497


498


499


500

SYSTem:COMMunicate:LAN:ADDRess <character_data> 501

SYSTem:COMMunicate:LAN:DGATeway <character_data> 503

SYSTem:COMMunicate:LAN:DHCP[:STATe] <boolean> 505

SYSTem:COMMunicate:LAN:DNAMe <character_data> 506

SYSTem:COMMunicate:LAN:HNAMe <character_data> 508

SYSTem:COMMunicate:LAN:MAC?

510

SYSTem:COMMunicate:LAN:RESTart 511

SYSTem:COMMunicate:LAN:SMASk <character_data> 512

SYSTem:DISPlay:BMP 514

SYSTem:ERRor?

515

SYSTem:HELP:HEADers?

523

SYSTem:LOCal 525

SYSTem:PRESet <character_data> 526

SYSTem:REMote 605

SYSTem:RWLock 606

SYSTem:VERSion?

607

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 remote address, and query the SCPI version.


491

12 SYSTem Subsystem


The SYStem command subsystem is used to:

• Return error numbers and messages from the power meter

• Preset the power meter

• Set the GPIB address

• Set the LAN address

• Set the command language

• Query the SCPI version

Keyword

SYSTem

:COMMunicate

:GPIB

[:SELF]

:ADDRess

:LAN

:AIP

[:STATe]

:CURRent

:ADDRess?

:DGATeway?

:DNAMe?

:SMASk?

:ADDRess

:DGATeway

:DHCP

[:STATe]

:DNAMe

:HNAMe

:MAC?

Parameter Form

<numeric_value>

<boolean>

<character_data>

<character_data>

<boolean>

<character_data>

<character_data>

Notes

[query only]

[query only]

[query only]

[query only]

[query only]

Page

page 494

page 496

page 497

page 498

page 499

page 500

page 501

page 503

page 505

page 506

page 508

page 510


Keyword

:RESTart

:SMASk

:DISPLAY

:BMP?

:ERRor

:HELP

:HEADers?

:LOCal

:PRESet

:REMote

:RWLock

:VERSion?

SYSTem Subsystem 12

Parameter Form

<character_data>

Notes

[no query]

[query only] character_data

[query only]

[event; no query]

[query only]

Page

page 511

page 512

page 514

page 515

page 523

page 525

page 526

page 605

page 606

page 607



SYSTem:COMMunicate:GPIB[:SELF]:ADDRess

<numeric_value>

This command sets the GPIB address of the power meter.

Syntax

SYST :COMM :GPIB :SELF :ADDR Space

?

numeric_value

DEF

MIN

MAX

Space MIN

MAX

Parameters

Item numeric_value


A numeric value for the address.

• DEF: the default value is 13

• MIN: 0

• MAX: 30

Range of Values

0 to 30

DEF

MIN

MAX

Example

SYST:COMM:GPIB:ADDR 13 This command sets the GPIB address to

13.



Query

SYSTem:COMMunicate:GPIB[:SELF]:ADDRess? MIN|MAX

The query returns the current setting of the GPIB address or the values associated with MIN and MAX.

Query Example

SYST:COMM:GPIB:ADDR?

This command queries the setting of the

GPIB address.



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

SYST :COMM :LAN :AIP :STAT Space 0|OFF

?

1|ON

Example

SYST:COMM:LAN:AIP ON This command enables the AutoIP

Query

SYSTem:COMMunicate:LAN:AIP?

• 1 is returned if AutoIP is enabled

• 0 is returned if AutoIP is disabled

Query Example

SYST:COMM:LAN:AIP?


AutoIP.



SYSTem:COMMunicate:LAN:CURRent:ADDRess?

This command returns the current setting of the IP address in use by the power meter.

N O T E

If DHCP or AutoIP are enabled and successful, then one of these IP address modes assigns the IP address, otherwise it is the static IP address.

Syntax

SYST :COMM :LAN :CURR :ADDR ?

Example

SYST:COMM:LAN:CURR:ADDR?

This command queries the current setting of the IP address.



SYSTem:COMMunicate:LAN:CURRent:DGATeway?

This command returns the current setting of the LAN IP router/gateway address in use by the power meter.

N O T E

If DHCP or AutoIP are enabled and successful, then one of these IP address modes assigns the LAN IP router/gateway address, otherwise it is the static LAN IP router/gateway address

Syntax

SYST :COMM :LAN :CURR :DGAT ?

Example

SYST:COMM:LAN:CURR:DGAT?

This command queries the current setting of the LAN IP router/gateway address.



SYSTem:COMMunicate:LAN:CURRent:DNAMe?

This command returns the current setting of the LAN domain name in use by the power meter.

N O T E

If DHCP or AutoIP are successfully enabled, then one of these IP address modes assign the

LAN domain name, otherwise it is the static LAN domain name.

Syntax

SYST :COMM :LAN :CURR :DNAM ?

Example

SYST:COMM:LAN:CURR:DNAM?

This command queries the current setting of the LAN domain name.



SYSTem:COMMunicate:LAN:CURRent:SMASk?

This command returns the current setting of the LAN subnet mask in use by the power meter.

N O T E

If DHCP or AutoIP are successfully enabled, then one of these IP address modes assign the

LAN subnet mask, otherwise it is the static LAN subnet mask.

Syntax

SYST :COMM :LAN :CURR :SMAS ?

Example

SYST:COMM:LAN:CURR:SMAS?

This command queries the current setting of the LAN subnet mask.



SYSTem:COMMunicate:LAN:ADDRess <character_data>

This command sets the LAN (IP) address of the power meter.

Syntax

SYST :COMM :LAN :ADDR Space

?

character_data

Parameters

Item character_data

Description

Numeric character values for the address.

Up to 15 characters, formatted as follows:

A.B.C.D where A, B, C, D = 0 to 255

Range of Values

0 to 255 (no embedded spaces)

Example

SYST:COMM:LAN:ADDR

‘130.015.156.255’

This command sets the LAN IP address to

130.015.156.255.

Query

SYSTem:COMMunicate:LAN:ADDRess?

The query returns the current setting of the LAN address.



Query Example

SYST:COMM:LAN:ADDR?


LAN IP address.

Remark

If the paramater value is more than 255, error –232 “Invalid format" occurs.



SYSTem:COMMunicate:LAN:DGATeway <character_data>

This command sets the LAN IP router/gateway address for the power meter.

Syntax

SYST :COMM :LAN :DGAT

Space character_data

?

Parameters

Item character_data

Description




Range of Values


Example

SYST:COMM:LAN:DGAT

‘130.2.6.200’

This command sets the gateway address to

130.2.6.200.

Query

SYSTem:COMMunicate:LAN:DGAT?

The query returns the current setting of the LAN gateway address.



Query Example

SYST:COMM:LAN:DGAT?

This command queries the setting of the gateway address.

Remark



SYSTem:COMMunicate:LAN:DHCP[:STATe] <boolean>

This command enables the dynamic host configuration protocol.

Syntax

SYST :COMM :LAN :DHCP :STAT Space 0|OFF

?

1|ON

Example

SYST:COMM:LAN:DHCP ON This command enables the DHCP.

Query

SYSTem:COMMunicate:LAN:DHCP?

• 1 is returned if DHCP is enabled

• 0 is returned if DHCP is disabled

Query Example

SYST:COMM:LAN:DHCP?


DHCP.


SYSTem:COMMunicate:LAN:DNAMe <character_data>

This command sets the domain name for the power meter.

Syntax

SYST :COMM :LAN :DNAM Space character_data

?

Parameters

Item character_data

Description

Character values of up to 16 characters

Range of Values

Maximum of 16 characters

Example

SYST:COMM:LAN:DNAM

‘myco.com’

This command sets the hostname to myco.com.

Query

SYSTem:COMMunicate:LAN:DNAM?

The query returns the current setting of the LAN domain name.



Query Example

SYST:COMM:LAN:DNAM?

This command queries the setting of the domain name.



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:

A- + product number + - + suffix 5 digits of serial number

For example, A- N1911A- 00204

Syntax

SYST :COMM :LAN :HNAM Space character_data

?

508

Parameters

Item character_data

Description

Character values of up to 15 characters

Range of Values

Maximum of 15 characters

Example

SYST:COMM:LAN:HNAM

‘PowerMeter1’

This command sets the hostname to

PowerMeter 1.

Query

SYSTem:COMMunicate:LAN:HNAM?

The query returns the current setting of the LAN hostname.



Query Example

SYST:COMM:LAN:HNAM?

This command queries the setting of the hostname.



SYSTem:COMMunicate:LAN:MAC?

This query returns the LAN MAC address.

Syntax

SYST :COMM :LAN :MAC ?

Example

SYST:COMM:LAN:MAC?

This command queries the current MAC address.



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

SYST :COMM :LAN :REST

Example

SYST:COMM:LAN:REST This command restarts the LAN network with new configuration.



SYSTem:COMMunicate:LAN:SMASk <character_data>

This command sets the subnet mask of the power meter.

Syntax

SYST :COMM :LAN :SMAS Space character_data

?

512

Parameters

Item character_data

Description




Range of Values


Example

SYST:COMM:LAN:SMAS

‘255.255.248.0’

This command sets the subnet mask to

255.255.248.0.

Query

SYSTem:COMMunicate:LAN:SMASk?

The query returns the current setting of the LAN subnet mask.



Query Example

SYST:COMM:LAN:SMAS?


LAN subnet mask.

Remark




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.

N O T E

It is not recommended to use this command in Fast Mode, as it slows down the measurement rate.

Syntax

SYST :DISP :BMP ?

Example

SYST:DISP:BMP?

This command returns the display image in bitmap format.



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. The errors are cleared in the order of first- in first- out, this is the oldest erros are cleared first. To clear all the errors from the error queue, execute

*CLS command. When the error queue is emply, subsequent

SYSTem:ERRor?

queries return a +0, “No error” message. The error queue has a maximum capacity of 30 errors.

Syntax

SYST :ERR ?

Example

SYST:ERR?

This command queries the oldest error message stored in the power meter’s error queue.

Reset Condition

On reset, the error queue is unaffected.



Error Messages

• If the error queue overflows, the last error is replaced with –350,

“Queue overflow”. No additional errors are accepted by the queue until space becomes available.



Error Message List

–101

–102

–103

–105

–108

–109

–112

–113

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#.

Syntax error

Invalid syntax was found in the command string.

For example, LIM:CLE:AUTO, 1 or LIM:CLE: AUTO 1.

Invalid separator

An invalid separator was found in the command string. You may have used a comma instead of a colon, semicolon, or blank space; or you may have used a blank space instead of a comma.

For example, OUTP:ROSC,1.

GET not allowed

A Group Execute Trigger (GET) is not allowed within a command string.

Parameter not allowed

More parameters were received than expected for the command. You may have entered an extra parameter, or added a parameter to a command that does not accept a parameter.

For example, CAL 10.

Missing parameter

Fewer parameters were received than expected for the command. You omitted one or more parameters that are required for this command.

For example, AVER:COUN.

Program mnemonic too long

A command header was received which contained more than the maximum 12 characters allowed.

For example, SENSeAVERageCOUNt 8.

Undefined header

A command was received that is not valid for this power meter. You may have misspelled the command, it may not be a valid command or you may have the wrong interface selected. If you are using the short form of the command, remember that it may contain up to four letters.

For example, TRIG:SOUR IMM.



–121

–123

–124

–128

–131

–134

–138

–148

–151

–158

–161

Invalid character in number

An invalid character was found in the number specified for a parameter value.

For example, SENS:AVER:COUN 128#H.

Exponent too large

A numeric parameter was found whose exponent was larger than 32,000.

For example, SENS:COUN 1E34000.

Too many digits

A numeric parameter was found whose mantissa contained more than 255 digits, excluding leading zeros.

Numeric data not allowed

A numeric value was received within a command which does not accept a numeric value.

For example, MEM:CLE 24.

Invalid suffix

A suffix was incorrectly specified for a numeric parameter. You may have misspelled the suffix.

For example, SENS:FREQ 200KZ.

Suffix too long

A suffix used contained more than 12 characters.

For example, SENS:FREQ 2MHZZZZZZZZZZZ.

Suffix not allowed

A suffix was received following a numeric parameter which does not accept a suffix.

For example, INIT:CONT 0Hz.

Character data not allowed

A discrete parameter was received but a character string or a numeric parameter was expected. Check the list of parameters to verify that you have used a valid parameter type.

For example, MEM:CLE CUSTOM_1.

Invalid string data

An invalid string was received. Check to see if you have enclosed the character string in single or double quotes.

For example, MEM:CLE “CUSTOM_1.

String data not allowed

A character string was received but is not allowed for the command. Check the list of parameters to verify that you have used a valid parameter type.

For example, LIM:STAT ‘ON’.

Invalid block data

A block data element was expected but was invalid for some reason.

For example, *DDT #15FET. The 5 in the string indicates that 5 characters should follow, whereas in this example there are only 3.



–168

–178

–211

–213

–214

–220

–221

–222

–224

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?.

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).

Trigger ignored

Indicates that <GET> or *TRG, or TRIG:IMM was received and recognized by the device but was ignored because the power meter was not in the wait for trigger state.

Init ignored

Indicates that a request for a measurement initiation was ignored as the power meter was already initiated.

For example, INIT:CONT ON

INIT.

Trigger deadlock

TRIG:SOUR was set to HOLD or BUS and a READ? or MEASure? was attempted, expecting TRIG:SOUR to be set to IMMediate.

Parameter error;Frequency list must be in ascending order.

Indicates that the frequencies entered using the

MEMory:TABLe:FREQuency command are not in ascending order.

Settings conflict

This message occurs under a variety of conflicting conditions. The following list gives a few examples of where this error may occur:

If the READ? parameters do not match the current settings.

If you are in fast mode and attempting to switch on for example, averaging, duty cycle or limits.

Trying to clear a sensor calibration table when none is selected.

Data out of range

A numeric parameter value is outside the valid range for the command.

For example, SENS:FREQ 2KHZ.

Illegal parameter value

A discrete parameter was received which was not a valid choice for the command.

You may have used an invalid parameter choice.

For example, TRIG:SOUR EXT.



–226

–230

–231

–231

–231

–231

–231

–231

–231

–231

–231

–231

–231

–232

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.

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.

Data questionable;CAL ERROR

Power meter calibration failed. The most likely cause is attempting to calibrate without applying a 1 mW power to the power sensor.

Data questionable;CAL ERROR ChA

Power meter calibration failed on Channel A. The most likely cause is attempting to calibrate without applying a 1 mW power to the power sensor.

Data questionable;CAL ERROR ChB

Power meter calibration failed on Channel B. The most likely cause is attempting to calibrate without applying a 1 mW power to the power sensor.

Data questionable;Input Overload

The power input to Channel A exceeds the power sensor’s maximum range.

Data questionable;Input Overload ChA

The power input to Channel A exceeds the power sensor’s maximum range.

Data questionable;Input Overload ChB

The power input to Channel B exceeds the power sensor’s maximum range.

Data questionable;Lower window log error

This indicates that a difference measurement in the lower window has given a negative result when the units of measurement were logarithmic.

Data questionable;Upper window log error

This indicates that a difference measurement in the upper window has given a negative result when the units of measurement were logarithmic.

Data questionable;ZERO ERROR

Power meter zeroing failed. The most likely cause is attempting to zero when some power signal is being applied to the power sensor.

Data questionable;ZERO ERROR ChA

Power meter zeroing failed on Channel A. The most likely cause is attempting to zero when some power signal is being applied to the power sensor.

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.

Invalid format



–241

–310

–310

–310

–310

–310

–310

–310

–310

–321

–330

Hardware missing

The power meter is unable to execute the command because either no power sensor is connected or it expects an E-Series or N8480 Series power sensor and one is not connected.

System error;Dty Cyc may impair accuracy with ECP sensor

This indicates that the sensor connected is for use with CW signals only.

System error;Ch A Dty Cyc may impair accuracy with ECP sensor

This indicates that the sensor connected to Channel A is for use with CW signals only.

System error;Ch B Dty Cyc may impair accuracy with ECP sensor

This indicates that the sensor connected to Channel B is for use with CW signals only.

System error;Sensor EEPROM Read Failed - critical data not found or unreadable

This indicates a failure with your E-Series or N8480 Series power sensor. Refer to your power sensor manual for details on returning it for repair.

System error;Sensor EEPROM Read Completed OK but optional data block(s) not found or unreadable

This indicates a failure with your E-Series or N8480 Series power sensor power sensor. Refer to your power sensor manual for details on returning it for repair.

System error;Sensor EEPROM Read Failed - unknown EEPROM table format


System error;Sensor EEPROM < > data not found or unreadable

Where < > refers to the sensor data block covered, for example,

Linearity, Temp - Comp (temperature compensation).


System error;Sensors connected to both front and rear inputs.

You cannot connect two power sensors to the one channel input. In this instance the power meter detects power sensors connected to both it’s front and rear channel inputs.

Out of memory

The power meter required more memory than was available to run an internal operation.

Self-test Failed;

The -330, “Self-test Failed” errors indicate that you have a problem with your power meter. Refer to Contacting Agilent

Technologies on page 119 for details of what to do with your faulty power meter.



–362

–363

–410

–330

–330

–330

–330

–330

–330

–330

–350

–361

–420

–430

–440

Self-test Failed;Measurement Channel Fault

Self-test Failed;Measurement Channel A Fault

Self-test Failed;Measurement Channel B Fault

Self-test Failed;Calibrator Fault

Refer to “Calibrator” on page 104 if you require a description of the calibrator test.

Self-test Failed;ROM Check Failed

Self-test Failed;RAM Check Failed

Self-test Failed;Display Assy. Fault

Refer to “Display” on page 104 if you require a description of the Display test.

Queue overflow

The error queue is full and another error has occurred which could not be recorded.

Parity error in program

The serial port receiver has detected a parity error and consequently, data integrity cannot be guaranteed.

Framing error in program

The serial port receiver has detected a framing error and consequently, data integrity cannot be guaranteed.

Input buffer overrun

The serial port receiver has been overrun and consequently, data has been lost.

Query INTERRUPTED

A command was received which sends data to the output buffer, but the output buffer contained data from a previous command (the previous data is not overwritten). The output buffer is cleared when power has been off, or after *RST

(reset) command has been executed.

Query UNTERMINATED

The power meter was addressed to talk (that is, to send data over the interface) but a command has not been received which sends data to the output buffer. For example you may have executed a CONFigure command (which does not generate data) and then attempted to read data from the remote interface.

Query DEADLOCKED

A command was received which generates too much data to fit in the output buffer and the input buffer is also full. Command execution continues but data is lost.

Query UNTERMINATED after indefinite response

The *IDN? command must be the last query command within a command string.



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- 21

below.

#xyyy..yddd................ddd<LF>

The number of data bytes (d) contained in the block.

The number of y digits

Line feed character signifies the end of the block

Data bytes

Signifies the start of the block

Example: if there are 12435 data bytes, y = 12435 and x = 5

Figure 12-21IEEE 488.2 Arbitrary Block Program Data Format

Each point in the trace is represented as an IEEE 754 32 bit floating point number, made up of four bytes in the data block. The MS byte is transmitted first. Each complete block is terminated by a line feed.

Commands are listed in alphabetical order.

Syntax

SYST :HELP :HEAD ?



Example

SYST:HELP:HEAD?

This command returns the SCPI commands supported by the instrument.



SYSTem:LOCal

This command unlocks the front panel keypad and enables the power meter to be controlled from the front panel. The power meter display status reporting line shows “LCL”.

Syntax

SYST :LOC

Example

SYST:LOC This command unlocks the power meter front panel keypad and enables local front panel control.



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.

N O T E

DEFault settings apply to both *RST and to

SYSTem:PREset DEFault unless stated otherwise.

526

For further information on preset configurations, refer to

Table 12- 26

through to Table 12- 83 .

Command results differ according to the sensor(s) connected to the power meter:

• If connected to a dual channel power meter, a P- Series or E9320 sensor are connected to one channel, and another model sensor is connected to the other channel, the channel connected to the P- Series or E9320 sensor is set up according to the <character_data> value and the other channel is set to DEFault values.

• If two P- Series or E9320 sensors are connected to a dual channel power meter, both channels are set to the same values except for bandwidth which is set to an appropriate value for each sensor.

Primary and Secondary Channels

Dual channel meter channels are defined as either primary or secondary.

The primary channel is always the trigger master and primary channel measurements occupy a greater share of the display space than secondary channel measurements.

• If a dual channel meter has a P- Series sensor connected, the P- Series or E9320 sensor channel is the primary channel. In such cases the primary channel could be either Channel A or Channel B. The other model’s channel is the secondary channel.

• If a dual channel meter has two, P- Series or E9320 sensors, connected to it, the primary channel is always Channel A and the secondary channel is Channel B.



Syntax

SYST :PRES Space character_data

Parameters

Item character_data

Description

A communications format which determines the preset values. Refer to

Table 12-26

through to

Table 12-74 for

the preset values for each format.

Range of Values

DEFault

GSM900

EDGE

NADC

BLUetooth

CDMAone

WCDMA

CDMA2000

IDEN

MCPa

RADar

WL802DOT11A

WL802DOT11B

XEVDO

XEVDV

TDSCdma

DVB

HIPERLAN2

WIMAX

HSDPA

DME

DMEPRT

LTE



Example

SYST:PRES DEF This command presets the power meter with default values. The same default values are set when the parameter is omitted.

Error messages

• If a non- E- Series power sensor or N8480 Series power sensor with

Option CFT is connected, the command can be used to set the power meter to Default settings. When non of the connected sensor is E9320 sensor, attempts to set the power meter to any of the other settings result in error –241 “Hardware missing: E9320 Series sensor required” occurring.

• If BLUetooth or CDMAone is selected and an E9322/6A (1.5 MHz bandwidth) or E9323/7A (5 MHz bandwidth) power sensor is not connected, error –241 “Hardware missing: Higher bandwidth E9320 sensor required on Channel X. Measurements on Channel X may be inaccurate” occurs.

• If WCDMA or CDMA2000 is selected and an E9323/7A (5 MHz bandwidth) power sensor is not connected, error –241 “Hardware missing: Higher bandwidth E9320 sensor required on Channel X.

Measurements on Channel X may be inaccurate” occurs.

• If two E9320 power sensors are connected to a dual channel power meter and only one is of sufficient bandwidth to support the selected format, error –241 “Hardware missing: Higher bandwidth E9320 sensor required on Channel X. Measurements on Channel X may be inaccurate” occurs.



Preset Values

DEFault

Table 12- 26

shows the power meter presets when <character_data> is set to

DEFault or omitted. Values are shown for all SCPI commands:

Table 12-26DEFault: Power Meter Presets

Command

CALC[1]|2|3|4:FEED[1]|2

CALC[1]|2|3|4:GAIN[:MAGN]

CALC[1]|2|3|4:GAIN:STAT

CALC[1]|2|3|4:LIM:CLE:AUTO

CALC[1]|2|3|4:LIM:LOW[:DATA]

CALC[1]|2|3|4:LIM:STAT

CALC[1]|2|3|4:LIM:UPP[:DATA]

CALC[1]|2|3|4:MATH[:EXPR]

CALC[1]|2|3|4:REL[:MAGN]:AUTO

CALC[1]|2|3|4:REL:STAT

CAL[1]|2:ECON:STAT

CAL[1]|2:RCAL

CAL[1]|2:RCF

DISP:CONT

DISP:ENAB

DISP:SCR:FORM

DISP[:WIND[1]|2]:ANAL:LOW

DISP[:WIND[1]|2]:ANAL:UPP

Setting

“POW:AVER”

0.000 dB

OFF

ON

–90 dBm

OFF

+90 dBm

Agilent N1911A:

Upper - Channel A

Lower - Channel A

Agilent N1912A:

Upper - Channel A

Lower - Channel B

OFF

OFF

OFF not affected

100.0 % not affected

ON

WIND

–70 dBm

20 dBm

Comments

Select average measurement type

Display offset value

Display offset disabled

Clear limit data at INIT

Lower limit

Window limits checking disabled

Math expression

Reference value disabled

Relative offset disabled

TTL zero/calibration inputs disabled zero/cal lockout

Reference calibration factor

Display contrast

Display enabled

Display format set to windowed

Lower scale limit

Upper scale limit



Command

DISP[:WIND[1]|2]:FORM

530

DISP[:WIND[1]|2]:MET:LOW

DISP[:WIND[1]|2]:MET:UPP

DISP[:WIND[1]|2|][:NUM[1]|2]

:RES

DISP[:WIND[1]|2]:SEL[1]|2

DISP[:WIND[1]|2][:STAT]

SENSe[1]|2:TRAC:LIM:UPP

SENSe[1]|2:TRAC:LIM:LOW

FORM[:READ]:BORD

FORM[:READ][:DATA]

INIT[1]|2:CONT

MEM:TABL:SEL

OUTP:REC[1]|2:FEED

OUTP:REC[1]|2:LIM:LOW

OUTP:REC[1]|2:LIM:UPP

OUTP:ROSC:STAT

OUTP:TRIG:STAT

[SENS[1]]|SENS2:AVER:COUN

[SENS[1]]|SENS2:AVER:COUN:AUTO

[SENS[1]]|SENS2:AVER:SDET

[SENS[1]]|SENS2:AVER[:STAT]

[SENS[1]]|SENS2:AVER2:COUN

[SENS[1]]|SENS2:AVER2[:STAT]

[SENS[1]]|SENS2:BAND|BWID:VID

[SENS[1]]|SENS2:CORR:CFAC|

GAIN[1][:INPut][:MAGNitude]

Setting

Agilent N1911A:

Upper - digital

Lower - analog

Agilent N1912A:

Upper - digital

Lower - digital

–70.000 dBm

+20.000 dBm

3 upper window

ON

DEF

DEF normal ascii

*RST: OFF

SYS:PRES ON

OFF

OFF

4

ON not affected not affected

–150 dBm

20 dBm

1

ON

4

ON

OFF

100.0 %

Comments

Display format

Analog meter lower limit

Analog meter upper limit

Window resolution

Window selected

Both windows enabled on display

Maximum power

Minimum power

Binary order

Data format

Power Meter in idle state

Power Meter in wait for trigger state

Active sensor calibration table

Previous measurement

Minimum scaling value

Maximum scaling value

50 MHz reference disabled

Trigger output signal disabled

Filter length

Auto-filtering enabled

Step detection enabled

Averaging enabled

Video average length

Video averaging enabled

Sensor video bandwidth set to off

Calibration factor



Command

[SENS[1]]|SENS2:CORR:CSET[1]|

CSET2[:SEL]

[SENS[1]]|SENS2:CORR:CSET[1]|

CSET2:STAT

[SENS[1]]|SENS2:CORR:DCYC|GAIN3

[:INP][:MAGN]

[SENS[1]]|SENS2:CORR:DCYC|GAIN3:ST

AT

[SENS[1]]|SENS2:CORR:FDOF|GAIN4[:I

NP][:MAGN]

[SENS[1]]|SENS2:CORR:GAIN2:STAT

[SENS[1]]|SENS2:CORR:GAIN2:STAT

[:INPut][:MAGNitude]

[SENS[1]]|SENS2:DET:FUNC

[SENS[1]]|SENS2:FREQ[:CW|:FIX]

[SENSe[1]]|SENS2:MRAT

[SENS[1]]|SENS2:POW:AC:RANG

[SENS[1]]|SENS2:POW:AC:RANG:

AUTO

[SENS[1]]|SENS2:SPE

Setting not affected not affected

1.000 %

OFF not affected

OFF

0.0 dB

NORM

+50.000 MHz

NORM upper

ON

20 readings/ second

0 [SENS[1]]|SENS2:SWE[1]|2|3|4

:OFFS:TIME

[SENS[1]]|SENS2:SWE[1]|2|3|4

:TIME

[SENS[1]]|SENS2:TRACe:OFFSet:

TIME

[SENS[1]]|SENS2:TRACe:TIME

[SENS[1]]|SENS2:V2P

SYST:GPIB[:SELF]ADDR

TRAC[1]|2:STAT

TRAC[1]|2:UNIT

TRIG[1]|2:DEL:AUTO

Gate 1: 100 µs

Other gates: 0 sec

0

100 µs

ATYP not affected

OFF dBm

ON

Comments

Selected sensor calibration table

Sensor calibration table disabled

Duty cycle factor

Duty cycle correction disabled

Return frequency dependent offset

Channel offset disabled

Enter channel offset value

Measurement mode

Frequency setting

Measurement speed

Upper range selected

Auto-ranging selected

Speed

Set delay

Set time gated period

Delay

Duration of trace

Select linearity correction

Power meter address

Disable trace capture

Trace units

Insert settling time delay



Command

TRIG[:SEQ]:DEL

TRIG[:SEQ]:HOLD

TRIG[:SEQ]:HYST

TRIG[:SEQ]:LEV

TRIG[:SEQ]:LEV:AUTO

TRIG[:SEQ]:SLOP

TRIG[:SEQ[1]|2]:COUN

TRIG[:SEQ[1]|2]:DEL:AUTO

TRIG[:SEQ[1]|2]:SOUR

UNIT:POW

UNIT:POW:RAT

Setting

0

1 µs

0 dB

0 dB

ON

POS

1

ON

IMM dBm dB

Comments

Delay between recognition of trigger event and start of a measurement

Trigger holdoff

Fall/rise below/above TRIG:LEV

Power level

Enable automatic setting of trigger level

Trigger event recognized on rising edge

Trigger events for measurement cycle

Enable settling time delay

Trigger source set up

Power units

Ratio units



GSM900

Table 12- 27

shows the power meter presets when <character_data> is set to

GSM900.

The GSM900 setup 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. The trigger level is set to –20 dBm. Time- gating is used to measure the average power in the useful part of a GSM burst.

Commands not listed are preset according to their DEFault values (for further information refer to

Table 12- 26 .

Table 12-27GSM900: Power Meter Presets

Command

Frequency


Sensor measurement mode


Sensor video bandwidth setup


Gate Setup

[SENS[1]]|SENS2:SWE[1]|2|3|4

:OFF:TIME

[SENS[1]]|SENS2:SWE[1]|2|3|4

:TIME

Trigger setup


INIT:CONT

Setting

+900.000 MHz

NORM

E9321A/25A: HIGH

E9322A/26A: MED

E9323A/27A: LOW

N1921/2A: LOW

Gate 1: 20 µs

Gates 2 - 4: 0

Gate 1: 520 µs

Gates 2 - 4: 0

INT1

ON

Comments

Frequency setting

Measurement mode

Sensor video bandwidth

Delay between trigger point and time gated period.

Length of time gated period for time gated measurements.

Trigger source set up and acquisition mode continuous triggering



Command

TRIG[:SEQ]:LEV:AUTO

TRIG[:SEQ]:LEV

TRIG[:SEQ]:SLOP

TRIG[:SEQ]:DEL

TRIG[:SEQ]:HOLD

Range

[SENS[1]]|SENS2:POW:AC:RANG:AUTO

[sens[1]]|SENS2:POWER:AC:RANG

Step detection

[SENSe[1]]|SENS2:AVER:SDET

Trace setup



[SENS[1]]|SENS2:TRAC:OFFS

:TIME <numeric_value>

[SENS[1]]|SENS2:TRAC:TIME

<numeric_value>

OFF

UPPER

1

+20 dBm

–35 dBm

–40 µs

700 µs

Setting

OFF

–15 dBm

POS

20 µs

4275 µs

Comments

Disable automatic setting of the trigger level

Power level

Trigger event recognized on the rising edge of a signal


Trigger holdoff

Auto range off

Range set to upper


Maximum power

Minimum power

Delay between delayed trigger point and the start of the trace

Length of the trace

N O T E

The Range setting in

Table 12-27

is only applicable for E-Series power sensor and N8480

Series power sensor (excluding Option CFT) .

534

Function

Display setup

Upper window

Lower window

Table 12-28GSM900: Power Meter Presets: Window/Measurement Settings

Setting

Single Channel Dual Channel

Channel A trace

LU single numeric

Primary channel

*

trace

See Table 12-29



Function Setting

Single Channel

Window/measurement setup

Upper window/upper measurement (UU)

Feed

Measurement

Upper window/lower measurement (UL)

Feed

Measurement

Lower window/upper measurement (LU)

Feed

Measurement

Lower window/lower measurement (LL)

Feed

Measurement

N/A

N/A

N/A

N/A

Gate 1 Channel A

Avg

DEF

DEF

* For further information refer to “Primary and Secondary Channels” on page 526.

Dual Channel

N/A

N/A

N/A

N/A

Gate 1 primary channel

*

Avg

See

Table 12-29

See Table 12-29

Table 12-29GSM900: Power Meter Presets For Secondary Channel Sensors

Function Secondary Channel Sensor

No Sensor Non P-Series or E9320

Sensor

Display setup

Lower window LU single numeric


Feed DEF

Dual numeric

Secondary channel

*

Measurement DEF Avg


P-Series and E9320

Sensor

Dual numeric

Gate1 secondary channel

*

(Channel B)

Avg



536

EDGE

EDGE (Enhanced Data for Global Evolution or Enhanced Data for GSM

Evolution) is an enhancement of the GSM standard. Whereas the GSM modulation scheme is GMSK which has constant amplitude, the EDGE modulation scheme is 8PSK which has variable amplitude.

The EDGE setup provides:

• Average power measurement in an EDGE burst.

• Peak- to- average ratio in an EDGE burst.

• A trace display of the burst profile

An EDGE measurement is started by detecting the rising edge of the

EDGE RF burst—for example the burst emitted by a mobile—using the internal RF level trigger. The internal level trigger is set to –20 dBm.

Trigger level hysteresis is used to prevent the power meter re- triggering on the varying power levels within the EDGE burst. Time- gating is used to measure the average power and the peak- to- average ratio in the useful part of the RF burst.

The following table shows the power meter presets when <character_data> is set to EDGE. Commands not listed are preset according to their DEFault

values (for further information refer to Table 12- 26

).

Table 12-30EDGE: Power Meter Presets

Command

Frequency






Gate Setup

[SENS[1]]|SENS2:SWE[1]|2|3|4

:OFF:TIME

Setting

+900.000 MHz

NORM

E9321A/25A: HIGH

E9322A/26A: MED

E9323A/27A: LOW

N1921/2A: LOW

Gate 1: 20 µs

Gates 2 - 4: 0

Comments

Frequency setting

Measurement mode





Command

[SENS[1]]|SENS2:SWE[1]|2|3|4

:TIME

Trigger setup


INIT:CONT

TRIG[:SEQ]:LEV:AUTO

TRIG[:SEQ]:LEV

TRIG[:SEQ]:SLOP

TRIG[:SEQ]:DEL

TRIG[:SEQ]:HOLD

TRIG[:SEQ]:HYST

Range



Averaging

[SENSe[1]]|SENSe2:AVER[:STATe]

[SENSe[1]]|SENSe2:AVER:COUN

Step detection


Trace setup






<numeric_value>

Setting

Gate 1: 520 µs

Gates 2 - 4: 0

OFF

UPPER

ON

64

1

INT1

ON

OFF

–15 dBm

POS

0 s

4275 µs

3 dB

+20 dBm

–35 dBm

–40 µs

700 µs

Comments




Power level



Trigger holdoff

Hysteresis

Auto range off

Range set to upper

Averaging On

Averaging set to 64


Maximum power

Minimum power


Length of the trace

N O T E


Table 12-30


Series power sensor (excluding Option CFT)



Table 12-31EDGE: Power Meter Presets: Window/Measurement Settings


Single Channel

Display setup

Upper window Channel A trace

Lower window



Feed

Measurement


Feed

Measurement


Feed

Measurement


Feed

Measurement

Dual numeric

N/A

N/A

N/A

N/A

Gate 1 Channel A

Avg

Gate 1 Channel A

Pk-to-Avg


Dual Channel

Primary channel

*

trace

See Table 12-32

N/A

N/A

N/A

N/A


*

Avg

See

Table 12-32

See

Table 12-32

Table 12-32EDGE: Power Meter Presets For Secondary Channel Sensors



Sensor

Display setup

Lower window Dual numeric


Dual numeric


Sensor

Dual numeric



Function

Feed

Secondary Channel Sensor

No Sensor


*

Non P-Series or E9320

Sensor

Secondary channel

*

Measurement Pk-to-Avg Avg



Sensor


*

(Channel B)

Avg



CDMAone

The cdmaOne setup 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.

The measurement is a continuously gated measurement on a cdmaOne signal. Its aim is to measure the peak and average power corresponding to a <0.01 % probability that there are no peaks above the returned peak reading. Time gating is therefore set to 10 ms, corresponding to 200000 samples. Triggering is set to occur continuously internally to the meter.

The internal trigger is set to AutoLevel. A reading over the 10ms period is returned and the reading is then re- initiated for the next 10ms period. In this way the reading always relates to a position beyond 0.01 % on the

CCDF curve and will refresh to track any signal or DUT changes.

The following table shows the power meter presets when <character_data> is set to CDMAone. Commands not listed are preset according to their

DEFault


):

Table 12-33CDMAone: Power Meter Presets

Command

Frequency






Setting

+850.000 MHz

NORM

E9321A/25A: DEF

E9322A/26A: OFF

E9323A/27A: OFF

N1921/2A: OFF

Comments

Frequency setting

Measurement mode


Gate Setup



Command

[SENS[1]]|SENS2:SWE[1]|2|3|4

:OFF:TIME

[SENS[1]]|SENS2:SWE[1]|2|3|4

:TIME

Trigger setup


INIT:CONT

TRIG[:SEQ]:LEV:AUTO

TRIG[:SEQ]:LEV

TRIG[:SEQ]:SLOP

TRIG[:SEQ]:DEL

TRIG[:SEQ]:HOLD

Range

1



Step detection


Setting

Gate 1: 0 s

Gates 2 - 4: 0

Gate 1: 10 ms

Gates 2 - 4: 0

INT1

ON

ON

AUTO

POS

0 s

MIN

OFF

UPPER

0

Comments




Enable automatic setting of the trigger level

Automatic Power level



Trigger holdoff

Auto range off

Range set to upper

Step detection disabled

1


Table 12-33 is only applicable for E-Series power sensor and N8480 Series

power sensor (excluding Option CFT).

Function

Display setup

Upper window

Lower window

Table 12-34CDMAone: Power Meter Presets: Window/Measurement Settings

Setting


UU single numeric

Dual numeric

See Table 12-35

See Table 12-35




Single Channel



Feed Gate 1 Channel A

Measurement


Feed

Measurement


Feed

Measurement


Feed

Measurement

Avg

DEF

DEF

Gate 1 Channel A

Peak

Gate 1 Channel A

Pk-to-Avg


Dual Channel


*

Avg

See

Table 12-35

See Table 12-35

See

Table 12-35

See

Table 12-35

See

Table 12-35

See

Table 12-35

Table 12-35 CDMAone: Power Meter Presets For Secondary Channel Sensors



Sensor

Display setup

Upper window UU single numeric



Feed DEF

Dual numeric

Dual numeric


*

Measurement DEF


Peak


Sensor

Dual numeric

Dual numeric


*

(Channel A)

Peak



Function

Feed


No Sensor


*


Sensor


*

Pk-to-Avg


Sensor

Gate 1 secondary channel

*

(Channel B)

Avg Measurement Peak


Feed


*

Secondary channel

*


*

(Channel B)

Pk-to-Avg Measurement Pk-to-Avg Avg




544

CDMA2000

The cdma2000 setup 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.

The measurement is a continuously gated measurement on a 3 GPP cdma2000 signal. Its aim is to measure the peak and average power corresponding to a <0.01 % probability that there are no peaks above the returned peak reading. Time gating is set to 10 ms, corresponding to

200,000 samples. Triggering is set to occur continuously internally to the meter. The internal trigger is set to AutoLevel. A reading over the 10 ms period is returned, then the reading is re- initiated for the next 10ms period. In this way the reading always relates to a position beyond 0.01 % on the CCDF curve and will refresh to track any signal or DUT changes.

The following table shows the power meter presets when

<character_data> is set to CDMA2000. Commands not listed are preset according to their DEFault values (for further information refer to

Table 12- 26

):

Table 12-36 cdma2000: Power Meter Presets

Command

Frequency






Gate Setup

[SENS[1]]|SENS2:SWE[1]|2|3|4

:OFF:TIME

Setting

+1900.000 MHz

NORM

E9321A/25A: DEF

E9322A/26A: DEF

E9323A/27A: OFF

N1921/2A: OFF

Gate 1: 0 s

Gates 2 - 4: 0

Comments

Frequency setting

Measurement mode





Command

[SENS[1]]|SENS2:SWE[1]|2|3|4

:TIME

Trigger setup


INIT:CONT

TRIG[:SEQ]:LEV:AUTO

TRIG[:SEQ]:LEV

TRIG[:SEQ]:SLOP

TRIG[:SEQ]:DEL

TRIG[:SEQ]:HOLD

Range

1



Step detection


OFF

UPPER

0

Setting

Gate 1: 10 ms

Gates 2 - 4: 0

INT1

ON

ON

AUTO

POS

0 s

MIN

Comments







Trigger holdoff

Auto range off

Range set to upper


1


Table 12-36 is only applicable for E-Series power sensor

and N8480


Function

Table 12-37 cdma2000: Power Meter Presets: Window/Measurement Settings

Setting


Display setup

Upper window

Lower window


UU single numeric

Dual numeric

UU single numeric

See Table 12-38




Single Channel


Feed Gate 1 Channel A

Measurement


Feed

Measurement


Feed

Measurement


Feed

Measurement

Avg

DEF

DEF

Gate 1 Channel A

Peak

Gate 1 Channel A

Pk-to-Avg


Dual Channel


*

Avg

DEF

DEF


*

Peak

See

Table 12-38

See

Table 12-38

Table 12-38 cdma2000: Power Meter Presets For Secondary Channel Sensors


No Sensor Non P-series or E9320

Sensor

Display setup




Feed DEF

Dual numeric

Dual numeric


*

Measurement DEF


Peak

P-series and E9320

Sensor

Dual numeric

Dual numeric


*

(channel A)

Peak



Function

Feed


No Sensor


*

Non P-series or E9320

Sensor


*

Pk-to-Avg

P-series and E9320

Sensor


*

(channel B)



Feed


*

Secondary channel

*


*

(channel B)





548

W-CDMA

The W- CDMA setup 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.

The measurement is a continuously gated measurement on a 3GPP

W- CDMA signal. Its aim is to measure the peak and average power corresponding to a <0.01 % probability that there are no peaks above the returned peak reading. Time gating is set to 10 ms, corresponding to

200000 samples. Triggering is set to occur continuously internally to the meter. The internal trigger is set to AutoLevel. A reading over the 10 ms period is returned then re- initiated for the next 10 ms period. In this way the reading always relates to a position beyond 0.01 % on the CCDF curve and will refresh to track any signal or DUT changes.

The following table shows the power meter presets when <character_data> is set to WCDMA. Commands not listed are preset according to their

DEFault values (for further information refer to

Table 12- 26

):

Table 12-39 W-CDMA: Power Meter Presets

Command

Frequency






Setting

+1900.000 MHz

NORM

Comments

Frequency setting

Measurement mode

Sensor video bandwidth E9321A/25A: DEF

E9322A/26A: DEF

E9323A/27A: OFF

N1921/2A: OFF

Gate Setup

[SENS[1]]|SENS2:SWE[1]|2|3|4

:OFF:TIME

Gate 1: 0 s

Gates 2 - 4: 0




Command

[SENS[1]]|SENS2:SWE[1]|2|3|4

:TIME

Trigger setup


INIT:CONT

TRIG[:SEQ]:LEV:AUTO

TRIG[:SEQ]:LEV

TRIG[:SEQ]:SLOP

TRIG[:SEQ]:DEL

TRIG[:SEQ]:HOLD

Range

1



Step detection


OFF

UPPER

0

Setting

Gate 1: 10 ms

Gates 2 - 4: 0

INT1

ON

ON

AUTO

POS

0 s

1 µs

Comments







Trigger holdoff

Auto range off

Range set to upper


1


Table 12-39

is only applicable for E-Series power sensor and N8480 Series power sensor (excluding Option CFT).

Function

Table 12-40 W-CDMA: Power Meter Presets: Window/Measurement Settings

Setting


Display setup

Upper window

Lower window


UU single numeric

Dual numeric

See Table 12-41

See Table 12-41




Single Channel


Feed

Measurement


Feed

Measurement


Feed

Measurement


Feed

Measurement

Gate 1 Channel A

Avg

DEF

DEF

Gate 1 Channel A

Peak

Gate 1 Channel A

Pk-to-Avg


Dual Channel


*

Avg

See

Table 12-41

See Table 12-41

See

Table 12-41

See

Table 12-41

See

Table 12-41

See

Table 12-41

Table 12-41 W-CDMA: Power Meter Presets For Secondary Channel Sensors



Sensor

Display setup

Upper window

Lower window

UU single numeric

Dual numeric


Feed DEF

Dual numeric

Dual numeric


*

Peak


Sensor

Dual numeric

Dual numeric


*

(Channel A)

Peak Measurement DEF


Feed


*


*


*

(Channel B)





Sensor

Pk-to-Avg Measurement Peak


Feed


*

Secondary channel

*




Sensor

Avg


*

(Channel B)

Pk-to-Avg



552

BLUetooth

The Bluetooth setup 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. The internal trigger is set to –20 dBm.

Time- gating is used to measure the peak and average power in a single

Bluetooth DHI data burst which lasts for 366 us. The DHI burst does not occupy a full Bluetooth timeslot, which lasts for 625 µs.

The following table shows the power meter presets when <character_data> is set to BLUetooth. Commands not listed are preset according to their

DEFault


):

Table 12-42 BLUetooth: Power Meter Presets

Command

Frequency






Gate Setup

[SENS[1]]|SENS2:SWE[1]|2|3|4

:OFF:TIME

[SENS[1]]|SENS2:SWE[1]|2|3|4

:TIME

Trigger setup


INIT:CONT

Setting

+2400.000 MHz

NORM

E9321A/25A: DEF

E9322A/26A: OFF

E9323A/27A: OFF

N1921/2A: OFF

Gate 1: 0.2

µs

Gates 2 - 4: 0

Gate 1: 366 µs

Gates 2 - 4: 0

INT1

ON

Comments

Frequency setting

Measurement mode







Command

TRIG[:SEQ]:LEV:AUTO

TRIG[:SEQ]:LEV

TRIG[:SEQ]:SLOP

TRIG[:SEQ]:DEL

TRIG[:SEQ]:HOLD

Range

1



Step detection


Trace setup






<numeric_value>

OFF

UPPER

1

+20 dBm

–35 dBm

–50 µs

3.8 ms

Setting

OFF

–15 dBm

POS

0 s

650 µs

Comments


Power level



Trigger holdoff

Auto range off

Range set to upper


Maximum power

Minimum power


Length of the trace

1

The Range setting in Table 12-42 is only applicable for E-Series power sensor and N8480 Series


Function

Display setup

Upper window

Lower window

Table 12-43 BLUetooth: Power Meter Presets: Window/Measurement Settings

Setting


Channel A trace

Dual numeric

Primary channel

*

trace

See Table 12-44




Single Channel



Feed

Measurement


Feed

Measurement


Feed

Measurement


Feed

Measurement

N/A

N/A

N/A

N/A

Gate 1 Channel A

Avg

Gate 1 Channel A

Peak


Dual Channel

N/A

N/A

N/A

N/A


*

Avg

See Table 12-44

See

Table 12-44

Table 12-44 BLUetooth: Power Meter Presets For Secondary Channel Sensors



Sensor

Display setup



Feed Gate 1 primary channel1

Dual numeric

Secondary channel

*

Measurement Peak Avg



Sensor

Dual numeric


*

(Channel B)

Avg



MCPA

The following table shows the power meter presets when <character_data> is set to MCPa. Commands not listed are preset according to their DEFault


).

Table 12-45 MPCA: Power Meter Presets

Command

Frequency






Setting

+1900.000 MHz

NORM

Comments

Frequency setting

Measurement mode


E9322A/26A: DEF

E9323A/27A: DEF

N1921/2A: HIGH

Gate Setup

[SENS[1]]|SENS2:SWE[1]|2|3|4

:OFF:TIME

[SENS[1]]|SENS2:SWE[1]|2|3|4

:TIME

Trigger setup


INIT:CONT

TRIG[:SEQ]:LEV:AUTO

TRIG[:SEQ]:LEV

TRIG[:SEQ]:SLOP

TRIG[:SEQ]:DEL

TRIG[:SEQ]:HOLD

Range

1


Gate 1: 0 s

Gates 2 - 4: 0

Gate 1: 10 ms

Gates 2 - 4: 0

INT1

ON

OFF

-15 dBm

POS

0 s

MIN

OFF





Power level



Trigger holdoff

Auto range off



Command


Step detection


Setting

UPPER

0

Comments

Range set to upper


1



Table 12-46 MPCA: Power Meter Presets: Window/Measurement Settings


Single Channel

Display setup

Upper window

Lower window



Feed

Measurement


Feed

Measurement


Feed

Measurement


Feed

Measurement

UU single numeric

Dual numeric

Gate 1 Channel A

Avg

DEF

DEF

Gate 1 Channel A

Peak

Gate 1 Channel A

Pk-to-Avg


Dual Channel

UU single numeric

See Table 12-47


*

Avg

See

Table 12-47

See Table 12-47

See

Table 12-47

See

Table 12-47

See

Table 12-47

See

Table 12-47



Table 12-47 MCPA: Power Meter Presets For Secondary Channel Sensors



Sensor

Display setup

Upper window

Lower window

UU single numeric

Dual numeric


Feed DEF

Dual numeric

Dual numeric


*

Peak


Sensor

Dual numeric

Dual numeric


*

(Channel A)



Feed


*


*

Pk-to-Avg


*

(Channel B)



Feed


*

Secondary channel

*




*

(Channel B)

Pk-to-Avg



RADAR

The following table shows the power meter presets when <character_data> is set to RADar. Commands not listed are preset according to their

DEFault


).

Table 12-48 RADAR: Power Meter Presets

Command

Frequency






Setting

+10.000 GHz

NORM

Comments

Frequency setting

Measurement mode


E9322A/26A: DEF

E9323A/27A: OFF

N1921/2A: OFF

Gate Setup

[SENS[1]]|SENS2:SWE[1]|2|3|4

:OFF:TIME


[SENS[1]]|SENS2:SWE[1]|2|3|4

:TIME

Gate 1: 0

Gate 2: 0

Gate 3: 750 ns

Gate 4: 0

Gate 1: 1.0 µs

Gate 2: 250 ns

Gate 3: 250 ns

Gate 4: 0


Trigger setup


INIT:CONT

TRIG[:SEQ]:LEV:AUTO

TRIG[:SEQ]:LEV

TRIG[:SEQ]:SLOP

TRIG[:SEQ]:DEL

INT1

ON

ON

AUTO

POS

0 s








Command

TRIG[:SEQ]:HOLD

Range

1



Step detection

[SENS[1]]|SENS2:AVER:SDET

Trace setup




<numeric_value>

Setting

MIN

OFF

UPPER

0

–250 ns

1.5 µs

Comments

Trigger holdoff

Auto range off

Range set to upper



Length of the trace

1

The Range setting in Table 12-48


Function

Table 12-49 RADAR: Power Meter Presets: Window/Measurement Settings

Setting


Display setup

Upper window

Lower window



Feed

Measurement


Feed 1

Feed 2

Measurement

Channel A trace

Dual numeric

Gate 1 Channel A

Pk-to-Avg

Gate 2 Channel A - Avg

Feed 1/ Feed 2

See

Table 12-50

Dual numeric

See

Table 12-50

See

Table 12-50

See Table 12-50

See

Table 12-50

See Table 12-50






Feed

Measurement


Feed

Measurement

Gate 1 Channel A

Peak

Gate 1 Channel A

Avg

See

Table 12-50

See

Table 12-50

See

Table 12-50

See Table 12-50

Table 12-50 RADAR: Power Meter Presets For Secondary Channel Sensors



Sensor

Display setup

Upper window

Lower window

Primary Channel Trace

Dual numeric


Feed


*

Measurement Pk-to-Avg


Feed 1


*

Feed 2

Measurement Avg


Feed 1


*

Dual numeric

Dual numeric


*

Peak


*

Peak


*


Sensor

Dual numeric

Dual numeric


*

Peak


*

Avg


*

(Channel B)

Feed 2

Measurement Peak


Avg Peak





Sensor

Secondary channel

* Feed

Measurement


*

Avg Avg



Sensor


*

(Channel B)

Avg



802.11a and HiperLan2

The following table shows the power meter presets when <character_data> is set to 802DOT11A and HIPERLAN2. Commands not listed are preset according to their DEFault values (for further information refer to

Table 12- 26

).

Table 12-51 802.11a and HiperLan2: Power Meter Presets

Command

Frequency






Setting

+5200.000 MHz

NORM

Comments

Frequency setting

Measurement mode


E9322A/26A: DEF

E9323A/27A: HIGH

N1921/2A: HIGH

Gate Setup

[SENS[1]]|SENS2:SWE[1]|2|3|4

:OFF:TIME

[SENS[1]]|SENS2:SWE[1]|2|3|4

:TIME

Trigger setup


INIT:CONT

TRIG[:SEQ]:LEV:AUTO

TRIG[:SEQ]:LEV

TRIG[:SEQ]:SLOP

TRIG[:SEQ]:DEL

TRIG[:SEQ]:HOLD

Range

1

Gate 1: 0

Gates 2 - 4: 0

Gate 1: 25 µs

Gates 2 - 4: 0

INT1

ON

ON

AUTO

POS

0 s

MIN





Power level



Trigger holdoff



Command



Step detection


Setting

OFF

UPPER

0

Comments

Auto range off

Range set to upper


1

The Range setting in Table 12-51



Table 12-52 802.11a and HiperLan2: Power Meter Presets: Window/Measurement Settings


Single Channel

Display setup

Upper window

Lower window



Feed

Measurement


Feed

Measurement


Feed

Measurement


Feed

Measurement

UU Single Numeric

Dual numeric

Gate 1 Channel A

Avg

DEF

DEF

Gate 1 Channel A

Peak

Gate 1 Channel A

Pk-to-Avg


Dual Channel

UU Single Numeric

See Table 12-53


*

Avg

See

Table 12-53

See Table 12-53

See

Table 12-53

See

Table 12-53

See

Table 12-53

See

Table 12-53



Table 12-53 802.11a and HiperLan2: Power Meter Presets For Secondary Channel Sensors



Sensor

Display setup

Upper window

Lower window

UU Single numeric

Dual numeric


Feed DEF

Dual numeric

Dual numeric


*

Peak


Sensor

Dual numeric

Dual numeric

Gate1 primary channel

*

(Channel A)



Feed


*


*

Pk-to-Avg


*

(Channel B)



Feed


*

Secondary channel

*


* For further information refer to

“Primary and Secondary Channels” on page 526.


*

(Channel B)

Pk-to-Avg



892.11b/g

The following table shows the power meter presets when <character_data> is set to 802DOT11B. Commands not listed are preset according to their

DEFault


).

Table 12-54 802.11b/g: Power Meter Presets

Command

Frequency






Setting

+2.400 GHz

NORM

Comments

Frequency setting

Measurement mode


E9322A/26A: DEF

E9323A/27A: HIGH

N1921/2A: HIGH

Gate Setup

[SENS[1]]|SENS2:SWE[1]|2|3|4

:OFF:TIME

[SENS[1]]|SENS2:SWE[1]|2|3|4

:TIME

Trigger setup


INIT:CONT

TRIG[:SEQ]:LEV:AUTO

TRIG[:SEQ]:LEV

TRIG[:SEQ]:SLOP

TRIG[:SEQ]:DEL

TRIG[:SEQ]:HOLD

Range

1


Gate 1: 0

Gates 2 - 4: 0

Gate 1: 100 µs

Gates 2 - 4: 0

INT1

ON

ON

AUTO

POS

0 s

MIN

OFF





Power level



Trigger holdoff

Auto range off



Command


Step detection


Setting

UPPER

0

Comments

Range set to upper


1


Table 12-54


Table 12-55 802.11b/g: Power Meter Presets: Window/Measurement Settings


Single Channel

Display setup

Upper window

Lower window



Feed

Measurement


Feed

Measurement


Feed

Measurement


Feed

Measurement

UU Single Numeric

Dual numeric

Gate 1 Channel A

Avg

DEF

DEF

Gate 1 Channel A

Peak

Gate 1 Channel A

Pk-to-Avg


Dual Channel

UU Single Numeric

See Table 12-56


*

Avg

See

Table 12-56

See Table 12-56

See

Table 12-56

See

Table 12-56

See

Table 12-56

See

Table 12-56



Table 12-56 802.11b/g: Power Meter Presets For Secondary Channel Sensors



Sensor

Display setup

Upper window

Lower window

UU Single numeric

Dual numeric


Feed DEF

Dual numeric

Dual numeric


*

Peak


Sensor

Dual numeric

Dual numeric

Gate1 primary channel

*

(Channel A)



Feed


*


*

Pk-to-Avg


*

(Channel B)



Feed


*

Secondary channel

*


* For further information refer to

“Primary and Secondary Channels” on page 526.


*

(Channel B)

Pk-to-Avg



568

1xeV-DO

The following table shows the power meter presets when <character_data> is set to XEVDO. Commands not listed are preset according to their

DEFault


).

Table 12-57 1xeV-DO: Power Meter Presets

Command

Frequency






Setting

+1900.000 MHz

NORM

Comments

Frequency setting

Measurement mode


E9322A/26A: DEF

E9323A/27A: HIGH

N1921/2A: LOW

Gate Setup

[SENS[1]]|SENS2:SWE[1]|2|3|4

:OFF:TIME

[SENS[1]]|SENS2:SWE[1]|2|3|4

:TIME

Trigger setup


INIT:CONT

TRIG[:SEQ]:LEV:AUTO

TRIG[:SEQ]:LEV

TRIG[:SEQ]:SLOP

TRIG[:SEQ]:DEL

TRIG[:SEQ]:HOLD

Range

1


Gate 1: 10 µs

Gates 2 - 4: 0

Gate 1: 810 µs

Gates 2 - 4: 0

INT1

ON

ON

AUTO

POS

0 s

1 ms

OFF





Power level



Trigger holdoff

Auto range off



Command


Step detection


Trace setup




<numeric_value>

Setting

UPPER

0

– 40 µs

1 ms

Comments

Range set to upper



Length of the trace

1



Function

Table 12-58 1exV-DO: Power Meter Presets: Window/Measurement Settings

Setting


Display setup

Upper window

Lower window



Feed

Measurement


Feed

Measurement


Feed

Measurement


Channel A trace

Dual numeric

N/A

N/A

N/A

N/A

Gate 1 Channel A

Avg

Primary channel

*

trace

See Table 12-59

N/A

N/A

N/A

N/A


*

Avg




Feed

Measurement

Single Channel

Gate 1 Channel A

Pk-to-Avg


Dual Channel

See

Table 12-59

See

Table 12-59

Table 12-59 1exV-DO: Power Meter Presets For Secondary Channel Sensors



Sensor

Display setup



Feed


*

Dual numeric

Secondary channel

*




Sensor

Dual numeric


*

(Channel B)

Avg



1xeV-DV

The following table shows the power meter presets when <character_data> is set to XEVDV. Commands not listed are preset according to their

DEFault


).

Table 12-60 1exV-DV: Power Meter Presets

Command

Frequency






Setting

+1900.000 MHz

NORM

Comments

Frequency setting

Measurement mode


E9322A/26A: DEF

E9323A/27A: HIGH

N1921/2A: LOW

Gate Setup

[SENS[1]]|SENS2:SWE[1]|2|3|4

:OFF:TIME

[SENS[1]]|SENS2:SWE[1]|2|3|4

:TIME

Trigger setup


INIT:CONT

TRIG[:SEQ]:LEV:AUTO

TRIG[:SEQ]:LEV

TRIG[:SEQ]:SLOP

TRIG[:SEQ]:DEL

TRIG[:SEQ]:HOLD

Range

1


Gate 1: 10 µs

Gates 2 - 4: 0

Gate 1: 810 µs

Gates 2 - 4: 0

INT1

ON

ON

AUTO

POS

0 s

1 ms

OFF





Power level



Trigger holdoff

Auto range off



Command


Step detection


Trace setup




<numeric_value>

Setting

UPPER

0

– 40 µs

1 ms

Comments

Range set to upper



Length of the trace

1



572

Function

Table 12-61 1xeV-DV: Power Meter Presets: Window/Measurement Settings

Setting


Display setup

Upper window

Lower window



Feed

Measurement


Feed

Measurement


Feed

Measurement


Channel A trace

Dual numeric

N/A

N/A

N/A

N/A

Gate 1 Channel A

Avg

Primary channel

*

trace

See Table 12-62

N/A

N/A

N/A

N/A


*

Avg




Feed

Measurement

Single Channel

Gate 1 Channel A

Pk-to-Avg


Dual Channel

See

Table 12-62

See

Table 12-62

Table 12-62 1xeV-DV: Power Meter Presets For Secondary Channel Sensors



Sensor

Display setup



Feed


*

Dual numeric

Secondary channel

*




Sensor

Dual numeric


*

(Channel B)

Avg



574

TD-SCDMA

The following table shows the power meter presets when <character_data> is set to TDSCdma. Commands not listed are preset according to their

DEFault


).

Table 12-63 TD-SCDMA: Power Meter Presets

Command

Frequency






Setting

+1900.000 MHz

NORM

Comments

Frequency setting

Measurement mode


E9322A/26A: DEF

E9323A/27A: HIGH

N1921/2A: LOW

Gate Setup

[SENS[1]]|SENS2:SWE[1]|2|3|4

:OFF:TIME

[SENS[1]]|SENS2:SWE[1]|2|3|4

:TIME

Trigger setup


INIT:CONT

TRIG[:SEQ]:LEV:AUTO

TRIG[:SEQ]:LEV

TRIG[:SEQ]:SLOP

TRIG[:SEQ]:DEL

TRIG[:SEQ]:HOLD

Range

1


Gate 1: 10 µs

Gates 2 - 4: 0

Gate 1: 810 µs

Gates 2 - 4: 0

INT1

ON

ON

AUTO

POS

0 s

1 ms

OFF





Power level



Trigger holdoff

Auto range off



Command


Step detection


Trace setup




<numeric_value>

Setting

UPPER

0

– 40 µs

1 ms

Comments

Range set to upper



Length of the trace

1



Table 12-64 TD-SCDMA: Power Meter Presets: Window/Measurement Settings


Single Channel

Display setup

Upper window

Lower window



Feed

Measurement


Feed

Measurement


Feed

Measurement


Channel A trace

Dual numeric

N/A

N/A

N/A

N/A

Gate 1 Channel A

Avg

Dual Channel

Primary channel

*

trace

See Table 12-65

N/A

N/A

N/A

N/A


*

Avg




Feed

Measurement

Single Channel

Gate 1 Channel A

Pk-to-Avg


Dual Channel

See

Table 12-65

See

Table 12-65

Table 12-65 TD-SCDMA: Power Meter Presets: Window/Measurement Settings



Sensor

Display setup



Feed


*

Dual numeric

Secondary channel

*




Sensor

Dual numeric


*

(Channel B)

Avg



NADC

The NADC setup provides:

• Average power measurement of both active timeslots in NADC or

IS- 136 “full rate” transmission. This assumes that there are two timeslots to be measured in each frame as for example with timeslots 0 in the following diagram:

IS-136 full rate frame

0 1 2 0 1 2

Figure 12-22A Trace Display Of The Active Timeslots

• A trace display of the active timeslots.

The measurement is started by detecting the RF burst—for example the burst emitted by a mobile—using the internal RF level trigger. The internal level trigger is set to –20 dBm. Time- gating is used to measure the average power in two active timeslots which are separated by two inactive timeslots

The following table shows the power meter presets when <character_data> is set to NADC. Commands not listed are preset according to their DEFault


):

Table 12-66 NADC: Power Meter Presets

Command

Frequency





Setting

+800.000 MHz

NORM

Comments

Frequency setting

Measurement mode



578

Command


Gate Setup

[SENS[1]]|SENS2:SWE[1]|2|3|4

:OFF:TIME

[SENS[1]]|SENS2:SWE[1]|2|3|4

:TIME

Trigger setup


INIT:CONT

TRIG[:SEQ]:LEV:AUTO

TRIG[:SEQ]:LEV

TRIG[:SEQ]:SLOP

TRIG[:SEQ]:DEL

TRIG[:SEQ]:HOLD

Range

1



Step detection


Trace setup






<numeric_value>

OFF

UPPER

1

+20 dBm

-35 dBm

-0.2 ms

28 ms

INT1

ON

OFF

-15 dBm

POS

0 s

30 ms

Setting

E9321A/25A: OFF

E9322A/26A: OFF

E9323A/27A: OFF

N1921/2A: OFF

Gate 1: 123.5 µ s

Gate 2: 20.123 ms

Gates 3 - 4: 0

Gate 1: 6.46 ms

Gate 2: 6.46 ms

Gates 3 - 4: 0

Comments






Power level



Trigger holdoff

Auto range off

Range set to upper


Maximum power

Minimum power


Length of the trace



1

The Range setting in Table 12-66 is only applicable for E-Series power sensor and N8480 Series power sensor (excluding Option CFT).

Table 12-67 NADC: Power Meter Presets: Window/Measurement Settings


Single Channel

Display setup

Upper window

Lower window



Feed

Measurement


Feed

Measurement


Feed

Measurement


Feed

Measurement

Channel A trace

Dual numeric

N/A

N/A

N/A

N/A

Gate 1 Channel A

Avg

Gate 2 Channel A

Avg


Dual Channel

Primary channel

*

trace

See Table 12-68

N/A

N/A

N/A

N/A


*

Avg

See

Table 12-68

See Table 12-68

Function

Table 12-68 NADC: Power Meter Presets For Secondary Channel Sensors



Sensor


Sensor

Display setup





Sensor

Dual numeric Lower window Dual numeric


Feed


*

Secondary channel

*

Measurement Avg Avg



Sensor

Dual numeric


*

(Channel B)

Avg



iDEN

The iDEN setup 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.

Time gating is used to measure the average power in the following 15 ms

(data pulse). Gate 1 is used to measure this data pulse. The 90 ms frame is also captured to measure the average power in the entire frame. Gate 2 is used to measure the 90 ms frame.

The following table shows the power meter presets when <character_data> is set to IDEN. Commands not listed are preset according to their DEFault


):

Table 12-69 iDEN: Power Meter Presets

Command

Frequency






Setting

+800.000 MHz

NORM

Comments

Frequency setting

Measurement mode

Sensor video bandwidth E9321A/25A: OFF

E9322A/26A: OFF

E9323A/27A: OFF

N1921/2A: OFF

Gate Setup

[SENS[1]]|SENS2:SWE[1]|2|3|4

:OFF:TIME

Gate 1: 0 µ s

Gates 2 - 4: 0




582

Command

[SENS[1]]|SENS2:SWE[1]|2|3|4

:TIME

Trigger setup


INIT:CONT

TRIG[:SEQ]:LEV:AUTO

TRIG[:SEQ]:LEV

TRIG[:SEQ]:SLOP

TRIG[:SEQ]:DEL

TRIG[:SEQ]:HOLD

Range

1



Averaging

[SENSe[1]]|SENSe2:AVER[:STATe]

[SENSe[1]]|SENSe2:AVER:COUN

Step detection


Trace setup






<numeric_value>

Setting

Gate 1: 15 ms

Gate 2: 90 ms

Gate 3: 160 µ s

Gate 4: 0

INT1

ON

OFF

-15 dBm

POS

0 s

20 ms

OFF

UPPER

ON

64

1

+20 dBm

-30 dBm

0 s

100 ms

Comments







Trigger holdoff

Auto range off

Range set to upper

Averaging On

Averaging set to 64


Maximum power

Minimum power


Length of the trace

1





Table 12-70 iDEN: Power Meter Presets: Window/Measurement Settings


Single Channel

Display setup

Upper window

Lower window



Feed

Measurement


Feed

Measurement


Feed

Measurement


Feed

Measurement

UU single numeric

Dual numeric

Gate 1 Channel A

Avg

DEF

DEF

Gate 1 Channel A

Peak

Gate 1 Channel A

Pk-to-Avg


Dual Channel

See Table 12-71

See Table 12-71


*

Avg

See

Table 12-71

See Table 12-71

See

Table 12-71

See

Table 12-71

See

Table 12-71

See

Table 12-71

Function

Table 12-71 iDEN: Power Meter Presets For Secondary Channel Sensors



Sensor


Sensor

Display setup

Upper window UU single numeric Dual numeric Dual numeric





Sensor

Dual numeric Lower window Dual numeric


Feed DEF


*

Peak


Sensor

Dual numeric


*

(Channel A)



Feed


*


*

Pk-to-Avg

Gate1 secondary channel*

(Channel B)



Feed


*

Secondary channel

*


*

(Channel B)





DVB

The following table shows the power meter presets when <character_data> is set to DVB. Commands not listed are preset according to their DEFault


).

Table 12-72 DVB: Power Meter Presets

Command

Frequency






Setting

+660.000 MHz

NORM

Comments

Frequency setting

Measurement mode


E9322A/26A: DEF

E9323A/27A: DEF

N1921/2A: OFF

Gate Setup

[SENS[1]]|SENS2:SWE[1]|2|3|4

:OFF:TIME

[SENS[1]]|SENS2:SWE[1]|2|3|4

:TIME

Trigger setup


INIT:CONT

TRIG[:SEQ]:LEV:AUTO

TRIG[:SEQ]:LEV

TRIG[:SEQ]:SLOP

TRIG[:SEQ]:DEL

Gate 1: 10 µ s

Gate 2: 0

Gates 3 - 4: 0

Gate 1: 15 ms

Gate 1: 90 ms

Gates 2 - 4: 0

INT1

ON

OFF

-15 dBm

POS

0 s





Power level





586

Command

TRIG[:SEQ]:HOLD

Range

1



Step detection


Setting

20 ms

OFF

UPPER

1

Comments

Trigger holdoff

Auto range off

Range set to upper


Function

1




Table 12-73 DVB: Power Meter Presets: Window/Measurement Settings

Setting


Display setup

Upper window

Lower window



Feed

Measurement


Feed

Measurement


Feed

Measurement


Feed

Measurement

UU single numeric

Dual numeric

Gate 1 Channel A

Avg

DEF

DEF

Gate 1 Channel A

Pk-to-Avg

Gate 2 Channel A

Avg

See Table 12-74

See Table 12-74


*

Avg

See

Table 12-74

See Table 12-74

See

Table 12-74

See

Table 12-74

See

Table 12-74

See Table 12-74




Table 12-74 DVB: Power Meter Presets For Secondary Channel Sensors



Sensor

Display setup




Feed DEF

Dual numeric

Dual numeric


*

Pk-to-Avg


Sensor

Dual numeric

Dual numeric


*

(Channel A)

Pk-to-Avg Measurement DEF


Feed


*


*

Avg


*

(Channel B)

Avg Measurement Pk-to-Avg


Feed


*

Secondary channel

*

Measurement Avg Avg



*

(Channel B)

Pk-to-Avg



588

WiMAX

The following table shows the power meter presets when <character_data> is set to WIMAX. Commands not listed are preset according to their

DEFault


).

Table 12-75 WiMAX: Power Meter Presets

Command

Frequency






Gate Setup

[SENS[1]]|SENS2:SWE[1]|2|3|4

:OFF:TIME

[SENS[1]]|SENS2:SWE[1]|2|3|4

:TIME

Trigger setup


INIT:CONT

TRIG[:SEQ]:LEV:AUTO

TRIG[:SEQ]:LEV

TRIG[:SEQ]:SLOP

TRIG[:SEQ]:DEL

Setting

+3.5 GHz

NORM

E9321A/25A: DEF

E9322A/26A: DEF

E9323A/27A: DEF

N1921/2A: HIGH

INT1

ON

ON

AUTO

POS

0 s

Gate 1: 0

Gates 2: 102 µ s

Gates 3- 4: 0

Gate 1: 102 µ s

Gate 2: 306 µ s

Gates 3- 4: 0

Comments

Frequency setting

Measurement mode






Power level





Command

TRIG[:SEQ]:HOLD

Range

1



Step detection


Trace setup




<numeric_value>

Setting

4 ms

OFF

UPPER

0

-0.2 ms

3 m s

Comments

Trigger holdoff

Auto range off

Range set to upper



Length of the trace

Function

1




Table 12-76 WiMAX: Power Meter Presets: Window/Measurement Settings

Setting


Display setup

Upper window

Lower window



Feed

Measurement


Feed

Measurement


Feed

Dual numeric

Dual numeric

Gate 1 Channel A

Avg

Gate 1 Channel A

Pk-to-Avg

Gate 2 Channel A

See

Table 12-77

See Table 12-77


*

Avg

See

Table 12-77

See

Table 12-77

See

Table 12-77




Measurement


Feed

Measurement

Single Channel

Avg

Gate 2 Channel A

Pk-to-Avg


Dual Channel

See Table 12-77

See

Table 12-77

See

Table 12-77

Table 12-77 WiMAX: Power Meter Presets For Secondary Channel Sensors



Sensor

Display setup

Upper window Dual numeric


Upper window/lower measurement (UL)

Feed


*


Lower window/upper measurement (LU)

Feed


*

Dual numeric

Dual numeric


*

Pk-to-Avg


*

Avg


Sensor

Dual numeric

Dual numeric


*

Pk-to-Avg


*

(Channel B)

Avg Measurement Avg


Feed


*

Secondary channel

*




*

(Channel B)

Pk-to-Avg



DME

The following table shows the power meter presets when <character_data> is set to DME. Commands not listed are preset according to their DEFault


).

Table 12-78 DME: Power Meter Presets

Command

Frequency






Setting

+1.1 GHz

NORM

Comments

Frequency setting

Measurement mode

Sensor video bandwidth E9321A/25A: OFF

E9322A/26A: OFF

E9323A/27A: OFF

N1921/2A: OFF

Gate Setup

[SENS[1]]|SENS2:SWE[1]|2|3|4

:OFF:TIME


[SENS[1]]|SENS2:SWE[1]|2|3|4

:TIME

Gate 1: -2 µ s

Gate 2: 8 µ s

Gate 3: 0

Gate4: 0

Gate 1: 8 µ s

Gate 2 : 50 µ s

Gate 3: 0

Gate 4: 0


Trigger setup


INIT:CONT

TRIG[:SEQ]:LEV:AUTO

TRIG[:SEQ]:LEV

TRIG[:SEQ]:SLOP

TRIG[:SEQ]:DEL

INT1

ON

ON

AUTO

POS

0 s



Power level





Command

TRIG[:SEQ]:HOLD

Range

1



Video averaging setup



Step detection


Trace setup

SENS[1]|2:TRAC:LIM:UPP

SENS[1]|2:TRAC:LIM:LOW




<numeric_value>

Reference level setup

TRAC[1]|2:DEF:TRAN:REF

TRAC[1]|2:DEF:DUR:REF

1 %, 81%

25%

Setting

50 μs

OFF

UPPER

1

32

1

+20 dBm

-30 dBm

-3

μs

53

μs

Comments

Trigger holdoff

Auto range off

Range set to upper

Video averaging is enabled

Length of video filter


Maximum power

Minimum power


Length of the trace

Transition reference levels

Pulse duration reference level

1



592

Function

Display setup

Upper window

Lower window

Table 12-79 DME: Power Meter Presets: Window/Measurement Settings

Setting


Channel A trace

Dual numeric

See Table 12-80

Dual numeric







Feed

Measurement


Feed

Measurement


Feed

Measurement


Feed

Measurement

Gate 1 Channel A

Avg

Gate 2 Channel A

Avg

Gate 1 Channel A

Peak

Gate 2 Channel A

Peak

See

Table 12-80

See Table 12-80

See

Table 12-80

See Table 12-80

See

Table 12-80

See

Table 12-80

See

Table 12-80

See

Table 12-80

Table 12-80 DME: Power Meter Presets For Secondary Channel Sensors



Sensor

Display setup

Upper window

Lower window

Primary channel trace

*

Dual numeric

Upper window/upper measurement (UU)

Feed


*

Measurement Avg

Upper window/lower measurement (UL)

Feed


*

Measurement Avg


Dual numeric

Single numeric


*

Peak


*

Peak


Sensor

Dual numeric

Dual numeric


*

Peak


*

Peak



Function

Feed


No Sensor


*


Sensor

Secondary channel

*

Avg


Sensor


*

(Channel B)

Peak Measurement Peak


Feed


*


*


*

(Channel B)

Peak Measurement Peak Avg




DME-PRT

The following table shows the power meter presets when <character_data> is set to DME-PRT. Commands not listed are preset according to their

DEFault


).

Table 12-81 DME-PRT: Power Meter Presets

Command

Frequency






Setting

+1.1 GHz

NORM

Comments

Frequency setting

Measurement mode


E9322A/26A: DEF

E9323A/27A: OFF

N1921/2A: OFF

Gate Setup

[SENS[1]]|SENS2:SWE[1]|2|3|4

:OFF:TIME


[SENS[1]]|SENS2:SWE[1]|2|3|4

:TIME

Gate 1: 0 µs

Gate 2: 8 µs

Gate 3: 0

Gate4: 0

Gate 1: 6 µs

Gate 2 : 50 µs

Gate 3: 0

Gate 4: 0


Trigger setup


INIT:CONT

TRIG[:SEQ]:LEV:AUTO

TRIG[:SEQ]:LEV

TRIG[:SEQ]:SLOP

TRIG[:SEQ]:DEL

INT1

ON

ON

AUTO

POS

0 s



Power level





Command

TRIG[:SEQ]:HOLD

Range

1



Video averaging setup



Step detection


Trace setup

SENS[1]|2:TRAC:LIM:UPP

SENS[1]|2:TRAC:LIM:LOW




<numeric_value>

Reference level setup

TRAC[1]|2:DEF:TRAN:REF

TRAC[1]|2:DEF:DUR:REF

0.25%, 9%

25%

Setting

50 µs

OFF

UPPER

1

32

0

+20 dBm

-30 dBm

-2 µs

5 µs

Comments

Trigger holdoff

Auto range off

Range set to upper

Video averaging is enabled

Length of video filter


Maximum power

Minimum power


Length of the trace

Transition reference levels

Pulse duration reference level

1



596

Function

Display setup

Upper window

Lower window

Table 12-82 DME-PRT: Power Meter Presets: Window/Measurement Settings

Setting


Channel A trace

Dual numeric

See Table 12-83

Dual numeric







Feed

Measurement


Feed

Measurement


Feed

Measurement


Feed

Measurement

Gate 1 Channel A

Avg

Gate 2 Channel A

Avg

Gate 1 Channel A

Peak

Gate 2 Channel A

Peak

See Table 12-83

See Table 12-83

See Table 12-83

See Table 12-83

See Table 12-83

See Table 12-83

See Table 12-83

See Table 12-83

Table 12-83 DME-PRT: Power Meter Presets For Secondary Channel Sensors



Sensor

Display setup

Upper window

Lower window

Primary channel trace

*

Dual numeric

Upper Window/upper measurement (UU)

Feed


*

Measurement Avg


Feed


*

Measurement Avg


Dual numeric

Single numeric


*

Peak


*

Peak


Sensor

Dual numeric

Dual numeric


*

Peak


*

Peak



Function

Feed


No Sensor


*


Sensor

Secondary channel

*

Avg


Sensor


*

(Channel B)

Peak Measurement Peak


Feed


*


*


*

(Channel B)

Peak Measurement Peak Avg




HSDPA

The following table shows the power meter presets when <character_data> is set to HSDPA. Commands not listed are preset according to their

DEFault values (for further information refer to

Table 12- 26

):

Table 12-84 HSPDA: Power Meter Presets

Command

Frequency






Setting

+1900.000 MHz

NORM

Comments

Frequency setting

Measurement mode


E9322A/26A: DEF

E9323A/27A: OFF

N1921/2A: OFF

Gate Setup

[SENS[1]]|SENS2:SWE[1]|2|3|4

:OFF:TIME

[SENS[1]]|SENS2:SWE[1]|2|3|4

:TIME

Trigger setup


INIT:CONT

TRIG[:SEQ]:LEV:AUTO

TRIG[:SEQ]:LEV

TRIG[:SEQ]:SLOP

TRIG[:SEQ]:DEL

TRIG[:SEQ]:HOLD

Range

1

Gate 1: 0 s

Gates 2 - 4: 0

Gate 1: 10 ms

Gates 2 - 4: 0

INT1

ON

ON

AUTO

POS

0 s

1 µs








Trigger holdoff



Command



Step detection


Setting

OFF

UPPER

0

Comments

Auto range off

Range set to upper


1


Table 12-84


Table 12-85 HSPDA: Power Meter Presets: Window/Measurement Settings


Single Channel

Display setup

Upper window

Lower window



Feed

Measurement


Feed

Measurement


Feed

Measurement


Feed

Measurement

UU single numeric

Dual numeric

Gate 1 Channel A

Avg

DEF

DEF

Gate 1 Channel A

Peak

Gate 1 Channel A

Pk-to-Avg


Dual Channel

See Table 12-86

See Table 12-86


*

Avg

See Table 12-86

See Table 12-86

See Table 12-86

See Table 12-86

See Table 12-86

See Table 12-86



Table 12-86 HSDPA: Power Meter Presets For Secondary Channel Sensors



Sensor

Display setup

Upper window

Lower window

UU single numeric

Dual numeric


Feed DEF

Dual numeric

Dual numeric


*

Peak


Sensor

Dual numeric

Dual numeric


*

(Channel A)



Feed


*


*

Pk-to-Avg


*

(Channel B)



Feed


*

Secondary channel

*




*

(Channel B)

Pk-to-Avg



LTE

The following table shows the power meter presets when <character_data> is set to LTE. Commands not listed are preset according to their DEFault


).

Table 12-87LTE: Power Meter Presets

Command

Frequency






Gate Setup

[SENS[1]]|SENS2:SWE[1]|2|3|4

:OFF:TIME

[SENS[1]]|SENS2:SWE[1]|2|3|4

:TIME

Trigger Setup


INIT:CONT

TRIG[:SEQ]:LEV:AUTO

TRIG[:SEQ]:LEV

TRIG[:SEQ]:SLOP

TRIG[:SEQ]:DEL

TRIG[:SEQ]:HOLD

Range

1

Setting

+2.0 GHz

NORM

E9321A/25A: DEF

E9322A/26A: DEF

E9323A/27A: DEF

N1920A: HIGH

Gate 1-4: 0

Gate 1: 1.2 m s

Gate 2: 10.0 ms

Gates 3-4: 0

INT1

ON

ON

AUTO

POS

0 s

4 ms

Comments

Frequency setting

Measurement mode






Power level



Trigger holdoff



Command



Step detection


Trace setup




<numeric_value>

Setting

OFF

UPPER

0

–0.2 ms

11.0 m s

Comments

Auto range off

Range set to upper

Step detection is disabled


Length of the trace

Function

1




Table 12-88 LTE: Power Meter Presets: Window/Measurement Settings

Setting


Display setup

Upper window

Lower window



Feed

Measurement


Feed

Measurement


Feed

Measurement


Channel A trace

Dual numeric

N/A

N/A

N/A

N/A

Gate 1 Channel A

Avg

Primary channel

*

trace

See Table 12-89

N/A

N/A

N/A

N/A

See

Table 12-89

See Table 12-89



Function

Feed

Measurement

Setting

Single Channel

Gate 1 Channel A

Pk-to-Avg

Dual Channel

See

Table 12-89

See

Table 12-89

Table 12-89 LTE: Power Meter Presets For Secondary Channel Sensors



Sensor

Display setup



Feed


*

Measurement Avg


Feed


*


Dual numeric


Avg

*


*

Pk-to-Avg



Sensor

Dual numeric


*

Avg


*

Pk-to-Avg



SYSTem:REMote

This command locks the power meter front panel keypad excepting the

Local key. The power meter display status reporting line shows “RMT”.

Local front panel operation of the power meter is inhibited but can be enabled by pressing the Local key.

Syntax

SYST :REM

Example

SYST:REM This command locks the power meter front panel keypad excepting the Local key.



SYSTem:RWLock

This command locks out the front panel keypad - including the front panel Local key. The power meter display status reporting line shows

“RMT” . In this state the power meter cannot be returned to manual control from the front panel.

Syntax

SYST :RWL

Example

SYST:RWL This command locks the power meter front panel keypad - including the Local key.



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

SYST :VERS ?

Example

SYST:VERS?

This command queries which version of

SCPI is used in the power meter.







13

TRACe Subsystem

TRACe Subsystem 610

TRACe[1]|2[:DATA]? <character_data> 612

TRACe[1]|2:DEFine:DURation:REFerence<numeric_value> 614

TRACe[1]|2:DEFine:TRANsition:REFerence <numeric_value>,

<numeric_value> 616

TRACe[1]|2:MEASurement:INSTant:REFerence? <numeric_value> 618

TRACe[1]|2:MEASurement:PULSe[1]|...|10:DCYCle?

620

TRACe[1]|2:MEASurement:PULSe[1]|...|10:DURation?

622

TRACe[1]|2:MEASurement:PULSe[1]|...|10:PERiod?

624

TRACe[1]|2:MEASurement:PULSe[1]|...|10:SEParation?

626

TRACe[1]|2:MEASurement:TRANsition[1]|...|10:NEGative:DURation?

6

28

TRACe[1]|2:MEASurement:TRANsition[1]|...|10:NEGative:OCCurrence?

630

TRACe[1]|2:MEASurement:TRANsition[1]|...|10:POSitive:DURation?

63

2

TRACe[1]|2:MEASurement:TRANsition[1]|...|10:POSitive:OCCurrence?

634

TRACe[1]|2:MEASurement:REFerence? <numeric_value> 636

TRACe[1]|2:STATe <boolean> 638

TRACe[1]|2:UNIT <character_data> 640

This chapter explains how to use the TRACe command subsystem to configure and read back the measured power trace.


609

13 TRACe Subsystem

TRACe Subsystem

N O T E

This command can only be used with P-Series and E9320 sensors. The E9320 sensor must be set to NORMal mode.

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 predefined TRACE blocks:

• TRACe1: associated with Channel A

• TRACe2: associated with Channel B

The following commands are described in this chapter:

Parameter Form Notes Keyword

TRACe[1]|2

[:DATA]?

:DEFine

:DURation

:REFerence

:TRANsition

:REFerence

:MEASurement

:INSTant

:REFerence?

:PULse[1]|...|10

:DCYCle?

:DURation?

:PERiod?

<character_data>

<numeric_value>

<numeric_value>,

<numeric_value>

<numeric_value>

[query only]

[query only]

[query only]

[query only]

Page

page 612

page 614

page 616

page 618

page 620

page 622

page 624


TRACe Subsystem 13

Keyword

:SEParation?

:TRANsition[1]|...|10

:NEGative

:DURation?

:OCCurrence?

:POSitive

:DURation?

:OCCurrence?

:REFerence?

:STATe

:UNIT

Parameter Form

<numeric_value>

<boolean>

<character_data>

N O T E

Notes

[query only]

[query only]

[query only]

[query only]

[query only]

[query only]

Page

page 626

page 628

page 630

page 632

page 634

page 636

page 638

page 640

When making trace measurements, use the following command sequence to synchronize the returned trace data with the measurement:

Command

TRIG:SOUR INT or

TRIG:SOUR EXT

INIT:CONT OFF

TRAC:STAT ON

1

AVER:STAT OFF or

TRIG:DEL:AUTO OFF

INIT

FETCH?

TRACE:DATA? MRES

1

Comment

Change trigger source to internal or external

Trace data can only be retrieved with

INIT:CONT OFF

Enables trace capture

No settling time delays for digital filter to fill

Initiates a new measurement

Fetch the result (waits for the measurement to complete)

Retrieves the trace data once the measurement has completed

1

A trace display format must be set when this command is used.



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) contained in the block.

The number of y digits

Line feed character signifies the end of the block

Data bytes

Signifies the start of the block

Example: if there are 12435 data bytes, y = 12435 and x = 5

Each point in the trace is represented as an IEEE 754 32 bit floating point number, made up of four bytes in the data block. The MS byte is transmitted first. Each complete block is terminated by a line feed.

TRACe data formatting is not affected by FORMat subsystem formatting.

N O T E

Syntax

TRAC 1

2

:DATA ?




Parameters

Item Description/Default character_data • HRESolution: high resolution. The complete capture buffer at the internal sample rate. The number of points in this trace is not fixed, as it is affected by the

SENS:TRACe:TIMe setting.

• MRESolution: medium resolution. A subset of the capture buffer - the buffer contents are decimated

1 to 1000 data points.

• LRESolution: low resolution. A subset of the capture buffer - the buffer contents are decimated

1

to provide 230 data points. This is the same number of data points as the power meter uses to display the trace on the front panel.

Hence, the LRES command can be used to replicate the power meter’s display.

Range of

Values

HRES

MRES

LRES

Example

TRAC:DATA? HRES This command returns the trace data for

Channel A at high resolution.

Error Messages

If TRAC:STAT is off, the error –221, “Settings Conflict” occurs.



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

TRAC 1

2

:DEF :DUR :REF Space

?

numeric_value

Parameters

Item Description/Default numeric_value Reference levels to be used in calculation of pulse duration

Range of

Values

0 to 100

DEF



Example

TRAC1:DEF:DUR:REF 25

TRAC1:DEF:DUR:REF DEF

This command sets trace 1 pulse duration measurements to look for the 25 % reference levels.

This command sets trace 1 pulse duration measurements to look for the 50 % reference levels.

Reset condition

On reset, the reference level will become 50 %, which is the default value

(DEF).

Query

TRACe[1]|2:DEFine:DURation:REFerence?

The query returns the numeric value of the reference level used in the pulse duration calculation.

Query Example

TRAC1:DEF:DUR:REF?

This command queries the value of the reference level used in pulse duration measurement for trace 1.



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 1

2

:DEF :TRAN :REF Space numeric_value

?

numeric_value

Parameters

Item Description/Default numeric_value Reference levels to be used in calculation of transition durations and occurences

Range of

Values

0 to 100

DEF



Example

TRAC1:DEF:TRAN:REF 1,18

TRAC1:DEF:TRAN:REF

DEF,DEF

This command sets trace 1 transition measurements to look for the 1 % and 81 % reference levels.

This command sets trace 1 transition measuremetns to look for the 10 % and 90

% reference levels.

Reset Condition

On reset, the reference level will set to 10 % and 90 % respectively.

Query

TRACe[1]|2:DEFine:TRANsition:REFerence?

The query returns trace 1 reference levels used in the transition occurences calculation.

Query Example

TRAC1:DEF:TRAN:REF?

This command queries the reference levels used in the calculation of transition durations and occurrences for trace 1.



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.

N O T E

This command is only applicable when P-Series power sensors are used with single or continuous triggered acquisition is selected.

Syntax

TRAC

2

1 :MEAS :INST :REF ?

Space numeric_value

Parameters

Item Description/Default numeric_value Reference level in percentage

Range of

Values

– 25 to 125



Example

TRAC1:MEAS:INST:REF? 25 This command return the time instant for 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.


TRACe[1]|2:MEASurement:PULSe[1]|...|10:DCYCle?

This command returns the duty cycle of the selected pulse in percentage.

Algorithm

Duty Cycle = (pulse duration / pulse period) * 100 where, pulse duration is the time difference between positive and negative transitions of one pulse and pulse period is the time difference between two consecutive transition occurrences of the same polarity.

Syntax

TRAC 1

2

:MEAS :PULS 1

2|...|10

:DCYC ?

Example

TRAC2:MEAS:PULS3:DCYC?

This command returns the duty cycle of the 3rd pulse found on trace 2.

Error Messages

• The command is only applicable when N192x or E932x Sensors are


N O T E present, otherwise Error –241, "Hardware Missing" is generated.

• If free run acquisition is selected or sensor average mode selected,

Error –221 "Settings Conflict" occurs.

If you attempt to measure a pulse out of the range of the capture, for example, measure the

5th pulse and there are only 4 pulses displayed, the power meter returns #0##9.91E37 as the result.



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 transition occurs else

PULSe:DURation = time the second negative transition occurs - time the

first positive transition occurs.

Syntax

TRAC 1

2

:MEAS :PUL S 1

2|...|10

:DUR ?

Example

TRAC2:MEAS:PULS3:DUR?

This command returns the duration of the 3rd pulse found on trace 2.



N O T E

Error Messages


• 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, measure the 5th pulse and there are only 4 pulses displayed, the power meter returns #0##9.91E37 as the result.



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


PULSe:PERiod = time the second positive transition occurrence - time the first positive transition occurs else

PULSe:PERiod = time the second negative transition occurs - time the first

negative transition occurs.

Syntax

TRAC 1

2

:MEAS :PULS 1

2|...|10

:PER ?

Example

TRAC:MEAS:PULS:PER?

This command returns the period of the pulse found on trace 1.



N O T E

Error Messages






TRACe[1]|2:MEASurement:PULSe[1]|...|10:SEParation?

This command returns the time difference of the n th

and (n+1) th

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.

Algorithm


PULSe:SEParation = time the second positive transition occurs - time the first negative transition occurs else

PULSe:SEParation = time the first positive transition occurs - time the first

negative transition occurs.

Syntax

TRAC 1

2

:MEAS :PULS 1

2|...|10

:SEP ?

Example

TRAC1:MEAS:PULS:SEP?

This command returns the time separation of the 1st and 2nd pulses found on trace 1.



N O T E

Error Messages






TRACe[1]|2:MEASurement:TRANsition[1]|...|10:NEGative:DUR ation?

This command returns the n th

negative transition duration found on a trace.

TRAC

Syntax

1

2

:MEAS :TRAN 1

2|...|10

:NEG :DUR ?

Reset Condition


Example

TRAC:MEAS:TRAN8:NEG:DUR?

This command returns the 8th negative transition duration found on trace 1.

Error Messages





N O T E


5th pulse and there are only 4 pulses displayed, the power meter returns #0#0#0 as the result.



TRACe[1]|2:MEASurement:TRANsition[1]|...|10:NEGative:OCC urrence?

This command returns the position, relative to the trigger instant, of the n th

occurrence of a negative transition found on a trace.

TRAC

Syntax

1

2

:MEAS :TRAN 1

2|...|10

:NEG :OCC ?

630

Reset Condition


Example

TRAC2:MEAS:TRAN7:NEG:OCC?

This command returns the position, relative to the trigger instant, of the 7th occurrence of a negative transition found on trace 2.

Error Messages





N O T E





TRACe[1]|2:MEASurement:TRANsition[1]|...|10:POSitive:DURa tion?

This command returns the n th

positive transition duration found on a trace.

TRAC

Syntax

1

2

:MEAS :TRAN 1

2|...|10

:POS :DUR ?

632

Reset Condition


Example

TRAC:MEAS:TRAN10:POS:DUR?

This command returns the 10th positive transition duration found on trace 1.

Error Messages


• If a P- Series sensor is connected and Free Run trigger acquisition is selected, error –221, “Settings conflict” occurs.



N O T E





TRACe[1]|2:MEASurement:TRANsition[1]|...|10:POSitive:OCCu rrence?

This command returns the position, relative to the trigger instant, of the n th

occurrence of a positive transition found on a trace.

TRAC

Syntax

1

2

:MEAS :TRAN 1

2|...|10

:POS :OCC ?

634

Reset Condition


Example

TRAC2:MEAS:TRAN:POS:OCC?

This command returns the position, relative to the trigger instant, of the 1st occurrence of a positive transition found on trace 2.

Error Messages


• If a P- Series sensor is connected and Free Run trigger acquisition is selected, error –221, “Settings conflict” occurs.



N O T E

TIf you attempt to measure a pulse out of the range of the capture, for example, measure the 5th pulse and there are only 4 pulses displayed, the power meter returns #0#0#0 as the result.



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 %.

Algorithm

P x%

= P

0%

+ x/100 (P

100%

- P

0%

) where:

• 0 % <= x <= 100 %

• P

0%

= level of low state

• P

100%

= level of high state

• P

0%

, P

100%

and P x%

are all in the same unit of measurement, for example, Watts.

Syntax

TRAC 1

2

:MEAS :REF ?

numeric_value

Reset Condition




Example

TRAC2:MEAS:REF? 100 This command returns the high state power for trace 2.

Error Messages





TRACe[1]|2:STATe <boolean>

This command enables or disables trace capture for the specified channel.

N O T E

This command does not allow the setting set to ON when either measurement channel (for dual channel) is configured to initiate trigger buffering.

638

Syntax

TRAC 1

2

:STAT Space

?

0|OFF

1|ON

Example

TRAC2:STAT 1 This command enables trace capture for

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 not trace capture is enabled or disabled.



• 1 is returned when trace capture is enabled

• 0 is returned when trace capture is disabled

Query Example

TRAC1:STAT?

This command queries the current state of trace capture for Channel A.

Error Messages

• If a P- Series or E- Series E9320 sensor is not connected, error –241,


• If an E- Series E9320 sensor is connected and set to AVERage mode rather than NORMal mode, error –221, “Settings conflict” occurs.

• If source is set to ON ( for dual channel, at either measurement channel) when the N1920 sensor is connected in normal mode and

SENse:BUFFer:COUNt or SENse:FREQuency:STEP is more than 1, error –221, “Settings conflict” occurs.



TRACe[1]|2:UNIT <character_data>

This command sets the units for the trace for the specified channel

N O T E

This command is included for compatibility purposes only. It has the same purpose as

[SENSe[1]]|SENSe2:TRACe:UNIT <character_data> , which should be the preferred command.

Syntax

TRAC 1

2

:UNIT Space

?

character_data

Parameters

Item character_data


• DBM: dBm

• W: Watts

Range of Values

DBM

W

Example

TRAC2:UNIT W This command sets the trace units for

Channel B Watts.



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

TRAC2:UNIT?

This command queries the current trace units for Channel B.







14


TRIGger Subsystem 644

ABORt[1]|2] 646

INITiate Commands 647

INITiate[1]|2:CONTinuous <boolean> 648

INITiate[1]|2[:IMMediate] 651

INITiate:CONTinuous:ALL <boolean> 652

INITiate:CONTinuous:SEQuence[1]|2 <boolean> 654

INITiate[:IMMediate]:ALL 656

INITiate[:IMMediate]:SEQuence[1]|2 657

TRIGger Commands 658

TRIGger[1]|2:DELay:AUTO <boolean> 659

TRIGger[1]|2[:IMMediate] 661

TRIGger[1]|2:SOURce

BUS|EXTernal|HOLD|IMMediate|INTernal[[1]|2] 662

TRIGger[:SEQuence]:DELay <numeric_value> 665

TRIGger[:SEQuence]:HOLDoff <numeric_value> 667

TRIGger[:SEQuence]:HYSTeresis <numeric_value> 669

TRIGger[:SEQuence]:LEVel <numeric_value> 671

TRIGger[:SEQuence]:LEVel:AUTO <boolean> 673

TRIGger[:SEQuence]:SLOPe <character_data> 675

TRIGger[:SEQuence[1]|2]:COUNt <numeric_value> 677

TRIGger[:SEQuence[1]|2]:DELay:AUTO <boolean> 680

TRIGger[:SEQuence[1]|2]:IMMediate 682

TRIGger[:SEQuence[1]|2]:SOURce

BUS|EXTernal|HOLD|IMMediate|INTernal[[1]|2] 683

This chapter explains how the TRIGger command subsystem is used to synchronize device actions with events.


643

14 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.

Keyword

ABORt[1]|2

INITiate[1]|2

:CONTinuous

[:IMMediate]

INITiate

:CONTinuous

:ALL

:SEQuence[1]|2

[:IMMediate]

:ALL

:SEQuence[1]|2

TRIGger[1]|2

:DELay

:AUTO

[:IMMediate]

:SOURce

TRIGger

[:SEQuence]

:DELay

:HOLDoff

:HYSTeresis

:LEVel

Parameter Form

<boolean>

<boolean>

<boolean>

Notes

[no query]

[non-SCPI]

[no query]

Page

page 646

page 648

page 651

[no query]

[no query]

page 652

page 654

page 656

page 657

<boolean>

BUS|EXTernal|HOLD|

IMMediate|INTernal[[1]|2]

[no query]

page 659

page 661

page 662

<numeric_value>

<numeric_value>

<numeric_value>

<numeric_value>

page 665

page 667

page 669

page 671


TRIGger Subsystem 14

Keyword

:AUTO

:SLOPe

[:SEQuence[1]|2]

:COUNt

:DELay

:AUTO

:IMMediate

:SOURce

Parameter Form

<boolean>

<character_data>

<numeric_value>

<boolean>

BUS|EXTernal|HOLD|

IMMediate|INTernal[[1]|2]

Notes

[no query]

Page

page 673

page 675

page 677

page 680

page 682

page 683

Many of the above commands contain a numeric which represents a channel number. For example TRIGger1 and TRIGger2 represent Channel

A and Channel B respectively. Channel B commands cannot be used with the single Channel N1911A power meter and result in the error “Header suffix out of range.”



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.

If INITiate:CONTinuous is ON, then after ABORt the specified channel immediately goes into the wait for trigger state.

Syntax

ABOR 1

2

Example

ABOR This command places Channel A in the idle state.



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.


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



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. For other trigger sources, INITiate:CONTinuous is set to ON.

If INITiate:CONTinuous is set to:

• OFF, the trigger system remains in the idle state until it is set to ON, or

INITiate:IMMediate is received. Once this trigger cycle is complete the trigger system returns to the idle state.

• ON, the trigger system is initiated and exits the idle state. On completion of each trigger cycle, the trigger system immediately commences another trigger cycle without entering the idle state.

N O T E

This command performs the same function as

INITiate:CONTinuous:SEQuence[1]|2 <boolean> .



Syntax

INIT

2

1 :CONT Space

?

0|OFF

1|ON

Example

INIT2:CONT ON This command places Channel B in the wait 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. For other trigger sources,

INITiate:CONTinuous is set to ON.

Query

INITiate[1]|2:CONTinuous?

The query enters a 1 or 0 into the output buffer.

• 1 is returned when there is continuous triggering

• 0 is returned when there is only a single trigger



Query Example

INIT2:CONT?

This command queries whether Channel B is set for single or continuous triggering.



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.

Use FETCh? to transfer a measurement from memory to the output buffer.

Refer to “FETCh[1]|2|3|4 Queries” on page 110 for further details.

N O T E

This command performs the same function as

INITiate:[IMMediate]:SEQuence[1]|2 .

Syntax

INIT

2

1 :IMM

Example

INIT2:IMM This command places Channel B in the wait for trigger state.

Error Messages

If the power meter is not in the idle state or INITiate:CONTinuous is ON, error –213, “INIT ignored” occurs.



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

INIT :CONT :ALL Space

?

0|OFF

1|ON

Example

INIT:CONT:ALL ON This command sets all trigger sequences to be continuously initiated.

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. For other trigger sources,

INITiate:CONTinuous is set to ON.



Query

INITiate:CONTinuous:ALL?


• 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

INIT:CONT:ALL?

This command queries whether both channels are in a wait for trigger state.



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.

If INITiate:CONTinuous:SEQuence[1|2] <boolean> is set to:

• OFF, the trigger system remains in the idle state until it is set to ON, or

INITiate:IMMediate is received. Once this trigger cycle is complete the trigger system returns to the idle state.

• ON, the trigger system is initiated and exits the idle state. On completion of each trigger cycle, the trigger system immediately commences another trigger cycle without entering the idle state.

N O T E

This command performs the same functions as INITiate[1]|2:CONTinuous

<boolean> .

Syntax

INIT :CONT :SEQ 1

2

Space

?

0|OFF

1|ON

Example

INIT:CONT:SEQ2 ON This command places Channel B in a wait for trigger state.



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?


• 1 is returned when there is continuous triggering

• 0 is returned when there is only a single trigger

Query Example

INIT2:CONT:SEQ?

This command queries whether Channel B is set for single or continuous triggering.



INITiate[:IMMediate]:ALL

This command initiates all trigger sequences.

Syntax

INIT :IMM :ALL

Example

INIT:IMM:ALL This command initiates all trigger sequences.

Error Messages

If the power meter is not in the idle state or INITiate:CONTinuous is ON, error –213, “INIT ignored” occurs.



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.

Use FETCh? to transfer a measurement from memory to the output buffer.

Refer to “FETCh[1]|2|3|4 Queries” on page 110 for further information.

This command performs the same function as INITiate[1]|2:[IMMediate].

N O T E

Syntax

INIT :IMM :SEQ

2

1

Example

INIT:IMM:SEQ1 This command places Channel A in the wait for trigger state.

Error Messages

If the power meter is not in the “idle” state or INITiate:CONTinuous is

ON , error –213, “INIT ignored” occurs.



TRIGger Commands

TRIGger commands control the behavior of the trigger system.


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>

TRIGger[:SEQuence[1]|2]:IMMediate


BUS|EXTernal|HOLD|IMMediate|INTernal[[1]|2



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. This settling time allows the internal digital filter to be updated with new values to produce valid, accurate measurement results. The trigger with delay command allows settling time for the internal amplifiers and filters. It does not allow time for power sensor delay.

In cases of large power changes, the delay may not be sufficient for complete settling. Accurate readings can be assured by taking two successive measurements for comparison.

• OFF, the power meter makes the measurement immediately a trigger is received.

TRIGger[1]|2:DELay:AUTO is ignored if TRIGger[1]|2[:IMMediate] is set to ON.

Syntax

TRIG 1

2

:DEL :AUTO Space

?

0|OFF

1|ON

N O T E

Trigger delay is not applicable when the power meter is set to power sweep mode or frequency sweep mode.



Example

TRIG:DEL:AUTO ON This command enables a delay on

Channel A.

Reset Condition

On reset, TRIGger:DELay:AUTO is set to ON.

Query

TRIGger:DELay:AUTO?


TRIGger:DELay:AUTO .

• 1 is returned when it is ON

• 0 is returned when it is OFF



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.


This command performs the same function as INITiate[1]|2:[IMMediate].

N O T E

Syntax

TRIG 1

2

:IMM

Example

TRIG This command causes a Channel A trigger to occur immediately.

Error Messages

If the power meter is not in the wait for trigger state, then

TRIGger:IMMediate causes error –211, “Trigger ignored”.



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.

N O T E

• This command has been included for compatibility purposes. It has the same purpose as


BUS|EXTernal|HOLD|IMMediate|INTernal[[1]|2] which should be used in preference.

• If the source is set to INT, INT1 or INT2 when connecting the N1920 or E9320 sensor in average mode, errors occurs.

Syntax

TRIG

2

1 :SOUR Space BUS

EXT

HOLD

IMM

INT

?

2

1



Parameters

Item source


Available trigger sources:

• BUS : the trigger source is the group execute trigger <GET> bus command, a

*TRG common command or the TRIGGER:IMMediate SCPI command.

• EXTernal : the trigger source is the trigger input in the back panel.

• HOLD: triggering is suspended. The only way to trigger the power meter is to use TRIGger:IMMediate.

• IMMediate : the trigger system is always true. If INITiate:CONTinuous is ON the power meter is continually triggering free (free run mode). If an

INITiate:IMMediate command is sent a measurement is triggered then the power meter returns to the idle state.

• INTernal : either INT1 (Channel A) or INT2 (Channel B).

Range of Values

BUS

EXTernal

HOLDIMMediate

INTernal[[1]|2]

N O T E

The trigger source is set to IMMediate on instrument power-up and when entering local mode.

The MEASure and CONFigure commands automatically set the trigger source to

IMMediate .

The READ? or MEASure commands should not be used if the trigger source is set to BUS or HOLD.

Example

TRIG:SOUR IMM This command configures Channel A for immediate triggering.

Reset Condition

On reset, the trigger source is set to IMMediate.



Query

TRIGger:SOURce?

The query returns the current trigger source, either IMM, BUS or HOLD.

Query Example

TRIG:SOUR?

This command queries Channel A’s trigger source.

Error Messages

• For dual channel power meters: if the master is changed to IMM, BUS or

HOLD , error –221 “Settings Conflict” occurs. In such situations the slave’s TRIG:SOUR must be changed so that it is no longer a slave.

• For dual channel power meters: setting the trigger source to INT1,

INT2 or EXT when the trigger source of adjacent channel is INT1, INT2 or

EXT in different mode (NORMal or AVERage), error –221 “Settings

Conflict” occurs.

• For dual channel power meters: if only a channel is connected with

P- Series power sensor, sensor mode is AVERage and trigger source is

EXT , setting the trigger source of adjacent channel to INT1, INT2 or

EXT, error –221 “Settings Conflict” occurs.

• If the source is changed to INT1, INT2 or EXT and SENS:SPEED has a value of 200, error –221 “Settings Conflict” occurs.

• If the source is changed to INT1, INT2 or EXT and SENS:DET:FUNC is set to AVERage, error –221 “Settings Conflict” occurs.

• If the source is set to INT1 or INT2 when connecting the N1920 sensor in average mode, error –221 “Settings Conflict” occurs.



TRIGger[:SEQuence]:DELay <numeric_value>

This command sets the delay between the recognition of a trigger event and the start of a measurement.

Syntax

TRIG :SEQ :DEL Space numeric_value

DEF

?

Parameters

Item numeric_value


The delay between the recognition of a trigger event and the start of the measurement.


Units are resolved to 1.25 ns.

Range of Values

–1 to 1 second

DEF

N O T E

Trigger delay is not applicable when the power meter is set to power sweep mode or frequency sweep mode.



Example

TRIG:SEQ:DEL 0.001

This command sets a delay of 1 ms for

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

TRIG:SEQ:DEL?

This command queries the trigger delay of

Channel A.

Reset Condition

On reset, trigger delay is set to 0 seconds.



TRIGger[:SEQuence]:HOLDoff <numeric_value>

This command sets the trigger holdoff in seconds.

Syntax

TRIG :SEQ :HOLD Space numeric_value

DEF

MIN

MAX

?

Parameters

Item numeric_value


The trigger holdoff in seconds.

• DEF : the default value is 1 µs

• MIN : 1 µs

• MAX : 400 ms


Range of Values

1 µs to 0.4 seconds

DEF

MIN

MAX

N O T E

Trigger holdoff is not applicable when the power meter is set to power sweep mode or frequency sweep mode.



Example

TRIG:SEQ1:HOLD 0.1

This command sets the trigger holdoff to

100 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

TRIG:SEQ:HOLD?

This command queries the trigger holdoff setting for Channel A.



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 Space numeric_value

DEF

?

Parameters

Item numeric_value


How far a signal must fall/rise before a rising or falling edge can be detected.

• DEF : the default value is 0 dB

Units are resolved to 0.05 dB.

Range of Values

0 to 3 dB

DEF



Example

TRIG:SEQ:HYST 0.1

This command sets the value to

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

TRIG:SEQ:HYST?

This command queries the value for

Channel A.



TRIGger[:SEQuence]:LEVel <numeric_value>

This command sets the power level at which a trigger event is recognized.

Syntax

TRIG :SEQ :LEV Space numeric_value

DEF

?

Parameters

Item numeric_value


The power level at which a trigger event is recognized.

• DEF : the default value is 0 dBm

Units are resolved to 0.1 dBm.

Range of Values

1

–40 to 20 dBm

DEF

1

If a channel offset has been previously set, a higher numeric value is permitted. See “Setting

Offsets” on page 38 for more information.



Example

TRIG:SEQ:LEV 10 This command sets the power level for a trigger event to 10 dBm.

Reset Condition

On reset the power level is set to 0 dBm.

Query

TRIGger[:SEQuence]:LEVel?

The query returns the current power level setting.

Query Example

TRIG:SEQ1:LEV?

This command queries the power level setting for Channel A.



TRIGger[:SEQuence]:LEVel:AUTO <boolean>

This command enables/disables automatic setting of the trigger level.


• 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. The value is then set to OFF.

Syntax

TRIG :SEQ :LEV :AUTO Space 0|OFF

1|ON

ONCE

?

Example

TRIG:SEQ:LEV:AUTO 0 This command disables the automatic setting of the trigger level for Channel A.

Reset Condition

On reset the value is set to ON.



Query

TRIGger[:SEQuence]:LEVel:AUTO?


TRIGger[:SEQuence]:LEVel:AUTO .



Query Example

TRIG:SEQ:LEV:AUTO?

This command queries the setting for

Channel A.



TRIGger[:SEQuence]:SLOPe <character_data>

This command specifies whether a trigger event is recognized on the rising or falling edge of a signal.

N O T E

This command is also applicable for external triggered average measurement when used with 8480, N8480, E4410, E9300 or E9320 sensor (Average mode only).

Syntax

TRIG :SEQ :SLOP Space character_data

?

Parameters

Item character_data


How a trigger event is recognized:

• POSitive : a trigger event is recognized on the rising edge of a signal.

• NEGative : a trigger event is recognized on the falling edge of a signal.

Range of Values

POSitive

NEGative



Example

TRIG:SEQ:SLOP NEG This command sets the trigger event to be recognized on the falling edge of the triggering signal.

Reset Condition

On reset the value is set to POSitive.

Query

TRIGger[:SEQuence]:SLOPe?

The query returns the current value of <character_data>.

Query Example

TRIG:SEQ:SLOP?

This command queries the current value of <character_data> for Channel A.

Error Messages

• If 8480, N8480, E4410, E9300 or E9320 sensor is connected and trigger source is not set to external, –221 “Settings conflict” occurs.



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.

COUNt can be set to a value >1 only when:

• [SENSe[1]]|SENSe2:MRATe <character_data> is set to FAST

• TRIGger[1]|2:SOURce set to BUS, IMMediate or HOLD.

When COUNt is set to a value >1,

• CALibration[1]|2:ZERO:AUTO will switch to OFF automatically. It will restored to its default setting when the COUNt is set to 1.

• Setting a channel from FAST mode to NORMal mode or DOUBle mode will also restore both the CALibration[1]|2:ZERO:AUTO and COUNt to its default setting automatically.

Syntax

TRIG :SEQ 1

2

:COUN Space numeric_value

DEF

?



Parameters

Item numeric_value


The number of triggered events for the measurement cycle.

• DEF : the default value is 1

Range of Values

1 to 50

DEF

Example

TRIG:SEQ1:COUN 10 This command sets the number of triggered 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

TRIG:SEQ2:COUN?


This command queries the number of triggered events for the Channel B measurement cycle.

Error Messages

If COUNt >1 when [SENSe[1]]|SENSe2:MRATe <character_data> is set to

NORMal or DOUBle, error –221, “Settings Conflict” occurs.



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.


• ON, the power meter inserts a settling- time delay before taking the requested measurement and for subsequent measurements. This settling time allows the internal digital filter to be updated with new values to produce valid, accurate measurement results. The trigger with delay command allows settling time for the internal amplifiers and filters. It does not allow time for power sensor delay.

In cases of large power changes, the delay may not be sufficient for complete settling. Accurate readings can be assured by taking two successive measurements for comparison.

• OFF, no settling- time delay is inserted and the power meter makes the measurement immediately a trigger is received.

• ONCE, a settling- time delay is inserted before taking the requested measurement, for one measurement only.


Syntax

TRIG :SEQ 1

2

:DEL :AUTO Space 0|OFF

1|ON

?

ONCE



Example

TRIG:SEQ:DEL:AUTO ON This command enables a delay on

Channel A.

Reset Condition

On reset, TRIGger:DELay:AUTO is set to ON.

Query

TRIGger:DELay:AUTO?


TRIGger:DELay:AUTO .



Query Example

TRIG:SEQ2:DEL:AUTO?

This command queries the settling- time delay of Channel B.



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. In other words, the instrument stops waiting for a trigger and takes a measurement ignoring any delay set by TRIG:DELay

.

Syntax

TRIG :SEQ :IMM 1

2

Example

TRIG:SEQ:IMM This command initiates a measurement on Channel A.



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.

N O T E

This command has the same purpose as TRIGger[1]|2:SOURce

BUS|EXTernal|HOLD|IMMediate|INTernal[[1]|2] .

Syntax

TRIG :SEQ

2

1 :SOUR Space BUS

EXT

HOLD

IMM

INT

?

2

1



N O T E

Parameters

Item source


Available trigger sources:

• BUS : the trigger source is the group execute trigger

<GET> bus command, a *TRG common command or the TRIGGER:IMMediate SCPI command.

• EXTernal : the trigger source is the trigger input in the back panel.

• HOLD : triggering is suspended. The only way to trigger the power meter is to use TRIGger:IMMediate.

• IMMediate : the trigger system is always true. If

INITiate:CONTinuous is ON the power meter is continually triggering free (free run mode). If an

INITiate:IMMediate command is sent a measurement is triggered then the power meter returns to the idle state.

• INTernal : either INT1 (Channel A) or INT2

(Channel B).

Range of Values

BUS

EXTernal

HOLD

IMMediate

INTernal[[1]|2]

The trigger source is set to IMMediate on instrument power-up and when entering local mode.

The MEASure and CONFigure commands automatically set the trigger source to

IMMediate .

The READ? or MEASure commands should not be used if the trigger source is set to BUS or HOLD.

Example

TRIG:SOUR IMM This command configures Channel A for immediate triggering.



Reset Condition

On reset, the trigger source is set to IMMediate.

Query

TRIGger[:SEQuence[1]|2]:SOURce?

The query returns the current trigger source.

Query Example

TRIG:SEQ1:SOUR?

This command queries the current trigger source for Channel A.

Error Messages

• For dual channel power meters: if the master is changed to IMM, BUS or

HOLD , error –221 “Settings Conflict” occurs. In such situations the slave’s TRIG:SOUR must be changed so that it is no longer a slave.

• If the trigger source is changed to INT1, INT2 or EXT and SENS:SPEED has a value of 200, error –221 “Settings Conflict” occurs.

• If the trigger source is changed to INT1 or INT2 and SENS:DET:FUNC is set to AVERage, error –221 “Settings Conflict” occurs.

• If the trigger source is set to INT1 or INT2 when 8480, N8480, E4410,

E9300 or E9320 (Average mode only) is connected, error –221 “Settings

Conflict” occurs.

• For dual channel power meters: if the adjacent sensor is in peak mode, setting the trigger source of 8480, N8480, E4410, E9300 or E9320

(Average mode only) to EXTernal causes error –221 “Settings

Conflict”.







15

UNIT Subsystem

UNIT Subsystem 688

UNIT[1]|2|3|4:POWer <amplitude_unit> 689

UNIT[1]|2|3|4:POWer:RATio <ratio_unit> 691

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).


687

15 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 upper window/lower measurement

UNIT2 lower window/upper measurement

UNIT4 lower window/lower measurement

Figure 15-23Measurement Display UNIT Block Window


Keyword

UNIT[1]|2|3|4

:POWer

:RATio


<amplitude unit>

<ratio_unit> [non-SCPI]

Page

page 689

page 691

The UNIT:POWer and UNIT:POWer:RATio commands are coupled as follows:

• If UNIT:POWer is set to dBm then UNIT:POWer:RATio is dB.

• If UNIT:POWer is set to W then UNIT:POWer:RATio is %.


UNIT Subsystem 15

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

For the N1911A:

• UNIT1:POWer sets the power measurement units for the upper window/upper measurement.

• UNIT2:POWer sets the power measurement units for the lower window/upper measurement.

• UNIT3:POWer sets the power measurement units for the upper window/lower measurement.

• UNIT4:POWer sets the power measurement units for the lower window/lower measurement.

For ratio and relative power measurements:

• If UNIT:POWer is W, the measurement units are percentage.

• If UNIT:POWer is DBM, the measurement units are dB relative.

Syntax

UNIT 1

2

3

4

:POW Space amplitude_unit

?



Parameters

Item amplitude_unit


The measurement unit.

• The default unit is dBm

Example

UNIT1:POW DBM

Range of Values

W

DBM

This command sets the power measurement 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.

Query Example

UNIT2:POW?

This command queries which measurement units are being used on the lower window/upper measurement.


UNIT Subsystem 15

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.

• UNIT4:POWer:RATio sets the ratio measurement units for the lower window/lower measurement.

Syntax

UNIT 1

2

3

4

:POW :RAT Space

?

ratio_unit

Parameters

Item ratio_unit


The ratio measurement unit.

• The default unit is DB

Range of Values

DB

PCT



Example

UNIT1:POW:RAT DB This command sets the ratio measurement 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

UNIT2:POW:RAT?

This command queries which ratio measurement units are being used on the lower window/upper measurement.




16


SERVice Subsystem 695

SERVice:BIST:CALibrator <boolean> 697

SERVice:BIST:CW[1]|2:LINearity 699

SERVice:BIST:CW[1]|2:LINearity:PERRor?

700

SERVice:BIST:CW[1]|2:ZSET:NUMber?

701

SERVice:BIST:PEAK[1]|2:LINearity <numeric_value> 702

SERVice:BIST:PEAK[1]|2:LINearity:PERRor?

703

SERVice:BIST:PEAK[1]|2:ZSET 704

SERVice:BIST:PEAK[1]|2:ZSET:NUMber?

705

SERVice:BIST:TBASe:STATe 706

SERVice:BIST:TBASe:STATe <boolean> 707

SERVice:BIST:TRIGger:TEST?

709

SERVice:CALibrator:ADJ:COUR <numeric_value> 710

SERVice:CALibrator:ADJ:FINE <numeric_value> 711

SERVice:LAN:PHOStname 712

SERVice:OPTion <character_data> 713

SERVice:SECure:ERASe 715

SERVice:SENSor[1]|2:CALFactor <cal_factor_data> 716

SERVice:SENSor[1]|2:CDATe?

718

SERVice:SENSor[1]|2:CORRections:STATe <boolean> 719

SERVice:SENSor[1]|2:CPLace?

721

SERVice:SENSor[1]|2:FREQuency:MAXimum?

722

SERVice:SENSor[1]|2:FREQuency:MINimum?

723

SERVice:SENSor[1]|2:PCALfactor <cal_factor_data> 724

SERVice:SENSor[1]|2:POWer:AVERage:MAXimum?

726

SERVice:SENSor[1]|2:POWer:PEAK:MAXimum?

727

SERVice:SENSor[1]|2:POWer:USABle:MAXimum?

728

SERVice:SENSor[1]|2:POWer:USABle:MINimum?

729


693

16 SERVice Subsystem

SERVice:SENSor[1]|2:RADC?

730

SERVice:SENSor[1]|2:SNUMber?

731

SERVice:SENSor[1]|2:TNUMber?

732

SERVice:SENSor[1]|2:TYPE?

733

SERVice:SNUMber <character_data> 734

SERVice:VERSion:PROCessor <character_data> 735

SERVice:VERSion:SYSTem <character_data> 736

This chapter explains how the SERVice command subsystem is used to obtain and set information useful for servicing the power meter.


SERVice Subsystem 16


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

SERVice

:BIST

:CALibrator

:CW[1]|2

:LINearity

:PERRor?

:ZSET

:NUMber?

:PEAK[1]|2

:LINearity

:PERRor?

:ZSET

:NUMber?

:TBASe

:STATe

:STATe

:TRIGger

:TEST?

:CALibrator

:ADJ

:COUR

:FINE

:LAN

:PHOStname

:OPTion


<boolean>

<numeric_value>

[No query]

[query only]

[query only]

[No query]

[query only]

[No query]

[query only]

[No query]

<boolean>

[query only]

<numeric_value>

<numeric_value>

<character_data>


Page

page 697

page 699

page 700

page 701

page 702

page 703

page 704

page 705

page 706

page 707

page 709

page 710

page 711

page 712

page 713

695


Keyword

:SECure

:ERASe

:SENSor[1]|2

:CALFactor

:CDATe?

:CORRections

:STATe

:CPLace?

:FREQuency

:MAXimum?

:MINimum?

:PCALfactor

:POWer

:AVERage

:MAXimum?

:PEAK

:MAXimum?

:USABle

:MAXimum?

:MINimum?

:RADC?

:SNUMber?

:TNUMber?

:TYPE?

:SNUMber

:VERSion

:PROCessor

:SYSTem


<cal_factor_data>

[query only]

<boolean>

[query only]

[query only]

[query only]

<cal_factor_data>

<character_data>

<character_data>

<character_data>

[query only]

[query only]

[query only]

[query only]

[query only]

[query only]

[query only]

[query only]

Page

page 715

page 716

page 718

page 719

page 721

page 722

page 723

page 724

page 726

page 727

page 728

page 729

page 730

page 731

page 732

page 733

page 734

page 735

page 736



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.

Syntax

SERV :BIST :CAL Space 0|OFF

1|ON

?

ONCE

Example

SERV:BIST:CAL OFF This command disables the calibrator self- test during power- up.

Query

SERVice:BIST:CALibrator?

The query enters a 1 or 0 into the output buffer indicating the status of the self- test.

• 1 is returned when the self- test is enabled

• 0 is returned when the self- test is disabled



Query Example

SERV:BIST:CAL?

This command queries whether the self- test is enabled or disabled.



SERVice:BIST:CW[1]|2:LINearity

This command initiates the CW linearity test.

Syntax

SERV :BIST :CW 1

2

:LIN

Example

SERV:BIST:CW:LIN This command enables the CW linearity test.



SERVice:BIST:CW[1]|2:LINearity:PERRor?

This command returns the worst case error in the CW linearity test.

Syntax

SERV :BIST :CW 1

2

:LIN :PERR

Example

SERV:BIST:CW:LIN:PERR?

This command queries the worst case error in the CW linearity test.



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 :CW 1

2

:ZSE T

:NUM ?

Example

SERV:BIST:CW:ZSET:NUM?

This command queries the worst case error in the CW zero test.



SERVice:BIST:PEAK[1]|2:LINearity <numeric_value>

This command initiates the PEAK linearity test.

Syntax

SERV :BIST :PEAK 1

2

:LIN Space numeric_value

DEF

?

Parameters

Item

Numeric_value


Define the number of samples taken for results, default:0

Range of Values

0 to 8000

Example

SERV:BIST:PEAK:LIN 8000 This command sets the number of samples of the PEAK linearity test to be 8000.



SERVice:BIST:PEAK[1]|2:LINearity:PERRor?

This command returns the PEAK linearity worst case error.

Syntax

SERV :BIST :PEAK 1

2

:LIN :PERR

Example

SERV:BIST:PEAK:LIN PERR?

This commands queries the PEAK linearity worst case error.



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 1

2

:ZSET

Example

SERV:BIST:PEAK1:ZSET This command enables the zero set and noise test for Channel A.



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 1

2

:ZSE T

:NUM ?

Example

SERV:BIST:PEAK:ZSET:NUM?

This command queries the worst case error in the PEAK zero test.



SERVice:BIST:TBASe:STATe

This command toggles the 10 MHz timebase out of the trigger outport.

Syntax

SERV :BIST :TBAS :STAT

Example

SERV:BIST:TBAS:STAT This command toggles the timebase out of the trigger outport.



SERVice:BIST:TBASe:STATe <boolean>

N O T E

This command sends a 10 MHz time base signal to the rear panel trig out for testing purposes.

This command overrides the OUTPut:TRIGger[:STATe] command.

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 . However, the 10 MHz remains out the Trig out port.

If the SERV:BIST:TBAS ON has been sent, the 10 MHz is on and the

OUTPut:TRIGger[:STATe] is then toggled to ON, the channel trigger is now routed to the Trig out overriding the service command turning the 10 MHz to off.

If the command is set to:

• ON, the 10 MHz time base signal is sent to the rear panel trigger out connector.

• OFF, the 10 MHz time base signal is disabled.

Syntax

SERV :BIST :TBAS :STAT Space

?

0|OFF

1|ON

Example

SERV:BIST:TBAS:STAT OFF This command disables the signal.



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

• 0 is returned when the signal is disabled

Query Example

SERV:BIST:TBASe:STAT?

This command queries whether the test is enabled or disabled.



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

N O T E

Before running this command, the read panel trigger out must be jumpered to the rear panel trigger in.

Syntax

SERV :BIST :TRIG :TEST ?

Example

SERV:BIST:TRIG:TEST?

This command queries trigger in and out.



SERVice:CALibrator:ADJ:COUR <numeric_value>

This command adjust the 1 mW calibrator output in coarse scale.

Syntax

SERV :CAL :ADJ :COUR Space numeric_value

DEF

?

Parameters

Item

Numeric_value


Adjust the 1 mW Power Reference Level

Increment Coarse by 1.

Range of Values

0 to 1023 (Unsigned Int

16)

Query

SERV:CAL:ADJ:COUR?

The query returns the Reference

Calibrator power level in unsigned Int 16.



SERVice:CALibrator:ADJ:FINE <numeric_value>

This command adjust the 1 mW calibrator output in fine scale.

Syntax

SERV :CAL :ADJ :FINE space numeric_value

DEF

?

Parameters

Item

Numeric_value


Adjust the 1 mW Power Reference Level

Increment Fine by 1.

Range of Values

0 to 1023 (Unsigned Int

16)

Query

SERV:CAL:ADJ:FINE?

The query returns the Reference

Calibrator power level in unsigned Int 16.



SERVice:LAN:PHOStname

This command preset the LAN hostname to its default value. It requires the serial number to be setup.

Syntax

SERV :LAN :PHOS

Example

SERV:LAN:PHOS The command presets the LAN hostname to its default value.



SERVice:OPTion <character_data>

This command loads the power meter memory with the options fitted. The query form of the command can be used to determine which options are fitted to the unit.

Syntax

SERV :OPT Space character_data

?

Parameters

Item character_data


Details the option number in a comma separated list. A maximum of 30 characters can be used.

Range of Values


0 - 9

_ (underscore)

Example

SERV:OPT “003” This command loads the power meter memory with 003 indicating that the unit is a rear panel option.



Query

SERVice:OPTion?

The query returns the current option string. For example, if the string

“003” is returned, the power meter is fitted with a sensor input and power reference on the back panel.



SERVice:SECure:ERASe

This command erases the P- Series power meter’s memory, for example, before you return it to Agilent 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.

Syntax

SERV :SEC :ERAS

Example

SERV:SEC:ERAS The command erases the P- Series power meter’s memory.



SERVice:SENSor[1]|2:CALFactor <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.

This command applies to the following sensors:

• E4410 Series

• N8480 Series (excluding Option CFT)

• E9300 Series

• E9320 Series, average path data

For E9320 Series sensors, peak path, refer to

“SERVice:SENSor[1]|2:PCALfactor <cal_factor_data>” on page 724.

Syntax

SERV :SENS 1

2

:CALF Space cal_factor_data

?

Parameters

Item cal_factor_data


A binary data block. Refer to

Appendix A , “Calibration

Factor Block Layout,” on page A-763 for further

information.



Query

SERVice:SENSor[1]|2:CALFactor?

The query returns the current calibration factor block.

Query Example

SERV:SENS:CALF?

This command returns the calibration factor block for Channel A.

Error Messages


• If a a sensor other than a N8480 Series (excluding Option CFT) or

E- Series power sensor is connected, error –241 “Hardware missing” occurs.

• If an E9320 Series sensor is connected and

SERVice:SENSor[1]|2:CORRections:STATe is set to ON, error –221,

“Settings conflict” occurs.

• If INIT:CONT is not set to OFF, error –221, “Settings conflict” occurs.



SERVice:SENSor[1]|2:CDATe?

This query returns the calibration date in P- Series, E- Series sensors and

N8480 Series sensors. Calibration date information is stored in the sensor’s EEPROM.

Syntax

SERV :SENS 1

2

:CDAT ?

Example

SERV:SENS2:CDATe?

This query returns the calibration date of the P- Series sensor, E- Series sensor or

N8480 Series sensor connected to Channel

B.

Error Messages


• If a a sensor other than a P- Series, N8480 Series or E- Series power sensor is connected, error –241 “Hardware missing” occurs.



SERVice:SENSor[1]|2:CORRections:STATe <boolean>

This command enables/disables the voltage to corrected power conversion.

It applies to E9320 Series and P- Series power sensors only.

N O T E

Before setting this command to OFF, you must set the INIT:CONT command to OFF.

After setting this command to OFF, you must only run commands relating to the gathering of ADC values—for example, the SERV:SENS:RADC command.

Syntax

SERV :SENS 1

2

:CORR :STAT Space

?

0|OFF

1|ON

Example

SERV:SENS2:CORR:STAT ON This command enables the voltage to corrected power conversion for Channel

B.

Reset Condition

On reset, the value is set to ON.



Query

SERVice:SENSor[1]|2:CORRections:STATe?

The query enters a 1 or 0 into the output buffer indicating the status of the voltage to corrected power conversion.

• 1 is returned when voltage to corrected power conversion is enabled

• 0 is returned when voltage to corrected power conversion is disabled

Query Example

SERV:SENS:CORR:STAT?

This command queries whether voltage to corrected power conversion is enabled for

Channel A.

Error Messages

• If INIT:CONT is not set to off, error –221, “Settings conflict” occurs.

• If the command is used when a sensor other than the E9320 Series or

P- Series is connected, error –241, “Hardware missing” occurs.



SERVice:SENSor[1]|2:CPLace?

This query returns the calibration place in P- Series, E- Series sensors and

N8480 Series sensors. Calibration place information is stored in the sensor’s EEPROM.

Syntax

SERV :SENS 1

2

:CPL ?

Example

SERV:SENS2:CPL?

This query returns the place of

calibration of the P- Series, E- Series sensor or N8480 Series sensor connected to Channel B.

Error Messages


• If a sensor other than a P- Series, N8480 Series or E- Series power sensor is connected, error –241 “Hardware missing” occurs.



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 1

2

:FREQ :MAX ?

Example

SERV:SENS2:FREQ:MAX?

This query returns the maximum frequency that can be measured by the

E- Series sensor currently connected to

Channel B.

Error Messages

• If no sensor is connected, error –241, “Hardware missing” occurs.

• If a a sensor other than an E- Series sensors is connected, error –241


• If the E- Series sensor sensor, currently connected, does not contain the necessary information in EEPROM, error –241 “Hardware missing” occurs.



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

2

1 :FREQ :MIN ?

Example

SERV:SENS1:FREQ:MIN?

This query returns the minimum frequency that can be measured by the


Channel A.

Error Messages


• If a a sensor other than an E- Series sensor is connected, error –241


• If the E- Series sensor currently connected does not contain the necessary information in EEPROM, error –241 “Hardware missing” occurs.



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.

This command applies to E9320 Series sensors for peak path data only.

For E4410 Series, E9300 Series and E9320 Series sensors, average path data, refer to

“SERVice:SENSor[1]|2:CALFactor <cal_factor_data>” on page 716.

Syntax

SERV :SENS 1

2

:PCAL Space cal_factor_data

?

Parameters

Item cal_factor_data


A binary data block. Refer to

Appendix A , “Calibration Factor Block

Layout,” on page A-763 for further information.

Query

SERVice:SENSor[1]|2:PCALfactor?

The query returns the current peak path calibration factor block.



Query Example

SERV:SENS:PCAL?

This command returns the peak path calibration factor block for Channel A.

Error Messages


• If a a sensor other than an E9320 power sensor is connected, error

–241 “Hardware missing” occurs.

• If INIT:CONT is not set to OFF, error –221, “Settings conflict” occurs.



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

2

1 :POW :AVER :MAX ?

Example

SERV:SENS:POW:AVER:MAX?

This query returns the maximum average power that can be measured by the


Channel A.

Error Messages







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

2

1 :POW :PEAK :MAX ?

Example

SERV:SENS2:POW:PEAK:MAX?

This query returns the maximum peak power that can be measured by the


Channel B.

Error Messages







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

2

1 :POW :USAB :MAX ?

Example

SERV:SENS1:POW:USAB:MAX?

This query returns the maximum power that can be accurately measured by the


Channel A.

Error Messages







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 :SENS 1

2

:POW :USAB :MIN ?

Example

SERV:SENS:POW:USAB:MIN?

This query returns the minimum power that can be accurately measured by the


Channel A.

Error Messages







SERVice:SENSor[1]|2:RADC?

This query returns a new raw uncorrected measurement in volts, as a 32 bit signed integer.

N O T E

For E9320 Series and P-Series sensors:

Before running this query, the voltage to corrected power conversion must be disabled using the SERVice:SENSor[1]|2:CORRections:STATe command.

Syntax

SERV :SENS 1

2

:RADC ?

Example

SERV:SENS2:RADC?

This query returns a new raw uncorrected measurement for the sensor connected to Channel B.

Error Messages

• If INIT:CONT is set to ON, error –221 “Settings Conflict” occurs.

• If the E9320 Series or P- Series sensor is connected and

SERVice:SENSor[1]|2:CORRections:STATe is set to ON, error –221

“Settings Conflict” occurs.



SERVice:SENSor[1]|2:SNUMber?

This query returns the serial number for P- Series, E- Series sensors and

N8480 Series sensors. Serial number information is stored in the sensor’s

EEPROM.

Syntax

SERV :SENS 1

2

:SNUM ?

Example

SERV:SENS2:SNUM?

This query returns the serial number of the P- Series, E- Series sensor or N8480

Series sensor connected to Channel B.

Error Messages


• If a a sensor other than a P- Series, N8480 Series or E- Series power sensor is connected, error –241 “Hardware missing” occurs.



SERVice:SENSor[1]|2:TNUMber?

This query returns the tracking number for P- Series and E- Series sensors.

Tracking number information is stored in the sensor’s EEPROM.

Syntax

SERV :SENS 1

2

:TNUM ?

Example

SERV:SENS2:TNUM?

This query returns the serial number of the E- Series sensor connected to Channel

B.

Error Messages


• If a a sensor other than a P- Series or E- Series power sensor is connected, error –241 “Hardware missing” occurs.



SERVice:SENSor[1]|2:TYPE?

This query identifies the sensor type connected to the power meter input channel(s). For Agilent 8480 Series Sensors, either “A”, “B”, “D”, or “H” is returned. For P- Series, E- Series and N8480 Series sensors, the model number stored in EEPROM is returned

Syntax

SERV :SENS 1

2

:TYPE ?

Example

SERV:SENS2:TYPE?

This query returns either, “A”, “B”, “D”, or

“H” if an Agilent 8480 Series sensor is connected to Channel B, or the sensor

model number if an P- Series, E- Series or

N8480 Series sensors is connected to

Channel B.

Error Messages




SERVice:SNUMber <character_data>

This command loads the power meter with a serial number in the form

GB12345678 or US12345678.

Syntax

SERV :SNUM Space character_data

?

Parameters

Item character_data


Details the power meter serial number in the form GB12345678 or US12345678. A maximum of 30 characters can be used.

Range of Values


0 - 9

Example

SERV:SNUM GB12345678 This command loads the power meter with the serial number GB12345678.

Query

SERVice:SNUMber?

The query returns the power meter serial number in the form GB12345678 or US12345678.



SERVice:VERSion:PROCessor <character_data>

This command loads the power meter with the processor board revision version.

Syntax

SERV :VERS :PROC


?

Parameters

Item character_data


Details the processor board revision version. A maximum of 20 characters can be used.

Range of Values


0 - 9

_ (underscore)

Example

SERV:VERS:PROC “C” This command loads the power meter with processor board revision version C.

Query

SERVice:VERSion:PROCessor?

The query returns the current processor board revision version.



SERVice:VERSion:SYSTem <character_data>

This command loads the power meter with the system version number.

Syntax

SERV :VERS :SYST Space character_data

?

Parameters

Item character_data


Details the system version number. A maximum of 20 characters can be used.

Range of Values


0 - 9

_ (underscore)

Example

SERV:VERS:SYST “1” This command loads the power meter with system version number 1.

Query

SERVice:VERSion:SYSTem?

The query returns the current power meter system version number.




17



*CLS 739

*DDT <arbitrary block program data>|<string program data> 740

*ESE <NRf> 742

*ESR?

744

*IDN?

745

*OPC 746

*OPT?

747

*RCL <NRf> 748

*RST 749

*SAV <NRf> 750

*SRE <NRf> 751

*STB?

753

*TRG 755

*TST?

756

*WAI 757

GPIB Universal Commands 758

This chapter contains information about the IEEE 488.2 Common

Commands that the power meter supports.


737

17 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. When combined with programming language codes, they provide all management and data communication instructions for the system.

The IEEE- 488.2 Common Command descriptions are listed below in alphabetical order.

*CLS Clear Status

*DDT and *DDT?

Define Device Trigger

*ESE and *ESE?

*ESR?

Event Status Enable

Event Status Register

*IDN?

*OPC and *OPC?

*OPT?

*RCL

Identify

Operation Complete

Options

Recall

*RST

*SAV

*SRE and *SRE?

*STB?

*TRG

*TST?

*WAI

Reset

Save

Service Request Enable

Status Byte

Trigger

Test

Wait

page 739

page 740

page 742

page 744

page 745

page 746

page 747

page 748

page 749

page 750

page 751

page 753

page 755

page 756

page 757


IEEE 488.2 Command Reference 17

*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.

Syntax

*CLS



*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.

Syntax

*DDT Space arbitrary block program data string program data

?

740

Parameters

Type arbitrary block program data string program data

Description

The command which is executed on a GET or

*TRG .

Range of Values

#nN<action>

1,2

“<action>”

1

1

The <action> field of the parameter may contain:

FETC?

FETC1?

FETC2? (N1912A only)

*TRG

TRIG1

TRIG2 (N1912A only)

2

The first digit after the # indicates the number of following digits. The following digits indicate the length of the data.



Examples of <arbitrary block program data> parameters are:

• #15FETC? and #206FETCh?

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>

value which is in the form of #nN<action> as described on page 715

.

Error Message

• If an invalid parameter is received, error –224, “Illegal parameter value” occurs.



*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. The parameter value, when rounded to an integer and expressed in base 2, represents the bit values of the Standard Event Status Enable

Register.

Table 17- 90

shows the contents of this register.

Table 17-90*ESE Mapping

Bit

5

6

3

4

7

0

1

2

Weight

1

2

4

8

16

32

64

128

Meaning

Operation Complete

Request Control (not used)

Query Error

Device Dependent Error

Execution Error

Command Error

Not used

Power On

Syntax

*ESE Space

?

NRf



Parameters

Type

NRf


A value used to set the Standard Event Status

Enable Register.

Range of Values

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.



*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- 91

shows the contents of this register.

Table 17-91*ESR? Mapping

Bit

5

6

3

4

7

0

1

2

Weight

1

2

4

8

16

32

64

128

Meaning

Operation Complete

Request Control (not used)

Query Error

Device Dependent Error

Execution Error

Command Error

Not used

Power On

Syntax

*ESR ?



*IDN?

The *IDN? query allows the power meter to identify itself. The string returned is either:

Agilent Technologies,N1911A,<serial number>,A1.XX.YY

Agilent Technologies,N1912A,<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.

Syntax

*IDN ?



*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.



*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 ?



*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

*RCL

Space NRf

Parameters

Type

NRf


The number of the register to be recalled.

Range of Values

1 - 10

Error Message

• If the register does not contain a saved state, error –224, “Illegal parameter value” occurs.



*RST

The *RST (ReSeT) command places the power meter in a known state.

Refer to

“SYSTem:PRESet <character_data>” on page 526 for information on

reset values.

Syntax

*RST



*SAV <NRf>

The *SAV <NRf> (SAVe) command stores the current state of the power meter in the specified register.

Syntax

*SAV

Space NRf

Parameters

Item

NRf


The number of the register that the current state of the power meter is to be saved to.

Range of Values

1 - 10



*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; a 0 disables the bit. The parameter value, when rounded to an integer and expressed in base 2, represents the bits 0 to 5 and bit 7 of the Service Request Enable Register. Bit 6 is always 0.

Table 17- 92

shows the contents of this register. Refer to the pullout at the end of Chapter 10 for further information.

Table 17-92*SRE Mapping

Bit

5

6

3

4

7

0

1

2

Weight

1

2

4

8

16

32

64

128

Meaning

Not used

Not used

Device Dependent

QUEStionable Status Summary

Message Available

Event Status Bit

Not used

OPERation Status Summary

Syntax

*SRE Space

?

NRf



Parameters

Type

NRf


A value used to set the Service Request

Enable Register.

Range of Values

0 - 255

Query

*SRE?

The query returns the contents of bits 0 to 5 and bit 7 of the Service

Request Enable Register. The format of the return is <NR1> in the ranges of 0 to 63 or 128 to 191 (that is, bit 6 is always 0).



*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. The format of the return is <NR1> in the ranges of 0 to 255.

Table 17- 93

shows the contents of this register. Refer to the Status Block Diagram at the end of

Chapter 11

for further information.

Table 17-93 *STB? Mapping

Bit Weight

0

1

1

2

2

3

4

5

6

7

4

8

16

32

64

128

Meaning

Not used

Device Dependent

0 - No device status conditions have occurred

1 - A device status condition has occurred

Error/Event Queue

0 - Queue empty

1 - Queue not empty

Questionable Status Summary

0 - No QUEStionable status conditions have occurred

1 - A QUEStionable status condition has occurred

Message Available

0 - no output messages are ready

1 - an output message is ready

Event Status Bit

0 - no event status conditions have occurred

1 - an event status condition has occurred

Master Summary Status

0 - power meter not requesting service

1 - there is at least one reason for requesting service

Operation Status Summary

0 - No OPERation status conditions have occurred

1 - An OPERation status condition has occurred



Syntax

*STB ?



*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

• If TRIGger:SOURce is not set to BUS, error –211, “Trigger ignored” occurs.

• If the power meter is not in the wait- for- trigger state, error –211,

“Trigger ignored” occurs.



*TST?

The *TST? (TeST) query causes the power meter to perform the self test.

The test takes approximately 100 seconds.

The result of the test is placed in the output queue.

• 0 is returned if the test passes

• 1 if the test fails

Syntax

*TST ?



*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



GPIB Universal Commands

758

DCL

The DCL (Device Clear) command causes all GPIB instruments to assume a cleared condition. The definition of device clear is unique for each instrument. For the power meter:

• All pending operations are halted, that is, *OPC? and *WAI.

• The parser (the software that interprets the programming codes) is reset and now expects to receive the first character of a programming code.

• The output buffer is cleared.

GET

The GET (Group Execute Trigger) command triggers all channels that are in the “wait- for- trigger” state.

Using the *DDT command may change the function of the GET command.

Error Message

If TRIGger:SOURce is not set to BUS, an error - 211, “Trigger ignored” occurs.

If the power meter is not in the “wait- for- trigger” state then error –211,

“Trigger ignored” occurs.

GTL

The GTL (Go To Local) command is the complement to remote. It causes the power meter to return to local control with a fully enabled front panel. When reverting to local mode the power meter triggering is set to free run.



LLO

The LLO (Local Lock Out) command can be used to disable the front panel local key. With this key disabled, only the controller (or a hard reset by the line power switch) can restore local control.

PPC

When addressed to listen, the PPC (Parallel Poll Configure) command causes the power meter to be configured according to the parallel poll enable secondary command which should follow this command.

PPD

Sending the PPC command followed by the PPD (Parallel Poll Disable) command disables the power meter from responding to a parallel poll.

This is effectively a selective disable.

Table 17-94PPD Mapping

Bit

6

7

4

5

2

3

0

1

Weight

16

32

64

128

4

8

1

2

Meaning

Always 0

Always 0

Always 0

Always 0

Always 1

Always 1

Always 1

Always 0



PPE

Once the power meter has received a PPC command, the PPE (Parallel Poll

Enable) secondary command configures the power meter to respond to a parallel poll on a particular data line with a particular level.

Table 17-95PPE Mapping

6

7

4

5

Bit

2

3

0

1

16

32

64

128

Weight

4

8

1

2

Meaning

Bit positions for response:

000 (bit 0), 001 (bit 1), 010 (bit 2), 011 (bit 3),

100 (bit 4), 101 (bit 5), 110 (bit 6), 111 (bit 7)

Sense bit

0 - response bit is cleared during a parallel poll if requesting service.

1 - response bit is set during a parallel poll if requesting service.

Always 0

Always 1

Always 1

Always 0

PPU

The PPU (Parallel Poll Unconfigure) command disables the power meter from responding to a parallel poll. This is effectively a universal disable.



SDC

The SDC (Selected Device Clear) command causes instruments using GPIB in the listen state, to assume a cleared condition. The definition of a selected device clear is unique for each instrument. For the power meter:

• All pending operations are halted, that is, *OPC? and *WAI.

• The parser (the software that interprets the programming codes) is reset and now expects to receive the first character of a programming code.

• The output buffer is cleared.

SPD

The SPD (Serial Poll Disable) command terminates the serial poll mode for the power meter and returns it to its normal talker state where device dependent data is returned rather than the status byte.

SPE

The SPE (Serial Poll Enable) command establishes the serial poll mode for the power meter. When the power meter is addressed to talk, a single eight bit status byte is returned.







A


Calibration Factor Block Layout A-764

This chapter contains information on the calibration factor block layout for N8480 Series (excluding Option CFT), E4410 Series, E9300 Series and

E9320 Series sensors.


A-763

A Calibration Factor Block Layout


The following tables provide information on the calibration factor block layout for E4410 Series, E9300 Serie, E9320 Series and N8480 Series sensors (excluding Option CFT). The information relates to service commands is described in

Chapter 16 .

Table A-96 Calibration Factor Block Layout: E4410 Series Sensors

E4410 Series

Sensors: Calibration

Factor Block Layout

Header:

Power, low

No.

Bytes

2

Power, high

Number of frequency points

Bytes per frequency point

2

2

1 -

-

-

-

Contents Data

Format

Data

Range

Units

-

7.8 (signed) –127.9 to

+127.9

7.8 (signed) –127.9 to

+127.9

16 bit integer

-

dBm dBm

None

None

Notes

Power for low power flatness.

Power for high power flatness.

Frequency LSB weight 2 1000 Hertz

Number of bytes in cal factor value at each frequency and power level.

Fhbp (Freq. Hz per bit).

1 KHz per bit for the cal factor: 1 KHz x 2^32 =

4.3E+12 = 4300 GHz range

Header Total: 9

Cal Factor Table:

Frequency (point ‘0’) 4

Cal factor (low power)

1 2

Cal factor (high power)

1 2

-

-

-

32 bit fixed 0 to Fhpb*

(2^32)

2.14

0.25 to 3

None

None

2.14

0.25 to 3 None

Fhpb = Freq Hz per bit

Power (in watts) is divided by this value.


A-764 N1911A/1912A P-Series Power Meters Programming Guide

Calibration Factor Block Layout A

E4410 Series



No.

Bytes

Contents Data

Format

Data

Range

These table entries are repeated as shown for each frequency point

Frequency (point ‘N’) 4 32 bit fixed 0 to Fhpb*

(2^32)


1 2 2.14

0.25 to 3

2.14

0.25 to 3


1 2

Table Size: -

See note

1

Units

None

None

None

Notes

Fhbp = Freq Hz per bit



The table size is dependent on the number of frequency points.


E9300 Series



Header:

Number of tables

No.

Bytes

1

Contents

2

Data

Format

Data

Range

Units Notes



2

1

Frequency LSB weight 2

-

-

1000

-

16 bit integer

-

-

None Number of cal factor tables. Note that the power levels and frequency points are the same for all tables.

None

None

Hertz



1 KHz per bit for the cal factor: 1KHz x 2^32 =

4.3E+12 = 4300 GHz range.

N1911A/1912A P-Series Power Meters Programming Guide A-765


E9300 Series



Header Total:

No.

Bytes

6

Contents Data

Format

Data

Range

Units Notes

For Each Table (tables are in the order of lower to upper):

Power, low 2 7.8 (signed) –127.9 to

+127.9

Power, high 2 -

Frequency (point ‘0’)


1

4

2 -

-

7.8 (signed) –127.9 to

+127.9


(2^32)

2.14

0.25 to 3


1 2 2.14

0.25 to 3



(2^32)

Cal factor (low power) 2 2.14

0.25 to 3 dBm dBm

None

None

None

None

None

Cal factor (high power) 2

Table size: -

-

See note

1

2.14

0.25 to 3 None



Fhpb = freq Hz per bit



Fhbp = Freq Hz per bit.





E9320 Series



Header:

No.

Bytes

Contents Data

Format

Data

Range

Units Notes



E9320 Series



Number of tables

No.

Bytes

1

Contents Data

Format

1 -

Data

Range

Units Notes



Frequency

2

1

LSB weight 2

-

-

1000

-

16 bit integer

-

-

-

None Number of cal factor tables. This is currently unused but has been set to a default value of

1.

None

None

Hertz

Number of bytes in cal factor value at each frequency .


1 KHz per bit for the cal factor: 1 KHz x

2^32 = 4.3E+12 =

4300 GHz range

Header Total: 6


Frequency (point ‘0’)

Cal factor

2

Table Size: -

4

2

-

-

See note

3


(2^32)

2.14

0.25 to 3

None

None


Used to adjust analog to digital convertor (ADC) values.



(2^32)

Cal factor 2 2.14

0.25 to 3

None

None


Used to adjust analog to digital converter (ADC) values.




Table A-99 Calibration Factor Block Layout: N8480 Series Sensors

N8480 Series



Header:

Power, low

No.

Bytes

2

Power, high



2

2

1 -

-

-

-

Contents Data

Format

Data

Range

Units

-

7.8 (signed) –127.9 to

+127.9

7.8 (signed) –127.9 to

+127.9

16 bit integer

-

dBm dBm

None

None

Notes



Frequency LSB weight 2 1000 Hertz



1 KHz per bit for the cal factor: 1 KHz x 2^32 =

4.3E+12 = 4300 GHz range

Header Total: 9


Frequency (point ‘0’) 4 32 bit fixed 0 to Fhpb*

(2^32)

2.14

0.25 to 3


1 2


1 2 -

-

2.14

0.25 to 3



(2^32)


1 2 2.14

0.25 to 3


1 2 2.14

0.25 to 3

None

None

None

None

None

None









N8480 Series



Table Size: -

No.

Bytes

Contents Data

Format

See note

1

Data

Range

Units Notes


1 Corrections are applied in power for E4410 Series, E9300 Series and N8480 Series sensors (excluding Option CFT).

2

Corrections are applied in voltage versus ADC reading for E9320 Series sensors. This format also requires only one correction factor across all power levels.

3

The block layout shown for E9320 Series sensors exists in two separate EEPROM locations. One location contains the calibration factor data for the average path and the other contains the calibration factor data for the peak path. These EEPROM blocks are accessed using the SERV:SENS:CALFactor and SERV:SENS:PCALfactor commands respectively.







B

Measurement Polling Example

Measurement Polling Example using VEE program B-772

This chapter contains an example of VEE program in measurement polling.


B-771

B Measurement Polling Example

Measurement Polling Example using VEE program

The following figure provides an example on how to do a measurement polling using a VEE program. The information relates to the condition

polling method as described in “Status Reporting” on page 50.

Example 1:

B-772 N1911A/1912A P-Series Power Meters Programming Guide

Example 2:

Measurement Polling Example B

Figure B-16 Example of VEE program used in measurement polling

N1911A/1912A P-Series Power Meters Programming Guide B-773

B Measurement Polling Example


B-774 N1911A/1912A P-Series Power Meters Programming Guide

www.agilent.com

Contact us

To obtain service, warranty, or technical support assistance, contact us at the following phone numbers:

United States:

(tel) 800 829 4444 (fax) 800 829 4433

Canada:

(tel) 877 894 4414 (fax) 800 746 4866

China:

(tel) 800 810 0189 (fax) 800 820 2816

Europe:

(tel) 31 20 547 2111

Japan:

(tel) (81) 426 56 7832 (fax) (81) 426 56 7840

Korea:

(tel) (080) 769 0800 (fax) (080) 769 0900

Latin America:

(tel) (305) 269 7500

Taiwan:

(tel) 0800 047 866 (fax) 0800 286 331

Other Asia Pacific Countries:

(tel) (65) 6375 8100 (fax) (65) 6755 0042

Or visit Agilent World Wide Web at: www.agilent.com/find/assist

Product specifications and descriptions in this document are subject to change without notice.

Always refer to the Agilent Web site for the latest revision.

© Agilent Technologies, Inc. 2006–2014

Printed in Malaysia

Twelfth Edition, July 1, 2014

N1912-90008
