Miscellaneous

The information as to whether a backup is running is stored in the data point element _DataManager(_2).Backup.Status.

The DPE is set by the server which is doing the backup.

When the backup is started, the value 1 is written.

If the backup was completed successfully, the value 0 is written.

A negative value is written if an error occurred during the execution of the backup.

The error codes and their description can be found in the WinCC OA documentation: System Management > Database > Online Backup > Configuration of the backup

Azure IOT Hub has an MQTT interface. It should therefore be possible to connect the Azure IOT Hub using 'sMQTT driver.

Azure IOT Hub provides a web interface which you can connect to by using the existing WinCC OA commands (net*), e.g. netGet() and parsing the answer inside a CTRL script.

A detailed description of the functions can be found in the WinCC OA documentation: CONTROL --> Control functions --> Functions N --> net*.

If you want to know the name of a DP type and only the ID is known you can use the tool WCCOAtoolNameToId.

1. Open a cmd-shell and go to the WinCC OA version/bin - directory
2. Enter the following command: WCCOAtoolNameToId.exe -proj <your projectname> -t <Type ID>

Example: WCCOAtoolNameToId.exe -proj MYPROJECT -t 523

Details can be found within the WinCC OA documentation -> Special Functions -> Identification Caching & DP Identification

If the debug flag -dbg STAT_HISTO is activated, detailed information about the processed value changes and changes to alert instances is reported

The information is written to the log file for the Event Manager.

The interval can be defined with the config entry MessageDiagSecs in the [general] section. The default value is 30 seconds.

The output may slightly differ from WinCC OA version to WinCC OA version.

When the output does not contain all lines described below, the information is still valid for the other lines.

If the output contains more columns then described below, the additional columns must not be taken into account, they are not used.

For every debug three lines of information are written.

• The first line contains information about the value changes in the system.
• The second line contains information about the processed alert instance changes. The information is written in the form of a histogram. Each slot of the histogram has a special meaning.
• The third line contains information about the size of the value changes for a DP element of type string or blob

Value changes

The first column contains the total number of value changes for the last period.

In the following columns detailed information for the latency is reported. The latency is the difference between the value change timestamp and the processing in the Event Manager.

If the value changes due to a dpSet/dpSetWait message, the difference is always 0 because the timestamp is specified by the Event Manager.

If the value is changed in a PLC and the driver provides the timestamp, some latency might be detected. Due to time synchronization there might be negative latency intervals as well, which are counted in a separate slot.

The histogram contains information for following latency intervals:

// slots:
// total number [ 0]
// 0 .. 90 ms [ 1] .. [10]
// 100 .. 900 ms [11] .. [19]
// 1 .. 9 s [21] .. [29]
// 10 .. 90 s [31] .. [39]
// <0.0 [102]
// >= 100s [101]

The log message example shows value changes triggered by a CTRL script running on the same server as the Event Manager. Therefore, no latency is detected.

There are 68 changes in total, and all are detected with a latency of less than 10 ms.

WCCILevent (0), <TIMESTAMP>, STAT_HISTO, "STAT_HISTO, "DPEChanges [10 ms] - decades: total 68 | 
68, 0, 0, 0, 0, 0, 0, 0, 0, 0 | 0, 0, 0, 0, 0, 0, 0, 0, 0 | 0, 0, 0, 0, 0, 0, 0, 0, 0 | 0, 0, 0, 
0, 0, 0, 0, 0, 0 | 0, 0, 0, 0, 0, 0, 0, 0, 0 | >= 100000 0, < 0 0"

Changes of alert instances

The first column contains the total number of changes of alert instances for the last period.

In the following columns detailed information is listed according to the alert type (continuous alarms, multi instance alarms, suppressed alarms) and the alert state.

// ALERTEVENT_CAME (0)
// ALERTEVENT_CAME_IMPULSE (1)
// ALERTEVENT_GONE (2)
// ALERTEVENT_MULTIPLE_ACK (3)
// ALERTEVENT_SINGLE_ACK (4)
// ALERTEVENT_GONE_INACTIVE (5)
// ALERTEVENT_GONE_IMPULSE (6)
// ALERTEVENT_GONE_OBSOLETE (7)
// NOEVENT (8) 

The histogram contains the following slots:

// slots:
// total number [ 0]
// continuous alarms [ 1] .. [10] sorted by AlertEvent constant
// multi instance alarms [11] .. [20] sorted by AlertEvent constant
// suppressed alarms due to minPrio setting [32]
// _alert_hdl config was set active/inactive [33]

1036 alarm changes in total
29 continuous alarms (ALERTEVENT_CAME)
7 continuous alarms (ALERTEVENT_GONE)
1000 multi instance alarms (ALERTEVENT_CAME)

