Modbus Protocol

blueplanet 3.0-10.0 TL3

blueplanet 15.0-20.0 TL3
blueplanet 50.0 TL3
Powador 39.0-72.0 TL3
blueplanet 87.0-150 TL3

Application Note
EN-US

Instructions

Modbus Protocol

Table of contents
1 General information..................................................... 3
1.1 Scope ...................................................................... 3
1.2 More information................................................... 3
1.3 Target group ........................................................... 4

2 Configuration ............................................................... 4
2.1 Physical Connection................................................ 4
2.2 GUI Setting ............................................................. 4
2.3 Resricted write acces.............................................. 4

3 Modbus Register Reading & Writing............................. 5

3.1 Function Code......................................................... 5
3.2 Data Types .............................................................. 5
3.3 Modbus TCP ........................................................... 5

4 Register Map................................................................ 6
4.1 Scaling factors......................................................... 6
4.2 SunSpec register map ............................................. 6
4.3 Adress calculation example .................................... 7

5 Register description ..................................................... 8

5.1 Common Block (Device ID001) ............................... 8

6 FAQ.............................................................................. 9

Page ii Modbus Protocol blueplanet 3.0-10.0 TL3 blueplanet 15.0-20.0 TL3 blueplanet 50.0 TL3 Powador
39.0-72.0 TL3 blueplanet 87.0-150 TL3
1 General information

EN-US
1.1 Scope
This document describes the general aspects of the MODBUS protocol of the KACO string inverter series. The inverters
support a subset of data models according to the SunSpec specification. For a detailed description of particular models re-
fer to [8]. In this document the supported subset is highlighted.

Besides that KACO supports some vendor specific models which will be described in [9].

Supported MODBUS protocols (legacy devices with local GUI)

ž Modbus TCP/UDP

Supported MODBUS protocols (new devices with dedicated web interface)

ž Modbus TCP/UDP

Supported Inverter Model

ž blueplanet TL1/TL3 series
ž Powador TL3 series

Supported SW Version
Inverter family Firmware Ver- Supported Models Device ID
sion
Kaco blueplanet V2.02 till 3.1x Read only inverter models 001, 102, 103
3.0 – 10.0 TL3; V3.22 till V3.xy 001, 102, 103, 122, 123
Kaco blueplanet
V4.00 till V 4.xy 001, 102, 103, 122, 123, 112, 113, 129, 130, 135, 136, 160
15.0-20.0 TL3;
Kaco blueplanet V5.00 till V 5.xy 001, 102, 103, 122, 123, 112, 113, 120, 121, 122, 123, 126, 129, 130, 132, 135, 136,
50.0 TL3 160
blueplanet V1.00 till V 1.xy 001, 103, 113, 120, 121, 122, 123, 126, 129, 130, 132, 135, 136, 160
87.0-150TL3 V2.00 till V 2.xy 001, 103, 113, 120, 121, 122, 123, 126, 129, 130, 132, 135, 136, 160
Powador V2.10 till V2.xy Read only inverter models 001, 102, 103
39.0-72.0 TL3 V3.00 till V3.xy 001, 102, 103, 122, 123
V4.00 till V4.xy 001, 102, 103, 122, 123, 112, 113, 129, 130, 135, 136, 160
V5.00 till V5.xy 001, 102, 103, 122, 123, 112, 113, 120, 121, 122, 123, 126, 129, 130, 132, 135, 136,
160
Tab. 1: Supported SW Version

To see all supported models and registers of this software version, see the attached excel charts.

SunSpec-Information-Model-Reference.xlsx

SunSpec-Information-Model-Reference-Kaco.xlsx

1.2 More information

Modbus Organization
[1] http://www.modbus.org

[2] Modbus_Application_Protocol_V1_1b3.pdf

[3] Modbus_Messaging_Implementation_Guide_V1_0b.pdf

SunSpec Specification
[4] http://www.sunspec.org

