D7sys Option e

s
Foreword, Contents
Basic software
1
CFC
SIMATIC D7-SYS 2
SFC
3
D7-SYS - STEP 7, CFC Index
and SFC configuring
Manual
01/2008
A5E01078201-02
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 to property damage only have no safety alert symbol. The
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.
Attention
indicates that an unintended result or situation can occur if the corresponding notice 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
awarning 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 notices 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 and its components 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.
이 기기는 업무용(A급) 전자파 적합기기로서 판매자 또는 사용자는 이 점을 주의하시기 바라며 가정 외의 지역에서 사용하는 것을 목적으로 합니다.
Copyright Siemens AG 2008 All rights reserved Disclaimer of Liability

The distribution and duplication of this document or the We have reviewed the contents of this publication to ensure consistency
utilization and transmission of its contents are not permitted with the hardware and software described. Since variance cannot be
without express written permission. Offenders will be liable for precluded entirely, we cannot guarantee full consistency. However, the
damages. All rights, including rights created by patent grant information in this publication is reviewed regularly and any necessary
or registration of a utility model or design, are reserved corrections are included in subsequent editions.
Siemens AG
Automation and Drives
Geschäftsgebiet Industrial Automation Systems Siemens AG 2008
Postfach 4848, D- 90327 Nürnberg Technical data subject to change.
Siemens Aktiengesellschaft A5E01078201-02

Foreword
Purpose of this Manual

This Manual explains the principle use and functions of the D7-SYS automation
software with the main focus on the appropriate technological and drive control
components SIMATIC TDC, FM 458-1 DP, T400, SIMADYN D.
TDC: Technology and Drives Control
Basic knowledge required

This Manual addresses programmers and commissioning engineers. General
knowhow regarding automation technology is required in order to understand the
contents of the Manual.
Validity of the Manual

This Manual is valid for SIMATIC D7-SYS Version 7.0.
D7-SYS - STEP 7, CFC and SFC configuring - SIMATIC D7-SYS

A5E01078201-02 - Edition 01.2008 iii
Foreword
Information overview
This manual is part of the overall documentation for the technological and drive
control components T400, FM 458, SIMADYN D, SIMATIC TDC and SIMATIC D7-
SYS.
Titel Inhalt
System and The first project in a few steps
communications This Section provides an extremely simple entry into the methodology when
configuring D7-SYS assembling and programming the SIMATIC TDC/SIMADYN D control system. It
is especially conceived for first-time users of a control system.
System software
This Section provides basic know-how about the structure of the operating
system and an application program of a CPU. It should be used to obtain an
overview of the programming methodology, and basis for configuring user
programs.
Communications configuring
This section provides you with basic know-how about the communication
possibilities and how you configure links to the communication partners.
Changeover from STRUC V4.x to D7-SYS
Essential features are included in this section, which have changed over
STRUC V4.x with the introduction of SIMATIC D7-SYS.
D7-SYS - STEP 7, Basis software
CFC and SFC This section explains the essential use and the functions of the STEP 7
configuring automation software. For first users, it provides an overview on configuring,
programming and commissioning a station.
When working with the basis software, you can access the online help which
provides you with support when it comes to detailed questions on using the
software.
CFC
The CFC language (Continuous Function Chart) allows you to graphically
interconnect blocks.
When working with the particular software, you can also use the online help
which can answer detailed questions regarding the use of the editors/compiler.
SFC
Configuring sequence controls using SFC (Sequential Function Chart) of
SIMATIC S7.
In the SFC editor, you generate a sequence chart using graphic resources. The
SFC elements of the chart are then positioned according to specific rules.
Hardware The complete hardware spectrum is described as reference in this Manuals.

iv A5E01078201-02 - Edition 01.2008
Foreword
Titel Inhalt
Selecting Function The Reference Manual provides you with an overview of all of the function
blocks blocks for the corresponding technology and drive control components -
SIMATIC TDC, FM 458-1 DP, SIMADYN D and T400.
Chapter 1
The function blocks that can be configured in all target systems of SIMATIC
D7-SYS are described in this Chapter.
Chapter 2
The function blocks that can only be configured for SIMATIC TDC are
described in this Chapter.
Chapter 3
The function blocks that can only only be configured for FM 458-1 DP
application module are described in this Chapter.
Chapter 4
The function blocks that can only be configured for SIMADYN D and T400 are
described in this Chapter.
Guide
As first time user, we recommend that this Manual is used as follows:
• Please read the first section on using the software in order to get to know some
of the terminology and basic procedure.
• Then use the particular sections of the Manual if you wish to carry-out certain
processing steps (e.g. loading programs).
If you have already executed a small project, and have gained some experience,
then you can read individual sections of the Manual in order to get up to speed
about a specific subject.
Special Notes
This user part of the Manual does not include any detailed information/instructions
with individual descriptions, but is only intended to provide a basic procedure. More
detailed information on the dialog boxes in the software and how they are handled
is provided in the appropriate online help.
Additional support
If you have questions relating to the use of the products described in the Manual,
which cannot be answered here, then please contact your local Siemens office.
You can also call the Hotline:
Tel.: +49 (180) 5050-222
Fax: +49 (180) 5050-223
E-Mail: adsupport@siemens.com
1

A5E01078201-02 - Edition 01.2008 v
Foreword
Training Center
Appropriate training courses are available in order to make it easier to get to know
the SIMADYN D automation system. Please contact the central Training Center in
D-Erlangen (I&S IS INA TC):
Tel.: +49 (9131) 7-27689, -27972
Fax: +49 (9131) 7-28172
Internet: www.siemens.de/sitrain
Intranet: http://info-tc.erlm.siemens.de/
Service & support in Internet

Can be accessed globally at any time of the day:
World-wide (Nürnberg)
Technical Support
Ortszeit: 0:00 bis 24:00 / 365 Tage
Telefon: +49 (180) 5050-222
Fax: +49 (180) 5050-223
E-Mail: adsupport@siemens.com
GMT: +1:00
Europa / Afrika (Nürnberg) United States (Johnson City) Asien / Australien (Peking)
Authorization Technical Support and Technical Support and
Authorization Authorization
Ortszeit: Mo.-Fr. 8:00 bis 17:00 Ortszeit: Mo.-Fr. 8:00 bis 17:00 Ortszeit: Mo.-Fr. 8:00 bis 17:00
Telefon: +49 (180) 5050-222 Telefon: +1 (423) 262 2522 Telefon: +86 10 64 75 75 75
Fax: 49 (180) 5050-223 Fax: +1 (423) 262 2289 Fax: +86 10 64 74 74 74
E-Mail: adsupport@siemens.com E-Mail: simatic.hotline@sea.siemens.com E-Mail: adsupport.asia@siemens.com
GMT: +1:00 GMT: -5:00 GMT: +8:00
Technical Support and Authorization speak generally German and English.

vi A5E01078201-02 - Edition 01.2008
Contents
Foreword ........................................................................................................................................ iii
1 Basic software........................................................................................................................ 1-1

1.1 Installation and start.................................................................................................. 1-2
1.1.1 System requirements ................................................................................................ 1-2
1.1.2 Installing the software ............................................................................................... 1-3
1.1.2.1 Installing from CD-ROM............................................................................................ 1-3
1.1.3 Start........................................................................................................................... 1-4
1.2 User interface............................................................................................................ 1-6
1.2.1 Starting the STEP 7 software ................................................................................... 1-6
1.2.2 User interface: Window............................................................................................. 1-7
1.2.3 User interface: Dialog boxes..................................................................................... 1-8
1.2.4 Calling-up the help functions .................................................................................... 1-9
1.2.5 Saving and restoring the window layout ................................................................. 1-10
1.3 STEP 7 projects and basic handling....................................................................... 1-11
1.3.1 Opening a project example..................................................................................... 1-11
1.3.2 Components to configure the hardware ................................................................. 1-13
1.3.3 Components to generate software ......................................................................... 1-13
1.3.4 Operator handling philosophy................................................................................. 1-14
1.3.5 Creating and manipulating objects ......................................................................... 1-15
1.3.6 Selecting objects in the dialog box ......................................................................... 1-17
1.4 Creating and handling projects ............................................................................... 1-18
1.4.1 Creating projects..................................................................................................... 1-18
1.4.2 Inserting and configuring stations ........................................................................... 1-19
1.4.3 Programs with and without assigned hardware...................................................... 1-20
1.4.4 Generating software without configured hardware................................................. 1-21
1.4.5 Principle procedure when generating software ...................................................... 1-22
1.4.6 Saving projects ....................................................................................................... 1-22
1.5 Configuring and parameterizing modules............................................................... 1-24
1.5.1 Creating a configuration.......................................................................................... 1-24
1.5.2 General handling..................................................................................................... 1-25
1.5.3 Example .................................................................................................................. 1-27
1.5.4 Arranging modules.................................................................................................. 1-27
1.5.5 Parameterizing modules ......................................................................................... 1-28
1.5.6 Linking-in hardware signals to the user program ................................................... 1-29
1.5.7 Consistency check, saving and loading.................................................................. 1-29
D7-SYS - STEP 7, CFC and SFC configuring - SIMATIC D7-SYS vii

A5E01078201-02 - Edition 01.2008
Contents
1.5.8 Working in the configuration table .......................................................................... 1-30

1.5.9 Configuring PROFIBUS DP .................................................................................... 1-30
1.6 Creating communication connections..................................................................... 1-31
1.6.1 Communications within a station ............................................................................ 1-31
1.6.1.1 Communications via $ signals ................................................................................ 1-31
1.6.1.2 Communications via virtual connections................................................................. 1-33
1.6.2 Communications with display units......................................................................... 1-34
1.7 Loading programs ................................................................................................... 1-35
1.7.1 Online loading .........................................................................................................1-35
1.7.1.1 Selecting the interface for the online connection .................................................... 1-35
1.7.1.2 Online loading into a CPU....................................................................................... 1-36
1.7.2 Offline loading ......................................................................................................... 1-37
1.7.2.1 What you need to know about memory modules and the programming interface . 1-37
1.7.2.2 Selecting the loading interface................................................................................ 1-37
1.7.2.3 Offline loading into a memory module .................................................................... 1-38
1.8 Testing programs .................................................................................................... 1-39
1.8.1 Testing programs .................................................................................................... 1-39
1.9 Diagnostics.............................................................................................................. 1-41
1.9.1 Diagnostics in the SIMATIC Manager in the offline project view ............................ 1-42
1.9.1.1 Transferring diagnostics information....................................................................... 1-43
1.9.1.2 Steps to call-up the module information from the SIMATIC Manager .................... 1-44
1.9.1.3 Evaluating the diagnostics buffer of the diagnostics............................................... 1-44
1.9.2 Diagnostics in the CFC ........................................................................................... 1-45
1.9.2.1 Steps to call-up the module status from the CFC ................................................... 1-45
1.9.2.2 Displaying and changing the operating mode ........................................................ 1-46
1.10 Archiving user programs ......................................................................................... 1-47
1.10.1 Archive programs .................................................................................................... 1-47
1.10.2 Archiving projects.................................................................................................... 1-48
1.10.3 De-archiving projects .............................................................................................. 1-49
1.11 Printing .................................................................................................................... 1-50
1.11.1 Setting-up the printer .............................................................................................. 1-50
1.11.2 Starting to print........................................................................................................ 1-50
2 CFC.........................................................................................................................................2-1
2.1 Working with the CFC editor ..................................................................................... 2-2
2.1.1 CFC in the STEP 7 environment............................................................................... 2-2
2.1.1.1 Software requirements.............................................................................................. 2-2
2.1.1.2 Project planning data flow......................................................................................... 2-4
2.1.2 Handling block types................................................................................................. 2-5
2.1.2.1 Importing SIMADYN D block libraries....................................................................... 2-5
2.1.2.2 Inserting block types ................................................................................................. 2-6
2.1.2.3 Deleting block libraries.............................................................................................. 2-6
2.1.2.4 Updating SIMADYN D block libraries ....................................................................... 2-7
2.1.3 Editing block inputs ................................................................................................... 2-8
2.1.3.1 Additional properties of the block I/Os ...................................................................... 2-8
2.1.3.2 Inverting inputs.......................................................................................................... 2-8
2.1.3.3 The GLOBAL data type............................................................................................. 2-9
viii D7-SYS - STEP 7, CFC and SFC configuring - SIMATIC D7-SYS

A5E01078201-02 - Edition 01.2008
Contents
2.1.4 Block interconnections.............................................................................................. 2-9

2.1.4.1 Interconnecting to global operands .......................................................................... 2-9
2.1.4.1.1 $ signals.................................................................................................................. 2-10
2.1.4.1.2 Virtual connections.................................................................................................. 2-11
2.1.4.1.3 Virtual connection names ....................................................................................... 2-11
2.1.4.1.4 OP connections....................................................................................................... 2-12
2.1.4.1.5 Hardware addresses............................................................................................... 2-12
2.1.4.1.6 Module names ........................................................................................................ 2-12
2.1.4.1.7 Name references .................................................................................................... 2-13
2.1.4.1.8 Process interrupts ................................................................................................... 2-13
2.1.5 Run-time properties ................................................................................................ 2-13
2.1.5.1 Tasks and run-time groups ..................................................................................... 2-13
2.1.5.2 Run-time attributes.................................................................................................. 2-14
2.1.6 Operator control and monitoring ............................................................................. 2-15
2.1.6.1 Configuring operator control and monitoring attributes .......................................... 2-16
2.1.7 Compiling and loading ............................................................................................ 2-16
2.1.7.1 Compiling the user program ................................................................................... 2-17
2.1.7.2 Loading the user program....................................................................................... 2-19
2.2 Brief guide............................................................................................................... 2-23
2.2.1 The first steps ......................................................................................................... 2-23
2.2.2 Creating a project.................................................................................................... 2-24
2.2.3 Starting CFC and inserting blocks .......................................................................... 2-26
2.2.4 Interconnecting blocks ............................................................................................ 2-28
2.2.5 Editing blocks.......................................................................................................... 2-28
2.2.6 Compiling and loading into the target system......................................................... 2-30
2.2.7 Monitoring and changing in the test mode.............................................................. 2-31
2.2.8 Generating documentation and closing project ...................................................... 2-32
2.3 Testing and commissioning .................................................................................... 2-34
2.3.1 Viewing and changing the operating mode ............................................................ 2-35
2.3.2 Checking that the configured data and the CPU program match........................... 2-37
2.3.3 Changing the refresh rate for monitoring................................................................ 2-37
2.3.4 Activating and de-activating the test mode............................................................. 2-38
2.3.5 Module status.......................................................................................................... 2-40
2.3.6 Monitoring block I/O ................................................................................................ 2-41
2.3.7 Parameterizing block I/O ........................................................................................ 2-43
2.3.8 Creating and deleting interconnections .................................................................. 2-44
2.3.9 Inserting and deleting blocks .................................................................................. 2-45
2.3.10 Communication interfaces ...................................................................................... 2-46
2.4 Creating block types ............................................................................................... 2-49
2.4.1 Creating a user library from charts ......................................................................... 2-49
2.5 Archiving projects on the MC - saving and retrieving ............................................. 2-52
2.5.1 Saving a project to be archived on MC................................................................... 2-52
2.5.1.1 Prerequisites for saving a project ........................................................................... 2-53
2.5.1.2 Procedure when saving .......................................................................................... 2-54
2.5.2 Retrieving an archived project from the MC ........................................................... 2-58
2.5.2.1 Prerequisites for retrieving a project....................................................................... 2-58
2.5.2.2 Procedure when retrieving...................................................................................... 2-58
D7-SYS - STEP 7, CFC and SFC configuring - SIMATIC D7-SYS ix

A5E01078201-02 - Edition 01.2008
Contents
2.6 Chart reference data-documentation ...................................................................... 2-61

2.6.1 Chart reference data ............................................................................................... 2-61
2.6.1.1 "Cross reference operands" list .............................................................................. 2-61
2.6.1.2 "Cross-reference run-time groups" list.................................................................... 2-63
2.6.1.3 "Cross-references block types" list ......................................................................... 2-63
2.7 Technical data......................................................................................................... 2-64
2.7.1 Field/name lengths and conventions ...................................................................... 2-64
2.7.2 Data types ............................................................................................................... 2-65
2.7.3 Abbreviations .......................................................................................................... 2-65
3 SFC..........................................................................................................................................3-1
3.1 Basics of the SFC ..................................................................................................... 3-3
3.1.1 SFC in the STEP 7 environment [SD]....................................................................... 3-3
3.1.2 SFC and technology hierarchy [SD] ......................................................................... 3-3
3.1.3 Setting-up the project structure [SD]......................................................................... 3-3
3.1.4 SFC-Elements........................................................................................................... 3-3
3.1.4.1 What are chart elements? [SD]................................................................................. 3-3
3.2 Tips & Tricks ............................................................................................................. 3-4
3.2.1 Generate reference data [SD]................................................................................... 3-4
3.2.2 Configuring SFC calls [SD] ....................................................................................... 3-4
3.3 Creating Sequential Control Systems (SFC Editor).................................................. 3-6
3.3.1 Working with Charts.................................................................................................. 3-6
3.3.1.1 Copying charts [SD] .................................................................................................. 3-6
3.3.2 Configuring Sequential Control Systems .................................................................. 3-6
3.3.2.1 Creating a jump [SD]................................................................................................. 3-6
3.3.2.2 Step: Editing addresses [SD] .................................................................................... 3-6
3.3.2.3 Transition: Editing addresses [SD] ........................................................................... 3-8
3.3.3 Shared Adresses and Permitted Data Types ........................................................... 3-9
3.3.3.1 Global addresses (operands) [SD] ........................................................................... 3-9
3.3.3.2 Absolute addressing [SD] ......................................................................................... 3-9
3.3.3.3 Symbolic addressing [SD]......................................................................................... 3-9
3.3.3.4 Permissible data types [SD]...................................................................................... 3-9
3.3.4 The Run-Time Properties........................................................................................ 3-10
3.3.4.1 Overview of the run-time properties [SD]................................................................ 3-10
3.3.4.2 Specifying the run sequence [SD] .......................................................................... 3-10
3.3.4.3 Installing an SFC chart in a task / deleting from a task [SD] .................................. 3-10
3.3.4.4 Run-time attributes for the run-time group and SFC chart [SD] ............................. 3-11
3.3.5 Configuruing Messages .......................................................................................... 3-12
3.3.5.1 How SFC works with messages [SD] ..................................................................... 3-12
3.3.6 Compiling Charts .................................................................................................... 3-12
3.3.6.1 Customizing the compiler [SD]................................................................................ 3-12
3.3.6.2 Compilation procedure [SD].................................................................................... 3-13
3.3.6.3 Consistency check [SD] .......................................................................................... 3-13
3.3.7 Downloading User Programs .................................................................................. 3-14
3.3.7.1 Downloading programs [SD] ................................................................................... 3-14
3.4 Sequential control systems on the PLC.................................................................. 3-16
3.4.1 Overview of sequential control systems on the PLC [SD] ...................................... 3-16
x D7-SYS - STEP 7, CFC and SFC configuring - SIMATIC D7-SYS

A5E01078201-02 - Edition 01.2008
Contents
3.4.2 How a chart is executed [SD] ................................................................................. 3-16

3.4.3 The operating modes [SD]...................................................................................... 3-16
3.4.4 Chart execution options [SD] .................................................................................. 3-16
3.4.5 Behavior of a sequential control system [SD]......................................................... 3-17
3.4.6 The operating states [SD] ....................................................................................... 3-18
3.4.7 The commands [SD] ............................................................................................... 3-18
3.4.8 SFC Elements of the PLC....................................................................................... 3-19
3.4.8.1 Phases of a step [SD] ............................................................................................. 3-19
3.4.8.2 Processing steps and transitions [SD].................................................................... 3-19
3.5 Using the Control Block .......................................................................................... 3-20
3.5.1 The control block [SD] ............................................................................................ 3-20
3.5.2 Inputs of the control block [SD]............................................................................... 3-20
3.5.3 Outputs of the control block [SD] ............................................................................ 3-20
3.6 Documenting Programs .......................................................................................... 3-20
3.6.1 Logs [SD] ................................................................................................................ 3-20
Index .............................................................................................................................................. I-1
D7-SYS - STEP 7, CFC and SFC configuring - SIMATIC D7-SYS xi

A5E01078201-02 - Edition 01.2008
1 Basic software
Overview 1.1 Installation and start 1-2
1.2 User interface 1-6
1.3 STEP 7 projects and basic handling 1-11
1.4 Creating and handling projects 1-18
1.5 Configuring and parameterizing modules 1-24
1.6 Creating communication connections 1-31
1.7 Loading programs 1-35
1.8 Testing programs 1-39
1.9 Diagnostics 1-41
1.10 Archiving user programs 1-47
1.11 Printing 1-50
D7-SYS - STEP 7, CFC and SFC configuring - SIMATIC D7-SYS 1-1

A5E01078201-02 - Edition 01.2008
Basic software
1.1 Installation and start
Overview This Section will show you how to install the software of the D7-SYS
option package using a setup program. Installation is menu-prompted.
Call-up the setup program with the standard procedure, generally used
under Windows to install software.
1.1.1 System requirements
Hardware platform You require as a minimum, the following platform in order to be able to
use this software:
• SIMATIC PG or PC with
− Pentium P133 processor (or higher) and
− RAM memory expansion ≥ 64 MByte (we recommend 128 MByte)
• Color monitor, keyboard and mouse, which are supported by Microsoft

Windows.
− Recommended screen resolution: 1024 x 768 (or higher)
• 190 MByte free memory space on the hard disk, on which the STEP 7
basis software was installed (in addition to the memory space
requirement for STEP 7 basis software and CFC).
• Minimum 1 MB free memory on drive C for setup (setup files are

deleted after installation has been completed).
• Hard disk memory size for the Windows swap file (at least 256 Mbytes
minus the size of your PC´s RAM).
• Free memory space on the hard disk for your project data.
• For offline loading of the compiled programs in the memory modules

for CPUs (optional):
− Plug-in PC card (PCMCIA).

In many notebooks and SIMATIC PGs this is already permanently
installed. Appropriate boards can be retrofitted in desktop- or tower
PCs (refer to the ”Readme” file)or
− External OmniDrive Professional device (refer to the “readme file”)

or
− Device to program Micro Memory Cards (MMC); appropriate slot in

SIMATIC PGs (e.g. Field PG) or an external USB prommer (refer
to the “readme file”).
• For online loading in CPUs and for testing (optional):
− An MPI interface between SIMATIC PG or PC and the station, i. e.

either a PC/MPI cable or an MPI module, which is installed in your
unit. This MPI interface is already integrated in several Siemens
programmers.
1-2 D7-SYS - STEP 7, CFC and SFC configuring - SIMATIC D7-SYS

A5E01078201-02 - Edition 01.2008
Basic software
You will require the following software:

Software platform
• Operating system:
• Basic STEP 7 software,
• CFC option package,
• Possibly option package SFC,
1.1.2 Installing the software
Overview The supplied software includes a setup program, which automatically

installs the software. You are prompted on the screen at each individual
installation step.
Prerequisites Before installing D7-SYS, ensure that Windows and STEP 7 and CFC are
already installed.
If required, install these products in the following sequence:
1. Windows
for permissible Windows-version refer to current “readme”-file.
2. Basic STEP 7 software

for needed version refer to current “readme”-file.
3. CFC option package

4. Possible SFC option package

Installing/de- A detailed description for installing and de-installing STEP 7 and CFC is
installing STEP7- provided in the product information which is supplied with the software
and CFC software products.
NOTE It is not possible to install several versions of STEP 7 and its option
packages in parallel.
1.1.2.1 Installing from CD-ROM
When installing from a CD-ROM, proceed as follows:
1. Insert the CD-ROM in your PC.
2. Start the "Setup" program of the CD-ROM.
3. The setup program then prompts you at all of the other steps .

A5E01078201-02 - Edition 01.2008
Basic software
Please observe the information and instructions in the "Readme" file

Readme
which is opened when installation is beginning.
Authorization The D7-SYS option package does not require any additional
authorization.
De-installation If you no longer require the D7-SYS software product, or you wish to
install a new version, then you can de-install it from your PC.
1. To de-install, call-up the application start > settings > Control Panel
> software from the start menu of Windows 95/NT.
2. Select "SIMATIC D7-SYS" from the list of installed products.
3. Click on the button "Add/remove", in order to de-install D7-SYS.
1.1.3 Start
Overview After you have installed D7-SYS, you can use the following STEP 7 tools:
• SIMATIC Manager
• HWConfig
• CFC
• SFC (if the option package is installed)
• DOCPRO (if the option package is installed)
SIMATIC Manager After Windows has been started, you will see a symbol for the SIMATIC
Manager on the Windows screen, the entry into the STEP 7 software.
Open the SIMATIC Manager window by double-clicking on the icon. You

can set-up new projects and process existing projects in the SIMATIC
Manager.
The most important information for handling the SIMATIC Manager is

provided in the online help, which you can call-up via the "Help" menu.
Please refer to the of this online help for the most important information
which you require when configuring with D7-SYS.

A5E01078201-02 - Edition 01.2008
Basic software
The most important STEP 7 applications (among others, the SIMATIC

Start menu
Manager and the CFC editor) can be directly accessed via the Windows
start menu in the program group Simatic > (STEP 7).
User You will find the most important information on the SIMATIC Manager,
documentation HWConfig and CFC in the online help functions of these applications.
The help function is accessible via the Help menu or via the F1 key,
which is then context-sensitive.
When installation has been completed you will find the user
documentation in German and English about the start menu of Windows
(Start > SIMATIC > Documentation).
You can also separately order user documentation on CD-ROM.

A5E01078201-02 - Edition 01.2008
Basic software
1.2 User interface
Overview The software to configure and program is configured according to state-

of-the-art principles and is therefore essentially self-explanatory.
If you do not have any experience with these types of user interfaces,
then the following Section will provide you with information concerning
the most important control elements and the terminology used.
All users with Windows knowhow should get to know starting STEP 7 in
the "Starting STEP 7 software" Section. You don’t have to read the other
Sections of this chapter.
1.2.1 Starting the STEP 7 software
Starting After starting Windows, you will find an icon for the SIMATIC Manager on
the Windows screen - which is the entry into the STEP 7 software.
STEP 7 is started the quickest by double-clicking on the "SIMATIC

Manager" icon. The SIMATIC Manager window then opens. From here,
you can call-up all of the functions which you installed both in the basis
system as well as the software options.
Alternatively, you can also start the SIMATIC Manager via the "Start"
button on the task bar in Windows: You will find the entry under
"Simatic").
SIMATIC Manager The SIMATIC Manager is the interface to configure and program with D7-
SYS. With it you can:
• set-up projects
• configure and parameterize hardware
• configure hardware networks
• configure CFC charts
SIMATIC Manager is object-oriented, intuitive and can be easily learnt.
Proceeding You generate automation solutions in the form of "Projects". Before

starting, get to know the following basic issues:
• the user interface,
• online help,
• several basic handling functions.

A5E01078201-02 - Edition 01.2008
Basic software
1.2.2 User interface: Window
Overview The standard components of a window are the title bar and the menu bar
System menu Active window Active fields for

(full display/close etc.) title icon full display close
Title bar SIMATIC Manager

