Easy BACnet- Home
- BACnet points lists
- Thermal Solutions
- EVA / EVO boiler - RWF40 controller (ProtoNode)
Boiler operating controller (RWF40) via ProtoNode gateway · BACnet points list
Thermal Solutions EVA / EVO boiler - RWF40 controller (ProtoNode) BACnet points list
Updated 28 October 2026
Thermal Solutions EVA/EVAW/EVO/EVOW boilers expose their RWF40 controller to BACnet IP or BACnet MS/TP through a ProtoNode FPC-N34 gateway that polls it over Modbus RTU. The RWF40 profile has 15 objects: three analog inputs, setpoint and mode readbacks, and writable process enable, process setpoint, relay enables, step control and modulation values.
This page lists 15 BACnet objects for the Thermal Solutions EVA / EVO boiler - RWF40 controller (ProtoNode) — 8 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 - RWF40 controller (ProtoNode)
- Equipment
- Boiler operating controller (RWF40) via ProtoNode gateway
- Equipment type
- Boilers & water heaters
- BACnet objects
- 15 (8 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
- RWF40, Siemens RWF40, EVA, EVAW, EVO, EVOW, FPC-N34-0643, ProtoNode FPC-N34
BMS integration notes: Thermal Solutions EVA / EVO boiler - RWF40 controller (ProtoNode)
Wire the RWF40 Modbus port to the ProtoNode, set the RWF40 to 19200 8N1 with a unique Node-ID, add the RWF40 profile in the Web Configurator, then discover the device at 50000 + Node-ID. The writable objects are Process Enable, Process Setpoint, the K1/K2/K3/K6 enables, Step Control and Modulation; the guide does not describe how the boiler uses them.
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 |
|---|---|---|---|
| BV 7 | Process Enable | Process enable from the BMS | Write |
| AV 8 | Process Setpoint | Process setpoint written by the BMS | Write |
| AV 14 | Modulation | Modulation level, % | Write |
| AV 6 | Operation Mode | Controller operating mode readback | Read |
| AI 1 | Input 1 | Analog input 1 reading; units per controller setup | Read |
| BI 1 | Com Status | Modbus link between ProtoNode and the RWF40 | Read |
Enable & remote start
The guide lists BV 7 Process Enable and AV 8 Process Setpoint as writable but gives no procedure for handing control to the BMS; check the RWF40 configuration.
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
- Points have no units in the guide; scale and units depend on how the RWF40 is configured.
- Access is inferred from the LonWorks names: AV 4-6 and the analog inputs are read-only outputs, AV/BV 7-14 are writable.
- RWF40 wiring: CA to ProtoNode Tx+, CB to Rx-, CG to GND.
Thermal Solutions EVA / EVO boiler - RWF40 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-RWF40 Modbus link status | Read | ||
| AImin | 1 | Input 1 | Analog input 1 value | Read | ||
| AI | 2 | Input 2 | Analog input 2 value | Read | ||
| AI | 3 | Input 3 | Analog input 3 value | Read | ||
| AV | 4 | First Setpoint | Setpoint 1 readback | Read | ||
| AV | 5 | Second Setpoint | Setpoint 2 readback | Read | ||
| AVmin | 6 | Operation Mode | Controller operating mode | Read | ||
| BVmin | 7 | Process Enable | Process enable from the BMS | Write | ||
| AVmin | 8 | Process Setpoint | Process setpoint written over the network | Write | ||
| BV | 9 | Enable K1 | Relay K1 enable | Write | ||
| BV | 10 | Enable K2 | Relay K2 enable | Write | ||
| BV | 11 | Enable K3 | Relay K3 enable | Write | ||
| BV | 12 | Enable K6 | Relay K6 enable | Write | ||
| AV | 13 | Step Control | Step control value | Write | ||
| AVmin | 14 | Modulation | Modulation level | % | Write |
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.
- The same ProtoNode can also carry the burner's RM7800 flame safeguard and an RWF55 controller; those have separate lists.
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 - RWF40 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 - RWF40 controller (ProtoNode)
How many BACnet points does the Thermal Solutions EVA / EVO boiler - RWF40 controller (ProtoNode) have?
This list has 15 BACnet objects: 3 analog inputs, 6 analog values, 1 binary input, 5 binary values. The exact set on a given unit depends on its firmware, installed options and configuration.
Which Thermal Solutions EVA / EVO boiler - RWF40 controller (ProtoNode) BACnet points are writable?
8 of the 15 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 - RWF40 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 - RWF40 controller (ProtoNode)?
Start with BV 7 Process Enable (Process enable from the BMS); AV 8 Process Setpoint (Process setpoint written by the BMS); AV 14 Modulation (Modulation level, %); AV 6 Operation Mode (Controller operating mode readback); AI 1 Input 1 (Analog input 1 reading; units per controller setup); BI 1 Com Status (Modbus link between ProtoNode and the RWF40).
How do I enable BMS control of the Thermal Solutions EVA / EVO boiler - RWF40 controller (ProtoNode)?
The guide lists BV 7 Process Enable and AV 8 Process Setpoint as writable but gives no procedure for handing control to the BMS; check the RWF40 configuration.
How do I check these points on the real EVA / EVO boiler - RWF40 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 (RWF55) via ProtoNode gateway
Thermal Solutions EVA / EVO boiler - RWF55 controller (ProtoNode)
Thermal Solutions EVA, EVAW, EVO and EVOW boilers whose operating control is an RWF55, connected through a ProtoNode FPC-N34.
Also known as: RWF55, Siemens RWF55, 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.