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

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

1.9.6 Protecting a Module with a Password

Introduction

A module can be assigned a password to protect it from unauthorized access. The password

is a part of the module-related information.

Note

If a module is protected by a password, all the procedures contained in it are also protected

by the password.

Procedure

1. Open Global Script.

2. Select the module to be assigned a password in the navigation window.

Click the button "Info/Trigger" in the toolbar or choose the pop-up menu command "Info".

The "Properties..." dialog appears.

Activate the check box "Password".

The dialog "Enter Password" is displayed.

5. Enter a password and confirm it.

6. Confirm your settings with OK.

Result

If an attempt is made to open the module or a procedure contained in it, a prompt appears

requesting the password.

Deactivate Password Protection

To clear the password protection, disable the "Password" check box.

Change Password

To change the password, open in the Properties dialog and click the "Change" button. Then

enter the new password.

NOTICE

If you forget the module password, the module cannot be edited.

VBS for Creating Procedures and Actions

1.9 Creating and Editing Procedures

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

System Manual, 11/2008,

Note

The "Info/Trigger" dialog can also be called if an open procedure is selected in the navigation

window.

The information stored in this dialog is always valid for the entire module and all the

procedures contained in it.

See also

Multiple Use of Procedures and Actions (Page 23)

Renaming a Procedure or Module (Page 54)

Saving a Procedure (Page 52)

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)

Modules and Procedures (Page 18)

Creating and Editing Procedures (Page 39)

1.9.7 Saving a Procedure

Introduction

Individual procedures are never stored but the module in which the procedure has been

programmed.

Before saving a module, check the code is syntactically correct. When saving a module, the

procedures contained are automatically checked and, in the case of syntax errors, a prompt

appears as to whether the module should be saved with the errors or not. In this way, for

example,

modules and procedures can be saved which are not fully programmed. Syntactically

incorrect procedures do not run in Runtime.

NOTICE

If a module contains a syntactically incorrect procedure, the module can no longer be loaded.

Procedures can no longer be called from the module.

VBS for Creating Procedures and Actions

1.9 Creating and Editing Procedures

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

System Manual, 11/2008,

Note

The syntax check can only detect syntax errors in the code. Programming errors, such as

missing references, only become visible in Runtime. Therefore, always check the scripts in

the Runtime environment and use a debugger, if necessary, to detect and eliminate errors.

Only syntactically correct modules are called in Runtime.

A list of all the possible syntax errors is available in the Appendix under " Basic Principles of

VBScript".

If a procedure is subjected to a syntax check prior to saving, any errors are displayed in the

lower

part of the editor window. Double click on an error line to access the error position in the

code directly.

Use the "Save As" command to store the module under another name. Note that the new

module is only displayed in the navigation window after updating the view.

Requirements

The procedure/module to be saved must be open in the editor window.

Procedure

Click the button "Syntax Check" in the toolbar.

2. If syntax errors appear in the output window, double click on the error line and correct the

error in the code. Repeat steps 1 and 2 until the code is correct.

Save the module by clicking "Save" in the toolbar.

See also

Diagnostics (Page 83)

Multiple Use of Procedures and Actions (Page 23)

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)

Modules and Procedures (Page 18)

Creating and Editing Procedures (Page 39)

VBS for Creating Procedures and Actions

1.9 Creating and Editing Procedures

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

System Manual, 11/2008,

1.9.8 Renaming a Procedure or Module

Introduction

Procedures and modules are renamed in the following cases:

● When a standard name (procedure# or Modul#), which was automatically assigned when

the new module/new procedure was created, is changed to a self-explanatory name.

● When a module or procedure is copied in order, for example, to create a new module with

See also

Multiple Use of Procedures and Actions (Page 23)

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)

Modules and Procedures (Page 18)

Creating and Editing Procedures (Page 39)

1.10 Creating and Editing Actions

1.10.1 Creating and Editing Actions

Introduction

When using VBS in WinCC, there is no differentiation between local (valid for entire project)

and global (valid on all computers) actions, as opposed to C. A configured action is always

valid globally.

A copied action is available for use in Runtime following a restart or opening and saving the

action. The become visible in the editor when the view is updated.

VBS actions can be used in to make graphic objects and object properties dynamic in Runtime

or to execute picture-independent actions.

Note

Please note that the object name length of objects made dynamic in Graphics Designer is

limited to approx. 200 characters, and each special character used in an object name is

converted to five characters in the script files. The special characters are represented by a

four-place

hexadecimal code behind the preceding X. If the name of an object made dynamic

is too long, a corresponding error message appears. Further information is available in this

help under "Structure of VBScript Files".

NOTICE

If you make an object property dynamic with a VBS action via the return value of a script, the

value of the object property is written only if it has changed in relation to the last script run.

It is not considered if the value had been changed from another location.

Therefore it is illegal to change properties which have been made dynamic by VBS action

via the return value from another location (e.g., other C scripts or VBS scripts).

VBS for Creating Procedures and Actions

1.10 Creating and Editing Actions

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

System Manual, 11/2008,

if you do not observe this, wrong values can be the results.

Using the Actions

Actions can be used as follows:

On graphic objects in Graphics Designer

Making properties dynamic (action with return value), e.g.:

Function BackColor_Trigger(ByVal Item)

'VBS143

BackColor_Trigger = RGB(125,0,0)

End Function

Triggered by an event on an object (action without return value), e.g.:

Sub OnClick(ByVal Item)

'VBS144

Item.BackColor = RGB(255,0,0)

End Sub

