application about communication - siemens€¦ · application about communication . diagnostic...

Application about Communication

Diagnostic Methods for PROFINET Network Components (PROFINET IO, SNMP, WBM) Volume 2: Diagnostics via SIMATIC NET CP (CP 343-1)

Application with Code

Application Description

0BTable of Contents

DIAG_NETWORK ID Number: 21566216

V2.0 08/30/07 2/38

Cop

yrig

ht ©

Sie

men

s A

G 2

007

All

right

s re

serv

ed

2156

6216

_DIA

G_N

ETW

OR

K_D

OK

U_B

AN

D2_

V20

_e.d

oc

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 correctly used. These Application Examples do not relieve you of the responsibility of safely and professionally using, installing, operating and servicing equipment. When using these Application Examples, you recognize that Siemens 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 – then the contents of the other documents have priority.

Warranty, liability and support

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”). However, claims arising from a breach of a condition which goes to the root of the contract shall be limited to the foreseeable damage which is intrinsic to the contract, unless caused by intent or gross negligence or based on mandatory liability for injury of life, body or health. The above provisions do not imply a change in the burden of proof to your detriment.

Copyright© 2007 Siemens A&D. It is not permissible to transfer or copy these Application Examples or excerpts of them without first having prior authorization from Siemens A&D in writing. For questions about this document please use the following e-mail address:

mailto:[email protected]

mailto:[email protected]


0BTable of Contents


V2.0 08/30/07 3/38

Cop

yrig

ht ©

Sie

men

s A

G 2

007

All

right

s re

serv

ed

2156

6216

_DIA

G_N

ETW

OR

K_D

OK

U_B

AN

D2_

V20

_e.d

oc

Foreword

Objective of the application This document is based on Volume 1 of the PROFINET diagnostics application and shows how the PROFINET diagnostic capabilities explained in Volume 1 can be realized via a CP as a PROFINET controller.

Note Volume 1 is available as a separate document on the download page of this document.

Main contents of this application The focus of this volume is on the configuration of the diagnostics via a CP as a PROFINET controller and on the necessary changes compared to Volume 1. For basic information on the different diagnostic capabilities (PROFINET IO, SNMP, WBM), the configuration with STEP 7 and the integration of the PROFINET devices, please refer to Volume 1.

The following main points are described in this application:

• Configuring ALARM S messages.

• Reading out and evaluating received diagnostics information with the aid of the FB 54 PROFINET alarm function block.

• Reading and writing data records with a CP as a PROFINET controller.


0BTable of Contents


V2.0 08/30/07 4/38

Cop

yrig

ht ©

Sie

men

s A

G 2

007

All

right

s re

serv

ed

2156

6216

_DIA

G_N

ETW

OR

K_D

OK

U_B

AN

D2_

V20

_e.d

oc

Delimitation This application does not include a description of

• the SIMATIC STEP 7 engineering tool

• the WinCC flexible visualization software

• SNMP (Simple Network Management Protocol)

• PROFINET IO

Basic knowledge of these topics is required.

Reference to Automation and Drives Service & Support This entry is from the internet application portal of Automation and Drives Service & Support. The link below takes you directly to the download page of this document.

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



0BTable of Contents


V2.0 08/30/07 5/38

Cop

yrig

ht ©

Sie

men

s A

G 2

007

All

right

s re

serv

ed

2156

6216

_DIA

G_N

ETW

OR

K_D

OK

U_B

AN

D2_

V20

_e.d

oc

Table of Contents

Application Description ............................................................................................... 6

1 Automation Problem ...................................................................................... 6 1.1 Overview........................................................................................................... 6 1.2 Requirements ................................................................................................... 6

2 Automation Solution ...................................................................................... 7 2.1 Overview of the overall solution........................................................................ 7 2.2 Required hardware and software components ................................................. 9 2.3 Alternative solutions........................................................................................ 11

Principles of Operation and Program Structures .................................................... 12

3 Functional Mechanisms of this Application............................................... 12 3.1 User interface to the CPU............................................................................... 12 3.1.1 Data transfer with FC 11................................................................................. 13 3.1.2 Data acceptance with FC 12........................................................................... 14 3.2 Evaluation of diagnostic alarms ...................................................................... 15 3.3 Display of messages....................................................................................... 17

4 Explanations of the Example Program ....................................................... 22 4.1 Configuration explanations for “ALARM_S”.................................................... 22 4.2 Explanations of the STEP 7 program ............................................................. 26

Structure, Configuration and Operation of the Application ................................... 34

5 Installation and Startup................................................................................ 34 5.1 Hardware and software installation................................................................. 34 5.2 Application software installation...................................................................... 36

6 Configuration ................................................................................................ 37

Appendix and Literature ............................................................................................ 38

7 Literature ....................................................................................................... 38 7.1 Bibliographic references ................................................................................. 38

Application Description1BAutomation Problem


V2.0 08/30/07 6/38

Cop

yrig

ht ©

Sie

men

s A

G 2

007

All

right

s re

serv

ed

2156

6216

_DIA

G_N

ETW

OR

K_D

OK

U_B

AN

D2_

V20

_e.d

oc


1 Automation Problem

1.1 Overview

Description of the automation problem The problem of this application is to realize the automation task described in Volume 1 using a CP as a PROFINET controller. All requirements, options and additional tasks are to be adapted to operation with a communications processor.

1.2 Requirements

Changes of the diagnostics requirement • Display of Alarm S messages on a PC with WinCC flexible Runtime

