Applikation Benutzerverwaltung RFID DOKU V10

Application Operator Control & Monitoring

WinCC flexible 2005, user log-on to the operator panel via RFID

Application description

Warranty, Liability and Support

User log-on to the operator panel via RFID Entry ID: 26481978

V1.0 20.11.2007 2/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

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 to use sound practices in application, installation, operation and maintenance. By using these application examples you accept that Siemens is not liable for any damages except for those specified in the above liability clause. 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.

Warranty, Liability and Support

We accept no liability for 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© 2008 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. If you have any questions about this document please e-mail us to the following address:

mailto:[email protected]

mailto:[email protected]�

Foreword


V1.0 20.11.2007 3/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

Foreword

Objective of the application This application was created to show the user...

• how to log on to an operator panel via RFID (card/chip card reader).

Main contents of this application The following main points are discussed in this application:

• STEP 7 program description

• WinCC flexible program description

• Hardware requirements

Delimitation This application does not include a description of

• the SIMATIC STEP 7 engineering tool.

• the used multi panel.

Basic knowledge of these topics is required.

Furthermore, the application does not provide a detailed description of the special properties of the used EKS devices 1 made by EUCHNER. Only the settings required for this application are described in this document.

Detailed information on the used EKS devices and their application can be found on the home page of the company EUCHNER. www.euchner.de

1EKS – Electronic Key System

http://www.euchner.de/�

Foreword


V1.0 20.11.2007 4/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

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

Part Description Application description Provides a general overview of the contents. You

will learn about the components used (standard hardware and software components and the specially created user software).

Function principles and program structures

This part describes the detailed function processes of the hardware and software components involved, the solution structures and – where useful – the specific implementation of this application. This part is necessary if you want to learn about the interaction of the solution components, e.g., in order to use them as the basis for your own development.

Structure, 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 section of the documentation includes further information, e.g. bibliographic references, glossaries etc.

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

http://support.automation.siemens.com/WW/view/de/26481978

http://support.automation.siemens.com/WW/view/de/26481978�

Foreword


V1.0 20.11.2007 5/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

Table of Contents

Table of Contents ......................................................................................................... 5

Application description................................................................................................ 7

1 Automation task.............................................................................................. 7 1.1 Overview........................................................................................................... 7 1.2 Requirements ................................................................................................... 9

2 Automation solution..................................................................................... 10 2.1 Overview of the overall solution...................................................................... 10 2.2 Description of the core functionality................................................................ 11 2.3 Advantages and benefits of the application .................................................... 11 2.4 Required hardware and software components ............................................... 12 2.5 Basic performance data.................................................................................. 14

Function Principles and Program Structures .......................................................... 15

3 General Function Mechanisms.................................................................... 15 3.1 Electronic key adapter .................................................................................... 15 3.2 Electronic key read/write................................................................................. 15 3.3 Operator panel(s)............................................................................................ 15 3.4 STEP 7 Program............................................................................................. 16

4 Functional Mechanisms of the STEP 7 Program ....................................... 17 4.1 STEP 7 program structure .............................................................................. 17 4.1.1 Block description............................................................................................. 18 4.2 Hardware configuration................................................................................... 22 4.3 Description of program execution FC15 (Pan_01_EKS_Evaluation).............. 23 4.3.1 Structure of the DB150 and DB151 blocks ..................................................... 24 4.3.2 Program description NW 1 and 2 of the FC15................................................ 25 4.3.3 Program description NW 4 of the FC15.......................................................... 26 4.3.4 Program description NW 5 of the FC15.......................................................... 27 4.3.5 Program description NW 6 of the FC15.......................................................... 29 4.3.6 Program description NW 7 of the FC15.......................................................... 31 4.3.7 Program description NW 8 of the FC15.......................................................... 31 4.3.8 Program description NW 9 of the FC15.......................................................... 32 4.3.9 Program description NW 10 of the FC15........................................................ 33 4.3.10 Program description NW 11 of the FC15........................................................ 34 4.4 Description of program execution FC16 (Pan_01_Clear_DB_Data) .............. 35

5 Functional Mechanisms of the WinCC flexible Project ............................. 36 5.1 WinCC flexible project structure ..................................................................... 36 5.1.1 Configuration explanation for “Screen_1” ....................................................... 37 5.1.2 Configuration explanation for “Screen_2” ....................................................... 39 5.1.3 Configuration explanation for Log-on/ log-off function .................................... 43

Foreword


V1.0 20.11.2007 6/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

6 Modifications to the Sample Program ........................................................ 45 6.1 Adapting the STEP 7 blocks ........................................................................... 45 6.2 Adapting the WinCC flexible configuration ..................................................... 45 6.2.1 Operator panels .............................................................................................. 45 6.2.2 Calling the “Screen 2” ..................................................................................... 45

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

7 Installation and Commissioning ................................................................. 46 7.1 Installation of hardware and software ............................................................. 46 7.2 Installation of the application software............................................................ 47

8 Operating the Application............................................................................ 48 8.1 Calling the start page using the example of the MP277 Touch ...................... 48 8.1.1 Operating the “Screen 1” page ....................................................................... 49 8.1.2 Operating the “Screen 2” page ....................................................................... 50 8.1.3 General information on operation / configuration............................................ 52

9 Literature ....................................................................................................... 53 9.1 Bibliographic references ................................................................................. 53 9.2 Internet links ................................................................................................... 53

10 History ........................................................................................................... 54


Automation task

User log-on to the operator panel via RFID Article ID: 26481978

V1.0 20.11.2007 7/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc


Content Here will you learn about the components used (software components and the created user software).

The performance data displayed illustrates the performance capability of this application.

1 Automation task

Here you find information on … the automation task discussed in the documentation on hand.

1.1 Overview

Introduction Your customer has different plant components, which can be operated and parameterized using several operator panels.