Picture-independent in Global Script

As a cyclic action, e.g. incrementing a tag:

Option Explicit

Function action

'VBS145

Dim objTag1

Dim lngValue

Set objTag1 = HMIRuntime.Tags("Tag1")

lngValue = objTag1.Read

objTag1.Write lngValue + 1

action = CLng(objTag1.value)

End Function

VBS for Creating Procedures and Actions

1.10 Creating and Editing Actions

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

System Manual, 11/2008,

Executing Actions

An action can be assigned several triggers. The action is always executed when one of the

triggering events occurs. Observe the following:

● Actions in Global Script cannot be executed simultaneously. The action triggered last is

held in a queue until the action currently being performed is completed.

● When using Graphics Designer, cyclically and tag-driven actions cannot be triggered

simultaneously. If the execution of a tag-driven action hinders the execution of a cyclic

action, the cyclic action is executed when the tag-driven action has finished. The cyclic

action is held in a queue during the non-execution phase. When the current action is

completed, the cyclic action is executed with the normal cycle.

● In Graphics Designer, event-driven actions cannot be executed simultaneously.

The action types mentioned do not prevent each other being executed: The execution of

actions in Global Script has no influence on actions in Graphics Designer. In the same way,

in Graphics Designer, the execution of cyclically or tag-driven actions has no effect on the

execution of event-driven actions.

Note

Actions in pictures which are still running one minute after the picture has been deselected

are terminated by the system. This is recorded in a logfile entry.

Locating Actions

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.10 Creating and Editing Actions

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

System Manual, 11/2008,

Procedure - Action Restrictions

Actions can be used to program instructions and call procedures. Codes are programmed

within

in procedures for use at several points in a configuration. Contrary to procedures, actions

always have a trigger.

Creating and Editing Actions

Actions can be configured in Global Script and Graphics Designer. Use Global Script to

configure global actions which can be executed independently of the picture currently open.

Graphics Designer is used to configure actions related to graphic objects which should be

executed when the picture is opened in Runtime or when the configured trigger occurs.

The script editors in WinCC provide the option of checking that scripts have a correct syntax

without executing them. Errors in the script are displayed in the output window under the editor

window. Double click on the corresponding error line to access the related point in the code.

Note

The syntax check can only check objects known to the system at the moment of execution.

Therefore, the tags and objects addressed in the scripts must be created in WinCC.

Only syntactically correct actions are executed in Runtime.

The automation objects "PDLRuntime" and "WinCC Runtime Project" cannot be used in VBS

actions.

Display of Actions

If you save a syntactically incorrect action, it will be displayed in the navigation window with

this adjacent symbol.

VBS for Creating Procedures and Actions

1.10 Creating and Editing Actions

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

System Manual, 11/2008,

If you save a syntactically correct action without trigger, it will be displayed in the Global

Script navigation window with this adjacent symbol.

If you save a syntactically correct action with trigger, it will be displayed in the Global Script

navigation window with this adjacent symbol.

Note

Actions can only be saved in the Graphics Designer if they have the correct syntax. If an

action with errors should still be retained and exited, however, enter the comments.

System behavior if actions are changed, deleted and saved at Runtime

If a local action is stored at runtime, then all local and global actions of the computer are reset

on the computer to which the local action belongs.

If a global action is stored during runtime, then all local and global actions for the entire project

– and thus on all computers – are reset.

Such a reset might reinitialize for examples tags and times that are used as triggers for actions,

triggering the action at that stage.

Static tags used in the reset actions are reinitialized.

See also

Structure of VBScript Files (Page 97)

Action and Procedure Names in the Debugger (Page 99)

How to Rename an Action (Page 81)

Saving Actions (Page 67)

Protecting an Action with a Password (Page 66)

How to add information to the action (Page 64)

How to Edit Actions (Page 61)

Creating a New Action (Page 59)

Triggers (Page 69)

Actions (Page 21)

1.10.2 Creating a New Action

Introduction

When a new action is created, the editor automatically suggests a file name (Action#.bac),

which can be changed.

Actions can be configured in Global Script and Graphics Designer.

VBS for Creating Procedures and Actions

1.10 Creating and Editing Actions

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

System Manual, 11/2008,

● Global Script is used to configure actions which can be executed, picture-independently,

in Runtime. Open Global Script via WinCC Explorer.

● Graphics Designer is used to configure a new action, related to the properties of a graphic

object,

by clicking on the right mouse button in the "Dynamic" column of the Properties tab

control and selecting VBS Action. An action, related to an event, is created in the same

ways using the Events tab control.

In both cases, the Action Editor of the Graphics Designer opens.

Note

The precise procedure for linking actions with graphic objects is described under the WinCC

help topic "Dynamics".

Procedure

1. Open Global Script.

2. Activating the Actions Tab Control in the Navigation Window.

Click the adjacent button in the tool bar or choose the menu command "File" > "New" >

"Action".

A new action is opened in the editor window. The action appears in the navigation window

after it has been saved.

Note

When creating a new action, the "Option explicit" instruction is automatically entered in the

declaration area and cannot be deleted. The instruction is necessary as it prevents errors

caused by the incorrect notation of tags without declaration.

The instruction requires that tags are always defined in your code with the "Dim" instruction.

Do not use the "Option explicit" instruction in the code because it may cause Runtime errors.

See also

How to Rename an Action (Page 81)

Saving Actions (Page 67)

Protecting an Action with a Password (Page 66)

How to add information to the action (Page 64)

How to Edit Actions (Page 61)

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,