[-199,-100] | [-299,-200]
[-399,-300] | [-499,-400]
[-899,-800] | [100-]
A List of Errors
An error 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 shall cause the Command Error (bit 5) in the event status register to be set.
Error Code | Error Message Description | |
---|---|---|
-100 | Command error | This is the generic syntax error |
-101 | Invalid character | A syntactic element contains a character which is invalid for that type. |
-102 | Syntax error | An unrecognized command or data type was encountered. |
-103 | Invalid separator | The parser was expecting a separator and encountered an illegal character. |
-104 | Data type error | The parser recognized a data element different than one allowed. |
-105 | GET not allowed | A Group Execute Trigger was received within a program message. |
-108 | Parameter not allowed | More parameters were received than expected for the header. |
-109 | Missing parameter | Fewer parameters were recieved than required for the header. |
-110 | Command header error | An error was detected in the header. |
-120 | Numeric data error | This error are generated when parsing a data element which apprears to be numeric, including the nondecimal numeric types. |
-130 | Suffix error | This error are generated when parsing a suffix. |
-131 | Invalid suffix | The suffix does not follow the syntax or the suffix is inappropriate for this device. |
-134 | Suffix too long | The suffix contained more than 12 characters. |
-138 | Suffix not allowed | A suffix was encountered after a numeric element which does not allow suffixes. |
-140 | Character data error | This error are generated when parsing a character data element. |
-141 | Invalid character data | Either the character data element contains an invalid character or the particular element received is not valid for the header. |
-144 | Character data too Long | The character data element contains more than twelve characters. |
-148 | Character data not allowed | A legal character data element was encountered where prohibited by the device. |
-150 | String data error | This error are generated when parsing a string data element. |
-160 | Block data error | This error are generated when parsing a block data element. |
-170 | Expression error | This error are generated when parsing an expression data element. |
-180 | Macro error | This error are generated when defining a macro or executing a macro. |
An error in the range [-299, -200] indicates that an error has been detected by the instrument’s execution control block. The occurrence of any error in this class shall cause the Execution Error (bit 4) in the event status register to be set.
The occurrence of any error in this class shall cause the Device Dependent Error (bit 3) in the event status register to be set.
Error Code | Error Message Description | |
---|---|---|
-350 | Queue overflow | A specific code entered into the queue in lieu of the code that caused the error. This code indicates that there is no room in the queue and an error occurred but was not recorded. |
-360 | Communication error | Communication error when the flow control is turned off. This error applies when the RS232C is used. |
-362 | Framing error in program message | Framing error. This error applies when the RS232C is used. |
-363 | Input buffer overrun | Buffer overrun error. This error applies when the RS232C is used. |
-364 | Time out error | Time out error. This error applies when the RS232C is used. |
An error in the range [-499, -400] indicates that the output queue control of the instrument has detected a problem with the message exchange protocol described in IEEE 488.2, chapter 6. The occurrence of any error in this class shall cause the Query Error (bit 2) in the event status register to be set.
Error Code | Error Message Description | |
---|---|---|
-400 | Query error (generic) | This is the generic query error for devices that cannot detect more specific errors. |
-410 | Query INTERRUPTED | Received a new command before the response was read. |
-420 | Query UNTERMINATED | The controller attempted to read the response after the device received an unsupported query or has not received a query. The -100 "COMMAND ERROR" and this error is stored in the error queue. The controller will time out. |
-430 | Query DEADLOCKED | The error queue, input buffer, and output buffer are full when sending large binary data as a response, and the transmission timing is off. |
-440 | Query UNTERMINATED after indefinite response | Received a separate query in semicolon-delimited format after a query that returns a response in an indefinite form. (Example: A command such as the following. *IDN?;SYST:ERR?) |
Operation complete event errors
An error in the range [-899, -800] is used when the PAT-T wishes to report an IEEE488.2 operation complete event. This event occurs when the instrument?s synchronization protocol, having been enabled by an *OPC command, completes all selected pending operations.
The occurrence of any event error in this class shall cause the Operation Complete (bit 0) in the event status register to be set.
Error Code | Error Message Description | |
---|---|---|
-800 | Operation complete | The instrument has completed all selected pending operations in accordance with the IEEE 488.2, 12.5.2 synchronization protocol. |
The occurrence of any error in this class shall cause the Device Dependent Error (bit 3) in the event status register to be set.
Error Code | Error Message Description | |
---|---|---|
101 | Operation denied while in LOCal state | Operation is denied because the PAT-T is in local mode. |
102 | Operation denied while in OUTPut ON state | Operation is denied because the OUTPUT is on. |
103 | Operation denied while in PROTection state | Operation is denied because a protection function is activated. |
104 | Operation denied while in SLAVe mode | Operation is denied because the PAT-T is set to slave mode. |