Modbus

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 a Widely Used Protocol
Modbus is used extensively for a number of reasons, including the following:

Modbus Utilizes Serial or Ethernet Connections
The Modbus protocol can be used with two types of serial connections, both RS-232 and RS-485. Some versions of Modbus can also be sent over Ethernet or TCP/IP. These Modbus communications are packed as a single bit, or 16-bit word packets.

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.

Two Variants of the Modbus Protocol
There are two variants of the Modbus protocol that travel over serial connections. One of these is Modbus RTU. 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.

The second variant is Modbus ASCII. 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 is a "Master/Slave " Protocol

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.


Download the SCADA White Paper

Related Products:
T/Mon NOC

Related Topics
Modbus rs485/rs232


Give Us a Call!

To find out more about this and other DPS applications, give us a call at our toll-free number and talk to one of our network specialists. They'll help you put together a perfect fit solution for your network!

Sales: 1-800-693-0351 · Fax: 559-454-1688
 Print-Friendly Format of this Page
 Join a Live Meeting Room with an Application Engineer
Related Pages
Popular White Papers

SNMPv3 Tutorial - New!

SNMP MIB Tutorial

SCADA Tutorial

SNMP Implementation

View All 33 Tutorials...

About DPS Telecom

Contact Information

News & Press Releases

Sales Representatives

DPS Departments

Industries Served

Factory Training Events

Factory Training Signup

Client Success Stories

Client Testimonials

Career Opportunities

Subscribe to Our DPS News Feed

  RSS

Add to Google

Add to My Yahoo!

Add to My MSN button

Name:

E-mail:

View past issues

Subscription options