Easy BACnet
  1. Home
  2. BACnet points lists
  3. Cleaver-Brooks
  4. CB780 flame safeguard with expanded annunciator (ProtoNode)

Boiler flame safeguard via BACnet gateway · BACnet points list

Cleaver-Brooks CB780 flame safeguard with expanded annunciator (ProtoNode) BACnet points list

Updated 7 November 2026Unofficial source

Short answer

The ProtoNode maps the CB780 burner control to BACnet: sequence state and status strings, run mode, flame signal, alarm and lockout, the fault code, six fault history records, cycle and hour totals and the expanded annunciator limit inputs. One AV (BC_Rem_Command) is writable.

This page lists 93 BACnet objects for the Cleaver-Brooks CB780 flame safeguard with expanded annunciator (ProtoNode) — 1 of them writable — with each object’s type, instance number, name, engineering units and access. It is re-typed from a copy of Cleaver-Brooks’s documentation hosted by watmfg.com, not by Cleaver-Brooks itself, so treat it as unofficial.

Manufacturer
Cleaver-Brooks
Model
CB780 flame safeguard with expanded annunciator (ProtoNode)
Equipment
Boiler flame safeguard via BACnet gateway
Equipment type
Boilers & water heaters
BACnet objects
93 (1 writable)
Transport
BACnet MS/TP, BACnet IP
Firmware
Not stated
Default device instance
50000 + Modbus Node-ID
Also known as
CB780, CB 780, CB780E, ProtoNode RER, 750-426
Source document
Cloud Enabled ProtoNode Gateway Startup Guide (RER/LER) for interfacing Cleaver-Brooks products · 750-426 · rev. 03/2018 (unofficial copy, hosted by watmfg.com)
Download CSV 93 rows Download EDE B.I.G.-EU JSON Source PDF (unofficial copy) ↗ Compare with your scan Download Easy BACnet Mobile App Google Play

Reference only, provided as-is: verify against Cleaver-Brooks’s current documentation and the live device before use. Not official Cleaver-Brooks information. Terms of use.

BMS integration notes: Cleaver-Brooks CB780 flame safeguard with expanded annunciator (ProtoNode)

Integration in brief

Mostly a monitoring profile: read sequence state, run mode, flame signal, alarm, lockout and the fault and first-out codes. BC_Rem_Command is the one writable object.

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.

ObjectNameWhyAccess
AV 1BC_Rem_CommandRemote command registerWrite
AI 3BC_Sequence_StateBurner sequence stateRead
BI 6BC_Run_ModeBurner in runRead
AI 7BC_Flame_Signal_StrengthFlame signal strengthRead
BI 9BC_Alarm_OutAlarm outputRead
BI 10BC_LockoutLockoutRead
AI 1BC_Fault_CodeFault codeRead
AI 49ExpAnn_First_Out_CodeAnnunciator first-out codeRead

Network setup

