Agilent Technologies E4400-90333 276, Because the device found it to be recursive see Ieee 488.2

Page 20

-299 to -200: Execution ErrorsESG Family Signal Generators

-276

Macro recursion error

 

A syntactically legal macro program data sequence could not be executed

 

because the device found it to be recursive (see IEEE 488.2, 10.7.6.4).

-275

Macro definition too long

 

A syntactically legal macro program data sequence could not be executed

 

because the string or block contents were too long for the device to handle

 

(see IEEE 488.2, 10.7.6.1).

-274

Macro parameter error

 

The macro definition improperly used a macro parameter placeholder (see

 

IEEE 488.2, 10.7.3).

-273

Illegal macro label

 

The macro label defined in the *DMC command was a legal string syntax,

 

but could not be accepted by the device (see IEEE 488.2, 10.7.3 and

 

10.7.6.2). For example, the label was too long, the same as a common

 

command header, or contained invalid header syntax.

-272

Macro execution error

 

A syntactically legal macro program data sequence could not be executed

 

due to an error within the macro definition (see IEEE 488.2, 10.7.6.3).

-271

Macro syntax error

 

A syntactically legal macro program data sequence, written in accordance

 

with IEEE 488.2, 10.7.2, could not be executed due to a syntax error

 

within the macro definition (see IEEE 488.2, 10.7.6.3).

-270

Macro error

 

A macro-related execution error occurred. This error message is used

 

when the device cannot detect the more specific errors described for errors

 

-271 through -279.

-261

Math error in expression

 

A syntactically legal expression program data element could not be

 

executed due to a math error. For example, a divide-by-zero was

 

attempted. The definition of a math error is device-specific.

18

Error Messages

Image 20
Contents Affix 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-Specific Errors Device has detected a failure during its self-test procedureNearest Agilent Technologies sales or service office 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-specific 285284 IllegalCommand header, or contained invalid header syntax Due to an error within the macro definition see Ieee 488.2Attempted. The definition of a math error is device-specific 276filename of was specified. This is not a legal filename An illegal memory subsystem name was used after the @File name error Illegal filename character File name not found SYSTEMFCDMA2KCHANFILE 254 Definition of what constitutes full media is device-specificCatalog. Afterwards, try again Try againSales or service office 252What constitutes missing media is device-specific 250Measurement accuracy is questionable Data corrupt or stale filename During the first power up after downloading new firmware into Algorithm. a potential cause is a failing backup batteryEeprom master copy if one exists. The system automatically 226223 Memory or related device-specific 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 Specified filename exceeds the maximum length Device cannot detect a more specific error Detect a more specific error150 148Header contains more than twelve characters see Ieee 488.2 110Command header error Syntax error 201 to 702 Device-Specific Errors Invalid file nameState file 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 filter must have at least one coefficient specified Modulation must have at least two states specifiedfile is either corrupt or is not a FIR file Burst shape file is corrupted, or is not in the proper format