Menu bar File View PLC Options Window Help
Function bar
Work area:
Contains information which you
can display or process
Status line Depress F1 in order to obtain Help
Fig. 1-1 Window components
Title bar and menu The title bar and menu bar are always located at the top edge of the
bar window. The title bar contains the window title and the symbols for the
window control. The menu bar includes all of the menus, which are
available in the window.
Tool bar The tool bar contains all of the icons which allow you to quickly access, at
the click of the mouse, frequently used and currently available menu
commands. A brief info about the function of a symbol is displayed if you
briefly position the cursor on the icon. An additional explanation is
displayed in the status line.
Status line If no access is possible in the current configuration, then the icons are
grey.
Context-sensitive information is displayed in the status line.

A5E01078201-02 - Edition 01.2008
Basic software
1.2.3 User interface: Dialog boxes
Entries in the You can enter data in the dialog boxes, which is required to execute a
dialog boxes specific task. The most frequently used components of the dialog boxes
are now explained using an example in Fig. 1-2:
Text fields Search/replace

to enter text via Search for: Replace by:
the keyboard
A1.0 A2.0
Only complete word/complete line
Observe upper/lower case
Round option fields Search range Only search in
to select one or
several items from the cursor position upwards 0.all
from the cursor position downwards 1.components
complete 2.components
only marked areas 3.components
4.components
Square option fields 5.components
to select one
or several items Search in column
all
Active fields Search Replace Replace all Cancel Help
Fig. 1-2 Example of a dialog box
List fields / If text fields have an arrow pointing downwards, then additional items can
combination fields be selected for this particular field. Click on the arrow to display a list- or
combination field. If you then click on an entry in the list- or combination
field, it is automatically transferred into the text field.
Register dialogs The contents of some dialog boxes is organized in sections to enhance
the transparency. The names of the individual sections are located at the
upper edge of the dialog box. In order to retrieve a specific section,
simple click on the section name.
Module status
Path: test01\program (online) CPU operating mode: STOP

Status: Module operating mode:
Register General Diagnos. buffer Memory Cycle time Time syst. Perform. data Communication Stacks
names
Events:
No. Time Date Event

1 09:15:22:842 11.12.95 Power on, buffered
2 18:00:22:378 08.12.95 STOP due to power failure
Fig. 1-3 Example of a dialog box under a tab

A5E01078201-02 - Edition 01.2008
Basic software
1.2.4 Calling-up the help functions
The online help provides information precisely at the location you require
it. You can quickly retrieve specific information without having to search
in Manuals. You find the following in the online help:
Online help • Help subjects: Provides various access to help information displays
• Help to the context (F1 key): Displays information on the marked

object or for the active dialog box or window.
• Introduction: Provides a brief overview about the application,

essential features and functional scope of an application.
• First steps: Combines the first operator interventions which you must
make so that you move forwards quickly.
• Using help: Offers a description of the possibilities which you have at

your disposal to find specific information in help.
• Info: Provides information regarding the current version of the

application.
• Using the Help menu, from any window, you can call-up subjects
which refer to the current dialog situation.
Calling-up online You can call-up online help in several ways:

help
• Select a menu command from the help menu in the menu bar.
• Click on the "Help" button in a dialog box. You will then receive help
information regarding this dialog box.
• Position the mouse pointer in a window or dialog box on the subject

for which you require help; then depress key F1 or select the menu
command Help > Help to context.
• Simultaneously press the toggle key and key F1. The mouse pointer
changes into a ?. Click on the element of the window or dialog box
where you require specific help.
The three last types are known as context-sensitive help.
Calling-up short A brief help info is displayed for the buttons in the tool bar if you position
help the cursor at an button and keep it briefly there.
Changing the Using the menu command Options > Format size in the help window,
format size you can change the format size to "small", "normal" or "large".

A5E01078201-02 - Edition 01.2008
Basic software
1.2.5 Saving and restoring the window layout
Overview The STEP 7 applications allow you to save the current window layout and
restoring it at a later time.
What is saved? If you save the window layout, the following information is recorded:
• position of the main window
• opened projects and the associated window positions
• sequence of windows which may be nested
Save window To save the current window layout, select the menu command Window >
layout Save setting.
Restore window In order to restore a saved window layout, select the menu command
layout Window > Restore setting.
Information When restoring a window, only that part of the hierarchy is displayed in
regarding the detail, in which the object lies which was selected when saving the
object hierarchy window layout.

A5E01078201-02 - Edition 01.2008
Basic software
1.3 STEP 7 projects and basic handling
Overview Projects represent all of the data and programs associated with an
automation solution. They are used to save all of the data and programs
associated with the automation solution in an orderly fashion. The data
associated with a project, include
• configuring data regarding the hardware structure and parameterizing

data of the modules.
• programs for programmable modules.
The main tasks when creating a project thus involve preparing this data
and creating the programs.
STEP 7 does not specify a fixed processing sequence. You can start with
any partial task.
Information when The first part of this Chapter describes, use an example, the essential
reading project components.
You can display the properties of most of the objects using the menu
command Edit > Object Properties. This gives you an impression of the
information which is assigned to the object.
Basic handling of objects associated with a project are described in the

second part of this Chapter, for example, opening, copying and re-
naming.
The systematic procedure when setting-up your own project is described

in the Chapter "Setting-up and processing projects".
1.3.1 Opening a project example
Opening the To select and open a project included in the scope of supply, please
project, displaying enter the menu command File > Open > user projects or project
the contents examples.... Then select a project. The project window is then opened.
Project window The project window is sub-divided into two sections. The project structure
is displayed in the lefthand half. The contents of the objects, marked in
the lefthand side are displayed in the righthand side.
To display the complete project structure, click on the box with a plus
symbol in the lefthand section of the window. You will then obtain a
screen similar to the following:

A5E01078201-02 - Edition 01.2008
Basic software
Fig. 1-4 Project window
Object_hierarchy Several objects in the real world have specific interrelationships with one
another. These interrelationships from the real world are illustrated when
displaying the components of a project in the project window using a
logical hierarchy.
In Fig. Project window, at the top of the object hierarchy, the

"FIBEL_BSP" object is displayed as symbol for the complete project. It
can be used to display the project properties and is used as container for
networks (to configure networks), stations (to configure the hardware) as
well as for programs (to generate software). The objects contained in it
are displayed to the right in the project window if you highlight the project
icon. The objects at the top of the hierarchy (this also include, in addition
to projects, also SIMATIC libraries) allow you to go into the dialog boxes
to select objects.

A5E01078201-02 - Edition 01.2008
Basic software
1.3.2 Components to configure the hardware
Icons Icons of specific components:
MPI network SIMATIC TDC/SIMADYN D
Fig. 1-5 Specific components to configure the hardware
MPI-network The symbol for the MPI network represents the central communications
bus which fulfills the following functions:
• The CPUs of all stations of a project are loaded and are

commissioned with the test functions of the CFC.
• Communications between stations and display units.
Station The symbol for a station represents the hardware structure of a station. If
you highlight a station in the lefthand section of the project window, you
will see the objects it contains in the righthand section of the project
window:
• Newly inserted stations only contain the "Hardware" object, which you
can use to start the tool to configure the hardware.
• In already configured stations, the programmable modules (CPUs)

are also displayed, which were inserted when configuring the station.
In Fig. Project window, the configured SIMATIC TDC station is shown as

an example; this involves a hardware structure (subrack with slots) which
contains a CPU, designated "D01_P1".
Hardware By double clicking on the "Hardware" object in a station, you can start the
tool to configure the hardware. This procedure is described in detail in the
Chapter "Configuring and parameterizing modules".
1.3.3 Components to generate software
Programs The programs are containers for the software of a CPU and serve as
starting point when generating software.
Contents of a A program contains a "Charts" container. As many CFC/SFC charts as

program required are stored in this container. The CPU program is generated
using these. A CFC chart is represented on 26 sub-charts - each with six
pages.

A5E01078201-02 - Edition 01.2008
Basic software
Fig. 1-6 Possible components in a program
Read further ... You were able to get to know the essential objects of a project up to this
section of the Chapter. The next section provides you with information
about some of the basic activities and handling in conjunction with
objects.
1.3.4 Operator handling philosophy
Goal: Simple The graphic user interface is intended to make all operator actions self-
handling explanatory. Thus, you will see objects which you know from your daily
work, e. g. stations, modules, programs.
The actions, which you execute when working with STEP 7, include the
generation, selection and manipulation of objects such as these.
Difference to tool- With conventional tool-oriented handling, you first have to consider which
oriented handling tool was required to solve a specific task, and then you had to call-up this
tool.
The basic procedure for object-oriented handling is to consider which

object is to be edited, and then to open and edit this object.
For object-oriented handling, it is no longer necessary to know a special

command syntax. Objects are represented on the screen using graphic
symbols, which can be opened using menu commands or the mouse.
When opening an object, the suitable software components are

automatically called which are then used to display or process the
contents of the object.
Read further ... The basic actions when processing objects are now described in the
following. Please get to know these, as they are often used.

A5E01078201-02 - Edition 01.2008
Basic software
1.3.5 Creating and manipulating objects
Overview The usual object handling involves:
• creating an object,
• selecting an object,
• executing actions with the object (e. g. copying, deleting).
Setting-up the save Before first setting-up a new project, you should set the save path for
path for new these objects. To realize this, select the menu command Options >
projects Settings. You can then specify a path name under the tab " General " of
the dialog box which is displayed, under which the newly-generated
projects can be saved. C:\Siemens\STEP7\S7proj. is the default path.
Create objects You can generate new projects using the menu command File > New >
Project. Projects form the top of an object hierarchy tree. All additional
objects of the hierarchy, if they are not automatically set-up, can be
generated via commands in the Insert menu. The modules of a station
are the exception, which are only set-up when configuring the hardware.
Opening objects There are several ways of opening an already generated object:
• click twice on the object symbol
• select the object and menu command Edit > Open object
After an object has been opened, you can generate or change its
contents. In this case, a differentiation must be made between
• containers, i. e. objects, which can themselves contain sub-objects

(for example, a "Directory" object in Windows Explorer, which in turn
can contain sub-directories and files), and
• objects which do not contain any sub-objects, (for example, a "File"

object in Windows Explorer).
If you open an object associated with the latter type, its contents are
displayed in a new window for editing using a suitable software
component.
Objects, whose contents are being used elsewhere, cannot be changed.
Create an object After a container has been opened, the objects already contained in the
hierarchy container are displayed on the screen. You can now set-up additional
sub-objects using the Insert menu, for example, other stations in a
project. Only the commands to insert such objects can be called-up in
this menu, which are permissible in the current container.

A5E01078201-02 - Edition 01.2008
Basic software
Object properties are object data, which define the objects behavior. The
Setting object
dialog box to set the object properties is displayed automatically if you
properties
generate an object for the first time, and you must define its properties.
However, the properties can be subsequently changed:
A dialog box is called-up with the menu command Edit > Object
properties, in which the properties of the selected object can be read or
set.
Cutting-out, You can cut-out, copy, insert or delete most of the objects just the same
copying, inserting as under Windows. The associated menu commands are provided in the
Edit menu.
You can also shift or copy objects using drag & drop. The cursor is
displayed as a prohibit symbol if you point to an illegal destination/target.
If you copy an object, the complete hierarchy below it is also copied. This
allows parts of an automation solution to be re-used.
Printing First open the object to display the contents. The print command is
located in the first window menu (e. g. in the "File" menu). The command
displays a dialog box where you can set the printer, printer range and the
number of copies to be printed.
For several dialog boxes, it is possible to print-out part of its contents.

These dialog boxes contain a "Print" button. Press the button to start
printing.
Re-naming objects You can directly edit or change object names which can be changed via
the object properties.
• Direct editing:
If you slowly click twice on the name of a marked object, a box
appears around the text. You can now change the name from your
keyboard.
• Changing the name via the object properties:

Select the required object, and then enter the menu command Edit >
Object properties. Change the name in the dialog box. After closing
the properties dialog box, the object is re-named, and displayed with
the new name.
If it is not permissible to change the name of an object, the input field in

the dialog box has a grey background, the actual name is displayed, and
it is not possible to enter text.

A5E01078201-02 - Edition 01.2008
Basic software
1.3.6 Selecting objects in the dialog box
Overview Selecting objects in a dialog box is something which is done in various

operating steps.
Calling-up the The dialog box is called-up, for example, in the hardware configuration,
dialog box using the menu commands such as Station > New.../Open... (the
"SIMATIC Manager" entry window is an exception).
Dialog box The following can be selected, illustrated in the "Dialog box to select
structure objects" display:
Entry point: Select the object type

here in which you wish to start Online/offline:
the search. (e. g. “Project“, For SIMATIC TDC/SIMADYN D,
“Library", but also entries, only the offline view is possible
which permit access to (project data on the PG/ PC).
drives or connected
automation systems). Search: Click on this
button to search for
objects which are not
included in the list.
Open
Entry: View:
Project Components view Online Offline
Name: Project
muster Search...
Example MPI network 1 SIMADYN D station (1)

The hierarchy tree SIMADYN D program (1)
of the object is
displayed here, which
can contain sub-objects. The contents of the object
marked on the left are
displayed here.
Object name:
Object type: Process all
OK Cancel Help
Name: The objects of the type Object type: You can specify a filter
specified under entry is criteria here for the object list.
displayed here in a list box. This allows the number of displayed
You can select a name from objects to be restricted.
the list or enter directly
from the keyboard. Object name: If you select an object,
the object name is entered here.
You can also directly enter the
required name.
Fig. 1-7 Dialog box to select objects

A5E01078201-02 - Edition 01.2008
Basic software
1.4 Creating and handling projects
Overview This Chapter describes how you create projects and set-up the project
structure step-by-step.
1.4.1 Creating projects
Project example You can simplify creating a new project by adapting the example included
in the scope of supply (project example) to your particular requirements.
Proceed as follows:
1. Open the project example (refer to STEP 7 projects and basic

handling)
2. Save the project example under another name
(menu command, File > Save under ... ).
3. Now close the project example; open the copy.
4. Change the name of the sub-objects in this copy so that you can
identify the names.
5. Open the objects in the copy and modify the contents.
This is an extremely easy way to create a project structure.
New project If the project example is not suitable for you as the starting point, then
you can create a new project in the SIMATIC Manager by entering the
menu command File > New > Project.... Now open the project so that
you can create the project structure (project hierarchy).
Alternative When selecting the processing sequence of a project, you have a high
procedure level of flexibility. After you have created a project, for example you can
• first configure the hardware (stations) and then generate the software
for it (CFC charts), or
Alternative 1: First • you can start to generate the software independently of a configured
configuring the hardware.
hardware
If you first wish to configure the hardware, proceed as described in
Chapter "Creating and handling projects" > "Inserting and configuring
stations". After configuring, the programs and chart containers which are
required to generate the software are already inserted. You can then
generate the software for the programmable modules.
Alternative 2: You can generate the software without first configuring the hardware
First generating the which can then be realized later. The hardware structure of a particular
software station does not have to be defined before entering programs.
Proceed as follows:

A5E01078201-02 - Edition 01.2008
Basic software
1. Enter the required software container (programs) into your project

(refer to the Chapter "Creating and handling projects" > "Programs
with and without assigned hardware").
2. Then generate the CFC charts in the chart containers of the
programs.
3. Now configure your hardware.
4. Now allocate the program to a CPU after you have configured the
hardware.
NOTE You can call-up a dialog box using the menu command Options >
Settings. Under the "General" tab, you can select, among other things,
that when a project is opened, an archive of this project is generated as
back-up copy. In this case, select the entry "Archiving automatically
when opening project/library" (archiving is described in Chapter
"Archiving user programs").
1.4.2 Inserting and configuring stations
Overview In a project, the stations represent the hardware structure and the
associated data to configure and parameterize individual modules.
Inserting a station In order to create a new station in a project, open the project so that the
project window is displayed (if this already hasn’t been done).
1. Select the object.

2. Generate the object for the required hardware using the menu
command Insert > Station.
The following items are displayed in the menu:
• SIMATIC TDC/SIMADYN D station
• SIMATIC 300 station
• SIMATIC 400 station
• SIMATIC H-Station
• SIMATIC PC-Station
• PC/PG
• SIMATIC S5
• Other stations, i. e. not SIMATIC S7/M7, SIMATIC S5
3. Select the station
4. In the project window, click on the "+" in front of the project icon if it is
still not displayed below the station.

A5E01078201-02 - Edition 01.2008
Basic software
Proceed as follows:
Configuring
1. Open the station. It contains the "Hardware" object.
2. Open the "Hardware" object. The "HWConfig" window is displayed. In
this window, you can define the hardware structure, and especially the
slot assignment.
3. Define the station structure in the "HWConfig" window. A module
catalog is available which you can display using the menu command
View > Catalog if it hasn’t already been displayed. First select a rack
from the module catalog. You can then select the modules which you
wish to insert in the rack slots. It is important to note that you must
configure at least one CPU.
Configuring result Further information on configuring is provided in the Chapter "Configuring
and parameterizing the hardware" of this Manual.
A program is automatically created as software container for each CPU

which you created when configuring.
If this object is still not visible in the project window, click on the "+" in
front of the station symbol in the project window to display the module,
and in the box in front of the CPU to display the program.
Continue with Now generate the software. The basic procedure is explained in the
software Chapter "Principle procedure when generating software".
generation
If you wish to use software which was generated independently of your
particular configuration, then first read the Chapter " programs with and
without assigned hardware" and "Software generation without configured
hardware".
1.4.3 Programs with and without assigned hardware
Overview The " program" object is used as container for the software of
programmable modules from the SIMATIC TDC/SIMADYN D spectrum
and the FM 458-1 DP..
Project
D7-SYS programm (no hardware assigned)

SIMADYN D station
SIMADYN D CPU
D7-SYS pogramm (assigned)
Fig. 1-8 Assigned and non-assigned program in the project window

A5E01078201-02 - Edition 01.2008
Basic software
You can use the programs which were automatically created for pre-
Program with
configured (assigned programs). Click on the "+" in front of the CPU icon
assigned hardware
in the project window if this was still not displayed below the program.
Program without You can create programs yourself independently of any special hardware
assigned hardware configuration (non-assigned programs). After the hardware has been
configured, you can, at a later date, assign a CPU.
1.4.4 Generating software without configured hardware
Inserting the The project must have been created and the project window opened.
program
independently of 1. Select the project symbol in the project window.
the hardware
2. Call-up the menu command
Insert > Program > D7-SYS Program
The program is created below the project, i. e. it is not assigned to any
special hardware.
Assigning a You can now generate software in this container, and assign it to a CPU,
program to a CPU as subsequently described.
Proceed as follows:
1. Highlight the project icon or click on the plus symbol in front of the
project icon so that the assigned program is visible in the project
window if this isn’t already the case.
2. Cut-out the non-assigned program or copy it (menu command Edit >
Cut-out or Edit > Copy).
3. Then highlight the CPU which you wish to assign to the program, and
insert it (menu command Edit > Insert).
If there is already a program located there, then it is overwritten after a
message is acknowledged. Alternatively, you can highlight the non-
assigned program, and transfer it to the programmable module.
Buffering programs If you erase a CPU, but you still wish to keep the associated program in
in the project the project, then before erasing the module, shift it directly under the
project icon. It then remains there in the project without being assigned to
a module. You can assign it as required at a later time.
If you erase a station, whose CPUs are assigned to a program, a dialog

box is displayed. You can now decide as to whether the program should
also be erased (deleted), or whether it should be saved in the project
(without assigned hardware).

A5E01078201-02 - Edition 01.2008
Basic software
1.4.5 Principle procedure when generating software
NOTE Using the menu command Insert > Program > D7-SYS program, you
can create a program directly under the project without having to first
configure the hardware. You can later assign the program to a CPU.
Procedure Generate the software as follows:
1. Open the program.

2. Open the "Charts" container contained in it.
3. Insert a CFC chart. The menu command is as follows:
− Insert > S7 software > CFC
4. Open the chart, insert the blocks in this, interconnect and
parameterize these.
Information on this procedure is provided in the Manual: "STEP 7,
Optionspakete für D7-SYS, Section CFC" as well as online help for
CFC.
Generating the To document a STEP 7 project, you can arrange all configured data,
documentation which was generated using STEP 7, in circuit manuals (menu command
Insert > Project documentation).
This function is only available if the DOCPRO option package is installed.
1.4.6 Saving projects
Overview To save a project, you can save a copy of the project under a different
name, or archive the project.
Saving under ... Proceed as follows:
1. Open the project.

2. Select the menu command File > Save under. The "Save project
under" dialog box is then displayed.
3. At " Path " select the directory in which the project is to be saved.
4. In the "Name" box enter a file name.
5. Close the dialog box with "OK".
NOTE It must be guaranteed that there is sufficient memory space still

available on the selected drive. For instance, it is not practical to select
a floppy disk drive to archive a project. To save projects on floppy
disks, you must archive these. Archives can be distributed over several
floppy disks.

A5E01078201-02 - Edition 01.2008
Basic software
Individual projects can be saved in an archive file in a "zipped" form. It is

Archiving
possible to save "zipped" files on the hard disk or on other portable data
mediums (floppy disks).
In order to access components of an archived project, the project must

first be de-archived. Archiving is described in detail in the Chapter
"Archiving user programs".
Automatic You can set the system, so that when a project is opened, an archive of
archiving this project is generated as back-up copy. Proceed as follows:
1. In the SIMATIC Manager, select the menu command

Options > Settings. A register dialog is now displayed.
2. Select the "General" tab.
3. Mark the "Archiving automatically when opening project/library" entry.
4. Close the dialog box with "OK".

A5E01078201-02 - Edition 01.2008
Basic software
1.5 Configuring and parameterizing modules
Overview When configuring with STEP 7, you define which modules you will use for
your system, independent of whether they actually exist for your
particular system or not.
You can copy the configuration as often as you like in other STEP 7
projects, and if required modify them. When a station runs-up, the CPUs
compare the reference configuration, generated using STEP 7, with the
actual configuration of the system. If errors or problems are present, they
are immediately identified and signaled.
When parameterizing, you set the characteristics of the modules. You do

not have to actuate a switch on the module, but just simply enter the
parameter using STEP 7. The parameters are loaded into the CPU, and
transferred from the CPU to the appropriate modules.
Modules can be very simply replaced, as the parameters, generated

using STEP 7, are automatically loaded in the new module at run-up.
1.5.1 Creating a configuration
Introduction The following provides you with an overview how you configure the
structure of a station, and how to parameterize the modules within this
structure.
Configuring "Configuring" involves locating racks and modules in a station window.

Racks are represented using a configuration table, which permits a fixed
number of plug-in modules just like the "real" racks.
Parameterization "Parameterization" is the following:
Setting parameters for modules which can be parameterized, e. g. a CPU

is a module which can be parameterized. The base sampling time is a
parameter which you can set.

A5E01078201-02 - Edition 01.2008
Basic software
Proceed as follows when configuring and parameterizing a system

Procedure
structure:
Select the rack
Select the modules
Parameterize the modules
Check the consistency of the configuration
Save the configuration
Fig. 1-9 Procedure when configuring and parameterizing
Before entering a Before you enter a new configuration, you must:

new
configuration... • create a project,
• generated in the project the object to be configured, i. e. a station, and
• you must have selected this station.
The procedure is described in the Chapter "Creating projects".
Calling-up the To call-up the application to configure a station, proceed as follows:

application
1. Select the "station" object in the project window.
2. Select the menu command Edit > Open Object.
The HWConfig user interface is displayed on the screen to configure
the hardware.
As an alternative to steps 1. and 2. you can also click twice on the
"Hardware" object in the station.
1.5.2 General handling
Main components You have two dialog windows available to configure an automation
of the user system.
interface
• With the station window, in which you locate the rack for the station
configuration.

A5E01078201-02 - Edition 01.2008
Basic software
• With the "Hardware Catalog" window, from which you can select the
necessary hardware components, e. g. racks, modules and sub-
modules.
General handling • If the "Hardware Catalog" window is not displayed, select the menu
command View > Catalog. You can now display or cancel the
Hardware Catalog using this menu command.
Independent of a particular station structure, you always configure in the

following steps:
1. To open the sub-directory, click on the "+" symbol in the directory

listing of the Hardware Catalog.
2. Mark a hardware component in the "Hardware Catalog" window.

3. Place the selected hardware component in the station window using
drag & drop.
This is how it’s The "Arrange rack" display shows the essential handling:
done
Fig. 1-10 Rack layout

A5E01078201-02 - Edition 01.2008
Basic software
As for Windows applications, you can implement the overall configuration

Summary
in STEP 7 per drag & drop. This example will show you what you must be
aware of.
1.5.3 Example
Procedure Exactly as you would in your real system, locate the modules in the racks
using STEP 7. The difference: In STEP 7, racks are represented using
"Configuration tables", which have as many lines as the number of
modules which can be inserted in the real racks.
Converting into a An example for converting a real structure into the configuration table is
configuration table shown in an example in the following Fig. 1-11.
Configuration table
(normal view)
SR12.1
1 PM5
1.1 MS5
2 MM3
3 EB11
4 PM6
4.1 MS5
5 IT41
6 CS7
6.1 SS52-MPI
6.2
6.3
Slot 1 2 3 4 5 6
Structure of a SIMADYN D station
Fig. 1-11 From a structure to a configuration table
1.5.4 Arranging modules
Select and arrange Prerequisite: The station window and "Hardware catalog" window are
racks open. Proceed as follows:
1. Select the right rack for your particular structure from the sub-directory
"racks" in the "Hardware catalog" window.
2. Locate the rack in the station window using drag & drop.
As an alternative to steps 1. and 2., you can also click twice on the rack
in the "Hardware catalog" window.

A5E01078201-02 - Edition 01.2008
Basic software
Proceed as follows to locate modules in the racks:

Select and arrange
modules
1. Select a module from the "Hardware catalog" window.
2. Place the module into the appropriate rack tier per drag & drop.
As an alternative to steps 1. and 2., you can also mark an empty tier, and
then double click on the module in the "Hardware catalog" window or
mark a module and hit the ENTER KEY ↵.
1.5.5 Parameterizing modules
Parameterizing You can set the characteristics of modules which can be parameterized.
The module type defines which parameters can be set.
Prerequisite Before you parameterize a module, you must first place the module in the
rack.
To parameterize a module, proceed as follows:
Parameterizing Double-click on the rack tier with the module, whose parameters you wish
modules to set, or mark the associated module and select the menu command
Edit > Object Properties.
A dialog box is displayed with one or several registers with information
and parameters which can be set for the particular module.
Allocating You assign module hardware addresses as follows:

I/O addresses
1. In the configuration table, click on a module, which has process signal
I/O, e. g. a CPU-, I/O- or extension module.
2. Select the menu command Edit > Object Properties and select the
"Addresses" tab in the dialog box "Properties".
3. Enter a name for each module connector in the "Symbol" field and
acknowledge with "OK". You can change the symbols about the
control button To "preset" also with unambiguous names preset.
NOTE Assign unique names within any one station.

You can obtain help information for an active tab if you press F1 with
the "Properties" dialog box open.

A5E01078201-02 - Edition 01.2008
Basic software
1.5.6 Linking-in hardware signals to the user program
Prerequisite Prior to this, you must have assigned I/O addresses (hardware
addresses) to the module in HWConfig.
Procedure in CFC Link-in the hardware signals to the user program in the CFC as follows:
1. In the CFC, configure an appropriate I/O block to address the