Changes of the user software requirement • Programming the PROFINET alarm FB (FB 54) for evaluating the

PROFINET IO diagnostic alarms.

• Integrating the PROFINET IO communication blocks (FC11/ FC12) for handling the data traffic between S7 CPU and S7 CP.

Application Description2BAutomation Solution


2 Automation Solution

2.1 Overview of the overall solution

Diagrammatic representation The following figure schematically shows the most important components of the solution:

Figure 2-1

V2.0 08/30/07 7/38

Cop

yrig

ht ©

Sie

men

s A

G 2

007

All

right

s re

serv

ed

2156

6216

_DIA

G_N

ETW

OR

K_D

OK

U_B

AN

D2_

V20

_e.d

oc



V2.0 08/30/07 8/38

Cop

yrig

ht ©

Sie

men

s A

G 2

007

All

right

s re

serv

ed

2156

6216

_DIA

G_N

ETW

OR

K_D

OK

U_B

AN

D2_

V20

_e.d

oc

Configuration • The following network stations are connected to the SCALANCE X208

switch via Industrial Ethernet:

– Port 1: CP 343-1 via the integrated Ethernet interface

– Port 2: Visualization PC via an Ethernet network card

– Port 5: SCALANCE X202-2P IRT

• The following network stations are connected to the SCALANCE X202-2P IRT switch via Industrial Ethernet and plastic optical fibers:

– Port 1: Optionally, a PC for port mirroring

– Port 2: SCALANCE X208

– Port 3: ET 200S PNFO via an IM 151-3 PN FO interface module with integrated optical-fiber interface

• The second ET 200S PNFO is connected to the first ET 200S PNFO (port 2) on port 1 (integrated optical-fiber interface).

• The first ET 200S PNFO is equipped with a power module and a digital output module.

• The second ET 200S PNFO is equipped with a power module and a digital input module.

• The signal contacts of the SCALANCEs can optionally be connected to a digital input module of the S7-300 station.



V2.0 08/30/07 9/38

Cop

yrig

ht ©

Sie

men

s A

G 2

007

All

right

s re

serv

ed

2156

6216

_DIA

G_N

ETW

OR

K_D

OK

U_B

AN

D2_

V20

_e.d

oc

2.2 Required hardware and software components

Hardware components Table 2-1

Component No. MLFB / order number Note PS 307 5A 1 6ES7 307-1EA00-0AA0 Alternatively, another

power supply can also be used.

CPU 315-2 DP 1 6ES7 315-2AG10-0AB0 Alternatively, another CPU can also be used.

CP343-1 1 6GK7 343-1EX30-0XE0 Micro Memory Card 1 6ES7 953-8LL11-0AA0 At least 2MB

for S7 CPU Micro Memory Card 2 6ES7 953-8LF11-0AA0 At least 64KB

for ET 200S PNFO SM322 digital output module 1 6ES7 322-1BH01-0AA0 DO 16x24VDC/0.5A SCALANCE X208 1 6GK5 208-0BA10-2AA3 Firmware version 2.1

or higher SCALANCE X202-2P IRT 1 6GK5 202-2BH00-2BA3 Firmware version 2.1

or higher IM151-3 PN FO 2 6ES7 151-3BB22-0AB0 Firmware version 5.0

or higher PM-E 24VDC 2 6ES7 138-4CA01-0AA0 Terminal module for power module

2 6ES7 193-4CD20-0AA0

DI HF digital electronic module

1 6ES7 131-4BD01-0AB0 Unit pack of 5

DO digital electronic module 1 6ES7 132-4BD01-0AA0 Unit pack of 5 Terminal module for electronic modules

2 6ES7 193-4CB20-0AA0 Unit pack of 5

Programming unit (PU) or PC with Ethernet network card, 100Mbps full duplex

2 Second PC only if you want to test port mirroring.

DIN rail 1 E.g. 6ES7 390-1AE80-0AA0

Length 480mm

Standard 35mm DIN rail 1 6ES5 710-8MA11 E.g., length 483mm



V2.0 08/30/07 10/38

Cop

yrig

ht ©

Sie

men

s A

G 2

007

All

right

s re

serv

ed

2156

6216

_DIA

G_N

ETW

OR

K_D

OK

U_B

AN

D2_

V20

_e.d

oc

Ethernet connecting cables Table 2-2

Component No. MLFB / order number Note

IE FC Standard Cable GP 2x2

1 6XV1 840-2AH10 Minimum order quantity: 20m

IE FC RJ45 Plug 180 6 6GK1 901-1BB10-2AA0 IE Stripping Tool 1 6GK1 901-1GA00 Stripping tool for

Ethernet cable

Fiber-optic cables Table 2-3

Component No. MLFB / order number Note

POF Standard Cable GP 980/1000

1 GXV1 874-2A Order quantity: Approx. 3m

IE SC RJ POF Plug 1 6GK1 900-0MB00-0AC0 20 per package Termination Kit SC RJ POF Plug

1 6GK1 900-0ML00-0AA0 Termination kit for POF SC RJ connectors.

Standard software components Table 2-4

Component No. MLFB / order number Note SIMATIC STEP 7 V5.4 SP 2 1 6ES7810-5CC10-0YC5 Or higher SIMATIC NET SOFTNET S7 LEAN 2006

1 6GK1704-1LW64-3AA0 Maximum of 8 connections The SIMATIC NET software is included in the delivery.

