Access to S7-200 PLCs with a PDA/Smartphone to S7-200 PLCs with a PDA/Smartphone. ... based on...

Cover Sheet

Access to S7-200 PLCs with a PDA/Smartphone

SIMATIC S7-200, WinCC flexible RT

Configuration Example X2 September 2009

Applications & Tools

Answers for industry.

Table of Contents

Access to S7-200 PLCs with a PDA/Smartphone V1.0, ID Number: 39099329 3

Warranty, liability and support Note The application examples are not binding and do not claim to be complete

regarding the circuits shown, equipping and any eventuality. The application examples do not represent customer-specific solutions. They are only intended to provide support for typical applications. You are responsible for ensuring that the described products are 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 we cannot be made liable for any damage/claims beyond the liability clause described. We reserve the right to make changes to these application examples at any time without prior notice. If there are any deviations between the recommendations provided in these application examples and other Siemens publications – e.g. Catalogs – then the contents of the other documents have priority.

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

Any claims against us – based on whatever legal reason – resulting from the use of the examples, information, programs, engineering and performance data etc. described in this application example shall be excluded. Such an exclusion shall not apply in the case of mandatory liability, e.g. under the German Product Liability Act (“Produkthaftungsgesetz”), in case of intent, gross negligence, or injury of life, body or health, guarantee for the quality of a product, fraudulent concealment of a deficiency or breach of a condition which goes to the root of the contract (“wesentliche Vertragspflichten”). 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.

It is not permissible to transfer or copy these application examples or excerpts of them without first having prior authorization from Siemens Industry Sector in writing.

For questions about this document please use the following e-mail address:

[email protected]

mailto:[email protected]

Table of Contents


Foreword

Industry Automation and Drive Technologies Service & Support Portal

This document is from the Internet service portal of Siemens AG, Industry Automation and Drive Technologies. The link below takes you directly to the download page of this document.

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


Table of Contents


Table of Contents 1 Automation Problem............................................................................. 6 1.1 Application environment....................................................................... 6 1.2 Specific automation problem................................................................ 6 1.3 List of components – central station..................................................... 7 1.4 List of components – remote station .................................................... 8 2 Automation Solution ............................................................................. 9 2.1 GPRS communications ........................................................................ 9 2.2 Central station ...................................................................................... 9 2.3 Connection diagram of the system components.................................. 9 2.4 Web-based remote access ................................................................ 10 2.5 miniWeb storage paths....................................................................... 12 2.6 User administration ............................................................................ 13 2.7 MWSL script ....................................................................................... 14 3 Configuration ...................................................................................... 19 3.1 Installing and wiring the hardware...................................................... 19 3.2 Configuring the S7-200 CPU and downloading the user program..... 19 3.3 Configuring the central station ........................................................... 20 3.4 Accessing the web site....................................................................... 22 4 Code Elements................................................................................... 23 5 History ................................................................................................ 24

Automation Problem


Co

pyr

igh

t

Sie

me

ns

AG

20

09

All

righ

ts r

ese

rve

d

Co

nfig

ura

tionE

xam

ple

_X

2_S

7-2

00

_V1

d0_e

n.d

oc

1 Automation Problem

1.1 Application environment

Several remote S7-200 controllers are to be managed from a central station using the SINAUT MICRO SC remote control system. Data exchange is to take place via GPRS. In the central station, the WinCC flexible HMI system is to allow to visualize and operate the remote S7-200 stations.

At the same time, important process data is to be editable on a PDA. Changing the process data is to be possible only after entering a login consisting of user name and password.

Figure 1-1

PPI RS232

S7-200MD 720-3

S Q C

S

Remote Station 1 + 2 + n

PPI RS232

S7-200MD 720-3

S Q C

S

PPI RS232

S7-200MD 720-3

S Q C

S

Central Station

SINAUT MICRO SC

WinCC flexible RT+

sm@rtAccesssm@rtService

OP

C

INTERNET

GPRS

PDA

Internet Explorer

Monitoring data

Chaning data

Wireless (GPRS/WLAN)

