Easy BACnet- Home
- BACnet points lists
- Laars
- Sola control - ProtoNode
Boiler controller gateway · BACnet points list
Laars Sola control - ProtoNode BACnet points list
Updated 28 October 2026
The ProtoNode reads the Sola control over Modbus RTU and serves 88 objects per boiler: 64 analog inputs and 24 analog values. The AIs cover sensors, firing rate, burner and CH/DHW status codes, pump status and lead-lag slave states; the AVs hold CH enable, CH, DHW and lead-lag setpoints, time-of-day setpoints and resettable counters.
This page lists 88 BACnet objects for the Laars Sola control - ProtoNode — 24 of them writable — with each object’s type, instance number, name, engineering units and access. It is re-typed from Laars’s own free documentation, linked below.
- Manufacturer
- Laars
- Model
- Sola control - ProtoNode
- Equipment
- Boiler controller gateway
- Equipment type
- Boilers & water heaters
- BACnet objects
- 88 (24 writable)
- Transport
- BACnet IP, BACnet MS/TP
- Firmware
- Not stated
- Default device instance
- 50000 + device Node-ID
- Also known as
- Sola, Laars Sola, ProtoNode FPC-N34, ProtoNode FPC-N35, FPC-N34-0701, Laars ProtoNode
BMS integration notes: Laars Sola control - ProtoNode
Write CH Enable and the CH setpoint (or the lead-lag setpoint on a lead-lag master), then read back CH status, the burner sequence, outlet temperature, firing rate and the lockout code. The mapping gives no values or units, so check written values against the boiler display.
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 76 | CH Enable | Central heat enable | Write |
| AV 46 | CH setpoint | Central heat water setpoint | Write |
| AV 50 | Lead Lag setpoint | Setpoint for a lead-lag (cascade) master | Write |
| AI 19 | CH status | Central heat status code | Read |
| AI 71 | Burner Control Sequence | Burner sequence state | Read |
| AI 2 | Outlet sensor | Outlet water temperature | Read |
| AI 3 | Firing rate | Burner firing rate | Read |
| AI 16 | Lockout code | Lockout status code | Read |
Enable & remote start
AV 76 CH Enable is the writable enable. The mapping does not give its values or say how it interacts with the boiler's own enable settings. AV 87 Burner Switch is also writable but is not explained.
Network setup
- Device instance = Node_Offset + boiler Node-ID. Node_Offset defaults to 50000 and is changed in the ProtoNode web configurator; Node-IDs must be unique, 1-255.
- Boiler to ProtoNode: Modbus RTU, 38400 baud, 8 data bits, no parity, 1 stop bit.
- Default ProtoNode IP address 192.168.1.24, mask 255.255.255.0. Choose BACnet IP or BACnet MS/TP with the Protocol Selector, then add one profile per device with its Node-ID.
- With more than one device on a ProtoNode, set BACnet Virtual Server Nodes to Yes. For BACnet MS/TP also set MAC address, baud rate and Max Master.
- Two or more ProtoNodes on the same subnet need different BACnet Network Numbers (default 50).
- A ProtoNode handles 1,500 registers in total; this profile uses 88 per device.
Watch out for
- No units or state texts are given; CH status, burner sequence and lockout codes must be decoded with the Sola documentation.
- AV 85/86 Password Reg 1/2 are writable but not explained in the mapping.
- Counters (burner run time, pump and burner cycle counts) are AVs, so the BMS can overwrite them.
Laars Sola control - 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 | |||||
|---|---|---|---|---|---|---|
| AI | 1 | Demand source | Read | |||
| AImin | 2 | Outlet sensor | Temperature | Read | ||
| AImin | 3 | Firing rate | Read | |||
| AI | 4 | Fan speed | Read | |||
| AI | 5 | Flame signal | Read | |||
| AI | 6 | Inlet sensor | Temperature | Read | ||
| AI | 7 | DHW sensor | Temperature | Read | ||
| AI | 8 | S5 sensor | Temperature | Read | ||
| AI | 9 | Stack sensor | Temperature | Read | ||
| AI | 10 | 4 - 20 mA remote ctl input | Read | |||
| AI | 11 | Active CH setpoint | Temperature | Read | ||
| AI | 12 | Active DHW setpoint | Temperature | Read | ||
| AI | 13 | Active LL setpoint | Temperature | Read | ||
| AI | 14 | Analog modulation input | Read | |||
| AI | 15 | Burner control status | Read | |||
| AImin | 16 | Lockout code | Read | |||
| AI | 17 | Alarm reason | Read | |||
| AI | 18 | Hold code | Read | |||
| AImin | 19 | CH status | Read | |||
| AI | 20 | CH setpoint source | Read | |||
| AI | 21 | CH heat demand | Read | |||
| AI | 22 | CH burner demand | Read | |||
| AI | 23 | CH requested rate | Read | |||
| AI | 24 | DHW status | Read | |||
| AI | 25 | DHW Priority Count | Read | |||
| AI | 26 | DHW heat demand | Read | |||
| AI | 27 | DHW burner demand | Read | |||
| AI | 28 | DHW requested rate | Read | |||
| AI | 29 | DHW pump status | Read | |||
| AI | 30 | DHW Pump Idle Days Count | Read | |||
| AI | 31 | System pump status | Read | |||
| AI | 32 | System Pump Idle Days Count | Read | |||
| AI | 33 | Boiler pump status | Read | |||
| AI | 34 | Boiler Pump Idle Days Count | Read | |||
| AI | 39 | Controller Cycle Count | Read | |||
| AI | 40 | Controller run time | Read | |||
| AI | 41 | Lead lag master status | Read | |||
| AI | 42 | Lead lag slave status | Read | |||
| AI | 43 | Lead Lag Master Setpoint Source | Read | |||
| AI | 44 | Lead Lag Master Pump Demand | Read | |||
| AI | 45 | Outdoor temperature | Temperature | Read | ||
| AI | 53 | Lead Lag active service | Read | |||
| AI | 54 | Slave 1 State | Read | |||
| AI | 55 | Slave 1 firing rate | Read | |||
| AI | 56 | Slave 2 State | Read | |||
| AI | 57 | Slave 2 firing rate | Read | |||
| AI | 58 | Slave 3 State | Read | |||
| AI | 59 | Slave 3 firing rate | Read | |||
| AI | 60 | Slave 4 State | Read | |||
| AI | 61 | Slave 4 firing rate | Read | |||
| AI | 62 | Slave 5 State | Read | |||
| AI | 63 | Slave 5 firing rate | Read | |||
| AI | 64 | Slave 6 State | Read | |||
| AI | 65 | Slave 6 firing rate | Read | |||
| AI | 66 | Slave 7 State | Read | |||
| AI | 67 | Slave 7 firing rate | Read | |||
| AI | 68 | Slave 8 State | Read | |||
| AI | 69 | Slave 8 firing rate | Read | |||
| AI | 70 | Master firing rate | Read | |||
| AImin | 71 | Burner Control Sequence | Read | |||
| AI | 72 | Active Rate Limiter | Read | |||
| AI | 74 | Lead Lag Slave Demand | Read | |||
| AI | 75 | Lead Lag Slave Requested Rate | Read | |||
| AI | 88 | S10 Sensor Reading | Temperature | Read | ||
| AV | 35 | Burner run time | h | Write | ||
| AV | 36 | DHW pump cycle count | Write | |||
| AV | 37 | System pump cycle count | Write | |||
| AV | 38 | Boiler pump cycle count | Write | |||
| AVmin | 46 | CH setpoint | Temperature | Write | ||
| AV | 47 | CH TOD setpoint | Temperature | Write | ||
| AV | 48 | DHW Demand Switch | Write | |||
| AV | 49 | Outlet high limit setpoint | Temperature | Write | ||
| AVmin | 50 | Lead Lag setpoint | Temperature | Write | ||
| AV | 51 | Leadlag modulation sensor | Write | |||
| AV | 52 | Warm weather shutdown setpoint | Temperature | Write | ||
| AV | 73 | Burner Cycle Count | Write | |||
| AVmin | 76 | CH Enable | Write | |||
| AV | 77 | DHW Setpoint | Temperature | Write | ||
| AV | 78 | DHW Time Of Day Setpoint | Temperature | Write | ||
| AV | 79 | Lead Lag Slave Enable | Write | |||
| AV | 80 | Lead Lag Time Of Day Setpoint | Temperature | Write | ||
| AV | 81 | Lead Lag Operation Switch | Write | |||
| AV | 82 | Warm Weather Shutdown Enbl/Disbl | Write | |||
| AV | 83 | Lead Lag DHW Setpoint | Temperature | Write | ||
| AV | 84 | Lead Lag DHW Time Of Day SP | Temperature | Write | ||
| AV | 85 | Password Reg 1 | Write | |||
| AV | 86 | Password Reg 2 | Write | |||
| AV | 87 | Burner Switch | Write |
No points match these filters.
Integration notes
- Each boiler on the ProtoNode's RS-485 bus shows up as its own BACnet device, and every one uses the same object IDs. The device instance is Node_Offset (default 50000) plus the boiler's Node-ID, so Node-ID 1 = device 50001.
- The mapping has no read/write column. AV, BV and MV objects are mapped to Metasys N2 outputs and LonWorks input variables, so they are listed here as writable; AI, BI and MI objects are read-only.
- No units or state texts are given. The LonWorks SNVT types in the source show which values are temperatures and which are hours.
- Runtime and cycle counters that span two Modbus registers (e.g. 40131/40132) are one object each.
- Weil-McLain publishes its own ProtoNode list for Sola boilers with different object numbers; use the list from the boiler's maker.
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 Sola control - 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 Laars Sola control - ProtoNode
How many BACnet points does the Laars Sola control - ProtoNode have?
This list has 88 BACnet objects: 64 analog inputs, 24 analog values. The exact set on a given unit depends on its firmware, installed options and configuration.
Which Laars Sola control - ProtoNode BACnet points are writable?
24 of the 88 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 Laars Sola control - ProtoNode BACnet documentation?
The source is Vendor Protocol Mapping (LAARS Vendor Mappings for the ProtoNode FPC-N34 / FPC-N35) (4404), revision Document Revision 14.B, October 2020, published free by Laars at https://www.laars.com/uploads/products/4404.pdf.
What are the minimum BACnet points to integrate the Laars Sola control - ProtoNode?
Start with AV 76 CH Enable (Central heat enable); AV 46 CH setpoint (Central heat water setpoint); AV 50 Lead Lag setpoint (Setpoint for a lead-lag (cascade) master); AI 19 CH status (Central heat status code); AI 71 Burner Control Sequence (Burner sequence state); AI 2 Outlet sensor (Outlet water temperature); AI 3 Firing rate (Burner firing rate); AI 16 Lockout code (Lockout status code).
How do I enable BMS control of the Laars Sola control - ProtoNode?
AV 76 CH Enable is the writable enable. The mapping does not give its values or say how it interacts with the boiler's own enable settings. AV 87 Burner Switch is also writable but is not explained.
How do I check these points on the real Sola control - 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 Laars BACnet points lists
- Boiler controller gateway
Laars HTD control - ProtoNode
Laars boilers with the HTD control, read through a ProtoNode FPC-N34 gateway (the document does not name the models).
Also known as: HTD, Laars HTD, ProtoNode FPC-N34, ProtoNode FPC-N35, FPC-N34-0701, Laars ProtoNode - Boiler controller gateway
Laars MagnaTherm - ProtoNode
Laars MagnaTherm units, read through a ProtoNode FPC-N34 gateway.
Also known as: MagnaTherm, Laars MagnaTherm, ProtoNode FPC-N34, ProtoNode FPC-N35, FPC-N34-0701, Laars ProtoNode - Boiler controller gateway
Laars Multiburner control - ProtoNode
Laars boilers with the Multiburner control, read through a ProtoNode FPC-N34 gateway (the document does not name the models).
Also known as: Multiburner, Laars Multiburner, Multi-burner, ProtoNode FPC-N34, ProtoNode FPC-N35, FPC-N34-0701, Laars ProtoNode - Boiler controller gateway
Laars OmniTherm - ProtoNode
Laars OmniTherm units, read through a ProtoNode FPC-N34 gateway.
Also known as: OmniTherm, Laars OmniTherm, ProtoNode FPC-N34, ProtoNode FPC-N35, FPC-N34-0701, Laars ProtoNode - Gas valve gateway
Laars SV2 gas valve - ProtoNode
The SV2 device on Laars equipment, read through a ProtoNode FPC-N34 gateway. The document does not describe the SV2; its point names cover a gas valve with VPS tests and pressure and fuel/air modules.
Also known as: SV2, Laars SV2, ProtoNode FPC-N34, ProtoNode FPC-N35, FPC-N34-0701, Laars ProtoNode
Source: Vendor Protocol Mapping (LAARS Vendor Mappings for the ProtoNode FPC-N34 / FPC-N35) · 4404 · rev. Document Revision 14.B, October 2020. Object names, instances and units are reproduced as published; descriptions are our own.