SMA CLCON-10 Manual

ClusterController_Modbus-TI-en-18 | Version 1.8 ENGLISH
Technical Information
SMA CLUSTER CONTROLLER Modbus®Interface

Legal Provisions SMA Solar Technology AG
2 ClusterController_Modbus-TI-en-18 Technical Information
Legal Provisions
The information contained in these documents is the 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. Missing designations do not
mean that a product or brand is not a registered trademark.
Modbus®is a registered trademark of Schneider Electric and is licensed by the Modbus Organiza-
tion, Inc.
SMA SOLAR TECHNOLOGY AG
Sonnenallee 1
34266 Niestetal
Germany
Tel. [phone]
Fax [phone]
www.SMA.de
E-Mail: [e-mail]
Copyright © 2017 SMA Solar Technology AG. All rights reserved.

SMA Solar Technology AG Table of Contents
Technical Information ClusterController_Modbus-TI-en-18 3
Table of Contents
1Information on this Document.................................................................5
2Safety..........................................................................................................7
2.1 Intended Use...............................................................................................................7
2.2 Skills of Qualified Persons.........................................................................................7
2.3 Safety Information ......................................................................................................7
2.4 Information on Data Security....................................................................................8
3Product Description...................................................................................9
3.1 Modbus Protocol........................................................................................................9
3.2 SMA Modbus Profile .................................................................................................9
3.3 User-Defined Modbus Profile....................................................................................9
3.4 PV System Topology...................................................................................................9
3.5Addressing and Data Transmission in the Modbus Protocol.............................12
3.5.1 Unit IDs.................................................................................................................12
3.5.2 Assignment of the Modbus Register to Unit IDs.................................................13
3.5.3 Modbus Register Address, Register Width and Data Block .............................13
3.5.4 Address Range for Modbus Register..................................................................13
3.5.5 Data Transmission................................................................................................13
3.6 Reading and Writing of Data................................................................................14
3.7 SMA Data Types and NaN Values......................................................................15
3.8 SMA Data Formats..................................................................................................15
4Commissioning and Configuration.......................................................17
4.1 Commissioning Steps and Requirements..............................................................17
4.2 Information on Changing Unit IDs ........................................................................17
4.3 Changing Unit IDs via the Gateway.....................................................................18
4.3.1 Reading Out the Gateway..................................................................................18
4.3.2 Changing A Unit ID in the Gateway ..................................................................19
4.4 Changing Unit IDs via the XML File usrplant.xml................................................20
4.4.1 Overview..............................................................................................................20
4.4.2 Structure of the XML File usrplant.xml.................................................................20
4.4.3 Activating and Deactivating usrplant.xml...........................................................21

Table of Contents SMA Solar Technology AG
4 ClusterController_Modbus-TI-en-18 Technical Information
4.5 Resetting the Cluster Controller to the Default Settings......................................22
5SMA Modbus Profile—Assignment Tables...........................................23
5.1 Information on the Assignment Tables..................................................................23
5.2 Gateway (Unit ID = 1) ...........................................................................................24
5.3 System Parameters (Unit ID = 2)...........................................................................26
6User-Defined Modbus Profile ................................................................30
6.1 Structure of the XML File for the User-Defined Modbus Profile.........................30
6.2 Example of a User-Defined Modbus Profile ........................................................31
6.3 Activating and Deactivating User-Defined Modbus Profile...............................32
7Troubleshooting.......................................................................................33
8Technical Data .........................................................................................34
8.1 Supported SMA Inverters.......................................................................................34
8.2 Number of SMA Devices.......................................................................................34
8.3 Modbus Communication Ports...............................................................................34
8.4 Data Processing and Time Behavior.....................................................................35
8.5 Number Codes of the Time Zones........................................................................36
8.6 Frequently Used Number Codes (ENUM)..........................................................38
9Contact......................................................................................................39

