Satcom Modbus Manual

Technical Description
SC-COM Modbus Interface
SC-COM-MODBUS-TB-EN-20 | Version 2.0
ENGLISH
Legal Provisions
SMA Solar Technology AG
Legal Provisions
The information contained in these documents is property of SMA Solar Technology AG. Any publication, whether in whole or
in part, requires prior written approval by SMA Solar Technology AG. Internal reproduction used solely for the purpose of
product evaluation or other proper use is allowed and does not require prior approval.
Trademarks
All trademarks are recognized, even if not explicitly identified as such. A lack of identification does not mean that a product or
symbol is not trademarked.
Modbus is a registered trademark of Schneider Electric licensed to the Modbus Organization, Inc.

Sonnenallee 1
34265 Niestetal (Germany)
Germany
Tel. +49 561 9522-0
Fax +49 561 9522-100
www.SMA.de
E-mail: info@SMA.de
2010 to 2014 SMA Solar Technology AG. All rights reserved.
SC-COM-MODBUS-TB-EN-20
Table of Contents
Table of Contents
1
Information on this Document ................................................................. 5
Safety .......................................................................................................... 9
2.1 Intended Use ...............................................................................................................9

2.2 Target Group Qualifications .....................................................................................9
2.3 Advices for Data Security ..........................................................................................9
Product Description .................................................................................10
3.1
3.2
3.3
3.4
3.5
3.6
Modbus Protocol ..................................................................................................... 10

SMA Modbus Profile .............................................................................................. 10
User-Defined Modbus Profile ................................................................................. 10
SMA Modbus Master Profile ................................................................................. 11
Plant Topology ......................................................................................................... 11
Addressing and Data Transmission in Modbus Protocol ................................... 13
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
Unit IDs .................................................................................................................13

Assignment of Modbus Registers to Unit IDs .....................................................14
Modbus Register Address, Register Width and Data Block .............................14
Address Range for Modbus Registers ................................................................14
Data Transmission ................................................................................................14
3.8.1
3.8.2
3.8.3
3.8.4
Data Types and NaN Values .............................................................................17

16 Bit Integer Values ...........................................................................................17
3.7 Reading and Writing Data in Modbus Protocol ................................................. 15

3.8 SMA Data Types ..................................................................................................... 17
3.9 SMA Data Formats .................................................................................................. 18
Commissioning & Configuration ...........................................................20
4.1 Comissioning Steps and Requirements ................................................................. 20

4.2 Plant Detection - Automatic Distribution of the Unit IDs ...................................... 21
4.3 Changing Unit IDs via the Gateway..................................................................... 22
4.3.1
4.3.2
Reading out the Gateway ...................................................................................22

Changing Unit IDs in the Gateway.....................................................................23
4.5.1
Uploading XML Profile-Files ................................................................................25
4.4 Changing Unit IDs with the user interface ............................................................ 24

4.5 Managing XML Profile-Files ................................................................................... 25
Table of Contents
4.5.2
4.5.3
Downloading XML Profile Files ...........................................................................26

Deleting XML Profile Files ....................................................................................26
SMA Modbus Profile Assignment Tables .........................................27
5.1
5.2
5.3
5.4
Information on the Assignment Tables .................................................................. 27

Gateway (Unit ID = 1) ........................................................................................... 28
Plant Parameters (Unit ID = 2) ............................................................................... 29
SMA Devices (Unit ID = 3 to 247) ....................................................................... 30
5.4.1
5.4.2
5.4.3
5.4.4
5.4.5
5.4.6
5.4.7
Device Family SC nnnCP and SC nnnHE-20 .....................................................30

Optiprotect ...........................................................................................................36
Sunny String-Monitor ...........................................................................................39
Sunny Central String-Monitor Controller ............................................................40
Sunny Central String-Monitor-US ........................................................................41
SMA Meteo Station .............................................................................................42
Sunny Sensorbox .................................................................................................43
SMA Modbus Master Profile .................................................................44
6.1 Structure of the XML File for the Modbus Master Profile ................................... 44
6.2 Activating and Deactivating the Modbus Master Profile ................................... 47
6.3 Moxa ioLogik E1242-T Assignment Table ....................................................... 47
User-Defined Modbus Profile ................................................................50
7.1 Structure of the XML File for the User-Defined Modbus Profile ......................... 50
7.2 Example of a user-defined Modbus profile ......................................................... 51
7.3 Activating and Deactivating the User-Defined Modbus Profile......................... 52
Troubleshooting .......................................................................................53
Technical Data .........................................................................................54
9.1
9.2
9.3
9.4
9.5
9.6
9.7
9.8
Supported SMA Devices ........................................................................................ 54

Supported Modbus Devices of other Vendors .................................................... 56
Modbus Communication Ports............................................................................... 56
Modbus Reaction Time ........................................................................................... 57
Interval of Data Request and Number of Values ................................................ 57
Number of SMA Devices ....................................................................................... 57
Numerical Codes of the Time Zones .................................................................... 58
Frequently used Numerical Codes (ENUM) ....................................................... 60
10 Contact ......................................................................................................62
11 Index .........................................................................................................65
4
Information on this Document
1 Information on this Document

