Section 8: Troubleshooting guide
Models 707B and 708B Switching Matrix Reference Manual
8-2
707B-901-01 Rev. B / January 2015
Effects of errors on scripts
Most errors will not abort a running script. The only time a script is aborted is when a Lua runtime
error (error number –286) is detected.
Runtime errors are caused by actions such as trying to index into a variable that is not a table.
Syntax errors (error number -285) in a script or command will not abort the script, but will prevent the
script or command from being executed.
Retrieving errors
When errors occur, the error messages are placed in the error queue. Use error queue commands to
request error message information. For example, the following commands request the next complete
error information from the error queue and return the code, message, severity, and node for that
error:
errorCode, message, severity, errorNode = errorqueue.next()
print(errorCode, message, severity, errorNode)
The following table lists the commands associated with the error queue.
Remote commands associated with the error queue
Command
Description
(on page 7-82)
Clear error queue of all errors
(on page 7-83)
Number of messages in the error queue
Request next error message from
queue
USB troubleshooting
This section provides information checks you can perform if the USB communication with the
instrument is not working.
Check driver for the USB Test and Measurement Device
1. Open Device Manager.
From the Start menu, you can enter
Devmgmt.msc
in the Run box or the Windows 7 search box to
start Device Manager.
2. Under USB Test and Measurement Devices, look for USB Test and Measurement Device.
If the device is not there, either VISA is not installed or the instrument is not plugged in and
switched on.
