- RS485 is a physical-layer interface standard, while Modbus RTU is a communication protocol that can run over RS485.
- RS485 networks typically use shielded twisted-pair cables and daisy-chain wiring, with 120Ω termination resistors recommended at both ends of longer networks.
- The number of connected devices and communication distance depend on factors such as transceiver capacity, cable quality, baud rate, and the use of repeaters.
- RS485 energy meters enable remote monitoring of electrical parameters such as voltage, current, active power, reactive power, and power factor.
- With long-distance transmission, strong noise immunity, and multi-device communication, RS485 energy meters are widely used in residential, commercial, and industrial energy management systems.
Interface Standards
First, let’s clarify: RS485 is not a communication protocol but an interface standard, alongside its two counterparts, RS232 and RS422. “RS” stands for Recommended Standard. For serial communication, RS232 and RS485 are commonly used in industrial applications, while RS422 is less frequent. RS485 is widely adopted due to its advantages like noise immunity, long-distance transmission, and multi-node support. Below is a comparison chart of RS232, RS422, and RS485.
Performance comparison of RS-232, RS-422 and RS-485
Wiring Methods
RS485 supports one-to-many connections, so how should we wire multiple RS485 devices? First, when choosing cables, it is recommended to use shielded twisted-pair cables, such as RVSP2*0.5 (two-core shielded twisted-pair cable, each core consisting of 16 strands of 0.2 mm wires) with a characteristic impedance of 120Ω. The correct wiring method is a daisy-chain, or hand-in-hand, connection. If the communication distance is long (e.g., over 100 meters), add a 120Ω resistor at both the start and end of the network to reduce signal reflection.
A common mistake, often used by many, is the star or tree topology. Although this setup may work for a small number of devices, it’s recommended to use the correct daisy-chain approach from the start, which facilitates troubleshooting and prevents rework.
Device Capacity
A frequent question is, “How many RS485 devices can be connected on a single RS485 bus?” The exact number depends on the load capacity of the RS485 converter. Generally, RS485 chips come in three levels, capable of supporting 32, 128, or 256 devices. Usually, the RS485 converters we use support up to 32 devices. It’s also advisable not to overload a single RS485 bus, as managing issues becomes more complex. If there are numerous devices, consider expanding the number of RS485 buses to distribute the load. For instance, 100 devices can be divided across 4 RS485 buses, with each bus carrying 25 devices.
Transmission Distance
Theoretically, RS485 can communicate over a distance of 1200 meters without a repeater. However, this assumes ideal conditions: a high-quality communication cable, a baud rate of 9600 bps, only one RS485 device, and allowance for occasional communication interruptions.
In reality, factors like increased device load, subpar cable quality, and RS485 converter performance reduce communication distance. Normally, for distances over 100 meters, terminal resistors should be added, and for distances exceeding 1000 meters, RS485 bus repeaters should be considered.
Communication Protocol
What is the relationship between Modbus RTU and RS485? To be precise, they operate at different levels. Modbus RTU is a communication protocol at the application layer, whereas RS485 is a physical layer interface standard.
When we talk about Modbus RTU communication, we usually mean it over RS485, but Modbus RTU can also be used over RS232, RS422, or even Ethernet TCP/UDP. Meanwhile, RS485 is not exclusive to Modbus RTU; any protocol can be transmitted via RS485. Whether it supports a master-slave configuration depends on whether the protocol layer includes device addressing.
To implement a master-slave configuration, both the physical layer and application layer must support it. For instance, if RS232 is used at the physical layer, even with the Modbus RTU protocol at the application layer, master-slave cannot be achieved.
Communication Speed
Many people perceive the Modbus protocol as slow, a notion that has been passed down over time. But is it really the case? Let’s analyze this in detail.
Communication speed is mainly affected by two factors: the data volume and the hardware speed. Data volume refers to the amount of data to be transmitted, while hardware speed depends on communication devices and network infrastructure; these two factors jointly determine communication speed.
For example, think of package delivery. The total time depends on the number of packages, the distance, and the mode of transportation.
Firstly, Modbus is a communication protocol, and it doesn’t inherently have a speed. Modbus messages are compact and efficient, using minimal frames to convey information compared to other protocols that may have more complex and voluminous messages.
Secondly, hardware speed relates to baud rate and communication distance. So if it seems “slow,” it’s really the serial communication that’s slow—not Modbus itself.
The following chart shows real-world communication results with Modbus TCP and various PLCs and boards. These are real test results without any bias.
Many people pursue high speeds, but for control systems, extremely high speeds may not be necessary. Human perception can register motion at around 25 frames per second (or 40 ms per frame), meaning speeds beyond this are largely imperceptible.
Master-Slave Communication
Some might find Modbus RTU slow due to the master-slave polling mechanism. The Modbus protocol’s message structure includes device addresses, which allows RS485 to implement master-slave communication. This configuration simplifies wiring, eases management, and saves costs.
In scenarios where communication demands aren’t too high, master-slave setups can be a good solution. However, the polling mechanism will inevitably affect communication efficiency. If you choose this setup, you must accept its limitations; otherwise, it might not be the right choice.
What is an RS485 Energy Meter?
The RS485 energy meter is a metering device equipped with RS485 remote communication capabilities. It enables real-time monitoring of key parameters such as current, voltage, power factor, active power, and reactive power. This allows both users and power companies to gain real-time insights into electricity usage, effectively controlling grid load and costs.
The RS485 energy meter offers excellent communication performance and application advantages, including:
- Long Communication Distance: RS485 meters can transmit data over distances of up to 1,200 meters, making them suitable for large-scale buildings requiring energy measurement and data collection.
- Strong Anti-Interference: The RS485 protocol uses a balanced driver and differential receiver combination, ensuring strong resistance to common-mode interference. This ensures stable and reliable operation while supporting high-speed, long-distance communication.
- Bidirectional Communication: RS485 energy meters can simultaneously send and receive data, supporting multiple communication protocols such as Modbus, DLT645, IEC1107, and DLMS. This allows seamless integration with various devices to meet energy meter data exchange requirements.
- Cost-Effective Half-Duplex Communication: Utilizing a single bus, RS485 enables communication with multiple devices, reducing wiring costs. The RS485 communication interface is also economical compared to other modules.
- Wide Application Range: These meters are ideal for residential electricity monitoring, commercial energy management, industrial power monitoring, and equipment energy tracking.
In conclusion, I believe every approach has its value. A skilled engineer should learn to choose the right solution for the situation to achieve their objectives efficiently.