SIMATIC HMI Configuration Support for Migrators Migration to Windows-Based Systems

Preface, Contents

Converting ProTool Projects 1

Global Settings 2

PLC Drivers 3

Tags 4

Messages 5

Screen Objects 6

Standard Screens 7

Function Keys 8

Events 9

Functions 10

PLC Jobs 11

Recipes 12

Index

SIMATIC HMI

Configuration Support for Migrators Migration to Windows-based Systems

This manual is a component of "How to configure Windows-based systems": Order number 6AV6594-1MA06-1AB0

Release 12/02

Safety Guidelines This manual contains notices which you should observe to ensure your own personal safety, as well as to protect the product and connected equipment. These notices are marked as follows according to the level of danger:

Danger

Q

T

I

CTclp

SBGP

S

indicates an imminently hazardous situation which, if not avoided, will result in death or serious injury.

Warning indicates a potentially hazardous situation which, if not avoided, could result in death or serious injury.

Caution used with the safety alert symbol indicates a potentially hazardous situation which, if not avoided, may result in minor or moderate injury.

Caution used without safety alert symbol indicates a potentially hazardous situation which, if not avoided, may.

Attention indicates that unwanted events or status can occur if the relevant information is not observed.

Note draws your attention to particularly important information on the product, handling the product, or to a particular part of the documentation.

ualified Personnel Only qualified personnel should be allowed to install and work with this software. Qualified personnel within the meaning of the safety notices of this documentation are persons capable of giving due consideration to safety engineering standards when using this software on systems.

rademarks The registered trademarks of the Siemens AG can be found in the preface.

mpressum Editor and Publisher: A&D PT1

opyright Siemens AG 2002 All rights reserved Exclusion of liability he transmission and reproduction of this documentation and the exploitation and ommunication of its contents are not allowed, unless expressly granted. Violators are

iable for damages. All rights reserved, especially in the case of the granting of a atent or registration by GM.

We have checked the content of this publication for compliance with the described hard and software. However, discrepancies cannot be excluded, with the result that we assume no guarantee for total compliance. The information in this publication is checked regularly, and any necessary corrections are included in the following editions. We would be grateful for any suggestions for improvement.

iemens AG ereich Automation & Drives eschäftsgebiet SIMATIC HMI ostfach 4848, D-90327 Nuernberg

Siemens AG 2002 Technical data subject to change.

iemens Aktiengesellschaft

Release 12/02 Preface

ProTool V6.0 Service Pack 2 Configuration Support for Migrators i

1 Preface

Purpose This document forms part of the documentation package for the ProTool CS configuration software. It provides all information required for the creation and configuration of projects.

Notation Different font formats simplify orientation within the text:

�Output� Names of dialog boxes, fields and buttons are shown in quotation marks.

�File� > �Edit� Menu items are shown in quotation marks. Successive submenus/options are separated by arrows. The complete route to the menu option in question is always shown.

Trademarks The following names are registered trademarks of the Siemens AG:

• SIMATIC® • SIMATIC HMI® • SIMATIC Multi Panel® • SIMATIC Multifunctional Platform® • SIMATIC Panel PC® • HMI® • ProAgent® • ProTool® • ProTool/Lite® • ProTool/Pro®

The remaining trademarks in this publication may be trademarks, whose use by third parties for their own purposes could violate the rights of the owner.

Preface Release 12/02

ii ProTool V6.0 Service Pack 2 Configuration Support for Migrators

Customer and Technical Support Available round the clock, worldwide:

Johnson City Nuremberg

Singapore

SIMATIC Hotline

Worldwide (Nuremberg) Technical Support (FreeContact) Local time: Mon.�Fri. 8:00 to 17:00 Telephone: +49 (180) 5050-222 Fax: +49 (180) 5050-223 E-Mail: techsupport@ ad.siemens.de GMT: +1:00

Worldwide (Nuremberg) Technical Support (fee-based, only with SIMATIC Card) Local time: Mon.�Fri. 0:00 to 24:00 Telephone: +49 (911) 895-7777 Fax: +49 (911) 895-7001 GMT: +01:00

Europa/Africa (Nuremberg) Authorization Local time: Mon.�Fri. 8:00 to 17:00 Telephone: +49 (911) 895-7200 Fax: +49 (911) 895-7201 E-Mail: authorization@ nbgm.siemens.de GMT: +1:00

America (Johnson City) Technical Support and Authorization Local time: Mon.�Fri. 8:00 to 19:00 Telephone: +1 423 461-2522 Fax: +1 423 461-2289 E-Mail: simatic.hotline@ sea.siemens.com GMT: -5:00

Asia/Australia (Singapore) Technical Support and Authorization Local time: Mon.�Fri. 8:30 to 17:30 Telephone: +65 740-7000 Fax: +65 740-7001 E-Mail: simatic.hotline@ sae.siemens.com.sg GMT: +8:00

The languages spoken by the SIMATIC Hotlines are generally German and English � the Authorization Hotline is also provided in French, Italian and Spanish.

Release 12/02 Preface

ProTool V6.0 Service Pack 2 Configuration Support for Migrators iii

SIMATIC Customer Support Online Services

The SIMATIC Customer Support team offers you substantial additional information about SIMATIC products via its online services:

• General current information can be obtained

� In the Internet under http://www.siemens.com/simatic

• Current Product Information leaflets, FAQs (Frequently Asked Questions), Downloads, Tips and Tricks can be obtained

� In the Internet under http://www.siemens.com/automation/service&support

Training Center

Siemens offers a number of training courses to familiarize you with the SIMATIC S7 automation system. Please contact your regional training center or our central training center in D 90327 Nuremberg, Germany for details.

Telephone: +49 (911) 895-3200

Internet: http://www.sitrain.com

E-Mail: [email protected]

Other Sources of Assistance

In case of technical queries, please contact the Siemens representatives in the subsidiaries and branches responsible for your area.

The addresses can be found:

• In the Siemens Catalog ST 80

• In the Internet under http://www.siemens.com/automation/partner

• In the Interactive Catalog CA01 http://www.siemens.com/automation/ca01

Preface Release 12/02

iv ProTool V6.0 Service Pack 2 Configuration Support for Migrators

Release 12/02 Contents

ProTool Service Pack 2 Configuration Support for Migrators v

Contents

1 Converting ProTool Projects ...........................................................1-1 1.1 Convertible Projects................................................................................1-2 1.2 How to convert a Project.........................................................................1-4

2 Global Settings..................................................................................2-1 2.1 How to make Settings in the Control Panel ............................................2-4 2.2 How to configure a Buffer Overflow Message ........................................2-5 2.3 How to convert the Interface Area ..........................................................2-6 2.4 How to evaluate the Keyboard Operation...............................................2-8

3 PLC Drivers .......................................................................................3-1 3.1 How to convert a Project for the SIMATIC-S5-DP PLC..........................3-3 3.2 How to convert a Project with the SIMATIC-S5-FAP PLC .....................3-4 3.3 Note the following for the SIMATIC S5-AS511.......................................3-5 3.4 How to convert a Project with two SIMATIC S7-200 PLCs ....................3-6

4 Tags....................................................................................................4-1

5 Messages...........................................................................................5-1

6 Screen Objects..................................................................................6-1 6.1 Text Fields ..............................................................................................6-2 6.2 Input/Output Fields and Text or Graphic Lists ........................................6-3 6.3 How to convert the Date/Time Display ...................................................6-5 6.4 Buttons....................................................................................................6-7 6.5 Graphics and Character Graphics ..........................................................6-8 6.6 Bars and Trend Graphics......................................................................6-10

7 Standard Screens..............................................................................7-1 7.1 Post-processing ProTool Standard Screens ..........................................7-2 7.2 Post-processing ProAgent Standard Screens ........................................7-5

8 Function Keys ...................................................................................8-1

9 Events ................................................................................................9-1

10 Functions.........................................................................................10-1 10.1 Example: Switching between the Event Message Buffer

Display and the Event Message Page Display...................................10-11

11 PLC Jobs .........................................................................................11-1 11.1 Replacing PLC Jobs by Functions........................................................11-5

12 Recipes ............................................................................................12-1

Contents Release 12/02

vi ProTool Service Pack 2 Configuration Support for Migrators

Release 12/02 Converting ProTool Projects

ProTool Service Pack 2 Configuration Support for Migrators 1-1

1 Converting ProTool Projects

Easy Conversion using ProTool

Using the ProTool conversion function, you can convert projects for graphical displays (OP 25, OP 27, OP 35, OP 37, TP 27-6", TP 27-10", TP 37 and C7-626) to projects for Windows-based systems without a lot of effort. Since most part of the conversion is done completely automatic, migrating from a graphical display to a new Windows-based system is not complicated. In this documentation, you will find: ! Step-by-Step conversion instructions ! A precise reference how the functionality of the old project is mapped to

the new project ! Alternative routes in cases where a 1:1 mapping of the projects is not

possible

Note Information on converting projects from one Windows-based system to another Windows-based system can be found in the "ProTool Online Help for Windows-based Systems".

Converting ProTool Projects Release 12/02

1-2 ProTool Service Pack 2 Configuration Support for Migrators

1.1 Convertible Projects

Converting Graphical Display > Windows-based System

Using ProTool, you can convert each project that has been created for a graphical display to a project for a Windows-based system.

It is necessary for the conversion that the project does not exceed the system limits of the Windows-based operating device. An example: You want to convert a TP 27 project to a project for TP 170B. On TP 170B, a maximum of 100 tags can be configured. If the TP 27 project has more tags, the conversion is cancelled and an error message is displayed.

Result Optimization during Conversion

Not every source project can be converted equally well to every target project. The quality of the conversion depends on the extent of the differences between the source device and the target device. Some differences between devices can be adjusted by post-processing the converted project, e.g. in the case of differences pertaining to the number of the keys, device dimensions or performance class). Other device differences (e.g. pertaining to the functionality, quantity schedule or performance) may limit the functional scope of the converted project.