hardware signals of a connector.
2. Select the "AD" input (hardware address) of this block, and select the
menu command Insert > Connect to operand. A dialog box opens to
enter the hardware address.
3. Select the connector name, defined in HWConfig, in the "Hardware

address" list field and acknowledge with "OK".
1.5.7 Consistency check, saving and loading
Introduction In this Section you will get to know how to check and save a generated
configuration for consistency. However a prerequisite is that the station is
parameterized and configured.
Configuration save, To save the configuration use the following menu command
Station > Save or Station > Save and compile.
For Station > Save and compile, the configuration is checked for
consistency, and saved in the current project (as station object).
A consistency check is not made for Station > Save.
NOTE CPU charts for this particular station can only be compiled in the CFC,
if the saved hardware configuration has been checked for consistency.
Configuration load In CFC, the hardware configuration is, together with the compiled user
program, automatically loaded in the CPUs of the station.
Consistency check You check the consistency using the menu command Station > Check
consistency.
• If the configuration is error-free, acknowledge the message "No error"

with "OK".
• If the configuration is not error-free, a message appears with a list of

errors. Hit the F1 key to obtain help for the "Check consistency" dialog
box.

A5E01078201-02 - Edition 01.2008
Basic software
1.5.8 Working in the configuration table
Introduction We will now provide you with several tips to simplify working with
HWConfig.
Mark several lines If you wish to mark several lines in the configuration table, for example, to
delete several modules or insert several modules of the same type, then
proceed as follows:
• Select all lines:
− select the menu command Edit > Select All
• Select associated ranges:
− click on the first line of the range to be marked
− keep the changeover key depressed and click on the last line of
the range to be marked.
• Selecting several lines:
Shifting modules − depress the CNTRL key, keep it depressed and then click on all of
the lines which you wish to select
You can shift modules or other components simply per drag & drop to
another legal slot within the station.
1.5.9 Configuring PROFIBUS DP
Introduction The communications module can be used both as master as well as

slave in a PROFIBUS DP sub-network.
Configuration as The configuration as slave in a network with an S7 module as master is

slave described in the Chapter "Configure the distributed periphery " of the
Manual "Configuring Hardware and Communication Connections
STEP7".
SS52 is included in the module catalog of HWConfig under "PROFIBUS

DP - SIMADYN".
Configuring as The PROFIBUS master is configured using the COM PROFIBUS tool of
master the SIMATIC S5 product family.
An FM 458-1 DP is configured as PROFIBUS Master in HW Config as

described in the Section “Configuring the distributed I/O“ of the Manual
“SIMATIC Software, basis software for S7 and M7 STEP7“.
Further information You will find further information in the Instruction Manual of COM
... PROFIBUS as well as in the Manual "System- and communication
configuring D7-SYS".

A5E01078201-02 - Edition 01.2008
Basic software
1.6 Creating communication connections
Overview If you require several CPUs for your automation solution, or it is

necessary to couple the display units, then you must ensure that the
components involved can communicate with one another.
Differentiation can be made between two communication types:
1. Communications within a station

2. Communication connections with display units
NOTE Communications between CPUs are exclusively created in CFC.
1.6.1 Communications within a station
Overview There are two ways to implement data transfer between CPUs:
Communications via Properties
$ signals: • are adequate for many
applications
• are simple to configure.
Virtual connections: • for more complex communication
associations between transmitters
and receivers
• takes longer to configure.
Table 1-4 Communications within a station
1.6.1.1 Communications via $ signals
Purpose of the $ signals permit efficient communications between a transmitter and

$ signals several receivers.
Prerequisites for Prerequisites for communications via $ signals:

communications
via $ signals • Transmitter and receiver are located on different CPUs within the
same station.
• A communications buffer module is used for communications between

the CPUs and is inserted in the subrack.

A5E01078201-02 - Edition 01.2008
Basic software
There are two types of $ signals:

Type Properties
Standard Ensures data consistency
Fast Data transfer with the shortest possible deadtimes
Table 1-5 Types of $ signals
NOTE In order to equalize the load levels due to $ signals of the two
backplane busses (for SIMADYN D), you can distribute the $ signals
between the L bus and C bus.
Procedure 1. In the SIMATIC Manager, double-click on the CFC charts which

include the block I/O for the communication connections.
2. In the CFC application window, select the block output, from which the
$ signal is to be taken.
3. Select the menu command Insert > Connection to operand.
4. Select the required "bus" and "type" options.
5. Enter a unique name of up to 14 characters in the "Name" field.

Acknowledge with "OK".
6. Select the block input as destination for the $ signal.
7. Select the menu command Insert > Connect to operand.
8. In the "Name" field, enter the $ signal, assigned at the block output.
Acknowledge with "OK".
NOTE • You can connect the $ signal with other block inputs. Proceed as
previously described under steps 6, 7 and 8.
• At step 8 in the "Name" list field, you will be provided with a

selection of already configured $ signals.
• You can obtain additional help info by depressing key F1 with the
"Global operand" dialog box open.

A5E01078201-02 - Edition 01.2008
Basic software
1.6.1.2 Communications via virtual connections
Prerequisites Additional function blocks must be configured:
• Transmit- and receive blocks of the process data utility
• Central blocks to administer the couplings used.
Communication Virtual connections permit communication associations between:

associations
• 1 transmitter - 1 receiver
• 1 transmitter - several receivers
• several transmitters - 1 receiver
An appropriate data transfer mode is specified at the transmit- and

receive blocks.
Transmitter and receiver can be located on different CPUs and can be

connected via any coupling.
Procedure 1. In the SIMATIC Manager, double-click on the CFC charts, which

include the I/O for the communications connection.
2. In the CFC application window, select the block output from which the
virtual connection is to be taken.
3. Select the menu command Insert > Connection to operand.
4. Select the "virtual connection" option.
5. Enter a unique name in the "virtual connection name" field, and a

number in the "sequence number field". The "virtual connection name"
can comprise six characters. Acknowledge with "OK".
6. Select the block input as destination for the virtual connection.
7. Select the menu command Insert > Connection to operand and the
"virtual connection" option.
8. In the "virtual connection name" field, enter the name assigned at the
block output, and in the "sequence number" field, the number
assigned at the block output. Acknowledge with "OK".
9. Configure the required transmit-, receive- and central blocks. You will
find the necessary steps in the Manual "System- and communication

A5E01078201-02 - Edition 01.2008
Basic software
NOTE • You can connect the virtual connection with other block inputs.
Proceed as previously described under steps 6, 7 and 8.
• At step 8 in the "Virtual connection name" list field, you will be

provided with a selection of already configured $ symbols.
• You can obtain additional help info by pressing F1 with the "Global
operand" dialog box open.
Additional information
on virtuell connections refer to the "System- and communication
configuring D7-SYS“.
1.6.2 Communications with display units
Overview Communication links can be configured to the following display units :
• SIMATIC-OPs
• WinCC
Prerequisites In order to establish a communications link to a display unit, the following

conditions must be fulfilled:
• The partner must be in an MPI network.
• A coupling module must be inserted in the subrack.
• The required function blocks (FB) must be configured in the user

program.
Refer to the "System- and communication configuring D7-SYS ". User
Documentation for communications with display units.

A5E01078201-02 - Edition 01.2008
Basic software
1.7 Loading programs
Overview After configuration, parameterization and program generation have been

completed, transfer the user program into the target system. This Chapter
describes how you select the interface and load the user programs.
The complete user program of a CPU is loaded into an automation

system at one go. The hardware configuration of this CPU as well as the
operating system are also automatically loaded.
There are two Loading via an online connection The user program is loaded into the
(access to the target system): memory module inserted in a module
possibilities of receptacle of the CPU. The program
loading data into memory is buffered during power
the CPU failures.
Loading the user program into the The user program is loaded into a
memory module offline: memory module in a PCMCIA socket
of the generating system. The
memory module with the loaded user
program is inserted in the module
receptacle of the CPU.
Table 1-6 How the programs can be loaded into the CPU
NOTE In order to activate the user program in the memory module of the CPU
the station with this CPU must be restarted (cold restart).
1.7.1 Online loading
1.7.1.1 Selecting the interface for the online connection
An online connection is required between the generating system and

target system for the following activities:
• Online loading into a CPU
• Testing user programs
• Displaying the module status of a CPU
• Displaying and changing the operating status of a CPU
You can select the online interface via which an online connection is to
be established to the target system.
Possible interfaces Possible interfaces for online connections:

for online
connections • Multi-point capable interface (MPI) or
• RS232 interface (COM1 or COM2)

A5E01078201-02 - Edition 01.2008
Basic software
1. From the Windows task bar, select the menu command Start >
Selecting the
Simatic > Step 7 > Set PG-PC interface.
interface for the
online connection
2. Select the interface used and select the correct parameter.
NOTE • If you depress key F1 with the dialog box open, you can obtain
additional info.
• For an online connection via the MPI interface, the generating

system must have an MPI interface.
• Ensure that the properties of the selected interface have been

correctly set. The baud rate for the MPI interface must correspond
with the baud rate which was configured for the coupling partner.
1.7.1.2 Online loading into a CPU
Prerequisites • You have established an online connection between the generating

system and the station with the CPU.
• You have compiled the user program of the CPU in the CFC.
Additional • You have set switch S1/8 on the T400 to the off position.
prerequisites when
loading a T400- • You have established an online connection between the generating
CPU system and the T400 (serial interface X01, terminals 67..68).
Procedure 1. In CFC bring into the foreground the window of any chart from the
CPU to be loaded.
2. In CFC select the menu command PLC > Download.
3. From the load versions, select the "online" option, and acknowledge
this with "Load".
4. Repeat steps 1 to 3 for the other CPUs of the station.
5. In the CFC select the menu command PLC > Operating Mode.
6. Restart the station in order to start the loaded user program.

A5E01078201-02 - Edition 01.2008
Basic software
1.7.2 Offline loading
1.7.2.1 What you need to know about memory modules and the
programming interface
CAUTION • Hitch-free and safe/reliable operation is only guaranteed if you use

! the memory modules which Siemens has released for SIMATIC
TDC/SIMADYN D. The memory cards from SIMATIC S7/M7 cannot
be used for SIMADYN D.
• Do not attempt to load a memory module, logged-on as drive with

Windows. The files you have on the drive could be lost.
Released memory PCMCIA/JEIDA modules according to the PC card standard can be used
modules as memory modules for CPUs.
The Micro Memory Cards from the SIMATIC family are used as memory
card for the FM 458-1 DP (refer to Catalog ST DA 2003).
The memory modules released by Siemens are listed together with their
Order Nos. in the HWConfig module catalog under "modules - program
memory".
NOTE FLASH memory modules, series 1

Older FLASH memory modules ("Series 1") cannot be used.
1.7.2.2 Selecting the loading interface
Prerequisites You have activated PC-card support on your generating system:
• A "PC card" icon is displayed in the "Control Panel" window of

Windows.
NOTE If PC-card support is not activated, then follow the instructions in the
online help of Windows under the index entry "PC cards, activating
support of".

A5E01078201-02 - Edition 01.2008
Basic software
1. From the Windows task bar, select the menu command Start >
Selecting the
Simatic > Step 7 > D7-SYS - Select PCMCIA interface.
programming
interface
2. In the "PCMCIA socket" dialog box select the required PCMCIA
socket and confirm with "OK".
NOTE • If your generation system has several PCMCIA sockets, then select
the socket which is to be used for offline loading. Number 1 is
automatically selected for this socket.
• If you press F1 with the "PCMCIA socket" dialog box open, then you
will obtain additional help info.
1.7.2.3 Offline loading into a memory module
Prerequisites • Your generating system has a PCMCIA socket.
• Your PC card support function is activated.
• You have selected the PCMCIA socket via which loading is to be

realized.
• You have compiled the user program of the CPU in the CFC.
Procedure 1. In CFC bring into the foreground the window of any chart from the
CPU to be loaded.
2. Insert a suitable memory module into the selected PCMCIA socket of

the generating system. Ensure that the write protection of the memory
module is not enabled.
3. In the CFC select the menu command PLC > Download.
4. Under load type select the "offline" option and acknowledge with
"load".
5. Repeat steps 1 to 4 for the other CPUs of the station.
6. Power-down the station, insert the memory module into the

appropriate receptacle of the CPUs and then power-up the station.
NOTE Please ensure that the memory module is inserted in the associated
CPU.

A5E01078201-02 - Edition 01.2008
Basic software
1.8 Testing programs
Overview A program is tested (debugged) using the CFC in the test mode. This
also provides you with the possibility of making changes to the software
online and in many cases eliminates you having to re-load the CPU.
With the CFC in the test mode you can, online:
• display values at any block I/O
• change values at block inputs which are not interconnected
• delete interconnections between blocks
• insert interconnections between blocks
• delete function blocks
• insert new function blocks (under the assumption that the block type is
already available on the CPU)
• change the number of inputs of generic blocks
1.8.1 Testing programs
CAUTION • When testing with the plant/system operational, incorrect operator

! control, functional faults/errors or program errors can cause severe
personal injury or material damage!
• Before executing any function, ensure that this cannot initiate a

potentially hazardous condition!
NOTE • Changes are made simultaneously both in the charts on the

generating system as well as in the user program being executed.
The statuses of the user program in the generating system and in
the target system are identical.
• After a cold restart or after the station has been powered-down,

changes are still effective.

system and stations with the CPUs to be tested.
• The CPUs to be tested are already loaded with the user program to be
tested.
• The CPUs are in the RUN operating mode or STOP operating mode.

A5E01078201-02 - Edition 01.2008
Basic software
• You have set switch S1/8 of the T400 to the off position.
Additional
prerequisites when
• You have established an online connection between the generating
testing user
system and the T400 (serial interface X01, terminals 67..68).
programs on a
T400-CPU
Procedure 1. Open the charts to be tested in the CFC.
2. Select the menu command Debug > Test mode
3. Select the I/O, which you wish to monitor in the target system, by
• selecting an I/O of a function block and selecting the menu

command Debug > Register I/O.
• selecting one or several function blocks and selecting the menu

command Test > Register I/O. All of the I/O of the selected
function blocks are now registered for testing.
4. The actual values are displayed.
NOTE The following functions of the create mode of the CFC result in the
appropriate online changes in the test mode:
• Changing parameter values
• Deleting and inserting interconnections
• Deleting and creating blocks
• Changing the input number of generic blocks

Further information on testing user programs, refer to the "STEP 7
Optionspakete für D7-SYS" or the online help to CFC.

A5E01078201-02 - Edition 01.2008
Basic software
1.9 Diagnostics
Overview Diagnostics includes the identification, evaluation and signaling of

diagnostic events, which occur within the SIMATIC TDC/SIMADYN D
control system. In this case, there is a diagnostics buffer in every CPU, in
which detailed information can be entered on all of the diagnostic events.
For the diagnostics, evaluate the following information, saved in the CPU:
• Information about the module status
• Information about the operating status of a CPU
By interpreting this information, you can quickly identify, localize and

resolve faults and errors. You also significantly reduce the standstill times
which occur when a fault/error condition develops.
Diagnostic You have the following diagnostic functionality:

functionality
• Call-up the module information from the SIMATIC Manager in the
Offline project view
• Call-up the module information from the CFC
• Display the value at connection YTS for communication blocks
• Display the type of diagnostics event via the 7-segment display on the
front panel of the particular CPU module
• Refer to the "Hardware" Manual for the seven-segment display of the

CPU modules.
• For the value at connection YTS of communication modules, refer to

