Autom IBS Profinet E - Industry Support Siemens

Cover Sheet

Automatic Commissioning of a PROFINET IO System

PROFINET IO

Application Description July 2009

Applikationen & Tools

Answers for industry.

Warranty, Liability and Support

2 Autom_IBS_PROFINET

Version 1.0, Entry ID: 36741408

Warranty, Liability and Support Note The Application Examples are not binding and do not claim to be

complete regarding the circuits shown, equipping and any eventuality. The Application Examples do not represent customer-specific solutions. They are only intended to provide support for typical applications. You are responsible for ensuring that the described products are used correctly. These application examples do not relieve you of the responsibility to use sound practices in application, installation, operation and maintenance. When using these Application Examples, you recognize that we cannot be made liable for any damage/claims beyond the liability clause described. We reserve the right to make changes to these Application Examples at any time without prior notice. If there are any deviations between the recommendations provided in these application examples and other Siemens publications – e.g. Catalogs – the contents of the other documents have priority.

We do not accept any liability for the information contained in this document.

Any claims against us – based on whatever legal reason – resulting from the use of the examples, information, programs, engineering and performance data etc., described in this Application Example shall be excluded. Such an exclusion shall not apply in the case of mandatory liability, e.g. under the German Product Liability Act (“Produkthaftungsgesetz”), in case of intent, gross negligence, or injury of life, body or health, guarantee for the quality of a product, fraudulent concealment of a deficiency or breach of a condition which goes to the root of the contract (“wesentliche Vertragspflichten”). The damages for a breach of a substantial contractual obligation are, however, limited to the foreseeable damage, typical for the type of contract, except in the event of intent or gross negligence or injury to life, body or health. The above provisions do not imply a change of the burden of proof to your detriment.

Any form of duplication or distribution of these Application Examples or excerpts hereof is prohibited without the expressed consent of Siemens Industry Sector.

If you have any questions concerning this document please e-mail us to the following address:

[email protected]

mailto:[email protected]

Preface

Autom_IBS_PROFINET Version 1.0, Entry ID: 36741408 3

Preface

Objective of the application It is the objective of this application to introduce new PROFINET IO functions using an application example.

The functions introduced here are particularly useful when realizing

• frequently occurring configurations such as for serial machine construction

• large plants with very many PROFINET IO devices.

Main contents of this application The following topics are discussed in this application:

• Automatic commissioning of a PN IO system using a setpoint topology

• Exchanging a PROFINET IO device without removable storage medium

• Basics on LLDP and Topology Editor (e.g. online/offline comparison, views etc.).

Structure of this document The documentation of this application is divided into the following main parts.

Components Description Application Description This section provides a general overview of the

contents. You are informed on the used components.

Functional principles Provides a detailed description of the function processes of the hardware and software components involved.

Setup, configuration and operation of the application

This part leads you step by step through the structure, important configuration steps, commissioning and operation of the application.

Appendix This part of the documentation provides additional information such as e.g. bibliographic references, glossaries, etc.

Industry Automation and Drives Technologies Service & Support Portal This article is taken from the Service Portal of Siemens AG, Industry Automation and Drives Technologies. The following link takes you directly to the download page of this document.

http://support.automation.siemens.com/WW/view/en/36741408


1 Automation Task

2.1 Overview of the overall solution



Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

Table of Contents

Application Description ............................................................................................... 5

1 Automation Task ........................................................................................ 5

2 Automation Solution.................................................................................. 7

2.1 Overview of the overall solution........................................................................ 7

2.2 Advantages of this solution............................................................................... 8

2.3 Required hardware and software components ................................................. 9

Functional Principles ................................................................................................. 11

3 Functional Mechanisms .......................................................................... 11

3.1 Basics “Link Layer Discovery Protocol” (LLDP) .............................................. 11

3.2 SIMATIC Topology Editor ............................................................................... 13

3.3 Sequence “Automatic Commissioning of a PROFINET IO System”............... 17

3.4 Sequence of the device replacement without storage medium ...................... 22

Configuration and Operation of the Application ..................................................... 25

4 Commissioning of the Application Scenarios....................................... 25

4.1 Automatic commissioning of a PROFINET IO system.................................... 25 4.1.1 Reset devices to factory defaults.................................................................... 25 4.1.2 Create new project and hardware configuration ............................................. 29 4.1.3 Create topology .............................................................................................. 31 4.1.4 Connect hardware components using the setpoint topology .......................... 38 4.1.5 Download controller ........................................................................................ 38

4.2 Reading out existing configuration.................................................................. 43

4.3 Exchanging a PROFINET IO device............................................................... 46

5 Modifications and Error Scenarios......................................................... 48

5.1 Scenario “non-LLDP-capable device in the PROFINET IO system”............... 48

5.2 Error scenario “Actual and setpoint topology differ”........................................ 52