The following table shows the conversions which should be preferred for optimal results and the conversions which may pose restrictions. The columns list the graphical displays whose projects are used as the source; the rows list the Windows-based systems for which the target projects are intended.



Legend:

Prefered variant for a conversion: This conversion leads to the best result

Conversion possible, but the destination device varies, for example, in the number of the keys, device dimensions or performance class

Conversion possible, but there are some restrictions with regard to the functionality, quantity schedule or the performance.

Note Information on converting projects from one Windows-based system to another Windows-based system can be found in the "ProTool Online Help for Windows-based Systems".

Information on system limits, available keys and device dimensions can be found in the equipment manuals of the individual operating devices.

Note When you convert an existing configuration for a different destination device, close the converted configuration and open it again before performing changes.



1.2 How to convert a Project

Migration from a Graphical Display to a Windows-based System

If you want to migrate from a graphical display to a Windows-based system, you can use the existing project as the basis for your new project. Proceed as follows:

1. Use ProTool to convert your graphical display project to a new project for a Windows-based system.

2. After the conversion, check whether the new project meets your standards with regard to functionality and the visual design of the screens. Support is provided by the messages that ProTool displays during the automatic conversion in the system message window. The areas of the old project which could not be converted automatically are also indicated by these messages.

3. After checking the new project and making revisions where necessary, it can be operated from the Windows-based system.

Prerequisite

The source project must comply with the system limits of the target device. A reference of the system limits can be found in the equipment manual of the respective operating device and in the ProTool Online Help.

An example: You want to convert a TP 27 project to a project for TP 170B. On TP 170B, a maximum of 100 tags can be configured. If the TP 27 project has more tags, the conversion is cancelled and an error message is displayed.



1st Step: Automatic Conversion

The following procedure describes the procedure in stand-alone operation. In integrated operation, an additional dialog opens requesting the target device.

Procedure 1 Select "File" > "Convert" > "Setting". The "Conversion Setting" dialog opens. 2 Select the "Convert resolution" option if you would like to convert projects

between different operating units with different resolutions or display sizes. Select the "Smooth graphics (anti-alias filter)" option to insert an anti-alias filter while you are converting a graphic in order to replace the missing pixels by interpolation. This setting leads to softer transitions with photo-realistic displays. With drawings, the display quality increases, particularly when graphics are reduced in size, since all information on the screen is preserved. Note: If the settings you selected did not produce a satisfactory result, converted again with the modified settings as a test.

3 Select "File" > "Convert" > "Start". The "Save As" dialog opens.

4 In the "Save As" dialog, enter a name for the target project. The converted project is saved under this name. The source project can be found under the old name.

5 At "Device Type", select the Windows-based system to which the source project should be converted.

6 Start the conversion with "Save". The system checks whether the source project maintains the system limits of the destination device. If these limits are exceeded, the conversion is aborted and a message is issued. During conversion, you can see in the system message window which objects in the source project could not be converted on a one-for-one basis. When the conversion has been successfully completed, a corresponding message is output to the system message window. The source project is closed and the converted project is opened automatically in ProTool.



2nd Step: View and Function Control

You should check the following areas of the converted project:

Procedure 1 If necessary, drag the system message window with the mouse to size. This

window contains the messages read out by ProTool during the conversion. 2 Get an overview of the objects that could not be converted on a one-for-one

basis in the system message window on the "General" and "Clipboard" tabs. With these objects, you have to make them fit in order to restore them in the destination project or replace them with other objects.

3 Check the global settings. On Windows-based devices, some of these settings are no longer specified in the ProTool project but are made directly in the Control Panel of the operating device.

4 Display all screens one by one and check the layout with regard to the arrangement of the control elements.

5 Check the global assignment of the function and the system keys. The configured assignment of the keys to the LED image is automatically converted. If the source project contains function or system keys used to set Bits in the area pointers "System Keypad" or " Functional Keypad", it is necessary to configure functions for these keys in the target project with which Bits in the PLC can be set. If the operating devices of source and target projects differ with respect to the number of the keys, the key assignment cannot be converted 1:1. Some key assignments may have to be dropped entirely or they have to be converted differently (e.g. by means of buttons). Depending on the project, it can also be useful to reassign keys (e.g. to optimize the usability of the project).

6 Check the function calls for which you have received the message, in the ProTool system message window, that they have nor been completely converted. You will find detailed information on reworking in "Functions" in this documentation. Check whether PLC jobs are still effective and the initiating events have been correctly converted. In some cases you have to adapt the destination project and the PLC manually.

7 Only for source projects with standard screens: The contents of standard screens are not transferred during conversion. If the target project requires functions that were part of the source project standard screens, the corresponding ProTool objects have to be inserted. An example: The standard screen Z_MESSAGES can be replaced by the object "Message View". Detailed information can be found at the subject index "Standard Screens" in this documentation.



Procedure 8 Only for projects with recipes:

In the target project, replace the screens for transferring data records by the screen object "Recipe View". Recreate the data records which are still needed. Detailed information can be found at the subject index "Recipes" in this documentation.

9 Only for projects with status/control tag:

In the target project, replace the screens with status/control tag by screens with the screen object "Status/Control".

3rd Step: Post-processing the Target Project

How individual objects can be adjusted or replaced is described in detail in the relevant section of this documentation.



Release 12/02 Global Settings


2 Global Settings

Settings at the Operating Device

In projects for graphical displays, several device settings are specified during configuration in the "Target System" menu. In the case of Windows-based devices, some of these settings are no longer specified in the ProTool project.They must be made directly at the operating device by means of the Control Panel (= System Control on Windows CE devices) or they can be replaced by Windows standard functions.

During conversion, these settings cannot be transferred but must be made directly at the operating device upon startup or during runtime.

The settings concerned are:

• System > Settings, Group "Time/Date Format" With Windows-based system, the date and time format can be set at "Control Panel" > "Regional Settings".

• Target System > Settings, Group "Recipe" The parameter set is not supported by Windows-based systems.

• Target System > Screen/Keys, Check-Box "Dynamic Position" (only in the case of source projects for OP 35/37) This option is not supported by Windows-based systems. In Windows-based systems, the ProTool project runs in a Windows standard window. On touch panels with a display size of at least 10" and on keyboard devices with mouse, the ProTool window can be moved and resized (as usual under Windows).

• Target System > Printer In Windows-based systems, the printers are configured in the "Control Panel" > "Printers".

• Target System > Messages > Settings, Group "Overflow Warnings" Windows-based systems do not offer any buffer overflow warning or buffer overflow reporting. It is thus necessary to configure a user-defined message for the "Buffer Overflow" event.

Global Settings Release 12/02


Fonts at the Operating Device

Windows-based systems support more fonts and font sizes than graphical displays. During conversion, the fonts of all texts in all languages are first converted to the following fonts:

• For devices of the xP170x family to "Tahoma"

• All other Windows-based devices to "Courier New"

If necessary, you can alter the fonts after the conversion as follows:

"System Font" can be set in the "Target System" > "Fonts" menu. The system font is used, for example, to display messages on the operating device.

You can set the font for the texts of screen objects in the properties dialog of the relevant object or via the toolbar. If you are using the toolbar, you can change the font of all highlighted screen objects in one step using multiple selection.

Area Pointers

Detailed information on "Area Pointers" can be found in the "Communication User's Guide for Windows-based Systems".

During conversion, most area pointers are transferred 1:1. Only in the following area pointers do graphical displays differ from the Windows-based systems.

Area Pointers for Graphical Displays

Area Pointers for Windows-based Systems

"Interface Range" The data is exchanged with the PLC via the following area pointers: -"Coordination" - "Job Mailbox" - "Date/Time" Conversion: After the conversion, it is necessary to configure the new area pointers in the target project.

"Data Mailbox" This data area is always 5 words long in Windows-based systems. Data words 6 through n are not needed for Windows-based systems, since it is not possible to indirectly transfer data records to the PLC via the data mailbox. Information on how to transfer data records indirectly can be found at the subject index "Recipes" in this documentation. During conversion, this area pointer is automatically converted.



Area Pointers for Graphical Displays

Area Pointers for Windows-based Systems

"System Keypad" No longer available Replacement: Configure a function from the "Edit Bits" Group to the ACK, ESC, ENTER or HELP key. You can use these functions to set Bits that can be evaluated in the PLC program.

"Function Keypad" No longer available Replacement: Configure a function from the "Edit Bits" group to the function key that had been assigned up to now. You can use this function to set Bits that can be evaluated in the PLC program.

Note The area pointers "Trend Transfer Area 1", "Trend Transfer Area 2" and "Trend Request Area" cannot be created in TP 170B and in OP 170B.



2.1 How to make Settings in the Control Panel

Control Panel instead of Target System Menu

In projects for graphical displays, several device settings are specified during configuration in the "Target System" menu.

During conversion, these settings can not be transferred but must be made directly at the operating device upon startup or during runtime using the Control Panel.

Opening the Control Panel and making the relevant Settings

Procedure 1 Open the Control Panel:

At startup: Click the "Control Panel" button in the start menu. During runtime: - If a control has been configured for the function Start Control Panel, click on it. - Alternatively: Press CTRL + ESC to open the Windows CE start menu. Select the menu command "Settings" and open the Control Panel.

2 Click on the corresponding item to make your settings:

"Regional Settings" for country-specific settings such as date and time format

"Date/Time", to set the date and the time of the operating device

"Printers", to configure printers 3 To define the date and the time format:

Select the corresponding region scheme in the "Regional Settings" dialog on the "Regional Settings" tab and click on "OK". To set the date and the time: In the "Date/Time� dialog, select the corresponding time zone. Click on "Apply�. Set the date and the time. Close the dialog with "OK� or by pressing the ENTER key. To configure printers: Carry out the relevant configurations in the "Printers" dialog.



2.2 How to configure a Buffer Overflow Message

