Easy BACnet- Home
- BACnet points lists
- Thermal Solutions
- EVA / EVO boiler - RWF55 controller (ProtoNode)
Boiler operating controller (RWF55) via ProtoNode gateway · BACnet points list
Thermal Solutions EVA / EVO boiler - RWF55 controller (ProtoNode) BACnet points list
Updated 28 October 2026
Thermal Solutions EVA/EVAW/EVO/EVOW boilers with an RWF55 controller are read through a ProtoNode FPC-N34 gateway that polls the RWF55 over Modbus RTU and serves it on BACnet IP or BACnet MS/TP. The profile has 10 objects: three analog inputs, the active setpoint, writable Setpoint 1 and 2, actuator position and a burner alarm value.
This page lists 10 BACnet objects for the Thermal Solutions EVA / EVO boiler - RWF55 controller (ProtoNode) — 2 of them writable — with each object’s type, instance number, name, engineering units and access. It is re-typed from Thermal Solutions’s own free documentation, linked below.
- Manufacturer
- Thermal Solutions
- Model
- EVA / EVO boiler - RWF55 controller (ProtoNode)
- Equipment
- Boiler operating controller (RWF55) via ProtoNode gateway
- Equipment type
- Boilers & water heaters
- BACnet objects
- 10 (2 writable)
- Transport
- BACnet IP, BACnet MS/TP
- Firmware
- Not stated
- Default device instance
- 50000 + the controller's Modbus Node-ID (Node_Offset default 50,000, changeable in the Web Configurator)
- Also known as
- RWF55, Siemens RWF55, EVA, EVAW, EVO, EVOW, FPC-N34-0643, ProtoNode FPC-N34
BMS integration notes: Thermal Solutions EVA / EVO boiler - RWF55 controller (ProtoNode)
Wire the RWF55 R+/R- terminals to the ProtoNode, set it to 19200 8N1 with a unique Node-ID, add the RWF55 profile in the Web Configurator, and discover it at 50000 + Node-ID. Setpoint 1 and Setpoint 2 are the only writable objects; the rest is monitoring.
Minimum points to map
The short list most integrators start with — enough to run the unit from a BMS. Map more as the job needs.
| Object | Name | Why | Access |
|---|---|---|---|
| AV 5 | Setpoint 1 | Setpoint 1 written by the BMS | Write |
| AI 4 | Actual Setpoint | Setpoint currently in use | Read |
| AI 1 | Analog Input InP1 | Input InP1 reading; units per controller setup | Read |
| AI 8 | Actual Angular Positioning | Actual actuator position | Read |
| AI 9 | Burner Alarm | Burner alarm; code meanings not given in the guide | Read |
| BI 1 | Com Status | Modbus link between ProtoNode and the RWF55 | Read |
Enable & remote start
The guide gives no remote-enable procedure; only Setpoint 1 (AV 5) and Setpoint 2 (AV 6) are writable.
Network setup
- Device instance = Node_Offset (default 50,000) + the controller's Modbus Node-ID, so Node-ID 1 gives 50001.
- ProtoNode default IP is 192.168.1.24 (255.255.255.0); change it in the FS-GUI under Setup > Network Settings.
- FPC-N34 S-bank DIP switches pick the protocol: all Off = BACnet IP, S0 On = BACnet MS/TP, S2 On = BACnet MS/TP single node.
- BACnet MS/TP: one MAC address (1-127) for the whole ProtoNode on A-bank DIP switches; baud on B-bank switches, factory default 38400.
- Modbus side: every RWF40, RWF55 and RM7800 must run Modbus RTU at 19200, 8N1 with a unique Node-ID (1-255); add each one as a profile in the Web Configurator.
- With more than one controller on a ProtoNode set BACnet Virtual Server Nodes to Yes; give each ProtoNode on a subnet its own BACnet Network Number (default 50).
Watch out for
- AI 3 and AI 7 are both named Analog Input InP3; AI 7 is the unfiltered value.
- RWF55 wiring: R+ to ProtoNode Tx+, R- to Rx-; the RWF55 has no ground terminal.
Thermal Solutions EVA / EVO boiler - RWF55 controller (ProtoNode) BACnet objects
Type: AI, AO, AV, BI, BO, BV, MI/MO/MV (multi-state) · Access: Read read-only, Write writable, Command writable with a priority array.
Note: the source document has no read/write column, so access here is inferred from the object type (inputs read-only, values writable). Confirm on the live controller before writing.
| Description | States | |||||
|---|---|---|---|---|---|---|
| BImin | 1 | Com Status | ProtoNode-to-RWF55 Modbus link status | Read | ||
| AImin | 1 | Analog Input InP1 | Analog input InP1 value | Read | ||
| AI | 2 | Analog Input InP2 | Analog input InP2 value | Read | ||
| AI | 3 | Analog Input InP3 | Analog input InP3 value | Read | ||
| AImin | 4 | Actual Setpoint | Setpoint currently in use | Read | ||
| AVmin | 5 | Setpoint 1 | Setpoint 1, writable | Write | ||
| AV | 6 | Setpoint 2 | Setpoint 2, writable | Write | ||
| AI | 7 | Analog Input InP3 | Analog input InP3, unfiltered value | Read | ||
| AImin | 8 | Actual Angular Positioning | Actual actuator angular position | Read | ||
| AImin | 9 | Burner Alarm | Burner alarm value | Read |
No points match these filters.
Integration notes
- Each connected controller shows up as its own BACnet device on the ProtoNode FPC-N34 gateway.
- The table has no read/write column; access here is inferred from the LonWorks direction (nvi = writable) in the same table.
- The guide gives no engineering units or value ranges; units follow the controller's own configuration.
- Two objects share the name Analog Input InP3: AI 3 and AI 7 (the LonWorks name marks AI 7 as the unfiltered value).
Check it against the live device. A points list tells you what the controller can expose; the unit in front of you may differ by firmware or installed options. Easy BACnet scans a network for BACnet IP devices from an Android phone, reads every object on the EVA / EVO boiler - RWF55 controller (ProtoNode) and exports what it actually has to Excel — free. New to BACnet? Start with what a BACnet points list is and what the object types mean.
Questions about the Thermal Solutions EVA / EVO boiler - RWF55 controller (ProtoNode)
How many BACnet points does the Thermal Solutions EVA / EVO boiler - RWF55 controller (ProtoNode) have?
This list has 10 BACnet objects: 7 analog inputs, 2 analog values, 1 binary input. The exact set on a given unit depends on its firmware, installed options and configuration.
Which Thermal Solutions EVA / EVO boiler - RWF55 controller (ProtoNode) BACnet points are writable?
2 of the 10 objects accept a write. Points marked Command have a priority array: a write holds until it is released, so release it back to automatic when you are done. The source has no read/write column, so this is inferred from object type.
Where is the official Thermal Solutions EVA / EVO boiler - RWF55 controller (ProtoNode) BACnet documentation?
The source is ProtoNode FPC-N34 and ProtoNode FPC-N35 Start-up Guide for Interfacing Thermal Solutions Product Models EVA/EVAW/EVO/EVOW with RWF40, RWF55 and RM7800 Controls (Document Revision 7.A (Web Configurator Template Revision 70)), revision 2018-08, published free by Thermal Solutions at https://boilers-water-heaters.thermalsolutions.com/Asset/Thermal%20Solutions%20EVA,%20EVAW,%20EVO%20&%20EVOW%20ProtoNode%20N34%20&%20N35%20Start-up%20Guide%202018-08.pdf.
What are the minimum BACnet points to integrate the Thermal Solutions EVA / EVO boiler - RWF55 controller (ProtoNode)?
Start with AV 5 Setpoint 1 (Setpoint 1 written by the BMS); AI 4 Actual Setpoint (Setpoint currently in use); AI 1 Analog Input InP1 (Input InP1 reading; units per controller setup); AI 8 Actual Angular Positioning (Actual actuator position); AI 9 Burner Alarm (Burner alarm; code meanings not given in the guide); BI 1 Com Status (Modbus link between ProtoNode and the RWF55).
How do I enable BMS control of the Thermal Solutions EVA / EVO boiler - RWF55 controller (ProtoNode)?
The guide gives no remote-enable procedure; only Setpoint 1 (AV 5) and Setpoint 2 (AV 6) are writable.
How do I check these points on the real EVA / EVO boiler - RWF55 controller (ProtoNode)?
Scan the network with a BACnet IP browser such as Easy BACnet, open the device and compare its object list with this table. Anything missing is usually an option that isn't installed or a point that is disabled in the controller's configuration.
More Thermal Solutions BACnet points lists
- Boiler controller via ProtoNode gateway
Thermal Solutions Apex / Arctic with Concert or Panasonic 4716 software (Universal Gateway)
Thermal Solutions Apex and Arctic boilers with the Concert control and display, and Apex boilers with the Panasonic display running 4716 software, through the Universal Gateway.
Also known as: Concert, Concert control, Apex 4716, Arctic, Arctic 1000, Arctic 1500, Universal Gateway, 106417-01, ProtoNode RER, FPC-N34-0816 - Boiler controller via ProtoNode gateway
Thermal Solutions Apex with Panasonic display, 4109 software (Universal Gateway)
Thermal Solutions Apex boilers with the control and Panasonic GT02 display running 4109 software, connected through the Universal Gateway.
Also known as: Apex, Apex 4109, Panasonic GT02, Universal Gateway, 106417-01, ProtoNode RER, FPC-N34-0816 - Boiler flame safeguard (RM7800) via ProtoNode gateway
Thermal Solutions EVA / EVO boiler - RM7800 flame safeguard (ProtoNode)
Thermal Solutions EVA, EVAW, EVO and EVOW boilers with an RM7800 series burner control, connected through a ProtoNode FPC-N34.
Also known as: RM7800, Honeywell RM7800, 7800 Series, EVA, EVAW, EVO, EVOW, FPC-N34-0643, ProtoNode FPC-N34 - Boiler operating controller (RWF40) via ProtoNode gateway
Thermal Solutions EVA / EVO boiler - RWF40 controller (ProtoNode)
Thermal Solutions EVA, EVAW, EVO and EVOW boilers whose operating control is an RWF40, connected through a ProtoNode FPC-N34.
Also known as: RWF40, Siemens RWF40, EVA, EVAW, EVO, EVOW, FPC-N34-0643, ProtoNode FPC-N34 - Boiler controller (TSBC) via ProtoNode gateway
Thermal Solutions TSBC boiler control (Universal Gateway)
Thermal Solutions boilers with the TSBC control (such as EVS and EVCA), connected through the Thermal Solutions Universal Gateway.
Also known as: TSBC, Thermal Solutions Boiler Control, Universal Gateway, 106417-01, ProtoNode RER, FPC-N34-0816, EVS, EVCA
Source: ProtoNode FPC-N34 and ProtoNode FPC-N35 Start-up Guide for Interfacing Thermal Solutions Product Models EVA/EVAW/EVO/EVOW with RWF40, RWF55 and RM7800 Controls · Document Revision 7.A (Web Configurator Template Revision 70) · rev. 2018-08. Object names, instances and units are reproduced as published; descriptions are our own.