Appendix and List of Further Literature ................................................................... 54

6 Bibliography ............................................................................................. 54

6.1 Bibliographic References................................................................................ 54

6.2 Internet Links .................................................................................................. 54

7 History....................................................................................................... 54

1 Automation Task



Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

Application Description

1 Automation Task

In some automation cells such as for serial machine construction plant units appears with identic hardware configuration.

For simplification and shortening the commission process, the PROFINET IO system should be started up automatically without the device names being assigned to each device via PG or MMC card

Additionally a PROFINET IO device shall be exchanged without removable storage medium.

Requirements The requirements through the automation task are:

• The Use of Devices without MMC slot (sealed casing for IP 65)

• Device replacement without MMC

• Commissioning without name assignment via PG/MMC

Overview The following image shows the commissioning as it has taken place up to now. Figure 1-1

IO-Controller

Assign device namesDownload configuration

1 Automation Task




Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

The figure below provides an overview of the commissioning process with the new function. Figure 1-2

IO-Controller

Download configuration

2 Automation Solution



Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c



The PROFINET IO function “Automatic addressing of I/O devices during commissioning” fulfils all requirements of the automation task.

A setpoint topology is generated during the configuration and only downloaded on the PROFINET IO controller. The PROFINET IO devices are named during startup on the basis of the setpoint topology.

In case of an error e.g. one I/O device is defective, this component can be simply replaced. The controller allocates its name automatically.

Schematic layout The following figure illustrates the components used in the setup of this function. Figure 2-1

P1 P1

P2

P3

P4

P5

P6

P7

P8

P1 P2 P1

P1 P2 P1

ET 200SSCALANCE X208CPU319-3DP/PN ET 200M

ET 200proET 200eco PN

P2 P1

ET 200eco PN

Configuration The PROFINET IO Controller is a 319-3DP/PN CPU. As PROFINET IO devices the following components are used:

• SCALANCE X208

• ET 200S

• ET 200M

• ET 200pro

• ET200eco PN


2.2 Advantages of this solution



Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

Note Which module supports the automatic commissioning is available in point \1\ of the appendix.

Scenarios The following scenarios are discussed in this application: Table 2-1

No Scenario Description

1. Automatic commissioning of a PROFINET IO system

The user generates the setpoint topology with the Topology Editor and then downloads it on the IO controller. The commissioning of the IO devices is taking place automatically.

2. Reading out existing configuration The user has the option to adopt the online topology from existing configurations in the project. This topology can be used for other projects with identical topology.

3. Exchanging a PROFINET IO device If an IO device fails the user should simply replace the IO device. The device is automatically commissioned.

4. Scenario “non-LLDP-capable device in the PROFINET IO system”

This scenario describes the behavior of the system during automatic commissioning if a component does not support this PROFINET function.

5. Scenario “actual and setpoint topology differ”

This scenario describes the behavior of the system if the configured and the online topology are not identical.

2.2 Advantages of this solution

• Commissioning a PROFINET IO system is simplified.

• Time saving and reduction of error sources during commissioning.

• For serial machines the device names need no longer be explicitly burned to storage media.

• Exchanging the PROFINET IO device without removable storage medium.


2.3 Required hardware and software components


Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c


Hardware components Table 2-2

Component Quantity MLFB / order number Note Power supply PS307 5A

2 6ES7307-1EA00-0AA0

CPU 319-3PN/DP 1 6ES7318-3EL00-0AB0 As of V2.7 Micro Memory Card 64kB (or larger)

1 6ES7 953-8LF20-0AA0

ET 200S: Interface module IM 151-3PN

1 6ES7 151-3AA23-0AB0 as of V6.0

Power module PM-E DC 24V

1 6ES7 138-4CA01-0AA0

Digital input module for ET200S 4 DI DC 24V

1 6ES7 131-4BD01-0AA0

Digital output module for ET200S/ 4 DO DC 24V/0.5A

1 6ES7 132-4BD02-0AA0

Terminal modules for power modules

1 6ES7 193-4CD30-0AA0

Terminal modules for electronic modules

2 6ES7 193-4CB20-0AA0

ET 200M: IM 153-4 PN 1 6ES7 153-4AA01-0XB0 as of V2.0 SM 323 1 6ES7 323-1BH01-0AA0 ET 200pro: IM 154-4 PN HF 1 6ES7 154-4AB10-0AB0 as of V6.0 Connection module CM IM PN M12

6ES7 194-4AJ00-0AA

Electronic module EM 141, 8 DI

1 6ES7 141-4BF00-0AA0

Connection module For digital electronic modules

1 6ES7 194-4CB00-0AA0

