The object value of a driver module instance can be used to provide information about how that particular driver is running. This is done by accessing the public variables described below.
Counts The number of successful communications since starting. Counts is a Long variable.
ErrorCounts The number of errors encountered since starting. ErrorCounts is a Long variable.
Error The error code number of the current communication attempt. Error is reset to "0" when the error clears. Error codes are listed in the table below:
|
Error |
Description |
|
0 |
No error |
|
1 |
Not executable in RUN mode |
|
2 |
Not executable in MONITOR mode |
|
3 |
Not executable with PROM mounted |
|
4 |
Address over (data overflow) |
|
B |
Not executable in PROGRAM mode |
|
C |
Not executable with PROM mounted |
|
D |
Not executable in LOCAL mode |
|
10 |
Parity error |
|
11 |
Framing error |
|
12 |
Overrun |
|
13 |
FCS error (checksum) |
|
14 |
Format error (parameter length error) |
|
15 |
Entry number data error (parameter error, data code error, data length error) |
|
16 |
Instruction not found |
|
18 |
Frame length error |
|
19 |
Not executable (due to unexecutable error clear, non-registration of I/O table, etc.) |
|
20 |
I/O table generation impossible (unrecognized Remote I/O unit, word over, duplication of Optical Transmitting I/O unit) |
|
80 |
Incomplete response to WRITE |
|
81 |
Bad serial port parameters |
|
82 |
Serial port already used |
|
83 |
FCS error (checksum) |
|
84 |
No response from PLC (timed-out) |
|
85 |
Wrong PLC station address responded |
|
86 |
TYPE parameter out-of-range |
|
87 |
Garbled/incomplete message |
|
A0 |
Aborted due to parity error in transmit data |
|
A1 |
Aborted due to framing error in transmit data |
|
A2 |
Aborted due to overrun in transmit data |
|
A4 |
Aborted due to format error in transmit data |
|
A5 |
Aborted due to entry number data error in transmit data |
|
A8 |
Aborted due to frame length error in transmit data |
|
B0 |
Not executable because the program area is not 16K |
LastError The error code number of the last error encountered by any communications attempt. LastError is not reset to zero when the error clears.
TimeStamp The time (in seconds) of the last successful communication since midnight. TimeStamp is a floating-point variable.
DateStamp The date of the last successful communication since January 1, 1970. DateStamp is a long variable.
ErrorTime The time of the last error encountered in any communication attempt in seconds since midnight. ErrorTime is a floating-point variable.
ErrorDate The date of the last error encountered in any communication attempt in days since January 1, 1970. ErrorDate is a Long variable.
ErrorOwner An object variable that holds the object value of the read or write statement that encountered the most recent error.
SCounts[255] An array of Counts values, one for each Omron PLC.
SDateStamp[255] An array of DateStamp values, one for each Omron PLC.
SError[255] An array of Error values, one for each Omron PLC.
SErrorCounts[255] An array of ErrorCounts values, one for each Omron PLC.
SErrorDate[255] An array of ErrorDate values, one for each Omron PLC.
SErrorTime[255] An array of ErrorTime values, one for each Omron PLC.
STimeStamp[255] An array of TimeStamp values, one for each Omron PLC.
Version A text variable that is set to the version number of the driver when the driver is started.
In the example above, the object value of the driver module was assigned to an object variable called, "Driver". To display any errors generated by any reads or writes using this driver, use an expression similar to the example shown below:
Output(0,0,1,0,0Driver\Error,15,0,0,0,0) { Show the current error code }