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

Saia S-Bus⇄WBoxgateway⇄BACnetOne WBox gateway · native conversion · no PC

The protocols

Saia S-Bus

Ether S-Bus is the native protocol of Saia-Burgess PCD controllers (SBC), widespread in Swiss buildings — reading and writing registers, flags, inputs and outputs.

Saia S-Bus driver →

BACnet

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

BACnet driver →

Typical use case

A site runs on Saia PCD controllers — boiler room, air handling, years of proven PG5 programs — and a new BACnet BMS arrives. Rather than reprogramming or replacing the PCDs, the WBox exposes their registers and flags as BACnet objects: the head-end supervises the legacy plant like native BACnet equipment, and setpoints written in the BMS land back in the controllers.

Example deployment

Typical scenario Saia PCD controllers in a BACnet BMS A fleet of Saia PCD controllers has run heating and ventilation for years. Instead of replacing them, the WBox reads registers and flags over Ether S-Bus (importing the address lists straight from PG5) and exposes them as BACnet objects: the new supervision sees the PCDs as native BACnet devices. Technical documentation →

How the WBox bridges Saia S-Bus and BACnet

The Saia S-Bus driver talks Ether-S-Bus over UDP (port 5050) to each PCD station — addresses 0 to 255 — reading and writing registers (R), flags (F), timers and counters. The BACnet driver maps them to Analog Values and Binary Values, with scaling applied on the gateway (a register holding tenths of a degree becomes a clean °C value). Both drivers run on the same WBox; a BACnet write updates the PCD register within the polling cycle.

Example mapping

A boiler-room example:

  • Saia station 12, register R 100 (flow temperature, ×0.1 °C) → BACnet Analog Value 10 (°C)
  • Saia flag F 205 (pump running) → BACnet Binary Value 4
  • BACnet Analog Value 12 (setpoint) → Saia R 120

Capacity & limits

  • Saia S-Bus — Ether S-Bus runs over UDP/IP — one connection per Saia PCD (station 0–255), reading and writing registers, flags, inputs and outputs; address lists import directly from PG5.
  • BACnet — BACnet/IP scales to large object counts; BACnet MS/TP carries up to 127 master nodes per segment.

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 connect Saia S-Bus and BACnet?

Saia S-Bus is the Saia PCD controller protocol (Ether S-Bus) and BACnet is the building-management (BMS) protocol. A single WBox gateway runs the Saia S-Bus and BACnet drivers, speaks both protocols at once and maps the data points between them — no PC, no middleware, no cloud dependency.

Is the Saia S-Bus ⇄ BACnet bridge bidirectional?

Yes. The WBox reads and writes on both sides: a value or command on the Saia S-Bus side propagates to BACnet, and vice-versa.

Do I need a PC, a PLC or proprietary hardware?

No. The Saia S-Bus and BACnet drivers are licence-activated on one WBox — no gateway PC, no intermediate PLC and no proprietary hardware.

Which WBox model do I need?

Any WBox with the Saia S-Bus and BACnet driver licences. The online configurator recommends the right model from your interfaces and point count.

What you need

One WBox gateway with these two driver licences:

Saia S-Bus Saia S-Bus Driver licence 100.00 CHF BACnet BACnet Driver licence 100.00 CHF

Route Saia S-Bus BACnet 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