6ES7671-0RC05-0YA0 - SIEMENS

SIMATIC

Windows Automation Center RTX

WinAC RTX 2005 incl. SP2

Manual

This documentation is part of the WinAC RTX 20 05 incl. SP2

package with order num ber:

6ES7 671-0RC05-0YA0 or 6ES7 671-0RC05-0YE0

Edition: 10/2007

Preface, Contents

Product Overview 1

Installation 2

Getting Started 3

Controller

Operations 4

STEP 7 Operations

and Components 5

Tuning the

Performance of the

Controller 6

Connecting the

Controller to the

SIMATIC NET OPC

Server 7

Reference

Information 8

Glossary, Index

This manual contains notices that you must observe to ensure your own personal safety, as well as to prevent damage to property.

The notices referring to your personal safety are highlighted in the manual by a safety alert symbol; notices referring only to property

damage have no safety alert symbol. The notices shown below are graded according to the degree of danger.

Danger

Indicates that death or severe personal injury will result if proper precautions are not taken.

Warning

Indicates that death or severe personal injury may result if proper precautions are not taken.

Caution

With a safety alert symbol indicates that minor personal injury can result if proper precautions are not taken.

Caution

Without a safety alert symbol indicates that property damage can result if proper precautions are not taken.

Notice

Indicates that an unintended result or situation can occur if the corresponding notice is not taken into

account.

Qualified Personnel

The device/system may only be set up and operated in conjunction with this documentation. Commissioning and operation of a

device/system may only be performed by qualified personnel. Within the context of the safety notices in this documentation qualified

persons are defined as persons who are authorized to commission, ground and label devices, systems and circuits in accordance with

established safety practices and standards.

Correct Usage

Note the following:

Caution

This device and its components may only be used for the applications describe d in the catalog

or the technical descriptions and on ly in connection with devices or components from other

manufacturers that have been approved or re commended by Siemens.

Correct, reliable operation of the pro duct requires proper transport, storage, positioning and

assembly as well as careful operation and maintenance.

Trademarks

Siemens® and SIMATIC® are registered trademarks of SIEMENS AG.

STEP 7™ and S7™are trademarks of SIEMENS AG.

Microsoft ®, Windows ®, Windows XP Professional ®, Windows 2000 ®, and Internet Explorer ® are registered trademarks of

Microsoft Corporation.

Adobe ® and Acrobat ® are registered trademarks of Adobe Systems Incorporated.

RTX™ is a trademark of Ardence, Inc.

CompactFlash™ is a trademark of COMPACTFLASH ASSOCIATION (CFA). Siemens is an authorized licensee of the

CompactFlash™ trademark.

The distribution and duplication of this document or the utilization

and transmission of its contents are not permitted without

express written permission. Offenders will be liable for damages.

All rights, including rights created by patent grant or registration

of a utility model or design, are reserved.

Siemens AG

Automation and Drives

Postfach 4848, D-90327 Nuernberg

Disclaimer of Liability

We have reviewed the contents of this publication to ensure

consistency with the hardware and software described. Since

variance cannot be precluded entirely, we cannot guarantee full

consistency. However, the information in this publication is

reviewed regularly and any necessary corrections are included in

subsequent editions.

Technical data subject to change.

이 기기는 업무용(A급) 전자파 적합기기로서 판매자 또는 사용자는 이 점을 주의하시기 바라며 가정 외의 지역에서 사용하는 것을 목적으로 합니다.

Windows Automation Center RTX 2005 incl. SP2 iii

A5E00992447-01

Preface

Purpose of the Documentation

This documentation provides detail ed information about the Windows Automation Center with Real-Time

Extensions (WinAC RTX 2005) software package that includes the following components:

• Windows Logic Controller RTX (WinLC RTX V4.3)

• Ardence RTX V6.5.1

• WinAC Time Synchronization V4.0 incl. SP1

• Automation License Manager V3.0 + SP1

• SIMATIC Softnet-S7 Lean Edition 2006 for Industrial Ethernet, including SIMATIC NET OPC

Server V6.4 (on SIMATIC NET CD)

You install WinAC RTX and the documentation from the installation CDs included with your release.

The Windows Logic Controller with Real-Time Extensions (WinLC RTX) provides the functio nality of a

programmable logic controller (PLC) in a real-time, PC-based environment. WinL C RTX uses the Ardence

Real-Time Extensions (RT X ) to Windows and is fully code-compatible with the SIMATIC product family.

WinLC RTX is part of the WinAC family of PC-based controllers. You can use many of the SIMATIC

products, such as Wi nCC flexible, with the WinAC P C-based controllers.

The PC-based controllers use a PROFI B US-DP network to communicate with distributed I/O, such as an

ET 200M device. They use PG/OP communication s (PROFIBUS or Industrial Ethernet) for connecting to

STEP 7 or other programming software on another computer.

Prerequisites

This documentation is intended for e ngineers, programmers, and maintenance personnel who have a

general knowledge of programmable logic controllers. Persons using this documentation also need

knowledge of Windows 20 00/XP operating systems and STEP 7 programming.

Scope

This document describes the features and the operation of WinAC RTX 2005.

Changes Compared to the Previous Version

The topic "What's New?" in the Product Overview enumerates the new features of WinAC RTX 2005 SP2.

Location of Documentation

The WinAC RTX installation includes this docume ntation as both online help and a PDF online manual and

also a PDF online manual for WinA C Time Synchronization. Installation of documentation is optional fro m

the setup. If installed, the online help is accessi ble from the controller panel and all applicable PDF files a re

accessible from the Start > Simatic > Documentation menu command.

Preface

iv Windows Automation Center RTX 2005 incl. SP2

A5E00992447-01

Other Manuals

You can find additional information in the online help for STEP 7 and in the following documents:

• STEP 7 - Programming with STEP 7. This manual provides basic information on designing and

programming a WinLC RTX STEP 7 user program.

• STEP 7 - System and Standard Functions for S7-300 and S7-400. WinLC RTX include s integrated

system functions and organization blocks, which you can use when programming. This manual

provides you with descriptions of the system functions, organization blocks, and loadable standard

functions.

• STEP 7 - Working with STEP 7. This manual explains the usage and the functions of the STEP 7

automation software. This manual provides you with an overview of the procedures used to

configure WinLC RTX and to develop ST EP 7 user programs.

• SIMATIC NET - Commissioning PC Stations. This manual support s you wh en commissioning your

SIMATIC NET PC modules in a PC Station, introduces all SIMATIC NET software tools, and helps

you use them successfully (available if you install SIM ATIC NET)

• SIMATIC NET - Industrial Comm unication with PG/PC, Parts 1 and 2. This manual helps you with

setting up industrial communication s over PRO FIBUS and Industrial Ethernet communications

networks (available if you install SIMATIC NET)

• WinAC Time Synchronizati on. This manual describes the configuration and operation of WinAC

Time Synchronization.

• Ardence RTX Runtime Release Notes. These release notes include the system requirem ents for

RTX and further information about RTX

To find the SIMATIC manuals, select the Start > Simatic > Documentation menu comm and from the Start

menu of the computer where the SIMATIC software is installed. The Ardence RTX Runtime Release Notes

are installed by default at C:\Program Files\Ardence\RTX\RTXRuntimeReleaseNotes.pdf.

Further Support

If you have any technical questions, please get in touch with your Siemens repr esentative or agent.

You can find your contact person at:

http://www.siemens.com/automation/partner

You can find a guide to the technical documentation offered for the individual SIMATIC Produ cts and

Systems here at:

http://www.siemens.com/simatic-tech-doku-portal

The online catalog and order system is found under:

http://mall.automation.siemens.com/

For additional assistan ce in answering technical q uestions, for training on this product, or for o rdering,

contact your Siemens distributor or sales office.

North America and South

America Europe and Africa Asia and Pacific region

Telephone: +1 (800) 333-7421 Telephone: +49 (0) 180 5050 222 Telephone: +86 10 64 75 75 75

Fax: +1 (423) 262-2200 Fax: +49 (0) 180 5050 223 Fax: +86 10 64 74 74 74

simatic.hotline@siemens.com adsupport@siemens.com adsupport.asia@siemens.com

For information about Ardenc e Real-Time Extensions (RTX):Internet: http://www.Ardenc e.com

Windows Automation Center RTX 2005 incl. SP2 v

A5E00992447-01

Contents

Product Overview................................................................................................9

Introduction to PC-Based Control..................................................................................9

Introduction to the Controller Panel.............................................................................10

PC-based Control Features.........................................................................................11

Advantages of Real-time Extensions (RTX)...........................................................................11

SIMATIC Functionality Supported by WinLC RTX .................................................................11

Windows Functionality Supported by WinLC RTX .................................................................12

What's New?................................................................................................................13

System Requirements .................................................................................................16

Windows User Privileges.............................................................................................18

Using Help...................................................................................................................19

Accessing Help from the Controller Panel..............................................................................19

Using the Table of Contents ...................................................................................................20

Using the Index.......................................................................................................................20

Using Full-Text Search ...........................................................................................................20

Printing Help Topics................................................................................................................20

Changing the Language of a Help Topic................................................................................20

Differences between WinLC RTX and WinLC Basis ...................................................21

Installation .........................................................................................................23

Overview of the Installation Tasks...............................................................................23

Installing the Ardence RTX Extensions .......................................................................24

Step 1: Install the Ardence RTX Extensions...........................................................................24

Step 2: Verify that the Ardence RTX Extensions Are Operational .........................................25

Step 3: Installing the WinAC RTX Software............................................................................25

Installing the WinAC RTX Software.............................................................................26

Licensing the WinAC RTX Software............................................................................27

Installing the License during Installation.................................................................................27

Installing the License at a Later Date .....................................................................................27

Transferring an Installed License............................................................................................27

Running the WinLC RTX Controller without a License...........................................................27

Recovering the License in Case of a Defective Hard Drive....................................................27

Uninstalling Ardence RTX or WinAC RTX...................................................................28

Evaluating your RTX Installation for your Application..................................................28

Evaluating your Platform for RTX Suitability...........................................................................28

Evaluating Performance of DP Interfaces with RTX...............................................................28

Getting Started ..................................................................................................29

Understanding the Concepts.......................................................................................29

What Is a PC Station?.............................................................................................................29

What Is a Communication Interface?......................................................................................32

What Is an Index?...................................................................................................................34

What Is a Submodule?............................................................................................................35

What Is an IF Slot? .................................................................................................................36

Contents

vi Windows Automation Center RTX 2005 incl. SP2

A5E00992447-01

Configuring Communication Interfaces........................................................................37

Designating a Communication Interface as a Submodule......................................................37

Testing a CP 5613 Configuration............................................................................................39

Viewing the Submodule Diagnostics of a DP Submodule......................................................40

Removing a Submodule..........................................................................................................41

Configuring the Controller in STEP 7........................................................................... 42

Connecting STEP 7 to the Controller......................................................................................42

Hardware Configuration in STEP 7.........................................................................................44

Correcting Invalid Characters in Earlier STEP 7 Versions .....................................................47

Verifying the Configuration ..........................................................................................48

Example PC Station Configuration.........................................................................................48

Station Configuration Editor and WinLC Properties ...............................................................48

STEP 7 PG/PC Interface ........................................................................................................49

STEP 7 Hardware Configuration ............................................................................................49

Controller Operations.......................................................................................51

Starting and Shutting Down the Controller ..................................................................51

Starting WinLC RTX................................................................................................................51

Shutting Down WinLC RTX ....................................................................................................51

Changing the Operating Mode of the Controller..........................................................52

Operating Mode (RUN/STOP) and Status Indicators.............................................................52

Allowed and Prohibited Actions for each Operating Mode.....................................................53

Resetting the Memory Areas: MRES Command (CPU Menu)....................................54

Using the Status Indicators..........................................................................................55

Flashing Indicators..................................................................................................................56

Corrective Action If the STOP Indicator is Flashing Slowly....................................................56

Corrective Action If All Status Indicators Are Flashing...........................................................56

Using the Tuning Panel ...............................................................................................57

Using the Diagnostic Buffer.........................................................................................59

Sorting Events (upper panel)..................................................................................................60

Choosing Format (lower panel) ..............................................................................................60

Selecting the Time Type.........................................................................................................60

Updating the Diagnostic Buffer...............................................................................................60

Saving the Diagnostic Buffer ..................................................................................................60

Displaying Help.......................................................................................................................60

Archiving and Restoring STEP 7 User Programs........................................................ 61

Creating an Archive File..........................................................................................................61

Restoring an Archive File........................................................................................................61

Closing the Controller Panel........................................................................................61

WinLC RTX Operation following a Windows Blue Screen...........................................62

Considerations for SFC 22, SFC 23 and SFC 82 to 85..........................................................63

WinLC RTX Restart Behavior after a Blue Screen.................................................................64

Configuring Automatic Reboot for Windows...........................................................................64

Storing Retentive Data.................................................................................................65

What Information about the Controller Does WinLC RTX Store?...........................................65

Available Options for WinAC Data Storage............................................................................67

Configuring WinAC Data Storage...........................................................................................69

Contents

Windows Automation Center RTX 2005 incl. SP2 vii

A5E00992447-01

Managing the Enhanced Write Filter ......................................................................................73

How WinLC RTX Loads Memory Areas on Startup................................................................75

Using SFCs to Retain Data.....................................................................................................77

Using an Uninterruptible P ower Supply (UPS).......................................................................78

Retentive Data Storage following Power Loss or Blue Screen...............................................79

Setting Controller Panel Options .................................................................................80

Customize Command (CPU Menu)........................................................................................80

Selecting the Language..........................................................................................................80

Selecting the Autostart Feature..............................................................................................80

Setting the Security Options...................................................................................................81

Security Command (CPU Menu)............................................................................................81

Changing the Password..........................................................................................................82

Startup Options for the Controller................................................................................82

Starting the Controller at PC Boot ..........................................................................................82

Setting the Restart Method.....................................................................................................83

STEP 7 Operations and Components..............................................................85

Using STEP 7 with the Controller................................................................................85

Configuring the Operational Parameters for the Controller .........................................85

Accessing Operational Parameters........................................................................................85

Logic Blocks Supported by WinLC RTX...................................................................... 86

Additional S7 Blocks...............................................................................................................86

S7 Communication Functions......................................................................................87

PROFIBUS DPV1........................................................................................................88

Organization Blocks (OBs) ..........................................................................................89

OBs for the Free Scan Cycle, Cold Restart, and Warm Restart.............................................90

Interrupt OBs...........................................................................................................................91

Considerations for Cyclic Interrupt OBs..................................................................................92

Error OBs................................................................................................................................92

System Functions (SFCs)............................................................................................94

Running Asynchronous SFCs Concurrently...........................................................................97

SFCs That Can Cause the Scan Cycle to Vary......................................................................98

Notes for SFC 82, SFC 83, and SFC 84.................................................................................98

System Function Blocks (SFBs).................................................................................. 99

Tuning the Performance of the Controller ....................................................101

Scan Cycle for a PC-Based Controller ......................................................................101

Tasks Performed during the Scan Cycle..............................................................................101

Methods for Managing the Performance of WinLC RTX......................................................103

What Causes Jitter? ..................................................................................................104

Priority Settings for Competing RTX Applications Can Cause Jitter ....................................104

Priorities among the WinLC RTX Threads Can Cause Jitter................................................106

The Sleep Interval Forced by the Execution Monitor Can Cause Jitter................................107

Adjusting the Priority of the Controller.......................................................................108

Real-Time Subsystem Priorities ...........................................................................................108

Managing the Sleep Time..........................................................................................109

Sleep Management Techniques...........................................................................................109

Contents

viii Windows Automation Center RTX 2005 incl. SP2

A5E00992447-01

Adjusting the Minimum Sleep Time and Cycle Time............................................................114

Using SFC 47 to Add Sleep Time in the STEP 7 User Program..........................................117

Adjusting the Sleep-Monitoring Algorithm of the Execution Monitor ....................................118

Example: Avoiding Jitter in the Start Time of an OB ............................................................124

Isochronous Mode for a Constant Bus Cycle ............................................................128

System Requirements for an Isochronous DP Cycle ...........................................................128

Connecting the Controller to the SIMATIC NET OPC Server.......................129

Task Overview...........................................................................................................129

Step 1: Add the OPC Server to the PC Station .........................................................130

Step 2: Add the OPC Server to the Hardware Configuration.....................................131

Creating the STEP 7 Project.................................................................................................131

Adding the OPC Server to the Hardware Configuration.......................................................132

Configuring the OPC Server.................................................................................................133

Step 3: Add an S7 Connection for the OPC Server in NetPro................................... 134

Configuring an OPC Server Connection in NetPro...............................................................134

Assigning a Local ID for the OPC Server Connection..........................................................136

Step 4: Download the Configuration to the Controller ...............................................137

Step 5: Connect the Controller to the OPC server..................................................... 138

Creating an OPC Project ......................................................................................................138

Adding a Connection (Group) for the OPC Server...............................................................138

Configuring the Items to be Accessed (Using Absolute Addressing)...................................140

Configuring the Items to be Accessed (Using the STEP 7 Symbol Table)...........................143

Reference Information....................................................................................145

Technical Data...........................................................................................................145

Order Number.......................................................................................................................145

Technical Specifications .......................................................................................................145

Execution Times........................................................................................................148

Troubleshooting......................................................................................................... 149

Relevant Information for Ardence RTX.................................................................................149

Troubleshooting Network Problems......................................................................................151

Improving the Performance of a DP Interface ......................................................................152

Responding to Diagnostic Events.........................................................................................153

Cross-Module Access Errors................................................................................................153

System Status List (SSL)...........................................................................................154

Using SFC 51 to Read the SSL............................................................................................154

SSL_ID Descriptions.............................................................................................................155

Glossary...........................................................................................................163

Index.................................................................................................................167

Windows Automation Center RTX incl. SP2 9

A5E00992447-01

Product Overview

Introduction to PC-Based Control

The WinAC (Windows Automation Center) PC-b ased controllers execute within a standard PC and provide

the same functionality as SIMATIC S7 CPUs (hardware controllers). They inclu de WinLC RTX, and the

WinAC Slot PLC. WinLC RTX is a programmable software PLC — a software applicatio n that runs on a

standard computer (PC).

WinLC RTX supports multiple networks and connects to the distributed I/O, such as ET 200M, by means of

DP interfaces that reside in your computer.

As part of the SIMATIC family of automation products, WinLC RTX can also communicate wi th STEP 7 or

other SIMATIC products, such as WinCC Flexible, ProTool Pro, or other SIMATIC S7 controllers, including

any of the PC-based controllers ove r PROFIBUS or Industrial Ethernet networks.

You can use the same prog ramming languages, program structure and prog ramming user interface

(STEP 7) as for hardware PLCs to develop your process control solution. Programs designed for S7

controllers can run on P C-based controllers and vice versa. The PC-based controllers also include a

controller panel that runs on the PC. With these capabilities, you can use WinLC RTX in a typical factory

automation configuration.

Product Overview

10 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Introduction to the Controller Panel

The controller panel correspond s to the faceplate of the SIMATIC S7 CPUs. It enables you to start or shut

down the controller and to perform othe r operations.

The controller panel is a display window on your

PC that contains the following elements for

working with the controller:

• Two operating mode selector switch

positions for changing the operating

mode of the controller

(similar to the mode selector switch on an

S7 CPU front panel.)

• Status indicators for the controller

• An MRES switch position for resetting the

memory areas

• Menus for controller operations

An icon is displayed in the Windows taskbar whe never the controller is operating. When the controller is

operating and the controller panel is closed, you can double-click this icon to open the controller panel.

Opening or closin g the controller panel does n ot influence the state of the controller. The statu s of the

operator switches and the LEDs are stored in the controller.

Product Overview

Windows Automation Center RTX incl. SP2 11

A5E00992447-01

PC-based Control Features

WinLC RTX is a software version of an S7 controller that adds real-time control provided by a real-time

subsystem for the Windows operating system. It executes STEP 7 user progra ms as do other

S7 controllers and allows for easy integration with STEP 7 and stan dard Windows applications.

WinLC RTX executes in two separate environments, including processes that run in the real-time

subsystem and processes that run in the Wind ows environment.

• The processes that run in the real-time subsystem execute the STEP 7 user program for

WinLC RTX, giving process control the highest priority.

• The processes that run in the Windo ws environment handle other operations, such as

communication and inte rfaces to Windows systems and applications.

Advantages of Real-time Extensions (RTX)

WinLC RTX uses real-time extensio ns (RTX) to provide the following features:

• Deterministic operation ensures that response is predictable. Execution of the STEP 7 user

program occurs enti rely in the real-time subsystem, thus reducing "jitter."

• The control process is protected from hard disk crash and Windows system failure. WinLC RTX is

notified of all Windows shutdowns (including the "blue screen") in order to shut down in an orderly

fashion. You can configure Windo ws to reboot automat ically after a system failure. This option is

accessed by the Startup and Recovery b utton under the Advanced tab of System Properties in the

Windows Control Panel.

SIMATIC Functionality Supported by WinLC RTX

WinLC RTX provides the following features:

• Implements a substantial subset of the S7 logic blocks of SIMATIC co ntrollers: Organization Block

(OB), System Function Block (SFB), and System Function (SFC)

• Uses PROFIBUS-DP as its I/O subsystem, supporting DPV0 and DPV1 slaves (PROFIBUS DPV1

provides enhanced alarm and statu s re porting, in order to communicate with intelligent slave

devices)

• Supports up to 4 separate PROFIBUS-DP subnets for co nnecting to distributed I/O

• Supports an isochronous mode, which allows WinLC RTX to operate in constant bus cycle mode to

help eliminate jitter

Note: WinLC RTX allows you to use isochronous mode on more than one PROFIBUS-DP subnet;

however, your computer must not share the interrupt (IRQ) of the PCI slots used by the DP

interfaces with any device operating in the Windows operating system (for example, a video card).

For example, the SIMATIC Box PC 627 provides two PCI slots that can be used for isochronous

mode on two different PROFIBUS-DP subnets.

• Uses S7 communication services, offering compatibility with SIMATIC applications such as

STEP 7, WinCC, and ProTool/Pro for tasks such as programming, debugging, monitoring or

visualization

• Allows peer-to-pe er communications between controllers (hardwar e or software) on the network

• Supports the routing of S7 communications through the submodul e CP cards of WinLC RTX,

allowing STEP 7 on one subnet to connect to an S7 station (such as an S7-400 controller) on a

different subnet

• Provides ability to archive and restore control prog rams

• Allows you to control the operating mode of the controller and to view status information fro m the

controller panel

Product Overview

12 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

• Provides a tuning panel for optimizing system performance

• Provides time synchronization as either a time master or slave

• Provides connectivity to the SIMATIC NET OPC Server, which enables OPC client applications to

access process d ata (requires installation of SIMATIC NET, a separate product)

• Ability to exchange data with custom PC applications developed with WinAC ODK: WinA C Open

Development Kit is a software packag e (sold separately) that supports two progra mming interfaces

to the STEP 7 user program: CCX (Custom Code Extension) and SMX (Share d Memory

Exchange.)

• Ability to develop software such as a control panel to perform controller operations and display

controller status information using the Controller Management Interface (CMI) of WinAC ODK.

(sold separately)

• Ability to use WinAC RTX with up to three CPU 41x-2 PCI (WinAC Slot PLCs) that are instal led in

your computer.

Windows Functionality Supported by WinLC RTX

Windows Administrator priv ileges (ADMIN) are not required in order to operate the WinLC RTX controll er.

With Power User, User or even with Gue st privilege s, you can perform operational tasks, such as changing

the operating mode of the controller from RUN to STOP, modifying the sleep time, or restoring an archived

control program.

If you configured WinLC RTX to start at PC boot (and if the controller wa s consequently started by

rebooting the computer), one user can log off and another user can log on without affecting the operation of

the controller.

Note: Although WinLC RTX supports logging off and logging on as a Windows user, the

Windows XP "Switch User" function is not supported by WinLC RTX.

Product Overview

Windows Automation Center RTX incl. SP2 13

A5E00992447-01

What's New?

The following features are new for WinAC RTX 2005 SP2:

Support of the SIMATIC WinAC NV128 Card for WinAC Data Storage

WinAC RTX 2005 SP2 support s the SIMATIC WinAC NV128 card for selected SIMATIC PCs. The

plug-in NVRAM card provides 128 Kbytes for WinAC data storage that can be retained following a

shut down, power failure, or even an abnormal Windows termination (blue screen). The o rde r

number for the plug-in SIMATIC WINAC NV128 card is 6ES7671-0AG00-1YA7.

Support of Integrated NVRAM for WinAC Data Storage

WinAC RTX 2005 SP2 support s the 128 Kbyte of integrated NVRAM on selected SIMATIC PCs.

The integrated NVRAM provides 128 KBytes for Win AC data storage that can be retained following

a shut down, power failure, or even an abnormal Windows termination (blue screen).

Support of Isochronous Mode with the CP 5611

WinAC RTX 2005 SP2 extends support of isochronous mode to the CP 5611. Prior to this rel ease,

only the CP 5613 cards supported isoch ronous mode.

Detection of Submodule Loss

WinAC RTX 2005 SP2 does not automatically delete the STEP 7 user program and configuration

when a submodule fail s, or when a submodule is removed. See the section "WinLC RTX Respo nse

to Submodule Changes" for a detailed description of the functionality.

Support of Additional SIMATIC PCs with Windo ws XP embedded

WinAC RTX 2005 SP2 support s additional SIMATIC PCs with Windows XP embedded:

• Microbox PC 427B

• Panel PC 477B

• Box PC 627B

• Panel PC 677B

WinAC RTX 2005 SP2 continues to su pport SIMATI C PCs with Windows XP or Windows 2000.

Detection of "NAU" signal on SIMATIC PCs that can signal power failure

The following SIMATIC PCs detect a power failure and send an "NAU" signal:

• Microbox PC 420

• Panel PC 477

• Microbox PC 427B

• Panel PC 477B

• Box PC 627 24V

• Panel PC 677 24V

• Box PC 627B 24V

• Panel PC 677B 24V

WinAC RTX 2005 SP2 initiates a fast shutdo wn of the controller panel when it receives an "NAU"

signal. If you have configured WinAC Data Storage to be in NVRAM , WinAC RTX can save the

retentive data to NVRAM, go to STOP mode, and shut down the controller before the power is lost.

Product Overview

14 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Use of LEDs on SIMATIC Microbox PC 427B and Panel PC 477B

WinAC RTX 2005 SP2 can activate the SF LED and the RUN/STOP LED on the Microbox PC 427B

and Panel PC 477B:

LED Color Description

SF Red A fault condition has occurred in the controller.

SF Unlit Normal controller operation

RUN/STOP Yellow Controller is in STOP mode

RUN/STOP Green Controller is in RUN mode

The selection for LED usag e is on the WinAC Data Storage dialog.

The following feature was new for WinAC RTX 2005 SP1:

Support of Internal SRAM for WinAC Data Storag e

WinAC RTX 2005 SP1 provides an a dditional alternative to storing retentive data in a file system.

For the SIMATIC Microbox PC 420 and the SIMATIC Panel PC 477, you can use the internal SRAM

of the PC for the retentive data storage. The SRAM provides d ata storage that can be retained

following a shutdown, power failure or even an abnormal Windows termination (blue screen). The

WinAC RTX 2005 SP1 release incl udes a WinAC Data Storage tool that allows you to configure

where WinLC RTX stores retentive data

The following features were new for WinAC RTX 2005:

Improved STEP 7 User Program Performance

STEP 7 user programs running on WinLC RTX have execution times up to twelve times as fast as

the same program running on WinLC RTX V4.0. The STEP 7 user program, however, requires up to

14 times more memory than it used in previous releases.

CP 5611 Card Support

WinAC RTX 2005 supports a CP 5611 card for communication to STEP 7 or to DP I/O. The

CP 5611 card has reduced functionality from a CP 5613 card (for example, fewer S7 connections,

fewer slaves and a limit of one as a submodule ), but offers lower costs tha n the CP 5613.

Ability to use built-in CP 5611 PROFIBUS interface of Siemens Box, Rack, and Panel PCs

For Siemens Box, Rack, and Panel PCs, WinAC RTX 2005 supports the use of the built-in CP 5611

PROFIBUS interface for communication to STEP 7 or DP I/O. This capability means that you do not

have to buy a separate communications ca rd.

Product Overview

Windows Automation Center RTX incl. SP2 15

A5E00992447-01

SIMATIC NET Installation no longer required fo r WinAC RTX

WinAC RTX 2005 no longer re quires you to install SIMATIC NET to be able to configure, program,

and use WinLC RTX. WinA C RTX does not install SIMATIC NET, however, the WinAC RTX release

includes the SIMATIC NET CD. Installation of the SIMATIC NET CD i s only re quired for needs such

as those listed below:

• Use of OPC Server

• Use of other SIMATIC NET products, for example, Softnet S7 for SIMATIC co mmunication

over Industrial Ethernet

Windows XP embedded Support

WinAC RTX pre-loaded o n a SIMATIC PC with the Windows XP embedded operating system

extends the use of WinAC RTX to diskless computer systems, as well as lower-co st, smalle r

systems. WinAC RTX supports the following SIMATIC PCs with Windows XP embedded:

• Microbox PC 420

• Panel PC 477

• Box PC 627

Contact your local sales re presentative for more information about WinAC RTX on XP embedded

systems, available as separate products from WinAC RTX.

Time Sync Feature

WinAC RTX 2005 include s a Time Syn chronization service as a component of the installation.

Like a hardware S7 controller, WinLC RTX has a sy stem clock based on the hardware clock of your

computer. WinLC RTX differs from a hardware S7 controlle r though because it has a real-time clock

that is independent of the system clock of the computer. The Win LC RTX real-time clock can

function as a time slave to the Time Synchronization service, or as a time slave to devices on

submodule DP-subnets. WinLC RTX can also serve as a time master to devices on the submodule

DP-subnets.

See your Time Synchronization service documentation for detailed information.

Increase in Flag Memory

WinAC RTX 2005 provides 16 Kbytes of flag memory, instead of 2 Kbytes as in WinAC RTX V4.1.

Additional Program Blocks

WinAC RTX 2005 adds the following blocks to the set that WinLC RTX sup ports:

• OB 88

• all OB 3x blocks

• SFB 31, SFB 33 - SFB 36

• SFC 9, SFC 10

To use these features, your PC must meet the system requireme nts.

Product Overview

16 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

System Requirements

To use WinLC RTX, your personal computer (PC) must meet the following criteria:

Category Requirement

Operating

System One of the following operating systems:

• Microsoft Windows 2000 Professional Service Pack 3 or Service Pack 4

• Microsoft Windows XP Professional Service Pack 1 or Service Pack 2

Ardence RTX version 6.5.1 (included with WinAC RTX)

Note: Some PC configurations that are not SIMATIC industrial PCs do

not support installation or operation of Ardence RTX. Refer to your RTX

Runtime Release Notes on your installation CD for hardware an d

software system requirements for RTX.

Processor and

memory Pentium multiproce ssor system:

• 400 MHz

• 256 Mbytes or more of RAM

• BIOS must support plug-and-play (ACPI, Advanced Configuration and

Power Interface)

Note: Dual-core and hyperthreading systems are also supported.

Hard drive A hard drive with 125 Mbytes of free space for th e complete installation; setup

options offer choice to not install some components such as documentation

thereby reducing disk space requirem ents

The setup program uses at least 1 Mbyte additional free space on drive C for the

WinLC Setup program (Setup files are deleted when the installation is com plete)

Operator

interface A color monitor, keyboard, and mouse or other pointing device (optional) that are

supported by Windows

Communication

interface One or more of the following communication interfaces for communications with

STEP 7 or other S7 applications or for communications with distributed I/O:

• CP 5611 hardware revision 5 or later

• CP 5613 V3 or CP 5613 V6 or later

• SIEMENS PC with built-in CP 5611 PROFIBUS interface: ASPC2 STEP

E2 or ASPC2 STEP R ASIC

• Communication interfa ce such a s Indu strial Ethernet interface that

SIMATIC NET supports. Industrial Ethernet interfaces can be used for

S7 communication but cannot be used for DP I/O communi cation.

Note: WinLC RTX supports as submodules a maximum of one CP 5611 card or

built-in CP 5611 PROFIBUS interface. The maximum number of submodules

that WinLC RTX supports is four.

Product Overview

Windows Automation Center RTX incl. SP2 17

A5E00992447-01

Category Requirement

Siemens

software Programming and configuration software: STEP 7 V5.3 SP2 with the installed

hardware update for WinLC RTX.

Note: You can use STEP 7 V5.2 or STEP 7 V5.3 if you do not need

features dependent on later STEP 7 releases. Minimum STEP 7

requirements for these feature s are listed below:

• Data exchange with broadcast between DP slave devices

(STEP 7 V5.3)

• Enhanced support for positioning and motion applications

(STEP 7 V5.3)

• Non-retentive DBs (STEP 7 V5.3)

• Multi-PLC support (STEP 7 V5.3)

• SSL_ID 0x1C (STEP 7 V5.3 SP2 + WinLC RTX hardware update)

• Time Synchronization (STEP 7 V5.3 SP2 + WinLC RTX hardware

update)

• CP 5611 as a WinLC RTX subm odule (STEP 7 V5.3 SP2 +

WinLC RTX hardware update)

• Isochronous mode or WinAC Time Synchronization for CP 5611

(STEP 7 V5.3 SP3 + WinLC RTX hardware update )

SIMATIC NET

(optional) You must install SIMATIC NET from the CD that the WinAC RTX installation

package includes if you need the followi ng features:

• Use of OPC Server

• Use of other SIMATIC NET products, for example, Softnet S7 for

SIMATIC communication over Indu strial Ethernet

The SIMATIC Softnet-S7 Lean (6GK1 704-1LW63-3AA0) licen se is included with

your WinAC RTX installation pa ckage.

For more information about SIMATIC NET products for PC-based automation

refer to the SIEMENS Mall or the ST PC catalog.

Product Overview

18 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Windows User Privileges

You are not required to have Windows Administrator (ADMIN) privileges in order to perform WinAC RTX

operations, such as changing the operating mode of the controller, modifying the sleep time or the

minimum scan time of the controller, archiving or restoring cont rol programs, or setting the security option s .

With Power User, User or even with Guest privileges, you can perform any operation from the WinLC RTX

controller panel. This allows you to manage the network privileges for the PC station within your application

and to avoid conflicts during installatio n, commissioning and operation of a PC-b ased automation solution

that is part of a larger system.

As shown in the following table, som e operations are restricted to certain Windows User privilege classes.

