DCC LoadSharing V3 0 en

SINAMICS S120:
DCC Loadsharing
Siemens
SINAMICS S120 Industry
Online
https://support.industry.siemens.com/cs/ww/en/view/38470057 Support
Legal information
Legal information
Use of application examples
Application examples illustrate the solution of automation tasks through an interaction of several
components in the form of text, graphics and/or software modules. The application examples are
a free service by Siemens AG and/or a subsidiary of Siemens AG (“Siemens”). They are non-
binding and make no claim to completeness or functionality regarding configuration and
equipment. The application examples merely offer help with typical tasks; they do not constitute
customer-specific solutions. You yourself are responsible for the proper and safe operation of the
products in accordance with applicable regulations and must also check the function of the
respective application example and customize it for your system.
Siemens grants you the non-exclusive, non-sublicensable and non-transferable right to have the
application examples used by technically trained personnel. Any change to the application
examples is your responsibility. Sharing the application examples with third parties or copying the
application examples or excerpts thereof is permitted only in combination with your own products.
The application examples are not required to undergo the customary tests and quality inspections
of a chargeable product; they may have functional and performance defects as well as errors. It is
your responsibility to use them in such a manner that any malfunctions that may occur do not
result in property damage or injury to persons.
Disclaimer of liability
Siemens shall not assume any liability, for any legal reason whatsoever, including, without
limitation, liability for the usability, availability, completeness and freedom from defects of the
application examples as well as for related information, configuration and performance data and
any damage caused thereby. This shall not apply in cases of mandatory liability, for example
under the German Product Liability Act, or in cases of intent, gross negligence, or culpable loss of
life, bodily injury or damage to health, non-compliance with a guarantee, fraudulent
non-disclosure of a defect, or culpable breach of material contractual obligations. Claims for
damages arising from a breach of material contractual obligations shall however be limited to the
© Siemens AG 2020 All rights reserved
foreseeable damage typical of the type of agreement, unless liability arises from intent or gross
negligence or is based on loss of life, bodily injury or damage to health. The foregoing provisions
do not imply any change in the burden of proof to your detriment. You shall indemnify Siemens
against existing or future claims of third parties in this connection except where Siemens is
mandatorily liable.
By using the application examples, you acknowledge that Siemens cannot be held liable for any
damage beyond the liability provisions described.
Other information
Siemens reserves the right to make changes to the application examples at any time without
notice. In case of discrepancies between the suggestions in the application examples and other
Siemens publications such as catalogs, the content of the other documentation shall have
precedence.
The Siemens terms of use (https://support.industry.siemens.com) shall also apply.
Security information
Siemens provides products and solutions with industrial security functions that support the secure
operation of plants, systems, machines and networks.
In order to protect plants, systems, machines and networks against cyber threats, it is necessary
to implement – and continuously maintain – a holistic, state-of-the-art industrial security concept.
Siemens’ products and solutions constitute one element of such a concept.
Customers are responsible for preventing unauthorized access to their plants, systems, machines
and networks. Such systems, machines and components should only be connected to an
enterprise network or the Internet if and to the extent such a connection is necessary and only
when appropriate security measures (e.g. firewalls and/or network segmentation) are in place.
For additional information on industrial security measures that may be implemented, please visit
https://www.siemens.com/industrialsecurity.
Siemens’ products and solutions undergo continuous development to make them more secure.
Siemens strongly recommends that product updates are applied as soon as they are available
and that the latest product versions are used. Use of product versions that are no longer
supported, and failure to apply the latest updates may increase customer’s exposure to cyber
threats.
To stay informed about product updates, subscribe to the Siemens Industrial Security RSS Feed
at: https://www.siemens.com/industrialsecurity.
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 2
Table of contents
Table of contents
Legal information ......................................................................................................... 2
1 Task ..................................................................................................................... 4
1.1 Design and structure ............................................................................ 4
1.2 Load sharing ......................................................................................... 5
2 Solution............................................................................................................... 6
2.1 Solution overview ................................................................................. 6
2.2 Mandatory Hardware- and Software components ............................... 7
3 Program Description ......................................................................................... 8
3.1 Operating mode .................................................................................... 8
3.1.1 Torque linking ....................................................................................... 8
3.1.2 Bias and Limitation ............................................................................... 8
3.1.3 Droop and Compensation .................................................................... 9
3.1.4 Balancer ............................................................................................. 11
3.1.5 Speed coupling ................................................................................... 11
3.1.6 External speed setpoint ...................................................................... 12
3.2 Faults and alarms ............................................................................... 13
3.2.1 Faults .................................................................................................. 13
3.2.2 Alarms ................................................................................................ 13
4 Commissioning ................................................................................................ 14
4.1 For your safety ................................................................................... 14

4.1.1 Markings used for safety notes .......................................................... 14
4.1.2 Responsibilities of the operating personnel ....................................... 14
4.2 Installing the application ..................................................................... 16
4.3 Notes on computation time and memory load levels ......................... 19
4.3.1 Computation time load ....................................................................... 19
4.3.2 Memory usage .................................................................................... 19
5 Using the application ...................................................................................... 20
6 Control function block FB38015 LDCC_LoadControl .................................. 22
6.1 Description of the function block interface. ........................................ 22
6.2 Interface description of the additional telegram ................................. 24
6.3 Use of the LDCC_LoadControl block ................................................. 25
6.3.1 Configure additional telegram ............................................................ 25
6.3.2 Connection of additional telegram in drive. ........................................ 26
6.3.3 Insert LDCC_LoadControl block in the project. .................................. 26
6.3.4 Functionality of the LDCC_LoadControl block. .................................. 28
7 Appendix .......................................................................................................... 30
7.1 Function diagramms ........................................................................... 30
7.2 Parameterlist ...................................................................................... 38
7.3 Application Support ............................................................................ 53
7.4 Links and Literature ............................................................................ 53
7.5 Change documentation ...................................................................... 54
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 3
1 Task
1 Task
Many industrial applications require that several motors operate together or are
coupled together. Optimum operation of systems such as these require that loads
are equalized between the mechanically coupled axes. If the load sharing between
the drives is not controlled, then these can work against one another and therefore
go into an overload condition. Load sharing is used to distribute the complete
mechanical load in a controlled fashion and in defined percentage levels across the
individual drives.
1.1 Design and structure

Coupled axes exist in many real-life applications, especially where a continuous
web is being manipulated. Drives together can be used to transport the material
and thus are coupled flexible or to move a single axis being coupled rigidly. These
two modes can also be mixed together, as for example rolls, which are driven by
two motors are coupled with each other thru the material. Motors being coupled
together will be also referred to as motors in a group.
Flexible coupling
With such couplings the rolls are connected to each other only with the material
web. This material web can be elastic, but this elasticity has also a limit. If a roll
pulls on the material stronger than another, the tension may vary, and this can
influence the whole process and damage the material and/or the equipment. This
can be avoided with the correct selection of a load distribution concept.
Figure 1-1
Rigid coupling
In this case the motors are connected to each other with stiff mechanics (rolls,
gears, etc.) which force them to turn with the same speed. Typically, identical
motor types are used, and so the produced torque of these motors should also be
identical. To ensure this, a load distribution system is necessary, since without
such a system the load might be distributed unevenly among the motors, in worst
case, one motor would try to constantly brake the axis and another will accelerate
against.
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 4
1 Task
Figure 1-2
1.2 Load sharing

For mechanically coupled axes, it is not enough to enter identical speed setpoints
at the axes involved. As a result of production tolerances, slip of the drive wheels,
measuring-related deviations when sensing the speed and operation-related wear,
distortion stress is obtained. This leads to increased wear and makes it more
difficult to optimally utilize the drive. This is the reason that the drives must be
operated as master-slave group. Within this group, mechanical distortion stress
that occurs is corrected using a load-balance controller.
With this concept, it is necessary to influence the setpoint channel of the master.
The master requires information about the state and the number of slaves – or as
to whether there are any slaves at all. This is also applicable for the slaves. All the
drives in the group operate independently of one another –slaves are only
connected through the mechanical system.
Pretension
For axes with slip or gearbox backlash, it may be necessary to establish a
pretension torque in the drives. This involves basic functionality, which can be
optionally used in parallel with load balance control. The slave establishes a torque
specified by the user. The master acts against the slave torque so that both drives
tension the mechanical coupling with a defined torque.
Load factor
A load factor can be defined between the master and slave in order to distribute
the load between the master and slave in a certain ratio.
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 5
2 Solution
2 Solution
2.1 Solution overview
The solution described here to simply and quickly implement load balancing
functionality is based on the SINAMICS S120 drive system.
This application does not contain a description of:
• The basic commissioning of the SINAMICS S120 drive system
• Configuring using the DCC Editor
It is assumed that readers have basic knowledge of these topics.
The application is implemented in SINAMICS DCC and is always computed in
every slave axis. Fehler! Verweisquelle konnte nicht gefunden werden. shows a
possible solution configuration.
Figure 2-1
In principle, each drive can be used as master; data is transferred from the master
to the slaves via BICO links with SINAMICS parameters.
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 6
2 Solution
2.2 Mandatory Hardware- and Software components

Table 2-1 shows the hardware and software components required.
Table 2-1
Component Note
SINAMICS S120 drive line-up with CU320- From firmware 5.2
2 Control Unit
Starter commissioning tool with installed Starter from V5.3 and higher
DCC
Or
Startdrive commissioning tool with installed Startdrive from V15.1 (SINAMICS FW from
option package 5.2 required)
A DCC engineering license “SINAMICS MLFB 6SL3070-4FA01-0XA5

DCC combo V15” is required which can (DVD with USB-Stick) or MLFB 6SL3070-
used for Starter as well as for Startdrive 4FA01-0XG5
DCC (Download)
The following table lists all the files, which are used for the application.
Table 2-2
Component Note
LSSlaveEN V3.0.zip This zipped file contains the XML exports
of the DCC charts for STARTER and plan

exports *.dcc for STARTDRIVE
38470057_DCC_Loadsharing_V3_0_en.pdf This document
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 7
3 Program Description
3.1 Operating mode
The different operating modes and their principle of operation are described in the
following.
3.1.1 Torque linking
In this operating mode, the slave drive is operated with a pure P controller without
integral component. In this operating mode, the slave drive, is not able to quickly
respond to act against the master drive. The integral component of the master
drive speed controller is entered the slave drive as supplementary torque. The
supplementary torque sets the load ratio between the master and slave drive. This
is because it is formed by multiplying a given load factor and the integral
component of the master speed controller. Figure 3-1 schematically shows the
torque coupling.
Figure 3-1
MASTER
Speed Torque
Setpoint PI_M
Setpoint
Actual PI
Speed I_M
SLAVE
Pretension
Load
factor
Speed
Setpoint Torque
P P_M Setpoint
Actual
Speed
Torque
Precontrol
3.1.2 Bias and Limitation
In this operating mode, the master torque setpoint (preferably without the torque
precontrol component) is added to the optional pre-control signal of the slave. This
signal is then used as symmetrical torque limit, and in this operating mode, the
speed controller remains in saturation (overcontrolled). The application enters the
overcontrol setpoint with the correct sign corresponding to the torque direction. If
the mechanical coupling is lost, for example due to material breakage or shaft
breakage, then the speed controller becomes operational again and controls the
slave drive speed to the specified speed setpoint plus the set overcontrol setpoint.
This prevents the drive from uncontrollably accelerating up to the maximum speed.
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 8
Friction torque and accelerating torque precontrol should be realized as accurately

as possible in order to avoid the drives being overloaded as a result of uneven load
sharing.
Figure 3-2
MASTER
Speed
Setpoint
Torque
PI PI_M
Actual Setpoint
Speed
SLAVE
Load
factor
Pretension
Bias
Speed
Setpoint Torque
PI PI_M Setpoint
Actual
Speed
3.1.3 Droop and Compensation
Droop
Entering a droop at the slave drive causes its operating point to be shifted. By
entering a droop, the slave speed setpoint is reduced as a function of the load.
This means, for example, for a droop factor of 5%, a torque with the magnitude of
the rated torque causes the speed setpoint to decrease to 95% and at half the
rated torque, to 97.5% of the speed setpoint, see characteristic (2). This influences
the speed of the slave drive as a function of the load; load compensation is
therefore realized at the slave drive. The slave drive can no longer work against the
master drive; this is because as a result of the droop feedback, a permanent
integral component cannot be established for the speed controller. Of course, this
simultaneously acts to weaken the slave load component with respect to the
master at the operating point (see characteristic (2) in the following diagram).
Figure 3-3
Speed
normal PI-Control (1)

Droop
PI Control with Droop

(2)
Nominal Torque Mn Torque
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 9
Compensation
To obtain an even load sharing even when the slave has droop feedback, in
addition to the own droop component, the torque setpoint of the master drive is
weighted with the droop factor and entered at the slave. This results in an
additional load difference compensation, as the droop characteristic (2) is shifted
on the droop and compensation characteristic (3). Therefore, the slave drive is
flexible around its operating point, and does not disturb the master; however, it
provides the load level specified by the master. Figure 3-4 shows the principle of
operation of the droop and compensation operating mode.
Figure 3-4
Speed
Compensation OP
PI-control (1)
Droop PI Control with droop and compensation
(3)
PI Control with droop (2)
Nominal Torque Mn Torque

Figure 3-5 shows the control structure of droop and compensation. Only the droop
factor is shown here, as generally, the droop factor is the same as the
compensation factor. The load-dependent droop is calculated based on the integral
component of the slave speed controller.
Figure 3-5
MASTER
Speed
Setpoint Torque
PI PI_M
Actual Setpoint
Speed
SLAVE
Load factor Droop factor
Compensation
Pretension Droop
Speed
Setpoint I_M
Actual PI PI_M Torque
Speed Setpoint
Torque
precontrol
Note When Master use torque precontrol, it is better not to use this signal in combination
with the output of the speed controller for the slave. Slave should do its own torque
precontrol
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 10
3.1.4 Balancer
In this operating mode torque setpoint of the master will be compared with torque
setpoint of the slave. The deviation will be evaluated by a PI-controller and output
value is entered at the slave additional speed setpoint. If the mechanical coupling
is lost, for example due to material breakage or shaft breakage, then output of the
balancer is limited to the preset value. This prevents the drive from uncontrollably
accelerating up to the maximum speed.
Figure 3-6
3.1.5 Speed coupling
In this operating mode, the master speed setpoint is connected to the slave. There
are no further compensations active.
Figure 3-7
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 11
3.1.6 External speed setpoint
In this operating mode, the master has no influence on the slave. The slave uses
the speed setpoint from parameter P1155. When a standard telegram is used,
speed setpoint out of the telegram is active. There are no further compensations
active.
Figure 3-8
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 12
3.2 Faults and alarms

3.2.1 Faults
F51050 Upper torque limit not connected

Drive object: SERVO, VECTOR
Response: OFF2
Acknowledgment: IMMEDIATELY
Cause: P21613 is not connected.
Remedy Connect r1534(Servo) or r1520(Vector) with P21613
F51051 Lower torque limit not connected

Response: OFF2
Cause: P21614 is not connected.
Remedy Connect r1535(Servo) or r1521(Vector) with P21614
F51052 Invalid gearbox ratio

Response: OFF2
Cause: At least one of the gearbox ratios in p21520 and p21521 is either zero or
negative
Remedy Check the transfer of the gearbox ratios, master-load and slave-load
3.2.2 Alarms
A51060 An invalid operating mode was selected

Response: NONE
Acknowledgment: NONE
Cause: No exclusive operating mode selected
Remedy Only one operating mode may be selected, using the fixed bit at p21512
and p21513 or by using control word p22102
A51061 Compensation is not active

Response: NONE
Acknowledgment: NONE
Cause: Mode Speed Coupling (4) or External Setpoint (5) is active.
Remedy Activate Mode 0 to 3.
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 13
4 Commissioning
4 Commissioning
4.1 For your safety
4.1.1 Markings used for safety notes
Pictogram, signal word and text

All safety information contained in this documentation is identified by a text graphic
- comprising a pictogram and a signal word – with an explanatory text. The
combination of pictogram and signal word permits clearly differentiated information
levels based on the degree of danger. Safety information precedes the information
about activities to be carried out.
Levels
For the safety notes, there are three levels. They are marked using the same
pictogram. They differ by the signal word used.
DANGER indicates that death or severe personal injury will result if proper
! precautions are not taken.
DANGER
WARNING indicates that death or severe personal injury may result if

! proper precautions are not taken.
WARNING
NOTICE NOTICE indicates that an undesirable result or state may occur if the
corresponding instructions are not observed.
4.1.2 Responsibilities of the operating personnel
Intended purpose
The proper use of the application components exclusively comprises the open-loop
and closed-loop control of test set-ups that were adapted to the power/performance
of the application components. In order that the application functions perfectly, the
required SINAMICS standard components as well as the necessary hardware and
software components must have been installed.
The operating personnel may only make changes to the application components
after prior written agreement from the suppliers.
Improper use
The following are considered to constitute improper use (misuse):
• All forms of use that deviate from or exceed the above mentioned proper use.
• Failure to observe the safety instructions.
• Failure to immediately rectify malfunctions that could impair safety.
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 14
4 Commissioning
• All forms of manipulation of devices that serve to ensure the proper

functioning, unrestricted use, or active or passive safety of the equipment.
• The recommended hardware and software components are not used.
• Operation of the application components if they are not in perfect technical
condition as well as failure to operate them safely while considering the
inherent risks and complying with all instructions contained in this document.
The manufacturer disclaims liability of any kind in the event of improper use.
Obligation to monitor
The operating personnel have a continuous obligation to observe the overall
technical condition of the application components (obvious defects or damage as
well as changes in operating behavior).
The operating personnel are obliged to only operate the application if it is in perfect
condition. He must check the state of the application components each time before
they are used and rectify any defects before commissioning.
Qualification of personnel
The operating company must always deploy trained, authorized and reliable
personnel. In so doing, all safety regulations must be observed.
The personnel must have received special, in-depth training and instructions about
possible hazards and dangers.
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 15
4 Commissioning
4.2 Installing the application

This chapter describes the steps required to install the application example.
Preconditions
• The speed controller was optimized in each drive
• Control parameters for identical motors with identical mechanical system must
be the same (for the speed and current controllers)
• Friction characteristic was calculated for each drive
• The configuration was roughly checked
Inserting the DCC plan into your STARTER project

Right-click on the slave drive in your project and select "Expert" -> "Import object".
Figure 4-1
Select "LSSlave.xml" file from the folder that was downloaded. After XML has been
imported, the DCC plan is displayed below the slave drive.
Figure 4-2
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 16
4 Commissioning
Inserting the DCC plan into your STARTER project

Right-click on the charts folder of slave drive in your project and select "Import
Drive Control Chart(s)".
Figure 4-3
Choose "StartdriveLoadsharingV3_0.dcc". After the import, the plans occur under

the chart folder. There are 5 charts, because with STARTDRIVE only one sampling
interval per chart is possible.
Figure 4-4
Table 4-1 (By "Saving/compiling" the Starter project or after importing the .dcc file
in Startdrive, the standard interconnections are created in the slave corresponding
to Table 4-1. )
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 17
4 Commissioning
Parameter Parameters
Description
inputs outputs
p1160 CI: Speed controller, common speed setpoint r21801

p1476.0 BI: Hold speed controller integrator r21624.0
p1477.0 BI: Set speed controller integrator value r21624.0
p1478.0 CI: Speed controller integrator value r21625
p1513 CI: Supplementary torque 2 r21623
p1552 CI: Torque limit, upper scaling without offset r21643
p1554 CI: Torque limit, lower scaling without offset r21647
p1545.0 BI: Activates travel to fixed stop1 r21641
P21517 BI: Slave OFF1 r898.0
p21604 CI: Slave speed controller integrator r1482
feedback
p21611 CI: Slave reference feed [RPM] r2700
p21612 CI: Slave reference torque [Nm] r2703
p22102 CI: Command word r22100 or PLC
Then you must interconnect the following parameters in the slave drive with the
master drive parameters as described in Table 4-2.
Table 4-2
DCC
parameters in Description Master
the slave
p21601 CI: Master speed setpoint [scaled] r62
p21602 CI: Master torque setpoint [scaled] r1480
p21603 CI: Master speed controller integrator output r1482
P21606 CI: Master-torque setpoint r79
p21609 CI: Master reference speed [RPM] r2700
p21610 CI: Master reference torque [Nm] r2703
DCC
parameters in Description Slave
the slave
p21605 CI: Slave torque setpoint [Nm] r79
p21613 CI: Slave upper torque limit [scaled] r1534(Servo)
r1520(Vector)
p21614 CI: Slave lower torque limit [scaled] r1535(Servo)
r1521(Vector)
1With this link operation, faults and alarms, initiated by continuous operation of the torque limit,
are suppressed. Important for the "Bias and limiting" operating mode.
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 18
4 Commissioning
4.3 Notes on computation time and memory load levels

4.3.1 Computation time load
The runtime groups of the DCC charts are already preset. Table 4-3 shows the CU
load for the preset runtime groups. Depending on which control mode is used, the
other two can be deactivated. The control and setpoints execution groups are
mandatory.
Table 4-3
Execution groups Execution groups Setting CU load
STARTER STARTDRIVE
Control LoadsharingA BEFORE basic positioner 2,5%
Setpoint LoadsharingE BEFORE pos ctrl 2,6%
Torquelinking LoadsharingB BEFORE pos ctrl 1,2%
DroopCompensation LoadsharingC BEFORE pos ctrl 4,8%
BiasLimitation
Balancer LoadsharingD BEFORE pos ctrl 1,2%
Execution groups "Control" and "Setpoint"/"LoadsharingA" and

"LoadsharingE" must be calculated in every case.
Note The master should always be calculated before the slaves, so that the slaves are
calculated with the already updated actual values of the master. The calculation
sequence on a Control Unit is defined by the DO number or can be adapted by

p7900 .
4.3.2 Memory usage
Because the memory load there is no limitation of maximum number of axis,
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 19
5 Using the application

The application is controlled via the control word and the load sharing parameters.
The status word is available for diagnostics. From Version V3.0 the operation mode
is set via P21512. There is no additional activation bit. The operation mode is
directly active, and it is possible to change on the fly.
Command word
The control word of the load sharing function can either be written by the fieldbus,
fixed bits or via digital inputs bit serially (p21515 to p21516) or as word (p22102).
The bits of the control word are explained in Table 5-1.
Table 5-1
Bit Parameter Description Note
Bit 00 p21515 Pretension Pretension activated
Bit 01 p21516 Block I-Part Block I-part of balancer
… … … …
Bit 15 n/a n/a n/a
Parameters
All the parameters can either be written using the automation system, or set using
STARTER or the SINAMICS operator panel AOP30
For the slave operating mode, the values described in Table 5-2 must be written.
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 20
Table 5-2
Parameter No. Description Note
p21512 Operation mode Set operation mode (0-5)
p21520 Slave gearbox ratio It is not permissible that it is set to zero
p21521 Master gearbox ratio It is not permissible that it is set to zero
p21522 Load factor [%] 100% -> symmetrical load sharing to the
master
For all operating modes
p21523 Pretension torque [Nm] Value of the optional pretension torque
Notice: The torque should not be
selected to be too high so that the drive
still has enough accelerating torque.
p21662 Droop factor [RPM/Nm] For "Droop compensation" operating
mode
Values between 2% and 5% are
recommended.
p21642 Bias factor [%] For the "Bias and limiting" operating
mode
5 % is recommended
Status word
Binary outputs are combined to create a status word (r22104) - and can be simply
transferred to the automation system
Table 5-3
Bit Description Note
Bit 00 Compensation active Operation mode 0 to 3 is active.
Bit 01 Droop and Droop and compensation operating mode exclusively
compensation ON selected
Bit 02 Bias and limiting ON "Bias and limiting" operating mode exclusively selected
Bit 03 Torque coupling ON Operating mode torque coupling exclusively selected
Bit 04 Pretension ON Set pretension is active
Bit 05 Valid operating mode Valid operating mode selected
Bit 06 Invalid gearbox ratio Invalid gearbox ratio - error message
Bit 07 Invalid gearbox ratio of Invalid gearbox ratio - error message
the master
Bit 08 Balancer ON "Balancer" operating mode exclusively selected
Bit 09 I-Part deactivated I-Part from "Balancer" is deactivated
Bit 10 Speed coupling ON Only speed coupling is active
Bit 11 External Setpoint ON Speed setpoint out of telegram of slave
Bit 12 F51050 P21613 not connected
Bit 13 F51051 P21614 not connected
Bit 14 n/a n/a
Bit 15 n/a n/a
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 21
6 Control function block FB38015 LDCC_LoadControl
6 Control function block FB38015

LDCC_LoadControl
6.1 Description of the function block interface.
Use the FB38015 to control the DCC application „Loadsharing“ with S7-1500/S7-
1200 controller. Do a separate function call for every drive in a cyclic program.
Picture 6-1
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 22
Table 6-1 Inputs of FB38015

Signal Type Default Format Description
enable I False Bool Enable function block
mode I 0 Int [0] Select mode ""Torque linking"
[1] Select mode ""Bias and limiting"
[2] Select mode ""Droop and compensation".
[3] Select mode ""Balancer".
[4] Select mode ""Speed coupling".
[5] Select mode "External setpoint".
pretensionOn I False Bool Activate „pretension“
disableIpart I False Bool Disable I-part of balancer
staticTorque I 0.0 Real Pretension value in % of reference value (P2003)
loadFactor I 100.0 Real Load distribution: With100% Slave is like Master
HardwareID I 0 HW_IO Hardware ID of the additional telegram
Table 6-2 Outputs of FB38015

Signal Type Default Format Description
valid O False Bool Function block works without error.

error O False Bool Error during write/read function.
errorID O 16#0 Word Error code of the function.
status O 16#0 Word Sate messages of the function block.
compensationActive O False Bool Operation mode 0 to 3 is active.
droopAndCompensationActive O False Bool DroopAndCompensation is active.
biasAndLimitingActive O False Bool BiasAndLimiting is active.
torqueCouplingActive O False Bool TorqueCoupling is active.
balancerActive O False Bool Balancer is active.
pretensionActive O False Bool Pretension is active.
balancerIpartDisabled O False Bool I-part of balancer is disabled.
invalidOperationMode O False Bool Invalid operation mode. Operation mode 4
(speed coupling) will be set internally.
invalidSlaveGearboxRatio O False Bool Invalid gear ratio slave.
invalidMasterGearboxRatio O False Bool Invalid gear ratio master.
speedCouplingActive O False Bool Only speed coupling is active.
externalSetpointActive O False Bool Speed setpoint from P1155 is active.
F51050Active O False Bool P21613 not connected.
F51050Active O False Bool P21614 not connected.
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 23
Table 6-3 Error code of parameter „errorID“

Error code Description
16#0000 No error occurred.
16#8090 You have not configured a module for the specified hardware identifier or
you have ignored the restriction concerning the length of consistent data, or
you have not specified a hardware identifier as an address at parameter LADDR .
16#8093 No device from which you can read consistent data exists for the hardware identifier. This
error code also occurs if the module does not have inputs.
16#80A0 An access error was detected when accessing the I/O.
16#80A1 Device not reachable. Drive not online or connection interrupted.
16#80B1 The length of the specified target range at parameter RECORD is shorter than the
configured user data length.
16#80C0 The data have not been read yet.
Table 6-4 Status code of parameter „status“

Status Description
code
16#7000 Function block is not working.
16#7001 First cycle of the function block.
16#7002 Function block is in cyclic operation.

16#8000 Function block is not working. Please check „errorID“.
16#8600 Application error.
Please consider the output parameter of the function block.
16#8640 Error with the telegram connection in the drive.
Please check the Bico connection of the telegram.
6.2 Interface description of the additional telegram

For the interface of FB38015 an additional telegram with 4/4 words is necessary.
The telegram must be created in the hardware configuration of the drive. The
control parameter of the DCC application must be manually connected to the
telegram, additionally.
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 24
Telegram 1 with additional telegram in the device configuration.
Receive direction in the drive
Send direction in the drive

6.3 Use of the LDCC_LoadControl block

The DCC charts was inserted in the project and the connection with the drive
parameter was done, like described in chapter 4. A standard telegram was
configured.
6.3.1 Configure additional telegram
Add an additional telegram 4/4 in the device configuration of TIA Portal.
Add an additional telegram 4/4 additionally to the standard telegram.
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 25
There must be added 4 words as actual value and as set point
6.3.2 Connection of additional telegram in drive.
You find the mask for Bico connection in Startdrive under the diagnostic view. Send
and receive parameter must be connected.
The parameter must be connected to the additional telegram.

The parameters must be connected as follows.

DCC-Parameter in slave Telegram interface of
Description
drive slave drive
P22102 CI: Control word P2050[offset]
P21514 CI: Operation mode P2050[offset + 1]
p21530 CI: Load factor P2050[offset + 2]
p21531 CI: Pretension P2050[offset + 3]
P22104 CO: Status word P2051[offset]
The length of the offset depends on the length of the used standard telegram.
6.3.3 Insert LDCC_LoadControl block in the project.
The control function block is delivered in the zipped library LSinaDCC.zal15_1. You
open the library out of the TIA Portal project. It is necessary to choose the right
data type. Then copy the control function block out of the library to the program
folder and do a function call in OB1.
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 26
Open global library and insert path of the library.

Choose the right type of file.
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 27
Do a function call in a cyclic OB and connect inputs and outputs of the function block.
You find the HarwareID for the function block in the device view of the drive (properties).
6.3.4 Functionality of the LDCC_LoadControl block.
The control function block will be enabled via the „enable“- input. The block reports
the faultless operation with the „valid“- output. The status-output reports cyclic
operation (16#7002). The operation mode is set by the „mode“- input. The adjusted
operation mode is immediately active. It is possible to switch the operation modes
on the fly.
Further optional functions:

1) Activate pretension (pretensionOn, Default: deactivated)
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 28
2) Deactivate I-Part of the balancer (disableIpart, Default: I-Part active).