[5] SunSpec-Alliance-Specification-Common-Models-v1.5.pdf

Modbus Protocol blueplanet 3.0-10.0 TL3 blueplanet 15.0-20.0 TL3 blueplanet 50.0 TL3 Powador 39.0-72.0 Page 3
TL3 blueplanet 87.0-150 TL3
 [6] SunSpec Alliance Specification - Inverter Models v1.1.pdf
EN-US

[7] SunSpec Information Models – 12041.pdf (SunSpec Information Model Specification SunSpec Alliance Interoperability
Specification V1.8)

SunSpec Models
[8] SunSpec-Information-Model-Reference.xlsx

[9] SunSpec-Information-Model-Reference-Kaco.xlsx

1.3 Target group

All activities described in the document may only be carried out by specially trained personnel with the following qualifi-
cations:
ž Knowledge about IP-based network protocols
ž Knowledge of the modbus specifications
ž Knowledge of the SunSpec modbus specifications
ž Education concerning the installation and configuration of IT systems
ž Training in the handling of hazards and risks during the installation and operation of electrical devices and systems.
ž Education concerning the installation and start-up of electrical devices and systems.
ž Knowledge of applicable standards and directives.
ž Knowledge and adherence to this document with all safety notices.

2 Configuration
2.1 Physical Connection
In order to use the MODBUS features the device must be connected to Ethernet, or to a RS485 bus respectively. For more
detailed information, please refer to Operating instruction in chapter “Connecting the interfaces”.

2.2 GUI Setting

It is necessary to activate the MODBUS/SunSpec protocol via the corresponding menus in local GUI or WEBGUI.

The MODBUS/TCP-Port is set to 502 by default.

The write access to the MODBUS registers has to be activated separately in the inverter MODBUS/SunSpec protocol
menu. If not, only read access is permitted for security reasons.

2.3 Resricted write acces

Some SunSpec settings have to be stored permanently on the inverters internal FLASH memory, so they will be persistent
over a power cycle. These settings are orange marked in the models of xy-reference.xls files

NOTE
These values must NOT be written periodically, because this would destroy the inverters internal FLASH
memory. Values which are NOT to be written periodically are marked by a red RW field in the SunSpec
model tables below.

Addr. Off- Block Off- Size Read/ Name Type Units SF Descrip- Value
set set Write tion Range
2 0 1 RW ActCrv Unit16 - - Index of 1-4
active
curve 0=no
active
curve.

Page 4 Modbus Protocol blueplanet 3.0-10.0 TL3 blueplanet 15.0-20.0 TL3 blueplanet 50.0 TL3 Powador 39.0-72.0
TL3 blueplanet 87.0-150 TL3
3 Modbus Register Reading & Writing

EN-US
3.1 Function Code
You can use two following MODBUS function codes.
ž 03 (0x03) Read holding registers
ž 06 (0x06) Write single holding register
ž 16 (0x10) Write multiple holding registers

3.2 Data Types

This MODBUS Protocol DATA Type follows the one of SunSpec Specifications.
ž uint32, uint16, int16
ž string, bitfiled32, enum16
ž NOTE: UDP – For all devices; TCP – For single devices.
ž For more detailed information, please refer to SunSpec Specifications in Chapter “Standard Data Formats”.

3.3 Modbus TCP

3.3.1 Server timeout
A server timeout on a TCP connection, of there is no more active communication between client and server after 5 min-
utes. Therefore a client should close open sockets after a successful Modbus request. The suggested communication flow
looks like this:
1. Client opens TCP socket to Server
2. Client writes Modbus Request to Server
3. Client receives complete Modbus reply from server
4. Client closes TCP socket to Server.
5. Although it is possible to have multiple Modbus request/replies on the same TCP socket, it is recommended to close
any TCP sockets, after all Modbus request/replies have been processed.
6. Otherwise the server will close any open sockets after the 5 minute timeout.

