Advantech ADAM-4017+/4018/4019 I/O

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
analog_input_ch0	0	I16	1
analog_input_ch1	1	I16	1
analog_input_ch2	2	I16	1
analog_input_ch3	3	I16	1
analog_input_ch4	4	I16	1
analog_input_ch5	5	I16	1
analog_input_ch6	6	I16	1
analog_input_ch7	7	I16	1

link settings as documented (unverified): RTU; Supported Protocols: ASCII command and Modbus/RTU

bench facts as documented (unverified)

connector	2 x plug-in terminal block (#14 ~ 22 AWG)
isolation	3,000 VDC
wiring notes	Built-in TVS/ESD Protection
protocol notes	Watchdog Timer: System (1.6 second) & Communication
power	Unregulated 10 ~ 30 VDC. Power Consumption: ADAM-4017+: 1.2 W @ 24 VDC; ADAM-4018+: 0.8 W @ 24 VDC; ADAM-4019+: 1.0 W @ 24 VDC
environment	Operating Humidity: 5 ~ 95% RH, Operating Temperature: -10 ~ 70°C (14 ~ 158°F), Storage Temperature: -25 ~ 85°C (-13 ~ 185°F)
accuracy	Voltage mode: ±0.1% or better, Current mode: ±0.2% or better, Resolution: 16-bit, Sampling Rate: 10 sample/second (total), CMR @ 50/60 Hz: 120 dB, NMR @ 50/60 Hz: 100 dB, Span Drift: ±25 ppm/°C (Typical), Zero Drift: ±6 μV/°C
certifications	CE, FCC, RoHS
doc revision	Last updated: 22-Sep-2023

generated by gemini:gemini-3.5-flash · harvested from https://advdownload.advantech.com/productfile/PIS/ADAM-4017+/file/ADAM-4017_4018_4019_DS(092223)20230928142137.pdf (Advantech); manual-faithful — the document's claims, panel risk: LOW — panel concurs, no field disagreements; 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.