Error Code | Error Description [description/explanation/examples] |
–200 | “Execution error” This is a generic syntax error for devices that cannot detect more specific errors. This code indicates only that an execution error as defined in IEEE 488.2, 11.5.1.1.5 has occurred. |
–201 | “Invalid while in local” Indicates that a command is not executable while the device is in local due to a hard local control (see IEEE 488.2, 5.6.1.5); for example, a device with a rotary switch receives a message which would change the switches state, but the device is in local so the message cannot be executed. |
–202 | “Settings lost due to rtl” Indicates that a setting associated with a hard local control (see IEEE 488.2, 5.6.1.5) was lost when the device was changed to LOCS from REMS or to LWLS from RWLS. |
–210 | “Trigger error” A trigger error occurred in the signal generator. |
–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; for example, the device was not ready to respond. Note: a DTO device always ignores GET and treats *TRG as a command error. |
–212 | “Arm ignored” Indicates that an arming signal was received and recognized by the device but was ignored. |
–213 | “Init ignored” Indicates that a request for 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. The measurement cannot be started until a GET is received, but the GET would cause an INTERRUPTED error. |
–215 | “Arm deadlock” Indicates that the arm source for the initiation of a measurement is set to GET and subsequent measurement query is received. The measurement cannot be started until a GET is received, but the GET would cause an INTERRUPTED error. |
–220 | “Parameter error” Indicates that a program data element related error occurred. This error message should be used when the device cannot detect the more specific errors described for errors –221 to –229. |
–221 | “Settings conflict” Indicates that a legal program data element was parsed but could not be executed due to the current device state (see IEEE 488.2, 6.4.5.3 and 11.5.1.1.5). |
–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 (see IEEE 488.2, 11.5.1.1.5). |
–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. |
–231 | “Data questionable” Indicates that measurement accuracy is suspect. |
–240 | “Hardware error” Indicates that a legal program command or query could not be executed because of a hardware problem in the device. Definition of what constitutes a hardware problem is completely device-specific. This error message should be used when the device cannot detect the more specific errors described for errors –241 through –249. |
–241 | “Hardware missing” Indicates that a legal program command or query could not be executed because of missing device hardware; for example, an option was not installed. Definition of what constitutes missing hardware is completely device specific. |
–250 | “Mass storage error” Indicates that a mass storage error occurred. This error message should be used when the device cannot detect the more specific errors described for errors –251 through –259. |
–251 | “Missing mass storage” Indicates that a legal program command or query could not be executed because of missing mass storage; for example, an option that was not installed. Definition of what constitutes missing mass storage is device-specific. |
–252 | “Missing media” Indicates that a legal program command or query could not be executed because of missing media; for example, no disk. Definition of what constitutes missing media is device-specific. |
–253 | “Corrupt media” Indicates that a legal program command or query could not be executed because of corrupt media; for example, bad disk or wrong format. Definition of what constitutes corrupt media is device-specific. |
–254 | “Media full” Indicates that a legal program command or query could not be executed because the media was full; for example, there is no room on the disk. The definition of what constitutes a full media is device-specific. |
–255 | “Directory full” Indicates that a legal program command or query could not be executed because the media directory was full. The definition of what constitutes a full media directory is device-specific. |
–256 | “File name not found” Indicates that a legal program command or query could not be executed because the file name on the device media was not found; for example, an attempt was made to read or copy a nonexistent file. The definition of what constitutes a file not being found is device-specific. |
–257 | “File name error” Indicates that a legal program command or query could not be executed because the file name on the device media was in error; for example, an attempt was made to copy to a duplicate file name. The definition of what constitutes a file name error is device-specific. |
–258 | “Media protected” Indicates that a legal program command or query could not be executed because the media was protected; for example, the write-protect tab on a disk was present. The definition of what constitutes protected media is device-specific. |
–260 | “Expression error” Indicates that an expression program data element related error occurred. This error message should be used when the device cannot detect the more specific errors described for errors –261 through –269. |
–261 | “Math error in expression” Indicates that a syntactically legal expression program data element could not be executed due to a math error; for example, a divide-by-zero was attempted. The definition of math error is device-specific. |
–270 | “Macro error” Indicates that a macro-related execution error occurred. This error message should be used when the device cannot detect the more specific errors described for errors –271 through –279. |
–271 | “Macro syntax error” Indicates that a syntactically legal macro program data sequence, according to IEEE 488.2, 10.7.2, could not be executed due to a syntax error within the macro definition (see IEEE 488.2, 10.7.6.3). |
–272 | “Macro execution error” Indicates that a syntactically legal macro program data sequence could not be executed due to a some error in the macro definition (see IEEE 488.2, 10.7.6.3). |
–273 | “Illegal macro label” Indicates that the macro label defined in the *DMC command was a legal string syntax, but could not be accepted by the device (see IEEE 488.2, 10.7.3 and 10.7.6.2); for example, the label was too long, the same as a common command header, or contained invalid header syntax. |
–274 | “Macro parameter error” Indicates that the macro definition improperly used a macro parameter placeholder (see IEEE 488.2, 10.7.3). |
–275 | “Macro definition too long” Indicates that a syntactically legal macro program data sequence could not be executed because the string or block contents were too long for the device to handle (see IEEE 488.2, 10.7.6.1). |
–276 | “Macro recursion error” Indicates that a syntactically legal macro program data sequence could not be executed because the device found it to be recursive (see IEEE 488.2, 10.7.6.6). |
–277 | “Macro redefinition not allowed” Indicates that a syntactically legal macro label in the *DMC command could not be executed because the macro label was already defined (see IEEE 488.2, 10.7.6.4). |
–278 | “Macro header not found” Indicates that a syntactically legal macro label in the *GMC? query could not be executed because the header was not previously defined. |
–280 | “Program error” Indicates that a downloaded program-related execution error occurred. This error message should be used when the device cannot detect the more specific errors described for errors –281 through –289. |
–281 | “Cannot create program” Indicates that an attempt to create a program was unsuccessful. A reason for the failure might include not enough memory. |
–282 | “Illegal program name” The name used to reference a program was invalid; for example, redefining an existing program, deleting a nonexistent program, or in general, referencing a nonexistent program. |
–283 | “Illegal variable name” An attempt was made to reference a nonexistent variable in a program. |
–284 | “Program currently running” Certain operations dealing with programs may be illegal while the program is running; for example, deleting a running program might not be possible. |
–285 | “Program syntax error” Indicates that a syntax error appears in a downloaded program. The syntax used when parsing the downloaded program is device-specific. |
–286 | “Program runtime error” |