ProSoft Insights / Vidéos

Modbus 101: The Protocol Basics You Need to Know





Yes, I would like to receive marketing information from ProSoft Technology, Inc., and its affiliates, subsidiary companies and brands indicated below.

I therefore provide my consent to the use of the personal information submitted here for the purpose of providing me marketing information related to ProSoft Technology, Inc. and its affiliates’ and subsidiaries’ products, services and marketing events. I understand that I may withdraw my consent at any time. Additional information regarding ProSoft’s data privacy policies, including how to withdraw this consent, is available at ProSoft Technology, Inc. is a subsidiary of Belden Inc., and their affiliates, subsidiary companies and brands include ProSoft Technology SAS, ProLinx Comunicacao Industria, LTDA; Global Blue Networks Inc., and ProSoft Technology (Asia Pacific) SDN BHD.

Articles récents

Consider the Benefits: Enable Secure Remote BAS Monitoring with QuickServer Gateway Upgrade

08 juin, 2023 / Infos produits

The latest update to ProSoft’s Universal QuickServer Gateway product line includes the ...

A Primer on Process Controls in Industrial Environments

16 mai, 2023 / Points techniques

A process control can be simple and straightforward or dynamic and complex, with a need...

Consider the Benefits: RLX2 Update Makes it Easier and More Secure to Manage and Configure AGVs

18 avr, 2023 / Infos produits

The latest update to ProSoft’s Fast Industrial Hotspot (RLX2-IHNF) makes configuration ...

Your FAQs About Cloud-Based Networking Solutions

29 mars, 2023 / Points techniques

We’ve been hearing from more companies lately about how cloud-based networking solution...

Modbus 101: The Protocol Basics You Need to Know

Modbus is a classic and widespread protocol for a reason. Originally developed by Modicon in 1979 for use in the company’s PLCs, the serial communications protocol has become a giant in the industrial automation industry. Today it’s an open protocol, used by a variety of devices.

That’s where ProSoft came in over 30 years ago: Our first module linked an Allen-Bradley® processor to a Modbus SCADA host. (It definitely points to why we’re still sometimes referred to as “the Modbus guys.”)

We still hear a lot of questions about Modbus at industry events, and our support team gets a lot of queries as well.

Today we’re taking a brief look at the three primary variations of the Modbus protocol; and sharing a full explainer video exploring the protocol, including Modbus data addressing; float and double integer values and how Modbus handles them; and more protocol basics you need to know.

Modbus: ASCII, RTU, and TCP/IP

Modbus ASCII, Modbus RTU, and Modbus TCP/IP are the three major types of Modbus protocols used today.

∙ ASCII characters were used in Modbus’ initial development, and it’s still used today in a variety of applications, including equipment at oil and gas sites, and in barcode readers in logistics facilities. It’s incompatible with Modbus RTU, so devices using one cannot communicate with equipment using the other.

∙ Modbus RTU is implemented most frequently, and uses binary coding. Modbus RTU devices can employ one of three electrical interfaces – RS232, RS485, or RS422. RS232 is ideal for point-to-point connectivity that needs to cover a distance of less than 50 feet. If you need multi-point connectivity and/or have a distance of greater than 50 feet, you’ll want to opt for RS485 or RS422.

∙ Modbus TCP/IP was one of the first industrial Ethernet protocols. Essentially, these applications have Modbus devices use Ethernet cables and switches to communicate with each other. A typical Modbus TCP/IP implementation features the use of an MBAP header, which includes the identifying information that’s needed to route the data to the correct device. Serial messages can also be sent as RTU messages encapsulated in a TCP/IP packet. However, devices must be set up to use either MBAP or serial messaging.

Check out the full Modbus primer below:

Which Modbus connectivity solution does your application need?