Depending on whether the station has to be operated, maintained or parameterized, different user authorizations are required.

Until now, user log-on to the operator panel has been carried out by entering the user name and the corresponding password manually.

It is intended to replace this log-on type by a chip card that is read out by a card reader.


Automation task


V1.0 20.11.2007 8/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

Overview of the automation task The figure below provides an overview of the automation task.

Figure 1-1

Description of the automation task The operator logs on to the operator panel with a transponder using a card reader. This log-on is active only as long as a transponder is plugged into the card reader. If the transponder is removed from the card reader, the user is automatically logged off.

The user data is evaluated by the operator panel and its user administration.

An authorized person can read the transponder data (user and password), change them and rewrite empty transponders using a separate system view.

The operator panels and the “card reader” are connected to an S7-300 controller via a PROFIBUS connection.


Automation task


V1.0 20.11.2007 9/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

1.2 Requirements

This WinCC flexible application is integrated into a STEP 7 project and is supposed to meet the requirements listed below:

Controller requirement The data exchange between the operator panels and the card readers is performed via a PLC controller.

HMI requirements • The user administration is located in the operator panel.

• Three user groups are to be created.

• At least one user is to be created for each group.

• A user view must be available.

• It should be possible to output the user data from the transponder and to input them using separate I/O fields.

Requirements for transponders and card readers • The card readers must be connected to the existing PROFIBUS

network via a PROFIBUS connection.

• It must be possible to read out and write the card readers via the operator panel/controller.

• The transponders must be readable and rewritable.


Automation solution


V1.0 20.11.2007 10/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

2 Automation solution

Here you find information on … the solution selected for the automation task.

2.1 Overview of the overall solution

Schematic layout The schematic figure below displays the most important components of the solution:

Figure 2-1

Configuration This automation solution example consists of two operator stations. The configuration is described in greater detail in the following.

Operator station 1:

The operator station 1 consists of an MP277 Touch with a permanently assigned EKS electronic key adapter . A transponder, which is located in the EKS electronic key adapter , can be read out and written only via this panel. Both devices are connected to a Profibus network .

Operator station 2:

The operator station 2 consists of an OP177B with a permanently assigned EKS electronic key adapter . A transponder, which is located in the EKS electronic key adapter , can be read out and written only via this panel. Both devices are connected to a Profibus network .

Note An EKS system is permanently assigned to each operator panel.


Automation solution


V1.0 20.11.2007 11/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

PLC controller:

A CPU 315-2DP is used as a controller. The data exchange between operator panels and write/read devices (EKS electronic key adapter) is performed via the controller.

PROFIBUS network: All components such as operator panels, write/read devices (EKS electronic key adapter) and the S7 controller communicate via this PROFIBUS connection .

2.2 Description of the core functionality

The core piece of this application is the creation of an example illustrating how to perform a user log-on to an operator panel via the RFID system by EUCHNER.

If an electronic key read/write (transponder) is inserted into the electronic key adapter (write/read device), the data is evaluated in the S7 controller via the I/O module and transmitted to the corresponding operator panel. The evaluation of the user data (user name and password) is performed on the operator panel. If the data sent comply with the data stored in the user administration, the log-on to the operator panel is successful. Otherwise, the log-on is rejected with a system message.

2.3 Advantages and benefits of the application

• Errors when entering user name and password can thus be avoided.

• Quick and easy handling.

• Easy log-on even under unfavourable working conditions, for example, when wearing working gloves.

• High flexibility (e.g., changing user data).


Automation solution


V1.0 20.11.2007 12/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

2.4 Required hardware and software components

Hardware components Table 2-1

Component No. MLFB / Order number Note SIMATIC S7-300, mounting rail L=480MM

1 6ES7390-1AE80-0AA0

= minimum length

SIMATIC S7-300, CPU 315-2 DP

1 6ES7 315-2AG10-0AB0 Alternatively, any other S7 300/400 CPU can also be used.

SIMATIC S7, MICRO MEMORY CARD F. S7-300/C7/ET 200S IM151 CPU, 3.3 VNFLASH, 64 Kbytes

1 6ES7953-8LF11-0AA0

64 KB MICRO MEMORY CARD or larger.

Multi panel MP277 Touch 12 inches

1 6AV6643-0CD01-1AX0 Alternatively, any other panel can also be used.

Operator panel OP177B PN/DP

1 6AV6642-0DA01-1AX0 Alternatively, any other panel can also be used.

SIMATIC NET, connecting cable 830-2 F. PROFIBUS, pre-configured line with two SUB-D connectors. 9-pin, terminating resistors switchable, 3m

1 6XV1830-2AH30

2-wire shielded cable with PROFIBUS connectors for connecting operator panels and EKS devices.

EKS electronic key adapter with PROFIBUS-DP interface

2 EUCHNER EKS-A-IDX-G01-ST09/03 *)

*) as of 20.11.07

EUCHNER For detailed information, please contact the manufacturer. http://www.euchner.de/




Automation solution


V1.0 20.11.2007 13/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

Component No. MLFB / Order number Note EKS electronic key read/write

3 EUCHNER EKS-A-K1xxWT32-EU *)

*) as of 20.11.07

EUCHNER For detailed information, please contact the manufacturer. http://www.euchner.de/

Standard software components Table 2-2

Component No. MLFB / Order number Note SIMATIC S7, STEP 7 V5.4 SP3

1 6ES7810-5CC10-0YA7 Further ordering information, system requirements and STEP 7 compatibility are available on the Customer Support pages on the internet. http://support.automation.siemens.com

GSD file (EKS adapter)

1 EUCHNER Order no. 092054. *) http://www.euchner.de/ *) as of 20.11.07

The GSD file used is included in the project for test purposes. If possible, always use the current Euchner GSD file!

