The information contained in this document is subject to change
without notice.
Agilent Technologies makes no warranty of any kind with regard to this
material, including but not limited to, the implied warranties of
merchantability and fitness for a particular purpose. Agilent
Technologies shall not be liable for errors contained herein or for
incidental or consequential damages in connection with the furnishing,
performance, or use of this material.
Where to Find the Latest Information
Documentation is updated periodically. For the latest information about
Agilent PSA or ESA spectrum analyzers, including firmware upgrades
and application information, please visit the following Internet URLs:
The analyzer can generate various messages that appear on the display during operation.
There are four types of messages.
This chapter describes the following types of messages displayed on the analyzer:
User Error
Messages
Informational
Messages
Status
Messages
Pop-up
Messages
Instrument Messages
Beginning on page 38, User Error Messages appear when an attempt has been
made to set a parameter incorrectly or an operation has failed (such as saving
a file). These messages are often generated during remote operation when an
invalid programming command has been entered. These messages appear in
the status line at the bottom of the display. If you are using the default display
colors, the message will appear in yellow. The message will remain until you
preset the analyzer, press
line.
Beginning on page 97, Informational Messages provide information that
requires intervention. These messages appear on the status line at the bottom
of the display. If you are using the default display colors, the message will
appear in green (ESA) or yellow (PSA). The message will remain until you
preset the analyzer, press
line. The information provided in brackets, for example <filename> or
<directory>, is a variable that represents a specific input provided previously.
Beginning on page 102, Status Messages appear on the right side of the
analyzer display and/or set status bits in the SCPI Status Register system.
These messages indicate a condition that may result in erroneous data being
displayed. Most messages will only be displayed until the error condition is
corrected. Multiple messages can be displayed and will be listed in the display
area. In each case the name of the corresponding status bit is indicated in
parenthesis. It will be noted if only a status bit is used (no message).
These messages indicate a condition that may require intervention. They
appear in the middle of the display in a framed box. The message will remain
until the appropriate intervention has taken place or the condition has been
corrected.
ESC, or another message is displayed on the status
ESC, or another message is displayed on the status
34Chapter 1
Page 35
Instrument Messages
Instrument Messages Introduction
Error Queues
There are two types of error queues, front panel and remote interface. These two queues
are viewed and managed separately. Refer to Table 1-1. for more information on the
characteristics of the Error Queue.
Front panel A summary of the last 11 error messages preceded by an error number
may be viewed in the Error Queue by pressing,
When a remote interface initiates activity that generates an error, the
messages are output to the remote bus. When output to the remote
interface, they are preceded by an error number.
Remote interface
(SCPI) When a user error condition occurs in the analyzer as a result of SCPI
(remote interface) activity, it is reported to both the front panel display
error queue and the SCPI error queue. If it is a result of front panel
activity, it reports to the front panel display error queue, and depending on
the error, may also report to the SCPI error queue.
Table 1-1. Characteristics of the Error Queue
System then Show Errors.
Characteristic
Capacity
(number of errors)
Overflow Handling
Viewing Entries
Clearing the Queue
Front-Panel Display
Error Queue
1130
Circular (rotating).
Drops oldest error as new error comes in.
Power up.
Send a *CLS command.
Read last item in the queue.
a. Error history includes the date and time an error last occurred, the error number,
the error message, and the number of times the error occurred.
Instrument Messages
Chapter 135
Page 36
Instrument Messages
Instrument Messages Introduction
Error Message Format
The system–defined error numbers are chosen on an enumerated (“1 of N”) basis. The error
messages are listed in numerical order according to the error message number. Status and
Informational messages without numbers will be listed in alphabetical order following the
numerical listing.
In this chapter, an explanation is included with each error to further clarify its meaning.
The last error described in each class (for example, –400, –300, –200, –100) is a “generic”
error. There are also references to the IEEE Standard 488.2-1992, IEEE Standard Codes, Formats, Protocols and Common Commands for Use with ANSI/IEEE Std 488.1-1987.
New York, NY, 1992.
Error messages are displayed at the bottom of the screen in the status line. If you are
using the default display colors, the message will appear in green (ESA) or yellow (PSA).
The error number is available through the remote interface and the show errors screen; it
is not displayed in the status line.
Figure 1-1. Error Message Example
Instrument Messages
36Chapter 1
Page 37
Instrument Messages
Instrument Messages Introduction
Error Message Types
Events do not generate more than one type of error. For example, an event that generates
a query error will not generate a device-specific, execution, or command error.
-499 to -400:
Query Errors
-399 to -300:
Device-Specific
Errors
-299 to -200:
Execution Errors
-199 to -100:
Command Errors
These errors indicate that the analyzer output queue control has detected a
problem with the message exchange protocol described in IEEE 488.2,
Chapter 6. Errors in this class set the query error bit (bit 2) in the event
status register (IEEE 488.2, section 11.5.1). These errors correspond to
message exchange protocol errors described in IEEE 488.2, 6.5. In this case:
• Either an attempt is being made to read data from the output queue when
no output is either present or pending, or
• Data in the output queue has been lost.
An error number in the range –399 to –300 indicates that the analyzer has
detected an error where some device operations did not properly complete,
possibly due to an abnormal hardware or firmware condition. This is not a
error in response to a SCPI query or command, or command execution. The
occurrence of any error in this class will cause the device-specific error bit
(bit 3) in the event status register to be set.
These errors indicate that an error has been detected during analyzer
execution.
These errors indicate that the analyzer parser detected an IEEE 488.2
syntax error. Errors in this class set the command error bit (bit 5) in the
event status register (IEEE 488.2, section 11.5.1). In this case:
• Either an IEEE 488.2 syntax error has been detected by the parser (a
control-to-device message was received that is in violation of the IEEE
488.2 standard. Possible violations include a data element which violates
device listening formats or whose type is unacceptable to the device.), or
Instrument Messages
64 to 799:
Device-Specific
Errors
Greater than
10000:
Measurement
Applications
Errors
• An unrecognized header was received. These include incorrect
device-specific headers and incorrect or unimplemented IEEE 488.2
common commands.
These errors indicate that a device operation did not properly complete,
possibly due to an abnormal hardware or firmware condition. These codes
are also used for self-test response errors. Errors in this class set the
device-specific error bit (bit 3) in the event status register (IEEE 488.2,
section 11.5.1).
The <error_message> string for a positive error is not part of the SCPI
standard. A positive error indicates that the analyzer detected an error
within the GPIB system, within the analyzer firmware or hardware, during
the transfer of block data, or during calibration.
These errors indicate that an error has been detected while executing
measurements requiring a personality option such as the GSM Measurement
Personality or those measurements found under the
key in SA mode.
Chapter 137
MEASURE front-panel
Page 38
Instrument Messages
Instrument Messages
Instrument Messages
Error Messages
NOTEError numbers are displayed in the error queue, not on the display.
To see an error number, press System, Show Errors.
0: No Error
0 No error
The queue is empty. Either every error in the queue has been read, or the
queue was cleared by power-on or *CLS.
−499 to −400: Query Errors
NOTEError numbers are displayed in the error queue, not on the display.
To see an error number, press System, Show Errors.
–440 Query UNTERMINATED after indefinite response
Indicates that a query was received in the same program message after a
query requesting an indefinite response was executed (see IEEE 488.2,
6.3.7.5).
–430 Query DEADLOCKED
Indicates that a condition causing a DEADLOCKED query error occurred
Instrument Messages
–420 Query UNTERMINATED
(see IEEE 488.2, 6.3.1.7). 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.
Indicates that a condition causing an UNTERMINATED query error
occurred (see IEEE 488.2, 6.3.2.2). For example, the device was addressed
to talk and an incomplete program message was received.
–410 Query INTERRUPTED
Indicates that a condition causing an INTERRUPTED query error
occurred (see IEEE 488.2, 6.3.2.7). For example, a query was followed by
DAB or GET before a response was completely sent.
38Chapter 1
Page 39
Instrument Messages
Instrument Messages
−400 Query Error
This is a generic query error for devices that cannot detect more specific
errors. The code indicates only that a query error as defined in IEEE
488.2, 11.5.1.1.7 and 6.3 has occurred.
−399 to −300: Device-Specific Errors
NOTEError numbers are displayed in the error queue, not on the display.
To see an error number, press System, Show Errors.
−340 Calibration failed
The instrument requires an
pressing
System, Alignments, Align All Now.
Align All Now. Restore the alignment by
−330 Self-test failed;
EEPROM checksum for <card>
The card identification header for a hardware card is incorrect. If the card
is not properly identified, the instrument is likely to be non-functional.
Report this error to the nearest Agilent Technologies sales or service office.
−330 Self-test failed;
Incompatible Hardware (Third Converter) for E4
(E4447A only) The instrument has detected an incompatible Third
Converter board. The upper-most frequency will be limited to 26.5 GHz,
but the instrument will otherwise continue to function normally.
−321 Out of memory
An internal operation needed more memory than was available. Report
this error to the nearest Agilent Technologies sales or service office.
−310 System error; Pretune DAC Calibration failed
System error; Pretune DAC Cal failed midpoint verification
System error
Instrument Messages
An internal system problem was detected. Report this error to the nearest
Agilent Technologies sales or service office.
−300 Device-specific error
This is a generic device-dependent error for devices that cannot detect
more specific errors. The code indicates only that a device-dependent error
as defined in IEEE 488.2, 11.5.1.1.6 has occurred. Report this error to the
nearest Agilent Technologies sales or service office.
Chapter 139
Page 40
Instrument Messages
Instrument Messages
−299 to −200: Execution Errors
NOTEError numbers are displayed in the error queue, not on the display.
To see an error number, press System, Show Errors.
−253 Corrupt media
A removable media was found to be bad or incorrectly formatted. Any
existing data on the media may have been lost.
−250 Mass storage error; EEPROM write timeout on EEPROM
Failure to initialize EEPROM. Report this error to the nearest Agilent
Technologies sales or service office.
−241 Hardware missing
Hardware missing; no such SIO address
Missing device hardware. For example, an option is not installed.
−230 Data corrupt or stale
Data corrupt or stale; EEPROM copy of <file>
Data corrupt or stale; NRAM copy of <file>
Possibly invalid data. A new measurement was started but not completed.
−224 Illegal parameter value
You have sent a parameter for this command that is not allowed. See the
Function Reference.
−223 Too much data; not all points entered
Too much data; <description of the type of data exceeded>
Indicates that a legal program data element of block, expression, or string
Instrument Messages
type was received that contained more data than the device could handle
due to memory or related device-specific requirements.
−222 Data out of range
A legal program data element was parsed but could not be executed
because the interpreted value was outside the legal range defined by the
device (see IEEE 488.2 11.5.1.1.5). The displayed results may be clipped.
40Chapter 1
Page 41
−221 Settings conflict;…
…Averaging unavailable when Sig ID is on
When in external mixing, with signal identification on, Averaging
Mode is not available as a selection.
…Cannot center unpreselected external mixer
Mixer type is Unpreselected. Preselector centering is not available for
unpreselected mixers.
…Command incompatible with band pair marker
Using remote commands, you have tried to adjust the start or stop
frequency of a span pair marker. You can adjust only the center and
span.
…External mixing unavailable when preamp on
Internal preamp is on and you tried to select external mixing, which is
not available.
Instrument Messages
Instrument Messages
…FFT unavailable when Sig ID is on
When in external mixing, with signal identification on, the Manual
FFT function is not available as a selection
…Settings Conflict, Preamp unavailable in external mixing
mode
With external mixing selected, you cannot use the internal preamp.
…Sig ID requires EXTERNAL mixing mode
The Input Mixer setting is set in internal and you tried to select signal
identification which is not valid.
…Sig ID unavailable in Manual:FFT
When in external mixing, with FFT on, signal identification is not
available as a selection.
…Sig ID unavailable when Averaging is on
When in external mixing, with Averaging Mode on, signal
identification is not available as a selection.
…Sig ID unavailable when Signal Track is on
When in external mixing with signal tracking on, signal identification
is not available as a selection.
Instrument Messages
Chapter 141
Page 42
Instrument Messages
Instrument Messages
…Signal ID unavailable with Presel Mixer
Signal identification is not available with the preselected mixer
selected.
…Signal Track unavailable when Sig ID is on
Signal tracking is not available as a selection when using external
mixing with signal identification on.
Settings conflict; parameter currently disabled
This parameter is grayed out (unavailable) in the current context. Check
the individual parameter help/documentation for more information.
−200 Execution Error
For devices that cannot detect more specific errors, this code indicates only
that an execution error as defined in IEEE 488.2, 11.5.1.1.5 has occurred.
−199 to −100: Command Errors
NOTEError numbers are displayed in the error queue, not on the display.
To see an error number, press System, Show Errors.
–178 Expression data not allowed
A legal expression data was encountered, but was not allowed by the
device at this point in parsing.
–171 Invalid expression
The expression data element was invalid (see IEEE 488.2, 7.7.7.2). For
example, unmatched parentheses or an illegal character.
–170 Expression data error
This error, as well as errors –171 through –179, is generated when parsing
Instrument Messages
an expression data element. This particular error message is used if the
device cannot detect a more specific error.
–168 Block data not allowed
A legal block data element was encountered, but not allowed by the device
at this point in the parsing.
–161 Invalid block data
A block data element was expected, but was invalid (see IEEE 488.2,
7.7.6.2). For example, an END message was received before the end length
was satisfied.
42Chapter 1
Page 43
–160 Block data error
This error, as well as errors –161 through –169, is generated when parsing
a block data element. This particular error message is used if the device
cannot detect a more specific error.
–158 String data not allowed
A string data element was encountered, but not allowed by the device at
this point in the parsing.
–151 Invalid string data
A string data element was expected, but was invalid (see IEEE 488.2,
7.7.5.2). For example, an END message was received before the terminal
quote character.
–150 String data error
This error, as well as errors –151 through –159, is generated when parsing
a string data element. This particular error message is used if the device
cannot detect a more specific error.
Instrument Messages
Instrument Messages
–148 Character data not allowed
A legal character data element was encountered where prohibited by the
device.
–144 Character data too long
The character data element contains more than twelve characters (see
IEEE 488.2, 7.7.1.4).
–141 Invalid character data
Either the character data element contains an invalid character or the
particular element received is not valid for the header.
–140 Character data error
This error, as well as errors –141 through –149, is generated when parsing
a character data element. This particular error message is used if the
device cannot detect a more specific error.
–138 Suffix not allowed
A suffix was encountered after a numeric element which does not allow
suffixes.
–134 Suffix too long
Instrument Messages
The suffix contained more than twelve characters (see IEEE 488.2,
7.7.3.4).
Chapter 143
Page 44
Instrument Messages
Instrument Messages
–131 Invalid suffix
Attempt to send a SCPI command with a suffix that does not match the
current units for the function.
The suffix does not follow the syntax described in IEEE 488.2, 7.7.3.2, or
the suffix is inappropriate for this device.
–130 Suffix error
This error, as well as errors –131 through –139, is generated when parsing
a suffix. This particular error message is used if the device cannot detect a
more specific error.
–128 Numeric data not allowed
A legal numeric data element was received, but the device does not accept
one in this position for the header.
–124 Too many digits
The mantissa of a decimal-numeric data element contained more than 255
digits excluding leading zeros (see IEEE 488.2, 7.7.2.4.1).
–123 Exponent too large
The magnitude of an exponent was greater than 32000 (see IEEE 488.2,
7.7.2.4.1).
–121 Invalid character in number
An invalid character for the data type being parsed was encountered. For
example, an alpha in a decimal numeric or a “9” in octal data.
−120 Numeric data error; VGR
Numeric data error
This error, and errors −121 through −129, is generated when parsing a
data element that appears to be numeric, including non-decimal numeric
Instrument Messages
types. This message is used if the device cannot detect a more specific
error.
–114 Header suffix out of range
The value of a header suffix attached to a program mnemonic makes the
header invalid.
–113 Undefined header
The header is syntactically correct, but it is undefined for this specific
device. For example, *XYZ is not defined for any device.
–112 Program mnemonic too long
The header contains more than twelve characters (see IEEE 488.2,
7.6.1.4.1).
44Chapter 1
Page 45
–111 Header separator error
A character which is not a legal header separator was encountered while
parsing the header.
–110 Command header error
An error was detected in the header. This message is used when the device
cannot detect the more specific errors described for errors –111 through
–119.
–109 Missing parameter
Fewer parameters were received than required for the header. For
example, the *ESE common command requires one parameter, so receiving
*ESE is not allowed.
–108 Parameter not allowed
More parameters were received than expected for the header. For example,
the *ESE common command only accepts one parameter, so receiving *ESE 0,1 is not allowed.
Instrument Messages
Instrument Messages
–105 GET not allowed
A Group Execute Trigger was received within a program message (see
IEEE 488.2, 7.7). Correct the GPIB controller program so that the GET does
not occur within a line of GPIB program code.
–104 Data type error
The parser recognized a data element that is not allowed. For example,
numeric or string data was expected, but block data was encountered.
–103 Invalid separator
The parser was expecting a separator and encountered an illegal
character. For example, the semicolon was omitted after a program
message unit.
–102 Syntax error
An unrecognized command or data type was encountered. For example, a
string was received when the device does not accept strings.
–101 Invalid character
A syntactic command contains a character which is invalid for that type.
For example, a header containing an ampersand, such as “SETUP&”. This
error might be used in place of error numbers –114, –121, –141, and some
others.
Instrument Messages
Chapter 145
Page 46
Instrument Messages
Instrument Messages
−100 Command error
This is a generic syntax error for devices that cannot detect more specific
errors. The code indicates only that a command error as defined in
IEEE 488.2, 11.5.1.1.4 has occurred.
64 to 799: Device-Specific Errors
64 System, Alignments, Align All Now, Needed
102 Excessive 50 MHz RF input power is preventing internal
alignments.
There is too much 50 MHz energy at the RF port for alignments to run.
Reduce input power to less than 0 dBm and run alignments again.
103 Sampling Oscillator Unlock; Failure acquiring SO frequency
lock
Report this error to the nearest Agilent Technologies sales or service office.
104 1st LO Unlock; Failure acquiring FracN LO frequency lock
1st LO Unlock; Failure acquiring single loop FracN LO lock
The first LO on has lost phase lock. Report this error to the nearest Agilent
Technologies sales or service office.
105 2nd LO Unlock
The second LO has lost phase lock. Report this error to the nearest Agilent
Technologies sales or service office.
106 4th LO Unlock
The fourth LO has lost phase lock. Report this error to the nearest Agilent
Technologies sales or service office.
Instrument Messages
107 Sample Clock Unlock
Report this error to the nearest Agilent Technologies sales or service office.
108 ESA Cal Oscillator Unlock
Report this error to the nearest Agilent Technologies sales or service office.
108 PSA Parameter not allowed
This error appears when POW:GAIN? is issued with parameters. The
POW:GAIN? command to query the state of the preamplifier does not
accept parameters.
109 Missing Parameter
A necessary parameter was not provided in the command that was sent.
46Chapter 1
Page 47
Instrument Messages
Instrument Messages
129 Meas Uncal
The measurement is uncalibrated, usually due to sweeping a narrow RBW
filter too quickly. Check the sweep time, span, and bandwidth settings, or
Auto Couple.
press
143 Final IF Overload
Either increase input attenuation or decrease the input signal level.
163 Freq Count: Reduce Span/RBW ratio
The span is too wide for the current resolution bandwidth. Either reduce
the span or increase the RBW.
177 Diagnostic override of Firmware Control; :DIAGnostic:ABUS
Diagnostic override of Firmware Control; :DIAGnostic:AMP
Diagnostic override of Firmware Control; :DIAGnostic:LATCh
Diagnostic override of Firmware Control; :DIAGnostic:MLATCh
Diagnostic override of Firmware
Control; :DIAGnostic:REGister:VALue
Diagnostic override of Firmware Control; :DIAGnostic:SBUS
Diagnostic override of Firmware Control; :DIAGnostic:SBUS:DBD
Diagnostic override of Firmware
Control; :DIAGnostic:SIO:PARallel
Diagnostic override of Firmware
Control; :DIAGnostic:SIO:SERial
187 Directory already exists
190 Unable to save file, invalid path
191 File Operation Status; directory <name> created
File Operation Status; <name> directory deleted
File Operation Status; <name> directory renamed to <name>
File Operation Status; <name> file copied
File Operation Status; <name> file deleted
File Operation Status; <name> file loaded
File Operation Status; <name> file renamed to <name>
File Operation Status; <name> file saved
Instrument Messages
File Operation Status; Volume <name> formatted
196 Can’t Auto-Couple Sweep Time in Zero Span
Chapter 147
Page 48
Instrument Messages
Instrument Messages
197 Marker Freq Count HW Failure
201 Option not installed
The desired operation cannot be performed because a required option is
not installed. For example, pressing
installed in the ESA analyzer, or issuing a POW:GAIN command without
Option 1DS or 110 installed in the PSA analyzer will generate this error.
202 No peak found
Source with no tracking generator
No signal peak was found that meets the criteria under
Search Param Criteria.
Peak Search,
204 ESA only TG Frequency Limit
The tracking generator has reached the limit of its allowable frequency
range.
205 Ext Ref
205 Command not recognized
Indicates that the command sent from the remote interface was not
recognized. Check the programming guide for correct syntax.
206 Unable to initialize flatness data
A failure occurred in setting the flatness data in the internal EEROM. Get
in touch with your local Agilent Technologies sales and service office.
207 Unable to store flatness data
A failure occurred in setting the flatness data in the internal EEROM. Get
in touch with your local Agilent Technologies sales and service office.
208 Preselector is not available at this frequency.
A preselector is available, but the marker is at a frequency which does not
support preselection (~<3 GHz). Preselector centering can be performed
Instrument Messages
only for frequencies above 3.025 GHz.
209 Preselector centering failed
An attempt to center the preselector failed. You tried to center the
preselector with the analyzer span too wide. Preselector centering can be
performed only for spans below 1.123 GHz.
211 RBW limited to 1 kHz when Span > 5 MHz
In spans greater than 5 MHz, narrow (digital) resolution bandwidths,
below 1 kHz, are not available.
213 Span limited to 5 MHz when RBW < 1 kHz
In narrow (digital) resolution bandwidths, below 1 kHz, spans greater
than 5 MHz are not available.
48Chapter 1
Page 49
214 ESA only TG start freq is less than 9 kHz
Tracking generator uncalibrated below 9 kHz.
215 ESA only TG start freq is less than 1/2 res bw
Tracking generator uncalibrated at start frequencies below 1/2 the current
resolution bandwidth.
216 Invalid Baud Rate
Attempt to use invalid baud rate. Refer to the programming language
chapter of Agilent Technologies ESA Series Spectrum Analyzer Programmer’s Guide for more information.
217 RS-232 Interface Error
An error occurred on the serial interface.
219 Command not valid in this model
Indicates that the command sent from the remote interface does not apply
to this analyzer model number. For example, attempting to center the
preselector in an analyzer without a preselector will generate this error.
Instrument Messages
Instrument Messages
220 Trace Menu is unavailable when Sig Ident is ON
221 Invalid option, unable to uninstall package
You have attempted to remove a personality that is not currently installed.
Verify command was entered correctly.
222 Command not valid when no measurement is active
Indicates that the command sent from the remote interface must be issued
while a measurement is running in the analyzer.
223 Neg. Trig Delay unavailable in Swept Mode, zero delay used.
Trigger Offset unavailable in swept spans
Trigger Offset is only available in Zero Span. Refer to “Trig” in your
Agilent Spectrum Analyzer User’s Guide for a description of this function.
224 Option not licensed.
The selected option requires a license. Refer to the installation procedures
in the user guide provided for this particular option.
The microwave preselector has been bypassed so it cannot be centered or
adjusted. Pressing the key or send the SCPI commands for
Presel Adjust will result in this error.
Presel Center or
230 Unpreselected external mixing - no preselector
If you are using an unpreselected mixer while doing external mixing then
there is no preselector to center or adjust. Pressing the key or sending the
SCPI commands for
Presel Center or Presel Adjust will result in this error.
231 Preselector unavailable while in external mixing
The internal preselectors cannot be used while in external mixing.
232 External mixing is off, can’t adjust external preselector
External mixing is turned off so the external mixer preselector is not
available.
The millimeter wave preselector has been bypassed so it cannot be
centered or adjusted. Pressing the key or send the SCPI commands for
Presel Center or Presel Adjust will result in this error.
236 PSA License conflict: Options X and Y can not be licensed at same
time
This error is generated if you attempt to license two incompatible options
together in the analyzer. For example, Options 115 and 117 are
incompatible and will generate this error if both are licensed. The “X” and
“Y” in this message are replaced with the actual options.
238 Trace smoothing: VBW filt or Average Detector; cannot use both
239 HW Diag is OFF
249 AC Coupled
Instrument Messages
332 Average Type incompatible for scale.
Amplitude Scale command should be sent prior to the Average Type
command.
601 PSA only
612 ESA only File not found
The analyzer could not find the specified file.
601 Floppy disk full
The floppy disk is full. Clear some space by deleting unwanted files.
50Chapter 1
Page 51
602 PSA only
605 ESA only Media is protected
A save was attempted to a write-protected device.
602 Floppy disk error
An unknown error has occurred while accessing the floppy disk.
603 PSA only
615 ESA only File is corrupt
Corrupted file
The file that you were trying to load is corrupt.
604 PSA only
607 ESA only File name error
File name error; Directory does not have a default file type
File name error; Directory does not support extenders
File name error; Empty filename
Instrument Messages
Instrument Messages
File name error; Illegal extender
File name error; Illegal filename character
File name error; Only one: is allowed
File name error; Only one extender character allowed
An invalid file name was specified. Use filenames with a maximum of 8
characters (letters and digits only), and use a 3-character extension. File
names are not case-sensitive. This error also occurs if you try to delete a
nonexistent file.
615 PSA only
604 ESA only File exists
File already exists
You attempted to save to a file that already exists. Either delete or rename
the existing file or select a new name, then try again.
602 PSA only
605 ESA only Media is protected
A save was attempted to a write-protected device.
Instrument Messages
Chapter 151
Page 52
Instrument Messages
Instrument Messages
605 Data corrupt or stale; EEPROM copy of <file>
WAR NING: Contact the factory if you see this error.
This error indicates that a file stored in EEPROM has become corrupt and
the Hamming codes are unable to repair the data.
When the EEPROM file has been corrupted, the system will store default
values into both the Non-Volatile RAM and EEPROM copies of the file. If
this error occurs often, it may indicate that there is a problem with the
physical memory.
Data corrupt or stale; RAM copy of <file>
This error indicates that a file stored in Non-Volatile RAM has become
corrupt and the Hamming codes are unable to repair the data.
When a Non-Volatile file has this error, the system will first try to verify
the state of the data in EEPROM and if valid it will copy the data in
EEPROM into the Non-Volatile ram copy of the file. When this happens,
the system will remain calibrated. If this error occurs often, it may
indicate that there is a problem with the physical memory.
606 Data questionable; EEPROM copy of <file>
EEPROM error occurred. The EEPROM copy of an internal file is either
corrupt or otherwise unusable. The system automatically updates the
non-volatile RAM copy of the EEPROM copy using a default initialization.
The actual EEPROM file is left as it is. Report this error to the nearest
Agilent Technologies sales or service office.
606 Media is corrupt
A save was attempted to a corrupt device.
604 PSA only
607 ESA only File name error
File name error; Directory does not have a default file type
Instrument Messages
File name error; Directory does not support extenders
File name error; Empty filename
File name error; Illegal extender
File name error; Illegal filename character
File name error; Only one: is allowed
File name error; Only one extender character allowed
An invalid file name was specified. Use filenames with a maximum of 8
characters (letters and digits only), and use a 3-character extension. File
names are not case-sensitive. This error also occurs if you try to delete a
nonexistent file.
608 Mass storage error; EEPROM write timeout
52Chapter 1
Page 53
609 Restoration of NVRAM data
This error indicates that a file stored in Non-Volatile RAM has been
corrected based on the Hamming codes stored with the file. After the
correction, the file will contain the same data as when the instrument was
shut off. If this error continues to occur on successive power cycles, it may
indicate that there is a problem with the physical memory.
627 PSA only
609 ESA only Media is not writable
A save was attempted to a read-only device or device that could not be
written to. Try a known-good disk.
610 File access is denied
The file is protected or hidden and cannot be accessed.
611 File access IO busy;
duplicate :SERVice[:PRODuction]:CALibrate:BEGin
File access IO busy; :SERVice[:PRODuction]:CALibrate:END
without a BEGin
Instrument Messages
Instrument Messages
601 PSA only
612 ESA only File not found
The analyzer could not find the specified file.
613 Flash memory is full
The internal flash memory is full. Clear some space by deleting unwanted
files. If your analyzer has a serial number less than US41440000 or
MY41440000 and Option B72 has not been installed, you may also
increase the flash memory size by purchasing Option B72.
763 PSA only
614 ESA only Bad, missing, or unformatted disk
Bad or missing floppy disk
The floppy disk is not inserted properly, is not formatted, or the directory
cannot be read. Insert a known good disk and try again.
615 PSA only
604 ESA only File already exists
File exists
You attempted to save to a file that already exists. Either delete or rename
the existing file or select a new name, then try again.
Instrument Messages
Chapter 153
Page 54
Instrument Messages
Instrument Messages
603 PSA only
615 ESA only File is corrupt
Corrupted file
The file that you were trying to load is corrupt.
617 Wrong density floppy inserted
The floppy disk has the wrong density. It should be 1.44 MB.
618 Illegal write access of Flash memory
Attempt to write to an unavailable area of internal flash memory.
619 Can’t Auto-Couple RBW in Zero Span
You sent a remote command to set the RBW into auto while in zero span.
620 Can’t Auto-Couple Sweep Time in Zero Span
You sent a remote command to set the sweep time to auto while in zero
span.
622 External reference missing or out of range
The external frequency reference signal is missing, has too low an
amplitude, or does not match the frequency value that you previously
entered into instrument memory.
623 Printer not responding
Printer not responding; ioctl ERROR
Check the printer. It may not be connected properly or turned on.
Print failed; DisplayExport illegal print language
Print failed; DisplayExport insufficient RAM space
Print failed; DisplayExport undetermined error
Print failed; Error transferring image to printer
Print failed; Printer ioctl failed
Print failed; Unknown printer response
54Chapter 1
Page 55
Instrument Messages
Instrument Messages
627 PSA only
609 ESA only Media is not writable
A save was attempted to a read-only device or device that could not be
written to. Try a known-good disk.
ERROR/NUMBER “609 Restoration of NVRAM data” IS ALREADY
USED FOR HAPPENING ./storage/directory/NRAM_Directory.cc
HAP_nramDataCorrected
651 Connect RF OUT to INPUT
Attempt to align the tracking generator without its output connected.
Connect the tracking generator RF OUT to the analyzer
INPUT.
652 Connect Amptd Ref Output to Input
For Agilent Technologies E4402B, E4403B, E4404B, E4405B, E4407B, and
E4408B only: you must connect the
INPUT with the appropriate cable.
AMPTD REF OUTPUT to the analyzer
653 Auto Align not available when using Calibration Defaults
The Auto Alignment system cannot be used until an
executed by pressing
System, Alignments, Align Now, All. On all Agilent
Technologies ESA spectrum analyzer models except Agilent Technologies
E4401B and E4411B, you must connect the
with the appropriate cable to perform this alignment. For Agilent Technologies E4401B and E4411B only: disconnect any signals from the
INPUT prior to performing this procedure.
701 Invalid printer response
In attempting to identify the printer an invalid response was received.
Check that you are using a supported printer. Be sure you are using the
proper cable and that it is securely fastened.
702 Unsupported printer
A printer which is recognized, but known to be unsupported was
identified. This printer cannot be used with the analyzer. For example, a
printer only supported by Microsoft Windows will generate this error.
703 Unknown printer
In attempting to identify the printer, a valid response was received but the
printer is not known to the analyzer. Use the
Print Setup to configure the printer.
Align Now All is
AMPTD REF OUT to the INPUT
Instrument Messages
Custom printer menu under
704 Printer interface error
An error occurred while trying to print. Make sure the printer is turned on
and properly connected.
Chapter 155
Page 56
Instrument Messages
Instrument Messages
705 Printer Type is None
The current printer type is set to
Change the type in the
Print Setup menu and try again.
None, so no print operations are possible.
727 In <filename>: [DATA] header missing
This message indicates that the data section of a file did not begin with the
token [
DATA].
728 In <filename>, line <nnn>: separator missing
The [HEADER] section of a file contains entries requiring an equal (=) sign,
such as <keyword> = <value>. This message appears if the equal sign does
not appear on the line.
729 In <filename>: error reading file
Appears when loading data from a limit line or corrections disk file and a
failure to the file occurs.
730 In <filename>, line <numeric_value>: line too long
When loading data from a limit line or corrections disk file, this message
will appear if the length of any line in the file exceeds 255 characters.
731 In <command>: bad data count (<numeric_value>): expected
multiple of <numeric_value>
This message indicates that the data sent to a corrections or limit table via
the
DATA or MERGE commands does not have the expected length for the
table. For example, this message would appear if an attempt were made to
merge 7 numeric values into a limit table, since each logical entry requires
3 values (frequency, amplitude, and connected).
732 In <filename>, line <numeric_value>: error parsing tokens
This message may appear when loading data from a limit line or
corrections disk file. It indicates a problem in the attempt to break a string
Instrument Messages
of text into tokens. There may be too few tokens in the string. In other
words, the file content must match the expected format. This typically
happens when there are too few numeric values in the [
DATA] section of a
limit or corrections file.
733 In <filename>, line <numeric_value>: <xxx> is not numeric
This message may appear when loading data from a limit line or
corrections disk file. It indicates that a non-numeric token <xxx> was
found where a numeric token was expected. In other words, the file
content must match the expected format.
56Chapter 1
Page 57
734 Interpolation error: cannot compute log of
<negative_frequency_value>
Occurs when the frequency interpolation of a limit line is set to log and the
start frequency of the instrument is negative. The
<negative_frequency_value> is limited to
– 80 MHz, so it may not match the frequency that caused the error.
735 In <filename>: bad amplitude unit <unit>
This message indicates that unit <unit> is not recognized or supported.
736 Too many data values at <freq_or_time_value>
This message may appear when data is sent to a corrections or limit table
using the
DATA or MERGE commands. These tables limit the number of
amplitudes associated with a frequency or time to 2 or less. This message
will appear if an attempt is made to attach 3 or more values to a frequency
or time.
751 Instrument state set to initial values
Instrument state may be corrupt, state has been reset to
initial values
Instrument Messages
Instrument Messages
While trying to load a trace or state, the state information was found to be
in error. This may be because the state had been stored on a later revision
of analyzer firmware. A default set of state variables was loaded instead.
There is nothing wrong with the analyzer.
An error in the internal instrument state has been detected. The state has
been reset to a default value.
752 Unable to load state from file
Attempt to load a state from a file failed.
753 Unable to save state to file
Attempt to save a state to a file failed. See the associated error messages
for the cause (press
System, Show Errors).
For PSA: If this error occurs after a mode switch that takes longer then
normal, you may need to free up some instrument memory. When you
switch to a different measurement mode, the analyzer must temporarily
store instrument state data. If you have less then 500 kB of available
memory, the switching process can take over 1 minute and result in this
error. Use the File key menu to delete any unnecessary files from
instrument memory.
755 Unable to load state from register
Instrument Messages
Attempt to load a state from an internal state register failed.
Chapter 157
Page 58
Instrument Messages
Instrument Messages
756 Unable to save state to register
Attempt to save a state to an internal state register failed. See the
associated error messages for the cause (press
System, Show Errors).
757 Unable to load user state, factory preset was done
A user preset failed, so the factory preset values were used. Save a valid
state into user preset and try again.
758 Unable to save user state
Attempt to save a user preset state failed. See the associated error
messages for the cause (press
System, Show Errors).
759 Unable to load state saved from firmware Rev A.xx.xx; Restore
Sys\nDefaults
Unable to load state
A saved state file from a newer firmware revision was attempted to be
loaded into an older instrument.
760 ESA only Unable to query state
Query of state over the remote interface was unsuccessful.
761 ESA only Unable to set state
Attempt to set the state over the remote interface was unsuccessful.
762 ESA only Incorrect filename, allowable extensions are .trc or .csv
Attempt to save a trace to a file with an incorrect extension.
762 ESA only Unable to load file
A failure occurred while loading a file; the file was not loaded.
763 PSA only
614 ESA only Bad, missing, or unformatted disk
Instrument Messages
Bad or missing floppy disk
The floppy disk is not inserted properly, is not formatted, or the directory
cannot be read. Insert a known good disk and try again.
763 ESA only Incorrect filename, allowable extensions are .gif or .wmf
Attempt to save a screen image to a file with an incorrect extension.
764 Unable to save file
Attempt to save a file failed; the file was not saved. See the associated
error messages for the cause (press
58Chapter 1
System, Show Errors).
Page 59
Instrument Messages
Instrument Messages
765 Unable to load file
Attempt to load a file failed; the file was not loaded.
766 Unable to format drive
767 Failed to Initialize ISTATE regions. Fatal LDS error
Attempt to initialize the instrument state has failed. Cycle instrument
power. If this fails to correct the problem, contact your nearest Agilent
Technologies service center.
768 Unable to load user state, required instrument mode is not
installed
Attempt to load a state failed, because the state was saved with a
measurement personality that is not currently loaded. Load the
appropriate personality and try again.
769 ESA only Invalid instrument mode
You have attempted to switch to an instrument mode that is currently not
installed. Confirm that the mode name (for INST:SEL) or number (for
INST:NSEL) was entered correctly and that the requested personality is
actually installed in the instrument.
770 Incorrect filename, allowable extensions are .gif or .wmf
You sent a remote command to save a screen file but did not specify a valid
extension.
Incorrect filename, allowable extension is .sta
You sent a remote command to save a state file but did not specify a valid
extension.
Incorrect filename, allowable extensions are .trc or .csv
You sent a remote command to save a trace file but did not specify a valid
extension.
770 Instrument mode requested is not supported
Instrument mode specified with: INST command is not valid. Refer to
programming information.
771 Store Ref trace before turning on Normalize
Attempt to turn on Normalize with trace 3 being at the noise floor (PSA). A
reference trace must be available for the Normalize function to be
activated. Refer to “View/Trace” in the Agilent ESA Spectrum Analyzer
User’s Guide where the
Normalize key function is explained in detail.
Instrument Messages
Chapter 159
Page 60
Instrument Messages
Instrument Messages
772 Cannot load a directory
Cannot load a directory, please choose a file
You have selected a directory instead of a file when attempting to perform
the Load function under the
File front-panel key.
773 Linear units unavailable with Normalize on
Attempt to change amplitude units to an absolute unit which is
not allowed with Normalize.
774 Linear scale unavailable with Normalize on
Attempt to change Scale Type to LIN which is not allowed with
Normalize.
780 No Peak Found
No signal peak was found that meets the criteria under
Search Param Criteria.
Peak Search,
781 Video Trigger cannot be active with Average Detector
You sent a remote command to do one of the following:
• Turn on video trigger while the Average Detector or a Marker Function
is active.
• Turn on the Average Detector or a Marker Function while Video Trigger
is active.
782 Video Trigger cannot be used with Mkr Func due to Average
Detector
783 Allowable span for current center frequency exceeded
When rotating the knob or step up/down keys to change the Span, the
value of the Center frequency is kept constant. Therefor, the span is
limited by the frequency range of the instrument.
Instrument Messages
784 Allowable CF for current span exceeded
When rotating the knob or step up/down keys to change the Center
frequency, the value of the Span is kept constant. Therefor, the center
frequency is limited by the frequency range of the instrument.
786 Cal file not initialized correctly, <filenumber>
This indicates that an older LO board is loaded in, with uninitialized
values for the milli-meter band edges in it's EEPROM band edge cal file.
This happening is will therefore only be visible in the service mode.
60Chapter 1
Page 61
787 WBIF Self Test Failed
Option 122 or 140 performs a loop-back self-test on power up. It does an
ADC image calibration, then stores a sine wave in RAM and plays it out
the DAC. It then measures the carrier power, image rejection and
signal-to-noise ratio. If this test fails, the wideband digitizer hardware is
either incorrectly installed or has a hardware failure. Call your Agilent
Service representative.
There is diagnostic information available. The self test can be run with
DIAG:WBIF:TEST? This command returns 4 values: passed, carrier
power, image rejection and signal to noise ratio.
First look at the carrier power. If it is below –50, the LVDS cable is
probably missing or faulty. If the carrier power is above 0 dBm, image
rejection less than 40 but SNR more than 50, there is probably a bad ADC.
788 WBIF ADC Image Calibration Failed
The wideband digitizer hardware uses two ADC's that must be kept in
perfect synchronization to avoid unwanted images appearing in the
spectrum. The instrument will occasionally perform an ADC Image
Calibration (formerly known as Step Cal) to resynchronize the ADC's. This
calibration is only known to fail if there is a hardware problem.
Instrument Messages
Instrument Messages
789 WBIF Firmware Reset
The wideband digitizer hardware has a local microprocessor controlling
the hardware trigger. If this microprocessor resets, it will automatically
restart and begin taking data again, and will send this error message.
While this should never happen, it is a self-recovering error that requires
no action on the part of the user. If, however, it starts to occur frequently,
contact your Agilent service representative to find out if there is a
firmware upgrade to solve the problem.
791 Acquiring Data...
WBIF Power On Test Failed
An error occurred when the wide bandwidth IF hardware (Option 122 or
140) was tested during the power on process.
795 No trigger before timeout; auto-triggered
797 Awaiting Trigger, no AUTO Trig
801 Memory limit caused Data Acquisition to be truncated
805 doing Alignment...
838 Log Frequency Interpolation not Implemented
Instrument Messages
This error message is displayed when you try to load a correction file that
is using logarithmic frequency interpolation.
Chapter 161
Page 62
Instrument Messages
Instrument Messages
Greater than 10000: Measurement Applications Errors
NOTEError numbers are displayed in the error queue, not on the display.
To see an error number, press System, Show Errors.
10008 to 10522: Power Suite Error Messages An error number in this range indicates
the instrument has detected an error relating to the Power Suite functionality.
10008 Preferred resolution bandwidth not available.
The calculated required resolution bandwidth for this measurement is not
available.
10010 One or more harmonics past freq limit: number decreased.
Highest harmonic was past the frequency limit of the analyzer, so the
number of measured harmonics was decreased.
10011 First harmonic is past analyzer frequency limit.
First harmonic was past the frequency limit, so no harmonics can be
measured. The analyzer will simply measure the fundamental. If you have
an Option AYZ it allows the use of Agilent 11970 Series, and Agilent 11974
external mixers to extend the frequency range to 110 GHz. Operation to
325 GHz is also possible with non-Agilent mixers.
10012 No Fundamental > 0 Hz found in given span.
There were no frequencies greater than 0 Hz in the starting span, so the
centre frequency at measurement entry will be used as the fundamental.
10013 No Fundamental > -50 dBm found in given span.
There was no fundamental found, so the centre frequency at measurement
entry will be used as the fundamental.
Instrument Messages
10020 Signal Tracking is not available when Noise Correction is on.
If signal tracking is turned on while noise correction is on, it will be turned
off. To use the signal tracking function, first turn noise correction off.
10138 Valid GSM burst not found in frame (Burst Type)
No active GSM bursts that match the selected burst type have been
detected in the RF input signal. Search was performed over a complete
GSM frame.
10139 Valid GSM burst not found in specified timeslot (Burst Type)
No active GSM bursts that match the selected burst type have been
detected in the RF input signal. Search was performed over the specified
timeslot.
62Chapter 1
Page 63
Instrument Messages
Instrument Messages
10140 Valid GSM burst not found in frame (Ref Burst)
No active GSM bursts that match the selected burst type have been
detected in the RF input signal. Search was performed over the specified
complete GSM frame using the Ref Burst type setting.
10141 Sync word not found in frame (Burst Type)
One or more active GSM bursts that match the selected burst type have
been detected in the RF input signal, but none contain the selected
Training Sequence Code (TSC). The search was performed over the
complete GSM frame.
10142 Sync word not found in specified timeslot (Burst Type)
One or more active GSM bursts that match the selected burst type have
been detected in the RF input signal, but none contain the selected
Training Sequence Code (TSC). The search was only performed over the
specified timeslot setting.
10143 Sync word not found in frame (Ref Burst)
One or more active GSM bursts that match the selected burst type have
been detected in the RF input signal, but none contain the selected
Training Sequence Code (TSC). The search was only performed using the
Reference Burst type and the Ref TSC settings over the complete GSM
frame.
The RF Communications Hardware (Option B7E) and Digital Signal Fast
ADC (Option B7D) cards required to perform the demodulation are not
present in the analyzer.
10147 Opt B7D bootrom requires upgrade.
The (Option B7D) bootrom revision is not supported by the currently
loaded personality version. Refer to the user’s guide for the personality in
use.
10148 Opt BAH DSP algorithm files not installed. Meas unavailable.
Contact your Service Center.
The Digital Signal Processor algorithm files required to perform the
demodulation are not present in the analyzer.
Instrument Messages
Chapter 163
Page 64
Instrument Messages
Instrument Messages
10148 B7D DSP Code Fail. Reload Opt BAH. Contact your Service
Center.
The Digital Signal Processor algorithm files required to perform the
demodulation are not present in the IDSP: drive.
The Digital Signal Processing algorithm code file revision is not supported
by the currently loaded personality version. Refer to the user guide for the
personality in use for more information on installation/upgrade.
The Digital Signal Processor algorithm coefficient file revision is not
supported by the currently loaded personality version. Refer to the user
guide for the personality in use.
The Digital Signal Processor algorithm files required to perform the
demodulation are corrupt and cannot be loaded properly. Reinstall
measurement personality.
10151 B7D DSP Code Fail. Reload Opt BAH. Contact your Service
Center.
The Digital Signal Processor algorithm files required to perform the
demodulation are present in the IDSP: drive and cannot be loaded
properly into DSP RAM. Reinstall measurement personality.
10152 Lost trigger, aborting measurement.
The selected trigger source was present at the start of the measurement,
but timed out before the measurement completed.
10153 DSP algorithm timeout, aborting measurement
The Digital Signal Processor demodulation algorithm timed-out for an
Instrument Messages
unknown reason. This message normally indicates a problem with the
modulated signal.
10154 Measurement not defined for Out of Band.
You have changed to an out-of-band frequency range. The band
measurement only operates in the selected band.
10155 No Fast ADC hardware installed. Meas unavailable.
The analyzer cannot use sweep times of less than 5 msec when Option B7D
or Option AYX is not installed. Therefore, the measurement will not be
executed.
64Chapter 1
Page 65
Instrument Messages
Instrument Messages
10156 No Fast ADC hardware installed.
The analyzer cannot use sweep times of less than 5 msec when Option
B7D or Option AYX is not installed resulting in all the radio standards not
being supported.
10156 The calibration data is invalid, and has been cleared.
10157 Tracking Generator hardware is not present. Meas unavailable.
The measurement requires a built-in tracking generator.
10158 This operation requires a measurement to be active.
10159 Entire trace is below threshold level
The measurement cannot operate properly because the trace has
completely fallen below the threshold level. Change the threshold level to
view trace.
10160 Valid burst not found
Cannot find a valid burst, either because it is not fully on the display, or
the level is too low to be detected properly.
10160 Upper Custom Mask is Invalid!
The user-specified upper custom mask cannot be resolved into a limit line.
The format may be bad.
10161 No Fast ADC hardware installed.
Cannot use sweep times less than 5 ms, due to the lack of a fadc, therefore
the meas will be severely restricted.
10161 Lower Custom Mask is Invalid!
The user-specified lower custom mask cannot be resolved into a limit line.
The format may be bad.
10162 Resolution BW <300 kHz.
This error message is a warning that the resolution bandwidth has been
set below 300 kHz. The test results will not meet GSM specifications.
10163 Cannot find the Power vs Time Limits File.
The limit line definition file for the GSM standards has been deleted. This
message is displayed while the
Measure key is grayed out. Reinstall the
GSM measurement personality.
10164 Band Measurement not defined for Out of Band.
Instrument Messages
You are attempting to monitor the band but have set the frequency outside
the band. Reset the band for the particular standard for which you are
testing or use the channel setting which does not require a frequency to be
set. (
Meas Setup, Method (Channel)).
Chapter 165
Page 66
Instrument Messages
Instrument Messages
10165 Carrier Not Present.
10166 Cannot update the list of cable types.
The cable file may have been moved or deleted accidentally. Reinstall the
measurement personality. This message is applicable to the GSM (Option
BAH) and Distance to Fault (Option 225) measurement personality
options.
10166 Cannot locate the file that contains the list of cable types.
The cable file may have been moved or deleted accidentally. Reinstall the
measurement personality. This message is applicable to the GSM (Option
BAH) and Distance to Fault (Option 225) measurement personality
options.
10167 The file containing the list of cable types has been updated.
10168 Cannot update the list of cable types on drive C:
The file update failed.
10170 The Cable Fault Measurement is active. Mode Setup is disabled.
Mode setup is not available in the cable fault utility.
10172 Sweep Time too fast (<2 sec)
The sweep time must be set to 2 seconds or longer for the results to be
valid.
10173 Carrier Not Present.
10177 There are no spurs to inspect.
You have attempted to switch the
Inspect Spur menu key to the On position
after the measurement has finished, but found no spurs.
10178 Carrier Not Present.
10179 Carrier Present. Test Stopped!
Instrument Messages
A carrier was found in the transmit band. Either disable the carrier or
insert a bandpass filter for the receive bandwidth.
10180 Gate option not installed. Results may not be accurate.
This measurement method requires the use of the time-gate (option 1D6)
in order to gate the spectrum during the 50-90% part of the burst. If the
gate option is not installed, the measurement will still run although this
warning will be displayed.
10181 Upper Custom Mask is Invalid!
The user-specified upper custom mask cannot be resolved into a limit line.
The format may be bad.
66Chapter 1
Page 67
Instrument Messages
Instrument Messages
10182 Lower Custom Mask is Invalid!
The user-specified lower custom mask cannot be resolved into a limit line.
The format may be bad.
10183 Resolution BW < 300kHz.
The test will not meet EDGE specifications because the resolution BW has
fallen below 300 kHz.
10184 Cannot find the Power vs Time Limits File.
Cannot find the limit line definition file for the EDGE standards. This
message is displayed while the
Measure key is grayed out.
10185 Gate option not installed. Results may not be accurate.
10186 Measurement does not support the current radio standard.
The measurement you have chosen is currently greyed out. Select a radio
standard which is supported or configure this measurement manually
(
Mode Setup, Radio Std. None).
10186 EDGE EVM only supports EDGE TCH burst type (Burst Type)
10187 Radio standard is not supported by the current measurement.
The standard you have chosen is currently greyed out. Select a radio
standard which is supported by the current measurement or configure this
measurement manually (
Mode Setup, Radio Std. None).
10187 EDGE ORFS only supports EDGE TCH burst type (Burst Type)
10188 EDGE PVT only supports EDGE TCH burst type (Burst Type)
10189 EDGE PVT only supports EDGE TCH burst type (Ref Burst)
10190 Select a valid Radio Standard/Measurement combination to
enable.
The Enable All Measurements menu key was pressed when it was
disabled. To enable select a radio standard that is supported by the current
measurement or a measurement that supports the current radio standard.
10190 EDGE ORFS only supports EDGE TCH burst type (Ref Burst)
10191 Mask unavailable for current Span - increase to display mask.
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.
Instrument Messages
10191 EDGE EVM only supports EDGE TCH burst type (Ref Burst)
Chapter 167
Page 68
Instrument Messages
Instrument Messages
10192 Sweep Point/Span ratio below minimum - results may be
inaccurate.
The sweep point to span ratio is below the minimum required to ensure
the bucket ratio is large enough to test DVB-T masks
10218 Hardkeys are disabled.
Some of the forms (for example Receiver Spurious in GSM) do not allow
you to close the form without either formally accepting or cancelling the
form settings. For this reason, all of the hardkeys are disabled until you
terminate the form.
10219 Awaiting trigger
The measurement requires a trigger to be present. If the trigger does not
occur or is delayed, this message will be displayed. Check your trigger
settings.
10220 Preselector cannot be bypassed in this mode.
The Option 123 allows the microwave preselector to be bypassed. This
functionality is not available from within either the Phase Noise or Noise
Figure application modes. If the preselector is set to off, it will
immediately be forced back to On.
10227 Measurement suspended until carrier is turned off.
The receive channel power and the receive spur measurements are
specified with the attenuation set to 0 dB. To prevent overload, the
frequency spectrum of interest is monitored for signal levels which exceed
a specified threshold before setting the attenuator to 0 dB. If a carrier is
found, this message is displayed and the completion of the measurement
will not occur until the carrier is removed. The carrier check may be
turned off using the properties form under the front-panel
Mode Setup key.
You may also change the signal threshold which determines a carrier on
the properties form.
Instrument Messages
10228 Cannot correlate to input signal.
This error is normally generated because of one of the following reasons:
1. There is no carrier signal.
2. Walsh channels other than the pilot are active.
3. There is some other modulation problem that will prevent the
measurement from being made.
This problem must be corrected before the measurement can continue.
10229 The regression portion failed.
This message occurs when (Option B7D) is not functioning properly.
Demodulation measurements (modulation accuracy and code domain)
might fail as a result of this error.
68Chapter 1
Page 69
10230 DSP timed out, resetting DSP.
Digital Signal Processor was unable to finish the selected measurement
within the given period of time. Restart the measurement.
10231 Measurement failed for unknown reasons.
Check instrument settings and restart measurement.
10232 RF Signal not found.
This message is generated if there is no signal at the center frequency that
is greater than 10 dB above the displayed average noise level.
10233 Level is low, results may degrade.
The signal being measured is of low power. The results may not be as
accurate as they would be if the signal level was higher.
10237 RF Board LO Unlocked. Contact service center.
This message occurs if the local oscillator on the (Option B7E) is in an
unlocked state. This indicates broken hardware.
Instrument Messages
Instrument Messages
10238 RF Board SR Osc Unlocked. Contact service center.
This message occurs if the sample rate (SR) oscillator on Option B7E is in
an unlocked state. This indicates broken hardware.
10239 Opt Freq Ref setting does not match external reference.
This message is generated if Source is set to External on the properties
form under the front-panel
Mode Setup key and the frequency on the same
form is set to a frequency that does not match the frequency of the signal
being used as the external reference.
10240 RF Board RF Osc Unlocked. Contact service center.
This message occurs if the reference oscillator on the (Option B7E) is in an
unlocked state. This indicates broken hardware.
10241 RF Board could not detect any bursts in signal.
This message is generated when the trigger is set to RF Burst and (Option
B7E) cannot detect a burst.
10245 Error reading file: SPCLIMIT.CSV. Cannot use custom limits.
The file could be missing or corrupt. Create a new limits file. Alternatively,
the actual limits defined in the file might not allow the measurement to be
executed. Redefine the limits or use the default limits. Restart the
measurement.
The file is missing or corrupt. Please reinstall the cdmaOne personality.
10256 Error reading file: OOBSTAB.CSV. Use Edit Table | Save Table.
This error is generated when you try to load a table (using the
Load Table
key on page 2 of the edit table form menu) before a table has been saved.
You must first save a table using the
table using the
Load Table key.
Save Table key before trying to load a
10259 Table could not be saved.
This message occurs if the C: drive is full or corrupt. Check the amount of
space left on the drive.
10260 Table could not be loaded.
When trying to load a table, the previous table has been somehow
corrupted. Use the
Save Table key to save a valid table. Then edit the valid
table, save it, and try to load it again.
10264 Emission bandwidth not found. Consider increasing span.
This error is normally generated when attempting occupied bandwidth
Instrument Messages
measurements. The “X dB” value you entered (
Meas Setup, X dB) to
calculate the emission bandwidth is the difference between the highest
point on the trace and the point “X dB” down on either side of the
maximum. If the actual difference is less than the value entered, the
emission bandwidth cannot be computed. Some responses to this situation
are as follows:
1. Connect a signal to the input. (If there is no signal present, the
difference between the trace minimum and maximum will generally be
less than “X dB”.)
2. Increase the span. (If the signal is wide, the shoulders of the signal
might not be present on the screen, and again, the difference between
the trace minimum and maximum will be less than “X dB”.)
70Chapter 1
Page 71
Instrument Messages
Instrument Messages
3. Center the signal. (There must be a point on the trace that is “X dB”
down from the maximum on both sides of that maximum.)
10286 Burst not found.
Either the signal being analyzed has insufficient power, the rising or
falling edges cannot be detected, or the burst is less than
126 microseconds.
10287 Valid Bluetooth burst not found. (Check Packet Type)
The burst that has been found does not correspond to the currently
selected Bluetooth packet type (the burst length may be too short).
10288 Option B7D or AYX FADC hardware required. Meas unavailable.
The measurement you are attempting requires either the DSP and Fast
ADC (Option B7D) or the Fast ADC (Option AYX) card to perform the
demodulation, but neither are present in the analyzer.
You have selected (by remote SCPI command) preamble sync with no
Bluetooth FM demodulation card present (Option 106).
10321 Start Marker must be at least 1% < Stop Marker.
You have attempted to input a start marker value that will result in the
difference between the start and stop markers being less than 1%.
10322 Stop Marker must be at least 1% > Start Marker.
You have attempted to input a stop marker value that will result in the
difference between the start and stop markers being less than 1%.
Instrument Messages
10323 Unable to Calculate Result using Current Setup.
You have changed the setup parameters such that the marker lines used to
measure the power cannot be displayed therefore accurate measurements
cannot be made.
Chapter 171
Page 72
Instrument Messages
Instrument Messages
10340 ’10101010’ pattern not detected - results may be inaccurate.
This message is displayed if the measurement cannot detect the
‘10101010’ pattern in the payload. The measurement will continue and
carry out the calculations on the payload data supplied, but may not be
correct.
10350 Payload data pattern ‘10101010’ not present.
This message is displayed when the “Payload Data” parameter is set to
Auto and the measurement has not detected either of the required
patterns in the payload.
10351 Required payload data pattern ‘10101010’ not present.
This message is displayed after successfully measuring and holding the
‘11110000’ pattern if the measurement is restarted and the ‘10101010’ data
pattern is not detected.
10352 Required payload data pattern ‘11110000’ not present.
This message is displayed after successfully measuring and holding the
‘10101010’ pattern if the measurement is restarted and the ‘11110000’ data
pattern is not detected.
10353 There is no valid result to hold.
You have attempted to hold either ∆ f1 or ∆f2 before it has been measured.
10360 Can’t compute result - not enough transitions.
This message is displayed when the measurement cannot find either a 111,
000, 101 or 010 pattern and is therefore unable to calculate the low or high
frequency deviations.
10389 Valid EDGE burst not found in frame (Burst Type)
No active EDGE bursts that match the selected burst type have been
detected in the RF input signal. Search was performed over the complete
Instrument Messages
EDGE frame.
10390 Valid EDGE burst not found in specified timeslot (Burst Type)
No active EDGE bursts that match the selected burst type have been
detected in the RF input signal. Search was performed over the specified
timeslot.
10391 Valid EDGE burst not found in frame (Ref Burst)
No active EDGE bursts that match the selected burst type have been
detected in the RF input signal. Search was performed over the specified
complete EDGE frame using the Ref Burst setting.
72Chapter 1
Page 73
Instrument Messages
Instrument Messages
10392 B7D DSP Code Fail. Reload Opt. 202. Contact your Service
Center
The DSP algorithm files required to perform the demodulation are not
present in the instrument ISDP: drive.
10395 B7D DSP Code Fail. Reload Opt. 202. Contact your Service
Center.
The DSP algorithm files required to perform the demodulation are present
in the instrument ISDP: drive, but cannot be loaded properly into DSP
RAM.
10396 EDGE Upgrade (252) unlicensed. Please contact your Agilent
Sales Rep.
10400 Valid signal not found.
This error is normally generated because of one of the following reasons:
1. There is no carrier signal.
2. The carrier signal power has changed during the measurement, causing
ADC to over/under range.
3. There is some other modulation problem that will prevent the
measurement from being made. This problem must be corrected before the
measurement can continue.
10401 Valid burst not found in frame (Burst Type).
No active bursts that match the Burst Type have been detected in the RF
input signal. The search was performed over the complete frame.
10402 Valid burst not found in specified timeslot (Burst Type).
No active bursts that match the Burst Type have been detected in the RF
input signal. The search was only performed over the specified timeslot
setting.
10403 Sync word not found in frame (TSC).
One or more active EDGE bursts that match the Normal Burst Type have
been detected in the RF Input signal, but none contain the selected
Training Sequence Code (TSC). The search was performed over the
complete EDGE frame.
10404 Sync word not found in specified timeslot (TSC).
Instrument Messages
One or more active EDGE bursts that match the Normal Burst Type have
been detected in the RF Input signal, but none contain the selected
Training Sequence Code (TSC). The search was only performed over the
specified timeslot setting.
Chapter 173
Page 74
Instrument Messages
Instrument Messages
10409 Wideband calibration not valid until Align Now, All performed.
Wideband calibration corrections cannot be applied to current
demodulation results. Results will not meet specified demodulation
performance levels until an Align Now, All has been performed.
Wideband calibration corrections cannot be applied to the current
demodulation results. Results will not meet specified demodulation
performance levels until
Wideband Cal has been selected and successfully
performed.
10411 Measurement uncalibrated, symbol rate exceeds +/-10% nominal.
Wideband calibration corrections cannot be applied to current
demodulation results, due to the
Symbol Rate setting exceeding +/-10% of
the nominal value. Results may not meet specified demodulation
performance levels.
10412 Cal Data corrupt. Wideband cal failed. Using previous data.
Wideband calibration procedure failed for an unknown reason. New
calibration data was not saved. Previous wideband calibration data is
being used, if available. However, it is not acceptable. Before re-attempting
Wideband Cal, ensure connection between the
INPUT 50 Ω is in place. If the error persists, get in touch with your service
AMPTD REF OUT and the
center.
10413 B7D DSP Code Install Fail Opt.229. Contact your Service
Center.
The Digital Signal Processor algorithm files required to perform the
demodulation are not present in the analyzer. Reinstall the measurement
personality and contact your service center.
The Digital Signal Processing algorithm code file revision is not supported
by the currently loaded personality version. Refer to the user guide for the
personality in use for more information on installation/upgrade.
The Digital Signal Processor algorithm coefficient file revision is not
supported by the currently loaded personality version. Refer to the user
guide for the personality in use for more information on
installation/upgrade.
10416 B7D DSP Code Reload Fail Opt.229. Contact your Service Center.
The Digital Signal Processor algorithm files required to perform the
demodulation are corrupt and cannot be loaded properly. Reinstall the
measurement personality and contact your service center.
74Chapter 1
Page 75
Instrument Messages
Instrument Messages
10417 This operation requires a measurement to be active.
The analyzer cannot perform this operation, because it requires a
measurement to be running and no measurement is running.
10418 Demod Format setting does not allow this value for
Points/Symbol.
Invalid Points/Symbol selection attempted for the given Demod Format
setting.
10419 Carrier Not Present.
A carrier signal/burst is expected at the analyzer input. This signal cannot
be found; however, the measurement will still run. Check input signal
connection.
10420 Valid burst not found.
This error only occurs when
RF Amptd is selected for Burst Sync. It
indicates that a valid burst envelope which meets the specified Burst
Search Threshold was not found within the specified Burst Search Length.
Note that the demodulation measurement will proceed by attempting to
demodulate the signal without Burst Sync alignment. Possible causes may
be:
1. Carrier signal is not actually bursted.
2. Burst Search Threshold and/or Burst Search Length may need to be
adjusted.
10421 Cannot lock to carrier.
This error only occurs when attempting to demodulate OFFSET QPSK
signals. It indicates that the demodulation algorithm is unable to lock to
your signal. Possible causes may be:
1. There is no carrier signal.
2. Carrier signal is present, but Demod settings do not match the
modulation format of the OFFSET QPSK signal being measured.
3. OFFSET QPSK signal is too noisy to achieve carrier lock.
10425 B7D DSP Code Install Fail Opt.231. Contact your Service
Center.
Instrument Messages
The Digital Signal Processor algorithm files required to for the 89600 VSA
SW are not present in the analyzer. Reinstall the measurement
personality and contact your service center.
The Digital Signal Processing algorithm code file revision is not supported
by the currently loaded personality version. Refer to the user guide for the
personality in use for more information on installation/upgrade.
The Digital Signal Processor algorithm coefficient file revision is not
supported by the currently loaded personality version. Refer to the user
guide for the personality in use for more information on
installation/upgrade.
10428 B7D DSP Code Reload Fail. Opt.231. Contact your Service
Center.
The Digital Signal Processor algorithm files required for the 89600 VSA
SW are corrupt and cannot be loaded properly. Reinstall the measurement
personality and contact your service center.
10450 Avg Mode changed to Repeat for Full Meas Type.
Meas Type has been changed to Full. Exponential Average Mode is not
available for Full Meas Type therefore Average Mode has been changed to
Repeat.
10451 Avg Mode changed to Exp for Examine Meas Type.
Meas Type has been changed to Examine. Repeat Average Mode is not
available for Examine Meas Type therefore Average Mode has been
changed to Exponential.
10452 Meas Type changed to Examine for Exp Avg Mode.
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.
10453 Meas Type changed to Full for Repeat Avg Mode.
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.
Instrument Messages
10454 Valid burst not found.
Cannot find a valid burst, either because it is not fully on the display, or
the level is too low to be detected properly.
Using the current instrument settings, the measurement cannot locate
four signals with enough energy or resolution to perform an accurate
measurement.
76Chapter 1
Page 77
Instrument Messages
Instrument Messages
10510 Signals do not fit expected Intermod (TOI) pattern.
Based on the current analyzer settings, the measurement cannot find two
signals of high enough amplitude that can be resolved in such a manner
that the third order products would lie within the measured span. You
need to widen the span to include TOI products.
10511 100 spurs found. Additional spurs ignored.
There are too many spurs for the table (the limit is 100), and any
additional spurs that are found will be ignored
10512 No spurs have been found.
You have 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.
10513 No ranges are defined.
There are no active ranges in the range table. You will need to activate at
least one range.
10514 Avg Mode changed to Repeat for Full Meas Type
Meas Type has been changed to Full. Exponential Average Mode is not
available for Full Meas Type therefore Average Mode has been changed to
Repeat.
10515 Avg Mode changed to Exp for Examine Meas Type
Meas Type has been changed to Examine. Repeat Average Mode is not
available for Examine Meas Type therefore Average Mode has been
changed to Exponential.
10516 Meas Type changed to Examine for Exp Avg Mode
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.
10517 Meas Type changed to Full for Repeat Avg Mode
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.
10518 Invalid State Register
There are only a limited number of instrument state registers/locations
available.
Instrument Messages
10520 Command not supported
Command my not be supported configuration or with the current settings
of other related functions.
Chapter 177
Page 78
Instrument Messages
Instrument Messages
10524 to 10561: Phase Noise Error Messages (Option 226) An error number in this
range indicates the instrument has detected an error relating to the Phase Noise
personality.
10524 This measurement does not support the *.CSV file format.
You cannot load or save base instrument traces, as this is not supported by
the Log Plot measurement.
10525 Invalid format: CSV files are not supported by this
measurement.
You cannot load or save base instrument traces, as this is not supported by
the Log Plot measurement.
10525 Use View/Trace menu when loading or saving logarithmic traces.
You cannot load CSV format trace files or save traces in the CSV format in
the Log Plot measurement of the Phase Noise Measurement Personality.
10526 Cannot display Ref Trace because it has no data.
Reference trace cannot be displayed, as there is currently no data assigned
to it - use the functions under the Store Ref Trace menu, or load a trace to
assign some data.
10527 Invalid Marker Trace. Marker moved to Raw Trace.
Cannot place markers on the reference trace, because the reference trace
is currently turned off or has no data.
10529 Failed to Load trace. Bad file format.
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.
10530 Trace file contains no compatible traces.
The trace file may have been created by another version of the Phase Noise
Instrument Messages
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.
10531 Trace file was created by incompatible version of Opt. 226
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.
10532 Cannot open trace file for writing. Save Failed.
Cannot write the trace file to the destination filename. This could be
because the disk is full, or possibly due to a filename error. If using a
floppy disk, check there is a formatted disk in the drive.
78Chapter 1
Page 79
Instrument Messages
Instrument Messages
10533 Cannot save Trace because it contains no data.
Cannot save Ref Trace because it contains no data.
Check the Ref Trace is turned on, and contains some valid trace data.
10534 Trace file saved successfully.
The trace saving operation was successful.
10535 Carrier Not Present
No Carrier > -50 dBm found at the analyzer input within the search span.
Solution: Modify center frequency to be closer to actual carrier, or
alternatively apply carrier of sufficient amplitude at the current center
frequency.
10535 Cancellation trace is not set to Reference or has no data.
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.
10536 Cancellation disabled while measuring DANL Floor.
Phase Noise cancellation does not make sense when measuring the DANL
Floor, so for this reason it has been disabled.
10537 10537 Cancellation trace has different X-Scale to Smoothed
trace.
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 have been measured over the same range of
offsets, and on the same instrument as the current measurement being
performed.
10560 Carrier Not Present. Verify frequency and amplitude settings.
No Carrier > –50 dBm found at the analyzer input within the search span.
Solution: Modify center frequency to be closer to actual carrier, or
alternatively apply carrier of sufficient amplitude at the current center
frequency.
10561 Signal Tracking disabled when measuring DANL Floor (Removal).
Measuring the DANL Floor with DANL Method set to Removal requires
that you remove the signal and attach a load to the analyzer RF Input.
Signal Tracking requires that the carrier be measured many times per
measurement, so the two are inherently incompatible.
Instrument Messages
Chapter 179
Page 80
Instrument Messages
Instrument Messages
10601 to 10700: GSM and EDGE Error Messages (Options BAH and 202) An error
number in this range indicates the instrument has detected an error relating to the GSM
or EDGE personality.
10602 Sync word not found
An attempt to position a GSM trace into the mask, when not enough data
was present. Try using the
Restart key to clear the problem. This can be
caused by a bad GSM burst, or the RF Sync Delay set too far.
10604 GSM burst out of limits
The GSM signal did not fit into the mask in the Power vs. Time
measurement.
10606 Insufficient pre-Trig for demod - decrease Trig Delay
10608 Incorrect RBW for demod - change RBW
10610 GSM Hopping enabled, waiting for valid burst
10612 Invalid GSM burst timing
A GSM-like burst was acquired, but its timing is not valid. Ensure the
correct
Burst Type has been selected.
10614 Valid GSM burst not found
In a GSM measurement, data was acquired but a GSM burst was not
found, with the timeslot mode disabled.
10138 Valid GSM burst not found in frame (Burst Type).
No active GSM bursts that match the selected Burst Type have been
detected in the RF input signal. The search was performed over the
complete GSM frame.
10139 Valid GSM burst not found in specified timeslot (Burst Type).
No active GSM bursts that match the selected Burst Type have been
Instrument Messages
detected in the RF input signal. The search was only performed over the
specified timeslot setting.
10140 Valid GSM burst not found in frame (Ref Burst).
No active GSM bursts that match the selected Burst Type have been
detected in the RF input signal. The search was performed using the Ref
Burst type setting over the complete GSM frame.
10616 Cannot synchronize frame trigger
Cannot synchronize the frame trigger to the even second clock.
10618 Dynamic range not optimum
10620 Cannot synchronize to RF amplitude (burst error)
80Chapter 1
Page 81
Instrument Messages
Instrument Messages
10622 GSM RF sync delay is out of range
Change RF Sync Delay.
10624 Sync word not found
In a GSM measurement using demodulation, the training sequence code
(sync word) could not be found.
10141 Sync word not found in frame (Burst Type)
One or more active GSM bursts that match the selected Burst Type have
been detected in the RF Input signal, but none contain the selected
Training Sequence Code (TSC). The search was performed over the
complete GSM frame.
10142 Sync word not found in specified timeslot (Burst Type)
One or more active GSM bursts that match the selected Burst Type have
been detected in the RF Input signal, but none contain the selected
Training Sequence Code (TSC). The search was only performed over the
specified timeslot setting.
10143 Sync word not found in frame (Ref Burst)
One or more active GSM bursts that match the selected Burst Type have
been detected in the RF Input signal, but none contain the selected
Training Sequence Code (TSC). The search was only performed using the
Reference Burst type and Reference TSC settings over the complete GSM
frame.
10626 Signal too noisy
In a GSM measurement, indicates that a burst could not be found in a
signal that appears noisy.
10628 Sync is RF Ampl (not Training Seq). Bits not accurate
10630 Marker X value not adjusted when right of Rise&Fall mark
10632 Incorrect trigger holdoff
10634 Break freq > FFT filter edge
10636 SCPI marker query not available in GSM Rise&Fall
10638 GSM Pwr Meas requires trig delay < −50 µs. Delay set to −50 µs
10640 Carrier frequency outside device’s transmit band
The entered channel/carrier frequency is not within the range of your
current mode setup selection of standard and device.
Instrument Messages
10642 ADC overload -- Carrier not at expected frequency
The carrier frequency of the signal may not match the instruments
channel frequency setting.
Chapter 181
Page 82
Instrument Messages
Instrument Messages
10644 Requested timeslot number not present
The selected timeslot is not on. (Timeslot is referenced to the trigger
point.)
10646 Tx Band Spur measurement not defined for mobiles
Only base station testing is available.
10648 Carrier power too low for optimum dynamic range
For better dynamic range, transmit band spur measurements require
>10 dBm signal power at the RF input port.
10650 Unexpected carrier frequency (BMT only)
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.
10652 EVM Measurement only supports EDGE TCH burst type
10654 Unable to demodulate signal
10655 Input overload
Excessive input power has been detected which will cause the ADC to clip
the signal. Reduce the signal level, change the attenuator setting (under
Input menu), or press Restart if the RF Input Range is Auto.
10656 Tx Band Spur measurement does not support this frequency band
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.
10657 Pretrigger too long
10658 Valid GSM burst not found for selected timeslot
Instrument Messages
In a GSM measurement, data was acquired but a GSM burst was not
found, with the timeslot mode enabled.
10659 Sync not found on AM path
The instrument failed to find the training sequence on the AM path.
10660 Sync not found on PM path
The instrument failed to find the training sequence on the PM path.
10661 Sync not found on AM and PM path
The instrument failed to find the training sequence on both the AM and
the PM paths.
82Chapter 1
Page 83
Instrument Messages
Instrument Messages
10662 Inconsistent sync word
The instrument detected the training sequence, but the training sequence
number is inconsistent between the AM path and the PM path.
10701 to 10800: W-CDMA Error Messages (Option BAF) An error number in this
range indicates the instrument has detected an error relating to the W-CDMA personality.
10702 Signal too noisy
10704 Input power too low
The instrument only identifies a channel as active if it meets the default
threshold criteria that it is within 20 dB of the highest power code
channel. The threshold can be changed using the Active Set Threshold
function in the Meas Setup menu.
10768 Cannot correlate to input signal
Cannot correlate to the input signal and no active channel is found. (from
the composite EVM measurement) An active channel must meet the
default threshold criteria that it is within 20 dB of the highest power code
channel. The threshold can be changed using the active set threshold
function in the Meas Setup menu.
10772 Burst not found.
Either the signal being analyzed has insufficient power, the rising or
falling edges cannot be detected, or the burst is less than
126 microseconds.
10776 PSA Cannot sync DPCCH pilot.
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.
10778 PSA Valid PRACH burst not found.
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.
10780 Critical memory shortage occurred.
This error message appears when a critical memory shortage occurs, and
the current measurement is aborted. To continue, restart the
measurement by pressing the
Preset key, or by exiting and then
re-entering the current mode or the current measurement, or cycle the
power.
Instrument Messages
Chapter 183
Page 84
Instrument Messages
Instrument Messages
10788 Stored data length too short
Stored acquisition data length is too short. You need to perform one or
more of the following actions:
• Use the same
Sync Type setting that was used when the data was
acquired.
• Use the same
Start Sync Slot setting that was used when the data was
acquired.
• Reduce the
Capture Interval setting.
10790 Slot format auto-detection not supported by slot power meas
The slot format auto-detection (AUTO selected) is not supported by
Power
measurement type. It is supported only by Slot Phase measurement
Slot
type.
10792 Not enough memory. Decrease Capture Interval.
Not enough memory left and the measurement cannot continue. You need
to reduce the
Capture Interval setting and then restart the measurement to
recover from this situation.
10801 to 10900: cdma2000 Error Messages (Option B78) An error number in this
range indicates the instrument has detected an error relating to the cdma2000 personality.
10824 Signal too noisy
10826 Input power too low
The instrument only identifies a channel as active if it meets the default
threshold criteria that it is within 20 dB of the highest power code
channel. The threshold can be changed using the Active Set Threshold
function in the Meas Setup menu.
10868 Can not get long code phase (RS-232)
Instrument Messages
For MS (mobile station) measurements, the long code phase information
could not be obtained from the signal at the RS-232 port (from code domain
power measurement or composite EVM measurement).
10872 Cannot correlate to input signal
Cannot correlate to the input signal and no active channel is found. (from
composite EVM measurement) An active channel must meet the default
threshold criteria that it is within 20 dB of the highest power code
channel. The threshold can be changed using the active set threshold
function in the Meas Setup menu.
84Chapter 1
Page 85
Instrument Messages
Instrument Messages
10901 to 10925: NADC Error Messages (Option BAE) An error number in this range
indicates the instrument has detected an error relating to the NADC personality.
10902 Sync word not found
In an EVM measurement, the sync word is not found and the
synchronization cannot be established when
Burst Sync menu.
Sync Word is selected in the
10904 Valid NADC burst not found
A valid NADC burst is not found when the
Device is MS.
10906 Signal too noisy
The valid EVM measurement cannot be performed, because the input
signal is too noisy.
10908 Burst Delay out of limit for EVM (2 ms)
In an EVM measurement, the
Burst Delay value must be less than 2 ms.
10926 to 10950: PDC Error Messages (Option BAE) An error number in this range
indicates the instrument has detected an error relating to the PDC personality.
10926 Sync word not found
In an EVM measurement, the sync word is not found and the
synchronization cannot be established when
Burst Sync menu.
Sync Word is selected in the
10928 Valid PDC burst not found
A valid PDC burst is not found when the
Device is MS.
10930 Signal too noisy
Instrument Messages
The valid EVM measurement cannot be performed, because the input
signal is too noisy.
10932 Burst Delay out of limit for EVM (2 ms)
In an EVM measurement, the
Burst Delay value must be less than 2 ms.
10951 to 10975: cdmaOne Error Messages (Option BAC) An error number in this
range indicates the instrument has detected an error relating to the cdmaOne personality.
10952 Signal exceeds maximum allowable power
10954 Input overload
Excessive input power has been detected which will cause the ADC to clip
the signal. Reduce the signal level, change the attenuator/max total power
setting (under
Chapter 185
Input menu), or press Restart if the RF Input Range is Auto.
Page 86
Instrument Messages
Instrument Messages
10956 Channel center frequency outside device’s transmit band.
10960 No power at carrier frequency
No power was detected as a CW or a modulated signal.
10962 Cannot correlate to input signal
A correlation failure with the pilot CDMA channel occurred during
synchronous demodulation.
10976 to 11000: Programming Code Compatibility Messages (Option 266) An
error number in this range indicates the instrument has detected an error relating to the
Programming Code Compatibility Suite.
10976 CMD ERR, <name of offending command>
When a command or command argument is not recognized by the parser a
command error is generated.
10977 PARAMETER ERROR, <name of offending parameter>
When an illegal parameter is sent following a command. For example,
when the “GRAT” or “ANNOT” 8566 series commands are used with
arguments other than ON, OFF, 1 or 0.
10978 INVALID ITEM, <offending item>
The invalid item message appears when a value that is not part of the
commands list of enumerated arguments is entered.
10979 INVALID SAVE REG, <invalid register>
When the RCLS or RC commands are used to recall a state register that
wasn’t previously saved with the SAVES or SV commands.
10980 INVALID TRACE, <trace>
Instrument Messages
When the argument to a trace command is not part of the predefined trace
enumeration (TRA, TRB or TRC).
10981 CMD NOT SUPPORTED, <command>
Command not supported errors are generated when a valid 8566 command
that is not supported by Chameleon is executed.
10982 LOG FILE FULL, CLEAR FOR FURTHER ERROR LOGGING
10983 LOG FILE CLEARED
86Chapter 1
Page 87
Instrument Messages
Instrument Messages
12000 to 12999: Noise Figure Error Messages (Option 219) An error number in this
range indicates the instrument has detected an error relating to the Noise Figure
personality.
12116 Two entries already exist at frequency.
When specifying limit line point, if there are more than two points at the
same frequency, the new limit point is discarded and the existing limit is
used.
12219 Command not valid in this mode.
Indicates that the command sent from the Remote interface does not apply
for this DLP.
12303 User cal invalidated
The existing user cal has been invalidated because of one of the following
reasons:
•Meas mode changed
• Freq outside cal range
•Fixed LO changed
• Sideband changed
12304 Alignment Failed
Calibration failed because an error was encountered at some point during
the calibration (for example gain < 0)
12305 Mode Setup Error
A mode setup error occurred because of one of the following:
• System input frequency out of range
• External LO frequency out of range
• Stop freq must be less than fixed LO freq
• Start freq must be greater than start IF freq
• LO – Stop freq must be >= min system input freq
• Start freq must be greater than fixed LO freq
• Stop IF freq must be less than fixed LO freq
• Start – LO freq must be >= min system input freq
• Stop freq must be less than stop RF freq
• Start freq must be greater than start RF freq
12307 Required Input attenuation not calibrated
Corrected measurements have been requested and the required RF
front-end setting of x dB has not been calibrated.
12308 Invalid frequency list for measurement mode
Instrument Messages
A frequency within the frequency list cannot be used to make a
measurement in the current mode.
Chapter 187
Page 88
Instrument Messages
Instrument Messages
12309 No entries in frequency list
A measurement was attempted with List frequency mode or a SCPI query
of the frequency list table was made and the frequency list table is empty.
12310 No entries in ENR table
A measurement was attempted or a SCPI query of an ENR table was made
and there were no entries in the relevant ENR table (Common, Meas or
Cal).
12311 No entries in Limit Line table
An attempt is made to either display or test against a limit line table
which has no entries.
12312 RF re-range required: Meas Restarted.
During a continuous measurement, a change of RF front-end attenuation
was required. To do this the measurement needs to be restarted.
12313 IF over range req. RF re-range: Meas Restarted.
During a continuous measurement, an IF section over range condition
occurred, requiring a change of RF front-end attenuation. To do this, the
measurement needs to be restarted.
12314 No entries in loss table
A measurement is attempted or a SCPI query of a before or after loss table
is made and there are no entries in the relevant loss table
12316 T hot must be greater than T cold
A spot T hot has been specified which is not greater than T cold.
12603 Illegal MSDOS name given
An invalid filename has been specified. Use filenames with a maximum of
8 characters (letters and digits only) and use a 3 character extension. Note
Instrument Messages
that lowercase and uppercase are perceived as the same.
12604 File already exists
Attempt to store a file that already exists. Delete or rename the old file
and try again
12605 Media is protected
A store was attempted to a write-protected device.
12606 Media is not writable
A store was attempted to a read-only device.
12612 File does not exist
The file you were trying to recall could not be found.
88Chapter 1
Page 89
12762 Incorrect filename, allowable extension CSV
Attempt to load/store table data with an incorrect extension.
12768 Failed to load ENR data
A problem occurred when trying to load or store table data.
12769 Failed to store ENR data
A problem occurred when trying to load or store table data.
12770 Incorrect filename, allowable extension ENR
Attempted to load/store table data with an incorrect extension.
12771 Failed to load Frequency List
A problem occurred when trying to load or store table data.
12772 Failed to store Frequency List
Attempt to load/store table data with an incorrect extension.
12773 Incorrect filename, allowable extension LST
Instrument Messages
Instrument Messages
Attempt to load/store table data with an incorrect extension.
12774 Failed to load Limit line
Attempt to load/store table data with an incorrect extension.
12775 Failed to store Limit line
Attempt to load/store table data with an incorrect extension.
Attempt to load/store table data with an incorrect extension.
12778 Failed to store Trace
A problem occurred when trying to load or store table data.
12779 Failed to load Loss data
A problem occurred when trying to load or store table data.
12780 Failed to store Loss data
A problem occurred when trying to load or store table data.
12781 Incorrect filename, allowable extension LOS
Attempt to load/store table data with an incorrect extension.
Instrument Messages
12995 Noise Figure DLP requires Noise Source Control Hardware
You have attempted to initiate the Noise Figure mode with the Noise
Source Control hardware installed in your instrument. You must install
the Noise Source Control hardware before running the Noise Figure mode.
Chapter 189
Page 90
Instrument Messages
Instrument Messages
13214 Frequency Hopping enabled, waiting for valid burst
The demodulated burst type has not been found in the originally
demodulated slot location within the frame.
13001 to 13100: 1xEV-DO Error Messages (Option 204) An error number in this
range indicates the instrument has detected an error relating to the 1xEV personality.
13024 Signal too noisy
13026 Input power too low
The instrument only identifies a channel as active if it meets the default
threshold criteria that it is within 20 dB of the highest power code
channel. The threshold can be changed using the Active Set Threshold
function in the
Meas Setup menu.
13070 Cannot correlate to input signal
Cannot correlate to the input signal and no active channel is found. (from
composite EVM measurement) An active channel must meet the default
threshold criteria that it is within 20 dB of the highest power code
channel. The threshold can be changed using the active set threshold
function in the
Meas Setup menu.
13074 Valid 1xEV burst not found
In a 1xEV measurement, data was acquired but a 1xEV burst was not
found, with the timeslot mode disabled.
13076 Critical memory shortage occurred
This error message appears when a critical memory shortage occurs, and
the current measurement is aborted. To continue, restart the
measurement by pressing the
Preset key, or by exiting and then
re-entering the current mode or current measurement, or cycle the power.
Instrument Messages
13080 PSA No Active slot is found
Occurs when
Meas Slot Type is Active and the Active slot is not found
during the capture interval. Synchronization occurs and the pilot is found
but no results are included in peak/average calculation.
13082 PSA No Idle slot is found
Occurs when
Meas Slot Type is Idle and the Idle slot is not found during the
capture interval. Synchronization occurs and the pilot is found but no
results are included in peak/average calculation.
This error message appears when memory shortage, related to long
capture interval, occurs. The current measurement is aborted and all the
results returned are invalid values. Decrease
Capture Intvl and restart the
measurement.
13101 to 13200: Flexible Digital Modulation Analysis Error Messages (Option
241) An error number in this range indicates the instrument has detected an error
relating to the Flexible Digital Modulation Analysis personality.
13102 Valid signal not found
The input signal cannot be demodulated because of inappropriate
parameter settings or incorrect signal
13104 Valid burst not found
The burst signal cannot be detected because of inappropriate parameter
settings or incorrect signal.
13106 Sync word not found
The sync word cannot be detected because of inappropriate parameter
settings or incorrect signal.
13108 Points/Symbol changed to an even number because of demod
format
Offset QPSK allows only even values for points/symbol. The demod format
was changed to OQPSK while the points/symbol was set to an odd value.
Therefore, the points/symbol was re-set to an even number.
13110 Sync Pattern includes non-hex characters
The sync pattern should only consist of hex characters. Invalid characters
are converted to 0.
13112 Sync Word Length changed to new upper limit
The upper limit of Sync word bits is 128. If the code word length (sync
word length) exceeds this value, then the sync word length is cut off. This
warning may happen only when the demod format is changed.
13114 Sync offset value not valid
The sync offset value is too far off from a value that would be reasonable to
measure valid portion of data. So the measurement gives up trying to
apply the offset value.
Instrument Messages
Chapter 191
Page 92
Instrument Messages
Instrument Messages
13116 Search Length is clipped to the upper value according to the
dependency of IF Band Width
Search length upper limits:
IF Band Width <= 1 MHz, Limit = 0.1 sec
1MHz < IF Band Width <= 10MHz, Limit = 0.05 sec
10MHz < IF Band Width <= 20MHz, Limit = 0.025 sec
20MHz < IF Band Width <= 40MHz, Limit = 0.013 sec
40MHz < IF Band Width, Limit = 0.007sec
13118 Search Length is clipped to the lower value as allowed by
current IF Band Width.
Search length lower limits:
IF Band Width <= 10MHz, Limit = 0.001 sec;
10MHz < IF Band Width Limit = 0.1 µsec
13120 Symbol Rate is clipped to its limit because of IF Path change.
Upper limit of Symbol Rate is 10 MHz when IF Path is Narrow.
13122 IF BW is clipped to its limit because of IF Path change.
Limit of IF BW depends on IF Path selection. If the value exceeds the
limit, it is clipped to the limit. This message will not appear when IF BW is
set to AUTO.
13124 Meas Interval is clipped to its upper limit because of
points/symbol change.
Upper limit of Meas Interval depends on points/symbol setting.
13126 Only one marker is available on Demod Bits trace.
Only one marker is available on Demod Bits trace.
13201 to 13300: Stimulus-Response Measurements Error Messages (Option 215)
Instrument Messages
An error number in this range indicates the instrument has detected an error relating to
the Stimulus Response measurement personality.
13226 Connection could not be established with specified IP Address.
A communication connection could not be established at the specified IP
Address. Check that the IP address entered is correct and that the signal
generator and PSA are both connected to the LAN or are connected to one
another using a LAN cross-over cable. If you are using a LAN cross-over
cable the IP address of both instruments must start with the same first
two integers. For example, if the analyzer IP address is 156.121.102.33
then the source IP address must be 156.121.xxx.xxx.
92Chapter 1
Page 93
Instrument Messages
Instrument Messages
13227 Freq range of ext src exceeded, PSA setting adjustments
required.
The calculated external source start or stop frequency exceeds the
frequency range of the external source. You need to adjust the PSA
settings so that the required source frequency is within it’s available
range. You may need to adjust the PSA start frequency, the PSA stop
frequency, the harmonic number (if on) and/or the frequency offset (if on).
The sweep will start again once the required frequency range is in the
range available to the source. See the Option 215 documentation for more
information about making these settings adjustments.
13228 Unable to store reference trace.
Unable to copy the data from trace 1 to trace 3. There is no data in trace 1.
Option 215 requires the gated sweep hardware. It has not been detected,
so an update is required. You should contact the local sales engineer and
order E444xAU Option 426.
13231 Freq band crossing not supported by Option 215
Option 215 does not support sweeping across a spectrum analyzer
hardware frequency band edge. For detailed frequency band information,
refer to the “Getting Started” information in the Option 215 guide.
13232 Video bandwidth fixed at 50MHz by Option 215
Option 215 forces the video bandwidth to be set to 50MHz when the
external source control state is set to ON
13233 Agilent PSG-A Series Signal Generators not supported.
Option 215 does not support the PSG-A signal generators. This includes
model number E8241A, E8242A, E8251A and E8254A.
13234 Open/Short CAL not possible, freq band crossing detected
You cannot perform a calibration if your PSA span includes frequencies in
more then one frequency band. Please adjust either the PSA start
frequency or its stop frequency to stay within a single frequency band. The
frequency band ranges are listed in the external source control guide
“Getting Started” chapter.
Instrument Messages
Chapter 193
Page 94
Instrument Messages
Instrument Messages
13301 to 13400: WLAN Error Messages (Option 217) An error number in this range
indicates the instrument has detected an error relating to the WLAN measurement
personality.
13338 Valid burst not found, extend search length
The instrument cannot find a valid WLAN burst. You may need to extend
the search length.
13340 Synchronization failed, check signal format
The instrument cannot synchronize the signal. Make sure the signal
format is correct
13342 Data is too short to measure
There is not enough data for proper analysis.
13382 Measurement Input Overload
The analyzer’s ADC input is overdriven. You need to reduce the signal
power at the input by using an external attenuator, or by increasing the
internal input attenuation of the analyzer.
13384 Point Quantities Limited
The capture point size exceeds the limit.
13386 Span Limited
The span exceeds the limit.
13388 Meas Offset exceeds valid burst length
The measurement offset exceeds the burst length detected. Default values
are returned.
13401 to 13500: Measuring Receiver Error Messages (Option 233) An error number
Instrument Messages
in this range indicates the instrument has detected an error relating to the Measuring
Receiver measurement personality.
13436 PSA Power meter connection failure
Attempt to connect to the power meter has failed. Please make sure that
the power meter is connected to the PSA and the connection settings are
correct.
13438 PSA Power meter connection time-out
A time-out occurred while the instrument was attempting to establish a
connection with the power meter.
13440 PSA No cal factor for power sensor
This message occurs when the power sensor model name is “NONE” or the
calibration factor table is empty.
94Chapter 1
Page 95
Instrument Messages
Instrument Messages
13442 PSA Power meter zero and calibration required
The power meter requires zeroing and calibration.
13444 PSA Power meter zero required
The power meter requires zeroing.
13446 PSA Power meter calibration required
The power meter requires calibration.
13448 PSA Power meter zero failure
The power meter zero function has failed.
13450 PSA Power meter calibration failure
The power meter calibration has failed.
13456 PSA Power meter reading not available. Retrying to connect.
The Tuned RF Level measurement cannot read the power meter. The
instrument is attempting to establish a connection.
13458 PSA Power meter model is not supported
The power meter model used is not supported by this version of the
firmware.
13460 PSA Power sensor hardware is missing
There is no power sensor connected to the input of the power meter.
13462 PSA RF frequency is beyond frequency range of cal factor table
The frequency of the input signal is either higher than the highest, or
lower than the lowest frequency in the cal factor table of the power sensor.
13464 PSA Audio level is out of range
Audio Range is not properly set. The input level is beyond the range.
The
13466 PSA Audio data acquisition failure
Audio measurement failed to acquire data due to I/O error. Data was lost
or DMA (direct memory access) aborted.
13727 to 13753: EMC Analyzer Error Messages (Option 239) An error number in
this range indicates the instrument has detected an error relating to the EMC Analyzer
personality.
Instrument Messages
13727 PSA EMC Analyzer
This message occurs when the PSA spectrum analyzer is placed in the
EMC Analyzer mode.
Chapter 195
Page 96
Instrument Messages
Instrument Messages
13729 PSA Connection with the Presel could not be established at the IP
A communication connection could not be established at the RF preselector
IP Address. Check to make sure that the IP Address that was entered is
correct. Also make sure that the RF preselector and PSA are both
connected to the LAN.
13731 PSA RF Presel model is not supported
The connected RF preselector model is not supported.
13733 PSA Connection with Source could not be established at the IP
A communication connection could not be established at the source IP
Address. Check to make sure that the IP Address that was entered is
correct. Also make sure that the source and PSA are both connected to the
LAN.
13735 PSA Connection with Source could not be established at the IP/GPIB
A communication connection could not be established at the source IP
Address. Check to make sure that the IP Address that was entered is
correct. Also make sure that the source and PSA are both connected to the
LAN.
13737 PSA Source model is not supported
The connected source model is not supported.
13739 PSA RF Presel conducted and radiated paths need to be aligned
The RF preselector conducted and radiated paths need to be aligned.
13741 PSA RF Presel conducted paths needs to be aligned
The RF preselector conducted paths need to be aligned.
13743 PSA RF Presel radiated paths need to be aligned
The RF preselector radiated paths need to be aligned.
Instrument Messages
13745 PSA RF Presel input is overloaded
The RF preselector input is overloaded.
13747 PSA RF Preselector alignment terminated by user
You have terminated the RF preselector alignment
13749 PSA RF Preselector conducted band alignment fails
The RF preselector conducted band is failing.
13751 PSA RF Preselector radiated band alignment fails
The RF preselector radiated band is failing.
96Chapter 1
Page 97
Instrument Messages
Instrument Messages
13753 PSA Frequency crossing Conducted and Radiated Band is not
supported
Option 239 does not support sweeping across Conducted and Radiated
Bands. Refer to the “EMC Analyzer Guide” for further details.
Instrument Messages Without Numbers
Error Messages Without Numbers
Error Attempt to change signal data failed.
EMC message, NOT USED
Error Awaiting valid signal.
This indicates that software enhanced triggering is ON and 5 successive
failures have been detected within a demod measurement
Error Unable to retrieve signal (remote).
EMC message NOT USED
Error Unable to uninstall personality, file not deletable.
This message occurs when you try to delete a personality which has been
marked as non-deletable. The personality is marked non-deletable at the
factory. Get in touch with your nearest service center for further
assistance.
Informational Messages
These messages simply provide information; you are not required to do anything.
Information in brackets (such as <directoryname>), is a previously-provided input.
Informational messages appear at the bottom of the screen in the status line.
Informational <directoryname> directory deleted
The directory indicated has been successfully deleted.
Informational <name1> directory renamed to <name2>
<directoryname1> directory renamed to <directoryname2>
Directory name1 has been successfully renamed to directory name2.
Instrument Messages
Informational <filename> file copied
The filename indicated has been successfully copied.
Informational <filename> file deleted
The filename indicated has been successfully deleted.
Chapter 197
Page 98
Instrument Messages
Instrument Messages
Informational <filename> file loaded
The filename indicated has been successfully loaded.
Informational <filename> file saved
The filename indicated has been successfully saved.
Informational <filename> too many data entries
This message may appear when loading data from a limit line or
amplitude correction file. The [DATA] section of such a file can contain at
most 200 lines of data. This message is displayed if that limit is exceeded.
Informational <filename1> file renamed to <filename2>
<name1> file renamed to <name2>
File name1 has been successfully renamed to file name2.
Informational Atten auto set to 15 dB
Indicates that an input signal has been detected which is of sufficient level
to damage the input circuitry and the input attenuator has been
automatically set to 15 dB. If the signal level is reduced, the attenuator
will stay at 15 dB. This overload protection occurs at an input power level
of 13 dBm (68 dBmV for Option 1DP) ± 7 dB when the input attenuation is
auto coupled and set to <15 dB. To return to the original measurement
setup, reduce the input signal level and press
Attenuation (Auto).
Amplitude. Then press
Overload protection is only available in the Agilent Technologies E4401B
and E4411B.
Informational Auto ranging...
Displayed during autoranging.
Informational B7D and/or B7E not found. Code Domain not available.
Instrument Messages
Digital Signal Processing and Fast Analog to Digital Converter (Option
B7D) and/or RF Communications Hardware (Option B7E) are not installed
options on your analyzer. Code domain is therefore not available.
Informational B7D and/or B7E not found. Mod Acc not available.
Digital Signal Processing and Fast Analog to Digital Converter (B7D)
and/or RF Communications Hardware (B7E) are not installed options on
your analyzer. Modulation accuracy is therefore not available.
Informational Carrier Not Present.
A carrier signal/burst is expected at the analyzer input. This signal cannot
be found; however, the measurement will still run. Check input signal
connection.
98Chapter 1
Page 99
Informational Channel frequency outside device’s transmit band.
Reset channel number or frequency.
Informational Default spur table values loaded.
No spur table has been previously saved when the Out-of-Band Spurious
measurement begins. Press
ranges of interest and press
Meas Setup, Edit Table to enter the frequency
Save Table to save that information. This
saved table will be loaded the next time the measurement is run.
Informational Device = Mobile. Code Domain not available.
Code Domain measurement is grayed out when the device is set to mobile
under the
Mode Setup front-panel key. Code Domain measurement is only
accessible when the device is set to base and RF Communications
Hardware (Option B7E) or Enhanced Memory Upgrade (Option B72) are
installed.
Informational Directory already exists
Each directory and file must have a unique name. The directory name you
have entered is currently being used on the selected drive. You may either
enter a new name or rename the directory currently existent.
Instrument Messages
Instrument Messages
Informational Device = Mobile. Mod Acc not available.
Modulation accuracy measurement is grayed out when the device is set to
mobile under
Mode Setup, front-panel key. Modulation accuracy is only
accessible when the device is set to base and RF Communications
Hardware (Option B7E) or Enhanced Memory Upgrade (Option B72) are
installed.
Informational Directory already exists
Each directory and file must have a unique name. The directory name you
have entered is currently being used on the selected drive. You may either
enter a new name or rename the directory currently existent. Refer to “File
Menu Functions” in the Agilent ESA Spectrum Analyzer User’s Guide.
Informational ENR table will be extrapolated
One or more calibration or measurement frequency points exceeds the
currently loaded Cal or Meas ENR Table frequency ranges. The
corresponding ENR tables lowest frequency ENR value will be re-used for
frequencies less than the table range, and the highest frequency ENR
value will be re-used for frequencies greater than the table range.
Informational HW Average
For Option 122 or 140 only. If frame triggering is on, this message shows if
you turn on the hardware time averaging.
Instrument Messages
Chapter 199
Page 100
Instrument Messages
Instrument Messages
Informational Entire trace is below the threshold level.
The measurement cannot operate properly because the trace has fallen
completely below the threshold level. Change the threshold level to view
signal.
Informational Invalid format: CSV files are not supported by this
measurement.
When utilizing the Phase Noise Personality: Option 226, the *.CSV file
format is not available.
Informational Invalid EDGE burst timing.
The burst has manually been positioned off the display.
Informational Measurement halted. Press a measurement key to continue.
This error occurs after you choose
Cancel to refrain from setting the
attenuator to 0 dB during the Receive Channel Power and Receive Spur
measurements.
Informational No Fast ADC hardware installed. Meas unavailable.
The analyzer cannot use sweep times of less than 5 milliseconds when
Option B7D or Option AYX is not installed. Therefore the measurement
will not be executed.
Informational Not enough frequency range to measure harmonics for channel.
Selected harmonics are above the frequency range of the analyzer.
Informational One or more harmonics beyond freq limit: number decreased.
The highest harmonic was beyond the frequency limit of the analyzer, so
the number of measured harmonics was decreased.
Informational Option activated
This message is displayed after entering the selected option’s License Key.
Instrument Messages
Informational Please set RF input range (INPUT menu) to manual first.
In order to manually set the reference level and/or the attenuation under
Amplitude front-panel key, the RF Input Range menu under the Input
the
front-panel key must be set to
Man (manual).
Informational Shutdown in process.
The analyzer is responding to the
the shutdown procedure.
100Chapter 1
Standby key selection, and is executing
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.