How it Works
Agilent Technologies
Loading...
E4400-90333
User Manual
72 pgs700.1 Kb0

Agilent Technologies E4400-90333 User Manual

Error Messages
Agilent Technologies
ESG Family Signal Generators
Serial Number Prefixes:
(Affix Label Here)
Part No. E4400-90333
Printed in USA
June 2001
Supersedes February 2001
Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Error Message Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Error Message Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
0: No Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
-499 to -400: Query Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
-399 to -300: Device-Specific Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
-299 to -200: Execution Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
-199 to -100: Command Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
201 to 702: Device-Specific Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
iii
ESG Family Signal Generators

Introduction

If an error condition occurs in the signal generator, it is reported to both the front panel display error queue and the SCPI (remote interface) error queue. These two queues are viewed and managed separately.
NOTE When there is an unviewed message in the front panel error queue, the ERR
annunciator appears on the signal generator’s display.
Characteristic Front Panel Display
Error Queue
Capacity (#errors) 30 30
Circular (rotating).
Overflow Handling
Viewing Entries
Clearing the Queue Press:
Permanent Errors (errors thatmustberesolved. For example: unlock, avalanched, and hi/lo)
Drops oldest error as new error comes in.
Press:
Utility > Error Info > View Next
(or Previous) Error Message
Utility > Error Info > Clear Error Queue(s)
Re-reported after queue is cleared.
SCPI Remote Interface
Error Queue
Linear, first-in/first-out. Replaces newest error with: -350, Queue
overflow
Use SCPI query
SYSTem:ERRor? or STATus:QUEue?
Power up Send a *CLS command Read last item in the queue
Re-reported after queue is cleared.
1
Error Message Format ESG Family Signal Generators

Error Message Format

The system-defined error numbers are chosen on an enumerated (“1 of N”) basis. The SCPI-defined error numbers and the <error_description> portions of the error query response are displayed on the instrument.
In this chapter, an explanation is included with each error to further clarify its meaning. The first error described in each class (for example, -400, -300, -200, -100) is a “generic” error. In selecting the proper error number to report, more specific error codes are preferred.
Error messages appear in the lower-left corner of the display.
2 ErrorMessages
ESG Family Signal Generators Error Message Types

Error Message Types

Events do not generate more than onetype of error.Forexample, an event that generates a query error will not generate a device-specific, execution, or command error.
Query Errors (–499 to –400) indicate that the instrument’s output queue control has detected a problem with the message exchange protocol described in IEEE 4888.2, Chapter 6. Errors in this class set the query error bit (bit 2) in the event status register (IEEE 488.2, section 11.5.1). These errors correspond to message exchange protocol errors described in IEEE 488.2, 6.5. In this case:
• Either an attempt is being made to read data from the output queue when no output is either present or pending, or
• data in the output queue has been lost.
Device Specific Errors (–399 to –300 and 201 to 702) indicate that a device operation did not properly complete, possibly due to an abnormal hardware or firmware condition. These codes are also used for self-test response errors. Errors in this class set the device-specific error bit (bit 3) in the event status register (IEEE 488.2, section 11.5.1).
The <error_message> string for a positive error is not defined by SCPI. A positive error indicates that the instrument detected an error within the GPIB system, within the instrument’s firmware or hardware, during the transfer of block data, or during calibration.
Execution Errors (–299 to –200) indicate that an error has been detected by the instrument’s execution control block. Errors in this class set the execution error bit (bit 4) in the event status register (IEEE 488.2, section 11.5.1). In this case:
• Either a <PROGRAM DATA> element following a header was evaluated by the device as outside of its legal input range or is otherwise inconsistent with the device’s capabilities, or
• a valid program message could not be properly executed due to some device condition.
Execution errors are reported after rounding and expression evaluation operations are completed. Rounding a numeric data element, for example, is not reported as an execution error.
Command Errors (–199 to –100) indicate that the instrument’s parser detected an IEEE 488.2 syntax error. Errors in this class set the command error bit (bit 5) in the event status register (IEEE 488.2, section 11.5.1). In this case:
• Either an IEEE 488.2 syntax error has been detected by the parser (a control-to-device message was received that is in violation of the IEEE 488.2 standard. Possible violations include a data element that violates device listening formats or whose type is unacceptable to the device.), or
• an unrecognized header was received. These include incorrect device-specific headers and incorrect or unimplemented IEEE 488.2 common commands.
Error Messages 3
0: No Error ESG Family Signal Generators
0: No Error
0 No error, No Error Message(s) in Queue
The queue is empty. Every error in the queue has been read, or the queue was purposely cleared using either the
Clear Error Queue(s) softkey or *CLS.
4 ErrorMessages
ESG Family Signal Generators -499 to -400: Query Errors
-499 to -400: Query Errors
The instrument’s output queue control has detected a problem with the message exchange protocol described in IEEE 4888.2, Chapter 6. Errors in this class set the query error bit (bit 2) in the event status register (IEEE 488.2, section 11.5.1). These errors correspond to message exchange protocol errors described in IEEE 488.2, 6.5.
In this case, either an attempt is being made to read data from the output queue when no output is either present or pending, or data in the output queue has been lost.
-440 Query UNTERMINATED after indefinite response
A query was received in the same program message in which a query requesting an indefinite response was executed (see IEEE 488.2, 6.3.7.5).
-430 Query DEADLOCKED
A condition causing a DEADLOCKED query error occurred (see IEEE 488.2, 6.3.1.7). For example, both the input buffer and the output buffer are full and the device cannot continue.
Query DEADLOCKED
A SCPI output queue has filled, preventing further SCPI command execution, and there is no more room left in the corresponding SCPI input queue to accept a query to read from the output queue. The system automatically discards output to correct the deadlock.
-420 Query UNTERMINATED
A condition causing an UNTERMINATED query error occurred (see IEEE 488.2, 6.3.2.2). For example, the device was addressed to talk and an incomplete program message was received.
-410 Query INTERRUPTED
A condition causing an INTERRUPTED query error occurred (see IEEE 488.2, 6.3.2.7). For example, a query was followed by DAB or GET before a response was completely sent.
-400 Query Error
This is a generic query error for devices that cannot detect more specific errors. The code indicates only that a query error as defined in IEE 488.2,
11.5.1.1.7 and 6.3 has occurred.
Error Messages 5
-399 to -300: Device-Specific Errors ESG Family Signal Generators
-399 to -300: Device-Specific Errors
Some device operations did not properly complete, possibly due to an abnormal hardware or firmware condition. These codes are also used for self-test response errors. Errors in this class set the device-specific error bit (bit 3) in the event status register (IEEE 488.2, section 11.5.1).
-362 Framing error in program message A stop bit was not detected when data was received (for example, a baud
rate mismatch).
-361 Parity error in program message The parity bit was not correct when data was received (for example, an
incorrect parity bit on a serial port).
-360 Communication error This is the generic communication error for devices that cannot detect the
more specific errors described for errors -361 and -362.
-350 Queue overflow This is a specific 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.
-340 Calibration failed The device has detected a failure during its calibration procedure.
-330 Self-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 office.
6 ErrorMessages
ESG Family Signal Generators -399 to -300: Device-Specific Errors
Self-test failed; Burst Generator Memory Test @ 0x____
The burst generator memory failed. Modulation data produced by the burst generator may not be correct. However, if an Unable to check Burst Generator Memory error was also seen, this result is not conclusive. The address of the first location that failed is reported. Report this error to the nearest Agilent Technologies sales or service office.
Self-test failed; Chips ___, ___ aliased @ 0x____
The data generator memory failed. Modulation data produced by the data generator may not be correct. An address that appeared to be aliased across multiple memory chips has been reported. Report this error to the nearest Agilent Technologies sales or service office.
Self-test failed; Data Generator Memory Test @ 0x____
The data generator memory failed. Modulation data produced by the data generator may not be correct. However, if an Unable to check Data Generator Memory error was also seen, this result is not conclusive. The address of the first location that failed is reported. Report this error to the nearest Agilent Technologies sales or service office.
Self-test failed; EEPROM header checksum error <card_name>.
The card identification header for a hardware card is incorrect. If the card is not properly identified, the instrument is likely to be non-functional. Report this error to the nearest Agilent Technologies sales or service office.
Self-test failed; Power supply self-test failure
The self-test for a particular power supply voltage has failed. The instrument is likely not functional. Report this error to the nearest Agilent Technologies sales or service office.
-321 Out of memory An internal operation needed more memory than was available.
Out of memory
There is insufficient working memory available. Report this error to the nearest Agilent Technologies sales or service office.
Out of memory
Insufficient working memory during arbitrary waveform generation. Report this error to the nearest Agilent Technologies sales or service office.
Error Messages 7
-399 to -300: Device-Specific Errors ESG Family Signal Generators
Out of memory
There was insufficient working memory during data generation pattern calculations. Reduce the size of any sweep lists and try again.
Out of memory
If this occurs during a memory catalogdisplay, it means the system did not have enough free RAM to prepare the catalog.
Out of memory; ARB communication failed.
There was insufficient memory to complete the dual arbitrary waveform generator (Option UND) communications. Report this error to the nearest Agilent Technologies sales or service office.
Out of memory; ARB is not functional.
There is insufficient memory to the ARB to generate the requested waveform.
Out of memory; Burst shape RAM cannot hold specified burst shape.
There is insufficient working memory available. Report this error to the nearest Agilent Technologies sales or service office.
Out of memory; Cannot create memory manager
A file system memory manager detected an internal error condition. Report this error to the nearest Agilent Technologies sales or service office.
Out of memory; Cannot precalculate frequencies. Try fewer frequencies.
Indicates that memory was exhausted during frequency precalculation (used to speed the process of sweep/list mode). List mode cannot run until either fewer frequencies have been supplied or more memory becomes available and the same set of frequencies are sent again, FREQ:MODE CW is executed, or :FREQ:MODE LIST is executed.
Out of memory; Cannot uncompress file.
A STATE: file cannot be uncompressed because there is not enough memory to run the decompression algorithm. Recall will fail and there will be no instrument state change. Reduce the size of any sweep lists and try again.
8 ErrorMessages
ESG Family Signal Generators -399 to -300: Device-Specific Errors
Out of memory; Complementary Cumulative Distribution. Display cannot function.
There is insufficient working memory available. Report this error to the nearest Agilent Technologies sales or service office.
Out of memory; Could not copy current istate.
An instrument state operation, such as save/recall, could not allocate enough space to copy an instrument state. The operation is aborted.
Out of memory; Display system out of memory. An abnormal display may result. Memory consumption should be reduced.
There was not enough memory in the system to properly update the display. Some inconsistencies may be seen. The size of any list/sweep should be reduced, and the source should be preset to clear up any inconsistencies. Report this error to the nearest Agilent Technologies sales or service office.
Out of memory; FFT display cannot function.
There is insufficient working memory available. Report this error to the nearest Agilent Technologies sales or service office.
Out of memory; FFT subsystem cannot function.
There is insufficient working memory available. Report this error to the nearest Agilent Technologies sales or service or service office.
Out of memory; File exceeds digital modulation memory size.
A digital modulation input file would result in more pattern data being generated than can fit in the pattern memory.
Out of memory; FIR subsystem generated more coefficients than the hardware can handle.
There is insufficient working memory available. Report this error to the nearest Agilent Technologies sales or service office.
Out of memory; FIR subsystem unable to operate.
There is insufficient working memory available. Report this error to the nearest Agilent Technologies sales or service office.
Out of memory; Graph subsystem cannot function.
There is insufficient working memory available. Report this error to the nearest Agilent Technologies sales or service office.
Error Messages 9
-399 to -300: Device-Specific Errors ESG Family Signal Generators
Out of memory; Histogram display cannot function.
There is insufficient working memory available. Report this error to the nearest Agilent Technologies sales or service office.
Out of memory; Impulse response display cannot function.
There is insufficient working memory available. Report this error to the nearest Agilent Technologies sales or service office.
Out of memory; There is insufficient memory to copy the current pattern. The secondary pattern is unchanged.
There was insufficient room to copy or create the current data generation pattern data in order to make it a secondary pattern. To avoid this, set up the smaller of the two patterns first.
Out of memory; There is insufficient memory to store the secondary frame in Pattern RAM. The secondary frame has been turned off.
There was insufficient room to copy or create the current data generation pattern data in order to make it a secondary pattern. To avoid this, set up the smaller of the two patterns first.
Out of memory; Insufficient RAM
A memory comparison between a shadow RAM data area and the corresponding EEPROM data area could not be performed due to insufficient working RAM. This does not necessarily imply a memory problem, since this comparison is only used in stringent diagnostic situations.
Out of memory; I/Q map display cannot function.
There is insufficient working memory available. Report this error to the nearest Agilent Technologies sales or service office.
Out of memory; List formation
The device was unable to allocate space for a lookup table, such as for list mode precalculation. List mode cannot run until either fewer frequencies have been supplied or more memory becomes available and the same set of frequencies are sent again, FREQ:MODE CW is executed, or :FREQ:MODE LIST is executed.
10 ErrorMessages
ESG Family Signal Generators -399 to -300: Device-Specific Errors
Out of memory; Memory allocation error.
There is insufficient working memory available. Report this error to the nearest Agilent Technologies sales or service office.
Out of memory; Memory catalog failed.
There is not enough memory to complete a catalog listing. Reduce the size of any sweep lists and try again.
Out of memory; Memory request failed, out of indices. Memory request greater than total memory size.
A file system memory manager detected an internal error condition. Report this error to the nearest Agilent Technologies sales or service office.
Out of memory; Modulation subsystem unable to operate. There is insufficient working memory available. Report this error to the
nearest Agilent Technologies sales or service office.
Out of memory; Not enough memory to buffer paging message.
There is not enough memory to buffer the asynchronous paging message, so it will not be played. Reduce the size of any list/sweep, and preset the source to clear up any inconsistencies. If the problem persists report this error to the nearest Agilent Technologies sales or service office.
Out of memory; Not enough memory to create progress bar.
There is not enough memory to create a progress bar. Reduce the size of any list/sweep, and preset the source to clear up any inconsistencies. If the problem persists report thiserror to the nearest Agilent Technologiessales or service office.
Out of memory; Not enough memory to read data file.
There is not enough memory to read the specified data file. Try a smaller file. Reduce the sizeof any list/sweep, and presetthe source to clear up any inconsistencies. If the problem persists report this error to the nearest Agilent Technologies sales or service office.
Out of memory; The pre-coded bit data for this transport channel is not generated due to the memory overflow or memory allocation error.
Reduce the amount of coding applied to data or decrease the amount of data.
Error Messages 11
-399 to -300: Device-Specific Errors ESG Family Signal Generators
Out of memory; There is not enough memory to create the modulation. Baseband cannot function.
There is not enough memory to create the modulation map. Reduce the size of any list/sweep, and preset the source to clear up any inconsistencies. If the problem persists report this error to the nearest Agilent Technologies sales or service office.
Out of memory; Object Memory Area
Indicates that memory was exhausted during instrument power-on. Report this error to the nearest Agilent Technologies sales or service office.
Out of memory; Pattern exceeds digital modulation memory size. If a user file is selected, it may be too large.
The user has specified a data file or other generation parameters that would require more data generation pattern memory than is available with the particular data generator installed in the instrument.
Out of memory; PRBS xx/xx
There was not enough memory to apply a scramble to data for the baseband generator. In this case, the scramble is not applied to the generator.
Out of memory; Shape subsystem unable to operate. There is insufficient working memory available. Report this error to the
nearest Agilent Technologies sales or service office.
Out of memory; The table editor cannot function properly until more memory is available.
There is insufficient working memory available. Reduce the size of any sweep lists and try again.
Out of memory; The table editor cannot function properly until more memory is available.
There is insufficient memory for the ARB to generate the requested waveform.
Out of memory; Unable to allocate memory for SCPI response.
There is not enough memory to execute this SCPI query. Reduce the size of any list/sweep, and preset the source to clear up any inconsistencies. If the problem persists report thiserror to the nearest Agilent Technologiessales or service office.
12 ErrorMessages
ESG Family Signal Generators -399 to -300: Device-Specific Errors
Out of memory; Unable to check Data Generator memory.
There was not enoughmemory in the system to properly complete thedata generator memory test. This does not imply a data generator memory failure. Check all other error messages to identify possible causes, discontinue list/sweep mode to free some memory, and repeat the test.
Out of memory; Unable to display format window.
The instrument was unable to create part of the graphical user interface due to an inability to allocate memory (possibly due to fragmentation). Report this error to the nearest Agilent Technologies sales or service office. The instrument is still functional.
Out of memory; Unable to display protocol window.
The instrument was unable to create part of the graphical user interface due to an inability to allocate memory (possibly due to fragmentation). Report this error to the nearest Agilent Technologies sales or service office. The instrument is still functional.
Out of memory; Unable to display timeslot window.
The instrument was unable to create part of the graphical user interface due to an inability to allocate memory (possibly due to fragmentation). Report this error to the nearest Agilent Technologies sales or service office. The instrument is still functional.
Out of memory; Unable to verify instrument state file.
An instrument state file could not be accessed and verified because of insufficient memory. Reduce the size of any sweep lists and try again.
Out of memory; User burst shape could not be generated.
There is insufficient working memory available. Report this error to the nearest Agilent Technologies sales or service office.
-320 Storage fault The firmware detected a fault when using data storage. This error is not
an indication of physical damage or failure of any mass storage element.
-315 Configuration memory lost Indicates that non-volatile configuration data saved by the device has been
lost. The meaning of this error is device-dependent.
Error Messages 13
-399 to -300: Device-Specific Errors ESG Family Signal Generators
Configuration memory lost; Persistent state checksum is bad. Using factory defaults.
The persistent state is corrupt and had to be reinitialized with the factory preset values.
Configuration memory lost; Persistent state preset. Using factory defaults.
The persistent state has been forced to return to factory preset values.
Configuration memory lost; Persistent state version is bad. Using factory defaults.
The persistent state version is not recognized as valid and is assumed to be corrupt. The persistent state is reinitialized with the factory preset values.
-314 Save/recall memory loss The non-volatile data saved by the *SAV? command has been lost.
-313 Calibration memory lost Indicates that non-volatile calibration data has been lost.
-312 PUD memory lost The protected user data saved by the *PUD command has been lost.
-311 Memory error An error was detected in the device’s memory.
Memory error; Unable to configure Save Recall registers from non-volatile memory. Save Recall registers re-initialized.
Indicates that saved states are no longer usable. Delete explicitly using Catalog.
-310 System error; Absolute I and Q voltages must be at most
1 volt.
An internal error has occurred that results in the normalized I or Q voltage to be greater than 1 volt. Report this error to the nearest Agilent Technologies sales or service office.
14 ErrorMessages
ESG Family Signal Generators -399 to -300: Device-Specific Errors
System error; Cannot change manual point until list mode error condition cleared.
An error is keeping the sweep/list from being able to set the frequency and/or power. Until the problem is addressed, the manual point cannot be changed.
System error; File Not Found.
The specified file cannot be found. Verify that the file exists in the instrument file system.
System Error; FIR subsystem generated more coefficients than the hardware can handle.
The maximum number of coefficients for a given set of hardware has been exceeded. The filter must be created with fewer coefficients.
System error; Hardware error. Unable to apply Phase inversion!
There is an error with the UN8 option. Try turning CDMA2000 mode off and on again to reset the card. If the problem persists, report this error to the nearest Agilent Technologies sales or service office.
System error; RS232 buffer overflow: character lost.
The RS232 buffer has been exceeded. The most recent character has been dropped.
System error; Unable to determine which attenuator is installed.
An invalid attenuator identification code has been detected. Possible causes include a loose attenuator control cable. The instrument will likely not produce the proper output power levels. Report this error to the nearest Agilent Technologies sales or service office.
-300 Device-specific error This is a generic device-dependent error for devices that cannot detect
more specific errors.The code indicates only that a device-dependent error as defined in IEEE 488.2, 11.5.1.1.6 has occurred.
Error Messages 15
-299 to -200: Execution Errors ESG Family Signal Generators
-299 to -200: Execution Errors
An error has been detected by the instrument’s execution control block. Errors in this class set the execution error bit (bit 4) in the event status register (IEEE 488.2, section 11.5.1). In this case:
• Either a <PROGRAM DATA> element following a header was evaluated by the device as outside of its legal input range or is otherwise inconsistent with the device’s capabilities, or
• a valid program message could not be properly executed due to some device condition.
Execution errors are reported after rounding and expression evaluation operations are completed. Rounding a numeric data element, for example, is not reported as an execution error.
-294 Incompatible type
The type or structure of a memory item is inadequate.
-293 Referenced name already exists
A downloaded program attempted to define an element (a variable, constant, filename, etc.) that had already been defined.
-292 Referenced name does not exist
A downloaded program attempted to access an undefined element (a variable, constant, filename, etc.).
-291 Out of memory
A downloaded program required more memory than was available in the instrument.
-290 Memory use error
A user request hasdirectly or indirectly caused an error related to memory or <data_handles>. This is not the same as “bad” memory.
-286 Program runtime error
A runtime error was detected in a downloaded program.
16 ErrorMessages
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
-299 to -200: Execution Errors ESG 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 ErrorMessages
ESG Family Signal Generators -299 to -200: Execution Errors
-260 Expression error An expression data element-related error occurred. This error message is
used when the device cannot detect the more specific errors described for errors -261 through -269.
-258 Media protected The device or user has attempted to write to a read-only memory
subsystem (msus). The definition of a protected media is device-specific.
-257 File name error A legal program command or query could not be executed because a file
name on the device media was in error. For example,an attempt wasmade to copy to a duplicate filename. The definition of what constitutes a file name error is device-specific.
File name error; Delete empty sequence <sequence_name>. Delete sequence ignored.
The user has attempted to delete a sequence that is empty (all registers unused). This is informational only. Typically this error is reported (several times) when the “Delete All Sequences” command is executed.
File name error; Delete a non-saved state register. Delete register ignored.
The user has attempted to delete a state that is empty (unused). This is informational only.
File name error; Directory does not support extenders.
An extender, which is specified by an @ sign followed by a memory subsystem name, has been specified for an explicit memory subsystem which does not allow the @ notation. Only the default (:) memory subsystem allows extenders.
File name error; Empty filename A filename of “ “ was specified. This is not a legal filename.
File name error; Illegal extender An illegal memory subsystem name was used after the @.
Error Messages 19
-299 to -200: Execution Errors ESG Family Signal Generators
File name error; Illegal filename character
An illegal character was used within a filename. \, :, @ and all non-printable ASCII characters are illegal in filenames.
File name error; Only one “:” is allowed.
Indicates that only one colon is allowed in any filename specification. The text before the colon is a user memory subsystem.
File name error; Only one “@” is allowed.
Indicates that only one @ is allowed in any filename specification. It specifies the memory subsystem that a user file actually resides in.
-256 File name not found A legal program command or query could not be executed because the file
name on the devicemedia could not be found. Forexample, an attempt was made to read or copy a nonexistent file. The definition of what constitutes a file not being found is device-specific.
File name not found; <filename>
The user has attempted to delete a file that does not exist, or an internal table editor column file has been lost.
File name not found; CDMA_DATA FILE
One of the internal working CDMA channel table files is missing.
File name not found; CDMA_WCODE FILE
One of the internal working CDMA channel table files is missing.
File name not found; CDMA_PNOFS FILE
One of the internal working CDMA channel table files is missing.
File name not found; CDMA_POW FILE
One of the internal working CDMA channel table files is missing.
File name not found; FCDMA2K_CHAN_FILE
An internal table editor column file has been lost. A new one will have to be created.
20 ErrorMessages
Loading...
+ 50 hidden pages
Buy Points How it Works FAQ Contact Us Questions and Suggestions Privacy Policy Cookie Policy Terms of Use