Operation Administrator Power

User User Guest

Installing WinAC RTX software Allowed Not allowed Not allowed Not allowed

Configuring or modifying the PC

Station Allowed Allowed Not allowed Not allowed

Performing WinAC RTX operations Allowed Allowed Allowed Allowed

Product Overview

Windows Automation Center RTX incl. SP2 19

A5E00992447-01

Using Help

The online help system provides informa t ion about the controller panel and the controller. This topic

provides information about using online help:

• Accessing Help from the Controller Panel

• Using the Table of Conten t s

• Using the Index

• Using Full-Text Search

• Printing Help Topics

• Changing the Language of a Help Topic

Note: If you have Windows XP SP 2 or later, you must allow blocked content in order to view all of

the online help. The increased security features of Windows XP SP 2 block some features and

controls used in the implementation of the online help. To enable blocke d content when displaying

the online help, click the security menu bar from your web browser and select "Allow Blocked

Content", answering any prompts ge nerated by this selection.

Accessing Help from the Controller Panel

To access online help from the controller panel, use o ne of the following methods:

• Click an entry on the Help menu.

• Click the Help button in a dialog or message box to view information about that specific dialog or

message box.

• Press the F1 key to view context-sensitive help on th e currently selected item (for example, a

window, dialog, or menu).

The menu commands avai lable from the controller panel Hel p menu are listed below:

• Help on Controller

The Help > Help on Controller command displays the initial page of the online help for the

controller that is connected to the controller panel. It describes controlle r and controller panel

operations.

• Introduction

The Help > Introduction command displays a topic that provide s an introduction to PC-based

control and the capabilities of the controller.

• Getting Started

The Help > Getting Started command displays a topi c that helps you get started when you begin

using the controller panel to work with the controller for the first time.

Product Overview

20 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Using the Table of Contents

The table of contents is in the left pane of the web browser and provides navig ation within the online help

system:

• Click a book to open it and displ ay the books and topics that it contains.

• Click the book again to close it.

• Click any topic within the table of contents to display that topic.

The topic you are currently viewing is highlighted in the table of contents.

The table of contents can be either hidden or displayed:

• Click the "x" in the left navigation pane to close the table of contents.

• Select the Contents button on the browser or the "Sho w" link in a topic to display it. (The "Show"

link appears only when you have displayed a context-sensitive topic from the application.)

Using the Index

The index provides access to information about a specific subject. Use one of the following methods to

access the index:

• Select the Index button on the browser. (If the Index button is not visible, click the "Show" link at

the top of the topic. The "Show" link appears only wh en you have displayed a context-sensitive

topic from the application.)

• Click the Index button in any help topic.

Using Full-Text Search

To use the full-text search capabilities of the online help, use the se arch field that is displayed above the

topic, or select the Search button on the browser. (If the Search field and Search button are not visible,

click the "Show" link at the top of the topic. The "Show" link appears only when you have displayed a

context-sensitive topic from the applica tion.)

The full-text search supports the Boolean operato r s AND, O R, and NOT and parentheses in your search

expression. Wildcards ("*") are not supported.

Printing Help Topics

To print a single topic that is displayed in your browser, right-click in the topic pane and select Print from

the context menu. Select the print options of your choice.

Changing the Language of a Help Topic

The browser contains lang uage buttons for each of the supported languages. To see the current help topic

in another language, click the language button of your choice. The current topic is displayed in the

language you selected, but the contents, index, and search features of the online help system remain in the

original language. This ma y be helpful if a topic is unclear and you want to read it in another language.

If you select a language that you did not install, the online help system cannot display the topic in that

language and display s a "Page not found" error. Changing the language of an online help topic does not

change the display langua ge of the controller panel.

Product Overview

Windows Automation Center RTX incl. SP2 21

A5E00992447-01

Differences between WinLC RTX and WinLC Basis

Some of the operations of WinLC RTX differ from WinLC Basis:

• WinLC RTX provides a way to shut your process down in an orderl y manner in the case of a

Windows Blue Screen.

• WinLC RTX provides deterministic operation, ensuring predictable response time and reduced

"jitter".

• WinLC RTX provides superior timing re solution in microseconds; whereas WinLC Basis provides

timing resolution in millisec onds. For example, the times returned by SFC 78 and the sleep time in

SFC 47 have a higher resol ution in WinLC RTX.

• WinLC RTX supports an i s ochronous mode (constant bus cycle time).

WinLC RTX and WinLC Basis differ in how the blocks of the STEP 7 user program are stored in the

memory of your computer:

• WinLC RTX uses only the non-paged RAM memory. All blocks of the STEP 7 user progra m and all

of the process data must fit in the available non-paged memory that is also shared with other

applications (such as device drivers) that are running on the computer.

• WinLC Basis runs in virtual memory that may be swapped to disk by the Windows operating

system.

In addition, all new features introduced with WinLC RTX V4.2 and V4.3 are not available with WinLC Basis

V4.1.

Caution

Downloading a STEP 7 user program that is too large for the memory of the computer

can lock up the computer or cause the operation of WinLC to be come unstable,

possibly causing damage to equipment and/or inj ury to person nel.

Although STEP 7 and WinLC do not limit the number of blocks o r the si ze of the STEP

7 user program, your computer does have a limit, based on the available drive space

and RAM memory. The limit for the size of the STEP 7 user program and number of

blocks for your computer can only be determined by testing a configured system

against the requirements of your control application.

Windows Automation Center RTX incl. SP2 23

A5E00992447-01

Installation

Overview of the Installation Tasks

To install WinAC RTX, your computer must meet the system requirements and you must have Windows

administrator (ADMIN) privileges and complete the following tasks:

• Uninstall any of the following software packages if they exist on your computer in the order listed,

rebooting when finished:

o WinAC Basis or WinAC Basis Demo

o WinAC RTX

o Ardence or VenturCom RTX

o WinAC Slot release prior to WinAC Slot V3.4, or upgrade your existing to release to V3.4

or V4.0

Note: Uninstalling these software package s is required if you do not have WinAC RTX 2005 incl.

SP1 installed on your computer. If you already have WinAC RTX 2005 incl. SP1 installed on your

computer, then you do not need to uninstall any software prior to installing WinAC RTX.

• Install the Ardence RTX extensions.

• Verify that the Ardence RTX extensions are working .

• Install the WinAC RTX software.

For communication with di stributed I/O over a PROFIBUS-DP network, your computer must have one or

more DP interfaces.

To use the OPC Server or other SIMATIC NET featu r es, you must install SIMATIC NET from the CD

included with your WinAC RTX installation; otherwise, you do not need to install the SIMATIC NET CD.

Following installation, license the WinAC RTX installation using the Automation License Manager.

The succeeding topics con t ain the installation and licensing pro ce dures.

Installation

24 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Installing the Ardence RTX Extensions

To install the WinAC RTX software in cluding the Ardence RTX extensions, remove in order the software

named in "Overview of the Installation Tasks" and perform the following tasks as directed from the WinAC

RTX 2005 Setup screen:

• Install the Ardence RTX extensions.

• Verify that the Ardence RTX extensions are working .

Note: You must have Windows administrator (ADMIN) privilege s to install the Ardence RTX

extensions.

• Install the WinAC RTX software.

When you insert the installation CD, the Setup program starts automatically. If the Setup program does not

automatically start, browse the CD and double -click the Setup.exe file. After you select the language for the

Setup program, the Setup program di splays a dialog that guides you through the installation tasks:

Step 1: Install the Ardence RTX Extensions

Click the square under Step 1 to start the Install Wizard for installing the Ardence RTX extensions. The

Install Wizard requires you to enter an Ardence PAC number and email address. The PAC number is on

the back of the WinAC RTX CD case. The email address to enter is winac@siemens.com.

Note: If you have previously installed Ardence RTX Version 6.5.1, the installation software detects

its presence and the first square is inactive.

Installation

Windows Automation Center RTX incl. SP2 25

A5E00992447-01

Step 2: Verify that the Ardence RTX Extensions Are Operational

The Install Wizard restarts your computer after installing the RTX extensions. Click the square under Step 2

and follow the instructions to verify that the RTX extensions a re working. The Install Wizard display s the

following instructions:

1. Open the Windows Control Panel.

2. Double-click the RTX Properties icon to display the RTX Properties dialog.

3. Click the Control tab to view the status of the RTX extensions.

The RTX extensions, with their current state of Running, Stopped, or Disabled are listed in the

Status field. Two buttons at the bottom of the Control dialog allow you to Start RTX and Stop RTX.

4. Click the Start RTX button to start the RTX extensions. Wait a few seconds to see that the status of

the Stopped RTX extensions change to Running.

Caution

Clicking the Stop RTX button before the RTX extensions have completely switched to

Running can cause the computer to become unresponsive. If this happens, you must

restart your computer to recover.

Always wait a few seconds until the requested action is complete and the display shows

current status before clicking the Start RTX or Stop RTX buttons.

5. Wait a few seconds and then click the Stop RTX button. Verify that the Running RTX extensi ons in

the Status field change to Stopped. If the Start and Stop buttons work corre ctly, your

RTX extensions are installed and functi oning. However, this procedure verifies only a minimum

level of platform suitability for RTX.

6. If the RTX extensions are working correctly, close the RTX Properties dialog.

After you have installed and verified the Ardence RTX installation, you can evaluate your platform and DP

interfaces for use with RTX.

Step 3: Installing the WinAC RTX Software

When you complete the verification of the RTX extensions on your platform, proceed with the i nstallation of

WinAC RTX.

Installation

26 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Installing the WinAC RTX Software

The WinAC RTX installation begins when you click the square under Step 3 of the setup screen. If the

Setup program is not runni ng, double-click the setup.exe file on the CD.

Note: You must remove a ny previous versions of WinAC or RTX from your computer and you must

have Windows administrator (ADMIN) privilege s to install the WinAC RTX software.

From the list of WinAC RTX components, select the components to be installed:

After you make your selections and clic k the Next bu tton, the Setup program continues. Proceed through

the installation dialogs.

During the installation proce ss, you cho ose which setup type you prefer:

• Typical: installs all software and by defa ult, all documentation in all supported languages

• Minimal: installs WinLC RTX in only one language and with no documentation, requiring the least

amount of disk space

• Custom: installs the languages, online help, and manuals that you select on subsequent dialogs

You can also choose to license WinAC RTX during the installation process or at a later time.

Note: If you have SIMATIC NET installed on your computer, an d you get messages from

SIMATIC NET that say the CP card is configured for use with SIMATIC NET and STEP 7, click OK.

This is a normal part of the installation process.

The Setup program notifies you when the installation is complete.

Installation

Windows Automation Center RTX incl. SP2 27

A5E00992447-01

Licensing the WinAC RTX Software

The WinAC RTX software requires a product-sp ecific license that you install using the Automation License

Manager. Each SIMATIC automation software product (for example, STEP 7) has a separate license. You

must install the license for each produ ct.

Installing the License during Installation

When you install the software for the first time, the Automation License Manager is part of the i nstallation

set. If it is not already on your computer, select the Automation License Manager checkbox during

installation. A subsequent dialog allows you cho ose whether to install the license during installation. Refer

to the Automation License Manager online help for help with installing a license.

Installing the License at a Later Date

If you attempt to start the WinAC RTX software and no license is found, a prompt appears on the

screen. You use the Automation License Manager to install the license. If the Automation License Manager

is not installed on your computer, follow these step s to install the Automation Licen se Ma nager and license

WinLC RTX:

1. Insert the WinAC RTX inst allation CD.

2. From the Welcome screen, click the square for Step 3.

3. When the Components dial og appears, select the Automation License Manager checkbox.

4. After the installation is complete, select the Start > SIMATIC > License Management >

Automation License Manager menu command or launch the Automation License Manager from

the desktop.

5. Proceed with license installation acco rding to the instructions in the Automation License Manager

online help.

If the Automation License Manager is already in stalled on your computer, follow the last two steps of the

preceding procedure to license WinLC RTX.

Transferring an Installed License

The Automation License Manager p rovid es steps to transfer a license from one computer to another

computer. The two comput ers do not have to be connected over a network to perform an offline transfer of

license keys. Refer to your Automation Li cense Manager online help for assistance.

Running the WinLC RTX Controller without a License

If no license for WinAC RTX exists on your computer, the WinLC RTX controller continues to operate;

however, a notification message appears peri odically to alert you that the license is missing.

Recovering the License in Case of a Defective Hard Drive

If a fault occurs with the license file on your hard disk, contact your local Siemens representative.

Installation

28 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Uninstalling Ardence RTX or WinAC RTX

Use the following procedu re to remove Ardence RTX or WinAC RTX from your computer. If you are

uninstalling both, ensure that you uninstall WinAC RTX first:

1. Double-click the Add/Remove Programs icon in the Windows Control Panel.

2. Select the Ardence RTX or SIMATIC Windows Logic Controller RTX component entry in the

displayed list of installed software. Click Add/Remove to uninstall the software.

If the Remove Shared File dialog boxes appear, click No if you are unsure how to respon d.

Evaluating your RTX Installation for your Application

WinLC RTX must work together with the Ardence re al-time extensions and your DP interfaces to control

your process. After you install Ardence RTX, check your platform for RTX suitability. In addition, check for

potential conflicts between your DP interfaces and other devices that can affect the performance of DP I/O

communications.

Evaluating your Platform for RTX Suitability

For uniprocessor (single processor) computers, Ardence provides a Platform Evaluator tool that measures

the suitability of the platform for real-time control with the Ardence RTX extensi on. Some hardware, such

as video cards and network cards, can add conside r able jitter or interrupt latency (time-lag between an

interrupt and the handling of the interrupt) to an RTX application. The Platform Evaluator measures timer

response latencies, thread switch times, and other aspects that can affect performance and allows variou s

loads to be placed on the h ardware while gathering these statistics. If your control application is highly

time-critical, run the Ardence Platform Evaluator in addition to performing the basic verification tasks of the

Installation Wizard.

The RTX Platform Evaluator is not included with WinAC RTX. Contact Ardence to obtain the RTX Platform

Evaluator and information about how to install and use it.

Note: The Platform Evaluator works only for uniprocessor syst em s.

Evaluating Performance of DP Interfaces with RTX

Evaluate whether your computer can be configured to provide a non-shared interrupt (IRQ) for the DP

interfaces. When a DP interface share s an IRQ with another d evice, the DP interface operates in polled

mode. In order to use an isochronous DP cycle fo r communi cating with the DP I/O, the DP interface must

run in interrupt mode. To run the DP interface card in interrupt mode, it must use an interrupt level (IRQ)

that is not shared with another device.

Running a DP interface in interrupt mode is also more efficient than running in polled mod e. If your

application is highly time-critical, or requires a n isochr onous DP cycle, refer to the topic Improving the

Performance of a DP Interface.

Windows Automation Center RTX incl. SP2 29

A5E00992447-01

Getting Started

The Getting Started section helps you to establi sh communications between the controller, STEP 7, and

I/O devices. You must perform the following tasks:

• Use the Station Configuration Editor to designate a communi cation interface as a submodule of

WinLC RTX.

• Use STEP 7 to configure the hardware a nd STEP 7 user program and to download the system

blocks.

The Getting Started section also helps you understand the basic concepts for setting up a PC-based

controller: PC station, Communication Interface, Index, Submodule, and Interfa ce (IF) Slot.

Understanding the Concepts

What Is a PC Station?

The PC station is a software-based virtual rack, represented in the Station Configuration Editor, for creating

a PC-based automation system. Like a hardwa re rack of an S7 CPU-based automation system, it contains

space for several modules required for the PC-based automation system.

When you install the WinAC RTX software, the controller appears by default in the seco nd slot (index) of

this virtual rack in the Station Configuration Editor. The PC Station is also rep re s ented in the STEP 7

Hardware Configuration editor. The controlle r in the PC Station con t ains four configurable IF Slots for

designating communicatio n interfaces a s sub modules to be used for communication with distributed I/O,

STEP 7, or other S7 applications.

Getting Started

30 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Communication Model with S7-400

A PC-based controller is similar to an S7-400 hardware controller. The S7-400 controller consists of

modules in a rack that communicate over the backplane bus of the rack. Communications for an S7-400

are defined as follows:

• STEP 7 communicates with the controller (in this example, an S7-400 CPU module) over an

MPI subnet, using a CP card that is installed in the computer.

• The controller communicates with expan sion modules over the backplane bus of the rack.

• The S7-400 CPU communicates with d istributed I/O over a PROFIBUS-DP subnet using a built-in

submodule interface or an IF module.

In an S7-400 station, the following types of communications are possible:

Onboard Interfaces CP Modules used over Backplane Bus

Operation of PROFIBUS DP I/O

Supported interfaces:

• MPI

• PROFIBUS

Operation of central I/O

Supported communication pro ce ssors:

• PROFIBUS

• Industrial Ethernet

Getting Started

Windows Automation Center RTX incl. SP2 31

A5E00992447-01

Communication Model with PC Station and PC-based Controller

WinLC RTX uses communi cation interfaces such as CP 5613 cards for communication ta sks and access to

distributed I/O. You can configure and use communication interfaces in WinLC RTX in one of two ways:

• Submodule configuration: A communication inte rface configured as a submodule operates in the

real-time subsystem and provide s optimal performance and stability for communi cation with

distributed I/O. Submodules of WinLC RTX are similar to the onb oard communication interface s of

an S7-400 controller.

• PC Station configuration: A communication interface configured in the PC Station operates in the

Windows operating sy stem and is available for a variety of communication tasks. It cannot,

however, be used for WinLC RTX com m unication with distributed I/O. PC Station communication

interfaces are similar to CP modules inst alled in the rack of an S7-400 controller. WinLC RTX uses

a virtual backplane bus that is similar to the S7 CPU backplane bu s for communication with

components in the PC Station and with other PC applications on the computer with WinLC RTX.

Note: Configuring communication interfaces as su bmodules of WinLC RTX requires no additional

software; configuration in the PC Station requi res the installation of SIMATIC NET, a separate

software package.

The following table lists the characte ristics of the two types of communication:

Submodule Communication

(similar to onboard interface on an S7 CPU) PC Station Communication

(similar to a CP module communicating over

the backplane bus of an S7-400 sta tion)

Operates exclusively in the real-time sub system

Access to PROFIBUS-DP I/O

Supported protocols/communication types:

• PROFIBUS

• PG/OP communication

• S7 communication

• S7 routing

• DP I/O

Operates in the Windows environment

No access to PROFIBUS-DP I/O (or central I/O)

Supported protocols/communication types:

• PROFIBUS

• PG/OP communication

• S7 communication

• S7 routing

• Industrial Ethernet

• PG/OP communication

• S7 communication

• S7 routing

Getting Started

32 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Submodule Communication

(similar to onboard interface on an S7 CPU) PC Station Communication

(similar to a CP module communicating over

the backplane bus of an S7-400 sta tion)

Does not require SIMATIC NET installation Requires SIMATIC NET installation

Refer to the topic "What Is a Communication

Interface?" for a list of communication interfaces

that WinLC RTX supports.

Refer to the SIMATIC NET documentation for a

list of supported communication interfaces.

Configuration for a PC-based Controller

You use the Station Configuration edito r to configure components of the PC Station. You edit the propertie s

of WinLC RTX in the Station Configuration Editor to configure su bmodules.

In the same way that you use STEP 7 to create the system and program blocks for an S7-400, you use the

STEP 7 Hardware Configuration tool to configure the comp onents that you installed in the PC station.

After you complete hardware configurat ion in STEP 7 and submodule configuration with the Station

Configuration Editor, you can downloa d your STEP 7 user program to the controller.

Note: To use the CP card for communicating with both STEP 7 and with the distributed I/O may

require an additional software license. See your Siemens sales representative or distributor for

more information.

What Is a Communication Interface?

A communication interface is a CP card, built-in PROFIBUS interface on a Sieme ns Box, Rack, or Panel

PC, or any card or service sup ported by SIMATIC NET for the purpose of communication. Communication

interfaces enable communication b etween WinLC RTX and STEP 7 or other S7 appli cation s.

What Is a DP Interface?

DP interfaces are communication inte rfaces that you can configure as WinLC RTX submodules to enable

communications b etween WinLC RTX and distri buted I/O over a DP-subnet. You must configure a DP

interface as a submodule of WinLC RTX in order to use it for DP I/O communications.

Getting Started

Windows Automation Center RTX incl. SP2 33

A5E00992447-01

What Is a PC Station Communication Interface?

With SIMATIC NET, you can configure Industrial Ethernet or oth er communication interfa ces in the PC

Station. You can use these communication interfaces for S7 communication, but they cannot be used to

communicate with DP I/O.

The following table shows the communication interfaces that you can configure as Wi nLC RTX submodules

as well as some that you can only configure in the PC Station with SIMATIC NET:

Communication Interface Submodule:

DP I/O, PG/OP,

S7, S7 Routing

PC Station:

PG/OP, S7,

S7 Routing

CP 5613 V3 or CP 5613 V6 or later

CP 5613 A2, all hardware revisions

CP 5611 hardware revision 5 or later

CP 5611 A2, all hardware revisions

SIEMENS PC with built-in CP 5611 PROFIBUS interface:

ASPC2 STEP E2 or ASPC2 STEP R ASIC

Communication interfa ce that SIMATIC NET su pports

such as Industrial Ethernet, Teleservice adapter, CP 1613

and others.

N/A

Getting Started

34 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

What Is an Index?

An index is a numbered slot in the virtual rack of the PC station. The PC Station provides slots for WinL C

RTX and the SIMATIC components of a PC-based a utomation solution. The following list shows some (but

not all) of the typical SIMATIC components that can occupy an index:

• CP card(s) (requires installation of SIMATIC NET)

• SIMATIC HMI

• SIMATIC NET OPC Server (requires installation of SIMATIC NET)

• CPU 41x-2 PCI (WinAC Slot PLC)

Each slot in the PC station corresponds to a number or index. When you install WinLC RTX, the setup

configures the controller in the second index slot by default. The Station Configuration Editor shows the

configuration of your PC station.

The index number for a component can be any index number you choose; however, the index number in

the Station Configuration Editor must be the same as the slot number in the STEP 7

Hardware Configuration tool for the same compone nt.

Note: If you have deleted WinLC RTX from the Station Configuration Editor, the Start > Simatic >

PC-based Control menu does not hav e an entry for WinLC RTX. To restore this menu selection,

you must configure WinLC RTX in an index of the Station Configuration Editor.

Getting Started

Windows Automation Center RTX incl. SP2 35

A5E00992447-01

What Is a Submodule?

A submodule is a configured communication interface that enables communication between WinLC RTX

and distributed I/O or between WinLC RTX and STEP 7 or other S7 applications.

In order for WinLC RTX to communicate with DP I/O devices on a PROFIBUS-DP network, you must

designate a DP interface as a submodule for the controller. With this submodu le approach, WinLC RTX

has full control over the DP I/O communications, providing optimum performance an d determinism for

operating the I/O. WinLC RTX supports up to four submodule s configured in any of the four IF slots. Wi nLC

RTX does not support the use of an Indu strial Ethernet interface for DP I/O communication. You cannot

configure an Industrial Ethernet interface as a submod ule of WinL C RTX, but with SIMATIC NET you can

configure one or more in the PC Station to be used for PG/OP or S7 communications.

If you use a CP 5611 card or built-in CP 5611 PROFIBUS interface as a submodule of WinLC, note that

you can insert only one as a subm odule.

Configuring a DP interface as a

submodule of WinLC RTX i s like

installing an IF module into a slot of an

S7-400 CPU.

Designating a DP interface as a

submodule of WinLC RTX not only

allows WinLC RTX to use that interface

for PG/OP communication, but also

allows WinLC RTX to use that interface

for communicating with the DP I/O.

In order for a submodul e to be used for SIMATIC communication s with an application other than

WinLC RTX (on the PC station), the se cond application must be a configured part of the PC station.

Note: Configuring a DP interface as a component of the PC Station requires the installation of

SIMATIC NET. As a component of the PC station, you can use the communica tion interface only for

SIMATIC communications with STEP 7, SIMATIC HMI, or other SIMATIC controllers. For example,

you can download a program from STEP 7 to WinLC RTX. A DP interface configured as a

component of the PC Station cannot be use d for WinLC RTX communications with DP I/O.

The comparison below shows the difference between a DP interface (in this case a CP card) as a

submodule of WinLC RTX and as a component of the PC station:

WinLC RTX Submodule Communication PC Station Communication

With a DP interface configured as a subm odule,

WinLC RTX can communi cate with both STEP 7

on a remote computer (using PG/OP

communication) an d with the DP I/O on the

PROFIBUS-DP subnet.

With a communications interface co nfigured as

a component of the PC station, WinLC RTX can

communicate with STEP 7 on a remote

computer, but cannot com municate with the

DP I/O.

Getting Started

36 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

What Is an IF Slot?

WinLC RTX provides four interface (IF) slots fo r designating communication interfaces as submod ules.

WinLC RTX has exclusive control of any card configured in an IF slot. The submodules enable the

controller to communicate with distributed I/O, or with STEP 7 or other S7 applications.

To use the PROFIBUS-DP network to communicate with I/O, you must configure at least one DP interface

to be a submodule of WinLC RTX. You use the WinLC Properties dialog to assi gn a communication

interface to one of four interface slots, IF1 through IF4:

If you use a CP 5611 card or built-in CP 5611 PROFIBUS interface as a submodule of WinLC, note that

you can insert only one as a subm odule.

The IF slot number of the submodule is independe nt of the PCI hardware slot. However, the IF slot number

for the submodule in WinLC Prop erties must match the IF slot number in the STEP 7 Hardware

Configuration tool.

For information on submodule configur ation, refer to the following topic: Designating a Communication

Interface as a Submodule.

Getting Started

Windows Automation Center RTX incl. SP2 37

A5E00992447-01

Configuring Communication Interfaces

Designating a Communication Interface as a Submodule

You configure a communication inte rface as a submodule of WinLC RTX by inserting it into an IF slot of the

controller. Submodule comm unication interfaces enable WinLC RTX to communicate with STEP 7 or other

S7 applications. Submodule DP interfaces communicate with distributed I/O over the PROFIBUS-DP

network.

You use the Station Configuration Editor to insert a comm unication interface into an IF slot of WinLC RTX.

You must also configure WinL C RTX, the submodules, and all other components of the PC station in

STEP 7.

To configure your communication Interfa ce a s a su bmodule, ensure that the controller is shut d own and

follow these steps:

1. Double-click the computer icon on the Windows taskbar to open the Station Co nfiguration

Editor.

2. Right-click WinLC RTX and select Properties from the context menu to display the WinLC

Properties dialog.

The WinLC Properties dialog displays the four submodule interfaces (IF1 to IF4) in the uppe r panel

and a list of available communication interface s in th e lower panel. The following example shows a

CP 5611 card already confi gured in IF Slot 2 and a CP5613/CP5614 card being added as a

submodule.

3. In the lower panel, select the communi cation interfa ce that you want to configure as a submodule.

