device library

Systemair Topvex SX/TX/SR/TR air handling unit

Register map(s) for this device, with a note of how far each has been checked. Addresses are 0-based, as on the wire. Scale and byte order are confirmed only at the hardware-verified rung.

structure-verified

Decode path is structurally sound (addresses, widths, finite values). Does NOT prove word order or scaling.

pointaddress (0-based)typescaleunit
Vpac1.TimeExtension1U161
TimePro.TimeGroupUnit1U161
Vpac1. UnitType1U161
StdObjs1.Ai1_SupplyTemp_Output1I1610
Vpac1.FilterAlarmReset2U161
QDig.DI12U161
Vpac1.Unitmode2U161
StdObjs1.Ai2_ExhaustAirTemp_Output2I1610
StdObjs1.FireAlarmActive3U161
QDig.DI23U161
Vpac1.Regulation3U161
StdObjs1.Ai3_FrostProtectionTemp_Output3I1610
StdObjs1.AktiveFanFire4U161
QDig.DI34U161
Vpac1.UnitOffLow4U161
StdObjs1.Ai4_OutDoorTemp_Output4I1610
Vpac1.NightCool_Enable5U161
QDig.DI45U161
Vpac1.FanSpeedChoice5U161
QAnaIn.AI15I1610
QDig.DI56U161
Vpac1.FilterAlarmModBus6U161
QAnaIn.AI26I1610
QDig.DQ17U161
Vpac1.SupplyTempModBus7U161°C
QAnaIn.AI37I1610
QDig.DQ28U161
Vpac1.Cooling8U161
QAnaIn.AI48I1610
QDig.DQ39U161
Vpac1.CoolRecycling9U161
StdObjs1.Ao1_Heating_OutPut9I1610
QDig.DQ410U161
Vpac1.HeatBatteryType10U161
StdObjs1.Ao2_Cooling_OutPut10I1610
QDig.DQ511U161
StdObjs1.Do4_Exchanger_Select11U161
StdObjs1.Ao3_RotatingSpeed_OutPut11I1610%
StdObjs1.Ao1_Heating_Select12U161
QAnaOut.AQ112I1610V
StdObjs1.Ao2_Cooling_Select13U161
QAnaOut.AQ213I1610V
StdObjs1. Ao3_RotatingSpeed_Select14U161
QAnaOut.AQ314I1610V
Vpac1.Ao1_ManInput15I1610V
QAnaOut.AQ415I1610V
Vpac1.Ao2_ManInput16I1610V
QAnaOut.AQ516I1610V
Vpac1.Ao3_ManInput17I1610V
Vpac1.FanSpeed_HighsetP18I161%
Vpac1.FanSpeed_MediumSetP19I161%
Vpac1.FanSpeed_LowsetP20I161%
Vpac1.SetPoint_M2021I161
Vpac1.SetPoint_M1522I161
Vpac1.MinSupplyTemp23I161
Vpac1.MaxSupplyTemp24I161
Vpac1.Unit_Pgain25I161
Vpac1.Unit_Itime26I161
Vpac1.Unit_Cascade_PGain27I161
Vpac1.Unit_cascade_ITime28I161
Vpac1.TimeExtensionSetPoint29I161
Not used30I161
Vpac1.FanSpeedChoice_Forced31U161
Vpac1.NightCool_OutdoorDay32I161
Vpac1.NightCool_OutdoorHighNight33I161
Vpac1.NightCool_OutdoorLowNight34I161
Vpac1.NightCool_RoomLimit35I161
StdObjs1.Ao4_RotatingSpeedEAF_Select36U161
StdObjs1.Ao5_Bypass_Select37U161
AlaPts.FilterAlarm50U161
TimeDp.Posts(0).T150I16100h
AlaData.FilterAlarm_Status50U161
AlaPts.AlarmFanMotor51U161
TimeDp.Posts(0).T251I16100m
AlaData.AlarmFanMotor_Status51U161
AlaPts.Overheat52U161
TimeDp.Posts(0).T352I16100
AlaData.Overheat_Status52U161
AlaPts.ExchangerRotatingAlarm53U161
TimeDp.Posts(0).T453I16100
AlaData.ExchangerRotatingAlarm_Status53U161
AlaPts.AlarmFrostProt54U161
TimeDp.Posts(1).T154I16100
AlaData.AlarmFrostProt_Status54U161
AlaPts.FireAlarm55U161
TimeDp.Posts(1).T255I16100
AlaData.FireAlarm_Status55U161
Not used56U161
TimeDp.Posts(1).T356I16100
NOT USED56U161
AlaPts.SensorAlarm_SupplyTemp57U161
TimeDp.Posts(1).T457I16100
AlaData.SensorAlarm_SupplyTemp _Status57U161
AlaPts.SensorAlarm_ExhaustTemp58U161
TimeDp.Posts(2).T158I16100
AlaData.SensorAlarm_ExhaustTemp_Status58U161
AlaPts.SensorAlarm_FrostTemp59U161
TimeDp.Posts(2).T259I16100
AlaData.SensorAlarm_FrostTemp_Status59U161
AlaPts.SensorAlarm_OutDoorTemp60U161
TimeDp.Posts(2).T360I16100
AlaData.SensorAlarm_OutDoorTemp_Status60U161
AlaPts.InternalBatteryError61U161
TimeDp.Posts(2).T461I16100
AlaData.InternalBatteryError_Status61U161
TimeDp.Posts(3).T162I16100
TimeDp.Posts(3).T263I16100
TimeDp.Posts(3).T364I16100
TimeDp.Posts(3).T465I16100
TimeDp.Posts(4).T166U160.01
TimeDp.Posts(4).T267U160.01
TimeDp.Posts(4).T368U160.01
TimeDp.Posts(4).T469U160.01
TimeDp.Posts(5).T170U160.01
TimeDp.Posts(5).T271U160.01
TimeDp.Posts(5).T372U160.01
TimeDp.Posts(5).T473U160.01
TimeDp.Posts(6).T174U160.01
TimeDp.Posts(6).T275U160.01
TimeDp.Posts(6).T376U160.01
TimeDp.Posts(6).T477U160.01
Alarms.AlaAcknow150U161
Alarms.AlaBlock151U161
Alarms.AlaUnBlock152U161

