KEBA KeContact P30 Modbus register map

Device identity

What a tool can read to check that this map fits the connected device (SPEC.md section 4.7). Registers with a role are read like any other register.

Sources and notes

• KeContact P30 Modbus TCP Programmers Guide · version 1.07, 2025-12
  linked in issue #198

Source: KEBA, KeContact P30 Modbus TCP Programmers Guide, V 1.07 (en), 12.2025

• The interface needs a P30 c-series with firmware 3.10.16 or later, or a P30 x-series with software 1.11 or later. DIP switch DSW1.3 on the station must be ON to enable Modbus TCP. The guide says Modbus TCP and the UDP interface must not be used together.
• The guide says the Unit ID must be 255, that only function codes 3 (read) and 6 (write) are supported, and that registers cannot be read in blocks: each value is read on its own, at most 2 registers (one 32-bit value). Registers are numbered from 0 (address_base 0), although the guide adds that some clients need +1.
• Every readable value is a 32-bit unsigned integer in two registers. The guide does not state the word order; big (high word first) is assumed. Check against the display or the serial number if a value looks wrong.
• Write registers hold one 16-bit value, are write-only (the guide marks them wo) and cannot be read back. The guide recommends reading no faster than every 0.5 s and writing no faster than every 5 s.
• Firmware version (1018) is hex-coded in the decimal value (30A0D00 hex is 3.10.14); it has no firmware role because the raw value is not a version string. The guide notes that Modbus TCP version 1.11 numbers this register 1013.
• Product type and features (1016) is a decimal number whose digits give the product type, cable or socket, maximum current, series, meter type and RFID; the digit tables are in the guide. Error code (1006) is a decimal number to be read as hex: the leading hex digit is the error group.
• Written from the manufacturer's document; not tested on a device.