(A built-in PROFIBUS interface is represented as a CP5611 card with a location of "System

Board.")

Getting Started

38 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

4. Drag the selected device to an empty interface slot (IF slot) in the upper panel or click the Ad d

button to add the card to the first available interface slot.

For multiple cards, repeat the above ste ps as needed.

5. Click OK on the WinLC Properties dialo g to accept your changes and to configure the

submodule(s). This configuration may ta ke several seconds.

Note: WinLC RTX suppo rts a maximum of one CP 5611 card or built-in CP 5611 PROFIBUS

interface as a submodule and a maximum of four CP 5613 cards a s su bmodules. You can

configure any combination of commu nication interfaces in the four interface slots as long as you

observe these maximums.

You can select an occupied interface slot (IF slot) and click the Edit button to change the interface slot

assignment for a configured DP interfac e, or to change its name. You can also use the up/down arrow keys

on the keyboard to move a submodule t o a different interface slot.

WinLC RTX Response to Submodule Changes

WinLC RTX can detect when a co nfigured submodule is no longer accessible, for example, when it has

been physically removed from the comp uter or it has failed.

In previous releases, WinLC RTX del eted the STEP 7 user program and configuration in this case. Now,

WinLC RTX informs you of the detected change and continues to operate without that submod ule;

however, you cannot set the controller to RUN mode. The diagnostic buffer also includes a "STOP cau se d

by I/O error", which indicates the del eted or failed submodule.

The next time you attempt to access WinLC Properties , WinLC RTX informs you that a submodule is no

longer accessible and prom pts you to confirm the re moval of that submodule. If you click OK, WinLC RTX

deletes that submodule from WinLC Properties. If you cancel, WinLC RTX leaves the submodule

configured and retains the current STEP 7 user program and configuration.

Getting Started

Windows Automation Center RTX incl. SP2 39

A5E00992447-01

Testing a CP 5613 Configuration

The WinLC Properties ring test allows you to verify whether a submodule CP 561 3 card is configured

correctly. This test is especially important if you have installed more than one CP 5613 card i n your

computer. This test is not available for a CP 5611 card.

To check the operation of the submodule CP card, follow these steps:

1. Start WinLC RTX if it is not already started. (The ring test is only available when WinLC RTX is

operating.)

2. Double-click the computer icon on the Windows taskbar to open the Station Co nfiguration

Editor.

3. Double-click the WinLC RTX index entry to display the WinLC Properties dialog.

4. Select the interface slot (IF slot) containing the CP card to be tested.

5. Click the Ring ON button.

The LEDs on the CP card at the back of your computer flash in an alternating pattern so you can

verify that you have configured the correct CP card. The computer also emits an audible beep if the

CP card is functioning.

6. Click the Ring OFF button to end the test of the CP card.

Getting Started

40 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Viewing the Submodule Diagnostics of a DP Submodule

You can select an interface slot

(IF slot) occupied by a CP card

and click the Diagnostics button

to view communication

information for a CP card. The

Submodule Network Diagnostics

dialog displays the current

version of the selected CP card

and the bus parameters.

You can also see a displ ay of all

of the nodes on the

communication network, and the

status of each one. You must

click the Update button to build

this display, because querying

each node puts an additional

load on the communication

network.

For some operations, such as

isochronous mode, the DP

interface must operate in

interrupt mode. You can improve

the performance of the DP

interface by changing the IRQ

settings. See the following topic:

Improving the Performance of a

DP Interface in the

Troubleshooting section of the

Reference Information.

Note: Submodule diagnostics are availa ble for CP 5613 and CP 5611 ca rds, including built-in

PROFIBUS ports on Siemens PCs.

Getting Started

Windows Automation Center RTX incl. SP2 41

A5E00992447-01

Removing a Submodule

From the WinLC Properties dialog, you can move a DP interface that is config ured as a submodule of

WinLC RTX to the set of available cards in your computer.

To remove a DP interface from the WinLC RTX subm odule configuration, ensure that the controller is shut

down and follow these steps:

1. Double-click the computer icon on the Windows taskbar to open the Station Co nfiguration

Editor.

2. Right-click WinLC RTX and select Properties from the context menu to display the WinLC

Properties dialog.

The WinLC Properties dialog displays the four submodule interfaces (IF1 to IF4) in the uppe r panel

and a list of available communications card s in the lower panel. The following example shows a

CP5613/CP5614 card being removed as a submodule, leaving a CP 5611 card in IF Slot 2.

3. In the upper panel, select the communi cation interface that you want to remove as a submodule.

4. Drag the selected card to an available p osition in the lowe r panel or right-click the selected ca rd

and click the Delete button or Delete key from the keyboard. After you confirm your action, the card

is removed as a submodul e and returned to the list of available cards.

5. Click OK on the WinLC Properties dialog to accept your changes.

Getting Started

42 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Configuring the Controller in STEP 7

Connecting STEP 7 to the Controller

You must establish a connection from STEP 7 to the controller to download the configuration and blocks of

the STEP 7 user program. This type of communication is called PG/OP communication. The controller can

connect to STEP 7 through any of the following interfaces:

• Virtual backplane bus to STEP 7 on the same computer as the controller

• Submodule communications interface t o STEP 7 on a different computer

• PC Station communications interface to STEP 7 on a different computer

Note: Configuring a communications interface in the PC Station and not as a submodule requires

the installation of SIMATIC NET, an additional software package.

Connecting STEP 7 to the Controller on the Same Computer

On the same computer, STEP 7 and the controlle r communicate across the virtual backplane bus:

To configure communicati ons between the controller and STEP 7 on the same computer, use the PC

internal access point:

Getting Started

Windows Automation Center RTX incl. SP2 43

A5E00992447-01

Connecting STEP 7 to the Controller on a Different Computer

STEP 7 can communicate to WinAC RT X on a different computer or programming device through a

communications inte rface that is configured as a submodule of the controller or through a communications

interface that is configured in the PC Station. To configure a comm unications interface in the PC Station

requires SIMATIC NET to be installed o n your computer.

The following communications type s are supported:

• PROFIBUS: for a CP 5613, CP 5611, or built-in PROFIBUS interface configured as a submodule

• Industrial Ethernet: for an IE card config ured in the PC Station

To configure communicati ons between the controller and STEP 7 on a different computer or programming

device, set the PG/PC interface to the access point for the specific communications interface and the type

of communications, for example an Industrial Ethernet card using the TCP/IP protocol:

You can connect STEP 7 to a WinAC RTX on a different computer though the PC Internal interface if the

following conditions are met:

• WinAC RTX is installed on the computer where STEP 7 is installed.

• The computer with STEP 7 and a local WinAC RTX installatio n is connected to a network to which

WinAC RTX on the other computer is co nnected.

If these conditions are met, you can set the S7ONLINE access point to PC Internal on the computer with

STEP 7 and connect to the remote WinAC RTX through the PC Internal interface. This connection method

is an alternative to connecting STEP 7 to a remote WinAC RTX through a PROFIBUS or Industrial Ethernet

interface, as described earlier.

Getting Started

44 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Hardware Configuration in STEP 7

You configure the STEP 7 project for a PC station with a PC-based controller in STEP 7 as you would for

any S7 hardware controller. Refer to the STEP 7 help system a nd documentation for detailed information.

Creating the Project and PC Station with the SIMATIC Manager

To create the project and PC station, follow these ste ps:

1. Select the File > New menu command from the SIMATIC Manager to create a new project.

2. Select the Insert > Station > SIMATIC PC Station to insert a PC station into th e project.

3. Change the name of the PC station to match the name of the PC station defined in the

Station Configuration Editor on the com puter where WinLC RTX resides. To find the station name,

open the Station Configuration Editor and click the Station Name button.

Configuring the PC Station Hardware with the STEP 7 Hardware Configuration Application

To configure the PC-based controller and DP I/O for the PC Station, follow these steps:

1. Open the PC Station folder in the project and double-click the Configuration icon to invoke the

STEP 7 Hardware Configuration applicat ion.

2. Navigate to your specific controller under SIMATIC PC Station.

Getting Started

Windows Automation Center RTX incl. SP2 45

A5E00992447-01

3. Drag the controller into the same index it occupies in the Station Configuratio n Editor on the target

computer.

4. Verify that the name of the controller matches the name of the controller configured in the Station

Configuration Editor.

5. Drag the submodule CP card fro m the Hardware Catalog into inte rface slots (IF slots) for the

WinLC RTX controller. The WinL C RTX folder in the Hardware Catalog lists the CP card types that

are available. (For built-in PROFIBUS interfaces on SIEMENS PCs, you select a CP5611 card.)

The submodule cards d o not have to have the same name as in the PC Station configuration;

however, this is recommended. They must have the same type and interface (IF) number as

specified in the Station Configuration Editor.

If you use a CP 5611 card or built-in CP 5611 PROFIBUS interface as a submodule of WinLC, note

that you can insert only one as a submodule.

6. Configure the distributed I/O for each of the submodule DP networks.

Getting Started

46 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Additional Hardware Configuration Options

The following tasks are optional, depending on your specific application:

1. Insert any CP PROFIBUS or CP Industrial Ethernet cards that your application requires into the PC

Station.

Note: You must have installed SIMATIC NET to configure CP cards or Etherne t cards in

the PC Station with the Station Configuration Editor. You do not need SIMATIC NET to

configure CP cards as subm odules of WinLC RTX.

2. Insert any HMI devices, for example, text displays or operator panels.

3. Configure WinLC RTX for peer-to-peer communicati ons:

a. Select the controller name in the SIMATIC Mana ger.

b. Double-click the Connections icon in the right-hand pane.

c. Use NetPro to describe the network.

After you have configured WinLC RTX y ou can use SIMATIC Manager to develop and to download your

STEP 7 user program.

Caution

Downloading a STEP 7 user program that is too large for the memory of the computer

can lock up the computer or cause the operation of WinLC to be come unstable,

possibly causing damage to equipment and/or inj ury to person nel.

Although STEP 7 and WinLC do not limit the number of blocks o r the si ze of the STEP

7 user program, your computer does have a limit, based on the available drive space

and RAM memory. The limit for the size of the STEP 7 user program and number of

blocks for your computer can only be determined by testing a configured system

against the requirements of your control application.

After you have downloaded your program to the controller, you can start the controller and use STEP 7 to

monitor and modify the process variabl es.

Getting Started

Windows Automation Center RTX incl. SP2 47

A5E00992447-01

Correcting Invalid Characters in Earlier STEP 7 Versions

You can use STEP 7 to create a name for the controller and to download the configuration with the new

name to the controller. However, some cha racters that might have been used in controller names in

versions of STEP 7 prior to V5.3 SP1 are invalid. Change these controller names to valid controller names

prior to downloading.

Caution

Prior to STEP 7 V5.3 SP1, using an invalid character in the cont roller name creates an

instance of the controller that cannot be restarte d.

Downloading a configuratio n that uses an invalid character in the controller name creates

an invalid instance of the controller. This invalid instance will continue to run and will

remain connected to STEP 7 until you shut down the controller. However, the desktop

icon and the Start menu command will be removed. Without the desktop icon or Start

menu command, you cannot restart the controller after it has bee n shut down.

Avoid the use of the invalid characters in controller names.

Invalid Characters

The following table describes invalid characters for controller names prior to STEP 7 V5.3 SP1 or SP2:

Character Name

/ Forward slash

(Problematic in versions prior to STEP 7 V5.3 SP1)

. Period

(Problematic in versions prior to STEP 7 V5.3 SP2)

- Hyphen (also called a dash or a minus sign)

(Problematic in versions prior to STEP 7 V5.3 SP1)

You cannot create a name that begins with a hyphen (-). You can, however, use a

hyphen within the name of the controller.

Valid:

Pump-1: Using a hyphen in the middle of the name is valid.

Pump1-: Using a hyphen at the end of the name is valid.

Invalid:

-Pump1: Using a hyphen at the beginning of the name is invalid.

-: Using a hyphen as a one-character name is invalid.

If you inadvertently downloaded a name that contains an invalid characte r, follow these steps to correct the

problem:

1. Using the STEP 7 Hardwa re Configuration application, rename the controller to the previous valid

name (the name prior to downloadin g the invalid name).

2. Download the configuration with the previous valid name to the PC station (even if the controller is

not running).

After downloading the valid name for the controller, the desktop icon and the Start menu command

reappear. You can now rename the controller to a new name that does not use invalid characters.

Getting Started

48 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Verifying the Configuration

A complete configuration for a PC-based automation project includes a configuration in the Station

Configuration Editor and WinLC Properties that matches the config uration in STEP 7.

Example PC Station Configuration

The following configuration is an exampl e of a PC-based automation project:

• WinLC RTX controller in index 2 of the PC station

• CP 5611 card configured as a Win LC RTX submodule in IF slot 2 connected to PROFIBUS -DP I/O

• CP5613/CP5614 card conf igured as WinLC RTX submodule in IF slot 3 connected to PROFIBUS-

DP I/O

• STEP 7 on same computer as WinLC RTX

The following pictures sho w the re sult of this configuration:

Station Configuration Editor and WinLC Properties

The Station Configuration Editor and WinLC Properties dialog show the configuration of the project:

Getting Started

Windows Automation Center RTX incl. SP2 49

A5E00992447-01

STEP 7 PG/PC Interface

The STEP 7 PG/PC interface show s the PC internal access point:

STEP 7 Hardware Configuration

The STEP 7 hardware configuration shows WinLC RTX in slot 2 of the hardware configuratio n and the two

submodule DP interfaces:

Windows Automation Center RTX incl. SP2 51

A5E00992447-01

Controller Operations

Starting and Shutting Down the Controller

The controller operates independently from the controller panel:

• Closing the panel (menu command File > Exit) does not shut down the controller.

• Shutting down the controller does not close the panel.

The following settings affect the starting or shutting down of the controller:

• Selecting the Autostart option

• Configuring the controller for sta rt at PC boot

Starting WinLC RTX

If the controller panel is not open, use one of the following methods to start the controlle r panel and WinLC:

• Select the Start > Simatic > PC Based Control menu command. Then select the name of your

WinLC controller. (After you have downl oaded the STEP 7 user program to your WinLC, the name

in the menu matches the name in STE P 7.)

• Double-click the desktop icon for WinLC:

If the controller panel is open, but the controlle r is shut down, select the CPU > Start Controller menu

command.

Shutting Down WinLC RTX

Select the CPU > Shut Down Controller menu co mm and to shut down the WinLC controller. This action

does not close the controller panel. This command is only available from the controller pan el when the

controller is operating. After you shut down the controller, you can still cha nge customi zation options.

An icon is displayed in the Windows taskbar whe never the controller is operating. When the controller is

operating and the controller panel is closed, you can double-click this icon to open the controller panel.

Note: To shut down the Ardence RTX e xtensions after you shut down WinLC RTX, you must either

reboot your computer or else manually stop a WinAC service that is still runnin g. Use the Start >

Control Panel > Service menu command to display the Windows Services dialog, and then stop

the SIMATIC WinAC FeatureServer serv ice. You can then use the RTX Properties dial og to stop

the RTX extensions.

Controller Operations

52 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Changing the Operating Mode of the Controller

The controller panel provides a mod e selector switch that allows you to change the operating mode of the

controller. Set the mode selector swit ch to RUN or STOP (or select the appropriate comma nd from the

CPU menu) to change the operating mo de of the controlle r either to RUN mode or to STOP mode.

The mode selector switch p ositions on the controller panel correspo nd to the mode selector switch

positions of an S7 hardware controlle r:

• RUN: The controller executes the STEP 7 user program.

• STOP: The controller does not execute the STEP 7 user program. Outputs a re set to their safe

states.

Specific controller actions are allowed or prohibited based on the operating mode.

Operating Mode (RUN/STOP) and Status Indicators

The mode selector switch o n the controller panel functions like the manual m ode selector switch on a

hardware S7 controller allowing you to switch b etween RUN and STOP mode.

For both hardware controll ers and PC-based controllers, the RUN and STOP status indicators show the

current operating mode of the controller. If the status indicator shows a different operating mode than the

mode selector switch position, the controller has changed operating mode, possibly due to some error in

the program or because y ou used STEP 7 to change the operating mode.

Controller Operations

Windows Automation Center RTX incl. SP2 53

A5E00992447-01

Allowed and Prohibited Actions for each Operating Mode

The operating mode allows or prohibits access to the controller for some types of operations as shown in

the following table:

Operating

Mode Description

RUN Allowed:

• Uploading a program from the controller to your computer

• Downloading a program to the controller

• Downloading individual blocks to the co ntroller

• Using STEP 7 to modify program variables an d to change the operating

mode of the controller

• Performing a memory reset from either the co ntroller panel or STEP 7

The controller automatically goes to STO P mode when you reset the

memory from the controller panel. To perform a mem ory reset from

STEP 7, you must first change the controller to STOP mode.

Not Allowed:

• Archiving and restoring a S TEP 7 user program

STOP Allowed:

• Uploading a program from the controller to your computer or

programming device

• Downloading a program or individual blocks to the controller

• Using STEP 7 to modify program variables

• Performing a memory reset from either the co ntroller panel or STEP 7

• Archiving and restoring a S TEP 7 user program

Not Allowed:

• Using STEP 7 to change the operating mode

Controller Operations

54 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Resetting the Memory Areas: MRES Command (CPU Menu)

The MRES (memory reset) command functions like a master reset of the controller by resetting the

controller to its initial (default) state. A memory reset deletes the STEP 7 user program and the system data

(configuration), and also di sconnects any online communications, for example STEP 7, WinCC Flexible,

PROFIBUS, or S7 communications.

Use one of the following methods to reset the memory:

• Click the MRES button on the control panel

• Select the CPU > MRES menu command

• Press the ALT+C+M keys

You can also use STEP 7 to perform a memory reset.

The MRES command changes the controller to STOP mode, if necessary, and then performs the followi ng

tasks:

• Deletes the entire STEP 7 user program (OBs, DB s, FCs, FBs, and the system data) from both the

work memory area and the load memory area

• Resets the memory areas (I, Q, M, T, and C) to 0

• Reloads the default system configu ration (for example, the size of the process-image areas, and

the size of the diagnostic buffer)

• Deletes all active communication s jobs (for example, TIS) and all open communications

The MRES command does not affect the submodule netwo rk addresses and does not affect the contents

of the diagnostic buffer.

The STOP indicator flashes while the memory reset is in progress. After the memory has bee n reset, the

diagnostics buffer is re sized to its default size. Input (I) and output (Q) memory areas are also resize d to

their default sizes. After a memory reset, you may need to reconfigure these values to your own

specifications.

You typically perform an MRES before downloading a new program to the controller. You must perform an

MRES if the STOP indicator on the controlle r panel is flashing slowly to alert you to one of the following

conditions:

• Errors were detected in the work memory area, for example, the size of the user program exceeds

the work memory area

• A power cycle followed a defective state of the controller

Controller Operations

Windows Automation Center RTX incl. SP2 55

A5E00992447-01

Using the Status Indicators

The status indicators on the controller p anel display the cu rrent operating mode and are helpful in

troubleshooting an error condition. These indicators correspond to the LED indicators on a hardware S7

PLC.

You cannot change the status of the con troller by clicking the status indicators.

If the STEP 7 user program reaches a break point set by the STEP 7 Program Editor, both the RUN and

STOP indicators turn on while the bre akpoint is a ctive: the RUN indicator flashes, and the STOP indicator

is on.

During a change from STOP mode to RUN mode, the RUN indicator flashes, and the STOP indicator is on.

When the STOP indicator turns off, the outputs are enabled.

The table below describes the different status indicators for the controlle r panel:

Indicator Description

ON Power supply. Lights up (solid) when you start the controller. Turns off when you shut

the controller down.

BATF Battery fault. Always off for the controller.

INTF This indicator lights up (solid) to show error conditions within the controller, such a s

programming erro rs, arithmetic errors, timer errors, and counter errors.

If the STEP 7 user program handles the error by executing OB 80 or OB 121, the

INTF indicator goes off after 3 seconds if there is no subsequent error condition.

EXTF This indi cator lights up (solid) to show error conditions that exist outside of the

controller, such as hardware faults, parameter a ssignment errors, loss of

communication or othe r communication errors, and I/O faults.

If the STEP 7 user program handles the error by executing OB 122, the EXTF

indicator goes off after 3 seconds if there is no subsequent error condition.

BUSF1

BUSF2

BUSF3

BUSF4

These indicators light up (fl ashing) to identify fault conditions in the communication

with the distributed I/O.

The number of the BUSF indicator correspond s to the IF number of the submodule

that has a fault condition.

FRCE This indicator is never lit. WinLC RTX does not support force jobs.

RUN

STOP Lights up (sol id) to show the operating mode (RUN or STOP).

When RUN is flashing and STOP is lighted (solid), the STEP 7 user program has

reached a breakpoint. (RUN light blinks with 0.5 Hz.)

Note: The RUN and STOP indicato rs show the actual operating mode of the

controller. The RUN and STOP mode selector switch position s sho w the selected

mode (similar to the mode selector switch position on an S7 CPU front panel), which

can differ from the operating mode. For example: Changing the op erating mode with

STEP 7 causes the status indicators to change, but the mode selector switch does

not change.

Controller Operations

56 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Flashing Indicators

Flashing patterns of the RUN and STOP indicators provide additional information about the controller or the

STEP 7 user program:

Indicator

RUN STOP

Description

flashing

2 Hz flashing

2 Hz The controller is in DEFECT mode. All status indicators flash.

flashing

0.5 Hz on The STEP 7 user program halted at a breakpoint.

flashing

2 Hz on A cold or warm restart is in progress. The RUN indicator continues to flash until

the restart completes. The time required for the restart operatio n depends on

the time required to execute the startup OB.

off flashing

0.5 Hz The controller requires a memory re set (MRES).

off flashing

2 Hz A memory reset (MRES) is in progress.

Corrective Action If the STOP Indicator is Flashing Slowly

If the STOP indicator flashes slowly, the controller require s a memo ry res et (MRES). To recover from this

condition, you must use the MRES command to reset the controller.

Corrective Action If All Status Indicators Are Flashing

If all of the status indicators are flashing at the same time, the controller is in a defective state and has

encountered an error condition that cannot be fixed by resetting the memory with the MRES command. To

recover from this condition, you must perform the following tasks:

1. Shut down the controller.

2. Restart the controller. The STOP indicator flashes with the RUN indicator off.

3. Use the MRES command to reset the memory.

4. Use STEP 7 to download the STEP 7 user program and system configuration, or to restore an

archived STEP 7 user program.

If either shutting down or restarting the controller does not resolve the problem, you may need to reboot

your computer.

Controller Operations

Windows Automation Center RTX incl. SP2 57

A5E00992447-01

Using the Tuning Panel

You can use the tuning panel to view and adjust the current performance of the controller. The tuning panel

displays information about the scan cycl e, such as the execution time and the sleep time. By adjusting

these values, you can tune the performance of the co ntroller.

Note: The tuning panel is designed for adjusting the parameters and verifying the performance for

WinLC. Because the tunin g panel causes an additional load on the computer resources, do not

leave the tuning panel open during no rmal operation of WinLC.

To open or close the tuning panel, sele ct the CPU > Tuning Pane l menu command. WinLC RTX opens the

tuning panel, as shown below. Click a re gion on the tuning panel picture for more information about its

functionality.

Values other than the minimum cycl e time are unique to WinLC RTX and are not stored in the system

configuration. Using the tuning panel to enter a value for minimum cycle time does not change the

configuration of the controller.

Changing the controller fro m STOP mode to RUN mode resets the minimum scan cycle time parameter to

the value that you configured in STEP 7. To make any changes made with the t uning panel permanent, you

must use the STEP 7 Hardware Configuration tool.

Caution

Variation in the execution time or response time of the STEP 7 user program could

potentially create a situation where the application b eing controlled can operate

erratically and possibly cause damage to equipm ent or injury to personnel.

If the controller does not provide sufficient sleep time for the other applications to run,

the computer can become unre sp onsive to operator input, or the controller and other

applications can operate erratically. In addition, the ex ecution of the STEP 7 user

program can experience non-determi nistic behavior (jitter) such that execution times

can vary and start events can be delaye d.

Always provide an external emergency stop circuit. In addition, always tune the sleep

time and manage the performance of the controll er so that your STEP 7 user program

executes consistently.

Controller Operations

58 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

The tuning panel contains the following functional areas:

Area Description

Cycle Time This area provides a histogram of execution times of the scan cycle over a 60-ms

range. This histogram tracks minimum (shorte st) and maximum (longest) scan times,

as well as the percentage of scans that fall in various ranges of scan times. To delete

the historical data and start a new histogram, click Clear. A STOP-to-RUN transition

also resets the Cycle Time display, as does closing and reopening the tuning p an el.

Timing

This read-only field displays the following information about the scan cycle:

Execution Time displays the execution time for the last (most current) scan, the

average scan cycle time, the shortest (minimum) scan cycle time, and the longest

(maximum) scan cycle time.

Sleep Time displays the amount of sleep time for the last (most current) scan.

Priority Use this slider to set the priority level for the execution of WinLC RTX relative to other

RTX applications running on your co mputer.

Because WinLC RTX run s at a higher priority than any Windows application, you

change the priority for WinLC RTX only if you are ru nning other RTX applications.

Setting the priority higher means that the operating system respo nds to WinLC RTX

before executing lower-priority tasks. This results in less jitter in the start times and

execution time of the OBs in your program.

Timing

Adjustment Use these fields to tune the scan cycle b y entering values for the minimum sleep time

and the minimum cycle time. These parameters determine the amount of sleep time

that is added at the end of the free cycle.

Click the Set button to apply these values. Click the Restore button to reset the

values to those currently being used by the controlle r. After you apply new values,

the panel stores these values for the cont roller and you can monitor the effect on the

execution of your control program.

To ensure that the minimum cycle time controls the sleep time for the controlle r, you

must configure the scan cycle monitoring time and minimum scan cycle time

parameters on the Cycle/Clock Memo ry tab of the Properties dialog box in STEP 7.

Set the minimum scan cycle time to a value less than the value for scan cycle

monitoring time. (The default scan cycle time is 6 seconds.)

Controller Operations

Windows Automation Center RTX incl. SP2 59

A5E00992447-01

Using the Diagnostic Buffer

Select the CPU > Diagnostic Buffer menu command to display the SIMATIC Diagnostic Buffer.

The Diagnostic Buffer allows you to view system diagnostic information without using the SIMATIC STEP 7

programming software. It consists of an upper panel that displays an event list and a lower panel that

displays specific event details.

The diagnostic buffer is implemented as a ring buffer that contains single event entries. The events are

displayed in descending order by time, with the most recent event at the top. If the ring buffer is full, a new

event overwrites the oldest entry in the buffer.

The Diagnostic Buffer displ ays the following information:

Event List (upper p anel): A list of all the events in the diagnostic buffer. The following information is shown

for each diagnostic event:

• The number of the entry

• The date and time of the event

• A brief description of the event

Event ID (between the upper and the lower panels): Displays the ID number of a selected ev ent.

Event Details (lower panel): Displays th e event details in either text or hexadecimal format.

If you have chosen Text format, the following details about a selected event appear in the lower panel:

• A brief description

• Additional information, depending on the event, such as the address of the instruction that caused

the diagnostic event and the mode transition that was caused by the event

• The event state (incoming or outgoing)

Controller Operations

60 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

If a single parameter of text cannot be identified, the diagnostic buffer displays the string "###" . If no text

exists for new modules or new events, the event numbers and the single parameters are displayed as

hexadecimal values.

If you have chosen Hexadecimal format, the hexadecimal values of the sele cted event appear in the lower

panel.

Sorting Events (upper panel)

You can sort the events listed in the upp er panel by clicking the specific column:

• Number (determined by time and date)

• Event description

Choosing Format (lower panel)

You can display the diagnostic information in the lower panel in text or hexadecimal (Hex) format. In Hex

format, the hexadecimal values of the 20 bytes of the selected event are displayed. To sele ct the format:

• Click Text to display the event details in text format.

• Click Hex to display the hexadecimal values of the event.

Selecting the Time Type

If you select the "Time including CPU/local time difference" checkbox, the diagnostic buffer applies a

correction value to the time-of-day. Use this setting if the location of the diagnostic buffer reader is in a

different time zone than the module. You can only select the chec kbox for modules which support time-of-

day status.

If you do not select the "Time including CPU/local time differen ce" checkbox, the diagnostic buffer displays

the entries with the time of day of the module. Use this setting if this time is the same as the time at the

location of the diagnostic buffer re ader (the same time zone).

If you change the settings, the diagnostic buffer immediately updates the time stamps of the entries.

Updating the Diagnostic Buffer

To display the most up-to-date information in the window, select the "Update" button.

Saving the Diagnostic Buffer

To save a text file containing the event list and the detailed information for every event, click the Save

button. The text file contains the information either in text or in hexadecimal format.

Displaying Help

To display help on the diagnostic buffer, click the Help button. To display help on a specific event:

1. Select the event in the upper panel.

2. Click the Help on Event button.

Controller Operations

Windows Automation Center RTX incl. SP2 61

A5E00992447-01

Archiving and Restoring STEP 7 User Programs

The Archive command enables you to save the configuration and STEP 7 user program to an archive file

(*.wld). The archive file allows you to easily restore the configuration and STEP 7 use r program for the

controller.

Note: You must update a proje ct or p rogram from a release of WinLC V3 or earlier. Use STEP 7 to

create a new project and to create a new configu ration for WinLC RTX and any submodules.

You can only archive or restore a STEP 7 user program when the controller is in STOP mode. You can not

archive or restore a STEP 7 user program when the controller is in RUN mode or is shut do wn.

The archive file functions like the removable memory cartridge (EEPROM cartridge) of an S7 CPU;

however, it differs in that the controller does not automatically restore the a rchive file after a memory reset

(MRES). You must manually restore the archive file.

Creating an Archive File

An Archive file stores the current STEP 7 user program, the current system configuratio n, and the current

values of the DBs. The Archive file does not store the configuration of the PC station.

To create an Archive file, select the File > Archive menu command. This command di splays the Save As

dialog, which allows you to give a name to the file. The controller then creates the archive file wi th the

extension .wld.

You can also use the SIMATIC Manager of STEP 7 to create an Archive file. Select the File > Memory

Card File > New menu command.

Restoring an Archive File

When you restore an archive file, you reload the STEP 7 user program and the configuration for the

controller. You can only restore archive files of extension .wld.

Before you can restore an archive file, you must set the controlle r to STOP mode. Use the following

procedure to load an archived configuration and STEP 7 user program:

1. Click the STOP button to place the controller in STOP mode.

2. Select the File > Restore menu comma nd.

3. Select the specific archive file to restore and click OK.

Closing the Controller Panel

Select the File > Exit menu command to close the control panel.

Note: Closi ng the controller panel does not shut down the controller or affect the operating mode.

An icon is displayed in the Windows taskbar whe never the controller is operating. When the controller is

operating and the controller panel is closed, you can double-click this icon to open the controller panel.

Controller Operations

62 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

WinLC RTX Operation following a Windows Blue Screen

WinLC RTX supports OB 84 (CPU Hardware Fault), whi ch allows you to initiate orde rly shutdown of your

process in case a Windows Blue Screen occurs while WinLC RTX is operating. Duri ng a blue screen,

communication interfa ce s config ured as submodules continue to function. If WinLC RTX can still operate

after Windows has initiated the system shutdown procedure, and the memory used by the real-time

subsystem is not corrupted, one of the following occurs:

• If WinLC RTX is in RUN mode and the control progra m includes OB 84, WinLC RTX starts OB 84

and continues in RUN mode until the STEP 7 user program calls SFC 46 (STP) to place the

controller in STOP mode. Windows doe s not co mplete its system shutdown until after WinLC RTX

transitions to STOP mode, either from the SFC 46 call or from a change to STOP mode initiated

from a programming device or communi cation partner accessing WinLC RTX through a subm odule

communication interfa ce.

• If WinLC RTX is in RUN mode and the control progra m does not include OB 84, WinLC RTX

transitions to STOP mode and then Windows completes its system shutdown.

• If WinLC RTX is not in RUN mode, Windows completes its system shutdown.

The operation of WinLC RTX during a blue scre en can be affected by SFC 22, SFC 23, SFC 82, SFC 83,

SFC 84, or SFC 85.

You can configure both Wi ndows and WinLC RTX to automatically restart following a blue screen.

The following restriction s a pply when Windows is shutting down:

• The WinLC RTX controller panel i s unavailable.

• Some system functions are disabled, including SFC 22, SFC 23, SFC 82, SFC 83, SFC 84, and

SFC 85.

• Block operations fail, returning an error code.

• Communication with Windows applications is unavailable; howeve r, communication with the

submodules of WinL C RTX is not affected.

• Communication with external systems (such as HMI devices or programming devices) is only

available if the network is connected to a configured submod ule of WinLC RTX.

• If the WinAC data storage is not in NVRAM, a restart of the computer followed by a restart of

WinLC RTX initializes all of the program variables to their default values and empties the diagnostic

buffer. If the WinAC data storage is in NVRAM, WinLC RTX can recover the retentive data when it

restarts. See the topic "Available Options for WinAC Data Storage" for a summary of which

SIMATIC PCs have NVRAM for WinAC data storage.

Notice

WinLC RTX cannot guarantee in all cases that it can detect a Windows Blue Screen and

continue operation. Operation is only possible if the cause of the blue screen doe s not

corrupt memory that WinLC RTX or the realtime operating system uses.

If WinLC RTX cannot detect the blue screen, it cannot call OB 84 or continue running.

You must reboot your computer to recover.

If you specified NVRAM storage for the retentive data, (either a SIMATIC WinAC NV128

card or integrated PC SRAM) and an undetected Windows Blue Screen occurs, WinAC

RTX will start with an unbuffered startup after the reboot. The controller panel lights up

the INTF status indicator, and the diagnostic buffer contains an "unbuffered power on"

error.

In actual practice, the occurrence of a blue screen is very rare, and the occurrence of a

blue screen that WinLC RTX cannot de tect is rarer still.

Controller Operations

Windows Automation Center RTX incl. SP2 63

A5E00992447-01

Considerations for SFC 22, SFC 23 and SFC 82 to 85

If a Windows Blue Screen occurs when WinLC RTX is in RUN mode, WinLC RTX attempts to stay in RUN

mode and initiates OB 84; however, the operation of WinLC RTX during a bl ue screen can be adversely

affected by SFC 22, SFC 23, SFC 82, SFC 83, SFC 84, or SFC 85.

Under most circumstances, SFC 22, SFC 23, SFC 82, SFC 83, SFC 84, and SFC 85 return error co de

8092 in the event of a Windows Blue Screen. Applications that nee d to continue operating after a blue

screen can check for this error code. If however, one of these SFCs is in a Windows call at the time of the

blue screen, the SFC is not able to return the 8092 error code and WinLC RTX cannot initiate OB 84.

Warning

Certain SFCs, if active at the time of a Windows failure, can ca use either WinLC RTX

or other functions to become unresponsive and lock up:

• If either SFC 22, SFC 23 or SFC 85 is in a call to a Windows function at the

time of the blue screen, the SFC cannot return from the SFC call and

WinLC RTX fails to maintain control of the process. If this occurs, the I/O

watchdog operation disa bles the inputs and outputs.

• If SFC 82, SFC 83, or SFC 84 is in a call to a Windows function at the time of

the blue screen, WinLC RTX attempts to stay in RUN mode (continuing to

control the process), but background operation s in cluding some

communication functio ns can lock up. Setting WinLC RTX to STOP mode,

whether by program action or by user intervention from a remote system, can

affect the shut-down sequence of the computer.

A blue screen that results in locking u p either the controller or background fun ctions

can cause damage to process equi pment or injury to personnel if you do not take

proper precautions in desi gning your STEP 7 user program.

If your process application needs to surv ive a Windows failure, call these SFCs

(SFC 22, SFC 23, SFC 82, SFC 83, SFC 84, or SFC 85) only when initializing (during

the execution of OB 100 or OB 102) or during non-critical parts of the control process.

Controller Operations

64 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

WinLC RTX Restart Behavior after a Blue Screen

If Windows is configured to reboot automatically after a Windows Blue Screen, WinLC RTX starts if it is

configured to start at PC boot.

Behavior when WinAC Data Storage is in NVRAM

If your computer supports NVRAM configuration for WinAC data storage, and you configured the WinAC

data storage for NVRAM prior to the blue screen event, then WinLC RTX restarts with the curre nt STEP 7

user program and uses the retentive data stored in the NVRAM, providing that WinLC RTX was able to

save the retentive data when the blue screen o ccurre d.

Behavior when WinAC Data Storage is not in NVRAM

WinLC RTX restarts with t he STEP 7 user program as it was last downloaded and exe cute s OB 100 (not

OB 102) if it is present. WinLC RTX executes OB 100 with event 1382 (hex) after a blue screen, even if

OB 102 "Cold Start" is configured in the STEP 7 Hardware Co nfiguration. The diagnostic buffers shows the

current/last startup type as "automatic warm reboot after non-backup power on with system memory reset".

You can program OB 100 to respond to event 1382. F or more information, see the online help for STEP 7

or the System Software for S7-3 00/400 System and Standard Functions Reference Manu al. To view this

manual from a computer where STEP 7 is installed, select the Start > Simatic > Documenta tion >

English menu command and then do uble-click "STEP 7 - System and Standard Functions for S7-300 and

S7-400".

Notice

WinLC RTX cannot guarantee in all cases that it can detect a Windows Blue Screen and

continue operation. Operation is only possible if the cause of the blue screen doe s not

corrupt memory that WinLC RTX or the realtime operating system uses.

If WinLC RTX cannot detect the blue screen, it cannot call OB 84 or continue running.

You must reboot your computer to recover.

If you specified NVRAM storage for the retentive data, (either a SIMATIC WinAC NV128

card or integrated PC SRAM) and an undetected Windows Blue Screen occurs, WinAC

RTX will start with an unbuffered startup after the reboot. The controller panel lights up

the INTF status indicator, and the diagnostic buffer contains an "unbuffered power on"

error.

In actual practice, the occurrence of a blue screen is very rare, and the occurrence of a

blue screen that WinLC RTX cannot de tect is rarer still.

Configuring Automatic Reboot for Windows

To configure automatic reboot for Windows, follow these steps:

1. Open the Windows Control Panel and d ouble-click System.

2. From the Advanced tab of the System Properties dialog, click the Settings button for Startup and

Recovery.

3. Select the "automatically restart" checkbox.

4. Click OK on the Startup and Recovery dialog and the Systems Properties Dialog.

The next time the computer restarts, the Windows operating system will restart.

Controller Operations

Windows Automation Center RTX incl. SP2 65

A5E00992447-01

Storing Retentive Data

What Information about the Controller Does WinLC RTX Store?

WinLC RTX stores the following operational information about the controller:

• Load memory: contains the system data (configuration of the controller and STEP 7 user program)

and the initial values of the data blocks of the STEP 7 user program.

• State of the controller: includes the last transition of the operating mode (STOP, RUN, or

STARTUP) for the controller and the setting for the mo de selector switch (STOP or RUN).

• Power-down state of the controller: as saved during the shutdown process, includes the contents of

the diagnostic buffer, the current values for the retentive memory areas of the controller (such as

timers, counters and bit memory), and the current values for the data blocks (Work memory).

WinLC RTX saves this information durin g operation and uses this information when starting up the

controller.

Load Memory

When you download the STEP 7 user program, Win LC RTX saves the data blocks and system data in the

Load memory area. These data blocks include the initial values for the process variables used by the

STEP 7 user program.

SFC 82 (CREA_DBL) allows you to create new d ata blocks in Load memory during the execution of the

STEP 7 user program. You can use SFC 84 (WRIT_DBL) to modify these data blocks. SFC 82 creates and

stores the new data blocks in the Load memory at the time that SFC 82 run s.

Note: Data blocks (DBs) created by SFC 22 (CREAT_ DB) an d SFC 85 (CREA_DB) are not saved

in the Load memory. These DBs are stored only in the Work memory.

State of the Controller

WinLC RTX stores the current operational status of the controller and the status of the following events:

• Whenever the controller changes o perating mode (RUN to STOP, STOP to STARTUP, or

STARTUP to RUN), WinLC RTX stores t he state of the controller in a file system to show the latest

transition.

• Whenever the mode selector switch on the controller panel changes (STOP o r RUN), WinL C RTX

stores the state of the mode selector switch in a file system to show the latest action.

Controller Operations

66 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Power-Down State

The power-down state includes the following information:

• Current operating state of the controller

• Diagnostic buffer

• Retentive data

When you configure WinLC RTX in ST EP 7, you specify the ranges of retentive data for the timers

(T memory), counters (C memory), bit memory (M memory), and retentive data blocks (DBs). When you

perform a normal shutdown of WinLC RTX, the controller saves this retentive data and the diagno stic buffer

in the power-down state. A normal shutdown of the Windows o perating system, whether by user action or

UPS signal, also causes WinLC RTX to save the power-do wn state.

After WinLC RTX starts up the next time, it loads the power-down state. See the topic "Loading Memory

Areas on Startup" for a description of how WinLC RTX loads memory areas at startup.

Note: If you are not using non-volatile RAM (NVRAM) for WinAC Data Storage, WinLC RTX can

not store the power-down state (which inclu des the diagnostic buffer) when WinLC RTX terminates

abnormally. An abnormal termination can occur when the computer loses power e i ther by turning

off the power or by power failure, or whe n WinLC RTX is not able to write to the file system, such

as following a Windows crash ("Blue Screen"). If, however, you are using either the internal SRAM

of a SIMATIC Microbox PC 420 or SIMATIC Panel PC 477, or a SIMATIC WinAC NV128 card for

WinAC data storage, WinLC RTX can st ore the retentive data when an abnormal termination

occurs.

When Does WinLC RTX Save the Retentive Data?

The following table shows the actions that cause WinLC RTX to save the retentive data.

Retentive Data Action That Causes WinLC RTX to Save This

Data

Load memory (data blocks and initial values

of the STEP 7 user program, and system

data)

Downloading the STEP 7 user pro gram from

STEP 7

Calling SFC 82, SFC 83, or SFC 84.

State of the controller Changing the operating mo de (RUN to STOP, or

STOP to RUN), either from STEP 7 or from the

controller panel

Normal shutdown of WinLC RTX

Abnormal termination with WinAC Data Storage in

NVRAM

Power-down state:

• retentive T, C, M, and DB memory

areas

• diagnostic buffer

Normal shutdown of WinLC RTX or

Abnormal termination with WinAC Data Storage in

NVRAM

See the topic "Retentive Data Storage following Power Loss or Blue Screen" for a descri ption of multiple

factors and conditions that affect retenti v e data storage.

Controller Operations

Windows Automation Center RTX incl. SP2 67

A5E00992447-01

Available Options for WinAC Data Storage

The controller can store the WinAC RTX retentive data in a file system on your computer as well as on non-

volatile RAM (NVRAM):

• Storing retentive data in a file system: WinAC RTX stores the retentive data at shutdown. This

shutdown can be caused by a shutdown command from the controller pan el or by a Windows

shutdown. In order to save retentive data in a power loss situation, protect your system with an

Uninterruptable Power Supply (UPS).

• Storing retentive data in NVRAM: Some SIMATIC PCs contain NVRAM that you can use for

retentive data storage. With the use of NVRAM, the retentive dat a can be saved even in the event

of a Windows Blue Screen event in most cases.

NVRAM Possibilities

The following types of NVRAM are available:

• 25 KByte integrated static RAM (SRAM)

• 128 KByte NVRAM of an optional plug-in SIMATIC WinAC NV128 card

Note: To use this SIMATIC WinA C NV128 card, plug the card into any available PCI slot when the

computer is shut down. When you power on the computer, the Windows Plug -and-Play manager

detects it and allocates memory for it. Whether you install WinAC RTX before or after you install the

SIMATIC WinAC NV128 card, WinAC RTX will automatically detect the card and make it available

for WinAC data storage.

• 128 KByte integrated NVRAM

Note: WinLC RTX su pports a maximum of 128 KByte NVRAM, whether on a SIMA TIC WinAC NV128 card

or integrated in the PC. You cannot use multiple SIMATIC WinAC NV128 ca rds with WinLC RTX, nor can

you use a SIMATIC WinAC NV128 card in conjunction with integrated NVRAM.

Controller Operations

68 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

The following table summarize s the avail able types of retentive storage solutions:

PC System Storage Size UPS

required Remark

Any PC File storage Limited only by

computer's disk

space

Yes Retentive data cannot be

saved to file storage in the

event of a blue screen.

Microbox PC 420

Panel PC 477 Integrated

SRAM 25 KB No Maximum 6W load over

USB and PC104 devices

Box PC 627 24V

Panel PC 677 24V SIMATIC

WinAC

NV128 card

128 KB No DC Power supply only

Box PC 627 230V

Panel PC 677 230V

Rack PC 847

Panel PC 877

PC IL43

Other SIMATIC PC

SIMATIC

WinAC

NV128 card

128 KB Yes

Microbox PC 427B

Panel PC 477B

Box PC 627B (with

PROFIBUS option)

Panel PC 677B

Integrated

NVRAM 128 KB No

To configure the storage of WinAC RTX retentive data, use the WinAC Data Storage tool.

Effect of Power Supply Load on Microbox PC 420

The ability of the Microbox PC 420 to save retentive data to the 25 KByte of internal SRAM is dependent on

the power supply load from other devices. The Mi crobox PC 420 cannot save the retentive data to the

internal SRAM if the power supply load exceeds the 6 Watt maximum. The power supply load is equal to

the sum of the USB devices and PC 104/Plus cards.

Effect of Power Loss

Notice

Power loss without a shutdown of the operating syste m can cause file systems

of Windows XP Professio nal or Windows 2000 Professional to be corrupted. For this

reason, use a UPS system to protect file systems with these operating systems.

In addition, some SIMATIC PCs can detect a power loss and sen d a NAU signal to

WinLC RTX. WinLC RTX can then initiate a fast shutdown and save retentive data to

NVRAM if so configured. See the topic "What' s New?" for a list of the SIMATIC PCs that

support the NAU signal, and a descri ption of how WinLC RTX responds to the NAU

signal.

Systems with Windows XP embedded that use a compact flash file system that is

protected with the Enhanced Write filter are stable against an unexpected loss of power.

See the topic "Retentive Data Storage following Power Loss or Blue Screen" for a descri ption of multiple

factors and conditions that affect retenti v e data storage.

Controller Operations

Windows Automation Center RTX incl. SP2 69

A5E00992447-01

Configuring WinAC Data Storage

With the WinAC Data Storage tool, you configure where WinLC RTX stores retentive data and the STEP 7

user program and configuration.

Notice

If you change the program and configurat ion path, WinLC RTX can no longer access the

STEP 7 user program and config uration data stored at the original location. If you change

the retentive data storage settings, WinLC RTX can no longer access the existing

retentive data from the original location.

For this reason, archive your STEP 7 user program and data prior to changing any

WinAC data storage parameters. You can restore the archive file after you restart the

controller with the new WinAC data storage parameters. Alternatively, you can upload the

STEP 7 user program and configuration to STEP 7 prior to making cha nges, and

download the program to the controller after making cha nges.

If your computer is a Microbox 427B or a Panel PC 477B, you can also use the WinAC data storage tool to

enable WinAC RTX to control the LEDs on those computers. When you specify the use of the LEDs,

WinLC RTX displays the RUN/STOP status of the controller as well as any potential fault condition by

means of the LEDs. The What's New topi c describes the LED status indications.

To use the WinAC Storage Tool, follow these steps:

1. Archive your STEP 7 user program and configuration. Alternatively, you can upload the STEP 7

user program and configuration to STEP 7 using the PLC > Upload Station to PG menu

command in STEP 7.

2. Shut down the controller.

3. Select the Start > SIMATIC > PC based Control > WinAC Data Storage menu command. The

WinAC Data Storage dialog appears:

4. In the Program and Configuration Path field, accept the default pat h or use the button to

browse to a folder to use for the storage of the STEP 7 user program an d configuration.

Controller Operations

70 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

5. If your computer has NVRAM of any type, you can select either NVRAM Storage or File Storage for

the Retentive Data specification. The dia log sh ows how much NVRAM storage is available.

Otherwise, File Storage is your only choice. You can use the button to browse to a folder for

the storage of the retentive data, or accept the default path.

See the topic "Available Options for WinA C Data Storage" for a summary of the NVRAM

possiblities and the comput ers that have NVRAM.

6. If your computer is a Microbox PC 427B or a Panel PC 477B, select the Use LE Ds checkbox if you

want WinLC RTX to show the RUN/ST OP status and fault condition on the LEDs.

7. Click OK.

8. Restart the controller to make your changes take effect.

9. Restore the STEP 7 user prog ram and configuration that you archived in Step 1. Alternatively, you

can download the program and configuration from STEP 7 to the controller.

Notice

For SIMATIC PCs with compact flash cards, you typica lly enable the Enhanced Write

Filter (EWF) for the C:\ drive and leave the Enhanced Write filter disabled for the D:\

drive. With this usage, if you specify a file storage location on the D:\ drive for the STEP 7

user program and configuration and for t he retentive data, WinAC RTX always recovers

these files after a reboot. For this reason , specify a D:\ drive location for STEP 7 files and

retentive data.

If however, you choose to store either program data or rete ntive data on the C:\ drive,

and you have enabled the Enhanced Write Filter for the C:\ drive, you must manage the

Enhanced Write Filter to commit data to the flash card. If you have files on the C:\ drive

and you have not committed these files to the flash card, WinAC RTX cannot recover

these files following a reboot. You must commit data on the C:\ drive to the flash card for

it to be available after a reboot.

If you choose "File Storage" for retentive data, you must use an Uninterruptible Power

Supply (UPS) to maintain data following a power loss. Without a UPS, retentive data in

"File Storage" is lost after a power failure. If you choose "NVRAM Storage", Siemens

recommends the use of a UPS, but a UPS is not a require ment.

Controller Operations

Windows Automation Center RTX incl. SP2 71

A5E00992447-01

File Storage Restrictions

Do not use a compressed f ile system for the Program and Configuration path or for the Retentive Data File

Storage path. To determine whether a file system is compressed, examine the disk propertie s for the drive

that you specified. Ensure that the “Compre ss drive to save disk space” checkbox is not sele cted.

NVRAM Memory Allocation

The following types of information share the available NVRAM:

Item Memory Consumption Default

System Startup Information 1 KByte 1 KByte

Diagnostic Buffer Number of entries * 20 bytes 2400 bytes 120 entries

Flag (M) Memory Number of flag memory bytes 16 bytes MB0 – MB15

S7-Timers Number of timers * 2 bytes 0 bytes No timers are retentive by

default

S7-Counters Number of counters * 2 bytes 16 bytes C0 - C7

Retentive DBs configured

with STEP 7 or created by

SFC 85 with ATTRIB=0x00

Number of KBytes in retentive

DBs User program configuration

Overhead for DBs created

by SFC 85 Number of DBs * 45 bytes 0 bytes

Notice

If you have stored retentive data on a SIMATIC WinAC NV12 8 card and you remove the

card when your computer is off, the next time you start WinAC RTX, it will start with an

unbuffered startup. The controlle r panel lights up the INTF status indicator, and the

diagnostic buffer contains an "unbuffered power on" error.

To recover, you must either shut d own WinAC RTX and your computer and reinstall the

SIMATIC WinAC NV128 card, or you mu st switch to File Storage for your retentive data.

Controller Operations

72 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Retentive Data Indication for Data Blocks

By default, STEP 7 configures all data blocks as retentive. As shown below, the Properties dialog for a

retentive data block displays all three of the following checkboxes as not selected (not checked):

• DB is write-protected in the PLC

• Non-retain

• Unlinked

If you select (check) any of these three checkboxes, the data block is non-retentive and not included by the

NVRAM rmemory allocation.

Data Blocks Created by SFC 85

A data block created by SFC 85 is retentive if the ATTRIB parameter is 0x00. When considering NVRAM

usage, these data blocks require memory for the overhead and for the retentive data. For data blocks

created by SFC 85 with the ATTRIB parameter not equal to 0x00, the data block requires memory only for

the overhead.

Exceeding NVRAM Storage

Notice

If you switch from File Storage to NVRAM Storage for your retentive data, and the

retentive data in your STEP 7 user program requires more me mory than the NVRAM

supports, no retentive data can be reload ed after a startup. A message in the Diagnostic

Buffer indicates that an unbuffered startup occu rred.

You must either reduce the size of the retentive data in your STEP 7 user program, or

use File Storage instead of NVRAM Storage for the retentive data. The STEP 7 Hardware

Configuration tool displays the curre nt memory usage in the Module Information dialog.

Controller Operations

Windows Automation Center RTX incl. SP2 73

A5E00992447-01

Managing the Enhanced Write Filter

The following Windows XP embedded systems u se CompactFlash cards:

• Microbox PC 420

• Panel PC 477

• Microbox PC 427B

• Panel PC 477B

• Box PC 627

The Enhanced Write Filter (EWF) is a Windows XP embedded utility for protecting a Com pa ctFlash card.

CompactFlash cards allow a limited number of write accesses. When the Enhanced Write Filt er is enabled,

Windows XP embedded writes no data to the CompactFlash card. Instead, the file writes are kept in virtual

memory. No difference is apparent to you when you view file contents. File information appears the same

whether it actually resides on the CompactFlash card or in virtual memory. The difference in file storage is

evident when you reboot the computer o r it lose s power. All data in virtual memory is lost, and the

computer restarts with the file contents of the CompactFlash card.

You can manage the EWF to maintain data that must persist after a reboot. If you disable the EWF, all file

writes go to the CompactFlash card. This does result in the persistence of all data after a power loss;

however, it causes the most stress over time to the CompactFlash card.

Notice

The Enhanced Write Filter default setting of the D:\ and C:\ drive on the Microbox PCs

and Panel PCs is "Disabled". To protect the Compa ctFla st card from early failure due to

continuous writes, enable the EWF for t he C:\ drive after you have finished the

development of applications on the C:\ drive.

You can also commit all data that is stored in virtual memory to the CompactFlash card at any point in time.

The "commitanddisable" E WF comma nd disables the EWF and then writes all data that has accumulated in

virtual memory to the CompactFlash card. Typically, this command is followed by an enable command to

once again protect the CompactFlash card.

To use the enhanced write filter manager, follow these steps:

1. Open a command prompt window.

2. Enter "ewfmgr" followed by a drive designation and a command as illustrated.

3. Reboot the computer to make the command take effect.

Controller Operations

74 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

The ewfmgr commands tha t are applicable appear below, as applied to the C:\ drive:

Enable the EWF:

File

Save =>=>=> Virtual

Memory Command:

ewfmgr c: -enable

Commit Data to Com pact Flash:

Virtual

Memory =>=>=> Compact

Flash Command:

ewfmgr c: -commit

Commit Data to Compact Flash and Disable the EWF:

Virtual

Memory =>=>=> Compact

Flash Command:

ewfmgr c: -commitanddisable

File

Save =>=>=> Compact

Flash

Note that the initial state of the Enhanced Write Filter is "disabled". Following a "commitanddisable"

command, use the "enable" comman d to protect the CompactFlash card, and to write data to virtual

memory.

Controller Operations

Windows Automation Center RTX incl. SP2 75

A5E00992447-01

How WinLC RTX Loads Memory Areas on Startup

Upon startup, WinLC RTX searches for the stored power-down state to determine whether the controller

had been shut down correctly and performs the following tasks:

• Loads the downloaded blo cks of the STEP 7 user p ro gram from the Load memory.

• Restores the work memory depending on whether a valid power-down state exists or not:

o If WinLC RTX does find a valid power-down state, it updates the work memory from the

power-down state and loads the retentive data with the values stored at the time that the

controller was shut down. With the use of NVRAM for WinAC data storage, the power-

down state is often available even after a Windows Blue Screen event, as well as after a

normal shutdown of the controlle r.

o If WinLC RTX does not find a valid power-down state (showing that the controller had not

been shut down correctly), it restores the work memory to its initial state from Load

memory (as downloaded from STEP 7). The po wer-down state can be missing or

unreadable if a Windows Blue Screen ev ent oc curred and WinAC Data storage is not in

NVRAM.

• Restores the state of the controller, based on the saved operating mode and the Autostart

configuration, and resets the mode sele ctor switch setting on the controller panel.

If WinLC RTX cannot read any element of the Load memory, state of the controller, or the power-down

state, WinLC RTX starts an unconfigured (empty) controller.

Note: WinLC RTX ca nnot read the stored load memory or power-down state saved from a previous

release of WinAC RTX or WinAC Basi s. You can restore a STEP 7 user program and co nfiguration

that was archived from a previous release, but WinLC RTX cannot access retentive data from a

previous release.

Loading Memory from a Valid Power-down State

If the power-down status was successfully saved when the controller shut down, WinLC RTX loads the

operational data for the controller:

• WinLC RTX loads data sto red in the po wer-down state during startup. This includes the retentive

S7 memory areas, the current values of the data blocks (work memory), and the contents of the

diagnostic buffer.

Note: If you configured the controller for a cold restart (OB 102), WinLC RTX resets the

process variables and S7 memory a rea s to the initial values from the Load memory.

• Based on the Autostart settings, WinLC RTX sets the state of the controller to either STOP mode

or RUN mode.

In case of a Windows Blue Screen where the WinAC data storage is not in NVRAM, WinLC RTX

sets the state of the controller to the state before the Windows Blue Screen occurred. Although the

controller performed a "normal" RUN-to-STOP transition, WinLC RTX is unable to save the state of

the controller during a Win dows Blue Screen, unless you configured NVRAM for WinAC data

storage.

Note: WinLC RTX generates a startup event that identifies the type of startup: buffered or

unbuffered. (An unbuffered startup is like reloading the control program from an EPROM file.)

You can program OB 100 to read this st art event. For an unbuffered startup, the variable

OB100_STOP at address LW6 is set to W#16#4309.

• WinLC RTX sets the mode selector switch to the setting when WinLC RTX last saved the stat e of

the controller.

After resetting these values and comple ting startup, WinLC RTX deletes the power-down state from the

retentive memory file.

Controller Operations

76 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Loading Memory when no Valid Power-down State Exists

If the controller was not sh ut down properly, and WinAC data storage wa s not in NVRAM, WinLC RTX did

not create the power-down state.

Note: If the power-down state was not created, the diagnostic buffer is not saved. When you restart

the controller, the diagnosti c buffer i s empty.

If the power-down state was not saved when shutting down the controller, Win LC RTX performs the

following tasks when restarting the controller:

• Reads the Load memory and reloads the system configuration, the process variables and S7

memory areas to the initial values configured in STEP 7.

• Reads the state of the controller a nd performs an unbuffered startup. (An unbuffered startup is like

loading the control program from an EPROM file. WinLC RTX generates a startup event that you

can program the OB 100 to read. ) Based on the Autostart settings, WinLC RTX sets the controller

to either STOP mode or RUN mode.

• WinLC RTX sets the mode selector switch to the setting when WinLC RTX last saved the stat e of

the controller.

Encountering Problems when Starting the Controller

If WinLC RTX cannot read (or encounters an error in reading) any element of the retentive memory area

(Load memory, state of the controller, or power-down state), WinLC RTX starts with an unconfigured

(empty) controller. In this case, the controller is set to STOP mode with the mode selector switch set to

STOP. WinLC RTX still contains the STEP 7 user program and configuration, but no retentive data.

Possible causes for this problem include a hardware error in your computer, or a partial block in the Load

memory area caused by an error that occurred whe n WinLC RTX was writing a block to the Load memory.

To recover from this condition, you must reload your control program and system data from STEP 7.

Note: The mode selector switch of the controller is set to STOP mode. You can download the

control program and system data from a remote computer, but you cannot use the remote

computer to set the controller to RUN mode. You must go to the local computer for WinLC RTX

and set the mode selector switch to RUN to place the controller in RUN mode.

Starting the Controller After a Windows Blue Screen wh en WinAC Data Storage is in

NVRAM

In most cases, WinLC RTX is able to save the power-down state when the WinAC data storage is in

NVRAM. When WinLC RTX starts up, it perfo rms the actions described in "Loading Memory from a Valid

Power-down State."

Starting the Controller After a Windows Blue Screen wh en WinAC Data Storage is not in

NVRAM

If the controller was in RUN mode at the time of the shutdown and is configure d for Autostart, WinLC RTX

restarts in RUN mode. If OB 84 (CPU Hardwa re Fault) had responded to a Windows Blue Screen and had

placed the controller in STOP mode before shutting down, WinLC RTX still starts in RUN mode because

without NVRAM data storage, WinLC RTX could not save the state setting for the controller during the

shutdown caused by the Windows crash.

If you do not have NVRAM data storage, and you do not want the controller to re start in RUN mode after a

Windows Blue Screen, you must include code in the startup OB (OB 100 or OB 102) to detect that WinLC

RTX terminated without saving the power-down state, and to set the controller to STOP mode when

restarted. A value of 0010 xxxx in bits 7 - 0 of the startup OB variable OB_STR_INFO indicates that the

power-down state is not available on disk.

Controller Operations

Windows Automation Center RTX incl. SP2 77

A5E00992447-01

Using SFCs to Retain Data

You can use SFC 82 (CREA_DBL), SFC 83 (READ_DBL), and SFC 84 (WRIT_ DBL) to save data at

significant events in your process. For example, you may want to store th e recipe values into Load memory

when changing a re cipe without downloading new blocks for the STEP 7 user prog ram.

SFC 82 and SFC 84 modify the data for the STEP 7 user p ro gra m that is stored in the Load memory.

Saving the blocks to Load memory (instead of keeping the values in Work memory) ensures that these

blocks are available even if WinLC RTX cannot save the power-down state when shutting do wn the

controller.

Note: You must consi der the possibility of a Windows Blue Screen when using SFC 22, SFC 23,

SFC 82, SFC 83, SFC 84, or SFC 85.

When executed from the STEP 7 user program, SFC 82 (CREA_DBL), SFC 83 (READ_DBL), and SFC 84

(WRIT_DBL) create and up date blocks that are stored as part of your STEP 7 user program in Load

memory.

SFC 82, SFC 83, and SFC 84 are asynchronous SFCs that run in the backgro und.

Note: If you call SFC 82, SFC 83, or SFC 84 from the startup OB (OB 100 or OB 102), Win LC RTX

executes these SFCs synchronously. This differs from the operation of a hardware PL C.

Like the other asynchronous SFCs, SFC 82, SFC 83, and SFC 84 are typically long-running SFCs that can

require a relatively long time to complete. (The time for the SFC call itself will be short, but the actual

operation for the SFC will be executing in the background.) In order to use asynchron ous SFCs, you must

allow sufficient sleep time to allow WinLC RTX to process the SFCs without encountering jitter.

Note: Do not use a polling loop that loo k s for the com pletion of an asynchronous SFC, especially

for SFC 82, SFC 83, or SFC 84. Because the asynchronou s SFC is being executed in the

background, having your STEP 7 user prog ram loop until the SFC finishe s will e x tend the

execution of the OB that is performing the polling loop and can cause jitter.

Caution

Whenever your STEP 7 user program calls SFC 82, SFC 83, or SFC 84, the SFC reads

or writes data to the disk. If you call these SFCs every scan (such as from OB 1) or from

a cyclical OB that is executing rapidly, the constant reading o r writing to the disk can

cause the disk to fail or can add jitter.

You should only call SFC 82, SFC 83, or SFC 84 to record a significant process event,

such as a change of recipe.

Controller Operations

78 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Using an Uninterruptible Power Supply (UPS)

You can use a UPS system to provide emergen cy power for your computer. A UPS system helps ensure

that WinLC RTX shuts down correctly and saves the p ower-down state in case of a power failure. Siemens

strongly recommends the use of a UPS for operation with Windows 200 0 Professional or Windows XP

Professional operating systems.

Refer to the manufacturer's docume ntation for your computer and your UPS system.

Microsoft Windows provides a dialog for configuring the UPS for your computer:

1. Select the Start > Settings > Control Panel menu command to display the control panel.

2. Double-click the Power Options icon to display the Po wer Options Properties dialog.

3. Click the UPS tab and configure the p arameters for your UPS system.

4. Click Apply or OK to set the UPS properties.

Notice

Power loss without a shutdown of the operating syste m can cause file systems

of Windows XP Professio nal or Windows 2000 Professional to be corrupted. For this

reason, use a UPS system to protect file systems with these operating systems.

In addition, some SIMATIC PCs can detect a power loss and sen d a NAU signal to

WinLC RTX. WinLC RTX can then initiate a fast shutdown and save retentive data to

NVRAM if so configured. See the topic "What' s New?" for a list of the SIMATIC PCs that

support the NAU signal, and a descri ption of how WinLC RTX responds to the NAU

signal.

Systems with Windows XP embedded that use a compact flash file system that is

protected with the Enhanced Write filter are stable against an unexpected loss of power.

Controller Operations

Windows Automation Center RTX incl. SP2 79

A5E00992447-01

Retentive Data Storage following Power Loss or Blue Screen

Previous topics discussed WinLC RTX response to a blue screen, retentive data, options for WinAC data

storage, configuring WinA C data storage and the possible use of an Uninterruptible Powe r Supply (UPS).

In addition, the "What's New?" topic described the NAU signal that some SIMATIC PCs can se nd to WinLC

RTX to indicate a power failure.

All of these variations in features, configuration choices, and types of Windows or power failures will

interact together. The behavior of your particular system depends on these variations in combination.

The following tables descri be WinLC RTX behavior on various SIMATIC PCs under various conditions.

NVRAM includes PCs with integrated 25 KByte SRAM, the SIMATIC WinAC NV128 card, or integrated 128

KByte NVRAM:

Retentive data storage

possible in File Storage Retentive data storage

possible in NVRAM

SIMATIC PC with NAU

(power failure) detection

UPS

in event of

power loss in event of

Blue Screen in event of

power loss in event of

Blue Screen

Box PC 627 (DC, basic

board 4 and higher)

Box PC 627B (without

integrated PROFIBUS)

Panel PC 677 (DC, basic

board 4 and higher)

Microbox 427B

Panel PC 477B

Not

required No* No Yes Yes

*The use of a UPS, though not required, would enable retentive data storage in file storage in the event of

a power loss.

Retentive data storage

possible in File Storage Retentive data storage

possible in NVRAM

SIMATIC PC

without NAU (power

failure) detection

UPS

in event of

power loss in event of

Blue Screen in event of

power loss in event of

Blue Screen

In use Yes No Yes Yes*

Box PC 627 (AC, DC up

to basic board 4)

Box PC 840

Panel PC 577

Panel PC 677 (AC, DC up

to basic board 4)

Panel PC 877

Rack PC 840

Rack PC 847B

Rack PC IL 43

Not in

use No No No Yes*

*To store retentive data in the event of Blue Screen on PCs without NAU (power failure) detection, WinAC

RTX must terminate properly by calling SFC STP (SFC 46). A power failure duri ng a Blue Screen will lead

to the loss of the retentive data.

The most reliable configuration is to use a SIMATIC PC with NA U detection and configure WinAC data

storage to be in NVRAM.

Controller Operations

80 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Setting Controller Panel Options

Customize Command (CPU Menu)

To open the Customize dialog box, sel ect the CPU > Options > Customize menu command. The tabs of

the dialog box allow you to customize the controller panel as follows:

General

Select Always On Top to display the controlle r panel on top of all other open windows.

Language

The language field display s the current display language for the cont roller panel.

The language select list displays the in stalled languages for the controller panel. Click a lan guage selection

to change the controller pa nel display language.

Note: To inst all the languages that are available for th e controller panel, run the setup progra m and

select the languages from the dialo g.

AutoStart

Select Autostart CPU to set the autostart feature. The autostart feature allows the controller to start

automatically in RUN mode under the condition s described in Selecting the Autostart Feature.

Selecting the Language

You can change the display language for the controller panel menu s and online help.

To change the display language, follo w these steps:

1. Select the CPU > Options > Cu stomize menu command to display the Customize dialog.

2. In the Customize dialog, select the Language tab.

3. Select the language for the controller p anel.

4. Click Apply to change the language.

5. Click OK to close the Customize di alog.

The controller panel automatically chang es to the selected language.

Selecting the Autostart Feature

The panel provides an Autostart feature that when enabled causes the controller to start in the same

operating mode as when previously shut down:

• If the controller was in RUN mode when shut down, the controller restarts in RUN mode.

• If the controller was in STOP mode when shut down, the controller restarts in STOP mode.

If the Autostart feature is not enabled, the controller always starts in STOP mod e.

Use the following procedure to enable the Autostart feature:

1. Select the CPU > Options > Cu stomize menu command to display the Customize dialog.

2. In the Customize dialog, select the Autostart tab.

3. Select the Autostart CPU option for the Startup Mode.

4. Click Apply to enable the Autostart feature and click OK to close the Customize dialog.

Controller Operations

Windows Automation Center RTX incl. SP2 81

A5E00992447-01

Setting the Security Options

Security Command (CPU Menu)

Select the CPU > Options > Security menu command to change security options. The controller panel

displays the Access Verification dialog. You must enter your password in this dialog in order to make a ny

changes to the security set tings for the controller.

Note: The default password is an empty field containi ng no characters. To enter the default

password, press the Enter key.

Security Level

The Security dialog allows you to set levels of password security that limit access to the controller. The

following security access options are prov ided:

• Password: When you select Password, certain controller panel operations such as changing the

operating mode and archiving and restoring a STEP 7 user progra m, require that the user enter a

password.

• Confirmation: When you select Confirmation, operating mode change s require that the user

acknowledge a confirmation dialog box.

• None: When you select None, no confirmation or p assword is required.

Password Prompt Interval

You can set the Password Prompt Interval to a time interval of your choice, from 0 to a maximum of 23

hours, 59 minutes. After you have entered your password, you are not prompted for it again until this time

interval has expired. The default setting of 0 means that you must enter a password for each protected

operation.

Shutting down and starting the controller does not affect the expiration of the Password Prompt Interval;

however, it is reset whenever you shut down the controller panel. The next time you start the controller

panel and access a p assword-protected function, you will be prompted for password entry.

Change Password

Click the Change Password button to display the Change Password dialog.

Note: If you create a password, but set the security level to None (disabling the password), you still

need to enter the configured password in the Access Verification dialog before you can access the

Security dialog box again.

Warning

Running the controller without confirmation or password protection increases the risk

that an operator may change the controller mode inadvertently, which could cause the

process or equipment to op erate unpredictably, resulting in potential damage to

equipment and/or death or serious injury to personnel.

Exercise caution to ensure that you do not inadvertently change the operating mode,

or permit unauthorized persons to access the machine or process. Always install a

physical emergency stop circuit for your machine or process.

Controller Operations

82 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Changing the Password

The Change Password di alog allows you to change the current password.

Note: The default password is an empty field containi ng no characters. To enter the default

password, press the Enter key.

Use the following procedu re to change the password:

1. In the Old Password field, enter the old password.

2. In the New Password field, enter the new passwo rd (maximum length 12 characters).

3. In the Confirm New Password field, enter the new password agai n.

4. Click OK to apply all the changes made in this dialog.

To subsequently access the security options, you must enter the password at the Access Verification

dialog.

Startup Options for the Controller

Starting the Controller at PC Boot

By default, you must start the controller manually after the computer reb oots. You can, however, register

the controller to start during the Windows boot sequence prior to user login.

Note: To configure the con t roller for starting in the same operating mode (STOP or RUN) as when

previously shut down, use the Autostart feature.

Registering the Controller for Start at PC Boot

To register the controller to start during the Windo ws boot sequence, follow these steps:

1. Shut down the controller.

2. Select the CPU > Register Controller for Start at PC Boot menu command.

Unregistering the Controller for Start at PC Boot

To unregister the controller for starting automatically, follow these steps:

1. Shut down the controller.

2. Select the CPU > Unregister Controller for Start at PC Boot menu command.

WinLC will now not start du ring the boot sequence. To start WinLC, you must manually start th e controller.

Controller Operations

Windows Automation Center RTX incl. SP2 83

A5E00992447-01

Setting the Restart Method

The restart method determines which startup OB the controller executes whenever a ch ange from STOP

mode to RUN mode occurs. The startup OB allows you to initialize your STEP 7 user program and

variables. WinLC RTX supports two restart method s:

• Warm restart: The controller executes OB 100 before starting the free cycle (O B 1). A warm

restart resets the peripheral inputs (PI) and changes the peripheral outputs (PQ) to a pre-defined

safe state (default is 0). The warm restart also saves the current value for the retentive memory

areas for the memory bits (M), timers (T), counters (C), and data blocks (DBs).

• Cold restart: The controller executes OB 102 before starting the free cycle (OB 1). Like a warm

restart, a cold restart resets the peripheral inputs (PI) and changes the peripheral outputs (PQ) to a

pre-defined safe state (default is 0). However, a cold restart does not save the retentive memory

(M, T, C, or DB), but sets these areas to their default (initial) values.

You use STEP 7 to configure the default restart metho d for the controlle r. The default restart method is

stored in the configuration (system data ) for the controller that you download with your STEP 7 user

program. WinLC RTX use s this restart method when WinLC RTX is co nfigured for Autostart and returns to

RUN mode following a power cycle.

Whenever you click (using the left mouse button) the RUN mod e selecto r switch on the panel to change

from STOP mode to RUN mode, WinLC RTX performs a wa rm restart, executing OB 100.

To select a specific restart method, cho ose one of the following options to change the controll er from STOP

mode to RUN mode:

• Select the CPU > RUN menu command to change the controller from STOP to RUN mode.

• Right-click (using the ri ght mouse button) the RUN mode select or switch position.

Both of these actions display the Restar t Method dialog that allows you to select either a warm or cold

restart.

Note: If you have configured the confirmation secu rity option, you must acknowledge a

confirmation dialog before the cont roller panel displays the Restart Method dial og.

If you have configured the password security option and the pa ssword prompt interval is either 0 or

has expired, the controller panel displays the Access Verification dialog for you to enter the

password. After verifying successful password entry, the controller panel displays the Restart

Method dialog.

After executing OB 100 (warm restart) or OB 102 (cold restart) according to your selection, the controller

executes the free cycle (OB 1).

Windows Automation Center RTX incl. SP2 85

A5E00992447-01

STEP 7 Operations and Components

Using STEP 7 with the Controller

STEP 7 provides programming and configuration tools for working with WinLC RTX. You perform the

following tasks with STEP 7:

• Define the controller and DP I/O configuration throu gh the STEP 7 Hardware Configuratio n tool

• Develop a STEP 7 user program using any of the STEP 7 control programming languages

• Configure operational parameters and I/O addresses for the controller

• Download your configuration and STEP 7 user program to the con t roller

Refer to your STEP 7 documentation for additional informatio n.

Configuring the Operational Parameters for the Controller

STEP 7 provides a Hardware Configuration application for configuring the operational param eters for the

controller. This configuration is then stored in various SDBs in the System Data container.

After you download the System Data, the controller uses the configured parameters for the following

events:

• Whenever you start the controller

• On the transition to RUN mode (if you modified the hardware configuration online while the

controller was in STOP mode)

To configure the operational parameters from the STEP 7 Hardware Configuration application, right-click

the controller entry in the station window and select Object Properties. From the Properties di alog, you

configure the operational parameters.

Accessing Operational Parameters

To configure any of these operational parameters in STEP 7, open the SIMATIC Manager and follow these

steps:

1. In the SIMATIC Manager, select the PC station.

2. Click the Configuration icon.

3. Right-click the controller in the stat ion window and select Obje ct Properties.

4. Click the tab with the name of the parameter that you want to conf igure (such as Cyclic Interrupt)

and enter the appropriate values in the d ialog.

5. Click OK to confirm your configuration.

Refer to your STEP 7 documentation for specific information about configuring the controller properties and

the operational parameters.

STEP 7 Operations and Components

86 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Logic Blocks Supported by WinLC RTX

Like the other S7 controllers, WinLC RTX provide s several types of logic blo cks for processing the user

program: organization blocks (OBs), system functions (SFCs), and system function blocks (SFBs). These

blocks are an integral part of WinLC RT X.

Organization Block (OB) System Function (SFC) System Function Block

(SFB)

OB 1

OB 10

OB 20

OB 30 to OB 38

OB 40

OB 52 to OB 57

OB 61 and OB 62

OB 80, OB 82 to OB 86, and

OB 88

OB 100 and OB 102

OB 121 and OB 122

SFC 0 to SFC 6

SFC 9 to SFC 15

SFC 17 to SFC 24

SFC 26 to SFC 34

SFC 36 to SFC 44

SFC 46 and SFC 47

SFC 49 to SFC 52

SFC 54 to SFC 59

SFC 62 and SFC 64

SFC 78 to SFC 80

SFC 82 to SFC 84

SFC 85 and SFC 87

SFC 126 and SFC 127

SFB 0 to SFB 5

SFB 8 and SFB 9

SFB 12 to SFB 15

SFB 22 and SFB 23

SFB 31 to SFB 36

SFB 52 to SFB 54

SFB 65001 and SFB 65002

Additional S7 Blocks

In addition to these system blocks, you can use these other S7 blocks to create the STEP 7 user pro gram:

• Function (FC): WinLC RTX supports up to 65,536 FCs (FC 0 to FC 65535). Each FC can contain

up to 65,570 bytes.

• Function block (FB): WinLC RTX supports up to 65,536 FBs (FB 0 to FB 65535). Each FB can

contain up to 65,570 bytes.

• Data block (DB): WinLC RTX support s up to 65,535 DBs (DB 1 to DB 65535). (DB 0 is reserved.)

Each DB can contain up to 65,534 bytes.

The number and size of F Cs, FBs, and DBs are also limited by the amount of available system memory.

For more information about the instruction list supported by WinLC RTX, see the following topics:

• Technical data

• Organization blocks (OBs)

• System functions (SFCs)

• System function blocks (SFBs)

STEP 7 Operations and Components

Windows Automation Center RTX incl. SP2 87

A5E00992447-01

S7 Communication Functions

Like other S7 controllers, WinLC RTX p rovide s S7 communication between controllers on the netwo rk. The

controllers can be either hardware or software logic controllers.

SFB or SFC Name Description

SFB 8

SFB 9 USEND

URCV Exchange data using a se nd and a receive SFB

SFB 12

SFB 13 BSEND

BRCV Exchange blocks of data of variable leng t h between a send

SFB and a receive SFB

SFB 14

SFB 15 GET

PUT Read data from a remote device

Write data to a remote device

SFB 22

SFB 23 STATUS

USTATUS Specific query of the status of a remote device

Receive status messages from a remote device s

SFC 62 CONTROL Query the status of a connection

SFC 87 C_DIAG Determines the current status of all S7 connections

Refer to your STEP 7 documentation for more informa tion about S7 communications.

STEP 7 Operations and Components

88 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

PROFIBUS DPV1

DPV1 extensions to PROFIBUS-DP allow the enhanced communication required by complex slave

devices. This enhanced communi cation includes acyclic data exchange, alarm and status messagi ng, and

the transmission of complex data types. WinLC RTX p rovides support for the following DPV1 functionality:

• DP-Norm, DP-S7, DPV1, and DPV1 S7-compliant slaves

• Alarm and status OBs for proce ssing DPV1-defined events, including:

o OB 40 (process alarm)

o OB 55 (status alarm)

o OB 56 (update alarm)

o OB 57 (manufacturer-sp ecified alarm)

o OB 82 (diagnostic alarm )

o OB 83 (module pull/plug alarm)

o Data set read and write function blocks:

o SFB 52 (RDREC), Read Data Set

o SFB 53 (WRREC), Write Data Set

o Execution of SFB 54 (RALRM), read alarm data, in the context of the triggering alarm

o Station and interface address

o Buffering of alarms received in DP mode CLEAR

For WinLC RTX to support DPV1, configure the submodule DP interface to be a DP Maste r. To sele ct DP

Master, follow these steps from the SIMATIC Manager:

1. Open the Hardware Configuration for your PC Station .

2. Double-click your su bmodule DP interface in the corresponding submodule slot of your

WinLC RTX.

3. Select the Operating Mode tab of the CP card Prop erties dialog.

4. Select DP Master and set the DP mode to DPV1.

Refer to your STEP 7 documentation for specific information about DPV1 functionality.

STEP 7 Operations and Components

Windows Automation Center RTX incl. SP2 89

A5E00992447-01

Organization Blocks (OBs)

Organization blocks (OBs) are the interface between the operating system of the controller and the STEP 7

user program. You use OBs to execute specific components of your STEP 7 user program for the following

events:

• When the controller start s and restarts

• Cyclically or at a specific time interval

• At certain times or on certa in days

• After running for a specified period of time

• When errors occur

• When a hardware interrupt occurs

The program logic in an OB can contain up to 65,570 bytes.

OBs are processed according to the priority assigned to them.

The following table lists the OBs that Wi nLC RTX supports:

OB Description Priority Class

OB 1 Free scan cycle 1 (lowest)

OB 10 Time-of-day interrupt 0, 2 to 24

OB 20 Time-delay interrupt 0, 2 to 24

OB 30 to OB 38 Cyclic interrupt 0, 2 to 24

OB 40 Hardware (process alarm) interrupts 0, 2 to 24

OB 52 to OB 54 ODK interrupt 15

OB 55 Status interrupt 0, 2 to 24

OB 56 Update interrupt 0, 2 to 24

OB 57 Manufacturer-specific interrupt 0, 2 to 24

OB 61 and OB 62 Synchronous cycle interrupts 0, 2 to 26

Default: 25

OB 80 Time error 26

OB 82 Diagnostic interrupt 24 to 26 (or 28)**

OB 83 Insert/remove module interrupt 24 to 26 (or 28)**

OB 84 CPU Hardware fault 24 to 26 (or 28)**

STEP 7 Operations and Components

90 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

OB Description Priority Class

OB 85 Priority class error 24 to 26 (or 28)**

OB 86 Rack (DP slav e) failure 24 to 26 (or 28)**

OB 88 Processing Interrupt (stop avoidance) 28

OB 100 Warm restart 27

OB 102 Cold restart 27

OB 121 Programming error

OB 122 I/O access error

Priority class of the OB where

the error occurred

** Priority class 28 during STARTUP, u ser-config urable priority class (from 24 to 26) in RUN mode.

OBs for the Free Scan Cycle, Cold Restart, and Warm Restart

The following table shows OBs for the free scan cycle and cold and warm restarts. WinLC RTX provides

OB 1 (free scan cycle) for contin uously executing the STEP 7 user program. On the transition from STOP

mode to RUN mode, WinLC RTX executes OB 100 (warm restart) or OB 102 (cold restart), based either on

the hardware configuratio n for WinLC RTX or which restart option was selected from a dialog displayed by

the WinLC RTX panel. After OB 100 (or OB 102) has been successfully executed, WinLC RTX executes

OB 1.

Organization Block (OB) Start Ev ent (in Hex) Priority Class

Main program cycle OB 1 1101, 1103, 1104 1

Warm restart OB 100 1381, 1382 27

Cold restart OB 102 1385, 1386 27

STEP 7 Operations and Components

Windows Automation Center RTX incl. SP2 91

A5E00992447-01

Interrupt OBs

WinLC RTX provides a variety of OBs that interrupt the execution of OB 1. The following table lists the

different interrupt OBs that are supported by WinLC RTX. These interrupts occur according to the type and

configuration of the OB.

The priority class determines whet her the controller suspends the execution of the STEP 7 user program

(or other OB) and executes the interrupting OB. You can change the priority class for the interrupt OBs.

Interrupts Start Event (in Hex) Default Priority Class

Time-of-day interrupt OB 10 1111 2

Time-delay interrupt

Range: 1 ms to 60000 ms OB 20 1121 3

Cyclic interrupt

Range: 1 ms to 60000 ms

Recommended: > 10 ms

OB 30

OB 31

OB 32

OB 33

OB 34

OB 35

OB 36

OB 37

OB 38

1131

1132

1133

1134

1135

1136

1137

1138

1139

Hardware interrupt OB 40 1141 16

Status interrupt OB 55 1155 2

Update interrupt OB 56 1156 2

Manufacturer-specific interrupt OB 57 1157 2

If WinLC RTX has been configured to execute a particular interrupt OB, but that OB has not been

downloaded, WinLC RTX reacts in the following manner:

• If OB 10, OB 20, OB 40, OB 55, OB 56, or OB 57 is missing and OB 85 has not been downloaded,

WinLC RTX changes opera t ing mode (from RUN to STOP).

• WinLC RTX remains in RUN mode if a cyclic interrupt OB (OB 32 to OB 36) is missing. If these

OBs cannot be executed at the specified time and OB 80 has not been downloaded, WinLC RTX

changes from RUN mode t o STOP mod e.

STEP 7 Operations and Components

92 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Considerations for Cyclic Interrupt OBs

Based on the time interval that you configure in the operational parameters for the cyclic interrupt,

WinLC RTX starts the execution of the cyclic interrupt OB at the appropriate time. The optimum time

interval for your application depends on the processing speed of your computer and the execution time of

the cyclic OB. Jitter can cause an occasional overrun in the start event for a cycli c OB, whi ch might cause

WinLC RTX to go to STOP mode. Other factors that affect the execution of the OB include the followin g

situations:

• The program in the OB takes longer to execute than the interval allows. If the execution of the

program consistently overruns the start event of the cyclic OB, WinLC RTX can go to STOP mode

(unless OB 80 is loaded).

• Programs in other priority classes frequently interrupt or take longer to execute, which prevents the

controller from executing the cycli c OB at the sch eduled time. If this occasionally causes a n

overrun, WinLC RTX starts the cyclic OB as soon as the first OB finishes.

• STEP 7 performs some task or function t hat causes the controller not to execute the cyclic OB at

the scheduled time.

The sleep time of the WinLC RTX scan cycle d oe s not affect the execution of a cyclic interrupt OB:

WinLC RTX attempts to execute the OB at the approp riate interval regardless of the amount of sleep time

that you configure for the scan. WinLC RTX provides several type s of free cycle sleep management for

managing sleep time. If a cyclic interrupt OB runs too frequently or requi res too much of the time allotted for

the total scan, it could cause the watchd og timer to time out (calling OB 80 or going to STOP mode).

If you schedule a cyclic interrupt OB (OB 30 to OB 38) to be executed at a specific interval, make certain

that the program can be executed within the time frame and also that your STEP 7 user program can

process the OB within the allotted time.

Error OBs

WinLC RTX provides a variety of error OBs. Some of these error OBs have the configured (the user-

assigned) priority class, while others (OB 121 and OB 122) inherit the priority class of the block where the

error occurred.

The local variables for OB 121 and OB 122 contain the following information that can be used by the

STEP 7 user program to respond to the error:

• The type of block (byte 4) and the number (bytes 8 and 9) whe re the error occurred

• The address within the block (bytes 10 and 11) where the error occurred

If the start event occurs for a particular error OB that has not been d ownloaded, WinLC RTX changes

operating mode from RUN to STOP.

Error or Fault Start Event (in Hex) Default

Priority Class

Time error OB 80 3501, 3502, 3505, 3507 26

Diagnostic interrupt OB 82 3842, 3942 26

Insert/remove module interrupt OB 83 3861, 3863, 3864, 3865, 3961 26

CPU hardware fault

(Windows "blue s creen") OB 84 3585 26 (or 28)

STEP 7 Operations and Components

Windows Automation Center RTX incl. SP2 93

A5E00992447-01

Error or Fault Start Event (in Hex) Default

Priority Class

Priority class error:

• Start event occurs for an

OB that has not been

downloaded.

• During the I/O cycle,

WinLC attempts to access

a module or DP slave that

is defective or not plugged

in.

OB 85 35A1, 35A3, 39B1, 39B2 26

Rack failure (distributed I/O): a

node in the PROFIBUS-DP subnet

has failed or has been rest ored.

OB 86 38C4, 38C5, 38C7, 38C8,

39C4, 39C5 26 (or 28)

Processing interrupt: execution of a

program block has bee n aborted OB 88 3571, 3572, 3573, 3575, 3576,

3578, 357A 28

Programming error

(For example: the user program

attempts to address a timer that

does not exist.)

OB 121 2521, 2522, 2 523, 2524, 2525,

2526, 2527, 2528, 2529, 2530,

2531, 2532, 2533, 2534, 2535,

253A; 253C, 253E

I/O access error

(For example: the user program

attempts to access a module that is

defective or is not plugged in.)

OB 122 2942, 2943

Same priority

class as the

OB in which

the error

occurred

For more information on the OBs, see the online help for STEP 7 or the System Software for S7-300/400

System and Standard Functions Reference Manual. To view this manual from a computer where STEP 7 is

installed, select the Start > Simatic > Documentation > English menu command and then double-click

"STEP 7 - System and Standard Functions for S7-300 and S7-4 00".

STEP 7 Operations and Components

94 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

System Functions (SFCs)

WinLC RTX provides SFCs, which are system fun ctions that perfo rm various tasks. The STEP 7 user

program calls the SFC and passes the required parameters; the SFC performs its task and returns the

result. The following table lists the SFCs that WinLC RTX supports:

SFC Name Description

SFC 0 SET_CLK Sets the system clock

SFC 1 READ_CLK Reads the syst em clock

SFC 2 SET_RTM Sets the run-time meter

SFC 3 CTRL_RTM Starts or stops the run-time meter

SFC 4 READ_RTM Reads the run-time meter

SFC 5 GADR_LGC Queries the logical address of a channel

SFC 6 RD_SINFO Reads the start information of an OB

SFC 9 EN_MSG Enable Block-Related, Symbol-Related and Group S t atus

Messages

SFC 10 DIS_MSG Disable Block-Related, Symbol-Related and Group Status

Messages

SFC 11* DPSYNC_FR Synchronizes groups of DP slaves

SFC 12* D_ACT_DP Deactivates and activates of DP slaves

SFC 13* DPNRM_DG Reads the diagnostic data of a DP slave

DP configuration tested: one ET 200M slave with one 8-input/8-

output module and one 16-output module

SFC 14* DPRD_DAT Reads the consi stent data from a DP slave

SFC 15* DPWR_DAT Writes the co nsistent data to a DP slave

SFC 17 ALARM_SQ Generates an acknowledgeable block-related messa ge

SFC 18 ALARM_S Generates a permanently acknowledgeable block-related message

SFC 19 ALARM_SC Queries the acknowledgement status for the last message

(SFC 17 or SFC 18).

SFC 20 BLKMOV Copies variables

STEP 7 Operations and Components

Windows Automation Center RTX incl. SP2 95

A5E00992447-01

SFC Name Description

SFC 21 FILL Initializes a memory area

1 word

50 words

100 words

SFC 22 CREAT_DB Creates a retentive data block in Work memory

The current values of the DB are retained after a warm restart

SFC 23 DEL_DB Deletes a data block.

WinLC RTX allows an application to del ete a non-sequence-

relevant data block.

SFC 24 TEST_DB Provides information about a data block

For WinLC RTX, SFC 24 can return the DB length and write-

protection flags for non-sequence-relevant data blocks, although it

returns error code 80B2 for non-sequence-relevant data blocks.

SFC 26 UPDAT_PI Updates the process-ima ge input table

SFC 27 UPDAT_PO Updates the process-image output table

SFC 28 SET_TINT Sets the time-of-day interrupt (OB 10)

SFC 29 CAN_TINT Cancels the time-of-day interrupt (OB 10)

SFC 30 ACT_TINT Activates the time-of-day interrupt (OB 10)

SFC 31 QRY_TINT Queries the time-of-day interrupt (OB 10)

SFC 32 SRT_DINT Starts the time-delay interrupt (OB 20 )

SFC 33 CAN_DINT Cancels the time-delay interrupt (OB 20)

SFC 34 QRY_DINT Queries the time-delay interrupt (OB 20 )

SFC 36 MSK_FLT Masks synchronous errors

SFC 37 DMSK_FLT Unmasks synchronous errors

SFC 38 READ_ERR Reads the error register

SFC 39 DIS_IRT Disables the processi ng of all new interrupts

SFC 40 EN_IRT Enables the processing of new interrupts

STEP 7 Operations and Components

96 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

SFC Name Description

SFC 41 DIS_AIRT Delays higher priority interrupts and asynchronous errors

SFC 42 EN_AIRT Enables the processing of new interrupts with higher priority than

the current OB

SFC 43 RE_TRIGR Retriggers cycle time moni toring

SFC 44 REPL_VAL Transfers a substitute value to ACCU1 (accumulator 1)

SFC 46 STP Changes the operating mode to STOP mode

SFC 47 WAIT Delays the execution of the STEP 7 user program by the specified

number of microseconds, rounded up to the nearest millisecond.

SFC 49 LGC_GADR Queries the module slot belonging to a logical address

SFC 50 RD_LGADR Queries all of the logical addresses of a module

SFC 51 RDSYSST Reads all or part of a system status list

SFC 52 WR_USMSG Writes a user-defined diagnostic event to the diagnostics buffe r

SFC 54* RD_DPARM Reads the defined parameter

SFC 55* WR_PARM Writes the dynamic parameters

SFC 56* WR_DPARM Writes the default parameters

SFC 57* PARM_MOD Assigns the parameters to a module

SFC 58* WR_REC Writes a data record

SFC 59* RD_REC Reads a data record

SFC 62 CONTROL Checks the status of the connection belonging to an SFB instance

SFC 64 TIME_TCK Reads the system time

SFC 78 OB_RT Reports OB run-time information, with resolution to the nearest

microsecond

SFC 79 SET Sets a range of outputs

SFC 80 RESET Resets a range of outputs

SFC 82 CREA_DBL Creates a data block in Load memory

STEP 7 Operations and Components

Windows Automation Center RTX incl. SP2 97

A5E00992447-01

SFC Name Description

SFC 83 READ_DBL Copies data from a block in Load memory

SFC 84 WRIT_DBL Writes to a Load Memory block so that the data is saved

immediately

Load memory blocks that are used to re cover from an abnormal

termination can be updated while the program is running. Use

SFC 84 only for larger segments of a database, not for frequent

variable processing.

SFC 85 CREA_DB Creates a DB that can be either retentive or non-retentive,

depending on the input parameter

• If retentive, the current values of the DB are retained after

a warm restart (OB 100).

• If non-retentive, the current values of the DB are not

retained after a warm restart (OB 100 ).

SFC 87 C_DIAG Determines the current status of all S7 connections

SFC 126 SYNC_PI Update process image part ition input table in synchronous cycle

SFC 127 SYNC_PO Update process image partition output table in syn chronou s cycle

* SFCs marked with an asterisk are available only when you have configured a DP interface as a

submodule

For more information on the SFCs, see the online hel p for STEP 7 or the System Software for S7-300/400

System and Standard Functions Reference Manual. To view this manual from a computer where STEP 7 is

installed, select the Start > Simatic > Documentation > English menu comma nd and then double-click

"STEP 7 - System and Standard Functions for S7-300 and S7-4 00".

Note: Some SFCs require special consideratio n regarding the possibility of a Windows Blue S cre en.

See the topic "Considerations for SFC 22, SFC 23, and SFC 82 - 85" for information.

Running Asynchronous SFCs Concurrently

WinLC RTX restricts the n umber of asynchronou s O B s that can b e running concurrently according to the

following rules:

• WinLC RTX allows a maximum of 5 instances of the asynchronous system function SFC 51 (index

B1, B3) to be running.

• WinLC RTX allows a maximum of 20 asynchronous SFCs from the following set to be

running: SFC 11, SFC 13, SFC 55, SFC 56, SFC 57, SFC 58, and SFC 59.

• WinLC RTX allows a maximum of 32 asynchronous SFCs in any combination from the following set

to be running: SFC 82, SFC 83, and SFC 84.

STEP 7 Operations and Components

98 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

SFCs That Can Cause the Scan Cycle to Vary

The following SFCs can cause the scan cycle to vary ("jitter"):

• SFC 22 (CREAT_DB)

• SFC 23 (DEL_DB)

• SFC 52 (WR_USMG)

• SFC 85 (CREA_DB)

Notes for SFC 82, SFC 83, and SFC 84

In contrast to the S7-300, WinLC RTX supports a synchronous interface for SFC 82, SFC 83, and SFC 84

in STARTUP. WinLC allows both the first call (with REQ = 1) and the second call (with REQ = 0) in

STARTUP so the action can be completed in STARTUP.

The normal STEP 7 error codes apply for SFC 82, SFC 83, and SFC 84, plus an additional return error

code of 80C3. These SFCs return the 80 C3 return error codes if WinLC RTX exceeds a limit of 32

outstanding SFC 82, SFC 83, and SFC 84 jobs.

STEP 7 Operations and Components

Windows Automation Center RTX incl. SP2 99

A5E00992447-01

System Function Blocks (SFBs)

System Function Blocks are logic blocks (similar to SFCs) that perform basic tasks when called by the

STEP 7 user program. You must provide a data block (DB) when you call an SFB.

The following table lists the SFBs that WinLC RTX supports.

SFB Name Description

SFB 0 CTU Provides a count-up counter

SFB 1 CTD Provides a count-down counter

SFB 2 CTUD Provides a count-up/down counter

SFB 3 TP Generates a pulse

SFB 4 TON Generates an on-delay timer

SFB 5 TOF Generates an off-delay timer

SFB 8 USEND Sends a data packet of CPU-specific length (two-way),

uncoordinated with receiving partner

SFB 9 URCV Asynchronously receives a data packet of CPU-specific length (two-

way)

SFB 12 BSEND Sends a segmented data block up to 6 4 Kbytes (two-way)

SFB 13 BRCV Receives a segmented data block up to 64 Kbytes (two-way)

SFB 14 GET Reads data up to a CPU-specific maximum length (one-way) from a

remote CPU

SFB 15 PUT Writes data up to a CPU-specific maximum length (one-way) to a

remote CPU

SFB 22 STATUS Query the status of a remote device

SFB 23 USTATUS Receive the status of a remote device

SFB 31 NOTIFY8P Generates block-relate d messages without acknowledgement

indication for 8 signals

SFB 32 DRUM Implements a sequencer

SFB 33 ALARM Generates block-related messages with acknowledgment display

SFB 34 ALARM_8 Generates block-related messages without values for 8 signals

SFB 35 ALARM_8P Generates block-related messages with values for 8 signals

STEP 7 Operations and Components

100 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

SFB Name Description

SFB 36 NOTIFY Generate block-related messages without acknowledgment display

SFB 52* RDREC Read data set

SFB 53* WRREC Write data set

SFB 54* RALRM Receives alarm data for a DP slave

SFB 65001 CREA_COM (WinAC ODK CCX)

SFB 65002 EXEC_COM (WinAC ODK CCX)

* SFBs marked with an asterisk are available only when you have configured a DP interface as a

submodule

For more information on the SFBs, see the onlin e help for STEP 7 or the System Software for S7-3 00/400

System and Standard Functions Reference Manual. To view this manual from a computer where STEP 7 is

installed, select the Start > Simatic > Documentation > English menu comma nd and then double-click

"STEP 7 - System and Standard Functions for S7-300 and S7-4 00".

Windows Automation Center RTX incl. SP2 101

A5E00992447-01

Tuning the Performance of the Controller

Scan Cycle for a PC-Based Controller

During one scan cycle, the controller updates the outputs, reads the inputs, executes the STEP 7 user

program, perform s communication tasks, and provides time for other applications to run. The following

parameters affect the scan cycle:

• Execution Time (in milliseconds) is the actual amoun t of time used by the controller to update the

I/O and to execute the STEP 7 user program.

• Scan Cycle Time (in millisecon ds) is the number of milliseconds from the start of one cycle to the

start of the next cycle. This value must be greater than the execution time of the scan to provide

execution time for any application that has a lower priority than WinLC RTX.

• Sleep Time (in milliseconds) determines how much time is available during the free cycle

(execution cycle for OB 1) to allow highe r prio rity OBs and other applications to use the resources

of the computer.

The Priority for the controller application also affects the scan cycle by determining when the controller runs

or is interrupted by other Windows ap plications. You must ensure that the sleep time occurs every 50

milliseconds or less in ord er for other Windows applications, such as moving the mouse, to operate

smoothly.

The tuning panel allows you to tune and test the performance of the controller by adjusting the parameters

that affect the scan cycle (minimum cycle time, minimum sleep time, and priority) without affecting the

system configuration for the controller. After testing tuning parameters, you use STEP 7 to configure the

minimum scan cycle time for the controller when you create the system (hardwa re) configuration.

Tasks Performed during the Scan Cycle

After you have used STEP 7 to create and download your co ntrol program to the controller, the controller

starts executing the control prog ram whe n you set the controlle r to RUN mode. Like any other S7 PLC, the

controller executes your STEP 7 user prog ram in a continuously repeated scan cycle.

In one scan, the controller performs the following tasks:

1. The controller writes the status of the OB 1-assig ned process-image output

table (the Q memory area) to the I/O module outputs.

2. The controller reads the states of the I/O module inputs into the OB 1-

assigned process-image input table (th e I memory a rea ).

3. The controller executes the STEP 7 user program in OB 1.

4. OB 1 waits until the minimum sleep time and minimum cycle time

requirements are met befo re starting another scan. Other OBs can execute

at this time.

Tuning the Performance o f the Controller

102 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Because the PC-based controller shares the resources of your computer with other programs (including the

operating system), you must ensure that the controller provide s sufficient time for other Wi ndows

applications to be processed. If the actual execution time for the scan cycle is less than the m inimum scan

cycle time that you configured with STEP 7, the controller suspends the free cycle (OB 1) until the minimum

scan cycle time is reached before starting the next scan. This waiting period, or sleep time, allows other

applications to use the resources of the computer.

The following figure provides an overview of the tasks that are performed by the controller during different

scan cycles.

Startup On a transition from STOP mode to RUN mode, the controller loads the system

configuration, sets the I/O to the default states, and executes the startup OB (OB 100

or OB 102).

The startup cycle is not affected by the minimum cycl e time and minimum sleep time or

watchdog parameters; however, it is affected by the execution time limit.

First

Scan

An OB with a higher priority class can interrupt the free cycle at any time, even during

the sleep time.

In the example above, the controller handles a hardware (I/O) interrupt that occu rs

during the sleep time by executing OB 40. After OB 40 has finished, the controller waits

for the minimum cycle time to start the next scan.

Note: It is possible for the controlle r to use all of the sleep time for processing

higher-priority OBs. In this case, other Windows applications may not have

sufficient time to run. Refer to the techniques for mana ging sleep time listed

below.

New

Scan

In the example above, the controller suspends the execution of OB 1 to execute a

cyclic OB (OB 35), which has a hi gher S7 priority than OB 1. The controller also

suspends the execution of OB 35 to han dle another I/O interrupt (OB 40).

After OB 40 finishes, the controller resume s the execution of OB 35, and after OB 35

finishes, the controller resumes the exe c ution of OB 1.

Tuning the Performance o f the Controller

Windows Automation Center RTX incl. SP2 103

A5E00992447-01

The length of the scan cycle is determined by the execution time of all OBs executed during the scan, the

minimum cycle time, and the minimum sleep time. If the execution time is less than the minimum cycle time

that was configured in the system configuration, the controller suspends the free cycle until the minimum

sleep time is met. During the sleep time, the computer runs any interrupt OBs and other Windows

applications.

Warning

Variation in the execution time or response time of the STEP 7 user program could

potentially create a situation where the equipment or application being controlled can

operate erratically and possibly cause damage to equipment or injury to personnel.

If the controller does not provide sufficient sleep time for other applications to run, the

computer can becom e unresponsive to operator inp ut, or the controller and other

applications can operate erratically. In addition, the ex ecution of the STEP 7 user

program can experience non-determi nistic behavior (jitter) such that execution times

can vary and start events can be delaye d.

Always provide an external emergency stop circuit. In addition, always tune the sleep

time and manage the performance of the controll er so that your STEP 7 user program

executes consistently.

Methods for Managing the Performance of WinLC RTX

While executing the STEP 7 user program, WinLC RTX can experience a variation in the process

execution time or response time that causes the scan times to vary or to exhibit non-deterministic behavior

("jitter"). You can use the following methods to manage the performance of WinLC RTX:

• Adjusting the priority for the controller: Affects the execution of Wi nLC RTX in relation to other RTX

processes executing on yo ur computer

• Adjusting the minimum sleep time and minimum cycle time parameters: Affects the execution of the

free cycle or OB 1 (OB priority class 1)

• Inserting sleep time into the STEP 7 user program (SFC 47 “WAIT”): Affects the execution for the

priority class of the OB that calls SFC 47 (and any lower prio rity class)

• Adjusting the sleep-monitoring algorithm of the execution monitor: Affects the execution of all OB

priority classes (if the other mechanisms do not meet the requireme nts for sleep time)

WinLC RTX provides a tuning panel for monitoring the performance and for modifying the parameters that

affect the scan cycle.

Tuning the Performance o f the Controller

104 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

What Causes Jitter?

Because the PC-based controller must share the computer with other running processes, the execution of

the control program can experie nce "jitter" when a higher-priority or active process uses the CPU or system

resources of the computer. Jitter is a variation in the process execution time or response time that causes

the scan times to vary or to exhibit non-deterministic behavior.

Jitter occurs when there is a delay in either the start or the finish of an OB. For example: the execution time

can deviate by a few milliseconds between scans, or the start of an interrupt OB can be delayed. For some

control applications, such time lapses do not disturb the proper operation of the controller, but in a highly

time-sensitive process, a jitter of even 1 ms can be significant.

The following settings for WinLC RTX can cause jitter in the execution of the control programs:

• Priority settings for competing RTX appli cation s

• Priorities among the WinLC RTX threads

• Execution Monitor sleep interval

The tuning panel of WinLC RTX provides several tools for redu cing jitter in the control program.

Jitter can also be caused by other sources than WinLC RTX:

• Jitter can be caused by the design of your control program. For ex ample, different branches in the

logic of the control program might cause the execution time to vary.

• Jitter can be caused by the computer h ardware. For example, jitter can be caused by an operation

with a long DMA cycle, such as a video card usin g the PCI bus. Jitter can also be caused by a

driver, such as for a CD drive or a diskette drive. Hardware-induced jitter cannot be managed by

software. For a uniprocessor system ru nning WinLC RTX, Ardence provides an application to help

evaluate the suitability of the computer hardware for use with the RTX extensions.

• Jitter can be caused by an application that was created with the WinAC RTX Open Development

Kit (ODK), such as when a synch ronous process takes too long to execute. Refer to the

documentation for WinAC RTX ODK for more information.

Priority Settings for Competing RTX Applications Can Cause Jitter

Every RTX application that is running on your computer has one or more threads (or tasks), and each

thread has a priority. The RTX subsystem executes the RTX application threads with the highest priority

first and executes a lower-priority thread only when all of the higher priority threads are finished or

suspended (for example, to wait for so me other activity to complete or to “sleep” for a specified time).

Threads with higher priorities interrupt and susp end the operations of threads with lower priorities. After the

higher-priority thread finishes, the lower-priority thread resumes its operation.

Tuning the Performance o f the Controller

Windows Automation Center RTX incl. SP2 105

A5E00992447-01

WinLC RTX operates in a real-time subsystem (RTSS) that provides a range of priorities above the typical

Windows priorities. All threads of WinLC RTX execute at higher priorities than threads for Windows

applications. Windows application s can not cause jitter in WinLC RTX, but another RTX thread that has a

higher RTSS priority than WinLC RTX can induce jitter.

You must also ensure that WinLC RTX and any other RTX application provide sufficient sleep time to allow

the Windows applications to run.

Jitter can occur when a process with a higher RTSS priority interrupts and suspends the execution of the

controller. As shown in the following figure, jitter typically appears in two forms.

The higher priority threads can cause jitter by delaying the start of an OB. This could delay

the start of the free cycle (OB 1) or of an interrupt OB (such as OB 35 or OB 4 0).

The higher priority application can cause jitter by extending the execution time for an

individual scan.

You can use the tuning panel to increase or decrease the priority for the WinLC RTX threads. The higher

you set the priority for the WinLC RTX threads in relation to the threads of the other RTX applications, the

less jitter you typically encounter. However, you must also e nsure that WinLC RTX provides enough sl eep

time for other RTX and Windows applications to run.

The tuning panel also provides informati on that allows you to monitor the amount of jitter in the scan cycle.

For more information about priorities, refer to the following topics:

• Adjusting the Priority

• Real-Time Subsystem Priorities

Tuning the Performance o f the Controller

106 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Priorities among the WinLC RTX Threads Can Cause Jitter

In addition to the thread that executes the OBs of the control program, WinLC RTX uses other threads,

including some with higher priority than the OB Execution thread. Some examples of higher-priority thread s

are the execution monitor, the start event for an OB, the watchdog e v ents, the timers, communication

interfaces, and the events for the DP I/O. Any of these higher-priority threads can induce jitter in the

execution of the control program.

The relative priorities (priorit y classes) of the OBs in the control program itself can also cause jitter. For

example, an error OB delays or interrupts the execution of all lower-priority OBs.

The threads of the interrupt events have a higher priority than the thread for the execution of

the control program. These threads can cause jitter by interrupting the execution of the

control program.

The OB Execution thread includes the different priority classes for the OBs of the control

program. The interrupt OBs can cause jitter not only by interrupting the free cycle (OB 1), but

also by interrupting another interrupt OB with a lower priority class.

The background tasks for WinLC RTX includes the threads use d for communicating with

other applications, such as STEP 7. The OB Execution thread and the higher-pri ority threads

affect the execution of these tasks.

Tuning the Performance o f the Controller

Windows Automation Center RTX incl. SP2 107

A5E00992447-01

The Sleep Interval Forced by the Execution Monitor Can Cause Jitter

WinLC RTX must sleep (relea se the

CPU) periodically in order for the other

applications to run. The free cycle

includes a sleep interval that follows the

execution of OB 1. However, this sleep

interval can be interrupted by higher-

priority OBs. Also, a scan cycle with a

relatively long execution time could

cause other applications to wait too long

to access the CPU.

To ensure that the controller does not

exceed a specified percentage of CPU

usage, an execution monitor measures

the sleep time within a fixed execution

time limit. If the controller does not sleep

for the specified amount of time within

the execution time limit, the execution

monitor forces a sleep interval.

Because the execution monitor ru ns in a higher priority class than any OB, the controller cannot interrupt

the forced sleep interval. This could delay the start of an interrupt OB, such as OB 35, until the end of the

forced sleep interval. This delay in han dling an interrupt OB results in jitter.

As a general rule for decreasing jitter, always design your control program to keep the execution time of the

higher-priority OBs as short as possible.

WinLC RTX provides several options for managing the sleep time to avoid the uninterruptible forced sleep

interval:

• You can increase the minimum sleep time paramete r for managing the sleep time for the free cycle

(priority class 1, or OB 1).

• You can call SFC 47 (“WAIT”) to insert an extra, interruptible sleep interval into the control program

for managing the sleep time for an appli cation -defin ed priority class (priority classes 2 to 24).

• You can adjust the sleep-monitoring algorithm for the execution monitor for managing sleep time at

a higher priority class tha n any OB.

Tuning the Performance o f the Controller

108 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Adjusting the Priority of the Controller

If other RTSS applications are installed in addition to WinLC RTX, you can adjust the priority of the

controller to improve performance. If not, you do not need to adjust the controller priority.

The priority of the controller determines how WinL C RTX run s in rel ation to other RTSS applications that

are running on the computer.

Adjusting the priority of the controller can redu ce or increase the amount of jitter in the scan time. The

tuning panel allows you to change the pr iority for the controller application. When you use the tuning panel

to change the priority, the controller automatically en sures that its interrupt activities, such as those which

schedule interrupt OBs, are also set to an app ropriate priority.

WinLC RTX does not control priorities in customer soft ware, such as asynchron ous threads in custom

software or other applications in the same environment.

Note: The CCX interface of the WinAC Open Development Kit (O DK) provides an

ODK_CreateThread function. Calling the ODK_CreateThread function creates asynchronous

threads with priorities that are adjusted when you change the priority of the cont roller.

If you do not use the ODK_CreateThread function to create threads (for example, if you use a

Windows API call to create a thread), changin g the priority of the controller does not adjust the

priority of those threads.

Refer to the documentation of the WinAC Open Deve lopment Kit (ODK) for more information.

While a PC-based controller mu st maintain the essential features of a SIMATIC S7 PLC, the PC-based

controller must also allow the other applications to run on the computer. The operating system of the

computer uses a concept of execution threads (or tasks) to run or execute the applications. Ea ch

application has one or more threads, and each thread has a priority. The operating system executes the

threads with the highest pri ority first and executes a lower-priority thread only when all of the higher priority

threads are suspended (for example, to wait for some other activity to complete or to “sleep” for a specified

time). Threads with higher priorities interrupt and suspend the operations of other threads that have lower

priorities. After the higher-priority thread finishes, the lo wer-priority thread resumes its operation.

To change the priority, follow these steps:

1. Use the Priority slider to choose a priorit y based on the prio rity levels for your operating system.

The new priority is displayed as you mov e the slide r.

2. Click Set to set the priority to the new value.

Real-Time Subsystem Priorities

WinLC RTX provides real-ti me priorities for the most demanding control projects that are absolutely time-

critical. Because WinLC RTX competes only with other appli cations in the real-time subsystem, the

controller provides the most deterministic behavior, with a possibility for reducing jitter in the scan cycle to

less than 500 microseconds.

Because the controller runs with an RT SS priority above the Windows priorities, the sleep time for the

STEP 7 user program determine s the amount of time for other Windows a ctivities and a pplications. Provide

sleep time that allows other applications more time to run. Use the tuning panel to monitor the variation in

scan times that occurs as the controller executes your STEP 7 user program.

Although the RTSS environment allows prio rities from 1 to 127, WinLC RTX only runs up to priority 62.

Another RTSS application thread could have a higher or lower priority than WinLC RTX.

The controller application installs with a default RTX priority of 50, which typically delivers satisfactory

performance. If the controller co mpetes with other RTSS applications for the computer resources, set the

priority for the controller applicatio n to run either above or below the priority of the other RTSS applications.

Tuning the Performance o f the Controller

Windows Automation Center RTX incl. SP2 109

A5E00992447-01

Managing the Sleep Time

Sleep Management Techniques

During a sleep interval, the controll er allows other applications to use the resources of the co mputer. By

managing the sleep time, you can tune the performa nce of the controller in order to allow all applications on

the computer to run with acceptable performance. You can use a variety of techniques for managing the

sleep intervals for the controller:

• Adjusting the minimum sleep time parameter. The minimum sleep time determines the amount of

sleep time that is added during the execution of the free cycle (OB 1). This sleep time affects only

OB priority class 1.

• Calling SFC 47 from your STEP 7 user program. SFC 47 inserts a sleep interval into the execution

of your STEP 7 user program. This sleep time affects OB priority classes 2 to 24.

• Adjusting the execution monitor. The execution monitor uses a sleep-monitoring algorithm (based

on the execution time limit and the maximum execution load parameters) to force a sleep interval.

The execution monitor runs asynchrono usly to the sc an cycle. This sleep time affects all OB priority

classes.

Contents of this topic:

• Managing the Sleep Time of the Controller

• Tuning Strategy

• Sample Interaction of the Execution Monitor and the Minimum Sleep Time

Managing the Sleep Time of the Controller

Because the controller sha res the resources of your computer with other applications, you must ensure that

the controller sleeps for a sufficient interval to allow the other ap plications to run.

Notice

The most effective method for granting time to other ap plications is to set the minimum sleep time

parameter to the largest value that your control application allows. The othe r methods for managing

the sleep time provide sufficient sleep time for the other applications to run, but may degrade the

performance of the controller.

Tuning the Performance o f the Controller

110 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

The controller provides the following techniques for managing the sleep time:

• The controller provides an executio n monitor that enforces the maximum execution load on the

resources of the computer. The execution monitor measu res the amount of sleep time taken by the

controller within an execution time limit, which is independ ent from the execution time of the scan

cycle. If necessary, the execution monitor forces a sleep interval to achieve the specified execution

load. This forced sleep interval susp ends the execution of any OB and can also delay the start of

an interrupt OB.

• The controller provides a minimum sleep time parameter that adds sleep time for the free cycle.

This sleep interval occurs after the execution of OB 1. The minimum sleep time affects only priority

class 1. An OB in a higher prio rity class can interrupt this sleep interval. The controller does not

adjust the minimum sleep time to compensate for the execution ti me of interrupt OB. However, any

forced sleep interval (g enerated by the execution monitor) is subt racted from the sleep interval

generated by the minimum sleep time.

• The controller supports SF C 47 ("WAIT"), which inserts a specified sleep interval for the priority

class of the OB that calls SFC 47. This sleep interval the OBs at the same or lower priority class as

the OB that calls SFC 47, but an OB in a higher priority class can interrupt this sleep interval. You

can use SFC 47 to create sleep time that can be interrupted so that the controller can avoid jitter

when handling any interrupts that are critical for the application.

Tuning Strategy

As you test the performance of the controller during the developme nt phase of your project, consider the

following strategy for adjusting the sleep time:

1. Set the minimum sleep time parameter to 0 and run the STEP 7 user p ro gra m. This allows you to

determine whether there is una cceptabl e jitter in the scan cycle.

2. To reduce any unacceptable jitter, first use the tuning panel to increase the minimum sleep time

and observe the effect on cycle time and CPU usage.

3. If the amount of jitter is still unacceptable, review the sections of the STEP 7 user program that are

being affected by the jitter. If possible, have your STEP 7 user program call SFC 47 to add sleep

time.

4. To further reduce any jitter, increase the execution time limit to the maximum possible executi on

time for your control program.

Tuning the Performance o f the Controller

Windows Automation Center RTX incl. SP2 111

A5E00992447-01

If the sleep management techni ques do not provide adequate improvement in reducing jitter, con sid er

increasing the priority for the controller. (The priority of the controller is not the same as the priority class of

an OB.)

Sample Interaction of the Execution Monitor and the Minimum Sleep Time

To help explain the tools for managing the slee p time of the controller, the followi ng example shows how

the execution monitor and the minimum slee p time can interact:

• The first sample shows the sleep time that would be g enerated by the execution monitor alone ,

with no minimum sleep time added to the free cy cle.

• The second sample shows how the execution of the free cycle is affected by adding a minimum

sleep time to the scan cycle.

The following example describ es the execution of a STEP 7 user program that uses OB 1 to start a 1-

second timer, and then che ck the timer after an elapsed time of 1 se cond (1000 ms). The cont roller has

been configured with the following parameters:

Parameter Value

Execution Time OB 1 takes 900 ms to execute.

Minimum Sleep Time 0 ms

Minimum Cycle Time 0 ms

Maximum Execution Load 90% (uses the default wake/sleep algorithm)

Execution Time Limit 9 ms (uses the default value)

Forced Execution Sleep 1 ms (uses the default value)

Tuning the Performance o f the Controller

112 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Sleep Time Generated by the Execution Monitor (Minimum Scan Time = 0)

If you set the minimum sleep time parameter to 0, the controller uses the execution monitor alone to

provide sleep time. The figure shows the operation of the execution monitor, using the default values.

The execution monitor suspends the execution of OB 1 for 1 ms after every 9 ms of execution by default in

order to enforce a limit of 90% execution load (CPU usage). For every 1 second of elapsed clock time, the

default execution time for OB 1 is 900 ms, with forced sleep intervals totaling 100 ms.

Notice that the sleep time occurs at intervals within the execution of OB 1.

Tuning the Performance o f the Controller

Windows Automation Center RTX incl. SP2 113

A5E00992447-01

Adding a Minimum Sleep Time for the Free Cycle

This figure shows how cha nging the minimum sleep time from 0 to 200 affects the execution of OB 1. The

execution monitor still forces 100 ms of sleep time to occur during the execution of OB 1. With the minimum

scan time parameter set to 200 ms, the controller then sleeps for only another 100 ms, for a combined total

of 200 ms, before starting the next free cycle.

The total scan time increases to approximately 1100 ms: the execution time (900 ms) for OB 1, the forced

sleep time (100 ms), and the sleep time at the end of the scan cy cle (100 ms).

Tuning the Performance o f the Controller

114 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Adjusting the Minimum Sleep Time and Cycle Time

The tuning panel provides the following parameters that allow you to manage the sleep time of the free

cycle (priority class 1, or OB 1):

• Minimum Cycle Time (in milliseconds) sets the minimum number of milliseconds f rom the start of

one free cycle to the start of the next free cycle. This value must be greater than the execution time

before it causes any sleep time to occur within the free cycle. You use STEP 7 to configure the

minimum cycle time for the controller when you create the system (hardware) configuratio n. You

can use the tuning panel t o adju st the minimum cycle time, but any changes are discarded when

you shut down the controller. Ho wever, you must use STEP 7 to make the changes p ermanent.

• Minimum Sleep Time (in milliseconds) determines how much sleep time is available during the free

cycle (OB 1) for allowing higher priority OBs and other applications to use the resources of the

computer. The controller automatically saves any changes to the minimum sleep time made with

the tuning panel. You do not use STEP 7 to make any change to the minimum sleep time

permanent.

The execution of the free cycle is affected by both the minimum sleep time and the minimum cycle time

values.

• The minimum cycle time by itself results i n a fixed sca n cycle time with a variable sleep time (if the

minimum cycle time is large enou gh to accommodate the execution time plus the sleep time ).

• The minimum sleep time by itself results in a fixed sleep time with a variable scan time, depending

on the length of the execution time.

The minimum sleep time value guarante es that a configured amount of sleep time occurs within each free

cycle, even if the value for the minimum cycle time is too small. The controll er releases control of the CPU

for a sleep interval, This sleep interval i s the larg er of either the configured minimum sleep time value or a

sleep time that is computed from the minimum cycle time parameter.

Warning

If you set the minimum scan time to a value larger than the watchdog time, WinLC

goes to STOP mode during the first scan at the end o f the watchdog time interval.

Causing the controller to go to STOP mode unexpecte dly can cause damage to

process equipment or inj ury to personnel.

Do not set the minimum scan cycle time to be longer than the scan cycle monitoring

time (the watchdog time) configured in the STEP 7 Hardware Configuration Editor.

Tuning the Performance o f the Controller

Windows Automation Center RTX incl. SP2 115

A5E00992447-01

Parameters That Affect the Sleep Time for the Free Cycle

The following figures expla in the interaction between the execution time, the minimum sleep time, and the

minimum cycle time parameters.

For the first sample scan shown in the example above, the execution time plus minimum

sleep time is less than the minimum cycle time. In this case, the controller increases the

sleep time until the minimum cycle time is achieved.

For the second sample scan shown in the example above, the execution of OB 35 increa ses

the execution time, and the execution time plus the minimum sle ep time is greater than the

minimum cycle time. In this case, the controlle r waits the minimum sleep time before starting

the next scan.

For the third sample scan shown in the example above, the controller executes both a cycli c

interrupt (OB 35) and an I/O interrupt (OB 40). The execution time exceeds the minimum

cycle time, and the controller waits the minimum sleep time before executing the next scan.

For the fourth sample scan shown in the example above, the controller executes OB 40

during the sleep time after OB 1 has finished. In this ca se, the controller waits until the

minimum cycle time before starting the n ext scan.

Because the execution of OB 40 does not reset the minimum sleep time counter, it is

possible that the controller does not provide sufficient sleep time to allow other Windo ws

applications to be processed. You must then use other metho ds for ensuring that the

controller provides a sufficient amount of sleep time.

Tuning the Performance o f the Controller

116 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Hints

You can use the following tech niques to adjust controller performance using the minimum sleep time and

minimum cycle time parameters:

• Use the tuning panel to test values for the minimum cycle time. After you have determined the

optimum value for the minimum cycle time, use STE P 7 to update and download the system

configuration for the control ler.

Changing the operating mode from STOP to RUN deletes any value entered by the tuning panel

and resets the minimum cycle time to the value stored in the system configuration.

• To ensure that the controller executes the scan cycle on a fixed schedule, use the minimum cycle

time parameter.

• To ensure that there is always a sleep interval even if the execution time changes, set the minimum

cycle time to 0 (the default value) and modify the minimum sleep time as needed. Modifying the

minimum sleep time is especially useful during the development of your STEP 7 user program.

When you are tuning the operation of the controller, be aware that the following situations can increase the

time required to complete the scan cycle:

• The controller executes other OBs (such as OB 40 a nd OB 35) with higher priorities than OB 1.

• You use STEP 7 to monitor and debug the STEP 7 user program.

• You use a variable table (VAT) with STEP 7 to display the status of the STEP 7 user program.

• An application with a higher priority is running on your computer.

• The controller interacts with an HMI interface, such as WinCC.

Additional Methods for Managing the Sleep Time

• Using SFC 47 to add sleep time in the STEP 7 user program

• Adjusting the sleep-monitoring algorithm of the execution monitor

Tuning the Performance o f the Controller

Windows Automation Center RTX incl. SP2 117

A5E00992447-01

Using SFC 47 to Add Sleep Time in the STEP 7 User Program

SFC 47 (WAIT) inserts sleep time into the execution of the STEP 7 user program, allowing you to manage

the sleep time for a control prog ram by inserting the sleep time in a specific priority class. When the

STEP 7 user program calls SFC 47, the controller suspends the execution of the OB for a spe cified number

of microseconds and sl eeps. During this sleep perio d, the controller can interrupt this sleep period to

execute an interrupt OB. Because an O B with a higher priority class can interrupt the sleep time, higher

priority OBs execute with less chance of jitter.

Typically, you call SFC 47 from a cyclic OB (su ch a s OB 35) that starts within the executio n time limit of the

execution monitor.

For more information, refer to the example: Avoiding Jitter in the Start Time of an OB

To provide greater control over when the sleep time occurs, you can use SFC 47 to insert sleep time into

your control program. Calling SFC 47 in the control program also allows you to define which O B s are

affected by setting the priority class of the OB that calls SFC 47.

As shown in the following figure, you can use SFC 47 to insert a sleep interval that can satisfy the

execution monitor and still allow the controller to handle an interrupt OB. By using a cyclic OB (such a s

OB 35) to call SFC 47, you can ensure that the sleep interval occurs within the execution time limit of the

execution monitor.

The sleep time parameter i s rounded up to the nearest multiple of the HAL timer period defined in the

RTX Properties dialog. For example, if the HAL timer period is 500 microsecond s (the default), and the

sleep time parameter is 1200 microseconds, WinLC RTX round s up the sleep time to 1500 microseconds.

Additional Methods for Managing the Sleep Time

• Adjusting the Minimum Sleep Time and Cycle Time

• Adjusting the Sleep-Monitoring Algorith m of the Execution Monitor

Tuning the Performance o f the Controller

118 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Adjusting the Sleep-Monitoring Algorithm of the Execution Monitor

The execution monitor uses a sleep-monitoring al gorithm to ensure that the controller does not exceed a

configurable maximum execution load for the CPU usage within a monitor interval.

The monitor interval is calculated as the amount of time such that the maximum load percentage of the

monitor interval equals the entered execution time limit. The executi on monitor calculates the forced

execution sleep time as the difference betwee n the monitor interval and the execution time limit.

The execution monitor determines whether to insert a forced execution sleep time if the OB execution

exceeds the execution time limit.

If there is sufficient sleep time within the monitor interval, the execution monitor does not affect the

execution of the program. Otherwise, the execution monitor forces a sleep interval. The default execution

load is 90%, and the default execution time limit is 9 ms. For the default settings, the execution monitor

calculates a monitor interval of 10 ms and a forced sleep interval of 1 ms.

The execution monitor runs asynchrono us to the scan cycle and measures the amount of sleep time that

occurs within the monitor interval and enforces a mi nimum sleep interval.

• If the scan cycle (execution time plus sl eep time) is shorter than the monitor interval and the sleep

time is greater than or equal to the forced sleep value: The execution monitor does not force a

sleep interval.

• If the scan cycle is longer than the monitor interval: The execution monitor forces the controller to

sleep for the required amount of time. Because the execution monitor runs in a higher prio rity class

than any OB, the controller cannot interrupt the forced sleep interval. This could delay the start of

an interrupt OB, such as OB 35 or OB 40.

Use the tuning panel to configure the parameters for the sleep-monitoring algorithm of the execution

monitor.

For more information, see the example: Avoiding Jitter in the Start Time of an OB

Contents of this topic:

• Operation of the Execution Monitor

• Parameters of the Sleep-monitoring Algo rithm

• Configuring the Parameters of the Sleep-Monito ring Algorithm

• Situations that Cause the Execution Monitor to Force a Sleep Interval

• Situations that Prevent the Execution Monitor from Providing Sufficient Sleep Time

In addition to the sleep time that is added to the scan cycle (based on the minimum sleep time and

minimum cycle time parameters), the execution monitor uses a sleep-monitoring algorithm that is base d on

a maximum execution load (perce ntage of CPU usage). For the default execution load (90% CPU usage),

the execution monitor measures the length of time that the controller sleep s du ring the monitor interval of

10 ms and ensures that the controll er sleeps for at least 1 ms.

By measuring the sleep time, the execution monitor ensures that the controller allows the other applications

to access the computer resources while the controller sleeps. The execution monitor also provi des the

safety net in cases where there are programming errors (for exam ple, an infinite loop in OB 100) that are

not handled with other me chanisms.

The difference between the forced sleep intervals and the minimum sleep time is that the co ntroller can

interrupt the minimum sleep time to handle interrupts (such as OB 35 or OB 4 0), but cannot interrupt the

forced execution sleep time.

Tuning the Performance o f the Controller

Windows Automation Center RTX incl. SP2 119

A5E00992447-01

When the execution monitor force s a sl eep interval, the following actions occur:

• The controller immediately suspend s the execution of the OB for the forced sleep interval. By

forcing a sleep interval, the execution monitor increases the actual time between starting and

finishing the OB being executed.

• The controller cannot respond to the start event for any interrupt OB until the end of the forced

sleep interval. Delaying the start of the OB (for example, OB 35 or OB 40) until the end of the

forced sleep interval creates jitter or latency in the actual start time for the OB.

Operation of the Execution Monitor

The following figure shows how the execution monitor might affect a control program. Because the

execution time for OB 1 in this example is greater than the execution time limit, the execution monitor

inserts a 1-ms sleep interval after the first two monitor intervals. However, the execution monitor does not

insert a forced sleep interv al in the third monitor inte rval because the controller sleeps long er than the

required forced sleep interval as require d by the confi gured minimum sleep time.

Note

The execution monitor runs asynchrono us to t he scan cycle. The example above sho ws the

execution monitor measuring time from the begi nning of the scan cycle, but because the execution

monitor runs asynchronous to the control prog ram, the beginning of the execution time limit of the

execution monitor does not necessarily coincide with the begi nning of the scan cycle.

Tuning the Performance o f the Controller

120 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Parameters of the Sleep-Monitoring Algorithm

The sleep-monitoring algorithm of the execution monitor uses the following para meters:

Parameter Description

Execution Time

Limit This value defines the maximum time (in microsecond s) that the execution

monitor allows for OB execution before exceeding the configured maximum

execution load (CPU usage) of the moni tor interval.

To determine the CPU load caused by the execution of the control program,

the execution monitor measures the time that the cont roller sleeps during the

monitor interval. If the controller does not use a sufficient amount of sleep time

(indicating that the CPU load exce eds the maximum execution load), the

execution monitor forces the controller to sleep for the remainder of the

required forced execution sleep time.

The default value is 9000 microseconds (9 ms).

Note: If you set this value greater than approximately 50000 (50 ms), you may

observe jitter in Windows applications and in response to the mouse or

keyboard. Test that the execution time limit you choose is appropriate for your

application.

Maximum

Execution Load This value defines the maximum percentage of CPU usage that is allowed for

the controller to execute OBs during each monitor interval.

The default value is 90%.

Forced Execution

Sleep This read-only field shows how mu ch sleep time (in microseconds) the

execution monitor requires durin g the monitor interval to satisfy the

requirement for the maximum executio n load. The execution monitor subtracts

any controller sleep time that occurs during a monito r interval from the forced

execution sleep time to determine how much sleep time (if any) to force.

The forced execution sleep time is a calculated number based on the

execution time limit and the maximum execution load. The execution monitor

corrects this value as required, depending on the capability of the operating

system configuration to have timers operate at the spe cified interval s. For

example, if the HAL timer period (in the RTX Properti es dialog) is set to

500 microseconds, you cannot have a forced executi on sleep time of

1200 microseconds. It would be rou nded up to 1500 microsecond s.

The default value is 1000 microseconds (or 1 ms).

The execution monitor uses the execution time limit and the maximum execution load to calculate the

forced execution sleep. For example, the execution monitor uses the 90% usage rate and the 9-ms

execution time limit to calculate a 1-ms sleep interval . In this case, the monitor interval is 10 ms such that

90% of the monitor interval corresponds to the entered execution time limit (9 ms).

Tuning the Performance o f the Controller

Windows Automation Center RTX incl. SP2 121

A5E00992447-01

During the monitor interval , the execution monitor measures the actual amount of time that no OBs are

executing (the sleep time).

• If the controller sleeps longer than the sleep interval (forced execution sleep time), then the

execution monitor restart s another monitor interval and does not affect the control program.

• If the controller sleeps less than the sleep interval (forced execution sleep time), then the execution

monitor blocks the execution of any OBs for the remainder of the sleep interval.

Any control program sleep time imposed because of the sleep-monitoring algorithm is subtracted from the

sleep time configured for the end of the free cycle as defined by the minimum sleep time pa rameter.

The default value for the “Execution Time Limit” interval is 9000 microseconds (o r 9 milliseconds) and the

default value for the “Forced Execution Sleep” inte rval is 1000 microseconds (or 1 millisecond). This ratio

ensures that the control program execution cannot use more than 90% of the CPU time in any of the worst

case situations described a bove.

Configuring the Parameters of the Sleep-Monitoring Algorithm

The parameters of the sle ep-monitoring algorithm of the execution monitor are configurable from the tuning

panel:

To change the sleep-m onitoring parameters, follow these steps:

1. Enter values in the Execution Time Limit and the Max. Execution Load fields. You can change one

of the fields or both.

2. Click Set to set the parameters.

To restore the default sleep-monitoring param eters, follow these steps:

1. Click Default to display the default parameters.

2. Click Set to set the default parameters.

Changes to the sleep-moni toring parameter take effect when the controller is in RUN mode.

Tuning the Performance o f the Controller

122 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Situations that Cause the Execution Monitor to Force a Sleep Interval

The controller must relinquish control of the CPU long enough to satisfy the maximum execution load.

Typically, the sleep time that is added to the end of the scan cycle allows sufficient time for the operating

system to process the other Windows applications. However, some situations may require that the

execution monitor force a sleep interval.

Condition Description

Execution time for the

control program exceeds

the execution time limit

The configured minimum sleep time for the free cycle occurs after

OB 1 finishes. If the execution time is longer than the execution time

limit, the execution monitor forces a sleep interval because the

controller did not sleep for the required a mount within the monitor

interval.

Minimum sleep time is

insufficient for the

maximum execution load

Even when the scan cycle is less than the execution time, the

minimum sleep time may not provide enough sle ep time. In this case,

the controller would exceed the maximum execution load. The

execution monitor forces an additional sl eep interval to ensure that the

operating system can run the other applications.

Interrupt OBs reduce the

sleep time To process an interrupt OB (su ch a s O B 35, OB 40, or OB 85), the

controller can interrupt the sleep time for the scan cycle. This redu ces

the time that the controller actually sleeps and can cause the controller

to exceed the maximum execution load, whi ch affects the performance

of the other Windows application s.

By forcing a sleep interval, the execution monitor en sures that the

other Windows application can b e pro ce ssed.

Tuning the Performance o f the Controller

Windows Automation Center RTX incl. SP2 123

A5E00992447-01

Situations that Prevent the Execution Monitor from Providing Sufficient Sleep Time

In some cases, a high execution time li mit can prevent the execution monitor from managing the sleep time

of the control program adequately. Under the following co nditions, the control program utilizes too much

CPU time, which can result in jitter in Windows response time to the mouse, keyboard, or other

applications. For either case, the problem can be re solved by lowering the execution time limit.

Condition Description

Execution time for the

startup OB (OB 100 or

OB 102) and the

configured execution time

limit exceed

approximately 50 ms

During startup, the controller turns the watchd og timer off and cannot

handle a program error, such as a loop in the logic of the OB or an

excessively long initialization routine.

Because the scan cycle does not provide any sleep time for the

startup OB (such as OB 100), the execution monitor cannot relinquish

CPU time for other applications. If the startup OB executes for more

than approximately 50 ms, jitter can occur in Windows response time

to the mouse, keyboard, or other applications.

Execution time for the

control program and the

configured execution time

limit exceed

approximately 50 ms

Whenever the operating system has to wait more than approximat ely

50 ms to process the other Windows application s, the perfo rmance of

those applications can be noticeably affected. This can be a problem

for an OB 1 with a long execution time, especially if other OBs (suc h

as OB 35 or OB 40) extend the execution of OB 1.

Because the sleep time is added at the end of the scan cycle, and the

execution time limit is set to a high value, the sleep intervals are t hen

spaced too far apart for the other Windows applications to perform

naturally.

Additional Methods for Managing Sleep Time

• Adjusting the minimum sleep time and minimum cycle time parameters

• Inserting sleep time into the control program (SF C 47 “WAIT”)

Tuning the Performance o f the Controller

124 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Example: Avoiding Jitter in the Start Time of an OB

The following example discusses two possi ble solutions for a program that experiences jitter in the start of

a cyclic interrupt (OB 32 to OB 36).

• Inserting a sleep interval into the execut ion of your STEP 7 user p rog ram. For this solution, you call

SFC 47 (“WAIT”) and speci f y the length of time to sleep. The controller can interrupt this sleep

interval to process other OBs.

• Changing the sleep-mo nito ring alg orithm of the execution monitor. For this solution, you use the

tuning panel to change the execution time limit.

Scenario

The following example describ es the execution of a STEP 7 user program that consists of OB 1 and OB 35.

OB 1 takes 20 ms to execute, and OB 35 starts every 100 ms and takes 1 ms to execute. The controller

has been configured with the following parameters:

Parameter Value

Execution Time for the STEP 7 user

program OB 1: 20 ms, and OB 35: 1 ms

Minimum Sleep Time 10 ms (uses the default value)

Minimum Cycle Time 0 ms (uses the default value)

Maximum Execution Load 90% (uses the default wa ke/sleep algorithm)

Execution Time Limit 9 ms (uses the default value)

Forced Execution Sleep 1 ms (uses the default value)

The sleep time (10 ms) is added to the scan cycle after OB 1 has finished. However, because the

execution time for OB 1 (20 ms) exceeds the execution time limit (9 ms), the controller exceeds the

configured maximum execution load (90%) by not sleeping during the execution time limit. Therefore, the

sleep-monitoring algorithm forces the controller to sleep for 1 ms after every 9 ms that OB 1 executes. As

shown in the following figure, this forced sleep can cause a variance or jitter of up to 1 ms betwee n the time

that the start event and the time that the controller starts to execute OB 35. This jitter happens because all

controller operations are suspended during a forced sleep interval. Similarly, OB 35 could be suspended for

1 millisecond if the end of the execution time limit interval occurs while OB 35 is executing.

Tuning the Performance o f the Controller

Windows Automation Center RTX incl. SP2 125

A5E00992447-01

For many applications, a 1-ms jitter might be acceptable. However, you have several options for removing

this jitter:

• You can modify the STEP 7 user program to call SFC 47 and insert sleep time that can be

interrupted by OB 35.

• You can adjust the parameters for the sl eep-monitoring algorithm to avoid the jitter caused by the

execution monitor.

Solution 1: Insert a sleep interval into the execution of your STEP 7 user program

You could avoid the forced sleep interval by using SFC 47 to add a periodic sleep interval that occurs

within the execution time limit (for this example, 9 ms). This sleep interval not on ly ensures that the sleep-

monitoring algorithm does not force the controlle r to sleep, but also allows the co ntroller to suspend this

sleep interval and execute any OB that has a higher priority than the OB that calle d SFC 47.

For this example, you can use SFC 47 to remove the jitter in OB 35:

• By ensuring that SFC 47 executes at a specified time. The STEP 7 user program calls SFC 47

from an OB (such as OB 36) that has a priority greater than OB 1.

• By ensuring that OB 35 executes as scheduled. You configure OB 36 to have a lower priority than

OB 35.

• By ensuring a sufficient sle ep interval during the execution time limit. You configure SFC 47 to wait

for 3 ms, which ensures a sleep interval of at least 2 ms.

To maintain a 50% ratio for CPU usage (20 ms execution time for OB 1 with a 10 ms minimum sleep time),

configure OB 36 to run every 6 ms (so that OB 1 executes for 6 ms, then sleeps for 3 ms). You can then

change the minimum sleep time to 0 ms, unless you want to decrease the ratio for CPU usa ge.

To create an OB 36 that calls SFC 47 to create a 3 ms sleep inte rval:

1. Using the STEP 7 Program Editor: Create an OB 36 for your STEP 7 user program, and enter the

following program:

CALL “WAIT” // SFC 47 wait function

WT: 3000 // 3000 microseconds or 3 milliseconds

2. Using the STEP 7 Hardwa re Configuration tool, configure the priority level and execution time for

OB 36:

• Open the WinLC Properties dialog box and select the Cyclic Interrupt tab.

• Set the priority for OB 36 to 2 (or any other priority lower than the priority for OB 35).

• Configure OB 36 to execute every 6 ms (by entering 6 in the Execution field).

The following figure shows how SFC 4 7 affects the execution of the STEP 7 user program. Because OB 36

ensures that the controller sleeps at least 1 ms within the 90% wake interval, the execution monitor does

not insert a forced sleep interval. Therefore, OB 35 executes witho ut any delay or jitter.

Tuning the Performance o f the Controller

126 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Solution 2: Change the sleep-monitoring algorithm to eliminate the forced sleep interval

The following figure shows the jitter in the start time of OB 35 and also shows the values displayed by the

tuning panel. Notice that the tuning panel shows only the information about OB 1. The tuning panel does

not display information about OB 35. For this example, the execution time for OB 1 is 20 ms. With the

minimum sleep time of 10 ms, the total free cycle time is 30 ms. OB 35 and other interrupt OBs can make

the total scan time more than this, depending on how fast the interrupt OBs execute.

By changing the parameters of the sleep-monito ring algorithm, you can configure the execution monitor to

use the minimum sleep time in the free cycle. For ex ample: if the longest total scan time for this example is

less than 45 ms, change the execution time limit to 45000 microse con ds (45 ms):

1. Open the tuning panel.

2. Change the execution time limit to 45000 (microseconds). For this example, do not change the

value for the maximum execution load.

3. Apply the new value.

Tuning the Performance o f the Controller

Windows Automation Center RTX incl. SP2 127

A5E00992447-01

The following figure shows the effect of the chang ed execution time limit.

Tuning the Performance o f the Controller

128 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Isochronous Mode for a Constant Bus Cycle

You can operate the DP Master in an isochron ous m ode to maintain a constant bus cycle time.

Note: WinLC RTX allows you to use isochronous mode on more than one PROFIBUS-DP subnet;

however, your computer must not share the interrupt (IRQ) of the PCI slots used by the DP

interfaces with any device operating in the Windows operating system (for example, a video card).

For example, the SIMATIC Box PC 627 provides two PCI slots that can be used for isochronous

mode on two different PROFIBUS-DP subnets.

To implement an isochronous DP cycle, you assign a synchronous interrupt OB (OB 61 or OB 62) with an

associated process image partition to the DP master for synchronous update. Each isochronous DP cycle

contains the following elements:

• A global control command (Send Authorization) notifies the slave d evices of the start of the bus

cycle.

• The cyclic inputs and outpu ts are updated.

• Any acyclic operations are performed.

• A variable delay allows the next DP cycle to start on the next multiple of the configured cycle time.

During the bus cycle, two e v ents signal the STEP 7 user program:

• At the end of the I/O update, an interrupt schedules the synchronous OB for execution.

• At the start of the succeeding cycle (when the Send Authori zation command is being transmitted to

the slave devices), an event signals Win LC RTX that further execution of SFC 126 and SFC 127

should return an error.

Between the two events (between the interrupt and the transmission of the global control command), the

synchronous OB can call SFC 126 and SFC 127 to execute the synchronous updating of the proce ss

image partition that was assigned to the synchro nous OB. If these SFC calls execute without error, the I/O

update is synchronized to the proces s image partition update and occurs at a constant interval between

updates.

You configure the DP bus cycle when you configure network properties for the DP master.

System Requirements for an Isochronous DP Cycle

For an isochronous DP cy cle, your system requires one of the following CP cards operating in interrupt

mode:

• CP 5613 card, hardware revision 6 or higher

• CP 5613 A2, any hardware revision

• CP 5611 card, hardware revision 5 or later

• CP 5611 A2, any hardware revision

To determine the revision level, you can use either the Set PG/PC Interface utility of STEP 7 or you can

view the submodule diagnostics.

Windows Automation Center RTX incl. SP2 129

A5E00992447-01

Connecting the Controller to the SIMATIC NET OPC

Server

WinAC RTX can use the SIMATIC NET OPC server to read and write data over the network. You use the

following tools to configure the OPC connection:

• OPC Scout for configuring the co nnection to the SIMATIC NET OPC server

• STEP 7 (HW Config and NetPro) for conf iguring the WinAC RTX controller

• Station Configuration Editor for configuring the PC station

Configuring an OPC Server conne ction requires the installation of SIMATIC NET.

Note: The critical step most frequently overloo ked is Step 3: Configuring the S7 connection for the

OPC server in NetPro. After adding the conne ction for the OPC server, you must set the

connection type to "S7 connection" and enter a Lo cal ID for the connection.

Task Overview

Step 1: Station Configuration Editor (SIMATIC NET)

Add the OPC server to the PC station.

Step 2: HW-Config (STEP 7)

Add the OPC server to the hardware configuration in S TEP 7.

Step 3: NetPro (STEP 7)

Add an S7 connection for the OPC server to the configuration of WinLC RTX.

Step 4: SIMATIC Manager (STEP 7)

Download the configuration to the controller.

Step 5: OPC Scout (SIMATIC NET)

Connect the controller to the OPC serv er.

Connecting the Controller to the SIMATIC NET OPC Server

130 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Step 1: Add the OPC Server to the PC Station

Tool: Station Configuration Editor (SIMATIC NET)

To configure the OPC server in the PC Station, follow these step s:

1. Open the Station Configuration Editor and select any index in the Station Configuration Editor.

2. Right-click the mouse to display the Add button. Click the Add button to display the

Add Component dialog.

3. Select "OPC Server" from the drop-down list of compo nent types:

4. Click OK to add the OPC server to the station co nfiguration. The Station Configuration Editor

displays the OPC Server in the index selected. (For this example, the OPC se rver is configured for

Index 1.)

5. Click OK to save the PC station configuration and to close the Station Co nfiguration Editor dialog.

Connecting the Controller to the SIMATIC NET OPC Server

Windows Automation Center RTX incl. SP2 131

A5E00992447-01

Step 2: Add the OPC Server to the Hardware Configuration

Tool: HW Config (STEP 7)

Task Summary:

• Create a STEP 7 project for a PC station with WinAC RTX.

• Insert the OPC server into the hard ware configuration.

• Configure the OPC server.

Creating the STEP 7 Project

1. Open STEP 7 and create a project (for example, OPCProject).

2. Insert a SIMATIC PC Station with the same name as entered in the Station Configuration Editor.

3. Double-click the Configuration icon for the PC Station to open the STEP 7 Hardware Configuration

utility.

4. Insert the WinAC RTX cont roller in the same index as configured in the Station Configuration

Editor.

Connecting the Controller to the SIMATIC NET OPC Server

132 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Adding the OPC Server to the Hardware Configuration

1. Expand the User Application folder in the Hardwa re Catalog.

2. Expand the OPC Server folder and sel ect the following component:

SW V6.4

3. Drag and drop the SW V6.4 component to the same index as configured in the Station

Configuration Editor. (For this example, the OPC server is configured for Index 1.)

Connecting the Controller to the SIMATIC NET OPC Server

Windows Automation Center RTX incl. SP2 133

A5E00992447-01

Configuring the OPC Server

1. Double-click the OPC Se rver entry (Index 1) to open the Properties dialog.

2. Click the S7 tab and select the Activate option (u nder Access Protection).

3. To use the STEP 7 symbols for accessing controller data from the OPC Server, select the option

for All (or for Selected, to specify specific entries in the symbol table) under the Use Symbols field.

4. Click OK to close the Properties dialog.

5. Click the Save and Compile icon to create the hardware configu ration for the PC station.

After you have compiled the configuration into the STEP 7 project, you can close HW Config and

return to SIMATIC Manager.

Connecting the Controller to the SIMATIC NET OPC Server

134 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Step 3: Add an S7 Connection for the OPC Server in NetPro

Tool: Ne tPro (STEP 7)

Task Summary:

• Configure an S7 connection for the OPC server to the PC Station configuratio n.

• Assign a Local ID for the OPC server connection.

Configuring an OPC Server Connection in NetPro

1. In SIMATIC Manager, browse to the OPC server and doubl e-click the Connections icon to open

NetPro.

2. Select the OPC Server in the PC station.

Connecting the Controller to the SIMATIC NET OPC Server

Windows Automation Center RTX incl. SP2 135

A5E00992447-01

3. Right-click the OPC server to display the context menu. Select the Insert New Connection menu

command to open the Inse rt New Connection dialog.

4. Set the connection type to S7 connection and cli ck OK to add the S7 connection for the

OPC server. The Properties dialog for the S7 connecti on opens automatically.

Connecting the Controller to the SIMATIC NET OPC Server

136 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Assigning a Local ID for the OPC Server Connection

1. In the Properties dialog, enter the Lo cal ID for the S7 connection (such as OPC_1).

2. Click OK to add the S7 connection to NetPro.

3. Click the Save and Compile icon to save and compile your changes into the S TEP 7 project.

After you have compiled the S7 connection for the OPC server into the STEP 7 project, you can close

NetPro and return to SIMATIC Manager.

Connecting the Controller to the SIMATIC NET OPC Server

Windows Automation Center RTX incl. SP2 137

A5E00992447-01

Step 4: Download the Configuration to the Controller

Tool: SIMATIC Manager (STEP 7)

Note: The controller must be executing to download the configuration from STEP 7.

To download the configuration, follow these ste ps:

1. If the controller is not executing, start the controller.

2. In SIMATIC Manager, select the SIMATIC PC Station icon.

3. Select the PLC > Download menu command or click the Download icon on the toolbar.

Connecting the Controller to the SIMATIC NET OPC Server

138 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Step 5: Connect the Controller to the OPC server

Tool: OPC Scout

Task Summary:

• Create an OPC Project.

• Add the connection to the SIMATIC NET OPC server .

• Define the items to be accessed through the OPC server.

Creating an OPC Project

Select the Start > SIMATIC >SIMATIC NET > OPC SCOUT menu comm and to create a new project in

OPC Scout.

Adding a Connection (Group) for the OPC Server

To add a connection to the SIMATIC NET OPC server, follow these steps:

1. Expand the Local Server(s) directory in the Servers a nd Groups for the project.

2. Double-click the OPC.SimaticNet element to add a connection (or group) fo r the SIMATIC NET

OPC server.

Connecting the Controller to the SIMATIC NET OPC Server

Windows Automation Center RTX incl. SP2 139

A5E00992447-01

3. In the Add Group dialog, enter the Group Name for the con nection (for example, Group1).

4. Click OK to add the group to the OPC server. OPC Scout adds the connection (Group1) to the

OPC server.

Connecting the Controller to the SIMATIC NET OPC Server

140 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Configuring the Items to be Accessed (Using Absolute Addressing)

Note: This procedure describes how to use absolute addressing when configuring the OPC server.

You can also use the STEP 7 symbol table for co nnecting the OPC server, as descri bed in the

section "Configuring the Items to be Accessed (Using the STEP 7 Symbol Table )".

Use the following procedure to configure the OPC server to use an absolute add ress for accessing data in

the controller:

1. Open the OPC Navigator by double-clicking the connection (Group1) for the OPC server.

2. To add an item to be accessed, expand the \S7: folder and select OPC_1.

Connecting the Controller to the SIMATIC NET OPC Server

Windows Automation Center RTX incl. SP2 141

A5E00992447-01

3. To configure access to M 0.0, expand the Obje cts folder and expand the M folder (for the bit

memory area).

4. Double-click the New Definition icon to open the Define New Item dialog.

5. To define a connection for M0.0, select X (for bit) field from the drop-down list in the Data Type and

enter the byte address (0) and bit numb er (0). (You can also enter an alias for the item.)

Connecting the Controller to the SIMATIC NET OPC Server

142 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

6. Click OK to define an item for M0.0.

7. Select the MX0.0 entry and click the Add arrow (-->) to enter the followin g syntax that defines a

connection for MX0.0:

S7:[OPC_1]MX0.0

8. Select the entry (S7:[OPC_1]MX0.0) and click OK to add the conne ction for MX0.0 to Group1.

Connecting the Controller to the SIMATIC NET OPC Server

Windows Automation Center RTX incl. SP2 143

A5E00992447-01

After adding the item to Group1, OPC Scout displays name and other parameters for the item. You can

now use any of the methods supported by SIMATIC NET OPC server.

Configuring the Items to be Accessed (Using the STEP 7 Symbol Table)

If you created a symbol table for the STEP 7 program that you downloaded, you can use the symbols for

connecting the OPC server to the data in the controller. To configure the items to be acce ssed using the

STEP 7 symbol table, follow these steps:

1. Open the OPC Navigator by double-clicking the connection (Group1) for the OPC server.

2. Browse to the folder for the controller to display the symbols that have been downloaded to the

controller.

Connecting the Controller to the SIMATIC NET OPC Server

144 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

3. After selecting the symbols for the data to be connected to the OPC server, click the Add button

(-->).

4. Click the OK button to add the symbol to Group1.

After adding the item to the group, OPC Scout displays symbol name and other parameters for the STEP 7

symbol.

Windows Automation Center RTX incl. SP2 145

A5E00992447-01

Reference Information

Technical Data

Order Number

WinLC RTX V4.3 is a component of the WinAC RTX 2005 package: 6ES7 671-0RC05-0YA0 or 6ES7 671-

0RC05-0YE0

WinLC RTX communicates with the distributed I/O as a PROFIBUS-DP master device. WinLC RTX does

not support local I/O.

Technical Specifications

The following table lists the techni cal information about WinLC RTX:

WinLC RTX Description

Work memory

Load memory

Limited by the amount of non-paging memory configured in

Windows. The following factors affect this amount:

• Amount of physical memory (RAM) installed in the

computer

• Other Windows drivers and RTSS programs being

executed at the same time as WinLC RTX

• Virtual memory configuration in Windows

To change the virtual memory paging co nfiguration,

follow these steps:

1. Select System from the Windows Control Panel.

2. From the Advanced tab of the System Properties

dialog, click the Settings button for Performa nce.

3. From the Advanced tab of the Performance Options

dialog, click the Change b utton for Virtu al memory.

4. Make any changes you need, and click OK on the

dialogs to complete your configuration.

Accumulators 4 (ACCU 1 to ACCU 4)

Local data 16 Kbytes for all priority classes (determined by HW Config,

Object Properties, Memory tab)

Clock Real-time system clock, based on the hardware clock of the

computer

With the WinAC Time Sync feature, WinLC RTX ca n function

as a time synchronization slave to the Time Synchronization

service, or as a time slave to devices on submodule DP-

subnets. WinLC RTX can also serve as a time master to

devices on the submodule DP-subnets.

I/O (digital and analog) 16384 bytes total I/O, addressable over a range of 0 to 1638 3

Reference Information

146 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

WinLC RTX Description

You can freely assign the I/O between digital and an alog

inputs and outputs. For example, you ca n assign all of

16384 bytes to the inputs or all of the 16384 bytes to the

outputs. However, the total amount allocated to all of the

inputs and outputs cannot exceed the maximum of

16384 bytes.

Process image I/O (user

configurable) Inputs: 512 bytes (default) or configurable from 0 bytes to

8192 bytes (I 0.0 to I 8191.7)

Outputs: 512 bytes (default) or configurable from 0 bytes to

8192 bytes (Q 0.0 to Q 8191.7)

Memory bytes

Retentive range (configurable)

Preset as retentive

16 Kbytes

Up to 16384 bytes (MB0 to MB16383)

16 bytes (MB0 to MB15)

Counters

Retentive range (configurable)

Preset as retentive

2048

C0 to C2047

8 (C0 to C7)

Timers

Retentive range (configurable)

Preset as retentive

2048

T0 to T2047

None

Clock memory 8 bits of clock memory (1 byte)

8 frequencies within 1 byte of bit memory (M): add ress is

configurable

Address rang es for logic blocks

(FB, FC, and DB): FB0 to FB65535

FC0 to FC65535

DB1 to DB65535 (DB0 is reserved)

Number of S7 connections CP 5611 and built-in PROFIBUS interfaces: 8

CP 5613: 50

Total for all submodules: 64

Nesting depth 24 per OB in a priority class (sequence l ayer)

At any one time, a priority class can have one OB an d up to

two synchronous OBs (OB 121 and OB 122). Each OB in the

priority class can have a nesting depth of 24.

Total number of blocks that can

be downloaded to WinLC RTX No fixed limit: The number of blocks that can be down loaded

is based on the memory requirements and the number of

blocks in the program

Reference Information

Windows Automation Center RTX incl. SP2 147

A5E00992447-01

Caution

Downloading a STEP 7 user program that is too large for the memory of the computer

can lock up the computer or cause the operation of WinLC RTX to become unstable,

possibly causing damage to equipment and/or inj ury to person nel.

Although STEP 7 and WinLC RTX do not limit the number of blocks or the size of the

STEP 7 user program, your computer d oes have a limit, based on the available drive

space and RAM. The limit for the size of the STEP 7 user program and number of

blocks for your computer can only be determined by testing a configured system

against the requirements of your control application.

The following table lists specific informa t ion about the PROFIBUS-DP interface, as supported by

WinLC RTX.

PROFIBUS-DP interface Description

DP address area 16384 bytes (inputs) and 16384 bytes (outputs)

Number of DP slaves supported

for each submodule DP in terface Dependent on the DP interface

• CP 5611 and built-in PROFIBUS interfaces: 64

• CP 5613: 125

Baud rate Up to 12 Mbaud:

9.6 KBPS, 19.2 KBPS, 45.45 (31.25) KBaud, 93.75 KBPS,

187.5 KBPS, 500 KBPS, 1.5 MBPS, 3 MBPS, 6 MBPS,

12 MBPS

Baud rate search (as a DP slave) Not applicable

Transfer memory (as a DP slave) Not applicable

Maximum distance Dependent on the baud rate

Reference Information

148 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Execution Times

Execution times for instructions in your user program vary depen ding on how the code is de signed and

implemented. The execution times listed below reflect typical execution times for STEP 7 user programs

running on WinLC RTX.

Math Operation Average Time

Bit operations 0.004 µs

Integer Math 0.003 µs

Floating-point math 0.004 µs

Reference Information

Windows Automation Center RTX incl. SP2 149

A5E00992447-01

Troubleshooting

Relevant Information for Ardence RTX

The RTX real-time extensions provide the determinism and performance of a real-time operating system

within the Windows 2000 or Windows XP environment. However, not all computer configurations (hardware

and software) support the installation and operation of Ardence RTX. When testing the operation of

Ardence RTX and WinLC RTX on your computer, check the following items:

• Ardence RTX installs a nd runs. Make certain that you have administrator (ADMIN) privileges for the

computer. Make certain that your comp uter meets the hardware and software requirements as

described in the RTX Runtime Release Notes and that the installed Hardware Abstraction Layer

(HAL) is one that RTX supports.

• Ardence RTX allows a free interrupt in order to operate a DP interface in interrupt mode (varies for

different computer manufacturers). If a free interrupt is not available, the DP interface operates only

in polled mode and not in interrupt mode.

• Ardence RTX is able to operate without interference from hardware comp onents installed in the

computer. Some compone nts (such as the video card) can cause problems that affect the

performance of real-time control with Arden ce RTX.

Setting the HAL Timer Period

The HAL timer period sets a numbe r of microseconds as the basis for RTX timers. The default value is

500 microseconds. WinLC RTX uses the RTX timers for starting certain OBs, for SFC 47 (WAIT), and for

other internal events. Changing the HAL timer period may provide more determi nistic behavior for some

applications that require accuracy of less than 1 millisecond. However, decreasing the HAL timer period

also increases the CP U load, with no b enefit for most applications.

Notice

Changing the HAL timer period to a value lower than the default value can increa se the

load on the CPU of your computer. This increased CPU usage could affect the operatio n

of your application.

If you change the HAL timer period, always test your application to ensure that the

increased CPU load d oes not adversely affect the operation of WinLC RTX.

To change the value for the HAL timer period, follow these steps:

1. Use the Start menu to open the Windows Control Panel.

2. Double-click the RTX Properties icon to display the RTX Properties dialog.

3. Click the Setting tab to display the parameters for the HAL timer.

4. Adjust the value for the HAL timer period (in microseconds) and click OK.

Running the DP Interface in Interrupt Mode

On some computers, Ardence RTX allows a free interrupt for the DP interface. (This varies for different

computer manufacturers.) If a free interrupt is not available, CP cards (including built-in PROFIBUS

adapters on Siemens PCs) operate only in polled mode and not in interrupt mode, which can affect the

performance of the CP card.

Refer to the topic on improving the perfo rmance of a DP interface.

Reference Information

150 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Using the RTX Platform Evaluator to Check Performance

On some computers, some comp onents of the computer (such as a video card) can cause problems with

Ardence RTX that affect the performance of real-time control.

For a uniprocessor system (singl e processor), you can use the RTX Platform Evaluation utility to determine

if your computer has any hardwa re in stalled (such as a video card) that may introduce jitter or latencies.

The RTX Platform Evaluator is not included with WinAC RTX. Contact Ardence to obtain the RTX Platform

Evaluator and information about how to install and use it.

Changing the HAL Type for the Computer

Caution

Changing the HAL type can create a situation where the computer cannot be booted. You

must then recover by using an Emergency Repair di sk.

Changing the HAL type changes the entry in the Windows registry. Errors in the registry

can keep the computer from rebo oting.

Before you make any changes to the Wi ndows registry (such as changing the HAL type),

always create an Emergency Repair disk. Select the Start > Programs > Accessories >

System Tools > Backup menu command to create an Emergency Repai r disk.

Refer to the Product Information document provid ed with your installation for specific directions regarding

changing the HAL type.

Reference Information

Windows Automation Center RTX incl. SP2 151

A5E00992447-01

Troubleshooting Network Problems

The controller panel provides the EXTF and BUSF status indicators that can be used to diagnose problems

with the PROFIBUS-DP network. The table belo w describes the activity of the EXTF and BUSF indicators

to help you determine the type of problem and a possible sol ution.

EXTF BUSF Description Action

No configuration Ensure that the DP configuration has been ente red into

your STEP 7 project. Download the project's System Data

container to the controller.

Off Off

Normal operation The configu re d DP slaves are responding. No action is

required.

Station failure

Check to see that the bus cable is con nected to

WinLC RTX (the CP card) and that all segments are

correctly terminated at powered nodes.

Check to see that the bus is not interrupt ed.

On Flashing

At least one of

the DP slaves

could not be

accessed

Wait for completion of the power-on cycle. If the indicator

continues to flash, check the DP slave s or evaluate the

diagnostic data for the DP slaves.

— On Bus fault

(hardware

failure)

Check the bus cable for an electrical short, or a broken

wire or connection.

On Off Diagnostic error

Indicates that a fault conditi on has not been cleared or

that one of the following problems has occurred:

• A DP module with diagnostic capability has

initiated OB 82.

• A submodule configuration does not match the

configuration downloaded from STEP 7, for

example one is CP 5613 and the other is

CP 5611.

In addition to these visual indicators, you can use the Diagnose Hardware feature of the STEP 7

programming softwa re to determine which nodes are experiencing problems and to determine the nature of

the problem.

Reference Information

152 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Improving the Performance of a DP Interface

To use a DP interface in isochronous m ode, the DP interface must operate in interrupt mode.

Note: WinLC RTX allows you to use isochronous mode on more than one PROFIBUS-DP subnet;

however, your computer must not share the interrupt (IRQ) of the PCI slots used by the DP

interfaces with any device operating in the Windows operating system (for example, a video card).

For example, the SIMATIC Box PC 627 provides two PCI slots that can be used for isochronous

mode on two different PROFIBUS-DP subnets.

Tool: You use the Windows Device Manager.

WinLC RTX accesses communications interfaces in e ither interrupt mode or polled mode. Interrupt mode

provides improved performance over polled mode.

In order for WinLC RTX to use interrupt mode for accessing a communication interface, you must configure

your computer so that the communication interface does not share an IRQ (interrupt request) with a

Windows-controlled devi ce.

Use the following procedure to determine whether the IRQ assignment for a communication interface is

shared with an IRQ assignment for a Wi ndows-controlled device:

1. Right-click the My Computer ico n and select the Manage menu command.

2. Click Device Manager, and then sel ect the View > Resources by Type menu command.

3. Expand the Interrupt request (IRQ) folder. The numerical values shown beside each entry indicate

the IRQ assignment.

4. Locate the entry for the communication card in the device list. If the IRQ assigned to this entry is

assigned to any other device, the card i s sharing an interrupt with that device. If this other device is

Windows-controlled, the co mmunication card will be operated in polled mode if it is configured as a

submodule of WinLC RTX. Otherwise, the comm unication card operates in interrupt mode.

To determine whether a device is Windo ws-controlled (as op posed to being RTX-controll ed), use the

following procedure:

1. Right-click the device entry for the communication card in the Device Manager list, and select

Properties.

2. Select the General tab on the Properties dialog, and check the Device type value. If it displays

"RTX Drivers", the device is RTX-controlled. Otherwise, it is Windows-controlled.

If the communication card shares the IRQ number with a Windows-controlled device, use one of the

following methods to change the system configuration for your computer and to assign a dif ferent IRQ

number to the communica tion interface:

• Use the BIOS setup utility for your computer to manipulate IRQ assignments and remove IRQ

conflicts.

• Install the communication card in a different PCI expansion slot of your computer. Because the PCI

slots are often assigned different IRQ n umbe rs, in sta lling the card in a different slot might eliminate

the conflict; however, changing the slot can also result in a new conflict.

• If the IRQ conflict is due to a built-in device (for example, an Ethernet or SCSI controller), con sider

using the BIOS setup utility to disable the conflicting built-in device, if possible. In this case, you

might have to use an equivalent expansi on card to replace the functionality for the disabled device.

Using these methods can be an iterative process, an d you might not find a solut ion that assigns a suitable

IRQ number to the communication interface. If no configuration can be found that eliminates the IRQ

conflict, you must either select a different PC platform or you must use the polled mode of operation for the

communication interfa ce.

For multiple cards, repeat this process as necessary to resolve all interrupt conflicts.

Reference Information

Windows Automation Center RTX incl. SP2 153

A5E00992447-01

Responding to Diagnostic Events

If an error is detected by the controller, the error condition is logged in the diagnostic buffer as a diagnostic

event. The diagnostic events that are typically associated with distributed I/O can cau se the controller to

execute the following OBs:

• OB 40 responds to hardware inte rrupts (process alarms) generated by an I/O module with

configured interrupt capability.

• OB 82 responds to diagnostic inte rrupts generated by an I/O module with configured diagno stic

interrupt capability.

• OB 83 responds to module removal/in sertion at a DP Slave, (for example, ET200M), which has

been configured for module pull/plug sup port.

• OB 85 responds to a priority class error. There are multiple causes for OB 85 relating to the DP I/O

system. If the controller attempts to copy a module's inputs to (or outputs from) the process image

during the I/O cycle, and the module is not operational, then an OB 85 is executed.

• OB 86 responds to a station failure or some other interruption of the physical network (such as a

short circuit).

• OB 122 responds to an I/O access error by the user program. If OB 122 is not programmed, the

controller goes to STOP mode.

You can use SFC 39 to SFC 42 to disable, delay, or re-enable any o f these OBs. If an OB is requested and

the OB has not been downloaded to the controller, the controller g oes to STOP mode.

The local variables for these OBs contain startup information indicating the cause for executing the OB.

The program for the OB can use this information for resp onding to the event. You can also use SFC 13

(DPNRM_DG) to read the diagnostic information from a DP slave .

For information about using OBs an d SFC 13, see the online help for STEP 7 or the System Software for

S7-300/400 System and Standard Functions Referenc e Manual. To view this manual from a co mputer

where STEP 7 is installed, select the Start > Simatic > Documentation > English menu command and

then double-click "STEP 7 - System and Standard Functions for S7-300 and S7-4 00".

Cross-Module Access Errors

Unlike hardware PL Cs, PC-based controllers do not allow a Load (L) or Transfer (T) instruction to access

bytes of more than one module. Consi der a configuration of two output modules, each containing five

bytes. Module 1 is addressed from 10 to 14, and Module 2 is addressed from 15 to 19. OB 1 contains the

instructions shown below:

L 5

T PAW 14

In this example, OB 122 is called becau se of an attempt to access bytes across a module boundary. A

word instruction at address 14 attempts to access add ress 14 and 15, which is prevented because the

addresses are not in the same module.

Reference Information

154 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

System Status List (SSL)

Using SFC 51 to Read the SSL

STEP 7 stores read-only information about the controller in the system status list (SSL) as a set of sublists.

You use SFC 51 (RDSYSST) to access the entries in the SSL. You supply the input parameters SSL_ID

and Index to access the records stored in the sublist. SFC 51 returns a two-word header and a sublist or

partial sublist. The header provides the following information abo ut the sublist:

• The first word defines the length (size in bytes) of a record for the sublist.

• The second word defines the number of record s contained in the sublist.

The requested information follows the header. The size of the sublist in bytes is the record length times the

number of records.

Note: The SSL_ID and Index values are represented as hexadecimal (16#) numbers.

For more information about the system status list, see the online help for STEP 7 or the System Software

for S7-300/400 System and Standard Fu nctions Reference Manual. To view this manual from a computer

where STEP 7 is installed, select the Start > Simatic > Documentation menu command. Select your

language and then double-click "STEP 7 - System and Standard Functions for S7-300 and S7-400".

WinLC RTX supports the following SSL e ntries. Some are available only when WinLC RTX has at least one

DP interface configured as a submodule :

Module Identification: 0111 Communications Status: 0132, 0232

CPU Characteristics: 0012, 0112, 0F12 LED Status: 0174

Memory Areas: 0113 DP Master System: 0090, 0190, 0F90

System Areas: 0014, 0F14 Module Status: 0591, 0991, 0C91, 0D91, 0E91

Block Types: 0015 Rack and Station Status: 0092, 0192, 0292,

0692

Local Module LED Status: 001 9, 0F19 Expanded DP Master: 0195, 0F95

Component Identific ation: 001C, 011C, 0F1C Diagnostic Buffer: 00A0, 01A0, 0FA0

Interrupt Status: 0222 Module Diagnosti cs: 00B1, 00B3, 00B4

Process Image Partitions: 0025, 0125, 0225,

0F25

Reference Information

Windows Automation Center RTX incl. SP2 155

A5E00992447-01

SSL_ID Descriptions

SSL_ID 0x11 (Module Identification)

0111 (hexadecimal)

SSL_ID Sublist Index and Contents of the Record

0111

Specific information for a module 0001: Order number, module type, and version

0007: Firmware version

SSL_ID 0x12 (CPU Characteristics)

0012, 0112, 0F12 (hexadecimal)

SSL_ID Sublist Index and Contents of the Record

0012 All characteristics for a module MC7 processing unit, time system, system response,

and MC7 language descri ption

0112 One specific group of

characteristics 0000: MC7 processing unit

0100: Time system

0200: System response

0300: MC7 language description

0F12 Header information only

SSL_ID 0x13 (Memory Areas)

0113 (hexadecimal)

SSL_ID Sublist Index and Contents of the Record

0113 Specific memory area 0001: User memory

0002: Load memory integrated

0003: Load memory inserted

0004: Maximum insertable Load memory

0005: Backup memory

0006: Peer-to-peer memory (shadow memory)

Reference Information

156 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

SSL_ID 0x14 (System Areas)

0014, 0F14 (hexadecimal)

SSL_ID Sublist Index and Contents of the Record

0014 All system memory areas for

a module Size and other parameters for eac h area of system memory

0F14 Header information only

SSL_ID 0x15 (Block Types)

0015 (hexadecimal)

SSL_ID Sublist Index and Contents of the Record

0015 All block types for a

module Maximum number and size for each type of block

SSL_ID 0x19 (Local Module LED Status)

0019, 0F19 (hexadecimal)

Note: SSL_ID 0x19 supports local, non-redundant CPUs. You can use SSL_ID 0x19 with a

redundant H CPU only when the H CP U is in a non-redundant operating mode. Use SSL_ID 0x74

to access information for a redundant H CPU.

SSL_ID Sublist Index and Contents of the Record

0019 All of the LEDs for the local module Status for all of the LEDs

0F19 Header information only

Reference Information

Windows Automation Center RTX incl. SP2 157

A5E00992447-01

SSL_ID 0x1C (Component Identification)

001C, 011C, 0F1C (hexadecimal)

SSL_ID Sublist Index and Contents of the Record

001C All of the information for a

component Controller name, module name, module tag, copyright,

serial number, project ID, module type, and

manufacturer information

011C Specific element for the

component 0001: Name of the controller

0002: Name of the module

0003: Module tag

0004: Copyright entry

0005: Serial number

0007: Module type

0009: Manufacturer and profile identification

000B: Location designation (OKZ) of a module

0F1C Header information only

SSL_ID 0x22 (Interrupt Status)

0222 (hexadecimal)

SSL_ID Sublist Index and Contents of the Record

0222 Start event for a specific OB OB number: Start event and time for the requested

Note: For a list of the OBs supported by WinLC RTX, refer to the following topics: Logic Blocks

Supported by WinLC RTX and Organization Blocks (OBs).

SSL_ID 0x25 (Process Image Partitions)

0025, 0125, 0225, 0F25 (hexade cimal)

SSL_ID Sublist Index and Contents of the Record

0025 All process image partitions Process image partitions for all of the OBs that

have been downloaded to t he module

0125 Process image partition for a specific

OB Partition number: OB configured for that partition

0225 OBs assigned for a specific pro cess

image partition OB number: Partition assigned for that OB

0F25 Header information only

Reference Information

158 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

SSL_ID 0x32 (Communications Status)

0132, 0232 (hexadecimal)

SSL_ID Sublist Index and Contents of the Record

0132 Specific set of parameters 0001: Number and type of connections

0002: Connections configu red

0003: Operator interface

0004: Protection level and mode switch selection

0005: Diagnostics

0006: Peer-to-peer status data

0008: Time system

000A: Baud rate

0232 Parameters for a redundant

system (H CP U) 0004: Protection level and mode switch selection

SSL_ID 0x74 (LED Status)

0174 (hexadecimal)

Note: Use SSL_ID 0x74 to access information about LEDs for any module, including a redundant

H CPU module. See also SS L_ID 0x19.

SSL_ID Sublist Index and Contents of the Record

0174 Specific LED 0002: INTF (Internal failure)

0003: EXTF (External failure)

0004: RUN (Run)

0005: STOP (Stop)

0006: FRCE (Force)

0008: BATF (Battery failure)

000B: BUSF1 (submodule 1 fault)

000C: BUSF2 (submodule 2 fault)

0012: BUSF3 (submodule 3 fault)

0013: BUSF4 (submodule 4 fault)

Reference Information

Windows Automation Center RTX incl. SP2 159

A5E00992447-01

SSL_ID 0x90 DP Master System

0090, 0190, 0F90 (hexadecimal)

SSL_ID Sublist Index and Contents o f th e Record

0090 All DP masters configured on the

network and downloaded to the module DP master identifier, address, and attributes

for all DP master s

0190 Specific DP master DP master identifier: Address and attributes

0F90 Header information only

SSL_ID 0x91 (Module Status)

0591, 0991, 0C91, 0D91, 0E91 (hexade cimal)

SSL_ID Sublist Index and Contents of the Record

0591 Module status information of all

submodules of the host m odule Irrelevant

0991 Module status information of all

submodules of the host m odule in the

rack specified

Rack or DP master syste m ID

0C91 Specific module, identified by the

logical base address Logical base address: Features and

parameters of the specified module

0D91 Specific station, identified either by

rack/station, by DP master identifier, or

by DP master identifier with station

number

Station identifier: Features and parameters fo r

all the modules of the specified station

0E91 Module status information of all

assigned modules Irrelevant

Reference Information

160 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

SSL_ID 0x92 (Rack and Station Status)

0092, 0192, 0292, 0692 (hexade cimal)

SSL_ID Sublist Index and Contents of th e Record

0092 Expected status of the stations of a

DP master 0: Local DP master

DP master identifier: Specific DP master

0192 Configuration and activation status for the

stations of a DP master 0: Local DP master

DP master identifier: Specific DP master

0292 Actual status for the stations of a

DP master 0: Local DP master

DP master identifier: Specific DP master

0692 OK state for the stations of a DP master 0: Local DP master

DP master identifier: Specific DP master

SSL_ID 0x95 (Expanded DP Master System)

0195, 0F95 (hexadecimal)

SSL_ID Sublist Index and Contents of the Record

0195 Specific DP master DP master identifier: Properties for the stations of the specified

DP master (such as DP mode, equidistant mode and cycle,

clock synchronization, and transmission rate)

0F95 Header information only

SSL_ID 0xA0 (Diagnostic Buffer)

00A0, 01A0, 0FA0 (hexadecimal)

SSL_ID Sublist Index and Contents of the Record

00A0 All of the entries in the diagnostics buffer Event information for every event listed in the

diagnostics buffer

01A0 Most recent entries in the diagnostics

buffer Number: Event information for the specified

number of entries in the diagno stics buffer

0FA0 Header information only

Reference Information

Windows Automation Center RTX incl. SP2 161

A5E00992447-01

SSL_ID 00B1, 00B3, and 00B4 (Module Diagnostics)

00B1, 00B2, 00B4 (hexadecimal)

Note: The information varies a ccording to the type of module specified.

SSL_ID Sublist Index and Contents of the Record

00B1 Diagno stic information (4 bytes) for a specific

module, identified by the logical base

address

Logical base address: First 4 bytes of

the diagnostic information

00B3 All of the diagnostic inform ation for a specific

module, identified by the logical base

address

Logical base address: Co mplete

diagnostic information

00B4 Specific DP slave, identified by the

configured diagno stic address Diagnostic address: Standard

diagnostic information for a DP station

Windows Automation Center RTX incl. SP2 163

A5E00992447-01

Glossary

Backplane bus: For hardware controllers such as the S7-300 or S7-400, the backplane bus is the printed

circuit board on the inside panel of the rack into which modules are inserted. (See topic "What Is a

PC Station?")

Blue Screen: Termination of the Windows operating system, resulting in a display on the monitor of the

fatal error on a blue background. A blue screen is also known as a Windows Stop Error.

Cold Restart: The controller executes OB 102 before starting the free cycle (OB 1). Like a warm restart, a

cold restart resets the peripheral inputs (PI) and changes the peripheral outputs (PQ) to a pre-

defined safe state (default is 0). However, a cold restart does not save the retentive memory (M, T,

C, or DB), but sets these areas to their default (initial) values.

Communications Interface: CP cards, Siemens PC built-in PROFIBUS interface, or Industrial Ethernet

interface that WinLC RTX uses for communications.

CP Card: Communications Pro ce ssor card: for WinLC RTX either a CP 5611 (including built-in PROFIBUS

interface on Siemens PCs), a CP 5613, or an Indu strial Ethernet interface (built-in or installed

card).

Deterministic behavior: Predi ctability of execution time and response time

DP interface: A Siemens CP card or Siemens PC built-in PROFIBUS interface used for PROFIBUS-DP

communications. (See topic "What Is a Communication Interface?")

Execution Load: The percentage of CPU time used by the controller.

Execution Monitor: The execution monitor of the controller measures the time that the controller sle ep s

and ensures that the cont roller does not exceed the maximum execution load. Th e execution

monitor uses the maximum execution load and the execution time limit to calculate the forced

execution sleep time.

Execution Time: The execution time is the actual time the controller takes to complete one pass through

the instructions of the STEP 7 user program. This include s executing OB 1 and updating the I/O.

Execution Time Limit: Defined maximum amount of time allowed for the controller to execute the STEP 7

user program. The execution monitor uses this value and the maxi mum execution load to calculate

the forced execution sleep time.

Forced Execution Sleep Time: The forced execution slee p time shows how much sleep time (in

microseconds) is required during the mo nitor interval t o meet the maximum execution load

requirement.

Free Cycle: The free cycl e consists of the basic tasks for priority class 1: writing to the outputs, reading the

inputs, executing OB 1, and completing the slee p time requi rement before triggering the next free

cycle. The controller executes these tasks at the base, or lowest, internal priority level for executing

the OBs. (Priority level in this context refers to OB priority classes, not the operating system priority

level.)

Glossary

164 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

HAL: Hardware Abstraction Layer. (See your Product Information for the relationship between HAL

configuration and WinL C RTX performance.)

IF Slot: Interface Slot. One of four slots allocated for communi cation interfaces configured as submodules

of the controller. (See topic "What Is an IF Slot?")

Index: A numbered slot in the PC Station, or virtual rack that represents a PC-based automation system.

The controller occupies one index; other component s can occupy other index slo t s. (See topic

"What is an Index?")

Industrial Ethernet: Physical communications layer that supports communicati on to STEP 7, S7 CPUs,

PGs, OPs, and S7 applications

Isochronous Mode: Configuration of DP cycle that yields a constant bus cycle time. (See topic

"Isochronous Mode for a Constant Bus Cycle".)

Jitter: Difference in the actual scan cycle time from the configured minimum scan time.

Load memory: Memory area (RAM) allo cated for all of the blocks downloaded from STEP 7 excluding the

symbol table and comments

Maximum Execution Load: Maximum percentage of CPU usage that is allocated for the controlle r. The

execution monitor uses this value and the execution time limit to calculate the forced execution

sleep time.

Minimum Cycle Time: Minimum number of milliseconds from the start of one cycle to the start of the next

cycle. You enter a value for the minimum cycle time when you use STEP 7 to configure the system

data for the controller. You can use the tuning panel to adjust this value as you test the

performance of the controller. After you have tuned the performance of the controller, use STEP 7

to enter the optimum cycle time value and download the new system data. Any value for the cycle

time that you enter with the tuning panel is overwritten by the value in the system data when the

controller changes from ST OP mode to RUN mode.

Minimum Sleep Time: Specific amount of time that the controller must wait before starting the next scan

cycle. You use the tuning panel to configure this para meter. The controller uses the minimum sleep

time and the minimum cycle time parameters to calculate the start of the next scan cycl e.

Monitor Interval: Length of time used by the execution monitor in determining whether to add a forced

sleep time. The monitor interval is the sum of the execution time limit and the forced execution

sleep time that is calculated based on the maximum execution load percentage.

MPI: Multi-point interface: physical communication s layer that can be used for S7 communica tions to STEP

7, S7 CPUs, and S7 applications

Non-deterministic behavior: Lack of predictability of execution time and response time asso ciated with

"jitter." (See topic "What Causes Jitter?")

Glossary

Windows Automation Center RTX incl. SP2 165

A5E00992447-01

OP: Operator panel

Organization Block (OB): Interface between the operating system and the STEP 7 user program. Called

by the operating system, organization blocks control cyclic and interrupt-driven program execution,

startup behavior of the controller and error handling.

PC Station: Representation of a software-base d virtual ra ck that defines a PC-based automation system.

(See topic "What is a PC Station?")

PG: Programming device

PG/OP communication: Communication between WinLC RTX and other S7 applications such a s

programming devices, ope rator panels, and S7 controllers. WinLC RTX supports PROFIBUS and

Industrial Ethernet for PG/OP communi cation.

Priority: The priority of an application determines the order in which the operating system executes or

interrupts an application in relation to the other applications that are running on the computer. An

application with a higher priority interrupts and suspends the exe cution of an application with a

lower priority. After the application with the higher p riority finishes, the application with the lower

priority resumes. A highe r number indicates a higher priority.

Priority Class: The priority class determines the order in which the controller e xecutes the individual

sections of the STEP 7 user program. Organization blocks (OBs) are ran ked by priority class.

Higher priority OBs interrupt lower priority OBs. The free cycle (OB 1) has the lowest priority. You

can use STEP 7 to change the prio rity class for an OB. A higher numbe r indicates a higher priority

class.

PROFIBUS: Physical communications layer that can be used for PROFIBUS-DP communications to I/O or

S7 communications to STEP 7, S7 CPUs, and S7 applications.

PROFIBUS-DP: Communications network proto col used to communicate to DP I/O

Restart Method: The restart method determines whi c h startu p OB is executed wheneve r the controlle r

changes from STOP mode to RUN mode . The startup OB allows you to initialize your STEP 7 user

program and variables. Th e two restart methods are Cold Re start (OB 102) and Warm Restart (OB

100).

RTX: Real-time extensions: Ardence real-time extensions to the Windows Operating system extensions

that allow processes to run in a real-time environment providing more deterministic execution and

protection from Windows operating system crashes.

S7 communication: Communication betwee n controllers on the network, hardware or software, using the

S7 communication functions. (See topic "S7 Communication Functions.")

S7 routing: Communications b etwe en S7 controllers, S7 applications or PC Stations across different

subnets through one or more network nodes acting as routers, configured with NetPro

Scan Cycle: The scan cycle includes writing to the outputs, reading the inputs, ex ecuting OB 1and all other

OBs, and completing the sleep time requirement.

Scan Cycle Time: Time required to execute the complete scan cycle, which includes the execution of OB1

and the minimum sleep time.

Glossary

166 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Sleep Time: Difference between the execution time of the free cycle and the total scan time. Sleep time

measures the time between the completion of OB1 and the start of the next scan cycle, and

ensures that the next scan cycle does not start until the end of the sleep interval. However, if the

start event for an interrupt OB (such as OB40) occurs during the sleep time, the controller executes

that interrupt OB.

Station Configuration Editor: Tool, accessible from taskbar, for configurin g the PC Station: for WinLC

RTX this includes Win LC Properties, submodule assigme nts, and submodule diagnostics for some

DP interfaces.

STEP 7 User Program: Application program created with STEP 7 and downloaded to the controller for

execution. It includes all organization bl ocks (such as OB 1 or OB 35) and the other logic blocks

that they call, including functions (FCs), system functi ons (SFCs), function blocks (FBs), and

system function blocks (SFBs).

Submodule: Communicati on interface in the PC that is designated for exclusive use by WinLC RTX. (See

topic "What Is a Submodule?")

System Function (SFC): Preprogrammed functio n that is integrated as a part of the operating system of

the controller and is not downlo aded as part of the STEP 7 user program. You can call an SF C in

your STEP 7 user program. Like a function (FC), an SFC is a blo c k "without memory."

System Function Block (SFB): Function block that is integrated as a part of the operating system of the

controller and is not downloaded as part of the STEP 7 user program. Like a function block (FB),

an SFB is a block "with memory." You must also create an instance data block (DB) for the SFB.

The instance DB is then downloaded to controller as part of the STEP 7 user pro gram.

Time Synchronization: The ability to broadcast a system standard time from a single source to all devices

within the system so that they may set their own clocks to the standard time.

Time Synchronization Serv ice (WinAC Time Synchronization): Software component of WinAC RTX

that provides the capability to synchronize time between components in the PC Station. (See the

documentation for the WinAC Time Synchronization Service.)

Virtual backplane bus: For PC-based controllers, the virtual backplane bus is a software-based, virtual

"rack" that enables communications between the controller and other PC Station components. (See

topic "What Is a PC Station?")

Wait Time: The wait time, or sleep time, is the time that the controller is not using the CPU. During this

time, the operating system can run other applications.

Warm Restart: Type of restart where the controlle r executes OB 100 before starting the free cycle (OB 1).

A warm restart resets the peripheral inputs (PI) and changes the peripheral outputs (PQ) to a pre-

defined safe state (default is 0). The warm restart also saves the current value for the retentive

memory areas for the memory bits (M), timers (T), counters (C), and data blocks (DBs).

Windows Stop Error: Termination of the Windows operatin g system, resulting in a display on the monitor

of the fatal error on a blue background. A Windows Stop Error is al so known as a blue screen.

Work memory: Memory area (RAM) allocated for the blocks used at runtime

Windows Automation Center RTX incl. SP2 167

A5E00992447-01

Index

Absolute addressing, OPC server, 132

Access points, 34

Access verification, 73

Accumulators, 139

Add/Remove Programs, 20

Adding blocks to Load memory, SFC 82 and SFC

84, 69

Adding S7 connection for OPC Server in NetPro,

128

Adding sleep time, 109, 110, 116

Address ranges, logic blocks, 139

Addressing errors, 147

Adjusting

minimum scan cycle time, 106

minimum sleep time, 106

priority, 93, 100

sleep-monitoring algorithm, 106, 110

Administrator user privileges, 10

Africa, customer support, iii

Alarms, 147

All indicators flashing, 47

ALT+C+M, resetting memory, 46

Always on top option, 72

Analog I/O, 139

Archiving, 53

Ardence RTX

advantages, 3

HAL (hardware abstra ction layer), 143

installation, 16

platform evaluator, 20

requirements, 8

Ardence RTX, 16

Asia, customer support, iii

Asynchronous SFC considerations, 69

Asynchronous threads, 100

Automatic reboot for Windows, 56

Automation License Manager, 18, 19

Autostart

configuring, 72

effect of setting on startup, 67

Avoiding jitter, 109, 110, 116

Backplane bus, 21

BATF status indicator, 47

Battery fault, 5, 47

BATTF, 5

Baud rate, 139

Blocks

creating, reading, and writing, 69

new, 5

OBs, 81

SFBs, 91

SFCs, 86

Blocks, 78

Blue Screen (unrecoverable fault in Windows), 3,

13, 54, 56, 57, 67, 81

Box PC, 5, 59

BRCV (SFB 13), 79

BSEND (SFB 12), 79

Bus cycle time, 120

BUSF status indicator, 47, 145

C_DIAG, 79

Change Password dialog, 74

Changing

HAL type or timer, 143

mode selector switch, 44

operating mode, 44

password, 74

priority, 100

sleep-monitoring algorithm, 110, 116

Characters (invalid in controller name ), 39

Index

168 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

Clock memory, 139

Closing the control panel, 43

Cold restart

configuring, 75

effect on startup, 67

Cold restart, 81

Commands

Diagnostic buffer, 51

Exit, 53

MRES (memory reset), 46

Options

Customize, 72

Security, 73

Tuning panel, 49

Commitanddisable (EWF command), 65

Communication

comparison to S7-400, 21

configuring, overview, 21

DPV1 extensions, 80

getting started overview, 21

nodes in network display, 32

PC Station vs. submodules, 21

PC-based control, 1

S7 communication functions, 79

STEP 7 and controller, 34

with DP I/O, 27

Communication interfa ces

configuration options, 27

configuring as submod ules, 29

definition, 24

IF slots, 28

supported, 24

Compact flash card, 65

Comparison, S7-400 to PC-based controller, 21

Compressed file system s, 61

Computer requirements, 8

Configuring

communication between STEP 7 and

controller, 34

communication interfa ce as submodule, 29

controller communications, overview, 2 1

language for controller panel and help, 72

Local ID for OPC server connection, 128

OPC server

connection, 132

hardware configuration, 125

in Station Configuration Editor, 124

items to be accessed, 132

overview, 123

OPC server, 125

operational parameters, 77

project in STEP 7, 36

S7 connection for OPC server in NetPro, 128

submodules, 29

verification, 40

WinAC data storage, 61

Confirmation, mode changes, 73

Connecting

controller to the OPC server, 123

STEP 7 to controller, 34

Connection

adding for OPC server with OPC Scout, 132

configuring for OPC server with NetPro, 128

Constant bus cycle time, 120

Contact information, iii

Context-sensitive help, 11

CONTROL (SFC 62), 79

Controller memory re set, 46

Controller name, invalid characters, 39

Controller panel

always on top, 72

introduction, 2

opening and closing, 43

status indicators, 47

Controller state, saving, 57

Index

Windows Automation Center RTX incl. SP2 169

A5E00992447-01

Counters supported, 139

CP 5611

available functionality, 5

communications sup ported, 24

improving performance, 146

operating in interrupt mode, 146

submodule limit, 28

CP 5613

communications sup ported, 24

improving performance, 146

operating in interrupt mode, 146

testing configuration, 31

CP Cards

configuration options, 27

configuring as submod ule, 29

configuring in STEP 7, 36

CPU hardware fault, 81

CPU indicators, 47

CPU menu

diagnostic buffer, 51

MRES (memory reset), 46

options

customize, 72

security, 73

tuning panel, 49

CPU usage

jitter, 96

CPU usage, 49

Crash operations (OB 84), 54

Creating

archive file, 53

data blocks, 69

password, 73

Cross-modul e access errors, 147

Customer service, iii

Customize command (CPU menu), 72

Cycle time, 49, 93, 106, 110, 116

Cycle/clock memory , 49

Cyclic input/output update, 120

Cyclic interrupt, 81

Cyclic OBs

calling SFC 47, 109

Dashes (in controller name), 39

Data blocks

created by SFC 85, 61

creating, reading, and writing, 69

Data retention, 67

Data set read and write SFBs, 80

DBs, 78

Default sleep monitor para meters, 110

Defective state, 47

Deleting

installed software, 15

submodules, 33

WinAC software, 20

Detecting

battery failure, 5

power loss, 5

Deterministi c scan cycle, 1 00

Device Manager, 146

Diagnosing hardware, STEP 7, 145

Diagnostic alarm interrupts, 81

Diagnostic buffer

saving the contents, 57

Diagnostic buffer, 51

Diagnostic buffer, 147

Diagnostic events, 51, 147

Differences between submodules and PC station

communication interfa ce s, 21

Differences between WinLC RTX and WinLC

Basis, 13

Digital I/O, 139

Disk space, 8

Display language, 72

Distributed I/O

Index

170 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

access error, 81, 147

available, 139

communication, 27

configuration, 36

overview, 1

supported communi cation interfaces, 24

technical data, 139

Documentation, iii

Downloading OPC server configuration, 131

DP address area, 139

DP bus cycle, 120

DP I/O

access error, 81, 147

communication, 27

configuration, 36

overview, 1

supported communi cation interfaces, 24

technical data, 139

DP I/O, 27

DP interface

configuration options, 27

configuring as a submod ule, 29

definition, 24

improving performance, 146

operating in interrupt mode, 146

DP interface, 27

DP Master

isochronous mode, 120

selecting, 80

DP network

subnet configuration, STEP 7, 36

troubleshooting, 145

DP network, 145

DP slaves

failure OB, 81

number supported, 139

DP submodule diagn ostics, 32

DPV1 event OBs, 80

DPV1 extensions, 80

Eliminating forced sleep interval, 116

E-mail addresses (Siemens), iii

Enable (EWF command), 65

English language option, 72

Enhanced Write Filter, 65

Equidistant DP, 120, 146

Error OBs, 81

Errors, 47, 147

Europe, customer support, iii

Evaluating Platform for RTX, 20

Events, diagnostic, 51

EWF, 65

Ewfmgr commands, 65

Execution monitor, 49, 93, 96, 101, 106, 110, 116

Execution priorities

adjusting, 100

Execution priorities, 100

Execution time

jitter, 96

limit, 110

Execution times of instructions, 142

Exit command (File menu), 53

External power supply, 70

EXTF status indicator, 47, 145

FBs, 78

FCs, 78

Features of PC-based control, 3

File menu

Archive, 53

Exit command, 53

Restore, 53

File Storage, 61

Flag memory size increase, 5

Flashing indicators, 47

Forced execution sleep time

Index

Windows Automation Center RTX incl. SP2 171

A5E00992447-01

eliminating, 116

Forced execution sleep time, 101, 110

Forced execution sleep time/counter, 49

Forced sleep, 109

Format for diagnostic buffer, 51

Forward slash (in controller name), 39

FRCE status indicator, 47

Free cycle, 81, 93, 96, 106, 110, 116

French language option, 72

Full-text search, 11

German language o ption, 72

GET (SFB 14), 79

Getting started, 21

Group name, OPC server connection, 13 2

Guest user privileges, 10

Hardware abstra ction layer (HAL)

Changing the HAL type, 143

HAL timer period, effect on sleep time

parameter, 109

Setting the HAL timer, 143

Hardware configuration

adding OPC server, 125

operational parameters, 77

STEP 7, 36

Hardware interrupts, 81, 147

Help menu

Using help, 11

Help on Event, diagnostic buffer, 51

HMI, effect on cycle time, 106

Hotline (Siemens), iii

Hyphen in controller name, 39

I/O

access error, 81, 147

available, 139

communication, 27

configuration, 36

overview, 1

supported communi cation interfaces, 24

technical data, 139

IF slots

configuration, STEP 7, 36

configuring, 29

IF slots, 28

Index, definition, 26

Indicator LEDs, 47

Industrial Ethernet

communication su pported, 5, 24

STEP 7 communication, 34

submodule limit, 28

TCP connections supported, 139

Insert New Connection dialog, 128

Inserting sleep time, 109, 110, 116

Installation

Automation License Manager, 18

evaluating, 20

licensing, 19

overview, 15

prerequisite software deleti on, 15

removing, 20

requirements, 8

SIMATIC WinAC NV128 card, 59

WinAC RTX software, 18

WinAC TimeSync, 18

Windows user privileges, 10

Interface slots

configuration, STEP 7, 36

configuration, WinLC Properties, 29

Interface slots, 28

Internet web sites (Siemens), iii

Interrupt assignments, 120

Interrupt mode, 146

Interrupt OBs, 81, 96

Interrupts, 93, 147

Index

172 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

INTF status indicator, 47

Invalid characters, controller names, 39

IRQ assignments, 120, 146

Isochronous Mode

interrupt mode requirements for DP interface,

146

Isochronous Mode, 120

Jitter

reducing, 49, 100, 101, 109, 110, 116

retentive data SFCs, 69

tuning panel, 49

Jitter, 96

Jitter, 100

Jitter, 101

Keyswitch position, 44

Language selection, 72

LEDs

controller panel, 47

CP 5613, 31

Microbox and Panel PC, 5

LEDs, 31

Licensing the softwa re, 19

Load instructions, 14 7

Load memory

Adding blocks with SFC82 and SFC84, 69

Creating, reading, and writ ing blocks, 69

reloading, 67

saving, 57

Load memory, 139

Local data space, 139

Local ID, OPC server connection, 128

Logic blocks

address ranges, 139

OBs, 81

SFBs, 91

SFCs, 86

Logic blocks, 78

Main program cycle, 81

Managing sleep time, 101

Manuals, iii

Manufacturer-specific interrupt, 81

Math operations, execution times, 142

Maximum execution load, 49, 101, 110, 116

Memory

areas, reloading on sta rtup, 67

problems, STEP 7 user program, 13, 36, 139

requirements, 8

reset, 46

saving, 57

specifications, 139

Microbox, 5, 59

Minimum scan cycle time, 49, 93, 101, 106

Minimum sleep time, 49, 93, 101, 106, 109, 110,

116

Minus sign (in controlle r name), 39

Mode, operating

allowed and prohibited actions, 44

changing, 44

saving switch position, 57

switch position on startup, 67

Modules

access errors, 147

pull/plug interrupts, 81

removal/insertion, 147

MPI, 34

MRES

effect on status indicators, 47

MRES, 46

Naming controller (invalid characters), 39

NAU signal, 5

Nesting depth, 139

Index

Windows Automation Center RTX incl. SP2 173

A5E00992447-01

NetPro, adding S7 connection for OPC server,

128

Network

nodes, 32

protocols, 34

STEP 7 communications, 34, 36

troubleshooting, 145

North America, customer support, iii

NVRAM, 59, 61

OB 1

example, avoiding jitter in starting cyclic

interrupt, 116

jitter, 96

managing sleep time, 106

OB 1, 75, 93

OB 100 and OB 102

startup after blue screen, 56

OB 100 and OB 102, 67

OB 100 and OB 102, 75

OB 100 and OB 102, 93

OB 122, 147

OB 20, effect on cycle time, 106

OB 32 to OB 36, jitter, 116

OB 35, effect on scan cycle, 93, 106

OB 40

effect on scan cycle, 93, 106

jitter, 96

OB 40, 147

OB 61/OB 62

isochronous mode usage, 120

OB 82, 147

OB 83, 147

OB 84, blue screen occurrence, 54

OB 85, 147

OB 86, 147

OB_STR_INFO, 67

Object properties, STEP 7, 77

OBs

diagnostic events, 147

execution, 96

interrupting sleep time, 110

supported by controller, 81

OBs, 81

ODK interrupt, 81

ON status indicator, 47

OPC Navigator, 132

OPC Project

adding OPC server connection, 132

creating, 132

defining items to access, 132

OPC Scout, 132

OPC server

adding S7 connection in NetPro, 128

adding to STEP 7 hardware configuration, 125

addition in Station Configuration Editor, 124

configuration overview, 123

configuring, 125

downloading configuration to controller, 131

properties, 125

required SIMATIC NET installation, 15

Opening the control panel, 43

Operating mode

allowed and prohibited actions, 44

changing, 44

saving switch position, 57

status indicators, 47

switch position at startup, 72

Operating mode, 44

Operating system requirements, 8

Operating system threads, 100

Operational parameters, 77

Optimizing performance, 49

Order number, 139

Organization blocks, 81

Overview

Index

174 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

getting started, 21

OPC server configuration, 123

PC-Based Control, 1

Pacific Region, customer support, iii

Panel

opening and closing, 43

status indicators, 47

Panel PC, 5, 59

Parameters, sleep monitor, 110

Part number, 139

Password

changing, 74

creating/changing, 73

prompt interval, 73

PC Boot, starting controller, 74

PC requirements, 8

PC station

communication interfa ce capabilitie s, 21

comparison to S7-400, 21

component difference from WinL C submodule,

configuring with STEP 7, 36

definition, 21

index, 26

names, 36

OPC Server component addition, 124

STEP 7 communication interface, 34

PC station, 29

PC-based control

features, 3

introduction, 1

PCI slot

independence from configured IF slot, 28

IRQ assignments, 146

Performance

DP interface, 146

improvements, 5

tuning, 49, 93, 101, 106, 110

Performance, 101

Period (in controller name ), 39

PG/OP communication

supported communi cation interfaces, 24

PG/OP communication, 27

PG/OP communication, 34

Platform Evaluator, 20

Polled mode, 146

Position of mode selector swit ch on startup, 67

Power failure, 5, 70

Power user privileges, 10

Power-Down State

using UPS to save, 70

Power-Down State, 57, 67

Priority

adjusting, 49, 93, 100, 101

effect of other applications on cycle time, 96,

106

OBs, 81

RTSS values, 100

setting, 116

Priority, 49

Priority, 81

Priority, 101

Priority, 110

Priority, 116

Priority class

error, 81, 147

values, 81

Priority class, 81

Privileges, 10

Process image

partition, 120

Process image, 139

Processing interrupt (stop avoidance), 81

PROFIBUS-DP

communicating with I/O, 27

Index

Windows Automation Center RTX incl. SP2 175

A5E00992447-01

CP card submodule, 29

DPV1 extensions, 80

equidistant DP, 120

isochronous mode, 120

network troubleshooting, 145

specifications, 139

supported communi cation interfaces, 24

Program blocks, new, 5

Programming error, 81

Properties - OPC Server dialog, 125

Protocols, 34

PUT (SFB 15), 79

Rack failure, 81

RAM requirements, 8

RDSYSST (SFC 51), 148

Reading data blocks, 69

Real-time subsystem priority, 100

Recovering

from a blue screen, 54

from a defective state, 47

license, 19

Registering controller for start at PC boot, 74

Reloading memory areas on startup, 67

Remote STEP 7 connection, 34

Removing

submodules, 33

WinAC software, 20

Renaming the controller (i nvalid characters), 39

Requirements, 8

Resetting memory areas, 46

Resolving IRQ conflicts, 146

Resources (computer), 106

Responding to diagn ostic events, 147

Restart

autostart feature, 72

following blue screen, 54

restart method, 75

Restart, 67

Restoring, 53

Retentive data

options, 59

SFCs, 69

Retentive data, 57

Retentive data, 61

Ring on test, 31

RTSS priority, 100

RTX extensions (Ardence)

advantages, 3

HAL (hardware abstra ction layer), 143

installation, 16

platform evaluator, 20

RTX extensions (Ardence), 16

RTX-controlled devices, 146

RUN

operating mode, 44

status indicator, 47

Running controlle r without a license, 19

S7 Blocks, 78

S7 Communication

functions, 79

supported communi cation interfaces, 24

S7 connections

adding for OPC server in NetPro, 128

number supported, 139

S7 memory areas, saving, 57

S7 routing, supported communication interfaces,

S7-400 communication

communication model, 21

PC-based control compari son, 21, 27

S7-400 communication, 21

Safety notification, 2

Scan cycle

adjusting priorities, 100

Index

176 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

jitter, 96

monitoring, 49

Scan cycle, 49

Scan cycle, 93

Scan cycle, 101

Scan cycle, 106

Scan cycle, 110

Scan cycle, 116

Security

setting level, 73

Security command (CPU menu ), 73

Selecting

autostart, 72

DP Master, 80

language for controller panel and help, 72

restart method, 75

Send Authorization command, 120

Service

starting the controller after reboot, 74

Service, 74

Setting

HAL timer/HAL type, 143

PG/PC Interface, 34

priority, 100, 116

restart method, 75

security options, 73

sleep monitor parameters, 110

Setup

Ardence RTX, 16

Setup, 15

Setup, 18

SFBs

S7 communications, 79

supported by controller, 91

supported by WinLC, 91

SFC 126/SFC 127

isochronous mode usage, 120

SFC 13, 147

SFC 39, 147

SFC 42, 147

SFC 47 (WAIT), 93, 101, 109, 116

SFC 51, 148

SFC 62, 79

SFC 85, 61

SFC 87, 79

SFCs

reading the system status list, 148

retaining data, 69

running asynchronous SF Cs concurrently, 86

S7 communications, 79

scan cycle jitter, 86

supported by controller, 86

Windows blue screen, 54, 55

SFCs, 86

Shutting down

result of NAU signal, 5

Shutting down, 43

Shutting down, 57

Shutting down, 67

Shutting down, 70

Siemens contact information, iii

SIEMENS PCs, built-in PROFIBUS interfaces, 24

SIMATIC NET

optional installation, 15

removal of requirement for WinAC RTX, 5

requirement for PC Station component

configuration, 21

requirement for using OPC server, 123

SIMATIC WinAC NV128 card, 59, 61

Slash (in controller name ), 39

Sleep interval

inserting, 116

Sleep interval, 96

Sleep management techni ques, 101

Sleep time

adding with SFC 47, 109

Index

Windows Automation Center RTX incl. SP2 177

A5E00992447-01

adjusting, 49, 106, 110

jitter, 96, 116

relationship to other applications, 100

scan cycle, 9 3

techniques for slee p management, 101

Sleep time parameter, SFC 47

relationship to HAL timer period, 109

Sleep-monitoring algorithm, 93, 101, 106, 110,

116

Sorting, diagnostic buffer events, 51

South America, customer suppo rt, iii

Specifications, 139

SRAM, 59, 61

SSL ID

0x11, 149

0x12, 149

0x13, 149

0x14, 150

0x15, 150

0x19, 150

0x1C, 151

0x22, 151

0x25, 151

0x32, 152

0x74, 152

0x90, 153

0x91, 153

0x92, 154

0x95, 154

0xA0, 154

0xB1, 155

0xB3, 155

0xB4, 155

backup memory (0x13), 149

block types (0x15), 150

C memory size (0x14), 150

communications status (0 x32), 152

component identification (0x1C), 151

contents (SSL IDs supported), 148

CPU characteristics (0x12 ), 149

CPU LED status (0x74), 152

CPU LED status, local only (0x19), 150

DB number and size (0x1 5), 150

diagnostic buffer (0xA0), 1 54

DP master system (0x90), 153

DP master system, expanded (0x95), 15 4

DP module diagnostics (00B1, 00B3, 00B4),

155

DP module status (0x91), 1 53

DP rack/station status (0x 92), 154

expanded DP master syste m (0x95), 154

FB and FC number and size (0x1 5), 150

H CPU LED status (0x74), 152

I memory size (0x14), 150

identification, module (0x11), 149

interrupt status (0x22), 151

L memory size (0x14), 150

LED status for redundant modules (0x74), 152

LED status, local only (0x19), 150

Load memory (0x13), 149

local module LED status (0x19), 150

M memory size (0x14), 150

master system (0x90), 153

maximum number and size of blocks (0x15),

150

memory area sizes (0x14), 150

memory areas (0x13), 149

module diagnostics (00B1, 00B3, 00B4), 155

module identification (0x11), 149

module LED status, local a nd redundant CPU

(0x74), 152

module LED status, local only (0x19), 150

module status (0x91), 153

OB number and size (0x1 5), 150

order number (0x11), 14 9

peer-to-peer memory (0x13), 149

PII memory size (0x14), 150

Index

178 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

PIQ memory size (0x14), 150

process image partitions (0x25), 151

Q memory size (0x14), 150

rack/station status (0x92), 154

redundant CPU LED status (0x74), 152

SDB number and size (0x15), 150

SFC51, 148

shadow memory (0x13), 149

size of blocks (0x15), 150

size of the memory areas (0x14), 150

size of user memory areas (0x13), 149

SSL IDs supported, 148

station, module status (0x91), 153

status, communications (0x32), 152

supported, 148

system areas (0x14), 150

T memory size (0x14), 150

types of blocks (0x15), 150

User memory (0x13), 149

version number (0x1 1), 149

SSL ID, 148

Start events, 81

Starting the controller

after blue screen, 56

at PC boot, 74

autostart, 72

effect on execution monitor, 110

programming blue scre en detection, 67

reloading memory areas, 67

restart method, 75

Starting the controller, 43

State, saving, 57

Station configuration editor

index in PC station, 26

OPC Server component addition, 124

using to configure sub modules, 29

Station failure, 147

STATUS (SFB 22), 79

Status alarm interrupt, 81

Status indicators, 47

STEP 7

connecting to WinLC, 34

diagnose hardware feature, 145

hardware configuration, 36

OPC server, 125

renaming the controller (inv alid characters), 39

requirements, 8

symbol table usage, OPC server, 132

system status list (SSL), 148

task summary, 77

STEP 7 user program

actions affected by operating mode, 44

adding sleep time with SFC 47, 109

archiving, 53

debugging, effect on cycle time, 106

deleting, 46

inserting sleep interval, 11 6

jitter, 96

memory problems, 36

restoring, 53

STOP

operating mode, 44

status indicator, 47

Submodules

capabilities, 21

configuration in WinLC Properties, 29

configuring in STEP 7, 36

connecting through to STEP 7, 34

definition, 27

diagnostics, 32

difference from PC station components, 27

IF slots, 28

removing, 33

Support, iii

Symbols

invalid characters in controller names, 39

Index

Windows Automation Center RTX incl. SP2 179

A5E00992447-01

OPC server data, 132

Synchronous cycle interrupts, 81

Synchronous interrupt OBs, 120

System function blocks (SFBs), 91

System functions (SFCs), 86

System requirements, 8

System status list (see SSL_ID), 148

Task summary, STEP 7, 77

TCP connections supported, 139

Technical specifications, 139

Technical support, iii

Telephone numbers (Siemens), iii

Testing

CP 5613 configuration, 31

jitter, 96

Threads, 96, 100

Time error, 81

Time Sync, 5

Time-delay interrupt, 81

Time-of-day interrupt, 81

Timer, HAL (hardware abstraction layer), 143

Timers supported, 139

TimeSync

feature description, 5

installation, 18

Timing adjustment, 49

Timing resolution, 13

Tools for OPC Server configuration, 123

Transfer instructions, 147

Transferring installed license, 19

Troubleshooting

defective state, 47

error conditions, 47

network problems, 145

Tuning panel, 49, 93, 96, 100, 106, 110, 116

Tuning performance, 93, 101, 106

Type, HAL (hardware abstraction layer), 143

Unbuffered startup, 67

Uninstalling

software prior to WinAC RTX installation, 15

WinAC, 20

Uninterruptible power supply (UPS), 70

Unrecoverable fault in Windows, 54

Update alarm interrupt, 81

UPS, 70

URCV (SFB 9), 79

USEND (SFB 8), 79

User privileges, 10

USTATUS (SFB 23), 79

Valid characters, controller name, 39

VAT, effect on cycle time, 106

Venturcom RTX (now Ardence RTX)

advantages, 3

HAL (hardware abstra ction layer), 143

installation, 16

platform evaluator, 20

Venturcom RTX (now Ardence RTX), 16

Verifying

configuration, 40

Virtual backplane bus, 21

WAIT (SFC 47), 109

Warm restart

configuring, 75

Warm restart, 81

Watchdog timer, 106

Web sites (Siemens), iii

WinAC Data Storage

options, 59

WinAC Data Storage, 61

WinAC RTX installation

Automation License Manager, 18

evaluating, 20

Index

180 Windows Automation Center RTX 2005 incl. SP2

A5EE00992447-01

licensing, 19

overview, 15

prerequisite software deleti on, 15

removing, 20

WinAC RTX software, 18

WinAC TimeSync, 18

Windows user privileges, 10

Windows

always on top, 72

automatic reboot, 56

blue screen (unrecoverable fault), 54

UPS settings, 70

user privileges, 10

Windows-controlled devi ces, 146

WinLC Properties

configuring a submodul e, 29

removing submodules, 33

WinLC Properties, 28

WinLC RTX differences from WinLC Basis, 13

Work memory

reloading, 67

saving, 57

Work memory, 139

Writing data blocks, 69