DCC Programming
DCC Programming
Introduction 1
Safety instructions and
industrial security 2
SINAMICS/SIMOTION
DCC editor functionality 3
Motion Control
SINAMICS/SIMOTION DCC Editor
DCC for SINAMICS 4
Description
DCC for SIMOTION 5
Programming and Operating Manual
Appendix A
06/2021
6SL3097-5AN00-0BP2
Legal information
Warning notice system
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent damage
to property. The notices referring to your personal safety are highlighted in the manual by a safety alert symbol, notices
referring only to property damage have no safety alert symbol. These notices shown below are graded according to
the degree of danger.
DANGER
indicates that death or severe personal injury will result if proper precautions are not taken.
WARNING
indicates that death or severe personal injury may result if proper precautions are not taken.
CAUTION
indicates that minor personal injury can result if proper precautions are not taken.
NOTICE
indicates that property damage can result if proper precautions are not taken.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will be
used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to property
damage.
Qualified Personnel
The product/system described in this documentation may be operated only by personnel qualified for the specific
task in accordance with the relevant documentation, in particular its warning notices and safety instructions.
Qualified personnel are those who, based on their training and experience, are capable of identifying risks and
avoiding potential hazards when working with these products/systems.
Proper use of Siemens products
Note the following:
WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended or
approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and maintenance
are required to ensure that the products operate safely and without any problems. The permissible ambient
conditions must be complied with. The information in the relevant documentation must be observed.
Trademarks
All names identified by ® are registered trademarks of Siemens AG. The remaining trademarks in this publication may
be trademarks whose use by third parties for their own purposes could violate the rights of the owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software described.
Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the information in this
publication is reviewed regularly and any necessary corrections are included in subsequent editions.
SIMOTION Documentation
An overview of the SIMOTION documentation can be found in the SIMOTION Documentation
Overview document.
This documentation is included as electronic documentation in the scope of delivery of
SIMOTION SCOUT. It comprises ten documentation packages.
The following documentation packages are available for SIMOTION product version V5.4.3:
• SIMOTION Engineering System Handling
• SIMOTION System and Function Descriptions
• SIMOTION Service and Diagnostics
• SIMOTION IT
• SIMOTION Programming
• SIMOTION Programming - References
• SIMOTION C
• SIMOTION P
• SIMOTION D
• SIMOTION Supplementary Documentation
SINAMICS documentation
The SINAMICS documentation is organized on 2 levels:
• General documentation/catalogs
• Manufacturer/service documentation
An overview of the current documentation in the respective available languages can be found
on the Internet:
http://www.siemens.com/motioncontrol
Select the menu items "Support" --> "Technical Documentation" --> "Overview of Publications".
Information on the range of training courses and FAQs (Frequently Asked Questions) is available
on the Internet:
http://www.siemens.com/motioncontrol
Select the menu item "Support".
Additional information
Click the following link to find information on the following topics:
• Ordering documentation / overview of documentation
• Additional links to download documents
• Using documentation online (find and search manuals/information)
http://www.siemens.com/motioncontrol/docu
My Documentation Manager
Click the following link for information on how to compile documentation individually on the
basis of Siemens content and how to adapt it for the purpose of your own machine
documentation:
https://support.industry.siemens.com/My/ww/en/documentation
Training
Click the following link for information on SITRAIN - Siemens training courses for automation
products, systems and solutions:
http://www.siemens.com/sitrain
FAQs
Frequently Asked Questions can be found in SIMOTION Utilities & Applications, which are
included in the scope of delivery of SIMOTION SCOUT, and in the Service&Support pages in
Product Support:
http://support.automation.siemens.com
Technical support
Country-specific telephone numbers for technical support are provided on the Internet
under Contact:
http://www.siemens.com/automation/service&support
Preface ................................................................................................................................................... 3
1 Introduction ......................................................................................................................................... 13
2 Safety instructions and industrial security .......................................................................................... 17
2.1 Fundamental safety instructions......................................................................................... 17
2.1.1 General safety instructions................................................................................................. 17
2.1.2 Warranty and liability for application examples ................................................................... 17
2.1.3 Security information .......................................................................................................... 17
2.2 Use write and know-how protection ................................................................................... 19
2.3 Industrial Security Configuration Manual ............................................................................ 20
3 DCC editor functionality ...................................................................................................................... 21
3.1 Overview ........................................................................................................................... 21
3.2 Requirement...................................................................................................................... 23
3.3 New device versions .......................................................................................................... 25
3.4 Establish the project requirements ..................................................................................... 26
3.4.1 Create a project ................................................................................................................. 26
3.4.2 Inserting a device into a project.......................................................................................... 27
3.4.3 Inserting the DCC chart in a project .................................................................................... 28
3.4.4 Inserting a new subchart.................................................................................................... 33
3.4.5 Inserting new chart partitions ............................................................................................ 34
3.4.6 View and representation .................................................................................................... 34
3.5 Handling blocks ................................................................................................................. 36
3.5.1 Introduction....................................................................................................................... 36
3.5.2 Inserting blocks in the DCC editor....................................................................................... 36
3.5.3 Inserting text ..................................................................................................................... 38
3.5.4 Specifying execution properties ......................................................................................... 39
3.5.5 Editing block connections .................................................................................................. 40
3.5.5.1 General ............................................................................................................................. 40
3.5.5.2 Block connection properties ............................................................................................... 40
3.5.6 Interconnecting blocks....................................................................................................... 42
3.5.7 Data type abbreviation in the DCC for connection and transformer blocks ........................... 43
3.5.8 Interconnection to chart connections ................................................................................. 44
3.5.9 Interconnection to global operands in DCC SIMOTION......................................................... 45
3.5.10 Deleting blocks .................................................................................................................. 45
3.5.11 Rearranging parameter numbers ........................................................................................ 46
3.5.12 Publishing all connections.................................................................................................. 47
3.5.13 Revoking connections ........................................................................................................ 50
3.6 Compiling.......................................................................................................................... 52
3.6.1 Consistency check without code generation ....................................................................... 52
3.6.2 Compiling the DCC in the DCC editor .................................................................................. 53
3.6.3 Error log ............................................................................................................................ 54
4.2.14 Interconnection to the BICO parameters of the basic system in DCC SINAMICS................... 184
4.2.15 BICO interconnections and reading back parameters......................................................... 185
4.2.16 Record with the trace signals from the DCC chart.............................................................. 186
4.2.17 Comparing DCC charts ..................................................................................................... 188
4.2.18 Archiving a project ........................................................................................................... 189
4.2.19 Creating documentation .................................................................................................. 189
4.2.20 Update to a new SINAMICS version................................................................................... 191
4.3 Connecting the DCC to the drive ...................................................................................... 192
4.3.1 Overview ......................................................................................................................... 192
4.3.2 Calculating a DCC chart with per-unit variables ................................................................. 192
4.3.3 Calculating a DCC chart with absolute variables ................................................................ 194
4.3.3.1 Example 2.1 (interconnecting input value) ....................................................................... 194
4.3.3.2 Example 2.2 (interconnecting output value) ..................................................................... 196
4.3.4 Interconnecting DCC signals with communication interfaces IF1 and IF2........................... 196
4.3.4.1 Preliminary remark........................................................................................................... 196
4.3.4.2 Interconnecting received process data with DCC ............................................................... 197
4.3.4.3 Interconnecting sent process data with DCC ..................................................................... 197
4.4 DCC SINAMICS specifications ............................................................................................ 198
4.4.1 Rules for assigning names in the DCC editor ..................................................................... 198
4.4.2 Field/name lengths and conventions ................................................................................ 199
4.4.3 Representation of the dynamic value display .................................................................... 199
5 DCC for SIMOTION ............................................................................................................................. 201
5.1 Overview ......................................................................................................................... 201
5.1.1 Introduction..................................................................................................................... 201
5.1.2 Software requirements .................................................................................................... 201
5.1.3 SIMOTION system integration........................................................................................... 202
5.1.3.1 Execution level, execution group and execution sequence ................................................ 202
5.1.3.2 HMI variables (publishing of variables and @ variables)..................................................... 204
5.1.3.3 Interconnecting with SIMOTION variables......................................................................... 206
5.1.4 DCC and SIMOTION trace ................................................................................................. 209
5.2 Working with DCC SIMOTION ........................................................................................... 210
5.2.1 Preliminary remarks on configuration ............................................................................... 210
5.2.2 Creating a project ............................................................................................................ 211
5.2.3 Inserting a chart .............................................................................................................. 211
5.2.4 Inserting blocks ............................................................................................................... 213
5.2.5 Interconnecting blocks..................................................................................................... 214
5.2.6 Parameterizing block connections in the chart .................................................................. 214
5.2.7 Structures for DCB block connections ............................................................................... 216
5.2.8 Default connection values for delta downloads................................................................. 221
5.2.9 Compiling the DCC in the DCC editor ................................................................................ 222
5.2.10 Loading the compiled DCC ............................................................................................... 224
5.2.11 Starting the CPU .............................................................................................................. 224
5.2.12 Enable attribute, execution groups ................................................................................... 224
5.2.13 Creating documentation .................................................................................................. 224
5.3 DCC SIMOTION specifications ........................................................................................... 226
5.3.1 Rules for assigning names in the DCC editor ..................................................................... 226
5.3.2 Field/name lengths and conventions ................................................................................ 227
5.3.3 Representation of the dynamic value display .................................................................... 228
5.3.4 Displaying operands......................................................................................................... 228
DCC comprises the DCC editor and the DCB library (block library with standard DCC blocks).
The user-friendly DCC editor enables easy graphic configuration and a clear representation of
control loop structures as well as a high degree of reusability of existing charts.
The open-loop and closed-loop control functionality is defined by using multi-instance-capable
blocks (Drive Control Blocks, DCBs) from a pre-defined library (DCB library) that are selected
and graphically linked by dragging and dropping. Test and diagnostic functions allow
verification of program behavior or the identification of causes in the event of errors.
The block library contains a large selection of control, arithmetic and logic blocks as well as
extensive open-loop and closed-loop control functions.
All commonly used logic functions are available for selection (AND, XOR, On/Off delay, RS flip-
flop, counters, etc.) for the logic operation, evaluation and acquisition of binary signals. Diverse
arithmetic functions such as absolute-value generation, dividers and minimum/maximum
analysis are available for monitoring and evaluating numeric variables. In addition to the drive
control, axial winder functions, PI controllers, ramp-function generators or sweep generators
can be configured simply and without problem.
Almost unlimited programming of control structures is possible in conjunction with the
SIMOTION motion control system. These can then be combined with other program sections to
form an overall program.
Drive Control Chart for SINAMICS drives also provides a convenient basis for resolving drive-level
open-loop and closed-loop control tasks directly in the converter. This results in further
adaptability of SINAMICS for the tasks set. On-site processing in the drive supports modular
machine concepts and results in increased overall machine performance.
• With SINAMICS, DCC can be activated simultaneously on several drive objects (DOs) on a
drive unit. With SIMOTION, several DCC charts can be created in a program container.
• Block library with management, arithmetic, control, logic and complex blocks.
• Graphic component connection editor with various editing, macro, help, search, comparison
and print functions.
• Simple configuration of axial winder functions, PI controller, ramp-function generator or
sweep generator.
• Execution environment for SIMOTION with sampling times that can be selected and mixed,
and consistent data transfer between sampling times.
• Execution environment for SINAMICS with the option of embedding technology in SINAMICS
using BICO technology so that applications can be set via configured parameters. Up to ten
different sampling times can be configured.
• Diagnostics environment with signal display, diagnostic and trace functions.
• Scalability with different performance features and quantity structures in DCC SIMOTION and
DCC SINAMICS.
Note
The DCC editor is a programming system based on CFC (Continuous Function Chart). The
following sections describe the principles of DCC operation that have not already been
covered in the manual titled "CFC Manual for S7".
Note
Further references for the DCC editor:
SINAMICS/SIMOTION Function Manual, Description of the standard DCC blocks
SIMOTION SINAMICS
System integration Via interconnection to variables of the Via adjustable parameter or interconnec‐
basic system tion via BICO parameter to the basic sys‐
tem
Execution system Any number of execution groups that Maximum of ten execution groups that
can be assigned five time slices (depend‐ can be assigned ten different sampling
ing on the system cycle clocks) times
Consistency in the data transfer Consistent data transfer also across the Consistency in the data transfer must be
time slices established by the user, when required,
by means of standard blocks (SAH_X)
Scope of standard blocks See SINAMICS/SIMOTION Function Man‐ See SINAMICS/SIMOTION Function Man‐
ual, Description of the standard DCC ual, Description of the standard DCC
blocks blocks
WARNING
Danger to life if the safety instructions and residual risks are not observed
If the safety instructions and residual risks in the associated hardware documentation are not
observed, accidents involving severe injuries or death can occur.
• Observe the safety instructions given in the hardware documentation.
• Consider the residual risks for the risk evaluation.
WARNING
Malfunctions of the machine as a result of incorrect or changed parameter settings
As a result of incorrect or changed parameterization, machines can malfunction, which in turn
can lead to injuries or death.
• Protect the parameterization against unauthorized access.
• Handle possible malfunctions by taking suitable measures, e.g. emergency stop or
emergency off.
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 (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
under
https://www.siemens.com/industrialsecurity (https://new.siemens.com/global/en/products/
services/cert.html#Subscriptions).
Further information is provided on the Internet:
Industrial Security Configuration Manual (https://support.industry.siemens.com/cs/ww/en/
view/108862708)
WARNING
Unsafe operating states resulting from software manipulation
Software manipulations, e.g. viruses, Trojans, or worms, can cause unsafe operating states in
your system that may lead to death, serious injury, and property damage.
• Keep the software up to date.
• Incorporate the automation and drive components into a holistic, state-of-the-art industrial
security concept for the installation or machine.
• Make sure that you include all installed products into the holistic industrial security concept.
• Protect files stored on exchangeable storage media from malicious software by with suitable
protection measures, e.g. virus scanners.
• On completion of commissioning, check all security-related settings.
WARNING
Danger to life through manipulation of DCC charts and DCC libraries
The use of unprotected DCCs and DCC libraries entails a higher risk of manipulation of DCCs,
DCC libraries and backup files.
• Protect important DCCs and DCC libraries via "Know-how protection programs" or "Know-
how protection drive units" in SCOUT or STARTER. Assign a strong password to prevent
manipulation.
• Therefore, for "Know-how protection programs" or "Know-how protection drive units", use
passwords which include at least eight characters, upper and lower case letters, numbers,
and special characters.
• Make sure that only authorized personnel can access the passwords.
• Protect the backup files on your file system using a write protection.
'&&&)&
$GG
0XO
&RQILJXULQJ &RPSLOLQJ
6&28767$57(5
%ORFNW\SHLPSRUW /RDG
6,027,21'&%OLEUDU\ 6,027,21
6,1$0,&6'&%OLEUDU\ 6,1$0,&6
1. When a new chart is created, the block types are taken from the device-specific block library
and inserted in the DCC editor's block manager.
2. The DCC editor is used to create charts, in which you can insert, parameterize and
interconnect blocks.
3. When you compile the charts, an intermediate code is created.
4. This is downloaded to the device or drive unit using STARTER/SCOUT.
3.2 Requirement
This description refers to the following software versions of the devices and engineering
systems:
• DCC V3.4.2.0
• SIMOTION P, C, D as of Version 5.3.1
• SINAMICS Integrated of the SIMOTION D as of Version 5.2
• SINAMICS S120, S150, G130, G150 as of Version 5.2
• SINAMICS MV as of Version 4.8.2
• SINAMICS DCM as of Version 1.5
Except for the utilization display, the SINAMICS DC MASTER as of Version 1.4 supports the
same function scope as SINAMICS S120 as of Version 4.7. Detailed information about the
SINAMICS DC MASTER Version 1.4 can be found in the SINAMICS DC MASTER 6RA80 DC
Converters Operating Instructions, 01/2014 Edition
• SINAMICS DCP as of Version 1.2
• SIMOTION SCOUT Version V5.4.3
• STARTER Version V5.4.2
• Required CFC versions for DCC V3.4.2.0:
– STARTER: CFC V9.0
– SIMOTION SCOUT: CFC V9.0
• Required engineering license for DCC V3.4.2.0:
– DCC SINAMICS: CFC for SINAMICS V7.1, V8.0, V8.1, V8.2 or V9.0
– DCC SIMOTION: CFC for SIMOTION V7.1, V8.0, V8.2 or V9.0
Note
If errors occur when charts are being compiled in SIMOTION SCOUT/STARTER, it is possible to
generate a comprehensive error report by compiling them again in the DCC editor. To do this,
activate Display all messages with 'Save and compile changes' on the Compiler tab under
the Settings menu command in SIMOTION SCOUT. A corresponding error report is automatically
created in STARTER.
Note
The DCC editor is installed automatically with the SIMOTION SCOUT/STARTER engineering
system.
• DCC-Setup V2.0.2 - V2.0.5 can be installed with all SIMOTION SCOUT/STARTER V4.1 service
packs and hotfixes.
• DCC-Setup V2.1 can be installed with SIMOTION SCOUT/STARTER V4.2.
• DCC-Setup V2.2 can be installed with SIMOTION SCOUT/STARTER V4.3.
• DCC-Setup V2.3 can be installed with SIMOTION SCOUT/STARTER V4.4.
• DCC-Setup V2.4 can be installed with STARTER V4.5.
• DCC-Setup V3.1 can be installed with STARTER V5.1.
• DCC-Setup V3.3 can be installed with STARTER V5.3.
• DCC-Setup V3.4 can be installed with STARTER V5.4.
• DCC-S Setup V3.4.2.0 can be installed with STARTER V5.4.2.
An appropriate program license is required for the DCC editor. This is on the USB stick supplied
with the DCC SIMOTION or DCC SINAMICS product.
The installation requirements are also stated in the Readme file for the software version.
Note
It is possible to print DCCs in the DCC editor, but not in SIMOTION SCOUT/STARTER.
Note
Only context-sensitive help is available for the DCC blocks, i.e. the descriptions cannot be
accessed from the main help page.
Note
If the DCC charts are opened with a different CFC version than the one with which they were
created, this may lead to inconsistencies within the project. The DCC chart must be recompiled
and reloaded. DCC charts that have been edited with a newer CFC version can no longer be
opened with an earlier CFC version. Backward conversion is not possible.
If you open a project whose charts have been created with an older CFC version, you can select
whether the data format of the charts should be updated. If you reject this, you can in fact view
the CFC charts, but cannot edit them any further. It is recommended to adapt the data format
of the CFC charts to the currently installed CFC version.
SIMOTION
The DCC functionality and performance of the new SIMOTION target devices is compatible with
the previous versions, i.e. DCC V3.4 within the framework of SIMOTION SCOUT 5.4 supports the
following target device versions:
• SIMOTION V4.1 devices
• SIMOTION V4.2 devices
• SIMOTION V4.3 devices
• SIMOTION V4.4 devices
• SIMOTION V4.5 devices
• SIMOTION V5.3.1 devices
• SIMOTION V5.4 devices
The DCC functionality and performance of the new SOC2-based SIMOTION target devices (e.g.
D410-2 DP) is compatible with the corresponding IDC-based previous devices and versions (e.g.
D410 DP).
Note
Device versions
The device versions and software versions supported may be listed in the corresponding
Readme files.
Note
A compatibility list is provided on the SIMOTION SCOUT DVD and at the following link on the
Internet:
SIMOTION compatibility list (https://support.industry.siemens.com/cs/ww/en/view/18857317)
SINAMICS
DCC SINAMICS supports in STARTER/SCOUT V5.4 all previously released device versions with
DCC.
In addition, DCC is offered for:
• SINAMICS MV V5.2 SP1
• DCP V1.3
Note
With the installation of an SSP, the latest standard dcblib library available for the device is
installed and can be used on the device.
Procedure
Proceed as follows to create a project:
1. Start the SIMOTION SCOUT/STARTER engineering system.
2. Execute the Project > New function from the menu bar.
3. In the New Project window, enter the name of the project in the Name field.
Note
Convention for assigning names for projects
The project name may contain a maximum of 24 characters. The folder name is generated using
the first eight characters of the project name. It is therefore important to ensure that the first
eight characters of the project name are unambiguous.
SIMOTION
Proceed as follows to insert a device into a project:
1. Open an existing SIMOTION SCOUT project if a project is not already open.
2. Execute the Create new device command.
3. In the Create new device window, select the required device and close the window with OK.
Note
For further information on the Open HW Config switch, please refer to the documentation
for SIMOTION SCOUT.
All requirements for creating a DCC in the project have now been met.
SINAMICS
1. Open an existing project or create a new project in which you want to insert a SINAMICS drive
unit (e.g. SINAMICS S120 CU 320). Note that the SINAMICS S110 (CU 305 module) does not
support DCC.
Procedure
1. Select a device from the project.
2. SIMOTION:
Execute the Insert DCC chart function from the PROGRAM subitem of the device.
SINAMICS, STARTER:
Execute the Insert DCC chart function on the desired drive object. There may only be one
DCC chart on a drive object.
Figure 3-6 Inserting a DCC chart in the CU drive object of a SINAMICS CU3x0.x drive unit with
STARTER
Figure 3-7 SIMOTION D4xx: Inserting a DCC SINAMICS chart on the drive object of the CU with
SCOUT
Note
Convention for assigning names to charts
The chart name may contain a maximum of 22 characters.
6KHHW
6XEFKDUW
&KDUWSDUWLWLRQV
Figure 3-9 Connection between the types of chart in the DCC editor
Select the DCC chart in the project navigator and open the DCC Chart Properties dialog via the
Properties... context menu to access certain properties of the DCC chart. On the General tab
under Time stamp under Last changed on (STEP7): you can see the date on which the DCC
chart was changed the last time by STEP 7 (CFC editor) or changes accepted in DCC chart
properties. Under Last changed on: you can see the date on which the DCC chart was last
compiled or changes accepted in DCC chart properties. Under Project storage location: you
can see the path under which the project was stored.
Requirement
You have created a DCC chart in the SIMOTION SCOUT/STARTER engineering system which is
opened in the DCC editor.
Procedure
1. Use the View > Overview menu command or the button on the toolbar to switch from
the page view to the chart overview. The six pages of the selected DCC chart are shown.
2. Use the Insert new chart context-menu command to insert a new subchart, then open the
subchart by selecting Open from its context menu.
Note
DCC charts should always be created in STARTER/SCOUT.
If a DCC chart that is assigned to a SINAMICS drive object is open and additional DCC charts are
created directly in the CFC editor, this can result in compilation errors.
Requirement
You have already created a DCC in the SIMOTION SCOUT/STARTER engineering system which is
opened in the DCC editor.
Procedure
1. Insert a new chart partition in the desired position using the menu items Insert > Chart
partition > In front of current chart partition or At the end.
2. Alternatively, you can right-click an already existing chart partition on the tab and
select Insert chart partition in front of current chart partition or Insert chart partition at
the end.
You can switch to a page view with the block catalog displayed on the left using the View ->
Catalog menu.
3.5.1 Introduction
In this section, you will learn which block types are available and how you can insert blocks in
a DCC and delete them. You will also learn how to edit block connections.
Note
The online help provides detailed information (incl. timing diagram and plant view) for the
individual blocks. To start the help, select the required block in the chart or in the block catalog
and press the F1 key.
User responsibility
The user is responsible for verifying and validating the DCC functions which have been
programmed with DCC. The user is responsible for the proper operation of all DCC functions
which have been created with DCC.
WARNING
Danger to life or malfunctions of the machine as a result of incorrect programming of the
DCC functions
Incorrect programming of DCC functions can cause machines to malfunction, which can lead
to injuries or death.
• Respond to possible malfunctions by applying suitable measures (e.g. EMERGENCY STOP or
EMERGENCY OFF).
• Verify and validate the DCC functions you have programmed.
Inserting a block
• Open a block family in the Closed-loop control family with the closed-loop control blocks.
• Select the required block and insert it in the chart using drag-and-drop. Only the outline of
the block in dashed lines is displayed during the copying procedure. Release the mouse
button at the required point.
• To search for a block, enter its name in the input field of the block catalog and click
the binoculars button. The search process begins.
Note
If blocks are superimposed on the chart with other elements, such as other blocks or the
sheet bar, the superimposed block will be displayed in gray and its connections will not be
visible. You must reposition the blocks to ensure that all block information can be viewed.
Procedure
Select the New text command via the directories of the block types and insert it in the chart
using drag-and-drop. Release the mouse button at the required point.
Alternatively, you can right-click at the desired position in the chart and select the Insert new
text command in the context menu. Note that this option is only available offline.
You can adapt the size of the text field to your requirements by selecting the black points at the
corners and the sides and dragging them to the desired size.
You can change your comments by clicking the text field and then entering or editing your text.
Figure 3-14 Execution editor of the dccReg1 chart with the execution groups Tsg_dccReg1 and Tsg2
In this window, you can also change the insert point in the execution sequence by dragging the
block to the desired position. The assignment of a block to an execution group can be changed
in the same way.
New inserted blocks are always placed in the execution system behind the block that is defined
as predecessor. By default, this is always the block that has been inserted last. If a block is to be
inserted in the execution sequence behind an already existing block, select the block with the
desired offset in the overview, right-click and select the Predecessor for insert point function
in the menu. The block now defined as predecessor block is displayed in light green in the DCC
editor.
Figure 3-15 Block context menu: Defining predecessor for insert point
The active execution position is displayed in the status bar. This is at the bottom right in the
execution editor.
3.5.5.1 General
There are two types of block connection (inputs and outputs), each of which has a distinct
function and is edited in a particular way.
The following sections contain further information about handling the block connections in the
DCC.
Input values
At the block inputs, a value can be entered in the Value field of the properties dialog box. If the
input is not interconnected, it always has the specified value. With interconnected blocks, the
output value of the upstream block always applies in the initialization phase and in the first cycle.
Output values
At the block outputs, a value can be entered in the Value field of the properties dialog box. In the
first cycle however, the specified value is overwritten by the calculated value.
Note
Special feature with hidden block connections
In the DCC editor, you can hide block connections to improve the clarity of the configured charts.
However, the hidden block connections remain active in the DCC, so their values are still
evaluated. With generic blocks, you can also reduce the number of block connections in the DCC
editor. The hidden connections are assigned default values. However, the hidden block
connections remain active in the target system, so their values are still evaluated.
It should also be noted that the inputs of these blocks must be interconnected consecutively,
starting from the first connection.
Pseudo comments
Comments at block connections that start with @ are pseudo comments; they influence the
function of the block connection and serve as interfaces to the basic system.
For further information about the pseudo comments, see:
• Creating customer-specific parameters ("declare") (Page 153)
You can change the names of the block inputs/outputs via Options > Settings > Display in the
submenu Connections.
The block type can be displayed in the form of both text and graphics. This can be configured via
Options > Settings > Display in the submenu Block headers.
If you want to display more than the first eight characters of the comment, then select Options >
Settings > Block / sheet bar width. Then in the Blocks / Sheet Bars window, set the block width
to Wide. The first twelve characters of the comment are now displayed at the connection.
See also
@ variables (SIMOTION) (Page 205)
Requirement
The inputs and outputs of the blocks must possess compatible data types so that they can be
interconnected. An overview of which data types can be interconnected is shown below:
Procedure
Connect the output of the first block (source) with the input of the second block (sink). You can
create this connection either by using drag-and-drop or by latching them together (clicking the
relevant input connection and output connection once).
The connection line is automatically drawn from the output of the first block to the input of the
second block.
3.5.7 Data type abbreviation in the DCC for connection and transformer blocks
Procedure
1. Model your DCC in the DCC editor.
2. Select the Chart Connections window via View -> Chart connections or with the button.
The chart connections (IN, OUT, IN_OUT) are shown in this window.
Note
Please note that chart connections of type IN_OUT are not permitted in DCC!
The block connection is interconnected to the chart connection. The assignment is displayed in
the variables sheet bar of the DCC editor. The block interface is defined as part of assigning block
connections to the interface.
Note
DCC SINAMICS: The use of chart I/Os is permitted for subcharts and DCC libraries.
Procedure
You can make an interconnection to a global operand as follows:
1. Open the DCC.
2. Right-click the block connection to be interconnected and select Interconnection to
operand in the context menu.
3. Now select the global operand to be interconnected in the DCC Signal Selection window.
4. Click OK to close the window.
The block connection is interconnected to the selected global operand.
Note
The blocks STM, RDP, SAV and WRP cannot be deleted or inserted online.
If you delete a block on which the inputs or outputs are interconnected to chart connections, the
connections are deleted, but not the chart connections. If these are not required, you must
delete them separately in the Chart connections field.
Call the Rearrange Parameter Numbers dialog box via the Chart -> Rearrange parameter
numbers menu to move parameter numbers.
Enter the new values and accept these with the Execute button.
The following warning is output for an invalid entry.
In the DCC editor, you can publish the connections of all blocks or the connections of one block.
For further information on the publishing of connections, refer to Creating customer-specific
parameters ("declare") (Page 153).
You can also perform this via the block context menu.
In the DCC editor, you can revoke the publication of the connections of all blocks and the
publication of the connections of one block.
3.6 Compiling
General
Some of the conditions that have to be met if a valid configuration is to be created from DCCs can
only be checked once charts have been created.
This procedure is carried out automatically at certain points, e.g. when a project or charts are
compiled.
Error log
You can also display the result of the consistency check via Options > Logs in the Consistency
check tab.
Note
If charts are deleted from previously compiled and downloaded projects, this can lead to
inconsistencies during the next compilation/download, as the overall chart execution system
has to be adjusted.
Note
Cross-chart consistency checks are performed only after the compilation of the charts.
The consistency check from the DCC chart always applies to the last compilation result.
Compiling
Please note that before the first compilation of a chart in a project, the project must first be saved
in STARTER/SIMOTION SCOUT (via the menu command Project -> Save or with the button).
You can begin compiling with Chart > Compile > Charts as program ... or with the button.
Compilation options
You can select the scope of the compilation:
• Scope: Only compile changes
Only those parts of the configuration that have been changed since the last compilation are
recompiled. When recompiling, this option reduces compilation time.
Note
All the configuration charts will be checked for consistency, even if you select the Only
compile changes option.
Additionally, you can select whether a map listing is to be generated and whether it should be
canceled in the event of an error occurring in a chart. A map listing is a list of the global objects,
the cross reference and the blocks used in the chart.
The map listing is saved in subfolder U7\debug in the project path.
Note
You can only compile DCC charts in the DCC editor. To carry out the creation process in full,
please use Save and compile all in STARTER/SCOUT.
As of STARTER/SCOUT V 4.2, this function is available under Save and recompile all.
As of STARTER/SCOUT V 4.3, this function is available under Save and recompile all including
DCC libraries.
As of STARTER/SCOUT V 4.4, this function is available under Save and recompile all.
Procedure
1. Open a chart from the relevant configuration and select Options > Block types in the menu.
2. The Import window is displayed. Click OK to close the window. In the window Import DCB
Libraries, the block libraries installed on your programming device are listed under Libraries
installed in SCOUT/STARTER. Under Libraries imported in the chart, all libraries which
have already been imported into this configuration are listed.
3. Check which previously imported libraries have a new version installed, by inspecting the
version of the library under Libraries installed in SCOUT/STARTER and Libraries imported
in the chart.
4. Select the library to be updated under Libraries installed in SCOUT/STARTER and click >>.
5. Click Accept.
6. The progress of the update is displayed in a window.
Response
The changes made compared with the old version are transferred to your existing configuration.
Note
The copying of charts or block groups between SINAMICS devices and SIMOTION devices and
vice versa is not supported.
You require a DCC license to copy a DCC chart as a block type into the SINAMICS library.
Note
Cross-chart interconnections
If you want to copy charts that contain cross-chart interconnections, this can lead to errors. Use
the XML import/export instead.
The chart has been copied from the source drive unit to the target drive unit.
Note
After copying, you must check whether the interconnections of block connections in the chart
copy have to be adapted to another drive object as a result of the copying. During copying, the
published block connections are automatically adapted to the basic system.
Cross-chart interconnections are lost.
DCC SIMOTION: When copying DCC charts, cross-chart interconnections are converted into
textual interconnections. They are closed again via Tools menu -> Close textual
interconnections .
Note
DCC SINAMICS and DCC SIMOTION
Only one SINAMICS DCC chart per drive object may be created.
Note
DCC SINAMICS and DCC SIMOTION
When copying a device, the associated charts are also copied.
An XML export or XML import of individual charts is possible. After the XML import, you must
check whether the interconnections of block connections in the XML import have to be adapted
to another drive object due to the XML import.
During a project export, the associated DCC charts are exported along with all interconnections.
Note
When copying DCC charts between different devices, the libraries used in the DCC charts are
exchanged with the libraries present on the device. In the case of SINAMICS devices, this
assumes that a version of the standard library is available for each device. As of SINAMICS 4.4,
multiple versions of the standard library are available on a device for compatibility reasons. If the
automatic selection option is used, the version with the highest firmware version is used. If
multiple library versions are installed for a firmware version, the library with the next-highest
version is selected.
For SIMOTION, dcblibV2_0_simotion4_1_x is also available on SIMOTION V4.2 devices.
V4.1 libraries are only available on device types that were also available in V4.1. V4.1 libraries
cannot be executed on a D455-2 or D455-2. New block types can be found
in dcblibV3_0_simotion4_2.
Note
Please note that you can only copy and paste DCC charts via the engineering system; you cannot
cut them.
If you want to copy a SINAMICS DCC chart to another project, then the chart must not use
SINAMICS libraries that are only available in the source project. This applies to the libraries in the
SINAMICS LIBRARIES subitem. In this case, an error message is displayed when the copy action
is attempted, and the DCC chart is not copied.
You can use the functionality of the XML export and the XML import in order to always copy DCC
charts correctly between projects.
Block numbering
When copying blocks or block groups in the DCC editor, the name of the new block is formed as
follows: if numeric characters are present at the end of the name, these are all deleted up to the
first non-numeric character and replaced by the next free numeric character. It is therefore
recommendable to allocate names consisting of letters (and numeric characters) such as block,
block1, block2, etc.
You can change the execution sequence at any time via the Edit > Execution sequence
command in the menu bar or the button.
See also Specifying execution properties (Page 39).
Note
Symbols that are defined from the DCC, so-called @ parameters, DCC parameters (SINAMICS),
links to BICO parameters are not considered when searching/replacing.
General conditions
• As of DCC 2.0.2, the symbols (variable in sheet bar) used in the DCC chart and the contents
of alias definitions can also be searched for and replaced.
• The CFC editor must be closed during the search/replace operation.
• If the CFC chart sources have been deleted or the charts have know-how protection,
searching/replacing of the sheet bar elements is not possible.
• It is not possible to undo these changes.
Note
Symbols that are defined from the DCC, so-called @ parameters, DCC parameters (SINAMICS),
links to BICO parameters are not considered when searching/replacing.
Boundary conditions
• As of DCC 2.0.2, the symbols (variable in sheet bar) used in the DCC chart and the contents
of alias definitions can also be searched for and replaced.
• The CFC editor must be closed during the search/replace operation.
• If the CFC chart sources have been deleted or the charts have know-how protection,
searching/replacing of the sheet bar elements is not possible.
• It is not possible to undo these changes.
Test settings
You can specify the Monitoring cycle via the menu Test > Test settings. This displays the Test
Settings window.
In this window, you can set the monitoring cycle for the objects that have been logged on for
testing, i.e. the cycle time for updating these objects. The monitoring cycles can be set in 1 to
100 steps each of 100 milliseconds (SIMOTION). Only whole seconds can be set as monitoring
time for SINAMICS.
Note
If you have logged on many objects for the test, it is better to use a slower updating cycle.
Saving settings
The logging on of blocks for monitoring is rejected when the online test is exited. The settings
of the block interfaces with regard to the test are saved in the project.
Note
If the monitoring function has been deactivated and you highlight a connection in order to log
it on for testing via , monitoring is activated for this connection and for all previously logged-
on connections of this block.
By activating test mode, connections are also established with the CPU for all connections listed
within a value display window. Activate monitoring by selecting the individual connections in
the Monitoring column.
deactivated for this block, it will also be activated for all connections that were logged on for
testing prior to this.
In edit mode or test mode (process or laboratory mode), you can log off individual block or chart
connections for testing:
• Select Test > Log off connections or click the button in the toolbar.
Note
Alternatively, it is also possible to log on/log off all connections of a block for testing in edit
mode by highlighting a block, selecting Object properties via the context menu, and
selecting or deselecting the individual connections in the For testing column of
the Connections tab.
displayed in the status bar with a green background. Any menu functions that are not permitted
in test mode are displayed as deactivated (grayed out).
Note
If the DCCs are different in the editor and in the target device, then they can behave differently,
see Consistency of charts in test mode (Page 73).
Note
Once the project has been uploaded from the target device, it needs to be saved before DCC test
mode can be started.
If you have made changes to connections or block types in the DCC, you will be informed that
you can still monitor and trace values when test mode starts.
Online changes can only be performed after the DCC has been recompiled and downloaded to
the target system. You are informed about this fact when starting test mode and can return to
editing mode or activate test mode for monitoring purposes - as shown in the following dialog
box.
Note
The dynamic display is limited to 256 values.
It includes the structure of a block connection with more than 256 single elements. As such, you
can only insert individual elements selectively into the dynamic display and not the block
connector in its entirety.
Drag individual elements to the dynamic display by means of drag-and-drop to display currently
relevant values.
Please note that monitoring values in the dynamic display influences the performance of the
target device
Figure 3-32 Inserting a block pin into the value or trend display
The desired trace parameters can be set in the Trace Parameters window, which can be
accessed via the Change button.
Inserting comments (text) Select the New text command via the directories of the block types and
in the chart insert it in the chart using drag-and-drop. Release the mouse button at the
required point.
Changing comments (text) You can move the text field in the DCC by selecting it and then dragging it
in the chart to the desired position. You can change your comments by double-clicking
the text field and then entering or editing your text.
Note
Please note that online changes can only be made in test mode.
In test mode, the "Server busy" message may be intermittently displayed if you attempt to
change values online.
You may need to acknowledge this message several times before the value that is being changed
online is accepted.
Repair the project using an XML export/import.
Note
In SIMOTION SCOUT, deactivate the option Options → Settings → Save → Automatic back-up
copy of the project data when working with large projects to prevent a drop in performance.
Otherwise, the entire project would be saved in test mode each time a change was made.
Requirement
Only signal values at block inputs that are not interconnected can be changed online.
Procedure
The Properties - Connection window is opened by double-clicking the desired block
connection. A new numerical value can now be entered for the block input in the Value line. The
new value takes effect and is displayed in the chart when Accept is clicked. The window is closed
by clicking OK.
Note
DCC-SINAMICS 2.5: Only signal values of block inputs can be changed online that have not been
published as BICO parameters.
As of SINAMICS 2.6., all non-interconnected and unpublished block inputs can be changed in
test mode.
Note
DCC SIMOTION: The signal value at the block input can be changed online, but with active
execution group is overwritten in the next cycle. Whether the signal value at the block input can
be changed online does not depend on whether it has been declared as an HMI variable or not.
Procedure
In the DCC, select the block connection that you want to disconnect. Then remove this with Edit
> Delete or with the Del key.
Result
The connecting line between the connections disappears and the last value that was transferred
on the connection appears as input value at the connection.
Note
DCC SIMOTION: Interconnections to chart connections cannot be deleted online!
Procedure
In the DCC chart, select the block connection from which you want to establish an
interconnection and drag an interconnection to the block connection to which the
interconnection is to be established.
Result
The connecting line between the selected connections is established and the current value that
has just been transferred appears at the output.
Note
Up to and including DCC-SINAMICS 2.5, a block input published as a BICO parameter may only
be interconnected with outputs published as BICO parameters or with BICO outputs of the basic
system.
Block connections cannot be published in test mode, i.e. new @ parameters inserted.
Note
DCC SIMOTION: Connections to published block inputs in the DCC or global operands cannot be
recreated online.
Procedure
Select the required interconnection and move it with drag&drop.
Note
When moving BICO interconnections, the signal can acquire the value 0 for a few cycles.
The no longer interconnected input on the original connection is permanently assigned the
value 0.
Procedure
Call the block catalog using the View > Catalog command. Open the block family and use drag-
and-drop to move the selected block to the working area.
The block instance is calculated with the next cycle.
The inserted block instance is assigned a standard name that can subsequently be changed
online: Select the block, right-click and select Rename. Recompilation and loading is only
required if the trend display, trace or monitoring of block connections has been activated.
Note
Whether a block can be added or deleted online is described under "Configuration data" in the
online help for blocks.
Note
Renaming blocks
When blocks are renamed in online mode, a new block is created that replaces the existing block.
This is then recalculated. The initialization values are newly set for the block.
Online renaming allows meaningful names to be assigned also for the online inserting of
module instances.
Procedure
First delete all output interconnections by selecting the connection and then selecting Edit >
Delete in the editor menu or with the Del key. Then select the block and remove it with the Del
key or the Edit > Delete command.
Note
In SINAMICS, blocks for which at least one connection has been published as a parameter cannot
be deleted.
Note
DCC SIMOTION: Blocks with interconnections to chart connections cannot be deleted online.
Note
The blocks STM, RDP, SAV and WRP cannot be deleted or inserted online.
Procedure
Select the New text command via the directories of the block types and insert it in the chart
using drag-and-drop. Release the mouse button at the required point.
Procedure
You can change your comments by clicking the text field and then entering or editing your text.
You can adapt the size of the text field to your requirements by selecting the black points at the
corners and the sides and dragging them to the desired size.
Procedure
Select the block and drag it to a suitable free position in the chart.
If the DCC charts differ online and offline and the DCC charts have already been compiled, a
prompt appears that the DCC charts are different online and offline.
• If only the constant values of the charts are different, you can restore the consistency using
the menu command Options > Read back constant values.
• If the DCC charts differ online and offline and have already been compiled, a prompt appears
that the DCC charts are different online and offline. Download the changes to the target
system so that monitoring and changes can be performed in test mode.
The download is performed when the target device is in the STOP state. With SINAMICS, the
download only functions in the "Power-on inhibit" and "Ready for power on" operating
modes.
Note
Double-clicking one of the displayed block types opens the associated chart and the selected
block type is highlighted.
Note
The names selected in the execution system (i.e. the names of the execution groups and
execution levels) for each device must be unique.
Compatibility
Please refer to the following table for information on which kernel version supports which DCB
libraries.
SINAMICS libraries
The following standard libraries are executable with SINAMICS V4.8:
• SINAMICS V4.8 (dcblibV3_0_sinamics4_8)
• SINAMICS V4.7 (dcblibV3_0_sinamics4_7)
• SINAMICS V4.6 (dcblibV3_0_sinamics4_6)
• SINAMICS V4.5 (dcblibV3_0_sinamics4_5)
• SINAMICS V4.4 (dcblibV3_0_sinamics4_4)
• SINAMICS V4.3 (dcblibV2_0_sinamics4_3)
The following standard libraries are executable with SINAMICS V4.7:
• SINAMICS V4.7 (dcblibV3_0_sinamics4_7)
• SINAMICS V4.6 (dcblibV3_0_sinamics4_6)
• SINAMICS V4.5 (dcblibV3_0_sinamics4_5)
• SINAMICS V4.4 (dcblibV3_0_sinamics4_4)
• SINAMICS V4.3 (dcblibV2_0_sinamics4_3)
It is possible that libraries and block types with the same names are present in the separate
directories for the SIMOTION and SINAMICS libraries. Block type names must be unique within
a library.
Note
Use the STM block in DCC library blocks that are only instantiated once per DO.
Note
You can no longer use a SINAMICS 2.6 library as of SINAMICS Version 4.x.
If the DCC library required in the chart is not available for selection, this means that a basic library
used within the library is not valid for the current device. You can change the basic library in the
DCC editor under Options > Block types. If a chart source is not available, you can call up the
Block types menu command from the context menu in the DCC library.
Name ambiguity in blocks from different libraries
If two blocks from different libraries (in the case of SIMOTION) have the same name, then the
block from the library whose name comes first in the alphabet will apply.
If a DCC chart has not been inserted for a chart container (Device/Library), it is not possible to
import a library.
Note
For SINAMICS, the libraries must always be imported under the device and not under the drive
object.
Deleting the last chart of a device clears the selection of the DCB libraries.
When importing a DCC library, it must be compiled.
Note
The library concerned must be selected for this purpose.
Note
The standard library is automatically installed during setup, but if you do uninstall it accidentally,
you can reinstall it by means of the DCC setup process.
The libraries for SINAMICS can also be installed via the SSPs (SINAMICS Support Packages).
If you wish to reinstall the DCB library from the SSP DVD, switch to directory CD_1\SSP\Disk1 and
unzip file dcblib.zip into any directory. Install the library dclbib_Vx.y_sinamics_w.z contained in
unzipped files.
As of DCC V2.1 (STARTER 4.2), the libraries for SINAMICS are also available via the menu
command Options -> Install libraries. See also Installing and uninstalling DCB libraries
(SINAMICS).
The libraries for SIMOTION are also available via the menu command Extras -> Install libraries.
See also Installing and uninstalling DCB libraries (SIMOTION) (Page 102). Here you will also find
information on where installable DCBLIB standard libraries are located and how to reinstall
these.
• Check which previously imported libraries have a new version installed, by inspecting the
version of the library under Libraries installed in SCOUT/STARTER and Libraries imported
in the chart.
• Select the library to be updated under Libraries installed in SCOUT/STARTER and click >>.
• Click Accept.
• The progress of the update is displayed in a window.
Note
In SINAMICS, you can check a selected device in the engineering system using the Select
technology packages function in the context menu as to whether all required block libraries
and technology packages have been activated.
Note
In SIMOTION, the library is automatically loaded to the device during the project download.
In SINAMICS, this action must be performed explicitly by the user before the project
download. (Page 179)
The library to be imported is checked to see whether it contains a block type that has already
been imported with another library.
Error log
If errors are detected when a library is being imported, an error log with details of the causes of
the errors is displayed.
Up to DCC V2.0.1, the version of the basic library used is permanently defined in a DCC library.
Exactly the same basic library version that was used to create the DCC library must be installed.
If the library sources have been deleted, it is not possible to select a new version of the basic
library in the typical library.
With DCC 2.0.2, you can combine an installable library that has been supplied with different
versions of a DCB library that is being used, provided the interface for the blocks called does not
change.
• The Import DCB Libraries window appears. The block libraries installed on your
programming device are listed under Libraries installed in SCOUT/STARTER.
Under Libraries imported in the chart all libraries which have already been imported into
this configuration are listed.
• Select the desired language in the selection list of available languages. The selected
language affects all imported libraries.
• Click Accept.
• The progress of the update is displayed in a window.
Note
Comments regarding the block types remain in the language in which they were created. The
comments regarding block pins are translated if they have not already been altered manually.
You can delete block libraries whose block types are no longer required in the configuration
concerned via the menu Options > Block types.
How to delete block libraries:
• Ensure that the block types from the block library to be deleted are no longer to be used at
all in the charts of the configuration.
• Open a chart from the relevant configuration and click Options > Block types.
• The Import window appears. Click OK to close the window.
• The Import DCB libraries window appears. The block libraries installed on your
programming device are listed under Libraries installed in SCOUT/STARTER.
Under Libraries imported in the chart, all libraries which have already been imported into
this configuration are listed.
• Select the library to be deleted under Libraries imported in the chart and click <<. The
deletion process is triggered when you click Accept.
Checks are performed when a block library is deleted. All unused block types of the library will
be removed from the selection list of the block types in the DCC editor; used block types remain
in the list. The chart cannot be compiled without an imported library if instances of the library
are still present in the chart.
3.11.1 Fundamentals
The DCC editor offers a function for saving a chart as a block library (DCB library = typical). This
kind of chart relates to a connection created by the user, which features an interface so that it
can be reused and is saved in a library. The charts as block library (DCB library) function therefore
include the option of know-how protection, since the configured DCCs are only available as a
transparent block within a block library. The DCC configuration that has been created is hidden.
The DCC chart created for a block can be permanently deleted via the function Delete source of
the block types... in the context menu of the library. This command is only available if all blocks
in the library have been compiled without errors. If it is executed, all the corresponding chart
sources are deleted leaving only what has been compiled in the project. You cannot undo the
action. By right-clicking on the DCC chart and selecting the Block types command, however, you
can open a dialog in which the block libraries used can be exchanged.
6,027,216&287
,P
SR
UW
2
SW
LR
QV
,PSRUW2SWLRQV!%ORFNW\SHV
!
%
OR
NF
W\
SH
V
'HYLFH
O
WDO
,QV
,PSRUWHG
'&%OLEUDU\
,QVWDOODEOH
'&%OLEUDU\ &UHDWHLQVWDOODEOHOLEUDU\ '&&OLEUDU\
Requirements
You have already created a new DCC library in the SIMOTION SCOUT engineering system.
SIMOTION DCC libraries are located in the folder Libraries of the project navigator, DCC libraries
in the SINAMICS Libraries folder of the project navigator.
Note
You can display the chart connections via the button in the toolbar.
You can use a library either in DCC charts for SINAMICS or for SIMOTION.
Create DCC libraries for SIMOTION in SCOUT in the Libraries container.
As of DCC 2.1 / SCOUT / STARTER V4.2, DCC libraries can also be created for SINAMICS.
For this purpose, the project navigator contains a new program container for SINAMICS libraries
under Libraries -> SINAMICS LIBRARIES.
Figure 3-42 Library container for DCC libraries for SINAMICS devices in SIMOTION SCOUT
The DCC libraries for SINAMICS and SIMOTION are distinguished from one another on the basis
of the different library containers in the project navigator.
Insert a DCC library for SIMOTION by selecting Libraries -> Insert DCC library from the context
menu in the project navigator.
Insert a DCC library for SINAMICS by selecting SINAMICS libraries -> Insert DCC library from the
context menu in the project navigator.
With DCC 2.0, you can insert SIMOTION DCC charts into the library container using copy and
paste.
The chart connections of the inserted DCC chart must be connected to the chart connections of
the SINAMICS DCC library without BICO interconnections and @ parameters before the
compilation.
The DCC libraries, but not the DCB block libraries, are found in the library containers.
By selecting Generate DCB library... from the context menu for the selected DCC library, you
can create installable DCB libraries from DCC libraries (typical libraries).
It is possible that libraries and block types with the same names are present in the separate
directories for the SIMOTION and SINAMICS libraries.
Note
Know-how protection
Protect the DCC blocks, sources and libraries by means of the know-how protection function
provided by STARTER/SCOUT.
Note
You need a DCC SIMOTION license to create and edit SIMOTION DCC libraries.
You need a DCC SINAMICS license to create and edit SINAMICS DCC libraries.
Procedure
Model your DCC in the DCC editor.
Insert an ADDer and a PI controller (PIC), for example, in the chart and interconnect them. See
Interconnection to chart connections (Page 44)
Following successful configuration, the DCC can be compiled as a program. To do this, select
Chart > Compile > Chart as program in the menu.
The newly created DCB library is available in the menu under Options > Block types in the DCC
editor. The DCB library is not shown in SIMOTION SCOUT/STARTER; only native libraries are listed
there.
See also
Creating an installable DCB library from DCC libraries (Page 97)
Within a library, a DCC chart can be created for each DCC block in the library. A new block type
is created using the Insert DCC chart context menu.
SIMOTION and SINAMICS libraries are both subject to the same rules for assigning DCC chart
names:
• Max. 22 characters, beginning with a letter
• If an underscore is used, only numbers may be used after it.
Figure 3-44 Connection example for a 1:N interconnection without NOP block
If there is a 1:N interconnection at an input within a hierarchical chart or block type, an NOP_x
block must be used in the chart for consistency reasons - refer to the following example:
Figure 3-45 Connection example for a 1:N interconnection with NOP block
3.11.4 Creating comments and icons for DCC libraries you have created yourself, and
assigning a block family to them
In the engineering system, you can save additional information on individual blocks of a DCB
library that you have created yourself.
Procedure
Select the block library you want to edit in the engineering system.
In the context menu of the DCC library, select the Block type properties command.
In the list under Chart, select the DCC chart you wish to edit and click the Additional block type
properties button to open the Block Type Properties dialog.
Block icon
Click the ... button and load a BMP file you wish to use as a block icon for the DCC chart.
Block family
Enter the family to which you want to assign the DCB library. You can either choose an existing
block family (e.g. Logic, System, Conversion, Arithmetic, etc.) or enter a new one, which will
then be created automatically. The default language for block families is English.
Block comment
Here you have the option of entering a comment for your DCB library; this will appear in the block
header. On the left-hand side, enter the comment in English (the default language). On the
right-hand side, you have the option of entering the comment in additional languages. To do
this, select the required language from the combo box above and to the right of the field, enter
the comment, and click Accept. Repeat this process for all other languages in which you wish to
create the comment.
Accept what you have entered using the Accept button and click OK to close the dialog.
In the dialog box, specify the online help directory for the library.
The name of the DCB library results from the name of the selected DCC library. You can freely
select the storage location of the DCB library and then start the creation via the Create DCB
library button. Information on the creation of the DCB library can be found in the detail view.
You have the option of deleting DCC chart sources for improved know-how protection.
Select the context menu Delete source of all block types in a compiled DCC library to delete the
sources of the DCC charts. The charts can then no longer be edited.
By selecting the context menu Block type -> Properties at the library, you can allocate
comments to block types and block connections in multiple languages.
An installable library may be installed on a different SCOUT/STARTER, regardless of the STEP7
project being used. This library does not contain the CFC chart sources.
Once you have installed the library using Options -> Install libraries, it is available for importing
into DCC charts on the devices (Options -> Block types).
Note
If you create an installable library from a DCC library, you must replace the DCC library with the
installable library in the DCC chart via the menu Options -> Block types of the CFC editor.
Note
The sources of the DCCs are no longer contained in the created DCB library. The contained
functions can no longer be changed or monitored (know-how protection).
Information on how to create an online help for the DCB library created can be found in the
section titled Creating the online help for block libraries (Page 98).
Note
It is possible to create C block libraries from exported DCC libraries automatically. This results in
improvements to the memory utilization in the execution performance of the DCC charts as well
as increased know-how protection.
See also
Exchanging the basic library version for installed libraries (Page 84)
Note
From SCOUT/STARTER 4.4 the block help editor is no longer part of the setup. A help can now be
created as part of SIMOTION CLIB Studio or SINAMICS DCB Studio.
You can create a separate online help for the created libraries with the aid of a supplied editor,
the DCB help editor. You edit your help files in the same view in which they are later displayed.
The DCB help editor can be found at ...\Siemens\Step7\S7BIN\helpeditor\DCB-Help-Editor.exe.
A <block>_doc.xml file can be stored for each block in the help_x folder. For example, save your
German language <block>_doc.xml file under help > help_a.
Procedure
1. Open the DCB help editor with a double-click on helpeditor DCB-Help-Editor.exe.
2. The STARTFILE_DOC.XML file, which is filled with elements and dummies, opens
automatically.
3. Replace these dummies with your own descriptions by selecting the dummies and entering
or copying your text in the file.
4. The Elements pane on the right-hand side contains additional elements for the description
(e.g. Truth table, Block diagram, Example, etc.), which you can drag to the desired position
on your file using drag-and-drop and edit there.
5. Insert your own graphics by dragging the Graphic element to a suitable position in the file
using drag-and-drop. In the following dialog box, enter the path under which the graphic is
stored (use the Browse button).
6. Save the edited file with the button or via the File > Save as... menu in the storage
structure described above.
You can create a new block description via File > New.
Note
Detailed operating instructions for the DCB help editor can be found in the menu under Help
> Help contents.
Note
The libraries are installed independently of the projects in SIMOTION SCOUT/STARTER. The
libraries are not transported when projects are archived or exported. If the project is to be loaded
on a different SCOUT/STARTER, the libraries used there must be reinstalled. This is also the case
after SCOUT/STARTER has been reinstalled.
The DCC standard libraries DCBLIB (supplied from the factory) are preinstalled. If you explicitly
require this as an installable library, you can find this library, e.g.
"dcblibV2_0_simotion4_1_5.zip" (version-dependent name) after the installation of SCOUT in
the"C:\Program Files\Siemens\Step7\U7umc\data\dcc\SIMOTION" directory or, if available, on
the DCC DVD under "VOL1\CD_1\DCC\DCC_DCBLIB_SIMOTION\Disk1". You can also, for example,
store the standard DCC libraries using the card reader in the USER directory on the CompactFlash
card for later service assignments (the version of the standard DCC library may not be available
in the engineering tool). This means that if service is required, you can use the CompactFlash
card reader and the functions described here to reinstall the relevant libraries.
Note
For SINAMICS libraries as compared with SIMOTION libraries, there is the restriction that DCBLIB
standard libraries can only be installed and uninstalled while no project is open.
The libraries are installed independently of the projects in STARTER. The libraries are not
transported when projects are archived or exported. If the project is to be loaded on a different
STARTER, the DCC libraries used there must be reinstalled. This is also the case after STARTER has
been reinstalled.
The DCC standard libraries DCBLIB (supplied from the factory) are preinstalled. If you explicitly
require this as an installable library, you can find this library, e.g. "dcblibV2_0_sinamics2_6.zip"
(version-dependent name) after the installation of STARTER in the directory "C:\Program Files
\Siemens\Step7\U7umc\data\dcc\SINAMICS" or, if available, on the DCC DVD under
"VOL1\CD_1\DCC\DCC_DCBLIB_SINAMICS\Disk1". You can also, for example, store the standard
DCC libraries using the CompactFlash card reader in the USER directory on the CompactFlash
card for later service assignments (the version of the standard DCC library may not be available
in the engineering tool). This means that if service is required, you can use the CompactFlash
card reader and the functions described here to reinstall the relevant libraries.
See also
Updating the block library (Page 81)
As of SIMOTION SCOUT V4.3 you can exchange DCC libraries between the SINAMICS and
SIMOTION target devices. In this way you can use a DCC library available for DCC SIMOTION on
a SINAMICS target device or a DCC library available for DCC SINAMICS on a SIMOTION target
device.
Note
This function is not available for STARTER.
Proceed as follows to insert DCC library blocks in a DCC library of a different target device family:
In the project navigator, select the DCC chart to be copied on the DCC library at the library
container and select Copy in the context menu. Switch to the library container for DCC library
of the other target device family and insert the DCC chart via the context menu command Insert
as SINAMICS chart or Insert as SIMOTION chart.
When you insert the chart, the original library/chart name is taken over and an underscore and
a number appended to the name. If there is already an underscore and a number appended to
the name, the number is incremented.
The execution groups are changed automatically when saving under a different target device
family.
Note
If chart sources of the DCC libraries are not available, no DCC editor is installed or there is no
license for the DCC editor, you cannot insert DCC libraries into a different target device family.
The Save as context menu command is then not available.
If block types from the library are not available on the target device, an error is output during
compilation of the library. In this case, you must either delete or modify the block instances.
WARNING
Danger to life through manipulation of DCC charts and DCC libraries
The use of unprotected DCC charts and libraries entails a higher risk of manipulation of DCC
charts, DCC libraries and backup files.
• Protect important DCC charts and DCC libaries by using know-how protection programs or
via the know-how protection for drive units in the SCOUT/STARTER. You can prevent
manipulation by assigning a strong password.
• For know-how protection programs, use passwords which include at least eight
characters, upper and lower cases, numbers and special characters.
• Make sure that only authorized personnel can access the passwords.
You can delete the standard login in this dialog box. A password is not required for this.
Note
The dialog box is only available in SIMOTION SCOUT.
Note
Only the standard coding can be used for DCC sources and libraries.
Note
The various levels of the know-how protection only apply to the new programs to be protected.
You may have to delete, reconfigure and activate the know-how protection for already protected
programs.
See also
Know-how protection for drive unit (Page 108)
As of SINAMICS V4.5, know-how protection is available for drive units in STARTER / SIMOTION
SCOUT. You can only activate/deactivate the know-how protection in online mode. When the
know-how protection is set, p parameters can be neither read nor written. If certain parameters
are to be excluded from the know-how protection, enter them in the expert list under parameter
p7764 before you set the know-how protection.
If no know-how protection for the drive unit has been activated, but a password has already been
defined (temporarily deactivated know-how protection for the drive unit), you can reactivate
know-how protection for the drive unit with the previous password. You can, however, also
change the password.
Define password
To define the password, you need to enter and confirm the new password. If you make a mistake,
a message appears to inform you that the passwords entered do not match. If this happens, you
need to reenter the passwords. Passwords are subject to the following rules:
• Min. length: 1 character, max. length: 30 characters.
• All read and write characters are permitted, see Opening a project under every set Windows
language setting (language-neutral).
• It is the personal responsibility of the user to ensure adequate password security.
WARNING
Danger to life through manipulation of DCC charts and DCC libraries
The use of unprotected DCC charts and libraries entails a higher risk of manipulation of DCC
charts, DCC libraries and backup files.
• Protect important DCC charts and DCC libaries by using know-how protection programs or
via the know-how protection for drive units in the SCOUT/STARTER. You can prevent
manipulation by assigning a strong password.
• For the know-how protection of drive units, use passwords which include at least eight
characters, upper and lower cases, numbers and special characters.
• Make sure that only authorized personnel can access the passwords.
Note
If you want to process your projects on Windows systems with different language settings, then
you must define this in the project settings. Navigate via the menu Project -> Properties to
the Properties - Project dialog box and activate the Can be opened under every Windows
language setting (language-neutral) checkbox. Only use ASCII characters for the password of
the know-how protection for drive units.
Diagnostics functions
If, despite active know-how protection, you still require the trace, measuring function or the
function generator, select the Permit diagnostic functions option. You may have to activate the
required parameters first in the exception list.
Note
Diagnostic functions possible as of V4.7
Diagnostic functions that work despite active know-how protection are available as of V4.7.
Combining know-how protection for drive unit with write protection for drive units
You can combine the Know-how protection for drive unit with Write protection for drive
units. Note that you must first set the Know-how protection for drive unit and then the Write
protection for drive units.
If you have combined the Know-how protection for drive unit with the Write protection for
drive units, the parameters of the exception list can only be read. The Write protection for
drive unit does not apply for parameters with the WRITE_NO_LOCK attribute. These parameters
can be written at any time. With combined write and know-how protection, the drive unit
behaves similar to absolute know-how protection for drive unit, since a password can no longer
be entered due to the write protection.
Behavior for devices with know-how protection for the drive unit
• Know-how protection always applies to the device, not to individual DOs.
• The content of the project navigator remains unchanged.
• All r parameters can still be read.
• p parameters can be neither read nor written with the following exceptions:
– Parameters with the KHP_ACTIVE_READ or WRITE_NO_LOCK attribute
– Parameters from the exception list
• Instead of a complete expert list, only a reduced expert list is displayed. This contains all the
r parameters as well as the p parameters that have been enabled by attributes or the
exception list. The behavior also applies to functions of the expert list, user-defined lists of
values, and watch tables.
• An expert list comparison can be performed, the values of the know-how-protected
parameters are displayed as know-how protected.
• No wizards are available.
• It is not permissible to delete this device in its entirety or to delete individual components
from it.
• It is not permissible to rename the device.
• It is not possible to call dialogs containing functions that are not supported by know-how
protection for the drive unit. An error message is displayed.
• Where windows contain functions that are not supported by the know-how protection for
the drive unit, they do not show any active contents (with the exception of the expert list and
version overview); instead, they indicate that know-how protection for the drive unit is
activated.
• Scripts which need read or write access to protected parameters/functions, cannot grant
appropriate access and are rejected.
See also
Know-how protection for libraries and programs (Page 106)
Write protection for drive unit (Page 117)
3. When using the know-how protection function for the first time, you will be prompted to
enter the required access data (login and password) for protection of the chart in the Know-
How Manager window. Close the Know-How Manager window via the OK button.
Note
When DCC charts are protected, the execution sequence cannot be protected in the execution
system. Although the chart can be moved, it cannot be edited. Note that if the execution
sequence of a protected DCC chart is changed, the functionality can no longer be guaranteed or
may fail.
Note
The know-how protection is not automatically reactivated in SIMOTION SCOUT/STARTER
when you close the DCC chart.
As of SINAMICS V4.5, write protection for drive units is available. You can only activate/
deactivate this write protection in online mode.
Activate/deactivate the write protection via the context menu Write protection for drive unit of
the drive unit or via parameter p7761 of the expert list. A password is not required to activate/
deactivate the write protection. You can query the status of the write protection via
parameterr7760.0 in the expert list (value = 0 means that the write protection is not set).
When write protection is activated, the following functions can be used in offline mode:
• Inserting, editing, deleting DCC libraries
• Inserting, editing, deleting DCC charts
• Inserting, editing, deleting DCC blocks
Note
When write protection is activated for a SINAMICS target device, however, a download to the
target device is not possible. This prevents any changes made offline in DCC charts taking effect
in the target device.
Note
If you want to activate the write protection permanently, execute the Copy RAM to ROM
function.
See also
Know-how protection for drive unit (Page 108)
Know-how protection for libraries and programs (Page 106)
Note
The properties of runtime groups must not be changed during operation, as otherwise
inconsistent signal transitions may occur.
For more detailed information on the start-up behavior, please see Chapter Characteristics of
block connections (Page 40).
Note
This specification applies as long as the device version does not change. Following a
replacement with a new device version, the DCB library versions present on the new device must
be imported and the DCC chart recompiled. The corresponding DCC license (CFC for SIMOTION/
SINAMICS) is required for this.
Until DCC 2.1, the library version had to be updated manually after the upgrade of a device
version.
As of DCC 2.1 / SCOUT/STARTER V4.2, the library version is upgraded automatically.
During the project export, the CFC charts with the STEP7 data storage are exported in binary
format.
From DCC Version 2.1, DCC charts can be individually exported in XML format and imported
again during XML import.
This means that you can transfer a DCC chart to another project (from a project with SINAMICS
2.6 devices to a project with SINAMICS 4.x devices, for example).
The following restrictions apply to the XML export/import of DCC charts:
• DCC charts that have been exported from SIMOTION devices cannot be imported into
SINAMICS devices, and vice versa
• DCC blocks that have been exported from SIMOTION DCC libraries cannot be imported into
SINAMICS DCC libraries, and vice versa.
The table below outlines the compatibility of XML exports/imports in relation to the relevant
SCOUT/STARTER version.
Compatibility
Project Projects exported with SCOUT/STARTER V4.1 can be imported with
V4.2 without any loss of information. After opening the project, the
user is asked to convert the CFC charts to CFC 7.1.
Projects exported with SCOUT/STARTER V4.2 can be imported with
V4.1 without any loss of information. However, it is not possible to
edit DCC charts with CFC 7.0.
In the case of projects that were created with V4.2 and imported
using an older version of SCOUT/STARTER, a warning appears when
the import process is carried out.
Device Devices exported with SCOUT/STARTER V4.1 can be imported with
V4.2 without any loss of information. If block types that were not
available in V4.1 are used in a V4.2 project, the devices can be im‐
ported without any loss of information. Errors are reported when
compilation is carried out, however.
Devices exported with SCOUT/STARTER V4.2 can be imported with
V4.1. The DCC chart sources are lost when they are imported with
V4.1. No errors or warnings are output.
Drive object (DO) Drive objects exported with SCOUT/STARTER V4.1 can be imported
with V4.2. These do not contain any DCC charts.
Drive objects exported with V4.2 can be imported with V4.1. The DCC
chart sources are not imported.
If a DCC chart is exported on a DO type A and imported on a DO type
B, the adaptation process for the sheet bar interconnection is the
same as copying/pasting DCC charts. When pasting on the new DO,
the old execution group is also transferred. During compilation, the
execution group that applies to the new DO is entered automatically.
Compatibility
CFC version DCC charts that were created with an older CFC version can be im‐
ported with a newer CFC version. Downward compatibility is also
supported.
The export/import of projects and chart containers only supports
upward compatibility. A chart created using CFC 7.1 can no longer be
opened with CFC 7.0.
The assigned DCC charts are included in the XML export/import of the selected object.
Note
If a CFC editor is not installed, only the DCC charts (i.e. without chart sources) are exported/
imported. No error message is output.
No DCC license is required for exporting/importing DCC charts.
Click OK to start the export. You can track the progress of the export on the XML export/import
status display tab.
If the target directory already exists, you will see the following dialog:
Choose Yes to overwrite the data in the target directory or No to cancel the export.
Note
DCC charts that were exported from SCOUT/STARTER cannot be imported into the SIMATIC
Manager.
XML import
DCC charts and DCC libraries can be individually exported from SCOUT/STARTER and reimported
into a SCOUT/STARTER project. They have the same layout after the import as they did before the
export. No information is lost from the DCC chart, i.e. the subcharts, library information, sheet
bar interconnections, execution groups, alias definitions, p21000 settings, and know-how
protection are all retained during an XML export/import. Know-how protection can be revoked
after the import, making it possible to edit the charts again.
You also have the option of importing a previously exported DCC chart into an existing chart.
When importing DCC charts, a distinction is made between importing a DCC chart and importing
into an existing DCC chart:
• Container in project navigator -> Expert -> Import object
• DCC chart -> Export/import object
You can track the progress of the import on the XML export/import status display tab.
Note
It is possible to export/import DCC charts even if the chart in the current project has not been
compiled or cannot be compiled without errors.
If the DCC chart has not been compiled so that it is up to date before the export/import, then the
imported DCC chart will be empty or will not be up to date.
Even in this case, DCC charts can still be imported without any information being lost, provided
that the libraries used in the chart are not yet installed or were imported on the program
container. Reinstall the SIMOTION libraries by selecting Options -> Install libraries..., or by
selecting Select technology packages... from the context menu in the case of SINAMICS.
The XML export/import can be carried out for DCC charts with existing DCC chart sources or for
DCC charts without DCC chart sources. Please observe the following:
• During the import of DCC charts with DCC chart sources, the set values of the expert list are
overwritten with the set values and BICO parameters from the DCC project.
• During the import of DCC charts without DCC chart sources, the adjustable parameters and
BICO parameters (@ parameters) are not overwritten.
If the DCC chart sources are not available in a project because the DCC charts were obtained as
a result of an upload from the target device or copying without a DCC license, or the DCC chart
sources were explicitly deleted, the DCC chart is exported and imported without chart sources.
The DCC chart that is created in this way can be loaded and compiled. You can select Block types
from the context menu to exchange the version of the subordinate basic DCB libraries.
See also
Exchanging the basic library version for installed libraries (Page 84)
3.19 Reading back DCC chart sources from the target device
In DCC 2.0, DCC charts can be read back from the target device and loaded to another target
device of the same type. To enable the DCC charts to be edited further, the DCC chart sources
must be present in the original project.
As of DCC 2.1, DCC charts for which no up-to-date DCC chart sources or no DCC chart sources at
all are present can be uploaded from the target device and read back to the DCC editor.
Chart sources for DCC libraries (typicals) are downloaded/uploaded via the library context menu.
They are uploaded as part of the project uploading process.
Procedure
Under Options -> Settings in SCOUT, select the Download tab and activate the Include DCC
chart data checkbox below the Store additional data on the target device checkbox to load
the DCC chart sources to the target device.
Figure 3-66 Storing additional data and sources on the target device - SCOUT
In STARTER, under Options -> Settings, select the Download tab and activate the Store
additional data on the target device checkbox to download the DCC chart sources to the target
device.
Figure 3-67 Storing additional data and sources on the target device - STARTER
During the CPU download, you can also select whether the DCC chart sources are to be
downloaded to the target device for the CPU.
The default setting for the CPU-specific option is taken from Options -> Settings -> Download.
The option selected for the CPU is then saved as the default setting for the next download.
Once you change the option under Options -> Settings -> Download, this is regarded as the
default setting for all CPUs.
If you deactivate the Store additional data on the target device option, the chart sources in the
target device are deleted during the next download.
If you activate the Store additional data on the target device option, the chart sources of the
DCC libraries are downloaded to the target device, which are used in the DCC charts of the CU
or CPU.
If DCC charts are available on the target device, the project is saved following upload.
When downloading to the PG, you must explicitly select whether the library sources from the
target device will be loaded into the offline project. In this way, you can keep different library
versions in different devices.
Note
In the project comparison, DCC charts are displayed differently following read-back (incl. DCC
chart sources), as the DCC chart sources are recreated and therefore have a different time stamp.
Conditions
• If the DCC chart is not open, the chart source will be updated automatically when the project
is read back.
• If DCC charts are open in the editor during the project upload, the chart sources will not be
updated automatically in the editor. In editor mode, the chart that has been read back can be
updated from the CFC using function key F5.
• The chart must not be in test mode while it is being read back.
• If the chart sources are not present in SCOUT/STARTER, the DCC chart sources will be created
automatically after the project has been uploaded.
• During the project upload, DCC charts with the same name that are already present in the
engineering system will be overwritten.
• If the chart names are the same, DCC sources with know-how protection overwrite existing
chart sources during the upload to the engineering system.
• DCC libraries are restored when the DCC chart sources are read back.
• The layout of the charts after the read-back process is the same as when they were edited:
The positions of the block instances are restored and comments are available in the same
position as they were before.
• The libraries used in the charts must be installed in SIMOTION SCOUT/STARTER so that the
upload of DCC charts is performed without errors.
The process of reading back DCC charts is independent of the SIMOTION firmware version.
For SINAMICS, it is possible as of SINAMICS V4.4.
The additional data for the read-back process must have been loaded to the target device.
Additional data for DCC charts can be created and loaded as of DCC 2.1.
When charts with know-how protection are read back, the know-how protection for the DCC
charts is restored in the engineering system.
Changes that have been made online in DCC test mode are taken into account when DCC chart
sources are read back.
The following restriction applies if you do not have a DCC license / the CFC has not been installed:
• DCC charts can be uploaded and loaded back onto the target device, but they can no longer
be edited - even if the CFC is installed or a DCC license is made available after this.
Note
Up to STARTER/SCOUT V4.1.5, the process of reading back BICOs/parameters for DCC SINAMICS
had to be explicitly initiated from the editor after the project had been read back from the target
device.
With STARTER/SCOUT V4.2, however, the BICOs/parameters are automatically read back when
the project is read back into the DCC chart.
4.1.1 Introduction
This product brief is intended for first-time users who are not yet familiar with the DCC program
package. Using a short example, you will find out how to create a new DCC, interconnect DCBs
(drive control blocks; function blocks), compile the chart, download it to the target device and
test it.
Note
In most cases, there are a number of options for working with the DCC editor (e.g. using the
keyboard). In this example, one option is used. Apart from a few exceptions, no alternative
methods of operation are explored here.
Note
The documentation on SINAMICS refers to versions STARTER 4.4, DCC 2.3 and SINAMICS
Firmware 4.7.
When the product is supplied, the DCC technology option is not yet available on the drive unit.
The DCC technology option must be loaded onto the drive unit's CF card in a separate operation
using SIMOTION SCOUT or STARTER. Afterwards, the SINAMICS CU3x0, SINAMICS DC MASTER or
the SIMOTION D4xx must be switched off and then on again. Only then can the DCCs be
downloaded and run on the drive objects.
From SINAMICS 4.3, the dcblib for S120 is already present on the card. For single drive units,
POWER ON after the download of the dcblib is no longer necessary.
There is only ever one DCC on a drive object. DCC can be activated simultaneously on several
drive objects on a drive unit. DCC is not available on SINAMICS S110 drive units (CU305 module).
Application
A logic operation, which connects several states (e.g. access control, plant status) to a control
signal (e.g. ON command), is required for controlling the drive system in a wide variety of
applications.
As well as logic operations, a number of arithmetical operations / storing elements are
increasingly becoming a requirement in drive systems.
Note
This additional functionality increases the computing time load. This means that the maximum
possible configuration for a Control Unit is restricted.
Drive Control Chart (DCC) functionality is available for every drive object of the drive unit listed
in the following table.
Description
Exactly one DCC chart can be created per drive object (DO = drive object). This DCC chart can
contain up to ten execution groups.
Note
The Interconnection with execution group... command is only supported with DCC SIMOTION.
WARNING
Changing the assignment of an execution group
If the assignment of an execution group is changed in the Set Execution Groups window (or
in parameter p21000[] ), the affected execution group is initially logged off during time slice
management and then logged on once again with the new assignment. The execution group
is not calculated during the period between logging off and logging back on. The log-on and
log-off take place in a background process of the drive unit; the duration is therefore not
defined and is determined by the current CPU time load of the drive unit. (This affects the path
of the output signal in the case of time-dependent blocks, e.g. the DIF differentiator.) Prior to
the first calculation cycle after logging back on, internal status variables of the blocks are
partially reset. For both of these reasons, this can result in jumps in the output signal of blocks,
which for example can affect the torque/force setpoint and (in the case of operated axes) also
the torque/actual force value. Logic signals can also acquire an unexpected state at this point
of operation.
If the change to the execution group also results in a change to the sampling time, internal
constants or factors are automatically adjusted for time-dependent blocks (BF, DCA, DIF, DT1,
INT, MFP, PCL, PDE, PDF, PIC, PST, PT1, RGE, RGJ, WBG). If you use these blocks in the following
execution groups, you must assign parameter p2048 the value of the isochronous master cycle
clock:
• Receive AFTER IF1 PROFIdrive PZD
• Send BEFORE IF1 PROFIdrive PZD
• Receive AFTER IF1 PROFIdrive flexible PZD
• Receive AFTER IF2 PZD
• Send BEFORE IF2 PZD
• Receive AFTER IF2 flexible PZD
Note that the execution groups created in the chart are only visible in the Set Execution Groups
window after the chart has been compiled.
Parameter r21002 displays the basic sampling time hardware.
Parameter r21003 displays the basic sampling time software.
For more detailed information on these parameters, see the online help for DCC parameters or
the "DCC blocks" Function Manual.
The execution groups created in the DCC editor must be assigned to the "Fixed execution groups"
and the "Free execution groups" of the SINAMICS drive object.
Note
For parameter p21000 (Properties execution group) and, therefore, in the context menu of the
"Set sampling times" chart, write access for the enabled controller is blocked in at least one drive
axis or infeed. The old value automatically takes effect again in this case. If necessary, switch off
all drive axes and infeeds, and make a new attempt.
The following fixed execution groups are available for SINAMICS as of FW Version 2.5:
• Read in AFTER digital inputs
This execution group is called after the current values of the digital inputs have been read in
on this drive object type and the corresponding binector outputs have been written.
The sampling time of this execution group corresponds to the sampling time of the CU inputs/
outputs (p0799) or the digital inputs/outputs of the TB30, TM31 and TM41 (p4099[0]).
• Output BEFORE digital outputs
This execution group is called before the digital outputs are output on this drive object type.
The sampling time of this execution group corresponds to the sampling time of the CU inputs/
outputs (p0799) or the inputs/outputs of the TB30, TM31 and TM41 (p4099[0]).
• Read in AFTER analog inputs
This execution group is called after the current values of the analog inputs have been read in
on this drive object type and the corresponding binector outputs have been written.
The sampling time of this execution group corresponds to the sampling time of the inputs/
outputs of the TB30, TM31 and TM41 (p4099[1]).
• Output BEFORE analog outputs
This execution group is called before writing is performed on the analog outputs.
The sampling time of this execution group corresponds to the sampling time of the inputs/
outputs of the TB30, TM31 and TM41 (p4099[1]).
• BEFORE speed controller
This execution group is called before the speed controller additional setpoint values "n_reg
n_set1" (p1155) and "n_reg n_set2" (p1160) are read into FP3080. The sampling time of the
speed controller (p0115[1]) produces the call, but a minimum sampling time of 1 ms is
required.
• BEFORE speed setpoint channel
This execution group is called before function block diagrams 3010, 3020, 3030, 3040 and
subsequent charts are calculated, if the setpoint channel has been activated (p0108.8 = 1).
If no setpoint channel has been configured (p0108.8 = 0), calculation takes place before
function block diagram 3095. The setpoint channel sampling time produces the call
(p0115[3]).
• BEFORE position controller
This execution group is called after the actual position value preparation (function block
diagram 4010) has been calculated and before the position controller (function block
diagrams 4015, 4020 and 4025) is calculated. The sampling time of this execution group
corresponds to the sampling time of the position controller (p0115[4]).
• BEFORE actual position value
This execution group is called before the actual position value preparation (function block
diagram 4010) and the position controller (function block diagrams 4015, 4020, and 4025)
are calculated. The sampling time of this execution group corresponds to the sampling time
of the position controller (p0115[4]). (Available as of V4.3).
• BEFORE basic positioner
This execution group is called before the basic positioner function module (function block
diagrams 3610 to 3650) is calculated. The sampling time of this execution group
corresponds to the sampling time of the basic positioner function module (p0115[5]).
70 7'; 70
0DVWHU 5 5 5 5 5
SRVLWLRQFRQWUROOHU
06* 5(6 *& '[ '[ '[ 06* 5(6 *& '[ '[ '[ 06* 5(6 *& '[ '[ '[ 06*
7=X
&XUUHQW
FRQWUROF\FOH
6ODYH
5 5
5
5 5 5
5 5 5
5 5 5
5 5 5
5 5 5
5 5 5
5 5 5
5 5 5
5 5 5
5 5 5
5 5 5
5 5 5
5 5 55
5 5 5
5 5
5 5 5
5 5 5
5 5 55
5 5 5
5
5
WR
7, 72 7, 72 7,
3URYLGHUHFHLYH 5HFHLYHUXQWLPH
GDWDVKRUWO\ JURXS$)7(5,)
EHIRUH72 352),GULYH3='
Figure 4-2 Calling the "Receive AFTER IF1 PROFIdrive PZD" or "Receive AFTER IF2 PROFIdrive PZD"
execution group for isochronous PROFIBUS communication. See also 3).
Receive data (sent by the master) is always processed and made available at the end of the
sampling time (no -1) TZu, so that the received process data remains valid until the start of the
next sampling period at the time To = no • TZu at r2050[..], r2060[..], r2090 - r2093. Thus, in
the last sampling time TZu before To. The "Receive AFTER IF1 PROFIdrive PZD" execution group
is then calculated in the following first sampling time TZu after To.
Note
Please take note that two connector-binector converters (function block diagram 2468:
p2099, r2094, r2095) are NOT called synchronously in isochronous mode but may be
processed within sampling time p2048 at any time depending on the computing time
utilization.
The calculation must be completed within the sampling time TZu; otherwise, warning
A01053 "System overload detected" or a time-slice overflow (F01205) will occur. For this
reason, only the absolute minimum number of DCBs that are necessary for the required
function should be calculated in this execution group.
The computing time available for this execution group decreases the more drive axes are
calculated on the CU since the current controllers (and also the speed controller for the servo)
of the drive axes are also calculated in the sampling time p0115[0] = TZu (>=125 µs).
If the utilization calculation is to be executed during ramp-up of the CU for isochronous
operation (unfavorable case regarding degree of utilization), p092 = 1 must be set.
Otherwise (p092 = 0) the utilization in r9976 will be updated only after switchover to
0DVWHU 70 7'; 70
5 5 5 5 5
SRVLWLRQFRQWUROOHU
06* 5(6 *& '[ '[ '[ 06* 5(6 *& '[ '[ '[ 06* 5(6 *& '[ '[ '[ 06*
&XUUHQW
FRQWUROF\FOH
6ODYH
5 5
5
5 5 5
5 5 5
5 5 5
5 5 5
5 5 5
5 5 5
5 5 5
5 5 5
5 5 5
5 5 5
5 5 57 5
5 5
5 5 55
5 5 5
5 5
5 5 5
5 5 5
5 5 55
5 5 5
5
5
WR
7, 7, 72 7,
6HQGFDOFXODWLRQRIUXQWLPH 3URYLGHWUDQVPLWGDWDDQG
JURXS%()25(,)352),G VHQGWKHVHGDWDWRPDVWHU
ULYH3='
Figure 4-3 Calling the "Send BEFORE IF1 PROFIdrive PZD" or "Send BEFORE IF2 PROFIdrive PZD" execution group for
isochronous PROFIBUS communication. See also 3).
The "Send BEFORE IF1 PROFIdrive PZD" execution group is calculated in the last sampling time
TZu before the data is sent to the master and before Ti and reading in the connector inputs
p2051[..], p2061[..].
Note
Please note that five connector-binector converters (function block diagram 2472: p2080 ...,
r2089) are also NOT called synchronously in isochronous operation but may be processed
within sampling time p2048 at any time depending on the computing time utilization.
The calculation of the execution group must be completed within sampling time TZu];
otherwise, a fault F1054 "System limit exceeded" (V4.3), a warning A01053 "System
overload measured" (V2.x) or a time-slice overflow (F01205) occurs. For this reason, only the
absolute minimum number of DCBs that are necessary for the required function should be
calculated in this execution group.
The computing time available for this execution group decreases as the number of drive axes
calculated on the CU increases, since the current controller (and the speed controllers for the
servo) of the drive axes are also calculated in sampling time p0115[0] = TZu.
If the utilization calculation during the ramp-up of the CU has already executed the
isochronous operation (the more unfavorable configuration regarding the utilization of the
CU), then p092 must be set to = 1. Otherwise (p092 = 0) the utilization in r9976 will be
updated only after switchover to isochronous operation. The increased maximum overall
utilization in isochronous operation will be displayed only in r9976.
Note
In the case of this execution group, please note that the higher computing time utilization
that applies in isochronous operation is not actually taken into account in the utilization
calculation until the time of the transition (specified by the PROFIBUS master) to isochronous
operation. After the drive device has ramped up, this means the utilization of the complete
system initially still lies within the valid range and it is only when the transition is made to
isochronous operation that the drive device shuts down with fault F1054 "System limits
exceeded".
Note
In the case of this execution group, please note that the higher computing time utilization
that applies in isochronous operation is not actually taken into account in the utilization
calculation until the time of the transition (specified by the PROFIBUS master) to isochronous
operation. After the drive device has ramped up, this means the utilization of the complete
system initially still lies within the valid range and it is only when the transition is made to
isochronous operation that the drive device shuts down with fault F1054 "System limits
exceeded".
This execution group is called after cyclic process data (PZD) has been received via
communication interface IF2 (e.g. via the integrated PROFIBUS interface) and output to
connector outputs r8850[..], r8860[..], binector outputs r8890 - r8893 and connector
binector converters r8894 and r8895.
The sampling time of this execution group corresponds to the PROFIdrive PZD sampling time.
The only difference from the Receive AFTER IF2 PROFIdrive PZD execution group is the way
in which the execution group behaves in isochronous mode. Even in isochronous mode this
execution group is called using the PROFIdrive PZD sampling time configured in the master
as with any other sampling time. This means that initially all shorter sampling times are called
at time To depending on the validity of the receive data (current controller; speed controller
if applicable). This execution group is called first only when the TDP sampling time starts to be
processed. You basically do not know how often the shorter sampling times with higher
priority of the current and speed controller are calculated before this execution group starts
to be processed. In addition, processing of this execution group is interrupted due to shorter
sampling times. This execution group should only be used if IF2 is usually operated in
isochronous mode. The benefit of this execution group is that considerably more blocks can
be calculated than in the Receive AFTER IF1 PROFIdrive PZD execution group because the
calculation does not have to be completed after current controller sampling time p0115[0].
However (due to the higher priority and interruption caused by shorter sampling times),
there is no longer a fixed synchronism between To and the time the execution group is called.
1) IF1 is the abbreviation for communication interface 1. With SINAMICS V2.5 and SIMO‐
TION V4.1, this refers to the integrated PROFIBUS interface or - if a CBE20 has been
inserted in the option slot - the PROFINET interface. IF1 supports the PROFIdrive profile
and isochronous operation.
2) IF2 is the abbreviation for communication interface 2. IF2 of the CU320 and CU320-2 can
only be used by the CAN bus if a CBC10 module has been inserted in the option slot and
SINAMICS software as of V2.5 is used. The CBE20 or integrated PROFIBUS/PROFINET
interface can be assigned to the IF2 via parameters (p8839, p8815). (See SINAMICS S120
Function Manual FH1 → Applications → Parallel operation of communications interfa‐
ces.) As of SINAMICS V4.4, isochronous mode is also supported on IF2.
3) For TDP, Ti and To, the formulas and limit values listed in the Function Manual FH1→
Communication → Communication via PROFIBUS DP → Motion Control with PROFIBUS →
"Time settings and Meanings" table apply.
On the SERVO drive object type, select "BEFORE speed controller" as a fixed execution group.
The associated system function is the speed controller.
The sampling time of the speed controller is p0115[1] = 125 µs in the factory setting of p0112
= 3.
In contrast to the sampling time of the speed controller, the sampling time of the DCC execution
group is set automatically to 1 ms.
Also refer to the description of parameter p0112 in the SINAMICS S List Manual.
WARNING
In the case of an online change to the sampling time (execution group) the START method of
the block is called. Initializations in the START method can result in jumps in the signal path.
– On the drive objects of the CU, TB30, TM15 DIDO, TM 31 and TM41, the sampling time for
additional functions p0115[0] = 4 ms is preset. If you want to configure a DCC execution
group with a smaller sampling time on these drive objects, you should first set the
sampling time for the additional functions p0115[0] on this drive object to the value of
the smallest desired sampling time. To do this, p0009 = 3 must first be set. Only then is it
possible to change p0115[0]. For the new value for p0115[0] to take effect, p0009 = 0
must be reset.
• Free execution groups whose sampling times are created in the software:
The software sampling times are generated as an integer multiple of the basic value for
software sampling times (read out in parameter r21003).
The possible set values for the software sampling times (1 * r21003 - 96 * r21003) can be
taken from the parameter description for p21000 (see Function Manual, Description of the
standard DCC blocks, in the appendix in the Parameters section).
WARNING
The START method of the block is called for an online change to the sampling time
(execution group). Initializations in the START method can result in jumps in the signal path.
Note
1. The assignment of identical names for DCCs in different drive objects is not permitted.
2. The assignment of identical names for execution groups in different drive objects is not
permitted.
If the same fixed or free execution group of the drive object is assigned to several execution
groups in the DCC editor, the execution groups of the DCC editor will be calculated in the
sequence from top (calculated first) to bottom (calculated last) as shown in the "Set Execution
Groups (Sampling Times)" window.
Figure 4-5 Properties - Connection window of the connection S (= Set) of the block INT (= INTegrator)
In SINAMICS, input and output connections of blocks can be published as parameters. "Publish"
means that users create the parameters themselves (parameter numbers and parameter text).
This is the prerequisite in order to interconnect the block connections using BICO parameters to
the basic system in order to assign the values to the input connections using adjustable
parameters and to monitor the values of the output connections using parameters. The
parameter number 251 in the above figure and in the following figure is arbitrary.
3DUDPHWHUQXPEHU 3DUDPHWHUQDPH
#
6WDUW
7KHRSWLRQDODVWHULVNLGHQWLILHV%,&2SDUDPHWHUV %ODQN
:LWKRXWDQDVWHULVNDQDGMXVWDEOHSDUDPHWHULV
FUHDWHGIRUEORFNLQSXWVDQGDWUDFHDEOHPRQLWRULQJ
SDUDPHWHUIRUEORFNRXWSXWV
The parameter name, which follows the parameter number separated by a space, is displayed in
the STARTER expert list.
The data type of the published input/output is taken over by the block connection.
For the "publishing" of block inputs, a distinction must be made between adjustable parameters
(without asterisk) and BICO parameters (with asterisk).
For the "publishing" of block outputs, the following distinction must be made:
• Without asterisk: pure monitoring parameter that cannot be interconnected and that can be
recorded with the trace function.
• With asterisk: as for the case without asterisk, but additional interconnection possible.
Block inputs to be published may not be already interconnected in the default setting of the DCC
editor. If necessary, an existing interconnection must first be deleted. To do this, click the
interconnection in the chart to mark it and select Delete interconnection(s) in the context
menu. In this DCC editor setting, the comment shown for a block input interconnected with a
different block is always that of the connected block output.
If you want to remove this constraint, select Options > Settings > Display ... in the DCC editor
and deactivate the Interconnection comment checkbox under Parameters and close the
window with OK. Already interconnected block inputs can now be published without having to
delete the interconnection first.
A parameter number may only be used just once in a chart. The DCC editor does not check when
the parameter number is entered in the Properties window of the connection whether this
parameter number is already used in the chart. The multiple use of the parameter numbers will
be indicated as error only when the chart is compiled.
The parameter numbers of the charts are represented on the number range from p21500 to
p25999 of the expert list of the STARTER. With each DCC chart, it is possible to specify where the
parameter range of the chart is to begin. This can be performed in the Parameters tab in the
Properties window of the chart in STARTER, using the parameter number base.
Figure 4-7 Properties window of the dccReg1 chart for setting the parameter number base
ᆰ )URPWKH6,1$0,&6EDVLF 7RWKH6,1$0,&6EDVLF
V\VWHP V\VWHP
$''
&RQQHFWRURXWSXW &RQQHFWRULQSXW
%,&2SDUDPHWHU ; < %,&2SDUDPHWHU
#
#
%,&2DGMXVWDEOHSDUDPHWHU %,&2GLVSOD\SDUDPHWHU
ᆱ ᆲ
$'' $'' $'' $''
; < ; < ; < ; <
#
#
%,&2GLVSOD\SDUDPHWHU 'LVSOD\SDUDPHWHU
ᆳ ᆴ
$'' $'' $''
; < ; < ; <
%,&2 FRQQHFWDEOH
2XWSXWPXVWEHSXEOLVKHGDV%,&2SDUDPHWHUVLQFHLQSXWLVSXEOLVKHGDWWKHVLQN
Example 1: For an interconnection of the block connection with the SINAMICS basic system, the
connection must be published as BICO parameter.
Example 2: Each block output connection can be published as BICO parameter. The signal on this
output can be recorded with the trace.
Example 3: Each block output connection can be published as (not interconnectable with other
BICO parameters) display parameter. The signal on this output can be recorded with the trace.
The block input can be interconnected to every other non-published block input.
Example 4: The block input connection X of the ADD 1 block is published as adjustable
parameter.
Example 5: Because the block input connection X of the ADD 2 is published as BICO parameter,
the block output connection interconnected with it must also be published as BICO parameter.
It is, however, possible in the DCC editor to interconnect ADD 1 Y with ADD 2 X when only the
block input ADD 2 X is published. This results in an error message when the chart is compiled.
The signal value of a block input published as BICO parameter cannot be recorded with the trace.
Note
No help function can be created for @parameters.
Procedure
Interconnection can be performed as follows:
1. Creating customer-specific parameters ("Publishing", @ parameters); see Creating customer-
specific parameters (Page 153).
Note
In the DCC editor, block connections can initially be connected with the drive's BICO
parameters without the need to publish them as parameters. However, this will cause errors
when compiling the chart, since only block connections that have been published as @*
parameters can be connected to the drive's BICO parameters.
Note
BICO parameters defined in other DCC charts will not be displayed in the signal selection list.
DCC-local parameters can be directly interconnected in the CFC chart as an interconnection of
block connections. This interconnection is then converted to a BICO interconnection.
Connections to BICO parameters in DCC charts on other DOs can be established graphically in the
DCC editor using two charts open next to one another.
Note
With the BICO technology of the SINAMICS drive family you can interconnect BICO parameters
with different data types, e.g. a BICO parameter of the FLOAT32 data type with a BICO parameter
of the INT32 data type. In this case, the value range of the FLOAT32 data type exceeds the value
range of the INT32 data type.
The SINAMICS basic system automatically ensures that in such cases the source parameters do
not exceed the value ranges of the sinks.
You must explicitly ensure this restriction in the DCC chart for published BICO parameters, e.g.
through an LIM block.
The following statements govern the use of DCC-SINAMICS on the SINAMICS S120, S150, G130,
G150 and (on the SINAMICS_Integrated in) SIMOTION D4xx devices. Details about other devices
are contained in the associated device documentation.
4.1.4.1 Computing time load for the SINAMICS V2.5 and V2.6 software versions
The processing of blocks requires computing time. This means with the computing of DCC
execution groups, it is no longer possible to calculate the maximum quantity structure for drive
objects of a CU3x0, D4xx and CX32.
The resulting computing time load is dependent on the following:
• Number of calculated execution groups
• Sampling time of execution groups
• Number of calculated blocks
• Calculated block types
• For some blocks, it depends on the parameterization (e.g. the setting of enable connections)
Parameter r9976 (system load; can be found on the CU's drive object) is available in the system
as an online tool. The average value for the computing time load in r9976[1] should always be
below 85.0%. Likewise, the maximum value for the computing time load in r9976[5] should
always be below 85.0%. Exceeding the computing time load limit of 90% triggers warning
A51003. The warning is reset if the computing time load falls below 88%.
The computing time load should not fall below the limit of 85.0% so that the response time of
the STARTER/SCOUT engineering tool is not too greatly restricted.
If the computing time load increases to the point that it is no longer possible for all blocks and
system functions assigned to a sampling time to be completed within this sampling time, the
drive unit switches off and outputs fault F01205: "CU: Time-slice overflow".
Offline mode enables the SIZER engineering tool to make an approximate statement regarding
whether a configuration can be calculated on a CU3x0 or D4xx. The additional computing time
load is not taken into account by activating the DCCs.
Note
The computing time load reaches its maximum value when the following conditions are met:
• All necessary function modules are activated.
• All drives and infeeds are in the operational status.
• Closed-loop control in the final configuration is approved on all drives and infeeds.
• Configured isochronous data transfer is used.
The values displayed in r9976 are thoroughly smoothed internally. A change in the computing
time load is therefore only displayed in full in r9976 after 2 - 3 minutes.
If, during OFFLINE configuration, it is not certain whether the limit value for the computing time
load of 85% (r9976[1] and r9976[5]) will be adhered to, you can initially call the execution
groups being used in a very large sampling time (e.g. 96 * r21003). After checking the actual
system load in r9976, you can then gradually select execution groups with shorter sampling
times right through to the execution group that is intended for the application in question.
During OFFLINE configuration, the following should be carried out:
• Activate all necessary function modules on the drive objects.
• Assign all necessary blocks to their execution groups.
• Establish all connections, both between the blocks and to the drive objects (as long as this
still makes sense even if an increased sampling time is being used).
AND, OR, XOR, NOT, BF, CTR, MUX8, NAND, NCM, SH_DW, ADD, SUB, MUL, DIV, AVA, MAS, MIS,
PLI20, DEL, DEZ, SUB_D, SUB_I, MUL_D, MUL_I, DIV_D, DIV_I, AVA_D, SII, STM, DLB, DX8, DX8D,
MFP, PCL, PDE, PDF, PST, RSR, DFR, BSW, NSW, LIM, PT1, INT, DIF, LVM, LIM_D, PC, PIC, RGE
In a sampling time of 1 ms, only around half the blocks can be calculated. Around twice as many
can be calculated in a 4 ms sampling time.
A SERVO axis with standard sampling times omitted from the maximum configuration thus
permits the use of approximately 50 blocks (of the above-mentioned types) for a sampling
period of 2 ms.
Approximately 50 blocks (of the above-mentioned types) in an execution group increase the
computing time load of the CU by approximately 11%.
The proportional computing time utilization caused by DCC is displayed on the drive objects on
which DCCs are configured in the parameter r21005[0…9] for the execution groups 1 to 10 (as
of SINAMICS V4.3). Note that the average computing time utilization for an execution group k
can be calculated only when this is registered for cyclical processing (p21000[k-1] ≠ 0, in the
STARTER/SCOUT in the context menu of the chart → Set sampling times).
In contrast to software versions V2.5 and V2.6, a parameter change (in online mode of the
STARTER) that affects the computing time utilization (e.g. change of the sampling time of a DCC
execution group) causes an immediate recalculation of r9976 (and r21005) by the drive device.
For parameters that may only be changed in the device states C1 (commissioning 1) or C2 , i.e.
may only be changed in STARTER/SCOUT offline mode (e.g. p0115), the new value of the
computing time utilization in r9976 will be displayed only after the project download and the
subsequent CU ramp-up.
As of V4.3, the permitted maximum value of the computing time utilization r9976 increases
practically to 99.99%. (For values > 100.00%, fault F1054 will be set; this simultaneously causes
an OFF2 on all drive objects of the CU.)
As rough configuration aid, the following is true for SERVO drives with the current controller
sampling time p0115[0] = 125 µs and the speed controller sampling time p0115[1] = 125 µs:
1. If on a SINAMICS CU320-2 one A-INF infeed with the sampling times set in the factory (p0112
= 2 == LOW → p115[0] = 250 µs), six SERVO drive axes with the speed and current controller
sampling times set in the factory (p0112 = 3 == STANDARD → p0115[1] = p0115[0]
=125 μs), the function modules set in the factory setting, one TB30 2) and with isochronous
PROFIBUS/PROFINET communication with T_DP >= 2 ms are configured, one (1) DCC with
approximately 50 blocks can be calculated in an execution group with a sampling time of 2
ms.
2. If on a SINAMICS CU320-2 one A-INF infeed with the sampling times set in the factory (p0112
= 2 == LOW → p115[0] = 250 µs), 5 SERVO drive axes with the speed and current controller
sampling times set in the factory (p0112 = 3 == STANDARD → p0115[1] = p0115[0]
=125 μs), the function modules set in the factory setting, 1 TB30 2), 3 TM31 2) and
isochronous PROFIBUS/PROFINET communication with T_DP >= 2 ms are configured, one (1)
DCC chart with approximately 75 blocks can be calculated 1) in an execution group with a
sampling time of 2 ms.
3. For each additional omitted SERVO axis, approximately 75 additional blocks 1) can be
calculated in the sampling time of 2 ms.
As rough configuration aid, the following is true for VECTOR drives with the current controller
sampling time p0115[0] = 500 µs and the speed controller sampling time p0115[1] = 2000 µs
(p0115[3] = 2000 µs, p0115[4]=2000 µs):
For more than three VECTOR axes on a CU320-2, the current controller sampling time will be
increased automatically to the value p0115[0] = 500 µs. This automatically increases the speed
controller sampling time to 2 ms.
1. If, on a SINAMICS CU320-2, one A-INF infeed with the sampling times set in the factory
(p0112 = 2 == LOW → p115[0] = 250 µs), six VECTOR drive axes with the current controller
sampling times p0115[0] = 500 μs, the speed controller sampling time p0115[1] = 2000 µs,
the functions and function modules set with the factory setting, one TB30 2) and with
isochronous PROFIBUS/PROFINET communication with T_DP >= 2 ms are configured, one (1)
DCC with approximately 50 blocks can also be calculated in an execution group with the
sampling time 2 ms.
2. If, on a SINAMICS CU320-2, one A-INF infeed with the sampling times set in the factory
(p0112 = 2 == LOW → p115[0] = 250 µs), five VECTOR drive axes with the current controller
sampling times p0115[0] = 500 μs, the speed controller sampling time p0115[1] = 2000 µs,
the functions and function modules set with the factory setting, with isochronous PROFIBUS/
PROFINET communication with T_DP >= 2 ms, one TB30 2) and three TM31 2) are configured,
one (1) DCC with approximately 75 blocks can also be calculated in an execution group with
the sampling time 2 ms.
3. For each additional omitted VECTOR axis (with p0115[0] = 500 µs and p0115[1] = 2000 µs),
approximately 75 additional blocks 1) can be calculated in the sampling time of 2 ms.
As rough configuration aid, the following is true for VECTOR drives with the current controller
sampling time p0115[0] = 250 µs and the speed controller sampling time p0115[1] = 1000 µs
(p0115[3] = 1000 µs, p0115[4] = 1000 µs):
For up to three VECTOR axes on a CU320-2, the current controller sampling time and the speed
controller sampling time have the values p0115[0] = 250 µs and 1 ms, respectively, in the factory
setting.
1. If, on a SINAMICS CU320-2, one A-INF infeed with the sampling times set in the factory
(p0112 = 2 == LOW → p115[0] = 250 µs), three VECTOR drive axes with the current
controller sampling times p0115[0] = 250 μs, the speed controller sampling time p0115[1]
= 1000 µs, the functions and function modules set with the factory setting, one TB30 2) and
with isochronous PROFIBUS/PROFINET communication with T_DP >= 2 ms are configured, one
(1) DCC with approximately 50 blocks can also be calculated in an execution group with the
sampling time 2 ms.
2. If, on a SINAMICS CU320-2, one A-INF infeed with the sampling times set in the factory
(p0112 = 2 == LOW → p115[0] = 250 µs), two VECTOR drive axes with the current controller
sampling times p0115[0] = 250 μs, the speed controller sampling time p0115[1] = 1000 µs,
the functions and function modules set with the factory setting, with isochronous PROFIBUS/
PROFINET communication with T_DP >= 2 ms, one TB30 2) and three TM31 2) are configured,
one (1) DCC with approximately 150 blocks can also be calculated in an execution group with
the sampling time 2 ms.
3. For each additional omitted VECTOR axis (with p0115[0] = 250 µs and p0115[1] = 1000 µs),
approximately 150 additional blocks 1) can be calculated in the sampling time of 2 ms.
The chart with 75 blocks consists of an execution group with the following blocks in the listed
1)
sequence:
AND, OR, XOR, NOT, BF, CTR, MUX8, NAND, NCM, SH_DW, ADD, SUB, MUL, DIV, AVA, MAS, MIS,
PLI20, DEL, DEZ, SUB_D, SUB_I, MUL_D, MUL_I, DIV_D, DIV_I, AVA_D, SII, STM, DLB, DX8, DX8_D,
MFP, PCL, PDE, PDF, PST, RSR, DFR, BSW, NSW, LIM, PT1, INT, DIF, LVM, LIM_D, PC, PIC, RGE, AND,
OR, XOR, NOT, BF, CTR, MUX8, NAND, NCM, SH_DW, ADD, SUB, MUL, DIV,AVA, MAS, MIS, PLI20,
DEL, DEZ, SUB_D, SUB_I, MUL_D, MUL_I, DIV_D.
The chart with 150 blocks consists of an execution group that contains the previously listed 75
blocks twice.
2)
All sampling times (p4099[]) of the TB30 and the TM31 have the value 4 ms (factory setting).
Maximum quantity structures with a topology of 5 servo or 3 vector axes with 1 ALM and 1 TB30
Drive unit CU3202 SINAMICS Integrated
on SIMOTION D4x5
SINAMICS 2.6.1 Blocks1 350 -
@Parameters 1
350 -
SINAMICS 2.6.2 Blocks 1
500 200
@Parameters1 500 200
Note
The specified maximum numbers for blocks and @parameters always apply for the entire drive
unit and should be regarded as guide values. Only the factory-set function modules are active.
The individual blocks and @parameters may be arbitrarily distributed across several charts.
Conserving @parameters has little effect on the quantity structure of the blocks; the specified
maximum numbers for the blocks should therefore not be exceeded.
Savings in further drive axes can increase the maximum limits by 50 blocks and 50 @parameters
for each axis saved.
Maximum limits when just one axis is used (including 1 ALM + TB30)
Drive unit CU320 and CU3102 CU320 and CU3102 SINAMICS Inte‐ SINAMICS Integrated3
with 1 servo axis with 1 vector axis grated3 with one vector axis
with one servo ax‐
is
SINAMICS Blocks1 550 450 - -
2.6.1 @Parameters 1
550 450 - -
SINAMICS Blocks1
700 600 400 300
2.6.2 @Parameters1 700 600 400 300
When using DCC on the CX32 the same quantity structure applies as on the CU320.
Note
The final limits are determined by the total memory available on the drive unit and the
computing time load. If the above-mentioned recommended maximum limits are exceeded,
this can result in errors during upload or download (e.g. fault F1105 CU: insufficient memory)
and the drive can no longer be switched on. If it is not possible to perform a new download with
a suitably adjusted project, a power OFF/ON must be performed on the affected drive unit.
By activating additional function modules (e.g. basic positioner EPOS), additional memory is
allocated and the specified maximum limits are decreased.
1
) The charts for the above-specified quantity structures are formed from n x (chart1 + chart2):
Chart1 contains 50 blocks (of the following types: AND, OR, XOR, NOT, BF, CTR, MUX8, NAND,
NCM, SH_DW, ADD, SUB, MUL, DIV, AVA, MAS, MIS, PLI20, DEL, DEZ, SUB_D,SUB_I, MUL_D,
MUL_I, DIV_D, DIV_I, AVA_D, SII, STM, DLB, DX8, DX8D, MFP, PCL, PDE, PDF, PST, RSR, DFR, BSW,
NSW,LIM, PT1, INT, DIF, LVM, LIM_D, PC, PIC, RGE) with 50 @parameters and approx. 90
connections (from block connector to block connector).
Chart2 contains 50 blocks (of block types AND, OR, ADD, MUL, DIV, B_DW, B_W, BY_W, D_I, D_R,
D_UI, D_US, DW_B, DW_R, DW_W, I_D, I_R, I_UD, I_US, N2_R,N4_R, R_D, R_DW, R_I, R_N2, R_N4,
R_UD, R_UI, R_US, UD_I, UD_R, UI_R, US_D, US_I, US_R, W_B, W_BY, W_DW, WBG,DCA, INCO,
OCA, TTCU, ADD, ADD_D, ADD_I, ADD_M, AVA, AVA_D, RSS), 50 @parameters and approx. 90
connections (from block connector to block connector)
For example, 350 blocks and 350 @parameters are compiled from 4 * chart1
+ 3 * chart2.
Only sampling times can be set as hardware sampling times, for which the following applies:
1 ms <= T_sampling <= r21003 - r21002 in p21000[x]
During configuration, note that the number of different hardware sampling times (1 ms = cycle
duration T_sampling <r21003 - r21002) used by the basic SINAMICS system, active function
modules (see r108) and Drive Control Chart is restricted as follows:
• CU310, CU320, D4xx --> no. of hardware sampling times = 13
• CU320-2 DP with SINAMICS V4.3 and higher --> no. of hardware sampling times = 25
• CU310-2 DP, CU310-2 PN, and CU320-2 PN with SINAMICS V4.4 and higher --> no. of
hardware sampling times = 25
• SINAMICS_Integrated on the D4x5-2 with SINAMICS V4.4 (contained in SIMOTION V4.2) and
higher --> no. of hardware sampling times = 25
• CUD (SINAMICS DC MASTER) --> number of hardware sampling times = 11
DCC and FBLOCKS together must not use more than 5 different hardware sampling times on one
drive unit. (This only refers to sampling times that deviate from the hardware sampling times
already present in the basic system.)
Note
Note that a long-term trace registers a sampling time of 2 ms and the trace registers sampling
times in accordance with the selected trace cycle clock. If these sampling times have not already
been registered by the basic SINAMICS system, "Free blocks" (FBLOCKS), or Drive Control Chart
(DCC), these functions require additional free hardware sampling times.
The registered hardware sampling times can be read (if the DCC is activated) in r21008[0...12].
The current number of free hardware sampling times is displayed in r7903 (as of
SINAMICS V2.6).
Preliminary remarks
The following is a brief explanation of what you will be configuring in this chart.
Configuration example
The requirement for this example is that there must be a STARTER or SCOUT version (≥ V4.1.2)
suitable for your SINAMICS SW version (≥ V2.6) installed on your computer. The SINAMICS
Support Package (SSP) V2.6 must also be installed. Your computer must also have a CFC license
to use the DCC editor. You can install this license from the USB stick provided with the help of the
Step7 Automation License Manager. A CU310 or CU320 is required with which STARTER/SCOUT
can connect online, e.g. via PROFIBUS.
The configuration example deals with a straightforward oscillating circuit that creates sinusoidal
oscillation at its output.
It will only take you a few minutes to create the chart; then you can execute it in test mode as
a demonstration.
The following blocks are used:
• Two integrators (INT)
• One inverter (SII)
As indicated by the differential equation f"(x) = - f(x), the oscillating circuit is comprised of two
integrator blocks that are linked by negation.
The frequency of the oscillating circuit is determined by the integrating time constant at the
integrators.
The oscillation amplitude is specified by the initial value at the integrator output.
• The Insert DCC window opens and you can enter a new name (of no more than 22
characters) for the chart (in our example dccReg1) and a comment. Please note that all
characters after an underscore in the chart name can only be digits.
• Click OK to close the window. The DCC is opened when the Open editor automatically
checkbox is activated
Alternatively, you can open the chart at any time by double-clicking on the chart symbol in
the project navigator.
• When first creating a chart in a project, you will be prompted to import a block library.
• In the window Import DCB Libraries, select the block library in the left column Libraries
installed in STARTER. Take the selected library into the right column by clicking the >>
button.
• Close the window with the Accept command. The block library is loaded and the DCC editor
opened with the chart.
The project structure has now been set up, a chart created and the block library loaded. All that
remains is to create some activity within the chart, i.e. by inserting blocks and interconnecting
them. Just one chart can be created for each drive object.
Figure 4-12 DCC editor with opened Closed-Loop Control DCB family
• Select the required block (e.g. INT) and insert it in the chart using drag-and-drop. Only the
outline of the block in dashed lines is displayed during the copying procedure. Release the
mouse button at the required point.
Note
If one block superimposes another block in the chart, the superimposed block will be
displayed in gray and its connections will not be visible. You must reposition the blocks to
ensure that all connections and block information are displayed.
Procedure
• Select the Y output of the first INTegrator, followed by the X input of the second INTegrator.
• Select the Y output of the second INTegrator, followed by the X input of the inverter (SII).
• Select the Y output of the inverter (SII), followed by the X input of the first INTegrator.
The autorouter creates the connecting lines from the outputs to the inputs and they are then
interconnected.
Figure 4-14 Chart "dccReg1" with interconnected blocks. Some connections have been assigned initial
values that differ from the factory setting.
Note
To make this assignment of the @ parameters to the connections in the chart visible, the display
form of the connections in the DCC editor must be changed. To do this, open the Display
Settings window in Options > Settings > Display, change there under Connections the display
from Name to Comment and click OK to close the window.
Figure 4-16 View from the expert list with the parameters defined in the DCC
Compiling
Before the first compilation from the DCC editor, the project must be saved once in STARTER (
button).
You can begin compiling from the DCC editor with Chart > Compile > Charts as program... or
via the button.
You can also start the compiling and saving of a project from the STARTER by clicking the
button.
If errors occur during compilation, the Logs dialog box will automatically be displayed at the end
of the procedure (just as in the case of the consistency check).
Compilation options
For detailed information about the compilation options, refer to Compiling (Page 52).
After compilation
The compilation log is displayed after compilation. If error messages are displayed, the causes
must be corrected before continuing.
Note
Once the DCC chart has been compiled, the interconnections from the DCC chart apply. For
detailed information on accepting the interconnections from the expert list into the DCC chart,
please refer to the section titled Reading back BICO interconnections and parameters (Page 185).
You can return to the DCC by selecting Edit > Execution sequence again or by clicking again.
Our chart was created on the CU drive object. There r21002 = 4 ms. A free execution group with
a sampling time of 1*r21002 is set.
Note
In the offline mode of the STARTER / SCOUT V4.1.x, r21002 and r21003 are always displayed with
the value 0. The value of r21002 is identical with the p0115[0] value on the associated drive
object.
When setting the sampling time, note that the minimum sampling time in the drive for DCC
execution groups is 1 ms. Only times that are shorter than r21003 may be chosen as a multiple
of r21002.
Please re-compile the chart once you have set the sampling time.
Note
The properties of runtime groups must not be changed during operation, as otherwise
inconsistent signal transitions may occur.
4.2.11 Loading the DCC technology option onto the CF card of the drive device
As of SINAMICS 4.3.1, the DCC technology package is located on the S120/S150 CompactFlash
Card supplied from the factory for stand-alone drive units. With all other SINAMICS and
SIMOTION D4xx CompactFlash Cards, the DCC technology package must be downloaded to the
card by means of a technology package download
To load the technology package, call up SCOUT/STARTER and establish an online connection with
the drive unit. SCOUT/STARTER is in online mode.
Then in the drive unit's context menu, select the Select technology packages... command.
In the Select Technology Packages window, select the desired block library and set Download
for this library in the action column. Then click the Perform actions button in the bottom-right
window above the progress bar. The label on the button changes to Cancel.
A progress bar shows how the downloading process is progressing. Once the downloading
process is complete, the label on the button changes back to Perform actions.
The window is closed by double-clicking OK.
Note
Once the technology package has been downloaded, the drive unit has to be switched off and
on again once. Only once the supply voltage to the CU and/or D4xx has been switched back on
and it has been ramped up can DCCs be downloaded to the drive unit and run.
As of SINAMICS 4.4 and with the CU310-2 and CU320-2 modules, it is not necessary to switch
off and restart the drive unit once the technology package has been downloaded. Once the
technology package has been downloaded, an internal ramp-up process is performed
automatically. DCC is loaded as part of this process.
When technology packages are deleted from the CompactFlash Card, all the DCC components
of all the projects saved on it are deleted at the same time. As of SINAMICS V4.4 and with the
CU310-2 and CU320-2 modules, an internal ramp-up process is then performed by the CU. This
removes DCC from the CU memory.
Note
When downloading the technology package, as few people as possible should be connected to
the bus, as the download time is significantly increased when multiple users are connected.
To make the oscillator vibrate, it must be excited once. To do this, set the p21501 parameter in
the expert list of the STARTER once to "1" (the set value SV = 2.0 is applied at the output of the
left-hand integrator) and then reset to "0". The oscillator vibrates and the output values of the
integrators show changing values in the chart and in the expert list (r21520).
If you want to make further changes to the chart, you can exit the test mode with Test > Test
mode or by clicking the button. It can take several seconds before the test mode of the DCC
editor is exited.
If you want to display the values of further block connections in test mode, right-click the desired
block connection and select Log on connection in the context menu.
If you want to display the signal value of a BICO output of the SINAMICS basic system, the signal
value supplied to the DCC via the sheet bar cannot be displayed directly. In this case, an NOP_xx-
block with the correct data type is inserted. The signal value of the output of the NOP_xx- can
then be displayed online.
4.2.14 Interconnection to the BICO parameters of the basic system in DCC SINAMICS
Procedure
You can make an interconnection to the BICO parameters of the basic system as follows:
1. Open the DCC chart.
2. Select the DCB connection to be interconnected.
3. Publish the selected connection as a BICO parameter (the comment for the connection must
start with "@*", see Creating customer-specific parameters ("publishing") (Page 153))
4. Right-click and select Interconnection with operand... from the context menu. The DCC
Signal Selection window appears.
5. Select the parameter to be interconnected. Only those parameters are offered that are
compatible according to the BICO interconnection rules. Further information on BICO
interconnections can be found in the online help of STARTER/SCOUT under the BICO
interconnections index entry.
6. Click OK to close the window.
The block connection is interconnected to the selected BICO parameter.
Note
The interconnected block connections must be published as BICO parameters for connections to
signal outputs or signal inputs of the basic system.
The connection can first be made in the DCC editor without publishing the block connections.
However, connecting an unpublished block connection to a BICO parameter of the basic system
results in an error when compiling the chart.
Note
Interconnections with published block connections, which are established via the expert list, are
not read back to the DCC editor. For this reason, subsequent compilation of the DCC chart will
result in interconnections created previously in the expert list being overwritten again.
You can prevent interconnections from being overwritten by selecting Chart -> Read back
BICOs and parameters in the open DCC chart in offline mode and then compiling the DCC chart.
Note
If symbolic assignment is enabled in the project, the Standard/automatic setting must be
changed to User-defined in the Telegram configuration dialog box for the drive objects in
which DCC is used.
The automatic telegram setting and automatic telegram extension must be deactivated.
Note
Implicit calling of the function "Read back BICO interconnections and parameters"
If drive objects are deleted, the function "Read back BICO interconnections and parameters" will
be automatically called.
Procedure
BICO interconnections and parameter values changed subsequently can be read back from the
target system via the DCC editor menu command Chart -> Read back BICOs and parameters.
As of DCC Version 2.1, you can find this under Options -> Read back BICOs and parameters.
Input and output BICO interconnections are read back. The read back process always applies to
all DCC charts of a device.
Requirements
• The structure of the block instances and interconnections must be the same both online and
offline.
• The sources of the DCC chart must be available.
Note
It is not possible to read back BICO interconnections in the case of DCC charts that have been
uploaded from a target device to an empty project.
4.2.16 Record with the trace signals from the DCC chart
The integrator output published as interconnectable parameter acts like any other connector
output of the SINAMICS basic unit. This means this signal can also be recorded with the trace.
The signal characteristic at block connections (that are not published as parameters) can still be
recorded with the trace. The trace is called in STARTER with Target system > Trace or . In this
example, the outputs of the two integrators in the DCC are recorded with a cycle clock of 1 ms.
The output of the first (left-hand) integrator is to be recorded as first signal in the trace. The
signal selection is opened with for this. Select the drive object on which the DCC is located
(only CU_S_126). Open the directory tree and the dccReg1 chart is displayed. Open the directory
tree of dccReg1 and the three blocks in the DCC are displayed. The desired connection is on block
1 (top left digit in the block symbol) of the dccReg1 chart. The designation of the connections
in the signal selection of the trace is made up of the _ChartName_BlockNumber_, i.e.
_dccReg1_1 in this case. The desired connection can now be selected in the list of block
connections. The window is then closed by clicking OK. See the following figure.
Figure 4-23 Trace signal selection for the block connections of the _dccreg1_1 block in the dccReg1 chart
The output of the second (right-hand) integrator is to be set as second signal. This block output
is published as BICO parameter r21520. The recording can be started with the button.
Note
When inserting block instances and connections online, the trace of the signal must be
restarted.
• Interconnections
• Execution groups
• @ parameters and external references
The detailed comparison enables possible inconsistencies between the DCC charts to be
precisely identified when going online or when activating the test mode.
The detailed comparison offers the following options:
• If the comparison attributes (source code, blocks, interconnections, execution groups,
@parameters) are not consistent, a comparison result is provided with detailed information.
• Tabular list of the comparison result
• If the DCC charts are inconsistent, you can jump to the appropriate position in the DCC chart
in order to avoid unnecessary searching in the DCC chart.
• As with the project comparison, the detailed comparison of DCC charts can be performed
with the same comparison partners. This means that the detailed comparison can be
performed between DCC charts and the project. The DCC charts and the project can be in the
offline-offline or offline-online states respectively.
• The DCC libraries are also contained implicitly as "DCC chart" comparison object.
Further information on the DCC detailed comparison can be found in the Project Comparison
Manual or in the STARTER/SCOUT online help (Project comparison index).
Complete documentation
The example has been successfully configured and tested. You can now create the complete
documentation for your example.
Printing a chart
You should also print the chart to document the interconnection of the blocks. Because only one
page was used on this chart, it suffices to print the current page. To begin printing, click:
If your chart consists of several pages, we recommend that you print them individually in the
page view. Click the button to change to the page view.
Click or to customize the display so that all blocks are shown on a single page on the PC
monitor.
The change of the hardware r21002 basic sampling time displays the value for p0115[0] in the
CU ramp-up of 1 ms. Here p0115[0] was changed from 4000 µs (factory setting) in offline mode
to 1000 µs and then downloaded to the CU.
When using DCC charts, the project must always be updated in the Engineering System and
downloaded to the target device.
4.3.1 Overview
Only DCB connections of a DCC chart declared as BICO parameters can be connected to the
connector inputs (CI) and connector outputs (CO) of the drive.
All block connections of data type REAL that are published as BICO parameters are per-unit
variables. This means that calculations are performed with per-unit signal values within DCC.
(1.0 corresponds to 100%). The conversion to the connector units of the drive is performed
automatically.
With all other data types, no conversion to a per-unit variable takes place.
The current output value (= per-unit speed setpoint = 1500 rpm / 3000 rpm = 0.5) is then
displayed.
The block was automatically assigned to an execution group when inserted into the chart. The
free execution group 20 * r21003 (selected at random) has been assigned to the execution
group in the Set execution group menu.
Note
The LIM type block supplies the absolute torque of 0.204625 Nm calculated in the chart at its Y
output. This absolute value is now divided by the reference variable for torque r2703 = 0.8185
Nm and the referenced torque value for interconnecting with the drive is thereby calculated. The
referenced torque value is available at the block DIV's output and is published as BICO parameter
r21530 (value = 0.2499 = 0.204625/0.8185). Block NOP1 has only been inserted so that the
value of reference torque r2703 can be shown in the chart at its r21527 output published as a
BICO parameter.
Monitoring parameter r1515 (total extra torque, function block diagram 6060) is only calculated
if the speed controller is enabled and the drive is magnetized (r0056.4 = 1 = yes). (A machine
must be connected to the motor modules and be running for this purpose.) Otherwise the value
is set to zero.
4.3.4 Interconnecting DCC signals with communication interfaces IF1 and IF2
Note
Connections to integer inputs can be made both online and offline in the DCC editor; a
corresponding error message is only issued when the chart is downloaded.
*) The chart name and block name must jointly consist of a maximum of 24 characters, including
separating characters.
Representation Meaning
Blue on white Representation of the values in edit mode (offline)
Black asterisks on yellow Values during transfer to the dynamic display
Black value on yellow Representation of the values read from the drive
object in test mode
#### on a red background Representation of values while the dynamized val‐
ues required from the drive object are missing
(fault, overload)
5.1.1 Introduction
This product brief is intended for experienced SIMOTION users who are not yet familiar with the
DCC program package. Using a short example, you will find out how to create a project after
starting up SIMOTION SCOUT, create a DCC chart, interconnect blocks, compile the chart,
download it to the target device and test it online.
Note
In most cases, there are a number of options for working with the DCC editor (e.g. using the
keyboard). In this example, the quickest or most suitable option is used. Apart from a few
exceptions, no alternative methods of operation or procedures are explored here.
&\FOLFH[HFXWLRQOHYHO
F\FOH
5XQWLPHJURXS 5XQWLPHJURXS
&DQEHVZLWFKHGRQRII
Tasks
A DCC task is available for the user programming in each of the five cyclic execution levels (in
descending order of priority):
• T1: servodcc in the servo level
• T2: ipodcc in the IPO level
• T3: ipodcc_2 in the IPO_2 level
• T4: dccaux in the DCCAUX level
• T5: dccaux_2 in the DCCAUX_2 level
Further information on the execution system of SIMOTION can be found in Section Execution
system / tasks / system cycle clocks of the SIMOTION SCOUT Basic Functions Function Manual.
Execution groups
The available tasks (sampling time and execution sequence in the system: T1 to T5) are assigned
execution groups. The blocks are embedded into these execution groups. The execution groups
therefore allow the task to be structured or divided as required by the user; e.g. dancer control,
setpoint processing, etc. The execution groups are embedded sequentially into the blocks. Only
blocks from one basic chart may be contained in an execution group.
You can use the "Enable" attribute to activate and deactivate an execution group. Normally,
execution groups are processed in cycles; however, the enable attribute can be used for
switching individual execution groups on and off.
A BOOL-type block output can be connected to enable an execution group or a block group. To
do this, highlight the connection to be interconnected and select the Interconnection with
execution group... command in the context menu.
Note
The Interconnection with execution group... command is only supported with DCC SIMOTION.
Execution sequence
For tasks: The execution sequence corresponds to the sequence in which execution groups and
blocks are inserted within a task.
The same applies to groups: The sequence in which the individual blocks are inserted is the
execution sequence within the execution group.
You can change the execution sequence.
To move blocks that have already been inserted from task T2 to higher-priority task T1:
• Double-click the T2 symbol.
• The execution groups are displayed in the right-hand window:
– When you highlight the execution group, the blocks it contains are displayed (including
the chart/block name, comment and position).
– Highlight the execution group that you want to move in task T2 and use drag-and-drop to
drag it to the task T1 symbol in the left-hand window. The right-hand window is now
empty.
– When you double-click task T1 to open it, the execution group that you have moved will
be displayed there.
• Close the window via Chart > Close and proceed to the next step.
HMI variables
You can declare block inputs and outputs as HMI variables and therefore generate a static
interface for these for use in your system visualization. This interface is largely static from an HMI
point of view, i.e. not every change made to the DCC configuration demands that the address
information of the HMI system be reimported.
The memory image with the HMI variables is not automatically deleted during compilation. It is
only deleted on request.
HMI variables that are removed from the DCC when the block that defined them is deleted
remain in the memory image until reorganization is requested during compilation in the DCC.
&RQWURO
0HPRU\LPDJH
ZLWK+0,
YDULDEOHV
'&&FKDUWV
2SHUDWRU3DQHO
HJ:LQ&&IOH[LEOH
@ variables (SIMOTION)
Comment Meaning
SIMOTION: The connection is entered as an HMI variable in
@name <<variable comment>> SIMOTION. Name is the part before the first blank
(whereby you must adhere to the ST conventions
(Page 226)).
The text which follows the variable name (separated by a blank), is transferred as a variable
comment. It is then displayed in the symbol browser. The variable identifier results from the
variable name.
The data type of the published input/output is taken over by the block connection. Where
necessary, it is mapped onto the appropriate data type of the engineering system.
No help function can be created for @ variables.
Exporting to WinCC
Procedure
A created DCC chart can be exported to WinCC, whereby the export specifications of the
SIMOTION SCOUT also apply for DCC charts. However, for this to happen the OPC-XML export
must be activated in the Properties dialog box of the chart in SIMOTION SCOUT.
In the engineering system, right-click the chart and select Properties in the context menu. The
export is activated via Enable OPC-XML on the Compiler tab.
The export can be performed in SIMOTION SCOUT via Options > Export OPC data.
Note
Please observe the Specifications for assigning names in DCC SIMOTION (Page 226).
Procedure
Interconnection can be performed as follows:
1. Select the block connection to be interconnected.
2. Execute the Insert > Interconnection to operand command in the menu. The
interconnection to a global operand can also be performed via the context menu of the block.
The Symbol Input Help window appears.
3. You can now navigate in the CPU or technology object assigned to the chart and select the
device variable to be interconnected – the application highlights compatible device variables
in bold-face type.
4. Click OK to close the window.
From this point on, the selected block connection is interconnected with the global operand and
the global operand is represented by a sheet bar variable in the DCC editor.
Note
The global variables and the I/O variables must first be created and then the interconnection
performed.
Note
You can search for a variable name or a parameter text in the search field of the Symbol Input
Help dialog box.
Procedure
Interconnection can be performed as follows:
1. Create a new ST program with an array variable in the SIMOTION SCOUT engineering system
using the Insert ST program command.
2. Right-click and select Interconnection with operand from the context menu. The Symbol
Input Help window appears.
Alias parameter
You can assign alias identifiers in the DCC editor for variables. The reason for assigning an alias
may be that a name is too long - the DCC editor only accepts a maximum of 49 characters for
identifiers.
Procedure
An alias can be created as follows:
1. Right-click the block connection and select Interconnection with operand from the context
menu. The Symbol Input Help window appears.
2. Select the connection that is to be defined by the alias.
Preliminary remarks
The following is a brief explanation of what you will be configuring in this chart.
Configuration example
The configuration example deals with a straightforward oscillating circuit that creates sinusoidal
oscillation at its output.
It will only take you a few minutes to create the chart; then you can execute it in test mode as
a demonstration.
The following blocks are used:
• Two integrators (INT)
• One inverter (SII)
As indicated by the differential equation f"(x) = - f(x), the oscillating circuit is comprised of two
integrator blocks that are linked by negation.
The frequency of the oscillating circuit is determined by the integrating time constant at the
integrators.
The oscillation amplitude is specified by the initial value at the integrator output.
The DCC editor can be started via the SIMOTION SCOUT engineering system.
• If the Open editor automatically option is activated, the DCC will be started automatically.
Alternatively, you can open the DCC by double-clicking the entry dccreg1.
• If a library has not yet been imported, at this point you will be prompted to import one:
Select TPdcblib_SIMOTION_4_2.3.0 [x.y] in the left-hand window, then click >> and
finally Close.
This creates the project structure and a chart. All that remains is to create some activity within
the chart, i.e. by inserting blocks and interconnecting them.
• Open a block family in the Closed-loop control family with the closed-loop control blocks.
• Select the required block and insert it in the chart using drag-and-drop. Only the outline of
the block in dashed lines is displayed during the copying procedure. Release the mouse
button at the required point.
• To search for a block, enter its name in the input field of the block catalog and click
the binoculars button. The search process begins. Once the block has been found, insert it
in an empty space on the chart using drag-and-drop.
Note
If blocks are superimposed on the chart with other elements, such as other blocks or the
sheet bar, the superimposed block will be displayed in gray and its connections will not be
visible. You must reposition the blocks to ensure that all block information can be viewed.
Procedure
• Select the Y output of the first INTegrator, followed by the X input of the second INTegrator.
• Select the Y output of the second INTegrator, followed by the X input of the inverter (SII).
• Select the Y output of the inverter (SII), followed by the X input of the first INTegrator.
The autorouter creates the connecting lines from the outputs to the inputs and they are then
interconnected.
Figure 5-9 Chart "dccReg1" with interconnected blocks. Some connections have been assigned values that differ from the
default values.
As of DCC 2.1/SIMOTION RT 4.2, user-defined data types structured for DCC SIMOTION can be
used for block connections. The structure definitions are taken from the DCC block library.
Purpose
Signals associated with one another from a technological perspective can be combined to form
structures.
For example, this means that a setpoint, factor, and control signal can be transferred as related
components of the same structure. The structure can be extended at block level; this means
there is no need to make any changes in the DCC chart.
Creating structures
New structures can only be generated by blocks that have been created with the SIMOTION CLib
Studio. Structures cannot be defined in the DCC editor.
Arrays are represented by individual symbols for display in the CFC editor.
Example: FIELD|2|.
Double-clicking a structure element or clicking the Properties button opens a dialog box that is
similar to the one for a block connection of an elementary data type.
Example of an ST source file for the interconnection of input X of the RMDP DCC block
INTERFACE
USEPACKAGE dcblib_simotion_4_3;
VAR_GLOBAL
x: DCB_RMDP_PAR;
END_VAR
END_INTERFACE
An input or output parameter of a block (in this case RMDP) with the appropriate structure type
can then be interconnected to the global ST variable via Interconnection to operand.... For
subcharts, the input of the block must already have been interconnected previously to an input
or output parameter of the subchart.
Note
DCB blocks with user-defined structures may only be edited as of SIMOTION 4.2.
Libraries with structures may not be generated for older SIMOTION versions.
Block types with user-defined structures may not be used in DCC SINAMICS.
Compiling
You can begin compiling with Chart > Compile > Charts as program... or via the button.
If errors occur during compilation, the Logs dialog box will automatically be displayed at the end
of the procedure (just as in the case of the consistency check).
Note
You can check whether all the required block libraries and technology packages have been
activated via the menu item Options -> Block types.
Compilation options
For detailed information about the compilation options, refer to Compiling (Page 52).
Note
The Reorganize HMI variable interface option enables you to reassign the addresses for all @
variables currently defined in the chart. @ variables that are still available in the interface, but are
no longer used in the charts, are deleted.
After compilation
On completion of the compilation procedure, a detailed compilation log appears.
• To access the relevant block that is causing an error, select the error line in the log and
click Go to.
• The log can be called again at a later point via the menu Options > Logs and, if necessary,
can also be printed out.
Note
The DCC editor assigns the configured DCBs to tasks T1 to T5 in the execution system.
Complete documentation
The example has been successfully configured and tested. You can now create the complete
documentation for your example.
You can open the Chart Ref: Display Chart Reference Data window via Options > Reference
data in the menu. In this window, you can use the buttons in the toolbar to create and display
the relevant lists. To begin printing, click:
Then close the dialog box with Reference data > Exit.
Note
The Chart Ref: Display Chart Reference Data window can only be opened when the window
of the execution editor is not open.
Printing a chart
You also want to print the chart. Since only one page has been used on this chart, a single page
display is recommended for printing. The chart is now set to Page view. To begin printing,
click:
If your chart consists of several pages, we recommend that you print them individually in the
page view. Click the button to change to the page view.
Click or to customize the display so that all DCBs are shown on a single page on the PC
monitor.
See also
Compiling the DCC in the DCC editor (Page 222)
Note
In the DCC editor, the length of the name is restricted to a maximum of 49 characters. In
SIMOTION, however, longer names are supported. Where this arises, it is necessary to either use
aliases or interpose ST variables.
The names in the DCC editor must therefore abide by the following rules:
• Basic chart:
– No keyword or previously defined name permitted
– Must start with a letter
– May contain numbers, letters, and underscores
– "_" must be followed by a number
• Subchart:
– Must start with a letter
– May contain numbers and letters
– Underscores are not permitted
– Keyword or previously defined name permitted (during compilation, a check is performed
to determine whether this is unique)
– During compilation in the DCC editor, the name is checked to determine whether it is
unique
• Block instance:
– Can start with a number
– May contain numbers and letters
– May not start with an underscore
– Keyword or previously defined name permitted
– In the DCC editor, a check is performed to determine whether the name has previously
been defined
• Execution group:
– Keyword or previously defined name permitted
– In the DCC editor, a check is performed to determine whether the name has previously
been defined
• Chart connection:
– No keyword or previously defined name permitted
– In the DCC editor, a check is performed to determine whether the name has previously
been defined
*) The chart name and block name must jointly consist of a maximum of 24 characters, including
separating characters.
See also
Rules for assigning names in the DCC editor (Page 226)
Representation Meaning
Blue on white Representation of the values in edit mode (offline)
Black asterisks on yellow Values during transfer to the dynamic display
Black value on yellow Representation of the values read from the SIMO‐
TION RT in test mode
#### on a red background Representation of values while the dynamized val‐
ues required from the SIMOTION RT are missing
(fault, overload)
Abbreviation Description
(G)UI (Grapical) User Interface
Connection General term for block input or block output
BI parameter Binector Input parameter. The parameter is used for the interconnec‐
tion of a binector to a sink signal that can only have the states 0 or 1
BICO Binector-Connector that designates an interconnectable parameter in
the drive
BO parameter Binector parameter (also Binector Output parameter).
The parameter can be used as a binary signal source (0 or 1)
CFC Drive Control Chart
CI parameter Connector Input parameter.
The parameter is used for the interconnection of a connector to a sink
signal
CO parameter Connector parameter (also Connector Output parameter).
The parameter can be used as a signal source
CSV Comma Separated Value, text format for column-oriented data
DCB Drive Control Block
DCC Drive Control Chart
DO Drive Object
ELF file File coded in Executable Linkable Format
FEAT Feature document
ITCP Instance, Time slice, Connection and Parameter/Variable
MBCS Multi-Byte Character Set, corresponds to UTF-8
MDI Multiple-Document Interface – an application with several windows
OEM Original Equipment Manufacturer
TP Technology Package
A.2 Glossary
Execution level Interface to the execution system used for the execution of
blocks.
Execution group Execution groups are used for structuring or subdividing exe‐
cution levels. The blocks and/or charts are integrated sequen‐
tially into the execution groups.
SIMOTION only: Execution groups, for example, can be switch‐
ed on and off separately through a connection to a block out‐
put (data type BOOL).
When an execution group is switched off, all blocks/charts
contained therein are no longer calculated.
Execution sequence Sequence in which the blocks should be calculated in an exe‐
cution level or execution group
User library A user library which contains block libraries. As the blocks are
based on charts, they can be handled individually in this case.
Output connections The output connections can be interconnected to other inputs
or assigned an initialization value. The value is then active at
this connection when the block is calculated in the INIT mode
for the first time. This is useful, for example, when a specific
value is to be assigned to the output connection of a flip-flop
block or a controller block.
HMI variables You can declare block inputs and outputs as HMI variables
and therefore generate a static interface for these for use in
your system visualization.
Basic library A library that has been created in C, e.g. with the aid of a DCB
tool.
Such a library is a closed unit, i.e. a DCB cannot, for example,
be separated from a library in order to transfer it to another
block. The supplied DCBLIB is an example.
Basic chart The chart that is visible and can be managed in STEP 7 or
SCOUT/STARTER. All other charts, i.e. chart partitions or sub‐
charts can only be managed in the DCC editor. Only the term
chart is used in the following.
Block help Detailed information about a certain block type can be ob‐
tained by selecting the block and pressing the F1 key.
Block type library Consists of the description of the block types contained in the
library and the object file that implements the blocks, e.g. ELF.
INIT mode Initialization, ramp-up
RUN mode Cyclic operation
DCB library A user-defined DCB is created from a chart.
DCB studio Development environment for the programming of C block
libraries.
DCB viewer You can read the descriptions of the individual block types in
the DCB viewer during the configuration in the DCC editor. The
DCB viewer is opened by selecting a block and pressing the F1
key.
" C
"Enable" attribute, 224 Chart as block type, 88
Execution group, 224 Multiple interconnection, 93
Chart partition, 32
Chart reference data
@ Block type cross references, 75
Execution group cross references, 75
@ parameter, 154, 205
Operand cross references, 75
@ variable, 205
Compiling, 53
Configuration example
SIMOTION, 210
A Configuring the block display, 41
Abbreviations of the data types, 43 Connection
Alias identifier, 208 Publishing, 154
Array and name lengths, 227 Creating a new device, 27
SIMOTION, 227 Creating a new project, 26
B D
Basic chart, 32 Data types
Block Abbreviations, 43
Block connection units, 41 DCB libraries
Configuring the display, 41 Installing, 103
Delete, 45 Uninstalling, 103
Deleting online, 72 DCB library
Execution properties, 39 Change, 55
Execution sequence, 39 DCC
Hidden connections, 41 Consistency Check, 52
Inserting online, 72 Creating an interconnection online, 71
Interconnecting, 42 Deleting a block online, 72
Pseudo comment, 41 Deleting an interconnection online, 70
Superimposition, 37 Inserting a block online, 72
Block catalog Moving an interconnection online, 71
Binoculars, 37 Reference data, 75
Search, 37 DCC chart
Block library, 88 Compiling, 53
Changing the language, 85 Copy, 56
Delete, 86 Copying block groups, 56
Importing, 81 Exporting to WinCC, 205
Naming convention, 81 Insert as SIMOTION chart, 105
Updating, 81 Insert as SINAMICS chart, 105
Block type Insert block, 36
Plant view, 36 Map listing, 54
Timing diagram, 36 Project storage location, 33
Block types, 79 Publishing all connections of all blocks, 48
Publishing all connections of one block, 49
K S
Know-how protection Set system cycle clock, 203
Drive unit, 108 SIMOTION
Know-how protection drive units Configuration example, 210
Deactivating, 110 SIMOTION SCOUT
With copy protection, 108 Copy DCC chart, 56
Without copy protection, 108 Creating a project, 26
Know-how protection for drive units Inserting a DCC chart, 29
Absolute know-how protection, 110 Inserting a device, 27
Activating, 108 Selecting technology packages, 83
Combining with write protection for drive SIMOTION trace, 209
units, 110 Software requirements, 201
Subchart, 32
L
Load to PG
T
SIMOTION SCOUT, 132 Tasks, 202
STARTER, 133 Test mode, 62
Deactivating, 69
Laboratory mode, 62
M Log on connection, 66
Monitoring, 66
Map listing, 54
Monitoring cycle, 62
Operating modes, 62
Power up, 64
O Process mode, 62
OPC XML export, 205 Trend display, 67
Value display, 67
Trace, 209
P Trend display, 67
Typical
Parameter
Multiple interconnection, 93
Alias, 208
Pseudo comment, 41
Publishing
Connection, 154
V
Value display, 67
R
Rearranging parameter numbers, 46
W
References, 3 Write protection for drive units
Representation of the dynamic value display, 228 Activating, 117
Rules for assigning names Deactivating, 117
Basic chart (SIMOTION), 226
Block instance (SIMOTION), 226