Cleaver-Brooks CB780 flame safeguard with expanded annunciator (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.

93 of 93 shown
Type
Binary
Access
Show
Cleaver-Brooks CB780 flame safeguard with expanded annunciator (ProtoNode) BACnet Points List
DescriptionStates
BI1BC_InitiateModbus 40013, bit 0Read
BI2BC_StandbyModbus 40013, bit 1Read
BI3BC_PurgeModbus 40013, bit 2Read
BI4BC_Pilot_IgnitionModbus 40013, bit 3Read
BI5BC_Main_IgnitionModbus 40013, bit 4Read
BImin6BC_Run_ModeModbus 40013, bit 5Read
BI7BC_PostpurgeModbus 40013, bit 6Read
BI8BC_PreignitionModbus 40013, bit 7Read
BImin9BC_Alarm_OutModbus 40013, bit 13Read
BImin10BC_LockoutModbus 40013, bit 15Read
AImin1BC_Fault_CodeModbus 40001Read
AI2BC_Fault_String_CodeModbus 40002Read
AImin3BC_Sequence_StateModbus 40003Read
AI4BC_State_String_Code_L1Modbus 40004Read
AI5BC_State_String_Code_L2Modbus 40005Read
AI6BC_Sequence_TimeModbus 40006Read
AImin7BC_Flame_Signal_StrengthModbus 40011Read
AI8BC_State_BitsModbus 40013Read
AI9BC_Flt_Hist_Code_Rec1Modbus 40017Read
AI10BC_Flt_Hist_String_Rec1Modbus 40018Read
AI11BC_Flt_Hist_State_Rec1Modbus 40019Read
AI12BC_Flt_Hist_Line1_Rec1Modbus 40020Read
AI13BC_Flt_Hist_Line2_Rec1Modbus 40021Read
AI14BC_Flt_Hist_Time_Rec1Modbus 40022Read
AI15BC_Flt_Hist_Code_Rec2Modbus 40027Read
AI16BC_Flt_Hist_String_Rec2Modbus 40028Read
AI17BC_Flt_Hist_State_Rec2Modbus 40029Read
AI18BC_Flt_Hist_Line1_Rec2Modbus 40030Read
AI19BC_Flt_Hist_Line2_Rec2Modbus 40031Read
AI20BC_Flt_Hist_Time_Rec2Modbus 40032Read
AI21BC_Flt_Hist_Code_Rec3Modbus 40037Read
AI22BC_Flt_Hist_String_Rec3Modbus 40038Read
AI23BC_Flt_Hist_State_Rec3Modbus 40039Read
AI24BC_Flt_Hist_Line1_Rec3Modbus 40040Read
AI25BC_Flt_Hist_Line2_Rec3Modbus 40041Read
AI26BC_Flt_Hist_Time_Rec3Modbus 40042Read
AI27BC_Flt_Hist_Code_Rec4Modbus 40047Read
AI28BC_Flt_Hist_String_Rec4Modbus 40048Read
AI29BC_Flt_Hist_State_Rec4Modbus 40049Read
AI30BC_Flt_Hist_Line1_Rec4Modbus 40050Read
AI31BC_Flt_Hist_Line2_Rec4Modbus 40051Read
AI32BC_Flt_Hist_Time_Rec4Modbus 40052Read
AI33BC_Flt_Hist_Code_Rec5Modbus 40057Read
AI34BC_Flt_Hist_String_Rec5Modbus 40058Read
AI35BC_Flt_Hist_State_Rec5Modbus 40059Read
AI36BC_Flt_Hist_Line1_Rec5Modbus 40060Read
AI37BC_Flt_Hist_Line2_Rec5Modbus 40061Read
AI38BC_Flt_Hist_Time_Rec5Modbus 40062Read
AI39BC_Flt_Hist_Code_Rec6Modbus 40067Read
AI40BC_Flt_Hist_String_Rec6Modbus 40068Read
AI41BC_Flt_Hist_State_Rec6Modbus 40069Read
AI42BC_Flt_Hist_Line1_Rec6Modbus 40070Read
AI43BC_Flt_Hist_Line2_Rec6Modbus 40071Read
AI44BC_Flt_Hist_Time_Rec6Modbus 40072Read
AI45BC_Rem_Comd_StatModbus 40085Read
AI46BC_Vlv_Prov_ModeModbus 40104Read
AI47BC_Vlv_Prov_TimeModbus 40106Read
AI48BC_Rem_CommandModbus 40128Read
AI50BC_Total_CyclesModbus 40007Read
AI51BC_Total_HoursModbus 40009Read
AI52BC_Flt_Hist_Cyc_Rec1Modbus 40023Read
AI53BC_Flt_Hist_Hrs_Rec1Modbus 40025Read
AI54BC_Flt_Hist_Cyc_Rec2Modbus 40033Read
AI55BC_Flt_Hist_Hrs_Rec2Modbus 40035Read
AI56BC_Flt_Hist_Cyc_Rec3Modbus 40043Read
AI57BC_Flt_Hist_Hrs_Rec3Modbus 40045Read
AI58BC_Flt_Hist_Cyc_Rec4Modbus 40053Read
AI59BC_Flt_Hist_Hrs_Rec4Modbus 40055Read
AI60BC_Flt_Hist_Cyc_Rec5Modbus 40063Read
AI61BC_Flt_Hist_Hrs_Rec5Modbus 40065Read
AI62BC_Flt_Hist_Cyc_Rec6Modbus 40073Read
AI63BC_Flt_Hist_Hrs_Rec6Modbus 40075Read
AVmin1BC_Rem_CommandModbus 40128; write pointWrite
AImin49ExpAnn_First_Out_CodeModbus 40014Read
BI11EA_Valve_POCModbus 40015, bit 4Read
BI12EA_Burner_SwitchModbus 40015, bit 5Read
BI13EA_Oper_ControlModbus 40015, bit 6Read
BI14EA_Aux_Limit_1Modbus 40015, bit 7Read
BI15EA_Aux_Limit_2Modbus 40015, bit 8Read
BI16EA_LWCOModbus 40015, bit 9Read
BI17EA_High_LimitModbus 40015, bit 10Read
BI18EA_Aux_Limit_3Modbus 40015, bit 11Read
BI19EA_Oil_SelectModbus 40015, bit 12Read
BI20EA_High_Oil_PressModbus 40015, bit 13Read
BI21EA_Low_Oil_PressModbus 40015, bit 14Read
BI22EA_High_Oil_TempModbus 40015, bit 15Read
BI23EA_Low_Oil_TempModbus 40015, bit 16Read
BI24EA_Gas_SelectModbus 40015, bit 17Read
BI25EA_High_Gas_PressModbus 40015, bit 18Read
BI26EA_Low_Gas_PressModbus 40015, bit 19Read
BI27EA_Air_Flow_SwitchModbus 40015, bit 20Read
BI28EA_Aux_Limit_4Modbus 40015, bit 21Read
BI29EA_Aux_Limit_5Modbus 40015, bit 22Read
Object ID lookup: Cleaver-Brooks CB780 flame safeguard with expanded annunciator point IDs by name

Integration notes

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. This list is provided as-is for reference only and may contain mistakes — confirming it before you write, map or commission anything is up to you (terms). Easy BACnet scans a network for BACnet IP devices from an Android phone, reads every object on the CB780 flame safeguard with expanded annunciator (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 Cleaver-Brooks CB780 flame safeguard with expanded annunciator (ProtoNode)

How many BACnet points does the Cleaver-Brooks CB780 flame safeguard with expanded annunciator (ProtoNode) have?

This list has 93 BACnet objects: 63 analog inputs, 1 analog value, 29 binary inputs. The exact set on a given unit depends on its firmware, installed options and configuration.

Which Cleaver-Brooks CB780 flame safeguard with expanded annunciator (ProtoNode) BACnet points are writable?

1 of the 93 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.

Where is the official Cleaver-Brooks CB780 flame safeguard with expanded annunciator (ProtoNode) BACnet documentation?

Cleaver-Brooks does not publish it on its own website. This list comes from Cloud Enabled ProtoNode Gateway Startup Guide (RER/LER) for interfacing Cleaver-Brooks products (750-426), revision 03/2018, a copy hosted by watmfg.com at https://watmfg.com/watmfg23082016/wp-content/uploads/2016/09/750-426-ProtoNode-Cloud.pdf. Ask Cleaver-Brooks or its representative for the current revision.

What are the minimum BACnet points to integrate the Cleaver-Brooks CB780 flame safeguard with expanded annunciator (ProtoNode)?

Start with AV 1 BC_Rem_Command (Remote command register); AI 3 BC_Sequence_State (Burner sequence state); BI 6 BC_Run_Mode (Burner in run); AI 7 BC_Flame_Signal_Strength (Flame signal strength); BI 9 BC_Alarm_Out (Alarm output); BI 10 BC_Lockout (Lockout); AI 1 BC_Fault_Code (Fault code); AI 49 ExpAnn_First_Out_Code (Annunciator first-out code).

How do I check these points on the real CB780 flame safeguard with expanded annunciator (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 Cleaver-Brooks BACnet points lists

Source: Cloud Enabled ProtoNode Gateway Startup Guide (RER/LER) for interfacing Cleaver-Brooks products · 750-426 · rev. 03/2018. Object names, instances and units are reproduced as published; descriptions are our own.