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

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

What to do

1. Start the debugger from the Windows Start menu ("Start" > "Programs" > "Options" >

"Microsoft Script Debugger").

2. Activate the "View" > "Running Documents" commands from the menu bar.

The "Running Documents" window is opened. This window displays all the scripts currently

running in WinCC Runtime, separated according to scripts, from Global Script ("Global

Script Runtime") and scripts from the graphical Runtime system ("PDLRT").

The example above, "Startbild.pdl" is active and only event-driven scripts are available in

the start picture.

3. Double click on the script document in the "Running Documents" window that is to be

debugged.

The script document is opened "read-only" in the Debugger window.

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)

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)

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,

101

1.12.4.8 Processing Scripts Step-by-Step

Introduction

The Microsoft Script Debugger can be used to process the scripts step-by-step in order, for

example,

to locate logical errors systematically. The effect of each individual script line can be

tested in Runtime.

The Procedure in Principle

1. Activate the document to be debugged in Runtime.

2. Start the debugger manually from the Start menu and open the required script file or activate

the debugger in WinCC. When activated in WinCC, the debugger automatically opens when

an attempt is made to execute an erroneous script.

3. Set a breakpoint in the script file. Breakpoints are normally set in front of code lines in which

errors are suspected.

Switch to WinCC Runtime and trigger an action which causes the script to run.

The Debugger stops at the first breakpoint and marks the current line.

5. In order to go through the script document step-by-step, select one of the following menu

commands:

"Debug"

> "Step Into": Skip to the next code line. If the script calls a procedure in this line,

it skips to the procedure using the "Step Into" command. The procedure called can then be

processed step-by-step.

"Debug" > "Step Over": Skips the procedure called. The procedure is called but the

debugger does not stop at the individual lines of the procedure. Instead, it moves to the

next line of the current script after the procedure has been executed.

6. To interrupt the step-by-step processing of a procedure, select the "Debug" > "Step Out"

menu commands. The debugger then skips to the next action.

7. Proceed step-by-step to the end of the document or select the "Debug" > "Run" menu items

to start the script again in Runtime.

VBS for Creating Procedures and Actions

1.12 Diagnostics

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

102

System Manual, 11/2008,

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)

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)

Testing with the Debugger (Page 90)

Diagnostics (Page 83)

1.12.4.9 Setting Breakpoints

Introduction

Breakpoints can be set in a script to stop at specific points when processing it and to start the

debugger.

Set a breakpoint in front of a line, for example, which you suspect contains a script

error.

It is possible to:

● Set breakpoints at specific lines to locate logical errors in the script step-by-step.

● Set a breakpoint and call the debugger before the next line in the script is processed. These

procedure is used, for example, for events such as "Change picture".

When a script file is updated in the debugger, all the breakpoints are lost.

If a breakpoint is set in one of the script files "<Bildname>.pdl_trigger" or

"<Bildname>.pdl_event", all the trigger-driven or all event-driven procedures are stopped,

respectively, in Runtime.

Requirements

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)

System Manual, 11/2008,

103

Procedure

Setting a breakpoint

1. Start the debugger and select the script. If automatic activation of the debuggers in WinCC

has been selected, the debugger is called in as soon as an erroneous script is executed.

2. Position the cursor on the action in which a breakpoint should be set.

Open the "Debug" menu and select the "Toggle Breakpoint" item or the icon from the

toolbar.

The next executable line will be marked by a red dot.

4. Switch to WinCC Runtime and execute the action you wish to debug.

The Debugger stops at the first breakpoint it finds in the script. The current line is displayed

on a yellow background. The script can then be processed step-by-step.

See also

Deleting Breakpoints (Page 104)

Executing Script Commands (Page 107)

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

How to Set Bookmarks in Scripts (Page 105)

Setting Breakpoints (Page 103)

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)

How to Activate the Debugger (Page 91)

Testing with the Debugger (Page 90)

Diagnostics (Page 83)

1.12.4.10 Deleting Breakpoints

Introduction

When an error has been cleared properly, the breakpoints in a script can be cleared individually

or all together.

VBS for Creating Procedures and Actions

1.12 Diagnostics

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

104

System Manual, 11/2008,

Procedure

1. Position the cursor in the line whose breakpoint is to be deleted.

Open the "Debug" menu and select the "Toggle Breakpoint" item or the icon from the

toolbar.

The next line will be displayed without a mark.

3. To delete all the breakpoints in a script, open the "Debug" menu and select the "Clear all

Breakpoints" entry or the icon from the toolbar.

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)

Setting Breakpoints (Page 103)

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)

How to Activate the Debugger (Page 91)

Testing with the Debugger (Page 90)

Diagnostics (Page 83)

1.12.4.11 How to Set Bookmarks in Scripts

