Modbus, fully unified inside xSERVA
xSERVA brings Modbus meters, generators, and legacy industrial equipment into the same platform as your BACnet, KNX, and MQTT systems, with both Modbus TCP and Modbus RTU supported from day one.
Book a DemoWhat is Modbus?
Modbus is a simple, open serial and network communication protocol originally developed for industrial programmable logic controllers, and now one of the most widely deployed protocols in industrial and building equipment worldwide. Its request/response model — a master device asking a slave device for a specific register value — is straightforward enough that it has been implemented on equipment ranging from decades-old mechanical controllers to modern energy meters. Because Modbus is old, well-documented, and cheap to implement, it remains the default protocol on a huge amount of equipment that predates BACnet, KNX, or MQTT, which makes it essential for any platform that needs to integrate a real building rather than an idealized one.
Modbus TCP and RTU support
xSERVA natively supports both major Modbus transports. Modbus TCP carries the same register-based command structure over standard Ethernet and IP networks, making it the natural fit for modern network-connected meters and controllers. Modbus RTU runs over RS-485 or RS-232 serial links, and remains the standard for older PLCs, generators, and mechanical equipment that has never been networked. Because a single site frequently has both — a newer TCP-connected meter alongside a decade-old RTU-only generator controller — xSERVA reads and writes to both transports through the same interface, so operators do not need to track which wiring standard a given device uses.
Legacy PLC and equipment integration
Modbus is frequently the only option for connecting equipment that was installed long before a modern BAS platform was ever considered: aging PLCs on mechanical plant, generators, standby power systems, and metering hardware that has quietly kept running for twenty years. Rather than forcing a costly hardware replacement just to get that equipment onto a unified dashboard, xSERVA integrates it as-is over Modbus, register by register, and folds it into the same monitoring and alarm infrastructure used for newer BACnet and KNX devices. That makes Modbus support less about a specific vertical and more about protecting the useful life of equipment that already works.
The Modbus Organization, and where recognition stands
The Modbus Organization is the industry body that maintains the official Modbus specification and promotes consistent, interoperable implementation of the protocol across vendors. The xSERVA Modbus integration is built against that official published specification rather than a reverse-engineered approximation pieced together from individual device manuals. For specifiers and integrators, what matters in practice is that register mapping, function-code handling, and per-device data typing inside xSERVA follow the same conventions the wider Modbus ecosystem relies on, reducing the risk of subtle mismatches when connecting third-party meters and controllers.
Formal Modbus Organization recognition is something VYROX is working toward and does not yet hold. See the full certification status →
Where Modbus shows up in real buildings
Modbus is the protocol behind most standalone energy meters, generator and standby-power controllers, industrial PLCs on mechanical plant, and a long tail of older equipment that predates any building-wide network standard. It is especially common in retrofit and brownfield projects, where the goal is to unify an existing equipment estate rather than replace it. xSERVA connects to that Modbus equipment directly, register by register, and folds every meter and controller into the same dashboards, scheduling engine, and energy models used for BACnet, KNX, and MQTT devices on the same site, so a Modbus generator and a BACnet chiller plant can be monitored and reported on from one console.
Frequently asked questions
Does xSERVA support both Modbus TCP and Modbus RTU?
Yes. xSERVA natively supports Modbus TCP for network-connected devices and Modbus RTU for serial field devices, so both modern and legacy Modbus equipment can be integrated.
Can xSERVA integrate old equipment that only speaks Modbus RTU?
Yes. Modbus RTU support is exactly what lets xSERVA bring legacy meters, generators, and PLCs onto the same platform as modern BACnet, KNX, and MQTT devices, without replacing the equipment.
Is VYROX a member of the Modbus Organization?
Not yet. Formal Modbus Organization recognition is something VYROX is working toward, not a credential already on file. What is true today is that the xSERVA Modbus integration is built against the official published specification — register mapping, function-code handling, and per-device data typing follow the conventions the wider Modbus ecosystem relies on. If membership is a condition of your tender, message our team for the current status.
What kind of equipment typically communicates over Modbus?
Energy meters, generators, industrial PLCs, and older mechanical equipment are the most common Modbus devices, since it has been the default industrial communication protocol for decades.