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

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

See also

Principles of Debugging (Page 93)

Executing Script Commands (Page 107)

How to Determine and Modify Tag and Property Values (Page 106)

How to Set Bookmarks in Scripts (Page 105)

Deleting Breakpoints (Page 104)

Setting Breakpoints (Page 103)

Processing Scripts Step-by-Step (Page 102)

Selecting a Script for Editing (Page 100)

Action and Procedure Names in the Debugger (Page 99)

Structure of VBScript Files (Page 97)

Components of the Microsoft Script Debuggers (Page 95)

How to Activate the Debugger (Page 91)

Diagnostics (Page 83)

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

displaylang=en)

1.12.4.2 How to Activate the Debugger

Principle

There are several ways of activating the debugger:

● Automatic activation of the debugger when an error occurs in Runtime.

● Opening an error box in Runtime via which the debugger can be activated.

● Starting the debugger from the Start menu and opening a running Runtime scripts.

Requirements

The Microsoft Script Debugger must be installed on the configuration computer.

Procedure

The following procedure describes the first two points, activating the debugger in WinCC.

1. In the computer's pop-up menu in WinCC Explorer, select the command "Properties". The

"Computer Properties" dialog appears.

2. Select the "Runtime" tab control.

VBS for Creating Procedures and Actions

1.12 Diagnostics

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

System Manual, 11/2008,

3. Activate the required debug options. The debug behavior for actions in Global Script and

Graphics Designer can be set independently of each other:

4. Select "Start debugger" when the debugger should be started directly following an error in

the Runtime.

5. Select "Display Error Dialog", if you do not want to start the Debugger directly but wish to

display

an error dialog with information about the error. The debugger can be started from

the error box by means of a button.

6. Click OK to confirm your entries.

Starting the Debugger and Opening a Running Script

The debugger can also be started up later and linked to the system currently running. Define

connection in the debugger to the respective processes, "pdlrt.exe" for the Graphical Runtime

System and "gscrt.exe" for the Global Runtime System. The way to open a running script in

the debugger is described under the topic "Select Script".

Exiting the Debuggers

It is possible to stop the debugger without exiting the WinCC Runtime.

VBS for Creating Procedures and Actions

1.12 Diagnostics

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

System Manual, 11/2008,

See also

How to Set Bookmarks in Scripts (Page 105)

Executing Script Commands (Page 107)

How to Determine and Modify Tag and Property Values (Page 106)

Deleting Breakpoints (Page 104)

Setting Breakpoints (Page 103)

Processing Scripts Step-by-Step (Page 102)

Selecting a Script for Editing (Page 100)

Action and Procedure Names in the Debugger (Page 99)

Structure of VBScript Files (Page 97)

Components of the Microsoft Script Debuggers (Page 95)

Principles of Debugging (Page 93)

Testing with the Debugger (Page 90)

Diagnostics (Page 83)

1.12.4.3 Principles of Debugging

Introduction

The Microsoft Script Debugger can be used to debug the VBScripts. The Microsoft Script

Debugger can be used to:

● View the script source code to be debugged

● Step-by-step processing of the scripts to be checked

● Display and modify tag and property values

● View and monitor the script progress

Note

Please note that the code displayed in the debugger is write-protected. The code cannot

be changed directly in the debugger but only test the necessary changes.

Error types

A distinction is made between the following types of error by the debug:

Syntax errors

Syntax errors occur, for example, when a key word is written incorrectly or a parenthesis is

not closed. When a syntax check from WinCC is used, syntax errors can be excluded before

testing the scripts in Runtime. In principle, only syntactically correct scripts can be saved in

Graphics Designer. The WinCC syntax check also checks:

VBS for Creating Procedures and Actions

1.12 Diagnostics

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

System Manual, 11/2008,

● Whether the procedure names are unique in Global Script

● Whether an action module in Global Script contains only one procedure

● Whether the action part in Graphics Designer contains only one procedure

As a result of the syntax check in WinCC, the script is parsed without being executed. The

script

is parsed again directly before executing in Runtime. All the script parts are parsed, even

those which are executed after a certain action has been executed at a later time.

If the script contains syntax errors, the script is not executed in Runtime.

Runtime error

A Runtime error occurs when an attempt is made to execute an invalid/erroneous action, e.g.

because a tag has not been defined. In order to intercept Runtime errors, use the "On Error

Resume Next" command in the VBScript. The command causes the subsequent command to

be executed following a Runtime error. The error code can subsequently be checked using

the Err object. In order to deactivate the processing of Runtime errors in the script, use the

"On Error Goto 0" command.

Logical errors

The debugger is particularly helpful in clearing up logical errors. A logical error occurs when