MW

SL

HTML - page

RS1 + 2 + n

Overview

RS 1RS 2RS n

1.2 Specific automation problem

How can process data from WinCC flexible RT be edited with the aid of a PDA?

What must be observed when configuring?

How does data transfer from the remote station to the PDA work?

Automation Problem


Co

pyr

igh

t

Sie

me

ns

AG

20

09

All

righ

ts r

ese

rve

d

Co

nfig

ura

tionE

xam

ple

_X

2_S

7-2

00

_V1

d0_e

n.d

oc

1.3 List of components – central station

Products

Component No. MLFB/order number Note

LOGO! Power 24V/1.3A 1 6EP1 331-1SH02

SIMATIC MicroBox 427B 1 6ES7 647-7AA30-0QA0

SINAUT MICRO SC (License: for 8 stations)

1 6NH9 910-0AA10-0AA3 Available: 8, 64 and 256 stations

WinCC flexible 2007 RT 1 6AV6613-1BA51-2CA0 128 tags

Note The above-listed order number of the SIMATIC Microbox 427B includes the following system configuration:

Celeron M 900MHz; 400MHz FSB; 1024MB DDR2 SDRAM; 2GB Compact Flash; Windows XP embedded incl. SP2.

The system data can be adjusted at the following address: https://mall.automation.siemens.com

Instead of the MicroBox 427B, a standard Windows PC can also be used.

Note The WinCC flexible version specified here enables you to start and operate the Runtime file (*.fwx). 128 tags can be displayed. If you want to be able to also edit the project file (*.hmi), other WinCC flexible licenses are necessary.

For example, WinCC flexible Advanced ES (6AV6613-0AA51-2CA5)

You can also use an older or newer version of WinCC flexible RT. But then you have to convert the attached project to this version.

Accessories

Table 1-1

Component No. MLFB/order number Note

Router 1 Specialist dealers With port forwarding

Internet access 1 Internet provider Broadband Internet access recommended

https://mall.automation.siemens.com/

Automation Problem


Co

pyr

igh

t

Sie

me

ns

AG

20

09

All

righ

ts r

ese

rve

d

Co

nfig

ura

tionE

xam

ple

_X

2_S

7-2

00

_V1

d0_e

n.d

oc

1.4 List of components – remote station

Products

Table 1-2

Components No. MLFB/order number Note

LOGO! Power 24V/1.3A 1 6EP1331-1SH02

SIMATIC S7-200 CPU 221

1 6ES7211-0AA23-0XB0 DC

SINAUT MD720-3 1 6NH9720-3AA00

ANT 794-4MR antenna 1 6NH9860-1AA00

Accessories

Table 1-3


PC/PPI cable 1 6ES7901-3CB30-0XA0 COM

Miniature circuit breaker 1 5SX2116-6 1 pole B, 16A

DIN rail 1 6ES5710-8MA11 483 mm

Internet access 1 Internet provider Broadband Internet access recommended

SIM card 1 Wireless service provider Special M2M plans are mostly available for GPRS

Configuration software/tools

Table 1-4


STEP 7 Micro/WIN 1 6ES7810-2CC03-0YX0

Note A remote station is only required to show that the values can be written to or read in the controller using SINAUT MICRO SC. All CPUs from CPU221 rel. 1.21 upwards can be used.

To show the basic function of this Configuration Example, it is sufficient to use internal variables in WinCC flexible on the central station.

Automation Solution


Co

pyr

igh

t

Sie

me

ns

AG

20

09

All

righ

ts r

ese

rve

d

Co

nfig

ura

tionE

xam

ple

_X

2_S

7-2

00

_V1

d0_e

n.d

oc

2 Automation Solution

2.1 GPRS communications

For the S7-200, GPRS library blocks are available for port 0 or port 1.

With the aid of these blocks, communication from the S7-200 CPU to the central station is realized in combination with the MD720-3 GSM/GPRS modem.

2.2 Central station