3.3.2 Maximum TCP connections

ž The maximum parallel TCP connection is restricted to 1 for inverter
ž The maximum parallel TCP connection is restricted to 10 for inverter
– All further connections will be rejected until a previous connection is closed by either the client or the server.

3.3.3 Modbus UDP support

Modbus UDP is supported by the inverters.

The Modbus UDP port is the same as the Modbus TCP port (defaults to port 502).

The support for Modbus UDP is restricted to write only Modbus commands. Therefore it has to be assured that Modbus
write access is enabled in the inverter menu. The commands are being processed, but no answer is send to the Modbus
client. Read requests have to be transferred via Modbus TCP.

In Modbus UDP unicast and broadcast write requests are supported by the inverters, For a broadcast request the usual
UDP broadcast address for the underlying subnet is to be used.

For example:
1 Subnetmask: 255.255.255.0
2 IP-Address space: 192.168.1.0
3 Broadcast address: 192.168.1.255

Modbus Protocol blueplanet 3.0-10.0 TL3 blueplanet 15.0-20.0 TL3 blueplanet 50.0 TL3 Powador 39.0-72.0 Page 5
TL3 blueplanet 87.0-150 TL3
 4 Register Map
EN-US

4.1 Scaling factors

“SF” in below table is an abbreviation of “Scaling Factor”. You can calculate a real value of specific address using SF value,
received value via MODBUS and following equation.

{Read Value}={Received value via MODBUS}*10{SF}

Example:
Address offset 29 and 30 mean DC voltage and the DCV-SF value is -1. If a received value via MODBUS is 5042, DC voltage
is as follow.

{DC Voltage}=(5042)*10(-1)=504.2 Volt

The way to use Scale Factor is the same of SunSpec specifications.

4.2 SunSpec register map

The register map must start with the SunSpec ID, indicating that the following registers are Modbus/SunSpec registers.
The base register address is 40001, and has the following representation:
Address Size R/W Name Type Units SF Descrip- Value
Start / End tion Range
40001 40002 2 R SunSpec ID uint32 - - Uniquely 0x53756e5
identifies 3
this as a
SunSPec
Modbus
Map

After this SunSpecID the supported SunSpec models follow one by one. To retrieve the offsets for the supported SunSpec
models in the register map, the headers for each have to be parsed until a specific “END_OF_MAP” model is found. This
model has the following content:
Address Block off- Size R/W Name Type Units SF Descrip- Value
Offsett set tion Range
0 - 1 R SunSpec uint16 - - End of Reg- 0xFFFF
DID ister map
1 - 1 R SunSpec uint16 - - Model 0
Length length

Page 6 Modbus Protocol blueplanet 3.0-10.0 TL3 blueplanet 15.0-20.0 TL3 blueplanet 50.0 TL3 Powador 39.0-72.0
TL3 blueplanet 87.0-150 TL3
4.3 Adress calculation example

EN-US
WARNING! If a device does not contain the same firmware version according to the specification "SunSpec Modbus In-
terface" version, parameters may be called incorrectly. If Modbus-UDP is activated, all connected devices need same
firmware-version.

NOTE: In a Modbus communication robustly constructed against model changes, first all models are read out and then
the register addresses are calculated.
1. Search for the string "Su"nS" -> in the example 40001 [Pos. 1]
2. Advance by the length of the string: i.e. + 2 auf 40003
3. Reading the model names -> 1 [Pos. 2]
4. Reading the model length -> 66 [Pos. 3]
5. Advance to the next model -> 40003 + 2 + 66 = 40071 [Pos. 4]
6. Reading the name (result depends on which models are supported)
7. Reading the length (result depends on which models are supported)
8. Move forward to the next model [Pos. 5]
9. Repeat the procedure to the end. [Pos. 6]
Addr.
40001 „0xxxxxx „Su“ 1 Model ID Start Register Offset

