Modbus Exception Codes; Table 16: Exception Codes - ABB AWIN GW100 User Manual

MOD BU S E XC E PT IO N CO DE S
Problem
Device connects and discon-
nects
Unable to connect new de-
vice
I/O Schedule Upload Failed
Low battery lifetime
Radio signal is weak
Weak mesh network
8.3

Modbus Exception Codes

The following exception codes are supported.
Exception code
0x01 ILLEGAL_FUNCTION
0x02 ILLEGAL_DATA_ADDRESS Starting address does not exist in mapping.
0x03 ILLEGAL_DATA_VALUE
5 2
Solution
Verify WirelessHART field device, adapter or wired HART device sup-
ports the command.
Trying to read data from unmapped register will result in exception.
If the device does not have good radio signal, then it can have unsta-
ble connection. This can be seen by looking into RSSI, latency, stabil-
ity and number of joins in network statistics page. If the number of
joins keep going up, then add repeater nodes (if possible) to im-
prove network reliability, stability and availability.
RSSI of the device's active link should be better than -75dBm.
If it is not possible to add a new device, make sure that there is re-
maining capacity left in the gateway to add new device. To check,
login to the network statistics page. Up to 24 devices can connect to
AWIN GW100.
Connected devices number can be reduced to 8 if all devices burst 3
messages simultaneously at 1sec update period.
When downloading the devices configuration to a gateway where
some devices are offline will result in this error. This error is followed
with a summary of device(s) which failed. For all other devices, con-
figuration upload is successful.
Try to bring the offline device online and import again.
If a device shows low battery lifetime then replace its battery by fol-
lowing the service manual of that device.
Make sure there is clearance around the antenna. Look into the
guidelines for installation of antenna in the antenna used in the
setup.
Login to the network statistics page and verify that each device can
communicate to at least 3 neighbors (recommended). If so, the de-
vice row will be color coded green.
If not, make sure that all connected devices are operating as mesh
nodes (i.e., routing enabled). You can verify this by logging into the
monitor account and looking at Devices Information page. To ena-
ble/disable routing status the user can use Devices Configuration
import file.

Table 16: Exception codes

Meaning
No request bytes present.
Read request for "Number of Neighbors" register for sub-de-
vice in simplified mapping.
Starting register valid, but length of requests spans at least
one unmapped register.
TR OU BL ES H OOT ING
3BN P 102 9 12 C