ONICON Incorporated 727-447-6140
Page 44
www.onicon.com
SYSTEM-20 BTU METER
11 (0B Hex) Return Bus Message Count
The response data field from the System-40 returns the quantity of messages
that it has detected on the communications system since its last restart, restart
communications option, or power-up.
This count is also available in the System-40’s diagnostic menu page.
12 (0C Hex) Return Bus Communication Error Count
The response data field returns the quantity of CRC errors encountered by the
System-40 since its last restart, restart communications option, or power-up.
This count is also available in the System-40’s diagnostic menu page.
13 (0D Hex) Return Bus Exception Error Count
The response data field returns the quantity of MODBUS exception responses
returned by the System-40 since its last restart, restart communications option, or
power-up.
This count is also available in the System-40’s diagnostic menu page.
14 (0E Hex) Return Server Message Count
The response data field returns the quantity of messages addressed to the
System-40, or broadcast, that the System-40 has processed since its last restart,
restart communications option, or power-up.
This count is also available in the System-40’s diagnostic menu page.
15 (0F Hex) Return Server No Response Count
The response data field returns the quantity of messages addressed to the
System-40 for which it has returned no response (neither a normal response nor
an exception response), since its last restart, restart communications option, or
power-up.
This count is also available in the System-40’s diagnostic menu page.
17 (11 Hex) Return Server Busy Count
The response data field returns the quantity of messages addressed to the
System-40 for which it returned a Server Device Busy exception response, since
its last restart, restart communications option, or power-up.
This count is also available in the System-40’s diagnostic menu page.
18 (12 Hex) Return Bus Character Overrun Count
The response data field returns the quantity of messages addressed to the
System-40 that it could not handle due to a character overrun condition, since its
last restart, restart communications option, or power-up. 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.
This count is also available in the System-40’s diagnostic menu page.