Remote Language Compatibility Measurement

Remote Language Compatibility Measurement
Keysight X-Series
Signal Analyzer
This help file provides documentation for the following
X-Series Instruments:
UXA Signal Analyzer N9040B
PXA Signal Analyzer N9030B
MXA Signal Analyzer N9020B
EXA Signal Analyzer N9010B
CXA Signal Analyzer N9000B
N9061C Remote
Language
Compatibility
Measurement
Application
User's &
Programmer's
Reference
Notices
Copyright Notice
© Keysight Technologies 2016
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
Keysight Technologies, Inc. as governed by
United States and international copyright
laws.
Trademarks
WiMAX and Mobile WiMAX are US
trademarks of the WiMAX Forum.
Manual Part Number
N9041-90005
Edition
Edition: 1, December 2016
Published in USA
Published by:
Keysight Technologies, Inc.
1400 Fountaingrove Parkway
Santa Rosa, CA 95403
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.
2
U.S. Government Rights
Warranty
The Software is “commercial computer
software,” as defined by Federal Acquisition
Regulation (“FAR”) 2.101. Pursuant to FAR
12.212 and 27.405-3 and Department of
Defense FAR Supplement (“DFARS”)
227.7202, the US government acquires
commercial computer software under the
same terms by which the software is
customarily provided to the public.
Accordingly, Keysight provides the Software
to US government customers under its
standard commercial license, which is
embodied in its End User License Agreement
(EULA), a copy of which can be found at
http://www.keysight.com/find/sweula. The
license set forth in the EULA represents the
exclusive authority by which the US
government may use, modify, distribute, or
disclose the Software. The EULA and the
license set forth therein, does not require or
permit, among other things, that Keysight:
(1) Furnish technical information related to
commercial computer software or
commercial computer software
documentation that is not customarily
provided to the public; or (2) Relinquish to,
or otherwise provide, the government rights
in excess of these rights customarily
provided to the public to use, modify,
reproduce, release, perform, display, or
disclose commercial computer software or
commercial computer software
documentation. No additional government
requirements beyond those set forth in the
EULA shall apply, except to the extent that
those terms, rights, or licenses are explicitly
required from all providers of commercial
computer software pursuant to the FAR and
the DFARS and are set forth specifically in
writing elsewhere in the EULA. Keysight shall
be under no obligation to update, revise or
otherwise modify the Software. With respect
to any technical data as defined by FAR
2.101, pursuant to FAR 12.211 and
27.404.2 and DFARS 227.7102, the US
government acquires no greater than
Limited Rights as defined in FAR 27.401 or
DFAR 227.7103-5 (c), as applicable in any
technical data.
THE MATERIAL CONTAINED IN THIS
DOCUMENT IS PROVIDED “AS IS,” AND IS
SUBJECT TO BEING CHANGED, WITHOUT
NOTICE, IN FUTURE EDITIONS. FURTHER,
TO THE MAXIMUM EXTENT PERMITTED BY
APPLICABLE LAW, KEYSIGHT DISCLAIMS
ALL WARRANTIES, EITHER EXPRESS OR
IMPLIED, WITH REGARD TO THIS MANUAL
AND ANY INFORMATION CONTAINED
HEREIN, INCLUDING BUT NOT LIMITED TO
THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE. KEYSIGHT 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 KEYSIGHT 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.
Safety Information
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.
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.
Remote Language Compatibility Measurement Application Reference
Table Of Contents
Table Of Contents
N9061C Remote Language Compatibility Measurement Application
User's & Programmer's Reference
1
Table Of Contents
3
1 Special Information for the N9061C Measurement Application
N9061C Application Description
General Rules and Limitations
AC/DC Coupling
Couplings
Markers
Numeric Ranges
Parsing
Predefined Functions
Remote Control
Returning Data
Units
User-defined Functions
Supported Commands
EP Parameter
OA Parameter
Handling of Unsupported Commands and Queries
Hardware and Firmware Requirements for N9061C
Hints and Tips
Compatibility (Speed and Consistency)
Compatibility and Sweep Times
Timeout
Synchronization (1)
Synchronization (2)
Changing Modes
AC and DC Coupling
2 User Interface
45
46
46
47
47
47
47
47
48
48
48
48
48
49
49
49
50
51
51
51
51
51
51
51
52
53
Screen Tabs
Mode Meas View dialog
Mode
Measurement
View
Screen
Select Screen
Screen Name
Delete This Screen
Delete All But This Screen
3
44
54
55
55
57
57
58
60
60
61
61
Remote Language Compatibility Measurement Application Reference
Table Of Contents
89600 VSA
Add Screen
System
Preset
Meas Bar
Measurement Display
Window Title
Measurement Data
Annotation Hotspot
Control Bar
Windows
Undo-Redo
File Functions
File Explorer
Help
Status and Message System
Events
Conditions
Status Dialog
History
Current Conditions
Clear Message Queue
Block Diagram
View Editor
View Editor Window Add
View Editor Window Move Resize
View Editor Window Delete
Create a User View
View Editor Delete User View
View Editor Use Case
Multiscreen
Select Screen
Full Screen
Menu Panel
Cancel
Onscreen Keyboard
Touch On/Off
Tab
3 RLC Mode & Swept SA Measurement
SCPI Support
Functions in this Chapter
RLC Swept SA Views
Normal
Remote Language Compatibility Measurement Application Reference
62
63
64
65
68
70
70
73
76
77
77
77
78
79
79
81
82
83
84
85
86
87
87
89
89
91
93
94
94
95
95
97
97
99
102
103
104
105
106
107
108
109
109
4
Table Of Contents
Spectrum
Amplitude
Y Scale Tab
Reference level
Scale/Div
Display Scale
Y Axis Unit
Reference Level Offset
Number of Divisions
Attenuation Tab
Mech Atten
Elec Atten
Mech Atten Step
Max Mixer Level
Max Mixer Lvl Rule
Signal Path Tab
Presel Center
Preselector Adjust
Internal Preamp
µW Path Control
BW
BW Settings Tab
Res BW
Video BW
VBW:3dB RBW
Span:3 dB RBW
RBW Filter
RBW Filter BW
Display
Display Tab
Display Line
Freq Line
Annotation Tab
Graticule
Screen Annotation
Trace Annotation
Control Annotation
Frequency Annotation
Meas Bar
RLC Swept SA Views
Normal
Frequency
Settings Tab
Center Frequency
5
109
110
110
110
111
112
112
115
116
117
118
120
124
124
124
125
125
127
128
129
134
134
134
135
137
139
140
140
143
143
143
143
144
144
144
145
145
146
146
146
147
148
148
148
Remote Language Compatibility Measurement Application Reference
Table Of Contents
Span
Swept Span v.s. Zero Span
Full Span
Start Freq
Stop Freq
Auto Tune
CF Step
Freq Offset
X Axis Scale
Signal Track
Input/Output
Input Tab
Select Input
RF Calibrator
RF Coupling
Input Z Correction
All Screens Use Same Input
Input/Output Preset
External Gain Tab
Ext Preamp
MS
BTS
Corrections Tab
Corrections On/Off
Edit Corrections
Frequency Interpolation
Transducer Unit
Description
Comment
Apply Corrections
Delete All Corrections
Freq Ref Input Tab
Select Freq Ref Input
External Ref Freq
Default External Ref Freq
External Ref Lock BW
Output Tab
Trig 1 Out
Trig 1 Out Polarity
Trig 2 Out
Trig 2 Out Polarity
Analog Out
Digital Bus Out On/Off
Remote Language Compatibility Measurement Application Reference
149
150
151
151
153
155
156
157
158
160
163
163
163
172
173
174
175
175
176
176
177
178
179
179
179
181
183
184
185
185
185
186
186
188
189
189
190
190
191
192
192
192
197
6
Table Of Contents
Wideband Digital Bus (Option RTS)
Aux IF Out
Marker
Settings Tab
Marker Frequency|Time
Marker Mode
Delta Marker (Reset Delta)
Marker Table
Marker Settings Diagram
All Markers Off
Couple Markers
Peak Search Tab
Peak Search
Next Peak
Next Pk Right
Next Pk Left
Minimum Peak
Pk-Pk Search
Marker Delta
Marker -> CF
Marker -> Ref Lvl
Peak Search Config Tab
Peak Threshold
Peak Excursion
Peak Threshold Line
Peak Search Mode
Peak Table
Peak Table Sort
Peak Table Readout
Δ to Limit
Marker Properties Tab
Marker Frequency|Time
Relative To
X Axis Scale
Lines
Marker Trace
Auto Initialize
Marker Settings Diagram
Marker Function Tab
Marker Frequency|Time
Band Function
Band Left
Band Right
Band Span
7
197
198
201
201
201
203
205
205
206
206
207
207
207
208
208
209
209
209
210
210
210
210
210
211
213
213
214
215
215
216
217
217
219
220
222
222
223
225
226
226
228
231
232
233
Remote Language Compatibility Measurement Application Reference
Table Of Contents
N dB Points
Measure at Marker
Measure at Marker Config
Marker-> Tab
Marker Frequency|Time
Marker -> CF
Marker -> CF Step
Marker -> Start
Marker -> Stop
Marker -> Ref Lvl
Marker Δ -> CF
Marker Δ -> Span
Counter Tab
Marker Count
Counter Gate
Meas Setup
RLC Config Tab
Compatibility Model
Cmd Error
Logging
Command Error Log
Refresh
Clear Log
Preferences
Limit RBW/VBW
Atten Offset
Sweep Type Rule
AC/DC Preset Default
Limit Sweep Time
ID Response
User ID
KSK Tolerance
Analog Out Preset Default
No Terminator
Settings Tab
Average/Hold Number
Average Type
Meas Setup Summary Table
Auto Couple
Meas Preset
Limits Tab
Select Limit
Limit
Remote Language Compatibility Measurement Application Reference
234
238
239
239
239
241
242
242
243
243
244
244
245
245
248
250
250
250
252
253
253
254
254
254
254
256
256
257
258
258
259
259
259
259
260
260
261
264
264
264
265
265
265
8
Table Of Contents
Margin
Type
Edit Limit
Navigate
Edit Limit Settings
Test Limits
X-Axis Unit
Delete All Limits
Meas Standard Tab
Radio Standard Presets
Enable Non-Std Meas
EMC Standard
CISPR Presets
Legacy Compat Tab
Average/Hold
Tune & Listen Tab
Demod Type
Demod Time
AM Channel BW
FM Channel BW
ΦM Channel BW
FM Demod De-emphasis
Advanced Tab
Phase Noise Optimization
ADC Dither
Swept IF Gain
FFT IF Gain
Noise Floor Extension
Noise Source
ACP Enhanced Dynamic Range
Global Tab
Global Center Freq
Global EMC Standard
Restore Defaults
Source Tab
RF Output
Source Amplitude
Source Mode
Source Setup Table
Point Trigger
Power Sweep
Amptd Offset
Amptd Step
Multiplier Numerator
9
266
267
267
268
268
270
271
272
272
272
273
274
275
276
276
277
277
278
279
279
280
280
281
281
284
286
287
289
292
294
294
294
295
296
296
296
297
297
299
300
303
304
305
306
Remote Language Compatibility Measurement Application Reference
Table Of Contents
Multiplier Denominator
Source Sweep Reverse
Freq Offset
Select Source
Add Installed USB Source
GPIB Address
Add Specified GPIB Address
Scan & Add GPIB Source
IP Address
Add Specified IP Address
Run Connection Expert
Add From Connection Expert
Select Highlighted Source
Delete Highlighted Source
Verify Connection
Show Source
Source Preset
Sweep
Sweep Control Tab
Sweep Time
Sweep/Measure
Restart
Sweep Config Tab
Sweep Type
Sweep Type Rules
Sweep Time Rules
FFT Width
Points
Trace
Trace Control Tab
Trace Type
Clear and Write | Restart Averaging | Restart Max/Min Hold
View/Blank
Trace Settings Table
Detector Tab
Detector
Detector Select
Math Tab
Math Function
Operand 1
Operand 2
Trace Function Tab
Copy
Remote Language Compatibility Measurement Application Reference
306
306
307
308
309
310
310
310
311
311
311
311
311
313
313
314
314
316
316
316
318
319
321
321
322
323
326
329
331
334
334
336
337
339
339
339
346
347
347
352
353
353
353
10
Table Of Contents
Exchange
Preset All Traces
Clear All Traces
Normalize Tab
Normalize
Store Ref Trace 1->Trace 3
Show Reference Trace 3
Norm Ref Lvl
Norm Ref Position
Open/Short Cal
Trigger
Trigger Tab
Free Run
Select Trigger Source
Trigger Settings Diagram
Video
Trigger Level
Trigger Delay
Trigger Slope
Trigger Settings Diagram
Line
Select Trigger Source
Trigger Delay
Trigger Slope
Trigger Settings Diagram
External 1/2
Select Trigger Source
Trigger Level
Trigger Delay
Trigger Slope
Trigger Settings Diagram
RF Burst
Select Trigger Source
Absolute Trig Level
Relative Trig Level
Trigger Delay
Trigger Slope
Trigger Settings Diagram
Periodic
Select Trigger Source
Period
Offset
Reset Offset Display
Sync Source
11
354
354
355
355
355
358
358
358
359
359
363
363
363
363
369
370
370
372
372
376
376
376
383
384
387
388
388
394
395
395
399
399
399
406
406
407
408
411
412
412
418
419
420
420
Remote Language Compatibility Measurement Application Reference
Table Of Contents
Trigger Delay
Trigger Setting Diagram
TV
TV Line
Field
Standard
Trigger Setting Diagram
Gate Source Tab
Line
Select Gate Source
Trigger Slope
Trigger Settings Diagram
Ext 1/2
Select Gate Source
Trigger Level
Trigger Slope
Zero Span Delay Compensation
Trigger Settings Diagram
RF Burst
Select Gate Source
Absolute Trigger Level
Trigger Slope
Zero Span Delay Compensation
Trigger Settings Diagram
Periodic
Select Gate Source
Period
Offset
Reset Offset Display
Sync Source
Trigger Settings Diagram
Gate Settings Tab
Gate
Gate View
Gate Delay
Gate Length
Gate Method
Control
Gate Holdoff
Gate View Sweep Time
Gate View Start Time
Periodic Sync Src Tab
Select Periodic Trigger Sync Source
Remote Language Compatibility Measurement Application Reference
421
421
422
422
423
423
424
424
424
424
426
429
430
430
431
433
436
437
438
438
439
440
443
444
445
445
446
446
448
448
448
449
449
450
451
452
452
454
454
456
457
457
457
12
Table Of Contents
Trigger Settings Diagram
Auto Holdoff Tab
Auto Trig
Trig Holdoff
4 Preset
460
Mode Preset
Restore Mode Defaults
Input Output Preset
User Preset
Save User Preset
User Preset All Modes
Restore Defaults All Modes
Restore Screen Defaults
RST Remote Command Only
Backwards Compatibility
5 System Settings
System
Windows Controls
Control Panel...
Web Browser
Application Controls
Show
Show System
Show Hardware
Show LXI
Sound
I/O Config
GPIB
GPIB Address
GPIB Controller
SCPI
SCPI Telnet
SCPI Socket
SICL Server
HiSLIP Server
Web Password Reset
System IDN Response
System IDN Response
User IDN
LXI
LAN Reset
Restore I/O Config Defaults
User Interface
13
458
458
458
459
463
464
465
467
468
469
471
472
473
473
474
475
475
476
476
476
476
476
478
478
479
481
481
481
482
482
483
483
483
484
484
485
485
486
487
487
487
489
Remote Language Compatibility Measurement Application Reference
Table Of Contents
Menu Panel Position
Menu Panel Tabs
Annotations
Display Theme
Backlight
Hints
Numeric Entry Auto Open
Touch
Control Size
Quick Save Mode
Language
Restore User Interface Defaults
Power On
Power On State
Power On Application
Restore Power On Defaults
Configure Applications – Desktop Application
Configure Applications - Instrument boot-up
Restore Defaults
Input/Output
I/O Config
User Interface
Power On
Alignments
Misc
All
Alignments
Auto Align
Auto Align
All But RF
Alert
Align Now
Align Now All but RF
Align Now All but RF (Overlapped)
Align Now RF
Align Now, RF (Overlapped)
Align Now External Mixer
Show Alignment Statistics
Current Start-up Time SCPI
Current Alignment Temperature SCPI
Last Align Now All Time SCPI
Last Align Now All Temperature SCPI
Last Align Now, RF Time SCPI
Remote Language Compatibility Measurement Application Reference
489
489
490
490
491
491
492
492
492
493
493
494
495
495
496
497
497
499
500
500
500
501
501
501
502
503
504
504
504
507
507
509
509
510
511
512
512
513
514
514
515
515
515
14
Table Of Contents
Last Align Now, RF Temperature SCPI
Last Characterize Preselector Time SCPI
Last Characterize Preselector Temperature SCPI
Auto Align Off Time SCPI
Last Align Now, Conducted Time SCPI
Last Align Now, Conducted Temperature SCPI
Last Align Now, Radiated Time SCPI
Last Align Now, Radiated Temperature SCPI
Timebase DAC
Timebase DAC
User Value
Advanced
Characterize Preselector
Characterize Reference Clock
Characterize Noise Floor
Backup or Restore Align Data...
Alignment Data Wizard
Restore Alignment Defaults
Licensing
License Manager
Install License
Remove License
List License
Validate License
Host ID
Security
USB Write Protect
Restore Security Defaults
Diagnostics
Show Hardware Statistics
Front Panel Test
Advanced
Key Recorder
Key Recorder On/Off
Show Keystroke History
Fault Detective
Fault Detective
Fault Detective DEV
Diagnostic Report
Test Summary
Test Result
Service
6 Save/Recall
15
515
516
516
516
516
517
517
517
517
517
518
519
519
521
524
526
527
534
536
536
536
536
537
537
538
539
539
539
540
540
540
540
541
541
541
541
541
542
542
543
543
544
545
Remote Language Compatibility Measurement Application Reference
Table Of Contents
Save
State
Register 1 thru Register 16
Edit Register Names
Save to File/Save As
Trace+State
Save From Trace
Register 1 thru Register 16
Edit Register Names
Save to File/Save As
Screen Config+State
Measurement Data
Save From Trace
Data Type
Notes
Dependencies
Trace
Peak Table
Marker Table
Spectrogram
Meas Results
Capture Buffer
Pulse Table
Current Stats
Cumulative Stats
Pulse Descriptive Word
Save to File/Save As
Limit
Correction
Select Correction
Save to File/Save As
Mask
FMT Mask
Screen Image
Theme
Save to File/Save As
Save to File/Save As
Recall
State
Register 1 thru Register 16
Edit Register Names
Recall From File/Open
Trace+State
Remote Language Compatibility Measurement Application Reference
546
546
547
548
549
550
552
553
553
554
555
556
556
557
557
557
557
562
566
569
573
620
620
621
621
622
622
624
629
630
631
632
632
637
638
639
640
642
643
644
645
645
646
16
Table Of Contents
Recall To Trace
Register 1 thru Register 16
Edit Register Names
Recall From File/Open
Screen Config + State
Measurement Data
Recall To Trace
Data Type
Trace
Capture Buffer
Recall From File/Open
Limit
Recall To Limit
Recall From File/Open
Correction
Amplitude Correction
Select Correction
Recall From File/Open
Mask
FMT Mask
Recall From File/Open
Print
Print
Page Setup
Page Setup
7 Programming the Instrument
List of Supported SCPI Commands
*
I
S
IEEE 488.2 Common Commands
*IDN? - Identification Query
*RST
*TRG - Trigger
*WAI - Wait-to-Continue
List of Legacy Analyzer Commands
Key to Table Columns "8566", "8568", and "8560 Series"
Alphanumeric List of all Legacy Commands with N9061C Support
Legacy Command Descriptions
Command Syntax
Command Description Notes
A1 [one] (Clear Write for Trace A)
Syntax
17
647
648
648
648
650
650
651
651
651
656
656
658
658
659
660
660
661
661
662
663
663
665
665
665
667
669
670
670
670
670
671
671
671
672
672
673
673
673
707
707
709
709
709
Remote Language Compatibility Measurement Application Reference
Table Of Contents
Legacy Products
Description
A2 [two] (Maximum Hold for Trace A)
Syntax
Legacy Products
Description
A3 [three] (View Mode for Trace A)
Syntax
Legacy Products
Description
A4 [four] (Blank Trace A)
Syntax
Legacy Products
Description
ACPALPHA (Adjacent Channel Power Alpha Weighting)
Syntax
Legacy Products
Description
ACPALTCH (Adjacent Channel Power Alternate Channels)
Syntax
Legacy Products
Description
ACPBRPER (Adjacent Channel Power Burst Period)
Syntax
Legacy Products
Description
ACPBRWID (Adjacent Channel Power Burst Width)
Syntax
Legacy Products
Description
ACPBW (Adjacent Channel Power Bandwidth)
Syntax
Legacy Products
Description
ACPCOMPUTE (Adjacent Channel Power Compute)
Syntax
Legacy Products
Description
ACPFRQWT (Adjacent Channel Power Frequency Weighting)
Syntax
Legacy Products
Description
ACPLOWER (Lower Adjacent Channel Power)
Remote Language Compatibility Measurement Application Reference
709
710
710
710
710
710
711
711
711
711
712
712
712
712
713
713
713
713
714
714
714
714
715
715
715
715
716
716
716
716
717
717
717
717
718
718
718
718
719
719
719
719
720
18
Table Of Contents
Syntax
Legacy Products
Description
ACPMAX (Maximum Adjacent Channel Power)
Syntax
Description
ACPMEAS (Measure Adjacent Channel Power)
Syntax
Legacy Products
Description
ACPMSTATE (Adjacent Channel Power Measurement State)
Syntax
Legacy Products
Description
ACPPWRTX (Adjacent Channel Power Total Power Transmitted)
Syntax
Legacy Products
Description
ACPRSLTS (Adjacent Channel Power Measurement Results)
Syntax
Legacy Products
Description
Query Data Type Details
ACPSP (Adjacent Channel Power Channel Spacing)
Syntax
Legacy Products
Description
ACPT (Adjacent Channel Power T Weighting)
Syntax
Legacy Products
Description
ACPUPPER (Upper Adjacent Channel Power)
Syntax
Legacy Products
Description
ADJALL (LO and IF Adjustments)
Syntax
Legacy Products
Description
AMB (A minus B into A)
Syntax
Legacy Products
Description
AMBPL (A minus B plus Display Line into A)
19
720
720
720
720
720
721
721
721
721
721
722
722
722
722
723
723
723
723
724
724
724
724
725
725
725
725
725
726
726
726
726
727
727
727
727
727
727
728
728
728
728
728
728
729
Remote Language Compatibility Measurement Application Reference
Table Of Contents
Syntax
Legacy Products
Description
AMPCOR
Syntax
Legacy Products
Description
AMPCORCFGCNT
Syntax
Legacy Products
Description
AMPCORCLEAR
Syntax
Legacy Products
Description
AMPCORDATA
Syntax
Legacy Products
Description
AMPCORRCL
Syntax
Legacy Products
Description
AMPCORRESET
Syntax
Legacy Products
Description
AMPCORSAVE
Syntax
Legacy Products
Description
AMPCORSIZE
Syntax
Legacy Products
Description
ANNOT (Annotation)
Syntax
Legacy Products
Description
APB (Trace A Plus Trace B to A)
Syntax
Legacy Products
Description
Remote Language Compatibility Measurement Application Reference
729
729
729
730
730
730
730
730
730
731
731
731
731
731
731
731
731
731
731
732
732
732
732
732
732
733
733
733
733
733
733
733
733
733
733
734
734
734
734
735
735
735
735
20
Table Of Contents
AT (Input Attenuation)
Syntax
Legacy Products
Description
AUNITS (Absolute Amplitude Units)
Syntax
Legacy Products
Description
AUTOCPL (Auto Coupled)
Syntax
Legacy Products
Description
AXB (Exchange Trace A and Trace B)
Syntax
Legacy Products
Description
B1 [one] (Clear Write for Trace B)
Syntax
Legacy Products
Description
B2 [two] (Maximum Hold for Trace B)
Syntax
Legacy Products
Description
B3 [three] (View Mode for Trace B)
Syntax
Legacy Products
Description
B4 [four] (Blank Trace B)
Syntax
Legacy Products
Description
BL (Trace B minus Display Line to Trace B)
Syntax
Legacy Products
Description
BLANK (Blank Trace)
Syntax
Legacy Products
Description
BML (Trace B Minus Display Line)
Syntax
Legacy Products
Description
21
736
736
736
736
737
737
737
737
738
738
738
738
739
739
739
739
739
739
740
740
740
740
740
740
741
741
741
741
741
741
742
742
742
742
742
742
743
743
743
743
744
744
744
744
Remote Language Compatibility Measurement Application Reference
Table Of Contents
BTC (Transfer Trace B to Trace C)
Syntax
Legacy Products
Description
BXC (Exchange Trace B and Trace C)
Syntax
Legacy Products
Description
C1 [one] (Set A Minus B Mode Off)
Syntax
Legacy Products
Description
C2 [two] (A Minus B Into A)
Syntax
Legacy Products
Description
CA (Couple Attenuation)
Syntax
Legacy Products
Description
CARROFF (Carrier Off Power)
Syntax
Legacy Products
Description
CARRON (Carrier On Power)
Syntax
Legacy Products
Description
CF (Center Frequency)
Syntax
Legacy Products
Description
CHANNEL (Channel Selection)
Syntax
Legacy Products
Description
CHANPWR (Channel Power)
Syntax
Legacy Products
Description
CHPWRBW (Channel Power Bandwidth)
Syntax
Legacy Products
Remote Language Compatibility Measurement Application Reference
744
744
745
745
745
745
745
745
746
746
746
746
747
747
747
747
748
748
748
748
749
749
749
749
749
749
750
750
750
750
750
750
751
751
751
751
752
752
752
752
753
753
753
22
Table Of Contents
Description
CLRAVG (Clear Average)
Syntax
Legacy Products
Description
CLRW (Clear Write)
Syntax
Legacy Products
Description
CNVLOSS (Conversion Loss Compensation)
Syntax
Legacy Products
Description
CONTS (Continuous Sweep)
Syntax
Legacy Products
Description
COUPLE (Input Coupling)
Syntax
Legacy Products
Description
CR (Couple Resolution Bandwidth)
Syntax
Legacy Products
Description
CS (Couple Frequency Step Size)
Syntax
Legacy Products
Description
CT (Couple Sweep Time)
Syntax
Legacy Products
Description
CV (Couple Video Bandwidth)
Syntax
Legacy Products
Description
DA (Display Address)
Syntax
Legacy Products
Description
DELMKBW (Occupied Power Bandwidth Within Delta Marker)
Syntax
Legacy Products
23
753
753
753
753
754
754
754
754
754
756
756
756
756
757
757
757
757
758
758
758
758
759
759
759
759
760
760
760
760
761
761
761
761
762
762
762
762
762
762
762
762
763
763
763
Remote Language Compatibility Measurement Application Reference
Table Of Contents
Description
DET (Detection Mode)
Syntax
Legacy Products
Description
DL (Display Line)
Syntax
Legacy Products
Description
DLE (Display Line Enable)
Syntax
Legacy Products
Description
DLYSWP (Delay Sweep)
Syntax
Legacy Products
Description
DONE (Done)
Syntax
Legacy Products
Description
DR (Display Read)
Syntax
Legacy Products
Description
E1[one] (Peak Marker)
Syntax
Legacy Products
Description
E2 [two] (Marker to Center Frequency)
Syntax
Legacy Products
Description
E3 [three] (Delta Marker Step Size)
Syntax
Legacy Products
Description
E4 [four] (Marker to Reference Level)
Syntax
Legacy Products
Description
EDITDONE (Edit Done)
Syntax
Remote Language Compatibility Measurement Application Reference
763
764
764
764
764
765
765
765
765
766
766
766
766
767
767
767
767
768
768
768
768
768
768
768
768
769
769
769
769
770
770
770
770
770
770
771
771
771
771
771
771
772
772
24
Table Of Contents
Legacy Products
Description
EDITLIML (Edit Limit Line)
Syntax
Legacy Products
Description
ERR (Error)
Syntax
Legacy Products
Description
ET (Elapsed Time)
Syntax
Legacy Products
Description
EX (Exchange Trace A and Trace B)
Syntax
Legacy Products
Description
FA (Start Frequency)
Syntax
Legacy Products
Description
FB (Stop Frequency)
Syntax
Legacy Products
Description
FDSP (Frequency Display Off)
Syntax
Legacy Products
Description
FOFFSET (Frequency Offset)
Syntax
Legacy Products
Description
FPKA (Fast Preselector Peak)
Syntax
Legacy Products
Description
FREF (Frequency Reference)
Syntax
Legacy Products
Description
FS (Full Span)
Syntax
25
772
772
773
773
773
773
774
774
774
774
776
776
776
776
776
776
776
777
777
777
777
777
778
778
778
778
779
779
779
779
780
780
780
780
781
781
781
781
782
782
782
782
782
782
Remote Language Compatibility Measurement Application Reference
Table Of Contents
Legacy Products
Description
FULBAND
Syntax
Legacy Products
Description
GATE (Gate)
Syntax
Legacy Products
Description
GATECTL (Gate Control)
Syntax
Legacy Products
Description
GD (Gate Delay)
Syntax
Legacy Products
Description
GL (Gate Length)
Syntax
Legacy Products
Description
GP (Gate Polarity)
Syntax
Legacy Products
Description
GRAT (Graticule)
Syntax
Legacy Products
Description
HD (Hold Data Entry)
Syntax
Legacy Products
Description
HNLOCK (Harmonic Lock)
Syntax
Legacy Products
Description
I1 [one] (Set RF Coupling to DC)
Syntax
Legacy Products
Description
I2 [two] (Set RF Coupling to AC)
Remote Language Compatibility Measurement Application Reference
783
783
785
785
785
785
786
786
786
786
786
786
787
787
787
787
787
787
788
788
788
788
789
789
789
789
790
790
790
790
791
791
791
791
792
792
792
792
793
793
793
793
794
26
Table Of Contents
Syntax
Legacy Products
Description
ID (Identify)
Syntax
Legacy Products
Description
IP (Instrument Preset)
Syntax
Legacy Products
Description
KS, (Mixer Level)
Syntax
Legacy Products
Description
KS= (8566A/B: Automatic Preselector Tracking, 8568A/B: Marker Counter
Resolution)
Syntax
Legacy Products
Description
KS( (Lock Registers)
Syntax
Legacy Products
Description
KS) (Unlock Registers)
Syntax
Legacy Products
Description
KSA (Amplitude in dBm)
Syntax
Legacy Products
Description
KSa (Normal Detection)
Syntax
Legacy Products
Description
KSB (Amplitude in dBmV)
Syntax
Legacy Products
Description
KSb (Positive Peak Detection)
Syntax
Legacy Products
Description
27
794
795
795
796
796
796
796
797
797
797
797
798
798
798
798
799
799
799
799
799
799
799
800
800
800
800
800
800
800
800
801
801
801
801
801
801
801
801
801
802
802
802
802
Remote Language Compatibility Measurement Application Reference
Table Of Contents
KSC (Amplitude in dBμV)
Syntax
Legacy Products
Description
KSc (A Plus B to A)
Syntax
Legacy Products
Description
KSD (Amplitude in Volts)
Syntax
Legacy Products
Description
KSd (Negative Peak Detection)
Syntax
Legacy Products
Description
KSE (Title Mode)
Syntax
Legacy Products
Description
KSe (Sample Detection)
Syntax
Legacy Products
Description
KSG (Video Averaging On)
Syntax
Legacy Products
Description
KSg (Display Off)
Syntax
Legacy Products
Description
KSH (Video Averaging Off)
Syntax
Legacy Products
Description
KSh (Display On)
Syntax
Legacy Products
Description
KSI (Extend Reference Level)
Syntax
Legacy Products
Remote Language Compatibility Measurement Application Reference
802
802
802
802
803
803
803
803
803
803
803
803
804
804
804
804
804
804
804
804
804
804
805
805
805
805
805
805
806
806
806
806
806
806
806
806
807
807
807
807
807
807
807
28
Table Of Contents
Description
KSi (Exchange Trace B and Trace C)
Syntax
Legacy Products
Description
KSj (View Trace C)
Syntax
Legacy Products
Description
KSK (Marker to Next Peak)
Syntax
Legacy Products
Description
KSk (Blank Trace C)
Syntax
Legacy Products
Description
KSL (Marker Noise Off)
Syntax
Legacy Products
Description
KSl (Transfer Trace B to Trace C)
Syntax
Legacy Products
Description
KSM (Marker Noise On)
Syntax
Legacy Products
Description
KSm (Graticule Off)
Syntax
Legacy Products
Description
KSN (Marker Minimum)
Syntax
Legacy Products
Description
KSn (Graticule On)
Syntax
Legacy Products
Description
KSO (Marker Span)
Syntax
Legacy Products
29
807
808
808
808
808
808
808
809
809
809
809
809
809
810
810
810
810
810
810
810
810
810
810
811
811
811
811
811
811
812
812
812
812
812
812
812
812
813
813
813
813
813
813
813
Remote Language Compatibility Measurement Application Reference
Table Of Contents
Description
KSo (Annotation Off)
Syntax
Legacy Products
Description
KSP (GPIB Address)
Syntax
Legacy Products
Description
KSp (Annotation On)
Syntax
Legacy Products
Description
KST (Fast Preset)
Syntax
Legacy Products
Description
KSV (Frequency Offset)
Syntax
Legacy Products
Description
KSx (External Trigger)
Syntax
Legacy Products
Description
KSy (Video Trigger)
Syntax
Legacy Products
Description
KSZ (Reference Level Offset)
Syntax
Legacy Products
Description
L0 [zero] (Display Line Off)
Syntax
Legacy Products
Description
LF (Low Frequency Preset)
Syntax
Legacy Products
Description
LG (Logarithmic Scale)
Syntax
Remote Language Compatibility Measurement Application Reference
813
814
814
814
814
814
814
814
814
815
815
815
815
815
815
815
815
816
816
816
816
816
816
816
816
817
817
817
817
818
818
818
818
819
819
819
819
819
819
819
819
820
820
30
Table Of Contents
Legacy Products
Description
LIMF (Limit Line Frequency Value)
Syntax
Legacy Products
Description
LIMIFAIL (Limits Failed)
Syntax
Legacy Products
Description
Query Data Type Codes
LIMIPURGE (Delete Current Limit Line)
Syntax
Legacy Products
Description
LIMIRCL (Recall Limit Line)
Syntax
Legacy Products
Description
LIMIREL (Relative Limit Lines)
Syntax
Legacy Products
Description
LIMISAV (Save Limit Line)
Syntax
Legacy Products
Description
LIML (Lower-Limit Amplitude)
Syntax
Legacy Products
Description
LIMTFL (Flat Limit Line)
Syntax
Legacy Products
Description
LIMITST (Activate Limit Line Test Function)
Syntax
Legacy Products
Description
LIMTSL (Slope Limit Line)
Syntax
Legacy Products
Description
LIMU (Upper-Limit Amplitude)
31
820
820
821
821
821
821
822
822
822
822
822
822
822
823
823
823
823
823
823
824
824
824
824
824
824
824
824
825
825
825
825
825
825
826
826
826
826
826
826
827
827
827
827
827
Remote Language Compatibility Measurement Application Reference
Table Of Contents
Syntax
Legacy Products
Description
LN (Linear Scale)
Syntax
Legacy Products
Description
M1 [one] (Marker Off)
Syntax
Legacy Products
Description
M2 [two] (Marker Normal)
Syntax
Legacy Products
Description
M3 [three] (Delta Marker)
Syntax
Legacy Products
Description
M4 [four] (Marker Zoom)
Syntax
Legacy Products
Description
MA (Marker Amplitude Output)
Syntax
Legacy Products
Description
MC0 [zero] (Marker Frequency Counter Off)
Syntax
Legacy Products
Description
MC1 [one] (Marker Frequency Counter On)
Syntax
Legacy Products
Description
MDS (Measurement Data Size)
Syntax
Legacy Products
Description
MDU (Measurement Data Units)
Syntax
Legacy Products
Description
Remote Language Compatibility Measurement Application Reference
827
827
827
828
828
828
828
829
829
829
829
830
830
830
830
831
831
831
831
832
832
832
833
833
833
833
833
834
834
834
834
834
834
834
834
835
835
835
835
835
835
835
836
32
Table Of Contents
MEAN (Trace Mean)
Syntax
Legacy Products
Description
MEANPWR (Mean Power measurement)
Syntax
Legacy Products
Description
MEAS (Meas)
Syntax
Legacy Products
Description
MF (Marker Frequency Output)
Syntax
Legacy Products
Description
MINH (Minimum Hold)
Syntax
Legacy Products
Description
MINPOS (Minimum X Position)
Syntax
Legacy Products
Description
MKA (Marker Amplitude)
Syntax
Legacy Products
Description
MKACT (Activate Marker)
Syntax
Legacy Products
Description
MKBW (Marker Bandwidth)
Syntax
Legacy Products
Description
MKCF (Marker to Center Frequency)
Syntax
Legacy Products
Description
MKD (Marker Delta)
Syntax
Legacy Products
Description
33
836
836
836
836
837
837
837
837
838
838
838
838
838
838
839
839
840
840
840
840
840
840
840
840
841
841
841
841
842
842
842
842
842
842
842
843
843
843
843
843
844
844
844
844
Remote Language Compatibility Measurement Application Reference
Table Of Contents
MKF (Marker Frequency)
Syntax
Legacy Products
Description
MKFC (Marker Counter)
Syntax
Legacy Products
Description
MKFCR (Marker Counter Resolution)
Syntax
Legacy Products
Description
MKMIN (Marker Minimum)
Syntax
Legacy Products
Description
MKN (Marker Normal)
Syntax
Legacy Products
Description
MKNOISE (Marker Noise)
Syntax
Legacy Products
Description
MKOFF (Marker Off)
Syntax
Legacy Products
Description
MKP (Marker Position)
Syntax
Legacy Products
Description
MKPK (Marker Peak)
Syntax
Legacy Products
Description
MKPT (Marker Threshold)
Syntax
Legacy Products
Description
MKPX (Marker Peak Excursion)
Syntax
Legacy Products
Remote Language Compatibility Measurement Application Reference
845
845
845
845
846
846
846
846
847
847
848
848
848
848
848
848
849
849
849
849
850
850
850
850
851
851
851
851
851
851
851
851
852
852
852
852
853
853
853
853
854
854
854
34
Table Of Contents
Description
MKREAD (Marker Readout)
Syntax
Legacy Products
Description
MKRL (Marker to Reference Level)
Syntax
Legacy Products
Description
MKSP (Marker Span)
Syntax
Legacy Products
Description
MKSS (Marker to Step Size)
Syntax
Legacy Products
Description
MKT (Marker Time)
Syntax
Legacy Products
Description
MKTRACE (Marker Trace)
Syntax
Legacy Products
Description
MKTRACK (Marker Track)
Syntax
Legacy Products
Description
MKTYPE (Marker Type)
Syntax
Legacy Products
Description
ML (Mixer Level)
Syntax
Legacy Products
Description
MT0 [zero] (Marker Track Off)
Syntax
Legacy Products
Description
MT1 [one] (Marker Track On)
Syntax
Legacy Products
35
854
855
855
855
855
856
856
856
856
857
857
857
857
858
858
858
858
858
858
859
859
859
859
859
859
860
860
860
860
861
861
861
861
862
862
862
862
863
863
863
863
864
864
864
Remote Language Compatibility Measurement Application Reference
Table Of Contents
Description
MXMH (Maximum Hold)
Syntax
Legacy Products
Description
MXRMODE (Mixer Mode)
Syntax
Legacy Products
Description
NORMLIZE (Normalize Trace Data)
Syntax
Legacy Products
Description
NRL (Normalized Reference Level)
Syntax
Legacy Products
Description
NRPOS (Normalized Reference Position)
Syntax
Legacy Products
Description
O1 [one] (Format - Display Units)
Syntax
Legacy Products
Description
O2 [two] (Format - Two 8-Bit Bytes)
Syntax
Legacy Products
Description
O3 [three] (Format - Real Amplitude Units)
Syntax
Legacy Products
Description
O4 [four] (Format - One 8-Bit Byte)
Syntax
Legacy Products
Description
OA or ? (Query Active Function)
Legacy Products
Description
OCCUP (Percent Occupied Power Bandwidth)
Syntax
Legacy Products
Remote Language Compatibility Measurement Application Reference
864
864
864
865
865
865
865
865
865
866
866
866
866
867
867
867
867
868
868
868
868
868
868
868
869
869
869
869
869
869
869
869
869
870
870
870
870
870
870
870
871
871
871
36
Table Of Contents
Description
OL (Output Learn String)
Syntax
Legacy Products
Description
OT (Output Trace Annotations)
Syntax
Legacy Products
Description
PEAKS (Peaks)
Syntax
Legacy Products
Description
PKPOS (Peak Position)
Syntax
Legacy Products
Description
PLOT (Plot)
Syntax
Legacy Products
Description
PP (Preselector Peak)
Syntax
Legacy Products
Description
PRINT (Print)
Syntax
Legacy Products
Description
PWRBW (Power Bandwidth)
Syntax
Legacy Products
Description
Q0 [zero] (Set Detector to EMI Peak Detection)
Syntax
Legacy Products
Description
Q1 [one] (Set Detector to Quasi Peak Detection)
Syntax
Legacy Products
Description
R1 [one] (Illegal Command SRQ)
Syntax
Legacy Products
37
871
871
871
871
872
873
873
873
874
875
875
875
875
876
876
876
876
876
876
876
876
877
877
877
877
878
878
878
878
878
878
879
879
879
879
879
879
880
880
880
880
880
880
880
Remote Language Compatibility Measurement Application Reference
Table Of Contents
Description
R2 [two] (End-of-Sweep SRQ)
Syntax
Legacy Products
Description
R3 [three] (Hardware Broken SRQ)
Syntax
Legacy Products
Description
R4 [four] (Units-Key-Pressed SRQ)
Syntax
Legacy Products
Description
RB (Resolution Bandwidth)
Syntax
Legacy Products
Description
RBR (Resolution Bandwidth to Span Ratio)
Syntax
Legacy Products
Description
RC (Recall State)
Syntax
Legacy Products
Description
RCLS (Recall State)
Syntax
Legacy Products
Description
REV (Revision)
Syntax
Legacy Products
Description
RL (Reference Level)
Syntax
Legacy Products
Description
RMS (Root Mean Square Value)
Syntax
Legacy Products
Description
ROFFSET (Reference Level Offset)
Syntax
Remote Language Compatibility Measurement Application Reference
880
881
881
881
881
881
881
881
881
881
881
882
882
882
882
883
883
884
884
884
884
884
884
885
885
886
886
886
886
887
887
887
887
887
887
888
888
889
889
889
889
889
889
38
Table Of Contents
Legacy Products
Description
RQS (Request Service Conditions)
Syntax
Legacy Products
Description
S1[one] (Continuous Sweep)
Syntax
Legacy Products
Description
S2 [two] (Single Sweep)
Syntax
Legacy Products
Description
SADD (Add Limit Line Segment)
Syntax
Legacy Products
Description
SAVES (Save State)
Syntax
Legacy Products
Description
SDEL (Delete Limit Line Segment)
Syntax
Legacy Products
Description
SDON (Terminate SEDI Command)
Syntax
Legacy Products
Description
SEDI (Edit Limit Line Segment)
Syntax
Legacy Products
Description
SER (Serial Number)
Syntax
Legacy Products
Description
SETDATE (Set Date)
Syntax
Legacy Products
Description
SETTIME (Set Time)
Syntax
39
890
890
891
891
891
891
892
892
892
892
893
893
893
893
893
893
893
893
894
894
894
894
894
894
894
894
895
895
895
895
895
895
895
895
896
896
896
896
896
896
896
897
897
897
Remote Language Compatibility Measurement Application Reference
Table Of Contents
Legacy Products
Description
SMOOTH (Smooth Trace)
Syntax
Legacy Products
Description
SNGLS (Single Sweep)
Syntax
Legacy Products
Description
SP (Frequency Span)
Syntax
Legacy Products
Description
SRQ (Service Request)
Syntax
Legacy Products
Description
SS (Center Frequency Step Size)
Syntax
Legacy Products
Description
ST (Sweep Time)
Syntax
Legacy Products
Description
STB (Status Byte Query)
Syntax
Legacy Products
Description
STDEV (Standard Deviation of Trace Amplitudes)
Syntax
Legacy Products
Description
SUM (Sum)
Syntax
Legacy Products
Description
SV (Save State)
Syntax
Legacy Products
Description
SWPCPL (Sweep Couple)
Remote Language Compatibility Measurement Application Reference
897
897
898
898
898
898
899
899
899
899
899
899
900
901
901
901
901
902
902
902
903
903
903
903
904
904
905
905
905
905
905
905
905
905
906
906
906
906
907
907
907
907
907
40
Table Of Contents
Syntax
Legacy Products
Description
T0 [zero] (Turn Off Threshold Level)
Syntax
Legacy Products
Description
T1 [one] (Free Run Trigger)
Syntax
Legacy Products
Description
T2 [two] (Line Trigger)
Syntax
Legacy Products
Description
T3 [three] (External Trigger)
Syntax
Legacy Products
Description
T4 [four] (Video Trigger)
Syntax
Legacy Products
Description
TA (Trace A)
Syntax
Legacy Products
Description
TB (Trace B)
Syntax
Legacy Products
Description
TDF (Trace Data Format)
Syntax
Legacy Products
Description
TH (Threshold)
Syntax
Legacy Products
Description
THE (Threshold Enable)
Syntax
Legacy Products
Description
TIMEDATE (Time Date)
41
907
908
908
908
908
908
908
909
909
909
909
909
909
910
910
910
910
910
910
911
911
911
911
911
911
912
912
912
912
912
912
913
913
913
913
914
914
914
915
915
915
915
915
916
Remote Language Compatibility Measurement Application Reference
Table Of Contents
Syntax
Legacy Products
Description
TITLE (Title)
Syntax
Legacy Products
Description
TM (Trigger Mode)
Syntax
Legacy Products
Description
TRA (Trace Data Input and Output)
Syntax
Legacy Products
Description
TRB (Trace Data Input and Output)
Syntax
Legacy Products
Description
TRC (Trace Data Input and Output)
Syntax
Legacy Products
Description
TRDSP (Trace Display)
Syntax
Legacy Products
Description
TRIGPOL (Trigger Polarity)
Syntax
Legacy Products
Description
TRSTAT (Trace State)
Syntax
Legacy Products
Description
TS (Take Sweep)
Syntax
Legacy Products
Description
USERREV
Syntax
Legacy Products
Description
Remote Language Compatibility Measurement Application Reference
916
916
916
917
917
917
917
917
917
918
918
919
919
919
919
919
919
920
920
920
920
920
920
921
921
921
921
921
921
921
922
922
922
922
922
923
923
923
923
923
923
923
923
42
Table Of Contents
VAVG (Video Average)
Syntax
Legacy Products
Description
VB (Video Bandwidth)
Syntax
Legacy Products
Description
VBO (Video Bandwidth Coupling Offset)
Syntax
Legacy Products
Description
VBR (Video Bandwidth to Resolution Bandwidth Ratio)
Syntax
Legacy Products
Description
VIEW (View Trace)
Syntax
Legacy Products
Description
VTL (Video Trigger Level)
Syntax
Legacy Products
Description
XCH (Exchange)
Syntax
Legacy Products
Description
43
924
924
924
925
926
926
927
927
927
927
927
927
928
928
928
928
929
929
929
929
930
930
930
930
931
931
931
931
Remote Language Compatibility Measurement Application Reference
Keysight X-Series Signal Analyzer
Remote Language Compatibility Measurement Application Reference
1 Special Information for the N9061C Measurement Application
This chapter provides information that is specific to the N9061C application.
It includes the following topics:
– "N9061C Application Description" on page 45
– "General Rules and Limitations" on page 46
– "Hardware and Firmware Requirements for N9061C" on page 50
– "Hints and Tips" on page 51
44
1 Special Information for the N9061C Measurement Application
N9061C Application Description
N9061C Application Description
N9061C is a Remote Language Compatibility application for Keysight Technologies
X-Series instruments. It allows X-Series instruments to be controlled using many
non-SCPI remote programming commands originally intended for the following
analyzers:
– 8560 E/EC Series Portable Spectrum Analyzers, comprising: 8560E, 8560EC,
8561E, 8561EC, 8562E, 8562EC, 8563E, 8563EC, 8564E, 8564EC, 8565E,
8565EC
– 8566A/B
– 8568A/B
(The 8566A/B and the 8568A/B are not considered part of the 8560 series of
analyzers.)
An X-Series instrument with N9061C installed can replace these analyzers in many
automated systems with minimal or no modification to the existing measurement
software.
45
Remote Language Compatibility Measurement Application Reference
1 Special Information for the N9061C Measurement Application
General Rules and Limitations
General Rules and Limitations
The N9061C application has been designed to emulate as closely as possible the
operation of the specified spectrum analyzers. It is not, however, intended as a fullycompatible, direct replacement for these analyzers. This section highlights the
following specific emulation differences and limitations:
– "AC/DC Coupling" on page 46
– "Couplings" on page 47
– "Markers" on page 47
– "Numeric Ranges" on page 47
– "Parsing" on page 47
– "Predefined Functions" on page 47
– "Remote Control" on page 48
– "Returning Data" on page 48
– "Units" on page 48
– "User-defined Functions" on page 48
– "Supported Commands" on page 48
– "EP Parameter" on page 49
– "OA Parameter" on page 49
– "Handling of Unsupported Commands and Queries" on page 49
AC/DC Coupling
The 44 GHz and 50 GHz X-Series instruments only have DC coupling. The X-Series
instruments with a 26.5 GHz frequency range, and lower, default to AC coupling on
preset. When the selected legacy instrument is HP8566A, HP8566B, HP8563,
HP8564, or HP8565, N9061C defaults to DC coupling.
When AC coupled, the 8560E/61E/62E have a 100 kHz low frequency limit, whereas
X-Series instruments have a 10 MHz limit.
For HP8568A/B compatibility and consistency, N9061C supports the I1 and I2
commands. These select AC or DC coupling at the RF input. Note that the
HP8568A/B has two RF input ports, whereas X-Series instruments have only one.
Remote Language Compatibility Measurement Application Reference
46
1 Special Information for the N9061C Measurement Application
General Rules and Limitations
Couplings
For optimal use of the X-Series instrument, N9061C uses the auto coupling features
of the X-Series, and does not attempt to mimic the exact coupling behavior of the
legacy analyzers. To eliminate the possibility of "Meas Uncal" errors between auto
and manual values, values generally default to the X-Series auto settings where
applicable (for example, Resolution Bandwidth). However, there are several
exceptions, as follows:
To prevent timeout errors in the legacy code, the Resolution Bandwidth minimum
matches the minimum in the legacy analyzer. Resolution Bandwidth steps and
resolution, however, conform to X-Series values.
The Video Bandwidth couples to the Resolution Bandwidth according to the Video
Bandwidth coupling offset value, specified by the VBO or VBR command. X-Series
instruments set the Video Bandwidth according to the VBO or VBR setting, but use the
X-Series instruments’ available bandwidths, to prevent 'Meas Uncal' errors.
Markers
N9061C emulates the behavior of legacy products. If any program uses a marker
state that is not available in the legacy instrument, further marker behavior is
undefined, until a subsequent instrument preset occurs.
On systems that support MKACT, there are 4 completely different marker pairs, each
with its own information. N9061C stores the currently active value of MKACT. For
example, if MKACT is 2, then it uses Markers 3 and 4 instead of 1 and 2.
Numeric Ranges
Numeric ranges are limited to that of X-Series unless otherwise stated, although
commands such as FS or IP that go to a default range use the range of the legacy
instrument.
Parsing
For 8566B and 8568B emulation, N9061C remembers the active function and
supports UP, DN, and OA, all of which change the active function. It also supports ?,
which does not change the active function.
Note that 8566/68 parses a command (for example CF 10.3GZ) immediately when it
recognizes a complete command (in this example, following GZ), whereas N9061C
parses at the end of a line, when it sees the line termination sequence.
Predefined Functions
In the 8566/8568/8560 Series analyzers, a “Predefined Function” is a command that
returns a number that can be operated on by other commands. “Predefined
Variables” follow the same concept, except that the value to be passed as a
parameter to the next command is stored in a variable.
47
Remote Language Compatibility Measurement Application Reference
1 Special Information for the N9061C Measurement Application
General Rules and Limitations
N9061C does not support this type of behavior, so any commands that originally
acted as Predefined Functions or Variables, or that accepted Predefined Functions
or Variables as arguments in the 8566/8568/8560 Series, no longer do so.
Remote Control
N9061C supports remote operation only via the GPIB interface. It does not support
operation via LAN, USB or Telnet.
Returning Data
X-Series and legacy instruments adopt differing approaches when returning data to
the controller.
X-Series and 8560-series analyzers operate a FIFO buffer for command return
values. If a command returns a value that the controller does not read, the returned
data is stored until such a time that the controller requires the value. In N9061C's
8560-series emulation mode, for example, if CF?MA?FA? is sent, the first query
returns the result of CF?, the second query returns the result of MA? and the third
query returns the result of FA?.
The 8566, 8568, and 8590-series legacy analyzers store only one value at a time.
Any value stored is overwritten each time a command returns a value. N9061C
handles this difference appropriately only within a single command string. In
N9061C's 8566 and 8568 emulation mode, for example, if CF?MA?FA? is sent, only
the result of FA? is returned.
Units
N9061C supports all units used in legacy products. The accepted units are HZ, KHZ,
MHZ, GHZ, KZ, MZ, GZ, DBM, DBMV, DBUV, MV, UV, V, MW, UW, W, DB, DM, MS,
US, SC, and S (case insensitive in 8566/68). A command terminator, such as ";", also
acts as a unit terminator.
User-defined Functions
User-defined functions, traces, or variables (FUNCDEF, TRDEF or VARDEF) cannot be
used as arguments or commands in programs for N9061C. In addition, the behavior
of certain commands that rely on the “active functions” (UP, DN, etc.) may be slightly
different.
Supported Commands
N9061C supports only a subset of 8566/8568/8560 Series commands. The list of
supported commands was determined by feedback from customers, combined with
technical considerations and constraints.
Device Clear is supported by N9061C, and causes a mode preset of the instrument.
Remote Language Compatibility Measurement Application Reference
48
1 Special Information for the N9061C Measurement Application
General Rules and Limitations
EP Parameter
The EP (Enable Parameter) is supported by N9061C for the same active functions as
the 8560 series. When used as a secondary keyword after a command, EP transfers
control to the analyzer’s front-panel.
EP is not displayed in any of the format diagrams for individual commands listed in
"Legacy Command Descriptions" on page 707.
OA Parameter
N9061C supports the OA parameter, which is used in conjunction with several legacy
commands, such as AT and CF. OA is equivalent to a query; for example, CF OA is
equivalent to CF?.
Handling of Unsupported Commands and Queries
If a command is valid for legacy products but not supported by N9061C, no error
message is generated, although a "Command Not Supported" comment is appended
to the Command Log file. Note that this logging behavior can be controlled via the
Logging menu, as described in "Logging" on page 253.
If N9061C receives a query that is valid for legacy products, but is not supported by
N9061C, it returns a "0", to avoid the situation where a program would otherwise
halt indefinitely waiting for a return value.
49
Remote Language Compatibility Measurement Application Reference
1 Special Information for the N9061C Measurement Application
Hardware and Firmware Requirements for N9061C
Hardware and Firmware Requirements for N9061C
For maximum compatibility, you should select an X-Series instrument that equals or
exceeds the frequency range of the legacy analyzer you are replacing. The
frequency limits of the legacy analyzers are listed below.
Frequency Ranges of Legacy Analyzers
Remote Language
Start Frequency
Stop Frequency
8560E/EC
30 Hz
2.9 GHz
8561E/EC
30 Hz
6.5 GHz
8562E/EC
30 Hz
13.2 GHz
8563E/EC
9 kHz
26.5 GHz
8564E/EC
9 kHz
40.0 GHz
8565E/EC
9 kHz
50.0 GHz
HP8566A
2 GHz
22 GHz
HP8566B
2 GHz
22 GHz
HP8568A
0 Hz
1.5 GHz
HP8568B
0 Hz
1.5 GHz
Remote Language Compatibility Measurement Application Reference
50
1 Special Information for the N9061C Measurement Application
Hints and Tips
Hints and Tips
This section provides hints and tips that will help you get the most from the X-Series
N9061C application.
Compatibility (Speed and Consistency)
To maximize compatibility with your legacy analyzer, the N9061C application should
be used on the instrument whose frequency range most closely matches the
frequency range of your legacy analyzer. For example, the best match for the 8563E,
which has a 26.5 GHz upper frequency limit, is an X-Series instrument that also has
an upper frequency limit of 26.5 GHz.
Compatibility and Sweep Times
To maximize compatibility between X-Series instruments and legacy analyzers, use
the Manual Swept mode for 8566A/B, 8568A/B analyzers. Manual Swept mode is
the default setting on X-Series instruments with N9061C installed.
When analyzing stationary signals, you can change to the Best Speed setting, which
is accessed from the Mode Setup > Preferences > Swp Type Rule menu. This results
in faster sweep times on an X-Series instrument than on the legacy analyzers, due
to the X-Series instrument’s better performance. In the majority of applications, this
faster speed would be desirable, but that is not always the case.
Timeout
Keysight recommends increasing the timeout on a serial poll (SPOLL) due to
differences in Sweep Times on some settings. Note, however, that this may not be
necessary when using the Best Speed setting on the Preferences > Swp Type Rule
menu (accessed from the Mode Setup hardkey).
Synchronization (1)
To synchronize after an IP command, Keysight recommends that you use the DONE
command. We also suggest that the DONE command be used in conjunction with a
timeout of about 5 seconds, in case the instrument starts to Auto Align.
Alternatively, you can switch off auto alignment. To set auto alignment to Off, press
System, Alignments, Auto Align on the front panel.
Synchronization (2)
Keysight recommends that synchronization (using the DONE command) be used with
marker functions when signal tracking is turned on.
Changing Modes
After changing into or out of N9061C mode, allow at least a 1 second delay before
sending subsequent commands.
51
Remote Language Compatibility Measurement Application Reference
1 Special Information for the N9061C Measurement Application
Hints and Tips
AC and DC Coupling
The 8560 Series of legacy analyzers have one RF input port, and support AC and DC
coupling through the command "COUPLE (Input Coupling)" on page 758.
The 8568A/B has two RF input ports:
– DC Coupled (with a BNC connector) to handle a frequency range of 100 Hz to 1.5
GHz
– AC Coupled (with an N Type connector) to handle a frequency range of 100 kHz
to 1.5 GHz
If the input signal to the X-series instrument has a DC component, ensure that when
you select legacy instrument emulation that involves a possible coupling change to
DC, the input signal does not exceed the input specifications of the X-series
instrument.
X-series instruments also have one RF input port. When using X-Series instruments,
you must use DC coupling to see calibrated frequencies of less than 20 MHz. Signals
of less than 20 MHz are not calibrated when using AC coupling on these
instruments.
Remote Language Compatibility Measurement Application Reference
52
Keysight X-Series Signal Analyzer
Remote Language Compatibility Measurement Application Reference
2 User Interface
The diagram below shows the basic elements of the Multitouch User Interface.
For more details, click an image region or caption.
This section also includes descriptions of the following front panel keys, which are not
described elsewhere.
For more information, click one of the images or labels.
"Cancel" on page 102
"Onscreen Keyboard"
on page 103
"Touch On/Off" on
page 104
"Tab" on page 105
53
2 User Interface
Screen Tabs
Screen Tabs
The Multitouch UI supports multiple “Screens” (see "Multiscreen" on page 95 for
more information). Each screen displays one Measurement in one Mode.
You can see up to six tabs at a time on UXA, and 4 at a time on CXA, EXA, MXA and
PXA. If there are more Screens configured than this, arrows appear to the left and
right of the Screen Tabs; pressing the arrows scrolls the Screen Tabs to the left or
right.
Pressing a Screen Tab selects that screen for operation. Pressing the blue (selected)
Screen Tab has the same effect as pressing the Mode/Meas front panel key (shown
below). Both actions open the "Mode Meas View dialog" on page 55.
Pressing the Add Screen (+) tab copies the selected screen to a new Screen, with
setup and settings identical to those of the copied Screen.
You can define up to 16 screens at once.
Example Multiscreen View
The example below shows a four-screen display, in Multiscreen view.
The Screen called “Real-Time SA 2” is selected, as indicated by its blue tab.
Touching any other screen or tab selects the screen for that tab and brings it to the
foreground.
54
Remote Language Compatibility Measurement Application Reference
2 User Interface
Screen Tabs
Mode Meas View dialog
The Mode/Meas/View Dialog opens when you press the selected (blue) Screen tab
(see "Screen Tabs" on page 54) or the Mode/Meas front panel key.
This dialog lists available Modes, Measurements and Views, as well as controls for
configuring Screens.
Mode
The first column in the "Mode Meas View dialog" on page 55 allows you to select the
desired Mode (measurement application) from those currently licensed in your
analyzer.
Once a Mode is selected, only the commands that are valid for that mode can be
executed
The :INSTrument[:SELect] command is used to remotely select a Mode by
sending the instrument a parameter which represents the name of the desired Mode
(see "Index to Modes" on page 56 below).
The :INSTrument:NSELect command is used to remotely select a Mode by
sending the Mode Number of the desired Mode.
For more information on Modes, preloading Modes, and memory requirements for
Modes, see "More Information" on page 56
Command
:INSTrument[:SELect] <mode_parameter>
See "Index to Modes" on page 56 below for possible values of <mode_parameter>
:INSTrument[:SELect]?
Remote Language Compatibility Measurement Application Reference
55
2 User Interface
Screen Tabs
Example
:INST SA
Preset
The default Mode is set to SA on a “Restore System Defaults->All”, unless noted below.
For N8973B, N8974B, N8975B, or N8976B: NFIG
State Saved
Saved in instrument state
Select Mode by Number
Command
:INSTrument:NSELect <integer>
:INSTrument:NSELect?
Example
:INST:NSEL 1
Preset
The default Mode is set to 1 on a “Restore System Defaults->All”, unless noted in the table above.
State Saved
Saved in instrument state
Backwards Compatibility
:INSTrument[:SELect] ‘SA’|’PNOISE’|’EDGE’|’GSM’|’BASIC’
Example
:INST ‘SA’
Notes
The query result is not a quoted string. It is an enumeration.
The command must be sequential: that is, continued parsing of commands cannot proceed until
the instrument select is complete and the resultant SCPI trees are available.
Index to Modes
The Mode Number in the table below is the parameter for use with the
:INSTrument:NSELect command. The Mode Parameter is the parameter for use
with the :INSTrument[:SELect] command. Your available choices will depend
upon which applications are installed in your instrument.
Mode
Mode
Number
Mode Parameter
Spectrum Analyzer Mode
1
SA
Real-Time Spectrum Analyzer Mode
2
RTSA
IQ Analyzer Mode
8
BASIC
W-CDMA with HSPA+ Mode
9
WCDMA
Phase Noise Mode
14
PNOISE
Noise Figure Mode
219
NFIGURE
Analog Demod Mode
234
ADEMOD
Pulse Mode
151
PULSEX
LTE Advanced FDD Mode
107
LTEAFDD
LTE Advanced TDD Mode
108
LTEATDD
Bluetooth Mode
228
BT
RLC Mode
266
RLC
More Information
The Mode name appears on the Screen Tab, followed by a number identifying
56
Remote Language Compatibility Measurement Application Reference
2 User Interface
Screen Tabs
which instance of the mode appears on that screen. Each Screen contains one
Mode. The example below shows one Spectrum Analyzer screen and two RealTime Spectrum Analyzer screens. The current Screen contains Real-Time SA 1.
You can specify the order in which the Modes appear in the Mode menu, using the
Configure Applications utility on the Desktop. Using the same utility, you can also
specify a subset of the available applications to load into memory at startup time,
which can reduce the instrument's startup time. During runtime, if an application
that is not loaded into memory is selected (by either pressing that application's
Mode key, or sending the appropriate :INST:SEL command), there will be a pause
while the Application is loaded. During this pause, the message “Loading
application, please wait…” is displayed.
Each application (Mode) that runs in an X-Series instrument consumes virtual
memory. The various applications consume varying amounts of virtual memory,
and as more applications run, the memory consumption increases. Keysight
characterizes each Mode and assigns a memory usage quantity based on a
conservative estimate. The Configure Applications utility shows an estimate for
how much memory each Mode will consume.
Measurement
The Measurement column of the Mode/Meas/View dialog shows all the
Measurements available for the Mode selected in the first column.
When you select a Measurement in the second column, the View column shows all
the Views available for that measurement.
Select the desired Mode, Measurement and View, then press OK in the "Mode Meas
View dialog" on page 55 to change the current Screen to that Mode, Measurement
and View.
View
A View is a collection of Result Windows. The View column of the "Mode Meas View
dialog" on page 55 shows all the Views available for the Measurement selected in
the second column.
Select the desired Mode, Measurement and View, then press OK in the "Mode Meas
View dialog" on page 55 to change the current Screen to that Mode, Measurement
and View.
The View may also be set by using the View tab on the Display menu. The View tab is
the last tab in the Display menu for every measurement. The Views are the same as
those listed in the "Mode Meas View dialog" on page 55.
Remote Language Compatibility Measurement Application Reference
57
2 User Interface
Screen Tabs
Screen
You can configure up to 16 different Screens at one time. Each Screen contains one
Mode, each Mode contains one Measurement, and each Measurement contains a
number of Windows. For each Measurement a number of preset window
configurations are available called Views.
You can configure multiple instances of the same Mode along with any combination
of other Modes. For example, below is shown a 6-Screen configuration utilizing four
different Modes:
58
Remote Language Compatibility Measurement Application Reference
2 User Interface
Screen Tabs
At any given time, only one screen is updating, which is shown by a blue colored
Screen Tab (all the other Screen Tabs are black). Touching any screen makes it the
current Screen and starts it updating.
The picture shown above is taken in “Multiscreen” mode; you can show a single
screen by turning off Multiscreen mode through the use of the icon on the bottom
row:
When this icon is blue, you are in Multiscreen mode; touching it turns it black and
puts you in Single Screen mode:
Remote Language Compatibility Measurement Application Reference
59
2 User Interface
Screen Tabs
Note that the same 6 screens are defined, as shown by the tabs across the top, but
now only one is in the foreground (displayed). Only the one in the foreground is
updating. Touching any screen’s tab brings it to the foreground, makes it the current
Screen and starts it updating.
Select Screen
You can select a screen by touching its tab or, in Multiscreen mode, touching the
screen itself. Selecting the Screen activates the screen and suspends the previously
selected screen (if any).
Command
:INSTrument:SCReen:SELect <screen name>
:INSTrument:SCReen:SELect?
Example
INST:SCR:SEL “Baseband”
Preset
Returns the name of the active screen
Notes
If the <screen name> is specified but not found in the list of Screens, the error
message “-224.1000,Illegal parameter value; Screen Name not found”.
Screen Name
By default, the screen name is the Mode (Application) name followed by a number
indicating the instance of the application.
You may change the name displayed on the Screen Tab of any screen. The control to
do this appears in the "Mode Meas View dialog" on page 55:
60
Remote Language Compatibility Measurement Application Reference
2 User Interface
Screen Tabs
When you touch this control, an onscreen keyboard appears, allowing you to change
the name. Whatever name you enter appears on the Tab, even if you subsequently
change the screen to a different Mode.
To reset the name, delete the screen name entirely.
Each Screen Name must be unique; you cannot give the same name to more than
one screen.
Command
:INSTrument:SCReen:REName <alphanumeric>
Example
INST:SCR:REN “Baseband”
Notes
The currently active screen is renamed.
If the <alphanumeric> specifying the new name is already present in the list of screen names, the
error message “–224.1001,Illegal parameter value; New name <name> already exists”.
Delete This Screen
Pressing this button deletes the current Screen (the one with the blue tab). Deleting
a screen removes it from view and selects the next lower screen in the list of
screens. If only one screen is configured it cannot be deleted.
If you press the Delete This Screen button, a prompt appears:
“This function will delete the current screen and its settings. This action cannot be
undone. Do you want to proceed?”
Pressing OK or Enter deletes the screen, pressing Cancel or ESC does not.
Command
:INSTrument:SCReen:DELete
Example
INST:SCR:DEL
Notes
The currently active screen is deleted.
If the screen you are attempting to delete is the only configured screen, the error message “–
221.9910,Settings conflict; Last screen cannot be deleted” is displayed.
Delete All But This Screen
Pressing this button deletes all the Screens except the current Screen (the one with
the blue tab).
If you press the Delete All But This Screen button, a prompt appears:
“This function will delete all defined screens and their settings, except for the current
screen. This action cannot be undone. Do you want to proceed?”
Pressing OK or Enter deletes the screen, pressing Cancel or ESC does not.
Command
INSTrument:SCReen:DELete:ALL
Remote Language Compatibility Measurement Application Reference
61
2 User Interface
Screen Tabs
Example
INST:SCR:DEL:ALL
Notes
You can reset the instrument to the power-on configuration by invoking INST:SCR:DEL:ALL
followed by SYSTem:DEFault ALL
89600 VSA
Pressing this button launches the 89600 VSA software.
The 89600 VSA software is powerful, PC-based software, offering the industry's
most sophisticated general purpose and standards specific signal evaluation and
troubleshooting tools for R&D engineers. Even for proprietary and non-standard
signals in SATCOM or MILCOM applications, you can make signal quality
measurements with customized IQ constellation.
89600 VSA offers the following features:
– Over 35 general-purpose analog and digital demodulators ranging from 2FSK to
4096QAM
– Flexible and custom IQ and OFDM signal analysis for single carrier
– Standards specific modulation analysis including: – Cellular: GSM/EDGE, cdma2000, W-CDMA, TD-SCDMA, LTE(FDD/TDD),
– LTE-Advanced and more
– Wireless networking: 802.11a/b/g, 802.11n, 802.ac, 802.16 WiMAX
(fixed/mobile), WiSUN (MR-FSK PHY)
– RFID
– Digital satellite video and other satellite signals, radar, LMDS
– Up to 400K bin FFT, for the highest resolution spectrum analysis
– A full suite of time domain analysis tools, including signal capture and playback,
time gating, and CCDF measurements
– 20 simultaneous trace displays and the industry's most complete set of marker
functions
– Easy-to-use Microsoft Windows graphical user interface
For more information, go to the Keysight 89600 Series VSA web site:
www.keysight.com/find/89600vsa
To learn more about how to use 89600 VSA in the instrument, start the 89600 VSA
software, then open the 89600 VSA Help and navigate to the topic "About Keysight
X-Series Signal Analyzer with 89600 VSA Software".
Example
62
INST:SEL VSA89601
Remote Language Compatibility Measurement Application Reference
2 User Interface
Screen Tabs
INST:NSEL 101
Add Screen
You can add screens by pressing the “+” icon in the "Screen Tabs" on page 54 panel.
The icon is shown below.
Every time you add a screen, the instrument copies the selected screen to the new
screen, preserving all the settings of the copied screen. If desired, you can then use
the "Mode Meas View dialog" on page 55 to change the Mode, Measurement and/or
View of the new Screen.
When you have defined the maximum number of screens (16), the “+” icon
disappears.
For more information about operating the instrument with multiple screens
configured, see "Multiscreen" on page 95.
Command
INSTrument:SCReen:CREate
Example
INST:SCR:CRE
Notes
The maximum number of screens is 16. If an attempt to add a screen occurs when the maximum
have been defined the error message “–221.9912, Settings conflict; Screen limit reached” is
generated.
When you create a new screen, the assigned Screen Name is the current Mode name followed by
a number indicating the instance of the Mode.
If the Display is disabled, the message “–221.9913,Settings conflict; Screen SCPI cannot be used
when Display is disabled” is generated.
Remote Language Compatibility Measurement Application Reference
63
2 User Interface
System
System
The System hardkey
and the gear icon
both open the System Settings dialog, which allows you to access various
configuration menus and dialogs. The tabs on the left side let you access various
configuration screens.
Notes
64
No remote command for this key specifically.
Remote Language Compatibility Measurement Application Reference
2 User Interface
Preset
Preset
The Preset functions are available in two ways; either by pressing the Mode Preset
or User Preset front panel keys, or from the Preset dropdown menu that appears
when you press the green Preset icon in the upper right corner of the display.
Types of Preset
The table below shows all possible presets, their corresponding SCPI commands
and front-panel access methods.
Instrument settings are tiered in scope from those local to the current
measurement to those global to all measurements and modes. There are presets
tailored to each scope. The table identifies the scope of each preset type.
To get a Mode back to a fully predefined state, you should execute a Restore Mode
Defaults and an Input/Output Preset, but since Input/Output Preset is a global
function, it affects all modes.
Type Of
Preset
SCPI Command
Scope of Preset
Front Panel
Access
Auto Couple
:COUPle ALL
Local to the current
measurement, only affects
Auto/Man variables
Meas Setup
Menu
Remote Language Compatibility Measurement Application Reference
65
2 User Interface
Preset
66
Type Of
Preset
SCPI Command
Scope of Preset
Front Panel
Access
Meas Preset
:CONFigure:<meas>
Local to the current
measurement
Meas Setup
Menu
Mode Preset
:SYSTem:PRESet
Local to the current mode,
global to all measurements in
the mode, affects most but not
all parameters in the mode,
does not affect Input/Output or
System variables
Mode Preset
(green key)
and Preset
Dropdown
Restore Mode
Defaults
:INSTrument:DEFault
Local to the current mode,
global to all measurements in
the mode, affects all
parameters in the mode but
does not affect Input/Output or
System variables
Preset
Dropdown
Restore
Defaults All
Modes
:SYSTem:DEFault MODes
Affects all parameters in ALL
modes but does not affect
Input/Output or System
variables
Preset
Dropdown
Restore
Screen
Defaults
:SYSTem:DEFault SCReen
Deletes all Screens but one,
restores that screen to its
default mode and performs a
Mode Preset for that mode.
Does not affect Input/Output or
System variables.
Preset
Dropdown
User Preset
:SYSTem:PRESet:USER
Local to the current mode,
global to all measurements in
the mode, affects all
parameters in the mode as well
as the Input/Output variables.
Does not affect System
variables.
User Preset
hardkey and
Preset
Dropdown
User Preset
All Modes
:SYSTem:PRESet:USER:ALL
Same as User Preset but
affects all Modes in the current
Screen.
Preset
Dropdown
*RST
*RST
Same as Mode Preset - and in
addition always sets
Single/Cont to Single
Not available
from front
panel
Input/Output
Preset
:SYSTem:DEFault INPut
Affects all Input/Output
variables
Input/Output
menu, Preset
dropdown,
and System
Menu,
Restore
Defaults
Full Mode
Preset
:SYSTem:PRESet:FULL
Same as doing Mode Preset,
Restore Mode Defaults and
Preset
Dropdown
Remote Language Compatibility Measurement Application Reference
2 User Interface
Preset
Type Of
Preset
SCPI Command
Scope of Preset
Front Panel
Access
Input/Output Preset.
Essentially a factory preset of
the current Mode.
Restore User
Interface
Defaults
:SYSTem:DEFault
UINTerface
Affects all variables in the
”User Interface” group
System
Menu,
Restore
Defaults and
User
Interface
tabs
Restore
Power On
Defaults
:SYSTem:DEFault PON
Affects all variables in the
”Power On” group
System
Menu:
Restore
Defaults and
Power On
tabs
Restore
Alignment
Defaults
:SYSTem:DEFault ALIGn
Affects all variables in the
”Alignments” group
System
Menu,
Restore
Defaults and
Alignments
tabs
Restore
Miscellaneous
Defaults
:SYSTem:DEFault MISC
Affects various variables not
reset by other commands
System
Menu,
Restore
Defaults
Restore All
Defaults
:SYSTem:DEFault [ALL]
Affects all variables
System
Menu,
Restore
Defaults
:SYSTem:PRESet:PERSistent
Remote Language Compatibility Measurement Application Reference
67
2 User Interface
Meas Bar
Meas Bar
The Meas Bar is used to display annotation for the current measurement. There are
three primary uses for the Meas Bar:
– To show annotation for the most important parameters in the measurement so
you can see them at a glance
– To show the annotation that you are most likely to want to record in a screen
dump
– To provide quick access to settings.
The Meas Bar is made up of a number of annotation panels, each of which, when
pressed, opens up a dialog below it that contains controls for those settings.
For example, here is what the display looks like when you touch one of the regions of
the Meas Bar:
Touching anywhere off the hotspot panel or pressing any hardkey except Save or
Quick Save closes the hotspot panel.
In a hotspot panel, the control in black with the blue border is the active function.
Each panel may have its own default active function.
Settings that are colored amber are those that you need to be particularly aware of;
for example, if Alignments are off, this is shown in amber, so you will know that you
may not be meeting spec. Similarly, if DC coupling is on, this is shown amber, to alert
you to take care about the input voltage.
68
Remote Language Compatibility Measurement Application Reference
2 User Interface
Meas Bar
You can turn the Meas Bar on and off with a switch on the Annotation tab of the
Display menu.
You can turn the Meas Bar on and off with a switch on the Annotation tab of the
Display menu.
Trace Detector Settings Panel
In the Swept SA and some other measurements, there is a special panel
summarizing the settings for the traces in the measurement:
There is one column for each trace. The rows are as follows:
– The top row shows the Trace Number, in the trace color.
– The second row shows the Trace Type for each trace (W=Clear/Write, A=Trace
Average, M=Max Hold, m=Min Hold); this letter is in white if the trace is Active, in
gray if the trace is inactive; there is a bar through the letter if the trace is not
being displayed
– The third row shows the detector for each trace (N=Normal, S=Sample,
A=Average, P=peak, p=negative peak, Q=Quasi Peak, E=EMI Average, R=RMS
Average, f=math function)
In the example above, trace 1 is active, visible, and in Average using the Sample
detector, the other traces are inactive, blanked and in Clear/Write using the
Normal detector.
Remote Language Compatibility Measurement Application Reference
69
2 User Interface
Measurement Display
Measurement Display
The Measurement Display contains one or more data windows displaying the result
of the current measurement. These may be graphical or textual windows.
Each window in the Measurement display contains a Window Title, Measurement
Data, and graphical windows also may contain Annotation Hotspots.
The selected window in the Measurement Display is indicated by a blue border.
Window-dependent controls in the menu panel always refer to the selected window.
Window Title
The Window Title appears in the upper left hand corner of the window, and includes
a title describing the measurement data currently being displayed in the window.
The title may also contain additional information about the data in the window, for
example in the LTE measurement supplication, the component carrier being
displayed in the window will be indicated (e.g., “CC0”).
Measurements that support User Views (see "View Editor" on page 89) also display
the Window Number in the Window Title, to enable window addressing from SCPI.
The number is the number that will be used in the SCPI command to address that
window, for example, in the WCDMA Mod Accuracy measurement, Code Domain
Power is assigned window number 6, so you address it with the following SCPI
command:
DISP:RHO:WIND6:TRAC:Y:RLEV 0.0
70
Remote Language Compatibility Measurement Application Reference
2 User Interface
Measurement Display
Note the arrow pointing down on the right side of the Window Title. This indicates
that touching the Window Title will display a dropdown, which enables you to select
the Measurement Data to be displayed in the window.
For example, if we wish to assign the results of the upper window in the display
below to the Marker Table, we would touch the window title and then the “Data”
control that is revealed, as shown below:
And then select Marker Table, yielding the result below:
Remote Language Compatibility Measurement Application Reference
71
2 User Interface
Measurement Display
Note also that the Window Data dropdown can be a cascaded list, if the number of
available results requires categorization to hold them all, as shown below:
Note also that the Window Data dropdown sometimes includes controls for further
configuring the window, for example, in LTE choosing the desired Component Carrier
and Data format.
72
Remote Language Compatibility Measurement Application Reference
2 User Interface
Measurement Display
Touching a window’s title dropdown also selects the window.
Measurement Data
The Measurement Data region shows graphical or textual data for the Data selected
in the Window Title Data control. Below you can see examples of both graphical and
textual windows in a four-window display.
There are many gestures that you can use to interact with a measurement display
window:
Swipe
There are several swipe actions, as listed below.
One of the most important actions is swiping a spectrum window to the left or right,
or up or down, to adjust the frequency and level of the spectrum, as shown below.
Remote Language Compatibility Measurement Application Reference
73
2 User Interface
Measurement Display
Swipe actions are summarized in the table below. Not all of these may be
available, depending on the measurement.
Object
Action
Spectrum Trace
Left/Right
Drag trace (change Center Frequency)
Spectrum Trace
up/down
Drag trace (change Ref Level)
Marker Left/Right
Drag marker along trace
Fixed Marker
Left/Right/Up/Down
Drag marker in space
Scrollable area
Scroll vertically or horizontally. Scrollable areas include the Menu Panel (if
overfull), tables and lists. A scrollable area is indicated by a vertical or
horizontal translucent white bar, which can also be dragged by a mouse.
When scrolling a table:
– Row headers remain in place when the table is scrolled horizontally, and
scroll with the table when the table is scrolled vertically
– Column headers remain in place when the table is scrolled vertically, and
scroll with the table when the table is scrolled horizontally
Toggle control
Toggle in that direction
Pinch
You can also pinch in or out either horizontally or vertically to zoom in the x-axis or
y-axis dimension. For example, a pinch horizontally lets you adjust the Span of the
Spectrum window. Also, pinching on the wings of a Band Power or other Band
Function allows you to widen or narrow that Band Function.
74
Remote Language Compatibility Measurement Application Reference
2 User Interface
Measurement Display
Pinching may sometimes be easier if you use the index finger of each hand, rather
than pinching with one hand.
Touch-and-Hold
You can also touch-and-hold the display, that is, touch it and hold your finger on
the display. A circle is drawn, and when the drawing completes, a right-click
gesture is performed that depends on the screen feature touched, as listed in the
table below.
Right Click
on a Trace
Peak Search, Trace Type (Clear/Write, Trace Average, Max Hold, Min Hold), Trace
View/Blank (Active, View, Blank, Background). Not all of these may be available,
depending on the measurement.
Right Click
on a Marker
Marker Mode (Normal. Delta, Fixed, Off), Peak Search, Next Peak, Next Pk Right,
Next Pk Left). Not all of these may be available, depending on the measurement.
Right Click
on the
Background
Lets you select Help.
Right Click
on a Menu
Panel control
Lets you add or remove that control from the User Menu or get Help on that control.
Tap
Tapping an object causes the actions defined in the table below:
Object
Action
Marker
Select
Marker (repeated taps
Cycle through stacked markers
Remote Language Compatibility Measurement Application Reference
75
2 User Interface
Measurement Display
Object
Action
on stacked)
Trace
Select. In addition if Marker is the active function, move the selected
marker to the point where you tapped.
Trace (repeated taps
on stacked)
Cycle through stacked traces
Window
Select if unselected
Screen
Select if unselected
Double Tap
Double-tapping an object causes the actions defined in the table below:
Object
Action
Window
Zoom/Unzoom
Annotation Hotspot
You can tap on a graticule annotation to modify one of the fields in that annotation. In
the example below, clicking on the region containing Center Freq and Res BW
displays a menu panel with just those settings on it.
Touching anywhere away from the hotspot panel, or pressing any hardkey (except
Save or Quick Save), closes the hotspot panel.
Annotation that cannot currently be adjusted is not grayed out on the display, but
the control in the hotspot that drops down or pops up is grayed out.
In a hotspot panel, the control in black with the blue border is the active function.
Each panel may have its own default active function.
76
Remote Language Compatibility Measurement Application Reference
2 User Interface
Control Bar
Control Bar
The Control Bar contains controls and readouts that let you control instrument
functions independent of the current measurement.
Tap a region or label below for more information on that function.
Windows
Pressing the Windows button in the "Control Bar" on page 77 has the same effect as
pressing the Windows icon in the Windows taskbar. It displays the Windows taskbar
and Start Menu, which allows you to launch Windows programs and access features
such as the Control Panel.
Undo-Redo
The Undo button in the "Control Bar" on page 77,
and the Undo front panel key,
are used to undo the most recently executed function.
If you Undo a function, and then decide you should not have done so, you can use
the Redo button in the "Control Bar" on page 77
to put it back the way it was. The Redo function may also be executed by pressing
Ctrl+Undo (holding the Ctrl key down while pressing the Undo font panel key).
Undo allows you to restore a setting, which you had previously set, to its value
before you changed it. When you press the Undo button or front panel key, the last
setting you changed is “undone”, that is, its previous setting is restored. You are
notified of this fact with an advisory pop up message; for example, if the Center
Remote Language Compatibility Measurement Application Reference
77
2 User Interface
Control Bar
Frequency had been 300 MHz, and you changed it to 1 GHz and then pressed Undo,
the message would show:
UNDO: Center Freq 1 GHz -> 300 MHz
The instrument can store 5 levels of action for Undo.
Actions that Cannot be Undone
There are some actions that cannot be undone, because these clear the
Undo/Redo stack:
– Restore Mode Defaults clears the stack for that Mode in that Screen
– Sending SCPI commands clears the stack for that Mode in that Screen
– Loading a state file (including User Preset) clears the stack for that Mode in that
Screen
– Deleting a Screen clears all the stacks in that screen
– Changing Views
Undo/Redo works within the context of a Mode. Each Mode in each Screen keeps its
own record. Settings in the Control Panel or System Settings menus cannot be
undone.
There are several actions that may change many parameters. Among these are Auto
Tune and Adjust Atten for Min Clipping. After executing such a function, Undo sets all
parameters back to their values before the function was selected. Auto Tune
appears to be a single action, even though the instrument executes it in several
steps.
Redo reverses the effect of the last Undo action, assuming that no other settings
have been changed since the last Undo. Changing a setting after an Undo clears
memory of all settings after that Undo, that is, it clears the Redo stack.
Neither Undo nor Redo perform any navigation, and have no effect on which menu
panel is displayed or which function is active.
File Functions
The File Functions popup contains controls for executing Save, Recall, File and Print
operations. You display the File Functions popup by tapping the File Functions icon in
the "Control Bar" on page 77.
For more information on a control, tap an icon in the image below.
78
Remote Language Compatibility Measurement Application Reference
2 User Interface
Control Bar
Tapping this folder icon displays the File Functions popup
File Explorer
Pressing the File Explorer button in the "File Functions" on page 78 dialog opens the
Windows File Explorer, which allows you to perform operating system file functions
such as Move, Copy and Delete.
File Explorer also allows you to map network drives to drive letters on your PC or
intranet, in order to more easily save screen images, states and other data, and load
them back into the instrument.
Help
Pressing the Help button in the "Control Bar" on page 77, the Help front panel key,
or F1 if you have a PC keyboard connected, opens the context-sensitive Help system
and allows you to get Help on the current menu panel. The Help button appears in
the "Control Bar" on page 77 and also in the banner of full-screen dialogs.
You can also use the Help window's Table of Contents to navigate to Help for any
function in the instrument.
In addition, if you touch and hold a specific control, one of the choices is “Help on this
setting”.
The Help system appears in full screen mode, with the Contents pane on the left and
the User Documentation pane on the right. The small pullout tab between the
Contents pane and the User Documentation pane enables you to hide or view the
Contents pane.
Help Toolbar
The buttons in the red toolbar at the top of the Help Document pane provide the
Remote Language Compatibility Measurement Application Reference
79
2 User Interface
Control Bar
following functions:
Button
Name
Function
Print
Opens a printer setup dialog that enables you to print the currently
displayed topic.
Expand all
Collapse all
Expands or closes all drop-down text sections in the displayed
Document pane.
Change Font
Size
Enables you to select one of 5 sizes for the text of the Help topics.
The default setting is Medium.
Go Back
Go back to the previous topic in the navigation history.
Go Forward
Go forward to the next topic in the navigation history.
Previous Topic
in Contents
Go to the previous topic in the Help Contents.
Next Topic in
Contents
Go to the next topic in the Help Contents.
Close Help
This control provides an alternative way to close Help. You can also
use the front-panel "Cancel" on page 102 key.
The Help system has the following features:
Search Option
The Help Search utility is located above the red toolbar in the upper right corner of
the Help window:
Enter the desired search topic and press the magnifying glass icon.
If you want to find a specific combination of words, you can enter the search
keywords within quotation marks (for example, "User Preset").
Context-Sensitivity
To view a Help topic on a specific panel control, touch and hold the control until the
menu shown below appears:
80
Remote Language Compatibility Measurement Application Reference
2 User Interface
Control Bar
Tap "Help on this setting" to display the Help content for that control.
Help Contents Tree
The listing in the Contents pane of the Help Window starts with topics on the User
Interface, then Measurement Modes, Measurements within the Modes and
functions that support the measurements.
Those sections are followed by common topics such as System settings, Save and
Recall, the User menu, and Programming information.
Tap a closed red book icon to expand the tree for that section. Tap an open red
book icon to collapse the tree for that section.
Status and Message System
The status and error messaging system in the X-Series Multi-touch UI is capable of
reporting events and conditions in a consistent fashion, as well as logging and
reporting event history.
The Status System provides the following services to users:
– Indication of events when they occur
– Display of all open conditions with no action required by the user.
– Display on demand of a list of all open conditions
– All open conditions queryable via SCPI (one at a time is acceptable but all with a
single query is a future want)
– Indication that a condition came and went (since this might have happened while
you were not looking)
– Display on demand of the front panel event history
– Display on demand of the SCPI event history
– Flagging of events as info, warning or error
– Flagging of conditions as warning or error
– ID Number associated with all events and warnings for easy lookup by front
panel user and easy ID remotely
The Status Panel appears at the bottom of the display and contains three fields:
Remote Language Compatibility Measurement Application Reference
81
2 User Interface
Control Bar
The message balloon appears on the left side of the Status Panel and lets you know
when there is an unread message in the queue as shown above. Pressing the
Message Balloon opens up the Show Status dialog with the Messages tab selected.
The message balloon has a gray outline and no fill if there are no unread messages;
it has a gray fill and a white outline and displays a white ellipsis in the middle if there
are unread messages.
Touching the Message Balloon opens up the Show Status dialog with the History tab
selected. Touching anywhere else on the Status Bar opens up the Show Status
dialog with the Current Conditions tab selected.
The Condition Indicator appears to the right of the Message Balloon and shows the
current number of open conditions, as below:
The triangle is unfilled if no there are no open conditions, yellow if all open conditions
are warnings, and red if at least one open condition is an error. The number
displayed is the total number of open conditions.
Pressing the Condition Indicator opens up the Show Status dialog with the Current
Conditions tab selected.
The Condition Message appears to the right of the Condition Indicator:
Warning condition messages display in yellow, error condition messages display in
red.
If there is more than 1 open condition, the Condition Message cycles through the
display of all of the open conditions, one at a time. Each message is displayed for 2
seconds, then the next for 2 seconds, and so on.
Pressing the Condition Message opens up the Show Status dialog with the Current
Conditions tab selected.
Events
An event is an occurrence of zero duration. Events generate messages which are
displayed in the center of the display for a period of time and then fade away.
Events are broken down into three categories: advisories, warnings, and errors.
Advisory events
82
Remote Language Compatibility Measurement Application Reference
2 User Interface
Control Bar
An advisory event (see picture above) is simply a message to let the front panel user
know something useful – for example “File saved successfully” or “Single Sweep
on.” Advisories are reported with a blue circle with an “I” in it, do not have an ID
number and are not reported to SCPI.
Warning events
Warning event messages are intended to let a user know about a potentially
unexpected condition that may influence the results of the measurement, for
example, if a value is clipped to a different value than that requested. Event
warnings are reported with a yellow triangle with a “!” in it, have an associated
number and go into both the front panel queue (seen under Show Status, Messages)
and into the SCPI queue for the interface that stimulated the event. A typical
warning event is:
Error events
An error event occurs when a requested operation is rejected. Generally this means
no change is made to the instrument settings. An example might be “Undefined
header” or “Peak not found.” Another type of error event might occur when an
operation was accepted, but failed to complete successfully; for example “Disc full”
when attempting to store data. Event errors are reported with a red circle with an
“X” in it, have an associated number and go into both the front panel queue and into
the SCPI queue for the interface that stimulated the event. A typical error event is:
Conditions
A condition is an occurrence of finite duration, that is, it has a start and an end.
Conditions are states of the analyzer characterized by some combination of settings
or some kind of failure that the user needs to be told about while it is happening, but
then can stop being told once it goes away.
Remote Language Compatibility Measurement Application Reference
83
2 User Interface
Control Bar
A condition has a start event and an end event. The start event and end event have
numbers and go into the front panel queue. Condition errors also go into the SCPI
queue, but condition warnings do not.
Conditions are broken down into two categories: warnings and errors.
Warning conditions
A condition is a warning condition if it is a situation where the instrument can make
measurements, but may not be making valid measurements under these conditions.
For example, “Meas Uncal” indicates that you have chosen a sweep time so fast that
the analyzer may not meet spec. Warning conditions send messages to the front
panel but not to SCPI, but they may set status bits in the SCPI Status tree.
The reason that condition warnings are not sent to SCPI is because of the fact that
Meas Uncal is a frequently encountered warning and X-Series customers
complained that their SCPI queues were filling up with Meas Uncal warnings. After
the system was changed so that warnings do not report to SCPI these customers
were happy and since then no one has complained that warning conditions are not
seen by SCPI.
Error conditions
A condition is an error condition if the analyzer cannot make valid measurements
while it is present. Examples of error conditions are “LO Unlocked” or “Alignment
required”. Error conditions report to the front panel and to all SCPI queues.
Status Dialog
The Status dialog appears whenever the Condition Panel or Message Balloon are
touched. It shows all of the open conditions, the message history, and allows you to
configure the messaging system. The Show Status dialog is a full screen dialog.
If the display fills up, scrolling is enabled just as in other X-Series Multi-touch UI
displays.
The Show Status display automatically refreshes as new messages and conditions
occur.
Command
:SYSTem:ERRor[:NEXT]?
Example
:SYST:ERR?
Notes
The return string has the format:
“<Error Number>,<Error>”
Where <Error Number> and <Error> are those shown on the Show Errors screen.
Backwards Compatibility
In some legacy analyzers, the Repeat field shows the number of times the message
has repeated since the last time the error queue was cleared. In the X-Series, the
Repeat field shows the number of times the error has repeated since the last
84
Remote Language Compatibility Measurement Application Reference
2 User Interface
Control Bar
intervening error. So the count may very well be different than in the past even for
identical signal conditions
Unlike previous analyzers, in the X-Series all errors are reported through the
Message or Status lines and are logged to the event queue. They never appear as
text in the graticule area (as they sometimes do in previous analyzers) and they are
never displayed in the settings panel at the top of the screen (as they sometimes do,
by changing color, in previous analyzers).
As a consequence of the above, the user can only see one status condition (the most
recently generated) without looking at the queue. In the past, at least in the
Spectrum Analyzer, multiple status conditions might display on the right side of the
graticule.
In general, there is no backwards compatibility specified or guaranteed between the
error numbers in the X-Series and those of earlier products. Error, event, and status
processing code in customers’ software will probably need to be rewritten to work
with X-Series.
In the legacy analyzers, some conditions report as errors and others simply turn on
status bits. Conditions that report as errors often report over and over as long as the
condition exists. In the X-series, all conditions report as start and stop events.
Consequently, software that repeatedly queries for a condition error until it stops
reporting will have to be rewritten for the X-series.
History
History brings up a screen displaying the front panel message queue in
chronological order, with the newest event at the top. Remember that the front
panel queue contains all of the events generated by front panel actions as well as
error events from all of the SCPI queues. A typical History appears below:
Remote Language Compatibility Measurement Application Reference
85
2 User Interface
Control Bar
The fields on the History display are:
– Type - Displays the icon identifying the event or condition as an error or warning.
– ID - Displays the error number.
– Message - Displays the message text.
– Repeat (RPT) - This field shows the number of consecutive instances of the
event, uninterrupted by other events. In other words, if an event occurs 5 times
with no other intervening event, the value of repeat will be 5.
If the value of Repeat is 1 the field does not display. If the value of Repeat is >1,
the time and date shown are those of the most recent occurrence. If the value of
repeat reaches 999,999 it stops there. The Repeat field can run itno some pretty
large numbers when apps (like the GSM app) report things like “GSM sync burst
not found” as events rather than conditions, which is actually fairly common.
Note that the repeat count is unavailable over SCPI.
– Time - Shows the most recent time (including the date) at which the event
occurred. Time is displayed to the second.
At the bottom of the screen is a Clear Message Queue button. This button clears all
errors in all error queues.
Note the following:
– Clear Error Queue does not affect the current status conditions.
– Mode Preset does not clear the error queue.
– Restore System Defaults (Super Preset) will clear all error queues.
– *CLS only clears the queue if it is sent remotely and *RST does not affect any
error queue.
– Switching modes does not affect any error queues.
Current Conditions
This display shows all of the open conditions in the instrument. An open condition is a
condition error or warning for which a start (detected) event has occurred but for
which no corresponding stop (cleared) event has occurred.
The fields on the Current Conditions display are:
– Type - Displays the icon identifying the event or condition as an error or warning
or informational.
– ID - Displays the error number.
– Message - Displays the message text.
86
Remote Language Compatibility Measurement Application Reference
2 User Interface
Control Bar
– Time - Shows the most recent time (including the date) at which the event
occurred. Time is displayed to the second.
Touching a condition message expands the display of that message. Touching again
collapses it.
Clear Message Queue
This clears all messages in all queues.
Note the following:
– Clear Message Queue does not affect the current status conditions.
– Mode Preset does not clear the message queue.
– Restore System Defaults will clear all message queues.
– *CLS only clears the queue if it is sent remotely and *RST does not affect any
message queue.
– Switching modes does not affect any message queues.
Block Diagram
When you press the Block Diagram button in the "Control Bar" on page 77, the
display changes to a stylized pictorial representation of the current internal
hardware setup and signal processing path. When you touch one of the blocks on
the Block Diagram, the corresponding menu panel opens.
When you press the Block Diagram button, the display changes to a stylized pictorial
representation of the current internal hardware setup and signal processing path.
When you touch one of the blocks on the Block Diagram, the corresponding menu
panel opens.
While in the Block Diagram display, the button is blue colored, as:
To exit the Block Diagram display, tap the button again.
Remote Language Compatibility Measurement Application Reference
87
2 User Interface
Control Bar
The Block Diagram display is not meant to be a completely accurate representation,
but one which can show differences as you change the hardware setup. For
example, here is the basic RF Block Diagram:
And here is the Block Diagram when External Mixing is selected:
And here is the Block Diagram when the I/Q inputs are selected:
88
Remote Language Compatibility Measurement Application Reference
2 User Interface
Control Bar
View Editor
This section describes the use of the View Editor, which allows you to:
– Add windows to and delete windows from the current measurement
– Resize and rearrange windows
– Create User Views (custom views)
To Open the View Editor
Pressing the View Editor button (shown above) in the "Control Bar" on page 77 at
the bottom right of the screen opens the View Editor.
While the View Editor is active, the button turns blue, as below.
To Close the View Editor
Tap the View Editor button again.
About User Views
A User View is any View that is not in the list of predefined Views. For example, the
Swept SA measurement comes with four predefined Views: Normal, Spectrogram,
Zone Span, and Trace Zoom.
User Views allow you to add, delete, change and rearrange the windows of a
predefined View, creating a new custom view.
Some measurements do not support User Views; these do not permit adding,
deleting or rearranging of windows, but they do permit resizing of windows. In
these measurements, you can open the View Editor, but the Add, Delete and Move
icons do not appear. You can still resize windows and, in some cases (for example,
Noise Figure), you can change window contents.
View Editor Window Add
You can add new windows to a predefined View. If you want to save the modified
view for future use, you need "Create a User View" on page 94 from the modified
view.
Select the view that you want to modify, using the "Mode Meas View dialog" on page
55.
Remote Language Compatibility Measurement Application Reference
89
2 User Interface
Control Bar
Open the "View Editor" on page 89. When the View Editor is active, additional
controls appear on the screen, as shown in the example below. The menu panel also
switches to the View menu.
As shown, each window displays two arrows containing + signs. Pressing either
arrow symbol adds a new window on the indicated side.
Pressing the right-pointing arrow in the lower left window of the screen above adds a
fifth window, as shown below.
90
Remote Language Compatibility Measurement Application Reference
2 User Interface
Control Bar
The number 5 is automatically assigned to the new window. This number, which is
displayed in the Window Title region, is used when sending SCPI commands to that
window.
Note that the View name "Basic" in the View menu now has an asterisk (*) added,
indicating that you are viewing a modified Basic View. The asterisk appears if you
add, delete or rearrange windows, but simply resizing a window does not display the
asterisk. When the asterisk is visible, you must save the modified View as a User
View before you leave the measurement, or it will be discarded.
You can specify which result you want to see in the new window by tapping its title
region.
A panel drops down, containing a Data control for specifying window results. Some
measurements, such as LTE-A , also provide controls on this dropdown for specifying
other window parameters, such as the Component Carrier and Data Format. Tap the
Data control to see a list of available results for the window. In some cases, as in
LTE-A, this will be a cascading list, due to the number of results available. Choose
the desired result and tap the OK button.
Note also that the Restore Layout to Default button is no longer grayed out. If you
press this button, it restores the Basic View to its default state. Restore Layout to
Default becomes available when you add, delete or rearrange windows and when
you resize them; otherwise it is grayed out.
You can add more windows by using the “+” arrow symbols. Note that the “+” arrow
symbols only appear if the current measurement has more windows available to
display. If you are already displaying all the measurement’s windows, the “+”
symbols disappear.
If you have an unsaved View and you change measurements via SCPI, the unsaved
View will be discarded.
You can save a modified view as a User View. See "Create a User View" on page 94.
View Editor Window Move Resize
If necessary, select the view that you want to modify, using the "Mode Meas View
dialog" on page 55. You can modify a Predefined View or a User View.
Open the "View Editor" on page 89.
To Resize a Window
When the View Editor is active, note the large, translucent white circles along the
edges of the draggable borders. These are the “resize handles”. You can resize
each window by dragging these handles.
Remote Language Compatibility Measurement Application Reference
91
2 User Interface
Control Bar
To Move a Window
Use the four-arrow icon in the center of each window to drag the whole window
around the screen.
The outline of the window appears as it is being dragged. When you start to drag a
window, target symbols appear in the other windows:
92
Remote Language Compatibility Measurement Application Reference
2 User Interface
Control Bar
If you drop a window on one of the targets, it swaps positions with the target
window. If you drag a window’s center into another window, green stripes appear
around the edges to show you where the window will snap to when released.
After you have moved or rearranged windows, you can save the modified view as a
User View. See "Create a User View" on page 94.
In either case, one or more of the remaining windows resize to occupy the space
formerly occupied by the window you were dragging.
View Editor Window Delete
If necessary, select the view that you want to modify, using the "Mode Meas View
dialog" on page 55. You can modify a Predefined View or a User View.
Open the "View Editor" on page 89. You can delete windows by:
Deleting a Single Window
When the View Editor is active, additional controls appear on the screen, including
a red circle containing an X at the top right of each window, as shown in the
example below. Tap the red circle in the window that you want to delete. (If the
View has only one window, the red circle is not visible.)
Restoring View Layout
You can also delete windows by pressing the Restore Layout to Default button in
the View menu. Pressing this button restores the View to its default state. Restore
Layout to Default is available when you add, delete, rearrange or resize windows;
otherwise it is grayed out.
Remote Language Compatibility Measurement Application Reference
93
2 User Interface
Control Bar
Create a User View
To create a User View, tap the View Editor icon
. This brings up a View Editor
screen and the menu panel switches to View menu. In the View Editor you will see
two "+" signs in each window.
Graphic
Press a plus sign to add a view to the right or below the current view.
Whenever you add or delete a window to or from a predefined View, or change what
is being displayed in a Predefined View’s window, the Predefined View is marked with
an asterisk (*), to show that it has been modified.
When you tap Done, the View is saved.
After saving the new User Views, the following menu changes occur:
– A User View region appears on the View menu panel above, with the new User
View called "My New View"
– The “Basic” view returns to its original, unedited state and its name no longer has
an asterisk suffix
– The Restore Layout to Default button in the View menu is grayed out
– The new User View also appears in the "Mode Meas View dialog" on page 55.
View Editor Delete User View
You can delete a User View by selecting that View and tapping Delete User View in
the View menu.
94
Remote Language Compatibility Measurement Application Reference
2 User Interface
Control Bar
View Editor Use Case
One common application for User Views is to create a View that allows the Spectrum
Analyzer to display both a Marker Table and a Peak Table at the same time.
To do this, simply add a Marker Table Window and a Peak Table window to the
Spectrum window of the Swept SA measurement. The result is shown below; note
that the new View has been named “Marker Table & Peak Table”:
There are legacy displays like Marker Table, Peak Table, Measure at Marker and
Gate View, which are not Views but special display modes. These are retained for
backwards compatibility, but they are turned on and off with switches and do not use
the View system. Turning on one of these switches does not create a modified View,
but merely adds the specified window to the current View; turning the switch back off
removes the window. While the switch is on, no View is shown as selected in the
View menu. These switches are grayed out if you are in a modified View or a User
View. Since only one of these switches can be on at a time, and because these
switches are turned off by a Preset, User Views offer a better way of adding windows
than using the switches.
Multiscreen
You can configure up to 16 different Screens at a time. Normally, you only see one
Screen, and the set of configured screens is shown across the top of the display as a
series of "Screen Tabs" on page 54. Touching any screen’s tab brings it to the
foreground, makes it the current Screen and starts it updating.
Multiscreen view lets you display all of the configured Screens at once.
Remote Language Compatibility Measurement Application Reference
95
2 User Interface
Control Bar
You can switch to Multiscreen View by pressing this button in the "Control Bar" on
page 77, at the bottom right of the screen:
While in Multiscreen View, the button changes from a black background to a blue
background:
To exit Multiscreen view, tap the button again.
In Multiscreen View, just as in Single Screen View, only one screen is active. Each
Screen contains one Mode, each Mode contains one Measurement, and each
Measurement contains a number of Windows arranged in Views. You can configure
multiple instances of the same Mode along with any combination of other Modes.
You switch Screens by tapping the Screen Tab you want, or when in Multiscreen
View, you can tap the Screen itself. When you switch Screens, the current Screen’s
state and measurement results are preserved, the new Screen’s previous state and
data are loaded, and the new Screen starts running its Mode.
In Multiscreen View:
– When possible, each Screen is contained within an equal-size box. As a
general guideline, “tall” is better than “wide” when there is a choice, as it
allows measurement data to be displayed with a bigger Y-Axis, which is best
for most of our measurements.
– When it is not possible to have equal sized screens, one or more screen will
be bigger than the rest.
– Each Screen has a tab that contains the name of the Mode and
Measurement in the box and a number associated with the instance of that
Mode. The user can enter a custom title that replaces the Mode name.
– The Meas Bar does not display
– There is always one and only one selected Screen. It is indicated by a
Selected Blue tab. Only the selected Screen is actually running a
measurement and updating its display.
– The selected window in the selected screen is the context for the current
menus. It is the only window with a blue border.
– You select a screen by touching it or touching its tab.
96
Remote Language Compatibility Measurement Application Reference
2 User Interface
Control Bar
– As you go from screen to screen, each screen remembers the last hardkey
that was active in that screen and restores it as the active menu.
In Multiscreen View, as in Single Screen View, tapping the blue tab or pressing the
Mode/Meas front panel key opens the "Mode Meas View dialog" on page 55, which
allows you to change the Mode (or Measurement or View) being displayed in that
Screen.
Command
INSTrument:SCReen:MULTiple[:STATe] OFF|ON|0|1
INSTrument:SCReen:MULTiple?
Example
INST:SCR:MULT ON
Preset
OFF
Notes
If only one screen is configured, attempting to set Multiscreen ON generates the error “–
221.9911,Settings conflict; Multi-Screen requires >1 screen”
Select Screen
You can select a screen by touching its tab or, in "Multiscreen" on page 95 mode,
touching the screen itself. Selecting the Screen activates the screen and suspends
the previously selected screen (if any).
Command
:INSTrument:SCReen:SELect <screen name>
:INSTrument:SCReen:SELect?
Example
INST:SCR:SEL “Baseband”
Preset
Returns the name of the active screen
Notes
If the <screen name> is specified but not found in the list of Screens, the error message “–
224.1000,Illegal parameter value; Screen Name not found” is generated.
Full Screen
The Full Screen button is in the "Control Bar" on page 77, at the lower right corner of
the display.
When Full Screen is pressed, the measurement window expands horizontally over
the entire instrument display. The screen graticule area expands to fill the available
display area.
It turns off the display of the menu panel, however the controls that drop down from
the Meas Bar and on-screen annotation are still available, and you can still drag the
trace and markers and perform a pich zoom, so you can still operate the instrument.
Pressing Full Screen again while Full Screen is in effect cancels Full Screen.
You can get even more screen area for your data display by turning off the Meas Bar
(using the Annotation tab of the Display menu).
Remote Language Compatibility Measurement Application Reference
97
2 User Interface
Control Bar
Full Screen is canceled by the Preset key.
Command
:DISPlay:FSCReen[:STATe] OFF|ON|0|1
:DISPlay:FSCReen[:STATe]?
Preset
Unaffected by Preset but set to Off by Restore Misc Defaults or shutdown and restart
State Saved
Not saved in instrument state.
SCPI
Backwards Compatibility
:DISPlay:MENU[:STATe] OFF|ON|0|1
This emulates ESA full screen functionality, which is the same as the FSCReen
command in PSA except that the sense of on/off is reversed (that is, OFF means the
menus are OFF, so Fullscreen is ON) and the default is ON (meaning Fullscreen is
OFF).
In ESA/PSA, Full Screen was turned on with a softkey, so pressing any other key
turned Full Screen off. In the X-Series, because a hardkey is provided to turn this
function on and off, pressing any other key no longer turns off Full Screen
98
Remote Language Compatibility Measurement Application Reference
2 User Interface
Menu Panel
Menu Panel
The menu panel is the main focus of the X-Series Multitouch user interface. The
controls include active functions, dropdowns, action buttons, radio buttons and
toggles.
The menu panel normally appears on the right side of the display, and consists of a
rectangular panel with multiple “sub-panels”. Each sub-panel is accessed by a tab
on the right.
Accessing Menus Using Front-Panel Keys
Press one of the twelve "measurement hardkeys" on the instrument front panel to
open the corresponding menu in the menu panel. The measurement hardkeys are
all in the outlined "Measurement" group on the front panel. The keys are: AMPTD,
BW, Display, FREQ, Input/Output, Marker, MEAS SETUP, Peak Search, SWEEP,
Trace, Trigger, User Menu.
With a menu open, tap a tab to access the controls in its sub-panel. Whenever you
press the front panel key associated with a menu, the default (top) tab is selected.
If the number of controls on a panel exceeds the height of the panel, scrolling is
enabled, which is indicated by a white bar on the left that fades away after a few
seconds. You can swipe up or down to scroll the panel, or you can grab the white
bar with a mouse.
Remote Language Compatibility Measurement Application Reference
99
2 User Interface
Menu Panel
Accessing Menus Without Using Front-Panel Keys
You can access the menu panels without using the front panel keys, as you would
need to do if you were operating the instrument using Remote Desktop. Touch or
click on the menu title, as shown below. A dropdown containing the twelve
measurement hardkeys appears. Selecting a hardkey from the dropdown displays
the corresponding menu, and the dropdown disappears.
Entering Numeric Values
Many controls on the menu panel allow you to enter numeric values. These are
called “active functions.” An active function control displays a number and a suffix,
as in the example below:
An active function is “active” if the numeric value is surrounded by a black
background with a blue border, as shown below. In this state, it is ready to receive
numeric input from the number pad on the front panel, the knob, or the step keys.
100
Remote Language Compatibility Measurement Application Reference
2 User Interface
Menu Panel
When an active function is in the active state, you can start typing or pressing the
number keys on the front panel, which causes the Numeric Entry Panel to appear,
as shown below. The Numeric Entry Panel displays the typed value, and the
terminators to complete the entry.
In the example above, pressing the "2" key on the instrument's front panel caused
the Numeric Entry Panel to appear. Type in as many digits as required, then touch
one of the unit terminator buttons in the Numeric Entry Panel to complete the
entry. In this case, "GHz" was selected.
The Numeric Entry Panel disappears, and, in the example, the active function value
becomes 2 GHz.
You can display the Numeric Entry Panel by touching any active function control
while it is active, but the panel appears automatically as soon as you start typing.
You can also adjust a value without displaying the Numeric Entry panel by turning
the knob or using the step keys while an active function is active. If you turn the
knob or use the step keys while the Numeric Entry Panel is displayed, it disappears,
allowing you to see the entire screen while you are making the adjustment.
Remote Language Compatibility Measurement Application Reference
101
2 User Interface
Cancel
Cancel
This front-panel key has the same functions as the Windows Esc (Escape) key. It
does the following:
– Cancels dialogs
– Cancels active functions (unless there is an entry in progress, in which case it
cancels that and reverts to the previous value)
– Resets input overloads
– Aborts print operations
– Cancels certain other operations (such as alignments)
– Returns you to Local Control (if in Remote)
– If the backlight is off, turns on the backlight, and does nothing else
Most of this functionality is the same as earlier X-Series models, and similar to ESA
and PSA operation.
102
Remote Language Compatibility Measurement Application Reference
2 User Interface
Onscreen Keyboard
Onscreen Keyboard
This key turns the onscreen alpha keyboard (OSK) on and off.
There are two onscreen keyboard types:
– The Multitouch OSK, which pops up automatically while using the analyzer
application, whenever a text field becomes the active function
– The Windows OSK, which you must open manually when a text field must be
entered while interacting with Windows or other apps
Remote Language Compatibility Measurement Application Reference
103
2 User Interface
Touch On/Off
Touch On/Off
This front-panel key turns the display touch functionality on and off. If Off, you can
turn it back on using the front panel Touch On/Off key. When the touch functionality
is off, you can still use a mouse as a pointer.
When toggled, a message box temporarily appears midscreen that confirms
“Touchscreen On” or “Touchscreen Off”.
Preset
Always starts up “ON”.
Unaffected by a Preset, but is turned on by "Restore User Interface Defaults" or "Restore System
Defaults->All".
State Saved
104
Not saved in state, not affected by preset, not Power On Persistent (does not survive shutdown
and restart).
Remote Language Compatibility Measurement Application Reference
2 User Interface
Tab
Tab
This front-panel key has the same function as the Tab key on a PC keyboard.
You can use this key to display the Windows Taskbar, as follows:
1. Alt-Tab to the Desktop
2. Touch the desktop
3. Touch TAB
4. The Taskbar appears
Remote Language Compatibility Measurement Application Reference
105
3 RLC Mode & Swept SA Measurement
3 RLC Mode & Swept SA Measurement
To select the N9061C Measurement Application and its only measurement
(RLC Swept SA) using the instrument's front-panel interface, use the "Mode Meas
View dialog" on page 55.
To select the N9061C Measurement Application, and its measurement,
programmatically, use either of the following SCPI commands:
– :INSTrument[:SELect] RLC
For more details of this command, see "Mode" on page 55.
– :INSTrument:NSELect 266
For more details of this command, see "Mode" on page 55.
N9061C has only one measurement, so, when you send either of the above
commands, the RLC Swept SA Measurement will automatically be selected.
Remote Language Compatibility Measurement Application Reference
106
3 RLC Mode & Swept SA Measurement
SCPI Support
SCPI Support
N9061C supports only a limited subset of SCPI commands. The full set of supported
commands is provided in "List of Supported SCPI Commands" on page 670.
The topics included in this chapter may apply to multiple instrument modes and
measurements. For this reason, the topic content may include SCPI command
definitions that are not supported by N9061C.
107
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Functions in this Chapter
Functions in this Chapter
This chapter provides complete details of the instrument's front-panel measurement
functions.
– "RLC Swept SA Views" on page 146
– "Amplitude" on page 110
– "BW" on page 134
– "Display" on page 143
– "Frequency " on page 148
– "Input/Output" on page 163
– "Marker" on page 201
– "Meas Setup" on page 250
– "Sweep" on page 316
– "Trace" on page 331
– "Trigger" on page 363
Remote Language Compatibility Measurement Application Reference
108
3 RLC Mode & Swept SA Measurement
RLC Swept SA Views
RLC Swept SA Views
The RLC Swept SA measurement has only one view ("Normal" on page 147).
Some views are multiple-window views. When in a multiple window view, you select
a window by touching it. The menu controls may sometimes change depending on
which window is selected.
Whenever the view changes, the default menu is Frequency, unless otherwise
specified in the view description.
For details of the User View-related controls in this menu, see the descriptions under
the "View Editor" on page 89.
SCPI
Command
Not available in N9061C
Dependencies
All views except NORMal require option EDP to be licensed. If the SCPI is sent to
select any other view and EDP is not licensed, an error “Option not available” is
generated.
Preset
NORMal
State Saved
Saved in instrument state
Normal
Single window view of the frequency domain or zero span. This is the classic SA view.
This is also the view into which the instrument switches whenever you do anything
that causes the frequency limits to change, for example:
– If you switch inputs (for example, if you switch from the RF Input to External
Mixing)
– If, while in External Mixing, you edit the Harmonic Table
– If, while in External Mixing, the Mixer Preset changes (for example, if you change
from A-band to V-band etc)
For N9061C, this is the only available view, and it has only one window: "Spectrum"
on page 109.
Spectrum
Window Number: 1
The Spectrum window is the fundamental window used in the Swept SA
measurement and several other measurements. It displays amplitude versus
frequency information (or, in Zero Span, amplitude versus time). Unless otherwise
noted, behaviors described in the Swept SA measurement description are assumed
to be behaviors of the Spectrum window.
The Spectrum window always displays and cannot be deleted.
109
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Amplitude
Amplitude
The Amplitude front-panel key activates the Amplitude menu and selects Reference
Level or Reference Value (depending on the measurement) as the active function.
Some features in the Amplitude menu apply to multiple measurements. Some other
features apply only to specific measurements and their controls are blanked or
grayed out in measurements that are not supported.
Y Scale Tab
Reference level
The Reference Level specifies the amplitude represented by the topmost graticule
line.
Changing the reference level does not restart a measurement, because it is a
display function only; instead it vertically ‘pans’ all displayed traces and markers to
the new value. If a change to the reference level changes the attenuation value (e.g.
through an auto coupling), then the measurement will be restarted.
Command
:DISPlay:WINDow[1]:TRACe:Y[:SCALe]:RLEVel <real>
:DISPlay:WINDow[1]:TRACe:Y[:SCALe]:RLEVel?
Example
DISP:WIND:TRAC:Y:RLEV 20 dBm
sets the reference level to 20 dBm, which displays in the current Y axis unit. For example,
if the Y axis unit is dBμV, then 126.99 dBμV will be displayed.
DISP:WIND:TRAC:Y:RLEV?
Preset
0 dBm
Min/Max
Min: -170 dBm + RefLevelOffset - ExtGain.
Max:+30 dBm + RL Offset – External Gain
This maximum value is determined by the maximum power that can be safely applied to
the input circuitry. The actual maximum value at any given time may be even less than
this, depending on other values including Mech Atten, Int Preamp Gain, Swept IF Gain,
FFT IF Gain, Max Mixer Level, and the total attenuation currently available.
Note that the maximum reference level is unaffected by the input choice of external
mixing.
State
Saved
Saved in instrument state.
Couplings
If you reduce the attenuation, the analyzer may have to lower the reference level
to keep it below its allowed maximum. This allowed maximum level is specified in
the “Max” row, along with other variables that affect it.
When you increase attenuation, the reference level does not change.
Backwards Compatibility Notes
Remote Language Compatibility Measurement Application Reference
110
3 RLC Mode & Swept SA Measurement
Amplitude
1. In PSA, there was a restriction on Ref Level Max which was that it could not
exceed 0 dBm when the preamp was on. This restriction does not apply to XSeries.
2. Ref Level – Ref Level is a display function, not a measurement control function,
so a change in the setting does not start a new sweep (unless attenuation
changes). This behavior differs from that of legacy analyzers.
Amplitude Representations
The following is an illustration of the reference level and Y Axis scales under various
conditions:
Scale/Div
Sets the units per vertical graticule division on the display. This function is only
available when Display Scale (Log) is selected and the vertical scale is power. When
Display Scale (Lin) is selected, Scale/Div is grayed out.
Command
:DISPlay:WINDow[1]:TRACe:Y[:SCALe]:PDIVision <rel_ampl>
:DISPlay:WINDow[1]:TRACe:Y[:SCALe]:PDIVision?
Example
DISP:WIND:TRAC:Y:PDIV 5 DB
Preset
10.00 dB / Div
Min/Max
0.10 dB/20 dB
State Saved
Saved in instrument state
Dependencies
Scale/Div is grayed out in linear Y scale. Sending the equivalent SCPI command
does change the Scale/Div, though it has no affect while in Lin.
Couplings
In measurements that support Auto Scaling, when the Auto Scaling is On, this
111
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Amplitude
value is automatically determined by the measurement result. When you set a
value manually, Auto Scaling automatically changes to Off.
Display Scale
Chooses a linear or logarithmic vertical scale for the display and for remote data
readout.
When Display Scale (Log) is selected, the vertical graticule divisions are scaled in
logarithmic units. The top line of the graticule is the Reference Level and uses the
scaling per division Scale/Div to assign values to the other locations on the
graticule.
When Display Scale (Lin) is selected, the vertical graticule divisions are linearly
scaled with the reference level value at the top of the display and zero volts at the
bottom. Each vertical division of the graticule represents one-tenth of the Reference
Level.
The Y Axis Unit used for each type of display is set by pressing Y Axis Unit. The
analyzer remembers separate Y Axis Unit settings for both Log and Lin.
:DISPlay:WINDow[1]:TRACe:Y[:SCALe]:SPACing LINear|LOGarithmic
Command
:DISPlay:WINDow[1]:TRACe:Y[:SCALe]:SPACing?
Example
DISP:WIND:TRAC:Y:SPAC LOG DISP:WIND:TRAC:Y:SPAC?
Preset
LOG
State Saved
Saved in instrument state.
Dependencies
If Normalize is on, Display Scale is forced to Log and is grayed out.
Couplings
Changing the Display Scale always sets the Y Axis unit to the last unit specified for
the current amplitude scale.
Y Axis Unit
Displays a dropdown menu that enable you to change the vertical (Y) axis amplitude
unit.
For measurements that support both Log and Lin scales, the analyzer retains the
entered Y Axis Unit separately for both Log and Lin amplitude Display Scales. For
example, if Display Scale has been set to Log, and you set Y Axis Unit to dBm,
pressing Display Scale (Log) sets the Y Axis Unit to dBm. If Display Scale has been
set to Lin and you set Y Axis Unit to V, pressing Display Scale (Lin) sets the Y Axis Unit
to V. Pressing Display Scale (Log) again sets the Y axis unit back to dBm.
Unit Examples
Unit
Examples
dBm
UNIT:POW
DBM
Notes
Remote Language Compatibility Measurement Application Reference
112
3 RLC Mode & Swept SA Measurement
Amplitude
Unit
Examples
Notes
dBmV
UNIT:POW
DBMV
dBmA
UNIT:POW
DBMA
W
UNIT:POW
W
V
UNIT:POW
V
A
UNIT:POW
A
Sets the amplitude unit for the selected amplitude scale (log/lin) to Ampere.
dBμV
UNIT:POW
DBUV
Sets the amplitude unit for the selected amplitude scale (log/lin) to dBmV.
dBμA
UNIT:POW
DBUA
The unit dBuA can also appear as an Antenna Unit. This will be used by
customers using current probes, because current probes are often supplied
with conversion tables that provide the transducer factors. When dBuA is
used as an Antenna Unit the normal conversion from power to amps for
dBuA (based on the analyzer input impedance) is not done, but instead the
conversion is based solely on the Correction that contains the transducer
factors. This is what distinguishes dBuA as a normal unit from dBuA as an
antenna unit. When querying the Y-Axis unit, you can query the Antenna
Unit to distinguish between regular dBuA and the dBuA antenna unit. If
:CORR:CSET:ANT? returns NOC (for No Conversion), you are using a normal
Y Axis dBuA. If it returns UA you are using an Antenna Unit dBuA.
dBpW
UNIT:POW
DBPW
Remote Interface
The settings of Y Axis Unit and Display Scale, affect how the data is read over the
remote interface. When using the remote interface no unit is returned, so you must
know what the Y axis unit is to interpret the results:
Example 1, set the following:
– Display Scale (Log)
– Y Axis Unit, dBm
– Scale/Div, 1 dB
– Ref Level, 10 dBm
This sets the top line to 10 dBm with each vertical division representing 1 dB. Thus, if
a point on trace 1 is on the fifth graticule line from the top, it represents 5 dBm and
will read out remotely as 5.
113
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Amplitude
Example 2, set the following:
– Display Scale (Lin)
– Y Axis Unit, Volts
– Ref Level, 100 mV (10 mV/div)
This sets the top line to 100 mV and the bottom line to 0 V, so each vertical division
represents 10 mV. Thus, if a point on trace 1 is on the fifth graticule line from the top,
it represents 50 mV and will read out remotely as 50.
The units of current (A, dBmA, dBuA) are calculated based on 50 ohms input impedance.
All four of the Antenna units (dBμA/m, dBμV/m, dBG, dBpT) are treated by the
instrument exactly as though they were dBuV. You must load an appropriate correction
factor using Amplitude Corrections for accurate and meaningful results.
If a SCPI command is sent to the analyzer that uses one of the Antenna units as a
terminator, the analyzer treats it as though DBUV had been sent as the terminator.
SCPI Command not available in N9061C.
Preset
dBm for log scale, V for linear. The true ‘preset’ value is dBm, since at preset the Y Display
Scale is set to logarithmic.
State
Saved
Saved in instrument state.
Notes
The Y axis unit has either logarithmic or linear characteristics. The set of units that is
logarithmic consists of dBm, dBmV, dBmA, dBμV, dBμA, dBμV/m, dBmA/m, dBpT,
and dBG. The set of units that are linear consists of V, W, and A. The chosen unit will
determine how the reference level and all the amplitude-related outputs like trace
data, marker data, etc. read out.
Dependencies
If an amplitude correction with an Antenna Unit other than None is applied and
enabled, then the Antenna Unit selection is forced and is the only Y Axis Unit
available. The specific Antenna Unit is shown in square brackets in the dropdown. All
other Y Axis Unit choices are grayed out.
If an amplitude correction with an Antenna Unit other than None is applied and
enabled, and you then turn off that correction or set Apply Corrections to No, the Y
Axis Unit that existed before the Antenna Unit was applied is restored.
Antenna Unit
When a Correction is turned on that uses an Antenna Unit, the Y Axis Unit changes to
that Antenna Unit. All of the selections in the Y-Axis Unit dropdown are then greyed
out, except the Antenna Unit selection. The unit being used is shown on this
selection in square brackets, and appears on the control followed by “(Antenna)”.
Example: the Antenna Unit in the Correction is dBpT
Remote Language Compatibility Measurement Application Reference
114
3 RLC Mode & Swept SA Measurement
Amplitude
The selection in the dropdown looks like this:
And on the control it looks like this:
The Antenna Units are:
Units
Example
dBμV/m
UNIT:POW DBUVM
dBμA
UNIT:POW DBUAM
dBpТ
UNIT:POW DBPT
dBG UNIT
:POW DBG
None
n/a
Reference Level Offset
Adds an offset value to the displayed reference level. The reference level is the
absolute amplitude represented by the top graticule line on the display.
Command
:DISPlay:WINDow[1]:TRACe:Y[:SCALe]:RLEVel:OFFSet <rel_ampl>
:DISPlay:WINDow[1]:TRACe:Y[:SCALe]:RLEVel:OFFSet?
Example
DISP:WIND:TRAC:Y:RLEV:OFFS 12.7 sets the Ref Level Offset to 12.7 dB. The only valid
suffix is dB. If no suffix is sent, dB will be assumed.
Preset
0 dBm
Min/Max
Min:The range for Ref Lvl Offset is variable. It is limited to values that keep the reference
level within the range of -327.6 dB to 327.6 dB.
Max:327.6 dB
State
Saved
Saved in instrument state.
Backwards Compatibility Notes
1. In pre-X-Series instruments, Ref Level Offset could not be adjusted by the knob
115
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Amplitude
or step keys. That is no longer the case.
2. In ESA and PSA, Ref Level Offset was applied to the data as it was acquired;
thus if the Offset changed the new offset was not applied until new trace data
was taken. In X-Series, the offset is applied as the data is displayed/queried, so
if you change the offset, it will change the data immediately.
More Information
Offsets are used when gain or loss occurs between a device under test and the
analyzer input. Thus, the signal level measured by the analyzer may be thought of
as the level at the input of an external amplitude conversion device. Entering an
offset does not affect the trace position or attenuation value, just the value of the
top line of the display and the values represented by the trace data. Thus, the
values of exported trace data, queried trace data, marker amplitudes, trace data
used in calculations such as N dB points, trace math, peak threshold, and so forth,
are all affected by Ref Level Offset.
Changing the offset causes the analyzer to immediately stop the current sweep
and prepare to begin a new sweep, but the data will not change until the trace data
updates, because the offset is applied to the data as it is taken. If a trace is
exported with a nonzero Ref Level Offset, the exported data will contain the trace
data with the offset applied.
The maximum reference level available is dependent on the reference level offset.
That is, Ref Level - Ref Level Offset must be in the range -170 to +30 dBm. For
example, the reference level value range can be initially set to values from -170
dBm to 30 dBm with no reference level offset. If the reference level is first set to -20
dBm, then the reference level offset can be set to values of -150 to +50 dB.
If the reference level offset is first set to -30 dB, then the reference level can be set
to values of -200 dBm to 0 dBm. In this case, the reference level is “clamped” at 0
dBm because the maximum limit of +30 dBm is reached with a reference level
setting of 0 dBm with an offset of -30 dB. If instead, the reference level offset is first
set to 30 dB, then the reference level can be set to values of -140 to +60 dBm.
Number of Divisions
Allow you to set the number of divisions vertically in the graticule. For example, set
this to 12 to allow 120 dB of dynamic range with a scale of 10 dB/division.
Command
:DISPlay:WINDow[1]:TRACe:Y[:SCALe]:NDIVision 6|8|10|12|16|20
:DISPlay:WINDow[1]:TRACe:Y[:SCALe]:NDIVision?
Example
DISP:WIND:TRAC:Y:NDIV 12
Preset
10
State Saved
Saved in instrument state.
Remote Language Compatibility Measurement Application Reference
116
3 RLC Mode & Swept SA Measurement
Amplitude
Attenuation Tab
There are two attenuator configurations in the X-Series. One is a dual attenuator
configuration consisting of a mechanical attenuator and an optional electronic
attenuator. The other configuration uses a single attenuator with combined
mechanical and electronic sections that controls all the attenuation functions.
Different models in the X-Series come with different configurations.
Most attenuation settings are the same for all measurements. They do not change
as you change measurements and are unaffected by a measurement preset.
Dual Attenuator Configurations
Configuration 1: Mechanical attenuator + optional electronic attenuator
Configuration 2: Mechanical attenuator, no optional electronic attenuator
(note that Configuration 2 is not strictly speaking a dual-section attenuator, since
there is no electronic section available. However, it behaves exactly like
Configuration 1 without the Electronic Attenuator option EA3, therefore for the sake
of this document it is grouped into the “Dual Attenuator” configuration)
Single Attenuator Configuration
In the single attenuator configuration, you control the attenuation with a single
control, as the fixed stage has only two states. In the dual attenuator configuration,
both stages have significant range so you are given separate control of the
mechanical and electronic attenuator stages.
117
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Amplitude
Dual Attenuator Configurations
Configuration 1: Mechanical attenuator + optional electronic attenuator
Configuration 2: Mechanical attenuator, no optional electronic attenuator
(note that Configuration 2 is not strictly speaking a dual-section attenuator, since
there is no electronic section available. However, it behaves exactly like
Configuration 1 without the Electronic Attenuator option EA3, therefore for the sake
of this document it is grouped into the “Dual Attenuator” configuration)
Single Attenuator Configuration
Mech Atten
This control is labeled Mech Atten in dual attenuator models and Atten in single
attenuator models. In the dual attenuator configuration, this control only affects the
mechanical attenuator.
Remote Language Compatibility Measurement Application Reference
118
3 RLC Mode & Swept SA Measurement
Amplitude
This control lets you modify the attenuation applied to the RF input signal path. This
value is normally auto coupled to the Ref Level, the Internal Preamp Gain, any
External Gain that is entered, and the Max Mixer Level, as described in the table
below.
Attenuator Configurations and Auto/Man
There are two distinct attenuator configurations available in the X-Series, the
single attenuator and dual attenuator configurations. In dual attenuator
configurations, we have the mechanical attenuation and the electronic attenuation,
and the current total attenuation is the sum of the electronic + mechanical
attenuation. In single attenuator configurations, we refer to the attenuation set
using the Mech Atten control (or POW:ATT SCPI) as the “main” attenuation; and
the attenuation that is set by the SCPI command POW:EATT as the “soft”
attenuation (the POW:EATT command is honored even in the single attenuator
configuration, for compatibility purposes). Then the current total attenuation is the
sum of the main + soft attenuation. See the "Elec Atten" on page 120 control
description for more on “soft” attenuation.
In the dual attenuator configuration, when the electronic attenuator is enabled,
there is no Auto/Man functionality for the mechanical attenuator, and the
Auto/Man toggle function disappears:
Command
[:SENSe]:POWer[:RF]:ATTenuation <rel_ampl>
[:SENSe]:POWer[:RF]:ATTenuation?
[:SENSe]:POWer[:RF]:ATTenuation:AUTO OFF|ON|0|1
[:SENSe]:POWer[:RF]:ATTenuation:AUTO?
Example
POW:ATT 20
Dual attenuator configuration: sets the mechanical attenuator to 20 dB.
Single attenuator mode: sets the main attenuation to 20 dB.
If the attenuator was in Auto, it sets it to Manual.
Preset
The preset for Mech Attenuation is “Auto.”
Min/Max
Min:0 dB
The attenuation set by this control cannot be decreased below 6 dB with the knob or step
keys. To get to a value below 6 dB it has to be directly entered from the keypad or via
SCPI. This protects from adjusting the attenuation to a dangerously small value which
can put the instrument at risk of damage to input circuitry. However, if the current
mechanical attenuation is below 6 dB it can be increased with the knob and step keys,
but not decreased.
Max:70 dB
In the single attenuator configuration, the total of ATT and EATT cannot exceed 50 dB, so
if the EATT is set to 24 dB first, the main attenuation cannot be greater than 26 dB and
119
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Amplitude
will be reduced accordingly; if the main attenuator is set to 40 dB first, EATT cannot be
greater than 10 dB.
State
Saved
Saved in instrument state.
Dependencies
Some measurements do not support the Auto setting of Mech Atten. In these
measurements, the Auto/Man selection is not available, and the Auto/Man toggle
function is not available.
In dual attenuator configurations, when the electronic attenuator is enabled, the
mechanical attenuator has no auto setting and the Auto/Man toggle function is not
available. The state of Auto/Man is remembered and restored when the electronic
attenuator is once again disabled.
Couplings
When Mech Atten is in Auto, it uses the following algorithm to determine a value:
If the USB Preamp is connected to USB, use 0 dB.
Otherwise, Atten = ReferenceLevel + PreAmpGain + ExternalGain – RefLevelOffset
- MaxMixerLevel + IF Gain.
Limit this value to be between 6 dB and the Max value (see Max row, below). No
value below 6 dB can ever be chosen by Auto.
The resulting value is rounded up to the largest value possible given the
attenuation step setting. That is, 50.01 dB would change to 60 dB (for a 10 dB
attenuation step).
The “IF Gain” term in the equation above is either 0 dB or +10 dB, depending on the
settings of FFT IF Gain, Swept IF Gain, max Ref Level and the Auto/Man setting of
Mech Atten. See Error! Reference source not found.
In External Mixing,where the Attenuator is not in the signal path, the Attenuator
setting changes as described above when Mech Atten is in Auto, but no changes
are made to the actual attenuator hardware setting until the input is changed back
to the RF Input.
Elec Atten
Controls the Electronic Attenuator in dual attenuator configurations. This control
does not appear in single attenuator configurations, as the control of both the
mechanical and electronic stages of the single attenuator is integrated into the
single Atten control.
This control includes an Enable/Disable toggle switch. It is only possible to enter a
value for the Electronic Attenuator when this switch is in the “Enable” position.
Using the Electronic Attenuator: Pros and Cons
The electronic attenuator offers finer steps than the mechanical attenuator, has no
acoustical noise, is faster, and is less subject to wear.
Remote Language Compatibility Measurement Application Reference
120
3 RLC Mode & Swept SA Measurement
Amplitude
The “finer steps” advantage of the electronic attenuator is beneficial in optimizing
the alignment of the analyzer dynamic range to the signal power in the front panel
as well as remote use. Thus, you can achieve improved relative signal
measurement accuracy. Compared to a mechanical attenuator with 2 dB steps, the
1 dB resolution of the electronic attenuator only gives better resolution when the
odd-decibel steps are used. Those odd-decibel steps are less accurately calibrated
than the even-decibel steps, though, so one tradeoff for this superior relative
accuracy is reduced absolute amplitude accuracy.
Another disadvantage of the electronic attenuator is that the spectrum analyzer
loses its “Auto” setting, making operation less convenient.
Also, the relationship between the dynamic range specifications (TOI, SHI,
compression and noise) and instrument performance are less well-known with the
electrical attenuator. With the mechanical attenuator, TOI, SHI and compression
threshold levels increase dB-for-dB with increasing attenuation, and the noise floor
does as well. With the electronic attenuator, there is an excess attenuation of
about 1 to 3 dB between 0 and 3.6 GHz, making the effective TOI, SHI, and so forth,
less well known. Excess attenuation is the actual attenuation relative to stated
attenuation. Excess attenuation is accounted for in the analyzer calibration.
Command
[:SENSe]:POWer[:RF]:EATTenuation <rel_ampl>
[:SENSe]:POWer[:RF]:EATTenuation?
[:SENSe]:POWer[:RF]:EATTenuation:STATe OFF|ON|0|1
[:SENSe]:POWer[:RF]:EATTenuation:STATe?
Example
POW:EATT 10
POW:EATT?
POW:EATT:STAT ON
Preset
0 dB
OFF for Swept SA measurement
ON for all other measurements that support the electronic attenuator
Min/Max
Min:0 dB
Max:Dual attenuator configuration: 24 dB
Single attenuator configuration: the total of ATT and EATT cannot exceed 50 dB, so if the
EATT is set to 24 dB first, the main attenuation cannot be greater than 26 dB and will be
reduced accordingly; if the main attenuator is set to 40 dB first, EATT cannot be greater
than 10 dB
State
Saved
Saved in instrument state.
Notes
Electronic Attenuation’s specification is defined only when Mechanical Attenuation
is 6 dB.
Dependencies
This control only appears in Dual Attenuator models with an Electronic Attenuator
installed. It does not appear in models with the Single Attenuator configuration, as
in the single attenuator configuration there is no “electronic attenuator” there is
121
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Amplitude
only a single integrated attenuator (which has both a mechanical and electronic
stage). However, in the single attenuator configuration, EATT SCPI commands are
accepted for compatibility with other X-series instruments and set a “soft”
attenuation as described in Attenuator Configurations and Auto/Man. The “soft”
attenuation is treated as an addition to the “main” attenuation value set by the
Atten control or the POW:ATT SCPI command and affects the total attenuation
displayed on the Atten control and the Meas Bar.
When Enable Elec Atten is off or grayed out, the Elec Atten control is grayed out.
This control only appears in Dual Attenuator models with an Electronic Attenuator
installed. It does not appear in models with the Single Attenuator configuration, as
in the single attenuator configuration there is no “electronic attenuator” there is
only a single integrated attenuator (which has both a mechanical and electronic
stage). However, in the single attenuator configuration, EATT SCPI commands are
accepted for compatibility with other X-series instruments and set a “soft”
attenuation as described in Attenuator Configurations and Auto/Man.
The electronic attenuator (and the “soft” attenuation function provided in single
attenuator configurations) is unavailable above 3.6 GHz. Therefore, if the Stop
Frequency of the analyzer is > 3.6 GHz then the Enable Elec Atten control will be
OFF and grayed out.
If the Internal Preamp is on, meaning it is set to Low Band or Full, the electronic
attenuator (and the “soft” attenuation function provided in single attenuator
configurations) is unavailable. In this case the Enable Elec Atten control will be OFF
and grayed out.
If either of the above is true, if the SCPI command is sent, an error indicating that
the electronic attenuator is unavailable will be sent.
If the electronic/soft Attenuator is enabled, then the Stop Freq of the analyzer is
limited to 3.6 GHz and the Internal Preamp is unavailable.
The SCPI-only “soft” electronic attenuation for the single-attenuator configuration
is not available in all measurements. It is not available in the Swept SA
measurement.
Couplings
Enabling and disabling the Electronic Attenuator affects the setting of the
Mechanical Attenuator (in dual attenuator configurations). This is described in more
detail below this table.
More Information
The electronic attenuator offers finer steps than the mechanical attenuator, has no
acoustical noise, is faster, and is less subject to wear. These advantages primarily
aid in remote operation and are negligible for front panel use. See Using the
Electronic Attenuator: Pros and Cons for a detailed discussion of the pros and cons
of using the electronic attenuator.
For the single attenuator configuration, for SCPI backwards compatibility, the
“soft” attenuation feature replaces the dual attenuator configuration’s electronic
Remote Language Compatibility Measurement Application Reference
122
3 RLC Mode & Swept SA Measurement
Amplitude
attenuator. All the same couplings and limitations apply. See Attenuator
Configurations and Auto/Man.
Mechanical Attenuator Transition Rules
When the Electronic Attenuator is enabled, the Mechanical Attenuator transitions
to a state that has no Auto function. Below are the rules for transitioning the
Mechanical Attenuator. Note that the information below ONLY applies to the dual
attenuator configurations, and ONLY when the Electronic Attenuator is installed:
When the Electronic Attenuation is enabled from a disabled state
– The Mechanical Attenuator is initialized to 10 dB (this is its optimal performance
setting). You can then set it as desired with SCPI, numeric keypad, step keys, or
knob, and it behaves as it normally would in manual mode.
– The Auto/Man state of (Mech) Atten is saved.
– The Auto/Man line on the (Mech) Atten softkey disappears and the auto rules
are disabled.
– The Electronic Attenuator is set to 10 dB less than the previous value of the
Mechanical Attenuator, within the limitation that it must stay within the range of
0 to 24 dB of attenuation.
Examples in the dual attenuator configuration
– Mech Atten at 20 dB. Elec Atten enabled, Mech Atten set to 10 dB, and Elec
Atten set to 10 dB. New total attenuation equals the value before Elec Atten
enabled.
– Mech Atten at 0 dB. Elec Atten enabled, Mech Atten set to 10 dB, and Elec
Atten set to 0 dB. New total attenuation does not equal the value before Elec
Atten enabled.
– Mech Atten at 40 dB. Elec Atten enabled, Mech Atten set to 10 dB, and Elec
Atten set to 24 dB. New total attenuation does not equal the value before Elec
Atten enabled.
When the Electronic Attenuation is disabled from an enabled state
– The Elec Atten key is grayed out.
– The Auto/Man state of (Mech) Atten is restored.
– If now in Auto, (Mech) Atten recouples.
– If now in Man, (Mech) Atten is set to the value of total attenuation that existed
before the Elec Atten was disabled. The resulting value is rounded up to the
smallest value possible given the (Mech) Atten Step setting - (That is, 57 dB
changes to 58 dB when (Mech) Atten Step is 2 dB.)
123
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Amplitude
Mech Atten Step
This controls the step size used when making adjustments to the input attenuation.
This control is labeled Mech Atten Step in dual attenuator models and Atten Step in
single attenuator models. In the dual attenuator configuration, this control only
affects the step size of the mechanical attenuator.
This feature has a toggle choice from the front panel, but it takes a specific value (in
dB) when used remotely. The only valid values are 2 and 10.
Command
[:SENSe]:POWer[:RF]:ATTenuation:STEP[:INCRement] 10 dB | 2 dB
[:SENSe]:POWer[:RF]:ATTenuation:STEP[:INCRement]?
Example
POW:ATT:STEP 2
Preset
2 dB unless noted below.
EXA and CXA: 10 dB (2 dB with option FSA)
State Saved
Saved in instrument state.
Couplings
When the attenuation step size changes, the current mechanical attenuation value
is adjusted (if necessary) to be quantized to the new step size. That is, if the step is
set to 10 dB,the mechanical attenuation is increased if necessary so it is a multiple
of 10 dB.
Dependencies
Blanked in CXA and EXA if option FSA (2 dB steps) is not present. If blanked,
attempts to set it via SCPI will yield an error.
Max Mixer Level
Controls the limitation on the Ref Level for a given attenuation setting, and therefore
also interacts with the Auto rules for selecting the attenuation as a coupling from the
reference level.
Command
[:SENSe]:POWer[:RF]:MIXer:RANGe[:UPPer] <real>
[:SENSe]:POWer[:RF]:MIXer:RANGe[:UPPer]?
Example
POW:MIX:RANG -15 dBm
Preset
-10 dBm
Min/Max
-50 dBm/0 dBm
State Saved
Saved in instrument state
Max Mixer Lvl Rule
The Max Mixer Level Rules allows you to optimize the Max Mixer Level setting for
certain kinds of measurements.
Remote Language Compatibility Measurement Application Reference
124
3 RLC Mode & Swept SA Measurement
Amplitude
– Normal – historical, and backwards compatible. The analyzer has been designed
so that, at the default setting, any signal below the reference level is extremely
unlikely to give ADC overloads. At this mixer level the scale fidelity will be within
specifications, thus compression with be negligible.
– TOI – allows a range of settings of the Max Mixer Level that can be optimum for
measurements limited by the analyzer third-order dynamic range. The default
setting is commonly appropriate but RBW affects this. A good setting for Max
Mixer Level would be higher than the optimum mixer level by half of the
attenuator step size.
– Compression – allows a range of settings of the Max Mixer Level that can be
optimum for measurements limited by the tradeoffs between analyzer accuracy
due to compression, and dynamic range due to the noise floor. The default
setting is commonly appropriate, representing mixer drive levels that cause 1 dB
or less compression at most carrier frequencies. Typical measurements that
would be optimized by this setting are the measurement of low sideband levels,
including nulls, in angle-modulated signals (FM and PM). Also pulsed-RF
measurements, including finding nulls to estimate pulse width, which are often
best done with significant overdrive (compression) of the front end.
Setting
Name
(readback)
Setting Name
(verbose)
Max Mixer Level
Preset Value,
dBm
Max Mixer Level
minimum value,
dBm
Max Mixer Level
maximum value,
dBm
Normal
Normal – balance
TOI, noise and
compression
−10
−50
0
TOI
TOI-limited dynamic
range
−25
−50
−10
Compression
Compression-limited
dynamic range
−3
−10
+30
Command
Not available in N9061C
Preset
NORM
Signal Path Tab
Presel Center
When this control is pressed, the centering of the preselector filter is adjusted to
optimize the amplitude accuracy at the frequency of the selected marker. If the
selected marker is not on when Presel Center is pressed, the analyzer will turn on
the selected marker, perform a peak search, and then perform centering on the
marker’s center frequency. If the selected marker is already on and between the
start and stop frequencies of the analyzer, the analyzer performs the preselector
calibration on that marker’s frequency. If the selected marker is already on, but
125
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Amplitude
outside the frequency range between Start Freq and Stop Freq, the analyzer will
first perform a peak search, and then perform centering on the marker’s center
frequency.
Command
[:SENSe]:POWer[:RF]:PCENter
Example
POW:PCEN
The value displayed on the Presel Adjust control will change to reflect the new
preselector tuning.
A number of considerations should be observed to ensure proper operation.
Proper Preselector Operations
A number of considerations should be observed to ensure proper operation:
1. If the selected marker is off, the analyzer will turn on a marker, perform a peak
search, and adjust the preselector using the selected marker’s frequency. It
uses the "highest peak" peak search method unqualified by threshold or
excursion, so that there is no chance of a ‘no peak found’ error. It continues with
that peak, even if it is the peak of just noise. Therefore, for this operation to work
properly, there should be a signal on screen in a preselected range for the peak
search to find.
2. If the selected marker is already on, the analyzer will attempt the centering at
that marker’s frequency. There is no preselector for signals below about 3.6
GHz, therefore if the marker is on a signal below 3.6 GHz, no centering will be
attempted and an advisory message generated.
3. In some models, the preselector can be bypassed. If it is bypassed, no centering
will be attempted in that range and a message will be generated
Notes
Note that the rules outlined above under the control description apply for the
remote command as well as the control.The result of the command is dependent
on marker position, and so forth. Any message shown by pressing the control is
also shown in response to the remote command.
Dependencies
Grayed out if the microwave preselector is off.
If the selected marker’s frequency is below Band 1, advisory message 0.5001 is
generated and no action is taken.
Grayed out if entirely in Band 0.
Blank in models that do not include a preselector, such as option 503. If the SCPI is
sent in these instruments, it is accepted without error, and the query always
returns 0.
Grayed out in the Spectrogram View.
Couplings
Remote Language Compatibility Measurement Application Reference
126
3 RLC Mode & Swept SA Measurement
Amplitude
The active marker position determines where the centering will be attempted.
If the analyzer is in a measurement such as averaging when centering is initiated,
the act of centering the preselector will restart averaging but the first average trace
will not be taken until the centering is completed.
Status Bits/OPC dependencies
When centering the preselector, *OPC will not return true until the process is
complete and a subsequent measurement has completed, nor will results be
returned to a READ or MEASure command.
The Measuring bit should remain set while this command is operating and should
not go false until the subsequent sweep/measurement has completed.
Preselector Adjust
Allows you to manually adjust the preselector filter frequency to optimize its
response to the signal of interest.
For general purpose signal analysis, using Presel Center is recommended.
Centering the filter minimizes the impact of long-term preselector drift. Presel Adjust
can be used instead to manually optimize the preselector. One application of manual
optimization would be to peak the preselector response, which both optimizes the
signal-to-noise ratio and minimizes amplitude variations due to small (short-term)
preselector drifting.
Command
[:SENSe]:POWer[:RF]:PADJust <freq>
[:SENSe]:POWer[:RF]:PADJust?
Example
POW:PADJ 100KHz
POW:PADJ?
Preset
0 MHz
Min/Max
–500 MHz/500 MHz
State
Saved
The Presel Adjust value set by Presel Center, or by manually adjusting Presel Adjust, is
not saved in instrument state, and does not survive a Preset or power cycle.
Notes
The value on the control reads out to 0.1 MHz resolution.
Dependencies
Grayed out if microwave preselector is off.
Grayed out if entirely in Band 0.
Blank in models that do not include a preselector, such as option 503. If the SCPI is
sent in these instruments, it is accepted without error, and the query always
returns 0.
Grayed out in the Spectrogram View.
Backwards Compatibility
Command
127
[:SENSe]:POWer[:RF]:MW:PADJust
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Amplitude
[:SENSe]:POWer[:RF]:MMW:PADJust
Note
The PSA had multiple preselectors, but the X-Series has only one. These commands
simply alias to [:SENSe]:POWer[:RF]:PADJust
Command
[:SENSe]:POWer[:RF]:PADJust:PRESelector MWAVe|MMWave|EXTernal
[:SENSe]:POWer[:RF]:PADJust:PRESelector?
Note
The PSA had multiple preselectors, and you could select which preselector to adjust.
Since the X-Series has only one mm/uW preselector, the preselector selection softkey
is no longer available. However, to provide backward compatibility, we accept the
legacy remote commands.
The command form has no effect, the query always returns MWAVe.
Internal Preamp
Accesses a menu of controls for the internal preamplifier. Turning on the preamplifier
gives a better noise figure, but a poorer TOI to noise floor dynamic range. You can
optimize this setting for your particular measurement.
The instrument takes the preamp gain into account as it sweeps. If you sweep
outside of the range of the preamp the instrument will also account for that. The
displayed result will always reflect the correct gain.
For some measurements, when the preamp is on and any part of the displayed
frequency range is below the lowest frequency for which the preamp has
specifications, a warning condition message appears in the status line. For example
,for a preamp with a 9 kHz lowest specified frequency: "Preamp: Accy unspec’d
below 9 kHz".
[:SENSe]:POWer[:RF]:GAIN[:STATe] OFF|ON|0|1
Command
[:SENSe]:POWer[:RF]:GAIN[:STATe]?
[:SENSe]:POWer[:RF]:GAIN:BAND LOW|FULL
[:SENSe]:POWer[:RF]:GAIN:BAND?
OFF
Preset
LOW
State Saved
Saved in instrument state.
Examples
Selection
Example
Note
Off
:POW:GAIN OFF
Low
Band
:POW:GAIN ON
:POW:GAIN:BAND
LOW
Sets the internal preamp to use only the low band. The frequency
range of the installed (optional) low-band preamp is displayed in
square brackets on the Low Band selection in the dropdown.
Full
Range
:POW:GAIN ON
:POW:GAIN:BAND
FULL
Sets the internal preamp to use its full range. The low band (03.6 GHz or 0-3GHz, depending on the model) is supplied by the
low band preamp and the frequencies above low band are
supplied by the high band preamp.
Remote Language Compatibility Measurement Application Reference
128
3 RLC Mode & Swept SA Measurement
Amplitude
Selection
Example
Note
The frequency range of the installed (optional) low-band preamp
is displayed in square brackets on the Full Range selection in the
dropdown. If the high band option is not installed the Full Range
selection does not appear.
Dependencies
Preamp is not available on all hardware platforms. If the preamp is not present or is
unlicensed, the key is not shown.
The preamp is not available when the electronic/soft attenuator is enabled.
If a POW:GAIN:BAND FULL command is sent when a low band preamp is available,
the preamp band parameter is to LOW instead of FULL, and an "Option not
installed" message is generated.
Couplings
The act of connecting the U7227A USB Preamplifier to one of the analyzer’s USB
ports will cause the Internal Preamp to be switched on. When this happens an
informational message will be generated: “Internal Preamp turned on for optimal
operation with USB Preamp.” Note that if the Internal Preamp was already on,
there will be no change to the setting, but if it was Off it will be switched On, to Full
Range.
Note that this same action occurs when the SA mode is selected while the USB
Preamp is connected to one of the analyzer’s USB ports, if it is the first time that the
SA mode has run since powerup, or if the last time the SA mode was running the
USB Preamp was NOT connected.
Subsequently disconnecting the USB Preamp from USB does not change the
Internal Preamp setting nor restore the previous setting.
µW Path Control
The µW Path Control functions include the µW Preselector Bypass (Option MPB) and
Low Noise Path (Option LNP) controls in the High Band path circuits.
When the µW Preselector is bypassed, you have better flatness, but will be subject
to spurs from out of band interfering signals. When the Low Noise Path is enabled,
the analyzer automatically switches around certain circuitry in the high frequency
bands that can contribute to noise, when it is appropriate based on other analyzer
settings.
For most applications, the preset state is Standard Path, which gives the best
remote-control throughput, minimizes acoustic noise from switching and minimizes
the risk of wear out in the hardware switches. For applications that utilize the
wideband IF paths, the preset state is the µW Preselector Bypass path, if option
MPB is present. This is because, when using a wideband IF such as the 140 MHz IF,
the µW Preselector’s bandwidth can be narrower than the available IF bandwidth,
causing degraded amplitude flatness and phase linearity, so it is desirable to bypass
the preselector in the default case.
129
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Amplitude
You may choose Low Noise Path Enable. It gives a lower noise floor, especially in the
21-26.5 GHz region, though without improving many measures of dynamic range,
and without giving the best possible noise floor. The preamp, if purchased and used,
gives better noise floor than does the Low Noise Path, however its compression
threshold and third-order intercept are much poorer than that of the non-preamp
Low Noise Path. There are some applications, typically for signals around −30 dBm,
for which the third-order dynamic range of the standard path is good enough, but the
noise floor is not low enough even with 0 dB input attenuation. When the third-order
dynamic range of the preamp path is too little and the noise floor of the standard
path is too high, the Low Noise Path can provide the best dynamic range.
Command
[:SENSe]:POWer[:RF]:MW:PATH STD|LNPath|MPBypass
[:SENSe]:POWer[:RF]:MW:PATH?
Example
:POW:MW:PATH LNP enables the Low Noise path
Preset
STD
State Saved
Save in instrument state.
Examples
Path
Example
Note
Standard
Path
:POW:MW:PATH
STD
This path gives the best remote-control throughput, minimizes
acoustic noise from switching and minimizes the risk of wear in
the hardware switches, particularly in remote test scenarios
where both low band and high band setups will follow in rapid
succession.
In this path, the bypass of the low band/high band switch and
microwave preamp is never activated, which can cause some
noise degradation but preserves the life of the bypass switch.
Low Noise
Path
Enable
:POW:MW:PATH
LNP
See "Low Noise Path Enable" on page 131
µW
Preselector
Bypass
:POW:MW:PATH
MPB
See "µW Preselector Bypass" on page 133
Notes
If a Presel Center is performed, the analyzer will momentarily switch to the
Standard Path, regardless of the setting of µW Path Control.
The DC Block will always be switched in when the low noise path is switched in, to
protect succeeding circuitry from DC. Note that this does not mean “when the low
noise path is enabled” but when, based on the Low Noise Path rules, the path is
actually switched in. This can happen when the selection is Low Noise Path Enable.
In the case where the DC Block is switched in the analyzer is now AC coupled.
However, if the user has selected DC coupling, the UI will still behave as though it
were DC coupled, including all annunciation, warnings, status bits, and responses
Remote Language Compatibility Measurement Application Reference
130
3 RLC Mode & Swept SA Measurement
Amplitude
to SCPI queries. This is because, based on other settings, the analyzer could switch
out the low noise path at any time and hence go back to being DC coupled.
Alignment switching ignores the settings in this menu, and restores them when
finished.
Dependencies
The µW Path Control control does not appear in BBIQ and External Mixing. The Low
Noise Path selection does not appear unless Option LNP is present and licensed.
The μW Preselector Bypass selection does not appear unless Option MPB is
present and licensed. In either of these two cases, if the SCPI command sent, error
-241, "Hardware missing; Option not installed" is generated.
The Low Noise Path selection is grayed out if the current measurement does not
support it.
Backwards Compatibility
Command
[:SENSe]:POWer[:RF]:MW:PRESelector[:STATe] ON|OFF|0|1
[:SENSe]:POWer[:RF]:MW:PRESelector[:STATe]?
Example
:POW:MW:PRES OFF by passes the microwave preselector
Notes
The ON parameter sets the STD path (:POW:MW:PATH STD)
The OFF parameter sets path MPB (:POW:MW:PATH MPB)
Preset
ON
Low Noise Path Enable
You may choose Low Noise Path Enable, which gives a lower noise floor under
some circumstances, particularly when operating in the 21-26.5 GHz region. With
the Low Noise Path enabled, the low band/high band switch and microwave
preamp are bypassed whenever all of the following are true:
– the analyzer is not in the Low Band, meaning:
– the start frequency is above 3.5 GHz and
– the stop frequency is above 3.6 GHz.
– the internal preamp is not installed or (if installed) is set to Off or Low Band
Note that this means that, when any part of a sweep is done in Low Band, the Low
Noise Path is not used, whether or not the Low Noise Path Enable is selected in the
user interface. Also, if the preamp is turned on, the Low Noise Path is not used,
whether or not the Low Noise Path Enable is selected in the user interface. The only
time the Low Noise Path is used is when Low Noise Path Enable is selected, the
sweep is completely in High Band (> 3.6 GHz) and no preamp is in use.
For measurements that use IQ acquisition, the low noise path is used when the
Center Frequency is in High Band (> 3.6 GHz) and no preamp is in use. The rules
above are modified to use only the center frequency to qualify which path to switch
in. This is not the case for FFT’s in the Swept SA measurement; they use the same
rules as swept measurements.
131
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Amplitude
You should understand that the Low Noise Path, while giving improved DANL, has
the disadvantage of decreased TOI performance and decreased gain compression
performance relative to the standard path.
The low noise path is useful for situations where the signal level is so low that the
analyzer performance is dominated by noise even with 0 dB attenuation, but still
high enough that the preamp option would have excessive third-order
intermodulation or compression. The preamp, if purchased and used, gives better
noise floor than does the “Low Noise Path.” However, its compression threshold
and third-order intercept are much poorer than that of the non-preamp path. There
are some applications, typically for signals around −30 dBm, for which the thirdorder dynamic range of the standard path is good enough, but the noise floor is not
low enough even with 0 dB input attenuation. When the third-order dynamic range
of the preamp path is too little and the noise floor of the standard path is too high,
the Low Noise Path can provide the best dynamic range
The graph below illustrates the concept. It shows, in red, the performance of an
analyzer at different attenuation settings, both with the preamp on and off, in a
measurement that is affected by both analyzer noise and analyzer TOI. The green
shows the best available dynamic range, offset by 0.5 dB for clarity. The blue
shows how the best available dynamic range improves for moderate signal levels
with the low noise path switched in. In this illustration, the preamp improves the
noise floor by 15 dB while degrading the third-order intercept by 30 dB, and the low
noise path reduces loss by 8 dB. The attenuator step size is 2 dB.
There are other times where selecting the low noise path improves performance,
too. Compression-limited measurements such as finding the nulls in a pulsed-RF
spectrum can profit from the low noise path in a way similar to the TOI-limited
Remote Language Compatibility Measurement Application Reference
132
3 RLC Mode & Swept SA Measurement
Amplitude
measurement illustrated. Accuracy can be improved when the low noise path
allows the optimum attenuation to increase from a small amount like 0, 2 or 4 dB to
a larger amount, giving better return loss at the analyzer input. Harmonic
measurements, such as second and third harmonic levels, are much improved
using the low noise path because of the superiority of that path for harmonic
(though not intermodulation) distortion performance.
µW Preselector Bypass
This toggles the preselector bypass switch for band 1 and higher. When the
microwave presel is on, the signal path is preselected. When the microwave
preselector is off, the signal path is not preselected. The preselected path is the
normal path for the analyzer.
The preselector is a tunable bandpass filter that prevents signals away from the
frequency of interest from combining in the mixer to generate in-band spurious
signals (images). The consequences of using a preselector filter are its limited
bandwidth, the amplitude and phase ripple in its passband, and any amplitude and
phase instability due to center frequency drift.
Option MPB or pre-selector bypass provides an unpreselected input mixer path for
certain X-Series signal analyzers with frequency ranges above 3.6 GHz. This signal
path allows a wider bandwidth and less amplitude variability, which is an
advantage when doing modulation analysis and broadband signal analysis. The
disadvantage is that, without the preselector, image signals will be displayed.
Another disadvantage of bypassing the preselector is increased LO emission levels
at the front panel input port.
Image responses are separated from the real signal by twice the 1st IF. For IF
Paths of 10 MHz and 25 MHz, the 1st IF is 322.5 MHz, so the image response and
the real signal will be separated by 645 MHz. The 1st IF will be different for other IF
Path settings. When viewing a real signal and its corresponding image response in
internal mixing, the image response will be to the left of the real signal.
Also, the image response and the real signal typically have the same amplitude
and exhibit the same shape factor.
However, if Option FS1, Fast Sweep Capability, is enabled, the image response in
the Swept SA measurement will appear lower in amplitude and have a much wider
shape factor compared to the real signal.
133
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
BW
BW
The BW key opens the bandwidth menu, which contains controls for the Resolution
Bandwidth and Video Bandwidth functions of the instrument.
The Resolution BW functions control filter bandwidth and filter type. There are two
filter types, Gaussian and Flattop. The Gaussian filters have a response curve that is
parabolic on a log scale. The Flattop filter shape is a close approximation of a
rectangular filter.
Backwards Compatibility Notes
The AVERAGE functions, which appeared in the BW menu in earlier analyzers, can
now be found in the Trace menu and the Meas Setup menu.
In the Trace menu, you may turn Trace Averaging on or off for the desired traces
(rather than globally as in the past).
In the Meas Setup menu you may configure Averaging, by setting the Average
Number and the Average Type.
BW Settings Tab
Res BW
Activates the resolution bandwidth active function, which allows you to manually set
the resolution bandwidth (RBW) of the analyzer. Normally, Res BW (Auto) selects
automatic coupling of the Res BW to Span using the ratio set by the Span:3 dB RBW
key. To decouple the resolution bandwidth, press the Auto/Man toggle on the Res
BW control, or simply enter a different value for Res BW.
When the Res BW is manually selected, it may be returned to the coupled state by
pressing the Auto/Man toggle on the Res BW control. This may also be done by
pressing Auto Couple or by performing a Preset.
Command
[:SENSe]:BANDwidth|BWIDth[:RESolution] <freq>
[:SENSe]:BANDwidth|BWIDth[:RESolution]?
[:SENSe]:BANDwidth|BWIDth[:RESolution]:AUTO OFF|ON|0|1
[:SENSe]:BANDwidth|BWIDth[:RESolution]:AUTO?
Example
BAND 1 KHZ
BAND?
BWID:AUTO ON
BWID:AUTO?
Preset
Auto
Min/Max
Min:1 Hz
Max:8 MHz is the max equivalent –3 dB RBW, which means that the named RBW can
actually exceed 8 MHz if using a filter other than –3 dB Gaussian
State
Saved
Saved in instrument state.
Remote Language Compatibility Measurement Application Reference
134
3 RLC Mode & Swept SA Measurement
BW
Notes
For numeric entries, all RBW Types choose the nearest (arithmetically, on a linear
scale, rounding up) available RBW to the value entered.
The setting and querying of values depends on the current bandwidth type.
Dependencies
When in Zero Span with no EMI Standard selected, there is no Auto setting for Res
BW. The Auto/Man toggle disappears in this case, and if the SCPI command
[:SENSe]:BWID[:RESolution]:AUTO ON is sent, it generates a message.
While using the Tracking Generator, you must make sure the Start Frequency is
high enough to avoid capturing LO feedthrough in the trace. How high you must
make the Start Frequency to avoid this will depend on the RBW you have set. The
analyzer displays a condition warning message if the Start Frequency falls below
roughly 2.5 times the current RBW. The warning is, “Source Uncal;adj Start
Freq|RBW|Points”. When you see this warning, you should increase the Start Freq,
narrow the RBW, or increase the number of Sweep Points.
Couplings
Res BW is normally coupled to Span; if Res BW is set to Auto, as the Span
decreases, so will the Res BW, to maintain the ratio set by the Span:3 dB RBW
control (or 106:1 for measurements that do not have a Span:3 dB RBW control). In
Zero Span, this coupling is normally turned off and Res BW has no Auto setting.
When a CISPR or MIL EMI Standard is in use, the Res BW is coupled to Center
Frequency and not to Span, and this is true even in Zero Span
More Information
When Res BW is set to Auto, the bandwidth selected depends on the Filter Type.
Only certain discrete resolution bandwidths are available. The available
bandwidths are dependent on the Filter Type or the EMC Standard. If an
unavailable bandwidth is entered with the numeric keypad, the closest available
bandwidth is selected.
The zero-span case in the Swept SA measurement deserves some mention,
because RBW is coupled to Span when in a swept (non-zero) span and in zero span
there is normally no meaningful RBW coupling in Zero Span. However, when a MIL
or CISPR EMC Standard is selected, there IS a meaningful coupling for RBW in Zero
Span – in fact, it is coupled to Center Frequency, in order to make measurements
according to the EMI specifications.
Video BW
Lets you change the analyzer post-detection filter (VBW or “video bandwidth”) from
1 Hz to 8 MHz in approximately 10% steps. In addition, a wide-open video filter
bandwidth may be chosen by selecting 50 MHz. The VBW is annotated at the bottom
of the display, in the center.
An * is displayed next to the VBW annotation when certain detector types (Average,
EMI Average, Quasi Peak, and RMS Average) are in use. This is because the VBW
filter is out of the circuit for these detectors and does not affect any traces which use
135
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
BW
them. If there is any active trace using one of these detectors the * is displayed. See
Annotation Examples.
Normally, Video BW (Auto) selects automatic coupling of the Video BW to RBW
using the ratio set by the VBW:3 dB RBW key. To decouple the resolution bandwidth,
press the Auto/Man toggle on the Video BW control, or simply enter a different value
for Video BW.
When the Video BW is manually selected, it may be returned to the coupled state by
pressing the Auto/Man toggle on the Video BW control. This may also be done by
pressing Auto Couple or by performing a Preset.
Command
[:SENSe]:BANDwidth|BWIDth:VIDeo <freq>
[:SENSe]:BANDwidth|BWIDth:VIDeo?
Example
BAND:VID 1 kHz
BAND:VID?
BWID:VID:AUTO ON
BWID:VID:AUTO?
Preset
Auto
ON
Min/Max
Min:1 Hz
Max:50 MHz
State Saved
Saved in instrument state.
Notes
For numeric entries, the analyzer chooses the nearest (arithmetically, on a linear
scale, rounding up) available VBW to the value entered. The 50 MHz VBW is
defined to mean “wide open”.
The values shown in this table reflect the conditions after a Mode Preset.
Dependencies
Some times the displayed Video BW is not actually used to process the trace data:
• When the Average Detector is selected and Sweep Type is set to Swept, the video
bandwidth filter cannot be used, because it uses the same hardware as the
Average Detector.
• When the Quasi-Peak, EMI Average or RMS Average detector is selected the
VBW is implemented by the digital IF as part of the detector
When this is the case, the VBW still acts to change the Sweep Time, if Sweep Time
is in Auto, and still affects the data on other traces for which this is not the case.
Couplings
Video bandwidth (VBW) is normally coupled to RBW. If VBW is set to Auto, then the
VBW is changed as the RBW changes, to maintain the ratio set by the VBW:3 dB
RBW control (or 10:1 for measurements that do not have a VBW:3 dB RBW
control).
Backwards Compatibility Notes
Remote Language Compatibility Measurement Application Reference
136
3 RLC Mode & Swept SA Measurement
BW
For backwards compatibility this command obeys both the BANDwidth and BWIDth
forms.
VBW:3dB RBW
Selects the ratio between the video bandwidth and the equivalent 3 dB resolution
bandwidth to be used for setting VBW when VBW is in Auto.
VBW:3dB RBW (Auto) selects automatic coupling of the VBW:3 dB RBW ratio to
Detector using the rules described below in "Auto Rules" on page 137. To decouple
the ratio, press Auto/Man until the toggle switch selects Man, or simply enter a new
value.
When the VBW:3dB RBW is manually selected, it may be returned to the coupled
state by pressing the VBW:3 dB RBW Auto/Man toggle switch until Auto is selected.
This may also be done by pressing Auto Couple on the Meas Setup menu or by
performing a Preset.
Command
Swept SA:
[:SENSe]:BANDwidth|BWIDth:VIDeo:RATio <real>
[:SENSe]:BANDwidth|BWIDth:VIDeo:RATio?
[:SENSe]:BANDwidth|BWIDth:VIDeo:RATio:AUTO OFF|ON|0|1
[:SENSe]:BANDwidth|BWIDth:VIDeo:RATio:AUTO?
TOI:
[:SENSe]:TOI:BANDwidth:VIDeo:RATio <real>
[:SENSe]:TOI:BANDwidth:VIDeo:RATio?
[:SENSe]:TOI:BANDwidth:VIDeo:RATio:AUTO OFF|ON|0|1
[:SENSe]:TOI:BANDwidth:VIDeo:RATio:AUTO?
Example
Swept SA:
BAND:VID:RAT 2
BAND:VID:RAT?
BAND:VID:RAT:AUTO 0
BAND:VID:RAT:AUTO?
TOI:
TOI:BAND:VID:RAT 2
TOI:BAND:VID:RAT?
TOI:BAND:VID:RAT:AUTO 0
TOI:BAND:VID:RAT:AUTO? ! TOI
Preset
1
ON
Min/Max
0.00001/3000000
State Saved
Saved in instrument state.
Notes
The values shown in this table reflect the conditions after a Mode Preset.
Auto Rules
137
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
BW
The Auto Rules for the VBW:3dB RBW function are as follows:
If Source Mode is set to “Tracking”: Use 1.0
Otherwise, we go through the following list of detector numbers and find the lowest
numbered detector being used on any active traces (traces for which Update is On):
1. Peak
2. Normal
3. Average
4. Sample
5. Negative Peak
6. EMI Average
7. Quasi Peak
8. RMS Average
Use that detector to pick the ratio based on the following criteria:
1. If the detector is Peak and the EMC Standard is set to either CISPR or MIL, use
10.0 (we use wide VBWs to capture peak levels accurately).
2. Otherwise, if the detector is Negative Peak, use 1.0 (in the Negative Peak case,
there are no known significant use models so we use a medium ratio).
3. Otherwise, if the detector is Normal, use 1.0 (historical precedent).
4. Otherwise, if the detector is Average, and the span is nonzero, use 0.1. The use
of a small ratio in Average detection is desirable because of its effect on the
sweep time equations. The VBW filter is not actually in-circuit when the
average detector is on. If the detector is Average, and the span is zero, use
10.0, which gives optimal behavior for Interval Markers in zero span. Note that
only the Swept SA measurement supports Zero Span.
5. Otherwise, if the detector is EMI Average, Quasi Peak or RMS Average, use
10.0. In fact this is a “don’t care” since no VBW is used for these detectors, as
noted under “Dependencies” for the VBW key
6. Otherwise, the detector is simply Peak or Sample. These two detectors,
surprisingly, can use the same rules. In these cases, if any active trace is in max
hold or min hold, use 10.0, because Max and Min Hold operations will usually be
intended to capture peaks and pits without smoothing from the VBW filter;
otherwise, use 1.0 as a compromise, because you have not set the analyzer in a
way that implies that you are measuring noise, pulsed-RF or CW signals, and
for backward compatibility with earlier analyzers.
Remote Language Compatibility Measurement Application Reference
138
3 RLC Mode & Swept SA Measurement
BW
Note that because the above couplings depend on which traces are active, they are
re-examined whenever any trace goes active or inactive, except when this leaves
no traces active. Transitioning to the state where no traces are active should not
affect the couplings. The annotation will always reflect the state of the last trace
which was active.
Span:3 dB RBW
Selects the ratio between span and resolution bandwidth.
Normally, Span:3dB RBW (Auto) selects a Span:3 dB RBW ratio of 106:1 . If you
manually enter the ratio, the Auto/Man toggle switch will move to Man, which
enables you to manually select ratios more suitable for certain measurements.
When the Span:3dB RBW is manually selected, it may be returned to the coupled
state by pressing the Span:3dB RBW Auto/Man toggle switch until Auto is selected.
This may also be done by pressing Auto Couple under Meas Setup or by performing a
Preset.
Command
Swept SA:
[:SENSe]:FREQuency:SPAN:BANDwidth[:RESolution]:RATio <integer>
[:SENSe]:FREQuency:SPAN:BANDwidth[:RESolution]:RATio?
[:SENSe]:FREQuency:SPAN:BANDwidth[:RESolution]:RATio:AUTO
OFF|ON|0|1
[:SENSe]:FREQuency:SPAN:BANDwidth[:RESolution]:RATio:AUTO?
TOI:
[:SENSe]:TOI:FREQuency:SPAN:BANDwidth[:RESolution]:RATio
<integer>
[:SENSe]:TOI:FREQuency:SPAN:BANDwidth[:RESolution]:RATio?
[:SENSe]:TOI:FREQuency:SPAN:BANDwidth[:RESolution]:RATio:AUTO
OFF|ON|0|1
[:SENSe]:TOI:FREQuency:SPAN:BANDwidth[:RESolution]:RATio:AUTO?
Example
FREQ:SPAN:BAND:RAT 200 sets a ratio of 200:1, and turns off the auto coupling.
FREQ:SPAN:BAND:RAT:AUTO ON
FREQ:SPAN:BAND:RAT?
TOI:
TOI:FREQ:SPAN:BAND:RAT 106
TOI:FREQ:SPAN:BAND:RAT:AUTO 0
Preset
106
ON
Min/Max
2/10000
State
Saved
Saved in instrument state.
Notes
The values shown in this table reflect the conditions after a Mode Preset.
139
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
BW
Dependencies
Grayed out when the EMC Standard is set to CISPR or MIL, since RBW is coupled to
Center Frequency rather than Span in this case.
RBW Filter
Selects the type for the resolution bandwidth filters. Historically, the Res BW filters
in HP/Agilent/Keysight spectrum analyzers were Gaussian filters, specified using
the –3 dB bandwidth of the filter. That is, a 10 MHz Res BW filter was a Gaussian
shape with its –3 dB points 10 MHz apart. In the X-Series, the RBW Filter BW menu
lets you choose between a Gaussian and Flat Top filter shape, for varying
measurement conditions.
Command
[:SENSe]:BANDwidth|BWIDth:SHAPe GAUSsian|FLATtop
[:SENSe]:BANDwidth|BWIDth:SHAPe?
Example
BAND:SHAP GAUS
BAND:SHAP?
Preset
Auto Couple chooses the preset value.
State Saved
Saved in instrument state.
Notes
GAUSsian= Gaussian
FLATtop = Flattop
Dependencies
The RBW Filter Type control is grayed out if the EMC Standard is set to CISPR or
MIL. In this case the Filter Type is always Gaussian. The Filter BW is chosen as
appropriate for the filter and the standard. Any attempt to set it to Flattop will give
an error.
RBW Filter BW
Selects the type of filter bandwidth used to specify the width of the Gaussian RBW
filters. Historically, the Gaussian Res BW filters in HP/Agilent/Keysight spectrum
analyzers were specified using the –3 dB bandwidth of the filter. That is, a 10 MHz
Res BW filter was a Gaussian shape with its –3 dB points 10 MHz apart. For certain
types of applications it can be useful to specify the filter width using points other
than the –3 dB points. In the X-Series, the RBW Filter BW function allows you to pick
the filter based on its –3 dB (Normal) bandwidth, its –6 dB bandwidth, its Noise
bandwidth, or its Impulse bandwidth. Note that in all four cases the –3 dB bandwidth
is the same. The filter does not change, but the way you specify it changes.
For example, set the RBW to 1.0 kHz with the RBW Filter BW set to Normal. Now set
the RBW Filter BW to –6 dB. The bandwidth displayed for RBW changes to 1.41 kHz.
The shape and bandwidth of the filter have not changed, only the way the filter is
annotated and the value that appears in the RBW active function area have.
See "More Information" on page 141
Remote Language Compatibility Measurement Application Reference
140
3 RLC Mode & Swept SA Measurement
BW
Command
[:SENSe]:BANDwidth|BWIDth:TYPE DB3|DB6|IMPulse|NOISe
[:SENSe]:BANDwidth|BWIDth:TYPE?
Example
BAND:TYPE NOIS
Preset
Auto Couple chooses the preset value.
State Saved
Saved in instrument state.
Notes
DB3 = –3 dB (Normal)
DB6 = –6 dB
IMPulse = Impulse
NOISe = Noise
Dependencies
Grayed out and displays --- if the Flattop filter type is selected.
When EMC Standard is set to CISPR or MIL, the RBW Filter BW Control is greyed
out and the readback annotation on the key is blanked. This is because the RBW
Filter BW is chosen as appropriate for the filter and the standard and not selected
by thiscontrol. Any attempt to set it otherwise will give an error.
Examples
Filter BW
SCPI Example
Displayed bandwidth of a filter
with 1 kHz -3 dB bandwidth
-3 dB (Normal)
BAND:TYPE DB3
1.0 kHz
–6 dB
BAND:TYPE DB6
1.41 kHz
Noise
BAND:TYPE NOIS
1.06 kHz
Impulse
BAND:TYPE IMP
1.48 kHz
More Information
The analyzer provides four ways of specifying the bandwidth of a Gaussian filter:
1. The –3 dB bandwidth of the filter.
2. The –6 dB bandwidth of the filter.
3. The equivalent Noise bandwidth of the filter, which is defined as the bandwidth
of a rectangular filter with the same peak gain that would pass the same power
for noise signals.
4. The equivalent Impulse bandwidth of the filter, which is defined as the
bandwidth of a rectangular filter with the same peak gain that would pass the
same power for impulsive (narrow pulsed) signals.
141
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
BW
The following figure shows the relationships of the various filter bandwidths for
filters with the X-Series’ shape factor (shape factor is defined as the ratio of the –60
dB bandwidth to the – 3 dB bandwidth):
The Filter Type menu lets you choose the filter bandwidth (–3 dB, –6 dB, Noise or
Impulse) that will be used when specifying the width of the filter. Note that for a
given Gaussian filter, changing the filter bandwidth specification does not affect the
filter width at all but only the means of specifying it. For example, the filter whose –
3 dB bandwidth is 1.0 kHz is the same as the filter whose –6 dB bandwidth is 1.41
kHz, whose Noise bandwidth is 1.06 kHz, and whose Impulse bandwidth is 1.48
kHz. As you cycle through these various filter bandwidths the filter does not
change, but the way the filter is annotated and the value which appears in the
active function area and on the softkey does.
Remote Language Compatibility Measurement Application Reference
142
3 RLC Mode & Swept SA Measurement
Display
Display
The Display Menu lets you configure display items for the current Mode,
Measurement View or Window.
Display Tab
Display Line
Activates an adjustable horizontal line in the Spectrum window that is used as a
visual reference line. The line’s vertical position corresponds to its amplitude value.
The display line can be adjusted using the step keys, knob, or numeric keypad. The
unit of the Display Line is determined by the Y axis unit setting under Amplitude. If
more than one window has a display line, the display line of the selected window is
controlled.
If the display line is off the screen, it shows as a line at the top or bottom of the
screen with an arrow pointing up or down.
The display line is unaffected by Auto Couple.
SCPI
Command
:DISPlay:WINDow[1]:TRACe:Y:DLINe[1]|2|3|4 <ampl>
:DISPlay:WINDow[1]:TRACe:Y:DLINe[1]|2|3|4?
:DISPlay:WINDow[1]:TRACe:Y:DLINe[1]|2|3|4:STATe OFF|ON|0|1
:DISPlay:WINDow[1]:TRACe:Y:DLINe[1]|2|3|4:STATe?
Example
DISP:WIND:TRAC:Y:DLIN:STAT ON Turn Display Line 1 on
DISP:WIND:TRAC:Y:DLIN:STAT3 -32 dBm Set Display line 3 to -32 dBm
Preset
Sets the Display Line to Off and -25 dBm on Preset.
OFF
Couplings
When a value is set for the display line, turn it On.
When the Display Line goes from Off to On, if it is off screen, set it to either the top or
bottom of screen, depending on which direction off screen it was.
The Display Line's value does not change when it is turned off.
State
Saved
Saved in instrument state.
Freq Line
This control affects whichever Freq Line has been selected by the Select Freq Line
control. It activates an adjustable vertical visual reference line on the selected
window. The Freq Line can be adjusted using the step keys, knob, or numeric keypad.
If the Freq Line is off the screen, it shows as a line at the left or right of the screen
with an arrow pointing left or right.
The Freq Line only displays in Swept Spans and is unaffected by Auto Couple.
Command
143
:DISPlay:WINDow[1]:TRACe:X:FLINe[1]|2|3|4 <ampl>
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Display
:DISPlay:WINDow[1]:TRACe:X:FLINe[1]|2|3|4?
:DISPlay:WINDow[1]:TRACe:X:FLINe[1]|2|3|4:STATe OFF|ON|0|1
:DISPlay:WINDow[1]:TRACe:X:FLINe[1]|2|3|4:STATe?
Example
DISP:WIND:TRAC:X:FLIN:STAT ON ! Turn Freq Line 1 on
DISP:WIND:TRAC:X:FLIN3 1 GHz ! Set Freq line 3 to 1 GHz
Preset
Freq Line 1 selected, Off, and set to 1 GHz
State Saved
Saved in instrument state.
Annotation Tab
Graticule
Pressing Graticule turns the display graticule On or Off for all windows with
graticules in all measurements in the current Mode. It also turns the graticule y-axis
annotation on and off.
Command
:DISPlay:GRATicule[:STATe] OFF|ON|0|1
:DISPlay:GRATicule[:STATe]?
Example
DISP:GRAT OFF
Preset
On
State Saved
Saved in instrument state.
Notes
The graticule is the set of horizontal and vertical lines that make up the
grid/divisions for the x-axis and y-axis.
Backwards Compatibility
:DISPlay:WINDow[1]:TRACe:GRATicule:GRID[:STATe] OFF|ON|0|1
:DISPlay:WINDow[1]:TRACe:GRATicule:GRID[:STATe]?
This command is accepted for backwards compatibility with older instruments, but
the WINDow, TRACe and GRID parameters are ignored.
Screen Annotation
This controls the display of the annunciation and annotation around the graticule,
including any annotation on lines (such as the display line, the threshold line, etc.)
and the y-axis annotation, for all windows with screen annotation in all
measurements in the current Mode.
This does NOT include marker annotation (or the N dB result). When off, the graticule
expands to fill the entire graticule area, leaving only the 1.5% gap above the
graticule as described in the Trace/Detector chapter.
Remote Language Compatibility Measurement Application Reference
144
3 RLC Mode & Swept SA Measurement
Display
Command
:DISPlay:ANNotation:SCReen[:STATe] OFF|ON|0|1
:DISPlay:ANNotation:SCReen[:STATe]?
Example
DISP:ANN:SCR OFF
Preset
On
This should remain Off through a Preset when System Settings, User Infterface,
Annotation is set to All Off.
State
Saved
Saved in instrument state.
Notes
Grayed-out and forced to OFF when System Settings, User Infterface, Annotation is
set to All Off.
Trace Annotation
Turns on and off the labels on the traces, showing their detector (or their math mode)
as described in the Trace/Detector section, for all windows in all measurements in
the current Mode for which Trace Annotation on/off is supported.
If trace math is being performed with a trace, then the trace math annotation will
replace the detector annotation.
:DISPlay:ANNotation:TRACe[:STATe] ON|OFF|1|0
Command
:DISPlay:ANNotation:TRACe[:STATe]?
Example
DISP:ANN:TRAC OFF
Preset
OFF
State Saved
Saved in instrument state.
Control Annotation
Turns on and off the display of values on the Active Function controls for all
measurements in the current Mode. This is a security feature.
:DISPlay:ACTivefunc[:STATe] ON|OFF|1|0
Command :DISPlay:ACTivefunc[:STATe]?
Example
DISP:ACT OFF
On
Preset
State
Saved
This should remain Off through a Preset when System Settings, User Infterface,
Annotation is set to All Off.
Saved in instrument state.
Notes
Grayed-out and forced to OFF when System Settings, User Infterface, Annotation is
145
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Display
set to All Off.
Frequency Annotation
This control turns on and off the absolute frequency annotation in the main display
for all windows in all measurements in the current Mode for which Frequency
Annotation on/off is supported.
The affected annotations include Center frequency, Start/Stop frequency,
Frequency Offset, Marker frequency. Any relative frequency annotation such as
Span and Marker Delta are not affected.
The frequency annotations in any other associated display such as in Active
Function, Softkey label, Limit Editor, Amp Corr Editor and Marker Table are not
changed.
Frequency annotations that are not associated with the spectrum such as RBW,
IBW, Sweep Time are excluded and they are shown regardless of this selection.
Command
:DISPlay:ANNotation:FREQuency[:STATe] ON|OFF|1|0
:DISPlay:ANNotation:FREQuency[:STATe]?
Example
DISP:ANN:FREQ OFF
Preset
On
Meas Bar
This function turns the Measurement Bar at the top of the screen on and off for all
measurements in the current Mode. When off, the graticule area expands to fill the
area formerly occupied by the Measurement Bar. This is the measurement bar.
Command
:DISPlay:ANNotation:MBAR[:STATe] OFF|ON|0|1
:DISPlay:ANNotation:MBAR[:STATe]?
Example
DISP:ANN:MBAR OFF
Preset
On
This should remain Off through a Preset when System Display Settings, Annotation is set
to Off
State
Saved
Saved in instrument state.
Notes
Grayed-out and forced to OFF when System Display Settings, Annotation is set to
Off.
RLC Swept SA Views
The RLC Swept SA measurement has only one view ("Normal" on page 147).
Remote Language Compatibility Measurement Application Reference
146
3 RLC Mode & Swept SA Measurement
Display
Some views are multiple-window views. When in a multiple window view, you select
a window by touching it. The menu controls may sometimes change depending on
which window is selected.
Whenever the view changes, the default menu is Frequency, unless otherwise
specified in the view description.
For details of the User View-related controls in this menu, see the descriptions under
the "View Editor" on page 89.
SCPI
Command
Not available in N9061C
Dependencies
All views except NORMal require option EDP to be licensed. If the SCPI is sent to
select any other view and EDP is not licensed, an error “Option not available” is
generated.
Preset
NORMal
State Saved
Saved in instrument state
Normal
Single window view of the frequency domain or zero span. This is the classic SA view.
This is also the view into which the instrument switches whenever you do anything
that causes the frequency limits to change, for example:
– If you switch inputs (for example, if you switch from the RF Input to External
Mixing)
– If, while in External Mixing, you edit the Harmonic Table
– If, while in External Mixing, the Mixer Preset changes (for example, if you change
from A-band to V-band etc)
For N9061C, this is the only available view, and it has only one window: "Spectrum"
on page 109.
147
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Frequency
Frequency
Opens a menu that enables you to control the Frequency and Channel parameters
of the instrument.
Settings Tab
Center Frequency
Pressing Center Freq sets the frequency that corresponds to the horizontal center of
the graticule (when frequency Scale Type is set to linear). While adjusting the Center
Frequency the Span is held constant, which means that both the Start Frequency
and Stop Frequency will change.
The Center Freq function sets (and queries) the Center Frequency for the currently
selected input. If your analyzer has multiple inputs, and you select another input, the
Center Freq changes to the value for that input and the value is remembered as you
go from input to input.
The instrument Min and Max values depend on instrument maximum frequency,
mode, measurement, and selected input.
Remote
Command
[:SENSe]:FREQuency:CENTer <freq>
Example
FREQ:CENT 50 MHz
[:SENSe]:FREQuency:CENTer?
FREQ:CENT?
REQ:CENT UP changes the center frequency to 150 MHz if you use FREQ:CENT:STEP 100
MHz to set the center frequency step size to 100 MHz
Preset
Depends on instrument maximum frequency, mode, measurement, and selected input.
State
Saved
Saved in instrument state.
Notes
This command sets either the RF or the I/Q Center Frequency depending on the
selected input.
For RF input it is equivalent to FREQ:RF:CENT
For I/Q input it is equivalent to FREQ:IQ:CENT
Preset and Max values are dependent on Hardware Options (5xx)
If no terminator (e.g. MHz) is sent the terminator Hz is used. If a terminator with unit
other than Frequency is used, an invalid suffix error message is generated.
Dependencies
The Center Frequency can be limited by Start or Stop Freq limits, if the Span is so
large that Start or Stop reach their limit
Couplings
When operating in “swept span”, any value of the Center Frequency or Span that is
Remote Language Compatibility Measurement Application Reference
148
3 RLC Mode & Swept SA Measurement
Frequency
within the frequency range of the analyzer is allowed when the value is being set
through the front panel numeric key pad or the SCPI command. The other
parameter is forced to a different value if needed, to keep the Start and the Stop
Frequencies within the analyzer’s frequency range
Span
Changes the displayed frequency range symmetrically about the center frequency.
While adjusting the Span the Center Frequency is held constant, which means that
both Start Frequency and Stop Frequency will change.
Span also sets the frequency entry mode to Center/Span. In Center/Span mode, the
center frequency and span values are displayed below the graticule, and the default
active function in the Frequency menu is Center Freq.
The Span control also includes a toggle switch to go back and forth between Swept
Span and Zero Span. Zero Span is a special sweep type in which the analyzer stops
sweeping over a range of frequencies and stays at the Center Frequency. In Zero
Span, the analyzer sweeps in the time domain, showing you the instantaneous
amplitude versus time at the Center Frequency. For more about Zero Span, see the
Zero Span section. Selecting Swept Span places the analyzer in Center/Span
frequency entry mode.
While in swept spans, setting the span to 0 Hz through SCPI or the front panel
numeric key pad puts the analyzer into zero span. However, using the Step keys and
the RPG in swept spans, the Span can only go as far down as 10 Hz and cannot be
set to zero.
When in Zero Span you can return to your last Swept Span by pressing the Swept
Span/Zero Span toggle on the Span control. This replaces the “Last Span” function
found on older HP/Agilent/Keysight Analyzers.
We use the term “Swept Span” to mean spans other than zero span, even though
sometimes when we are in what we call a “swept span” we might be performing an
FFT-style sweep, which is not a true “swept span”.
If the Span is set to a value greater than the maximum allowable span of the
instrument, an error message is generated indicating the data is out of range and
was clipped to upper limit.
Remote
Command
[:SENSe]:FREQuency:SPAN <freq>
Example
FREQ:SPAN 2GHz sets the span to 2 GHz
[:SENSe]:FREQuency:SPAN?
FREQ:SPAN 0 Hz sets the span to 0 Hz and puts the instrument in Zero Span
Couplings
Span affects RBW, sweeptime, FFT & Sweep choice (including FFT Width, Phase
Noise Optimization and ADC Dither auto couplings.)
When operating in “swept span”:
149
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Frequency
– When using the knob or the step up/down keys or the UP |DOWN keywords in
SCPI, the value that is being changed i.e. the Center Frequency or Span, is
limited so that the other parameter is not forced to a new value.
– Any value of the Center Frequency or Span that is within the frequency range of
the analyzer is allowed when the value is being set through the front panel
numeric keypad or the SCPI command. The other parameter is forced to a
different value if needed, to keep the Start and the Stop Frequencies within the
analyzer’s frequency range.
– The Span cannot be set to Zero by setting Start Frequency = Stop Frequency.
The value of the last setting will be changed to maintain a minimum value of 10
Hz for the difference between start and stop frequencies.
Zero Span
While in Swept Span, pressing the Swept Span/Zero Span toggle on the Span
control puts you in Zero Span. You can also go to Zero Span by setting the span to 0
Hz through SCPI or the front panel numeric key pad. However, you cannot go to
Zero Span by setting Start freq = Stop freq using the numeric keypad, nor by using
the Step keys and the RPG to “roll” down to zero, the Span can only go as far down
as 10 Hz using this means.
Example
FREQ:SPAN 0 Hz sets the span to zero, switches to Zero Span
Sending FREQ:SPAN 1 MHz while in Zero Span, switches to Swept span
Dependencies
If the Zoomed Trace window is present, Zero Span is not allowed.
If the Zone Spectrum window is present, Zero Span is not allowed in the Spectrum
window
Couplings
Switching to Zero Span:
• Turns off Signal Track
• Turns off the auto-coupling of RBW and sweep time
• Places the analyzer in Center/Span frequency entry mode
"Swept Span v.s. Zero Span" on page 150
Swept Span v.s. Zero Span
When you enter Zero Span, the analyzer changes the displayed frequency span to 0
Hz. The horizontal axis changes to time rather than frequency. The amplitude
displayed is the input signal level at the current center frequency. This is a timedomain mode that changes several measurement functions and couplings. The
instrument behavior is similar to an oscilloscope with a frequency selective detector
installed in front of the oscilloscope. See Application Note 150 for more information
on how to use zero span.
While in zero span, setting the Span to a non-zero value through SCPI or Front
Panel puts the analyzer back into Swept Span. You can also return to your last
Remote Language Compatibility Measurement Application Reference
150
3 RLC Mode & Swept SA Measurement
Frequency
Swept Span by pressing the Swept Span/Zero Span toggle on the Span control. This
replaces the “Last Span” function found on older HP/Agilent/Keysight Analyzers.
The following table summarizes the differences between Zero Span and Swept
Spans:
Zero Span
Swept Spans
X axis is time
X axis is frequency
There is no auto-RBW selection unless the EMC
Standard is CISPR or MIL
RBW coupled to Span when RBW is in
auto
There is no auto sweep time
Sweep time is coupled to RBW when
sweep time in auto
Interval Power is calculated in the Marker function
Band Power is calculated in Marker
function
You can only define time limits when in zero span
You can only define frequency limits when
in swept SA
Marker Count counts at the center frequency
Marker Count counts at the marker
frequency
CF Step Size set to RBW value
CF Step autocouples to 10% of Span
Some “Marker ->” commands are not available
Other “Marker ->” commands are not
available
Freq entry mode is always Center/Span
Freq entry mode can be Center/Span or
Start/Stop
N dB points reports a time difference
N dB points reports a frequency difference
Full Span
Changes the frequency span of the analyzer to the Preset frequency span of the
analyzer and sets the Frequency entry mode to Center/Span.
The span is dependent on the currently selected Input (see the Section
“Input/Output”). For example, when using external mixing, it changes the frequency
to the Preset frequency range specified for the selected external mixing band.
Pressing this key while in zero span puts the analyzer back in swept span.
Command
[:SENSe]:FREQuency:SPAN:FULL
Example
FREQ:SPAN:FULL sets the span to full frequency range of the analyzer
Couplings
Turns off signal tracking (span zoom). It does NOT turn off the markers, nor the
current active function.
Start Freq
Sets the frequency at the left side of the graticule. While adjusting the start
frequency, the stop frequency is held constant, which means that both the center
151
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Frequency
frequency and span will change.
Start Freq also sets the frequency entry mode to Start or Stop. In Start or Stop
mode, the start frequency and stop frequency values are displayed below the
graticule, and the default active function in the Frequency menu is Start Freq.
Preset and Max values are dependent on hardware options.
Command
[:SENSe]:FREQuency:STARt <freq>
[:SENSe]:FREQuency:STARt?
Example
FREQ:STAR 220 MHz
FREQ:STAR?
Preset
Start Freq does not preset. On Mode Preset, Span & CF preset, and Start Freq is derived.
On a Meas Preset only Span presets, CF does not, so Start Freq will vary depending on
CF.
When a Mode Preset is performed while in External Mixing, the Start frequency of the
current Mode is set to the nominal Min Freq of the lowest harmonic range in the
Harmonic Table for the current mixer setup.
If the current measurement has a limited Span available to it, and cannot achieve the
Span shown in the table (Span=Stop Freq – Start Freq), the analyzer uses the maximum
Span the measurement allows, and sets the Center Freq to the midpoint of the Start and
Stop Freq values in the Harmonic Table. Thus, in this case, the Start Freq will preset to a
frequency below the preset Center Freq by ½ of the maximum Span.
When Restore Input/Output Defaults is performed, the mixer presets to the 11970A,
whose Start frequency is 26.5 GHz.
Therefore, after a Restore Input/Output Defaults, if you go into External Mixing and do a
Mode Preset while in the Spectrum Analyzer Mode, the resulting Start Freq is 26.5 GHz.
Min/Max
Min:-80 MHz, unless Source Mode is set to Tracking, in which case it is limited by the
minimum frequency of the Source.
If the knob or step keys are being used, depends on the value of the other three
interdependent parameters.
While in External Mixing, the minimum Start Freq you can set is determined by the
external mixing parameters. It will be close to the minimum LO frequency (3.8 GHz if
undoubled, 8.6 GHz if doubled) times the harmonic number, for the lowest harmonic
range in the Harmonic Table for the current mixer setup. It can be queried with the SCPI
command :FREQ:STARt? MIN.
Max:Depends on the instrument maximum frequency – 10 Hz. Note that, if the Source
Mode is set to Tracking, the effective instrument maximum frequency may be limited by
the source maximum frequency.
If the knob or step keys are being used, it depends on the value of the other three
interdependent parameters.
While in External Mixing, the maximum Start Freq you can set is determined by the
external mixing parameters. It will be close to the maximum LO frequency (7 GHz if
undoubled, 14 GHz if doubled) times the harmonic number, for the highest harmonic
range in the Harmonic Table for the current mixer setup. It can be queried with the SCPI
command :FREQ:STARt? MAX.
State
Saved
Saved in instrument state
Remote Language Compatibility Measurement Application Reference
152
3 RLC Mode & Swept SA Measurement
Frequency
Dependencies
By direct entry:
You cannot set the Stop frequency < Start frequency. You cannot set Start
frequency = Stop frequency. You cannot select zero span by setting Start = Stop.
You cannot set Stop Frequency to a value that would create a span of less than 10
Hz. If you try to do any of these, Start Frequency will change to maintain a minimum
value of 10 Hz for the difference between Start and Stop
With the knob or step keys:
Cannot decrement Stop Freq to a value less than Start Freq + 10 Hz. If already in
zero span, cannot decrement at all, and the first increment will be forced to at least
10 Hz.
The Stop Frequency can be limited by Span limits, if the Start Frequency is above its
preset value.
If the electronic/soft attenuator is enabled, any attempt to set the Stop Frequency
>3.6 GHz fails and results in an advisory message. If the equivalent SCPI command
is sent, this same message is generated as part of a “-221, Settings conflict”
warning.
If Source Mode is set to Tracking, and the Max or Min Stop Freq is therefore limited
by the limits of the source, a warning message is generated -222.2001, “Data out of
range;clipped to source max/min” if these limits are exceeded. Note that for an
external source, these limits can be affected by the settings of Source Numerator,
Source Denominator and Power Sweep.
Couplings
In the Spectrum Analyzer, the four parameters Center Freq, Start Freq, Stop Freq
and Span are interdependent, as changing one necessarily affects one or more of
the others. The couplings between Center Freq and Span are detailed under the
key descriptions for those keys. These couplings also affect Start Freq and Stop
Freq.
You cannot set Start frequency = Stop frequency. You cannot select zero span by
setting Start = Stop. The instrument will alter the value of the last setting to
maintain a minimum value of 10 Hz for the difference between Start and Stop.
Stop Freq
Sets the frequency at the right side of the graticule. While adjusting the stop
Frequency, the start frequency is held constant, which means that both the center
frequency and span will change.
Stop Freq also sets the frequency entry mode to Start or Stop. In Start or Stop mode,
the start frequency and stop frequency values are displayed below the graticule, and
the default active function in the Frequency menu is Start Freq.
Command
[:SENSe]:FREQuency:STOP <freq>
[:SENSe]:FREQuency:STOP?
153
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Frequency
Example
FREQ:STOP 220 MHz
FREQ:STOP?
Preset
On Mode Preset, Span and CF preset, and Stop Freq is derived.
If the current measurement has a limited Span available to it, and cannot achieve the
Span shown in the table (Span=Stop Freq – Start Freq), the analyzer uses the maximum
Span the measurement allows, and sets the Center Freq to the midpoint of the Start and
Stop Freq values in the Harmonic Table. Thus, in this case, the Stop Freq will preset to a
frequency above the preset Center Freq by ½ of the maximum Span.
When Restore Input/Output Defaults is performed, the mixer presets to the 11970A,
whose Stop frequency is 40 GHz.
Therefore, after a Restore Input/Output Defaults, if you go into External Mixing and do a
Mode Preset while in the Spectrum Analyzer Mode, the resulting Stop Freq is 40 GHz.
State
Saved
Saved in instrument state.
Min
-79.999999999 MHz, unless Source Mode is set to Tracking, in which case it is
limited by the minimum frequency of the Source
If the knob or step keys are being used, depends on the value of the other three
interdependent parameters.
While in External Mixing, the minimum Stop Freq you can set is determined by the
external mixing parameters. It will be close to the minimum LO frequency (3.8 GHz if
undoubled, 8.6 GHz if doubled) times the harmonic number, for the lowest
harmonic range in the Harmonic Table for the current mixer setup. It can be queried
with the SCPI command :FREQ:STOP? MIN.
Max
Depends on instrument maximum frequency. Note that, if the Source Mode is set to
Tracking, the effective instrument maximum frequency may be limited by the source
maximum frequency.
If the knob or step keys are being used, depends on the value of the other three
interdependent parameters.
While in External Mixing, the maximum Stop Freq you can set is determined by the
external mixing parameters. It will be close to the maximum LO frequency (7 GHz if
undoubled, 14 GHz if doubled) times the harmonic number, for the highest
harmonic range in the Harmonic Table for the current mixer setup. It can be queried
with the SCPI command :FREQ:STOP? MAX.
Dependencies
By direct entry:
You cannot set the Stop frequency < Start frequency. You cannot set Start
frequency = Stop frequency. You cannot select zero span by setting Start = Stop.
You cannot set Stop Frequency to a value that would create a span of less than 10
Hz. If you try to do any of these, Start Frequency will change to maintain a minimum
value of 10 Hz for the difference between Start and Stop
Remote Language Compatibility Measurement Application Reference
154
3 RLC Mode & Swept SA Measurement
Frequency
With the knob or step keys:
Cannot decrement Stop Freq to a value less than Start Freq + 10 Hz. If already in
zero span, cannot decrement at all, and the first increment will be forced to at least
10 Hz.
The Stop Frequency can be limited by Span limits, if the Start Frequency is above its
preset value.
If the electronic/soft attenuator is enabled, any attempt to set the Stop Frequency
>3.6 GHz fails and results in an advisory message. If the equivalent SCPI command
is sent, this same message is generated as part of a “-221, Settings conflict”
warning.
If Source Mode is set to Tracking, and the Max or Min Stop Freq is therefore limited
by the limits of the source, a warning message is generated -222.2001, “Data out of
range;clipped to source max/min” if these limits are exceeded. Note that for an
external source, these limits can be affected by the settings of Source Numerator,
Source Denominator and Power Sweep.
Couplings
In the Spectrum Analyzer, the four parameters Center Freq, Start Freq, Stop Freq
and Span are interdependent, as changing one necessarily affects one or more of
the others. The couplings between Center Freq and Span are detailed under the
key descriptions for those keys. These couplings also affect Start Freq and Stop
Freq.
You cannot set Start frequency = Stop frequency. You cannot select zero span by
setting Start = Stop. The instrument will alter the value of the last setting to
maintain a minimum value of 10 Hz for the difference between Start and Stop
Auto Tune
Auto Tune is an immediate action control. When it is pressed, it causes the analyzer
to change Center Frequency to the strongest signal in the tunable span of the
analyzer, excluding the LO. It is designed to quickly get you to the most likely signal
(s) of interest, with no signal analysis knowledge required. As such, there are no
configurable parameters for this feature. There are only preselected values that
work in most real world situations.
Auto Tune performs a Preset as part of its function, so it always returns you to the
Normal View and a preset state, although it does leave the AC/DC coupling and
Single/Cont state unaffected.
You will see an hourglass, and you may see a slight pause, until the signal of interest
is presented at mid-screen.
Command
[:SENSe]:FREQuency:TUNE:IMMediate
Example
FREQ:TUNE:IMM
Dependencies
If the Zoomed Trace or Zone Spectrum window is present, Auto Tune is not present.
Auto Tune is not available (grayed out) when Source Mode=Tracking.
155
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Frequency
CF Step
Changes the step size for the center frequency and start and stop frequency
functions. Once a step size has been selected and the center frequency function is
active, the step function (and the UP|DOWN parameters for Center Frequency from
remote commands) changes the center frequency by the step-size value. The step
size function is useful for finding harmonics and sidebands beyond the current
frequency span of the analyzer.
Note that the start and stop frequencies also step by the CF Step value.
Preset and Max values are dependant on hardware options.
Command
[:SENSe]:FREQuency:CENTer:STEP[:INCRement] <freq>
[:SENSe]:FREQuency:CENTer:STEP[:INCRement]?
[:SENSe]:FREQuency:CENTer:STEP:AUTO OFF|ON|0|1
[:SENSe]:FREQuency:CENTer:STEP:AUTO?
Example
FREQ:CENT:STEP:AUTO ON
FREQ:CENT:STEP 500 MHz FREQ:CENT UP increases the current center frequency value
by 500 MHz
FREQ:CENT:STEP?
FREQ:CENT:STEP:AUTO?
Preset
Auto
ON
Min/Max
Min:– (the maximum frequency of the instrument). That is, 27 GHz max freq instrument
has a CF step range of +/- 27 GHz. Note that this is the maximum frequency given the
current settings of the instrument, so in External Mixing, for example, it is the maximum
frequency of the current mixer band.
Max:the maximum frequency of the instrument. That is, 27 GHz max freq instrument has a
CF step range of +/- 27 GHz. Note that this is the maximum frequency given the current
settings of the instrument, so in External Mixing, for example, it is the maximum
frequency of the current mixer band.
State
Saved
Saved in instrument state.
Dependencies
Span, RBW, Center frequency
If the electronic/soft attenuator is enabled, any attempt to change the value of the
center frequency >3.6 GHz by pressing the Up-arrow key, fails and results in an
advisory message. If the equivalent SCPI command is sent, this same message is
generated as part of a “-221, Settings conflict” warning.
Couplings
When auto-coupled in a non-zero span, the center frequency step size is set to
10% of the span. When auto-coupled in zero span, the center frequency step size is
set to the equivalent -3 dB RBW value.
Remote Language Compatibility Measurement Application Reference
156
3 RLC Mode & Swept SA Measurement
Frequency
Freq Offset
Enables you to set a frequency offset value to account for frequency conversions
outside of the analyzer. This value is added to the display readout of the marker
frequency, center frequency, start frequency, stop frequency, and all other absolute
frequency settings in the analyzer including frequency count. When a frequency
offset is entered, the value appears below the center of the graticule. To eliminate
an offset, perform a Mode Preset or set the frequency offset to 0 Hz.
Preset and Max values are dependent on the hardware options.
Command
[:SENSe]:FREQuency:OFFSet <freq>
[:SENSe]:FREQuency:OFFSet?
Example
FREQ:OFFS 10 MHz
Min/Max
-500 GHz/500 GHz
State Saved
Saved in instrument state.
Dependencies
Freq Offset is not available in External Mixing. In this case Freq Offset is grayed out
and shows a value of zero. However, the value of CF Offset that was set for the RF
Input is retained and restored when the user switches back to the RF Input.
Backwards Compatibility
Command
DISPlay:WINDow[1]:TRACe:X[:SCALe]:OFFSet
The DISPlay version of the command is in the instrument for compatibility across
platforms and is not recommended for new development.
Notes
1. In pre-X-Series instruments, Frequency Offset could not be adjusted by the knob or
step keys. That is no longer the case.
2. Some previous spectrum analyzers did not adjust frequency counter results for the
Frequency Offset. The X-Series does adjust the frequency counter for the offset.
More Information
This command does not affect any bandwidths or the settings of relative frequency
parameters such as delta markers or span. It does not affect the current hardware
settings of the analyzer, but only the displayed frequency values. Entering an offset
does not affect the trace position or display, just the value of the start and stop
frequency and the values represented by the trace data. The frequency values of
exported trace data, queried trace data, markers, trace data used in calculations
such as N dB points, trace math, etc., are all affected by Freq Offset. Changing the
offset, even on a trace that is not updating will immediately change all of the above,
without taking new data needing to be taken.
If a trace is exported with a nonzero Freq Offset, the exported data will contain the
trace data with the offset applied. Therefore, if that trace were to be imported back
into the analyzer, you would want Freq Offset to be 0, or the offset would be
applied again to data which is already offset. No such care need be taken when
saving a State+Trace file because the data and state are saved together.
157
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Frequency
X Axis Scale
Selects either linear or logarithmic scaling for the frequency axis.
The scaling can be changed at any time and determines only how the data is
displayed; it has no impact on the actual sweep or measurement of trace data (with
the exception that the detector auto-rules never select the Normal detector while in
Log Scale Type). Changing the scaling does not restart the sweep (unless the
detector changes) and has no impact on the number of sweep points. The scaling
can be changed while traces are in View and they will scale appropriately. Markers
stay at their set frequency, so they may move on the display.
Note that the actual trace data does not change as you go between Log and Linear
Scale Type; hence trace data saved while the display is in log will look identical to
trace data saved while the display is in linear. When recalling trace data, the current
value of Scale Type is used to display the data. (Trace +State files will of course
recall with whatever Scale Type setting was in effect when they were saved, since
the State is saved with them).
This function has no effect on the zero span display, although it is available while in
zero span.
See "More Information" on page 159
Command
:DISPlay:WINDow[1]:TRACe:X[:SCALe]:SPACing LINear|LOGarithmic
:DISPlay:WINDow[1]:TRACe:X[:SCALe]:SPACing?
Example
DISP:WIND:TRAC:X:SPAC LOG
Preset
LIN
State Saved
Saved in instrument state.
Dependencies
Has no effect in Zero Span, but if changed while in Zero Span then it will be
changed on returning to nonzero span.
The Normal detector will never be selected by the detector auto-rules while in Log,
the rules select Sample if Normal would have been selected.
Couplings
In Linear the Frequency controls and notation at the bottom of the screen default to
Center/Span. In Log they default to Start/Stop. When switching from Linear to Log,
the notation at the bottom of the screen changes to Start/Stop, and.if the active
function was one of the frequency controls (Center Freq, Start Freq, Stop Freq, or
Span), it changes to Start Freq. When switching from Log to Linear, the notation at
the bottom of the screen changes to Center/Span, and if the active function was
one of the frequency controls (Center Freq, Start Freq, Stop Freq, or Span), it
changes to Center Freq.
When switching to Log, if the Start Frequency is 0 Hz it is changed to 10 Hz.
Backwards Compatibility
Unlike the similar feature in the ESA-Series and E7400 series analyzer, this function
Remote Language Compatibility Measurement Application Reference
158
3 RLC Mode & Swept SA Measurement
Frequency
has no impact on the way data is gathered or stored in the analyzer (other than the
change to detector auto-coupling), it is simply a scaling function that determines
how the data will be displayed. Therefore trace data saved or queried while in log
will generate exactly the same files as when in linear (assuming the same detector
is used); this is not the case in the legacy analyzers. Nor is the number of sweep
points affected in any way by this function, as it was in the legacy analyzers.
Command
[:SENSe]:SWEep:SPACing LINear|LOGarithmic
More Information
The log graticule is drawn to optimize the display based on the range of frequencies
being shown. The center frequency is marked with a small triangle at the top and
bottom of the display, regardless of whether the scaling is log or linear.
Center Freq mark in Linear Scale Type is in the center of the display:
Center Freq mark in Log Scale Type is to the right of center:
159
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Frequency
Signal Track
When Marker 1 is placed on a signal and Signal Track is pressed, the marker remains
on the signal while the analyzer retunes the center frequency to the marker
frequency. The analyzer keeps the signal at the center of the display, as long as the
amplitude of the signal does not change by more than +/–3 dB from one sweep to
another. If Marker 1 is not in Normal or Delta, turning on Signal Track sets it to
Normal, perform a peak search, and centers the marker on the display.
Command
:CALCulate:MARKer:TRCKing[:STATe] OFF|ON|0|1
:CALCulate:MARKer:TRCKing[:STATe]?
Example
CALC:MARK:TRCK ON turns on Signal Track using Marker 1.
CALC:MARK:TRCK?
Preset
OFF
State Saved
Saved in instrument state.
Dependencies
Signal Track is not available (grayed out) when the Waterfall window is present.
Signal Track is associated with Marker 1. When marker 1 is turned off or set to
Fixed, signal track is turned off as well.
Signal Track is not available (grayed out) when Source Mode=Tracking.
Signal Track is not available (grayed out) when Signal ID = on.
Remote Language Compatibility Measurement Application Reference
160
3 RLC Mode & Swept SA Measurement
Frequency
Signal Track and Continuous Peak Search cannot be used with each other. If one is
on, the other is grayed out.
Signal Track is grayed out if in Zero Span.
But if Zero Span is entered while in Signal Track, Signal Track is turned off.
Signal Track can only function properly if the trace Marker 1 is on is updating.
Therefore if Signal Track is on and the trace Marker 1 is on is put into View, Signal
Track is turned off and the Signal Track key grayed out. Whenever the trace Marker
1 is on is not updating, the Signal Track key is grayed out.
Signal Track is only available in the Swepts SA measurement.
Couplings
Signal Track can only function properly if the trace Marker 1 is on, is in Trace Update
= Active. Therefore if the trace Marker 1 is on is in Update Off when Signal Track is
turned on, it is changed to Update On. If the trace Marker 1 is on is set to Update Off
while Signal Track is on, it turns off Signal Track.
Backwards Compatibility Notes
1. Signal Track is now in the Span menu. It was located in the Frequency menu in
ESA and PSA, under its own hardkey in 859xA, under Marker Function (and
called Marker Track) in 859xB/C/D/E. It was placed in Span in the X-Series
because of the value that one of Signal Track’s features, Auto Zoom, provides
when changing span (see below).
2. In ESA and PSA the Span Zoom key (in the Span menu) turned on Signal Track in
order to let the user enter a new span with Auto Zoom on; by putting Signal
Track into the Span menu we achieve the same functionality more clearly.
Hence Span Zoom is eliminated as a separate function. There never was a
remote command for Span Zoom so there are no SCPI issues with this.
3. Signal Track now obeys the Excursion and Threshold criteria, allowing the user
to control the search better; but this may cause low level signals that could
previously be tracked to need the Excursion and Threshold adjusted.
4. Signal Track is now bound to only Marker 1, and cannot be enabled for any
other marker. ESA/PSA allowed a subopcode to specify the marker to use. In XSeries, no subopcode is allowed and the marker is always assumed to be
marker 1.
5. Signal Track now turns off when it finds an unstable signal. In the past it kept
searching which caused inpredictable results.
More Information
If marker 1 is off when Signal Track is turned on, marker 1 is turned on in the center
of the screen and a peak search is performed. If marker 1 is already on, it stays on
and is used where it is. If it is Fixed, it is set to Normal.
161
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Frequency
If you move the marker during Signal Track, a Mkr-> CF is performed and the signal
track function starts over.
If the signal is lost, an attempt will be made to find it again and continue tracking. If
there are other signals on screen that are near the same amplitude, one of them
may be found instead since the algorithm is seeking a signal with amplitude similar
to the amplitude of the original signal
Signals near 0 Hz cannot be tracked effectively as they cannot be distinguished
from the LO feed-through, which is excluded by intent from the search algorithm.
As a speed optimization, the center frequency is only changed if it differs from the
marker position by 1% or more of the span.
If the analyzer is in Single Sweep and Signal Track is turned on, then nothing
happens until a sweep is actually initiated (i.e. by an INIT:IMM or Single key press,
and a trigger). Once the sweep is initiated, the entire set of sweeps necessary to
complete a pass through the signal track algorithm ensues before the analyzer
returns *OPC true, returns results to a READ or MEASure, or returns to the idle
state.
If the span is changed while in Signal Track, either by you or because moving the
instrument to the signal’s frequency results in Span Limiting (as described under
the Frequency key), an “auto-zoom” algorithm is executed to get to the new span
without losing the signal. In “auto zoom”, the span is reduced in stages, with a
sweep between each stage. You will see this zooming occur as each sweep is
performed, and the new span is set.
When auto-zooming, the set of steps necessary to achieve the target span is to be
considered a “measurement,” thus the entire process executes even if the analyzer
is in single sweep. *OPC will not return true until the process is complete nor will
results be returned to a READ or MEASure command. Note further that if the
analyzer is in a measurement such as averaging when this happens, the act of
changing the span restarts averaging but the first average trace is the last trace of
the auto zoom.
When you increase the span, we go directly to the new span. No zooming is
required.
This function is intended to track signals with a frequency that is changing (drifting),
and an amplitude that is not changing. It keeps tracking if you are in continuoussweep mode. If in single-sweep mode, as described above, the analyzer only does
one center frequency adjustment as necessary.
Remote Language Compatibility Measurement Application Reference
162
3 RLC Mode & Swept SA Measurement
Input/Output
Input/Output
The Input/Output key accesses menus that let you control the Input/Output
parameters of the instrument. In general, these are functions associated with
external connections to the analyzer, either to the inputs or the outputs.
Since the Input/Output connections tend to be based on how you have your
hardware set up, in general the input/output settings do not change when you
perform a Mode Preset. They can be set to their default value in one of the three
ways:
– by using the Input/Output Preset control on the Input panel of the InputOutput
menu,
– by using the System->Restore System Defaults->Input/Output Settings or,
– by using the System -> Restore System Defaults->All. Also, they survive a Preset
and a Power cycle.
A very few of the Input/Output settings do respond to a Mode Preset. For example, if
the Calibrator is on it turns off on a Preset, and if DC coupling is in effect it switches
to AC on a Preset. These exceptions are made in the interest of reliability and
usability, that overrides the need for absolute consistency.
The Input/Output features are common across multiple Modes and Measurements.
In general they do not change when you change Modes or Measurements, although
some controls appear only in certain measurement.
Input Tab
Select Input
Select Input lets you choose which signal input you want to analyze.
Command
[:SENSe]:FEED RF|AIQ|EMIXer
[:SENSe]:FEED?
Example
:FEED RF selects the RF Input
:FEED:EXT selects external Mixing
:FEED?
Preset
This setting is unaffected by a Preset or power cycle. It survives a Mode Preset and mode
changes.
It is set to RF on a "Restore Input/Output Defaults" or "Restore System Defaults->All"
State
Saved
Saved in instrument state.
RF Input
Selects the front-panel RF input port to be the analyzer signal input. If RF is already
selected, pressing this control accesses the RF input setup functions.
External Mixer (requires Option EXM)
163
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Input/Output
This selection allows you to choose an External Mixer through which to apply signal
input to the analyzer. When chosen, the LO/IF port becomes the input to the
analyzer.
External Mixing requires option EXM. External Mixer will not appear unless option
EXM is installed. The presence of the LO/IF connector alone does not indicate that
you have Option EXM licensed. To verify that option EXM is installed, press System,
Show, System. See "More Information on External Mixer" on page 168.
IQ (requires Option BBA)
Selects the front-panel I/Q input ports to be the analyzer signal input. If I/Q is
already selected, pressing this key accesses the I/Q setup menu.
The Baseband I/Q functionality is a hardware option. It is option BBA. If the option is
not installed, none of the I/Q functionality is enabled.
The Baseband I/Q has four input ports and one output port. The input ports are I, Ibar, Q, and Q-bar. The I and I-bar together compose the I channel and the Q and Qbar together compose the Q channel. Each channel has two modes of operation,
Single-Ended (also called "unbalanced") and Differential Input (also called
"balanced"). When in Single-Ended operation, only the main port (I or Q) is used and
the complementary port (I-bar or Q-bar) is ignored. When in Differential Input
mode, both main and complementary ports are used.
The input settings (range, attenuation, skew, impedance, external gain) apply to
the channels, not the individual ports.
The system supports a variety of 1 MΩ input passive probes as well as the Keysight
113x Series active differential probes using the Infinimax probe interface.
The Keysight 113x Series active probes can be used for both single ended and
differential measurements. In either case a single connection is made for each
channel (on either the I or Q input). The input is automatically configured to 50Ω
single ended and the probe power is supplied through the Infinimax interface. The
probe can be configured for a variety of input coupling and low frequency rejection
modes. In addition, a wide range of offset voltages and probe attenuation
accessories are supported at the probe interface. The active probe has the
advantage that it does not significantly load the circuit under test, even with unity
gain probing.
With passive 1 MΩ probes, the probe will introduce a capacitive load on the circuit,
unless higher attenuation is used at the probe interface. Higher attenuation
reduces the signal level and degrades the signal-to-noise-ratio of the
measurement. Passive probes are available with a variety of attenuation values for
a moderate cost. Most Keysight passive probes can be automatically identified by
the system, setting the input impedance setting required as well as the nominal
attenuation. For single ended measurements a single probe is used for each
channel. Other passive probes can be used, with the attenuation and impedance
settings configured manually.
For full differential measurements, the system supports probes on each of the four
inputs. The attenuation of the probes should be the same for good common mode
rejection and channel match.
Remote Language Compatibility Measurement Application Reference
164
3 RLC Mode & Swept SA Measurement
Input/Output
Both active and passive probes in single ended and differential configurations can
be calibrated. This calibration uses the Cal Out BNC connection and a probe
connection accessory. The calibration achieves excellent absolute gain flatness in
a probed measurement. It matches both the gain and frequency response of the I
and Q channels as well as any delay skew, resulting in high accuracy in derived
measurements such as Error Vector Magnitude (EVM).
When a probe is connected a status message will be displayed. The message will
indicate if calibration data is available or not. Calibration data is saved for each type
of probe (including "none") for each port and will be reapplied whenever that type of
probe is re-connected to the same port. For probes with EEPROM identification, the
calibration data will be stored based on the unique probe identifier and will reapply
data for that particular probe if it is available. The data will not follow a probe from
one port to another. For probes without EEPROM identification, the instrument
cannot distinguish between different probes of the same type and it will use the
data from the last calibration for that probe type on that port.
When in differential mode, both the main and complementary probes are expected
to be of the same type.
In some situations, the I and Q channels should be configured identically. In other
situations it is convenient to control them independently. Some menus have a "Q
Same as I" setting that will cause the Q channel configuration to mirror the I
channel configuration, avoiding the overhead of double data entry when the
channels should be the same.
The output port is for calibrating the I/Q input ports, although it can also be
manually controlled.
There are two types of calibrations available: cable calibration and probe
calibration. The cable calibration will guide the user through connecting each input
port in turn. All ports must be calibrated together. The probe calibration is done for
a specific channel (I or Q). If in Single-Ended mode, only the main port is calibrated.
When in Differential Input mode, the user is guided through calibrating both main
and complementary ports.
The front panel I/Q port LEDs indicate the current state of that port. On (green)
indicates it is active, and off (dark) indicates it is not in use. For example, the Cal Out
port LED is on if and only if there is signal coming out of that port.
The input is a context and some parameters have separate values for each context.
The SCPI for these parameters has an optional "[:RF|IQ]" node. If the specific
context is omitted, the command acts on the current input context's value. Here are
the parameters that are input context sensitive:
– Center Frequency
– Trigger Source
It is important to distinguish between the I and Q input ports and the displayed I and
Q data values. The I and Q input ports feed into a digital receiver that does digital
tuning and filtering. The I and Q data seen by the user (either on the display or
through SCPI) corresponds to the real ("I") and the imaginary ("Q") output from the
165
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Input/Output
digital receiver. When the input path is I+jQ or I Only and the center frequency is 0
Hz the I input ends up in as the real output from the receiver and appears as "I"
data. Likewise, when the input path is I+jQ and the center frequency is 0 Hz, the Q
input ends up as the imaginary output from the receiver and appears as "Q" data.
However, when the input path is Q Only, the Q input is sent to the receiver as Q+j0,
so the receiver output has the Q input coming out on the real output, and so in Q
Only, the signal from the Q input port appears as the "I" data. Another situation
where the I and Q data do not necessarily correspond directly to the I and Q inputs
is when the center frequency is non-zero. The digital processing involved in the
tuning is a complex operation. This will result in I Only data appearing as both "I"
and "Q" data, the same as that signal would appear if seen through the RF input
port.
BBIQ is only supported in certain Modes and Measurements in the X-Series. When
I/Q is selected in a measurement that does not support it, the “No Result; Meas
invalid with I/Q inputs” message appears. This is error 135.
Baseband I/Q Remote Language Compatibility
For the Agilent E4406A VSA Series Transmitter Tester, Option B7C provided
baseband I/Q inputs. Code compatibility has been provided to allow many of the
commands for option B7C to function properly with the X-Series. The X-Series has
hardware differences and additional capabilities (e.g., E4406A does not have
independent settings of I & Q nor does it provide for probe calibrations) which make
100% compatibility impossible.
1. The following commands are supported:
:CALibration:IQ:FLATness
:INPut:IMPedance:IQ U50|B50|U1M|B1M
:INPut:IMPedance:REFerence <integer>
2. The [:SENSe]:FEED RF|IQ|IONLy|QONLy|AREFerence|IFALign command supports
all parameters except IFALign. The FEED? query will return only RF|AIQ|AREF.
3. The following commands are not supported:
:CALibration:GIQ
:CALibration:IQ:CMR
:INPut:IQ:ALIGn OFF|ON|0|1
The Rohde & Schwarz FSQ-B71 also provides baseband I/Q inputs. A certain
amount of code compatibility is provided in the X-Series, however hardware
differences make this a somewhat limited set.
Supported:
The "<1|2>" is supported as "[1]".
INPut<1|2>:IQ:BALanced[:STATe] ON | OFF
INPut<1|2>:IQ:TYPE I | Q | IQ
Remote Language Compatibility Measurement Application Reference
166
3 RLC Mode & Swept SA Measurement
Input/Output
INPut<1|2>:IQ:IMPedance LOW | HIGH
Not Supported:
INPut<1|2>:SELect AIQ | RF
TRACe<1|2>:IQ:DATA:FORMat COMPatible | IQBLock | IQPair>
TRACe<1|2>:IQ:DATA:MEMory? <offset samples>,<# of samples>
TRACe<1|2>:IQ:DATA?
TRACe<1|2>:IQ:SET <filter type>,<rbw>,<sample rate>,<trigger
source>,<trigger slope>, <pretrigger samples>, <# of samples>
TRACe<1|2>:IQ:SRATe 10.0kHz to 81.6MHz
TRACe<1|2>:IQ[:STATe] ON|OFF
The Rohde & Schwarz FMU has the following SCPI, which is not supported (these
commands start/abort the probe calibration procedure, which is manually
interactive from the front panel):
CALibration:ABORt
CALibration:PROBe[:STARt]
Couplings
The [:SENSe]:FEED RF command turns the calibrator OFF.
The act of connecting the U7227A USB Preamplifier to one of the analyzer’s USB
ports will cause the Input to automatically switch to the RF Input. If the RF
Calibrator is On, it is turned Off. Subsequently disconnecting the USB Preamp from
USB does not change the Input selection nor restore the previous selection.
Backwards Compatibility
[:SENSe]:FEED AREFerence
In the PSA the calibrator was one of the inputs and selected using the AREF
parameter to the same :FEED command that switched the inputs. In the X-Series it
is controlled in a separate menu and overrides the input selection. For code
compatibility the [:SENSe]:FEED AREFerence command is provided, and is aliased
to [SENSe]:FEED:AREF REF50, which causes the input to be switched to the 50 MHz
calibrator. The [:SENSe]:FEED RF command switches the input back to the RF port
and turns the calibrator OFF, thus providing full compatibility with the PSA
calibrator function.
Note that after sending this, the query [:SENSe]:FEED? will NOT return “AREF” but
instead the currently selected input.
Most of the settings in the X-Series Input/Output system, including External Gain,
Amplitude Corrections settings and data, etc., are shared by all modes and are not
changed by a mode switch. Furthermore, most variables in the Input/Output
system key are not affected by Mode Preset. Both of these behaviors represent a
departure from legacy behavior.
167
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Input/Output
In the X-Series. Input/Output settings are reset by using the "Restore Input/Output
Defaults" function. They can also be reset to their default values through the
System->Restore System Defaults-> In/Out Config key or through the System >Restore System Defaults -> All key (and corresponding SCPI).
While this matches most use cases better, it does create some code compatibility
issues. For example, Amplitude Corrections are no longer turned off by a Mode
Preset, but instead by using the "Restore Input/Output Defaults" key/SCPI.
Although Input/Output settings are not part of each Mode’s State, they are saved
in the Save State files, so that all of the instrument settings can be recalled with
Recall State, as in legacy instruments.
Legacy Input Mixer Backwards Compatibility
Command
:INPut:MIXer EXTernal|INTernal
:INPut:MIXer?
Example
INP:MIX INT
INP:MIX?
Preset
INT
In legacy analyzers you choose between the Internal mixer or an External Mixer. In
the X-Series, the External Mixer is one of the choices for the Input and is selected
using the FEED command (:SENSe:FEED EXTMixer).
For compatibility, the INPut:MIXer EXTernal|INTernal legacy command is mapped
as follows:
1. When INPut:MIXer EXTernal is received, SENSe:FEED EMIXer is executed.
2. When INPut:MIXer INTernal is received, SENSe:FEED RF is executed.
3. When INPut:MIXer? is received, the response will be INT if any input other than
the external mixer is selected and EXT if the external mixer is selected.
PSA supports the following SCPI Command :
:INPut:MIXer:TYPE PRESelected|UNPReselect
:INPut:MIXer:TYPE?
PXA does not support the :INPut:MIXer:TYPE command.
More Information on External Mixer
When External Mixer is selected, the Center Freq key controls the setting of the
Center Freq in external mixing, which is separate from the settings of Center Freq
for the RF Input or BBIQ. Each input retains its unique settings for Center Freq. A
unique SCPI command is provided solely for the external mixing Center Freq (see
the Center Freq key description), which only affects the External Mixer CF, although
sending the generic Center Freq command while External Mixer is selected also
controls the External Mixer CF.
Remote Language Compatibility Measurement Application Reference
168
3 RLC Mode & Swept SA Measurement
Input/Output
Unless option EXM is present, the External Mixer key is blanked, and all SCPI
commands associated with menus accessed by this key return an error.
Manual FFT mode is available with external mixing, but not with Signal ID.
All settings under this selection, and all Frequency settings, are remembered when
you go out of External Mixer, so that when External Mixer is chosen again, all the
external mixer functions will retain their previous settings, with the exception of
Signal ID which is set to OFF (Signal ID is also set to Off unless External Mixer is the
selected Input). Note that this differs from ESA and PSA, in which all external mixer
settings including Center Frequency are lost when you turn off External Mixing or
Preset the analyzer.
X-series analyzers have a combined LO Out/IF In connection, whereas earlier
analyzers used separate ports for the LO Out and the IF in. Internal diplexers in the
analyzer and the mixer simplify the connection for the user – only a single SMA
cable is required.
Legacy HP/Agilent and some third party mixers have separate LO In and IF out
connections. This requires you to use an external diplexer to connect these mixers.
A diplexer can easily be purchased for this purpose (for example, Diplexer Model #
DPL.26 or # DPL.313B from OML Inc., Morgan Hill CA)
The connection diagram for such a legacy mixer is:
169
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Input/Output
In addition, External Mixing in the X-Series supports the new Keysight M1970 series
of Harmonic Mixers, which provide a USB connection for download of calibration
data and additional control.
The connection diagram for one of the Keysight USB mixers is:
Also available in the M197x series are the M1971 series USB Mixers, which provide
additional inputs and outputs for special functionality as described below. These
mixers have multiple signal paths which allow them to function in three different
states:
– Normal, in which it functions as a classic external mixer with a single conversion:
Remote Language Compatibility Measurement Application Reference
170
3 RLC Mode & Swept SA Measurement
Input/Output
– Dual Conversion, which gives you a wider image-free range. In Dual
Conversion, the first conversion is to a higher IF frequency and you provide a 10
MHz signal to which an internal PLL is locked, to effect a second
downconversion:
– Aux Equipment, wherein the first mixer output drives an output connector on the
mixer and the analyzer is out of the circuit:
External Mixing is only supported in certain Modes and Measurements in the XSeries, as shown in the table below. When External Mixer is selected in a
measurement that does not support it, the "No result; Meas invalid with Ext Mixing"
error condition occurs:
171
Mode
Measurement
Sig ID (Image
Suppress only)
Spectrum Analyzer
Swept SA
Y*
TOI
Y
Spurious Emissions
Y
Harmonics
N
Channel Power
Y
Occupied BW
Y
ACP
Y
Spectrum Emissions Mask
Y
CCDF
N
Burst power
N
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Input/Output
Mode
Phase Noise
I/Q Waveform
Measurement
Sig ID (Image
Suppress only)
List Sweep
N
Monitor Spectrum
Y
Log Plot
Y
Spot Frequency
N
Waveform
N
Complex Spectrum
N
Waveform
N
* the Swept SA measurement also supports Image Shift
RF Calibrator
Lets you choose a calibrator signal to look at or turns the calibrator off.
Only appears when RF Input is selected as the input.
Command
[:SENSe]:FEED:AREFerence REF50|REF4800|OFF
[:SENSe]:FEED:AREFerence?
Example
FEED:AREF REF50 selects the 50 MHz amplitude reference as the signal input.
FEED:AREF REF4800 selects the 4.8 GHz amplitude reference as the signal input
FEED:AREF OFF turns the calibrator "off"
Preset
OFF
State Saved
Saved in instrument state.
Dependencies
Selecting an input (RF, Ext Mix or I/Q) turns the Calibrator OFF. This is true whether
the input is selected through the front panel or with the [:SENSe]:FEED command.
The 4.8 GHz internal reference is only available in some models and frequency
range options. If the 4.8 GHz reference is not present, the 4.8 GHz selection will be
blanked, and if the REF4800 parameter is sent, the analyzer will generate an error.
Couplings
When one of the calibrator signals is selected, the analyzer routes that signal (an
internal amplitude reference) to the analyzer, and changes the main input selection
to RF so the calibrator signal can be seen. When you turn the calibrator off it does
not switch back to the previously selected input.
Backwards Compatibility
For ESA backwards compatibility.
In the ESA the calibrator was a separate output which you connected to the input
and switched on with this command.
Remote Language Compatibility Measurement Application Reference
172
3 RLC Mode & Swept SA Measurement
Input/Output
In the X-Series, the ON parameter is aliased to the [SENSe]:FEED:AREF REF50
command and the OFF parameter is aliased to [SENSe]:FEED:AREF OFF.
When CALibration:SOURce:STATe? is received, 1 will be returned if any of the
references is selected and 0 if the Calibrator is "Off"
:CALibration:SOURce:STATe OFF|ON|0|1
Command
:CALibration:SOURce:STATe?
RF Coupling
Specifies alternating current (AC) or direct current (DC) coupling at the analyzer RF
input port. Selecting AC coupling switches in a blocking capacitor that blocks any DC
voltage present at the analyzer input. This decreases the input frequency range of
the analyzer, but prevents damage to the input circuitry of the analyzer if there is a
DC voltage present at the RF input.
When operating in DC coupled mode, ensure protection of the analyzer input
circuitry by limiting the DC part of the input level to within 200 mV of 0 Vdc. In AC or
DC coupling, limit the input RF power to +30 dBm (1 Watt).
See "More information" on page 173
Only appears when RF Input is selected as the Input.
Command
:INPut:COUPling AC|DC
:INPut:COUPling?
Example
INP:COUP DC
Preset
AC on models that support AC coupling.
On models that are always DC coupled, such as millimeter wave models (frequency
ranges 30 GHz and above), the preset is DC
State
Saved
Saved in instrument state.
Dependencies
This control does not appear in models that are always AC coupled. When the SCPI
command to set DC coupling is sent to these models, it results in the error “Illegal
parameter value; This model is always AC coupled”. In these models, the SCPI
query INP:COUP? always returns AC.
This control does not appear in models that are always DC coupled. When the
SCPI command to set AC coupling is sent to these models, it results in the error
“Illegal parameter value; This instrument is always DC coupled”. In these models,
the SCPI query INP:COUP? always returns DC.
More information
In AC coupling mode, you can view signals below the corner frequency of the DC
block, but below a certain frequency the amplitude accuracy is not specified.
173
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Input/Output
The lowest frequency for which specifications apply is:
Some amplitude specifications apply only when coupling is set to DC. Refer to the
appropriate amplitude specifications and characteristics for your analyzer.
Input Z Correction
Sets the input impedance for unit conversions. This affects the results when the yaxis unit is voltage or current units (dBmV, dBµV, dBµA, V, A), but not when it is
power units (dBm, W). The impedance you select is for computational purposes only,
since the actual impedance is set by internal hardware to 50 ohms. Setting the
computational input impedance to 75 ohms is useful when using a 75 ohm to 50 ohm
adapter to measure a 75 ohm device on an analyzer with a 50 ohm input impedance.
There are a variety ways to make 50 to 75 ohm transitions, such as impedance
transformers or minimum loss pads. The choice of the solution that is best for your
measurement situation requires balancing the amount of loss that you can tolerate
with the amount of measurement frequency range that you need. If you are using
one of these pads or adaptors with the Input Z Corr function, you might also want to
use the Ext Gain key. This function is used to set a correction value to compensate
for the gain (loss) through your pad. This correction factor is applied to the displayed
measurement values.
Command
[:SENSe]:CORRection:IMPedance[:INPut][:MAGNitude] 50|75
[:SENSe]:CORRection:IMPedance[:INPut][:MAGNitude]?
Example
CORR:IMP 75 sets the input impedance correction to 75 ohms.
CORR:IMP?
Preset
This is unaffected by a Preset but is set to 50 ohms on a "Restore Input/Output Defaults"
or "Restore System Defaults->All".
State
Saved
Saved in instrument state
Remote Language Compatibility Measurement Application Reference
174
3 RLC Mode & Swept SA Measurement
Input/Output
Couplings
In CXA option C75, when RF Input 2 is selected, the Input Z Correction will
automatically change to 75 ohms. You may then change it to whatever is desired.
When the main RF Input is selected, the Input Z Correction will automatically
change to 50 ohms. You may then change it to whatever is desired.
All Screens Use Same Input
– ON - the input/output state is shared between all screens. This is the default.
– OFF - independent input/output per screen.
Pressing Input/Output Preset affects only the current Screen.
When you clone a Screen, you also clone its Input/Output state.
Preset
ON (not affected by Input/Output Preset but set to ON by Restore Input/Output
Defaults)
Initial S/W
Revision
A.19.00
Input/Output Preset
Input/Output Preset resets the group of settings and data associated with the
Input/Output front-panel key to their default values. These settings are not affected
by a Mode Preset because they are generally associated with connections to the
instrument, and most users would not want these resetting every time they pressed
the Mode Preset key.
By using Input/Output Preset and Restore Mode Defaults, a full preset of the current
mode will be performed, with the caveat that since Input/Output Preset is a global
function it will affect ALL modes.
This is the same as the button found in the Preset dropdown, and also the same as
the Input/Output button in the Restore Defaults menu under the System key.
All the variables set under the Input/Output front panel key are reset by
Input/Output Preset, including Amplitude Corrections and Data.
When Input/Output Preset is selected, a message appears saying:
“This will reset all of the Input/Output variables to their
default state, including which input is selected, all Amplitude
Correction settings and data, all External Mixing settings, all
Frequency Reference settings and all Output settings.
It will not affect Alignment data or settings.
This action cannot be undone. Do you want to proceed?”
The message provides an OK and Cancel button for the user to affirm or cancel the
operation.
Example
175
:SYST:DEF INP
Presets all the Input/Output variables to their factory default values.
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Input/Output
External Gain Tab
Ext Preamp
This function is similar to the reference level offset function. Both affect the
displayed signal level. Ref Lvl Offset is a mathematical offset only, no analyzer
configuration is affected. Ext Preamp gain is used when determining the autocoupled value of the Attenuator. The External Gain value and the Maximum Mixer
Level settings are both part of the automatic setting equation for the RF attenuation
setting. (10 dB of Attenuation is added for every 10 dB of External Gain.)
Note that the Ref Lvl Offset and Maximum Mixer Level are described in the Amplitude
section. They are reset by the instrument Preset. The External Preamp Gain is reset
by the "Restore Input/Output Defaults" or "Restore System Defaults->All functions.
The External Gain is subtracted from the amplitude readout so that the displayed
signal level represents the signal level at the output of the device-under-test, which
is the input of the external device that is providing gain or loss.
The Swept SA Measurement supports the “Ext Preamp” function under External
Gain. The other External Gain functions are grayed out and generate a settings
conflict if the SCPI for them is sent.
The Swept SA Measurement does not support the Data Source function. The key is
blanked, and if the :FEED:DATA SCPI is sent an Undefined Header error is
generated.
The Swept SA Measurement supports the Corrections function. In
Modes/Measurements that do not support Corrections, the control is blanked, and
sending SCPI for Corrections will generate a Settings Conflict message.
The Swept SA Measurement does not support the Digital Bus function or the I/Q Cal
Out function under Output Config; although the controls display, the outputs do not
function in this measurement.
The Swept SA Measurement supports all of the functions under Output Config,
Analog Out. If the appropriate license is present the associated keys appear, and
function properly. In Modes/Measurements that do not support particular controls,
they still appear, but no output will be generated if they are selected.
The reference level limits are determined in part by the External Gain/Atten, Max
Mixer Level, and RF Atten.
See "More Information" on page 177.
This control is grayed out in Modes that do not support External Gain.
Command
[:SENSe]:CORRection:SA[:RF]:GAIN <rel_ampl>
[:SENSe]:CORRection:SA[:RF]:GAIN?
Example
CORR:SA:GAIN 10 sets the Ext Gain value to 10 dB CORR:SA:GAIN -10 sets the Ext Gain
Remote Language Compatibility Measurement Application Reference
176
3 RLC Mode & Swept SA Measurement
Input/Output
value to -10 dB (that is, an attenuation of 10 dB)
Preset
This is unaffected by Preset but is set to 0 dB on a "Restore Input/Output Defaults" or
"Restore System Defaults->All"
Min/Max
–120 dB/120 dB
State
Saved
Saved in instrument state.
Backwards Compatibility
[:SENSe]:CORRection:OFFSet[:MAGNitude]
! The legacy "Ext Preamp Gain" key is now called "Ext Gain" and the sub-menu has
choices of Ext Preamp | MS | BTS for backwards compatibility.
More Information
The U7227A USB Preamplifier is an accessory for the X-Series Signal Analyzer that
provides gain externally, and whose gain settings are automatically loaded into the
analyzer over USB whenever it is connected to one of the analyzer’s USB ports.
While the USB Preamplifier is plugged into one of the analyzer’s USB ports, the
analyzer will consider it to be in the signal path of the RF Input and will apply the
calibration data from the USB Preamp to measurements taken at the RF Input (on 2
input boxes, it will be considered to be in the signal path of RF Input 1; it is not
supported for RF Input 2).
The USB Preamplifier contains its own cal data. This includes a noise trace suitable
for use with NFE, for those models which support NFE. The act of connecting the
Preamp to USB will cause the cal data to be downloaded from the preamp. When
this happens an informational message is provided saying “Cal data loaded from
USB Preamp”. The analyzer will then automatically apply the calibration factors
loaded from the Preamp in any measurement that supports the USB Preamp.
The External Preamp Gain setting may still be used, even though it is not required
for the USB Preamp (since the USB Preamp supplies its own gain data to the
analyzer which is applied automatically). Connecting the USB Preamp does not
change the External Preamp Gain setting, however unless you have another gain or
attenuation element in the signal path, the appropriate setting for External Preamp
Gain is 0 dB.
Overload detection and reporting will apply when the USB preamplifier is
connected to USB. The USB Preamplifier has its own overload detector which
reports overloads to the instrument over USB. This generates an error condition,
“Input Overload;USB Preamp.”
If, while the USB Preamp is connected to USB, a measurement is selected that
does not support the USB preamplifier, the "No result; Meas invalid with Preamp"
error condition is generated.
MS
Sets an external gain/attenuation value for MS (Mobile Station) tests.
This selection is grayed out in modes that do not support MS.
177
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Input/Output
Cammand
[:SENSe]:CORRection:MS[:RF]:GAIN <rel_ampl>
[:SENSe]:CORRection:MS[:RF]:GAIN?
Example
CORR:MS:GAIN 10
Sets the Ext Gain value to 10 dB
CORR:MS:GAIN -10
Sets the Ext Gain value to -10 dB (that is, a loss of 10 dB.)
Preset
This is unaffected by a Preset but is set to 0 dB on a "Restore Input/Output Defaults" or
"Restore System Defaults->All"
Min/Max
–100 dB/100 dB
State
Saved
Saved in instrument state.
Dependencies
The reference level limits are determined in part by the External Gain, Max Mixer
Level, RF Atten.
BTS
Sets an external attenuation value for BTS (Base Transceiver Station) tests.
This selection is grayed out in modes that do not support BTS
Command
[:SENSe]:CORRection:BTS[:RF]:GAIN <rel_ampl>
[:SENSe]:CORRection:BTS[:RF]:GAIN?
Example
CORR:BTS:GAIN 10
Sets the Ext Gain value to 10 dB
CORR:BTS:GAIN -10
Sets the Ext Gain value to -10 dB (that is, a loss of 10 dB.)
Preset
This is unaffected by a Preset but is set to 0 dB on a "Restore Input/Output Defaults" or
"Restore System Defaults->All"
Min/Max
–100 dB/100 dB
State
Saved
Saved in instrument state.
Dependencies
The reference level limits are determined in part by the External Gain, Max Mixer
Level, RF Atten.
Remote Language Compatibility Measurement Application Reference
178
3 RLC Mode & Swept SA Measurement
Input/Output
Corrections Tab
Corrections On/Off
Turning the Selected Correction from the OFF state to the ON state allows the
values in it to be applied to the data. This state transition also automatically turns on
"Apply Corrections" (sets it to ON), otherwise the correction would not take effect.
A new sweep is initiated if an amplitude correction is switched on or off. Note that
changing, sending or loading corrections data does NOT directly initiate a sweep,
however in general these operations will turn corrections on, which DOES initiate a
sweep.
Command
[:SENSe]:CORRection:CSET[1]|2|3|4|5|6|7|8[:STATe] ON|OFF|1|0
[:SENSe]:CORRection:CSET[1]|2|3|4|5|6|7|8[:STATe]?
Example
SENS:CORR:CSET1 ON
Preset
Not affected by a Preset. Set to OFF by Restore Input/Output Defaults
State Saved
Saved in instrument state.
Dependencies
Changing this from the OFF state to the ON state automatically turns on "Apply
Corrections".
Only the first correction array (Correction 1) supports Transducer units. When this
array is turned on, and it contains a Transducer Unit other than “None”, the Y Axis
Unit of the analyzer is forced to that Transducer Unit. All other Y Axis Unit choices
are grayed out.
Note that this means that a correction file with a Transducer Unit can only be
loaded into the Corrections 1 register. Consequently only for Correction 1 does the
dropdown in the Recall dialog include.ant, and if an attempt is made to load a
correction file into any other Correction register which DOES contain a Transducer
unit, a Mass Storage error is generated.
This command will generate an “Option not available” error unless you have the
proper option installed in your instrument.
Backwards Compatability
Unlike legacy analyzers, Preset does not turn Corrections off (Restore Input/Output
Defaults does).
Edit Corrections
Invokes the integrated editing facility for this correction set.
When entering the menu, the editor window turns on, the selected correction is
turned On, Apply Corrections is set to On, the amplitude scale is set to Log, and the
Amplitude Correction (“Ampcor”) trace is displayed. The actual, interpolated
correction trace is shown in green for the selected correction. Note that since the
actual interpolated correction is shown, the correction trace may have some
179
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Input/Output
curvature to it. This trace represents only the correction currently being edited,
rather than the total, accumulated amplitude correction for all amplitude corrections
which are currently on, although the total, accumulated correction for all corrections
which are turned on is still applied to the data traces.
Because corrections data is always in dB, but the Y-axis of the analyzer is in absolute
units, it is necessary to establish a reference line for display of the Corrections data.
The reference line is halfway up the display and represents 0 dB of correction. It is
labeled “0 dB CORREC”. It is drawn in blue.
Corrections data is always in dB. Whatever dB value appears in the correction table
represents the correction to be applied to that trace at that frequency. So if a table
entry shows 30 dB that means we ADD 30 dB to each trace to correct it before
displaying it. By definition all points are connected. If a gap is desired for corrections
data, enter 0 dB.
Note that a well-designed Corrections array should start at 0 dB and end at 0 dB.
This is because whatever the high end point is will be extended to the top frequency
of the instrument, and whatever the low end point is will be extended down to 0 Hz.
So for a Corrections array to have no effect outside its range, you should start and
end the array at 0 dB.
The table editor will only operate properly if the analyzer is sweeping, because its
updates are tied to the sweep system. Thus, you should not try to use the editor in single
sweep, and it will be sluggish during compute-intensive operations like narrow-span FFT
sweeps.
When exiting the edit menu (by using the Return key or by pressing an instrument
front-panel key), the editor window turns off and the Ampcor trace is no longer
displayed; however, Apply Corrections remains On, any correction that was on while
in the editor remains on, and the amplitude scale returns to its previous setting.
Corrections arrays are not affected by a Preset, because they are in the
Input/Output system. They also survive shutdown and restarting of the analyzer
application, which means they will survive a power cycle.
When editing a correction, the editor remembers which correction and which
element in the correction array you were editing, and returns you to that correction
and that element when you return to the editor after leaving it.
Select Correction
Specifies the selected correction. The term "selected correction" is used
throughout this document to specify which correction will be affected by
the functions.
Frequency
Touching a frequency value makes the touched row the current row and
lets you edit the frequency.
Amplitude
Remote Language Compatibility Measurement Application Reference
180
3 RLC Mode & Swept SA Measurement
Input/Output
Touching an amplitude value makes the touched row the current row
and lets you edit the amplitude..
Go To Row
Lets you move through the table to edit the desired point.
Insert Row Below
Inserts a point below the current point. The new point is a copy of the
current point and becomes the current point. The new point is not yet
entered into the underlying table, and the data in the row is displayed in
light gray.
Delete Row
Deletes the currently-selected point, whether or not that point is being
edited, and selects the Navigate functionality. The point following the
currently-selected point (or the point preceding if there is none) will be
selected.
Scale X Axis
Matches the X Axis to the selected Correction, as well as possible. Sets
the Start and Stop Frequency to contain the minimum and maximum
Frequency of the selected Correction. The range between Start
Frequency and Stop Frequency is 12.5% above the range between the
minimum and maximum Frequency, so that span exceeds this range by
one graticule division on either side. If in zero-span, or there is no data in
the Ampcor table, or the frequency range represented by the table is
zero, no action is taken. Standard clipping rules apply if the value in the
table is outside the allowable range for the X axis.
Delete Correction
Deletes the correction values for this set. When this key is pressed a
prompt is placed on the screen that says “Please press Enter or OK key
to delete correction. Press ESC or Cancel to close this dialog.” The
deletion is only performed if you press OK or Enter.
Command
[:SENSe]:CORRection:CSET[1]|2|3|4|5|6:DELete
Example
CORR:CSET:DEL
CORR:CSET1:DEL
CORR:CSET4:DEL
Frequency Interpolation
This setting controls how the correction values per-bucket are calculated. We
interpolate between frequencies in either the logarithmic or linear scale.
This setting is handled and stored individually per correction set.
Interpolation
For each bucket processed by the application, all of the correction factors at the
181
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Input/Output
frequency of interest (center frequency of each bucket) are summed and added to
the amplitude. All trace operations and post processing treat this post-summation
value as the true signal to use.
To effect this correction, the goal, for any particular start and stop frequency, is to
build a correction trace, whose number of points matches the current Sweep Points
setting of the instrument, which will be used to apply corrections on a bucket by
bucket basis to the data traces.
For amplitudes that lie between two user specified frequency points, we
interpolate to determine the amplitude value. You may select either linear or
logarithmic interpolation between the frequencies.
If we interpolate on a log scale, we assume that the line between the two points is
a straight line on the log scale. For example, let’s say the two points are (2,4) and
(20,1). A straight line between them on a log scale looks like:
On a linear scale (like that of the spectrum analyzer), this translates to:
Remote Language Compatibility Measurement Application Reference
182
3 RLC Mode & Swept SA Measurement
Input/Output
If we interpolate on a linear scale, we assume that the two points are connected by
a straight line on the linear scale, as below:
The correction to be used for each bucket is taken from the interpolated correction
curve at the center of the bucket.
Command
[:SENSe]:CORRection:CSET[1]|2|3|4|5|6|7|8:X:SPACing
LINear|LOGarithmic
[:SENSe]:CORRection:CSET[1]|2|3|4|5|6|7|8:X:SPACing?
Example
CORR:CSET:X:SPAC LIN
Preset
Unaffected by a Preset. Set to Linear by Restore Input/Output Defaults.
State
Saved
Saved in instrument state.
Transducer Unit
For devices (like antennas) that make measurements of field strength or flux density,
the correction array should contain within its values the appropriate conversion
factors such that, when the data on the analyzer is presented in dBμV, the display is
calibrated in the appropriate units. The "Transducer Unit" used for the conversion is
contained within the corrections array database. It may be specified or loaded in
from an external file or SCPI.
When an array with a Transducer Unit other than "None" is turned on, the Y Axis Unit
of the analyzer is forced to that unit. When this array is turned on, and it contains a
Transducer Unit other than “None”, the Y Axis Unit of the analyzer is forced to that
Transducer Unit., and all other Y Axis Unit choices are grayed out.
Command
[:SENSe]:CORRection:CSET[1]:ANTenna[:UNIT]
GAUSs|PTESla|UVM|UAM|UA|NOConversion
[:SENSe]:CORRection:CSET[1]:ANTenna[:UNIT]?
183
Example
CORR:CSET:ANT GAUS
Preset
Unaffected by Preset. Set to NOC by Restore Input/Output Defaults
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Input/Output
State
Saved
Saved in instrument state.
Transducer Unit does not appear in all Modes that support Corrections.
Examples
The units that may be specified and what appears in the file and on the screen are
shown below:
Transducer
Unit
Example
In the Correction File
On the Screen (also Y Axis Unit
forced to)
dBμV/m
:CORR:CSET:ANT
UVM
Antenna Unit=μV/m
dBμV/m
dBμA/m
:CORR:CSET:ANT
UVA
Antenna Unit=μA/m
dBμA/m
dBμA
:CORR:CSET:ANT
UA
Antenna Unit=μA
dBμA
dBpT
:CORR:CSET:ANT
PTES
Antenna Unit=pTesla
dBpT
dBG
:CORR:CSET:ANT
GAUS
Antenna Unit=Gauss
dBG
None
:CORR:CSET:ANT
NOC
Antenna Unit= (or no
line at all)
none (not forced)
Dependencies
Only the first correction array (Correction 1) supports Transducer units.
Note that this means that a correction file with a Transducer Unit can only be
loaded into the Corrections 1 register. Consequently only for Correction 1 does the
dropdown in the Recall dialog include.ant, and if an attempt is made to load a
correction file into any other Correction register which DOES contain a Transducer
unit, a Mass Storage error is generated.
Description
Sets an ASCII description field which will be stored in an exported file. Can be
displayed in the active function area by selecting as the active function, if desired to
appear in a screen capture.
The maximum number of characters is 45.
Command
[:SENSe]:CORRection:CSET[1]|2|3|4|5|6|7|8:DESCription "text"
[:SENSe]:CORRection:CSET[1]|2|3|4|5|6|7|8:DESCription?
Example
:CORR:CSET1:DESC "11941A Antenna correction"
Remote Language Compatibility Measurement Application Reference
184
3 RLC Mode & Swept SA Measurement
Input/Output
Preset
Unaffected by a Preset. Set to empty by Restore Input/Output Defaults
State Saved
Saved in instrument state.
Comment
Sets an ASCII comment field which will be stored in an exported file. Can be
displayed in the active function area by selecting as the active function, if desired to
appear in a screen capture.
The maximum number of characters is 60.
Command
[:SENSe]:CORRection:CSET[1]|2|3|4|5|6|7|8:COMMent "text"
[:SENSe]:CORRection:CSET[1]|2|3|4|5|6|7|8:COMMent?
Example
:CORR:CSET1:COMM "this is a comment"
Preset
Unaffected by Preset. Set to empty by Restore Input/Output Defaults.
State Saved
Saved in instrument state.
Apply Corrections
Applies amplitude corrections, which are marked as ON to the measured data. If this
is set to OFF, then no amplitude correction sets will be used, regardless of their
individual on/off settings. If set to ON, the corrections that are marked as ON (see
"Corrections On/Off" on page 179) are used.
Command
[:SENSe]:CORRection:CSET:ALL[:STATe] ON|OFF|1|0
[:SENSe]:CORRection:CSET:ALL[:STATe]?
Example
SENS:CORR:CSET:ALL OFF This command makes sure that no amplitude corrections are
applied, regardless of their individual on/off settings.
Preset
Not affected by Preset. Set to OFF by Restore Input/Output Defaults
Saved
State
Saved in instrument state.
Delete All Corrections
Erases all correction values for all 4 Amplitude Correction sets.
When this control is pressed a prompt is placed on the screen that says “Please
press Enter or OK key to delete all corrections. Press ESC or Cancel to close this
dialog.” The deletion is only performed if you press OK or Enter.
185
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Input/Output
Command
[:SENSe]:CORRection:CSET:ALL:DELete
Example
CORR:CSET:ALL:DEL
Freq Ref Input Tab
Select Freq Ref Input
Specifies the frequency reference as being the internal reference at the rear panel
input labeled EXT REF IN, a 1 pulse per second signal at the EXT REF IN input,
external reference or sensing the presence of a signal at the EXT REF IN input.
Selection Examples
Selection
Example
Notes
Sense
:ROSC:SOUR:TYPE
SENS
If Sense is selected, the instrument checks whether a signal is
present at the external reference connector. If it senses a signal
within 5 ppm of the External Ref Freq (as set on the External Ref
Freq softkey), it will use this signal as an External Reference. If it
senses a 1 pulse per second signal, it will use this signal to
adjust the internal reference by adjusting the User setting of the
Timebase DAC. When no signal is present, it automatically
switches to the internal reference.
Internal
:ROSC:SOUR:TYPE
INT
The internal reference is used. A 1 pps signal at the EXT REF IN
port, or a signal there between 1 and 50 MHz, will cause a
warning triangle to appear in the settings panel next to the word
“INTERNAL”, but will otherwise be ignored.
External
:ROSC:SOUR:TYPE
INT
The external reference is used.
Pulse
:ROSC:SOUR:TYPE
PULS
The internal reference continues to be the frequency reference
for the instrument in that it determines the reference
contribution to the phase noise, but its average frequency is
adjusted to follow the 1 pps signal at the EXT REF IN input.
Therefore, the analyzer frequency accuracy will be dominated by
the aging rate of the 1 pps signal instead of the aging rate of the
internal reference, except during the time it takes to lock to a
new 1 pps signal, approximately 10 minutes.
See "More Information" on page 186.
More Information
When a 1 pps signal is present at the EXT REF IN input, and either Pulse or Sense is
selected, the internal reference frequency is affected by this signal; in effect, it
“learns” a new accuracy setting. This setting can be seen by going to the System,
Alignments, Timebase Dac menu, and looking at the User key in that menu. You will
note that User has become automatically selected, and that the value shown on
the User key is the updated value of the timebase DAC as “learned” from the 1 pps
Remote Language Compatibility Measurement Application Reference
186
3 RLC Mode & Swept SA Measurement
Input/Output
signal. Note that this replaces any value the user might have previously set on this
key.
Once the setting is learned the user may remove the 1 pps signal; the User setting
for the Timebase DAC is retained until you manually select “Calibrated” or execute
a System, Restore Defaults, Align or a System, Restore Defaults, All. If you want to
make the User setting permanent there is information in the Service Guide that tells
you how to change the Calibrated setting of the Timebase DAC.
Note also that if the 1 pps signal is removed when Sense is selected, the analyzer
will simply switch to the normal state of the Internal reference and display
SENSE:INT in the Settings Panel. However, if the 1 pps signal is removed when
Pulse is selected, the analyzer will generate an error.
The J7203A Atomic Frequency Reference is an accessory for the X-Series Signal
Analyzer that provides a highly accurate 1 pps timebase to use in conjunction with
the Pulse setting. With the J7203A, the 1 pps signal is guaranteed to meet the
input requirements of the EXT REF IN port, and the improved accuracy of the
analyzer’s internal frequency reference is specified. This is the only 1 pps signal
that is guaranteed to function properly with the X-Series.
Command
[:SENSe]:ROSCillator:SOURce:TYPE INTernal|EXTernal|SENSe|PULSe
[:SENSe]:ROSCillator:SOURce:TYPE?
Example
:ROSC:SOUR:TYPE:SENS
Preset
This is unaffected by a Preset but is set to SENSe on a "Restore Input/Output Defaults" or
"Restore System Defaults->All".
State
Saved
Saved in instrument state.
Dependencies
The PULSe parameter, and support of the 1 pps signal at the EXT REF IN input, are
not available in firmware prior to A.13.00. They are also not available in some
model numbers. If not available, the Pulse key will be blank, and sending the
PULSe parameter via SCPI will generate an error.
Status Bits/OPC Dependencies
STATus:QUEStionable:FREQuency bit 1 set if unlocked.
Backwards Compatibility
[:SENSe]:ROSCillator:SOURce INTernal|EXTernal
For PSA compatibility the command form is provided and is directly mapped to
[:SENSe]:ROSCillator:SOURce:TYPE
Frequency Reference Query (Remote Command Only)
The query [SENSe]:ROSCillator:SOURce? returns the current switch setting. This
means:
187
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Input/Output
1. If it was set to SENSe but there is no external reference nor 1pps signal so the
instrument is actually using the internal reference, then this query returns
INTernal and not SENSe.
2. If it was set to SENSe and there is an external reference present, the query
returns EXTernal and not SENSe.
3. If it was set to SENSe and there is a 1 pps signal present, the query returns
PULSe and not SENSe.
4. If it was set to EXTernal, then the query returns "EXTernal"
5. If it was set to INTernal, then the query returns “INTernal”.
6. If it was set to PULSe, then the query returns “PULSe
Backwards Compatibility:
The query [:SENSe]:ROSCillator:SOURce? was a query-only command in ESA
which always returned whichever reference the instrument was using. The
instrument automatically switched to the ext ref if it was present.
In PSA (which had no sensing) the command [:SENSe]:ROSCillator:SOURce set the
reference (INT or EXT), so again its query returned the actual routing.
Thus the query form of this command is 100% backwards compatible with both
instruments.
External Ref Freq
This control sets the frequency of the external reference. When the external
reference is in use (either because the reference has been switched to External or
because the Reference has been switched to Sense and there is a valid external
reference present) this information is used by the analyzer to determine the internal
settings needed to lock to that particular external reference signal.
For the instrument to stay locked, the value entered must be within 5 ppm of the
actual external reference frequency. So it is important to get it close, or you risk an
unlock condition.
Note that this value only affects the instrument’s ability to lock. It does not affect any
calculations or measurement results. See "Freq Offset" in the Frequency section for
information on how to offset frequency values.
Command
[:SENSe]:ROSCillator:EXTernal:FREQuency <freq>
[:SENSe]:ROSCillator:EXTernal:FREQuency?
Example
ROSC:EXT:FREQ 20 MHz sets the external reference frequency to 20 MHz, but does not
select the external reference.
ROSC:SOUR:TYPE EXT selects the external reference.
Remote Language Compatibility Measurement Application Reference
188
3 RLC Mode & Swept SA Measurement
Input/Output
Preset
This is unaffected by a Mode Preset or an "Input/Output Preset" or "Restore Defaults,
Input/Output" but is set to 10 MHz on a "Restore Defaults, Misc" or "Restore Defaults,
All" or by pressing the “Default External Ref Freq” button.
Min/Max
1 MHz/50 MHz
Dependencies
Still available with Internal or Pulse selected, to allow setup for when External is in
use. However, the setting has no effect if the Internal Reference is in use (Freq Ref
In set to Internal, Pulse, or SENSE:INT or SENSE:PULSE).
Default External Ref Freq
This control restores the External Ref Freq to its default of 10 MHz.
When you set an External Ref Freq value with the Ext Ref Freq control, that
Frequency is persistent; is not affected by Mode Preset or Input/Output Preset, and
survives shutdown and power cycle. This control allows you to reset the External Ref
Freq to its default value.
The persistence of the External Ref Freq is a new behavior as of firmware version
A.18.00, necessitating the addition of this control. In versions before A.18.00, the
frequency reset on a power cycle/restart. Thus you may need to use this command to
retain backwards compatibility.
This control is grayed out if the Ext Ref Freq is already set to the default
Command
[:SENSe]:ROSCillator:EXTernal:FREQuency:DEFault
Example
ROSC:EXT:FREQ:DEF ! resets the external ref frequency
External Ref Lock BW
This control lets you adjust the External Reference phase lock bandwidth. This
control is available in some models of the X-Series.
The variable reference loop bandwidth allows an external reference to be used and
have the analyzer close-in phase noise improved to match that of the reference. This
could result in an improvement of tens of decibels. The choice of “Wide” or “Narrow”
affects the phase noise at low offset frequencies, especially 4 to 400 Hz offset. When
using an external reference with superior phase noise, we recommend setting the
external reference phase-locked-loop bandwidth to wide (60 Hz), to take advantage
of that superior performance. When using an external reference with inferior phase
noise performance, we recommend setting that bandwidth to narrow (15 Hz). In
these relationships, inferior and superior phase noise are with respect to −134
dBc/Hz at 30 Hz offset from a 10 MHz reference. Because most reference sources
have phase noise behavior that falls off at a rate of 30 dB/decade, this is usually
equivalent to −120 dBc/Hz at 10 Hz offset.
Command
189
[:SENSe]:ROSCillator:BANDwidth WIDE|NARRow
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Input/Output
[:SENSe]:ROSCillator:BANDwidth?
Example
ROSC:BAND WIDE
Preset
This is unaffected by a Preset but is set to Narrow on a "Restore Input/Output Defaults"
or "Restore System Defaults -> All"
State
Saved
Saved in Input/Output state.
Dependencies
Still available with Internal or Pulse selected, to allow setup for when External is in
use. However, the setting has no effect if the Internal Reference is in use (Freq Ref
In set to Internal, Pulse, or SENSE:INT or SENSE:PULSE).
This key only appears in analyzers equipped with the required hardware.
Output Tab
Trig 1 Out
This control selects the type of output signal that will be output from the Trig 1 Out
connector.
The SCPI command applies to all Trig Out connectors and selects the type of output
signal that will be output from the Trig 1 Out, or Trig 2 Out connector.
Command
:TRIGger|TRIGger1|TRIGger
[:SEQuence]:OUTPutHSWP|MEASuring|MAIN|GATE|GTRigger|OEVen|SPOint|SS
Weep|SSETtled|S1Marker|S2Marker|S3Marker|S4Marker|OFF
Example
TRIG:OUTP HSWP
Preset
Trigger 1: Sweeping (HSWP)
:TRIGger|TRIGger1|TRIGger2[:SEQuence]:OUTPut?
TRIG2:OUTP GATE
Trigger 2: Gate
This is unaffected by a Preset but is preset to the above values on a “Restore Input/Output
Defaults” or “Restore System Defaults->All”
State
Saved
Saved in instrument state.
Trigger Outputs
Source
Example
Notes
Off
TRIG1:OUTP
OFF
Selects no signal to be output to the Trig 1 Out, or Trig 2 Out
connector.
Remote Language Compatibility Measurement Application Reference
190
3 RLC Mode & Swept SA Measurement
Input/Output
Source
Example
Notes
TRIG2:OUTP
OFF
Sweeping
(HSWP)
TRIG1:OUTP
HSWP
Selects the Sweeping Trigger signal to be output to the Trig 1 Out, or
Trig 2 Out, connector when a measurement is made. This signal has
historically been known as "HSWP" (High = Sweeping), and is 5 V TTL
level with 50 ohm output impedance.
Measuring
TRIG1:OUTP
MEAS
Selects the Measuring trigger signal to be output to the Trig 1 Out, or
Trig 2 Out, connector. This signal is true while the Measuring status
bit is true.
Main
Trigger
TRIG1:OUTP
MAIN
Selects the current instrument trigger signal to be output to the Trig
1 Out, or Trig 2 Out connector
Gate
Trigger
TRIG1:OUTP
GTR
Selects the gate signal to be output to the Trig 1 Out, or Trig 2 Out,
connector. This is the source of the gate timing, not the actual gate
signal.
Gate
TRIG1:OUTP
GATE
Selects the gate signal to be output to the Trig 1 Out, or Trig 2 Out
connector. The gate signal has been delayed and its length
determined by delay and length settings. When the polarity is
positive, a high on the Trig 1 Out, or Trig 2 Out represents the time
the gate is configured to pass the signal.
Odd/Even
Trace
Point
TRIG1:OUTP
OEV
Selects either the odd or even trace points as the signal to be output
to the Trig 1 Out, or Trig 2 Out connector when performing swept
spectrum analysis. When the polarity is positive, this output goes high
during the time the analyzer is sweeping past the first point (Point 0)
and every other following trace point. The opposite is true if the
polarity is negative.
Source
Point
Trigger
TRIG1:OUTP
SPO
Selects the gate signal to be output to the Trig 1 Out, or Trig 2 Out
connector for use as the Point Trigger when operating an external
source in Tracking mode. When Ext Trigger 1 is selected as the Point
Trigger under Source, the Source Point Trigger under Trig1 Out
automatically gets selected. Similarly, when Ext Trigger 2 is selected
as the Point Trigger under Source, the Source Point Trigger key
under Trig 2 Out automatically gets selected.
Trig 1 Out Polarity
This control sets the output to the Trig 1 Out connector to trigger on either the
positive or negative polarity.
The SCPI command applies to all Trig Out connectors and selects the trigger polarity
for the Trig 1 Out, or Trig 2 Out connector.
Command
191
:TRIGger|TRIGger1|TRIGger2[:SEQuence]:OUTPut:POLarity
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Input/Output
POSitive|NEGative
:TRIGger|TRIGger1|TRIGger2[:SEQuence]:OUTPut:POLarity?
Example
TRIG1:OUTP:POL POS
Preset
This is unaffected by a Preset but is set to POSitive on a "Restore Input/Output Defaults"
or "Restore System Defaults->All"
State
Saved
Saved in instrument state.
Trig 2 Out
This control selects the type of output signal that will be output from the Trig 2 Out
connector.
The SCPI command (detailed in"Trig 1 Out" on page 190) applies to all Trig Out
connectors and selects the type of output signal that Select the type of output signal
that will be output from the Trig 1 Out, or Trig 2 Out connectors.
TRIG2:OUTP HSWP
Example
TRIG2:OUTP GATE
Dependencies
The second Trigger output (Trig 2 Out) does not appear in all models; in models that
do not support it, the Trig 2 Out key is blanked, and sending the SCPI command for
this output generates an error, “Hardware missing; Not available for this model
number”. In models that do not support the Trigger 2 output, this error is returned if
trying to set Trig 2 Out and a query of Trig 2 Out returns OFF.
Trig 2 Out Polarity
This control sets the output to the Trig 2 Out connector to trigger on either the
positive or negative polarity.
The SCPI command (detailed in "Trig 1 Out" on page 190) applies to all Trig Out
connectors and selects the trigger polarity for the Trig 1 Out, or Trig 2 Out
connectors.
Example
TRIG2:OUTP:POL POS
Preset
This is unaffected by a Preset but is set to POSitive on a "Restore Input/Output Defaults"
or "Restore System Defaults->All"
Analog Out
This menu lets you control which signal is fed to the “Analog Out” connector on the
analyzer rear panel.
Remote Language Compatibility Measurement Application Reference
192
3 RLC Mode & Swept SA Measurement
Input/Output
In the Auto state, the Analog Output will automatically be set to the most sensible
setting for the current mode or measurement.
If you make a selection manually from the Analog Out menu, the manually selected
choice will remain in force until you change it (or re-select Auto), even if you go to a
mode or measurement for which the selected output does not apply.
Notes About Analog Outputs
Screen Video
This mode is similar to the Analog Output of the HP 8566 family and the Video Out
(opt 124) capability of the Keysight PSA analyzer (E444x), although there are
differences in the behavior.
Screen Video output changes while in FFT Sweeps, so for measurements that use
exclusively FFT Sweeps, or if the user manually chooses FFT Sweeps, the Screen
Video output will look different than it does in swept mode
Because the Screen Video output uses one of the two IF processing channels, only
one detector is available while Screen Video is selected. All active traces will
change to use the same detector as the selected trace when Screen Video is
activated.
Screen Video output is not available while any EMI Detector is selected (Quasi
Peak, RMS Average or EMI Average), because these detectors use both IF
processing channels. Consequently, if the user chooses an EMI Detector, there will
be no Screen Video output.
The output holds at its last value during an alignment and during a marker count.
After a sweep:
If a new sweep is to follow (as in Continuous sweep mode), the output holds at its
last value during the retrace before the next sweep starts. If the analyzer is in zerospan, there is no retrace, as the analyzer remains tuned to the Center Frequency
and does not sweep. Therefore, in zero-span, the output simply remains live
between display updates.
If no new sweep is to follow (as in Single sweep mode), the output remains live, and
continues to show the pre-detector data
This function depends on optional capability; the selection is not available blanked
and the command will generate an “Option not available” error unless you have
Option YAV or YAS licensed in your instrument.
The Screen Video function is intended to be very similar to the 8566 Video Output
and the PSA Option 124. However, unlike the PSA, it is not always on; it must be
switched on by the Screen Video key. Also, unlike the PSA, there are certain
dependencies (detailed above) – for example, the Quasi Peak Detector is
unavailable when Screen Video is on.
Furthermore, the PSA Option 124 hardware was unipolar and its large range was
padded to be exactly right for use as a Screen Video output. In the X-Series, the
hardware is bipolar and has a wider range to accommodate the other output
193
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Input/Output
choices. Therefore, the outputs won’t match up exactly and users may have to
modify their setup when applying the X-Series in a PSA application.
Log Video
Log Video shows the RF Envelope with the Reference equal to the Mixer Level. The
output is designed so that full scale (1 V) corresponds to -10 dBm at the mixer. The
full range (0-1 V) covers 192.66 dB; thus, 0 V corresponds to -202.66 dBm at the
mixer.
Because the Log Video output uses one of the two IF processing channels, only one
detector is available while Screen Video is selected. All active traces will change to
use the same detector as the selected trace when Log Video is activated.
Log Video output is not available while any EMI Detector is selected (Quasi Peak,
RMS Average or EMI Average), because these detectors use both IF processing
channels. Consequently, if the user chooses an EMI Detector, there will be no Log
Video output.
The output holds at its last value during an alignment, during a marker count, and
during retrace (after a sweep and before the next sweep starts).
This function depends on optional capability. The key will be blanked and the
command will generate an “Option not available” error unless you have Option YAV
licensed in your instrument.
Log Video output changes while in FFT Sweeps, so for measurements that use
exclusively FFT Sweeps, or if the user manually chooses FFT Sweeps, the Log
Video output will look different than it does in swept mode.
Linear Video
Linear Video shows the RF Envelope with the Reference equal to the Ref Level. The
scaling is set so that 1 V output occurs with an instantaneous video level equal to
the reference level, and 0 V occurs at the bottom of the graticule. This scaling gives
you the ability to control the gain without having another setup control for the key.
But it requires you to control the look of the display (the reference level) in order to
control the analog output.
This mode is ideal for looking at Amplitude Modulated signals, as the linear
envelope effectively demodulates the signal.
Because the Linear Video output uses one of the two IF processing channels, only
one detector is available while Linear Video is selected. All active traces will
change to use the same detector as the selected trace when Log Video is
activated.
Linear Video output is not available while any EMI Detector is selected (Quasi Peak,
RMS Average or EMI Average), because these detectors use both IF processing
channels. Consequently, if the user chooses an EMI Detector, there will be no
Linear Video output.
The output holds at its last value during an alignment and during a marker count
and during retrace (after a sweep and before the next sweep starts).
Remote Language Compatibility Measurement Application Reference
194
3 RLC Mode & Swept SA Measurement
Input/Output
This function depends on optional capability; the key will be blanked and the
command will generate an “Option not available” error unless you have Option YAV
licensed in your instrument.
Linear Video output changes while in FFT Sweeps, so for measurements that use
exclusively FFT Sweeps, or if the user manually chooses FFT Sweeps, the Linear
Video output will look different than it does in swept mode.
Demod Audio
When Analog Out is in the Auto state, this output is auto-selected when in the
Analog Demod mode or when Analog Demod Tune and Listen is operating in the
Swept SA measurement.
If any other Analog Output is manually selected when in the Analog Demod mode
or when Analog Demod Tune and Listen is operating in the Swept SA
measurement, a condition warning message appears.
This key only appears if the Analog Demod application (N9063A), the N6141A or
W6141A application, or Option EMC is installed and licensed, otherwise the key will
be blanked and the command will generate an “Option not available” error.
The output holds at its last value during an alignment and during a marker count. It
is not held between sweeps, in order for Tune and Listen to work properly.
When Demod Audio is the selected Analog Output, all active traces are forced to
use the same detector, and the CISPR detectors (QPD, EMI Avg, RMS Avg) are
unavailable
Command
:OUTPut:ANALog OFF|SVIDeo|LOGVideo|LINVideo|DAUDio
:OUTPut:ANALog?
:OUTPut:ANALog:AUTO OFF|ON|0|1
:OUTPut:ANALog:AUTO?
Example
OUTP:ANAL SVIDeo causes the analog output type to be Screen Video
OUTP:ANAL:AUTO ON
Preset
This is unaffected by Preset but is set to DAUDio on a "Restore Input/Output Defaults" or
"Restore System Defaults->All
ON
State
saved
Saved in Input/Output state.
Backwards Compatibility Notes
Prior to A.04.00, OFF was the default functionality except when in the Analog
Demod application or with Tune and Listen, in which case it was DAUDio, and there
was no selection menu. So for backwards compatibility with earlier X-Series
firmware versions, Auto (:OUTP:ANAL:AUTO ON) will duplicate the prior behavior.
The DNWB and SANalyzer parameters, which were legal in PSA but perform no
function in the X-Series, are accepted without error.
Analog Outputs
195
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Input/Output
Source
Example
Notes
Off
OUTP:ANAL
OFF
The Analog Output is off.
Screen
Video
OUTP:ANAL
SVID
Selects the analog output to be the screen video signal. In this mode, the
pre-detector data is output to the Analog Out connector. The output
looks very much like the trace displayed on the analyzer’s screen, and
depends on the Log/Lin display Scale, Reference Level, and dB per
division, but is not influenced by the selected detector or any digital
flatness corrections or trace post-processing (like Trace Averaging).
Log
Video
OUTP:ANAL
LOGV
Selects the analog output to be the log of the video signal. In this mode,
the pre-detector data is output to the Analog Out connector with a Log
scaling. The output is referenced to the current level at the mixer, does
not depend on display settings like Reference Level or dB per division,
and it is not influenced by the selected detector or any digital flatness
corrections or trace post-processing (like Trace Averaging), but does
change with input attenuation.
Linear
Video
OUTP:ANAL
LINV
Selects the analog output to be the envelope signal on a linear (voltage)
scale. In this mode, the pre-detector data is output to the Analog Out
connector with a Linear scaling. The output is based on the current
Reference Level, and is not influenced by the selected detector or any
digital flatness corrections or trace post-processing (like Trace
Averaging).
Demod
Audio
OUTP:ANAL
DAUD
Selects the analog output to be the demodulation of the video signal.
When Demod Audio is selected, the demodulated audio signal appears at
this output whenever the Analog Demod application is demodulating a
signal or when Analog Demod Tune and Listen is operating in the Swept
SA measurement. When Analog Out is in the Auto state, this output is
auto-selected when in the Analog Demod mode or when Analog Demod
Tune and Listen is operating in the Swept SA measurement.
Output Ranges
Analog
Out
Normal
Range
exc. (10%
overrange)
Scale Factor
Notes
Off
1V
Screen
Video
0 – 1 V open
circuit
10%/division
8566 compatible
Log
Video
0– 1V
terminated
1/(192.66
dB/V)
dB referenced to mixer level, 1V out for –10 dBm at
the mixer.
Linear
Video
0– 1V
terminated
100%/V
Linear referenced to Ref Level, 1 V out for RF
envelope at the Ref Level.
Remote Language Compatibility Measurement Application Reference
196
3 RLC Mode & Swept SA Measurement
Input/Output
Analog
Out
Normal
Range
exc. (10%
overrange)
Scale Factor
Demod
Audio
(varies with analyzer setting)
Notes
Digital Bus Out On/Off
When Bus Out is on, all acquisitions are streamed to the output port including
acquisitions for internal purposes such as Alignment. The internal processing and
routing of acquisitions continues as usual and is unaffected by the state of Bus Out.
When Bus Out is off, no signal appears on the LVDS port.
Command
:OUTPut:DBUS[1][:STATe] ON|OFF|1|0
:OUTPut:DBUS[1][:STATe]?
Example
OUTP:DBUS ON
Preset
This is unaffected by a Preset but is set to Off on a "Restore Input/Output Defaults" or
"Restore System Defaults -> All"
State
Saved
Saved in Input/Output state.
Wideband Digital Bus (Option RTS)
The Wideband Digital Bus control turns on the LVDS port on the Wideband IF, which
causes the I/Q pairs from the current measurement to be sent to this port. The
control is grayed out unless in the RTSA measurement application, which is the only
measurement that supports wideband streaming.
When Wideband Digital Bus is on, the internal processing and routing of acquisitions
continues as usual and the display of measurement data is unaffected.
When Wideband Digital Bus is off, no signal appears on the LVDS port.
Requires option RTS or control is not displayed.
Command
OUTPut:DBUS2[:STATe] OFF|ON|0|1
OUTPut:DBUS2[:STATe]?
Example
OUTP:DBUS2 ON
Preset
OFF (set by Restore Input/Output Defaults)
State Saved
Saved in Input/Output state.
Notes
If this command is sent while running a measurement that does not support
Wideband Digital Bus, the message “Settings conflict; Feature not supported for
197
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Input/Output
this measurement” is displayed.
Dependencies
Digital Bus and Wideband Digital Bus cannot be on at the same time, so:
– When Wideband Bus is turned on, if Digital Bus is already on, an advisory
message is displayed, “Wideband Digital Bus On, Digital Bus (narrow band)
forced to Off.”
– When Digital Bus is turned on, if Wideband Digital Bus is already on, an advisory
message is displayed, “Digital Bus (narrow band) On, Wideband Digital Bus
forced to Off.”
Aux IF Out
This menu controls the signals that appear on the SMA output on the rear panel
labeled “AUX IF OUT".
The Aux IF Out functionality is only valid for RF and External Mixer inputs. When using
the External Mixing path, the Aux IF Out levels (for all three Options CR3, CRP, and ALV)
will be uncalibrated because the factory default Aux IF level was set to accommodate
the expected IF levels for the RF path.
Aux IF Out is valid for the RF Input and for the External Mixer input. In external mixing,
the Aux IF output level is set by factory default to accommodate expected IF levels for
the RF path. When using the External Mixing path, the Aux IF Out levels (for all three
options CR3, CRP and ALV) will therefore be uncalibrated.
The control does not appear in models that do not support the Aux IF Out.
Notes on Aux IF Outputs
Second IF
The frequency of the 2nd IF depends on the current IF signal path as shown in the
table below:
IF Path Selected
Frequency of “Second IF” Output
10 MHz
322.5 MHz
25 MHz
322.5 MHz
40 MHz
250 MHz
85-160
300 MHz
255 MHz
750 MHz
510 MHz
877.1484375 MHz
The signal quality, such as signal to noise ratio and phase noise, are excellent in
this mode.
The Second IF choice does not appear unless Option CR3 is installed.
Remote Language Compatibility Measurement Application Reference
198
3 RLC Mode & Swept SA Measurement
Input/Output
Arbitrary IF
The bandwidth of this IF output varies with band and center frequency, but is about
40 MHz at the -3 dB width. When the output is centered at lower frequencies in its
range, signal frequencies at the bottom of the bandwidth will “fold”. For example,
with a 40 MHz bandwidth (20 MHz half-bandwidth), and a 15 MHz IF center, a
signal -20 MHz relative to the spectrum analyzer center frequency will have a
relative response of about -3 dB with a frequency 20 MHz below the 15 MHz IF
center. This -5 MHz frequency will fold to become a +5 MHz signal at the IF output.
Therefore, lower IF output frequencies are only useful with known band-limited
signals.
The Arbitrary IF choice does not appear unless Option CRP is installed.
Fast Log Video
The output is off during an alignment but not during a marker count, and is not
blanked during retrace (after a sweep and before the next sweep starts).
The Fast Log Video choice does not appear unless Option ALV is installed.
Command
:OUTPut:AUX SIF|AIF|LOGVideo|OFF
:OUTPut:AUX?
Example
OUTP:AUX:LOGV
Preset
This is unaffected by a Preset but is set to OFF on a "Restore Input/Output Defaults" or
"Restore System Defaults->All”
State
Saved
Saved in Input/Output state.
Backwards Compatibility Notes
In the PSA, the IF output has functionality equivalent to the "Second IF" function in
the X-Series’ Aux IF Out menu. In the X-Series, it is necessary to switch the Aux IF
Out to “Second IF” to get this functionality, whereas in PSA it is always on, since
there are no other choices. Hence a command to switch this function to “Second IF”
will have to be added by customers migrating from PSA who use the IF Output in
PSA.
Various Aux IF Outputs
199
Source
Example
Notes
Off
OUTP:AUX
OFF
In this mode nothing comes out of the “AUX IF OUT” connector on the
rear panel. The connector appears as an open-circuit (that is, it is not
terminated in any way).
Second
IF
OUTP:AUX
SIF
In this mode the 2nd IF output is routed to the rear panel connector.
Annotation on the menu panel shows the current 2nd IF frequency in use
in the analyzer.
Arbitrary
IF
OUTP:AUX
AIF
In this mode the 2nd IF output is mixed with a local oscillator and mixer to
produce an arbitrary IF output between 10 MHz and 75 MHz with 500 kHz
resolution. The phase noise in this mode will not be as good as in Second
IF mode.
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Input/Output
Source
Example
Notes
The IF output frequency is adjustable, through an active function which
appears on the menu panel, from 10 MHz to 75 MHz with 500 kHz
resolution.
In instruments with Options B2X or B5X, the
Arbitrary IF Output is only practical when
the IF Bandwidth is <= 40 MHz, IF Path is <=
40 MHz, or FFT Width is <= 40 MHz.
Fast Log
Video
OUTP:AUX
LOGV
In this mode the 2nd IF output is passed through a log amp and the log
envelope of the IF signal is sent to the rear panel. The open circuit output
level varies by about 25 mV per dB, with a top-of-screen signal producing
about 1.6 Volts. The output impedance is nominally 50 ohms.
This mode is intended to meet the same needs as Option E4440A-H7L
Fast Rise Time Video Output on the Keysight E4440A PSA Series,
allowing you to characterize pulses with fast rise times using standard
measurement suites on modern digital scopes.
Remote Language Compatibility Measurement Application Reference
200
3 RLC Mode & Swept SA Measurement
Marker
Marker
The Marker panel accesses the Marker menu. A marker can be placed on a trace to
allow the value of the trace at the marker point to be determined precisely.
When Marker is pressed, if the selected marker is Off, it is set to Normal and placed it
at the center of the screen on the trace determined by the Marker Trace rules. If the
selected marker is already On it will remain at the frequency/time and amplitude to
which it is already set, even if this means it will be offscreen.
The fundamental marker operation involves setting a Marker’s X-Axis value and then
reading the marker’s Y-Axis value. From the front panel you do this using the Marker
menu and the green marker readout in the upper right corner of the display.
Markers may also be used in pairs to read the difference (or delta) between two data
points. They can be used in Marker Functions to do advanced data processing, or to
specify operating points in functions like Signal Track and N dB Points.
Programmatically, to set the Marker’s control mode, use the :CALCulate:MARKer
[n]:MODE command. To set the Marker’s X-Axis value use the :CALCulate:MARKer
[n]:X <freq|time> command. To query the Marker’s Y-Axis value, use the
:CALCulate:MARKer[n]:Y? query.
In earlier HP/Agilent/Keysight analyzers, markers stayed at the same position on
the display even when you changed frequency. In the X-Series, markers stay at the
frequency they are set to, even if you change Center Frequency. So your marker will
move, possibly offscreen, when you change frequency. This is a superior method for
a number of reasons but it may take some getting used to if you are used to placing a
marker at center screen and then changing Center Frequency and having the marker
stay there.
Settings Tab
Marker Frequency|Time
The Marker Frequency control is the fundamental control that you use to move a
marker around on the trace. Because it is the default active function in the Marker
menu, all you need to do is press Marker and turn the knob to move the marker left
and right on the display. This is always the first control on any Marker menu page
which follows the Selected Marker.
When in Zero Span (for measurements that support Zero Span), the label on this
control changes to “Marker Time”. When the Marker Mode is Delta, the label
changes to “Marker D Frequency” or Marker D Time”
The SCPI command sets the marker X Axis value in the current marker X Axis Scale
unit. The marker that is addressed becomes the selected marker. It has no effect
(other than to cause the marker to become selected) if the control mode is Off, but it
is the SCPI equivalent of entering an X value if the control mode is Normal, Delta, or
Fixed.
Command
201
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:X <freq|time>
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Marker
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:X?
Preset
After a preset, if X is queried with no value sent first, the center of screen value will be
returned. This will depend on the frequency range of the instrument. 13.255 GHz is
correct for the 26 GHz instruments only (Option 526).
Min/Max
Min:
–∞ (minus infinity)
Max:
+∞ (plus infinity)
Notes
If no suffix is sent it will use the fundamental units for the current marker X Axis
Scale. If a suffix is sent that does not match the current marker X Axis Scale unit, an
invalid suffix message will be generated.
If the specified marker is Fixed and a Marker Function is on, a message is
generated. If the key is pressed, an advisory message is generated. If the
equivalent SCPI command is sent, this same message is generated as part of a “–
221, Settings conflict” warning.
The query returns the marker’s absolute X Axis value if the control mode is Normal
or Fixed. It returns the offset from the marker’s reference marker if the control mode
is Delta. The query is returned in the fundamental units for the current marker X
Axis scale: Hz for Frequency and Inverse Time, seconds for Period and Time. If the
marker is Off the response is not a number.
Dependencies
Grayed out and displays three dashes for the value when the selected Marker is
Off.
You cannot directly set the X value of a Fixed marker which has a marker function
turned on.. If an attempt is made to actually adjust it while a Marker Function is on,
a warning message is generated.
Marker Backwards Compatibility
In earlier HP/Agilent/Keysight analyzers, markers were position markers, which
means that Normal and Delta markers stayed at the same screen position when X
Axis parameters were changed. So a marker at center screen stayed at center
screen even if Center Frequency was changed (which means that the marker’s
frequency changed). In the X-Series, markers are value markers, which means that
when the analyzer’s X Axis settings are changed, the marker’s X Axis value in
fundamental X Axis units remains unchanged. For example, if you put a marker at a
particular frequency, it will stay at that frequency regardless of whether or not you
change the Center Frequency of the analyzer, even if that means that the marker
ends up offscreen.
While this change resulted in an overall higher level of usability of the marker
system, there are some use cases where the user depends on the marker staying
at the center of the screen. The most common one is where the user turns on a
marker at center screen and uses it to measure the trace amplitude at the center
frequency or at a series of center frequencies, without the need to ever move the
Remote Language Compatibility Measurement Application Reference
202
3 RLC Mode & Swept SA Measurement
Marker
marker. In the X-Series, to mimic the legacy behavior for this use case, the user
must turn the marker off and then back on after changing the center frequency of
the analyzer. This causes the marker to reappear in the center of the screen.
Also as a result of the change from position markers to value markers, markers can
be at a frequency which is offscreen, whereas in the past, they were clipped to the
screen edges and hence were never offscreen. Users who depended on this
clipping behavior to force markers to the edges of the screen will have to rewrite
their code. Furthermore, since markers could never be offscreen they always
returned a valid result. In the X-Series, markers which are offscreen return not a
number as a result; hence the potential now exists for not a number to be returned
for a marker query.
Setting the Marker X Position in Trace Points
The command below sets the marker X position in trace points. It has no effect if the
marker control mode is Off. But it is the SCPI equivalent of entering a value if the
control mode is Normal or Delta or Fixed – except the setting is in trace points
rather than X Axis Scale units.
The entered value in Trace Points is immediately translated into the current X Axis
Scale units for setting the value of the marker. The marker’s value in X Axis Scale
Units, NOT trace points, will be preserved if a change is made to the X Axis scale
settings. Thus, if you use this command to place a marker on bucket 500, which
happens at that time to correspond to 13 GHz, and then you change the Start
Frequency so that bucket 500 is no longer 13 GHz, the marker will stay at 13 GHz,
NOT at bucket 500! This is important to realize as it differs from the behavior of past
HP/Agilent/Keysight analyzers.
Command
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:X:POSition <real> :CALCulate:MARKer
[1]|2|3|4|5|6|7|8|9|10|11|12:X:POSition?
:CALCulate:MARKer[1]|2|3|4:X:POSition:CENTer
This alias is provided for compatibility with the Band Power function in PSA and ESA.
Preset
After a preset, if X is queried with no value sent first, the center of screen value will be
returned. So if per default, the number of Trace points is 1001, the center value will be
500.
Min/Max
0/Number of trace points – 1
Marker Mode
There are four control modes for markers:
– Normal (POSition) - A marker that can be moved to any point on the X Axis by
specifying its X Axis value, and who's absolute Y Axis value is then the value of
the trace point at that X Axis value.
– Delta (DELTa) - A marker that can be moved to any point on the X Axis by
specifying its X Axis offset from a reference marker, and whose absolute Y Axis
value is then the value of the trace point at that X Axis value.
203
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Marker
– Fixed (FIXed) - A marker whose X Axis and Y Axis values may be directly or
indirectly specified by you, but whose Y Axis value remains fixed, once specified,
and does not follow the trace. Fixed markers are useful as reference markers for
Delta markers, as operands in a Peak Search operation, and as arbitrary
reference points settable by you. These markers are represented on the display
by an “X” rather than a diamond. Not every measurement supports Fixed
markers.
– Off (OFF) - A marker which is not in use.
See "Marker Modes" on page 204 for more information.
The SCPI command in the table below selects the marker and sets the marker
control mode as described under Normal, Delta, Fixed and Off, below. All
interactions and dependencies detailed under the key description are enforced when
the remote command is sent.
Command
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:MODE
POSition|DELTa|FIXed|OFF
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:MODE?
Preset
OFF (all markers)
State
Saved
The marker control mode (Normal, Delta, Fixed, Off) and X Axis value are saved in
instrument state.
Backwards Compatibility
In legacy analyzers, only a Reference marker could be Fixed, and it was always
Fixed. Additionally it could not be moved. In the X-Series, any marker can be set to
Fixed and can be moved to any X or Y value.
In pre X-Series analyzers, pressing Delta (or sending the
CALC:MARK:MODE:DELTa command) always moved the reference marker to the
delta marker. Now it only does so if the marker was already a delta marker.
Command
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:STATe OFF|ON|0|1
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:STATe?
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:STATe ON|1
Setting a marker which is OFF to ON or 1 selects the marker, puts it in Normal mode
and places it at the center of the screen.
Setting a marker which is not OFF to ON has no effect (does not change its control
mode).
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:MODE SPAN|BAND
To support band function backwards compatibility, both of these legacy parameters are
accepted and aliased to POSition. They are never returned to a query.
Example
CALC:MARK2:STAT ON sets Marker 2 to Normal if it was off; otherwise it does nothing.
The response to the query will be ON unless the marker is OFF.
Marker Modes
Remote Language Compatibility Measurement Application Reference
204
3 RLC Mode & Swept SA Measurement
Marker
Value
Example
Notes
Normal
:CALC:MARK2:MODE
POS
A Normal marker can be moved to any point on the X Axis by
specifying its X Axis value. Its absolute Y Axis value is then the
value of the trace point at that X Axis value.
Delta
:CALC:MARK2:MODE
DELT
In Delta mode the marker result shows the relative result
between the selected (Delta) marker and its reference marker. A
delta marker can be moved to any point on the X Axis by
specifying its X Axis offset from a reference marker. Its absolute
Y Axis value is then the value of the trace point at that X Axis
value.
Fixed
:CALC:MARK2:MODE
FIX
A fixed marker is fixed in the sense that it stays where you place
it. It can be directly moved in both X and Y. It can be moved with
a Peak Search. It can also be indirectly moved by re-zeroing the
delta if it is a relative marker. If it is moved, it again becomes
fixed at the X Axis point it moved to and it has a Y-axis result
that it took on when it moved there. If a Normal or Delta marker
is changed to Fixed it becomes fixed at the X Axis point it was at,
and with the Y-axis result it had when it was set to Fixed. In
Fixed mode the marker result shows:
– If no Marker Function is on, the absolute X Axis and Y axis
value of the marker
– If a Marker Function is on, the X Axis value and the Y-axis
function result the marker had when it became fixed.
Off
:CALC:MARK2:MODE
OFF
Off turns off the marker, removes the marker annunciation from
the display, turns off any active function and any marker
function, and resets the following properties to their default
value:
– X Axis scale: Auto
– Band Span: 0
– Auto Trace: On Off does not affect which marker is selected.
Delta Marker (Reset Delta)
Pressing this control is exactly the same as pressing the “Delta” selection on the
Marker Mode radio button. The selected marker becomes a Delta Marker. If the
selected marker is already a Delta marker, the reference marker is moved to the
current position of the selected marker, thus resetting the Delta to zero.
Marker Table
When set to On, the display is split into a measurement window and a marker data
display window. For each marker which is on, information is displayed in the data
display window, which includes the marker number, control mode, trace number, X
205
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Marker
axis scale, X axis value, and the Y-axis result. Additional information is shown for
markers which have marker functions turned on.
Turning the Marker Table on turns the Peak Table off and vice versa.
:CALCulate:MARKer:TABLe[:STATe] OFF|ON|0|1
Command
:CALCulate:MARKer:TABLe[:STATe]?
CALC:MARK:TABL ON turns on the marker table.
Example
CALC:MARK:TABL?
Preset
OFF
State Saved
The on/off state of the Marker Table is saved in instrument state.
Marker Settings Diagram
The Marker Settings Diagram lets you configure the Marker system using a visual
utility.
All Markers Off
Turns off all markers.
Command
:CALCulate:MARKer:AOFF
Example
CALC:MARK:AOFF
In the Swept SA measurements, this sets the selected marker to 1.
Remote Language Compatibility Measurement Application Reference
206
3 RLC Mode & Swept SA Measurement
Marker
Couple Markers
When this function is On, moving any marker causes an equal X Axis movement of
every other marker which is not Fixed or Off. By “equal X Axis movement” we mean
that we preserve the difference between each marker’s X Axis value (in the
fundamental x-axis units of the trace that marker is on) and the X Axis value of the
marker being moved (in the same fundamental x-axis units).
Note that Fixed markers do not couple. They stay where they were while all the
other markers move. Of course, if a Fixed marker is being moved, all the non-fixed
markers do move with it.
This may result in markers going off screen.
:CALCulate:MARKer:COUPle[:STATe] OFF|ON|0|1
Command
:CALCulate:MARKer:COUPle[:STATe]?
Example
:CALC:MARK:COUP ON sets Couple Markers on.
Preset
SA:OFF, presets on Mode Preset and All Markers Off
RTSA:OFF
State Saved
Saved in instrument state.
Peak Search Tab
Peak Search
Pressing the Peak Search control moves the selected marker to the trace point
which has the maximum y-axis value for that marker’s trace.
Pressing the Peak Search hardkey automatically moves you to the Peak Search page of
the Marker menu AND performs a Peak Search.
In the Swept SA measurement, the Pk Search Config menu enables you to define specific
search criteria to determine which signals can be considered peaks, excluding unwanted
signals from the search.
Command
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:MAXimum
Example
CALC:MARK2:MAX performs a peak search using marker 2.
CALC:MARK2:Y? queries the marker amplitude (Y-axis) value for marker 2.
CALC:MARK2:X? queries the marker frequency or time (X-axis) value for marker 2.
SYST:ERR? can be used to query the errors to determine if a peak is found. The message
“No peak found” will be returned after an unsuccessful search
More Information
207
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Marker
The behavior of a Peak Search is dependent on settings under the Peak Criteria
control on the second page of the menu. If Same as “Next Peak” Criteria is
selected, and either Pk Excursion or Pk Threshold are on, a signal must meet those
criteria to be considered a peak. If no valid peak is found, a “No peak found”
message is generated and the marker is not moved. When Highest Peak is on, or
both Pk Excursion and Pk Threshold are off, the marker is always placed at the
point on the trace with the maximum y-axis value, even if that point is on the very
edge of the trace (exception: negative frequencies and signals close to the LO are
not searched at all.
Pressing Peak Search with the selected marker off causes the selected marker to
be set to Normal at the center of the screen, then a peak search is immediately
performed.
Pressing the front panel Peak Search key always does a peak search. Occasionally,
you may need to get to the Peak Search menu key functions without doing a peak
search. You can do this by first accessing the Peak Search menu. Then go to the
other menus that you need to access. Finally, you can get back to the Peak Search
key menu by using the front panel Return key and pressing it as many times as
required to navigate back through the previously accessed menus until you get
back to the Peak Search menu.
Next Peak
Pressing Next Peak moves the selected marker to the peak that has the next highest
amplitude less than the marker current value. Only peaks which meet all enabled
peak criteria are considered. If there is no valid peak lower than the current marker
position, a “No peak found” message is generated and the marker is not moved.
If the selected marker was off, then it is turned on as a normal marker and a peak
search is performed.
Command
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:MAXimum:NEXT
Sending this command selects the subopcoded marker.
Example
CALC:MARK2:MAX:NEXT
selects marker 2 and moves it to the peak that is closest in amplitude to the current
peak, but the next lower value.
Next Pk Right
Pressing Next Peak moves the selected marker to the peak that has the next highest
amplitude less than the marker current value. Only peaks which meet all enabled
peak criteria are considered. If there is no valid peak lower than the current marker
position, a “No peak found” message is generated and the marker is not moved.
If the selected marker was off, then it is turned on as a normal marker and a peak
search is performed.
Remote Language Compatibility Measurement Application Reference
208
3 RLC Mode & Swept SA Measurement
Marker
Command
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:MAXimum:RIGHt
Sending this command selects the subopcoded marker.
Example
CALC:MARK2:MAX:RIGH selects marker 2 and moves it to the next peak to the right of
the current marker position.
Next Pk Left
Pressing Next Pk Left moves the selected marker to the nearest peak left of the
current marker that meets all enabled peak criteria. If there is no valid peak to the
left of the current marker position, a “No peak found” message is generated and the
marker is not moved.
If the selected marker was off, then it is turned on as a normal marker and a peak
search is performed.
Command
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:MAXimum:LEFT
Example
CALC:MARK2:MAX:LEFT selects marker 2 and moves it to the next peak to the left of the
current marker position.
Minimum Peak
Moves the selected marker to the minimum y-axis value on the current trace.
Minimum (negative) peak searches do not have to meet the peak search criteria. It
just looks for the lowest y-axis value. If the selected marker is Off, it is turned on
before the minimum search is performed.
Command
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:MINimum
Sending this command selects the subopcoded marker.
Example
CALC:MARK:MIN selects marker 1 and moves it to the minimum amplitude value.
Pk-Pk Search
Finds and displays the amplitude and frequency (or time, if in zero span) differences
between the highest and lowest y-axis value. It places the selected marker on the
minimum value on its selected trace. And it places that marker’s reference marker on
the peak of its selected trace.
This function turns on the reference marker and sets its mode to Fixed or Normal if it
is not already on. (These markers may be on two different traces.)
The rules for finding the maximum peak are exactly the same as for Peak Search,
including the use of the peak criteria rules. However, the minimum trace value is not
required to meet any criteria other than being the minimum y-axis value in the trace.
If the selected marker is off, a delta type marker is turned on and the peak-to-peak
search is done. If the selected marker is on, but it is not a delta marker, then it is
209
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Marker
changed to delta which turns on the reference marker if needed, and then it
performs the peak-to-peak function.
Command
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:PTPeak
Sending this command selects the subopcoded marker.
Example
CALC:MARK:PTP
CALC:MARK:Y? queries the delta amplitude value for marker 1.
Notes
Turns on the Marker Δ active function.
Dependencies
Pk-Pk Search is grayed out when Coupled Markers is on.
Couplings
The selected marker becomes a delta marker if not already in delta mode.
Marker Delta
This function is exactly the same as the “Delta” selection on the Marker Mode radio
button on the Settings tab. The selected marker becomes a Delta Marker. If the
selected marker is already a Delta marker, the reference marker is moved to the
current position of the selected marker, thus resetting the Delta to zero.
The is duplicated here in the Peak Search Menu to allow you to conveniently perform
a peak search and change the marker’s control mode to Delta without having to
access two separate menus.
Marker -> CF
Assigns the selected marker’s frequency to the Center Frequency setting.
The is duplicated here in the Peak Search Menu to allow you to conveniently perform
a peak search and marker to CF without having to access two separate menus.
Marker -> Ref Lvl
Assigns the selected marker’s level to the Reference Level setting. The is duplicated
here in the Peak Search Menu to allow you to conveniently perform a peak search
and marker to RL without having to access two separate menus.
Peak Search Config Tab
Peak Threshold
Turns the peak threshold requirement on/off and sets the threshold value. The peak
threshold value defines the minimum signal level (or min threshold) that the peak
identification algorithm uses to recognize a peak.
Remote Language Compatibility Measurement Application Reference
210
3 RLC Mode & Swept SA Measurement
Marker
When both Pk Excursion and Pk Threshold are on, a signal must rise above the Pk
Threshold value by at least the Peak Excursion value and then fall back from its local
maximum by at least the Peak Excursion value to be considered a peak.
For example, if a threshold value of –90 dBm is selected, the peak search algorithm
will only consider signals with amplitude greater than the –90 dBm threshold. If a
threshold value of –90 dBm is selected, and Peak Excursion is On and set to 6 dB, the
peak search algorithm will only consider signals with amplitude greater than the –90
dBm threshold which rise 6 dB above the threshold and then fall back to the
threshold.
If a signal comes onto the screen falling and falls all the way to the threshold without
ever rising, it is considered a peak at the far left edge of the display. Similarly, if a signal
rises from the threshold and leaves the screen without ever falling, it is considered a
peak at the far right edge of the display.
Command
:CALCulate:MARKer:PEAK:THReshold <ampl>
:CALCulate:MARKer:PEAK:THReshold?
:CALCulate:MARKer:PEAK:THReshold:STATe OFF|ON|0|1
:CALCulate:MARKer:PEAK:THReshold:STATe?
Example
CALC:MARK:PEAK:THR:STAT ON turns on the threshold criterion.
CALC:MARK:PEAK:THR –60 dBm sets the threshold to –60 dBm.
Preset
–90.0 dBm
ON
Min/Max
Min:
The current displayed Ref Level – 200 dB. The current displayed Ref Level is the current
Ref Level, offset by the Ref Level Offset.
Max:
The current displayed Ref Level. This means the current Ref Level, offset by the Ref Level
Offset.
State
Saved
Saved in instrument state.
Dependencies
When Ref Level Offset changes, Peak Threshold must change by the same amount.
Couplings
Whenever you adjust the value of Pk Threshold, the Peak Threshold Line is turned
on and, if Peak Excursion is also on, the Peak Excursion Region is displayed.
Peak Excursion
Turns the peak excursion requirement on/off and sets the excursion value. The value
defines the minimum amplitude variation (rise and fall) required for a signal to be
identified as peak. For example, if a value of
211
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Marker
6 dB is selected, peak search functions like the marker Next Pk Right function move
only to peaks that rise and fall 6 dB or more.
When both Pk Excursion and Pk Threshold are on, a signal must rise above the Pk
Threshold value by at least the Peak Excursion value and then fall back from its local
maximum by at least the Peak Excursion value to be considered a peak
In the event that a sequence of trace points with precisely the same values represents
the maximum, the leftmost point is found.
If a signal comes onto the screen falling and falls all the way to the threshold without
ever rising, it is considered a peak at the far left edge of the display. Similarly, if a signal
rises from the threshold and leaves the screen without ever falling, it is considered a
peak at the far right edge of the display.
See "More Information" on page 212.
Command
:CALCulate:MARKer:PEAK:EXCursion <rel_ampl>
:CALCulate:MARKer:PEAK:EXCursion?
Example
:CALC:MARK:PEAK:EXC:STAT ON :CALC:MARK:PEAK:EXC 30 DB sets the minimum peak
excursion requirement to 30 dB
Preset
6.0 dB
Min/Max
0.0 dB/100.0 dB
State
Saved in instrument state.
saved
Dependencies
Available only when Y axis unit is amplitude units, otherwise grayed out.
Couplings
Whenever you adjust the value of Pk Excursion (with the knob, step keys, or by
completing a numeric entry), if the Peak Threshold is turned ON, the Peak
Threshold Line is turned on and the Peak Excursion Region is displayed.
More Information
If two signals are very close together and the peak excursion and threshold criteria
are met at the outside edges of the combined signals, this function finds the highest
of these two signals as a peak (or next peak). However, if a signal appears near the
edge of the screen such that the full extent of either the rising or falling edge
cannot be determined, and the portion that is on screen does not meet the
excursion criteria, then the signal cannot be identified as a peak.
When measuring signals near the noise floor, you can reduce the excursion value
even further to make these signals recognizable. To prevent the marker from
identifying noise as signals, reduce the noise floor variations to a value less than
the peak-excursion value by reducing the video bandwidth or by using trace
averaging.
Remote Language Compatibility Measurement Application Reference
212
3 RLC Mode & Swept SA Measurement
Marker
Peak Threshold Line
Turns the peak threshold line on or off. Preset state is Off. No equivalent SCPI
command.
The Peak Threshold line is green and has the value of the peak threshold (for
example, “–20.3 dBm”) written above its right side, one pixel above the line itself. If
Peak Excursion is ON it shows on the left side as a region above the Peak Threshold
line. As with all such lines (Display Line, Trigger Level line, etc.) it is drawn on top of
all traces.
This function is automatically set to ON (thus turning on the Peak Threshold line)
whenever the value of Peak Threshold or Peak Excursion becomes the active
function, unless Peak Threshold is OFF. It is automatically set to OFF whenever Peak
Threshold is set to OFF. Manually turning it ON automatically turns on Pk Threshold.
The Peak Excursion part is on whenever the Pk Threshold part is on, unless Peak
Excursion is OFF.
Peak Search Mode
This control lets you decide what kind of search you want to do when the Peak
Search key is pressed (or the equivalent SCPI command sent).
Note that there are two “types” of peak search functions. One type is the “Peak
Search” type, the other type is the “Next Peak” type. “Next Peak” searches (for
example, Next Peak, Next Pk Left, Next Pk Right) are qualified by using the Excursion
and Threshold criteria. The “Peak Search” type of search simply finds the highest
point on the trace, subject to the peak-search qualifications.
213
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Marker
However, using the Peak Search Mode control, you can change the “Peak Search”
type of search so that it also uses the Excursion and Threshold criteria. This allows
you to find the Maximum point on the trace that also obeys the Excursion and/or
Threshold criteria. This would be useful if, for example, you did not want to perform
the Peak Search at all unless there was a signal on the screen above a certain level.
When Highest Peak is selected, pressing Peak Search simply finds the highest peak
on the marker’s trace. When Use Excursion & Threshold is selected, the search is
also qualified by the Excursion and Threshold values (as long as these criteria are
On).
Note that this control also affects the Continuous Peak Search and the Peak Search
half of Pk-Pk search.
Command
:CALCulate:MARKer:PEAK:SEARch:MODE MAXimum|PARameter
:CALCulate:MARKer:PEAK:SEARch:MODE?
Example
CALC:MARK:PEAK:SEAR:MODE MAX sets Highest Peak mode
CALC:MARK:PEAK:SEAR:MODE PAR sets Excursion & Threshold mode
Preset
MAXimum
Range
Highest Peak|Use Excursion & Threshold
State
Saved
Saved in instrument state.
Backwards Compatibility
This control was a submenu called “Peak Search” Criteria in the X-Series Amodels, was a submenu called Peak Search Type in the ESA, and in the PSA was
not a submenu but a single control called Peak Search with a toggle between
Param and Max.
Nonetheless, the functionality and SCPI commands are identical in all four, only
the structure of the user interface is different.
Peak Table
Turns Peak Table on/off. When turned on, the display is split into a measurement
window and a peak table display window.
When the Peak Table turns on, if Peak Threshold is On then it becomes the active
function.
Turning the Peak Table on turns the Marker Table off and vice versa.
Command
:CALCulate:MARKer:PEAK:TABLe:STATe OFF|ON|0|1
:CALCulate:MARKer:PEAK:TABLe:STATe?
Example
CALC:MARK:PEAK:TABL:STAT ON
Preset
OFF
Remote Language Compatibility Measurement Application Reference
214
3 RLC Mode & Swept SA Measurement
Marker
State Saved
Saved in instrument state.
Peak Table Sort
Sets the peak table sorting routine to list the peaks in order of descending amplitude
or ascending frequency. The remote command can also be used to sort the peaks
found using the :CALCulate:DATA:PEAKs command (see the Trace key
documentation).
Command
:CALCulate:MARKer:PEAK:SORT FREQuency|AMPLitude
:CALCulate:MARKer:PEAK:SORT?
Example
CALC:MARK:PEAK:SORT AMPL
CALC:MARK:PEAK:SORT?
Preset
AMPLitude
State Saved
Saved in instrument state.
Peak Table Readout
Shows up to twenty signal peaks as defined by the setting:
All (ALL) - lists all the peaks defined by the peak criteria, in the current sort setting.
Above Display Line (GTDLine) - lists the peaks that are greater than the defined
display line, and that meet the peak criteria. They are listed in the current sort order.
Below Display Line (LTDLine) - lists the peaks that are less than the defined display
line, and that meet the peak criteria. They are listed in the current sort order.
If the Peak Threshold and/or the Peak Excursion are turned on, then only peaks that
meet the defined criteria will be found.
Turning Display Line off forces Readout to ALL.
If GTDL or LTDL, then if the display line is not already on, it is turned on (it has to be
on or it cannot be used to exclude peaks).
See "More Information" on page 216
Command
:CALCulate:MARKer:PEAK:TABLe:READout ALL|GTDLine|LTDLine
:CALCulate:MARKer:PEAK:TABLe:READout?
Example
CALC:MARK:PEAK:TABL:READ ALL
CALC:MARK:PEAK:TABL:READ GTDL
CALC:MARK:PEAK:TABL:READ LTDL
215
Preset
ALL
State Saved
Saved in instrument state.
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Marker
Backwards Compatibility
In ESA the display line does not have to be on for a peak to be qualified “above
display line” or “below display line.” In X-Series the display line has to be on to be
used to exclude peaks.
More Information
If the Display Line (see the Section “View/Display”) is turned on, the Peak Table can
be selected to include all peaks, only those above the Display Line, or only those
below the Display Line. See Figures 1–2 and 1–3 to understand what happens if
both Display Line and Pk Threshold are turned on.
Above Display Line Peak Identification
Below Display Line Peak Identification
Δ to Limit
Selects the Limit to be used for the Δ to Limit column in the Peak Table and turns the
Δ to Limit column on and off.
When on, this column shows the difference between each peak and the specified
Limit.
Command
:CALCulate:MARKer:PEAK:TABLe:DTLimit
LLINE1|LLINE2|LLINE3|LLINE4|LLINE5|LLINE6
:CALCulate:MARKer:PEAK:TABLe:DTLimit?
Remote Language Compatibility Measurement Application Reference
216
3 RLC Mode & Swept SA Measurement
Marker
:CALCulate:MARKer:PEAK:TABLe:DTLimit:STATe ON|OFF
:CALCulate:MARKer:PEAK:TABLe:DTLimit:STATe?
Example
CALC:MARK:PEAK:TABL:DTL:STAT ON
CALC:MARK:PEAK:TABL:DTL LLINE1
Preset
LLINE1
OFF
Marker Properties Tab
Marker Frequency|Time
The Marker Frequency control is the fundamental control that you use to move a
marker around on the trace. Because it is the default active function in the Marker
menu, all you need to do is press Marker and turn the knob to move the marker left
and right on the display. This is always the first control on any Marker menu page
which follows the Selected Marker.
When in Zero Span (for measurements that support Zero Span), the label on this
control changes to “Marker Time”. When the Marker Mode is Delta, the label
changes to “Marker D Frequency” or Marker D Time”
The SCPI command sets the marker X Axis value in the current marker X Axis Scale
unit. The marker that is addressed becomes the selected marker. It has no effect
(other than to cause the marker to become selected) if the control mode is Off, but it
is the SCPI equivalent of entering an X value if the control mode is Normal, Delta, or
Fixed.
Command
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:X <freq|time>
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:X?
Preset
After a preset, if X is queried with no value sent first, the center of screen value will be
returned. This will depend on the frequency range of the instrument. 13.255 GHz is
correct for the 26 GHz instruments only (Option 526).
Min/Max
Min:
–∞ (minus infinity)
Max:
+∞ (plus infinity)
Notes
If no suffix is sent it will use the fundamental units for the current marker X Axis
Scale. If a suffix is sent that does not match the current marker X Axis Scale unit, an
invalid suffix message will be generated.
If the specified marker is Fixed and a Marker Function is on, a message is
generated. If the key is pressed, an advisory message is generated. If the
equivalent SCPI command is sent, this same message is generated as part of a “–
221, Settings conflict” warning.
217
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Marker
The query returns the marker’s absolute X Axis value if the control mode is Normal
or Fixed. It returns the offset from the marker’s reference marker if the control mode
is Delta. The query is returned in the fundamental units for the current marker X
Axis scale: Hz for Frequency and Inverse Time, seconds for Period and Time. If the
marker is Off the response is not a number.
Dependencies
Grayed out and displays three dashes for the value when the selected Marker is
Off.
You cannot directly set the X value of a Fixed marker which has a marker function
turned on.. If an attempt is made to actually adjust it while a Marker Function is on,
a warning message is generated.
Marker Backwards Compatibility
In earlier HP/Agilent/Keysight analyzers, markers were position markers, which
means that Normal and Delta markers stayed at the same screen position when X
Axis parameters were changed. So a marker at center screen stayed at center
screen even if Center Frequency was changed (which means that the marker’s
frequency changed). In the X-Series, markers are value markers, which means that
when the analyzer’s X Axis settings are changed, the marker’s X Axis value in
fundamental X Axis units remains unchanged. For example, if you put a marker at a
particular frequency, it will stay at that frequency regardless of whether or not you
change the Center Frequency of the analyzer, even if that means that the marker
ends up offscreen.
While this change resulted in an overall higher level of usability of the marker
system, there are some use cases where the user depends on the marker staying
at the center of the screen. The most common one is where the user turns on a
marker at center screen and uses it to measure the trace amplitude at the center
frequency or at a series of center frequencies, without the need to ever move the
marker. In the X-Series, to mimic the legacy behavior for this use case, the user
must turn the marker off and then back on after changing the center frequency of
the analyzer. This causes the marker to reappear in the center of the screen.
Also as a result of the change from position markers to value markers, markers can
be at a frequency which is offscreen, whereas in the past, they were clipped to the
screen edges and hence were never offscreen. Users who depended on this
clipping behavior to force markers to the edges of the screen will have to rewrite
their code. Furthermore, since markers could never be offscreen they always
returned a valid result. In the X-Series, markers which are offscreen return not a
number as a result; hence the potential now exists for not a number to be returned
for a marker query.
Setting the Marker X Position in Trace Points
The command below sets the marker X position in trace points. It has no effect if
the marker control mode is Off. But it is the SCPI equivalent of entering a value if
the control mode is Normal or Delta or Fixed – except the setting is in trace points
rather than X Axis Scale units.
Remote Language Compatibility Measurement Application Reference
218
3 RLC Mode & Swept SA Measurement
Marker
The entered value in Trace Points is immediately translated into the current X Axis
Scale units for setting the value of the marker. The marker’s value in X Axis Scale
Units, NOT trace points, will be preserved if a change is made to the X Axis scale
settings. Thus, if you use this command to place a marker on bucket 500, which
happens at that time to correspond to 13 GHz, and then you change the Start
Frequency so that bucket 500 is no longer 13 GHz, the marker will stay at 13 GHz,
NOT at bucket 500! This is important to realize as it differs from the behavior of past
HP/Agilent/Keysight analyzers.
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:X:POSition <real> :CALCulate:MARKer
[1]|2|3|4|5|6|7|8|9|10|11|12:X:POSition?
Command
:CALCulate:MARKer[1]|2|3|4:X:POSition:CENTer
This alias is provided for compatibility with the Band Power function in PSA and ESA.
Preset
After a preset, if X is queried with no value sent first, the center of screen value will be
returned. So if per default, the number of Trace points is 1001, the center value will be
500.
Min/Max
0/Number of trace points – 1
Relative To
Selects the marker to which the selected marker is relative (its reference marker).
Every marker has another marker to which it is relative. This marker is referred to as
the “reference marker” for that marker. This attribute is set by the Marker,
Properties, Relative To key. The marker must be a Delta marker to make this
attribute relevant. If it is a Delta marker, the reference marker determines how the
marker is controlled and how its value is displayed. A marker cannot be relative to
itself.
Command
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:REFerence
<integer>
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:REFerence?
Example
CALC:MARK1:REF 2 sets the marker 1 reference marker to 2 and turns marker 1 on as a
delta marker.
Preset
The preset default “Relative To” marker (reference marker) is the next higher numbered
marker (current marker +1). For example, if marker 2 is selected, then it’s default
reference marker is marker 3. The exception is marker 12, which has a default reference
of marker 1.
Set to the defaults by using Restore Mode Defaults. This is not reset by Marker Off, All
Markers Off, or Preset.
Min/Max
1/12
State
Saved
Saved in instrument state. Not affected by Marker Off and hence not affected by Preset
or power cycle.
Notes
A marker cannot be relative to itself so that choice is grayed out. If the grayed out
key is pressed, an advisory message is generated.
219
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Marker
This command causes the marker specified with the subopcode to become
selected.
Range (for SCPI command): 1 to 12. If the range is exceeded the value is clipped.
A marker cannot be relative to itself so that choice is not available, and if sent from
SCPI generates error -221: “Settings conflict; marker cannot be relative to itself.”
When queried a single value is returned (the specified marker numbers relative
marker).
Couplings
The act of specifying the selected marker’s reference marker makes the selected
marker a Delta marker.
If the reference marker is off it is turned on in Fixed or Normal mode at the delta
marker location.
X Axis Scale
Accesses a menu that enables you to affect how the X Axis information for the
selected marker is displayed in the marker area (top-right of display) and the active
function area of the display, and how the marker is controlled. The available settings
for the X Axis Scale are Frequency, Period, Time, and Inverse Time.
Command
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:X:READout
FREQuency|TIME|ITIMe|PERiod
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:X:READout?
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:X:READout:AUTO
ON|OFF|1|0
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:X:READout:AUTO?
Example
CALC:MARK3:X:READ TIME sets the marker 3 X Axis Scale to Time.
Preset
AUTO
Marker Preset (selected when a marker is turned Off). In most measurements the Auto
settings results in Frequency being the preset readout.
ON
State
Saved
Saved in instrument state.
More Information
Value
Example
Notes
Frequency
:CALC:MARK2:X:READ
FREQ
Displays the absolute frequency of a normal marker or the
frequency of the delta marker relative to the reference
marker.
Period
:CALC:MARK2:X:READ
PER
Displays the reciprocal of the frequency of the marker, or
the reciprocal of the frequency separation of the two
Remote Language Compatibility Measurement Application Reference
220
3 RLC Mode & Swept SA Measurement
Marker
Value
Example
Notes
markers in a delta-marker mode. The units are those of time
(sec, msec, etc.). If the markers are at the same frequency in
a delta marker mode, the result will be the reciprocal of 0,
which is infinitely large. The display will show “---” and a
SCPI query will return infinity.
Time
:CALC:MARK2:X:READ
TIME
Displays the time interval between a normal marker and the
start of a sweep or the time of the delta marker relative to
the reference marker. Time is the auto setting for time
domain traces. In a delta-marker mode it is the (sweep) time
interval between the two markers.
Inverse
Time
:CALC:MARK2:X:READ
ITIM
Displays the reciprocal time. It is useful in a delta mode to
show the reciprocal of (sweep) time between two markers.
This function is only meaningful when on a time domain
trace and in the Delta control mode. If the markers are at
the same X Axis value, the time between them is 0, so the
reciprocal of sweep time is infinitely large. The display will
show “---” and a SCPI query will return infinity.
The X Axis Scale of a marker is the scale of its X Axis value. This affects the units
displayed in the Marker Result block and used to specify the marker’s X Axis
location. The X Axis Scale is specified using the Marker, Properties, X Axis Scale
key.
All markers in swept spans have both a time and frequency value. Which of these is
used for the result display, and for positioning the marker, depends on the X Axis
Scale setting. The X Axis Scale setting can be Frequency or Time, as well as the
reciprocal of either (Period or Inverse Time). There is also an Auto setting - when in
Auto, a marker’s X Axis Scale changes whenever the domain of the trace, upon
which it set, changes. All choices for X Axis Scale are allowed. Note that this
behavior differs from the behavior in previous instruments: previously the
instrument remembered a different X Axis Scale (formerly called Readout) for each
domain, and the choices of X Axis Scale were restricted. These restrictions were
based on the current domain of the instrument.
When in Auto, the X-Axis Scale is Frequency if the Marker Trace is a frequency
domain trace, Time if the Marker Trace is a time domain trace. When in Auto, if the
marker changes traces, or the domain of the trace the marker is on changes, the
auto result is re-evaluated. If the X Axis Scale is chosen manually, that Scale is
used regardless of the domain of the trace.
If Frequency or Period is selected for a time domain trace, all of the points in the
trace will show the same value. Attempting to use the knob or step keys to adjust
the X Axis value of the marker or entering an X Axis value from the numeric keypad
or remotely will have no effect but will generate no error.
Frequency domain traces taken in FFT mode have no valid time data. Therefore
when Time or Inverse Time is selected for markers on such traces, the X Axis value
221
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Marker
is taken as the appropriate percentage of the displayed sweep time, which is a
calculated estimate.
Lines
When on, displays a vertical line of graticule height and a horizontal line of graticule
width, intersecting at the indicator point of the marker (that is, the center of the X or
the bottom tip of the diamond. The lines are blue in color.
If the marker is off screen the lines should be extended from the marker so that they
go thru the screen area if possible. This is really useful for off screen Fixed markers
as it lets you see their amplitude even though they are off the X Axis.
Command
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:LINes[:STATe]
OFF|ON|0|1
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:LINes[:STATe]?
Example
:CALC:MARK2:LIN:ON turns Lines on for marker 2.
Preset
OFF
State
Saved
Saved in instrument state.
Couplings
Sending the remote command causes the addressed marker to become selected.
Marker Trace
Selects the trace on which you want your marker placed. A marker is associated with
one and only one trace. This trace is used to determine the placement, result, and X
Axis Scale of the marker. All markers have an associated trace, even Fixed markers;
it is from that trace that they determine their attributes and behaviors, and it is to
that trace that they go when they become Normal or Delta markers.
In measurements that support Auto Initialize, if Auto Initialize is on (the default state)
the trace is automatically chosen when the Marker is turned on.
Specifying a Marker Trace manually or with this command associates the marker
with the specified trace and turns Auto Initialize OFF for that marker. If the marker is
not Off it moves the marker from the trace it was on to the new trace. If the marker is
Off it stays off but is now associated with the specified trace.
The query returns the number of the trace on which the marker is currently placed,
even if that marker is in Auto mode.
For RTSA More Information
Remote Language Compatibility Measurement Application Reference
222
3 RLC Mode & Swept SA Measurement
Marker
Traces 1-6 are Spectrum traces and Traces 7-12 are PvT traces. Thus, selecting
Marker Trace 7 is equivalent to selecting Trace 1 of the PvT trace.
SCPI Command not available in N9061C
Preset
1
Swept SA and RTSA presets on Meas Preset or All Markers Off.
Min/Max
Min: 1
Max:
Swept SA - 6
RTSA- 12
ACP- 3
State Saved
The Marker Trace and state of Auto Init for each marker is saved in instrument state.
Notes
A marker may be placed on a blanked and/or inactive trace, even though the trace
is not visible and/or updating.
An application may register a trace name to be displayed on the key instead of a
trace number.
Couplings
The state of Marker Trace is not affected by the Auto Couple key.
If a Marker Trace is chosen manually, Auto Initialize goes to Off for that marker.
Sending the remote command causes the addressed marker to become selected.
For RTSA mode and measurement:
Traces 1-6 are Spectrum traces and Traces 7-12 are PvT traces. Thus, selecting
Marker Trace 7 is equivalent to selecting Trace 1 of the PvT trace.
Auto Initialize
When Auto Initialize is true for a given marker, the marker’s trace is re-determined
automatically by the analyzer whenever the marker turns on (Normal, Delta or Fixed)
from an Off state. This is the default state of Markers. (The trace attribute is also
determined for all markers that are on, whenever Auto Init is turned on).
When Auto Initialize is turned off for a given marker, the Marker remains associated
with the trace it is currently on regardless of whether the marker and/or the marker’s
trace is subsequently turned on or back off. If the marker is Off it stays off but is now
associated with the specified trace.
Auto Initialize is turned off automatically whenever Marker Trace is used to directly
specify a marker’s trace.
See "Marker Trace" on page 222 for more information.
See "More Information" on page 224
Command
223
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:TRACe:AUTO
OFF|ON|0|1
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Marker
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:TRACe:AUTO?
Preset
ON
Notes
Turning Marker Trace Auto Init off has no effect on the trace on which the marker is
currently placed.
The response to the query will be 0 if OFF, 1 if ON.
Couplings
The state of Auto Init is not affected by the Auto Couple key.
Auto Init is set to True on a Preset or All Markers Off.
Backwards Compatibility
The Marker Trace Auto function in legacy analyzers has been replaced by Marker
Trace Auto Init, but the same SCPI command is used for the new function. This
should work fine for most legacy users.
More Information
When the marker moves between traces the marker’s X position in trace points is
retained as it moves. For moving between active traces this generally means the xaxis value of the marker will not change. But for moving to or from an inactive trace,
the x-axis value will take on that of the new trace at the bucket the marker was on
the old trace (and is still on, on the new trace, since the bucket doesn’t change).
Note this is true even if the marker is off screen. Thus, a marker that is at the center
of the screen on the old trace stays at the center of the screen on the new trace. A
marker that is off screen one whole screen to the left on the old trace remains off
screen one whole screen to the left on the new trace – even if this means it will be
at negative time!
Auto Init Rules Flowchart
The following flowchart depicts the Auto Init rules:
Remote Language Compatibility Measurement Application Reference
224
3 RLC Mode & Swept SA Measurement
Marker
This flowchart makes it clear that putting all lower-numbered traces in View is the
simplest way to specify which trace you want the markers to go to when they turn
on. For example, if you want all Markers to go to trace 2 when they turn on, put
trace 1 in View.
Marker Settings Diagram
The Marker Settings Diagram lets you configure the Marker system using a visual
utility.
225
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Marker
Marker Function Tab
Marker Frequency|Time
The Marker Frequency control is the fundamental control that you use to move a
marker around on the trace. Because it is the default active function in the Marker
menu, all you need to do is press Marker and turn the knob to move the marker left
and right on the display. This is always the first control on any Marker menu page
which follows the Selected Marker.
When in Zero Span (for measurements that support Zero Span), the label on this
control changes to “Marker Time”. When the Marker Mode is Delta, the label
changes to “Marker D Frequency” or Marker D Time”
The SCPI command sets the marker X Axis value in the current marker X Axis Scale
unit. The marker that is addressed becomes the selected marker. It has no effect
(other than to cause the marker to become selected) if the control mode is Off, but it
is the SCPI equivalent of entering an X value if the control mode is Normal, Delta, or
Fixed.
Command
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:X <freq|time>
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:X?
Preset
After a preset, if X is queried with no value sent first, the center of screen value will be
returned. This will depend on the frequency range of the instrument. 13.255 GHz is
correct for the 26 GHz instruments only (Option 526).
Min/Max
Min:
–∞ (minus infinity)
Remote Language Compatibility Measurement Application Reference
226
3 RLC Mode & Swept SA Measurement
Marker
Max:
+∞ (plus infinity)
Notes
If no suffix is sent it will use the fundamental units for the current marker X Axis
Scale. If a suffix is sent that does not match the current marker X Axis Scale unit, an
invalid suffix message will be generated.
If the specified marker is Fixed and a Marker Function is on, a message is
generated. If the key is pressed, an advisory message is generated. If the
equivalent SCPI command is sent, this same message is generated as part of a “–
221, Settings conflict” warning.
The query returns the marker’s absolute X Axis value if the control mode is Normal
or Fixed. It returns the offset from the marker’s reference marker if the control mode
is Delta. The query is returned in the fundamental units for the current marker X
Axis scale: Hz for Frequency and Inverse Time, seconds for Period and Time. If the
marker is Off the response is not a number.
Dependencies
Grayed out and displays three dashes for the value when the selected Marker is
Off.
You cannot directly set the X value of a Fixed marker which has a marker function
turned on.. If an attempt is made to actually adjust it while a Marker Function is on,
a warning message is generated.
Marker Backwards Compatibility
In earlier HP/Agilent/Keysight analyzers, markers were position markers, which
means that Normal and Delta markers stayed at the same screen position when X
Axis parameters were changed. So a marker at center screen stayed at center
screen even if Center Frequency was changed (which means that the marker’s
frequency changed). In the X-Series, markers are value markers, which means that
when the analyzer’s X Axis settings are changed, the marker’s X Axis value in
fundamental X Axis units remains unchanged. For example, if you put a marker at a
particular frequency, it will stay at that frequency regardless of whether or not you
change the Center Frequency of the analyzer, even if that means that the marker
ends up offscreen.
While this change resulted in an overall higher level of usability of the marker
system, there are some use cases where the user depends on the marker staying
at the center of the screen. The most common one is where the user turns on a
marker at center screen and uses it to measure the trace amplitude at the center
frequency or at a series of center frequencies, without the need to ever move the
marker. In the X-Series, to mimic the legacy behavior for this use case, the user
must turn the marker off and then back on after changing the center frequency of
the analyzer. This causes the marker to reappear in the center of the screen.
Also as a result of the change from position markers to value markers, markers can
be at a frequency which is offscreen, whereas in the past, they were clipped to the
screen edges and hence were never offscreen. Users who depended on this
clipping behavior to force markers to the edges of the screen will have to rewrite
227
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Marker
their code. Furthermore, since markers could never be offscreen they always
returned a valid result. In the X-Series, markers which are offscreen return not a
number as a result; hence the potential now exists for not a number to be returned
for a marker query.
Setting the Marker X Position in Trace Points
The command below sets the marker X position in trace points. It has no effect if
the marker control mode is Off. But it is the SCPI equivalent of entering a value if
the control mode is Normal or Delta or Fixed – except the setting is in trace points
rather than X Axis Scale units.
The entered value in Trace Points is immediately translated into the current X Axis
Scale units for setting the value of the marker. The marker’s value in X Axis Scale
Units, NOT trace points, will be preserved if a change is made to the X Axis scale
settings. Thus, if you use this command to place a marker on bucket 500, which
happens at that time to correspond to 13 GHz, and then you change the Start
Frequency so that bucket 500 is no longer 13 GHz, the marker will stay at 13 GHz,
NOT at bucket 500! This is important to realize as it differs from the behavior of past
HP/Agilent/Keysight analyzers.
Command
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:X:POSition <real> :CALCulate:MARKer
[1]|2|3|4|5|6|7|8|9|10|11|12:X:POSition?
:CALCulate:MARKer[1]|2|3|4:X:POSition:CENTer
This alias is provided for compatibility with the Band Power function in PSA and ESA.
Preset
After a preset, if X is queried with no value sent first, the center of screen value will be
returned. So if per default, the number of Trace points is 1001, the center value will be
500.
Min/Max
0/Number of trace points – 1
Band Function
Band Functions are Marker Functions that allow you to define a band of frequencies
around the marker. The band defines the region of data used for the numerical
calculations. These marker functions also allow you to perform mathematical
calculations on trace and marker data and report the results of these calculations in
place of the normal marker result.
Unlike regular markers, Band Function markers are not placed directly on the trace.
They are placed at a location which is relative to the result of the function calculation.
:CALC:MARK:FUNC BDEN turns on marker 1 as a band density marker.
:CALC:MARK:FUNC OFF turns off marker functions for marker 1
Command
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:FUNCtion
NOISe|BPOWer|BDENsity|OFF
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:FUNCtion?
Example
CALC:MARK:FUNC NOIS CALC:MARK:FUNC? returns the current band function for
Remote Language Compatibility Measurement Application Reference
228
3 RLC Mode & Swept SA Measurement
Marker
marker 1. For Marker Noise it returns NOIS, for Band Power it returns BPOW, and for
Band Density it returns BDEN. CALC:MARK:Y? ! returns the y-axis value of marker 1,
which means it returns the Band Function value if a Band Function is on for Marker 1.
Note that the delta value when the Y axis unit is Watt is the square of the delta value
when the Y axis unit is Volt. For example, when the percent ratio with Y axis unit in Volt is
0.2, the percent ratio with Y axis unit in Watt will be 0.22 = 0.04. When you read the
value out remotely you have to know whether your Y Axis Unit is log (dB), linear (V or A),
or power (W).
Preset
OFF
State
Saved
The band function for each marker is saved in instrument state.
Notes
The zero-width case and the case of a width less than .499 buckets is treated as one
bucket wide although it shows a width of 0.
When the trace the marker is on crosses domains, the width crosses domains as
well, to remain the same percentage of the trace.
Sending this command selects the specifies marker
Dependencies
Fixed markers: It is not possible to change the Band Function for a Fixed marker; so
the Band Function selections are grayed out for a Fixed marker.
If a marker function was already on when the marker became Fixed, then the
selected Band Function is shown but cannot be changed. Therefore, you cannot
directly set the X or Y value of a Fixed marker that has a marker function turned on.
To turn off the function, turn off the marker.
Average detector and Power Averaging are auto selected when Marker Noise on
If the selected (specified) marker is off, selecting Marker Noise via front panel or SCPI
will turn the marker on.
Couplings
When you choose any Band Function and Band Span Auto/Man is in the Auto state,
the Band Span is set to 5% of the screen width.
Adjusting the Band Span sets Band Span Auto/Man to Man.
While in Marker Noise and with Band Span Auto/Man in the Auto state, if the
analyzer Span is changed Band Span will stay at 5% of the new span.
If the selected (specified) marker is off, selecting a Band Function via front panel or
SCPI will turn the marker on.
If the detector mode for the detector on the marker’s trace is set to Auto, the
average detector is selected. If the Average type is set to Auto, Power Averaging is
229
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Marker
selected. Other choices for the detector or Average type will usually cause
measurement inaccuracy.
Backwards Compatibility
The introduction of adjustable-width Band Functions in the X-Series fundamentally
changes the way Band Power markers are controlled. See the section entitled Band
Function Backwards Compatibility below for a complete discussion of programming
Band Functions in a backwards compatible fashion.
More Information
The Band Functions are Marker Noise, Band Power, and Band Density, only one of
which can be on for a given marker.
Value
Example
Notes
Marker
Noise
CALC:MARK:FUNC
NOIS !turns on
marker 1 as a noise
marker.
When Marker Noise is on, the marker’s Y Axis Result is the average
noise level, normalized to a 1 Hz noise power bandwidth, in the
band specified under the Band Adjust key. To guarantee accurate
data for noise-like signals, a correction for equivalent noise
bandwidth is made by the analyzer. The Marker Noise function
accuracy is best when the detector is set to Average or Sample,
because neither of these detectors will peak-bias the noise. The
tradeoff between sweep time and variance of the result is best
when Average Type is set to Power Averaging. Therefore, Auto
coupling chooses the Average detector and Power Averaging when
Marker Noise is on. Though the Marker Noise function works with
all settings of detector and Average Type, using the positive or
negative peak detector gives less accurate measurement results.
Noise Markers assume that the signal to be measured is noiselike. Based on this assumption, we can actually make reasonable
measurements under very non-ideal conditions: any detector may
be used, any averaging type, any VBW. In contrast, the Band Power
and Band Density markers make no assumption about the
statistics of the signal.
Band
Power
CALC:MARK:FUNC
BPOW !turns on
marker 1 as a band
power marker.
The band power marker computes the total power within a span in
a nonzero span. The results computation must include the RBW. In
zero span the band power marker measures the average power
across a time interval. This is sometimes referred to as the interval
power.
Band
Density
CALC:MARK3:FUNC
BDEN !turns on
marker 3 as a band
density marker.
On frequency domain traces, the band density across a band is the
total band power divided by the bandwidth over which it is
measured. In zero span the band density marker measures the
average power across a time interval, divided by Bn. Bn is the noise
bandwidth of the RBW filter, as noted and used within the Band
Power computation. This is sometimes referred to as the interval
density. It may seem like the band density marker function is
Remote Language Compatibility Measurement Application Reference
230
3 RLC Mode & Swept SA Measurement
Marker
Value
Example
Notes
exactly like a function of a noise marker with variable width. But
they are somewhat different. The Noise marker assumes that the
signal to be measured is noise-like and applies a correction based
on that assumption. The Band Density markers make no
assumption about the statistics of the signal
Off
:CALC:MARK:FUNC
OFF turns off band
functions for marker
1
Off turns off all Band Functions. Turning off the marker function has
no effect on the band span nor does it turn the marker off.
Band Left
Sets the left edge frequency or time for the band of the selected marker. The right
edge is unaffected.
Command
:CALCulate:MARKer
[1]|2|3|4|5|6|7|8|9|10|11|12:FUNCtion:BAND:LEFT <freq>
:CALCulate:MARKer
[1]|2|3|4|5|6|7|8|9|10|11|12:FUNCtion:BAND:LEFT?
Example
:CALC:MARK12:FUNC:BAND:LEFT 20 GHz sets the left edge of the band span of marker
12 to 20 GHz :CALC:MARK:FUNC:BAND:LEFT? queries the band span of Marker 1
Preset
If 0, Band Span is set to 5% of span, when a marker function is turned on, which affects
Band Left.
Min/Max
Min:0 Hz
Max:Infinity. Unlike legacy analyzers, where the markers were forced to be on screen, XSeries marker values are not limited and do not clip.
State
Saved
Saved in instrument state.
Notes
Units are those of the trace’s domain, Hz for frequency domain, s for time domain.
When the left edge is moved, the right edge stays anchored; thus, the marker’s
frequency will change.
Sending this command selects the subopcoded marker
The unit of the parameter must match the current domain of the trace the selected
marker is on, or an invalid suffix error will be generated. If no unit is sent the
fundamental unit for the trace domain will be used (Hz for freq domain traces, s for
time domain traces).
Note that all the values provided in this table are only valid for frequency domain
traces. If the current domain of the trace is time domain, values and unit will be
different. In frequency domain, the Preset value is dependent on the frequency range
of the instrument. The default value 1.3245 GHz is appropriate only if the instrument
231
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Marker
is a 26.5 GHz instrument (Option 526). In a 26.5 GHz Instrument, the default span is
26.49 GHz, so 5% of the span corresponds to 1.3245 GHz.
Couplings
Changing the Band Left necessarily changes the Band Span and Band Center
values.
Band Span is set to 0 when the marker is turned off so that means Band Left is set to
the center value at this time.
Band Span is set to 5% of span when any marker function is turned on if and only if it
is zero at that time.
Backwards Compatibility
:CALCulate:MARKer[1]|2|3|4:X:STARt
Band Right
Sets the right edge frequency or time for the band of the selected marker. The left
edge is unaffected.
Command
:CALCulate:MARKer
[1]|2|3|4|5|6|7|8|9|10|11|12:FUNCtion:BAND:RIGHt <freq>
:CALCulate:MARKer
[1]|2|3|4|5|6|7|8|9|10|11|12:FUNCtion:BAND:RIGHt?
Example
:CALC:MARK12:FUNC:BAND:RIGHt 20 GHz sets the right edge of the band span of
marker 12 to 20 GHz :CALC:MARK:FUNC:BAND:RIGHt? queries the band span of Marker
1
Preset
If 0, Band Span is set to 5% of span, when a marker function is turned on, which affects
Band Right.
Min/Max
Min:0 Hz
Max:Infinity. Unlike legacy analyzers, where the markers were forced to be on screen, XSeries marker values are not limited and do not clip.
State
Saved
Saved in instrument state.
Notes
Units are those of the trace’s domain, Hz for frequency domain, s for time domain.
When the right edge is moved, the left edge stays anchored; thus, the marker’s
frequency will change.
Sending this command selects the subopcoded marker
The unit of the parameter must match the current domain of the trace the selected
marker is on, or an invalid suffix error will be generated. If no unit is sent the
fundamental unit for the trace domain will be used (Hz for freq domain traces, s for
time domain traces).
Remote Language Compatibility Measurement Application Reference
232
3 RLC Mode & Swept SA Measurement
Marker
Note that all the values provided in this table are only valid for frequency domain
traces. If the current domain of the trace is time domain, values and unit will be
different. In frequency domain, the Preset value is dependent on the frequency range
of the instrument. The default value 1.3245 GHz is appropriate only if the instrument
is a 26.5 GHz instrument (Option 526). In a 26.5 GHz Instrument, the default span is
26.49 GHz, so 5% of the span corresponds to 1.3245 GHz.
Couplings
Changing the Band Right necessarily changes the Band Span and Band Center
values
Band Span is set to 0 when the marker is turned off so that means Band Right is set
to the center value at this time
Backwards Compatibility
:CALCulate:MARKer[1]|2|3|4:X:STOP
:CALCulate:MARKer[1]|2|3|4:X:POSition:STOP <integer>
:CALCulate:MARKer[1]|2|3|4:X:POSition:STOP?
:CALCulate:MARKer[n]:X:POSition:STOP <param>
! was used to control the Delta marker in trace points (buckets) in Band Pair/Delta
Pair mode. There is no new command for setting the stop of a Band Function in trace
points. So, when this command is received, the analyzer first converts the specified
span in trace points to the current X Axis Scale Units (e.g., frequency or time) of the
trace upon which the marker resides. Then, that value is sent to the
:CALC:MARKer[n]:FUNCtion:BAND:RIGHt <param>
! command to set the stop of the marker’s Band Function.
! The query form of the command will return the marker function RIGHt value in trace
points (buckets) by translating back based on the current X Axis Scale settings at the
time the query is sent.
See "Band Function" on page 228, Band Functions Backwards Compatibility for more
information.
Band Span
Determines whether the Band Span for Marker Noise will track the analyzer’s Span.
When you choose any Band Function and Band Span Auto/Man is in the Auto state,
the Band Span is set to 5% of the screen width.
Adjusting the Band Span sets Band Span Auto/Man to Man.
This function only affects Marker Noise. While in Marker Noise and with Band Span
Auto/Man in the Auto state, if the analyzer Span is changed Band Span will stay at
5% of the new span.
233
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Marker
If Band Span Auto/Man is in the Man state, the Band Span does not change when
the Span is changed. Also, if any Band Function but Marker Noise is in effect, the
Band Span does not change when the Span is changed.
The Band Span is set to 5% regardless of whether or not this would place part of the
Band offscreen. The Marker Noise function is well able to function with part of the
band offscreen.
Note that, if in Zero Span, “Span” should be replaced by “Sweep Time” in the
discussion above.
Command
:CALCulate:MARKe
[1|2|3|4|5|6|7|8|9|10|11|12:FUNCtion:BAND:SPAN:AUTO ON|OFF
:CALCulate:MARKer
[1]|2|3|4|5|6|7|8|9|10|11|12:FUNCtion:BAND:SPA
Example
:CALC:MARK12:FUNC:BAND:SPAN:AUTO ON sets the band span of marker 12 to Auto
:CALC:MARK:FUNC:BAND:SPAN:AUTO? queries the auto band span state of Marker 1
Preset
Auto
State
Saved
Saved in instrument state.
Dependencies
This only appears when the Marker Function for the selected marker is Marker
Noise. If the SCPI command is sent to a marker that does not have Marker Noise
selected, it is honored but of course, the user will not see any indication of this.
Couplings
When Auto Band Span is turned on, it immediately adjusts the band span to 5% of
the Span. If you select Marker Noise, and Auto Band Span is on, the Band Span will
immediately change to 5% of Span.
If the Band Span is changed, either by the Band Span key, the Band Left key, or the
Band Right key, or the equivalent SCPI commands, this function is set to Man.
Backwards Compatibility
In legacy analyzers, the Noise Marker had a width that was always equal to 5% of
the span. But in the X-Series it is possible for the user to change the span of the
Marker Noise band using the Band Adjust function. To preserve the legacy behavior,
the Band Span Auto/Man function is provided. When it is in Auto, which it is by
default, the Maker Noise band is always held at 5% of Span, even if the Span
changes. When the user adjusts the Marker Noise Band Span, Band Span Auto/Man
is set to Manual. So the legacy behavior is preserved, but now the user can set the
Marker Noise Span as well and that setting will be preserved when Span is changed.
N dB Points
Turns N dB points on and off and allows you to set the N dB value. N dB uses the
selected marker. If the selected marker is not on when N dB is turned on, the
selected marker turns on, as a Normal marker, at center screen, and is used by N dB.
Remote Language Compatibility Measurement Application Reference
234
3 RLC Mode & Swept SA Measurement
Marker
If the selected marker is turned Off it turns off N dB Points.
N dB Points is unaffected by Auto Couple.
SCPI Commands not available in N9061C
Preset
–3.01dB
Min/Max
–140 dB/–0.01 dB
State Saved
The on/off status and the offset value are both saved in instrument state.
Backwards Compatibility
In ESA, N dB points paid attention to the peak excursion and peak threshold set in
the Search Criteria menu under Peak Search. This is not the case in the X-Series.
In ESA, an invalid N dB reading was indicated, both onscreen and remotely, with a
value of –100. In the X-Series it is indicated on screen by --- but remotely still by –
100 Hz
More Information
A marker should be placed on the peak of interest before turning on N dB
points. The N dB points function looks for the two points on the marker’s trace
closest to the marker’s X Axis value that are N dB below the marker’s amplitude,
one above and the other below the marker’s X Axis value. (That is, one point is to
the right and one is to the left of the selected marker.) The selected N dB value is
called the offset. The function reports the frequency difference (for frequency
domain traces) or time difference (for time domain traces) between those two
points.
Each point is identified by a horizontal arrow pointing towards the marker, next to
the trace. The arrows used by the N dB Points function will be as shown in the figure
below (where each square represents one pixel). They point in, horizontally, at the
trace below a peak, on either side of its skirts. There is one pixel between the arrow
and the trace, as shown below:
235
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Marker
N dB Points can be used to measure the bandwidth of a signal; it is commonly used
in conjunction with a tracking generator to measure filter bandwidths.
In one of the common use cases, the marker is placed on a peak, and the arrows
are displayed N dB down the skirt from the marker on either side of the peak. The N
dB value and the frequency difference between the two arrows is displayed around
the arrow as shown in the figure above. Normally this displays on the right hand
arrow, but if this would place any part of the text offscreen to the right then it
displays on the left arrow.
If the analyzer is unable to find data that is N dB below the marker on either side of
the marker, the arrows are displayed at the indicator point of the marker, no value
(---) will be displayed as the result and –100 Hz returned remotely (see figure
below):
Some sample N dB scenarios are shown below to illustrate how the function works
in various cases. In each case, the two-headed blue arrow represents N dB of
amplitude.
Remote Language Compatibility Measurement Application Reference
236
3 RLC Mode & Swept SA Measurement
Marker
237
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Marker
Measure at Marker
When this key is pressed, the analyzer executes one Measure at Marker function
and then returns. Measure at Marker goes to the frequency of the selected marker
and takes a reading with each of the three detectors selected in the Detectors
menu, using the dwell times specified there, then displays the readings in a window
on the display, using the current Y-Axis Unit.
When the Measure at Marker is complete, the analyzer restores all settings to their
pre-Measure-at-Marker values and normal sweeps resume.
Command
:CALCulate:MARKer
[1]|2|3|4|5|6|7|8|9|10|11|12:FUNCtion:MAMarker?
Example
:CALC:MARK2:FUNC:MAM? performs a Measure at Marker function at Marker 2’s
current frequency and, when completed, returns the results of the measure at marker
window in a query
Notes
This query command returns comma separated values for the 3 specified detectors
and the frequency value of the marker. If a Detector is off or if no measurement has
yet completed, –999.0 will be returned. This can happen, for example, if you are
operating with too large a value of (span/sweep points) and the Measure at Marker
function does not execute but instead puts up the advisory message, “Span per point
too large, narrow span or increase RBW or number of points” (see below).
The size of the return data array is fixed at 4. The elements are:
1. Detector 1 value ( if off, –999.0 for backwards compatibility)
2. Detector 2 value ( if off, –999.0 for backwards compatibility)
3. Detector 3 value ( if off, –999.0 for backwards compatibility)
4. Frequency of Marker
If a sweep is in process when this function executes it aborts, and restarts after the
function is complete.
Dependencies
This control only appears with the N6141A or W6141A application or when Option
EMC is installed and licensed.
If BW & Avg Type is in an Autocoupled state, the (up to three) measurements taken
by Measure at Marker are taken with Auto Coupled settings for the functions in the
BW menu, even if those functions are in manual.
Couplings
If the specified Marker is not on, the analyzer turns it on at the center of the screen
and does a peak search before performing the function.
Remote Language Compatibility Measurement Application Reference
238
3 RLC Mode & Swept SA Measurement
Marker
Measure at Marker Config
Measure at Marker Config opens up a dialog that allows you to configure the
Measure at Marker Function.
The two most important settings are the detectors and the dwelltime associated
with each. Any of the analyzer’s detectors (up to three) can be used as the Measure
at Marker detectors, or any of the three can be turned off. The dwell time for each
detector is also settable.
When performing a Meas at Marker, the dwell time settings that you select will
depend on the characteristics of the emission you are measuring. The default dwell
time (200 ms) should work well for typical EUT emissions, but sometimes you will
encounter emissions for which the defaults are not optimal. This is especially the
case for emissions that vary slowly over time or have a slow repetition rate. By
lengthening the dwell times you can increase the likelihood of accurately measuring
these low repetition rate signals.
When Measure at Marker is activated, the receiver makes a zero span measurement
for each of the (up to) three detectors selected, using the Dwell Time set for each
detector. If the signal's repetition period is greater than 200 ms (the default setting),
the dwell time should be increased to capture at least two and preferably more
repetitions of the signal. Additionally, if you do not need or do not wish to use a
detector to make a measurement, that specific detector may be turned off.
If the Measure at Marker window is being displayed, and one of the detectors is
changed, any value being displayed for that detector changes to “---“ until the next
successful reading from that detector.
Marker-> Tab
Marker Frequency|Time
The Marker Frequency control is the fundamental control that you use to move a
marker around on the trace. Because it is the default active function in the Marker
menu, all you need to do is press Marker and turn the knob to move the marker left
and right on the display. This is always the first control on any Marker menu page
which follows the Selected Marker.
When in Zero Span (for measurements that support Zero Span), the label on this
control changes to “Marker Time”. When the Marker Mode is Delta, the label
changes to “Marker D Frequency” or Marker D Time”
The SCPI command sets the marker X Axis value in the current marker X Axis Scale
unit. The marker that is addressed becomes the selected marker. It has no effect
(other than to cause the marker to become selected) if the control mode is Off, but it
is the SCPI equivalent of entering an X value if the control mode is Normal, Delta, or
Fixed.
239
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Marker
Command
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:X <freq|time>
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:X?
Preset
After a preset, if X is queried with no value sent first, the center of screen value will be
returned. This will depend on the frequency range of the instrument. 13.255 GHz is
correct for the 26 GHz instruments only (Option 526).
Min/Max
Min:
–∞ (minus infinity)
Max:
+∞ (plus infinity)
Notes
If no suffix is sent it will use the fundamental units for the current marker X Axis
Scale. If a suffix is sent that does not match the current marker X Axis Scale unit, an
invalid suffix message will be generated.
If the specified marker is Fixed and a Marker Function is on, a message is
generated. If the key is pressed, an advisory message is generated. If the
equivalent SCPI command is sent, this same message is generated as part of a “–
221, Settings conflict” warning.
The query returns the marker’s absolute X Axis value if the control mode is Normal
or Fixed. It returns the offset from the marker’s reference marker if the control mode
is Delta. The query is returned in the fundamental units for the current marker X
Axis scale: Hz for Frequency and Inverse Time, seconds for Period and Time. If the
marker is Off the response is not a number.
Dependencies
Grayed out and displays three dashes for the value when the selected Marker is
Off.
You cannot directly set the X value of a Fixed marker which has a marker function
turned on.. If an attempt is made to actually adjust it while a Marker Function is on,
a warning message is generated.
Marker Backwards Compatibility
In earlier HP/Agilent/Keysight analyzers, markers were position markers, which
means that Normal and Delta markers stayed at the same screen position when X
Axis parameters were changed. So a marker at center screen stayed at center
screen even if Center Frequency was changed (which means that the marker’s
frequency changed). In the X-Series, markers are value markers, which means that
when the analyzer’s X Axis settings are changed, the marker’s X Axis value in
fundamental X Axis units remains unchanged. For example, if you put a marker at a
particular frequency, it will stay at that frequency regardless of whether or not you
change the Center Frequency of the analyzer, even if that means that the marker
ends up offscreen.
While this change resulted in an overall higher level of usability of the marker
system, there are some use cases where the user depends on the marker staying
at the center of the screen. The most common one is where the user turns on a
Remote Language Compatibility Measurement Application Reference
240
3 RLC Mode & Swept SA Measurement
Marker
marker at center screen and uses it to measure the trace amplitude at the center
frequency or at a series of center frequencies, without the need to ever move the
marker. In the X-Series, to mimic the legacy behavior for this use case, the user
must turn the marker off and then back on after changing the center frequency of
the analyzer. This causes the marker to reappear in the center of the screen.
Also as a result of the change from position markers to value markers, markers can
be at a frequency which is offscreen, whereas in the past, they were clipped to the
screen edges and hence were never offscreen. Users who depended on this
clipping behavior to force markers to the edges of the screen will have to rewrite
their code. Furthermore, since markers could never be offscreen they always
returned a valid result. In the X-Series, markers which are offscreen return not a
number as a result; hence the potential now exists for not a number to be returned
for a marker query.
Setting the Marker X Position in Trace Points
The command below sets the marker X position in trace points. It has no effect if the
marker control mode is Off. But it is the SCPI equivalent of entering a value if the
control mode is Normal or Delta or Fixed – except the setting is in trace points
rather than X Axis Scale units.
The entered value in Trace Points is immediately translated into the current X Axis
Scale units for setting the value of the marker. The marker’s value in X Axis Scale
Units, NOT trace points, will be preserved if a change is made to the X Axis scale
settings. Thus, if you use this command to place a marker on bucket 500, which
happens at that time to correspond to 13 GHz, and then you change the Start
Frequency so that bucket 500 is no longer 13 GHz, the marker will stay at 13 GHz,
NOT at bucket 500! This is important to realize as it differs from the behavior of past
HP/Agilent/Keysight analyzers.
Command
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:X:POSition <real> :CALCulate:MARKer
[1]|2|3|4|5|6|7|8|9|10|11|12:X:POSition?
:CALCulate:MARKer[1]|2|3|4:X:POSition:CENTer
This alias is provided for compatibility with the Band Power function in PSA and ESA.
Preset
After a preset, if X is queried with no value sent first, the center of screen value will be
returned. So if per default, the number of Trace points is 1001, the center value will be
500.
Min/Max
0/Number of trace points – 1
Marker -> CF
Sets the center frequency of the analyzer to the frequency of the selected marker.
The marker stays at this frequency, so it moves to the center of the display. In delta
marker mode, this function sets the center frequency to the x-axis value of the delta
marker. When the frequency scale is in log mode, the center frequency is not at the
center of the display.
If the currently selected marker is not on when this key is pressed, it will be turned on
at the center of the screen as a normal type marker.
241
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Marker
Command
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12[:SET]:CENTer
Example
CALC:MARK2:CENT sets the CF of the analyzer to the value of marker 2.
Notes
Sending this command selects the subopcoded marker
If specified marker is off, this command will turn it on at the center of the screen as
a normal type marker.
Dependencies
This function is not available (key is grayed out) when x-axis is the time domain
Couplings
All the usual couplings associated with setting Center Frequency apply.
Marker -> CF Step
Sets the center frequency (CF) step size of the analyzer to the marker frequency, or
in a delta-marker mode, to the frequency difference between the delta and
reference markers.
If the currently selected marker is not on when this key is pressed, it will be turned
on at the center of the screen as a normal type marker.
Command
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12[:SET]:STEP
Example
CALC:MARK1:STEP sets the CF step to the value (or delta value) of marker 1.
Notes
Sending this command selects the subopcoded marker
If specified marker is off, this command will turn it on at the center of the screen as
a normal type marker.
Dependencies
This function is not available (key is grayed out) when x-axis is the time domain.
Couplings
All the usual couplings associated with setting CF Step apply.
Marker -> Start
Changes the start frequency to the frequency of the selected marker. The marker
stays at this frequency, so it moves to the left edge of the display. In delta marker
mode, this function sets the start frequency to the x-axis value of the delta marker.
If the currently selected marker is not on when this key is pressed, it will be turned
on at the center of the screen as a normal type marker.
Command
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12[:SET]:STARt
Example
CALC:MARK1:STAR sets the start frequency to the value (or delta value) of marker 1.
Remote Language Compatibility Measurement Application Reference
242
3 RLC Mode & Swept SA Measurement
Marker
Notes
Sending this command selects the subopcoded marker
If specified marker is off, this command will turn it on at the center of the screen as a
normal type marker.
Dependencies
This function is not available (key is grayed out) when x-axis is the time domain.
Couplings
All the usual couplings associated with setting Start Frequency apply.
Marker -> Stop
Changes the stop frequency to the frequency of the selected marker. The marker
stays at this frequency, so it moves to the right edge of the display. In delta marker
mode, this function sets the stop frequency to the x-axis value of the delta marker.
If the currently selected marker is not on when this key is pressed, it will be turned on
at the center of the screen as a normal type marker.
Command
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12[:SET]:STOP
Example
CALC:MARK3:STOP sets the stop frequency to the value (or delta value) of marker 3.
Notes
Sending this command selects the subopcoded marker
If specified marker is off, this command will turn it on at the center of the screen as a
normal type marker.
Dependencies
This function is not available (key is grayed out) when x-axis is the time domain.
Couplings
All the usual couplings associated with setting Stop Frequency apply.
Marker -> Ref Lvl
Sets the reference level to the amplitude value of the selected marker, moving the
marked point to the reference level (top line of the graticule). The marker’s mode
(Normal, Delta, Fixed) doesn’t matter in this case. For example, given a delta marker,
if the delta marker is the selected marker, its amplitude is applied to the reference
level. If the reference marker is selected, its amplitude is applied to the reference
level.
If the currently selected marker is not on when this key is pressed, it will be turned on
at the center of the screen as a normal type marker, and its amplitude applied to the
reference level.
Command
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12[:SET]:RLEVel
Example
CALC:MARK2:RLEV sets the reference level of the analyzer to the amplitude of marker 2.
Notes
243
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Marker
Sending this command selects the subopcoded marker
If specified marker is off, this command will turn it on at the center of the screen as
a normal type marker.
Couplings
All the usual couplings associated with setting Reference Level apply.
Backwards Compatibility
Mkr-> RefLvl behavior for a delta marker is slightly different from earlier models.
ESA would calculate the delta amplitude (difference between reference marker
and delta marker in dB) and assign that value to the reference level (in dBm). PSA
would just assign the delta marker’s amplitude to the reference level, ignoring the
reference marker altogether. The X-Series products allow the user to select either
the reference or the delta marker individually. It is the selected marker’s amplitude
that will be applied to the reference level.
Marker Δ -> CF
Sets the center frequency to the frequency difference between the selected marker
and its reference marker. The marker is then changed to a Normal marker and
placed at the center of span.
Command
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12
[:SET]:DELTa:CENTer
Example
CALC:MARK2:CENT sets the CF of the analyzer to the value of marker 2.
Notes
Sending this command selects the subopcoded marker.
Dependencies
This function is only available when the selected marker is a delta marker.
Otherwise the key is grayed out.
In addition, this function is not available when x-axis is the time domain.
Marker Δ -> Span
Sets the start and stop frequencies to the values of the delta markers. That is, it
moves the lower of the two marker frequencies to the start frequency and the higher
of the two marker frequencies to the stop frequency. The marker mode is unchanged
and the two markers (delta and reference) end up on opposite edges of the display.
Command
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12[:SET]:DELTa:SPAN
Example
CALC:MARK2:DELT:SPAN sets the start and stop frequencies to the values of marker 2
and its reference marker.
Notes
Sending this command selects the subopcoded marker
Remote Language Compatibility Measurement Application Reference
244
3 RLC Mode & Swept SA Measurement
Marker
Dependencies
This function is only available when the selected marker is a delta marker.
Otherwise the key is grayed out.
In addition, this function is not available when x-axis is the time domain.
Couplings
All the usual couplings associated with setting Span apply.
Backwards Compatibility
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12[:SET]:SPAN
In earlier ESA and PSA products, MkrD ->Span would adjust the span and change
the delta marker to a normal marker placing it at the center of screen. In all the XSeries products, this is no longer true. The markers will remain in delta mode and
the delta and reference marker will end up on opposite edges of the display.
Counter Tab
Marker Count
Turns the marker frequency counter on and off. The selected marker is counted, and
if the selected marker is a delta marker and its reference marker is not fixed, the
reference marker is counted as well.
See "Understanding Marker Count" on page 246:
– "Delta Marker" on page 247
– "Fixed Markers" on page 247
– "More Information on "Counter"" on page 248
See "Query Count Value" on page 246
Command
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:FCOunt[:STATe]
OFF|ON|0|1
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:FCOunt[:STATe]?
Example
CALC:MARK2:FCO ON selects marker 2, turns it on, and turns on the counter.
CALC:MARK2:FCO:X? returns the counted frequency.
Preset
OFF
State
Saved
The state of the counter (on/off) is saved in instrument state. In the case of Fixed
markers, the count stored in the marker is saved in instrument state.
Notes
Fixed markers are not counted, but a Fixed marker will have a count stored in it if it
is selected or is the reference marker for the selected marker. The count already in
the marker is stored when the marker becomes fixed and if there is none or the
marker moves (for example, Pk Search) it is counted and stored after the next
sweep.
245
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Marker
If a Fixed marker has a count stored in it, that count will be displayed when the
marker is selected, and used as the reference count when that marker is a
reference marker.
If a Fixed marker has a count stored in it, that count will be deleted if the marker X is
adjusted.
If a Fixed marker has a count stored in it, and a Search function is performed using
the Fixed marker, while the counter is on, the count stored in the marker will be
updated.
If a Fixed marker has a count stored in it, and is a reference marker, and the
reference is moved to a valid trace point by re-zeroing the delta (by pressing Delta
again or sending the DELTa SCPI command), while the counter is on, the count
stored in the marker will be updated.
This command causes the specified marker to become selected.
Dependencies
Marker Count is unavailable (grayed out and Off) if the Gate function is on
Couplings
If the selected marker is Off when the counter is turned on, the selected marker is
set to Normal and placed at center of screen on the trace determined by the
Marker Trace rules.
Backwards Compatibility
In some legacy analyzers (e.g., the 8560 series) the FreqOffset value was applied
to the Marker Count. In others (e.g., ESA and PSA) it was not. The X-Series follows
the ESA/PSA model and does not apply Freq Offset to the Marker Count.
In ESA and PSA the reference marker for Delta markers was always counted. In the
X-Series the marker is counted for Normal and Delta markers; but for the reference
marker, if it is a Fixed marker, we use the count stored in the Fixed marker. This
enhanced capability may require a change to some users’ code and/or test
procedures.
Query Count Value
Queries the frequency count. The query returns the absolute count unless the
specified marker is in Delta mode, then it returns the relative count. If the marker is
off, or the marker is on but the counter is off, the analyzer will return not a number
to a SCPI count query. A marker with no stored count, or a non-Fixed marker on a
stored trace, will also return not a number to a SCPI count query. Note this result
may simply mean that the first sweep after the counter turned on has not yet
completed.
This query does NOT cause the specified marker to become selected.
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:FCOunt:X?
Understanding Marker Count
Using the internal counter we can count the frequency of a marker, but we cannot
Remote Language Compatibility Measurement Application Reference
246
3 RLC Mode & Swept SA Measurement
Marker
count while we are actually sweeping. So, once we are done with a sweep, we
move to the selected marker frequency and count that frequency. Then, if the
marker is a Delta marker, the count is also taken for its reference marker. The count
is actually performed by moving the LO to the frequency (or frequencies in the case
of a delta marker) we wish to count. The count is executed on a marker by marker
basis and no further count is taken until after the next sweep (even if the marker
moves before another sweep has completed).
The Marker Count is taken by tuning the instrument to the frequency of the marker
and counting the IF, with the instrument not sweeping. The count is adjusted for
display by adding or subtracting it (as appropriate) from the LO frequency, so that
you see a count that represents the signal frequency. This is true even if External
Mixing is on. Since all this happens between sweeps, you never see the instrument
retuning to do the counts.
If you wish to see the entered frequency of a counted marker it will appear in the
active function area when that marker is selected (for Fixed markers, you have to
press the Marker, Fixed key to select Fixed markers and then press it a second time
to view or adjust the x or y marker values).
Counting Off-screen Markers
If the selected marker is off the X-axis the instrument can still be tuned to the
marker (unless it is outside the current range of the instrument), so the count can
still be displayed. This means you can see a count for an off-screen marker even
though there may be no valid Y-value for the marker. If the marker frequency is
outside the range of the instrument, the display will show three dashes in the count
block (---), and not a number is returned to a SCPI count query
Delta Marker
When a Delta Marker is selected while Marker Count is on:
1. If the reference marker is not a fixed marker, the display shows the difference
between the count of the selected marker and the count of the reference
marker
2. If the reference marker is a fixed marker and there is a count stored in the
marker (because Marker Count was on when the marker became a fixed
marker), the display shows the difference between the count at the marker and
the count stored in the reference marker.
Marker Count works in zero span as well as in Swept SA. The instrument tunes to
the frequency of the selected marker, which, for active zero span traces, is simply
the center frequency of the analyzer.
Fixed Markers
Fixed markers have a count stored in them that is generally kept fixed and not
updated. If a fixed marker is selected, or used as a reference, the signal at the
marker frequency is not counted; rather the stored count is seen or used as the
reference. The count is stored, if Count is on, when the marker becomes fixed or
when, while fixed, the marker is moved by re-zeroing the reference (if it is the
247
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Marker
reference marker) or via a peak search (since both of these, by definition, use valid
trace data). The count stored in a Fixed marker is lost if the counter is turned off, if
the marker is moved to an inactive trace, or if the marker is moved by adjusting its xvalue.
More Information on "Counter"
When the counter is on, the count (or the delta count) for the selected marker is
displayed.
The invalid data indicator (*) will turn on until the completion of the first count.
Marker Count frequency readings are corrected using the Freq Offset function (in
some previous analyzers, they were not). Note however that Marker Delta readings
are not corrected, as any offset would be applied to both.
In zero span on active traces the counter continues to function, counting any signal
near the center frequency of the analyzer.
No signal farther from the marker frequency than the Res BW will be seen by the
counter.
The above command turns on or off the frequency counter. If the specified marker
number in the command is not the selected marker, it becomes the selected
marker. If the specified marker number is not on, FCOunt ON sets it to Normal and
places it at center of screen on the trace determined by the Marker Trace rules.
Once the marker count is on, it is on for any selected marker, not just for the one
used in the command. A 1 is returned to the state query only if marker count is on
and the specified number is the selected marker. The invalid data indicator (*) will
turn on until the completion of the first count but this does not keep a value from
being returned.
Counter Gate
Controls the length of time during which the frequency counter measures the signal
frequency. Longer gate times allow for greater averaging of signals whose frequency
is “noisy”, though the measurement takes longer. If the gate time is an integer
multiple of the length of a power-line cycle (20 ms for 50 Hz power, 16.67 ms for 60
Hz power), the counter rejects incidental modulation at the power line rate. The
shortest gate time that rejects both 50 and 60 Hz modulation is 100 ms, which is the
value chosen in Auto, or on Preset or when Auto Couple is pressed.
The start time of the Gate Time of the counter must be controlled by the same
trigger parameters as controls the sweep. Thus, if the Trigger is not in Free Run, the
counter gate must not start until after the trigger is received and delayed.
Command
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:FCOunt:GATetime
<time>
:CALCulate:MARKer[1]|2|3|4|5|6|7|8|9|10|11|12:FCOunt:GATetime?
Remote Language Compatibility Measurement Application Reference
248
3 RLC Mode & Swept SA Measurement
Marker
:CALCulate:MARKer
[1]|2|3|4|5|6|7|8|9|10|11|12:FCOunt:GATetime:AUTO OFF|ON|0|1
:CALCulate:MARKer
[1]|2|3|4|5|6|7|8|9|10|11|12:FCOunt:GATetime:AUTO?
Example
CALC:MARK2:FCO:GAT 1e–2 sets the gate time for Marker 2 to 10^(–2) s = 10 ms.
Preset
100 ms
ON
Min/Max
1 μs/500 ms
State
Saved
Saved in instrument state.
Notes
When Auto Couple is pressed, Gate Time is set to 100 ms.
This command causes the specified marker to become selected.
Backwards Compatibility
:CALCulate:MARKer[1]|2|3|4:FCOunt:RESolution <freq>
:CALCulate:MARKer[1]|2|3|4:FCOunt:RESolution?
This command is provided for ESA compatibility, which allowed the user to control
the gate resolution, rather than the gate time.
:CALCulate:MARKer[1]|2|3|4:FCOunt:RESolution <freq> Sets the gate time to
1/freq
:CALCulate:MARKer[1]|2|3|4:FCOunt:RESolution? Returns 1/gate_time
:CALCulate:MARKer[1]|2|3|4:FCOunt:RESolution:AUTO OFF|ON|0|1 is accepted and
ignored
:CALCulate:MARKer[1]|2|3|4:FCOunt:RESolution:AUTO? Always returns 1
All of these commands cause the marker to become selected.
:CALCulate:MARKer[1]|2|3|4:FCOunt:RESolution:AUTO ON|OFF|1|0
:CALCulate:MARKer[1]|2|3|4:FCOunt:RESolution:AUTO?
249
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Meas Setup
Meas Setup
Opens a menu that allows you to set up the measurement.
RLC Config Tab
This tab appears only when the N9061C Remote Language Compatibility
Measurement Application is selected. It contains controls that are specific to this
application.
Compatibility Model
This key selects which legacy instrument to emulate. The selected instrument
determines the response to the “ID?” remote command, and affects the behavior of
commands such as IP. You can use any command offered by any of the legacy
instruments regardless of the language setting, but if the command is not correct for
the selected legacy instrument there is no guarantee that the command will work as
expected. This does not affect the response to the SCPI command “*IDN?”
The remote command “ID?” or “:SYST:LANG?” returns exactly which legacy model is
being emulated.
In cases where a language is selected with implied different frequency range than
the current base box supports, the frequency range will be clipped to the outer limits
of the base box.
For example, 8566B 2GHz to 22 GHz language selected on a N9020A 20Hz – 3.6
GHz option the frequency range will be clipped to 0Hz – 3.6GHz.
Note that an X-Series that is emulating a legacy instrument will continue to emulate
that legacy instrument even if the X-Series is rebooted, and will restart in the startup
state of the legacy instrument.
Control
Path
Meas Setup, RLC Config
Control
Type
Dropdown
Remote
Command
SYSTem:LANGuage HP8566A | HP8566B | HP8568A | HP8568B |
HP8560E | HP8561E| HP8562E | HP8563E | HP8564E | HP8565E |
HP8590L | HP8592L | HP8594L | HP8591E | HP8593E | HP8594E |
HP8595E | HP8596E
SYSTem:LANGuage?
Example
SYST:LANG HP8566A
Range
HP8560E/EC | HP8561E/EC | HP8562E/EC | HP8563E/EC | HP8564E/EC | HP8565E/EC |
HP8566A | HP8566B | HP8568A | HP8568B
Preset
HP8563E/EC. Unaffected by power cycle or mode preset, but preset by Restore Mode
Defaults. Pressing X-Series’s instrument preset key will result in a legacy-equivalent
preset.
Couplings
The selected language has the following impact:
Remote Language Compatibility Measurement Application Reference
250
3 RLC Mode & Swept SA Measurement
Meas Setup
1. It determines the response to the “ID?” remote command.
2. It affects the behavior of any command which had different implementation in
the different boxes, such as “KS”
3. It affects the frequency range of commands such as FS and LF.
4. It changes defaults to match the appropriate instrument, for purposes of
instrument preset (note that the instrument will automatically preset on
language switch).
5. It will NOT affect the Preferences parameters in the Preference menu or the
Logging parameters in the Logging menu.
As we do not expect customers to use commands which their selected legacy instrument
never supported, we do not need to block customers from using commands which a
different instrument supported. For example, the “CR” command may work even if the
selected language is HP8563E.
Note HP856xE and HP856xEC analyzers both respond as HP856xE to the “ID?” command.
As such they will share the same softkey front panel.
State
Saved
Saved in instrument state.
Initial
S/W
Revision
Prior to A.02.00
Modified
at S/W
Revision
A.18.00
Changing the RLC Language performs a mode preset into the new mode, which
includes the following:
RLC App
All
Behavior
– Base Instrument Preset
– Internal oscillator [:ROSC:SOUR:TYPE INT]
– RBR set to 0.011
– Trace update on recall
HP8566A/B
– Sets the number of trace points to 1001
– Start frequency to 2GHz
– Stop frequency to 22GHz
– RF coupling to DC
– Restrict Sweep Type to swept [:SWE:TYPE SWE]
– Sets the Video Bandwidth one step higher than the resolution bandwidth
251
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Meas Setup
– Sets DL to –45 dBm
HP8568A/B
– Sets the number of trace points to 1001
– Start frequency to 0Hz
– Stop frequency to 1.5GHz
– RF coupling to DC
– Restrict Sweep Type to swept [:SWE:TYPE SWE]
– Sets the Video Bandwidth one step higher than the resolution bandwidth
– Sets DL to –45 dBm.
HP8560E
HP8561E
HP8562E
HP8563E
HP8564E
HP8565E
– Sets the number of trace points to 601
– Sets the start frequency to 2.75 GHz 62A and 63A all others 0 Hz
– Sets the stop frequency: 2.9 GHz (60A, 62B, 60E), 6.5 GHz (61A, 61B, 61E),
13.2 GHz (62E), 22GHz (62A, 62B) 26.5GHz (62A#026, 63A#026, 63E), 40
GHz (64E), or 50 GHz (65E)
– Sets the instrument in CF/SP mode
– Sets the Video Bandwidth to Resolution Bandwidth Ratio to 1
– RF coupling to DC (62A, 62A#026, 62B, 63A, 63A#026, 63E, 64E, 65E) or AC
(60A, 60E, 61A, 61B, 61E, 62E).
– Set Sweep Type to auto [:SWE:TYPE AUTO]
– Sets DL to 0 dBm.
Cmd Error
Enables or disables the display of the “CMD ERR” error messages, which will appear
in the Message bar as an advisory message, ERR? message buffer and Cmd error
log.
The format of the errors are as follows:
CMD ERR, <string>
This occurs if either the command syntax or any of its parameters are incorrectly
formed.
The length of <string> is limited to the first 20 characters of the input string
(message unit).
Further details of these errors, after they have occurred, can be reviewed in the
Command Error Log, provided that Cmd Error Logging has been enabled.
The selected value is preserved after presetting or power cycling the instrument.
Disabling the display of command errors disables the display of all error types.
Remote Language Compatibility Measurement Application Reference
252
3 RLC Mode & Swept SA Measurement
Meas Setup
Control Path
Meas Setup, RLC Config
Control Type
Toggle
Preset
Previously selected value
Initial S/W Revision
Prior to A.02.00
Modified at S/W Revision
A.18.00
Logging
Pressing the Logging button puts you in the Logging screen. When you are in the
logging screen, the log will be displayed, obscuring the main screen display. This
display will not update as new items are added to the log file unless the Refresh
control is pressed.
The Command Error Log records details of command errors and known legacy
commands that have been received, but that are not supported by the Remote
Language application.
If enabled, the RLC Command Error Log may be displayed onscreen or accessed in
the file “Logfile.txt”. The Log file will be located in the D: drive at location \User_My_
Documents\[USERNAME]\My Documents\RLC\data folder of the base instrument as
a plain text file, and be accessible for users. The log is not cleared on power-up,
language switch, or mode switch. If the log file becomes full, the first 10% of the log
will be discarded without signaling the user. The log file has a maximum capacity of
10M.
Control Path
Meas Setup, RLC Config
Control Type
Dialog
Initial S/W Revision
Prior to A.02.00
Modified at S/W Revision
A.18.00
Command Error Log
Enables or disables the RLC Command Error Log. This log keeps track of the
command errors and unsupported commands. The log may be disabled to allow
operation in a secure environment that would not wish to have a record of
commands used.
If enabled, the Command Error Log may be displayed onscreen or accessed in the
file “Logfile.txt”.
253
Control Path
Meas Setup, RLC Config, Logging
Control Type
Toggle
Preset
Off. Unaffected by power cycle or mode preset, but can be preset using
Restore Mode Defaults.
Initial S/W Revision
Prior to A.02.00
Modified at S/W
Revision
A.18.00
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Meas Setup
Refresh
Refreshes the RLC Command Error Log display with commands sent since the
display was opened. New entries added to the log since the display was opened will
be added to the displayed log. If there are new entries, the log will be scrolled to the
bottom.
Control Path
Meas Setup, RLC Config, Logging
Control Type
Immediate Action
Initial S/W Revision
Prior to A.02.00
Modified at S/W Revision
A.18.00
Clear Log
Clears the RLC Command Error Log, erasing the contents of the log file. The log can
only be cleared by using the clear log function. The log is not cleared on power-up,
language switch, or mode switch.
Control Path
Meas Setup, RLC Config, Logging
Control Type
Immediate Action
Initial S/W Revision
Prior to A.02.00
Modified at S/W Revision
A.18.00
Preferences
In RLC mode, each preference is a configurable feature. The default value for each
parameter in the Preferences menu is the closest emulation of legacy behavior.
Preferences are persistent. If they are changed by the user, they are unaffected by
mode switching, language switching, mode preset, or power on. They are only
preset to their default state using theRestore Mode Defaults key in the Mode Setup
menu, INST:DEF command or SYST:PRES:PERS.
Control Path
Meas Setup
Limit RBW/VBW
Limits the valid resolution bandwidth and video bandwidth values to those
appropriate for the currently selected remote language.
The restriction on resolution and video bandwidth ranges is solely intended to avoid
situations where RBW or VBW is significantly lower than legacy, as significant
increases in sweep time could result in timeouts in legacy code.
Limit Resolution Bandwidth / Video Bandwidth limits the valid resolution bandwidth
and video bandwidth values to those appropriate for the currently selected
language. While this limitation reduces measurement flexibility, it helps to ensure
that the measurement time in emulation mode is the same as the legacy
measurement time, and ensures that the responses to RB? and VB? match the
legacy instrument.
Remote Language Compatibility Measurement Application Reference
254
3 RLC Mode & Swept SA Measurement
Meas Setup
Note that limiting the resolution bandwidths on HP8590-series analyzers prevents
usage of the EMI bandwidths 200 Hz, 9 kHz, and 120 kHz which were available as
options. If your measurement requires those bandwidths, turn this option off.
Control
Path
Meas Setup, RLC Config, Preferences
Control
Type
Toggle
Remote
Command
[:SENSe]:RLC:BANDwidth:LIMit ON|OFF|1|0
Example
:RLC:BAND:LIM ON
Preset
ON. Unaffected by power cycle or mode preset, but can be preset using Restore Mode
Defaults.
Couplings
If the selected RLC Language is HP8566A/B or HP8568A/B, setting this to ON causes the
resolution and video bandwidths to be limited to the following range of values:
– Resolution Bandwidth Range: 10 Hz, 30 Hz, 100 Hz, 300 Hz, 1 kHz, 3 kHz, 10 kHz, 30
kHz, 100 kHz, 300kHz, 1 MHz, 3 MHz
– Video Bandwidth Range: 1 Hz, 3 Hz, 10 Hz, 30 Hz, 100 Hz, 300 Hz, 1 kHz, 3 kHz, 10
kHz, 30 kHz, 100 kHz, 300kHz, 1 MHz, 3 MHz
If the selected RLC Language is HP856x, setting this to ON causes the resolution and
video bandwidths to be limited to the following range of values:
– Resolution Bandwidth Range: 1 Hz, 3 Hz, 10 Hz, 30 Hz, 100 Hz, 300 Hz, 1 kHz, 3 kHz,
10 kHz, 30 kHz, 100 kHz, 300kHz, 1 MHz, 2 MHz
– Video Bandwidth Range: 1 Hz, 3 Hz, 10 Hz, 30 Hz, 100 Hz, 300 Hz, 1 kHz, 3 kHz, 10
kHz, 30 kHz, 100 kHz, 300kHz, 1 MHz, 3 MHz
If the selected RLC Language is HP859x, setting this to ON causes the resolution and
video bandwidths to be limited to the following range of values:
– Resolution Bandwidth Range: 300 Hz, 1 kHz, 3 kHz, 10 kHz, 30 kHz, 100 kHz,
300kHz, 1 MHz, 3 MHz
– Video Bandwidth Range: 1 Hz, 3 Hz, 10 Hz, 30 Hz, 100 Hz, 300 Hz, 1 kHz, 3 kHz, 10
kHz, 30 kHz, 100 kHz, 300kHz, 1 MHz, 3 MHz
Note: This restriction on resolution & video bandwidth range changes to use the base XSeries range of bandwidths if the detector type is set to Quasi Peak, EMI Peak, MIL Peak,
EMI Average or Average.
Setting this to OFF causes the resolution & video bandwidth filters to use the base XSeries range of values.
Note that limiting the resolution bandwidths on 9x-series analyzers prevents usage of the
EMI bandwidths 200 Hz, 9 kHz, and 120 kHz.
255
Initial
S/W
Revision
Prior to A.02.00
Modified
A.18.00
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Meas Setup
at S/W
Revision
Atten Offset
Adds an offset to any attenuation selected from the front panel, remote interface, or
auto coupling rule. Display and query results will continue to return the old value.
Attenuation Offset will allow greater input power to the spectrum analyzer, while
significantly increasing the noise floor. Since many of the older spectrum analyzers
had noise floor 10 dB higher than the X-Series, this will give the most accurate
emulation.
Control
Path
Meas Setup, RLC Config, Preferences
Control
Type
Numeric Toggle
Remote
Command
N/A
Preset
0 dB, Off. Unaffected by power cycle or mode preset, but can be preset using Restore
Mode Defaults.
Couplings
All attenuation values from any source (GUI, RUI, or Auto coupling rules) will be
increased by 10 dB when setting the actual attenuator, up to the maximum allowed by
the X-Series. The GUI and RUI will continue to report the same value that they used to
report (which will now be incorrect by 10 dB).
Initial
S/W
Revision
Prior to A.02.00
Modified
at S/W
Revision
A.18.00
Sweep Type Rule
Changes the Auto rules for determining whether the instrument uses FFT or Swept
mode (this can be manually overridden).
FFT mode offers substantially faster measurements in some cases. The HP8566/68
series and the HP8590 series did not have FFT mode capability, so most accurate
emulation requires that the instrument preserves Swept mode unless the user
manually overrides that setting.
HP8560-series analyzers used both FFT and Swept mode, in which case “Legacy” is
equivalent to “Dynamic range”.
Control Path
Meas Setup, RLC Config, Preferences
Control Type
Dropdown
Remote Command
[:SENSe]:RLC:SWEep:TYPE:AUTO:RULes
AUTO|SPEed|DRANge|LEGACY
Remote Language Compatibility Measurement Application Reference
256
3 RLC Mode & Swept SA Measurement
Meas Setup
Example
:RLC:SWE:TYPE:AUTO:RUL SPE
Range
Auto | Best Speed | Best Dynamic Range | Legacy
Preset
Auto. Unaffected by power cycle or mode preset, but can be preset using
Restore Mode Defaults.
Couplings
See Couplings, below
Initial S/W Revision
Prior to A.02.00
Modified at S/W
Revision
A.18.00
Couplings
This is identical to the Sweep/Control->Sweep Setup->Sweep Type Rules menu,
except for one additional setting; Legacy. For 8560-series, this is identical to
DRange; for 8590-series and 8566/68-series, Legacy rules indicate that FFT sweeps
should not be used unless set explicitly.
Sweep Type Rules
856x
859x / 8566 / 8568
Speed
GPSA Sweep Type: AUTO
GPSA Sweep Type: AUTO
FFT Width : Auto
FFT Width : N/A
GPSA S.T. Rules: BEST SPEED
GPSA S.T. Rules: BEST SPEED
GPSA Sweep Type: AUTO
GPSA Sweep Type: AUTO
FFT Width : Auto
FFT Width : N/A
GPSA S.T. Rules: BEST D. RANG
GPSA S.T. Rules: BEST D. RANGE
GPSA Sweep Type: AUTO
GPSA Sweep Type: SWEPT
FFT Width : <4.01
FFT Width : N/A
GPSA S.T. Rules: BEST D. RANG
GPSA S.T. Rules: N/A
GPSA Sweep Type: AUTO
GPSA Sweep Type: SWEPT
FFT Width : Auto
FFT Width : N/A
GPSA S.T. Rules: BEST D. RANG
GPSA S.T. Rules: N/A
Dynamic Range
Legacy
Auto
AC/DC Preset Default
Allows the user to define the behavior for AC and DC coupling mode when presetting
the instrument. This command is needed because legacy instruments had AC cutoff
frequency of 100kHz, whereas X-Series has AC cutoff frequency at 10MHz.
When the user want to do measurements, he usually first send “IP” to preset the
system. This functions defines the RF coupling after an “IP”. You can choose AC
coupled, DC coupled or the default value of the X-Series instrument.
257
Control Path
Meas Setup, RLC Config, Preferences
Control Type
Dropdown
Range
As X-Series | AC Coupled | DC Coupled
Preset
As X-Series. Unaffected by power cycle or mode preset, but can be preset using
Restore Mode Defaults.
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Meas Setup
Initial S/W
Revision
Prior to A.02.00
Modified at S/W
Revision
A.18.00
Limit Sweep Time
Allows the user to constrain the sweep time to no less than the minimum sweep
time of the legacy boxes. If set to On, the sweep time will be constrained no less
than the value listed in the table below. If set to Off, no constraint is applied.
Instrument
Non Zero Span
Zero Span
HP8566/68
20ms
1 µs
HP856x
50ms
50 µs
In general the X-Series has sweep times much faster than legacy instruments, and
this can cause problems in test systems with critical timing dependencies. This
control keeps the analyzer from sweeping faster than the legacy product was
capable of.
Control Path
Meas Setup, RLC Config, Preferences
Control Type
Toggle
Remote Command
[:SENSe]:RLC:SWEep:TIME:LIMit ON|OFF|1|0
Example
:RLC:SWE:TIME:LIM ON
Preset
On. Unaffected by power cycle or mode preset, but can be preset using
Restore Mode Defaults.
Initial S/W Revision
Prior to A.02.00
Modified at S/W
Revision
A.18.00
ID Response
Allows you to define the exact response to the query “ID?”, because scripts may
sometimes require a specific response.
Control Path
Meas Setup, RLC Config, Preferences
Control Type
Dropdown
Range
System Option | User Option
Preset
As X-Series. Unaffected by power cycle or mode preset, but can be preset using
Restore Mode Defaults.
Initial S/W
Revision
Prior to A.02.00
Modified at S/W
Revision
A.18.00
Remote Language Compatibility Measurement Application Reference
258
3 RLC Mode & Swept SA Measurement
Meas Setup
User ID
Lets you enter an ID string to be returned when you have selected “User Option” on
the System/User Option control. When you tap this control, the onscreen keyboard
opens up, allowing you to enter a text string.
Control Path
Meas Setup, RLC Config, Preferences
Control Type
Text
Dependencies
60 characters max
Preset
“” (null String), not affected by Mode Preset, preset by Restore Mode Defaults.
Initial S/W Revision
A.18.00
KSK Tolerance
Allows you to define the tolerance for “KSK” when searching the next peak. Because
the accuracy of the X-Series instrument is much higher than that of the legacy
instruments, scripts may sometimes be unable to find the correct next peak.
Control Path
Meas Setup, RLC Config, Preferences
Control Type
Numeric Toggle
Preset
0.1 dB, Off. Unaffected by power cycle or mode preset, but can be preset using
Restore Mode Defaults.
Initial S/W
Revision
Prior to A.02.00
Modified at S/W
Revision
A.18.00
Analog Out Preset Default
Allows you to define the behavior for analog out mode when presetting the
instrument. This command is needed because legacy instruments have different
behaviors when presetting.
In 6x series, the preset default is Screen Video. In other models, it is OFF.
Control Path
Meas Setup, RLC Config, Preferences
Control Type
Dropdown
Range
As X-Series | As Legacy
Preset
As X-Series. Unaffected by power cycle or mode preset, but can be preset using
Restore Mode Defaults.
Initial S/W
Revision
Prior to A.02.00
Modified at S/W
Revision
A.18.00
No Terminator
Allows you to accept a command stream that has no terminator, such as “\r” or “ ”.
259
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Meas Setup
Currently, only “ERR?” is accepted as a terminator.
Control Path
Meas Setup, RLC Config, Preferences
Control Type
Toggle
Preset
Off. Unaffected by power cycle or mode preset, but can be preset using
Restore Mode Defaults.
Initial S/W Revision
Prior to A.02.00
Modified at S/W
Revision
A.18.00
Settings Tab
Average/Hold Number
Sets the terminal count number N for Average, Max Hold and Min Hold trace types.
This number is an integral part of how the average trace is calculated. Basically,
increasing N results in a smoother average trace.
Restarting any of these functions (Average, Max Hold or Min Hold) restarts all of
them, as there is only one count.
See "More Information" on page 260
See "AVER:CLE command" on page 261
Command
[:SENSe]:AVERage:COUNt <integer>
[:SENSe]:AVERage:COUNt?
Example
AVER:COUN 100
Preset
100
Min/Max
1/10000
Status Bits/OPC
dependencies
See the Sweep key description for a discussion of the Sweeping,
Measuring, Settling and OPC
bits, and the Hi Sweep line. All are affected when a sequence is reset.
State Saved
Saved in instrument state
Backwards Compatibility Notes
In older analyzers, when changing the Average Count (now Average/Hold
Number), you had to re-start the trace at the beginning of a sweep to ensure valid
average data. Now, the system will ensure valid results when changing the count
limit.
More Information
When in Single, the sweep stops when N is reached. You can add more sweeps by
increasing the Average/Hold Number. For example, if you want to add one more
Average, or one more trace to Max Hold or Min Hold, simply increment this number
by one, which you can do by pressing the Up key while Average/Hold Number is the
active function.
Remote Language Compatibility Measurement Application Reference
260
3 RLC Mode & Swept SA Measurement
Meas Setup
In Cont (continuous), averaging and holding continues even after N is reached.
Therefore, using doing trace holding in Cont, the value of N is irrelevant. But for
averaging, each new sweep is exponentially averaged in with a weighting equal to
N.
For details of how the average trace is calculated and how this depends on the
Average/Hold Number, see "Average Type" on page 261. For details on how the
various control functions in the instrument start and restart averaging, see
"Average Type" on page 261.
AVER:CLE command
The AVER:CLE command (below) resets the average/hold count and does an
INIT:IMM, which begins another set of sweeps when trigger conditions are satisfied.
It only does this if an active trace is in Average or Hold type.
Command
[:SENSe]:AVERage:CLEar
Example
AVER:CLE
sets the current count (k and K) to 1 and restarts the averaging process.
Notes
When the instrument receives this command it performs an INIT:IMM, if and only if
there is an active trace in Max Hold, Min Hold, or Average type.
Average Type
Lets you control the way averaging is done by choosing one of the following
averaging scales: Log-Power (Video), Power (RMS), or Voltage averaging. Also lets
you choose Auto Average Type (default).
There are four different averaging processes in the Swept SA measurement, and all
of them are affected by this setting: Trace Averaging, the Average detector, the
Noise Marker, and VBW filtering.
See "More Information" on page 262
Remote Command
[:SENSe]:AVERage:TYPE LOG|RMS|SCALar
[:SENSe]:AVERage:TYPE?
[:SENSe]:AVERage:TYPE:AUTO OFF|ON|0|1
[:SENSe]:AVERage:TYPE:AUTO?
Preset
LOG/ON
Range
Log-Power (Video) | Power (RMS) | Voltage
State Saved
Saved in instrument state
Backwards Compatibility Notes
The following legacy parameters to the [:SENSe]:AVERage:TYPE command are
aliased as shown:
LINear aliased to SCALar, sets Scalar averaging
VOLTage aliased to SCALar, sets Scalar averaging
VIDeo aliased to LOG, sets Log-Power averaging
261
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Meas Setup
LPOWer aliased to LOG, sets Log-Power averaging
POWer aliased to RMS , sets RMS averaging
More Information
There are four different averaging processes in the Swept SA measurement that
are affected by this setting:
– Auto - When Auto is selected, the analyzer chooses the optimum type of
averaging for the current instrument measurement settings. When one of the
average types is selected manually, the analyzer uses that type regardless of
other analyzer settings, and shows Man on the Average Type toggle.
– Trace Averaging - averages signal amplitudes on a trace-to-trace basis. When
performing Trace Averaging, the equation that is used to calculate the
averaged trace depends on the average type. The average type applies to all
traces in Trace Average (it is not set on a trace-by-trace basis).
– Average detector - averages signal amplitudes during the time or frequency
interval represented by a particular measurement point.
– Noise Marker - averages signal amplitudes across measurement points to
reduce variations for noisy signals.
– VBW filtering - adds video filtering which is a form of averaging of the video
signal.
Averaging is done by choosing one of the following averaging scales:
Auto
When Auto is selected, the analyzer chooses the optimum type of averaging for
the current instrument measurement settings. When one of the average types is
selected manually, the analyzer uses that type regardless of other analyzer
settings, and shows Man on the Average Type toggle.
Here are the auto-select rules for Average Type:
Auto selects Voltage Averaging if the Detector for any active trace is
EMI Average or QPD or RMS Average; otherwise it selects Power
(RMS) Averaging if a Marker Function (Marker Noise, Band/Intvl
Power) is on, or Detector is set to Man and Average; otherwise if
Amplitude, Scale Type is set to Lin it selects Voltage Averaging;
otherwise, if the EMC Standard is set to CISPR, it selects Voltage;
otherwise Auto selects Log-Power Average.
Note that these rules are only applied to active traces. Traces which
are not updating do not impact the auto-selection of Average
Type.When you select log-power averaging, the measurement
results are the average of the signal level in logarithmic units
(decibels). When you select power average (RMS), all measured
results are converted into power units before averaging and filtering
Remote Language Compatibility Measurement Application Reference
262
3 RLC Mode & Swept SA Measurement
Meas Setup
operations, and converted back to decibels for displaying.
Remember: there can be significant differences between the average
of the log of power and the log of the average power.
Log-Power (Video)
The Log-Power averaging type selects the logarithmic (decibel) scale for all
filtering and averaging processes. This scale is sometimes called “Video” because
it is the most common display and analysis scale for the video signal within a
spectrum analyzer. This scale is excellent for finding CW signals near noise, but its
response to noise-like signals is 2.506 dB lower than the average power of those
noise signals. This is compensated for in the Marker Noise function.
The equation for trace averaging on the log-pwr scale is shown below, where K is
the number of averages accumulated. (In continuous sweep mode, once K has
reached the Average/Hold Number, K stays at that value, providing a continuous
running average.)
New avg = ((K–1)Old avg + New data)/K
This equation assumes all values in decibel scale.
Power (RMS)
In this average type, all filtering and averaging processes work on the power (the
square of the magnitude) of the signal, instead of its log or envelope voltage. This
scale is best for measuring the true time average power of complex signals. This
scale is sometimes called RMS because the resulting voltage is proportional to
the square root of the mean of the square of the voltage.
In the equation for averaging on this scale (below), K is the number of averages
accumulated. (In continuous sweep mode, once K has reached the Average/Hold
Number, K stays at that value, providing a running average.)
New avg = 10 log ((1/K)((K–1)(10Old avg/10)+10New data/10))
This equation assumes all values are in the decibel scale.
Voltage Averaging
In this Average type, all filtering and averaging processes work on the voltage of
the envelope of the signal. This scale is good for observing rise and fall behavior of
AM or pulse-modulated signals such as radar and TDMA transmitters, but its
response to noise-like signals is 1.049 dB lower than the average power of those
noise signals. This is compensated for in the Marker Noise function.
In the equation for averaging on this scale (below), K is the number of averages
accumulated. (In continuous sweep mode, once K has reached the Average/Hold
Number, K stays at that value.)
New avg = 20 log ((1/K)((K–1)(10Old avg/20)+10New data/20))
This equation assumes all values are in the decibel scale.
263
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Meas Setup
Meas Setup Summary Table
This table lets you view and access many of the parameters in the Meas Setup
panel.
Auto Couple
The Auto Couple control immediately puts all Auto/Man functions into Auto for the
current measurement only. It does not affect other measurements in the mode.
In the Auto state, Auto/Man functions are said to be “coupled”, meaning their value
will change depending on changes you make to other values in the measurement.
This helps ensure accurate measurements and optimum dynamic range. Auto
Couple is an immediate action function, and when it is executed, all the Auto/Man
controls for the current measurement are set to Auto and all measurement settings
coupled to the Auto/Man parameters are automatically set to their optimal value.
SCPI Command not available in N9061C.
Meas Preset
This control returns the Meas Local variables in the Swept SA measurement to their
preset values. This is the same as sending the SCPI command CONF:SAN.
The only exception is Limits On/Off, which is a persistent Meas Local variable. It will
be set to Off by a Mode Preset but not by Meas Preset.
Remote Language Compatibility Measurement Application Reference
264
3 RLC Mode & Swept SA Measurement
Meas Setup
Limits Tab
Select Limit
Specifies the selected limit. The term “selected limit” is used throughout to specify
which limit will be affected by the functions.
The selected limit is remembered even when not in the Limit Menu.
Preset
Limit 1, not affected by Mode Preset, preset by Restore Mode Defaults.
State Saved
Saved in instrument state.
Limit
Selects whether the limit and margin are displayed. If Test Limits is on, this also
determines whether the test trace will be tested against the limit. If Limit On/Off is
On, the following occurs:
– The limit line is displayed, in the same color as the limited trace, but paler.
Portions of traces which fail the limits will be displayed in red.
– The margin line is displayed if Margin is on and the Margin Value is non-zero. The
margin line is displayed in the same color as the limit line, but paler still and
dashed. Portions of traces which pass the limits but fail the margin will be
displayed in amber.
– The trace is tested for the purpose of the “Trace Pass/Fail” indication in the
graticule if, in addition to Limit On/Off being On, the trace is displayed and Test
Limits (All Limits) is on. If the trace is not tested, no report of the trace passing or
failing is seen on the graticule. Note that the SCPI queries of Limit Pass/Fail are
independent of these conditions. The test is always performed when queried over
SCPI.
The PASS/FAIL box in the corner of the Meas Bar is only displayed if there is at least
one “Trace Pass/Fail” indication displayed in the graticule.
Note that the red and amber coloring of traces that fail the limits and/or margins only
applies to traces whose X-axis corresponds to the current analyzer X-axis. Traces
that are not updating (in View, for example) will not change color if the analyzer Xaxis settings (e.g., start and stop frequency) do not match those of the trace, for
example if they have been changed since the trace stopped updating. In this case,
the Invalid Data indicator (*) will appear in the upper right corner.
When the limits are frequency limits but the trace is a zero-span trace, the limit trace
is drawn at the limit amplitude of the center frequency. When the limits are time
limits but the trace is a frequency domain trace, the limit trace is drawn according to
the current time axis, with the left of the screen being 0 and the right being equal to
sweep time.
Remote Command
265
:CALCulate:LLINe[1]|2|3|4|5|6:DISPlay OFF|ON|0|1
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Meas Setup
:CALCulate:LLINe[1]|2|3|4|5|6:DISPlay?
Example
:CALC:LLIN2:DISP 2 ON turns on the display for limit line 2.
Preset
OFF
State Saved
Saved in instrument state
Dependencies
This command will generate an “Option not available” error message unless you
have the proper option installed in your instrument. )
Couplings
Limit display ON selects the limit.
Testing is done on all displayed limits if Test Limits (All Limits) is ON.
Entering the limit menu from the User Interface turns on the selected limit.
Backwards Compatibility SCPI
:CALCulate:LLINe[1]|2:STATe OFF|ON|0|1
In the past you had to send the DISP command as well as the STATe command to
get a limit on and testing. Now, the DISP command is sufficient, but we accept the
state command and map it to DISP.
Margin
Selects a margin for this limit, which will cause a trace to Fail Margin when the trace
is between the limit line and the margin line. Portions of the traces which pass the
limit but fail the margin will be displayed in an amber color.
A margin is always specified in dB relative to a limit – an upper limit will always have
a negative margin, and a lower limit will always have a positive margin. If a value is
entered with the incorrect sign, the system will automatically take the negative of
the entered value.
If the limit type is switched from lower to upper while margin is present, the margin
will reverse sign.
When the Margin is selected, it may be turned off by pressing the Margin key until Off
is underlined. This may also be done by performing a preset. Margin is the default
active function whenever the margin is on, and it is not the active function whenever
the margin is off.
The margin lines are displayed in the same color as limit lines, but paler. If the
limited trace is blanked then the limit line and the margin line will be blanked as well.
Remote
Command
:CALCulate:LLINe[1]|2|3|4|5|6:MARGin <rel_ampl>
:CALCulate:LLINe[1]|2|3|4|5|6:MARGin?
:CALCulate:LLINe[1]|2|3|4|5|6:MARGin:STATe OFF|ON|0|1
:CALCulate:LLINe[1]|2|3|4|5|6:MARGin:STATe?
Example
:CALC:LLIN1:MARG –2dB sets limit line 1’s margin to –2 dB (Limit Line 1 is by default
Remote Language Compatibility Measurement Application Reference
266
3 RLC Mode & Swept SA Measurement
Meas Setup
an upper limit).
:CALC:LLIN2:MARG 1dB sets limit line 2’s margin to 1 dB (Limit Line 2 is by default a
lower limit).
:CALC:LLIN2:MARG:STAT OFF !turns off the margin for limit line 2 and removes any
tests associated with that margin line.
Preset
Not affected by Mode Preset, set to 0 dB for all Limits by Restore Mode Defaults.
Min/Max
Min:–40 dB (Upper); 0 dB (Lower)
Max:0 dB (Upper); 40 dB (Lower)
State
Saved
Saved in instrument state.
Notes
The queries “Limit Line Fail?” (:CALCulate:LLINe[1]|2|3|4|5|6:FAIL?) and “Trace
Fail?” (:CALCulate:TRACe[1]|2|3|4|5|6:FAIL?) will return 1 if the margin fails.
Couplings
This will affect :CALC:LLIN3:FAIL or :CALC:TRAC2:FAIL?
Type
Selects whether the limit you are editing is an upper or lower limit. An upper limit
fails if the trace exceeds the limit. A lower limit fails if the trace falls below the limit.
Remote
Command
:CALCulate:LLINe[1]|2|3|4|5|6:TYPE UPPer|LOWer
Example
:CALC:LLIN2:TYPE LOW sets limit line 2 to act as a lower limit.
Preset
Upper for Line 1, 3, and 5; Lower for Line 2, 4, 6. Not affected by Mode Preset, preset
by Restore Mode Defaults.
State Saved
Saved in instrument state.
:CALCulate:LLINe[1]|2|3|4|5|6:TYPE?
Couplings
If a margin has already been set for this limit line, and this key is used to change the
limit type, then the margin value will reverse sign.
Edit Limit
The Edit Limit dialog allows you to edit the content and the properties of the Limit
Line.
When entering the menu, the editor window (with the limit table) turns on, the
selected Limit is turned On and the amplitude scale is set to Log, and the ΔLimit peak
table is turned off. The display of the trace to which the selected limit applies is
turned on (thus, traces in Blank are set to View and traces in Background are set to
On). Turning on the Limit means it’s display will be on, and it’s testing mode will be on
as well. You should turn off any other limits that are on if they interfere with the
editing of the selected limit.
267
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Meas Setup
The table editor will only operate properly if the analyzer is sweeping, because its
updates are tied to the sweep system. Thus, you should not try to use the editor in
single sweep, and it will be sluggish during compute-intensive operations like
narrow-span FFT sweeps.
When exiting the edit menu (by using the Return key or by pressing an instrument
front panel key), the editor window turns off, however the Limit is still on and
displayed, the ΔLimit peak table remains off, and the amplitude scale remains Log.
Limits are turned off by a Preset, but the Limits arrays (data) are only reset (deleted)
by Restore Mode Defaults. They survive shutdown and restarting of the analyzer
application, which means they will survive a power cycle.
When editing a limit, the editor remembers which limit and which element in the limit
array you were editing, and returns you to that limit and that element when you
return to the editor after leaving it.
A remote user can enter or access limit line data via :CALCulate:LLINe
[1]|2|3|4|5|6:DATA
"Select Limit" on page 265
Navigate - lets you move through the table to edit the desired point
Insert Point Below - inserts a point below the current point. The new point is a copy
of the current point. And becomes the current point The new point is not yet entered
into the underlying table, and the data in the row is displayed in light gray
Delete Point - immediately deletes the currently selected point, whether or not that
point is being edited, and selects Navigate. The point following the currently
selected point (or the point preceding if there is none) will be selected.
Navigate
Lets you move through the table to edit the desired point
Edit Limit Settings
The Edit Limit Settings dialog is the second page of the Edit Limits dialog.
To access this dialog, press Edit Limits on the Settings tab. When the Edit Limits
dialog appears, press Settings.
Remote Language Compatibility Measurement Application Reference
268
3 RLC Mode & Swept SA Measurement
Meas Setup
269
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Meas Setup
Test Limits
Selects whether the displayed traces are tested against the displayed limits (i.e.
those for which Limit On/Off is set to On).
For each displayed trace for which a Limit is turned on, a message will be displayed
in the upper-left corner of the graticule to notify whether the trace passes or fails the
limits.
If the trace is at or within the bounds of all applicable limits and margins, the text
“Trace x Pass” will be displayed in green, where x is the trace number. A separate
line is used for each reported trace.
If the trace is at or within the bounds of all applicable limits, but outside the bounds
of some applicable margin, the text “Trace x Fail Margin” will be displayed in amber,
where x is the trace number. A separate line is used for each reported trace.
If the trace is outside the bounds of some applicable limits, the text “Trace x Fail” will
be displayed in red, where x is the trace number. A separate line is used for each
reported trace.
If the trace has no enabled limits, or the trace itself is not displayed, no message is
displayed for that trace.
Remote Language Compatibility Measurement Application Reference
270
3 RLC Mode & Swept SA Measurement
Meas Setup
The PASS/FAIL box in the corner of the Meas Bar is only displayed if there is at least
one “Trace Pass/Fail” indication displayed in the graticule.
If two amplitude values are entered for the same frequency, a single vertical line is
the result. In this case, if an upper line is chosen, the lesser amplitude is tested. If a
lower line is chosen, the greater amplitude is tested.
This command only affects the display, and has no impact on remote behavior. Limit
queries over SCPI test the trace against the limit regardless of whether the trace or
the limit is turned on (exception: the query :CALCulate:TRACe[1]|2|3|4|5|6:FAIL? tests
only the limits that are turned on for that trace).
Remote
Command
:CALCulate:LLINe:TEST OFF|ON|0|1
Example
:CALC:LLIN:TEST ON turns on testing, and displays the results in the upper left
corner.
Preset
On, not affected by Mode Preset, preset by Restore Mode Defaults.
State Saved
Saved in instrument state.
:CALCulate:LLINe:TEST?
X-Axis Unit
Selects how the limit-line segments are defined. Pressing X Axis Unit selects
whether the limit lines will be entered using frequency (Freq) or sweep time (Time) to
define the segments. They can be specified as a table of limit-line segments of
amplitude versus frequency, or of amplitude versus time.. When the X-Axis Unit is
set to Time, a time value of zero corresponds to the start of the sweep, which is at
the left edge of the graticule, and the column and softkey in the Limit Table Editor
will read Time instead of Frequency.
Switching the limit-line definition between Freq and Time will erase all of the current
limit lines. When you do this from the front panel, a warning dialog will appear letting
you know that you are about to erase all the limit lines, and prompting you to select
“OK” if you are sure:
Changing the X Axis Unit will erase all your limit lines. Are you sure you want to do
this? Press Enter or OK to proceed, or Cancel(Esc) to cancel.
Command
:CALCulate:LLINe:CONTrol:DOMain FREQuency|TIME
:CALCulate:LLINe:CONTrol:DOMain?
Example
:CALC:LLIN:CONT:DOM FREQ deletes all currently existing limit lines, then sets all limit
lines to be specified in terms of frequency.
Preset
Freq, not affected by Mode Preset, preset by Restore Mode Defaults.
State
Saved
Saved in instrument state.
Couplings
This affects all limit lines simultaneously, and resets all limit line data except the
.wav file and email address stored in the Actions.
271
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Meas Setup
Delete All Limits
Purges the data from all limit line tables. All limit data will be cleared and returned
to factory preset settings.
When pressed a prompt is placed on the screen that says:
“Please press Enter or OK key to delete all limits. Press ESC or
Cancel to close this dialog.”
The deletion is only performed if you press OK or Enter. After a deletion, the
informational message “All Limits deleted” appears in the MSG line.
Command
:CALCulate:LLINe:ALL:DELete
Example
:CALC:LLIN:ALL:DEL deletes all data for all limit lines.
Meas Standard Tab
Radio Standard Presets
Allows you to specify the radio standard to be used. Spectrum Analyzer mode
supports many radio standards. You can select the desired radio standard using the
Radio Std Presets control.
Command
[:SENSe]:RADio:STANdard[:SELect]
NONE|JSTD|IS95a|IS97D|IS98D|GSM|W3GPP|CDMA2000MC1|C20001X|NADC|PDC|BLU
Etooth|TETRa|WL802DOT11A|WL802DOT11B|WL802DOT11G|HIPERLAN2|DVBTLSN|DVB
TGPN|DVBTIPN|FCC15|SDMBSE|UWBINDOOR|LTEB1M4|LTEB3M|LTEB5M|LTEB10M|LTEB
15M|LTEB20M|WL11N20M|WL11N40M|WL11AC20M|WL11AC40M|WL11AC80M|WL11AC160M
[:SENSe]:RADio:STANdard[:SELect]?
E- RAD:STAN NONE RAD:STAN?
xample
P- NONE
reset
S- Saved in instrument state
ta-
Remote Language Compatibility Measurement Application Reference
272
3 RLC Mode & Swept SA Measurement
Meas Setup
te
Saved
Couplings
By changing the radio standard, the measurement parameters will be
automatically set to an appropriate default value.
Radio Std Preset Table
The Radio Std Preset Table enables you to select the standard for the current
measurement.
Enable Non-Std Meas
Allows you to specify whether all measurements and radio standards are enabled or
not. In default, Enable All Measurements is set to No, so you can select only the
valid combination of preset available standard and measurement. Any measurement
or standard that make the combination that have no valid preset value are grayed
out. When Enable Non-Std Measurements is set to Yes, all measurements and
standard selections are enabled so that you can choose any.
If you select an unavailable measurement or unavailable radio standard using the
Enable Non-Std Meas control, the measurement results may not conform to the
selected standard.
273
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Meas Setup
Command
[:SENSe]:RADio:STANdard:EAMeas YES|NO [:SENSe]:RADio:STANdard:EAMeas?
Example
RAD:STAN:EAM YES RAD:STAN:EAM?
Preset
NO
Range
Yes|No
State Saved
Saved in instrument state.
EMC Standard
This menu allows you to select None (no EMI standard), CISPR (CISPR 16–1–1), and
MIL (MIL–461A). Each standard has a unique way of determining the couplings
between detectors and RBWs, as well as its own set of available RBW’s.
Note that Auto Couple will have no effect on the EMC Standard setting.
Command
[:SENSe]:EMC:STANdard[:SELect] NONE|CISPr|MIL
[:SENSe]:EMC:STANdard[:SELect]?
[:SENSe]:BANDwidth|BWIDth:[:RESolution]:MODE EMI|SAN|OFF
[:SENSe]:BANDwidth|BWIDth:[:RESolution]:MODE?
Example
:EMC:STAN CISP
State Saved
Saved in instrument state
Dependencies
When the EMC Standard changes to CISPR or MIL, the RBW Control key is grayed
out. The Filter Type is then always Gaussian; the Filter BW is chosen as appropriate
for the filter and the standard.
When the EMC Standard changes to None, the Filter Type is set to Gaussian and
the Filter BW is set to –3 dB.
Only appears with Option EMC installed and licensed. If not, the SCPI command
generates a message.
Couplings
The auto rules for detector select Peak for any trace in Auto when the EMI
Standard is CISPR or MIL.
Choosing a CISPR detector or CISPR presets automatically picks the CISPR
Standard, however switching from a CISPR detector has no impact on EMC
Standard.
Backwards Compatibility Notes
This command is mapped to the EMC:STANdard command with the following
Remote Language Compatibility Measurement Application Reference
274
3 RLC Mode & Swept SA Measurement
Meas Setup
mappings: EMI=>CISPr, SAN =>None, and if the legacy command comes in with the
OFF parameter, it sets EMC Standard to None and Res BW to Manual . The query
returns “OFF” if Res BW in Manual, otherwise “EMI” if EMC Standard is CISPR or
MIL, and “SAN” if EMC Standard is None.
CISPR Presets
This group of controls lets you easily set up the analyzer for CISPR measurements.
Selecting a CISPR preset sets the EMI Standard to CISPR, performs an autocouple
all, and sets the Y Axis Unit to dBµV (unless dBuV is grayed out, in which case it will
leave the Y Axis Unit unaffected).
Command
[:SENSe]:FREQuency:CISPr:BAND A|B|C|CD|D|E
Example
FREQ:CISPR:BAND A activates the CISPR preset for Band A
Controls in the CISPR Group
This group contains controls to set the following Presets:
SetupBand
The number of sweep points for each band is roughly calculated by the formula 2*
(Stop Frequency-Start Frequency)/RBW, so that you get two points for every RBW
width. This number is increased as necessary to make it an odd integer, so that you
always end up with an odd number of sweep points. This is desirable so that you
always have a sweep point at the Center Freq.
The table above is based on the fact that the Res BW autocouples to the center
frequency when in the CISPR EMC standard as follows:
275
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Meas Setup
Sweep Points in Band E
Note that the Res BW will be 1 MHz in band E. The number of sweep points for band
E is dependent on the maximum frequency of the analyzer. The formula above gives
the following values for Band E:
Legacy Compat Tab
Certain behaviors in the X-Series analyzers were changed from legacy HP/Agilent
analyzers to give users access to new, more powerful functionality. Keysight
recognizes that from time to time, it is necessary to EXACTLY match legacy
behaviors. The Legacy Compat tab contains controls for setting the Legacy
Compatibility functions, which lets you modify certain behaviors to exactly match our
legacy products.
Average/Hold
In the X-Series analyzers, Max Hold and Min Hold traces were added to the trace
types that were controlled by the Average Number (which became the
Average/Hold Number). For example, setting an Average/Hold number of 100 and
then performing a Max Hold in Single sweep takes 100 traces and then stops, and
pressing Restart restarts the Max Hold Sequence. This allows you to exactly control
Remote Language Compatibility Measurement Application Reference
276
3 RLC Mode & Swept SA Measurement
Meas Setup
how the number of Max Hold traces are taken. However, many users need a way of
stopping and then resuming a Max/Min Hold without clearing the accumulated
result.
Previously you could stop and start Max Hold by going back and forth between
Single and Continuous. Currently, neither the X-Series nor the legacy analyzers like
ESA and PSA clear the Max or Min Hold when going from Cont to Single and vice
versa. You can go to Single to stop temporarily and then resume the Max or Min Hold
by going back to Cont. However, in the X-Series, because Max and Min Hold obey
the Average/Hold number, this is not an effective method for stopping a sweep, until
you have reached the terminal count. Also, Restart is sometimes used as part of this
method and in the X-Series, Restart clears the accumulated Max/Min Hold, whereas
in the PSA (for example) it does not.
The Average/Hold switch in the Legacy Compatibility menu solves this problem.
When this switch is in the “Legacy” position, the following is true for traces in Max
Hold or Min Hold:
– They pay no attention to the Average/Hold number; “Single” for Max Hold and
Min Hold causes one sweep only, so going to Single stops after the current
sweep, and going to Cont starts you going again without clearing the
accumulated result.
– They don’t clear the Max or Min Hold on a Restart or Single or INIT:IMM (changing
a measurement parameter like frequency or bandwidth, etc. would still restart
the Max/Min Hold).
Note that whenever any trace is in Average, the Single/Cont controls do tie in to the
Avg/Hold number and pressing Single will cause a set of sweeps (100 by default).
This is also true in PSA.
SCPI Command not available in N9061C.
State Saved
Saved in instrument state.
Tune & Listen Tab
Demod Type
Selects the type and state of the demodulation.
Command
[:SENSe]:DEMod AM|FM|PM|OFF
[:SENSe]:DEMod?
Example
DEM AM turns amplitude demodulation function ON
Preset
OFF
State Saved
Saved in instrument state.
Dependencies
When Tune & Listen is turned on, all active traces are forced to use the same
detector.
277
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Meas Setup
CISPR detectors (QPD, EMI Avg, RMS Avg) and Tune & Listen are mutually
exclusive. No sound output will be heard if one of these detectors is selected.
Backwards Compatibility Commands
[:SENSe]:DEMod:STATe ON|1
Sending DEM:STAT ON will have the same effect as sending DEM:AM, turning AM
Demod on.
[:SENSe]:DEMod:STATe OFF|0
Sending DEM:STAT OFF will have the same effect as sending DEM:OFF, turning
Demod off.
[:SENSe]:DEMod:STATe?
Queries the state of the Analog Demod Tune and Listen function. The response to
the query is determined by the current setting of [:SENSE]:DEMod AM|FM|PM|OFF.
The response will be 1 if AM, FM, PM are selected, or 0 if OFF is selected.
Backwards Compatibility Notes
In ESA, the command [:SENSe]:DEMod AM|FM would select the demodulation type
but would not activate it (turn it on). In X-Series this command will both select and
activate demodulation.
The X-Series implementation of Demod Tune and Listen does not include Squelch
Control as was supported in ESA.
The speaker control for Tune and Listen for X-Series is done with the volume
up/down and mute hardkeys in the System Settings dialog and is handled by the
Windows operating system. There is no software speaker on/off control as was
supported in ESA.
Demod Time
Sets the amount of time the instrument demodulates the signal after each sweep.
The demodulated signal can be heard through the speaker during demodulation. In
zero span, demodulation can be performed continuously, making this parameter not
applicable, hence it is grayed out in zero span.
Command
[:SENSe]:DEMod:TIME <time>
[:SENSe]:DEMod:TIME?
Example
DEM:TIME 500 ms
DEM:TIME?
Preset
500 ms
Min/Max
2 ms/100 s
State Saved
Saved in instrument state.
Remote Language Compatibility Measurement Application Reference
278
3 RLC Mode & Swept SA Measurement
Meas Setup
AM Channel BW
Sets the RBW setting used by the hardware during the demodulation period in
nonzero spans. Note that this is a separate parameter only for the demodulation
function and does not affect the RBW setting in the BW menu which is used during
the normal sweep. The flat top filter type must be used during the demodulation
period. A 5 kHz Video Bandwidth filter is used.
In Zero Span, the instrument’s RBW & VBW filters are used for the demodulation;
thus, the Channel BW (and RBW filter type) will match those of the instrument. This
allows gap-free listening. The Channel BW key is grayed out and the value displayed
on the key matches the current RBW of the instrument. Upon leaving zero span, the
non-zero-span setting of Channel BW is restored as well as the flattop filter type.
In zero span only, the value is set equal to the instrument’s current RBW value and it
displays that value, but the selection is grayed out.
Command
[:SENSe]:DEMod:AM:BANDwidth:CHANnel <freq>
[:SENSe]:DEMod:AM:BANDwidth:CHANnel?
Example
DEM:AM:BAND:CHAN 200 kHz
Preset
30 kHz
Min/Max
390 Hz/8 MHz
State
Saved
Saved in instrument state.
FM Channel BW
Sets the RBW setting used by the hardware during the demodulation period in
nonzero spans. Note that this is a separate parameter only for the demodulation
function and does not affect the RBW setting in the BW menu which is used during
the normal sweep. The flat top filter type must be used during the demodulation
period. A 5 kHz Video Bandwidth filter is used.
In Zero Span, the instrument’s RBW & VBW filters are used for the demodulation;
thus, the Channel BW (and RBW filter type) will match those of the instrument. This
allows gap-free listening. The Channel BW key is grayed out and the value displayed
on the key matches the current RBW of the instrument. Upon leaving zero span, the
previous setting of Channel BW and the flattop filter type are restored.
In zero span only, the value is set equal to the instrument’s current RBW value and it
displays that value, but the control is grayed out.
Command
279
[:SENSe]:DEMod:FM:BANDwidth:CHANnel <freq>
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Meas Setup
[:SENSe]:DEMod:FM:BANDwidth:CHANnel?
Example
DEM:FM:BAND:CHAN 200 MHz
Preset
150 kHz
Min/Max
390 Hz/8 MHz
State Saved
Saved in instrument state.
ΦM Channel BW
Sets the RBW setting used by the hardware during the demodulation period in
nonzero spans. Note that this is a separate parameter only for the demodulation
function and does not affect the RBW setting in the BW menu which is used during
the normal sweep. The flat top filter type must be used during the demodulation
period. A 5 kHz Video Bandwidth filter is used.
In Zero Span, the instrument’s RBW & VBW filters are used for the demodulation;
thus, the Channel BW (and RBW filter type) will match those of the instrument. This
allows gap-free listening. The Channel BW key is grayed out and the value
displayed on the key matches the current RBW of the instrument. Upon leaving zero
span, the previous setting of Channel BW and the flattop filter type are restored.
In zero span only, the value is set equal to the instrument’s current RBW value and it
displays that value, but the control is grayed out.
Command
[:SENSe]:DEMod:PM:BANDwidth:CHANnel <freq>
[:SENSe]:DEMod:PM:BANDwidth:CHANnel?
Example
DEM:PM:BAND:CHAN 200 MHz
Preset
100 kHz
Min/Max
390 Hz/8 MHz
State Saved
Saved in instrument state.
FM Demod De-emphasis
The De-emphasis setting controls a single-pole filter (6 dB/octave roll off), usually to
counter intentional pre-emphasis in the transmitter. When De-emphasis state is
OFF the hardware digital filter is bypassed, otherwise the setting is applied.
The choices are Off, 25 µs, 50 µs, 75 µs, and 750 µs.
Remote Language Compatibility Measurement Application Reference
280
3 RLC Mode & Swept SA Measurement
Meas Setup
The De-emphasis control is only available when FM is the demod selected. It is
grayed out for AM and ΦM.
[:SENSe]:DEMod:FM:DEEMphasis OFF|US25|US50|US75|US750
Command
[:SENSe]:DEMod:FM:DEEMphasis?
Example
DEM:FM:DEEM US75 sets the de-emphasis for FM demod to 75 µs DEM:FM:DEEM?
Preset
US75 (recommended for US commercial FM 75 µs pre-emphasis)
State Saved
Saved in instrument state.
Advanced Tab
Phase Noise Optimization
Selects the LO (local oscillator) phase noise behavior for various desired operating
conditions.
See "Phase Noise Optimization Auto Rules" on page 284.
Command
[:SENSe]:FREQuency:SYNThesis[:STATe] 1|2|3|4|5
[:SENSe]:FREQuency:SYNThesis[:STATe]?
[:SENSe]:FREQuency:SYNThesis:AUTO[:STATe] OFF|ON|0|1
[:SENSe]:FREQuency:SYNThesis:AUTO[:STATe]?
Example
FREQ:SYNT 2 selects optimization for best wide offset phase noise.
FREQ:SYNT:AUTO ON
Preset
Because this function is in Auto after preset, and because Span after preset > 314.16
kHz, the state of this function after Preset will be 2
ON
Range
EP0: "Best Close-in Φ Noise" on page 282|"Best Wide-offset Φ Noise" on page 283|"Fast
Tuning" on page 283|"Balance Noise and Spurs" on page 282|"Best Spurs" on page 282
See "Range (Long Form)" on page 283
Notes
Parameter:
1: balances close-in phase noise with spur avoidance. In instruments without EP0
optimizes phase noise for small frequency offsets from the carrier.
2: optimizes phase noise for wide frequency offsets from the carrier.
3: optimizes LO for tuning speed
4: balances close-in phase noise with spur avoidance. In instruments without EP0
this setting is accepted but no action taken.
5: emphasizes spur avoidance with close-in phase noise performance. In
instruments without EP0 this setting is accepted but no action taken.
281
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Meas Setup
The actual behavior varies somewhat depending on model number and option; you
always get fast tuning by choosing #3, but in some models, the “Fast Tuning”
choice is identical to the “Best Close-In” choice. Specifically:
Dependencies
Does not appear in all models. The control is blank in those models, but the SCPI
command is accepted for compatibility (although no action is taken).
More Information
The Phase Noise Optimization control lets you optimize the setup and behavior of
the Local Oscillator (LO) depending on your specific measurement conditions. You
may wish to trade off noise and speed, for example, to make a measurement faster
without regard to noise or with optimum noise characteristics without regard to
speed.
Auto
SCPI Example FREQ:SYNT:AUTO ON
Selects the LO (local oscillator) phase noise behavior to optimize dynamic range
and speed for various instrument operating conditions. See Phase Noise
Optimization Auto Rules for details on the Auto rules.
Best Close-in Φ Noise
SCPI Example FREQ:SYNT 1
The LO phase noise is optimized for smaller offsets from the carrier, at the expense
of phase noise farther out.
The actual frequency offset within which noise is optimized is shown with in square
brackets, as this can vary depending on the hardware set in use. For example, in
some analyzers this annotation appears as [offset <20 kHz]
The LO is configured for the best possible phase noise at offsets up to 600 kHz from
the carrier, regardless of spurious products that occur with some center
frequencies.
Balance Noise and Spurs
SCPI Example FREQ:SYNT 4
Tthe LO is configured for the best possible phase noise at offsets up to 600 kHz
from the carrier whenever there are no significant spurs within the span observed
with an on-screen carrier. When there will be such a spur, the LO is reconfigured in
a way that allows the phase noise to increase by 7 dB mostly within ±1 octave
around 400 kHz offset. The spurs will always be below −70 dBc.
Best Spurs
SCPI Example FREQ:SYNT 5
The LO is configured for better phase noise than the “Wide-Offset” case close to
the carrier, but the configuration has 11 dB worse phase noise than the “Best
Close-In” case mostly within ±1 octave around 300 kHz offset. Spurs are even
Remote Language Compatibility Measurement Application Reference
282
3 RLC Mode & Swept SA Measurement
Meas Setup
lower than in the “Balance Noise and Spurs” case at better than −90 dBc, whether
or not the carrier is on-screen.
This setting is never selected when Phase Noise Optimization is in Auto, you must
select it manually.
Best Wide-offset Φ Noise
SCPI Example FREQ:SYNT 2
The LO phase noise is optimized for wider offsets from the carrier. Optimization is
especially improved for offsets from 70 kHz to 300 kHz. Closer offsets are
compromised and the throughput of measurements (especially remote
measurements where the center frequency is changing rapidly), is reduced.
The actual frequency offset beyond which noise is optimized is shown with in
square brackets, as this can vary depending on the hardware set in use. For
example, in some analyzers this annotation appears as [offset >30 kHz]
The LO is configured for the best possible phase noise at offsets up to 600 kHz from
the carrier whenever there are no significant spurs within the span observed with
an on-screen carrier. When there will be such a spur, the LO is reconfigured in a
way that allows the phase noise to increase by 7 dB mostly within ±1 octave around
400 kHz offset. The spurs will always be below −70 dBc.
Fast Tuning
SCPI Example FREQ:SYNT 3
In this mode, the LO behavior compromises phase noise at many offsets from the
carrier in order to allow rapid measurement throughput when changing the center
frequency or span. The term “fast tuning” refers to the time it takes to move the
local oscillator to the start frequency and begin a sweep; this setting does not
impact the actual sweep time in any way.
The LO behavior compromises phase noise at offsets below 4 MHz in order to
improve measurement throughput. The throughput is especially affected when
moving the LO more than 2.5 MHz and up to 10 MHz from the stop frequency to the
next start frequency.
In instruments with Option EP0, this is the same configuration as the Best Spurs
configuration. It is available with this “Fast Tuning” label to inform the user, and to
make the user interface more consistent with other X-Series analyzer family
members.
(In models whose hardware does not provide for a fast tuning option, the settings
for Best Close-in Φ Noise are used if Fast Tuning is selected. This gives the fastest
possible tuning for that hardware set.)
Range (Long Form)
Best Close-In ΦNoise
[offset < 600 kHz] |
Balance Noise & Spurs
[offset < 600 kHz] |
283
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Meas Setup
Best Spurs
[offset < 600 kHz] |
Best Wide-Offset ΦNoise
[offset > 800 kHz] |
Fast Tuning
[same as Close-in]
Phase Noise Optimization Auto Rules
Auto will choose:
Balanced Noise and Spurs whenever:
Center frequency is < 699.9 kHz
Otherwise, Auto will choose Fast Tuning whenever:
Span > 114.1 MHz, or when
RBW > 800 kHz
Otherwise, Auto will choose Best Wide-offset Φ Noise whenever:
RBW > 290 kHz, or when
Span > 4.2 MHz
Otherwise, Auto will choose Balanced Noise and Spurs.
The RBW to be used in the calculations above is the equivalent –3 dB bandwidth of
the current RBW filter.
These rules apply whether in swept spans, zero span, or FFT spans.
ADC Dither
Accesses the menu to control the ADC Dither function. The dither function enhances
linearity for low level signals at the expense of reduced clipping-to-noise ratio. The
reduced clipping-to-noise ratio results in higher noise, because we work to ensure
that the clipping level of the ADC relative to the front terminals remains unchanged
with the introduction of dither, and this results in reduced ADC dynamic range. So
making measurements with ADC dither gives you better amplitude linearity, but
turning ADC dither off gives you a lower noise floor (better sensitivity).
With dither on, the third-order distortions are usually invisible for mixer levels below
–35 dBm. With dither off, these distortions can be visible, with typical power levels of
–110 dBm referred to the mixer. Detection nonlinearity can reach 1 dB for dither off
at mixer levels around –70 dBm and lower, while the specified nonlinearity is many
times smaller with dither on.
When ADC Dither is on, the linearity of low-level signals is improved. The enhanced
linearity is mostly improved scale fidelity. The linearity improvements of dither are
Remote Language Compatibility Measurement Application Reference
284
3 RLC Mode & Swept SA Measurement
Meas Setup
most significant for RBWs of 3.9 kHz and less in swept mode, and FFT widths of 4 kHz
and less in FFT mode.
The increased noise due to turning dither on is most significant in low band (0 to 3.6
GHz) with IF Gain set to Low, where it can be about 0.2 dB.
Command
[:SENSe]:ADC:DITHer[:STATe] OFF|ON|HIGH
[:SENSe]:ADC:DITHer[:STATe]?
[:SENSe]:ADC:DITHer:AUTO[:STATe] OFF|ON|0|1
[:SENSe]:ADC:DITHer:AUTO[:STATe]?
Example
ADC:DITH HIGH sets the ADC dither setting to High
ADC:DITH ON sets the ADC dither setting to Medium
In older instruments the “Medium” key was labeled “On” and the SCPI for this setting is
NOT changing.
ADC:DITH:AUTO ON
Preset
AUTO
ON
Range
High | Medium | Off
State
Saved
Saved in instrument state.
Dependencies
In some models, the “High” parameter is not available. (Models without the 16-bit
ADC) In some instruments, the HIGH parameter is honored and the HIGH state set,
and returned to a query, but the Medium dither level is actually used.
Backwards Compatibility
!The old command ![:SENSe]:ADC:DITHer AUTO ! is aliased to !
[:SENSe]:ADC:DITHer:AUTO[:STATe] ON; because of this, the !
[:SENSe]:ADC:DITHer function cannot be a true Boolean, so the query, !
[:SENSe]:ADC:DITHer? returns OFF or ON (not 1 or 0 like a true Boolean)
More information
Auto
Sets the ADC dither to automatic. The analyzer then chooses the dither level
according to which is most likely to be the best selection, based on other settings
within the digital IF.
When in Auto, the analyzer sets the dither to Medium whenever the effective IF
Gain is Low by this definition of IF Gain = Low:
– When Sweep Type = Swept, IF Gain = Low whenever Swept IF Gain is set to Low
Gain, whether by autocoupling or manual selection.
– When Sweep Type = FFT, IF Gain = Low whenever FFT IF Gain is set to "Low
Gain," which cannot happen by autocoupling.
Whenever the IF Gain is not low by this definition, Auto sets the dither to Off.
285
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Meas Setup
Medium (Log Accy)
The Medium setting of ADC Dither (known as “On” in earlier versions of the
instrument software) improves the linearity of low-level signals at the expense of
some noise degradation.
SCPI Example ADC:DITH:ON
Off (Best Noise)
When ADC Dither is Off, the instrument noise floor is improved, because without
the need to make room for the dither, you get a lower noise floor and better
sensitivity.
SCPI Example ADC:DITH:OFF
Swept IF Gain
To take full advantage of the RF dynamic range of the analyzer, there is an added
switched IF amplifier with approximately 10 dB of gain. When you can turn it on
without overloading the analyzer, the dynamic range is always better with it on than
off. The Swept IF Gain key can be used to set the IF Gain function to Auto, or to High
Gain (the extra 10 dB), or to Low Gain. These settings affect sensitivity and IF
overloads.
This function is only active when in Swept sweeps. In FFT sweeps, the FFT IF Gain
function is used instead.
Command
[:SENSe]:IF:GAIN:SWEPt[:STATe] OFF|ON|0|1
[:SENSe]:IF:GAIN:SWEPt[:STATe]?
[:SENSe]:IF:GAIN:SWEPt:AUTO[:STATe] OFF|ON|0|1
[:SENSe]:IF:GAIN:SWEPt:AUTO[:STATe]?
Example
IF:GAIN:SWEP ON
IF:GAIN:SWEP:AUTO ON
Preset
Off
ON
Range
Low Gain | High Gain
where ON = high gain
OFF = low gain
State Saved
Saved in instrument state.
Dependencies
The IF Gain control (FFT IF Gain and Swept IF Gain) have no effect when the
U7227A USB Preamplifier is connected. This is not annotated or reflected on any
control. There are no controls grayed out nor any SCPI locked out. The analyzer
simply behaves as though both FFT IF Gain and Swept IF Gain are set to Low
regardless of the setting on the controls.
Couplings
Remote Language Compatibility Measurement Application Reference
286
3 RLC Mode & Swept SA Measurement
Meas Setup
The ‘auto’ rules for Swept IF Gain depend on attenuation, preamp state, start and
stop frequency and the setting of FFT IF Gain. Set the Swept IF Gain to High (On)
when the total input attenuation is 0 dB, the preamp is off, the start frequency is 10
MHz or more, and the FFT IF Gain is autocoupled, or manually set to Autorange, or
manually set to High. Also set the Swept IF Gain to High (On) when the total input
attenuation is 2 dB or less, the preamp is on, the start frequency is 10 MHz or more,
and the stop frequency is 3.6 GHz or less and the FFT IF Gain is autocoupled, or
manually set to Autorange, or manually set to High. Under all other circumstances,
set the Swept IF Gain to Low (Off).
If the sweep type is Swept, the start frequency of the instrument is less than 10
MHz, and you put Swept IF Gain in Manual On, a warning condition is generated
and remains in effect as long as this condition exists. The warning message is about
a possible IF overload.
As with most parameters with an AUTO state, AUTO COUPLE sets it to Auto, and
setting any specific value (for example on or off) will set the AUTO state to false.
Auto
Activates the auto rules for Swept IF Gain.
Low Gain (Best for Large Signals)
Forces Swept IF Gain to be off.
SCPI Example: IF:GAIN:SWEP OFF
High Gain (Best Noise Level)
SCPI Example: IF:GAIN:SWEP ON
Dependencies The High setting for Swept IF Gain is grayed out when FFT IF Gain is
manually set to Low (not when Low is chosen by the auto-rules).
FFT IF Gain
Accesses thecontrols to set the ranging in the digital IF when doing FFT sweeps.
When in Autorange mode, the IF checks its range once for every FFT chunk, to
provide the best signal to noise ratio. You can specify the range for the best FFT
speed, and optimize for noise or for large signals.
When the sweep type is FFT and this function is in Autorange, the IF Gain is set ON
initially for each chunk of data. The data is then acquired. If the IF overloads, then the
IF Gain is set OFF and the data is re-acquired. Because of this operation, the Auto
setting uses more measurement time as the instrument checks/resets its range. You
can get faster measurement speed by forcing the range to either the high or low gain
setting. But you must know that your measurement conditions will not overload the
IF (in the high gain range) and that your signals are well above the noise floor (for the
low gain range), and that the signals are not changing.
AUTO COUPLE sets the state to Auto, which then picks AUTOrange, and setting any
specific value (AUTOrange, LOW or HIGH) will set the AUTO state to false.
Command
287
[:SENSe]:IF:GAIN:FFT[:STATe] AUTOrange|LOW|HIGH
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Meas Setup
[:SENSe]:IF:GAIN:FFT[:STATe]?
[:SENSe]:IF:GAIN:FFT:AUTO[:STATe] OFF|ON|0|1
[:SENSe]:IF:GAIN:FFT:AUTO[:STATe]?
Example
IF:GAIN:FFT ON
IF:GAIN:FFT:AUTO ON
Dependencies
The IF Gain controls (FFT IF Gain and Swept IF Gain) have no effect when the U7227A
USB Preamplifier is connected. This is not annotated or reflected on any control.
There are no controls grayed out nor any SCPI locked out. The analyzer simply
behaves as though both FFT IF Gain and Swept IF Gain are set to Low regardless of
the setting on the keys.
Preset
AUTOrange
ON
State Saved
Saved in instrument state.
Backwards Compatibility
DISPlay:WINDow[1]:TRACe:Y[:SCALe]:LOG:RANGe:AUTO
Included for ESA compatibility
[:SENSe]:ADC:RANGe AUTO|NONE
Included for PSA compatibility. Accepted without error but ignored; the query is
ignored as well.
Auto
Allows the instrument to pick the FFT IF Gain method as appropriate. When in Auto,
the FFT IF Gain is set as follows:
– when the Sweep Type Rules are set to “Best Speed,” the instrument selects
Low Gain as the auto choice
– when the Sweep Type Rules are not “Best Speed,” the instrument selects
Autorange as the auto choice
“Auto” is selected when Auto Couple is pressed.
Autorange (Slower: Follows Signals)
Turns the ADC ranging to automatic which provides the best signal to noise ratio.
Example
: IF:GAIN:FFT AUTOrange
Low Gain (Best for Large Signals)
Forces FFT IF Gain to be off.
Example
IF:GAIN:FFT LOW
High Gain (Best Noise Level)
Forces FFT IF Gain to be on.
Remote Language Compatibility Measurement Application Reference
288
3 RLC Mode & Swept SA Measurement
Meas Setup
Example
: IF:GAIN:FFT HIGH
Noise Floor Extension
Allows you to turn on the Noise Floor Extension function in either of two states, Full
or Adaptive.
– Full NFE: the expected noise power of the analyzer (derived from a factory
calibration) is subtracted from the trace data. This will usually reduce the
apparent noise level by about 10 dB in low band, and 8 dB in high band (>~3.6
GHz).
– Adaptive NFE: there is not the same dramatic visual impact on the noise floor as
there is in Full NFE. Adaptive NFE controls the amount of correction that is
applied based on other analyzer settings like RBW, averaging and sweep time.
Adaptive NFE controls the degree of potential improvement in the noise floor to
give more improvement for those analyzer settings that can make good use of
the potential improvement, such as settings that provide more averaging. The
result is that when not much averaging is being performed, the signal displays
more like the NFE-off case. When lots of averaging is being performed, the signal
displays more like the full-NFE case. Adaptive NFE is recommended for generalpurpose use. For fully ATE (automatic test equipment) applications, where the
distraction of a person using the instrument is not a risk, Full NFE is
recommended.
Noise Floor Extension works with any RBW, VBW, detector, any setting of Average
Type, any amount of trace averaging, and any signal type. It is ineffective when the
trace is not smoothed (smoothing processes include narrow VBWs, trace averaging,
and long sweep times with the detector set to Average or Peak). It works best with
extreme amounts of smoothing, and with the average detector, with the Average
Type set to Power.
In those cases where the cancellation is ineffective, it nonetheless has no
undesirable side-effects. There is no significant speed impact to having Noise Floor
Extension on.
The best accuracy is achieved when substantial smoothing occurs in each point
before trace averaging. Thus, when using the average detector, results are better
with long sweep times and fewer trace averages. When using the sample detector,
the VBW filter should be set narrow with less trace averaging, instead of a wide VBW
filter with more trace averaging.
Noise Floor Extensions has no effect unless the RF Input is selected, therefore it does
nothing when External Mixing is selected.
With the introduction of Adaptive NFE, in firmware version A.18.00, the default state of
NFE is now Adaptive. Before the introduction of Adaptive NFE, NFE was Off by default.
289
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Meas Setup
With the introduction of Adaptive NFE, the menu control is changed from On|Off to
Full|Adaptive|Off. For SCPI Backwards Compatibility, the existing SCPI command to
turn NFE on and off is retained, and a new command is added to set the state to turn
Adaptive On and Off
[:SENSe]:CORRection:NOISe:FLOor ON|OFF|1|0 is retained, default changed to On
[:SENSe]:CORRection:NOISe:FLOor:ADAPtive ON|OFF|1|0 is added, default=On,
Off=Full
See "More Information" on page 290
Command
[:SENSe]:CORRection:NOISe:FLOor ON|OFF|1|0
[:SENSe]:CORRection:NOISe:FLOor?
[:SENSe]:CORRection:NOISe:FLOor:ADAptive ON|OFF|1|0
[:SENSe]:CORRection:NOISe:FLOor:ADAptive?
Example
For NFE:
CORR:NOIS:FLO ON
For Adaptive:
CORR:NOIS:FLO ON ! First turn NFE on
CORR:NOIS:FLO:ADAP ON ! Then set it to Adaptive
Couplings
When NFE is enabled in any mode manually, a prompt will be displayed reminding you to
perform the Characterize Noise Floor operation if it is needed. If NFE is enabled through
SCPI and a Characterize Noise Floor operation is needed, an error will be entered in the
system error queue.
To turn Adaptive on, you must issue the commands in the proper order, as shown in the
example above.
Preset
Unaffected by Mode Preset. Turned ON at startup and by Restore Mode Defaults.
More Information
The analyzer is characterized in the factory (or during a field calibration) with a
model of the noise, referred to the input mixer, versus frequency in each band and
path combination. Bands are 0 (low band) and 1 through 4 (high band) in a 26.5 GHz
instrument, for example. Paths include normal paths, preamp paths, the electronic
attenuator, etc.
In most band/path combinations, the noise can be well characterized based on just
two parameters and the analyzer frequency response before compensation for
frequency-dependent losses.
After the noise density at the input mixer is estimated, the effects of the input
attenuator, RBW, detector, etc. are computed to get the estimated input-portreferred noise level.
In the simplest case, the measured power (signal plus analyzer noise) in each
display point (bucket) is compensated by subtracting the estimated noise power,
leaving just the signal power. This is the operation when the detector is Average
and the Average Type is set to Power.
Remote Language Compatibility Measurement Application Reference
290
3 RLC Mode & Swept SA Measurement
Meas Setup
In other cases, operation is often not quite as good but still highly effective. With
peak detection, the noise floor is estimated based on the RBW and the duration of
the bucket using the same equations used in the noise marker function. The voltage
of the noise is subtracted from the voltage of the observed signal-plus-noise
measurement to compute the estimated signal voltage. The peak detector is one
example of processing that varies with detector to give good estimates of the signal
level without the analyzer noise.
For best operation, the average detector and the power scale are recommended,
as already stated. Peak detection for pulsed-RF can still give excellent
effectiveness. FFT analysis does not work well, and does not do NFE well, with
pulsed-RF signals, so this combination is not recommended. Negative peak
detection is not very useful, either. Sample detection works well, but is never better
than the average detector because it doesn’t smooth as well. The Normal detector
is a combination of peak and negative peak behaviors, and works about as well as
these.
For best operation, extreme smoothing is desirable, as already stated. Using
narrow VBWs works well, but using very long bucket durations and the average
detector works best. Reducing the number of trace points will make the buckets
longer.
For best operation, the power scale (Average Type = Power) is optimum. When
making CW measurements in the presence of noise without NFE, averaging on the
decibel scale has the advantage of reducing the effect of noise. When using NFE,
the NFE does an even better job than using the log scale ever could. Using NFE with
the log scale is not synergistic, though; NFE with the power scale works a little
better than NFE with log averaging type.
The results from NFE with internal preamp can often be lower than the theoretical
noise in a signal source at room temperature, a noise density of -174 dBm/Hz. This
is expected and useful behavior, because NFE is designed to report the amount of
input signal that is in excess of the thermal noise, not the amount that includes the
thermal noise. This can be a useful behavior because thermal noise often interferes
with what you want to measure, instead of being part of what you want to measure.
Note that NFE is not adequately accurate to always be able to read below kTB.
Adaptive NFE provides an alternative to fully-on and -off NFE. Fully-on NFE can,
notably in cases with little or no averaging of the spectrum, result in a display that
is distractingly unfamiliar in the variability in response to low level signals. Fully-off
NFE fails to achieve the potential improvement in dynamic range and associated
accuracy of measurement of low level signals. Adaptive NFE controls the degree of
potential improvement in the noise floor to give more improvement for those
analyzer settings that can make good use of the potential improvement—those
settings with high degrees of variance reduction through some variant of averaging.
When the potential improvement is small, the display acts like the NFE-off case,
and when it is high, it acts like the fully-on case, and in-between, application is a
compromise between atractiveness and effectiveness.
On instruments with the NF2 license installed, the calibrated Noise Floor used by
Noise Floor Extensions should be refreshed periodically. Keysight recommends that
the Characterize Noise Floor operation be performed after the first 500 hours of
291
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Meas Setup
operation, and once every calendar year. The key to perform this is located in the
System, Alignments, Advanced menu. If you have not done this yourself at the
recommended interval, then when you turn on Noise Floor Extensions, the analyzer
will prompt you to do so with a dialog that says:
“This action will take several minutes to perform. Please disconnect all cables from
the RF input and press Enter to proceed. Press ESC to cancel, or Postpone to
postpone for a week.”
If you Cancel, you will be prompted again the next time you turn NFE on. If you
postpone, you will be prompted again after a week passes and you then turn NFE
on.
Noise Source
This control allows you to turn the noise source power on or off and select the type
of Noise Source to be used when making manual noise figure measurements.
If no SNS is connected, this parameter will be set to “Normal”
When Type is set to “SNS” and the SNS is disconnected, this parameter gets
bumped to “Normal”
When an SNS is not connected, the SNS type will be grayed (disabled).
Command
:SOURce:NOISe:TYPE NORMal | SNS
:SOURce:NOISe:TYPE?
:SOURce:NOISe[:STATe] ON|OFF|1|0
:SOURce:NOISe[:STATe]?
Example
SOUR:NOIS:TYPE NORM
SOUR:NOIS OFF
Preset
Normal
OFF
State Saved
Saved in instrument state.
Backwards Compatibility
In previous Noise Figure analysis applications, this command could optionally be
preceded with the :SENSe keyword. The optional :SENSe keyword is no longer
supported.
If an SNS is connected, and the Type is set to SNS, this parameter turns the SNS on
and off.
When an SNS is not connected this parameter turns the BNC 28V output on and
off.
When the SA mode is first entered this parameter is set to OFF and the 28v drive
turned OFF.
Remote Language Compatibility Measurement Application Reference
292
3 RLC Mode & Swept SA Measurement
Meas Setup
When the SA mode is exited this parameter is set to OFF and the 28v drive turned
OFF.
More Information
There are several types of noise sources:
– 346/7 Series
– N4000 series Smart Noise Source (SNS)
– USB Noise Source (connects via USB rather than via the Noise Source
connector on the rear panel)
This menu allows the user to control any of these.
When an SNS is connected the user can then select it from the “Type” dropdown,
allowing the State parameter to then control the SNS. The "Normal" source is
controlled by a BNC connector that supplies 28V. If SNS is NOT connected then the
“state” parameter controls the "Normal" noise source 28V BNC port. If both are
connected the “Type” parameter will determine which source the “State”
parameter will control. Two sources can never be controlled together. The “SNS
attached” SCPI query detailed below can be used remotely to determine if an SNS
is connected. SNS functionality is limited to turning on and off only. The SNS ENR
data and temperature cannot be queried, unless the Noise Figure application is
installed. The SNS ENR data is issued in printed form when an SNS is purchased or
can be read from the analyzer’s Noise Figure application if installed, or other
Keysight noise figure instruments that support the SNS (NFA and ESA with option
219).
Only one SNS is supported at a time. To switch to a different SNS (a USB SNS or an
N4000 series SNS), disconnect the one that is no longer being used prior to
connecting a new one.
When first entering the Swept SA measurement the “State” will be set to OFF and
the 28v BNC drive and SNS turned off to ensure the two are in sync. When the
Swept SA measurement is exited, the “State” parameter will be set to OFF and the
28v BNC and SNS drive turned off.
For making manual noise figure measurements the following setup is
recommended:
– Set the SPAN to Zero
– Set attenuation to 0 dB
– Set the PRE-AMP ON
– Set the RBW to 4 MHz
– Set the Detector to AVERAGE
– Set the sweep time to 16 ms - sets the variance correctly for good results.
293
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Meas Setup
– Set a Band/Interval Power Marker function and set the interval over the full
width of trace i.e. Left to 0s and Right to 16 ms
ACP Enhanced Dynamic Range
The ACP Enhanced Dynamic Range function causes a 300 kHz SAW filter (also
called the “ACP Filter”) to be switched into the signal path to allow third-order
critical measurements, such as ACP measurements, to be made with improved
dynamic range when the spectrum is substantially wider than 300 kHz. When ACP
Enhanced Dynamic Range is on:
1. When RBW ≤ 300 kHz, the “ACP filter” is switched in. This means that the RBW
shape is affected, but not excessively.
2. When RBW > 300 kHz, ACP Enhanced Dynamic Range causes no changes in the
signal path.
Command
[:SENSe]:IF:EDRange ON|OFF|1|0
[:SENSe]:IF:EDRange?
Example
IF:EDR ON
Preset
OFF
State Saved
Saved in instrument state.
Global Tab
Global Center Freq
The software maintains a Mode Global value called “Global Center Freq”.
When the Global Center Freq key is switched to On in any mode, the current mode’s
center frequency is copied into the Global Center Frequency, and from then on all
modes that support global settings use the Global Center Frequency. So you can
switch between any of these modes and the Center Freq will remain unchanged.
Adjusting the Center Freq of any mode which supports Global Settings, while Global
Center Freq is On, will modify the Global Center Frequency.
When Global Center Freq is turned Off, the Center Freq of the current mode is
unchanged, but now the Center Freq of each mode is once again independent.
When Mode Preset is pressed while Global Center Freq is On, the Global Center
Freq is preset to the preset Center Freq of the current mode.
This function is reset to Off when the Restore Defaults key is pressed in the Global
Settings menu, or when System, Restore Defaults, All Modes is pressed.
Remote Language Compatibility Measurement Application Reference
294
3 RLC Mode & Swept SA Measurement
Meas Setup
Command
:INSTrument:COUPle:FREQuency:CENTer ALL|NONE
:INSTrument:COUPle:FREQuency:CENTer?
Example
INST:COUP:FREQ:CENT ALL
INST:COUP:FREQ:CENT?
Preset
Set to Off on Global Settings, Restore Defaults and System, Restore Defaults, All Modes.
Backwards Compatibility
GLOBal:FREQuency:CENTer[:STATe] 1|0|ON|OFF
:GLOBal:FREQuency:CENTer[:STATe]?
Preset: Off
Global EMC Standard
When the Global EMC Std control is switched to On in any mode, the current mode’s
EMC Std is copied into the Global EMC Std, and from then on all modes that support
global settings use the Global EMC Std. You can switch between any of these modes
and the EMC Std will remain unchanged.
Adjusting the EMC Std of any mode that supports Global Settings, while Global EMC
Std is On, will modify the Global EMC Std.
When Global EMC Std is turned Off, the EMC Std of the current mode is unchanged,
but now the EMC Std of each mode is once again independent. When Mode Preset is
pressed while Global EMC Std is On, the Global EMC Std is preset to the preset EMC
Std of the current mode.
This function is reset to Off when the Restore Defaults key is pressed in the Global
Settings menu, or when System, Restore Defaults, All Modes is pressed.
Command
:INSTrument:COUPle:EMC:STANdard ALL|NONE
:INSTrument:COUPle:EMC:STANdard?
Example
INST:COUP:EMC:STAN ALL
INST:COUP:EMC:STAN?
295
Preset
Set to Off on Global Settings, Restore Defaults and System, Restore Defaults, All Modes.
Range
On|Off
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Meas Setup
Restore Defaults
This control resets all of the functions in the Global Settings menu to Off. This also
occurs when System, Restore Defaults, All Modes is pressed.
Command
:INSTrument:COUPle:DEFault
Example
INST:COUP:DEF
Backwards Compatibility
:GLOBal:DEFault
Source Tab
RF Output
Allows you to turn the source RF Power on or off.
Note: as stated below, when the RF Output is turned on, the Source Mode is set to
Tracking. See the Source Mode control description for special considerations
concerning how to configure your N5172B or N5182B source for use with External
Source Control.
Command
:OUTPut[:EXTernal] [:STATe] ON|OFF|1|0
:OUTPut[:EXTernal] [:STATe]?
Example
:OUTP ON
:OUTP?
Dependencies
Grayed out in measurements that do not support a source. If you go to such a
measurement the output will be forced to Off.
Grayed out if there is no valid source selection, in this case go to the Select Source
menu to choose, configure and/or verify your source
When there is no available Source Mode (other than Off), due to other couplings,
then the RF Ouput control is grayed out.
Couplings
When RF Output is turned On, Source Mode is set to Tracking When Source Mode is
turned Off, RF Output is turned Off.
When Source Mode is turned Off (or forced to Off by another coupling), RF Output is
turned Off.
Turning RF Output Off does not affect Source Mode or other settings.
Preset
OFF (on either a Mode Preset, a Source Preset, or Restore Input/Output Defaults)
State Saved
Part of the Input/Output system, which means it is Loaded and Saved with state.
Remote Language Compatibility Measurement Application Reference
296
3 RLC Mode & Swept SA Measurement
Meas Setup
Source Amplitude
Allows you to adjust the power level of the selected source. Note that the actual
amplitude is also affected by the Amplitude Offset and Power Sweep parameters.
Command
:SOURce[:EXTernal]:POWer[:LEVel][:IMMediate][:AMPLitude]
<ampl>
:SOURce[:EXTernal]:POWer[:LEVel][:IMMediate][:AMPLitude]?
Example
:OUTP ON
:SOUR:POW -10dBm
Dependencies
If the requested setting of Source Amplitude causes the calculated external source
start or stop Amplitude to exceed the external source capability, a warning status
message is generated, “Data out of Range; clipped to source max/min” The “Show
Source Capabilities and Settings” menu can then be examined to check the source
capabilities. This parameter test and clip is also performed at source acquisition.
Preset
-10.00 dBm (On Source Preset and Restore Input/Output Defaults)
Not affected by Mode Preset
Min/Max
Min:The range of the amplitude parameter is dependent on the amplitude range of
the source that is selected, and the settings of Amplitude Offset and Power Sweep.
Max:The range of the amplitude parameter is dependent on the amplitude range of
the source that is selected, and the settings of Amplitude Offset and Power Sweep.
State Saved
Part of the Input/Output system, which means it is Loaded and Saved with state.
Backwards Compatibility
:SOURce:POWer:STARt <ampl>
:SOURce:POWer:STARt?
!This alias is for the ESA tracking generator. It specifies the source output power
level at the start of the power sweep, just as does :SOURce:POWer.
Source Mode
This control lets you select Tracking mode or Independent mode for the Source, and
also allows you to set the Source Mode to OFF
The Source Mode can be set to Tracking without the user setting it directly. There
are several couplings that cause Source Mode to be automatically set to Tracking
(detailed in the table below). One important coupling is that Source Mode is forced to
Tracking when the RF Output is turned on if the measurement supports Tracking.
Since Source Mode is set to Off on a Mode Preset, this means that you will rarely
need to change the Source Mode setting directly.
297
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Meas Setup
When the Source Mode is set to Tracking, the analyzer acquires control of the source.
When this happens the source is told to save its state and then perform a preset.
Usually both of these operations take very little time; however, on an N5172B or an
N5182B, if many Source real-time apps are in use, both save and preset can take many
seconds. If it takes longer than the analyzer expects to acquire control, you will see an
error: “Source connection lost, check interface connection”. If you see this error, and you
are using an N5172B or an N5182B, you can shorten the acquire time by presetting your
MXG before attempting to use External Source Control.
Command
:INSTrument:SOURce[:SELect] TRACking|OFF
:INSTrument:SOURce[:SELect]?
Example
:INST:SOUR TRAC
Dependencies
Grayed out if no Source is selected, in this case go to the Select Source menu to
choose, configure and/or verify your source.
Grayed out and forced to Off if either BBIQ or External Mixing are selected.
Grayed out in Measurements that do not support a source.
Tracking is grayed out when the RF Preselector is on (in MXE and other models
which support the RF Preselector).
Couplings
When RF Output is turned On, Source Mode is set to Tracking. When Source Mode
is turned Off, RF Output is turned Off. Whenever you switch to an application (Mode)
in which the Source Mode was previously set to Tracking, it is again set to Tracking.
That is, the last setting of the Source Mode is remembered when you leave an
application (Mode) and restored when you return Source Mode is forced to Tracking
when the RF Output is turned on if the measurement supports Tracking If Source
Mode is set to Tracking, then it is forced to Off when you select a measurement that
does not support Tracking. If Source Mode is set to Tracking, then it is forced to Off
when you turn on the RF Preselector (in models which support the RF Preselector).
Whenever the Source Mode is set to Tracking, the analyzer acquires the Source.
Similarly, the Source is released whenever the Source Mode is set to Off. This is true
whether the Source Mode was set directly by you, was set indirectly through a
coupling, if you switched to an application (Mode) that had previously been set to
Tracking, or if you switched to an application (Mode) in which the Source Mode is
not set to Tracking. For an external source, “acquiring the source” involves
contacting the external instrument over the remote interface (which puts it into
Remote) and taking control of it.
When you set the Source Mode to OFF, it releases the Source (and puts it into
Local). For an external source, this means you are now free to operate the source for
other purposes.
When the Source is acquired, its previous state is saved, and when it is released,
that state is restored, so that you can acquire and then release the source and it will
return to the state it was in before you acquired it.
Preset
OFF
State Saved
Saved in instrument state.
Remote Language Compatibility Measurement Application Reference
298
3 RLC Mode & Swept SA Measurement
Meas Setup
Source Setup Table
This dialog allows you to access various setup parameters for the Source. In
addition, the results of the source control sweep algorithms can be viewed. This
gives information of the source range required for a given analyzer sweep range. This
can be used dynamically as a way of configuring the sweep settings.
Point Trigger: Lets you set up how you want to trigger the source as it steps from
frequency to frequency. For more on triggering in Tracking Mode, see Tracking Setup
Details.
Amplitude parameters: Power Sweep, Amlitude Offset, Amlitude Step. The
resolution of the Source amplitude parameters is coupled to match the minimum
resolution of the source when the source is acquired. When the source is released,
the amplitude parameter resolution reverts to default values.
Frequency parameters: Multiplier (Numerator and Denominator), Reverse Sweep,
Freq Offset. These controls give you added flexibility when using a stepped tracking
source for stimulus/response measurements.
– Because with a stepped source, the source frequency does not need to track 1:1
with the analyzer LO frequency, it is possible to measure scalar harmonic and
subharmonic responses of devices. For example, the second harmonic response
is measured by stepping the analyzer and source so that the analyzer is always
at twice the source frequency.
– In addition, the frequency offset capability allows the measurement of frequency
conversion devices (like mixers).
– In tracking mode, the source frequency tracks the analyzer frequency according
to the source frequency equation:
Source Frequency = (Analyzer Frequency *Multiplier Numerator / Multiplier
Denominator) + Source Frequency Offset
In the above equation, Analyzer Frequency is the frequency to which the analyzer is set,
which is the analyzer’s displayed frequency, offset by any Freq Offset set under the
Frequency hardkey. Source Frequency Offset is the value set under Source, Frequency,
Freq Offset.
For some Stimulus/Response measurements you may wish to bypass the
Microwave Preselector. For information on bypassing the Microwave Preselector,
see Use of the YTF (Microwave or mm Preselector) with External Source Control.
Use of the YTF (Microwave or mm Preselector) with External Source Control
In most stimulus/response measurements that utilize External Source Control, the
source exactly tracks the tuned analyzer frequency. Consequently, preselection is
not needed, and you can achieve greatly superior amplitude accuracy and
repeatability by bypassing the YTF (Preselector) using the Microwave Preselector
Bypass control in the Amplitude, uW Path Control menu (note: this control is only
available if option MPB is installed) .
299
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Meas Setup
Point Trigger
Shows point trigger type selected and navigates to the Point Trigger menu.
The Point Trigger menu lists all analyzer point trigger types. The analyzer and
source point trigger synchronization can be done using SCPI bus commands or by
using external trigger output and input lines.
For X-Series software versions earlier than A.10.01, hardware triggering was
unavailable in stepped tracking at frequencies above 3.6 GHz, so above 3.6 GHz,
software triggering was always used. This is no longer the case.
Command
:SOURce:TRIGger:TYPE BUS|EXTernal[1]|EXTernal2
:SOURce:TRIGger:TYPE?
Example
:SOUR:TRIG:TYPE EXT1
Selects analyzer external trigger 1 in and out for point trigger synchronization with
selected source.
Dependencies
If an internal Tracking Generator is selected, then this menu is unavailable.
Additionally, the External 1 and External 2 Trigger keys on the Spectrum Analyzer are
released from any grayout that may have been forced on them by the external source
Point Trigger selection. In some models, there is no second External input. In these
models, the External 2 selection does not appear and the EXTernal2 parameter will
generate a “Hardware missing; Not available for this model number” message.
Couplings
The source control point trigger selection can select external trigger 1 or 2 in for
synchronized point triggering. This can conflict with the selection under the Trigger
hardkey, if it has External 1 or 2 selected. If there is a conflict when the selection is
made under the Point Trigger menu, the Trigger selection under the Trigger hardkey
will be changed to Free Run.
Preset
This is unaffected by “Mode Preset” but is set to EXTernal1 on a “Source Preset” or
"Restore Input/Output Defaults".
State Saved
Part of the Input/Output system, which means it is Loaded and Saved with state
Tracking Setup Details
When an external source is operating in Tracking Mode, operation can be greatly
enhanced by using hardware triggers Below is a typical connection diagram
showing a hardware handshake using Trigger 1 inputs and outputs on the analyzer
(trigger 2 in and out is also a valid connection).
Remote Language Compatibility Measurement Application Reference
300
3 RLC Mode & Swept SA Measurement
Meas Setup
Analyzer Trigger 1 Out: Triggers the external source to step to next point in the
frequency step/list.
Analyzer Trigger 1 In: Triggers the analyzer to make a measurement on this point
Source Trigger In (or “Trig 1” at default setting for N5181B/82B, N5183B MXG or
N5171B/72B, N5173B EXG):
Triggers the source to step to the next point.
Source Trigger Out (or “Trig 2” at default setting for N5181B/82B, N5183B MXG or
N5171B/72B, N5173B EXG): Indicates that the source has settled.
IO interface Connection: analyzer can connect to sources with its GPIB, USB or LAN
interface.
Notes:
– Trigger sync connections are optional – synchronization can be done via remote
commands if Bus Trigger is enabled in the Source Setup menu.
– Connection from the SA external frequency reference output to the source
frequency reference input (10 MHz Out to Ref In) is not required, but may
improve the measurement accuracy.
SW Trigger
Analyzer and source point trigger synchronization is setup using the SCPI
commands. Source is stepped via SCPI commands. Analyzer waits for source to
settle by polling source.
SCPI example: :SOUR:TRIG:TYPE BUS
Ext Trigger 1
301
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Meas Setup
SCPI example: :SOUR:TRIG:TYPE EXT1
Analyzer and source point trigger synchronization is setup using the analyzer
Trigger 1 Output and Trigger 1 Input. The Source is stepped via Trigger 1 Output.
The Analyzer waits for source to settle via Trigger 1 Input.
With an acquired source, selecting this point trigger mode overrides existing
external trigger 1 output level, slope, and delay, and external trigger 1 type and
polarity.
External trigger 1 input level = 1.20 V
External trigger 1 input slope = Positive
External trigger 1 input delay = Off
External trigger 1 output type = Source Point Trigger
External trigger 1 output polarity = Positive
When this selection is made:
– The External 1 selection in the Trigger menu (under the Trigger hardkey) does
not appear and, if External 1 was previously selected, it will be changed to Free
Run.
– Trig 1 Out selected under Output Config in the Input/Output menu will be
changed to Source Point Trigger
If the user subsequently goes into the Trig 1 Out menu and selects a different
Trigger Output, the Point Trigger will revert to SW Trigger.
Ext Trigger 2
Analyzer and source point trigger synchronization is setup using the analyzer
Trigger 2 Output and Trigger 2 Input. The Source is stepped via Trigger 2 Output.
The Analyzer waits for source to settle via Trigger 2 Input.
SCPI example: :SOUR:TRIG:TYPE EXT2
With an acquired source, selecting this point trigger mode overrides existing
external trigger 2 output level, slope, and delay, and external trigger 2 type and
polarity.
External trigger 2 input level = 1.20 V
External trigger 2 input slope = Positive
External trigger 2 input delay = Off
External trigger 2 output type = Source Point Trigger
External trigger 2 output polarity = Positive
When this selection is made:
Remote Language Compatibility Measurement Application Reference
302
3 RLC Mode & Swept SA Measurement
Meas Setup
– The External 2 selection in the Trigger menu (under the Trigger hardkey) does
not appear and, if External 2 was previously selected, it will be changed to Free
Run.
– Trig 2 Out selected under Output Config in the Input/Output menu will be
changed to Source Point Trigger
If the user subsequently goes into the Trig 2 Out menu and selects a different
Trigger Output, the Point Trigger will revert to SW Trigger.
Power Sweep
Allows you to set up a Power Sweep. Power Sweep is useful for measuring
saturation behavior in a test device, such as a power amplifier.
The source will sweep the power between the start power defined by the Amplitude
function and the stop power = start power + power sweep value:
Source (start) amplitude = Amplitude – Amplitude Offset
Source (stop) amplitude = Amplitude – Amplitude Offset + Power Sweep
In Stepped Tracking, such as is used with an external source{Future} or the CXA-m
TG {/Future}, the analyzer controls the source with step sweep mode, which
provides a linear progression from one selected frequency, amplitude, or both, to
another, pausing at linearly spaced points (steps) along the sweep. The analyzer
continues to sweep the specified frequency range when power sweep is on,
although generally Power Sweep is performed in Zero Span.
With CXA options T03, T06 and SCT, the hardware is capable of continuous power
sweeps. This makes it possible to use the swept sweep time rules and should be
employed for faster sweeps. Care should be taken to limit the sweep time you use as
there are no sweep time couplings to Power Sweep settings. The recommended
minimum sweep time depends on the RBW and power-sweep range. Start by
computing (1.28/RBW)* (abs(startPower – stopPower)/(5 dB)). The recommended
minimum sweep time is the larger of this value and 50 ms.
Some external Sources have mechanical attenuators, which are not used in Power
Sweep in order to save wear on the attenuators. To allow an acceptable range of
Power Sweep without changing the mechanical attenuation, the Sources are put in a
mode that allows the Source to handle a wide amplitude range without switching
the attenuators. When the Power Sweep settings put the Source in an amplitude
range that requires the mechanical attenuators, the analyzer displays a condition
warning message:
Settings Alert;Src pwr ramp>ALC range
Command
:SOURce:POWer:SWEep <rel_ampl>
:SOURce:POWer:SWEep?
:SOURce:POWer:SWEep:STATe ON|OFF|1|0
303
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Meas Setup
:SOURce:POWer:SWEep:STATe?
Example
:SOUR:POW -5
:SOUR:POW:SWE:STAT ON
:SOUR:POW:SWE 10
Set source start power to – 5 dBm and stop power + 5dBm (-5 + 10).
:SOUR:POW:SWE:STAT ON
Dependencies
If the requested setting of Power Sweep causes the calculated external source start
or stop Amplitude to exceed the external source capability, a warning status
message is generated, -222.2001 “Data out of Range; clipped to source max/min”.
The Show Source Capabilities and Settings menu can then be examined to check the
source capabilities. This parameter test and clip is also performed at source
acquisition.
Preset
This is unaffected by “Mode Preset” but is set to 0dB on a “Source Preset” or
"Restore Input/Output Defaults".
Min/Max
-500 dB/+500 dB
State Saved
Part of the Input/Output system, which means it is Loaded and Saved with state.
Backwards Compatibility
This alias is for the ESA tracking generator and PSA option 215. It specifies the
range of power levels through which the source output will sweep just as does
:SOURce:POWer:SWEep.
:SOURce[:EXTernal][:SWEep]:POWer:SPAN <rel_ampl>
:SOURce[:EXTernal][:SWEep]:POWer:SPAN?
:SOURce[:EXTernal]:POWer:MODE FIXed|SWEep
:SOURce[:EXTernal]:POWer:MODE?
The ESA tracking generator and the PSA option 215 support this SCPI command. It
sets the source output to be at a single amplitude (fixed) or to sweep through a
range of power levels
SOURce:POWer:MODE FIXed
is equivalent to :SOURce:POWer:SWEep:STATe OFF
SOURce:POWer:MODE SWEep
is equivalent to :SOURce:POWer:SWEep:STATe ON
Amptd Offset
Offsets the displayed power of the source in the Amplitude parameter. Using the
amplitude offset allows you to take into account any system losses or gains (for
example, due to cable loss), thereby displaying the actual power delivered to the
Remote Language Compatibility Measurement Application Reference
304
3 RLC Mode & Swept SA Measurement
Meas Setup
device under test. See the equations under the Source, Amplitude, Power Sweep
key.
Command
:SOURce:CORRection:OFFSet <rel_ampl>
:SOURce:CORRection:OFFSet?
Example
:SOUR:CORR:OFFS 5
Dependencies
If the requested setting of Amptd Offset causes the calculated external source start
or stop Amplitude to exceed the external source capability, a warning status
message is generated, -222.2001 “Data out of Range; clipped to source max/min”.
The Show Source Capabilities and Settings menu can then be examined to check the
source capabilities. This parameter test and clip is also performed at source
acquisition.
Preset
This is unaffected by Mode Preset but is set to 0.00dBm on a Source Preset or
Restore Input/Output Defaults.
Min/Max
-1000 dB/+1000 dB
State Saved
Part of the Input/Output system, which means it is Loaded and Saved with state.
Amptd Step
Allows you to set the step size associated with the Source Amplitude key. When
auto-coupled, the step size is the current Scale/Div setting under the Amplitude
hardkey (note that this is true even if the analyzer is currently in Linear amplitude
scale).
Once a step size has been selected and the Source Amplitude function is active, the
step keys (and the UP|DOWN parameters for Source Amplitude from remote
commands) change the Source Amplitude by the step-size value.
You may change the step size manually by pressing Amptd Step and entering a
value. The function (and the step size) will return to Auto when a Mode Preset or
Auto Couple is performed.
Command
:SOURce:POWer:STEP[:INCRement] <ampl>
:SOURce:POWer:STEP[:INCRement]?
:SOURce:POWer:STEP:AUTO OFF|ON|0|1
:SOURce:POWer:STEP:AUTO?
Example
:SOUR:POW:STEP 0.1
:SOUR:POW:STEP:AUTO ON
Couplings
In Auto, coupled to the size of one logarithmic vertical graticule division.
Preset
10 dB
Auto
305
Min/Max
0.1 dB/20 dB
State Saved
Part of the Input/Output system, which means it is Loaded and Saved with state.
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Meas Setup
Multiplier Numerator
The multiplier numerator parameter offsets the source frequency from the analyzer
frequency. The source frequency tracks the SA frequency according to the source
frequency equation shown at the bottom of the Source Setup Table.
The multiplier numerator must be restricted to operate within the range of the
source minimum and maximum frequencies.
Command
:SOURce:FREQuency[:MULTiplier]:NUMerator <integer>
:SOURce:FREQuency[:MULTiplier]:NUMerator?
Example
:SOUR:FREQ:NUM 3
Dependencies
If the currently selected source does not support this capability (for example, an
internal Tracking Generator which must track the LO), this control is forced to its
Preset value and grayed out
Preset
This is unaffected by Mode Preset but is set to 1 on a Source Preset or Restore
Input/Output Defaults.
Min/Max
1/1000
State Saved
Part of the Input/Output system, which means it is Loaded and Saved with state.
Multiplier Denominator
The multiplier denominator parameter offsets the source frequency from the
analyzer frequency. The source frequency tracks the SA frequency according to the
source frequency equation shown at the bottom of the Source Setup Table.
The multiplier denominator must be restricted to operate within the range of the
source minimum and maximum frequencies.
Command
:SOURce:FREQuency[:MULTiplier]:DENominator <integer>
:SOURce:FREQuency[:MULTiplier]:DENominator?
Example
:SOUR:FREQ:DEN 3
Dependencies
If the currently selected source does not support this capability (for example, an
internal Tracking Generator which must track the LO), this control is forced to its
Preset value and grayed out.
Couplings
Preset
This is unaffected by Mode Preset but is set to 1 on a Source Preset or Restore
Input/Output Defaults.
Min/Max
1/1000
State Saved
Part of the Input/Output system, which means it is Loaded and Saved with state
Source Sweep Reverse
Allows you to reverse the source sweep direction
Remote Language Compatibility Measurement Application Reference
306
3 RLC Mode & Swept SA Measurement
Meas Setup
Normally, the source will sweep from a lower frequency to a higher frequency.
However, there are test scenarios in which the source sweep needs to be
“reversed”. In this case, it sweeps from a higher frequency to a lower frequency. For
example, when the DUT is a frequency converter and a measurement of the Lower
Side Band characteristics is desired, a reverse sweep is employed. Reverse sweeps
are supported for such scenarios, but two cautions are in order:
1. Reverse Sweep only reverses the direction of the source’s sweep, not the
analyzer’s sweep. Unless you are actually using a device like a frequency
converter and looking at the lower sideband, thus effectively reversing the
direction of the source’s sweep, the source will be sweeping in the opposite
direction from the analyzer, and it will not be possible track the desired device
output frequency.
2. Any time you are using a frequency converter, care must be taken in setting up all
of the sweep parameters, including analyzer start/stop frequency and source
multiplier, to make sure that the analyzer’s sweep tracks the output of the
converter device.
You must be in Spectrum Analyzer mode to use this command. Use
INSTrument:SELect to set the mode.
Command
:SOURce:FREQuency:SSReverse:ON|OFF|0|1
:SOURce:FREQuency:SSReverse?
Example
SOUR:FREQ:SSR:OFF
SOUR:FREQ:SSR?
Dependencies
If the currently selected source does not support this capability (for example, an
internal Tracking Generator which must track the LO), this control is forced to its
Preset value and grayed out.
Preset
This is unaffected by Mode Preset but is set to OFF on a Source Preset or Restore
Input/Output Defaults.
State Saved
Part of the Input/Output system, which means it is Loaded and Saved with state
Freq Offset
The frequency offset parameter offsets the source frequency from the analyzer
frequency. The source frequency tracks the SA frequency according to the equations
at the bottom of the Source Setup Table.
The frequency offset must be restricted to operate within the range of the source
minimum and maximum frequencies.
Command
:SOURce:FREQuency:OFFSet <freq>
:SOURce:FREQuency:OFFSet?
:SOURce:FREQuency:OFFSet:STATe ON|OFF|1|0
:SOURce:FREQuency:OFFSet:STATe?
307
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Meas Setup
Example
:SOUR:FREQ:OFFS 10MHz
Dependencies
If the currently selected source does not support this capability (for example, an
internal Tracking Generator which must track the LO), this control is forced to its
Preset value and grayed out.
Preset
This is unaffected by Mode Preset but is set to 0.00Hz on a Source Preset or Restore
Input/Output Defaults.
Min/Max
-500 GHz/500 GHz
State Saved
Part of the Input/Output system, which means it is loaded and saved with state.
Backwards Compatibility
The PSA option 215 supports this SCPI command. This command is equivalent to :
SOURce:FREQuency:OFFSet
:SOURce:EXTernal:SWEep:OFFSet:FREQuency <freq>
:SOURce:EXTernal:SWEep:OFFSet:FREQuency?
The PSA option 215 supports this SCPI command. This command is equivalent to :
SOURce:FREQuency:OFFSet:STATe
:SOURce:EXTernal:SWEep:OFFSet:STATe ON|OFF|1|0
:SOURce:EXTernal:SWEep:OFFSet:STATe?
Select Source
The Select Source dialog allows you to maintain a list of available external and
internal Sources, and choose the Source that you want to use from the list. The
controls for adding sources to the list are shown at the top of the screen, the list of
available sources in the middle of the screen, and the currently selected source at
the bottom of the screen.
The sources in the Available Source List are as follows:
– Any internal sources which are installed and licensed
Only one internal source can be installed, displayed at address “INTERNAL”
– Any external sources which you have previously configured, whether or not they
are currently connected, displayed with their VISA address
The list of available sources includes any sources that you have previously used
(unless you have deleted them) and any found usong the “Add Source to List”
controls.
Double-tap the source you want to use, or use the up and down arrows to move to
the source that you want and press Select Highlighted Source” or “Enter”. The
source you have selected shows up at the bottom of the screen as the “Selected
Remote Language Compatibility Measurement Application Reference
308
3 RLC Mode & Swept SA Measurement
Meas Setup
Source”. Press “Verify Connection” to make sure that the interface connection to the
Source is functional.
At any time you may use the “Add Source to List” controls to find new sources or
“Delete Highlighted Source” to remove a source from the list of available sources.
Note that only external sources that are supported by the Tracking Source Mode are
displayed in the Available Source List. Here are the Sources currently supported:
Source UXA
PXA
MXA
EXA
CXA
MXG N5181A
X
X
X
X
X
MXG N5182A
X
X
X
X
X
MXG N5183A
X
X
X
X
EXG N5171B
X
X
X
X
X
MXG N5181B
X
X
X
X
X
EXG N5172B
X
X
X
X
X
EXG N5173B
X
X
X
X
X
MXG N5182B
X
X
X
X
X
MXG N5183B
X
X
X
X
X
PSG E8257D
X
X
X
X
PSG E8267D
X
X
X
X
Add Installed USB Source
Sources on USB (once installed) can be added to the list by pressing “Add Installed
USB Sources.” Any supported source found will be added to the list.
309
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Meas Setup
Press this control to add USB sources to the Available Source List. Note that this
function will ONLY find sources that have previously been installed onto the USB. For
information on how to install a USB source, see Installing a USB source.
Installing a USB source
USB is the only interface which requires no runtime action by the user in the Select
Source menu, but does require “installation” when a source is plugged in.
You start by connecting the USB source to the analyzer. You will get a series of
messages indicating that the analyzer is installing required device software.
When the installation is complete, you will get a message to that effect. You can
then use the “Add Installed USB Sources” function (above) to add the source to the
list of sources in the Available Source List.
GPIB Address
Lets you enter the GPIB address of a GPIB source. After you enter the address press
Add Specified GPIB Address to add the source at that address to the Available
Source List.
For the GPIB interface to work properly when controlling a Source, it must be configured
as a Controller. You can find this setting in the System menu under System, I/O Config,
GPIB. Set the GPIB Controller function to Enabled.
Preset
Unaffected by Mode Preset but set to 19 by “Restore Input/Output defaults”
Min/Max
0/30
Add Specified GPIB Address
Add the source at the entered GPIB address to the Available Source List. If a
supported source is found at that address it will be added to the list.
If GPIB controller mode is not enabled, an error message is generated.
If no supported source is found at the specified address, an error message is
generated.
Scan & Add GPIB Source
Sources on GPIB can be added by pressing Scan & Add GPIB Source. Any supported
source found will be added to the Available Source List.
This will cause any older, non-SCPI compatible devices on your GPIB to generate error
messages.
If the GPIB controller mode is not enabled, an error message is generated.
Remote Language Compatibility Measurement Application Reference
310
3 RLC Mode & Swept SA Measurement
Meas Setup
If no GPIB device is found which is a supported source, an error message is
generated.
IP Address
Lets you enter the IP address of a source om the LAN. After you enter the address
you should press “Add” to add the source at that address to the Available Source
List.
Unaffected by Mode Preset but set to 0.0.0.0 by Restore Input/Output defaults.
Add Specified IP Address
Adds the source at the entered IP address to the Available Source List. If a
supported source is found at that address it will be added to the list.
If no supported source is found at the specified address, an error message is
generated.
Run Connection Expert
The LAN cannot be scanned directly from the analyzer software, but if you want to
discover sources on the LAN, you can open Keysight Connection Expert by pressing
the “Run Connection Expert…” control. You can import the list of currently configured
devices from Keysight Connection Expert by pressing “Add From Connection Expert”.
The Connection Expert list depends on which instruments have been discovered by
the Keysight Connection Expert application. Any connected, supported sources in
that list will be added.
Add From Connection Expert
You can import the list of currently configured devices from Keysight Connection
Expert by pressing Add From Connection Expert. The Connection Expert list depends
on which instruments have already been discovered by the Keysight Connection
Expert application. Any connected, supported sources in that list will be added.
If no supported source is found in the Connection Expert list, an error message is
generated.
Select Highlighted Source
You can navigate up and down in the list with the up and down arrow keys, and can
select any entry by pressing the Select Highlighted Source control (or by doubletapping on the entry in the table). The highlighted source becomes the Current
Source and is prominently displayed at the bottom of the screen.
311
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Meas Setup
At any given time there is only one selected Source for the entire system; once a
Source is selected, it becomes the Current Source and will be used by all
applications that support Source Control.
For example, if no Source has yet been selected, the statement at the bottom of the
screen would say
Selected Source
None
If an N5182A connected via USB were the Current Source, the statement at the
bottom of the screen might say:
Selected Source
Keysight N5182A US00000258 at
USB0::2931::7937::US00000258::0::INSTR
The SCPI command defined below allows the programmatic user to directly define
the VISA address via a string parameter. The parameter is checked for proper
syntax, the connection to the instrument is verified, and the source is added to the
Available Source List if it verifies. If it does not verify or no source is found at that
address, an error message is generated.
Normally the source selection activities should be performed only when the user
changes the hardware connection configuration or activates/deactivates a source
option license; shutdown and startup of the application will not cause source reselection.
The Keysight IO Libraries Suite provides an “Keysight VISA Help” document that has
a section that shows the proper syntax for valid VISA address strings, in the ViOpen
function definition.
Command
:SYSTem:COMMunicate:SOURce[1]:ADDRess <address string>
:SYSTem:COMMunicate:SOURce[1]:ADDRess?
Example
:SYST:COMM:SOUR:ADDR “TCPIP0::MyHostName::INSTR”
:SYST:COMM:SOUR:ADDR “TCPIP0::123.121.100.210::INSTR”
:SYST:COMM:SOUR:ADDR “USB0::12212::32145::US1234567A::INSTR”
:SYST:COMM:SOUR:ADDR “GPIB1::19::INSTR”
Dependencies
Operation with a source requires a license. If the proper license is not installed, the
SCPI command generates an error message, “Settings conflict;option not installed”
If no supported source, or no source at all, is found at the specified address, the SCPI
command generates an error message
Notes
Empty string is allowed and means no source is defined or selected.
Preset
The current source selection is unaffected by a Mode Preset and Source Preset but
reverts to [None] on a Restore Input/Output Defaults.
If an internal Tracking Generator is installed, then instead of None, the default
selection will be INTERNAL.
State Saved
Selected Source is
Remote Language Compatibility Measurement Application Reference
312
3 RLC Mode & Swept SA Measurement
Meas Setup
– Power On Persistent (survives power cycle)
– Part of the Input/Output system, which means it is Loaded and Saved with state.
Backwards Compatibility
:SYSTem:COMMunicate:LAN:SOURce[:EXTernal]:IP <address string>
:SYSTem:COMMunicate:LAN:SOURce[:EXTernal]:IP?
This command is provided for compatibility with PSA Option 215. The address string
is reformatted for the X-Series. For example, if the customer sends
:SYSTem:COMMunicate:LAN:SOURce:EXTernal:IP 146.208.172.111
The analyzer turns this into
:SYSTem:COMMunicate:SOURce:ADDRess “TCPIP0::146.208.172.111::INSTR"
Delete Highlighted Source
Deletes the highlighted source from the list of available sources. You will be
prompted with a dialog box to make sure you REALLY want to do this. The prompt
says “The highlighted source will be permanently deleted from the list. Are you sure
you want to do this? Press Enter to proceed, or Cancel (ESC) to cancel.”
Verify Connection
This control verifies the interface connection to the Current Source (it does NOT
verify any signal connections!)
Until the selected source is verified, a statement appears at the bottom of the screen
which says (in red):
This Source has not been verified. Press “Verify Source” to check
the interface connection.
When you press this key, the connection is checked to the selected source. If all is
well, the statement is changed to (in green):
This connection to this source has been verified.
If the verification fails, the statement at the bottom will change to (in red):
Verification of this source failed. Check the interface connection
The selected source is also verified whenever it is acquired. If a Source’s connection
has been verified by any means, then that Source is considered to have been verified
until either the analyzer software is shut down or if, in attempting to use the Source,
communication with it fails.
313
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Meas Setup
Show Source
Shows the capabilities of the currently selected Source. The menu is useful for
displaying source capabilities such as frequency and amplitude ranges.
If no source is selected this control is grayed out.
Show Source Graphic
Source Preset
The Source Preset control forces all the settings in the analyzer’s Source State to
their preset condition.
The Source State is the set of Source settings that is maintained and remembered
by the analyzer for use in the Tracking Source Mode. The Source State variables are
controlled and set in the menus under the Source front panel key. These settings
include:
– RF Output Off
– Amplitude = - 10 dBm
– Amplitude Step = Auto
– Power Sweep = 0 dB
– Amplitude Offset = 0 dB
Remote Language Compatibility Measurement Application Reference
314
3 RLC Mode & Swept SA Measurement
Meas Setup
– Source Sweep Reverse = Off
– Multiplier Numerator = 1
– Multiplier Denominator = 1
– Freq Offset = 0 Hz
– Point trigger is set to "Ext1"
The Source State is saved along with the state of the current Mode when you save a
State, and is recalled when that Mode State is recalled.
When the analyzer first starts up, a Source Preset is performed. In the Input/Output
menu, Restore Input/Output Defaults will also perform a Source Preset.
A Mode Preset, from modes that support the External Source, will turn the RF Off but
will NOT perform a Source Preset. By the same token, Source Preset does NOT
perform a Mode Preset.
Source Preset does not change the Source Mode nor the selection of which physical
source is being used, nor does it release the current source (the source remains
under the control of the analyzer) nor exit the Source menu.
315
Command
:SOURce:PRESet
Example
:SOUR:PRES
Preset
Initiates a Source Preset
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Sweep
Sweep
The Sweep front-panel key opens the sweep menu, which contains controls for the
Sweep Control and Sweep Configuration functions of the instrument.
Sweep Control Tab
Sweep Time
Controls the time the analyzer takes to sweep the current frequency span when the
Sweep Type is Swept, and displays the equivalent Sweep Time when the Sweep
Type is FFT.
When Sweep Time is in Auto, the analyzer computes a time that will give accurate
measurements based on other settings of the analyzer, such as RBW and VBW.
You can choose a shorter sweep time to improve the measurement throughput (with
some potential unspecified accuracy reduction), but the Meas Uncal indicator will
come on if the sweep time you set is less than the calculated Auto Sweep time. You
can also select a longer sweep time, which can be useful (for example) for obtaining
accurate insertion loss measurements on very narrowband filters. The number of
measurement points can also be reduced to speed the measurement (at the
expense of frequency resolution).
Because there is no “Auto Sweep Time” when in zero span, the Auto/Man toggle on
this control disappears when in Zero Span.
When Sweep Type is FFT, you cannot control the sweep time, it is simply reported by
the analyzer to give you an idea of how long the measurement is taking. The
Auto/Man toggle therefore disappears when in an FFT sweep. In this case the
sweep time function is grayed out.
Note that although some overhead time is required by the analyzer to complete a
sweep cycle, the sweep time reported when Sweep Type is Swept does not include
the overhead time, just the time to sweep the LO over the current Span. When
Sweep Type is FFT, however, the reported Sweep Time takes into account both the
data acquisition time and the processing time, in order to report an equivalent
Sweep Time for a meaningful comparison to the Swept case.
Significantly faster sweep times are available for the Swept SA measurement with
Option FS1.
Remote Language Compatibility Measurement Application Reference
316
3 RLC Mode & Swept SA Measurement
Sweep
The Meas Uncal (measurement uncalibrated) warning is given in the Status Bar at the
bottom of the screen when the manual Sweep time entered is faster than the time
computed by the analyzer’s Sweep time equations, that is, the Auto Sweep Time. The
analyzer’s computed Sweep time will give accurate measurements; if you sweep faster
than this your measurements may be inaccurate. A Meas Uncal condition may be
corrected by returning the Sweep Time to Auto; by entering a longer Sweep Time; or by
choosing a wider RBW and/or VBW.
On occasion other factors such as the Tracking Generator’s maximum sweep rate, the
YTF sweep rate (in high band) or the LO’s capability (in low band) can cause a Meas
Uncal condition. The most reliable way to correct it is to return the Sweep Time to Auto.
If the analyzer calculates that the Auto Sweep Time would be greater than 4000s (which
is beyond its range), the warning message “Settings Alert;Sweep Rate Unavailable” is
displayed. In this case increase the RBW or reduce the span.
If the analyzer’s estimated sweep time in an FFT sweep is greater than 4000s, the
warning message “Settings Alert;Span:RBW Ratio too big” is displayed. In this case
reduce the span or increase the RBW and/or FFT Width.the RBW or reduce the span.
Command
[:SENSe]:SWEep:TIME <time>
[:SENSe]:SWEep:TIME?
[:SENSe]:SWEep:TIME:AUTO OFF|ON|0|1
[:SENSe]:SWEep:TIME:AUTO?
Example
SWE:TIME 500 ms
SWE:TIME:AUTO OFF
Preset
The preset SweepTime value is hardware dependent since Sweep Time presets to
“Auto”
ON
Min/Max
Min:In swept spans: 1 ms, In zero span: 1 μs
Max:In swept spans: 4000 s, In zero span: 6000 s
State
Saved
Saved in instrument state.
Notes
The values shown in this table reflect the “swept spans” conditions, which are the
default settings after a preset. See “Couplings” for values in the zero span domain.
Dependencies
Sweep Time is blanked in Modes that do not support swept mode.
Sweep Time is grayed out in Measurements that do not support swept mode.
Set to Auto when Auto Couple is pressed or sent remotely.
317
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Sweep
The SCPI command :SWEep:TIME:AUTO ON if sent in FFT sweeps generates an
error.
Sweep Time is grayed out while in Gate View, to avoid confusing those who want to
set GATE VIEW Sweep Time.
The Auto/Man toggle disappears in Zero Span. The SCPI command
SWEep:TIME:AUTO ON if sent in Zero Span it generates an error message.
The Auto/Man toggle disappears in Zero Span and the Sweep Time control is
grayed out. Pressing the key or sending the SCPI for sweep time while the
instrument is in FFT sweep generates a -221, “Settings Conflict;” error.
Couplings
Sweep time is coupled to RBW when in a non-zero span. If Sweep Time is set to
Auto, then the sweep time is changed as the RBW changes, to maintain amplitude
calibration.
Sweep Time is also coupled to the Video Bandwidth (VBW). As the VBW is
changed, the sweep time (when set to Auto) is changed to maintain amplitude
calibration. This occurs because of common hardware between the two circuits.
Although the VBW filter is not “in-circuit” when using the average detector and the
EMI detectors, the Video BW control can have an effect on (Auto) sweep time in
these cases, and is not disabled. Because the purpose of the average detector and
the VBW filter are the same, either can be used to reduce the variance of the result.
In this case, reducing the VBW setting increases the sweep time, which increases
the averaging time, producing a lower-variance trace.
Span, Center Frequency, and the number of sweep points also can have an effect.
So changing these parameters may change the Sweep Time.
The Sweep Time used upon entry to Zero Span is the same as the Sweep Time that
was in effect before entering Zero Span. The Sweep Time can be changed while in
Zero Span. Upon leaving Zero Span, the Auto/Man state of Sweep Time that
existed before entering Zero Span is restored.
If Sweep Time was in Auto before entering Zero Span, or if it is set to Auto while in
zero span (which can happen via remote command or if Auto Couple is pressed) it
returns to Auto and recouples when returning to non-zero spans.
If Sweep Time was in Man before entering Zero Span, it returns to Man when
returning to non-zero spans, and any changes to Sweep Time that were made
while in Zero Span are retained in the non-zero span (except where constrained by
minimum limits, which are different in and out of zero span).
Status Bits/OPC dependencies
Meas Uncal is Bit 0 in the STATus:QUEStionable:INTegrity:UNCalibrated register
Sweep/Measure
Allows you to toggle between Continuous and Single sweep or measurement
operation. The single/continuous state is Meas Global so the setting will affect all
measurements.
Remote Language Compatibility Measurement Application Reference
318
3 RLC Mode & Swept SA Measurement
Sweep
The front-panel Single/Cont key performs this exact same function.
See "More Information" on page 319
SCPI Command not available in N9061C
Preset
ON (Note that SYST:PRESet sets INIT:CONT to ON but *RST sets INIT:CONT to OFF)
State Saved
Saved in instrument state.
More Information
For Spectrum Analysis mode in ESA and PSA, there is no Cont hardkey, instead
there is a Sweep Single/Cont softkey. In these analyzers, switching the Sweep
Single/Cont softkey from Single to Cont restarts averages (displayed average
count reset to 1), but does not restart Max Hold and Min Hold.
The X-Series A-models have Single and Cont hardkeys in place of the Sweep
Single Cont softkey. In the X-Series A-models, if in single measurement, the Cont
hardkey (and INIT:CONT ON ) switches to continuous measurement, but never
restarts a measurement and never resets a sweep.
The X-Series B-models have a Cont/Single toggle control instead of Single and
Cont hardkeys, but it is still true that, if in single measurement, the Cont/Single
toggle control never restarts a measurement and never resets a sweep.
For Spectrum Analysis mode in ESA and PSA, the Single hardkey and the
INITiate:IMM switched from continuous measurement to single measurement and
restarted sweeps and averages (displayed average count reset to 1), but did not
restart Max Hold and Min Hold. In the X-Series, the Restart control and the
INITiate:IMM command initiate a sweep/ measurement/ average sequence/hold
sequence including Max Hold and Min Hold.
For Spectrum Analysis mode in ESA and PSA, the Single hardkey restarted the
sweep regardless of whether or not you were in an active sweep or sweep
sequence. In the X-Series, Restart does this.
INIT[:IMM] in ESA & PSA Spectrum Analysis Mode does an implied ABORt. In some
other PSA Modes, INIT[:IMM] is ignored if not in the idle state. This conforms to
SCPI specified operation for INIT[:IMM] as shown in SCPI Command Reference
section 24.7.2. The X-Series follows the ESA/PSA SA Mode model, which may
cause some Modes to have compatibility problems.
Restart
The Restart function restarts the current sweep, or measurement, or set of
averaged/held sweeps or measurements. If you are Paused, pressing Restart does a
Resume.
The front panel key Restart performs this exact same function.
See "More Information" on page 320
SCPI command not available in N9061C.
Notes
:INITiate:RESTart and :INITiate:IMMediate perform exactly the same function.
319
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Sweep
Couplings
Resets average/hold count k. For the first sweep overwrites all active (update=on)
traces with new current data. For application modes, it resets other parameters as
required by the measurement.
Status Bits/OPC dependencies
This is an Overlapped command.
The STATus:OPERation register bits 0 through 8 are cleared.
The STATus:QUEStionable register bit 9 (INTegrity sum) is cleared.
The SWEEPING bit is set.
The MEASURING bit is set.
Backwards Compatibility Notes
For Spectrum Analysis mode in ESA and PSA, the Restart hardkey and the
INITiate:RESTart command restart trace averages (displayed average count reset
to 1) for a trace in Clear Write, but did not restart Max Hold and Min Hold.
In the X-Series, the Restart hardkey and the INITiate:RESTart command restart not
only Trace Average, but Max Hold and Min Hold traces as well.
For wireless communications modes in ESA and PSA, the Restart hardkey and the
INITiate:RESTart command restart every measurement, which includes all traces
and numeric results. There is no change to this operation.
More Information
The Restart function first aborts the current sweep or measurement as quickly as
possible. It then resets the sweep and trigger systems, sets up the measurement
and initiates a new data measurement sequence with a new data acquisition
(sweep) taken once the trigger condition is met.
If the analyzer is in the process of aligning when a Restart is executed, the
alignment finishes before the restart function is performed.
Even when set for Single operation, multiple sweeps may be taken when Restart is
pressed (for example, when averaging/holding is on). When we say that Restart
"restarts a measurement," we may mean:
– It restarts the current sweep
– It restarts the current measurement
– It restarts the current set of sweeps if any trace is in Trace Average, Max Hold or
Min Hold
– It restarts the current set of measurements if Averaging, or Max Hold, or Min
Hold is on for the measurement
– depending on the current settings
Remote Language Compatibility Measurement Application Reference
320
3 RLC Mode & Swept SA Measurement
Sweep
With Average/Hold Number (in Meas Setup menu) set to 1, or Averaging off, or no
trace in Trace Average or Hold, a single sweep is equivalent to a single
measurement. A single sweep is taken after the trigger condition is met and the
analyzer stops sweeping once that sweep has completed. However, with
Average/Hold Number >1 and at least one trace set to Trace Average, Max Hold, or
Min Hold (SA Measurement) or Averaging on (most other measurements), multiple
sweeps/data acquisitions are taken for a single measurement. The trigger
condition must be met prior to each sweep. The sweep is stopped when the
average count k equals the number N set for Average/Hold Number. A
measurement average usually applies to all traces, marker results, and numeric
results, but sometimes it only applies to the numeric results.
Once the full set of sweeps has been taken, the instrtument goes to the idle state.
To take one more sweep without resetting the average count, increment the
average count by 1, by pressing the step up key while Average/Hold Number is the
active function, or send the remote command CALC:AVER:TCON UP.
Sweep Config Tab
Sweep Type
Chooses between the FFT and Sweep types of sweep.
Sweep Type refers to whether or not the instrument is in Swept or FFT analysis.
When in Auto, the selection of sweep type is governed by two different sets of rules,
depending on whether you want to optimize for dynamic range or for speed.
FFT “sweeps” should not be used when making EMI measurements. When a CISPR
detector (Quasi Peak, EMI Average, RMS Average) is selected for any active trace
(one for which Update is on), the FFT key in the Sweep Type menu is grayed out, and
the Auto Rules only choose Swept. If Sweep Type is manually selected to be FFT,
the CISPR detectors are all grayed out.
FFT sweeps will never be auto-selected when Screen Video, Log Video or Linear
Video are the selected Analog Output.
Command
[:SENSe]:SWEep:TYPE FFT|SWEep
[:SENSe]:SWEep:TYPE?
[:SENSe]:SWEep:TYPE:AUTO OFF|ON|0|1
[:SENSe]:SWEep:TYPE:AUTO?
Example
SWE:TYPE SWE
:SWE:TYPE:AUTO ON
Preset
AUTO
ON
State Saved
Saved in instrument state.
Dependencies
Grayed out in Zero Span, however, the setting can be changed remotely with no
error indication.
Grayed out or blanked in measurements that do not support swept mode.
321
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Sweep
When Gate is on, Gate Method selection affects Sweep Type availability:
When Gate Method is FFT, Swept grayed out and rules choose FFT
When Gate Method is Video or LO, FFT grayed out and rules choose Swept
Swept is Grayed out while in Gated FFT (meaning Gate is ON and Gate Method is
FFT).
When a CISPR detector (Quasi Peak, EMI Average, RMS Average) is selected for
any active trace, the FFT selection is grayed out.
When the RF Preselector is on, the FFT selection is grayed out.
When Signal ID is on, Manual FFT is grayed out.
While in Gated LO (meaning Gate is ON and Gate Method is LO), the FFT selection is
grayed out.
While in Gated Video (meaning Gate is ON and Gate Method is Video), the FFT
selection is grayed out.
Couplings
Pressing Auto Couple always sets Sweep Type to Auto.
Swept is always chosen whenever any form of Signal ID is on, or any EMI detector
is selected, or the RF Preselector is ON.
Examples
Value
Example
Notes
Auto
:SWE:TYPE:AUTO
ON
When in Auto, the selection of sweep type is governed by two
different sets of rules, depending on whether you want to optimize for
dynamic range or for speed. These rules are chosen under the Sweep
Type Rules control.
FFT
SWE:TYPE FFT
Manually selects FFT analysis, so it cannot change automatically to
Swept.
Swept
SWE:TYPE SWE
Manually selects swept analysis, so it cannot change automatically
to FFT.
This selection is chosen automatically if any of the CISPR detectors
is chosen for any active trace, in which case the FFT Sweep Type
selection is also grayed out.
Sweep Type Rules
Selects which set of rules will be used for automatically choosing the Sweep Type
when Sweep Type is in Auto.
Command
[:SENSe]:SWEep:TYPE:AUTO:RULes SPEed|DRANge
Remote Language Compatibility Measurement Application Reference
322
3 RLC Mode & Swept SA Measurement
Sweep
[:SENSe]:SWEep:TYPE:AUTO:RULes?
[:SENSe]:SWEep:TYPE:AUTO:RULes:AUTO[:STATe] OFF|ON|0|1
[:SENSe]:SWEep:TYPE:AUTO:RULes:AUTO[:STATe]?
:SWE:TYPE:AUTO:RUL SPE
Example
:SWE:TYPE:AUTO:RUL:AUTO ON
DRANge
Preset
ON
State saved
Saved in instrument state.
Dependencies
Grayed out in Zero Span, however, the setting can be changed remotely with no
error indication.
Couplings
Pressing Auto Couple always sets Sweep Type Rules to Auto.
Backwards Compatibility Notes
The legacy parameter DYNamicrange is unsupported.
Examples
Value
Example
Notes
Auto
:SWE:TYPE:AUTO:RUL:AUTO
ON
When in Auto, the Sweep Type Rules are set to Best
Dynamic Range. It seems like a very simple Auto
function but the use of this construct allows a
consistent statement about what the Auto Couple
function does.
Best
Dynamic
Range
SWE:TYPE:AUTO:RUL DRAN
This selection tells the analyzer to choose between
swept and FFT analysis with the primary goal of
optimizing dynamic range. If the dynamic range is very
close between swept and FFT, then it chooses the
faster one. This auto selection also depends on RBW
Type.
Best
Speed
SWE:TYPE:AUTO:RUL SPE
This selection tells the analyzer to choose between FFT
or swept analysis based on the fastest analyzer speed.
Sweep Time Rules
Allows the choice of three distinct sets of sweep time rules. These are the rules that
are used to set the sweep time when Sweep Time is in Auto mode. Note that these
rules only apply when in the Swept Sweep Type (either manually or automatically
chosen) and not when in FFT sweeps.
If any selection is manually chosen, the AUTO/MAN toggle is set to MAN.
See "More Information" on page 324
323
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Sweep
Command
[:SENSe]:SWEep:TIME:AUTO:RULes NORMal|ACCuracy|SRESponse
[:SENSe]:SWEep:TIME:AUTO:RULes?
[:SENSe]:SWEep:TIME:AUTO:RULes:AUTO[:STATe] ON|OFF|1|0
[:SENSe]:SWEep:TIME:AUTO:RULes:AUTO[:STATe]?
Example
:SWE:TIME:AUTO:RUL ACC
:SWE:TIME:AUTO:RUL:AUTO ON
Preset
AUTO
ON
State Saved
Saved in instrument state.
Dependencies
Grayed out in Zero Span, however, the setting can be changed remotely with no
error indication.
Grayed out in FFT sweeps. Pressing this selection while the instrument is in FFT
sweep generates an advisory message. The SCPI is acted upon if sent, but has no
effect other than to change the readout on the control, as long as the analyzer is in
an FFT sweep.
Couplings
Set to Auto on Auto Couple.
Backwards Compatibility Commands
:SWEep:TIME:AUTO:MODE SRESponse
This legacy command is aliased to :SWEep:TIME:AUTO:RULes SRESponse
:SWEep:TIME:AUTO:MODE SANalyzer
This legacy command is aliased to :SWEep:TIME:AUTO:RULes NORMal
The old Auto Sweep Time command was the same
[:SENSe]:SWEep:TIME:AUTO:RULes NORMal|ACCuracy
so it still works although it now has a third parameter (SRESponse)
The old Sweep Coupling command was
[:SENSe]:SWEep:TIME:AUTO:MODE SRESponse|SANalyzer and it is aliased as
described in "More Information" on page 324.
More Information
Value
Example
Notes
Auto
:SWE:TYPE:AUTO:RUL:AUTO
ON
When in Auto, the Sweep Type Rules are set
to Best Dynamic Range. It seems like a very
simple Auto function but the use of this
construct allows a consistent statement
Remote Language Compatibility Measurement Application Reference
324
3 RLC Mode & Swept SA Measurement
Sweep
Value
Example
Notes
about what the Auto Couple control does.
SA - Normal
:SWE:TIME:AUTO:RUL
NORM
This selection selects auto rules for optimal
speed and generally sufficient accuracy.
SA - Accuracy
:SWE:TIME:AUTO:RUL ACC
This selection selects auto rules for
specified absolute amplitude accuracy.
Stimulus/Response
:SWE:TIME:AUTO:RUL SRES
This selection selects auto rules for the case
where the analyzer is sweeping in concert
with a source.
Automatically selected when the Source is
on (Source Mode not set to OFF).
The first set of rules is called SA – Normal. Sweep Time Rules is set to SA-Normal
on a Preset or Auto Couple. These rules give optimal sweep times at a loss of
accuracy. Note that this means that in the Preset or Auto Coupled state,
instrument amplitude accuracy specifications do not apply.
Setting Sweep Time Rules to SA-Accuracy will result in slower sweep times than
SA-Normal, usually about three times as long, but with better amplitude accuracy
for CW signals. The instrument absolute amplitude accuracy specifications only
apply when Sweep Time is set to Auto, and Sweep Time Rules are set to SAAccuracy. Additional amplitude errors that occur when Sweep Time Rules are set to
SA-Normal are usually well under 0.1 dB with non-EMI detectors (though this is not
guaranteed). With EMI detectors (Quasi Peak, EMI Average and RMS Average), the
errors are usually well under 0.5 dB. For best accuracy when using EMI detectors,
zero span is the preferred measurement technique. For the EMI detectors, zero
span measurements will not fully agree with swept measurements except at
extremely slow sweep rates.
Because of the faster sweep times and still low errors, SA-Normal is the preferred
setting of Sweep Time Rules.
The third set of sweep time rules is called Stimulus/Response and is automatically
selected when an integrated source is turned on, such as a Tracking Generator or a
synchronized external source.
Note that there are two types of source-synchronized sweeping, one where the
source sweeps (as with a built in tracking generator) and one where the source
steps. The former is usually much faster than even general purpose sweeps
because when sweeping along with a swept source the RBW and VBW filters do
not directly interact with the Span. However, sweeping in concert with a stepped
source usually slows the sweep down because it is necessary to wait for the
stepped source and the analyzer to settle at each point. The analyzer chooses one
of these methods based on what kind of a source is connected or installed. It picks
the former if there is no source in use, which means that by selecting
Stimulus/Response rules manually when there is no source in use, you can achieve
faster sweep times than SA – Normal.
Stimulus-response auto-coupled sweep times are typically valid in stimulusresponse measurements when the system’s frequency span is less than 20 times
325
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Sweep
the bandwidth of the device under test. As noted above you can select these rules
manually (even if not making Stimulus-Response measurements), which will allow
you to sweep faster before the “Meas Uncal” warning comes on, but you are then
not protected from the over-sweep condition and may end up with uncalibrated
results. However, it is commonplace in measuring non-CW signals such as noise to
be able to get excellent measurement accuracy at sweep rates higher than those
required for CW signal accuracy, so this is a valid measurement technique.
When the X-series analyzer is in Auto Sweep Time, the sweep time is estimated
and displayed in the Sweep/Control menu as well as in the annotation at the
bottom of the displayed measurement. Since this can be dependent on variables
outside the analyzer’s control, the actual sweep time may vary slightly from this
estimate.
FFT Width
This menu displays and controls the width of the FFT’s performed while in FFT mode.
The “FFT width” is the range of frequencies being looked at by the FFT, sometimes
referred to as the “chunk width” -- it is not the resolution bandwidth used when
performing the FFT.
It is important to understand that this function does not directly set the FFT width, it
sets the limit on the FFT Width. The actual FFT width used is determined by several
other factors including the Span you have set. Usually the instrument picks the
optimal FFT Width based on the current setup, but on occasion you may wish to limit
the FFT Width to be narrower than the one the instrument would have set.
This function does not allow you to widen the FFT Width beyond that which the
instrument might have set; it only allows you to narrow it. You might do this to improve
the dynamic range of the measurement or eliminate nearby spurs from your
measurement.
Note that the FFT Width setting will have no effect unless in an FFT sweep.
See "More Information" on page 327
Command
[:SENSe]:SWEep:FFT:WIDTh <real>
[:SENSe]:SWEep:FFT:WIDTh?
[:SENSe]:SWEep:FFT:WIDTh:AUTO OFF|ON|0|1
[:SENSe]:SWEep:FFT:WIDTh:AUTO?
Example
SWE:FFT:WIDT 167 kHz sets this function to “<167.4 kHz”
:SWE:FFT:WIDT:AUTO ON
Preset
The Preset is Auto, but Preset will also pick Best Dynamic Range and hence this function
will be set to ~Maximum
ON
Min/Max
Min:4.01 kHz
Max:The maximum available FFT width is dependent on the IF Bandwidth option. The
maxim mum available width is:
Standard, 10 MHz;
Remote Language Compatibility Measurement Application Reference
326
3 RLC Mode & Swept SA Measurement
Sweep
Option B25, 25 MHz,
Option B40, 40 MHz
State
Saved
Saved in instrument state
Notes
The parameter is in units of frequency.
For values sent from SCPI, the analyzer chooses the smallest value that is at least
as great as the requested value.
Examples:
Parameter 3.99 kHz is sent over SCPI. Analyzer chooses ≤4.01 kHz
Parameter 4.02 kHz is sent over SCPI. Analyzer chooses ≤28.81 kHz
Parameter 8 MHz is sent over SCPI. Analyzer chooses 10 MHz
Dependencies
In some models, the analog prefilters are not provided. In these models the FFT
Width function is always in Auto. The FFT Width key is blanked in these models, and
the SCPI commands are accepted without error but have no effect.
Grayed out in Zero Span, however, the setting can be changed remotely with no
error indication.
Couplings
The FFT Width affects the ADC Dither function (see Meas Setup key) and the point
at which the instrument switches from Swept to FFT acquisition.
Backwards Compatibility Commands
[:SENSe]:SWEep:FFT:SPAN:RATio <integer>
[:SENSe]:SWEep:FFT:SPAN:RATio?
This is the legacy “FFTs per Span” command, because in the PSA, this is what you
set rather than the FFT Width. The behavior of the analyzer when it receives this
command is to compute the “intended segment width” by dividing the Span by the
FFTs/Span parameter, then converting this intended width to an actual width by
using the largest available FFT Width that is still less than the intended segment
width. The “Span” used in this computation is whatever the Span is currently set to,
whether a sweep has been taken at that Span or not.
More Information
An FFT measurement can only be performed over a limited span known as the “FFT
segment”. Several segments may need to be combined to measure the entire
span. For advanced FFT control in the X-Series, you have direct control over the
segment width using the FFT Width control. Generally, in automatic operation, the
X-Series sets the segment width to be as wide as possible, as this results in the
fastest measurements.
327
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Sweep
However, to increase the dynamic range, most X-series models provide a set of
analog prefilters that precede the ADC. Unlike swept measurements, which pass
the signal through a bandpass before the ADC, FFT measurements present the full
signal bandwidth to the ADC, making them more susceptible to overload, and
requiring a lower signal level. The prefilters act to alleviate this phenomenon - they
allow the signal level at the ADC to be higher while still avoiding an ADC overload,
by eliminating signal power outside the bandwidth of interest, which in turn
improves dynamic range.
Although narrowing the segment width can allow higher dynamic ranges in some
cases, this comes at the expense of losing some of the speed advantages of the
FFT, because narrower segments require more acquisitions and proportionately
more processing overhead.
However, the advantages of narrow segments can be significant. For example, in
pulsed-RF measurements such as radar, it is often possible to make high dynamic
range measurements with signal levels approaching the compression threshold of
the analyzer in swept spans (well over 0 dBm), while resolving the spectral
components to levels below the maximum IF drive level (about –8 dBm at the input
mixer). But FFT processing experiences overloads at the maximum IF drive level
even if the RBW is small enough that no single spectral component exceeds the
maximum IF drive level. If you reduce the width of an FFT, an analog filter is placed
before the ADC that is about 1.3 times as wide as the FFT segment width. This
spreads out the pulsed RF in time and reduces the maximum signal level seen by
the ADC. Therefore, the input attenuation can be reduced and the dynamic range
increased without overloading the ADC.
Further improvement in dynamic range is possible by changing the FFT IF Gain (in
the Meas Setup menu of many measurements). If the segments are reduced in
width, FFT IF Gain can be set to High, improving dynamic range.
Depending on what IF Bandwidth option you have ordered, there can be up to three
different IF paths available in FFT sweeps, as seen in the diagram below:
Remote Language Compatibility Measurement Application Reference
328
3 RLC Mode & Swept SA Measurement
Sweep
The 10 MHz path is always used for Swept sweeps. It is always used for FFT
sweeps as well, unless you specify ~25 MHz in which case the 25 MHz path will be
used for FFT sweeps, or ~40 MHz, in which case the 40 MHz path will be used for
FFT sweeps. Note that, although each of these selections pick the specified path,
the analyzer may choose an FFT width less than the full IF width, to optimize
speed, trading off acquisition time versus processing time.
Points
Sets the number of points taken per sweep, and displayed in the traces. The current
value of points is displayed parenthetically, next to the sweep time in the lower-right
corner of the display. Using more points provides greater resolution. Using fewer
points compacts the data and decreases the time required to access a trace over the
remote interface.
Increasing the number of points does not increase the sweep time. However, it can
slightly impact the trace processing time and therefore the overall measurement
speed. Decreasing the number of points does not decrease the sweep time, but it
may speed up the measurement, depending on the other sweep settings (for
example, in FFT sweeps). Fewer points will always speed up the I/O.
Due to minimum sweep rate limitations of the hardware, the minimum sweep time
available to the user will increase above its normal value of 1 ms as the number of
sweep points increases above 15001.
Changing the number of sweep points has several effects on the analyzer. The
sweep time resolution will change. Trace data for all the traces will be cleared and, if
Sweep is in Cont, a new trace taken. If any trace is in average or hold, the averaging
starts over.
When in a split screen display each window may have its own value for points.
329
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Sweep
When sweep points is changed, an informational message is displayed, "Sweep
points changed, all traces cleared."
Command
[:SENSe]:SWEep:POINts <integer>
[:SENSe]:SWEep:POINts?
Example
SWE:POIN 5001 SWE:POIN?
Preset
1001
Min/Max
1/20001
State Saved
Saved in instrument state.
Dependencies
– This function is not available when Signal ID is set to On in External Mixing.
– Neither the knob nor the step keys can be used to change this value. If it is tried,
a warning is given.
– Clipped to 1001 whenever you are in the Spectrogram View.
– Grayed out in measurements that do not support swept.
– Blanked in modes that do not support Swept.
– Grayed out if Normalize is on. You cannot change the number of sweep points
with Normalize on, as it will erase the reference trace.
Couplings
Whenever the number of sweep points change:
– All trace data is erased
– Any traces with Update Off will also go to Display Off (like going from View to
Blank in the older analyzers)
– Sweep time is re-quantized
– Any limit lines that are on will be updated
– If averaging/hold is on, averaging/hold starts over
Backwards Compatibility Notes
1. In ESA and PSA, Sweep Points was adjustable with the knob and step keys. This
caused the sweep time to increase whenever Points was adjusted (either up or
down), due to excessive application of the quantization rules. In the X-Series the
value of Sweep Points must be entered manually, which avoids this anomaly
2. In ESA the preset value of Sweep Points is 401, in PSA it is 601. In X-Series it is
1001.
Remote Language Compatibility Measurement Application Reference
330
3 RLC Mode & Swept SA Measurement
Trace
Trace
A trace is a series of data points, each having an x and a y value. The x value is
frequency (or time, in zero span) and the y value is amplitude. Each data point is
referred to as a trace point. In any given trace, trace point 0 is the first point, and
trace point (sweep_points – 1) is the last. For example, in a 1001 point trace, the first
point is 0 and the last is 1000.
Another term sometimes used to describe traces is bucket. A bucket is the frequency
span of a trace point, equal to the point spacing. For swept analysis, the y value in
each bucket is measured while the analyzer is sweeping across the bucket. How it is
measured depends on which detector is selected.
The Trace menu lets you control the acquisition, display, storage, detection and
manipulation of trace data for the available traces.
Select Trace
Specifies the selected trace. The term “selected trace” is used to specify which trace
will be affected when you change trace settings, perform a math operation, etc.
The Select Trace control appears above the menu panel, indicating that it applies to
all controls in the Trace menu panels. Select Trace is blanked if you select a tab
whose controls do NOT depend on the selected trace (e.g., Normalize).
In the SA Measurement:
– In Image Suppress mode when you select a trace it becomes the active trace,
and the formerly active trace goes into View
– When you turn on Image Suppress, Update turns off for all traces except the
selected trace
In the ACP Measurement:
– When Meas Method is RBW, FAST or Fast Power, Select Trace is disabled.
Trace Update Indicator
Trace updates can take one of two forms:
1. The trace is updated in a single operation that affects all of the points in the trace
at once. This happens, for example, in the case of very fast (< 200 ms) sweeps,
single-chunk FFT’s, and the initial math operation after a math function is set for
a trace.
2. The trace is updated in a series of discrete steps, with measurement data being
gathered between each step. This will be the case for slow sweeps, multi-chunk
FFT’s, etc.
In the first case, no update indicator is required. In the second case, however, a
visual indicator exists on the trace where the new data is being written, a green
“caret” or ^ symbol, which moves across the bottom of the graticule showing the
current trace point.
331
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trace
Trace Annunciator Panel
The trace annunciator panel appears on the right hand side of the Meas Bar. Here
is an explanation of the fields in this panel:
On the top line each trace number is shown, in the trace color. A blue box is drawn
around the currently selected trace.
Below each trace number is a letter signifying the trace type for that trace number,
where:
W=Clear/Write
A=Trace Average
M=Max Hold
m=Min Hold
If the letter is white it means the trace is being updated (Update = On); if the letter is
dimmed, it means the trace is not being updated (Update = Off). A strikethrough
(e.g., W) indicates that the trace is blanked (Display = Off). Note that it is possible
for a trace to be updating and blanked, which is useful if the trace is a trace math
component.
The third line shows the detector type for each trace, or, if trace math is on for that
trace, it shows an “f” (for “math function”). It is not always possible to have a unique
detector for each trace, but the analyzer hardware provides the maximum flexibility
of detector selection in order to maintain the highest accuracy. The letters used for
this readout are:
N=Normal
A=Average
P=peak
p=negative peak
S=Sample
Q=Quasi Peak
Remote Language Compatibility Measurement Application Reference
332
3 RLC Mode & Swept SA Measurement
Trace
E=EMI Average
R=RMS Average
f=math function
If the DET letter is green it means the detector is in Auto; if it is white it means the
detector has been manually selected.
So in the example above, the panel shows the following:
Trace 1: Visible, being updated, in Clear/Write, with Normal detector auto selected
Trace 2: Visible, being updated, in Clear/Write, being written to with a math
function
Trace 3: Visible, not updating, data was taken in Max Hold, with the peak detector
auto selected
Trace 4: Blanked, not updating, data was taken with Averaging turned on, Sample
detector manually selected
Trace 5: Visible, not updating, data was taken in Min Hold with Negative Peak
detector auto selected
Trace 6: Blanked, not updating, in Clear/Write, with Normal detector manually
selected
Trace Annotation
When Trace Annotation (see the Display menu) is On, each non-blanked trace is
labeled on the trace with the detector used to take it, unless a trace math function
is on for that trace, in which case it is labeled with the math function.
The detector labels are:
NORM = Normal
PEAK = Peak
SAMP = Sample
NPEAK = Negative Peak
RMS = Average detector with Power Average (RMS)
LG AVG = Average detector with Log-Pwr Average
VAVG = Average detector with Voltage Average
QPEAK = Quasi Peak
EMI AVG = EMI Average
RMS AVG = RMS Average
The trace math labels are:
PDIF = Power Difference
PSUM = Power Sum
333
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trace
LOFF = Log Offset
LDIF = Log Difference
Trace Control Tab
Controls the selection of the trigger source and the setup of each of the trigger
sources. The instrument is designed to allow triggering from a number of different
sources: Free Run, Video, External, RF Burst, and so forth.
Note that the Trigger Tab parameters change depending on which source is
selected.
Trace Type
There are four trace Types:
"Clear/Write" on page 336 = WRITe
"Trace Average" on page 336 = AVERage
"Max Hold" on page 336 = MAXHold
"Min Hold" on page 336 = MINHold
You may select one of these types for each trace. Re-selecting the current Trace
Type initiates the same action that selecting it the first time did, even though it is
already selected. For example, selecting Clear/Write while Clear/Write is already
selected will nonetheless clear the trace and begin rewriting it.
Both the Trace Type, the View/Blank state must be set to Active (Update On, Display
On) for a trace to be updating and visible. Selecting any Trace Type automatically
makes the trace Active.
See also the View/Blank menu description.
Command
:TRACe[1]|2|3|4|5|6:TYPE WRITe|AVERage|MAXHold|MINHold
:TRACe[1]|2|3|4|5|6:TYPE?
Example
TRAC:TYPE WRIT TRAC:TYPE?
Preset
WRITe
After a Preset, all traces are cleared (all trace points set to mintracevalue).
State Saved
The type of each trace is saved in instrument state
Backwards Compatibility Notes
The legacy TRACe:MODE command is retained for backwards compatibility. In
conjunction with the legacy :AVErage command, it works as follows:
– :AVErage ON|OFF sets/clears a variable which we will call average for the
sake of this discussion. This variable is maintained by the analyzer solely for
backwards compatibility. See the [:SENSe]:AVERage[:STATe] command
description below.
Remote Language Compatibility Measurement Application Reference
334
3 RLC Mode & Swept SA Measurement
Trace
– :TRACe:MODE WRITe sets :TRACe:TYPE WRITe (Clear/Write) unless average
is true, in which case it sets it to :TRACe:TYPE AVErage. It also sets
:TRACe:UPDate ON, :TRACe:DISPlay ON, for the selected trace.
– :TRACe:MODE MAXHold sets:TRACe:TYPE MAXHold (Max Hold). It also
sets:TRACe:UPDate ON, :TRACe:DISPlay ON, for the selected trace.
– :TRACe:MODE MINHold sets :TRACe:TYPE MINHold (Min Hold). It also
sets:TRACe:UPDate ON, :TRACe:DISPlay ON, for the selected trace.
– :TRACe:MODE VIEW sets :TRACe:UPDate OFF, :TRACe:DISPlay ON, for the
selected trace • :TRACe:MODE BLANk sets :TRACe:UPDate OFF,
:TRACe:DISPlay OFF, for the selected trace
The query will return the same value as a :TRACe:TYPE? Query, meaning that if you
set :TRACe:MODE:VIEW or :TRACe:MODE:BLANk, the query response will not be
what you sent.
Trace Mode Backwards Compatibility
Command
:TRACe[1]|2|3|4|5|6:MODE WRITe|MAXHold|MINHold|VIEW|BLANk
:TRACe[1]|2|3|4|5|6:MODE?
Preset
WRITe
State
Saved
The trace mode is an alias only
Notes
The legacy command :TRACe[n]:MODE was formerly used to set the type or “writing
mode” of the trace. At that time, View and Blank were writing modes. The new
TRACe:TYPE command should be used in the future, but TRACe:MODE is retained to
afford backwards compatibility.
In the X-Series, unlike earlier analyzers, Max Hold and Min Hold now obey the Average
Number and counts up to a terminal value as Average always has.
As the Average/Hold Number now affects Min Hold and Max Hold, the things that
restart Averaging (e.g., the Restart key) now also restart Min Hold and Max Hold.
As a result of these changes, users who used to restart averaging while retaining a
running Max Hold will find that they need to rewrite their code, because the Max Hold
will restart when the Average does.
Also, previous to the X-Series,
- pressing Max Hold while already in Max Hold (or doing so remotely) had no
effect. Now it will clear the trace and restart the sweep and the Max Hold
sequence.
- changing the vertical scale (Log/Lin or dB/div) of the display restarted Max
Hold and Min Hold. This is no longer the case
Trace Averaging Backwards Compatibility
Command
[:SENSe]:AVERage[:STATe] ON|OFF|1|0
[:SENSe]:AVERage[:STATe]?
335
Preset
OFF
State
The state of Average is saved in Instrument State for ghosting purposes.
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trace
Saved
Notes
Previous to the X-Series, Averaging (also sometimes known as trace averaging) was
global to all traces, that is, it was either on or off for all active traces. The legacy
command [:SENSe]:AVERage[:STATe] ON | OFF | 1 | 0 was used to turn averaging on and
off.
In the X-Series, Averaging is turned on and off on a per-trace basis, so it can be on for
one trace and off for another.
For backwards compatibility, the old global Average State variable is retained solely as
a legacy variable, turned on and off and queried by the legacy command
[:SENSe]:AVERage[:STATe] OFF|ON|0|1. When Average is turned on, any trace in
Clear/Write will get put into Average. While Average is on, any trace put into
Clear/Write by the old TRAC:MODE command will instead get put into Average. When
Average is turned off, any trace in Average will get put into Clear/Write.
Trace Writing Type
Value
Example
Notes
Clear/Write
:TRAC2:TYPE
WRIT
In Clear/Write type each trace update replaces the old data in the
trace with new data.
Selecting Clear/Write clears the trace and initiates a new sweep.
Trace
Average
:TRAC2:TYPE
AVER
In Trace Average type the analyzer maintains and displays an
average trace, which represents the cumulative average on a pointby-point basis of the new trace data and previous averaged trace
data.
Selecting Trace Average will clear the trace, initiate a new sweep,
and restart the Average sequence.
Max Hold
:TRAC3:TYPE
MAXH
In Max Hold type the analyzer maintains and displays a max hold
trace, which represents the maximum data value on a point-bypoint basis of the new trace data and previous trace data
Selecting Max Hold will clear the trace, initiate a new sweep, and
restart the hold sequence.
Min Hold
:TRAC5:TYPE
MINH
In Min Hold type the analyzer maintains and displays a min hold
trace, which represents the minimum data value on a point-point
basis of the new trace data and previous trace data.
Selecting Min Hold will clear the trace, initiate a new sweep, and
restart the hold sequence.
Clear and Write | Restart Averaging | Restart Max/Min Hold
This control is provided to start the trace writing as though the trace type had just
been selected. Pressing this control is exactly like selecting the radio button of the
current trace type again.
This control takes on different labels depending on the Trace Type:
Remote Language Compatibility Measurement Application Reference
336
3 RLC Mode & Swept SA Measurement
Trace
– Clear/Write: Clear and Write
– Trace Average: Restart Averaging
– Max Hold: Restart Max Hold
– Min Hold: Restart Min Hold
View/Blank
This control lets you set the state of the two trace values, Update and Display. The
four choices available in this menu are:
– Active: Update and Display both On
– View: Update Off and Display On
– Blank: Update Off and Display Off
– Background: Update On, Display Off (this allows a trace to be blanked and
continue to update “in the background”, which was not possible in the past)
A trace with Display Off is indicated by a strike-through thru the type letter in the
trace annotation panel in the Measurement bar. A trace with Update Off is indicated
by dimming the type letter in the trace annotation panel in the Measurement bar. So
in the example below, Traces 3, 4, 5 and 6 have Update Off and Traces 4 and 6 have
Display Off.
See "More Information" on page 338
When Signal ID is on, this key is grayed out.
Command
:TRACe[1]|2|3|4|5|6:UPDate[:STATe] ON|OFF|0|1
:TRACe[1]|2|3|4|5|6:UPDate[:STATe]?
:TRACe[1]|2|3|4|5|6:DISPlay[:STATe] ON|OFF|0|1
:TRACe[1]|2|3|4|5|6:DISPlay[:STATe]?
Example
TRAC2:UPD 0 Makes trace 2 inactive (stops updating)
TRAC2:DISP,1 Makes trace 2 visible
TRAC3:DISP,0 Blanks trace 3
Preset
1|0|0|0|0|0 (On for Trace 1; Off for 2–6)
State Saved
Saved in instrument state .
Couplings
337
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trace
Whenever you set Update to On for any trace, the Display is set to On for that trace.
A trace is put in the active state (Update On and Display On) in the following:
– a trace type is selected on the Trace Control tab (Clear/Write, Trace Average,
Max Hold, Min Hold) for a trace, even if that trace type was already selected.
– a detector is selected for a trace on the Detector tab (or sending a
[:SENS]:DET:TRAC command, even if that detector was already selected.
– a math mode other than Off is selected for a trace on the Math tab (or sending
the equivalent SCPI command), even if that math mode was already selected.
Loading a trace from a file puts that trace in View regardless of the state it was in
when it was saved, as does being the target of a Copy or a participant in an
Exchange.
Backwards Compatibility
:TRACe:MODE VIEW sets :TRACe:UPDate OFF, :TRACe:DISPlay ON, for the
selected trace. In earlier analyzers, View and Blank were trace modes, set by
TRACe:MODE command. In the X-Series, View and Blank are two of the states set
by the :TRACe:UPDate and :TRACe:DISPlay commands. The TRACe:MODE VIEW
command will yield its new equivalent, which is Update=Off, Display=On
:TRACe:MODE BLANk sets :TRACe:UPDate OFF, :TRACe:DISPlay OFF, for the
selected trace. In earlier analyzers, View and Blank were trace modes, set by
TRACe:MODE command. In the X-Series, View and Blank are two of the states set
by the :TRACe:UPDate and :TRACe:DISPlay commands. The TRACe:MODE BLANk
command will yield its new equivalent, which is Update=Off, Display=Off
More Information
When a trace becomes inactive, any update from the SENSe system (detectors)
immediately stops – this does not wait for the end of the sweep. The trace data
remains unchanged but stops updating. If the trace is blanked this still does not
affect the data in the trace. Traces which are blanked (Display=off) do not display
nor appear on printouts but their data stays intact and they may be queried and
markers may be placed on them
In most cases, inactive traces are static and unchanging. However, there are cases
when an inactive trace will update, specifically:
– if data is written to that trace from remote
– if trace data is loaded from mass storage if the trace is the target of a Copy or
participant in an Exchange
– if the trace is cleared using the Clear Trace function (below)
Inactive traces that are also being displayed (traces in View) are displayed at half
intensity. Traces in View display across the entire X Axis of the instrument. Their
horizontal placement does not change even if X Axis settings subsequently are
changed, although Y-axis settings will affect the vertical placement of data.
Remote Language Compatibility Measurement Application Reference
338
3 RLC Mode & Swept SA Measurement
Trace
When a trace becomes active (Update=On), the trace is cleared, the average count
is reset, and a new sweep is initiated.
Note that the action of putting a trace in Display=Off and/or Update=Off does not
restart the sweep and does not restart Averaging or Hold functions for any traces.
Trace Settings Table
The Trace Settings Table lets you configure the Trace system using a visual utility.
Detector Tab
Detector
Opens a dropdown list that enables you to select a specific detector for the current
measurement. The detector selected is then applied to the selected trace.
The analyzer is in Auto detection by default, and normally Auto detection will choose
the best detector for you automatically. If you choose a detector manually, this will
turns Auto detection off for the selected trace.
For the SCPI UI, two commands are provided. One is a legacy command, which
affects all traces. There is also a command which is new for the X-Series, which uses
a subopcode to specify to which trace the specified detector is to be applied.
The three detectors at the end of the Detector menu, Quasi Peak, EMI Average, and
RMS Average, are referred to collectively as the “CISPR detectors” because their
behaviors are specified by the CISPR 16–1–1 specification.
See "More Information" on page 343
339
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trace
The analyzer can typically provide 3 different detectors simultaneously. Occasionally the
analyzer can only provide 2 simultaneous detectors, typically when the Average
detector is selected. When one of the CISPR detectors is selected, it is only possible to
have that one detector so all active traces change to that detector. It is never possible to
have more than 3 simultaneous detectors.
Command
[:SENSe]:DETector:TRACe[1]|2|3|4|5|6
AVERage|NEGative|NORMal|POSitive|SAMPle|QPEak|EAVerage|RAVerag
e
[:SENSe]:DETector:TRACe[1]|2|3|4|5|6?
Example
DET:TRAC AVER sets trace 1’s detector to average
DET:TRAC1 AVER sets trace 1’s detector to average
DET:TRAC2 SAMP sets trace 2’s detector to sample
Preset
Preset returns all traces to “auto”, which will result in Normal (Rosenfell) detection for all
traces.
State
Saved
Saved in instrument state.
Notes
The query returns a name that corresponds to the detector type as shown below,
and indicates the setting for Trace 1.
String Returned
Definition
NORM
Normal
AVER
Average/RMS
POS
Positive Peak
SAMP
Sample
NEG
Negative Peak
QPE
Quasi peak
EAV
EMI Average
RAV
RMS Average
Dependencies
When Tune & Listen is turned on, or Demod Audio is the selected Analog Output, all
active traces are forced to use the same detector.
CISPR detectors are grayed out when you have manually selected FFT sweep.
Conversely, if any CISPR detector is selected on an active trace, the auto rules for
sweep type will never select FFT, and manual FFT selection will be grayed out.
When Signal ID is on, the Detector key is grayed out for Traces 2-6 in Image
Suppress mode and for Traces 3-6 in Image Shift Mode.
Remote Language Compatibility Measurement Application Reference
340
3 RLC Mode & Swept SA Measurement
Trace
The VBW filter is not used for the Average detector or any of the CISPR detectors
(Quasi Peak, EMI Average, RMS Average), as indicated by a * after the VBW value
on the graph if any of these detectors is selected for any updating trace.
It is never possible to have more than 3 simultaneous detectors, and sometimes
fewer than three. If the analyzer has to enforce this limit a message is generated,
“Detector n changed due to physical constraints” where “n” is the detector number.
Couplings
Selecting a detector for a trace (pressing the key or sending a [:SENS]:DET:TRAC
command) puts Update On and Display On for that trace, even if that detector was
already selected. Note that the legacy command [:SENS]:DET[:FUNC] does NOT
exhibit this behavior.
The auto detector rules depend upon marker type, averaging state and type, trace
state writing mode, and trace active state
Selecting a detector, whether by pressing the control or sending the equivalent
SCPI command, will turn trace math to Off for the selected/specified trace.
Use of the Average detector affects the VBW setting because of its effect on the
VBW/RBW coupling.
Selecting any CISPR detector on any active trace sets the EMC Standard to CISPR.
If any trace with a CISPR detector becomes active, the EMC Standard is set to
CISPR.
If the Avg Type is in Auto, and any of the CISPR detectors is selected on any active
trace, the Voltage Averaging type is auto-selected.
In Tracking Source mode, if a stepped source is used, the best detector is Average,
as this gives optimal sensitivity. Therefore, when operating a source in Tracking
Source mode, Auto selection is Average. All other detector selections are allowed,
but in most cases the user will want to stick with the Auto selection, which gives
optimal sensitivity.
Backwards Compatibility
Command
[:SENSe]:DETector[:FUNCtion]
NORMal|AVERage|POSitive|SAMPle|NEGative|QPEak|EAVerage|EPOSitiv
e|MPOSitive|RMS
[:SENSe]:DETector[:FUNCtion]?
Example
DET AVER sets detector to average for all traces
Notes
This is a SCPI only legacy command to preserve the classic functionality wherein all traces
are affected when a detector is selected (in the X-Series, the detector is set on a pertrace basis).
DET:FUNC? returns trace 1’s detector setting
The query returns a name that corresponds to the detector type as shown below, and
indicates the setting for Trace 1.
The RMS selection sets the detector type to AVERage and the Average Type to RMS.
Therefore if RMS has been selected, the query will return the “AVER” string.
The EPOS selection sets the detector type to Peak and the EMC Standard to CISPR. A
query will then return POS.
341
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trace
The MPOS selection sets the detector type to Peak and the EMC Standard to MIL
Impulse. A query will then return POS.
The RAV parameter is not included in the command because this is not a legacy detector;
nonetheless, if it happens to be the detector on Trace 1 then RAV will be returned.
String Returned
Definition
NORM
Normal
AVER
Average/RMS
POS
Positive Peak
SAMP
Sample
NEG
Negative Peak
QPE
Quasi peak
EAV
EMI Average
RAV
RMS Average
Preset
NORMal
State
Saved
Saved in instrument state.
Notes:
1. In ESA and E7400, selecting QPD or EMI Average sets the Amplitude Scale Type
to Linear and performs an auto-ranging function resulting in the Reference Level
being adjusted such that the highest level of the trace is near (but below) the
Reference Level. Subsequent selection of Peak, Negative Peak, Sample, or
Average (the 'non-EMI Detectors') will return the Reference Level and Amplitude
Scale Type to their pre-EMI Detector values. The X-Series does not perform this
scale and reference level change because the digital IF makes it unnecessary..
2. The commands which select the CISPR detectors are not generally compatible
with pre-PSA instruments, because the CISPR detectors are now part of the
overall detector set, rather than a separate set. However, the basic behavior of
coupling the resolution bandwidth to the selected detector is similar to the
behavior of previous EMI analyzers, like the E4400B series.
3. In the past, selecting Auto Couple All did not change the selected CISPR
detector. Now, since the CISPR detectors are part of the full set of detectors,
pressing Auto Couple All will switch from the selected CISPR detector to an auto
coupled detector according to the Auto Detector rules in the Detector, Auto key
description below.
4. The following ESA/E7400 detector commands are no longer accepted:
[:SENSe]:DETector[:FUNCtion]:EMI QPD|AVERage|OFF
[:SENSe]:POWer:QPGain[:STATe]
[:SENSe]:ARDT
Remote Language Compatibility Measurement Application Reference
342
3 RLC Mode & Swept SA Measurement
Trace
More Information
Value
Example
Notes
Normal
:DET:TRAC3
NORM
Determines the peak of CW-like signals, and yields alternating
maximums and minimums of noise-like signals. This is also referred to as
Rosenfell detection.
Average
:DET:TRAC3
AVER
Determines the average of the signal within the bucket. The averaging
method depends upon Average Type selection (voltage, power or log
scales) and delivers: RMS detection when Avg Type = Power Video
detection when Avg Type = Log-Pwr Scalar detection when Avg Type =
Voltage
Peak
:DET:TRAC3
POS
Determines the highest signal within the bucket.
Sample
:DET:TRAC3
SAMP
Determines the instantaneous level of the signal at the center of the
bucket
Negative
Peak
:DET:TRAC3
NEG
Determines the minimum of the signal within the bucket
Quasi
Peak
:DET:TRAC3
QPE
EMI – CISPR detector
Only appears with the N6141A or W6141A application or Option EMC
installed and licensed.
A fast-rise, slow-fall detector used in making CISPR compliant EMI
measurements, compliant with the latest CISPR 16-1-1standard.
EMI
Average
:DET:TRAC3
EAV
EMI – CISPR detector
Only appears with the N6141A or W6141A application or Option EMC
installed and licensed.
Provides a standard means to “smooth” the signal while still providing
compliance to CISPR pulse response standards. It displays the average
value of the amplitude envelope, rather than the average value of
sample-detected amplitude, and uses an advanced algorithm to realize
a lowpass filter that conforms to the latest CISPR 16-1-1standard.
RMS
Average
:DET:TRAC3
RAV
EMI – CISPR detector
Not to be confused with the RMS mode of the regular Average detector,
this is a special frequency-dependent EMI filter which only appears
when the N6141A or W6141A application or Option EMC is installed and
licensed.
This filter conforms to the latest revision of the CISPR 16–1–1 standard.
Detector Basics
To understand detectors you must understand the concept of trace buckets. For
every trace point in swept and zero span analysis, there is a finite time during which
the data for that point is collected. The analyzer has the ability to look at all of the
data collected during that time and present a single point of trace data based on
the detector type. We call the interval during which the data is being collected the
“bucket.” Often the term “trace point” is used to mean the same thing.
343
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trace
However, it is important to understand that a trace is more than a series of single
points. The data is sampled rapidly enough within each “bucket” and processed so
that the detector results are equivalent to those that would be achieved with a
continuous time (non-sampled) system.
Detector Notes
– The VBW filter is not used for the Average detector or any of the CISPR
detectors (Quasi Peak, EMI Average, RMS Average), so varying the VBW will
have no effect for any traces for which this detector is selected (other than to
slow down the sweep, because of the coupling to Sweep Time of VBW). If any
traces for which VBW does not apply are in Update On state (traces with
Average, EMI Average, RMS Average or Quasi Peak detectors selected), then
an * displays after the VBW annotation on the front panel.
– Rosenfell (Normal) detection: when the signal is CW-like, it displays the peakdetected level in the interval (bucket) being displayed. If the signal is noise-like
(within a bucket the signal both rose and fell), it alternates displaying the
max/min values. That is, an even bucket shows the peak (maximum) within a
two-bucket wide interval centered on the even bucket. And an odd bucket will
show the negative peak (minimum) within a two-bucket wide interval. For
example, for an even bucket the two-bucket wide interval is a combination of
one-half bucket to the left of the even bucket, the even bucket itself, and onehalf bucket to the right of the even bucket, so the peak found will be displayed in
the correct relative location on screen. The odd buckets are similar.
– The Average Detector result depends on the Average Type. To explicitly set the
averaging method, use the Meas Setup, Average Type key.
– Because they may not find a spectral component's true peak, neither average
nor sample detectors measure amplitudes of CW signals as accurately as peak
or normal, but they do measure noise without the biases of peak detection.
– Peak detection is used for CW measurements and some pulsed-RF
measurements. For FFT analysis, the highest amplitude across the frequency
width of a bucket is displayed, even if that peak amplitude falls between
samples of the spectrum computed in the FFT process.
– Sample detection is good for displaying noise or noise-like signals but is not the
best choice for making amplitude measurements of CW-like signals. This is
because:
- the peak response to a signal can occur between samples. So unless the
Span to RBW ratio is lower than usual, then the highest sample can be well
below the peak signal amplitude.
Remote Language Compatibility Measurement Application Reference
344
3 RLC Mode & Swept SA Measurement
Trace
- for the high sweep rates normally used, the peak response of the RBW
filters is up to –0.5 dB. This sweeping error is compensated when using the
peak and normal detectors by changing the overall gain. But the gain is not
changed when in the sample detector, because doing so would cause
errors in the response to noise. Instead, the auto-couple rules for sweep
time are modified to give slower sweeps (see the Sweep/Control Section).
– When the Detector choice is Auto, the detector selected depends on marker
functions, trace functions, average type, and the trace averaging function.
– When you manually select a detector (instead of selecting Auto), that detector
is used regardless of other analyzer settings.
CISPR Detector Notes
– Quasi Peak
This is a fast-rise, slow-fall detector used in making CISPR compliant EMI
measurements and defined by CISPR Publication 16–1–1. Quasi-peak detection
displays a weighted, sample-detected amplitude using specific, charge,
discharge, and meter time constants derived from the legacy behaviors of
analog detectors and meters. It is used for EMI measurements to provide a
specific and consistent response to EMI-like signals.
Also in the past, EMI analysis equipment would need to perform a ranging
operation to set the reference level when one of these detectors was turned
on, but the X-series analyzers do not - because of its digital IF, there is no
need to set the reference level (range) to improve the accuracy nor to allow
visibility of the detected level.
– EMI Average
The EMI Average detector in Agilent’s X-Series analyzers is so called to
distinguish it from the Average detector, although EMI users typically refer to it
simply as the “Average detector”. The intent of this detector is to provide a
standard means to “smooth” the signal while still providing compliance to
CISPR pulse response standards.
Unlike the regular Average detector, which averages on a bucket-by-bucket
basis using either a power, log-power or voltage scale (a bucket is the same
as a trace point), the EMI Average detector displays the average value, on the
voltage scale, of the overall amplitude envelope, independent of the trace
bucket width. It is defined for EMI measurements by the CISPR 16–1–1
standard and, in the X-series, uses a sophisticated algorithm to implement a
lowpass filter that conforms to the latest CISPR standard.
Note that CISPR standard operation is to perform the envelope averaging on
the voltage scale. You can manually set the Average Type to Log-Power or
Power, but the results will no longer be CISPR compliant. See note under
Quasi-Peak.
345
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trace
– RMS Average
Not to be confused with the RMS mode of the regular Average detector, this is
a special filter for making EMI measurements. It is a frequency dependent
RMS/Averaging filter, used in making CISPR compliant EMI measurements. This
filter conforms to the 2007 revision of the CISPR 16–1–1 standard. This detector
does one averaging process (in the VBW hardware) on the "power" (a.k.a. RMS)
scale and another process on the voltage scale using a "meter movement
simulator" similar to the one used in the QPD filter.
Note that CISPR standard operation is to perform the envelope averaging on
the voltage scale. You can manually set the Average Type to Log-Power or
Power, but the results will no longer be CISPR compliant. See note under
Quasi-Peak.
Multiple Detectors
The analyzer always provides the requested detector on the specified trace.
Depending on the detectors requested the analyzer can provide up to three
different detectors simultaneously within the constraints of its digital processing
algorithms. Some detectors utilize more resources; the Quasi-Peak detector, for
example, utilizes most of the digital IF’s resources, and the hardware in some
analyzers is incapable of providing another detector when Quasi-Peak is on. If the
limit of system resources is exceeded, detectors on some existing traces may be
forced to change. When this happens, they change to match the detector just
requested, and a message is generated: “Detector <X> changed due to physical
constraints”, where X might contain multiple values.
Example: User has traces 1, 2, and 3 with Peak, Average, and Negative Peak. User
specifies QPD for trace 1. Traces 2 and 3 also change to QPD and we generate the
message “Detector 2,3 changed due to physical constraints”. Now all three traces
have the QPD.
Detector Select
This toggle sets the Detector mode to Auto or Manual. In Auto, the proper detector
is chosen based on rules that take into account the measurement settings and other
analyzer settings.
When you manually select a detector, this toggle automatically sets to Man
(manual).
Command
[:SENSe]:DETector:TRACe[1]|2|3|4|5|6:AUTO ON | OFF | 1 | 0
[:SENSe]:DETector:TRACe[1]|2|3|4|5|6:AUTO?
Example
DET:TRACE2:AUTO ON sets trace 2 detection to automatic.
Remote Language Compatibility Measurement Application Reference
346
3 RLC Mode & Swept SA Measurement
Trace
Preset
Auto (On) for all detectors.
State Saved
Saved in instrument state.
Dependencies
The auto detector rules depend upon marker type, averaging state and type, trace
state writing mode, and trace active state.
Couplings
Selecting AUTO, whether by toggling the control or sending the equivalent SCPI
command, will turn trace math to Off for the selected/specified trace.
Backwards Compatibility
Command
[:SENSe]:DETector:AUTO ON | OFF | 1 | 0 [:SENSe]:DETector:AUTO?
Example
DET:AUTO ON
Notes
SCPI only. Turns AUTO on or off for ALL detectors. This is a legacy command to
preserve the classic functionality wherein all traces are affected when a detector is
addressed
The query returns the Auto state of Trace 1.
Math Tab
Math Function
The trace math functions perform mathematical operations between traces and, in
some cases, user-specified offsets. When in a trace math function, the indicated
function is performed during the sweep with the math function used in place of a
detector.
The trace operands for the math function are set using the Trace Operands control.
See "Math: More Information" on page 349
Command
:CALCulate:MATH TRACE1|TRACE2|TRACE3|TRACE4|TRACE5|TRACE6,
PDIFference|PSUM|LOFFset|LDIFference|OFF,
TRACE1|TRACE2|TRACE3|TRACE4|TRACE5|TRACE6,
TRACE1|TRACE2|TRACE3|TRACE4|TRACE5|TRACE6, <real>,<real>
:CALCulate:MATH?
TRACE1|TRACE2|TRACE3|TRACE4|TRACE5|TRACE6
Example
:CALC:MATH TRACE1,PDIF,TRACE4,TRACE5,, sets Trace 1 to Power Diff trace math
function, and sets the First Trace operand (for Trace 1) to Trace 4 and the Second Trace
operand (for Trace 1) to Trace 5.
:CALC:MATH TRACE1,PSUM,TRACE4,TRACE5,, sets Trace 1 to Power Sum trace math
function and sets the First Trace operand (for Trace 1) to Trace 4 and the Second Trace
operand (for Trace 1) to Trace 5.
347
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trace
:CALC:MATH TRACE1,LOFF,TRACE4,,–6.00, sets Trace 1 to Log Offset trace math
function, sets the First Trace operand (for Trace 1) to Trace 4, leaves the Second Trace
operand (for Trace 1) unchanged (it is irrelevant for this function) and sets the Log Offset
(for Trace 1) to –6 dB. :CALC:MATH TRACE1,LDIF,TRACE4,TRACE5,,–6.00 sets Trace 1 to
Log Diff trace math function, sets the First Trace operand (for Trace 1) to Trace 4, sets
the Second Trace operand (for Trace 1) to Trace 5, and sets the Log Difference reference
for Trace 1 to –6 dBm.
CALC:MATH TRACE1 OFF turns off trace math for trace 1.
Preset
OFF,TRACE5,TRACE6,0,0 | OFF,TRACE6,TRACE1,0,0 | OFF,TRACE1,TRACE2,0,0 |
OFF,TRACE2,TRACE3,0,0 | OFF,TRACE3,TRACE4,0,0 | OFF,TRACE4,TRACE5,0,0
State
Saved
The trace math function for each trace is saved in instrument state.
Notes
The Trace Math Function command has 6 main set of parameters:
- Set 1 defines the “result trace”:
TRACE1|TRACE2|TRACE3|TRACE4|TRACE5|TRACE6
-Set 2 defines the “function”:
PDIFference|PSUM|LOFFset|LDIFference|OFF
- Set 3 is a “trace operand” (1):
TRACE1|TRACE2|TRACE3|TRACE4|TRACE5|TRACE6
- Set 4 is a “trace operand” (2):
TRACE1|TRACE2|TRACE3|TRACE4|TRACE5|TRACE6
- Set 5 defines the “Log Offset” (in dB).
- Set 6 defines the “Log Difference Reference” (in dBm).
Note that the trace math mode is an enumeration; that is, when a math function is
set for a trace it turns off any math function that is on for that trace and sets the
new math function.
The parameters sent in the command are reflected in the values in the softkey
menu. There is no default for any parameter; all 6 parameters must be sent to
satisfy the parser. Failure to specify a parameter will result in a missing parameter
message. See error –109.
Note that for some of the math modes some of the parameters are not relevant.
For those modes, the parameters are ignored, and sending “,,” is sufficient for
those parameters.
The query returns the math mode, the operand traces, the offset and the reference
for the specified trace, all separated by commas. The return value of irrelevant
parameters is undefined; empty fields (“,,”) would be desirable.
Dependencies
Remote Language Compatibility Measurement Application Reference
348
3 RLC Mode & Swept SA Measurement
Trace
Trace Math is not available if Normalize is on.
Trace Math is not available if Signal ID is on.
None of the trace operands can be the destination trace. If any of the three trace
math commands is sent with a destination trace number matching one of the
operands a warning is generated and the function does not turn on.
Couplings
Whenever a math function other than “Off” is selected for a trace, that trace is set
to Display=On and Update=On.
Status Bits/OPC dependencies
*OPC can be used to detect the completion of a sweep, which will also correspond
to the completion of the math operation, since all math takes place during the
sweep.
Backwards Compatibility Notes
The legacy TRACE:MATH:ADD and TRACE:MATH:SUBTract commands have been
eliminated.
Math: More Information
To generate a trace math result, you must take a sweep. The trace math engine,
described below, operates in concert with the sweep engine in the analyzer. Until a
sweep has been taken, even if the constituent traces are not in Update mode, no
result is generated. Note that certain events can affect the trace in ways that
affects all points at once. This can happen in any number of ways, including:
– A trace clear taking place
– A trace being loaded from the file system
– Trace data being sent in from the remote interface
– A copy or exchange of trace data
You should try to avoid these occurrences during a sweep, as they will tend to
invalidate the math result being accumulated.
The Trace Math Functions:
Power Diff (Op1 – Op2)
Calculates a power difference between the First Trace operand and the Second
Trace operand and puts the result in the destination trace.
During the sweep, the following formula is executed for each point in the trace
operands, and the corresponding point is generated for the destination trace:
DestinationTrace = 10 log(10(1/10)(FirstTrace) – 10(1/10)(SecondTrace))
349
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trace
The values of the trace points are assumed to be in a decibel scale, as they are
internally stored.
If a point in FirstTrace is equal to maxtracevalue, the resultant point is also
maxtracevalue.
Otherwise, if the result of the subtraction is less than or equal to 0, the resultant
point is mintracevalue.
Power Sum (Op1 + Op2)
Calculates a power sum between the First Trace operand and the Second Trace
operand and puts the result in the destination trace.
During the sweep, the following formula is executed for each point in the trace
operands, and the corresponding point is generated for the destination trace:
DestinationTrace = 10 log(10(1/10)(FirstTrace) + 10(1/10)(SecondTrace))
The values of the trace points are assumed to be in a decibel scale, as they are
internally stored.
If a point in either trace operand is equal to maxtracevalue, the resultant point is
also maxtracevalue.
Log Offset (Op1 + Offset)
Calculates a log offset from the First Trace operand and puts the result in the
destination trace. This is like the B-DL function in some older analyzers. The offset
is entered on the Offset control, which only appears when this math function is in
force for the selected trace. Each destination trace has its own offset.
During the sweep, the following formula is executed for each point in the trace
operand, and the corresponding point is generated for the destination trace:
DestinationTrace = FirstTrace + Offset
The values of the trace points are assumed to be in dBm (as they are internally
stored) and the offset is in dB.
If a point in the trace operand is equal to maxtracevalue, the resultant point is also
maxtracevalue.
If a point in the trace operand is equal to mintracevalue, the resultant point is also
mintracevalue.
Example: If offset is 25 dB, then our destination trace will be higher than the
operand trace by 25 dB.
Note that the Second Trace operand is not used for this function.
Log Diff (Op1 – Op2 + Ref)
Offsets the difference between the First Trace operand and the Second Trace
operand by a reference and puts the result in the destination trace. This is like the
A-B+DL function in some older analyzers. The Reference is entered on the
Remote Language Compatibility Measurement Application Reference
350
3 RLC Mode & Swept SA Measurement
Trace
Reference control, which only appears when this math function is in force for the
selected trace. Each destination trace has its own reference.
During the sweep, the following formula is executed for each point in the trace
operands, and the corresponding point is generated for the destination trace:
DestinationTrace = (FirstTrace - SecondTrace) + Reference
The values of the operand trace points are assumed to be in decibel units (as they
are internally stored) and the reference is in dBm so the result is in dBm.
For each active trace, the current trace point is processed for Trace 1, then Trace 2,
then Trace 3, etc. Trace data is taken from either the detector for that trace, or from
the mathematical result of up to two other traces and an offset, depending on
whether trace math is on or not. The resultant data is then fed to the Average/Hold
processing block, where (if the trace type is Average, Max Hold, or Min Hold) it is
351
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trace
processed with previous trace data. The new trace data resulting from this process
is then available for display, storage or remote output.
When the processing is complete for Trace 1, Trace 2 is processed, and so on until
all six traces have been processed. This allows a downstream trace to use as one
of its math components a fully processed upstream trace. In other words, if math is
on for Trace 4, and its operand traces are Trace 2 and Trace 3, all detector, math,
average and hold processing for traces 2 and 3 is complete before the math is
performed for trace 4. When the current trace point is completed for all traces, the
analyzer moves on to the next trace point.
This allows very flexible and powerful math functions to be configured. For
example, Trace 1 can be an average trace, which can be fed with an offset to Trace
2, which can also be in Max Hold, allowing the user to take the Max Hold of an
Average trace.
Note that none of this processing is performed on inactive traces.
Note also that for any active trace with math on, you want your operand traces to
have a lower number than the trace (e.g., using Trace 4 as an operand for Trace 1
will cause the data coming from Trace 4 to be delayed by one sweep). This does not
pertain if the operand trace is inactive, so we have decided to make no attempt to
enforce this condition. It is up to the user to understand and conform.
Operand 1
Selects the first trace operand to be used for the trace math functions for the
destination trace.
Example
:CALC:MATH TRACE1,PDIF,TRACE4,TRACE5,,
sets Trace 1 to Power Diff trace math function, and sets the First Trace operand (for Trace
1) to Trace 4 and the Second Trace operand (for Trace 1) to Trace 5.
:CALC:MATH TRACE1,LOFF,TRACE4,,–6.00,
sets Trace 1 to Log Offset trace math function, sets the First Trace operand (for Trace 1) to
Trace 4, leaves the Second Trace operand (for Trace 1) unchanged (it is irrelevant for this
function) and sets the Log Offset (for Trace 1) to –6 dB.
Preset
Trace number minus 2 (wraps at 1). For example, for Trace 1, Operand 1 presets to Trace 5;
for Trace 6, it presets to Trace 4
State
Saved
Operand 1 for each trace is stored in instrument state.
Notes
See the Math Function section for how to specify Operand 2 using the
:CALCulate:MATH SCPI command.
Dependencies
The destination trace cannot be an operand. The destination trace number is gray
on the dropdown.
Remote Language Compatibility Measurement Application Reference
352
3 RLC Mode & Swept SA Measurement
Trace
Operand 2
Selects the second trace operand to be used for the trace math functions for the
destination trace. The operands are common to all math functions for a given trace.
The most recently sent :CALCulate:MATH command for a given trace sets the
operands for that trace and will be reflected on the trace operand controls for that
trace.
Example
:CALC:MATH TRACE1,PDIF,TRACE4,TRACE5,,
sets Trace 1 to Power Diff trace math function, and sets the First Trace operand (for Trace
1) to Trace 4 and the Second Trace operand (for Trace 1) to Trace 5.
Preset
Trace number minus 1 (wraps at 1). For example, for Trace 1, Operand 2 presets to Trace 6;
for Trace 6, it presets to Trace 5.
State
Saved
Operand 2 for each trace is stored in instrument state.
Notes
See the Math Function section for how to specify Operand 2 using the
:CALCulate:MATH SCPI command.
Dependencies
The destination trace cannot be an operand. The destination trace number is gray
on the dropdown.
Trace Function Tab
The Trace Function tab lets you copy and exchange traces and preset or clear all
traces.
– From Trace - Selects the trace to be copied to or exchanged with the To Trace.
– To Trace - Selects the trace to be copied from or exchanged with the From Trace.
Copy
This button executes a Trace Copy based on the From Trace and To Trace
parameters. The Copy is done from the From Trace to the To Trace. The action is
performed once.
The X-Axis settings and domain of a trace go with it when it is copied.
Command
:TRACe:COPY TRACE1|TRACE2|TRACE3|TRACE4|TRACE5|TRACE6,
TRACE1|TRACE2|TRACE3|TRACE4|TRACE5|TRACE6
:TRACe:COPY?
353
Example
TRAC:COPY TRACE1,TRACE3 copies Trace 1 to Trace 3 and puts Trace 3 in Update=Off,
Display=On
Preset
TRACE1, TRACE2
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trace
Dependencies
When Signal ID is on, this key is grayed out.
Couplings
The destination trace is put in View (Update=Off, Display=On) after the copy.
Backwards Compatibility Notes
The copy and exchange operations menu in ESA and PSA is replaced with the more
general purpose Trace Function menu. The remote commands are unaffected, as
they were already general.
The 2-DL->2 function in ESA and PSA (which was really a trace math function) has
been eliminated, because its use case was very rare. It actually subtracted the dBequivalent of the dBm-expressed display line, regardless of the y axis unit. For
example, if DL = +21.99 dBmV, it subtracted –25.00 dB (i.e. add +25.00 dB) to trace
2. New, more useful functions are provided in the new Trace, Math menu.
Exchange
This button executes a Trace Exchange based on the From Trace and To Trace
parameters. The From Trace and To Trace are exchanged with each other. The
action is performed once.
The X-Axis settings and domain of a trace go with it when it is exchanged with
another trace.
Command
:TRACe:EXCHange TRACE1|TRACE2|TRACE3|TRACE4|TRACE5|TRACE6,
TRACE1|TRACE2|TRACE3|TRACE4|TRACE5|TRACE6
:TRACe:EXCHange?
Example
TRAC:EXCH TRACE1,TRACE2 exchanges Trace 1 and Trace 2 and puts both traces in
Update=Off, Display=On.
The TRACe:EXCHange command is of the form:
:TRACe:EXCHange <trace_1>,<trace_2>
Couplings
Both traces are put in View (Update=Off, Display=On) after the exchange.
Backwards Compatibility Notes
The copy and exchange operations menu in ESA and PSA is replaced with the more
general purpose Trace Function menu. The remote commands are unaffected, as
they were already general.
Preset All Traces
Turns on Trace 1 and blanks all other traces. Useful when you have many traces on
and you want to go back to having only Trace 1 on the display. Does not affect the
trace type, detector or any other aspect of the trace system.
When Signal ID is on, this key is grayed out.
Remote Language Compatibility Measurement Application Reference
354
3 RLC Mode & Swept SA Measurement
Trace
Command
:TRACe:PRESet:ALL
Example
TRAC:PRES:ALL
Clear All Traces
Clears all traces. Does not affect the state of any function or variable in the
instrument. Loads mintracevalue into all of the points all traces, except traces in Min
Hold in which case it loads maxtracevalue. Does so even if Update=Off.
When Signal ID is on, this control is grayed out.
:TRACe:CLEar:ALL
Command
:TRACe:PRESet:ALL
Example
TRAC:CLE:ALL
Normalize Tab
Normalize
Normalize (On) activates the normalize function. On each sweep, the normalized
trace (Trace 3) is subtracted from Trace 1 and the result is added to the normalized
reference level. This arithmetic assumes all values are in decibel units, so we are
actually taking a ratio.
The steps to perform the Normalize function are:
1. Store the current Trace 1 into the reference trace, which is Trace 3
2. Turn on Normalize
If you try to turn on Normalize without first storing a reference trace, you will get an
error.
See "More Information" on page 356, "Measurement Details" on page 356,
"Normalize Block Diagram" on page 357
Command
:CALCulate:NTData[:STATe] OFF|ON|0|1
:CALCulate:NTData[:STATe]?
Example
CALC:NTD ON
CALC:NTD?
Couplings
When Normalize is turned on, Trace 1 is placed in Clear/Write with Update = On and
Display = On.
Preset
OFF
State
Saved
Saved in instrument state.
Dependencies
355
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trace
– If Normalize (On) is pressed before Store Ref (1→ 3), an error message is
generated. Normalize remains off in this case.
– Normalize is not available (grayed out) if any Trace Math function is on.
– Normalize is not available if Amplitude, Scale Type is set to 'Lin”.
More Information
The normalize function is most useful for applying correction data to a trace while
making a stimulus-response measurement with a tracking generator (or
synchronized source). For example, connect the cables and a through line, in place
of the device to be measured, between the tracking generator and the analyzer
input. Notice that the frequency response is not perfectly flat, showing the
response of the cables, as well as the flatness of both the tracking generator and
the analyzer. Now press Store Ref (1→ 3), Normalize On. Notice that the displayed
trace is now flat, or normalized. The position of the normalized trace can now be
moved to a different position on the display by changing the normalized reference
position. This may be useful if the device to be tested has positive gain, such as an
amplifier. Now replace the through line with the device under test, and an accurate
measurement of the gain or loss can be made.
The normalize function can also be used to perform a scalar reflection
measurement (return loss). In this case a directional coupler or bridge is used to
extract the reflected signal. In the simplest reflection measurement a Short is
placed at the end of the cable and the result is stored to trace 3 (as before). When
Normalize is turned on, the result is the calibrated return loss in dB. For a more
accurate calibration, an Open and Short can be used. To do the Open/Short
calibration, the Open/Short control at the bottom of the Normalize menu is
pressed. This will initiate a guided calibration procedure, which captures the
reference trace. This is then stored to Trace 3, as before. When Normalize is turned
on the corrected return loss is displayed.
Measurement Details
First the following calculation is performed:
Trace 1 = (Trace 1D – Normalized Trace)
Where:
Trace 1D is the measured value of trace 1, as it comes from the SENSe
subsystem.
Normalized Trace is Trace 3, in which you have previously stored a
reference trace
All values are in decibel units.
This Trace 1 contains the values that will be returned from a trace query, or if the
marker is placed on the trace.
Remote Language Compatibility Measurement Application Reference
356
3 RLC Mode & Swept SA Measurement
Trace
For example, let's say bucket 1 on Trace 1 is at 0 dBm, and bucket 1 on Trace 3 is at
10 dBm. The resultant bucket is at 0 dBm – 10 dBm = –10 dB (just like with a delta
marker).
You are also given the ability to define what (dB) value to use for Ref Level, and to
define where on the screen the Ref Lvl line will appear using Normalized Reference
Position. This flexibility in displaying the result allows a wide range of devices,
including amplifiers, to be tested using Normalize.
In the example above, bucket 1 has the value of –10 dB. Let us assume you have
set Norm Ref Lvl to 5 dB. Thus bucket 1 will display 1.5 divisions below the
Reference Level line (assuming 10 dB per division).
The Reference Level line is normally the top line of the graticule. If Norm Ref
Position is set to 10, this is the case. If it is set to 9, it is the next line down. If it is set
to 5, it is the middle line of the graticule. If set to 0 it is the bottom line.
So in the example above, if Norm Ref Position is set to 9, then bucket 1 will display
2.5 divisions below the top line of the graticule.
None of the manipulations of Norm Ref Position and Norm Ref Lvl affect the data in
the trace.
As Normalize displays a ratio between two traces (a difference, in dB) the Y-Axis
Unit while in Normalize is dB in Log Amplitude and dimensionless in Linear. The Y
Axis Unit chosen in the Y Axis Unit menu is unaffected by Normalize. When you
leave Normalize the Y Axis Unit returns to the value set in the Y Axis Unit menu.
While in Normalize, all amplitude functions, such as Marker Y and the values in
other traces, should be always in dB unit, and so should the returned trace query
results. In other words, both trace query result and marker Y become independent
of the Y Axis Unit chosen in the Y Axis Unit menu when normalize is on.
(In Linear, the equivalent calculation is performed but it yields a dimensionless
ratio, so the normalized ref level will be unitless, presetting to 1, just as in Log it
presets to 0 dB. Linear normalization is not currently available in the X-Series).
Y Axis annotation is blanked while in Normalize. Any other traces on the display are
plotted in dB, where the dB value used is equivalent to the dBm value of the trace.
For example, if bucket 1 in trace 2 is at –40 dBm, that bucket is plotted at –40 dB.
All traces use Norm Ref Lvl and Norm Ref Position for positioning on the display.
When Normalize exits, the normal Ref Lvl is restored. This normal Ref Level is
unaffected by Normalize.
Normalize Block Diagram
A block diagram showing how Normalize works is presented below:
357
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trace
Store Ref Trace 1->Trace 3
Copies trace 1 into trace 3. Store Reference (Trace 1→Trace 3) must be pressed
before pressing Normalize (On). Note that this puts Trace 3 in Update=Off (not
updating) and Display=On (visible).
Show Reference Trace 3
Views or blanks the reference trace on the display. The reference trace is trace 3, so
this is the same as setting Trace 3’s “Display” attribute.
Use the TRAC3:DISP command to show or blank the reference trace.
Trace 3 is always the reference trace by definition.
Example
TRAC3:DISP 1 Shows the reference trace.
State Saved
Saved in instrument state.
Norm Ref Lvl
Sets the level (in dB) of the normalized reference. This is the Level of the line
specified by the Norm Ref Position control.
Command
:DISPlay:WINDow[1]:TRACe:Y[:SCALe]:NRLevel <rel_ampl>
:DISPlay:WINDow[1]:TRACe:Y[:SCALe]:NRLevel?
Example
DISP:WIND:TRAC:Y:NRL .10 dB
DISP:WIND:TRAC:Y:NRL?
Preset
0 dB
Min/Max
–327.6 dB/327.6 dB
State Saved
Saved in instrument state.
Remote Language Compatibility Measurement Application Reference
358
3 RLC Mode & Swept SA Measurement
Trace
Norm Ref Position
Sets the graticule line that represent the Norm Ref Lvl. This function may be used to
offset the displayed trace without affecting the instrument gain or attenuation
settings. This allows the displayed trace to be moved off the top of the screen so that
it may be completely seen, but without decreasing measurement accuracy.
The top and bottom graticule lines correspond to 10 and 0, respectively. The
normalized reference position is indicated with a white right arrow on the left side of
the display and a white left arrow on the right side of the display, just inside the
graticule
Command
:DISPlay:WINDow[1]:TRACe:Y[:SCALe]:NRPosition <integer>
:DISPlay:WINDow[1]:TRACe:Y[:SCALe]:NRPosition?
Example
DISP:WIND:TRAC:Y:NRP 5
DISP:WIND:TRAC:Y:NRP?
Preset
10
Min/Max
0/10
State Saved
Saved in instrument state.
Open/Short Cal
Performs a guided open/short calibration, while providing step-by-step instructions
to the user. This is the most accurate way to make the return loss measurement on
the X-series analyzers. You are directed through a 1-Port coaxial open calibration,
and a 1-Port coaxial short calibration. The result can then be saved to Trace 3. It is
used to perform calibrated scalar reflection measurements (return loss), using the
Normalize function.
This control is grayed out unless Source Mode is Tracking.
Open/Short Guided Cal
On pressing the Open/Short Cal control in the Normalize menu, the Open Calibration
Form is displayed. The form shows a diagrammatic representation of how to connect
the external source to the spectrum analyzer to perform the calibration. When the
Continue button is pressed, the Open calibration sweep is taken and stored in
internal memory, for use later in this cal process. If the Cancel button is pressed, the
Open/Short Cal is cancelled and the Normalize menu is returned.
359
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trace
On completion of the Open Calibration, the Short Calibration Form is displayed. This
form shows a diagrammatic representation of how to connect the external source to
the spectrum analyzer to perform the Short calibration. When the Continue button is
pressed, the Short calibration sweep is taken and stored in internal memory, for use
later in this cal process. If the Cancel button is pressed, the Open/Short Cal is
cancelled and the Normalize menu is returned.
Remote Language Compatibility Measurement Application Reference
360
3 RLC Mode & Swept SA Measurement
Trace
On completion of the Short Calibration, the Open and Short calibration
measurements are averaged (power). The picture with a prompt is taken off the
screen and a menu with “Store Cal” and “Exit Without Storing Cal” is displayed.
When you press “Store Cal” the resulting trace is stored to Trace 3. If the “Exit
Without Storing Cal” button is pressed, the Open/Short Cal is cancelled. In either
case you return to the Normalize menu.
361
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trace
The Open Short calibration is applied by taking the average of the Open and the
Short trace. The average is a linear average point-by-point. You can further
configure averaging on the traces (Open, Short, and final measurement). In this
case, the value of the averaged Open and Short trace are linear averaged (by
performing a point-by-point average of the two traces). Both the Open and the Short
terminations should have approximately unity reflection. Taking the average gives
the best estimate of a perfect reflector for a scalar return loss measurement. You
should store the result in reference trace 3, for later application with the Normalize
function.
Remote Language Compatibility Measurement Application Reference
362
3 RLC Mode & Swept SA Measurement
Trigger
Trigger
Accesses a panel that enables you to control the selection of the trigger source and
the setup of each of the trigger sources. The analyzer is designed to allow triggering
from a number of different sources, for example, Free Run, Video, External, RF Burst,
and so forth.
Trigger Tab
Free Run
Free run triggering occurs immediately after the sweep/measurement is initiated.
Select Trigger Source
The TRIG:SOURCe command specifies the trigger source for the currently selected
input (RF or I/Q). If you change inputs, the new input remembers the trigger source it
was last programmed to for the current measurement, and uses that trigger source.
When in External Mixing, the analyzer uses the RF trigger source.
See "Trigger Sources" on page 364.
See "Select Trigger Source" on page 363.
SCPI Commands not available in N9061C
Preset
IMM
Notes
Not all measurements have all the trigger sources available to them. Check the
trigger source documentation for your specific measurement to see what sources
are available.
Not all trigger sources are available for each input. See the RF Trigger Source and
I/Q Trigger Source commands for detailed information on which trigger sources are
available for each input.
Other trigger-related commands are found in the INITiate and ABORt SCPI
command subsystems.
*OPC should be used after requesting data. This will hold off any subsequent
changes to the selected trigger source, until after the sweep is completed and the
data is returned.
Available ranges and presets can vary from mode to mode.
RTSA FMT
The amplitude resolution of the Frequency Mask is coupled to the Scale/Division.
There are 256 vertical points therefore the amplitude resolution is computed using
the algorithm;
(10 * Scale/Div) / # Vertical Points
Dependencies
363
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
In some models, there is no second External input. In these models, the External 2
key is blanked and the EXTernal2 parameter will generate a “Hardware missing;
Not available for this model number” message.
RTSA
Level trigger is allowed in average detector mode.
When Level Trigger is the selected Trigger Source in the Spectrum measurement,
Spectrum minimum Acquisition Time is limited to the PVT minimum Acquisition
Time. If the Spectrum Acquisition Time changed as a result of going into Level
Trigger, a message is posted “Min Acq Time is 200 usec when Level Trigger is ON”.
When Level Trigger is no longer the selected Trigger Source, Spectrum minimum
Acquisition Time is restored.
RTSA FMT
If you were not in Free Run when you entered the FMT Setup View, you can change
Trigger Source to Free Run while in the editor. This will allow you to configure the
mask with a continually updating trace. When exiting FMT Setup View, the Trigger
Source will be changed back to FMT.
Couplings
RTSA FMT
A remote user can enter or access FMT data via :TRIGger[:SEQuence]:FMT
[1]|2:DATA
The upper and lower masks can have different freq/ampl pairs therefore subop
code 1 is for the upper mask and subop code 2 is for the lower mask.
Status Bits/OPC Dependencies
The Status Operation Register bit 5 "Waiting for Trigger" is set at the same time as
the Sweeping or Measuring bit is set. It is cleared when the trigger actually occurs
(that is, after the trigger event occurs and all the applicable trigger criteria have
been met). A corresponding pop-up message ("Waiting for trigger") is generated if
no trigger signal appears after approximately 2 sec. This message goes away when
a trigger signal appears.
Backwards Compatibility
In analyzers prior to the X-Series, the Average detector was not available when
Video triggering was on, and consequently, functions that set the detector to
average (such as Marker Noise or Band/Intvl Power) were not available when the
video trigger was on. Similarly, Video triggering was not available when the
detector was Average. In the X-Series, these restrictions are removed.
This backwards compatibility alias command is provided for ESA/PSA compatibility.
:TRIGger:SOURCe
Trigger Sources
Remote Language Compatibility Measurement Application Reference
364
3 RLC Mode & Swept SA Measurement
Trigger
Source
Example
Annotation
(Meas
Bar)
Notes
Free
Run
TRIG:SOUR
IMM
Free Run
Free run triggering occurs immediately after the sweep/measurement is initiated.
Level
TRIG:SOUR
LEV
Level
The Level trigger condition is met when the signal (the
filtered and detected version of the input signal,
including RBW filtering) crosses the trigger level.
FMT
The Level trigger condition is met when
RTSA
measurement
FMT
TRIG:SOUR
FMT
RTSA
measurement
Video
TRIG:SOUR
VID
Video
The Video trigger condition is met when the video
signal at the left edge of the graticule (the filtered and
detected version of the input signal, including both
RBW and VBW filtering) crosses the video trigger level
with the chosen slope.
Line
TRIG:SOUR
LINE
Line
When Line is selected a new sweep/measurement will
start synchronized with the next cycle of the line
voltage. Line trigger is not available when operating
from a "dc power source", for example, when the
instrument is powered from batteries.
External
1
TRIG:SOUR
EXT1
External 1
A new sweep/measurement will start when the external
trigger condition is met using the external 1 input
connector on the rear panel.
Grayed out if Ext 1 is in use by Point Trigger in the
Source Setup menu.
Forced to Free Run if already selected and Point Trigger
is set to External 1.
External
2
TRIG:SOUR
EXT2
External 2
A new sweep/measurement will start when the external
trigger condition is met using the external 2 input
connector on the rear panel.
Grayed out if Ext 2 is in use by Point Trigger in the
Source Setup menu.
Forced to Free Run if already selected and Point Trigger
is set to External 2
365
RF
Burst
TRIG:SOUR
RFB
RF Burst
A new sweep/measurement will start when an RF burst
envelope signal is identified from the signal at the RF
Input connector.
Periodic
TRIG:SOUR
FRAM
Periodic
Uses a built-in periodic timer signal as the trigger.
Trigger occurrences are set by the Periodic Timer
parameter, which is modified by the Offset and Periodic
Sync Src.
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
Source
Example
Annotation
(Meas
Bar)
Notes
Use this trigger when there a periodic signal but no
reliable signal on which to trigger. You can synchronize
the periodic signal with outside events (using the
Periodic Sync Src) to get closer to a reliable trigger
signal.
If you do not have a sync source selected (it is Off), then
the internal timer will not be synchronized with any
external timing events.
TV
TRIG:SOUR
TV
Swept SA
TV
For triggering on analog TV signals. A new sweep/measurement will start synchronized with the next
occurrence of the synchronizing pulse of the selected
TV line number.
The Trigger menus let you select the trigger source and trigger settings for a sweep
or measurement. In triggered operation (basically, any trigger source other than
Free Run), the analyzer will begin a sweep or measurement only when the selected
trigger conditions are met, generally when your trigger source signal meets the
specified trigger level and polarity requirements. (In FFT measurements, the trigger
controls when the data acquisition begins for FFT conversion.)
For each of the trigger sources, you may define a set of operational parameters or
settings which will be applied when that source is selected as the current trigger
source. Examples of these settings are Trigger Level, Trigger Delay, and Trigger
Slope. You may apply different settings for each source; so, for example, you could
have a Trigger Level of 1v for External 1 trigger and -10 dBm for Video trigger.
Once you have established the settings for a given trigger source, they generally will
remain unchanged for that trigger source as you go from measurement to
measurement within a Mode (although the settings can change as you go from Mode
to Mode). Furthermore, the trigger settings within a Mode are the same for the
Trigger menu, the Gate Source menu, and the Periodic Sync Src menu. That is, if Ext1
trigger level is set to 1v in the Trigger menu, it will appear as 1v in both the Gate
Source and the Periodic Sync Src menus. For these reasons the trigger settings
commands are not qualified with the measurement name, the way the trigger source
commands are.
Trigger Source Notes:
– Video Trigger: When the detector selected for all active traces is the average
detector, the video signal for triggering does not include any VBW filtering.
– RF Burst: In some models, a variety of burst trigger circuitry is available, resulting
in various available burst trigger bandwidths. The analyzer automatically
Remote Language Compatibility Measurement Application Reference
366
3 RLC Mode & Swept SA Measurement
Trigger
chooses the appropriate trigger path based on the hardware configuration and
other settings of the analyzer. {E6630A}For E6630A, whether RF Burst trigger
works is dependent on MPA’s status. If MPA is used, the menu is enable and RF
Burst trigger is available; if MPA is unused, the menu will be blank and RF Burst
trigger is disable.{/E6630A}
– Periodic Timer:
– TV Trigger
The figure below shows the action of the periodic timer trigger. Before reviewing the
figure, we’ll explain some uses for the periodic trigger.
A common application is measuring periodic burst RF signals for which a trigger
signal is not easily available. For example, we might be measuring a TDMA radio
which bursts every 20 ms. Let’s assume that the 20 ms period is very consistent.
Let’s also assume that we do not have an external trigger source available that is
synchronized with the period, and that the signal-to-noise ratio of the signal is not
high enough to provide a clean RF burst trigger at all of the analysis frequencies. For
example, we might want to measure spurious transmissions at an offset from the
carrier that is larger than the bandwidth of the RF burst trigger. In this application,
we can set the Periodic Timer to a 20.00 ms period and adjust the offset from that
timer to position our trigger just where we want it. If we find that the 20.00 ms is not
exactly right, we can adjust the period slightly to minimize the drift between the
period timer and the signal to be measured.
A second way to use this feature would be to use Sync Source temporarily, instead
of Offset. In this case, we might tune to the signal in a narrow span and use the RF
Burst trigger to synchronize the periodic timer. Then we would turn the sync source
off so that it would not miss-trigger. Miss-triggering can occur when we are tuned so
far away from the RF burst trigger that it is no longer reliable.
A third example would be to synchronize to a signal that has a reference time
element of much longer period than the period of interest. In some CDMA
applications, it is useful to look at signals with a short periodicity, by synchronizing
that periodicity to the "even-second clock" edge that happens every two seconds.
Thus, we could connect the even-second clock trigger to Ext1 and use then Ext1 as
the sync source for the periodic timer.
The figure below illustrates this third example. The top trace represents the evensecond clock. It causes the periodic timer to synchronize with the leading edge
shown. The analyzer trigger occurs at a time delayed by the accumulated offset from
the period trigger event. The periodic timer continues to run, and triggers continue to
occur, with a periodicity determined by the analyzer time base. The timer output
(labeled "late event") will drift away from its ideal time due to imperfect matching
between the time base of the signal being measured and the time base of the
analyzer, and also because of imperfect setting of the period parameter. But the
synchronization is restored on the next even-second clock event. ("Accumulated
offset" is described in the in the Offset function section.)
367
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
– TV Trigger
Pressing this control, when it is not selected, selects the TV input signal as the
trigger.
Pressing this control, when it is already selected, opens a menu of TV Trigger setup
functions. The default active function in this menu is the TV line number on which you
want to trigger.
The Frame and Field options enable you to determine how the fields of the TV
picture signal will be affected by the trigger system. One complete TV image
consists of one frame of 525 or 625 horizontal lines depending on the TV standard
being used. Each frame is composed of two fields of interlacing lines, each consisting
of 262 1/2 lines (or 312 1/2 lines). The fields are called Field One and Field Two. Field
One is viewed as having 263 lines (or 313 lines) and Field Two is viewed as having
262 lines (or 312 lines).
For the 525 line NTSC video standard, we refer to TV lines as follows (these are the
Field Modes):
Entire Frame, lines 1 to 525
Field One, lines 1 to 263
Field Two, lines 1 to 262 (note that this really refers to "actual" lines 264 to 525)
For the 625 line PAL and SECAM video standards, we refer to TV lines as follows:
Entire Frame, lines 1 to 625
Field One, lines 1 to 313
Field Two, lines 314 to 625
As the Field is changed, the appropriate value for Line is chosen to keep triggering on
the same line as before, or if this is not possible, the corresponding line in the new
Field. For example, suppose line 264 is selected while in the NTSC-M standard and
the Entire Frame mode. This is the first line in Field Two. If Field Two is then selected,
the Line number changes to Line 1, the same actual line in the TV signal. If Field One
is then selected, the line number stays at 1, but now we are triggering in the first line
Remote Language Compatibility Measurement Application Reference
368
3 RLC Mode & Swept SA Measurement
Trigger
in Field One. The only exception to this is if we are on the last line of Field One and
change to Field Two. In this case, we go to the last line in Field Two.
Trigger Setup Parameters:
The following examples show trigger setup parameters using an external trigger
source.
Example 1 illustrates the trigger conditions with negative slope and no trigger occurs
during trigger Holdoff time.
Example 2 illustrates the trigger conditions with positive slope, trigger delay, and
auto trigger time.
Trigger Settings Diagram
The Trigger Settings Diagram lets you configure the Trigger system using a visual
utility.
369
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
Video
The Video trigger condition is met when the video signal at the left edge of the
graticule (the filtered and detected version of the input signal, including both RBW
and VBW filtering) crosses the video trigger level with the chosen slope.
Trigger Level
Sets the amplitude level for Trigger and Gate sources that use level triggering.
When the video signal crosses this level, with the chosen slope, the trigger occurs.
Trigger and Gate sources that use level triggering include:
– Video
– Level
– External 1|2
– I/Q Mag
– I (Demodulated)
– Q (Demodulated)
– Input I
– Input Q
– Aux Channel I/Q Mag
Remote Language Compatibility Measurement Application Reference
370
3 RLC Mode & Swept SA Measurement
Trigger
For any given Trigger, Gate, or Periodic Sync Src, the same Trigger Level is used for
the Trigger source in the Trigger menu, for the Gate source in the Gate Source menu,
and for the Periodic Sync source in the Periodic Sync Src menu.
If Video is the selected trigger source, the trigger level displays as a green horizontal
line with the label TRIG LVL just above it on the right:
If the value of trigger level is off screen low this line displays along the bottom of the
graticule. If the value of trigger level is off screen high this line displays above the
graticule but no farther above than 1.5 % of the graticule height (the same as the
trace itself). Note that the TRIG LVL label cannot display above the graticule so the
label itself stops at the top of the graticule.
For the I/Q Triggers, the I/Q reference impedance is used for converting between
power and voltage.
See "Trigger Level Parameters" on page 371.
See "More Information" on page 372
Command
:TRIGger
[:SEQuence]:EXTernal1|EXTernal2|VIDeo||LEVel|IQMag|IDEMod|QDEMod|
IINPut|QINPut|AIQMag:LEVel <ampl>
:TRIGger
[:SEQuence]:EXTernal1|EXTernal2|LEVel|VIDeo|IQMag|IDEMod|QDEMod|I
INPut|QINPut|AIQMag:LEVel?
Example
TRIG:VID:LEV -40 dBm
State
Saved
Saved in instrument state.
Backwards Compatibility
:TRIGger[:SEQuence]:IF:LEVel taken as video trigger level
:TRIGger[:SEQuence]:IF:LEVel? taken as video trigger level query
:TRIGger[:SEQuence]:EXTernal:LEVel the parameter EXTernal is mapped to
EXTernal1
:TRIGger[:SEQuence]:FRAMe:EXTernal1:LEVel
Trigger Level Parameters
371
Source
Example
Min
Max
Preset
Video
TRIG:VID:LEV -40 dBm
-170 dBm
+30 dBm
-25 dBm
Level
TRIG:LEV:LEV -40 dBm
-170 dBm
+30 dBm
-25 dBm
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
External 1|2
TRIG:EXT1:LEV 0.4 V
1.2 V
-5 V
5V
I/Q Mag
TRIG:IQM:LEV -30 dBm
-200 dBm
100 dBm
-25 dBm
I (Demod)
TRIG:IDEM:LEV 0.5 V
-1 V
1V
0.25 V
Q (Demod)
TRIG:QDEM:LEV 0.5 V
-1 V
1V
0.25 V
Input I
TRIG:IINP:LEV 0.5 V
-1 V
1V
0.25 V
Input Q
TRIG:QINP:LEV 0.5 V
-1 V
1V
0.25 V
Aux Chan I/Q Mag
TRIG:AIQM:LEV -30 dBm
-200 dBm
100 dBm
-25 dBm
More Information
For Video Trigger Level, when sweep type = FFT, the video trigger uses the
amplitude envelope in a bandwidth wider than the FFT width as a trigger source.
This might often be useful, but does not have the same relationship between the
displayed trace and the trigger level as in swept triggering.
For Video Trigger Level the settable resolution of the function is 0.01 dB, even
when the Y Axis Unit is linear. In Linear Y Axis Unit (for example, Volts) this requires
4 significant digits to display on the control.
Trigger Delay
Controls a time delay that the analyzer will wait to begin a sweep after meeting the
trigger criterion.
Command
:TRIGger[:SEQuence]:LEVel:DELay <time>
:TRIGger[:SEQuence]:LEVel:DELay?
:TRIGger[:SEQuence]:LEVel:DELay:STATe OFF|ON|0|1
:TRIGger[:SEQuence]:LEVel:DELay:STATe?
Example
TRIG:LEV:DEL:STAT ON
TRIG:LEV:DEL 100 ms
Preset
30.01 ms
OFF
Min/Max
0 ms /70 sec (but dependent on Acq Time like FMT)
State Saved
Saved in instrument state.
Notes
Level trigger delay may not be set to negative values. Negative settings of Level
Trig Delay are treated as a zero setting within the internal hardware.
Trigger Slope
Sets the trigger polarity for Trigger and Gate sources that support Trigger Slope. It is
set positive to trigger on a rising edge and negative to trigger on a falling edge.
Remote Language Compatibility Measurement Application Reference
372
3 RLC Mode & Swept SA Measurement
Trigger
Trigger and Gate sources that support Trigger Slope include:
– Video
– Line
– External 1|2
– RF Burst
– I/Q Mag
– I (Demodulated)
– Q (Demodulated)
– Input I
– Input Q
– Aux Channel I/Q Mag
For any given Trigger, Gate, or Periodic Sync source, the same Trigger Slope is used
for the Trigger source in the Trigger menu, for the Gate source in the Gate Source
menu, and for the Periodic Sync source in the Periodic Sync Src menu.
See "Trig Delay Parameters" on page 374
See "More Information" on page 375
Command
:TRIGger
[:SEQuence]:LINE|EXTernal1|EXTernal2|VIDeo|RFBurst|IQMag|IDEMod|QD
EMod|IINPut|QINPut|AIQMag:SLOPe POSitive|NEGative
:TRIGger
[:SEQuence]:LINE|EXTernal1|EXTernal2|VIDeo|RFBurst|IQMag|IDEMod|QD
EMod|IINPut|QINPut|AIQMag:SLOPe?
Example
TRIG:VID:SLOP NEG
TRIG:VID:SLOP?
TRIG:EXT1: SLOP NEG
TRIG:EXT2: SLOP POS
TRIG:LINE:SLOP NEG
Preset
POSitive
State
Saved
Saved in instrument state.
Dependencies
Only appears when Video, Line, External 1|2, RF Burst trigger is selected as the
Trigger Source
Backwards Compatibility
373
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
In ESA/PSA, the Trigger Slope was global to all triggers. In the X-Series, the slope
can be set individually for each Trigger Source. For backward compatibility, the
global SLOPe command updates all instances of trigger slope (VID, LINE, EXT1,
EXT2, TV, RFB). The query returns the trigger slope setting of the currently selected
trigger source.
Command
:TRIGger[:SEQuence]:SLOPe POSitive|NEGative
:TRIGger[:SEQuence]:SLOPe?
Example
TRIG:SLOP NEG
Preset
POSitive
State Saved
Saved in instrument state.
Trig Delay Parameters
Source
Example
Preset
Min
Max
Video
TRIG:VID:DEL:STAT
ON
Off, 1
us
-150
ms
+500 ms
Off, 30
ms
0 ms
70 sec Off, 30
ms
0 ms
Off, 1
us
-150
ms
+500 ms
Off, 1
us
-150
ms
+500 ms
Off, 1
us
-150
ms
+500 ms
Off, 1
us
-150
ms
+500 ms
Off, 1
us
-2.5 s
+10 s
Off, 1
us
-2.5 s
+10 s
TRIG:VID:DEL 100 ms
Level
TRIG:LEV:DEL:STAT
ON
(but dependent on Acq Time
like FMT)
TRIG:LEV:DEL 100 ms
FMT
TRIG:FMT:DEL:STAT
ON
(but dependent on Acq Time
like FMT)
TRIG:FMT:DEL 100 ms
External 1|2
TRIG:EXT1:DEL:STAT
ON
70 sec TRIG:EXT2:DEL 100
ms
Line
TRIG:LINE:DEL:STAT
ON
TRIG:LINE:DEL 100 ms
RF Burst
TRIG:RFB:DEL:STAT
ON
TRIG:RFB:DEL 100 ms
Periodic Timer
TRIG:FRAM:DEL:STAT
ON
TRIG:FRAM:DEL 100
ms
I/Q Mag
TRIG:IQM:DEL:STAT
ON
TRIG:IQM:DEL 10 ms
I (Demod)
TRIG:IDEM:DEL:STAT
ON
TRIG:IDEM:DEL 10 ms
Remote Language Compatibility Measurement Application Reference
374
3 RLC Mode & Swept SA Measurement
Trigger
Q (Demod)
TRIG:QDEM:DEL:STAT
ON
Off, 1
us
-2.5 s
+10 s
Off, 1
us
-2.5 s
+10 s
Off, 1
us
-2.5 s
+10 s
Off, 1
us
-2.5 s
+10 s
TRIG:QDEM:DEL 10
ms
Input I
TRIG:IINP:DEL:STAT
ON
TRIG:IINP:DEL 10 ms
Input Q
TRIG:QINP:DEL:STAT
ON
TRIG:QINP:DEL 10 ms
Aux Chan I/Q
Mag
TRIG:AIQM:DEL:STAT
ON
TRIG:AIQM:DEL 10 ms
More Information
When FMT Trigger Criteria is INSIDE or OUTSIDE, FMT Trigger Delay State is forced
to OFF
FMT Trigger Delay MaxValue is dependent on the current AcquisitionTime. The
equation is: MaxValue = 2^16 x AcqTime, but never to exceed 70 sec. Ex: In PVT
View with a min PVT Acq Time of 200 us, this Trigger Delay MaxValue is 13.26 sec.
In RT Spectrum and Spectrogram with a min Acq Time of 100 us, this Trigger Delay
MaxValue is 6.55 sec. When the user increases the Acq Time, it will increase this
MaxValue.
FMT Trig Delay Diagram
375
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
Trigger Settings Diagram
The Trigger Settings Diagram lets you configure the Trigger system using a visual
utility.
Line
Selects the line signal as the trigger. A new sweep/measurement will start to
synchronize with the next cycle of the line voltage.
Select Trigger Source
The TRIG:SOURCe command specifies the trigger source for the currently selected
input (RF or I/Q). If you change inputs, the new input remembers the trigger source it
was last programmed to for the current measurement, and uses that trigger source.
When in External Mixing, the analyzer uses the RF trigger source.
See "Trigger Sources" on page 378.
Remote Language Compatibility Measurement Application Reference
376
3 RLC Mode & Swept SA Measurement
Trigger
See "Select Trigger Source" on page 376.
SCPI Commands not available in N9061C
Preset
IMM
Notes
Not all measurements have all the trigger sources available to them. Check the
trigger source documentation for your specific measurement to see what sources
are available.
Not all trigger sources are available for each input. See the RF Trigger Source and
I/Q Trigger Source commands for detailed information on which trigger sources are
available for each input.
Other trigger-related commands are found in the INITiate and ABORt SCPI
command subsystems.
*OPC should be used after requesting data. This will hold off any subsequent
changes to the selected trigger source, until after the sweep is completed and the
data is returned.
Available ranges and presets can vary from mode to mode.
RTSA FMT
The amplitude resolution of the Frequency Mask is coupled to the Scale/Division.
There are 256 vertical points therefore the amplitude resolution is computed using
the algorithm;
(10 * Scale/Div) / # Vertical Points
Dependencies
In some models, there is no second External input. In these models, the External 2
key is blanked and the EXTernal2 parameter will generate a “Hardware missing;
Not available for this model number” message.
RTSA
Level trigger is allowed in average detector mode.
When Level Trigger is the selected Trigger Source in the Spectrum measurement,
Spectrum minimum Acquisition Time is limited to the PVT minimum Acquisition
Time. If the Spectrum Acquisition Time changed as a result of going into Level
Trigger, a message is posted “Min Acq Time is 200 usec when Level Trigger is ON”.
When Level Trigger is no longer the selected Trigger Source, Spectrum minimum
Acquisition Time is restored.
RTSA FMT
If you were not in Free Run when you entered the FMT Setup View, you can change
Trigger Source to Free Run while in the editor. This will allow you to configure the
mask with a continually updating trace. When exiting FMT Setup View, the Trigger
Source will be changed back to FMT.
Couplings
377
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
RTSA FMT
A remote user can enter or access FMT data via :TRIGger[:SEQuence]:FMT
[1]|2:DATA
The upper and lower masks can have different freq/ampl pairs therefore subop
code 1 is for the upper mask and subop code 2 is for the lower mask.
Status Bits/OPC Dependencies
The Status Operation Register bit 5 "Waiting for Trigger" is set at the same time as
the Sweeping or Measuring bit is set. It is cleared when the trigger actually occurs
(that is, after the trigger event occurs and all the applicable trigger criteria have
been met). A corresponding pop-up message ("Waiting for trigger") is generated if
no trigger signal appears after approximately 2 sec. This message goes away when
a trigger signal appears.
Backwards Compatibility
In analyzers prior to the X-Series, the Average detector was not available when
Video triggering was on, and consequently, functions that set the detector to
average (such as Marker Noise or Band/Intvl Power) were not available when the
video trigger was on. Similarly, Video triggering was not available when the
detector was Average. In the X-Series, these restrictions are removed.
This backwards compatibility alias command is provided for ESA/PSA compatibility.
:TRIGger:SOURCe
Trigger Sources
Source
Example
Annotation
(Meas
Bar)
Notes
Free
Run
TRIG:SOUR
IMM
Free Run
Free run triggering occurs immediately after the sweep/measurement is initiated.
Level
TRIG:SOUR
LEV
Level
The Level trigger condition is met when the signal (the
filtered and detected version of the input signal,
including RBW filtering) crosses the trigger level.
FMT
The Level trigger condition is met when
RTSA
measurement
FMT
TRIG:SOUR
FMT
RTSA
measurement
Video
TRIG:SOUR
VID
Video
The Video trigger condition is met when the video
signal at the left edge of the graticule (the filtered and
detected version of the input signal, including both
RBW and VBW filtering) crosses the video trigger level
with the chosen slope.
Line
TRIG:SOUR
Line
When Line is selected a new sweep/measurement will
Remote Language Compatibility Measurement Application Reference
378
3 RLC Mode & Swept SA Measurement
Trigger
Source
Example
Annotation
(Meas
Bar)
LINE
External
1
TRIG:SOUR
EXT1
Notes
start synchronized with the next cycle of the line
voltage. Line trigger is not available when operating
from a "dc power source", for example, when the
instrument is powered from batteries.
External 1
A new sweep/measurement will start when the external
trigger condition is met using the external 1 input
connector on the rear panel.
Grayed out if Ext 1 is in use by Point Trigger in the
Source Setup menu.
Forced to Free Run if already selected and Point
Trigger is set to External 1.
External
2
TRIG:SOUR
EXT2
External 2
A new sweep/measurement will start when the external
trigger condition is met using the external 2 input
connector on the rear panel.
Grayed out if Ext 2 is in use by Point Trigger in the
Source Setup menu.
Forced to Free Run if already selected and Point
Trigger is set to External 2
RF
Burst
TRIG:SOUR
RFB
RF Burst
A new sweep/measurement will start when an RF burst
envelope signal is identified from the signal at the RF
Input connector.
Periodic
TRIG:SOUR
FRAM
Periodic
Uses a built-in periodic timer signal as the trigger.
Trigger occurrences are set by the Periodic Timer
parameter, which is modified by the Offset and Periodic
Sync Src.
Use this trigger when there a periodic signal but no
reliable signal on which to trigger. You can synchronize
the periodic signal with outside events (using the
Periodic Sync Src) to get closer to a reliable trigger
signal.
If you do not have a sync source selected (it is Off), then
the internal timer will not be synchronized with any
external timing events.
TV
TRIG:SOUR
TV
Swept SA
TV
For triggering on analog TV signals. A new sweep/measurement will start synchronized with the next
occurrence of the synchronizing pulse of the selected
TV line number.
The Trigger menus let you select the trigger source and trigger settings for a sweep
or measurement. In triggered operation (basically, any trigger source other than
Free Run), the analyzer will begin a sweep or measurement only when the selected
379
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
trigger conditions are met, generally when your trigger source signal meets the
specified trigger level and polarity requirements. (In FFT measurements, the trigger
controls when the data acquisition begins for FFT conversion.)
For each of the trigger sources, you may define a set of operational parameters or
settings which will be applied when that source is selected as the current trigger
source. Examples of these settings are Trigger Level, Trigger Delay, and Trigger
Slope. You may apply different settings for each source; so, for example, you could
have a Trigger Level of 1v for External 1 trigger and -10 dBm for Video trigger.
Once you have established the settings for a given trigger source, they generally will
remain unchanged for that trigger source as you go from measurement to
measurement within a Mode (although the settings can change as you go from Mode
to Mode). Furthermore, the trigger settings within a Mode are the same for the
Trigger menu, the Gate Source menu, and the Periodic Sync Src menu. That is, if Ext1
trigger level is set to 1v in the Trigger menu, it will appear as 1v in both the Gate
Source and the Periodic Sync Src menus. For these reasons the trigger settings
commands are not qualified with the measurement name, the way the trigger source
commands are.
Trigger Source Notes:
– Video Trigger: When the detector selected for all active traces is the average
detector, the video signal for triggering does not include any VBW filtering.
– RF Burst: In some models, a variety of burst trigger circuitry is available, resulting
in various available burst trigger bandwidths. The analyzer automatically
chooses the appropriate trigger path based on the hardware configuration and
other settings of the analyzer. {E6630A}For E6630A, whether RF Burst trigger
works is dependent on MPA’s status. If MPA is used, the menu is enable and RF
Burst trigger is available; if MPA is unused, the menu will be blank and RF Burst
trigger is disable.{/E6630A}
– Periodic Timer:
– TV Trigger
The figure below shows the action of the periodic timer trigger. Before reviewing the
figure, we’ll explain some uses for the periodic trigger.
A common application is measuring periodic burst RF signals for which a trigger
signal is not easily available. For example, we might be measuring a TDMA radio
which bursts every 20 ms. Let’s assume that the 20 ms period is very consistent.
Let’s also assume that we do not have an external trigger source available that is
synchronized with the period, and that the signal-to-noise ratio of the signal is not
high enough to provide a clean RF burst trigger at all of the analysis frequencies. For
example, we might want to measure spurious transmissions at an offset from the
carrier that is larger than the bandwidth of the RF burst trigger. In this application,
we can set the Periodic Timer to a 20.00 ms period and adjust the offset from that
timer to position our trigger just where we want it. If we find that the 20.00 ms is not
Remote Language Compatibility Measurement Application Reference
380
3 RLC Mode & Swept SA Measurement
Trigger
exactly right, we can adjust the period slightly to minimize the drift between the
period timer and the signal to be measured.
A second way to use this feature would be to use Sync Source temporarily, instead
of Offset. In this case, we might tune to the signal in a narrow span and use the RF
Burst trigger to synchronize the periodic timer. Then we would turn the sync source
off so that it would not miss-trigger. Miss-triggering can occur when we are tuned so
far away from the RF burst trigger that it is no longer reliable.
A third example would be to synchronize to a signal that has a reference time
element of much longer period than the period of interest. In some CDMA
applications, it is useful to look at signals with a short periodicity, by synchronizing
that periodicity to the "even-second clock" edge that happens every two seconds.
Thus, we could connect the even-second clock trigger to Ext1 and use then Ext1 as
the sync source for the periodic timer.
The figure below illustrates this third example. The top trace represents the evensecond clock. It causes the periodic timer to synchronize with the leading edge
shown. The analyzer trigger occurs at a time delayed by the accumulated offset from
the period trigger event. The periodic timer continues to run, and triggers continue to
occur, with a periodicity determined by the analyzer time base. The timer output
(labeled "late event") will drift away from its ideal time due to imperfect matching
between the time base of the signal being measured and the time base of the
analyzer, and also because of imperfect setting of the period parameter. But the
synchronization is restored on the next even-second clock event. ("Accumulated
offset" is described in the in the Offset function section.)
– TV Trigger
Pressing this control, when it is not selected, selects the TV input signal as the
trigger.
Pressing this control, when it is already selected, opens a menu of TV Trigger setup
functions. The default active function in this menu is the TV line number on which you
want to trigger.
The Frame and Field options enable you to determine how the fields of the TV picture
signal will be affected by the trigger system. One complete TV image consists of one
frame of 525 or 625 horizontal lines depending on the TV standard being used. Each
381
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
frame is composed of two fields of interlacing lines, each consisting of 262 1/2 lines
(or 312 1/2 lines). The fields are called Field One and Field Two. Field One is viewed
as having 263 lines (or 313 lines) and Field Two is viewed as having 262 lines (or 312
lines).
For the 525 line NTSC video standard, we refer to TV lines as follows (these are the
Field Modes):
Entire Frame, lines 1 to 525
Field One, lines 1 to 263
Field Two, lines 1 to 262 (note that this really refers to "actual" lines 264 to 525)
For the 625 line PAL and SECAM video standards, we refer to TV lines as follows:
Entire Frame, lines 1 to 625
Field One, lines 1 to 313
Field Two, lines 314 to 625
As the Field is changed, the appropriate value for Line is chosen to keep triggering on
the same line as before, or if this is not possible, the corresponding line in the new
Field. For example, suppose line 264 is selected while in the NTSC-M standard and
the Entire Frame mode. This is the first line in Field Two. If Field Two is then selected,
the Line number changes to Line 1, the same actual line in the TV signal. If Field One
is then selected, the line number stays at 1, but now we are triggering in the first line
in Field One. The only exception to this is if we are on the last line of Field One and
change to Field Two. In this case, we go to the last line in Field Two.
Trigger Setup Parameters:
The following examples show trigger setup parameters using an external trigger
source.
Example 1 illustrates the trigger conditions with negative slope and no trigger occurs
during trigger Holdoff time.
Example 2 illustrates the trigger conditions with positive slope, trigger delay, and
auto trigger time.
Remote Language Compatibility Measurement Application Reference
382
3 RLC Mode & Swept SA Measurement
Trigger
Trigger Delay
Controls a time delay that the analyzer will wait to begin a sweep after meeting the
trigger criterion.
Command
:TRIGger[:SEQuence]:LEVel:DELay <time>
:TRIGger[:SEQuence]:LEVel:DELay?
:TRIGger[:SEQuence]:LEVel:DELay:STATe OFF|ON|0|1
:TRIGger[:SEQuence]:LEVel:DELay:STATe?
Example
TRIG:LEV:DEL:STAT ON
TRIG:LEV:DEL 100 ms
Preset
30.01 ms
OFF
Min/Max
0 ms /70 sec (but dependent on Acq Time like FMT)
State Saved
Saved in instrument state.
Notes
Level trigger delay may not be set to negative values. Negative settings of Level
Trig Delay are treated as a zero setting within the internal hardware.
383
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
Trigger Slope
Sets the trigger polarity for Trigger and Gate sources that support Trigger Slope. It is
set positive to trigger on a rising edge and negative to trigger on a falling edge.
Trigger and Gate sources that support Trigger Slope include:
– Video
– Line
– External 1|2
– RF Burst
– I/Q Mag
– I (Demodulated)
– Q (Demodulated)
– Input I
– Input Q
– Aux Channel I/Q Mag
For any given Trigger, Gate, or Periodic Sync source, the same Trigger Slope is used
for the Trigger source in the Trigger menu, for the Gate source in the Gate Source
menu, and for the Periodic Sync source in the Periodic Sync Src menu.
See "Trig Delay Parameters" on page 385
See "More Information" on page 386
Command
:TRIGger
[:SEQuence]:LINE|EXTernal1|EXTernal2|VIDeo|RFBurst|IQMag|IDEMod|Q
DEMod|IINPut|QINPut|AIQMag:SLOPe POSitive|NEGative
Example
TRIG:VID:SLOP NEG
:TRIGger
[:SEQuence]:LINE|EXTernal1|EXTernal2|VIDeo|RFBurst|IQMag|IDEMod|Q
DEMod|IINPut|QINPut|AIQMag:SLOPe?
TRIG:VID:SLOP?
TRIG:EXT1: SLOP NEG
TRIG:EXT2: SLOP POS
TRIG:LINE:SLOP NEG
Preset
POSitive
State
Save-
Saved in instrument state.
Remote Language Compatibility Measurement Application Reference
384
3 RLC Mode & Swept SA Measurement
Trigger
d
Dependencies
Only appears when Video, Line, External 1|2, RF Burst trigger is selected as the
Trigger Source
Backwards Compatibility
In ESA/PSA, the Trigger Slope was global to all triggers. In the X-Series, the slope
can be set individually for each Trigger Source. For backward compatibility, the
global SLOPe command updates all instances of trigger slope (VID, LINE, EXT1,
EXT2, TV, RFB). The query returns the trigger slope setting of the currently selected
trigger source.
Command
:TRIGger[:SEQuence]:SLOPe POSitive|NEGative
:TRIGger[:SEQuence]:SLOPe?
Example
TRIG:SLOP NEG
Preset
POSitive
State Saved
Saved in instrument state.
Trig Delay Parameters
Source
Example
Preset
Min
Max
Video
TRIG:VID:DEL:STAT
ON
Off, 1
us
-150
ms
+500 ms
Off, 30
ms
0 ms
70 sec Off, 30
ms
0 ms
Off, 1
us
-150
ms
+500 ms
Off, 1
us
-150
ms
+500 ms
Off, 1
us
-150
ms
+500 ms
Off, 1
us
-150
ms
+500 ms
TRIG:VID:DEL 100 ms
Level
TRIG:LEV:DEL:STAT
ON
(but dependent on Acq Time
like FMT)
TRIG:LEV:DEL 100 ms
FMT
TRIG:FMT:DEL:STAT
ON
(but dependent on Acq Time
like FMT)
TRIG:FMT:DEL 100 ms
External 1|2
TRIG:EXT1:DEL:STAT
ON
70 sec TRIG:EXT2:DEL 100
ms
Line
TRIG:LINE:DEL:STAT
ON
TRIG:LINE:DEL 100 ms
RF Burst
TRIG:RFB:DEL:STAT
ON
TRIG:RFB:DEL 100 ms
Periodic Timer
TRIG:FRAM:DEL:STAT
ON
TRIG:FRAM:DEL 100
ms
385
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
I/Q Mag
TRIG:IQM:DEL:STAT
ON
Off, 1
us
-2.5 s
+10 s
Off, 1
us
-2.5 s
+10 s
Off, 1
us
-2.5 s
+10 s
Off, 1
us
-2.5 s
+10 s
Off, 1
us
-2.5 s
+10 s
Off, 1
us
-2.5 s
+10 s
TRIG:IQM:DEL 10 ms
I (Demod)
TRIG:IDEM:DEL:STAT
ON
TRIG:IDEM:DEL 10 ms
Q (Demod)
TRIG:QDEM:DEL:STAT
ON
TRIG:QDEM:DEL 10
ms
Input I
TRIG:IINP:DEL:STAT
ON
TRIG:IINP:DEL 10 ms
Input Q
TRIG:QINP:DEL:STAT
ON
TRIG:QINP:DEL 10 ms
Aux Chan I/Q
Mag
TRIG:AIQM:DEL:STAT
ON
TRIG:AIQM:DEL 10 ms
More Information
When FMT Trigger Criteria is INSIDE or OUTSIDE, FMT Trigger Delay State is forced
to OFF
FMT Trigger Delay MaxValue is dependent on the current AcquisitionTime. The
equation is: MaxValue = 2^16 x AcqTime, but never to exceed 70 sec. Ex: In PVT
View with a min PVT Acq Time of 200 us, this Trigger Delay MaxValue is 13.26 sec.
In RT Spectrum and Spectrogram with a min Acq Time of 100 us, this Trigger Delay
MaxValue is 6.55 sec. When the user increases the Acq Time, it will increase this
MaxValue.
FMT Trig Delay Diagram
Remote Language Compatibility Measurement Application Reference
386
3 RLC Mode & Swept SA Measurement
Trigger
Trigger Settings Diagram
The Trigger Settings Diagram lets you configure the Trigger system using a visual
utility.
387
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
External 1/2
A new sweep/measurement will start when the external trigger condition is met
using the external 1 or 2 input connector on the rear panel.
Select Trigger Source
The TRIG:SOURCe command specifies the trigger source for the currently selected
input (RF or I/Q). If you change inputs, the new input remembers the trigger source it
was last programmed to for the current measurement, and uses that trigger source.
When in External Mixing, the analyzer uses the RF trigger source.
See "Trigger Sources" on page 389.
See "Select Trigger Source" on page 388.
SCPI Commands not available in N9061C
Preset
IMM
Notes
Not all measurements have all the trigger sources available to them. Check the
trigger source documentation for your specific measurement to see what sources
are available.
Not all trigger sources are available for each input. See the RF Trigger Source and
I/Q Trigger Source commands for detailed information on which trigger sources are
available for each input.
Other trigger-related commands are found in the INITiate and ABORt SCPI
command subsystems.
*OPC should be used after requesting data. This will hold off any subsequent
changes to the selected trigger source, until after the sweep is completed and the
data is returned.
Available ranges and presets can vary from mode to mode.
RTSA FMT
The amplitude resolution of the Frequency Mask is coupled to the Scale/Division.
There are 256 vertical points therefore the amplitude resolution is computed using
the algorithm;
(10 * Scale/Div) / # Vertical Points
Dependencies
In some models, there is no second External input. In these models, the External 2
key is blanked and the EXTernal2 parameter will generate a “Hardware missing;
Not available for this model number” message.
RTSA
Level trigger is allowed in average detector mode.
Remote Language Compatibility Measurement Application Reference
388
3 RLC Mode & Swept SA Measurement
Trigger
When Level Trigger is the selected Trigger Source in the Spectrum measurement,
Spectrum minimum Acquisition Time is limited to the PVT minimum Acquisition
Time. If the Spectrum Acquisition Time changed as a result of going into Level
Trigger, a message is posted “Min Acq Time is 200 usec when Level Trigger is ON”.
When Level Trigger is no longer the selected Trigger Source, Spectrum minimum
Acquisition Time is restored.
RTSA FMT
If you were not in Free Run when you entered the FMT Setup View, you can change
Trigger Source to Free Run while in the editor. This will allow you to configure the
mask with a continually updating trace. When exiting FMT Setup View, the Trigger
Source will be changed back to FMT.
Couplings
RTSA FMT
A remote user can enter or access FMT data via :TRIGger[:SEQuence]:FMT
[1]|2:DATA
The upper and lower masks can have different freq/ampl pairs therefore subop
code 1 is for the upper mask and subop code 2 is for the lower mask.
Status Bits/OPC Dependencies
The Status Operation Register bit 5 "Waiting for Trigger" is set at the same time as
the Sweeping or Measuring bit is set. It is cleared when the trigger actually occurs
(that is, after the trigger event occurs and all the applicable trigger criteria have
been met). A corresponding pop-up message ("Waiting for trigger") is generated if
no trigger signal appears after approximately 2 sec. This message goes away when
a trigger signal appears.
Backwards Compatibility
In analyzers prior to the X-Series, the Average detector was not available when
Video triggering was on, and consequently, functions that set the detector to
average (such as Marker Noise or Band/Intvl Power) were not available when the
video trigger was on. Similarly, Video triggering was not available when the
detector was Average. In the X-Series, these restrictions are removed.
This backwards compatibility alias command is provided for ESA/PSA compatibility.
:TRIGger:SOURCe
Trigger Sources
Source
Example
Annotation
(Meas
Bar)
Notes
Free
Run
TRIG:SOUR
IMM
Free Run
Free run triggering occurs immediately after the sweep/measurement is initiated.
Level
TRIG:SOUR
LEV
Level
The Level trigger condition is met when the signal (the
filtered and detected version of the input signal,
including RBW filtering) crosses the trigger level.
RTSA
measurement
389
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
Source
Example
Annotation
(Meas
Bar)
Notes
FMT
TRIG:SOUR
FMT
FMT
The Level trigger condition is met when
RTSA
measurement
Video
TRIG:SOUR
VID
Video
The Video trigger condition is met when the video
signal at the left edge of the graticule (the filtered and
detected version of the input signal, including both
RBW and VBW filtering) crosses the video trigger level
with the chosen slope.
Line
TRIG:SOUR
LINE
Line
When Line is selected a new sweep/measurement will
start synchronized with the next cycle of the line
voltage. Line trigger is not available when operating
from a "dc power source", for example, when the
instrument is powered from batteries.
External
1
TRIG:SOUR
EXT1
External 1
A new sweep/measurement will start when the external
trigger condition is met using the external 1 input
connector on the rear panel.
Grayed out if Ext 1 is in use by Point Trigger in the
Source Setup menu.
Forced to Free Run if already selected and Point Trigger
is set to External 1.
External
2
TRIG:SOUR
EXT2
External 2
A new sweep/measurement will start when the external
trigger condition is met using the external 2 input
connector on the rear panel.
Grayed out if Ext 2 is in use by Point Trigger in the
Source Setup menu.
Forced to Free Run if already selected and Point Trigger
is set to External 2
RF
Burst
TRIG:SOUR
RFB
RF Burst
A new sweep/measurement will start when an RF burst
envelope signal is identified from the signal at the RF
Input connector.
Periodic
TRIG:SOUR
FRAM
Periodic
Uses a built-in periodic timer signal as the trigger.
Trigger occurrences are set by the Periodic Timer
parameter, which is modified by the Offset and Periodic
Sync Src.
Use this trigger when there a periodic signal but no
reliable signal on which to trigger. You can synchronize
the periodic signal with outside events (using the
Periodic Sync Src) to get closer to a reliable trigger
signal.
If you do not have a sync source selected (it is Off), then
Remote Language Compatibility Measurement Application Reference
390
3 RLC Mode & Swept SA Measurement
Trigger
Source
Example
Annotation
(Meas
Bar)
Notes
the internal timer will not be synchronized with any
external timing events.
TV
TRIG:SOUR
TV
Swept SA
TV
For triggering on analog TV signals. A new sweep/measurement will start synchronized with the next
occurrence of the synchronizing pulse of the selected
TV line number.
The Trigger menus let you select the trigger source and trigger settings for a sweep
or measurement. In triggered operation (basically, any trigger source other than
Free Run), the analyzer will begin a sweep or measurement only when the selected
trigger conditions are met, generally when your trigger source signal meets the
specified trigger level and polarity requirements. (In FFT measurements, the trigger
controls when the data acquisition begins for FFT conversion.)
For each of the trigger sources, you may define a set of operational parameters or
settings which will be applied when that source is selected as the current trigger
source. Examples of these settings are Trigger Level, Trigger Delay, and Trigger
Slope. You may apply different settings for each source; so, for example, you could
have a Trigger Level of 1v for External 1 trigger and -10 dBm for Video trigger.
Once you have established the settings for a given trigger source, they generally will
remain unchanged for that trigger source as you go from measurement to
measurement within a Mode (although the settings can change as you go from Mode
to Mode). Furthermore, the trigger settings within a Mode are the same for the
Trigger menu, the Gate Source menu, and the Periodic Sync Src menu. That is, if Ext1
trigger level is set to 1v in the Trigger menu, it will appear as 1v in both the Gate
Source and the Periodic Sync Src menus. For these reasons the trigger settings
commands are not qualified with the measurement name, the way the trigger source
commands are.
Trigger Source Notes:
– Video Trigger: When the detector selected for all active traces is the average
detector, the video signal for triggering does not include any VBW filtering.
– RF Burst: In some models, a variety of burst trigger circuitry is available, resulting
in various available burst trigger bandwidths. The analyzer automatically
chooses the appropriate trigger path based on the hardware configuration and
other settings of the analyzer. {E6630A}For E6630A, whether RF Burst trigger
works is dependent on MPA’s status. If MPA is used, the menu is enable and RF
Burst trigger is available; if MPA is unused, the menu will be blank and RF Burst
trigger is disable.{/E6630A}
391
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
– Periodic Timer:
– TV Trigger
The figure below shows the action of the periodic timer trigger. Before reviewing the
figure, we’ll explain some uses for the periodic trigger.
A common application is measuring periodic burst RF signals for which a trigger
signal is not easily available. For example, we might be measuring a TDMA radio
which bursts every 20 ms. Let’s assume that the 20 ms period is very consistent.
Let’s also assume that we do not have an external trigger source available that is
synchronized with the period, and that the signal-to-noise ratio of the signal is not
high enough to provide a clean RF burst trigger at all of the analysis frequencies. For
example, we might want to measure spurious transmissions at an offset from the
carrier that is larger than the bandwidth of the RF burst trigger. In this application,
we can set the Periodic Timer to a 20.00 ms period and adjust the offset from that
timer to position our trigger just where we want it. If we find that the 20.00 ms is not
exactly right, we can adjust the period slightly to minimize the drift between the
period timer and the signal to be measured.
A second way to use this feature would be to use Sync Source temporarily, instead
of Offset. In this case, we might tune to the signal in a narrow span and use the RF
Burst trigger to synchronize the periodic timer. Then we would turn the sync source
off so that it would not miss-trigger. Miss-triggering can occur when we are tuned so
far away from the RF burst trigger that it is no longer reliable.
A third example would be to synchronize to a signal that has a reference time
element of much longer period than the period of interest. In some CDMA
applications, it is useful to look at signals with a short periodicity, by synchronizing
that periodicity to the "even-second clock" edge that happens every two seconds.
Thus, we could connect the even-second clock trigger to Ext1 and use then Ext1 as
the sync source for the periodic timer.
The figure below illustrates this third example. The top trace represents the evensecond clock. It causes the periodic timer to synchronize with the leading edge
shown. The analyzer trigger occurs at a time delayed by the accumulated offset from
the period trigger event. The periodic timer continues to run, and triggers continue to
occur, with a periodicity determined by the analyzer time base. The timer output
(labeled "late event") will drift away from its ideal time due to imperfect matching
between the time base of the signal being measured and the time base of the
analyzer, and also because of imperfect setting of the period parameter. But the
synchronization is restored on the next even-second clock event. ("Accumulated
offset" is described in the in the Offset function section.)
Remote Language Compatibility Measurement Application Reference
392
3 RLC Mode & Swept SA Measurement
Trigger
– TV Trigger
Pressing this control, when it is not selected, selects the TV input signal as the
trigger.
Pressing this control, when it is already selected, opens a menu of TV Trigger setup
functions. The default active function in this menu is the TV line number on which you
want to trigger.
The Frame and Field options enable you to determine how the fields of the TV picture
signal will be affected by the trigger system. One complete TV image consists of one
frame of 525 or 625 horizontal lines depending on the TV standard being used. Each
frame is composed of two fields of interlacing lines, each consisting of 262 1/2 lines
(or 312 1/2 lines). The fields are called Field One and Field Two. Field One is viewed
as having 263 lines (or 313 lines) and Field Two is viewed as having 262 lines (or 312
lines).
For the 525 line NTSC video standard, we refer to TV lines as follows (these are the
Field Modes):
Entire Frame, lines 1 to 525
Field One, lines 1 to 263
Field Two, lines 1 to 262 (note that this really refers to "actual" lines 264 to 525)
For the 625 line PAL and SECAM video standards, we refer to TV lines as follows:
Entire Frame, lines 1 to 625
Field One, lines 1 to 313
Field Two, lines 314 to 625
As the Field is changed, the appropriate value for Line is chosen to keep triggering on
the same line as before, or if this is not possible, the corresponding line in the new
Field. For example, suppose line 264 is selected while in the NTSC-M standard and
the Entire Frame mode. This is the first line in Field Two. If Field Two is then selected,
the Line number changes to Line 1, the same actual line in the TV signal. If Field One
is then selected, the line number stays at 1, but now we are triggering in the first line
393
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
in Field One. The only exception to this is if we are on the last line of Field One and
change to Field Two. In this case, we go to the last line in Field Two.
Trigger Setup Parameters:
The following examples show trigger setup parameters using an external trigger
source.
Example 1 illustrates the trigger conditions with negative slope and no trigger occurs
during trigger Holdoff time.
Example 2 illustrates the trigger conditions with positive slope, trigger delay, and
auto trigger time.
Trigger Level
Sets a level for the signal trigger. This level is displayed as a horizontal line. When
the signal crosses this level, the trigger occurs.
For the Level trigger source, External Gain and Ref Level Offset modify the actual
trace data as it is taken and are taken into account by Trig Level.
Command
:TRIGger[:SEQuence]:LEVel:LEVel <ampl>
:TRIGger[:SEQuence]:LEVel:LEVel?
Example
TRIG:LEV:LEV -40 dBm
Preset
Sets the Trigger Level -25 dBm on Preset. When the Trigger Level becomes the active
function, if the value is off screen, set it to either the top or bottom of screen, depending
Remote Language Compatibility Measurement Application Reference
394
3 RLC Mode & Swept SA Measurement
Trigger
on which direction off screen it was.
Min/Max
–170 dBm /+30 dBm
State
Saved
Saved in instrument state.
Notes
The Level trigger uses the amplitude envelope in a bandwidth wider than the FFT
width as a trigger source.
External Gain and Ref Level Offset, modify the actual trace data as it is taken and
are taken into account by Trig Level.
Backwards Compatibility
:TRIGger[:SEQuence]:IF:LEVel
:TRIGger[:SEQuence]:IF:LEVel?
This alias is provided for backward compatibility with VSA/PSA comms apps.
Trigger Delay
Controls a time delay that the analyzer will wait to begin a sweep after meeting the
trigger criterion.
Command
:TRIGger[:SEQuence]:LEVel:DELay <time>
:TRIGger[:SEQuence]:LEVel:DELay?
:TRIGger[:SEQuence]:LEVel:DELay:STATe OFF|ON|0|1
:TRIGger[:SEQuence]:LEVel:DELay:STATe?
Example
TRIG:LEV:DEL:STAT ON
TRIG:LEV:DEL 100 ms
Preset
30.01 ms
OFF
Min/Max
0 ms /70 sec (but dependent on Acq Time like FMT)
State Saved
Saved in instrument state.
Notes
Level trigger delay may not be set to negative values. Negative settings of Level
Trig Delay are treated as a zero setting within the internal hardware.
Trigger Slope
Sets the trigger polarity for Trigger and Gate sources that support Trigger Slope. It is
set positive to trigger on a rising edge and negative to trigger on a falling edge.
Trigger and Gate sources that support Trigger Slope include:
395
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
– Video
– Line
– External 1|2
– RF Burst
– I/Q Mag
– I (Demodulated)
– Q (Demodulated)
– Input I
– Input Q
– Aux Channel I/Q Mag
For any given Trigger, Gate, or Periodic Sync source, the same Trigger Slope is used
for the Trigger source in the Trigger menu, for the Gate source in the Gate Source
menu, and for the Periodic Sync source in the Periodic Sync Src menu.
See "Trig Delay Parameters" on page 397
See "More Information" on page 398
Command
:TRIGger
[:SEQuence]:LINE|EXTernal1|EXTernal2|VIDeo|RFBurst|IQMag|IDEMod|Q
DEMod|IINPut|QINPut|AIQMag:SLOPe POSitive|NEGative
Example
TRIG:VID:SLOP NEG
:TRIGger
[:SEQuence]:LINE|EXTernal1|EXTernal2|VIDeo|RFBurst|IQMag|IDEMod|Q
DEMod|IINPut|QINPut|AIQMag:SLOPe?
TRIG:VID:SLOP?
TRIG:EXT1: SLOP NEG
TRIG:EXT2: SLOP POS
TRIG:LINE:SLOP NEG
Preset
POSitive
State
Saved
Saved in instrument state.
Dependencies
Only appears when Video, Line, External 1|2, RF Burst trigger is selected as the
Trigger Source
Remote Language Compatibility Measurement Application Reference
396
3 RLC Mode & Swept SA Measurement
Trigger
Backwards Compatibility
In ESA/PSA, the Trigger Slope was global to all triggers. In the X-Series, the slope
can be set individually for each Trigger Source. For backward compatibility, the
global SLOPe command updates all instances of trigger slope (VID, LINE, EXT1,
EXT2, TV, RFB). The query returns the trigger slope setting of the currently selected
trigger source.
Command
:TRIGger[:SEQuence]:SLOPe POSitive|NEGative
:TRIGger[:SEQuence]:SLOPe?
Example
TRIG:SLOP NEG
Preset
POSitive
State Saved
Saved in instrument state.
Trig Delay Parameters
Source
Example
Preset
Min
Max
Video
TRIG:VID:DEL:STAT
ON
Off, 1
us
-150
ms
+500 ms
Off, 30
ms
0 ms
70 sec Off, 30
ms
0 ms
Off, 1
us
-150
ms
+500 ms
Off, 1
us
-150
ms
+500 ms
Off, 1
us
-150
ms
+500 ms
Off, 1
us
-150
ms
+500 ms
Off, 1
us
-2.5 s
+10 s
Off, 1
us
-2.5 s
+10 s
TRIG:VID:DEL 100 ms
Level
TRIG:LEV:DEL:STAT
ON
(but dependent on Acq Time
like FMT)
TRIG:LEV:DEL 100 ms
FMT
TRIG:FMT:DEL:STAT
ON
(but dependent on Acq Time
like FMT)
TRIG:FMT:DEL 100 ms
External 1|2
TRIG:EXT1:DEL:STAT
ON
70 sec TRIG:EXT2:DEL 100
ms
Line
TRIG:LINE:DEL:STAT
ON
TRIG:LINE:DEL 100 ms
RF Burst
TRIG:RFB:DEL:STAT
ON
TRIG:RFB:DEL 100 ms
Periodic Timer
TRIG:FRAM:DEL:STAT
ON
TRIG:FRAM:DEL 100
ms
I/Q Mag
TRIG:IQM:DEL:STAT
ON
TRIG:IQM:DEL 10 ms
I (Demod)
TRIG:IDEM:DEL:STAT
ON
TRIG:IDEM:DEL 10 ms
397
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
Q (Demod)
TRIG:QDEM:DEL:STAT
ON
Off, 1
us
-2.5 s
+10 s
Off, 1
us
-2.5 s
+10 s
Off, 1
us
-2.5 s
+10 s
Off, 1
us
-2.5 s
+10 s
TRIG:QDEM:DEL 10
ms
Input I
TRIG:IINP:DEL:STAT
ON
TRIG:IINP:DEL 10 ms
Input Q
TRIG:QINP:DEL:STAT
ON
TRIG:QINP:DEL 10 ms
Aux Chan I/Q
Mag
TRIG:AIQM:DEL:STAT
ON
TRIG:AIQM:DEL 10 ms
More Information
When FMT Trigger Criteria is INSIDE or OUTSIDE, FMT Trigger Delay State is forced
to OFF
FMT Trigger Delay MaxValue is dependent on the current AcquisitionTime. The
equation is: MaxValue = 2^16 x AcqTime, but never to exceed 70 sec. Ex: In PVT
View with a min PVT Acq Time of 200 us, this Trigger Delay MaxValue is 13.26 sec.
In RT Spectrum and Spectrogram with a min Acq Time of 100 us, this Trigger Delay
MaxValue is 6.55 sec. When the user increases the Acq Time, it will increase this
MaxValue.
FMT Trig Delay Diagram
Remote Language Compatibility Measurement Application Reference
398
3 RLC Mode & Swept SA Measurement
Trigger
Trigger Settings Diagram
The Trigger Settings Diagram lets you configure the Trigger system using a visual
utility.
RF Burst
A new sweep/measurement will start when an RF burst envelope signal is identified
from the signal at the RF Input connector.
Select Trigger Source
The TRIG:SOURCe command specifies the trigger source for the currently selected
input (RF or I/Q). If you change inputs, the new input remembers the trigger source it
was last programmed to for the current measurement, and uses that trigger source.
When in External Mixing, the analyzer uses the RF trigger source.
See "Trigger Sources" on page 401.
See "Select Trigger Source" on page 399.
SCPI Commands not available in N9061C
Preset
IMM
Notes
Not all measurements have all the trigger sources available to them. Check the
trigger source documentation for your specific measurement to see what sources
are available.
399
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
Not all trigger sources are available for each input. See the RF Trigger Source and
I/Q Trigger Source commands for detailed information on which trigger sources are
available for each input.
Other trigger-related commands are found in the INITiate and ABORt SCPI
command subsystems.
*OPC should be used after requesting data. This will hold off any subsequent
changes to the selected trigger source, until after the sweep is completed and the
data is returned.
Available ranges and presets can vary from mode to mode.
RTSA FMT
The amplitude resolution of the Frequency Mask is coupled to the Scale/Division.
There are 256 vertical points therefore the amplitude resolution is computed using
the algorithm;
(10 * Scale/Div) / # Vertical Points
Dependencies
In some models, there is no second External input. In these models, the External 2
key is blanked and the EXTernal2 parameter will generate a “Hardware missing;
Not available for this model number” message.
RTSA
Level trigger is allowed in average detector mode.
When Level Trigger is the selected Trigger Source in the Spectrum measurement,
Spectrum minimum Acquisition Time is limited to the PVT minimum Acquisition
Time. If the Spectrum Acquisition Time changed as a result of going into Level
Trigger, a message is posted “Min Acq Time is 200 usec when Level Trigger is ON”.
When Level Trigger is no longer the selected Trigger Source, Spectrum minimum
Acquisition Time is restored.
RTSA FMT
If you were not in Free Run when you entered the FMT Setup View, you can change
Trigger Source to Free Run while in the editor. This will allow you to configure the
mask with a continually updating trace. When exiting FMT Setup View, the Trigger
Source will be changed back to FMT.
Couplings
RTSA FMT
A remote user can enter or access FMT data via :TRIGger[:SEQuence]:FMT
[1]|2:DATA
The upper and lower masks can have different freq/ampl pairs therefore subop
code 1 is for the upper mask and subop code 2 is for the lower mask.
Status Bits/OPC Dependencies
The Status Operation Register bit 5 "Waiting for Trigger" is set at the same time as
Remote Language Compatibility Measurement Application Reference
400
3 RLC Mode & Swept SA Measurement
Trigger
the Sweeping or Measuring bit is set. It is cleared when the trigger actually occurs
(that is, after the trigger event occurs and all the applicable trigger criteria have
been met). A corresponding pop-up message ("Waiting for trigger") is generated if
no trigger signal appears after approximately 2 sec. This message goes away when
a trigger signal appears.
Backwards Compatibility
In analyzers prior to the X-Series, the Average detector was not available when
Video triggering was on, and consequently, functions that set the detector to
average (such as Marker Noise or Band/Intvl Power) were not available when the
video trigger was on. Similarly, Video triggering was not available when the
detector was Average. In the X-Series, these restrictions are removed.
This backwards compatibility alias command is provided for ESA/PSA compatibility.
:TRIGger:SOURCe
Trigger Sources
Source
Example
Annotation
(Meas
Bar)
Notes
Free
Run
TRIG:SOUR
IMM
Free Run
Free run triggering occurs immediately after the sweep/measurement is initiated.
Level
TRIG:SOUR
LEV
Level
The Level trigger condition is met when the signal (the
filtered and detected version of the input signal,
including RBW filtering) crosses the trigger level.
FMT
The Level trigger condition is met when
RTSA
measurement
FMT
TRIG:SOUR
FMT
RTSA
measurement
Video
TRIG:SOUR
VID
Video
The Video trigger condition is met when the video
signal at the left edge of the graticule (the filtered and
detected version of the input signal, including both
RBW and VBW filtering) crosses the video trigger level
with the chosen slope.
Line
TRIG:SOUR
LINE
Line
When Line is selected a new sweep/measurement will
start synchronized with the next cycle of the line
voltage. Line trigger is not available when operating
from a "dc power source", for example, when the
instrument is powered from batteries.
External
1
TRIG:SOUR
EXT1
External 1
A new sweep/measurement will start when the external
trigger condition is met using the external 1 input
connector on the rear panel.
Grayed out if Ext 1 is in use by Point Trigger in the
Source Setup menu.
401
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
Source
Example
Annotation
(Meas
Bar)
Notes
Forced to Free Run if already selected and Point Trigger
is set to External 1.
External
2
TRIG:SOUR
EXT2
External 2
A new sweep/measurement will start when the external
trigger condition is met using the external 2 input
connector on the rear panel.
Grayed out if Ext 2 is in use by Point Trigger in the
Source Setup menu.
Forced to Free Run if already selected and Point Trigger
is set to External 2
RF
Burst
TRIG:SOUR
RFB
RF Burst
A new sweep/measurement will start when an RF burst
envelope signal is identified from the signal at the RF
Input connector.
Periodic
TRIG:SOUR
FRAM
Periodic
Uses a built-in periodic timer signal as the trigger.
Trigger occurrences are set by the Periodic Timer
parameter, which is modified by the Offset and Periodic
Sync Src.
Use this trigger when there a periodic signal but no
reliable signal on which to trigger. You can synchronize
the periodic signal with outside events (using the
Periodic Sync Src) to get closer to a reliable trigger
signal.
If you do not have a sync source selected (it is Off), then
the internal timer will not be synchronized with any
external timing events.
TV
TRIG:SOUR
TV
Swept SA
TV
For triggering on analog TV signals. A new sweep/measurement will start synchronized with the next
occurrence of the synchronizing pulse of the selected
TV line number.
The Trigger menus let you select the trigger source and trigger settings for a sweep
or measurement. In triggered operation (basically, any trigger source other than
Free Run), the analyzer will begin a sweep or measurement only when the selected
trigger conditions are met, generally when your trigger source signal meets the
specified trigger level and polarity requirements. (In FFT measurements, the trigger
controls when the data acquisition begins for FFT conversion.)
For each of the trigger sources, you may define a set of operational parameters or
settings which will be applied when that source is selected as the current trigger
source. Examples of these settings are Trigger Level, Trigger Delay, and Trigger
Slope. You may apply different settings for each source; so, for example, you could
have a Trigger Level of 1v for External 1 trigger and -10 dBm for Video trigger.
Remote Language Compatibility Measurement Application Reference
402
3 RLC Mode & Swept SA Measurement
Trigger
Once you have established the settings for a given trigger source, they generally will
remain unchanged for that trigger source as you go from measurement to
measurement within a Mode (although the settings can change as you go from Mode
to Mode). Furthermore, the trigger settings within a Mode are the same for the
Trigger menu, the Gate Source menu, and the Periodic Sync Src menu. That is, if Ext1
trigger level is set to 1v in the Trigger menu, it will appear as 1v in both the Gate
Source and the Periodic Sync Src menus. For these reasons the trigger settings
commands are not qualified with the measurement name, the way the trigger source
commands are.
Trigger Source Notes:
– Video Trigger: When the detector selected for all active traces is the average
detector, the video signal for triggering does not include any VBW filtering.
– RF Burst: In some models, a variety of burst trigger circuitry is available, resulting
in various available burst trigger bandwidths. The analyzer automatically
chooses the appropriate trigger path based on the hardware configuration and
other settings of the analyzer. {E6630A}For E6630A, whether RF Burst trigger
works is dependent on MPA’s status. If MPA is used, the menu is enable and RF
Burst trigger is available; if MPA is unused, the menu will be blank and RF Burst
trigger is disable.{/E6630A}
– Periodic Timer:
– TV Trigger
The figure below shows the action of the periodic timer trigger. Before reviewing the
figure, we’ll explain some uses for the periodic trigger.
A common application is measuring periodic burst RF signals for which a trigger
signal is not easily available. For example, we might be measuring a TDMA radio
which bursts every 20 ms. Let’s assume that the 20 ms period is very consistent.
Let’s also assume that we do not have an external trigger source available that is
synchronized with the period, and that the signal-to-noise ratio of the signal is not
high enough to provide a clean RF burst trigger at all of the analysis frequencies. For
example, we might want to measure spurious transmissions at an offset from the
carrier that is larger than the bandwidth of the RF burst trigger. In this application,
we can set the Periodic Timer to a 20.00 ms period and adjust the offset from that
timer to position our trigger just where we want it. If we find that the 20.00 ms is not
exactly right, we can adjust the period slightly to minimize the drift between the
period timer and the signal to be measured.
A second way to use this feature would be to use Sync Source temporarily, instead
of Offset. In this case, we might tune to the signal in a narrow span and use the RF
Burst trigger to synchronize the periodic timer. Then we would turn the sync source
off so that it would not miss-trigger. Miss-triggering can occur when we are tuned so
far away from the RF burst trigger that it is no longer reliable.
A third example would be to synchronize to a signal that has a reference time
element of much longer period than the period of interest. In some CDMA
403
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
applications, it is useful to look at signals with a short periodicity, by synchronizing
that periodicity to the "even-second clock" edge that happens every two seconds.
Thus, we could connect the even-second clock trigger to Ext1 and use then Ext1 as
the sync source for the periodic timer.
The figure below illustrates this third example. The top trace represents the evensecond clock. It causes the periodic timer to synchronize with the leading edge
shown. The analyzer trigger occurs at a time delayed by the accumulated offset from
the period trigger event. The periodic timer continues to run, and triggers continue to
occur, with a periodicity determined by the analyzer time base. The timer output
(labeled "late event") will drift away from its ideal time due to imperfect matching
between the time base of the signal being measured and the time base of the
analyzer, and also because of imperfect setting of the period parameter. But the
synchronization is restored on the next even-second clock event. ("Accumulated
offset" is described in the in the Offset function section.)
– TV Trigger
Pressing this control, when it is not selected, selects the TV input signal as the
trigger.
Pressing this control, when it is already selected, opens a menu of TV Trigger setup
functions. The default active function in this menu is the TV line number on which you
want to trigger.
The Frame and Field options enable you to determine how the fields of the TV
picture signal will be affected by the trigger system. One complete TV image
consists of one frame of 525 or 625 horizontal lines depending on the TV standard
being used. Each frame is composed of two fields of interlacing lines, each consisting
of 262 1/2 lines (or 312 1/2 lines). The fields are called Field One and Field Two. Field
One is viewed as having 263 lines (or 313 lines) and Field Two is viewed as having
262 lines (or 312 lines).
For the 525 line NTSC video standard, we refer to TV lines as follows (these are the
Field Modes):
Entire Frame, lines 1 to 525
Field One, lines 1 to 263
Remote Language Compatibility Measurement Application Reference
404
3 RLC Mode & Swept SA Measurement
Trigger
Field Two, lines 1 to 262 (note that this really refers to "actual" lines 264 to 525)
For the 625 line PAL and SECAM video standards, we refer to TV lines as follows:
Entire Frame, lines 1 to 625
Field One, lines 1 to 313
Field Two, lines 314 to 625
As the Field is changed, the appropriate value for Line is chosen to keep triggering on
the same line as before, or if this is not possible, the corresponding line in the new
Field. For example, suppose line 264 is selected while in the NTSC-M standard and
the Entire Frame mode. This is the first line in Field Two. If Field Two is then selected,
the Line number changes to Line 1, the same actual line in the TV signal. If Field One
is then selected, the line number stays at 1, but now we are triggering in the first line
in Field One. The only exception to this is if we are on the last line of Field One and
change to Field Two. In this case, we go to the last line in Field Two.
Trigger Setup Parameters:
The following examples show trigger setup parameters using an external trigger
source.
Example 1 illustrates the trigger conditions with negative slope and no trigger occurs
during trigger Holdoff time.
Example 2 illustrates the trigger conditions with positive slope, trigger delay, and
auto trigger time.
405
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
Absolute Trig Level
Sets the absolute trigger level for the RF burst envelope.
When using the External Mixing path, the Absolute Trigger Level is uncalibrated because
the factory default was set to accommodate the expected IF levels for the RF path.
Only appears when RF Burst is selected as the Trigger, Gate or Periodic Sync
Source.
Command
:TRIGger[:SEQuence]:RFBurst:LEVel:ABSolute <ampl>
:TRIGger[:SEQuence]:RFBurst:LEVel:ABSolute?
Example
TRIG:RFB:LEV:ABS 10 dBm
sets the trigger level of the RF burst envelope signal to the absolute level of 10 dBm.
Preset
–20 dBm
Min/Max
–200 dBm/100 dBm
State Saved
Saved in instrument state.
Couplings
This same level is used for the RF Burst trigger source in the Trigger menu, for the
RF Burst selection in the Gate Source menu, and also for the RF Burst selection in
the Periodic Sync Src menu.
Notes
Sending this command does not switch the setting from relative to absolute. To
switch it you need to send the command :TRIGger
[:SEQuence]:RFBurst:LEVel:TYPE.
Backwards Compatibility SCPI
:TRIGger[:SEQuence]:FRAMe:RFBurst:LEVel:ABSolute
Relative Trig Level
Sets the relative trigger level for the RF burst envelope.
In some models, the relative burst trigger function is implemented in hardware. In
other models, without the advanced triggering hardware required, the relative burst
trigger function is implemented in software in some measurements, and is
unavailable in other measurements.
When implemented in software, the relative RF Burst trigger function is
implemented as follows:
1. The measurement starts with the absolute RF Burst trigger setting. If it cannot
get a trigger with that level, auto trigger fires and the acquisition starts anyway.
After the acquisition, the measurement searches for the peak in the acquired
waveform and saves it.
2. Now, in the next cycle of the measurement, the measurement determines a new
absolute RF Burst level based on the peak value from the first measurement and
Remote Language Compatibility Measurement Application Reference
406
3 RLC Mode & Swept SA Measurement
Trigger
the Relative RF Burst Trigger Level (always 0 or negative dB) set by the user. The
following formula is used:
absolute RF Burst level = peak level of the previous acquisition + relative RF
Burst level
3. If the new absolute RF Burst level differs from the previous by more than 0.5 dB,
the new level is sent to the hardware; otherwise it is not updated (to avoid
slowing down the acquisition)
Steps 2 and 3 repeat for subsequent measurements.
SCPI command not available in N9061C.
Preset
-6 dB
Min/Max
-45 dB/0 dB
State Saved
Saved in instrument state.
Dependencies
This key is grayed out and Absolute Trigger Level selected if the required hardware
is not present in your analyzer and the current measurement does not support
Relative triggering.
Only appears when RF Burst is selected as the Trigger Source.
Couplings
This same level is used for the RF Burst trigger source in the Trigger menu, for the
RF Burst selection in the Gate Source menu, and also for the RF Burst selection in
the Periodic Sync Src menu.
Notes
Sending this command does not switch the setting from absolute to relative; to
switch it you need to send the :TRIGger[:SEQuence]:RFBurst:LEVel:TYPE
command, above.
The relative trigger level is not available in some measurements. In those
measurements the RELative parameter, and the :TRIGger
[:SEQuence]:RFBurst:LEVel:TYPE
command (above), will generate an error if sent.
Backwards Compatibility SCPI
:TRIGger[:SEQuence]:RFBurst:LEVel
This legacy command is aliased to :TRIGger[:SEQuence]:RFBurst:LEVel:RELative
because the PSA had ONLY relative burst triggering
Trigger Delay
Controls a time delay that the analyzer will wait to begin a sweep after meeting the
trigger criterion.
Command
407
:TRIGger[:SEQuence]:LEVel:DELay <time>
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
:TRIGger[:SEQuence]:LEVel:DELay?
:TRIGger[:SEQuence]:LEVel:DELay:STATe OFF|ON|0|1
:TRIGger[:SEQuence]:LEVel:DELay:STATe?
Example
TRIG:LEV:DEL:STAT ON
TRIG:LEV:DEL 100 ms
Preset
30.01 ms
OFF
Min/Max
0 ms /70 sec (but dependent on Acq Time like FMT)
State Saved
Saved in instrument state.
Notes
Level trigger delay may not be set to negative values. Negative settings of Level
Trig Delay are treated as a zero setting within the internal hardware.
Trigger Slope
Sets the trigger polarity for Trigger and Gate sources that support Trigger Slope. It is
set positive to trigger on a rising edge and negative to trigger on a falling edge.
Trigger and Gate sources that support Trigger Slope include:
– Video
– Line
– External 1|2
– RF Burst
– I/Q Mag
– I (Demodulated)
– Q (Demodulated)
– Input I
– Input Q
– Aux Channel I/Q Mag
For any given Trigger, Gate, or Periodic Sync source, the same Trigger Slope is used
for the Trigger source in the Trigger menu, for the Gate source in the Gate Source
menu, and for the Periodic Sync source in the Periodic Sync Src menu.
See "Trig Delay Parameters" on page 409
See "More Information" on page 410
Remote Language Compatibility Measurement Application Reference
408
3 RLC Mode & Swept SA Measurement
Trigger
Command
:TRIGger
[:SEQuence]:LINE|EXTernal1|EXTernal2|VIDeo|RFBurst|IQMag|IDEMod|QD
EMod|IINPut|QINPut|AIQMag:SLOPe POSitive|NEGative
:TRIGger
[:SEQuence]:LINE|EXTernal1|EXTernal2|VIDeo|RFBurst|IQMag|IDEMod|QD
EMod|IINPut|QINPut|AIQMag:SLOPe?
Example
TRIG:VID:SLOP NEG
TRIG:VID:SLOP?
TRIG:EXT1: SLOP NEG
TRIG:EXT2: SLOP POS
TRIG:LINE:SLOP NEG
Preset
POSitive
State
Saved
Saved in instrument state.
Dependencies
Only appears when Video, Line, External 1|2, RF Burst trigger is selected as the
Trigger Source
Backwards Compatibility
In ESA/PSA, the Trigger Slope was global to all triggers. In the X-Series, the slope
can be set individually for each Trigger Source. For backward compatibility, the
global SLOPe command updates all instances of trigger slope (VID, LINE, EXT1,
EXT2, TV, RFB). The query returns the trigger slope setting of the currently selected
trigger source.
Command
:TRIGger[:SEQuence]:SLOPe POSitive|NEGative
:TRIGger[:SEQuence]:SLOPe?
Example
TRIG:SLOP NEG
Preset
POSitive
State Saved
Saved in instrument state.
Trig Delay Parameters
Source
Example
Preset
Min
Max
Video
TRIG:VID:DEL:STAT
ON
Off, 1
us
-150
ms
+500 ms
Off, 30
ms
0 ms
70 sec Off, 30
ms
0 ms
TRIG:VID:DEL 100 ms
Level
TRIG:LEV:DEL:STAT
ON
(but dependent on Acq Time
like FMT)
TRIG:LEV:DEL 100 ms
FMT
TRIG:FMT:DEL:STAT
ON
TRIG:FMT:DEL 100 ms
409
70 sec (but dependent on Acq Time
like FMT)
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
External 1|2
TRIG:EXT1:DEL:STAT
ON
Off, 1
us
-150
ms
+500 ms
Off, 1
us
-150
ms
+500 ms
Off, 1
us
-150
ms
+500 ms
Off, 1
us
-150
ms
+500 ms
Off, 1
us
-2.5 s
+10 s
Off, 1
us
-2.5 s
+10 s
Off, 1
us
-2.5 s
+10 s
Off, 1
us
-2.5 s
+10 s
Off, 1
us
-2.5 s
+10 s
Off, 1
us
-2.5 s
+10 s
TRIG:EXT2:DEL 100
ms
Line
TRIG:LINE:DEL:STAT
ON
TRIG:LINE:DEL 100 ms
RF Burst
TRIG:RFB:DEL:STAT
ON
TRIG:RFB:DEL 100 ms
Periodic Timer
TRIG:FRAM:DEL:STAT
ON
TRIG:FRAM:DEL 100
ms
I/Q Mag
TRIG:IQM:DEL:STAT
ON
TRIG:IQM:DEL 10 ms
I (Demod)
TRIG:IDEM:DEL:STAT
ON
TRIG:IDEM:DEL 10 ms
Q (Demod)
TRIG:QDEM:DEL:STAT
ON
TRIG:QDEM:DEL 10
ms
Input I
TRIG:IINP:DEL:STAT
ON
TRIG:IINP:DEL 10 ms
Input Q
TRIG:QINP:DEL:STAT
ON
TRIG:QINP:DEL 10 ms
Aux Chan I/Q
Mag
TRIG:AIQM:DEL:STAT
ON
TRIG:AIQM:DEL 10 ms
More Information
When FMT Trigger Criteria is INSIDE or OUTSIDE, FMT Trigger Delay State is forced
to OFF
FMT Trigger Delay MaxValue is dependent on the current AcquisitionTime. The
equation is: MaxValue = 2^16 x AcqTime, but never to exceed 70 sec. Ex: In PVT
View with a min PVT Acq Time of 200 us, this Trigger Delay MaxValue is 13.26 sec.
In RT Spectrum and Spectrogram with a min Acq Time of 100 us, this Trigger Delay
MaxValue is 6.55 sec. When the user increases the Acq Time, it will increase this
MaxValue.
FMT Trig Delay Diagram
Remote Language Compatibility Measurement Application Reference
410
3 RLC Mode & Swept SA Measurement
Trigger
Trigger Settings Diagram
The Trigger Settings Diagram lets you configure the Trigger system using a visual
utility.
411
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
Periodic
Uses a built-in periodic timer signal as the trigger. Trigger occurrences are set by the
Periodic Timer parameter, which is modified by the Offset and Periodic Sync Src.
Use this trigger when there a periodic signal but no reliable signal on which to
trigger. You can synchronize the periodic signal with outside events (using the
Periodic Sync Src) to get closer to a reliable trigger signal.
If you do not have a sync source selected (it is Off), then the internal timer will not be
synchronized with any external timing events.
Select Trigger Source
The TRIG:SOURCe command specifies the trigger source for the currently selected
input (RF or I/Q). If you change inputs, the new input remembers the trigger source it
was last programmed to for the current measurement, and uses that trigger source.
When in External Mixing, the analyzer uses the RF trigger source.
See "Trigger Sources" on page 413.
See "Select Trigger Source" on page 412.
SCPI Commands not available in N9061C
Preset
IMM
Notes
Not all measurements have all the trigger sources available to them. Check the
trigger source documentation for your specific measurement to see what sources
are available.
Not all trigger sources are available for each input. See the RF Trigger Source and
I/Q Trigger Source commands for detailed information on which trigger sources are
available for each input.
Other trigger-related commands are found in the INITiate and ABORt SCPI
command subsystems.
*OPC should be used after requesting data. This will hold off any subsequent
changes to the selected trigger source, until after the sweep is completed and the
data is returned.
Available ranges and presets can vary from mode to mode.
RTSA FMT
The amplitude resolution of the Frequency Mask is coupled to the Scale/Division.
There are 256 vertical points therefore the amplitude resolution is computed using
the algorithm;
(10 * Scale/Div) / # Vertical Points
Dependencies
In some models, there is no second External input. In these models, the External 2
Remote Language Compatibility Measurement Application Reference
412
3 RLC Mode & Swept SA Measurement
Trigger
key is blanked and the EXTernal2 parameter will generate a “Hardware missing;
Not available for this model number” message.
RTSA
Level trigger is allowed in average detector mode.
When Level Trigger is the selected Trigger Source in the Spectrum measurement,
Spectrum minimum Acquisition Time is limited to the PVT minimum Acquisition
Time. If the Spectrum Acquisition Time changed as a result of going into Level
Trigger, a message is posted “Min Acq Time is 200 usec when Level Trigger is ON”.
When Level Trigger is no longer the selected Trigger Source, Spectrum minimum
Acquisition Time is restored.
RTSA FMT
If you were not in Free Run when you entered the FMT Setup View, you can change
Trigger Source to Free Run while in the editor. This will allow you to configure the
mask with a continually updating trace. When exiting FMT Setup View, the Trigger
Source will be changed back to FMT.
Couplings
RTSA FMT
A remote user can enter or access FMT data via :TRIGger[:SEQuence]:FMT
[1]|2:DATA
The upper and lower masks can have different freq/ampl pairs therefore subop
code 1 is for the upper mask and subop code 2 is for the lower mask.
Status Bits/OPC Dependencies
The Status Operation Register bit 5 "Waiting for Trigger" is set at the same time as
the Sweeping or Measuring bit is set. It is cleared when the trigger actually occurs
(that is, after the trigger event occurs and all the applicable trigger criteria have
been met). A corresponding pop-up message ("Waiting for trigger") is generated if
no trigger signal appears after approximately 2 sec. This message goes away when
a trigger signal appears.
Backwards Compatibility
In analyzers prior to the X-Series, the Average detector was not available when
Video triggering was on, and consequently, functions that set the detector to
average (such as Marker Noise or Band/Intvl Power) were not available when the
video trigger was on. Similarly, Video triggering was not available when the
detector was Average. In the X-Series, these restrictions are removed.
This backwards compatibility alias command is provided for ESA/PSA compatibility.
:TRIGger:SOURCe
Trigger Sources
413
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
Source
Example
Annotation
(Meas
Bar)
Notes
Free
Run
TRIG:SOUR
IMM
Free Run
Free run triggering occurs immediately after the sweep/measurement is initiated.
Level
TRIG:SOUR
LEV
Level
The Level trigger condition is met when the signal (the
filtered and detected version of the input signal,
including RBW filtering) crosses the trigger level.
FMT
The Level trigger condition is met when
RTSA
measurement
FMT
TRIG:SOUR
FMT
RTSA
measurement
Video
TRIG:SOUR
VID
Video
The Video trigger condition is met when the video
signal at the left edge of the graticule (the filtered and
detected version of the input signal, including both
RBW and VBW filtering) crosses the video trigger level
with the chosen slope.
Line
TRIG:SOUR
LINE
Line
When Line is selected a new sweep/measurement will
start synchronized with the next cycle of the line
voltage. Line trigger is not available when operating
from a "dc power source", for example, when the
instrument is powered from batteries.
External
1
TRIG:SOUR
EXT1
External 1
A new sweep/measurement will start when the external
trigger condition is met using the external 1 input
connector on the rear panel.
Grayed out if Ext 1 is in use by Point Trigger in the
Source Setup menu.
Forced to Free Run if already selected and Point
Trigger is set to External 1.
External
2
TRIG:SOUR
EXT2
External 2
A new sweep/measurement will start when the external
trigger condition is met using the external 2 input
connector on the rear panel.
Grayed out if Ext 2 is in use by Point Trigger in the
Source Setup menu.
Forced to Free Run if already selected and Point
Trigger is set to External 2
RF
Burst
TRIG:SOUR
RFB
RF Burst
A new sweep/measurement will start when an RF burst
envelope signal is identified from the signal at the RF
Input connector.
Periodic
TRIG:SOUR
FRAM
Periodic
Uses a built-in periodic timer signal as the trigger.
Trigger occurrences are set by the Periodic Timer
parameter, which is modified by the Offset and Periodic
Remote Language Compatibility Measurement Application Reference
414
3 RLC Mode & Swept SA Measurement
Trigger
Source
Example
Annotation
(Meas
Bar)
Notes
Sync Src.
Use this trigger when there a periodic signal but no
reliable signal on which to trigger. You can synchronize
the periodic signal with outside events (using the
Periodic Sync Src) to get closer to a reliable trigger
signal.
If you do not have a sync source selected (it is Off), then
the internal timer will not be synchronized with any
external timing events.
TV
TRIG:SOUR
TV
Swept SA
TV
For triggering on analog TV signals. A new sweep/measurement will start synchronized with the next
occurrence of the synchronizing pulse of the selected
TV line number.
The Trigger menus let you select the trigger source and trigger settings for a sweep
or measurement. In triggered operation (basically, any trigger source other than
Free Run), the analyzer will begin a sweep or measurement only when the selected
trigger conditions are met, generally when your trigger source signal meets the
specified trigger level and polarity requirements. (In FFT measurements, the trigger
controls when the data acquisition begins for FFT conversion.)
For each of the trigger sources, you may define a set of operational parameters or
settings which will be applied when that source is selected as the current trigger
source. Examples of these settings are Trigger Level, Trigger Delay, and Trigger
Slope. You may apply different settings for each source; so, for example, you could
have a Trigger Level of 1v for External 1 trigger and -10 dBm for Video trigger.
Once you have established the settings for a given trigger source, they generally will
remain unchanged for that trigger source as you go from measurement to
measurement within a Mode (although the settings can change as you go from Mode
to Mode). Furthermore, the trigger settings within a Mode are the same for the
Trigger menu, the Gate Source menu, and the Periodic Sync Src menu. That is, if Ext1
trigger level is set to 1v in the Trigger menu, it will appear as 1v in both the Gate
Source and the Periodic Sync Src menus. For these reasons the trigger settings
commands are not qualified with the measurement name, the way the trigger source
commands are.
Trigger Source Notes:
– Video Trigger: When the detector selected for all active traces is the average
detector, the video signal for triggering does not include any VBW filtering.
– RF Burst: In some models, a variety of burst trigger circuitry is available, resulting
in various available burst trigger bandwidths. The analyzer automatically
415
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
chooses the appropriate trigger path based on the hardware configuration and
other settings of the analyzer. {E6630A}For E6630A, whether RF Burst trigger
works is dependent on MPA’s status. If MPA is used, the menu is enable and RF
Burst trigger is available; if MPA is unused, the menu will be blank and RF Burst
trigger is disable.{/E6630A}
– Periodic Timer:
– TV Trigger
The figure below shows the action of the periodic timer trigger. Before reviewing the
figure, we’ll explain some uses for the periodic trigger.
A common application is measuring periodic burst RF signals for which a trigger
signal is not easily available. For example, we might be measuring a TDMA radio
which bursts every 20 ms. Let’s assume that the 20 ms period is very consistent.
Let’s also assume that we do not have an external trigger source available that is
synchronized with the period, and that the signal-to-noise ratio of the signal is not
high enough to provide a clean RF burst trigger at all of the analysis frequencies. For
example, we might want to measure spurious transmissions at an offset from the
carrier that is larger than the bandwidth of the RF burst trigger. In this application,
we can set the Periodic Timer to a 20.00 ms period and adjust the offset from that
timer to position our trigger just where we want it. If we find that the 20.00 ms is not
exactly right, we can adjust the period slightly to minimize the drift between the
period timer and the signal to be measured.
A second way to use this feature would be to use Sync Source temporarily, instead
of Offset. In this case, we might tune to the signal in a narrow span and use the RF
Burst trigger to synchronize the periodic timer. Then we would turn the sync source
off so that it would not miss-trigger. Miss-triggering can occur when we are tuned so
far away from the RF burst trigger that it is no longer reliable.
A third example would be to synchronize to a signal that has a reference time
element of much longer period than the period of interest. In some CDMA
applications, it is useful to look at signals with a short periodicity, by synchronizing
that periodicity to the "even-second clock" edge that happens every two seconds.
Thus, we could connect the even-second clock trigger to Ext1 and use then Ext1 as
the sync source for the periodic timer.
The figure below illustrates this third example. The top trace represents the evensecond clock. It causes the periodic timer to synchronize with the leading edge
shown. The analyzer trigger occurs at a time delayed by the accumulated offset from
the period trigger event. The periodic timer continues to run, and triggers continue to
occur, with a periodicity determined by the analyzer time base. The timer output
(labeled "late event") will drift away from its ideal time due to imperfect matching
between the time base of the signal being measured and the time base of the
analyzer, and also because of imperfect setting of the period parameter. But the
synchronization is restored on the next even-second clock event. ("Accumulated
offset" is described in the in the Offset function section.)
Remote Language Compatibility Measurement Application Reference
416
3 RLC Mode & Swept SA Measurement
Trigger
– TV Trigger
Pressing this control, when it is not selected, selects the TV input signal as the
trigger.
Pressing this control, when it is already selected, opens a menu of TV Trigger setup
functions. The default active function in this menu is the TV line number on which you
want to trigger.
The Frame and Field options enable you to determine how the fields of the TV picture
signal will be affected by the trigger system. One complete TV image consists of one
frame of 525 or 625 horizontal lines depending on the TV standard being used. Each
frame is composed of two fields of interlacing lines, each consisting of 262 1/2 lines
(or 312 1/2 lines). The fields are called Field One and Field Two. Field One is viewed
as having 263 lines (or 313 lines) and Field Two is viewed as having 262 lines (or 312
lines).
For the 525 line NTSC video standard, we refer to TV lines as follows (these are the
Field Modes):
Entire Frame, lines 1 to 525
Field One, lines 1 to 263
Field Two, lines 1 to 262 (note that this really refers to "actual" lines 264 to 525)
For the 625 line PAL and SECAM video standards, we refer to TV lines as follows:
Entire Frame, lines 1 to 625
Field One, lines 1 to 313
Field Two, lines 314 to 625
As the Field is changed, the appropriate value for Line is chosen to keep triggering on
the same line as before, or if this is not possible, the corresponding line in the new
Field. For example, suppose line 264 is selected while in the NTSC-M standard and
the Entire Frame mode. This is the first line in Field Two. If Field Two is then selected,
the Line number changes to Line 1, the same actual line in the TV signal. If Field One
is then selected, the line number stays at 1, but now we are triggering in the first line
417
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
in Field One. The only exception to this is if we are on the last line of Field One and
change to Field Two. In this case, we go to the last line in Field Two.
Trigger Setup Parameters:
The following examples show trigger setup parameters using an external trigger
source.
Example 1 illustrates the trigger conditions with negative slope and no trigger occurs
during trigger Holdoff time.
Example 2 illustrates the trigger conditions with positive slope, trigger delay, and
auto trigger time.
Period
Sets the period of the internal periodic timer clock. For digital communications
signals, this is usually set to the frame period of your current input signal. In the case
that sync source is not set to OFF, and the external sync source rate is changed for
some reason, the periodic timer is synchronized at the every external
synchronization pulse by resetting the internal state of the timer circuit.
Only appears when Periodic Timer is selected as the Trigger or Gate Source
Command
:TRIGger[:SEQuence]:FRAMe:PERiod <time>
:TRIGger[:SEQuence]:FRAMe:PERiod?
Example
TRIG:FRAM:PER 100 ms
Remote Language Compatibility Measurement Application Reference
418
3 RLC Mode & Swept SA Measurement
Trigger
Preset
20 ms
Min/Max
100.000 ns/559.0000 ms
State Saved
Saved in instrument state.
Dependencies
The invalid data indicator turns on when the period is changed, until the next
sweep/measurement completes.
Couplings
The same period is used in the Gate Source selection of the period timer.
Offset
Adjusts the accumulated offset between the periodic timer events and the trigger
event. Adjusting the accumulated offset is different than setting an offset, and
requires explanation.
The periodic timer is usually not synchronized with any external events, so the timing
of its output events has no absolute meaning. Since the timing relative to external
events (RF signals) is important, you need to be able to adjust (offset) it. However,
you have no direct way to see when the periodic timer events occur. All that you can
see is the trigger timing. When you want to adjust the trigger timing, you will be
changing the internal offset between the periodic timer events and the trigger event.
Because the absolute value of that internal offset is unknown, we will just call that
the accumulated offset. Whenever the Offset parameter is changed, you are
changing that accumulated offset. You can reset the displayed offset using Reset
Offset Display. Changing the display does not change the value of the accumulated
offset, and you can still make additional changes to accumulated offset.
To avoid ambiguity, we define that an increase in the "offset" parameter, either from
the knob or the SCPI adjust command, serves to delay the timing of the trigger
event.
Only appears when Periodic Timer is selected as the Trigger or Gate Source.
Command
:TRIGger[:SEQuence]:FRAMe:OFFSet <time>
:TRIGger[:SEQuence]:FRAMe:OFFSet?
Example
TRIG:FRAM:OFFS 1.2 ms
Preset
0s
Min/Max
–10.000 s/10.000 s
State Saved
Saved in instrument state.
Notes
The front panel interface (for example, the knob), and this command, adjust the
accumulated offset, which is shown on the control.
419
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
However, the actual amount sent to the hardware each time the offset is updated
is the delta value, that is, the current accumulated offset value minus the previous
accumulated offset value. Note that the accumulated offset value is essentially
arbitrary; it represents the accumulated offset from the last time the offset was
zeroed (with the Reset Offset Display key).
Note that this command does not change the period of the trigger waveform. Note
also that Offset is used only when the sync source is set to OFF, otherwise delay is
used.
An increase in the "offset" parameter, either from the knob or the SCPI adjust
command, serves to delay the timing of the trigger event.
When the SCPI command is sent the value shown on the key is updated with the
new value. However, the actual amount sent to the hardware is the delta value,
that is, the current accumulated offset value minus the previous accumulated
offset value.
The SCPI query simply returns the value currently showing on the key.
Dependencies
The invalid data indicator turns on when the offset is changed, until the next
sweep/measurement completes.
Couplings
The same offset is used in the Gate Source selection of the period timer.
Reset Offset Display
Resets the value of the periodic trigger offset display setting to 0.0 seconds. The
current displayed trigger location may include an offset value defined with the Offset
key. Pressing this key redefines the currently displayed trigger location as the new
trigger point that is 0.0 s offset. The Offset key can then be used to add offset relative
to this new timing.
Only appears when Periodic Timer is selected as the Trigger or Gate Source
Command
:TRIGger[:SEQuence]:FRAMe:OFFSet:DISPlay:RESet
Example
TRIG:FRAM:OFFS:DISP:RES
Sync Source
For convenience you can select the Periodic Timer Sync Source using this dropdown.
You can also select it from the Periodic Sync Src tab, which also contains controls
that let you configure the Sync Source.
Remote Language Compatibility Measurement Application Reference
420
3 RLC Mode & Swept SA Measurement
Trigger
Selects a signal source for you to synchronize your periodic timer trigger to,
otherwise you are triggering at some arbitrary location in the frame. Synchronization
reduces the precision requirements on the setting of the period.
Only appears when Periodic Timer is selected as the Trigger or Gate Source.
TRIG:FRAM:SYNC EXT1
Example
TRIG:FRAM:SYNC EXT2
TRIG:FRAM:SYNC RFB
TRIG:FRAM:SYNC OFF
Preset
Off
State Saved
Saved in instrument state.
Trigger Delay
Controls a time delay that the analyzer will wait to begin a sweep after meeting the
trigger criterion.
Command
:TRIGger[:SEQuence]:LEVel:DELay <time>
:TRIGger[:SEQuence]:LEVel:DELay?
:TRIGger[:SEQuence]:LEVel:DELay:STATe OFF|ON|0|1
:TRIGger[:SEQuence]:LEVel:DELay:STATe?
Example
TRIG:LEV:DEL:STAT ON
TRIG:LEV:DEL 100 ms
Preset
30.01 ms
OFF
Min/Max
0 ms /70 sec (but dependent on Acq Time like FMT)
State Saved
Saved in instrument state.
Notes
Level trigger delay may not be set to negative values. Negative settings of Level
Trig Delay are treated as a zero setting within the internal hardware.
Trigger Setting Diagram
The Trigger Settings Diagram lets you configure the Trigger system using a visual
utility.
421
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
TV
For triggering on analog TV signals. A new sweep/measurement will start
synchronized with the next occurrence of the synchronizing pulse of the selected TV
line number.
This choice only appears in Modes that support TV Trigger.
TV Line
Selects the TV line number on which to trigger. Line number range is dependent on
the settings of the Standard and Field menus within the TV trigger setup functions.
When the line number is incremented beyond the upper limit, the value will change
to the lower limit and continue incrementing from there. When the line number is
decremented below the lower limit, the value will change to the upper limit and
continue decrementing from there.
Only appears when TV is selected as the Trigger Source.
SCPI Commands not available in N9061C
Preset
17
Min/Max
Min:1
The minimum value is the minimum line, and rolls over to the maximum value. The
minimum line number depends on which Field and standard are selected.
Max:
The maximum value is the maximum line, and rolls over to the minimum value. The
Remote Language Compatibility Measurement Application Reference
422
3 RLC Mode & Swept SA Measurement
Trigger
maximum line number depends on which Field and standard are selected.
Field 1 (ODD):
Maximum line is 263 for formats NTSC-M, NTSC-Japan, NTSC-4.43, PAL-M and PAL-60
Maximum line is 313 for formats PAL-B, D, G, H, I, PAL-N, PAL-N Combin, and SECAM-L
Field 2 (EVEN):
The maximum line 262 for formats NTSC-M, NTSC-Japan, NTSC-4.43, PAL-M and PAL-60
The maximum line is 312 for formats PAL-B, D, G, H, I, PAL-N, PAL-N Combin, and
SECAM-L
Field = Entire Frame:
525, for formats NTSC-M, NTSC-Japan, NTSC-4.43, PAL-M and PAL-60
625, for formats PAL-B, D, G, H, I, PAL-N, PAL-N Combin, and SECAM-L
State
Saved
Saved in instrument state.
Field
Selects the Field on which to trigger.
– ENTire Frame causes the selected line number to be viewed as an offset into the
entire frame starting with line 1, the first line in Field One.
– Field One (ODD) causes the selected line number to be viewed as an offset into
the first field starting with Line 1, the first line in Field One.
– Field Two (EVEN) causes the selected line number to be viewed as an offset into
the second field. If Line 1 is selected, it is the 264th line of the frame (NTSC-M,
NTSC-Japan, NTSC-4.43, PAL-M, PAL-60) or the 314th line of the frame (PALB,D,G,H,I, PAL-N, PAL-N-Combin, SECAM-L).
Only appears when TV is selected as the Trigger Source
SCPI Commands not available in N9061C
State Saved
Saved in instrument state.
Standard
Accesses the Standard menu keys which select from the following TV standards:
NTSC-M, NTSC-Japan, NTSC-4.43, PAL-M, PAL-B,D,G,H,I , PAL-N, PAL-N-Combin,
PAL-60, SECAM-L.
As the TV standard is changed, the current line value is clipped as necessary to keep
it valid for the chosen standard and field mode. For example, line 600 is selected in
Entire Frame mode in PAL-N; if NTSC-M is selected, the line number is clipped to
525. Or, if line 313 is selected in Field 1 mode in PAL-N and NTSC-M is selected, the
line number is clipped to 263. Changing back to the PAL-N standard will leave the
line number at 263.
Only appears when TV is selected as the Trigger Source.
423
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
SCPI Commands not available in N9061C
Preset
MNTS
Range
NTSC-M|NTSC-Japan|NTSC-4.43|PAL-M|PAL-N|PAL-N Combin|PAL-B,D,G,H,I|PAL60|SECAM-L
State
Saved
Saved in instrument state.
Trigger Setting Diagram
The Trigger Settings Diagram lets you configure the Trigger system using a visual
utility.
Gate Source Tab
The gate parameters differ depending on which source is selected.
Line
Select Gate Source
The menus under the Gate Source tab are the same as those under the Trigger tab,
with the exception that only the following Gate Sources are available:
Remote Language Compatibility Measurement Application Reference
424
3 RLC Mode & Swept SA Measurement
Trigger
– Line
– External 1|2
– RF Burst
– Periodic
Although the menus are the same as Trigger, a different SCPI command is used to
select the Gate Source because you may independently set the Gate Source and the
Trigger Source.
Any changes to the settings in the setup menus under each Gate Source selection
key (for example: Trigger Level, Trigger Delay, etc.) also affect the corresponding
settings under the Trigger menu keys. The gate system uses the Trigger SCPI
commands for the setup functions, since each setting affects both Gate and Trigger.
Example: to set the Trigger Level for External 1 Trigger you use the command
:TRIG:EXT1:LEV; to set the Trigger Level for External 1 Gate you use the same
command, :TRIG:EXT1:LEV
The menus under the Gate Source key are an exact duplicate of the Trigger menu,
with these exceptions:
– The Free Run and Video selections are not provided for Gate.
– The Trig Delay controls are not present
– Relative RF Burst Triggering is not available, just Absolute.
If SCPI is sent to the TRIG node to change or set the setup functions that are left out
of the Gate Source menus (Auto Trig, Holdoff, Trig Delay) it is accepted and the
values stored, but the values are not visible from the Gate Source menus.
For the selection of the gate source the SCPI node
:TRIGger[:SEQuence]:
is replaced by
[:SENSe]:SWEep:EGATe:
as shown in the remote command below.
Command
[:SENSe]:SWEep:EGATe:SOURce EXTernal1|EXTernal2
|LINE|FRAMe|RFBurst
[:SENSe]:SWEep:EGATe:SOURce?
Example
SWE:EGAT SOUR EXT1 SWE:EGAT:SOUR?
Preset
EXTernal 1
Dependencies
In some models, there is no second External input. In these models, the External 2
key is blanked and the EXTernal2 parameter will generate a “Hardware missing;
425
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
Not available for this model number” error.
Backwards Compatibility
In ESA, there is a single Gate input port. In PSA, the Gate Source may be taken from
one of two specified input ports. In the X-Series, five Trigger Sources can be Gate
Sources.
Trigger Slope
Sets the trigger polarity for Trigger and Gate sources that support Trigger Slope. It is
set positive to trigger on a rising edge and negative to trigger on a falling edge.
Trigger and Gate sources that support Trigger Slope include:
– Video
– Line
– External 1|2
– RF Burst
– I/Q Mag
– I (Demodulated)
– Q (Demodulated)
– Input I
– Input Q
– Aux Channel I/Q Mag
For any given Trigger, Gate, or Periodic Sync source, the same Trigger Slope is used
for the Trigger source in the Trigger menu, for the Gate source in the Gate Source
menu, and for the Periodic Sync source in the Periodic Sync Src menu.
See "Trig Delay Parameters" on page 427
See "More Information" on page 428
Command
:TRIGger
[:SEQuence]:LINE|EXTernal1|EXTernal2|VIDeo|RFBurst|IQMag|IDEMod|Q
DEMod|IINPut|QINPut|AIQMag:SLOPe POSitive|NEGative
Example
TRIG:VID:SLOP NEG
:TRIGger
[:SEQuence]:LINE|EXTernal1|EXTernal2|VIDeo|RFBurst|IQMag|IDEMod|Q
DEMod|IINPut|QINPut|AIQMag:SLOPe?
TRIG:VID:SLOP?
TRIG:EXT1: SLOP NEG
TRIG:EXT2: SLOP POS
TRIG:LINE:SLOP NEG
Remote Language Compatibility Measurement Application Reference
426
3 RLC Mode & Swept SA Measurement
Trigger
Preset
POSitive
State
Saved
Saved in instrument state.
Dependencies
Only appears when Video, Line, External 1|2, RF Burst trigger is selected as the
Trigger Source
Backwards Compatibility
In ESA/PSA, the Trigger Slope was global to all triggers. In the X-Series, the slope
can be set individually for each Trigger Source. For backward compatibility, the
global SLOPe command updates all instances of trigger slope (VID, LINE, EXT1,
EXT2, TV, RFB). The query returns the trigger slope setting of the currently selected
trigger source.
Command
:TRIGger[:SEQuence]:SLOPe POSitive|NEGative
:TRIGger[:SEQuence]:SLOPe?
Example
TRIG:SLOP NEG
Preset
POSitive
State Saved
Saved in instrument state.
Trig Delay Parameters
Source
Example
Preset
Min
Max
Video
TRIG:VID:DEL:STAT
ON
Off, 1
us
-150
ms
+500 ms
Off, 30
ms
0 ms
70 sec Off, 30
ms
0 ms
Off, 1
us
-150
ms
+500 ms
Off, 1
us
-150
ms
+500 ms
Off, 1
us
-150
ms
+500 ms
TRIG:VID:DEL 100 ms
Level
TRIG:LEV:DEL:STAT
ON
(but dependent on Acq Time
like FMT)
TRIG:LEV:DEL 100 ms
FMT
TRIG:FMT:DEL:STAT
ON
(but dependent on Acq Time
like FMT)
TRIG:FMT:DEL 100 ms
External 1|2
TRIG:EXT1:DEL:STAT
ON
70 sec TRIG:EXT2:DEL 100
ms
Line
TRIG:LINE:DEL:STAT
ON
TRIG:LINE:DEL 100 ms
RF Burst
427
TRIG:RFB:DEL:STAT
ON
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
TRIG:RFB:DEL 100 ms
Periodic Timer
TRIG:FRAM:DEL:STAT
ON
Off, 1
us
-150
ms
+500 ms
Off, 1
us
-2.5 s
+10 s
Off, 1
us
-2.5 s
+10 s
Off, 1
us
-2.5 s
+10 s
Off, 1
us
-2.5 s
+10 s
Off, 1
us
-2.5 s
+10 s
Off, 1
us
-2.5 s
+10 s
TRIG:FRAM:DEL 100
ms
I/Q Mag
TRIG:IQM:DEL:STAT
ON
TRIG:IQM:DEL 10 ms
I (Demod)
TRIG:IDEM:DEL:STAT
ON
TRIG:IDEM:DEL 10 ms
Q (Demod)
TRIG:QDEM:DEL:STAT
ON
TRIG:QDEM:DEL 10
ms
Input I
TRIG:IINP:DEL:STAT
ON
TRIG:IINP:DEL 10 ms
Input Q
TRIG:QINP:DEL:STAT
ON
TRIG:QINP:DEL 10 ms
Aux Chan I/Q
Mag
TRIG:AIQM:DEL:STAT
ON
TRIG:AIQM:DEL 10 ms
More Information
When FMT Trigger Criteria is INSIDE or OUTSIDE, FMT Trigger Delay State is forced
to OFF
FMT Trigger Delay MaxValue is dependent on the current AcquisitionTime. The
equation is: MaxValue = 2^16 x AcqTime, but never to exceed 70 sec. Ex: In PVT
View with a min PVT Acq Time of 200 us, this Trigger Delay MaxValue is 13.26 sec.
In RT Spectrum and Spectrogram with a min Acq Time of 100 us, this Trigger Delay
MaxValue is 6.55 sec. When the user increases the Acq Time, it will increase this
MaxValue.
FMT Trig Delay Diagram
Remote Language Compatibility Measurement Application Reference
428
3 RLC Mode & Swept SA Measurement
Trigger
Trigger Settings Diagram
The Trigger Settings Diagram lets you configure the Trigger system using a visual
utility.
429
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
Ext 1/2
Select Gate Source
The menus under the Gate Source tab are the same as those under the Trigger tab,
with the exception that only the following Gate Sources are available:
– Line
– External 1|2
– RF Burst
– Periodic
Although the menus are the same as Trigger, a different SCPI command is used to
select the Gate Source because you may independently set the Gate Source and the
Trigger Source.
Remote Language Compatibility Measurement Application Reference
430
3 RLC Mode & Swept SA Measurement
Trigger
Any changes to the settings in the setup menus under each Gate Source selection
key (for example: Trigger Level, Trigger Delay, etc.) also affect the corresponding
settings under the Trigger menu keys. The gate system uses the Trigger SCPI
commands for the setup functions, since each setting affects both Gate and Trigger.
Example: to set the Trigger Level for External 1 Trigger you use the command
:TRIG:EXT1:LEV; to set the Trigger Level for External 1 Gate you use the same
command, :TRIG:EXT1:LEV
The menus under the Gate Source key are an exact duplicate of the Trigger menu,
with these exceptions:
– The Free Run and Video selections are not provided for Gate.
– The Trig Delay controls are not present
– Relative RF Burst Triggering is not available, just Absolute.
If SCPI is sent to the TRIG node to change or set the setup functions that are left out
of the Gate Source menus (Auto Trig, Holdoff, Trig Delay) it is accepted and the
values stored, but the values are not visible from the Gate Source menus.
For the selection of the gate source the SCPI node
:TRIGger[:SEQuence]:
is replaced by
[:SENSe]:SWEep:EGATe:
as shown in the remote command below.
Command
[:SENSe]:SWEep:EGATe:SOURce EXTernal1|EXTernal2
|LINE|FRAMe|RFBurst
[:SENSe]:SWEep:EGATe:SOURce?
Example
SWE:EGAT SOUR EXT1 SWE:EGAT:SOUR?
Preset
EXTernal 1
Dependencies
In some models, there is no second External input. In these models, the External 2
key is blanked and the EXTernal2 parameter will generate a “Hardware missing;
Not available for this model number” error.
Backwards Compatibility
In ESA, there is a single Gate input port. In PSA, the Gate Source may be taken from
one of two specified input ports. In the X-Series, five Trigger Sources can be Gate
Sources.
Trigger Level
Sets the amplitude level for Trigger and Gate sources that use level triggering.
When the video signal crosses this level, with the chosen slope, the trigger occurs.
Trigger and Gate sources that use level triggering include:
431
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
– Video
– Level
– External 1|2
– I/Q Mag
– I (Demodulated)
– Q (Demodulated)
– Input I
– Input Q
– Aux Channel I/Q Mag
For any given Trigger, Gate, or Periodic Sync Src, the same Trigger Level is used for
the Trigger source in the Trigger menu, for the Gate source in the Gate Source menu,
and for the Periodic Sync source in the Periodic Sync Src menu.
If Video is the selected trigger source, the trigger level displays as a green horizontal
line with the label TRIG LVL just above it on the right:
If the value of trigger level is off screen low this line displays along the bottom of the
graticule. If the value of trigger level is off screen high this line displays above the
graticule but no farther above than 1.5 % of the graticule height (the same as the
trace itself). Note that the TRIG LVL label cannot display above the graticule so the
label itself stops at the top of the graticule.
For the I/Q Triggers, the I/Q reference impedance is used for converting between
power and voltage.
See "Trigger Level Parameters" on page 433.
See "More Information" on page 433
Command
:TRIGger
[:SEQuence]:EXTernal1|EXTernal2|VIDeo||LEVel|IQMag|IDEMod|QDEMod|
IINPut|QINPut|AIQMag:LEVel <ampl>
:TRIGger
[:SEQuence]:EXTernal1|EXTernal2|LEVel|VIDeo|IQMag|IDEMod|QDEMod|I
INPut|QINPut|AIQMag:LEVel?
Exam-
TRIG:VID:LEV -40 dBm
Remote Language Compatibility Measurement Application Reference
432
3 RLC Mode & Swept SA Measurement
Trigger
ple
State
Saved
Saved in instrument state.
Backwards Compatibility
:TRIGger[:SEQuence]:IF:LEVel taken as video trigger level
:TRIGger[:SEQuence]:IF:LEVel? taken as video trigger level query
:TRIGger[:SEQuence]:EXTernal:LEVel the parameter EXTernal is mapped to
EXTernal1
:TRIGger[:SEQuence]:FRAMe:EXTernal1:LEVel
Trigger Level Parameters
Source
Example
Min
Max
Preset
Video
TRIG:VID:LEV -40 dBm
-170 dBm
+30 dBm
-25 dBm
Level
TRIG:LEV:LEV -40 dBm
-170 dBm
+30 dBm
-25 dBm
External 1|2
TRIG:EXT1:LEV 0.4 V
1.2 V
-5 V
5V
I/Q Mag
TRIG:IQM:LEV -30 dBm
-200 dBm
100 dBm
-25 dBm
I (Demod)
TRIG:IDEM:LEV 0.5 V
-1 V
1V
0.25 V
Q (Demod)
TRIG:QDEM:LEV 0.5 V
-1 V
1V
0.25 V
Input I
TRIG:IINP:LEV 0.5 V
-1 V
1V
0.25 V
Input Q
TRIG:QINP:LEV 0.5 V
-1 V
1V
0.25 V
Aux Chan I/Q Mag
TRIG:AIQM:LEV -30 dBm
-200 dBm
100 dBm
-25 dBm
More Information
For Video Trigger Level, when sweep type = FFT, the video trigger uses the
amplitude envelope in a bandwidth wider than the FFT width as a trigger source.
This might often be useful, but does not have the same relationship between the
displayed trace and the trigger level as in swept triggering.
For Video Trigger Level the settable resolution of the function is 0.01 dB, even when
the Y Axis Unit is linear. In Linear Y Axis Unit (for example, Volts) this requires 4
significant digits to display on the control.
Trigger Slope
Sets the trigger polarity for Trigger and Gate sources that support Trigger Slope. It is
set positive to trigger on a rising edge and negative to trigger on a falling edge.
Trigger and Gate sources that support Trigger Slope include:
– Video
– Line
433
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
– External 1|2
– RF Burst
– I/Q Mag
– I (Demodulated)
– Q (Demodulated)
– Input I
– Input Q
– Aux Channel I/Q Mag
For any given Trigger, Gate, or Periodic Sync source, the same Trigger Slope is used
for the Trigger source in the Trigger menu, for the Gate source in the Gate Source
menu, and for the Periodic Sync source in the Periodic Sync Src menu.
See "Trig Delay Parameters" on page 435
See "More Information" on page 436
Command
:TRIGger
[:SEQuence]:LINE|EXTernal1|EXTernal2|VIDeo|RFBurst|IQMag|IDEMod|Q
DEMod|IINPut|QINPut|AIQMag:SLOPe POSitive|NEGative
Example
TRIG:VID:SLOP NEG
:TRIGger
[:SEQuence]:LINE|EXTernal1|EXTernal2|VIDeo|RFBurst|IQMag|IDEMod|Q
DEMod|IINPut|QINPut|AIQMag:SLOPe?
TRIG:VID:SLOP?
TRIG:EXT1: SLOP NEG
TRIG:EXT2: SLOP POS
TRIG:LINE:SLOP NEG
Preset
POSitive
State
Saved
Saved in instrument state.
Dependencies
Only appears when Video, Line, External 1|2, RF Burst trigger is selected as the
Trigger Source
Backwards Compatibility
In ESA/PSA, the Trigger Slope was global to all triggers. In the X-Series, the slope
can be set individually for each Trigger Source. For backward compatibility, the
Remote Language Compatibility Measurement Application Reference
434
3 RLC Mode & Swept SA Measurement
Trigger
global SLOPe command updates all instances of trigger slope (VID, LINE, EXT1,
EXT2, TV, RFB). The query returns the trigger slope setting of the currently selected
trigger source.
Command
:TRIGger[:SEQuence]:SLOPe POSitive|NEGative
:TRIGger[:SEQuence]:SLOPe?
Example
TRIG:SLOP NEG
Preset
POSitive
State Saved
Saved in instrument state.
Trig Delay Parameters
Source
Example
Preset
Min
Max
Video
TRIG:VID:DEL:STAT
ON
Off, 1
us
-150
ms
+500 ms
Off, 30
ms
0 ms
70 sec Off, 30
ms
0 ms
Off, 1
us
-150
ms
+500 ms
Off, 1
us
-150
ms
+500 ms
Off, 1
us
-150
ms
+500 ms
Off, 1
us
-150
ms
+500 ms
Off, 1
us
-2.5 s
+10 s
Off, 1
us
-2.5 s
+10 s
Off, 1
us
-2.5 s
+10 s
TRIG:VID:DEL 100 ms
Level
TRIG:LEV:DEL:STAT
ON
(but dependent on Acq Time
like FMT)
TRIG:LEV:DEL 100 ms
FMT
TRIG:FMT:DEL:STAT
ON
(but dependent on Acq Time
like FMT)
TRIG:FMT:DEL 100 ms
External 1|2
TRIG:EXT1:DEL:STAT
ON
70 sec TRIG:EXT2:DEL 100
ms
Line
TRIG:LINE:DEL:STAT
ON
TRIG:LINE:DEL 100 ms
RF Burst
TRIG:RFB:DEL:STAT
ON
TRIG:RFB:DEL 100 ms
Periodic Timer
TRIG:FRAM:DEL:STAT
ON
TRIG:FRAM:DEL 100
ms
I/Q Mag
TRIG:IQM:DEL:STAT
ON
TRIG:IQM:DEL 10 ms
I (Demod)
TRIG:IDEM:DEL:STAT
ON
TRIG:IDEM:DEL 10 ms
Q (Demod)
TRIG:QDEM:DEL:STAT
ON
TRIG:QDEM:DEL 10
435
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
ms
Input I
TRIG:IINP:DEL:STAT
ON
Off, 1
us
-2.5 s
+10 s
Off, 1
us
-2.5 s
+10 s
Off, 1
us
-2.5 s
+10 s
TRIG:IINP:DEL 10 ms
Input Q
TRIG:QINP:DEL:STAT
ON
TRIG:QINP:DEL 10 ms
Aux Chan I/Q
Mag
TRIG:AIQM:DEL:STAT
ON
TRIG:AIQM:DEL 10 ms
More Information
When FMT Trigger Criteria is INSIDE or OUTSIDE, FMT Trigger Delay State is forced
to OFF
FMT Trigger Delay MaxValue is dependent on the current AcquisitionTime. The
equation is: MaxValue = 2^16 x AcqTime, but never to exceed 70 sec. Ex: In PVT
View with a min PVT Acq Time of 200 us, this Trigger Delay MaxValue is 13.26 sec.
In RT Spectrum and Spectrogram with a min Acq Time of 100 us, this Trigger Delay
MaxValue is 6.55 sec. When the user increases the Acq Time, it will increase this
MaxValue.
FMT Trig Delay Diagram
Zero Span Delay Compensation
In zero span, there is a natural delay in the signal path, which comes from the RBW
filter. This is usually desirable, as it allows you to trigger on events and also see
those events, because the signal is delayed from the trigger event. However, in
Remote Language Compatibility Measurement Application Reference
436
3 RLC Mode & Swept SA Measurement
Trigger
some cases it is desirable to eliminate this delay, so that trigger events line up
exactly with the zero time point in zero span. You can use the Zero Span Delay Comp
On/Off feature to enable or disable zero span delay compensation.
Trigger and Gate sources that support Zero Span Delay Compensation include:
– External 1|2
– RF Burst
Command
:TRIGger
[:SEQuence]:EXTernal1|EXTernal2|RFBurst:DELay:COMPensation
OFF|ON|0|1 :TRIGger
[:SEQuence]:EXTernal1|EXTernal2|RFBurst:DELay:COMPensation?
Example
TRIG:EXT1:DEL:COMP ON
TRIG:EXT1:DEL:COMP?
TRIG:EXT2:DEL:COMP ON
TRIG:RFB:DEL:COMP ON
Preset
OFF
State
Saved
Saved in instrument state.
Trigger Settings Diagram
The Trigger Settings Diagram lets you configure the Trigger system using a visual
utility.
437
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
RF Burst
Select Gate Source
The menus under the Gate Source tab are the same as those under the Trigger tab,
with the exception that only the following Gate Sources are available:
– Line
– External 1|2
– RF Burst
– Periodic
Although the menus are the same as Trigger, a different SCPI command is used to
select the Gate Source because you may independently set the Gate Source and the
Trigger Source.
Remote Language Compatibility Measurement Application Reference
438
3 RLC Mode & Swept SA Measurement
Trigger
Any changes to the settings in the setup menus under each Gate Source selection
key (for example: Trigger Level, Trigger Delay, etc.) also affect the corresponding
settings under the Trigger menu keys. The gate system uses the Trigger SCPI
commands for the setup functions, since each setting affects both Gate and Trigger.
Example: to set the Trigger Level for External 1 Trigger you use the command
:TRIG:EXT1:LEV; to set the Trigger Level for External 1 Gate you use the same
command, :TRIG:EXT1:LEV
The menus under the Gate Source key are an exact duplicate of the Trigger menu,
with these exceptions:
– The Free Run and Video selections are not provided for Gate.
– The Trig Delay controls are not present
– Relative RF Burst Triggering is not available, just Absolute.
If SCPI is sent to the TRIG node to change or set the setup functions that are left out
of the Gate Source menus (Auto Trig, Holdoff, Trig Delay) it is accepted and the
values stored, but the values are not visible from the Gate Source menus.
For the selection of the gate source the SCPI node
:TRIGger[:SEQuence]:
is replaced by
[:SENSe]:SWEep:EGATe:
as shown in the remote command below.
Command
[:SENSe]:SWEep:EGATe:SOURce EXTernal1|EXTernal2
|LINE|FRAMe|RFBurst
[:SENSe]:SWEep:EGATe:SOURce?
Example
SWE:EGAT SOUR EXT1 SWE:EGAT:SOUR?
Preset
EXTernal 1
Dependencies
In some models, there is no second External input. In these models, the External 2
key is blanked and the EXTernal2 parameter will generate a “Hardware missing;
Not available for this model number” error.
Backwards Compatibility
In ESA, there is a single Gate input port. In PSA, the Gate Source may be taken from
one of two specified input ports. In the X-Series, five Trigger Sources can be Gate
Sources.
Absolute Trigger Level
Sets the absolute trigger level for the RF burst envelope.
When using the External Mixing path, the Absolute Trigger Level is uncalibrated because
the factory default was set to accommodate the expected IF levels for the RF path.
439
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
Command
:TRIGger[:SEQuence]:RFBurst:LEVel:ABSolute <ampl>
:TRIGger[:SEQuence]:RFBurst:LEVel:ABSolute?
Example
TRIG:RFB:LEV:ABS 10 dBm sets the trigger level of the RF burst envelope signal to the
absolute level of 10 dBm
Preset
–20 dBm
Min/Max
–200 dBm/100 dBm
State
Saved
Saved in instrument state.
Notes
Sending this command does not switch the setting from relative to absolute; to
switch it you need to send the :TRIGger[:SEQuence]:RFBurst:LEVel:TYPE
command, below.
If mode is Bluetooth, the default value is -50 dBm.
Dependencies
Only appears when RF Burst is selected as the Trigger, Gate or Periodic Sync
Source.
Coupling
This same level is used for the RF Burst trigger source in the Trigger menu, for the
RF Burst selection in the Gate Source menu, and also for the RF Burst selection in
the Periodic Sync Src menu.
Backwards Compatibility
:TRIGger[:SEQuence]:FRAMe:RFBurst:LEVel:ABSolute
Trigger Slope
Sets the trigger polarity for Trigger and Gate sources that support Trigger Slope. It is
set positive to trigger on a rising edge and negative to trigger on a falling edge.
Trigger and Gate sources that support Trigger Slope include:
– Video
– Line
– External 1|2
– RF Burst
– I/Q Mag
– I (Demodulated)
Remote Language Compatibility Measurement Application Reference
440
3 RLC Mode & Swept SA Measurement
Trigger
– Q (Demodulated)
– Input I
– Input Q
– Aux Channel I/Q Mag
For any given Trigger, Gate, or Periodic Sync source, the same Trigger Slope is used
for the Trigger source in the Trigger menu, for the Gate source in the Gate Source
menu, and for the Periodic Sync source in the Periodic Sync Src menu.
See "Trig Delay Parameters" on page 442
See "More Information" on page 443
Command
:TRIGger
[:SEQuence]:LINE|EXTernal1|EXTernal2|VIDeo|RFBurst|IQMag|IDEMod|QD
EMod|IINPut|QINPut|AIQMag:SLOPe POSitive|NEGative
:TRIGger
[:SEQuence]:LINE|EXTernal1|EXTernal2|VIDeo|RFBurst|IQMag|IDEMod|QD
EMod|IINPut|QINPut|AIQMag:SLOPe?
Example
TRIG:VID:SLOP NEG
TRIG:VID:SLOP?
TRIG:EXT1: SLOP NEG
TRIG:EXT2: SLOP POS
TRIG:LINE:SLOP NEG
Preset
POSitive
State
Saved
Saved in instrument state.
Dependencies
Only appears when Video, Line, External 1|2, RF Burst trigger is selected as the
Trigger Source
Backwards Compatibility
In ESA/PSA, the Trigger Slope was global to all triggers. In the X-Series, the slope
can be set individually for each Trigger Source. For backward compatibility, the
global SLOPe command updates all instances of trigger slope (VID, LINE, EXT1,
EXT2, TV, RFB). The query returns the trigger slope setting of the currently selected
trigger source.
Command
:TRIGger[:SEQuence]:SLOPe POSitive|NEGative
:TRIGger[:SEQuence]:SLOPe?
441
Example
TRIG:SLOP NEG
Preset
POSitive
State Saved
Saved in instrument state.
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
Trig Delay Parameters
Source
Example
Preset
Min
Max
Video
TRIG:VID:DEL:STAT
ON
Off, 1
us
-150
ms
+500 ms
Off, 30
ms
0 ms
70 sec Off, 30
ms
0 ms
Off, 1
us
-150
ms
+500 ms
Off, 1
us
-150
ms
+500 ms
Off, 1
us
-150
ms
+500 ms
Off, 1
us
-150
ms
+500 ms
Off, 1
us
-2.5 s
+10 s
Off, 1
us
-2.5 s
+10 s
Off, 1
us
-2.5 s
+10 s
Off, 1
us
-2.5 s
+10 s
Off, 1
us
-2.5 s
+10 s
Off, 1
us
-2.5 s
+10 s
TRIG:VID:DEL 100 ms
Level
TRIG:LEV:DEL:STAT
ON
(but dependent on Acq Time
like FMT)
TRIG:LEV:DEL 100 ms
FMT
TRIG:FMT:DEL:STAT
ON
(but dependent on Acq Time
like FMT)
TRIG:FMT:DEL 100 ms
External 1|2
TRIG:EXT1:DEL:STAT
ON
70 sec TRIG:EXT2:DEL 100
ms
Line
TRIG:LINE:DEL:STAT
ON
TRIG:LINE:DEL 100 ms
RF Burst
TRIG:RFB:DEL:STAT
ON
TRIG:RFB:DEL 100 ms
Periodic Timer
TRIG:FRAM:DEL:STAT
ON
TRIG:FRAM:DEL 100
ms
I/Q Mag
TRIG:IQM:DEL:STAT
ON
TRIG:IQM:DEL 10 ms
I (Demod)
TRIG:IDEM:DEL:STAT
ON
TRIG:IDEM:DEL 10 ms
Q (Demod)
TRIG:QDEM:DEL:STAT
ON
TRIG:QDEM:DEL 10
ms
Input I
TRIG:IINP:DEL:STAT
ON
TRIG:IINP:DEL 10 ms
Input Q
TRIG:QINP:DEL:STAT
ON
TRIG:QINP:DEL 10 ms
Aux Chan I/Q
Mag
TRIG:AIQM:DEL:STAT
ON
TRIG:AIQM:DEL 10 ms
Remote Language Compatibility Measurement Application Reference
442
3 RLC Mode & Swept SA Measurement
Trigger
More Information
When FMT Trigger Criteria is INSIDE or OUTSIDE, FMT Trigger Delay State is forced
to OFF
FMT Trigger Delay MaxValue is dependent on the current AcquisitionTime. The
equation is: MaxValue = 2^16 x AcqTime, but never to exceed 70 sec. Ex: In PVT
View with a min PVT Acq Time of 200 us, this Trigger Delay MaxValue is 13.26 sec.
In RT Spectrum and Spectrogram with a min Acq Time of 100 us, this Trigger Delay
MaxValue is 6.55 sec. When the user increases the Acq Time, it will increase this
MaxValue.
FMT Trig Delay Diagram
Zero Span Delay Compensation
In zero span, there is a natural delay in the signal path, which comes from the RBW
filter. This is usually desirable, as it allows you to trigger on events and also see
those events, because the signal is delayed from the trigger event. However, in
some cases it is desirable to eliminate this delay, so that trigger events line up
exactly with the zero time point in zero span. You can use the Zero Span Delay Comp
On/Off feature to enable or disable zero span delay compensation.
Trigger and Gate sources that support Zero Span Delay Compensation include:
– External 1|2
– RF Burst
Command
:TRIGger
[:SEQuence]:EXTernal1|EXTernal2|RFBurst:DELay:COMPensation
OFF|ON|0|1 :TRIGger
[:SEQuence]:EXTernal1|EXTernal2|RFBurst:DELay:COMPensation?
443
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
Example
TRIG:EXT1:DEL:COMP ON
TRIG:EXT1:DEL:COMP?
TRIG:EXT2:DEL:COMP ON
TRIG:RFB:DEL:COMP ON
Preset
OFF
State
Saved
Saved in instrument state.
Trigger Settings Diagram
The Trigger Settings Diagram lets you configure the Trigger system using a visual
utility.
Remote Language Compatibility Measurement Application Reference
444
3 RLC Mode & Swept SA Measurement
Trigger
Periodic
Select Gate Source
The menus under the Gate Source tab are the same as those under the Trigger tab,
with the exception that only the following Gate Sources are available:
– Line
– External 1|2
– RF Burst
– Periodic
Although the menus are the same as Trigger, a different SCPI command is used to
select the Gate Source because you may independently set the Gate Source and the
Trigger Source.
Any changes to the settings in the setup menus under each Gate Source selection
key (for example: Trigger Level, Trigger Delay, etc.) also affect the corresponding
settings under the Trigger menu keys. The gate system uses the Trigger SCPI
commands for the setup functions, since each setting affects both Gate and Trigger.
Example: to set the Trigger Level for External 1 Trigger you use the command
:TRIG:EXT1:LEV; to set the Trigger Level for External 1 Gate you use the same
command, :TRIG:EXT1:LEV
The menus under the Gate Source key are an exact duplicate of the Trigger menu,
with these exceptions:
– The Free Run and Video selections are not provided for Gate.
– The Trig Delay controls are not present
– Relative RF Burst Triggering is not available, just Absolute.
If SCPI is sent to the TRIG node to change or set the setup functions that are left out
of the Gate Source menus (Auto Trig, Holdoff, Trig Delay) it is accepted and the
values stored, but the values are not visible from the Gate Source menus.
For the selection of the gate source the SCPI node
:TRIGger[:SEQuence]:
is replaced by
[:SENSe]:SWEep:EGATe:
as shown in the remote command below.
Command
[:SENSe]:SWEep:EGATe:SOURce EXTernal1|EXTernal2
|LINE|FRAMe|RFBurst
[:SENSe]:SWEep:EGATe:SOURce?
445
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
Example
SWE:EGAT SOUR EXT1 SWE:EGAT:SOUR?
Preset
EXTernal 1
Dependencies
In some models, there is no second External input. In these models, the External 2
key is blanked and the EXTernal2 parameter will generate a “Hardware missing;
Not available for this model number” error.
Backwards Compatibility
In ESA, there is a single Gate input port. In PSA, the Gate Source may be taken from
one of two specified input ports. In the X-Series, five Trigger Sources can be Gate
Sources.
Period
Sets the period of the internal periodic timer clock. For digital communications
signals, this is usually set to the frame period of your current input signal. In the case
that sync source is not set to OFF, and the external sync source rate is changed for
some reason, the periodic timer is synchronized at the every external
synchronization pulse by resetting the internal state of the timer circuit.
Only appears when Periodic Timer is selected as the Trigger or Gate Source
Command
:TRIGger[:SEQuence]:FRAMe:PERiod <time>
:TRIGger[:SEQuence]:FRAMe:PERiod?
Example
TRIG:FRAM:PER 100 ms
Preset
20 ms
Min/Max
100.000 ns/559.0000 ms
State Saved
Saved in instrument state.
Dependencies
The invalid data indicator turns on when the period is changed, until the next
sweep/measurement completes.
Couplings
The same period is used in the Gate Source selection of the period timer.
Offset
Adjusts the accumulated offset between the periodic timer events and the trigger
event. Adjusting the accumulated offset is different than setting an offset, and
requires explanation.
The periodic timer is usually not synchronized with any external events, so the timing
of its output events has no absolute meaning. Since the timing relative to external
events (RF signals) is important, you need to be able to adjust (offset) it. However,
you have no direct way to see when the periodic timer events occur. All that you can
Remote Language Compatibility Measurement Application Reference
446
3 RLC Mode & Swept SA Measurement
Trigger
see is the trigger timing. When you want to adjust the trigger timing, you will be
changing the internal offset between the periodic timer events and the trigger event.
Because the absolute value of that internal offset is unknown, we will just call that
the accumulated offset. Whenever the Offset parameter is changed, you are
changing that accumulated offset. You can reset the displayed offset using Reset
Offset Display. Changing the display does not change the value of the accumulated
offset, and you can still make additional changes to accumulated offset.
To avoid ambiguity, we define that an increase in the "offset" parameter, either from
the knob or the SCPI adjust command, serves to delay the timing of the trigger
event.
Only appears when Periodic Timer is selected as the Trigger or Gate Source.
Command
:TRIGger[:SEQuence]:FRAMe:OFFSet <time>
:TRIGger[:SEQuence]:FRAMe:OFFSet?
Example
TRIG:FRAM:OFFS 1.2 ms
Preset
0s
Min/Max
–10.000 s/10.000 s
State Saved
Saved in instrument state.
Notes
The front panel interface (for example, the knob), and this command, adjust the
accumulated offset, which is shown on the control.
However, the actual amount sent to the hardware each time the offset is updated is
the delta value, that is, the current accumulated offset value minus the previous
accumulated offset value. Note that the accumulated offset value is essentially
arbitrary; it represents the accumulated offset from the last time the offset was
zeroed (with the Reset Offset Display key).
Note that this command does not change the period of the trigger waveform. Note
also that Offset is used only when the sync source is set to OFF, otherwise delay is
used.
An increase in the "offset" parameter, either from the knob or the SCPI adjust
command, serves to delay the timing of the trigger event.
When the SCPI command is sent the value shown on the key is updated with the
new value. However, the actual amount sent to the hardware is the delta value,
that is, the current accumulated offset value minus the previous accumulated
offset value.
The SCPI query simply returns the value currently showing on the key.
Dependencies
The invalid data indicator turns on when the offset is changed, until the next
sweep/measurement completes.
Couplings
The same offset is used in the Gate Source selection of the period timer.
447
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
Reset Offset Display
Resets the value of the periodic trigger offset display setting to 0.0 seconds. The
current displayed trigger location may include an offset value defined with the Offset
key. Pressing this key redefines the currently displayed trigger location as the new
trigger point that is 0.0 s offset. The Offset key can then be used to add offset relative
to this new timing.
Only appears when Periodic Timer is selected as the Trigger or Gate Source
Command
:TRIGger[:SEQuence]:FRAMe:OFFSet:DISPlay:RESet
Example
TRIG:FRAM:OFFS:DISP:RES
Sync Source
For convenience you can select the Periodic Timer Sync Source using this dropdown.
You can also select it from the Periodic Sync Src tab, which also contains controls
that let you configure the Sync Source.
Selects a signal source for you to synchronize your periodic timer trigger to,
otherwise you are triggering at some arbitrary location in the frame. Synchronization
reduces the precision requirements on the setting of the period.
Only appears when Periodic Timer is selected as the Trigger or Gate Source.
Example
TRIG:FRAM:SYNC EXT1
TRIG:FRAM:SYNC EXT2
TRIG:FRAM:SYNC RFB
TRIG:FRAM:SYNC OFF
Preset
Off
State Saved
Saved in instrument state.
Trigger Settings Diagram
The Trigger Settings Diagram lets you configure the Trigger system using a visual
utility.
Remote Language Compatibility Measurement Application Reference
448
3 RLC Mode & Swept SA Measurement
Trigger
Gate Settings Tab
Gate
When the Gate Function is on, the selected Gate Method is used along with the gate
settings and the signal at the gate source to control the sweep and video system
with the gate signal. Not all measurements allow every type of Gate Methods.
If the Gate is turned on without a gate signal present, Marker Count operation is
unreliable, so it is locked out whenever Gate is on for measurements that support
Marker Count.
Command
[:SENSe]:SWEep:EGATe[:STATe] OFF|ON|0|
[:SENSe]:SWEep:EGATe[:STATe]?
Example
SWE:EGAT ON
SWE:EGAT?
449
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
Preset
Off
Range
On|Off
State Saved
Saved in instrument state.
Dependencies
The function is unavailable (grayed out) and Off when:
– Gate Method is LO or Video and FFT Sweep Type is manually selected.
– Gate Method is FFT and Swept Sweep Type is manually selected.
– Marker Count is ON.
– The following are unavailable whenever Gate is on:
– FFT under Sweep Type when Method=LO or Video or Swept under Sweep Type
when Method=FFT
– Marker Count
While Gate is on, the Auto Rules for Sweep Type are modified so that the choice
agrees with the Gate Method: i.e., FFT for Method = FFT and Swept for Method = LO
or Video.
The Gate softkey and all SCPI under the [:SENSe]:SWEep:EGATe SCPI node are
grayed out when Source Mode is Tracking with an external source. This is because
the Gate circuitry is used to sync the external source. If the Tracking Source is turned
on, the Gate is turned off.
Backwards Compatibility
[:SENSe]:SWEep:TIME:GATE[:STATe] ESA compatibility
Gate View
Turning on Gate View puts the analyzer into Gate View. When in Gate View, the
regular view of the current measurement traces and results are reduced vertically to
about 70% of the regular height. The Zero Span window, showing the positions of
the Gate, is shown between the Measurement Bar and the reduced measurement
window. By reducing the height of the measurement window, some of the
annotation on the Data Display may not fit and is not shown.
Command
[:SENSe]:SWEep:EGATe:VIEW ON|OFF|1|0
[:SENSe]:SWEep:EGATe:VIEW?
Example
SWE:EGAT:VIEW ON turns on the gate view.
Preset
OFF
Remote Language Compatibility Measurement Application Reference
450
3 RLC Mode & Swept SA Measurement
Trigger
Range
On|Off
State Saved
Saved in instrument state.
Dependencies
In Gate View, the regular Sweep Time (or Acquisition Time) key is grayed out, to
avoid confusing the user who wants to set Gate View Sweep Time. When pressed,
the grayed out key puts up the informational message "Use Gate View Sweep Time
in the Gate menu."
Couplings
– When Gate View is turned on, the instrument is set to Zero Span.
– Gate View automatically turns off whenever a Span other than Zero is selected.
– Gate View automatically turns off if you press the Last Span key while in Gate
View, and the instrument returns to the Span it was in before entering Gate View
(even if that is Zero Span).
– When Gate View is turned on, the sweep time used is the gate view sweep time.
This is set according to the rules in section Error! Reference source not found.
– When Gate View is turned off, Sweep Time is set to the normal Swept SA
measurement sweep time.
– If Gate View is on and Gate is off, then turning on Gate turns off Gate View.
More Information
Turning Gate View off returns the analyzer to the Normal measurement view.
Gate Delay
Controls the length of time from the time the gate condition goes True until the gate
is turned on.
Command
[:SENSe]:SWEep:EGATe:DELay <time>
[:SENSe]:SWEep:EGATe:DELay?
Example
SWE:EGAT:DELay 500ms
SWE:EGAT:DELay?
Preset
57.7 us
Min/Max
0.0 us/ 100 s
State Saved
Saved in instrument state
Notes
Units of time are required or no units; otherwise an invalid suffix error message will
be generated.
Backwards Compatibility SCPI
This command is for ESA compatibility.
451
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
[:SENSe]:SWEep:TIME:GATE:DELay
.
Gate Length
Controls the length of time that the gate is on after it opens.
[:SENSe]:SWEep:EGATe:LENGth <time>
Command
[:SENSe]:SWEep:EGATe:LENGth?
SWE:EGAT:LENG 1
Example
SWE:EGAT:LENG?
Preset
461.6 us
Min/ Max
100 ns/ 5 s
State Saved
Saved in instrument state
Notes
Units of time are required or no units; otherwise an invalid suffix error message will
be generated.
Dependencies
Grayed out when Gate Method is set to FFT in which case the label changes to that
shown below.
The key is also grayed out if Gate Control = Level.
Backwards Compatibility SCPI
This command is for ESA compatibility.
[:SENSe]:SWEep:TIME:GATE:LENGth
Gate Method
This lets you choose one of the three different types of gating.
Not all types of gating are available for all measurements.
Command
[:SENSe]:SWEep:EGATe:METHod LO|VIDeo|FFT
[:SENSe]:SWEep:EGATe:METHod?
Example
SWE:EGAT:METH FFT
Preset
LO
Range
Video|LO|FFT
State Saved
Saved in instrument state
Dependencies
Remote Language Compatibility Measurement Application Reference
452
3 RLC Mode & Swept SA Measurement
Trigger
This control is unavailable when Gate is On and FFT Sweep Type manually
selected.
When selected, Sweep Type is forced to Swept and the FFT key in Sweep Type is
grayed out.
Only the FFT method is supported in the non-SA products
More Information
LO
In LO gating, when Gate is set to On, the LO sweeps whenever the gate conditions
as specified in the Gate menu are satisfied by the signal at the Gate Source.
This form of gating is more sophisticated, and results in faster measurements. With
Gated LO, the analyzer only sweeps while the gate conditions are satisfied. This
means that a sweep could take place over several gate events. It would start when
the gate signal goes true and stop when it goes false, and then continue when it
goes true again. But since the LO is sweeping as long as the gate conditions are
satisfied, the sweep typically finishes much more quickly than with Gated Video.
When in zero span, there is no actual sweep performed. But data is only taken
while the gate conditions are satisfied. So even though there is no sweep, the gate
settings will impact when data is acquired.
Video
In Video gating, when Gate is set to On, the video signal is allowed to pass through
whenever the gate conditions as specified in the Gate menu are satisfied by the
signal at the Gate Source.
This form of gating may be thought of as a simple switch, which connects the signal
to the input of the spectrum analyzer. When the gate conditions are satisfied, the
switch is closed, and when the gate conditions are not satisfied, the switch is open.
So we only look at the signal while the gate conditions are satisfied.
With this type of gating, you usually set the analyzer to sweep very slowly. In fact, a
general rule is to sweep slowly enough that the gate is guaranteed to be closed at
least once per data measurement interval (bucket). Then if the peak detector is
used, each bucket will represent the peak signal as it looks with the gate closed.
FFT
In FFT gating, when Gate is set to On, an FFT is performed whenever the gate
conditions as specified in the Gate menu are satisfied by the signal at the Gate
Source. This is an FFT measurement which begins when the gate conditions are
satisfied. Since the time period of an FFT is approximately 1.83/RBW, you get a
measurement that starts under predefined conditions and takes place over a
predefined period. So, in essence, this is a gated measurement. You have limited
control over the gate length but it works in FFT sweeps, which the other two
methods do not.
Gated FFT cannot be done in zero span since the instrument is not sweeping. So in
zero span the Gated LO method is used. Data is still only taken while the gate
conditions are satisfied, so the gate settings do impact when data is acquired.
453
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
The Gate Length will be 1.83/RBW.
This is a convenient way to make a triggered FFT measurement under control of an
external gating signal.
Control
Sets the method of controlling the gating function from the gating signal.
Edge
In Edge triggering, the gate opens (after the Delay) on the selected edge (for
example, positive) of the gate signal and closes on the alternate edge (for example,
negative).
Level
In Level triggering, the gate opens (after the Delay) when the gate signal has
achieved a certain level and stays open as long as that level is maintained.
Command
[:SENSe]:SWEep:EGATe:CONTrol EDGE|LEVel
[:SENSe]:SWEep:EGATe:CONTrol?
Example
SWE:EGAT:CONT EDGE
Preset
EDGE
State Saved
Saved in instrument state.
Dependencies
If the Gate Method is FFT, Control is grayed out and Edge is selected.
If the Gate Source is TV, Frame, or Line, Control is grayed out and Edge is selected.
Backwards Compatibility
[:SENSe]:SWEep:TIME:GATE:TYPE ESA Compatibility
Gate Holdoff
Enables you to increase or decrease the wait time after a gate event ends before the
analyzer will respond to the next gate signal.
After any Gate event finishes, the analyzer must wait for the sweep system to settle
before it can respond to another Gate signal. The analyzer calculates a "wait time,"
taking into account a number of factors, including RBW and Phase Noise
Optimization settings. The goal is to achieve the same accuracy when gated as in
ungated operation. The figure below illustrates this concept:
Remote Language Compatibility Measurement Application Reference
454
3 RLC Mode & Swept SA Measurement
Trigger
When Gate Holdoff is in Auto, the wait time calculated by the analyzer is used. When
Gate Time is in Manual, the user may adjust the wait time, usually decreasing it in
order to achieve greater speed, but at the risk of decreasing accuracy.
When the Method key is set to Video or FFT, the Gate Holdoff function has no effect.
In measurements that do not support Auto, the value shown when Auto is selected
is “---“ and the manually set holdoff is returned to a query.
Command
[:SENSe]:SWEep:EGATe:HOLDoff <time> [:SENSe]:SWEep:EGATe:HOLDoff?
[:SENSe]:SWEep:EGATe:HOLDoff:AUTO OFF|ON|0|1
[:SENSe]:SWEep:EGATe:HOLDoff:AUTO?
Example
SWE:EGAT:HOLD 0.0002
SWE:EGAT:HOLD?
SWE:EGAT:HOLD:AUTO ON
SWE:EGAT:HOLD:AUTO?
Preset
Auto
Auto/On
Min/Max
1 μsec/1 sec
State Saved
Saved in instrument state.
Couplings
When Gate Holdoff is Auto, the Gate Holdoff key shows the value calculated by the
analyzer for the wait time.
Pressing the Gate Holdoff key while it is in Auto and not selected, causes the key to
become selected and allows the user to adjust the value. If the value is adjusted,
the setting changes to Man.
455
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
Pressing the Gate Holdoff key, while it is in Auto and selected, does not change the
value of Gate Holdoff, but causes the setting to change to Man. Now the user can
adjust the value.
Pressing the key while it is in Man and selected, cause the value to change back to
Auto.
Pressing the key while it is in Man and not selected, causes the key to become
selected and allows the user to adjust the value.
When Method is set to Video or FFT, the Gate Holdoff function has no effect.
Gate View Sweep Time
Controls the Sweep Time in the Gate View window. To provide an optimal view of the
gate signal, the analyzer initializes Gate View Sweep Time based on the current
settings of Gate Delay and Gate Length.
Since Gate View Sweep Time is used to calculate Gate Delay and Gate Length
increments, it is maintained even when not in Gate View.
Command
[:SENSe]:SWEep:EGATe:TIME <time>
[:SENSe]:SWEep:EGATe:TIME?
Example
SWE:EGAT:TIME 500 ms
Preset
519.3 µs
Min/Max
1 µs/6000 s
State Saved
Saved in instrument state.
Dependencies
Gate View Sweep Time is initialized:
– On Preset (after initializing delay and length).
– Every time the Gate Method is set/changed.
Additionally, in the Swept SA measurement, whenever you do a Preset, or leave
Gate View, the analyzer remembers the Gate Delay and Gate Length settings.
Then, when returning to Gate View, if the current Gate Delay and/or Gate Length
do not match the remembered values Gate View Sweep Time is re-initialized.
Remote Language Compatibility Measurement Application Reference
456
3 RLC Mode & Swept SA Measurement
Trigger
Gate View Start Time
Controls the Acquisition Time in the Gate View window. To provide an optimal view of
the gate signal, the analyzer initializes Gate View Acquisition Time based on the
current settings of Gate Delay and Gate Length.
[:SENSe]:SWEep:EGATe:TIME <time>
Command
[:SENSe]:SWEep:EGATe:TIME?
Example
SWE:EGAT:TIME 500 ms
Preset
519.3 µs
Min/Max
100 ns/6000 s
State Saved
Saved in instrument state.
Dependencies
Gate View Acquisition Time is initialized:
– On Preset (after initializing delay and length).
– Every time the Gate Method is set/changed.
Periodic Sync Src Tab
Select Periodic Trigger Sync Source
Selects a signal source for you to synchronize your periodic timer trigger to,
otherwise you are triggering at some arbitrary location in the frame. Synchronization
reduces the precision requirements on the setting of the period.
For convenience you may adjust the level and slope of the selected sync source in a
conditional branch setup menu accessed from the Sync Source menu. Note that
these settings match those in the Trigger and Gate Source menus; that is, each
trigger source has only one value of level and slope, regardless of which menu it is
accessed from.
One of the choices is Off. With the sync source off, the timing will drift unless the
signal source frequency is locked to the analyzer frequency reference.
Command
:TRIGger[:SEQuence]:FRAMe:SYNC
EXTernal1|EXTernal2|RFBurst|OFF
:TRIGger[:SEQuence]:FRAMe:SYNC?
Example
TRIG:FRAM:SYNC EXT1
TRIG:FRAM:SYNC EXT2
TRIG:FRAM:SYNC RFB
TRIG:FRAM:SYNC OFF
Preset
457
Off
Remote Language Compatibility Measurement Application Reference
3 RLC Mode & Swept SA Measurement
Trigger
State
Saved
Saved in instrument state.
Dependencies
In some models, there is no second External input. In these models, the External 2
key is blanked and the EXTernal2 parameter will generate a “Hardware missing;
Not available for this model number” message.
Backwards Compatibility
:TRIGger[:SEQuence]:FRAMe:SYNC EXTernal
For backward compatibility, the parameter EXTernal is mapped to EXTernal1
Trigger Settings Diagram
The Trigger Settings Diagram lets you configure the Trigger system using a visual
utility.
Auto Holdoff Tab
Auto Trig
Sets the time that the analyzer will wait for the trigger conditions to be met. If they
are not met after that much time, then the analyzer is triggered anyway.
Remote Language Compatibility Measurement Application Reference
458
3 RLC Mode & Swept SA Measurement
Trigger
Command
:TRIGger[:SEQuence]:ATRigger <time>
:TRIGger[:SEQuence]:ATRigger?
:TRIGger[:SEQuence]:ATRigger:STATe OFF|ON|0|1
:TRIGger[:SEQuence]:ATRigger:STATe?
Example
TRIG:ATR:STAT ON
TRIG:ATR 100 ms
Preset
100 ms
OFF
Min/Max
1 ms/100 s
State Saved
Saved in instrument state.
Notes
The "time that the analyzer will wait" starts when the analyzer is ready for a trigger,
which may be hundreds of ms after the data acquisition for a sweep is done. The
"time" ends when the trigger condition is satisfied, not when the delay ends.
Trig Holdoff
Sets the holdoff time between triggers. When the trigger condition is satisfied, the
trigger occurs, the delay begins, and the holdoff time begins. New trigger conditions
will be ignored until the holdoff time expires. For a free-running trigger, the holdoff
value is the minimum time between triggers.
Command
:TRIGger[:SEQuence]:HOLDoff <time>
:TRIGger[:SEQuence]:HOLDoff?
:TRIGger[:SEQuence]:HOLDoff:STATe OFF|ON|0|1
:TRIGger[:SEQuence]:HOLDoff:STATe?
Example
TRIG:HOLD:STAT ON
TRIG:HOLD 100 ms
Preset
100 ms
OFF
459
Min/Max
0 s/0.5 s
State Saved
Saved in instrument state.
Remote Language Compatibility Measurement Application Reference
Keysight X-Series Signal Analyzer
Remote Language Compatibility Measurement Application Reference
4 Preset
The Preset functions are available in two ways; either by pressing the Mode Preset or
User Preset front panel keys, or from the Preset dropdown menu that appears when
you press the green Preset icon in the upper right corner of the display.
Types of Preset
The table below shows all possible presets, their corresponding SCPI commands and
front-panel access methods.
Instrument settings are tiered in scope from those local to the current measurement
to those global to all measurements and modes. There are presets tailored to each
scope. The table identifies the scope of each preset type.
To get a Mode back to a fully predefined state, you should execute a Restore Mode
Defaults and an Input/Output Preset, but since Input/Output Preset is a global
function, it affects all modes.
460
4 Preset
461
Type Of
Preset
SCPI Command
Scope of Preset
Front Panel
Access
Auto Couple
:COUPle ALL
Local to the current
measurement, only affects
Auto/Man variables
Meas Setup
Menu
Meas Preset
:CONFigure:<meas>
Local to the current
measurement
Meas Setup
Menu
Mode Preset
:SYSTem:PRESet
Local to the current mode,
global to all measurements in
the mode, affects most but not
all parameters in the mode,
does not affect Input/Output or
System variables
Mode Preset
(green key)
and Preset
Dropdown
Restore Mode
Defaults
:INSTrument:DEFault
Local to the current mode,
global to all measurements in
the mode, affects all
parameters in the mode but
does not affect Input/Output or
System variables
Preset
Dropdown
Restore
Defaults All
Modes
:SYSTem:DEFault MODes
Affects all parameters in ALL
modes but does not affect
Input/Output or System
variables
Preset
Dropdown
Restore
Screen
Defaults
:SYSTem:DEFault SCReen
Deletes all Screens but one,
restores that screen to its
default mode and performs a
Mode Preset for that mode.
Does not affect Input/Output or
System variables.
Preset
Dropdown
User Preset
:SYSTem:PRESet:USER
Local to the current mode,
global to all measurements in
the mode, affects all
parameters in the mode as well
as the Input/Output variables.
Does not affect System
variables.
User Preset
hardkey and
Preset
Dropdown
User Preset
All Modes
:SYSTem:PRESet:USER:ALL
Same as User Preset but
affects all Modes in the current
Screen.
Preset
Dropdown
*RST
*RST
Same as Mode Preset - and in
addition always sets
Single/Cont to Single
Not available
from front
panel
Input/Output
Preset
:SYSTem:DEFault INPut
Affects all Input/Output
variables
Input/Output
menu, Preset
dropdown,
and System
Menu,
Restore
Remote Language Compatibility Measurement Application Reference
4 Preset
Type Of
Preset
SCPI Command
Scope of Preset
Front Panel
Access
Defaults
Full Mode
Preset
:SYSTem:PRESet:FULL
Same as doing Mode Preset,
Restore Mode Defaults and
Input/Output Preset.
Essentially a factory preset of
the current Mode.
Preset
Dropdown
Restore User
Interface
Defaults
:SYSTem:DEFault
UINTerface
Affects all variables in the
”User Interface” group
System
Menu,
Restore
Defaults and
User
Interface tabs
Restore
Power On
Defaults
:SYSTem:DEFault PON
Affects all variables in the
”Power On” group
System
Menu:
Restore
Defaults and
Power On
tabs
Restore
Alignment
Defaults
:SYSTem:DEFault ALIGn
Affects all variables in the
”Alignments” group
System
Menu,
Restore
Defaults and
Alignments
tabs
Restore
Miscellaneous
Defaults
:SYSTem:DEFault MISC
Affects various variables not
reset by other commands
System
Menu,
Restore
Defaults
Restore All
Defaults
:SYSTem:DEFault [ALL]
Affects all variables
System
Menu,
Restore
Defaults
:SYSTem:PRESet:PERSistent
Remote Language Compatibility Measurement Application Reference
462
4 Preset
Mode Preset
Mode Preset
Returns the current Mode to a known state. Mode Preset only presets the current
Screen, it does not affect any other Screens.
Mode Preset can be executed from the Preset dropdown or by pressing the Mode
Preset front panel key.
Mode Preset does the following for the currently active mode:
– Aborts the currently running measurement.
– Switches to the default measurement and brings up the default menu for that
measurement.
– Sets most parameters for the Mode and all of its Measurements to a preset
state.
– Clears the input and output buffers.
– Sets Status Byte to 0.
Mode Preset does not cause a Mode switch or affect any Input/Output or System
settings (those set in the System Settings dialog).
463
Remote Language Compatibility Measurement Application Reference
4 Preset
Mode Preset
Furthermore, there are some Mode settings that are unaffected by a Mode Preset
(for example, Noise Floor Extensions, Limit Line data, reference marker numbers,
etc.) These are only reset by Restore Mode Defaults.
See "Types of Preset" on page 460 for more information.
Command
:SYSTem:PRESet
Example
:SYST:PRES
Notes
*RST is preferred over :SYST:PRES for remote operation. *RST does a Mode Preset, as done by
the :SYST:PRES command, and it sets the measurement mode to Single measurement rather
than Continuous for optimal remote control throughput.
Status Bits/OPC
dependencies
Clears all pending OPC bits. The Status Byte is set to 0.
Backwards Compatibility
In the X-Series, the legacy “Factory Preset” has been replaced with Mode Preset,
which only presets the currently active mode, not the entire instrument. In the XSeries, the way to preset the entire instrument is by using System, Restore System
Defaults All, which behaves essentially the same way as restore System Defaults
does on ESA and PSA.
There is also no “Preset Type” as there is on the PSA. There is a green Mode Preset
front-panel key that does a Mode Preset and a white-with-green-letters User
Preset front-panel key that does a User Preset. The old PRESet:TYPE command is
ignored (without generating an error), and SYST:PRES without a parameter does a
Mode Preset, which should cover most backward code compatibility issues.
The settings and correction data under the Input/Output front-panel key
(examples: Input Z Corr, Ext Amp Gain, etc.) are no longer part of any Mode, so they
will not be preset by a Mode Preset. They are preset using Restore Input/Output
Defaults, Restore System Defaults All. Note that because User Preset does a
Recall State, and all of these settings are saved in State, they ARE recalled when
using User Preset.
Restore Mode Defaults
Restore Mode Defaults causes the currently running measurement to be aborted
and causes the default measurement to be active. It gets the mode to a consistent
state with all of the default couplings set.
Note that a Recall State affects all of a Mode’s settings, both the Mode Preset
settings and the ones additionally affected by Restore Mode Defaults.
Restore Mode Defaults can be executed from the Preset drop-down menu.
Remote Language Compatibility Measurement Application Reference
464
4 Preset
Mode Preset
When Restore Mode Defaults is selected, a message appears saying:
“This will reset all of the current Mode’s variables to their
default state. This action cannot be undone. Do you want to
proceed?”
The message provides an OK and Cancel button to let you affirm or cancel the
operation.
Command
:INSTrument:DEFault
Example
:INST:DEF
Notes
Clears all pending OPC bits. The Status Byte is set to 0.
Input Output Preset
Input/Output Preset resets the group of settings and data associated with the
Input/Output front-panel key to their default values. These settings are not affected
by a Mode Preset because they are generally associated with connections to the
instrument, and most users would not want these resetting every time they pressed
the Mode Preset key.
Input/Output Preset can be executed from the Input/Output menu, from the Preset
menu, or from the Restore Defaults menu under the System key.
When Input/Output Preset is selected, a message appears saying:
“This will reset all of the Input/Output variables to their
default state, including which input is selected, all Amplitude
Correction settings and data, all External Mixing settings, all
Frequency Reference settings and all Output settings.
It will not affect Alignment data or settings.
465
Remote Language Compatibility Measurement Application Reference
4 Preset
Mode Preset
This action cannot be undone. Do you want to proceed?”
The message provides an OK and Cancel button to let you affirm or cancel the
operation.
Example
:SYST:DEF INP presets all the Input/Output variables to their factory default values.
Remote Language Compatibility Measurement Application Reference
466
4 Preset
User Preset
User Preset
User Preset recalls a state previously saved using the Save User Preset function.
You can save a User Preset state for each Mode, allowing you to define your own
favorite state for each Mode and recall it at the touch of a single button.
User Preset can be executed by pressing the User Preset front panel key or from the
Preset dropdown.
Because User Preset is actually a Recall State, rather than a predefined Preset, it
works a little differently than Mode Preset, in that it affects all of the variables that
normally only reset on Restore Mode Defaults, and it affects the Input/Output
variables, because both of these are included in State files.
A default User Preset file is provided for each Mode which simply matches the
current Mode’s state after a Restore Mode Defaults and Input/Output Preset has
been performed.
In products that run multiple instances of the X-Series Application, all instances use the
same location to save User Preset state. So Save User Preset of one instance will
overwrite the Save User Preset of another instance.
Command
:SYSTem:PRESet:USER
Example
:SYST:PRES:USER:SAVE Save the User Preset:SYST:PRES:USER Recall
the User Preset
Notes
:SYST:PRES:USER:SAVE is used to save the current state as the user preset state.
If loading a User Preset file from a different instrument, some settings may be limited and/or
coupled differently, since the capabilities of the mode may have changed from when the User
467
Remote Language Compatibility Measurement Application Reference
4 Preset
User Preset
Preset file was saved.
Status Bits/OPC
dependencies
Clears all pending OPC bits. The Status Byte is set to 0.
Backwards Compatibility
In the X-Series A-models, the User Preset hardkey opened a menu that let you
select from User Preset, Save User Preset, or User Preset All Modes. In the Bmodels, the User Preset hardkey immediately performs a User Preset, and the
aforementioned menu is found under the Preset dropdown.
User Preset actually loads a state, and in legacy analyzers, it was possible to load
a state without affecting the trace data, limit lines or correction data. Similarly it
was possible to do a User Preset without affecting the trace data, limit lines or
correction data.
In the X-Series, “state” always includes all of this data; so whenever state is
loaded, or User Preset is executed, all of the traces, limit lines and corrections are
affected. Although this differs from previous behavior, it is desirable behavior, and
should not cause adverse issues for users.
On ESA and PSA, User Preset affected the entire instrument’s state. In the XSeries, User Preset only recalls the state for the active mode. There is a User
Preset file for each mode. User Preset can never cause a mode switch as it can in
legacy analyzers. If you want to recall all modes to their user preset file state, you
will need to do a User Preset after mode switching into each mode.
User Preset recalls mode state which can now include data like traces; whereas on
ESA and PSA, User Preset did not affect data.
For more details of each menu item, see:
– "Save User Preset" on page 468
– "User Preset All Modes" on page 469
Save User Preset
Saves the state of the currently active mode in a unique location for recall by the
User Preset key. Each Mode has one such location, so for each Mode one User
Preset can be defined.
Save User Preset can be executed from the Preset menu.
Remote Language Compatibility Measurement Application Reference
468
4 Preset
User Preset
All Mode variables are saved, including those reset by Mode Preset and those only
reset by Restore Mode Defaults, as well as all of the Input/Output variables, so
when you press the User Preset key, the instrument returns to the exact same setup
that existed when you pressed the Save User Preset control. Thus, User Preset is a
preset of larger scope than Mode Preset.
Command
:SYSTem:PRESet:USER:SAVE
Example
:SYST:PRES:USER:SAVE
Notes
:SYST:PRES:SAVE creates the same file as if the user requested a *SAV or a MMEM: STOR:STAT,
except User Preset Save does not allow the user to specify the filename or the location of the file.
User Preset All Modes
User Preset All Modes recalls all of the User Preset files for each mode, switches to
the power-on mode, and activates the saved measurement from the power-on
mode User Preset file.
User Preset All Modes can be executed from the Preset menu.
469
Remote Language Compatibility Measurement Application Reference
4 Preset
User Preset
See the "User Preset" on page 467 description for more details on User Preset.
Command
:SYSTem:PRESet:USER:ALL
Example
:SYST:PRES:USER:SAVE
:SYST:PRES:USER:ALL
Notes
:SYST:PRES:USER:SAVE is used to save the current state as the user preset state.
Status Bits/OPC
dependencies
Clears all pending OPC bits. The Status Byte is set to 0.
Remote Language Compatibility Measurement Application Reference
470
4 Preset
Restore Defaults All Modes
Restore Defaults All Modes
This selection resets all of the Modes in the current Screen back to their default
state, switches the instrument to the power-on mode and causes the default
measurement for the power-on mode to be active.
Restore Defaults All Modes can be executed from the Preset menu.
When Restore Defaults All Modes is selected, a message appears saying:
“This will reset all of the variables for all of the Modes in the
current Screen to their default state. This action cannot be
undone. Do you want to proceed?”
The message provides an OK and Cancel button.
Example
471
:SYST:DEF MOD
Remote Language Compatibility Measurement Application Reference
4 Preset
Restore Screen Defaults
Restore Screen Defaults
This selection resets the Screen configuration to the factory default. A single screen
will remain, set to the power-on Mode in a preset state with the default screen
name.
Restore Screen Defaults can be executed from the Preset menu.
When Restore Screen Defaults is selected, a message appears saying:
“This function will delete all defined screens and their settings.
This action cannot be undone.
Do you want to proceed?”
The message provides an OK and Cancel button.
Example
:SYST:DEF SCReen
Remote Language Compatibility Measurement Application Reference
472
4 Preset
RST Remote Command Only
RST Remote Command Only
*RST causes the currently running measurement to be aborted and causes the
default measurement to be active. *RST sets the mode to a consistent state, with all
of the default couplings set.
*RST is equivalent to :SYST:PRES;:INIT:CONT OFF, which is a Mode Preset in the
Single measurement state. This remote command is preferred over Mode Preset
remote command - :SYST:PRES, as optimal remote programming occurs with the
instrument in the single measurement state.
Command
*RST
Example
*RST
Notes
Sequential
Status Bits/OPC dependencies
Clears all pending OPC bits. The Status Byte is set to 0.
Backwards Compatibility
In legacy analyzers *RST did not set the analyzer to Single, but in the X-Series it
does, for compliance with the IEEE 488.2 specification.
In the X-Series, *RST does not do a *CLS (clear the status bits and the error queue).
In legacy analyzers, *RST used to do the equivalent of SYSTem:PRESet, *CLS and
INITiate:CONTinuous OFF. To be 488.2 compliant, *RST in the X-Series does not do a
*CLS.
473
Remote Language Compatibility Measurement Application Reference
Keysight X-Series Signal Analyzer
Remote Language Compatibility Measurement Application Reference
5 System Settings
474
5 System Settings
System
System
The System page allows access to several general system functions including three
“Show” screens for viewing system parameters. Several such “Show” screens are
available on this and other System menu pages. They can also be accessed with the
following SCPI command:
Command
:SYSTem:SHOW
OFF|ERRor|SYSTem|HARDware|LXI|HWSTatistics|ALIGnment|SOFTware|CA
PPlication
:SYSTem:SHOW?
Example
:SYST:SHOW SYST
Preset
OFF
State
Saved
No
Windows Controls
Windows controls let you open the Control Panel or Web Browser.
475
Remote Language Compatibility Measurement Application Reference
5 System Settings
System
Control Panel...
Opens the Windows Control Panel. The Control Panel is used to configure certain
elements of Windows that are not configured through the hardkey/softkey System
menus.
This feature is not available if option SF1 is installed.
The Control Panel is a separate Windows application, so to return to the analyzer
once you are in the Control Panel, you may either:
– Exit the Control Panel by tapping on the red X in the upper right hand corner.
– Or use Alt-Tab: press and hold the Alt key and press and release the Tab key
until the Analyzer logo is showing in the window in the center of the screen, then
release the Alt key.
Web Browser
This key launches whatever Web Browser you have defined as your default, usually
Microsoft Internet Explorer. A mouse and external keyboard are highly desired for
using Internet Explorer. Close Internet Explorer to return focus to the Instrument
Application (or use Alt-Tab).
This feature is not available if option SF1 is installed.
Application Controls
The Application controls let you Minimize and Exit the application.
Pressing the Exit Program icon displays a prompt, asking you to confirm that you
want to close the program. If you click “OK” the entire analyzer application shuts
down, and you will lose any unsaved trace or measurement data.
No equivalent remote command for this key.
Show
Show panel lets you to see system, hardware, and LXI information.
Show System
The Show System screen is formatted into three groupings: product descriptive
information, options tied to the hardware, and software products. Swipe up and
Remote Language Compatibility Measurement Application Reference
476
5 System Settings
System
down on this screen with your finger to scroll the display and see more information.
Graphic
Example
SYST:SHOW SYST
Backwards Compatibility Notes
The hardware statistics that are displayed in the PSA Show System screen have
been moved to a dedicated Show Hardware Statistics screen in the Service Menu.
Show System contents (Remote Command Only)
A remote command is available to obtain the contents of the Show System screen
(the entire contents, not just the currently displayed page).The output is an IEEE
Block format of the Show System contents. Each line is separated with a new-line
character.
Command
:SYSTem:CONFigure[:SYSTem]?
Example
:SYST:CONF?
Computer System description (Remote Command Only)
A remote command is available to obtain the Computer System description. The
Computer System is the operating system and patch level as reported by operating
system.The return value is the Computer System name and service pack level.
477
Remote Language Compatibility Measurement Application Reference
5 System Settings
System
Command
:SYSTem:CSYStem?
Example
:SYST:CSYS?
Show Hardware
The show hardware screen is used to view details of the installed hardware. This
information can be used to determine versions of hardware assemblies and field
programmable devices, in the advent of future upgrades or potential repair needs.
The screen is formatted into two groupings: product descriptive information and
hardware information. The hardware information is listed in a table format.
Graphic
Example
SYST:SHOW HARD
Show LXI
This key shows you the product number, serial number, firmware revision, computer
name, IP address, Host ID, LXI Class, LXI Version, MAC Address, and the Auto-MDIX
Capability.
Graphic
Remote Language Compatibility Measurement Application Reference
478
5 System Settings
System
SYST:SHOW LXI
Example
Sound
The Sound panel lets you adjust the speaker volume with the slider, and Mute/Unmute the speaker, by tapping the Speaker icon.
Moving the slider up and down changes the speaker volume. It un-mutes the
speaker if muted.
Speaker icon when muted:
479
Remote Language Compatibility Measurement Application Reference
5 System Settings
System
Remote Language Compatibility Measurement Application Reference
480
5 System Settings
I/O Config
I/O Config
Activates a menu for identifying and changing the I/O configuration for remote
control. Controls in this menu allow configuration of the I/O ports used for SCPI
remote control over GPIB and LAN.
The SCPI LAN parameters are set using the I/O Config menu, but configuration of the
LAN settings themselves is performed using the Windows® Control Panel (DHCP,
Gateway, Subnet Mask, etc.).
The USB port is also available for remote control, but requires no configuration.
GPIB
Activates a menu for configuring the GPIB I/O port.
GPIB Address
Select the GPIB remote address.
Changing the Address on the GPIB port requires all further communication to use the
new address.
Command
:SYSTem:COMMunicate:GPIB[1][:SELF]:ADDRess
<integer>
:SYSTem:COMMunicate:GPIB[1][:SELF]:ADDRess?
481
Example
:SYST:COMM:GPIB:ADDR 17
Preset
18; This is unaffected by Preset but is set to 18 on a “Restore System
Defaults->Misc”
Min/Max
0/30
State Saved
No
Remote Language Compatibility Measurement Application Reference
5 System Settings
I/O Config
GPIB Controller
Sets the GPIB port into controller or device mode. In the normal state, GPIB
controller is disabled, which allows the analyzer to be controlled by a remote
computer. When GPIB Controller is enabled, the instrument can run software
applications that use the instrument's computer as a GPIB controller; controlling
devices connected to the instrument's GPIB port.
When GPIB Controller is enabled, the analyzer application itself cannot be controlled
over GPIB. In this case it can easily be controlled via LAN or USB. The GPIB port cannot
be a controller and device at the same time. Only one controller can be active on the
GPIB bus at any given time. If the analyzer is the controller, an external PC cannot be a
controller.
To control the instrument from the software that is performing GPIB controller
operation, you can use an internal TCP/IP connection to the analyzer application.
Use the address TCPIP0:localhost:inst0:INSTR to send SCPI commands to the
analyzer application.
Command
:SYSTem:COMMunicate:GPIB[1][:SELF]:CONTroller
[:ENABle] ON|OFF|0|1
:SYSTem:COMMunicate:GPIB[1][:SELF]:CONTroller
[:ENABle]?
Example
:SYST:COMM:GPIB:CONT ON
:SYST:COMM:GPIB:CONT OFF
Preset
Disabled; This is unaffected by Preset but is set to OFF on a “Restore
System Defaults->Misc”
Range
Disabled|Enabled
State Saved
No
Notes
When the instrument becomes the Controller bit 0 in the Standard Event Status
Register is set (and when the instrument relinquishes Controller capability bit 0 is
cleared in the Standard Event Status Register).
SCPI
Activates a menu for identifying and changing the SCPI over a LAN configuration.
There are a number of different ways to send SCPI remote commands to the
instrument over LAN. It can be a problem to have multiple users simultaneously
accessing the instrument over the LAN. These keys limit that somewhat by disabling
the telnet, socket, and/or SICL capability.
Remote Language Compatibility Measurement Application Reference
482
5 System Settings
I/O Config
When multiple instances of the application are running, Telnet port 5023, socket port
5025, SICL server inst0 and HiSLIP server Device 0 will be assigned to the first instance;
Telnet port 5123, socket port 5125, SICL server inst1 and HiSLIP server Device 1 will be
assigned to the second instance; Telnet port 5223, socket port 5225, SICL server inst2
and HiSLIP server Device 2 will be assigned to the third instance; Telnet port 5323,
socket port 5325, SICL server inst3 and HiSLIP server Device 3 will be assigned to the
fourth instance.
SCPI Telnet
Turns the SCPI LAN telnet capability On or Off allowing you to limit SCPI access over
LAN through telnet.
:SYSTem:COMMunicate:LAN:SCPI:TELNet:ENABle
OFF|ON|0|1
Command
:SYSTem:COMMunicate:LAN:SCPI:TELNet:ENABle?
Example
:SYST:COMM:LAN:SCPI:TELN:ENAB OFF
Preset
ON; This is unaffected by Preset but is set to ON with a “Restore
System Defaults->Misc”
Range
On | Off
State Saved
No
SCPI Socket
Turns the capability of establishing Socket LAN sessions On or Off. This allows you to
limit SCPI access over LAN through socket sessions.
:SYSTem:COMMunicate:LAN:SCPI:SOCKet:ENABle
OFF|ON|0|1
Command
:SYSTem:COMMunicate:LAN:SCPI:SOCKet:ENABle?
Example
:SYST:COMM:LAN:SCPI:SOCK:ENAB OFF
Preset
ON;This is unaffected by a Preset but is set to ON with a “Restore
System Defaults->Misc”
State Saved
No
SICL Server
Turns the SICL server capability On or Off, enabling you to limit SCPI access over
LAN through the SICL server. (SICL IEEE 488.2 protocol.)
483
Parameter
Description
Setting
Maximum
Connections
The maximum number of connections that can be accessed simultaneously
5
Instrument
Name
The name (same as the remote SICL address) of your analyzer
inst0
Instrument
Logical Unit
The unique integer assigned to your analyzer when using SICL LAN
8
Remote Language Compatibility Measurement Application Reference
5 System Settings
I/O Config
Parameter
Description
Setting
Emulated GPIB The name (same as the remote SICL address) of the device used when
Name
communicating with your analyzer
gpib7
Emulated GPIB The unique integer assigned to your device when it is being controlled using SICL 8
Name
LAN
Emulated GPIB The emulated GPIB address assigned to your transmitter tester when it is a SICL
Address
server (the same as your GPIB address)
Command
18
:SYSTem:COMMunicate:LAN:SCPI:SICL:ENABle
OFF|ON|0|1
:SYSTem:COMMunicate:LAN:SCPI:SICL:ENABle?
Example
:SYST:COMM:LAN:SCPI:SICL:ENAB OFF
Preset
ON; This is unaffected by Preset, but is set to ON with a “Restore
System Defaults->Misc”
State Saved
No
HiSLIP Server
Turns the HiSLIP server capability On or Off, enabling you to limit SCPI access over
LAN through the HiSLIP server.
HiSLIP stands for High Speed LAN Instrument Protocol and is part of the IVI-6.1
specification.
Here is an example of a VISA connection string used to connect to the HiSLIP Server
on an X-Series Spectrum Analyzer:
TCPIP0::a-n9030a-93016::hislip0::INSTR
In the example above, hislip0 is the HiSLIP device name that VISA users must
include in their HiSLIP VISA Address strings. Your HiSLIP device name may be
different depending on your VISA settings.
Command
:SYSTem:COMMunicate:LAN:SCPI:HISLip:ENABle
OFF|ON|0|1
:SYSTem:COMMunicate:LAN:SCPI:HISLip:ENABle?
Example
:SYST:COMM:LAN:SCPI:HISL:ENAB OFF
Preset
ON; This is unaffected by Preset, but is set to ON with a “Restore
System Defaults->Misc”
State Saved
No
Web Password Reset
The embedded web server contains certain capabilities that are password
protected, such as modifying the LAN configuration of the instrument, and access to
Remote Language Compatibility Measurement Application Reference
484
5 System Settings
I/O Config
web pages that can change the settings of the instrument. The control provided here
is the means to set the web password as the user desires, or to reset the password
to the factory default.
Selecting Reset web password displays a control for resetting the password as
desired, or to the factory default. The built-in alpha keyboard appears. You may
change the password from the factory default of “measure4u”.
You can cancel this entry by pressing the Cancel (ESC) front-panel key.
System IDN Response
This control allows you to specify a response to the *IDN? query, return the analyzer
to the Factory response if you have changed it, or, if your test software is expecting
the *IDN response to indicate Agilent Technologies, configure the instrument to
respond with Agilent as the manufacturer.
The current *IDN response is displayed at the top of the panel, followed by the
System IDN Response and User IDN controls.
System IDN Response
To choose the factory-set response, press the Factory key.
To specify your own response, press the User key, and enter your desired response.
If your test software is expecting the response to indicate Agilent Technologies as
the Manufacturer, you can configure this response by pressing the Agilent key.
See More Information.
Command
:SYSTem:IDN:CONFigure FACTory|AGILent|USER
:SYSTem:IDN:CONFigure?
Example
:SYST:IDN:CONF FACT
Preset
The *IDN response is reset to FACTory by Restore Misc Defaults or Restore
System Defaults All and survives subsequent running of the software.
Notes
– This affects the response given in all Modes of the Analyzer, unless the current
Mode has also specified a custom response, in which case the current Mode’s
custom IDN response takes precedence over the System’s, but only while that
Mode is the current Mode.
– It survives shutdown and restart of the software and therefore survives a power
cycle.
More Information
Here are details about the several options available for the System *IDN response:
Factory
SCPI example: :SYST:IDN:CONF FACT
485
Remote Language Compatibility Measurement Application Reference
5 System Settings
I/O Config
Selects the factory default configuration of *IDN?, which indicates the Manufacturer
as Keysight Technologies. For example,
“Keysight Technologies,N9040B,MY00012345,A.15.00”
where the fields are manufacturer, model number, serial number, firmware
revision.
Agilent
SCPI example: :SYST:IDN:CONF AGIL
Starting with software version x.14.50, the *IDN? response in the Factory
configuration will indicate the Manufacturer as Keysight Technologies. If your test
software is expecting the response to indicate Agilent Technologies you can
conveniently configure the response with this menu selection key or SCPI
command.
For example:
“Agilent Technologies,N9020A,MY00012345,A.05.01”
User
SCPI example: :SYST:IDN:CONF USER
Selects your customized configuration of *IDN?
Enter your desired response using the User IDN control.
User IDN
This control allows you to specify your own response to the *IDN? query. You may
enter your desired response with the Alpha Editor or a plugin PC keyboard. Once the
value is entered select “User” under System IDN Response.
When you select this control, the active function becomes the current User string
and is highlighted, so typing replaces it. If instead you wish to edit the existing string
press the left or right arrow to go to the beginning or the end.
If you enter a null string (for example, by clearing the User String while editing and
then pressing Done) the analyzer automatically reverts to the Factory setting.
In products that run multiple instances of the X-Series Application, all instances use the
same User System IDN response.
Command
:SYSTem:IDN <string>
:SYSTem:IDN?
Preset
This is unaffected by Preset but is set to the original factory setting on a
“Restore System Defaults->Misc”
Notes
– The format of the <string> must be four fields each separated by a comma,
Remote Language Compatibility Measurement Application Reference
486
5 System Settings
I/O Config
example:
:SYST:IDN “XYZ Corp,Model 12,012345,A.01.01”
– The four fields are <manufacturer>, <model number>, <serial number>,
<firmware revision>. Thus, the text within a field cannot contain a comma.
– This affects the response given in all Modes of the Analyzer, unless the current
Mode has also specified a custom response, in which case the current Mode’s
custom IDN response takes precedence over the System’s, but only while that
Mode is the current Mode..
– It survives shutdown and restart of the software and therefore survives a power
cycle
– Null string as parameter restores the Factory setting, example:
:SYST:IDN ""
LXI
Opens a menu that allows you to access the various LXI configuration properties.
LAN Reset
Resets the LAN connection. This will result in the following settings and will restart
the LAN operation:
– DHCP: Enabled
– Automatic IP Address: Enabled
– ICMP Ping Responder: Enabled
– Web Password: measure4u
– Dynamic DNS: Enabled
– mDNS and DNS-SD: Enabled
– Dynamic Link Local Addressing: Enabled
– Auto Negotiation: Enabled
There is no SCPI command for this function.
Restore I/O Config Defaults
Causes the group of settings associated with the I/O Config menu to be reset to their
default values. This also happens on a Restore Misc Defaults, which has a SCPI
command.
When Restore I/O Config Defaults is selected, a message appears saying:
487
Remote Language Compatibility Measurement Application Reference
5 System Settings
I/O Config
“This will reset all of the I/O Config variables to their default state, including the
GPIB address and SCPI LAN settings.
It will not affect Alignment data or settings.
This action cannot be undone. Do you want to proceed?”
The message provides an OK and Cancel button for the user to affirm or cancel the
operation.
Remote Language Compatibility Measurement Application Reference
488
5 System Settings
User Interface
User Interface
The User Interface panel lets you configure functions specific to the User Interface,
such as the menu panel orientation and the display color theme.
Menu Panel Position
Allows the Menu Panel to be positioned on the Right or Left side of the display.
Command
SYSTem:DISPlay:MPPosition RIGHt|LEFT
SYSTem:DISPlay:MPPosition?
Example
SYST:DISP:MPP LEFT
Preset
This is unaffected by a Preset but is set to RIGHt on a "Restore User Interface
Defaults" or "Restore System Defaults->All".
State Saved
Power On Persistent (survives shutdown and restart)
Menu Panel Tabs
Allows the Menu Panel Tabs to be positioned on the Right or Left side of the menu
panel.
Command
SYSTem:DISPlay:MPTab RIGHt|LEFT
SYSTem:DISPlay:MPTab?
489
Example
SYST:DISP:MPT LEFT
Preset
This is unaffected by a Preset but is set to RIGHt on a "Restore User Interface
Defaults" or "Restore System Defaults->All".
State Saved
Power On Persistent (survives shutdown and restart)
Remote Language Compatibility Measurement Application Reference
5 System Settings
User Interface
Annotations
This function overrides the annotation settings for all measurement in all modes and
turns them all off. This provides the security based "annotation off" function of
previous analyzers; hence it uses the legacy SCPI command.
When this control is set to All Off, the Screen Annotation, Meas Bar, Trace
Annotation, and Control Annotation keys under the Display, Annotation menu are
grayed out and forced to Off for all measurements in all modes. When Local Settings
is selected, you are able to set the local annotation settings on a measurement by
measurement basis.
Command
:DISPlay:WINDow[1]:ANNotation[:ALL] OFF|ON|0|1
:DISPlay:WINDow[1]:ANNotation[:ALL]?
Example
:DISP:WIND:ANN OFF
Preset
This is unaffected by a Preset but is set to ON on a "Restore User Interface
Defaults", “Restore Misc Defaults” or "Restore System Defaults->All".
State Saved
Power On Persistent (survives shutdown and restart)
Backwards Compatibility Notes
The WINDow parameter and optional subopcode is included for backwards
compatibility but ignored – all windows are equally affected.
Display Theme
This key allows you to change the Display theme. This is similar to the Themes
selection under Page Setup and Save Screen Image.
The two available themes are:
Filled:
This is the normal theme using filled objects
Outline:
This theme uses color but does not use fills. It is ideal for images that need to be
printed on inkjet printers. Although setting the Display Theme to Outline will not
affect screen image saves or prints, it will show you exactly how screen images will
look when using the Outline theme under Save Screen Image, and how prints will
look when using the Outline theme under Page Setup.
Command
:DISPlay:THEMe
TDColor|TDMonochrome|FCOLor|FMONochrome|FILLed|OUTLine
:DISPlay:THEMe?
Example
SYST:DISP:THEM OUTL ! sets the display style to Outline
Preset
This is unaffected by a Preset but is set to FILLed on a "Restore User
Interface Defaults", “Restore Misc Defaults” or "Restore System Defaults>All".
Remote Language Compatibility Measurement Application Reference
490
5 System Settings
User Interface
State Saved
Power On Persistent (survives shutdown and restart)
Notes
To permit code compatibility between X-Series Signal Analyzer instruments, the
command parameters will be mapped as follows:
FCOLor mapped to OUTLine
FMONochrome mapped to OUTLine
TDColor mapped to FILLed
TDMonochrome mapped to FILLed
The query of :DISPlay:THEMe? will always return FILLed or OUTLine, it will not
return FCOLor, FMONochrome, TDColor, or TDMonochrome.
Backlight
Turns the display backlight on and off. This setting may interact with settings under
the Windows "Power" menu.
When the backlight is off, pressing ESC, TAB, SPACE, ENTER, UP, DOWN, LEFT,
RIGHT, DEL, BKSP, CTRL, or ALT turns the backlight on without affecting the
application. Pressing any other key will turn backlight on and could potentially
perform the action as well.
Command
:DISPlay:BACKlight ON|OFF
:DISPlay:BACKlight?
Example
DISP:BACK ON
DISP:BACK OFF
Preset
ON
State Saved
Not Saved in State
Hints
Hints are descriptions that provide additional information for a control. This function
allows you to have Hints enabled or disabled.
Command
SYSTem:DISPlay:HINTs[:STATe] OFF|ON|0|1
SYSTem:DISPlay:HINTs?
491
Example
SYST:DISP:HINT OFF
Preset
This is unaffected by a Preset but is set to ON on a "Restore User Interface
Remote Language Compatibility Measurement Application Reference
5 System Settings
User Interface
Defaults" or "Restore System Defaults->All".
State Saved
Power On Persistent (survives shutdown and restart)
Numeric Entry Auto Open
Configures whether the Numeric Entry Panel will appear immediately when an
active function control is activated (Auto Open On), or be deferred until you touch it
again or begin to enter a value (Auto Open Off). When configured for Auto Open Off
(the default), adjusting the value with the front panel Up/Down keys or the RPG will
hide the Numeric Entry Panel.
Command
SYSTem:DISPlay:NEPimmediate ON|OFF|1|0
SYSTem:DISPlay:NEPimmediate?
Example
SYST:DISP:NEP OFF
Preset
This is unaffected by a Preset but is set to ON on a "Restore User Interface
Defaults" or "Restore System Defaults->All".
State Saved
Power On Persistent (survives shutdown and restart)
Touch
Turns the touch functionality on and off on the display. If Off, you can turn it back on
using the front panel Touch On/Off key, or by using a mouse to toggle this control.
Preset
Always starts up “ON”. Unaffected by a Preset but is turned on by "Restore
User Interface Defaults" or "Restore System Defaults->All".
State Saved
Not saved in state, not affected by preset, not Power On Persistent (does not
survive shutdown and restart).
Control Size
Configures the size of the controls in the user interface. This can be used to make
screen dumps from a large screen instrument match those from a smaller screen
instrument, to make the controls more readable on a large-screen instrument, or to
display more information on a smaller screen instrument.
Command
:DISPlay:UINTerface:CSIZe SMALl|LARGe
:DISPlay:UINTerface:CSIZe?
Example
DISP:UINT:CSIZ LARG
Preset
This is unaffected by a Preset but is set to SMALl on a "Restore User Interface Defaults" or
"Restore System Defaults->All".
State Saved
Power On Persistent (survives shutdown and restart)
Remote Language Compatibility Measurement Application Reference
492
5 System Settings
User Interface
Quick Save Mode
When Quick Save Mode is in Normal (the default setting), the instrument does an
immediate save of a new file of the same type and to the same directory as the
previous Save action.
When Quick Save Mode is in the Prompt state, instead of immediately performing a
Save, the Alpha Keyboard appears with the proposed auto-filename in the entry
area. You can then press Enter to accept the auto filename, or edit the name then
press Enter. This allows you to easily save a file with a custom file name.
Preset
This is unaffected by a Preset but is set to NORMal on a "Restore User Interface Defaults" or
"Restore System Defaults->All".
State Saved
Power On Persistent (survives shutdown and restart)
Language
Accesses the selection of language displayed on the menus and controls. English is
the default language. The selection of language is available when the instrument is
licensed with a language option.
All Measurement Applications that share common controls will display the localized
controls.
The description on the control labels is bounded by the control size. Any given
language will have labels in that language which are shorter or longer than the
equivalent label in English. Any localized text on the controls that does not fit the
label size will remain in English. Thus for any given menu, controls may be displayed
in English and the selected language. Also, labels that are acronyms, engineering, or
technology specific terms may remain in English.
All Application and Measurement names will remain in English.
All data in exported files will remain in English.
The Diagnostic and Service menus in the System Subsystem will remain in English.
The Windows operating system must remain in English. Changing the Region and
Language settings in the Windows Control Panel is not supported.
External keyboards in English are supported. Localized external keyboards are not
supported. When the language selected is not English, a message is presented to
the user that any external keyboards must remain English.
Other aspects of the Graphical User Interface remain in the English language. The
Remote User Interface, SCPI, remains in English.
If option AKT is installed and Russian is selected, Russian (русск ий) language is
displayed on the control labels.
Command
SYSTem:DISPlay:LANGuage ENGLish|RUSSian
SYSTem:DISPlay:LANGuage?
Example
493
SYST:DISP:LANG ENGL
Remote Language Compatibility Measurement Application Reference
5 System Settings
User Interface
SYST:DISP:LANG RUSS ! Requires Option AKT
Preset
This is unaffected by a Preset but is set to English on a "Restore User Interface
Defaults", “Restore Misc Defaults” or "Restore System Defaults->All".
Restore User Interface Defaults
Causes the group of settings associated with the User Interface menu to be reset to
their default values. This also happens on a Restore Misc Defaults.
When User Interface is selected, a message appears saying:
“This will reset all of the User Interface variables to their default state, including the
menu panel location, display theme, and language.
It will not affect Alignment data or settings.
This action cannot be undone. Do you want to proceed?”
The message provides an OK and Cancel button for the user to affirm or cancel the
operation.
Example
:SYST:DEF UINT
Remote Language Compatibility Measurement Application Reference
494
5 System Settings
Power On
Power On
Enables you to select how the instrument should power on.
Power On State
Enables you to select whether the instrument powers up in a default state or some
other state. The options are: Mode and Input/Output Defaults, User Preset and Last
State.
Command
:SYSTem:PON:TYPE MODE|USER|LAST
:SYSTem:PON:TYPE?
Example
:SYST:PON:TYPE MODE :SYST:PON:TYPE USER :SYST:PON:TYPE LAST
Preset
This is unaffected by a Preset but is set to Mode on a “Restore System
Defaults->All”
State Saved
No
Backwards Compatibility SCPI
:SYSTem:PON:TYPE PRESet
The “PRESet” parameter is supported for backward compatibility only and behaves
the same as MODE.
Backwards Compatibility Notes
The Preset Type key in legacy analyzers has been removed, and the Power On
toggle key has been replaced by this 1-of-N key in the System menu.
Mode and Input/Output Defaults
When the analyzer is powered on in Mode and Input/Output Defaults, it performs a
Restore Mode Defaults to all modes in the instrument and also performs a Restore
Input/Output Defaults.
Persistent parameters (such as Amplitude Correction tables or Limit tables) are not
affected at power on, even though they are normally cleared by Restore
Input/Output Defaults and/or Restore Mode Defaults.
User Preset
Sets Power On to User Preset. When the analyzer is powered on in User Preset, it
will User Preset each mode and switch to the power-on mode. Power On User
495
Remote Language Compatibility Measurement Application Reference
5 System Settings
Power On
Preset will not affect any settings beyond what a normal User Preset affects.
Backward Compatibility Note: Power On User Preset will cause the instrument to
power up in the power-on mode, not the last mode the instrument was in prior to
shut down. Also, Power On User Preset will User Preset all modes. This does not
exactly match legacy behavior.
An instrument could never power up for the first time in User Preset.
Last State
Sets Power On to Last. When the analyzer is powered on, it will put all modes in
the last state they were in prior to when the analyzer was put into Power Standby
and it will wake up in the mode it was last in prior to powering off the instrument.
The saving of the active mode prior to shutdown happens behind the scenes when
a controlled shutdown is requested by using the front panel power Standby key or
by using the remote command SYSTem:PDOWn. The non-active modes are saved
as they are deactivated and recalled by Power On Last State.
Power on Last State only works if you have done a controlled shutdown prior to
powering on in Last. If a controlled shutdown is not done when in Power On Last
State, the instrument will power up in the last active mode, but it may not power up
in the active mode’s last state. If an invalid mode state is detected, a Mode Preset
will occur. To control the shutdown under remote control use the :SYSTem:PDOWn
command.
Backward Compatibility Note:
It is no longer possible to power-up the analyzer in the last mode the analyzer
was running with that mode in the preset state. (ESA/PSA SYST:PRESET:TYPE
MODE with SYST:PON:PRESET) You can power-on the analyzer in the last mode
the instrument was running in its last state (SYST:PON:TYPE LAST), or you can
specify the mode to power-up in its preset state (SYST:PON:MODE <mode>).
An instrument can never power up for the first time in Last.
If line power to the analyzer is interrupted, for example by pulling the line cord plug or
by switching off power to a test rack, Power On Last State may not work properly. For
proper operation, Power On Last State depends on you shutting down the instrument
using the Standby key or the SYSTem:PDOWn SCPI command. This will ensure the last
state of each mode is saved and can be recalled during a power up.
Power On Application
Accesses a menu that lists the available Modes and lets you select which Mode is to
be the power-on application. Whichever application is selected runs at power on
when the Power On Type is set to “Mode and Input/Output Defaults”.
Command
:SYSTem:PON:MODE SA|RTSA|BASIC|PNOISE
:SYSTem:PON:MODE?
Example
SYST:PON:MODE SA
Preset
This is unaffected by a Preset but is set on a “Restore System Defaults->All”
Remote Language Compatibility Measurement Application Reference
496
5 System Settings
Power On
to: SA
State Saved
No
Restore Power On Defaults
This selection causes the Power On settings to be reset to their default value.
When this button is pressed, a message appears saying:
“This will reset Power On State and Power On Application to their default state.
It will not affect Alignment data or settings.
This action cannot be undone. Do you want to proceed?”
The message provides an OK and Cancel button for the user to affirm or cancel the
operation.
Example
:SYST:DEF PON
Configure Applications – Desktop Application
The Configure Applications utility is run from the Windows Desktop. You must close
the analyzer application before running Configure Applications.
Configure Applications can be used to:
– select applications for preload
– determine how many applications can fit in memory at one time
– specify the order of the Modes in the Mode menu.
This utility consists of a window with instructions, a set of “Select Application”
checkboxes, a “fuel bar” style memory gauge, and keys that help you set up your
configuration.
For more information, see the following topics:
Preloading Applications
During runtime, if a Mode that is not preloaded is selected using the Mode menu or
sending SCPI commands, there will be a pause while the Application is loaded.
During this pause a message that says “Loading application, please wait …” is
displayed. Once loaded, the application stays loaded, so the next time you select it
during a session, there is no delay.
Preloading enables you to “preload” at startup, to eliminate the runtime delay.
Preloading an application will cause it to be loaded into the analyzer’s memory
when the analyzer program starts up. If you do this, the delay will increase the time
it takes to start up the analyzer program, but this may be preferable to having to
wait the first time you select an application. Note that, once an application is
loaded into memory, it cannot be unloaded without exiting and restarting the
analyzer program.
497
Remote Language Compatibility Measurement Application Reference
5 System Settings
Power On
Note that there are more applications available for the X-Series than can fit into
Windows Virtual Memory. By allowing you to choose which licensed applications to
load at startup, the Configure Applications utility allows you to make optimal use of
your memory.
Access to Configure Applications utility
A version of the utility runs the first time you power up the analyzer after purchasing
it from Keysight. The utility automatically configures preloads so that as many
licensed applications as possible are preloaded while keeping the total estimated
virtual memory usage below the limit. This auto-configuration only takes place at
the very first run, and after analyzer software upgrades.
You may, at any time, manually call up the Configure Applications utility by closing
the analyzer application and double-tapping the Configure Applications icon on the
desktop.
When you run it, the utility looks like this:
Virtual memory usage
There are more applications available for the X-Series than can fit into memory at
any one time, so the Configure Applications utility includes a memory tracker that
serves two purposes:
Remote Language Compatibility Measurement Application Reference
498
5 System Settings
Power On
1. It will not let you preload more applications than will fit into memory at once.
2. You can determine how many of your favorite applications can reside in memory
at one time.
The utility provides a graphical representation of the amount of memory (note that
the memory in question here is Virtual memory and is a limitation imposed by the
operating system, not by the amount of physical memory you have in your
analyzer). You select applications to preload by checking the boxes on the left.
Checked applications preload at startup. The colored fuel bar indicates the total
memory required when all the checked applications are loaded (either preloaded or
selected during runtime).
Here is what the fuel bar colors mean:
– RED: the applications you have selected cannot all fit into the analyzer’s
memory. You must deselect applications until the fuel bar turns yellow.
– YELLOW: the applications you have selected can all fit into the analyzer’s
memory, but there is less than 10% of the memory left, probably not enough to
load any other applications, either via preload or by selecting a Mode while the
analyzer is running..
– GREEN: The indicator is green when <90% of the memory limit is consumed.
This means the applications you have selected can all fit into the analyzer’s
memory with room to spare. You will likely be able to load one or more other
applications without running out of memory.
Configure Applications - Instrument boot-up
At start-up of the analyzer program, a dialog box similar to the one you see when you
run Configure Applications may be displayed, allowing you to choose which licensed
applications are to be loaded.
This dialog is displayed only if the memory required to pre-load all of the licensed
applications exceeds the Virtual Memory available.
499
Remote Language Compatibility Measurement Application Reference
5 System Settings
Restore Defaults
Restore Defaults
Provides initialization of system setting groups, including the option to set the entire
instrument back to a factory default state.
State Saved
No
Input/Output
Input/Output Preset resets the group of settings and data associated with the
Input/Output front-panel key to their default values. These settings are not affected
by a Mode Preset because they are generally associated with connections to the
instrument, and most users would not want these resetting every time they pressed
the Mode Preset key.
By using Input/Output Preset and Restore Mode Defaults, a full preset of the current
mode will be performed, with the caveat that since Input/Output Preset is a global
function it will affect ALL modes.
This is the same as the Input/Output Preset button in the Preset dropdown and the
Input/Output menu.
When Input/Output is selected, a message appears saying:
“This will reset all of the Input/Output variables to their default state, including
which input is selected, all Amplitude Correction settings and data, all External
Mixing settings, all Frequency Reference settings and all Output settings.
It will not affect Alignment data or settings.
This action cannot be undone. Do you want to proceed?”
The message provides an OK and Cancel button for the user to affirm or cancel the
operation.
Example
:SYST:DEF INP
I/O Config
Causes the group of settings associated with the I/O Config menu to be reset to their
default values. This also happens on a Restore Misc Defaults, which has a SCPI
command, although I/O Config does not.
When I/O Config is selected, a message appears saying:
“This will reset all of the I/O Config variables to their default state, including the
GPIB address and SCPI LAN settings.
It will not affect Alignment data or settings.
This action cannot be undone. Do you want to proceed?”
Remote Language Compatibility Measurement Application Reference
500
5 System Settings
Restore Defaults
The message provides an OK and Cancel button for the user to affirm or cancel the
operation.
User Interface
Causes the group of settings associated with the User Interface menu to be reset to
their default values. This also happens on a Restore Misc Defaults.
When User Interface is selected, a message appears saying:
“This will reset all of the User Interface variables to their default state,
including the menu panel location, display theme, and language.
It will not affect Alignment data or settings.
This action cannot be undone. Do you want to proceed?”
The message provides an OK and Cancel button for the user to affirm or cancel the
operation.
Example
:SYST:DEF UINT
Power On
This selection causes the Power On settings to be reset to their default value.
The Power On settings are Power On State and Power On Application.
When Power On is selected, a message appears saying:
“This will reset Power On State and Power On Application to their default state.
It will not affect Alignment data or settings.
This action cannot be undone. Do you want to proceed?”
The message provides an OK and Cancel button for the user to affirm or cancel the
operation.
Example
:SYST:DEF PON
Alignments
This selection causes the Alignment system settings to be reset to their default
values. This does not affect any Alignment data stored in the system.
After performing this function, it may impact the auto-alignment time of the
instrument until a new alignment baseline has been established.
When Alignments is selected, a message appears saying:
“This will reset all of the settings for the Alignment system to their default
values.
No alignment data will be erased.
This action cannot be undone. Do you want to proceed?”
501
Remote Language Compatibility Measurement Application Reference
5 System Settings
Restore Defaults
The message provides an OK and Cancel button for the user to affirm or cancel the
operation.
Example
:SYST:DEF ALIG
Misc
This selection causes miscellaneous system settings to be reset to their default
values. With this reset, you lose the GPIB address and it is reset to 18, so this should
be used with caution.
When Misc is selected, a message appears saying:
“This will reset miscellaneous system settings to their default values. This
includes settings for I/O Config (GPIB and SCPI LAN), the User Interface, the
Save/Recall system, and the Preset type.
It will not affect Alignment data or settings.
This action cannot be undone. Do you want to proceed?”
The message provides an OK and Cancel button for the user to affirm or cancel the
operation.
Example
:SYST:DEF MISC
This miscellaneous group contains the rest of the settings that have not been part of
the other Restore System Defaults groups. These include:
– All settings on the I/O Config page of the System Settings dialog
– All settings in the following table:
Miscellaneous Setting
Default Value
The SYST:PRES:TYPE
MODE
Auto File Name Number
000
Save Type
State
State Save To
Register 1
Screen Save To
SCREEN000.png
Save/Recall Shortcuts
Deleted
Display Theme
Filled
Backlight
ON
System Annotation
Local Settings
Language
English
DISP:ENABle
ON
Full Screen
Off
Remote Language Compatibility Measurement Application Reference
502
5 System Settings
Restore Defaults
All
This performs a comprehensive reset of ALL analyzer settings to their factory default
values.It resets all of the system setting groups, causes a Restore Mode Defaults for
all modes in the instrument, and switches back to the power-on mode. It does not
affect the User Preset file or any user saved files.
When All is selected, a message appears saying:
“This will reset all of the settings in the instrument to their factory default
values, including the state of all Modes and Screens, the GPIB settings, the
Alignment settings, and the Power On Mode.
It will not affect Alignment data or settings.
This action cannot be undone. We recommend canceling this operation and
restoring settings individually (I/O Config, User Interface, Alignments, etc)
instead.
Do you want to proceed?”
The message provides an OK and Cancel button for the user to affirm or cancel the
operation.
If you are using a Keysight USB External Mixer, then you will need to perform a Refresh
USB Mixer Connection after Restoring All Defaults.
Example
:SYST:DEF ALL
Notes
If using a Keysight USB External Mixer, perform a Refresh USB Mixer Connection
(SCPI command :MIX:BAND USB) following a Restore All Defaults.
Couplings
An All will cause the currently running measurement to be aborted and get all
modes to a consistent state, so it is unnecessary to couple any settings.
Backward compatible Restore System Defaults
Command
:SYSTem:PRESet:PERSistent
Example
SYST:PRES:PERS
Notes
SYST:PRES:PERS is exactly the same as :SYST:DEF ALL
503
Remote Language Compatibility Measurement Application Reference
5 System Settings
Alignments
Alignments
The Alignments menu gives you access to the alignment system of the instrument.
You can control the automatic alignments, view alignment statistics and manually
perform alignments.
The current setting of the alignment system is displayed in the Meas Bar along the
top of the display. This annotation will be in amber for conditions that may cause
specifications to be impacted.
Auto Align
Lets you configure the automatic background alignments and the alerts from the
automatic alignment system.
Auto Align
Configures the method the automatic background alignment will use when it runs.
Automatic background alignments are run periodically between measurement
acquisitions. The instrument’s software determines when alignments are to be
performed to maintain warranted operation. The recommended setting for Auto
Align is Normal.
An Auto Align execution cannot be aborted with the Cancel (ESC) key. To interrupt
an Auto Align execution, select Auto Align Off.
Command
:CALibration:AUTO ON|LIGHt|PARTial|OFF
:CALibration:AUTO?
Example
:CAL:AUTO ON
Preset
This is unaffected by Preset but is set to ON upon a “Restore System
Defaults->Align”.
State Saved
No
Notes
While Auto Align is executing, bit 0 of Status Operation register is set.
Couplings
Auto Align is set to Off if Restore Align Data is invoked.
Status Bits/OPC dependencies
When Auto Align is executing, bit 0 in the Status Operational register is set.
Backwards Compatibility SCPI
:CALibration:AUTO ALERt
Parameter ALERt is for backward compatibility only and is mapped to PARTial
Backwards Compatibility Notes
1. ESA SCPI for Auto Align is :CALibration:AUTO <Boolean>. The command for XSeries is an enumeration. Thus the parameters of “0” and “1” are not possible in X-
Remote Language Compatibility Measurement Application Reference
504
5 System Settings
Alignments
Series.
2. Similarly, the ESA SCPI for :CALibration:AUTO? returned the Boolean value 1 or
0, in X-Series it is an Enumeration (string). Thus, queries by customer applications
into numeric variables will result in an error
3. In PSA Auto Align OFF was not completely off, it is equivalent to PARTial in XSeries. In X-Series, OFF will be fully OFF. This means users of PSA SCPI who
choose OFF may see degraded performance and should migrate their software to
use PARTial.
The available settings for Auto Align are as follows:
Normal
Example:CAL:AUTO ON
Auto Align, Normal turns on the automatic alignment of all measurement systems.
The Auto Align, Normal selection maintains the instrument in warranted operation
across varying temperature and over time.
If the condition “Align Now All required” is set, transition to Auto Align, Normal will
perform the required alignments and clear the “Align Now All required” condition
and then continue with further alignments as required to maintain the instrument
adequately aligned for warranted operation.
When Auto Align, Normal is selected the Auto Align Off time is set to zero.
When Auto Align, Normal is selected the Meas Bar indicates Align: Auto (in white)
or Align: Auto/No RF (in amber). The amber color is intended to inform you that you
are responsible for maintaining the RF alignment of the instrument.
An interfering user signal may prevent automatic alignment of the RF subsystem. If
this occurs, the Error Condition message “Align skipped: 50 MHz interference” or
“Align skipped: 4.8 GHz interference” is reported, the Status Questionable
Calibration bit 11 is set, and the alignment proceeds. When a subsequent
alignment of the RF subsystem succeeds, either by the next cycle of automatic
alignment or from an Align Now, RF, the Error Condition and Status Questionable
Calibration bit 11 are cleared.
Alignment processing as a result of the transition to Normal will be executed
sequentially. Thus, *OPC? or *WAI following CAL:AUTO ON will return when the
alignment processing is complete.
Light
Example: :CAL:AUTO LIGH
Auto Align, Light turns on the automatic alignment of all measurement systems.
The Auto Align, Light selection allows considerably more drift in amplitude accuracy
in order to allow much less frequent measurement interruptions to perform
alignments. The temperature changes required to trigger each alignment are
increased by a factor of three. Alignments also expire from time as well as
temperature. In a stable thermal environment, the alignments occur one-ninth as
often as in Normal. With these less frequent alignments, all accuracy specifications
(those expressed with ±x dB tolerances) change by nominally a factor of 1.4.
505
Remote Language Compatibility Measurement Application Reference
5 System Settings
Alignments
If the condition “Align Now, All required” is set, transition to Auto Align, Light will
perform the required alignments and clear the “Align Now, All required” condition
and then continue with further alignments as required to maintain the instrument
adequately aligned for warranted operation.
Alignment processing as a result of the transition to LIGHT will be executed
sequentially. Thus, *OPC? or *WAI following CAL:AUTO LIGHT will return when the
alignment processing is complete.
When Auto Align, Light is selected the Auto Align Off time is set to zero.
When Auto Align, Light is selected the Settings Panel indicates Align: Light.
Partial
Example:CAL:AUTO PART
Auto Align, Partial disables the full automatic alignment and the maintenance of
warranted operation for the benefit of improved measurement throughput.
Accuracy is retained for the Resolution Bandwidth filters and the IF Passband,
which is critical to FFT accuracy, demodulation, and many measurement
applications. With Auto Align set to Partial, you are now responsible for maintaining
warranted operation by updating the alignments when they expire. The Auto Align,
Alert mechanism will notify you when alignments have expired. One solution to
expired alignments is to perform the Align All, Now operation. Another is to return
the Auto Align selection to Normal.
Auto Align, Partial is recommended for measurements where the throughput is so
important that a few percent of improvement is more valued than an increase in the
accuracy errors of a few tenths of a decibel. One good application of Auto Align,
Partial would be an automated environment where the alignments can be called
during overhead time when the device-under-test is exchanged.
When Auto Align,Partial is selected the elapsed time counter begins for Auto Align
Off time.
When Auto Align,Partial is selected the Settings Panel indicates Align: Partial in an
amber color. The amber color is to inform the operator that they are responsible for
maintaining the warranted operation of the instrument.
Off
Example :CAL:AUTO OFF
Auto Align Off disables automatic alignment and the maintenance of warranted
operation, for the benefit of maximum measurement throughput. With Auto Align
set to Off, you are now responsible for maintaining warranted operation by
updating the alignments when they expire. The Auto Align, Alert mechanism will
notify you when alignments have expired. One solution to expired alignments is to
perform the Align All, Now operation. Another is to return the Auto Align selection
to Normal.
The Auto Align Off setting is rarely the best choice, because Partial gives almost
the same improvement in throughput while maintaining the warranted
performance for a much longer time. The choice is intended for unusual
Remote Language Compatibility Measurement Application Reference
506
5 System Settings
Alignments
circumstances such as the measurement of radar pulses where you might like the
revisit time to be as consistent as possible.
When Auto Align Off is selected the Auto Align Off time is initialized and the elapsed
time counter begins.
WhenAuto Align Off is selected the Settings Panel indicates Align: Off in an amber
color. The amber color is to inform the operator that they are responsible for
maintaining the warranted operation of the instrument.
All But RF
This controlconfigures automatic alignment to include or exclude the RF subsystem.
(Eliminating the automatic alignment of the RF subsystem prevents the input
impedance from changing. The normal input impedance of 50 ohms can change to an
open circuit when alignments are being used. Some devices under test do not
behave acceptably under such circumstances, for example by showing instability.)
When All but RF is ON is selected, the operator is responsible for performing an Align
Now RF when RF-related alignments expire. The Auto Align, Alert mechanism will
notify the operator to perform an Align Now All when the combination of time and
temperature variation is exceeded.
When All But RF is ON the Settings Panel indicates Align: Auto/No RF (in amber). The
amber color is intended to inform you that you are responsible for maintaining the RF
alignment of the instrument.
Command
:CALibration:AUTO:MODE ALL|NRF
:CALibration:AUTO:MODE?
Example
:CAL:AUTO:MODE NRF
Preset
This is unaffected by Preset but is set to ALL on a “Restore System Defaults>Align”.
State Saved
No
Alert
The instrument will signal an Alert when conditions exist such that you will need to
perform a full alignment (for example, Align Now All). The Alert can be configured in
one of four settings; Time & Temperature, 24 hours, 7 days, or None.
With Auto Align set to Normal, the configuration of Alert is not relevant because the
instrument’s software maintains the instrument in warranted operation.
A confirmation is required when a selection other than Time & Temperature is
chosen. This prevents accidental deactivation of alerts.When setting Alert from the
front panel to any value but Time and Temperature, confirmation is required to
transition into this setting of Alert. The confirmation dialog is:
“This will suppress alerts from the Alignment system, which would notify you
when an Alignment is required to maintain warranted operation. Without the
alerts you will be responsible for performing an Align Now All at appropriate
intervals to maintain warranted operation.
Do you want to proceed?”
507
Remote Language Compatibility Measurement Application Reference
5 System Settings
Alignments
The message provides an OK and Cancel button for the user to affirm or cancel the
setting change.
No confirmation is required when Alert is configured through a remote command.
For more information see "Time & Temperature" on page 508.
Command
:CALibration:AUTO:ALERt
TTEMperature|DAY|WEEK|NONE
:CALibration:AUTO:ALERt?
Example
:CAL:AUTO:ALER TTEM
Preset
This is unaffected by Preset but is set to TTEMperature on a
“Restore Alignment Defaults.
State Saved
No
Status Bits/OPC dependencies
When an alert is generated, the condition message “Align Now All required”
appears in the Status Bar, and bit 14 is set in the Status Questionable Calibration
register.
The settings for alert are detailed below.
Time & Temperature
SCPI example CAL:AUTO:ALER TTEM
With Auto Align Alert set to Time & Temperature the instrument will signal an alert
when alignments expire due to the combination of the passage of time and changes
in temperature. The alert is the Error Condition message “Align Now All required”. If
this choice for Alert is selected, the absence of an alert means that the analyzer
alignment is sufficiently up-to-date to maintain warranted accuracy.
24 hours
SCPI example CAL:AUTO:ALER DAY
With Auto Align Alert set to 24 Hours the instrument will signal an alert after a time
span of 24 hours since the last successful full alignment (for example, Align Now All
or completion of a full Auto Align). You may choose this selection in an environment
where the temperature is stable on a daily basis at a small risk of accuracy errors in
excess of the warranted specifications. The alert is the Error Condition message
“Align Now All required”.
7 days
SCPI example CAL:AUTO:ALER WEEK
With Auto Align Alert is set to 7 days the instrument will signal an alert after a time
span of 168 hours since the last successful full alignment (for example, Align Now
All or completion of a full Auto Align). You may choose this selection in an
environment where the temperature is stable on a weekly basis, at a modest risk of
accuracy degradations in excess of warranted performance. The alert is the Error
Condition message “Align Now All required”.
Remote Language Compatibility Measurement Application Reference
508
5 System Settings
Alignments
None
SCPI example CAL:AUTO:ALER NONE
With Auto Align Alert set to None the instrument will not signal an alert. This is
provided for rare occasions where you are making a long measurement which
cannot tolerate Auto Align interruptions, and must have the ability to capture a
screen image at the end of the measurement without an alert posted to the display.
Keysight does not recommend using this selection in any other circumstances,
because of the risk of accuracy performance drifting well beyond expected levels
without the operator being informed.
Align Now
Accesses alignment processes that are immediate action operations. They perform
complete operations and run until they are complete.
Executing immediate alignments from SCPI can be problematic due to the length of
time required for the alignments to complete. Alignment commands are by their
nature sequential, meaning they must complete before any other SCPI commands
can be processed. In many cases the alignment itself will take longer than the
typical SCPI timeout value. Furthermore status cannot be easily queried while a
sequential command is running.
For this reason, overlapped versions of the Align Now commands are provided.
When using these No-Operation-Pending (NPENDing) commands, the SCPI thread
will not be blocked (will be released immediately), so that the user can use
“:STATus:OPERation:CONDition?” to query the alignment status bit and use
“STATus:QUEStionable:CALibration:CONDition?” to check the alignment results. As
an example: :CALibration[:ALL]:NPENding is the overlapped replacement of
:CALibration[:ALL].
While the alignment is performing, the coming NOP calibration will be ignored, and
error message “SettingConflict, Alignment is in process.” will be posted. Also, any
other operations to the instrument will be pended and postponed until the alignment
is completed. The operations include: Preset, Initiate a new measurement, Device
clear and so on. Accordingly, changing parameters will not take effect although the
UI is updated immediately. So to avoid unexpected timeouts and results, these
operations are not suggested during any such alignments.
Align Now All but RF
Immediately executes an alignment of all subsystems except the RF subsystem. The
instrument will stop any measurement currently underway, perform the alignment,
and then restart the measurement from the beginning (similar to pressing the
Restart key). This can be used to align portions of the instrument that are not
impacted by an interfering user input signal.
This operation might be chosen instead of All if you do not want the device under test
to experience a large change in input impedance, such as a temporary open circuit at
the analyzer input.
509
Remote Language Compatibility Measurement Application Reference
5 System Settings
Alignments
The query form of the remote commands (:CALibration:NRF?) will invoke the
alignment and return a success or failure value.
Successful completion of Align Now All but RF will clear the “Align Now All required”
Error Condition, and clear bit 14 in the Status Questionable Calibration register. If
“Align Now All required” was in effect prior to executing the All but RF, the Error
Condition message “Align Now RF required” is generated and bit 12 in the Status
Questionable Calibration register is set. It will also begin the elapsed time counter
for Last Align Now All Time, and capture the Last Align Now All Temperature.
Align Now All but RF can be interrupted by pressing the Cancel (ESC) front-panel
key or remotely with Device Clear followed by the :ABORt SCPI command. When
this occurs the Error Condition message “Align Now All required” is generated, and
bit 14 is set in the Status Questionable Condition register. This is because new
alignment data may be used for an individual subsystem, but not a full new set of
data for all subsystems.
Command
:CALibration:NRF
:CALibration:NRF?
Example
:CAL:NRF
Notes
:CALibration:NRF? returns 0 if successful
:CALibration:NRF? returns 1 if failed
While Align Now All but RF is performing the alignment, bit 0 in the Status
Operation register is set. Completion, or termination, will clear bit 0 in the Status
Operation register.
This command is sequential; it must complete before further SCPI commands are
processed. Interrupting the alignment from remote is accomplished by invoking
Device Clear followed by the :ABORt command.
Successful completion will clear bit 14 in the Status Questionable Calibration
register and set bit 12 if invoked with “Align Now All required”.
Couplings
Initializes the time for the Last Align Now All Time.
Records the temperature for the Last Align Now All Temperature.
Status Bits/OPC dependencies
Bits 12 or 14 may be set in the Status Questionable Calibration register.
Align Now All but RF (Overlapped)
Command
:CALibration:NRF:NPENding
Example
CAL:NRF:NPEN
Notes
:CALibration:NRF:NPENding is the same as :CALibration:NRF
Remote Language Compatibility Measurement Application Reference
510
5 System Settings
Alignments
including all conditions, status register bits, except that this scpi command does not
BLOCK the scpi session, so the user should use status register bits to query if the
calibration is successfully completed or not.
Typical usage is:
1):CALibration:NRF:NPENding (start theAll but RF calibration)
2):STATus:OPERation:CONDition? (If bit 0 is set, then the system is doing
calibration, the user should do re-query until this bit is cleared )
3):STATus:QUEStionable:CALibration:CONDition? ( to check if there are any
errors/failures in previous calibration procedure)
Align Now RF
Immediately executes an alignment of the RF subsystem. The instrument stops any
measurement currently underway, performs the alignment, then restarts the
measurement from the beginning (similar to pressing the Restart key).
This operation might be desirable if the alignments had been set to not include RF
alignments, or if previous RF alignments could not complete because of interference
which has since been removed.
If an interfering user signal is present at the RF Input, the alignment will terminate
and generate the Error Condition message “Align skipped: 50 MHz interference” or
“Align skipped: 4.8 GHz interference”, and Error Condition “Align Now, RF required”.
In addition, bits 11 and 12 will be set in the Status Questionable Calibration register.
The query form of the remote commands (:CALibration:RF?) will invoke the alignment
of the RF subsystem and return a success or failure value. An interfering user signal
is grounds for failure.
Successful completion of Align Now, RF will begin the elapsed time counter for Last
Align Now, RF Time, and capture the Last Align Now, RF Temperature.
Align Now, RF can be interrupted by pressing the Cancel (ESC) front-panel key or
remotely with Device Clear followed by the :ABORt SCPI command. When this
occurs, the Error Condition message “Align Now, RF required” is generated, and bit
12 is set in the Status Questionable Condition register. None of the new alignment
data is used.
Command
:CALibration:RF
:CALibration:RF?
Example
:CAL:RF
Notes
:CALibration:RF? returns 0 if successful
:CALibration:RF? returns 1 if failed (including interfering user signal)
While Align Now, RF is performing the alignment, bit 0 in the Status Operation
register is set. Completion, or termination, will clear bit 0 in the Status Operation
register.
511
Remote Language Compatibility Measurement Application Reference
5 System Settings
Alignments
This command is sequential; it must complete before further SCPI commands are
processed. Interrupting the alignment from remote is accomplished by invoking
Device Clear followed by the :ABORt command.
Successful completion clears the Error Conditions “Align skipped: 50 MHz
interference” and “Align skipped: 4800 MHz interference” and the Error Conditions
“Align RF failed” and “Align Now, RF required”, and clears bits 3, 11, and 12 in the
Status Questionable Calibration register.
A failure encountered during alignment will generate the Error Condition message
“Align RF failed” and set bit 3 in the Status Questionable Calibration register.
An interfering user signal will result in bits 11 and 12 to be set in the Status
Questionable Calibration register to indicate Align Now, RF is required.
An interfering user supplied signal will result in the instrument requiring an Align
Now, RF with the interfering signal removed.
Couplings
Initializes the time for the Last Align Now, RF Time.
Records the temperature for the Last Align Now, RF Temperature.
Status Bits/OPC dependencies
Bits 11, 12, or 14 may be set in the Status Questionable Calibration register.
Align Now, RF (Overlapped)
Command
:CALibration:RF:NPENding
Example
CAL:RF:NPEN
Notes
:CALibration:RF:NPENding is the same as :CALibration:RF
including all conditions, status register bits, except that this scpi command does
not BLOCK the scpi session, so the user should use status register bits to query if
the calibration is successfully completed or not.
Typical usage is:
1):CALibration:RF:NPENding (Start a RF calibration)
2):STATus:OPERation:CONDition? (If bit 0 is set, then the system is doing
calibration, the user should do re-query until this bit is cleared )
3):STATus:QUEStionable:CALibration:CONDition? ( to check if there are any
errors/failures in previous calibration procedure)
Align Now External Mixer
Immediately executes an alignment of the External Mixer that is plugged into the
USB port. The instrument stops any measurement currently underway, performs the
alignment, then restarts the measurement from the beginning (similar to pressing
Remote Language Compatibility Measurement Application Reference
512
5 System Settings
Alignments
the Restart key). As this alignment calibrates the LO power to the mixer, this is
considered an LO alignment; and failure is classified as an LO alignment failure.
The query form of the remote commands (:CALibration:EMIXer?) will invoke the
alignment of the External Mixer and return a success or failure value.
Command
:CALibration:EMIXer
:CALibration:EMIXer?
Example
:CAL:EMIX
Notes
:CAL:EMIX? returns 0 if successful
:CAL:EMIX? returns 1 if failed
While Align Now, Ext Mix is performing the alignment, bit 0 in the Status Operation
register is set. Completion, or termination, will clear bit 0 in the Status Operation
register.
This command is sequential; it must complete before further SCPI commands are
processed. Interrupting the alignment from remote is accomplished by invoking
Device Clear followed by the :ABORt command.
A failure encountered during alignment will generate the Error Condition message
“Align LO failed” and set bit 5 in the Status Questionable Calibration register.
Successful completion will clear the “Align LO failed” message and bit 5 in the
Status Questionable Calibration register.
Dependencies
This key does not appear unless option EXM is present and is grayed-out unless a
USB mixer is plugged in to the USB.
Status Bits/OPC dependencies
Bit3 may be set in the Status Questionable Calibration Extended Failure register.
Show Alignment Statistics
Shows alignment information you can use to ensure that the instrument is operating
in a specific manner. The Show Alignment Statistics screen is where you can view
time and temperature information.
Values which are displayed are only updated when the Show Alignment Statistics
screen is invoked, they are not updated while the Show Alignment Statistics screen
is being displayed. The remote commands that access this information obtain
current values.
An example of the Show Alignment Statistics screen :
513
Remote Language Compatibility Measurement Application Reference
5 System Settings
Alignments
A successful Align Now, RF will set the Last Align RF temperature to the current
temperature, and reset the Last Align RF time. A successful Align Now All or Align
Now All but RF will set the Last Align Now All temperature to the current
temperature, and reset the Last Align Now All time. A successful Align Now All will
also reset the Last Align RF items if the RF portion of the Align Now succeeded.
Notes
The values displayed on the screen are only updated upon entry to the screen and
not updated while the screen is being displayed.
Current Start-up Time SCPI
Command
:SYSTem:PON:TIME?
Example
:SYST:PON:TIME?
State Saved
No
Notes
Value is the time since the most recent start-up in seconds.
Current Alignment Temperature SCPI
Command
:CALibration:TEMPerature:CURRent?
Example
:CAL:TEMP:CURR?
State Saved
No
Remote Language Compatibility Measurement Application Reference
514
5 System Settings
Alignments
Notes
Value is in degrees Centigrade.
Value is invalid if using default alignment data (Align Now All required)
Last Align Now All Time SCPI
Command
:CALibration:TIME:LALL?
Example
:CAL:TIME:LALL?
State Saved
No
Notes
Value is the elapsed time, in seconds, since the last successful Align Now All or
Align Now All but RF was executed.
Last Align Now All Temperature SCPI
Command
:CALibration:TEMPerature:LALL?
Example
:CAL:TEMP:LALL?
State Saved
No
Notes
Value is in degrees Centigrade at which the last successful Align Now All or Align
Now All but RF was executed.
Last Align Now, RF Time SCPI
Command
:CALibration:TIME:LRF?
Example
:CAL:TIME:LRF?
State Saved
No
Notes
Value is the elapsed time, in seconds, since the last successful Align Now, RF was
executed, either individually or as a component of Align Now All.
Last Align Now, RF Temperature SCPI
Command
:CALibration:TEMPerature:LRF?
Example
:CAL:TEMP:LRF?
State Saved
No
Notes
Value is in degrees Centigrade at which the last successful Align Now, RF was
executed, either individually or as a component of Align Now All.
515
Remote Language Compatibility Measurement Application Reference
5 System Settings
Alignments
Last Characterize Preselector Time SCPI
Command
:CALibration:TIME:LPReselector?
Example
:CAL:TIME:LPR?
State Saved
No
Notes
Value is the date and time the last successful Characterize Preselector was
executed. The date is separated from the time by a space character. Returns “” if no
Characterize Preselector has ever been performed on the instrument.
Dependencies
In models that do not include preselectors, this command is not enabled and any
attempt to set or query will yield an error.
Last Characterize Preselector Temperature SCPI
Command
:CALibration:TEMPerature:LPReselector?
Example
:CAL:TEMP:LPR?
State Saved
No
Notes
Value is in degrees Centigrade at which the last successful Characterize
Preselector was executed.
Dependencies
In models that do not include preselectors, this command is not enabled and any
attempt to set or query will yield an error.
Auto Align Off Time SCPI
Command
:CALibration:AUTO:TIME:OFF?
Example
:CAL:AUTO:TIME:OFF?
State Saved
No
Notes
Value is the elapsed time, in seconds, since Auto Align has been set to Off or Off
with Alert. The value is 0 if Auto Align is ALL or NORF.
Last Align Now, Conducted Time SCPI
Command
:CALibration:TIME:RFPSelector:LCONducted?
Example
:CAL:TIME:RFPS:LCON?
State Saved
No
Notes
Values are the date and time the last successful Align Now, 20 Hz – 30 MHz was
Remote Language Compatibility Measurement Application Reference
516
5 System Settings
Alignments
executed. The date is separated from the time by a semi-colon character.
Last Align Now, Conducted Temperature SCPI
Command
:CALibration:TEMPerature:RFPSelector:LCONducted?
Example
:CAL:TEMP:RFPS:LCON?
State Saved
No
Notes
Value is in degrees Centigrade at which the last successful Align Now, 20 Hz – 30
MHz was executed.
Last Align Now, Radiated Time SCPI
Command
:CALibration:TIME:RFPSelector:LRADiated?
Example
:CAL:TIME:RFPS:LRAD?
State Saved
No
Notes
Value is the date and time the last successful Align Now, 30 MHz – 3.6 GHz was
executed. The date is separated from the time by a semi-colon character.
Last Align Now, Radiated Temperature SCPI
Command
:CALibration:TEMPerature:RFPSelector:LRADiated?
Example
:CAL:TEMP:RFPS:LRAD?
Notes
Value is in degrees Centigrade at which the last successful Align Now, 30 MHz –
3.6 GHz was executed.
Timebase DAC
This screen allows you to change the setting of the Timebase DAC from a factory
calibrated setting to your own desired setting.
The display shows the current Timebase DAC setting at the top, and gives you a
choice of Calibratedor User setting. There is also a field for you to enter your desired
setting.
Timebase DAC
Allows control of the internal 10 MHz reference oscillator timebase. This may be
used to adjust for minor frequency alignment between your signal’s reference and
the internal frequency reference. This adjustment has no effect if the instrument is
operating with an External Frequency Reference.
If the value of the Timebase DAC changes (by switching to Calibrated from User with
User Value set to a different value, or in User with a new value entered) an alignment
517
Remote Language Compatibility Measurement Application Reference
5 System Settings
Alignments
may be necessary. The alignment system will take appropriate action; which will
either invoke an alignment or cause an Alert.
The Calibrated setting sets the Timebase DAC to the value established during
factory or field calibration. In this case the value displayed at the top of the screen is
the calibrated value.
The User setting sets the Timebase DAC to the value set on the User Value control.
In this case the value displayed at the top of the screen is the user value.
Command
:CALibration:FREQuency:REFerence:MODE CALibrated|USER
:CALibration:FREQuency:REFerence:MODE?
Example
:CAL:FREQ:REF:MODE CAL
Preset
This is unaffected by Preset but is set to CALibrated on a “Restore
System Defaults->Align”.
State Saved
Notes
If the value of the timebase is changed the alignment system automatically
performs an alignment or alerts that an alignment is due.
If the value of the timebase is changed the alignment system automatically
performs an alignment or alerts that an alignment is due.
User Value
Allows setting the Timebase DAC to a value other than the value established during
the factory or field calibration. The value displayed on the menu key is the calibrated
value.
Command
:CALibration:FREQuency:REFerence:FINE <integer>
:CALibration:FREQuency:REFerence:FINE?
Example
:CAL:FREQ:REF:FINE 8191
Preset
This is unaffected by Preset but is set to the factory setting on a
“Restore System Defaults->Align”.
State Saved
Notes
If the value of the timebase is changed the alignment system automatically
performs an alignment or alerts that an alignment is due.
Couplings
Setting :CAL:FREQ:REF:FINE sets :CAL:FREQ:REF:MODE USER
Backwards Compatibility SCPI
:CALibration:FREQuency:REFerence:COARse
! ESA hardware contained two DAC controls for the Timebase. In X-Series the
command :CALibration:FREQuency:REFerence:FINE is the method for adjusting the
timebase. The :COARse command is provided as an alias to :FINE.
Remote Language Compatibility Measurement Application Reference
518
5 System Settings
Alignments
:CALibration:FREQuency:REFerence:COARse <integer>
Command
:CALibration:FREQuency:REFerence:COARse?
Example
:CAL:FREQ:REF:COAR 8191
Notes
This is an alias for CAL:FREQ:REF:FINE any change to COARse is
reflected in FINE and vice-versa. See CAL:FREQ:REF:FINE for
description of functionality.
Couplings
Setting :CAL:FREQ:REF:COAR sets :CAL:FREQ:REF:MODE USER
State Saved
Advanced
Accesses alignment processes that are immediate action operations that perform
operations that run until complete. Advanced alignments are performed on an
irregular basis, or require additional operator interaction.
Characterize Preselector
The Preselector tuning curve drifts over temperature and time. Recognize that the
Amplitude, Presel Center function adjusts the preselector for accurate amplitude
measurements at an individual frequency. Characterize Preselector improves the
amplitude accuracy by ensuring the Preselector is approximately centered at all
frequencies without the use of the Amplitude, Presel Center function. Characterize
Preselector can be useful in situations where absolute amplitude accuracy is not of
utmost importance, and the throughput savings or convenience of not performing a
Presel Center is desired. Presel Center is required prior to any measurement for best
(and warranted) amplitude accuracy.
More Information
Keysight recommends that the Characterize Preselector operation be performed
yearly as part of any calibration, but performing this operation every three months
can be worthwhile.
Characterize Preselector immediately executes a characterization of the
Preselector, which is a YIG-tuned filter (YTF). The instrument stops any
measurement currently underway, performs the characterization, then restarts the
measurement from the beginning (similar to pressing the Restart key).
The query form of the remote commands (:CALibration:YTF?) will invoke the
alignment of the YTF subsystem and return a success or failure value.
A failure encountered during alignment will generate the Error Condition message
“Characterize Preselector failure” and set bit 3 in the
STATus:QUEStionable:CALibration:EXTended:FAILure status register. Successful
completion of Characterize Preselector will clear this Condition. It will also begin
the elapsed time counter for Last Characterize Preselector Time, and capture the
Last Characterize Preselector Temperature.
The last Characterize Preselector Time and Temperature survives across the
power cycle as this operation is performed infrequently.
519
Remote Language Compatibility Measurement Application Reference
5 System Settings
Alignments
Command
:CALibration:YTF
:CALibration:YTF?
Example
:CAL:YTF
State Saved
No
Notes
The Characterize Preselector function can be interrupted by pressing the Cancel
(ESC) front-panel key or remotely with Device Clear followed by the :ABORt SCPI
command. None of the new characterization data is then used. However, since the
old characterization data is purged at the beginning of the characterization, you
now have an uncharacterized preselector. You should re-execute this function and
allow it to finish before making any further preselected measurements.
:CALibration:YTF? returns 0 if successful
:CALibration:YTF? returns 1 if failed (including interfering user signal)
While Advanced, Characterize Preselector is performing the alignment, bit 0 in the
Status Operation register is set. Completion, or termination, will clear bit 0 in the
Status Operation register.
This command is sequential; it must complete before further SCPI commands are
processed. Interrupting the alignment from remote is accomplished by invoking
Device Clear followed by the :ABORt command.
Successful completion will clear bit 9 in the Status Questionable Calibration
register.
A failure encountered during alignment will generate the Error Condition message
“Characterize Preselector failed” and set bit 9 in the Status Questionable
Calibration register.
For Options that support frequencies > 3.6 GHz only.
Dependencies
This key does not appear in models that do not contain preselectors. In these
models the SCPI command is accepted without error but no action is taken.
Couplings
Initializes the time for the Last Characterize Preselector Time.
Records the temperature for the Last Characterize Preselector Temperature.
Command
:CALibration:YTF:NPENding
Example
CAL:YTF:NPEN
Preset
Range
State Saved
No
Notes
Remote Language Compatibility Measurement Application Reference
520
5 System Settings
Alignments
:CALibration:YTF:NPENding is the same as :CALibration:YTF
including all conditions, status register bits, except that this scpi command does not
BLOCK the scpi session, so the user should use status register bits to query if the
calibration is successfully completed or not.
Typical usage is:
1) :CALibration:YTF:NPENding (Start a YTF calibration)
2) :STATus:OPERation:CONDition? (Check if the calibration is completed or not, If
bit 0 is set, then the system is doing calibration, the user should repeat this scpi
query until the bit is cleared )
3):STATus:QUEStionable:CALibration:EXTended:FAILure:CONDition? (Check if bit 2
is set or not. If this bit is set, that means there are some errors in previous internal
source calibration)
.
Characterize Reference Clock
Characterize Reference Clock calibrates the Reference Input Phase with the
External Reference Output. This feature is only available when either option DP2 or
B40 is present. It requires connecting the 10 MHz OUT to the EXT REF IN port with a
BNC cable before running the characterization.
Front Panel Guided Calibration Sequence
When selecting “Characterize Reference Clock” through the front panel, the
following form will be shown.
Step 1 of the guided calibration sequence:
521
Remote Language Compatibility Measurement Application Reference
5 System Settings
Alignments
Step 2 of the guided calibration sequence:
Step 3 of the guided calibration sequence:
Command
:CALibration:REFerence:CLOCk?
Example
:CAL:REF:CLOC:INIT?
//connect cable
:CAL:REF:CLOC?
//disconnect cable
:CAL:REF:CLOC:END?
State Saved
No
Notes
:CALibration:REFerence:CLOCk? returns 0 if successful
:CALibration:REFerence:CLOCk? returns 1 if failed
Dependencies
Option DP2 or B40
Couplings
Initializes the time for the Last Characterize Reference Clock Time.
Records the temperature for the Last Characterize Reference Clock Temperature.
Expected to be run after :CAL:REF:CLOC:INIT, and before :CAL:REF:CLOC:END.
Remote Language Compatibility Measurement Application Reference
522
5 System Settings
Alignments
The following parameter tables are for Remote Command Only.
Command
:CALibration:REFerence:CLOCk:INITialize?
Example
:CAL:REF:CLOC:INIT?
State Saved
No
Notes
:CALibration:REFerence:CLOCk:INIT? returns 0 if successful
:CALibration:REFerence:CLOCk:INIT? returns 1 if failed
Dependencies
Option DP2 or B40
Couplings
Expected to be run before sending the :CAL:REF:CLOC? command. This will stop
the current measurement when it has completed (does not abort the current data
acquisition), and it will prepare the instrument for the expected cabling.
Command
:CALibration:REFerence:CLOCk:END?
Example
:CAL:REF:CLOC:END?
State Saved
No
Notes
:CALibration:REFerence:CLOCk:END? returns 0 if successful
:CALibration:REFerence:CLOCk:END? returns 1 if failed
Dependencies
Option DP2 or B40
Couplings
Expected to be run after sending the :CAL:REF:CLOC? command, and after
removing the cable used in that Characterize Reference Clock step. This will
resume any queued measurements, and it concludes the reference clock
characterization.
Command
:CALibration:TIME:REFerence:CLOCk?
Example
:CAL:TIME:REFerence:CLOCk?
State Saved
No
Notes
Value is the date and time the last successful Characterize Reference Clock was
executed. The date is separated from the time by a space character. Returns “” if
Characterize Reference Clock has never been performed on the instrument.
Dependencies
Option DP2 or B40
.
523
Remote Language Compatibility Measurement Application Reference
5 System Settings
Alignments
Characterize Noise Floor
On instruments with the NF2 license installed, the calibrated Noise Floor used by
Noise Floor Extensions should be refreshed periodically. To do this, press the
Characterize Noise Floor key. When you press this key, the instrument stops any
measurement currently underway, and a dialog appears with an OK and Cancel
button which says:
“This action will take several minutes to perform. Please disconnect all cables from
the RF input and press Enter to proceed. Press ESC to cancel.”
When you press Enter or OK, the characterization proceeds. After the
characterization, the analyzer restarts the measurement from the beginning (similar
to pressing the Restart key). The characterization takes many minutes to run.
The noise floor model used by NFE includes an estimation of the temperature
behavior of the noise floor, but this is only an estimation. The noise floor changes
little with the age of the components. However, even small changes in the
estimated level of the noise floor can make large changes in the effective noise floor,
because the effective noise floor is the error in the estimation of the noise floor.
Keysight recommends that the Characterize Noise Floor operation be performed
when the analyzer is operating at an ambient temperature that is significantly
different than the ambient temperature at which this alignment was last run. In
addition, Keysight recommends that the Characterize Noise Floor operation be
performed after the first 500 hours of operation, and once every calendar year.
The noise floor model from the last operation of Characterize Noise Floor survives
across the power cycle.
The Characterize Noise Floor function can be interrupted by pressing the Cancel (ESC)
front-panel key or remotely with Device Clear followed by the :ABORt SCPI command.
None of the new characterization data is then used. However, since the old
characterization data is purged at the beginning of the characterization, you now have
an uncharacterized noise floor. You should re-execute this function and allow it to finish
before making any further measurements with NFE. Until you do, the analyzer will
display a “Characterize Noise Floor required” message and set bit 12 in the Status
Questionable Calibration register
(STATus:QUEStionable:CALibration:EXTended:NEEDed).
Command
:CALibration:NFLoor
:CALibration:NFLoor?
Example
:CAL:NFL
State Saved
Notes
:CALibration:NFLoor? returns 0 if successful :CALibration:NFLoor? returns 1 if failed
(including interfering user signal) While Characterize Noise Floor is performing the
alignment, bit ? in the Status Operation register is set. Completion, or termination,
Remote Language Compatibility Measurement Application Reference
524
5 System Settings
Alignments
will clear bit ? in the Status Operation register. This command is sequential; it must
complete before further SCPI commands are processed. Interrupting the alignment
from remote is accomplished by invoking Device Clear followed by the :ABORt
command. A failure encountered during characterization will generate the Error
Condition message “Characterize Noise Floor failed” message and set bit ? in the
Status Questionable Calibration register. Successful completion will clear bit ? in
the Status Questionable Calibration register.
Dependencies
This key does not appear in models that do not contain NFE. In these models the
SCPI command is accepted without error but no action is taken.
Couplings
Successful completion of Characterize Noise Floor will begin the elapsed time
counter or the Last Characterize Noise Floor Time.
Command
:CALibration:TIME:NFLoor?
Example
:CAL:TIME:NFL?
Preset
Range
State Saved
Notes
Value is the date and time the last successful Characterize Noise Floor was
executed. The date is separated from the time by a space character. Returns “” if no
Characterize Noise Floor has ever been performed on the instrument.
Dependencies
In models that do not include NFE, this command is not enabled and any attempt to
set or query will yield an error.
Command
:CALibration:TEMPerature:NFLoor?
Example
:CAL:TEMP:NFL?
Preset
Range
State Saved
Notes
Value is the temperature of the last successful Characterize Noise Floor was
executed. Returns “” if no Characterize Noise Floor has ever been performed on the
instrument.
Dependencies
In models that do not include NFE, this command is not enabled and any attempt to
set or query will yield an error.
Command
525
:CALibration:TIME:ELAPsed:NFLoor?
Remote Language Compatibility Measurement Application Reference
5 System Settings
Alignments
Example
:CAL:TIME:ELAP:NFL?
Preset
Range
State Saved
Notes
Value is the elapsed time the instrument was powered-on since the last successful
Characterize Noise Floor was executed. Returns “” if no Characterize Noise Floor
has ever been performed on the instrument.
Dependencies
In models that do not include NFE, this command is not enabled and any attempt to
set or query will yield an error.
Backup or Restore Align Data...
Opens the utility for backing-up or restoring the alignment data. Since this utility
cannot be run while the instrument software is running, a prompt tells you to shut
down the analyzer first:
Press OK and the analyzer will shut down and open the backup utility.
Alignment data for the instrument resides on the hard drive in a database. Keysight
uses high quality hard drives; however it is highly recommended the alignment data
be backed-up to storage outside of the instrument. Additionally, for customers who
use multiple CPU Assemblies or multiple disk drives, the alignment that pertains to
the instrument must be transferred to the resident hard drive after a CPU or hard
drive is replaced. This utility facilitates backing-up and restoring the alignment data.
This utility allows the operator to navigate to any location of the Windows file system. It
is intended that the operator use a USB memory device or Mapped Network Drive to
back up the alignment data to storage outside of the instrument.
The PC6 and PC7 CPUs contain a removable SD memory card. With one of these
CPU’s installed the Backup and Restore Alignment Data wizard will default to the
Remote Language Compatibility Measurement Application Reference
526
5 System Settings
Alignments
SD card as the backup location. At (every) power-on, the software will check to
determine if the calibration data on the SD memory card (the backup) is newer than
the data in use on the SSD. In such situations, before the application is loaded the
operator will be given the opportunity to restore the data from the backup. If the
operator responds “Yes”, the Backup and Restore Alignment Data wizard will be
invoked to perform the restore.
Command
:CALibration:DATA:DEFault
Example
:CAL:DATA:DEF
Couplings
Sets Auto Align to Off. Sets bit 14 in the Status Questionable Calibration register.
The Error Condition message “Align Now All required” is generated.
Alignment Data Wizard
The Backup or Restore Alignment Data wizard guides you through the operation of
backing-up or restoring the alignment data.
The following dialogue boxes operates without a mouse or external keyboard when
you use the default file names.
527
Remote Language Compatibility Measurement Application Reference
5 System Settings
Alignments
The backup screen indicates the approximate amount of space required to contain
the backup file.
The default file name will be AlignDataBackup_<model number>_<serial number>_
<date in YYYYMMDDHHMMSS>.bak.
The default backup location will be first drive identified as an external drive (USB or
LAN) if such is available; if not, the internal D: partition will be selected.
Remote Language Compatibility Measurement Application Reference
528
5 System Settings
Alignments
Changing the drive letter will also modify the path displayed in the box below. When
this step is first loaded, the drive drop-down menu is populated with connected
drives, which provide the user with write access. If there are many unreachable
network drives connected to the instrument, this step can take a few seconds. If a
USB drive is present, it will be selected by default. The path defaults to the
AlignmentBackups folder, and a filename is automatically created in the form of
AlignDataBackup_<model>_<serial number>_<date><time>. When the "Next >"
button is pressed, you will be prompted to create a new folder if the chosen path
does not yet exist.
529
Remote Language Compatibility Measurement Application Reference
5 System Settings
Alignments
Remote Language Compatibility Measurement Application Reference
530
5 System Settings
Alignments
The restore operation checks the validity of the restore file using the database's
built-in file validation. If the restore file is corrupt, the existing alignment data will
remain in use.
If the serial number information in the backup file being restored is different from that
of the instrument, the following message appears (the serial number shown are
examples):
The default restore location will be first drive identified as an external drive (USB or
LAN) if such is available; if not, the internal D: partition will be selected. The default
531
Remote Language Compatibility Measurement Application Reference
5 System Settings
Alignments
restore file will be the most recent file that matches the default backup file name
format: AlignDataBackup_<model number>_<serial number>_<date>.bak
Changing the drive letter also modifies the path displayed in the box below. When
this step is first loaded, the drive drop-down menu is populated with connected
drives, which provide you with read access. The path defaults to the AlignBackups
folder. The most recent *.bak file in the folder will also be selected by default.
Remote Language Compatibility Measurement Application Reference
532
5 System Settings
Alignments
533
Remote Language Compatibility Measurement Application Reference
5 System Settings
Alignments
Restore Alignment Defaults
This selection causes the Alignment system settings to be reset to their default
values. This does not affect any Alignment data stored in the system.
After performing this function, it may impact the auto-alignment time of the
instrument until a new alignment baseline has been established.
When Alignments is selected, a message appears saying:
“This will reset all of the settings for the Alignment system to their default values.
No alignment data will be erased.
This action cannot be undone. Do you want to proceed?”
The message provides an OK and Cancel button for the user to affirm or cancel the
operation.
Align Now All must be executed if the value of the Timebase DAC results in a
change.
Remote Language Compatibility Measurement Application Reference
534
5 System Settings
Alignments
Command
Example
:SYST:DEF ALIG
State Saved
The parameters affected are:
535
Parameter
Settings
Timebase DAC
Calibrated
Timebase DAC setting
Calibrated value
Auto Align State
Normal (if the instrument is not operating with default
alignment data, Off otherwise)
Auto Align All but RF
Off
Auto Align Alert
Time & Temperature
Remote Language Compatibility Measurement Application Reference
5 System Settings
Licensing
Licensing
Accesses capabilities for configuring the licenses in your instrument.
License Manager
Pressing License Manager opens the license explorer.
This feature is not available if option SF1 is installed.
For Help on licensing, select Help in the menu bar at the top of the license explorer
window.
Notes
No equivalent remote command for this key.
Backwards Compatibility Notes
In ESA the SCPI command for displaying the Show Licenses screen is:
:SYSTem:CONFigure:LKEY:STATe OFF|ON|0|1
:SYSTem:CONFigure:LKEY:STATe?
There are no equivalent SCPI commands in the X-Series for displaying the License
Explorer.
Install License
Command
Example
:SYSTem:LKEY <”OptionInfo”>, <”LicenseInfo”>
SYST:LKEY “N9073A1FP”,”027253AD27F83CDA5673A9BA5F427FDA5E4F25AEB1017638211AC9F60D9C639FE53
9735909C551DE0A91”
Notes
The <”OptionInfo”> contains the feature and the version. You must specify the
feature but can omit the version. If you omit the version, the system regards it as
the latest one, since the system knows which version is supported for each feature.
The <”LicenseInfo”> contains the signature, the expiration date, and serial number
for transport if transportable. You must specify the signature, but you can omit the
other information. If you omit the expiration date, the system regards it as
permanent. If you omit the serial number, the system regards it as nontransportable. As a result, this supports reverse compatibility.
Remove License
Command
Exampl-
:SYSTem:LKEY:DELete <”OptionInfo”>,<”LicenseInfo”>
SYST:LKEY:DEL ‘N9073A1FP”,”027253AD27F83CDA5673A9BA5F427FDA5E4F25AEB1017638211AC9F60D9C639FE53
Remote Language Compatibility Measurement Application Reference
536
5 System Settings
Licensing
9735909C551DE0A91”
e
Notes
The <”OptionInfo”> contains the feature and the version. You must specify the
feature but can omit the version. If you omit the version, the system regards it as
the latest one, if more than one version is installed.
The <”LicenseInfo”> contains the signature, the expiration date, and whether or not
be transportable. You must specify the signature, but you can omit the other
information. If you omit the expiration date, the system regards it as permanent. If
you omit the transportability, the system regards it as non-transportable. As a
result, this supports reverse compatibility.
List License
Command
:SYSTem:LKEY:LIST?
Notes
Return Value:
An <arbitrary block data> of all the installed instrument licenses.
The format of each license is as follows.
<Feature>,<Version>,<Signature>,<Expiration Date>,<Serial Number for
Transport>
Return Value Example:
#3136
N9073A-1FP,1.000,B043920A51CA
N9060A-2FP,1.000,4D1D1164BE64
N9020A-508,1.000,389BC042F920
N9073A-1F1,1.000,5D71E9BA814C,13-aug-2005
<arbitrary block data> is
Where:
N is the number of digits that describes the number of MMM characters. For
example if the data was 55 bytes, N would be 2.
MMM would be the ASCII representation of the number of bytes. In the previous
example, N would be 55.
<data> ASCII contents of the data
Validate License
537
Command
:SYSTem:LKEY? <”OptionInfo”>
Example
SYST:LKEY? “N9073A-1FP”
Remote Language Compatibility Measurement Application Reference
5 System Settings
Licensing
Notes
The <”OptionInfo”> contains the feature and the version. You must specify the
feature but can omit the version. If you omit the version, the system regards it as
the latest one.
Return Value:
<”LicenseInfo”> if the license is valid, null otherwise.
<”LicenseInfo”> contains the signature, the expiration date, and serial number if
transportable.
Return Value Example:
“B043920A51CA”
Host ID
Command
:SYSTem:HID?
Notes
Return value is the host ID as a string
Remote Language Compatibility Measurement Application Reference
538
5 System Settings
Security
Security
Accesses capabilities for operating the instrument in a security controlled
environment.
USB Write Protect
The Windows operating system can be configured to disable write access to the USB
ports for users who are in a secure environment where transferring data from the
instrument is prohibited. The USB Write Protect control is a convenient way to
disable write access to USB.
This control is only available to users with Administrator privileges..
Preset
This is unaffected by Preset or any Restore System Defaults. A
Keysight Recovery will set the USB to write protect OFF
Range
Read-Write|Read only
State Saved
No
Notes
When the USB ports are in Read-only mode then no data can be stored to USB,
including the internal USB memory used for a back-up location for the calibration
data.
Dependencies
This key is grayed-out unless the current user has administrator privileges.
Restore Security Defaults
Pressing this button sets USB Read/Write to Enable.
This control is only available to users with Administrator privileges.
539
Remote Language Compatibility Measurement Application Reference
5 System Settings
Diagnostics
Diagnostics
The Diagnostics page of the System menu has a slider on it that allows you to view
Hardware Statistics.
Show Hardware Statistics
Provides a display of various hardware statistics. The statistics include the following:
– Mechanical relay cycles
– High and Low temperature extremes
– Elapsed time that the instrument has been powered-on (odometer)
The display should appear listing the statistics, product number, serial number, and
firmware revision.
The CXA models in which the AC/DC Switch field is called Fixed Atten and that omit
the mechanical attenuation fields are the N9000A-503/507 models.
Modular HWs only have time and temperature information in Show Hardware
Statistics.
The data will be updated only when the Show Hardware Statistics menu key is
pressed, it will not be updated while the screen is displayed.
The tabular data should be directly printable.
The values displayed on the screen are only updated upon entry to the screen and not
updated while the screen is being displayed.
Front Panel Test
Allows verification of each front-panel key and the RPG. The Front Panel Test is a
standalone windows program.
Once launched, the operator has responsibility for exiting the Front Panel Test and
returning focus to the Instrument Application.
This feature is not available if option SF1 is installed.
Operator is responsible for Notepad and returning focus to the Instrument
Application.
Advanced
Accesses advanced diagnostic capabilities performed in the factory or under
instructions from repair procedures. This menu key is only visible when the logged-in
user is “saservice”.
This feature is not available if option SF1 is installed.
Remote Language Compatibility Measurement Application Reference
540
5 System Settings
Diagnostics
The first access to the Advanced Diagnostic Menu after invoking the instrument
application will require an authentication, which is to enter the Service Code.
Subsequent accesses to the Advanced Diagnostic Menu are unimpeded. The
Authentication dialog looks like:
“OK” is the default key thus the Enter key is used to complete the entry. If invalid
Service Code is entered authentication is not granted and you are provided the
following dialog:
Key Recorder
Access the Key Recorder feature.
Key Recorder On/Off
Turn On/Off the Key Recorder function.
The startup of the key recorder is controlled by a registry entry.
Show Keystroke History
Launches Notepad with the key recorder history file loaded.
Operator is responsible for exiting Notepad and returning focus to the Instrument
Application.
.
Fault Detective
Accesses the Fault Detective feature.
Fault Detective
Fault Detective is a program to locate faults in the measurement hardware of the
instrument during the Manufacturing Process. Fault Detective is a standalone
541
Remote Language Compatibility Measurement Application Reference
5 System Settings
Diagnostics
windows program. The menu key located here for launching Fault Detective. Fault
Detective can be launched from SCPI using the general purpose ‘RUN’ command:
SERV:RUN “C:\Program
Files\Keysight\SignalAnalysis\FaultDetective\SystemApp.exe;<password>”
Once launched, the operator has responsibility for exiting the Fault Detective and
returning focus to the Instrument Application.
Notes
Operator is responsible for exiting Fault Detective and returning focus to the
Instrument Application.
.
Fault Detective DEV
Fault Detective DEV is a program to locate faults in the measurement hardware of
the instrument during the development of Fault Detective. Fault Detective DEV is a
standalone windows program. The menu key located here for launching Fault
Detective DEV. Fault Detective DEV can be launched from SCPI using the general
purpose ‘RUN’ command:
SERV:RUN “C:\Program
Files\Keysight\SignalAnalysis\FaultDetective\SystemAppDev.exe”
Once launched, the operator has responsibility for exiting the Fault Detective DEV
and returning focus to the Instrument Application.
Notes
Operator is responsible for exiting Fault Detective DEV and returning focus to the
Instrument Application.
Diagnostic Report
nvokes Notepad with the Diagnostic Report loaded. The report can be viewed or
saved to an external media or drive. Notepad can be closed without a mouse or
external keyboard by pressing ALT front-panel key, then arrow down to highlight
Exit, then press Enter.
The Diagnostic Reported file is: C:\Program Files\Keysight\Signal Analysis\Fault
Detective\Dut\report.txt
The Diagnostic Report can be retrieved from the instrument using the MMEM set of SCPI
command, once you have the fully qualified path and file name.
Example
MMEM:DATA? “:\Program Files\Keysight\Signal Analysis\Fault
Detective\Dut\report.txt”
Notes
Operator is responsible for Notepad and returning focus to the Instrument
Application.
Remote Language Compatibility Measurement Application Reference
542
5 System Settings
Diagnostics
.
Test Summary
Invokes Notepad with the Test Summary loaded. The summary can be viewed or
saved to an external media or drive. Notepad can be closed without a mouse or
external keyboard by pressing ALT front-panel key, then arrow down to highlight Exit,
then press Enter.
The Test Summary file is: C:\Program Files\Keysight\Signal Analysis\Fault
Detective\Dut\testSummary.txt.
The Test Summary can be retrieved from the instrument using the MMEM set of SCPI
command, once you have the fully qualified path and file name.
Example
MMEM:DATA? “:\Program Files\Keysight\Signal Analysis\Fault
Detective\Dut\testSummary.txt”
Notes
Operator is responsible for Notepad and returning focus to the Instrument
Application.
.
Test Result
Invokes Notepad with the Test Result loaded. The result can be viewed or saved to
an external media or drive. Notepad can be closed without a mouse or external
keyboard by pressing ALT front-panel key, then arrow down to highlight Exit, then
press Enter.
The Test Result file is: C:\Program Files\Keysight\Signal Analysis\Fault
Detective\Dut\testdata.txt
.The Test Result can be retrieved from the instrument using the MMEM set of SCPI
command, once you have the fully qualified path and file name.
Command
Example
MMEM:DATA? “:\Program Files\Keysight\Signal Analysis\Fault
Detective\Dut\testdata.txt”
State Saved
Notes
Operator is responsible for Notepad and returning focus to the Instrument
Application.
.
543
Remote Language Compatibility Measurement Application Reference
5 System Settings
Service
Service
Accesses capabilities performed in the factory or under instructions from repair
procedures. This selection is only visible when the logged-in user is “advanceduser”
or “saservice”. The first access to the Service Menu after invoking the instrument
application will require an authentication Service Code.
Remote Language Compatibility Measurement Application Reference
544
Keysight X-Series Signal Analyzer
Remote Language Compatibility Measurement Application Reference
6 Save/Recall
This section describes the functions that can be accessed via the front-panel folder
icon, as shown below.
545
6 Save/Recall
Save
Save
The Save dialog lets you save states, traces, screen images and other items from
the analyzer to files on the analyzer’s internal storage, to removable devices, and to
directories on the network. You access the Save dialog by pressing the Save
hardkey, or by pressing the folder icon at the bottom of the display and then pressing
the Save icon.
The Save dialog has section tabs running down the left side, which you use to specify
what you want to save.
You choose the save item and then complete the save by choosing a register or file
location to which to save the item.
Notes
No remote command for this key specifically, but the :MMEM:STORe command is
available for specific file types. An example is :MMEM:STOR:STATe <filename>.
State
Save State lets you choose a register or file for saving the state.
546
Remote Language Compatibility Measurement Application Reference
6 Save/Recall
Save
State files contain essentially all the information required to return the analyzer to
the measurement and settings that were in effect at the time of the save. State files
are in a proprietary binary form (for speed) and cannot be read or edited by PC
software, but can be loaded back into the analyzer to restore the state.
State files contain all of the settings of the Input/Output system as well, even
though Input/Output variables are outside of the Mode’s state and unaffected by
Mode Preset, because these are needed to restore the complete setup.
Persistent System settings (for example, GPIB address) are affected by neither Mode
Preset or Restore Mode Defaults, nor are they included in a saved State file.
For rapid saving, the State menu lists 16 registers to which you can save states.
Pressing a Register button initiates the save. You can also select a file to which to
save by pressing “Save to File”.
The default path for all State Files is:
My Documents\<mode name>\state
where <mode name> is the parameter used to select the mode with the INST:SEL
command (for example, SA for the Spectrum Analyzer).
State files have the extension “.state”. The default filename is State_0000.state,
where the 4 digit number is the lowest number that does not conflict with any
filename in the current directory.
In products that run multiple simultaneous instances of the X-Series Application, all
instances share the same registers and file directories, so take care not to overwrite files
and/or registers from one instance which were saved by another instance.
Command
:MMEMory:STORe:STATe <filename>
Example
MMEM:STOR:STATe "MyStateFile.state"
Notes
Both single and double quotes are supported for any filename parameter over
remote.
After saving to a register, that register’s menu key is updated with the date the
time, unless a custom label has been entered for that key.
After saving to a register, you remain in the Save State menu, so that you can see
the Register key update. After saving to a file, the analyzer automatically returns to
the previous menu and any Save As dialog goes away.
Backwards Compatibility Notes
For backwards compatibility, :MMEMory:STORe:STATe 1,<filename> is supported.
Register 1 thru Register 16
Selecting any one of these register buttons causes the State of the currently active
mode to be saved to the specified Register. The registers are provided for rapid
saving and recalling, since you do not need to specify a filename or navigate to a file.
Each of the register menu keys annotates whether it is empty or at what date and
Remote Language Compatibility Measurement Application Reference
547
6 Save/Recall
Save
time it was last modified. In addition, you can edit any of the register names to enter
custom names for any register.
Although these 16 registers are the only registers available from the front panel,
there are 128 state registers available in the instrument. Registers 17-128 are only
available from the SCPI interface, using the *SAV command.
There is one set of 128 state registers in the instrument, not one set for each Mode.
When a state is saved, the Mode it was saved from is saved with it; then when it is
recalled, the instrument switches to that Mode.
In products that run multiple simultaneous instances of the X-Series Application, all
instances share the same registers and file directories, so take care not to overwrite files
and/or registers from one instance which were saved by another instance.
The date displayed follows the format specified in the Date Format setting under the
Control Panel. The time shows hours and minutes.
After the save completes, the corresponding register menu key annotation is
updated with the date and time and the message "Register <register number>
saved" is displayed.
IEEE 488.2 Command not available in N9061C
Edit Register Names
You may enter a custom name for any of the Registers, to help you remember what
you are using that state to save. To do this, press the Name field for the register you
want to rename, which brings up the onscreen alpha keyboard. Press the “Done”
button on this keyboard when you are done editing.
The maximum number of characters for a register name is 30. If you delete all the
characters in the custom name, it restores the default (time and date).
The register names are stored within the state files, but they are not part of the
instrument state; that is, once you have edited a register name, loading a new state
will not change that register name. Another consequence of this is that the names
will be persistent through a power cycle. Also, if a named state file is transferred to
another analyzer, it will bring its custom name along with it.
If you try to edit the name of an empty register, the analyzer will first save the state
to have a file to put the name in. If you load a named state file into an analyzer with
older firmware it will ignore the metadata.
The *SAV and *RCL commands will not be affected by the custom register names,
nor will the MMEM commands.
Command
:MMEMory:REGister:STATe:LABel <reg
number>,”label”
:MMEMory:REGister:STATe:LABel? <reg number>
548
Example
:MMEM:REG:STAT:LAB 1,”my label”
Preset
The names are unaffected by Preset or power cycle but are set to the
default label (time and date) on a “Restore System Defaults->Misc”
Remote Language Compatibility Measurement Application Reference
6 Save/Recall
Save
Notes
<reg number> is an integer from 1 to 16. If the SCPI specifies an invalid register
number an error message is generated, -222,"Data out of range;Invalid register
label number"
“label” is a string from 0 to 30 characters in length. If a label exceeds 30 characters,
an error message is generated, -150,“String data error;Label clipped to 30
characters”
“label” of length 0 erases the custom label and restores the default (time and date)
label. E.g.: :MMEM:REG:STAT:LAB 1,””
Save to File/Save As
For every Save type, a button appears called “Save to File” or “Save As”. “Save to
File” appears for save types that also include registers (like State and Trace+State),
and “Save As” appears for all other save types.
When you push the “Save to File” or “Save As” button, a dialog slides in from the
right that allows you to see what files are already saved in the current directory.
Graphic
The default directory is the internal directory for the current Mode and save type, on
the D: drive. You may also change to another Mode’s state directory by pressing the
dropdown in the upper right corner labelled “Mode”. Once you have chosen a
directory, the files in that directory whose extension matches the current data type
(e.g., .state or .trace) are displayed in the right hand window of the dialog. You can
sort this list by name, date, file size or extension by tapping the Name, Date, Size, or
Content header at the top of each column. A second tap toggles the sort order
between Ascending and Descending.
Remote Language Compatibility Measurement Application Reference
549
6 Save/Recall
Save
Also displayed is a path depiction showing the path to the current directory. In the
example above, the path is D:\Users\Instrument\Documents\SA\screen. Tapping
any element of this path lets you select an alternate route. Tapping the “Computer”
arrow lets you select a different drive.
Tapping the “back” arrow navigates to the previously selected directory.
Using the C: drive is strongly discouraged, since it runs the risk of being overwritten
during an instrument software upgrade.
When you plug in a removable drive (e.g., a thumb drive), the browser immediately
navigates to the root of that drive.
Note that for each data type there is a “current” directory and it is the last directory
used by either Save or Recall for that Mode.
After a successful save, a message "File <filename> saved" or "State Register
<register number> saved" is displayed in an information box for a few seconds.
Trace+State
Save Trace+State lets you choose a register or file for saving selected traces and the
state.
Trace+State files contain essentially all the information required to return the
analyzer to the measurement and settings that were in effect at the time of the save,
as well as the data for one or all traces. Trace+State files are in a proprietary binary
form (for speed) and cannot be read or edited by PC software, but can be loaded
back into the analyzer to restore the state and trace(s).
Trace+State files contain all of the settings of the Input/Output system as well, even
though Input/Output variables are outside of the Mode’s state and unaffected by
Mode Preset, because these are needed to restore the complete setup.
Persistent System settings (for example, GPIB address) are affected by neither Mode
Preset or Restore Mode Defaults, nor are they included in a saved Trace+State file.
For rapid saving, the Trace+State menu lists 16 registers to which you can save
trace+state files. The Trace+State registers are separate registers from the State
registers. Pressing a Register button initiates the save. You can also select a file to
which to save by pressing “Save to File”.
The default path for all Trace+State files is the same as that for State files:
My Documents\<mode name>\state
where <mode name> is the parameter used to select the mode with the INST:SEL
command (for example, Basic for the IQ Analyzer).
In products that run multiple simultaneous instances of the X-Series Application, all
instances share the same registers and file directories, so take care not to overwrite files
and/or registers from one instance which were saved by another instance.
550
Remote Language Compatibility Measurement Application Reference
6 Save/Recall
Save
Trace+State files have the extension “.trace”. The default filename is State_
0000.trace, where the 4 digit number is the lowest number that does not conflict
with any filename in the current directory.
The Trace+State selection only appears for measurements that support trace saves.
It is blanked for modes that do not support trace saves. Saving Trace is identical to
saving State except a .trace extension is used on the file instead of .state, and
internal flags are set in the file indicating which trace was saved.
See "More Information" on page 552.
Command
:MMEMory:STORe:TRACe
TRACE1|TRACE2|TRACE3|TRACE4|TRACE5|TRACE6|ALL,<filename>
:MMEMory:STORe:TRACe:REGister
TRACE1|TRACE2|TRACE3|TRACE4|TRACE5|TRACE6|ALL,<integer>
Example
:MMEM:STOR:TRAC TRACE1,“myState.trace” saves the file myState.trace on
the default path and flags it as a “single trace” file with Trace 1 as the single
trace (even though all of the traces are in fact stored).
:MMEM:STOR:TRAC ALL,“myState.trace” saves the file myState.trace on the
default path and flags it as an “all traces” file
:MMEM:STOR:TRAC:REG TRACE1,2 stores trace 1 data in trace register 2
Notes
This command actually performs a save state, which in the Swept SA
measurement includes the trace data. However it flags it (in the file) as a “save
trace” file of the specified trace (or all traces).
Some modes and measurements do not have available all 6 traces. The Phase
Noise mode command, for example, is: MMEMory:STORe:TRACe
TRACE1|TRACE2|TRACE3|ALL,<filename>
Some modes and measurements have more than 6 traces available. The Realtime
SA mode command, for example, is: MMEMory:STORe:TRACe TRACE1 | TRACE2 |
TRACE3 | TRACE4 | TRACE5 | TRACE6 | TRACE7 | TRACE8 | TRACE9 | TRACE10 |
TRACE11 | TRACE12 | ALL,<filename>
The range for the register parameter is 1-5
When you initiate a save, if the file already exists, a dialog will appear that allows
you to replace the existing file by selecting OK or you can Cancel the request. If you
select OK, the file will be overwritten. Using the C: drive is strongly discouraged,
since it runs the risk of being overwritten during an instrument software upgrade.
Both single and double quotes are supported for any filename parameter over
remote.
After saving to a register, that register’s menu key is updated with the date and
time of the save.
After saving to a register, you remain in the Save Trace menu, so that you can see
the Register key update. After saving to a file, the analyzer automatically returns to
the previous menu and any Save As dialog goes away.
Remote Language Compatibility Measurement Application Reference
551
6 Save/Recall
Save
More Information
In measurements that support saving Traces, for example, Swept SA, the Trace
data is saved along with the State in the State file. When recalling the State, the
Trace data is recalled as well. Traces are recalled exactly as they were stored,
including the writing mode and update and display modes. If a Trace was updating
and visible when the State was saved, it will come back updating and visible, and
its data will be rewritten right away. When you use State to save and recall traces,
any trace whose data must be preserved should be placed in View or Blank mode
before saving.
The following table describes the Trace Save and Recall possibilities:
You want to recall
state and one
trace’s data,
leaving other
traces unaffected.
Save
Trace+State
from 1
trace. Make
sure that no
other traces
are
updating
(they should
all be in
View or
Blank mode)
when the
save is
performed.
On Recall, specify the trace you want to load the one trace’s
data into. This trace will load in View. All other traces’ data
will be unaffected, although their trace mode will be as it
was when the state save was performed.
You want to recall
all traces
Save
Trace+State
from ALL
traces.
On Recall, all traces will come back in View (or Blank if they
were in Blank or Background when saved)
You want all traces
to load exactly as
they were when
saved.
Save State
On recall, all traces’ mode and data will be exactly as they
were when saved. Any traces that were updating will have
their data immediately overwritten.
Save From Trace
This control enables you to select the trace to be saved. The default is the currently
selected trace, selected in this this or any other menu with Trace selection. If you
have chosen All then it remains chosen until you specifically change it to a single
trace, regardless of the trace selected in the Trace menu.
When you select a trace, it makes that trace the current trace, so it displays on top of
all of the other traces.
552
Remote Language Compatibility Measurement Application Reference
6 Save/Recall
Save
Register 1 thru Register 16
Selecting any one of these register buttons causes the State of the currently active
mode to be saved to the specified Register. The registers are provided for rapid
saving and recalling, since you do not need to specify a filename or navigate to a file.
Each of the register menu keys annotates whether it is empty or at what date and
time it was last modified. In addition, you can edit any of the register names to enter
custom names for any register.
Although these 16 registers are the only registers available from the front panel,
there are 128 state registers available in the instrument. Registers 17-128 are only
available from the SCPI interface, using the *SAV command.
There is one set of 128 state registers in the instrument, not one set for each Mode.
When a state is saved, the Mode it was saved from is saved with it; then when it is
recalled, the instrument switches to that Mode.
The date displayed follows the format specified in the Date Format setting under the
Control Panel. The time shows hours and minutes.
After the save completes, the corresponding register menu key annotation is
updated with the date and time and the message "Register <register number>
saved" is displayed.
IEEE 488.2 Command not available in N9061C
Edit Register Names
You may enter a custom name for any of the Registers, to help you remember what
you are using that trace+state to save. To do this, press the Name field for the
register you want to rename, which brings up the onscreen alpha keyboard. Press
the “Done” button on this keyboard when you are done editing.
The maximum number of characters for a register name is 30. If you delete all the
characters in the custom name, it restores the default (time and date).
The register names are stored within the trace+state files, but they are not part of
the instrument state; that is, once you have edited a register name, loading a new
state will not change that register name. Another consequence of this is that the
names will be persistent through a power cycle. Also, if a named state file is
transferred to another analyzer, it will bring its custom name along with it.
If you try to edit the name of an empty register, the analyzer will first save the
trace+state to have a file to put the name in. If you load a named state file into an
analyzer with older firmware it will ignore the metadata.
Command
:MMEMory:REGister:TRACe:LABel <reg
number>,”label”
:MMEMory:REGister:TRACe:LABel? <reg number>
Example
:MMEM:REG:TRAC:LAB 1,”my label”
Preset
The names are unaffected by Preset or power cycle but are set to the
default label (time and date) on a “Restore System Defaults->Misc”
Remote Language Compatibility Measurement Application Reference
553
6 Save/Recall
Save
Notes
<reg number> is an integer from 1 to 16. If the SCPI specifies an invalid register
number an error message is generated, -222,"Data out of range;Invalid register
label number"
“label” is a string from 0 to 30 characters in length. If a label exceeds 30 characters,
an error message is generated, -150,“String data error;Label clipped to 30
characters”
“label” of length 0 erases the custom label and restores the default (time and date)
label. E.g.: :MMEM:REG:TRAC:LAB 1,””
Save to File/Save As
For every Save type, a button appears called “Save to File” or “Save As”. “Save to
File” appears for save types that also include registers (like State and Trace+State),
and “Save As” appears for all other save types.
When you push the “Save to File” or “Save As” button, a dialog slides in from the
right that allows you to see what files are already saved in the current directory.
Graphic
The default directory is the internal directory for the current Mode and save type, on
the D: drive. You may also change to another Mode’s state directory by pressing the
dropdown in the upper right corner labelled “Mode”. Once you have chosen a
directory, the files in that directory whose extension matches the current data type
(e.g., .state or .trace) are displayed in the right hand window of the dialog. You can
sort this list by name, date, file size or extension by tapping the Name, Date, Size, or
Content header at the top of each column. A second tap toggles the sort order
between Ascending and Descending.
554
Remote Language Compatibility Measurement Application Reference
6 Save/Recall
Save
Also displayed is a path depiction showing the path to the current directory. In the
example above, the path is D:\Users\Instrument\Documents\SA\screen. Tapping
any element of this path lets you select an alternate route. Tapping the “Computer”
arrow lets you select a different drive.
Tapping the “back” arrow navigates to the previously selected directory.
Using the C: drive is strongly discouraged, since it runs the risk of being overwritten
during an instrument software upgrade.
When you plug in a removable drive (e.g., a thumb drive), the browser immediately
navigates to the root of that drive.
Note that for each data type there is a “current” directory and it is the last directory
used by either Save or Recall for that Mode.
After a successful save, a message "File <filename> saved" or "State Register
<register number> saved" is displayed in an information box for a few seconds.
Screen Config+State
Pressing the Save key and selecting Screen Config+State lets you save the
complete configuration of all your screens to a file. Selecting Save As enables you to
choose a file where the exported data will reside.
Command
:MMEMory:STORe:SCONfig <filename>
Example
:MMEM:STOR:SCON "myScreenConfig.screen"
Remote Language Compatibility Measurement Application Reference
555
6 Save/Recall
Save
This stores the current screen configuration in the file MyScreenConfig.screen in the default
directory.
Measurement Data
Save Measurement Data lets you specify a data type (e.g., trace data) and choose a
file to which to export the data.
Measurement Data files are.csv files, and contain the requested data in a form that
can be imported into Excel® or other spreadsheets, as well as header data that
gives information on relevant instrument settings at the time the save occurred.
The main application of Measurement Data files is for importing data to a PC for
analysis, but in some cases Measurement Data files can also be imported back into
the instrument to recreate the data object that existed at the time of the save. For
example, most Trace data files can be imported back into the instrument.
The default path for Measurement Data Files is:
My Documents\<mode name>\data
with the subdirectory reflecting the data type and where <mode name> is the
parameter used to select the mode with the INST:SEL command (for example, SA for
the Spectrum Analyzer) and <measurement name> is the parameter used to select
the measurement with the CONF: command (for example, SAN for the Swept SA). So
a Peak Table file from the Swept SA would be stored in:
My Documents\SA\data\SAN\results
Measurement Data files have the extension “.csv”. The default filename is Prefix_
0000.csv, where the 4 digit number is the lowest number that does not conflict with
any filename in the current directory, and “Prefix” is dependent on the data type:
Type
Default Prefix
Traces
Trace_
Measurement Result
MeasR_
Capture Buffer
CapBuf_
For example, the default filename for a trace data file in an empty directory would be
Trace_0000.csv.
Save From Trace
This control enables you to select the specific item to be saved, for example, if you
are exporting trace data you may specify Trace 1, Trace 2, etc.
The default for traces is the currently selected trace, selected in this this or any other
menu with Trace selection. If you have chosen All then it remains chosen until you
specifically change it to a single trace, regardless of the trace selected in the Trace
menu. The All selection saves all six traces in one .csv file with the x-axis data in the
first column and the individual trace data in succeeding columns. The header data
and x-axis data in this file reflect the current settings of the measurement. Note that
556
Remote Language Compatibility Measurement Application Reference
6 Save/Recall
Save
any traces which are in View or Blank may have different x-axis data than the current
measurement settings; but this different x-axis data will not be output to the file.
Preset
Not part of Preset, but is reset to by Restore Mode Defaults; survives
shutdown
Data Type
You choose the data type to save by using the radio button selection box. The
available selections are listed below.
Notes
There is no SCPI command for Data Type, as the type is implied in the SCPI
command for each item.
Dependencies
The Data Type menu for any given measurement only contains data types that are
supported by that measurement.
Trace
Selecting Trace allows you to export Trace files in the PC-readable .csv format.
Trace files have the extension “.csv”. The default filename is Trace_0000.csv, where
the 4 digit number is the lowest number that does not conflict with any filename in
the current directory.
The default path for Trace data files is:
My Documents\<mode name>\data\traces
where <mode name> is the parameter used to select the mode with the INST:SEL
command (for example, SA for the Spectrum Analyzer).
The trace file contains a “meta” data header which describes the current state of the
analyzer. The metadata is detailed in Trace File Contents below.
See "More Information" on page 558.
Command
:MMEMory:STORe:TRACe:DATA
TRACE1|TRACE2|TRACE3|TRACE4|TRACE5|TRACE6|ALL,<filename>
Example
:MMEM:STOR:TRAC:DATA TRACE2,"myTrace2.csv" Exports the 2nd trace to the
file myTrace2.csv in the current path. The default path is My
Documents\SA\data\traces
Notes
If the save is initiated via SCPI, and the file already exists, the file will be
overwritten.
Remote Language Compatibility Measurement Application Reference
557
6 Save/Recall
Save
Using the C: drive is strongly discouraged, since it runs the risk of being overwritten
during an instrument software upgrade.
Both single and double quotes are supported for any filename parameter over
SCPI.
Dependencies
For SA measurements, traces cannot be recalled from a trace file that was saved
with ALL traces selected.
Couplings
When you select which trace to save, it makes that trace the current trace, so it
displays on top of all of the other traces.
More Information
Trace File Contents
A Trace Data File contains the data for one trace.
Note that when importing the data from one of these files back into the instrument,
it has to run through units conversion to get it back into dBm, which is how it is
stored internally.
Metadata: Trace Specific
Besides the trace data, there is metadata describing the context by which the trace
was produced. Some of the metadata is trace specific:
– Trace Type
– Detector
– Trace math (function, operand1, operand2, offset, reference)
– Trace name/number
When importing a trace, the detector and/or trace math function specified in the
metadata is imported with the trace, so that the annotation correctly shows the
detector and/or math type that was used to generate the data
Metadata: Display Specific
There is also some display-related metadata:
– Ref Level Offset
– External Gain
– X-Axis Unit
– Y-Axis Unit
NOTE: Because the trace data in the file needs to appear in the current X-axis and
Y-Axis unit, in the same way that data is output to SCPI in those units, the units
need to be included in the file. Note, however, that when the display-specific
558
Remote Language Compatibility Measurement Application Reference
6 Save/Recall
Save
settings change, this is NOT something that needs to restart the measurement or
turn on the dirty marker.
Metadata: Measurement Related
The rest of the metadata is measurement specific and reflects the state of the
measurement the last time the trace was updated. These are the “measurementrelated instrument settings” that are referred to in section Error! Reference source
not found., the ones which, if changed, cause a measurement restart.
– Number of Points
– Sweep Time
– Start Frequency
– Stop Frequency
– Average Count (actual; not the limit for the instrument)
– Average Type
– RBW
– RBW Filter Type
– RBW Filter BW Type
– VBW
– Sweep Type (FFT vs. Swept)
– Log/Lin X Scale (sometimes called Log Sweep)
– Preamp (on/off, band)
– Trigger (source, level, slope, delay)
– Phase Noise optimization setting
– Swept IF Gain
– FFT IF Gain
– AC/DC setting (RF Coupling)
– FFT Width
– External Reference setting
– Input (which input is in use)
Remote Language Compatibility Measurement Application Reference
559
6 Save/Recall
Save
– RF calibrator on/off
– Attenuation
Because any inactive trace can have a value that does not match the rest of the
measurement, when performing a Save the metadata for each trace is pulled from
the individual trace, not from the measurement.
A revision number is also included in the trace database, to allow for future
changes.
Note that the formatting of the numbers (integer, float) should be driven by the
implementer, who will be most familiar with the internals, rather than by this
example. Amplitude values are stored in units corresponding to the definitions in
the Amplitude chapter of the SA Mode PD, so no suffixes need to be included.
Frequency and time are stored in fundamental units so again no suffixes are
needed.
The choices for the various 1 of N and binary fields are as follows:
– Average Type: Power(RMS), Voltage, LogPower(Video)
– RBW Filter Type: Flattop, EMI, Gaussian
– RBW Filter BW: 3dB, 6dB, Noise, Impulse
– Sweep Type: Swept, FFT
– PreAmp State: On, Off
– PreAmp Band: Low, Full
– Trigger Source: Free, RFBurst, Video, Line, Periodic, Ext1, Ext2, TV
– Trigger Slope: Positive, Negative
– Phase Noise Optimization: Fast, Narrow, Wide
– Swept IF Gain: Low, High
– FFT If Gain: Autorange, Low, High
– Input: RF, ExtMix, BBIQ
– RF Calibrator: 50M, 400G, Comb, Off
– Trace Type: ClearWrite, TraceAverage, MaxHold, MinHold
– Detector: Normal, Average, Peak, NegPeak, Sample
– Trace Math: Off, PowerDifference, PowerSum, LogOffset, LogDifference
– Y Axis Unit: dBm, dBmV, dBmA, W, V, A, dBuV, dBuA, dBuV/m, dBuA/m, dBuV,
dBpT, dBG, dB
560
Remote Language Compatibility Measurement Application Reference
6 Save/Recall
Save
After the header, just before the trace data, a line with just the word DATA on it is
inserted to flag the start of the trace data.
The following file example shows the first lines of a Trace 1 file with X Axis Unit = Hz
and Y Axis Unit = dBuV, after importing into Excel (the second row contains the
Title):
Trace
“AS/NZS 1044; Conducted >1000 W, Motors, Average”
A.15.00
N9040B
526 EA3 B25 P26 PFR
1
Segment
0
Number of Points
1001
Sweep Time
0.066266667
Start Frequency
18827440
Stop Frequency
24463718
Average Count
0
Average Type
Power(RMS)
RBW
51000
RBW Filter
Gaussian
RBW Filter BW
3dB
VBW
51000
Sweep Type
Swept
X Axis Scale
Lin
PreAmp State
Off
PreAmp Band
Low
Trigger Source
Video
Trigger Level
1.2
Trigger Slope
Positive
Trigger Delay
1.00E–06
Phase Noise Optimization
Fast
Swept IF Gain
Low
FFT IF Gain
Autorange
RF Coupling
AC
FFT Width
411900
Ext Ref
10000000
Input
RF
Remote Language Compatibility Measurement Application Reference
561
6 Save/Recall
Save
RF Calibrator
Off
Attenuation
10
Ref Level Offset
0
External Gain
0
Trace Type
ClearWrite
Detector
Normal
Trace Math
Off
Trace Math Oper1
Trace5
Trace Math Oper2
Trace6
Trace Math Offset
0
Trace Name
Trace1
X Axis Unit
Hz
Y Axis Unit
dBm
DATA
1.6009301E+07
4.82047E+01
1.6018694E+07
4.69737E+01
1.6028087E+07
4.81207E+01
1.6037480E+07
4.72487E+01
1.6046873E+07
4.66437E+01
1.6056266E+07
4.66237E+01
1.6065659E+07
4.66967E+01
1.6075052E+07
4.77117E+01
1.6084445E+07
4.75787E+01
1.6093838E+07
4.83297E+01
1.6103231E+07
4.71327E+01
1.6112624E+07
4.78957E+01
1.6122017E+07
4.67507E+01
1.6131410E+07
4.81137E+01
Peak Table
Selecting Peak Table allows you to export Peak Table files in the PC-readable .csv
format.
Peak Table files have the extension “.csv”. The default filename is MeasR_0000.csv,
where the 4 digit number is the lowest number that does not conflict with any
filename in the current directory.
The default path for Peak Table data files is:
562
Remote Language Compatibility Measurement Application Reference
6 Save/Recall
Save
My Documents\<mode name>\data\<measurement name>\results
where <mode name> is the parameter used to select the mode with the INST:SEL
command (for example, SA for the Spectrum Analyzer) and <measurement name> is
the parameter used to select the measurement with the CONF: command (for
example, SAN for the Swept SA).
The Peak Table file contains a “meta” data header which describes the current state
of the analyzer. The metadata is detailed below.
See "More Information" on page 563.
Command
:MMEMory:STORe:RESults:PTABle <filename>
Example
:MMEM:STOR:RES:PTAB “myResults.csv” ! Saves the results from the
current peak table to the file myResults.csv in the current path.
Notes
If the save is initiated via SCPI, and the file already exists, the file will be
overwritten.
Using the C: drive is strongly discouraged, since it runs the risk of being overwritten
during an instrument software upgrade.
Both single and double quotes are supported for any filename parameter over
SCPI.
Dependencies
If a save of Peak Table results is requested and the Peak Table is not on, no file is
saved and a message is generated.
More Information
This section discusses the Peak Table Meas Results file format.
The Meas Results file, when opened, would show the header data (the same as for
the Marker Table except that the Result Type is Peak Table) ending with a few
fields of specific interest to Peak Table users:
• Peak Threshold
• Peak Threshold State (On|Off)
• Peak Excursion
• Peak Excursion State (On|Off)
• Display Line
• Peak Readout (All|AboveDL|BelowDL)
• Peak Sort (Freq|Amptd)
These fields are then followed by the data for the Peak Table itself.
Note that the label for the Frequency column changes to Time in 0 span.
Here is what the table for the above display looks like:
Remote Language Compatibility Measurement Application Reference
563
6 Save/Recall
Save
MeasurementResult
Swept SA
564
A.01.40_R0017
N9020A
526 B25 PFR P26 EA3
1
Result Type
Peak Table
Ref Level
0
Number of Points
1001
Sweep Time
0.066266667
Start Frequency
10000000
Stop Frequency
26500000000
Average Count
0
Average Type
LogPower(Video)
RBW
3000000
RBW Filter
Gaussian
RBW Filter BW
3dB
VBW
3000000
Sweep Type
Swept
X Axis Scale
Lin
PreAmp State
Off
PreAmp Band
Low
Trigger Source
Free
Trigger Level
1.2
Trigger Slope
Positive
Trigger Delay
1.00E–06
Phase Noise Optimization
Fast
Swept If Gain
Low
FFT If Gain
Autorange
RF Coupling
AC
FFT Width
411900
Ext Ref
10000000
Input
RF
RF Calibrator
Off
Attenuation
10
Ref Level Offset
0
Remote Language Compatibility Measurement Application Reference
6 Save/Recall
Save
External Gain
0
X Axis Units
Hz
Y Axis Units
dBm
Peak Threshold
–85
Peak Threshold State
On
Peak Excursion
6
Peak Excursion State
On
Display Line
–61
Peak Readout
AboveDL
Peak Sort
Amptd
DATA
Peak
Frequency
Amplitude
1
1.0000E+06
1.86
2
1.0020E+06
–57.27
3
1.0048E+06
–58.97
4
9.8320E+05
–58.99
5
9.5120E+05
–59.58
6
9.9360E+05
–59.71
7
1.0390E+06
–59.71
8
1.0054E+06
–59.78
9
1.1086E+06
–60.05
10
9.9740E+05
–60.25
11
9.6680E+05
–60.25
12
1.0286E+06
–60.69
13
9.5500E+05
–60.74
14
9.5240E+05
–60.88
15
9.5140E+05
–60.89
16
9.5920E+05
–60.90
17
18
19
20
Remote Language Compatibility Measurement Application Reference
565
6 Save/Recall
Save
Marker Table
Selecting Marker Table allows you to export Marker Table files in the PC-readable
.csv format.
Marker Table files have the extension “.csv”. The default filename is MeasR_
0000.csv, where the 4 digit number is the lowest number that does not conflict with
any filename in the current directory.
The default path for Marker Table data files is:
My Documents\<mode name>\data\<measurement name>\results
where <mode name> is the parameter used to select the mode with the INST:SEL
command (for example, SA for the Spectrum Analyzer) and <measurement name> is
the parameter used to select the measurement with the CONF: command (for
example, SAN for the Swept SA).
The Marker Table file contains a “meta” data header which describes the current
state of the analyzer. The metadata is detailed below.
See "More Information" on page 566.
Command
:MMEMory:STORe:RESults:MTABle <filename>
Example
:MMEM:STOR:RES:MTAB “myResults.csv” ! Saves the results from
the current marker table to the file myResults.csv in the current path.
Notes
If the save is initiated via SCPI, and the file already exists, the file will be
overwritten.
Using the C: drive is strongly discouraged, since it runs the risk of being overwritten
during an instrument software upgrade.
Both single and double quotes are supported for any filename parameter over
SCPI.
Dependencies
If a save of Marker Table results is requested and the Marker Table is not on, no file
is saved and a message is generated.
More Information
Marker Table File Contents
This section discusses the Marker Table Meas Results file format.
The Meas Results file, when opened, would show the following data:
MeasurementResult
Swept SA
A.15.00
566
N9040-
Remote Language Compatibility Measurement Application Reference
6 Save/Recall
Save
B
526 B25
PFR P26
EA3
1
Result Type
Marker
Table
Ref Level
0
Number of
Points
1001
Sweep Time
0.066266667
Start
Frequency
10000000
Stop
Frequency
26500000000
Average
Count
0
Average
Type
LogPower
(Video)
RBW
3000000
RBW Filter
Gaussian
RBW Filter
BW
3dB
VBW
3000000
Sweep Type
Swept
X Axis Scale
Lin
PreAmp
State
Off
PreAmp
Band
Low
Trigger
Source
Free
Trigger
Level
1.2
Trigger
Pos-
Remote Language Compatibility Measurement Application Reference
567
6 Save/Recall
Save
568
Slope
itive
Trigger
Delay
1.00E–
06
Phase Noise
Optimization
Fast
Swept If
Gain
Low
FFT If Gain
Autorange
RF Coupling
AC
FFT Width
411900
Ext Ref
10000000
Input
RF
RF
Calibrator
Off
Attenuation
10
Ref Level
Offset
0
External
Gain
0
X Axis Units
Hz
Y Axis Units
dBm
MKR
MODE
TRC
SCL
X
Y
FUNCTION
FUNCTION
WIDTH
FUNCTION
VALUE
FUNCTION
UNIT
1
Normal
1
Frequency
2.2350E+09
67.481
Off
0.0000E+00
0
None
2
Delta3
1
Frequency
0.0000E+00
–
0.761
Off
0.0000E+00
0
None
3
Fixed
1
Frequency
1.3255E+10
–
64.71
Off
0.0000E+00
0
None
4
Normal
2
Frequency
1.5904E+10
73.108
Off
0.0000E+00
0
None
Remote Language Compatibility Measurement Application Reference
6 Save/Recall
Save
5
Delta7
2
Frequency
2.7280E+09
30.258
Band
Power
1.3250E+06
–
3.969
dB
6
Normal
2
Time
5.2620E–02
70.177
Band
Power
2.3840E+06
–
43.15
dBm
7
Normal
3
Period
1.0680E–10
75.458
Off
0.0000E+00
0
None
8
Normal
3
Frequency
6.7120E+09
–
77.33
Noise
3.3910E+06
–
139.714
dBm/Hz
9
Fixed
3
Inverse
Time
4.0000E+01
–
30.05
Off
0.0000E+00
0
None
10
Normal
3
Frequency
1.1454E+10
75.161
Band
Density
1.3250E+06
–
138.973
dBm/Hz
11
Off
1
Frequency
0.0000E+00
0
Off
0.0000E+00
0
None
12
Off
1
Frequency
0.0000E+00
0
Off
0.0000E+00
0
None
Spectrogram
Selecting Spectrogram allows you to export Spectrogram files in the PC-readable
.csv format.
Spectrogram files have the extension “.csv”. The default filename is MeasR_
0000.csv, where the 4 digit number is the lowest number that does not conflict with
any filename in the current directory.
The default path for Spectrogram data files is:
My Documents\<mode name>\data\<measurement name>\results
where <mode name> is the parameter used to select the mode with the INST:SEL
command (for example, SA for the Spectrum Analyzer) and <measurement name> is
the parameter used to select the measurement with the CONF: command (for
example, SAN for the Swept SA).
The Spectrogram file contains a “meta” data header which describes the current
state of the analyzer. The metadata is detailed below.
Remote Language Compatibility Measurement Application Reference
569
6 Save/Recall
Save
Command
:MMEMory:STORe:RESults:SPECtrogram <filename>
Example
:MMEM:STOR:RES:SPEC “myResults.csv” ! Saves the results from the
current Spectrogram display to the file myResults.csv in the current
path.
The default path is My Documents\SA\data\SAN\results
Notes
If the save is initiated via SCPI, and the file already exists, the file will be
overwritten.
Using the C: drive is strongly discouraged, since it runs the risk of being overwritten
during an instrument software upgrade.
Both single and double quotes are supported for any filename parameter over
SCPI.
Dependencies
If a save of Spectrogram results is requested and the Spectrogram is not on, no file
is saved and a message is generated.
The Spectrogram choice only appears if option EDP is licensed.
More Information
This section discusses the Spectrogram Results file format. The Spectrogram
choice only appears if option EDP is licensed.
The Spectrogram results are the same as a Trace data export, except that instead
of having just one trace’s data, all 300 traces appear one after the other.
Each trace has its own data mark; the data for Spectrogram Trace 0 follows the row
marked DATA, the data for Spectrogram Trace 1 follows the row marked DATA1, for
Spectrogram Trace 2 follows the row marked DATA2, and so on.
Each DATA row has a timestamp in the second column (as of firmware revision
A.11.01). So, for example, if Trace 0 had a relative start time of 1729.523 sec, then
the first DATA row would look like this:
DATA,1729.523
And if Trace 13 had a relative start time of 100.45 sec, then the fourteenth data row
would look like:
DATA13,100.453
To find the absolute time for the relative timestamps of each trace, the last row
before the first DATA row gives the absolute start time of the Spectrogram, in the
form YYYYMMDDHHMMSS
So, for example, if the absolute start time is 13:23:45:678 on January 30, 2012, this
row would look like:
Start Time,20120130132345678
570
Remote Language Compatibility Measurement Application Reference
6 Save/Recall
Save
The resolution of the absolute time stored is 1 ms, which matches up with the fact that
the fastest sweep time is also 1 ms. However, there is no specification for the absolute
accuracy of the clock in the analyzer, nor is there any facility provided to allow the user
to set this time to any particular degree of accuracy.
Traces that have not yet been filled in the Spectrogram display are empty; there is
no DATA header for them. The file ends after the last non-empty trace.
For the purpose of this example, we have set the Average/Hold Number to 10, thus
we have only traces 0 thru 10. The Spectrogram was started at 02:28:08:700 pm
on April 25, 2012 (that is, 700 ms after 2:28:08 pm), although the screen dump itself
shows a different time, as it was taken ten minutes after the Spectrogram data.
Trace 0 is showing a start time of 5.30 seconds, meaning 5.3 seconds after the
Spectrogram started (trace 10 has a start time of 0, as it was the first trace taken
but has now rolled up into the tenth trace slot).
The Meas Results file, when opened, shows the header data and ten traces of
trace data. Below is an extract from the result file for the above display. Note the
start time of 20120425142808700 showing in the last row before the first DATA
row, and the relative time of 5.299231048 showing in the first DATA row:
Result Type
Spectrogram
MeasResult
Swept SA
A.15.00
N9040B
503 508 513 526 ALL ALV B1C B1X B25 B2X B40 BAB BBA CR3 CRP DP2
DRD EA3 EDP EMC EP1 ERC ESC ESP EXM FSA HBA K03 LFE MPB P03 P08
P13 P26 PFR RTL RTS S40 SB1 SEC SM1 UK6 YAS YAV
1
Segment
0
Number of Points
1001
Sweep Time
0.523333333
Start Frequency
5999984415
Stop Frequency
6000009415
Average Count
0
Average Type
LogPower(Video)
RBW
240
RBW Filter
Gaussian
RBW Filter BW
3dB
VBW
240
Sweep Type
Swept
X Axis Scale
Lin
Remote Language Compatibility Measurement Application Reference
571
6 Save/Recall
Save
572
PreAmp State
Off
PreAmp Band
Low
Trigger Source
Free
Trigger Level
1.2
Trigger Slope
Positive
Trigger Delay
0
Phase Noise Optimization
Wide
Swept If Gain
Low
FFT If Gain
Autorange
RF Coupling
AC
FFT Width
411900
Ext Ref
10000000
Input
RF
RF Calibrator
Off
Attenuation
14
Ref Level Offset
0
External Gain
0
Trace Type
Clearwrite
Detector
Normal
Trace Math
Off
Trace Math Oper1
Trace5
Trace Math Oper2
Trace6
Trace Math Offset
0
Trace Name
Trace1
X Axis Units
Hz
Y Axis Units
dBm
Start Time
20120425142808700
DATA
5.299231048
5999984415
-76.34749519
5999984440
-77.28097006
5999984465
-75.32317869
5999984490
-73.64417681
5999984515
-72.67154604
...
...
Remote Language Compatibility Measurement Application Reference
6 Save/Recall
Save
6000009315
-77.94423277
6000009340
-79.51829697
6000009365
-78.46108961
6000009390
-78.46108957
6000009415
-76.59570596
DATA2
4.708697055
5999984415
-80.98197882
5999984440
-80.98197879
5999984465
-75.83142132
5999984490
-74.02712079
5999984515
-73.57213005
...
...
6000009315
-75.9183103
6000009340
-79.53787488
6000009365
-78.82602191
6000009390
-78.82602188
6000009415
-76.37486709
DATA10
0
5999984415
-75.56751112
5999984440
-75.76485645
5999984465
-76.67718717
5999984490
-78.79238489
5999984515
-83.72680212
...
...
6000009315
-71.3942461
6000009340
-72.28308332
6000009365
-73.92684489
6000009390
-75.45548832
6000009415
-75.17904815
Meas Results
This control is only available when one of the following measurements is selected:
– Spectrum Analyzer Mode Measurements: Channel Power, Occupied Bandwidth,
ACP, Spectrum Emissions Mask, Spurious Emissions, Power Stat CCDF, Burst
Remote Language Compatibility Measurement Application Reference
573
6 Save/Recall
Save
Power
– Phase Noise Mode: All measurements
– Analog Demod Mode: All measurements
– Noise Figure Mode: All measurements
– Pulse Mode: All measurements
– W-CDMA Mode: All Measurements
A Meas Results file contains information describing the current state of the analyzer.
The contents of the file vary by measurement, as detailed in Meas Result File
Contents sections below.
Command
:MMEMory:STORe:RESults <string>
Example
MMEM:STOR:RES “MeasR_0000.csv”
Status Bits/OPC
dependencies
Sequential – waits for the previous measurement to complete.
Notes
If the save is initiated via SCPI and the file already exists, the file will be overwritten.
The SCPI command exports measurement results to the file specified as the
parameter in the current path. The default path is My Documents\<current
mode>\data\<measurement name>\results
where <mode name> is the parameter used to select the mode with the INST:SEL
command (for example, SA for the Spectrum Analyzer) and <measurement name>
is the parameter used to select the measurement with the CONF: command (for
example, CHP for the Channel Power)
Using the C: drive is strongly discouraged, since it runs the risk of being overwritten
during an instrument software upgrade.
The SCPI parameter is a quoted string, which specifies the filename. Both single
and double quotes are supported for any filename parameter over SCPI.
CHP Meas Results File Contents
A Meas Results File contains measurement results with the following information.
– File ID string, which is “MeasResult”
– Measurement ID following Mode ID, which is “SA:CHP” for example.
– Firmware rev and model number
– Option string
– Auto Sweep Time Rules
– Average Mode
574
Remote Language Compatibility Measurement Application Reference
6 Save/Recall
Save
– Average Number
– Average State
– Center Frequency
– Detector
– Electrical Atten
– Electrical Atten State
– IFGain
– IFGainAuto
– Impedance
– Integ BW
– Internal Preamp
– Internal Preamp Band
– Mechanical Atten
– MechanicalAttenStepEnum
– PSD Unit
– Resolution Band Width
– Resolution Bandwidth Shape
– RRC Filter Alpha
– RRC Filter BW
– RRC Filter State
– Span
– Sweep Points
– Sweep Time
– Sweep Time Auto
– TriggerSource
– Video Bandwidth
– Y Axis Unit
Remote Language Compatibility Measurement Application Reference
575
6 Save/Recall
Save
The file contains these data followed by MeasResult1 and MeasResult2, which flag
the start of the measurement results. Each line of Measurement Results consists of
two comma separated values, MeasResult1 value and MeasResult2 value.
MeasResult1 contains the same results as MEAS/READ/FETCh:CHPower1;
MeasResult2, MEAS/READ/FETCh:CHPower2.
Exported file is .csv file. The Meas Results file, when imported into Excel, will show
the following data:
MeasResult
SA:CHP
576
A.10.53
N9030A
526 ALV ATP B1X B1Y B25 B40 BBA CR3 CRP DCF DDA DP2 DRD EA3
EDP EMC EP1 ERC ESC ESP EXM FSA LFE LNP MAT MPB NFE NUL
P26 PFR PNC RTL RTS S40 SB1 SEC SM1 TVT YAS YAV
1
Auto Sweep Time Rules
Normal
Average Mode
Exponential
Average Number
10
Average State
TRUE
Center Frequency
13255000000
Detector
Average
IFGain
FALSE
IFGainAuto
FALSE
Impedance
50
Integ BW
2000000
Internal Preamp
FALSE
Internal Preamp Band
Low
PSD Unit
DbmHz
Resolution Band Width
27000
Resolution Bandwidth Shape
Gaussian
RRC Filter Alpha
0.22
RRC Filter BW
3840000
RRC Filter State
FALSE
Span
3000000
Sweep Points
1001
Sweep Time
0.004933333
Sweep Time Auto
TRUE
TriggerSource
Free
Video Bandwidth
270000
Y Axis Unit
DecibelMilliwatt
MeasResult1
MeasResult2
Remote Language Compatibility Measurement Application Reference
6 Save/Recall
Save
–76.8141133132837
–95.29174
–139.824413269924
–94.99601
–94.95281
–95.17146
OBW Meas Results File Contents
The content of a Meas Results File is defined in this section.
The first lines in the file consist of identification and instrument configuration
details, as follows.
– File ID string, which is “MeasResult”
– Measurement ID following Mode ID, which is “SA:OBW” for example.
– Firmware rev and model number
– Option string
– Auto Sweep Time Rules
– Average Mode
– Average Number
– Average State
– Center Frequency
– Detector
– Electrical Atten
– Electrical Atten State
– IFGain
– IFGainAuto
– Internal Preamp
– Internal Preamp Band
– Limit
– Limit State
– Max Hold
– Mechanical Atten
Remote Language Compatibility Measurement Application Reference
577
6 Save/Recall
Save
– MechanicalAttenStepEnum
– OBW Percent Pwr
– Resolution Band Width
– Resolution Bandwidth Shape
– Span
– Sweep Points
– Sweep Time
– Sweep Time Auto
– TriggerSource
– Video Bandwidth
– x DB
The data above is followed in the file by a line containing “MeasResult1” and
“MeasResult2”. This line forms a header for each set of measurement results,
which appear in subsequent lines. Each line of Measurement Results consists of
two comma-separated values, for MeasResult1 and MeasResult2 respectively.
The MeasResult1 set in the file corresponds to the data returned by
MEAS|READ|FETCh:OBWidth1, and the MeasResult2 set corresponds to the data
returned by MEAS|READ|FETCh:OBWidth2.
The exported file is in CSV format, with a .csv extension.
Meas Results File Example
When imported into Microsoft Excel, a typical Meas Results CSV file appears as
shown in the example below.
MeasResult
SA:OBW
578
A.10.53
N9030A
526 ALV ATP B1X B1Y B25 B40 BBA CR3 CRP DCF DDA DP2 DRD EA3
EDP EMC EP1 ERC ESC ESP EXM FSA LFE LNP MAT MPB NFE NUL P26
PFR PNC RTL RTS S40 SB1 SEC SM1 TVT YAS YAV
1
Auto Sweep Time Rules
Normal
Average Mode
Exponential
Average Number
10
Average State
TRUE
Center Frequency
1.33E+10
Detector
Average
IFGain
FALSE
Remote Language Compatibility Measurement Application Reference
6 Save/Recall
Save
IFGainAuto
FALSE
Internal Preamp
FALSE
Internal Preamp Band
Low
Limit
5000000
Limit State
FALSE
Max Hold
FALSE
OBW Percent Pwr
99
Resolution Band Width
27000
Resolution Bandwidth Shape
Gaussian
Span
3000000
Sweep Points
1001
Sweep Time
0.004933
Sweep Time Auto
TRUE
TriggerSource
Free
Video Bandwidth
270000
x DB
–26
MeasResult1
MeasResult2
2971020.10835045
–
94.3702543927405
–74.9741251886604
–
94.1447790390963
ACP Meas Results File Contents
A Meas Results File contains measurement results with the following information.
– File ID string, which is “MeasResult”
– Measurement ID following Mode ID, which is “SA:ACP” for example.
– Firmware rev and model number
– Option string
– Auto Scaling
– Auto Sweep Time Rules
– Automatic Trigger Time
– Automatic Trigger Time State
– Average Mode
– Average Number
Remote Language Compatibility Measurement Application Reference
579
6 Save/Recall
Save
– Average State
– Bar Graph
– Carrier Coupling
– Carrier Pwr Present
– Carrier Spacing
– Carriers
– Center Frequency
– Center Frequency Step
– Center Frequency Step State
– Detector Auto
– Detector Selection
– Electrical Atten
– Electrical Atten State
– External Array Trigger Delay
– External Array Trigger Delay State
– External Array Trigger Level
– External Array Trigger Slope
– Filter Alpha
– Filter BW
– Filter Type
– Internal Preamp
– Internal Preamp Band
– Limit Test
– Line Trigger Delay
– Line Trigger Delay State
– Line Trigger Slope
– Meas Method
580
Remote Language Compatibility Measurement Application Reference
6 Save/Recall
Save
– Meas Type
– Measurement Noise Bandwidth
– Mechanical Atten
– MechanicalAttenStepEnum
– Method
– Noise Correction
– Offset Abs Limit
– Offset Fail
– Offset Filter Alpha
– Offset Filter BW
– Offset Filter Type
– Offset Freq
– Offset Freq State
– Offset Integ BW
– Offset Method
– Offset Rel Lim (Car)
– Offset Rel Lim (PSD)
– Offset Res BW
– Offset Res BW Mode
– Offset Video BW
– Offset Video BW Mode
– Periodic Timer Period
– Periodic Timer Sync Source
– Periodic Timer Trigger Delay
– Periodic Timer Trigger Delay State
– Points
– Power Ref
Remote Language Compatibility Measurement Application Reference
581
6 Save/Recall
Save
– Power Ref State
– Preselector Adjust
– PSD Ref
– PSD Unit
– Ref Car Freq
– Ref Car Freq State
– Ref Carrier
– Ref Carrier Mode
– Ref Position
– Ref Value
– Res BW
– Res BW Mode
– RFBurst Trigger Delay
– RFBurst Trigger Delay State
– RFBurst Trigger Level Abs
– RFBurst Trigger Level Rel
– RFBurst Trigger Level Type
– RFBurst Trigger Slope
– Scale/Div
– Span
– Sweep Time
– Sweep Time Auto
– Trigger Holdoff
– Trigger Holdoff State
– Trigger Source
– Video BW
– Video BW Auto
582
Remote Language Compatibility Measurement Application Reference
6 Save/Recall
Save
The file contains these data followed by MeasResult1, MeasResult2, and
MeasResult3, which flag the start of the measurement results. Each line of
Measurement Results consists of three comma separated values, MeasResult1
value, MeasResult2 value, and MeasResult3 value. MeasResult1 contains the
same result as MEAS/READ/FETCh:ACPower1; MeasResult2,
MEAS/READ/FETCh:ACPower2; MeasResult3, MEAS/READ/FETCh:ACPower3.
Exported file is .csv file. The Meas Results file, when imported into Excel, will show
the following data:
MeasResult
SA:ACP
A.10.53
N9030
A
526 ALV
ATP B1X
B1Y B25
B40 BBA
CR3 CRP
DCF DDA
DP2 DRD
EA3 EDP
EMC EP1
ERC ESC
ESP EXM
FSA LFE
LNP MAT
MPB NFE
NUL P26
PFR PNC
RTL RTS
S40 SB1
SEC SM1
TVT YAS
YAV
1
Auto
Scaling
TRUE
Auto
Sweep
Time Rules
Accy
Automatic
Trigger
Time
0.1
Automatic
Trigger
Time State
FALSE
Average
Mode
Expone
ntial
Remote Language Compatibility Measurement Application Reference
583
6 Save/Recall
Save
584
Average
Number
10
Average
State
TRUE
Bar Graph
TRUE
Carrier
Coupling
TRUE
TRU
E
TR
UE
TR
UE
TR
UE
TR
UE
T
R
U
E
T
R
U
E
T
R
U
E
T
R
U
E
T
R
U
E
T
R
U
E
Carrier Pwr
Present
Yes
Yes
Ye
s
Ye
s
Ye
s
Ye
s
Y
es
Y
es
Y
es
Y
es
Y
es
Y
es
Carrier
Spacing
500000
0
500
000
0
50
00
00
0
50
00
00
0
50
00
00
0
50
00
00
0
5
0
0
0
0
0
0
5
0
0
0
0
0
0
5
0
0
0
0
0
0
5
0
0
0
0
0
0
5
0
0
0
0
0
0
5
0
0
0
0
0
0
Carriers
1
Center
Frequency
1.33E+
10
Center
Frequency
Step
800000
Center
Frequency
Step State
TRUE
Detector
Auto
TRUE
Detector
Selection
Averag
e
Electrical
Atten
0
Electrical
Atten State
FALSE
External
Array
Trigger
Delay
1.00E–
06
1.00
E–
06
External
Array
Trigger
Delay State
FALSE
FAL
SE
External
Array
Trigger
1.2
1.2
Remote Language Compatibility Measurement Application Reference
6 Save/Recall
Save
Level
External
Array
Trigger
Slope
Positiv
e
Posi
tive
Filter Alpha
0.22
0.22
0.
22
0.
22
0.
22
0.
22
0.
2
2
0.
2
2
0.
2
2
0.
2
2
0.
2
2
0.
2
2
Filter BW
Minus3
dB
Filter Type
Gaussi
an
Internal
Preamp
FALSE
Internal
Preamp
Band
Low
Limit Test
FALSE
Line
Trigger
Delay
1.00E–
06
Line
Trigger
Delay State
FALSE
Line
Trigger
Slope
Positiv
e
Meas
Method
IbwSpe
ed
Meas Type
TPRef
Measureme
nt Noise
Bandwidth
200000
0
200
000
0
20
00
00
0
20
00
00
0
20
00
00
0
20
00
00
0
2
0
0
0
0
0
0
2
0
0
0
0
0
0
2
0
0
0
0
0
0
2
0
0
0
0
0
0
2
0
0
0
0
0
0
2
0
0
0
0
0
0
Mechanical
Atten
10
Mechanical
AttenStepE
num
S2dB
Method
IBW
IBW
IB
W
IB
W
IB
W
IB
W
IB
W
IB
W
IB
W
IB
W
IB
W
IB
W
Noise
FALSE
Remote Language Compatibility Measurement Application Reference
585
6 Save/Recall
Save
Correction
586
Offset Abs
Limit
0
0
0
0
0
0
Offset Fail
Relativ
e
Rel
ativ
e
Re
lat
ive
Re
lat
ive
Re
lat
ive
Re
lat
ive
Offset Filter
Alpha
0.22
Offset Filter
BW
Minus3
dB
Min
us3
dB
Mi
nu
s3
dB
Mi
nu
s3
dB
Mi
nu
s3
dB
Mi
nu
s3
dB
Offset Filter
Type
Gaussi
an
Gau
ssia
n
Ga
us
sia
n
Ga
us
sia
n
Ga
us
sia
n
Ga
us
sia
n
Offset Freq
300000
0
0
0
0
0
0
Offset Freq
State
TRUE
FAL
SE
FA
LS
E
FA
LS
E
FA
LS
E
FA
LS
E
Offset Integ
BW
200000
0
200
000
0
20
00
00
0
20
00
00
0
20
00
00
0
20
00
00
0
Offset
Method
FALSE
Offset Rel
Lim (Car)
–45
–60
0
0
0
0
Offset Rel
Lim (PSD)
–28.87
–
43.8
7
0
0
0
0
Offset Res
BW
220000
220
000
22
00
00
22
00
00
22
00
00
22
00
00
Offset Res
BW Mode
TRUE
TRU
E
TR
UE
TR
UE
TR
UE
TR
UE
Offset
Video BW
22000
220
00
22
00
0
22
00
0
22
00
0
22
00
0
Offset
Video BW
Mode
TRUE
TRU
E
TR
UE
TR
UE
TR
UE
TR
UE
Periodic
Timer
Period
0.02
Remote Language Compatibility Measurement Application Reference
6 Save/Recall
Save
Periodic
Timer Sync
Source
None
Periodic
Timer
Trigger
Delay
1.00E–
06
Periodic
Timer
Trigger
Delay State
FALSE
Points
1001
Power Ref
–76.81
dBm
Power Ref
State
On
Preselector
Adjust
0
PSD Ref
–
139.82
dBm/H
z
PSD Unit
DbmHz
Ref Car
Freq
13.255
000000
GHz
Ref Car
Freq State
On
Ref Carrier
1
Ref Carrier
Mode
On
Ref
Position
Top
Ref Value
–30
Res BW
220000
Res BW
Mode
FALSE
RFBurst
Trigger
Delay
1.00E–
06
RFBurst
Trigger
Delay State
FALSE
RFBurst
–20
Remote Language Compatibility Measurement Application Reference
587
6 Save/Recall
Save
Trigger
Level Abs
RFBurst
Trigger
Level Rel
–6
RFBurst
Trigger
Level Type
Absolu
te
RFBurst
Trigger
Slope
Positiv
e
Scale/Div
10
Span
800000
0
Sweep
Time
0.02
Sweep
Time Auto
TRUE
Trigger
Holdoff
0.1
Trigger
Holdoff
State
FALSE
Trigger
Source
Free
Video BW
22000
Video BW
Auto
TRUE
MeasResult
1
MeasR
esult2
Me
asR
esul
t3
–
76.8058517
744559
0
1
0.08479001
9950006
–
76.805
851774
4559
0
0.02839291
28313787
–999
1
–999
0
–999
1
SEM Meas Results File Contents
A Meas Results File contains measurement results with the following information.
588
Remote Language Compatibility Measurement Application Reference
6 Save/Recall
Save
– File ID string, which is “MeasResult”
– Measurement ID following Mode ID, which is “SA:SEM” for example.
– Firmware rev and model number
– Option string
– Automatic Trigger Time
– Automatic Trigger Time State
– Center Frequency
– ChanIntegBW
– ChannelDetector
– ChannelDetectorState
– ChanPwrRefAuto
– ChanResBW
– ChanResBWAuto
– ChanSpan
– ChanSweepTime
– ChanSweepTimeAuto
– ChanVbwRbwRatio
– ChanVbwRbwRatioAuto
– ChanVideoBW
– ChanVideoBWAuto
– Electrical Atten
– Electrical Atten Bypass
– Electrical Atten State
– External1 Trigger Delay
– External1 Trigger Delay State
– External1 Trigger Level
– External1 Trigger Slope
Remote Language Compatibility Measurement Application Reference
589
6 Save/Recall
Save
– External2 Trigger Delay
– External2 Trigger Delay State
– External2 Trigger Level
– External2 Trigger Slope
– FilterAlpha
– Internal Preamp
– Internal Preamp Band
– Line Trigger Delay
– Line Trigger Delay State
– Line Trigger Slope
– Mechanical Atten
– Mechanical Atten Auto
– OffsetDetector
– OffsetDetectorState
– OffsetLimitAbsStartBTS
– OffsetLimitAbsStartMS
– OffsetLimitAbsStopBTS
– OffsetLimitAbsStopMS
– OffsetLimitFailMaskBTS
– OffsetLimitFailMaskMS
– OffsetLimitRelStartBTS
– OffsetLimitRelStartMS
– OffsetLimitRelStopBTS
– OffsetLimitRelStopMS
– OffsetMeasBWBTS
– OffsetMeasBWMS
– OffsetResolutionBWAutoBTS
590
Remote Language Compatibility Measurement Application Reference
6 Save/Recall
Save
– OffsetResolutionBWAutoMS
– OffsetResolutionBWBTS
– OffsetResolutionBWMS
– OffsetSideBTS
– OffsetSideMS
– OffsetStartFrequencyBTS
– OffsetStartFrequencyMS
– OffsetStateBTS
– OffsetStateMS
– OffsetStopFrequencyBTS
– OffsetStopFrequencyMS
– OffsetSweepTimeAutoBTS
– OffsetSweepTimeAutoMS
– OffsetSweepTimeBTS
– OffsetSweepTimeMS
– OffsetVbwRbwRatioAutoBTS
– OffsetVbwRbwRatioAutoMS
– OffsetVbwRbwRatioBTS
– OffsetVbwRbwRatioMS
– OffsetVideoBWAutoBTS
– OffsetVideoBWAutoMS
– OffsetVideoBWBTS
– OffsetVideoBWMS
– PeakReference
– Periodic Timer Period
– Periodic Timer Sync Source
– Periodic Timer Trigger Delay
Remote Language Compatibility Measurement Application Reference
591
6 Save/Recall
Save
– Periodic Timer Trigger Delay State
– PowerReference
– PSDReference
– Radio Device
– RFBurst Trigger Delay
– RFBurst Trigger Delay State
– RFBurst Trigger Level Abs
– RFBurst Trigger Level Rel
– RFBurst Trigger Level Type
– RFBurst Trigger Slope
– RrcFilter
– SemAverageNumber
– SemAverageState
– TotalAtten
– Trigger Holdoff
– Trigger Holdoff State
– TriggerSource
– Video Trigger Delay
– Video Trigger Delay State
– Video Trigger Level
– Video Trigger Slope
– ViewSelection
The file contains these data followed by MeasResult1 to MeasResult12, which flag
the start of the measurement results. Each line of Measurement Results consists of
twelve comma separated values from MeasResult1 value to MeasResult12 value.
MeasResult1 contains the same results as MEAS/READ/FETCh:SEMask1;
MeasResult2, MEAS/READ/FETCh:SEMask2; MeasResult3,
MEAS/READ/FETCh:SEMask3;… (continues in the same manner)
The exported file is in CSV format, with a.csv extension. The Meas Results file,
when imported into Excel, shows the following data:
592
Remote Language Compatibility Measurement Application Reference
6 Save/Recall
Save
MeasResu
lt
SA:SEM
A.10.53
N9
03
0A
526 ALV
ATP B1X
B1Y B25
B40 BBA
CR3 CRP
DCF DDA
DP2 DRD
EA3 EDP
EMC EP1
ERC ESC
ESP EXM
FSA LFE
LNP MAT
MPB NFE
NUL P26
PFR PNC
RTL RTS
S40 SB1
SEC SM1
TVT YAS
YAV
1
Automatic
Trigger
Time
0.1
Automatic
Trigger
Time
State
FA
LS
E
Center
Frequency
1.3
3E
+1
0
ChanInteg
BW
38
40
00
0
ChannelD
etector
Av
era
ge
ChannelD
etectorSt
ate
TR
UE
38
40
00
0
Remote Language Compatibility Measurement Application Reference
593
6 Save/Recall
Save
594
ChanPwrR
efAuto
TR
UE
ChanResB
W
10
00
00
10
00
00
ChanResB
WAuto
FA
LS
E
FA
LS
E
ChanSpan
50
00
00
0
50
00
00
0
ChanSwee
pTime
0.0
02
50
7
0.0
02
50
7
ChanSwee
pTimeAut
o
TR
UE
TR
UE
ChanVbw
RbwRatio
1
1
ChanVbw
RbwRatio
Auto
FA
LS
E
FA
LS
E
ChanVide
oBW
10
00
00
10
00
00
ChanVide
oBWAuto
TR
UE
TR
UE
Electrical
Atten
0
Electrical
Atten
Bypass
TR
UE
Electrical
Atten
State
FA
LS
E
External1
Trigger
Delay
1.0
0
E–
06
External1
Trigger
Delay
State
FA
LS
E
External1
1.2
Remote Language Compatibility Measurement Application Reference
6 Save/Recall
Save
Trigger
Level
External1
Trigger
Slope
Po
siti
ve
External2
Trigger
Delay
1.0
0
E–
06
External2
Trigger
Delay
State
FA
LS
E
External2
Trigger
Level
1.2
External2
Trigger
Slope
Po
siti
ve
FilterAlph
a
0.2
2
Internal
Preamp
FA
LS
E
Internal
Preamp
Band
Lo
w
Line
Trigger
Delay
1.0
0
E–
06
Line
Trigger
Delay
State
FA
LS
E
Line
Trigger
Slope
Po
siti
ve
Mechanic
al Atten
10
Mechanic
al Atten
Auto
TR
UE
OffsetDet
ector
Pe
ak
OffsetDet
TR
Remote Language Compatibility Measurement Application Reference
595
6 Save/Recall
Save
596
ectorStat
e
UE
OffsetLimi
tAbsStart
BTS
–
14
–
14
–
26
–13
–
13
–
13
OffsetLimi
tAbsStart
MS
–
14
–
14
–
26
–13
–
13
–
13
OffsetLimi
tAbsStopB
TS
–
14
–
26
–
26
–13
–
13
–
13
OffsetLimi
tAbsStop
MS
–
14
–
26
–
26
–13
–
13
–
13
OffsetLimi
tFailMask
BTS
AB
Sol
ute
AB
Sol
ute
AB
Sol
ute
ABSol
ute
AB
Sol
ute
AB
Sol
ute
OffsetLimi
tFailMask
MS
AB
Sol
ute
AB
Sol
ute
AB
Sol
ute
ABSol
ute
AB
Sol
ute
AB
Sol
ute
OffsetLimi
tRelStartB
TS
–
30
–
30
–
30
–30
–
30
–
30
OffsetLimi
tRelStart
MS
–
30
–
30
–
30
–30
–
30
–
30
OffsetLimi
tRelStopB
TS
–
30
–
30
–
30
–30
–
30
–
30
OffsetLimi
tRelStop
MS
–
30
–
30
–
30
–30
–
30
–
30
OffsetMea
sBWBTS
1
1
1
1
1
1
OffsetMea
sBWMS
1
1
1
1
1
1
OffsetRes
olutionBW
AutoBTS
FA
LS
E
FA
LS
E
FA
LS
E
FALS
E
FA
LS
E
FA
LS
E
OffsetRes
olutionBW
AutoMS
FA
LS
E
FA
LS
E
FA
LS
E
FALS
E
FA
LS
E
FA
LS
E
OffsetRes
olutionBW
BTS
30
00
0
30
00
0
30
00
0
10000
00
10
00
00
0
10
00
00
0
Remote Language Compatibility Measurement Application Reference
6 Save/Recall
Save
OffsetRes
olutionBW
MS
30
00
0
30
00
0
30
00
0
10000
00
10
00
00
0
10
00
00
0
OffsetSide
BTS
Bo
th
Bo
th
Bo
th
Both
Bo
th
Bo
th
OffsetSide
MS
Bo
th
Bo
th
Bo
th
Both
Bo
th
Bo
th
OffsetStar
tFrequenc
yBTS
25
15
00
0
27
15
00
0
35
15
00
0
40000
00
80
00
00
0
12
50
00
00
OffsetStar
tFrequenc
yMS
25
15
00
0
27
15
00
0
35
15
00
0
40000
00
80
00
00
0
12
50
00
00
OffsetStat
eBTS
TR
UE
TR
UE
TR
UE
TRUE
TR
UE
FA
LS
E
OffsetStat
eMS
TR
UE
TR
UE
TR
UE
TRUE
TR
UE
FA
LS
E
OffsetStop
Frequency
BTS
27
15
00
0
35
15
00
0
40
00
00
0
80000
00
12
50
00
00
15
00
00
00
OffsetStop
Frequency
MS
27
15
00
0
35
15
00
0
40
00
00
0
80000
00
12
50
00
00
15
00
00
00
OffsetSwe
epTimeAu
toBTS
TR
UE
TR
UE
TR
UE
TRUE
TR
UE
TR
UE
OffsetSwe
epTimeAu
toMS
TR
UE
TR
UE
TR
UE
TRUE
TR
UE
TR
UE
OffsetSwe
epTimeBT
S
0.0
17
33
3
0.0
69
32
0.0
42
02
7
0.002
053
0.0
02
25
3
0.0
01
25
3
OffsetSwe
epTimeM
S
0.0
17
33
3
0.0
69
32
0.0
42
02
7
0.002
053
0.0
02
25
3
0.0
01
25
3
OffsetVbw
RbwRatio
AutoBTS
FA
LS
E
FA
LS
E
FA
LS
E
FALS
E
FA
LS
E
FA
LS
E
Remote Language Compatibility Measurement Application Reference
597
6 Save/Recall
Save
598
OffsetVbw
RbwRatio
AutoMS
FA
LS
E
FA
LS
E
FA
LS
E
FALS
E
FA
LS
E
FA
LS
E
OffsetVbw
RbwRatio
BTS
0.0
1
0.0
1
0.0
1
0.01
0.0
1
0.0
1
OffsetVbw
RbwRatio
MS
0.0
1
0.0
1
0.0
1
0.01
0.0
1
0.0
1
OffsetVide
oBWAuto
BTS
TR
UE
TR
UE
TR
UE
TRUE
TR
UE
TR
UE
OffsetVide
oBWAuto
MS
TR
UE
TR
UE
TR
UE
TRUE
TR
UE
TR
UE
OffsetVide
oBWBTS
30
0
30
0
30
0
10000
10
00
0
10
00
0
OffsetVide
oBWMS
30
0
30
0
30
0
10000
10
00
0
10
00
0
PeakRefer
ence
–
82.
99
57
Periodic
Timer
Period
0.0
2
Periodic
Timer
Sync
Source
No
ne
Periodic
Timer
Trigger
Delay
1.0
0
E–
06
Periodic
Timer
Trigger
Delay
State
FA
LS
E
PowerRef
erence
–
73.
69
66
PSDRefer
ence
–
13
Remote Language Compatibility Measurement Application Reference
6 Save/Recall
Save
9.5
4
Radio
Device
Bts
RFBurst
Trigger
Delay
1.0
0
E–
06
RFBurst
Trigger
Delay
State
FA
LS
E
RFBurst
Trigger
Level Abs
–
20
RFBurst
Trigger
Level Rel
–6
RFBurst
Trigger
Level Type
Ab
sol
ute
RFBurst
Trigger
Slope
Po
siti
ve
RrcFilter
FA
LS
E
SemAvera
geNumber
10
SemAvera
geState
FA
LS
E
TotalAtten
10
Trigger
Holdoff
0.1
Trigger
Holdoff
State
FA
LS
E
TriggerSo
urce
Fre
e
Video
Trigger
Delay
1.0
0
E–
06
Video
FA
Remote Language Compatibility Measurement Application Reference
599
6 Save/Recall
Save
Trigger
Delay
State
LS
E
Video
Trigger
Level
–
25
Video
Trigger
Slope
Po
siti
ve
Video
Selection
Ab
sP
wr
Fre
q
MeasResu
lt1
Me
as
Re
sul
t2
Me
as
Re
sul
t3
Me
as
Re
sul
t4
Meas
Resul
t5
Me
as
Re
sul
t6
Me
as
Re
sul
t7
Me
as
Re
sul
t8
Me
as
Re
sul
t9
Me
asR
esu
lt10
Me
asR
esu
lt11
Me
asR
esu
lt12
–999
–
78.
89
35
9
–
13
99
9
–
73.69
66334
09987
9
–
99
9
–
99
9
–
99
9
–
99
9
–
999
–
999
–
999
–
73.696633
4099879
–
78.
95
23
5
–
13
99
9
–999
–
99
9
–
99
9
–
99
9
–
99
9
–
999
–
999
SPUR Meas Results File Contents
The content of a Meas Results File is defined in this section.
The first lines in the file consist of identification and instrument configuration
details, as follows.
– File ID string, which is “MeasResult”
– Measurement ID following Mode ID, which is “SA:SPUR” for example.
– Firmware rev and model number
– Option string
– Abs Start Limit
– Abs Stop Limit
– Abs Stop Limit Mode
600
Remote Language Compatibility Measurement Application Reference
6 Save/Recall
Save
– Auto Scaling
– Auto Sweep Time Rules
– Automatic Trigger Time
– Automatic Trigger Time State
– Average Mode
– Average Number
– Average State
– Detector 1
– Detector 2
– Electrical Atten
– Electrical Atten State
– External Array Trigger Delay
– External Array Trigger Delay State
– External Array Trigger Level
– External Array Trigger Slope
– Filter Type
– IF Gain Auto
– IF Gain State
– Internal Preamp
– Internal Preamp Band
– Line Trigger Delay
– Line Trigger Delay State
– Line Trigger Slope
– Meas Type
– Mechanical Atten
– MechanicalAttenStepEnum
– Peak Excursn
Remote Language Compatibility Measurement Application Reference
601
6 Save/Recall
Save
– Periodic Timer Period
– Periodic Timer Sync Source
– Periodic Timer Trigger Delay
– Periodic Timer Trigger Delay State
– Pk Threshold
– Points
– Points Mode
– Range State
– Ref Value
– Res BW
– Res BW Mode
– RFBurst Trigger Delay
– RFBurst Trigger Delay State
– RFBurst Trigger Level Abs
– RFBurst Trigger Level Rel
– RFBurst Trigger Level Type
– RFBurst Trigger Slope
– Scale/Div
– Spurious Report Mode
– SpurRangeStartFrequecnyArray
– SpurRangeStopFrequencyArray
– Sweep Time
– Sweep Time Mode
– Trigger Holdoff
– Trigger Holdoff State
– TriggerSource
– Video BW
602
Remote Language Compatibility Measurement Application Reference
6 Save/Recall
Save
– Video BW Mode
The data above is followed in the file by a line containing “MeasResult1” to
“MeasResult42”. This line forms a header for each set of measurement results,
which appear in subsequent lines. Each line of Measurement Results consists of 42
comma-separated values, from the MeasResult1 value to the MeasResult42
value.
The MeasResult1 set in the file corresponds to the data returned by
MEAS/READ/FETCh:SPURious1; the MeasResult2 set corresponds to the data
returned by MEAS/READ/FETCh:SPURious2, and so on.
The exported file is in CSV format, with a .csv extension.
Meas Results File Example
When imported into Excel, a typical Meas Results file appears as shown in the
example below.
NOTE: The following table omits the columns for MeasResult11 to MeasResult42,
due to lack of space.
MeasResult
1
2
3
4
5
6
7
8
9
10
SA:SPUR
A.10.53
N90
30A
526 ALV ATP
B1X B1Y B25
B40 BBA CR3
CRP DCF
DDA DP2
DRD EA3
EDP EMC
EP1 ERC ESC
ESP EXM
FSA LFE LNP
MAT MPB
NFE NUL P26
PFR PNC RTL
RTS S40 SB1
SEC SM1
TVT YAS YAV
1
Abs Start
Limit
–50
–50
–50
–50
–50
–50
–50
–50
–50
–50
Abs Stop
Limit
–50
–50
–50
–50
–50
–50
–50
–50
–50
–50
Abs Stop
Limit Mode
TR
UE
TR
UE
TR
UE
TR
UE
TR
UE
TR
UE
TR
UE
TR
UE
TRU
E
TRU
E
Auto Scaling
TR
UE
Auto Sweep
Nor
Remote Language Compatibility Measurement Application Reference
603
6 Save/Recall
Save
604
Time Rules
m
Automatic
Trigger Time
0.1
Automatic
Trigger Time
State
FAL
SE
Average
Mode
Exp
one
ntia
l
Average
Number
10
Average
State
FAL
SE
Detector 1
Pea
k
Pea
k
Pea
k
Pea
k
Pea
k
Pea
k
Pea
k
Pea
k
Pea
k
Pea
k
Detector 2
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Electrical
Atten
0
Electrical
Atten State
FAL
SE
External
Array Trigger
Delay
1.0
0E–
06
1.0
0E–
06
External
Array Trigger
Delay State
FAL
SE
FAL
SE
External
Array Trigger
Level
1.2
1.2
External
Array Trigger
Slope
Pos
itive
Pos
itive
Filter Type
Gau
ssia
n
Gau
ssia
n
Gau
ssia
n
Gau
ssia
n
Gau
ssia
n
Gau
ssia
n
Gau
ssia
n
Gau
ssia
n
Gau
ssia
n
Gau
ssia
n
IF Gain Auto
FAL
SE
FAL
SE
FAL
SE
FAL
SE
FAL
SE
FAL
SE
FAL
SE
FAL
SE
FAL
SE
FAL
SE
IF Gain State
FAL
SE
FAL
SE
FAL
SE
FAL
SE
FAL
SE
FAL
SE
FAL
SE
FAL
SE
FAL
SE
FAL
SE
Internal
Preamp
FAL
SE
Internal
Preamp Band
Low
Line Trigger
1.0
Remote Language Compatibility Measurement Application Reference
6 Save/Recall
Save
Delay
0E–
06
Line Trigger
Delay State
FAL
SE
Line Trigger
Slope
Pos
itive
Meas Type
Exa
min
e
Mechanical
Atten
10
MechanicalA
ttenStepEnu
m
S2d
B
Peak Excursn
6
Periodic
Timer Period
0.02
Periodic
Timer Sync
Source
Non
e
Periodic
Timer Trigger
Delay
1.0
0E–
06
Periodic
Timer Trigger
Delay State
FAL
SE
Pk Threshold
6
6
6
6
6
6
6
6
6
–90
–90
–90
–90
–90
–90
–90
–90
–90
–90
Points
601
601
601
601
601
601
601
601
601
601
Points Mode
FAL
SE
FAL
SE
FAL
SE
FAL
SE
FAL
SE
FAL
SE
FAL
SE
FAL
SE
FAL
SE
FAL
SE
Range State
TR
UE
TR
UE
TR
UE
TR
UE
TR
UE
FAL
SE
FAL
SE
FAL
SE
FAL
SE
FAL
SE
Ref Value
0
Res BW
120
000
0
510
000
100
000
100
000
400
000
0
300
000
0
300
000
0
300
000
0
300
0000
300
0000
Res BW
Mode
FAL
SE
FAL
SE
FAL
SE
FAL
SE
FAL
SE
TR
UE
TR
UE
TR
UE
TRU
E
TRU
E
RFBurst
Trigger Delay
1.0
0E–
06
RFBurst
Trigger Delay
State
FAL
SE
Remote Language Compatibility Measurement Application Reference
605
6 Save/Recall
Save
606
RFBurst
Trigger Level
Abs
–20
RFBurst
Trigger Level
Rel
–6
RFBurst
Trigger Level
Type
Abs
olut
e
RFBurst
Trigger Slope
Pos
itive
Scale/Div
10
Spurious
Report Mode
All
SpurRangeSt
artFrequecny
Array
1.9
2E+
09
1.8
9E+
09
2.1
E+0
9
2.1
8E+
09
8E+
08
1.5
E+0
9
1.5
E+0
9
1.5
E+0
9
1.5E
+09
1.5E
+09
SpurRangeSt
opFrequency
Array
1.9
8E+
09
1.9
2E+
09
2.1
E+0
9
2.1
8E+
09
1E+
09
2.5
E+0
9
2.5
E+0
9
2.5
E+0
9
2.5E
+09
2.5E
+09
Sweep Time
0.0
01
0.0
01
0.0
012
0.0
039
6
0.0
01
0.0
01
0.0
01
0.0
01
0.00
1
0.00
1
Sweep Time
Mode
TR
UE
TR
UE
TR
UE
TR
UE
TR
UE
TR
UE
TR
UE
TR
UE
TRU
E
TRU
E
Trigger
Holdoff
0.1
Trigger
Holdoff State
FAL
SE
TriggerSourc
e
Fre
e
Video BW
120
000
510
00
100
00
100
00
390
000
300
000
300
000
300
000
300
000
300
000
Video BW
Mode
TR
UE
TR
UE
TR
UE
TR
UE
TR
UE
TR
UE
TR
UE
TR
UE
TRU
E
TRU
E
MeasResult1
Me
asR
esul
t2
Me
asR
esul
t3
Me
asR
esul
t4
Me
asR
esul
t5
Me
asR
esul
t6
Me
asR
esul
t7
Me
asR
esul
t8
Me
asR
esul
t9
Mea
sRes
ult1
0
Mea
sRes
ult1
1
19
–
80.
272
09
–
80.
878
62
–
90.
945
77
–
89.
270
86
–
76.
778
56
9.9
1E+
37
9.9
1E+
37
9.9
1E+
37
9.91
E+37
9.91
E+37
1
–
78.
284
97
–
80.
939
96
–
91.
004
85
–
90.
560
63
–
76.
339
68
Remote Language Compatibility Measurement Application Reference
6 Save/Recall
Save
CCDF Meas Results File Contents
The content of a Meas Results File is defined in this section.
The first lines in the file consist of identification and instrument configuration
details, as follows.
– File ID string, which is “MeasResult”
– Measurement ID following Mode ID, which is “SA:PST” for example.
– Firmware rev and model number
– Option string
– Automatic Trigger Time
– Automatic Trigger Time State
– CcdfCurrentCounts
– Center Frequency
– Center Frequency Step
– Center Frequency Step State
– Counts
– Electrical Atten
– Electrical Atten State
– External Array Trigger Delay
– External Array Trigger Delay State
– External Array Trigger Level
– External Array Trigger Slope
– Gaussian Line
– IF Gain Auto
– IF Gain State
– Info BW
– Internal Preamp
– Internal Preamp Band
– Line Trigger Delay
Remote Language Compatibility Measurement Application Reference
607
6 Save/Recall
Save
– Line Trigger Delay State
– Line Trigger Slope
– Meas Cycles
– MeasInterval
– Mechanical Atten
– MechanicalAttenStepEnum
– Periodic Timer Period
– Periodic Timer Sync Source
– Periodic Timer Trigger Delay
– Periodic Timer Trigger Delay State
– Preselector Adjust
– Ref Trace
– RFBurst Trigger Delay
– RFBurst Trigger Delay State
– RFBurst Trigger Level Abs
– RFBurst Trigger Level Rel
– RFBurst Trigger Level Type
– RFBurst Trigger Slope
– Scale/Div
– Trigger Holdoff
– Trigger Holdoff State
– TriggerSource
The data above is followed in the file by a