Hitachi SJ100/L100/SJ200/L200 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
output_frequency_monitor	3000	U32BE	0.1
output_current_monitor	3002	U32BE	0.1
rotation_direction_monitor	3004	U32BE	1
pid_feedback_monitor	3006	U32BE	0.01
intelligent_input_terminal_status	3008	U32BE	1
intelligent_output_terminal_status	3010	U32BE	1
scaled_output_frequency_monitor	3012	U32BE	0.001
trip_counter	3158	U32BE	1
error_code_of_trip_1	3160	U32BE	1
error_code_of_trip_2	3162	U32BE	1
error_code_of_trip_3	3164	U32BE	1
output_frequency_setting_from_volume	3198	U32BE	0.01
output_frequency_monitor_l100_sj100	3200	U32BE	0.01
frequency_setpoint_l100_sj100	3202	U32BE	0.01
run_mode	8000	U32BE	1
trip_history_1_time	8004	U32BE	1
trip_history_1_cause	8006	U32BE	1
trip_history_1_frequency	8008	U32BE	1
trip_history_1_current	8010	U32BE	1
trip_history_1_voltage	8012	U32BE	1

link settings as documented (unverified): TCP; FC 03,04,06,16; Supports MODBUS/TCP communication protocol.

bench facts as documented (unverified)

terminals	Power Alm Rly +24V- GNDC CM NC NO
connector	RJ45 Jack (marked ETHERNET), RJ11 Jack (marked SERIAL)
wiring notes	Connects to inverter via RJ11 to RJ45 cable.
max registers/read	125
power	Requires 24 VDC via terminals marked '+ 24 V -'.
doc revision	HAL1052, December 2005

generated by gemini:gemini-3.5-flash · harvested from https://www.hitachi-iesa.com/sites/default/files/supportingdocs/SJL-EN_Instruction_Manual_HAL1052.pdf (Hitachi); 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.