ET 200eco PN 1 6ES7142-6BF00-0AB0 8 D0, as of V6.0 ET 200eco PN 1 6ES7141-6BF00-0AB0 8 DI, as of V6.0 SCALANCE X208 1 6GK5 208-0BA10-2AA3 SCALANCE X108 1 6GK5 108-0AB00-1AA3 IE FC M12 Plug 5 6GK1 901-0DB20-6AA0





Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

Component Quantity MLFB / order number Note PRO IE FC RJ45 PLUG 7 6GK1 901-1BB10-2AA0 IE FC TP STANDARD CABLE

6XV1 840-2AH10 Meter ware

IE FC stripping tool, insulation tool

1 6GK1 901-1GA00

Power Plug Pro 1 6GK1 907-0AB10-6AA0 IE Power M12 Cable Connector pro

1 6GK1907-0DC10-6AA3

Standard software components Table 2-3

Component Quantity MLFB / order number Note STEP 7 V5.4 SP4 1 6ES7 810-4CC08-0YA5 Or higher

version

Note For installation and mounting of the components please note the descriptions and manuals as well as delivery information which are delivered with the respective products.

3 Functional Mechanisms

3.1 Basics “Link Layer Discovery Protocol” (LLDP)


Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

Functional Principles



Introduction The functions “Device replacement without storage medium” and “Automatic commissioning of a PROFINET IO systems” is based on the LLDP protocol.

The LLDP (Link Layer Discovery Protocol) is a producer independent layer 2 protocol which enables the neighbor devices to inter-exchange information.

Principle All devices are connected and arrange a neighbor relationsship.

Via these Ethernet ports each device sends LLDP packages with information on itself to the neighbor devices and receives their information. This occurs in periodic intervals.

The LLDP protocol is referred to as “one-way protocol”. The sending and receiving processes work independent of each other. After sending the response of the partner is not waited for.

The LLDP packages are sent to the target address 01:80:2C:00:00:0E with the Ethernet type identifier 0x88CC. The packages which are sent to this address only reach the port of the direct neighbor device and are not forwarded. The received information is stored in the neighbor table (LLDP MIB Management Information Base) of the device.

These tables are read from the network management station using SNMP (e.g. STEP7 with the Topology Editor). The network management station can generate a topology representation.

Each connection point in the topology is uniquely identified via alias. A alias is made with the device identifier (MAC address or device name) and the port identifier (port number). Because of the MAC address, the alias only occur once in a network. That’s why STEP7 can uniquely determine the topology.





Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

In the following figure the topology setting is displayed via LLDP: Figure 3-1

P1 P1

P2

P3

P4

Topology request through STEP 73

P5

P6

P7

P8

PartnerID.PortID Info

X208.P1

Port

Port 1

Info

XXXPartnerID.PortID

CPU319-3PN/DP.P1

Port

Port 1

Info

XXX

I am “CPU319-3PN/DP“

I am “X208“1 1

LLDP MIBs are read out4

5 Topology representation

2 2

Table 3-1

No Description Additional information

1. Each device sends information about itself to its neighbor device.

Via LLDP

2. This information is stored in the neighbor table of the neighbor device.

The received information from the neighbor device is saved in the own table.

3. At topology query is started from STEP 7.

Via SNMP

4. The neighbor tables ( LLDP MIBs) are read out.

Via SNMP

5. Using the information from the neighbor tables the topology is generated and represented in the Topology Editor.


3.2 SIMATIC Topology Editor


Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c


Features The SIMATIC Topology Editor (as of STEP 7 V5.4 SP4) gives you the option of topologically configuring PROFINET IO systems.

The topology is configured by interconnecting the interfaces and ports.

The Topology Editor has the following functions and properties:

• Display of all PROFINET devices and their ports in the project

• Configured line length and configured line type with calculated signal runtime for each port

• Interconnection data with location identifier of the individual PROFINET devices

• Diagnostic information of PROFINET devices for each individual port

• Simple error detection through online/offline comparison of the node data

• Calling the diagnostics (module status) from the graphical view

• Importing the network topology





Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

Table view In the table view all configured PROFINET devices with their ports and their interconnections are listed. The topology can be exported as layout plan. Figure 3-2




Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

Graphic view In the graphic view, the PROFINET devices and their interconnections are represented graphically. It is also possible to print the graphical topology. Figure 3-3





Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

Online/offline comparison In the online/offline comparison, both offline and online topologies are displayed. There is the option to adopt the offline topology in the project via the offline/online comparison. Figure 3-4


3.3 Sequence “Automatic Commissioning of a PROFINET IO System”


Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c


The function “Automatic commissioning of a PROFINET IO system” is based on the LLDP protocol. Especially with the commission of serial machine construction with identic configuration and setpoint topology this function is particularly important: the time expenditure and possible error causes during commissioning reduce

Features

With this function the IP address and device names of the PROFINET IO devices are automatically assigned by the respective PROFINET IO controller, without requiring

