RS485, Modbus RTU, Device Address, Registers and CRC: A Complete Sensor Communication Guide

Many integration problems are not "wired", but a mixture of RS485, Modbus RTU, device address and registers. When these layers are separated, PLC, RTU, gateway and computer debugging will be much clearer.

Let's first clarify the four concepts

RS485 is an electrical interface standard for serial communication that specifies how differential signals are transmitted on both A/B lines. It addresses “how to reliably send out electrical signals” and does not define where temperature, humidity or wind speed data are placed.

Modbus RTU is a common serial communication protocol. The device address (Slave ID) is used to distinguish different devices on the same bus, the function code determines the read or write operation, and the register address tells the master device where a certain measurement value is stored. CRC is the check code at the end of the message, which is used to check whether there is an error in the data transmission process.

What Exactly Happened to a Normal Read

• The master device opens the serial port according to the set baud rate, data bits, stop bits and parity mode.
• Send a Modbus query frame to the specified Slave ID.
• The sensor takes out the measured value in the corresponding register and returns it.
• The master device converts the original value into the engineering unit according to the data type, magnification and decimal places.

Therefore, “being able to receive the message” and “parsing the data correctly” are two different stages. Be able to receive a valid Modbus response, at least indicating that the power supply, wiring, and the basic communication link is generally working; if the values are abnormal, it is more appropriate to check the register order, magnification, byte order, and data type.

Practical practices when integrating NiuBoL sensors

Many NiuBoL soil, meteorological and water quality sensors use RS485/Modbus RTU. In actual engineering, it is usually more efficient to directly connect the USB-RS485 converter to the computer to verify the original message, and then connect it to the PLC, RTU or IoT gateway than to troubleshoot it directly on the cloud platform.

When you need to view specific registers and communication examples, you can start from the corresponding model pages and instructions of NiuBoL RS485 soil sensor, NBL-W-71GUWS 7-in-1 ultrasonic weather sensor, etc.

Most error-prone

• Treating RS485 as the protocol name and checking only the interface while ignoring the Modbus register table.
• Multiple devices use the same Slave ID, causing communication conflicts.
• Poll with the old address after modifying the device address.
• A command was copied without recalculating CRC by a new address or length.
• The number of registers read is incorrect, for example a three-parameter sensor reads only two registers.

FAQ

Q1: Is RS485 and Modbus RTU the same thing?

A1: No. RS485 is the electrical interface and Modbus RTU is the communication protocol. A device can use an RS485 interface and run Modbus RTU, or it can run other serial protocols.

Q2: Is Slave ID the same thing as the device address?

A2: In Modbus RTU scenario, it usually refers to the same concept, which is used to distinguish different slave devices on the same bus.

Q3: Why is CRC likely to change each time the command is modified?

A3: CRC is calculated for the entire message. If any bytes such as the device address, register address, data length, etc. change, CRC will need to be recalculated.

Q4: Can the sensor be read as long as the PLC has an RS485 port?

A4: PLC is also required to support the corresponding Modbus RTU master device function, and correctly configure the serial port parameters, device address, registers, and data format.