Every device. One tool. Pay once. Modbus · BACnet · Siemens S7 · one-time licence · also from us: BACManager ↗

Carel pCO Modbus: From Carel Variables to Modbus Addresses (A, I, D and the Threshold)

Carel pCO controllers run thousands of chillers, air handlers and heat pumps — under Carel's name and under the names of the OEMs that build on them. There is no single pCO register list: every application program publishes its own list of supervisor variables, numbered the Carel way (A1, I12, D70). What Carel does define is how those numbers become Modbus addresses. This guide covers that rule, the threshold that moves the integers, the × 10 on analogues, and a worked example with Carel's own Standard Modular Chiller application.

ModbusManager Pro dashboard for a Carel pCO running the Standard Modular Chiller application: chiller element running with chilled water out 6.9 °C and return 12.2 °C, unit status active, mode chiller, cooling and actual set point 7.0 °C, band 2.0 K, antifreeze, flow, high and low pressure alarms OK, compressor hours 12811 and 12795, and an inlet / outlet water trend
The free workspace below on a simulated pCO with Carel's Standard Modular Chiller HP application — digitals as coils, analogues × 10, integers from register 129.

Enable Modbus on the pCO

The Mapping Rule

Carel variableModbusFunction codes
Digital D[n]coil n01 / 02 read (same data), 05 / 15 write
Analogue A[n]register n, value × 10, signed03 / 04 read (same data), 06 / 16 write
Integer I[n]register Th + n03 / 04, 06 / 16

The threshold Th depends on the protocol number and the BMS_EXTENSION setting:

ProtocolBMS_EXTENSIONThI[1] is register
3 (Modbus)0128129
3 (Modbus)1208209
30 (Modbus extended)—50015002

Through a pCOWeb (Modbus TCP, port 502) the layout is digitals = coils 1–2048, analogues = registers 1–5000, integers = registers 5001–10000; pCOWeb talks to the pCO with the Carel protocol or Modbus extended (30), not simple Modbus (3).

n or n + 1? Carel's own manual is not consistent: its table and Italian text put A[1] at register 1, its English text says register 2, and its Report Slave ID example reports the first analogue at data address 2. The workspace on this page uses the table (A[n] at address n). On your unit, read one variable you know — a set point — at n and at n + 1. A master that supports FC17 (Report Slave ID) gets the exact first and last address of the analogue, integer and digital areas from the pCO itself.

Worked Example: Standard Modular Chiller HP

From the supervisor variable list in Carel's application manual (protocol 3, BMS_EXTENSION 0, Th = 128):

VariableModbusValue
D1coil 1Unit on / off
D42coil 42On / off from supervisor (R/W, needs screen R4 enabled)
D51coil 51Mode: 0 chiller, 1 heat pump
D57coil 57Reset alarms (R/W)
D70coil 70General alarm
D71 / D77 / D78 / D82coilsAntifreeze / evaporator flow switch / high pressure / low pressure
A11 / A12register 11 / 12Cooling / heating set point (R/W) × 10
A14 / A15register 14 / 15Current set point / band × 10
A45 / A46register 45 / 46Main inlet / outlet water temperature × 10
I12register 140Unit status: 0 active, 1 off by alarm, 2 off by supervisor, 3 time bands, 4 digital input, 5 keypad, 6 manual
I20 / I21register 148 / 149Main pump hours, high / low word
I22…I29register 150…157Compressor 1–4 hours, high / low word each

Another application — or an OEM's own program on the same pCO — uses the same numbers for something else. Always work from the supervisor list of the program that runs on your unit.

Common Mistakes

Step-by-Step: Reading a pCO with ModbusManager

  1. Set the supervisor protocol to Modbus, note the address and speed, and get the application's supervisor variable list.
  2. In ModbusManager choose RTU, that speed, the frame, the address.
  3. Read FC01 from coil 1 for the digitals; FC03 from register 1 for the analogues (÷ 10); FC03 from Th + 1 for the integers.
  4. Check one set point at n and n + 1. Or open the workspace below if your unit runs the Standard Modular Chiller application.

Download a Ready-Made Workspace

Read-only, one application. Nothing is written. The addresses fit Carel's Standard Modular Chiller HP application with protocol 3 and BMS_EXTENSION 0, address 1; other programs need their own list. Tags and dashboard are ModbusManager Pro features; Standard opens the poll windows only.

Carel_pCO_Chiller.json

Carel pCO workspace for the Standard Modular Chiller HP application (Modbus RTU). Open via Workspace › Open in ModbusManager Pro, or from the in-app Device library.

Download Workspace

Try it with ModbusManager Pro

Chiller and AHU elements, Structured Text for application-specific decoding, alarms, historian, and MQTT to Home Assistant. Free 14-day trial. No credit card. Windows 10/11.

Download Pro Trial

Your unit's map in a PDF? The register map service turns it into a workspace. Pumps on the same water circuit: Grundfos MAGNA3. All guides: Modbus device guides.

Frequently Asked Questions

Is there a standard Carel pCO Modbus register list?

No. Each pCO application program publishes its own list of supervisor variables. Carel defines only how a variable number becomes a Modbus address: digital D[n] = coil n, analogue A[n] = register n (x 10), integer I[n] = register threshold + n.

What is the integer offset on a Carel pCO?

The threshold depends on the protocol: 128 for Modbus (protocol 3) with BMS_EXTENSION 0, 208 with BMS_EXTENSION 1, and 5001 for Modbus extended (protocol 30). Integer I[1] is then register 129, 209 or 5002.

Why are Carel analogue values ten times too big?

Analogue variables are sent multiplied by 10 as signed 16-bit registers: 70 is 7.0 °C, -120 is -12.0 °C.

Is A1 register 1 or register 2 on a Carel pCO?

Carel's manual says both in different places. Read a variable you know, such as a set point, at n and n + 1, or ask the pCO itself with FC17 Report Slave ID, which returns the first and last address of each variable area.

How do I switch a pCO from the Carel protocol to Modbus?

In the application's supervisor settings (in Carel's Standard Modular Chiller, screen R5) choose Modbus instead of CAREL, then set speed and address (screen R6). The system variable behind it is COM_PROTOCOL_BMS = 3.

Sources

Carel, Modbus protocol for pCO controllers, +030221945 rel. 1.1 (2012); pCOWeb user manual, +030220966 rel. 1.2 (2018); Standard Modular Chiller HP application manual, +030221251 rel. 2.9 (2015), all carel.com. Tested against a simulator built from these documents, not against a physical controller.

// beyond the chiller

The chiller plus the rest of the plant

ModbusManager Pro reads the pCO next to pumps, meters and the BMS, and republishes the values as one Modbus TCP map or as MQTT topics with Home Assistant discovery.

Modbus gateway software →