• a removable storage medium (e.g. Micro Memory Card) with stored device name or

• a programming device (PG).

Requirements

The following requirements apply for automatic commissioning:

• The IO controller and the IO devices must support the PROFINET functionality “Device replacement without removable storage medium/PC”. A list with these devices is available in \1\ .

• During the configuration with STEP7 the option "Device replacement without removable storage medium" must have been selected in the controller.

• The devices must be reset to delivery state.

• The topology of the PROFINET IO systems with the respective IO devices must be configured.

• The configured setpoint topology must be identical with the actual topology.

Principle The topology of the PROFINET IO system is configured offline. Using this setpoint topology the neighbor relationships of all PROFINET IO devices located in the PROFINET IO system are reported to the PROFINET IO controller.

From the neighbor relationships given by the setpoint topology and the actual neighbor relationships determined by the real PROFINET devices via LLDP, the IO controller can identify the IO devices without names and assign the configured name and IP address to them.





Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

The following figure shows the functional sequence of an automatic commissioning.

Step 1: The devices are physically connected with each other. Since the IO devices have no name yet, each IO device sends its own MAC address and port number for each neighbor relation to their neighbors. This information are stored in the neighbor table of the neighbor device.

Figure 3-5

P1 P1

P2

P3

P4

P5

P6

P7

P8

P1 P2 P1

P1 P2 P1 P2 P1

- - -

PartnerMAC.P2

PartnerMAC.P1

- - -

PartnerMAC.P2

- - -

PartnerMAC.P1

PartnerMAC.P1

PartnerMAC.P1

- - -

PartnerMAC.P5

PartnerMAC.P1

- - -

PartnerMAC.P2

PartnerMAC.P1

Device Name

PartnerMAC.PartnerPort

Neighbor table

Port 1

Port 2

Port 5

Port 1

Port 2

Port

Port 1

Port 2

Port 1

Port 2

Port 2

- - -

PartnerMAC.P2Port 1




Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

Step 2: The setpoint topology is downloaded to the IO controller. Using the setpoint and actual topology the IO controller can identify the devices and assign the configured name and IP address to them. Table 3-2

Bild Description

2a After the IO controller has been downloaded it has the setpoint topology information for all neighbor relationships in the PROFINET IO system.

2b The IO controller has already had a name assigned to it after downloading the configuration. It then sends its name and information about itself to its neighbor devices. In this case to the SCALANCE X208. This information is stored in the neighbor table of the SCALANCE X208.

2c In the IO controller this unique neighbor relationship (referred to as alias) is compared with the information located in the topology table. The device has its port 1 connected to port 1 of the CPU has the name “X208”. This name is then assigned to the SCALANCE X208.

Figure 3-6

PROFINET IO Controller Topology info

P1 P1

P2

P3

P4

P5

P6

P7

P8

- - -

PartnerMAC.P1

PartnerMAC.P1

PartnerMAC.P1

Port 1

Port 2

Port 5

X208

CPU319-3PN/DP.P1

ET200ecoPN-DO.P1

ET200S.P1

Port 1

Port 2

Port 5

ET200S

X208.P5

ET200M.P1

Port 1

Port 2

ET200M

ET200S.P2Port 1

ET200ecoPN-DI

ET200pro.P2Port 1

ET200pro

ET200ecoPN-DO.P2

ET200ecoPN-DI.P1

Port 1

Port 2

ET200ecoPN-DO

X208.P2

ET200pro.P1

Port 1

Port 2

- - -

CPU319-3PN/DP.P11

PartnerMAC.P1

PartnerMAC.P1

Port 1

Port 2

Port 5

P1 P1

P2

P3

P4

P5

P6

P7

P8

2a 2b

X208

CPU319-3PN/DP.P1

PartnerMAC.P1

PartnerMAC.P1

Port 1

Port 2

Port 5

P1 P1

P2

P3

P4

P5

2c

P6

P7

P8





Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

Step 3: After the SCALANCE X208 now has a name it sends the information itself to its neighbor devices (in this example to the ET 200S and the ET 200eco PN-DO). This information is stored in the neighbor table of the neighbor devices. Figure 3-7

X208

CPU319-3PN/DP.P11

PartnerMAC.P1

PartnerMAC.P1

Port 1

Port 2

Port 5

P1

P2

P3

P4

P5

P6

P7

P8

P1 P2

- - -

X208.P2

PartnerMAC.P1

Port 1

Port 2

P1 P2

- - -

X208.P5

PartnerMAC.P1

Port 1

Port 2

Using this information and the topology information stored in the controller, the controller identifies the IO devices and assigns names to them. After the devices have received their names they send that name to their partner.

In the same principle the entire PROFINET IO system is put to operation.




Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

Figure 3-8

P1 P1

P2

P3

P4

P5

P6

P7

P8

P1 P2 P1

