Easy Modbus
  1. Home
  2. Modbus register maps
  3. Carlo Gavazzi
  4. DCM1 DC energy meter for EV chargers (Modbus RTU / TCP)

Energy meter (DC) · Modbus register map

Carlo Gavazzi DCM1 DC energy meter for EV chargers (Modbus RTU / TCP) Modbus register map

Updated 17 November 2026

Short answer

The DCM1 is a two-part DC meter (DCM-D display/meter plus DCM-T transducer) for DC fast chargers, with RS485 Modbus RTU and Modbus TCP. Readings are 32-bit integers sent low word first with fixed weights. This map covers voltage, current, power, energy and Ah counters, run hours, shunt temperatures, serial and Ethernet settings, resets, the device state word and the main OCMF charging-session registers.

This page lists 71 Modbus registers for the Carlo Gavazzi DCM1 DC energy meter for EV chargers (Modbus RTU / TCP) — 32 writable — with the table, 0-based wire address, data type, word order, scale, units and access of each, re-typed from Carlo Gavazzi’s own free documentation (linked below) and checked against it.

Manufacturer
Carlo Gavazzi
Model
DCM1 DC energy meter for EV chargers (Modbus RTU / TCP)
Equipment type
Energy meter (DC)
Registers
71 (32 writable)
Transport
Modbus RTU, Modbus TCP
Default unit ID
1
Default serial
9600 baud, 8N1
TCP port
502
Documented addressing
Modicon 3xxxx/4xxxx (drop the prefix, subtract 1)
32-bit word order
CDAB low word first (word-swapped)
Firmware
OCMF display/string registers need firmware 1.5.3 onward
Also known as
DCM1A60V10L20S1PFA, DCM1A60V10L20S1PFB, DCM1A60V10L20S2DEB, DCM1A60V10L20S3DEB, DCM1A60V10L20S2DEBF, DCM1A60V10L20S3DEBF, DCM1A30V10L20S1PFA, DCM1A30V10L20S1PFB, DCM1A30V10L20S2DEB, DCM1A30V10L20S3DEB, DCM1A30V10L20S2DEBF, DCM1A30V10L20S3DEBF, DCM1A60V10L20S1ULB, DCM1A30V10L20S1ULB
Source document
DCM1 Modbus Communication Protocol - Public version · Version 1.11 · rev. 2025-07-30
Download CSV all columns JSON Manufacturer PDF ↗

Integration notes: Carlo Gavazzi DCM1 DC energy meter for EV chargers (Modbus RTU / TCP)

Integration in brief

Poll input registers 0000h-0005h (function 04 or 03) for V, A and W and 0010h-0027h for energy; values are INT32 low word first with fixed weights. For signed charging sessions follow the OCMF procedure around 7040h and 7100h.

Minimum registers to map

Addresses are 0-based wire addresses. Enough to monitor and run the unit; map more as the job needs.

RegisterNameTypeWhyAccess
IR 0VoltageINT32 CDABDC voltageRead
IR 2CurrentINT32 CDABDC currentRead
IR 4PowerINT32 CDABDC powerRead
IR 16kWh (+) TOTINT32 CDABImported energy totalRead
IR 32kWh (-) TOTINT32 CDABExported energy totalRead
HR 20498Device stateBITMAP16Device state / transducer healthRead
HR 28741Charging statusUINT16Charging session statusRead

Enable Modbus control & writes

RS485 and Ethernet are both active. Serial settings at 2000h-2004h take effect after writing 1 to 2010h; Ethernet settings at 2100h-210Dh after writing 1 to 210Eh or a power cycle.

Byte order & addressing

Network setup

Watch out for

Carlo Gavazzi DCM1 DC energy meter for EV chargers (Modbus RTU / TCP) Modbus registers

Address = 0-based wire address (the documented number is shown under it when it differs) · Order: ABCD = high word first, CDAB = low word first · Scale: engineering value = raw × scale.