Validity
This document is valid for the SMA devices listed in section 9.1 Supported SMA Devices, p. 54. It
describes the variation of the communication protocol Modbus 1 Application Protocol
implemented by SMA, as well as the associated parameters, measured values and data exchange
formats.
This document does not include any information on the software communicating with the Modbus
interface (see instructions of the software manufacturer).
Target Group
This document is for qualified employees. Only persons with corresponding qualifications are
allowed to perform the tasks set forth in this document (see section 2.2 "Target Group
Qualifications", p. 9).
Secondary Information
SMA documents
Additional information is available www.SMASolar.com:
Title of Document
Type of Document
Sunny Central Communication Controller
Operating instructions
Other documents
Title of Document
Source
Service Name and Transport Protocol

Port Number Registry
http://www.iana.org/assignments/service-names-portnumbers/service-names-port-numbers.xml
Modbus Application Protocol

Specification
http://www.modbus.org/specs.php
Modbus is a registered trademark of Schneider Electric and is licensed by the Modbus Organization, Inc.
Symbols
Symbol
Explanation
Indicates information that is important for a specific topic or objective, but is not
safety-relevant.
Prerequisite that has to be met for a specific target.
Desired result.
Possibly occurring problem.
Typographies
Typography
Usage
Bold
File names
Elements that you have to select
Elements at a user interface
Elements that you have to enter
Parameters
Example
Select Settings.
Read the set port in field Port

Enter the value 502 in field
Port
>
Connects several elements that

you have to select
Select Settings > Port
[Button]
Button that you have to select or

click on
Select [Next]
[Source]
Data channel name
Requesting the plant time

(UTC) [SerTm]
Nomenclature
Complete designation
Designation in this document
Photovoltaic plant
PV plant
SMA Modbus Master profile
Modbus Master profile
Sunny Central Communication Controller
SC-COM
Abbreviations and Terms

Abbreviation/ Designation
Explanation
Attribute value
Variable content of an XML attribute, e. g.

attribute=My content
CT
Current measuring unit
Hardware for string monitoring
Device-ID
Numerical value, which identifies a certain

SMA device type, e.g. 155 = Sunny Central
250U.
DWORD
Double word
Data with a width of 32 bit, according to

IEC 61131-3
GFDI
Ground-Fault Detection and

Interruption
Detection of grounding faults and following

disruption of the circuit
Hex
Hexadecimal number
IP
Internet Protocol
Network protocol for connections over the

Internet
MPP
Maximum Power Point
The point on the current-voltage (I-V) curve of

a solar module under illumination, where the
product of current and voltage is maximum
(PMAX, measured in watts).
NaN
Not a number
No valid value is available
PMAX
Active power, maximum value
A device can generated active power up to

this limit
RO
Read Only
Value can only be read
RW
Read/Write
Value can be read and written
SCADA
Supervisory Control and Data

Acquisition
Concept for monitoring and controlling

technical processes; this handbook uses
SCADA as an example for a Modbus master
system.
Term
SMA fieldbus
Interface for communication between SMA

devices (e.g. RS485 or Ethernet). You can find
information on supported communication
interfaces in the data sheets of the SMA
devices.
SMID
Supervised Multiple Input

Device
Technical system in the SMA product

Optiprotect
SMU
String Monitoring Unit
A String Monitoring Unit recognizes, in

cooperation with a Sunny Central StringMonitor Controller, a reduced power or a
breakdown of solar panels (Strings).
Source register
Modbus register that will be assigned to

another Modbus address (target register)
Target register
Modbus register that another Modbus

address (source register) will be assigned to.
The target register is used instead of the
source register for further data processing
UTC
Coordinated Universal Time
VPN
Virtual Private Network
VPN is used to establish a connection from

one private computer network to another. The
point of connection is established on both
sides by what is referred to as a 'VPN
gateway'. In each case the VPN gateway may
be a computer or a router. The connection
itself is described as a VPN tunnel. A secured
data stream runs via the tunnel from one
network to the other, providing VPN nodes
from one network with access to services and
devices of the other network.
WORD
Data with a width of 16 bit, according to

IEC 61131-3
Safety
2 Safety
2.1
Intended Use
The Modbus interface of SC-COM is designed for industrial use and has the following tasks:
Remote control of grid management services of a PV plant.
Remote controlled request of measured values of a PV.
Remote controlled change of parameters of a PV plant.
The Modbus interface can be used with the protocol Modbus TCP, as well as with the protocol
Modbus UDP.
The enclosed documentation is an integral part of this product:
Read and observe this documentation.
Keep this document in a convenient place for future reference.
2.2
Target Group Qualifications
2.3
Advices for Data Security
The activities described in this document must only be performed by qualified persons. Qualified
persons must have the following skills:
Knowledge of IP based network protocols
Training for installation and configuration of IT systems
Knowledge and observance of this document
Data Security in Ethernet networks

You can connect the SC-COM to the Internet. Note that connecting to the Internet carries
the risk that unauthorized users can gain access to and manipulate the data or devices in
the plant.
Take preventive safety measures, e.g.:
Set up a firewall
Close unnecessary network ports
Allow remote access only through a VPN tunnel
Do not install a port forwarding for the used Modbus port
Product Description
3 Product Description
3.1
Modbus Protocol
The Modbus Application Protocol is an industrial communication protocol that is currently mainly
used in the solar sector for plant communication in PV power stations.
The Modbus protocol has been developed for reading data from or writing data to clearly defined
data areas. The Modbus specification does not specify what data is within which data area. This
information must be defined specifically for a device in a so-called Modbus profile. With
knowledge of the specific Modbus profile, a Modbus master (e.g. a SCADA system) can access
the data of a Modbus slave (e.g. SC-COM).
The SMA Modbus profile is the special Modbus profile for SMA devices.
3.2
SMA Modbus Profile
The SMA Modbus profile contains definitions for selected SMA devices. For the definition there was
a reduction of the available data and an assignment to the respective Modbus registers. The SMA
Modbus profile contains for example overall and daily energy, current output, voltages and
currents. The assignment between SMA device data and Modbus addresses is divided into sections
in the SMA Modbus profile that can be addressed by Unit IDs (see section 3.6 Addressing and
Data Transmission in Modbus Protocol, page 13)
In order to enable access to data of an SMA device, a special gateway is required that is provided
by SC-COM.
3.3
User-Defined Modbus Profile
The user-defined Modbus profile allows for reorganising Modbus addresses of the SMA Modbus
profile. The advantage of a reorganisation of Modbus addresses can be e.g. that measured values
and parameters interesting for a special purpose can be placed on continuous Modbus addresses,
one behind the other. These addresses with it can be read and set in one data block.
10
3.4
SMA Modbus Master Profile
3.5
Plant Topology
Product Description
The SMA Modbus Master profile is an extension of the Modbus interface. It is used for accessing
Modbus-able slave devices of other vendors. The Modbus registers of such Modbus devices are
bundled in an assignment table thats named SMA Modbus Master profile. The SMA Modbus
Master profile is stored in the gateway of SC-COM and is accessible under Unit ID = 105. Under
this Unit ID the Modbus registers of the slave devices are accessible for super-ordinate SCADA
systems.
The SMA Modbus profile has been designed for a hierarchical plant structure. This structure
contains the SC-COM as communication device that is equipped with a Modbus TCP/IP and with a
Modbus UDP interface. All other SMA devices that are connected to the
SC-COM via the SMA fieldbus are subordinate to it.
From the perspective of the Modbus protocol, the SC-COM is a Modbus slave that provides a
gateway to SMA devices. The SMA devices can only be addressed using this gateway per Unit ID.
11
Product Description
Examplary plant topology from the perspective of the SMA devices
Line
Explanation
IP network connection between SCADA system and SC-COM (PV plant router)
SMA fieldbus
Logical assignment of SMA device to Unit ID
12
3.6
Product Description
Addressing and Data Transmission in Modbus Protocol
3.6.1 Unit IDs
The Unit ID is a super-ordinate addressing method in Modbus protocol. The SMA Modbus profile
has 247 Unit IDs available of which 245 can be assigned to individual devices. When a device is
assigned to a Unit ID, its parameters and measured values can be accessed.
The following table shows a summary of the Unit IDs in SMA Modbus profile. Individual Unit IDs
and ranges of Unit IDs are reserved and are not used by the automatic plant detection but can be
used when changing manually:
Unit ID
Explanation
This Unit ID is reserved for the gateway of SC-COM.
This Unit ID is reserved for the plant parameters.
This Unit ID is reserved for the inverter, in which SC-COM is built in.
4 to 99
Reserved
100
User-defined Modbus-profile
101 to 104
Reserved
105
Modbus master profile
106 to 109
Reserved
110
Sunny Central String-Monitor Controller, Optiprotect
111 to 119
Reserved
120
SMA Meteo Station, Sunny Sensorbox
121 to 139
Reserved
140 to 189
Sunny String-Monitor, Sunny Central String-Monitor US
190 to 247
Reserved
255
Devices that are assigned to this Unit ID cannot be adressed. You have to assign
these devices to Unit IDs of range 3 to 247 (see section 4.3 Changing Unit IDs
via the Gateway, page 22).
13
Product Description
3.6.2 Assignment of Modbus Registers to Unit IDs
The assignment of parameters and measured values of SMA devices to Modbus register addresses
is realised with assignment tables and accordingly explained in this document (see section 5 SMA
Modbus Profile Assignment Tables, page 27).
The assignment table Gateway (Unit ID = 1) stores the assignments of SMA devices to individual
Modbus registers. The assignment starts with address 42109 and each of it comprises an
address range of 4 Modbus registers, whereby only the register with the Modbus address is
writeable.
The assignment table Plant Parameters (Unit ID = 2) stores parameters and measured values of
SC-COM, as well as of the PV plant.
The assignment tables SMA Devices (Unit ID = 3 to 247) store the parameters and measured
values in separate tables that are used for the individual SMA device families.
3.6.3 Modbus Register Address, Register Width and Data Block
A Modbus register is 16 bits wide. For broader data, connected registers are used and considered
as data blocks. The number of connected Modbus registers is given in the assignment tables. The
address of the first Modbus register of a data block is the start address of the data block.
Moreover, large data blocks can be created.
3.6.4 Address Range for Modbus Registers
The address range 0 to 0xFFFF with 65536 addresses is available for addressing Modbus
registers.
3.6.5 Data Transmission
According to the Modbus specification, only a certain amount of data can be transported in a
simple protocol data unit (PDU) during a data transmission. The data also contains functional
parameters, like e.g. functional code, start address or number of Modbus registers to be
transmitted. The amount of data is depending on the used Modbus command and has to be
considered for data transmission. The allowed number of Modbus registers per command is given
in section 3.7.
Because of the data filing in Motorola format Big-Endian in case of a data transmission first the
high byte and then the low byte of a Modbus register will be transmitted.
14
3.7
Product Description
Reading and Writing Data in Modbus Protocol
The Modbus interface can be used with the protocol Modbus TCP, as well as with the protocol
Modbus UDP. With Modbus TCP the Modbus registers can be read and written (RW), with
Modbus UDP only writing is possible (WO).
The following Modbus commands are supported by the implemented Modbus interface:
Modbus Command
Hexadecimal Value
Amount of Data (Number of

Registers) 2
Read Coils 3
0x01
1 to 2000
Read Holding Registers
0x03
1 to 125
Read Input Registers
0x04
1 to 125
Write Single Register
0x06
Write Multiple Registers
0x10
1 to 123
Read Write Multiple Registers
0x17
Read: 1 to 125, Write: 1 to 121
Reading or writing a single Modbus register

A Modbus exception will be generated if a Modbus register that is not contained in Modbus profile
is accessed or if a Modbus command is erroneous. Just as, Modbus exceptions will be generated if
a read only register is written or a write only register is read.
Reading or Writing Data Blocks
In order to avoid inconsistencies, data blocks of registers belonging together must be read or
written in one step. For example, the 4 bytes of a 64 bit Modbus register have to be read with one
operation into a 64 bit SMA data type.
Writing several Modbus registers as a data block
If several registers are written in a data block (Modbus commands 0x10 and 0x17) and an error
occurs during writing, the next register in the data block will be processed. If data is mutually
dependent or excludes each other a data block will only be processed if it is valid completely.
Otherwise, the complete data block will be rejected. In the event of an error a Modbus exception
will be generated.
2
3
Number of Modbus registers (16 bit) transferable per command as data block
Only available for the SMA Modbus master profile.
15
Product Description
Reading several Modbus registers as a data block

An answer will be returned if a data block is read and at least one register that is defined in the
Modbus profile can be determined in the data blocks data range. If this block moreover contains
Modbus registers that are not defined in Modbus profile, NaN will be generated in each case for
their request values. A request is not valid and a Modbus exception will be generated if none of the
Modbus registers in the data range of a data block is defined in Modbus profile.
Modbus exceptions
Modbus exceptions see specification Modbus Application Protocol Specification, under
http://www.modbus.org/specs.php.
16
3.8
Product Description
SMA Data Types
3.8.1 Data Types and NaN Values
The following table gives the data types used in the SMA Modbus profile and sets them against
possible NaN values. The SMA data types are used in the assignment tables, in the Type column.
They describe the data widths of the assigned values:
Type
Description
NaN value
U16
A word (16 bit/WORD) in the local processor format
0xFFFF
S16
Signed word (16 bit/WORD) in the local processor format
0x8000
U32
A double word (32 bit/DWORD) in the local processor format
0xFFFF FFFF
S32
A signed double word (32 bit/DWORD) in the local processor

format
0x8000 0000
U64
A quad word (64 bit/2 x DWORD) in the local processor

format
0xFFFF FFFF FFFF

FFFF
3.8.2 16 Bit Integer Values
16 bit integers are stored in one Modbus register.

Modbus register
Byte
Bits
8 15
07
32 bit integers are stored in two Modbus registers.

Modbus register
Byte
Bits
24 31
16 23
8 15
07
17
Product Description
64 bit integers are stored in four Modbus registers.

Modbus register
Byte
Bits
56 63
48 55
40 47
32 39
Modbus register
Byte
Bits
24 31
16 23
8 15
07
3.9
SMA Data Formats
The following SMA data formats describe how SMA data have to be interpreted. Data formats are
e. g. important for data display or for further processing. In the assignment tables the SMA data
formats are used in column Format.

Format
Explanation
Duration
Time period
Time in seconds, in minutes or in hours, depending on the Modbus register.
DT
Date/Time
Date/time, in accordance with country setting. Transmission as UTC (seconds since
01/01/1970).
FIX0
Factor 1
Decimal number, commercially rounded, no decimal places.
FIX1
Factor 0.1
Decimal number, commercially rounded, one decimal place.
FIX2
Factor 0.01
Decimal number, commercially rounded, two decimal places.
FIX3
Factor 0.001
Decimal number, commercially rounded, three decimal places.
FW
Firmware version (see Firmware version excursus, below).
RAW
Text or number. A RAW number has no decimal places and no thousand or other
separation indicators.
18
Product Description
ENUM
Coded numerical values. You will find the breakdown of the code in each case
directly under the description of the Modbus register in the assignment tables of the
SMA Modbus profile (see also section 9.8 Frequently used Numerical Codes, page
60).
TEMP
Temperature
Temperature values are given in special Modbus registers in degrees Celsius, in
degrees Fahrenheit or in Kelvin. The values are given commercially rounded with one
decimal place.
Firmware version excursus, format FW: Four values are extracted from the delivered
DWORD. The values Major and Minor are contained BCD coded in bytes 1 and 2. Byte 3
contains the Build value (not BCD coded). The Release type in accordance with the following
table is contained in the 4th byte:
Release
Coded Release
Type
Explanation
No revision number
Experimental release
Alpha release
Beta release
Release
Special release
>5
As number
No special interpretation
Type
Example:
Firmeware version of the product:
Values from DWORD:
1.5.10.R
Major: 1, Minor: 5, Build: 10, Release type: 4
(Hex: 0x1 0x5 0xA 0x4)
19
Commissioning & Configuration
4 Commissioning & Configuration

4.1
Comissioning Steps and Requirements
Requirements:
The devices in the plant have to be connected to the SC-COM and the plant has to be set
into operation (Comissioning see operating instructions of the SC-COM).
Log in on the SC-COM as installer (Logging In and Out of the User Interface see operating
instructions of the SC-COM)
Procedure:
1.
2.
Check the firmware version and if necessary carry out a firmware update (Updating the
firmware see operating instructions of the SC-COM). A firmware update to a newer version
is recommended to enable the SC-COM to support the SMA devices contained in the
included SMA Modbus profile. You can find the required firmware versions in section 9.1
Supported SMA Devices, page 54.
Activate the Modbus server and if necessary, adjust the communication port (Adjusting
network ports see operating instructions of SC-COM).
Distribution of Unit IDs through the activation of the Modbus server
3.
With activating the Modbus server of SC-COM Unit IDs will be assigned to the already
connected SMA devices. The already assigned Unit IDs remain valid when the Modbus
server is deactivated and reactivated again.
Execute plant detection if new devices have been added or if devices have been changed
(see section 4.2 Plant Detection - Automatic Distribution of the Unit IDs, page 21).
4. Change the Unit IDs for the case that new or exchanged devices of the plant cannot be
reached with the Modbus protocol. You can either change the Unit IDs with the Modbus
protocol through the gateway or with the user interface:
With the gateway, see section 4.3 Changing Unit IDs via the Gateway, page 22
With the user interface, see section 4.4 Changing Unit IDs with the user interface,
page 24
5.
6.
20
If necessary, define and activate a user-defined Modbus profile

(see section 7 User-Defined Modbus Profile, page 50)
If necessary, active the SMA Modbus master profile
(see section 6.2 Activating and Deactivating the Modbus Master Profile, page 47)
4.2
Plant Detection - Automatic Distribution of the Unit IDs
For a new PV plant or if other SMA devices are added or replaced, they must be added to the SCCOM. During that process Unit IDs are allocated to the SMA devices (see section 3.6.1 Unit IDs,
page 13):
Plant detection
If the plant is detected once again without any changes being made, existing Unit IDs that
have been assigned will remain valid.
Unit ID after plant detection
During the detection process Unit IDs are assigned to all Modbus capable SMA devices
(possible Unit IDs see 3.6.1 Unit IDs, page 13) If the number of detected devices exceeds
the number of intended Unit IDs for this device type, all devices will be identified with the
Modbus Unit ID = 255 (NaN). These devices can then no longer be addressed and their
measured values and parameters cannot be accessed via the Modbus gateway. You must
change such assignments manually (see section 4.4 "Changing Unit IDs with the user
interface", page 24).
Procedure (plant detection):
1.
Log into the SC-COM user interface as a user or an installer.
1.
Select Data > Detect.

The Plant detection page opens.
Interfaces for plant detection
The SC-COM has different interfaces for the connection with plant devices. If several of the
available interfaces are activated, each interface needs to be detected individually. The
following steps describe the plant detection process for one of those interfaces.
2.
In the Total number of devices to be detected field, enter the number of devices
connected to this SC-COM interface.
3.
Select [Start detection].

The SC-COM starts detecting the devices connected to this interface and displays its
progress. Once all devices connected to this interface have been detected, the SC-COM
displays "### Device detection finished ###".
4.
Select [OK].
21
4.3
Changing Unit IDs via the Gateway
4.3.1 Reading out the Gateway
You can read out the individual Unit IDs of the SMA devices from the gateway.
Accessing the gateway
You access the gateway via the IP address of the SC-COM under the Unit ID = 1.
The assignment of the plant devices to the Unit IDs 3 to 247 is saved in the Modbus registers from
address 42109on. Each assignment has an address range of 4 Modbus registers. You can find the
Modbus registers of the gateway in section 5.2 "Gateway", page 28.
Example Reading an additional device from the gateway
An additionall device was assigned the Unit ID = 120 by the automatic plant detection (in the
following table labelled C in Column Device#). The assignments of the gateway were displayed
with a SCADA system, as follows:
Modbus address
Content
Description
42109
158
Device-ID
42110
2145600972
Serial number
42112
Unit ID
42113
97
Device-ID
42114
2145600320
Serial number
42116
110
Unit ID
42117
232
Device-ID
42118
2145600934
Serial number
42120
120
Unit ID
22
Device #
4.3.2 Changing Unit IDs in the Gateway
You change a Unit ID by writing it to the corresponding Modbus address. To do this all three
Modbus registers belonging to a device-Unit ID-assignment must be transferred in one block of
data, whereby only the register with the Unit ID is writeable. For the following example this means
that all of the three Modbus addresses 42117, 42118 and 42120 have tob e contained in the
data block.
Do not assign duplicate Unit IDs
You must not assign duplicate Unit IDs. If there is a duplicate assignment of a Unit ID, the
device data that is entered in the assignment table of the gateway under the lowest
Modbus address is always read out in the event of a Modbus request of this Unit ID.
Example Changing the Unit ID in the Gateway
The following table shows an example assignment of device to Unit ID. A weather station with
device-ID = 232 and serial number 2145600934 has been detected subsequently as the third
device in the plant. The Unit ID of this device was manually set to 4:
Modbus address
Description
After detection
Modified
42113
Device-ID
232
232
42114
Serial number
2145600934
2145600934
42116
Unit ID
120
23
4.4
Changing Unit IDs with the user interface
Overview:
Show the assignment table in the user interface
Change Unit ID in the assignment table in the user interface
(see section 3.6.1 Unit IDs, page 13)
Checking the Unit IDs automatically
You cannot allocate the same Unit ID twice in a user interface. Only Unit IDs from the valid
range can be assigned. If you have accidentally entered a Unit ID twice or if a Unit ID is not
from the valid range, a warning message will be displayed when saving. You may then
correct and save the entries.
Procedure:
1.
2.
Log into the SC-COM user interface as an installer.

Select Data > Devices > Modbus.
On the page displayed, you can see the section Device with the columns Device ID and
Unit ID.
3.
4.
Enter the required Unit ID in the column Unit ID next to the respective device or profile.
Select [Save].
Warning: data could not be saved. Please check your entry. Any incorrect entries will be
highlighted in red and one of the following information will be displayed next to the field:
"Unit ID is already assigned": Enter another Unit ID
"Unit ID is not within the range (3247)" Use a Unit ID from the range 3 to 247.
The SC-COM displays: "Your data has been successfully saved".
24
4.5
Managing XML Profile-Files
Currently, the following Modbus XML profile files are used by SC-COM:
SMA Modbus Master profile (file name modbusmaster.xml)
(see section 6 "SMA Modbus Master Profile", page 44)
User-defined Modbus profile (file name virtualmodbus.xml)

(see section 7 "User-Defined Modbus Profile", page 50)
In order to activate a Modbus profile, upload a corresponding XML file to the SC-COM and
confirm the activation. Name and content of the XML profile files will be checked when uploading.
If name or content is not valid, an error message will be generated. When deactivating, the
corresponding XML profile file will be deleted from the SC-COM. It is still possible to download
XML profiles.
4.5.1 Uploading XML Profile-Files

1.
2.

On the displayed page, you will see below the section Manage profiles.
3.
Under manage profiles, upload a usable XML file in the field Upload profile and select
[Browse] (usable XML files see above in this section).
4.
Select file *.xml per double click in the open dialogue box.
5.
Select [Upload].
The SC-COM checks the file for validity and displays "Do you really want to apply the
profile?"
The SC-COM checks the file for validity and displays "The settings have not been
activated since the file has an invalid format or invalid entries."
Click on the symbol .
Read the error in the open dialogue window and correct the custom.xml file.
Ensure that the XML file is valid and correct.
6.
Select [Confirm].
The SC-COM says: "The profile has been successfully saved."
25
4.5.2 Downloading XML Profile Files

1.
2.
3.
4.

On the displayed page, you will see below the section Manage profiles. The buttons
behind the profile name will be displayed in grey if no profile is active
Select [Download] behind the corresponding profile.
Select a place to save the file and save.
4.5.3 Deleting XML Profile Files

1.
2.
3.
4.
26

On the displayed page, you will see below the section Manage profiles. The buttons
behind the profile name will be displayed in gray if no profile is active
Select [Delete] behind the corresponding profile.
The SC-COM will ask for a confirmation Confirm file deletion. When a profile file is
deleted the user-defined assignments will get lost. You should download the XML file
before deletion by reasons of security (see section above).
Select [OK].
The profile has been deleted.
SMA Modbus Profile Assignment Tables
5 SMA Modbus Profile Assignment Tables

5.1
Information on the Assignment Tables
The following sections are sorted by Unit ID. Each section contains a table of the Modbus
addresses which can be accessed under the corresponding Unit ID. The tables present the
following information:
Information
Explanation
ADR (DEC)
Decimal Modbus address (see also section 3.6 and following)
Description/Numerical Brief description of the Modbus register and the possible numerical
codes. The name of the SMA data channel is additionally specified in
code(s)
square brackets if available.
CNT
Number of utilized Modbus registers (see also section 3.6 and

following)
Type
Data type, e.g. U32 = 32 bit without algebraic sign (see also section
3.6)
Format
Data format of the stored value, e.g. DT = date, FIX n = output with n
decimal places, TEMP = output as temperature (see also section 3.9)
Access
Access type for Modbus TCP (see section 3.7 Reading and Writing
Data in Modbus Protocol, page 15):
RO: read-only access
RW: read-write access
A Modbus exception will be generated if an access type is not
supported.
27
5.2
Gateway (Unit ID = 1)
In the following table you can find the parameters and measured values provided by the gateway,
which you can access under the Unit ID = 1. Furthermore you will find the assignment of the SMA
devices to the Unit IDs. You can access the gateway under the IP address of the SC-COM:
Assignment of Unit IDs to Devices
The assignment of Unit IDs to devices is restricted to certain Unit ID ranges (see section
3.6.1 Unit IDs, page 13)
Unit ID = 255
(WORD)
Type
Format
Access
30001 Version number of the SMA Modbus profile
U32
RAW
RO
30003 Device ID of the SC-COM
U32
RAW
RO
U32
RAW
RO
U32
RAW
RO
ADR
(DEC)
CNT
For Unit ID = 255, observe section 3.6.1 Unit IDs, page 13.
30007
Description/Numerical code
Modbus data change: Counter value will increase if

data in the profile has changed.
30057 Serial number of the SC-COM
Assignment Unit ID SMA devices (see also section 4.3 Changing Unit IDs via the
Gateway, page 22):
42109 Device 1: Device-ID
U16
RAW
RO
42110 Device 1: Serial number
U32
RAW
RO
42112 Device 1: Unit ID, e.g. 3
U16
RAW
RW
U16
RAW
RO
U32
RAW
RO
U16
RAW
RW
U16
RAW
RO
U32
RAW
RO
U16
RAW
RW
28
5.3
Plant Parameters (Unit ID = 2)
(WORD)
Type
Format
Access
30001 Version number of the SMA Modbus profile
U32
RAW
RO
30003 Device ID of the SC-COM
U32
RAW
RO
U32
RAW
RO
30057 Serial number of the SC-COM [Serial Number]
U32
RAW
RO
30193 Reading the plant time (UTC) [SerTm]
U32
DT
RO
Reading the time zone (UTC).

30195 For possible values, see section 9.7 "Numerical
Codes for Time Zones", page 58.
U32
ENUM
RO
30513 Total yield (Wh) [E-Total]
U64
FIX0
RO
30517 Day yield (Wh) [E-heute]
U64
FIX0
RO
U32
FIX0
RO
30531 Total yield (kWh) [E-Total]
U32
FIX0
RO
30533 Total yield (MWh) [E-Total]
U32
FIX0
RO
U32
FIX0
RO
30537 Day yield (kWh) [E-heute]
U32
FIX0
RO
30539 Day yield (MWh) [E-heute]
U32
FIX0
RO
30775 AC active power across all phases (W) [Pac]
S32
FIX0
RO
40001 Setting of the plant time (UTC) [SerTm]
U32
DT
RW
Selected time zone for the display [TmZn]. For

40003 possible values, see section 9.7 "Numerical Codes
for Time Zones", page 58.
U32
ENUM
RW
ADR
(DEC)
CNT
In the following table you can find the plant parameters which you can access under Unit ID = 2.
The plant parameters represent measured values and parameters of the SC-COM, as well as of the
devices of the PV plant that are connected via Modbus protocol. Parameters like for example time
settings are passed through to the devices of the PV plant by SC-COM. Depending on the device
types the parameters are furtheron processed accordingly. Measured values like for example
energy counters are requested from the devices and provided as accumulated values:
30007
Modbus data change: Counter value will increase if

data in the profile has changed.
29
5.4
SMA Devices (Unit ID = 3 to 247)
5.4.1 Device Family SC nnnCP and SC nnnHE-20
(WORD)
Type
Format
Access
30057 Serial number [Serial Number]
U32
RAW
RO
U32
DT
RO
Reading the time zone (UTC) [TmZn]:

U32
ENUM
RO
Event ID of the current event (number of digits is

30197 limited by the device) [ErrNo]; see also section 8
Troubleshooting, page 53.
U32
FIX0
RO
30199 Time until grid connection attempt (s) [TmsRmg]
U32
Duration
RO
Recommended action [Prio]:

336 = Contact manufacturer
30211
337 = Contact installer
338 = Invalid
U32
ENUM
RO
Grid contactor [GriSwStt]:

30217 51 = Contactor closed
311 = Contactor open
U32
ENUM
RO
30225 Insulation resistance (ohms) [Riso]
U32
FIX0
RO
Status of the key switch [DInKeySwStrStp]:

30227 381 = Stop
569 = Activated
U32
ENUM
RO
Maximum possible continuous active power, fixed

30231 configuration. Can be greater than the nominal
power (W) [Plimit]
U32
FIX0
RO
30233 Permanent active power limitation (W) [Pmax]
U32
FIX0
RO
ADR
(DEC)
CNT
In the following table, you will find the measured values and parameters supported by the
SC nnnCP and SC nnnHE-20 device family, which you can access under the Unit IDs = 3-247 (see
section 3.6.1 Unit IDs, page 13):
30
Operating state [Mode]:

309 = Operation
381 = Stop
455 = Warning
1392 = Error
30241 1393 = Wait for PV voltage
1394 = Wait for AC grid
1480 = "Wait for electricity supplier" operating state
(for regulation 0 %)
1560 = Remote control disconnection active
2383 = Manual restart
U32
ENUM
RO
Error [Error]:
267 = Inverter
30243
1395 = DC section
1396 = AC grid
U32
ENUM
RO
30247 Current event number for manufacturer [ErrNoSma]
U32
FIX0
RO
GFDI relay status [DInGfdi]:

30249 51 = closed
311 = open
U32
ENUM
RO
Restart block status [ManResStt]:

1690 = Fast shut-down
2386 = Overvoltage
2387 = Undervoltage
30251
2388 = Overfrequency
2389 = Underfrequency
2390 = Passive island detection
2490 = Phase Lost Detection
U32
ENUM
RO
DC switch in cabinet [DcSwStt]:

30257 51 = Closed
311 = Open
U32
ENUM
RO
AC switch 1 in cabinet [AcSwStt]:

30261 51 = Closed
311 = Open
U32
ENUM
RO
31
AC switch-disconnector in cabinet [AcDiscon]:

30265 51 = Closed
311 = Open
U32
ENUM
RO
30513 Total yield (Wh) [E-total]
U64
FIX0
RO
U64
FIX0
RO
30521 Operating time (s) [h-On]
U64
Duration
RO
30525 Feed-in time (s) [h-total]
U64
Duration
RO
U32
FIX0
RO
U32
FIX0
RO
30533 Total yield (MWh) [E-Total]
U32
FIX0
RO
U32
FIX0
RO
30537 Day yield (kWh) [E-heute]
U32
FIX0
RO
30539 Day yield (MWh) [E-heute]
U32
FIX0
RO
30541 Operating time (s) [h-on]
U32
Duration
RO
30543 Feed-in time (s) [h-Total]
U32
Duration
RO
30545 Operating time interior fan 1 (s) [CntFanCab1]
U32
Duration
RO
U32
Duration
RO
30549 Operating time heat sink fan (s) [CntFanHs]
U32
Duration
RO
30557 Operating time cabinet heating 2 (s) [CntHtCab2]
U32
Duration
RO
U32
Duration
RO
30769 DC current input (A) [Ipv]
S32
FIX3
RO
30771 DC voltage input (V) [Vpv]
S32
FIX2
RO
30773 DC power input (W) [Ppv]
S32
FIX0
RO
30775 AC active power across all phases (W) [Pac]
S32
FIX0
RO
30789 Grid voltage phase AB (V) [VacL12]
U32
FIX2
RO
30791 Grid voltage phase BC (V) [VacL23]
U32
FIX2
RO
30793 Grid voltage phase CA (V) [VacL31]
U32
FIX2
RO
30795 Grid current (A) [Iac]
U32
FIX3
RO
30797 Grid current L1 (A) [IacL1]
U32
FIX3
RO
32
U32
FIX3
RO
U32
FIX3
RO
30803 Power frequency (Hz) [Fac]
U32
FIX2
RO
30805 Reactive power (var) [Qac]
S32
FIX2
RO
30813 Apparent power 4 (VA) [Sac]
S32
FIX0
RO
30821 Displacement power factor, across all phases [PF]
U32
FIX2
RO
Excitation type of cos [PFExt]:

30823 1041 = Capacitive
1042 = Inductive
U32
ENUM
RO
Operating mode of reactive power regulation [QVArMod]:

303 = Off
1069 = Reactive power/Voltage characteristic curve
Q(U)
1070 = Reactive power Q, direct default setting
1071 = Reactive power const. Q (kvar)
1072 = Reactive power Q, default setting via plant
30825 control
1074 = cos , direct default setting
1075 = cos , default setting via plant control
1076 = cos (P) characteristic curve
1387 = Reactive power Q, default setting via analog
input
1388 = cos , default setting via analog input
1389 = Reactive power/Voltage characteristic curve
Q(U) with hysteresis and deadband
U32
ENUM
RO
30827 Reactive power target value (var) [SpntPwrRt]
S32
FIX0
RO
30829 Reactive power target value (%) [Q-VArNom]
S32
FIX1
RO
Due to internal calculation of the apparent power [Sac] for SC nnnCP it cannot be guaranteed
that this value is available synchronous to the measured values reactive power [Qac] and active
power [Pac].
33
30831 Target value cos [PF-PFSpt]
S32
FIX2
RO
Target value excitation type of cos [PF-PFExtSpt]:

30833 1041 = Capacitive
1042 = Inductive
U32
ENUM
RO
Operating mode of active power limitation [PWMod]:

303 = Off
1077 = Active power limitation P (W)
30835 1078 = Active power limitation P in (%) of PMAX
1079 = Active power limitation P through plant
control
1390 = Active power limitation P via analog inputs
1391 = Active power limitation P via digital inputs
U32
ENUM
RO
30837 Active power target value (W) [P-WSpt]
U32
FIX0
RO
30839 Active power target value (%) [P-WNom]
U32
FIX0
RO
30841 AC voltages (average of all string voltages) (V) [Vac]
U32
FIX2
RO
Operating mode of static voltage-stability for Q at

Night [QoDQ-VArMod]:
303 = Off
1069 = Reactive power/voltage characteristic curve
Q(U)
1070 = Reactive power Q, direct specification
30919
1071 = React. power const. Q in kvar
1072 = Q specified by plant control
1387 = Reactive power Q, specified via analogue
input
1389 = Reactive power/volt. char. Q(U)
parameterised
U32
ENUM
RO
30921
Reactive power setpoint for Q at Night (var)

[QoDQ-VAr]
S32
FIX0
RO
30923
Reactive power setpoint for Q at Night (%)

[QoDQ-VArNom]
S32
FIX1
RO
U64
Duration
RO
U64
Duration
RO
34
34105 Operating time heat sink fan (s) [CntFanHs]
U64
Duration
RO
34109 Heat sink temperature 1 (C) [TmpHs]
S32
TEMP
RO
34113 Interior temperature 1 (C) [TmpCab1]
S32
TEMP
RO
34117 Interior temperature 3 (C) [TmpCab3]
S32
TEMP
RO
34125 External temperature 1 (air supply) (C) [TmpExl1]
S32
TEMP
RO
34141 Operating time interior heater 2 (s) [CntHtCab2]
U64
Duration
RO
S32
TEMP
RO
34613 Total irradiation on sensor surface (W/m) [ExtSolIrr]
U32
FIX0
RO
34637 Analogue current input 1 (mA) [ExtSolIrr]
S32
FIX2
RO
34639 Analogue current input 2 (mA) [ExLAnaInCur]
S32
FIX2
RO
34645 Analogue voltage input 1 (V) [ExLAnaInV1]
S32
FIX2
RO
40001 Setting of the plant time (UTC) [SerTm]
U32
DT
RW
Selected time zone for the display [TmZn].

40003 For possible values, see section "Numerical Codes for
Time Zones", page 58.
U32
ENUM
RW
Operating state [SpntRemEna]:

40009 381 = Stop
569 = Switched on
U32
ENUM
RW
External measurement of the insulation resistance:

40020 303 = Off
308 = On
U32
ENUM
RW
34145
Temperature of the sine-wave filter chokes (C)

[TmpCol]
35
5.4.2 Optiprotect
(WORD)
Type
Format
Access
U32
ENUM
RO
30057 Serial number SMID-CONT [Serial Number]
U32
RAW
RO
30061 Firmware SMID-CONT [Firmware]
U32
FW
RO
30063 Boot loader SMID-CONT [Firmware-2]
U32
FW
RO
30065 Firmware SMID-CT1 [Firmware-3]
U32
FW
RO
30067 Boot loader SMID-CT1 [Firmware-4]
U32
FW
RO
U32
FW
RO
U32
FW
RO
U32
FW
RO
U32
FW
RO
U32
FW
RO
U32
FW
RO
30097 Serial number SMID-CT1 [Serial Number-1]
U32
RAW
RO
U32
RAW
RO
U32
RAW
RO
U32
RAW
RO
U32
DT
RO
Reading the time zone (UTC) [TmZn]:

U32
ENUM
RO
ADR
(DEC)
CNT
In the following table, you will find the measured values and parameters supported by the
Optiprotect, which you can access under the Unit IDs = 3-247 (see section 3.6.1 Unit IDs, page
13).
30051
36
Device class [MainModel]:
8001 = Sensor system general

30197 limited by the device) [ErrNo]; section 8
U32
FIX0
RO
30199 Time until grid connection attempt (s) [TmsRmg]
U32
Duration
RO
Recommended action [Prio]:

336 = Contact manufacturer
30211
337 = Contact installer
338 = Invalid
U32
ENUM
RO
30225 Insulation resistance (ohms) [Riso]
U32
FIX0
RO

309 = Operation
30241
455 = Warning
1392 = Error
U32
ENUM
RO
Error [Error]:
267 = Inverter
30243
1395 = DC section
1396 = AC grid
U32
ENUM
RO
SMID DC switch 1 to 16 [DcSwStt1.1] to

30267 [DcSwStt4.4]:
to
51 = closed
30297 311 = opened
1694 = has triggered
U32
ENUM
RO
Error message SMID DC switch 1 to 16

[DcSwErr1.1] to [DcSwErr4.4]
1508 = 90 % of the DC-switching cycles reached
30331 1509 = 100 % of the DC switching times reached
1695 = DC switch waits for connection
to
30361 1696 = DC switch blocked by spindle
1697 = DC switch manually blocked
1698 = DC switch triggered 3 times
1699 = DC switch defective
U32
ENUM
RO
30771 DC voltage (V) [Vpv]
S32
FIX2
RO
31791 Number of DC current measurement units [CTNoOf]
U32
FIX0
RO
37
31793
to
String current 1 to 32 (A) [Ipv1.1.B] to [Ipv4.4.B]
31855
S32
FIX3
RO
Status of the monitored strings 1 to 32 [DcInStt1.1.B]

to [DcInStt4.4.B]:
307 = OK
467 = DC overvoltage
477 = Reverse current
32057 1492 = String temporarily deselected due to earth
to
fault
32119 1493 = String permanently deselected due to earth
fault
1649 = String x has low power
1650 = Partial string x has low power
1692 = String deactivated due to power reduction
1693 = No string connected
U32
ENUM
RO
40001 Setting of the plant time (UTC in s) [SerTm]
U32
DT
RW
Setting of the time zone [TmZn].

U32
ENUM
RW
U32
ENUM
RW
40011
38
Acknowledgement:
26 = Acknowledge fault
5.4.3 Sunny String-Monitor
(WORD)
Type
Format
Access
30057 Serial number [Seriennummer]
U32
RAW
RO
30245 SMU ID [SSM Identifier]
U32
FIX0
RO
String current of the string 1 of an SMU/SMID (A)

31793
[IString 1]
S32
FIX3
RO
31795

[IString 2]
S32
FIX3
RO
31797

[IString 3]
S32
FIX3
RO
31799

[IString 4]
S32
FIX3
RO
31801

[IString 5]
S32
FIX3
RO
31803

[IString 6]
S32
FIX3
RO
31805

[IString 7]
S32
FIX3
RO
31807

[IString 8]
S32
FIX3
RO
Status of signal contact 1 [Signal contact 1]:

32053 303 = Off
308 = On
U32
ENUM
RO
Status of signal contact 2 [Signal contact 2]:

32055 303 = Off
308 = On
U32
ENUM
RO
ADR
(DEC)
CNT
In the following table, you will find the measured values and parameters supported by the Sunny
String-Monitor, which you can access under the Unit IDs = 3-247 (see section 3.6.1 Unit IDs,
page 13).
39
5.4.4 Sunny Central String-Monitor Controller
(WORD)
Type
Format
Access
U32
RAW
RO

30197 limited by the device); see also section 8
U32
FIX0
RO
Operating state [mode]:

309 = Operation
30241 455 = Warning
1392 = Error
1470 = Fault
U32
ENUM
RO
Error [Error]:
2440 = String-current error (coming)
2441 = Communication error (coming)
30243 2442 = SMU error (WD, EEPROM) (coming)
2443 = String-current error (going)
2444 = Communication error (going)
2445 = SMU error (WD, EEPROM) (going)
U32
ENUM
RO
30521 Operating time (s) [h-On]
U64
Duration
RO
30541 Operating time (s) [h-on]
U32
Duration
RO
31283 PV string current group 1 (A) [MeanCurGr1]
S32
FIX3
RO
S32
FIX3
RO
S32
FIX3
RO
S32
FIX3
RO
S32
FIX3
RO
S32
FIX3
RO
32051 SMU warning code for string error [SSMUWrnCode]
U32
FIX3
RO
ADR
(DEC)
CNT
String-Monitor Controller, which you can access under the Unit IDs = 3-247 (see section 3.6.1
Unit IDs, page 13).
40
5.4.5 Sunny Central String-Monitor-US
(WORD)
Type
Format
Access
U32
RAW
RO

309 = Operation
30241 455 = Warning
1392 = Fault
1470 = Disruption
U32
ENUM
RO
30245 SMU ID [SSMId]
U32
FIX0
RO
ADR
(DEC)
CNT
Central String-Monitor-US, which you can access under the Unit IDs = 3-247 (see section 3.6.1
Unit IDs, page 13).
31793

[CurCh1]
S32
FIX3
RO
31795

[CurCh2]
S32
FIX3
RO
31797

[CurCh3]
S32
FIX3
RO
31799

[CurCh4]
S32
FIX3
RO
31801

[CurCh5]
S32
FIX3
RO
31803

[CurCh6]
S32
FIX3
RO
31805

[CurCh7]
S32
FIX3
RO
31807

[CurCh8]
S32
FIX3
RO
41
5.4.6 SMA Meteo Station
(WORD)
Type
Format
Access
U32
ENUM
RO
Operating status [Stat]:

455 = Warning
30241
1392 = Error
1787 = Initialisation
U32
ENUM
RO
Error [Stat]:
503 = Fault sensor ambient temperature
1006 = Unknown error
1118 = Calibration failed
30243
1835 = Fault sensor module temperature
1836 = Fan life-time reached
1837 = Error in pyranometer
1838 = Pyranometer calibration necessary
U32
ENUM
RO
30521 Operating time (s) [SMA h-On]
U64
Duration
RO
34609 Environment temperature (C) [TmpAmb C]
S32
TEMP
RO
34613 Total irradiation on sensor surface (W/m) [IntSolIrr]
U32
FIX0
RO
34615 Wind speed (m/s) [WindVel m/s]
U32
FIX1
RO
34617 Relative humidity (%) [envhmdt]
U32
FIX2
RO
34619 Air pressure (Pa) [envpress]
U32
FIX2
RO
34621 PV module temperature (C) [TmpMdul C]
S32
TEMP
RO
34625 Environment temperature (F) [TmpAmb F]
S32
TEMP
RO
34627 Environment temperature (K) [TmpAmb K]
S32
TEMP
RO
34629 PV module temperature (F) [TmpMdul F]
S32
TEMP
RO
34631 PV module temperature (K) [TmpMdul K]
S32
TEMP
RO
34633 Wind speed (km/h) [WindVel km/h]
U32
FIX1
RO
34635 Wind speed (mph) [WindVel mph]
U32
FIX1
RO
ADR
(DEC)
CNT
In the following table, you will find the measured values and parameters supported by the SMA
Meteo Station, which you can access under the Unit IDs = 3-247 (see section 3.6.1 Unit IDs,
page 13).
30051
42
5.4.7 Sunny Sensorbox
(WORD)
Type
Format
Access

U32
ENUM
RO
30521 Operating time (s) [SMA h-On]
U64
Duration
RO
34609 Environment temperature (C) [TmpAmb C]
S32
TEMP
RO
34613 Total irradiation on sensor surface (W/m) [IntSolIrr]
U32
FIX0
RO
34615 Wind speed (m/s) [WindVel m/s]
U32
FIX1
RO
34621 PV module temperature (C) [TmpMdul C]
S32
TEMP
RO
U32
FIX0
RO
34625 Environment temperature (F) [TmpAmb F]
S32
TEMP
RO
34627 Environment temperature (K) [TmpAmb K]
S32
TEMP
RO
34629 PV module temperature (F) [TmpMdul F]
S32
TEMP
RO
34631 PV module temperature (K) [TmpMdul K]
S32
TEMP
RO
34633 Wind speed (km/h) [WindVel km/h]
U32
FIX1
RO
34635 Wind speed (mph) [WindVel mph]
U32
FIX1
RO
ADR
(DEC)
CNT
Sensorbox, which you can access under the Unit IDs = 3-247 (see section 3.6.1 Unit IDs, page
13).
30051
34623
Total irradiation on external sensor/pyranometer

(W/m) [ExlSolIrr]
43
6 SMA Modbus Master Profile
With the Modbus master profile Modbus devices (slaves) of other manufacturers can be integrated
in the SC-COM. The Modbus master profile acts like a Modbus device of SMA Solar Technology
AG. It can be obtained via the gateway under the Unit ID = 105 (see section 3.6.1 Unit IDs,
page 13).
The Modbus master profile is a XML file in which per Channel tag one Modbus register of a slave
device is allocated to any Modbus address. For assignment an address range from 0 to 65535 is
available. The stored assignments are requested in regular intervals. The Modbus master profile
currently contains register assignments for the devices "Moxa ioLogik E1242-T" (see section 6.3
"Moxa ioLogik E1242-T", page 47).
6.1
Structure of the XML File for the Modbus Master Profile
The Modbus master profile will be created in the file modbusmaster.xml .

The basic structure of the XML file is as follows:
<?xml version=1.0 encoding=UTF-8?>
<modbus_master_profile>
<channel name="device-register" ip="xxx.xxx.xxx.xxx" port="yyy"
slaveunitid="zzz" source="sss" type="t" size="n"
cycletime="c" destination="d" status="st" quality="q"
signed="m" factor="f" divisor="div" offset="o" />
<!End of instructions-->
</modbus_master_profile>
Legend for XML tags and attributes:
The term "source register" in the following table stands for a specific Modbus register of the slave
device, which is used as source for the assignment.
XML tag or attribute
Explanation
<modbus_master_profile>
</modbus_master_profile>
Within this XML structure, the Modbus master profile is defined.
<channel />
Within every Channel tag, one Modbus master profile is assigned to

a source register of a slave device.
name=device-register
Here you can give any name to the assignment.
44
ip=xxx.xxx.xxx.xxx
IPv4 address of the slave device.
port=yyy
Modbus communication port of the slave device. The default setting

is 502.
slaveunitid=zzz
Unit ID (8 bit) of the slave device. Available Unit IDs for individual
devices are 0 to 247.
source=sss
Decimal address of the source register (see attribute "destination").

You can find possible "source" values in the datasheet of the
manufacturer of the Modbus device.
type=t
Type of source register (Modbus command), possible values:

Coil = Read Coils (0x01)
Holding = Read Holding Registers (0x02)
Input = Read Input Registers (0x03)
For more information about Modbus commands, see section 3.7
Reading and Writing Data in Modbus Protocol, page 15.
size=n
Length of the source register (in WORD) (1 = 16, 2 = 32 or 4 = 64

bit), depending on register type.
Holding or input register: 1, 2, 4
Coil: 1
Depending on the length of the source register (1, 2 or 4 WORD),
the target addresses should be set for the status register and quality
register following the "destination" register, e.g. destination = 1000
(size = 2), "status" = 1002, "quality" = 1003 + 1004, ensuring that
they do not overlap with the following registers.
cycletime=c
Query interval for the source register (standard value is 500). This
value can be indicated for each register. But all source registers will
be requested with the same query interval. The smallest query
interval indicated for a IP address is used. The query interval can be
equal or greater than 100 ms and equal or less than 12 h.
destination=d
Decimal address (0 to 65535) of the Modbus register that the value

has been allocated to (destination register). Observe the length (in
WORD) of the source register (see attribute "size"). The destination
register is followed by a status register and a quality register.
Therefore, the decimal address of the higher destination register must
not be overlapped by the combined length of these three registers.
If the following register overlaps, it becomes incomplete and
Modbus exceptions are generated when it is requested.
45
status=st
Decimal Modbus address (0 to 65535) for the status register (length

= 1 WORD). The status register contains one of the following
information about the destination register:
0 = OK
1 = Initialisation
2 = Invalid type
3 = Reading failed
4 = Writing failed
5 = Not connected
quality=q
Decimal Modbus address (0 to 65534) of the quality register

(length = 2 WORD). In the second WORD, the "quality" register
contains the period of time (ms) between 2 requests of the source
register. The value displayed should deviate only slightly from the set
cycle time. A typical deviation would be 20 ms.
signed=s
Signs of the source register:

0 = Without sign
1 = With sign
factor=f
Multiplier with signs (length = 2 WORD) for scaling the source data.
The default setting is 1.
divisor=div
Divisor with signs (length = 2 WORD) for scaling the source data.
The default setting is 1.
offset=o
Offset value (length = 2 WORD) which shall be added to the source

data. The default setting is 0.

Comments out section xyz, e.g. to deactivate a command.
Modbus exceptions
46
6.2
Activating and Deactivating the Modbus Master Profile
To activate a Modbus master profile, upload the file modbusmaster.xml on the SC-COM.
For deactivating the Modbus master profile you need to delete it. If the Modbus master profile is
deactivated on the SC-COM, only the SMA Modbus profile remains active.
Manage profile files
You will find further information on uploading, downloading and deleting the profile file via
the SC-COM user interface in section 4.5 "Managing XML Profile-Files", page 25.
6.3
Moxa ioLogik E1242-T Assignment Table
In this section you will find a table of the Modbus registers saved in the Modbus master profile for
the "Moxa ioLogik E1242-T". In accordance with the XML structure, each line of the table shows the
attribute of a Modbus registration assignment. The attribute values in the columns "source", "type"
and "size" correspond to the standard values of the "Moxa ioLogik E1242-T".
Changed settings of the Moxa ioLogik E1242-T
If you change the settings (e.g. ip, port, slave Unit ID etc.) of the "Moxa ioLogik E1242-T",
you also have to change the attribute values of the Modbus master profile.
You can find a description of the table columns in the legend to the XML tags in section 6.
Due to lack of space, the following attribute values are not shown in the following table.
ip: current IPv4-address of the "Moxa ioLogik E1242-T"
port: current communication port of the "Moxa ioLogik E1242-T"
factor
divisor
offset
input
1000 1001 1002
Moxa_AI_RAW_Value_2
513
input
1004 1005 1006
Moxa_AI_RAW_Value_3
514
input
1008 1009 1010
Moxa_AI_RAW_Value_4
515
input
1012 1013 1014
Moxa_AI_FLOAT_Value_1
520
input
1016 1018 1019
521
input
1021 1023 1024
522
input
1026 1028 1029
523
input
1031 1033 1034
port
ip
quality
512
status
signed
( )
destination
cycletime
Source
Moxa_AI_RAW_Value_1
Channel/name
type
slaveunitid
size (WORD)
cycle time: 500 ms
47
Moxa_DO_ALL_Values
32
holding
1036 1037 1038
Moxa_DI_ALL_Values
48
input
1040 1041 1042
Moxa_DI_COUNTER_Value
16
input
1044 1046 1047
Moxa_DO_Value_1
coil
2000 3000 4000
Moxa_DO_Value_2
coil
2001 3001 4002
Moxa_DO_Value_3
coil
2002 3002 4004
Moxa_DO_Value_4
coil
2003 3003 4006
Moxa_DI_Value_1
coil
2004 3004 4008
Moxa_DI_Value_2
coil
2005 3005 4010
Moxa_DI_Value_3
coil
2006 3006 4012
Moxa_DI_Value_4
coil
2007 3007 4014
Moxa_DI_Value_5
coil
2008 3008 4016
Moxa_DI_Value_6
coil
2009 3009 4018
Moxa_DI_Value_7
coil
2010 3010 4020
Moxa_DI_Value_8
coil
2011 3011 4022
Moxa_DI_COUNTER_
START_STOP_1
256
coil
2012 3012 4024
Moxa_DI_COUNTER_
START_STOP_2
257
coil
2013 3013 4026
Moxa_DI_COUNTER_
START_STOP_3
258
coil
2014 3014 4028
Moxa_DI_COUNTER_
START_STOP_4
259
coil
2015 3015 4030
Moxa_DI_COUNTER_
START_STOP_5
260
coil
2016 3016 4032
Moxa_DI_COUNTER_
START_STOP_6
261
coil
2017 3017 4034
Moxa_DI_COUNTER_
START_STOP_7
262
coil
2018 3018 4036
Moxa_DI_COUNTER_
START_STOP_8
263
coil
2019 3019 4038
Moxa_DI_COUNTER_
CLEAR_1
272
coil
2020 3020 4040
Moxa_DI_COUNTER_
CLEAR_2
273
coil
2021 3021 4042
Moxa_DI_COUNTER_
CLEAR_3
274
coil
2022 3022 4044
Moxa_DI_COUNTER_
CLEAR_4
275
coil
2023 3023 4046
Moxa_DI_COUNTER_
CLEAR_5
276
coil
2024 3024 4048
Moxa_DI_COUNTER_
CLEAR_6
277
coil
2025 3025 4050
48
Moxa_DI_COUNTER_
CLEAR_7
278
coil
2026 3026 4052
Moxa_DI_COUNTER_
CLEAR_8
279
coil
2027 3027 4054
Moxa_DO_Pulse_1
16
coil
2028 3028 4056
Moxa_DO_Pulse_2
17
coil
2029 3029 4058
Moxa_DO_Pulse_3
18
coil
2030 3030 4060
Moxa_DO_Pulse_4
19
coil
2031 3031 4062
49
7 User-Defined Modbus Profile

You can change the assignment of Modbus addresses by creating a user-defined Modbus profile.
In the user-defined Modbus profile you can reassign the addresses that were predefined in the
SMA Modbus profile to other Modbus addresses. You can use the whole Modbus address range
between 0 and 65535.
The user-defined Modbus profile can be accessed like other devices via the gateway and the
profile has a Unit ID set to 100 by default (see also section 3.6.1 Unit IDs, page 13).
One advantage of the user-defined Modbus profile is that all measured values and parameters,
which are relevant for controlling the plant, can be put on consecutively running Modbus addresses
and hence, can be read or set in one block.
7.1
Structure of the XML File for the User-Defined Modbus Profile
The user-defined Modbus profile is defined in the file virtualmodbus.xml additionally to the SMA
Modbus profile.
The XML file's basic structure looks like this:
<?xml version=1.0 encoding=UTF-8?>
<virtual_modbusprofile>
<channel unitid=aaa source=bbbbb destination=ccccc />
<!End of instructions-->
</virtual_modbusprofile>
Legend for XML tags and attributes:
XML tag or attribute
Explanation
The user-defined Modbus profile is defined within this XML

structure.
<channel />
Within a channel tag, a new Modbus address can be defined in a

Unit ID:
unitid=aaa
Specifies the Unit ID of a device which Modbus addresses have to

be redefined. Available Unit IDs for individual devices are 3 to
247.
50
source=bbbbb
Specifies a Modbus address of a device selected under "unitid"

whose value is to be used as source. Information on the
assignment tables, see section 5).
destination=ccccc
Specifies the new Modbus address from which the value is to be

