Mitsubishi FR-E800 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 |
|---|
| inverter_reset | 1 | U16 | 1 | |
| parameter_clear | 2 | U16 | 1 | |
| all_parameter_clear | 3 | U16 | 1 | |
| inverter_status_control_extended | 7 | U16 | 1 | |
| inverter_status_control | 8 | U16 | 1 | |
| operation_mode_setting | 9 | U16 | 1 | |
| set_frequency_ram | 13 | U16 | 0.01 | Hz |
| set_frequency_eeprom | 14 | U16 | 0.01 | Hz |
| fault_record_1 | 500 | U16 | 1 | |
link settings as documented (unverified): RTU/TCP; default 19200 8E1; unit ID 0; FC 03,06,08,16,70; Supports MODBUS RTU and MODBUS/TCP. Station number 0 is for broadcast.
⚠ Always set the communication check time interval before starting operation to prevent hazardous conditions. — Starkest reads only; we never write a control register.
bench facts as documented (unverified)
| terminals | PU connector (RJ-45) |
| A/B polarity | RDA, RDB, SDA, SDB |
| termination | Connect a 100 Ohm 1/2 W terminating resistor between RDA (pin 3) and RDB (pin 6) |
| connector | RJ-45 |
| shield/ground | SG (pins 1 and 7) connected to terminal 5 |
| wiring notes | Pins 2 and 8 provide power to the operation panel or parameter unit. Do not use these pins for RS-485 communication. |
| max registers/read | 125 |
| response timeout | 50 ms |
| broadcast | supported |
| protocol notes | No response is returned in the case of broadcast communication. |
| model register | 44001 |
| identification notes | Model name can be read in ASCII code from registers 44001 to 44010. |
| power | Pins 2 and 8 of PU connector provide power to the operation panel or parameter unit. |
field reports — community-sourced, unverified (checked 2026-06-11)
- The FR-E800 contains gaps in holding register allocation at addresses 40011, 40012, and 40013. Attempting continuous block reads across these gaps causes communication failure (e.g., Error Code 7360 on QJ71MB91 module). Workaround: Split block reads into multiple parameter sets (e.g., read 40001-40010 in one block, then 40014-400XX in a second block). [source]
- confirmed: Baud rates [4800, 9600, 19200, 38400, 57600, 76800, 115200] — confirmed by FR-E800 Instruction Manual (Communication) Pr.118 setting range
- confirmed: Default baud rate 19200 — confirmed by FR-E800 Instruction Manual (Communication) Pr.118 initial value of 192
- confirmed: Default unit ID 0 — confirmed by FR-E800 Instruction Manual (Communication) Pr.117 initial value of 0
- confirmed: Framing [RTU, TCP] — confirmed by FR-E800 Instruction Manual (Communication) which details both MODBUS RTU and MODBUS/TCP protocols
- confirmed: Function codes [3, 6, 8, 16, 70] — confirmed by FR-E800 Instruction Manual (Communication) which lists H03, H06, H08, H10, and H46 (70 decimal) as supported
- confirmed: Station number 0 is for broadcast — confirmed by FR-E800 Instruction Manual (Communication) stating that address 0 is broadcast and returns no reply
- confirmed: Parity 'E' and Stop bits 1 — confirmed by FR-E800 Instruction Manual (Communication) Pr.120 default (Even) and Pr.119 default (1 stop bit)
- confirmed: Control warning regarding setting communication check time interval — confirmed by FR-E800 Instruction Manual (Communication) safety warnings
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.