71 of 71 shown
Carlo Gavazzi DCM1 DC energy meter for EV chargers (Modbus RTU / TCP) Modbus register map
TableAddressNameDescriptionTypeOrderScaleUnitsAccessValues / bits
IR0doc 300001 / 0000hVoltageINT32CDAB× 0.1VRead
IR2doc 300003 / 0002hCurrentINT32CDAB× 0.001ARead
IR4doc 300005 / 0004hPowerSigned DC power.INT32CDAB× 0.1WRead
IR11doc 300012 / 000BhCarlo Gavazzi identification codeModel code, e.g. 1824 = DCM1A60V10L20S1PFA; see the part-number table.UINT16Read
IR16doc 300017 / 0010hkWh (+) TOTINT32CDAB× 0.1kWhRead
IR18doc 300019 / 0012hAh (+) TOTINT32CDAB× 0.1AhRead
IR20doc 300021 / 0014hkWh (+) PARINT32CDAB× 0.1kWhRead
IR22doc 300023 / 0016hAh (+) PARINT32CDAB× 0.1AhRead
IR32doc 300033 / 0020hkWh (-) TOTINT32CDAB× 0.1kWhRead
IR34doc 300035 / 0022hAh (-) TOTINT32CDAB× 0.1AhRead
IR36doc 300037 / 0024hkWh (-) PARINT32CDAB× 0.1kWhRead
IR38doc 300039 / 0026hAh (-) PARINT32CDAB× 0.1AhRead
IR44doc 300045 / 002ChRun hour meterINT32CDAB× 0.01hRead
IR46doc 300047 / 002EhRun hour meter kWh-Hours counted while energy flows in the negative direction.INT32CDAB× 0.01hRead
IR48doc 300049 / 0030hRun hour meter ON timeHours the meter has been powered.INT32CDAB× 0.01hRead
IR50doc 300051 / 0032hRun hour meter PARINT32CDAB× 0.01hRead
IR52doc 300053 / 0034hRun hour meter kWh- PARINT32CDAB× 0.01hRead
IR54doc 300055 / 0036hRun hour meter ON time PARINT32CDAB× 0.01hRead
IR80doc 300081 / 0050hT1 (shunt terminal 1 temperature)INT32CDAB× 0.1°CRead
IR82doc 300083 / 0052hT2 (shunt terminal 2 temperature)INT32CDAB× 0.1°CRead
IR770doc 300771 / 0302hFirmware version DCM-D (meter)High byte: bits 0-3 minor, bits 4-7 major; low byte: revision.UINT16Read
IR771doc 300772 / 0303hFirmware version DCM-D (cryptography)High byte: bits 0-3 minor, bits 4-7 major; low byte: revision.UINT16Read
IR772doc 300773 / 0304hFirmware version DCM-T (transducer)High byte: bits 0-3 minor, bits 4-7 major; low byte: revision.UINT16Read
HR4096doc 304097 / 1000hPassword0 = no password (default), up to 9999.UINT16Read/write
HR4355doc 304356 / 1103hEasy connectionUINT16Read/write0 = Disabled (default); 1 = Enabled
HR4361doc 304362 / 1109hQuick set up at next power onUINT16Read/write0 = Menu disabled; 1 = Menu enabled (default)
HR4363doc 304364 / 110BhStart-up current of run hour counterDefault 480 (0.48 A); A30 models 160-300000, A60 models up to 600000.UINT32CDAB× 0.001ARead/write
HR8192doc 308193 / 2000hRS485 instrument address1-247, default 1.UINT16Read/write
HR8193doc 308194 / 2001hRS485 baud rateUINT16Read/write1 = 9.6 kbps (default); 2 = 19.2 kbps; 3 = 38.4 kbps; 4 = 57.6 kbps; 5 = 115.2 kbps
HR8194doc 308195 / 2002hRS485 parityUINT16Read/write1 = No parity (default); 2 = Even parity
HR8195doc 308196 / 2003hStop bitUINT16Read/write1 = 1 (default); 2 = 2
HR8196doc 308197 / 2004hRS485 delay on reply0-1000, default 0.UINT16msRead/write
HR8208doc 308209 / 2010hUpdate serial communication settingsWrite 1 to apply new serial settings.UINT16Read/write
HR8448doc 308449 / 2100hStored IP address octet ADefault 192.168.1.10; used when DHCP is off.UINT16Read/write
HR8449doc 308450 / 2101hStored IP address octet BUINT16Read/write
HR8450doc 308451 / 2102hStored IP address octet CUINT16Read/write
HR8451doc 308452 / 2103hStored IP address octet DUINT16Read/write
HR8452doc 308453 / 2104hStored subnet mask octet ADefault 255.255.255.0.UINT16Read/write
HR8453doc 308454 / 2105hStored subnet mask octet BUINT16Read/write
HR8454doc 308455 / 2106hStored subnet mask octet CUINT16Read/write
HR8455doc 308456 / 2107hStored subnet mask octet DUINT16Read/write
HR8456doc 308457 / 2108hStored default gateway octet ADefault 192.168.1.1.UINT16Read/write
HR8457doc 308458 / 2109hStored default gateway octet BUINT16Read/write
HR8458doc 308459 / 210AhStored default gateway octet CUINT16Read/write
HR8459doc 308460 / 210BhStored default gateway octet DUINT16Read/write
HR8460doc 308461 / 210ChModbus TCP/IP port1-9999, default 502.UINT16Read/write
HR8461doc 308462 / 210DhDHCP enabledUINT16Read/write0 = DHCP off (default); 1 = DHCP on
HR8462doc 210EhUpdate TCP/IP communication settingsWrite 1 to apply new Ethernet settings (or power-cycle).UINT16Read/write
HR8480doc 308481 / 2120hActual IP address octet AReads 0xFFFF while DHCP has not assigned an address.UINT16Read
HR8481doc 308482 / 2121hActual IP address octet BUINT16Read
HR8482doc 308483 / 2122hActual IP address octet CUINT16Read
HR8483doc 308484 / 2123hActual IP address octet DUINT16Read
HR9471doc 309472 / 24FFhSignature typeUINT16Read0 = 256-bit signature; 1 = 384-bit signature; 2 = No signature
HR16387doc 316388 / 4003hReset total countersWrite 1. Non-certified: totals, Ah, run hours. Certified: Ah and run hours only.UINT16Read/write
HR16388doc 316389 / 4004hReset partial countersWrite 1 to clear partial energy, Ah and run-hour counters.UINT16Read/write
HR20498doc 320499 / 5012hDevice stateBits 11-12: 00 DCM-T OK, 01 warning (over range), 11 failure.BITMAP16Readbit 0 = Voltage over range (beyond ±1150.1 V); bit 1 = Current over range (beyond ±600.1 A); bit 2 = Terminal 1 temperature below -25.1 °C; bit 3 = Terminal 1 temperature above 120.1 °C; bit 4 = Terminal 2 temperature below -25.1 °C; bit 5 = Terminal 2 temperature above 120.1 °C; bit 11 = DCM-T status, low bit; bit 12 = DCM-T status, high bit; bit 13 = Transducer disconnected; bit 14 = Invalid transducer connected; bit 15 = Internal device fault
HR20499doc 320500 / 5013hShunt temperature position 1UINT16× 0.1°CRead
HR20500doc 320501 / 5014hShunt temperature position 2UINT16× 0.1°CRead
HR20736doc 320737 / 5100hCable loss valueCable resistance used to correct energy; max 500.INT32CDABmOhmRead
HR28721doc 328722 / 7031hLocal time deltaOffset from UTC, -1440 to 1440.INT16minRead/write
HR28726doc 328727 / 7036hDisplay charging directionUINT16Read/write0 = Charging vehicle; 1 = Vehicle to grid; 2 = Bidirectional
HR28736doc 328737 / 7040hOCMF commandWrite ASCII 'B' to begin, 'E' to end, 'A' to abort a transaction.UINT16Read/write
HR28741doc 328742 / 7045hCharging statusUINT16Read0 = No charging; 1 = Charging; 2 = End of last transaction; 3 = End of last transaction with error
HR28752doc 328753 / 7050hCharging session end page duration60-300, default 300.UINT16sRead/write
HR28768doc 328769 / 7060hTime synchronization statusUINT16Read0 = Time not synchronized; 1 = Time synchronized
HR28928doc 328929 / 7100hOCMF stateWrite 0 after reading the OCMF file to allow a new session.UINT16Read/write0 = Ready for new transaction; 1 = Running; 2 = Session completed, OCMF file ready; 3 = Session completed with internal error, OCMF file corrupted
HR28929doc 328930 / 7101hOCMF file lengthUINT16wordsRead
HR28930doc 328931 / 7102hOCMF last transaction idUINT32CDABRead
HR31232doc 331233 / 7A00hSession delta kWh+Energy delivered in the current/last charging session.UINT64CDABWhRead
HR31236doc 331237 / 7A04hSession delta kWh-UINT64CDABWhRead
HR31240doc 331241 / 7A08hSession durationUINT64CDABsRead