retrieved (0 to 65535). Consider the number of Modbus registers
that are stored at the initial address. The destination registers must
not overlap. If later on incomplete Modbus registers are retrieved,
a Modbus exception is generated. If register addresses are
retrieved, which don't have values, NaN will be returned.

Comments out section xyz, e.g. to deactivate a command.
Modbus exceptions
7.2
Example of a user-defined Modbus profile
(WORD)
Type
Format
Access
U32
FIX0
RO
30775 AC active power on all line conductors (W) [Pac]
S32
FIX0
RO
Type
Format
Access
S32
FIX3
RO
[IString 1]
CNT
ADR
(DEC)
ADR
31793
CNT
(DEC)
(WORD)
Various registers of the devices stored under the Unit IDs 3 and 140 are to be read as
consecutively running Modbus addresses from address 00000 on. The following tables are
exemplary excerpts from the SMA Modbus profile:
51
31795

[IString 2]
S32
FIX3
RO
31797

[IString 3]
S32
FIX3
RO
The exact structure of the XML file looks like this:

<?xml version="1.0" encoding="utf-8"?>
<channel unitid="3" source="30531" destination="0" />
7.3
Activating and Deactivating the User-Defined Modbus Profile
To activate a user-defined Modbus profile, load the file virtualmodbus.xml on the SC-COM.
To deactivate a user-defined Modbus profile, you have to delete it. Deleting is equivalent to
deactivating. If the user-defined Modbus profile on the SC-COM is deactivated, the user-defined
assignments are lost and only the SMA Modbus profile stays active.
Managing profile files
For further information on uploading and downloading files as well as on deleting the
profile file via the user interface of the SC-COM, refer to section 4.5 Managing XML
Profile-Files, page 25.
52
Troubleshooting
8 Troubleshooting
You can find further information for error analysis of the SMA Modbus profile in section
3.7 Reading and Writing Data in Modbus Protocol, page 15.
For troubleshooting SMA devices use the event numbers provided by the devices under the
Modbus address 30197.
Event numbers of the SMA devices cannot be decoded with the numerical codes
of this document
The event numbers of the SMA devices are device-specific and cannot be decoded with the
numerical codes of this document.
For breakdown of the event numbers of central inverters contact our Service Line (see
section 10 Contact, page 62).
53
Technical Data
9 Technical Data
9.1
Supported SMA Devices