40002 „0xxxxxx „nS“ 1 40003

40003 0x0001 „1“ Model 1 2 103 40071

40004 0x0042 „66" Length 66 3 40086 14

.
? 40123
.
.
.
66 Register
40003+2+66 .
.
4 .

40071 0x00067 „103" Model 103 5

40072 0x00032 „50" Length 50

.
.
Example . 40086 0x186A0 „100000" 100000W
.
50 Register
.
.
.

40123 ? „?" Model ?

.
.
.
.
.

X 0xFFFF
End Model 6
X+1 0x0000

Fig. 1: Address calculation model

Modbus Protocol blueplanet 3.0-10.0 TL3 blueplanet 15.0-20.0 TL3 blueplanet 50.0 TL3 Powador 39.0-72.0 Page 7
TL3 blueplanet 87.0-150 TL3
 This method to enumerate all supported models can be repeated, until the “END_OF_MAP” model with DID 0xFFFF is
EN-US

found.

To retrieve an explicit value from a certain model, the offset of that value has to be added to the models offset retrieved
in the manner above.

5 Register description
NOTE
For a detailed description of particular models / registers refer to SunSpec Models xls.!

NOTE
Again – keep in mind, that when you refer to a specific address in a model you´ve to use the register_ad-
dress – 1 > on the wire!

NOTE
Setting specific functions via model 123
Refer to the Chapter “Specifications” in the device manual. You will find additional explanations of func-
tions there, as well as examples that use sample parameters.

5.1 Common Block (Device ID001)

The register description for “Common Block (DID 001) is only an example may not reflect the current implementation.
Address Block Off- Size R/W Name Type Units SF Descrip- Value
Offset set tion Range
0 - 1 R SunSpec unit16 - - SunSpec 001 (dec)
DID Common
Model
1 - 1 R SunSpec uint16 - - Model 66 (dec)
Length Length
2 0 16 R Manufac- string - - „KACO new
turer energy“
18 16 16 R Model string - - KACO in- e.g.
verter “Powador
name 39.0 TL3”
34 32 8 R Options string - - Data logger e.g.
ID-String “390TL“
42 40 8 R Version string - - The packet e.g.
version of “V2.10”
the cur-
rently in-
stalled
software
50 48 16 R Serial string - - Serial num- e.g.
Number ber set “39.0TL011
during pro- 23456”
duction
process
66 64 1 - Device Ad- uint16 - - Not imple- -
dress mented
67 65 1 R - pad - - Force even 0
alignment

Page 8 Modbus Protocol blueplanet 3.0-10.0 TL3 blueplanet 15.0-20.0 TL3 blueplanet 50.0 TL3 Powador 39.0-72.0
TL3 blueplanet 87.0-150 TL3
6 FAQ

EN-US
Fault Cause
What communication protocol should be used? The SunSpec protocol provided and the KACO extension list
pave the way for dynamic addressing. Update these proto-
cols at regular intervals.
What should I do if the device does not answer? Check whether you can reach the device using a ping (de-
vice address). In the event of a fault, please check the com-
munication line.
Modbus is not displaying the value expected. Check whether you have performed the calculation via the
chosen start address in accordance with the example - Cal-
culation model addresses. Adress calculation example [See
section 4.3} Page 7]
You can obtain a demo tool from our service team that will
assist you in calculating the required register address.

Modbus Protocol blueplanet 3.0-10.0 TL3 blueplanet 15.0-20.0 TL3 blueplanet 50.0 TL3 Powador 39.0-72.0 Page 9
TL3 blueplanet 87.0-150 TL3
Carl-Zeiss-Strasse 1 · 74172 Neckarsulm · Germany · Tel. +49 7132 3818-0 · Fax. +49 7132 3818-703 · [email protected] · www.kaco-newenergy.de
The text and figures reflect the current technical state at the time of printing. Subject to technical changes. No liability for printing errors.
3012902-09-191210