An error message is displayed against a red background in the instrument message/warning area in the lower left part of the screen. Pushing a front panel key or executing :DISP:CCL command clears the error message. Errors caused by the operation of a front panel key simply appear on the display. They are not stored in the error queue with some exceptions.
An error with a positive error number is one uniquely defined for this instrument. On the other hand, an error with a negative error number is basically one defined for common GPIB devices in IEEE488.2
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
|
No. |
Message |
Description |
|
221 |
AC constant operation failed |
This error occurs when AC constant operation fails to execute. |
|
10 |
Additional standard needed |
The GPIB command that turns ON the calibration function has been sent before all the data measurements required to calculate the calibration factor have been completed. Be sure to measure all the necessary calibration data before sending commands. This error is not generated by front key operations. |
|
No. |
Message |
Description |
|
-168 |
Block data not allowed |
An block-data element has been received at a position where this instrument does not accept one. |
|
No. |
Message |
Description |
|
97 |
Calculate equivalent parameter failed |
This error occurs when equivalent parameter calculation fails. |
|
59 |
Calibration aborted. Stimulus settings exceeded the parameters of original calibration / compensation |
One of the following problems has occurred. • In the middle of or after the completion of the setup for user calibration or fixture compensation (measurement of required calibration data and calculation and storage of error coefficients), the setting of calibration points (FIXED or USER) is changed. The current setup and error coefficients previously stored become invalid. • When the setting of calibration points is USER, in the middle of or after the completion of the setup for user calibration or fixture compensation (measurement of required calibration data and calculation and storage of error coefficients), the sweep condition (sweep range, sweep parameter, number of sweep points, sweep type) is changed. The current setup and error coefficients previously stored become invalid. • In the middle of the setup for user calibration or four-terminal pair extension (measurement of required calibration data and calculation and storage of error coefficients), the setup is canceled (the cancel key command is executed). The setup is invalid, but error coefficients previously stored are still available. If necessary, again perform the setup for user calibration, fixture compensation, or four-terminal pair extension. |
|
58 |
Calibration / Compensation interpolated |
This error occurs when calibration and compensation are interpolated. |
|
240 |
Calibration data lost |
This error occurs when a file containing the system calibration data is not found or in a damaged state at time of the startup of this instrument, indicating a failure of this instrument. Contact the Keysight Technology sales office or the company from which you bought the instrument. |
|
12 |
Calibration not usable |
A command to execute data measurement for unnecessary (not allowed) calibration (user calibration or fixture compensation) for the current adapter selection is sent. The command is invalid. For example, when NONE (no adapter) is selected as the adapter selection, sending the CALA command, which executes OPEN data measurement for the user calibration, causes this error (when the adapter selection is NONE, you cannot execute the user calibration). Execute the measurement of necessary (allowed) calibration data for the current adapter selection. |
|
11 |
Calibration required |
In user calibration, although error coefficients based on the measurement of the required calibration standards (OPEN, SHORT, or LOAD) have not been acquired, a GPIB command to turn on the user calibration function is sent. Valid error coefficients are not detected, and the command is invalid. For user calibration, it is necessary to measure all calibration standards (OPEN, SHORT, LOAD) and acquire error coefficients based on the measurement. |
|
-148 |
Character data not allowed |
A character data element (not violating the standard) has been received at a position where this instrument does not accept one. Double quotes (") are omitted where it is necessary to place a parameter in double quotes ("), for example. |
|
-100 |
Command error |
A comprehensive syntax error has occurred showing that this instrument cannot detect a more detailed error. This code simply shows that a command error defined in 11.5.1.1.4, IEEE488.2 has occurred. |
|
90 |
Compensation required |
In fixture compensation, although error coefficients based on the measurement of the required calibration standards (OPEN, SHORT, or LOAD) have not been acquired, a GPIB command to turn on the fixture compensation function is sent. Valid error coefficients are not detected, and the command is invalid. For fixture compensation, it is necessary to measure a calibration standard (OPEN, SHORT, or LOAD) corresponding to the fixture compensation function (OPEN compensation function, SHORT compensation function, or LOAD compensation function) you select and obtain error coefficients based on the measurement. |
|
460 |
Continuous switching may damage source switch |
This error occurs when different power ranges are selected in multiple channel measurement settings to avoid source attenuator damage. |
|
No. |
Message |
Description |
|
-222 |
Data out of range |
A data element (not violating the standard) outside the range defined by this instrument has been received. This error occurs when an integer-based command for which the parameter can be rounded exceeds the range of -65536 to +65536 or when a real-number-based command for which the parameter can be rounded exceeds the range of -9.9e37 to +9.9e37, for example. This error occurs also when a numeric value other than a specified one is entered into a command in which the "port number" and "CalKit number" are specified as parameters and hence the parameters are not rounded. |
|
-104 |
Data type error |
The parser has recognized a data element that must not exist. Block data has been sent instead of numeric value data or character string data that had been expected, for example. |
|
63 |
DC Bias constant operation failed |
This error occurs when DC Bias constant operation fails to execute. |
|
No. |
Message |
Description |
|
502 |
Equation runtime error |
This error occurs under the following conditions:
# of trace available depends on the maximum number of channel/traces
# of port available depends on the model option |
|
95 |
Equivalent circuit analysis not allowed |
This error occurs when equivalent circuit analysis is not allowed to be executed. |
|
-200 |
Execution error |
An error associated with execution has been generated for which this instrument cannot specify the error message. This code shows that an error associated with execution defined in 11.5.1.1.5, IEEE488.2 has occurred. This error also occurs when a calibration measurement is aborted. |
|
-123 |
Exponent too large |
The absolute value of the exponent exceeds 32,000 (see 7.7.2.4.1, IEEE488.2). |
|
-178 |
Expression data not allowed |
An expression-data element has been received at a position where this instrument does not accept one. |
|
-170 |
Expression error |
When the expression data is put to syntactic analysis, an error not corresponding to one of Error Numbers -171 through -179 occurs. |
|
No. |
Message |
Description |
|
102 |
Failed to copy file |
This error occurs when copying a file (MMEM:COPY command) fails. |
|
104 |
Failed to create directory |
This error occurs when creating a directory (MMEM:MDIR command) fails. |
|
103 |
Failed to delete file |
This error occurs when deleting a file (MMEM:DEL command) fails. |
|
100 |
Failed to read file |
This error occurs when a 2-port touchstone file (CALC:FSIM:SEND:PMC:PORT:USER:FIL command), the formatted data array (MMEM:LOAD:FDAT command) and limit table (MMEM:STOR:LIM command) for the active trace on the active channel, segment sweep table (MMEM:LOAD:SEGM command) for the active channel, a VBA project file (MMEM:LOAD:PROG command), etc. cannot be read normally. |
|
101 |
Failed to write file |
This error occurs when the formatted data array (MMEM:STOR:FDATcommand) and limit table (MMEM:STOR:LIM command) for the active trace on the active channel, segment sweep table (MMEM:STOR:SEGM command) for the active channel, display image (MMEM:STOR:IMAG command) for the LCD screen, a VBA project file (MMEM:STOR:PROG command), etc. cannot be written normally. |
|
-257 |
File name error |
A file name error. This message appears when an error exists in the file name and hence a command is not executed correctly. This error occurs when you try to copy to an unsuitable file name, for example. |
|
-256 |
File name not found |
The file name specified is not found and hence the command is not executed correctly. This error occurs when you try to read a file that does not exist in a disk or a disk is not correctly inserted into the drive to read or write a file, for example. |
|
201 |
Firmware license not found |
Frequency option or/and Generation code license codes do not exist in .lic file. |
|
56 |
Frequency sweep only |
When a sweep parameter other than frequency is specified, you attempt to execute an equivalent circuit analysis command. You can execute the equivalent circuit analysis only when the sweep parameter is frequency. |
|
No. |
Message |
Description |
|
-105 |
GET not allowed |
A group execution trigger (GET) has been received in the program message (see 7.7, IEEE488.2). |
|
No. |
Message |
Description |
|
-240 |
Hardware error |
The program command cannot be executed due to a hardware-related error. This indicates that an error other than -241 to -249 has occurred. |
|
-114 |
Header suffix out of range |
The unit of the header is outside the range. The header is invalid in the unit for numeric parameters following a SCPI command. |
|
No. |
Message |
Description |
|
-224 |
Illegal parameter value |
This error occurs when the parameter value is not suitable. It also occurs because the number of specified traces exceed the maximum number of trace set. |
|
-282 |
Illegal program name |
This error occurs when a nonexistent VBA program name is specified by the PROG:SEL:NAME command. |
|
-213 |
Init ignored |
Because another measurement is in progress, the request for initiating a measurement ("INIT" command) is ignored. |
|
243 |
Insufficient privileges |
This error occurs when multiple processes are executed at the same time and the memory is exhausted, which causes the last process to be aborted. In this case, terminate some of the processes and then perform the next operation. |
|
-161 |
Invalid block data |
Block data has been expected, but the block data that appears is invalid for some reason (see 7.7.6.2, IEEE488.2). The END message is received before the length of block data has been filled, for example. |
|
28 |
Invalid calibration method |
This error occurs when the type of calibration is not specified or not correct when partial overwrite is executed with the GPIB command. This error does not occur for operation with front keys. |
|
-101 |
Invalid character |
An invalid character exists in the program message character string. |
|
-141 |
Invalid character data |
An invalid character is found in the character data element, or the parameter received is not valid. |
|
-121 |
Invalid character in number |
A character that is invalid for the data type subject to syntactic analysis has been received. For example, a letter is found in a decimal numeric value or a numeric character "9" in octal data. |
|
501 |
Invalid equation expression |
The equation expression used in Equation Editor is not valid. |
|
502 |
Invalid equation label |
The equation label used in Equation Editor is not valid. |
|
-171 |
Invalid expression |
The expression-data element is invalid (see 7.7.7.2, IEEE488.2). Parentheses are not paired, or illegal characters are used, for example. |
|
-232 |
Invalid format |
An invalid format is received. |
|
-103 |
Invalid separator |
The parser (a syntactic analysis program) had been expecting a delimiter, but a character that is not a delimiter has been sent. |
|
-151 |
Invalid string data |
Character string data has been expected, but the character string data that appears is invalid for some reason (see 7.7.5.2, IEEE488.2). The END message is received before the ending quotation mark character appears, for example. |
|
-131 |
Invalid suffix |
The suffix does not comply with the syntax defined in 7.7.3.2, IEEE488.2. Or it does not suit E4990A. |
|
No. |
Message |
Description |
|
53 |
Log sweep requires an octave minimum span |
The span of sweep range is not satisfied the requirement for logarithmic sweep. The sweep type is automatically changed to linear sweep when this error occurs. For example, this error occurs when, with the start and stop frequency are set 1 MHz and 1.5 MHz respectively, the sweep type is changed to linear sweep. Set the stop frequency to two times or more than the start frequency. And then select logarithmic sweep. |
|
No. |
Message |
Description |
|
-270 |
Macro error |
The error occurs when wrong macro is executed. |
|
+60 |
Maximum wait time exceeded |
Total time of wait time has been exceeded the limit.
|
|
-109 |
Missing parameter |
The number of parameters is less than that required for the command, or the parameter has not been entered. For example, the command SENS{1-6}:SWE:POIN requires one more parameter. Therefore, when a message "SENS1:SWE:POIN" is sent to a correct program message "SENS1:SWE:POIN 201" this instrument receives the former message as an invalid one because all parameters have not been entered. Enter command parameters correctly. |
|
55 |
Measurement parameter not for analysis |
When a measurement parameter other than |Z|-q is set, you attempt to execute a waveform analysis command (for example, OUTPCERR?) and, as a result, the command is ignored. Before executing a waveform analysis command, set the measurement parameter to |Z|-θ. |
|
96 |
Must be more than 2 points for analysis |
Although the calculation of equivalent circuit parameters is executed, because the number of points (NOP) within the sweep range (if the partial search function is on and within the specified search range) is two, they cannot be calculated. Set the number of points within the sweep range (if the partial search function is on, within the specified search range) to three or more. |
|
No. |
Message |
Description |
|
-120 |
Numeric data error |
An error resulting from the numeric value data (including numeric value data having no decimal point representation) has occurred. A numeric value error other than Errors -121 through -129 has occurred. |
|
-128 |
Numeric data not allowed |
An numeric-value-data element (not violating the standard) has been received at a position where this instrument does not accept one. |
|
52 |
No valid memory trace |
This error occurs when you have executed either DISP:WIND:TRAC:MEM ON command to display memory trace, or any other command to enable data calculation using memory trace (CALC:MATH:FUNC command with other than NORM is specified), though no valid data exists in memory trace. This error is not generated by front key operations. |
|
No. |
Message |
Description |
|
200 |
Option not installed |
The command received has been ignored because of the mismatch between the contents of an option for this instrument and the command. It also occurs when you try to enable the time domain function in a model not having the time domain option. This holds true for the frequency offset option. This error is not generated by front key operations. |
|
-225 |
Out of memory |
Insufficient memory is available in this instrument to perform the required operation. |
|
No. |
Message |
Description |
|
-220 |
Parameter error |
When a parameter-related error other than Errors -221 through -229 occurs, that error is displayed. |
|
-108 |
Parameter not allowed |
The number of parameters exceeds that required for the command. For instance, when a program message ":SENS1:SWE:TYPE LIN, SEGM" is sent instead of a correct program message with a command ":SENS1:SWE:TYPE LIN" which requires a parameter, the instrument receives the message as the number of parameters is invalid. See the command reference to confirm the required number of parameters. |
|
41 |
Peak not found |
This error occurs when, after specifying a peak and executing the CALC:MARK:FUNC:EXEC and CALC:FUNC:EXEC commands, the specified peak is not found in the marker search analysis. |
|
220 |
Phase lock loop unlocked |
This error occurs when the PLL circuit of this instrument becomes unlocked while the measurement is in progress. The measurement value is not correct. This error may occur when an external reference out of specification is connected to this instrument. Should an error occur with an external reference not connected, this instrument is faulty. Contact the sales office or the company from which you bought the instrument. |
|
106 |
Printer error |
This error occurs when the previous printing is still in progress or the printer fails (offline, short of paper, etc.) at time of outputting the display image on the LCD screen to the printer (HCOP:IMM command). |
|
120 |
Print failed |
This error occurs when printing fails for reasons other than Error 120, Printer error. |
|
241 |
Power on test failed |
This error occurs when the power-on test fails, indicating a failure of this instrument. Contact the sales office or the company from which you bought the instrument. |
|
-284 |
Program currently running |
This error occurs when the PROG:SEL:STAT RUN command is executed with the VBA program in the Run state. |
|
-112 |
Program mnemonic too long |
The length of the header exceeds 12 characters (see 7.6.1.4.1, IEEE488.2). |
|
-286 |
Program runtime error |
An error occurring when VBA /macro is executed. |
|
No. |
Message |
Description |
|
-430 |
Query DEADLOCKED |
The state that generates a "DEADLOCKED" Query error (see 6.3.1.7, IEEE488.2). This error occurs when both input and output buffers have become full, preventing the instrument from continuing processing, for example. |
|
-400 |
Query error |
A comprehensive query error has occurred showing that this instrument cannot detect a more detailed error. This code simply shows that a query error defined in 11.5.1.1.7 and 6.3, IEEE488.2 has occurred. |
|
-410 |
Query INTERRUPTED |
The state that generates a "INTERRUPTED" Query error (see 6.3.2.3, IEEE488.1). This error occurs when data bytes (DAB) or GET are received before the transmission of the response after a query has not been completed, for example. |
|
-350 |
Queue overflow |
The queue contains a specific code in place of the code which caused this error. The code indicates that the error occurred because of no space available in the queue, but the error is not recorded. |
|
-420 |
Query UNTERMINATED |
The state that generates an "UNTERMINATED" Query error (see 6.3.2, IEEE488.2). This error occurs when this instrument is designated as the talker and an incomplete program message is received, for example. |
|
-440 |
Query UNTERMINATED after indefinite response |
After a query asking for an indefinite response has been run, another query is received in the same program message (See 6.5.7.5.7, IEEE488.2). |
|
No. |
Message |
Description |
|
105 |
Recall failed |
This error occurs when reading an instrument status file (State01.sta, etc.) (MMEM:LOAD:STAT command) fails. |
|
45 |
Reference tracking not allowed with Log-Y scale |
This error occurs when Log-Y scale is set and reference tracking is attempted. |
|
No. |
Message |
Description |
|
106 |
Save failed |
This error occurs when writing an instrument status file (State01.sta, etc.) (MMEM:STOR:STAT command) fails. |
|
54 |
Set start and stop DC value as positive and an octave minimum span to select Log DC Bias sweep |
This error occurs when Log DC Bias sweep is selected but start DC value is not set to positive and stop DC value is not set to correct minimum span. |
|
50 |
Specified channel hidden |
This error occurs when an attempt is made to activate a channel not on display using the DISP:WIND:ACT command. This error is not generated by front key operations. |
|
51 |
Specified trace does not exist |
This error occurs when CALC:PAR:SEL command is executed to activate more traces than specified by CALC:PAR:COUN command. This error is not generated by front key operations. |
|
57 |
SnP request not valid |
This error occurs when you try to save data to a Touchstone file but no measurement has been executed. This error also occurs when you try to save a Touchstone file with power sweep measurement specified or with the frequency offset function set to ON. |
|
-150 |
String data error |
When a character-string-data element is put to syntactic analysis, an error not corresponding to one of Error Numbers -151 through -159 occurs. |
|
-158 |
String data not allowed |
A character-string-data element has been received at a position where this instrument does not accept one. |
|
-138 |
Suffix not allowed |
A suffix is attached to a numeric value element to which a suffix is not allowed to be attached. |
|
-134 |
Suffix too long |
The unit is too long. The unit is expressed in 12 or more characters (see 7.7.3.4, IEEE488.2). |
|
-102 |
Syntax error |
A command or data type that is not recognized exists. |
|
-310 |
System error |
One of the errors designated as "system errors" in this instrument has occurred. |
|
No. |
Message |
Description |
|
40 |
Target value not found |
This error occurs when the target is not found during the marker search analysis after specifying the target and executing the CALC:MARK:FUNC:EXEC and CALC:FUNC:EXEC commands. This error occurs also when the bandwidth is not found after executing the bandwidth marker command, CALC:MARK:BWID:DATA? |
|
-124 |
Too many digits |
The number of digits of the argument of the decimal numeric-value-data element exceeds 255 with the preceding 0 removed (see 7.7.2.4.1, IEEE488.2). |
|
-223 |
Too much data |
The block-, expression-, or character-string-type program data that has been received conforms with the standard. But it exceeds the amount that can be processed under the condition of the memory or conditions specific to memory-related devices. In this instrument, this error occurs when the number of characters exceeds 254 in a character-string parameter. |
|
-211 |
Trigger ignored |
This instrument receives and detects a trigger command ("TRIG") or an external trigger signal. But it is ignored due to the timing condition (This instrument is not in the wait-for- trigger state, for example). Change the setup so that a trigger command or an external trigger signal can be sent after the instrument has entered the wait-for- trigger state. |
|
No. |
Message |
Description |
|
-113 |
Undefined header |
A command not defined in this instrument, though not illegal in the syntactic structure, has been received. For example, when a message ":DISP:WIND1:TABL:MEM ON" is sent to a correct program message ":DISP:WIND1:TRAC1:MEM ON," the message sent is received as an undefined command by this instrument. See the command reference and use correct commands. |