Operating
Errors
2000
{
2999
2013
Item not found
or
XXXXX not found
The
XXXXX
will be replaced by the name of the item that was not found.
Cause: A request was made to operate on an item in memory that was not located.
Cure: Use the DEBUG command to locate the programming error. Refer to the
HP 70000
Modular
Spectrum
Analyzer
Programming
Manual
.
2014
Duplicate identifier
Cause: A variable, trace, or DLP name matches a reserved spectrum analyzer command.
Cure: Use the DEBUG command to locate the programming error. Refer to the
HP 70000
Modular Spectrum Analyzer Programming Manual
.
2015
Too many entries
Too many user deînitions
Cause:
More
entries
have
been
made
in
an
internal
table
then
was reserved. The most common
time
this
will
occur
is
having
too
many
entries
in
the
Limit Line Table.
Cure:
Use
the
LIMILINE
command
to
allocate
more
space
for
limit
line entries.
2016
Label
too
long
Cause: A user generated key label that has more than 14 characters, or a FUNCDEF,VARDEF,
or ACTDEF with more than 12 characters will generate this error.
Cure: The system will truncate the text to the correct number of characters and execute the
requested function. Use the DEBUG command to locate the programming error. Refer to the
HP 70000 Modular Spectrum Analyzer Programming Manual
.
2018
State protected
Cause: This error occurs if a user stored instrument state that is protected was requested to be
removed from memory. The state will not be removed. Also, if the number of user states is
reduced using NSTATE, all states above the requested number will be deleted. If any of those
states were protected, the NSTATE command will be ignored and this error will occur.
Cure: Unprotect any states no longer needed.
Error Messages 6-15
To Next Page
Loading...
