Error Messages
Agilent Technologies
N5181A/82A MXG Signa l Generators
This guide applies to the following signal generator models:
N5181A MXG Analog Signal Generator
N5182A MXG Vector Signal Generator
Due to our continuing efforts to improve our products through firmware and hardware revisions, signal
generator design and operation may vary from descriptions in this guide. We recommend that you use the
latest revision of this guide to ensure you have up-to-date product information. Compare the print date of this
guide (see bottom of page) with the latest revision, which can be downloaded from the following website:
www.agilen t.com/find/mxg
Manufacturing Part Number: N5180-90020 - For Online Use Only
Printed in USA
September 2006
© Copyright 2006 Agilent Technologies, Inc.
Notice
The material contained in this document is provided “as is”, and is subject to being changed, without no tice,
in future editions.
Further, to the maximum extent permitted by applicable law, Agilent disclaims all warranties, either express
or implied with regard to this manual and to any of the Agilent products to which it pertains, including but
not limited to the implied warranties of merchantability and fitness for a particular purpose. Agilent shall not
be liable for errors or for incidental or consequential damages in connection with the furnishing, use, or
performance of this document or any of the Agilent products to which it pertains. Should Agilent have a
written contract with the User and should any of the contract terms conflict with these terms, the contract
terms shall control.
Questions or Comments about our Documentation?
We welcome any questions or comments you may have about our documentation. Please send us an E-mail
at sources_manuals@am.exch.agilent.com.
ii
Error Messages
Introduction
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
Overflow Handling Circular (rotating).
Drops oldest error as new error comes in.
Viewing Entries Press:
Clearing the Queue Press:
Unresolved Errors
(errors that must be
resolved.
For example: unlock,
avalanched, and
hi/lo)
Utility > Error Info > View Next
(or
Previous) Error Message
Utility > Error Info >
ClearErrorQueue(s)
Re-reported after queue is cleared. Re-reported after queue is
SCPI Remote Interface
Error Queue
Linear, first-in/first-out.
Replaces newest error with:
-350, Queue overflow
Use SCPI query
SYSTem:ERRor[:NEXT]?
Power up
Send a *CLS command
Read last item in the queue
cleared.
Error Messages
Error Message Format
Error Message Format
When accessing error messages through the front panel display error queue, the error numbers, messages
and descriptions are displayed on an enumerated (“1 of N”) bas is. When acces s ing err or mess ages using the
SCPI (remote interface) error queue, the error numbers and the <error_description> portions of the error
query response are displayed on the host terminal.
In this guide, an explanation is generally included with each error to further clarify its meaning. The error
messages in this guide are listed numerically. In cases where there are multiple listings for the same error
number, the messages are in alphabetical order, excluding simple words like “the” and “it”.
Error messages appear in the lower-left corner of the display as they occur.
Error Messages
Error Message Types
Error Message Types
Events do not generate more than one type of error. For example, 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 488.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 703) 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 comp leted . Round ing
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 syn tax error.
Errors in this class set the command error bit (bit 5 ) in the ev ent s tatus regist er (I EEE 4 88.2 , s ection 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.
-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 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.
-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.
-330 Self-test failed; BBG{value}: {name}
A self-test executed on the baseband generator failed. Report this
error to Agilent Technologies.
-330 Self-test failed; The loop back test failed because the digital module
could not be set up.
To run a diagnostic loop back test, the instrument needs to
communicate with and set up the module. This error is reported when
the instrument cannot communicate with the module.
-321 Out of memory
*** No documentation ***
-321 Out of memory; Arb file selection failed. File System failed to access
required file. Some table editor files may be corrupted.
There was a problem accessing a required file.
-321 Out of memory; ARB is not functional.
There is insufficient memory for the ARB to generate the requested
waveform.
Page 1
lperrordoc.txt
-321 Out of memory; BBG 3GPP cannot function properly.
3GPP cannot function properly due to dynamic memory allocation
failure.
-321 Out of memory; Burst shape subsystem unable to operate.
Operations on a Burst Shape could not be completed because of
insufficient memory.
-321 Out of memory; Cannot convert binary file to bit file.
There is not enough memory to convert a binary file to a bit file.
Reduce the size of any sweep lists and try again.
-321 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.
-321 Out of memory; Complementary Cumulative Distribution Display cannot
function.
There is insufficient working memory available. Report this error
to Agilent Technologies.
-321 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.
-321 Out of memory; Could not perform channelization code conflict test.
This error is reported when an attempt to check WCDMA DL channels
for conflicting channelization codes fails due to an out of memory
error.
-321 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 Agilent
Technologies.
-321 Out of memory; FFT subsystem unable to function.
There is insufficient working memory available. Report this error
to Agilent Technologies.
-321 Out of memory; FILE NAME
A file system operation has failed due to a lack of memory in the
system. Reduce memory usage and try again.
-321 Out of memory; FIR subsystem unable to operate.
Page 2
There is insufficient working memory available. Report this error
to Agilent Technologies.
-321 Out of memory; Front panel firmware upgrade unable to begin.
There is insufficient working memory available. Report this error
to Agilent Technologies. The front panel firmware was not
successfully upgraded, but it was not corrupted either.
-321 Out of memory; Graph subsystem cannot function.
There is insufficient working memory available. Report this error
to Agilent Technologies.
-321 Out of memory; Histogram display cannot function
There is insufficient working memory available. Report this error
to Agilent Technologies.
-321 Out of memory; Impulse response display cannot function.
There is insufficient working memory available. Report this error
to Agilent Technologies.
-321 Out of memory; I/Q map display cannot function.
There is insufficient working memory available. Report this error
to Agilent Technologies.
lperrordoc.txt
-321 Out of memory; Memory allocation error.
There is insufficient working memory available. Report this error
to Agilent Technologies.
-321 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.
-321 Out of memory; Modulation subsystem unable to operate.
There is insufficient working memory available. Report this error
to Agilent Technologies.
-321 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 Agilent Technologies.
-321 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 size of any list/sweep, and preset the
source to clear up any inconsistencies. If the problem persists
report this error to Agilent Technologies.
-321 Out of memory; Not enough Waveform Memory on BBG{value}
There is not enough memory left on the baseband board to generate
the required baseband file. Remove any file that might have been
previously downloaded and is not required anymore (e.g. ARB files).
Page 3
Select different parameters that require a smaller file. Upgrade to
a baseband option with larger memory.
-321 Out of memory; The pre-coding 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.
-321 Out of memory; Shape subsystem unable to operate.
There is insufficient working memory available. Report this error
to Agilent Technologies.
-321 Out of memory; Simulation requires {value} points free in ARB memory.
The simulation cannot occur until the specified number of points
are available in ARB memory. Increase the amount of available ARB
memory and try again.
-321 Out of memory; SMI is not functional.
There is insufficient memory for the SMI to generate its cal data.
-321 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.
lperrordoc.txt
-321 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 Agilent Technologies. The
instrument is still functional.
-321 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 Agilent Technologies. The
instrument is still functional.
-321 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 Agilent Technologies. The
instrument is still functional.
-321 Out of memory; {name}
The header file to be written is too big to fit on the media. The
new information was not written and the original header is
untouched.
-321 Out of memory; {name} display cannot function.
There is insufficient working memory available. Report this error
to Agilent Technologies.
-315 Configuration memory lost; Persistent state checksum is bad. Using
Page 4
factory defaults.
The persistent state is corrupt and had to be reinitialized with
the factory preset values.
-315 Configuration memory lost; Persistent state preset. Using factory
defaults.
The persistent state has been forced to return to factory preset
values.
-313 Calibration memory lost; Cal not found and was created: {name}
The specified cal file was not found so it was created by the
system.
-313 Calibration memory lost; Cal out of mem: {name}
Inadequate memory for specified cal file.
-313 Calibration memory lost; Cal resizing: {name}
Inadequate memory to resize specified cal file.
-313 Calibration memory lost; Cal restored from backup: {name}
A specified cal file was restored from backup.
-313 Calibration memory lost; Cannot restore cal from backup:
{name}err={value}
lperrordoc.txt
Cannot restore specified cal from backup because of a file error.
-313 Calibration memory lost; Cannot store cal to backup: {name}err={value}
Cannot store specified cal to backup because of a file error.
-313 Calibration memory lost; Cannot store cal: {name}err={value}
Cannot store specified cal because of a file error.
-313 Calibration memory lost; Error occurred while trying to load data from
previous internal IQ calibration.
An expected file was not found while trying to load internal IQ
calibration data.
-313 Calibration memory lost; Previous Internal IQ calibration data is
invalid. Data has been removed. A new user IQ calibration is
recommended.
An expected file was not found while trying to load internal IQ
calibration data. All other data has been removed. A new cal should
be performed.
-313 Calibration memory lost; Stored calibration data is invalid.
An unexpected error occur while attempting to restore cal data. The
stored data is not valid. Service is required. report this error to
Agilent Technologies.
-310 System error
Page 5
*** No documentation ***
-310 System error; The ADC {name} has timed out during a conversion.
The returned data is not valid. Report this error to Agilent
Technologies.
-310 System error; Arb generation failed. File System failed to access
required file.
There was a problem opening, reading or writing to the specified
file.
-310 System error; Automatic reboot performed due to exception vector
#{value} at PC 0x%06X
An exception occurred at the instruction address. This is a
internal firmware error. Currently not supported.
-310 System error; Cal in use, cannot delete: {name}
Calibration file cannot be deleted since it is currently in use.
Error caused by diagnostic command.
-310 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.
lperrordoc.txt
-310 System error; Could not create percent complete window semaphore.
When trying to initialize a percent complete Window the needed
semaphore could not be created. Report this error to Agilent
Technologies.
-310 System error; Could not limit frequency settings. Please preset.
Based on the current frequency settings (multiplier, offset, etc.)
the signal generator cannot successfully limit the frequency.
Preset the signal generator to insure the firmware will return to a
valid state.
-310 System error; Critical digital module error. Report this error to
Agilent Technologies.
This error cannot be generated under normal operating conditions
and should be reported to Agilent Technologies.
-310 System error; Display could not be initialized: {name}
A fatal error has occurred while the LCD controller was being
initialized. The display is not functional. Repeated errors of this
nature may mean that service is required. Report this error to
Agilent Technologies.
-310 System error; Error backing up system files.
Error encountered while writing system files to backup storage.
-310 System error; Error creating directory: {name}
Page 6
Error creating a directory. The directory is shown in error
message.
-310 System error; Error restoring system files.
Error encountered while restoring system files from backup storage.
-310 System error; Error sending RS232 XON/XOFF. {name}
Caused by either framing, parity, or overrun errors during RS232
communication.
-310 System error; Error updating RS232 configuration. {name}
Caused by either framing, parity, or overrun errors during RS232
communication.
-310 System error; Error updating RS232 RTS line. {name}
Caused by either framing, parity, or overrun errors during RS232
communication.
-310 System error; Expected memory media not found. {name}.
Expected memory media (storage media) was not found. Report this
error to Agilent Technologies.
-310 System error; Failed to write file.
lperrordoc.txt
An attempt to write to a file in the internal file system has
failed. This may be a temporary condition caused by insufficient
disk space or system interaction. Try reducing file system usage
and try again. If the problem persists, report this error to
Agilent Technologies.
-310 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.
-310 System error; Hardware communication error during ramp sweep.
The synthesis system had a hardware communications failure during
ramp sweep.
-310 System error; Hardware error. Unable to apply phase inversion!
There is an error with the baseband generator. Try turning CDMA2000
or 1xEVDV mode off and on again to reset the card. If the problem
persists, report this error to Agilent Technologies.
-310 System error; Invalid object. {name}
Internal error. File system operation encountered invalid object.
-310 System error; Line:{value} file: {name} stack: {name}
An internal error occurred at the specified location within the
specified file.
-310 System error; Media raw. {name}
Page 7
The flash storage media was never formatted or is corrupted. The
system will reformat it now.
-310 System error; Not implemented. {name}
Internal error. This functionality is not implemented.
-310 System error; Null pointer. {name}
Internal error. File system operation failed.
-310 System error; Path too long deleting cal
Resulting path to calibration file was too long and file was not
removed. Error caused by diagnostic command.
-310 System error; Previous boot failed at step {value}.
An internal error occurred during previous boot up at the specified
step.
-310 System error; Receive pace not supported
Command is not supported for RS232 communication.
-310 System error; Revert to default cal not implemented
Command not implemented.
lperrordoc.txt
-310 System error; RS232 receive error. {name}
Caused by either framing, parity, or overrun errors during RS232
communication.
-310 System error; RS232 send error. {name}
Caused by either framing, parity, or overrun errors during RS232
communication.
-310 System error; RTS pace not supported
The RS232 command is not supported.
-310 System error; Storage media not present: {name}.
Internal error. The storage media referenced was not found but was
expected. This could happen on a vector box when the internal USB
memory was not found during bootup.
-310 System error; The system was powered off during file system update.
File system volumes were verified.
Informational warning. Powering down system (turning the power off)
during file system write operation may leave the file system in
inconsistent state. On subsequent reboot the volume was verified
and errors repaired.
-310 System error; Transmit pace not supported
Command is not supported for RS232 communication.
-310 System error; Unknown file system error. {name}
Page 8
Internal error.
-310 System error; Volume already exists: {name}
Internal error. The attempt to mount volume detected that volume
already exists. The system will proceed anyway.
-310 System error; Volume consistency check failed: {name} Volume needs to
be reformatted.
Consistency check detected that volume is corrupted and cannot be
automatically fixed. Contact service for help.
-310 System error; Volume failed to mount after reformatting: {name}
The volume was reformatted successfully but failed to mount. The
storage media could be damaged.
-310 System error; Volume failed to mount. It was reformatted: {name} -
{name}.
The volume was reformatted because is failed to mount. It was
either completely damaged or never initialized. This error reports
the 'Success' or 'Failure' of formatting operation. The system will
try to proceed either way.
-310 System error; Volume format failed: {name}
The formatting of the file system volume failed. The instrument
hardware may be damaged.
lperrordoc.txt
-310 System error; Volume reformatted: {name}
Informational error that a file system volume was reformatted
because it was damaged or formatting was requested by user.
-310 System error; {name}
An compatibility language specific system error occurred. The
string contains information about the error.
-310 System error; The {name} board's DCM unlock.
The FPGA's DCM reported unlock. The clocks may not work correctly.
Cycle the instrument's power. If the error is repeated, service is
required. Report this error to Agilent Technologies.
-310 System error; The {name} subsystem was not found. The requested
operation could not be completed.
The subsystem named in the error was not found. Operations within a
subsystem depend on the subsystem for successful execution. If it
is not found the operations cannot be executed. Digital
personalities are also considered subsystems.
-280 Program error; The following error is not recognized:{name}
The specified error is not recognized by the system. Report this
error to Agilent Technologies.
-280 Program error; The following SCPI command generated an error:{name}
The SCPI command generated an error.
Page 9
lperrordoc.txt
-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).
-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.
Page 10
-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.
-259 LAN error; A NetBIOS name conflict occurred. This device no longer has
a NetBIOS hostname.
Change the instrument's hostname. Contact your network system
administrator for assistance.
-259 LAN error; A NetBIOS scope was detected on the network: NetBIOS naming
may not work properly.
Contact your network system administrator for assistance.
-259 LAN error; Default gateway IP address is inconsistent with subnet mask
or IP class rules. The instrument automatically corrects the offending
entry.
Check the entry for syntax and numerical errors and try again.
Verify that the subnet mask is consistent with this address (host
bits should not be all 0s or 1s). If no subnet is specified, verify
that the address is valid with respect to the default class
netmasks: A (0x00FFFFFF), B(0x0000FFFF), or C(0x000000FF).
-259 LAN error; The desired hostname could not be registered through
NetBIOS.
lperrordoc.txt
Contact your network system administrator for assistance.
-259 LAN error; Domain names can only contain letters, numbers, hyphens '-'
and dots '.'; the first character must also be a letter or number.
-259 LAN error; Hostnames are limited to 15 characters and can only contain
letters, numbers and hyphens. The first character must be a letter and
the last character must be a letter or a number.
-259 LAN error; The instrument could not extend lease for a dynamic IP
address using DHCP.
An initial DHCP LAN configuration was obtained. However, when the
lease expired, the instrument was unable to extend it and as a
result lost the previously assigned IP address. Refer to the
internet DHCP protocol documentation for further information.
-259 LAN error; The instrument could not obtain a LAN configuration using
DHCP or Auto-IP: manual configuration was used instead. This error
occurs if no DHCP servers are present or the DHCP server did not
provide a lease of at least 5 minutes.
The instrument was configured to use DHCP with a fallback to
Auto-IP to obtain the LAN interface configuration. The instrument
was not able to negotiate with surrounding DHCP servers. Either
DHCP servers are not present, the lease times are less than 5
minutes or they are not allowing this device to obtain an IP
address. Possibly, the LAN cable is disconnected or is broken.
Page 11
-259 LAN error; The instrument could not obtain a LAN configuration using
DHCP: {name} configuration was used instead. This error occurs if no
DHCP servers are present or the DHCP server did not provide a lease of
at least 5 minutes.
The instrument was configured to use DHCP to obtain the LAN
interface configuration. The instrument was not able to negotiate
with surrounding DHCP servers. Either DHCP servers are not present,
the lease times are less than 5 minutes or they are not allowing
this device to obtain an IP address. Possibly, the LAN cable is
disconnected or is broken.
-259 LAN error; The instrument detected an IP address conflict.
Enter a new IP address or switch to DHCP/AUTO-IP.
-259 LAN error; IP address and default gateway must be on the same subnet.
The instrument automatically changes the offending entries.
The IP address and default gateway are not on the same network as
specified by the subnet mask. Verify that both addresses are on the
same subnet and try again. Contact your network system
administrator for assistance.
-259 LAN error; IP address is inconsistent with subnet mask or IP class
rules. The instrument automatically changes the offending entry.
The IP address is invalid. Check the entry for syntax and numerical
errors and try again. Verify that the subnet mask is consistent
with this address (host bits should not be all 0s or 1s). If no
subnet is specified, verify that the address is valid with respect
to the default class netmasks: A (0x00FFFFFF), B(0x0000FFFF) or
C(0x000000FF).
lperrordoc.txt
-259 LAN error; The network has been disconnected.
-259 LAN error; The network has been reconnected.
-259 LAN error; Network initialization failed. {name}
An error occurred during network initialization. The string
contains information about the error.
-257 File name error; Filename cannot contain any directory information:
{name}
This error occurs when a filename with any directory information is
passed to the SCPI command RADio:ARB:GENerate:SINE. The parameter
is the bad filename.
-257 File name error; The filename specified for saving or recalling is not
valid. Note that only the STATE memory subsystem can be used with
save/recall. Name supplied: {name}
Save/Recall can only operate on the STATE memory subsystem. The
parameter is the bad filename.
-257 File name error; Invalid Filename
Page 12
An invalid filename was encountered. Please refer to the user
manual for guidelines on filename format.
-257 File name error; No file has been selected for use as the PRAM file.
Please select an existing file before trying to use PRAM.
No file has been selected for use as the PRAM file. Please select
an existing file before trying to use PRAM.
-257 File name error; Waveform file not selected.
Waveform file or sequence file must be selected when turning ARB
on.
-257 File name error; {name}
There was a problem with the specified file name. Check the syntax
and try again.
-256 File name not found; User preset file could not be found: a user
preset state must be saved before the preset type can be set to User.
The instrument could not find a user-saved preset state. The user
must first save a preset state before the Preset Type can be set to
User.
-256 File name not found; {name}
The file specified does not exist.
lperrordoc.txt
-256 File name not found; {name} The modulation type has been defaulted.
The specified file is not a modulation file type so the modulation
type has been defaulted.
-255 Directory full; {name}
A legal program command or query could not be executed because the
media directory was full.
-254 Media full; Could not convert file to normalized secure form: {name}
If a secure file is written in three parts to the non-volatile
storage, extra storage (2 times the total size of the files) is
required to complete the write operation. If there is insufficient
memory, the file cannot be written.
-254 Media full; {name}
Invalid file or device name.
-253 Corrupt media; {name}
A source media (possibly EEPROM) for a data file is corrupt. This
error is usually seen in conjunction with errors concerning a
certain file.
-241 Hardware missing; Cannot access a baseband generator that does not
exist.
Tried to retrieve access information that was not created for a
given baseband generator. The hardware probably does not exist.
Page 13
-241 Hardware missing; No Source Module connected
Cannot turn on Source Module Mode if source module is not
connected. Check cable connection.
-241 Hardware missing; SIO address does not exist
The expected board is not installed. Report this error to Agilent
Technologies.
-240 Hardware error; BBG Arb Fifo has emptied.
The Baseband board BBG FIFO has emptied prematurely. The BBG FIFO
buffers digital data from SDRAM Waveform memory. Report this error
to Agilent Technologies.
-240 Hardware error; BBG Arb SDRAM refresh failure.
The baseband board BBG waveform memory failed a refresh cycle.
Report this error to Agilent Technologies.
-240 Hardware error; BBG Arb waveform memory (SDRAM) cannot be reliably
accessed.
There is a problem aligning the phase of the SDRAM access clock.
Report this error to Agilent Technologies.
-240 Hardware error; BBG Communication failure
lperrordoc.txt
Communication with the BBG FPGA failed; specifically, the SSIO bus
failed to respond. Cycle the instrument's power. Report this
failure to Agilent Technologies.
-240 Hardware error; BBG Feldspar ASIC has failed to initialize.
The BBG Assembly Feldspar Asic has failed to initialize properly.
The instrument will require power cycling. Report this error to
your Agilent Technologies sales and service office.
-240 Hardware error; BBG waveform memory transaction aborted.
BBG temporarily stalled. No data was lost. The operation may have
exceeded the computational bandwidth. To prevent this error, use a
less complex waveform or stop the BBG before performing other
tasks.
-233 Invalid 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 file or block
data elements are recognized by the instrument, but cannot
be executed for reasons of version incompatibility. For
example, a non-supported file version or a non-supported
instrument version.
-230 Data corrupt or stale; EEPROM @ offset 0x%06X: wrote 0x%02hX, read
0x%02hX
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 Agilent Technologies.
Page 14
-230 Data corrupt or stale; Either the file is not a bit file, or the
number of bits specified does not match the number of data bytes in
the file.
An error has occurred while downloading a user file to the Bit
memory catalog. Either the user file is not a bit file, or the
number of bits specified in the SCPI command does not match the
number of bytes in the file. Ensure that the bit specifier matches
the actual number of bits in the file.
-230 Data corrupt or stale; File is unusable: {name}
The file ({name}) is not properly formed, so it cannot be used. This
can happen if a file is not of the type expected, or the data was
damaged prior to being placed in the instrument.
-230 Data corrupt or stale; Header File is Not Found or Invalid: {name}.
This error occurs when trying to open a header file, the file does
not match any known header format or does not exist. {name} is the
filename being accessed.
-230 Data corrupt or stale; Header File Parameter Out of Range or Not
Valid: {name}.
This error is reported when trying to apply the header parameters
to the instrument state. If one of the parameters does not contain
a valid value for that state, this error is reported. The {name} will
describe which header field contained the invalid value.
lperrordoc.txt
-230 Data corrupt or stale; The user file version is not recognized. {name}
An error has occurred while loading a user file where the version
of the file is not recognized as a supported version.
-230 Data corrupt or stale; {name}
The sequence file that you are attempting to run is the wrong size.
-224 Illegal parameter value
Used where an exact value was expected from a list of
possibilities.
-224 Illegal parameter value; Analog bus node not present
The analog bus node that was selected is not a valid node in the
system.
-224 Illegal parameter value; Command requires at least one data value.
A modulation type cannot be created without data.
-224 Illegal parameter value; Illegal parallel bus address
Internal error. The instrument tried to access an illegal parallel
bus address.
-224 Illegal parameter value; Latch name not present
The latch name that was selected is not a valid latch in the
system.
Page 15
Loading...