Modbus Agile
02/2011
24
Protocol
7 Protocol
The MODBUS serial communication protocol is a Master/Slave-Protocol. With the bus only one master
is connected (at a time). One or several (max. 247) slave-nodes are connected with each other on the
same bus. A MODBUS communication is always initiated by the master. The slave nodes do not com-
municate with each other. The master only initiates one MODBUS communication at a time.
The master sends a MODBUS request to the slave-nodes in two different operation modes::
−
In the Unicast operation mode the master addresses a single slave-node. After reception and
processing of the request, the slave-node sends a message (reply) to the master. In this operation
mode a MODBUS transfer consists of two messages: a request from the master and a reply from
the slave-node. Each slave-node must have a unique address (from 1 to 247), so that the slave-
nodes can receive requests independent of each other.
−
In the Broadcast operation mode the master can send a request to all slave-nodes. The slave-
nodes do not send a reply to the request.. The request consists of write commands. All slaves must
accept the write commands. Address 0 is reserved for the recognition of a broadcast request.
7.1
Address Representation
Up to 247 frequency inverters can be operated on MODBUS. These are assigned addresses in the
range 1 … 247. With address 0, all clients connected to the bus can be addressed simultaneously.
Address 0 is also referred to as the Broadcast-Address.
7.2
Message Structure
A MODBUS message is made up of the following fields:
Address
Function Code Data
CRC (or LRC)
The Address field contains the slave-address in the Modbus message.
Valid slave node addresses are in the range of 0 – 247 (decimal). The individual slave devices are
assigned addresses in the range of 1 – 247. A master addresses a slave by placing the slave address
in the address field of the message. When the slave returns its response, it places its own address in
the response address field to let the master know which slave is responding.
The Function Code indicates to the inverter what kind of action to perform. The function code can
be followed by a
Data field that contains request parameters (or, in the case of the inverter's re-
sponse, the response parameters).
If no error occurs related to a correctly received Modbus request then the data field contains the data
requested. If an error occurs then the field contains an Exception Code to indicate to the master that
the request was unsuccessful. Exception Responses and Codes are described in detail in chapter 7.3.9
"Exception Codes".
If a request is not received correctly (communication error, checksum error) then no response is sent.
The inverter waits for the next request.
The Error Checking Field is the result of a "Redundancy Checking" calculation that is performed on
the message contents. Two kinds of calculation methods are used depending on the transmission
mode that is being used (RTU or ASCII). See Chapter 7.3.10 "Modbus Transmission Modes".
Summary of Contents for Agile
Page 1: ...Agile Modbus Communication manual Frequency inverter 230V 400V ...
Page 2: ......
Page 5: ...Modbus Agile 5 02 2011 13 2 Warning Messages Application 76 13 3 Error Messages 76 INDEX 77 ...
Page 44: ...Modbus Agile 02 2011 44 Handling of Data Sets Cyclic Writing ...
Page 69: ...Modbus Agile 69 02 2011 10 2 1 Statemachine diagram ...
Page 78: ......
Page 79: ......
