Raycap ProSMS 8, Installation Manual

Page: 19 / 24

2017 ©Raycap • All rights reserved
130 620 300 Rev.C 171116
Page 19 of 24
www.raycap.com
INSTALLATION MANUAL
ProSMS 8
Diagnostic registers, MODBUS function Read 8
MODBUS function code 08 provides a series of tests to check communication between the client
(Master) and the Slave (ProSMS), or to check various internal error conditions within the ProSMS. This
functionality is most useful during installation to check that there are no communication problems across
the network before commissioning. It is recommended to read diagnostics registers once per month to
confirm that the network is still performing optimally.
The function uses a two–byte sub-function code field in the query to define the type of test to be
performed. ProSMS echoes both the function code and sub-function code in a normal response.
The following diagnostic functions are supported by ProSMS:
Sub function diagnostic return codes response data filed. Detailed description:
10 (0x0A) Clears all MODBUS diagnostic counters and registers. After the command is issued
all counters start to count from zero.
11 (0x0B) Quantity of messages that the ProSMS has detected on the communications system
since: last power–up (every morning), last clearing of this counters or after a remote
ProSMS restart.
12 (0x0C) Quantity of CRC errors encountered by the ProSMS since: last power–up (every
morning), last clearing of this counters or after a remote ProSMS restart.
13 (0x0D) Quantity of MODBUS exception responses returned by the ProSMS since: last
power–up (every morning), last clearing of this counters or after a remote ProSMS
restart.
14 (0x0E) Quantity of messages addressed to the ProSMS (including broadcast messages)
that the remote device has processed since: last power–up (every morning), last
clearing of this counters or after a remote ProSMS restart.
15 (0x0F) Quantity of messages addressed to the ProSMS for which it has returned no response
(neither a normal response nor an exception response), since: last power–up (every
morning), last clearing of this counters or after a remote ProSMS restart.
16 (0x10) Quantity of messages addressed to the ProSMS for which it returned a
Negative Acknowledge (NAK) exception response, since: last power–up (every
morning), last clearing of this counters or after a remote ProSMS restart.
17 (0x11) Quantity of messages addressed to the ProSMS for which it returned a
Slave Device Busy exception response, since: last power–up (every morning), last
clearing of this counters or after a remote ProSMS restart.
18 (0x12) Quantity of messages addressed to the ProSMS that it could not handle due to a
character overrun condition, since: last power–up (every morning), last clearing of
this counter or after a remote ProSMS restart. A character overrun is caused by data
characters arriving at the port faster than they can be stored, or by the loss of a
character due to a hardware malfunction.
Subfunction Data Type Possible Ret. Values Unit Description
00 UINT16 0..65536 Return Return query data
01-09 Not used
10 UINT16 0..65536 Return Clear counters and diagnostic registers
11 UINT16 0..65536 Counter Return bus message count
12 UINT16 0..65536 Counter Return bus communication error count
13 UINT16 0..65536 Counter Return bus exception error count
14 UINT16 0..65536 Counter Return slave message count
15 UINT16 0..65536 Counter Return no response count
16 UINT16 0..65536 Counter Return slave NAK count
17 UINT16 0..65536 Counter Return slave busy count
18 UINT16 0..65536 Counter Return bus character overrun count
Diagnostics