3) Set pretension value (staticTorque, Default: 0%)
4) Set load distribution (loadFactor, Default 100% correspond to a load
distribution of 1:1)
The block outputs show the status of the “command function block” and were
described in chapter 6.1. When there is an error during write/read function, the
“error” - output is set and the“valid“- output is reset. The „errorID“-output shows a
fault number. When an error occur the function block must be disabled and
enabled again, to reset the “error” - output. In case of write/read fault the „error”-
output is set. Error in DCC-application is shown by the „status“-output. Detailed
error information shows the outputs of the block and the error messages in the
drive itself.
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 29
7 Appendix
7 Appendix
7.1 Function diagramms
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 30
7 Appendix
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 31
r22003 Gear Ratio invalid

[LS2010.7]
Gear Slave
<= 0
7 Appendix
p21520
1 F51052
Gear Master
<= 0
DCC Loadsharing
p21521
Bias factor [%] [0..1]
Entry-ID: 38470057,
[LS2010.7] p21642 Bias Level
[LS2070.2]
r22004 Master Gear Ratio invalid
Speed Transmission
V3.0,
1
CI: Master Speed Setpoint [0...1]

Speed Setpoint [RPM]
p21601 [LS2070.2]
11/2020
Master. r62
CI: Master Speed Reference [RPM]

