- Home
- BACnet points lists
- Peerless
- PureFire PF-460, PF-850, PF-1000, PF-1500 (852IF) - ProtoNode
Boiler controller gateway · BACnet points list
Peerless PureFire PF-460, PF-850, PF-1000, PF-1500 (852IF) - 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 852IF profile has 35 objects: state, status and error codes for the managing and dependent controls, temperatures, firing rate, pump states and counters, plus writable CH/DHW setpoints and modes, a units selector and a controller reset.
This page lists 35 BACnet objects for the Peerless PureFire PF-460, PF-850, PF-1000, PF-1500 (852IF) - ProtoNode — 6 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-460, PF-850, PF-1000, PF-1500 (852IF) - ProtoNode
- Equipment
- Boiler controller gateway
- Equipment type
- Boilers & water heaters
- BACnet objects
- 35 (6 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, 852IF, PF-460, PF-850, PF-1000, PF-1500, ProtoNode FPC-N34, PB Heat
BMS integration notes: Peerless PureFire PF-460, PF-850, PF-1000, PF-1500 (852IF) - ProtoNode
Set each boiler's Modbus node ID, let the ProtoNode auto-discover them, then find each boiler as its own BACnet device. Write the CH mode and CH setpoint AVs (DHW mode and setpoint for DHW), and read state, status, supply temperature, firing rate and the error and warning codes.
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 | CH Mode | Central heat mode command | Write |
| AV 3 | CH Setpoint | Central heat setpoint command | Write |
| AI 3 | State (Managing) | Operating state code | Read |
| AI 4 | Status (Managing) | Status code | Read |
| AI 11 | Supply Temp | Supply water temperature | Read |
| AI 16 | Firing Rate | Burner firing rate | Read |
| AI 5 | Error Code (Managing) | Active error code | Read |
| AI 6 | Warning Code | Active warning code | Read |
Enable & remote start
The writable objects are AV 3 CH Setpoint, AV 4 DHW Setpoint, AV 5 CH Mode, AV 6 DHW Mode, BV 1 Controller Reset and BV 2 Modbus Units. The guide does not give the mode values or say how they interact with the boiler's local settings.
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; BI 1 / BV 2 Modbus Units appear to set the unit system (the guide does not say), so check temperatures against the boiler display.
- Code points (state, status, error, warning) need the boiler manual to decode.
Peerless PureFire PF-460, PF-850, PF-1000, PF-1500 (852IF) - 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 | |||||
|---|---|---|---|---|---|---|
| BI | 1 | Modbus Units | Unit system in use | Read | ||
| AI | 2 | Device Type | Device type code | Read | ||
| AImin | 3 | State (Managing) | Managing control state | Read | ||
| AImin | 4 | Status (Managing) | Managing control status | Read | ||
| AImin | 5 | Error Code (Managing) | Managing control error code | Read | ||
| AImin | 6 | Warning Code | Active warning code | Read | ||
| AI | 7 | CH Setpoint | Central heat setpoint readback | Read | ||
| AI | 8 | DHW Setpoint | DHW setpoint readback | Read | ||
| AI | 9 | CH Mode | Central heat mode readback | Read | ||
| AI | 10 | DHW Mode | DHW mode readback | Read | ||
| AImin | 11 | Supply Temp | Supply water temperature | Read | ||
| AI | 12 | Return Temp | Return water temperature | Read | ||
| AI | 13 | DHW Temp | DHW temperature | Read | ||
| AI | 14 | Flue Gas Temp | Flue gas temperature | Read | ||
| AI | 15 | Header Temp | System header temperature | Read | ||
| AImin | 16 | Firing Rate | Firing rate | Read | ||
| AI | 17 | Flame Current | Flame current | Read | ||
| AI | 18 | Analog In | Analog input value | Read | ||
| AI | 19 | CH Pump | Central heat pump state | Read | ||
| AI | 20 | DHW Pump | DHW pump state | Read | ||
| AI | 21 | Successful Igntions | Successful ignition count | Read | ||
| AI | 22 | Failed Ignitions | Failed ignition count | Read | ||
| AI | 23 | Flame Failures | Flame failure count | Read | ||
| AI | 24 | Burner On | Burner on hours | Read | ||
| AI | 25 | Burner On DHW | Burner on hours for DHW | Read | ||
| AI | 26 | State (Dependent) | Dependent control state | Read | ||
| AI | 27 | Status (Dependent) | Dependent control status | Read | ||
| AI | 28 | Error Code (Dependent) | Dependent control error code | Read | ||
| AI | 29 | Firiing Rate (Dependent) | Dependent control firing rate | Read | ||
| BV | 1 | Controller Reset | Controller reset command | Write | ||
| BV | 2 | Modbus Units | Unit system selection | Write | ||
| AVmin | 3 | CH Setpoint | Central heat setpoint command | Write | ||
| AV | 4 | DHW Setpoint | DHW setpoint command | Write | ||
| AVmin | 5 | CH Mode | Central heat mode command | Write | ||
| AV | 6 | DHW Mode | DHW mode 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-50 through PF-399 boilers use the smaller PFA-1 profile.
- Points come in Managing and Dependent pairs (state, status, error code, firing rate).
- BI 1 and BV 2 are both named Modbus Units (readback and command).
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-460, PF-850, PF-1000, PF-1500 (852IF) - 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-460, PF-850, PF-1000, PF-1500 (852IF) - ProtoNode
How many BACnet points does the Peerless PureFire PF-460, PF-850, PF-1000, PF-1500 (852IF) - ProtoNode have?
This list has 35 BACnet objects: 28 analog inputs, 4 analog values, 1 binary input, 2 binary values. The exact set on a given unit depends on its firmware, installed options and configuration.
Which Peerless PureFire PF-460, PF-850, PF-1000, PF-1500 (852IF) - ProtoNode BACnet points are writable?
6 of the 35 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-460, PF-850, PF-1000, PF-1500 (852IF) - 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-460, PF-850, PF-1000, PF-1500 (852IF) - ProtoNode?
Start with AV 5 CH Mode (Central heat mode command); AV 3 CH Setpoint (Central heat setpoint command); AI 3 State (Managing) (Operating state code); AI 4 Status (Managing) (Status code); AI 11 Supply Temp (Supply water temperature); AI 16 Firing Rate (Burner firing rate); AI 5 Error Code (Managing) (Active error code); AI 6 Warning Code (Active warning code).
How do I enable BMS control of the Peerless PureFire PF-460, PF-850, PF-1000, PF-1500 (852IF) - ProtoNode?
The writable objects are AV 3 CH Setpoint, AV 4 DHW Setpoint, AV 5 CH Mode, AV 6 DHW Mode, BV 1 Controller Reset and BV 2 Modbus Units. The guide does not give the mode values or say how they interact with the boiler's local settings.
How do I check these points on the real PureFire PF-460, PF-850, PF-1000, PF-1500 (852IF) - 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.