SMA Modbus profile version
Starting with SC-COM firmware version 1.1, the SMA Modbus profile can be updated at
the SC-COM with a separate XML file. The separate XML file has a profile version. With
profile version 1.30 the device-IDs assigned until now will change. Take a look at the profile
version and device-ID at all of the following SMA devices listed hereafter.
This document applies only for the following SMA devices:

Communication device:
Sunny Central Communication Controller (SC-COM) with firmware version 1.0 or higher,
device-ID = 188
Inverters:
Device family SC nnnCP and SC nnnHE-20:
Sunny Central 500CP (firmware version 01.13.07.R or higher), device-ID = 160,
model = 9088. From profile version 1.30 on, device-ID = 122
Sunny Central 500CP-JP (firmware version 01.18.25.R, or higher), device-ID = 253,
Sunny Central 500CP-US (firmware version 01.16.16.R, or higher), device-ID = 262,
Sunny Central 500CP-US 600V (firmware version 01.16.16.R, or higher), deviceID = 271, model = 9221. From profile version 1.30 on, device-ID = 122
Sunny Central 500HE-20 (firmware version 01.15.41.R or higher), device-ID = 202,
model = 9228
54
Technical Data

model = 9227
Sunny Central 850CP (firmware version 01.13.07.R, or higher), device-ID = 254,
model = 9210
String monitoring devices:
Optiprotect (firmware version 1.00 or higher), device-ID = 198, model = 9120. From profile
version 1.30 on, device-ID = 161
Sunny Central String-Monitor Controller (firmware version 1.05 or higher), device-ID = 187,
Sunny Central String-Monitor-US (firmware version 1.04 or higher), device-ID = 190,
Sunny String-Monitor (firmware version 1.04 or higher), device-ID = 171
Weather stations:
SMA Meteo Station (firmware version 1.00 or higher), device-ID = 232, model = 9176
Sunny Sensorbox (firmware version 1.00 or higher), device-ID = 81, model = 9061
55
Technical Data
9.2
Supported Modbus Devices of other Vendors
9.3
Modbus Communication Ports
The Modbus master profile described in this document is valid for the followingModbus-able
devices of other vendors:
Moxa ioLogik E1242-T
The following table shows the factory settings of the supported network ports:
Network protocol
Communication ports,Factory setting
TCP/UDP
502
Use a free communication port

