KACO new energy blueplanet / Powador TL1 and TL3 (SunSpec) Modbus register map
String inverters with Modbus TCP/UDP and RTU using the SunSpec register layout
- Official
- 8 registers
- Modbus TCP and RTU
- Revision 1 · 2026-11-11
- Identity: firmware, serial number
Official: Written from the manufacturer's documentation, but not tested on a device yet. Check the map against the manufacturer's documentation before you write to a live device. Tested it? Report a test.
Communication
- Protocol
- Modbus TCP and RTU
- Unit ID
- 1
- TCP port
- 502
- Serial
- 9600 8E1 · 9600 baud, 8 data bits, even parity, 1 stop bit defaults
- Byte / word order
- ABCD · bytes big-endian, words high first
- Addresses
- 0-based
Connection values are defaults: the device may be configured differently.
Map
- Registers
- 8 holding registers
- Groups
- 1
- Revision
- 1 · 2026-11-11
- Added
- ()
- File
- maps/kaco/blueplanet-tl-sunspec.mbmap.json · 4 KB · history
- SHA-256
- 4e7c7099eaf24cc4d2f93225b2cd494146d8b8ec5ff4dd4f9d3e757357dd7a28
- Manufacturer
- kaco-newenergy.com
Device identity
What a tool can read to check that this map fits the connected device (SPEC.md section 4.7). Registers with a role are read like any other register.
| Role | Register | Address | Type | Values |
|---|---|---|---|---|
| Firmware | Version | holding 40044 | string[8] | |
| Serial number | Serial number | holding 40052 | string[16] |
Sources and notes
- Modbus Protocol Application Note - Tx1 and Tx3 Series · version 180730 Sections 2 to 5; the SunSpec model tables are in SunSpec-Information-Model-Reference-Kaco.xlsx, which is attached to the note and was not available
Source: KACO new energy, Modbus Protocol Application Note, Tx1 and Tx3 Series, version 180730
- The inverters follow the SunSpec specification: the map starts with 'SunS' at register 40001 (address 40000 on the wire), then the common block, then the models the inverter supports one after another until the end model (DID 0xFFFF). The note names models 1, 101/102/103, 111/113, 112, 122, 123, 129, 130, 135, 136 and 160, depending on the software version.
- This map holds only the common block, which the note describes. The position of the inverter model depends on the device and the version: walk the chain (each model's length is in its header) and then use the generic maps in maps/sunspec-alliance/ (inverter 101-103 and 111-113) from the position found. The note's own arithmetic puts the next model at 40069; the specification's 66-register common block puts it at 40071, so read the DID to check.
- Values use SunSpec scale factors: real value = register value x 10^SF. Function 0x03 reads, 0x06 and 0x10 write. Write access has to be enabled in the inverter menu; some settings go to flash and must not be written cyclically.
- Modbus TCP on port 502 (default); older units have TCP/UDP only through the local GUI, newer ones also Modbus RTU on RS485. The unit identifier addresses auxiliary devices such as a string combiner on newer units. Modbus UDP (packet version 4.0 and later) accepts write commands only.
- Supported inverters: blueplanet TL1/TL3 (software V2.02 or higher for TL3, V3.00 for TL1) and Powador TL3 (V2.10 or higher).
| Area | Address | Name | Type | Access | Unit | Scale | Description |
|---|---|---|---|---|---|---|---|
| HR | 40000 | string[2] | R | Reads 'SunS' (0x53756E53) on a SunSpec device | |||
| HR | 40002 | uint16 | R | SunSpec DID, 1 | |||
| HR | 40003 | uint16 | R | 66 | |||
| HR | 40004 | string[16] | R | 'KACO new energy' | |||
| HR | 40020 | string[16] | R | Inverter name, for example 'Powador 39.0 TL3' | |||
| HR | 40036 | string[8] | R | Data logger ID string | |||
| HR | 40044 | string[8] | R | Packet version of the installed software, for example 'V2.10' | |||
| HR | 40052 | string[16] | R | Serial number set in production |
No registers match
Try part of the name, an address (decimal or 0x hex) or clear the filters.
Help improve this map
- I tested it on a deviceReport whether it worked, even if you did not write the map.
- Suggest a correctionEdit the file on GitHub; it opens a pull request.
- Report a problemA wrong address, type, scale or byte order.
- Read the formatWhat each key of the file means (SPEC.md).