[-199,-100] | [-299,-200]
[-399,-300] | [-499,-400]
[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 that 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. |
-113 | Undefined header | The header is undefined for this device. |
-120 | Numeric data error | This error is generated when parsing a data element that appears to be numeric, including the nondecimal numeric types. |
-130 | Suffix error | This error is 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 is 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 is generated when parsing a string data element. |
-160 | Block data error | This error is generated when parsing a block data element. |
-170 | Expression error | This error is generated when parsing an expression data element. |
-180 | Macro error | This error is 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.
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 a subsequent measurement query was 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 an exact value, from a list of possible values, 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. |
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 interface is used. |
-362 | Framing error in program message | Framing error. This error applies when the RS232C interface is used. |
-363 | Input buffer overrun | Buffer overrun error. This error applies when the RS232C interface is used. |
-364 | Time out error | Time out error. This error applies when the RS232C interface 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" error and this error are 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?) |
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 | |
---|---|---|
103 | Operation denied while in PROTection state | The operation was denied because a protection function has been activated. |
141 | CURR setting conflicts with CURR:PROT setting | The set current conflicts with the set OCP. |
142 | CURR:PROT setting conflicts with CURR setting | The set OCP conflicts with the set current. |
151 | VOLT setting conflicts with VOLT:PROT setting | The set voltage conflicts with the set OVP. |
152 | VOLT:PROT setting conflicts with VOLT setting | The set OVP conflicts with the set voltage. |
153 | VOLT setting conflicts with VOLT:LIM:LOW setting | The set voltage conflicts with the set UVP. |
154 | VOLT:LIM:LOW setting conflicts with VOLT setting | The set UVP conflicts with the set voltage. |
155 | Operation denied during ALARM condition | The operation was denied because an alarm is occurring on the PWX. |
901 | EEPROM content error for CRITICAL data | An error has occurred in a critical area. Contact your Kikusui agent or distributor. |
902 | EEPROM content error for CAL data | An error has occurred in a calibration area. Contact your Kikusui agent or distributor. |
903 | EEPROM content error for CONFIG data | An error has occurred in the configuration area. The PWX will be reset to its factory default settings. This error occurring multiple times indicates that the memory is damaged. Contact your Kikusui agent or distributor. |
904 | EEPROM content error for PANEL data | An error has occurred in the panel memory area. The PWX will be reset to its factory default settings. This error occurring multiple times indicates that the memory is damaged. Contact your Kikusui agent or distributor. |