You should only use free communication ports. Generally, the following range of ports is
available: 49152 to 65535.
You can find further information about used ports in the database Service Name and
Transport Protocol Port Number Registry under http://www.iana.org/assignments/servicenames-port-numbers/service-names-port-numbers.xml.
Changing the communication port
If you change the "Modbus-Port" of the SC-COM, you must also change the Modbus port of
a connected Modbus master system. Otherwise, the SC-COM can no longer be accessed
via Modbus protocol.
56
9.4
Technical Data
Modbus Reaction Time
This section contains typical reaction times. The reaction time is the interval within which changes in
value are available in the SMA devices at the Modbus interface of the SC-COM. Consequently,
changes in value can only be displayed in a corresponding or larger interval in a Modbus master
system (e.g. in a SCADA system).
Device Family
Reaction Time (s)
SC nnnCP and SC nnnHE-20
String Monitoring Unit (provides 300

5-minute mean values)
9.5
Interval of Data Request and Number of Values
Limit of data processing capabilities

Due to reasons of system stability the period between data transfers via the Modbus protocol
should be at least 10 seconds, whereby not more than 30 Modbus registers should be transmitted.
This specification is the upper limit for SMA devices connected through the Modbus protocol,
according to section Number of SMA Devices.
9.6
Number of SMA Devices
Recommended number of SMA devices

