Modbus TCP PM en 2.12-2
Modbus TCP PM en 2.12-2
Solar-Log™
1
Publisher:
Solar-Log GmbH
Fuhrmannstr. 9
72351 Geislingen-Binsdorf
Germany
International support
Tel.: +49 (0)7428/4089-300
e-mail: [email protected]
Contact: https://www.solar-log.com
Italy
Technical support: +39 0471 631032
France
Technical support: +33 97 7909708
Switzerland
Technical support: +41 565 355346
United States
Technical support: +1 203 702 7189
2
Inhaltsverzeichnis
2 Power Management������������������������������������������������������������������������������������������� 5
2.1 PM – Power Control������������������������������������������������������������������������������������������������������������������������������������������� 5
2.2 PM – Data confirmation������������������������������������������������������������������������������������������������������������������������������������ 7
2.3 Change Log��������������������������������������������������������������������������������������������������������������������������������������������������������� 9
3
Solar-Log™ Modbus TCP PM
Note!
A description of the initially used version 1.0 of the Modbus TCP PM interface can be found in
the document „Modbus TCP PM V. 2.7“ on our homepage.
From firmware version 6.xx at the latest, version 1 of the interface can no longer be used.
The purpose of this interface is to communicate with external control devices or communication devices in PV
plants. Active- and Reactive Power commands can be sent to the system via the interface. In the other direction,
plant values can be transmitted to the, for example, energy supplier.
The interface requires a license (Modbus TCP PM, Item no. 255511) and must be configured in the PM area of the
Solar-Log™.
ModbusTCP port:
• 502
Slave ID:
• 1
The functions of the Modbus TCP PM interface have been redesigned in firmware version 3.3.0.
To ensure compatibility of existing applications, the existing functions / register (V1 Power Control and
Data Confirmation) were left as they were designed before. The new functionality is available in a separate register
area
(Power Control V2).
Power Control V2 provides you with all available functions for new developments - the use of the V1 register is no
longer supported.
The Solar-Log™ Modbus implementation uses different byte and word orders. The Modbus protocol byte order
follows the big-endian Modbus specification and is thus compatible with standard Modbus implementations. The-
refore, the higher byte in value is transferred first.
The proprietary-specific register order for 32-bit values uses a little-endian word order. For a 32-bit value, the
lower value word is stored in the first register and the higher value word in the second register.
4
Power Management
2 Power Management
The Modbus registers for Power Management are divided into two regions. First region is for specifying the power
commands like required power reduction or reactive power, second is the return information of current measure-
ment.
Please note, that for most return information in addition a Utility Meter device is necessary. Refresh interval with
Utility Meter is ca. 200 ms. Power commands typically will be executed within less tan a second, depending on
number of inverters and brand.
5
Power Management
WatchDog_Li- % 16bit unsigned 10215 1 4/6 3.3.0 - 5.x Active power limit in
mit* % in case of watchdog
timeout
Utility_connect_ - 16bit unsigned 10216 1 4/6 3.3.0 External utility data validi-
good ty indicator
1=use data from register
10218 to 10234 as utility
meter data
Utility_fQacR VAR 32 bit float 10230 2 4/16 3.3.0 External utility reactive
power (phase 1)
Utility_fQacS VAR 32 bit float 10232 2 4/16 3.3.0 External utility reactive
power (phase 2)
Utility_fQacT VAR 32 bit float 10234 2 4/16 3.3.0 External utility reactive
power (phase 3)
Qref/Pbinst % 32 bit float 10244 2 4/16 6.x Parameter for Q with vol-
tage limiting function
% Pbinst with sign ind/kap.
Range defined by curve
Qref_total VAR 32 bit float 10246 2 4/16 6.x Range defined by curve
Qref_type - 16bit unsigned 10248 1 4/6 6.x Type=0 Reg 10244 is valid
Type=1 Reg 10246 is valid
* In register 10213 a time span in seconds must be set in which the watchdog Register 10211 must be triggered.
Register 10211 must be written cyclically. No signal within the WatchDog Time (10213) triggers the fallback: „Fai-
lure of the remote control“. With firmware 6.xx there is a 2nd watchdog possibility, where the write accesses in all
PM registers are controlled.
6
Power Management
Uac (Phase 1-2) V 16bit unsigned 10518 1 4 Uac (Phase1-2) from Utili-
ty-Meter
7
Power Management
Iac-inverter A*100 32 bit unsigned 10528 2 4 3.1.2 Iac from inverters * 100
23,42A = 2342
Status - 16bit unsigned 10601 1 4/6 6.0.1 1=all inverters are online
Qac Var 32bit signed 10604 2 4/6 6.0.1 QAC measured by inverter
(Sum)
CosPhi cosPhi 16bit signed 10609 1 4/6 6.0.1 cosPhi (calculated by inver-
ter values)
8
Power Management
V1.4:
New addresses: 10513, 10514, 10515, 10516
V1.5:
New addresses: 10006, 10517, 10518, 10519, 10520, 10521, 10523, 10525
Deleted addresses: 10000
V1.6:
Unit Error in address 10513 corrected
V1.7:
New addresses: 10527 and 10528
V2.0:
New adresses: 10200 - 10234
V2.5:
New Note page 4
Description generally adjusted
Headings adjusted page 4
Implemented Modbus functions - Descriptions added page 4
10209 Number Register changed
10205 Description updated
V2.6:
10503 changed to signed
V2.7:
New adresses: 10242 and 10244
10204 Description updated
102015 Firmware updated
V2.8:
10204 Description updated
10213 Description updated
10242 Description updated
Deleted:
Chapter 2.1 (old Version V1)
10210
10517
V2.9:
10209 Description updated
10244 Description updated
V2.10:
10216 Correction
V2.11:
New adresses: 10246 and 10248
V2.12:
New adresses:
10600, 10601, 10602, 10604
10606, 10607, 10609
10528 Number Register changed
9
Solar-Log GmbH The copyright of these instructions remains with the