Status Listings

SCPI-Defined Errors

listening formats or whose type is unacceptable to the device.

•An unrecognized header was received. Unrecognized headers include incorrect device-specific headers and incorrect or unimplemented IEEE 488.2 common commands.

•A Group Execute Trigger (GET) was entered into the input buffer inside of an IEEE 488.2 <PROGRAM MESSAGE>.

Events that generate command errors shall not generate execution errors, device-specific errors, or query errors; see the other error definitions in this chapter.

Table 5-1. Command Errors (1 of 4)

Error Number

Error Description [description/explanation/examples]

 

 

–101

desc = “Invalid character”

 

help = ““

 

[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

desc = “Syntax error”

 

help = ““

 

[An unrecognized command or data type was encountered for example, a sting

 

was received when the instrument does not accept strings.]

–103

desc = “Invalid separator”

 

help = ““

 

[The parser was expecting a separator and encountered an illegal character; for

 

example, the semicolon was omitted after a program message unit, *EMC

 

1:CH1:VOLTS 5.]

–104

desc = “Wrong Parameter Type”

 

help = ““

 

[The parser recognized a data element different than one allowed; for example,

 

numeric or string data was expected but block data was encountered.]

–105

desc = “GET not allowed”

 

help = ““

 

[A Group Execute Trigger was received within a program message (see

 

IEEE 488.2, 7.7).]

5-7