P1 P2 P1 P2 P1

Device Name

Partner Device Name .PartnerPort

Neighbor table

Port

X208

CPU319-3PN/DP.P1

ET200ecoPN-DO.P1

ET200S.P1

Port 1

Port 2

Port 5

ET200S

X208.P5

ET200M.P1

Port 1

Port 2

ET200M

ET200S.P2Port 1

ET200ecoPN-DI

ET200pro.P2Port 1

ET200pro

ET200ecoPN-DO.P2

ET200ecoPN-DI.P1

Port 1

Port 2

ET200ecoPN-DO

X208.P2

ET200pro.P1

Port 1

Port 2


3.4 Sequence of the device replacement without storage medium



Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c


This chapter describes the sequence of a device replacement without storage medium. In this example we assume that the device ET 200ecoPN-DI is defective and must be replaced.

Figure 3-9

P1 P1

P2

P3

P4

P5

P6

P7

P8

P1 P2 P1

P1 P2 P1 P2 P1

X208

CPU319-3PN/DP.P1

ET200ecoPN-DO.P1

ET200S.P1

Port 1

Port 2

Port 5

ET200S

X208.P5

ET200M.P1

Port 1

Port 2

ET200M

ET200S.P2Port 1

ET200ecoPN-DI

ET200pro.P2Port 1

ET200pro

ET200ecoPN-DO.P2

ET200ecoPN-DI.P1

Port 1

Port 2

ET200ecoPN-DO

X208.P2

ET200pro.P1

Port 1

Port 2

Step 1: If the device is disconnected from the PROFINET IO system the neighbor device, in this case ET 200pro, will notice. Since the ET 200pro does no longer receive any LLDP packages from the ET 200eco PN, the alias in their neighbor table is empty.




Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

Figure 3-10

P1 P1

P2

P3

P4

P5

P6

P7

P8

P1 P2 P1 P2

ET200pro

ET200ecoPN-DO.P2

- - -

Port 1

Port 2 Step 2:

The defective module is replaced with a new module. If the user connects the substitute device it has no name at first. However, the LLDP protocol already runs and the ET 200pro sends the information about itself to the new ET 200eco PN. For this reason the alias for the connection to ET 200pro is already contained in the neighbor table of the ET 200eco PN. Figure 3-11

P1 P1

P2

P3

P4

P5

P6

P7

P8

P1 P2 P1 P2

ET200pro

ET200ecoPN-DO.P2

- - -

Port 1

Port 2

P1

- - -

ET200pro.P2Port 1

Substitute device





Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

Step 3: Using this alias, which is unique for every connection, and the topology information stored in the controller the controller can identify the new IO device and assigns its name to it as illustrated in the figure below.

Figure 3-12

P1 P1

P2

P3

P4

P5

P6

P7

P8

P1 P2 P1 P2

ET200pro

ET200ecoPN-DO.P2

- - -

Port 1

Port 2

P1

Substitute device

ET200ecoPN-DI

ET200pro.P2Port 1

PROFINET IO Controller Topology info

X208

CPU319-3PN/DP.P1

ET200ecoPN-DO.P1

ET200S.P1

Port 1

Port 2

Port 5

ET200S

X208.P5

ET200M.P1

Port 1

Port 2

ET200M

ET200S.P2

ET200ecoPN-DI

ET200pro.P2Port 1

Port 1

ET200pro

ET200ecoPN-DO.P2

ET200ecoPN-DI.P1

ET200ecoPN-DO

X208.P2

ET200pro.P1

Port 1

Port 2

Port 1

Port 2

This sequence occurs within few seconds and is transparent for the user.

The new station runs automatically without the user having to do anything. The IP address of the device is determined automatically. Unlike for PROFIBUS systems, the user needs not set an address.

4 Commissioning of the Application Scenarios

4.1 Automatic commissioning of a PROFINET IO system


Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

Configuration and Operation of the Application


This chapter discusses the following scenarios: Table 4-1

No Scenario Chapter

1. Automatic commissioning of a PROFINET IO system 4.1 2. Reading out existing configuration 4.2 3. Exchanging a PROFINET IO device 4.3


Configuration of the PROFINET IO system requires the following steps: Table 4-2

No Action steps Chapter

1. Reset devices to factory defaults 4.1.1 2. Create new project and hardware configuration 4.1.2 3. Create topology 4.1.3 4. Connect hardware components using the setpoint topology 4.1.4 5. Download controller 4.1.5

4.1.1 Reset devices to factory defaults

If your components are new you proceed with step 2 in chapter 4.1.2.

If the RPOFINET IO devices have already been configured for other reset them to factory settings as follows:

Table 4-3

No Action Comment 1. Via Ethernet you connect your PG to the

device you wish to reset.

2. Open SIMATIC Manager via Start-> SIMATIC-> SIMATIC Manager.

