Scribd
Upload
540 views

Difference Between RS485 & Modbus Protocol

RS485 is a hardware serial interface standard that defines how data is transmitted physically, while Modbus is a messaging protocol that defines the format and content of messages. Modbus requires messages transmitted over a serial line to end after 3.5 character times of inactivity, but this is unnecessary for Ethernet which ends messages at packet boundaries. When using Modbus over Ethernet, there can be issues with duplicate CRC checksums at the message and packet levels.

Uploaded by

erkamlakar2234
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
540 views

Difference Between RS485 & Modbus Protocol

RS485 is a hardware serial interface standard that defines how data is transmitted physically, while Modbus is a messaging protocol that defines the format and content of messages. Modbus requires messages transmitted over a serial line to end after 3.5 character times of inactivity, but this is unnecessary for Ethernet which ends messages at packet boundaries. When using Modbus over Ethernet, there can be issues with duplicate CRC checksums at the message and packet levels.

Uploaded by

erkamlakar2234
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

Difference between RS485 & Modbus Protocol http://www.edaboard.com/thread180181.

html

Difference between RS485 & Modbus Protocol


RS485 is hardware serial-interface standard that defines the hardware for carrying a message.
Modbus is a messaging protocol that defines the content of that message.
So far, so good: the two do not 'differ' at all. BUT, there is one hardware requirement for Modbus
over a SERIAL-line: the message ends when no character has been sent for 3.5(?) character-
times.
That requirement is meaningless for Ethernet because a message 'ends' when its packet ends.

Another potential problem is that Modbus defines a CRC for its messages and Ethernet already
has a CRC on its packets.

You need to know how your converter works: how it knows when an output-packet starts and
when it ends.

1 of 1 11/05/17, 10:00 AM

You might also like