System Manual: Siemens SIMATIC HMI (WinCCv7.0: Scripting VBS, ANSI-C, VBA)

Подождите немного. Документ загружается.

1.4 Actions

Introduction

An action is always started by a trigger. An action, for example, is triggered in Runtime when

object is operated by a mouse click, a certain time has occurred or a tag has been modified.

Action Features

Actions are defined once in Global Script and then available independent of the picture. Global

Script actions are only valid in the project in which they were defined. Actions linked to a graphic

object are only valid in the picture in which they were defined.

Note

VBS does not currently allow the creation of computer-specific actions.

The following applies for clients in a multi-user system: All global actions configured on a

server are also executed on a client when a project is opened.

The following applies to clients in a distributed system: If actions should be used on a client

computer, copy all the action files in the corresponding project directory on the client.

Actions have the following properties:

● Actions are created and modified by the user.

● Actions in Global Script can be protected against modification and viewing by means of a

password.

● Actions have at least one trigger.

● Actions in Global Script have the file extension *.bac.

● Global Script actions are stored in the WinCC file system under: <Projektverzeichnis>

\ScriptAct\Aktionsname.bac

Action Trigger

Triggers are required to execute actions in Runtime. A trigger is linked to an action thus forming

the triggering event which calls the action. Actions without triggers will not be carried out.

The following trigger types are available in WinCC:

● Timer: Acyclic or cyclic trigger, e.g. for calling a picture or every hour.

● Tags: Change of value

● Event: Modification of object properties (e.g. change of color) or event on an object (e.g.

mouse click).

VBS for Creating Procedures and Actions

1.4 Actions

MDM - WinCC: Scripting (VBS, ANSI-C, VBA)

System Manual, 11/2008,

Processing of Actions in Runtime

In Graphics Designer

Two actions of the same type can be executed simultaneously in Runtime. In order, for

example, that cyclic actions are not hindered by an action executed by a mouse click, event

triggered actions and cyclic/tag triggered actions in Graphics Designer are executed

independently of each other.

Note

Please note that synchronization between both action types in WinCC may only be executed

by the DataSet object or by internal WinCC tags. As a result of the separate processing, no

common data area exists between event triggered and cyclic/tag triggered actions.

If processing cyclic actions in pictures, for example, is prevented by a high system load or

another

action, the action is started once at the next opportunity. Cycles which are not executed

are not retained in a queue but rejected.

After a change of picture, scripts still running are automatically stopped 1 minute after the

change of picture.

Scripts which are still running when Runtime is terminated are stopped after 5 seconds.

In Global Script

Picture-independent actions from Global Script are executed in Runtime in succession after

being triggered. If an action is triggered while another action is in progress, the second action

is retained in a queue until it can be executed.

Note

Please note that synchronization between actions in Global Script and in Graphics Designer

may

only be executed by the DataSet object or by internal WinCC tags. There is no common

data area between the actions in Graphics Designer and in Global Script.

Using the Actions

Actions can be used as follows:

● In Global Script The global actions defined here run picture-independent in Runtime.

● In Graphics Designer: The actions defined here only run in the configured picture. An action

is configured in Graphics Designer on an object property or an event on a graphic object.

VBS for Creating Procedures and Actions

1.4 Actions

MDM - WinCC: Scripting (VBS, ANSI-C, VBA)

System Manual, 11/2008,

See also

Creating and Editing Actions (Page 55)

Basic Principles of VBScript (Page 760)

Modules and Procedures (Page 18)

Using Visual Basic Script in WinCC (Page 14)

1.5 Multiple Use of Procedures and Actions

Introduction

An action configured with VBS in WinCC is always valid for the project in which it was defined.

Procedures have the following areas of application:

● Standard procedures apply globally to projects located on the computer on which they were

created.

● Project procedures can only be used in the project in which they were created. If a project

is copied, the project procedures (modules) are copied together with the project.

Multiple Use of Procedures and Actions

If actions or procedures/modules are to be used in other projects or on other computers, it is

possible either to:

● use the "Save As" function to store the action or module in a different project directory or,

for example, on a disk.

● to copy the action or module file in Windows Explorer and paste it in the corresponding

project or standard directory on the target computer.

The properties and trigger configured are retained during copying. Copied modules are directly

available in Runtime. Copied actions are executed in Runtime after they have been opened

and stored once.

Note

Tags used in an action or procedure must also be available on the target computer. If the tag

is not available, the action or procedure is not executed.

Procedures which are called in an action must be available on the target computer. If the

procedure is not available, a Runtime error occurs during Runtime.

VBS for Creating Procedures and Actions

1.5 Multiple Use of Procedures and Actions