The central station that consists of a PC is connected to the Internet. With the aid of SINAUT MICRO SC, it manages all configured connections to the remote stations. The integrated OPC server of SINAUT MICRO SC allows to visualize all process data with the aid of the WinCC flexible RT OPC client.

Note Further system explanations of GPRS and SINAUT MICRO SC can be found in Micro Automation Set 31. http://support.automation.siemens.com/WW/view/en/30321000

2.3 Connection diagram of the system components

Central station

Figure 2-1

L1

N

24VDC+

24VDC-

Miniaturecircuit breaker

INTERNET

SINAUT Micro SC

WinCCflexible

Internet access:Fixed IP address orDynDNS service


Automation Solution


Co

pyr

igh

t

Sie

me

ns

AG

20

09

All

righ

ts r

ese

rve

d

Co

nfig

ura

tionE

xam

ple

_X

2_S

7-2

00

_V1

d0_e

n.d

oc

Remote station

Figure 2-2

L1

N

24VDC+

24VDC-

Miniature circuit breaker

LOGO!Power6EP1331-1SH02

s

Input:AC 100-240V

Output: DC 24V/1,3AClaus 2

CPU 222DC/DC/DC

212-1AB22-0XB0

PORT1

RUN

STOP

s

SIMATICS7-200

SF

SINAUTMD 720-3

s

2.4 Web-based remote access

Sm@artAccess and Sm@rtService

To be able to remotely operate the stations configured in WinCC flexible RT with a PDA, WinCC flexible RT provides the “Sm@rtAccess” service and “Sm@rtService”.

Sm@rtAccess and Sm@rtService are options for WinCC flexible RT that enable the user to realize data exchange between HMI systems via TCP/IP connections (e.g., LAN or INTERNET).

miniWeb

The “miniWeb” web server is integrated in Sm@rtAccess. Using the “MWSL” script language (MiniWeb Server Language), the web server allows to access the WinCC flexible variable area. The language resembles JavaScript but forms a small subset.

The script is embedded in an HTML page. The HTML page is stored on the web contents of the “miniWeb” server. When this HTML page is called, a script is run on the server side. A temporary dynamic web site is provided within the scope of this action. Figure 2-3 illustrates this action.

Furthermore, the web server offers the option to manage several users with different access rights.

Automation Solution


Co

pyr

igh

t

Sie

me

ns

AG

20

09

All

righ

ts r

ese

rve

d

Co

nfig

ura

tionE

xam

ple

_X

2_S

7-2

00

_V1

d0_e

n.d

oc

Figure 2-3

INTERNET

Central Station

SINAUT Micro SC

WinCCflexible

Variable areafor localvisualization

Variable areafor localvisualization

Access to thevariable area andgeneration of anHTML page

Access to thevariable area andgeneration of anHTML page

PDA

Display of an HTML pageDisplay of an HTML page

Request on

HTML pageReturn of the

generated HTML page

SetVarGetVar

By default, the miniWeb server is used to gain remote access to WinCC flexible Runtime and to check the system status. The original start page that is called up when entering the web address (IP address) in a web browser is shown in figure 2-4.

However, the HTML structure can be changed as desired, for example to represent processes with the aid of process variables or to display values. This functionality is the basis of this Configuration Example.

Figure 2-4

Automation Solution


Co

pyr

igh

t

Sie

me

ns

AG

20

09

All

righ

ts r

ese

rve

d

Co

nfig

ura

tionE

xam

ple

_X

2_S

7-2

00

_V1

d0_e

n.d

oc

2.5 miniWeb storage paths

The miniWeb server is located in the “WinCC flexible 200x Runtime” folder of your WinCC flexible installation. It is run automatically after starting a Sm@rtAccess project.

The following three folders that are accessed belong to the miniWeb server:

SystemRoot

WebContent

WebService

When using WinCC flexible version 2005 or 2007, the folders are located in the default installation directory:

C:\Program Files\Siemens\SIMATIC WinCC flexible\WinCC flexible 200x Runtime\

Figure 2-5

When using WinCC flexible version 2008, the folders can be found in the following default installation directory:

C:\Documents and Settings\All Users\Application Data\Siemens\ HmiRTm\MiniWeb1.2.1