In Windows-based systems, there is no buffer overflow warning and reporting.

Instead, you can configure a user-defined message for the "Buffer Overflow" event.

Procedure 1 Call the "Global Functions" dialog via "Target System" > "Functions". 2 Double-click on "Other".

The "Messages" dialog will open. 3 Select "Buffer Overflow". 4 At the object selection, select the function Display System Message

Text from the "Messages" group and enter the corresponding message text. Note The message text can only be written in one language. This message text is displayed on the operating device in runtime in the case of a buffer overflow. Alternatively, you can also configure other functions or scripts to the "Buffer Overflow" event, e.g. a script with the function Print Report.

5 Apply your settings with OK.



2.3 How to convert the Interface Area

Subdividing the Interface Area

In Windows-based systems, the function of the "Interface Area" pointer is subdivided to three area pointers: "Coordination", "Job Mailbox" and "Date/Time". This distribution simplifies the data transfer between the operating device and the PLC. After the conversion, the new area pointers have to be inserted in the target project and set according to the source project.

Procedure 1

Double-click on "Area Pointer" on the left side of the project window. The "Area Pointer" dialog opens.

2 Select the area pointer "Coordination" and click on OK. 3 In the following dialog, enter the beginning of the PLC communication area as

the address. In many cases, you can simply configure the new area pointer to the location which had been reserved for the "Interface Area" in the source project. Example for S7 PLCs: Graphical Display: Interface Area n+0 through n+31 Windows-based System: Coordination n+0 through n+1 Job Mailbox n+4 through n+11 Date/Time n+15 through n+26

4 Proceed as outlined above for the area pointers "Job Mailbox" and "Date/Time". The communication between the operating device and the PLC is now configured as in the source project.

Note The data record transfer is not coordinated via the area pointer "Coordination", but via the area pointer "Data Mailbox" (word 4). Additional information can be found at the subject index "Recipes".

Detailed information on "Area Pointers" can be found in the "Communication User's Guide for Windows-based Systems".



Handling the Startup Bit

In Windows-based systems, the startup Bit will be temporarily be set to "0" by the operating device during the initial startup. As soon as startup has been finished, the startup Bit is set to "1". To evaluate the restart of the operating device in the PLC, you can evaluate the positive edge change of the startup Bit in the PLC program.

For the SIMATIC S5, note the following

In Windows-based systems, the existing interface DB of the source project can continue to be used.

Example:

Area pointer PLC of Group 1 PLC of Group 2 Job Mailbox DW32 through DW35 DW32 through DW35 Date/Time DW42 through DW47 DW66 through DW71

For the PLC of Group 2: Only one job mailbox can be configured in Windows-based systems. The PLC job with its 3 parameters is directly entered into this mailbox.



2.4 How to evaluate the Keyboard Operation

Replacement for the Area Pointers "System Keypad" and "Function Keypad"

The area pointers "System Keypad" and "Function Keypad" are not available in Windows-based systems.

If you want to evaluate in the PLC program whether a system key or function key has been pressed, you must configure a function from the "Edit Bits" group to the corresponding keys. For system keys, this is only possible for the ACK, ESC, ENTER and HELP keys.

So as not to adjust adjust the PLC program, you can use the function to set the same Bit that was set in the source project's system or function keypad image.



Assigning Functions to Keys after the Conversion

Procedure 1 To configure a global assignment to system or function keys select "Target

System" > "Screen/Keys". The "Screen/Keys" dialog will open.

2 Click on the key that you want to assign. The "Properties" dialog of the function key will open.

3 In the "Functions" tab, keep the preset event "Press Key", and at the object selection, select the function Set Bit when pressing a Key from the "Edit Bits" group.

4 Assign the function to the same Bit that the key has been assigned to in the source project. The system keys have been assigned the following Bits in the system keyboard image: ACK (Acknowledgement Key): 1. Word Bit 1 ESC: 1. Word Bit 3 ENTER: 1. Word Bit 6 HELP: 1. Word Bit 0

6 Close the dialog with OK.

Note If you want to evaluate whether a function key has been pressed in a specific screen in the PLC, you must configure the function Set Bit when pressinga Key at the desired function key locally in this screen. This ensures that the key is evaluated in the PLC during runtime only when this screen is open. If you assign functions to a function key screen-specifically (locally), the screen independent (global) assignment to the function key becomes disabled when selecting this screen.



Release 12/02 PLC Drivers


3 PLC Drivers

Automatic Conversion with the same PLC Driver on both Operating Devices

Most PLC drivers available for graphical displays are also available for Windows-based systems. They are automatically adjustded during the conversion. This applies to the following PLC drivers:

• SIMATIC S7-300/400

• SIMATIC S7-200 (one PLC)

• SIMATIC 500/505

• Allen-Bradley DF1 PLC-5

• Allen-Bradley DF1 SLC 500

• Allen-Bradley DH485

• GE Fanuc SNP/SNPX

• MITSUBISHI FX

• Modicon Modbus

• Omron Host-Link/Multilink

• Telemecanique Uni-Telway

For these PLC Drivers, note the following

Some PLC drivers of the graphical displays converted to Windows-based systems possess certain limitations. This applies to the following PLC drivers:

• SIMATIC S5-DP

• SIMATIC S5-FAP

• SIMATIC S5-AS511

• SIMATIC S7-200 (2 PLCs with PPI connection)

This documentation provides a separate description of these particulars.

PLC Drivers Release 12/02


PLC Drivers without Equivalent in Windows-based Systems

Some PLC drivers are not available for Windows-based systems.

If you try to convert a graphical project with a link to a PLC for which no driver is available in the Windows-based system, the SIMATIC S7-300/400 is set as the PLC driver in the target project. All tags will be disconnected from the PLC. This applies to the following PLC drivers:

• FREE SERIAL

• Telemecanique Adjust



3.1 How to convert a Project for the SIMATIC-S5-DP PLC

Conversion using the S5-AS511 PLC Driver

The SIMATIC S5-L2-DP PLC driver for graphical displays corresponds to the SIMATIC-S5-DP PLC driver for Windows-based systems. However, a direct conversion is not possible.

Instead, you have to

1. Switch to the SIMATIC S5-AS511 PLC driver in the project for the graphical display.

2. Start the conversion. 3. Switch to the SIMATIC-S5-DP PLC driver in the target project. Procedure 1 Open the source project. 2 Select "PLCs" in the project window. On the right, the PLC with the SIMATIC

S5-L2-DP driver is displayed. 3 Switch the PLC driver by double-clicking on the preset PLC. 4 In the "PLC" dialog, select the SIMATIC S5-AS511 as the PLC driver. Confirm

with OK. 5 Convert the project for the desired Windows-based system (menu

commands: "File" > "Convert" > "Start"). After the conversion, the target project is opened in ProTool.

6 In the target project, switch the PLC driver from SIMATIC S5-AS511 to SIMATIC-S5-DP. Proceed as described in step 2 to 4 .

7 In the PLC program, replace the standard-FB (FB 58) by the FB 158 for Windows-based systems. Otherwise errors in the communication between the PLC and operating device may occur.

Note Additional information on "Startup of a Windows-based System on a DP Network" can be found in the "Communication User's Guide for Windows-based Systems".



3.2 How to convert a Project with the SIMATIC-S5-FAP PLC

Conversion using the S5-AS511 PLC Driver

For the SIMATIC-S5-FAP PLC driver graphical displays, no direct equivalent is available for Windows-based systems. However, you can convert your project to the SIMATIC S5-AS511 PLC driver or to the SIMATIC S5-DP driver.

For this, you have to:

1. Switch to the SIMATIC S5-AS511 PLC driver in the project for the graphical display.

2. Start the conversion. 3. If necessary, switch to the SIMATIC S5-DP PLC driver. Procedure 1 Open the source project. 2 In the project window, select "PLCs". On the right, the PLC with the SIMATIC

S5-FAP driver is displayed. 3 Switch the PLC driver by double-clicking on the preset PLC. 4 In the "PLC" dialog, select the SIMATIC S5-AS511 as the PLC driver. Confirm


commands: "File"> "Convert"> "Start" ). After the conversion, the target project is opened in ProTool. You can retain the SIMATIC S5-AS511 PLC driver or switch to SIMATIC S5-DP.

6 Only, if you want to use the SIMATIC S5-DP PLC driver: In the target project, switch the PLC driver from SIMATIC S5- AS511 to SIMATIC-S5-DP. Proceed as described in step 2 to 4. In the PLC program, replace the standard-FB (FB 58) by the FB 158 for Windows-based systems. Otherwise, errors in the communication between the PLC and the operating device may occur.

Note Additional information on "Startup of a Windows-based System on a DP Network" can be found in the "Communication User's Guide for Windows-based Systems".



3.3 Note the following for the SIMATIC S5-AS511

After the Conversion

After converting a project with the SIMATIC S5 -AS511 PLC driver, you must observe the following points:

• Delete the standard-FB (FB 51) in the PLC program, since it is not needed for the communication. Otherwise, errors in the communication between the PLC and the operating device may occur.

• The 6XV1440-2A... standard cable can continue to be used for the MP 270 and MP 370. For all other devices (also for the MP 270B), a converter from V.24 to TTY is required.



3.4 How to convert a Project with two SIMATIC S7-200 PLCs

Converting after Profile Change

In projects for graphical displays, it is possible to use the SIMATIC S7-200 PLC driver to configure multiple PLCs, if the PPI profile is used.

In Windows-based systems, the connection with two PLCs is only possible with the MPI profile. For a successful conversion, you must therefore change the PLC profile in the source project before the conversion.

Procedure 1 Open the source project. 2 Select "PLCs" in the project window. On the right, the two PLCs with the

SIMATIC S7-200 driver are displayed. 3 Open the "PLC" dialog by double-clicking on the first PLC. 4 Click on "Parameters" and select "MPI " as the "Profile". Confirm the setting


commands: "File"> "Convert"> "Start" ). After the conversion, the target project is opened in ProTool.

