In this section:
Introduction .............................................................................. 8-1
Error levels ............................................................................... 8-1
Effects of errors on scripts ....................................................... 8-1
Retrieving errors ....................................................................... 8-2
Error summary list .................................................................... 8-2
LAN troubleshooting suggestions ............................................. 8-6
Introduction
Troubleshooting information includes information on the Keithley Instruments 2606B errors (including
a complete listing of error messages) and LAN troubleshooting suggestions.
Error levels
Error messages are listed in
(on page 8-2). Errors have one of the following error
levels:
Number
Error level
Description
0
NO_SEVERITY
The message is information only. This level is used when the error
queue is empty; the message does not represent an error.
10
INFORMATIONAL
The message is information only. This level is used to indicate status
changes; the message does not represent an error.
20
RECOVERABLE
The error was caused by improper use of the instrument or by
conditions that can be corrected. This message indicates that an
error occurred. The instrument is still operating normally.
30
SERIOUS
There is a condition that prevents the instrument from functioning
properly. The message indicates that the instrument is presently
operating in an error condition. If the condition is corrected, the
instrument will return to normal operation.
40
FATAL
There is a condition that cannot be corrected that prevents the
instrument from functioning properly. Disconnect the DUT and turn
the power off and then on again. If the error is a hardware fault that
persists after cycling the power, the instrument must be repaired.
Effects of errors on scripts
Most errors will not abort a running script. The only time a script is aborted is when a Lua run-time
error (error code -286, "TSP runtime error") is detected. Run-time errors are caused by actions such
as trying to index into a variable that is not a table.
Syntax errors (error code -285, "Program syntax") in a script or command will prevent execution of the
script or command.
Section 8
Troubleshooting guide