4.3 Configuring the WebNavigator system
4.3.4 Differences to the WinCC Basic System
Introduction
The WebNavigator has certain functional restrictions compared to the WinCC basic system.
You should therefore check your WinCC projects for these restrictions and adjust the project settings as required.
Overview
When you use functions that are not supported in a project, corresponding messages are generated in Runtime to draw your attention to the fact.
The following restrictions apply to the WebNavigator Client:
● The client provides only a view of the running WinCC project.
It is not possible to configure the WinCC Server projects.
● You can only use WinCC options and WinCC add-ons if specified explicitly in the documentation.
● Not all "Runtime API functions" are supported.
A list of supported functions is available at "Supported functions (Page 150)".
● For information on restrictions in combination with Basic Process Control, refer to "Options for Process Control > Overview of process control system options > Configuring in the PCS 7 environment > Web Client in the WinCC Information System.
● The WinCC reporting system is not supported. This means that reports can only be output on the Web Navigator Server and WinCC Client.
● You cannot use the print function in the WinCC Controls.
Instead, use the WinCC hardcopy function to print. You can find out how to use the hardcopy WinCC/WebNavigator Documentation 4.3 Configuring the WebNavigator system
● The "WinCC Alarm Control" function does not support the "triggers an action" property for a message.
For the correct display of message blocks, the "Apply project settings" option cannot be activated. You can find this option on the "Message blocks" tab of the "WinCC AlarmControl"
properties dialog.
● The hotkeys configured in WinCC are not supported.
Operator control using the tab key is supported.
● The following objects contained in the "Global library/Operation/Operating panels" folder of the WinCC shared library are not supported:
– 1_Slider – 2_Slider – 4_Slider
● National special characters in names of process pictures or referenced graphics are not supported on the Internet.
● The overlap lock in process pictures is not supported.
● The advanced zoom functions cannot be disabled. If you do not want to employ the zoom functions, do not use a wheel mouse with "auto-scroll" setting on the client.
● The redundancy switch is only supported on the dedicated web server.
4.3.4.2 Using Scripts
Scripts running exclusively for the WebNavigator
In order to execute scripts only for the WebNavigator, use the pre-processor definition
"RUN_ON_WEBNAVIGATOR" in the script. For example:
void OnOpenPicture (char* lpszPictureName, char* lpszObjectName, char* lpszPropertyName)
{
#ifdef RUN_ON_WEBNAVIGATOR
// here you enter the code that is to be executed only in the WebNavigator
#else
// here you enter the code that is executed only in the WinCC basic system
#endif }
Visual Basic Script
There are only slight restrictions imposed by unsupported functions when VBS is used. A list of these functions is available at "Unsupported functions (Page 160)".
Global Script
You configure the scripts on the WinCC Server in the server project.
4.3 Configuring the WebNavigator system
WinCC/WebNavigator
122 System Manual, 07/2013, A5E32316269-AB
Global scripts cannot be executed on the WebNavigator Client. Global Scripts on the server are supported.
The scripts generated using the Dynamic Wizard cannot contain unsupported functions and, therefore, cannot be executed on the WebNavigator Client. Check and correct the scripts, if necessary. Add the following condition, for example: "#ifdef RUN_ON_WEBNAVIGATOR".
Script with trigger tags
The WebNavigator queries tags at cyclic intervals of "1 second". The update cycle of trigger tag "upon change" is also one second.
This may lead to an increased communication load between the AS and WinCC Server. Take increased loads into account if communication between the AS and WinCC Server is operated at load limits.
If tag-triggered scripts request additional tags having a name that is generated using a string function, for example, unknown tags can only be read synchronously. Enter the tag names you are using in the trigger list in order to avoid extended selection times.
Script for picture selection and deselection
In contrast to the basic system, a picture is downloaded in asynchronous mode when WebNavigator is used. Account for this fact when using scripts that contain picture changes.
If a picture selection for a picture window is initiated within a script, you cannot access the objects of the new picture within the same script afterwards. The picture is not yet loaded at this time. A time delay, e.g. "Sleep(2000)" is of no help since the script and Internet Explorer are waiting. You should then execute the next script elements in the "OpenPicture" function that is triggered after the picture is loaded.
Other functions called in the script following a picture deselection will be executed with errors or not at all. The picture context is lost due to the picture deselection.
Synchronous script functions
Synchronous script functions impose a heavy load on the system.
You should therefore refrain from using the "SetTagxxx" function in cyclic scripts. The server will be overloaded when many clients call the "SetTagxxx" functions in a fast cycle, e.g. 1 sec or less.
Note that the following script functions and calls are transferred synchronously to the server:
WinCC/WebNavigator Documentation 4.3 Configuring the WebNavigator system
Picture in picture method and cyclic scripts
Many synchronous calls in a picture may reduce performance, for example, in the following cases:
● More than ten windows are configured in a picture window.
● Cyclic scripts with synchronous calls, for example, "SetTagxxx", are used in the windows.
Execution of certain scripts may fail due to timeout.
The following elements are supported in a window:
● 16 windows with cyclic scripts.
● 31 windows without cyclic scripts.
4.3.4.3 Using tags
Computer-local tags
The WebNavigator Client supports computer-local tags with the following restrictions:
● When a dedicated web server is used, only the computer-local tags of that server are available on the client. The tags on the client cannot assume their own values.
● Computer-local tags of the subordinate WinCC servers cannot have their own values on the client.
● The start value of computer-local text tags can only contain characters that are allowed in tag names. If the start value of a text tag contains a colon, for example, the tag is not recognized on the client.
● Computer-local tags are not supported on the client when User Archives are used, because User Archives can only identify the local tags of the server, but not the tags of the
WebNavigator Client.
Defining picture-local script tags
Do not use WinCC tags for WebNavigator if picture-specific data is stored in scripts.
The reading or writing of data in scripts always generates data traffic to the server. This places a load on the communication.
You can save picture-specific data as follows:
● Configure "hidden" graphic objects so that you can use their properties as picture-specific tags. Actions are executed at the object properties upon changes to the stored values.
● You have created the hidden "static text" object, for example. The "Text" property is used to store any texts, while the color properties are used to store any colors. The properties are read and/or written using scripts and influence the picture status without requiring a roundtrip to the server.
4.3 Configuring the WebNavigator system
WinCC/WebNavigator
124 System Manual, 07/2013, A5E32316269-AB