Release 12/02 Tags


4 Tags

Converting Tags

During the conversion of a graphical display project to a project for a Windows-based system, tags are automatically converted. However, some properties and functionalities are not supported by Windows-based systems. In this case, your project must be customized and it may be that certain functionalities are no longer available.

Converting STRING tags

For the conversion of a graphic or text-based display project to a project for Windows-based systems, the StringChar data type is made available in the Windows-based projects. Special characters might be interpreted differently due to the different fonts. In projects for Windows-based systems, the hexadecimal value 00H is interpreted as the identifier for the end of the string. The following characters in the string are not displayed.

Attributes

The following attributes are not supported in Windows-based systems:

• Writing Tags indirectly It is no longer possible to transfer the tag values to the PLC via the "Data Mailbox". Additional information on how to customize a project can be found at the subject index "Recipes".

• Setting Tags "Off-line" In Windows-based systems, single tags linked to the PLC cannot be temporarily unlinked. However, you can temporarily unlink all those tags from the operating device that are linked to the same PLC (e.g. upon startup). For this purpose, use the function PLC_Link_Unlink. Additional information on this function can be found in the ProTool Online Help.

Transferring Decimal Places

In Windows-based systems, decimal places cannot be configured for the new tag.

The source project's tags with decimal places are converted as follows:

• The decimal places in the input/output fields of these tags are not affected.

• Recipes transfer the decimal places in the recipe view.

• The decimal places for bars, trends and messages are not transferred.

Tags Release 12/02


Different Treatment of the Initial Value

In Windows-based systems, the initial value is written to the tag not only at the first startup of the operating device but at each startup. Since tag values are not buffered, the value that has been waiting last cannot be written to the tag at startup.

In Windows-based systems, the tags are only initialized upon startup of the operating device. A later initialization of the tags is only indirectly possible by using a script. In this script, you evaluate the value change of the tag that contains the startup Bit: As soon as the value of the startup Bit changes from 0 to 1, the operating device is on the network. Depending on the value change of the startup Bit, you can set the value of the tag that is to be initialized to the initial value.

Note In Windows-based systems, the tag values are not buffered when the system is restarted. If the tag is linked to the PLC, the value stored in the PLC will be written to the tag after it has been linked to the PLC and the initial value will be overwritten.

Release 12/02 Messages


5 Messages

Converting Messages

During the conversion of a graphical display project to a project for a Windows-based system, the messages are automatically converted. However, some properties and functionalities are not supported by the Windows-based systems. In this case, your project must be customized and it may be that certain functionalities are no longer available.

In detail, the following features are not supported on Windows-based systems:

• Stand-by message: There is no special event message for no messages being queued .

• Attributes of messages: "Priority" is not supported. "Port" and "Relay" are not assigned a function, since Windows-based systems do not have ports or relays. After the conversion, those attributes are no longer available.

• Message tag type: The "Dec,Dec" tag type does not exist on Windows-based systems. After the conversion, a message tag of this type is treated as "Decimal".

Messages Release 12/02


Release 12/02 Screen Objects


6 Screen Objects

Conversion with Screen Objects

During conversion, screen objects are adapted to the Windows-based systems' demands and capabilities as far as possible. However, it is advisable to briefly check the results after the conversion has taken place.

Post-processing

In the following cases, post-processing will be necessary:

• Source project outputs date/time A special screen object is available for this output on Windows-based systems.

• Source project with character graphics Character graphics must be replaced by vector graphics for Windows-based systems. This also allows to dynamize the graphics.

• Source project has tiny symbolic input/output fields During conversion, the symbolic input/output fields are replaced by selection fields with a specific minimum height. This procedure may lead to space problems on some screens which then will require post-processing.

Additional Information

Specific information on the various screen objects can be found at the following subject indices:

Text Fields

Input/Output Fields and Text or Graphic Lists

Converting the Date/Time Display

Graphics and Character Graphics

Buttons

Bars and Trend Graphics

Screen Objects Release 12/02


6.1 Text Fields

Converting the Text Fields

The following customizations are made when the text fields are converted:

• The fields are increased in width by 2 pixels to the right and to the left. If the field is on the edge of the screen, it will be moved in.

• The text in the fields is vertically aligned in the center and horizontally aligned to the left.

• The following fonts are used: - For xP 170x: Tahoma - for all other systems: Courier New

Note When you converts a project for a graphics display to a project for a Windows-based system, note the following: Text fields in standard style with gaps that are not filled with blanks are not supported by Windows-based systems. A line break is inserted for each gap in the text for Windows-based systems.

Converting the Font Size

The font size is changed as follows:

Graphical display (in pixels) Courier New (in points) Tahoma (in points)

8x8 6 5 8x16 10 10 16x16 10 10 16x24 16 15 24x24 16 15 24x32 22 20 32x32 22 20 32x48 34 30 48x48 34 34



6.2 Input/Output Fields and Text or Graphic Lists

Converting the Input/Output Fields and Text or Graphic Lists

During the conversion of input/output fields and text or graphic lists, the following customizations are made:

• The fields are increased in width by 2 pixels to the right and to the left. If the field is on the edge of the screen, it will be moved in.

• The text in the fields is vertically aligned in the center and horizontally aligned as it has been in the source project.

• The following fonts are used: - For xP 170x: Tahoma - for all other systems: Courier New

• The font size is converted in the same way as it is converted in the text fields

• Decimal places of the source project tags are transferred to the target project as an attribute of the input/output field.

• Should an invalid value occur in a text or graphic list, nothing is displayed in the text or graphic list with a graphic display; either ### or a cactus screen is displayed with a Windows-based system.



Converting the Field Types

The "Input/Output Field" screen element that can be configured with different attributes in graphical displays corresponds to different screen objects in Windows-based systems. This is also relevant for the conversion: Depending on the attribute, the source project input/output field is converted to different screen objects of the target object.

Input/Output Field on a Graphical Display with Display

Input/Output Field on a Graphical Display of Type

Screen Object on Windows-based System

Dec, Hexadec, Binary, String

Input Input Field without Update


Input/Output Input Field with Update


Output Output Field

Text Input Selection Field without

Update Text Input/Output

Selection Field with Update Text Output

Symbolic Output Field Graphic Output

Graphics List

Post-processing

The screen object "Selection Box" used in ProTool is a standard-Windows object with a specific minimum height. If the source project used tiny input/output fields the automatically inserted selection fields may overlap each other after the conversion or they may overlap other screen objects.

In these cases, the screen layout has to be customized by hand. In most cases, it will suffice to move the screen objects.



6.3 How to convert the Date/Time Display

The Screen Object "Date/Time"

In Windows-based systems, the system time is displayed using the screen object "Date/Time". If, in the source project, a tag to display the system time has been configured using the function Date Input/Output or Time Input/Output you must replace it after the conversion by the screen object "Date/Time".

Replacing the Date/Time Display Tag by a Screen Object

Note The screen object "Date/Time" is not available on the TP 170A. Since the TP 170A does not have a buffered system clock, the system time of the PLC must be used instead. For this purpose, configure a date/time tag for an input/output field. A detailed example configuration can be found in the ProTool Online Help at the subject index "Displaying the Date and Time on the TP 170A".

Procedure 1 On the open screen, delete the input/output field that was used to display the

date and time. 2

Select "Date/Time Display" in the "Screen Objects" toolbar.

3 Use the mouse to draw the object to the desired position in the screen. The "Properties" dialog for "Date/Time Display" opens. It has several tabs.

4 On the "General" tab, set the basic properties for the object. In the "Display" field, set whether the "Date" or the "Time" or both shall be displayed. You can use the default "Data Source" setting "System Time" if the time and/or the date of the device are to be displayed during runtime. In Windows-based systems (in contrast to graphical displays), you do not need a tag with the corresponding function. These settings on the "General" tab suffice to configure the date/time display. If necessary, you can make the additional settings on the other tabs of the "Properties" dialog as described in step 5 to 10.

5 On the "Color" tab, you can set the border color and the color for the foreground and the background.

6 If necessary, you can define on the "Enable" tab under which conditions the "Date/Time Display" will be displayed or hidden during runtime.



Procedure 7 You can use the "Attributes" tab to change for example the foreground or

background color or to enable or disable flashing during runtime. 8 You can use the "Position" tab to specify the position for the screen object

down to one pixel. On this tab, you can also specify whether the position will be static or dynamically changed during runtime.

9 You can use the "Name" tab to name the screen object. You can use this name for example as a parameter in functions referring to the screen object.

10 You can use the "Font" tab to change the font properties, such as the font itself or the font size.



6.4 Buttons

Converting Buttons

In Windows-based touch panels, the screen objects used for button configuration are different from those used in graphical displays. During the conversion the source project's buttons are converted to the corresponding screen objects of the Windows-based system.

In detail, the following buttons are concerned:

Graphical Display Windows-based System

Button of Field Type "Visible" Button

Button of Field Type "Invisible" Invisible button

Set/Reset Bit Button with corresponding Function from the "Edit Bits" Group

Screen Selection Button with Function Screen_Selection_fixed

Light Indicator Status Area

Converting the Button Design

The target project buttons differ from the source project buttons as follows:

• Margin color and margin width are only transferred with "Status Area".

• "Button" type screen objects are assigned a 3-D frame as usual for Windows.

Post-processing

If you configure labelled buttons in a graphical display, line breaks are automatically inserted during configuration. These automatic line breaks are not transferred during conversion. Check the button labels in the target project and insert line breaks where necessary.



6.5 Graphics and Character Graphics

Converting Bitmap Graphics

All Bitmap graphics are transferred during the conversion and, if necessary, customized to the resolution of the target device. You can use the "Set Conversion" dialog ("File" > "Convert" > "Setting") to improve the quality of the converted graphics. The following options are available:

• "Convert Resolution" (default setting: enabled): Enable this option if you want to convert projects between operating devices with varying resolutions or display sizes.

