Agilent Technologies OmniBER 720 Manual page 353

Hide thumbs Also See for OmniBER 720:
Table of Contents

Advertisement

SCPI Error Messages
SCPI Error Messages
The system-defined error/event numbers are chosen on an enumerated ("1 of N")
basis. The SCPI defined error/event numbers and the error description portions of
the ERRor query response are listed here. The first error/event described in each
class (for example, −100, −200, −300, −400) is a "generic" error. In selecting the
proper error/event number to report, more specific error/event codes are preferred,
and the generic error/event is used only if the others are inappropriate.
No Error
This message indicates that the device has no errors.
No Error
The queue is completely empty. Every error/event in the queue has been read or the
queue was purposely cleared by power-on, *CLS, etc.
Command Errors [
An < error/event number > in the range [−199, −100 ] indicates that an IEEE 488.2
syntax error has been detected by the instrument's parser. The occurrence of any
error in this class should cause the command error bit (bit 5) in the event status
register (IEEE 488.2, section 11.5.1) to be set. One of the following events has
occurred:
• An IEEE 488.2 system error has been detected by the parser. That is, a controller-
to-device message was received which is in violation of the IEEE 488.2 standard.
Possible violations include a data element which violates the device 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 not implemented IEEE 488.2 common
commands.
• A Group Execute Trigger (GET) was entered into the input buffer inside of an
8-20
Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com
199,
100 ]

Advertisement

Table of Contents
loading

Table of Contents