p21609 r21900 CO: Master Speed Setpoint [RPM]
M.r2700
Pretension On
Torque Transmission [LS2010.4]
1
CI: Master Torque Setpoint [0...1] Droop factor[RPM/Nm]

Torque Setpoint [Nm] [LS2060.7]
p21602 Pretension Value [RPM]
[LS2060.2]
M.r1480 [LS2070.2]
CI: Static Torque [%]
r21902 CO: Master TorqueSetpoint [Nm] p21531 +
0%
0
CI: Master Reference Torque Static Torque [Nm]

[Nm] p21706 Pretension Value [NM]
Supplementry Torque [Nm]
p21610 Reference torque S [LS2080.2]
[LS2040.2]
M.r2703
CI: Master Speed Controller
Integrator Output [0...1] CO: Master Speed Controller Reference torque S
r21901
p21603 Integrator Output [Nm]
M. r1482
CI: Slave Speed Controller

Integrator Output [0...1] Load Factor
Slave Speed Controller Load factor [%]
p21604 Integrator Output [Nm] [LS2040.1]
p21522
S.r1482 [LS2060.2] [LS2060.2]
CO: Slave Speed Controller

r21664
Integrator Output [Nm] CI: Load factor [%]
CI: Slave Reference Torque [Nm] Slave Reference Torque p21530
p21612 [Nm] 100%
S.r2703 [LS2040.1]
[LS2050.2]
1 2 3 4 5 6 7 8
32
VisioPläneLoadSharing_V30_e
DO: SERVO, VECTOR n.vsd Function diagram
- LS2030 -
Sectional drive – Parameter_Signal Scaling 24.01.2020 V03.0 SINAMICS
CI: Speed Controller Integrator Setting Value [%]

