MODBUSA Driver Errors
- Last UpdatedDec 02, 2021
- 2 minute read
MODBUSA has two kinds of protocol driver errors:
-
Generic errors, which are hardware errors 0-31 and common to all protocols. Some generic errors are common to all protocols. Sometimes only the generic error is available, though often both the generic error and a specific error are given.
-
Specific errors, which can be unique and therefore cannot be recognized by the hardware alarm system. The drivers convert their specific errors into generic errors that can be identified by the I/O server. For example, when a driver experiences an error, there is often both a protocol-specific error and a corresponding generic error.
When a hardware error occurs, Plant SCADA generates an alarm and displays the alarm on the Hardware Alarm page (in the alarm description of the hardware alarm). To see the error number, make sure you have Alarm Category 255 defined with a display format that includes {ErrDesc,15} {ErrPage,10}.
Specific Errors
The following errors, listed in (hexadecimal) sequence, are specific to this driver. Plant SCADA displays the error number and description for common protocol-specific errors. Uncommon errors are not contained in the Plant SCADA error database, in which case Plant SCADA only displays the error number.
You might need additional information to rectify an error. This information should be detailed in the documentation that accompanied the I/O device (or network). If, after reviewing all documentation, you cannot rectify an error, contact Technical Support for this product.
|
Error (in hex) |
Description |
|
0x0101 Illegal function |
The message function received is not allowed for the addressed slave. |
|
0x0102 Illegal data address |
The address referenced is out of range. |
|
0x0103 Illegal data value |
Invalid data is being written to the PLC. |
|
0x0108 Memory parity error |
An error has been encountered in the computer's memory. |
|
0x28 |
Bad response from PLC |
|
0x104 |
Device inoperative |
|
0x105 |
Acknowledge |
|
0x106 |
Busy – rejected |
|
0x107 |
Negative Acknowledge |