Easy BACnet- Home
- BACnet points lists
- Cleaver-Brooks
- UDC 2500 loop controller profile (ProtoNode)
Process loop controller via BACnet gateway · BACnet points list
Cleaver-Brooks UDC 2500 loop controller profile (ProtoNode) BACnet points list
Updated 7 November 2026Unofficial source
The ProtoNode maps the UDC 2500 controller to BACnet: process variable, remote variable, inputs, alarm states and actions as AIs, and working setpoint, output, tuning, alarm setpoints, limits, overrides, local/remote setpoint and auto/manual selection as writable AVs.
This page lists 42 BACnet objects for the Cleaver-Brooks UDC 2500 loop controller profile (ProtoNode) — 31 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
- UDC 2500 loop controller profile (ProtoNode)
- Equipment
- Process loop controller via BACnet gateway
- Equipment type
- Other equipment
- BACnet objects
- 42 (31 writable)
- Transport
- BACnet MS/TP, BACnet IP
- Firmware
- Not stated
- Default device instance
- 50000 + Modbus Node-ID
- Also known as
- UDC 2500, UDC2500, Honeywell UDC 2500, 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)
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 UDC 2500 loop controller profile (ProtoNode)
Read the process variable and output; write the local setpoint and auto/manual mode only if the BMS is meant to adjust the loop.
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 14 | SP1_LSP1 | Local setpoint 1 | Write |
| AV 30 | AutoMan | Auto/manual selection | Write |
| AI 1 | PV | Process variable | Read |
| AV 1 | WorkingSP | Working setpoint | Write |
| AV 2 | Output | Controller output | Write |
| AI 10 | AlarmStat1_16 | Alarm status bits 1-16 | Read |
Network setup
- BACnet Device Instance = the controller's Modbus Node-ID + Node_Offset (default 50,000), so Node-ID 1 = 50001. Change Node_Offset in the ProtoNode web configurator to pick other instances.
- The ProtoNode RER does BACnet MS/TP or BACnet IP, selected on its S bank DIP switches.
- BACnet MS/TP: one MAC address (1-127) for the whole ProtoNode on the A bank DIP switches; baud on B0-B3 (38400 factory default).
- BACnet IP: default ProtoNode address 192.168.1.24; change it in the web configurator.
Watch out for
- Tuning (gain, reset, rate) and limit AVs change the controller's configuration; don't write them cyclically.
Cleaver-Brooks UDC 2500 loop controller profile (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 | PV | Modbus 40001 | Read | ||
| AI | 2 | RV | Modbus 40002 | Read | ||
| AI | 3 | Input1 | Modbus 40005 | Read | ||
| AI | 4 | Input2 | Modbus 40006 | Read | ||
| AI | 5 | Direction | Modbus 40008 | Read | ||
| AI | 6 | PVLow | Modbus 40012 | Read | ||
| AI | 7 | PVHigh | Modbus 40013 | Read | ||
| AI | 8 | Alm1Action | Modbus 40016 | Read | ||
| AI | 9 | Alm2Action | Modbus 40026 | Read | ||
| AImin | 10 | AlarmStat1_16 | Modbus 47153 | Read | ||
| AI | 11 | AlarmStat17_32 | Modbus 47154 | Read | ||
| AVmin | 1 | WorkingSP | Modbus 40003 | Write | ||
| AVmin | 2 | Output | Modbus 40004 | Write | ||
| AV | 3 | Gain1 | Modbus 40007 | Write | ||
| AV | 4 | Reset1 | Modbus 40009 | Write | ||
| AV | 5 | Rate1 | Modbus 40010 | Write | ||
| AV | 6 | CycleTime1 | Modbus 40011 | Write | ||
| AV | 7 | Alm1SP1 | Modbus 40014 | Write | ||
| AV | 8 | Alm1SP2 | Modbus 40015 | Write | ||
| AV | 9 | Gain2 | Modbus 40017 | Write | ||
| AV | 10 | Deadband | Modbus 40018 | Write | ||
| AV | 11 | Reset2 | Modbus 40019 | Write | ||
| AV | 12 | Rate2 | Modbus 40020 | Write | ||
| AV | 13 | CycleTime2 | Modbus 40021 | Write | ||
| AVmin | 14 | SP1_LSP1 | Modbus 40022 | Write | ||
| AV | 15 | LSP2 | Modbus 40023 | Write | ||
| AV | 16 | Alm2SP1 | Modbus 40024 | Write | ||
| AV | 17 | Alm2SP2 | Modbus 40025 | Write | ||
| AV | 18 | SPLowLimit | Modbus 40027 | Write | ||
| AV | 19 | SPHighLimit | Modbus 40028 | Write | ||
| AV | 20 | WorkingSPa | Modbus 40029 | Write | ||
| AV | 21 | OutputLowLimit | Modbus 40030 | Write | ||
| AV | 22 | OutputHighLimit | Modbus 40031 | Write | ||
| AV | 23 | OutputWorkValue | Modbus 40032 | Write | ||
| AV | 24 | PVOverride | Modbus 40033 | Write | ||
| AV | 25 | SPOverride | Modbus 40034 | Write | ||
| AV | 26 | OutOverride | Modbus 40035 | Write | ||
| AV | 27 | Ratio | Modbus 40036 | Write | ||
| AV | 28 | Bias | Modbus 40037 | Write | ||
| AV | 29 | LocRemSP | Modbus 40253 | Write | ||
| AVmin | 30 | AutoMan | Modbus 40251 | Write | ||
| AV | 31 | SPState | Modbus 40252 | Write |
No points match these filters.
Object ID lookup: Cleaver-Brooks UDC 2500 loop controller profile point IDs by name
AI1PVAI2RVAI3Input1AI4Input2AI5DirectionAI6PVLowAI7PVHighAI8Alm1ActionAI9Alm2ActionAI10AlarmStat1_16AI11AlarmStat17_32AV1WorkingSPAV2OutputAV3Gain1AV4Reset1AV5Rate1AV6CycleTime1AV7Alm1SP1AV8Alm1SP2AV9Gain2AV10DeadbandAV11Reset2AV12Rate2AV13CycleTime2AV14SP1_LSP1AV15LSP2AV16Alm2SP1AV17Alm2SP2AV18SPLowLimitAV19SPHighLimitAV20WorkingSPaAV21OutputLowLimitAV22OutputHighLimitAV23OutputWorkValueAV24PVOverrideAV25SPOverrideAV26OutOverrideAV27RatioAV28BiasAV29LocRemSPAV30AutoManAV31SPState
Integration notes
- Each Cleaver-Brooks controller on the ProtoNode is its own BACnet device; the object instances below are the same on every device.
- The guide prints no write-point stars for this profile; the AV/BV objects map to Metasys N2 outputs and Modbus output registers or coils, so they are taken as writable. Access is inferred from object type.
- The guide gives no engineering units or state texts; units appear only where the object name carries them (DEG F / DEG C).
- Where a description is filled in, it gives the register from the guide's Modbus column.
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 UDC 2500 loop controller profile (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 UDC 2500 loop controller profile (ProtoNode)
How many BACnet points does the Cleaver-Brooks UDC 2500 loop controller profile (ProtoNode) have?
This list has 42 BACnet objects: 11 analog inputs, 31 analog values. The exact set on a given unit depends on its firmware, installed options and configuration.
Which Cleaver-Brooks UDC 2500 loop controller profile (ProtoNode) BACnet points are writable?
31 of the 42 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 Cleaver-Brooks UDC 2500 loop controller profile (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 UDC 2500 loop controller profile (ProtoNode)?
Start with AV 14 SP1_LSP1 (Local setpoint 1); AV 30 AutoMan (Auto/manual selection); AI 1 PV (Process variable); AV 1 WorkingSP (Working setpoint); AV 2 Output (Controller output); AI 10 AlarmStat1_16 (Alarm status bits 1-16).
How do I check these points on the real UDC 2500 loop controller profile (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
- Boiler feedwater deaerator and surge tank controller via BACnet gateway
Cleaver-Brooks ADAC 1000 deaerator / surge tank control (ProtoNode, EtherNet/IP)
Cleaver-Brooks deaerator and surge tank packages with the ADAC 1000 PLC control, read through a ProtoNode RER gateway over EtherNet/IP.
Also known as: ADAC 1000, ADAC_1000, ProtoNode RER, 750-426 - Boiler feedwater deaerator and surge tank controller via BACnet gateway
Cleaver-Brooks ADAC deaerator / surge tank control (ProtoNode)
Cleaver-Brooks deaerator and surge tank packages with the ADAC control, read through a ProtoNode RER gateway.
Also known as: ADAC, CB deaerator control, ProtoNode RER, 750-426 - Boiler flame safeguard via BACnet gateway
Cleaver-Brooks CB120 flame safeguard (ProtoNode)
Cleaver-Brooks boilers with the CB120 flame safeguard, read through a ProtoNode RER gateway.
Also known as: CB120, CB 120, ProtoNode RER, 750-426 - Boiler flame safeguard via BACnet gateway
Cleaver-Brooks CB780 flame safeguard with expanded annunciator (ProtoNode)
Cleaver-Brooks boilers with the CB780 burner management control and expanded annunciator, read through a ProtoNode RER gateway.
Also known as: CB780, CB 780, CB780E, ProtoNode RER, 750-426 - Hot water boiler control via BACnet gateway
Cleaver-Brooks Falcon Hydronic boiler control (ProtoNode)
Cleaver-Brooks hot water boilers with the Falcon hydronic burner control, read through a ProtoNode RER gateway.
Also known as: Falcon Hydronic, ClearFire Falcon, CB Falcon, ProtoNode RER, 750-426 - Steam boiler control via BACnet gateway
Cleaver-Brooks Falcon Steam boiler control (ProtoNode)
Cleaver-Brooks steam boilers with the Falcon steam burner control, read through a ProtoNode RER gateway.
Also known as: Falcon Steam, CB Falcon steam, ProtoNode RER, 750-426 - Boiler flame safeguard and fuel-air ratio control via BACnet gateway
Cleaver-Brooks FARC with CB780 / CB783 burner control (ProtoNode)
Cleaver-Brooks boilers with a CB780/CB783 burner control and FARC fuel-air ratio control, read through a ProtoNode RER gateway.
Also known as: FARC, CB 780/783, CB783, ProtoNode RER, 750-426 - Steam or hot water boiler control via BACnet gateway
Cleaver-Brooks Hawk 1000 boiler control (ProtoNode)
Cleaver-Brooks boilers with the Hawk 1000 PLC boiler control, read through a ProtoNode RER gateway.
Also known as: Hawk 1000, CB Hawk 1000, ProtoNode RER, 750-426 - Steam or hot water boiler control via BACnet gateway
Cleaver-Brooks Hawk 2000 boiler control (ProtoNode)
Cleaver-Brooks boilers with the Hawk 2000 control, read through a ProtoNode RER gateway.
Also known as: Hawk 2000, CB Hawk 2000, ProtoNode RER, 750-426 - Steam or hot water boiler control via BACnet gateway
Cleaver-Brooks Hawk 4000 boiler control (ProtoNode)
Cleaver-Brooks boilers with the Hawk 4000 PLC boiler control, read through a ProtoNode RER gateway.
Also known as: Hawk 4000, CB Hawk 4000, ProtoNode RER, 750-426 - Steam or hot water boiler control via BACnet gateway
Cleaver-Brooks Hawk 4000 V2 boiler control (ProtoNode)
Cleaver-Brooks boilers with the HAWK 4000 V2 PLC boiler control, read through a ProtoNode RER gateway.
Also known as: HAWK 4000 V2, CB HAWK 4000 V2, HAWK_4000_V2, ProtoNode RER, 750-426 - Steam or hot water boiler control via BACnet gateway
Cleaver-Brooks Hawk 4500 boiler control (ProtoNode, EtherNet/IP)
Cleaver-Brooks boilers with the Hawk 4500 PLC boiler control, read through a ProtoNode RER gateway over EtherNet/IP.
Also known as: Hawk 4500, CB Hawk 4500, ProtoNode RER, 750-426 - Steam boiler control via BACnet gateway
Cleaver-Brooks Hawk 5000 boiler control (ProtoNode)
Cleaver-Brooks steam boilers with the Hawk 5000 control, read through a ProtoNode RER gateway.
Also known as: Hawk 5000, CB Hawk 5000, ProtoNode RER, 750-426 - Steam or hot water boiler control via BACnet gateway
Cleaver-Brooks Hawk ICS boiler control (ProtoNode)
Cleaver-Brooks boilers with the Hawk ICS control, read through a ProtoNode RER gateway.
Also known as: Hawk ICS, CB ICS, ProtoNode RER, 750-426 - Boiler lead/lag master panel via BACnet gateway
Cleaver-Brooks Hawk Master Panel lead/lag (ProtoNode)
Cleaver-Brooks Hawk Master Panels sequencing up to eight Hawk boilers (A-H), read through a ProtoNode RER gateway.
Also known as: Hawk Master Panel, Hawk Master, CB Master Panel, ProtoNode RER, 750-426 - Boiler interface module via BACnet gateway
Cleaver-Brooks HSC Boiler Interface Module (ProtoNode)
Cleaver-Brooks HSC boiler interface modules (one boiler each), read through a ProtoNode RER gateway.
Also known as: Boiler Interface Module, HSC Boiler Interface, BIM, ProtoNode RER, 750-426 - Multi-boiler sequencer (hot water boiler plant) via BACnet gateway
Cleaver-Brooks HSC Hydronic System Controller (ProtoNode)
Cleaver-Brooks HSC panels sequencing up to 10 condensing and 10 non-condensing boilers, read through a ProtoNode RER gateway.
Also known as: HSC, Hydronic System Controller, CB HSC, ProtoNode RER, 750-426 - Pump interface module (boiler plant pumps) via BACnet gateway
Cleaver-Brooks HSC Pump Interface Module (ProtoNode)
Cleaver-Brooks HSC pump interface modules (up to four system pumps), read through a ProtoNode RER gateway.
Also known as: Pump Interface Module, HSC Pump Interface, ProtoNode RER, 750-426 - Boiler water level controller via BACnet gateway
Cleaver-Brooks LCS Level Control System (ProtoNode)
Cleaver-Brooks LCS water level controllers (one or two tanks), read through a ProtoNode RER gateway.
Also known as: LCS, Level Control System, ProtoNode RER, 750-426 - Boiler feed pump controller via BACnet gateway
Cleaver-Brooks PCS Pump Control System (ProtoNode)
Cleaver-Brooks PCS pump controllers (up to four pumps on header pressure or tank level), read through a ProtoNode RER gateway.
Also known as: PCS, Pump Control System, ProtoNode RER, 750-426 - Electric power meter via BACnet gateway
Cleaver-Brooks Shark 100 power meter profile (ProtoNode)
Shark 100 power meters supplied on Cleaver-Brooks equipment, read through a ProtoNode RER gateway.
Also known as: Shark 100, Electro Industries Shark 100, ProtoNode RER, 750-426 - Electric power meter via BACnet gateway
Cleaver-Brooks Shark 200 power meter profile (ProtoNode)
Shark 200 power meters supplied on Cleaver-Brooks equipment, read through a ProtoNode RER gateway.
Also known as: Shark 200, Electro Industries Shark 200, ProtoNode RER, 750-426
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.