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.
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 | unit |
|---|---|---|---|---|
| flow_speed | 30000 | F32BE | 1 | m/s |
| volume_flow | 30002 | F32BE | 1 | m3/s |
| mass_flow | 30004 | F32BE | 1 | kg/s |
| coil_temperature | 30006 | F32BE | 1 | K |
| conductivity | 30008 | F32BE | 1 | S/m |
| diagnosis_value | 30010 | F32BE | 1 | |
| display_channel_1 | 30012 | F32BE | 1 | |
| display_channel_2 | 30014 | F32BE | 1 | |
| operating_time | 30016 | F32BE | 1 | s |
| terminals | D- (Signal A / D0), D (Signal B / D1), C- (Common 0 V), C (Not connected) |
| A/B polarity | D- is Signal A, D is Signal B |
| termination | 120 Ohm / 560 Ohm termination/polarization resistors activated by jumpers X5/X6 |
| connector | Terminals A and B of the converter are dependent on options selected at order |
| isolation | RS485, galvanically isolated |
| shield/ground | Screened twisted pair cable |
| wiring notes | Maximum 1.2 km / 3937 ft without repeater |
| max registers/read | 125 |
| broadcast | supported |
| protocol notes | Address 0 is reserved for broadcast |
| identification notes | Supports Modbus Device Identification (FC43/14) with objects VendorName, ProductCode, MajorMinorRevision, Vendor URL, ProductName, ModelName, UserApplicationName |
| FC 43 device ID | supported |
| doc revision | AD Modbus IFC 300 R02 en |
| firmware applicability | ER 3.2.xx (SW.REV. 3.2x) |
Each rung states what it proved and what it did not. Gray until proven; green is earned by hardware only.
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.