WinCC flexible 2005 Standard SP1

1 6AV6 612-0AA01-1CA5 To open the project, at least WinCC flexible 2005 Standard SP1 HF7 is required.



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




Automation solution


V1.0 20.11.2007 14/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

Example files and projects The following list contains all files and projects used in this example. Table 2-3

Component Note RFID_Projekt.zip The zip file contains:

• The STEP 7 project • The WinCC flexible project

integrated in STEP 7 • EUCHNER GSD file.

2.5 Basic performance data

Application software Table 2-4: Performance data of the application software

Criterion Basic performance data Additional note

Program size Project: 18 MB Project (.zip) 4.2 MB

Maximum cycle time 6 ms for CPU 315-2 DP Number of HMI screens, MP277 Touch 2

Number of HMI screens, OP177B PN/DP 3

Use of special characters no Digits and letters only

Number of characters for password and user name 10

In this example. Depends on the “Read/write module” used

Function Principles and Program Structures

General Function Mechanisms


V1.0 20.11.2007 15/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc


Content This part discusses the detailed function processes of the hardware and software components involved, the solution structures, and - where useful -the concrete implementation of this application.

You only need this part if you want to learn more about the interaction of the solution components.

3 General Function Mechanisms

Here you find information on … general function mechanisms concerning the data exchange between the electronic key adapter by EUCHNER, the operator panels and STEP 7.

3.1 Electronic key adapter

The electronic key adapter is used to read out the electronic key read/write. The electronic key adapter is integrated into the STEP 7 hardware using a special GSD file.

Note The GSD file can be downloaded from the EUCHNER home page.

The data exchange between the electronic key adapter and the STEP 7 program is performed via a specified I/O area. The PROFIBUS address is set on the electronic key adapter via a DIP switch.

3.2 Electronic key read/write

The electronic key read/write features a user-programmable memory area. This memory area is written and read out using STEP 7 program blocks.

3.3 Operator panel(s)

The user administration is created in the configuration and transferred with the configuration to the operator panels.

Corresponding user rights are assigned to variables and buttons that can only be executed by the user with the appropriate authorizations.

When executing a password-protected function, a dialog box is displayed where the user can enter a user name and a password.

This log-on procedure via the “log-on dialog” is supplemented /replaced by previously reading out the RFID data via the electronic key adapter.


General Function Mechanisms


V1.0 20.11.2007 16/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

The STEP 7 program evaluates the data of the electronic key read/write, processes them and sends the data (user data) to the operator panel. There, an internal function evaluates whether the operator has the required authorization.

Note By means of the user administration stored, the operator panel compares whether the user data read out is correct. The user data is not stored in the controller.

3.4 STEP 7 Program

The STEP 7 program accesses the I/O data of the electronic key adapter. The write/read area is assigned to the respective data block. The further evaluation is then performed using these data blocks.

Notes • You can download a special manual from the EUCHNER home page, which provides you with information on the EKS electronic key adapter with a PROFIBUS-DP interface. This manual contains detailed information on how to parameterize the electronic key adapter. (www.euchner.de) (See also Chapter 9.1 Bibliographic references)

• There are two previously parameterized data blocks for the write/read area that are used for communication. The blocks can be adapted accordingly by the user.



Functional Mechanisms of the STEP 7 Program


V1.0 20.11.2007 17/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

4 Functional Mechanisms of the STEP 7 Program

Here you find information on … • the structure of the STEP 7 program.

• the data exchange between the EKS electronic key adapter and the STEP 7 program.

4.1 STEP 7 program structure

Overview The screenshot below shows the program structure / program blocks of the STEP 7 project. Figure 4-1




V1.0 20.11.2007 18/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

4.1.1 Block description

The following table lists and explains the STEP 7 blocks used. The S7 program is structured so that individual FCs and DBs are assigned to each operator panel.

The following sections of this chapter describe the individual blocks in detail.

Table 4-1

Block Explanation

OB1 Organization block: (Cycle Execution) is called by the operating system. For cyclic program processing.

OB82 Diagnostic alarm OB: (I/O Point Fault 1) (Detailed information can be found in the online help on STEP 7)

OB85 Program sequence error OB: (OB Not Loaded Fault) (Detailed information can be found in the online help on STEP 7)

OB86 Module rack failure OB: (Loss of Rack Fault) (Detailed information can be found in the online help on STEP 7)

OB100 Startup OB: (Complete Restart) (Detailed information can be found in the online help on STEP 7)

FC15 Pan_01_EKS_Evaluation:

contains the program for evaluating the EKS electronic key adapter for the Operator panel 01 (MP277 Touch)

FC16 Pan_01_Clear_DB_Data: in the event of an EKS electronic key adapter failure for the Operator panel 01, the data read out (DB150) and the diagnostic data (DB152) are set to “Zero“. (setting DBs to a defined status).

FC20 Pan_02_EKS_Evaluation: contains the program for evaluating the EKS electronic key adapter for the Operator panel 02 (OP177B PN/DP)

FC21 Pan_02_Clear_DB_Data: in the event of an EKS electronic key adapter failure for the Operator panel 02, the data read out (DB160) and the diagnostic data (DB162) are set to “Zero“. (setting DBs to a defined status).




V1.0 20.11.2007 19/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

Block Explanation

FC125 GLOBAL_DP_DIAG: The FC125 evaluates the information on the bus node that has failed or malfunctioned. For more information, refer to http://support.automation.siemens.com/WW/view/de/387257

DB10 STEP 7_Global_Data:

This DB is intended for general data. DB15 Pan_01_Global_Data_STEP 7:

This DB serves as a “global“ data block for the Operator panel 01 (MP277 Touch). -> Edge evaluation, temporary files etc.

DB20 Pan_02_Global_Data_STEP 7: This DB serves as a “global“ data block for the Operator panel 02 (OP177B PN/DP). -> Edge evaluation, temporary files etc.

