In industrial equipment connectivity, building automation, equipment-room power and environment monitoring, and energy-metering projects, RS-485 is often the first layer of on-site data access. Tongwei Smart’s practice in these projects is that the gateway is responsible for connecting the equipment, and the platform is responsible for alarms, work orders, and operations records. When communication is unstable, check the physical link first, rather than attributing the cause to the gateway or the platform first.
The most common field problem, and the one most easily let through, is wiring topology. The fact that equipment has A and B terminals does not mean several branches can be split at will from one junction box. When there are few devices and the distance is short, a star connection can sometimes still communicate. After the number of devices increases, the cable is pulled longer, or the baud rate is raised, packet loss and timeouts appear easily, and the whole bus can even drop together.
RS-485 should be connected as a bus-type daisy chain
RS-485 is a differential bus. Engineering practice recommends connecting the equipment in sequence with one trunk line, that is, a daisy-chain or bus-type connection. The master leads out the trunk, passes through one device and then the next, until the end. Intermediate devices are tapped onto the trunk, and the stub lines are kept as short as possible.
What needs to be avoided is a star, a tree, and wide branching. Each branch point causes an impedance discontinuity, and the signal reflects at the cable end. At low speed and short distance, reflection does not necessarily show up as a fault at once. After the baud rate is raised, the line becomes longer, and the number of nodes increases, reflection and interference become intermittent errors.
Bus topology and Modbus broadcast are not the same thing
Bus-type wiring for RS-485 refers to the physical layer. Broadcast in Modbus RTU refers to the protocol. A broadcast message at address 0 can let several slaves receive a write command, but slaves usually do not return a response. A broadcast at the protocol level cannot be taken as a basis for wiring the field cable into a star network.
When the site is already wired as a star, pull it back to the shortest link first
Do not start by changing parameters over and over in the platform. Bring the link back in the following order.
- Confirm the master, the slave, the cable, and the power supply. First build the shortest daisy-chain link, leave only one master and one slave, and verify basic communication.
- Then add the devices back one by one in order. Each time a device is added, record whether communication is stable.
- After the branch that causes the fault is found, change it to a continuous trunk first. When the wiring conditions are truly constrained, then evaluate a verified RS-485 hub or repeater, rather than simply paralleling several branches.
Three details easily overlooked together with topology
- The naming of A and B may be reversed between manufacturers. Do not rely on the silkscreen alone. Follow the manual and the actual message.
- Termination resistors are fitted at the two ends of the bus, not on every device.
- Shielding, reference ground, and isolation should be confirmed according to the equipment manual, the power system, and the site equipotential plan. They should not be shorted by habit.
Confirm the safety boundary before changing the wiring
Before rewiring, plugging or unplugging terminals, or adjusting a termination switch, first disable the related control, remove power, and confirm that there is no risk of unintended action. Where power distribution, pumps, fans, access control, and other actuators are involved, communication commissioning cannot replace on-site safety permission and the protection of the original system.
Frequently asked questions
- If a star can still communicate when there are few devices, can it be kept?
- At short distance and low speed, the problem may not show for a while. After the number of devices increases, the line becomes longer, or the baud rate is raised, reflection from the branches more easily becomes packet loss and timeouts. When it can be changed to a continuous trunk, the topology should be changed first.
- If Modbus can broadcast, can the cable also be split out as a star?
- No. Broadcast is a write command at the protocol layer, and slaves usually do not respond. The recommended RS-485 connection is still one trunk and short stub lines.