KEB COMBIVERT F5 drive

Register map(s) for this device, each at the trust rung it earned. Addresses are 0-based as on the wire. Word order and scaling are confirmed at the hardware-verified rung and at no rung below it.

interop-verified

Read + decoded cleanly over a real network vs an independent third-party Modbus test server (transport and framing; reads are remapped into the server's register window, so the map's own addresses are NOT exercised). Does NOT prove word order/scaling against the actual device.

point	address (0-based)	type	scale
mdb_prot_cfg	24320	U16	1
mdb_slave_addr_op	24321	U16	1
mdb_map_start_addr_rd	24322	U16	1
mdb_map_start_addr_wr	24323	U16	1
mdb_map_nr_rd	24324	U16	1
mdb_map_nr_wr	24325	U16	1
watchdog_inhibit	24326	U16	1
watchdog_activation	24327	U16	1
mdb_command	24369	U16	1
mdb_mapping_rd_0	24370	U32BE	1
mdb_mapping_wr_0	24470	U32BE	1

link settings as documented (unverified): RTU/ASCII; baud 1200/2400/4800/9600/19200/38400/55500; unit ID 255; FC 03,04,06,16,100,101; ModBus transmission speed is adjusted through parameter SY.07 in the frequency inverter control. Default protocol configuration is ModBus RTU, 8 data bits, even parity, 1 stop bit.

bench facts as documented (unverified)

terminals	SUBD9 (Female) connector X6C
A/B polarity	Pin 4: RS485_RxD(A), Pin 5: RS485_RxD(B), Pin 8: RS485_TxD(A), Pin 9: RS485_TxD(B)
connector	SUBD9 Female
shield/ground	Pin 7: GND (Reference potential of the serial interface)
wiring notes	Supports RS232 or alternatively RS485 transmission standard.
max registers/read	100
broadcast	supported
protocol notes	At KEB functions 3 and 4 are completely identical. Two additional user-defined ModBus functions are supported: 100 (Read Registers32) and 101 (Write Registers32).
identification notes	Operator Type (0180h) and Software date (0182h) are only available via COMBIVIS / diagnosis interface, not via Modbus.
FC 43 device ID	not supported
power	VCC on Pin 6 of SUBD9 connector. Red LED (ERROR) is constantly off if there is no power supply.
doc revision	12/2003 (CM.F5.010-K000)

⚠ disputed: Framing ["RTU", "ASCII"] — disputed by KEB Combicom ModBus Manual Section 3, which states that ModBus ASCII protocol is 'not yet adjustable' (not supported in the firmware)

field reports — community-sourced, unverified (checked 2026-06-11)

confirmed: Document revision 12/2003 (CM.F5.010-K000) — confirmed by KEB Combicom ModBus Manual cover page [1.1.1]
confirmed: Baud rates [1200, 2400, 4800, 9600, 19200, 38400, 55500] — confirmed by KEB Combicom ModBus Manual Section 1.2
confirmed: Default unit ID 255 — confirmed by KEB Combicom ModBus Manual Section 2.1
confirmed: Function codes [3, 4, 6, 16, 100, 101] — confirmed by KEB Combicom ModBus Manual Section 2.3 and 2.4
confirmed: Physical connector SUBD9 Female X6C — confirmed by KEB Combicom ModBus Manual Section 1.1
confirmed: Pinout polarity (Pin 4: RS485_RxD(A), Pin 5: RS485_RxD(B), Pin 8: RS485_TxD(A), Pin 9: RS485_TxD(B)) — confirmed by KEB Combicom ModBus Manual Section 1.1
confirmed: Operator Type (0180h) and Software date (0182h) are not available via Modbus — confirmed by KEB Combicom ModBus Manual Section 3 (Operator Parameters table)
confirmed: Register addresses (mdb_prot_cfg @ 24320, mdb_slave_addr_op @ 24321, mdb_map_start_addr_rd @ 24322, mdb_map_start_addr_wr @ 24323, mdb_map_nr_rd @ 24324, mdb_map_nr_wr @ 24325, watchdog_inhibit @ 24326, watchdog_activation @ 24327, mdb_command @ 24369, mdb_mapping_rd_0 @ 24370, mdb_mapping_wr_0 @ 24470) — confirmed by KEB Combicom ModBus Manual Section 3 (Operator Parameters table)

The trust ladder

Each rung states what it proved and what it did not. Gray until proven; green is earned by hardware only.

generated — A prompt produced it. Unproven — anyone can regenerate this.
structure-verified — Decode path is structurally sound (addresses, widths, finite values). Does NOT prove word order or scaling.
interop-verified — Read + decoded cleanly over a real network vs an independent third-party Modbus test server (transport and framing; reads are remapped into the server's register window, so the map's own addresses are NOT exercised). Does NOT prove word order/scaling against the actual device.
simulator-verified — Decoded correctly against a protocol emulator seeded with known-true values — catches word-order/scaling errors vs the emulator, not the physical device.
hardware-verified x1 — Matched a real device with operator-attested readings as ground truth — the only rung that confirms word order + scaling on the wire.

If your device isn't here, upload its register map. Generation is free, and the connector keeps the rung it earns under testing.

To prove a connector against your own device, order hardware verification. If it doesn't verify, you don't pay.

Platform builders can license the verified library: machine-readable maps, the firmware matrix, API access.