• "Smooth Graphics (anti-alias filter)" (default: disabled): Enable this option if you want to use an anti-alias filter which replaces missing pixels by interpolation when converting a graphic. In photo realistic displays, this setting achieves softer transitions. For drawings, the quality of the display in particular increases when graphics are minimized since the complete graphic information remains unchanged.

If the settings you chose have not led to a satisfying result, try modified settings for the conversion.



Post-processing Character Graphics

Note Vector graphic objects are not available on the TP 170A. In projects that have been converted for this operating device, replace all character graphics by Bitmap graphics.

In Windows-based systems, character graphic characters are no longer available. After the conversion, use the screen editor to replace these objects with vector graphics. The following tools are available for this purpose:

Line

Rectangle

Rectangle with rounded edges

Circle

Polyline

Note You can also assign dynamic attributes to these objects (e.g. color change). To do so, call the "Properties" dialog in the context menu by pressing the right mouse button and make the desired settings on the "Attributes" tab. This allows you to indicate specific system situations during runtime. Additional information on this topic can be found in the ProTool Online Help at the subject index "Dynamic Attributes".



6.6 Bars and Trend Graphics

Converting Bars

When bars are converted, the following properties are transferred:

• Tag (all properties except decimal places)

• Direction

• Bar size (maximum value and minimum value)

• Display (border and limit line)

• Bar color

• Axis view (scale, axis label and axis position)

• Name

After the conversion, the following differences between the source and target project must be considered:

Graphical Display Windows-based System Border Color = Scale Color Border Color = black Places for axis labeling are set automatically

Places for axis labeling are configurable

If more positions are needed for the axis label, the entire object is enlarged to provide space for the label. The size of the bar is always constant.

If more positions are needed for the axis label, bar width is reduced. The size of the entire object is always constant.

The bar tag can be configured with decimal places.

The decimal places from the source project are lost after conversion.

Post-processing Bars

Since most part of the bar properties is transferred when bars are converted, it is hardly ever necessary to post-process the project. Only the following things need customization:

• Axis label Enter the number of the positions required for the axis label in the dialog "Properties" > tab "Axis".

• Object size Check the size of the bar after the conversion. If necessary, adjust the bar size in the screen editor.



Converting Trend Graphics

Multiplex trends cannot be configured for Windows-based systems. Therefore they are not transferred during conversion.

All other trend graphics are transferred almost completely. Only the following differences between the source and target project must be considered:

Graphical Display Windows-based System "Background" (dialog "Properties" > tab "Color") does not affect the scale background

"Background" also affects the scale background

The scale marks are set automatically The scale marks can be configured (dialog "Properties" > tab "Axis Scale")

Places for axis labeling are set automatically Places for axis labeling are configurable (dialog box "Properties" > Tabs "Y-Axis Right" and "Y-Axis Left")

The trend tag can be configured with decimal places

Decimal places from the source project are not available after the conversion

History trend plotted to left History trend is plotted to right History trend is plotted to right History trend plotted to left

Post-processing Trend Graphics

Since most part of the attributes of trend graphics is transferred during conversion, it is hardly ever necessary to post-process the project. Only a few things need customization:

• Scale marks Set the scale marks in the dialog "Properties" > tab "Axis Scale".

• Axis label Specify the number of the positions required for the axis label in the dialog "Properties" > tab "Y Axis, Right" and "Y Axis, Left".

• Plotting direction of history trends In the dialog box "Properties" > Tab "X-Axis", change the properties "New values from left " or "New values from right".



Release 12/02 Standard Screens


7 Standard Screens

Standard Screens are deleted

ProTool standard screens are no longer available for Windows-based systems. If the source project has standard screens, they are first emptied and then deleted together with their objects (e.g. tags) during conversion. However, only objects which are not referenced somewhere else in the project can be deleted.

Note During conversion ProTool recognizes standard screens and their objects by the object name starting with Z_. If your source project has objects that you have configured yourself and whose name starts with Z_, they can be deleted together with the standard screens. However, you can copy them from the source project to the target project after the conversion.

Post-processing

You can post-process your ProTool screens in the target project and delete those standard objects which are no longer required and have not been deleted automatically.

If there have been ProAgent standard screens in the source project, you can replace them in the target project by the ProAgent standard screens for Windows-based systems.

Standard Screens Release 12/02


7.1 Post-processing ProTool Standard Screens

Post-processing

In order to reconfigure the standard screen functions of the source project in the target project, most Windows-based systems offer standard ProTool objects. How you can integrate these objects into a screen in the target project and which settings you can make, can be read in the ProTool Online Help at the relevant subject index.

Below you find an overview which functionality of the standard screens you can replace by ProTool objects:

Standard Screen in the Source Project

Task Replacement on Windows-based Systems

Z_BACKUP Archive data (Backup)Read archived data (Restore)

On Windows CE devices, this setting can be made in the Control Panel using the Backup/Restore option.

Z_FORCE Control Tag Screen Object "Status/Control"

Z_STATUS_INP only for touch panels no longer required on Windows-based systems

Z_MESSAGES Edit Messages Print Messages

Screen Object "Message View"

To print: Use Reports Z_MARCHIVE Settings for Messages

Output To print: Use Reports

Z_PASSWORD Assign and change password Log-in

"Password List" screen object To link entry of a password with a log-in, configure a String tag for the input field. Configure the Log-In User function for the "Value change" event of this tag.You will find a detailed description in the ProTool online Help at "Configuring input fields for passwords".

Z_PRINTER Set the printer and the printer parameters.

On Windows devices, this setting can be made in the Control Panel using the "Printer" option

Z_HARDCOPY only for the OP/TP 27: Set parameter for hardcopy (ASCII/graphic)

no longer required on Windows-based systems



Standard Screen in the Source Project

Task Replacement on Windows-based Systems

Z_COLOR For OP/TP 27 only: Disable individual colors or modify color assignments for printing

No longer required on Windows-based systems

Z_RECORD 1 Basic Functions for using Data Records Screen Object "Recipe View"

Detailed information can be found in this documentation at the subject index "Recipes".

Z_RECORD 2 Expanded Functions for using Data Records


Z_SETTINGS General System Settings Screen Object "Date/Time" to enter

the date and time Detailed information can be found in this documentation at subject index "Converting the Date/Time Display".

Screen Object "Button" with the Function Change Language, to change the language.

Screen Object "Button" with the Function Switch Operating Mode, to switch between "On-line", "Off-line" or "Transfer" operating mode.

Z_STATUS Status Tag for PLC Diagnosis Screen Object "Status/Control"

Z_STATUS_INP only for touch panels no longer required on Windows-based systems

Z_SYSTEM_MEN Overview on Standard Screens available




Deleting the remaining Standard Objects

During conversion, only objects which are not referenced somewhere else in the project can be automatically deleted. If there are references left after conversion, you should check whether they are still necessary. It is advisable to delete by hand those objects that are no longer required or to replace them by references to new objects. The ProTool standard objects are identified by names starting with Z_.

Searching references is supported by the cross reference function:

Procedure 1 With the right mouse button, click on the object that has not been deleted

during conversion. 2 Select "Cross Reference" in the context menu. 3 Select "Show All" or double-click on an object to display all lower levels. 4 Select "Show Usage" to open the corresponding referenced object. 5 Delete the reference or replace it by a reference to the corresponding new

object.



7.2 Post-processing ProAgent Standard Screens

Deleting the remaining Standard Objects

During conversion, only objects which are not referenced somewhere else in the project can be automatically deleted. If, after conversion, there are references to standard objects left which could not be resolved, you should check whether they are still necessary. ProAgent standard screens are identified by names starting with ZP_. It is advisable to delete by hand objects that are no longer required or to replace them with references to new objects.

Searching references is supported by the cross reference function:

Procedure 1 With the right mouse button, click on the object that has not been deleted

during conversion. 2 Select "Cross Reference" in the context menu. 3 Select "Show All" or double-click on an object to display all lower levels. 4 Select "Show Usage" to open the corresponding referenced object. 5 Delete the reference or replace it by a reference to the corresponding new

object.

Integrating the ProAgent Diagnosis Screens for Windows-based Systems

ProAgent supplies standard projects for all Windows-based systems.

You can integrate these standard project screens into the target project to replace the source project diagnosis screens. The following table shows which diagnosis screens of graphical displays correspond to those of Windows-based systems.

Graphical Display Windows-based System ZP_PROAGENT ZP_PROAGENT ZP_ALARM ZP_ALARM ZP_UNITS ZP_UNIT ZP_UNITS_S7G ZP_UNIT ZP_DETAILAWL ZP_DETAIL ZP_DETAILLAD ZP_DETAIL ZP_DETAILSIG ZP_DETAIL ZP_STEP ZP_STEP ZP_MOTION ZP_MOTION



To ensure the interaction of ProAgent standard screens with the screens you configured yourself, you should prodeed as follows to integrate the ProAgent standard screens for the target device after conversion:

Procedure 1 Open the converted project. After conversion, the ProAgent standard screens

are almost empty. 2 Rename the following screens:

"ZP_DETAILSIG" in "ZP_DETAIL "ZP_UNITS" in "ZP_UNIT"

3 Open the STEP7 standard project supplied to you using Simatic Manager in the ProTool directory at Standard/ProAgent.

4 Open the ProAgent/ProTool standard project suitable for your destination device.

5 Copy all standard diagnostic screens using the menu options "Edit" > "Copy" and "Edit" > "Paste/Replace" from the standard project to your converted ProTool project. This replaces all the old ProAgent screens with those of the destination device.

6 The screens ZP_DETAILAWL, ZP_DETAILLAD and ZP_UNITS_S7G are no longer used and can be deleted.

Release 12/02 Function Keys


8 Function Keys

Converting Function Keys

During conversion, the source project key assignment is transferred to the target project key assignment. The keys are assigned to each other as follows:

• The keys to the left and to the right of the display are integrated one after the other starting at top left.