SIMATIC NET IE SNMP OPC SERVER BASIC/2006

1 6GK1706-1NW64-3AA0

SIMATIC WinCC flexible 2005 Advanced SP1 HF7

1 6AV6613-0AA01-1CA5

Network sniffer 1 E.g., Wireshark

Example files and projects The following list includes all files and projects that are used in this example.

Table 2-5

Component Note 21566216 _DIAG_NETWORK _CODE_BAND2_V20.zip This zip file contains the

STEP 7 project with integrated HMI station.

21566216_ DIAG_NETWORK_DOKU_BAND2_V20_e.pdf This document.

http://www.wireshark.org/



V2.0 08/30/07 11/38

Cop

yrig

ht ©

Sie

men

s A

G 2

007

All

right

s re

serv

ed

2156

6216

_DIA

G_N

ETW

OR

K_D

OK

U_B

AN

D2_

V20

_e.d

oc

2.3 Alternative solutions

S7 station Alternatively to the CPU 315-2 DP, another CPU can also be used.

Note When changing the specified module, the hardware configuration in STEP 7 has to be adjusted.

PROFINET controller Alternatively to a CP as a PROFINET controller, a PROFINET CPU can also be used.

Note The example with a CPU as a PROFINET controller is described in Volume 1 that is available as a separate document on the download page of this document.

Principles of Operation and Program Structures

3BFunctional Mechanisms of this Application



3 Functional Mechanisms of this Application

Note Fundamental principles concerning Ethernet and PROFINET IO, OPC server and SNMP are described in detail in Volume 1.

3.1 User interface to the CPU

The following functions are available for the data traffic between the user program of the CPU and the PROFINET devices via a CP as a PROFINET IO controller.

• PNIO_SEND (FC 11)

V2.0 08/30/07 12/38

Cop

yrig

ht ©

Sie

men

s A

G 2

007

All

right

s re

serv

ed

2156

6216

_DIA

G_N

ETW

OR

K_D

OK

U_B

AN

D2_

V20

_e.d

oc

• PNIO_RECV (FC 12)

In addition, the following function blocks for diagnostics exist:

• PNIO_RW_REC (FB 52) (not used in this application)

• PNIO_ALARM (FB 54)

The blocks are included in the SIMATIC_NET_CP library.

Schematic diagram The figure below shows a schematic representation of the data traffic between CPU and CP.

Figure 3-1

STEP 7 user program

Data block

PROFINET IO data area

S7-300 station

PNIO_RECV

PNIO_SEND

PROFINET IO interface

CPU CP - PROFINET controller

receive

send

PROFINET IO device

PROFINET IO interface

Process inputs

Process outputs




3.1.1 Data transfer with FC 11

FC 11 (PNIO_SEND) is used for transferring process data and is called in the user program. It transfers the process data (outputs) of a specified output range to the CP for forwarding to PROFINET IO devices.

Call interface The figure below shows the call of FC 11 in FBD representation: Figure 3-2

V2.0 08/30/07 13/38

Cop

yrig

ht ©

Sie

men

s A

G 2

007

All

right

s re

serv

ed

2156

6216

_DIA

G_N

ETW

OR

K_D

OK

U_B

AN

D2_

V20

_e.d

oc

The EN and EN0 parameters are only visible in the Graphic view.

Explanation of the formal parameters The formal parameters have the following meaning:

Table 3-1

Parameter Type Declaration Meaning

CPLADDR WORD INPUT CP start address LEN INT INPUT Length of the data area to be transferred

• Details of the largest configured address of the devices

• Transfer of the data in the order of the logical addresses

• The block starts the data transfer at output address 0 independently of your specific configuration of the output addresses

SEND ANY IN_OUT Data area to be transferred IOCS ANY OUTPUT Status bit(s); one status bit is transferred per

output byte DONE BOOL OUTPUT Status parameter; indicates the job status. ERROR BOOL OUTPUT Indicates an error of the block. STATUS WORD OUTPUT Status display CHECK_IOCS BOOL OUTPUT Help bit; indicates whether it is necessary to

check the IOCS status bits



DIAG_NETWORK ID Number: 21566216 3.1.2 Data acceptance with FC 12

FC 12 (PNIO_RECV) is used for accepting process data and is called in the user program. The block accepts the process data of PROFINET IO devices (controller inputs) and the IO provider status (IOPS) from the PROFINET IO devices to the specified input areas.

Call interface The figure below shows the call of FC 12 in FBD representation: Figure 3-3

V2.0 08/30/07 14/38

Cop

yrig

ht ©

Sie

men

s A

G 2

007

All

right

s re

serv

ed

2156

6216

_DIA

G_N

ETW

OR

K_D

OK

U_B

AN

D2_

V20

_e.d

oc



Table 3-2


CPLADDR WORD INPUT CP start address LEN INT INPUT Length of the data area to be transferred

• Details of the largest configured address of the devices

• Transfer of the data in the order of the logical addresses

• The block starts the data transfer at output address 0 independently of your specific configuration of the output addresses

RECV ANY IN_OUT Data area for received data IOPS ANY OUTPUT Status bit(s); one status bit is transferred per

input byte NDR BOOL OUTPUT Status parameter; indicates the job status. ERROR BOOL OUTPUT Indicates an error of the block. STATUS WORD OUTPUT Status display




V2.0 08/30/07 15/38

Cop

yrig

ht ©

Sie

men

s A

G 2

007

All

right

s re

serv

ed

2156

6216

_DIA

