DCC Programming - PDF en-US
DCC Programming - PDF en-US
Introduction 1
03.2007
6SL3097-2AN00-0BP0
Safety Guidelines
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 device/system may only be set up and used in conjunction with this documentation. Commissioning and
operation of a device/system may only be performed by qualified personnel. Within the context of the safety notes
in this documentation qualified persons are defined as persons who are authorized to commission, ground and
label devices, systems and circuits in accordance with established safety practices and standards.
Prescribed Usage
Note the following:
WARNING
This device may only be used for the applications described in the catalog or the technical description and only
in connection with devices or components from other manufacturers which have been approved or
recommended by Siemens. Correct, reliable operation of the product requires proper transport, storage,
positioning and assembly as well as careful operation and maintenance.
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 60 SIMOTION documents and documents on other products (e.g.
SINAMICS).
The following documentation packages are available for SIMOTION V4.1:
● SIMOTION Engineering System
● SIMOTION System and Function Descriptions
● SIMOTION Diagnostics
● SIMOTION Programming
● SIMOTION Programming - References
● SIMOTION C2xx
● 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
If you have any technical questions, please contact our hotline (worldwide):
A&D Technical Support:
● Phone: +49 (180) 50 50 222
● Fax: +49 (180) 50 50 223
● E–mail: [email protected]
● Internet: http://www.siemens.de/automation/support-request
If you have any questions, suggestions, or corrections regarding the documentation, please
fax or e-mail them to:
● Fax: +49 (9131) 98 63315
● E–mail: [email protected]
Note
The DCC editor is a programming system based on CFC (Continuous Function Chart). The
following sections will 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 DCC Block Description Function Manual
'&& &)&
$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
Open the SIMOTION SCOUT/STARTER application and insert a device or drive unit in the
project.
Create a new chart in the project. To do this, use the Insert DCC chart command. You
should then select the DCB library to be used. No blocks are available for selection in the
DCC editor when a block library is not selected here.
In the Import DCB Library dialog box, select the desired language version of the blocks via
the Language with which the DCBs are imported drop-down list box.
It is currently possible to configure the following devices using DCC:
● SIMOTION P, C and D, Version 4.1 or higher
● SINAMICS Integrated of the SIMOTION D, Version 2.5 or higher
● SINAMICS S120, S150, SM150, G130, G150, GM150, GL150, Version 2.5 or higher
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.
If errors occur when charts are being compiled in SIMOTION SCOUT, it is possible to
generate a comprehensive error report by compiling them again in the DCC editor.
Note
The DCC editor is installed automatically with the SIMOTION SCOUT engineering
system. An appropriate program license is required for the DCC editor.
Note
It is only possible to print DCC charts 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.
Procedure
Proceed as follows to create a project:
1. Start the SIMOTION SCOUT 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.
3. In the Create new device window, select the required device and close the window with
OK.
All requirements for creating a DCC chart in the project have now been met.
Procedure
1. Select a device from the project.
2. Execute the Insert DCC chart function from the PROGRAM subitem of the device.
6KHHW
6XEFKDUW
&KDUWSDUWLWLRQV
Figure 2-6 Connection between the types of chart in the DCC Editor
Requirement
You have already created a DCC chart in the SIMOTION SCOUT engineering system which
is opened in DCC Editor.
Procedure
1. Use View > Overview to switch from page view to the chart overview. The six chart
partitions of the DCC chart selected are now shown.
2. You can use the Insert new chart menu item from the context menu to insert new sub-
charts. Double-click on them to open them.
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.
Note
The Chart > New function generates new basic charts in the DCC editor which are visible in
SIMOTION STARTER/SCOUT!
Procedure
You can use drag-and-drop to insert the required block type in the chart from the open
directory.
The New text icon for free text is displayed above the block type directories. You can insert
the text field in the same way as a block.
● Check whether a new version has been installed for each of the libraries that have
already been imported by looking at the library versions under Available libraries and
Imported libraries.
● Select the library to be updated under Available libraries and click >>.
● Select the library to be removed under Imported libraries and click <<.
● Click Accept.
● The progress of the update is displayed in a window.
Note
In SIMOTION, the library is automatically loaded to the device when required. This action
must be performed explicitly for SINAMICS.
Note
When the language is changed, the block type comments will not change unless they
have already been changed within the context of instantiation.
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 that are installed on your
programming device are listed under Available libraries. The libraries that have already
been imported into this configuration are listed under Imported libraries.
● Select the library to be deleted under Imported libraries 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 the imported library.
2.5.1 Introduction
In this section, you will learn which block types are available and how you can insert blocks
in a DCC chart 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 and press the F1
key.
Insert block
You can position the block catalog anywhere on the screen.
● 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. The outline of the
block is represented by a dashed line. Release the mouse button at the required point.
The block (actual size) is displayed on the chart.
● To search for a block, enter its name in the input field of the block catalog and click the
magnifying glass icon. 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.
Requirement
The inputs and outputs of the blocks must possess compatible data types so that they can
be interconnected.
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 autorouter creates the connecting lines between the inputs and outputs and they are
then interconnected.
2.5.4.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, an initialization value can be entered in the Value field of the properties
dialog box. This value is present at the input in the first cycle. Where this refers to an input
that is not interconnected, the value will be present here during subsequent calculation
cycles as well.
Output values
At the block outputs, an initialization value can be entered in the Value field of the properties
dialog box. This value is present at the output in the first cycle. During subsequent
calculation cycles, this initialization value will be overwritten with a computed value.
Note
NB: 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 CFC, so their values will
still be analyzed.
It should also be noted that the inputs of these blocks must be interconnected consecutively,
starting from the first connection.
The following generic blocks exist: AND, ADD, MAS, MIS, MUL, NAND, NOR, SUB, OR,
XOR
In the current version of the DCC editor, four connections are always functionally evaluated
for all generic blocks.
The note above also applies to data-type-specific variants of the blocks listed above.
Pseudo comments
Block connection comments beginning with @ are pseudo comments and are taken into
account during compilation in DCC. Pseudo comments affect the function of the block
connection.
Further information about pseudo comments is contained in the following sections:
● @parameter (SIMOTION) (Page 86)
● Creating customer-specific parameters ("declare") (Page 49)
2.6 Compiling
General
Some of the conditions that have to be met if a valid configuration is to be created from DCC
charts 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.
Compiling
You can begin compiling with Chart > Compile > Charts as program... or via the icon.
The Logs dialog box will be displayed automatically when the compilation task completes
(also for the consistency check). Here, errors are indicated by an "E" and warnings by a "W".
Note
You can check a selected device in the engineering system using the Select technology
packages function in the context menu, which enables you to see whether all necessary
block libraries and technology packages are activated.
Compilation options
You have a choice of three different compilation options:
● 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 by around 25%.
Note
All the configuration charts will be checked for consistency, even if you select the Only
compile changes option.
After compilation
On completion of the compilation procedure, a detailed compilation log appears.
● To navigate to the block that caused the error, select the error line in the log and click Go
to, or double-click the error line.
● The log can be displayed again at a later point via the menu Options > Logs and, if
necessary, can also be printed out.
Procedure
1. Click Options > Block types.
2. The Import window opens. You must close this window by clicking OK.
3. The Import DCB libraries window appears. The block libraries that are installed on your
programming device are listed under Available libraries. The libraries that have already
been imported into this configuration are listed under Imported libraries.
4. Now select the new version of the library from the Available libraries list.
5. The old library must be removed from the previous version.
Behavior
The changes made compared with the old version are transferred to your existing
configuration.
If block type connections that you have positioned in your charts also change, this can affect
the appearance of the blocks. This is because all connections that have recently been
added, or whose properties (such as the data type) have changed, become invisible in the
DCC.
When the parameter lists are read back, the declared parameters and the HMI variables will
not be automatically updated in the chart. The parameter values will be synchronized as part
of the upload/download of the expert list, however, only while no further compilation of the
chart is performed, because this would be overwritten otherwise.
Press function key F5 to update the screen content and display the changes.
Note
If you want to see the connections in the block display again, highlight the block and select
Object properties. You can display them again in the Connections tab.
Note
The copying of charts or block groups between SINAMICS devices and SIMOTION devices
and vice versa is not supported.
Figure 2-10 Inserting a block pin into the value or trend display
Note
The use of test mode requires an online connection to the device.
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.
Note
If you have logged on many objects for the test, it is better to use a slower updating cycle.
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.
● When using the know-how protection function for the first time, you will be prompted to
enter the required access data (user name and password) for protection of the plan in the
Know-How manager window. Close the Know-How manager window via the Closebutton.
Note
The know-how protection is not automatically reactivated in SIMOTION SCOUT/STARTER
when you close the DCC chart.
Starting procedure
The block behavior for the initialization between SIMOTION and SINAMICS was previously
different and has now been matched. For this purpose, the start process of a block was
divided into two phases - Init and Startup. The processing of the individual blocks is
performed in accordance with the level priority (T1, T2, ... T5) and the sequence of the
blocks in the execution groups. The Init and the Startup of a block are called after the
instantiation of the block immediately after each other in a single pass. Only the Startup
phase is performed for the subsequent start processes of the block.
As part of the start process, all blocks will be processed, even those in deactivated execution
groups.
If during the start process of the block an access is made to the connections of other blocks,
this access should be performed in the Startup phase. The Init phase is provided for internal
data initializations.
For interconnected blocks, access to the output value of the upstream block connection is
always possible during the Init and Startup phase (even between levels).
Note
The value of the upstream block connection depends on whether or not this block has
calculated the output pin. In the first case, the calculated value is used, otherwise the initial
value of the output.
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 project after
starting up STARTER/SCOUT, create a DCC chart, 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.
Applications
Combinational logic, 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.
Drive Control Chart (DCC) functionality is available for every drive object of the drive device
listed in the following table.
Features
When the product is supplied, the DCC technology option is not yet available on the drive
device. The DCC technology option must be loaded onto the drive device's CF card in a
separate operation using SIMOTION SCOUT or STARTER. The SINAMICS CU3xx or
SIMOTION D4x5 then has to be switched off and on. Only then can the DCC charts be
downloaded and run on the drive objects.
There is only ever one DCC chart on a drive object. This DCC chart consists of up to 6
pages. DCC can be activated simultaneously on several drive objects on a drive unit. The
DCC technology option is available on the following drive object types:
Note
This additional functionality increases the computing time load. This means that the
maximum possible configuration for a Control Unit is restricted.
Description
Exactly one (1) DCC chart can be created per drive object (DO = drive object). Although this
DCC chart can contain many execution groups, only the first ten execution groups in the
DCC editor can be assigned to fixed or free execution groups of the drive object.
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.
Received data (sent by the master) is always processed and made available at the end of
the sampling time (no*k-1) p0115[0], so that the received process data remains valid until
time To = no * k * p0115[0] at r2050, r2060, r2090, r2091, r2092 and r2093, i.e. in the last
(shortest) sampling time before To. Once the received data has been written to the BICO
outputs, the execution group "Receive AFTER IF1 PROFIdrive PZD" is calculated. The
processing of data that has been received and execution group "AFTER IF1..." are
calculated in the same sampling period Ta.
The calculation must be completed within sampling time p0115[0]; 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 axles are calculated
on the CU since the current controller (and the speed controller if needed) of the drive
axles are also calculated in sampling time p0115[0].
If you want to calculate a larger number of DCBs, please check whether you would not do
better to configure this using the "Receive AFTER IF1 PROFIdr. flexible PZD" execution
group.
3. Connector inputs p2051 and p2061 are read in and data is sent.
The sampling time of this execution group corresponds to the IF1 PROFIdrive PZD
sampling time p2048.
The only difference from the Receive AFTER IF1 PROFIdrive PZD execution group is the
way in which the execution group behaves in isochronous mode. Even in isochronous
mode, this execution group is called using the PROFIdrive PZD sampling time configured
in the Master as with any other time slot. This means that initially all time slots with a
shorter sampling time are called at time To depending on the validity of the receive data
(current controller, if need be speed controller). This execution group is only called first
once the PROFIdrive PZD sampling time starts to be processed. You basically do not
know how often the higher priority, shorter sampling times of the current and speed
controller are calculated before this execution group starts to be processed. Processing
of this execution group is also interrupted by shorter sampling times.
The benefit of this execution group is that considerably more DCBs can be calculated
than in the Receive AFTER IF1 PROFIdrive PZD execution group because the
calculation does not have to be completed after current controller sampling time p0115[0].
If several rated values from this execution group are forwarded to the speed or current
controller in a shorter sampling time, if necessary, the consistency of this data has to be
ensured because an interrupt caused by the shorter sampling times may occur at any
time.
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. In the case SINAMICS V2.5,
IF2 can only be used by the CAN bus when a CBC10 module has been inserted in
the option slot.
Not every fixed execution group is available on every drive object type. This means that, for
instance, 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. Warning
A51004 (see r2122) is set to indicate this deviation. The warning value of the warning
(r2124) + 1 gives the number of the execution group where the deviation has occurred.
Example:
On the SERVO drive object type, select "BEFORE speed controller" as a fixed execution
group.
The system function corresponding to this is the speed controller.
The sampling time of the speed controller is p0115[1] = 125 µs in the factory setting of p0112
= 3.
Please also refer to the description of parameter p0112 in the SINAMICS List Manual.
ways. The two methods have different limits for the maximum possible number of different
sampling times.
● Free execution groups whose sampling times are created in the hardware:
With the hardware sampling times, in p21000[0...9] each integer multiple of the basic
sampling time (read-only in r21002) ranging from 1 * r21002 to 256 * r21002 can be
generated with the following limits:
– Minimum sampling time = 1 ms
– Maximum sampling time = r21003 - r21002 < r21003 (approx. 8 ms; on the D410 of
the DP cycle)
– On the D410 drive device, r21003 always matches the DP cycle (PROFIBUS T_DP
cycle clock) or with the send cycle clock for PROFINET. If 1 ms is configured as DP
cycle / send cycle for PROFINET, this means no hardware sampling times (but only
software sampling times) from DCC are used on this device.
– On a CU or D4xx, a maximum of 13 different hardware sampling times can be used by
DCC and by the drive objects. Consequently, the number of different hardware
sampling times on a drive unit (i.e. for all DCC charts on the drive unit) is limited to a
maximum of five. A sampling time can be used simultaneously by several DCC charts.
Note that the limit on the number of different hardware sampling times for the
configuration in STARTER is not monitored.
– The assignment of the hardware sampling times (sampling time < r21003) can be
fetched from r21008. The 13 available sampling times are displayed in indices 0 - 12
of r21008. If the value of r21008[k] = 0, the sampling time Tk can still be freely
assigned.
If the value of r21008[k] ≠ 0, the value gives the sampling time Tk in milliseconds. If all
indices from r21008[i] ≠ 0, the CU cannot provide any other hardware sampling time
that is different from r21008[0] - r21008[12]. As far as the selection in r21000 is
concerned, only those execution groups (with a sampling time that is < r21003) whose
sampling time is already provided in r21008[0] - r21008[12] can be used. The same is
true for the selection of the execution group in STARTER in the project navigator (left-
hand side) with the context menu of the chart (select the chart and call the context
menu using the right mouse button) from Set execution groups…
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 - r21002. 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 replacement value; if it is too large, r21003 will be set as replacement value.
● 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 SINAMICS/SIMOTION DCC block
description in the Function Manual, as an appendix to the chapter titled "Parameters" ).
Note
1. The assignment of identical names for DCC charts 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-3 Properties windows - connection of the connection S (= Set) of the DCB INT (=
INTegrator)
Where SINAMICS is concerned, input and output connections of DCBs can be declared as
parameters. "Declare" means that the users create the parameters themselves (parameter
numbers and parameter text). This is the prerequisite in order to interconnect the DCB
connections using BICO parameters to the basic system in order to assign the values to the
input connections using setting parameters and to monitor the values of the output
connections using parameters. The parameter number 251 in the above figure and in the
following figure is arbitrary.
3DUDPHWHUQXPEHU )XOOSDUDPHWHUQDPH
# 6WDUW
7KHRSWLRQDODVWHULVNGHQRWHVD%,&2SDUDPHWHU 6SDFH
,IQRDVWHULVNLVSUHVHQWDVHWWLQJSDUDPHWHULVFUHDWHG
The full parameter name, which is separated from the parameter number by a space, is
displayed in the STARTER expert list.
The data type of the declared input/output is transferred by the DCB connection.
For the "declaration" of DCB inputs, a differentiation must be made between setting
parameters (without asterisk) and BICO parameters (with asterisk).
For the "declaration" of DCB outputs, the following differentiation must be made:
● Without asterisk: pure monitoring parameter that can be used to record the trace function.
● With asterisk: as for the case without asterisk, but additional interconnection possible.
DCB inputs to be declared 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
with the mouse on 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
DCB input interconnected with a different DCB is always that of the connected DCB 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 DCB inputs can now be declared without having
to delete the interconnection first.
If the parameters configured on the DCB connections are to be displayed in the DCC editor,
then select Options > Settings > Display ... and select Comment under Connections. The
first eight characters of the comment are then displayed at the respective DCB connections
in the DCB symbols.
If you want to display more than the first eight characters of the comment, then select
Options > Settings > Block / sheet bar width. Then in the Blocks / Sheet Bars window, set
the block width to Wide. The first twelve characters of the comment are now displayed at the
connection.
A parameter number may only be used just once in a chart. The DCC editor does not check
when the parameter number is entered in the properties window of the connection whether
this parameter number is already used in the chart. The multiple use of the parameter
numbers will be indicated as error only when the chart is compiled.
The parameter numbers of the charts are represented on the number range from p21500 to
p25999 of the expert list of the STARTER. With each DCC chart, it is possible to specify
where the parameter range of the chart is to begin. This can be performed in the Parameters
tab in the properties window of the chart in STARTER, using the parameter number base.
Figure 3-5 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
# #
%,&2VHWWLQJSDUDPHWHU %,&2GLVSOD\SDUDPHWHU
ᆱ ᆲ
$'' $'' $'' $''
; < ; < ; < ; <
# #
%,&2GLVSOD\SDUDPHWHU 'LVSOD\SDUDPHWHU
ᆳ ᆴ
$'' $'' $''
; < ; < ; <
%,&2 FRQQHFWDEOH
2XWSXWPXVWEHGHFODUHGVLQFHLQSXWLVGHFODUHGDWWKHVLQN
Example 1: For an interconnection of the DCB connection with the SINAMICS basic system,
the connection must be declared as BICO parameter.
Example 2: Each DCB output connection can be declared as BICO parameter. The signal on
this output can be recorded with the trace.
Example 3: Each DCB output connection can be declared as (not interconnectable) display
parameter. The signal on this output can be recorded with the trace.
Example 4: The DCB input connection X of the DCB ADD 1 is declared as setting parameter.
Example 5: Because the DCB input connection X of the ADD 2 is declared as BICO
parameter, the DCB output connection interconnected with it must also be declared as BICO
parameter. It is, however, possible in the DCC editor to interconnect ADD 1 Y with ADD 2 X
when only the DCB input ADD 2 X is declared. This results in an error message when the
chart is compiled.
Note
No help function can be created for @parameters.
Procedure
Interconnection can be performed as follows:
1. Creating customer-specific parameters ("declare", @Parameter); see previous section.
Note
In the DCC editor, block connections can initially be connected with the drive's BICO
parameters without the need to declare them as parameters. However, this will cause
errors when compiling the chart, since only block connections that have been declared as
@parameters can be connected to the drive's BICO parameters.
Description
The processing of DCBs requires computing time. This means for the activation of the DCC
editor that it is no longer possible to calculate the maximum quantity structure for drive
objects of a CU3xx, D4x5 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 DCBs
● For some DCBs, it depends on parameterization (e.g. the setting of release 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 fall below 85 %. Likewise, the maximum value for the computing time load in r9976[5]
should always fall below 85 %. Exceeding the computing time load limit of 90 % triggers
warning A50512. The warning is reset if the computing time load falls below 88%.
If the computing time load increases to the point that it is no longer possible for all DCBs 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 CU3xx/D4xx. The additional
computing time load is not taken into account by activating the DCC charts.
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 DCBs to their execution groups.
● Establish all connections, both between the DCBs 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 DCBs 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 DCBs (of the above-mentioned types) for a sampling
period of 2 ms.
Approximately 50 DCBs (of the above-mentioned types) in an execution group increase the
computing time load of the CU by approximately 11%.
When commissioning a configuration, the current computing time load must always be
checked online on the drive device for compliance with the limits stated at the start for
r9976[1] and r9976[5].
NOTICE
After the copy, be sure to check whether the interconnections of declared DCB connections
in the chart copy must be changed to another drive object because of the copy. During the
copy, no automatic change of the interconnections of the chart copy is made to the base
system or to other DCC charts.
NOTICE
After the copy, be sure to the check whether the interconnections of declared DCB
connections in the chart copy must be changed to another drive object because of the
copy. During the copy, no automatic change of the interconnections of the chart copy is
made to the base system or to other DCC charts.
Configuration example
The requirement for this example is that there must be a STARTER or SCOUT version
suitable for your SINAMICS SW version installed on your computer. Your computer must
also have a CFC license for using DCC Editor. You can install this license from the USB
stick provided with the help of the Step7 Automation License Manager.
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 Drive Control Blocks (DCBs) are used:
● 2 integrators (INT)
● 1 subtractor (SUB)
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.
14.Archiving a project.
15.Creating documentation.
● Highlight the technology package in this window and confirm by selecting OK.
● You can now insert a chart.
● The Insert DCC chart window opens and you can enter a new name (of no more than 8
characters) for the chart (in our example dccReg1) and comments. Please note that all
characters after a "_" in the chart name can only be digits.
● Then click on OK, the window closes and the DCC Editor is automatically opened with
the plan. For this to happen, the Option Editor must be set to remain open automatically
(bottom left above the OK button).
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 asked to import a DCB library.
● In the Import DCB libraries window, highlight the DCB library in the "Existing libraries"
column on the left. Click on the >> button to move the library into the "Imported libraries"
column on the right.
● Close the window by clicking on Accept. The DCB library is loaded and the DCC Editor
opened with the chart.
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.
● Select the required block and insert it in the chart using drag-and-drop. The outline of the
block is represented by a dashed line. Release the mouse button at the required point.
The block (actual size) is displayed on the chart.
● To search for a block, enter its name in the input field of the block catalog and click the
magnifying glass icon. The search process begins. Once the block has been found, insert
it in an empty space on the chart using drag-and-drop.
● Drag the two integrators (INT) and one subtractor (SUB) needed for the example into the
chart.
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 block information can be viewed.
The names of the block families are not available in languages other than English.
Procedure
● Select the Y output of the left-hand INTegrator, followed by the X input of the right-hand
INTegrator.
● Select the Y output of the right-hand INTegrator, followed by the X2 input of the
SUBtractor.
● Select the Y output of the SUBtractor, followed by the X input of the left-hand INTegrator.
The autorouter creates the connecting lines from the outputs to the inputs and they are then
interconnected.
Figure 3-11 Chart "dccReg1" with interconnected DCBs. Some connections have been assigned initial values that differ
from the factory setting.
Figure 3-13 View from the expert list with the parameters defined in the DCC chart
Compiling
You can begin compiling from the DCC Editor with Chart > Compile > Charts as program...
or via the icon.
You can also start the process of compiling and saving a chart from the STARTER by
clicking on the icon.
Compilation options
For detailed information about the compilation options, please see the Section Compiling
(Page 25).
Note
The Redeclare parameter interface option enables you to reassign the addresses for all
BICO parameters currently defined in the chart. BICO parameters 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.
● If error messages are displayed: To access the relevant DCB 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.
You can return to the DCC chart by again selecting Edit > Execution sequence or by again
clicking on .
3.2.11 Loading the DCC technology option onto the CF card of the drive device
When the drive device is supplied, the DCC technology option will not yet be present on the
CF card of the drive unit. This is loaded onto the CF card with the aid of SIMOTION SCOUT
or SINAMICS STARTER.
To do this, call e.g. the STARTER and link to the drive device online. STARTER is in online
mode.
In the drive device's context menu, then select the Select technology packages... item.
In the Select technology packages window, select the DCB library you want and select
Download for this library in the action column. Then click on Run 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.
The window is closed by double-clicking on OK.
NOTICE
Once the technology package has been downloaded, the drive device has to be switched
off and on again once. Only once the supply voltage to the CU3xx and/or D4xx has been
switched back on and it has been powered up can DCC charts be downloaded to the drive
device and run.
do this, highlight the drive device in the project navigator and call Properties from the context
menu. The bus address specified in the SINAMICS properties window in the Drive
device/bus address tab must match the value previously established from diagnostics. If
necessary, set the bus address to the value found and close the window by clicking on OK.
Again try to go online.
If the connection has been successful, click on the Download button in the Online/offline
comparison window.
Downloading can take place in STARTER at any time via the Download function.
Once the download is complete, the DCC chart is calculated in cycles on the CU drive
object.
To make the oscillator vibrate, it must be excited once. To do this, set the p20501 parameter
in the expert list of the STARTER once to "1" (the set value SV = 2.0 is located at the output
of the left-hand integrator, r20519 = 2.0) 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
(r20519, r20520).
If you want to make further changes to the chart, you must leave the test mode with Test >
Test mode or by clicking the button. It can take several tens of seconds before the test
mode of the DCC editor is exited.
3.2.14 Record with the trace signals from the DCC chart
The integrator outputs declared as interconnectable parameters act like any other REAL
connector output of the SINAMICS base unit. This means these signals can also be
recorded with the trace. The trace is called in STARTER with Target system > Trace or .
In this example, the r20519 and r20520 parameters (i.e. the outputs of the two integrators in
the DCC chart) will be recorded with a cycle of 1 ms. The recording can be started with the
button.
Complete documentation
The example has been successfully configured and tested. You can now create the
complete documentation for this short example.
Execution editor
The execution editor displays the execution groups with the block types and the execution
sequence. In the function bar of the function bar of the DCC editor, click: and open the
execution editor. Open the chart and the execution group in the middle column. Double-click
on one of the DCBs (yellow). The DCBs of the execution group in the sequence of the call
are listed in the right-hand window. To begin printing, click:
Printing a chart
You should also print the chart to document the interconnection of the DCBs. 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 DCBs are shown on a single page on the
PC monitor.
The change of the hardware sampling times r21002 base sampling time displays the value
for p0115[0] in the CU startup 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.
The current output value (= per-unit speed setpoint = 1500 rpm / 3000 rpm = 0.5) is then
displayed.
The DCB 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.
3.3.3 Interconnecting DCC signals with communication interfaces IF1 and IF2
The basic system can be connected to process data interfaces IF1 and IF2 via free telegram
configuration using BICO (p0922 = 999) or via (standard) telegrams depending on p0922. To
interconnect with the basic system, the DCC connections needed must be published as
BICO parameters. These DCC parameters should always be interconnected with the basic
system in the DCC Editor by calling the context menu Interconnection to operand.
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
One or more tasks are available in each execution level for user programming.
The main features of the tasks are:
● Start behavior: When and under what conditions a task is started?
● Priority: Which task is interrupted by which other task?
Execution groups
The available tasks (scan and order of sequence in the system: T1 to T5) are arranged in
run-time groups. The blocks are embedded into these run-time groups. The run-time groups
therefore allow the task to be structured or divided as required by the user; e.g. dancer
control, setpoint processing, etc. The run-time groups are embedded sequentially into the
blocks. Only blocks from one basic chart may be included in within a run-time group.
You can use the "Enable" attribute to activate and deactivate an execution group. In the
normal case, run-time groups are processed in cycles; however, the enable attribute can be
used for switching single run-time groups on and off.
A BOOL-type block output can be connected to enable a run-time 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
Where tasks are concerned, The "run sequence" corresponds to the sequence in which run-
time groups and blocks are integrated within a task.
The same applies to groups: The sequence in which the individual blocks are integrated is
the run sequence within the run-time group.
You can change the execution sequence.
HMI variables
You can declare block inputs and outputs as HMI variables. It is also possible to implement
an interface that 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
@parameter (SIMOTION)
Block inputs and outputs can be declared. The variables/parameters declared by the user
are expanded in the map listing. Declaration allows you to to create an interface that is as
static as possible. Consequently, a change to the DCC configuration does not necessitate
reimporting of the address information for the HMI system.
Structure of @parameters
In the comment, block inputs and outputs are declared by the variable name preceded by @.
Comment Meaning
SIMOTION: The connection is entered as an HMI variable in
@name <<parameter comment>> SIMOTION. The name is inserted before the first
space (here, you must adhere to ST
conventions).
The text which follows the variable name (separated by a space), is transferred as a
parameter comment. It is then displayed in the SIMOTION STARTER expert list, for
example. The parameter identifier results from the variable name.
The data type of the declared input/output is transferred 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 @parameters.
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.
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 drive 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 by variable name, parameter number or parameter text (with DCC-
SINAMICS) in the search box in the Icon input aid 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.
3. Select the array variable to be interconnected.
4. Enter the number of the array element to be interconnected.
5. Click OK to close the window.
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 parameters. 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 on 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. Enter the alias name in the entry field.
5. Close the window.
The alias has been successfully created and can now be used - the computer now resolves
the alias as required, e.g. within the framework of the compilation.
4.1.4.1 Fundamentals
The DCC editor offers a function for saving a chart as a block 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 function therefore includes the
option of know-how protection, since the configured DCC charts are only available as a
transparent block within a block library. The DCC chart configuration that has been created
is hidden. The DCC chart that has been created for a block can be definitively deleted via the
Remove chart source... function 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.
Prerequisites
You have already created a new DCC library in the SIMOTION SCOUT Engineering System.
There is already a DCC chart available for saving in the block library.
The chart connections are displayed.
Note
You can display the chart connections via the icon in the toolbar.
Procedure
In the project, first click Insert DCC library in the project navigation tree to create a new
library.
Following this, click Insert DCC chart to create a new DCC chart for the library. You can then
model the DCC chart in the DCC editor.
Insert e.g. an ADDer and a PI controller (PIC) in the chart and interconnect them.
The block connections can be interlinked to the chart connections in two ways.
The first way is to select the interface type (IN, OUT, IN_OUT) from the left pane and then
drag the block connection you want into the right pane using drag & drop.
The second way is to press and hold down the Ctrl key and drag the block connection to be
interconnected to the interface type required directly into the left pane using drag & drop.
Each 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.
Following successful configuration, the DCC chart can be compiled as a block type. To do
this, select Chart > Compile > Chart as block type. A new block with the defined inputs and
outputs will now be created in the selected block library.
The newly created library is available in the menu under Extras > block types in the DCC
Editor. The library is not shown in the SIMOTION SCOUT; only native libraries are shown
there.
4.1.4.2 Creating comments for block libraries you have created yourself
In the SIMOTION SCOUT engineering system, you can save additional information on
individual blocks for a block 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 block library, select the Block type properties item.
3. In the Block type properties window, select the DCC chart to be edited and click on the
Extra block type properties button.
4. Now enter the information you require and then close the window with OK.
Figure 4-8 Connection example for a 1:N interconnection without NOP block
Figure 4-9 Connection example for a 1:N interconnection with NOP block
Note
Before copying into the SIMOTION SCOUT target instance, you must activate the
technology packages needed if no corresponding chart has yet been produced.
Procedure
In the DCC chart, highlight the block connection whose interconnection you wish to
disconnect. Then select Edit > Delete to delete it.
Result
The connecting line between the connections disappears and the last value that was
transferred to the connection appears as a parameter value at the connection.
Note
It is now no longer possible to recreate or delete connections to global operands online.
Procedure
In the DCC chart, highlight the block connection from which you want to establish a
connection.
Result
The connecting line between the selected connections is established and the current
parameter value that has been transferred appears at the output.
Procedure
Double-click to select the block input whose parameter value is to be changed. The
Connection Properties dialog box appears. You can change the value here.
Result
The effect of the change can immediately be seen in the DCC chart.
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.
Note
Not all blocks can be inserted online. This depends on the total system behavior, for
example, is a save request only possible during ramp-up.
Further information is available under "Configuration data" in the online help for the block.
Procedure
Select the block and use the Edit > Delete command to remove it.
Preliminary remarks
Before we go any further, the intention here is to provide 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:
● 2 integrators (INT)
● 1 subtractor (SUB)
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. The outline of the
block is represented by a dashed line. Release the mouse button at the required point.
The block (actual size) is displayed on the chart.
● To search for a block, enter its name in the input field of the block catalog and click the
magnifying glass icon. 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 left-hand INTegrator, followed by the X input of the right-hand
INTegrator.
● Select the Y output of the right-hand INTegrator, followed by the X2 input of the
SUBtractor.
● Select the Y output of the SUBtractor, followed by the X input of the left-hand INTegrator.
The autorouter creates the connecting lines from the outputs to the inputs and they are then
interconnected.
Compiling
You can begin compiling with Chart > Compile > Charts as program... or via the icon.
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 the selected device in the engineering system using the Select technology
packages function, which enables you to see whether all necessary block libraries and
technology packages are activated. The basic DCBADM package must always be activated,
the dcblib technology package must be activated if you are using the blocks of the standard
library.
Compilation options
For detailed information about the compilation options, please see the chapter titled
"Compiling".
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.
When the project is downloaded, the DCBs are active immediately if the CPU is in RUN.
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.
All input and output values that have been activated for monitoring purposes are updated in
accordance with the set monitoring cycle.
Complete documentation
The example has been successfully configured and tested. You can now create the
complete documentation for this short 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 wish to print out 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:
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 interface variable:
– 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 108)
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)
See also
● Interconnection of global operands (Page 23)
4.3.5 Data type abbreviation in the DCC for connection and transformer blocks
Abbreviation Description
DCB Drive Control Block
DCC Drive Control Chart
DO Drive Object / Antriebsobjekt
@ C
@parameters, 86
Changing parameters online, 95
Chart as block type, 90
Dependencies, 94
A
Multiple interconnection, 93
Abbreviations of the data types, 111 Chart partition, 16
Alias identifier, 89 Chart reference data
Array and name lengths, 109 Cross References Block Types, 33
SIMOTION, 109 Cross References Execution Groups, 33
Cross References Operands, 33
Comment
B Block type, 19
Compiling, 26
Basic chart, 16
Configuration example
Block
SIMOTION, 97
Block I/O units, 24
Configuring the block display, 22
Configuring the display, 22
Connection
Connection properties, 23
Declaring, 50
Delete, 23
Create new device, 14
Deleting online, 96
Creates a new project, 13
Execution properties, 22
Cyclic part
Execution sequence, 22
Startup behavior, 37
Generic blocks, 24
Hidden connections, 24
Inserting online, 96
D
Interconnect, 22
Pseudo comment, 24 Data types
superimposition, 21 Abbreviations, 111
Block catalog, 18, 21 DCB library
Find, 21 Change, 28
Magnifying glass, 21 DCC chart
New text, 18 Changing parameters online, 95
Block help, 12 Compiling, 26
Block library Consistency Check, 25
Changing the language, 19 Copy, 29
Delete, 19 Copying block groups, 29
Import, 17 Deleting a block online, 96
R Trace, 96
Trend display, 30
References, 3
Typical, 90
Representation of the dynamic value display, 110
Dependencies, 94
Rules for assigning names
Multiple interconnection, 93
Basic chart (SIMOTION), 108
Rules of creation, 91
Block instance (SIMOTION), 108
Chart interface variables (SIMOTION), 108
Execution group (SIMOTION), 108
V
SIMOTION, 108
Subchart (SIMOTION), 108 Value display, 30
Run-time group, 84
S
Set system cycle clock, 85
SIMOTION
Configuration example, 97
SIMOTION SCOUT
Adding a Device, 14
Copy DCC chart, 29
Create a project, 13
Inserting a DCC chart, 14
Know-how Protection, 35
Selecting Technology Packages, 26
SIMOTION trace, 96
Software requirements, 83
Starting procedure
Init, 37
Start-up, 37
Start-up, 37
Startup behavior, 37
Cyclic part, 37
Init, 37
Initialization, 37
Start-up, 37
Subchart, 16
T
Task, 84
Test mode, 30
Laboratory mode, 32
Log on connection, 31
Monitoring, 31
Monitoring cycle, 32
Operating Modes, 32
Process mode, 32
Switching off, 31
Switching on, 30
Trend display, 30
Value display, 30