3. Ensure that the PG/PC interface has been set to TCP/IP.





Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

No Action Comment 4. If this is not the case change the PG/PC

Interface via Options-> Set PG/PC Interface...

5. Select the TCP/IP option with your network card and acknowledge with OK.

6. Open the window with the Ethernet properties via PLC -> Edit Ethernet Node...




Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

No Action Comment 7. Click on Browse .

8. Select the device and acknowledge with OK.

9. Click on Reset in the Edit Ethernet Node window.





Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

No Action Comment 10. Acknowledge warning with Yes .

11. The device has now been reset to factory defaults. Press OK to close the window.

12. Repeat steps 1-11 for all PROFINET IO devices.

13. Close the window with Close if all required devices have been reset.

Note When using MMCs please delete them in your PG since at activated device replacement and plugged MMC the name on the MMC leads.




Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

4.1.2 Create new project and hardware configuration

Table 4-4

No Action Comment 1. In the SIMATIC Manager you create a

new project via File -> New .

2. Add a SIMATIC 300 station to the project name using the right mouse button-> Insert New Object .

3. Select the SIMATIC 300 station. Open HW-Config by double-clicking Hardware.

4. Add the RACK-300 Rail and the 319-3PN CPU.

This components you will find in the catalog profile under SIMATIC 300.

5. The window with the Ethernet properties of the CPU opens. Enter your desired IP address and Subnet mask. Then click New to generate a new Industrial Ethernet subnet. Acknowledge all windows with OK.

6. The PROFINET IO string has been added to HWConfig.





Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

No Action Comment 7. PROFINET IO contains the IO devices.

Add all devices using the order number in the configuration.

8. Double-click the SCALANCE X 208 to open the object properties.

9. Enter your desired IP address and device name.

10. Repeat step 8 and 9 for all devices. The hardware configuration looks as in Figure 4-1.

Figure 4-1

The following table contains the overview of all used IP addresses and device names in this example. Table 4-5

Component IP Address Device name

PG 192.168.0.100 IP address for the configuration

(no PROFINET IO device)

CPU 319-3 PN/DP 192.168.0.1 PN-IO SCALANCE X208 192.168.0.2 X208 ET 200S 192.168.0.3 ET200S ET 200M 192.168.0.4 ET200M ET 200eco PN 192.168.0.5 ET 200ecoPN-DO ET 200pro 192.168.0.6 ET200pro ET 200eco PN 192.168.0.7 ET200ecoPN-DI

The subnet mask in all network components is 255.255.255.0.




Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

4.1.3 Create topology

The topology can be configured via 3 different routes.

• In the table view of the Topology Editor

• In the graphical view of the Topology Editor

• In HW Config

Preparation

No Action Comment 1. At the PROFINET IO controller (CPU

319-3 PN/DP) you double-click PN-IO to open the PN-IO properties.

2. Ensure that the option Support device

replacement without exchangeable medium has been selected. Enter your desired device name. (see table 5-5)

Note: This option is selected by default.





Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

Generate topology in the table view Table 4-6

No Action Comment 1. Select the option PROFINET IO

Topology with the right mouse-button on PN-IO. The Topologie Editor opens.

2. In this example the PN-IO port of the CPU319-3PN/DP shall be connected with port 1 of the SCALANCE X208.

3. In the Table view you click the port of the CPU319-3PN/DP with the right mouse-button. Then select the option Object Properties.

4. The window with the port properties

opens. Go to the Topology tab.




Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

No Action Comment 5. Select the port of the partner to which you

wish to connect the CPU. In this case port 1 of the SCALANCE X208. Acknowledge with OK.

6. The connection can be seen in the Table view. The connected ports are displayed with green color

7. The filter gives you the option of only

displaying the connected ports.





Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

Generate topology in the graphic view Table 4-7

No Action Comment 1. Go to Graphic view.

Here the port connections are displayed graphically.

2. Port 1 of the ET 200S shall be connected

with port 5 of the SCALANCE X208.

3. Click port 1 of the ET 200S with the left mouse-button and keep it pressed while drawing a line up to the SCALANCE X208 port 5. The port connection has been configured.




Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

Create topology in HW Config Table 4-8

No Action Comment 1. Port 2 of the ET 200S shall be connected

to port 1 of the ET 200M

2. Select the ET 200S

3. Click port 2 with the right mouse-button

and select the Object Properties… option.

4. The window with the port properties

opens. Go to the Topology tab.





Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

No Action Comment 5. Select the port of the partner to which you

wish to connect the ET 200S, in this case port 1 of the ET 200M and acknowledge with OK.

6. When opening the Topology Editor you can see this connection in the Table view or in the Graphic view.




Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

Export/print topology Table 4-9

No Action Comment 1. Create the topology for all devices in the

project either in the Table view or in the Graphic view .

