Instrument Messages and
Functional Tests
Agilent Technologies PSA Spectrum Analyzers
This manual provides documentation for the following instrument:
Agilent Technologies PSA Series
E4440A (3 Hz – 26.5 GHz)
Manufacturing Part Number: E4440-90030
Printed in USA
January 2001
© Copyright 2001 Agilent Technologies
The information contained in this document is subject to change
without notice.
Agilent T echnologies makes no warranty of any kind with r egard to this
material, including but not limited to, the implied warranties of
merchantability and fitness for a particular pur pose. Agilent
Technologies shall not be liable for errors contained herein or for
incidental or consequential damages in connect ion with the furnishing,
performance, or use of this material.
Where to Find the Latest Information
Documentation is updated periodically. Fo r the latest information about
Agilent PSA spectrum analyzers, including firmware upgrades and
application information, see: http://www.agilent.com/find/psa.
ii
Contents
1. Instrument Messages
Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Error Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Error Message Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Error Message Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
0: No Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
−499 to −400: Query Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
−399 to −300: Device-Specific Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
−299 to −200: Execution Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
−199 to −100: Command Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
102 to 799: Device-Specific Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Informational Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Status Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2. Functional Tests
Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Performing Functional Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Required Test Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Amplitude Accuracy at 50 MHz . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Testing Option 1DS (Preamp) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Displayed Average Noise Level (DANL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Frequency Readout Accuracy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Frequency Response (Flatness) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Amplitude Linearity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Second Harmonic Distortion (SHD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Index
iii
1 Instrument Messages
This chapter describes the following types of messages displayed on the analyzer:
• Error Messages, beginning on page 2, appear at the bottom of the screen in the status
line.
These messages normally indicate that a user-error has occurred as a result of either
front-panel or remote interface activity.
• Informational Messages, beginning on page 16, appear at the bottom of the screen in
the status line
These messages simply provide information; you are not required to do anything.
• Status Messages, beginning on page 17, appear in the upper-right portion of the screen
grid
These messages indicate conditions that can cause the display of incorre ct data.
1
Instrument Messages
Error Messages
Error Messages
Error messages appear at the bottom of the screen in the status line (in yellow on color
displays). This section provides information to help you understand and resolve errors:
• An overview of error queues, below.
• An overview of the information provided in an error message, on page 3.
• A description of the types of error messages, on page 4.
• A description of error messages , grouped by type, beginning on page 5.
Error Queues
There are two types of errors in the instrument, and two corresponding error queues:
• Front panel
• Remote interface (SCPI)
If an error condition occurs , it may be reported to both error queues.
These two queues are viewed and managed separately, as described in the following table.
Characteristic
Capacity
(number of errors)
Overflow Handling
Viewing Entries
Clearing 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.
Circular (rotating).
Drops oldest error as new error comes in.
Press:
Press:
System, Show Errors, Clear Error Queue
Front-Panel Display
Error Queue
11 30
System, Show Errors
a
SCPI Remote Interface
Error Queue
Linear, first-in/first-out.
Replaces newest error with:
350,Queue overflow
−
Use SCPI query
SYSTem:ERRor?
Power up .
Send a *CLS command.
Read last item in the queue.
2 Chapter 1
Instrument Messages
Error Messages
Error Message Information
The system-defined error numbers are chosen on an enumerated (“1 of N”) basis. The
<error description > portion of the error query response (not the number) appears at the
bottom of the screen in the status line (in yellow on color displays).
NOTE To see an error number, view the error queue as described on page 2.
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. In selecting the proper error number to report, more sp ecific error codes are
preferred.
There are also references in this chapter 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.
Chapter 1 3
Instrument Messages
Error Messages
Error Message Types
Events do not generate more than one type of error. For example , an event that gener ates a
query error will not generate a device-specific, execution, or command error.
Query Errors (–499 to –400) indicate that the instrument output queue control has
detected a problem with the message exchange protocol described in IEEE 488.2, Ch apter
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.
Device-Specific Errors (–399 to –300 and 102 to 799) 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 defined by SCPI. A positive error
indicates that the instrument detected an error within the GPIB system, within the
instrument’s firmware or hardware, during the transfer of block data, or during
calibration.
Execution Errors (–299 to –200) indicate that an error has been detected during
instrument execution.
Command Errors (–199 to –100) indicate that the instrument 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
• an unrecognized header was received. These include incorrect device-specific headers
and incorrect or unimplemented IEEE 488.2 common commands.
4 Chapter 1
Instrument Messages
Error Messages
0: No Error
NOTE Error numbers are displayed in the error queue, not on the display.
To s ee an error number, view the error queue as described on page 2.
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.
Chapter 1 5
Instrument Messages
Error Messages
−499 to −400: Query Errors
The instrument 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.
NOTE Error numbers are displayed in the error queue, not on the display.
To s ee an error number, view the error queue as described on page 2.
−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 IEE 488.2, 11.5.1.1.7 and 6.3 has occurred.
6 Chapter 1
Instrument Messages
Error Messages
−399 to −300: Device-Specific Errors
Some device operations did not properly complete, possibly due to an abnormal hardware
or firmware condition. These codes are also used fo r self-test re sponse 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).
NOTE Error numbers are displayed in the error queue, not on the display.
To s ee an error number, view the error queue as described on page 2.
−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.
−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
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 1 7
Instrument Messages
Error Messages
−299 to −200: Execution Errors
An error has been detected by the instr ument’ s ex ecution contro l block. Errors in this cl ass
set the execution error bit (bit 4) in the event status register (IEEE 488.2, section 11.5.1).
NOTE Error numbers are displayed in the error queue, not on the display.
To s ee an error number, view the error queue as described on page 2.
−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
Missing device hardware. For example, an option is not installed.
Hardware missing; no such SIO address
The expected board is not installed. Report this error to the nearest Agilent Technologies sales or
service office.
−230 Data corrupt or stale
Possibly invalid data. A new measurement was started but not completed.
Data corrupt or stale; RAM copy of EEPROM
The EEPROM copy of a 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.
Data corrupt or stale; RAM copy of EEPROM
The non-volatile RAM copy of a file is either corrupt or is out of date with the EEPROM master
copy (if one exists). The system automatically re-initializes the file from EEPROM (if
appropriate) or from a default algorithm. A potential cause is a failing backup battery.
−224 Illegal parameter value
You have sent a parameter for this command that is not allowed. See the Function Reference.
8 Chapter 1
−222 Data out of range
A legal program data element was parsed but could not be execute d because the interpreted
value was outside the legal range defined by the device (see IEEE 488.2 11.5.1.1.5).
−221 Settings conflict; Command incompatible with span 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.
Settings conflict; Command incompatible with band pair marker
Using remote commands, you have tried to adjust the center frequency or span of a delta pai r
marker. You can adjust only the reference ma rker frequency or the delta marker frequency.
−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.
Instrument Messages
Error Messages
Chapter 1 9
Instrument Messages
Error Messages
−199 to −100: Command Errors
The instrument 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 whic h violates device listening formats or whose type
is unacceptable to the device.), or
• an unrecognized header was received. These include incorrect device-specific headers
and incorrect or unimplemented IEEE 488.2 common commands.
NOTE Error numbers are displayed in the error queue, not on the display.
To s ee an error number, view the error queue as described on page 2.
−120 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 types. This message is used if the device
cannot detect a more specific error.
−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.
10 Chapter 1
Instrument Messages
Error Messages
102 to 799: Device-Specific Errors
Some device operations did not properly complete, possibly due to an abnormal hardware
or firmware condition. These codes are also used fo r self-test re sponse 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 defined by SCPI. A positive error
indicates that the instrument detected an error within the GPIB system, within the
instrument firmware or hardware, during the transfer of block data, or during calibration.
NOTE Error numbers are displayed in the error queue, not on the display.
To s ee an error number, view the error queue as described on page 2.
102 High 50MHz Power Level
There is too much 50 MHz energy at the RF port for alignments to run. Reduce input power and
run alignments again.
103 Sampling Oscillator Unlock
Report this error to the nearest Agilent Technologies sales or service office.
104 1st LO Unlock
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.
107 Sample Clock Unlock
Report this error to the nearest Agilent Technologies sales or service office.
108 Cal Oscillator Unlock
Report this error to the nearest Agilent Technologies sales or service office.
Chapter 1 11
Loading...