MDM - WinCC: Scripting (VBS, ANSI-C, VBA)

System Manual, 11/2008,

Storing Procedures

If procedures need to be copied in other project directories in order to be able to use then in

other

projects or different computers, observe the storage path of the procedures in the WinCC

file system:

● Standard procedures: <WinCC-Installationsverzeichnis>\ApLib\ScriptLibStd

\Modulname.bmo

● Project procedures: <Projektverzeichnis>\ScriptLib\Modulname.bmo

Note

Since procedures are always stored in modules, always copy the module (*.bmo) in which

the procedure is contained.

The copied procedures/modules are visible after updating the Global Script navigation window

(context menu command "Update") or restarting the editor.

Storing Actions

If actions need to be copied in other project directories in order to be able to use then in other

projects or different computers, observe the storage path of the actions in the WinCC file

system:

<Projektverzeichnis>\ScriptAct\Aktionsname.bac

Each action is stored in a separate file. When an action is copied, all the triggers related to it

are also copied.

Note

Only actions created in Global Script are stored in the WinCC file system. Actions which are

programmed

in Graphics Designer are always stored with the current picture and cannot be

transferred individually. If a Graphics Designer picture is copied into another project directory,

the actions stored with the picture are also copied.

The copied actions are visible after updating the Global Script navigation window (context

menu command "Update") or restarting the editor.

VBS for Creating Procedures and Actions

1.5 Multiple Use of Procedures and Actions

MDM - WinCC: Scripting (VBS, ANSI-C, VBA)

System Manual, 11/2008,

See also

Modules and Procedures (Page 18)

Renaming a Procedure or Module (Page 54)

Saving a Procedure (Page 52)

Protecting a Module with a Password (Page 51)

Adding Module-related Information (Page 49)

Using Standard and Project Procedures (Page 47)

How to Write Procedure Codes (Page 45)

Creating a New Procedure (Page 42)

Creating and Editing Procedures (Page 39)

1.6 Use of CrossReference

CrossReference and Tag Trigger

The CrossReference from WinCC can be used to quickly find all the application points of tags,

even in VBS actions. Tag triggers in actions in Graphics Designer can be "linked" using

CrossReference, i.e. replaced by other tags at all or selected points.

Note

Tags can also be directly linked in Graphics Designer by marking the graphic object and

selecting the "Linking ..." command from the context menu.

Further information on CrossReference is available in the WinCC documentation.

Actions and CrossReference

All the actions used in a picture can be displayed by means of the picture properties. To do

this mark the picture in WinCC Explorer and select the "Properties" context menu command.

After double clicking on an entry, detailed information on the type of dynamics appears.

It is also possible to display all the tags and pictures used in actions by means of the WinCC

CrossReference.

CrossReference can also be used for the to link tag connections of Graphics

Designer actions easily.

Note

Use the standard formulations

HMIRuntime.BaseScreenName = "Screenname" and

HMIRuntime.Tags("Tagname") when addressing pictures and tags in your code in order

to ensure that the pictures and tags are registered by the CrossReference.

VBS for Creating Procedures and Actions

1.6 Use of CrossReference

MDM - WinCC: Scripting (VBS, ANSI-C, VBA)

System Manual, 11/2008,

Tags and CrossReference

All the pictures which are addressed with the standard formulation

' VBS1

HMIRuntime.Tags("Tagname")

are automatically compiled by the CrossReference of WinCC and then listed in the picture

properties.

If tags are addressed with different formulations in the code, this can be notified by the following

section of the CrossReference:

' WINCC:TAGNAME_SECTION_START

Const TagNameInAction = "TagName"

' WINCC:TAGNAME_SECTION_END

The section can be inserted in VBS actions as often as required.

Note

It is not possible to guarantee the compilation of combined tag names from the

CrossReference.

Pictures and CrossReference

All the pictures which are addressed with the standard formulation

'VBS2

HMIRuntime.BaseScreenName = "Screenname"

are automatically compiled by the CrossReference of WinCC and then listed in the picture

properties.

If pictures are addressed with different formulations in the code, this can be notified by the

following section of the CrossReference:

' WINCC:SCREENNAME_SECTION_START

Const ScreenNameInAction = "ScreenName"

' WINCC:SCREENNAME_SECTION_END

The section can be inserted in VBS actions as often as required.

Note

Always enter picture names without the extension "PDL" for reasons of compatibility with

future versions.

VBS for Creating Procedures and Actions

1.6 Use of CrossReference

MDM - WinCC: Scripting (VBS, ANSI-C, VBA)

System Manual, 11/2008,

See also

VBS Reference (Page 109)

VBScript Editors (Page 28)

Basic Principles of VBScript (Page 760)

Actions (Page 21)