7 Appendix
p1478[0]
Integralanteil Value 0 r21625 r21625
DCC Loadsharing
Entry-ID: 38470057,
BI: Speed Controller Set Integrator Value
V3.0,
p1477[0]
r21624
BO: Integrator set to zero and Freeze
11/2020
Torque Linking On
r21624
[LS2020.7] BI: Speed Controller hold Integrator
p1476[0]
r21624
Supplementary Torque
[Nm]
[LS2030.4]
CO: Linking Torque Value [Nm]
r21622
CI: Supplementary Torque 2
Linking Torque
Linking Torque CO: Linking Torque Value [0...1] P1513[0]]
Value
r21623 r21623
0
Load Factor
[LS2030.8]
Slave Torque Reference

[Nm]
[LS2030.4]
1 2 3 4 5 6 7 8
33
VisioPläneLoadSharing_V30_
DO: SERVO, VECTOR en.vsd Function diagram
- LS2040 -
Sectional drive – Torque Linking 24.01.2020 V03.0 SINAMICS
BI: Activates Travel to fix Stop

P1545[0]
Bias and Limiting On
r21641
[LS2020.7]
7 Appendix
DCC Loadsharing
CI: Slave Upper Torque Limit [%]
Entry-ID: 38470057,
p21613
CO: Slave Upper Torque Limit [Nm]
V3.0,
r21646
CO: Effective Upper Torque Limit [Nm]
11/2020
r21644
CI: Torque Limit Upper Scaling without Offset
CO: Effective Upper Torque Limit [0..1] p1552

