LS Electric M100 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_model	0	U16	1
inverter_capacity	1	U16	1
inverter_input_voltage	2	U16	1
version	3	U16	0.01
command_frequency	5	U16	0.01	Hz
operation_command	6	U16	1
acceleration_time	7	U16	0.1	sec
deceleration_time	8	U16	0.1	sec
current	9	U16	0.1
output_frequency	10	U16	0.01
output_voltage	11	U16	1
dc_link_voltage	12	U16	1
output_power	13	U16	0.1
operation_status	14	U16	1
fault_trip_information_a	15	U16	1
input_terminal_information	16	U16	1
output_terminal_information	17	U16	1
v1_input	18	U16	1
v2_input	19	U16	1
i_input	20	U16	1
rpm	21	U16	1
fault_trip_information_b	29	U16	1
pid_feedback	30	U16	0.1	%

link settings as documented (unverified): RTU; default 9600 8N1; unit ID 1; FC 03,04,06,16; RS-485 half duplex system. Supports up to 16 connected inverters.

bench facts as documented (unverified)

terminals	RJ45 connector (pin 1: S+, pin 8: S-, pin 7: SG)
A/B polarity	pin 1: S+, pin 8: S-
termination	Terminating resistor selection switch (SW3)
connector	RJ45
isolation	insulated power source from the inverter's power circuit
shield/ground	SG (pin 7)
model register	0x0000
firmware register	0x0003
power	0.1-2.2kW [200V]

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

LS Electric documents a known 'Addressing Decrement' issue where an offset of -1 (decrementing the register address by 1) may be required depending on the Modbus master software/PLC configuration. [source]
confirmed: comms.baud_rates [1200, 2400, 4800, 9600, 19200, 38400] — confirmed by LS M100 Inverter Operation Manual
confirmed: comms.default_baud 9600 — confirmed by LS M100 Inverter Operation Manual (CM03 default is 3: 9600 bps)
confirmed: comms.default_unit_id 1 — confirmed by LS M100 Inverter Operation Manual (CM01 default is 1)
confirmed: physical.connector RJ45 — confirmed by LS M100 Inverter Operation Manual
confirmed: physical.polarity pin 1: S+, pin 8: S- — confirmed by LS M100 Inverter Operation Manual
confirmed: physical.shield_ground SG (pin 7) — confirmed by LS M100 Inverter Operation Manual
confirmed: physical.termination Terminating resistor selection switch (SW3) — confirmed by LS M100 Inverter Operation Manual
confirmed: register_map (inverter_model @ 0, version @ 3, command_frequency @ 5, operation_command @ 6, current @ 9, output_frequency @ 10, fault_trip_information_b @ 29, pid_feedback @ 30) — confirmed by LS M100 Inverter Operation Manual

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.

If your device isn't here, upload its register map. Generation is free, and the connector keeps the rung it earns under testing.

To prove a connector against your own device, order hardware verification. If it doesn't verify, you don't pay.

Platform builders can license the verified library: machine-readable maps, the firmware matrix, API access.