DB125 GLOBAL_DIAG_DB: This DB is used for evaluating the FC125. (Evaluation of the bus nodes that have failed or malfunctioned).

DB150 Pan_01_Read_Transponder: (previously parameterized EUCHNER data block) This DB contains the data read out of the electronic key read/write. The DB is assigned to the Operator panel 01 (MP277 Touch).

DB151 Pan_01_Write_Transponder: (previously parameterized EUCHNER data block) This DB contains the data that is to be sent to the electronic key read/write. The DB is assigned to the Operator panel 01 (MP277 Touch).

DB152 Pan_01_DP_Diagnostic: (previously parameterized EUCHNER data block) This DB contains the device-specific diagnostic data of the EKS electronic key adapter. The DB is assigned to the Operator panel 01 (MP277 Touch).

DB153 Pan_01_User_Data: This DB is used to input and output the user data on the operator panel. The DB is assigned to the Operator panel 01 (MP277 Touch).






V1.0 20.11.2007 20/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

Block Explanation

DB155 Pan_01_General_Data: This DB contains “general data“ that is used on the Operator panel 01 (MP277 Touch). (I/O fields with required input authorizations).

DB160 Pan_02_Read_Transponder: (DB150 copy) This DB contains the read out data of the electronic key read/write. The DB is assigned to the Operator panel 02 (OP177B PN/DP).

DB161 Pan_02_Write_Transponder: (DB151 copy) This DB contains the data that is to be sent to the electronic key read/write. The DB is assigned to the Operator panel 02 (OP177B PN/DP).

DB162 Pan_02_DP_Diagnostic: (DB152 copy) This DB contains the device-specific diagnostic data of the EKS electronic key adapter. The DB is assigned to the Operator panel 02 (OP177B PN/DP).

DB163 Pan_02_User_Data: (DB153 copy) This DB is used to input and output the user data on the operator panel. The DB is assigned to the Operator panel 02 (OP177B PN/DP).

DB165 Pan_02_General_Data: This DB contains “general data“ that is used on the Operator panel 02 (OP177B PN/DP). (I/O fields with required input authorizations).

DB200 String_Initialize: This DB is used to “empty” written text fields on the operator panel. (To overwrite them with an “empty entry“).

Note: The EUCHNER company provides pre-configured data blocks for evaluation of the send or receive data in an example project. The DBs can be adapted to the specific requirements. The present application uses the DB150, DB151 and DB152 blocks from this example project, which have been adapted accordingly. (Analogously, DB160, DB161 and DB162)




V1.0 20.11.2007 21/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

Block Explanation

SFC13 DPNRM_DG: Reading the diagnostic data (Slave diagnostics). (Detailed information can be found in the online help on STEP 7)

SFC14 DPRD_DAT: Reading consistent data of a DP standard slave/PROFINET IO devices. (Detailed information can be found in the online help on STEP 7)

SFC15 DPWR_DAT: Writing consistent data to a DP standard slave/ PROFINET IO device. (Detailed information can be found in the online help on STEP 7)

SFC20 BLKMOV: Copying memory area. (Detailed information can be found in the online help on STEP 7)

SFC51 RDSYSST: Reading out an SSL part list or an SSL part list excerpt. Is used in the FC125! (Detailed information can be found in the online help on STEP 7)




V1.0 20.11.2007 22/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

4.2 Hardware configuration

The following screenshot shows the STEP 7 hardware configuration. Figure 4-2

Install the “EKS Profibus GSD file“ first. If you have installed the GSD file, the “EKS-PROFIBUS Module“ is available under ”PROFIBUS DP > Additional Field Devices > ID System > EUCHNER > EKS“.

Connect the EKS module to the existing PROFIBUS. Then select the corresponding module . In this case, the “Read/write 32 I/O” module. You can define the I/O area or apply the suggested value via the module properties.

Add a further EKS module for each additional electronic key adapter and repeat the steps and .

Note The EUCHNER EKS manual “Electronic-Key Adapter with Profibus-DP Interface” provides detailed information on different modules and their parameterization.




V1.0 20.11.2007 23/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

4.3 Description of program execution FC15 (Pan_01_EKS_Evaluation)

The FC15 program block contains the program for evaluating the EKS electronic key adapter for the operator panel 01 (MP277 Touch).

The figure below provides a schematic overview of the EKS data evaluation. Figure 4-3

Reading out the key data The output area of the electronic key adapter is used to read out the output data via the SFC14 and assign them to the DB150DBX... The data read out is split into two string variables and assigned to the DB153DBX... via the SFC20 .

The reason for this is that the string variable read out (DB150DBX...) consists of an “overall text”. This “overall text” must be split into “user name” and “password” for evaluation. This is done using the SFC20.

The “result” is then written to the DB153DBX... and output on the operator panel.

Writing data to the key The two string variables DB153.DBX... can be used to specify the user name and the password via the operator panel.

The two string variables are combined to one string variable via the SFC20 and assigned to the DB151.DBX... This string variable is assigned to the

input area of the electronic key adapter via the SFC15 and written to the electronic key read/write.




V1.0 20.11.2007 24/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

4.3.1 Structure of the DB150 and DB151 blocks

The DB150 and DB151 are data blocks that have been previously parameterized by EUCHNER. These data blocks are used for data exchange between the S7 controller and the electronic key adapter. The data blocks can be adapted to the specific user requirements. One data block with the structures of the DB150/DB151 is required for each EKS electronic key adapter. Copy the DB150/DB151 for this purpose and rename them accordingly.

Notes • Detailed information, for example, on the “status byte” is available in the EKS manual “Electronic-Key Adapter with Profibus-DP Interface“ (See also Chapter 9.1 Bibliographic references).