G_N

ETW

OR

K_D

OK

U_B

AN

D2_

V20

_e.d

oc


CHECK_IOPS BOOL OUTPUT Help bit; indicates whether it is necessary to check the IOPS status bits

ADD_INFO WORD OUTPUT Additional diagnostics information: • un controller mode:

– 0: No alarm – >0: Number of pending alarms

• In device mode, the parameter is always 0.

3.2 Evaluation of diagnostic alarms

When a channel error occurs, e.g. link down of a port, the faulty component generates a diagnostic alarm to the PROFINET controller, the CP.

FB 54 (PNIO_ALARM) is used for the alarm evaluation by a CP 343-1 that is operated as a PROFINET IO controller and is called in the user program of the CPU. All PROFINET IO alarms are detected, evaluated and acknowledged by this block. This enables the user to program an error analysis that is more exact and an individual reaction to the error.

If FB 54 is not called in the user program, all alarms are internally acknowledged by the CP. In this case, no alarm information is forwarded to the user program.

Note The PROFINET communication between CP and CPU via the backplane bus is block-related, i.e. only special communication blocks (FC11, FC 12, FB54, etc.) are used for the communication. The error OBs (OB82, OB83, OB86, etc.) are thus not automatically called in the user program.




Functional sequence The following step table shows the sequence of the error analysis: Table 3-3

No. Action Note

1. A diagnostic alarm occurs E.g., by removing/inserting a module or link down on a port

2. FB 54 is called in the user program and provided with the alarm information.

E.g., slot number, channel number, alarm type, incoming / outgoing alarm

3. Evaluation of the alarm information and individual reaction.

Among other things, this application shows the failure of a component on an LED of a digital output.

Call interface

V2.0 08/30/07 16/38

Cop

yrig

ht ©

Sie

men

s A

G 2

007

All

right

s re

serv

ed

2156

6216

_DIA

G_N

ETW

OR

K_D

OK

U_B

AN

D2_

V20

_e.d

oc

The figure below shows the call of FB 54 in FBD representation: Figure 3-4





V2.0 08/30/07 17/38

Cop

yrig

ht ©

Sie

men

s A

G 2

007

All

right

s re

serv

ed

2156

6216

_DIA

G_N

ETW

OR

K_D

OK

U_B

AN

D2_

V20

_e.d

oc


Table 3-4


CPLADDR WORD INPUT CP start address MODE DWORD IN_OUT Reserved TINFO ANY IN_OUT Destination area for the alarm management

information. AINFO ANY IN_OUT Destination area for header information and

additional alarm information DONE BOOL OUTPUT Status parameter; indicates the job status. ERROR BOOL OUTPUT Indicates an error of the block. NEW BOOL OUTPUT When DONE = 1 and NEW = 1, a newly received

alarm is signaled. STATUS WORD OUTPUT Status display ID WORD OUTPUT Logical start address of the PN IO component

triggering the alarm (board or module). LEN INT OUTPUT Length of the received alarm information

(AINFO)

3.3 Display of messages

System messages as known from the “Report System Error” function are not automatically displayed for a PROFINET IO communication via a CP. The reason is that the error OBs calling the special “Report System Error” blocks do not have a function in this communication.

Alternatively, special SFBs and SFCs for sending block-related messages are available:

• SFC 17 “ALARM_SQ”

• SFC 18 “ALARM_S” (realized in this application)

• SFC 107 “ALARM_DQ”

• SFC 108 “ALARM_D”

Depending on the reported message number, the program generates a block-related error message and sends this message to the HMI system.




Schematic diagram The figure below schematically shows the way of a PROFINET IO diagnostic alarm from a PROFINET device via the controller to the HMI system.

Figure 3-5

V2.0 08/30/07 18/38

Cop

yrig

ht ©

Sie

men

s A

G 2

007

All

right

s re

serv

ed

2156

6216

_DIA

G_N

ETW

OR

K_D

OK

U_B

AN

D2_

V20

_e.d

oc

WinCCflexible RT

IE/PN

IE/PN

POF

PG/PC

SCALANCE X208

SCALANCE X202

ET200 S

IE/P

N

S7 program

FB 54

S7 station

PROFINET IO diagnostic alarm

Message generation(Alarm S)

ET200 SPOF

IE/PN

POF




Functional sequence The following step table shows the sequence of the error analysis: Table 3-5

Action Note

1. A diagnostic alarm occurs E.g., by removing/inserting a module or link down on a port

2. SFC 18 is called in the user program with a specific number (see Table 3-7).

3. Generation of an error message and automatic display on the HMI device.

One message text exists for each error channel.

Call interface

V2.0 08/30/07 19/38

Cop

yrig

ht ©

Sie

men

s A

G 2

007

All

right

s re

serv

ed

2156

6216

_DIA

G_N

ETW

OR

K_D

OK

U_B

AN

D2_

V20

_e.d

oc

The figure below shows the call of SFC 18 in FBD representation: Figure 3-6


Explanation of the formal parameters The formal parameters have the following meaning: Table 3-6


SIG BOOL INPUT Signal triggering the message ID WORD INPUT Data channel for messages:

W#16#EEEE EV_ID DWORD INPUT Message number SD ANY INPUT Associated value for the message RET_VAL INT OUTPUT Error information




V2.0 08/30/07 20/38

Cop

yrig

ht ©

Sie

men

s A

G 2

007

All

right

s re

serv

ed

2156

6216

_DIA

G_N

ETW