2. Using the cursor you can enlarge or reduce the image. You can also change the location of the devices.

3. After you have created the topology there

is the option to print it via the Print button.

4. Go to Table view. You can export the topology via the Export button. The exposed file can be opened with Excel and be used as layout plan.





Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

4.1.4 Connect hardware components using the setpoint topology

After the topology has been created and exported from the Topology Editor or printed as a plan you can then connect the devices.

Table 4-10

No Action Comment 1. Connect the hardware component using

the topology which you have exported or printed from the Topology Editor.

Note: It is important that you connect the correct ports which are configured in STEP 7.

4.1.5 Download controller

As last step, the topology shall be downloaded to the controller. The IP address of the controller and the computer must be set.

Assign IP address of the controller Table 4-11

No Action Comment 1. Connect the computer to one of the free

ports of the SCALANCE X208.

2. Open the window with the Ethernet properties via PLC -> Edit Ethernet Node...

3. Click on Browse .




Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

No Action Comment 4. Select the device S7-300 with the left

mouse-button and acknowledge with OK.

5. Assign the IP address as shown in the screenshot. Then click on Assign IP Configuration. Close the window with Close .





Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

Set IP address of the computer Table 4-12

No Action Comment 1. Open the Internet Protocol (TCP/IP)-

Properties via Start -> Settings -> Network Connection ->Local Connections Select the options field Use following IP-address and fill in the field according to the screenshot on the right. Close the dialog boxes with “OK”.

Download controller Table 4-13

No Action Comment 1. In HWConfig you click on the

CPU 319-3PN/DP and then on the download symbol.




Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

No Action Comment 2. Click on OK in the window which has

been opened. This starts the download to the CPU. Acknowledge all windows with OK.

Test automatic commissioning Table 4-14

No Action Comment 1. After the PROFINET IO controller has

been downloaded and the devices have been started up you observe your PROFINET IO system.

You will notice that one station after the other receives data from the controller. The SF LED to the devices goes out.

2. Check the function by searching via Nodes accessible online. All PROFINET IO devices have been displayed. The devices automatically have a name and IP address assigned to them.

Alternatively, you can also the “Verify device name” function. Table 4-15

No Action Comment 1. Select the PROFINET network.

2. Open PLC-> Ethernet-> Verify Device Name.





Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

No Action Comment 3. The PROFINET IO devices are displayed

with name and IP address.

Note In your program you add the required organization blocks so the CPU does not go to STOP mode when the distributed IO fails.

Information on these blocks are available chapter \3\ of the appendix.


4.2 Reading out existing configuration


Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c


For already existing configurations there is the option to adopt the online topology in the project in order to then also use it for other projects with identical topology.

Table 4-16

No Action Comment 1. Open HWConfig.

At the PROFINET IO controller double-click PN-IO to open the PN-IO properties.

2. Ensure that the option Support device

replacement without exchangeable medium has been selected.

3. Download the controller as described in chapter 4.1.5.

4. Connect your computer to one of the free ports of the SCALANCE X208. (Port 7 was used for this demo.)

5. Open the Topology Editor. Go to the Graphic view tab. Since no topology has been created yet no port connections have been indicated. Go to Offline/Online Comparison tab.





Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

No Action Comment 6. In the left window pane you see the

offline topology. All devices are shaded in orange since no comparison has occurred yet. In the right window the online topology is displayed. (Since no comparison has occurred yet this field is empty.) Click Start to start the comparison.

7. The ports in the left and right window are

displayed in yellow since the offline and online configuration is not identical.

8. Clicking (+) opens the ports of the device.

Select a port of the determined (online) topology which has been topologically connected e.g. port 1 of the ET 200eco PN-DI module.

9. Subsequently select with <Strg A> the

whole online topology.Click on Apply to adopt all online connections in the offline project.




Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

No Action Comment 10. The online topology has therefore been

adopted in the project. All devices are displayed green (except of the configuration computer). This means the offline and the online configuration is identical.

11. Go to the Graphic view tab. Here the

connections are also graphically displayed.


4.3 Exchanging a PROFINET IO device



Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c


The functions of PROFINET IO contain the option of exchanging a PROFINET IO device by connecting the substitute device at the location of the defective device.

This chapter additionally gives the diagnostics options with the Topology Editor.

Table 4-17

No Action Comment 1. Via the Online function in Table view the

status of the PROFINET IO devices can be seen.

2. This function is also available in the

Graphic view tab.

3. If a device has not been connected or is

defective, it is displayed red in the Graphic View (see screenshot). In the CPU the BF 3 LED flashes ad the SF LED is on.

Note: Please download the OB86 in the CPU. With this block you avoid the CPU-STOP if a module is defective.

4. Substitute the defective device with the substitute device.

Note: The substitute device must have been reset to factory settings.

5. Through the configuration of the device




Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

