Solplanet Ai-Logger 1000 (Modbus TCP for ASW fleet)

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 only confirmed at the hardware-verified rung.

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
sensor1_wind_speed	986	U16	1	m/s
sensor1_irradiance	987	U16	0.1	Watt/m2
sensor1_cell_temperature	988	I16	0.1	°C
sensor1_humidity	991	U16	1	%
inverter_rated_power	1027	U32BE	1	W
inverter_grid_rated_voltage	1300	U16	0.1	V
inverter_grid_rated_frequency	1301	U16	0.01	Hz
inverter_e_today	1302	U32BE	0.1	kWh
inverter_e_total	1304	U32BE	0.1	kWh
inverter_internal_temperature	1310	I16	0.1	℃
inverter_bus_voltage	1316	U16	0.1	V
inverter_pv1_voltage	1318	U16	0.1	V
inverter_pv1_current	1319	U16	0.01	A
inverter_pv2_voltage	1320	U16	0.1	V
inverter_pv2_current	1321	U16	0.01	A
inverter_l1_voltage	1358	U16	0.1	V
inverter_l1_current	1359	U16	0.1	A
inverter_apparent_power	1368	U32BE	1	VA
inverter_active_power	1370	U32BE	1	W
inverter_reactive_power	1372	U32BE	1	Var
inverter_power_factor	1374	I16	0.01
total_active_power	36100	U32BE	1	W
total_reactive_power	36102	U32BE	1	Var
meter_l1_voltage	36104	F32BE	1	Volts
meter_l1_current	36110	F32BE	1	Amps
meter_l1_power	36116	F32BE	1	Watts
meter_total_power	36156	F32BE	1	Watts
meter_frequency	36174	F32BE	1	Hz
meter_import_wh	36176	F32BE	1	kWh/ MWh
meter_export_wh	36178	F32BE	1	kWh/ MWh
active_power_control_command	60000	I16	0.01	%Pn
ac_power_factor_control_command	60001	I16	0.0001
inverter_on_off_control_command	60002	U16	1
active_power_limitation_percentage	60003	U16	0.01	%Pn

link settings as documented (unverified): TCP; unit ID 239; FC 03,04,06,10; Default port is 9999 (customizable), selected port is 502. Slave ID can be 239 (Method 1) or the Modbus 485 RTU address of the inverter (Method 2).

⚠ Third party devices need to continuously communicate with the Modbus TCP every 1~3 seconds. Cannot use single communication and then pause method. If they only need to be read/write once, the correct method of operation is to disconnect the TCP link after the read/write is completed. If TCP is disconnected or timeout occurs, the third-party device should be reconnected after 5 seconds. At the same time, only one device can communicate with Modbus TCP. — Starkest reads only; we never write a control register.

bench facts as documented (unverified)

protocol notes	Third party devices need to continuously communicate with the Modbus TCP every 1~3 seconds. Cannot use single communication and then pause method. If they only need to be read/write once, the correct method of operation is to disconnect the TCP link after the read/write is completed. If TCP is disconnected or timeout occurs, the third-party device should be reconnected after 5 seconds. At the same time, only one device can communicate with Modbus TCP.
model register	1018
serial register	1002
firmware register	1029
identification notes	Model register range 1018-1025, Serial register range 1002-1017, Firmware register range 1029-1035 (Master) and 1036-1042 (Slave).
doc revision	UM0058_Ai-logger Modbus TCP_EN_V03_0424
firmware applicability	Applicable to software versions 003R or above. Method 2 supported by software version 006R or above.

generated by gemini:gemini-3.5-flash · harvested from https://solplanet.net/wp-content/uploads/2024/04/UM0058_Ai-logger-Modbus-TCP_EN_V03_0424.pdf (Solplanet (AISWEI)); manual-faithful — the document's claims, panel risk: LOW — panel concurs, no field disagreements; proved interop-verified on 2026-06-10 · recorded 2026-06-10

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.

Have a device that isn't here? Upload its register map — generation is free, and the connector earns its rung by being proven, not claimed.

Need it proven on your own device? Hardware verification — if it doesn't verify, you don't pay.

Building a platform? License the verified library — machine-readable maps, firmware matrix, API access.