Burkert Type 8619 multiCELL controller

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 only confirmed at the hardware-verified rung.

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
main_board_id	0	U16	1
main_board_module_status	1	U16	1
m1_m3_status	2	U16	1
m4_m6_status	3	U16	1
system_switch	4	U16	1
di1_status	5	U16	1
di2_status	6	U16	1
do1	8	U16	1
do2	9	U16	1
ao1	10	F32BE	1
ao2	12	F32BE	1
di1_frequency	14	F32BE	1
di1_flow	16	F32BE	1
di1_tot_a	18	F32BE	1
di1_tot_b	20	F32BE	1
di2_frequency	22	F32BE	1
di2_flow	24	F32BE	1
di2_tot_a	26	F32BE	1
di2_tot_b	28	F32BE	1
m1_id	32	U16	1
m1_module_status	33	U16	1
pvn1	0	F32BE	1
pvn2	2	F32BE	1
pvn3	4	F32BE	1
pvn4	6	F32BE	1
pvn5	8	F32BE	1
pvc1_status	513	U16	1
pvc1_value	514	F32BE	1
pvc2_status	516	U16	1
pvc2_value	517	F32BE	1
pvc3_status	519	U16	1
pvc3_value	520	F32BE	1

link settings as documented (unverified): TCP; FC 03,04,16,23; Modbus TCP uses a Client/Server access method. The device Type 8619 is a server.

bench facts as documented (unverified)

wiring notes	The data exchange between the device Type 8619 and the other equipment of the network is only possible 25 s after the device start.
protocol notes	The device Type 8619 stores and sends the values of all variables in 'big-endian' format.
identification notes	Identity object (EtherNet/IP) lists Product Code 8619, Vendor ID 87, Product Name multiCELL.
doc revision	Supplement to Operating Instructions 2204/03_EU-ML 00569043 / Original_EN
firmware applicability	from software version B.02.00

generated by gemini:gemini-3.5-flash · harvested from https://www.burkert.com/en/Media/plm/MAN/MA/ma8619-supplement-eu-en.pdf?id=MAN0000000000000001000338748END (Burkert); manual-faithful — the document's claims, panel risk: ELEVATED — panel is not confident; proved interop-verified on 2026-06-10 · recorded 2026-06-10

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.

Have a device that isn't here? Upload its register map — generation is free, and the connector earns its rung by being proven, not claimed.

Need it proven on your own device? Hardware verification — if it doesn't verify, you don't pay.

Building a platform? License the verified library — machine-readable maps, firmware matrix, API access.