For performance reasons, we recommend operating approx. 25 SMA devices on the SC-COM
and not to fully utilize the maximum possible number of 50 SMA devices that the SC-COM can
handle.
57
Technical Data
9.7
Numerical Codes of the Time Zones
The following table contains the most important time zones and their numerical codes that are used
in the SMA Modbus profile. With a known location you can find out the numerical code and the
time zone with it. The tables of section 5 SMA Modbus Profile Assignment Tables, page 27,
refer to this time zone table.
City/Country
Code
Time zone
Fidschi, Marshall Islands
9531
UTC+12:00
Adelaide
9513
UTC+09:30
Greenland
9535
UTC-03:00
Abu Dhabi, Muskat

Alaska
Amman
Amsterdam, Berlin, Bern, Rome,

Stockholm, Vienna
9503
9501
9542
UTC+04:00
UTC-09:00
UTC+02:00
Georgetown, La Paz, San Juan

Guadalajara, Mexico City,
Monterrey
UTC-06:00
Guam, Port Moresby
9580
UTC+10:00
Hawaii
9538
UTC-10:00
UTC+01:00
Arizona
9574
UTC-07:00
Asuncion
9594
UTC-04:00
Helsinki, Kiev, Riga, Sofia, Tallin,

Wilna
UTC-04:00
Indiana (East)
Athens, Bucharest, Istanbul

Atlantic (Canada)
Auckland, Wellington
Azores
Baghdad
Baku
Bangkok, Hanoi, Jakarta

Beirut
Belgrade, Bratislava, Budapest,

Ljubljana, Prague
9515
9537
9505
9553
9509
9504
9508
9566
9546
UTC+06:00
UTC+02:00
UTC+12:00
UTC+01:00
Bogot, Lima, Quito
9563
UTC-05:00
Brisbane
9525
UTC+10:00
Brussels, Copenhagen, Madrid,

Paris
Buenos Aires
Canberra, Melbourne, Sydney

Caracas
Casablanca
Cayenne
Chennai, Kolkata, Mumbai, New

Delhi
Chicago, Dallas, Kansas City,
Winnipeg
Chihuahua, La Paz, Mazatlan

Darwin
Denver, Salt Lake City, Calgary
Dublin, Edinburgh, Lisbon, London

Yerevan
58
9527
UTC-03:00
9560
UTC+01:00
9562
UTC-03:00
9507
9564
9585
9593
UTC+10:00
9523
UTC-12:00
Islamabad, Karatschi
Jekaterinburg
Jerusalem
Kabul
Cairo
Cape Verde Islands

Katmandu
Caucasian Standard Time

Krasnoyarsk
Kuala Lumpur, Singapore

Kuwait, Riyardh
Midway Islands, Samoa
UTC-06:00
9587
UTC-07:00
9512
International Date Line (Western)
UTC-03:00
UTC+00:00
9583
9534
UTC+10:00
UTC-04:30
UTC+05:30
9547
9570
Magadan, Solomon Islands, New