WCCILevent (0), <TIMESTAMP>, STAT_HISTO, "AlarmChanges [#]: total 1036 | 29, 0, 7, 0, 0, 0, 
0, 0, 0, 0 | 1000, 0, 0, 0, 0, 0, 0, 0, 0, 0 | 0, 0, 0, 0, 0, 0, 0, 0, 0, 0| 0, 0, 0, 0, 0, 
0, 0, 0, 0, 0 | 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 | 0, 0, 0, 0, 0, 0, 0,0, 0, 0 | 0, 0, 0, 0, 0, 
0, 0, 0, 0, 0 | 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 | 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 | 0, 0, 0, 0, 0, 
0, 0, 0, 0, 0 | > 10 0, < 0 0"

Size of value changes (strings, blobs)

The first column contains the total number of messages which were counted in the last period.

In the following columns the number of messages is listed according to the size of the message in decades.

The histogram contains information for following message sizes:

// slots:
// total number of messages [ 0]
// 0-1 .. 9-9.99 kB [ 1] .. [10]
// 10-19.99 .. 90-99.99 kB [11] .. [19]
// 100-199.99 .. 900-999.99 kB [20] .. [29]
// 1000-1999.99 .. 9000-9999.99 kB [30] .. [39]
// 10000-19999.99 [40]
// >20000 [41]

WCCILevent (0), <TIMESTAMP>, STAT_HISTO, "Msg Size [kB] - decades: total 56 | 11,
10, 10, 10, 10, 5, 0, 0, 0, 0 | 0, 0, 0, 0, 0, 0, 0, 0, 0 | 0, 0, 0, 0, 0, 0, 0, 0,
0 | 0, 0, 0, 0, 0, 0, 0, 0, 0 | 0, 0, 0, 0, 0, 0, 0, 0, 0 | >= 100000 0, < 0 0"

If you want to connect WinCC OA systems using distributed systems, they need to have unique system numbers and names.

With the command line tool WCCOAtoolSyncTypes (can be found in WinCC OA installation folder/bin) it is possible to change the name and number of an existing system.

1. Stop the project
2. Make a backup of the database. If HDB archiving is used, it is not necessary to back up the VA_* directories as they are not modified when changing the system number and/or system name.
3. Open a command line window/terminal and switch to the bin folder of your used WinCC OA installation (e.g. C:\Siemens\Automation\WinCC_OA\3.19\bin).
4. Run the following command:

   WCCOAtoolSyncTypes -proj <the project name> -system <new System number> <new System name> -log +stderr

5. Wait until the command is finished and check the log output if an error is written

You can find an overview in our product help (in general: ONVIF 2.0 (Profile S) support is required) or at our technical solution partner Accellence Technologies:https://www.accellence.de/uploads/media/vimacc_Systemdokumentation_Bildquellenliste_EN_01.pdf

Yes, in rare cases installation of WinCC OA 3.17+ is not possible due to a conflict with Qt and the Matrox driver.

Our Recommendation:

• Install the newest Matrox driver.
• Set the environment variable QT_OPENGL and try one of the following values:
  • software
  • angle
  • desktop

The easiest and fastest way to create your own object library (including symbols, DPTs, faceplates) is to use the Stdlib.

The Stdlib is a framework that allows creating an object library by following some Rules instead of the required CTRL programming.

The basic rules are the location where to save panels, how to name DPTs and functions. Details about how to create an object library based on the Stdlib framework can be found in the Online help of the Stdlib. The BasicS7, AdvS7 and BACnet libraries are all created with the Stdlib.

The object library should be used as sub project and has a high level of reusability.

When using WinCC OA 3.16 or a newer version, only UTF8 languages are supported.

If your project framework uses ISO languages ​​and you want to use UTF8 languages you need to follow the instructions given below to migrate the panels and message catalogs into your project framework.

Modification of panels

When using special characters in the panel, texts may not be displayed correctly if the panels with ISO texts are used in a UTF8 project. This rule also applies to $ parameters defined in the panel files.

The easiest way to make the panels readable in UTF8 projects is to save them as XML files. A panel file in XML format is always saved as a UTF8 file.

All you need to do is change the format of the panel file. Even if the panel file is saved as an XML file, you can use the file extension “.pnl” or another extension..

• The conversion of panel files in PNL format to XML is done via the WinCC OA UI with the command line option -xmlConvert. The file names are given the extension ".xml".

  For example, conversion of the main.pnl for the PlantProject

  WCCOAui -xmlConvert main.pnl -proj PlantProject

• Rename the converted panels back to “.pnl” or the extension you used before. Then you don't need to change the scripts or code that refers to the panel names.

If you have many panels, you can write a script (e.g. a CTRL script) that performs the tasks.

Change in message catalogs

The encoding for the catalog files must be changed to UTF8. This can be done with a text editor, e.g. Notepad++

You must save the converted message catalog in the msg/<language>.utf8 directory.

• Open the news catalog with a text editor
• Change encoding to UTF8 without BOM
• Save the message catalog in the correct directory

Causes of the following log messages

WCCOAopc (1), 2016.11.23 08:07:02.465, IMPL, WARNING, 54, Unexpected state, OPCServer, 
CheckSrvInterfaces, Server does not support IOPCBrowseAddressSpace -> no browse info (No such interface 
supported(0x80004002))WCCOAopc (1), 2016.11.23 08:07:02.465, IMPL, SEVERE, 54, Unexpected state, OPCServer, 
CheckSrvInterfaces, Server does not support IOPCServer -> server cannot be used (No such interface 
supported(0x80004002))