r21643 r21643
Slave Reference Torque [Nm]

[LS2030.5]
Compensation [Nm]
[LS2060.7]
CI: Torque Limit Lower Scaling without Offset
CO: Effective Lower Torque Limit [0..1] p1554

r21647 r21647
CO: Effective Lower Torque Limit [Nm]

r21648
CO: Slave Lower Torque Limit

r21649
CI: Slave Lower Torque Limit [%]
p21614
1 2 3 4 5 6 7 8
34
- LS2050 -
Sectional drive – Bias und Limiting 24.01.2020 V03.0 SINAMICS
7 Appendix
Droop [%] CO:Droop [% ]
DCC Loadsharing
Slave Speed Controller Integrator
Entry-ID: 38470057,
r21666
Output [Nm]
[LS2030.5]
V3.0,
Droop factor [%]
[LS2030.6]
11/2020
- CO: Applied Droop and Compensation [%]
+ r21667
0
Droop Factor [%] +
p21662 LS2070.2
1
Applied Droop factor

[% or 1]
Droop and Compensation On
[LS2020.7]
LS2050.2
Torque Setpoint [Nm] CO: Compensation [% ]
[LS2030.5]
r21665
Compensation [%]
Load Factor
[LS2030.8]
Compensation
[LS2050.2]
1 2 3 4 5 6 7 8
35
- LS2060 -
Sectional drive – Droop and Compensation 24.01.2020 V03.0 SINAMICS
Mode selection valid

