Need to connect BACnet and OPC UA? The Weble WBox routes BACnet OPC UA natively: one gateway speaks both protocols and maps data points in real time — no PC, no middleware, no cloud dependency.

BACnet⇄WBoxgateway⇄OPC UAOne WBox gateway · native conversion · no PC

The protocols

BACnet

BACnet (BACnet/IP, MS/TP) is the standard for building management systems and HVAC supervision.

BACnet driver →

OPC UA

OPC UA is the secure, platform-independent client/server standard for Industry 4.0 data exchange.

OPC UA driver →

Typical use case

When building BACnet data has to reach an OPC UA supervision or IT analytics platform — typically where building management and industrial/IT systems converge — the WBox maps BACnet objects into an OPC UA address space. The BMS keeps running on BACnet while IT consumes a clean, browsable model of the same points, with the security and subscriptions OPC UA clients expect. No duplicate database, no manual tag list to maintain on both sides.

In the field

Weble customers run this routing in production:

Customer story Paul Vaucher SA Routes BACnet — alongside KNX and DALI — up to a central OPC UA supervision on 50 WBox S485 KNX gateways, for the Lombard Odier campus in Geneva. Read the case →

How the WBox bridges BACnet and OPC UA

Activate the BACnet and OPC UA drivers. BACnet objects (Analog and Binary) become OPC UA nodes; COV subscriptions drive node updates, so changes propagate event-by-event without polling. OPC UA writes are applied to the BACnet present-value. A JavaScript step can structure the node tree, attach engineering units and descriptions, or expose only the subset of objects IT actually needs — keeping the OPC UA model tidy and the BACnet side untouched.

Example mapping

A worked example, all on one gateway:

  • BACnet Analog Input 20 zone temperature → OPC UA node ns=3;s=Building.Zone4.Temp (Float)
  • BACnet Binary Input 3 occupancy → OPC UA ns=3;s=Building.Zone4.Occupied (Boolean)
  • OPC UA write ns=3;s=Building.Zone4.Setpoint → BACnet Analog Value 8 setpoint

Capacity & limits

  • BACnet — BACnet/IP scales to large object counts; BACnet MS/TP carries up to 127 master nodes per segment.
  • OPC UA — OPC UA imposes no node limit — the address space scales with the server.

On the WBox, a driver licence enables the whole protocol — there is no artificial per-point tier to unlock. Capacity scales with the gateway model, from the compact S103 to the E413: you are bounded by the field bus, not by your licence.

Frequently asked questions

How do I expose BACnet data over OPC UA?

A WBox with the BACnet and OPC UA drivers maps BACnet objects (Analog and Binary) to OPC UA nodes; the BMS keeps running on BACnet while IT consumes a clean, browsable OPC UA model of the same points.

Is the BACnet ⇄ OPC UA bridge bidirectional?

Yes. OPC UA writes are applied to the BACnet present-value, and BACnet COV subscriptions drive OPC UA node updates event-by-event — no polling.

Does it read BACnet/IP and BACnet MS/TP?

Yes. The WBox reads BACnet/IP and, with an RS-485 trunk, BACnet MS/TP, and surfaces both on the OPC UA side. See also the BACnet/IP to BACnet MS/TP page for pure BACnet routing.

Do I need a duplicate database or tag list?

No. Both drivers run on one WBox; there is no duplicate database and no tag list to maintain on both sides. A JavaScript step can structure the node tree and attach units and descriptions.

What you need

One WBox gateway with these two driver licences:

BACnet BACnet Driver licence 100.00 CHF OPC UA OPC UA Driver licence 100.00 CHF

Route BACnet OPC UA on your project

Find the right WBox gateway for your installation, or get in touch to validate your case.

Configure my gateway

Related routes

← All routes