Agilent Technologies E4400-90333 manual Error Message Types

Page 5

ESG Family Signal Generators

Error Message Types

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.

Query Errors (–499 to –400)indicate that the instrument’s output queue control has detected a problem with the message exchange protocol described in IEEE 4888.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.

Device Specific Errors (–399 to –300and 201 to 702) 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 by the instrument’s execution control block. Errors in this class set the execution error bit (bit 4) in the event status register (IEEE 488.2, section 11.5.1). In this case:

Either a <PROGRAM DATA> element following a header was evaluated by the device as outside of its legal input range or is otherwise inconsistent with the device’s capabilities, or

a valid program message could not be properly executed due to some device condition.

Execution errors are reported after rounding and expression evaluation operations are completed. Rounding a numeric data element, for example, is not reported as an execution error.

Command Errors (–199 to –100)indicate that the instrument’s 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 that 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.

Error Messages

3

Image 5
Contents Supersedes February Copyright 1999-2001 Agilent Technologies Affix Label Here Part No. E4400-90333Contents Introduction Error Message Format Error Message Types No Error To -400 Query Errors Device has detected a failure during its self-test procedure To -300 Device-Specific ErrorsSelf-test for a particular power supply voltage has failed. Nearest Agilent Technologies sales or service officeBurst generator memory failed. Modulation data produced by 321Out of memory ARB communication failed Out of memory Could not copy current istate Out of memory Histogram display cannot function Out of memory Memory allocation error Out of memory Object Memory Area Instrument is still functional Lost. The meaning of this error is device-dependent320 315Protected user data saved by the *PUD command has been lost Non-volatile data saved by the *SAV? command has been lostAn error was detected in the device’s memory ValuesSystem error File Not Found To -200 Execution Errors 285 When parsing a downloaded program is device-specific284 IllegalDue to an error within the macro definition see Ieee 488.2 Command header, or contained invalid header syntaxAttempted. The definition of a math error is device-specific 276An illegal memory subsystem name was used after the @ filename of was specified. This is not a legal filenameFile name error Illegal filename character File name not found SYSTEMFCDMA2KCHANFILE Definition of what constitutes full media is device-specific 254Catalog. Afterwards, try again Try again252 Sales or service officeWhat constitutes missing media is device-specific 250Measurement accuracy is questionable Data corrupt or stale filename Algorithm. a potential cause is a failing backup battery During the first power up after downloading new firmware intoEeprom master copy if one exists. The system automatically 226Memory or related device-specific requirements 223To -200 Execution Errors Too much data User filter has too many symbols Data out of range Synthesizer Frequency out of bounds Data out of range value clipped to upper limit To -200 Execution Errors All digital modulation multicarriers must be the same format To -200 Execution Errors ESG Family Signal Generators Settings conflict Edge Bert requires Normal as Timeslot Type Settings conflict FM & PM not allowed Settings conflict GSM Bert requires Normal as Timeslot Type ESG Family Signal Generators Settings conflict I/Q & AM WB cannot be on at the same time ESG Family Signal Generators To -200 Execution Errors Used in RC3 and 4 for channel Used in RC1To -200 Execution Errors ESG Family Signal Generators Error For errors -221 throughManual mode is on and therefore the instrument cannot sweep 220212 Have described the error that is stalling list/sweepIgnored 211Execution Error Cannot update FlexDG with Even Second Delay To -100 Command Errors Specified filename exceeds the maximum length Detect a more specific error Device cannot detect a more specific error150 148Header contains more than twelve characters see Ieee 488.2 110Command header error Syntax error Invalid file name 201 to 702 Device-Specific ErrorsUser has attempted to write to a read-only memory subsystem State file is not readable and the recall was abortedInstrument’s output is unleveled Synthesizer is unlocked. Service may be neededInternal error report to factory 513 1 GHz Oscillator unlocked Calibration failure Dcfm DC overrange Reverse Power Protection RPP Tripped DSP FW download failed Demodulator board DSP times out Demodulator communication failed Option 300 DSP for Bert capability returns an error Configuration Error Option reconfiguration failed Configuration error Installed board not supported Configuration error OPTION, Invalid inconsistent license key Option UN7 hardware has an invalid revision of Fpga code Demodulator board has an invalid revision of DSP boot codeFpga download failed Demodulator board Modulation must have at least two states specified filter must have at least one coefficient specifiedBurst shape file is corrupted, or is not in the proper format file is either corrupt or is not a FIR file