Fuji FRENIC-Ace drive
Register map(s) for this device, with a note of how far each has been checked. Addresses are
0-based, as on the wire. Scale and byte order are confirmed only at the hardware-verified rung.
cross-referenced (demoted: under-extracted stub (<=3 regs); needs re-extraction (#52))
Imported from a third-party source and NOT verified by us — not even structure-checked. An unverified claim, shown so you can find the device; trust it no more than the source it came from.
| point | address (0-based) | type | scale | unit |
|---|
| frequency_reference | 1797 | U16 | 0.01 | Hz |
| operation_command | 1798 | U16 | 1 | |
link settings as documented (unverified): RTU/TCP; default 19200 8N2; unit ID 1; FC 01,03,05,06,08,15,16; Modbus RTU is supported as standard via RS485. Modbus over Ethernet is supported via OPC-PRT option card.
bench facts as documented (unverified)
| terminals | DX+/DX- (port 2) |
| connector | RJ45 (port 1) |
| wiring notes | Wiring to DX+/DX- terminals is recommended as the RJ45 jack is typically reserved for keypad use. |
| max registers/read | 100 |
| protocol notes | Read Coil Status is limited to 80 coils maximum. Read Holding Registers is limited to 100 registers maximum. Force Multiple Coils is limited to 16 coils maximum. Preset Multiple Registers is limited to 100 registers maximum. |
| identification notes | Modbus registers are organized by drive function code group. The hi-byte of the register address is determined by its function code group; the low byte is determined by the drive function code number. |
| doc revision | None |
field reports — community-sourced, unverified (checked 2026-06-11)
- The OPC-PRT3 Multiprotocol Ethernet Interface manual lists S05 (frequency command) as register 1798 and S06 (operation command) as register 1799 due to 1-based addressing, which can cause off-by-one confusion compared to the standard 0-based Modbus RTU addresses of 1797 and 1798. [source]
- confirmed: Baud rates: [2400, 4800, 9600, 19200, 38400] — confirmed by Fuji Electric FRENIC-Ace Modbus Communications Application Note (FECA-AN-183)
- confirmed: Default baud: 19200 — confirmed by FECA-AN-183 (y04/y14 default setting is 3, which corresponds to 19200 bps)
- confirmed: Default unit ID: 1 — confirmed by FECA-AN-183 (y01/y11 default setting is 1)
- confirmed: Framing: RTU, TCP (via OPC-PRT option card) — confirmed by FECA-AN-183
- confirmed: Function codes: [1, 3, 5, 6, 8, 15, 16] — confirmed by FECA-AN-183
- confirmed: Parity: N, Stop bits: 2 — confirmed by FECA-AN-183 (y06/y16 default setting is 0, which corresponds to None parity with 2 stop bits)
- confirmed: Modbus registers are organized by drive function code group. The hi-byte of the register address is determined by its function code group; the low byte is determined by the drive function code number. — confirmed by FECA-AN-183
- confirmed: RJ45 (port 1), DX+/DX- (port 2). Wiring to DX+/DX- terminals is recommended as the RJ45 jack is typically reserved for keypad use. — confirmed by FECA-AN-183
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.
- coherence-checked — Round-trips through a real Modbus stack with no overlapping addresses and a word-order-sensitive codec — the map is internally coherent and wire-decodable. Does NOT prove byte-order or scaling match a real device: the emulator is seeded from the map's own types, so a uniformly wrong byte-order still round-trips. Only hardware-verified confirms byte-order/scale on the wire.
- hardware-verified (software-key) x1 — Matched a real device with operator-attested readings as ground truth — the only rung that confirms word order + scaling on the wire.