• The figures below referring to the DB150/DB151 may deviate from the current version of the EKS manual.

DB150 structure Figure 4-4

DB151 structure Figure 4-5




V1.0 20.11.2007 25/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

4.3.2 Program description NW 1 and 2 of the FC15

Figure 4-6

The data of the EKS electronic key adapter is read out via the SFC14.

LADDR:= Address in hex format. In this case, W#16#100 means address 256. (See also hardware configuration Chapter 4.2).

RECORD:= The start address of the data block used is specified for reading the “I/O data”. The length depends on the module used. (See also hardware configuration Chapter 4.2).

The SFC15 is used to write the data to the EKS electronic key adapter.

LADDR:= Address in hex format. In this case, W#16#100 means address 256. (See also hardware configuration Chapter 4.2).

RECORD:= The start address of the data block used is specified for writing the “I/O data”. The length depends on the module used. (See also hardware configuration Chapter 4.2).




V1.0 20.11.2007 26/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

4.3.3 Program description NW 4 of the FC15

Figure 4-7

Network 4 is used to specify the “number of the bytes read”. The byte number depends on the module used in the GSD file. (See description of the DB150/DB151 Chapter 4.3.1 – Number of bytes).

Note You can also permanently assign the string length (“28”) directly in the corresponding data block.




V1.0 20.11.2007 27/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc


Network 5 is used to write the user data to the electronic key read/write with (user name and password).

The user data is specified via two I/O fields (string variables) on the operator panel. These two string variables are combined to one string via the SFC20.

Function overview: Figure 4-8

The DB151.DBB4 variable (Send_Data_To_Transponder) has a string length of 28 bytes. Two string variables from the DB153 with a length of 10 bytes each are written to this area (28 bytes).

Area 01 (user name): DB151.DBB4 to DB151.DBB15

Area 02 (password): DB151.DBB16 to DB151.DBB27

Note In this example, not the entire memory area (28 bytes) of the electronic key read/write is written with data. The maximum length of user name and password for the user administration is limited to 10 characters.




V1.0 20.11.2007 28/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

Writing user data to the transponder: Figure 4-9

The DB151.DBX0.7 variable is set or reset on the operator panel via the “Writing transponder data” button. Writing the electronic key read/write is triggered by this function.

Writing the user data: User name: SRCBLK: DB153.DBX0.0, bytes 12

DB153.DBX0.0: => Start address of the user name DB153.DBB0 -> DB153.DBB11, number = 12 bytes

DSTBLK: DB151.DBX4.0

DB151.DBX4.0: => Start address of the “key contents”. (see DB151 structure, Chapter 4.3.1) DB151.DBB4 -> DB151.DBB15, number = 12 bytes

Password: SRCBLK: DB153.DBX12.0, bytes 12

DB153.DBX12.0: => Start address of the password DB153.DBB12 -> DB153.DBB23, number = 12 bytes

DSTBLK: DB151.DBX4.0

DB151.DBX16.0: => the “second” area. DB151.DBB16 -> DB151.DBB27, number = 12 bytes




V1.0 20.11.2007 29/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc


Network 6 is used to read out the contents of the electronic key read/write (user name and password) via the DB150.

To enable the user data to be read out and evaluated via the corresponding I/O fields (string variables), the contents of the electronic key read/write (DB150) have to be split into two separate string variables (DB153).

Function overview:

Figure 4-10

The DB150.DBB4 variable (Readout_Transponder) has a string length of 28 bytes. This area (28 bytes) is split into two string variables of 10 bytes each and written to the DB153.

Area 01 (user name): DB150.DBB24 to DB150.DBB35

Area 02 (password): DB150.DBB36 to DB150.DBB47

Note In this example, not the entire memory area (28 bytes) of the electronic key read/write is read out. The maximum length of the user name and password for the user administration is limited to 10 characters.




V1.0 20.11.2007 30/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

Reading out the transponder with the user data: Figure 4-11

Reading out the user data: User name: SRCBLK: DB150.DBX4.0


DSTBLK: DB153.DBX24.0, bytes 12

DB153.DBX24.0: DB153.DBB24 -> DB153.DBB35, number = 12 bytes

Password: SRCBLK: DB150.DBX16.0, bytes 12







V1.0 20.11.2007 31/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc


Network 7 is used to read out the diagnostic data of the DP slave (electronic key adapter).

Figure 4-12

The SFC13 is not processed (REQ), as long as the reading process has not been completed (BUSY).

LADDR: Configured diagnostic address of the DP slave in HEX format.

RECORD: Data block previously parameterized by EUCHNER for DP diagnostics.

Note Detailed information on SFC13 can be found in the STEP 7 online help.


Network 8 is used to reset the “Transponder present” evaluation signal in case of a failure.

A “global PROFIBUS diagnostics” is performed via the FC125 (OB1). When the respective slave fails, the bit associated with the DP slave is set.




V1.0 20.11.2007 32/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc


A delay time can be set in network 9 to delay the “Log-on” function on the operator panel.

The “DB150.DBX0.1” bit is used to determine whether a transponder is present in the read/write device. (See also Chapter 4.3.1 – DB150 structure, status byte)

Background: If the electronic key read/write is inserted in the electronic key adapter, the contents of the electronic key read/write are first read out via the S7 controller. This data is then transmitted to the operator panel to the parameters of the “Log-on” function.

This parameter transmission (user name and password) must be completed first before the “Log-on” function is executed on the operator panel.

Note If the selected time is too short, it is possible that the user will not be able to log on.

The delay time depends on the CPU cycle time and the communication load on the PROFIBUS.

500ms are set by default.




V1.0 20.11.2007 33/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc


Network 10 is used for the operator panel “log-on and log-off”. Figure 4-13

The DB15.DBW16 “auxiliary variable” is used to execute the “log-on and log-off” function on the operator panel.