Caledonia
9539
9506
Hobart
Yakutsk
UTC+02:00
UTC+09:30
UTC-07:00
UTC+00:00
UTC+04:00
UTC+02:00
UTC+02:00
UTC+04:00
UTC+07:00
9567
9532
Irkutsk
9517
Brasilia
Harare, Pretoria
UTC-01:00
UTC+03:00
UTC-04:00
9584
9578
Astana, Dhaka
9591
9573
9555
9579
9581
9530
9541
9500
9529
9511
9552
9582
9556
9544
9502
UTC-05:00
UTC+08:00
UTC+05:00
UTC+09:00
UTC+05:00
UTC+02:00
UTC+04:30
UTC+02:00
UTC-01:00
UTC+05:45
UTC+04:00
UTC+07:00
UTC+08:00
UTC+03:00
9519
UTC+11:00
Manaus
9516
UTC-04:00
Minsk
9526
UTC+02:00
Central Atlantic
Monrovia, Reykjavk
Montevideo
Moskow, St. Petersburg, Volgograd

Nairobi
Newfoundland
New York, Miami, Atlanta, Detroit,

Toronto
9565
9545
9536
9588
9561
9524
9554
9528
UTC-11:00
UTC-02:00
UTC+00:00
UTC-03:00
UTC+03:00
UTC+03:00
UTC-03:30
UTC-05:00
Technical Data
Novosibirsk
9550
UTC+06:00
Sri Jayawardenepura
9568
UTC+05:30
Osaka, Sapporo, Tokyo
9571
UTC+09:00
Taschkent
9589
UTC+05:00
Nuku'alofa
Pacific (USA, Canada)
Peking, Chongqing, Hongkong,

Urumchi
9572
9558
UTC+13:00
UTC-08:00
9522
UTC+08:00
Perth
9576
UTC+08:00
Port Louis
9586
UTC+04:00
Petropavlovsk-Kamtschatski
Santiago
Sarajevo, Skopje, Warsaw, Zagreb

Saskatchewan
Seoul
9595
9557
9518
9510
9543
UTC+12:00
UTC-04:00
UTC+01:00
UTC-06:00
UTC+09:00
Taipeh
Teheran
9540
Tiflis
Tijuana, Baja California (Mexico)

Ulan-Bator
West.Centr.Africa
9559
9592
9551
Yangon (Rangoon)
Central America
9533
9577
Windhoek
Vladisvostok
9569
9575
9549
9520
UTC+08:00
UTC+03:30
UTC+04:00
UTC-08:00
UTC+08:00
UTC+01:00
UTC+02:00
UTC+10:00
UTC+06:30
UTC-06:00
59
Technical Data
9.8
Frequently used Numerical Codes (ENUM)
The following table provides numerical codes that are frequently used as a functional coding in
data format ENUM. The enumeration(s) column contains the corresponding abbreviations. Due to
the variety of devices, several abbreviations may be specified.
Event Numbers
The event numbers provided by the devices under the Modbus address 30197 are devicespecific. For their breakdown, use the documentation of the respective device. You cannot
decode the event numbers using the numerical codes of this document (see section 8
Troubleshooting, page 53).
Code
Meaning
Enumeration(s)
51
Closed
Cls
276
Instantaneous value
LimFst
295
MPP
Mpp, MPP, Mpp-Betrieb, Mpp-Operation
303
Off
Off
308
On
On
309
Operation
Operation
311
Open
Opn
336
Contact manufacturer
PrioA
337
Contact installer
PrioC
338
Invalid
PrioIna
381
Stop
Stop
455
Warning
Wrn, Disturbance, Stoer, Stoerung, Strung, Warning
461
SMA (manufacturer specification)
973
Not set, NaN
NaN, ---, ----, -----, ------, -------, --------
1041
Capacitive
OvExt, Capacitive
1042
Inductive
UnExt, Inductive
1069
Reactive power/Voltage characteristic Q(U)
VArCtlVol
1070
Reactive power Q, direct default setting
VArCnstNom
1071
Reactive power const. Q (kvar)
VArCnst
1072
Reactive power Q, default setting via plant control
VArCtlCom
1073
Reactive power Q(P)
VArCtlW
1074
cos , direct specification
PFCnst
1075
cos , default setting via plant control
PFCtlCom
1076
cos (P) characteristic curve
PFCtlW
60
Technical Data
1077
Active power limitation P (W)
WCnst
1078
Active power limitation P in (%) of PMAX
WCnstNom
1079
Active power limitation P via plant control
WCtlCom
1387
Reactive power Q, default setting via analog input
VArCnstNomAnIn
1388
cos , default setting via analog input
PFCnstAnIn
1389
Reactive power/Voltage characteristic curve Q(U) with

hysteresis and deadband
VArCtlVolHystDb
1390
Active power limitation P via analog input
WCnstNomAnIn
1391
Active power limitation P via digital inputs
WCnstNomDgIn
1392
Error
Flt
1393
Wait for PV voltage
WaitPV
1394
Wait for valid AC grid
WaitGri
1395
DC range
DcDm
1396
AC grid
Gri
1455
Emergency Stop
EvtEmgStop
1466
Waiting
Wait
1467
Starting
Str
1468
MPP search
MppSrch
1469
Shut-down
Shtdwn
1470
Fault
Dst
1471
Warning/Error mail OK
EvtWrnErrTxOk
1472
Warning/Error mail not OK
EvtWrnErrTxNok
1473
Plant information mail OK
EvtPlntDatTxOk
1474
Plant information mail not OK
EvtPlntDatTxNok
1475
Error mail OK
EvtErrTxOk
1476
Error mail not OK
EvtErrTxNok
1477
Warning mail OK
EvtWrnTxOk
1478
Warning mail not OK
EvtWrnTxNok
1479
Wait after grid interruption
GriFltMon
1480
Wait for electricity supplier
WaitUtil
61
Contact
10 Contact
If you have technical problems concerning our products, contact the SMA Service Line. We need
the following information in order to provide you with the necessary assistance:
Used Modbus master software or hardware

Software version of the SC-COM
Type of communication interface between the SC-COM and the devices
Type, serial numbers, and software version of the devices connected to the PV plant
Australia
SMA Australia Pty Ltd.

Sydney
Toll free for

Australia:
1800 SMA AUS

(1800 762 287)
International:
+61 2 9491 4200
Belgien/Belgique/Belgi
SMA Benelux bvba/sprl

Mechelen
+32 15 28 67 30
esko
SMA Central & Eastern Europe s.r.o.
+420 235 010 417
Danmark
SE Deutschland (Tyskland)
Deutschland

Niestetal
Praha
Medium Power Solutions

Wechselrichter:
Kommunikation:
SMS mit
Rckruf:
+49 561 9522-1499

+49 561 9522-2499
+49 176 888 222 44
Hybrid Energy Solutions

Sunny Island:
+49 561 9522-399
Power Plant Solutions

Sunny Central:
Espaa
62
SMA Ibrica Tecnologa Solar, S.L.U.
Barcelona
+49 561 9522-299
+34 900 14 22 22
France
Contact
SMA France S.A.S.

Lyon
Medium Power Solutions

Onduleurs :
Communication :
+33 (0)4 72 09 04 40
+33 (0)4 72 09 04 41
Hybrid Energy Solutions

Sunny Island :
+33 (0)4 72 09 04 42
Power Plant Solutions

Sunny Central :
+33 (0)4 72 09 04 43
India
SMA Solar India Pvt. Ltd.

Mumbai
+91 022 61713844
Italia
SMA Italia S.r.l.

Milano
+39 02 89347 299
Luxemburg/Luxembourg
Siehe Belgien
Voir Belgien (Belgique)
Magyarorszg
lsd esko (Csehorszg)
Nederland
zie Belgien (Belgi)
sterreich
Siehe Deutschland
Polska
Patrz esko (Czechy)
Portugal
SMA Solar Technology Portugal, +351 212377860

Unipessoal Lda, Lisboa
Romnia
Vezi esko (Cehia)
Schweiz
Siehe Deutschland
Slovensko
pozri esko (esk republika)
South Africa
SMA Solar Technology

South Africa Pty Ltd.
Centurion (Pretoria)
Toll free
worldwide:
United Kingdom
SMA Solar UK Ltd.

Milton Keynes
+44 1908 304899
SMA Hellas AE
+30 210 9856 666
()
+27 12 643 1785
63
Contact
SMA Solar (Thailand) Co., Ltd.
+66 2 670 6999
SMA Technology Korea Co., Ltd.
+82 2 508 8599
SMA Beijing Commercial

Company Ltd.
+86 010 56701361
SMA Japan K.K.
+81-(0)3-3451-9530
+971 2 698 5080
Other countries
64
SMA Middle East LLC
International SMA Service Line

Niestetal
Toll free worldwide: 00800 SMA SERVICE

(+800 762 7378423)
11 Index
0
0x01 .................................................... 15, 45

0x02 ........................................................... 45
0x03 .................................................... 15, 45
0x04 ........................................................... 15
0x06 ........................................................... 15
0x10 ........................................................... 15
0x17 ........................................................... 15
0x8000
NaN ....................................................... 17
0x80000000
NaN ....................................................... 17
0xFFFF
NaN ....................................................... 17
0xFFFFFFFF
NaN ....................................................... 17
0xFFFFFFFFFFFFFFFF
NaN ....................................................... 17
100
Unit ID .................................................... 50
105
Unit ID ............................................. 11, 44
255
Unit ID .................................................... 21
30001 ................................................. 28, 29

30003 ................................................. 28, 29
30007 ........................................................ 28
30057 ........................................................ 28
30061 ........................................................ 36
30063 ........................................................ 36
30065 ........................................................ 36
30067 ........................................................ 36
30069 ........................................................ 36
30071 ........................................................ 36
30073 ........................................................ 36
30075 ........................................................ 36
30077 ........................................................ 36
30079 ........................................................ 36
Index
30097 .........................................................36
30099 .........................................................36
30101 .........................................................36
30103 .........................................................36
30193 ..................................................29, 30
30195 ..................................................29, 30
30197 ..................................................30, 40
Event numbers .................................53, 60
30199 ..................................................30, 37
30211 ..................................................30, 37
30217 .........................................................30
30225 ..................................................30, 37
30227 .........................................................30
30231 .........................................................30
30233 .........................................................30
30243 .........................................................31
30257 .........................................................31
30261 .........................................................31
30265 .........................................................32
30267 .........................................................37
30297 .........................................................37
30331 .........................................................37
30361 .........................................................37
30513 .........................................................29
30517 ..................................................29, 32
30521 ..................................................32, 42
30525 .........................................................32
30529 ..................................................29, 32
30531 ..................................................29, 32
30533 ..................................................29, 32
30535 ..................................................29, 32
30537 ..................................................29, 32
30539 ..................................................29, 32
30541 .........................................................32
30543 .........................................................32
30545 .........................................................32
30547 .........................................................32
30549 .........................................................32
30557 .........................................................32
30601 .........................................................32
30769 .........................................................32
30771 .........................................................32
30773 .........................................................32
65
Index
30775 ................................................. 29, 32