• The keys below the display are integrated one after the other from left to right.

• If K keys are available on the target device they are integrated one after the other starting with K1.

• The LED assignment configured is transferred as far as possible.

• The keyboard assignment area cannot be transferred since there is no corresponding area pointer in Windows-based systems. In this case, the key assignments have to be reconfigured in post-processing.

Converting Single Keys

The assignment of single keys and the LED assignment between the keys of source and target project depends on the operating devices. Especially if source and target device differ in the number of keys available, a 1:1 assignment is not always possible.

Conversion OP 25, OP 27 > OP 170B, OP 270 6"

Keys LED Assignment F1...F14 > F1...F14 F1...F8 > F1...F8 K1...K10 > K1...K10 K1...K10 > K1...K10 Conversion OP 25, OP 27 > MP 270, MP 270B, OP 270 10"

Keys LED Assignment F1...F8 > F1...F8 F9...F14 > F13...F18

F1...F8 > F1...F8

K1...K10 > K1...K10 K1...K10 > K1...K10

Function Keys Release 12/02


Conversion OP 25, OP 27 > MP 370, Panel PCs

Keys LED Assignment F1, F3, F5, F7 > S1...S4 F2, F4, F6, F8 > S9...12 F9...F12 > F1...F6

F1, F3, F5, F7 > S1...S4 F2, F4, F6, F8 > S9...12

The following keys are not transferred: K1...K10


Conversion OP 35, OP 37 > OP 170B, OP 270 6"

Keys LED Assignment F1...F8 > F1...F8 F13...F18 > F9...F14

F1...F8 > F1...F8

K1...K10 > K1...K10 K1...K10 > K1...K10 The following keys are not transferred: F9...F12, F19, F20, K11...K16

No transfer

Conversion OP 25, OP 27 > MP 270, MP 270B, OP 270 10"

Keys LED Assignment F1...F20 > F1...F20 F1...F12 > F1...F12 K1...K16 > K1...K16 K1...K16 > K1...K16 Conversion OP 35, OP 37 > MP 370, Panel PCs

Keys LED Assignment F1, F3, F5, F7, F9, F11 > S1...S6 F2, F4, F6, F8, F10, F12 > S9...14 F13...F20 > F1...F8

F1, F3, F5, F7, F9, F11 > S1...S6 F2, F4, F6, F8, F10, F12 > S9...14



Release 12/02 Function Keys


Converting Icons

The size of the icons that represent the keys will be adapted to the target device's display size. The size of the target icons will be:

Source Device Icon Size OP 25, OP 27, 6" Display 53 x 38 OP 35, OP 37, 10" Display 80 x 58

Target Device Icon Size OP 170B, 6" Display 53 x 38 OP 270, 6" Display 53 x 38 OP 270, 10" Display 80 x 58 MP 270, 10" Display 80 x 58 MP 270B, 10" Display 80 x 58 PC 670, 10" Display 62 x 42 MP 370, 12" Display 80 x 56 PC 670, 12" Display 78 x 53 PC 870, 12" Display 78 x 53 FI 25 78 x 53 PC 670, 15" Display 100 x 69 PC 870, 15" Display 100 x 69 FI 45 100 x 69

Post-processing

1. If, in the source project, graphics or text fields have been used to describe function keys, check their assignment on the display of the target project.

2. If, in the source project, the "Function Key Assig." and "System Key Assig." area pointers have been used, it will be necessary to replace this functionality. Configure the function Set_Bit_upon_Key_Operation from the "Edit Bits" group for the corresponding key (menu "System"> "Screen/Keys"). Assign the function the same Bit that has been assigned to the source project key.

Function Keys Release 12/02


Release 12/02 Events


9 Events

Converting Events

Only part of the function triggering events are transferred without changes during conversion. Some events are not required any longer because of the different functionality of the operating devices or cannot can be configured any more. In this case, you may need to post-process the target project to achieve the source project functionality.

Events being transferred 1:1

For the following events, no post-processing is necessary after the conversion:

Graphical Display Windows-based System Press Key Press Key Release Key Release Key Select Field Select Field Exit Field Exit Field Select Screen Generate Screen Exit Screen Clear Screen Buffer Overflow Buffer Overflow

Events Release 12/02


Events being only transferred with Changes

For the following events, the functionality has either changed or they can no longer be configured in Windows-based systems. The table provides information on the workarounds available which can be inserted when post-processing the target project. Additional information (e.g. detailed instructions) can be found in other sections of this documentation and in the "ProTool Online Help for Windows-based Systems"

Graphical Display Windows-based System Explanation/Replacement/WorkaroundInitialization ---- In Windows-based systems, tags are

initialized as a rule upon each startup of the operating device. The startup Bit can be evaluated to replace the event.

Before Tag Initialization

cannot be configured In Windows-based systems, tags are initialized as a rule upon each startup of the operating device. The startup Bit can be evaluated to replace the event.

After Tag Initialization

cannot be configured In Windows-based systems, tags are initialized as a rule upon each startup of the operating device. The startup Bit can be evaluated to replace the event.

Communication in Progress The function SetInitial Valueof Tag can be configured for this event. In this case, an initial value is set in the tag upon each startup of the operating device and, simultaneously, the value is written into the PLC.

cannot be configured In Windows-based systems, tags are initialized as a rule upon each startup of the operating device. The startup Bit can be evaluated to replace the event and if the value has been changed with the function SetValue, the value for a tag with PLC connection can be set.

Release 12/02 Events


Graphical Display Windows-based System Explanation/Replacement/Workaround Data Input always triggers the functions configured for it when something has been entered on the operating device irrespective of whether the tag value has changed.

Change Value alway triggers the functions configured for it whenever the tag has changed its value (no matter whether in the PLC or via data input on the operating device). If a frozen value is entered on the operating device, the "Change Value" event is not triggered.

To trigger input on the operating device only: Configure an addititional function of the group "Set Bit" for the ENTER key (used to terminate the input) and evaluate the set Bit.

Data Output only triggers the functions when the value has been changed in the PLC.

