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

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

See also

Actions (Page 21)

How to change a trigger (Page 78)

How to add a trigger of the type "Tag" (Page 76)

How to add a trigger of the type "Timer" (Page 74)

Triggers (Page 69)

Creating and Editing Actions (Page 55)

1.10.8 How to Rename an Action

Introduction

Actions can be renamed in Global Script. When an action is renamed, the action name and

file name are changed.

The action to be renamed must not be open in the editor window.

Procedure

1. Open Global Script.

2. Select the name of the action to be renamed in the editor's navigation window.

3. Select the "Rename" command from the context menu.

4. Enter a new name for the action with the extension *.bac.

See also

Protecting an Action with a Password (Page 66)

Saving Actions (Page 67)

How to add information to the action (Page 64)

How to Edit Actions (Page 61)

Creating a New Action (Page 59)

Triggers (Page 69)

Creating and Editing Actions (Page 55)

Actions (Page 21)

VBS for Creating Procedures and Actions

1.10 Creating and Editing Actions

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

System Manual, 11/2008,

1.11 Activating Global Actions in Runtime

Introduction

Scripts defined in Global Script are always executed when the configured trigger occurs.

Scripts in the graphical Runtime system are executed when the picture is called in and the

configured event or trigger occurs.

In order that the picture-independent, Global Script global actions can be executed, the Global

Script Editor must be registered in the startup list of the Runtime computer.

Procedure

1. Select the "Properties" command in the computer's context menu WinCC Explorer. The

"Computer properties" dialog will open.

2. Click on the "Startup" tab

3. Activate Global Script Runtime.

4. Click OK to confirm your entries.

VBS for Creating Procedures and Actions

1.11 Activating Global Actions in Runtime

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

System Manual, 11/2008,

See also

Creating and Editing Actions (Page 55)

Creating and Editing Procedures (Page 39)

VBScript Editors (Page 28)

Using Visual Basic Script in WinCC (Page 14)

1.12 Diagnostics

1.12.1 Diagnostics

Introduction

If the scripts are executed and tested in Runtime, the Diagnostics window can be used to

display an analysis quickly.

Diagnostics Tools

WinCC provides a range of tools with which to analyze the behavior of actions in Runtime:

● The GSC Runtime and GSC Diagnostics application windows

● Use of a debugger

GSC Runtime and GCS Diagnostics

The GSC Runtime and GSC Diagnostics application window are used by inserting them in a

process screen. This can be a process screen developed for diagnostics purposes which is

called in Runtime.

The application windows are used for different strategies:

While Runtime is active, GSC Runtime provides information on the dynamic behavior of all

(Global

Script) actions, enables the individual startup as well as log on and off of each individual

action and offers the access point to the Global Script Editor.

GSC Diagnostics issues the Trace methods contained in the actions in the chronological

sequence they are called. This also applies to Trace instructions in procedures which are called

in actions. The targeted implementation of Trace instructions, e.g. for the output of tag values,

enables the progress of actions and the procedures called in them to be traced. The Trace

instructions are entered in the form "HMIRuntime.Trace(<Ausgabe>)".

The GSC Diagnostics displays trace output from C and VBS.

VBS for Creating Procedures and Actions

1.12 Diagnostics

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

System Manual, 11/2008,

Debugger

In order to test the scripts in Runtime, a debugger can be used instead of the Diagnostics

window.

The utilization of the Microsoft Script Debugger is described in chapter "Testing with

the Debugger".

The Microsoft Script Debugger is located in the Microsoft Download-Center under the following

URL:

● http://www.microsoft.com/downloads/Search.aspx?displaylang=en (

http://

www.microsoft.com/downloads/Search.aspx?displaylang=en)

Use the "Search" field to search for "Script Debugger" and select the required download.

See also

Testing with the Debugger (Page 90)

GSC Runtime (Page 87)

GSC Diagnostics (Page 84)

Microsoft Download Center (http://www.microsoft.com/downloads/Search.aspx?

displaylang=en)

1.12.2 GSC Diagnostics

1.12.2.1 GSC Diagnostics

Introduction

GSC Diagnostics displays the chronological sequence of calls of the trace methods contained

the actions in the Diagnostics window. This also applies to Trace instructions in procedures

which are called in actions. The targeted implementation of Trace instructions, e.g. for the

output of tag values, enables the progress of actions and the procedures called in them to be

traced.

Application

In order to use GSC Diagnostics, insert a GSC Diagnostics type application window in a