OR

K_D

OK

U_B

AN

D2_

V20

_e.d

oc

Message texts The errors, the associated message texts and the corresponding error numbers are listed in the following table:

Table 3-7

Message number Error Message text

DW#16#60000001 Failure of the SCALANCE X208

Failure of Modul SCALANCE X208. Diagnostic address @1i%1d@

DW#16#60000002 Failure of the SCALANCE X202

Failure of Modul SCALANCE X202 Diagnostic address @1i%1d@

DW#16#60000003 Failure of the first ET 200S PNFO

Failure of Modul ET200_1 Diagnostic address @1i%1d@

DW#16#60000004 Failure of the second ET 200S PNFO

Failure of Modul ET200_2 Diagnostic address @1i%1d@

DW#16#60000005 Link down on port 5 of the SCALANCE X208

SCALANCE X208:connection to Cell interrupted! Diagnostic address @1i%1d@


SCALANCE X208:connection to CPU interrupted! Diagnostic address @1i%1d@


SCALANCE X208:connection to HMI interrupted! Diagnostic address @1i%1d@

DW#16#60000008 Link Down on port 3 of the SCALANCE X202

SCALANCE X202:connection of Port 3 interrupted! Diagnostic address @1i%1d@

DW#16#60000009 Link down on port 2 of the first ET 200S PNFO

ET200_1:connection of Port 2 interrupted! Diagnostic address @1i%1d@

DW#16#6000000A Link down on port 1 of the second ET 200S PNFO

ET200_2:connection of Port 1 interrupted! Diagnostic address @1i%1d@

DW#16#6000000B Module removed from the ET 200S PNFO

Submodule drawn PROFINET Systemnumber (HWConfig): @1c%1s@ Slotnumber of drawn module: @3c%1s@

DW#16#6000000C Power module removed from the first ET 200S PNFO

PowerModul of ET200-1 drawn PROFINET Systemnumber (HWConfig): @1c%1s@ Slotnumber of drawn module: @3c%1s@

DW#16#6000000D Power module removed from the second ET 200S PNFO

PowerModul of ET200-2 drawn PROFINET Systemnumber (HWConfig): @1c%1s@ Slotnumber of drawn module: @3c%1s@



DIAG_NETWORK ID Number: 21566216 Display on the HMI system

On the HMI system (here: WinCC flexible RT), all pending messages are displayed in an automatically displayed message window and an additional message screen.

Figure 3-7

V2.0 08/30/07 21/38

Cop

yrig

ht ©

Sie

men

s A

G 2

007

All

right

s re

serv

ed

2156

6216

_DIA

G_N

ETW

OR

K_D

OK

U_B

AN

D2_

V20

_e.d

oc


4BExplanations of the Example Program


4 Explanations of the Example Program

4.1 Configuration explanations for “ALARM_S”

Process To send a block-related message from an S7 CPU, the following steps have to be performed:

1. Selecting the desired message block (here: SFC 18)

2. Defining the function block and instance data block to be used (here: FB50 /DB50)

3. Determining the assignment of the message numbers (see Table 3-7)

4. Configuring the “IN parameters” of the FB for one or several messages by assigning specific attributes.

V2.0 08/30/07 22/38

Cop

yrig

ht ©

Sie

men

s A

G 2

007

All

right

s re

serv

ed

2156

6216

_DIA

G_N

ETW

OR

K_D

OK

U_B

AN

D2_

V20

_e.d

oc

5. Configuring the message texts in the special object properties of the associated instance data block.

Assigning the message numbers How the message numbers for the individual messages are to be assigned can be defined in the special object properties of the instance data block of FB 50. Two options are available:

• Assigning CPU-oriented unique message numbers

• Assigning project-related unique message numbers Figure 4-1

In this application, CPU-oriented unique message numbers are assigned.



DIAG_NETWORK ID Number: 21566216 Configuring of FB 50 as a message FB

To prepare FB 50 for sending messages, an input parameter has to be declared in the variable declaration table of FB 50 for each message or each call of the SFC 18 alarming block. Each of these variables must be provided with the following properties:

• Data type is “DWORD” without initial value

• Assignment of the S7_a_type and S7_server system attributes with the alarm_s and alarm_archiv values.

The attributes are assigned in the object properties of each variable in the Attributes tab: Figure 4-2

V2.0 08/30/07 23/38

Cop

yrig

ht ©

Sie

men

s A

G 2

007

All

right

s re

serv

ed

2156

6216

_DIA

G_N

ETW

OR

K_D

OK

U_B

AN

D2_

V20

_e.d

oc

After assigning the system attributes, these variables are displayed with a green flag in the variable declaration table.




Figure 4-3

V2.0 08/30/07 24/38

Cop

yrig

ht ©

Sie

men

s A

G 2

007

All

right

s re

serv

ed

2156

6216

_DIA

G_N

ETW

OR

K_D

OK

U_B

AN

D2_

V20

_e.d

oc

When calling FB 50, these variables are automatically supplied with the corresponding message numbers.

Figure 4-4




Configuring the message texts The message texts are configured in the special object properties of the instance data block assigned to the message FB.

In this dialog box, all variables are listed, which have received the system attributes as parameters in the message FB. A unique message number and a unique message text are assigned to each message identifier. Position and format of a possible associated value are directly defined in the message text.

Figure 4-5

V2.0 08/30/07 25/38

Cop

yrig

ht ©

Sie

men

s A

G 2

007

All

right

s re

serv