Notes on this map

Check it against the live device. A register map tells you what the controller can expose; the unit in front of you may differ by firmware or options. Read a few registers and compare them with the unit’s own display; for a 32-bit value the float and byte-order decoder shows all four word orders at once, so a wrong word order or scale is obvious. New to this? Read what a register map is and why addresses are off by one.

Questions about the Carlo Gavazzi DCM1 DC energy meter for EV chargers (Modbus RTU / TCP)

What Modbus registers does the Carlo Gavazzi DCM1 DC energy meter for EV chargers (Modbus RTU / TCP) have?

This map lists 71 registers: 23 input registers, 48 holding registers. 32 of them can be written. Registers vary with firmware, options and configuration, so confirm against the device.

Are the Carlo Gavazzi DCM1 DC energy meter for EV chargers (Modbus RTU / TCP) Modbus addresses 0-based or 1-based?

The manufacturer's document numbers registers Modicon 3xxxx/4xxxx (drop the prefix, subtract 1). Every address on this page is the 0-based wire address you put in the request; the documented number is shown under it where it differs. Rows give a 6-digit Modicon number (3xxxxx for function 04, 4xxxxx for function 03) and the hex physical address that goes in the frame. 300001 / 0000h is wire address 0. Functions 03 and 04 return the same data.

