device library

Burkert Type 8619 multiCELL controller

Register map(s) for this device, with a note of how far each has been checked. Addresses are 0-based, as on the wire. Scale and byte order are confirmed only at the hardware-verified rung.

coherence-checked

Round-trips through a real Modbus stack with no overlapping addresses and a word-order-sensitive codec — the map is internally coherent and wire-decodable. Does NOT prove byte-order or scaling match a real device: the emulator is seeded from the map's own types, so a uniformly wrong byte-order still round-trips. Only hardware-verified confirms byte-order/scale on the wire.

pointaddress (0-based)typescaleunit
PVN10F32BE1
ID0U161
Module Status1U161
PVN22F32BE1
M1-M3 Status2U161
M4-M6 Status3U161
PVN34F32BE1
SystemSwitch4U161
DI1 Status5U161
PVN46F32BE1
DI2 Status6U161
Reserved7U161
PVN58F32BE1
DO18U161
DO29U161
PVN610F32BE1
AO110F32BE1mA
PVN712F32BE1
AO212F32BE1mA
PVN814F32BE1
DI1Frequency14F32BE1Hz
PVN916F32BE1
DI1Flow16F32BE1L/min
PVN1018F32BE1
DI1TotA18F32BE1L
PVN1120F32BE1
DI1TotB20F32BE1L
PVN1222F32BE1
DI2Frequency22F32BE1Hz
PVN1324F32BE1
DI2Flow24F32BE1L/min
PVN1426F32BE1
DI2TotA26F32BE1L
PVN1528F32BE1
DI2TotB28F32BE1L
PVN1630F32BE1
Reserved30F32BE1
PVN1732F32BE1
M1 ID32U161
M1 Module Status33U161
PVN1834F32BE1
M1 Reserved34U161
M1 Reserved35U161
PVN1936F32BE1
M1 Reserved36U161
M1 Reserved37U161
PVN2038F32BE1
PVC ID512U161
PVC1 Status513U161
PVC1 Value514F32BE1
PVC2 Status516U161
PVC2 Value517F32BE1
PVC3 Status519U161
PVC3 Value520F32BE1
PVC4 Status522U161
PVC4 Value523F32BE1
PVC5 Status525U161
PVC5 Value526F32BE1
PVC6 Status528U161
PVC6 Value529F32BE1
PVC7 Status531U161
PVC7 Value532F32BE1
PVC8 Status534U161
PVC8 Value535F32BE1
PVC9 Status537U161
PVC9 Value538F32BE1
PVC10 Status540U161
PVC10 Value541F32BE1
PVC11 Status543U161
PVC11 Value544F32BE1
PVC12 Status546U161
PVC12 Value547F32BE1

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 notesThe data exchange between the device Type 8619 and the other equipment of the network is only possible 25 s after the device start.
protocol notesThe device Type 8619 stores and sends the values of all variables in 'big-endian' format.
identification notesIdentity object (EtherNet/IP) lists Product Code 8619, Vendor ID 87, Product Name multiCELL.
doc revisionSupplement to Operating Instructions 2204/03_EU-ML 00569043 / Original_EN
firmware applicabilityfrom software version B.02.00
field reports — community-sourced, unverified (checked 2026-06-11)
  • confirmed: comms framing [TCP], function codes [3,4,16,23] — confirmed by Burkert Type 8619 Industrial Ethernet Supplement (00569043)
  • confirmed: facts doc_revision 'Supplement to Operating Instructions 2204/03_EU-ML 00569043 / Original_EN' — confirmed by Burkert Type 8619 Industrial Ethernet Supplement (00569043)
  • confirmed: facts firmware_applicability 'from software version B.02.00' — confirmed by Burkert Type 8619 Industrial Ethernet Supplement (00569043)
  • confirmed: physical 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.' — confirmed by Burkert Type 8619 Industrial Ethernet Supplement (00569043)
  • confirmed: register map addresses (e.g., pvc1_status @ 513, pvc1_value @ 514) — confirmed by Burkert Type 8619 Industrial Ethernet Supplement (00569043)

The trust ladder

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

Device not here? Upload its manual and get a checked map back. It's free.

Want it confirmed against your own device? Order hardware verification. If it doesn't check out, you don't pay.

Building on a lot of devices? License the library — machine-readable maps, the firmware matrix, and API access.