Introduction - Honeywell UDC2800 Product Manual

Chapter 13 - Modbus Communication Exception Codes

Introduction

222
When a master device sends a query to a responder device it expects
a normal response. One of four possible events can occur from the
master's query:
Responder device receives the query without a communication
n
error and can handle the query normally.
It returns a normal response.
Responder does not receive the query due to a communication
n
error No response is returned. The master program will eventually
process a time-out condition for the query.
Responder receives the query but detects a communication error
n
(parity, LRC or CRC).
No response is returned. The master program will eventually
process a time-out condition for the query.
Responder receives the query without a communication error but
n
cannot handle it (i.e., request is to a non-existent coil or register).
The responder will return with an exception response informing
the master of the nature of the error (Illegal Data Address.)
The exception response message has two fields that differentiate it
from a normal response:
Function Code Field
In a normal response, the responder echoes the function code of the
original query in the function code field of the response. All function
codes have a most-significant bit (MSB) of 0 (their values are below
80 hex). In an exception response, the responder sets the MSB of the
function code to 1. This makes the function code value in an
exception response exactly 80 hex higher than the value would be for
a normal response.
With the function code's MSB set, the master's application program
can recognize the exception response and can examine the data field
for the exception code.
Data Field:
In a normal response, the responder may return data or statistics in
the data field. In an exception response, the responder returns an
exception code in the data field. This defines the responder condition
that caused the exception.