Agilent Technologies E4400-90333 285, When parsing a downloaded program is device-specific, 284

Page 19

ESG Family Signal Generators

-299 to -200: Execution Errors

 

Program runtime error; Floating-Point Exception

 

A floating-point math error (such as a divide by zero) has been detected.

 

The system will attempt to recover automatically. Report this error to the

 

nearest Agilent Technologies sales or service office.

-285

Program syntax error

 

A syntax error appears within a downloaded program. The syntax used

 

when parsing a downloaded program is device-specific.

-284

Program currently running

 

Indicates that certain operations related to programs may be illegal while

 

the program is running. For example, deleting a running program may be

 

illegal.

-283

Illegal variable name

 

An attempt was made to reference a nonexistent variable.

-282

Illegal program name

 

The name used to reference a program was invalid. For example,

 

redefining an existing program, deleting a nonexistent program, or in

 

general, referencing a nonexistent program.

-281

Cannot create program

 

An attempt to create a program was unsuccessful. This may be due to

 

insufficient memory.

-280

Program error

 

A downloaded program-related execution error occurred. This error

 

message is used when the device cannot detect the more specific errors

 

described for errors -281 through -289. The syntax used in a program and

 

the mechanism for downloading a program is device-specific.

-278

Macro header not found

 

A syntactically legal macro label in the *GMC? query could not be executed

 

because the header was not previously defined.

-277

Macro redefinition not allowed

 

The macro label defined in the *DMC command could not be executed

 

because the macro label was already defined (see IEEE 488.2, 10.7.6.4).

Error Messages

17

Image 19
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 Errors321 Nearest Agilent Technologies sales or service officeSelf-test for a particular power supply voltage has failed. Burst generator memory failed. Modulation data produced byOut 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 320Values 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 memorySystem error File Not Found To -200 Execution Errors Illegal When parsing a downloaded program is device-specific285 284276 Command header, or contained invalid header syntaxDue to an error within the macro definition see Ieee 488.2 Attempted. The definition of a math error is device-specificAn 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 Try again 254Definition of what constitutes full media is device-specific Catalog. Afterwards, try again250 Sales or service office252 What constitutes missing media is device-specificMeasurement accuracy is questionable Data corrupt or stale filename 226 During the first power up after downloading new firmware intoAlgorithm. a potential cause is a failing backup battery Eeprom master copy if one exists. The system automaticallyMemory 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 220 For errors -221 throughError Manual mode is on and therefore the instrument cannot sweep211 Have described the error that is stalling list/sweep212 IgnoredExecution Error Cannot update FlexDG with Even Second Delay To -100 Command Errors Specified filename exceeds the maximum length 148 Device cannot detect a more specific errorDetect a more specific error 150Header 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 abortedInternal error report to factory Synthesizer is unlocked. Service may be neededInstrument’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 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