ed

2156

6216

_DIA

G_N

ETW

OR

K_D

OK

U_B

AN

D2_

V20

_e.d

oc

Associated value



DIAG_NETWORK ID Number: 21566216 4.2 Explanations of the STEP 7 program

Overview The figure below shows the most important program parts and the call structure of the STEP 7 program.

Figure 4-6

V2.0 08/30/07 26/38

Cop

yrig

ht ©

Sie

men

s A

G 2

007

All

right

s re

serv

ed

2156

6216

_DIA

G_N

ETW

OR

K_D

OK

U_B

AN

D2_

V20

_e.d

oc

DB50

OB 1

FC 3

ALARM

FC 2

CELL

FC 11

PNIO_SEND

FC 12

PNIO_RECV

DB 2

READ_WRITE_DATA

FB 54

PNIO_ALARM

FB50

SEND_MSG

SFC 18

ALARM_S

DB 3

PNIO_ALARM_INFO

DB 1

ADRESS&STATUS

Use

r pro

gram

Ala

rm e

valu

atio

n/in

divi

dual

err

or d

iagn

ostic

sM

essa

ges

DB55




V2.0 08/30/07 27/38

Cop

yrig

ht ©

Sie

men

s A

G 2

007

All

right

s re

serv

ed

2156

6216

_DIA

G_N

ETW

OR

K_D

OK

U_B

AN

D2_

V20

_e.d

oc

Explanations of the program structure The following table shows the used STEP 7 blocks and their functionality.

Table 4-1

Block Description

OB 1 • If no link down on port 5 of the SCALANCE X208 switch was reported, FC 2 is called for control of the process in the cell.

• The status of port 5 is displayed by an output bit (an output bit of the digital output module flashes in the event of a link down)

• Block FC 3 is called. FC 2 CELL

• FC 2 includes the control of the cell (flashing LEDs on the ET 200S PNFO).

• An active cell is also symbolized via a running light on the S7-300 station.

FC 3 ALARM

• Call of the FB 54 PN IO alarm block that detects, evaluates and acknowledges the PROFINET IO alarms. The information is stored in DB 3 (PNIO_ALARM_INFO).

• Evaluation of the alarm information from the data block. • The status of the individual modules is indicated by means of

output bits (output set if module cannot be accessed) • If a link down is detected on port 5 of the SCALANCE X208 switch,

a flag is set. • Call of FB 50 (SEND_MSG) for generating a plain-text message.

FC 11 /FC 12 PNIO_SEND/ PNIO_RECV

• PROFINET IO blocks for handling the data traffic via the CP.

DB 2 READ_WRITE_DATA

• Storage of the output data returned by the FC 11 and FC 12 PROFINET IO blocks.

DB 3 PNIO_ALARM_INFO

• Storage of the alarm information returned by the FB 54 (PNIO_ALARM) PROFINET IO alarm block.

DB 1 ADRESS&STATUS

• Contains all diagnostic addresses from HW Config

FB 54 PNIO_ALARM

• PROFINET IO alarm block for detecting, evaluating and acknowledging the diagnostic alarms

FB 50 SEND_MSG

• Call of SFC 18 (ALARM_S) for generating a plain-text message by means of message numbers

SFC 18 ALARM_S

• Generation of plain-text messages with associated value and automatic sending to the HMI device




Description of the STEP 7 code in OB 1 The operating system of the S7 CPU cyclically executes OB 1. All function blocks can be called here.

Table 4-2

V2.0 08/30/07 28/38

Cop

yrig

ht ©

Sie

men

s A

G 2

007

All

right

s re

serv

ed

2156

6216

_DIA

G_N

ETW

OR

K_D

OK

U_B

AN

D2_

V20

_e.d

oc

NW Explanation Code

1 This network is only processed if the communication to the cell is not faulty. After restarting the CPU, the two running lights are preset with values. Subsequently, FC 2 (CELL) for executing the running light program is called.

2 The cell failure is indicated by the CELL_LinkDown flag. If the flag is true, the output bit flashes cyclically.

3 The running light on the S7 station is stopped after a cell failure and has to be restarted when the cell returns.

4 The last network calls the block for alarm diagnostics.




Description of the STEP 7 code in FC 2 The FC 2 (CELL) function block is called cyclically in OB 1 and includes the user program. On the hand, a running light is generated on the digital output directly on the S7 station, on the other hand, a running light is generated on the first ET 200S PNFO. The characteristic feature is that the data traffic from and to the PROFINET devices has to be handled via special communication blocks.

Table 4-3

V2.0 08/30/07 29/38

Cop

yrig

ht ©

Sie

men

s A

G 2

007

All

right

s re

serv

ed

2156

6216

_DIA

G_N

ETW

OR

K_D

OK

U_B

AN

D2_

V20

_e.d

oc

NW Explanation Code

1 To ensure that the running lights do not “race”, the code for the running lights is executed only every 500ms.

2 This network executes the running light for the digital output of the S7 station. It starts at the value 3, i.e. bit 0 and bit 1 are true. As soon as the running light reaches the last bit of the output byte, it is restarted. Otherwise, the bits are shifted to the left by one position.

3 This network executes the running light for the digital output of the ET 200S PN IO. The bits are shifted to the left by one position. As soon as the output byte reaches the value 8 (bit 3 is true), it is restarted.

4 Via FC 11 (PNIO_SEND), these process data are transferred to the CP for forwarding to the PROFINET IO devices.




NW Explanation Code

