1c-5
Operation messages
GPIB Command Messages
GPIB Command Messages
-
1
0
1
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
-121, -141, and perhaps some others.
-
1
0
2
Syntax error
An unrecognized command or data type was encountered. For example, a string was
received when the device does not accept strings. Additional information is available
over GPIB.
-
1
0
3
Invalid separator
The parser was expecting a separator and encountered an illegal character. For example,
the semicolon was omitted after a program unit, *EMC1;CH1:VOLTS5.
-
1
0
4
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.
-
1
0
5
GET not allowed
A Group Execute Trigger was received within a program message (see IEEE 488.2.7.7).
-
1
0
8
Parameter not allowed
More parameters were received than expected for the header. For example, the *EMC
common command only accepts one parameter, so receiving *EMC0,1 is not allowed.
-
1
0
9
Missing parameter
Fewer parameters were received than required for the header. For example, the *EMC
common command requires one parameter, so receiving *EMC is not allowed.
-
1
1
1
Header separator error
A character which is not a legal header separator was encountered while parsing the
header. For example, no white space followed the header, thus *GMC”MACRO” is in
error.
-
1
1
2
Program mnemonic too long
The header contains more than twelve characters (see IEEE 488.2, 7.6.1.4.1).
To Next Page
Loading...
Need help?
General
