Easy BACnet- Home
- BACnet points lists
- Peerless
- PureFire PF-50 to PF-399 (PFA-1) - ProtoNode
Boiler controller gateway · BACnet points list
Peerless PureFire PF-50 to PF-399 (PFA-1) - ProtoNode BACnet points list
Updated 28 October 2026
A ProtoNode FPC-N34 auto-discovers PureFire boilers on Modbus RTU and makes each one a BACnet IP or BACnet MS/TP device. The PFA-1 profile is short: 14 read-only values (state, status, error and warning numbers, flow, return, DHW and flue temperatures, modes and setpoints) and two writable setpoint commands for CH and DHW.
This page lists 16 BACnet objects for the Peerless PureFire PF-50 to PF-399 (PFA-1) - ProtoNode — 2 of them writable — with each object’s type, instance number, name, engineering units and access. It is re-typed from Peerless’s own free documentation, linked below.
- Manufacturer
- Peerless
- Model
- PureFire PF-50 to PF-399 (PFA-1) - ProtoNode
- Equipment
- Boiler controller gateway
- Equipment type
- Boilers & water heaters
- BACnet objects
- 16 (2 writable)
- Transport
- BACnet IP, BACnet MS/TP
- Firmware
- Not stated
- Default device instance
- 50000 + boiler Modbus node ID (Node_Offset default 50000)
- Also known as
- PureFire, PFA-1, PF-50, PF-399, ProtoNode FPC-N34, PB Heat
BMS integration notes: Peerless PureFire PF-50 to PF-399 (PFA-1) - ProtoNode
Set each boiler's Modbus node ID, let the ProtoNode auto-discover them, then find each boiler as its own BACnet device. The BMS can write the CH and DHW setpoint commands and read state, status, temperatures and the error and warning numbers.
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 15 | CH_SETPOINT CMD | Central heat setpoint command | Write |
| AI 1 | STATE | Operating state code | Read |
| AI 2 | STATUS | Status code | Read |
| AI 5 | FLOW_TEMP | Supply water temperature | Read |
| AI 6 | RETURN_TEMP | Return water temperature | Read |
| AI 13 | CH_SETPOINT | Central heat setpoint in use | Read |
| AI 3 | ERROR_NUMBER | Active error number | Read |
| AI 4 | WARNING_NUMBER | Active warning number | Read |
Enable & remote start
Only AV 15 CH_SETPOINT CMD and AV 16 DHW_SETPOINT CMD are writable. The profile has no run/enable command; CH_MODE and DHW_MODE are read-only.
Network setup
- Device instance = Node_Offset + Modbus node ID; Node_Offset defaults to 50000 and is changed in the Web Configurator (default IP 192.168.1.24).
- S-bank DIP switches: S0-S2 all off = BACnet IP, S0 on = BACnet MS/TP.
- BACnet MS/TP: one MAC address (1-127) on the A-bank switches; baud on B0-B3, factory default 38400.
- Boiler side: Modbus RTU 9600 baud, no parity, 8 data bits, 1 stop bit; each boiler needs a unique node ID (1-255).
- A ProtoNode handles up to 1,500 registers in total.
- Auto-discovery: S3 on at first power-up; after about 3 minutes, turn S3 off to save the configuration.
Watch out for
- No units are given; check the temperature scale against the boiler display.
- State, status, error and warning values need the boiler manual to decode.
Peerless PureFire PF-50 to PF-399 (PFA-1) - 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 | |||||
|---|---|---|---|---|---|---|
| AImin | 1 | STATE | Operating state code | Read | ||
| AImin | 2 | STATUS | Status code | Read | ||
| AImin | 3 | ERROR_NUMBER | Active error number | Read | ||
| AImin | 4 | WARNING_NUMBER | Active warning number | Read | ||
| AImin | 5 | FLOW_TEMP | Supply (flow) water temperature | Read | ||
| AImin | 6 | RETURN_TEMP | Return water temperature | Read | ||
| AI | 7 | DHW_TEMP | DHW temperature | Read | ||
| AI | 8 | FLUE_TEMP | Flue temperature | Read | ||
| AI | 9 | APPLIANCE_TYPE | Appliance type code | Read | ||
| AI | 10 | CONTROL_CONFIG_BYTE | Control configuration byte | Read | ||
| AI | 11 | CH_MODE | Central heat mode readback | Read | ||
| AI | 12 | DHW_MODE | DHW mode readback | Read | ||
| AImin | 13 | CH_SETPOINT | Central heat setpoint readback | Read | ||
| AI | 14 | DHW_SETPOINT | DHW setpoint readback | Read | ||
| AVmin | 15 | CH_SETPOINT CMD | Central heat setpoint command | Write | ||
| AV | 16 | DHW_SETPOINT CMD | DHW setpoint command | Write |
No points match these filters.
Integration notes
- Each boiler is its own BACnet device: device instance = Node_Offset (default 50000) + the boiler's Modbus node ID.
- No read/write column is given. AVs and BVs map to LonWorks input variables and are marked writable; AIs and BIs are read-only.
- No units or state texts are given.
- PF-460 through PF-1500 boilers use the larger 852IF profile.
- There is no writable mode or enable object in this profile; only the CH and DHW setpoint commands are writable.
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 PureFire PF-50 to PF-399 (PFA-1) - 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 Peerless PureFire PF-50 to PF-399 (PFA-1) - ProtoNode
How many BACnet points does the Peerless PureFire PF-50 to PF-399 (PFA-1) - ProtoNode have?
This list has 16 BACnet objects: 14 analog inputs, 2 analog values. The exact set on a given unit depends on its firmware, installed options and configuration.
Which Peerless PureFire PF-50 to PF-399 (PFA-1) - ProtoNode BACnet points are writable?
2 of the 16 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 Peerless PureFire PF-50 to PF-399 (PFA-1) - ProtoNode BACnet documentation?
The source is ProtoNode FPC-N34 and ProtoNode FPC-N35 Start-up Guide for Interfacing Peerless PureFire Boilers Products: 852IF, PFA-1 (PF8296 R0), revision Document Revision 1.C, November 2016, published free by Peerless at https://www.peerlessboilers.com/wp-content/uploads/2017/12/PF8296-REV0_Manual-ProtoNode-Start-up-Guide-PF850-1500.pdf.
What are the minimum BACnet points to integrate the Peerless PureFire PF-50 to PF-399 (PFA-1) - ProtoNode?
Start with AV 15 CH_SETPOINT CMD (Central heat setpoint command); AI 1 STATE (Operating state code); AI 2 STATUS (Status code); AI 5 FLOW_TEMP (Supply water temperature); AI 6 RETURN_TEMP (Return water temperature); AI 13 CH_SETPOINT (Central heat setpoint in use); AI 3 ERROR_NUMBER (Active error number); AI 4 WARNING_NUMBER (Active warning number).
How do I enable BMS control of the Peerless PureFire PF-50 to PF-399 (PFA-1) - ProtoNode?
Only AV 15 CH_SETPOINT CMD and AV 16 DHW_SETPOINT CMD are writable. The profile has no run/enable command; CH_MODE and DHW_MODE are read-only.
How do I check these points on the real PureFire PF-50 to PF-399 (PFA-1) - 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 Peerless BACnet points lists
Source: ProtoNode FPC-N34 and ProtoNode FPC-N35 Start-up Guide for Interfacing Peerless PureFire Boilers Products: 852IF, PFA-1 · PF8296 R0 · rev. Document Revision 1.C, November 2016. Object names, instances and units are reproduced as published; descriptions are our own.