FIMER TRIO-50.0/60.0-TL string inverter

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.

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.

point	address (0-based)	type	scale	unit
remote_on_off	179	U16	1
remove_reset_by_hand_latch_state	180	U16	1
heartbeat_counter	299	U16	1	s
grid_reactive_power	300	F32LE	1	VAr
grid_voltage	302	F32LE	1	V
grid_active_power	304	F32LE	1	W
grid_current	306	F32LE	1	A
global_state	1049	U16	1
alarm_state	1050	U16	1
dc_dc_converter_state	1051	U16	1
dc_ac_converter_state	1052	U16	1
derating_state	1053	U16	1
daily_energy	1069	U32BE	1	Wh
total_energy	1071	U32BE	1	Wh
partial_energy	1073	U32BE	1	Wh
weekly_energy	1075	U32BE	1	Wh
monthly_energy	1077	U32BE	1	Wh
yearly_energy	1079	U32BE	1	Wh
mean_grid_voltage	1089	F32LE	1	V
mean_output_current	1091	F32LE	1	A
output_active_power_instantaneous	1093	F32LE	1	W
output_active_power_absolute_peak	1095	F32LE	1	W
output_active_power_daily_peak	1097	F32LE	1	W
output_active_power_feedback	1099	F32LE	1	W
reactive_power_feedback	1101	F32LE	1	VAr
power_factor_feedback	1103	F32LE	1
mean_grid_frequency	1105	F32LE	1	Hz
active_power_dc_input_1	1107	F32LE	1	W
voltage_dc_input_1	1109	F32LE	1	V
current_dc_input_1	1111	F32LE	1	A
active_power_dc_input_2	1113	F32LE	1	W
voltage_dc_input_2	1115	F32LE	1	V
current_dc_input_2	1117	F32LE	1	A
internal_temperature	1119	F32LE	1	°C
inverter_temperature	1121	F32LE	1	°C
isolation_resistance	1125	F32LE	1	MΩ
max_leakage_current	1127	F32LE	1	A
active_power_dc_input_3	1129	F32LE	1	W
voltage_dc_input_3	1131	F32LE	1	V
current_dc_input_3	1133	F32LE	1	A

link settings as documented (unverified): RTU; default 19200 8N1; FC 03,04,06,16; Interface: RS-485 (half duplex). Byte order: Big-endian. Bit order: LSB sent first. Minimum Timeout: 100ms.

bench facts as documented (unverified)

terminals	RS485-1, RS485-2
wiring notes	Interface: RS-485 (half duplex)
response timeout	100 ms
broadcast	supported
protocol notes	Any Modbus request on 32 bit data type (SF32 and U32) must include both registers otherwise the inverter will trigger an exception with code 2. Any Modbus request on Ascii String must include all registers of the block.
model register	1021
serial register	1008
firmware register	3651
identification notes	Model register is 1021 (Data Address 1022), Serial register is 1008 (Data Address 1009), Firmware registers are 3651-3653 (Data Addresses 3652-3654)
power	Nominal apparent power: 50 kVA / 60 kVA, Nominal Active Power: 50 kW / 60 kW
environment	Ambiente Temperature: <= 50°C (TRIO-50), <= 45°C (TRIO-60)
doc revision	Version Gt03.0, Effective: 31/01/2018 Rev. 3.0
firmware applicability	Minimum inverter update version: 1711C for Europe, 1711D for USA, 1708B for Japan

field reports — community-sourced, unverified (checked 2026-06-11)

For SF32 (Word Swapped Floating Point 32-bit) data types, the two Modbus registers are swapped before processing the IEEE754 floating point. [source]
Reactive Power sign is swapped on Volt-VAr curve configuration through Aurora Manager Lite and Aurora Manager TL (Positive Sign for Under-excited reactive power, Negative Sign for Over-Excited). [source]
confirmed: comms.baud_rates [2400, 4800, 9600, 19200, 38400, 57600, 115200] — confirmed by Fimer Modbus RTU Register Map Version Gt03.0
confirmed: comms.default_baud 19200 — confirmed by Fimer Modbus RTU Register Map Version Gt03.0
confirmed: comms.framing ['RTU'] — confirmed by Fimer Modbus RTU Register Map Version Gt03.0
confirmed: comms.function_codes [3, 4, 6, 16] — confirmed by Fimer Modbus RTU Register Map Version Gt03.0
confirmed: comms.parity 'N' — confirmed by Fimer Modbus RTU Register Map Version Gt03.0
confirmed: comms.stop_bits 1 — confirmed by Fimer Modbus RTU Register Map Version Gt03.0
confirmed: facts.doc_revision 'Version Gt03.0, Effective: 31/01/2018 Rev. 3.0' — confirmed by Fimer Modbus RTU Register Map Version Gt03.0
confirmed: facts.environment 'Ambiente Temperature: <= 50°C (TRIO-50), <= 45°C (TRIO-60)' — confirmed by ABB string inverters TRIO-50.0-TL-OUTD / TRIO-60.0-TL-OUTD-480 datasheet

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.

Device not here? Upload its manual and get a checked map back. It's free.

Want it confirmed against your own device? Order hardware verification. If it doesn't check out, you don't pay.

Building on a lot of devices? License the library — machine-readable maps, the firmware matrix, and API access.