Modules and Procedures (Page 18)

Using Visual Basic Script in WinCC (Page 14)

1.7 Using Global Tags in VBS

Introduction

Global tags can be defined in the Global Script Editor which can then be used in all actions

and procedures.

Using Global Tags in Graphics Designer and Global Script

Observe the following conditions when using global tags in Graphics Designer and Global

Script:

● In order to use a global tag in an action in Graphics Designer, call in the procedure in which

the tag is defined so that the associated module is loaded in Runtime.

● In order to use a global tag in an action in Global Script, at least one procedure must be

activated from the module in at least one global action in which the tag is defined so that

the module is loaded in Global Script Runtime. This does not need to be the procedure in

which the tag was defined.

This process is necessary because actions from Global Script and Graphics Designer are

processed independently of each other in Runtime. There is no common data area between

the two Runtime systems.

If you need to synchronize actions from Global Script and Graphics Designer, use the DataSet

object or internal WinCC tags.

Using Global Tags in Graphics Designer

When using global tags in Graphics Designer, observe the following conditions:

● In order to use a global tag in cyclic or tag triggered action in Graphics Designer, call in the

procedure in which the tag is defined. This also applies when the tag has already been

called in an event triggered action.

● In order to use a global tag in an event triggered action in Graphics Designer, call in the

procedure in which the tag is defined. This also applies when the tag has already been

called in a cyclic or tag triggered action.

VBS for Creating Procedures and Actions

1.7 Using Global Tags in VBS

MDM - WinCC: Scripting (VBS, ANSI-C, VBA)

System Manual, 11/2008,

This process is necessary because the cyclic/tag triggered actions and the event triggered

actions in Graphics Designer in Runtime are processed independently of each other in

Runtime. There is no common data area between the two types of action.

If you need to synchronize cyclic or tag-triggered actions and event-triggered actions, use the

DataSet object or internal WinCC tags.

In the case of Graphics Designer, it is also possible to define global tags in a separate

declaration section. Since event triggered and cyclic/tag triggered actions are separately

processed

in Runtime, the global tags can only be jointly addressed within the event triggered

or cyclic/tag triggered actions.

See also

Basic Principles of VBScript (Page 760)

Structure of VBScript Files (Page 97)

Creating and Editing Actions (Page 55)

Creating and Editing Procedures (Page 39)

VBScript Editors (Page 28)

Use of CrossReference (Page 25)

Actions (Page 21)

Modules and Procedures (Page 18)

1.8 VBScript Editors

1.8.1 VBScript Editors

Introduction

VBScripts can be programmed at two points in WinCC:

● In Global Script Global Script is the central editor for VBS programming. Call it in via WinCC

Explorer.

VBS for Creating Procedures and Actions

1.8 VBScript Editors

MDM - WinCC: Scripting (VBS, ANSI-C, VBA)

System Manual, 11/2008,

● In Graphics Designer: Graphics Designer can be used to program actions related to object

properties or events related to graphic objects. The action editor in Graphics Designer is

called in via the context menu in the Properties dialog of a graphic object.

Restrictions, Global Script - Graphics Designer

Graphics Designer can be used to program actions and picture-specific procedures but not

global procedures valid for the entire project. However, global procedures which were

programmed in Global Script can be called in.

Note

This documentation is used primarily to describe Global Script and, if necessary, makes

reference to deviations in the functionality compared to Graphics Designer. A detailed

description of the Graphics Designer action editor is provided in the WinCC help topic

"Dynamization".

Further Information

Further information on "Dynamization" is available in the WinCC documentation.

See also

Global Script Editor (Page 30)

VBS for Creating Procedures and Actions

1.8 VBScript Editors

MDM - WinCC: Scripting (VBS, ANSI-C, VBA)

System Manual, 11/2008,

1.8.2 Global Script Editor

Introduction

Global procedures and actions are created and edited in the Global Script editor.

Global Script provides a similar range of functions to that of the C script editor in WinCC.

Note

A detailed description of the action editor for the creation of picture-based actions and

procedures in Graphics Designer is provided under the WinCC help topic "Dynamics".

Starting Global Script

Global Script is started using the context menu "Open" command in the WinCC Explorer project

window.

Global Script is also automatically started when a module or action is opened by means of a

double click in WinCC Explorer.

Design of Global Script

Global Script editor is designed in accordance with the Windows standards.

The action editor in the Graphics Designer provides a similar range of functions to that of Global

Script.

A description of the Graphics Designer action editor is provided in the WinCC help topic

"Dynamization".

VBS for Creating Procedures and Actions

1.8 VBScript Editors

MDM - WinCC: Scripting (VBS, ANSI-C, VBA)

System Manual, 11/2008,