Figure 2-6

Automation Solution


Co

pyr

igh

t

Sie

me

ns

AG

20

09

All

righ

ts r

ese

rve

d

Co

nfig

ura

tionE

xam

ple

_X

2_S

7-2

00

_V1

d0_e

n.d

oc

The “SystemRoot” folder contains all relevant configuration files as XML files. The “WebServices” folder contains a configuration file for SOAP access, which will not be described in greater detail at this point.

The “WebContent” folder provides the actual HTML documents that are visible when accessing externally. All newly created HTML documents have to be stored here.

2.6 User administration

The “WinCC flexible 200x Runtime” folder contains the “UserDataBaseEdt.exe” file. With the aid of this file, users can be created and managed.

A user with limited access rights is required for this Configuration Example. Chapter 3 Configuration provides a detailed explanation of how to create a user with limited access rights.

Automation Solution


Co

pyr

igh

t

Sie

me

ns

AG

20

09

All

righ

ts r

ese

rve

d

Co

nfig

ura

tionE

xam

ple

_X

2_S

7-2

00

_V1

d0_e

n.d

oc

2.7 MWSL script

Integrating MWSL into an HTML document requires knowledge of Java and HTML programming. For a better understanding of the following descriptions, it is helpful to open, the belonging to this Configuration Example, HTML document with an editor, to catch the coherences better.

Accessing process variables

All commands described in the following sections require that WinCC flexible process variables be accessed. The call is performed via the storage path of the variable in WinCC flexible. Folder and variable name have to be separated by two backslashes: “\\”. For example:

CE_X2\\USER_Bool

Figure 2-7

Displaying values with GetVar() or WriteVar()

The function returns the value of a variable from a variable source. In this case, the variables are process variables from the WinCC flexible variable source.

To display a value, an MWSL script is written to the place in the HMTL document where the value is to be displayed. For example, as a “value” of an I/O field or directly on the page.

Call:

GetVar(“variable name”, “variable source”) or WriteVar(“variable name”, “variable source”)

When not using the variable source, you automatically gain access to the process variables.

Example 1:

Writing the value of the “USER_Bool” variable to the HTML page

or

Result when calling the HTML page:

true

Example 2:

Writing the value of the “USER_Bool” variable to an I/O field

Automation Solution


Co

pyr

igh

t

Sie

me

ns

AG

20

09

All

righ

ts r

ese

rve

d

Co

nfig

ura

tionE

xam

ple

_X

2_S

7-2

00

_V1

d0_e

n.d

oc

Result when calling the HTML page:

Changing values with SetVar()

This function writes process variables. For security reasons, only variables starting with the prefix “USER_” or “SESSION_” can be written.

Call:

SetVar(“variable name”, “value”)

Example 3:

Permanently setting the “USER_Bool” process variable to the value “1”. The change by the user on the client is not possible. The variable is always overwritten with the value “1”.

If the user is to be able to change values, this is possible only by evaluating the URL in the browser address bar.

By sending a value written in the I/O field or when using a button, the URL in the browser address bar is extended by the just changed variable name and value. The question mark “?” serves as a separator to the master URL.

Example 4:

Overwriting the “USER_Bool” process variable with the just entered value from the “Bool” input field. The value is, for example, “true”.

Result after pressing “Enter”:

Checking whether a variable exists using ExistVariable()

This command is used to check whether a variable exists. It returns TRUE or FALSE.

Call:

ExistVariable(“variable name”, “variable source”)

This command is mostly queried in an if condition to be able to react to the existence of a variable. Example 4 illustrates this query.

Automation Solution


Co

pyr

igh

t

Sie

me

ns

AG

20

09

All

righ

ts r

ese

rve

d

Co

nfig

ura

tionE

xam

ple

_X

2_S

7-2

00

_V1

d0_e

n.d

oc

Checking whether a user is logged in with the aid of ShareRealm()

This command indicates whether the current user is a member of the group transferred as a parameter. In this case, the command is used to check whether any user is logged in.

Call:

ShareRealm(“parameter”)

Permissible as parameters are:

“NO_REALM” (no group membership or no user logged in)

“ANY_REALM” (any group membership or user logged in)

“Group Name” (membership of a special group. Each group has different authorizations. To access process variables, the user must be a member of the “SoapUser” group.)

Example 5:

Disabling operation of an input field or a button when no user is logged in.

Result on the HTML page:

No user is logged in.

A user is logged in.

Using additional functions in the HTML document

Aside from the display of values, the values from the variables can also be edited and evaluated with all common JavaScript functions.

If you want to make style-related changes in the HTML document, JavaScript has to be inserted into the HTML document header. This JavaScript is then executed when calling the HTML page on the client. If the client is not Java-capable, the script will be ignored.

Automation Solution


Co

pyr

igh

t

Sie

me

ns

AG

20

09

All

righ

ts r

ese

rve

d

Co

nfig

ura

tionE

xam

ple

_X

2_S

7-2

00

_V1

d0_e

n.d

oc

As an example, figure 2-8 shows the code to change the background color of an I/O field for the values “true” or “false” of a variable.

Figure 2-8

Using the Login/Logout template

The miniWeb server already offers a user name and password prompt that can be integrated into each HTML page simply by copying and pasting the code. The code is written to the place where the Login or Logout field is to be displayed.

Figure 2-9

The result is as follows:

or

Updating the HTML page on the client

Since the MWSL script is run on the server, the user is only provided with a temporary image of the process values available when calling the HTML page. If current process values are to be displayed, the HTML page must be updated.

An update also has to be performed if process values have been changed via the HTML page and the changed values are not yet displayed.

HTML also provides the option to automatically update the page every x seconds. This function is useful when frequently changing process values are to be permanently monitored. However, this function also increases the data volume since the complete HTML page always has to be retransferred.

Automation Solution


Co

pyr

igh

t

Sie

me

ns

AG

20

09

All

righ

ts r

ese

rve

d

Co

nfig

ura

tionE

xam

ple

_X

2_S

7-2

00

_V1

d0_e

n.d

oc

Configuration


Co

pyr

igh

t

Sie

me

ns

AG

20

09

All

righ

ts r

ese

rve

d

Co

nfig

ura

tionE

xam

ple

_X

2_S

7-2

00

_V1

d0_e

n.d

oc

3 Configuration

3.1 Installing and wiring the hardware

Table 3-1

No. Instruction Note/picture

1. Mount the LOGO! Power, the S7-200 CPU 221 and the MD720-3 modem on a DIN rail.

2. Connect the controller and the modem to the 24 V DC supply voltage of the LOGO! Power.

See chapter 2.3.

3. Connect all ground connections to ground.

4. Connect the antenna to the modem.

5. Connect the modem to the controller using the PC/PPI cable. Use the following switch positions:

1 2 3 4 5 6 7 8

1 1 1 0 0 1 1 0

3.2 Configuring the S7-200 CPU and downloading the user program

Table 3-2

No. Instruction Note/picture

1. Open the file from table 4-1, no. 1, using STEP 7 Micro/WIN.

CE_x2a_Configuration_P0_V1d0.mwp

2. Perform the GPRS configuration in the data block.

PIN of the SIM card,

APN of your wireless service provider,

address of your central station

3. Download the project to the controller.

4. Wait until the modem has logged on to the central station.

5. Open the file from table 4-1, no. 3, using STEP 7 Micro/WIN.

CE_x2a_Userprogram_P0_V1d0.mwp

6. Download the project to the controller.

Note For a detailed configuration description, please refer to Micro Automation Set 31:



Configuration


Co

pyr

igh

t

Sie

me

ns

AG

20

09

All

righ

ts r

ese

rve

d

Co

nfig

ura

tionE

xam

ple

_X

2_S

7-2

00

_V1

d0_e

n.d

oc

3.3 Configuring the central station

SINAUT MICRO SC

Table 3-3

No. Action Remark

1. Connect your PC to the INTERNET.

