simatic component based automation configuring plants with ... · component based automation...

Preface, ContentsComponent based Automation- Overview 1

Installing SIMATIC iMap 2

Creating PROFInet Components 3

Working with SIMATIC iMap 4

Configuring Plants 5

Online Operation 6SIMATIC Devices forComponent based Automation 7

Appendix

References

Abbreviation List

GlossaryIndex

SIMATIC

Component based AutomationConfiguring Plantswith SIMATIC iMap

Manual

Edition 12/2002A5E00122598-03

Copyright © Siemens AG 2001-2002 All rights reservedThe reproduction, transmission or use of this document or itscontents is not permitted without express written authority.Offenders will be liable for damages. All rights, including rightscreated by patent grant or registration of a utility model or design,are reserved.

Siemens AGBereich Automatisierungs- und AntriebstechnikGeschaeftsgebiet Industrie-AutomatisierungssystemePostfach 4848, D- 90327 Nuernberg

Disclaimer of LiabilityWe have checked the contents of this manual for agreement withthe hardware and software described. Since deviations cannot beprecluded entirely, we cannot guarantee full agreement. However,the data in this manual are reviewed regularly and any necessarycorrections included in subsequent editions. Suggestions forimprovement are welcomed.

©Siemens AG 2001-2002Technical data subject to change.

Siemens Aktiengesellschaft A5E00122598

Safety Guidelines

This manual contains notices intended to ensure personal safety, as well as to protect the products andconnected equipment against damage. These notices are highlighted by the symbols shown below andgraded according to severity by the following texts:

! Dangerindicates that death, severe personal injury or substantial property damage will result if properprecautions are not taken.

! Warningindicates that death, severe personal injury or substantial property damage can result if properprecautions are not taken.

! Cautionindicates that minor personal injury can result if proper precautions are not taken.

Cautionindicates that property damage can result if proper precautions are not taken.

Noticedraws your attention to particularly important information on the product, handling the product, or to aparticular part of the documentation.

Qualified Personnel

Only qualified personnel should be allowed to install and work on this equipment. Qualified persons aredefined as persons who are authorized to commission, to ground and to tag circuits, equipment, andsystems in accordance with established safety practices and standards.

Correct Usage

Note the following:

! WarningThis device and its components may only be used for the applications described in the catalog or thetechnical description, and only in connection with devices or components from other manufacturerswhich have been approved or recommended by Siemens.

This product can only function correctly and safely if it is transported, stored, set up, and installedcorrectly, and operated and maintained as recommended.

Trademarks

SIMATIC®, SIMATIC HMI® and SIMATIC NET® are registered trademarks of SIEMENS AG.

Third parties using for their own purposes any other names in this document which refer to trademarks mightinfringe upon the rights of the trademark owners.

Component based Automation Configuring Plants with SIMATIC iMapA5E00122598-03 iii

Preface

Purpose of the ManualThis manual provides you with a complete overview of programming with SIMATICiMap. It supports you while creating PROFInet components and configuring plants.

The manual is intended for persons with the appropriate qualifications who areinvolved in configuration, commissioning, and service of programmable logiccontrollers with component based automation.

We recommend that you familiarize yourself with the example in the "GettingStarted with SIMATIC iMap" documentation. This will help you to get to knowSIMATIC iMap quickly.

Required Basic KnowledgeTo understand the manual, you should have general experience of automationengineering.You should also be familiar with working on computers or PC-type machines (forexample, programming devices) with the Windows 2000 operating system. SinceSIMATIC iMap uses the STEP 7 platform, you should also be familiar with workingwith the standard software described in the "Programming with STEP 7 V5.2"manual.

Where is this Manual valid?The manual is valid for the SIMATIC iMap V1.2 software package.

Preface

Component based Automation Configuring Plants with SIMATIC iMapiv A5E00122598-03

Changes compared to the previous version• In SIMATIC iMap V1.2

New functionality for configuring, commissioning and testing plants:

- Online Testing with the Variable Table � Chapter 6.8

- Check online accessibility of the devices � Chapter 6.5

- Find and replace PROFInet components � Chapters 4.3 and 5.11

- Configure substitute values � Chapter 5.7.8

- Clearer user interface with improved navigation � Chapter 4.4.1

- Start other applications from SIMATIC iMap � Chapter 4.5

• In SIMATIC iMap V1.2, STEP 7 AddOnExtended configuration options when creating PROFInet components:

- intelligent DP slaves on the local PROFIBUS of a PROFInet device �Chapter 7.1.2

- intelligent DP slaves with local PROFIBUS � Chapter 7.1.2

- one integral HMI device on the local PROFIBUS or local MPI bus of aPROFInet or PROFIBUS device � Chapter 7.1.7

Place of this Documentation in the Information EnvironmentThis manual is part of the SIMATIC iMap documentation package. Thedocumentation is installed with the software and includes the following electronicmanuals in PDF format:

• Component Based Automation and SIMATIC iMap

• Getting Started with SIMATIC iMap

• Commissioning Systems, TutorialThe entire documentation is available for you as HTML help.

Preface

Component based Automation Configuring Plants with SIMATIC iMapA5E00122598-03 v

Finding Your WayThis manual is organized into the following subject areas:

• Chapter 1 provides you with an overview of the entire concept and the productstructure of component based automation.

• Chapter 2 describes how to install the software

• Chapter 3 describes how to create PROFInet components

• Chapters 4 to 6 describe how to work with SIMATIC iMap

• Chapter 7 describes the special features when using SIMATIC devices inSIMATIC iMap

• The appendices contain a summary of the control elements for your reference.

• The glossary defines important technical terms.

• The index helps you to quickly find text on important key words.

ConventionsMenu commands are printed in bold print, for example, Project > Save.

Further SupportIf you have any technical questions, please get in touch with your Siemensrepresentative or agent responsible.

http://www.siemens.com/automation/partnerhttp://www.ad.siemens.de/cba/

Training CentersSiemens offers a number of training courses to familiarize you with the SIMATICS7 automation system. Please contact your regional training center or our centraltraining center in D 90327 Nuremberg, Germany for details:Telephone: +49 (911) 895-3200.Internet: http://www.sitrain.com

http://www.siemens.com/automation/partner

http://www.ad.siemens.de/cba/

http://www.sitrain.com

Preface

Component based Automation Configuring Plants with SIMATIC iMapvi A5E00122598-03

A&D Technical SupportWorldwide, available 24 hours a day:

Beijing

Nuernberg

Johnson City

Worldwide (Nuernberg)Technical Support

24 hours a day, 365 days a year

Phone: +49 (0) 180 5050-222

Fax: +49 (0) 180 5050-223

E-Mail: [email protected]

GMT: +1:00

Europe / Africa (Nuernberg)Authorization

Local time: Mon.-Fri. 8:00 to 17:00

Phone: +49 (0) 180 5050-222

Fax: +49 (0) 180 5050-223

E-Mail: [email protected]

GMT: +1:00

United States (Johnson City)Technical Support andAuthorizationLocal time: Mon.-Fri. 8:00 to 17:00

Phone: +1 (0) 423 262 2522

Fax: +1 (0) 423 262 2289

E-Mail: simatic.hotline@

sea.siemens.com

GMT: -5:00

Asia / Australia (Beijing)Technical Support andAuthorizationLocal time: Mon.-Fri. 8:30 to 17:30

Phone: +86 10 64 75 75 75

Fax: +86 10 64 74 74 74

E-Mail: adsupport.asia@

siemens.com

GMT: +8:00The languages of the SIMATIC Hotlines and the authorization hotline are generally German and English.

Preface

Component based Automation Configuring Plants with SIMATIC iMapA5E00122598-03 vii

Service & Support on the InternetIn addition to our documentation, we offer our Know-how online on the internet at:http://www.siemens.com/automation/service&support

where you will find the following:

• The newsletter, which constantly provides you with up-to-date information onyour products.

• The right documents via our Search function in Service & Support.

• A forum, where users and experts from all over the world exchange theirexperiences.

• Your local representative for Automation & Drives via our representativesdatabase.

• Information on field service, repairs, spare parts and more under "Services".

http://www.siemens.com/automation/service&support

Preface

Component based Automation Configuring Plants with SIMATIC iMapviii A5E00122598-03

Contents

Component based AutomationA5E00122598-03 vii

Contents1 Component based Automation - Overview.........................................................................1-1

1.1 Product Overview..............................................................................................1-11.2 PROFInet components......................................................................................1-31.3 Technological function ......................................................................................1-71.4 Devices of PROFInet Components.................................................................1-101.5 New Engineering Concept with SIMATIC iMap ..............................................1-121.6 User Documentation for PROFInet and SIMATIC iMap .................................1-17

2 Installing SIMATIC iMap........................................................................................................2-1

2.1 Requirements....................................................................................................2-12.2 Installation .........................................................................................................2-3

3 Creating PROFInet Components..........................................................................................3-1

3.1 Creating PROFInet Components ......................................................................3-13.2 Define the Devices and Their Functions...........................................................3-2

4 Working with SIMATIC iMap .................................................................................................4-1

4.1 Starting SIMATIC iMap .....................................................................................4-14.2 Help Functions in SIMATIC iMap......................................................................4-24.3 Operating Philosophy........................................................................................4-34.3.1 Objects and Object Hierarchy ...........................................................................4-34.3.2 Working with Objects ........................................................................................4-54.4 Windows and Views ........................................................................................4-104.4.1 SIMATIC iMap User Interface .........................................................................4-104.4.2 Plant View .......................................................................................................4-124.4.3 Network view...................................................................................................4-144.4.4 Project Window ...............................................................................................4-174.4.5 Library Window ...............................................................................................4-184.4.6 Preview Window..............................................................................................4-204.4.7 Diagnostic Window..........................................................................................4-234.4.8 Diagnostic window, "Variable table" tab..........................................................4-264.4.9 Information window .........................................................................................4-274.5 Setting Up and Calling Tools ..........................................................................4-29

5 Configuring Plants.................................................................................................................5-1

5.1 Main procedure .................................................................................................5-15.2 Working with Projects........................................................................................5-25.2.1 Creating a New Project .....................................................................................5-25.2.2 Opening and Closing Projects ..........................................................................5-25.2.3 Saving and Archiving Projects ..........................................................................5-45.2.4 Generating a Project .........................................................................................5-7

Contents

Component based Automationviii A5E00122598-03

5.2.5 Documenting and Printing a Project ...............................................................5-105.3 Working with Libraries.....................................................................................5-125.3.1 Creating a New Library ...................................................................................5-125.3.2 Opening and Closing Libraries........................................................................5-135.3.3 Importing PROFInet Components...................................................................5-145.3.4 Administering Libraries....................................................................................5-155.3.5 Archiving and Retrieving Libraries ..................................................................5-165.4 Inserting PROFInet Components into a SIMATIC iMap Project .....................5-185.5 Interconnecting Technological Functions........................................................5-205.5.1 Interconnecting with Constant Values.............................................................5-245.5.2 Moving Interconnections .................................................................................5-265.6 Coupling Devices in the Network View ...........................................................5-275.7 Looking Up And Modifying Properties.............................................................5-305.7.1 Addresses of PROFInet Devices ....................................................................5-315.7.2 Assigning Addresses.......................................................................................5-335.7.3 Password Protection for iMap Projects ...........................................................5-345.7.4 Naming Conventions.......................................................................................5-355.7.5 Generation status............................................................................................5-365.7.6 Setting the Transfer Frequency ......................................................................5-375.7.7 Configure substitute values.............................................................................5-395.8 Creating Subordinate Charts ..........................................................................5-415.9 Storing Data in SIMATIC iMap........................................................................5-435.10 Editing in the Vendor-Specific Programming and Configuration Tool ............5-465.11 Working with Modified PROFInet Components ..............................................5-485.12 Creating an OPC Symbol File.........................................................................5-495.13 OPC Information Variables for SIMATIC iMap ...............................................5-50

6 Online operation ....................................................................................................................6-1

6.1 Overview of the Online Functions .....................................................................6-16.2 Diagnostic Concept for PROFInet Components ...............................................6-36.3 Diagnosing PROFInet Components..................................................................6-66.4 Comparing the Online and Offline Data ............................................................6-86.5 Check Accessibility of the Devices .................................................................6-106.6 Downloading Programs and Interconnections ................................................6-146.7 Displaying and Setting Online Values in the Plant View.................................6-206.8 Online Testing with the Variable Table ...........................................................6-246.8.1 Creating the Variable Table ............................................................................6-246.8.2 Online Monitoring and Control of Variables ....................................................6-28

7 SIMATIC Devices for Component based Automation........................................................7-1

7.1 SIMATIC Devices as PROFInet Components ..................................................7-17.1.1 Overview of SIMATIC Devices..........................................................................7-17.1.2 Configurations for PROFInet Components .......................................................7-67.1.3 Central Processing Units.................................................................................7-127.1.4 WinLC PN .......................................................................................................7-197.1.5 Distributed Peripherals....................................................................................7-227.1.6 DP/DP Coupler................................................................................................7-257.1.7 HMI Devices in PROFInet Components .........................................................7-297.2 Creating PROFInet Components with STEP 7 ...............................................7-347.2.1 Basic procedure ..............................................................................................7-34

Contents

Component based AutomationA5E00122598-03 ix

7.2.2 Create a Project in STEP 7.............................................................................7-357.2.3 Properties of the Interface DB.........................................................................7-367.2.4 Special Features of DP Slaves .......................................................................7-457.2.5 Creating the Interface DB................................................................................7-507.2.6 Creating PROFInet Components in SIMATIC Manager .................................7-627.2.7 Importing PROFInet Components to a Library................................................7-687.2.8 Modifying PROFInet Components ..................................................................7-697.2.9 System Library ................................................................................................7-707.2.10 Properties of PROFInet Components of SIMATIC Devices............................7-737.2.11 Version numbers of PROFInet components ...................................................7-757.3 Plants with SIMATIC Devices .........................................................................7-767.3.1 Special Features of Plants with SIMATIC Devices .........................................7-767.3.2 Using SIMATIC devices in Online Mode.........................................................7-817.3.3 Editing with STEP 7 ........................................................................................7-837.3.4 Setting the PG/PC Interface............................................................................7-857.3.5 Assigning the PG/PC ......................................................................................7-887.3.6 Setting up the OPC Server .............................................................................7-937.4 Off-The-Shelf PROFInet Components ............................................................7-947.4.1 Overview of the off-the-shelf PROFInet components .....................................7-947.4.2 IE/PB Link .......................................................................................................7-947.4.3 Diagnostic Repeater........................................................................................7-97

8 Reference................................................................................................................................8-1

8.1 Toolbar ..............................................................................................................8-18.2 Menu bar ...........................................................................................................8-38.3 Actions ..............................................................................................................8-88.4 Error numbers .................................................................................................8-118.5 File Types........................................................................................................8-13

9 Abbreviations.........................................................................................................................9-1

10 Glossary..............................................................................................................................10-1

Index

Component based AutomationA5E00122598-03 1-1

Component based Automation -Overview 11.1 Product Overview

What is Component based Automation?As part of Totally Integrated Automation (TIA), Component based Automation is aconcept for implementing modular, distributed automation applications based on openstandards.

This concept meets the demand for increased modularization in the field of plant andmachine construction by extensively distributing the intelligent processing required.Component based Automation allows different types of programmable controller to beused as standardized automation components- known as PROFINet components-in large-scale systems.

Component based Automation is implemented by the PROFInet specification forprogrammable controllers and by means of suitable engineering tools such asSIMATIC iMap.

What is PROFInet ?To implement Component based Automation, TIA uses the PROFInet specification(draft) issued by the PROFIBUS User Organisation e.V. (PNO). The PROFInetstandard defines a cross-vendor communication, automation and engineering model.

PROFINet has the following objectives:

• Open, distributed automation across networks

• Integrated communication via field bus and Ethernet

• Use of open IT standards

Programmable controllers that conform to the PROFInet standard must have certaincommunication interfaces based on Microsoft DCOM (Distributed Component ObjectModel).

Component based Automation - Overview

Component based Automation1-2 A5E00122598-03

What is SIMATIC iMap?SIMATIC iMap is a cross-vendor engineering tool for configuring PROFInetapplications. It brings together distributed automation applications in a graphical formatso that they can be displayed for the entire plant. All the PROFInet componentsneeded are provided in a standardized format in the form of library elements. EveryPROFInet component is a discrete automation function with inputs and outputs which,in turn, can be combined with other functions. The interconnections usecommunication links via DCOM mechanisms. SIMATIC iMap can download thecontents of PROFInet components and the associated interconnections to the devicesin the plant. During commissioning and while the plant is in operation, you can useSIMATIC iMap to look up process data and diagnostic data concerning the devices aswell as modify parameters and project data for testing purposes.

The new engineering tool can also integrate device-specific programming andconfiguration tools.

Product RangeThe product range for Component based Automation based on the PROFInetspecification essentially comprises:

• PROFInet devices that conform to the PROFInet specification.

• SIMATIC iMap - the engineering tool for Component based Automation. It is used toconfigure plants and provide a link to device-specific programming, configurationand diagnostic tools.

A wide range of existing automation and field devices from various vendors can alsobe used as PROFINet components.

The PNO has also published a specification for the communication mechanisms andengineering model. This allows other devices to be made PROFInet-compliant, andproprietary configuration and programming tools to be linked to SIMATIC iMap.



1.2 PROFInet components

What are PROFInet Components?The mechanical, electrical and electronic parts of a programmable controller thatperform a specific technological function within the automation system or productionprocess, combined with the associated control program, form an independenttechnological submodule. If this technological submodule meets the communicationrequirements of the PROFInet standard, then it can be used to create a PROFInetcomponent.

Figure 1-1 Creating a PROFInet component from a technological submodule