SMA Solar Technology AG Information on this Document
Technical Information ClusterController_Modbus-TI-en-18 5
1Information on this Document
Validity
This document is applicable for device type "CLCON-10" and device type "CLCON-S-10"*
(SMA Cluster Controller). It describes the Modbus interface of the SMA Cluster Controller, the
variant of the "Modbus®Application Protocol" implemented by SMA, and the corresponding pa-
rameters, measured values and data exchange formats.
* Not available in all countries (see the SMA Cluster Controller product page at
www.SMA-Solar.com)
This document does not contain any information on software which can communicate with the
Modbus interface (see the software manufacturer's manual).
Target Group
This document is intended for qualified persons. Only persons with appropriate skills are allowed to
perform the tasks described in this document (see Section 2.2 "Skills of Qualified Persons", page 7)
Symbols
Icon
Explanation
Indicates a hazardous situation that, if not avoided, will result in
death or serious injury.
Indicates a hazardous situation that, if not avoided, can result in
death or serious injury.
Indicates a hazardous situation that, if not avoided, can result in
minor or moderate injury.
Indicates a situation that, if not avoided, can result in property dam-
age.
Information that is important for a specific topic or goal, but is not
safety-relevant.
◻
Indicates a requirement for meeting a specific goal.

Information on this Document SMA Solar Technology AG
6 ClusterController_Modbus-TI-en-18 Technical Information
Typographies
Typography
Application
Example
bold
•Elements to be selected
•Elements on a user interface
•File names
•Parameters
•Select Settings.
•Control via communication.
•The file usrprofile.xml
•The values Major and Minor
Nomenclature
Complete designation
Designation in this document
Modbus register
Register
Photovoltaic system
PV system
SMA Cluster Controller
Cluster Controller
Abbreviations
Abbreviation
Designation
Explanation
GFDI
Ground-Fault Detection and
Interruption
Detection of the grounding error and subse-
quent interruption of the electric circuit.
PMAX
Set active power limit
The device can generate active power up to
this limit.
Power Balancer
-
The Power Balancer is a function in
Sunny Mini Central devices for controlling
three-phase grid feed-in, for example, to avoid
unbalanced loads.
SMA fieldbus
-
Hardware interface for communication be-
tween SMA devices (e.g. Speedwire). For
information on the supported communication
interfaces, refer to the datasheet of the SMA
device being used.
SUSy ID
SMA update system ID
Numeric value that identifies a specific
SMA device type, e.g.
128 = STP nn000TL-10.

SMA Solar Technology AG Safety
Technical Information ClusterController_Modbus-TI-en-18 7
2Safety
2.1 Intended Use
The Modbus interface of the SMA Cluster Controller is designed for industrial use and has the
following tasks:
•Remote control of the grid management services of a PV system.
•Remote-controlled querying of the measured values of a PV system.
•Remote-controlled changing of the parameters of a PV system.
The Modbus interface can be used via the protocol Modbus TCP and
by the protocol Modbus UDP.
The enclosed documentation is an integral part of this product:
•Read and observe the documentation.
•Keep the documentation in a convenient place for future reference.
2.2 Skills of Qualified Persons
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 in the installation and configuration of IT systems
•Knowledge of and compliance with this document and all safety information
2.3 Safety Information
This section contains safety information that must be observed at all times when working on or with
the product. To prevent personal injury and property damage and to ensure long-term operation of
the product, read this section carefully and observe all safety information at all times.
Damage to SMA inverters
The parameters of the SMA inverters that can be changed with writable Modbus registers (RW)
are intended for long-term storage of device settings. Cyclical changing of these parameters leads
to destruction of the flash memory of the devices.
•Device parameters must not be changed cyclically.
Contact the SMA Service Line if you would like to automate the remote control of your PV system
(see Section 9 "Contact", page 39).

Safety SMA Solar Technology AG
8 ClusterController_Modbus-TI-en-18 Technical Information
2.4 Information on Data Security
Data security in Ethernet networks
You can connect the Cluster Controller to the Internet. When connecting to the Internet,
there is a risk that unauthorized users can access and manipulate the data of your PV sys-
tem.
•Take appropriate protective measures, for example:
•Set up a firewall
•Close unnecessary network ports
•Only enable remote access via VPN tunnel
•Do not set up port forwarding at the Modbus port in use

SMA Solar Technology AG Product Description
Technical Information ClusterController_Modbus-TI-en-18 9
3Product Description
3.1 Modbus Protocol
The Modbus Application Protocol is an industrial communication protocol that is currently used in
the solar sector mainly for system communication in PV power plants.
The Modbus protocol has been developed for reading data from or writing data to clearly defined
data areas. The Modbus specification does not prescribe what data is within which data area. The
data areas must be defined device-specifically in Modbus profiles. With knowledge of the device-
specific Modbus profile, a Modbus master (e.g. SCADA system) can access the data of a Modbus
slave (e.g. SMA Cluster Controller). Information on firmware versions and device-specific Modbus
registers of SMA products can be found on our product pages or Modbus page at
www.SMA-Solar.com.
The special Modbus profile for SMA devices is the SMA Modbus profile.
3.2 SMA Modbus Profile
The SMA Modbus profile contains definitions for SMA devices. A reduction of the available data
on SMA devices was carried out for the definition and this was then assigned to the corresponding
Modbus registers. The SMA Modbus profile contains, for example, the total and daily energy,
current power, voltage and current levels. The assignment between SMA device data and Modbus
addresses is split into ranges in the SMA Modbus profile and these can be addressed via unit IDs
(see Section 3.5 "Addressing and Data Transmission in the Modbus Protocol", page 12).
To enable access to data of an SMA device, a special gateway is required and this is provided by
way of the Cluster Controller.
3.3 User-Defined Modbus Profile
The user-defined Modbus profile enables you to reassign Modbus addresses of the SMA Modbus
profile. One advantage of reassigning Modbus addresses is, for example, that you can arrange
relevant measured values and parameters in sequence for a specific purpose. These addresses can
then be read and written in a single data block.
3.4 PV System Topology
The SMA Modbus profile was developed for a hierarchical system structure. In this structure, the
Cluster Controller is a communication device which is equipped with a Modbus TCP/IP and Mod-
bus UDP/IP interface. All additional SMA devices that are connected to the Cluster Controller via
the SMA fieldbus are subordinate to the Cluster Controller. From the perspective of the Modbus
protocol, the Cluster Controller represents a Modbus slave that provides a gateway to SMA devic-
es. The SMA devices can only be addressed using this gateway per unit ID.

Product Description SMA Solar Technology AG
10 ClusterController_Modbus-TI-en-18 Technical Information
Example 1: PV System Topology from the Perspective of the SMA Devices
Line
Explanation
IP network connection between SCADA system and Cluster Controller
(PV system router)
SMA fieldbus
Logical assignment of SMA device to unit ID

SMA Solar Technology AG Product Description
Technical Information ClusterController_Modbus-TI-en-18 11
Example 2: PV System Topology from the Perspective of the Modbus Protocol
In the following example, an inverter is assigned to a unit ID between 3 and 247 in each case. This
way the inverter data can be addressed in the Modbus protocol. Unit ID 1 represents the gateway
to the Modbus protocol and unit ID 2, the PV system parameters.

Product Description SMA Solar Technology AG
12 ClusterController_Modbus-TI-en-18 Technical Information
3.5 Addressing and Data Transmission in the Modbus Protocol
3.5.1 Unit IDs
The Unit ID is a superordinate addressing type in the Modbus protocol. The SMA Modbus protocol
has 247 unit IDs, of which, 245 can be assigned to individual devices. If a unit ID is assigned to a
device, then the parameters and measured values of this device can be accessed.
The following table shows an overview of the unit IDs in the SMA Modbus profile:
Unit ID
Explanation
1
This unit ID is reserved for the gateway of the Cluster Controller.
2
This unit ID is reserved for the system parameters.
3 to 247
The unit IDs 3 to 247 are used for addressing individual devices and for the user-
defined Modbus profile. Information on firmware versions and device-specific Mod-
bus registers of SMA products can be found on our product pages or Modbus page
at www.SMA-Solar.com. You can change the assignment of these unit IDs (see Sec-
tion 4.2 "Information on Changing Unit IDs", 17).
255
Devices which are assigned to this unit ID, were connected to the Cluster Controller or
replaced after activation of the Modbus server. The devices cannot be addressed with
this unit ID. You must assign unit IDs from the range 3 to 247 to these devices (see
Section 4.2 "Information on Changing Unit IDs", page 17).

SMA Solar Technology AG Product Description
Technical Information ClusterController_Modbus-TI-en-18 13
3.5.2 Assignment of the Modbus Register to Unit IDs
The assignment of the parameters and measured values of the SMA devices to Modbus register
addresses is achieved using assignment tables and is also shown in this document (see Section 5
"SMA Modbus Profile—Assignment Tables", page 23).
In the assignment table "Gateway (unit ID = 1)", the assignment of SMA devices to individual
unit IDs is saved in the Modbus registers from address 42109. Each assignment has an address
range of four Modbus registers, although only the corresponding register is writable with the
unit ID.
In the assignment table "PV System Parameters (unit ID = 2)", parameters and measured values of
the Cluster Controller and the PV system are stored.
In the assignment table "SMA devices (unit ID = 3 to 247)", the parameters and measured values
intended for all SMA devices are stored. The individual SMA devices use a subset of these for their
device-specific parameters and measured values. Information on firmware versions and device-
specific Modbus registers of SMA products can be found on our product pages or Modbus page
at www.SMA-Solar.com.
3.5.3 Modbus Register Address, Register Width and Data Block
A Modbus register is 16 bits wide. For wider data items, connected Modbus registers are used and
considered as data blocks. The number of connected Modbus registers is indicated in the assign-
ment tables. The address of the first Modbus register in a data block is the start address of the data
block.
3.5.4 Address Range for Modbus Register
For addressing Modbus registers, the address range 0 to 0xFFFF is available with 65536 address-
es.
3.5.5 Data Transmission
In accordance with the Modbus specification, only a specific volume of data can be transported in
a single data transmission in a simple protocol data unit (PDU). The data also contains function-
dependent parameters such as the function code, start address or number of Modbus registers to
be transmitted. The amount of data depends on the Modbus command used and has to be taken
into account during data transmission. You can find the number of possible Modbus registers per
command in section 3.6.
With data storage in the Motorola format "Big Endian", data transmission begins with the high byte
and then the low byte of the Modbus register.

Product Description SMA Solar Technology AG
14 ClusterController_Modbus-TI-en-18 Technical Information
3.6 Reading and Writing of Data
The Modbus interface can be used via the protocol Modbus TCP and by the protocol Modbus
UDP. Using Modbus TCP enables read- and write access (RW) and using Modbus UDP enables
only write access (WO) to the Modbus register.
The following Modbus commands are supported by the implemented Modbus interface:
Modbus command
Hexadecimal value
Data volume
(number of registers)1
Read Holding Registers
0x03
1 to 125
Read Input Registers
0x04
1 to 125
Write Single Register
0x06
1
Write Multiple Registers
0x10
1 to 123
Read Write Multiple Registers
0x17
Read: 1 to 125, Write: 1 to 121
Error messages on reading or writing individual Modbus registers
If a Modbus register is accessed, which is not contained in a Modbus profile, or if a Modbus com-
mand is incorrect, a Modbus exception is generated. Modbus exceptions are also generated when
write access occurs on a read-only Modbus register or read access occurs on a write-only Modbus
register.
Reading or writing of data blocks
To prevent inconsistencies, data blocks of associated registers or register ranges must be read or
written consecutively. The 4 bytes of a 64-bit Modbus register must, for example, be read with an
operation in a 64-bit SMA data type.
Error message on writing multiple Modbus registers as a data block
If multiple registers are written as a data block (Modbus commands 0x10 and 0x17) and an error
occurs during writing, the faulty register as well as all the subsequent registers in the packet will be
rejected. In the event of an error, a Modbus exception will be generated.
Modbus exceptions
For Modbus exceptions, see "Modbus Application Protocol Specification" at
http://www.modbus.org/specs.php.
1
Number of Modbus registers transferable as data block per command

SMA Solar Technology AG Product Description
Technical Information ClusterController_Modbus-TI-en-18 15
3.7 SMA Data Types and NaN Values
The following table shows the data types used in the SMA Modbus profile and compares these to
possible NaN values. The SMA data types are listed in the assignment tables in the Type column.
They describe the data widths of the assigned values:
Type
Description
NaN value
S16
A signed word (16-bit).
0x8000
S32
A signed double word (32-bit).
0x8000 0000
STR32
32 byte data field, in UTF8 format.
ZERO
U16
A word (16-bit).
0xFFFF
U32
A double word (32-bit).
0xFFFF FFFF or -1
U32
For status values, only the lower 24 bits of a double word (32-
bit) are used.
0xFFFF FD or 0xFFFF
FE or -1
U64
A quadruple word (64-bit).
0xFFFF FFFF FFFF
FFFF or -1
3.8 SMA Data Formats
The following SMA data formats describe how SMA data is to be interpreted. The data formats are
important, for example, for the display of data or for its further processing. The SMA data formats
are listed in the Format column of the assignment tables.
Format
Explanation
Duration
Time in seconds, in minutes or in hours, depending on the Modbus register.
DT
Date/time, in accordance with country setting. Transmission as UTC
(seconds since 1970-01-01).
ENUM
Coded numerical values. The breakdown of the possible codes can be found directly
under the designation of the Modbus register in the SMA Modbus profile—assignment
tables (see also Section 8.6 "Frequently Used Number Codes", page 38).
FIX0
Decimal number, commercially rounded, no decimal place.
FIX1
Decimal number, commercially rounded, one decimal place.

Product Description SMA Solar Technology AG
16 ClusterController_Modbus-TI-en-18 Technical Information
FIX2
Decimal number, commercially rounded, two decimal places.
FIX3
Decimal number, commercially rounded, three decimal places.
FW
Firmware version (see "Firmware version extract" below)
IP4
4-byte IP address (IPv4) of the form XXX.XXX.XXX.XXX.
RAW
Text or number. A RAW number has no decimal places and no thousand or other
separation indicators.
REV
Revision number of the form 2.3.4.5.
TEMP
Temperature values are stored in special Modbus registers in degrees Celsius (°C), in
degrees Fahrenheit (°F), or in Kelvin K. The values are commercially rounded, with
one decimal place.
UTF8
Data in UTF8 format.
Firmware version extract, format "FW": From the delivered DWORD, four values are extract-
ed. The values Major and Minor are contained BCD-coded in bytes 1 and 2. Byte 3 contains the
Build value (not BCD-coded). Byte 4 contains the Release Type value according to the following
table:
Release type
Release-type coding
Explanation
0
N
No revision number
1
E
Experimental release
2
A
Alpha release
3
B
Beta release
4
R
Release
5
S
Special release
> 5
As number
No special interpretation
Example:
Firmware version of the product: 1.5.10.R
Values from DWORD: Major: 1, Minor: 5, Build: 10, Release type: 4
(Hex: 0x1 0x5 0xA 0x4)

SMA Solar Technology AG Commissioning and Configuration
Technical Information ClusterController_Modbus-TI-en-18 17
4Commissioning and Configuration
4.1 Commissioning Steps and Requirements
Requirements:
☐The devices of the PV system must be connected to the Cluster Controller and the
Cluster Controller must be commissioned (for information on connection and commissioning,
see the Cluster Controller installation manual).
☐You must log in as installer to the Cluster Controller (for login to or logout of the
Cluster Controller, see the Cluster Controller user manual).
Procedure:
1. Activate the Modbus server(s) and, if required, configure the communication ports
(for Modbus configuration, see the Cluster Controller user manual).
Allocation of unit IDs by activation of the Modbus servers
Upon activation of the Modbus servers of the Cluster Controller, unit IDs are assigned to
the SMA devices already connected to the Cluster Controller. The protocol types TCP/UDP
can be activated individually or together. If one or both of the servers are deactivated and
reactivated, the previously assigned Modbus Unit IDs are maintained.
2. Change the unit IDs if, after activation of the Modbus servers, further SMA devices have
been added to the PV system or SMA devices have been replaced (see the following sec-
tions).
4.2 Information on Changing Unit IDs
You can change the unit IDs of SMA devices. A change is required, for example, if additional or
changed SMA devices are connected to the Cluster Controller after activation of the Modbus
servers. By way of the automatic detection of the PV system, additional or changed devices are
assigned the Modbus unit ID = 255 (NaN). On the other hand, it may be necessary to change the
unit IDs if a restructuring of the system topology is required, for example, to better map the physical
arrangement of the devices in the Modbus protocol.
Depending on whether you wish to change individual unit IDs or restructure the entire system topol-
ogy, you have two options:
•Changing Unit IDs via the gateway (recommended for changing individual Unit IDs)
•Changing Unit IDs via an XML file (recommended for restructuring of the system topology)
Both of these methods are described in separate Sections.

Commissioning and Configuration SMA Solar Technology AG
18 ClusterController_Modbus-TI-en-18 Technical Information
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, for example, using
a SCADA system.
Accessing the gateway
You access the gateway via the IP address of the Cluster Controller, under the unit ID = 1.
The assignment of the system devices for unit IDs 3 to 247 is stored in the Modbus registers from
address 42109. Each assignment has an address range of four Modbus registers. You can find the
Modbus register of the gateway in Section 5.2 "Gateway", page 24.
Example "Read out additional device from the gateway“
Via automatic detection, an additional SMA device was assigned to unit ID = 255 (indicated with
C in column "Device #" in the following table). The assignments of the gateway were, as follows
here, shown with a SCADA system as a table:
Modbus address
Content
Description
Device #
…
…
…
42109
158
SUSy-ID
A
42110
2145600972
Serial number
A
42112
3
Unit ID
A
42113
158
SUSy-ID
B
42114
2145600320
Serial number
B
42116
4
Unit ID
B
42117
158
SUSy-ID
C
42118
2145600934
Serial number
C
42120
255
Unit ID
C
…
…
…
…

SMA Solar Technology AG Commissioning and Configuration
Technical Information ClusterController_Modbus-TI-en-18 19
4.3.2 Changing A Unit ID in the Gateway
You change a unit ID by writing it to the relevant Modbus address. All three of the Modbus regis-
ters that belong to a device-unit-ID assignment must be transmitted in a single data block, although
only the register with the unit ID is writable. For the following example, this means that all the data
of the three Modbus addresses 42117, 42118 and 42120 must be contained in the data block.
Do not assign unit IDs more than once
You must not assign a Unit ID more than once. In the event of a Modbus query with a unit
ID that has been assigned more than once, the data is read out for the device that is en-
tered with this unit ID in the gateway under the lowest Modbus address.
Example "Changing A Unit ID in the Gateway"
The following table shows an example of assignment of a device to a unit ID. An inverter was
subsequently detected with SUSy ID = 158 and serial number 2145600934, as the third device in
the PV system (Modbus addresses 42117 to 42120). The unit ID of this device was manually set to
5:
Modbus address
Designation
After detection
Modified
42117
SUSy-ID
158
158
42118
Serial number
2145600934
2145600934
42120
Unit ID
255 (NaN)
5

Commissioning and Configuration SMA Solar Technology AG
20 ClusterController_Modbus-TI-en-18 Technical Information
4.4 Changing Unit IDs via the XML File usrplant.xml
4.4.1 Overview
The Cluster Controller stores the assignments of the devices of the PV system to unit IDs in the file
sysplant.xml. This file contains an excerpt of the gateway (see Section 5.2 "Gateway (Unit ID =
1)", page 24). If new SMA devices are added or if SMA devices are replaced, these are respec-
tively added to the available XML structure of this file with unit ID = 255 by the Cluster Controller.
You can define your own variant of this file in the file usrplant.xml. You can use
sysplant.xml as a template for usrplant.xml.
You can download the file sysplant.xml from the Cluster Controller.
Uploading and downloading XML files
For more information on uploading and downloading XML files via the user interface, see
the SMA Cluster Controller user manual.
The file usrplant.xml must be activated in the Cluster Controller. Once the file usrplant.xml is
activated, the file sysplant.xml is not taken into consideration for the duration of the activation.
4.4.2 Structure of the XML File usrplant.xml
The files sysplant.xml and usrplant.xml have the same tag structure.
The basic structure of the files is as follows:
<?xml version=“1.0“ encoding=“UTF-8“?>
<plant version=“001“>
<device regoffs=“aaa“ susyid=”bbb“ serial=”cccccccccc“ unitid=”ddd“ />
…
</plant>
Legend for XML tags and attributes:
XML tag or attribute
Explanation
<device…/>
Within the tag "Device" is the assignment of a device to a unit ID.
regoffs=”aaa“
Number of the device in file sysplant.xml. The number must not neces-
sarily be assigned sequentially. There are four Modbus register ad-
dresses between two devices. Regoffs = 0 defines the first device under
the Modbus address 42109, Regoffs = 244 the last device under the
Modbus address 43085.
susyid=”bbb“
SUSy ID of the device