THORLABS 4000 Series, Programmer'S Reference Manual, Page: 84 / 97

© 2015 Thorlabs 82
Series 4000 SCPI Programmers Reference Manual
4.1 Command Errors
Error Description
-100
Command error
This is the generic syntax error for devices that cannot detect more specific errors. This code indicates
only that a Command Error as defined in IEEE 488.2, 11.5.1.1.4 has occurred.
-101
Invalid character
A syntactic element contains a character which is invalid for that type; for example, a header
containing an ampersand, SETUP&. This error might be used in place of errors -114, -121, -141, and
perhaps some others.
-102
Syntax error
An unrecognized command or data type was encountered; for example, a string was received when
the device does not accept strings.
-103
Invalid separator
The parser was expecting a separator and encountered an illegal character; for example, the
semicolon was omitted after a program message unit,
INP:POL CG*STB?
instead of
INP:POL CG;*STB?
-104
Data type error
The parser recognized a data element different than one allowed; for example, numeric or string data
was expected but block data was encountered.
-105
GET not allowed
A Group Execute Trigger was received within a program message (see IEEE 488.2, 7.7).
-108
Parameter not allowed
More parameters were received than expected for the header; for example, the
*SRE
common
command only accepts one parameter, so receiving
*SRE 0,1
is not allowed.
-109
Missing parameter
Fewer parameters were received than required for the header; for example, the
*SRE
common
command requires one parameter, so receiving
*SRE
is not allowed.
-110
Command header error
An error was detected in the header. This error message should be used when the device cannot
detect the more specific errors described for errors -111 through -119.
-113
Undefined header (Unknown command)
The header is syntactically correct, but it is undefined for this specific device; for example,
*XYZ
is not
defined for any device.
-115
Unexpected number of parameters
The number of parameters received does not correspond to the number of parameters expected.
-120
Numeric data error
This error is generated when parsing a data element which appears to be numeric, including the
nondecimal numeric types.
-130
Suffix error
This error, as well as error -131, is generated when parsing a suffix.
-131
Invalid suffix
The suffix does not follow the syntax described in IEEE 488.2, 7.7.3.2, or the suffix is inappropriate for
this device.
-151
Invalid string data
A string data element was expected, but was invalid for some reason (see IEEE 488.2, 7.7.5.2); for
example, an END message was received before the terminal quote character.