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 confirmed at the hardware-verified rung and at no rung below it.
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 |
|---|
| 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 |
field reports — community-sourced, unverified (checked 2026-06-11)
- Register address offset: Users must use 0-based addressing (subtracting 1 from the documentation's 1-based start addresses) to avoid reading/writing incorrect registers. [source]
- Coil mapping / Alarm trip issue: Writing to the third coil (thinking it is a direction command) actually triggers an external trip command (alarm) on the VFD because of a mismatch/inconsistency in register/coil numbering. [source]
- confirmed: Supports MODBUS/TCP communication protocol with function codes 3, 4, 6, 16 — confirmed by SJ/L-EN Ethernet Communications Module Instruction Manual (HAL1052) [1.2.9]
- confirmed: Physical connectors include RJ45 (marked ETHERNET) and RJ11 (marked SERIAL) with RJ11-to-RJ45 connection to the inverter — confirmed by SJ/L-EN Ethernet Communications Module Instruction Manual (HAL1052)
- confirmed: Requires 24 VDC via terminals marked '+ 24 V -' — confirmed by SJ/L-EN Ethernet Communications Module Instruction Manual (HAL1052)
- confirmed: Terminals are marked 'Power Alm Rly +24V- GNDC CM NC NO' — confirmed by SJ/L-EN Ethernet Communications Module Instruction Manual (HAL1052)
- confirmed: Max read registers is 125 — confirmed by SJ/L-EN Ethernet Communications Module Instruction Manual (HAL1052)
- confirmed: Register map matches 0-based start addresses of 32-bit parameters (e.g., output_frequency_monitor at 3000, run_mode at 8000) — confirmed by SJ/L-EN Ethernet Communications Module Instruction Manual (HAL1052)
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.