The concept is based on COM/DCOM (Microsoft's (Distributed) Component ObjectModel), a data and communication model that is widely used in the world of WindowsPCs. It defines the protocol for exchanging data between COM-based softwarecomponents from different vendors.

In Component based Automation, all the functionality of a technological module isencapsulated in a single component. A PROFInet component is the mapping of atechnological submodule - i.e. an automation unit with defined functionality in thePROFInet standard. PROFInet components are modular and thus can be easilyassembled and reused, greatly simplifying the process of configuring an automationsystem.



A PROFInet component incorporates all the hardware configuration data, the moduleparameters and the associated user program. It is made up of:

• an (optional) technological (software) function and

• the associated device

as illustrated in the diagram above.

The technological function of the component comprises the interface to otherPROFInet components in the form of interconnectable inputs and outputs.

The device is the representation of the physical programmable controller or fielddevice, including any peripheral devices, sensors and actuators, the mechanicalsystem and the device's firmware.

Communication between PROFInet components is based on DCOM mechanisms andis independent of their internal functionality. The working data and the data fordiagnostics or visualization are made available to the other communicating devices in astandardized form. Standardization of the component interface is part of the PROFInetspecification published by the PROFIBUS User Organization e.V.

How are PROFInet components created?The programmable controller or field device of the PROFInet component is configuredand programmed using the configuration and programming tool supplied by the devicemanufacturer. A PROFInet component is then created from the configuration of theprogrammable controller and its user program, using a simple menu command, forexample. The device's functionality is also encapsulated with the application-specificprograms. From the outside, only the component interfaces that are needed forinteraction across a machine or plant or for diagnostics, visualization and verticalintegration are accessible.

The technological interfaces of a PROFInet component are written in XML (ExtendedMarkup Language) and are saved in an XML file. XML allows you to displayinformation in a platform and vendor-independent format. A specification of the XMLfile structure is given in the PROFInet engineering model.

The PROFInet component can incorporate information on the hardware configurationand on the user program, if necessary, in a device specific form.



Properties of PROFInet components• Modularization and reusability

The concept of the PROFInet component allows extensive modularization ofautomation systems. PROFInet components can be reused as often as necessaryin different automation systems.

• Constant communication by support for the PROFInet specification

PROFInet defines a cross-vendor communication standard based on COM/DCOM.Each PROFInet component provides a device interface for communication withother components on the Ethernet or PROFIBUS, regardless of the internalfunctionality. The PROFInet specification describes the open communicationinterface for PROFInet-compliant devices.

• Cross-vendor engineering

The technological functions of individual devices are programmed in vendor-specifictools. However, cross-vendor engineering tools such as SIMATIC iMap are used forthe plant-wide interconnection of technological functions, since they allow productsfrom different vendors to be incorporated into PROFInet communication. Thus, allfield device and programmable controller vendors have to do is extend theirprogramming and configuration tools to allow them to be linked to the device-neutral engineering tool (e.g. SIMATIC iMap).

Programmable and Fixed FunctionalityIn an intelligent device, the application-specific functionality is defined by the userprogram that is downloaded to the device. More simple devices, such as drives or fielddevices, do not have their own user programs. The functionality of such devices isintegrated into the firmware. We therefore differentiate between PROFInetcomponents:

• with programmable functionality

The component has its own user program that can be downloaded from SIMATICiMap to the device.

• with fixed functionality

These components do not have their own user program that can be downloaded tothe device.



Representation of PROFInet ComponentsSIMATIC iMap represents PROFInet components in different ways:

• As part of a library (window 1), the PROFInet components are represented by aseparate icon.

• In a SIMATIC iMap project, the PROFInet components are shown in different views:the technological function in the plant view (window 2), and the device in thenetwork view (window 3).

Figure 1-2 Representation of a PROFInet component in SIMATIC iMap



1.3 Technological function

Definition of a technological functionThe technological function of a PROFInet component comprises the application-specific functionality of a programmable controller or field device and the componentinterface for communication with other PROFInet components.

The term "technological function“ is often occurs in automation technology, and alwaysin association with the implementation of specific functions within an automationprocess, e.g. positioning, counting, controlling motors, cam control, etc. In most cases,it relates to individual functions within the programmable controllers. In terms ofComponent based Automation, a technological function means the entire functionalityof a device or group of devices, whereas the associated hardware is represented by adevice in the SIMATIC iMap network view.

Component InterfaceThe component interface defines the connectors - i.e. the inputs and outputs - of thePROFInet component. The connectors represent the external communication interfacethat is accessed via Ethernet or PROFIBUS. Every connector is characterized by thefollowing features, as defined in the user program for the PROFInet component:

• Direction: Every connector has a direction – it is either an input or an output.

• Interconnectability in SIMATIC iMap: Inputs and outputs that are visible inSIMATIC iMap may be interconnected.

Non-interconnectable connectors are not represented graphically in SIMATIC iMap.They can be accessed via other communication mechanisms, e.g. OPC (OLE forProcess Control), and are generally used for operator control and processmonitoring.

• Name

Any connector names can be selected, provided that it conforms to the namingconventions and is no more than 24 characters long.

• Data type

A data type, e.g. BOOL, I1 or U2, is defined for each connector. Complex datatypes, such as arrays, are also supported.

• Value

While the plant is in operation, the current value of a connector can be displayedonline in SIMATIC iMap. Online values of PROFInet inputs may also be modified.



PROFInet data typesThe following PROFInet data types, which conform to Microsoft OLE 2.0, aresupported for the connectors of technological functions.

Table 1-1 Data types

Data type Range of values

BOOL TRUE / FALSEI1 -128 to +127UI1 0 to 255R4 3.4E +/- 38I2 -32,768 to +32,767UI2 0 to 65,535I4 2,147.483.648 to +2,147,483.647UI4 0 to 4,294,967,295DATE* 01.01.1900 00:00:00 to 31.12.9999 23:59:59BSTR String of charactersARRAY** One-dimensional

* Depends on the device type

**An ARRAY can be formed from the PROFInet data types: I1, UI1, I2, UI2, I4 and UI4. The maximum length depends on the amount of memory in the device.

InterconnectionsIn SIMATIC iMap, an interconnection is the connection between an output and aninput. An output can be interconnected to one or more inputs. Once theinterconnections have been downloaded to the programmable controllers, thecorresponding communication links are automatically established between sendersand receivers.



Representation of technological functionsThe technological functions of a plant are represented by blocks with interconnectableinputs and outputs. The inputs are arranged on the left-hand side and the outputs onthe right-hand side of a block. Interconnections are represented by connecting lines.

Figure 1-3 Interconnected Technological Functions

Key:

1. Inputs

2. Outputs

3. Interconnection



1.4 Devices of PROFInet Components

PROFInet and PROFIBUS DevicesThe device is the part of the PROFInet component that contains the hardware-specificdata for that component.

In Component based Automation, a device is a representation of the physical devicefor which the PROFInet component was created. Such devices include programmablecontrollers, intelligent field devices and peripheral, hydraulic and pneumatic devices.

The main feature of a device is that it is integrated into the PROFInet communicationvia an Ethernet or PROFIBUS. We differentiate between the following types of devicedownstream of the bus connectors:

• PROFInet devices

A PROFInet device always has an Ethernet connector. A PROFInet device mayalso have a PROFIBUS connector, and thus act as a master with proxyfunctionality.

• PROFIBUS devices

A PROFIBUS device has just one PROFIBUS connector and is always a slave. Itcannot participate directly in PROFInet communication, and must always beintegrated via a PROFIBUS master with proxy functionality.

The PROFInet device with proxy functionality acts as a proxy master with respect toother PROFIBUS devices. The proxy functionality allows a PROFIBUS device tocommunicate with all participants in the PROFInet communication, as well as with itsown master.

Representation of the DevicesPROFInet and PROFIBUS devices are represented in the SIMATIC iMap networkview.

Designation Representationin SIMATIC iMap

Example

PROFInet device on theEthernet



Designation Representationin SIMATIC iMap

Example

PROFInet device on theEthernet (with localPROFIBUS)

PROFInet device on theEthernet and acting as aPROFIBUS master withproxy functionality

PROFInet device on theEthernet and acting as amaster on the PROFIBUS(with local PROFIBUS)

PROFIBUS device (Slaveon the PROFIBUS)



1.5 New Engineering Concept with SIMATIC iMap

Device-independent engineering conceptSIMATIC iMap is a device-independent engineering tool for configuring, commissioningand operating plants using PROFInet components.

In addition to the technological plant view, SIMATIC iMap also provides a link todevice-specific or proprietary programming and configuration tools for programmablecontrollers and intelligent field bus devices.

Figure 1-4 SIMATIC iMap engineering concept



The main engineering procedureThe following steps must be carried out in order to structure and operate anautomation system using SIMATIC iMap:

1. Planning the Plant

The plant planner defines the following aspects:

– Which functions are needed

– Which programmable controllers and field devices are to be used

– Which functions can be combined to create reusable technological submodules

– NEW features of Component based Automation are the definition of componentinterfaces and the interaction between components, as well as the definition ofthe variables for diagnostic and visualization purposes.

2. Creating PROFInet Components

The plant or machine constructor creates the PROFInet component using thedevice-specific configuration and programming tool by:

– Configuring and programming the hardware

– Creating the user program

– Creating the description of the component interface

– Testing the technological submodule

– Creating the PROFInet component (XML file and associated data)

– Optional: Importing the PROFInet component into a SIMATIC iMap library

3. Configuring the plant in SIMATIC iMap

The plant project engineer creates the project in SIMATIC iMap by:

– Opening an existing library or creating a new library

– If necessary: Importing the new PROFInet component into the library

– Inserting the PROFInet components into the project

– Networking the devices in the network view

– Assigning the device addresses (IP address and/or PROFIBUS address) to thedevices (this step is device-specific)

– Interconnecting the technological functions in the plant view



4. Commissioning and testing the plant

The plant operator is responsible for the following tasks:

– Commissioning individual devices

– Downloading project data to the devices in the plant

– If necessary: Fine-tuning devices and technological functions in the device-specific engineering tool.

– Testing the plant

– Creating the symbol data for access via OPC

5. Operating the plant

– Monitoring and modifying process data online (vertical integration)

– Diagnosing faults in the plant

– Operator control and process monitoring

– Carrying out maintenance and modifications

Support from SIMATIC iMapSIMATIC iMap provides the following support for plant engineering:

• Storage of in-house and off-the-shelf PROFInet components in libraries

Libraries are used to administer PROFInet components that you create yourself orpurchase. The content of these libraries can be configured as required.

• Interconnection of technological functions in the plant view

In the plant view, you can position and interconnect technological functionsgraphically, and easily check and modify their properties.

• Networking of devices in the network view

In the network view, you can link devices graphically to a PROFIBUS or Ethernetsubnet, and assign the corresponding addresses.

• Online monitoring and control of variables

You can access the process data online at any time by using a variable table,incorporating HMI devices such as ProTool/Pro into your plant via PROFInet orusing OPC-based client programs.

• Diagnosing PROFInet devices and technological functions

The separate diagnostic window constantly displays the current status of PROFInetdevices and technological functions. while the online/offline comparison allows youto determine whether it is time to download to a PROFInet device.



• Representation of the project in a hierarchical tree structure

All parts of the plant needed for easy navigation and other administration functionswithin the project are clearly displayed.

• Automatic creation of the plant documentation

Full documentation of the configured plant, including all devices, technologicalfunctions and their connectors, plus a graphical representation of the networkingand interconnections can be created automatically in SIMATIC iMap.

Device-specific configuration and programming toolsSIMATIC iMap provides the following functions for linking to device-specificconfiguration and programming tools:

• Software for creating PROFInet components using the device-specific configurationand programming tool. SIMATIC iMap STEP 7 AddOn can also be used to createPROFInet components for SIMATIC devices in STEP 7, for example.

• Access to vendor-specific tools for configuring and diagnosing devices.



Transparent Data AccessPROFInet communication supports access to process data from different levels of theplant. Using PROFInet, you can now use standard communication and IT mechanisms,such as OPC, XML, COM/DCOM, in your automation system, which means that office-bound company managers can directly access the data from PROFInet devices at thecontrol and production levels.

Figure 1-5 Access to Process Data



1.6 User Documentation for PROFInet and SIMATIC iMap

Types of documentationThe user documentation for PROFInet and SIMATIC iMap is subdivided into specifictarget groups:

Title Content Target group

Component basedAutomation - Overview(this document)

Introduction to Component based Automation, PROFInetcomponents and SIMATIC iMap

BeginnersPlant planners

Getting Started(available as a separatePDF file)

Step-by-step instructions based on a specific example• Creating PROFInet components with the STEP 7 AddOn• Working with SIMATIC iMap• Online monitoring and diagnostics

Beginners

Installing SIMATIC iMap Description of the requirements and procedure Systemadministrators

Creating PROFInetComponents

Description of the main procedure MachineconstructorsPlantconstructors

Working with SIMATICiMap

Detailed descriptions and instructions• User interface and controls• Control options

Plant designers

Configuring a plant Detailed descriptions and instructions• Placing and interconnecting technological functions• Networking PROFInet devices

Plant designers

Online Mode Detailed descriptions and instructions• Accessing variables online• Diagnostics

Plant operators

SIMATIC devices forComponent basedAutomation

• Information on the use of programmable controllers andfield devices as PROFInet components

• Detailed descriptions and instructions for creatingPROFInet components in the device-specificconfiguration and programming tool (STEP 7 Add-on)

MachineconstructorsPlantconstructors

Commissioning a plant -tutorial(available as a separatePDF file)

Step-by-step instructions for configuration andcommissioning plants with SIMATIC devices:• Creating PROFInet components with the STEP 7 AddOn• Configuring Plants with SIMATIC iMap• Commissioning plants

Plant operators



Accessing the DocumentationAll the documentation is available as HTML help in SIMATIC iMap and as a printablePDF file. You can also call up context-sensitive help on dialogs and messages.

Additional InformationThe associated product documentation contains information on related topics, e.g.descriptions of individual devices.


Installing SIMATIC iMap 22.1 Requirements

Hardware requirementsThe computer on which SIMATIC iMap is installed must have at least the followingconfiguration:

• 500 MHz Pentium processor or faster (1 GHz is recommended)

• At least 256 MB RAM (512 MB is recommended)

General software requirementsMicrosoft Windows 2000 Professional, version V5.0 or later (build 2195: servicepack 3) must be installed.

You will need administrator rights in order to install SIMATIC iMap.

You will need at least primary user rights in order to use SIMATIC iMap.

Before installing SIMATIC iMap, you must first install the add-on software from theproduct CD-ROM.

• Microsoft Internet Explorer, V6.0 SP1 or later

• Microsoft XML Parser V4.0 SP1

• Adobe Acrobat Reader, V4.0 or later

Installing SIMATIC iMap


Software requirements for SIMATIC devicesIf you are using PROFInet components of SIMATIC devices, you will also need thefollowing software packages:

• STEP 7 V5.1, SP6 or later, including NCM for Industrial Ethernet and PROFIBUS or

– STEP 7 V5.2

– STEP 7 Professional V5.1 + SP6

– STEP 7 Professional V5.2

• SIMATIC NET IE SOFTNET-PG, V6.0 + SP5 or later

• Software required for the SIMATIC devices used:

Device/Function Software required

WinAC PN WinAC PN V1.1SIMATIC NET IE SOFTNET-S7, V6.0 + SP5 orlater

HMI Process Visualization ProTool/Pro Configuration, V6.0 + SP2 or laterAccess to process variables via OPC SIMATIC NET PN OPC Server, V6.0 SP6 or

laterAccess to process variables via OPC SIMATIC NET IE SOFTNET-S7, V6.0 SP5 or

laterSIMATIC NET PN OPC Server, V6.0 SP6 orlater

More important information...on SIMATIC iMap can be found in the readme file.

Installing SIMATIC iMap


2.2 Installation

RequirementThe conditions described in the "Requirements" section must be fulfilled.

ProcedureThe procedure for installing the SIMATIC iMap software is as follows:

1. Insert the "SIMATIC iMap" CD into the CD-ROM drive. The setup program startsautomatically. If this is the case, you can continue from step 4, otherwise start fromstep 2.

2. Select the CD-ROM drive in Windows Explorer.

3. Double click on the setup.exe file to start the setup program. The setup program willinstall the entire SIMATIC iMap program and the necessary software packages.

4. Run the necessary setup programs in the order specified by clicking on thehyperlinks in the installation instructions.

NoteYou will be prompted to restart the computer after installing some softwarepackages. Please restart your computer when prompted to do so by the setupprogram.

Please follow the notes on installing and using SIMATIC iMap in the readme file, whichis also on the CD-ROM.


Creating PROFInet Components 33.1 Creating PROFInet Components

RulePROFInet components are created using device-specific configuration andprogramming tools. The XML file for the PROFInet component must conform to thePROFInet specification. Other component data may be provided in a device-specificformat.

Basic ProcedureThe following steps are required to create PROFInet components:

Specifying the devices and their functions

Configuring, programming and testingTechnological Functionsin manufacturer-specific Tool

Creating PROFInet Components

Modifying PROFInet Components (optional)

Figure 3-1 Steps required

Creating PROFInet Components


Further information...on the PROFInet specification can be found at the PNO website (PROFIBUS UserOrganization)

http://www.profibus.com/profibus.html

• At Downloads you will find PROFInet – Architecture, Description and Specification

• At Technical Description > PROFInet you will find an introduction to PROFInet.

A description of how to create PROFInet components from SIMATIC devices can befound in the section entitled "Creating PROFInet Components with STEP 7".

3.2 Define the Devices and Their Functions

RecommendationsSeparate PROFInet components should be formed from parts of the plant that:

• occur more than once (reusable ) or/and

• generate high communication traffic over the Ethernet or PROFIBUS.

• form a discrete mechanical and electrical unit.

PROFIBUS devices can only be used in conjunction with a PROFInet device that actsas a PROFIBUS master with proxy functionality.–

Basic procedure1. Break down the plant into individual, discrete technological modules so that each

module forms a separate component within the overall project.

2. Define the programmable controllers that you need for the individual PROFInetcomponents, including any peripheral devices.

3. Define the interfaces of the PROFInet components, i.e. the inputs and outputs forcommunication with other components.

4. Define the required communication networks Ethernet or PROFIBUS.

5. Write the programs with the component functions.

Further information...Information on the creation of PROFInet components can be found in the device-specific and vendor-specific descriptions, e.g. in the section entitled "SIMATIC Devicesfor Component based Automation".


Working with SIMATIC iMap 44.1 Starting SIMATIC iMap

RequirementSIMATIC iMap must be installed on your PC/PG.

Starting SIMATIC iMapThere are two ways to start SIMATIC iMap: Click on the Start / Programs /Component based Automation / SIMATIC iMap command or Click on the iMap iconon your desktop. Result: The SIMATIC iMap user interface opens

Figure 4-1 SIMATIC iMap user interface

Working with SIMATIC iMap


Getting Started with SIMATIC iMapIf this is the first time you have worked with SIMATIC iMap, we recommend that youwork through the introduction to learn, with reference to a step-by-step practicalexample, exactly what you need to do to create an application.

To do this, select the ? menu.> Getting Started.

4.2 Help Functions in SIMATIC iMap

Online HelpSIMATIC iMap's built-in help system provides targeted information for the points in theprogram at which you need help. You can thus quickly and efficiently access theinformation you need. The ways in which you can obtain help for each procedure aredescribed below.

Via the "?" menu• Help: Displays information on the selected object or the active dialog box or

window.

• Help Topics: Opens the "Component based Automation" online help system. Youcan then use the Content, Index, Find and Favorites tabs to navigate within theonline help.

• Getting Started: Describes the first steps that you have to carry out to create aworking application.

• About: Opens an information box listing the most important properties of theinstalled software version.

In dialog boxesIn all dialog boxes containing a "Help" button, you can click on this button to obtain adescription of the dialog box.

In messagesIn all message boxes containing a "Help" button, you can click on this button to obtaina detailed description of the message.



Via the F1 function keyUse the F1 function key to move directly from your current working context to the pointin the online help that describes this aspect. For example, if there is a dialog box onscreen, pressing F1 will call up a description of this dialog.

In the status barThe status bar contains a brief help text that describes the selected menu command.

Via the Tooltip textIf you move the cursor slowly over a button in the toolbar, a brief description appearsfor a short time.

SIMATIC iMap DocumentationThe complete SIMATIC iMap documentation is available in the form of a pdf file forreference and printing purposes. Use the Start > Programs > Component basedAutomation > SIMATIC iMap – Manual or > SIMATIC iMap – Getting Startedcommand to open the document.

4.3 Operating Philosophy

4.3.1 Objects and Object Hierarchy

Easy to operateSIMATIC iMap's graphical user interface is designed to be as straightforward andintuitive to use as possible. It therefore contains objects with which you are familiarfrom your usual working environment:

• Charts

• Functions

• Devices

Object-Oriented OperationObjects are represented by icons in the SIMATIC iMap user interface. The objects areopened for editing by selecting the relevant icon. In most cases, when you work withSIMATIC iMap you will use the normal Windows conventions.



Object HierarchyProjects may be given a hierarchical structure in SIMATIC iMap. By default, the projectwindow contains two tabs called "Plant tree" and "Network tree". The technologicalfunctions are listed under "Plant tree" and the devices under "Network tree" whenPROFInet components are inserted into the project.

New charts, which may contain further charts or objects, may be inserted into theproject window under "Plant tree" . Example:

Figure 4-2 Project window, example of an object hierarchy

PROFIBUS masters with the associated PROFIBUS slaves may be shownhierarchically under "Network tree".

Object propertiesObjects have properties, e.g. addresses and connectors. Once you have selected anobject, you can then open a dialog box using the Properties context menu, forexample, in order to make certain object-specific settings.

Actions on objectsYou can carry out certain actions on each object, such as Copy, Cut, Paste, etc. Whenyou select an object, the actions that you can carry out on that object are displayed inthe context menu.



4.3.2 Working with Objects

Basic actionsCertain basic actions on objects are shared by all objects. These fundamentalsequences of actions are summarized below. In the following chapters of this manual,we have assumed that you already know how to use them when we describe individualprocedures. If you attempt to carry out an illegal action, you will be stopped and thecursor which will change into a Stop sign.

The usual sequence of actions for handling objects is as follows:

• Create the object

• Select the object

• Carry out actions on the object, e.g. copy, paste, interconnect.

Creating ObjectsWith SIMATIC iMap you can create new libraries, projects and charts. The actualPROFInet components are created using the STEP 7 AddOn.

Use the following menu commands to create objects:

• Library > New

• Project > New

• Insert > New Chart

Creating an Object HierarchyThe project forms an object hierarchy. The "Plant tree" and " Network tree" views areautomatically created in the project window. When a chart is opened, objects alreadycontained in that chart appear in the project window.

You can then structure the project further by inserting more charts into a project oreven into another chart. You can also insert new charts into the project window andplant view.

At the bottom of the object hierarchy are the technological functions and devices.These are automatically created when the PROFInet components are inserted into aproject.



Opening ObjectsIn SIMATIC iMap you can open libraries, projects and charts. These objects areopened using the following menu commands:

• Library > Open

• Project > Open

• Edit > Open Selected Chart or by double clicking on the chart.

Once you have opened an object, you can then create or modify its content. Youcannot, however, open projects that are currently in use.

Setting object propertiesObject properties are the data of an object that define its behaviour. Select theProperties context menu to open a dialog box in which you can read or set theproperties of the selected object.

NoteIf you change the settings of objects, e.g. interconnections, offline in SIMATICiMap, they do not take immediate effect on the plant. The changes are notactivated until you download the data to the target system.

Cutting, Pasting and CopyingMost objects can be cut, pasted and copied as is usual under Windows. The relevantmenu commands are located in the Edit menu and in the context menus that youactivate by right clicking.

You can also copy objects by dragging and dropping. If you attempt to drop the objectat a destination that is not permitted, the cursor changes into a Stop sign.

NoteNew PROFInet components are inserted into the project from a library.

PROFInet components that have already been inserted may be copied or insertedin the network or plant view, or may be taken from the project window to thenetwork or plant view using Drag&Drop.



Selecting Objects - Multiple SelectionSeveral objects may be selected at the same time in the network and plant views(multiple selection . To do this, hold down the left mouse button and catch the objectsusing the lasso.

With multiple selection, only objects of the same type may be selected, e.g. onlytechnological functions and charts or only connectors may be selected in the plantview. Objects are selected in the following order: If the lasso contains completetechnological functions and charts, these objects are selected together with theassociated complete interconnections. If they are not complete, any completeconnectors that they contain are selected. If there are no connectors, then anyinterconnections that they contain are selected.

TipHold down the SHIFT or CTRL key at the same time to select multiple objects.

Copying subordinate charts

When you copy a subordinate chart, the entire hierarchy beneath that object is copiedas well. This means that, once a subsystem has been developed, it can then be reusedin many other systems.

NotePlease note that, in this case, PROFInet components without technologicalfunctions such as the IE/PB Link are not copied as well. To copy a PROFIBUSmaster together with its PROFIBUS slaves, we recommend that you make amultiple selection in the network view.

Renaming ObjectsSIMATIC iMap allows you to change the names of technological functions, devices andcharts. The names of PROFInet components in the libraries cannot be changed,however.

Technological functions and devices are given the name of the PROFInet componentby default. If the same PROFInet component is used several times, then the name willbe supplemented with a consecutive number, regardless of the hierarchical level inwhich the component is located, e.g. Machining_1.

A newly inserted chart is called "New Chart" by default. A second chart will be called"New Chart_1", etc.

Highlight the object you wish to rename and then select Edit > Properties.... Changethe name in the dialog. When you close the Properties dialog, the object is renamedand appears with the new name.



Moving ObjectsIn SIMATIC iMap you can move the following objects using Drag&Drop:

• PROFInet components from one library to another.

• Devices in the network view from one PROFIBUS network to another.

• Technological functions in the plant view.

• Charts within the project window.

NotePROFIBUS devices cannot be moved in the network view.

Deleting ObjectsYou can delete both folders and objects . When you delete a chart, you also delete allthe objects contained in that chart.

The deletion operation cannot be reversed. If you are not sure whether you really nolonger need an object, we recommend that you archive the entire project first.

The project window and the network and plant views in SIMATIC iMap are differentrepresentations of the same project. If an object is removed from one of the windows, itautomatically disappears from the other windows.

CautionA PROFInet component should not be deleted from the library if it occurs in aproject. If you do delete it, you will be unable to regenerate the project.

CautionWhen you delete an object, you also delete the corresponding interconnectionswith a technological function! It may therefore be necessary to reconnect the inputsand outputs to other technological functions.



Searching for objectsYou can search for objects in the following ways:

• If you highlight a PROFInet component in a library, you can select Find Instancesfrom the context menu to search for all instances (all devices and technologicalfunctions of this PROFInet component inserted into the project).

• You can use the Edit > Find... menu command to find all instances whose namescontain a certain character string.

The devices and functions thus found are listed in the information window. Double-clickon an entry in the information window to select and display the corresponding object inthe plant view or network view.

Selecting associated objectsWhen you select an object, you can use the Edit > Select in all Windows menucommand to select all the associated objects in the other windows as well.

Example: If you call the Edit > Select in all Windows menu command for atechnological function in the plant view, the following objects are selected:

• in the library: the PROFInet component whose instance contains the selectedfunction,

• in the plant tree in the project window: the same technological function and

• in the network view and in the network tree in the project window: the associateddevice.



4.4 Windows and Views

4.4.1 SIMATIC iMap User Interface

Structure of the user interfaceThe SIMATIC iMap user interface consists of various windows that may be opened andclosed as required by clicking the icons.

Figure 4-3 SIMATIC iMap User Interface



Table 4-1 Key

No. Window Icon

1 Project Window

2 Diagnostic Window

3 Information window

4 Library Window

5 Preview window (can only be opened together with the librarywindow)

6 Plant view or network view (always open)

Working with SIMATIC iMapDepending on which window is active, various actions can be carried out. Featuresused in Windows applications are available here:

• Menu commands (menu bar, context menus or icons in the toolbar),

• Drag&Drop,

• Double-clicking on a selected object,

• Keyboard input.

Call up helpTo call up help about a window in the user interface, click in the window and pressfunction key F1.



4.4.2 Plant View

DescriptionIn the plant view the inserted PROFInet components are visible as technologicalfunctions. The interconnections, i.e. the logical data connections between two or moretechnological functions, are represented by a line. These lines cannot be manipulated.Lines which cannot be displayed, for example, due to a lack of space are replaced by"continuation" connectors.

Figure 4-4 Plant View



ActionsYou can carry out the following actions in the plant view:

• Inserting PROFInet components from the libraries.

• Creating and deleting interconnections.

• Downloading interconnections and programs to the devices of the plant.

• Inserting new charts.

• Printing charts.

• Displaying and setting online values

• Comparing online and offline data

• Diagnosing technological functions and interconnections.

Reference to Further Windows and ViewsWhen a PROFInet component is inserted into the plant view, the technological functionis automatically displayed in the plant tree and the device is displayed in the networktree of the project window.

From a selected object in the plant view you can use the Go To context menu to jumpdirectly to the corresponding object in the project window or network view.



4.4.3 Network view

DescriptionIn the network view the inserted PROFInet components are displayed as objects withone or more network connectors. They are designated as "Devices" in the networkview. The devices have IP and/or PROFIBUS addresses.

The Ethernet is created as a green vertical line and the PROFIBUS network as a violethorizontal line when a PROFInet component of a PROFIBUS master with proxyfunctionality is inserted from a library. Possible insertion positions for PROFIBUSdevices are displayed as a green section on the PROFIBUS.

Figure 4-5 Network view



ActionsYou can carry out the following actions in the network view:

• Inserting PROFInet components from the libraries.

• Moving PROFIBUS devices

• Coupling unconnected PROFIBUS devices to a PROFIBUS network.

• Assigning addresses.

• Downloading programs and interconnections to all or the selected devices.

• Printing the network view.

• Monitoring and diagnosing devices online


Reference to Further Windows and ViewsWhen a PROFInet component is inserted into the network view, the technologicalfunction is automatically displayed in the plant tree and the device is displayed in thenetwork tree of the project window.

From a selected object in the network view you can use the Go To context menu tojump directly to the corresponding object in the project window or plant view.



Unconnected PROFIBUS DevicesUnconnected PROFIBUS devices are saved in the network view above a separatingline

• If no PROFInet component with PROFIBUS master functionality has been insertedyet or

• if the PROFIBUS master to which they were coupled was deleted from the projectwindow, network or plant view or

• if the "Couple PROFIBUS Devices Automatically" check box is unchecked on the"Network view" tab in the Settings dialog (Options > Settings menu command).

Unconnected PROFIBUS devices can be coupled to a PROFIBUS network usingDrag&Drop.

Figure 4-6 Network View, Unconnected PROFIBUS Devices



4.4.4 Project Window

DescriptionThe objects in the project are represented hierarchically in the project window. Theproject view consists of two parts:

• Plant tree – corresponds to the plant view

• Network tree – corresponds to the network view

Figure 4-7 Project Window

The technological functions are displayed in the plant tree and the devices in thenetwork tree when PROFInet components are inserted into the project. Subordinatecharts are also shown hierarchically in the plant tree. PROFInet components which donot contain a technological function, for example the IE/PB link, are only displayed inthe network tree.

The plant tree contains the name of the function, while the network tree contains thename of the device, e.g. BM 147.

Changing the project viewThe View > Project view >... menu command is used to:

• display additional information about the objects and

• show/hide hierarchical levels.

ActionsYou can carry out the following actions in the project view:



• Navigating between different charts.

• Downloading interconnections and programs to the devices of the plant.

• Looking up properties

• Creating and opening subordinate charts in the plant tree (chart-in-chart).


Reference to Further Windows and ViewsWhen a PROFInet component is inserted into the plant view, the technological functionis automatically displayed in the plant tree and the device is displayed in the networktree in the project window.

An object is displayed and selected in the plant or in the network view by double-clicking on the corresponding object in the project window.

4.4.5 Library Window

DescriptionSeveral libraries can be opened concurrently in the library window. Libraries are usedto manage and structure PROFInet components.

The PROFInet components in a library can be displayed via the View context menuwith large or small icons, as a list with or without details.

Figure 4-8 Library Window



ActionsYou can carry out the following actions in the library window:

• Creating, opening and closing libraries.

• Importing PROFInet components from the file system into a library.

• Inserting PROFInet components from a library into the plant or network view.

• Cutting or copying PROFInet components and pasting them into other libraries.

• Displaying properties of a PROFInet component.

• Searching for instances of a PROFInet component in the project.

NoteLibraries are stored as folders in the file system, where they can be moved, copied,inserted or deleted. Libraries which are deleted in Explorer can no longer beopened via SIMATIC iMap.

Reference to Further WindowsIf a PROFInet component is selected in the library window, information on thiscomponent is displayed on three tabs in the preview window.

Figure 4-9 Library and Preview Window



4.4.6 Preview Window

DescriptionThe preview window displays information on the PROFInet component selected in alibrary on three tabs.

The library window must be open in order to open the preview window.

Info TabThis tab displays information on the PROFInet component selected in a library.

Click on the "Documentation" link to open the documentation for the PROFInetcomponent. The link is only displayed if there is a documentation link in thecomponent.

Figure 4-10 Preview Window, Info Tab



Function TabThis tab displays the technological function of the PROFInet component selected in alibrary.

Figure 4-11 Preview Window, Function Tab



Device TabThis tab displays the device for the PROFInet component selected in a library.

Figure 4-12 Preview Window, Device Tab

ActionsYou can carry out the following actions in the preview window:

• On the Info tab: Open the documentation stored for a PROFInet component (ifavailable).

• On the Function tab: Display a technological function.

• On the Device tab: Display a device.

Reference to Further Windows and ViewsThe preview window can only be opened if the library window is open. The previewwindow is closed when the library window is closed.



4.4.7 Diagnostic Window

DescriptionDiagnostic information about process variables and faults in the technological functionsand devices are displayed on three tabs in the diagnostic window. The three tabs in thediagnostic window are:

• Functions

• Device

• Variable table - described in a separate section

Functions TabOnline > Monitor is used to activate diagnosis of the technological functions. All themalfunctions are displayed in the left-hand window. Information on the currentlyselected object is displayed in the right-hand window.

Figure 4-13 Diagnostic Window, Functions Tab



Devices TabOnline > Monitor is used to activate diagnosis of the devices. Information on all thefaulty devices is displayed in the left-hand window. Information on the currentlyselected object is displayed in the right-hand window. Troubleshooting information canbe obtained by clicking on the "Help" button.

Figure 4-14 Diagnostic Window, Devices Tab

ActionsYou can carry out the following actions in the diagnostic window:

• Searching for and analyzing errors

• Reading troubleshooting information, e.g. that a download is required.

• Monitoring and controlling process variables of selected connectors

Reference to Further Windows and ViewsA fault that appears in the diagnostic window is identified by a symbol on the affecteddevice in the network view and on the technological function in the plant view.

Double- click on a faulty function in the diagnostic window to display the affectedtechnological function in the plant view.

Double-click on a faulty device in the diagnostic window to display the affected devicein the network view.



Example of a Fault at a Device

Figure 4-15 Diagnostic Window: Example of a Fault at a Device



4.4.8 Diagnostic window, "Variable table" tab

DescriptionIn SIMATIC iMap, the variable table is used for online monitoring and control ofvariables during the plant testing and commissioning phases. It has its own onlinemode that can be switched on and off independently of the online monitoring in theplant and network views.

The variable table contains the data for the connectors of the SIMATIC iMap project tobe monitored. You can enter the connectors directly or simply drag them from the plantview and drop them into the variable table.

You can show / hide individual columns of the variable table using the View > Variabletable >... menu command or with the Columns >... context menu.

The following diagram shows a variable table in the online view.

Figure 4-16 Diagnostic window, "Variable table" tab



Actions• Adding, copying, deleting and sorting entries

• Changing the display format

• Showing / hiding columns

• Monitoring selected or all variables online

• Editing control values and transferring them to the devices of the plant for testingpurposes.

• Importing and exporting data

Reference to Further WindowsUse the Go To > Function connector context menu command to select theassociated connector in the plant view.

4.4.9 Information window

DescriptionThe information window displays information about recent actions in SIMATIC iMap. Itis opened automatically when new information about an action is available, e.g. errorswhile generating (see diagram below).

Figure 4-17 Information window

ActionsThe following messages are automatically displayed in the information window:

• Execution status and progress, e.g. during generation, downloading or onlinemonitoring

• Errors while executing commands



• Results of certain commands, e.g. online-offline comparison of programs andinterconnections, or searching for objects.

The "Reference object" column lists the names of the devices or functions to which themessages relate.

NoteThe old contents of the information window are not automatically deleted whennew messages are displayed.

You can edit the content of the information window as follows:

• Use the Edit > Information Window > Copy All menu command to copy allmessages in text format to the clipboard so that they can be further processed bypasting them into a text editor, for example.

• Use the menu command Edit > Information Window > Delete All to delete allmessages.

Reference to Further WindowsDouble-click on a reference object to select the associated object in the correspondingview - technological functions in the plant view and devices in the network view.



4.5 Setting Up and Calling Tools

You can set up SIMATIC iMap so that you can call up any software tool using a menucommand in order to further process data from the current project, for example.

Setting up toolsThe procedure for setting up a new tool is as follows:

1. Select the Options > Settings menu command and click on the "Tools" tab.

2. Click on the "New Entry" button.

3. In the "Name" box, enter the name under which you wish to call the program inSIMATIC iMap.

4. In the "Command" box, enter the path of the program, or click on the "Browse"button to select the program from the file system. The following may be selected:

– the actual program (e.g. winword.exe) or

– a file (e.g. <document>.doc) that is opened with this program.

5. Click on "OK" or "Accept" to confirm your input.

Result: the program is added to the list of tools that you can call directly fromSIMATIC iMap.

Figure 4-18 Setting up a tool



NoteYou can use the buttons in the Settings dialog to move or delete entries in the listof tools.

Calling toolsYou can only call tools that are included under "Tools" in the settings.

To start a tool, select the Options > Tools > ... menu command.

Result: The called program is started.


Configuring Plants 55.1 Main procedure

RequirementsThe following requirements must be fulfilled before you can configure a plant usingSIMATIC iMap:

• SIMATIC iMap must be installed on your PC/PG.

• The device-specific configuration and programming tool, e.g. STEP 7, is installedon your PC/programming device (optional). Depending on the type of device, thissoftware is needed in order to carry out certain actions, e.g. generating ordownloading.

• The necessary PROFInet components must have been created.

Main procedure1. Start SIMATIC iMap

2. The options are as follows, regardless of whether the PROFInet components havealready been imported into a target library:

– Open the library with the PROFInet components or

– Open a library or create a new library and import the PROFInet components.

3. Insert PROFInet components into the SIMATIC iMap project.

4. Couple devices in the network view.

5. Assign IP and/or PROFIBUS addresses to the devices.

6. Interconnect technological functions in the plant view.

7. Generate the SIMATIC iMap project and download it to the devices of the plant.

Configuring Plants


5.2 Working with Projects

5.2.1 Creating a New Project

Creating a New Project

A new SIMATIC iMap project is always opened when you open SIMATIC iMap. Youcan edit and save this project or open an existing project for editing.

ProcedureYou can create a new SIMATIC iMap project in the following ways:

• Restart SIMATIC iMap or

• Select the Project > New menu command.

A new SIMATIC iMap project opens in both cases.

NoteIn SIMATIC iMap, you can only edit one project at a time. If you wish to editseveral projects at the same time, then you must start several instances ofSIMATIC iMap.

5.2.2 Opening and Closing Projects

RequirementA new, empty SIMATIC iMap project is always opened when you open SIMATIC iMap.You can open a different project at any time, provided that this project was saved inSIMATIC iMap.

You can only have one project open at a time in SIMATIC iMap. When you open a newproject, the current project is closed and you are prompted to save any changes youhave made.

Configuring Plants


NoteA SIMATIC iMap project cannot be open in two SIMATIC iMap applications at thesame time.

Opening a projectTo open a project in SIMATIC iMap:

1. Select the Project > Open... menu command.

A dialog box for browsing the file system for existing projects opens. Search for aproject file with the file extension .cbp.

2. Select the project folder from the "Search in" box. The box below contains onlydirectories and files of the desired file type (SIMATIC iMap project).

3. Select the file name with the file extension .cbp.

The file name is displayed in the "File name" box.

4. If the selected project is password-protected, enter your password in the"Password" box.

5. Click on the "Open" button.

Result: the project is opened in SIMATIC iMap.

Tip: The "File name" drop-down list contains the most recently opened SIMATIC iMapprojects.

Configuring Plants


Closing a projectTo close a project in SIMATIC iMap, you can either:

• Exit SIMATIC iMap,

• Create a new project or

• Open another project.

Each of these options closes the current project. If you have made any changes to thecurrent project, you are prompted to save these changes. A dialog box with thefollowing selection options opens:

• "Yes" to save the changes to the current project before closing

• "No" to close the current project without saving

• "Cancel" to cancel the operation and return to the current project.

5.2.3 Saving and Archiving Projects

Storing a SIMATIC iMap projectA SIMATIC iMap project is created in the form of a directory tree, and can be stored asan archive file.

If you save it, all the files belonging to the SIMATIC iMap project are stored in aseparate folder. You are prompted to enter the path when you save the project for thefirst time. You can enter any project folder name, and the folder is automatically giventhe extension .cbp. The project file is saved together with other project data in a folderof the same name.

If you archive it, all the project data is stored in an archive file. You can enter any filename, and the archive file is automatically given the extension .arp.

NoteUse the Options > Settings menu command to specify a storage location on the"Directories" tab that will be offered by default when you open, save or archiveprojects.

Password ProtectionIn SIMATIC iMap, you can enter a password to protect your project againstunauthorized access. This password is defined in the project properties and must beentered whenever you open the project. The project cannot be opened without thepassword.

When you archive a project, it retains its password protection.

Configuring Plants


Saving a ProjectYou can save a SIMATIC iMap project in the following ways:

• Select the Project > Save menu command to save the current project under thesame name. The old project is overwritten.

• Select the Project > Save As... menu command to save the current project under adifferent name. The old project remains unchanged. You can enter any path andname for the new project.

If you save a project with a new name, it retains its password protection.

Archiving a Project

NoteYou can only archive a SIMATIC iMap project if it is closed. To archive the currentproject, you must first close it by creating a new project or opening another project.

To archive a project, proceed as follows:

1. Make sure that the project to be archived is closed and that no other programs areaccessing the project folder.

2. Select the Project > Archive... menu command.

A dialog box for browsing the file system for existing projects opens. Search for aproject file with the file extension .cbp.

3. Select the project folder from the "Search in" box. The box below contains onlydirectories and files of the desired file type (SIMATIC iMap project).

4. Select the file name with the file extension .cbp.



A dialog box for selecting the storage location opens.

6. In the Archive iMap project library as... dialog box, select the folder in which thearchive file is to be stored.

7. Accept the name suggested in the "File name“ box or enter the name of the archivefile and click on "Save“.

Result: The archive file is created and the result is signalled to you.

Configuring Plants


Retrieving a Project

NoteYou can only retrieve projects that were archived using SIMATIC iMap.

The procedure for retrieving a project is as follows:

1. Select the Project > Retrieve... menu command.

A dialog box for browsing the file system for existing archive files opens.

2. Select an archive file (.ARP file). There are two options:

– You can enter the required archive file in the "Search in" box or

– You can select one of the recently archived projects from the "File name" drop-down list.


A dialog box for selecting the target folder opens.

4. Select the folder to which you wish to save the retrieved project and click on "OK".

Result: The project folder is created in the specified target folder, and the result issignalled to you.

NoteWhen you archive a project, it retains its password protection.

Configuring Plants


5.2.4 Generating a Project

Generating SIMATIC iMap projectsYou must generate a project before you can download data from that project to thedevices of the plant. When you generate the project in SIMATIC iMap, the currentproject data for all PROFInet components contained in the SIMATIC iMap project isprepared for specific devices, so that it can be downloaded to those devices in theplant.

The Shadow ProjectWhen the project is generated, the data for the PROFInet components is generallyprepared in a shadow project for the specific device. The shadow project has a device-specific structure formed from the component projects of the PROFInet componentsfrom the library or libraries.

The shadow project is created when the SIMATIC iMap project is generated for the firsttime. All changes to PROFInet components in the SIMATIC iMap project, e.g. IPaddresses or PROFIBUS addresses, are transferred to the STEP shadow projectwhenever the SIMATIC iMap project is regenerated.

NoteThe shadow project is not updated when the project is saved using the Shadowproject > Save menu command.

WarningThe shadow project must not be modified directly using the device-specificconfiguration and programming tool (e.g. STEP 7).Changes to the shadow project may lead to inconsistencies in the SIMATIC iMapproject, preventing any further downloads.

Possible remedies

• Regenerate the SIMATIC iMap project or

• Recreate the PROFInet components with the changes and insert them into theSIMATIC iMap project once more.

Configuring Plants


Which actions are transferred when the project is generated?The following actions in SIMATIC iMap are transferred when the project is generated:

• Cutting, copying or deleting devices or technological functions and theirinterconnections

• Replacing instances

• Inserting new instances of PROFInet components into the project

• Changing the properties of instances, e.g. names or addresses

• Changes to the networking of the devices, e.g. connecting and disconnectingPROFIBUS devices

NoteIf you have made any of the above changes to the project, they cannot bedownloaded to the devices of the plant until the project has been generated.The generation status determines whether the project needs to be generated. Thegeneration status of an instance of a PROFInet component is displayed in theProperties dialog box for the technological function and the associated device. Thegeneration status "Created" means that downloading to the devices of the plant ispossible.

Which actions are not transferred when the project is generated?Changes to the device-specific data of the shadow project that are made using one ofthe Edit > Special... menu commands are ignored during generation. These changesmust be downloaded to the devices in the plant using the device-specific configurationand programming tool.

RequirementsCheck the following points before you generate a project:

• The device-specific configuration and programming tool(s), e.g. STEP 7, and thecorresponding link(s) in SIMATIC iMap, e.g. STEP 7 Add-on, must be installed onthe computer.

• The library or libraries in which the PROFInet components for the project arelocated must be open since the open libraries are searched for necessaryPROFInet components.

NoteWhen you generate the project, the identification (class ID) and the versionnumber of each instance are compared with those of the correspondingPROFInet component in the library. The corresponding instance cannot begenerated successfully unless they are totally identical.

Configuring Plants


Generate changes to the projectCall the Project > Generate > Changes Only menu command to generate just thechanges to the project. The generation progress messages and any error messagesare displayed in the information window.

When this menu command is run for the first time, the shadow project is created fromthe component projects in the library(ies) - just as with the Project > Generate > Allmenu command. Whenever this menu command is called again, the shadow project isupdated with any changes you have made.

If generation is successful, all the components of the project are given the generationstatus "Created". This status can be viewed in the component properties. The programcan then be downloaded.

Regenerating a ProjectIf the SIMATIC iMap project cannot be generated because the shadow project containsincorrect or inconsistent data, for example, then the shadow project must be recreated.The shadow project is recreated from the component projects for the PROFInetcomponents from the library(ies) when it is regenerated..

Select the Project > Generate > All menu command. If the project has already beengenerated, a message appears to indicate the effect that the command has had. Clickon "Yes" to acknowledge this message and start regeneration.

The generation progress messages and any error messages are displayed in theinformation window.

Result: The shadow project is created once more from the component projects for thePROFInet components from the library. The regenerated shadow project does notcontain any changes you have made using the device-specific configuration andprogramming tool. A copy is made of the old shadow project. You can use this to copyany changes in the new shadow project.

NoteOnly 3 backup copies of the shadow project are kept in the project directory.

If there are already 3 backup copies, then the oldest is deleted during generation.

Cancelling GenerationGeneration can take a long time for large projects, You can cancel and subsequentlyresume the generation of changes at any time by clicking on the "Cancel" button in themessage box. Any data you have already generated is retained when you cancel.

If you then call the Project > Generate > Changes Only menu command again, onlythe new, modified and still ungenerated parts of the project are generated.

Configuring Plants


5.2.5 Documenting and Printing a Project

Content of the project documentationYou can create documentation for a SIMATIC iMap project containing the followinginformation:

• General project data, such as name, path and creation date

• All the technological functions and subordinate charts of the plant chart and theirinterconnections

• All PROFInet and PROFIBUS devices of the network chart

• The PROFInet components used as library elements and their instances (devicesand functions) in the project

• Optional – descriptions of the interconnectable and non-interconnectableconnectors of the component interfaces.

• Optional – graphical representations of all charts (network chart, plant chart andsubordinate charts, if applicable)

Creating the Project DocumentationProceed as follows:

1. Select the Project > Document... menu command.

2. In the "Create Project Documentation" dialog box activate the options for theinformation to be transferred to the documentation.

3. If necessary, click on the "Change" button and change the path under which theproject documentation is stored.

4. Click on the "OK" button.

Result: The current version of the project is documented. The project documentation isstored as an HTML file together with the associated graphics files (icons, etc.) in thefolder.

NoteThe project documentation is recreated whenever you call the Project >Document... menu command.

You can display stored project documentation versions by opening the HTML filedirectly in an HTML browser.

Configuring Plants


Page SetupSelect the Project > Page Setup menu command to make the following settings forprinting the current window:

• Paper size and source

• Paper orientation (portrait or landscape)

• Width of the page margins

Header and footer settingsYou can set up the header and footer as follows in order to print the plant or networkview:

1. Select the Project > Headers and Footers menu command.

A dialog box for setting the header and footer opens.

2. Enter the content of your header and footer. You can edit the "Left", "Centre" and"Right" boxes. The field buttons can be used to automatically insert field functions,such the project name or page.

3. You can specify the font and point size.

4. You can specify the type of separating lines to be inserted between adjacent pagesand for the lines in the header and footer.

5. Click on "OK" to confirm your settings.

Printing the project• Select the Project > Print > Active Window menu command to print either the

plant view or the network view for the current project, regardless of which window iscurrently open.

• Select the Project > Print > All Charts menu command to print all the charts in theproject, i.e. the network view and the plant view, including all subordinate charts.

Large projects are printed on several pages.

Configuring Plants


5.3 Working with Libraries

5.3.1 Creating a New Library

Storage of SIMATIC iMap LibrariesYou can open, create or close any number of libraries in the SIMATIC iMap librarywindow, regardless of which project you are currently editing.

In SIMATIC iMap, new libraries are created as folders. When you create a new library,a library file with the extension .CBL is generated. You can specify any name. The fileis stored in a folder of the same name. You can use any path.

You can also archive an existing library. In this case, the entire content of the library isstored in an archive file with the extension .ARL. You can enter any path and name forthe archive file.

Creating a new libraryTo create a new library in SIMATIC iMap:

1. Select the Library > New... menu command.

A dialog box for browsing the file system opens.

2. In the "Search in" box, select the folder in which you wish to create the library.

3. Enter the name of the library in the "File name" box. The extension CBL is assignedautomatically to the name.

4. Click on the "Save" button.

Result: The library is created and opened.

Configuring Plants


5.3.2 Opening and Closing Libraries

RequirementThe library must have been created in SIMATIC iMap.

Opening a LibraryTo open an existing library in SIMATIC iMap:

1. Select the Library > Open... menu command.A dialog box for browsing the file system for existing libraries opens.

2. Select the library folder from the "Search in" box. The box below contains onlydirectories and files of the desired file type (SIMATIC iMap library).

3. Select the file name with the file extension .cbl.



Result: The library is opened in the SIMATIC iMap library window.

Tip: The "File name" drop-down list contains the most recently opened SIMATIC iMaplibraries.

Closing a LibraryTo close a library in SIMATIC iMap:

1. Click on the library that you wish to close.

2. You can then either:

– Click on the cross (X) in the top right-hand corner of the library or

– Select the Library > Close menu command or

– Select the Close library command from the context menu.

Configuring Plants


5.3.3 Importing PROFInet Components

PROFInet Components in LibrariesBefore you can insert a PROFInet component into a SIMATIC iMap project, it must firstbe located in a library. You can then insert instances of the PROFInet component intothe project.

When you create a PROFInet component, you can define whether it should be storedin the file system or imported into an existing library. Once a PROFInet component hasbeen created in the file system, it can then be imported into a library in SIMATIC iMap.

Unique identification of PROFInet componentsPROFInet components are uniquely identified by the identification (class ID) and theversion number. Both the identification (class ID) and the version number are displayedin the "Properties" dialog box for the PROFInet component.

RequirementThe PROFInet component must have been created using the vendor-specificconfiguration and programming tool, e.g. STEP 7.

NotePROFInet components cannot be overwritten when they are imported into a library.If the library already contains a PROFInet component with the same versionnumber and identification (class ID), then the selected component is not imported.

Importing PROFInet Components into a LibraryProceed as follows:

1. Click on the library into which you wish to import the PROFInet component.

2. Select the Edit > Import PROFInet component menu command.

A dialog box for browsing the file system for existing PROFInet components opens,and the system searches for the associated .XML files.

3. Select an XML file.

Tip: A list containing the recently opened XML files is displayed if you click on thedown arrow in the "File name" box.

4. Click on "Open" to import the selected PROFInet component.

Result: The selected PROFInet component is imported and the component's iconappears in the library.

Configuring Plants


5.3.4 Administering Libraries

Editing PROFInet Components in the LibraryYou can edit PROFInet components contained in one or more libraries in the followingways:

• Move from one library to another

• Cut

• Copy

• Paste cut or copied PROFInet components

Move a PROFInet componentYou can move a PROFInet component from one library to another:

• Using Drag&Drop

• By cutting and pasting

Deleting a PROFInet ComponentYou can delete a PROFInet component from a library:

• Using the "Delete" key

• Using the Edit > Delete menu command.

CautionThe PROFInet components used must be present in the library in order togenerate a project. Before you delete a PROFInet component from a library, makesure that it is no longer used in your projects.

Copying, Cutting and Pasting PROFInet ComponentsYou can use the following menu commands:

• Edit > Copy - Copies the selected PROFInet components to the clipboard.

• Edit > Cut - Cuts the selected PROFInet component and places it on the clipboard.

• Edit > Paste - Inserts the clipboard contents.

The commands are also available in the context menu, depending on which window isactive.

Configuring Plants


5.3.5 Archiving and Retrieving Libraries

Storage of SIMATIC iMap LibrariesA SIMATIC iMap library is created in the form of a directory tree, and can be stored asan archive file. When you archive a library, all the data for the PROFInet componentscontained in that library is stored in an archive file. You can enter any file name, andthe file is automatically given the extension .ARL.

NoteUse the Options > Settings menu command to specify a storage location on the"Directories" tab that will be offered by default when you create, open or archivelibraries.

Archiving a Library

NoteYou can only archive a SIMATIC iMap library if it is closed. To archive the currentlibrary, you must close it first.

To archive a library, proceed as follows:

1. Make sure that the library to be archived is closed and that no other programs areaccessing the library folder.

2. Select the Library > Archive... menu command.

A dialog box for browsing the file system for existing libraries opens. Search for aproject file with the file extension .cbl.

3. Select the library folder from the "Search in" box. The box below contains onlydirectories and files of the desired file type (SIMATIC iMap library).

4. Select the file name with the file extension .cbl.



A dialog box for selecting the storage location opens.

6. In the "Archive iMap library as..." dialog box, select the folder in which the archivefile is to be stored.

7. Accept the name suggested in the "File name“ box or enter the name of the archivefile and click on "Save“.

Result: The archive file is created and the result is signalled to you.

Configuring Plants


HintAlways include the library archive containing the PROFInet components used whenyou create an archive file for a SIMATIC iMap project. You will need these librarieswhen you generate the project.

Retrieve Library

NoteYou can only retrieve libraries that were archived using SIMATIC iMap.

To retrieve a library, proceed as follows:

1. Select the Library > Retrieve... menu command.

A dialog box for browsing the file system for existing archive files opens.

2. Select an archive (.ARL file). There are two options:

– You can enter the required archive file in the "Search in" box or

– You can select a file from the list of recently archived libraries from the "Filename" box. (A list containing the recently opened libraries is displayed if youclick on the down arrow in the "File name" box).

3. Click on "Open" to select the archive file.

A dialog box for selecting the target folder opens.

4. Select the folder to which you wish to save the retrieved library and click on "OK".

Result: The library folder is created in the specified target folder, and the result issignalled to you.

Configuring Plants


5.4 Inserting PROFInet Components into a SIMATIC iMap Project

Inserting into the SIMATIC iMap ProjectPROFInet components are inserted from a library into your SIMATIC iMap project. Youcan insert a PROFInet component:

• into the plant view window or

• into the network view window or

• into the project window.

In all cases, both parts of the PROFInet component - the technological function and theassociated device - are inserted. PROFInet components with no technological functioncan also be inserted into every window, although they cannot be viewed in thosewindows.

Instances of a PROFInet componentAn instance of the PROFInet component, i.e. one use of this type of component, iscreated in the project by inserting a PROFInet component from a library to theSIMATIC iMap project. Any number of instances of a PROFInet component may beinserted into a project. Additional properties are assigned to each instance, such asname and address. The association between all instances and the original PROFInetcomponent is defined by the identical class ID and version number.

RequirementThe PROFInet components that you want to insert into your project must be containedin a library in SIMATIC iMap.

Inserting PROFInet ComponentsProceed as follows:

1. Select the PROFInet component from the library.

2. Insert it into the window You have several options, e.g.:

– Drag-and-Drop

– Paste -> Component from Library menu command.

– Paste Into Project command (context menu)

Configuring Plants


Result: The technological function of the component - if it contains one - appearsin the plant view and in the plant tree in the project view. The associated deviceappears in the network view and in the network tree in the project view.

Figure 5-1 Inserting a PROFInet Component into a SIMATIC iMap Project

Configuring Plants


5.5 Interconnecting Technological Functions

Rules for Interconnection• An interconnection can only be set up between an output and an input. An output

can be interconnected with several inputs, but an input can only be interconnectedwith an output.

• The two connectors of an interconnection must be of the same data type, e.g. bothof type I2 or type R4.

RequirementThe technological functions to be interconnected must have been inserted into theproject.

InterconnectingProceed as follows:

1. Open the plant view and click on a connector. The connector changes color, andthe shape of the cursor also changes.

2. There are two options:

– Hold down the mouse button and drag to the second connector or

– Click on the second connector of the interconnection.

With this procedure, those connectors that are suitable for the data type of thetechnological functions are always highlighted in color.

The interconnection appears between the two connectors in the form of a line or aninterconnection endpoint.

Configuring Plants


Tip: Multiple interconnectionsUsed to connect several inputs to one output:

• Hold down the CTRL key and select the required inputs.

• Release the CTRL key and select the output to be interconnected.

Result: All the selected inputs are interconnected to this output.

InterconnectionsAn interconnection is represented by a line that connects the input of a technologicalfunction to the output of a second technological function.

When you delete a technological function, all the associated interconnections aredeleted.

When you move a technological function, the course of the associatedinterconnections is also changed.

If the full line of the interconnection cannot be calculated, e.g. due to lack of space,then only the two ends of the interconnection, known as continuation connectors aredisplaced.

The color of the line changes when you select an interconnection. You can delete aselected interconnection or look up and modify its properties.

Configuring Plants


Displaying the Interconnection LinesUse the View > Plant View > Display Interconnection Lines menu command toshow or hide the interconnection lines.

You can switch off the interconnection lines temporarily by removing the tick from themenu command in order to work more efficiently in the plant view. In this case, only theend points of the interconnections are displayed in the form of continuation connectors.Interconnection endpoints with the same number represent an interconnection. In thisdisplay mode, you computer does not have to constantly recalculate the lines, whichallows you to move and interconnect technological functions faster.

Figure 5-2 Display Interconnection Lines

Configuring Plants


Figure 5-3 Displaying the interconnection endpoints

Tip: Recalculate Interconnection LinesUse the View > Plant View > Recalculate Interconnection Lines menu command orfunction key F5 to refresh the representation of the interconnection lines.

Configuring Plants


5.5.1 Interconnecting with Constant Values

Constant values at component inputsSome technological functions require a constant value to be applied at an input, inorder to test the function, for example. This value can be set using SIMATIC iMap.

RuleIn SIMATIC iMap, only inputs can be interconnected with constant values. This is notpossible with outputs.

NoteFor a connector of the type ARRAY, only one value may be entered for allelements of the array.

RequirementThe input to be interconnected must not already be interconnected. If this is the case,the existing interconnection must first be deleted.

Interconnecting with a Constant ValueProceed as follows:

1. Select the input so that the mouse pointer with the interconnection icon appears.

2. Select Interconnect Constants from the context menu.

3. Enter the desired value in the "Interconnect with constant value" dialog box andclick on the "OK" or "Accept" button.

The input is identified by a constant icon, and the value of the constant is displayed atthe input.

Configuring Plants


ExampleThe selected input is interconnected with the value 30.

Figure 5-4 Interconnecting with a constant value

Changing the Interconnected Constant ValueProceed as follows:

1. Select the constant icon for the input.

2. Open the interconnection properties.

3. Enter the required value in the Constant Value" box in the "Interconnection withConstant Value" dialog box.

4. Click on the "OK" or "Apply" button.

The changed value is displayed at the input.

Configuring Plants


Deleting an Interconnection with a Constant ValueProceed as follows:

1. Select the constant icon for the input.

2. Select the Delete Interconnection command from the context menu.

The constant icon disappears, and the input can be interconnected once more.

5.5.2 Moving Interconnections

DefinitionIn SIMATIC iMap, the end point of an interconnection can be moved onto a connectorof another technological function.

Rules for Moving InterconnectionsThe target connector to which the end point of an interconnection is to be moved mustfulfil a number of conditions. These conditions depend on the number of end points tobe moved.

• Some or all of the end points of the interconnections of a technological function canonly be moved onto connectors of the same type (input or output), same name andsame data type of another technological function.

• There are two ways to move the interconnection at an individual end point:

– at a connector of the same type (input or output) and same data type (in whichcase the I/O names do not have to be the same) or

– at a different technological function. In this case, the technological functionselected as the target must contain a connector of the same type (input oroutput), same name and same data type.

• If the end point is an input, it can only be moved to an unconnected input. Anoutput can be moved onto an already interconnected output.

• Interconnections cannot be moved across the boundaries of a chart; the source andtarget must be in the same chart.

• The configured substitute values of the interconnections are accepted.

• Interconnections with configured substitute values cannot be moved from aPROFInet device to a PROFIBUS device if the configured substitute values are notequal to the default values.

Configuring Plants


To move several interconnections:1. Select the connectors of a technological function from which the interconnections

are to be removed. Select the entire technological function if you wish to move allthe interconnections.

2. Select the Move Interconnections command from the context menu. Thetechnological functions to which the selected interconnections can be moved arehighlighted in color when the mouse pointer moves over them.

3. Click on the technological function to which the interconnections are to be moved.

4. You are prompted to confirm that you want to move the interconnections. Click on"Yes" to confirm.

Result: the interconnections are moved to suitable connectors in the newtechnological function.

If no suitable targets are found for interconnections, they are not moved and remain atthe original technological function.

To move an individual interconnection:1. Select the connector from which the interconnection is to be removed.

2. Select the Move Interconnections command from the context menu. The possibletarget connectors or technological functions to which the interconnection can bemoved are highlighted in color when the mouse pointer moves over them.

3. Click on the target connector to which the interconnection is to be moved.

Result: the end point of the interconnection is moved to the target connector.

5.6 Coupling Devices in the Network View

Arrangement of the devices in the network viewThe devices in the network view are always arranged according to the following rules:

• All PROFInet devices with Ethernet connectors are automatically connected to theEthernet bus.

• Drag PROFIBUS devices and drop them onto the PROFIBUS of the DP master toconnect.

Configuring Plants


Changing the NetworkingYou can make the following changes to the networking:

• Coupling a stand-alone PROFIBUS device to a DP master device

• Decoupling a PROFIBUS device from a DP master device

• Coupling a PROFIBUS device to another DP master device

• Moving the DP slaves on the PROFIBUS

All changes in the network view can be carried out using Drag-and-Drop.

NotePROFInet devices cannot be moved on the Ethernet.

"Couple PROFIBUS Devices Automatically" optionFor PROFIBUS devices (DP slaves), you can use the Options > Settings... menucommand to activate or deactivate the "Couple PROFIBUS Devices Automatically"option on the "General" tab:

• If "Couple PROFIBUS Devices Automatically" is activated, then newly insertedPROFIBUS devices (DP slaves) are automatically connected to the PROFIBUS ofthe most recently inserted PROFInet device of a DP master if they are notdeliberately positioned in the network view or network tree using drag-and-drop.

Figure 5-5 Coupled PROFIBUS devices

• If "Couple PROFIBUS Devices Automatically" is deactivated, newly insertedPROFIBUS devices (DP slaves) remain uncoupled unless they are deliberatelypositioned in the network view or network tree using drag-and-drop.

Configuring Plants


Figure 5-6 Uncoupled PROFIBUS devices

Configuring Plants


5.7 Looking Up And Modifying Properties

Properties - OverviewIn SIMATIC iMap you can view and, if necessary, modify the properties of the followingobjects:

• Project

• Instance

• Chart

• Interconnection

• Connector

• Library

• PROFInet component

A description of the properties can be found in the context-sensitive help for the"Properties" dialogs.

Displaying or Modifying PropertiesProceed as follows:

1. Open the desired window.

2. Select the object and then select one of the following menu commands:

– Edit > Properties from the menu bar or

– Properties from the context menu.

The "Properties" dialog box opens.

3. If necessary, modify the desired properties and click on "Accept" to confirm yourchanges.

4. Close the dialog box.

– Click on OK if you want your changes to take effect

– Click on "Cancel" if you want to cancel all your changes.

Configuring Plants


5.7.1 Addresses of PROFInet Devices

PROFInet devices may have the following addresses, depending on the bus portsused:

Bus connector Address

Ethernet IP addressPROFIBUS PROFIBUS address

Range of Values for IP AddressesThe IP address consists of 4 decimal numbers which are separated from each oneanother by a dot, e.g.141.80.0.16. The possible ranges are:

Class of the IP address Range of values

A 1.xxx.xxx.xxx - 126.xxx.xxx.xxxB 128.0.xxx.xxx - 191.255.xxx.xxxC 192.0.0.xxx - 223.255.255.xxx

Range of values for subnet masksThe subnet mask consists of 4 decimal numbers with values ranging from 0 to 255 andseparated from one another by a dot, e.g. 255.255.0.0

In binary format, the 4 decimal numbers of the subnet mask must contain a continuoussequence of 1s from the left and a continuous sequence of 0s from the right.

The "1" values determine the network number within the IP address. The "0" valuesrepresent the host address within the IP address.

ExampleValue Decimal Binary

Correct value 255.0.0.0 1111 1111. 0000 0000.0000 0000.0000 0000Correct value 255.255.128.0 1111 1111.1111 1111.1000 0000.0000 0000Correct value 255.254.0.0 1111 1111.1111 1110.0000 0000.0000.0000Incorrect value 255.0.1.0 1111 1111.0000 0000.0000 0001.0000 0000

Configuring Plants


Association between the IP address and subnet maskThe first decimal number (from the left) of the IP address determines the structure ofthe subnet mask with regard to the number of "1" values (binary) as follows:

Table 5-1 Connection between IP address and subnet mask

First decimal number ofthe IP address

Subnet mask

0 to 126 255.x.x.x128 to 191 255.255.x.x192 to 223 255.255.255.x

"x" stands for the host address

RouterYou will need a network transition (router) if you want the device to be able tocommunicate with other devices outside its own subnet. The structure of your plant willdetermine whether you use a network transition or not. The address is specified by thenetwork administrator or plant operator.

PROFIBUS addressThe PROFIBUS address is entered as a decimal number from 1 to 125. The currentrange of values depends on the module concerned.

Example of AddressesAddresses Example

IP address 141.30.20.5Subnet mask 255.255.128.0PROFIBUS address 25

Configuring Plants


5.7.2 Assigning Addresses

Addresses of PROFInet and PROFIBUS devicesIP and/or PROFIBUS addresses are assigned to devices via the "Properties" dialogs.IP addresses and subnet masks must be assigned in order to be able to establishonline connections with the devices of the plant.

NoteThe IP address and subnet mask that you assign to a PROFInet device inSIMATIC iMap must be the same as the IP address and subnet mask of the devicewithin the plant, otherwise the devices cannot be accessed online from SIMATICiMap.

If you use a network transition: The IP address of the device and the IP addressof the network transition must belong to the same subnet.

RequirementThe IP addresses and associated subnet masks have to be assigned to the devices ofthe plant using vendor-specific configuration tools. They are generally defined by thenetwork administrator.

Assigning AddressesProceed as follows:

1. Select the desired device from the network view or the associated function from theplant view.

2. Open the object properties

– using the Properties context menu or

– using the Edit > Properties menu command.

3. On the "Addresses" tab, enter the addresses required for the type of device:

– IP address and subnet mask:Enter the IP address and subnet mask that were assigned to the device usingthe device-specific configuration and programming tool.

– PROFIBUS address:Enter the PROFIBUS address that was assigned to the device using the DILswitch, for example. The default is the PROFIBUS address defined when thePROFInet component was created. If this is already in use, then the lowest freeaddress on the PROFIBUS becomes the default.

Configuring Plants


4. If you use a router (network transition), you must activate the "Network transition,Use router" option and enter the IP address of the router in the "Address" box.

5. Confirm your input by clicking on the

– "OK" button to accept your input and close the dialog box.

– "Accept" button to accept your input and keep the dialog box open.

Result: The assigned addresses are displayed on the device in the network view.

5.7.3 Password Protection for iMap Projects

Effect of the passwordYou can assign a password to your SIMATIC iMap project in order to protect it againstunauthorized access. The password is defined in the project properties and must beentered when you open the project.

If you attempt to open a project and do not enter the correct password, the project willnot be opened.

Defining a passwordTo define a password for the project:

1. Open the project properties using the Project > Properties menu command andfollow the procedure detailed below:

– To enter a new password for the first time, enter the password in the "Newpassword" box and then repeat it in the "Confirm" box.

– To change an existing password, enter the old password in the "Old password"box. Then enter the new password in the "New password" box and then repeat itin the "Confirm" box.


Removing password protectionTo remove the password protection from a project:

1. Open the project properties using the Project > Properties menu command.

2. Enter the old password in the "Old Password“ box and leave the "New Password“and "Confirm" boxes blank.


Configuring Plants


5.7.4 Naming Conventions

RulesThe following rules must be followed when you assign names:

• A file name must not contain any of the following characters:\ / :„?“ * < > |

• A path name must not contain any of the following characters:„?“ * < > | / :

• The name of a chart, PROFInet component, technological function or device mustnot contain any characters with the following ISO 8859-1 code: 0 to 31, 33, 34, 38,42 to 44, 46, 47, 58 to 63, 91 to 94, 96, 124, 127 to 159, 180.

The following characters are not permitted: \ / : „?“ * < > | . & = + [ ] , ; ´` ^!

Spaces are not permitted at the start and end of the name.

• The name of a chart, PROFInet component, technological function or device mustnot exceed 32 characters in length in SIMATIC iMap. This length is reduced to 16characters for PROFInet components created in STEP 7.

• The names of connectors may only contain the following characters (ISO 10646-1):

Letters A to Z and a to z, digits 0 to 9, and the underscore character "_".

• The first character of a connector name must be a letter.

• The name of a connector must not exceed 24 characters in length.

Configuring Plants


5.7.5 Generation status

Status of the Shadow ProjectThe shadow project is generated in SIMATIC iMap from the component projects ofPROFInet components present in the project. The generation status of a PROFInetcomponent is displayed simultaneously in the properties of the correspondingassociated technological function and in the properties of the associated device.

Generation status Meaning Action

Not created The shadow project has notyet been generated or doesnot yet contain thePROFInet component

Generating a ProjectChanges onlyAll

Created The shadow project hasbeen generated, it containsthe PROFInet componentand the properties of thePROFInet component areconsistent with the STEP7shadow project

No action required

Inconsistent/modified The properties of thePROFInet component havebeen modified and are nolonger consistent with theshadow project

Generating a Project

Generation not possible The properties of thePROFInet componentcontain illegal values (e.g.an address is assignedtwice) which makegeneration impossible.

Eliminate the error(s) andthen generate the projectagain

Configuring Plants


5.7.6 Setting the Transfer Frequency

The transfer frequency of an interconnectionA transfer frequency (quality of service) that relates to the quality of the transfer isdefined for every interconnection in SIMATIC iMap.

Every variable value on the sender side of the interconnection (output from atechnological function) is cyclically checked for changes. If the value has changed,then it is transferred to the recipient (input to a technological function). The transferfrequency is thus the latest time after which a changed variable value is sent from thesender to the recipient.

Setting the transfer frequencyTo define the transfer frequency of an interconnection:

1. Select the interconnection in the plant view and select the Edit > Properties menucommand.

2. In the "Properties" dialog, enter the value and the unit of measure of the transferfrequency and click on "OK" or "Accept" to confirm.

Figure 5-7 Defining the Transfer Frequency

Configuring Plants


Setting the transfer frequency for new interconnectionsYou can set a default transfer frequency for all new interconnections.

Proceed as follows:

1. Select the Options > Settings menu command.

2. In the "Transfer frequency for new interconnections" box on the "Plant View" tab,select the value of the transfer frequency and click on "OK" or "Accept" to confirm.

This setting will apply to all subsequently created interconnections. It is retained inSIMATIC iMap until this value is changed.

You can change the transfer frequency of individual interconnection via theinterconnection properties.

Configuring Plants


5.7.7 Configure substitute values

Substitute valuesIf a fault on a device causes the values that are sent via the device's interconnectionsto be no longer valid, then substitute values are activated at the recipient..

Figure 5-8 Example - Substitute values

There is a default substitute value for every interconnection in SIMATIC iMap. Thismay be the last known value or a defined value.

NoteSubstitute values may only be configured for interconnections between PROFInetdevices.

If a PROFIBUS device is involved, only the substitute value 0 may be activated.Exception: For connectors of the type DATE, it is always the last known value thatis activated as a substitute value.

Configuring Plants


Changing the configuration of a substitute valueThe procedure for changing the default substitute value of an interconnection is asfollows:

1. Select the interconnection from the plant view.

2. Select Properties from the context menu.

3. In the "Properties" dialog, activate the desired option in the "Substitute value" box. Ifyou wish to activate a specific value as the substitute value, then enter this value.

4. Click on the "OK" or "Accept" button to accept your changes.

5. Select the function with the affected input (on the recipient side), and selectDownload Selected Device > Interconnection Only from the context menu todownload the reconfigured interconnection to the associated device.

Figure 5-9 Example - Changing substitute values

Result: the change takes effect immediately. If there is already a fault on the device,you can monitor the changed substitute value online.

Configuring Plants


5.8 Creating Subordinate Charts

Subordinate chartsSubordinate charts are used to create a hierarchical structure for your plant, just like adirectory tree in the file system.

In the plant tree of the project view, a subordinate chart is represented as a folder thatcan contain technological functions and further subordinate charts. There are nosubordinate charts in the network tree of the project view.

In the plant view, a subordinate chart looks like a technological function with a chartinterface for creating interconnections. The chart interface contains the inputs andoutputs of the technological functions contained in the subordinate chart, which canextend beyond the limits of individual charts.

Creating a Subordinate ChartProceed as follows:

1. Open the project plant view.

2. Select the Insert > New Chart menu command.

The new chart is inserted and is displayed in both the plant view and the projectwindow.

3. Give the subordinate chart a name

– Via the editable name box in the plant view or

– Via the "Properties" dialog box

4. Open the subordinate chart by double-clicking or using the Open chart contextmenu command.

5. Insert your PROFInet components from the library and interconnect.

6. For each connector to be contained in the chart interface, select the connector andactivate the In Chart Interface option from the context menu If the connector isalready contained in the chart interface, this is indicated by a tick in the contextmenu.

If you then return to the chart one level up, the subordinate chart is represented in thesame way as a technological function with the defined chart interface.

Configuring Plants


Moving Technological Functions to a new ChartIf you want to create a new subordinate chart from several technological functions:

1. Select the technological functions.

2. You have several options: Select:

– the Paste > New Chart menu command or

– the "Insert Chart" icon from the toolbar or

– the Move to new chart command from the context menu (right mouse button).

Result: A new subordinate chart is created and the selected technological functions aremoved to this chart. Any existing interconnections between charts are automaticallyinserted into the chart interface.

Working with Subordinate ChartsYou can work with subordinate charts just as though they were technological functions,i.e. they can be interconnected, moved, deleted, cut and copied.

The content and connectors of a subordinate chart can be modified as required.

It is not possible to download a selected subordinate chart to all devices. To carry out aspecific download, you must select individual objects. If you download to all devices inthe plant, those devices whose functions are contained in the subordinate chart areincluded in the download.

Tip: Navigation aidSelect a connector of a subordinate chart, and select Go To > Function connectorfrom the context menu (right mouse button) to access the associated connector of thetechnological function.

Configuring Plants


5.9 Storing Data in SIMATIC iMap

OverviewData storage in SIMATIC iMap primarily covers the following types of folder:

• PROFInet components

• SIMATIC iMap projects

• SIMATIC iMap libraries

The structure of these folders is described below.

SIMATIC iMap also uses other types of file, such as:

• Archive files

• Project documentation

• Variable tables

• OPC symbol files

In SIMATIC iMap, there are default storage locations for every type of file and folderused.

Project structure for PROFInet componentsDifferent types of project occur during the life cycle of a PROFInet component, and thecontent and structure of these projects are defined by the vendor-specific configurationand programming tool used for the component. We differentiate between the followingtypes of project:

• The basic project is the project from which the PROFInet component is created.

• The component project is assigned to the finished PROFInet component. It isstored in the file system or in a library together with the PROFInet component.

• The shadow project is assigned to a SIMATIC iMap project. It is generated inSIMATIC iMap from the component projects of all the PROFInet componentsinvolved. The shadow project is needed for downloading programs and device-specific data.

Configuring Plants


Figure 5-10 Project structure for PROFInet components

File Structure of PROFInet ComponentsA PROFInet component consists of a folder containing:

• The XML file containing the description of the PROFInet component and, inparticular, the technological function. The system searches for this XML file whenimporting to a library.

• The icon files

• The component project (a copy of the corresponding part in the basic project).

• The file of documentation links (optional).

The folder name is formed from the name, the identification (class ID) and versionnumber of the PROFInet component. This file structure is retained for all instances ofthe PROFInet component.

Configuring Plants


File structure of SIMATIC iMap libraries and projectsA SIMATIC iMap library is created as a folder. This must contain the library file with thesame name and the extension .cbl, which must be specified when the library isopened. A library also contains the folder with the PROFInet components.

A SIMATIC iMap project is created as a folder. This must contain the project file withthe same name and the extension .cbp, which must be specified when the library isopened. A project folder also contains:

• Information on the inserted instances of the PROFInet components

• The shadow project which is generated by generating the iMap project and anycopies of old shadow projects if the project has been regenerated a few times.

• A variable table (if one was created).

Figure 5-11 File Structure of iMap Libraries and Projects

Accessing iMap Libraries and ProjectsSIMATIC iMap libraries and projects behave just like normal documents. You canopen, modify, save and archive them in SIMATIC iMap.

Multiple simultaneous access to SIMATIC iMap projects is not possible.

Configuring Plants


Deleting iMap libraries and projectsYou can delete SIMATIC iMap libraries and projects by deleting the folder concernedfrom the file system using Windows Explorer.

CautionThe PROFInet components used must be present in the library in order togenerate a project. Before you delete an iMap library, make sure that thePROFInet components are no longer used in your projects.

Default storage locationsThe Options > Settings menu command on the "Directories" tab displays the defaultdirectories for use as the storage locations for the file types used in SIMATIC iMap.These directories are suggested when you create, save and select the correspondingfile types.

Click on the "Change" button to change the paths.

These settings apply to all SIMATIC iMap projects.

5.10 Editing in the Vendor-Specific Programming and Configuration Tool

Accessing the vendor-specific programming and configuration toolYou can call the vendor-specific programming and configuration tool fromSIMATIC iMap in the following ways:

• Modify a technological function in the plant view

• Modify a device in the network view

Depending on which object you have selected, you can open certain applications in thevendor-specific engineering tool in order to edit parts of the PROFInet component.

Read the documentation for the PROFInet component to identify the available editingoptions.

Configuring Plants


Editing in the vendor-specific programming and configuration toolProceed as follows:

1. Select the object to be edited:

– The technological function in the plant view or project window

– The device in the network view or project window.

2. Select Edit > Special using one of the available commands. These commands aredevice-specific. The menu is grayed out if there is nothing to edit or if nothing hasbeen generated yet.

3. Save any changes and download them to the target system.

CautionWhen you are editing with the vendor-specific configuration and programming tool,you must make sure that no inconsistencies or other errors occur in the editedcomponent project or shadow project

In the event of an error, you may find that you have to generate the SIMATIC iMapproject again.

CautionWhen you regenerate the iMap project using the Project > Generate > All menucommand, any changes you have made using the vendor-specific configurationand programming tool will be lost. A copy of the old shadow project is created,however.

Changes you make using the vendor-specific configuration and programming toolcannot be undone in SIMATIC iMap.

Configuring Plants


5.11 Working with Modified PROFInet Components

When you import a new version of a PROFInet component into a library,SIMATIC iMap provides a simple way to replace instances of the previous versionalready present within the project with instances of the more recent version.

RequirementsBefore using a changed PROFInet component, you must first make sure that thecomponent is located in one of the open libraries. If necessary, you must import thePROFInet component into the library or open the library in which it is located.

You can only replace instances if the old and new versions of the PROFInetcomponent have identical bus ports. For example, a PROFInet device with Ethernetconnector cannot be replaced with a PROFIBUS device (DP slave).

Replacing an instance of a PROFInet componentProceed as follows:

1. Select the new PROFInet component from the library.

2. Hold down the ALT key and drag this PROFInet component onto the instance to bereplaced. The target may be either the technological function or the device of theinstance. Release the ALT key when the cursor changes shape.

If you drag the PROFInet component into the project without holding down the ALTkey, an instance of the new PROFInet component is inserted without replacing theexisting instance.

3. You are asked whether you wish to replace the instance. Click on "Yes" to confirm.

Result. The selected instance is replaced with an instance of the selectedPROFInet component.

4. Generate the project using the Project > Generate > Changes Only menucommand.

5. Use the Download Selected Device > All menu command to download all theprogramming and configuration data to the target system.

NoteThe properties of the old instance, such as the names, address(es) and optionallythe transfer frequency of the interconnections are transferred to the new instance.

If there are differences in the technological functions, the instance is still replaced,and the applicable rules are those that apply to moving interconnections.

Configuring Plants


5.12 Creating an OPC Symbol File

OPC symbol filesIn SIMATIC iMap, you can create OPC symbol files for the current project that can beanalyzed using client programs on the SIMATIC NET PN OPC servers. The OPCsymbol files are created for the entire iMap project and are stored in the folder of yourchoice.

RequirementThe SIMATIC iMap project must have been generated. If the project contains objectsthat do not have the generation status "Created", you cannot create an OPC symbolfile.

ProcedureThe procedure for creating the OPC symbol file is as follows:

1. Select the Options > Create OPC Symbol File menu command.

2. In the "Save OPC symbol file as" dialog, select a directory from the "Search in" boxand enter a name in the "File name" box.

Result: Two symbol files with the entered file names and the file extensions .ssd and.wsd are created and are stored in the selected folder.

NoteSelect the Options > Settings menu command to define a directory for storingOPC symbol files. This directory is suggested by default when you look up thestorage location.

The created OPC symbol files can be integrated into the SIMATIC NET PN OPCserver configuration.

CautionNetwork load on the Industrial Ethernet and in the devices of the plantAdditional communication functions are performed on the Industrial Ethernet - inaddition to those via OPC - for monitoring connectors,Note that the network load can be affected both by the number of connectors thatare monitored and the frequency of the value changes.

Configuring Plants


5.13 OPC Information Variables for SIMATIC iMap

SyntaxAt the OPC interface, process variables are identified by a unique name - the OPCitem ID. The OPC item ID is made up of the following:

<Protocol ID>:[<Connection name>]<Variable name>

The individual components have the following significance for PROFInet:

• The protocol ID specifies the protocol used to access the process variable. Theprotocol ID "PN" is used for the PROFInet protocol.

• The connection name specifies the connection or the device via which the variablecan be reached.

• The variable name is the symbolic name of the variable.

Accessing variables via symbolsIn the browser (e.g. the SIMATIC NET symbol file wizard), the process variablesymbols are displayed in the following hierarchical order:

Project [<chart>] <function> <variable>

Where "Project" is the main chart and <chart> is a subordinate chart. Subordinatecharts are optional and may have multiple levels. <function> is the name of thetechnological function and <variable> is the name of the input or output.

Variable Types for PROFInetIn PROFInet, we differentiate between the following three types of variables:

• Process variables

• System variables

• Device-specific information variables

Configuring Plants


Process variablesProcess variables are assigned to the inputs and outputs of technological functions.The OPC item ID of a process variable has the following structure:

PN:[aaa.bbb.ccc.ddd|<devicename>|<funcname>]<variable>

Designation Explanation

aaa.bbb.ccc.ddd • For PROFInet devices - the IP address of the device• For PROFIBUS devices - the IP address of the master (proxy)

< devicename > Name of the configured device in iMap< funcname > Name of the technological function in iMap<variable> Name of the input or output of the technological function

Access rights to process variablesProcess variables for inputs can both be written and read.

Process variables for output can only be read.

Example - Process variablesRepresentation of process variables in the SIMATIC NET symbol file wizard

Figure 5-12 Example – Process variables

System variablesThese information variables are located in the browser's "&System" folder. They applyto the entire plant.

Configuring Plants


Variable icon OPC item ID Meaning

&localhost PN:[SYSTEM]&localhost() Designation of the host computer

&version PN:[SYSTEM]&version() Version of the PROFInet coreserver

Example - System variablesRepresentation of system variables in the SIMATIC NET symbol file wizard

Figure 5-13 Example – System variables

Device-specific information variablesThese information variables are located in the "&DevicePlan" folder and are assignedto the individual devices.

Variable icon OPC item ID Meaning

&statepath PN:[aaa.bbb.ccc.ddd|<devicename>]&statepath()

Status of the connection as astring

&statepathval PN:[aaa.bbb.ccc.ddd|<devicename>]&statepathval()

Status of the connection as avalue

&statepath()Returns the state of a communication link to a partner device as a string.

Returned values:

Configuring Plants


• DOWN - Connection not established

• UP - Connection established

• RECOVERY - Establishing connection

• ESTABLISH (reserved for future upgrades)

Data types:

OLE data type Visual Basic type

VT_BSTR STRING

&statepathval()Returns the state of a communication link to a partner device.

Returned values:

1 - Connection not established

2 - Connection established

3 - Establishing connection

4 (reserved for future upgrades)

Data types:

OLE data type Visual Basic type

VT_UI1 BYTE

Configuring Plants


Example - Device-Specific Information VariablesRepresentation of device-specific information variables in the SIMATIC NET symbolfile wizard

Figure 5-14 Example – Device-specific information variables


Online operation 66.1 Overview of the Online Functions

SIMATIC iMap in the Online and Offline ViewSIMATIC iMap must be connected to the plant via Ethernet in order to monitor thedevices online. Both PROFInet and PROFIBUS devices (via a PROFInet device withproxy functionality) can be accessed via the online connection. SIMATIC iMap is in theoffline view by default (no connections to the devices are established). Online modemay be switched on and off for individual views in SIMATIC iMap.

• Variable table - by clicking on the "Monitor variables online" icon or via the Online >Variable Table > Monitor Variables menu command.

• All other views (e.g. the plant view, network view or the "Functions" and "Devices"tabs in the diagnostic window) by clicking on the "Monitor Online" icon or via theOnline > Monitor menu command.

Online operation


NoteIf several instances of SIMATIC iMap have been started, online monitoring shouldonly be active in one application.

Starting multiple instances of SIMATIC iMap in the online view would increase theprocessor load in the devices of the plant.

Online FunctionsSIMATIC iMap offers the following functions for starting and for controlling andmonitoring the plant during operation:

Online monitoring activated

• Diagnosis for devices, functions and interconnections

• Downloading interconnections to the devices of a plant

• Displaying and setting online values

• Displaying the module status (depending on the device type)

• Displaying the operating status (depending on the device type)

Online monitoring deactivated

• Comparison between the online and offline interconnection and program data

• Downloading programs to the devices of a plant

• Checking the accessibility of devices

• Device-specific online function via the vendor-specific configuration andprogramming tool.

Possible actions in the online viewIf Monitor Online is activated, certain actions that change the project, such ascopying, pasting, deleting and interconnecting are disabled. Generating, documentingand archiving/retrieving are also unavailable in the online view.

Actions such as viewing (not changing) properties, printing the current window andcalling the Edit > Special... menu command are still possible in the online view,however.

Online operation


6.2 Diagnostic Concept for PROFInet Components

IntroductionWhen SIMATIC iMap is connected online to the plant, it provides information ingraphical format about

• The availability and status of the PROFInet stations,

• The status of the interconnections and online values, and

• The operating status of the devices (depending on the device type)

Online-Offline ComparisonSIMATIC iMap allows you to compare the online and offline interconnection andprogram data. The result of an online-offline comparison is displayed:

• as text in the information window and the diagnostic window, and

• as graphical information in the plant and network views, and in the diagnosticwindow. Graphical information means:

– Icons, e.g. "Interconnection download required" or

– Colors of objects, e.g. grey devices are not accessible.

Status of the PROFInet Communication NodesFrom the viewpoint of PROFInet communication the nodes have certain states whichare indicated in SIMATIC iMap by icons and diagnostic messages.

• The following information is displayed in the network view:

– Whether the devices are available online

– Whether a diagnostic interrupt has occurred on the devices

– Whether an interconnection download is required.

• The following information is displayed in the plant view:

– Whether the devices are available online

– Whether a diagnostic interrupt has occurred on the associated devices,

– Whether interconnections are functioning correctly,

– Whether online values are valid,

– Whether an interconnection download is required.

An online-offline comparison determines whether a download is required.

Online operation


Table 6-1 Diagnostic Icons

Icon/Display Meaning

The device is not available

The device is faulty orthe interconnection to the device is faulty

An interconnection download is required

Device-specific diagnostics available.You can look up diagnostic information in the device-specificconfiguration and programming tool using the Special >Diagnose hardware or Special > Module information menucommand.For a subordinate chart, this icon indicates that one or moredevices within the chart is/are faulty.The device can be accessed, but its state cannot bedetermined. (This can happen to a DP slave, for example, if theDP master state is STOP).

No icon The device is OK

Status of the interconnectionsThe status is indicated by the color of the interconnection line:

Color of the interconnectionline

Meaning

Black the interconnection is OKGreen The interconnection has been selectedRed The interconnection is faulty (the fault generally occurs at

the output from the technological function of the sendingdevice)

Gray There is no information about the interconnection (e.g. ifthe device is unavailable or a download is required)

Online operation


Diagnostic Messages in the Diagnostic WindowWhen SIMATIC iMap is connected online to the plant, current messages are displayedin the diagnostic window

• The "Functions" tab displays diagnostic messages on the technological functions,for example a list of the functions for which the interconnections must bedownloaded.

• The "Devices" tab displays diagnostic messages on the devices, for example a listof faulty or unavailable devices.

The inaccessible devices are displayed hierarchically by DP master system so thatall the DP slaves assigned to a DP master can be recognized readily.

NoteIf a PROFInet device with proxy functionality (DP master) is faulty orunavailable, no diagnostic messages or icons are displayed for the associatedPROFIBUS devices.

ExampleExample Display

Diagnostic window,"Functions" tab

Diagnostic window,"Devices" tab

Online operation


6.3 Diagnosing PROFInet Components

Main Diagnostic ProcedureWhen diagnosing PROFInet components in SIMATIC iMap you can either follow thisprocedure or carry out specific individual actions:

Figure 6-1 Main Diagnostic Procedure

Online operation


Diagnosis ScenariosThe individual diagnosis scenarios are described in the following table.

Diagnosisscenario

Possible causes Possible remedies

The device is notavailable

• Communication fault, for example,cable break, cable not connected

• Error in the hardware configuration(incorrect configuration)

• The device has not been started orhas not been initialized completely

• The device is switched off• The program has not been loaded yet• The device is not a PROFInet device

• Check the communication links• Check the hardware configuration• Check the IP addresses and subnet

masks• Check the PROFIBUS addresses• Eliminate the fault• Switch on or start device• Download program to the device

The device has afault

• Error in the program• The device has STOPped

• Call up device-specific diagnostics• Eliminate the error• Download program to the device

Programdownload isrequired

• Online-offline comparison indicateddifferences between the device-specific offline data in SIMATIC iMapand the online data in the device

• Download program to the device

Downloading oftheinterconnectionsrequired

• The interconnection data in SIMATICiMap and in the device differ.

• Download interconnections into thedevice

Aninterconnection isfaulty

• Communication fault, for example,cable break, cable not connected

• The interconnection data in SIMATICiMap and in the device differ.

• Communication partner of the devicehas a fault or is not available.

• Check the communicationconnections

• Check the IP addresses and subnetmasks

• Check the PROFIBUS addresses• Run an online-offline comparison of

the interconnections and• Eliminate the fault or• Download the interconnection to the

partner device

Online operation


6.4 Comparing the Online and Offline Data

Comparison optionsIf SIMATIC iMap is linked to a device of the plant via Ethernet, it is possible to run anonline-offline comparison for one or more devices or technological functions. Thiscompares the online data in the plant with the offline data in the SIMATIC iMapproject.You can compare the following data in SIMATIC iMap:

• Program Only – all the blocks in the user program, including all device-specific datasuch as the hardware and network configurations.

• Interconnection Only – connectors and interconnections of the technologicalfunctions

Online-Offline Comparison of InterconnectionsAn online-offline comparison of the interconnection identifies any differences betweenthe online and offline technological function, in addition to any interconnections thathave been added or removed:

• Added or removed inputs and outputs

• Different data types for connectors

NoteThere is no automatic online-offline comparison of interconnections before theyare downloaded, since this would extend the run time. For security reasons, wetherefore strongly recommend that you run a comparison before downloading toavoid run time errors.

Requirements• Your PC/programming device must be connected to the plant via the Ethernet.

• The SIMATIC iMap project must have been generated before you can run theonline-offline comparison for programs.

• Online monitoring must be switched off in SIMATIC iMap.

Online operation


Comparing programs1. Select

– the required devices from the network view or

– the required technological functions from the plant view.

2. Select Online-Offline Comparison > Program Only from the context menu.

The result of the comparison is displayed in the information window.

Example: Comparing programsComparison of the program and configuration information before online monitoring.Devices in which differences were found are identified by a STOP symbol.

Figure 6-2 Online-offline comparison of programs

Comparing interconnections1. Select

– the required devices from the network view or

– the required technological functions from the plant view.

2. Select Online-Offline Comparison > Interconnection Only from the contextmenu.

Online operation


The result of the comparison is displayed in the information window.

Additional error messages may be displayed for faulty interconnections (see"References, Error numbers for PROFInet devices")

Example: Comparing interconnectionsIn the following diagram, the comparison shows that the interconnections will have tobe downloaded.

Figure 6-3 Online-offline comparison of interconnections

6.5 Check Accessibility of the Devices

RequirementYour PG/PC must be connected to the plant via Ethernet in order to check theaccessibility of the devices.

Online operation


Accessible deviceA device in the plant must be accessible using PROFInet communication mechanismsin order to carry out a download or to monitor variables.

SIMATIC iMap provides several ways of checking whether a PROFInet device isaccessible online.

• If online monitoring is activated:

– The accessibility of the device is represented graphically in the network andplant views: accessible devices are blue and non-accessible devices are greyand have a diagnostic icon.

– The non-accessible devices are listed on the "Devices" tab in the diagnosticwindow.

• If online monitoring is deactivated, you can look up the accessibility of individualdevices.

Looking up accessibilityTo look up the online accessibility of a device:

1. Switch of the "Online Monitoring" option using the Online > Monitor menucommand, for example.

2. Select the device from the network view or the technological function from the plantview. You may also select several objects.

3. Select:

– Check Accessibility from the context menu or

– the Online > Check Accessibility menu command.

Result: The online accessibility of the devices is checked and the results are displayedin the information window.

Online operation


Possible messages

Message Possible causes Remedy

No station isavailable at the IPaddress<IP_Address>.

• The physical connection to the device is faultyor not available.

• The device is not switched on.• For PROFIBUS devices: The associated

PROFInet device with proxy functionality isnot accessible or is in STOP mode.

If the device is a PROFInet device with proxyfunctionality, any PROFIBUS devices coupled toit will also be inaccessible.

• Check the connection orcable

• Switch on the device• Check the PROFInet

device with proxyfunctionality (DP master)

The PROFInetaccess to the device<IP_Address> is notavailable

The device is physically connected, but• it is not on standby (e.g. set to STOP) or• it has no PROFInet configuration data

• Switch the device to RUN• Download the program

The logical device<device name>(proxy at <IPaddress>) isaccessible, while thephysical device isnot.

For PROFIBUS devices only:The PROFInet configuration data for the device islocated on the associated PROFInet device withproxy functionality (proxy DP master), but the linkbetween the DP master and DP slave isinterrupted.

Check the PROFIBUSconnection between the DPmaster and DP slave.

The device <devicename> is accessible

Logical deviceThe logical device is the part of the runtime software that is responsible for thePROFInet communication of a device, and which is addressed during online monitoringby SIMATIC iMap. The PROFInet configuration data of a component that isdownloaded to the device is assigned to this logical device.

NoteThe logical device of a PROFIBUS device is on the associated PROFInet devicewith proxy functionality (proxy DP master).

If the logical device of a PROFIBUS device is signalled as accessible, but thedevice is represented as non-accessible in the online view, then this may bebecause: The PROFInet configuration of the PROFIBUS device s OK, but thephysical device of the DP slave is not accessible because the connection to the DPmaster is faulty, for example.

Online operation


Example: Accessibility

Figure 6-4 Representation in the network view

Figure 6-5 Message in the information window

Online operation


6.6 Downloading Programs and Interconnections

Download OptionsThe term "downloading" means loading data from SIMATIC iMap onto a programmablecontroller or field device. The following data can be downloaded from SIMATIC iMap tothe devices of the plant:

• Program

Downloading of the user program including all the device-specific data, such as thehardware configuration and network configuration. The device-specific configurationand programming tool, for example STEP 7, is required for the program download.

• Interconnections

Downloading of the interconnection information into the corresponding devices ofthe plant. Interconnections may be downloaded from SIMATIC iMap without thedevice-specific configuration tool.

• All

Loads the program and interconnections onto the devices of the plant. The device-specific configuration and programming tool is required for this purpose.

The following downloads are possible, depending on which objects are selected:

Selected Possible download Menu command

Nothing selected for the complete project• All• Program Only• Interconnection Only

Main menuOnline > Download All Devices> All> Program Only> Interconnection Only

One or moreobjects(technologicalfunction ordevices) selected

for the selected objects• All• Program Only• Interconnection Only

Main menuOnline > Download All Devices> All> Program Only> Interconnection OnlyContext menuDownload Selected Devices> All> Program Only> Interconnection Only

Online operation


NoteMake sure that the program and interconnections are download to a device fromone instance of SIMATIC only at any given time.

If the wrong IP addresses are used, the user program in the affected target systemmay be overwritten.

Target of the download

Download... Selected device toSIMATIC iMap

Download target device within the plant

Program PROFInet device Relevant PROFInet devicePROFIBUS device Relevant PROFIBUS device

Interconnections PROFInet device Relevant PROFInet devicePROFIBUS device Associated PROFInet device with proxy

functionality

NoteAdditional steps may be needed to permanently store the downloaded data to thedevice, depending on the device type.

When Is A Download Required?The program must be downloaded when a device is commissioned. Interconnectionscan be downloaded later if required, for example in order to test the PROFInetcommunication between the components.

You can determine whether a program download is necessary by carrying out anonline-offline comparison.

Online operation


The devices and technological functions for which an interconnection download isrequired are identified by a vertical arrow and are listed on the "Devices" or "Functions"tab in the diagnostic window.

Figure 6-6 Download required

Requirements for the download• All instances of the PROFInet components for which the download is to be carried

out must have the generation status "Created" in their properties. You may have togenerate the SIMATIC iMap project.

• Your PC/programming device must be connected to the plant via the Ethernet.

• The devices must be accessible.

• For program downloads only: Online monitoring must be switched on inSIMATIC iMap.

Online operation


Downloading to All DevicesSelect one of the following commands from the main menu in the project network orplant view:

• Online > Download All Devices > Program Only, in order to download theprograms to all the devices of the plant

• Online > Download All Devices > Interconnections Only, in order to downloadthe interconnections to all the devices of the plant

• Online > Download All Devices > All, in order to download the programs andinterconnections to all the devices of the plant.

Result: The desired data is downloaded to all the devices of the plant. Information onthe progress and completion of the action and any error messages are displayed in theinformation window.

Download to Selected DevicesProceed as follows:

1. Select the PROFInet component(s) for which a download is to be carried out. Theoptions are as follows:

– One or more technological functions in the plant view or project tree.

– One or more devices in the network view or project tree.

2. Select one of the following commands from the context menu:

– Online > Download Selected Devices > Program Only, to download theprogram only

– Online > Download Selected Devices > Interconnection Only, to downloadthe interconnections only

– Online > Download Selected Devices > All, to download both the program andthe interconnections.

Result: The desired data is downloaded to those devices of the plant which areassigned to the selected objects. Information on the progress and completion of theaction and any error messages are displayed in the information window.

Online operation


Order during the program downloadWhen you download programs to selected devices, you must first download theprogram to the PROFInet device with proxy functionality and then to the coupledPROFIBUS devices.

When you couple or uncouple PROFIBUS devices, a program download to theassociated PROFInet device with proxy functionality and to all intelligent PROFIBUSdevices associated with the DP master system is required.

CautionWhen you download the program to a PROFInet device, both the interconnectionsof the actual PROFInet device and the interconnections of any coupled PROFIBUSdevices are deleted.

You will then have to download the interconnections to all devices of the DPmaster system once more.

Download Interconnections

Caution

Interconnections are downloaded into the target system regardless of the operatingmode or level of protection on the target system. Existing interconnections aredeleted. Make sure that all settings, such as function names and IP addresses,have been made correctly in order to guarantee the security of your plant. Thesame applies to the "Download" button in the diagnostic window.

Select the Online > Online-Offline Comparison >... menu command to determinethe differences between the SIMATIC iMap project (offline) and the plant (online).

Online operation


Examples

Table 6-2 Examples: Download required

Example Display

Function,interconnectiondownload required

Device,interconnectiondownload required

List of functions withfaults

List of devices withfaults

Online operation


6.7 Displaying and Setting Online Values in the Plant View

Online Values of PROFInet VariablesThe online values of PROFInet variables are the current values in the plant

In the Online view of SIMATIC iMap you can:

• Monitor selected online values at the connector of technological functions,

• Set online values of individual inputs once in order to test a PROFInet component inthe commissioning phase, for example,

• Monitor and set online values in the variable table (see the section entitled "OnlineTesting with the Variable Table).

The procedure for displaying and setting online values in the plant view is describedbelow.

RequirementsSIMATIC iMap must be connected to the plant online ("Monitor" button pressed).

Display Online ValuesProceed as follows:

1. select the required connectors of the technological function(s) from the plant view.

2. Select the Online > Display Online Values or Display Online Values commandfrom the context menu.

Result: The online values of the connectors are displayed in the plant view.

The online values are updated dynamically.

CautionNetwork load on the Industrial Ethernet and in the devices of the plant

Additional communication functions are performed on the industrial Ethernet formonitoring connectors.

Note that the network load can be affected both by the number of connectors thatare monitored and the frequency of the value changes.

Remedy: Individually select the connectors whose values you wish to monitoronline.

Online operation


NoteThe number of online values of the type Array that can be displayed is limited to 16elements. Larger arrays must be visualized via OPC.

Validity of online valuesThe validity of displayed online values is indicated by different colors.

Color of the online value Significance: the value is ...

Black validRed invalid (e.g. due to a fault or immediately after setting, if

the online value has not yet been confirmed in the targetsystem)

Red question mark no value has yet been confirmed or the device is notaccessible

Gray uncertain (the validity cannot be determined)Gray italic an alternative value

Example: Displaying Online Values

Figure 6-7 Displaying online values

Setting Online ValuesProceed as follows:

1. Select the desired input of a technological function in the plant view.

2. Select the Online > Display Online Value menu command.

Online operation


Result: The online value of the connector is displayed.

3. Click on the value or select the Online > Set Online Values menu command.

Result: Depending on the data type of the connector either

– A selection box with the permitted values, e.g. True and False for the data typeBOOL or

– An edit box for all other data types is displayed.

4. Select the required value or enter it in the edit box and press Enter to confirm.

Result: The entered value must be confirmed from the device in the plant. It can thenchange to black, red or gray (see above "Validity of the Online Values").

The set value is not confirmed if the device cannot be accessed online or if a fault hasoccurred. In this case, the last known value is displayed in red or a red question markis displayed.

The value remains constant as long as this input is not interconnected or modified bythe user program of the technological function. If the input is interconnected viaSIMATIC iMap, the online value can be modified via the interconnection.

NoteOnline values of the data type Array cannot be set

Tip: You can also interconnect inputs to constant values for testing purposes.

Online operation


Example: Setting an online valueSetting an input of the DATE type.

Figure 6-8 Setting Online Values

Online operation


6.8 Online Testing with the Variable Table

6.8.1 Creating the Variable Table

Structure of the variable tableThe variable table contains the variables of the connectors to be tested online.

Table 6-3 Structure of the variable table

Column Meaning

No. Line numberAutomatically indicates whether the entry is deactivated,monitored online or is not accessible

Device Here you can enter the device names or select them from a list.Function Here you can enter the function names or select them from a

list.Connector Here you can enter the connector names or select them from a

list.Type The data type of the connector is displayed here.Format Here you can select the display format for the online value.

<Automatic> means the default format, e.g. decimal for I1, I2,UI1, R4 or True/False for BOOL.

Online value Displays the online values when the variable is monitoredonline.

Control value Here you can enter control values for inputs. You can transferthese values to the plant at any time in order to set thecorresponding online values.

Comment A comment is entered here.

Select the Columns > command from the context menu to show/hide individualcolumns.

Online operation


Inserting entriesThe procedure for inserting entries is as follows:

1. In the diagnostic window, select the "Variable table" tab.

2. Select the required connectors or technological functions from the plant view, anddrag them into the variable table.

Result: An entry is added to the variable table for every inserted connector.

You can insert entries in the following ways:

• Enter data directly into the "Function" and "Connector boxes or

• Select the function and connector from the drop-down list.

The other boxes are filled in automatically.

RuleThe variable table can hold up to 50 entries.

Invalid entries are shown in red. Variables with invalid fields cannot be monitored.

Example - Variable tableThe following variable table contains the connectors of the "Coordinator" function.

Moving, copying, cutting and deleting entriesMove

Online operation


You can move selected entries within the variable table using drag-and-drop

Copy, cut and delete

To copy, cut or delete selected entries, select the appropriate commands from thecontext menu.

Sorting entriesYou can sort the entries by clicking on the required column header.

Saving the variable tableThe variable table is always saved together with the SIMATIC iMap project. If you wishto store a variable table in the file system in order to test another project, for example,then you will have to export it.

Exporting a variable tableProceed as follows:

1. Select the Options > Export Variable Table menu command.

2. In the "Export Variable Table" dialog, select a directory from the "Search in" box.

3. Enter a file name in the "File name" box or select a name from the list.

4. Click on the "Save" button.

Result: The current variable table is stored in the file system. The file name always hasthe extension .CBV

Online operation


Importing a variable tableBy importing, you can copy a variable table from the file system to the currently openSIMATIC iMap project.

NoteThe existing entries are overwritten when you import the variable table. Werecommend that, if necessary, you back up the current variable table before theimport using the Options > Export Variable Table menu command.

Proceed as follows:

1. Select the Options > Import Variable Table menu command.

2. Select the desired variable table from the "Import Variable Table" dialog. Look for afile name with the extension .CBV.


Result: The entries in the imported variable table are copied to the project variabletable.

Default storage location for variable tablesSelect the Options > Settings menu command to define a directory for storingvariable tables on the "Directories" tab. This directory will be suggested whenever youimport and export variable tables.

Online operation


6.8.2 Online Monitoring and Control of Variables

OverviewThe variable table is used to test the plant by:

• monitoring selected variables online and

• assigning control values to selected variables during the testing phase.

You can only monitor variables if their entries have been activated in the variable table.You can exclude selected variables from the monitoring by deactivating the associatedentries in the variable table.

The variable table allows you to monitor variables online regardless of whetherMonitor is switched on in the plant or network view. You can monitor selected or allactive variables in the variable table.

You can enter control values for selected input variables. You can then assign thesecontrol values to the variables for testing purposes, and thus replace their currentonline values.

Deactivating and reactivating entriesThe procedure for deactivating entries is as follows:


2. Select the entries. Hold down the CTRL key at the same time to select severalentries.

3. Select the Deactivate command from the context menu.

Result: The selected entries are identified by a cross symbol. The associated variablescan no longer be monitored.

To be able to monitor such variables once more, you will have to reactivate the entriesby selecting the Reactivate command from the context menu.

Online operation


In the following example, entries no. 1 and 2 have been deactivated.

Figure 6-9 Example - Deactivate entries in the variable table

RequirementYour PG/PC must be connected to the plant via Ethernet in order to monitor variablesand set online values.

Start monitoringProceed as follows:


2. Select:

– the Online > Variable Table > Monitor Variables menu command or click onthe "Monitor variable table" icon to monitor all active variables, or

– the desired entries, and then select the Monitor command from the contextmenu in order to monitor only the selected variables.

Result: All or the selected entries are identified in the second column with a "Monitor"symbol (glasses), and the current online values of the variables are displayed in the"Online value" column. The online values are displayed in the defined format."<Automatic>" means the default display format, e.g. decimal for I1, I2, I4, UI1, UI2,UI4, R4 or True/False for BOOL.

No online values are displayed for deactivated entries.

Variables of non-accessible devices are identified with a separate symbol (glasses withcross).

The validity of the displayed online values is represented by different colors, as for theonline values in the plant view.

Online operation


NoteChanges to the interconnections in the plant that were not made using theSIMATIC iMap application are not automatically displayed in the variable table. Toupdate the variable table, you will have to switch online monitoring of the variablesoff and on again.

Example - Variable table onlineThe diagram contains the following:

• Variable no. 1 and 2 cannot be monitored because the associated device is notaccessible.

• Variable no. 5 and 7 have been deactivated.

• All the other variables are monitored.

Stop monitoringProceed as follows:

• Select the Online > Variable Table > Monitor Variables menu command again orclick on the "Monitor variable table" icon again to stop monitoring all variables.

• Select the desired entries from the variable table, and then select the Do notmonitor command from the context menu in order to stop monitoring the selectedvariables.

Online operation


Set Online ValuesFor input variables, you can enter control values that can be set as online values fortesting purposes. You cannot set online values at outputs.

Proceed as follows:


2. Enter the control values in the boxes in the "Control value" column, ensuring thatthe values are interpreted in the display format, e.g. if Hexadecimal is set in the"Format" box for a variable, then you must also enter the control value inhexadecimal.

3. Select the variables whose online values you wish to set.

4. From the context menu, select the Monitor command to start monitoring thesevariables.

5. From the context menu, select the Set Online Values command or click on the "SetOnline Values" icon.

Result: The control values are transferred to the plant and appear in the boxes in the"Online value" column.

No online values are set for deactivated entries and variables of non-accessibledevices.

NoteIf a variable is selected more than once for setting online values, then the processis interrupted with an error message, and no online values are set.

Copy Online ValueTo copy the online value of a variable, select the Copy Online Value command fromthe context menu.

Result: The online value is copied to the clipboard.

TipsYou can enter control values regardless of whether the monitoring of variables in thevariable table is switched on or off. No input is possible for deactivated and invalidentries.

Control values that have already been transferred are displayed in gray.


SIMATIC Devices for Component basedAutomation 77.1 SIMATIC Devices as PROFInet Components

7.1.1 Overview of SIMATIC Devices

Types of SIMATIC deviceYou can create PROFInet components from the following types of SIMATIC device:

• Central processing units with centralized and distributed peripherals

• PCs with a Windows logic controller for PROFInet (WinLC PN)

• "Intelligent" DP slaves (I-slaves), i.e. DP slaves with programmable functionalityrunning their own S7 programs.

• DP slaves with fixed functionality

Bus portsThe device's bus ports are shown in the SIMATIC iMap network view.

PROFInet devices can have the following bus ports:

• Industrial Ethernet – always

• PROFIBUS DP as a DP master with proxy functionality with respect to PROFIBUSdevices – on some devices only

PROFIBUS devices used as DP slaves have only one PROFIBUS connector.

SIMATIC Devices for Component based Automation


Table 7-1 Representation of the devices in SIMATIC iMap

Bus Ports Representation in SIMATIC iMap

PROFInet device on the Industrial Ethernet

PROFInet device on the industrial Ethernetand as a DP master on the PROFIBUS

PROFIBUS deviceDP slave on the PROFIBUS

The internal networking of the devices via a local PROFIBUS or MPI bus, for example,cannot be seen in SIMATIC iMap.

Representation: Devices and FunctionsA PROFInet component is represented as follows in SIMATIC iMap:

• As a PROFInet component – unit consisting of device and technological function –in the library,

• As a PROFInet or PROFIBUS device in the network view and

• As a technological function (if present) in the plant view.



FunctionalityWe differentiate between PROFInet components:

• with programmable functionality

These components have their own S7 program which can be downloaded fromSIMATIC iMap to the module (e.g. to a CPU or WinLC PN).

• with fixed functionality

These components do not have their own S7 program, e.g. ET 200M or IE/PB Link.

Features of STEP 7 ProjectsPROFInet components from SIMATIC devices are created from STEP 7 projects inSIMATIC Manager. The following features are important:

• Station

The device from which the PROFInet component is created may be located in aseparate station in SIMATIC Manager (e.g. a CPU or WinLC PN), or it may beconfigured as a DP slave with fixed functionality (e.g. ET 200M) on any DP mastersystem. In the second case, the DP master is not part of the PROFInet componentto be created.

• Local PROFIBUS

Programmable controllers, such as CPUs or WinLC PN, may be configured as DPmasters with a local PROFIBUS DP master system. In this case, the entire local DPmaster system is part of the PROFInet component, but the local DP slaves still donot appear in SIMATIC iMap.

• Local MPI bus

CPUs may be configured with a local MPI bus in order to integrate an HMI device.In this case, the HMI device is part of the PROFInet component, but neither the HMIdevice nor the MPI bus can be seen in SIMATIC iMap.

• Blocks required

The block folder of the S7 program must contain the following blocks which, in turn,contain the interface declaration for the technological function.

– Interface DB - for all PROFInet components that contain a technological function

– Additional blocks for intelligent DP slaves, for example

Information on blocks can be found under "Creating PROFInet components withSTEP 7".



NoteA PROFInet component can have either a local PROFIBUS or a local MPIconnector. Both connectors are not permitted in a component.

Off-the-shelf PROFInet componentsThe following PROFInet components are supplied with the PROFInet product:

• IE/PB Link

• Repeater diagnostics

• ProTool/ Pro visualization device

Available as System components in the \imap\components directory.

Summary

Table 7-2 Features of SIMATIC devices as PROFInet components in SIMATIC iMap

Type of device Bus Ports Representation inSIMATIC iMap

Functionality

Win LC PN EthernetPROFIBUSmaster

1 PROFInet device1 technological function

Programmable

S7-300 CPU withCP 343-1 PN

Ethernet 1 PROFInet device1 technological function

Programmable

S7-300 CPU as anintelligent DP slave

PROFIBUS slave 1 PROFIBUS device1 technological function

Programmable

ET 200X , BM 147 /CPU ET 200S, IM 151 /CPU


Programmable

Standard slaves and S7slaves as DP slaves withfixed functionality


Fixed



Table 7-3 Features of PROFInet components in STEP 7

Type of device Station LocalPROFIBUSis possible

Local MPIbus is

possible

Blocksrequired

Win LC PN Separate station Yes No Interface DBS7-300 CPU withCP 343-1 PN

Separate station Yes Yes interface DBadditional FB

S7-300 CPU as anintelligent DP slave

Separate station Yes Yes Interface DB foradditional DB,FC

ET 200X , BM 147 /CPU ET 200S, IM 151 /CPU

Separate station No No Interface DB foradditional DB,FC

Standard slaves and S7slaves as DP slaves withfixed functionality

DP slave on astation with anyDP master

No No Interface DB



7.1.2 Configurations for PROFInet Components

Device types in Component based AutomationWe differentiate between the following types of device downstream of the busconnectors:

• PROFInet devices

• PROFIBUS devices

PROFInet deviceA PROFInet device always has an Ethernet connector. A PROFInet device may alsohave a PROFIBUS connector as a proxy master for PROFIBUS devices.

Possible Configurations for a PROFInet DeviceThe PROFInet device may be one of the following SIMATIC devices:

• S7-300 CPU with a PROFInet-compliant communication processor (PROFInet CP),such as the CP 343-1 PN.

The PROFInet device of an S7-300 central processing unit does not have proxyfunctionality, but it can run a local PROFIBUS as the master or a local MPI bus.

• Windows logic controller WinLC PN

The WinLC PN is a PROFInet device with proxy functionality. Local DP slavesand/or a local HMI device may be connected to the PROFIBUS.

• Network transition IE/PB Link

The IE/PB Link is a PROFInet device with proxy functionality, but no local DPslaves may be connected.



Locally connected devices of a PROFInet deviceThe locally connected devices of a PROFInet device cannot be seen in SIMATIC iMapand are not involved in the PROFInet communication.

The following devices may be connected to the local PROFIBUS:

• Intelligent DP slaves

• DP standard slaves

• DP-S7 slaves

• DP-ASI links

• DP-PA links

• An HMI device

The intelligent DP slaves on the local PROFIBUS can, in turn, each run a localPROFIBUS as a master. Only the following devices may be connected to this localPROFIBUS, however:


• DP-S7 slaves

• DP-ASI links

• DP-PA links

NoteDuring a program download to the PROFInet device, the programs of theassociated local intelligent DP slave are automatically downloaded, as well.

Only one HMI device may be connected to the local MPI bus of a PROFInet device.Downloading to a local HMI device is only possible using ProTool/Pro CS.

Connecting S7 slaves

NoteNot every DP master can run S7 slaves. This information can be found in therelevant manuals.



Example: Maximum configuration for a PROFInet device

Figure 7-1 Maximum configuration for a PROFInet device with a local PROFIBUS

PROFIBUS deviceA PROFIBUS device has just one PROFIBUS connector and is always a slave. It doesnot participate directly in PROFInet communication and is integrated via a PROFInetdevice with proxy functionality.

PROFIBUS devices are subdivided into:

• PROFIBUS devices with programmable functionality running their own S7programs, i.e. "intelligent" DP slaves (I slaves).

• PROFIBUS devices with fixed functionality - DP standard slaves or S7 slaveswithout their own program.



Possible configuration for a PROFIBUS device• A PROFIBUS device with programmable functionality may be one of the

following SIMATIC devices:

– ET 200X with BM 147/CPU

– ET 200S with IM 151CPU

– CPU 31x-2DP, CPU 318-2 or CPU 31xC-2DP as an intelligent DP slave

– Complete C7 6xy DP devices as intelligent DP slaves

A PROFIBUS device with programmable functionality always has an integralPROFIBUS interface that is used to couple it to the PROFIBUS master withproxy functionality in SIMATIC iMap.

• A PROFIBUS device with fixed functionality may be one of the following devices:

– DP standard slave

– DP-S7 slave

– DP-ASI link

Locally connected devices of a PROFIBUS deviceCentral processing units as intelligent DP slaves may have up to one further interface:

• to a local PROFIBUS or

• to a local MPI bus.

The locally connected devices of a PROFInet device cannot be seen in SIMATIC iMap.

Only the following devices may be connected to the local PROFIBUS:


• DP-S7 slaves

• DP-ASI links

• DP-PA links

• An HMI device

Only one HMI device may be connected to the local MPI bus of a PROFIBUS device.



Examples: Configurations of PROFIBUS devices

Figure 7-2 Maximum configuration for an intelligent PROFIBUS device with local PROFIBUS

Figure 7-3 PROFIBUS devices with fixed functionality, hardware configurations



Rule: No more than 2 network interfaces per deviceThe CPU in the station of the PROFInet component may have up to 2 networkinterfaces, only one of which is the DP master. The following combinations arepossible:

• For PROFInet devices - always one Ethernet connector and

– one PROFIBUS connector as the master with proxy functionality (optionally withlocal DP slaves on this DP master system)

– one local PROFIBUS connector as the master

– one local MPI connector

• For PROFIBUS devices - always one PROFIBUS connector as the slave and

– one local PROFIBUS connector as the master

– one local MPI connector

Illegal configurationsThe following configurations are not permitted in PROFInet components:

• Intelligent DP slaves with local PROFIBUS with further intelligent DP slavesconnected.

• Intelligent DP slaves on the local PROFIBUS via PROFIBUS-CP

If the local PROFIBUS of a CPU is structured via a PROFIBUS CP (e.g. CP 342-5),no local intelligent DP slaves may be connected to it.

• Combination of several stations or DP slaves without a DP master system for aPROFInet component

• Configuration of more than one DP master system within a station

• C7 with an integral HMI device on the MPI bus as a local intelligent DP slave of aPROFInet device.

• More than one integral HMI device.



7.1.3 Central Processing Units

Configuration optionsA CPU from the SIMATIC S7-300 product family always creates a PROFInetcomponent with programmable functionality. CPUs may be used as:

• PROFInet devices (with an Ethernet connector)

• Intelligent PROFIBUS devices (with a PROFIBUS connector as a DP slave)

The station forms a unit with a defined function, such as a machining station orcoordinator. The PROFInet component generally consists of a technological functionand the associated device.

A local (internal) connector is possible:

• a local PROFIBUS for connecting local DP slaves, e.g. via the integral DP interfaceon the CPU 31x-2DP or

• a local MPI connector for an HMI device

The locally connected devices, such as DP slaves or an HMI device, cannot be seenon the PROFInet component in SIMATIC iMap.

7.1.3.1 Network Configurations for CPUsThe possible network configurations for different CPU types are described below.

CPU 31x, CPU 31xC and CPU31x-2PtPThe components of a PROFInet device may be created from a SIMATC-300 stationwith a CPU 31x or CPU 31xC and the CP 343-1 PN.

Internal networking:

• Either a local PROFIBUS with the CP 342-5DP or

• a local MPI bus for connecting an HMI device only.

Configuration as a PROFIBUS device (intelligent DP slave) is not possible.



CPU 31x-2DP and CPU 31x-2DPPROFInet components of the following device types may be created from a SIMATC-300 station with a CPU 31x-2DP or CPU 31xC-2DP:

• PROFInet device - the CP 343-1 PN must be suitably configured.


– Either a local PROFIBUS if the "DP master" operating mode is configured for theintegral network interface X2, or

– a local MPI bus for connecting an HMI device only.

• PROFIBUS device (intelligent DP slave), the "DP slave" operating mode isconfigured for the integral network interface X2.


– Either a local PROFIBUS with the CP 342-5DP or

– a local MPI bus for connecting an HMI device only.

CPU 318-2PROFInet components of the following device types may be created from a SIMATIC-300 station with a CPU 318-2:

• CPU 318-2 as a PROFInet device - the CP 343-1 PN must be suitably configured.


– A local PROFIBUS is possible if the "DP master" operating mode is configuredfor the integral network interface X2. The integral network interface X1 may notthen be networked.

– The integral network interface X1 may also be programmed for MPI in order toconfigure an HMI device as part of the PROFInet component. The integralnetwork interface X2 may not then be networked.

• CPU 318-2 as a PROFIBUS device

PROFIBUS device (intelligent DP slave), the "DP slave" operating mode isconfigured for the integral network interface X2. (The network interface X1 as a "DPslave" is not permitted).


– A local PROFIBUS may be configured via the integral network interface X1. APROFIBUS interface via a PROFIBUS-CP (e.g. CP 342-5DP) is not permitted.

– A local MPI bus may be configured via the integral network interface X1. Thiscan then be used to connect a local HMI device.



Complete C7-6xy or C7-6xy DP devicePROFInet components of the following device types may be created from a SIMATC-300 station with a complete C7-6xy or C7-6xy DP device:

• PROFInet device - the CP 343-1 PN must be suitably configured.

• PROFIBUS device (intelligent DP slave) from the C7-6xy DP only, provided that the"DP slave" operating mode is configured for the integral network interface X2.


• An HMI device may be configured as part of the PROFInet component via MPI.

• A local PROFIBUS CANNOT be configured.

7.1.3.2 Central Processing Units as PROFInet Devices

The CPU must be combined with a PROFInet-compliant communication processor(PROFInet CP), such as the CP 343-1 PN.

Optionally, the SIMATIC 300 station may contain the associated central and distributedperipherals, i.e. all the configurable modules.

Configuration optionsPROFInet components with an Ethernet connector may be created from the followingS7-300 CPUs:

• CPU 31x

• CPU 31x IFM

• CPU 31x-2DP

• CPU 318-2

• CPU 614

• CPU 31x-C and CPU 31xC-2DP

• Complete C7-6xy or C7-6xy DP device



If a PROFInet CP is used...please note the following points:

• Hardware configuration: Only one PROFInet CP may be configured in the centralrack in a Simatic 300 station.

• Configuration: When you configure the Ethernet port, you must:

– select the "IP address is used" option

– deselect the "Set MAC address / Use ISO protocol" option.

• S7 program: Function block PN_InOut (FB88) must be called in the program on theCPU. This function block transfers the data from the interface DB to the PROFInetCP and from the PROFInet CP to the interface DB.

Examples: Central processing units as PROFInet devices

Table 7-4 Configurations: Central processing units as PROFInet devices

Hardware configuration Technological function Device

CPU 316-2 DP with CP 343-1 PN

CPU 316-2 DP with CP 343-1 PN andwith local DP master system



7.1.3.3 Central Processing Units as PROFIBUS Devices

Configuration optionsPROFInet components with a PROFIBUS connector as the DP slave may be createdfrom the following S7-300 CPUs:

• CPU 31x-2DP and

• CPU 31xC-2DP

• CPU 318-2

• C7-6xy DP

Optionally, the SIMATIC 300 station may contain the associated central and distributedperipherals, i.e. all the configurable modules.

These modules all have at least one integral network connector that must beconfigured as a DP slave.

A local DP master system may also be configured as follows:

• For the CPU 318-2P, via the integral network connector X1. Network connector X2must be configured as a DP slave. A PROFIBUS CP may not be used as a DPmaster.

• For a CPU 315-2DP, CPU 316-2DP and CPU 31xC-2DP via CP 342-5 in thecentral rack.



Examples: Central processing units as PROFIBUS devices

Table 7-5 Configurations Central processing units as PROFIBUS devices


CPU 315-2DP

CPU 315-2 DP with Local DPMaster System



Special featuresThe CP 342-5 is not permitted in the expansion rack.

No intelligent DP slaves may be configured in the local DP master system.

When you configure a CPU 31x-2DP as an intelligent slave, you must set "DP slave"mode in the DP interface properties in HW Config and select the "Programming, ...possible" option (see diagram).

Figure 7-4 Configuring a CPU 31x-2DP as an intelligent slave



7.1.4 WinLC PN

IntroductionThe WinLC PN (Windows Logic Controller with PROFInet functionality) is a PROFInet-compliant device, and always forms a PROFInet component with programmablefunctionality.

Possible configurationsYou can create a PROFInet component from a SIMATIC PC station that contains thefollowing hardware:

• A WinLC PN

• Local distributed peripherals, e.g. via CP 5613 or CP 5611 (up to 32 DP slaves).

• A local HMI device

The local DP slaves and the local HMI device, cannot be seen on the PROFInetcomponent in SIMATIC iMap.

The station forms a unit that performs a defined function, generally a central controlfunction.

PROFInet FunctionalityThe WinLC PN is a PROFInet device with proxy functionality. The WinLC PN providesan interconnectable interface for other PROFInet components.

Bus PortsA PROFInet component created from a WinLC PN with the above setup has two busports:

• For an Industrial Ethernet and

• For Profibus DP acting as a DP master via a CP 5613 or CP 5611



Blocks requiredThe S7 program on the WinLC PN must contain the following organizational blocks inorder to be able to respond to events:

• Diagnostic alarm OB (OB 82) – e.g. if a DP slave is switched to STOP or RUN

• Program sequence error OB (OB 85) - for errors that occur when updating theprocess image when a DP slave fails

• Rack failure OB (OB 86) - when the connector to a DP slave is interrupted

If these blocks are not present, the WinLC PN switches to STOP when an error occursand can no longer provide its proxy functionality for the interconnected PROFIBUSdevices. If the error OBs are present (even with no content), the WinLC PN continuesto run in the event of an error. If necessary, a suitable response to the error must beprogrammed in each error OB.

Sample Plant Configuration with WinLC PN

Figure 7-5 Sample Plant with WinLC PN



Examples of PROFInet components

Table 7-6 Possible configurations with the WinLC PN


WinLC PN without distributedperipherals

WinLC PN With a Local DP MasterSystem



7.1.5 Distributed Peripherals

Distributed peripherals as PROFIBUS devicesDepending on the structure of the S7 program, we differentiate between:

• PROFIBUS devices with programmable functionality - intelligent DP slaves (I-slaves) with a CPU running a separate S7 program, such as the IM 151/CPU for ET200S or BM 147/CPU for ET 200X. This type of device also includes CPUs that canbe configured as DP slaves, e.g. CPU 315-2DP (see also the chapter entitled"Central Processing Units"). The program for such a device may be downloadedfrom SIMATIC iMap.

• PROFIBUS devices with fixed functionality - DP standard slaves or S7 slaveswithout their own program.

The representation in the SIMATIC iMap network view is the same for both types ofdevice - they are shown as PROFIBUS devices with a PROFIBUS connector andacting as a DP slave. The plant view shows the technological function of the PROFInetcomponent.

Intelligent DP slaves as PROFInet componentsYou can create PROFInet components from the following programmable distributedperipheral devices:

• ET 200X with BM 147/CPU

• ET 200S with IM 151/CPU

• CPU 31x-2DP, C7 6xy DP, CPU 31xC-2DP (see also the section entitled "CentralProcessing Units").

The SIMATIC 300 station may also contain all the configurable modules.

Special Features of Intelligent DP SlavesFor an intelligent DP slave, the DP master accesses a transfer area in the addressspace of the CPU, rather than directly accessing the connected inputs/outputs of theintelligent DP slave. Special blocks are required in the user program for this purpose(see "Special Features of DP Slaves").

NoteDirect exchange of data (cross-traffic) between PROFIBUS devices is notsupported.



Example: PROFIBUS device with programmable functionality

Table 7-7 PROFInet components from an ET 200S with IM 151 CPU

Configuration Technological function Device

DP Slaves with Fixed Functionality as PROFInet ComponentsA DP slave with fixed functionality, such as a compact (ET 200B) or modular (ET200M) distributed peripheral device, must be configured in the station of the STEP 7basic project on any DP master in order to create a PROFInet component from it. Inthis case, the DP master is not part of the PROFInet component.

Devices supportedYou can create PROFInet components with fixed functionality from the followingdevices:

• all SIMATIC distributed peripherals: ET 200B, ET 200C, etc, with all modules thatcan be configured

• all standard slaves that are described by a GSD file



Special features of DP slaves with fixed functionalityThe PROFInet component of a compact or modular DP slave has fixed functionality,i.e. there is no separate S7 program running on the device. The interface for thetechnological function is defined and set on the device. The names of the inputs andoutputs of this interface are defined in the interface DB located in the station's blockfolder. The DP master accesses the distributed inputs/outputs of the DP slave directly,so the interface DB is an image of the process inputs and outputs (see "SpecialFeatures of DP Slaves").

The hardware configurations of standard and S7 slaves with fixed functionality thatcontain programmable modules such as FMs and CPs cannot be used to createPROFInet components.

The ET 200L-SC must be configured using GSD files before a PROFInet componentcan be created from it.

NoteDirect exchange of data (cross-traffic) between PROFIBUS devices is notsupported.

Example

Table 7-8 PROFInet components from an ET 200 M




7.1.6 DP/DP Coupler

Using the DP/DP Coupler in SIMATIC iMapThe DP/DP coupler is used to exchange data between two PROFIBUS-DP masters,one of which may be a non PROFInet-compliant device, e.g. an IM308-C or aCPU 4xx.

It is thus possible to integrate PROFIBUS networks into SIMATIC iMap projects, evenwithout PROFInet-compliant devices. Such networks cannot be shown inSIMATIC iMap, however.

ConfigurationIn STEP 7, the DP/DP coupler is configured as a modular slave in both PROFIBUSnetworks using a GSD file. The desired length of the input and output data is set duringconfiguration. The output data from one of the slaves is used as the input data for theother slave, and vice versa,

Example:PROFIBUS network with a PROFInet-compliant master: 2-byte inputs, 4-byte outputsPROFIBUS network without a PROFInet-compliant master: 4-byte inputs, 2-byteoutputs



NoteWhen you configure the DP/DP coupler for the PROFInet-compliant master, makesure that the option "Extended diagnostics enabled" is set in the Properties dialog(see diagram). This means that the diagnostics in SIMATIC iMap can identifywhether the master on the other network is available.

AddressingThe DP/DP coupler may have different addresses in the two PROFIBUS networks.

The addressing must be carried out both on the device and in SIMATIC iMap.

NoteOnly use addresses 1 to 124. No other addresses are permitted on PROFIBUS-DP. Changed addresses do not take effect until you switch the power off and onagain.



Creating the PROFInet component with STEP 7The user creates the PROFInet component for the DP/DP coupler in STEP 7 andstores it in the file system in the same way as for a DP slave with fixed functionality.The procedure is described in the section entitled "Creating PROFInet Componentswith STEP 7".

Figure 7-6 Example: Interface DB for a DP/DP coupler

Working with the PROFInet component in SIMATIC iMap• Import the PROFInet component for the DP/DP coupler from the file system to a

SIMATIC iMap library.

• In the network view, link the PROFInet component for the DP/DP coupler to thedesired PROFIBUS.

• In the Properties dialog box for the DP/DP coupler in the network view, enter thePROFIBUS address set using DIL switches on the device.Note down as a comment which PROFIBUS networks are linked by the DP/DPcoupler.

• Interconnect the inputs and outputs in the plant view.

• Generate the project, then download the programs to the associated DP masterwith proxy functionality.Download the interconnections to the DP/DP coupler.



Representation in SIMATIC iMapThe DP/DP coupler is a PROFIBUS device and is represented accordingly in theSIMATIC iMap plant and network views.

No connection can be seen between the two PROFIBUS networks linked in this way.

Table 7-9 PROFInet component of the DP/DP coupler

Technological function PROFIBUS device

Function in the PROFInet environmentThe DP/DP coupler acts as a DP slave at the PROFIBUS interface.

PROFIBUS device: The PROFInet component of the DP/DP coupler has aPROFIBUS connector.

Technological function: The input and output signals of the DP/DP coupler may berepresented as a technological function via the interface DB.

DiagnosticsThe DP/DP coupler has two diagnostics options:

• The "Diagnostic" DIL switch on the top of the DP/DP coupler can be used to showthe validity of data within the I/O data by setting the DIL switch to "1".

The least significant bit of the first configured input byte (LSB) indicates whetherdata is being exchanged between the two PROFIBUS masters without faults.If the value of the bit it "1", all the DP/DP coupler data is valid.If the bit is set to "0", all the data is invalid.

• HW Config may be used to activated "extended diagnostics". To do this set thevalue to "Extended diagnostics enabled" during configuration in STEP 7.

If the DP/DP coupler signals a diagnostic event, OB82 is called in the master andan entry is made in the diagnostic buffer.

In SIMATIC iMap, diagnostics can be carried out via online monitoring or via themodule state.



Further informationThe structure, configuration, commissioning and diagnosis of the DP/DP coupler aredescribed in detail in the DP/DP coupler manual.

The manual and further information can be obtained from:

http://www.ad.siemens.de/support

7.1.7 HMI Devices in PROFInet Components

Options for using HMI devices in PROFInet componentsHMI device can be incorporated into the PROFInet communication in two ways:

• HMI device as an off-the-shelf PROFInet component

In the SIMATIC iMap install directory

\IMAP\COMPONENTS

there are a number of off-the-shelf PROFInet components for HMI device. Thesecan be imported into a SIMATIC iMap library and inserted into a project (e.g.PC670TOUCH_12''-{...}-0.0.0.1).

• HMI device integrated into a PROFInet component

When you create a PROFInet component, you can configure an HMI device as partof the component.

This section describes the points you should note.

Network configurations with integral HMI devicesYou can integrate an HMI device into a PROFInet component by incorporating it intothe internal networking of the station. The options are as follows:

• either on the local PROFIBUS

• or on the local MPI bus

• or within a PC station

The local bus systems of the PROFInet component, and the devices that they network,cannot be seen in SIMATIC iMap. Consequently, an integral HMI device is not alsodisplayed as such in SIMATIC iMap.



Rules for integrating HMI devices• A PROFInet component may only have one HMI device. Several HMI devices in a

PROFInet component are not supported.

• The station of a PROFInet component may not contain two local bus systems(PROFIBUS and MPI). If a local PROFIBUS is configured, an HMI device may notbe configured via MPI and vice versa.

• For a complete C7 6xy device, the HMI device may only be integrated via MPI. Itcannot be configured on the PROFIBUS.

Example: Integral HMI device on the local PROFIBUS of a PROFInet device

Figure 7-7 HMI device on the local PROFIBUS of a PROFInet device



Example: Integral HMI device on the local MPI bus of a PROFInet device

Figure 7-8 HMI device on the local MPI bus of a PROFInet device

Example: Integral HMI device on the local PROFIBUS of a PROFIBUS device

Figure 7-9 HMI device on the local PROFIBUS of a PROFIBUS device



Example: Integral HMI device on the local MPI bus of a PROFIBUS device

Figure 7-10 HMI device on the local MPI bus of a PROFIBUS device

Processing in SIMATIC iMapAn integral HMI device as part of a PROFInet component cannot be seen inSIMATIC iMap. The device must be configured and the program downloaded to thedevice using ProTool/Pro CS.

RequirementA connection between the PC and the HMI device is required in order to download tothe HMI device. Set the access point of the S7ONLINE (STEP7) application to one ofthe following interface parameter settings in the PG/PC interface:

• MPI

• PROFIBUS

• Point-to-point connection.



Configuration and downloadingThe following steps are required:

1. Generate the project in SIMATIC iMap using the Generate > menu command sothat the generation status of the device is "Created".

2. Select the device from the network view and select Special > HMI from the contextmenu. This calls the associated project in ProTool/Pro CS for the HMI device.

3. In ProTool/Pro CS: Change the configuration, if necessary, and download the datato the HMI device.



7.2 Creating PROFInet Components with STEP 7

7.2.1 Basic procedure

Basic procedureFollow the steps described below to create PROFInet components using STEP 7:



7.2.2 Create a Project in STEP 7

RuleA PROFInet component can be created from the station of a STEP 7 project asfollows:

• from the entire station (CPU, intelligent DP slave) or

• from one of the DP slaves with fixed functionality.

Please note the options for configuring SIMATIC devices as PROFInet components inthe chapter of the same name.

Procedure1. Create the STEP 7 basic project in SIMATIC Manager. Then create the PROFInet

component from the station of the project.

2. Configure the hardware and modules in HWConfig.

3. Copy the blocks from the PROFInet system library to the block folder of the S7program. (Note the special features of DP slaves with fixed functionality andintelligent DP slaves).

4. Convert the external inputs and outputs of the future PROFInet component intodeclarations for the interface DB using the interface DB block templates from thesystem library, and adapt them to the component interface of the PROFInetcomponent to be created.

5. Create the program for your station.



7.2.3 Properties of the Interface DB

IntroductionThe future PROFInet component has an interface that you can use to communicatewith other PROFInet components. There must be a description of this interface in theSTEP 7 basic project when the PROFInet component is created. In the STEP 7 basicproject, the interface description is stored in a data block - the interface DB. Exactlyone interface DB is assigned to a PROFInet component. When you create thePROFInet component, STEP 7 determines the structure of the interface, i.e. thenumber and properties of the I/Os, from this interface DB.

For PROFInet components with programmable functionality, the interface DB is usedat runtime as a storage location for data that is sent via the interface of the PROFInetcomponent. Other STEP 7 blocks can then access this data directly via the interfaceDB.

For PROFInet components 'with fixed functionality', the interface DB is used solely todescribe the interface.

DefinitionThe interface DB is a global DB or instance DB that contains the interface definition ofthe PROFInet component. A declaration line in the interface DB may contain thedefinition of a connector or act as a separating or filler element for special components.

Declaration LinesYou must include a declaration line with the following content in the interface DB foreach connector:

Column Content

Address Displays the address in the data block that STEP 7automatically assigns to the connector's variables.

Declaration(for instance DBs only)

Defines how the connector variables are declared:Input (in)Output (out)The other types of declaration do not relate to the interface DB.

Name Name of the connector

Type Data type of the connectorComment Description of the connector



The declaration lines for the inputs form the input section, while the declaration linesfor the outputs are the output section of the interface DB.

NoteThe initial values of the variables are only used as starting values at runtime forPROFInet devices. For PROFIBUS devices, the initial values are ignored.

Name and number of connectorsA connector name must not exceed 24 alphanumeric characters.

Lifestate outputA lifestate output that is used to monitor the state of the device by means of thecommunication partners is automatically added to every PROFInet component createdwith STEP7 Add-on, even though this output is not explicitly declared in the interfaceDB. Information on the lifestate output can be found under "Properties of the PROFInetcomponents of SIMATIC devices".

Data typesThe declaration lines of the interface DB can be configured with the following S7 datatypes the conform to the PROFInet data types defined in Microsoft OLE 2.0 (see"Properties of PROFInet Components of SIMATIC Devices, Data Types".

Data lengths of declared connectorsThere is no limit on the data length for interface DBs for devices with Ethernetconnectors. With interface DBs for DP slaves, the data length per connector and thetotal data length of all connectors are limited (see "Special Features of DP Slaves").

Number of connectorsThe input section of an interface DB may have up to 300 interconnectable inputs, andthe output section up to 300 interconnectable outputs (including the lifestate output).There is no limit to the number of non-connectable connectors.



Attribute of the interface DBThe interface DB must have the following attribute to indicate that it is an interfacedescription for a PROFInet component:

Attribute Value

CBA_db true

Attributes of the declaration linesThe declaration lines of the data block must have certain attributes to ensure that theyare correctly converted into the connectors of the component. The following attributescan be applied to the interface description of the PROFInet component:

Attribute Possible values Meaning Note

CBA_direction in Connector type: input Forced at the start of the inputsection

out Connector type: output Forced at the start of the outputsection

CBA_transfer_type connectable Connectableconnector

Automatically set at the start ofthe input and output sections.

connectable_off Marks the limit for non-connectableconnectors

For OPC via the PROFInetprotocol only (e.g. WinLC PN)

s7extended Non-connectableconnector

For OPC via S7 protocols (e.g.intelligent DP slaves)

s7extended_off End of the non-connectableconnectors

For OPC via S7 protocols (e.g.intelligent DP slaves)

CBA_pad_item true Separating elementbetween the input andoutput area

Only for devices that require theaddresses to be explicitlyaligned at the ends of words.

CBA_unused true Filler element for anempty slot

Relates to DP slaves with fixedfunctionality, for example

NoteRemember that the attributes are case sensitive.



NoteThe attributes CBA_direction and CBA_pad_item only have to be set in globaldata blocks. This is not necessary for an instance data block since the input andoutput areas are already identified in the variable declaration table for theassociated function block.

Attributes are assigned as follows in the data block declaration lines:

• For a global DB– when editing the data block

• For an instance DB – when editing the variable declaration table for the associatedcode block (FB).

The attributes CBA_direction and CBA_transfer_type, which are entered for adeclaration line, are adopted for all subsequent declaration lines until the next attributeis entered.

The attributes CBA_pad_item and CBA_unused only apply to the current declarationline.

Connectable and non-connectable connectorsUse the CBA_transfer_type attribute to define whether a connector isinterconnectable or non-connectable.

• Connectable connectors relate to process values that are part of the componentinterface and can be transferred during PROFInet communication.

All connectable connectors in the technological function must have the attributeCBA_transfer_type = connectable. The interconnectable connectors appear in theplant view and can be accessed via OPC (OLE for Process Control).

• Non-connectable connectors relate to data that is not part of the componentinterface, and is only contained in the OPC symbol file. Such connectors do notappear in the plant view, and the data can only be accessed via OPC. It may beused for operator control and process monitoring, commissioning or diagnostics, forexample.

Depending on which protocols are supported for OPC, we differentiate between:

– Devices that support OPC via PROFInet protocols, such as WinLC PN.

The start of non-connectable connectors is identified by the attribute

CBA_transfer_type=connectable_off.

– Devices that support both PROFInet and S7 protocols for OPC, such asintelligent DP slaves.

The start of non-connectable connectors is identified by the attribute

CBA_transfer_type=s7extended.



Default setting for the CBA_transfer_type attributeThe default setting for the first declaration line in the input and output sections of theinterface DB has the attribute CBA_transfer_type with the value connectable.

Variable Sub-BlocksVariable sub-blocks can be created by assigning the CBA_transfer_type attribute.

• Variables for interconnectable connectors (CBA_transfer_type attribute with thevalue connectable)

A sub-block starts with the attribute "CBA_transfer_type = connectable" and endswith the attribute " CBA_transfer_type = connectable_off" (first variable no longerconsidered).

• Variables for non-connectable connectors (attribute CBA_transfer_type with thevalue s7extended), for intelligent DP slaves only

A sub-block starts with the attribute "CBA_transfer_type = s7extended" and endswith the attribute " CBA_transfer_type = s7extended_off" (first variable no longerconsidered).

Separator elements– for global data blocks onlyFor interface DBs from global data blocks, the input and output sections must bealigned at the ends of words so an additional declaration line is generally added as aseparator element between the input section and the output section. The declarationline of the separator element must have the attribute CBA_pad_item and the valuetrue.

The only exception is the WinLC PN which does not require a separator element.

The data type of the separator element must ensure alignment at the ends of words,e.g. WORD or BYTE.

Filler elementFiller elements are used to "hide" unused data in the interface DB. They do not defineconnectors. The declaration line of a filler element must have the attributeCBA_unused and the value true.

They are used, in particular, for DP slaves with fixed functionality in order to identifyunused I/O sections of the DP interface within the interface DB (see "Structure of theinterface DB for DP slaves with fixed functionality").



Rules for the order of connectorsThe connector entries in the interface DB must keep to a set order:

• The declaration lines for inputs come before the output declaration lines.

• The declaration lines for connectable connectors come before the declaration linesfor non-connectable connectors (for intelligent DP slaves only).

Structure of the interface DB for PROFInet component with an Ethernet connectorThe interface DB of a PROFInet component with a connector to an Industrial Ethernet,e.g. a SIMATIC 300 station with a CPU 318-2 with CP 343-1 PN, generally has thefollowing structure:

1. Inputs

2. A declaration line of the data type WORD as a separator element with the attributeCBA_pad_item = true

3. Outputs

Example

Figure 7-11 Example: Interface DB for the PROFInet component of a PROFInet device



Entries must have the following attributes (for global data blocks only - not for instancedata blocks):

Declaration line Attribute Value

First input CBA_direction inFirst non-connectable input(optional)

CBA_transfer_type connectable_off

Separator element betweeninputs and outputs

CBA_pad_item true

First output CBA_direction outFirst non-connectable output(optional)

CBA_transfer_type connectable_off

Structure of the Interface DB for Intelligent DP SlavesThe interface DB of an intelligent DP slave generally has the following structure:

1. Connectable inputs,

2. Non-connectable inputs,

3. A declaration line of the data type WORD as a separator element with the attributeCBA_pad_item = true.

4. Connectable outputs,

5. Non-connectable outputs

NoteIndividual sections may be omitted.



Example

Figure 7-12 Example: Interface DB for the PROFInet component of a programmable PROFIBUSdevice

Entries must have the following attributes:Declaration line To be specified

for ...Attribute Value

First input Global DB CBA_direction inFirst non-connectable input(optional)

Global DB andinstance DB

CBA_transfer_type s7extended

Separator element betweeninputs and outputs*

Global DB CBA_pad_item true

First output Global DB CBA_direction out

First non-connectable output(optional)

Global DB andinstance DB

CBA_transfer_type s7extended

* Only required if the first output does not start at the limit of a double word.



Structure of the Interface DB for DP Slaves with Fixed FunctionalityThe interface DB of a PROFInet component created from a DP slave with fixedfunctionality generally has the following structure:

1. Inputs

2. A declaration line of the data type WORD as a separator element with the attributeCBA_pad_item = true.

3. Outputs

4. Declaration lines as filler elements, if required.

DP slaves with fixed functionality do not have their own user program, so the interfaceDB can only be a global data block.

Example

Figure 7-13 Example: Interface DB for the PROFInet component of a PROFIBUS device withfixed functionality



Entries must have the following attributes:

Declaration line Attribute Value

First input CBA_direction inSeparator element betweeninputs and outputs*

CBA_pad_item true

First output CBA_direction outFor filler elements CBA_unused true

* Only required if the first output does not start at the limit of a double word.

7.2.4 Special Features of DP Slaves

Exchange of data between the DP master and intelligent DP slavesTo allow data to be exchanged between the DP master and an intelligent DP slave, theinput and output data for the PROFInet component, i.e. the data from the interface DB,have to be transferred from the transfer area and to the transfer area of the intelligentDP slave (using the PN_IN and PN_OUT functions) when the user program runs.

Figure 7-14 Exchange of data between the interface DB and the I/O areaof the intelligent DP slave



Blocks required in the S7 program of an intelligent DP slaveThe following blocks are supplied in the PROFInet system library:

Block Description

FC10 PNPN_IN - Copies the data from the transfer area of the DP master withproxy functionality to the input of the interface DBAttribute: CBA_islave_copy_fc and value: inThe block PN_IN (FC10) must be called right at the start of OB1 to ensurethat it is the current data that is transferred to the interface DB.

FC11 PN_OUT – Copies the outputs of the interface DB to the transfer area of theDP master with proxy functionality.Attribute: CBA_islave_copy_fc and value: outThe block PN_OUT (FC11) must be called right at the end of OB1 to ensurethat the data in the transfer area is not overwritten.

DB2 Data block with the attribute: CBA_islave_copy_db and value: true The DBcontains data for the PN_IN and PN_OUT functions and must not bemodified.

DB100 Global data block PN_Interface_DB as a template for the interface DB.Attribute: CBA_db and value: true

The numbers of these blocks can be modified as required.

You can use global data block DB100 as a template for creating the interface DB. Thisglobal DB must be adapted to suit the technological function (inputs and outputs) andsupplied from the user program.

Organizational Blocks RequiredThe S7 program of an intelligent DP slave must contain the following organizationalblocks in order to be able to respond to events:

• Diagnostic alarm OB (OB 82) – e.g. if the DP master is switched to STOP or RUN

• Rack failure OB (OB 86) - e.g. when the connection to the DP master is interrupted



Data Lengths of Intelligent DP SlavesData length per connector

The maximum data length per connector is 32 bytes to ensure consistent transmissionof data. For a connector of the data type STRING, the maximum length of the workingdata is just 30 bytes (corresponding to 30 characters, i.e. STRING[30]).

Data lengths of all connectors

The maximum permitted total data length depends on:

• The properties of the device (Profibus interface, max. length of the I/O areas)

• The way the device is configured.

You can find further information in the documentation for individual devices.

Device Total length of allinputs in bytes

Total length of alloutputs in bytes

S7-300 CPU as an intelligent slave Max. 244 Max. 244CPU 31x-C as an intelligent slave Max. 244 Max. 244ET 200S, IM 151 /CPU Max. 244 Max. 244ET 200X , BM 147 /CPU Max. 32 Max. 32



Special features of DP slaves with fixed functionalityDP slaves with fixed functionality do not have their own user program. For thePROFInet component, you must create an interface DB for the DP slave and save it tothe block folder of the S7 program assigned to the DP master station. If a station hasseveral DP slaves, then there may be several interface DBs in the block folder and aninterface DB for each DP slave from which a PROFInet component is to be created.

The following applies to the structure of the interface DB:

• The input section of the interface DB forms the output signals from the DP interfaceof the DP master at the inputs of the technological function.

• The output section of the interface DB forms the input signals to the DP interface ofthe DP master at the outputs of the technological function.

Figure 7-15 Structure of the interface DB for DP slaves with fixed functionality

A global data block as the template for the interface DB of a DP slave with fixedfunctionality is supplied in the system (PROFInet) library.

Data length of a connectorFor DP slaves with fixed functionality, the maximum data length corresponds exactly tothe consistent length of the signal input/output area.

The data length of a connector cannot be longer than the slot for which it is defined.



Consistency of the transferred dataWhen you create the interface DB for a DP slave, you must make sure for eachconnector that the data length of the connector does not exceed the configured lengthof the consistently transferred data.

Consistent means that the data belongs together and must not be separated. If thelength of a connector exceeds the configured or maximum permitted consistent length,it is possible for data that belongs together to be transferred separately.

CautionIf the data cannot always be transferred consistently, the created PROFInetcomponent may not be able to run on the PROFIBUS.

Consistent length

The length of the consistently transferred data is displayed under the properties of themodule concerned in HW Config. If no consistent length is displayed, the following rulegenerally applies:

• The maximum consistent length is 32 bytes.

• Unless otherwise specified, the consistent length:

– of a digital input or output is 1 byte (8 bits)

– of an analog input or output is 1 word (16 bits)

This may be different for some modules. Detailed information can be found in thetechnical data for the module concerned.

Examples:

• For an ET200eco, 8DI/8DO DP the consistent length is 1 byte per input or output.

• For an ET200M with an AI2x12Bit analog module, the consistent length is 1 wordper input or output.

Filler elementUnused areas of a slot must be identified by a filler element (user-defined attributeCBA_unused with the value true) according to their length (BOOL, BYTE, WORD,etc).



7.2.5 Creating the Interface DB

How many interface DBs are required?Just one interface DB, i.e. a data block with the attribute CBA_db = true, is needed inorder to create a PROFInet component.

The following applies according to the type of device used:

• Create a basic project with a station for each PROFInet component withprogrammable functionality (PROFInet devices or intelligent PROFIBUS devices (I-slaves)). There must be only one interface DB in the user program block folder.

• For PROFInet components with fixed functionality (PROFIBUS slaves), create abasic project with a SIMATIC 300 station that forms a DP master system for one ormore DP slaves. In this case, the PROFInet component is only created from a DPslave, and the DP master is not part of the component.

There may thus be several interface DBs in the user program block folder for sucha station. In this case, an interface DB can, if necessary, be used for several DPslaves with the same input/output areas, if this is permitted by the hardware setup.

Requirement: Block template from the PROFInet system libraryThe PROFInet system library contains a data block DB100 (PN_Interface_DB) for eachdevice type as a template for creating the interface DB. To use the block templatesfrom the PROFInet system library:

• In SIMATIC Manager select the File > Open menu command from the "Libraries"tab to open the "PROFInet system library".

• In the library, open the block folder corresponding to the device type of thePROFInet component to be created and copy the block template to the block folderof the basic project.

• Adapt the block template to the technological function of the PROFInet component.

NoteYou can rename the blocks that you use as templates in the basic projectprogram as required.

HintCopy all the blocks for the device type concerning (including the OBs) that you willneed to create the PROFInet component.



Creating the interface DB from a global DBThe procedure for creating the interface DB for the future PROFInet component is asfollows:

1. In SIMATIC Manager, open the basic project for the PROFInet component to becreated.

2. Open the global data block DB100 that you have copied from the system library.The DB already has the required attribute CBA_db with the value true. You cancheck this under Object properties, "Attributes" tab.

3. Adapt the DB declarations to the technological function of the PROFInet componentto be created, making sure that there is an entry with the appropriate data type foreach input.

The attributes for the connectors exist already. All you have to do is make sure thatthey are in the correct order.

There must be a separator element between the declaration line of the last inputand the declaration line of the first output. This is a declaration line with the attributeCBA_pad_item and the value true. This declaration line already exists in thetemplate.

Exception: no separator element is required for WinLC PN.

4. For the interface DB of an intelligent DP slave only: If necessary, enter the attributeCBA_transfer_type and the value s7extended for the declaration lines of the non-connectable connectors that are not to appear on the technological function in theplant view.

5. Filler elements for all unassigned addresses of the input/output section must beentered for the interface DB of a DP slave with fixed functionality. These aredeclaration lines with the attribute CBA_unused and the value true.

6. Save the interface DB.

7. For stations with several DP slaves from which individual PROFInet componentsare to be created, create an interface DB for each DP slave. You could also use asingle interface DB for several components with the same interface.



Enter the attributesThe attribute CBA_direction must be set for the first line of the input section andoutput section. In contrast to the normal procedure for data blocks in STEP 7, you donot have to enter attributes for each line of the interface DB.

All you have to do is enter the attribute CBA_direction for the first line of the inputsection and output section. These attributes are then adopted for the subsequent lines.

Figure 7-16 Attribute for inputs

Figure 7-17 Attribute for outputs

You must also enter the attribute CBA_transfer_type with the value s7extended oncefor the declaration line of the first non-connectable input and first non-connectableoutput. These attributes are also adopted for the subsequent lines - until the next timean attribute is changed.

Figure 7-18 Attribute for non-connectable inputs and outputs (OPC via S7 protocol)

Figure 7-19 Attribute for non-connectable inputs and outputs (OPC via PROFInet protocol)

The attributes CBA_pad _item and CBA_unused only apply to the declaration line.They are not adopted for the subsequent declaration lines.

Figure 7-20 Attribute for a separator element



Figure 7-21 Attribute for a filler element

The lines for which attributes are explicitly entered are identified by a flag (seeexamples).

Example 1: Interface DB for a PROFInet device

Figure 7-22 Interface DB for a PROFInet component with an Ethernet connector

Lines Attribute Meaning

1 Attribute for inputsOnly applies to inputs "Input1"to "Input3"

4 Attribute for non-connectableconnectors (OPC via PROFInetprotocol)Only applies to inputs"HMI_Input1" to "HMI_Input2"

6 Attribute for a separatorelementApplies to the "Pad" entry.



Lines Attribute Meaning7 Attribute for outputs

Applies to outputs "Output1" to"Output3"

10 Attribute for non-connectableconnectors (OPC via PROFInetprotocol)Applies to outputs"HMI_Output1" toHMI_Output2"

Example 2: Interface DB for a programmable PROFIBUS device

Figure 7-23 Interface DB of a PROFInet component with a PROFIBUS connector (intelligent DPslave)

Lines Attribute Meaning

1 Attribute for inputsOnly applies to inputs "Input1"to "Input2"

3 Attribute for non-connectableconnectors (OPC via S7protocol)Only applies to inputs"S7Input1" to "S7Input2"

5 Attribute for a separatorelementApplies to the "Pad" entry.



Lines Attribute Meaning6 Attribute for outputs

Applies to outputs "Output1" to"Output2"

8 Attribute for non-connectableconnectors (OPC via S7protocol)Applies to outputs "S7Output1"to "S7Output2"



Example 3: Interface DB for a PROFIBUS device, DP slave with fixed functionalityHardware configuration of a DP slave with an IM 153.

Figure 7-24 DP slave ET 200M with IM 153, hardware configuration



Interface DB of the PROFInet component for IM 153

• the inputs in the interface DB are mapped onto the addresses of the outputs (3bytes) and

• the outputs in the interface DB are mapped onto the addresses of the inputs (4bytes)

Figure 7-25 Interface DB of the PROFInet component for ET 200M with IM 153



The following table shows the assignment between the DP interface of the DP masterand the declarations in the interface DB for IM 153:

I/O address on theDP master

Number of bits Corresponds in theinterface DB to...

Data type

Outputs InputsAB0 8 Input1 BYTEQ1.0 1 Input2 BOOLQ1.1 1 Input3 BOOLQ1.2 1 Input4 BOOLQ1.3 1 Unused1 BOOLQ1.4 1 Unused2 BOOL

Q1.5 1 Input5 BOOLAB 2 8 Unused3 BYTEInputs OutputsEB0 8 Output1 BYTEEB1 8 Output2 BYTEEB2 8 Unused4 BYTEEB3 8 Output3 BYTE

The technological function thus has 5 inputs and 3 outputs.



Creating the Interface DB from an Instance DBThe procedure for creating the interface DB for the future PROFInet component is asfollows:

1. In SIMATIC Manager, open the basic project for the PROFInet component to becreated.

2. Creating a Function Block.

3. Open the properties of the function block. On the "Attributes" tab, set the user-defined attribute CBA_db with the value true.

4. In the FB variable declaration table declare the inputs and outputs of thetechnological function for the PROFInet component to be created. Make sure thatyou have a declaration line with the appropriate data type for every input and outputof the technological function.

5. For the interface DB of an intelligent DP slave only: If necessary, enter the attributeCBA_transfer_type and the value s7extended for the declaration line of the firstnon-connectable input and first non-connectable output. These connectors cannotbe seen in the plant view of the technological function. They can only be accessedvia OPC.

Make sure that they are in the correct order.

In this case, you do not have to set the attributes CBA_direction andCBA_pad_item since the input and output areas are already identified by thedeclaration (in or out) in the FB variable declaration table.

6. Save the function block.

Select the Insert > S7 Block > Data Block menu command to create an instanceDB. In the "Name and Type" box in the Properties dialog, select "Instance DB" andthe function block to be edited as the associated FB. Enter the desired propertiessuch as name, etc., and click on "OK" to confirm your input.

7. Result: The instance DB is created. This contains the declaration lines of theassociated FB. All the user-defined attributes of the FB, plus the declaration lines,are automatically assigned to the instance DB as well.

You cannot edit the block.

You have now created your interface DB.



Example : Interface DB for a PROFInet deviceVariable declaration table for function block FB11 for a PROFInet device,e.g. CPU 315-2DP with CP 343-1 PN.

Figure 7-26 Declarations of the inputs and outputs in the FB of a PROFInet device

The declarations are transferred to instance DB DB11.

Figure 7-27 Instance DB DB11 of FB11



Example : Interface DB for a programmable PROFIBUS deviceVariable declaration table of function block FB12 for a programmable PROFIBUSdevice, e.g. CPU 315-2DP (intelligent DP slave).

Figure 7-28 Declarations of the inputs and outputs in the FB of a PROFIBUS device

The declaration for input S7_IN_1 contains the user-defined attributeCBA_transfer_type with the value true. The same attribute is also assigned to thedeclaration for output S7_OUT_1. The attribute identifies the following inputs oroutputs as non-connectable. No separator element is required.

The declarations, including the attributes, are transferred to instance DB DB12.

Figure 7-29 Instance DB DB12 of FB12



7.2.6 Creating PROFInet Components in SIMATIC Manager

IntroductionIf you wish to create PROFInet components from SIMATIC programmable controllers,you must do this using the STEP 7 SIMATIC Manager.

RequirementThe STEP 7 basic project must be complete, i.e.:

• The S7 program and the interface DB have been created.

• The hardware configuration and parameter settings for the modules are complete.

• The STEP 7 basic project have been tested.

• You have the documentation for the future PROFInet component.

• You have the files with the icons for representing the entire PROFInet component,the technological function and the associated device. If you do not have your ownicon files for the component to be created, you can use the files supplied with thesoftware which are provided as defaults.

ProcedureProceed as follows:

1. In your STEP 7 basic project, select the station from which the component is to becreated.

2. Select the Create PROFInet component menu command. There are two options:

– Edit > Create PROFInet component menu command or

– Context menu (right mouse button) Create PROFInet component.

Result: The "Create PROFInet component" dialog box opens.

3. Enter the properties of the PROFInet component to be created (see below).

4. End your input by clicking on "OK" or "Cancel". If you click on "OK", the PROFInetcomponent is created in STEP 7. If you click on "Cancel", the dialog box closeswithout applying the changes in STEP 7.



"General" tabThis tab is used to define:

• which elements should be used to create the PROFInet component, e.g. the entirestation (a DP master and one or more local DP slaves, if applicable) or an individualDP slave,

• Properties, such as name and version, and identifications of the component.

Figure 7-30 Creating the PROFInet component from a station

Figure 7-31 Creating the PROFInet component from a DP slave



NameThe name must not exceed 16 characters and must start with a letter.

Version numberThe version contains four series of numbers, separated by dots.

Any numbers (up to 3 digits) may be assigned to the first two parts of the versionnumber. The last two parts are automatically incremented.

When you enter a version number, it must always be higher than the previous number.

Identification of the PROFInet componentThe identification of the PROFInet component is a unique identifier conforming to theCOM standard. This comprises the class ID, the interface name and the interface ID. InSIMATIC iMap, PROFInet components are identified by their class ID and versionnumber.

The options are as follows:

• If you select "New", a new identification is automatically generated. You will have toassign a new identification if:

– you are creating the PROFInet component for the first time, or

– you have changed the name of the PROFInet component.

• If you select the "Retain" option, the default identification is retained, and thePROFInet component is only given a new version number.

We recommend that you accept the default values ("Retain" option).

NoteThe interface ID is automatically changed whenever the component interface ischanged.



In the "Storage Areas" tab

Figure 7-32 Storage locations

With this tab, you define whether component created is to be saved to the file systemand/or imported directly into a library.

NoteIf the PROFInet component is to be imported into a library, the library must havebeen created using SIMATIC iMap.



"Additional Properties" tabThis tab is used to define which icons are to be assigned to the technological function,the PROFInet device and the PROFInet component, and the path name or Internetaddress for the PROFInet component documentation.

Figure 7-33 Additional Properties

NoteDocumentation link

If you enter the documentation link as the URL, you must make sure that thedocumentation is actually accessible in the plant.

A documentation link can only reference a single file.

If an HTM file containing cross-references to other files is specified when thePROFInet component is created, only the specified HTM file is copied to thePROFInet component folder - not the referenced files.

Remedy:

We recommend that you use a different format, e.g. PDF or CHM, if you requirecomplex documents.



ResultThe PROFInet component is stored as a directory in the specified storage area in thefile system or directly in the library or both. The directory name contains the names, theidentification (class ID) and the version number of the PROFInet component. Thedirectory contains the following:

• The XML file containing the description of the PROFInet component and, inparticular, the technological function. The system searches for this XML file whenimporting to a library.

• The icon files

• The STEP 7 component project that contains a copy of the station or the DP slavefrom the basic project.

• The file for the documentation link, if a path name in the file system was specifiedas the documentation link.



7.2.7 Importing PROFInet Components to a Library

Basic procedureA PROFInet component must be located in a library before it can be inserted intoSIMATIC iMap. You can insert a PROFInet component into a library in the followingways:

• When you create the PROFInet component in the device-specific programming andconfiguration tool, e.g. SIMATIC Manager

• In SIMATIC iMap, by importing to a library (described in the SIMATIC iMap Helptopics under "Configuring a plant, Importing PROFInet components“).

RequirementIf you create a PROFInet component and wish to import it, then the library must havebeen created using SIMATIC iMap.

Importing the PROFInet Component into a Library after CreationProceed as follows:

1. Create and test your basic project.

2. In SIMATIC Manager, select the station for the component to be created.

3. From the context menu, select Create PROFInet Component.

4. In the "Create PROFInet component" dialog box, "Storage Areas" tab, select one ofthe following options:

– "Target library" or

– "Target library and File system"

and select the desired target library.

5. On the other tabs of the dialog box, enter any settings you wish to make and clickon OK to confirm.

Result: The PROFInet component is created in the specified folder in the library (and inthe file system, if necessary).



7.2.8 Modifying PROFInet Components

Modification optionsIf you wish to modify existing PROFInet components, you must always modify theassociated STEP 7 project in SIMATIC Manager, and then recreate the PROFInetcomponent.

Procedure for Editing a STEP 7 Basic ProjectThe procedure for modifying an existing PROFInet component is as follows:

1. Open the basic project in SIMATIC Manager.

2. Make your changes to the program or hardware configuration.

3. If necessary, compile the program changes and save the STEP 7 project (andhardware configuration, if necessary).

4. Create a new PROFInet component from the modified station or DP slave. Selectthe Edit > Create PROFInet Component menu command.

5. Click on "OK" to confirm.

6. If you have only specified the file system (and no library) as the storage location,import the created PROFInet component into a SIMATIC iMap library.

You can then use the modified PROFInet component in a SIMATIC iMap project.



7.2.9 System Library

STEP 7 library with templates for PROFInet componentsSIMATIC iMap STEP 7 AddOn installs an S7 library containing all the blocks you needas templates for creating PROFInet components.

The PROFInet library can be found in the STEP 7 \s7libs\PROFInet directory.

You can open the PROFInet library in SIMATIC Manager, and then copy and adapt theblocks you need in the basic project for the PROFInet component.

Content of the PROFInet Library

Figure 7-34 Content of the PROFInet Library



Folder Content: Blocks for...

CP 300 PROFInet devices with CP 343-1 PNDP slave PROFIBUS devices with fixed functionalityI-DP slave PROFIBUS devices with programmable functionality (intelligent

PROFIBUS devices)WinLC PN Windows logic controller WinLC PN

NoteThe numbers of the blocks (DB, FC, FB) may be modified as required in the S7program.

Blocks for PROFInet devices with CP 343-1 PN

Block Description


FB88 PN_InOut - Data transmission between interface DB and PROFInet CP .The function block must be called in the user program (OB1) for thePROFInet component.Attribute: CBA_iecp_copy_fb and value: true



Blocks for PROFIBUS Devices with Fixed Functionality

Block Description


Blocks for Intelligent PROFIBUS Devices

Block Description

FC10 PNPN_IN - Copies the data from the transfer area of the DP master withproxy functionality to the input of the interface DBAttribute: CBA_islave_copy_fc and value: in

FC11 PN_OUT – Copies the outputs of the interface DB to the transfer area ofthe DP master with proxy functionality.Attribute: CBA_islave_copy_fc and value: out

DB2 Data block PN_IO_DBAttribute: CBA_islave_copy_db and value: true


OB82, OB86 Error organizational blocks (see the section entitled " Special Features ofDP Slaves")

* The functions PN_IN and PN_OUT must be called in the user program (OB1) for the PROFInetcomponent.

NoteThe blocks PN_IN, PN_OUT and PN_IO_DB must always have the same version,otherwise errors may occur in the plant.

Blocks for WinLC PN

Block Description

DB100 Global data block PN_Interface_DB as a template for the interfaceDB.Attribute: CBA_db and value: true

OB82, OB85, OB86 Error organizational blocks (see section entitled "WinLC PN" )



7.2.10 Properties of PROFInet Components of SIMATIC Devices

Special Features of SIMATIC DevicesPROFInet components of SIMATIC devices have the following special features:

• Conversion of S7 data types into PROFInet data types

• The "lifestate" connector

• Connectable and non-connectable connectors (see also "Properties of the InterfaceDB")

Conversion of S7 data types into PROFInet data typesThe following table illustrates the conversion of S7 data types into the correspondingPROFInet data types (as per Microsoft OLE 2.0).

PROFInet data type S7 data type Range of values

BOOL BOOL TRUE / FALSEI1 CHAR -128 to +127UI1 BYTE 0 to 255R4 REAL 3.4E +/- 38I2 INT -32,768 to +32,767UI2 WORD 0 to 65,535I4 DINT 2,147.483.648 to +2,147,483.647UI4 DWORD 0 to 4,294,967,295DATE* DT (DATE_AND_TIME) 01.01.1900 00:00:00 to

31.12.9999 23:59:59BSTR STRING String of charactersARRAY** ARRAY One-dimensional

* Depends on the device type

** An ARRAY may be formed from the following PROFInet data types: I1, UI1, I2, UI2, I4 andUI4. The maximum length depends on the amount of memory in the device.



The "Lifestate"“ ConnectorThe technological functions of PROFInet components created using STEP 7 have anadditional output of the type UI1, known as "lifestate". This output allows the PROFInetcomponents to be monitored by the user program of a PROFInet communicationpartner. The lifestate output can be interconnected as required for diagnostic purposes.

The lifestate output can return the following values which describe the current state ofthe device:

Table 7-10 Lifestate values

Value Designation of thestate

General significance

0x00 NonExistent The device is not powered and is thus unable tocommunicate. This operating state cannot betransferred via the interconnection since nocommunication is possible. It is only listed for the sakeof completeness.This value is also the default substitute value.

0x01 Initializing The device is initializing, e.g. after a power off or reset.0x02 Ready The device is ready for use, but the component is not

active. The device outputs are in the safe state.This state corresponds to the STOP operating state ofa CPU, for example.

0x03 Operating The device is operating normally.This state corresponds to the RUN operating state of aCPU, for example.

0x04 Defect There is an error in the device that cannot be rectifiedwithout further intervention. Typical examples includehardware or firmware errors. The device can only berestarted by switching the power off and on again.Only limited communication is possible with the device,depending on the type of error.

The value is 1 byte long.



7.2.11 Version numbers of PROFInet components

ApplicationEvery PROFInet component has a version number that forms a unique identifier for thecomponent together with the identification (class ID). This ensures that a newly createdPROFInet component does not accidentally overwrite an earlier issue of thecomponent.

Structure of the Version NumberThe version contains four series of numbers, separated by dots.

• The first two parts of the version number (user version) may be assigned asrequired (up to 3 digits) e.g. 01.04

• The last two parts (build version) cannot be modified and are incrementedautomatically.

Figure 7-35 Structure of the Version Number

RulesWhen you enter a version number, it must always be higher than the previous number.

You can change the first two parts or leave them unchanged. If you change them, youare asked whether the last two parts should be reset to 0 or incremented.



Automatically incrementing the version numberThe last two parts of the version number are automatically incremented as follows:

• The last part (minor build version) is incremented by one whenever a new versionof the PROFInet component is successfully created.

• The penultimate part (major build version) is incremented by one whenever theinterface DB is changed. The last part is automatically set to 0.

This applies both to the general interface DB (CBA_db attribute with the value true)and to any internal interface DB (CBA_intern_db attribute with the value true).

If the general interface DB (CBA_db attribute with the value true) is changed, then anew interface ID is also assigned automatically.

NoteThese changes are only applied if the PROFInet component was createdsuccessfully. If creation was cancelled, the version number and the interface ID (ifapplicable) remain unchanged.

7.3 Plants with SIMATIC Devices

7.3.1 Special Features of Plants with SIMATIC Devices

SIMATIC devices in SIMATIC iMap projectsPlease note the following points when you use SIMATIC devices as PROFInet devicesin a project:

• When you commission the plant, certain software requirements must be fulfilled,and certain settings must be made in STEP 7.

• STEP 7 provides a number of special options for editing PROFInet components ofSIMATIC devices.

• The SIMATIC iMap online view contains device-specific online and diagnosticfunctions.

• You must configure the OPC server in order to monitor variables via OPC.



Requirements for commissioning the plant• You must be running STEP 7 V5.2 or later on your PC/PG in order to:

– Generate the project

– Download device-specific data (programs) to the devices

– Edit the PROFInet components of the SIMATIC iMap project using STEP 7

• The optional configuration and programming packages associated with the devicesused for must be installed.

• SIMATIC NET Softnet IE PG V6.0 SP6 is needed in order to run online functionswith SIMATIC iMap via Ethernet – e.g. download, monitor or online-offlinecomparison.

• The devices of the plant must have been assembled, wired, networked, and startedup correctly. All the necessary addresses, such as the IP address, subnet mask,gateway address and PROFIBUS address, must have been assigned using thedevice-specific resources, e.g. using STEP 7 via MPI. You will find the necessaryinformation in the associated product documentation.

• To be able to access target systems from SIMATIC iMap, configure a PG/PC andthen assign the configured PG/PC to the system you have created. In this way, youcan transfer default settings to the installed interfaces of your created system duringthe configuration process. (In this situation, interfaces are module parametersettings on the PG/PC). The steps are as follows:

– Setting the PG/PC Interface

– Assigning the PG/PC



Data storage- the STEP 7 shadow projectWhen you generate a SIMATIC iMap project with PROFInet components of SIMATICdevices for the first time, a common STEP 7 component project is formed from all thecomponent projects in the shadow project. The STEP 7 shadow project is located inthe SIMATIC iMap project directory under Step7\Shadow. It contains a station forevery component with programmable functionality in the SIMATIC iMap project.PROFIBUS devices with fixed functionality are assigned to the station of the DPmaster system concerned.

Figure 7-36 Data storage with STEP 7 projects

All changes to PROFInet components, e.g. IP addresses or PROFIBUS addresses, aretransferred to the STEP 7 shadow project whenever the SIMATIC iMap project isregenerated.



The shadow project is automatically opened for editing in SIMATIC iMap whenever theEdit > Special > SIMATIC Manager) menu command is called for a technologicalfunction or device.

CautionChanges made to the shadow project in the device-specific programming andconfiguration tool (e.g. STEP 7) are ignored during generation with SIMATIC iMap,and may thus be overwritten.When you edit the STEP 7 shadow project, you must make sure that it contains noinconsistencies, since these could lead to inconsistencies in the SIMATIC iMapproject and to communication faults in the plant.

Regenerating a ProjectThe Project > Generate > Changes Only menu command only generates thechanges. If this is not possible because the S7 program or the hardware or networkconfiguration contains incorrect or inconsistent data, for example, then the STEP 7shadow project must be fully regenerated.

When you select the Project > Generate > All menu command a new STEP7 projectis created, and all the stations of the associated component projects from the libraryare added to the library once more.

CautionAny changes that you have made to the shadow project using STEP 7 areoverwritten by the regenerated shadow project. A copy is made of the old shadowproject. You can use this to copy any changes in the new shadow project.

The new shadow project is always called "Shadow". An extension is appended to thename of the copy of the old shadow project.



Consistency analysis after generationThe consistency analysis is a comparison between the SIMATIC iMap project and theassociated shadow project.

The consistency analysis checks the following:

• Generation status of all instances in the SIMATIC iMap project

• Existence and comparison of the devices

• Existence and comparison of the technological functions

• Comparison of object properties transferred to the shadow project: Names of thedevices and functions, IP addresses, subnet masks, router addresses, MACaddresses and PROFIBUS addresses of the devices.

• Comparison of the assignments between devices and technological functions.

• Comparison of the assignments between PROFIBUS master and PROFIBUSslaves

This used to trace actions carried out on the shadow project.

NoteThere is no check to determine whether the interface DB and other blocks of theS7 program are consistent with the hardware configuration.

The consistency analysis is only carried out for SIMATIC devices.

The ProTool component and other non-Siemens devices are not included in thecomparison.

Switching the consistency analysis on and off

Use of the consistency analysis is controlled via the SIMATIC iMap settings.

If the "Consistency analysis after generation" option is checked, then the consistencyanalysis is carried out whenever the project is generated. The results of theconsistency analysis are displayed in the information window.

Select the Options > Settings menu command on the "General" tab to view thecurrent settings and change them if necessary.



7.3.2 Using SIMATIC devices in Online Mode

Special Features of SIMATIC DevicesThe following online functions are provided for SIMATIC devices:

• Online/offline comparison of STEP 7 data

• Display the operating states of accessible PROFInet devices

• Diagnostics

Online-Offline Comparison of the ProgramsThe online-offline comparison of the program data for SIMATIC device compares theblocks of the associated STEP 7 shadow project with the online blocks. The result ofthe comparison is displayed in the Diagnostic window, "Info" tab.

Program download

CautionProgram downloads can only be carried out when the devices are in the STOPoperating state.

The devices must be in the STOP operating state while the program is downloaded. Ifthis is not the case, the devices attempt to switch to STOP when one of the followingmenu commands is called:

• Download All Devices > All / > Program Only

• Download Selected Device > All / > Program Only

Before the program is downloaded, you are asked whether the device should beswitched to STOP. You may also have to press the operating mode switch, andpossibly enter a password, depending on the type of device, and the currently set levelof protection.

Once the program has been downloaded to a device, you are asked whether you wishto switch the device to RUN. If you click on "Yes" to confirm, this occurs automatically.If you click on the "No" button, the device remains set to STOP, and can subsequentlybe switched to RUN.



Tip: Permanently storing the downloaded data

With some devices in SIMATIC iMap, once you have downloaded the program youmust call the Special > Copy RAM to ROM menu command in order to transfer thedata to the ROM area of a device. This means that the data is retained even after thepower is switched off.

Operating States of SIMATIC DevicesThe current operating state of a device is displayed as a symbol in the SIMATIC iMaponline network view. The operating states STOP, RUN and STARTUP are displayedfor SIMATIC programmable controllers.

Icon Operating state

RUN

STOP

STARTUP

DEFECTIVE

For PROFIBUS devices it is also indicated whether the device is connected to thePROFIBUS master:

Icon State

Connected to the DP master (proxyfunctionality)Not connected

PROFIBUS Device InputsWhen a PROFInet device acting as a PROFIBUS master is switched to the STOPoperating state, the inputs of the technological functions of the associated PROFIBUSdevices are set to zero (safe state).



7.3.3 Editing with STEP 7

IntroductionIf you have created a PROFInet component using STEP 7, you can call certain STEP 7applications from SIMATIC iMap, e.g. ladder diagram/sequential functionchart/statement list or HW Config, in order to modify the S7 program or parametersettings for a module. This will also edit the associated STEP 7 shadow project.

In SIMATIC iMap you can edit PROFInet components using STEP 7 in the followingways:

• Modify a technological function in the SIMATIC iMap project

• Modify a PROFInet device in the SIMATIC iMap project

CautionWhen you edit the STEP 7 shadow project, you must make sure that it contains noinconsistencies, since these could lead to inconsistencies in the SIMATIC iMapproject and to communication faults in the plant.

Special editing functions for SIMATIC devices

Table 7-11 Editing technological functions in the plant view

Edit > Special > menu command Meaning

Compare blocks Runs an online-offline comparison of the programblocks, i.e. compares the blocks in the targetsystem (online) with the blocks in theSIMATIC iMap shadow project (offline).

Program Opens the program folder for the associatedmodule in SIMATIC Manager. You can open theblocks, sources and symbol table for editing.

SIMATIC Manager Opens the shadow project in SIMATIC ManagerMonitor variable Opens variable table VAT1 for the station in the

shadow project. You can enter the variables ofthe technological function (from the interface DB)to be monitored in the variable table, for example.If a variable table called VAT1 already existedwhen you created the PROFInet component, it isopened at the first call, otherwise the VAT1 tablein the shadow project is originally empty.



Table 7-12 Editing devices in the network view

Edit > Special > menu command Meaning

Download user program to memorycard

Downloads the generated user program to theCPU's memory card (only for modules thatsupport a memory card).

Module state Displays the current state of the module. The"Module State" tab opens in the online view.

Operating state Displays the current operating state of themodule. You can then modify the module'soperating state in the "Operating state" dialog.

Diagnose hardware Opens the hardware setup for the station that canbe accessed online in diagnostic mode.

Configuration Opens the station's hardware configuration(offline, on the PC/PG)

Network configuration Opens the network configuration (Netpro) for thestation

Assigning the PG/PC Opens the "Assign PG/PC" dialog boxCopy RAM to ROM Copies the content of the RAM memory of the

current module to the ROM area (only formodules that support this functionality).

SIMATIC Manager Opens the shadow project in SIMATIC ManagerClear / Reset Clears / Resets the device.

RequirementsThe following software must be installed on your computer in order to edit PROFInetcomponents using STEP 7:

• STEP 7 basic package with the necessary optional packages

• SIMATIC iMap STEP 7 Add-on

The project must have been saved and generated in SIMATIC iMap (Project >Generate menu command).



Editing a Technological Function or DeviceProceed as follows:

1. Select the technological function or device from the SIMATIC iMap project.

2. Select Edit > Special from the context menu using one of the available commands.

3. Save any changes and close STEP 7.

4. Select the device from the network view.

5. Select the Download Selected Device > Program Only menu command todownload the program to the target system.

NoteIf you change the interface DB and download from STEP 7 to the device, youmust make sure that all the associated PROFInet blocks with the attributeCBA_... are downloaded as well, otherwise run-time errors may occur in theprogram.

HintAfter using a special editing function, you can also download the program from STEP7. This is a good idea, particularly if you have only modified blocks, for which you donot have to switch the device to STOP.

CautionThe shadow project is overwritten when you regenerate the SIMATIC iMap projectusing the Edit > Generate > All menu command. A copy of the old shadow projectis stored in the same directory. You can use this copy to update any changes thatyou made in the shadow project using special editing functions.

7.3.4 Setting the PG/PC Interface

ApplicationYou must establish a connection from STEP 7 to the Ethernet in order to downloadprograms or use certain online functions on the SIMATIC devices in the plant. To dothis, you must set the PG-PC interface in STEP 7 as follows:

• To TCP/IP if all remote devices in the plant can be accessed via Ethernet or

• To "PC internal" (local computer) if a WinLC PN is installed there.



In this way you can access all the SIMATIC devices, whether they are on the Ethernetor PROFIBUS or are on a local PC/PG, e.g. a WinLC PN.

Setting the PG/PC interface to TCP/IPProceed as follows:

1. Select Start > Simatic > STEP 7 > Set PG-PC interface.

2. In the "Set PG-PC interface" dialog box , "Access path" tab, select from the "Accesspoint for application" box:S7ONLINE (STEP 7).

3. Select "TCP/IP..." with the associated network card from the "Interface parametersettings used" box.


Figure 7-37 Setting the PG/PC interface to TCP/IP



Setting the PG/PC interface to local computerIf a WinLC PN representing part of the iMap project is installed on the local computer,this WinLC PN takes over communication with the PROFInet and PROFIBUScommunication partners. The procedure is as follows:

1. Select Start > Simatic > STEP 7 > Set PG-PC interface.

2. In the "Set PG-PC interface" dialog box , "Access path" tab, select from the "Accesspoint for application" box:S7ONLINE (STEP 7).

3. Select "PC internal (local) from the "Interface parameters settings used" box.


Figure 7-38 Setting the PG/PC Interface to Local Computer

NoteIf there is a local WinLC PN on the computer running SIMATIC iMap, then theprogram must first be downloaded to this WinLC PN so that programs andinterconnections can then be downloaded to the other devices of the plant.



7.3.5 Assigning the PG/PC

Basic procedureBefore you can download programs from SIMATIC iMap to all the PROFInet andPROFIBUS devices, you must first assign the PG/PC interface to each iMap project.The steps are as follows:

• Select an interface

• Configure the interface

• Assign the configured interface to the PG/PC

NoteThe PG/PC assignment is automatically carried out in SIMATIC iMap when theproject is generated for the first time, and then whenever it is regenerated. Inspecial cases, the PG/PC assignment cannot be carried out automatically, e.g.

• there are several network cards on the PG/PC or

• the PG/PC interface S7ONLINE (STEP 7) is not set to TCP/IP.

In these cases, an error is signalled in the information window during generation,and you will have to assign the PG/PC as described below.

The PG/PC assignment is not required if a local WinLC incorporating a networkcard is used.



Selecting an interfaceProceed as follows:

1. Generate the SIMATIC iMap project using the Project > Generate > ChangesOnly menu command.

2. Select any SIMATIC device from the network view and call the Edit > Special >Assign PG/PC menu command.

3. In the "PG/PC interface" dialog box, "Interfaces" tab, click on the "New" button andselect "Ind. Ethernet" from the selection list. Click on "OK" to confirm your choice.



Configure the interface

1. Enter the IP address and subnet mask of the local computer in the "Properties ofthe Ethernet interface" dialog box and select the Ethernet subnet.

2. Click on "OK" to confirm your input. Result: The interface you have just configuredappears on the "Interfaces" tab.

Assign the configured interface to the PG/PCThe Ethernet interface you have just configured appears under "Not assigned" in the"Configured interfaces" selection box on the "Assignment" tab.



1. Under "Not assigned" in the "Configured interfaces:" selection box, highlight theEthernet interface you have just configured and, in the "Interface parameter settingson the PG/PC:"TCP/IP -> <Network card used >box, select the interface of the system you have created to be assigned to theinterface selected above.

2. Click on the "Assign" button.

3. Activate the "S7ONLINE access" option.



Result: The assigned interface appears in the "Assigned" selection box. Click on "OK"to activate the assignment.



7.3.6 Setting up the OPC Server

OPC symbol fileCreate the OPC symbol file for the plant in SIMATIC iMap using the Options > CreateOPC symbol file menu command. The following OPC symbol files are created andstored in the directory of your choice:

• _TAGFILE_.SSD

• _TAGFILE_.WSD

Setting up the OPC serverTo set up the OPC server:

1. Select the following command: Start > Simatic > SIMATIC NET > Settings > SetPC station. The configuration console opens. This is used to make your new OPCsymbol file known to a SIMATIC NET OPC server.

2. In the "Structure" window, open the "Applications > OPC settings" folder.

3. Open the OPC protocol selection dialog box and select the following protocols:.

– PROFInet – always

– S7 – for non-connectable connectors of programmable PROFIBUS devices(intelligent DP slaves) only. The non-connectable connectors are highlighted inthe interface DB with the attribute CBA_transfer_type = s7extended.

4. Click on the "Accept" button.

5. Open the "Symbols" folder. Select the "Use symbol file" option and enter the path ofthe _TAGFILE_.SSD symbol file under "File name" (see above).

Click on the "Browse" button to search for the file.

6. Click on the "Extended symbols" button and select the module for the TCP/IPprotocol on your PG/PC from the "PROFInet" box.

7. Click on the "Accept" button.

The OPC server is now set up on your PG/PC, and you can visualize process data withreference to the OPC symbol data using an OPC client such as the OPC Scout.



7.4 Off-The-Shelf PROFInet Components

7.4.1 Overview of the off-the-shelf PROFInet components

Off-The-Shelf PROFInet ComponentsThe following off-the-shelf PROFInet components are supplied with SIMATIC iMap:

• IE-PB-Link PN for use with an Industrial Ethernet - PROFIBUS DP IE/PB Linknetwork transition(for different transmission speeds)

• ProTool-Std-PC for use with the ProTool/Pro Configuration V5.2 SP3 HMI software(for different HMI devices)

• "Diag Repeater" for use with the diagnostic repeater

The off-the-shelf PROFInet components are located in the \iMap\componentsdirectory. You will have to import them into a SIMATIC iMap library (Library > ImportComponent menu command) before they can be used in SIMATIC iMap.

7.4.2 IE/PB Link

ApplicationThe IE/PB Link is a network transition that interconnects the two types of network:Industrial Ethernet (factory level) and PROFIBUS (cell level).

Function in the PROFInet environmentIE/PB Link is a PROFInet device, and is represented accordingly in the SIMATIC iMapnetwork view.

The IE/PB Link acts as a DP master on the PROFIBUS interface. The IE/PB Linkprovides the connection to coupled PROFIBUS devices for the PROFInet devicesconnected to the Ethernet. For the coupled PROFIBUS devices, the IE/PB-Link is a DPmaster with proxy functionality.



Representation in SIMATIC iMapThe PROFInet component of the IE/PB Link has fixed functionality, but has notechnological function. It is supplied ready for use in the SIMATIC iMap system library,It is not necessary to create a component in STEP 7 for the IE/PB Link.

• Network view in SIMATIC iMap

In the network view, the IE/PB Link is represented as a component that links theEthernet and PROFIBUS. The IE/PB Link can be selected and configured from thisview.

• Plant view in SIMATIC iMap

The IE/PB Link is not shown in the plant view.

Bus PortsThe PROFInet component of the IE/PB Link has two bus ports:

• A connector to PROFIBUS as the DP master and

• A connector to the Industrial Ethernet

Figure 7-39 Bus Ports of the IE/PB Link



Special features• Range of functions as a DP master

The IE/PB Link supports operation with DP standard slaves (DP V0). Acyclicalservices (reading and writing records) are not supported.

• Substitute values for DP slaves under PROFInet

When it acts as a DP master under PROFInet, the IE/PB Link is configured to applysubstitute values.

If the IE/PB Link detects the failure of a connected (interconnected in PROFInet)DP slave, it sends the substitute value "0" to the inputs interconnected with this DPslave.

Lifestate monitoring allows this PROFInet component to detect if the input valuessupplied are substitute values.

Example

Table 7-13 PROFInet component of the IE/PB Link, representation in SIMATIC iMap

Technological function PROFInet device

None



7.4.3 Diagnostic Repeater

ApplicationThe Diagnostic Repeater is a repeater that is able to monitor a segment of an RS 485PROFIBUS subnet (copper wire) during operation and to signal line faults to the DPmaster via a diagnostic telegram. Operating and monitoring devices (HMI) can be usedto display the location and cause of the fault in clear text.

The Diagnostic Repeater performs its line diagnostics during operation, so line faultscan be detected early and located, thus minimizing the duration of any plantstoppages.

Function in the PROFInet environmentThe Diagnostic Repeater is a PROFIBUS device, and is represented accordingly in theSIMATIC iMap network view.

The Diagnostic Repeater acts as a DP slave at the PROFIBUS interface.

You can look up the diagnostic information as follows in SIMATIC iMap:

• Select the "DiagRepeater" device from the network view.

• Select the Special > Module State command from the context menu.

The information can be found in the diagnostic buffer.

Representation in SIMATIC iMapThe PROFInet component of the Diagnostic Repeater is supplied ready for use in theSIMATIC iMap system library, so the component does not have to be created in STEP7.

• Network view in SIMATIC iMap

The Diagnostic Repeater is represented in the network view as a component on thePROFIBUS, where it can be selected and configured.

• Plant view in SIMATIC iMap

The Diagnostic Repeater cannot be seen in the plant view since it is not atechnological function.



Bus PortsThe PROFInet component of the Diagnostic Repeater has four PROFIBUS connectors:

• Connector A1/B1 for the incoming bus cable for segment DP1

• Connector A1'/B1' for the outgoing bus cable for segment DP1

• Connector for the bus cable of segment DP2, with test circuit for line diagnostics

• Connector for the bus cable of segment DP3, with test circuit for line diagnostics

Of these, only connector A1/B1 for the incoming bus cable of segment DP1 can beseen in the SIMATIC iMap network view.

Figure 7-40 Bus ports for the Diagnostic Repeater

Special featuresNone

Further information...can be found in the Diagnostic Repeater for PROFIBUS-DP manual, order number6ES7972-0AB00-8AA0.



Example

Table 7-14 PROFInet components of the Diagnostic Repeater, representation inSIMATIC iMap

Technological function PROFInet device

None


Reference 88.1 Toolbar

Buttons on the toolbarThe buttons on the toolbar are specially designed for working with SIMATIC iMap.They correspond to the following menu commands:

Table 8-1 Buttons on the SIMATIC iMap toolbar

Icon Menu command

Project > New

Project > Open...

Project > Save

Project > Generate > Changes Only

Project > Print...

Edit > Cut

Edit > Copy

Edit > Paste

Edit > Open Chart One Level Up

Paste > New Chart (and move selected objects if necessary)

Plant > Plant View > Display Interconnection Lines

Online > Monitor

Online > Variable Table > Monitor Variables

Online > Variable Table > Transfer Control Values

Help > Help Topics

View > Project Window

View > Diagnostic Window

View > Information Window

View > Library Window

Reference


Icon Menu command View > Preview Window

View > Zoom > Zoom In

View > Zoom > Zoom Out

View > Zoom > Entire Content

View > Zoom > 100%

Reference


8.2 Menu bar

Menu commands can be used to create and edit selected objects (e.g.charts, functionsand libraries). These menu commands can be accessed via the menu bar, in thecontext menu and sometimes as an icon on the toolbar.

The menus on the menu bar of the SIMATIC iMap user interface are explained brieflybelow. This description may differ slightly from the actual application, but anydifferences will be updated in the next version.

Project menu

Menu commands Description

New Creates a new project. Before it is opened, the currently openproject is closed.

Open... Opens an existing project. Before a new project is opened,the currently open project is automatically closed.

Save Saves the current project.

Save As... Saves the current project under a new name.Archive... Archives the current project.Retrieve... Retrieves a project.Generate > Changes Only Saves and generates the changes to the current project, i.e.

the modified data is synchronized with the shadow project.This is required in order to use the online functionality(download and diagnostics).

Generate > All Saves and generates the current project from scratch, i.e. theshadow project is recreated from the PROFInet componentsin the library.

Page Setup... Opens a dialog box for making settings for printing.Headers / Footers Displays the settings for the header and footer of a printout.All Charts Prints the network view and all the charts in the plant view.Print > Active Window Prints the current plant or network view.Document... Creates the documentation for the current project.Properties... Opens a dialog box containing the individual parts of the

project. You can enter a password in order to protect theproject against unauthorized access.

Recent Projects List of the recently opened projects.

Exit Exits SIMATIC iMap. If the edited project has not yet beensaved, you are prompted to save it.

Reference


Edit menu


Cut Removes the selected objects and saves them on theclipboard.

Copy Copies the selected objects to the clipboard.Paste Inserts the clipboard contents.

Delete Removes the selected objects.Select All Selects all the objects in the current window.Undo Selection Deselects the selected objects.Select in all Windows Selects all the associated objects in the project window, the

plant view, the network view and the library

Open Selected Chart Opens the selected chart.Open Chart One Level Up Opens the chart one level up.Go To > Used to navigate between the various windows.Find ... Finds functions and devices that match the search text.Plant View > In Chart Interface Transfers the selected connectors to the chart interface.Plant view > InterconnectConstants

Sets a constant value at the input.

Plant View > MoveInterconnections

Moves the interconnections of the technological function.

Variable Table > Deactivate Deactivates monitoring of the selected variables.

Variable Table > Reactivate Reactivates monitoring of the selected variables.Information Window > Copy All Copies all the messages in text format to the clipboard.Information Window > Deletes all the messages from the information window.Special > Delete All Calls up functions or dialogs associated with the device-

specific programming / configuration tool, e.g. SIMATICManager, module status.

Properties... Displays the properties of the selected object.

Reference


View menu


Toolbars Shows or hides the toolbar.Status Bar Shows or hides the status bar.Project Window Shows or hides the project window.

Diagnostic Window Shows or hides the diagnostic window.Library Window Shows or hides the library window.Preview Window Shows or hides the component preview window.Information window Shows or hides the information window.Plant View > Page Margins Shows or hides the page margins for printing in the plant or

network view.Plant View > Dot Screen Shows or hides the dot screen in the plant view.Plant View > RecalculateInterconnection Lines

Redraws the interconnection lines.

Plant View > DisplayInterconnection Lines

Shows or hides the interconnection lines

Project View > Plant Chart > Changes the representation of the plant chart in the projectwindow.

Project View > Network Chart > Changes the representation of the network chart in the projectwindow.

Project View > Show Levels Shows all the levels below the selected object in the projectview.

Project View > Hide Levels Hides all the levels below the selected object in the projectview.

Variable Table > Shows or hides columns in the variable table.Zoom > Used to change the size of the project displayed in the plant

or network view.

Insert menu


New chart Inserts a new chart into the plant chart.Library Components Inserts the selected PROFInet component from the library into

the plant or network view.

Reference


Online menu


Monitor Activates / deactivates the online connection betweenSIMATIC iMap and the devices of the plant. Activating theonline connection does not result in a download. "Monitor"must be activated before diagnostics can be used.

Download All Devices > All Downloads the interconnections and programs to all thedevices of the plant.

Download All Devices > ProgramOnly

Downloads the programs to all the devices of the plant.

Download All Devices >Interconnection Only

Downloads the interconnections to all the devices of the plant.

Download Selected Device > All Downloads the programs and interconnections to the selecteddevices.

Download Selected Device >Program Only

Downloads only the programs to the selected devices.

Download Selected Device >Interconnection Only

Downloads only the interconnections to the selected devices.

Online / Offline Comparison All Runs an online-offline comparison for the programs andinterconnections of the selected objects.The result appears in the information window.

Online / Offline ComparisonProgram Only

Runs an online-offline comparison for the programs of theselected objects.The result appears in the information window.

Online / Offline ComparisonInterconnection Only

Runs an online-offline comparison for the interconnections ofthe selected objects.The result appears in the information window.

Check Accessibility Checks whether the associated devices are accessible online.The result appears in the information window.

Variable Table > MonitorVariables

Activates online monitoring with the variable table.The result appears in the diagnostic window.

Variable Table > Transfer ControlValues

Transfers the control values of the selected variables to theplant.

Variable Table > Copy OnlineValue

Copies the current online values of the selected variableswithin the variable table to the clipboard.Use the Paste context menu to insert the values, e.g. ascontrol values.

Reference


Library menu


New... Opens a dialog box for creating a new library, e.g. for a newproject or new operations.

Open... Opens a dialog box for selecting an existing library.Close Closes the current library.Archive... Opens a dialog box for archiving the current library and

specifying the path.Retrieve... Opens a dialog box for selecting a library from an archive.Import Components... Imports an existing PROFInet component from a directory to a

library.View > Changes the view of the PROFInet components in the

selected library.Auto Arrange Automatically arranges the representation in the library

window.Properties... Opens the Properties dialog box for the selected library.Find Instances Searches the project for the PROFInet components

(instances) that are selected in the library window.The result appears in the information window.

Recent Libraries Lists the most recently opened libraries.

Options menu


Settings ... Used to change the general settings in SIMATIC iMap.Language > Changes the language of the SIMATIC iMap user interface.Create OPC Symbol File... Creates an OPC symbol file for the entire project.Import Variable Table... Imports a stored variable table to the diagnostic window.Export Variable Table... Saves a variable table as a .cbv file.Tools... Opens the programs that are defined under “Settings“.

Reference


? menu


Help F1 Opens the online help for the current windowHelp Topics Opens the "Component based Automation" online help.Getting Started Opens the Introduction to SIMATIC iMap.About Provides information on the current software version and

copyright.

8.3 Actions

Which actions do you want to carry out?The following table lists, in alphabetical order, the actions that you can carry out withSIMATIC iMap and describes where and how these actions can be used.

As a rule, the objects to be processed must be selected first.

Which object? Which action? In whichwindow?

How?

Addresses Assign Network view orplant view

Edit > Properties > Address tab

Library Create Library Library > NewArchive Library > ArchiveRetrieve Library > RetrieveClose Library Library > CloseOpen Library Library > Open

Library Window Display View > Library Window.Diagnostic Window Display View > Diagnostic Window

Download Run Online > Download...Documentation forPROFInetcomponents

Open Options > Documentation Link

Documentation forSIMATIC iMap

Open Desktop Start / Programs /Component basedAutomation / SIMATIC iMap Manual

Inputs / Outputs Interconnect Plant View Click on the input that you wish tointerconnect, and then on the correspondingoutput.

Reference



How?

Properties Display / modify Edit > Properties...Project > Properties

Faulty Diagnose DiagnosticWindow

Online > Monitor

Device Rename Network view Edit > Properties > Address tabInformation window Display View > Information Window

IP address Assign Network view Edit > Properties > Address tabChart Print Network view Print context menu

Zoom Network view Zoom context menuSubordinate chart Create Plant View Paste > New chartOnline value Display Plant View Online > Monitor

Display Online Values context menuSet Plant view /

variable tableSelect connectorSet Online Values context menu

Copy Variable table Copy Online Values context menuPaste Variable table Paste context menu

PROFIBUSaddress

Assign Network view Edit > Properties > Address tab

PROFInetcomponent

Import into alibrary

Library Import PROFInet component context menu

Insert into thenetwork view

Library Drag&DropEdit > Paste

Create STEP7 See the ? menu command > Help TopicsCopy Plant / network

viewCopy context menuResult: The component is on the clipboardand can be pasted into the selected windowvia the context menu.

Rename Library Not possible.Move From library to

libraryDrag&DropEdit > Copy / Paste

Project Archive SIMATIC iMap Project > ArchiveRetrieve Project > RetrieveDocument Project > DocumentPrint Project > Print

(Keyboard: Ctrl + P)Generate Project > Generate

Open Project > Open(Keyboard: Ctrl + O)

Reference



How?

Save Project > Save / Save As(Keyboard: Ctrl + S)

Delete WindowsExplorer

Project Window Display View > Project Window.Technologicalfunction

Rename Plant View Edit > Properties > Address tab

Variable table Display DiagnosticWindow

View > Diagnostic Window > Variable Tabletab

Monitor Online > Variable Table > Monitor VariablesImport / export Options > Import / Export Variable TableImport / export Diagnostic

WindowImport... / Export... context menu

Interconnections Create Plant View Click on the input that you wish tointerconnect, and then on the correspondingoutput.

Delete Plant View Highlight the line and press the Del key.Tools Paste Options > Settings > Tools tab

Use Options > Tools...

Reference


8.4 Error numbers

Error messages for PROFInet devicesThe structure of the error messages (HRESULT) conform to the Microsoft coding rules.

The error messages always relate to a device and have the following meaning:

Error message Identifier Meaning Remedy

Out of memory(0x8007000E)

E_OUTOFMEMORY The device does nothave enoughmemory to establishthe connector

--

Establishinginterconnection(0x0004CA01)

CBA_S_ESTABLISHING The connector hasnot yet beenestablished

Try again later

Unknown object(0x8004CB01)

CBA_E_UNKNOWNOBJECT The target connectorof theinterconnection wasnot found

Download theprogram again

Different datatype(0x8004CB03)

CBA_E_TYPEMISMATCH Different or invaliddata type for theconnector

Download theprogram again

Invalidinterconnection(0x8004CB08)

CBA_E_INVALIDCONNECTION Invalidinterconnection of aconnector to itself

Download theinterconnection to thedevices once more.

Invalid DATEvalue(0x8004CB0A)

CBA_E_TIMEVALUEUNSUPPORTED The value of typeDATE is notsupported by thePLC.

Check the programsof both devices.

QoS type notsupported(0x8004CB0B)

CBA_E_QOSTYPEUNSUPPORTED The unit of measure(Quality of Servicetype) is notsupported by thetarget device

Change the unit ofmeasure anddownload theinterconnection to thedevices.

QoS value notsupported(0x8004CB0C)

CBA_E_QOSVALUEUNSUPPORTED The transferfrequency is notsupported by thetarget device

Change the transferfrequency anddownload theinterconnection to thedevices.

Reference


Error message Identifier Meaning RemedyData length toolong(0x8004CB12)

CBA_E_LIMITVIOLATION The data exceedsthe permitted volumeof data for the datatype concerned.

Run an online-offlinecomparison anddownload everythingto the device oncemore

Internal error(0x80004005)

E_FAIL Internal error --

Internal error(0x80070057)

E_INVALIDARG Internal error --

Communicationerror(0x8001****)

RPC_E_*(e.g.RPC_S_SERVER_UNAVAILABLE)

Generalcommunication fault:device inaccessibleor faulty, or faultyconnection

Check the deviceand the connections,and remedy the fault

Reference


8.5 File Types

Overview of the file types in SIMATIC iMapThe following table contains the file name extensions for the file types used inSIMATIC iMap.

File type Extension Created ... In ...

Project CBP with the menu commandProject > Save orProject > Save As

the project folder of the same name

Library CBL with the menu commandLibrary > New orLibrary > Create NewLibrary

the library folder of the same name

Archived project ARP with the menu commandProject > Archive

any folder in the file system

Archived library ARL with the menu commandLibrary > Archive

any folder in the file system

PROFInetcomponent

XML in the device-specificconfiguration andprogramming tool, e.g.STEP 7

in the component folder- in the file system or- in a library

Variable table CBV with the menu commandOptions > ExportVariable Table

in any folder in the file system

Projectdocumentation

HTML with the menu commandProject > Document


OPC symbol file SSDWSD

with the menu commandOptions > Create OPCSymbol File


NoteFor each file type, you can use the SIMATIC iMap Options > Settings menucommand, "Directories" tab, to define a directory that will be suggested firstwhenever you create, save and select this file type.


Abbreviations 9Abbreviations

Abbreviation Explanation

CbA Component based AutomationCOM Component Object ModelDCOM Distributed Component Object ModelGUID Global Unique IDentifier

HMI Human Machine InterfaceMAC Medium Access ControlPN PROFINetPNO PROFIBUS Nutzer Organisation e.V. (PROFIBUS User

Organization)

TIA Totally Integrated AutomationUNC Uniform Naming ConventionURL Uniform Resource LocatorXML EXtended Markup Language


Glossary 10Term Description

Basic project Project folder in the vendor-specific configuration tool from which aPROFInet component is created.Example: STEP 7 basic project

Chart In SIMATIC iMap, this is a folder containing technological functionsand their interconnections. The chart is used to structure the plant.We differentiate between the -> Main chart and -> subordinate charts

Chart, subordinate In SIMATIC iMap, a subordinate chart may be located at anyhierarchical level below the main chart in the plant view. It maycontain technological functions and further subordinate charts.

Component based Automation Concept for implementing modular, distributed automationapplications based on open standards for data processing and datacommunications.Component based Automation is an extension of Totally IntegratedAutomation (TIA).

Component project A folder containing the vendor-specific project data for the PROFInetcomponent, e.g. in the form of a STEP 7 project.

Device In Component based Automation, this is part of the PROFInetcomponent that contains the hardware-specific data for the PROFInetcomponent. In SIMATIC iMap, a device is the software representationof the physical device for which the PROFInet component wascreated. It is represented as an object with one or more bus ports inthe SIMATIC iMap network view. We differentiate between ->PROFInet devices and -> PROFIBUS devices according to thecommunication functions to be performed.

Filler element Declaration line in the interface DB that identifies unused I/O addresssections. The filler element is needed for certain types of device, e.g.for DP slaves with fixed functionality.

Functionality, fixed A PROFInet component with fixed functionality does not contain itsown user program.

Functionality, programmable A PROFInet component with programmable functionality contains itsown user program.

Interconnection General: A logical data link between two objects.In SIMATIC iMap: A connection between two technological functions.An output is always connected to an input of the same data type.Interconnections are represented by lines in SIMATIC iMap.

Glossary


Term DescriptionInterface DB In Component based Automation, this is a data block in STEP 7 that

describes the inputs and outputs of the technological function.Library In Component based Automation, this is a folder containing reusable

PROFInet components.Main chart In SIMATIC iMap, the main chart is the highest level of the

hierarchical representation of the plant. It contains all thetechnological functions and subordinate charts and theirinterconnections.

Network view Representation of the devices and networks (Ethernet, PROFIBUS)in SIMATIC iMap.

Plant view Representation of the technological functions of the automationsystem and its interconnections in SIMATIC iMap. The plant viewdisplays one chart.

PROFIBUS device In Component based Automation, a PROFIBUS device has just onePROFIBUS connector as a slave. It does not participate directly inPROFInet communication and is integrated via a PROFInet devicewith proxy functionality.

PROFInet Standard published by the Profibus User Organization (PNO) todefine a cross-vendor communication and engineering model.

PROFInet component Software representation of a technological module with definedfunctionality. An automation system is made up of several PROFInetcomponents.A PROFInet component essentially consists of a technologicalfunction and the associated device.

PROFInet device A device on the Ethernet is a PROFInet device. A PROFInet devicemay also have a PROFIBUS connector as a master and a proxyPROFInet device for PROFIBUS devices.

PROFInet device with proxyfunctionality

A PROFInet device that acts as the master for PROFIBUS devices.PROFIBUS slaves can thus be integrated into PROFInetcommunication.If the device has a local (internal) PROFIBUS, then it is the DPmaster for the local DP slaves.

Project window In Component based Automation, this is the hierarchicalrepresentation of the SIMATIC iMap project. There are two parts tothis representation:• The plant part contains the technological functions. This part may

be structured hierarchically using subordinate charts. The plantpart always contains the main chart and may contain any numberof nested subordinate charts.

• The network part contains the devices. The slaves coupled to aPROFIBUS master are represented hierarchically.

Separator element A declaration line in the interface DB that separates the input areafrom the output area, and ensures that the data is aligned at themargins. The separator element is required for certain types ofdevice, e.g. for DP slaves.

Glossary


Term DescriptionShadow project A folder in which the vendor-specific data for the project is stored

during generation in SIMATIC iMap.SIMATIC iMap The Siemens engineering tool for Component based Automation. It is

used to configure, commission and monitor modular, distributedautomation systems based on the PROFInet standard.

SIMATIC iMap - STEP 7 AddOn Software that links SIMATIC iMap to STEP 7.Technological function General: This is a task or sub-task within a technological process,

e.g. measurement, control of motors, positioning. A technologicalfunction may be implemented either as hardware - e.g. a functionalmodule - or as software - e.g. a controller module.In Component based Automation, the technological function of aPROFInet component comprises the application-specific functionalityof a programmable controller or field device and the componentinterface for communication with other PROFInet components.It is represented as a block with input and outputs in the SIMATICiMap plant view.

Index

Component based AutomationA5E00122598-03 Index-1

IndexAccess to process data 1-16Accessible device 6-11Automatically incrementing the version

number 7-76Basic project 5-43, 10-1Bus ports 7-1Calling tools 4-30Cancel generation 5-9CBA_direction 7-38CBA_pad_item 7-38CBA_transfer_type 7-38CBA_unused 7-38Chart

Subordinate 10-1Chart interface 5-41Class ID 5-18, 7-64Closing a project 5-4Commissioning 7-77

Requirement 7-77SIMATIC devices 7-76

Component based Automation 1-1, 10-1Component interface 1-7Component project 10-1connector

Input 1-7Interconnectable 1-7Non-interconnectable 1-7Output 1-7

Connector 1-7Data type 1-7

ConnectorsInterconnectable 7-39Non-connectable 7-39Order 7-41

ConnnectorName 1-7

Consistency analysis 7-80Switching on and off 7-80

Consistency analysis after generation 7-80Consistency of the transferred data

DP slaves 7-49Constant values

Interconnect 5-24Continuation connector 5-21, 5-22

Creating the interface DBfrom a global DB 7-51

Data access 1-16Data storage 7-78

SIMATIC iMap 5-43STEP 7 7-78

Data types 1-8, 7-73Interface DB 7-37PROFInet 7-73S7 7-73

Deactivating and reactivating entries 6-28Define the devices and their functions 3-2Deleting

iMap library 5-46iMap project 5-46

Device 1-4, 10-1Device-independent engineering concept 1-

12Device-specific configuration and

programming tools 1-15Diagnostic window 4-23Documentation (preview window) 4-20Download 6-8, 6-14

Targets 6-15DP slaves

Special features 7-48DP slaves with fixed functionality

Structure of the interface DB 7-48Drag-and-drop 4-6Editing objects 4-5Engineering concept

Basic procedure 1-13Device-independent 1-12

File structure 5-46iMap library 5-45iMap project 5-45

File types 8-13Filler element 7-40, 7-49, 10-1Find Instances 4-9Fixed functionality 1-5, 7-3functionality

Fixed 1-5Programmable 1-5

Functionality, fixed 10-1

Index

Component based AutomationIndex-2 A5E00122598-03

Functionality, programmable 10-1Generating SIMATIC iMap projects 5-7Generation

Consistency analysis 7-80Generation status 5-8, 6-16Global DB

Interface DB 7-39Icon 8-1Identification of the PROFInet component 7-

64Information window 4-27Initial values 7-37Input section

Interface DB 7-37Inserting PROFInet components 5-18Instance 4-9Instance DB

Interface DB 7-39Instance of a PROFInet component 5-18

Replacing 5-48Intelligent DP slave

Blocks required in S7 program 7-46Intelligent DP slaves

Exchange of data with DP master 7-45Interconnect

Constant value 5-24Interconnectable connectors 7-39Interconnecting technological functions 5-20Interconnection 5-21, 10-1

Rules 5-20Interconnection lines

Display 5-22Recalculate 5-23

Interconnections 1-8multiple 5-21

Interface DB 7-3, 7-36, 10-2Attribute 7-38Declaration line 7-36From an instance DB 7-59Initial values 7-37PROFInet device 7-53, 7-60programmable PROFIBUS device 7-61Programmable PROFIBUS device,

intelligent DP slave 7-54Interface DB for a PROFIBUS device

DP slave with fixed functionality 7-56Library 10-2Library window 4-18Lifestate 7-37, 7-74Local MPI bus 7-2, 7-3Local PROFIBUS 7-2

Logical device 6-12Main chart 10-2Major build version 7-76Master with proxy functionality 1-10Minor build version 7-76Modified PROFInet components 5-48Monitor variables online 6-28Moving objects 4-8MPI bus 7-3

Local 7-3Multiple interconnections 5-21Multiple selection 4-7Naming conventions 5-35Network chart 4-17Network tree 4-17Non-connectable connectors 7-39Object hierarchy 4-4, 4-5Object properties 4-6Object-oriented operation 4-3Objects

Selecting associated objects 4-9Offline view 6-1Online values

Validity 6-21Online view 6-1Online-offline comparison

SIMATIC devices 7-81OPC symbol file 5-49

Save as 5-49Opening a project 5-3Operating states

SIMATIC devices 7-82Output section

Interface DB 7-37Password for the project

Define 5-34password protection

Removing 5-34Password protection 5-34Plant tree 4-17Plant view 4-12, 10-2Preview window 4-20Product range 1-2PROFIBUS device 1-10, 1-11, 10-2

Representation in SIMATIC iMap 1-11PROFIBUS devices

Coupling 4-16PROFIBUS master

Proxy functionality 1-10PROFIBUS master functionality 3-2

Index

Component based AutomationA5E00122598-03 Index-3

PROFIBUS User Organisation e.V. (PNO) 1-1

PROFInet 1-1, 10-2PROFInet component 10-2

Basic project 5-43Component project 5-43Creation 1-4Device 1-4Shadow project 5-43Technological function 1-4With fixed functionality 7-3With programmable functionality 7-3

PROFInet componentsDefinition 1-3Properties 1-5Representation in SIMATIC iMap 1-6

PROFInet data types 1-8PROFInet device 1-10, 1-11, 10-2

Representation in SIMATIC iMap 1-10, 1-11

with proxy functionality 10-2PROFInet devices 7-1PROFInet library 7-70PROFInet specification 1-2, 1-5, 3-2PROFInet standard 1-1, 1-2, 1-3PROFInet-Standard 1-1Program download

SIMATIC devices 7-81Programmable functionality 1-5, 7-3Project

Generate 5-7Regenerate All 5-7

Project window 4-17, 10-2Properties of interconnections 5-21, 5-37Proxy functionality 1-10, 3-2, 10-2Quality of service 5-37Regenerating

the SIMATIC iMap project 7-85Regenerating a project 5-9, 7-79Replacing

Instance of a PROFInet component 5-48Reusability 3-2Rules for creating PROFInet components 3-2Search for objects 4-9Searching for objects 4-9Separator element 7-40, 10-2Setting the PG/PC interface 7-86, 7-87

STEP 7 7-86WinLC PN 7-87

Setting up tools 4-29Shadow project 5-7, 7-78, 10-3

STEP 7 7-78SIMATIC devices

Commissioning 7-76Special editing functions 7-83

SIMATIC iMap 1-2SIMATIC IMap 10-3SIMATIC iMap - STEP 7 AddOn 10-3Simultaneous access

iMap library 5-45iMap project 5-45

Special editing functionsSIMATIC devices 7-83

subordinate chartChart interface 5-41Create 5-41

Subordinate chart 5-41subordinate charts

Copy 4-7System components 7-50

PROFInet library 7-70Target groups 1-17technological function

Definition 1-7Technological function 1-4, 1-7, 10-3

Representation in SIMATIC iMap 1-9Technological functions

Move to a new chart 5-42Technological module 1-3Toolbar 8-1Totally Integrated Automation 1-1Transfer frequency 5-37

Default value 5-38Types of documentation 1-17Unconnected PROFIBUS devices 4-16User documentation 1-17

Target groups 1-17User interface

Overview 4-10Validity of online values 6-21Variable table

Moving entries 6-26Set Online Values 6-31Start monitoring 6-29

Version number 5-18, 7-64Automatically incrementing 7-76Major build version 7-76Minor build version 7-76PROFInet components 7-75

Windows 4-10Windows conventions 4-3WinLC PN

Index

Component based AutomationIndex-4 A5E00122598-03

as PROFIBUS master 7-82

simatic component based automation configuring plants with ... · component based automation...

Documents