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.
Manual Part Number
N9020-90095
Edition
Edition: 9, October 2019
Supersedes: July 2019
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.
U.S Government Rights
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 U.S. 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 U.S. 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 U.S. 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
U.S. 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.
Warranty
THEMATERIALCONTAINEDINTHIS
DOCUMENTISPROVIDED “ASIS,” ANDIS
SUBJECTTOBEINGCHANGED, WITHOUT
NOTICE, INFUTUREEDITIONS. FURTHER, TO
THEMAXIMUMEXTENTPERMITTEDBY
APPLICABLELAW, KEYSIGHTDISCLAIMSALL
WARRANTIES, EITHEREXPRESSORIMPLIED,
WITHREGARDTOTHISMANUALANDANY
INFORMATIONCONTAINEDHEREIN,
INCLUDINGBUTNOTLIMITEDTOTHE
IMPLIEDWARRANTIESOFMERCHANTABILITY
ANDFITNESSFORAPAR TICU LAR PURPOSE.
K
EYSIGHTSHALLNOTBELIABLEFOR
ERRORSORFORINCIDENTALOR
CONSEQUENTIALDAMAGESINCONNECTION
WITHTHEFURNISHING, USE, OR
PERFORMANCEOFTHISDOCUMENTOROF
ANYINFORMATIONCONTAINEDHEREIN.
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.
2
Page 3
Where to Find the Latest Information
Documentation is updated periodically. For the latest information about these
products, including instrument software upgrades, application information, and
product information, see the following URLs:
http://www.keysight.com/find/pxe
http://www.keysight.com/find/uxa
http://www.keysight.com/find/pxa
http://www.keysight.com/find/mxa
http://www.keysight.com/find/exa
http://www.keysight.com/find/cxa
http://www.keysight.com/find/mxe
http://www.keysight.com/find/nfa
To receive the latest updates by email, subscribe to Keysight Email Updates:
http://www.keysight.com/find/emailupdates
Information on preventing instrument damage can be found at:
Periodically, Keysight releases software updates to fix known defects and incorporate
product enhancements. To search for software updates for your product, go to the
Keysight Technical Support website at:
http://www.keysight.com/find/techsupport
3
Page 4
Table of Contents
List of Instrument Messages 6
1 Overview of Instrument Messaging System24
A-Series and B-Series Differences24
Message Types24
Event and Condition Categories26
Error Message Fields29
Event Queues & Displays30
Message Display & Controls32
Instrument Messages Guide
Contents
Event Categories27
Condition Categories28
A-Series32
B-Series32
Event Message Boxes32
Status Bar34
Status Dialog34
2 Instrument Messages35
Advisory Messages36
Event Messages42
–800, Operation Complete Event43
–700, Request Control Event43
–600, User Request Event 43
–500, Power on Event 43
–400 to –499, Query Errors43
–300 to –399, Device-Specific Errors45
–221 Settings Conflict Errors48
–200 to –299, Execution Errors67
–100 to –199, Command Errors84
0 No Error86
Condition Messages87
1 to 99, Calibration87
6 to 34, Calibration Skipped87
36 to 64, Calibration Needed or Failed88
65 to 92, Calibration Needed (Extended)90
67 to 95, Calibration Failure (Extended)91
101 to 199, Measurement Integrity92
201 to 299, Signal Integrity97
4
Page 5
301 to 399, Uncalibrated Integrity102
401 to 499, Power106
501 to 599, Frequency108
601 to 699, Error Summaries109
701 to 799, Operation110
801 to 899, Temperature111
3 Status Register System & SCPI STATus Subsystem 114
Where to find Detailed Information114
Status Register System Overview115
Appendix A References118
Documents & Web Sites118
Contents
5
Page 6
List of Instrument Messages
This list includes every Instrument Message described in this document, in alphabetical order.
2nd LO Unlocked108
AC coupled: Accy unspec’d <10 MHz103
ADC Alignment Failure89
Align 30MHz to 1GHz failed92
Align 30MHz–1GHz required90
Align 9kHz to 30MHz failed91
Align 9kHz–30MHz required90
Align Now, All required90
Align Now, RF required90
Align RF Skipped88
Align Skipped Sum Summary90
Align Source IQ failed92
Align Source RF failed92
All Auto/Man functions have been set to Auto36
All Auto/Man functions have been set to Auto.36
All ranges are off. Turn on at least a range68
Allowable Center Frequency exceeded for the current span36
Allowable Span exceeded for the current center frequency36
Allowable Start Frequency exceeded for the current span36
Allowable Stop frequency exceeded for the current span36
Allowable X Ref Level exceeded for the current Capture Length36
Allowable X Scale/Div exceeded for the current Capture Length36
Already in Single, press Restart to initiate a new sweep or sequence36
Antenna Unit already in used in another range78
Arm deadlock71
Arm ignored70
At Full Zoom68
Auto sweep time rules do not apply in FFT sweeps36
Band Adjust has no effect on a Fixed marker37
Band Adjust has no effect with Mkr Function Off37
Band-pass filter set to OFF37
Block data error85
Block data not allowed85
Burst Not Found99
Burst not found;with selected Time Slot99
Cal Cancelled; Calibration data cleared37
Cal Invalid: meas freq pt(s) > 3.6GHz are > 50MHz from existing Cal pts37
Instrument Messages Guide
List of Instrument Messages
6
Page 7
List of Instrument Messages
Calibrating111
Calibration failed; <failure msg><port>47
Calibration memory lost46
Calibration Oscillator Unlocked108
Calibration105
Calibration110
Calibration; ENR table extrapolated105
Calibration; No ENR data present105
Cannot create program82
Cannot move marker outside of displayed frequency span68
Carrier power is too low for optimum dynamic range.37
Carrier(s) incorrect or missing100
Character data error85
Character data not allowed85
Character data too long85
Characterize Noise Floor required91
Characterize Preselector failure92
Characterize Preselector required91
Command error84
Command header error84
Command protected70
Command protected; feature not licensed70
Command protected;Feature Not Supported. No appropriate waveform license installed for
<filename>70
Communication error47
Communication error; SNS data read failure. Disconnect then reconnect SNS47
Communication error; SNS is not connected47
Configuration memory lost47
Connecting to source…37
Corrupt media81
Data corrupt or stale; Measurement data is not available76
Data corrupt or stale; Trace contains no data.76
Data corrupt or stale; Unable to load state from file76
Data corrupt or stale;76
Data out of Range; clipped to source max/min73
Data out of Range; Dwell Time clipped to minimum value allowed73
Data out of range; Invalid list data73
Data out of range; Invalid slice data at the number specified73
Data out of range; Invalid Correction Group range data73
Data out of Range; Scan Time limited, multiple CISPR det’s in use for prescan73
Data out of Range; Step Size clipped to nearest value allowed73
Data out of range; Two entries already exist at this x-axis value.74
Data out of range;73
Instrument Messages 7
Page 8
List of Instrument Messages
Data out of range;Calibration Date (YYYYMMDD) is invalid74
Data questionable76
Data type error84
DC Coupled111
De-emphasis only available in FM48
Demod Error101
Demod Error;Acq Time too short102
Demod Error;Can’t correlate101
Demod Error;Data interval too short101
Demod Error;Muxed bits not found101
Demod Error;No active channel101
Demod Error;No full subframe found101
Demod Error;Not an active slot101
Demod Time is not available in Zero Span37
Demodulation108
Detector <X> changed due to physical constraints37
Device-specific error45
Directory full81
Disturbance List is Empty68
Disturbance selected is not in the Disturbance List68
Dynamic range is not optimum. Set AUTO RF input.37
Execution Error68
Execution error; Carrier frequency outside device’s transmit band68
Execution Error; Data in Correction File Range x File x does not cover the range frequency
span68
Execution error; Invalid GSM burst timing68
Execution error; Invalid IP address68
Execution error; Invalid Marker Trace.68
Execution Error; No peak found.68
Execution error; No ranges are defined. Activate a range.69
Execution Error; Preselector centering failed69
Execution Error; Signal not stable enough to track69
Execution Error; Store ref trace before turning on Normalize69
Execution error; Sync word was not found.69
Execution error; Trace file contains no compatible traces.69
Execution error; Trace file created by incompatible version of Phase Noise App69
Exp. Averaging not available when AUTO PhNoise is active.37
Exponent too large84
Expression data not allowed85
Expression error82
Expression error85
Extended Align Failure Summary90
Extended Align Needed Summary89
Instrument Messages 8
Page 9
List of Instrument Messages
FFT Width is not settable unless Sweep Type is set to FFT37
File <filename> saved37
File name error; Allowable extension is .csv81
File name error; Allowable extension is .png81
File name error; Allowable extension is .state81
File name error; Invalid file name81
File name error; name too long81
File name error;81
File name error;<filename> contains unrecognized file suffix81
File name error;Waveform file not selected81
File name not found;81
File name not found:<file name>81
Filter BW function is only available for Gaussian filter type37
Fixed LO freq should be greater than RF Stop freq38
FM Demod Alignment Failure89
Framing error in program message47
Freq Out of Range100
Freq Out of Range; External LO100
Freq Out of Range; System input (IF)100
Freq Scale Type=Log is not available in Zero Span38
Frequency Hopping enabled, waiting for valid burst38
Frequency menu has changed to reflect frequency context switch38
Frequency Reference Unlocked108
Frequency110
Full Bypass Enabled, maximum safe input power reduced107
Function not available before Marker Zoom is performed69
Function not available before perform Disturbance Zoom69
Function not available before Signal Zoom is performed69
Function not available in Zero Span48
Gate required for valid results38
GET not allowed84
Hardware error77
Hardware error; See details in Windows Event Log under SA77
Hardware missing77
Hardware missing; Input not available77
Hardware missing; Internal preamp not available at all frequency points77
Hardware missing; not available for this model number77
Hardware missing; Option not installed77
Hardware missing; Output not available77
Hardware missing; Power sensor hardware is missing78
Header separator error84
Header suffix out of range84
High-pass and Low-pass filters set to OFF38
Instrument Messages 9
Page 10
List of Instrument Messages
High-pass filter set to OFF38
I/O Error95
I/O Error; Ext Source needs IP Addr95
IF Alignment Failure89
IF Fixed freq should be greater than LO Stop freq38
IF Fixed freq should be greater than RF Stop freq38
IF Start freq should be greater than LO Fixed freq38
IF Start freq should be greater than RF Start freq38
IF Synthesizer Unlocked108
Illegal macro label82
Illegal parameter value74
Illegal parameter value; <Value> invalid. Fractional values are not allowed.74
Illegal parameter value; <value> out of range.74
Illegal parameter value; Cannot set waveform to continue previous waveform on the first
step74
Illegal parameter value; EMI Avg/RMS Avg and Average detector can’t be used together74
Illegal parameter value; Exceeding the max list length74
Illegal parameter value; existing Screen Name not found74
Illegal parameter value; Gated FFT is not available while Sweep Type is set to Swept74
Illegal parameter value; Gated LO is not available while Sweep Type is set to FFT75
Illegal parameter value; Gated Video is not available while Sweep Type is set to FFT75
Illegal parameter value; Index out of range75
Illegal parameter value; Invalid list length75
Illegal parameter value; Measurement not available75
Illegal parameter value; new Name already exists75
Illegal parameter value; QPD + EMI Average + RMS Average is not allowed75
Illegal parameter value; Res BW value not allowed with current Span75
Illegal parameter value;Cannot set waveform to continue previous waveform when previous step is
set to CW or Off75
Illegal parameter value;Channel number is invalid for current band/link combination75
Illegal parameter value;This instrument is always DC coupled75
Illegal parameter value;This model is always AC coupled76
Illegal program name82
Illegal variable name82
Incompatible type83
Init ignored70
Input Attenuation not calibrated91
Input buffer overrun47
Input caution107
Input caution;T/R unprotected107
Input is internal38
Input Overload107
Input Overload93
Instrument Messages 10
Page 11
List of Instrument Messages
Input Overload;ADC over range94
Input Overload;Gen reverse power107
Input Overload;I/Q ADC over range94
Input Overload;I/Q Voltage over range94
Input Overload;RF Preselector Overload94
Input Overload;T/R port107
Insufficient Data94
Insufficient Data; ENR table empty94
Insufficient Data; frequency list empty94
Insufficient Data; Incr. Demod Time94
Insufficient Data; Loss table empty95
Insufficient Data; trigger received before current segment is complete95
Integrity110
Invalid block data85
Invalid character data85
Invalid character in number84
Invalid character84
Invalid Data95
Invalid expression85
Invalid format76
Invalid format; Map information not loaded76
Invalid format;<filename> contains invalid waveform header and cannot be loaded into ARB
memory77
Invalid format;<filename> has less than 500 IQ samples77
Invalid format;Syntax error on source step <step number>77
Invalid format;Unable to open encrypted waveform file <filename>77
Invalid inside macro definition86
Invalid outside macro definition85
Invalid separator84
Invalid string data85
Invalid suffix85
Invalid version77
Invalid while in local70
List not same length76
LO Alignment Failure89
LO Fixed freq should be greater than IF Stop freq39
LO Fixed freq should be greater than RF Stop freq39
LO Start freq should be greater than IF Fixed freq39
LO Start freq should be greater than RF Start freq39
LO Stop freq should be greater than RF Stop freq39
LO Unleveled107
LO Unlocked108
Low-pass filter set to OFF39
Instrument Messages 11
Page 12
List of Instrument Messages
Macro definition too long82
Macro error82
Macro error85
Macro execution error82
Macro header not found82
Macro parameter error82
Macro parameter error86
Macro recursion error82
Macro redefinition\ not allowed82
Macro syntax error82
Mass storage error; Access denied78
Mass storage error; Bad path name78
Mass storage error; Can only import single trace .csv files78
Mass storage error; Can only load an Antenna Unit into Correction 178
Mass storage error; Can only load one file with Antenna Unit per range78
Mass storage error; Cannot make78
Mass storage error; Different Antenna Unit already in use78
Mass storage error; Different78
Mass storage error; Directory not found78
Mass storage error; Failed to Load trace. Bad file format.78
Mass storage error; File <filename> and instrument version mismatch78
Mass storage error; File <filename> wrong type79
Mass storage error; File <filename>. Model and serial number fields don’t match selected
sensor79
Mass storage error; File contains incorrect data for this operation79
Mass storage error; File empty79
Mass storage error; Invalid register number for *SAV or *RCL Mass Storage error79
Mass storage error; Lock violation79
Mass storage error; Mkr Table must be on to save Mkr Table as Meas Results79
Mass storage error; No file names available79
Mass storage error; Open failed79
Mass storage error; Pk Table must be on to save Pk Table as Meas Results79
Mass storage error; Read fault79
Mass storage error; Register <number> empty79
Mass storage error; Sharing violation80
Mass storage error; Spectrogram must be on to save as Meas Results80
Mass storage error; Too many open files80
Mass storage error; Write fault80
Mass storage error;78
Mass storage error;<directory> does not exist80
Mass storage error;<filename> cannot be deleted as it is currently in use80
Mass storage error;<filename> cannot be deleted as it is used in sequencer80
Mass storage error;<filename> used by sequencer is not in the ARB memory, cannot start
Instrument Messages 12
Page 13
List of Instrument Messages
sequencer80
Mass storage error;Create Directory Error: <directory> <err info>80
Mass storage error;Delete File Error: <filename> <err info>80
Mass storage error;Write File Error: <filename> <err info>80
Math error in expression82
Meas Error95
Meas Error; Power meter error95
Meas Uncal103
Measuring111
Media full81
Media Full;<filename> cannot be loaded to ARB memory81
Media Protected82
Memory error46
Memory Error95
Memory Error;Shorten capture interval95
Memory use errors82
Missing media80
Missing parameter84
MPA Align failed92
MPA Align required91
Must perform Scan before do Search69
No error86
No Long Code Phase103
No marked signal69
No Measure At Marker Added to Signal List69
No Peak Added to Signal List70
No Result93
No Result; Meas invalid with I/Q inputs93
No Result;Meas/Radio Std incompatibility93
No Result;Turn on MCE93
No spurs have been found39
No unmarked signals70
Numeric data error84
Numeric data not allowed84
Operation complete43
Operation complete; Loaded <ARB filename> successfully, but no license <required licenses>
installed43
Out of memory47
Out of memory76
Out of memory83
Out of memory; Insufficient resources to load Mode <mode name>76
Out of memory; Insufficient resources to load Mode <mode name>. Paging file size too
small76
Instrument Messages 13
Page 14
List of Instrument Messages
Out of memory; Memory limit caused Data Acquisition to be truncated76
Out of memory; Results truncated47
Out of memory; Sequence too long47
Out of memory; Total analysis step reaches its limitation47
Over current: reboot112
Over Range94
Over temperature: let cool and reboot112
Over temperature112
Over temperature; T/R port112
Parameter error71
Parameter error; <filename> is not loaded into ARB memory. Load the file before assigning to a
multi-pack71
Parameter error; License slot <n> is illegal, slot number must be positive71
Parameter error;<filename> does not have a unique id, therefore cannot be assigned to a
multi-pack71
Parameter error;Cannot create directory to save waveform sequence file. <error info>71
Parameter error;Cannot find the first waveform file <filename>71
Settings conflict;QPD + EMI Average + RMS Average is not allowed66
Settings conflict;Range <{0}> is turned off as total range points > 4,000,001.67
Settings conflict;Scan Time & Points do not apply in current Step/Time Control.67
Settings conflict;Screen limit reached67
Settings conflict;Screen SCPI cannot be used when Display is disabled67
Settings conflict;Step Size & Meas Time do not apply in current Step/Time Control.67
Settings conflict;The number of input parameters is too large and is truncated to current list step
number67
Settings conflict;Transition time may be short on step <step number>.67
Settings lost due to rtl70
Settling111
Signal ID on103
Signal List is Empty70
Signal List is Full70
Signal Selected is not in the Signal List70
Signal selected is out of display range70
Instrument Messages 21
Page 22
List of Instrument Messages
Signal Summary93
Signal Too Noisy102
Signal Track is turned off when Zero Span is selected40
Signals deleted41
Slot Error102
Slot Error; No idle slot found102
Slot error;No active slot found102
Source LO Unleveled107
Source Sweeping111
Source Synth Unlocked108
Source Uncal105
Source Uncal;adj Start Freq or RBW105
Source Uncal;adjust Source Amplitude105
Source Unleveled107
Source Waiting for Trigger111
Storage fault;47
String data error85
String data not allowed85
Suffix error85
Suffix not allowed85
Suffix too long85
Sweep Points/Span is < minimum. Results may be inaccurate.41
Sweep Setup is not available in Zero Span41
Sweeping111
Sync Error100
Sync Error;Midamble sync fail100
Sync Error;No freq ref pilot burst100
Sync Error;No pilot burst100
Sync Error;Preamble length zero100
Sync Error;Sync code not found100
Sync is RF Ampl (not Training Sequence). Bits are not accurate.41
Syntax error84
System error; <feature> expired, please reboot within <time>45
System error; <feature> expired, rebooting in <time>45
System Error; <filename> not recalled45
System error; A license will soon expire;<feature code> will expire in <time>45
System Error; enable GPIB controller mode45
System error; feature <feature code> not licensed45
System error; Feature expired; <feature code>45
System error; License installation failed;<feature code>45
System error; License removal failed; <feature code>45
System error; No license; <feature code> will terminate in <time>45
System Error; No power meter or sensor is selected46
Instrument Messages 22
Page 23
List of Instrument Messages
System Error; No supported source found46
System Error; Power meter or sensor calibrate failure46
System Error; Power meter or sensor calibration required46
System Error; Power meter or sensor not responding or connection timeout. Please check your
power meter connection and try again.46
System Error; Power meter or sensor zero and calibration required46
System Error; Power meter or sensor zero failure46
System Error; Power meter or sensor zero required46
System Error; source connection lost, check interface connection46
System error;45
Temperature110
TG Alignment Failure89
Time out error47
Time out error; Operation on source is held. If analyzer is waiting for trigger, change to free run to
proceed48
Timing Error99
Timing Error:No time ref pilot burst100
Too many digits84
Too much data74
Too much data; 200 spurs found. Additional spurs ignored.74
Trace file saved.41
Trig Error95
Trigger deadlock70
Trigger error70
Trigger ignored70
Uncalibrated Summary93
Undefined header84
Under Range94
Unexpected number of parameters84
Use Gate View Sweep Time in the Gate menu.41
User Cal valid. Apply Cal from Meas Setup menu41
User cal103
User Cal; Adjusted for new RBW105
User Cal; Cal invalidated104
User Cal; Cal will be interpolated105
User Cal; Freq outside cal range105
User request43
Waiting for Arm111
Waiting for Trigger111
Instrument Messages 23
Page 24
Instrument Messages Guide
Overview of Instrument Messaging System
1Overview of Instrument Messaging System
The Error and Status messaging system of the instrument reports events and
conditions in a consistent fashion, as well as logging and reporting event
history.
This chapter contains the following topics:
— “A-Series and B-Series Differences” on page 24
— “Message Types” on page 24
— “Event and Condition Categories” on page 26
— “Error Message Fields” on page 29
— “Event Queues & Displays” on page 30
— “Message Display & Controls” on page 32
A-Series and B-Series Differences
This guide now covers both "A-Series" and "B-Series" instruments:
— A-Series instruments have part numbers ending in A (for example, N9020A)
— B-Series instruments have part numbers ending in B (for example, N9040B)
The set of messages and the underlying messaging system are common to
both A and B-Series. However, the method of displaying messages, and the
controls that you can use to interact with the messaging system, differ
between A and B-Series. Differences are highlighted below where necessary.
Message Types
Messages may be Events or Conditions:
—An Event is simply a message indicating that something has happened.
Events are divided according to their severity, into Error, Warning or
Advisory categories. These are described in more detail in “Event
Categories” on page 27.
24
Page 25
Overview of Instrument Messaging System
Message Types
The method of displaying messages differs between A-Series and B-Series
instruments. For details, see “Message Display & Controls” on page 32.
—A Condition is a state of the instrument, which is characterized by a
Detection (Start) event and a Clearing (End) event.
Conditions are divided into two categories: Warnings and Errors. These are
described in more detail in “Condition Categories” on page 28.
The method of displaying messages differs between A-Series and B-Series
instruments. For details, see “Message Display & Controls” on page 32.
Each Condition’s 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.
All Conditions are mirrored by a bit in the STATus Register Subsystem (see
“Status Register System Overview” on page 115).
Instrument Messages 25
Page 26
Overview of Instrument Messaging System
Event and Condition Categories
Event and Condition Categories
The categories of severity are described below, for both Events and Conditions.
— Event Categories
— Condition Categories
Instrument Messages 26
Page 27
Overview of Instrument Messaging System
Event and Condition Categories
Event Categories
ErrorsAn Event Error occurs when a requested operation is rejected. Generally this means no change is
made to the instrument settings. Examples are “Undefined header” or “Peak not found.” Event
Errors also occur when an operation is accepted, but fails to complete successfully; for example
“Disc full” when attempting to store data.
Error messages are often generated during remote operation when an invalid programming
command has been entered.
In some cases, front panel activity generates an Advisory and not an Error event, even though the
equivalent SCPI activity generates an Error Event. Typically this is when a function is grayed out; a
benign advisory appears on the front panel, because nothing happened, but SCPI must treat it as an
error because something that was requested was not delivered.
Event Errors have an associated number, and are sent to both the front panel queue and the SCPI
queue for the interface that stimulated the Event.
WarningsEvent Warnings advise you 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.
Another example would be the case where you requested too high a stop frequency, which causes
“Data out of range” to be displayed, and the instrument to set itself to the highest available stop
frequency.
Event Warnings have an associated number, and are sent to both the front panel queue and the
SCPI queue for the interface that stimulated the event.
AdvisoriesEvent Advisories simply provide some useful information. (For example, “File saved successfully” or
“Measuring the fundamental”.)
Event Advisories do not have an associated number, and are not reported to SCPI or logged in error
queues.
Grayout messages are a special type of Advisory, which appear when you attempt to access a
function that is not available. This could be a grayed out front panel key, or an inappropriate SCPI
command. There are two types of grayout messages: Benign and Forced.
1. Benign: the requested function is not available because it does not make sense with the
current instrument settings. Changing it does not affect the current measurement. (For
example, setting the number of FFTs/Span when you are not in the FFT mode.)
A benign grayout gives an Advisory type of message only when the front panel key is pressed.
The requested function cannot be changed from the front panel, but it can be changed
remotely.
2. Forced: the requested function is not available either because changing it would cause an
invalid measurement, or because of hardware limitations, or because the selection conflicts
with other settings. (For example, selecting the electrical attenuator when the frequency span
includes frequencies above 3.6 GHz.)
A forced grayout function cannot be changed either from the front panel or remotely. It
generates a special type of Advisory message. It also only appears on the front panel when
the key is pressed. Remotely, the message will appear in the event queue as a warning “-221,
Settings conflict; <conflict description>”.
Instrument Messages 27
Page 28
Overview of Instrument Messaging System
Event and Condition Categories
Condition Categories
ErrorsCondition Errors notify you that the instrument cannot make valid measurements while the
condition is present.
Examples of error conditions are “LO Unlocked” or “Alignment required”.
A Condition Error exists for a period of time, so it has associated “Detected” and “Cleared” events.
(For example, “LO Unlocked” or “External reference out of range”.)
Condition Errors are displayed in the front panel. The Detected and Cleared Events associated with
each Condition Error message are logged in the error queues.
WarningsCondition Warnings appear when a requested operation has completed successfully, but there are
modifications and/or side effects.
For example, if you set the sweep time too fast for a measurement to meet the instrument
specifications then the “Meas Uncal” message is displayed until you slow down the sweep time.
A Warning Condition exists for a period of time, so it has a “Detected” event and a “Cleared” event.
Condition Warnings are displayed in the front panel, but are not sent to SCPI. They may set status
bits in the SCPI Status tree (see “Status Register System & SCPI STATus Subsystem” on page 114).
Instrument Messages 28
Page 29
Overview of Instrument Messaging System
Error Message Fields
Error Message Fields
NOTE The messages defined for Keysight’s instruments extend those specified in
the 1999 SCPI Syntax & Style Standard. As a result, the terminology used
here differs from that used in the Standard, as shown in Table 1-1 below.
Each Error message consists of three fields (Error Number, Error Message and
Error Description), as shown in the table below (Events of this type are listed in
“–221 Settings Conflict Errors” on page 48).
The SCPI query :SYStem:ERRor:NEXT? returns a string containing these three
fields. For more details, see the description of the query in the instrument’s
online help, or any X-Series User’s & Programmer’s Reference.
Additionally, most messages have an associated Verbose/Correction
Explanation, which is provided only in this document and is not displayed in
the instrument or returned via SCPI.
SCPI Standard TermError/event NumberError/event DescriptionDevice-dependent info
Example–221Settings conflictElectronic attenuator is disabled
For the example above, the Verbose/Correction Explanation is:
You are using the mechanical attenuator, and have not enabled the
electronic attenuator. You cannot set the value of the electronic
attenuator because it automatically sets/changes when enabled.
In this document, Event messages are listed in numerical order, according to
their message number, except for Advisory Event messages, which do not have
numbers and are listed in alphabetical order.
Condition messages are listed according to the number of their associated
Start Event.
As specified in Volume 2, Section 21.8 of the 1999 SCPI Syntax & Style
Standard, messages with Error Numbers less than or equal to zero are
predefined. The definitions listed in this document for those messages
correspond to those in the Standard.
Instrument Messages 29
Page 30
Overview of Instrument Messaging System
Event Queues & Displays
Event Queues & Displays
Events are logged into queues. Each source of control has its own queue. Thus
there is a Front Panel queue, a SCPI GPIB queue, a SCPI LAN queue, and so on.
Each remote queue is queried separately via its own interface.
The Front Panel queue may be viewed in two ways, via the Status or History
lists, as described in Table 1-2 below.
Error events generated by one interface may only be queried over that
interface; for example, you cannot query GPIB errors from the LAN queue.
Note that Conditions are logged in the queues as pairs of Events: a Detected
Event and a corresponding Cleared Event.
Table 1-2 Event Queue & Display Types
Front Panel
Status (Current
Conditions)
Front Panel Event
History
Remote
interfaces
A-Series: Messages can be viewed by pressing System, Show Errors, Status.
B-Series: Displayed as a list in the Current Conditions tab of the Status Dialog.
The Status/Current Conditions list shows existing conditions.
When an event is caused by a command sent over a remote interface, the resulting messages are
logged in the queue for that interface. For convenience, such Events are also logged in the Front
Panel queue.
A-Series: Messages can be viewed by pressing System, Show Errors, History.
B-Series: Displayed as a list in the History tab of the Status Dialog.
The History list shows all the events that have occurred since the instrument was turned on, up to a
maximum of 100 messages.
When an error situation is caused by a command sent over a remote interface, the resulting
messages are logged in the queue for that interface. For convenience, they are also logged in the
front panel queue.
When an error event is caused by a command sent over a remote interface, the resulting messages
are output to the queue for that interface. To return an error, you must query the queue for that
interface.
An error event that is caused by a front panel action is not reported to any remote interface queue.
However, a status condition is usually caused by an internal event that is not related to a particular
interface, so the Detected/Cleared Events for status conditions are reported to all the queues.
B-Series: Tap the Message
Indicator balloon in the
Send SCPI query to the desired
interface:
:SYSTem:ERRor?
Status Bar
Clearing the QueueA-Series: Press System,
Show Errors,
Clear Error Queue
B-Series: Select the
History tab of the Status
Dialog, then tap Clear
Message Queue
Clears the messages in all
the queues.
A-Series: Press System,
Show Errors,
Clear Error Queue
B-Series: Select the
History tab of the Status
Dialog, then tap Clear
Message Queue
Clears the messages in all
the queues.
Send *CLS command to the desired
interface.
Clears messages in the queue for this
particular interface only.
Table 1-4 Summary of Event Reporting Modes
Event TypeSCPI Error
Queues
Front Panel
History Queue
Status Panel Display
Error/Warning/Advisory EventLoggedLoggedA-Series: displayed in Message Line
B-Series: displayed via Message Box
Error/Warning Condition: Detected (Start)
Event
Error/Warning Condition: Cleared (End)
Logged
Logged
a
b
Logged
a
A-Series: Displayed in Status Line
B-Series: displayed via Message Box
Event
Grayout Advisory (Benign)Not loggedLoggedA-Series: Displayed in Status Line
B-Series: displayed via Message Box
Grayout Advisory (Forced)
See note
c
LoggedA-Series: Displayed in Status Line
B-Series: displayed via Message Box
a. Logged with the same severity (Error or Warning) as the Condition
b. Logged with a “green” severity (Condition Resolved)
c. Not logged, unless the cause of the Advisory was remotely generated, in which case a Warning mes-
sage, type –221, is logged.
Instrument Messages 31
Page 32
Overview of Instrument Messaging System
Message Display & Controls
Message Display & Controls
A-Series
In A-Series instruments, messages are displayed as follows.
— Event messages appear in the Message Line at the bottom left of the
instrument’s display window, as shown in Figure 1-1 below.
— Condition messages appear in the Status Panel at the bottom right of the
instrument’s display screen, as shown in Figure 1-1 below.
Figure 1-1 Instrument Message Line & Status Panel for A-Series Instruments
B-Series
In B-Series instruments, messages are displayed as follows.
— Event Messages are displayed via popup Event Message Boxes that appear
temporarily in the center of the screen.
— Condition Messages are displayed in the Status Bar at the bottom of the
screen.
Event Message Boxes
A typical Event Message box is shown in Figure 1-2 below. Event Message
boxes appear in the center of the instrument screen when the event occurs,
then fade away.
Instrument Messages 32
Page 33
Overview of Instrument Messaging System
Message Display & Controls
Figure 1-2 Event Message Box for B-Series Instruments
In the Message Box, the icon on the left indicates the appropriate Event
category (see Event Categories): blue for Advisory, yellow for Warning, and red
for Error.
For more details, see the topic User Interface > Control Bar > Status Bar >
Events in the instrument’s online help.
Instrument Messages 33
Page 34
Overview of Instrument Messaging System
Message Display & Controls
Status Bar
The Status Bar appears at the bottom of the display and contains three fields,
as shown in Figure 1-3 below.
Tapping anywhere in the Status Bar displays the Status Dialog.
For full details of the fields in the Status Bar and their operation, see the topic
User Interface > Control Bar > Status Bar in the instrument’s online help.
Figure 1-3 Status Bar for B-Series Instruments
Status Dialog
The Status Dialog has three tabs:
1. History
2. Current Conditions
3. Settings
For full details of the tabs of the Status Dialog and their content, see the topic
User Interface > Control Bar > Status Bar > Status Dialog in the instrument’s
online help.
Instrument Messages 34
Page 35
2Instrument Messages
This chapter includes the following sections:
— “Advisory Messages” on page 36
— “Event Messages” on page 42
— “Condition Messages” on page 87
Instrument Messages Guide
Instrument Messages
35
Page 36
Instrument Messages
Advisory Messages
Advisory Messages
An advisory is simply a message that lets you know something useful—for
example “File saved successfully” or “Measuring fundamental.” Operation
completion and running status indications are common types of Advisories.
Advisories have no number and are not logged in the error queue. They are not
defined in the 1999 SCPI Syntax & Style Standard.
Advisories include gray-out “settings conflict” errors. These gray-outs are
benign (that is, changing them has no impact on the current measurement).
Advisories are Event-type errors only. They are never Conditions.
MessageDescription/Correction Information
All Auto/Man functions have
been set to Auto
All Auto/Man functions have
been set to Auto.
Allowable Center Frequency
exceeded for the current
span
Allowable Span exceeded for
the current center
frequency
Allowable Start Frequency
exceeded for the current
span
Allowable Stop frequency
exceeded for the current
span
Allowable X Ref Level
exceeded for the current
Capture Length
Allowable X Scale/Div
exceeded for the current
Capture Length
Message generated by pressing the Auto Couple front-panel key.
When rotating the knob or step up/down keys to change the Center frequency, the
value of the Span is kept constant. Therefore, the center frequency is limited by the
frequency range of the instrument.
When rotating the knob or step up/down keys to change the Span, the value of the
Center frequency is kept constant. Therefore, the span is limited by the frequency
range of the instrument.
When rotating the knob or step up/down keys to change the Start frequency, the
value of the Span is kept constant. Therefore, the start frequency is limited by the
frequency range of the instrument.
When rotating the knob or step up/down keys to change the Stop frequency, the
value of the Span is kept constant. Therefore, the stop frequency is limited by the
frequency range of the instrument.
The X Ref Level and X Scale/Div is limited by the Capture Length of the
measurement.
The X Ref Level and X Scale/Div is limited by the Capture Length of the
measurement.
Already in Single, press
Restart to initiate a new
sweep or sequence
Auto sweep time rules do
not apply in FFT sweeps
Instrument Messages 36
The instrument is already in the single state. If you want to start a new sweep or
sequence, press the Restart key instead.
FFT sweeps do not use the auto sweep time rules, so the rules setting cannot be
changed from the front panel. The setting can be changed remotely and it will have
no effect on the current operation unless the analyzer is switched out of FFT
sweeps.
Page 37
Instrument Messages
Advisory Messages
MessageDescription/Correction Information
Band Adjust has no effect
on a Fixed marker
Band Adjust has no effect
with Mkr Function Off
Band-pass filter set to OFFTurning on any high-pass or low-pass filter will turn off band pass filters.
Cal Cancelled; Calibration
data cleared
Cal Invalid: meas freq
pt(s) > 3.6GHz are > 50MHz
from existing Cal pts
Carrier power is too low
for optimum dynamic range.
Connecting to source…External Signal Generator is being sent SCPI commands interrogating it to see if it
If a Marker is a Fixed type marker, the marker's value does not change from when it
first became fixed. So you cannot change the band of a fixed marker.
If Marker Function is off changing the band has no effect
User has canceled the cal either directly or indirectly by changing the setup
parameters. The current cal data has been erased. Perform a new user cal to obtain
calibrated results again.
When freq points being measured are above 3.6 GHz and a calibration has been
successfully performed, and the number of points are changed, the new points are
required to be within 50 MHz of the current cal points or the preselector optimize
frequencies become inaccurate and the whole cal needs to be invalidated.
Interpolation of the cal can only be performed if the new freq points are within 50
MHz of the cal points. To overcome this problem, change the number of freq points
back to match cal points or perform another user cal.
For better dynamic range, transmit band spur measurements require >10 dBm
signal power at the RF input port.
is suitable for the MXA to control. Please wait until complete before pressing any
buttons.
Demod Time is not available
in Zero Span
Detector <X> changed due to
physical constraints
Dynamic range is not
optimum. Set AUTO RF input.
Exp. Averaging not
available when AUTO PhNoise
is active.
FFT Width is not settable
unless Sweep Type is set to
FFT
File <filename> savedThe file save operation executed successfully.
Filter BW function is only
available for Gaussian
filter type
The Demod Time function is not available in zero span because in zero span we are
ALWAYS demodulating.
You have selected more detectors than the instrument hardware can implement.
An existing detector selection has been changed to allow the current detector
choice to be selected.
<X> indicates the trace number for which the detector was changed.
You must select the FFT sweep type before you can set the FFT Width
Flattop and CISPR/MIL filters have defined shapes that cannot be altered. So only
the Gaussian filter type allows filter bandwidth definition changes.
Instrument Messages 37
Page 38
Instrument Messages
Advisory Messages
MessageDescription/Correction Information
Fixed LO freq should be
greater than RF Stop freq
Freq Scale Type=Log is not
available in Zero Span
Frequency Hopping enabled,
waiting for valid burst
Frequency menu has changed
to reflect frequency
context switch
Gate required for valid
results
High-pass and Low-pass
filters set to OFF
High-pass filter set to OFFTurning on any band pass filter will turn off high-pass filters.
IF Fixed freq should be
greater than LO Stop freq
The setup frequencies break the rules for a downconverter measurement. The
measurement will still run, but check setup frequencies are correct before
continuing. The LO fixed freq should be greater than the RF freq’s for an LSB or
DSB (for DSB measurements the setup uses LSB values) downconverter setup. Use
the graph icon on the DUT setup form to clarify the setup required.
Logarithmic scaling cannot be used for time domain sweeps (0 Hz span).
The demodulated burst type has not been found in the originally demodulated slot
location within the frame.
The frequency context parameter has been changed either by the user or the
system. The frequency menu will now contain the frequencies for the new context.
No action required.
Turning on any band pass filter will turn off high-pass and low-pass filters.
The setup frequencies break the rules for an upconverter measurement. The
measurement will still run, but check setup frequencies are correct before
continuing. The IF fixed freq should be greater than the LO Stop freq for a USB
upconverter swept LO setup. Use the graph icon on the DUT setup form to clarify
the setup required.
IF Fixed freq should be
greater than RF Stop freq
IF Start freq should be
greater than LO Fixed freq
IF Start freq should be
greater than RF Start freq
Input is internalThe instrument’s input is set to internal (the internal amplitude reference signal). So
The setup frequencies break the rules for an upconverter measurement. The
measurement will still run, but check setup frequencies are correct before
continuing. The IF fixed freq should be greater than the RF Stop freq for an
upconverter swept LO setup. Use the graph icon on the DUT setup form to clarify
the setup required.
The setup frequencies break the rules for an upconverter measurement. The
measurement will still run, but check setup frequencies are correct before
continuing. The IF start freq should be greater than the LO fixed freq for an USB
upconverter fixed LO setup. Use the graph icon on the DUT setup form to clarify the
setup required.
The setup frequencies break the rules for an upconverter measurement. The
measurement will still run, but check setup frequencies are correct before
continuing. The IF start freq should be greater than the RF Start freq for an
upconverter fixed LO setup. Use the graph icon on the DUT setup form to clarify the
setup required.
any signals connected to the front/rear panel inputs cannot be measured.
Instrument Messages 38
Page 39
Instrument Messages
Advisory Messages
MessageDescription/Correction Information
LO Fixed freq should be
greater than IF Stop freq
LO Fixed freq should be
greater than RF Stop freq
LO Start freq should be
greater than IF Fixed freq
LO Start freq should be
greater than RF Start freq
LO Stop freq should be
greater than RF Stop freq
The setup frequencies break the rules for an upconverter measurement. The
measurement will still run, but check setup frequencies are correct before
continuing. The LO fixed freq should be greater than the IF Stop freq for an LSB
upconverter fixed LO setup. Use the graph icon on the DUT setup form to clarify the
setup required.
The setup frequencies break the rules for a downconverter measurement. The
measurement will still run, but check setup frequencies are correct before
continuing. The LO fixed freq should be greater than the RF Stop freq’s for an LSB
or DSB (for DSB measurements the setup uses LSB values) downconverter fixed LO
setup. Use the graph icon on the DUT setup form to clarify the setup required.
The setup frequencies break the rules for an upconverter measurement. The
measurement will still run, but check setup frequencies are correct before
continuing. The LO Start freq should be greater than the IF fixed freq for an LSB
upconverter swept LO setup. Use the graph icon on the DUT setup form to clarify
the setup required.
The setup frequencies break the rules for a downconverter measurement. The
measurement will still run, but check setup frequencies are correct before
continuing. The LO start freq should be greater than the RF Start freq’s for an LSB
downconverter swept LO setup. Use the graph icon on the DUT setup form to
clarify the setup required.
The setup frequencies break the rules for a downconverter measurement. The
measurement will still run, but check setup frequencies are correct before
continuing. The LO Stop freq should be greater than the RF Stop freq’s for a DSB
(for DSB measurements the setup uses LSB values) downconverter swept LO
setup. Use the graph icon on the DUT setup form to clarify the setup required.
Low-pass filter set to OFFTurning on any band pass filter will turn off low-pass filters.
No spurs have been foundYou has started a measurement in examine meas type in single or continual sweep
mode, or full meas type in single sweep mode, but no spurs were found.
Power meter or sensor is
connected
Preparing Calculation…
Preselector is centeredThe preselector has been successfully centered
Preselector not used in
this frequency range.
Probe connected, cal data
is being reapplied; <port>;
<probe>
Probe connected, no probe
cal; using cable cal data;
<port>; <probe>
A power meter or sensor at the given address is connected.
You cannot center or adjust the preselector because it is not used at all at the
current marker frequency or between the current start and stop frequencies
A probe has been connected, calibration data is being reapplied
A probe has been connected and no probe calibration data is available. The latest
cable calibration data will be used
Instrument Messages 39
Page 40
Instrument Messages
Advisory Messages
MessageDescription/Correction Information
Probe disconnected,
reverting to cable
calibration data; <port>
Reading SNS data…The Keysight Smart Noise Source has been connected and the application is
Recalled File <filename>A file recall (open/load) was successfully completed.
Refer to online help for
assistance with DSB
measurements
Requested timeslot number
is not present.
Res BW changedIn instruments with Option B5X, Span was set to > 255 MHz while Res BW was
RF Start freq should be
greater than IF Fixed freq
RF Start freq should be
greater than IF start freq
A probe has been disconnected, calibration data reverting to the last cable
calibration data
reading the device EEPROM data. Please wait until complete before continuing.
The Double Side Band measurement requires careful setup to obtain valid results.
Please refer to the manuals for help with this setup.
The selected timeslot is not on. (Timeslot is referenced to the trigger point.)
greater than Res BW 4.
The setup frequencies break the rules for a downconverter measurement. The
measurement will still run, but check setup frequencies are correct before
continuing. The RF Start freq should be greater than the IF Fixed freq for a DSB (for
DSB measurements the setup uses LSB values) downconverter swept LO setup.
Use the graph icon on the DUT setup form to clarify the setup required.
The setup frequencies break the rules for a downconverter measurement. The
measurement will still run, but check setup frequencies are correct before
continuing. The RF start freq should be greater than the IF Start freq’s for an LSB
downconverter fixed LO setup. Use the graph icon on the DUT setup form to clarify
the setup required.
RF Start freq should be
greater than LO fixed freq
RF Start freq should be
greater than LO Start freq
RF Stop freq should be
greater than IF Stop freq
Scale/Div only applies in
Log Y Scale
Signal Track is turned off
when Zero Span is selected
The setup frequencies break the rules for a downconverter measurement. The
measurement will still run, but check setup frequencies are correct before
continuing. The RF start freq should be greater than the LO fixed freq’s for an USB
downconverter fixed LO setup. Use the graph icon on the DUT setup form to clarify
the setup required.
The setup frequencies break the rules for a downconverter measurement. The
measurement will still run, but check setup frequencies are correct before
continuing. The RF start freq should be greater than the LO Start freq’s for an USB
downconverter swept LO setup. Use the graph icon on the DUT setup form to
clarify the setup required.
The setup frequencies break the rules for a downconverter measurement. The
measurement will still run, but check setup frequencies are correct before
continuing. The RF Stop freq should be greater than the IF Stop freq’s for an USB or
DSB (for DSB measurements the setup uses LSB values) downconverter fixed LO
setup. Use the graph icon on the DUT setup form to clarify the setup required.
Setting the Scale/Division only makes sense when you are using a logarithmic Y
scale.
Signal Track is not available when you have selected Zero Span. So if Zero Span is
entered while in Signal Track is On, Signal Track is turned off.
Instrument Messages 40
Page 41
Instrument Messages
Advisory Messages
MessageDescription/Correction Information
Signals deletedThe signals in the signal list were successfully deleted.
Sweep Points/Span is <
minimum. Results may be
inaccurate.
Sweep Setup is not
available in Zero Span
Sync is RF Ampl (not
Training Sequence). Bits
are not accurate.
Trace file saved.The trace saving operation was successful.
Use Gate View Sweep Time in
the Gate menu.
User Cal valid. Apply Cal
from Meas Setup menu
The sweep point to span ratio is below the minimum required to ensure the bucket
ratio is large enough to test DVB-T masks
Zero span is a display at a single frequency, so there is no “sweeping” to set up.
When in Gate View you use Gate View Sweep Time, rather than Sweep Time, to
control the Gate View window
The measurement setup has changed such that the current cal data can be applied
to the results. To apply the cal, press Meas Setup/Cal Setup/Apply Calibration. A
new cal can be performed if required.
Instrument Messages 41
Page 42
Instrument Messages
Event Messages
Event Messages
Event messages and message numbers are defined by the 1999 SCPI Syntax &
Style Standard. All message numbers are less than or equal to zero.
The SCPI Standard refers to all these messages as "Error/event Messages".
Most X-Series Event Messages fall into the Error Category (see “Event
Categories” on page 27), but a small number are Warnings, as noted for the
relevant entries below.
Device-dependent sub-messages are often appended, to provide additional
information. For example, error –221 is defined as Settings Conflict, but you
will often see a longer description appended to error –221, such as Settings
Conflict; Function not available in Zero Span. This provides more
information about why there is a Settings Conflict error.
The tables in this section are divided by Error Number range, as follows:
— “–800, Operation Complete Event” on page 43
— “–700, Request Control Event” on page 43
— “–600, User Request Event ” on page 43
— “–500, Power on Event ” on page 43
— “–400 to –499, Query Errors” on page 43
— “–300 to –399, Device-Specific Errors” on page 45
— “–221 Settings Conflict Errors” on page 48
— “–200 to –299, Execution Errors” on page 67
— “–100 to –199, Command Errors” on page 84
— “0 No Error” on page 86
Instrument Messages 42
Page 43
Instrument Messages
Event Messages
–800, Operation Complete Event
Err#MessageVerbose/Correction Information
–800Operation completeThe instrument has completed all selected pending operations in
accordance with the IEEE 488.2, 12.5.2 synchronization protocol.
–800Operation complete;
Loaded <ARB filename>
successfully, but no
license <required
licenses> installed
This is a Warning, and is GUI only, that is, this warning cannot queried
by SCPI. It indicates that the ARB is successfully loaded into ARB
memory, but requires licenses that are not present on the instrument.
Install the required license(s) according to <required license> string to
license it or multi-pack license it.
–700, Request Control Event
Err#MessageVerbose/Correction Information
–700Request controlThe instrument requested to become the active IEEE 488.1
controller-in-charge.
–600, User Request Event
Err#MessageVerbose/Correction Information
–600User requestThe instrument has detected the activation of a user request local
control.
–500, Power on Event
Err#MessageVerbose/Correction Information
–500Power onThe instrument has detected an off to on transition in its power supply.
–400 to –499, Query Errors
Err#MessageVerbose/Correction Information
–400Query ErrorThere was a problem with a query command. The exact problem cannot
be specifically identified.
–410Query INTERRUPTEDSome condition caused an INTERRUPTED query to occur. For example, a
query was followed by DAB or GET before a response was completely
sent.
–420Query UNTERMINATEDSome condition caused an UNTERMINATED query to occur. For example,
the device was addressed to talk and an incomplete program message
was received.
Instrument Messages 43
Page 44
Instrument Messages
Event Messages
Err#MessageVerbose/Correction Information
–430Query DEADLOCKEDSome condition caused a DEADLOCKED query to occur. For example,
both the input buffer and the output buffer are full and the analyzer
cannot continue. The analyzer automatically discards output to correct
the deadlock.
–440Query UNTERMINATED
after indefinite
response
A query was received in the same program message after a query
requesting an indefinite response was executed.
Instrument Messages 44
Page 45
Instrument Messages
Event Messages
–300 to –399, Device-Specific Errors
Err#MessageVerbose/Correction Information
-300Device-specific errorAn instrument error occurred and the exact problem cannot be
specifically identified. Report this error to the nearest Keysight
Technologies sales or service office.
-310System error;An internal system-type error has occurred. The exact problem cannot
be specifically identified. Report this error to the nearest Keysight
Technologies sales or service office.
-310System error;
<feature> expired,
please reboot within
<time>
-310System error;
<feature> expired,
rebooting in <time>
-310System Error;
<filename> not
recalled
-310System error; A
license will soon
expire;<feature code>
will expire in <time>
-310System Error; enable
GPIB controller mode
-310System error; feature
<feature code> not
licensed
-310System error; Feature
expired; <feature
code>
The trial license for the specified feature, for example “N9030T-RT1, has
expired. You must finish any measurements in process and reboot the
instrument within the time specified.
The trial license for the specified feature, for example “N9030T-RT1, has
expired. The instrument will automatically reboot at the time specified;
you should save your measurement results immediately.
The auto recall of cal factor .xml file has failed. You should load the cal
factor manually from the recall dialog.
The indicated feature/software will expire in the specified time. Contact
Keysight Technologies to purchase continued use of this functionality.
Press System, I/O Config, GPIB and set GPIB Controller to Enabled so
that the analyzer can control the source over GPIB
The specified feature, for example “N9073A-TR2” is not licensed. The
license may have expired. You cannot use it until you get a license.
The specified feature has expired. The license is no longer valid.
-310System error; License
installation
failed;<feature code>
-310System error; License
removal failed;
<feature code>
-310System error; No
license; <feature
code> will terminate
in <time>
Instrument Messages 45
The license installation of the specified feature, for example
"N9073A-TR2", has failed. You should refer to the event log in the
control panel for more details.
The license removal of the specified feature, for example “N9073A-TR2”
has failed. You should refer to the event log in the control panel for more
details.
The specified feature will stop working in the specified time due to the
license expiration You will be prompted to save results and exit.
Page 46
Instrument Messages
Event Messages
Err#MessageVerbose/Correction Information
-310System Error; No
power meter or sensor
is selected
-310System Error; No
supported source
found
-310System Error; Power
meter or sensor
calibrate failure
-310System Error; Power
meter or sensor
calibration required
-310System Error; Power
meter or sensor not
responding or
connection timeout.
Please check your
power meter
connection and try
again.
-310System Error; Power
meter or sensor zero
and calibration
required
You must select a power meter or sensor before you can do this.
Signal source at given IP address is not responding / IP does not belong
to a source. Check IP address and network connection.
The power meter or sensor calibration failed. Make sure you connect the
power sensor to the reference output of power meter and re-perform
the operation.
The power meter or sensor needs calibration. Please perform power
meter calibration.
Power meter or sensor at the given address is not responding within the
timeout duration or it is not one of the supported power meter models.
Check power meter model, address and timeout.
The power meter or sensor needs zero and calibration. Please perform
power meter zero and calibration.
-310System Error; Power
meter or sensor zero
failure
-310System Error; Power
meter or sensor zero
required
-310System Error; source
connection lost,
check interface
connection
-311Memory errorThere is a physical problem with the instrument memory, such as a
-312PUD memory lostProtected user data saved by the *PUD command has been lost.
-313Calibration memory
lost
-314Save/recall memory
lost
The power meter or sensor zero failed. Make sure you disconnect the
power sensor from any source of power and re-perform the operation.
The power meter or sensor needs zeroing. Please perform power meter
zero.
Signal source at given IP address is not responding / IP does not belong
to a source. Check IP address and network connection.
parity error.
The nonvolatile calibration data used by the *CAL? command has been
lost.
The nonvolatile data saved by the *SAV? command has been lost.
Instrument Messages 46
Page 47
Instrument Messages
Event Messages
Err#MessageVerbose/Correction Information
-315Configuration memory
lost
-320Storage fault;A problem was found while using data storage. The error is not an
-321Out of memoryAn internal operation needed more memory than was available. Report
-321Out of memory;
Results truncated
-321Out of memory;
Sequence too long
-321Out of memory; Total
analysis step reaches
its limitation
-340Calibration failed;
<failure msg><port>
-350Queue overflowAn error occurred that did not get put in the error queue because the
-360Communication errorThere was a problem with instrument remote communications. The
The nonvolatile configuration data saved by the instrument has been
lost.
indication of physical damage or failure of any mass storage element.
this error to the nearest Keysight Technologies sales or service office.
Reduce the acquisition count, analysis step count, or measurement
count.
The Sequence is too large to be captured. Reduce the Number of
Acquisitions or the Acquisition Duration of each Acquisition.
Reduce the analysis steps count.
The calibration for one of the I-Q ports did not succeed. The information
in the “failure msg” field can be used to troubleshoot this problem.
Contact Keysight technical support.
queue was full.
exact problem cannot be specifically identified.
-360Communication error;
SNS data read
failure. Disconnect
then reconnect SNS
-360Communication error;
SNS is not connected
-361Parity error in
program message
-362Framing error in
program message
-363Input buffer overrunA software or hardware input buffer on a port overflowed with data
-365Time out errorThere was a time-out problem in the instrument. The exact problem
The Keysight Smart Noise Source connected to the MXA has failed to be
read by the application. Please disconnect and reconnect the SNS. If
this continues to fail, then the SNS may have had its EEPROM corrupted
or another hardware fault exists. Check SNS on another instrument, NFA
and ESA are also SNS compatible instruments. Check the device is not
an Keysight power sensor which uses the same cable interface.
The Keysight Smart Noise Source connected to the MXA has failed to be
read by the application. Please disconnect and reconnect the SNS. If
this continues to fail, then the SNS may have had its EEPROM corrupted
or another hardware fault exists. Check SNS on another instrument, NFA
and ESA are also SNS compatible instruments. Check the device is not
an Keysight power sensor which uses the same cable interface.
A parity bit was not correct when the data was received. For example, on
a parallel port.
A stop bit was not detected when data was received. For example, on a
remote bus port.
because of improper or nonexistent pacing.
cannot be specifically identified.
Instrument Messages 47
Page 48
Instrument Messages
Event Messages
Err#MessageVerbose/Correction Information
-365Time out error;
Operation on source
is held. If analyzer
is waiting for
trigger, change to
free run to proceed
This is a warning message.
This warning can only occur when issuing SCPI to operate the source
while the analyzer is waiting for a trigger. When the analyzer is waiting
for a trigger, source operation is set to pending. (Trigger Source
operation is an exception)
To avoid this, do not operate the source when the analyzer is waiting for
a trigger. If source and analyzer both are utilized, configure the source
parameters ready and run before analyzer waits for trigger.
If both the analyzer and source are waiting for a trigger, the only
operations allowed on the source are trigger source operations, like
external, manual, or bus trigger.
–221 Settings Conflict Errors
This is one of the messages in the standard SCPI range from “–200 to –299,
Execution Errors” on page 67.
Err#MessageVerbose/Correction Information
-221De-emphasis only
available in FM
-221Function not available in
Zero Span
The de-emphasis function is only available if FM demod is
selected.
The function you are trying to access is not available in zero span.
-221Settings conflict:
Timebase DAC not
available with Pulse
selected
-221Settings conflict;A legal command was received but it could not be executed due
-221Settings conflict; *.CSV
file format is not
available in this
measurement.
-221Settings conflict; <Q
Param> cannot be changed
when Q same as I
-221Settings conflict;
<trigger source> trigger
is not available in
current IF Path
The manual adjustment of the Timebase DAC cannot be
performed when the currently selected timebase is Pulse.
to the current device state.
You cannot load or save base instrument traces, as this is not
supported by the Log Plot measurement.
When the “Q Same as I” parameter is set to Yes, the I parameter
value is copied to <Q Param> and the <Q Param> value cannot be
changed. Set Q Same as I to No to enable explicit control of the
<Q Param> value.
The trigger source (Video, RF Burst, I/Q Mag, etc.) is not available
when using the current IF Path, for example FMT is not available
in the 1 GHz IF Path
Instrument Messages 48
Page 49
Instrument Messages
Event Messages
Err#MessageVerbose/Correction Information
-221Settings conflict;
<trigger source> trigger
is not available while
input is <input port>
-221Settings conflict; A
Valid User Cal is
required. Optimize
aborted
-221Settings conflict;
Acquisition # Analysis
Step # not exist
-221Settings conflict;
Acquisition # not exist.
-221Settings conflict;
Acquisition duration time
too short, Acq=#
-221Settings conflict;
Analysis Interval should
be less than ** ms, Acq=#
Step=#
The trigger source (Video, RF Burst, I/Q Mag, etc.) is not available
with the current input port (RF, IQ, etc.)
Optimize Preselector can only be performed if a valid user cal
exists and is applied to current results. Perform a user cal first or
apply existing cal.
The configured Analysis Step does not exist.
Add the specified analysis step into the sequence.
The configured acquisition does not exist.
Add the specified acquisition into this sequence.
Acquisition duration cannot be less than < (analysis offset +
analysis interval).
Increase the acquisition duration time or decrease the analysis
offset and analysis interval.
The analysis interval is too large for basic transmit power
measurement.
Decrease the analysis interval.
-221Settings conflict;
Analysis Offset should be
greater than # us, Acq=#
Step=#
-221Settings conflict; At
least one Phase must be
turned on
-221Settings conflict; At
least one Protective
Earth must be turned on
-221Settings conflict; Auto
Carrier Frequency is only
available when Modulation
Mode is FM or PM
-221Settings conflict; Auto
Set RF Level failed, Too
much dynamic range is
requested
-221Settings conflict; Auto
Tune not available in
Tracking Source mode
The Analysis Offset should be greater than # µs due to physics
requirement.
Increase the time of Analysis Offset.
At least one Protective Earth must be turned on
You are not allowed to change the Auto Carrier Frequency
settings in AM Modulation Mode.
The sequence requests too much dynamic range, auto range
cannot be preformed correctly.
Change the Peak Power or DUT Expected Power.
The Auto Tune feature cannot be used when you are using a
Tracking Source.
Instrument Messages 49
Page 50
Instrument Messages
Event Messages
Err#MessageVerbose/Correction Information
-221Settings conflict;
Averaged acquisition
duration time exceeds
maximum value, Acq=#
-221Settings conflict; Basic
Discrete PAvT measurement
cannot be averaged, Acq=#
Step=#
-221Settings conflict; Basic
IQ data measurement
cannot be averaged, Acq=#
Step=#
-221Settings conflict; BTS
gain is not available in
this Mode
-221Settings conflict; Cal
only available when
Source Mode is Tracking
-221Settings conflict;
Calibrate TRFL is only
available in Manual Range
Switching when Recal is
needed
Total acquisition duration time after averaging (average count *
acquisition duration) exceeds maximum value.
Reduce the average count or decrease the acquisition duration
time.
The average count of acquisition which contains basic Discrete
PAvT measurement cannot be greater than 1.
Set the average count of current acquisition to 1. Or remove the
Basic Discrete PAvT measurement from this analysis step.
The average count of acquisition which contains basic IQ data
measurement cannot be greater than 1.
Set the average count of current acquisition to 1. Or remove the
Basic IQ data measurement from this analysis step.
Base Transceiver Station gain correction is not available in some
Modes, or in some measurements (for example, the SA
measurement).
You must be in Tracking Source mode to use the Cal functions
under Normalize. Press Source, Source Mode and set it to
Tracking.
You can only perform this operation when in Manual Range
Switching mode and input power fall in the recal range.
-221Settings conflict;
Calibration cannot be
performed without valid
ENR data
-221Settings conflict;
Cancellation is not
available while measuring
DANL floor.
-221Settings conflict;
Cancellation Ref trace
has no data.
-221Settings conflict;
Cancellation trace has
different X-Scale
The cal ENR table has no values in it, and hence the cal cannot be
performed. Correct by either populating the cal ENR table, set
ENR mode to Spot, or set the ‘Use Meas Table Data for Cal’ to
‘On’.
Phase Noise cancellation does not make sense when measuring
the DANL Floor, so for this reason it has been disabled
When performing phase noise cancellation, you need to supply a
reference trace that will be used to cancel out the background
noise of the analyzer. The reference trace must be in Reference
(View) mode, and selected by the Ref Trace parameter under the
Cancellation menu
Reference trace for the cancellation has a different range of
X-axis against the target trace
Instrument Messages 50
Page 51
Instrument Messages
Event Messages
Err#MessageVerbose/Correction Information
-221Settings conflict; Cannot
delete current step,
minimum number of steps
reached
-221Settings conflict; Cannot
insert more steps,
maximum number of steps
reached
-221Settings conflict; Cannot
optimize while user cal in
progress
-221Settings conflict; Can't
Auto-Couple Res BW in Zero
Span
-221Settings conflict;
Carrier freq not allowed
with BMT.
(Bottom/Middle/Top only)
-221Settings conflict; Code
channel duplication
-221Settings conflict; Cont
Mode is not available
An attempt was made to delete the current step which is already
the only step in the list sequence.
An attempt was made to insert more steps into list sequence
which already contains the maximum of 1000 steps.
Optimize Preselector cannot be performed while a user cal is in
progress. The user cal performs an optimize preselector prior to
taking the noise source on/off level results for the cal data.
The resolution bandwidth cannot be set to auto while you are in
zero span (time domain).
The transmit band spur measurement only allows bottom (B),
middle (M), and top (T) channel frequencies for each supported
frequency band. The carrier frequency must be set to the bottom,
middle or top frequency of the current frequency band.
This error is reported when the given code channel overlaps other
code channel
Current measurement does not support Continuous Sweep, only
Single Sweep is available
-221Settings conflict;
Continuous Peak is not
available with Fixed
marker
-221Settings conflict;
Continuous Peak is not
available with Signal
Track on
-221Settings conflict;
Correction file not
specified
-221Settings conflict;
Correction not available
with Corr Group on
-221Settings conflict;
Current setting is not
available while input is
RF/Audio
The continuous peak feature cannot be used with a marker that is
fixed. By definition that marker value cannot change.
The continuous peak feature cannot be used while you are also
using the signal tracking function.
Correction file has not been specified. There is no file to be
removed.
Correction is not available with Correction Group turned on.
This control is specific to measurement that is not currently used.
You can only perform this operation when the measurement is
selected.
Instrument Messages 51
Page 52
Instrument Messages
Event Messages
Err#MessageVerbose/Correction Information
-221Settings conflict;
dB*/MHz is not applicable
to the following Y-Axis
units, dBm, W, V, A
-221Settings conflict;
De-emphasis is only
available when Modulation
Mode is FM
-221Settings conflict;
Destination trace for
Trace Math cannot be a
trace operand
-221Settings conflict;
Differential setting
determined by probe type
-221Settings conflict;
Display unit control not
available when in
Relative measurement
-221Settings conflict;
Downconv only available
when DUT is Amplifier
You cannot turn on dB*/MHz for Y-Axis units: dBm, W, V, A. It is
not applicable to these units.
You are not allowed to change the De-emphasis value in AM and
PM Modulation Mode.
The resulting trace data (from doing a trace math function) cannot
be put into the any of the traces that are being used by the math
operation.
A probe is connected that has a built in Differential setting. The
setting cannot be changed manually.
You are not allowed to change the display settings. The result is
currently displayed in relative value, which reference to the power
level when Set Ref action. To change the display settings, switch
the Measurement Mode to Absolute.
SCPI only message. The System Downconverter can only be set to
‘On’ when the DUT type is amplifier. Change DUT type to Amplifier
if the System Downconverter is required.
-221Settings conflict; DUT
Expected Power cannot be
greater than Peak Power,
Acq=# Step=#
-221Settings conflict; EDGE
EVM only supports EDGE TCH
burst type.
-221Settings conflict;
Electronic attenuator is
disabled
-221Settings conflict;
Electronic attenuator is
not available above
3.6 GHz
-221Settings conflict;
Electronic attenuator
unavailable in current
state
Changing Peak Power will cause DUT Expected Power to be
clipped.
You are using the mechanical attenuator, and have not enabled
the electronic attenuator. You cannot set the value of the
electronic attenuator because it automatically sets/changes when
enabled.
The maximum frequency of the electronic attenuator is 3.6 GHz.
This is because of switching capacitance.
Instrument Messages 52
Page 53
Instrument Messages
Event Messages
Err#MessageVerbose/Correction Information
-221Settings conflict;
Electronic attenuator
unavailable with Preamp
on
-221Settings conflict; EMI
Avg and Voltage Avg cannot
be selected
simultaneously
-221Settings conflict; EMI
Avg/RMS Avg and Average
detector can’t be used
together
The internal preamp is on. Electronic attenuator cannot be used
while you are using the internal preamp.
You cannot turn on both EMI Avg and Voltage Avg detectors
concurrently. If the EMI Average detector is selected, then
Voltage Average detector cannot be turned on.
User is not allowed to turn on EMI Avg/RMS Avg and Average
detector together. They are always mutually exclusive.
QPD, EMI Average, EMI Peak, and MIL Peak are not allowed when
in the manually selected FFT sweep mode.
Turning one modulation format (like AM, PM, FM or ARB) on when
another modulation format is already on results in the previous
modulation format being turned off and the generation of an
error.
-221Settings conflict;
External Mixer not
available
-221Settings conflict; FAST
method can only be used
while Radio Std is W-CDMA
-221Settings conflict;
Feature not available for
Option <abc>
-221Settings conflict;
Feature not available in
this View
-221Settings conflict;
Feature not supported for
selected source
-221Settings conflict;
Feature not supported for
this Input.
A command has been sent to reference the External Mixer in a
model that does not contain it
This functionality is not part of the instrument configured with the
indicated option
Some functionality is available in one View, but not in another.
(See the Views under the View/Display key.) This error occurs if
you send a SCPI command or push a gray-out key that is not
available in the current selected View.
You have asked for a feature that the selected source is not
capable of.
Some functionality is not available when certain Inputs are
selected. For example, Trigger Holdoff is not available for the
BBIQ input
Instrument Messages 53
Page 54
Instrument Messages
Event Messages
Err#MessageVerbose/Correction Information
-221Settings conflict;
Feature not supported for
this measurement.
-221Settings conflict;
Feature not supported for
this model number
-221Settings conflict; FFT IF
Gain High not available
when Swept IF Gain =
Manual Low
-221Settings conflict; FFT is
not available when Signal
ID is on
-221Settings conflict; FFT is
not available when Signal
ID is on
-221Settings conflict; FFT is
not available with EMI
detector
-221Settings conflict; FFT
method is unavailable for
level gating
Some functionality is available in one measurement, but not in
another. (See the measurements under the Meas key.) This error
occurs if you send a SCPI command or push a gray-out key that is
not available in the current selected measurement.
This functionality is not a part of the instrument you are using but
may be found in other models in the X-Series.
When Swept IF Gain is manually set to Low, you cannot set the
FFT IF Gain to High because that would make the Reference Level
couplings wrong in FFT mode.
When in external mixing, if you have signal identification on, then
FFT sweep type cannot be selected.
When in external mixing, if you have signal identification on, then
FFT sweep type cannot be selected.
FFT sweep type cannot be selected when the EMI detector is
being used for a trace.
If you are using level gating, you cannot select the FFT Gate
Method.
-221Settings conflict; FFT
sweep type is not
available while in Gated
LO
-221Settings conflict; FFT
sweep type is not
available while in Gated
Video
-221Settings conflict; FFT
Sweeps unavailable in
Tracking Source mode
-221Settings conflict; Fixed
marker adjust not
available while Marker
Function is on
-221Settings conflict; Fixed
Marker Y value is not
adjustable with Normalize
On
The gated LO function turns the LO on and off as it sweeps. So the
FFT sweep type is not available if you have selected gated LO.
The FFT sweep type is not available if you have selected the gated
video function.
Since FFT’s do not sweep, you cannot use a Tracking Source
while doing FFT’s
If a Marker Function is on for a Fixed marker, the marker's
reported value is derived from the function. Therefore, you cannot
directly set the X or Y value of a Fixed marker that has a marker
function turned on.
If Normalize is on the Amplitude scale is in dB units, so adjusting
the Y value of a Fixed marker is not possible.
Instrument Messages 54
Page 55
Instrument Messages
Event Messages
Err#MessageVerbose/Correction Information
-221Settings conflict; Freq >
3.6 GHz unavailable while
electronic attenuator
enabled
-221Settings conflict;
frequency is outside
available range
-221Settings conflict;
Function not available in
Correction Trace Display.
-221Settings conflict;
Function not available in
External Mixing
-221Settings conflict;
Function not available in
Tracking Source mode
-221Settings conflict;
Function not available
while running multirange
scan
-221Settings conflict;
Function not available
with current LISN Type
The electronic attenuator does not function above 3.6 GHz. So if
you have that attenuator enabled, you cannot change the center
frequency so that frequencies above 3.6 GHz are
displayed/measured.
The desired frequency is not a valid setting.
The correction trace for the selected range is turned on. There is
no range to setup, If you want to edit the range, turn off
correction trace display.
The frequency offset feature cannot be used when you have
selected a log scale for the frequency axis.
The feature cannot be used when you are using a Tracking
Source.
Settings change is not allowed while multirange scan is running.
You must stop the current measurement if you wish to change the
settings.
Not all functionality is available for all LISN types
-221Settings conflict;
Function not available
with time domain scan
type.
-221Settings conflict;
Function only available
in Tracking Source mode
-221Settings conflict;
Function unavailable with
MW Presel off
-221Settings conflict;
Function unavailable with
this EMC Standard
-221Settings conflict; Gate
control is Edge for Gated
FFT
-221Settings conflict; Gate
control must be Edge for
this Gate Source
Scan Time and Points not supported in TDS
The feature cannot be used unless you are using a Tracking
Source.
You cannot center or adjust the preselector because the
Microwave Preselector is currently off
Filter BW is auto-coupled when EMC Standard is set to CISPR or
MIL. You must set the EMC standard to None if you are to change
the Filter BW.
You cannot use level triggering to control the gate if you are using
the FFT gating method.
You cannot use level triggering to control the gate when you are
using the currently selected gate source.
Instrument Messages 55
Page 56
Instrument Messages
Event Messages
Err#MessageVerbose/Correction Information
-221Settings conflict; Gate
is not available when
Marker Count on
-221Settings conflict; Gate
Length is not settable in
FFT sweeps
-221Settings conflict; Gate
Length is not settable in
FFT sweeps
-221Settings conflict; Gate
Method is not compatible
with current Sweep Type
setting
-221Settings conflict; Gate
not available with
external Tracking Source
-221Settings conflict; Gate
not available with
Tracking Generator
-221Settings conflict; Gated
FFT is not available while
Sweep Type is set to Swept
The gate function cannot be used while you have marker count
turned on.
The sweep time for FFT sweeps is set by the calculations. So
sweep time settings cannot be adjusted.
The sweep time for FFT sweeps is set by the calculations. So
sweep time settings cannot be adjusted.
If the Gate is On and you have the FFT Sweep Type manually
selected, then the Gate Method cannot be selected.
The Gate functions are unavailable when Source Mode is Tracking
with an external source. This is because the Gate circuitry is used
to sync the external source.
If the Source Type is Tracking Generator, the Gate circuitry is
used for TG sync and is not available for gating
The gated FFT function is not available if you have selected the
swept type of sweep. You must be in the FFT sweep type.
-221Settings conflict; Gated
LO is not available while
Sweep Type is set to FFT
-221Settings conflict; Gated
Video is not available
while Sweep Type is set to
FFT
-221Settings conflict;
Incorrect RBW for demod.
Change RBW
-221Settings conflict; Ind
I/Q is not available for
this measurement
-221Settings conflict; Input
Port is not available
while occupied by Output
The FFT sweep type moves the LO frequency in steps. So the
gated LO function is not available if you have selected FFT sweep.
The gated video function is not available if you have selected the
FFT sweep type.
The Independent I and Q setting is not available for the current
measurement. Only some measurements (initially, only VXA)
support this setting.
The desired destination for the Input Port is already occupied by
the Output Port. First set the Output to a different port or None.
Note the Output must be OFF before it can be changed to a
different port.
Instrument Messages 56
Page 57
Instrument Messages
Event Messages
Err#MessageVerbose/Correction Information
-221Settings conflict; Input
Port is not available
while occupied by Output
of incompatible frequency
-221Settings conflict; Input
Port is not available
while port bank is
occupied by Output
-221Settings conflict; Input
Z unavailable when probe
sensed
-221Settings conflict;
Instrument Gain LOW is not
supported when frequency
> 3.6 GHz. Auto change it
to ZERO, Acq=#
-221Settings conflict;
Internal Preamp is not
available for this
measurement
You attempted to select a port as an Input for a mmWave
Transceiver of a given frequency range, but the Output is already
configured for a mmWave Transceiver of an incompatible
frequency range. First set the Output Port to None and then
select an Input port.
The desired destination port bank for the Input Port is already
occupied by the Output Port. First set the Output to a different
port bank or None. Note the Output must be OFF before it can be
changed to a different port.
A probe is connected and the Input Z is set based on the probe
type. It cannot be changed manually.
When the acquisition frequency is change to be greater than
3.6GHz, the Instrument Gain will be set to ZERO automatically if
the current value is LOW.
This is a warning message, no action is required.
You are not allowed to change internal preamp in the current
measurement.
-221Settings conflict;
Invalid trace number
-221Settings conflict; Knob
is not available to modify
this function
-221Settings conflict; Limit
cannot be auto-coupled
while freq is out of
CISPR14 range
-221Settings conflict; LO
Phase Noise Adj not
available
-221Settings conflict; LPF
300 kHz setting is not
available in Audio
Measurement
-221Settings conflict; Manual
RF Input Ranging is not
available
-221Settings conflict; Marker
1 Trace Update=off turns
off Signal Track
The subopcode used to specify the trace number is invalid for this
measurement or query
You should select a specific value for this function. So scrolling
through values with the knob is not allowed.
Settings conflict; Limit cannot be auto-coupled while freq is out of
CISPR14 range
For instruments without the Dual-Loop LO, this feature is not
available
You are not allowed to change LPF setting to 300 kHz in Audio
Measurement because the input only can read until 200 kHz.
You are not allowed to change the Input Attenuation in the current
range.
Signal Track not available unless the trace containing Marker 1 is
updating
Instrument Messages 57
Page 58
Instrument Messages
Event Messages
Err#MessageVerbose/Correction Information
-221Settings conflict; Marker
cannot be relative to
itself
-221Settings conflict; Marker
Count is not available
when Gate on
-221Settings conflict; Marker
Function is not available
for a Fixed marker
-221Settings conflict; Marker
type must be delta
-221Settings conflict;
Marker-> function is not
available in zero span
-221Settings conflict; Mask
unavailable for current
Span. Increase to display
mask.
-221Settings conflict; Meas
Type was changed to
Examine for Exp Avg Mode.
A marker must be set relative to another marker, not to itself.
The marker count function cannot be used while you have gating
turned on.
If a Marker is a Fixed type marker, the marker's value does not
change from when it first became fixed. You cannot turn on or
change a Marker Function because there is no ongoing
measurement data to use for the marker function calculation.
Mkr∆->Span and Mkr∆->CF require that the selected marker be
a delta marker.
Most of the “Marker To” functions are not available if you are in
zero span (span = 0 Hz, or time domain). So you cannot send the
commands for these functions.
The current span setting is either narrower than the mask width
or so wide that there are too few display points to allow the mask
to be drawn. Increase or decrease the span to display the mask.
Average Mode has been changed to Exponential. Full Meas Type
is not available for Exponential Average Mode therefore Meas
Type has been changed to Examine.
-221Settings conflict; Meas
Type was changed to Full
for Repeat Avg Mode
-221Settings conflict;
Measurement Bitmap ***
not available in Radio
Standard ***, Acq=#
-221Settings conflict;
Minimum setting is only
available when Modulation
Mode is AM
-221Settings conflict;
MinPts/RBW limit not met
-221Settings conflict; Mkr ->
CF is not available when
the x-axis is time domain
-221Settings conflict; Mod
Scheme AutoDet
unavailable when Burst
Sync=RF Amptd
Average Mode has been changed to Repeat. Examine Meas Type
is not available for Repeat Average Mode therefore Meas Type has
been changed to Full.
The configured measurement is not supported by the current
radio standard.
Remove this measurement from the current acquisition or change
the radio standard of the current acquisition.
You are not allowed to change IF BW Type setting to Minimum if
you are not in AM Depth or Modulation Mode is not in AM.
The marker to center frequency functionality does not work when
the x-axis is in the time domain.
The modulation scheme auto detection is unavailable when the
burst sync is set to RF Amptd (GSM/EDGE)
Instrument Messages 58
Page 59
Instrument Messages
Event Messages
Err#MessageVerbose/Correction Information
-221Settings conflict; MPA
GPS port power setting
<n>dBm is lower than
-130dBm minimum
-221Settings conflict; MPA TX
port<n> amplitude
correction delta exceeds
<n>dB between port<n1>
and port<n2>
-221Settings conflict; MPA TX
port<n> amplitude
correction value <n>dB is
out of range. The valid
range is <n> ~ <n>dB”
-221Settings conflict; MPA TX
port<n> power setting
<n>dBm is lower than
-130dBm minimum
-221Settings conflict; MS
gain is not available in
this Mode
Indicating the power output setting (UI power + Amp Corr Value)
on MPA GPS port is lower than supportable minimum -130dBm.
Set power output setting to be larger than -130dBm to eliminate
this warning.
Indicating the amplitude correction delta value between MPA TX
port<n1> and port<n2> for MXG mode (port difference) exceeds
max loss delta value.
Set related amplitude correction delta value to be lower than the
max loss delta value given in error message.
Indicating the amplitude correction value of MPA TX port<n> for
MXG mode is out of range.
Set related amplitude correction value within the valid range
given in error message.
Indicating the power output setting (UI power + Amp Corr Value)
on MPA TX port<n> is lower than supportable minimum
-130dBm.
Set power output setting to be larger than -130dBm to eliminate
this warning.
Mobile Station gain correction is not available in some Modes, or
in some measurements (for example, the SA measurement).
-221Settings conflict; Must
apply Amplitude
Correction to make this
unit available
-221Settings conflict; No Cal
Factor for Power Sensor
-221Settings conflict; No
meas frequencies are
above 3.6 GHz
-221Settings conflict; no
source selected
-221Settings conflict; No
Stepped Scan Type
-221Settings conflict;
Normalize is not
available when Scale Type
= Lin
These special units only apply when you are doing antenna
measurements so you have to have a correction which includes
Antenna Units enabled
The center frequency set has no cal factor data associated with it.
Optimize Preselector can only be performed on frequencies in
high band i.e. freqs above 3.6 GHz. The current setup does not
have input freqs (IF) in this range so an Optimize Preselector
cannot be performed.
You must select a source using Select Source before you can do
this
Discrete Scan Type does not appear in this model
Normalize does not support Linear amplitude scale, since the
results are always presented as a dB ratio.
Instrument Messages 59
Page 60
Instrument Messages
Event Messages
Err#MessageVerbose/Correction Information
-221Settings conflict;
Normalize is not
available while Demod
View is on
-221Settings conflict;
Normalize is not
available while Trace
Math is on
-221Settings conflict; not
available with Global EMC
Standard
-221Settings conflict; Only
active Antenna Unit
available; no other Y axis
units
-221Settings conflict; Option
not available
-221Settings conflict; Output
Port is not available
while occupied by Input
-221Settings conflict; Output
Port is not available
while occupied by Input of
incompatible frequency
The normalization (correction) function cannot be used if you are
using the Demod View.
The Normalize function works by doing trace manipulation. So if
trace math is on you cannot turn on normalization.
You can’t use this function. To enable this function, turn off Global
EMC Standards.
When a correction with antenna units is turned on, the only Y-Axis
units you can have are those that match the Antenna Unit. Turn off
the Correction or the Antenna Unit under Input/Output,
Corrections
You have attempted to perform an action for which a required
option is not installed
The desired destination for the Output Port is already occupied by
the Input Port. First set the Input to a different port or None.
You attempted to select a port as an Output for a mmWave
Transceiver of a given frequency range, but the Input is already
configured for a mmWave Transceiver of an incompatible
frequency range. First set the Input Port to None and then select
an Output port.
-221Settings conflict; Output
Port is not available
while port bank is
occupied by Input
-221Settings conflict; Param
only available when DUT is
a freq converter
-221Settings conflict; Param
only available when
External LO Mode is Swept
-221Settings conflict; Param
only available when
External LO Mode is Fixed
-221Settings conflict; Param
only available when
Frequency Mode is Fixed
Instrument Messages 60
The desired destination port bank for the Output Port is already
occupied by the Input Port. First set the Input to a different port
bank or None.
SCPI only message. The sideband and freq context parameters
are only available when a freq conversion setup is in use. Change
setup to contain a freq conversion to use these parameters.
SCPI only message. This parameter is only available when the LO
mode is set to Swept. Change the LO Mode to Swept.
SCPI only message. This parameter is only available when the LO
mode is set to Fixed. Change the Freq Mode to Fixed.
SCPI only message. This parameter is only available when the
Freq mode is set to Fixed. Change the Freq Mode to Fixed.
Page 61
Instrument Messages
Event Messages
Err#MessageVerbose/Correction Information
-221Settings conflict; Param
only available when
Frequency Mode is Swept
-221Settings conflict; Param
only available when valid
cal data exists
-221Settings conflict; PAvT
step end time exceeds the
analysis interval
-221Settings conflict; PAvT
step start time is less
than zero
-221Settings conflict; Phase
Discontinuity measurement
cannot be averaged, Acq=#
Step=#
-221Settings conflict; Power
search is not available
when ALC is On
SCPI only message. This parameter is only available when the
Freq mode is set to Swept. Change the Freq Mode to Swept
SCPI only message. The ‘Apply Calibration’ parameter is only
available when the stored cal data matches the current setup.
Perform a fresh ‘Calibrate Now’ or change setup such that current
cal data is valid.
The end time of PAvT measurement exceeds the analysis interval.
Decrease the end time of PAvT or increase the Analysis interval.
The start time of PAvT measurement cannot be less than ZERO.
The average count of acquisition which contains Phase
Discontinuity measurement cannot be greater than 1.
Set the average count of current acquisition to 1. Or remove the
Phase Discontinuity measurement from this analysis step.
Cannot do power search when ALC is On.
-221Settings conflict; Power
search is not available
when RF is Off
-221Settings conflict; Power
search is not available
when trigger type is not
free-run
-221Settings conflict; Preamp
gain is not available in
this Mode
-221Settings conflict; Preamp
unavailable with
electronic attenuator on
-221Settings conflict; Presel
Center not available for
unpreselected external
mixers
-221Settings conflict;
Preselector Adjust not
available for
unpreselected Ext mixer
Cannot do power search when RF is Off.
Cannot do power search when trigger type is not free-run.
Preamp gain correction is not available in some Modes or
Measurements
The electronic attenuator is on. Internal preamp cannot be used
while you are using the electronic attenuator.
The selected mixer type is Unpreselected. Preselector power
centering cannot be done on an unpreselected mixer.
The selected mixer type is Unpreselected. The preselector
adjustment cannot be done on an unpreselected mixer.
Instrument Messages 61
Page 62
Instrument Messages
Event Messages
Err#MessageVerbose/Correction Information
-221Settings conflict; Radio
Band *** *** not available
in Radio Standard ***,
Acq=#
-221Settings conflict; Radio
Device BTS not supported,
Acq=#
-221Settings conflict; Radio
Standard *** not
available, Acq=#
-221Settings conflict;
Reference marker must be
in same window
-221Settings conflict;
Relative Trigger needs
hardware support for this
meas
-221Settings conflict; RF
Envelope trace is not
available without Basic
IQ data measurement,
Acq=# Step=#
The radio band is not supported by the selected Radio Standard.
Change the radio band.
Sequence analyzer does not support BTS.
Change the device type of the acquisition radio standard related
mode to MS. For example: if acquisition 3 is configured as
WCDMA, so you should change the device type of WCDMA mode
to MS.
The radio standard related application is not preloaded.
Manually switch to the radio standard related mode and switch
back to Sequence Analyzer mode. Or select this mode as
preloaded in configure-application panel and then restart.
A delta marker and its reference must be in the same window.
This error occurs when you try to turn on a delta marker who’s
reference is in a different window.
To do Relative Triggering in this measurement requires optional
hardware that is not present in this analyzer.
RF envelope view is available only when the selected analysis step
contains basic IQ data measurement.
Configure Basic IQ data measurement into current analysis step
or switch the view to Result Metrics.
-221Settings conflict; Sample
Rate is fixed
-221Settings conflict; Scale
Type = Lin is not
available when Normalize
is on
-221Settings conflict;
Sequence may have gaps
when playing step <n>, if
next step trigger comes
later than current step
expires
-221Settings conflict;
Sequence too long, Acq = #
-221Settings conflict;
Pre-trigger is
insufficient for demod.
Decrease Trig Delay.
Instrument Messages 62
You attempted to set the sample rate on a product with fixed
sample rate.
Only the Log amplitude scale is available in Normalize, since the
results are always presented as a dB ratio.
You set the step duration type of step n to Time or Play Count
while the Step Trigger of step n+1 is not set to “Free Run”. So if
next step trigger comes later than the expiration of the current
step play time, the ARB will stop playing and cause a gap between
steps. This is a warning.
The duration of the whole sequence is too long. With current
configurations, The Sequence can only handle #-1 Acquisitions.
Page 63
Instrument Messages
Event Messages
Err#MessageVerbose/Correction Information
-221Settings conflict; Signal
Track is not available
with Continuous Peak
-221Settings conflict; Signal
Track is only available in
Swept SA measurement
-221Settings conflict; Signal
Track is turned off when
Zero Span is selected
-221Settings conflict; Source
List Step<n> MPA GPS port
power setting <n>dBm is
lower than -130dBm
minimum
-221Settings conflict; Source
List Step<n> MPA TX
port<n> amplitude
correction value <n>dB is
out of range. The valid
range is <n> ~ <n>dB”
-221Settings conflict; Source
List Step<n> MPA TX
port<n> amplitude
correction delta exceeds
<n>dB between port<n1>
and port<n2>
The signal tracking feature cannot be used while you are also
using the continuous peak function.
The signal track functionality can be used when making a swept
SA measurement. It is not available in the SA measurement when
you are using FFT sweeps.
Signal Track is not available when you have selected Zero Span.
So if Zero Span is entered while in Signal Track is On, Signal Track
is turned off.
Indicating the power output setting (UI power + Amp Corr Value)
on MPA GPS port on Source List Step<n> is lower than
supportable minimum -130dBm.
Set power output setting to be larger than -130dBm to eliminate
this warning.
Indicating the amplitude correction value of MPA TX port<n> on
Source List Step<n> is out of range.
Set related amplitude correction value within the valid range
given in error message.
Indicating the amplitude correction delta value between MPA TX
port<n1> and port<n2> on Source List Step<n> (port difference)
exceeds max loss delta value.
Set related amplitude correction delta value to be lower than the
max loss delta value given in error message.
-221Settings conflict; Source
List Step<n> MPA TX
port<n> power setting
<n>dBm is lower than
-130dBm minimum
-221Settings conflict; Source
Output is not available
while Output Port is None.
-221Settings conflict; Span
limited to XXX
-221Settings conflict; Span
Zoom is not available in
Zero Span
-221Settings conflict; Step
duration cannot be set to
Play Count when the step
is generating a CW tone
Instrument Messages 63
Indicating the power output setting (UI power + Amp Corr Value)
on MPA TX port<n> on Source List Step<n> is lower than
supportable minimum -130dBm.
Set power output setting to be larger than -130dBm to eliminate
this warning.
You are attempting to enable the Source Output power while no
Output Port is selected; first select the Output Port.
Span Zoom does not work with a time domain x-axis. You must
select a span greater then 0 Hz.
The you tried to set the source list step duration type to Play
Count while the waveform of the step is CW. Play Count only
applies to ARB.
Page 64
Instrument Messages
Event Messages
Err#MessageVerbose/Correction Information
-221Settings conflict; Step
keys are not available to
modify this function
-221Settings conflict; Sweep
Setup only available in
swept measurements
-221Settings conflict; Sweep
Time cannot be
auto-coupled in FFT
sweeps
-221Settings conflict; Sweep
Time cannot be
auto-coupled while in
Zero Span
-221Settings conflict; Sweep
Time cannot be set while
in FFT sweeps
-221Settings conflict; Swept
IF Gain High not available
when FFT IF Gain = Manual
Low
You should select a specific value for this function. So using the
Up/Down step keys to scroll through values is not allowed.
The current measurement uses FFT mode and so does not use the
Sweep Setup menu
The sweep time for FFT sweeps is set by the calculations. So
sweep time settings cannot be adjusted.
You cannot send the remote command to set the sweep time to
auto while you are in zero span.
The sweep time for FFT sweeps is set by the calculations. It
cannot be manually controlled.
When FFT IF Gain is manually set to Low, you cannot set the
Swept IF Gain to High because that would make the Reference
Level couplings wrong in swept mode.
-221Settings conflict; Swept
LO not available when freq
mode is Fixed
-221Settings conflict; Swept
Type=Swept is not
available while in Gated
FFT
-221Settings conflict; System
Display Settings,
Annotation is Off
-221Settings conflict; T hot
must be greater than T
cold
-221Settings conflict; The
parameter cannot be
changed in FAST mode
-221Settings conflict; Time
Domain Scan is not
available with EMC "None"
Standard
SCPI only message. The LO Mode cannot be set to Swept when
the freq mode is set to fixed. Change the freq mode away from
fixed, or perform the measurement at several fixed frequencies.
If you have selected gated FFT then you are using the FFT sweep
type and you cannot select the swept type of sweeping.
This is an override that turns off many of the annotations. This is
available as a security feature.
The Tcold value set under Meas Setup/ENR/Tcold, needs to be
lower than the Thot value currently being set. Tcold is often taken
as the ambient temperature of the noise source. If using an SNS
the Tcold value may be read automatically before every sweep.
TDS only supports CISPR and MIL standards
Instrument Messages 64
Page 65
Instrument Messages
Event Messages
Err#MessageVerbose/Correction Information
-221Settings conflict; Too
many points; Stop Freq
clipped to nearest value
allowed
-221Settings conflict; Trace
Math is not available
while Normalize is on
-221Settings conflict;
Tracking Source
unavailable in FFT Sweeps
-221Settings conflict;
Transition Time should be
greater than # us, Acq=#
-221Settings conflict;
Trigger Delay should be
greater than # us, Acq=#
-221Settings conflict;
Trigger input in use for
source synchronization
-221Settings conflict;
Trigger is not available
with span > 0 Hz.
Range Stop Frequency has been clipped to the nearest value
The Normalize function works by doing trace manipulation, so
trace math is not available while normalization is running.
Since FFT’s do not sweep, you cannot use a Tracking Source
while doing FFT’s
The transition time of acquisition # should be greater than physics
required minimum time.
Increase the transition time.
The trigger delay of acquisition # should be greater than physics
required minimum time.
Increase the time of trigger delay.
If Point Trigger is being used with an external trigger input to
synchronize an external source to the analyzer, that trigger input
is unavailable for triggering.
-221Settings conflict;
Trigger Level is too low,
Acq=#
-221Settings conflict; Tx
Band Spur meas does not
support this frequency
band.
-221Settings conflict; Tx
Band Spur measurement is
not defined for mobiles.
-221Settings conflict;
X-Scale > 255 MHz
unavailable in PvT
-221Settings
conflict;Administrator
privileges required
The Trigger Level on the specified Acquisition is too low, so that
the test-set cannot be triggered correctly.
Increase the trigger level.
The transmit band spur measurement does not support all of the
commercially available frequency bands. You need to change your
selection under Mode Setup, Radio, Band to one of the supported
bands.
Only base station testing is available.
In the PvT window, X-Scale (Acq BW) cannot be greater than 255
MHz, even if Option B5X is installed.
You must be logged in with Administrator privileges to do this.
Log out and log back in as the Administrator, then restart the SA
application.
Instrument Messages 65
Page 66
Instrument Messages
Event Messages
Err#MessageVerbose/Correction Information
-221Settings conflict;Auto
Scan Time/Meas Time do not
apply in Stepped Scan
Type.
-221Settings conflict;Cannot
accept time or count input
when step duration type is
Continuous on step #
-221Settings
conflict;ClearList &
Start not available when
ScanSeq = (Re)measure
-221Settings conflict;Freq >
1 GHz is not available
while RF Input 2 enabled
-221Settings
conflict;Function not
available while
measurement is running
-221Settings
conflict;function
unavailable with this EMC
Standard
The Auto Scan Time/Meas Time are not available when Scan Type
=Stepped Scan.
An attempt to set list sequence a step’s “Duration Time” or “Play
Count” when that step’s “Duration Type” is “Continuous”. This
error can only occur on SCPI input.
Set that step’s “Duration Type” to “Play Count” or “Duration Time”
first then setup count or time.
Cannot perform Clear List & Start during (Re)measure because
we needs the frequency information of the peaks in signal list to
perform (Re)measure.
Frequency is limited to 1GHz while RF Input 2 is enabled.
Settings change is not allowed while measurement is running.
You must stop the current measurement if you wish to change the
settings.
-221Settings conflict;Include
Source is Yes. ARB memory
operation is rejected
-221Settings conflict;Last
screen cannot be deleted
-221Settings conflict;Log
Percent Auto Step Rule
does not apply in Swept
Scan Type.
-221Settings
conflict;Multi-Screen
requires >1 screen
-221Settings conflict;QPD +
EMI Average + RMS Average
is not allowed
The you tried to load or delete files to/from ARB memory in the
Sequence Analyzer mode when Include Source is set to Yes.
First set Include Source to No, then perform desired ARB memory
operation.
There must be at least one Screen configured, you cannot delete
the last remaining screen.
The Log Percent rule is not available when Scan Type=Swept
Scan because we are always doing linear sweep.
There must be more than one Screen configured for Multi-Screen
to be enabled.
User is not allowed to turn on all 3 EMI detectors together. You
must turn off one of the EMI Detectors before you turn this on.
Instrument Messages 66
Page 67
Instrument Messages
Event Messages
Err#MessageVerbose/Correction Information
-221Settings conflict;Range
<{0}> is turned off as
total range points >
4,000,001.
-221Settings conflict;Scan
Time & Points do not apply
in current Step/Time
Control.
-221Settings conflict;Screen
limit reached
-221Settings conflict;Screen
SCPI cannot be used when
Display is disabled
-221Settings conflict;Step
Size & Meas Time do not
apply in current
Step/Time Control.
-221Settings conflict;The
number of input
parameters is too large
and is truncated to
current list step number
Max of Total range points is 4,000,001. Reduce Scan Points or
increase Step Size in order to turn on that range.
The Scan Time & Points are not available when Step/Time Control
is set to Step & Dwell.
You requested to add another screen with the number of screens
at the maximum.
The instrument is operating with display disabled
(DISPlay:ENABle OFF), you cannot create new Screens with the
display disabled.
The Step Size & Meas Time are not available when Step/Time
Control is set to Scan Time&Pts.
An attempt to set list sequence parameter whose index exceeds
the “Number of Steps”. This way only those parameters whose
indexes fall in number of steps will be accepted.
Reduce the number of parameters to be no large than “Number of
Steps”.
-221Settings
conflict;Transition time
may be short on step <step
number>.
–200 to –299, Execution Errors
This section lists all messages in the range except –221 messages. For details
of –221 messages, see “–221 Settings Conflict Errors” on page 48.
Note that Execution Errors are divided into subclasses, as follows:
–21xTrigger errors
–22xParameter error
–23xData corrupt or stale (invalid data)
–24xHardware error
–25xMass storage error
An attempt was made to set the source step transition time to a
value shorter than the hardware settling time
This is provide as a warning. Instrument operation may not be
impacted because the hardware could settle more quickly than is
normal. You can eliminate this warning by setting a longer
transition time.
Instrument Messages 67
Page 68
Instrument Messages
Event Messages
–26xExpression data error
–27xMacro error
–28xProgram error (a downloaded program-related execution error)
–29xMemory use error
Err#MessageVerbose/Correction Information
-200All ranges are off.
Turn on at least a
range
-200At Full ZoomMarker Zoom is not available as it has reached full zoom.
-200Cannot move marker
outside of displayed
frequency span
-200Disturbance List is
Empty
-200Disturbance selected
is not in the
Disturbance List
-200Execution ErrorA program execution error has occurred. The exact problem cannot be
-200Execution error;
Carrier frequency
outside device’s
transmit band
-200Execution Error; Data
in Correction File
Range x File x does
not cover the range
frequency span
There are no range turn on in scan table. You need to turn on at least a
range to initiate a scan.
Meters frequency is out of displayed frequency range. You must
extend the displayed range from the scan table if you wish to set the
selected marker to this frequency on the graph display.
Cannot perform the selected function because the disturbance list
contains no data.
The user has selected an invalid disturbance (one that is not in the list)
specifically identified.
The entered channel/carrier frequency is not within the range of your
current mode setup selection of standard and device.
You have tried to use a correction file that does not cover the
frequency span of the correction range. Please fix the file or select
another file.
-200Execution error;
Invalid GSM burst
timing
-200Execution error;
Invalid IP address
-200Execution error;
Invalid Marker Trace.
-200Execution Error; No
peak found.
Instrument Messages 68
A GSM-like burst was acquired, but its timing is not valid. Ensure the
correct Burst Type has been selected.
The IP address supplied is either not valid or does not belong to a
compatible Signal Generator. Please check the IP address and
instrument connection and try again.
Cannot place markers on the reference trace, because the reference
trace is currently turned off or has no data.
No signal peak was found within the defined parameters of the search.
(Note: for ESA/PSA compatibility, the Swept SA measurement uses
780 for this error number; all other measurements use -220)
Page 69
Instrument Messages
Event Messages
Err#MessageVerbose/Correction Information
-200Execution error; No
ranges are defined.
Activate a range.
-200Execution Error;
Preselector centering
failed
-200Execution Error;
Signal not stable
enough to track
-200Execution Error; Store
ref trace before
turning on Normalize
-200Execution error; Sync
word was not found.
-200Execution error; Trace
file contains no
compatible traces.
There are no active ranges in the range table. You will need to activate
at least one range.
Algorithm failed to center the preselector. This may be caused by the
signal peak being too low in amplitude, or it could be due to excessive
CW input signal, alignment error, or hardware failure.
The signal that you have selected to track is changing too much for the
function to track it properly.
The Reference trace data must be stored in the Ref trace before you
turn on the Normalization function.
NADC & PDC: In an EVM measurement, the sync word is not found and
the synchronization cannot be established when Sync Word is
selected in the Burst Sync menu.
Flexible Digital Demodulation: The sync word cannot be detected
because of inappropriate parameter settings or incorrect signal.
The trace file may have been created by another version of the Phase
Noise personality, which uses a different trace format that is
incompatible with the version you are running. Please check you are
running the most up to date version of the personality.
-200Execution error; Trace
file created by
incompatible version
of Phase Noise App
-200Function not available
before Marker Zoom is
performed
-200Function not available
before perform
Disturbance Zoom
-200Function not available
before Signal Zoom is
performed
-200Must perform Scan
before do Search
-200No marked signalCannot perform the selected function because no signal was marked.
-200No Measure At Marker
Added to Signal List
The trace file may have been created by another version of the Phase
Noise personality, which uses a different trace format that is
incompatible with the version you are running. Please check you are
running the most up to date version of the personality.
Function not available before perform Marker Zoom
Need to zoom in before you can zoom out
Function not available before Signal Zoom is performed.
Cannot perform Search as the trace data is found empty
You must mark the peak of interest before selecting the function.
No signal peak was added into Signal List as there is no valid measure
to Marker result. You must perform Measure at maker before selecting
Measure At Marker --> List.
Instrument Messages 69
Page 70
Instrument Messages
Event Messages
Err#MessageVerbose/Correction Information
-200No Peak Added to
Signal List
-200No unmarked signalsCannot perform the selected function because no signal was
-200Signal List is EmptyCannot perform the selected function because the signal list contains
-200Signal List is FullCannot perform the selected function because the signal list is full.
-200Signal Selected is not
in the Signal List
-200Signal selected is out
of display range
-201Invalid while in localThe command cannot be executed while the instrument in Local
-202Settings lost due to
rtl
-203Command protectedThe command could not be executed because it is disabled. It was
No signal peak was added from the Search to Signal List as there is no
signal peaks found within the defined parameters of the search
criteria.
unmarked. You must unmark the peak of interest before selecting the
function.
no data.
Please clear the list.
The signal selected is not the list. You only can perform the operation
on signal that is already available in the list.
Signal selected is out of display range. You must extend the display
range if you wish to view the selected signal on the graph display.
control.
A “return to local” control was forced and some settings were lost as a
result of this.
disabled by licensing or password protection
-203Command protected;
feature not licensed
-203Command
protected;Feature Not
Supported. No
appropriate waveform
license installed for
<filename>
-210Trigger errorA trigger error has occurred, but the exact problem cannot be
-211Trigger ignoredA GET, *TRG or other triggering signal was received, but it was ignored
-212Arm ignoredAn arming signal was received, but it was ignored.
-213Init ignoredAn initiate trigger/sweep request was received and ignored, because
-214Trigger deadlockThe trigger source for the initiation of a measurement is set to GET,
The specified feature, for example “N9073A-TR2” is not licensed. The
license may have expired. You cannot use it until you get a license.
An attempt was made to select a waveform while the required license
is not installed
Install necessary Signal Studio waveform licenses or multi-pack
licenses.
specifically identified.
because of timing considerations. For example, maybe the instrument
was not ready to respond when the command was received.
another measurement was already in progress.
and the following measurement query was received. The measurement
cannot be started until a GET is received, but the GET would cause an
INTERRUPTED error.
Instrument Messages 70
Page 71
Instrument Messages
Event Messages
Err#MessageVerbose/Correction Information
-215Arm deadlockThe arm source for the initiation of a measurement is set to GET and
the following measurement query is received. The measurement
cannot be started until a GET is received and the GET would cause an
INTERRUPTED error.
-220Parameter errorA problem was found with a program data element. The exact problem
cannot be specifically identified.
-220Parameter error;
<filename> is not
loaded into ARB
memory. Load the file
before assigning to a
multi-pack
-220Parameter error;
License slot <n> is
illegal, slot number
must be positive
-220Parameter
error;<filename> does
not have a unique id,
therefore cannot be
assigned to a
multi-pack
-220Parameter error;Cannot
create directory to
save waveform sequence
file. <error info>
-220Parameter error;Cannot
find the first
waveform file
<filename>
An attempt was made to assign a multi-pack license to a waveform,
while the waveform file has not been loaded into ARB memory.
Load ARB into ARB memory first then add the ARB in multi-pack
license slot.
An attempt was made to input a slot number less than or equals 0.
Waveform slot number must be positive
An attempt was made to add a Signal Studio waveform to a license
slot while the waveform unique id is zero.
Set the waveform unique ID to a value other than zero.
An attempt was made to create a directory to store new waveform
sequence but failed.
Input correct directory path parameter.
An attempt was made to build a new waveform sequence while the
first specified waveform file is not found.
Specify correct path for the first waveform segment.
-220Parameter
error;Invalid waveform
sequence file path
-220Parameter
error;License slot <n>
is already locked
-220Parameter
error;License slot <n>
is locked and cannot
be cleared
Instrument Messages 71
An attempt was made to build or query a waveform sequence while the
waveform sequence file path is invalid or not specified.
Specify a correct path for the waveform sequence.
An attempted was made to lock a slot while the slot was already
locked.
An attempt was made to clear a slot while the slot was already locked.
Page 72
Instrument Messages
Event Messages
Err#MessageVerbose/Correction Information
-220Parameter
error;License slot <n>
is locked, therefore
cannot be replaced
-220Parameter
error;License slot <n>
is not assigned,
therefore cannot be
locked
-220Parameter error;Nested
sequence file is not
supported
-220Parameter error;Nested
sequence file is not
supported
-220Parameter error;No.
<n> waveform file path
is invalid
-220Parameter
error;Repetition value
must be within 1 and
65535
An attempt was made to replace a slot with another waveform while
the slot was already locked.
An attempt was made to lock a slot while the slot was not assigned.
An attempt was made to add a sequence file as a waveform segment
into another sequence file.
An attempt was made to build a new waveform sequence which
contains another waveform sequence file.
Do not nest waveform sequence file (*.seq) into another waveform
sequence file (*.seq).
An attempt was made to build a new waveform sequence while the nth
waveform file path is invalid or not specified.
Specify a correct path for the waveform.
An attempt was made to build a new waveform sequence with the
repetition value set to less than 1 or greater than 65535.
-220Parameter
error;Sequence will be
stuck on step <step
number>. Next step
trigger cannot be free
run when current step
duration is continuous
-220Parameter error;Suffix
of waveform sequence
file should be “.seq”
-220Parameter
error;Transition time
is longer than
duration time on
step<step number>
-220Parameter
error;Unrecognized
marker type: <marker>
An attempt was made to set the current step duration to continuous,
while the step trigger of the next step is set to free run.
Make the next step trigger to be other than free run.
An attempt was made to build a new waveform sequence while the
suffix of waveform sequence file is not “.seq”.
Ensure that the waveform sequence file suffix and file format is
consistent with “seq”.
An attempt was made to set the source step transition time to a value
that is longer than step duration time, when the step duration type is
“Time”.
Make the transition time shorter than the duration time.
An attempt was made to build a new waveform sequence while the
marker type value is invalid.
Input correct maker type parameter.
Instrument Messages 72
Page 73
Instrument Messages
Event Messages
Err#MessageVerbose/Correction Information
-220Parameter
error;Waveform
<filename> is already
assigned to a waveform
slot
-220Parameter
error;Waveform cannot
be multi-pack
licensed, no
multi-pack slots
available
-220Parameter
error;Waveform of that
ID is already
multi-pack licensed
-221Settings conflict;There are many types of settings conflict errors. See section 3.5 for
-222Data out of range;A data element was found but the instrument could not be set to that
An attempt was made to assign a waveform to a slot while the
waveform was already assigned to another waveform slot.
An attempt was made to multi-pack license a waveform, but there are
no free multi-pack license slots.
Install multi-pack licenses to get multi-pack license slots.
An attempt was made to multi-pack license a waveform that was
already licensed by a different multi-pack license slot.
information about these errors.
value because it was outside the range defined for the command. A
descriptive message may be appended, such as “clipped to upper
limit”
-222Data out of Range;
clipped to source
max/min
-222Data out of Range;
Dwell Time clipped to
minimum value allowed
-222Data out of range;
Invalid Correction
Group range data
-222Data out of range;
Invalid list data
-222Data out of range;
Invalid slice data at
the number specified
-222Data out of Range;
Scan Time limited,
multiple CISPR det’s
in use for prescan
-222Data out of Range;
Step Size clipped to
nearest value allowed
A source parameter has been entered that exceeds the range of the
selected source. The parameter has been clipped to match the range
of the source
The dwell time entered could not be set to. It is clipped to the
minimum allowable value, which is determined by the smallest RBW
set in Scan Table.
You tried to set the data for a Correction Group range which is not
connecting to the range currently available.
You tried to use a trace that has a number of sweep points that is
different from the current setting of sweep points.
You tried to query for an invalid range of time slice data.
The scan time/ meas time entered could not be set to. Scan time is
limited to 2.4 ks with multiple CIPSR detectors turned on.
The step size entered could not be set to. It is clipped to the nearest
allowable value.
Instrument Messages 73
Page 74
Instrument Messages
Event Messages
Err#MessageVerbose/Correction Information
-222Data out of range; Two
entries already exist
at this x-axis value.
-222Data out of
range;Calibration Date
(YYYYMMDD) is invalid
-223Too much dataA data element (of block, expression, array type, or string type) had
-223Too much data; 200
spurs found.
Additional spurs
ignored.
-224Illegal parameter
value
-224Illegal parameter
value; <Value>
invalid. Fractional
values are not
allowed.
-224Illegal parameter
value; <value> out of
range.
When entering values for limit lines, you cannot have more than two
y-axis (amplitude) values entered for a specific x-axis (frequency)
value.
You have entered an invalid calibration date. The calibration date
should be in the format of YYYYMMDD.
more data then allowed by the command, or by the available memory.
There are too many spurs for the table (the limit is 200), and any
additional spurs that are found will be ignored.
An exact data value (from a list of the allowed values) was required but not found. See the feature description for information about the
expected parameter values.
The seconds parameter of an LXI time may not contain a fractional
portion. For example 123456789.0 is valid while 123456789.1 is not.
The value does not fall in the valid range
-224Illegal parameter
value; Cannot set
waveform to continue
previous waveform on
the first step
-224Illegal parameter
value; EMI Avg/RMS Avg
and Average detector
can’t be used together
-224Illegal parameter
value; Exceeding the
max list length
-224Illegal parameter
value; existing Screen
Name not found
-224Illegal parameter
value; Gated FFT is
not available while
Sweep Type is set to
Swept
An attempt was made to set the waveform for the first step in a
sequence to “Continue Previous” while there is no previous waveform
to continue playing back.
User is not allowed to turn on any EMI Avg/RMS Avg and Average
detector together. They are always mutually exclusive.
The list parameters have a maximum allowed length. You are trying to
set a length longer than the maximum.
An attempt was made to reference an existing Screen Name, but the
text provided did not match an existing Screen Name.
The gated FFT function is not available if you have selected the swept
type of sweep. You must be in the FFT sweep type.
Instrument Messages 74
Page 75
Instrument Messages
Event Messages
Err#MessageVerbose/Correction Information
-224Illegal parameter
value; Gated LO is not
available while Sweep
Type is set to FFT
-224Illegal parameter
value; Gated Video is
not available while
Sweep Type is set to
FFT
-224Illegal parameter
value; Index out of
range
-224Illegal parameter
value; Invalid list
length
-224Illegal parameter
value; Measurement not
available
-224Illegal parameter
value; new Name
already exists
The FFT sweep type moves the LO frequency in steps. So the gated LO
function is not available if you have selected FFT sweep.
The gated video function is not available if you have selected the FFT
sweep type.
When querying the LXI Event Log or the Servo Log, an index may be
used to look at a specific entry. This error occurs if the index provided
does not point to a valid entry.
You are trying to set some list measurement settings, but the multiple
lists that you sent were not all the same length. The number of settings
must be consistent from list to list.
You tried to turn on a measurement that is not available in the current
mode.
An attempt was made to specify a new Name, but the name already
exists; a unique name must be specified.
-224Illegal parameter
value; QPD + EMI
Average + RMS Average
is not allowed
-224Illegal parameter
value; Res BW value
not allowed with
current Span
-224Illegal parameter
value;Cannot set
waveform to continue
previous waveform when
previous step is set
to CW or Off
-224Illegal parameter
value;Channel number
is invalid for current
band/link combination
-224Illegal parameter
value;This instrument
is always DC coupled
User is not allowed to turn on all 3 EMI detectors together. You must
turn off one of the EMI Detectors before you turn this on.
With Option B5X, with Spans greater than 255 MHz the Res BW
desired is not available.
An attempt was made to set the step duration for a step in a sequence
to “Continue Previous”, but the previous step was outputting a CW
tone or is Off, so there is no waveform to continue.
An attempt was made to enter a channel number for a step within the
List Sequencer, but the channel number is out of the valid range for
the Band and Radio Band Link direction combination defined within
the step.
You can’t set AC coupling in this instrument
Instrument Messages 75
Page 76
Instrument Messages
Event Messages
Err#MessageVerbose/Correction Information
-224Illegal parameter
value;This model is
always AC coupled
-225Out of memoryThere is not enough memory to perform the requested operation.
-225Out of memory;
Insufficient resources
to load Mode <mode
name>
-225Out of memory;
Insufficient resources
to load Mode <mode
name>. Paging file
size too small
-225Out of memory; Memory
limit caused Data
Acquisition to be
truncated
-226List not same lengthYou are using the LIST structure, but have individual lists that are not
You can’t set DC coupling in this analyzer
If you attempt to load a mode via SCPI that will exceed memory
capacity, the Mode does not load and this message is returned. “mode
name” is the SCPI parameter for the Mode in question, for example, SA
for Spectrum Analyzer Mode. You can free up resources in the System,
Power On, Configure Applications menu
If you attempt to load a mode via SCPI that will exceed memory
capacity, the Mode does not load and this message is returned. “mode
name” is the SCPI parameter for the Mode in question, for example, SA
for Spectrum Analyzer Mode. You can free up resources in the System,
Power On, Configure Applications menu.
Also, paging file size is unexpectedly small. Consider increasing the
paging file size or cleaning up unnecessary files from system drive.
the same lengths.
-230Data corrupt or stale;A legal data element was found, but it could not be used because the
data format or the data structure was not correct. Maybe a new
measurement had been started but had not completed.
-230Data corrupt or stale;
Measurement data is
not available
-230Data corrupt or stale;
Trace contains no
data.
-230Data corrupt or stale;
Unable to load state
from file
-231Data questionableIndicates that the measurement accuracy is suspect
-232Invalid formatA data element was found but it could not be used because the data
-232Invalid format; Map
information not loaded
Measurement data not available. The measurement that you are trying
to get data from must be the current active measurement. Maybe you
have not initiated the measurement, or it has not completed all the
sweeps/averages needed.
Trace cannot be displayed because currently there is no data assigned
to it. Use the functions under the Trace menu, or load a previously
saved trace, to assign data to the trace.
There is something wrong with the state data in the desired file. Maybe
the file is corrupt, or it is from an instrument/version that is not
recognized by the current instrument.
format or the data structure was not correct.
Instrument failed to load the burst mapping information from the
selected file.
Instrument Messages 76
Page 77
Instrument Messages
Event Messages
Err#MessageVerbose/Correction Information
-232Invalid
format;<filename>
contains invalid
waveform header and
cannot be loaded into
ARB memory
-232Invalid
format;<filename> has
less than 500 IQ
samples
-232Invalid format;Syntax
error on source step
<step number>
-232Invalid format;Unable
to open encrypted
waveform file
<filename>
-233Invalid versionA legal data element was found but could not be used because the
An attempt was made to load, into ARB memory, a Signal Studio
waveform file that contains an invalid waveform header.
An attempt was made to load, into ARB memory, a waveform file, but
the file does not contain enough IQ samples.
Load an ARB waveform with a sample number equal to or greater than
500.
An attempt was made to load in a list sequencer file that was
incorrectly formatted.
An attempt was made to load, into ARB memory, a Signal Studio
waveform file, but the file cannot be opened due to invalid file format.
version of the data is incorrect. For example, state data changes as
new instrument features are added, so old state files may not work in
an instrument with a newer version of software.
-240Hardware errorA legal program command or query could not be executed because of
a hardware error. The exact problem cannot be specifically identified.
-240Hardware error; See
details in Windows
Event Log under SA
-241Hardware missingThe operation could not be performed because of missing hardware;
-241Hardware missing;
Input not available
-241Hardware missing;
Internal preamp not
available at all
frequency points
-241Hardware missing; not
available for this
model number
-241Hardware missing;
Option not installed
-241Hardware missing;
Output not available
The internal data acquisition system detected a problem at startup and
logged the details in the Windows Event Log.
perhaps the optional hardware is not installed.
The hardware required is not part of this model or the option is not
installed
The Internal Preamp is currently turned on, but the measurement is
being performed completely or partially outside the range of the
preamp. It is recommended that the user turns preamp off to ensure
consistent results across the entire measurement.
The hardware required is not part of this model
The optional hardware is not installed.
The hardware required is not part of this model or the option is not
installed
Instrument Messages 77
Page 78
Instrument Messages
Event Messages
Err#MessageVerbose/Correction Information
-241Hardware missing;
Power sensor hardware
is missing
-250Mass storage error;A problem was found with the mass storage device (memory, disk
-250Mass storage error;
Access denied
-250Mass storage error;
Bad path name
-250Mass storage error;
Can only import single
trace .csv files
-250Mass storage error;
Can only load an
Antenna Unit into
Correction 1
-250Mass storage error;
Can only load one file
with Antenna Unit per
range
There is no power sensor detected at the selected power meter. You
need to setup the power sensor before proceed.
drive, etc.). The exact problem cannot be specifically identified.
Access is denied.
The specified path is invalid.
Trace files containing multiple traces can not be imported. However, if
you need to recall multiple traces you can use the Save and Recall
functions rather than the Import and Export functions.
The only Correction register that supports Antenna Units is number 1.
You have attempted to load an Ampcor file which contains antenna
units into another register
You already have a Correction file with Antenna Unit in this range.
Attempt to import more than one Corrections file with Antenna Unit is
not allowed.
-250Mass storage error;
Cannot make
-250Mass storage error;
Different
Antenna Unit already
in used in another
range
-250Mass storage error;
Different Antenna Unit
already in use
-250Mass storage error;
Directory not found
-250Mass storage error;
Failed to Load trace.
Bad file format.
-250Mass storage error;
File <filename> and
instrument version
mismatch
The directory or file cannot be created.
You have attempted to import a Corrections file with Antenna Unit
different from another range.
Attempt to import Corrections file with Antenna Unit that differs from
an in-use correction.
The system cannot find the path specified.
The load trace operation could not be completed, as the input file was
not in the expected format. You can only load traces that were
previously saved using the 'Save Trace' feature.
While opening a file, there was a mismatch between file version or
model number with instrument version or model number. The import
still tried to load as much as possible, but you should check it closely.
Instrument Messages 78
Page 79
Instrument Messages
Event Messages
Err#MessageVerbose/Correction Information
-250Mass storage error;
File <filename> wrong
type
-250Mass storage error;
File <filename>. Model
and serial number
fields don’t match
selected sensor
-250Mass storage error;
File contains
incorrect data for
this operation
-250Mass storage error;
File empty
-250Mass storage error;
Invalid register
number for *SAV or
*RCL Mass Storage
error
-250Mass storage error;
Lock violation
Attempt to import a data file that is not the proper type for this
operation.
The model and serial number fields don’t match the selected sensor.
Check cal factor .xml file content.
There is a mismatch between the file data type of the file specified and
the destination indicated. For example, a correction set cannot be
loaded/imported into a limit line.
Cannot save trace because it contains no data. Check that the trace is
turned on and contains some valid data.
You have used the *SAV command to save a state to a non existent
state register.
Or
You have used the *RCL command to recall a state register that wasn’t
previously saved with the *SAV command.
The process cannot access the file because another process has
locked a portion of the file.
-250Mass storage error;
Mkr Table must be on
to save Mkr Table as
Meas Results
-250Mass storage error; No
file names available
-250Mass storage error;
Open failed
-250Mass storage error; Pk
Table must be on to
save Pk Table as Meas
Results
-250Mass storage error;
Read fault
-250Mass storage error;
Register <number>
empty
You have to have a Marker Table on the screen before you can save it.
Turn on the Marker Table and try again.
Attempt to use the auto file name generation when all 10,000 file
names are taken.
The system cannot open the device or file specified. This could be
because the storage media is full, or possibly due to a filename error. If
using an external storage devise, check that the devise is properly
formatted.
You have to have a Peak Table on the screen before you can save it.
Turn on the Peak Table and try again.
The system cannot read from the specified device.
Attempt to recall a register with nothing in it
Instrument Messages 79
Page 80
Instrument Messages
Event Messages
Err#MessageVerbose/Correction Information
-250Mass storage error;
Sharing violation
-250Mass storage error;
Spectrogram must be on
to save as Meas
Results
-250Mass storage error;
Too many open files
-250Mass storage error;
Write fault
-250Mass storage
error;<directory> does
not exist
-250Mass storage
error;<filename>
cannot be deleted as
it is currently in use
-250Mass storage
error;<filename>
cannot be deleted as
it is used in
sequencer
The process cannot access the file because it is being used by another
process.
You have to have a Spectrogram on the screen before you can save it.
Turn on the Spectrogram and try again.
The system cannot open the file.
The system cannot write to the specified device.
An attempt was made to load all file from a directory while the
specified directory does not exist on the instrument hard disk.
Create the specified directory and then load the files or load the files
using an existing directory.
With ARB ON, an attempt was made to delete a waveform that was
being played.
Turn ARB to Off first, then delete ARB file from ARB memory.
With the list sequencer state ON, an attempt was made to delete a
waveform that was being used by the sequencer.
First turn the List Sequencer to Off, then delete the ARB file from ARB
memory.
-250Mass storage
error;<filename> used
by sequencer is not in
the ARB memory, cannot
start sequencer
You are using the wrong type of file extension for the current data/file
type.
The filename, directory name, or volume label syntax is incorrect.
An attempt was made to load or save a file with a suffix other than
“bin”, “waveform”, ”wfm” or “seq”.
Ensure that the waveform file suffix and file format are consistent with
“bin”, “waveform”, ”wfm” or “seq”.
An attempted was made to turn the ARB player ON but a file has not
been selected for playback.
Select a waveform first, and then turn on ARB state.
Page 82
Instrument Messages
Event Messages
Err#MessageVerbose/Correction Information
-258Media ProtectedA legal command or query could not be executed because the media
was protected. For example, the write-protect was set
-260Expression errorAn error was found with an expression type of data element. The exact
problem cannot be specifically identified.
-261Math error in
expression
-270Macro errorIndicates that a macro-related execution error occurred.
-271Macro syntax errorIndicates a syntax error within the macro definition
-272Macro execution errorIndicates that a syntactically legal macro program data sequence
-273Illegal macro labelIndicates that the macro label defined in the *DMC command was a
-274Macro parameter errorIndicates that the macro definition improperly used a macro parameter
-275Macro definition too
long
-276Macro recursion errorIndicates that a syntactically legal macro program data sequence
-277Macro redefinition\
not allowed
-278Macro header not foundIndicates that a syntactically legal macro label in the *GMC? query
An expression that has legal syntax could not be executed because of
a math error. For example, maybe you are dividing by zero.
could not be executed due to some error in the macro definition
legal string syntax, but could not be accepted
placeholder
Indicates that a syntactically legal macro program data sequence
could not be executed because the string or block contents were too
long for the device to handle
could not be executed because the device found it to be recursive
Indicates that a syntactically legal macro label in the *DMC command
could not be executed because the macro label was already defined
could not be executed because the header was not previously defined.
-280Program errorThere was an execution error in a down-loaded program. The exact
problem cannot be specifically identified.
-281Cannot create programIndicates that an attempt to create a program was unsuccessful. A
reason for the failure might include not enough memory.
-282Illegal program nameThe name used to reference a program was invalid; for example,
redefining an existing program, deleting a nonexistent program, or in
general, referencing a nonexistent program.
-283Illegal variable nameAn attempt was made to reference a nonexistent variable in a program.
-284Program currently
running
-285Program syntax errorIndicates that a syntax error appears in a downloaded program. The
-286Program runtime error
-290Memory use errors
Instrument Messages 82
Certain operations dealing with programs may be illegal while the
program is running; for example, deleting a running program might not
be possible.
syntax used when parsing the downloaded program is device-specific.
Page 83
Instrument Messages
Event Messages
Err#MessageVerbose/Correction Information
-291Out of memory
-292Reference name does
not exist;Waveform
sequence contains an
invalid waveform
<filename>
-292Referenced name does
not exist
-293Referenced name
already exists
-294Incompatible typeIndicates that the type or structure of a memory item is inadequate
A waveform sequence was selected for playback but not all of the
waveform segments in the waveform sequence are loaded into ARB
memory.
Ensure that all of the waveform segments are loaded into the ARB
memory.
Instrument Messages 83
Page 84
Instrument Messages
Event Messages
–100 to –199, Command Errors
Err#MessageVerbose/Correction Information
-100Command errorThere is a problem with the command. The exact problem cannot be
specifically identified.
-101Invalid characterAn invalid character was found in part of the command.
-102Syntax errorAn unrecognized command or data type was found, for example a string was
received for a command that doesn’t accept strings.
-103Invalid separatorThe command was supposed to contain a separator but we found an illegal
character. For example, the semicolon was omitted after a command string.
-104Data type errorWe found a data type different then what was expected. For example, numeric
or string data was expected, but block data was found.
-105GET not allowedA Group Execute Trigger was received within a program message.
-108Parameter not allowedMore parameters were received than were expected for the command. For
example, the *ESE common command only accepts one parameter, so sending
*ESE 0,1 is not allowed.
-109Missing parameterFewer parameters were received than required for this command.
-110Command header errorThis is a general error that is generated when a problem is found in a command
header, but we can’t tell more specifically what the problem is
-111Header separator
error
-112Program mnemonic too
long
-113Undefined headerThe command meets the SCPI syntax requirements, but is not valid in the
-114Header suffix out of
range
-115Unexpected number of
parameters
-120Numeric data errorAn error was found in a data element that appears to be numeric. The exact
-121Invalid character in
number
-123Exponent too largeThe magnitude of an exponent was greater than 32000.
We found an illegal character in a command where we expected to find a
separator.
The command contains a keyword that is more than twelve characters.
current measurement environment.
The value of a numeric suffix that is attached to a program mnemonic makes
the header invalid. (A suffix is usually units, like Hz or DB.)
The number of parameters received does not correspond to the number of
parameters expected.
problem cannot be specifically identified.
A character was found that is not valid for the data type. For example, an alpha
in a decimal numeric or a “9” in octal data.
-124Too many digitsThe mantissa of a decimal-numeric contained more than 255 digits, excluding
leading zeros.
-128Numeric data not
allowed
Instrument Messages 84
A legal numeric data element was found, but that is not a valid element at this
position in the command.
Page 85
Instrument Messages
Event Messages
Err#MessageVerbose/Correction Information
-130Suffix errorA problem was found in a suffix (units). The exact problem cannot be
specifically identified.
-131Invalid suffixThere is a syntax problem with the suffix. You need to use the suffix (units) that
are allowed by this command.
-134Suffix too longThe suffix contained more than twelve characters.
-138Suffix not allowedA suffix was found after a numeric element that does not allow suffixes (units).
-140Character data errorA problem was found with a character data element. The exact problem cannot
be specifically identified.
-141Invalid character
data
-144Character data too
long
-148Character data not
allowed
-150String data errorA problem was found with a string data element. The exact problem cannot be
-151Invalid string dataA string type of data element was expected, but it is invalid for some reason.
-158String data not
allowed
-160Block data errorA problem was found with a block data element. The exact problem cannot be
-161Invalid block dataA block data element was expected, but it was invalid. For example, an END
-168Block data not
allowed
Either the character data element contains an invalid character or the element
itself is not valid for this command.
The character data element contains more than twelve characters.
A character data element that you sent is valid, but it is not allowed in this point
in the parsing.
specifically identified.
For example, an END message was received before the terminal quote
character.
A string data element that you sent is valid, but it is not allowed at this point in
the parsing.
specifically identified.
message was received before the end length was satisfied.
A legal block data element was found, but it is not allowed at this point in the
parsing.
-170Expression errorA problem was found with an expression data element. The exact problem
cannot be specifically identified.
-171Invalid expressionAn expression data element is not valid. For example, there may be unmatched
parentheses or an illegal character.
-178Expression data not
allowed
-180Macro errorA problem was found with a macro element. The exact problem cannot be
-181Invalid outside macro
definition
Instrument Messages 85
A legal expression data was found, but it is not allowed at this point in the
parsing.
specifically identified.
Indicates that a macro parameter placeholder was encountered outside of a
macro definition.
Page 86
Instrument Messages
Event Messages
Err#MessageVerbose/Correction Information
-183Invalid inside macro
definition
-184Macro parameter errorIndicates that a command inside the macro definition had the wrong number or
Indicates that the program message unit sequence, sent with a *DDT or *DMC
command, is syntactically invalid
type of parameters.
0 No Error
Err#MessageVerbose/Correction Information
0No errorThe queue is empty. Either every error in the queue has been read, or the
queue was cleared by power-on or *CLS.
Instrument Messages 86
Page 87
Instrument Messages
Condition Messages
Condition Messages
Condition messages are classified as either “Errors” or “Warnings.” Condition
messages are not defined in the 1999 SCPI Syntax & Style Standard, and have
numbers greater than zero.
Every Condition has an associated Detected (Start) Event and Cleared (End)
Event. The Condition itself has the same number as its Detected Event. The
Detected Event has a number less than 1000, and the Cleared Event has the
same number plus 1000.
In the tables in this section, an E in the Error or Warning column means that an
Error is displayed on the front panel and sent out to SCPI when this condition is
detected. A W in this column means that a Warning is displayed on the front
panel, but nothing is sent to SCPI.
For each Condition Message, there is a corresponding bit in one of the SCPI
status registers. These bits are listed in the "Bit in status register" column of the
tables below. Some messages exist only as status bits; for these messages the
Error or Warning column contains “status bit only”.
The tables in this section are divided by number range, as follows:
— “1 to 99, Calibration” on page 87
— “101 to 199, Measurement Integrity” on page 92
— “201 to 299, Signal Integrity” on page 97
— “301 to 399, Uncalibrated Integrity” on page 102
— “401 to 499, Power” on page 106
— “501 to 599, Frequency” on page 108
— “601 to 699, Error Summaries” on page 109
— “701 to 799, Operation” on page 110
— “801 to 899, Temperature” on page 111
1 to 99, Calibration
These messages correspond to the STATus:QUEStionable:CALibration
register (see “X-Series Status Register System” on page 116). Since this
register is fanned out to three sub-registers, with summary bits in the main
STATus:QUEStionable:CALibration register, each sub-register has its own
range of message numbers.
6 to 34, Calibration Skipped
This series of messages corresponds to the bits in the
STATus:QUEStionable:CALibration:SKIPped sub-register (see “X-Series
Status Register System” on page 116). The second column in the table shows
the corresponding bit in that register.
Instrument Messages 87
Page 88
Instrument Messages
Condition Messages
An event with the number shown in the table means the condition has been
detected. When the condition is cleared, an event with the number plus 1000
is generated. These numbers can be viewed in the Show Errors screen, along
with the DETECTED and CLEARED indicators.
For example, message 6 indicates that the “RF Alignment being skipped”
condition has been detected, and message 1006 indicates that failure has
been cleared.
This register is summarized as bit 11 of the
STATus:QUEStionable:CALibration register, as described in section “36 to
64, Calibration Needed or Failed” on page 88.
Err#Bit in
status
register
60 Align RF SkippedW
81unused
102unused
123unused
144unused
165unused
186unused
207unused
228unused
249unused
2610unused
2811unused
3012unused
MessageError or
More Information
Warning
3213unused
3414unused
36 to 64, Calibration Needed or Failed
This series of messages corresponds to the bits in the
STATus:QUEStionable:CALibration register (see “X-Series Status Register
System” on page 116). The second column in the table shows the
corresponding bit in that register.
Instrument Messages 88
Page 89
Instrument Messages
Condition Messages
An event with the number shown in the table means the condition has been
detected. When the condition is cleared, an event with the number plus 1000
is generated. These error numbers can be viewed in the Show Errors screen,
along with the DETECTED and CLEARED indicators.
For example, message 42 indicates that the “RF Alignment Failure” condition
has been detected, and message 1042 indicates that failure has been cleared.
Several bits in this register are “summary bits” for registers at a lower level.
There are no messages associated with these bits; they exist only as status bits,
which can be read with a STATus:QUEStionable:CALibration? event query or
a STATus:QUEStionable:CALibration:CONDition? query.
Note that these summary bits summarize the state and history of the event
registers at the lower level. This is true even for bits in the
STATus:QUEStionable:CALibration condition register. This means that:
— The summary bits read by the
STATus:QUEStionable:CALibration:CONDition? query are true if any
event bits are set in any of the :CALibration sub-registers :SKIPped,
:EXTended:NEEDed or :EXTended:FAILure.
— The summary bits read by the STATus:QUEStionable:CALibration? event
query are true if any event bit has undergone a false-to-true transition with
the PTRansition filter set, or a true-to-false transition with the NTRansition
filter set, in any of the :CALibration sub-registers :SKIPped,
:EXTended:NEEDed or :EXTended:FAILure.
Thus, the summary bits cannot be used to determine the current state of a
lower level condition bit; only the state and history of the lower level event bits.
This register is itself summarized as bit 8 of the STATus:QUEStionable register,
as described in the section “601 to 699, Error Summaries” on page 109.
Err#Bit in status
register
360unused
381unused
402TG Alignment FailureE
423RF Alignment FailureE
444IF Alignment FailureE
465LO Alignment FailureE
MessageError or
More Information
Warning
486ADC Alignment FailureE
507FM Demod Alignment FailureE
528Extended Align Needed
Summary
Instrument Messages 89
status bit
only
This bit is the summary bit for the
STATus:QUEStionable:CALibration:EXT
ended:NEEDed sub-register.
Page 90
Instrument Messages
Condition Messages
Err#Bit in status
register
549Extended Align Failure
5610unused
5811Align Skipped Sum Summarystatus bit
6012Align Now, RF requiredE
6213unused
6414Align Now, All requiredEOn PSA, this was error 64
MessageError or
Warning
status bit
Summary
only
only
More Information
This bit is the summary bit for the
STATus:QUEStionable:CALibration:EXT
ended:FAILure sub-register.
This bit is the summary bit for the
STATus:QUEStionable:CALibration:SKIP
ped sub-register.
65 to 92, Calibration Needed (Extended)
This series of messages corresponds to the bits in the
STATus:QUEStionable:CALibration:EXTended:NEEDed sub-register (see
“X-Series Status Register System” on page 116). The second column in the
table below shows the corresponding bit in that register.
An event with the number shown in the table means the condition has been
detected. When the condition is cleared, an event with the number plus 1000
is generated. These error numbers can be viewed in the Show Errors screen,
along with the DETECTED and CLEARED indicators.
For example, message 72 indicates that the “Input Attenuation not calibrated”
condition has been detected, and message 1072 indicates that failure has
been cleared.
This register is summarized as bit 8 of the STATus:QUEStionable:CALibration
register, as described in the section “36 to 64, Calibration Needed or Failed” on
page 88.
Msg#Bit in
status
register
650unused
661Align 9kHz–30MHz requiredEAn EMI conducted frequency range
682Align 30MHz–1GHz requiredEAn EMI radiated frequency range
3
MessageError or
Warning
More Information
alignment is needed.
alignment is needed.
Instrument Messages 90
Page 91
Instrument Messages
Condition Messages
Msg#Bit in
status
register
724Input Attenuation not
745unused
766unused
787unused
808MPA Align requiredWEXT only
829unused
8410unused
8611Characterize Preselector
8812Characterize Noise Floor
9013unused
MessageError or
Warning
ECorrected measurements have been
calibrated
WAlign
required
W
required
More Information
requested and the required RF front-end
setting of x dB has not been calibrated.
9214unused
67 to 95, Calibration Failure (Extended)
This series of errors corresponds to the bits in the
STATus:QUEStionable:CALibration:EXTended:FAILure sub-register (see
“X-Series Status Register System” on page 116). The second column in the
table shows the corresponding bit in that register.
An event with the error number shown in the table means the condition has
been detected. When the condition is cleared, an event with the error number
plus 1000 is generated. These numbers can be viewed in the Show Errors
screen, along with the DETECTED and CLEARED indicators.
For example, error 71 indicates that the Characterize Preselector Failure has
been detected, error 1071 indicates that failure has been cleared.
This register is summarized as bit 9 of the STATus:QUEStionable:CALibration
register, as described in the section “36 to 64, Calibration Needed or Failed” on
page 88.
Err#Bit in
status
register
MessageError or
More Information
Warning
670Align 9kHz to 30MHz
failed
Instrument Messages 91
WOn PSA, this was error 13749
Page 92
Instrument Messages
Condition Messages
Err#Bit in
status
register
691Align 30MHz to 1GHz
712Characterize Preselector
733unused
754unused
775unused
796Align Source IQ failed WThe alignment of the built-in source IQ section
817Align Source RF failed WThe alignment of the built-in source RF
838MPA Align failedWMultiport adapter alignment failed, EXT only
859unused
8710unused
MessageError or
Warning
WOn PSA, this was error 13751
failed
WThe preselector characterization routine failed.
failure
More Information
failed (products with built-in sources only)
section failed (products with built-in sources
only)
8911unused
9112unused
9313unused
9514unused
101 to 199, Measurement Integrity
This series of errors corresponds to the bits in the
STATus:QUEStionable:INTegrity register (see “X-Series Status Register
System” on page 116). The second column in the table shows the
corresponding bit in that register.
An event with the number shown in the table means the condition has been
detected. When the condition is cleared, an event with the number plus 1000
is generated. These error numbers can be viewed in the Show Errors screen,
along with the DETECTED and CLEARED indicators.
For example, error 141 indicates an Input Overload condition has been
detected, error 1141 indicates that failure has been cleared.
Two bits in this register are “summary bits” for registers at a lower level. There
are no error messages associated with these bits; they exist only as status bits,
which can be read with a STATus:QUEStionable:INTegrity? event query or a
STATus:QUEStionable:INTegrity:CONDition? query.
Instrument Messages 92
Page 93
Instrument Messages
Condition Messages
Note that these summary bits summarize the state and history of the event
registers at the lower level. This is true even for bits in the
STATus:QUEStionable:INTegrity condition register. This means that:
— The summary bits read by the
STATus:QUEStionable:INTegrity:CONDition? query are true if any event
bits are set in any of the :INTegrity sub-registers :SIGNal or :UNCalibrated.
— The summary bits read by the STATus:QUEStionable:INTegrity? event
query are true if any event bit has undergone a false-to-true transition with
the PTRansition filter set, or a true-to-false transition with the NTRansition
filter set, in any of the :INTegrity sub-registers :SIGNal or :UNCalibrated
Thus, the summary bits cannot be used to determine the current state of a
lower level condition bit; only the state and history of the lower level event bits.
This register is itself summarized as bit 9 of the STATus:QUEStionable register,
as described in the section “601 to 699, Error Summaries” on page 109.
Err#Bit in
status
register
1330Signal SummaryStatus bit
1351No ResultE
1351No Result;Turn on MCEETo calculate Timing and Phase results
1351No Result; Meas invalid with I/Q
1351No Result;Meas/Radio Std
MessageError or
Warning
only
EThe current measurement does not
inputs
EThe current measurement is
incompatibility
More Information
This bit is the summary bit for the
STATus:QUEStionable:INTegrity:SIGN
al sub-register.
in the Code Domain Power view of
Mod Accuracy, the "Multi Channel
Estimator" must be set to ON.
Otherwise these results are invalid.
support I/Q input; switch to the RF or
another input or select a different
measurement
incompatible with the current Radio
Standard; change Radio Standard to
use this measurement
1372unused
1393Uncalibrated SummaryStatus bit
only
1414
Input Overload
Instrument Messages 93
a
E*
This bit is the summary bit for the
STATus:QUEStionable:INTegrity:UNCa
librated sub-register.
Page 94
Instrument Messages
Condition Messages
Err#Bit in
status
register
1414Input Overload;ADC over rangeE*The signal at the input to the IF
1414Input Overload;I/Q ADC over rangeE*The I or Q input exceeds the ADC
1414Input Overload;I/Q Voltage over
1414Input Overload;RF Preselector
1435Over RangeStatus Bit
MessageError or
Warning
E*The input voltage on the I or Q
range
E*The level at the input of the MXE RF
Overload
Only
More Information
section is too high. You should
increase the attenuation or lower the
signal level.
upper limit.
channel exceeds the channel limit. In
differential mode the over voltage may
occur without causing an ADC
overload, for example, if I is at +5.01 V
and I-bar is at +5.0 the ADC will be in
range but both I and I-bar will exceed
the voltage limit.
Preselector has exceeded tolerances,
reduce the input level
The signal at the input for this
measurement s too high. You should
increase the attenuation or decrease
the signal level.
1456Under RangeStatus Bit
Only
1477Insufficient DataE
1477Insufficient Data; Incr. Demod
Time
1477Insufficient Data; frequency list
empty
1477Insufficient Data; ENR table
empty
EThere is insufficient acquisition data to
EA measurement was attempted with
EA measurement was attempted or a
The signal at the input for this
measurement is too low. You should
decrease the attenuation or increase
the signal level.
provide accurate metrics. You should
increase the Demod Time to acquire
enough data.
List frequency mode or a SCPI query
of the frequency list table was made
and the frequency list table is empty.
SCPI query of an ENR table was made
and there were no entries in the
relevant ENR table (Common, Meas or
Cal).
Instrument Messages 94
Page 95
Instrument Messages
Condition Messages
Err#Bit in
status
register
1477Insufficient Data; Loss table
1477Insufficient Data; trigger
1498Meas Error
1498Meas Error; Power meter errorThe power meter has returned an
1519Memory ErrorE
MessageError or
Warning
EA measurement is attempted or a
empty
EIn PAvT measurement with Meas Type
received before current segment
is complete
More Information
SCPI query of a before or after loss
table is made and there are no entries
in the relevant loss table
of Triggered, a new trigger was
received before processing of the
current segment is complete. Shorten
Meas Offset + Meas Interval or
prevent trigger from occurring.
error. Details are in the error history.
This must be corrected so that the
measurement can complete
successfully.
1519Memory Error;Shorten capture
interval
15310I/O ErrorE
15310I/O Error; Ext Source needs IP
Addr
15511Trig ErrorE
15712Invalid DataStatus bit
15913Settings AlertW
EA shortage of free memory related to
ENo IP address entered for external
only
longer capture intervals has occurred.
The measurement is aborted and all
results return invalid values
source and external LO control is ON.
This is the “invalid data indicator”,
same as the “*” in the upper right
corner of the screen. It means that the
on-screen annotation does not match
the on-screen data, usually because a
measurement is pending after a
settings change. There is no message
in the status line and nothing in the
history queue, but there IS an
on-screen indication and a status bit.
Instrument Messages 95
Page 96
Instrument Messages
Condition Messages
Err#Bit in
status
register
15913Settings Alert;LO may overload IFWIf the sweep type is Swept, the start
15913Settings Alert; Diff probe
15913Settings Alert; Acquisition
MessageError or
Warning
WThe attenuation values of the two
mismatch; <I|Q|I,Q>
WIn the Analog Demod mode, certain
truncated
More Information
frequency of the instrument is less
than 10 MHz, and you put Swept IF
Gain in Manual High, then a warning
condition is generated and remains in
effect as long as this condition exists.
In some older analyzers this was error
1109.
probes on the I and/or Q channels
differ by too much for a valid
differential reading.
extreme settings combinations will
result in a required acquisition length
in excess of the capacity of the
analyzer.Increase the AF Spectrum
RBW or the RF Spectrum RBW,
decrease the Channel BW, and/or
decrease the Demod Waveform
Sweep Time.
15913Settings Alert; Analog Out
settings conflict
15913Settings Alert;I/Q
mismatch:<Differential|Input
Z|Attenuation>
15913Settings Alert;Parm/data
mismatch
15913Settings Alert;Src pwr ramp>ALC
range
WThe user has manually set the Analog
Output under the Input/Output menu
to a setting that conflicts with the
current measurement. There will be
no output on the Analog Out port until
this conflict is resolved. In most cases,
simply set Analog Out to Auto for the
optimal setting.
WThe impedance, differential, or
attenuation settings for the I and Q
channels do not match. For valid I+jQ
measurements the impedance and
differential settings should be the
same on both channels and the
attenuation should match within 1 dB
WFor Bluetooth, the detected
parameters did not match the data
WYou have chosen a Power Sweep
range that exceeds the ability of the
external Source to follow without
changing mechanical attenuation.
Lower your Power Sweep range.
Instrument Messages 96
Page 97
Instrument Messages
Condition Messages
Err#Bit in
status
register
15913Settings Alert;Sweep Rate
15913Settings Alert;Span:RBW Ratio too
15913Settings Alert;Freq>USB Preamp
MessageError or
Unavailable
big
max
More Information
Warning
WThe auto coupled sweep time exceeds
the maximum allowed. Therefore, full
amplitude accuracy cannot be
attained. Please increase the RBW or
reduce the span.
WThe chosen large ratio of span to RBW
is not possible. Please reduce the
span or increase the RBW and/or FFT
Width.
WThe highest analysis frequency
exceeds the frequency range of the
USB preamp used. In Noise Figure
measurement applications, this
situation will cause gradual
degradation of uncertainty with
increasing frequency. In Spectrum
Analyzer applications, this will cause
rapidly declining amplitude accuracy
with increasing frequency.
16114Setting ModifiedE
16114Setting Modified; Filter not
applied
EThe filter you have selected is larger
than the sampling frequency. You
should select a different filter.
a. The Input Overload error is not reported to the SCPI queue unless the :SYSTem:ERRor:OVERload ON
command has been issued, however it always sets the status bit.
201 to 299, Signal Integrity
This series of errors corresponds to the bits in the
STATus:QUEStionable:INTegrity:SIGNal sub-register (see “X-Series Status
Register System” on page 116). The second column in the table shows the
corresponding bit in that register.
An event with the number shown in the table means the condition has been
detected. When the condition is cleared, an event with the number plus 1000
is generated. These error numbers can be viewed in the Show Errors screen,
along with the DETECTED and CLEARED indicators.
For example, error 207 indicates a Burst Not Found condition has been
detected, error 1207 indicates that failure has been cleared.
Instrument Messages 97
Page 98
Instrument Messages
Condition Messages
This register is summarized as bit 0 of the STATus:QUEStionable:INTegrity
register, as described in the section “101 to 199, Measurement Integrity” on
page 92.
Err#Bit in
Status
Register
2030unused E
2051unusedE
MessageError or
More Information
Warning
Instrument Messages 98
Page 99
Instrument Messages
Condition Messages
Err#Bit in
Status
Register
2072Burst Not FoundEThe burst signal cannot be detected because
MessageError or
Warning
More Information
of inappropriate parameter settings or
incorrect signal content:
— An inappropriate parameter setting
could cause the signal to be
partially, rather than fully, on the
display, Burst Search Threshold
and/or Burst Search Length may
need to be adjusted.
— An incorrect signal could have
either insufficient power, the rising
or falling edges cannot be detected,
or the burst is less than
126microseconds.
— Carrier signal might not be actually
bursted.
W-CDMA: Either the signal being analyzed
has insufficient power, the rising or falling
edges cannot be detected, or the burst is less
than 126microseconds.
W_CDMA: Cannot synchronize measurement
with PRACH channel for Power Control
measurement, because the signal cannot be
found. Make sure PRACH is present in the
W-CDMA uplink signal, and that the preamble
signature and scramble code are set
correctly.
2072Burst not found;with
selected Time Slot
2093Timing ErrorE
Instrument Messages 99
GSM: Data was acquired but a GSM burst was
not found, with the timeslot mode disabled.
Bluetooth: The burst that has been found
does not correspond to the currently selected
Bluetooth packet type (the burst length may
be too short).
WLAN: The instrument cannot find a valid
WLAN burst. You may need to extend the
search length.
In the PSA, this error was reported as one of
the following error numbers: 10772, 13104,
10160, 10286, 10420, 10454, 10614, 10904,
10928, 13074, 10287
EThe selected timeslot does not contain the
expected burst.
Page 100
Instrument Messages
Condition Messages
Err#Bit in
Status
Register
2093Timing Error:No time
2114Carrier(s) incorrect or
2135Freq Out of RangeE
2135Freq Out of Range;
2135Freq Out of Range;
2156Sync ErrorEW-CDMA: Cannot sync DPCCH pilot.
MessageError or
Warning
EThe pilot burst used for time reference is not
ref pilot burst
EIn the PSA, this error was reported as one of
missing
EOne or more system input frequencies are out
System input (IF)
EOne or more external LO frequencies are out
External LO
More Information
active.
the following error numbers: 10165, 10173,
10178, 10419, 10421, 10535, 10560, 10642,
10648, 10650, 10960
of range. If using a frequency list, check that
all entries are valid for current measurement
mode.
of range. Check that the LO frequency limits
are set correctly and check the entered
measurement frequencies and measurement
mode.
Cannot synchronize measurement with
DPCCH pilot for Power Control measurement,
because the pilot signal cannot be found.
Make sure DPCCH is present in the W-CDMA
uplink signal, and that the slot format and
scramble code are set correctly.
2156Sync Error;No pilot
burst
2156Sync Error;Sync code
not found
2156Sync Error;No freq ref
pilot burst
2156Sync Error;Midamble
sync fail
2156Sync Error;Preamble
length zero
Instrument Messages 100
EThere is no Pilot burst detected.
ESynchronization code is not found in the
measured time slot.
EThe pilot burst used for frequency reference is
not active.
EFailed to find the uplink slot, which caused
the synchronization with the midamble to fail.
EBurst type is "Data" or "Preamble" and the
measurement cannot find a Preamble
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.