Agilent Technologies E4400-90333 manual To -300 Device-Speciﬁc Errors

Page 8

-399 to -300: Device-Speciﬁc Errors

ESG Family Signal Generators

-399 to -300: Device-Speciﬁc Errors

Some device operations did not properly complete, possibly due to an abnormal hardware or ﬁrmware condition. These codes are also used for self-test response errors. Errors in this class set the device-speciﬁc error bit (bit 3) in the event status register (IEEE 488.2, section 11.5.1).

-362Framing error in program message

A stop bit was not detected when data was received (for example, a baud rate mismatch).

-361Parity error in program message

The parity bit was not correct when data was received (for example, an incorrect parity bit on a serial port).

-360Communication error

This is the generic communication error for devices that cannot detect the more speciﬁc errors described for errors -361 and -362.

-350Queue overflow

This is a speciﬁc code entered into the queue in lieu of the code that caused the error. This message indicates that there is no more room in the queue and an error occurred but was not recorded.

-340Calibration failed

The device has detected a failure during its calibration procedure.

-330Self-test failed

The device has detected a failure during its self-test procedure.

Self-test failed; Bad address position @ 0x____

The data generator memory failed. Modulation data produced by the data generator may not be correct. An address that appeared to have a failed address line was reported. Report this error to the nearest

Agilent Technologies sales or service ofﬁce.

6	Error Messages

Image 8

Contents Afﬁx Label Here Part No. E4400-90333 Supersedes February Copyright 1999-2001 Agilent TechnologiesContents Introduction Error Message Format Error Message Types No Error To -400 Query Errors To -300 Device-Speciﬁc Errors Device has detected a failure during its self-test procedureNearest Agilent Technologies sales or service ofﬁce Self-test for a particular power supply voltage has failed.Burst 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 Lost. The meaning of this error is device-dependent Instrument is still functional320 315Non-volatile data saved by the *SAV? command has been lost Protected user data saved by the *PUD command has been lostAn error was detected in the device’s memory ValuesSystem error File Not Found To -200 Execution Errors When parsing a downloaded program is device-speciﬁc 285284 IllegalCommand header, or contained invalid header syntax Due to an error within the macro deﬁnition see Ieee 488.2Attempted. The deﬁnition of a math error is device-speciﬁc 276ﬁlename of was speciﬁed. This is not a legal ﬁlename An illegal memory subsystem name was used after the @File name error Illegal filename character File name not found SYSTEMFCDMA2KCHANFILE 254 Deﬁnition of what constitutes full media is device-speciﬁcCatalog. Afterwards, try again Try againSales or service ofﬁce 252What constitutes missing media is device-speciﬁc 250Measurement accuracy is questionable Data corrupt or stale filename During the ﬁrst power up after downloading new ﬁrmware into Algorithm. a potential cause is a failing backup batteryEeprom master copy if one exists. The system automatically 226223 Memory or related device-speciﬁc requirementsTo -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 RC1 Used in RC3 and 4 for channelTo -200 Execution Errors ESG Family Signal Generators For errors -221 through ErrorManual mode is on and therefore the instrument cannot sweep 220Have described the error that is stalling list/sweep 212Ignored 211Execution Error Cannot update FlexDG with Even Second Delay To -100 Command Errors Speciﬁed ﬁlename exceeds the maximum length Device cannot detect a more speciﬁc error Detect a more speciﬁc error150 148Header contains more than twelve characters see Ieee 488.2 110Command header error Syntax error 201 to 702 Device-Speciﬁc Errors Invalid ﬁle nameState ﬁle is not readable and the recall was aborted User has attempted to write to a read-only memory subsystemInstrument’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 Demodulator board has an invalid revision of DSP boot code Option UN7 hardware has an invalid revision of Fpga codeFpga download failed Demodulator board ﬁlter must have at least one coefﬁcient speciﬁed Modulation must have at least two states speciﬁedﬁle is either corrupt or is not a FIR ﬁle Burst shape ﬁle is corrupted, or is not in the proper format