link settings as documented (unverified): baud 9600; FC 01,02,03,04,05,06,15,16; The modbus master must wait for a minimum of 3.5 charactertimes (4ms at 9600 bps) between two messages. When the modbus master communicate with more than one controller on the same communication line (RS485), the modbus master must wait for a minimum of 14 charactertimes (16ms at 9600bps) between the answer and the first question for the next controller.

bench facts as documented (unverified)
wiring notesRS485 communication line
max registers/read47
inter-frame delay4 ms
broadcastnot supported
protocol notesIn the controller there is a limit of 10 fast communications in every half minute, the other communications will have a delayed answer of approximately 1 second.
identification notesThe address of the controller is always as default PLA=254 and ELA=30.
doc revision11-12-05 A002
field reports — community-sourced, unverified (checked 2026-06-11)
  • confirmed: comms defaults (baud rate 9600, function codes 1, 2, 3, 4, 5, 6, 15, 16) — confirmed by Systemair Topvex Modbus Exoline Variables document (11-12-05 A002) [1.3.1]
  • confirmed: inter-frame delay and communication limits (3.5 charactertimes / 4ms at 9600 bps, 14 charactertimes / 16ms between controllers) — confirmed by Systemair Topvex Modbus Exoline Variables document (11-12-05 A002)
  • confirmed: default PLA=254 and ELA=30 — confirmed by Systemair Topvex Modbus Exoline Variables document (11-12-05 A002)
  • confirmed: limit of 10 fast communications per half minute (others delayed by ~1s) — confirmed by Systemair Topvex Modbus Exoline Variables document (11-12-05 A002)
  • confirmed: register map addresses (e.g., StdObjs1.Ai1_SupplyTemp_Output at address 1, Vpac1.UnitType at address 1, AlaData.FilterAlarm_Status at address 50) — confirmed by Systemair Topvex Modbus Exoline Variables document (11-12-05 A002)

The trust ladder

Each rung states what it proved and what it did not. Gray until proven; green is earned by hardware only.

Device not here? Upload its manual and get a checked map back. It's free.

Want it confirmed against your own device? Order hardware verification. If it doesn't check out, you don't pay.

Building on a lot of devices? License the library — machine-readable maps, the firmware matrix, and API access.