Sunday, February 19, 2012

Modbus RTU Protocol

MODBUS is judged as a layer messaging protocol application, offering communication of Master/Slave between machines linked together throughout networks or buses. MODBUS is located at level 7. MODBUS is aimed to be a request or reply protocol and brings services specific by codes of function on the OSI model. The codes functions of MODBUS are parts of MODBUS’ request or reply Protocol Data Unit (PDUs).

In order to make the unit of MODBUS application data, the client have to start a transaction of MODBUS. It is the function which tells the server as to which kind of action to execute. The request format initiated by a Master is recognized by the application protocol of MODBUS. The field of function code is coded into one byte. Only codes in the range of 1 - 255 are decided valid, with 128 to 255 being stored for exclusion responses. It is the field of function code which tells the server of what kind of action to execute when the Master delivers a message to the Slave.

To identify multiple actions, some functions will have sub function codes extra to them. For example, the Master is capable to interpret a group ON/OFF states of discreet inputs or outputs. It could also read or write a group data contents of registers MODBUS. The field of function code is utilized by the Slave to specify either an error free response or an exclusion response when the Master accepts the Slave response. The Slave repeats to the initial request of the function code in the normal response case.

Properties of Data Object
The packets of MODBUS RTU are only aimed to deliver data; they don’t have the ability to send parameters for example resolution, point name, units, etc. If the capability to send such parameters is required, one should examine a EtherNet/IP, BACnet, or extra modern protocols.

MODBUS RTU VS Other Protocols
There are still a lot of good reasons regarding why it is still a nominee amid other protocols of industrial automation despite the limitations of MODBUS RTU. The MODBUS RTU is much easier to realize than newer protocols and is a main force in the market. MODBUS RTU also needs considerably less memory. You can robust the required size of 2Kb on a PIC processor s or mall 8-bit CPU to realize MODBUS RTU, while with EtherNet/IP and BACnet, you might need memory 30-100Kb.

The Requirements of MODBUS RTU Address
The standard node addresses of MODBUS RTU are 1 to 254, with 0 being stored for write and broadcast messages only. Although the 0 address is seldom applied because of the actuality that there is no verification that the message was correctly accepted at the slave node. This doesn’t have much change if your material layer is RS-232 because only one node can be realized anyway. The number of nodes for RS-485 limits to 32, although some drivers will let you to enlarge the amount.

The most essential difference between MODBUS TCP and MODBUS RTU is that MODBUS TCP works on the physical layer of Ethernet and Modbus RTU is a protocol of serial level. Modbus TCP also utilizes a 6 byte header to enable routing.

Bit Structure
The Bit of smallest amount importance is firstly sent and received. All machines within the network have to understand every byte transmitted analogously in this mode There are no techniques for recognition of automated baud rates is not allocated and the same baud rate have to be used by the Server as well as all clients linked to the bus. No particular baud rate is specific by the MODBUS: the characteristic baud rates are 9600 or 19200.


Newer Post Older Post Home

You may also like these ebook:

Get Free PLC eBook directly sent to your email,
and email subscription to

We hate SPAM. Your information is never sold or shared with anyone.

Your Email Will Be 100% Secured !