If the electronic key read/write is inserted and the T15 delay time expired (see NW9), value “2” is assigned to the DB15.DBW16 variable.

As soon as the electronic key read/write is removed from the electronic key adapter (evaluation is performed via the DB150.DBX0.1 bit), value “-1” is assigned to the “DB15.DBW16” variable.

Background: The following limits have been assigned to the DB15.DBW16 variable in the WinCC flexible configuration:

• Upper limit: “1”

• Lower limit: “0”

Under “Events”:

• Upper limit exceeded -> “Log-on” function assigned

• Lower limit fallen below -> “Log-off” function assigned.

Thus, the “log-on” function is automatically executed if the limit is exceeded and the “log-off” function if the limit is fallen below. (depending on whether an electronic key read/write is inserted in the electronic key adapter)




V1.0 20.11.2007 34/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc


The “Screen_2” of the MP277 Touch features a button for deleting the data from the electronic key read/write.

This “function” is executed via network 11.

You need this function only if all the data is to be deleted from the electronic key read/write via the operator panel.

Figure 4-14

DB15.DBX18.0: The DB15.DBX18.0 variable is �set and reset

using a button on the operator panel.

SRCBLK: DB200.DBX0.0

DB200.DBX0.0: Auxiliary DB. This data block does not include any values (’ ’ is set for each string by default) number = 28 bytes



DB151.DBX0.7 This bit is used to write data to the electronic key read/write. (see DB151 structure - Chapter 4.3.1, status byte)




V1.0 20.11.2007 35/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

4.4 Description of program execution FC16 (Pan_01_Clear_DB_Data)

The FC16 is used to set the existing entries to a defined value for the operator panel_01 (slave failure) in DB150 “Pan_01_Read_Transponder” and DB152 “Pan_01_DP_Diagnostic” in the event of a failure of the electronic key adapter.


Functional Mechanisms of the WinCC flexible Project


V1.0 20.11.2007 36/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

5 Functional Mechanisms of the WinCC flexible Project

Here you find information on … • the WinCC flexible program structure.

5.1 WinCC flexible project structure

Overview The WinCC flexible project consists of two operator panels.

• MP277 Touch

• OP177 PN/DP

The structure and functional scope of both configurations is identical. The functions of OP177 PN/DP are divided into three screens. (MP277 Touch has two screens)

The description below applies to the MP277 Touch.

Figure 5-1




V1.0 20.11.2007 37/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

5.1.1 Configuration explanation for “Screen_1”

Overview of “Screen_1” (test page with user input request) “Screen_1” is called as a start screen.

Three different user groups with the three “users” assigned are configured. The user can make entries in the corresponding I/O fields depending on the user’s authorization.

Note This page is only a “test screen” to show the “automatic” user log-on to the operator panel and test the basic function principle.

Figure 5-2

(1), Current user display: The current user is shown in the output field.

The assignment is realized via the “Scheduler”. (Project tree > Device Settings > Scheduler).

The “ReadUser” function is executed from the function list via the “Change user” event and the current user is written to the variable.




V1.0 20.11.2007 38/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

(2), User groups: This project contains three user groups that have been assigned different authorizations.

• Group_01 -> Operator control

• Group_02 -> Operator control, monitoring

• Group_03 -> Operator control, monitoring and managing

(3), I/O fields: Three I/O fields, which have been assigned different authorizations, are configured in the project (Properties > Security).

• Operator control

• Monitoring

• Managing

The corresponding authorization must first be provided in Runtime before a value is entered.

(4), User assignment: The “table” shows the user assignment graphically. The user name corresponds to the “table heading”. The default password configured is the number “in brackets”.

• Inputs in the I/O field next to Group_01 may be performed by all users.

• Inputs in the I/O field next to Group_02 may only be performed by user “U2“ and “U3”.

• Inputs in the I/O field next to Group_03 may only be performed by user “U3”.

(5), “Log-off” button: The “Log-off” button is used for a manual log-off, irrespective of whether the electronic key read/write is still inserted in the electronic key adapter.

(Properties > Events > Click > Log-off)




V1.0 20.11.2007 39/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

5.1.2 Configuration explanation for “Screen_2”

Overview of “Screen_2” The “Screen_2” is used to output and specify data of the electronic key read/write via I/O fields.

The and buttons start the data transmission to the electronic key read/write.

The user data can be checked and edited if required via the user view .

Figure 5-3

(1), User view The user data can be checked and edited in Runtime via the configured user view.




V1.0 20.11.2007 40/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

(2), “Read out transponder data” This area is used to output the data of the electronic key read/write on the operator panel.

The following settings must be taken into account for both variables used. (Properties > General).

• Acquisition mode: Cyclically continued

• Acquisition cycle: 100ms

Note If the selected acquisition cycle of variables is too long, the log-on may be executed incorrectly.

(3), “Specifying transponder data” This area is used to specify the data (user and password) for the electronic key read/write via the operator panel.

Note The data (user and password) must comply with the existing data of the user view.

(4), Button “Delete transponder data” Pressing this button sets the bit of the “Visible_01” variable. This variable displays an additional “window” (grouped elements) in Runtime. It serves as a “confirmation dialog” to prevent accidental deletion of transponder data. (see the Figure 5-4 below)

Note The “window” can be displayed or hidden via “Layer 1” in the configuration view (Screen properties > Properties > Layer).




V1.0 20.11.2007 41/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

Figure 5-4

Grouped element: The grouped element consists of four composed individual elements.

• Rectangle

• Text field

• Two buttons (Yes / No)

Grouped element Visible / hidden:

Pressing the “Delete transponder data” button sets the bit of the “Visible_01” variable.

All elements of the grouped element use the “Visible_01” variable under “Properties > Animations > Visibility”.

If the “Visible_01” variable is set, the grouped element is displayed in Runtime.