an unexpected result is received because, for example, a condition was incorrectly checked.

To clear logical errors, go through the scripts step-by-step in order to detect the part which

does not function properly.

Basic Procedure

When an error has occurred and the debugger is open, the script appears in a window, write-

protected. It is possible to navigate through the script document, set breakpoints, execute the

script again in Runtime and to process the script step-by-step.

The most important steps for successful debugging of the scripts are described under

"Processing Scripts Step-by-Step".

The source codes of the scripts cannot be edited directly in the scripts. When an error has

been detected, the error can be corrected in the original script in WinCC, e.g. load the picture

again and update it in the debugger.

Note

Tips and tricks for debugging, frequently occurring error codes and other information is

available in the Microsoft Script Debugger online help.

Change Picture During Debug

If a picture change is executed during debugging, the script document of the "old" picture

remains open but is no longer valid. If necessary, invalid errors are displayed because the

objects called following the picture change are no longer available.

VBS for Creating Procedures and Actions

1.12 Diagnostics

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

System Manual, 11/2008,

See also

Testing with the Debugger (Page 90)

Executing Script Commands (Page 107)

How to Determine and Modify Tag and Property Values (Page 106)

How to Set Bookmarks in Scripts (Page 105)

Deleting Breakpoints (Page 104)

Setting Breakpoints (Page 103)

Processing Scripts Step-by-Step (Page 102)

Selecting a Script for Editing (Page 100)

Action and Procedure Names in the Debugger (Page 99)

Structure of VBScript Files (Page 97)

Components of the Microsoft Script Debuggers (Page 95)

How to Activate the Debugger (Page 91)

Diagnostics (Page 83)

1.12.4.4 Components of the Microsoft Script Debuggers

Introduction

The Microsoft Script Debugger offers several components which assist in debugging:

"Command Window"

The "Command Window" is called in using the "View" > "Command Window" menu commands.

While a script is running in Runtime, the "Command Window" of the debugger can be used,

for

example, to compile and modify values of tags and properties in the script currently running.

Changes made in the "Command Window" are effected directly in the running script so that

planned changes can be tested immediately.

The following actions can be executed in the "Command Window":

● Enter commands: Commands can be entered and executed directly in VBScript.

● Change tag values: Tag values can be compiled and modified directly in the "Command

Window". This relates to both tags in the current script as well as global tags.

● Modify properties: It is possible to read and write the properties of all objects in the current

script context.

The "Command Window" can always be used when a script has reached a breakpoint or a

skip has been made from a breakpoint to other commands.

VBS for Creating Procedures and Actions

1.12 Diagnostics

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

System Manual, 11/2008,

Note

Please note that the changes executed in the "Command Window" have no effect on the

source code of the script but only serve for test purposes in the debugger.

"Running Documents" Window

The "Running Documents" window is called via the "View" > "Running Documents" menu

command.

This window displays all the scripts currently running in WinCC Runtime, separated according

scripts, from Global Script ("Global Script Runtime") and scripts from the graphical Runtime

system ("PDLRT"). All the running Global Script Runtime actions and modules are displayed.

In the graphical Runtime system, the scripts are separated according to trigger-controlled

actions (picturename_trigger) and event-controlled actions (picturename_events).

"Call Stack" Window

The "Call Stack" window is called via the "View" > "Call Stack" menu command.

This window displays a list of all running actions and called procedures. When a procedure is

called, for example, the name is added to the "Call Stack" list. When the procedure has finished,

the name is removed from the list. A procedure can be selected from the list in order to skip

to the corresponding position in the script document at which the procedure was called.

See also

Executing Script Commands (Page 107)

How to Determine and Modify Tag and Property Values (Page 106)

How to Set Bookmarks in Scripts (Page 105)

Deleting Breakpoints (Page 104)

Setting Breakpoints (Page 103)

Processing Scripts Step-by-Step (Page 102)

Selecting a Script for Editing (Page 100)

Action and Procedure Names in the Debugger (Page 99)

Structure of VBScript Files (Page 97)

Principles of Debugging (Page 93)

How to Activate the Debugger (Page 91)

Testing with the Debugger (Page 90)

Diagnostics (Page 83)

VBS for Creating Procedures and Actions

1.12 Diagnostics

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

System Manual, 11/2008,

1.12.4.5 Structure of VBScript Files

Principle

In order not to hinder the simultaneous processing of cyclic and event-driven scripts in the

graphical Runtime system, the event-driven actions and cyclic/tag-driven actions are strictly

separated during processing. In this way, a cyclic action, for example, cannot hinder the

execution of an action initiated by clicking a button.

