A BACnet to Modbus gateway maps Modbus RTU registers onto BACnet objects (AI, AO, AV, BI, BO, BV) so one BMS can supervise chillers, VFDs and meters without BACnet. Capacity is the constraint: Matinal's QSP-800B handles 2,048 points, the QSP-400B 1,024, the DSP-200B 512 and the DSP-100B 256. BACnet automation mitigated 1.4 billion tonnes of CO₂ since 1995 (Climate Control News, 18 June 2026).
Short answer
A gateway does not make two protocols interoperate; it maintains a translation table. Every register you expose becomes a BACnet object with a name, an engineering unit and a poll rate, and every point you add consumes capacity and polling bandwidth. Get it right and the integration disappears; get it wrong and every fault lands on the gateway.
Mistake 1: sizing by device count instead of point count
Most disappointing BMS integration projects are not protocol failures. They fail on arithmetic. A bill of materials lists 4 chillers, 30 VFDs and 120 fan coil groups. Someone counts boxes rather than objects, orders a gateway sized for "a few hundred devices", and then finds that each device exposes twenty to forty readable points.
Count objects, not boxes. Read-only status counts too: a value you only trend still occupies a point slot and a poll slot. The table below is illustrative arithmetic for a mid-size office building, not a vendor figure.
| Equipment | Devices | Points per device | Subtotal |
|---|---|---|---|
| Chillers | 4 | 40 | 160 |
| VFDs | 30 | 20 | 600 |
| Energy meters | 48 | 15 | 720 |
| Fan coil groups | 120 | 6 | 720 |
| Total | 202 | — | 2,200 |
A 202-device building carrying 2,200 points is normal, not exceptional. It is also well above the 512-point ceiling of the entry model and just past the 2,048-point top of the current MatyLink range, which is where the procurement conversation has to happen: split the job across two gateways, step up to the 2,048-point QSP-800B, or take a hard look at what really has to be a BACnet point.
| Specification | MatyLink DSP-200B | MatyLink QSP-400B | MatyLink QSP-800B |
|---|---|---|---|
| Point capacity | Up to 512 points | Up to 1,024 points | Up to 2,048 points |
| Modbus RS-485 master ports | 2 | 4 | 4 |
| Max. Modbus slaves per port | 32 | 32 | 32 |
| BACnet data link | BACnet/IP or BACnet MS/TP (one at a time) | BACnet/IP or BACnet MS/TP (one at a time) | BACnet/IP or BACnet MS/TP (one at a time) |
| Other ports | 1 * RJ45 Ethernet (BACnet/IP + web config), dedicated MS/TP RS-485 | 1 * RJ45 Ethernet (BACnet/IP + web config), dedicated MS/TP RS-485 | 1 * RJ45 Ethernet (BACnet/IP + web config), dedicated MS/TP RS-485 |
| Object mapping | AI / AO / AV / BI / BO / BV | AI / AO / AV / BI / BO / BV | AI / AO / AV / BI / BO / BV |
| Power and mounting | AC/DC 9–24 V, < 3 W, DIN rail | AC/DC 9–24 V, < 3 W, DIN rail | AC/DC 9–24 V, < 3 W, DIN rail |
| Operating range | −20 to +70 °C, 0–95% RH non-condensing | −20 to +70 °C, 0–95% RH non-condensing | −20 to +70 °C, 0–95% RH non-condensing |
All four models expose the same six object types, the same BACnet service set and the same browser configuration; the difference is point capacity and Modbus port count. The DSP-200B is the honest answer for a small plant room below 512 points. The QSP-400B adds two more RS-485 ports and 1,024 points, and the QSP-800B takes the same four ports to 2,048 points for buildings like the one above.
Mistake 2: ignoring polling budget
Point count is a static number; polling is a rate. A gateway that is comfortably sized on memory can still deliver stale data because the bus, not the point list, is the bottleneck.
How many Modbus transactions per second you actually have
Modbus RTU is a strict request-response protocol on a shared two-wire bus: one master, one conversation at a time. At 9,600 bps with 8N1 framing a character occupies roughly 1.04 ms, so a request plus a twenty-byte reply is about 30 ms of raw bus time before the device's own turnaround delay. Budget 50 ms per transaction as a planning assumption and one port gives you about 20 transactions per second.
Twenty per second sounds generous until you divide it by 2,200 points. Polling every point once every 30 seconds needs roughly 73 transactions per second on one port — over three times what 9,600 bps can carry. Raising the rate to 38,400 or 115,200 bps buys headroom, but only if every device supports it: one 9,600-bps meter sets the ceiling for the bus.
COV subscriptions vs polling
BACnet change-of-value (COV) subscriptions cut traffic on the BACnet side — the head-end subscribes once and the gateway reports changes as they happen. They do nothing for the Modbus side, because a Modbus RTU device does not push; the gateway must still read it. So use COV to relieve the BMS, and tier the Modbus poll rates by what a point does: alarms and safeties every few seconds, temperatures every 15 to 30 seconds, meter totals every five minutes.
Mistake 3: mapping raw registers straight to BACnet objects
The fastest way to make a gateway look broken is to map holding register 40001 straight into an analogue value with no scale, no unit and no name. The numbers arrive; they are simply not the ones the plant engineer expects.
Scaling, units and engineering values
A Modbus register is an integer; the meaning lives in the device manual. Tenths of a degree, hundredths of a bar, a signed 16-bit value, or a 32-bit float split across two registers in an unusual word order. Apply the scale and the offset in the gateway, not in the head-end graphic, so every consumer sees the same engineering value. A supply temperature of 7.4 °C should arrive as 7.4 °C with °C as its unit, not as the integer 74.
Four traps catch most projects: signed versus unsigned, 32-bit values spanning two registers, byte and word order on floats, and status words where each bit is really a separate binary point. Function codes matter as well — 03H holding registers and 04H input registers are not interchangeable, and a mapping configured to read 03H from a device that only answers 04H will time out quietly rather than fail loudly.
The point-naming schedule your client will accept
Agree the naming convention before mapping, not after. A pattern such as site-plant-device-function — BLD1-CH01-SUPPLYTEMP — survives head-end graphics, trend exports and the next integrator. Keep the register address, function code, data type, scale, unit and description in the schedule itself: that table is the document the client actually keeps.
Mistake 4: one RS-485 segment for everything (and why port count matters)
The most common hardware mistake is ordering the two-port gateway because "it is only one RS-485 bus", then discovering that the chillers sit on one riser and the meters on another, at different baud rates, with no practical way to join them.
RS-485 ports are not redundancy; they are independent conversations. The QSP-400B and QSP-800B carry four Modbus RTU ports, so a chiller segment, a metering segment, a boiler room and a lift group can run in parallel, each at its own baud rate, each with its own unit-ID space. The two-port DSP-200B and DSP-100B cover a single plant room. Unit IDs only have to be unique within a segment: address 5 on both ports is legal, address 5 twice on one port is a collision that shows up as intermittent timeouts nobody can reproduce.
Modbus unit addressing stops at 247, but the electrical limit usually arrives first — the classic ceiling is 32 unit loads per segment without a repeater. Long risers, mixed cable types and devices with weak bias resistors produce reflections that look exactly like a gateway fault, so terminate and bias the segment before blaming the mapping.
Mistake 5: treating the gateway as a cybersecurity boundary
A gateway sits between two networks, which makes it tempting to treat it as the place where security happens. It is not: it is a translator with a Modbus port on one side and an IP stack on the other, and the Modbus side has no authentication at all — any device that can answer a read gets read.
Segmentation, not translation, is the control. Put building controls on their own VLAN, firewall the paths that need to exist, and treat every gateway as an untrusted endpoint that needs a known firmware version, a changed default credential and a documented admin path.
What BACnet/SC actually solves (Plugfest 2026 findings)
BACnet/SC adds encrypted, certificate-based, device-to-device transport for BACnet. At Plugfest 2026 in Prague, 28 companies and 28 teams tested BACnet/IP and MS/TP as well as a dedicated BACnet/SC network for certificate handling and secure device-to-device connections (BIG-EU, 10–12 June 2026). The MatyLink DSP-200B, QSP-400B and QSP-800B support BACnet/IP or BACnet MS/TP on the BACnet side, but none of them terminates BACnet/SC. If a tender mandates BACnet/SC, ask how the gateway fits that topology rather than assuming it terminates SC.
Mistake 6: no fallback when the gateway dies
When the gateway stops, the plant does not. Chillers keep running, VFDs keep following their last command, and the head-end simply goes blind — which is worse than a visible failure, because nobody notices until a tenant complains.
Design the failure explicitly: alarm on communication loss at the head-end, keep schedules and setpoints in the controllers or the BMS rather than in the gateway, confirm that outputs fail to a safe state, and hold one programmed spare on site. A gateway is a single point of failure for visibility, and where the BMS also writes setpoints, for control as well. Where the BACnet side is a controller rather than a gateway, an MVC-WMB-1866BA keeps local logic in the field device, with two MS/TP and two Modbus RTU ports of its own.
Mistake 7: no documentation handover
Six months after handover the integrator has moved on, the laptop with the mapping file is gone, and the point reading zero cannot be traced to a register.
The handover pack should contain the point schedule, the register map with function codes and addresses, device instance numbers, IP addresses, MS/TP MAC addresses, baud and parity settings, firmware versions, and a note on where MQTT sits if the site uses it — in the management software layer (MatyContrE), not in the gateway. Screenshots of the mapping help; the editable source file is what gets remembered. Two application scenarios worth reading before you write that pack are the office building BMS integration and DDC control scenario and the airport terminal HVAC monitoring and control scenario; both are scenario write-ups, not client case studies with measured savings.
The compliance backdrop: EPBD interoperability and the BACnet carbon case
Two European rules turn all of the above from good practice into a documented requirement.
Article 13(10)(c) of the recast Energy Performance of Buildings Directive requires building automation and control systems to be interoperable across proprietary technologies. Article 13(9) has required a BACS in non-residential buildings above 290 kW since 31 December 2024, extending to systems above 70 kW by 31 December 2029, and the general transposition deadline fell on 29 May 2026 (eu.bac, 29 May 2026). A gateway is how a mixed-vendor plant room meets that test without replacing the plant.
The carbon argument is now quantified: research by the University of New Hampshire for ASHRAE found that BACnet-enabled building automation mitigated 1.4 billion tonnes of CO₂ since 1995 — equivalent to 300 million cars for a year — with 2.06 billion tonnes projected avoided by 2030 (Climate Control News, 18 June 2026).
Those figures are a reason to keep the integration honest, not a sales claim. From 27 September 2026 the EU EmpCo Directive requires environmental claims to be substantiated (BIG-EU, August 2026). Vendor-cited results, such as the AI-over-BACnet rollout that reports 60 Porsche Holding sites with 55 online and an option to 600, with savings of around 30% (BIG-EU citing OQDO, August 2026), are claims to verify against your own metering, not benchmarks to quote.
Frequently asked questions
What does a BACnet to Modbus gateway do?
It bi-directionally maps Modbus RTU registers to BACnet objects so that one BMS can supervise equipment from different vendors. Reads become analogue and binary values; writes become coil and register commands.
How many points do I need?
Count every readable object, not every device. A chiller exposing 40 registers is 40 points before alarms and setpoints are added, so a plant room with four chillers, thirty VFDs and fifty meters fills a small gateway quickly. Step up at roughly 2,048 points.
Does point count include read-only status?
Yes. Status, alarms and setpoints all consume point capacity and polling bandwidth, whether or not the BMS ever writes to them.
BACnet/IP or MS/TP on the gateway uplink?
IP when the head-end is IP-native and Ethernet reaches the plant room. MS/TP when you are extending an existing field bus, subject to segment load, baud rate and MAC addressing — a BACnet MS/TP to Modbus RTU converter is the same gateway with a different uplink.
Will a gateway fix a badly behaved Modbus device?
No. Fix timeouts, register gaps and unit-ID collisions at the device first; a gateway forwards bad data faithfully and with great punctuality.
Does a gateway make my site cybersecure?
No. Segmentation, firewalls and BACnet/SC do that. A gateway is a protocol translator, not a security boundary, and the Modbus side has no authentication to offer.
Sources
- Climate Control News — BACnet and building automation climate impact study, 18 June 2026
- eu.bac — EPBD transposition deadline and Article 13 BACS requirements, 29 May 2026
- BIG-EU / BACnet Journal — Plugfest 2026, Prague, 10–12 June 2026 (reported August 2026)
- BIG-EU — AI over BACnet and EmpCo claims rules, August 2026
- Matinal — MatyLink DSP-200B specification (512 points, 2 RS-485 ports), accessed 28 October 2026
- Matinal — MatyLink QSP-400B specification (1,024 points, 4 RS-485 ports), accessed 28 October 2026