“Yes” button: Two functions have been configured for the “Yes” button under “Properties > Events”.

Press: Pressing the button sets the DB15.DBX18.0 bit. The electronic key read/write is deleted by the controller via this bit (see also Chapter 4.3.10)

Release: Releasing the button resets the bit of the “Visible_01” variable. The “grouped element” is hidden again.

“No” button:




V1.0 20.11.2007 42/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

One function is assigned to the “No” button under “Properties > Events”.

Press: Pressing the button resets the bit of the “Visible_01” variable. The “grouped element” is hidden again.

(5), Button “Writing transponder data” Two functions have been configured for the “Writing transponder data” button under “Properties > Events”.

Press: Pressing the button sets the DB151.DBX0.7 bit. This bit starts the “command” for writing the electronic key read/write via the controller (see also Chapter 4.3.4).

Release: Releasing the button resets the DB151.DBX0.7 bit.

A color change has been configured for the headings “Reading transponder data”, “Transponder default parameter” and the button “Writing transponder data” under “Properties > Animations > Appearance”. These different colors allow you to determine whether an electronic key read/write is inserted in the electronic key adapter.

Transponder present -> Background color “green”

Transponder is not present -> Background color “yellow”




V1.0 20.11.2007 43/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

5.1.3 Configuration explanation for Log-on/ log-off function

The “log-on / log-off” function is executed via the DB15.DBW16 variable.

Three functions have been configured for this variable.

• Upper and lower limit

• Event “Upper limit exceeded”

• Event “Lower limit fallen below”

Upper / lower limit: The “1” value is set for the “upper limit” and “0” for the “lower limit” under the tag property “Properties > Settings”.

Figure 5-5




V1.0 20.11.2007 44/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

Event “Upper / lower limit exceeded”: Figure 5-6

If the controller detects that an electronic key read/write is provided in the electronic key adapter, value “2” is entered into the DB15.DBW16 variable via the controller (see also Chapter 4.3.9).

The “limit value monitoring” is used to execute the “log-on” function via the “Upper limit exceeded” event.

If the electronic key read/write is removed from the electronic key adapter again, value “-1” is entered into the DB15.DB16 variables via the controller (see also Chapter 4.3.9).

The “limit value fallen below” is used to execute the “log-off” function via the “Lower limit fallen below” event.

Note The following settings must be taken into account for the DB15.DBW16 variable used. (Properties > General).

• Acquisition mode: Cyclically continued

• Acquisition cycle: 100ms

If the selected acquisition cycle is too long, the log-on may be executed incorrectly.


Modifications to the Sample Program


V1.0 20.11.2007 45/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

6 Modifications to the Sample Program

Here you find information on … what you can do to adapt the sample project to your project environment.

6.1 Adapting the STEP 7 blocks

In this project, separate program blocks are assigned to each operator panel.

Operator panel_01 (MP277 Touch)

• FC15, FC16

• DB15, DB150, DB151, DB152, DB153, DB155

Operator panel_02 (OP177 PN/DP)

• FC20, FC21

• DB20, DB160, DB161, DB162, DB163, DB165

These blocks can be given any names and adapted to your individual requirements.

Note Please pay attention to the data structure of the data blocks previously parameterized by EUCHNER (e.g., DB150, DB151, DB152).

This data structure should not be changed.

6.2 Adapting the WinCC flexible configuration

You can adapt the WinCC flexible to your individual requirements.

6.2.1 Operator panels

You can use any operator panels that support a user administration.

6.2.2 Calling the “Screen 2”

In practice, the “Screen 2” would only be called using the corresponding user rights (Admin). This person may also write the corresponding user data to the electronic keys read/write.


Installation and Commissioning


V1.0 20.11.2007 46/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc


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

7 Installation and Commissioning

Here you find information on … the hardware and software to be installed, and the steps necessary for commissioning the example.

7.1 Installation of hardware and software

This chapter describes the hardware and software components to be installed. The description and manuals, as well as delivery information contained in the delivery scope of the respective products, should be observed in any case.

Hardware installation The hardware components are available in Chapter 2.3. For the hardware setup, proceed in accordance with the table below:

Table 7-1

No. Instructions Note 1. Install your S7-300/400 controller according to the

installation instructions. The following FAQ entry provides more information on this topic. http://support.automation.siemens.com/WW/view/de/15390415

---

2. Install your operator panel according to the installation regulations. The following entry provides more information on this topic (e.g, MP277 manual). http://support.automation.siemens.com/WW/view/de/23337820

---

3. Install the EKS electronic key adapter according to the EUCHNER installation instructions and set the corresponding PROFIBUS address using the DIP switches.

---

4. Connect all PROFIBUS nodes to the S7 controller via a PROFIBUS cable.

---

Note The installation guidelines must always be observed.






Installation and Commissioning


V1.0 20.11.2007 47/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

Installation of the standard software Table 7-2

No. Instructions Note 1. It is assumed that the software specified in Table 2-2

of Chapter 2.4 is installed on your PG/PC. Please observe the system requirements in any case. More information on this topic is available on the Customer Support pages on the internet.

Link to the Customer Support pages. http://support.automation.siemens.com

7.2 Installation of the application software

Table 7-3

No. Instructions Note 1. Transfer the STEP 7 configuration to your

S7 controller. Information on how to transfer a STEP 7 configuration to an S7 controller is available on the Customer Support pages on the internet.


2. Transfer the WinCC flexible configuration to your operator panel. Information on how to transfer a configuration to an operator panel can be found in the respective device manual.









Operating the Application


V1.0 20.11.2007 48/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

8 Operating the Application

Here you will find information on … how to operate all functions of this application.

Overview The essential functions have already been described in the previous chapters.

It is required that

• you have already transferred the STEP 7 configuration and the WinCC flexible configuration to the corresponding hardware,