process screen. The GSC Diagnostics attributes can be used to control the appearance of the

GSC Diagnostics window.

In the case of a picture change, the content of the GSC Diagnostics window is deleted.

Note

Messages are also displayed in the "GSC Diagnostics" window when the debugger is

activated.

VBS for Creating Procedures and Actions

1.12 Diagnostics

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

System Manual, 11/2008,

See also

GSC Diagnostics Toolbar (Page 86)

GSC Diagnostics Attributes (Page 86)

Inserting the GSC Diagnostics Window into a Picture (Page 85)

1.12.2.2 Inserting the GSC Diagnostics Window into a Picture

Introduction

In order to use GSC Diagnostics, insert a GSC Diagnostics process screen. The process

screen

can be an existing picture or a picture which serves customized diagnostics purposes.

GSC Diagnostics cannot be inserted directly in the process screen as an application but is

inserted as an application in an application window. In this case, the application window is a

component part of the process screen.

Requirements

Graphics Designer has been started and the process screen is open.

Procedure

1. Use the "Smart Objects" object palette to insert the "Application Window" in the picture.

2. Select the "Global Script" option from the "Window Contents" dialog and confirm the

selection with "OK".

3. Select the "GSC Diagnostics" option from the "Templates" dialog.

4. Confirm the selection with OK in order to insert the Diagnostics window.

See also

GSC Diagnostics Toolbar (Page 86)

GSC Diagnostics Attributes (Page 86)

GSC Diagnostics (Page 84)

VBS for Creating Procedures and Actions

1.12 Diagnostics

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

System Manual, 11/2008,

1.12.2.3 GSC Diagnostics Attributes

Overview

GSC Diagnostics has attributes which affect the appearance of the GSC Diagnostics window

in Runtime. These relate to the geometric attributes, particularly to the following:

● Display: This attribute defines whether the window should be visible or hidden. The attribute

can be made dynamic with the name Visible.

● Sizeable: This attribute defines whether the size of the window should be changeable in

Runtime.

● Movable: This attribute defines whether the window should be moveable or not during

Runtime.

● Border: This attribute defines whether the without is provided with a border. If the window

has a border, its height and width can be modified in Runtime.

● Title: This defines whether the window has a title bar.

● Can be maximized: This attribute defines whether the title bar should contain the button to

maximize the window.

● Can be closed: This attribute defines whether the title bar should contain the button to close

the window.

● Foreground: This attribute defines whether the window should always be in the foreground.

See also

GSC Diagnostics Toolbar (Page 86)

Inserting the GSC Diagnostics Window into a Picture (Page 85)

GSC Diagnostics (Page 84)

1.12.2.4 GSC Diagnostics Toolbar

Overview

The GSC Diagnostics toolbar enables the output in the diagnostics window to be controlled

and to save, print and open window content:

1: Delete the content of the diagnostics window

2: Stop the window being updated

3: Activate the window being updated

4: Opens a text file in the window

VBS for Creating Procedures and Actions

1.12 Diagnostics

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

System Manual, 11/2008,

5: Saves the window contents in a text file

6: Print the window contents

See also

GSC Diagnostics Attributes (Page 86)

Inserting the GSC Diagnostics Window into a Picture (Page 85)

GSC Diagnostics (Page 84)

1.12.3 GSC Runtime

1.12.3.1 GSC Runtime

Introduction

GSC Runtime is a window which displays the dynamic behavior of all Global Script actions in

Runtime.

In addition, GSC Runtime can also be used during Runtime to influence the execution

of each individual action and provide access to the Global Script editor.

Actions

C actions and VBS actions are differentiated in the GSC Runtime window:

●

Symbolizes a C action

●

Symbolizes a VBS action

The following information is issued:

● Action name: The name of the action

● ID: Action ID. They are used internally by the system. GSC Runtime supplies the

corresponding action name together with the Action ID. The link between ID and action

name is only valid until Runtime is stopped or, during Runtime, until an action is saved.

● Status: Provides information on the current status of the action. Refer to the table below

for the possible statuses.

● Activation Interval: The time in the form Hour:Minute:Second, which should elapse between

the action being called.

● Return Value: The return value of the action

● Started On: Date and time the current action was started

● Next Start: Date and time the action will be started again

● Error message: Contains the error text in the case of an error

VBS for Creating Procedures and Actions

1.12 Diagnostics

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

System Manual, 11/2008,

Actions Status

Possible action status:

● Action was activated.

● Action was deactivated

● Action was stopped.

● Action in progress

● Error logging on the action!

● Error executing the action!

Pop-Up Menu

The following functions are available for every action in the pop-up menu:

● Log off: The relevant action will not be executed again when the current execution has

finished.

● Log on: The relevant action will be executed again when the next trigger event occurs

● Start: The relevant action will be executed once.

● Edit: The relevant action will be opened in the Global Script editor for editing. Runtime will

remain active. If the edited action is compiled (when necessary) and saved the changes

will be applied by the Runtime system immediately.

The option of opening the pop-up menu for every action can be controlled by assigning an

authorization.

In order to use GSC Runtime, insert a GSC Runtime type application window in a process

screen. The GSC Runtime attributes can be used to control the appearance of the GSC

Runtime window.

Note

Updating the GSC Runtime window increases the system load. The system load is dependent

how many actions are visible in the window. The system load can be lowered by reducing

the height of the window so that fewer lines are visible.

See also

Inserting the GSC Runtime Window into a Picture (Page 88)

GSC Runtime Attributes (Page 89)

1.12.3.2 Inserting the GSC Runtime Window into a Picture

Introduction

In order to use GSC Runtime, insert a GSC Runtime process screen. The process screen can

be an existing picture or a picture which serves customized diagnostics purposes. GSC

VBS for Creating Procedures and Actions

1.12 Diagnostics

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

System Manual, 11/2008,

Runtime cannot be inserted directly in the process screen but is inserted as an application in

application window. In this case, the application window is a component part of the process

screen.

Requirements

Graphics Designer has been started and the process screen is open.

Procedure

1. Use the "Smart Objects" object palette to insert the "Application Window" in the picture.

2. Select the "Global Script" option from the "Window Contents" dialog and confirm the

selection with "OK".

3. Select the "GSC Runtime" option from the "Templates" dialog.

4. Confirm the selection with OK in order to insert the Diagnostics window.

See also

GSC Runtime (Page 87)

GSC Runtime Attributes (Page 89)

1.12.3.3 GSC Runtime Attributes

Overview

GSC Runtime has attributes which affect the appearance of the GSC Runtime window in

Runtime. These relate to the geometric attributes, particularly to the following:

● Display: This attribute defines whether the window should be visible or hidden. The attribute

can be made dynamic with the name Visible.

● Sizeable: This attribute defines whether the size of the window should be changeable in

Runtime.

● Movable: This attribute defines whether the window should be moveable or not during

Runtime.

● Border: This attribute defines whether the without is provided with a border. If the window

has a border, its height and width can be modified in Runtime.

● Title: This defines whether the window has a title bar.

● Can be maximized: This attribute defines whether the title bar should contain the button to

maximize the window.

● Can be closed: This attribute defines whether the title bar should contain the button to close

the window.

● Foreground: This attribute defines whether the window should always be in the foreground.

VBS for Creating Procedures and Actions

1.12 Diagnostics

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

System Manual, 11/2008,

See also

GSC Runtime (Page 87)

Inserting the GSC Runtime Window into a Picture (Page 88)

1.12.4 Testing with the Debugger

1.12.4.1 Testing with the Debugger

Overview

A debugger can be used to test the VBScripts in Runtime, e.g.:

● Microsoft Script Debugger (runs with Windows 2000 and Windows XP)

● Debugger "InterDev" (contained in scope of installation material supplied with Developer

Studio )

● Microsoft Script Editor (MSE) Debugger (contained in material supplied with Microsoft

Office)

The following description relates exclusively to handling the Microsoft Script Debugger.

Download the Microsoft Script Debugger

The Microsoft Script Debugger is located in the Microsoft Download-Center under the following

URL:

● http://www.microsoft.com/downloads/Search.aspx?

displaylang=en833a6a92-961e-4ce1-9069-528d22605127

Use the "Search" field to search for "Script Debugger" and select the required download.

Notes on the MSE Debugger

The following settings must be changed when using the MSE Debugger so that the running

processes will be displayed:

1. Select the "Properties" button in the "Processes" window.

2. Activate the option "Just-In-Time-Debugging" in the "Debuffer properties" dialog.

3. Restart the computer.

4. Deactivate the "Disable script debugging" option in the MS Internet Explorer so that the

Internet Explorer cannot prevent the WinCC debugging procedure.

VBS for Creating Procedures and Actions

1.12 Diagnostics

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

System Manual, 11/2008,