Manuals / Agilent Technologies / Lawn and Garden / Portable Generator

Agilent Technologies E4400-90333 manual Data corrupt or stale filename

Models: E4400-90333

1 72

Download 72 pages 43.69 Kb

Page 27

Image 27

ESG Family Signal Generators

-299 to -200: Execution Errors

Data corrupt or stale; <filename>.

The sequence ﬁle that you are attempting to run is the wrong size.

Data corrupt or stale; <NAME> differs offset 0x<VALUE>: NVRAM 0x<VALUE>, EEPROM 0x<VALUE>.

This message can occur only if full power-on EEPROM comparison mode is set by the factory. If this mode is set, this message indicates that the data that was retained by the EEPROM did not match the shadow data that was retained by the shadow non-volatile RAM, even though no uncorrectable errors or CRC mismatch was found in the shadow memory. This error usually indicates that the instrument lost power during EEPROM programming. If the instrument was quiescent when it was powered off, report this error to the nearest Agilent Technologies sales or service ofﬁce.

Data corrupt or stale; EEPROM @ offset 0x<VALUE>: wrote 0x<VALUE>, read 0x<VALUE>.

After writing shadow RAM data to EEPROM, a memory comparison detected a difference. The EEPROM may not be retaining data properly. Report this error to the nearest Agilent Technologies sales or service ofﬁce.

Data corrupt or stale; EEPROM copy of <filename>.

The EEPROM copy of a ﬁle 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 ﬁle is left as it is. Report this error to the nearest Agilent Technologies sales or service ofﬁce.

Data corrupt or stale; Either the file is not a bit file, or the number of bits specified does not match with the number of data bytes in the file.

An error has occurred while downloading a user ﬁle to the Bit memory catalog. Either the user ﬁle is not a bit ﬁle, or the number of bits speciﬁed in the SCPI command does not match the number of bytes in the ﬁle. Ensure that the bit speciﬁer matches the actual number of bits in the ﬁle.

Data corrupt or stale; file @ offset 0x<VALUE>: wrote 0x<VALUE>, retained 0x<VALUE>.

After writing shadow RAM data to EEPROM, a memory comparison detected a difference. The EEPROM may not be retaining data properly. Report this error to the nearest Agilent Technologies sales or service ofﬁce.

Error Messages

25

Image 27

Agilent Technologies E4400-90333 manual Data corrupt or stale filename

Contents

Supersedes February Copyright 1999-2001 Agilent Technologies Afﬁx Label Here Part No. E4400-90333 Contents 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-Speciﬁc Errors 321 Nearest Agilent Technologies sales or service ofﬁceSelf-test for a particular power supply voltage has failed. Burst generator memory failed. Modulation data produced by Out 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 315 Lost. The meaning of this error is device-dependentInstrument is still functional 320 Values Non-volatile data saved by the *SAV? command has been lostProtected user data saved by the *PUD command has been lost An error was detected in the device’s memory System error File Not Found To -200 Execution Errors Illegal When parsing a downloaded program is device-speciﬁc285 284 276 Command header, or contained invalid header syntaxDue to an error within the macro deﬁnition see Ieee 488.2 Attempted. The deﬁnition of a math error is device-speciﬁc An illegal memory subsystem name was used after the @ ﬁlename of was speciﬁed. This is not a legal ﬁlename File name error Illegal filename character File name not found SYSTEMFCDMA2KCHANFILE Try again 254Deﬁnition of what constitutes full media is device-speciﬁc Catalog. Afterwards, try again 250 Sales or service ofﬁce252 What constitutes missing media is device-speciﬁc Measurement accuracy is questionable Data corrupt or stale filename 226 During the ﬁrst power up after downloading new ﬁrmware intoAlgorithm. a potential cause is a failing backup battery Eeprom master copy if one exists. The system automatically Memory or related device-speciﬁc requirements 223 To -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 RC1 To -200 Execution Errors ESG Family Signal Generators 220 For errors -221 throughError Manual mode is on and therefore the instrument cannot sweep 211 Have described the error that is stalling list/sweep212 Ignored Execution Error Cannot update FlexDG with Even Second Delay To -100 Command Errors Speciﬁed ﬁlename exceeds the maximum length 148 Device cannot detect a more speciﬁc errorDetect a more speciﬁc error 150 Header contains more than twelve characters see Ieee 488.2 110Command header error Syntax error Invalid ﬁle name 201 to 702 Device-Speciﬁc Errors User has attempted to write to a read-only memory subsystem State ﬁle is not readable and the recall was aborted Synthesizer is unlocked. Service may be needed Internal error report to factoryInstrument’s output is unleveled 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 code Fpga download failed Demodulator board Modulation must have at least two states speciﬁed ﬁlter must have at least one coefﬁcient speciﬁed Burst shape ﬁle is corrupted, or is not in the proper format ﬁle is either corrupt or is not a FIR ﬁle