• a connection between S7 controller and operator panel has been established,

• the required EKS electronic key adapters have been installed.

8.1 Calling the start page using the example of the MP277 Touch

Table 8-1

No. Instructions Note 1. The following start screen is displayed

after starting Runtime on the operator panel. Buttons in the permanent window (buttons displayed on all screens) • Button “Screen 1”

Use the “Screen 1” button to display this start page.

• Button “Screen 2” Use the “Screen 2” button to display the page for reading out and writing the electronic key read/write.

• Button “English (German)” Use this button to switch between German/English. The project is configured in German and English.

• Button “Terminate RT” Use this button to terminate Runtime of the operator panel.




V1.0 20.11.2007 49/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

8.1.1 Operating the “Screen 1” page

Table 8-2

No. Instructions Note 1. Use the “Screen 1” button to call screen

1. There are three I/O fields each with different user rights located on this screen. You have to log on first to be able to operate/enter values in these I/O fields. Log-on: The log-on is performed via the evaluation of the electronic key read/write inserted in the electronic key adapter. Alternatively, you can also log on “manually” by selecting an I/O field. A log-on dialog appears where you can enter the user data. Note: The log-on dialog always appears if an I/O field has been selected and no user has yet logged on with the corresponding authorization. If the operator has the appropriate user rights, he/she can enter values in the I/O fields. Note: The required user data - User name and password - can be found in the "Table"

. 2. Log-off:

Use the “Log-off” button to log off manually at any time, irrespective of whether an electronic key read/write is inserted in the electronic key adapter.




V1.0 20.11.2007 50/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

8.1.2 Operating the “Screen 2” page

Table 8-3

No. Instructions Note 1. Use the “Screen 2” button to call screen

2. Writing the electronic key read/write: • Insert an electronic key read/write

into the electronic key adapter. If the key is recognized, the heading color is changed and the “Writing transponder data” button turns green.

• Enter the user and password into the field under . The user in this example is: U3 password: 333

Note: The data (user and password) must comply with the existing data of the user view. • Press the “Writing transponder data”

button . The data is written to the transponder.

• Remove the electronic key read/write from the electronic key adapter.

2. Reading the electronic key read/write: • Insert the previously written electronic

key read/write into the electronic key adapter. If the key is recognized, the heading color is changed and the “Writing transponder data” button turns green.

• All users are displayed in the user view .

• The data of the electronic key read/write is output in the field under

.




V1.0 20.11.2007 51/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

No. Instructions Note 3. Deleting data of the electronic key

read/write: • Insert the previously written electronic

key read/write into the electronic key adapter. If the key is recognized, the heading color is changed and the “Writing transponder data” button turns green.

• Press the “Delete transponder data” button .

• A “confirmation dialog opens. Answer with “Yes” or cancel the process by clicking “No”.

• If you click “Yes”, the data is deleted from the electronic key read/write.

Note: You can rewrite the electronic key read/write at any time. • Remove the electronic key read/write

from the electronic key adapter.




V1.0 20.11.2007 52/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

8.1.3 General information on operation / configuration

Table 8-4

No. Instructions Note 1. Changes in the user view:

If you make changes to the user view, the electronic key read/write has to be updated subsequently with these changes. The user data cannot be automatically applied to the “text fields” from the user view for writing the transponder data.

---

2. Log-off time: If the plant operator has logged on via the system (electronic key read/write is inserted in the electronic key adapter), and the time upon which the user is automatically logged-off has elapsed, the user has to relog on to the system. Remove the electronic key read/write from the electronic key adapter and insert it again. The user is relogged on to the device.

---

3. Logging-on failed: If the log-on via the RFID system has failed, although you are sure that the user data on the electronic key read/write is correct, check the following in the configuration:

• Delay time of the log-on (set a longer time) (see Chapter 4.3.8).

• Check the variable parameters that are used for the log-on and off (see Chapter 5.1.3).

• Check the variable parameters that are used to read out the transponder data (see Chapter 5.1.3, number 2)

---


Literature


V1.0 20.11.2007 53/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

9 Literature

9.1 Bibliographic references

Table 9-1

Topic Title /1/ WinCC flexible

2005 User manual WinCC flexible 2005 Compact / Standard / Advanced Order no. 6AV6691-1AB01-0AA0 http://support.automation.siemens.com/WW/view/de/18796010

/2/ WinCC flexible 2005

MP277 manual Order no. 6AV6691-1DJ01-0AA0 http://support.automation.siemens.com/WW/view/de/23337820

/3/ WinCC flexible 2005

OP177 PN/DP manual Order no. 6AV6691-1DG01-0AA1 http://support.automation.siemens.com/WW/view/de/21084461

/4/ EUCHNER EKS manual

EUCHNER EKS manual, “Electronic-Key Adapter with Profibus-DP Interface”. Order no. 092009 (as of 20.11.07) http://www.euchner.de/

9.2 Internet links

Topic Title \1\ Reference to

this entry http://support.automation.siemens.com/WW/view/de/26481978

\2\ Siemens A&D Customer Support

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

\3\ Siemens A&D Customer Support

Tips and tricks for the topic of user administration http://support.automation.siemens.com/WW/view/de/24456113








http://support.automation.siemens.com/WW/view/de/ 26481978�

http://support.automation.siemens.com/WW/view/de/ 26481978�

http://www.ad.siemens.de/support�




History


V1.0 20.11.2007 54/54

Cop

yrig

ht ©

Sie

men

s A

G 2

008

All

right

s re

serv

ed

2648

1978

_App

likat

ion_

Ben

utze

rver

wal

tung

_RFI

D_D

OK

U_V

10_e

.doc

10 History Table 10-1 History

Version Date Modification

V1.0 13.12.2007 First edition

Documents

Applikation Benutzerverwaltung RFID DOKU V10