Modbus is an open serial communications protocol. It was developed in 1979 for use with Programmable Logic Controller (PLC) devices, and is now widely used for connecting many types of industrial electronic devices connected on different types of networks.
Modbus is not part of a physical layer on a network, as with some other protocols. Modbus communications are transferred on top of physical layers, enabling it to be utilized on many different types of networks. This non-physical layer property makes Modbus an application layer protocol.
There are two variants of the Modbus protocol that travel over serial connections: The Modbus RTU and the Modbus ASCII.
This variation is more compact, and uses binary communication. In this format, data transmissions are always followed by a cyclic redundancy check checksum, which are used to detect transmission problems.
This version is more verbose, and it uses hexadecimal ASCII encoding of data that can be read by human operators. A different type of checksum, the longitudinal redundancy check checksum, takes place after Modbus ASCII data transmissions. Modbus ASCII is the less secure of the two variants.
As it is also less efficient than Modbus RTU, operators should only utilize Modbus ASCII for the transmission of data to devices which do not support the Modbus RTU format. Modbus ASCII can also be useful when RTU messaging cannot be properly applied.
Modbus communications take place between a centralized master and up to 247 connected electronic devices on a single network.
The design is commonly referred to as a "master/slave" protocol, because the system "master" requests information from connected devices, which are referred to as "slaves".
Slave devices only send information to the master in response to these requests, and do not operate autonomously. The master can also write information to the slave devices, but the slave devices cannot write information to the master.
When a slave device transmits a communication to the Modbus master, it begins the message with a unique address identifier. This is a number ranging from 1 to 247. This enables the master to identify which specific device is responding with the requested information.
There is no other network on the planet that is exactly like yours. For that reason, you need to build a monitoring system that's the right fit for you.
"Buying more than you need" and "buying less than you need" are real risks. You also have to think about training, tech support, and upgrade availability.
Send me a quick online message about what you're trying to accomplish. I'll work with you to build a custom PDF application diagram that's a perfect fit for your network.
Join over 17,000 clients and receive a personalized quote and virtual model. Then let our field-proven units and 30 years of industry experience do the rest.