30789 ........................................................ 32
30791 ........................................................ 32
30793 ........................................................ 32
30795 ........................................................ 32
30799 ........................................................ 33
30801 ........................................................ 33
30803 ........................................................ 33
30805 ........................................................ 33
30813 ........................................................ 33
30821 ........................................................ 33
30823 ........................................................ 33
30825 ........................................................ 33
30827 ........................................................ 33
30829 ........................................................ 33
30831 ........................................................ 34
30833 ........................................................ 34
30835 ........................................................ 34
30837 ........................................................ 34
30839 ........................................................ 34
30841 ........................................................ 34
30919 ........................................................ 34
30921 ........................................................ 34
30923 ........................................................ 34
31301 ........................................................ 40
31307 ........................................................ 40
31313 ........................................................ 40
31791 ........................................................ 37
31793 ........................................................ 38
31795 ........................................................ 39
31797 ........................................................ 39
31799 ........................................................ 39
31801 ........................................................ 39
31803 ........................................................ 39
31805 ................................................. 39, 41
31807 ................................................. 39, 41
31855 ........................................................ 38
32051 ........................................................ 40
32053 ........................................................ 39
32055 ........................................................ 39
32057 ........................................................ 38
32119 ........................................................ 38
34097 ........................................................ 34
34101 ........................................................ 34
34105 ........................................................ 35
66
34109 .........................................................35
34113 .........................................................35
34117 .........................................................35
34125 .........................................................35
34141 .........................................................35
34145 .........................................................35
34609 ..................................................42, 43
34613 ..................................................35, 42
34615 ..................................................42, 43
34617 .........................................................42
34619 .........................................................42
34621 ..................................................42, 43
34623 .........................................................43
34625 ..................................................42, 43
34627 ..................................................42, 43
34629 ..................................................42, 43
34631 ..................................................42, 43
34633 ..................................................42, 43
34635 ..................................................42, 43
34637 .........................................................35
40001 ..................................................29, 38
40003 ..................................................29, 38
40009 .........................................................35
40011 .........................................................38
40020 .........................................................35
42109 ..................................................22, 28
42110 .........................................................28
42112 .........................................................28
43088 .........................................................28
Abbreviations ................................................ 7
Activating
XML profile file .......................................25
Address range
Modbus ..................................................14
ADR .............................................................27
Amount of Data
Number of registers ...............................15
Assignment
SMA devices to the Modbus data area
............................................................10
Assignment tables .......................................14
Header ....................................................27
Available and reserved Unit IDs ............... 13
Big-Endian .................................................. 14
Change
Unit ID .................................................... 23
Changes in value
Modbus.................................................. 57
Changing the Gateway ............................ 23
Check
XML profile file ...................................... 25
Check the firmware status ......................... 20
Commissioning
Modbus.................................................. 20
Communication port
Configuring ............................................ 20
CT ........................................................... 7, 36
Data
display.................................................... 18
Reduction ............................................... 10
Data block.................................................. 14
Number of Modbus registers ............... 15
of registers belonging together ............ 15
reading several registers....................... 16
writing several registers ........................ 15
Data fomats................................................ 18
Data requests
Upper limit ............................................. 57
Data Security ................................................ 9
Data types .................................................. 17
Deactivate
XML profile file ...................................... 25
Deleting
XML profile file ...................................... 26
Descriptions ................................................... 7
Detecting new or changed devices .......... 21
Detecting new or replaced devices .......... 20
Device detection finished .......................... 21
Device family
SC nnnCP............................................... 30
SC nnnHE-20 ......................................... 30
Device-ID ................................................ 7, 22
Index
Downloading
XML profile file .......................................26
DT ................................................................18
Duplicate Assignment
Unit ID .....................................................23
Duration ......................................................18
DWORD ................................................. 7, 17
ENUM ..................................................19, 60
Event numbers
Information on breakdown .............53, 60
Excursus
Firmware version ....................................19
Firmware version
Excursus ..................................................19
SMA Modbus profile version ................20
FIX0 .............................................................18
FIX1 .............................................................18
FIX2 .............................................................18
FIX3 .............................................................18
Format
Term definition ........................................27
FW ...............................................................18
Gateway ..............................................10, 14
SC-COM .................................................28
Hierarchical plant structure ........................11
Identification
Time zones ..............................................58
IEC 61131-3 ................................................ 7
Industrial use ................................................. 9
Intended use ................................................. 9
Internet .......................................................... 9
IP address
SC-COM .................................................22
Manage
XML profile files ......................................25
67
Index
Modbus
Activating ............................................... 20
Address range ....................................... 14
Changes in value .................................. 57
Implementation ...................................... 14
PDU ........................................................ 14
Port ......................................................... 56
Reaction time ......................................... 57
Read Coils ...................................... 15, 45
Read Holding Registers.................. 15, 45
Read Input Registers....................... 15, 45
Read Write Multiple Registers .............. 15
Register .................................................. 14
Specification .......................................... 14
TCP Port.................................................. 56
UDP Port................................................. 56
Write Multiple Registers........................ 15
Write Single Register............................. 15
Modbus activation
Background information ....................... 20
Modbus addresses
Reassignment ......................................... 50
Modbus assignments ................................. 14
Modbus exceptions ............................ 16, 51
Modbus master profile .............................. 15
Modbus Master Profile....................... 11, 44
Modbus profile .......................................... 10
SMA ....................................................... 10
User-defined.................................... 10, 50
Modbus registers
Data block ............................................. 15
Read and write ...................................... 15
Modbus slave device
Moxa ioLogik E1242-T ......................... 47
Modbus-able devices
Other vendors........................................ 56
modbusmaster.xml .............................. 25, 44
Motorola format ........................................ 14
Moxa ioLogik E1242-T ...................... 44, 56
Modbus slave device ............................ 47
MPP ............................................................... 7
NaN ....................................................... 7, 21
Overview ............................................... 17
68
Network Topology .....................................11

Nomenclature ............................................... 6
Number of SMA Devices ...........................57
Numerical code
Definition .................................................27
Numerical codes
ENUM.....................................................60
Time zones ..............................................58
Optiprotect ...........................................36, 55
PDU
Modbus ..................................................14
PDU data
Amount....................................................14
Number of Modbus registers ................14
Plant detection ............................................21
Add. or changed devices ......................21
Repetition ................................................21
SC-COM .................................................21
Plant parameters .........................................14
Table .......................................................29
Plant structure
Hierarchical ............................................11
PMAX ............................................................ 7
Port
TCP ..........................................................56
UDP .........................................................56
Qualifications
Target group ............................................. 9
RAW ............................................................18
Reaction time
Modbus ..................................................57
Read and write
Modbus registers ...................................15
Read Coils...................................................15
Read Holding Registers ..............................15
Read Input Registers ...................................15
Read Write Multiple Registers ...................15
Reading out the gateway assignment table

................................................................ 22
Reduction
Available data ....................................... 10
Register
Data block ............................................. 14
Modbus.................................................. 14
Repetition
Plant detection ....................................... 21
RO ................................................................. 7
RW ................................................................. 7
S16 ............................................................. 17
S32 ............................................................. 17
Safety............................................................. 9
SC nnnCP
Device family .................................. 30, 54
SC nnnHE-20
Device family .................................. 30, 54
SCADA .......................................................... 7
SC-COM .................................................... 54
Gateway ................................................ 28
IP address .............................................. 22
Modbus Master Profile ......................... 44
Serial number ............................................. 22
Slave devices
Modbus.................................................. 11
SMA data formats ..................................... 18
SMA data types ......................................... 17
SMA devices .............................................. 14
SMA fieldbus ......................................... 8, 11
SMA Meteo Station............................ 42, 55
SMA Modbus Master profile.................... 11
SMA Modbus profile
Assignment tables.................................. 27
Current version ...................................... 20
Explanation ............................................ 10
SMID ............................................................. 8
SMU .............................................................. 8
Source register .............................................. 8
Sunny Central Communication Controller 54
Sunny Central String-Monitor Controller . 40,
55
Sunny Central String-Monitor-US....... 41, 55
Index
Sunny Sensorbox.................................43, 55
Sunny String-Monitor ...........................39, 55
System stability ...........................................57
Table
Plant parameters ....................................29
Target group ................................................. 5
Qualifications ........................................... 9
Target register ............................................... 8
TEMP ...........................................................19
Third-party vendors
Modbus devices .....................................11
Time zones ..................................................58
Identification ...........................................58
Numerical codes ....................................58
Topology .....................................................11
Total number of devices to be detected....21
Trademarks ................................................... 2
type
Coil ..........................................................45
Holding ...................................................45
Input ........................................................45
U16 .............................................................17
U32 .............................................................17
U64 .............................................................17
Unit ID
= 1 ...................................................13, 28
= 100...............................................13, 50
= 105...............................................13, 44
= 110......................................................13
= 120......................................................13
= 140......................................................13
= 2 ..........................................................13
= 255...............................................13, 21
= 3 ..........................................................13
Architecture.............................................13
Change ............................................20, 23
Changing via the user interface ............24
Check for duplicates ..............................24
Duplicate Unit IDs ..................................23
Range check ...........................................24
Term definition ........................................13
Wrong Data ...........................................23
69
Index
Unit ID = 2 ................................................. 29
Unit IDs ....................................................... 14
Available and reserved......................... 13
Unit-ID is already assigned ....................... 24
Unit-ID is not within the range (3247) .. 24
Upload
XML profile file ...................................... 25
User-defined Modbus profile .................... 10
Validate
XML profile file ...................................... 25
Validity of the document .............................. 5
virtual_modbusprofile ................................ 50
virtualmodbus.xml ............................... 25, 50
WORD.................................................... 8, 17
Write Multiple Registers ............................ 15
Write Single Register ................................. 15
XML
channel ........................................... 44, 50
cycletime ................................................ 45
destination....................................... 45, 51
divisor ..................................................... 46
70
factor .......................................................46
modbus_master_profile .........................44
name .......................................................44
offset........................................................46
quality .....................................................46
signed .....................................................46
size ..........................................................45
slaveunitid ...............................................45
source ..............................................45, 51
status .......................................................46
type .........................................................45
unitid .......................................................50
virtual_modbusprofile ............................50
XML file
modbusmaster ........................................44
virtualmodbus ..................................44, 50
XML profile file............................................25
Activate ...................................................25
Deactivate...............................................25
Deleting...................................................26
Downloading ..........................................26
Test ..........................................................25
Validate...................................................25
XML profile files
Manage ..................................................25
SMA Solar Technology
www.SMA-Solar.com

Satcom Modbus Manual

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Satcom Modbus Manual

Uploaded by

Copyright:

Available Formats

Technical Description

SC-COM Modbus Interface

SC-COM-MODBUS-TB-EN-20 | Version 2.0

SMA Solar Technology AG

SMA Solar Technology AG

SMA Solar Technology AG

Information on this Document ................................................................. 5

2.1 Intended Use ...............................................................................................................9

Product Description .................................................................................10

Modbus Protocol ..................................................................................................... 10

Unit IDs .................................................................................................................13

Data Types and NaN Values .............................................................................17

3.7 Reading and Writing Data in Modbus Protocol ................................................. 15

3.9 SMA Data Formats .................................................................................................. 18

Commissioning & Configuration ...........................................................20

4.1 Comissioning Steps and Requirements ................................................................. 20

Reading out the Gateway ...................................................................................22

Uploading XML Profile-Files ................................................................................25

4.4 Changing Unit IDs with the user interface ............................................................ 24

SMA Solar Technology AG

Downloading XML Profile Files ...........................................................................26

SMA Modbus Profile Assignment Tables .........................................27

Information on the Assignment Tables .................................................................. 27

Device Family SC nnnCP and SC nnnHE-20 .....................................................30

SMA Modbus Master Profile .................................................................44

User-Defined Modbus Profile ................................................................50

Technical Data .........................................................................................54

Supported SMA Devices ........................................................................................ 54

SMA Solar Technology AG

Information on this Document

1 Information on this Document

Sunny Central Communication Controller

Service Name and Transport Protocol

Modbus Application Protocol

SMA Solar Technology AG

Information on this Document

Prerequisite that has to be met for a specific target.

Possibly occurring problem.

Read the set port in field Port

Connects several elements that

Select Settings > Port

Button that you have to select or

Data channel name

Requesting the plant time

Designation in this document

SMA Modbus Master profile

Modbus Master profile

Sunny Central Communication Controller

SMA Solar Technology AG

Information on this Document

Abbreviations and Terms

Variable content of an XML attribute, e. g.

Current measuring unit

Hardware for string monitoring

Numerical value, which identifies a certain

Data with a width of 32 bit, according to

Ground-Fault Detection and

Detection of grounding faults and following

Network protocol for connections over the

Maximum Power Point

The point on the current-voltage (I-V) curve of

No valid value is available

Active power, maximum value