5. Gateway Initialization and Diagnostics
The correct use of this status word by the DeviceNet master, to read a diagnostic generated by the gateway, goes through the following steps:
•Checking of (ABC_HS_SEND ≠ FB_HS_CONFIRM).
• Reading of the value of ABC_DU to determine whether all of the Modbus input data are
• Reading of the value of the “Periodicity of Modbus exchanges” bit to determine whether the periodicity of the Modbus communications has been maintained.
• Reading of the values of EC and ED to check for any error detected by the gateway on the Modbus network (see table below).
• Copying of the value of the ABC_HS_SEND bit to the FB_HS_CONFIRM bit.
This last step is essential because it allows the gateway to transmit a future diagnostic! Even if you do not wish to read the content of the gateway’s status word, it is preferable to automate this step in your DeviceNet master software.
The values of the EC and ED fields are described in the table below:
EC | Description of the error | ED | Notes |
2#0000 | Number of re- | Total number of | |
| Modbus network | transmissions (1) | on the |
2#0001 | A Modbus slave is missing | Address of the missing | — |
|
| Modbus slave |
|
2#0010 | Several Modbus slaves | — | — |
| are missing |
|
|
2#0011 | Excessive data in a | Address of the Modbus | This error occurs when the gateway receives too |
| Modbus response | slave involved | much data in the response sent by one of its |
|
|
| Modbus slaves. |
2#0100 | Unknown Modbus error | Address of the Modbus | — |
|
| slave involved |
|
(1) The
36