When the OPC HDA Client is started:

WCCOAopchda (2), 2016.11.23 08:11:58.283, PARAM,SEVERE, 54, Unexpected state, 
OpcHDAClientServer, OpcHDAClientServer, Error when creating instance for server WINCC_OA.OPCHDA. hr 
= 524306, -2147467262, -2147467262, 0

While browsing for available OPC DA Servers in the panel System Management > OPC > Driver > OPC Driver

WCCOAui1:CreateInstance Failed (80040154)
WCCOAui1:Are you sure you have registered the latest OPCPROXY.DLL?          

These log messages occur if the installation of the OPC Core Components is missing or if different versions are installed.

See below for a detailed description:

1. OPC Core components are not installed

2. WinCC OA 3.14 or newer was installed after the installation of WinCC OA 3.12 or WinCC OA 3.13 or the OPC Core Components Redistributable 105.0 was installed.

   During the setup an update of the OPC Core Components Redistributable (x64) from 105.0 to 106.0 is made. This update sometime fails and therefore the new version 106.0 is not installed properly.

If you try to uninstall the OPC Core Components 106.0 manually, you will receive this error message:

There is a problem with this Windows Installer package. A program that is required to complete the installation could not be executed...

Solution:

Please use the "Repair" function, which is available via the Windows function Control Panel > Programs and Features

If you have not installed any OPC Core Components before the installation of WinCC OA 3.14 or a newerWinCC OA version, the upgrade of the OPC Core Components is not necessary.

If the current OPC Core Components (x64) 106.0 have already been installed before the installation of WinCC OA 3.14 or newer, the error does not occur.

In this case, it is recommended to have a local project installation on the remote computers with a correct link to the Data and Event Manager on the server computers. This can be configured by creating a new remote UI project using the WinCC OA Project Administrator.

Outside of this project, it is possible to start remote processes with the “-proj” option via CMD-Line. In this case, you don't have to worry about the actual status of redundant servers because the connection is established automatically

In some cases, it is necessary to simulate NaN (not a number) values for testing purposes (f.e. if you want to test, how your business logic is able to handle such values (they could come from PLCs in case of errors).

Here is a code-sample for generating a NaN-value (-1.#QNAN0) with a Control-Script:

main()
{
  blob source;
  int len, pos;
  string s;
  float value;
  s = "7F,FF,FF,FF";
  source = s;
  len = 4;
  pos = 0;

  blobGetValue(source, pos, value, len, FALSE);
  DebugN(isnan(value));        //this will result into a TRUE output<o:p></o:p>
  dpSet("System1:TestValue.", value);  //If some other Script is connected to this DPE, 
                                         it must be able to handle this value
}

If you used a CSS editor/text editing program (Notepad is a well known "culprit" for this) that saves the file with a BOM (Byte Order Mark), WinCC OA can no longer apply that .css file correctly.

Please note: There is no log viewer message.

You can easily check if your file uses a BOM by validating it here: http://validator.w3.org/i18n-checker/check

Solution: Use a different editor (e.g. Notepad++) or disable the BOM option.

Yes, the TLS Gateway is available for all delivered WinCC OA platforms.

After configuring a trend and viewing it in the trend panel there is the possibility to print this view. This can be triggered by using the "Print" button in the bottom bar of the panel.

If the user wants to print the panel with the legend there is also the "Legend" button in the bottom bar. This includes the legend of the currently configured datapoints of this trend on the top of the print.

When the browser is (accidentally) zoomed, panel design may not be displayed as planned in ULC UX. Add the following lines to [projectdirectory]\data\ulc\customer.js to show the user an info about it

$(document).ready(function()
{
  if(window.devicePixelRatio != 1)
  {
    alert("window zoom level is not 100%.");
  }
}
);

This FAQ is for information about the advantages and disadvantages about the usage of VMware vSphere clusters with WinCC OA.

There are 5 configuration options:

1. VMware vSphere vMotion®
2. VMware vSphere Storage vMotion
3. VMware vSphere High Availability (HA)
4. VMware vSphere Fault Tolerance (FT)
5. vSphere Storage Appliance (VSA)

____________________________________

• WinCC OA is already released for:

  Virtualization on vmWare

• WinCC OA will be released for:

  Virtualization on vmWare Clusters (without special vSphere options)

• WinCC OA evaluates the release for:

  vSphere High Availability virtualization on vmWare Clusters

• WinCC OA will not be released (in near future) for:

  vSphere Fault Tolerant option (Nr. 4)

  vSphere vMotion option (Nr.1)

Note: Due to known issues with the 5th option is this one not supported by WinCC OA.

This table shows the advantages and disadvantages of a WinCC OA System in combination with a VMware vSphere cluster.

Although it is technically possible, we strongly recommend - for increased security - to use different machines for the server project and the webserver.