-100 To -199, Command Errors - Keysight N9000A Service Manual

Instrument Messages

-100 to -199, Command Errors

-100 to -199, Command Errors
Err# Message
-100
Command error
-101
Invalid character
-102
Syntax error
-103
Invalid separator
-104
Data type error
-105
GET not allowed
-108
Parameter not allowed
-109
Missing parameter
-110
Command header error
-111
Header separator error
-112
Program mnemonic too
long
-113
Undefined header
-114
Header suffix out of
range
-115
Unexpected number of
parameters
-120
Numeric data error
102
Verbose/Correction Information
There is a problem with the command. The exact problem
cannot be specifically identified.
An invalid character was found in part of the command.
An unrecognized command or data type was found, for
example a string was received for a command that doesn't
accept strings.
The command was supposed to contain a separator but we
found an illegal character. For example, the semicolon was
omitted after a command string.
We found a data type different then what was expected. For
example, numeric or string data was expected, but block data
was found.
A Group Execute Trigger was received within a program
message.
More parameters were received than were expected for the
command. For example, the *ESE common command only
accepts one parameter, so sending *ESE 0,1 is not allowed.
Fewer parameters were received than required for this
command.
This is a general error that is generated when a problem is
found in a command header, but we can't tell more specifically
what the problem is
We found an illegal character in a command where we
expected to find a separator.
The command contains a keyword that is more than twelve
characters.
The command meets the SCPI syntax requirements, but is not
valid in the current measurement environment.
The value of a numeric suffix that is attached to a program
mnemonic makes the header invalid. (A suffix is usually units,
like Hz or DB.)
The number of parameters received does not correspond to the
number of parameters expected.
An error was found in a data element that appears to be
numeric. The exact problem cannot be specifically identified.
Chapter 3