Value Change alway triggers the functions configured for it whenever the tag has changed its value (regardless, whether in the PLC or via data input on the operating device.

---

Read Data Record Tag

not necessary Transferring data records in Windows-based systems simplified

Read Data Record not necessary Transferring data records in Windows-based systems by means of functions (e.g. Data_Record_DAT_to_SPS) or with PLC jobs (e.g. 70 "Write Data Record into PLC"). To find out the transfer status, evaluate the return value of the function or word 4 ("Status Word") of the data mailbox.

Write Data Record not necessary Transferring data records in Windows-based systems by means of functions (e.g. Data_Record_SPS_to_DAT) or PLC jobs (e.g. 69 "Read Data Record from PLC"). To find out the transfer status, evaluate the return value of the function.

Read Message Tag

cannot be configured Configure the functions for the "Message Arrives", "Message Acknowledged" or "Message Departs" events.

Delete EM Buffer cannot be configured In combination with the function DeleteMessage Buffer, call the function SetBit and set the Bit of a tag without PLC connection. Configure those functions for the "Change Value" event of the tag, which have been configured for the "Delete EM Buffer" event in the source project.

Events Release 12/02


Graphical Display Windows-based System Explanation/Replacement/WorkaroundDelete AM Buffer cannot be configured Together with the Delete Message

Buffer function, call the Set Bit function and set the Bit of a tag without PLC connection. Configure those functions for the "Change Value" event of the tag, which have been configured for the "Delete AM Buffer" event in the source project.

Repeat Key (TP only)

cannot be configured ---

Print cannot be configured Together with the functions from the "Print" group, call the Set Bit function and set the Bit of a tag without PLC connection. Configure those functions for the "Change Value" event of the tag, which have been configured for the "Print" event in the source project.

Release 12/02 Functions


10 Functions

Converting Functions

Only a part of the functions is transferred without changes during conversion. Some functions are no longer required because of the different functionality of the operating devices or cannot can be configured any more. In this case, you may need to post-process the target project to achieve the source project functionality.

Functions being transferred 1:1

For the following functions, post-processing is not necessary after conversion:

Graphical Display Windows-based System Screens Select Screen Frozen Select Screen Dynamic Select Screen 1 Variable Select Screen Dynamic Select Screen 2 Variable Select Screen Reset Select Screen Reset Select Screen

PROFIBUS Screen Number (TP only) PROFIBUS Screen number (TP only)

Edit Bits Reset Bit Reset Bit Reset Bit in Word Reset Bit in Tag Set Bit Set Bit Set Bit upon Key Operation Set Bit upon Key Operation Set Bit in Word Set Bit in Tag Set/Reset Bit in Word Set/Rest Bit in Word Set/Reset Bit Set/Rest Bit Direct Key (TP only) Direct Key (TP only) Print Start/Stop Hardcopy Print Screen Messages Event Message Window Display Event Message Window Delete Event Message Buffer Delete Message Buffer,

Parameter "Buffer Type" = 1 = Event Messages

Display Event Messages

Functions Release 12/02


Graphical Display Windows-based System Parameter "Display" = 0 = Page Parameter "Display" = 1 = Buffer

Display Event Message Page Display Event Message Buffer

Message Log ON/OFF Message Log On/Off Display Messages Parameter "Message Type" = 0 = Alarm Messages Parameter "Message Type"= 1 = Event Messages

Display Alarm Message Page Display Event Message Page

Delete Alarm Message Buffer Delete Message Buffer, Parameter "Buffer Type" = 0 = Alarm Messages

Display Alarm Messages Parameter "Display"= 0 = Page Parameter "Display"= 1 = Buffer

Display Alarm Message Page Display Alarm Message Buffer

Calculations Tag: Value minus/plus Value plus Tag: Set Value Set Value System settings Display Help Text (TP only) Display Help Text (TP only)

Clean Screen (TP only) Clean Screen (TP only)

Acoustic Signal (TP only) Acoustic Signal (TP only)

Touch Calibration (TP 37 only) Touch Calibration (TP only) Keyboard Page up Page up Page down Page down Switch Switch Operating Mode Switch Operating Mode Change Language Change Language



Functions being only transferred with Changes

For the following functions, the basic realization of the functionality has either changed or they cannot can be configured any more in Windows-based systems. The table provides information on workarounds available which can be inserted in the target project when post-processing. Additional information (e.g. detailed instructions) can also be found in other sections of this documentation and in the "ProTool Online Help for Windows-based Systems".


Explanation/Replacement/ Workaround

Edit Bits Initialize Bitduring Startup

not required In Windows-based systems, the initial value is written to the tag not only at first startup but upon each startup of the operating device.

Reset BOOL Variable not supported --- Set BOOL Variable not supported --- Data Record Select Data Record Edit data record Delete data record Data record: DAT >OP Data record: DAT >OP/SPS Data record: OP >DAT Data record: OP >SPS Data record: SPS >OP Data record: SPS >OP/DAT Format disk

Functions are mapped differently

Windows-based systems provide the screen object "Recipe View" and new functions for transferring data records. Detailed information can be found at the subject index "Recipes" in this documentation.





Date/Time Date and Time Date Input/Output Time Input/Output

Functions are not required

Windows-based systems support the screen object "Date/Time". As a result, the display of the date and time has basically changed. Detailed information can be found at the subject index "Converting the Date/Time Display" in this documentation.

Print Automatic GraphicsPrint

Not supported On Windows-based systems you can output messages as follows: ASCII mode: By means of automatic message logging ("System" > "Messages" > "Settings", check box "Log" selected) Graphics mode:

By means of a report with the object "Print Message". With projects in languages having non�ASCII characters you can output messages as a report.

Graphics Mode forReport of ScreenLists

not required In Windows-based systems, screens and reports are always printed in the graphics mode.

Print Screen List not supported Copy the screens into a report and print it using the function Print Report.

Print Messages not required

Insert the "Print Messages" object in a report. Activate the "Alarm Messages" and/or "Event Messages" classes on the "Messages" tab. Print the report using the function Print Report.





Print Messages withFilter 1 Print Messages withFilter 2

Functions are not supported

Replace these functions by a report with the "Print Messages" object. In Windows-based systems, messages can only be filtered according to the message type. All other attributes of messages can only be displayed and printed (setting on the "Messages" and "Columns" tab).Print the report using the function Print Report. During runtime, the message view can be sorted according to columns by double-clicking on the relevant column heading. To print contents which are temporarily limited, Windows-based systems can use the message archive. This is where a defined time segment of an archive can be recorded via the report.

Printer Parameter Printer Parameter(Anchor) ColorAssignment forPrinter Hardcopy Parameter HardcopyParameter(Anchor)


Make the relevant settings in the Control Panel of the operating device

(Option: "Printers").

Messages Screen For ShortMessage Page (TPonly)

Function not required Response of alarm message indicator for Windows-based systems in Runtime:if the flashing alarm message indicator is touched, only the alarm message window is placed on top. If the non-flashing alarm message indicator is touched, the alarm message page is opened.





Switch EMPage/Buffer

Display EventMessage Page

In Windows-based systems, the event message page and the event message buffer can be displayed using the functions Display Event MessagePage and Display EventMessage Buffer. An example configuration for switching between these displays can be found at the subject index "Example: Switching between the Event Message Buffer Display and the Event Message Page Display" found in this documentation.

Switch AMPage/Buffer

Display AlarmMessage Page

In Windows-based systems the system message page and buffer can be viewed using the functions Display SystemMessage Page and DisplaySystem Message Buffer. To switch between the display of the system message buffer and the system message page, you can adapt the "Example: Switching between Event Message Buffer Display and Event Message Page Display" accordingly. You will find it in this documentation.

Operate MessageScreen (TP only)

Function is not required

In Windows-based systems, the message window, message page, message buffer and message view have a scroll bar. Help texts can be called by pressing the "Help" button. Switching between the message page and the message buffer can be realized as described under Switch EMPage/Buffer .





Filter Messages Function is not supported

In Windows-based systems, messages are displayed using the "Message View" screen object. Messages can only be filtered by using the settings on the "General" tab. Filtering according to "Priority", "Ack. Group" and "Status" is not supported. By double-clicking a column heading, the message view can be sorted during runtime according to the criterion shown in this column (only for the "Date" and "Time" columns).

Buffer OverflowWarning

Function is not supported

To replace the function BufferOverflow Warning, you can configure the function DisplaySystem Message Text for the global event "Buffer Overflow". You can use this function to display your own message text. The message text is restricted to one language.

Alarm MessagesFirst/Last

Function not supported

For Windows-based systems you can set the sort order for the alarm message window, the alarm message page, and the alarm message buffer by choosing "System" > "Messages " > "Settings" from the menu. You can set the sort order on the "Columns" tab for each message view. In Runtime you can sort the message view, by double-clicking on a column heading, according to the criterion displayed in this column (only for the "Date" and "Time" columns).





Password Define Password Define PasswordLevel Display Passwords


Windows-based systems support the "Display Password" screen object. You can use this object to authorize operators to manage the passwords of other operators and to assign operator authorizations.

Enter Password Function not supported

For entering a password, configure an input field with the "Password" display. To link password entry with a log-in, configure a String tag for the input field. Configure the " Log-In User" function to the "Value change" event of this tag. Furthermore, a password level can be assigned to most of the ProTool objects on the "Enable" tab. If a password-protected control is operated in Runtime without the operator having been provided with the required password level, a log-in window opens for entering the password. To transfer all passwords of a project to another project or to another operating unit, use the function Import/ExportPasswords.

Calculations Set Initial Valuefor Tag


In Windows-based systems, tags are initialized as a rule upon each startup of the operating device. To write the initial value of a tag also into the PLC, evaluate the startup Bit and use the function SetValue to set a tag with PLC connection to the required value for the "Change Value" event.





Scale Linear 1 Scale Linear 2

"Scaling" tab in the "Properties" dialog box for the tag

The scaling function is automatically entered, after conversion, in the "Properties" dialog box of the tag on the "Scaling" tab. Note: The functions Scale Linear 1 and Scale Linear 2 refer to the conversion of the value of a tag to the value of a second tag. They therefore cannot be used here.

Scaling square 1 Scaling square 2


Use the appropriate scripts.

Status/Control Tag S5 Status/ControlInit 1 S5 Status/ControlInit 2 S5 Control Tag S5/S7 StatusStart/Stop S5/S7 Status Tag S5/S7 DeselectStatus/Control S5/S7 SelectStatus/Control S5/S7 Control Input

S5/S7 HideStatus/Control

S5/S7Status/ControlIdentification

S7 Status/ControlInit 1 S7 Control Tag


Insert the "Status/Control" screen object into the screen which, in the source project, included the functions from the "Status/Control Tag" group. You can use this screen object to replace all functions of the "Status/Control Tag" group. Note: The "Status/Control" screen object cannot be used for S7 200 PLC .





System Settings Backup/RestoreModule

Function is not required

On Windows CE devices, if you want to transfer all data of a Windows-based system to a storage card, you can use the Control Panel with the Backup/Restore option. Alternatively you can use the Backup/Restore function of the ProSave service tool. To save single data records to a storage card or to read them from there, you can use the functions Export DataRecord and Import DataRecord.

Dim Screen Function is not required

Windows-based systems can dim the brightness of the screen or activate a screen saver after a period of time that can be set by the user.

You can use the "Screensaver" option to make both settings in the Control Panel.

Adjust Contrast This function continues to be available for touch panels with STN display. This function is not supported on touch panels with TFT display.

For devices with a membrane keyboard, the contrast can be adjusted in Runtime as follows:

+ Cursor left: Reduce contrast

+ Cursor right: Increase contrast



10.1 Example: Switching between the Event Message Buffer Display and the Event Message Page Display

Example Configuration

You can configure the display switch between the event message buffer and the event message page by using the following script:

Procedure 1 Create a tag without PLC connection of type BOOL. In the example

configuration, the tag is named "Switch_PageBuffer". 2 Create a script with the following contents:

If Switch_PageBuffer = 0 Then Call PtFct.Display_EMBuffer(OFF) Call PtFct.Display_EMPage(ON) Call PtFct.Set_Bit(PtVar.Switch_PageBuffer) Else Call PtFct.Display_EMPage(OFF) Call PtFct.Display_EMBuffer(ON) Call PtFct.Reset_Bit(PtVar.Switch_PageBuffer) End If

3 Configure the script for a key or a button.



Release 12/02 PLC Jobs


11 PLC Jobs

Converting PLC Jobs

Only part of the PLC jobs can be reused in Windows-based systems. Some PLC jobs are no longer required because of the different functionality of the operating devices or cannot be used at all. In these cases you may need to post-process the target project and the PLC program to achieve the source project functionality.

If post-processing the target project will be necessary anyway, you should check whether it is more efficient to handle tasks that have been done by PLC jobs in the source project by using functions in the target project.

PLC Jobs being used without Changes after the Conversion

Post-processing is no longer necessary after the conversion for the following PLC jobs:

14 "Set Time (BCD coded)"

15 "Set Date (BCD coded)"

23 "Set Password Level"

24 "Password Logout"

41 "Transfer Date/Time to PLC"

42 "Get LED-Area from PLC"

43 "Get Event Message Area from PLC"

44 "Get Alarm Message Area from PLC"

45 "Get Acknowledgement Area from PLC"

49 "Delete Event Message Buffer"

50 "Delete Alarm Message Buffer"

51 "Select Screen"

PLC Jobs Release 12/02


PLC Jobs requiring Post-editing

For the following PLC jobs, the basic realization of the functionality has either changed, or they can no longer be used in Windows-based systems. The following table provides information on some workarounds which may be inserted into the target project or into the PLC program during post-processing. Additional information (e.g. detailed instructions) can be found in other sections of this documentation and in the ProTool Online Help.

Graphical display Windows-based system Explanation/Substitution/ Workaround

2 "Hide Screen" PLC job is not required Windows-based systems can dim the brightness after a period of time that can be set by the user or activate a screen saver.

You can use the "Screensaver" option to make both settings in the Control Panel.

3 "Hardcopy" PLC job is not supported Instead, you can configure the function Print Screen for the "Change Value" event of a tag with PLC connection.

4 "Assign Port / Set Relay"

PLC job is not required There are no ports or relays in Windows-based systems.

12 "Message Log On/Off"

PLC job is not supported Instead, you can configure the function Message LogOn/Off for the "Change Value" event of a tag with PLC connection.

13 "Change Language"

PLC job is not supported Instead, you can configure the function Change Language for the "Change Value" event of a tag with PLC connection.




21 "Alarm Message View"

PLC job is not supported For Windows-based systems you can set the sort order for the alarm message window, the alarm message page, and the alarm message buffer by choosing "System" > "Messages " > "Settings" from the menu. You can set the sort order on the "Columns" tab for each message view. In Runtime you can sort the message view, by double-clicking on a column heading, according to the criterion displayed in this column (only for the "Date" and "Time" columns).

37 "Activate/Deactivate Overflow Warning for Event Messages" 38 "Activate/Deactivate Overflow Warning for Alarm Messages"

PLC job is not required There are no buffer overflow warnings in Windows-based systems. To replace the buffer overflow warning, configure the function Display System MessageText for the global event "Buffer Overflow". You can use this function to output your own message text. The message text is restricted to one language.

47 "Transfer LED Area directly to the Operating Device"

PLC job is not supported Instead you can use the PLC job 42 "Get LED-Area from PLC".

69 "Transfer Recipe Record from PLC to TP/OP "

69 "Read Data Record from PLC"

The "Recipe Number" and "Data Record Number" must be specified as parameters in Windows-based systems. If you want to transfer the recipe name or the record name from PLC to the operating device, instead of PLC job 69, you can use the function Data RecordPLC to Tags.




70 "Transfer Recipe Record from TP/OP to PLC"

70 "Write Data Record to PLC"

The "Recipe Number" and "Data Record Number" must be specified as parameters in Windows-based systems. If you want to transfer the recipe name or the record name from the operating device to PLC, instead of the PLC job 70, you can use the function DataRecord Tags to PLC.

72 "Cursor Positioning in active Screen"

PLC job is not supported Instead, you can use the PLC job 51 "Select Screen".



11.1 Replacing PLC Jobs by Functions

Replacing PLC Jobs by Functions

Some PLC jobs which cannot be reused in Windows-based systems can be replaced by functions.

If post-processing the target project will be necessary anyway, you should also check, whether it is more efficient to solve tasks which have been done in the source project by PLC jobs by using functions in the target project.

Configuration

If, from the PLC, you want to start the execution of a function configured on the operating device you can configure a tag with the "Read Continuously " option in ProTool. For the "Change Value" event, configure the corresponding function to this tag.

Execution

If the value of the tags changes in the PLC, the function is executed on the operating device as soon as the operating device detects the change.



Example: Starting the "Message Log_On_Off" Function from the PLC

You can use the following configuration to replace the PLC job 12 "Switching Message Log on/off" used in the source project by a function in the target project.

In ProTool

Procedure 1 Create an INTEGER tag with a PLC connection. 2 In the "Properties" dialog of the tag, activate the "Read Continuously" check

box on the "Optinons" tab. 3 Configure the function Message Log On Off for the "Change Value" event

to this tag. Specify the tag itself as the parameter. In the PLC

Procedure 1 In the PLC program, set this tag either to value 0 (Message Log: Off) or to

value 1 (Message Log: On). The message log is switched on or off according the value of the tag.

Release 12/02 Recipes


12 Recipes

Preliminary Remark

The way in which recipes and data records are treated in Windows-based systems basically differs from graphical displays. It may be best to realize recipes in your target project in a different way than in the source project. The "ProTool Online Help for Windows-based Systems" provides detailed information on "Recipes" and instructions for configuring a recipe view and a recipe screen.

Converting Recipes

During the conversion, recipes are transferred from the source project and adapted to the demands and capabilities of Windows-based systems as far as possible.

The following customizations are made during the conversion:

• Transferring and Synchronization In Windows-based systems, recipes are transferred directly, i. e. via tags with a PLC connection. Synchronization can only be made to a PLC. When converting transfer and synchronization, the following settings are transferred without changes: "Direct Transfer" "No Synchronization" "Synchronization to PLC_n" The following settings are customized automatically:

Graphical Display Windows-based System Indirect Transfer Direct Transfer Synchronization to "All PLCs" No Synchronization • Name, Version, Number

The settings are transferred completely. Settings unspecified in the source project are set to defaults in the target project.

• Identification The identification is not available in Windows-based systems. The recipes are identified in the PLC via their recipe number and recipe name.

Recipes Release 12/02


Post-processing: Entering New Data Records

The way data records are kept in Windows-based systems basically differs from graphical displays. Therefore the data records cannot be transferred from the source to the target device but must be re-entered.

Post-processing: Replacing the Standard Screen

During conversion, the standard screens "Z_RECORD 1" and "Z_RECORD 2" containing the basic functions for using data records are deleted.

In the target project, you can replace these standard screens by screens containing the screen object "Recipe View". The "ProTool Online Help for Windows-based Systems" provides detailed information on how to configure a recipe view or a recipe screen.

Post-processing: Data Record Transfer

In Windows-based systems, data record transfer is significantly simplified compared to graphical displays. Since the basic functionality has changed, you must post-process the target project and the PLC program. Post-processing depends on how the data record transfer had been realized in the source project:

Realization via the PLC jobs 69 "Read Data Record from PLC" and 70 "Write Data Record to PLC" In this case, you only have to set new values for the parameters "Recipe Number" and "Data Record Number" in the ProTool project. The parameters "Identification1" through to "Identification3" are not available in Windows-based systems. To coordinate the recipe transfer in the PLC program you have to evaluate the "Status Word" (4th word) instead of the "Status Area" in the "Data Mailbox" area pointer.

Realization via Functions If the data record transfer has been realized in the source project via functions you have to reconfigure it. There are two possibilities:

• Using the Screen Object "Recipe View" for the Data Record Transfer Configure a screen with the screen object "Recipe View". On the "Display" tab, activate the check boxes for the "from PLC" and "to PLC" buttons. The operator can now transfer the data records at runtime using those two buttons in the recipe view.

• Data Record Transfer via Functions Configure the following functions for one button each: When transferring using a disk Data Record DAT to PLC and Data Record PLC to DAT When transferring using recipe tags Data Record PLC to Tags and DataRecord Tags to PLC. The operator can now transfer the data records at runtime using these buttons.

Release 12/02 Recipes


Post-processing: Checking the Status of the Data Record Transfer

To check the data record transfer status, you have the following possibilities:

• If you have used functions to transfer data records: Evaluate their return value.

• For all other realizations: Evaluate the "Status Word" (4th word) in the "Data Mailbox" area pointer. In addition to changing the ProTool project, it may also be necessary to customizate the PLC program. The status word can have the following values: 0 = Transfer Allowed, Data Mailbox Free 2 = Transfer in Progress 4 = Transfer succeeded without Errors 12 = Transfer terminated with Error

Post-processing: Continuing to use indirect Data Record Transfer

If you have indirectly transferred data records to the PLC in your source project and if you want to continue to use this method, proceed as follows:

Procedure 1 Select "Recipes" in the project window. Select "Properties" in the context

menu of the converted recipe (right mouse button). The "Properties" dialog for the recipe opens.

2 Activate the option "Synchronize with" on the "Transfer" tab and enter the PLC to which your project is linked.

3 Close the dialog with OK. 4 Open a screen and insert an input field for the Data Record Name or Number

or

insert the "Recipe View" screen object. The "Properties" dialog of the input field or the recipe view opens.

5 On the "General" tab, configure the tag for data record name/number such that the address directly refers to the corresponding location in the "old" data mailbox (of the source project).

6 Close the dialog with OK.

Recipes Release 12/02


Release 12/02 Index

ProTool Service Pack 2 Configuration Support for Migrators I-1

Index

A Area pointer 2-1

B Bars 6-10 Buffer Overflow 2-5

C Character Graphics 6-8 Control Panel 2-4 Converting 1-2, 1-4

D Date 6-5

E Event 9-1 Event Message Buffer 10-11 Event Message Buffer and Page Display

10-11 Event Message Page 10-11

F Function Keys 2-8, 8-1 Functions 10-1, 11-5

G Global Settings 2-1, 2-4 Graphics 6-8

I Input/Output Field 6-3 Interface Area 2-1, 2-6

M Messages 5-1

P PLC Driver 3-4 PLC Drivers 3-1, 3-3, 3-5, 3-6 PLC Job 11-5 PLC Jobs 11-1 Printing 2-4 ProAgent Standard Screens 7-5 Projects

converting projects 1-2, 1-4 ProTool Standard Screens 7-2

R Recipes 12-1

S SIMATIC S5 - DP 3-3 SIMATIC S5-AS511 3-5 SIMATIC S5-L2-DP 3-3 SIMATIC S7-200 3-6 SIMATIC-S5 - FAP 3-4 Standard Screens 7-1, 7-2, 7-5 System Keypad 2-8

T Tags 4-1 Target System 2-1

Area Pointer 2-1, 2-6, 2-8 Fonts 2-1 Messages>Settings 2-1, 2-5 Printer 2-1, 2-4 Screen/Keys 2-1, 2-4 Settings 2-1, 2-4

Text Field 6-2 Text or Graphics List 6-3 Time 6-5 Trend Graphics 6-10

Index Release 12/02

I-2 ProTool Service Pack 2 Configuration Support for Migrators

Documents

SIMATIC HMI Configuration Support for Migrators Migration to Windows-Based Systems