Wireless BACnet and Modbus with mixed baud rates on one network
Most retrofit and expansion projects start in a building that already works. The controllers have been in place for years, the meters came later, and the new equipment comes from yet another vendor. One detail is easy to miss until commissioning: they don’t all communicate at the same baud rate.
The baud-rate problem on a wired trunk
On an RS-485 trunk, whether it carries BACnet MS/TP or Modbus RTU, every device has to share one baud rate. If the existing controllers run at 9,600 bps and the new equipment at 38,400 bps, you have three options:
- Reconfigure the existing devices, sometimes without current documentation or the right tool.
- Set the new equipment down to the old rate and accept the slower trunk.
- Split the network into separate trunks, with extra cable runs and extra ports at the panel.
Each option takes time. The first also carries a real risk: you change a setting on a working device and find out during commissioning that something else has stopped working.
How W-BACnet and W-Modbus handle it
W-BACnet and W-Modbus replace the RS-485 cable with a wireless mesh. Each field device connects to its own node, and a gateway connects the network to your BMS (with W-Modbus, your BMS, SCADA or HMI system). The data stays BACnet MS/TP or Modbus RTU, so objects, registers, and addressing stay the same.
Baud rate is configured per node. The gateway keeps running at the baud rate your existing system already uses, and each node either inherits the gateway’s settings or uses its own local baud rate. Each node communicates with its device at that device’s baud rate, so devices running at different baud rates can share the same wireless network. The protocol itself doesn’t change.
W-BACnet nodes find the rate themselves. With autobaud enabled (DIP switch 4 on Wall mount and DIN), a node listens for BACnet MS/TP messages from its device and locks on to the right baud rate. If it can’t detect one, it falls back to the gateway’s settings. The W-BACnet Compact always tries autobaud first.
W-Modbus nodes are set locally. On W-Modbus Wall mount and DIN nodes, you set baud rate, parity, and stop bits with the node’s DIP switches. The W-Modbus Compact always uses the gateway’s baud rate, so use Wall mount or DIN nodes for devices that run at a different rate.
Supported settings:
- Baud rate (W-BACnet and W-Modbus): 9,600, 19,200, 38,400 or 76,800 bps
- Additional rates with autobaud (W-BACnet, firmware 4.0.0 or later): 57,600 and 115,200 bps
- Parity and stop bits (W-Modbus): none or even, 1 or 2
What it means on site
Design around the equipment. You plan the network around where devices sit and what the BMS needs. Which devices share a baud rate no longer matters, and you don’t need a separate trunk per rate.
Leave working equipment alone. Existing controllers keep their settings. There’s no need to dig up an old configuration tool or retest a sequence that worked before you arrived.
Expand without reopening the installation. When a tenant fit-out or new plant adds devices at a different rate, they join the network with their own settings.
Fewer surprises at commissioning. Each node only has to match the device it’s connected to. For the installer, that means setting the gateway, turning on autobaud with DIP switch 4 on W-BACnet nodes or setting the DIP switches on W-Modbus nodes, and validating the installation in the W-BACnet or W-Modbus app.
A typical scenario: a VAV retrofit with mixed equipment
Take a typical office floor upgrade. The existing VAV controllers run BACnet MS/TP at 9,600 bps. The owner wants to add new equipment from another vendor, configured for 38,400 bps, and pulling new cable through occupied ceilings is off the table.
With W-BACnet, the nodes at the VAV controllers detect 9,600 bps and the nodes at the new equipment detect 38,400 bps. The BMS sees the same devices, objects, and addresses as before.
With W-Modbus, the pattern is the same. An older energy meter at 9,600 bps and newer equipment at 19,200 bps each sit on a Wall mount or DIN node set to their own rate, and the Modbus client polls the same registers as before.
Part of a broader design principle
Baud-rate agnosticism is a small line on a datasheet. It reflects how we design W-BACnet and W-Modbus as a whole: wireless should fit into the installation and workflow you already have. The same thinking applies to hybrid installations, Remote Diagnostics, LON replacement and security, which we will cover in upcoming articles.
Talk to us about your project
Planning a retrofit or expansion with devices at different baud rates? Tell us about the site and the equipment, and we’ll help you plan the network.
Or see the Get Started with W-BACnet page and the Get Started with W-Modbus page.
