Schneider Altivar ATV31/ATV312 drive

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
switching_frequency	3102	U16	0.1	0.1 kHz
maximum_output_frequency	3103	U16	0.1	0.1 Hz
high_speed	3104	U16	0.1	0.1 Hz
low_speed	3105	U16	0.1	0.1 Hz
acceleration	9001	U16	1	s

link settings as documented (unverified): RTU; default 19200 8E1; unit ID 1; FC 03,06,16,43; Modbus format defaults to 8E1. Address range is 1 to 247.

⚠ If Modbus fault management SLL is set to nO, communication control will be inhibited. For safety reasons, inhibition of communication fault should only be used for adjustment or special applications purpose. — Starkest reads only; we never write a control register.

bench facts as documented (unverified)

terminals	RJ45 connector
A/B polarity	Pin 4: D1 Modbus signal, Pin 5: D0 Modbus signal, Pin 8: Common Modbus signal
termination	One 120 Ohm 0.25 W resistor in series with a 1nF 10 V capacitor
connector	RJ45
shield/ground	Connect the cable shielding to the ground of each device.
wiring notes	Type of trunk cable: Shielded cable with 1 twisted pair and at least a third conductor. Maximum length of bus: 1000 m at 19200 bps with Telemecanique TSX CSA••• cable.
max registers/read	29
response timeout	10000 ms
broadcast	supported
protocol notes	Max write registers (FC16): 27 words max. End of frame detected on silence >= 3 characters.
identification notes	Function 43 (16#2B) returns Manufacturer name (Object 1), Device reference (Object 2), and Device version (Object 3).
FC 43 device ID	supported
power	VP (Pin 7) supply for RS232 / RS485 converter or a remote terminal
doc revision	BBV52816 04/2009

generated by gemini:gemini-3.5-flash · harvested from https://www.electrocentr.com.ua/files/documentation/ATV312_Modbus_2009_en (Schneider Electric); 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.