ebm-papst EC fan (84/112/150/200 Lite)

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	unit
reset	53248	U16	1
default_set_value	53249	U16	1
operating_hours_counter	53257	U16	1
operating_minutes_counter	53258	U16	1
fan_address	53504	U16	1
maximum_speed	53529	U16	1
maximum_permissible_speed	53530	U16	1
limit_speed	53544	U16	1
maximum_power	53589	U16	1
minimum_sensor_value	53600	F32BE	1
maximum_sensor_value	53602	F32BE	1
reference_dc_link_voltage	53664	U16	0.02	mV
reference_dc_link_current	53665	U16	0.002	mA
actual_speed	53264	U16	1
motor_status	53265	U16	1
warning	53266	U16	1
dc_link_voltage	53267	U16	1
dc_link_current	53268	U16	1
module_temperature	53269	I16	1
motor_temperature	53270	I16	1
interior_electronics_temperature	53271	I16	1
current_direction_of_rotation	53272	U16	1
current_modulation_level	53273	U16	0.0015258789
current_set_value	53274	U16	1
sensor_actual_value	53275	U16	0.00015258789
current_parameter_set	53277	U16	1
current_power	53281	U16	1
sensor_actual_value_1	53283	U16	1

link settings as documented (unverified): RTU; default 19200 8E1; unit ID 1; FC 03,04,06,08,16,67,68,70,80; Maximum telegram length is 23 bytes. ASCII transmission mode is not supported.

bench facts as documented (unverified)

wiring notes	A twisted pair wire with RS485 standard should preferably be used.
max registers/read	9
broadcast	supported
protocol notes	Maximum telegram length is 23 bytes.
model register	D1A5
serial register	D1A2
identification notes	Fan type is stored in D1A5-D1AA. Fan serial number is stored in D1A2-D1A3.
FC 43 device ID	not supported
doc revision	V5.01 Lite

generated by gemini:gemini-3.5-flash · harvested from https://www.ebmpapst.com/content/dam/ebm-papst/loc/europe/gb/modbus-parameter-specifications/MODBUS%20Lite%20Basic%20Functionality%20V5_01.pdf (ebm-papst); 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.