7 Appendix
[LS2020.7]
DCC Loadsharing
CI: Slave Speedsetpoint Telegram [0..1]
Speed Setpoint [RPM]
Entry-ID: 38470057,
[LS2030.5] p21518
S. r2050[1] External Setpoint ON
[LS2020.7]
V3.0,
Bias and Limitation ON
[LS 2020.7] CI: Speed Controller Speed Setpoint 2
CO: Common Speed setpoint [%] p1160[0]
+ - + r21801 r21801
11/2020
Bias Level [1...2]
[LS2030.8]
CI: Slave Reference Speed

p21611
S.r2700
Balance controller ON
[LS2020.7]
Pretension Value [RPM]

[LS2030.7]
Droop and Compensation ON +

[LS2020.7]
Droop and Compensation [RPM]

[LS2060.7]
Balance controller
speedsetpoint [%]
[LS2080.7]
Filter time [ms]
p21529
40
1 2 3 4 5 6 7 8
36
- LS2070 -
Sectional drive – Speed Setpoint 24.01.2020 V03.0 SINAMICS
[LS2020.7]
P-Gain
7 Appendix
p21525
DCC Loadsharing
0.1
Entry-ID: 38470057,
Integrator time [ms]
V3.0,
p21526
2000
Upper limit [%]
11/2020
p21527
10.0
Lower limit [%]
p21528
-10.0
CI: Master torquevalue[%] Reference torque M Load factor

p21606 [LS 2030.8]
M.r79
CI: Slave torquevalue [%] Reference torque S

p21605
PI-controller Balance controller speedsetpoint
S.r79 -
[LS2070.2]
[LS2020.7]
Pretension Value [Nm]

[LS2030.8] Referenz speed S
BI: Controller enable
p21517 CO: Speedsetpointl RPM]
S. r898.0 r21632
Deactivate integrator
[LS2010.4]
1 2 3 4 5 6 7 8
37
- LS2080 -
Balance controller 24.01.2020 V03.0 SINAMICS
7 Appendix
7.2 Parameterlist
r21500 LS LoadSharing-Version
SERVO, VECTOR Can be changed: U/T Calculated: - Access stage: 1
Data type: DINT Dynamic index: - Function chart:
P-Group: - Units group: - Units selection: -
No for motor type: - Expert list: 1
Min Max Factory setting
3.0
Description: Shows the software version of the DCC chart for the "Load balance control"
r21501 Entry ID
38470057
Description: Shows the article ID of the DCC chart for the "Load balance control"
r21503 Internal-ID

76837271
Description: Shows the Internal ID of the DCC chart for the "Load balance control"
p21512 Operating mode [0-5]

Data type: INT Dynamic index: - Function chart: LS2010
0
Description: [0] Select mode ""Torque linking" for the slave.
[1] Select mode ""Bias and limiting" for the slave.
[2] Select mode ""Droop and compensation" for the slave.
[3] Select mode ""Balancer" for the slave.
[4] Select mode ""Speed coupling" for the slave.
[5] Select mode "External setpoint" for the slave.
r21513 Connector Operating mode [0-5]

0
Description: Connector for Operating Mode P21512
p21514 CI: Connector Operating mode [0-5]
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 38
7 Appendix

r21513
[0] Select mode ""Torque linking" for the slave.
Description:
[1] Select mode ""Bias and limiting" for the slave.
[2] Select mode ""Droop and compensation" for the slave.
[3] Select mode ""Balancer" for the slave.
[4] Select mode ""Speed coupling" for the slave.
[5] Select mode "External setpoint" for the slave.
p21515 BI: Pretension ON/OFF

Data type: BOOL Dynamic index: - Function chart: LS2010
-
Description: Activates the optional "Pretension" functionality
Dependency: see also: p21512
p21516 BI: Balancer disable I-Part


-
Description: Disable I-Part in operating mode "Balancer".
p21517 BI: Slave OFF1

r898.0
Description: Shows operating state of the slave.
p21518 CI: Slave speed setpoint from telegram [0..1]

r2050[1]
Description: Speed setpoint from telegram".
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 39
7 Appendix
p21520 Gearbox ratio, slave drive load

Data type: REAL Dynamic index: - Function chart: LS2030

- - 1
Description: Gearbox ratio between the slave and the load
Note: An error is signaled if the gearbox ratio is zero.
p21521 Gearbox ratio master-load

- - 1
Description: Gearbox ratio between the master and the load
Note: An error is signaled if the gearbox ratio is zero.
p21522 Load Factor [%]

-3,40282E+43 3,40282E+43 100.0
Load factor: Defines how much torque the drive should provide compared to the master (ratio). The sign has
Description:
no meaning. 1 means 100%, 0.1 means 10%. If zero, then it is assumed that the master torque input is zero
Note: A load factor of 100% means that the slave should generate the same torque as the master.
p21523 Pretension Torque [Nm]

SERVO, VECTOR Can be changed: T Calculated: - Access stage: 1
-3,40282E+43 3,40282E+43 -
Pretension torque, e.g. to compensate gearbox backlash or slip. The value is only adjusted in Mode 3. In
Description:
Mode 0-2 it triggers only a value proportionally to P21523.
Note: The pretension torque reduces the drive torque that is available.
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 40
7 Appendix
p21525 P-gain balancer

-3,40282E+43 3,40282E+43 0.1
Description: Gain off the balancer.
p21526 Integral time balancer

-3,40282E+43 3,40282E+43 2000[ms]
Description: Integral time off the balancer.
p21527 Upper limit balancer


-3,40282E+43 3,40282E+43 10%
Description: Upper limit off the balancer. Value relate to reference speed of slave.
p21528 Lower limit balancer

-3,40282E+43 3,40282E+43 -10%
Description: Lower limit off the balancer. Value relate to reference speed of slave.
p21529 Balance controller filter time

-3,40282E+43 3,40282E+43 40.0 ms
Description: Filter time of PT1 Filter for additional speed setpoint B. Active with Balancer and Droop/Compensation
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 41
7 Appendix
p21530 CI: Load Factor [%]

