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 shall cause the command error bit (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. |
Execution errors
An <error/event number> 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 (bit 4) in the event status register to be set.
| Error Code | Error Message Description | |
| -200 | Execution error (generic) | This is the generic syntax error for devices that cannot detect more specific errors. |
| -203 | Command protected | Indicates that a legal password-protected program command or query could not be executed because the command was disabled. |
| -210 | Trigger error | Trigger error |
| -211 | Trigger ignored | Indicates that a GET, *TRG, or triggering signal was received and recognized by the device but was ignored because of device timing considerations. |
| -213 | Init ignored | Indicates that a request for a measurement initiation was ignored as another measurement was already in progress. |
| -214 | Trigger deadlock | Indicates that the trigger source for the initiation of a measurement is set to GET and subsequent measurement query is received. |
| -220 | Parameter error | Indicates that a program data element related error occurred. |
| -221 | Settings conflict | Indicates that a legal program data element was parsed but could not be executed due to the current device state |
| -222 | Data out of range | Indicates that a legal program data element was parsed but could not be executed because the interpreted value was outside the legal range as defined by the device. |
| -223 | Too much data | Indicates that a legal program data element of block, expression, or string type was received that contained more data than the device could handle due to memory or related device-specific requirements. |
| -224 | Illegal parameter value | Used where exact value, from a list of possibles, was expected. |
| -230 | Data corrupt or stale | Possibly invalid data; new reading started but not completed since last access. |
| -241 | Hardware missing | Indicates that a legal program command or query could not be executed because of missing device hardware. |
Query errors
An <error/event number> 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 (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 | Indicates that a condition causing an INTERRUPTED Query error occurred (see IEEE 488.2, 6.3.2.3). |
| -420 | Query UNTERMINATED | Indicates that a condition causing an UNTERMINATED Query error occurred (see IEEE 488.2, 6.3.2.2). |
| -430 | Query DEADLOCKED | Indicates that a condition causing an DEADLOCKED Query error occurred (see IEEE 488.2, 6.3.1.7). |
| -440 | Query UNTERMINATED after indefinite response | Indicates that a query was received in the same program message after an query requesting an indefinite response was executed.(Example: when SYST:ERR? is received after a *IDN? query and a semicolon separator) |
Operation complete event errors
An <error/event number> in the range [-899, -800] is used when the instrument 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.
This event also sets the operation complete bit (bit 0) of the standard event status register.
Table 17 Operation complete event errors
| 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. |
Errors specific to the KFM2150
Error +900 and subsequent errors occur as a result of a self-test executed by the *TST? query.
Table 18 Operation complete event errors
| Error Code | Error Message Description | |
| 106 | Operation is denied when inlocal mode | Operation is denied because the KFM2150 is in local mode. |
| 107 | Operation is denied when MEASurement is in progress | Operation is denied because measurement is in progress. |