5 Via FC 12 (PNIO_RECV), the input data that have been transferred from a PROFINET IO device to the CP are read from the CP into the user program.

Note For the exact meaning of the parameter assignments in the call of the communication blocks, please refer to the well-documented code.

V2.0 08/30/07 30/38

Cop

yrig

ht ©

Sie

men

s A

G 2

007

All

right

s re

serv

ed

2156

6216

_DIA

G_N

ETW

OR

K_D

OK

U_B

AN

D2_

V20

_e.d

oc

Description of the STEP 7 code in FC 3 FC 3 (ALARM) is called cyclically in OB 1 and, in turn, calls FB 54. As soon as a diagnostic alarm is detected by the CP, the alarm is transferred to FB 54.



DIAG_NETWORK ID Number: 21566216 Table 4-4

V2.0 08/30/07 31/38

Cop

yrig

ht ©

Sie

men

s A

G 2

007

All

right

s re

serv

ed

2156

6216

_DIA

G_N

ETW

OR

K_D

OK

U_B

AN

D2_

V20

_e.d

oc

NW Explanation Code

1 FB 54 (PNIO_ALARM) is called. TINFO and AINFO contain information on the alarm. If no new alarm has been detected, the block is terminated. The EventClass parameter from TINFO provides the information whether the alarm is incoming or outgoing and the program is continued at the corresponding jump label (COME/GONE).

2 If an incoming alarm has been detected, this network uses the diagnostic address to check which component has caused the alarm. If the component is a PROFINET IO device, this means a failure of the module. A corresponding output bit is set. Bit 1 corresponds to PROFINET IO address 1, bit 2 to PROFINET IO address 2, etc. If the component is port 5 of the SCALANCE X208, this means that the communication to the cell is interrupted. The Cell_LinkDown flag is set.




NW Explanation

V2.0 08/30/07 32/38

Cop

yrig

ht ©

Sie

men

s A

G 2

007

All

right

s re

serv

ed

2156

6216

_DIA

G_N

ETW

OR

K_D

OK

U_B

AN

D2_

V20

_e.d

oc

Code

3 When the device or the communication connection to the cell returns, the alarm is marked as outgoing. This network uses the diagnostic address to check which component has reported the outgoing alarm. If the component has been found, the corresponding output bit or the flag is reset.




NW Explanation

V2.0 08/30/07 33/38

Cop

yrig

ht ©

Sie

men

s A

G 2

007

All

right

s re

serv

ed

2156

6216

_DIA

G_N

ETW

OR

K_D

OK

U_B

AN

D2_

V20

_e.d

oc

Code

4 The direction (incoming/outgoing) of the diagnostic alarm is important for the message to the HMI system. The EventClass parameter included in TINFO provides this information. For sending the message to the HMI system, FB 50 (SEND_MSG) is called to which the block-related messages are assigned. The “EV_Idx” parameters are assigned automatically, “INT-Incoming” contains the direction of the alarm, “RET_VAL_xxx” the return value, the remaining parameters information on the component that has caused the alarm.

Structure, Configuration and Operation of the Application

5BInstallation and Startup


V2.0 08/30/07 34/38

Cop

yrig

ht ©

Sie

men

s A

G 2

007

All

right

s re

serv

ed

2156

6216

_DIA

G_N

ETW

OR

K_D

OK

U_B

AN

D2_

V20

_e.d

oc


5 Installation and Startup

5.1 Hardware and software installation

This chapter describes which hardware and software components have to be installed. The descriptions and manuals as well as delivery information included in the delivery of the respective products should be observed in any case.

Hardware installation The hardware components are listed in chapter 2.2. For the hardware configuration, please follow the instructions listed in the table below:

WARNING Only switch on the power supply after the last step has been completed!

Note For the preparation of the necessary connecting cables, the installation of the PC module and the required software, please refer to VOLUME 1.




V2.0 08/30/07 35/38

Cop

yrig

ht ©

Sie

men

s A

G 2

007

All

right

s re

serv

ed

2156

6216

_DIA

G_N

ETW

OR

K_D

OK

U_B

AN

D2_

V20

_e.d

oc

Installing the controller components Table 5-1

No. Instruction Remark 1. Mount the SCALANCE X208 and SCALANCE

X202 on the S7-300 DIN rail.

2. Mount the power supply, the CPU, the CP and the SM322 DO module of the S7-300 on the S7-300 DIN rail.

3. Mount the two ET 200S PNFO on the 35mm top-hat rail.

4. Attach the following modules and the corresponding terminal modules to the first ET 200S PNFO head module in the following order: • PM 24VDC • 4 DO 24VDC 0.5A

Connect PIN 2 (L1) and PIN 3 (M) of the power module to a 24V power supply. You can pick up the 24V from the head module.

5. Attach the following modules and the corresponding terminal modules to the second ET 200S PNFO head module in the following order: • PM 24VDC • 2 DI 24VDC

Connect PIN 2 (L1) and PIN 3 (M) of the power module to a 24V power supply. You can pick up the 24V from the head module.

6. Ensure the power supply with 24VDC for SCALANCE X208, SCALANCE X202, CPU, CP, SM322 DO module and the two ET 200S PNFO.

7. Supply the power supply with 230VAC. 8. Use the Ethernet cables to network CP, PG and

SCALANCE X 202 with the SCALANCE X208 switch.

Port 1 CP Port 2 HMI station/ PG Port 5 SCALANCE X202 port 2