- - 100.0
Description: Load ratio between master and slave
p21531 CI: Static Torque [%]

- - 0.0
Description: Additional torque for slave
p21601 CI: Master speed Setpoint


-
Description: Scales the speed setpoint of the master drive. This input should be connected to parameter r62 of the master
Recommendation: Must be connected to master parameter r62
Dependency: see also: r21900, p21520, p21521, p21609
p21602 CI: Master torque Setpoint controller

Description: The torque setpoint of the master drive must be connected at this input
Dependency: see also: r79 in the master drive
Note: This signal is used for the operating modes "Droop and compensation" and "Bias and limiting"
p21603 CI: Master speed controller, integrale component

-
Master speed control integral component for the operating mode "Torque coupling" as supplementary torque in
Description:
the slave drive.
Dependency: see also: r1482
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 42
7 Appendix
p21604 CI: Slave speed controller, integrale component

-
Description: Scaled integral component of the slave drive speed controller. This is used to calculate "droop"
Recommendation: Must be connected to drive parameter r1482
Dependency: see also: r1482, p21512, p21664
p21605 CI: Slave torque Setpoint

-
Description: The torque setpoint of the slave drive must be connected at this input
Recommendation: Must be connected to slave parameter r79
Dependency: see also: "Balancer"
p21606 CI: Master torque Setpoint

-
Description: The torque setpoint of the master drive must be connected at this input
Dependency: see also: "p21512
p21609 CI: Master Reference speed [RPM]

-
Reference speed of the master This value is required to convert a scaled speed setpoint to a physical variable
Description:
in [RPM]
Dependency: see also: p21601, master drive parameter r2700
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 43
7 Appendix
p21610 CI: Master reference torque [Nm]

-
Reference torque of the master This value is required to convert a scaled torque setpoint to a physical variable
Description:
in [Nm]
Dependency: see also: p21602, p21603, master parameter p2703
p21611 CI: Slave reference speed

-
Reference speed of the slave. This value is required to convert a scaled speed setpoint to a physical variable in
Description:
[RPM]
Recommendation: Must be connected to r2700
Dependency: see also: r21801, r21802, r2700
p21612 CI: Slave Reference torque [Nm]

-
Reference torque of the slave. This value is required to convert a scaled torque setpoint to a physical variable
Description:
in [Nm]
Recommendation: Must be connected to r2703
Dependency: see also: r2703, p21604
p21613 CI: Slave upper torque limit, [%]

-
Description: Scaled torque limit of the slave. This input is required for the "Bias and torque limiting" operating mode.
Recommendation: Must be connected to parameter r1534 (SERVO) or r1520 (VECTOR)
Dependency: see also: p21646, p21513, p22102
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 44
7 Appendix
p21614 CI: Slave lower torque limit, [%]

-
Description: Scaled torque limit of the slave. This input is required for the "Bias and torque limiting" operating mode.
Recommendation: Must be connected to parameter r1535 (SERVO) or. r1521 (VECTOR).
r21621 BO: Torque Linking ON

-
Description: Shows the exclusive selection of the operating mode "Torque linking"
Dependency: see also: p21512;
r21622 CO: Linking Torque [Nm]


-
Supplementary torque from the master (integral component) scaled with the load factor. This is used in the
Description:
"Torque linking" operating mode.
r21623 CO: Linking Torque

-
Scaled supplementary torque from the master scaled using the load factor. This is used in the "Torque
Description:
coupling" operating mode. Must be connected to p1513 of the slave.
Dependency: see also: r21622, p1513
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 45
7 Appendix
r21624 BO: Set and hold speed controller integral component

-
If the "Torque linking" operating mode is selected, using this BO, the speed controller integral component is
Description:
held and set to zero.
Recommendation: Must be connected to p1477 and p1476 of the slave drive
Dependency: see also: p21621, p21623, p21625, p1477, p1476
r21625 CO: Speed controller integrator setting value

-
Speed controller integrator setting value – this output is always zero and must be connected to p1478. This is
Description:
used in the "Torque coupling" operating mode.
p21631 BO: Balancer ON

-
Description: Shows the exclusive selection of the "Balancer" operating mode
Dependency: see also: P21512
p21632 CO: Slave additional speed [RPM)

-
Description: Shows slave additional speed in RPM.
Dependency: see also: P21512
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 46
7 Appendix
r21641 BO: Bias And Limitation ON

-
Description: Shows the exclusive selection of the "Bias and limiting" operating mode
p21642 Bias factor [%]

-3,40282E+43 3,40282E+43 5%
Bias factor of the "Bias and limiting" operating mode. This is used to overcontrol
Description:
the speed setpoint with a certain percentage. The value is specified as a percentage
The Bias factor should be set to approximately 5% so that no excessive
Recommendation:
speed deviations (> 5%) can occur.
r21643 Effective upper torque limit [0..1]

-
Scaled torque limit for the "Bias and limiting" operating mode. The calculated torque limit is scaled with the
Description:
upper torque limit (p21646)
Recommendation: Must be connected to p1552 in the slave.
Dependency: see also: r1534, p21646, p21644, p21665
r21644 CO: Effective upper torque limit [Nm]

-
Description: The effective torque limit in the "Bias and limiting" operating mode.
Dependency: see also: p21641, p21643, p21646, p1552
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 47
7 Appendix
r21646 CO: Slave upper Torque Limit [Nm]

-
Description: Upper torque limit. Is used to scale the effective upper torque limit.
Dependency: see also: p21612, P1520; r1534, p21643,
r21647 Effective lower torque limit [0..1]
-
Scaled torque limit for the "Bias and limiting" operating mode. The calculated torque limit is scaled with the
Description:
lower torque limit (p21649)
Recommendation: Must be connected to p1554 in the slave.
Dependency: see also: P1521, r1535, p21649, p21648, p21665
r21648 CO: Effective lower torque limit [Nm]


-
Description: The effective torque limit in the "Bias and limiting" operating mode.
Dependency: see also: p21641, p21647 p1554
r21649 CO: Slave lower Torque Limit [Nm]

-
Description: Lower torque limit. Is used to scale the effective lower torque limit.
Dependency: see also: p21614, r1521, p1535, p21647; p21648;
r21661 BO: Drop and Compensation ON

-
Description: Shows the exclusive selection of the "Droop and compensation" operating mode
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 48
7 Appendix
p21662 : Droop factor [RPM/Nm]

-3,40282E+43 3,40282E+43 -5%
Description: In the "Droop and compensation" operating mode, the droop factor is used to process the speed setpoint. The
same factor is also used to compensate the speed setpoint
Recommendation: Generally, low droop factors from 2% to 5% are enough.
r21664 CO: Slave speed controller integral component [Nm]

-
Description: Integral component of the slave drive speed controller
Dependency: see also: p21604, p21612, r1482, r2703
r21665 CO: Compensation [%]


-
The compensation value is calculated from the torque setpoint of the master multiplied by the droop factor and
Description:
the load factor (operating mode "Droop and compensation").
Dependency: see also: p21662, p21522, p21602, p21902
r21666 Droop [%]

