Error conditions in an application call the OnError event. Application errors can happen for several reasons, including during a communication error with an instrument using an I/O Table as an interface to GPIB.
OnError events are processed in the sequence as shown in the following table:
Module |
Event |
When Processed |
Usage Examples |
"Source" module |
OnError |
When a procedure encounters an error condition. The module that caused the error is the first module to be processed in sequence. |
Clear error conditions on the UUT and return registers to valid values. Preserve detailed information on the state of the device at the time of the error. Keep a recoverable error log which could warn of progressive deterioration of the device. Write error information to the Test Log. |
Program |
OnError |
When a Program encounters an error condition. |
Clear error conditions on the UUT and return registers to valid values. Preserve detailed information on the state of the device at the time of the error. Keep a recoverable error log which could warn of progressive deterioration of the device. Write error information to the Test Log. |
Driver(s) |
OnError |
When a Driver encounters an error condition. The events are processed in the reverse order of the Drivers listed. |
For a test executive program prompt the user to retry, ignore, or return. Write error information to the log. |
System |
OnError |
When the System encounters an error condition. |
Do any error processing that the Driver did not handle. |
An error condition can be of two types:
● Recoverable errors enable code to send a message to the Test Log, such as "Instrument not responding". The code can also call the GetErrorModule, GetErrorNum, and GetErrorMsg procedure statements to obtain information, such as the error number and message.
Use one of the following commands to terminate an error:
● Retry -- Resume the command that produced the error.
● Ignore -- Go to the next command.
● Return -- Activate the default event, such as, go to the next OnError event.
If no action is taken, ATEasy displays the default dialog box that asks "Abort, Retry, or Ignore?"
● Fatal errors, in which case the ATEasy application or environment terminates.