the "Function Block Library" Reference Manual, or fault numbers in
the online help "Help on events". (Press the F1 key in the CFC and
call-up the topic "Help on events" under "CFC”.)

A5E01078201-02 - Edition 01.2008
Basic software
Call from the SIMATIC Manager

SIMATIC Manager Menu command:
Project Program PLC > Module Information
SIMADYN D station
CPU
Module Information
Fig. 1-12 Calling-up the diagnostics from the SIMATIC Manager
You do not have to configure the diagnostics data acquisition by the

diagnostics. It is available as standard and runs automatically.
Diagnostic events Operating status transitions (e.g. from RUN to STOP) and entries of the
following error classes are displayed as diagnostics events:
• Error while initializing ("0")
• Monitoring error ("b")
• Communications error ("C")
• Task administration error ("E")
• User error ("A")

(Diagnostics event defined by the user with function block USF)
1.9.1 Diagnostics in the SIMATIC Manager in the offline project view
NOTE • For diagnostics you must have the Station configuring software
(HWConfig and CFC) on the PC/PG.
• If you do not have the Station configuring software on your PG/PC,

then you must configure the Station hardware in HWConfig. In this
case, you can only use a limited scope of the diagnostics, as you
don't have access to the charts.

A5E01078201-02 - Edition 01.2008
Basic software
1.9.1.1 Transferring diagnostics information
The CPU identifies the error, and enters the diagnostic events into the
diagnostics buffer. The PG/PC can read-out these diagnostic messages.
CPU
The diagnostics function of the

CPU identifies the diagnostics
event.
System status list
STEP 7
Diagnostics buffer
Fig. 1-13 Transferring diagnostics information
Reading-out You can display the diagnostic messages in plain text using the following
diagnostics dialog boxes in the SIMATIC Manager:
information
• Dialog box "Module Information"
− indicates where and when the error occurred
• Dialog box "Diagnostics"
− indicates the type of diagnostics event associated with the entry

(user error, communications error, transitions between operating
statuses, ...)
− displays the module names of the diagnostic events (if available)

A5E01078201-02 - Edition 01.2008
Basic software
1.9.1.2 Steps to call-up the module information from the SIMATIC Manager

system and the stations, which include CPUs whose status you wish
to call-up.
• The CPUs are either in the RUN condition or STOP condition.
Procedure 1. Select a station from the project view (offline) of the SIMATIC
Manager and open this by clicking on it twice.
2. Select the CPU to be diagnosed.
3. Select the PLC > Module Information menu command.
4. The "Module information" dialog box with the tab "General" and
"Diagnostic buffer" of the CPU are displayed.
5. Click on the "Special diagnostics" button, in order to open the dialog
box "Diagnostics" using the "Diagnostic buffer" tab.
NOTE You can obtain additional help by pressing key F1 with the "Module
Information" or "Diagnostics" dialog box open.
1.9.1.3 Evaluating the diagnostics buffer of the diagnostics
Organization of the The contents of the diagnostics buffer are also kept even after the station
diagnostics buffer has been reset.
NOTE The entries in the diagnostics buffer are deleted at power failure or by
powering-down the power supply voltage of the subrack, if there is no
back-up battery or if this battery is displayed.
The diagnostics buffer is designed as ring buffer for a maximum of 120

entries. If the maximum number of entries is reached, then for a new
diagnostics buffer entry, the oldest entry is overwritten. All of the entries
then shift forwards. This means, that the most recent diagnostic entry is
always in the first position.
Special diagnostics Events

- "Diagnostic The following information must be entered, for each diagnostics event, in
buffer" tab the list of the "Diagnostic buffer" tabs in the " Diagnostics" dialog box:
• Consecutive entry number
• Date and time of the diagnostics event
• Error class of the entry
• Brief designation of the event

A5E01078201-02 - Edition 01.2008
Basic software
• Number of the CPU, name of the chart and block name, for which the
diagnostics event occurred, separated by a point.
Details on the event

In the list, select an event and in this field you will obtaine a detailed
description:
• Designation of the event and event number
• Supplementary information, dependent on the event
• Incoming or outgoing event
Help on the event

Using the "Help on event" button, you will obtain information about the
cause of the event and counter-measures for the event marked in the list
field.
1.9.2 Diagnostics in the CFC
In the CFC, you can call-up the module information of a CPU.
The module status includes:
• the error fields of the CPU
• the exception buffer of the CPU
1.9.2.1 Steps to call-up the module status from the CFC

system and the stations which include the CPUs whose status you
wish to call-up.
Procedure 1. In the CFC bring into the foreground the window of any chart of the
CPU whose module status you wish to call-up.
2. Select the menu command CPU > Module Information.
3. Select the "Error panels" or "Exceptions" tab.
NOTE You will obtain additional help info if you depress key F1 with the
"Module Information" dialog box open.
Further information
on the contents of the exception buffer, please contact the Hotline.

A5E01078201-02 - Edition 01.2008
Basic software
1.9.2.2 Displaying and changing the operating mode

system and stations with the CPUs whose operating status you wish
to display.
Procedure 1. In the CFC bring into the foreground the window of any chart of the
CPU whose status you wish to display.
2. Select the menu command PLC > Operating Mode. The actual
operating mode of the CPU is then displayed in the "Operating Mode"
dialog box.
3. If you wish to restart the CPUs of the station, select "Cold restart".
4. If you wish to set the CPUs of the station into the "User stop" mode
then select "Stop".
NOTE You will obtain additional help info if you press F1 with the "Operating
Mode" dialog box open.

A5E01078201-02 - Edition 01.2008
Basic software
1.10 Archiving user programs
Overview Individual projects can be saved, "zipped" in an archive file. These

"zipped" files can be archived on hard disk or on other transportable
mediums (floppy disks).
1.10.1 Archive programs
Application You archive user programs in the SIMATIC Manager.
The archiving function provides you with an interface to call-up your

preferred archiving program.
Archiving You can use the following archiving programs:

programs which
can be used • pkzip from Version 2.04g
• arj from Version 2.41a
• lha from Version 2.13
• winzip from Version 6.0
The arj archiving program is included in the scope of supply.
Prerequisites You must have installed the archiving program on your system. An
explanation of how you embed it in STEP 7 is given in Chapter "Archiving
projects".
NOTE A DOS window is displayed while archiving/de-archiving; you can only

continue to work in the SIMATIC Manager when this window is closed.
Set the In the properties of the archiving program, select that the DOS window
characteristics of automatically closes after archiving/de-archiving.
the archiving
program Proceed as follows:
1. In Windows Explorer select the archiving program and then the menu
command File > Properties
2. Select the "Program" tab in the dialog box which is then displayed.
3. Select the "Close when completed" option
4. Click on the "OK" button.

A5E01078201-02 - Edition 01.2008
Basic software
1.10.2 Archiving projects
Selecting your In order to select an archiving program, proceed as follows:

preferred archiving
program 1. In the SIMATIC Manager select the menu command Options >
Settings. You can then select from the displayed tabs.
2. Select your preferred archiving program under the "Archiving" tab.
The arj archiving program is preset (default).
Selecting the The standard STEP 7 configuration assumes that the archiving program
search path for the is installed in the DOS search path. If the archiving program is installed
archiving program outside the search path, proceed as follows:
1. In the SIMATIC Manager select the menu command Options >

Settings. You can then select from a number of tabs.
2. Using the "Configuring" button under the "Archiving" tab, call-up the
"Configure archiving" dialog box.
3. In the "Program path" field enter the path name of the archiving
program or select it using the "Search" button.
4. Close the dialog boxes with "OK".
Pre-setting the You can pre-set target directories, both for archiving and also de-
target directories archiving. Using these settings you can eliminate having to enter
directories when archiving and de-archiving.
Proceed as follows to pre-set target directories:
1. In the SIMATIC Manager select the menu command Options >

Settings.
2. In the dialog box displayed, select the "Archiving" tab.
3. Enable the "Use the archive directory when archiving" or "Use the
archive directory when de-archiving" options.
4. Enter the path in the associated text field or select a directory via the
"Search" button.
For de-archiving, you can select the automatic target directory search.
Archiving projects 1. Close the dialog box with "OK".
Proceed as follows to set-up an archive
1. Ensure that no windows are open for the project which you wish to
archive.
2. Select the menu command File > Archiving > Project.
3. Depending on your archiving settings (under Options > Settings,
under "Archiving" tab), an additional dialog box is displayed. There,
you can set the target directory for the archive file, the file names and
the file type. Via the file type, STEP 7 identifies the archiving program
to be used (e. g. "zip" for PKZIP).

A5E01078201-02 - Edition 01.2008
Basic software
4. Select the project, which you wish to archive, from the subsequent
dialog box.
5. If required, you can make special archiving settings in an additional
dialog box (e. g. saving over several floppy disks). The dialog box is
only displayed if you activated the options prompt in your archiving
settings, and the archiving program supports options.
A DOS window is opened, in which the archiving runs. The project is
"zipped" and saved in the target directory.
Copying onto You can archive a project as described above and copy the archived file
floppy disk onto a floppy disk. It is also possible to select a floppy disk drive in the
"Archiving" dialog box.
1.10.3 De-archiving projects
Overview Projects cannot be directly processed in archives. The associated files

and data must first be retrieved from the archive.
Processing Proceed as follows:

archived projects
1. In the SIMATIC Manager select the menu command
File > De-archiving.
2. In the dialog box which is displayed, select the archive file, which
contains the "zipped" project.
The settings which you made under the "Archiving" tab, which you can
call-up with Options > Settings, determines whether the following
dialog boxes are displayed.
3. If relevant, select the target directory where data are to be de-archived

("unzipped") in the next dialog box.
4. If relevant, additional settings for "unzipping" can be made in an

additional dialog box.
NOTE The directory names, in the path, must not exceed 8 characters
After the dialog box is closed, a DOS window is opened, where you can
see how the file is unzipped.
When unzipping, the project is set-up, and its contents retrieved from the
archive. You can now open the project and process it or copy sections
out of it, and insert them into another project.

A5E01078201-02 - Edition 01.2008
Basic software
1.11 Printing
Overview After you have completed generating the program for your automation
task, you can print out all of the important data using the print function
integrated in STEP 7. This then allows you to generate your own project
documentation.
DOCPRO option To create, process and print standardized circuit manuals, you can use
package the DOCPRO option package. Thus, you have at your fingertips a
plant/system documentation which fulfills the DIN- and ANSI Standards.
1.11.1 Setting-up the printer
Setting-up the Select the menu command File > Print Setup to set-up a printer and
printer define the page orientation (portrait or landscape).
Setting the page Select the menu command File > Page Setup to set the page format for
format printing (e. g. A4, A5, Letter).
Setting headers Change the print form so that it matches the required paper format. If the
and footers form is too wide, the righthand margin is printed-out on a subsequent
sheet.
You can set the headers and footers for your documents to be printed
using the SIMATIC Manager with the menu command File > Headers,
footers.
Print preview You can preview the printout using the menu command File > Preview.
NOTE Several STEP 7 application programs only offer a part of these menu
commands.
1.11.2 Starting to print
Project parts which You can print the following specific components of a project:
you can print
• The configuration table of a station with the layout of the modules and
module parameters
• CFC charts
Basic procedure To print proceed as follows:
1. Open a suitable object to display the information to be printed on the

screen.

A5E01078201-02 - Edition 01.2008
Basic software
2. Insert the "Print" dialog box into the window using

the menu command File > Print....
Depending on the window, the first entry in the menu bar can be other
than "File", e. g. "Station".
3. When required, change the printer settings (e. g. printer, print range,
number of copies) in the dialog box and then close it. You can obtain
more detailed information on printing in the online help.

A5E01078201-02 - Edition 01.2008
2 CFC
Overview 2.1 Working with the CFC editor 2-2
2.2 Brief guide 2-23
2.3 Testing and commissioning 2-34
2.4 Creating block types 2-49
2.5 Archiving projects on the MC - saving and retrieving 2-52
2.6 Chart reference data-documentation 2-61
2.7 Technical data 2-64

A5E01078201-02 - Edition 01.2008
CFC
2.1 Working with the CFC editor
This Chapter provides you with system-specific information about CFC

(Continuous Function Chart)and how it is embedded in the STEP 7
software package. It also describes the mode of operation of the CFC
editor, if this wasn’t previously discussed in the Manual "CFC for S7".
2.1.1 CFC in the STEP 7 environment
How CFC is Fig. 2-1 shows how the CFC is embedded in the STEP 7 environment:
embedded
SIMATIC Manager
CFC
STEP 7 components STEP 7
SIMATIC TDC/ SIMADYN D
Fig. 2-1: CFC in the STEP 7 environment
The following STEP 7 components are of significance when working with

CFC for the option package D7-SYS.
STEP 7 • SIMATIC Manager

components The SIMATIC Manager administers tools and data. It also sets-up and
changes a project structure (SIMATIC TDC/SIMADYN D-/SIMATIC
400 stations, D7-SYS programs, CFC-/SFC charts and starts the
CFC/SFC editor as well as compiles charts.
• HWConfig
You can configure the hardware configuration of a SIMATIC
TDC/SIMADYN D station or SIMATIC 400 station with FM 458-1 DP
using HWConfig. Using CFC, you refer to the properties of the
configured modules, for instance, names of hardware.
2.1.1.1 Software requirements
The operating system Windows 95, 98, ME, NT 4.0, 2000 or XP and the
STEP 7 basis software must be installed. For CFC, you require different
software option packages depending on the target system.

A5E01078201-02 - Edition 01.2008
CFC
With the CFC for SIMATIC TDC/SIMADYN D and FM 458-1 DP you

Prerequisites
require the D7-SYS option package.
With D7-SYS, you are provided block libraries for SIMATIC
TDC/SIMADYN D and FM 458-1 DP which are available in CFC.
Installation for The following diagram shows the inter-dependencies of the CFC
SYMADYN D software:
S7 M7 S IM A T IC T D C /
CFC S IM A D Y N D
B o rla n d C / C ++
SCL M 7-S Y S D 7 -S Y S
STEP7
Fig. 2-2: Inter-dependencies of the CFC software in the STEP7 system environment

A5E01078201-02 - Edition 01.2008
CFC
2.1.1.2 Project planning data flow
data flow The following diagram shows the project planning data flow in
SIMATIC TDC/SIMADYN D and the FM 458-1 DP, starting from importing
block type up to loading the machine code into the target system.
Block types CFC charts

CFC Editor Block instances Parameters

Generate
Type code
C sources

Compile and
link
Compile
SIMADYN D SIMADYN D User program

operating block libraries *.BR3
system
Load
SIMATIC TDC / SIMADYN D target system
Machine code
... Sequence
Fig. 2-3: Project planning data flow
Description of the The data flow for the user program of a SIMATIC TDC/SIMADYN D-
SIMADYN D data CPU or the FM 458-1 DP application module is as follows:
flow
1. The block types of the standard block library "FBSLIB" of SIMADYN D
are already included in a newly created chart container.
When required, the user can import the necessary supplementary
libraries.
2. The CFC Editor is used to create charts by inserting blocks (from the
block libraries), and then parameterizing and inter-connecting them.

A5E01078201-02 - Edition 01.2008
CFC
3. The CFC charts are compiled; a user program is generated which can
be loaded.
When compiling, the hardware configuration data of the CPU,
configured in HWConfig, are transferred into the user program.
4. The user program (and if necessary, the operating system) is
downloaded into the target system.
2.1.2 Handling block types
In this section, you will see how you import block types and insert them in
the CFC chart.
• Importing block libraries
• Inserting block types
• Deleting block libraries
The function blocks are organized in block libraries. You import and
delete all block types of a library together.
Within a library, blocks are grouped into block families, which include
blocks which have associated or similar functionality.
2.1.2.1 Importing SIMADYN D block libraries
Standard block The function blocks of the standard function block library "FBSLIB" are
library already imported in a newly created chart container of a D7-SYS
program. When required, additional block libraries can be imported and
are then available in all charts of the chart container.
Procedure This is how you import block libraries:
1. Open a chart of the chart container and select the menu item
Options > Block types.
A dialog box opens with two windows. The block libraries, installed on
your generating system, are listed in the lefthand window "Existing
libraries". The libraries, which have already been imported into this
chart container, are listed in the righthand window "Imported libraries".
2. In the lefthand window, select the library to be imported, and click on
the "Import" button. The selected library is then imported and a dialog
box opens and shows you how the operation is progressing.
Tests The following test is executed when importing a block library:
• A check is made as to whether the library to be imported contains a

block type which was already imported with another library.
Error report If an error is identified when a library is being imported, an error report is
displayed with information on the cause of the error. Select an error line
of the report and click on the "Help text" button to obtain further
information regarding the error cause and how it can be resolved.

A5E01078201-02 - Edition 01.2008
CFC
2.1.2.2 Inserting block types
The chart is open. You will find directories of the block families as well as
the directories "All blocks" (contains all blocks)” and "Other blocks" (for
blocks which are not assigned to a particular family), in the block catalog.
An icon for free text is shown above the directories. Insert the text field
just the same as for a block.
Inserting You can insert the required block from the open directory by dragging it
into the chart.
2.1.2.3 Deleting block libraries
You can delete block libraries using the function Options > Block types.
This function is used for block types which are no longer required in this
particular chart.
NOTE The standard block library "FBSLIB" cannot be deleted.
Procedure This is how you delete block libraries:
1. First ensure that the library which you intend to delete, no longer has
block types which are required in the charts of the chart container.
2. Open a chart of the associated chart container and select the menu
item Options > Block types.
A dialog box is displayed with two windows. The block libraries

installed on your generating system are listed in the lefthand window
"Existing libraries". The libraries which have already been imported
into this chart container are listed in the righthand window "Imported
libraries".
3. In the righthand window, select the library to be deleted and click on
the "Delete" button. Deletion is started and a dialog box opens to
indicate the progress.
Checks When deleting a block library, the following checks are made:
• It is checked as to whether block types, in the library to be deleted,

are used in the charts of the current chart container.
Error report If an error is identified when deleting a library, an error report is displayed
with information on the cause of the error. Select an error line of the
report and click on the "Help text" button to obtain additional information
on the cause of the error and how it can be resolved. Click on the "Go to"
button to jump to the associated function block.

A5E01078201-02 - Edition 01.2008
CFC
2.1.2.4 Updating SIMADYN D block libraries
Procedure This is how you update the block libraries:

1. Open a chart of the associated chart container and select the menu
item Options > Block types.
A dialog box is displayed with two windows. The block libraries,
installed on your generation system are listed with their version
releases in the lefthand window "existing libraries". The libraries,
which have already been imported into this chart container, are
listed in the righthand window "imported libraries".
2. Using the version releases of the libraries in the lefthand and
righthand windows, check for which already imported libraries, a
new version has been installed.
3. In the lefthand window, select the library to be updated, and click on
the "new version" button.
4. An additional dialog box, which has a security prompt is displayed.
Update is initiated if you exit this box by clicking on the "yes" button.
A dialog box opens which displays how the update is progressing.
Checks When updating a block library, the following checks are made:
• It is checked as to whether all of the block types which are used are
still available in the new library version.
• A check is made as to whether block types have changed in the new

version so that it is no longer possible to implement a fully automatic
update.
Those positions, which must be manually edited, are listed in the error
report.
Error report If an error is determined when updating the library, then an error report is
displayed with information on the error causes. Select an error line of the
report and click on the "help text" button in order to obtain more
information on the error cause and how it can be resolved.

A5E01078201-02 - Edition 01.2008
CFC
2.1.3 Editing block inputs
The Manual "CFC for S7 describes in detail how you edit block inputs, i.e.
change the properties of the inputs
2.1.3.1 Additional properties of the block I/Os
In the target system, SIMATIC TDC/SIMADYN D bzw. FM 458-1 DP, I/O

can have additional properties.
Scaling factor An optional scaling factor can be configured at the I/O of the data type
REAL (R), to normalize analog values (define them as per unit values).
The scaling factor is pre-assigned the value 1.0.
Values at the An initialization value can be specified in the "Value" field of the property
outputs dialog box at the block outputs. This value is available at the output if the
associated block was calculated for the first time in the operating mode
INIT.
Pseudo comments Comments at block I/Os, which start with "@", are pseudo comments and
are taken into account when compiling data for the
SIMATIC TDC/SIMADYN D bzw. FM 458-1 DP target system. Pseudo
comments influence the user program function:
@DATX : The input is connected, bypassing the consistency
mechanisms.
@TP_bnnn: Connection is a parameter (with range ID "H", "L", "c" or
"d" and a three-digit parameter number nnn, e. g.
@TP_H089).
@TC_nnnn: I/O is a technology connector (identified by a four-digit
connector number nnnn,
e.g. @TC_0034
on pseudocomments, refer to the SIMADYN D User Documentation:
• "System Software and Communications Configuring D7-SYS" Manual

Section "System Software, Sec. Generating CFC Charts"
• "Communications Communications Configuring D7-SYS" Manual,

Section " Communications Configuring " Sec. "Parameter Access
Technology for D7-SYS"
2.1.3.2 Inverting inputs
It is not possible to invert binary inputs for SIMATIC TDC/SIMADYN D

and FM 458-1 DP (menu item Edit > Invert Input).

A5E01078201-02 - Edition 01.2008
CFC
2.1.3.3 The GLOBAL data type
I/O of the GLOBAL (GV) data type cannot be interconnected. They must
be interconnected with global operands (refer to Section 2.1.4.1).
2.1.4 Block interconnections
The definition and procedure when interconnecting blocks is described in

the Manual "CFC for S7". A description of the system-specific properties
of the interconnection are now described.
Interconnectability For SIMATIC TDC/SIMADYN D and FM 458-1 DP, not only can I/O of
of data types identical types be interconnected, but also:
• REAL (R) and SDTIME (TS)
• INT (I) and WORD (W)
• DINT (DI) and DWORD (DW)
The STRING data I/O of the STRING (S) data type cannot be interconnected, neither to
type each other nor with global operands.
The GLOBAL data I/O of the GLOBAL (GV) data type cannot be interconnected.
type They must be interconnected with global operands (refer to Section
2.1.4.1). GLOBAL I/O which are not connected are flagged as erroneous
during the consistency check or when compiling.
2.1.4.1 Interconnecting to global operands
Definition Global operands are connection partners which are located outside the
CFC charts.
For SIMATIC TDC/SIMADYN D und FM 458-1 DP, communication

aspects as well as linking input/output blocks to hardware addresses are
configured as interconnections to global operands.
Special feature For nested charts all connections to global operands must be routed to
the chart interface. This avoids global operates being defined a multiple
number of times (e.g. $ signals are created a multiple number of times).
Types of global For SIMATIC TDC/SIMADYN D und FM 458-1 DP, a differentiation is

operands made between the following types of global operands:
• $ signals
• virtual connections
• virtual connection names
• OP connections
• hardware addresses

A5E01078201-02 - Edition 01.2008
CFC
• module names
• name references
• process interrupts
Entry dialog boxes Select the block I/O which is to be connected with a global operand and
select the menu command Insert > Connection to operand. Depending
on the block I/O type, CFC opens an appropriate dialog box.
Selection lists in the dialog boxes offer practical entries depending on the
particular context. Further, you can directly enter a name in the dialog
box input field.
You can change the name of a $ signal after you have double-clicked on
the name in the margin.
Entry syntax When entering names, the syntax for the particular global operand type
must be observed (refer to Table 2-6 Name lengths).
Help To obtain information on what you can enter, depress F1 with the entry
dialog box open.
For further information, refer to the help for the function blocks to be
interconnected. To access this help, select the block in the chart and then
depress F1.
2.1.4.1.1 $ signals
Block I/O $ signals can be configured at all inputs and outputs with the exception of
STRING (S) and GLOBAL (GV) data types. They are used to simply
configure interconnections between blocks on different CPUs within a
SIMADYN D station.
on configuring $ signals, refer to the Manual "System Software and
Configuring D7-SYS" .
Bus and type If you "create" a $ signal, i. e. you configure it at a block output, you can
define whether the signal is transferred via the L- or C bus of the subrack,
and which type it is (Standard or Fast).
Contents of the The selection list shows you the already configured $ signals configured
selection list at other CPUs of the SIMADYN D station with which the I/O can be
connected:
• At block outputs, these are all data types, which match $ signals
which are used at block inputs of other CPUs, but which still haven’t
been created.
• At block inputs, these are all data types which match $ signals and
which are created at the block outputs of the other CPUs.

A5E01078201-02 - Edition 01.2008
CFC
Using $ signals, not only can I/O of the same type be connected, but
Interconnectability
also:
of data types
• REAL (R) and SDTIME (TS)
• INT (I) and WORD (W)
• DINT (DI) and DWORD (DW)
2.1.4.1.2 Virtual connections
Block I/O Virtual connections can be configured at all I/O with the exception of
those of STRING (S) and GLOBAL (GV) data types. They are used to
configure communication connections via the "Process data" utility.
on configuring virtual connections, refer to the Manual "System- and
communication configuring D7-SYS".
Virtual connection By specifying a virtual connection name, you establish a reference to a

name transmitter or receiver which transfers the net data of this particular
connection.
Sequence number Using the sequence number, the transmit- and receive blocks arrange the
virtual connections, transferred from them, to the transferred telegram.
Contents of the You are provided with a list of all of the "Virtual connection names" in the
selection list selection list for "Virtual connection name", which were configured at a
transmit/receive block of this particular CPU.
2.1.4.1.3 Virtual connection names
Block I/O Virtual connection names (transmitting and receiving) are configured at
transmit and receive blocks only at data type GLOBAL (GV).
on configuring virtual connections, refer to the Manual "System- and
Contents of the Up until now, you were provided with a list of virtual connection names in
selection list the selection list, which although specified in a virtual connection, have
still not been configured at a transmitter or receiver.

A5E01078201-02 - Edition 01.2008
CFC
2.1.4.1.4 OP connections
Block I/O OP connections can be configured at all inputs and outputs, with the
exception of data types STRING (S) and GLOBAL (GV). They are used
to simply configure connections to SIMATIC OPs.
on configuring OP connections, refer to the “System- and communication
configuring D7-SYS", Section "Communications with SIMATIC Operator
Panels".
OP connection If you generate an OP connection, you must specify a symbol name and
data a flag. For inputs, you can additionally specify an initialization value
(default value).
2.1.4.1.5 Hardware addresses
Block I/O Hardware addresses are configured at input/output blocks. They define
which hardware signal is to be read-in or output from this block.
Contents of the All of the SIMATIC TDC/SIMADYN D station hardware addresses or an

selection list FM 458-1 DP application module and its expansion module (EXM 438-1,
EXM 448), configured in HWConfig, are contained in the selection list
which you can access from the block I/O to be connected. In this case, it
is taken into account whether the associated module can be addressed
from the current CPU and whether the input/output block type
corresponds to the hardware address type.
2.1.4.1.6 Module names
Block I/O Module names are configured at communication blocks. They define the
coupling via which communications is to be established.
on configuring module names, refer to the Manual "System- and
communication configuring D7-SYS"
Contents of the You are provided with a list of all of the coupling modules, which can be
selection list addressed from the current CPU, in the selection list.

A5E01078201-02 - Edition 01.2008
CFC
2.1.4.1.7 Name references
Block I/O Name references are configured at block connections GLOBAL (GV) of
the utility of various communication utilities. They connect several blocks
of the associated utility, which fulfill a common task.
on configuring name references, refer to the Manual "System- and
Contents of the All of the name references, which have already been configured in the
selection list current chart container are provided in the selection list.
2.1.4.1.8 Process interrupts
Block I/O Process interrupts are configured at special blocks block and influence
the handling of process interrupts.
on process interrupts, refer to the Manual "System- and communication
Contents of the You are provided with a list of SIMATIC TDC/SIMADYN D or FM 458-1
selection list DP process interrupts in the selection list. It is not possible to directly
enter other process interrupts.
2.1.5 Run-time properties
A detailed description of the run-time properties and how you can change
these, is provided in the Manual "CFC for S7". You will find some
supplements to the following subjects here:
• Tasks and run-time groups
• Run-time attributes
2.1.5.1 Tasks and run-time groups
Definition For SIMATIC TDC/SIMADYN D and FM 458-1 DP, a task is a cyclic or

interrupt task of a SIMATIC TDC/SIMADYN D CPU or a FM 458-1 DP
which can be configured in HWConfig.
Task structure The structure of a task with run-time group and blocks is illustrated in the
Fig. Chart reference data: Run sequence (in the Manual, "CFC for S7").
Tasks A task contains blocks and optional run-time groups with blocks. The
tasks are specified for the SIMATIC TDC/SIMADYN D and
FM 458-1 DP target system.

A5E01078201-02 - Edition 01.2008
CFC
The properties, which define the run properties of a task, are configured
Run-time
in HWConfig The properties are parameterized under the tab "Basic
properties
cycle", "Cyclic task" and "Interrupt task" of the property dialog boxes of
the CPU modules.
Run-time groups Run-time groups are optional. They are used to structure and sub-divide
tasks. The blocks are sequentially inserted in the individual run-time
groups.
A run-time group is enabled and disabled via run-time attributes.
Order in which the The following is valid for the tasks: The sequence of groups and blocks
tasks are executed inserted within a task, is the run sequence.
The same is true for groups: The sequence in which the individual blocks
are inserted is the run sequence within the group.
You can change the order of execution.
Blocks are not In the SIMATIC TDC/SIMADYN D target system, and for the FM 458-1
inserted a multiple DP, each block must be inserted precisely once. It is not permissible to
number of times insert blocks a multiple number of times in several tasks.
2.1.5.2 Run-time attributes
A run-time group has the following three attributes in the CFC:
Enable
Scan rate (not permissible for SIMATIC TDC/SIMADYN D

and FM 458-1 DP)
Phase offset (not permissible for SIMATIC TDC/SIMADYN D

and FM 458-1 DP)
The group inherits these attributes in all of the blocks which it contains.
The attributes are assigned when creating the run-time group. The
enable attribute can be controlled via an interconnection.
Scan and phase In the SIMATIC TDC/SIMADYN D and for the FM 458-1 DP target system
offset not possible it is not possible to specify different scan rates and phase offset of a run-
time group.
Enable attribute The enable attribute activates or deactivates a group (on=1, off=0). As
long as it is set to 0, the group is not executed, irrespective of all of the
other conditions.
The enable attribute is set to 1 as standard. However, it can also be

dynamically set. In this case, the output value of a CFC block determines
whether the group is to be activated or de-activated. You can
interconnect the binary output of a block with the run-time group for this
purpose.

A5E01078201-02 - Edition 01.2008
CFC
CAUTION Certain blocks (especially communication blocks) may never be

! disabled in the RUN operating mode. This means that they cannot
be configured in run-time groups, whose enable signal is
controlled from a binary output.
Please observe the appropriate instructions in the function blocks

library.
2.1.6 Operator control and monitoring
CFC offers you a user-friendly method to control and monitor variables of

your process or your automation system using WinCC.
The advantage over previous methods is that you no longer have to

individually configure data for each operator station (OS), but you only
have to do it once in the CFC. You can transfer the data generated when
configuring with CFC into the WinCC data administration using the
transfer program D7-SYS-OS Engineering (this belongs to the "D7-SYS"
software package). Data consistency and compatibility with the display
system is also checked. WinCC uses the data in the display blocks and
graphic objects
For SIMATIC TDC/SIMADYN D, you can configure and change the

operator control and monitoring attributes for the block connections (I/O).
Principle When configuring variables which can be controlled and monitored,

procedure proceed as follows:
1. Assign the I/O, which you wish to control and monitor, with the
necessary operator control and monitoring attributes, in a dialog box.
These can include limit values, equivalent values and logging
characteristics, etc.
2. Transfer the configured software data, generated with CFC, to your
display unit (WinCC) using the D7-SYS-OS Engineering.
Name syntax In order that the configured data for WinCC can be saved and
transferred, the D7-SYS OS engineering transfer program automatically
allocates unique names. These are then saved in WinCC.
The name is made up of the following components:

• SIMATIC TDC/SIMADYN D station name
• CPU name
• CFC chart name
• Block name
• Block connection (I/O) name
The names may not include any underlines, blanks or special characters
" ‘ ", ".", "%", "-", "/", "*", "+".

A5E01078201-02 - Edition 01.2008
CFC
2.1.6.1 Configuring operator control and monitoring attributes
In WinCC, each Operator Control and Monitoring-capable connection

(I/O) of a block which has been activated for operator control and
monitoring, can be accessed. Data transfer is always realized using an
instance DB. When configuring, this is automatically assigned to the
operator control and monitoring attributes in the CFC.
Procedure Proceed as follows when configuring operator control and monitoring

attributes of operator control and monitoring-capable connections:
1. Select the block.

2. Select the menu command Edit > Object properties.
3. Activate the "Operator C and M possible" control box in the "special
object properties" area
4. Click on the "Operator Control and Monitoring" button. This allocates
an instance DB to the block. The instance DB is used to establish
communications with the WinCC.
5. You can now enter or change the operator control and monitoring
attribute values in the "Operator Control and Monitoring" dialog box.
NOTE You can obtain additional help by pressing the F1 key with the
"Operator Control and Monitoring" dialog box open.
6. Close the dialog box by clicking on the ”OK” button.

Please observe the following when configuring:
• It is not possible to make I/O operator control and monitoring capable

with CFC in the online mode. If a new I/O for operator control and
monitoring using WinCC is required, the program must always be
newly compiled and loaded!
• I/O of block-type structures, which were generated in the CFC using

nested charts, are not operator control and monitoring-capable!
2.1.7 Compiling and loading
The next two sections describe the following:
• Compiling the user program
• Loading the user program

A5E01078201-02 - Edition 01.2008
CFC
2.1.7.1 Compiling the user program

Interrelationships When compiling the charts for a SIMATIC TDC/SIMADYN D-CPU or an
FM 458-1 DP, observe the following:
• All of the charts of the chart container of a CPU or the FM 458-1 DP

are always compiled in the CFC together with a user program, which
can be loaded and run.
• In this case, all of the block types used are automatically linked-in.
Thus, for the SIMATIC TDC/SIMADYN D target system and FM 458-1
DP, it is not necessary to separately compile and load.
• The hardware configuration of the SIMADYN D station, in which the

CPU is inserted, is also included in the user program.
Thus, it is not necessary to separately compile and load the hardware
configuration for a SIMATIC TDC/SIMADYN D target system and FM
458-1 DP.
• When compiling, the resources of a SIMATIC TDC/SIMADYN D-CPU

and a FM 458-1 DP CPU are automatically assigned. It is not
necessary to make manual interventions to the resource
management.
• The cross-compilers required are invisible to the user and are called-
up by the CFC. The CFC already identifies any configuring errors. You
don’t have to know anything about the cross-compiler.
Prerequisites Before you can compile the charts of a SIMATIC TDC/SIMADYN D-CPU
or a FM 458-1 DP, the hardware configuration of the station, in which the
CPU or FM 458-1 DP is inserted, must be compiled and saved.
Compiling You start chart compilation by entering Chart > Compile > Charts as
program; acknowledge the dialog box using "OK". Compilation is
initiated and a dialog box is opened where you can see how compilation
is progressing.
Compilation scope When compiling, you can select one of two possibilities:
• Scope: Only compile changes

Only those parts of the chart container are compiled, which have been
changed since the last compilation. Thus, when re-compiling,
compilation times can be reduced by approximately 25%.
Note: Even if you only compile changes, all of the charts of the chart
container are checked for consistency (consistency check).
• Scope: Compile everything

The complete contents of the chart container are compiled,
independent of whether the configured software has been changed
since the last compilation.

A5E01078201-02 - Edition 01.2008
CFC
1. When compilation has been completed, you will see a display of the
After compilation
number of errors and warnings which have been identified. You can
open a detailed compilation report using the "Details" button.
2. Select an error line of the report and click on the "Help text" button to
obtain more detailed information about the cause of the error and how
it can be resolved. Click on the "Go to" button to jump to the
associated function block.
3. You can call-up the report at a later time using the menu command
Options > Report; if required you can also print these reports.
Settings for You can make several settings before compiling:
compilation
You can call-up a dialog box using the menu item Options > Settings >
Compilation. This allows you to make the following settings:
• Which directory should be used to save temporary files which are

created during compilation?
e.g. Default: c:\temp
• Should an address book be created, yes or no?

If you activate this option, when compiling, it is guaranteed that the
name syntax of STRUC Version 4.2 is maintained for chart, block and
$ signal names for SIMADYN D This note only refers to SIMADYN D.
• Should a map listing of the user program be created, yes or no?
• Which function block types are to be inserted online in the test mode
of the CFC:
− only already configured block types
− the block types in the "FBSLIB" standard library
− block types from all of the imported libraries
• Is system data (operating system and block libraries) to be taken

from the D7-SYS installation or from the archive (path) in the present
configured software? This means that it is possible to edit older
configured software with the matching system data without having to
adapt the version.
• Should a file be created in which the data of all connections (I/O) or

only the string connections are to be entered?
The appropriate box can be marked under "Create file for:" the
corresponding box can be marked.

A5E01078201-02 - Edition 01.2008
CFC
• Is a compiler other than the integrated GNU compiler to be used?

If you activate the “Use alternative compiler” option, then when
compiling, the integrated gnu compiler is not started – but a batch file
gnu.bat is generated in the selected directory for temporary data
(refer above). All calls of the GNU compiler for the files to be
compiled should be entered into theis gnu.bat file.
In order to use another compiler, these calls should now be adapted
to the compiler that is to be used (prerequisite: MIPS 3 command
set).
The gnu.bat file can then be started with a double click; the program
is compiled and the psw.br3 load object is generated. This load
object can then be subsequently loaded as usual.
If a compiler other than the integrated compiler is used, then this
results in a load object where the user is resposible for ensuring an
error-free function.
Multi-processing It must be ensured that the user programs of all CPUs of a station are
and compilation consistent with respect to one another to guarantee that all of the CPUs
of a SIMATIC TDC/SIMADYN D station run-up and operate together in a
coordinated fashion.
When compiling the user program, a CPU is checked, with reference to $

signals as to whether there are anyinconsistencies with the user
programs of the other CPUs in the station.
NOTE Inconsistencies can occur if you make changes to the configured data
within a station, after you have already compiled the individual CPUs.
After which configuring changes do you have to re-compile a user

program?
• If you changed the charts of this CPU.
• If you changed the station hardware configuration. In this case, you

should re-compile the user program of all CPUs in the station.
• If you removed or changed the name of $ signals at the block outputs.

In this case, all of the CPUs, which use the $ signal, are used.
If you are not certain whether the user program of a CPU must be re-
compiled, then check it using the "Only compile changes" option. If the
user program does not have to be re-compiled, then the CFC will flag this
and will interrupt compilation.
2.1.7.2 Loading the user program
In order to use a user program on a CPU or FM 458-1 DP, it must first be

loaded.
The user program, compiled from the charts of the CPU or FM 458-1 DP,
is loaded into that CPU or FM 458-1 DP which is assigned to the active
chart window. The user program is transferred into the CPU or FM 458-1
DP program memory, but is however still not active.

A5E01078201-02 - Edition 01.2008
CFC
The new user program is activated if the CPU or FM 458-1 DP is re-

started (also refer to Section 2.3.1).
You can either load the user program offline or online.
Offline loading Remove the memory module from the CPU or FM 458-1 DP module,
insert it into the appropriate slot of your PG/PC or external programming
device (OmniDrive or USB-Prommer) and load it offline. This is only
possible for modules, which use a separate memory module (for
example, this cannot be used for the T400 technology module).
Online loading For online loading you connect your PC with an appropriate
communications interface of a SIMATIC TDC/SIMADYN D station
(DUST1 or MPI) or a SIMATIC CPU/SIMATIC CP for a FM 458-1 DP
(refer to Section 2.3.10) and load the user program online.
Depending on the selected communications connection, you can load the

program memory of a CPU/FM 458-1 DP or all CPUs of a station online.
If you have a system-wide MPI bus interface, you can centrally load each
CPU of your system without having to get involved with the wiring or
hardware of your system.
Booting A special procedure is required for the following cases, when loading
online via the MPI bus interface:
• In the boot status (initialization status), i. e. before software is first

loaded, all of the program memories have the same software. Initially,
all stations have the same address, as the addresses of the stations
on the MPI bus are only defined after the user program has been
loaded. In order to establish unique addresses, the stations which you
do not want to load data in, must be disconnected from the bus or
powered-down. You can switch-in another station after loading the
programs of the stations and transferring the new programs into the
working memory (RAM memory) (with a cold restart of the station).
CPU addressing within the station does not pose a problem as it is

realized, slot-related.
• If you modify the hardware of a station, i. e. add, remove or

changeover modules, the station goes back into the boot status where
only reloading is possible; the displays of all of the CPUs of the station
have a flashing "O".
If you change several stations simultaneously, an address conflict will
occur, as in the boot status (initialization status), which must be
resolved as described above.
Prerequisites The prerequisites and conditions for loading the user program depend on
the type of loading technique which will be selected.
The following conditions must be fulfilled to load offline:
1. The user program to be loaded has been compiled, error free.

2. The create mode of the CFC is selected.

A5E01078201-02 - Edition 01.2008
CFC
To load the user program online, the following conditions must be

fulfilled:
1. A memory module is inserted in the CPU to be loaded. The
SIMADYN D operating system is already loaded in this memory
module. You can identify this by the fact that, after the power supply is
powered-up, the 7-segment display of the CPU has a flashing "0"
however, not with a point.
2. There is a communications link between the CPU and your PC

3. The user program to be loaded has been compiled, error-free.
4. The create mode of the CFC is selected.
5. Additional requirements when downloading into a T400-CPU online:
− Switch S1/8 of the T400 has been switched-out
− You have established an online connection between the generating

system and the T400 (serial interface X01, terminals 67 .. 68).

A5E01078201-02 - Edition 01.2008
CFC
You can load the user program as follows:

Procedure
1. Select the menu item PLC > Download...
2. The "Download" dialog box opens.
3. Define the scope of the software to be downloaded:
− Generally, it is sufficient to only load the configured software ("Only
user program") thus reducing the download time. However, if CFC
has identified that the operating system release has changed since
the last time that data was loaded into this CPU or FM 458-1 DP,
then the new release of the operating system is automatically
downloaded.
− If software has still not been downloaded into the CPU

or FM 458-1 DP, you must download the complete software
("system and user program").
4. Specify how the PC can access the program memory:

− During start-up, generally you will leave the memory module with
the user program in the CPU or FM 458-1 DP and select the
"online" option.
− With "offline" you must remove the memory module from the CPU
or FM 458-1 DP and insert it in the appropriate PCMCIA socket or
MMC slot of your PC.
5. To start loading, use the Load function. The CFC responds by

showing how loading is progressing.
6. After loading has been completed, you will find the new user program
in the CPU or FM 458-1 DP program memory and this becomes active
when re-started (cold restart).
NOTE The archived project is deleted when the user program is downloaded
(refer to Section 2.5.1, "Saving a project to be archived on MC"). This
applies both for offline as well as online.

A5E01078201-02 - Edition 01.2008
CFC
2.2 Brief guide
This brief guide is intended for newcomers who have still not had a
chance to get up to speed with the CFC program package. We will show
you a small example where, after starting the SIMATIC Manager, you can
create a project, create a CFC chart, interconnect blocks, compile the
chart and load the software into the target system SIMATIC
TDC/SIMADYN D or FM 458-1 DP and then test it online.
Comment Generally, there are various ways to achieve a goal. However, in this
particular example we only want to show you one, namely the fastest or
best way. Alternative procedures will not be discussed here with just a
few exceptions.
2.2.1 The first steps
So, you want to create a small application, using the CFC, for the
automation system.
You are knowledgeable about the Windows interface of the operating

system; the STEP 7 software package and the CFC software (including
the D7-SYS option package) are already installed.
Power-up your PC or PG and wait until the Windows screen appears on

your display. Now you can start .......
Starting On the Windows screen you will see an icon for the SIMATIC Manager,
the entry into the STEP 7 software.
STEP 7 is started just like a Windows application by double-clicking on

the SIMATIC Manager. The SIMATIC Manager window opens and the
STEP 7 Assistant is also opened. You must acknowledge the STEP 7
Assistant with "Cancel".

A5E01078201-02 - Edition 01.2008
CFC
To start-off with, you will create a project. A project allows you to save the
...the next steps
data and programs, obtained while creating the project, in an orderly
fashion. There is no specified sequence when creating a project, but that
you can see for yourself ....
2.2.2 Creating a project
Set-up a project Firstly, set-up your project structure. Set-up a new project in SIMATIC
structure Manager and open it. You can do this by using the icon in the tool bar:
(new project)
• In the "New" dialog box, select the Path, enter the required Project
name (in this case: "auto_ex") and close the box with "OK".
The project window appears, split into two fields: The project icon with
the project name is shown in the lefthand field and, the contents in the
righthand field, which in this case are: The icon and the name of the
MPI network.
You can now decide whether you first want to set-up the hardware
and then the software or vice versa. If you create the software first,
then after the hardware configuration, you can assign it to a CPU
using drag & drop.
Inserting the We start by inserting a SIMATIC TDC/SIMADYN D station in the project.

hardware
• Select the project container and then
Insert > Station > "Station name"
(Select a SIMATIC TDC station or a SIMADYN D station)
The "Station name" icon is inserted.
• Place the mouse pointer at the selected station icon and depress the
right mouse key. Click on Open object ... in the menu which is now
displayed.
The HWConfig application to configure the hardware now opens. If the

"Hardware catalog" window is not visible, then open it using the icon:
NOTE For more detailed information on configuring the SIMATIC

TDC/SIMADYN D hardware, please refer to the section "Configuring
and parameterizing modules" in the User Documentation "Basis
software for D7-SYS."

A5E01078201-02 - Edition 01.2008
CFC
In SIMATIC Manager you will now see, below the "SIMATIC

TDC/SIMADYN D station the icon D01_P1", the CPU module which you
just configured.
• Click on the "D01_P1" icon to open it.
You will see, that a D7-SYS program has already been assigned to the
CPU. This already contains a chart container "Charts". You will see this
when you open the D7-SYS program.
Inserting the If you open the chart container, you will see that it already has a function
software chart. This is "@SIMD" system chart.
Now, insert your first CFC chart:
1. Select the chart container and then, using the right mouse key
Insert New Object > CFC
2. Now give the chart a new name. The text field of the CFC name is
already selected and the cursor activated.
3. Edit the new name, in this case: "cfc_reg1".
Fig. 2-4: Inserting the new CFC chart in the chart container
Thus, the project structure has been set-up, and a chart created. Blocks
must now be inserted into this chart and interconnected so that a control
task can be implemented.

A5E01078201-02 - Edition 01.2008
CFC
2.2.3 Starting CFC and inserting blocks
Preliminary Before we really get going, we should first briefly discuss what will be
comments configured in this chart.
Configuring This configuring example involves a basic oscillation circuit, which

example generates a sinusoidal oscillation at its output. You can create this chart
yourself in just a few minutes which you can then run as demonstration in
the test mode.
You use two block types:
• 2 integrators (INT)
• 1 subtractor (SUB).
The oscillation circuit (according to the differential equation f"(x) = - f(x) )

is formed using two integrator blocks with feedback via a negation
function.
The frequency of the oscillation circuit is defined by the integral action

time of the integrator.
The amplitude of the oscillation is determined by the initial value at the

integrator output.
Opening the CFC By double-clicking on the chart icon, you can open the chart and implicitly
chart start the CFC Editor.
The CFC window is opened. The chart window and the block catalog are
located in the CFC window. The block catalog can be switched-in and
switched-out using the following symbol.
(catalog)

A5E01078201-02 - Edition 01.2008
CFC
You can position the block catalog anywhere on the screen.

Block catalog
Fig. 2-5: Block catalog
You can use the blocks of the standard library "FBSLIB", supplied with
the system, to configure the CFC chart.
Open the "Closed-loop control" family of control blocks.
Select the INT block and drag it, with the left mouse key depressed, into
the chart. The block outline will be represented as a dotted line. Release
the mouse at a suitable position. The block will be displayed in the chart
with its real size.
Place a second copy of the INT block next to the first.
Now you should look for the SUB block. Enter the SUB name (in upper
case letters) in the entry field of the block catalog, and click on the
"Binocular" icon (field glasses). The search starts and the SUB block is
quickly found which is included in the "Arith." family.
As before, drag this block to a free location in the chart.

A5E01078201-02 - Edition 01.2008
CFC
If your chart was displayed as an overview. Click in a free location in the

Go into the page
chart using the right mouse key and in the context menu in page view. In
view
this zoomed display you will also see the block connection designations
(I/O connections).
2.2.4 Interconnecting blocks
Interconnecting We now come to interconnecting.

blocks
• Select output "Y" of the lefthand INTegrator and then input "X" of the
righthand INTegrator.
• Select output "Y" of the righthand INTegrator and then input "X2" of
the SUBtractor.
• Select output "Y" of the SUBtractor and then input "X" of the lefthand
INTegrator.
The autorouter has already drawn the connecting lines from the outputs
to the inputs; the I/O are interconnected.
2.2.5 Editing blocks
We will now parameterize the blocks which we interconnected and

change the sequence in which they are executed (run sequence).
Changing the run Select the menu item Edit > Run sequence...
sequence
The "Run sequence" dialog box is displayed: You will see the task
structure in the lefthand window; the contents are displayed in the
righthand window. The default location of the block is in the highest
priority cyclic task T1.
We now want to shift the block, just inserted from task T1, into the lower-
priority task T3.
• Double click on the "T1 [cyclic task]" icon.
The blocks (including chart/block name, comments and position) are

displayed in the righthand window. Select all three of the blocks, and
drag these to the cyclic task "T3" icon in the lefthand window. The
righthand window is now empty. If you open "T3 [cyclic task]", the
three blocks are now displayed there.
• Close the dialog box with Chart > Close and then proceed to the next
step.
Parameterizing The limit inputs of the integrators must now be supplied with other values.
inputs You can now do this, individually for each input, by double-clicking and
calling-up the dialog box "Properties - I/O" or you can take the easier
route:

A5E01078201-02 - Edition 01.2008
CFC
• Double-click on the lefthand "INT" block.
The "Block Properties" dialog box opens and then you can select the
"I/O" tab. The parameters in the fields with grey background, cannot
be changed.
In the table, first go to the "Values" column, and change as follows:
• LL: From "0.0" to "-10.0" (the lower limit value)
• LU: From "0.0" to "10.0" (the upper limit value)
• TI: From "0ms" to "500ms" (the integrating time constant)
• In the "For test" column, highlight the input, which is later to be

monitored in the test: Y.
• Close the dialog box with "OK".
Double-click on the right "INT" block and enter the same value as at the
lefthand INT block. Also change the initialization value at the block
output:
• Y: From "0.0" to "10.0" (the initialization value of the output)

The block output has this value when the block is first executed
The "SUB" block doesn't require any values to be changed. It acts as

negation element when it has the default value 0.0 at its input X1.
Help for the block If you require more detailed information on a block, then select it and
types press F1.
Thus, our small example has now been configured and the chart can be
compiled and loaded.

A5E01078201-02 - Edition 01.2008
CFC
2.2.6 Compiling and loading into the target system
Compiling The graphically-created chart must now be compiled into the machine
code of the SIMADYN D target system.
Click on the tool bar:
(compile)
The "Compile" dialog box is displayed with the following entries:

Target system: SIMADYN D
CPU: 1 D01_P1
In the "Scope" field, you can now select whether the complete chart
container ("Compile everything") or only the changed objects ("Only
compile changes") should be re-compiled. In this case, we wish to
"Compile everything".
Compilation is initiated with "OK".

The new dialog box is displayed. The compilation progress is displayed in
the new dialog box.
Consistency check Before actual compilation, the system automatically executes a

consistency check. Before compilation, if you wish to check whether
compilation makes sense, you can first execute this consistency check
with Chart > Consistency > Charts as program.
...after compilation A dialog box with the "Compilation error-free" message is displayed after
compilation.
Compilation has now been completed and the user program, which can
be loaded has been generated. In a next step, you can load the program
into a memory module for the SIMADYN D CPU.
Insert the memory Insert a SIMADYN D memory module into the PCMCIA slot ("socket") No.
module in a PC 1 of your PC or in the OmniDrive (external PC card drive).
Loading In the tool bar, click on
(load)
Select "System and user program" loading as scope in the "Load" dialog
box; and, "offline (OmniDrive)" as loading type. Start loading with "Load".
The user program and the operating system of the CPU are loaded into
the memory module.
Starting the CPU Insert the memory module, which was just loaded, into receptacle X01
(module receptacle) of your SIMATIC TDC/SIMADYN D CPU and power-
up the subrack.

A5E01078201-02 - Edition 01.2008
CFC
The CPU runs-up and after a few seconds, CPU number "1" appears on
the display.
2.2.7 Monitoring and changing in the test mode
Testing the In the test mode, you can monitor the values of the block connections
program (block I/O) and you can change the values of the block inputs. The
values, registered for test, have a yellow background.
You can easily monitor the control characteristics by changing several

parameters, for example, how the manipulated value approaches the
setpoint and stabilizes.
Changing-over into Before you change over into the test mode, select the test mode
the test mode "Laboratory operation" with Test > Laboratory operation. This means
that all of the block connections (I/O), registered "for test" will be
automatically switched-in for "monitoring".
NOTE In the “process mode” no connection is preset for monitoring. In this

test mode, you must mark the appropriate blocks and explicitly register
them for monitoring.
Activating the test Activate the CFC test mode:

mode
Click on the icon in the tool bar:
(Testmodus)
• or select Test > Test mode
In the status line, the text in green "Text: RUN (laboratory)" is displayed.
Monitoring You can now see your oscillation circuit working, i. e. how the values of
the connections, selected for the test, change. The values of the I/O have
a yellow background.
Change input value In the test mode you can also change all of the values at the inputs which
have not been interconnected. If you want to see how the characteristics
change when a value is changed, enter "5000ms" as integration time at
the lefthand INT block.
• Double-click on input "TI".
The "Properties - I/O" dialog box opens. Change the value for the
block input and acknowledge the new value with "OK".
In the chart, you can now see how the "Y" output changes significantly
slower as a result of the new input.

A5E01078201-02 - Edition 01.2008
CFC
• Select input "X2" of the SUB block and remove the interconnection
Deleting
with Edit > Delete.
interconnections
The interconnections between the output of the righthand integrator
and the SUB block is deleted, thus interrupting the oscillation circuit
feedback.
In the chart, you can now see how the input- and output values of the
blocks remain stationary.
Re-establishing • Select output "Y" of the righthand INTegrator, using the lefthand
interconnections mouse key, and then input "X2" of the SUBtractor.
The interconnection between the output of the righthand integrator

and the SUB block is re-established.
In the chart, you can now see how the values start to change again.
Insert and delete In the CFC test mode, you can insert additional function blocks online in
blocks the chart and interconnect them with already configured blocks (offline).
De-activate test To return to the create mode, deactivate the test mode. Click on
mode
(test mode)
The create mode is now re-activated.
2.2.8 Generating documentation and closing project
Complete Your example has been successfully configured and debugged (tested).
documentation You can now generate a complete set of documentation for this small
example.
Chart reference The chart reference data in this case are the "Cross references block
data types" and the "Run sequence". On the tool bar click on
(Referenzdaten)
You can now generate and display the appropriate lists, using the icons
in the tool bar in the dialog box "Chart ref: Display chart reference data".
You can then print these lists
(print)
Then close the dialog box with Reference data > Exit.

A5E01078201-02 - Edition 01.2008
CFC
You also wish to print the chart. Only one page was used on this chart.
Print chart
This is the reason that we recommend the single-sheet print-out. The
chart is still set to "Page view". You can now start printing:
(print)
Close The project has now been completely created; you can now close the
CFC Editor with Chart > Close. The CFC window is closed..
You can close the SIMATIC Manager with File > Close
The window of the SIMATIC Manager is closed and you return to the
Windows screen.

A5E01078201-02 - Edition 01.2008
CFC
2.3 Testing and commissioning
Before you can commission the complete software structure, you must
test its functionality in detail. To support commissioning, functions are
integrated in the CFC Editor to monitor values online and to make
corrections in the loaded software. These functions are described in this
Chapter.
Editing modes The CFC Editor has two edit modes:
• The create mode to configure charts
• Test mode to test and commission the configured user programs.
Menus The functions of the CFC Editor for commissioning and test are provided
in the two menus PLC and Test. With the PLC options, you can display
and change the status of the CPU presently being processed. With the
options of the Test (debug) menu, you can directly influence the CPU
program (at the target software).
Function groups The functions for test and commissioning can be sub-divided into the
following main groups:
• Functions when preparing for testing are:
– Loading the user program into the CPU (refer to 2.2.6)
– Viewing and changing the operating mode
– Checking that the configured software and CPU program match
– Changing the refresh rate for monitoring
– Working in the test mode
• Display functions for the CPU

The CPU supports you for system diagnostics by saving information
about errors which have been identified. This is realized without any
specific configuring work having to be done. This allows you to
quickly identify and remove errors. When a fault condition occurs,
standstill times can be significantly reduced.
You can obtain information on the system diagnostics using the
functions of the PLC > Module information.... menus
• Monitoring and parameterizing block I/O
You can monitor the values of all of the block I/O during operation
and change the parameter values at the block inputs online.
• Creating and deleting interconnections:

In the automation system you can create or delete interconnections
between block I/O online.

A5E01078201-02 - Edition 01.2008
CFC
• Inserting and deleting blocks:

In the automation system you can insert and delete blocks into the
CPU program which is running, online.
2.3.1 Viewing and changing the operating mode
Operating modes A SIMATIC TDC/SIMADYN-D-CPU or an FM 458-1 DP can have various

operating modes:
• Power off
In this mode, the system is not operational (it is powered-down). The
seven-segment display and LEDs are dark; communications with the
CPU or the FM 458-1 DP cannot be established.
• INIT
In this mode, the system initializes itself (runs-up). The seven-
segment displays indicates "0" or the RUN LED flashes;
communications with the CPU or FM 458-1 DP cannot be established.
After this mode, the system goes into the following modes.
• RUN
This is the standard operating mode. The CPU or the FM 458-1 DP
processes the configured user program. The status display shows the
CPU number ("1" ... "8") or an error code "C", "E", "b" or "A". For an
FM 458-1 DP, the RUN-LED is bright or one of the fault LEDs (CF, TF,
MF, UF) is bright. In this mode, the CPU can be accessed online via
the local service interface and the configured service interfaces.
An FM 458-1 DP can be accessed, online via the SIMATIC CPU or an
appropriate SIMATIC CP.
Using the "Cold restart" or "Stop" commands (refer below), it is
possible to go into the INIT mode or user stop mode.
• User stop
The CPU or FM 458-1DP only goes into this mode, if an explicit stop
command is issued (refer below). A seven-segment display indicates
"d" or the STOP LED of the FM 458-1 DP is bright.
for two CPUs: CPU with user stop: "d2 flashes

other CPUs: "d" is continuously displayed
This mode is used to quickly load the user program into the CPU.
Fast means that in this mode, cyclic processing (execution) is
stopped, and the complete computational performance of the CPU or
FM 458-1 DP is available for loading (STOP LED flashes for FM 458-1
DP). Loading can be realized via the local service interface or via the
configuring service interfaces for FM 458-1 DP via SIMATIC CPU or
SIMATIC CP.
Using the "Cold restart" command (refer below), it is possible to enter
the INIT state.
• STOP due to initialization error

The CPU or FM 458-1 DP goes into this mode, if an error is identified
in the INIT mode where it does not make sense to go into the RUN
mode. An "O" or the STOP and IF LED of the FM 458-1 DP are
displayed on the 7-segment display. In this state, the local CPU

A5E01078201-02 - Edition 01.2008
CFC
service interface as well as the initialization interface are available for

loading and for fault diagnostics. For an FM 458-1 DP, the interface of
the SIMATIC CPU or a SIMATIC CP can be used. It is possible, to go
into the INIT mode by issuing a "Cold restart" (refer below) command.
• STOP due to system errors

The CPU or FM 458-1 DP goes into this state, if a fatal error was
identified in one of the other states, so that the system should not go
into another operating state. An "H" or the STOP and INTF-LED of FM
458-1 DP are displayed on the 7-segment display. In this state, only
the local service interface is available for loading and error
diagnostics. For the FM 458-1 DP, in this state, the interface of the
SIMATIC CPU or a SIMATIC CP can be used. It is possible to go into
the INIT state by issuing the "Cold restart" command (refer below).
For SIMADYN D, it is not possible to change thestate of individual CPUs

for SIMATIC TDC/SIMADYN D, due to the tight coupling between the
CPUs; a mode change always involves the complete station.
Prerequisites You can restart the SIMATIC TDC/SIMADYN D station or an FM 458-1

DP by either issuing a command from the PC, as described in the
following, switching the power supply voltage off and then on again or
activating the reset signal of the subrack power supply.
If you wish to view the operating mode and change it using CFC, then the
following conditions must be fulfilled:
• There must be a communications link between a CPU of the current

station and your PC
• The create mode must be selected for all CPUs.
Procedure If you wish to view and change the operating mode using CFC, then
proceed as follows:
• Select the menu item PLC > Operating Mode ...; the associated
dialog box is displayed.
• Press the "Cold restart" button if you wish to bring the station into the
INIT mode; the "Stop" button, if you wish to change from the RUN into
the user stop mode.
For SIMATIC TDC/SIMADYN D, the CFC responds with a progress

display. After a short time, you can see at the station that the 7-
segment displays of all of the CPUs inserted in the station have a new
value.
For an FM 458-1 DP, the appropriate change of state is displayed in
the same dialog box. The LEDs of the FM 458-1 DP also indicate this
change of state.
After the state change, the PC re-attempts to establish a
communications link to the current CPU for SIMATIC TDC/SIMADYN
D and displays the new mode.

A5E01078201-02 - Edition 01.2008
CFC
(only for SIMATIC TDC/SIMADYN D):

Please observe
The interface assignment can change due to a state change. For
instance, if you enter a restart command, in the "Stop due to user error"
mode, via the initialization interface, then this has its configured function
after restart and transition into the RUN mode.
Recommended Configure a service utility at the initialization interface, to be able to test

configuring and load using the CFC via the initialization interface, also in the RUN
mode.
2.3.2 Checking that the configured data and the CPU program match
After loading the configured software the last time, changes could have
been made, either in the CPU or FM 458-1 DP or in the CFC Editor
(offline).
Thus, before you start testing (debugging) or commissioning the system,

you should check that the configured software and program in the target
system match.
Prerequisites This check can be executed under the following conditions:
• There is a communications link between the CPU or FM 458-1 DP

and your PC
Procedure Select the menu item PLC > Compare .... The "Compare" dialog box
opens. The CPU number, CPU name and the date of the last compilation
are specified and compared with one another. The configured software
and program in the target system are only consistent if the appropriate
parameters are the same. In addition, a check is made as to whether
online changes were made using another start-up tool, bypassing the
CFC, or if offline changes were made, in the configured software.
NOTE If the configured software and program in the target system are
inconsistent, you can only activate a restricted level of test operation,
where it is only possible to view and change parameter values.
2.3.3 Changing the refresh rate for monitoring
The CFC Editor periodically interrogates the SIMADYN D CPU for the
latest I/O value so that the values can be dynamically updated. The user
can set this scan time.
If values are not refreshed within 300 % of this time, for example,
because the data transfer capacity of the communications link is not
sufficient, or the computation performance of your PC is being fully
utilized, then the values which have not been refreshed, are flagged as
being faulted (refer to Section 2.3.6).
In this case, you should either reduce the number of registered values or
increase the refresh period.

A5E01078201-02 - Edition 01.2008
CFC
If you wish to change the refresh rate for monitored values, then proceed
Procedure
as follows:
• Select the menu item Debug > Test Settings ...; the associated
dialog box is displayed with a field for the refresh period, which can be
edited.
• Enter new refresh periods in tenths of a second or select a new value

using the arrow keys.
• Press the "OK" button; the refresh period then becomes valid for all
values of the current CPU.
2.3.4 Activating and de-activating the test mode
Before you can view (monitor) values in a CPU or FM 458-1 DP, or make
online changes, you must select the CFC test mode. The test functions
can only be activated after first changing into this mode.
In the test mode, only changes can be made in the configured software,
which can be implemented and realized online. This is the only way to
ensure that the assignment of objects in the configured software match
that of the objects of the program in the target system. Further you can
also make changes which only refer to the screen display and do not
influence the program, e. g. shifting blocks. These basic functions can be
activated both in the test- as well as in the create mode.
The test mode refers to the CPU or FM 458-1 DP, which is associated
with the currently active chart. The test mode must be individually
enabled or disabled for every CPU or FM 458-1 DP being processed in
the CFC Editor.
Changing between When changing into the test- or into the create mode, the CFC still views
the test- and the current chart.
setting mode
When changing into the test mode, it is checked as to whether the current
status of the configured software matches the change release of the
program. If this is not the case, for example, because you changed the
configured software in the CFC create mode since the last load of the
program, then the appropriate message is displayed. You can now
activate restricted test operation (debugging) (only "monitoring") where
you can only view and change parameter values.
Changes in the test All of the changes made in the CFC test mode, are immediately and
mode permanently changed in the change memory (presently, EEPROM) of the
SIMATIC TDC/SIMADYN D CPU or the FM 458-1 DP; i. e. when the CPU
or the FM 458-1 DP is reset, these changes are kept. If the CFC system
crashes in the test mode, then in order to achieve a consistent status, the
program must be re-compiled and loaded. The changes which you made
up until the system crashed, still remain effective.
If the change memory is full or defective, structural changes (blocks

deleted, connections changed) are locally made in the RAM of the CPU
or the FM 458-1 DP; however, they are not saved. This results in

A5E01078201-02 - Edition 01.2008
CFC
inconsistencies with the configured software in the CFC. (For example, in

the CPU or the FM 458-1 DP, the connection is changed, but not in the
CFC.
• Remedy for a full change memory: Re-compile the configured

software in the CFC and load the memory card.
• Remedy for a defective change memory:

Replace the memory card or reset the subrack.
Test-operating There are two test operating modes:

modes
• Process mode
In the process mode, the communications of the online update for the
blocks is limited in order to only slightly additionally load the PC and
bus. When switching-in the test mode, all of the blocks have the
"monitoring off" status. In this test mode, you must select the
associated block I/O and explicitly register them for monitoring.
• Laboratory operation
The laboratory mode is selected to be able to efficiently test and
commission the system in a user-friendly fashion. In the laboratory
mode, contrary to the process mode, communications of the online
update for the CFC charts is not limited. When switching-in the test
mode, all of the blocks have the "monitoring on" status.
The test mode can be selected in the create mode using the menu
commands in the "Test" menu. Changeover is not possible in the test
mode.
Activating the test The test mode is activated. A check mark is displayed next to the menu
mode item. Depending on the selected test mode, the text "test: RUN
(laboratory)" or "Test: RUN (process mode)", with green background is
displayed in the status bar. All of the menu functions, which are not
permitted in the test mode, are de-activated (light grey font).
NOTE If you made changes offline, or online using another start-up tool,
bypassing the CFC, the "Different software release" dialog box is
displayed. In spite of the fact that it is a different software release, this
still allows you to changeover into the test mode.
CAUTION If you go into the monitoring mode, in spite of the different software
! releases, CFC can occasionally indicate erroneous situations, as the
displayed parameter values, blocks and interconnections may not
match with those in the target system.
De-activating the This is how you de-activate the test mode:

test mode
• Select the menu item Debug > Test Mode

A5E01078201-02 - Edition 01.2008
CFC
The test mode is de-activated; the check mark next to the menu item and
the text in the status bar disappear.
This is how you activate the test mode:
• Select the menu item Test > Test Mode
2.3.5 Module status
During operation, and especially during start-up, the CPU or the FM 458-
1 DP can identify an error condition of the configured system, e. g. if the
task cannot be calculated in one sampling time, because higher-priority
tasks fully utilize the available time. These statuses, which are also
generally identified by the appropriate 7-segment display value of the
CPU or using an appropriate LED display for the FM 458-1 DP, can be
analyzed using the "Module status" function.
Further, when the CPU or the FM 458-1 DP goes into the STOP
operating mode due to a system error, it records the cause of the crash
(the "exception") with information about the internal state. This
information is available after restart.
Prerequisites The prerequisites to determine the module state is that you have first
done the following:
• There is a communications link between the CPU or the FM 458-1 DP

and your PC.
• The create mode is selected.
You can display the error fields of a CPU or the FM 458-1 DP as follows:
• Select the menu item PLC > Module Information....
• The dialog field "Module information" is opened
• Select the tab page "Error fields".The tab page "Error fields" is
opened.
The contents of the internal error field of the current CPU or FM 458-1 DP
are displayed as text here on the page under this tab.
Displaying crash They indicate the exceptions as follows:

conditions
• Select the menu item PLC > Module Information....
• The "Module information" dialog box is opened (module status).
• Select the "Exception buffer" tab. The page under the "Exception
buffer" tab opens.
The contents of the internal exception buffer of the current CPU or

FM 458-1 DP are displayed as text on the page under this tab.

A5E01078201-02 - Edition 01.2008
CFC
2.3.6 Monitoring block I/O
Connections (I/O) which have been registered for test, are supplied, in
the test mode with the actual values from the CPU or FM 458-1 DP if
"monitoring" is enabled for these I/O.
Prerequisites The "Monitor block I/O" function can only be executed under the following
conditions:
• There is a communications link between the CPU or FM 458-1 DP

and your PC.
• The page view of the chart is activated.
• The test mode (laboratory or process mode) is selected.
Monitoring in the When the test mode is switched-in, for CFC charts in the ”Laboratory
"Laboratory mode"
mode”, the "monitoring on" function is also activated.
This means, that in the test mode, you can display how the values of
those block I/O develop, which were registered for display. This means
that the values are cyclically read-out of the CPU or FM 458-1 DP and
are displayed. You can change the options for this dynamic value display
and the parameters of the I/O in the test mode.
Monitoring in the
"Process mode" In the "Process mode", the "Monitoring off" function is activated. This
means, that to dynamically update, you must first select the blocks (select
them in the chart) which you wish to monitor; then select "monitoring on".
Vice versa, for an overload condition, you can exclude individual blocks
from the monitoring function (select the block and select the menu
command "monitoring off").
Caution:
If monitoring is switched-out and you select a connection and register this
for test via , then monitoring is switched-in for this connection and for
all previously registered connections of this block.
When the test mode is switched-in, the connections to the CPU or FM

458-1 DP are established for all listed connections of a value display
window. You can activate ”Monitoring” by marking the individual
connections in the ”Monitoring” column.
Registering/de- In the create mode or in the test mode (process or laboratory operation),
registering you can register individual block or chart connections for test, by
connections for selecting the connection and selecting the menu command Test >
test
Register connections or you can click on the icon in the function
bar.

A5E01078201-02 - Edition 01.2008
CFC
In the test mode, monitoring is simultaneously switched-in, i.e. the

connection has a yellow background and is displayed with its actual
value. If monitoring was switched-out for this block, then all of the
connections, which were previously registered for test, are also switched-
in for monitoring.
You can de-register the connections by selecting the connection and

selecting the menu command Test > De-register connections or you
can click on the icon in the function bar.
NOTE Alternatively: In the create mode, you can register and de-register all
of the block connections for test if you call the "object properties" for a
selected block and in the "connections" tab in the "For test" column, set
or reset the marking of the individual connections.
Connections, You switch-in monitoring (to display the actual value of the connection)
switching- for the block connections, registered for test, as follows:
in/switching-out
monitoring • Automatically when the test mode is switched-in in the laboratory
mode.
• With the menu command Test > Monitor on or using the icon in
the function bar. In the laboratory mode, this function applies for all
blocks; in the process mode, only for the blocks previously selected in
the chart.
• By selecting the menu command Test > Monitoring off or using the
icon, you can disable the monitoring function, i.e. the connection
values are not longer updated.
In the laboratory mode, this applies for all blocks; in the process
mode, only for the blocks selected in the chart.
All of the input and output values, switched-in for monitoring are updated
according to the set monitoring cycle.

A5E01078201-02 - Edition 01.2008
CFC
The values are output next to the connections corresponding to their data
Representation of
type. They are shown on the screen with colored background (refer to
the dynamic value
Table 2-1).
display
Blue on white Values displayed in the create mode (offline)
Black on yellow, stars Values displayed during the changeover to
dynamic value display
Black on yellow, value Values read-out of the CPU/FM 458-1 DP
displayed in the test mode
#### on a red background Values, requested from the CPU/FM 458-1
DP and which are not available, are
displayed (error condition)
Table 2-1 Displaying values in the CFC Editor (pre-setting)
2.3.7 Parameterizing block I/O
An important task at start-up (commissioning) of a control system is

optimizing the control parameters, i. e. setting the correct parameter
values at the block inputs.
With this function, you can change the values at the inputs of the blocks
during operation and simultaneously monitor the effects in the control
process.
CAUTION Please observe that death, severe bodily injury or significant

! material damage can occur if changes such as these are made
with the system connected to the process and without having
taken the appropriate precautionary measures.
Prerequisites The "Parameterize block I/O" function can be made under the following
conditions:
• There is a communications link between the CPU/FM 458-1 DP and

your PC.
• The test mode is selected.
Procedure In order to change an input (not connected) then proceed as follows:
• Double-click on the input which is not connected, and whose value

you wish to change. The dialog box "I/O properties" is displayed.
• Enter the required parameter value in the "Value" input field.

• By pressing the "OK" button, the value is transferred into the working
memory of the CPU/FM 458-1 DP and into the configured software.
The dialog box is then closed.

A5E01078201-02 - Edition 01.2008
CFC
NOTE The default for the output value cannot be changed online. This is also
true for function blocks which have been newly inserted.
2.3.8 Creating and deleting interconnections
For SIMATIC TDC/SIMADYN D/FM458-1 DP, you can make changes to

the control structure during operation; this also includes "Creating and
deleting interconnections".

Prerequisites The "Creating and deleting interconnections" function can be executed

under the following conditions:

your PC.
• The configured software and CPU/FM 458-1 DP are consistent.
Creating To interconnect an input, which was previously not connected, to an

interconnections output, proceed as follows:
• In the chart, using the left mouse key, mark the output which you wish
to interconnect to the input; the color of this output changes.
• Position the mouse pointer in the chart to the input which up until now
has not been interconnected and which you now wish to connect.
Depress the left mouse key. The interconnection is now displayed as
a line in the chart. At the same time, a data connection is established
between the I/O in the working memory of the CPU/FM 458-1 DP.
Deleting To remove an interconnection between an input and an output, proceed

interconnections as follows:
• Select the block input in the chart, which you wish to remove and then
delete the interconnection with Edit > Delete.
The connecting line between the connections disappears, and the last
value, which was transferred at the data connection, is displayed as
parameter value at the input.
NOTE: Interconnections to global operands can neither be created online

nor deleted online.

A5E01078201-02 - Edition 01.2008
CFC
2.3.9 Inserting and deleting blocks
For SIMATIC TDC/SIMADYN D/FM 458-1 DP, you can make changes to
the control structure during operation; this also involves "Inserting and
deleting blocks".

Prerequisites This function can be made under the following conditions:

your PC.
• The block catalog is open (menu item View > Catalog)
Inserting blocks To insert blocks online, proceed as follows:
• In the block catalog, select the required block type, and with the left
mouse key, drag it to the required position at a free location in the
chart.
• The block is simultaneously inserted in the software as well as in the

working memory of the CPU/FM 458-1 DP at the standard insertion
position of the run sequence.
Note Some block types cannot be inserted online. If these block types are
selected, an error message is output.
Deleting blocks In order to delete blocks online, proceed as follows:
• Remove all connections from the outputs of the block to the inputs of
the other blocks. Proceed as described in Section 2.3.8. Connections
to global operands do not have to be deleted.
• Position the mouse pointer in the chart at the block to be deleted and
press the right mouse key. A pop-up menu is displayed.
• In this pop-up menu, select the item "Delete", the block is deleted from
the chart and is no longer processed in the working memory of the
CPU/FM 458-1 DP.

A5E01078201-02 - Edition 01.2008
CFC
Proceed as follows to change the number of I/O of a generic block online:

Changing the I/O
number of generic
blocks • Position the mouse pointer in the chart at the associated block and
depress the righthand mouse key. A pop-up menu is displayed.
• In this pop-up menu, select No. I/O ...; a dialog box is displayed in
which you can select the required number of block I/O.
NOTE It is not permissible that a connection has been registered for

monitoring. Generic blocks are, e.g. adders and multiplexers.
2.3.10 Communication interfaces
For SIMATIC TDC/SIMADYN D, you can structure the communication

links between the PC and CPU in several ways.
The local service interface of the CPU (front panel connector) is

provided by the system (and is therefore always available). This serial
interface permits communications with the CPU itself in the operating
mode STOP after fatal system errors ("H" on the CPU display).
For a single-processor system (e. g. T400) this is the only interface for
test and start-up. If this interface is to be used to load and test (debug)
multi-processor systems, then the connecting cable must always be
inserted at the actual CPU.
Thus, to test multi-processor systems, we recommend a configured

service interface. This allows the service connection for a complete
station to be made available at one or several communication interfaces.
System-wide bus operation for test and start- up (commissioning) is
possible if an SS52 MPI module is used as interface module for this
connection instead of the serial SS4 module.
Even when first commissioning a station, you are not limited to just a
local interface. Communications via the so-called initialization interface
is possible as soon as there is a certain level of harmonization between
the CPUs of a station (this can be identified by a "0" on the CPU display)
(only for SIMADYN D).
For example, the CPU programs for a complete station can be loaded
online via this interface, without having to changeover cables.
For the FM 458-1 DP application module, the communications link

between the PG/PC and the module is always established via the
interface of a SIMATIC CPU or a SIMATIC CP in the same rack (as is
usual for SIMATIC).
Local service When using the local service interface, this must be connected with a free
interface serial interface of the PC (COM1 or COM2).

A5E01078201-02 - Edition 01.2008
CFC
How a configured service interface is handled, depends on whether a

Configured service
serial SS4 module or an SS52 MPI module is used for the interface.
interface
If an SS4 interface is used, this should be connected with a free serial
interface of the PC (COM1 or COM2).
The connecting cable uniquely defines the station to be addressed and

the SS4 interface to be used.
When an SS52 or CP50M0 MPI interface is used, the station cannot be

uniquely defined, as several SS52 MPI connections of a single station
can be connected to the same bus. The configured software can tell you
which MPI connections have been configured for the station, but the PC
does not know which of these connections it should use.
In this case, the PC checks all of the configured connections one after the
other, until it can establish a communications link to the "Service" utility of
the CPU. The PC can then use this connection for communications.
NOTE In order to access a CPU via the configured service interface, you must
include an appropriate service utility function block in your configured
software.
If you require more information, refer to the Chapter "Service utility" in
the User Documentation "System- and communication configuring D7-
SYS".
Initialization The initialization interface is always the top connection of the CS7
interface module which is inserted at the far left in the subrack. To be used as
initialization interface, either an SS4 module or SS52 module must be
inserted here. This connection can only be used as initialization interface,
as long as the CPUs of the station are in the operating mode "STOP due
to an initialization error".
Creating The connection between the CFC and the "Service" utility of a CPU/FM
connections 458-1 DP is essentially automatically established. You must only insert
the serial connecting cable at the correct SS4 module and at a free serial
interface on the PC (COM1 or COM2) or the MPI bus cable at the
appropriate SS52/ CP50M0 module or the appropriate SIMATIC CPU for
FM 458-1 DP and at the PC MPI port.
Selecting the You tell the CFC which communications interface is to be used. To do
communications this, start the program via the Windows 95/NT task bar Start > Simatic >
interface STEP 7 > Set PG/PC interface and select the right alternative. This
selection is kept even after you power-down your PC.
Setting the MPI You must set the correct operating parameters of the MPI interface at
interface your PC if you wish to establish an online connection via the MPI
interface. Refer to the help info for the dialog box to obtain information as
to how you should proceed.

A5E01078201-02 - Edition 01.2008
CFC
The baud rate for the MPI interface must coincide with the coupling
partner.
NOTE The maximum baud rate for the particular protocol may not be
exceeded.
Checks when When establishing a connection in the test mode and changing the CPU
establishing a mode, the CFC checks whether it is connected with the correct CPU/FM
connection 458-1 DP; if this is not the case, the connection is canceled and an
appropriate message is output.
When establishing the connection for online loading, the CFC checks
whether it is connected with the correct CPU/FM 458-1 DP; if this is not
the case, you are prompted as to whether you still wish to load.
In all other cases no check is made.

A5E01078201-02 - Edition 01.2008
CFC
2.4 Creating block types
If you have installed the "D7 SYS" software package, you automatically
have access to the block types in the standard "FBSLIB" block library.
You can use these to configure your system in the CFC. You can import
additional standard block libraries (FBSLDC, FBSLT1, FBSWCC and
FBSLSL). Further, you can create the block types yourself, by creating a
user library from charts.
2.4.1 Creating a user library from charts
If you always re-use certain functions when configuring your system in

the CFC, you can create block types from charts. A user library is created
when compiling the charts. The block types in this library can be used
when configuring your system, just like the existing function blocks from
the standard block libraries.
NOTES • All charts of a chart folder are compiled and combined in a user
library.
• The interface of a chart, which is to be compiled, is the future

interface of the appropriate block type. The interface comprises the
margins at the lefthand and righthand side of a CFC chart. They
contain, on one hand, the references to the interconnected objects –
e.g. other blocks or task groups, which are not on the actual sheet.
On the other hand, they contain the number of the connection
(transition point) if the autorouter cannot draw the connecting line to
the margin because the sheet is too full.
• Init values at blocks within a chart, which becomes a chart block,

are not taken into account; this means that a block with Init values at
the outputs behaves differently as a single block (Init value) than
within a chart block (no Init value).
• The libraries created are saved in the "s7cfc\sdblocks" directory of

the STEP 7 installation. If you wish to work with a symbolic
representation of the created block types, then you can locate the
bitmaps which you created ("block type name.bmp" type) in the
"s7cfc\sdblocks\icons" directory.

A5E01078201-02 - Edition 01.2008
CFC
• The names of all chart interfaces must be unique:

Name syntax
1 to 3 alphanumeric characters, only upper case letters, the 1st
character must be a letter.
• The name of the created block type must be unique:

1 to 6 alphanumeric characters, only upper case letters, the 1st
character can be a letter or a "@", a "_" is also permitted for the 2nd to
6th characters.
• The library name must be unique:

1 to 6 alphanumeric characters, only upper case letters, the first
character must be a letter; a "_" is also permitted for the 2nd to 6th
characters.
Restrictions The CFC chart is subject to specific rules, if it is to be compiled in a block

type for SIMATIC TDC/SIMADYN D or FM 458-1 DP:
• Only top charts can be compiled in block types.
• The chart may not include any other charts (chart nesting is not
permissible). Block types, created with CFC are permitted.
• Interconnections between charts are not permitted.
• No pseudo comments may be configured at the interface I/O of the

chart and the blocks contained in them.
• All of the blocks must be located in the same task. In this task, the
blocks of the chart must follow one another directly.
• The chart folder to be compiled may never contain any run-time

groups.
• If the chart includes blocks, which has attributes, then the block type,
created with CFC also takes on these attributes.
• Global operands must be routed through to the chart interface.
• For SIMATIC TDC/SIMADYN D or FM 458-1 DP, a block type may

have a maximum of one symbolic hardware address (global operand).
Prerequisites Before you create a user library from the chart, you must have completed
the following preparatory steps:
1. You must have created a chart folder in SIMATIC Manager. The

system library "FBSLIB" is automatically imported into this chart folder.
2. You have configured the charts in CFC.
3. In CFC, you parameterized, for each chart, which is to be compiled, a
chart interface.
4. In CFC, you opened a chart of the chart folder to be compiled

A5E01078201-02 - Edition 01.2008
CFC
In order to create a user library from charts, proceed as follows:

Procedure
1. Make a consistency check, in order to check that the charts can be
compiled as block types:
Select the menu command Chart > Consistency Check > Chart as
Block.
NOTE The "Check the charts as block types" dialog box is displayed. If you
press key F1 with the dialog box opened, you will receive additional
help.
2. Compile the charts as block types:

Select the menu command Charts > Compile > Chart as Block.
NOTE The "Create a library from charts" dialog box is displayed. If you press
key F1 with the dialog box open, you obtain additional help.
3. Import the created library in order to use the created block types to
configure your system.

A5E01078201-02 - Edition 01.2008
CFC
2.5 Archiving projects on the MC - saving and retrieving
Basic information The save/retrieve functionality is only possible on SIMATIC TDC /

SIMADYN D memory cards or on the memory integrated in the T400.
It is not possible to archive data on MMC (FM 458-1 DP) or SIMATIC

memory cards.
NOTE In the following text, the name MC is used for these cards and the
memory of the T400.
Functional scope Projects can be saved online and offline on the MC. This is possible for
projects archived using the SIMATIC Manager (zipped files) as well as
projects that have still not been archived (these are then zipped before
saving).
The project archive is saved in addition to the program that can run on
the MC. The data archived on the MC can be again retrieved at a later
point in time. When retrieving data, the project archive that was last
saved, is retrieved.
The save/retrieve on/from MC functionality has been implemented for the

following target systems:
• SIMADYN D
• SIMATIC TDC
• T400
Save/retrieve offline has been implemented for the following device:
• OMNI Drive (also USB LF)
It is only possible to archive a project for the FM458 and FM458-1 DP on

SIMATIC CPUs using the SIMATIC Manager.
Consistency When downloading the user program, existing project archives are
deleted on the MC. This avoids that runable programs and the archive
program are inconsistent with one another.
2.5.1 Saving a project to be archived on MC
Memory A significantly higher amount of memory is required for the project

requirement archive than for the user program.
If a project is saved repeatedly, without the user program being re-loaded

in between, then several project archives are on the MC. This results in
an appropriately high memory usage. When retrieving a project archive,
the project archive last saved in retrieved.

A5E01078201-02 - Edition 01.2008
CFC
2.5.1.1 Prerequisites for saving a project
General When saving a project, a differentiation can be made between two cases:
information
• The project was already archived using the SIMATIC Manager (then it
is already available as a zipped file).
• The project was still not archived. This means that the project must be
zipped before it is saved.
If such a project that has still not been archived, is saved on the MC, then
it may not be opened in any application (SIMATIC Manager, HWConfig,
CFC). Otherwise, data compression would not be possible.
When saving online, the original project (this is only possible for already
zipped archives) or a project where the hardware was re-configured in
HWConfig, must be opened and selected in the CFC so that a
communications link can be established to the appropriate CPU.
When saving offline, any project can be opened with the appropriate
target system.
NOTE If there is no runable program on an MC, then the project can also be
saved on it. However, this is then only possible offline.

A5E01078201-02 - Edition 01.2008
CFC
2.5.1.2 Procedure when saving
Procedure 1. Select an appropriate project.

2. In the CFC, select the menu item Options > "Save on MC ..."
3. The dialog box "Save project and other files on PLC" is opened.
4. Define the download method:

Either Online or Offline can be selected
− For Offline, the memory card must be inserted in the programming
device (OMNI Drive) connected at the PC/PG.
− For Online, the memory card must be inserted in the CPU slot
(exception: T400).
If neither offline nor online is possible because, for example, there is
no prommer, then both of the option fields and the "Save" button are
de-activated (grayed-out).
5. Now select the project that is to be saved:

It is possible to either select a project that has already been archived
or one that has still not been archived:
− If you wish to save an already archived project, then enter a
checkmark in the control box "Use project already archived".
Press the Projects button. A dialog box is opened where you can
select the required file.
The *.zip file type is already preset.

A5E01078201-02 - Edition 01.2008
CFC
By selecting a file and pressing the "Open" button, the dialog box
is closed and the selected file is accepted. The path is entered into
the higher-level dialog box. Alternatively, the file can be selected
by double clicking on it. In this case the dialog box is automatically
closed.
The dialog box is closed by pressing the "Cancel" button. The
higher-level dialog box remains open and no changes are made.
The contents of the already archived project are not checked.
− If your project has still not been archived, remove the checkmark in
the control box.
Press the Projects button. A dialog box is opened in which you
can select the required project directory.
Select a directory by clicking on it. It must be ensured that it is a

project that was generated using the SIMATIC Manager.

A5E01078201-02 - Edition 01.2008
CFC
By pressing the "OK" button, the dialog box is closed, the selected
directory is accepted and the path checked. If it involves a project
directory that was generating using the SIMATIC Manager, the
path is entered in a higher-level dialog box under Project data. A
check is not made as to whether the correct target system is
involved as far as the project is concerned. If the selected directory
is not a project directory in the sense of the SIMATIC Manager,
then the user is flagged. The "Select project directory" dialog box is
re-opened after closing the fault message.
The dialog box is exited by pressing the "Cancel" button. The
higher-level dialog box remains open.
The path of the selected project is entered into the field to the right next
to the button.
6. Select Other files:
In addition to the archived project, "Other files" can still be archived
in the MC. This functionality is optional.
Other files are only transferred if the project was not transferred. If the
memory is not large enough for the project, then Other files are also
not transferred.
− You can select an individual file using the "Add file" button. The
paths are entered into the list on the righthand side.
− Individual files can be again removed from the list using the
"Remove file" button.
7. You can initiate the operation by pressing the "Save" button.

If entries are available in the "Other files" list box, then these files are
also compressed and transferred. If a file, selected under "Other files"
has been opened from another process, then an error message is
displayed and this file is not transferred to the MC.
A progress bar is displayed while data is being transferred. This
provides information on how data transfer is proceeding.

A5E01078201-02 - Edition 01.2008
CFC
The data save operation can be cancelled by pressing the "Cancel"

button in the progress dialog box.
If the data save operation is cancelled, it cannot be guaranteed that
the contents of the MC are still consistent. This is the reason that the
user program must be again downloaded into the MC.
8. After completing the download operation, the archived project is in the
program memory of the CPU/module and, when required, can be
again retrieved.
NOTES • When downloading the user program, the archived project is

deleted. This applies both for offline as well as for online.
• During data transfer, a file is listed in the list with "Other files", that
contains file management information (drive and absolute paths) for
the individual files.
• If additional load objects (e.g. load objects with tables, that were
generated with the Additional Component Builder) are assigned
to the project, then it should be noted that these are not in the
project directory. These files should then also be included with
"Other files" in the project archiving.
• The system files are only saved (archived) if they are in the project
directory. If the user would like such a archive, then he must call the
dialog box "Options for compiling" in the CFC using the menu
Options | Settings | Compile/load ... and select the "System data
from archive" option. This means that system data is saved in the
project directory and is also archived.

A5E01078201-02 - Edition 01.2008
CFC
2.5.2 Retrieving an archived project from the MC
2.5.2.1 Prerequisites for retrieving a project
When retrieving a project offline, then it is sufficient if any project is

opened with one of the above mentioned target systems.
If a project was archived on an MC, on which there is no runable

program, then this project can only be retrieved from the MC offline.
To retrieve a project online, in the CFC, the original project (for

restrictions, refer to Save), or a project where the hardware was re-
configured in HWConfig, must be opened and selected.
If an already existing project is to be overwritten with the retrieved project,

then it may not be opened in any application (HWConfig,
SIMATIC Manager, CFC)!
2.5.2.2 Procedure when retrieving
Procedure 1. Select a project.

2. In the CFC, select the menu item Options > Project retrieve from
MC ...
3. The "Retrieve" dialog box is opened.
4. Select how you wish to download the project:

You can select between either Online and Offline
− For Offline, the memory card must be inserted in the programming
device (OMNI Drive) connected at the PC/PG.
− For Online, the memory card must be inserted in the CPU slot
(exception: T400).
If neither offline nor online is possible because, for example, there is
no prommer, then both of the option fields and the "Save" button are
de-activated (grayed-out).
The dialog box "Retrieve" can be exited by pressing the "Cancel"
button.
5. Initiate the operation by pressing the OK button.

The archived project, and if available, other files, are retrieved.

A5E01078201-02 - Edition 01.2008
CFC
The CFC responds by displaying the progress bar for retrieve. This
provides information about the current status of the data transfer.
This operation can be cancelled by pressing the "Cancel" button in

the progress dialog box.
6. The dialog box to select directories is displayed after the data has
been transferred. You can now select the target directory for the
project and acknowledge using OK.
Note: If you only wish to retrieve "Other files", then by pressing the
"Cancel" button, you can go directly to Other files in the directory
selection dialog box.
7. If a project with the same name already exists in the selected

directory, then the "Project already exists" dialog box is displayed.
Press the "Yes" button to overwrite the project, or "Save under", in

order to select another directory. The directory, entered for "Save
under" is also checked. This is done until a directory is selected in
which the project does still not exist.
8. The project is saved in the specified directory.

9. After the project has been unzipped and saved, the dialog box is
closed.

A5E01078201-02 - Edition 01.2008
CFC
10. If Other files were archived in the MC, then the dialog box is
displayed with "Other files".
In order to save files at their original location, acknowledge with

"Yes". If a file already exists, a dialog box is displayed and you can
save the file(s) under another name or in another directory.
If you press the "No" button, a dialog box is displayed and the
particular file can be saved under another name or in another
directory.
If you press the "Cancel" button, the dialog box is closed and the files
are rejected. They can be retrieved from the MC at a later time.
As soon as a file is already available, this is signaled using a dialog

box.
For all of the files, there is an individual prompt as to where they

should be saved.
As soon as the "Yes, all" button is pressed, no other prompt will be

displayed.

A5E01078201-02 - Edition 01.2008
CFC
2.6 Chart reference data-documentation
This Chapter describes how you can create the chart reference data for
comprehensive documentation of your CFC configuring structure.
2.6.1 Chart reference data
In addition to graphic CFC displays, you can display and print the
following information in list form using the "Chart reference data" function:
• Cross references
Listing the accesses to different objects.
• Run sequence
The complete run sequence of a CPU.
You can check the structure of your configured software in this fashion.
Cross-reference You can display and print the following chart reference data lists:
lists
• Cross references, operands
The list shows all of the global operands, used in the project together
with the elements which they access.
• Cross references run-time groups

The list shows which run-time groups are accessed from any CFC
charts.
• Cross references block types

The list shows the block types used and the positions
(CFC chart) where they are used.
2.6.1.1 "Cross reference operands" list
List structure This is a list of the global operands, used on the CPU/FM 458-1 DP with
the block connections which are used to connect them.
You can output this list via

Options > Reference data > View > Cross references Operands

A5E01078201-02 - Edition 01.2008
CFC
Fig. 2-6: Chart reference data: Cross references, operands
Column title Significance

Icon For SIMADYN D, empty
Operand Name of the global operands
Data type Code word for the data type used
R/W For SIMADYN D, always W, i. e. write access
Chart Name of the chart from which the operands are
accessed
Chart element Name of the interconnected
block and I/O
Element comment Block comment
Type Block type (e.g. INT)
Table 2-2: Cross-references of the operands

A5E01078201-02 - Edition 01.2008
CFC
2.6.1.2 "Cross-reference run-time groups" list
The list contains, for all run-time groups of the active CPU/FM 458-1 DP,
the access operations to the enable of the task group from any CFC
charts (block I/O).

Options > Reference data > View > Cross references Run-time
groups
Run-time group Group name
R/W Reading (R) or writing (W)
Chart Name of the CFC chart
Chart element Name of the interconnected block and I/O
Element comment Block comment
Type Block type (e. g. INT)
Table 2-3: Cross-references of the run-time groups
2.6.1.3 "Cross-references block types" list
The list of block types indicates where these are used. This can be useful
when administering the blocks, for example, before deleting a block type
which you think is not used, you can use the cross-reference list to
indicate whether this particular block type is used or not.

Options > Reference data > View > Cross references Block types
Block type Name of the block type (e. g. INT)
Chart Name of the CFC chart in which the block is used
Block Name of the instance block (e. g. integrator1)
Block comment Block comment
Table 2-4: Cross references of the block types

A5E01078201-02 - Edition 01.2008
CFC
2.7 Technical data
2.7.1 Field/name lengths and conventions
Object Length Comment

Chart 22 *) **) The following characters may not be used:
\ . : / * ? " < > | # %
Chart comment 255 All ANSI characters are permitted.
Run-time group 22 Character scope as for "Chart"
Task 22 Character scope as for "Chart"
Block type 6 Defined by SIMADYN D.
Comment 80 All ANSI characters are permitted.
Block instance
Parameter name 4 Defined by SIMADYN D.
The 1st character may not be a digit (0-9).
Parameter comment 80 All ANSI characters are permitted.
Block name 16 *) **) The following characters may not be used:
(instance name) \ . : / * ? " < > | # %
Global operand max. 14 Depending on the global operand type
- $ signal name 14 All ANSI characters with the exception of, ‘*’, ‘!’ and ‘$’
- Hardware address 16 All ANSI characters with the exception of, ‘*’, ‘!’ and ‘$’
st
- Virtual 6 1 character: ‘A’ ... ‘Z’
connection name additional characters: ‘A’ ... ‘Z’, ‘0’ ... ‘9’, ‘_’
Symbol name 12 All ANSI characters with the exception blanks, ‘*’, ‘!’, ‘$’, '#' and '"'
- Sequence number 4 "1" ... "9999"
- Name reference 6 1st character: ‘A’ ... ‘Z’
additional characters: ‘A’ ... ‘Z’, ‘0’ ... ‘9’, ‘_’
st
- Module name 6 1 character: ‘A’ ... ‘Z’
or "0"
- Partial connector name 3 1st character: ‘A’ ... ‘Z’
*) The chart- and block name together may only be a maximum of 24 characters,
including the separator
**) If the "Create address book" compile option is activated, then
this name must have the syntax of STRUC Version 4.2:
1st character: ‘A’ ... ‘Z’
additional characters ‘A’ ... ‘Z’, ‘0’ ... ‘9’, ‘_’
Table 2-5: Name lengths

A5E01078201-02 - Edition 01.2008
CFC
2.7.2 Data types
Code Code word Name Bits

BO BOOL Logical number 8
BY BYTE 8-bit sequence 8
DI DINT Double integer number 32
DW DWORD 32-bit sequence 32
GV GLOBAL To interconnect to global operands -
I INT Integer number 16
R REAL Floating point number 32
S STRING Character sequence, any length 256 bytes
TS SDTIME High-resolution time period in the SIMATIC 32
TDC/SIMADYN D format
W WORD 16-bit sequence 16
Table 2-6: data types
2.7.3 Abbreviations
AG Automation units
AP User program
CFC Continuous Function Chart
CPU Central Processing Unit
FB Function block
IBS Start-up
IEC International Electrical Commission
MPI Multi Point Interface
MS Microsoft
OS Operator Station
PC Personal Computer
PG Programmer
PLC Programmable logic controller
SFC Sequential Function Chart
SINEC Siemens Network Architecture
STEP 7 Software development environment for SIMATIC S7/M7 and SIMATIC
TDC/SIMADYN D/FM 458-1 DP

A5E01078201-02 - Edition 01.2008
3 SFC
Overview 3.1 Basics of the SFC 3-3
3.2 Tips & Tricks 3-4
3.3 Creating Sequential Control Systems (SFC Editor) 3-6
3.4 Sequential control systems on the PLC 3-16
3.5 Using the Control Block 3-20
3.6 Documenting Programs 3-20

A5E01078201-02 - Edition 01.2008
SFC
Introduction [SD] This section is supplementary documentation for SIMATIC

TDC/SIMADYN D and only includes deviations and special features
with respect to the S7 target system.
A detailed description is provided in the online help for the SFC for the
target system S7 and
Start > Simatic > Dokumentation > Englisch > SFC Manual for S7.
Restrictions and Data types

expansions [SD]
The data types CHAR, DATE, S5TIME, STRING, TIME, TIME_OF_DAY,
are not permissible for SIMATIC TDC/SIMADYN D. SDTIME, TS data
type is also included.
Global addresses (operands)
For SIMATIC TDC/SIMADYN D, global addresses (operands) are not

permissible as addresses (operands) in assignments of steps or
comparisons from transitions in SFCs.
Messages
SFCs do not generate messages in the SIMATIC TDC/SIMADYN D

target systems.
Run properties
For SIMATIC TDC/SIMADYN D, the location of the chart is irrelevant for

its processing;
the run properties of the chart are defined by the location of the
assigned function block (type: SFC), which must be configured for
each SFC.
Changing-over SFC operation for SIMATIC TDC/SIMADYN D is a new feature. This

from older projects means, that there are no older projects which have to be changed-over.
to SFC V5.x [SD]

A5E01078201-02 - Edition 01.2008
SFC
3.1 Basics of the SFC
3.1.1 SFC in the STEP 7 environment [SD]
The following STEP 7 components are of significance when working with

the SFC for SIMATIC TDC/SIMADYN D:
The SIMATIC Manager is used to set-up and change a project structure

(SIMATIC TDC /SIMADYN D stations, SIMADYN D programs, CFC
charts, SFC charts) and to start
the CFC or SFC editor as well as compiling charts.
The following diagram shows how the CFC and SFC are embedded in
the STEP 7 environment:
SIMATIC Manager
STEP 7
STEP 7 components
CFC SFC
SIMATIC TDC / SIMADYN D
3.1.2 SFC and technology hierarchy [SD]
The technology hierarchy cannot be used for SIMATIC TDC/SIMADYN D.
3.1.3 Setting-up the project structure [SD]
Contrary to SIMATIC S7, for SIMATIC TDC/SIMADYN D it is not possible

to use PCS7 and the S7 Assistant. You can only create a new project via
the menu commands.
3.1.4 SFC-Elements
3.1.4.1 What are chart elements? [SD]
The elements of a SFC chart are, for SIMATIC TDC/SIMADYN D, the

same as for SIMATIC S7. However, contrary to [S7], you cannot access
other SFC charts or global operands of the user program.

A5E01078201-02 - Edition 01.2008
SFC
3.2 Tips & Tricks
3.2.1 Generate reference data [SD]
Reference data cannot be generated for SIMATIC TDC/SIMADYN D. The

display functionality is not available.
3.2.2 Configuring SFC calls [SD]
Hierarchic SFC- Configuring hierarchic SFC-chart calls for SIMATIC TDC/SIMADYN D is

chart calls somewhat different than for SIMATIC S7. The reason for this is that SFC
charts have no EN connection.
Instead, the inputs and outputs of the associated SFC block (in CFC)
must be used.
In order to control the "SFC-Slave1" and "SFC-Slave2" charts using an

SFC chart "SFC-Coord", configure as follows (the SFC block for "SFC-
Slave1" would be configured as "Slave1" and the SFC block for "SFC-
Slave2" as "Slave2" in the CFC chart "SFCs"):
• The previous transition of the step, which should activate "SFC-

Slave1", must ensure that the "SFC-Slave1" is ended. This is
guaranteed using the following condition in the transition properties
dialog box:
SFCs.Slave1.QRU = 0
• The step to activate the "SFC-Slave1" must generate a rising edge at

input RUN of the associated block. The following instructions in the
property dialog box of the step generate the required behavior:
Under the “Initialization” tab:

SFCs.Slave1.RUN = 1
Under the “Processing” tab:

SFCs.Slave1.RUN = 1
Under the “Termination” tab:

SFCs.Slave1.RUN = 0
The subsequent transition (following transition) must ensure that the

"SFC-Slave1" was ended; i.e. the transition contains the following
condition in its properties dialog box
SFCs.Slave1.QRU = 0
The control of SFC-Slave2 via SFC-Coord is realized in a similar fashion.
The above representation is only valid, if the slaves are running in the
automatic mode. In the manual mode, additional statuses can be
accepted, which can then also be processed.

A5E01078201-02 - Edition 01.2008
SFC
For SIMATIC TDC/SIMADYN D, contrary to SIMATIC S7, the user has no

Coordinating SFC
variables, which exist independent of a function block (single data cells).
charts
This means, that in this case connections of dummy blocks (e. g.
NOP1_B) must be used, which can fulfill the same function.

A5E01078201-02 - Edition 01.2008
SFC
3.3 Creating Sequential Control Systems (SFC Editor)
3.3.1 Working with Charts
3.3.1.1 Copying charts [SD]
For SIMATIC TDC/SIMADYN D, charts are essentially copied the same

as when copying to the SIMATIC S7 target system.
3.3.2 Configuring Sequential Control Systems
3.3.2.1 Creating a jump [SD]
Creating and changing jumps for SIMATIC TDC/SIMADYN D is

essentially the same as the SIMATIC S7 target system. However,
generally, the subsequent compilation run rejects jumps in and out of
simultaneous sequences as being erroneous.
3.3.2.2 Step: Editing addresses [SD]
The left address can be:
• A block input of a block which has not been linked into a CFC chart
Syntax: <chart name>.<block name>.<I/O name>
• A run-time (turn on/off)

Syntax: <group name>.EN (enable)
The right address can be:
• A block I/O of a block on a CFC chart

Syntax: <chart name>.<block name>.<I/O name>
• A run-time group (state, turn on/off)

Syntax: <group name>.EN (enable)
• A constant
Syntax: Depending on the data type
For data types, BOOL, BYTE, INT, DINT, WORD, DWORD, instead of
the absolute numerical values, their symbolic value designations can also
be specified.
Selecting Using an additional dialog box, you can edit or select addresses for the
addresses statements. The dialog box is opened using the “Browse...” button. The
third possibility is to drag the block I/O from the CFC charts and directly
drop them in the box for the address (drag&drop).

A5E01078201-02 - Edition 01.2008
SFC
The "Browse" dialog box contains two different tab sheets: "CFC Charts"
and "Run-Time Groups". When you browse (e.g. CFC Charts), all of the
available objects of the chart folder are found and displayed.
Using the "Filter" button, you can limit the list of I/Os; in other words, only
display those currently relevant at the present stage of the configuration.
You can then select the required chart and then the block and I/O. Click
the "Apply" button to enter your selection in the active address box (or
drag and drop with the mouse). The dialog box remains open until you
close it explicitly with the "Close" button or you close the "Object
Properties" dialog box.
Note Accesses to CFC blocks can also be modified in the associated CFC
chart. However, this modification is restricted to "Re-connecting" SFC
accesses, i.e. moving the access to another block I/O (with ALT +
drag&drop).
Value identifiers To allow the value identifiers to be displayed in the SFC, the option
"Parameter: Value identifier" must be selected in
Options > Customize > Layout....
If you insert a block I/O with a value identifier in the address field, the
value identifier is also entered in the right (empty) address field. If there is
more than one value identifiers for this I/O, you can open the combobox
with the value identifiers in the right address field by pressing the key
combination ALT + DOWN. In the drop-down list box, you can select the
required value identifier for this address.
Editing addresses When making textual entries, make sure that the names are consistent. A
symbol that does not exist in the symbol list (or a referenced symbol that
is subsequently re-named) cannot be checked in the editor and is
assumed to be correct. Such inconsistencies show up when you compile
or run the consistency check.
Notes • In the addresses, you can reference CFC block I/Os whose block
does not yet really exist in the CFC chart providing that it does exist
as block type in the block folder of the S7 program. These statements
are displayed in the statement line on a yellow background and the
"virtual" block is listed in the CFC catalog of "Unplaced blocks".
• When you enter a virtual reference, you can specify a block name in
the statement, that is not yet known in the CFC chart. The specified
block I/O must, however, actually exist in a block type contained in the
block folder. A list of the block types that have this I/O is displayed in
the "Select Address Type" dialog box. After you select the required
block type, CFC creates a block instance and stores it in the CFC
catalog of "Unplaced blocks". This can be identified in the catalog by
the index “R" (R = reference). The same appearance and marking is
also used if a previously real reference becomes a virtual reference
when the reference block is deleted.
• Before you compile, these virtual accesses must be converted to

real accesses (in other words, the relevant block must be placed in
the CFC chart), otherwise compilation is stopped with an error.

A5E01078201-02 - Edition 01.2008
SFC
The statement "<run-time group>.EN := ON" starts a run-time group. A

EN attributes
run-time group is de-activated using the statement "<run-time group>.EN
:= OFF". You can therefore enable or disable the processing of CFC
blocks and FCS charts in a run-time group with one statement.
Notes • When you enter statements, they are checked for consistency so that
the correct syntax and semantic formulation is guaranteed. The
program, for example, also checks whether the data types of the
logically combined addresses are compatible.
• If the specified addresses is recognized as address type unknown, a

dialog box is opened in which you can enter more detailed
information. Here, you can assign a CFC access, an SFC chart, a run-
time group or a symbol to the address as the type with the
corresponding data type. You can save your entry with “OK”, but it
cannot be compiled until the address is defined (this results in an error
message).
Go to point of use If you want to see where an operand is used, select the address (or place
the cursor in the field associated with the address), and click on the “Go
to” button to jump to the relevant chart (or double-click on the address). If
the address is an input or output of a block in the CFC chart, the relevant
block is selected.
The "Go to" function cannot be used for run-time groups
3.3.2.3 Transition: Editing addresses [SD]
You can enter addresses textually or as described in “Step: Editing

addresses” using the “Browse” dialog. The advantage of browsing is that
the addresses are then unique. As a third possibility, you can also drag
the block I/Os from the CFC charts directly to the box for the address
(drag and drop).
As when selecting addresses for the steps, you can also enter the value
identifiers of the I/Os for the transitions (refer there).
If you make a selection in a CFC chart with "Browse" or by dragging with

the mouse, the entries also include the path of the plant hierarchy (if this
exists). The hierarchy path and chart name are separated by a double
backslashes ( \\ ).
Note Access to CFC blocks can also be modified in the relevant CFC chart.
This modification is, however, restricted to "Re-connecting" SFC
accesses; in other words, moving the access to another block I/O (with
ALT + drag&drop).
EN Attribute With the condition
• <run-time group>.EN = ON
• <run-time group>.EN = OFF
you can query whether an SFC chart is activated or de-activated.

A5E01078201-02 - Edition 01.2008
SFC
When you enter conditions, they are checked for consistency so that
Note
correct syntax and semantic formulation of the conditions is guaranteed.
The program also checks whether the data types of the logically
combined address are compatible.
The pre-configured logic is normally adequate. If you require more

complex formulations, you can create them with blocks in a CFC chart
and enter the results calculated in the chart as the address for transition
conditions.
Go to point of use If you want to see where an address is used, select the address (or
locate the cursor in the field associated with the address), and click on
the “Go To” button to jump to the relevant chart. If the address is an input
or output of a block in the CFC chart, the relevant block is selected.
The "Go To" function cannot be used for run-time groups.
3.3.3 Shared Adresses and Permitted Data Types
3.3.3.1 Global addresses (operands) [SD]
For SIMATIC TDC/SIMADYN D, global addresses (operands) are not

permissible as addresses (operands) in assignments of steps or
comparisons from transitions in SFCs.
3.3.3.2 Absolute addressing [SD]
Absolute addressing is not possible for SIMATIC TDC/SIMADYN D.
3.3.3.3 Symbolic addressing [SD]
For SIMATIC TDC/SIMADYN D, it is not possible to address operands

via the symbol table (symbolic addressing).
3.3.3.4 Permissible data types [SD]
The following data types when formulating actions and conditions in the
SFC are permissible for SIMATIC TDC/SIMADYN D:
Data type Permissible Permissible in
in the step the transition
BOOL, BO Yes Yes
BYTE, BY Yes Yes
DINT, DI Yes Yes
DWORD, DW Yes Yes
INT, I Yes Yes
REAL, R Yes Yes
SDTIME, TS Yes Yes
WORD, W Yes Yes

A5E01078201-02 - Edition 01.2008
SFC
3.3.4 The Run-Time Properties
3.3.4.1 Overview of the run-time properties [SD]
For SIMATIC TDC/SIMADYN D, the location of the chart is irrelevant for

its processing;
the run-time properties of a SFC chart are defined by the location of
the assigned function block (type: SFC), which must be configured
for every SFC chart.
The run-time properties of the SFC block determine how the SFC chart is
included in the processing of the entire structure on the target system.
These properties are decisive for the response of the PLC (target system)
in terms of response times, deadtimes or the stability of time-dependent
structures, for example, control loops.
The run-time properties are defined using the “Run-time property dialog
box”.
SFC function blocks can be incorporated in run-time groups, which

means that they have the attributes of the run-time group (scan rate,
phase).
Note For SIMATIC TDC/SIMADYN D, only the following constant values are
permissible:
• Scan rate = 1
• Phase shift = 0
3.3.4.2 Specifying the run sequence [SD]
There are various ways of editing the run sequence of SFC charts. The
run sequence involves the positions of the associated SFC blocks in the
tasks and run-time groups.
3.3.4.3 Installing an SFC chart in a task / deleting from a task [SD]
The generation system automatically incorporates every SFC chart into a

task. This does not have to be done twice as for SIMATIC S7, and is also
not possible. In addition, for each SFC chart, a SFC function block must
be incorporated in a CFC chart, whose input SFC, must be tagged with
the name of the SFC chart.

A5E01078201-02 - Edition 01.2008
SFC
This block carries the SFC functionality. Using the name configured at the
SFC input, it searches the associated SFC chart and interprets this as
program. This is the reason that only the position of the block within the
task is decisive for the run position of the SFC chart.
However, we recommend that the SFC chart is directly located in front of
the associated block, so that there is no confusion regarding where the
SFC chart is processed.
In order to avoid confusion regarding the run-time properties of the SFC
chart, you should
• always configure the associated SFC chart in front of the appropriate

SFC block
• and when deleting, remove the SFC chart as well as the associated
SFC block.
Note If you configure an SFC block in an interrupt task, please observe, that
each time that the task is activated, the SFC block is only run once.
3.3.4.4 Run-time attributes for the run-time group and SFC chart [SD]
Enable attributes of For SIMATIC TDC/SIMADYN D, there is no enable attribute for an SFC
the SFC chart chart. Instead, you can use input EN of the associated SFC function
block (on=1, off=0).
Run-time attributes For SIMATIC TDC/SIMADYN D, the location of the chart is irrelevant for
for the run-time its processing; the run-time properties of the chart are determined by the
group location of the assigned function block (type: SFC), which must be
configured for every SFC. This block can be incorporated in a run-time
group.
You can enable and disable a run-time group using the enable attribute.
The attributes
• Scan rate
• Phase
cannot be directly assigned to an SFC chart. Instead, only by

incorporating the associated function block in a run-time group, from
which it receives the selected attributes. However, for SIMATIC
TDC/SIMADYN D, only a scan rate of 1 and a phase shift of 0 are
permissible.
If SFC blocks of a CPU are to run with different run-time attributes, then
these SFC charts must be incorporated in different run-time groups.
The SFC chart has no run-time properties of its own (which it can
change). This is the reason that the object properties cannot be opened
in the run sequence for the selected SFC chart.

A5E01078201-02 - Edition 01.2008
SFC
You can generate a run-time group in the window of the run sequence
(call using or Edit > Run sequence... ) using the menu command
Insert run-time group... .
Enter the name, if required a comment and the run attribute for scan rate
and phase shift in the dialog box.
Incorporate the SFC block into the run-time group as usual (this is done
just like incorporating a task).
Note You can run SFC blocks in various cyclic tasks by incorporating them in
run-time groups. (This allows the project to be better structured from a
technological perspective).
3.3.5 Configuruing Messages
3.3.5.1 How SFC works with messages [SD]
SFCs do not generate any messages in the SIMATIC TDC/SIMADYN D

target systems.
3.3.6 Compiling Charts
3.3.6.1 Customizing the compiler [SD]
You can call-up a dialog box using the menu item Options > Customize
> Compilation. This allows you to make the following settings:
1. In which directory should buffer files be saved, which are generated

during compilation?
2. Should an addressbook be generated or not?
Note If you activate this option, when compiling, it is ensured that you have
maintained the correct syntax for STRUC Version 4.2 for the chart, block
and $ signal names.
1. Should a maplisting of the user program be generated or not?

2. Which function block types should be able to be inserted online in
the CFC test mode?
• Only block types which have been already configured
• The block types of the standard "FBSLIB“library
• Block types from all imported libraries
Default hardware Here, you can define for which hardware, block libraries are to be
imported into a chart folder without hardware assignment via HWConfig:
• Select the control box “SIMATIC TDC”, if you wish to configure

software
for SIMATIC TDC.

A5E01078201-02 - Edition 01.2008
SFC
• De-select the control box “SIMATIC TDC”, if you wish to configure

software
for SIMADYN D.
Note For chart folders with hardware assignment, the block libraries, which
automatically match the hardware, are imported.
Generate file for all Select the control box “All I/O”, if you wish to generate a file with all I/O.
I/O
Generate file for Select the control box “String I/O”, if you wish to generate the file, which
string I/O only contains the string I/O.
Note The procedure for “Customize the compiler [SD]” is identical with that of
the CFC.
3.3.6.2 Compilation procedure [SD]
This is how you • Select the menu command Chart > Compile as Program... or click
compile your
configured charts: on .
A dialog box opens, where you can either select compile "Entire
program" (all of the charts are compiled), or compile "Changes only"
(only those objects which were changed since the last compilation,
are compiled) and the compilation of an individual SFC. The selection
is made using the option switches.
• Select the compilation type "Compile all", "Compile only changes" or

“Only compile individual SFC”. In the latter case, you must still search
for the SFC, which you wish to compile, using the selection box. Then
start compilation by entering “OK”.
• The selected compilation scope of the charts of the current program

(chart folder) are checked for consistency and are subsequently
compiled.
A dialog box with a progress bar is displayed while compiling. You can
stop compilation at any time by pressing the “Cancel” button.
Logs The result of the consistency check and all of the messages which were
output when compiling, can be read and printed in the dialog box "Logs”
(menu command Options > Logs...).
Note You can also run a consistency check without compilation. To do this,
select the menu command Chart > Consistency check....
3.3.6.3 Consistency check [SD]
Before the actual compilation run, in addition to the consistency checks of

the CFC compilation, the system automatically makes consistency
checks at the SFCs:
• Checks, whether all of the blocks, which are accessed by SFC

conditions or statements still exist.

A5E01078201-02 - Edition 01.2008
SFC
• Checks, whether the jump target names, specified for jumps, are used
in the same SFC as step names.
• Checks, that jumps do not lead to simultaneous sequences.
You can also make these consistency checks without subsequent

compilation. For example, if you wish to check whether compilation
makes sense at all.
Proceed as follows:
• Select the menu command Chart > Consistency check....

This checks all of the charts of the current chart folder.
• After the check has been completed, the result is displayed in the
"Logs" dialog box. The log can be read or printed-out at a later time, if
you select, in the SFC, the menu command Options > Logs... (or in
SIMATIC Manager Options > Charts > Logs...).
Note The procedure for the “Consistency check [SD]” is identical with that for
the CFC.
3.3.7 Downloading User Programs
3.3.7.1 Downloading programs [SD]
In order to run a user program on a CPU, it must be first loaded.
The user program, compiled from the CPU charts, is downloaded into the
particular CPU, which is assigned the active chart window. The user
program is transferred into the CPU program memory. However, it is still
not active.
The new CPU program only becomes active if the CPU is restarted (refer
to View and change operating statuses).
You can either load the user program offline or online.
This is how you download the user program:
1. Select the menu item PLC > Download...

2. The "Download" dialog box is opened.
3. Define the scope of the software to be downloaded:
• Generally, it is sufficient to only load the configured software ("Only
user program ") which reduces the download time. However, if the
CFC recognizes that the operating system release has changed since
the last time that data was downloaded into this CPU, then the new
version of the operating system is automatically downloaded.
• If no software has been previously downloaded into the CPU, you

must download the complete software ("System and user program")
into the CPU.

A5E01078201-02 - Edition 01.2008
SFC
• If only an individual SFC was revised and compiled, then you can
download this online. In this case, select the “online” and “only
individual SFC” options. In the activated selection box, you can select
the SFC which still have to be downloaded.
4. Specify how the PC can access the program memory:

• During start-up, generally, you will leave the memory module with the
user program in the CPU, and appropriately select the "online" option.
• For "offline", you must remove the memory card from the CPU, and
insert it in the appropriate PCMCIA-slot of your PC.
5. To start downloading, initiate the Download function. The CFC

responds with the progress bar when downloading.
6. After downloading has been completed, the new user program is in
the CPU program memory. This becomes active the next time that
the station is restarted.
Note The procedure when “Downloading programs [SD]” is identical with that
of CFC.

A5E01078201-02 - Edition 01.2008
SFC
3.4 Sequential control systems on the PLC
3.4.1 Overview of sequential control systems on the PLC [SD]
For SIMATIC TDC/SIMADYN D:
• Not a control block in the S7 sense, but instead an SFC function block
(block type: SFC), which must be configured for each SFC chart.
Basically no phase shift and no scan rate for run-time groups, because
only the following constant values are permissible:
• Scan rate = 1
• Phase shift = 0
3.4.2 How a chart is executed [SD]
For SIMATIC TDC/SIMADYN D, cyclic interrupts are implemented as

interrupt tasks.
The operating system evaluates specific events, and executes the SFC
chart according to these events. Such events are, e.g.:
• Warm restart
The SFC chart is automatically called for initialization.
• Interrupt tasks
The SFC chart is executed in the interrupt task, in which it was
configured using the run-sequence editor.
The assignment of an SFC chart to the events must be explicitly carried-

out using the run-sequence editor, i.e. the chart must be incorporated in
the appropriate task (directly or in run-time groups). Call in the SFC: Edit
> Run sequence...).
3.4.3 The operating modes [SD]
The following operating modes, can be selected using the SFC block:
• Manual, and
• Automatic
3.4.4 Chart execution options [SD]
The behavior of SIMATIC TDC/SIMADYN D corresponds to that of

SIMATIC S7.

A5E01078201-02 - Edition 01.2008
SFC
Using the chart execution options, you can define how the chart behaves.
What are chart
The individual execution options can be combined with one another. The
execution options?
following chart execution options are available and can be changed in the
"Chart > Properties: Operating Parameters PLC" dialog box:
Command output • For "Command output: On”, the actions of the active steps are
processed.
• For "Command output: Off”, the actions of the active steps are not
processed.
During installation and commissioning, or if errors occur, blocking

command output in conjunction with certain operating modes, can bring
the sequential control system into a defined state without influencing the
process.
Cyclic operation • With "Cyclic operation: On”, the initial step of the SFC chart is
activated again after the final step is de-activated.
• With "Cyclic operation: Off”, the sequential control system is set to the
"IDLE" state after the final step has been de-activated; i.e. no steps
are active and more actions and no more transitions are executed.
Time monitoring • For "Time monitoring: On”, after activating a step, the active time of
the step is compared with the monitoring time (object properties of the
step, tab sheet "General", option "Maximum run time") and a step
error is signaled if this time is exceeded.
• For "Time monitoring: Off", the active time and monitoring time are not
compared.
Autostart An SFC chart with the “Autostart: On” property starts immediately after a
CPU warm restart without any further operator input. After downloading
changes (the CPU does not go into the STOP condition), there is no
automatic start and the SFC chart must be started again by the operator
or using the control block.
The setting for "Autostart" can only be changed in the dialog box Chart >
Properties > Tab: Operating Parameters.
Use default With the chart execution option "Use default operating parameters when
operating SFC starts: On", all of the default settings / options, set in the run-time
parameters when properties become effective again when the SFC chart is started. For
the SFC starts example, the options which were changed in the test mode.
3.4.5 Behavior of a sequential control system [SD]
Sequential control system behavior depends on the operating

parameters: Operating state, mode, step module mode and the chart
execution options.
You can set the operating parameters when testing and commissioning
(with the exception of “Auto start”); this parameter can only be set in the
Chart properties dialog box under the "Operating Parameters PLC" tab).

A5E01078201-02 - Edition 01.2008
SFC
• Operating mode Manual (operator mode)

Default settings of
the PLC operating
• Step control mode T (process control)
parameters
• Chart execution options:
− command output On
− cyclic operation Off
− time monitoring Off
• Further options
− auto start Off
− use default operating parameters

when starting the SFC start Off
The following operating mode is set after the PLC runs-up:
• Operating mode OFF (if auto start = off)

ON (if auto start = on)
Behavior when When starting the SFC chart, the behavior depends on the chart
starting [SD] properties.
Auto operation
When the chart starts, the SFC block parameters are used.
Manual operation
When the chart starts, the defaults of the SFC block or the actual SFC-
chart parameters are used.
Depending on the setting of the operating parameters (Chart >

Properties: Operating Parameters PLC) or in the test mode, option:
"Use the default operating parameters when SFC starts", the actual
values are kept, or these values are overwritten by default values.
3.4.6 The operating states [SD]
Refer to the SFC help for the SIMATIC S7 target system.
Note The function of the control block (SFC_CTRL), for

SIMATIC TDC/SIMADYN D, is assumed
by the SFC block.
3.4.7 The commands [SD]
The behavior of SIMATIC TDC/SIMADYN D corresponds to that of

SIMATIC S7.
What do the In the test mode, you can set or modify the operating states using the
commands do? following commands:

A5E01078201-02 - Edition 01.2008
SFC
This command changes the sequential control system from the “IDLE”,
Start / Resume "ABORTED" or "TERM" into the “RUN” state. This means that the chart
is immediately processed. The initial step automatically becomes active,
Meaning of "Start" if its are executed and the results of the successor transitions of the initial
step are evaluated.
Exception: If, in the test mode, a step was selected as target step, then
when starting, the initial step isn’t activated, but instead, the target step.
Meaning of This command changes the sequential control system from the “HOLD”
"Resume" state to the ”RUN” state. This means that the SFC chart is continued,
transition results are evaluated, the actions are executed and the chart
progresses according to the selected step control mode.
Exception: If a step was selected as the target step in the test mode, the
held SFC chart resumes the target step after correct processing of the
interrupted steps when the "Resume" command is set. This means that
the cyclic processing of these steps is executed a maximum of once
more and the termination overlaps the initialization of the target step in
the same cycle.
This command changes the sequential control system from the “HOLD”
Abort state to the “ABORTED” state. The active steps are processed
completely and then the final step. Existing target step selections are
ignored and deleted.
This allows the sequential control system to be brought into a defined
state.
This command changes the sequential control system from the “RUN”
Hold state to the ”HOLD” state. This means that the SFC chart is stopped, the
transition results are not evaluated, the actions are not executed, and a
command must be issued before the chart can continue.
This command changes the sequential control system from the “HOLD”
Restart state to the ”RUN” state. The active steps are de-activated, the initial step
is activated and its actions executed.
3.4.8 SFC Elements of the PLC
3.4.8.1 Phases of a step [SD]
For SIMATIC TDC/SIMADYN D, there is no difference to the target

system SIMATIC S7.
3.4.8.2 Processing steps and transitions [SD]
For SIMATIC TDC/SIMADYN D, there is no difference to the target

system SIMATIC S7.

A5E01078201-02 - Edition 01.2008
SFC
3.5 Using the Control Block
3.5.1 The control block [SD]
For SIMATIC TDC/SIMADYN D, the function of the monitoring block is

undertaken by the SFC block.
3.5.2 Inputs of the control block [SD]
For SIMATIC TDC/SIMADYN D the control block function is taken from

the SFC block.
3.5.3 Outputs of the control block [SD]
For SIMATIC TDC/SIMADYN D the control block function is taken from

the SFC block.
3.6 Documenting Programs
3.6.1 Logs [SD]
The logs are not part of the complete documentation of the configuration
structure, but can however supply important information during
configuring (engineering) and commissioning, if, for example, errors have
occurred.
The tab sheets described here are also relevant for the SFC.
Generating logs Using the Options > Generating logs... menu command, you can open
a dialog with several tab sheets. The tab sheets are only available, if the
appropriate functions were actually executed.
You can print-out the messages by pressing the “Print” button. You can
select the layout using the “Page set-up” button.
Tab sheet: Compile This lists the messages which were output when compiling or when
making a consistency check (including the compiler messages); e.g. if a
jump to target was not available: "Error in transition ‘3’: The specified
jump target is not available in the SFC."

A5E01078201-02 - Edition 01.2008
Index
$
$ signals .............................................................................................................................1-31, 2-10
Block I/O................................................................................................................................... 2-10
Bus ........................................................................................................................................... 2-10
Interconnectability .................................................................................................................... 2-11
Type ......................................................................................................................................... 2-10
A
Activate
Test mode ................................................................................................................................ 2-31
Activating
Test mode ................................................................................................................................ 2-39
Allocating I/O addresses ............................................................................................................. 1-28
Archive file ................................................................................................................................... 1-47
Archiving program
Properties ................................................................................................................................. 1-47
Archiving programs ..................................................................................................................... 1-47
Archiving projects ........................................................................................................................ 1-48
B
Block catalog
Open......................................................................................................................................... 2-27
Block connections
Configuring operator control and monitoring attributes............................................................ 2-16
Monitor ..................................................................................................................................... 2-41
Block I/O
$ signals ................................................................................................................................... 2-10
Hardware addresses ................................................................................................................ 2-12
Module names.......................................................................................................................... 2-12
Monitoring................................................................................................................................. 2-34
Name references...................................................................................................................... 2-13
OP connection.......................................................................................................................... 2-12
Parameterizing ................................................................................................................2-34, 2-43
Process interrupts .................................................................................................................... 2-13
Virtual connection names......................................................................................................... 2-11
Virtual connections ................................................................................................................... 2-11
Block I/Os
Properties ................................................................................................................................... 2-8
Block inputs
Inverting...................................................................................................................................... 2-8
Block interconnections .................................................................................................................. 2-9
Block library
Check ......................................................................................................................................... 2-5
Checks ....................................................................................................................................... 2-6
D7-SYS - STEP 7, CFC and SFC configuring - SIMATIC D7-SYS I-1

A5E01078201-02 - Edition 01.2008
Index
Creating .................................................................................................................................... 2-49

Deleting ...................................................................................................................................... 2-6
Importing..................................................................................................................................... 2-5
Block outputs
Values......................................................................................................................................... 2-8
Block types
Creating .................................................................................................................................... 2-49
Handling ..................................................................................................................................... 2-5
Help .......................................................................................................................................... 2-29
Inserting...................................................................................................................................... 2-6
Blocks
Delete ....................................................................................................................................... 2-32
Deleting .................................................................................................................................... 2-45
Edit ........................................................................................................................................... 2-28
Insert................................................................................................................................2-26, 2-32
Inserting.................................................................................................................................... 2-45
Interconnect.............................................................................................................................. 2-28
Operator control and monitoring............................................................................................... 2-15
Bus
$ signals ................................................................................................................................... 2-10
C
CFC
Embedded .................................................................................................................................. 2-2
Start .......................................................................................................................................... 2-26
CFC chart
Open......................................................................................................................................... 2-26
Change
Input value ................................................................................................................................ 2-31
Run sequence .......................................................................................................................... 2-28
Test mode................................................................................................................................. 2-31
Change object properties ............................................................................................................ 1-16
Changes
in the test mode ........................................................................................................................ 2-38
Changing
between the test- and setting mode ......................................................................................... 2-38
Refresh rate.............................................................................................................................. 2-37
Chart
Print .......................................................................................................................................... 2-33
Check
Block library ................................................................................................................................ 2-5
Establishing a connection......................................................................................................... 2-48
Check consistency....................................................................................................................... 1-29
Checks
Block library ................................................................................................................................ 2-6
Communication connections ....................................................................................................... 1-31
Communication interfaces ........................................................................................................... 2-46
Communications bus ................................................................................................................... 1-13
Communications interface
Selecting................................................................................................................................... 2-47
Compilation
Muli-processing ........................................................................................................................ 2-19
Settings..................................................................................................................................... 2-18
Compiling..................................................................................................................................... 2-30
I-2 D7-SYS - STEP 7, CFC and SFC configuring - SIMATIC D7-SYS

A5E01078201-02 - Edition 01.2008
Index
Chart as block type................................................................................................................... 2-49

Interrelationships ...................................................................................................................... 2-17
Scope ....................................................................................................................................... 2-17
User program ........................................................................................................................... 2-17
Complete documentation ............................................................................................................ 2-32
Configuration load ....................................................................................................................... 1-29
Configuration save ...................................................................................................................... 1-29
1-30
1-27
Configured service interface........................................................................................................ 2-47
Configuring .................................................................................................................................. 1-24
Configuring operator control and monitoring attributes............................................................... 2-16
Configuring PROFIBUS DP......................................................................................................... 1-30
Connection
Creating.................................................................................................................................... 2-47
Connections................................................................................................................................. 2-44
Creating.................................................................................................................................... 2-44
Deleting .................................................................................................................................... 2-44
Consistency check ...................................................................................................................... 2-30
Chart as block type................................................................................................................... 2-51
Containers for the software ......................................................................................................... 1-13
Container "Charts".................................................................................................................... 1-13
CPU
Starting ..................................................................................................................................... 2-30
Crash conditions
Displaying................................................................................................................................. 2-40
Create objects ............................................................................................................................. 1-15
Create project .............................................................................................................................. 1-18
Create station .............................................................................................................................. 1-19
Creating
Block types ............................................................................................................................... 2-49
Connection ............................................................................................................................... 2-47
Connections ............................................................................................................................. 2-44
Creating a configuration .............................................................................................................. 1-24
Cross references
Block types ......................................................................................................................2-61, 2-63
List ............................................................................................................................................ 2-61
Operands.................................................................................................................................. 2-61
Run-time groups..............................................................................................................2-61, 2-63
D
Data flow
Description ................................................................................................................................. 2-4
Project planning data.................................................................................................................. 2-4
Data type ..................................................................................................................................... 2-65
GLOBAL ..................................................................................................................................... 2-9
STRING...................................................................................................................................... 2-9
De-activating
Test mode ................................................................................................................................ 2-39
De-archiving projects................................................................................................................... 1-49
Delete
Blocks....................................................................................................................................... 2-32
Deleting
Block library................................................................................................................................ 2-6

A5E01078201-02 - Edition 01.2008
Index
Blocks ....................................................................................................................................... 2-45

Connections.............................................................................................................................. 2-44
Diagnostics .................................................................................................................................. 1-41
Diagnostics buffer........................................................................................................................ 1-44
Diagnostics events ...................................................................................................................... 1-42
Diagnostics in the CFC................................................................................................................ 1-45
Diagnostics in the SIMATIC Manager ......................................................................................... 1-42
Diagnostics information ............................................................................................................... 1-43
Diagnostics interface ................................................................................................................... 2-46
Dialog box.................................................................................................................................... 1-17
Display functions.......................................................................................................................2-34
Display units ................................................................................................................................ 1-34
Displaying
Crash conditions....................................................................................................................... 2-40
DOCPRO..................................................................................................................................... 1-50
Dynamic value display
Start .......................................................................................................................................... 2-43
E
Edit
Blocks ....................................................................................................................................... 2-28
Editing
Block inputs ................................................................................................................................ 2-8
Editing block inputs........................................................................................................................ 2-8
Editing modes.............................................................................................................................. 2-34
Enable attribute ........................................................................................................................... 2-14
Entry dialog boxes
Global operands ....................................................................................................................... 2-10
Error classes................................................................................................................................ 1-42
Error report
Block library .........................................................................................................................2-5, 2-6
Establishing a connection
Check ....................................................................................................................................... 2-48
F
Field
Length....................................................................................................................................... 2-64
Function groups........................................................................................................................... 2-34
Functions when preparing for testing .......................................................................................... 2-34
G
Generate software ....................................................................................................................... 1-21
Generating software
Procedure ................................................................................................................................. 1-22
Global operand ............................................................................................................................ 1-34
Interconnection ........................................................................................................................... 2-9
Types.......................................................................................................................................... 2-9
H
Hardware
Inserting.................................................................................................................................... 2-24

A5E01078201-02 - Edition 01.2008
Index
Hardware addresses ................................................................................................................... 2-12

Block I/O................................................................................................................................... 2-12
Help
Block types ............................................................................................................................... 2-29
I
Initialization interface................................................................................................................... 2-46
Input value
Change..................................................................................................................................... 2-31
Inputs
Parameterizing ......................................................................................................................... 2-28
Insert
Blocks..............................................................................................................................2-26, 2-32
Inserting
Block library................................................................................................................................ 2-6
Blocks....................................................................................................................................... 2-45
Hardware.................................................................................................................................. 2-24
Software ................................................................................................................................... 2-25
Installing from a CD-ROM ............................................................................................................. 1-3
Interconnect
Blocks....................................................................................................................................... 2-28
Interconnectability
$ signals ................................................................................................................................... 2-11
of data types............................................................................................................................... 2-9
Interconnection
Deleting .................................................................................................................................... 2-32
Re-establishing......................................................................................................................... 2-32
Interconnections .......................................................................................................................... 2-44
Inverting
Block inputs ................................................................................................................................ 2-8
L
Length
Field.......................................................................................................................................... 2-64
Name........................................................................................................................................ 2-64
Link-in hardware signals in the CFC ........................................................................................... 1-29
Loading
Offline ....................................................................................................................................... 2-20
Online ....................................................................................................................................... 2-20
Prerequisites ............................................................................................................................ 2-20
User program ..................................................................................................................2-19, 2-30
Local service interface................................................................................................................. 2-46
M
Map listing ................................................................................................................................... 2-18
Module information in the CFC ................................................................................................... 1-45
Module information in the SIMATIC Manager ............................................................................. 1-44
Module names............................................................................................................................. 2-12
Block I/O................................................................................................................................... 2-12
Module status .............................................................................................................................. 2-40
Determine prerequisites ........................................................................................................... 2-40
Monitor

A5E01078201-02 - Edition 01.2008
Index
Test mode................................................................................................................................. 2-31

Monitoring
Block connections .................................................................................................................... 2-41
MPI interface ............................................................................................................................... 2-47
MPI network................................................................................................................................. 1-13
Multi-processing .......................................................................................................................... 2-19
N
Name
Length....................................................................................................................................... 2-64
Name references ......................................................................................................................... 2-13
Block I/O ................................................................................................................................... 2-13
O
Object hierarchy .......................................................................................................................... 1-12
Offline loading.....................................................................................................................1-37, 2-20
Loading interface...................................................................................................................... 1-37
Offline-Laden ............................................................................................................................... 1-37
Online help .................................................................................................................................... 1-9
Online loading.....................................................................................................................1-35, 2-20
Interfaces.................................................................................................................................. 1-35
OP connection ............................................................................................................................. 2-12
Block I/O ................................................................................................................................... 2-12
OP connection data.................................................................................................................. 2-12
Opening objects........................................................................................................................... 1-15
Operating modes ......................................................................................................................... 2-35
INIT........................................................................................................................................... 2-35
Power off .................................................................................................................................. 2-35
Prerequisites............................................................................................................................. 2-36
RUN.......................................................................................................................................... 2-35
STOP due to initialization error ................................................................................................ 2-35
STOP due to system errors......................................................................................................2-36
User stop .................................................................................................................................. 2-35
Operating status .......................................................................................................................... 1-46
Operator control and monitoring.................................................................................................. 2-15
P
Parameterizing ............................................................................................................................ 1-24
Block I/O ..........................................................................................................................2-34, 2-43
Inputs........................................................................................................................................ 2-28
Parameterizing modules.............................................................................................................. 1-28
1-5
Prerequisites
Loading..................................................................................................................................... 2-20
Operating modes...................................................................................................................... 2-36
Print
Chart......................................................................................................................................... 2-33
Print preview................................................................................................................................ 1-50
Printing ........................................................................................................................................ 1-50
Process interrupts........................................................................................................................ 2-13
Block I/O ................................................................................................................................... 2-13
PROFIBUS master ...................................................................................................................... 1-30

A5E01078201-02 - Edition 01.2008
Index
Programs
assigned ................................................................................................................................... 1-21
non-assigned............................................................................................................................ 1-21
Project
Set-up....................................................................................................................................... 2-24
Project planning data
Data flow .................................................................................................................................... 2-4
Project structure
Set-up....................................................................................................................................... 2-24
Projects........................................................................................................................................ 1-11
R
Re-establishing
Interconnection......................................................................................................................... 2-32
Reference data...................................................................................................................2-32, 2-61
Refresh rate
Changing .................................................................................................................................. 2-37
Requirements
Software ..................................................................................................................................... 2-2
Run sequence ............................................................................................................................. 2-14
Change..................................................................................................................................... 2-28
Run-time attributes ...................................................................................................................... 2-14
Run-time groups.......................................................................................................................... 2-13
Run-time properties..................................................................................................................... 2-13
S
Save project................................................................................................................................. 1-22
Select modules............................................................................................................................ 1-28
Select racks ................................................................................................................................. 1-27
Selecting
Communications interface........................................................................................................ 2-47
Service interface
Configured................................................................................................................................ 2-47
Local ......................................................................................................................................... 2-46
Setting object properties.............................................................................................................. 1-16
Setting-up the printer................................................................................................................... 1-50
Set-up
Project ...................................................................................................................................... 2-24
Project structure ....................................................................................................................... 2-24
SFC
Absolute addressing................................................................................................................... 3-9
Compilation procedure ............................................................................................................. 3-13
Configuring SFC calls................................................................................................................. 3-4
Consistency check ................................................................................................................... 3-13
Copying charts ........................................................................................................................... 3-6
Creating a jump .......................................................................................................................... 3-6
Customizing the compiler......................................................................................................... 3-12
Downloading programs ............................................................................................................ 3-14
Element of chart ......................................................................................................................... 3-3
Generate reference data ............................................................................................................ 3-4
Global addresses (operands)..................................................................................................... 3-9
How SFC works with messages............................................................................................... 3-12
Installing an SFC chart in a task / deleting from a task............................................................ 3-10

A5E01078201-02 - Edition 01.2008
Index
Introduction................................................................................................................................. 3-2
Overview of sequential control systems on the PLC................................................................ 3-16
Overview of the run-time properties ......................................................................................... 3-10
Permissible data types ............................................................................................................... 3-9
Restrictions and expansions ...................................................................................................... 3-2
Run-time attributes for the run-time group and SFC chart....................................................... 3-11
Setting-up the project structure .................................................................................................. 3-3
Specifying the run sequence ....................................................................................................3-10
STEP 7 environment .................................................................................................................. 3-3
Step, Editing addresses ............................................................................................................. 3-6
Symbolic addressing .................................................................................................................. 3-9
Transition, Editing addresses ..................................................................................................... 3-8
SFC:................................................................................................................. 3-16, 3-17, 3-18, 3-20
SIMATIC Manager......................................................................................................................... 1-4
Software
Inserting.................................................................................................................................... 2-25
Requirements ............................................................................................................................. 2-2
SS52 configuration as slave........................................................................................................ 1-30
Start
CFC .......................................................................................................................................... 2-26
Dynamic value display.............................................................................................................. 2-43
Starting
CPU .......................................................................................................................................... 2-30
SIMATIC Manager.................................................................................................................... 2-23
Starting to print ............................................................................................................................ 1-50
Station ......................................................................................................................................... 1-13
STEP 7
Components ............................................................................................................................... 2-2
T
Task ............................................................................................................................................. 2-13
Test mode.................................................................................................................................... 2-38
Activate..................................................................................................................................... 2-31
Activating .................................................................................................................................. 2-39
Change ..................................................................................................................................... 2-31
De-activating............................................................................................................................. 2-39
Monitor...................................................................................................................................... 2-31
Testing programs......................................................................................................................... 1-39
Top chart ..................................................................................................................................... 2-50
Type
$ signals ................................................................................................................................... 2-10
U
User library .................................................................................................................................. 2-49
User program
Compiling.................................................................................................................................. 2-17
Loading............................................................................................................................2-19, 2-30
V
Virtual connection names ............................................................................................................ 2-11
Block I/O ................................................................................................................................... 2-11
Virtual connections .............................................................................................................1-33, 2-11

A5E01078201-02 - Edition 01.2008
Index
Block I/O................................................................................................................................... 2-11
W
WinCC ......................................................................................................................................... 2-15

A5E01078201-02 - Edition 01.2008

D7sys Option e

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

D7sys Option e

Caricato da

Copyright:

Formati disponibili

s

Note the following:

Copyright Siemens AG 2008 All rights reserved Disclaimer of Liability

Siemens Aktiengesellschaft A5E01078201-02

Purpose of this Manual

Basic knowledge required

Validity of the Manual

D7-SYS - STEP 7, CFC and SFC configuring - SIMATIC D7-SYS

D7-SYS - STEP 7, CFC and SFC configuring - SIMATIC D7-SYS

D7-SYS - STEP 7, CFC and SFC configuring - SIMATIC D7-SYS

Service & support in Internet

D7-SYS - STEP 7, CFC and SFC configuring - SIMATIC D7-SYS

Foreword ........................................................................................................................................ iii

1 Basic software........................................................................................................................ 1-1

D7-SYS - STEP 7, CFC and SFC configuring - SIMATIC D7-SYS vii

1.5.8 Working in the configuration table .......................................................................... 1-30

viii D7-SYS - STEP 7, CFC and SFC configuring - SIMATIC D7-SYS

2.1.4 Block interconnections.............................................................................................. 2-9

D7-SYS - STEP 7, CFC and SFC configuring - SIMATIC D7-SYS ix

2.6 Chart reference data-documentation ...................................................................... 2-61

x D7-SYS - STEP 7, CFC and SFC configuring - SIMATIC D7-SYS

3.4.2 How a chart is executed [SD] ................................................................................. 3-16

Index .............................................................................................................................................. I-1

D7-SYS - STEP 7, CFC and SFC configuring - SIMATIC D7-SYS xi

Overview 1.1 Installation and start 1-2

1.2 User interface 1-6

1.3 STEP 7 projects and basic handling 1-11

1.4 Creating and handling projects 1-18

1.5 Configuring and parameterizing modules 1-24

1.6 Creating communication connections 1-31

1.7 Loading programs 1-35

1.8 Testing programs 1-39

1.9 Diagnostics 1-41

1.10 Archiving user programs 1-47

1.11 Printing 1-50

D7-SYS - STEP 7, CFC and SFC configuring - SIMATIC D7-SYS 1-1

1.1 Installation and start

1.1.1 System requirements

− Pentium P133 processor (or higher) and

− RAM memory expansion ≥ 64 MByte (we recommend 128 MByte)

• Color monitor, keyboard and mouse, which are supported by Microsoft

− Recommended screen resolution: 1024 x 768 (or higher)

• Minimum 1 MB free memory on drive C for setup (setup files are

• For offline loading of the compiled programs in the memory modules

− Plug-in PC card (PCMCIA).

− External OmniDrive Professional device (refer to the “readme file”)

− Device to program Micro Memory Cards (MMC); appropriate slot in

• For online loading in CPUs and for testing (optional):

− An MPI interface between SIMATIC PG or PC and the station, i. e.

1-2 D7-SYS - STEP 7, CFC and SFC configuring - SIMATIC D7-SYS

You will require the following software:

• Basic STEP 7 software,

• CFC option package,

• Possibly option package SFC,

1.1.2 Installing the software

Overview The supplied software includes a setup program, which automatically

If required, install these products in the following sequence:

2. Basic STEP 7 software

3. CFC option package

4. Possible SFC option package

1.1.2.1 Installing from CD-ROM

When installing from a CD-ROM, proceed as follows:

1. Insert the CD-ROM in your PC.