-
The droop is incorporated in the "Droop and compensation" operating mode load dependent and negative in
Description:
the slave speed setpoint. It is calculated from the integral component of the slave speed controller multiplied by
the droop factor.
Dependency: See also: p21662, p21666
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 49
7 Appendix
r21667 Droop compensation [RPM]

-
Description: Difference between compensation and droop in [RPM], which is added to the slave speed setpoint.
Dependency: See also: p21665, p21666
r21801 CO: Common Speed Setpoint A [0…1]

-
Description: Common Slave speed setpoint
Recommendation: Must be connected to p1160 of the slave
Dependency: see also: p21611, p1155
r21900 CO: Master Speed Setpoint [RPM]


-
Description: The master speed setpoint is emulated here.
r21901 CO: Master speed controller integral component [Nm]

-
Description: The integral component of the master drive speed controller is emulated here.
r21902 CO: Master Torque Setpoint [Nm]

-
Master torque setpoint. Is calculated using the scaled value in p21602 and the master reference torque in
Description:
p21610.
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 50
7 Appendix
r22001 BO: Compensation is not active

-
Description: Compensation is inactive – status bit
r22002 BO: Invalid operating mode

-
Description: No exclusive operating mode selected - status bit
r22003 BO: Invalid gearbox ratio slave load


-
Description: Specified gearbox ratio between the slave drive and load is invalid (zero or negative) - status bit
r22004 BO: Invalid gearbox ratio master-load

-
Description: Specified gearbox ratio between the slave drive and load is invalid (zero or negative) - status bit
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 51
7 Appendix
r22100 CO: Internal control word

Data type: WORD Dynamic index: - Function chart: LS2010
-
Description: Internal control word - displays the control word internally generated from control bits p21515 to p21516
Bitfield: Bit Signal name 1-Signal 0-Signal FP
00 Pretension ON See p21515 See p21515
01 Balancer disable I-Part See p21516 See p21516 LS2010
02 Reserved LS2010
03 Reserved
04 Reserved
05 Balancer
06 Reserved
07 Reserved - -
08 Reserved - -
09 Reserved - -
10 Reserved - -
11 Reserved - -
12 Reserved - -
13 Reserved - -
14 Reserved - -
15 Reserved - -
p22102 CI: Command word

Data type: WORD Dynamic index: - Function chart: LS2010
-
Control word: In the factory setting, r22100 (internal control word) is connected at this input, i.e. the application
Description:
is controlled via binary inputs. Alternatively, another source can be used in the control word (e.g. via fieldbus).
The bit assignment is shown at r22100. When using a source other than r22100, binary inputs (p21515 to
p21516) are disabled.
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 52
7 Appendix
7.3 Application Support

Siemens AG
Digital Industries
Factory Automation
Production Machines
DI FA PMA APC
Frauenauracher Str. 80
D-91056 Erlangen, Germany
mailto: [email protected]
7.4 Links and Literature

Table 7-1
No. Topic
\1\ Siemens Industry Online Support
https://support.industry.siemens.com
\2\ Link to this entry page of this application example
https://support.industry.siemens.com/cs/ww/en/view/38470057
\3\
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 53
7 Appendix
7.5 Change documentation
Table 7-2
Version Date Modifications
V1.0 2010-01 First release
V1.0.2 2010-07 Update
V2.0 2015-09 Complete revision and simplification
V2.1 2017-03 Implementation of a rise limitation during switchover for
speed setpoint (LS2070).
Change of droop factor (P21662) from RPM/Nm to %.
Sign error with negative torque setpoint was solved
(Operating mode: Droop and Compensation).
False parameter descriptions in the manual were corrected.
V2.2 08/2019 Implementation of function "Balancer".
Change of "Mode selection" (Integer instead Bool with
parameter P21519)
Implementation of an output filter for "Balancer" and "Droop
and Limitation" (P21529)
The application was supplemented with DCC-Charts for
STARTDRIVE.
V3.0 11/2020 Implementation of function “Speed setpoint coupling” and
“External speed setpoint”. Change of “Mode selection”.

P21512 instead of P21519. Operation modes are directly
active. There is no additional “Enable Bit”. Pretension
P21523 now works in Mode 3, too. Connectors have been
added to control the application via an “S7 Control Block”. A
“S7 Control Block” FB38015 was added to the application
DCC Loadsharing
Entry-ID: 38470057, V3.0, 11/2020 54

DCC LoadSharing V3 0 en

Uploaded by

Copyright:

Available Formats

DCC LoadSharing V3 0 en

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

DCC LoadSharing V3 0 en

Uploaded by

Copyright:

Available Formats

SINAMICS S120:

4.1 For your safety ................................................................................... 14

1.1 Design and structure

1.2 Load sharing

2.2 Mandatory Hardware- and Software components

A DCC engineering license “SINAMICS MLFB 6SL3070-4FA01-0XA5

of the DCC charts for STARTER and plan

3.1.1 Torque linking

3.1.2 Bias and Limitation

Friction torque and accelerating torque precontrol should be realized as accurately

3.1.3 Droop and Compensation

normal PI-Control (1)

PI Control with Droop

Nominal Torque Mn Torque

PI Control with droop (2)

Nominal Torque Mn Torque

3.1.5 Speed coupling

3.1.6 External speed setpoint

3.2 Faults and alarms

F51050 Upper torque limit not connected

F51051 Lower torque limit not connected

F51052 Invalid gearbox ratio

A51060 An invalid operating mode was selected

A51061 Compensation is not active

Pictogram, signal word and text

WARNING indicates that death or severe personal injury may result if

4.1.2 Responsibilities of the operating personnel

• All forms of manipulation of devices that serve to ensure the proper

4.2 Installing the application

Inserting the DCC plan into your STARTER project

Inserting the DCC plan into your STARTER project

Choose "StartdriveLoadsharingV3_0.dcc". After the import, the plans occur under

p1160 CI: Speed controller, common speed setpoint r21801

4.3 Notes on computation time and memory load levels

Execution groups "Control" and "Setpoint"/"LoadsharingA" and

sequence on a Control Unit is defined by the DO number or can be adapted by

4.3.2 Memory usage

Because the memory load there is no limitation of maximum number of axis,

5 Using the application

6 Control function block FB38015

Table 6-1 Inputs of FB38015

Table 6-2 Outputs of FB38015

valid O False Bool Function block works without error.

Table 6-3 Error code of parameter „errorID“

Table 6-4 Status code of parameter „status“

16#7002 Function block is in cyclic operation.

6.2 Interface description of the additional telegram

Telegram 1 with additional telegram in the device configuration.

Receive direction in the drive

Send direction in the drive

6.3 Use of the LDCC_LoadControl block

6.3.1 Configure additional telegram

Add an additional telegram 4/4 in the device configuration of TIA Portal.

Add an additional telegram 4/4 additionally to the standard telegram.

There must be added 4 words as actual value and as set point

6.3.2 Connection of additional telegram in drive.

The parameter must be connected to the additional telegram.

The parameters must be connected as follows.

6.3.3 Insert LDCC_LoadControl block in the project.