Agilent Technologies E4400-90333 manual Measurement accuracy is questionable

Page 26

-299 to -200: Execution Errors

ESG Family Signal Generators

Hardware missing; no such SIO address

The expected board is not installed. Report this error to the nearest

Agilent Technologies sales or service ofﬁce.

-240Hardware error

A legal program command or query could not be executed because of a hardware problem in the device. The deﬁnition of what constitutes a hardware problem is completely device-speciﬁc. This error is used when the device cannot detect the more speciﬁc errors described for errors -241 through -249.

-233Invalid version

A legal program data element was parsed but could not be executed because the version of the data is incorrect to the device. This particular error is used when ﬁle or block data elements are recognized by the instrument, but cannot be executed for reasons of version incompatibility. For example, a non-supported ﬁle version or a non-supported instrument version.

-232Invalid format

A legal program data element was parsed but could not be executed because the data format or structure is inappropriate. For example, when loading memory tables or when sending a SYSTem:SET parameter for an unknown instrument.

-231Data questionable

The measurement accuracy is questionable.

Data questionable; EEPROM copy of <filename>.

The EEPROM copy of a ﬁle has a correctable error. The system automatically performs the correction. A potential cause is a failing EEPROM. Report this error to the nearest Agilent Technologies sales or service ofﬁce.

Data questionable; RAM copy of <filename>.

The non-volatile RAM copy of a ﬁle has a correctable error. The system automatically performs the correction. A potential cause is a failing backup battery.

-230Data corrupt or stale

Possibly invalid data. A new reading was started but not completed since last access.

24	Error Messages

Image 26

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 procedureBurst generator memory failed. Modulation data produced by Nearest Agilent Technologies sales or service ofﬁceSelf-test for a particular power supply voltage has failed. 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 320 Lost. The meaning of this error is device-dependentInstrument is still functional 315An error was detected in the device’s memory Non-volatile data saved by the *SAV? command has been lostProtected user data saved by the *PUD command has been lost ValuesSystem error File Not Found To -200 Execution Errors 284 When parsing a downloaded program is device-speciﬁc285 IllegalAttempted. The deﬁnition of a math error is device-speciﬁc Command header, or contained invalid header syntaxDue to an error within the macro deﬁnition see Ieee 488.2 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 Catalog. Afterwards, try again 254Deﬁnition of what constitutes full media is device-speciﬁc Try againWhat constitutes missing media is device-speciﬁc Sales or service ofﬁce252 250Measurement accuracy is questionable Data corrupt or stale filename Eeprom master copy if one exists. The system automatically During the ﬁrst power up after downloading new ﬁrmware intoAlgorithm. a potential cause is a failing backup battery 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 Manual mode is on and therefore the instrument cannot sweep For errors -221 throughError 220Ignored Have described the error that is stalling list/sweep212 211Execution Error Cannot update FlexDG with Even Second Delay To -100 Command Errors Speciﬁed ﬁlename exceeds the maximum length 150 Device cannot detect a more speciﬁc errorDetect a more speciﬁc error 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