What byte order does the Carlo Gavazzi DCM1 DC energy meter for EV chargers (Modbus RTU / TCP) use for 32-bit values?

Multi-register values in this map use CDAB (low word first (word-swapped)). Set your client to this order for every 32/64-bit value in the table.

What are the minimum Modbus registers to integrate the Carlo Gavazzi DCM1 DC energy meter for EV chargers (Modbus RTU / TCP)?

Start with IR 0 Voltage (DC voltage); IR 2 Current (DC current); IR 4 Power (DC power); IR 16 kWh (+) TOT (Imported energy total); IR 32 kWh (-) TOT (Exported energy total); HR 20498 Device state (Device state / transducer health); HR 28741 Charging status (Charging session status).

How do I enable Modbus control of the Carlo Gavazzi DCM1 DC energy meter for EV chargers (Modbus RTU / TCP)?

RS485 and Ethernet are both active. Serial settings at 2000h-2004h take effect after writing 1 to 2010h; Ethernet settings at 2100h-210Dh after writing 1 to 210Eh or a power cycle.

Where is the official Carlo Gavazzi DCM1 DC energy meter for EV chargers (Modbus RTU / TCP) Modbus documentation?

The source is DCM1 Modbus Communication Protocol - Public version (Version 1.11), revision 2025-07-30, published free by Carlo Gavazzi at https://www.gavazziautomation.com/fileadmin/images/PIM/OTHERSTUFF/COMPRO/DCM1_CPP.pdf.

More Carlo Gavazzi Modbus register maps

Other power & energy meters register maps

All power & energy meters Modbus register maps →

Source: DCM1 Modbus Communication Protocol - Public version · Version 1.11 · rev. 2025-07-30. Register numbers, types, scaling and units are reproduced as published; descriptions are our own.