Introduction

During the debug routine, bookmarks can be set on code lines so that they can be found easier

again one line later.

Setting or deleting bookmarks

Position the mouse pointer into the cell where you wish to set a bookmark, and click <CTRL

+F2> to set or delete a bookmark.

Skipping to the next bookmark

Press <F2> to skip to the next bookmark in the script.

VBS for Creating Procedures and Actions

1.12 Diagnostics

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

System Manual, 11/2008,

105

Skipping to the previous bookmark

Press <SHIFT+F2> to skip to the previous bookmark in the script.

See also

Executing Script Commands (Page 107)

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

Deleting Breakpoints (Page 104)

Setting Breakpoints (Page 103)

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)

How to Activate the Debugger (Page 91)

Testing with the Debugger (Page 90)

Diagnostics (Page 83)

1.12.4.12 How to Determine and Modify Tag and Property Values

Introduction

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 or properties in the script currently running.

It is possible, for example, to reset a process value for a script to zero without having to stop

the process.

Note

If you wish to determine the name of a WinCC object in Runtime, click <CTRL+ALT+SHIFT>

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

then appears in a tooltip.

Requirements

The script runs in Runtime and the debugger is opened.

VBS for Creating Procedures and Actions

1.12 Diagnostics

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

106

System Manual, 11/2008,

Procedure

1. Set at least one breakpoint in the current script.

2. Switch to WinCC Runtime and trigger an action which causes the script to be

executed.

The Debugger stops at the first breakpoint.

3. Open the "View" menu and activate the "Command Window" entry.

The "Command Window" opens.

4. In order to determine the value of a tag or property, enter a "?" followed by a Space and

the name of the tag or property whose value is to be determined, e.g. "?myTag".

Press <RETURN> to execute the command.

5. In order to modify the value of a tag/property, assign a value in the VBS syntax.

See also

Principles of Debugging (Page 93)

Executing Script Commands (Page 107)

How to Set Bookmarks in Scripts (Page 105)

Deleting Breakpoints (Page 104)

Setting Breakpoints (Page 103)

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)

Testing with the Debugger (Page 90)

Diagnostics (Page 83)

1.12.4.13 Executing Script Commands

Introduction

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

execute script commands directly and thus manipulate the running of the current script. The

script

commands can be executed directly for test purposes without creating the command in

a script and activating it. It is possible, for example:

● To retrieve methods

● To retrieve procedures

● To manipulate object properties

"Command Window" can basically be used to execute all commands which can also be

executed from a VBScript.

VBS for Creating Procedures and Actions

1.12 Diagnostics

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

System Manual, 11/2008,

107

Requirements

The script runs in Runtime and the debugger is opened.

Procedure

1. Set at least one breakpoint in the current script.

2. Switch to WinCC Runtime and trigger an action which causes the script to be

executed.

The Debugger stops at the first breakpoint.

3. Open the "View" menu and activate the "Command Window" entry.

The "Command Window" opens.

4. Enter the required command and press "ENTER".

Note

If a faulty command is entered in the Command window, no error message is issued in

Runtime. The message "<Script Error> appears in the Command window instead.

See also

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)

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)

How to Activate the Debugger (Page 91)

Testing with the Debugger (Page 90)

Diagnostics (Page 83)

1.13 Printing VBScripts

Principle

The actions and procedures configured in both Global Script and in Graphics Designer can be

documented in WinCC.

VBS for Creating Procedures and Actions

1.13 Printing VBScripts

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

108

System Manual, 11/2008,

The documentation options are distinguished between:

● Print Feedback Doc: In Graphics Designer, all the configured actions are printed with the

feedback of the current picture. The Feed Back contains the C-actions and VBS actions,

located beside each other, differentiated by the source text (C or VBScript).

● Print current script: The Feed Back in Global Script always contains the currently open

procedure or action.

WinCC provided predefined print layouts for the layout of the Feed Back. Customized print

layouts can also be developed and linked to the Print Job tab control with "Project

Documentation - Setup".

Procedure

1. Open Global Script or Graphics Designer according to the scripts to be documented.

2. Configure the print job, if necessary, using the "Project Documentation - Setup" command.

3. Use the "View Project Documentation" command to preview the data to be printed.

4. Select the menu commands "File" > "Print Project Documentation" to print the data.

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.14 VBS Reference

1.14.1 VBS Reference

VBS object model in WinCC

The WinCC object model of the graphic Runtime system enables access to graphic objects

and tags in Runtime.

When you click on an object name, you are shown a detailed description.

VBS for Creating Procedures and Actions

1.14 VBS Reference

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

System Manual, 11/2008,

109

Object and List

VBS for Creating Procedures and Actions

1.14 VBS Reference

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

110

System Manual, 11/2008,