No Action Comment replacement without removable storage medium the new device is automatically started up after several seconds. The LEDs SF and BF 3 of the CPU go out. In the Topology Editor all devices are displayed green again.

5 Modifications and Error Scenarios

5.1 Scenario “non-LLDP-capable device in the PROFINET IO system”



Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c



The following scenario describes the behavior of the system during automatic commissioning if a component does not support this PROFINET function. (Here a SCALANCE X108 is used) To start up the IO devices in this case a device must have the configured device name in each line. Then commissioning for the remaining device occurs automatically.

Table 5-1

No Action Comment 1. Reset all devices to factory settings as

described in chapter 4.1.1 .

2. In HWConfig you delete the SCALANCE X208. All port connections to the SCALANCE X208 are deleted.

3. Open the Topology Editor. In Passive

Components you find the SCALANCE X100 switches. Select the SCALANCE X108 while keeping the mouse-button pressed and draw it to your topology.

4. Create the missing port connections to

SCALANCE X108.

5. Connect the hardware components with the SCALANCE X108 using the setpoint topology.

Note: Since the SCALANCE X108 does not support PROFINET functions other ports can also be used instead of the configured ports.


7. Monitor your PROFINET IO system. You see that the IO device are not automatically started up since the BF LED is flashing.




Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

No Action Comment 8. Via Nodes accessible online all

PROFINET IO devices are displayed. Only the IO controller has a name assigned to it after CPU download. The IO devices have no name and IP address automatically assigned to them.

9. To start up the IO devices in this case a device must have the configured device name in each line. For example, the ET 200pro and the ET 200M in this configuration. Select the ET 200pro module and acknowledge with OK.

10. In HWConfig open the ET 200pro properties by double-clicking this module. Copy the device name.





Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

No Action Comment 11. Go to the still opened Edit Ethernet

Node window. Enter the name for this module and click on Assign Name.

12. Monitor your PROFINET IO system. The IO devices which are at the same line as the ET200pro are automatically started up.

13. Repeat steps 9-12 for ET 200M. The ET 200S is automatically started up.




Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

No Action Comment 14. Open the Topology Editor. Go to Graphic

View and click Online. All PROFINET IO devices are displayed bright green. SCALANCE X108 does not support PROFINET which is why the Ethernet connections with SCALANCE X108 are displayed dark green.


5.2 Error scenario “Actual and setpoint topology differ”



Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c


The following scenario describes the behavior of the PROFINET IO system when the online port connections are not identical with the configured connections.

Table 5-2

No Action Comment 1. Reset all devices to factory settings as

described in chapter 4.1.1 .

2. Connect the modules as described in chapter 4. Exchange the Ethernet cables at the ET 200pro Ports .


4. Monitor your PROFINET IO system. All PROFINET IO devices are automatically started up except by the ET 200eco PN, which is connected after the ET 200pro in line. Additionally the SF LED lights for ET 200pro, ET 200eco PN-DO and CPU 319-3PN/DP.

5. Open HW Config and go to the online view.




Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

No Action Comment 6. Double-click on one of the devices

displayed with red circle an white cross inside, e.g. the ET 200eco PN-DI (device number 4). The Module Information window opens. Go to the Communication Diagnostics tab. The cause of the error is described. In this case the port of the partner connected at port 2 of the ET 200eco PN-DI is wrong.

7. The Module Information window for the ET 200pro indicates for both ports that the partner and the partner ports are wrong.

8. Check your hardware configuration and remove the error using this error description. In this example you connect the ports of the ET 200pro as in the configured configuration.

The ET 200eco PN is automatically started up. The SF LED of the ET 200pro and the other ET 200eco PN go out.

6 Bibliography



Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3674

1408

_Aut

om_I

BS_P

RO

FIN

ET_

e.do

c

Appendix and List of Further Literature

6 Bibliography

6.1 Bibliographic References

This list is by no means complete and only provides a selection of appropriate sources. Table 6-1

Topic Title /1/ ET 200eco PN ET 200eco PN Operating Instruction


/2/ ET 200pro ET 200pro Operating Instruction http://support.automation.siemens.com/WW/view/en/21210852

6.2 Internet Links

This list is not complete and only represents a selection of relevant literature. Table 6-2

Topic Title \1\ Which PROFINET nodes support the

automatic commissioning or the function device replacement without removable storage medium?


\2\ Siemens I IA Customer Support http://support.automation.siemens.com

\3\ Which organization blocks must be downloaded to the CPU to prevent it from going to STOP mode when the distributed IO fails.


\4\ PROFINET IO - Configuration & Diagnostics


7 History Table 7-1 History

Version Date Modification

V1.0 03.07.2009 First issue







http://support.automation.siemens.com/

http://support.automation.siemens.com/





Documents

Autom IBS Profinet E - Industry Support Siemens