2. Make sure that the used port 26862 is, if necessary, routed through the firewall and, if necessary, through a router on your PC.

If you have enabled a firewall on your PC, define an exception for port 26862.

When using a router, forward port 26862 to the internal IP address of your PC. (for example, using the “Port Forwarding” function or “Virtual Server”)

3. Copy the file from table 4-1, no. 7, to the SINAUT MICRO SC installation directory.

OPCM2M.xml

4. Restart SINAUT MICRO SC.

WinCC flexible Runtime

Table 3-4

No. Action Remark

1. Unzip the file from table 4-1 no. 6. WinCC_flexible_200x_CEx2_AccessPDA_v1d0_en.zip

2. Start the generated WinCC flexible project file (*.fwx).

WinCC flexible Runtime + sm@rtServer + miniWeb server are started

3. For experts, the WinCC flexible project file is also included.

4. Unzip the file from table 4-1, no. 5. WebContent.zip

5. Copy the file contents to the “WebContent” folder of your WinCC flexible Runtime.

See chapter 2.5.

Configuration


Co

pyr

igh

t

Sie

me

ns

AG

20

09

All

righ

ts r

ese

rve

d

Co

nfig

ura

tionE

xam

ple

_X

2_S

7-2

00

_V1

d0_e

n.d

oc

Creating a user

Table 3-5

No. Action Remark

1. Open the “UserDataBaseEdt.exe” file. See chapter 2.6.

2. Enter the administrator password.

Default: 100

3. In the “User Manager” tab, click on “New” and create a new user with password.

4. Go to the “Authorizations” tab and assign the rights for the “SoapUser” group.

5. Close the program by selecting the cross and confirm that you want to save your changes.

Configuration


Co

pyr

igh

t

Sie

me

ns

AG

20

09

All

righ

ts r

ese

rve

d

Co

nfig

ura

tionE

xam

ple

_X

2_S

7-2

00

_V1

d0_e

n.d

oc

3.4 Accessing the web site

Table 3-6

No. Action Remark

1. In the browser of your PDA, enter the address of your central station + HTML page.

http://111.222.333.444/CEx2_Start.html

2. Select a station.

By default, station 1 is created as a remote station.

By default, station 2 is created with internal variables of WinCC flexible

3. Log in with your user name.

4. Change the values as desired and monitor the changes in WinCC flexible Runtime on the central station or in the status table of your remote station.

Code Elements


Co

pyr

igh

t

Sie

me

ns

AG

20

09

All

righ

ts r

ese

rve

d

Co

nfig

ura

tionE

xam

ple

_X

2_S

7-2

00

_V1

d0_e

n.d

oc

4 Code Elements The software examples are available on the HTML page from which you downloaded this document.

Table 4-1

No. File name Contents

1 CE_x2a_Configuration_P0_V1d0.mwp STEP 7 Micro/WIN project for configuring the modem of RS 1

5. CE_x2b_Configuration_P0_V1d0.mwp STEP 7 Micro/WIN project for configuring the modem of RS 2

6. CE_x2a_Userprogram_P0_V1d0.mwp STEP 7 Micro/WIN project application for RS 1

7. CE_x2b_Userprogram_P0_V1d0.mwp STEP 7 Micro/WIN project application for RS 2

8. sinautmicrosc_flex_Px.mwl GPRS library for port 0 or port 1

9. CE-x2_Webcontent_Central_Station_v1d0.zip

HTML pages for miniWeb

10. CE-x2_WinCC_flexible_Central_Station_v1d0.zip WinCC flexible configuration for the central station

11. OPCM2M.xml Configuration file for SINAUT MICRO SC

History


Co

pyr

igh

t

Sie

me

ns

AG

20

09

All

righ

ts r

ese

rve

d

Co

nfig

ura

tionE

xam

ple

_X

2_S

7-2

00

_V1

d0_e

n.d

oc

5 History Table 5-1 History

Version Date Modification

V1.0 10/26/09 First edition

Date post:	21-Mar-2018
Category:	Documents
Upload:	ngodieu
View:	215 times
Download:	2 times