DCC Programming
DCC Programming
1
SINAMICS/SIMOTION SINAMICS/SIMOTION DCC editor description
______________
Introduction
2
______________
DCC editor functionality
SINAMICS/SIMOTION
3
______________
DCC for SINAMICS
4
SINAMICS/SIMOTION DCC editor ______________
DCC for SIMOTION
description
A
Programming and Operating Manual
______________
Appendix
11/2009
6SL3097-4AN00-0BP0
Legal information
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
with a safety alert symbol, indicates that minor personal injury can result if proper precautions are not taken.
CAUTION
without a safety alert symbol, indicates that property damage can result if proper precautions are not taken.
NOTICE
indicates that an unintended result or situation can occur if the corresponding information is not taken into
account.
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 for the specific task, 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 adhered to. The information in the relevant documentation must be observed.
Trademarks
All names identified by ® are registered trademarks of the 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 a separate list of references.
This documentation is included as electronic documentation with the supplied SIMOTION
SCOUT.
The SIMOTION documentation consists of 9 documentation packages containing
approximately 80 SIMOTION documents and documents on related systems (e.g.
SINAMICS).
The following documentation packages are available for SIMOTION V4.1 SP4:
● SIMOTION Engineering System
● SIMOTION System and Function Descriptions
● SIMOTION Service and Diagnostics
● SIMOTION Programming
● SIMOTION Programming - References
● SIMOTION C
● SIMOTION P350
● SIMOTION D4xx
● SIMOTION Supplementary Documentation
SINAMICS documentation
The SINAMICS documentation is organized into 2 parts:
● General documentation/catalogs
● Manufacturer/service documentation
A current overview of the documentation in the available languages can be found on the
Internet:
http://www.siemens.com/motioncontrol
Select the menu items "Support" --> "Technical Documentation" --> "Overview of
Publications."
The Internet version of DOConCD (DOConWEB) is available on the Internet:
http://www.automation.siemens.com/doconweb
Information on the range of training courses and FAQs (Frequently Asked Questions) are
available on the Internet:
http://www.siemens.com/motioncontrol
Follow the menu item "Support".
Additional support
We also offer introductory courses to help you familiarize yourself with SIMOTION.
For more information, please contact your regional Training Center or the main Training
Center in 90027 Nuremberg, Germany.
Information about training courses on offer can be found at:
www.sitrain.com
Technical support
If you have any technical questions, please contact our hotline:
Europe / Africa
Phone +49 180 5050 222 (subject to charge)
Fax +49 180 5050 223
€0.14/min from German wire-line network, mobile phone prices may differ.
Internet http://www.siemens.com/automation/support-request
Americas
Phone +1 423 262 2522
Fax +1 423 262 2200
E-mail mailto:techsupport.sea@siemens.com
Asia / Pacific
Phone +86 1064 757575
Fax +86 1064 747474
E-mail mailto:support.asia.automation@siemens.com
Note
Country-specific telephone numbers for technical support are provided under the following
Internet address:
http://www.automation.siemens.com/partner
Preface ...................................................................................................................................................... 3
1 Introduction.............................................................................................................................................. 11
2 DCC editor functionality ........................................................................................................................... 17
2.1 Overview ......................................................................................................................................17
2.2 Requirement.................................................................................................................................19
2.3 Establish the project requirements ..............................................................................................20
2.3.1 Create a project............................................................................................................................20
2.3.2 Inserting a device into a project ...................................................................................................21
2.3.3 Inserting the DCC chart in a project.............................................................................................23
2.3.4 Inserting a new chart (subchart) ..................................................................................................27
2.3.5 Inserting new chart partitions .......................................................................................................27
2.3.6 View and representation ..............................................................................................................28
2.4 Library handling ...........................................................................................................................29
2.4.1 Importing block libraries ...............................................................................................................29
2.4.2 Updating the block library ............................................................................................................30
2.4.3 Changing the block library language ...........................................................................................32
2.4.4 Removing block libraries from the configuration..........................................................................34
2.4.5 Exchanging the basic library version for installed libraries ..........................................................35
2.5 Handling blocks............................................................................................................................36
2.5.1 Introduction ..................................................................................................................................36
2.5.2 Inserting blocks in the DCC editor ...............................................................................................36
2.5.3 Inserting text.................................................................................................................................38
2.5.4 Specifying execution properties ...................................................................................................40
2.5.5 Editing block connections ............................................................................................................41
2.5.5.1 General ........................................................................................................................................41
2.5.5.2 Block connection properties.........................................................................................................41
2.5.6 Interconnecting blocks .................................................................................................................44
2.5.7 Data type abbreviation in the DCC for connection and transformer blocks.................................45
2.5.8 Interconnection to chart connections ...........................................................................................46
2.5.9 Interconnection to global operands in DCC SIMOTION ..............................................................47
2.5.10 Deleting blocks.............................................................................................................................47
2.6 Compiling .....................................................................................................................................48
2.6.1 Consistency check without code generation................................................................................48
2.6.2 Compiling the DCC in the DCC editor .........................................................................................49
2.6.3 Error log .......................................................................................................................................51
2.7 Editing configurations further .......................................................................................................52
2.7.1 Editing programs further: overview ..............................................................................................52
2.7.2 Changing the block library ...........................................................................................................52
2.7.3 Copying of charts or chart sections .............................................................................................53
2.7.4 Search in the project from STARTER/SCOUT ............................................................................55
2.7.5 Replace in the project from STARTER/SCOUT ..........................................................................56
2.8 Test mode ....................................................................................................................................57
2.8.1 Test modes ..................................................................................................................................57
2.8.2 Monitoring in laboratory mode .....................................................................................................58
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
flipflop, 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 DCCs 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 10 different sampling times can be configured.
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
basic system interconnection via BICO parameter to
the basic system
Execution system Any number of execution groups that Maximum of 10 execution groups that
can be assigned five time slices can be assigned 10 different sampling
(depending on the system cycle times
clocks)
Consistency in the data transfer Consistent data transfer also across Consistency in the data transfer must
the time slices be established by the user, when
required, by means of standard blocks
(SAH_X)
Use of libraries Additional libraries can be used No additional libraries can be used
(Page 154)
Scope of standard blocks See SINAMICS/SIMOTION Function See SINAMICS/SIMOTION Function
Manual, Description of the standard Manual, Description of the standard
DCC blocks DCC blocks
'&& &)&
$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.
2.2 Requirement
This description refers to the following device SW versions:
● DCC 2.0.5
● SIMOTION P, C, D as of Version 4.1.5
● SINAMICS Integrated of the SIMOTION D410 as of Version 2.5
● SINAMICS Integrated of the SIMOTION D as of Version 2.6
● SINAMICS S120, S150, SM150, G130, G150, GM150, GL150 as of Version 4.3
● SINAMICS DCM as of Version 1.1
Except for the load level, the SINAMICS DC MASTER as of Version 1.1 supports the
same function scope as SINAMICS S120 as of Version 4.3.
Detailed information about SINAMICS DC MASTER as of Version 1.1 is contained in the
SINAMICS DC MASTER 6RA80 DC Converters operating instructions.
● At least CFC 7.0.1.3 must be installed as of DCC 2.0.3.
As well as the SIMOTION SCOUT and STARTER engineering tools as of V4.1.3
Note
Configuration should not be carried out in SIMATIC Manager, but directly using
SCOUT/STARTER. SIMATIC Manager uses a type of syntax for naming new charts that
causes an error when they are compiled in SIMOTION SCOUT/STARTER.
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 all' 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. 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.
Note
It is only 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 CFC 7.1 can no longer be
edited with CFC 7.0.1.3.
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 function from the PROGRAM subitem of the device.
SINAMICS, STARTER:
Execute the Insert DCC function on the desired drive object. There may only be one DCC
on a drive object.
Figure 2-6 Inserting a DCC in the CU drive object of a SINAMICS CU3x0.x drive unit with
STARTER
Figure 2-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 2-9 Connection between the types of chart in the DCC editor
Requirement
You have already created a DCC in the SIMOTION SCOUT/STARTER engineering system
which is opened in the DCC editor.
Procedure
1. Use View > Overview or the button to switch from the page view to the chart
overview. The six pages of the selected DCC are now shown.
2. You can now insert new subcharts using the menu item Insert new chart in the context
menu and open these by right-clicking the subchart and selecting the Open command in
the context menu.
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.
Note
The standard library is automatically installed during setup, however if you accidentally
uninstall the library it can be reinstalled via the DCC setup.
The libraries for SINAMICS can also be installed via the SSPs (SINAMICS Support
Packages).
The libraries for SIMOTION are also available via the menu command Extras -> Install
libraries. See also Creation of block libraries (Page 154)
● 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 125)
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 an error is detected when a library is being imported, an error log with details of the causes
of the error is displayed.
● 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.
The basic libraries are selected from the DCC charts used in the dialog Options → Block
types of the DCC editor.
If there are no DCC sources available at the DCC charts, you can open a dialog via the
context menu Block types of the DCC chart, where you can exchange the block libraries
used.
2.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.
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 2-17 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 2-18 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.
2.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.
Note
The specified limits for the possible number of connections 2...120 are not valid; the above-
mentioned limit of four input signals applies.
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:
● @ variables (SIMOTION) (Page 149)
● Creating customer-specific parameters ("declare") (Page 98)
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:
Table 2- 2 Conversions
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.
2.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!
Note
The interconnection to the chart connection by the context menu is available only
when at least one chart connection exists already. The first interconnection to the
chart connection functions only with drag&drop.
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 connections is only permitted for subcharts.
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.
2.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.
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.
WARNING
After copying, you must check whether the interconnections of published block connections
in the chart copy have to be adapted to another drive object as a result of the copying.
During copying, no automatic adaptation of the interconnections of the chart copy is made
to the basic system or to other DCCs.
Overall chart interconnections are converted into text interconnections when copied.
Note
Only one DCC per drive object may be created in the STARTER engineering system.
Note
If charts are to be copied from one project to another, then STARTER or SCOUT must be
started twice as only one project can be opened in each. Please note that, outside the
engineering system, you can only copy and not cut.
Note
When copying a device, the associated charts are also copied.
An XML export or XML import of individual charts is not possible, but the associated DCCs
are contained in the project export.
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.
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) and alias definitions used in the
DCC 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.
NOTICE
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.
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.
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 68).
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 changed value is only visible when the connection has been logged on for testing.
Figure 2-27 Inserting a block pin into the value or trend display
Note
Please note that online changes can only be made in test mode.
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.
From SINAMICS 2.6. onward, all non-interconnected block inputs can be changed in test
mode. They do not have to be published.
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.
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 they have already been compiled,
a prompt will inform you of this differentiation. Download the changes into the target
system so that monitoring and changes can be performed in test mode.
The download is performed when the target device is stopped. With SINAMICS, the
download only functions in the "Power-on inhibit" and "Ready for power on" operating
modes.
Note
You can also generate the reference data of a DCC or a DCC library via the context
menu with the Reference data > Generate command and then display it via Reference
data > Display.
You can then always display the reference data again, but you only have to generate it
once when first called or after changes to the @ variables.
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.
3. When using the know-how protection function for the first time, you will be prompted to
enter the required access data (login & password) for protection of the chart in the Know-
How Manager window. Close the Know-How Manager window via the OK button.
Note
The know-how protection is not automatically reactivated in SIMOTION
SCOUT/STARTER when you close the DCC.
Note
This specification is applicable 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 recompiled. The corresponding DCC license (CFC for
SIMOTION / SINAMICS) is required for this.
3.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 DCC SINAMICS option package contains on a USB stick the Step7 CFC license
required for the DCC editor. The installation is made using the Step7 Automation License
Manager (refer to the help of the Step7 Automation License Manager). The Step7
Automation License Manager program is installed automatically together with STARTER.
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. The SINAMICS CU3x0, SINAMICS CUD
or the SIMOTION D4xx then must be switched off and on once. Only then can the DCCs be
downloaded and run on the drive objects.
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 can be created per drive object (DO = drive object). This DCC can contain
up to ten execution groups.
WARNING
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).
Note that the execution groups created in the chart are only visible in the Set execution
groups window after the chart has been compiled.
In the offline mode of the STARTER / SCOUT V4.1.x, r21002 and r21003 are always
displayed with the value 0 in the Set Execution Groups window.
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 the p21000 parameter (Properties execution group) and so also in the context menu of
the "Set sampling times" chart, the write access for 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.
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 3-2 Calling the "Receive AFTER IF1 PROFIdrive PZD" execution group for isochronous
PROFIBUS communication. See also 3).
Received 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 -
r2095. 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.
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 CPU time available for this execution group falls 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 you want to calculate a larger number of DCBs, check whether you cannot configure
this
better with the "Receive AFTER IF1 PROFIdr. flexible PZD" execution group.
Note
Note for this execution group that the higher computing time load in isochronous
operation is considered by the load calculation only at the time of the transition (specified
by the PROFIBUS master) into the isochronous operation. This means after the startup of
the drive device, the load of the complete system initially still lies within the permitted
range and only with the transition into the isochronous operation does the drive device
shutdown with fault F1054 (system limits exceeded).
As of SINAMICS software version V4.3, the PROFIBUS data is received and sent at two
separate times.
The "Send BEFORE IF1 PROFIdrive PZD" execution group is processed at the end of
the IF1 PROFIdrive PZD sampling time before the complete data is still sent at the end of
the sampling time. For the non-isochronous (cyclical) communication at the
communications interface IF1, the execution group is calculated cyclically with the
sampling time of the interface IF1 (p2048) (before sending the data), i.e. also before
calculating the connector binector transformer p2080 – p2084 and reading in the
connector inputs p2051[..], p2061[..].
For calculating the utilization of system r9976 correctly, p092 must be = 0 (== factory
setting) in non-isochronous operation.
This means only integer multiples of TZu >= 125 µs can be set 3) as times Ti and To for the
drive.
→ Ti = ni • TZu and TDP = nDP * TZu
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 3-3 Calling the "Send BEFORE IF1 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, i.e. also before
calculating the binector connector transformer p2080 – p2084 and reading in the
connector inputs p2051[..], p2061[..].
The calculation of the execution group must be completed within sampling time Ta];
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 CPU time available for this execution group becomes smaller the more drive axes
are calculated on the CU because the current controller (and the speed controller 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
Note for this execution group that the higher computing time load in isochronous
operation is considered by the load calculation only at the time of the transition (specified
by the PROFIBUS master) into the isochronous operation. This means after the startup of
the drive device, the load of the complete system initially still lies within the permitted
range and only with the transition into the isochronous operation does the drive device
shutdown with fault F1054 (system limits exceeded).
1) IF1 is the abbreviation for communication interface 1. With SINAMICS V2.5 and
SIMOTION 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. With SINAMICS V2.5, IF2 can
only be used by the CAN bus when a CBC10 module has been inserted in the option
slot.
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.
Not every fixed execution group is available on every drive object type. This means, for
instance, that SERVO, VECTOR, VECTORMV... drive object types do not contain any digital
or analog inputs; therefore, the fixed execution groups for the digital inputs/outputs and
analog inputs/outputs are not available here.
Please ensure that the sampling time for DCC SINAMICS is restricted to below 1 ms. As a
property of an execution group, select a fixed execution group in which the sampling time for
the assigned system function is < 1 ms. This execution group will thus only be called with the
sampling time of 1 ms, and will thereby deviate from the assigned system function. Fault
F51004 (see r0947) is set to indicate this deviation. The fault value of the fault (r0949) + 1
gives the number of the execution group where the deviation has occurred.
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.
Note
As regards offline configuration using STARTER commissioning software, values 0 -
256 can be entered in p21000[0..9], even if this violates the limits stated above for the
hardware sampling times from 1 ms ... <r21003. This will only be detected once the
Control Unit has been downloaded, and will result in the use of a replacement value
and the F51004 fault. If the set value is too small, 1 ms will be set as substitute value;
if it is too large, the next largest SW sampling time will be set.
– 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 3-5 Properties - Connection window of the connection S (= Set) of the block INT
(= INTegrator)
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, 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 3-7 Property 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 98).
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.
3. Right-click and select Interconnection with operand... from the context menu. The DCC
Signal Selection window appears.
Note
BICO parameters defined in other DCC charts will not be displayed in the signal selection
list.
Links to BICO parameters in other DCC charts can be drawn in the DCC editor directly
between the charts.
WARNING
After copying, you must check whether the interconnections from and to published block
connections in the chart copy have to be adapted to another drive object as a result of the
copying. During copying, no automatic adaptation of the interconnections of the chart copy
is made to the basic system or to other DCCs.
WARNING
After copying, you must check whether the interconnections from and to published block
connections in the chart copy have to be adapted to another drive object as a result of the
copying. During copying, no automatic adaptation of the interconnections of the chart copy
is made to the basic system or to other DCCs.
3.1.4 Computing time load, memory requirement and assignment of the HW sampling
times
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.
3.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 A50512. 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.
NOTICE
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).
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 load 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 load 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 load (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 load in r9976 will be displayed only after the project download
and the subsequent CU startup.
As of V4.3, the permitted maximum value of the computing time load 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 DCC with approx. 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 approx. 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 DCC with approx. 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 DCC with approx. 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 DCC with approx. 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 DCC with approx. 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.
1) The chart with 75 blocks consists of an execution group with the following blocks in the
listed 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) Allsampling 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 120
@Parameters1 350 120
SINAMICS 2.6.2 Blocks1 500 200
@Parameters1 500 200
2) SINAMICS G130, G150, S120, S120 Chassis, S120CM, S150
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 SINAMICS Integrated3
with 1 servo axis with 1 vector axis Integrated3 with one vector axis
with one servo
axis
SINAMICS Blocks1 550 450 320 220
2.6.1 @Parameters1 550 450 320 220
SINAMICS Blocks1 700 600 400 300
2.6.2 @Parameters1 700 600 400 300
2) SINAMICS G130, G150, S120, S120 Chassis, S120CM, S150
3) S120i on D4x5
When expanding the topology on a drive unit with TMxx or DMC20 modules, one drive unit
must be omitted for each additional TMxx module.
Please note when connecting CX32 modules to a D4x5 that memory and CPU time are also
allocated for each CX32 on the D4x5. When using the DCC, another servo or vector axis
must be omitted for every 2 CX32s (i.e. the axis must be omitted for the first CX32).
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.
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 hardware sampling times to be assigned is displayed in r7903 (from
SINAMICS V2.6 onward).
Note
The number of different hardware sampling times possible on a Control Unit is restricted.
For this reason, software sampling times (multiple of r21003) or, if necessary, the fixed
execution group (p21000[0...9] ≥ 2000) should ideally be used.
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 3-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 3-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 3-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 48).
After compilation
The compilation log is displayed after compilation. If error messages are displayed, the
causes must be corrected before continuing.
You can return to the DCC by selecting Edit > Execution sequence again or by clicking
again.
Note
In the offline mode of the STARTER / SCOUT V4.1.x, r21002 and r21003 are always
displayed with the value. The r21002 value 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.
3.2.11 Loading the DCC technology option onto the CF card of the drive device
When the drive unit is supplied, the DCC technology option will not yet be present on the CF
card of the drive unit. This is loaded to the CF card with the aid of SIMOTION SCOUT or
STARTER.
To do this, call the STARTER, for example, and connect to the drive unit online. 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 Execute in the bottom right of the
window.
A progress bar shows how the downloading process is progressing. Once the downloading
process is complete, the button in the bottom left changes from Cancel to OK.
At present, the Load to PG action is not available for DCC SINAMICS.
The window is closed by double-clicking OK.
NOTICE
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 powered up can DCCs be downloaded to the drive unit and run.
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.
3.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.
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 98))
4. Right-click and select Interconnection to operand... from the context menu. The DCC
Signal Selection window appears.
5. Select the parameter to be interconnected.
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, the connection of an unpublished block connection to a BICO
parameter of the basic system results in an error when compiling the chart.
Procedure
Subsequently changed BICO interconnections and parameter values can be read back from
the target system via the menu command of the DCC editor File -> BICO interconnections
and read back parameters.
Input and output BICO interconnections are read back. The read back process always
applies to all DCC charts of a device.
Requirement
● The structure of the block instances and interconnections are the same both online and
offline.
● The sources of the DCC chart must be available.
● It is not possible to read back BICO interconnections in the case of DCC charts that have
been loaded from a target device into an empty project.
3.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 3-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.
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.
3.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 interfaces declared 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.
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.
3.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.
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
values required from the drive object are missing
(fault, overload)
4.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
Task
Five DCC tasks are available in each execution level for user programming.
The main features of the tasks are:
● Start behavior: When and under what conditions is a task started?
● Priority: Which task is interrupted by which other task?
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 Interconnect with
execution group command in the context menu.
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.
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 176)).
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 176).
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 IO 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.
From this point on, the selected block connection is interconnected with the array element
and the array element is represented by a sheet bar variable in the DCC editor.
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.
4.1.4.1 Fundamentals
The DCC editor offers a function for saving a chart as a block library (DCB library). 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
,PSRUW 2SWLRQV!%ORFNW\SHV
!
%
OR
FN
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.
Note
You can display the chart connections via the button in the toolbar.
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 46)
See also
Creating an installable DCB library from DCC libraries (Page 160)
4.1.4.2 Creating comments for DCB libraries you have created yourself
In the SIMOTION SCOUT engineering system, you can save additional information on
individual blocks of a DCB library that you have created yourself.
Procedure
1. Select the block library you want to edit in the SIMOTION SCOUT engineering system.
2. In the context menu of the DCB library, select the Block type properties item.
3. In the Block Type Properties window, select the DCC to be edited and click the Extra
block type properties button.
4. Now enter the information you require and then close the window with OK.
Figure 4-9 Connection example for a 1:N interconnection without NOP block
Figure 4-10 Connection example for a 1:N interconnection with NOP block
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. An error log appears in the output window in the lower part of the dialog
box.
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 created DCB library can be found in
Section Creating the online help for block libraries (Page 161)
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.
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. Further elements for the description (e.g. Truth table, Block diagram, Example, etc), are
available in the right-hand Elements pane, 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.
Note
Detailed operating instructions for the DCB help editor can be found in the menu under Help
> Help contents.
Note
The libraries are installed project-independently in SIMOTION SCOUT. The libraries are not
transported when projects are archived or exported. If the project needs to be dearchived or
exported on a different SCOUT, the libraries used there need to be reinstalled. After a
SCOUT reinstallation, the libraries must also be reinstalled.
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.
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 4-19 Chart "dccReg1" with interconnected blocks. Some connections have been assigned values that differ from
the default values.
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 48).
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.
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.
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 or underscore
– May contain numbers, letters and "_"
– "_" must be followed by a number
● Subchart:
– Must start with a letter or underscore
– May contain numbers and letters
– "_" is 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
– "_" is not permitted at the beginning
– 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
See also
Rules for assigning names in the DCC editor (Page 176)
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
SIMOTION RT in test mode
#### on a red background Representation of values while the dynamized
values required from the SIMOTION RT are
missing (fault, overload)
Note
Error analysis when a DCB block crashes
If a DCB block crashes during operation, information about the cause and the block
instance can be found in the device diagnostics buffer in SIMOTION. With this
information, you can contact the creator of the block library, remove the relevant block
instance or change the parameterization.
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
interconnection 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
execution levels. The blocks and/or charts are integrated
sequentially into the execution groups.
SIMOTION only: Execution groups, for example, can be
switched on and off separately through a connection to a
block output (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 are to be calculated in an
execution 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
subcharts 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
obtained 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 builder 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, 174 Chart as block type, 154
Execution group, 174 Dependencies, 159
Multiple interconnection, 158
Chart partition, 26
@ Chart reference data
Block type cross references, 70
@ parameters, 149
Execution group cross references, 70
Operand cross references, 70
Compiling, 49
A
Configuration example
Abbreviations of the data types, 45 SIMOTION, 166
Alias identifier, 153 Configuring the block display, 43
Array and name lengths, 177 Connection
SIMOTION, 177 Publishing, 99
Creating a new device, 21
Creating a new project, 20
B
Basic chart, 26
D
Block
Block connection units, 42 Data types
Configuring the display, 43 Abbreviations, 45
Delete, 47 DCB library
Deleting online, 67 Change, 52
Execution properties, 40 DCC
Execution sequence, 40 Compiling, 49
Hidden connections, 42 Consistency Check, 48
Inserting online, 67 Copy, 53
Interconnecting, 44 Copying block groups, 53
Pseudo comment, 42 Creating an interconnection online, 66
Superimposition, 37 Deleting a block online, 67
Block catalog Deleting an interconnection online, 65
Binoculars, 37 Insert block, 36
Search, 37 Inserting a block online, 67
Block library, 154 Map listing, 50
Changing the language, 32 Moving an interconnection online, 66
Delete, 34 Reference data, 70
Importing, 29 DCC chart
Naming convention, 29 Exporting to WinCC, 150
Updating, 30 DCC editor
Block type Page view, 28
Plant view, 36 Rules for assigning names (SIMOTION), 176
Timing diagram, 36 Sheet bar, 47
Software requirements, 145
DCC Editor, 25