To ensure this, the event-driven actions and the cyclic/tag-driven actions are stored in separate

script files when saving a picture. If a global picture section has been defined in actions in

Graphics

Designer, this is copied into both scripts. In the same way, modules which are used

in an action are also copied in both script files.

If a tag from a module should be used, the corresponding module must be called in. Otherwise,

the module is not copied in the script file and an error is generated.

Note

Since the two script files are handled separately, they have no common data area. Therefore,

there is no synchronization of global tags between the two script files. If synchronization is

required, implement this using the DataSet object or internal WinCC tags.

Structure of the Script Files

When scripts are debugged with a debugger, the script files always open the different Runtime

systems.

In the case of the graphical Runtime system, this means that you receive two script files per

picture:

● <Bildname>.pdl_events: Contains the event-driven actions.

● <Bildname>.pdl_triggers: Contains the cyclic and tag-controlled actions.

The following section describes how the script files are structured:

Graphical Runtime system

VBS for Creating Procedures and Actions

1.12 Diagnostics

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

System Manual, 11/2008,

Global Script Runtime

Note

Please note that the actions and procedures of the graphic Runtime system are not displayed

with the action name in the script file under which it was saved in WinCC. The name

conventions for actions and procedures in the script files sate described in "Action and

Procedure Names in the Debugger".

See also

How to Activate the Debugger (Page 91)

Executing Script Commands (Page 107)

How to Determine and Modify Tag and Property Values (Page 106)

How to Set Bookmarks in Scripts (Page 105)

Deleting Breakpoints (Page 104)

Setting Breakpoints (Page 103)

Processing Scripts Step-by-Step (Page 102)

Selecting a Script for Editing (Page 100)

Action and Procedure Names in the Debugger (Page 99)

Components of the Microsoft Script Debuggers (Page 95)

Principles of Debugging (Page 93)

Testing with the Debugger (Page 90)

Diagnostics (Page 83)

VBS for Creating Procedures and Actions

1.12 Diagnostics

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

System Manual, 11/2008,

1.12.4.6 Action and Procedure Names in the Debugger

Action and Procedure Names in the Debugger

The names of procedures and actions in debugger script files differ from the names under

which they were saved by the scripts in WinCC.

The action and procedure names in the script files are compiled according to the following

rules:

Action type Name of the script file

Cyclic or tag-driven actions on a property ObjectName_PropertyName_Trigger

Mouse events ObjektName_OnClick

ObjektName_OnLButtonDown

ObjektName_OnLButtonUp

ObjektName_OnRButtonDown

ObjektName_OnRButtonUp

Keyboard events ObjektName_OnKeyDown

ObjektName_OnKeyUp

Object events

ObjektName_OnObjectChanged

ObjektName_OnSetFocus

Events on properties ObjektName_PropertyName_OnPropertyChanged

ObjektName_PropertyName_OnPropertyStateCha

nged

Picture events Document_OnOpen

Document_OnClosed

Permitted length of action names

The names of the actions in the script files are limited to 255 characters. Each special character

used

in an object name is converted to five characters. The special characters are represented

by a four-place hexadecimal code behind the preceding X. If, for example, an action is

configured on a button with the name "PushHere" per mouse click, the script in the script file

appears as "PushHere_OnClick".

If the object name compiled is too long, an error message is issued during the syntax check

in WinCC. As a result of this restriction, graphic object names cannot be selected with any

length during configuration.

VBS for Creating Procedures and Actions

1.12 Diagnostics

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

System Manual, 11/2008,

Note

If you wish to determine the name of an object in Runtime, press <CTRL+ALT+SHIFT> and

position the mouse over the corresponding object. The picture name and object name then

appears in a tooltip.

See also

Executing Script Commands (Page 107)

How to Determine and Modify Tag and Property Values (Page 106)

How to Set Bookmarks in Scripts (Page 105)

Deleting Breakpoints (Page 104)

Setting Breakpoints (Page 103)

Processing Scripts Step-by-Step (Page 102)

Selecting a Script for Editing (Page 100)

Structure of VBScript Files (Page 97)

Components of the Microsoft Script Debuggers (Page 95)

Principles of Debugging (Page 93)

How to Activate the Debugger (Page 91)

Testing with the Debugger (Page 90)

Diagnostics (Page 83)

1.12.4.7 Selecting a Script for Editing

Introduction

If the Microsoft Script Debugger is called from the Windows Start menu instead of automatic

activation using WinCC, scripts which are currently running can be called in for editing in

Runtime.

Prerequisite

Runtime is activated, the picture to be debugged is active.

VBS for Creating Procedures and Actions

1.12 Diagnostics

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

100

System Manual, 11/2008,