Swegon GOLD RX (version F)

Swegon · air handling unit with rotary heat exchanger, BACnet/IP and Modbus TCP · GOLD RX, wersja F

Illustrative drawing to scale from the vendor datasheet, two views (size 005)

what it is

An air handling unit with a rotary heat exchanger (the letter RX in the name), controlled by the IQlogic system. Size 005 has a 1499 × 825 × 920 mm casing (length × width × height, excluding the connection box on the roof), weighs 234–278 kg and has Ø315 mm duct connections; airflow up to 2340 m³/h (manufacturer datasheet, version F).

The controller exposes several paths at once:

BACnet/IP on UDP port 47808,
Modbus TCP on port 502,
a web panel over HTTP on port 80, unencrypted,
its own Wi-Fi access point (SSID GOLD) for operation from a phone,
links to the manufacturer's cloud services, disabled with separate switches in the panel.

There is no SNMP agent. In BACnet the unit identifies itself as GOLD ver. E/F, vendor ID 300, protocol revision 14. The version and size are given in the web page header, for example GOLD RX Version F 05/05.

what we read from it

Discovery without login. A BACnet Who-Is request returns the vendor, model and firmware version of every unit in the segment — without any credentials.

Full point list. On IQlogic firmware 2.46 the unit exposes 2109 objects with name, value and unit (reading of October 10, 2026). The most important of them:

operating state — a single object with 41 states described in text,
summary alarms A and B — instead of several hundred alarm group objects,
temperatures: outdoor, supply and extract,
fans: speed, airflow in m³/h, control voltage and energy consumed,
filters: pressure drop across the supply and extract filters in Pa,
state of its own Wi-Fi access point — whether the radio is on.

Comparing the point list with a reading taken after a firmware update shows whether the manufacturer added, removed or renamed points.

measured pitfalls

The unit is silent outside its own subnet. From the factory it has no default gateway, so it responds only within its own layer 2 network. The panel works locally, while a request from another subnet vanishes without a trace.
The energy counter periodically "drops" by about 1000 kWh. The counters are split into two objects: whole MWh and the remainder in kWh. The value is MWh × 1000 + kWh, and a missing component means a missing sum.
Zero is not always a measurement. Humidity, CO₂ and auxiliary function objects exist in every unit, including where those functions are absent, and then they show 0.
Some object names end with a space, for example Outdoor temperature . Comparing names without trimming the space does not match.
The state Communication … stop means a stop by the supervisory system (BMS), not by the unit's own schedule. In that case, look for the cause of the stop in the supervisory system.
Some object properties do not exist — the read ends with an unknown-property error. The inventory must continue, not abort on the first refusal.

writing and access

Changing setpoints via building automation protocols takes effect immediately, and on the other side is the building's ventilation. That is why we only read from the unit, without any write operation, and who may communicate with it is decided by segregating the building automation network.

The web panel has two access levels: user and installer.

what we cannot read

Anything over SNMP — the unit has no agent.
Humidity and CO₂ where the unit does not have those functions — the objects exist, the measurement does not.
The cause of an alarm from the summary alarms alone — A and B say that an alarm exists; its type has to be read from the alarm group objects.

full parameter list

A full parameter list for this model is not here yet — the ones described above are those we have read and verified. A missing list does not mean the device exposes nothing more.