How to bring a Systemair air handling unit with the Access controller onto a BMS over BACnet/IP: switching BACnet/IP on (it leaves the factory off), the device ID that Systemair gives no default for, the 1201-object EDE list for Access 5.5, the temperatures that arrive without a unit, the BMS watchdog — and which setpoint the unit actually uses. With a free BACManager workspace.
Sources: Systemair “Access 5.x Modbus variables and BACnet objects” (communication document 5.5-1-01 build 411) and the Access communication manual 153831-A011
The Access controller talks BACnet/IP on its own TCP/IP port. Access 4.0-1-05 brought BACnet as an application specific controller (B-ASC). From 4.3-1-00 it is an advanced application controller (B-AAC). Systemair's communication manual describes BACnet/IP only, with nothing on MS/TP.
Press the “i” button on the Access home page. The object lists for Access 4.x and 5.x are different, so download the zip that matches your unit. Systemair's download page also says that an upgrade to 5.5 from an earlier 5.x is not available yet; support is planned for the second half of 2026.
An EDE object list (1201 objects for 5.5-1-01) with state texts and unit codes, and a Modbus signal list that gives defaults. We found no PICS: BIBBs, segmentation, max APDU and protocol revision are not published. Older Systemair units with a Corrigo E controller are not covered here.
You change these in the controller's web interface, or through the NaviPad, which opens the same pages.
| Setting | On delivery | Set to |
|---|---|---|
| BACnet/IP | No | Yes. BACnet is switched off until you do this |
| BACnet device ID | not given | A device instance that no other device in the building uses. Systemair says the ID has to be unique but does not give a default |
| BACnet device name | not given | A name the BMS will list, e.g. the AHU tag |
| BACnet/IP UDP port number | 47808 | Leave it at 47808 unless the site uses a different port |
| BBMD address | — | Only when the BMS is on another IP subnet. Enter it as host:port, e.g. 10.100.50.99:47808, or name:47808 if DNS is set up |
| Communication → Ethernet | DHCP or static (not stated) | A static IP, mask, gateway and DNS for a BMS network. With no DHCP server the controller falls back to an Auto-IP address, 169.254.x.y |
| System settings → Communication → BMS watchdog | BMS protocol None, 60 s | BACnet, with a timeout of 10–3600 s. Use it when the BMS writes values that the unit depends on |
The EDE file that Systemair ships shows the instance 114112 in its device column and names the Device object “Access”. Treat that as the instance of the controller the file was exported from, not as a factory value: read the ID in the web interface or with a Discover. If the BMS reaches the unit through a router, the BBMD entry lets the controller be found from the other subnet. BACManager can also register itself as a foreign device with the site's BBMD.
Systemair's object list does not say which BACnet objects can be written: the EDE “settable” column is N for all 1201 rows. In the Modbus list the same signals are split into settings (S_ prefix: holding registers and coils) and actual values (A_: input registers). The table uses that split. Check every write on the unit.
| Object | Object name | Default | What it does |
|---|---|---|---|
| MV12 | AirUnitAutoMode | — | Running mode: 1 OFF, 2 Manual, 3 AUTO (time schedule), 4 Low speed, 5 Normal speed, 6 High speed. It is in the EDE but not in the Modbus list |
| AV39 | SupplySetpoint | 18 °C | The supply air setpoint for constant supply air temperature control |
| MV14 | VentControl | 0 in the Modbus list = Const.supply air | Selects the temperature control mode (nine choices: outdoor-compensated, cascade room, extract…). The mode decides which setpoint applies |
| MV31 | ExternalControl | No External control | Extended run at low/normal/high speed, external stop, free cooling, recirculation |
| MV32 | AirUnitServiceStop | — | No/Yes. Systemair describes it as a stop “with No 1 prio” |
| AV47–49 / AV50–52 | SAF… / EAFLow/Normal/HighSpeedPressure | 250 / 500 / 750 Pa | Duct pressure setpoints for each fan speed |
| AV170 | CO2Setpoint | 1000 | CO2 setpoint, ppm |
| AV466 | BMS_OutDoorTemp | 0 °C | Outdoor temperature written by the BMS. It is used only when the outdoor-temperature input is set to Device = BMS |
| BV8 / BV6 | AlaAcknowAll / FilterAlarmReset | 0 | Acknowledge all alarms; reset the filter alarm counter |
SupplySetpoint (AV39) only applies in constant supply air mode. In the other modes the unit works out its own setpoint, from outdoor compensation, a room or extract cascade, or a speed offset. Watch SupplyPID_SetP (AV273), the setpoint actually in use, and not only the one you wrote.
Systemair does not say whether these objects have a priority array, or which priority a BMS should write at. BACManager writes at priority 8 unless you choose another. Read the value back after writing, and see the priority array explained for how to hand a point back.
Once the BMS watchdog is set to BACnet, a quiet period longer than the timeout makes every value written by the BMS invalid and raises a watchdog alarm (class C, no action, by default). The BMS outdoor temperature gets a sensor-error alarm too. BACManager's per-tag “Refresh (s)” can rewrite AV466 regularly.
A new unit does not answer Who-Is until BACnet/IP is set to Yes, however good the network is. It is the first thing to check when Discover finds nothing.
In the EDE, temperatures, pressures and air flows have unit code 95, “no units”. The number follows the temperature, flow and pressure units chosen in the controller's preferences, so the BMS has to be told whether 18 means °C or °F, and whether the flow is in m³/h or l/s.
The 4.x manual builds instances from the Modbus address (10XXX/20XXX binary, 30XXX/40XXX analogue and multistate). The 5.5 EDE uses plain instances (AI3 is supply air). A BMS mapped for one version shows wrong values on the other.
Object names as in Systemair's Access 5.5-1-01 EDE. S = a setting in Systemair's Modbus list (writable over Modbus; BACnet write access is not stated), R = an actual value. Multistate values count from 1 in the order of Systemair's state texts.
| Object | Object name | Access | What it is |
|---|---|---|---|
| MV12 / MV32 / MV31 | AirUnitAutoMode / AirUnitServiceStop / ExternalControl | S | Running mode, service stop, external control (see above) |
| MV15 | UnitMode | R | Unit run mode: Stop, Starting up, Low/Normal/High speed run, support heating/cooling, CO2, free cooling, fire, smoke, de-icing… (16 states) |
| MV16 | UnitModeControl | R | What triggered the current run mode: time schedule, manual run, digital input, alarm, external control, service stop… |
| MV69 / MV70 | SAFSpeed / EAFSpeed | R | Off, Low, Normal, High speed, Manual setpoint, Manual output |
| AI1 / AI2 / AI3 | AI_OutDoorTemp / AI_IntakeAirTemp / AI_SupplyAirTemp | R | Outdoor, intake and supply air temperature |
| AI5 / AI4 | AI_ExtractAirTemp / AI_ExhaustAirTemp | R | Extract (from the rooms) and exhaust (to outdoors) |
| AI6–9 / AI20 / AI21 | AI_RoomTemp1… / AI_CO2 / AI_HumidityRoom | R | Room temperatures, CO2 in ppm, room humidity |
| AI10 / AI11, AI12 / AI13 | AI_SAFPressure / AI_EAFPressure, AI_SAFFlow / AI_EAFFlow | R | Fan duct pressure and air flow, supply and extract |
| AI17 | AI_FrostprotTemp1 | R | Frost protection temperature 1 (the heater's water) |
| AI34 / AI35 | AI_FilterGuard1 / AI_FilterGuard2 | R | Supply and extract air filter pressure |
| AV39 / AV273 | SupplySetpoint / SupplyPID_SetP | S / R | Setpoint written; setpoint actually used |
| AV274 / AV275 | SAFPID_SetP / EAFPID_SetP | R | Fan setpoints actually used |
| AV427 | Efficiency | R | Heat exchanger efficiency, % |
| AV467 / AV468 / AV469 | SequenceA / SequenceB / SequenceC | R | Sequence outputs, % (Systemair's feedback inputs name A heating, B exchanger, C cooling) |
| AO1–10 / AO13 / AO14 | AO_SequenceA… / AO_SAF / AO_EAF | R | The physical Y outputs and the fan control signals |
| AV283 / AV11 / AV12 | SFP / SAFRunTime / EAFRunTime | R | Specific fan power; fan running hours |
| AV287 / AV288 / AV286 | EnergyFanPwr / EnergyHeaterPwr / EnergyExchangerPwr | R | Fans, heater, recovered by the exchanger. The EDE gives kWh as the unit, the Modbus list calls them actual power: check on your unit |
| BI1 / BI2 | DI_SAF / DI_EAF | R | Fan feedback (motor protection / run indication) |
| BV9 / BV10 / BV11 / BV12 | SumAlarm / SumAlarmA / SumAlarmB / SumAlarmC | R | Any alarm; any A, B or C alarm |
| PIV5–7 | AlarmACount / AlarmBCount / AlarmCCount | R | Number of A, B and C alarms |
| SCH2 / SCH3–6 / CAL1 | TC_FanSpeed / TC_Extra1–4 / Calendar | — | Time schedules and calendar; BACManager has a schedule and calendar editor |
| TL1–98 | TL_SupplyAirTemp, TL_SupplyAirTemp_Avg2min… | R | 96 Trend Logs, many with a 2-minute average twin; BACManager reads Trend Logs |
The full list also holds heat pump, humidity, damper and fan fault bitmask objects, digital inputs and outputs, and the alarm limits. The EDE lists notification classes 1–3 (alarm classes A, B and C) and 4 (event points), and every analog input refers to class 2, so the unit reports some alarms itself. Systemair does not document how. BACManager's device alarms show whatever the unit sends. The EDE marks COV support on the analog objects.
One dashboard page for a Systemair unit with heat recovery, a heater and a cooler: the AHU with intake air, supply air, air flow and coil valves, both fans with pressure and speed, outdoor, extract and exhaust air, filter pressure, exchanger efficiency, SFP, a trend, and the running mode, supply setpoint, service stop and alarm acknowledge as controls.
On the BACnet tab open BACnet/IP on the PC's network card and press Discover. The unit appears with the device ID set in its web interface. If it is on another subnet, register with the site's BBMD first.
Workspace → Open. The file reads device 20201. If your unit has another instance, BACManager asks which discovered device takes its place and moves every point over.
BACManager starts reading the unit by itself. On the Dashboard press Run to use the controls. They write only in Run mode, and only once the unit has answered. Check that SupplyPID_SetP follows what you wrote.
| What you see | Why | What to do |
|---|---|---|
| Discover finds nothing | BACnet/IP is still No, as delivered | Configuration → Communication → BACnet: BACnet/IP = Yes |
| Found on the same switch, not from the BMS subnet | Who-Is broadcasts do not cross IP routers | Enter the BBMD address in the unit, or register the client as a foreign device |
| Two units answer with the same instance | The device ID was copied or never set | Set a unique BACnet device ID on every unit |
| Temperatures look wrong or have no unit | Unit code 95; values follow the controller's unit preference | Check the preference setting and set the unit in the BMS |
| Object names do not match the list | 4.x and 5.x object lists differ | Check the version with the “i” button; use the matching zip |
| SupplySetpoint written, supply air does not follow | VentControl is not constant supply air | Read MV14 and SupplyPID_SetP (AV273) |
| Unit stays stopped in AUTO | Service stop, external stop, or the schedule says off | Read UnitModeControl (MV16) and AirUnitServiceStop (MV32) |
| Watchdog alarm; BMS values ignored | Nothing received within the watchdog timeout | Poll more often than the timeout, or set a longer timeout |
| Sensor error on BMS outdoor temperature | AV466 is not updated while the watchdog supervises it | Rewrite it regularly (Refresh (s) on the tag) |
Systemair: “Access 5.x Modbus variables and BACnet objects”, communication document 5.5-1-01 build 411 (BACnet EDE, object types, state texts, engineering units and the Access5ModbusSignals list), and Communication manual, Access software from 4.0-1-04, document 153831-A011, chapter 2 (BACnet, watchdog, BMS outdoor temperature, Ethernet). Get them from Systemair's Access software & tools download page and use the files for your unit's software version. Which BACnet objects accept writes, the command priority and the default device ID are not stated by Systemair. The S/R split is taken from the Modbus list and is our reading. Systemair, Geniox, Topvex and Access are Systemair names; BACManager is not affiliated with Systemair. The pictures on this page are from BACManager connected to a simulated unit built from the published object list.
Download the free trial, discover the unit and open the Access workspace — every point by name, setpoint and running mode on the page. No credit card.
Windows 10/11 · $149 one-time
We use Google Analytics cookies to see how the site is used. You can accept or decline — declining keeps analytics off.