9. Use the POF cable to network the first ET 200S PNFO with the SCALANCE X202 switch.

Port 3 of the SCALANCE X202 switch with port 1 of the ET 200S PNFO

10. Optional: Connect a second PC to the SCALANCE X202 switch for port mirroring

PC to port 1 of the SCALANCE X202 switch

11. Use the POF cable to network the second ET 200S PNFO with the first ET 200S PNFO.

Port 2 of the first ET 200S PNFO with port 1 of the second ET 200S PNFO

Note The installation guidelines for SIMATIC S7 and SIMATIC NET always have to be observed.




5.2 Application software installation

General preparations Unzip this file: 21566216_DIAG_NETWORK_CODE_BAND2_V20.zip.

This folder contains

• the archived Diagnostic_CP.zip STEP 7 project

• the device profiles for the SCALANCE X208 and X202 switches.

Assigning name and IP address of the PROFINET nodes To ensure the PROFINET functionality, all network stations require unique names that are identical in the device and in the configuration of the S7 CPU. To assign these names and the IP addresses, follow the instructions listed in VOLUME 1.

V2.0 08/30/07 36/38

Cop

yrig

ht ©

Sie

men

s A

G 2

007

All

right

s re

serv

ed

2156

6216

_DIA

G_N

ETW

OR

K_D

OK

U_B

AN

D2_

V20

_e.d

oc

• Changing the IP address of the PG/PC

• Assigning name and IP address of the PROFINET nodes

The following table provides an overview of the PROFINET device names and IP addresses used in this volume: Table 5-2

Module Device name IP address

CP343-1 cp-343-1 140.80.0.1 SCALANCE X208 scalance-x208 140.80.0.2 SCALANCE X202 scalance-x202-2pirt 140.80.0.3 ET 200S PNFO im151-3pnfov50 140.80.0.4 ET 200S PNFO im151-3pnfov50-1 140.80.0.5 HMI station 140.80.0.6

Loading the STEP7 project to the CPU Table 5-3

No. Instruction Remark 1. Open the SIMATIC MANAGER and retrieve

the Diagnostic_CP.zip STEP 7 project. File -> Retrieve…

2. Select the SIMATIC 300 S7 station and use PLC-> Download to load the entire project to your CPU.

Configuring the Station Configuration Editor To commission the HMI station, open the Station Configuration Editor and load the XDB file that is located in the directory of the STEP 7 project.

For a detailed description of the procedure, please refer to VOLUME 1.


6BConfiguration


6 Configuration

Setting up the Alarm S messages in Runtime

Note The display of Alarm S messages on an HMI client requires that the WinCC flexible project is integrated into the STEP 7 project.

The STEP 7 project directory includes a database file with an assignment of the error information to the corresponding plain-text message. The integrated WinCC flexible project can access this file.

Table 6-1

V2.0 08/30/07 37/38

Cop

yrig

ht ©

Sie

men

s A

G 2

007

All

right

s re

serv

ed

2156

6216

_DIA

G_N

ETW

OR

K_D

OK

U_B

AN

D2_

V20

_e.d

oc

No. Instruction Note

1. Open the WinCC flexible project via STEP 7.

2. In the WinCC flexible project tree, go to Alarm Management -> Settings -> Alarm Settings. In Alarm Procedure, activate the values 0-15 for ALARM_S.

3. When inserting a message window, the event type to be displayed can be selected.

Appendix and Literature

7BLiterature


V2.0 08/30/07 38/38

Cop

yrig

ht ©

Sie

men

s A

G 2

007

All

right

s re

serv

ed

2156

6216

_DIA

G_N

ETW

OR

K_D

OK

U_B

AN

D2_

V20

_e.d

oc

Appendix and Literature

7 Literature

7.1 Bibliographic references

This list is by no means complete and only provides a selection of appropriate sources. After installing SIMATIC NET, the manuals are available via Start SIMATIC Documentation English.

Table 7-1

Topic Title

1. SCALANCE-X100/X200 Commissioning Manual On the CD included in the delivery of the SCALANCE-X2xx. Available in Product Support; Entry ID: 21420847

SCALANCE Industrial Ethernet SCALANCE-X100/X200

2. Manual on standards, topologies and devices as well as installation guidelines. On the SIMATIC NET documentation CD-ROM. Available in Product Support; Entry ID: 8763736

SIMATIC NET Twisted-Pair and Fiber-Optic Networks

3. White paper on network management, Simple Network Management Protocol, RMON On the SIMATIC NET documentation CD-ROM. SIMATIC Net Documentation/Literature on the internet.

SIMATIC NET Network Management White Paper 05/2003

4. Manual Part B3S for CP343-1 (EX30) as of hardware version 2, as of firmware version V2.0. On the SIMATIC NET documentation CD-ROM. Available in Product Support; Entry ID: 24485272

CP343-1 EX30 Manual

5. Manual for migration / Comparison of PROFIBUS DP and PRONET IO On the SIMATIC NET documentation CD-ROM. Available in Product Support; Entry ID: 19289930

From PROFIBUS DP to PROFINET IO

6. Commissioning PC stations, configuring the OPC server, OPC scout manual On the SIMATIC NET documentation CD-ROM. Available in Product Support; Entry ID: 13542666

SIMATIC NET Commissioning PC Stations



https://www2.automation.siemens.com/net/html_76/produkte/040_snmp-dokumentation.shtml




application about communication - siemens€¦ · application about communication . diagnostic...

Documents