Help Articles: Notes for Upgrading a WinCC OA Project

Back to All Topics

Introduction

General information on updating a WinCC OA project is described in the Updating a WinCC OA Project article. This section is limited only to the information that should be noted when upgrading a project to version 3.16.

  • Before upgrading a project a full backup is recommended! Read the article on how to backup your project. > Learn More
  • Since WinCC OA version 3.11 also supports 64-bit operating systems (please refer to software requirements), a WinCC OA project which is created for 32-bit needs to be adapted to 64-bit. In particular, any customer-developed 32-bit API-Manager, CONTROL Extensions, and Error-Handling must be changed to 64-bit.
  • Note that before an old WinCC OA project can be updated, and modified standard libraries (especially pt.ctl) has to be synchronized with the current libraries or moved temporarily. This also applies to sub-projects. For a generation of the panel topology sum alert data points, the updated library pt.ctl from the WinCC OA version is used. If the library is already available in the project, the library is taken from the project and the changes in the pt.ctl from the new version are not considered. Therefore, you have to synchronize the project-specific pt.ctl with that of the version or move it from the project.
  • Note that the old project, which uses the panel topology feature, has to contain the panel files when updating the project. For the generation of the Panel Topology sum alert data points, project panels are required. Without these, the panel topology sum alert data points cannot be created correctly. Therefore, the project panels have to exist when updating the project. Otherwise, the sum alert data points will be deleted or generated wrong.
  • Note also that the WinCC OA user “root” has to be enabled when updating a project. You cannot update a project if the user “root” is disabled.
  • When updating an older WinCC OA project to 3.16, you have to adjust the project-specific CTRL extensions manually.
  • Incorrect CTRL extensions, which are loaded in the UI or CTRL manager and are stored outside of the /bin WinCC OA directory, may cause a crash of the corresponding manager. The information on the concerned CTRL extension is shown in the WinCC OA log viewer. This must be corrected accordingly. With the new command-line option -noUserCtrlExt for every manager the loading of the CTRL extension, which is stored outside of the /bin directory, can be blocked. This option is also used for WCCOAtoolConvertDb.
  • With the WCCOAtoolConvertDb tool, a new ASCII file will be created without configuration history. This reduces the needed time for the updating process because only the recent configuration comes into the update when importing this ASCII file. In projects which are older than 3.10, the project must be updated to 3.10 firstly before it can be updated to 3.16.
  • If you update a 3.8 project (or an older project) to the WinCC OA version 3.16, the system modifies all historic RAIMA file sets that are online. The file sets are modified due to
  1. The new alarm reduction (sum alerts in sum alerts);
  2. The possibility to have more than 255 WinCC OA systems;
  3. The discrete alert handling;
  4. The new data buffering of the RDB manager in the event of a failed database connection
  • If you update a 3.8 project (or an older project) to the WinCC OA version 3.16, note that RAIMA archiving is not default anymore. (for more details see: History DB in the WinCC OA help files).
  • When updating a project that contains subprojects that do not exist or are not accessible anymore, these have to be commented out in the config file before updating the project.
  • If the powerconfigs file is present in the WinCC OA project directory under \configs, this has to be merged with the current version from the WinCC OA installation directory under \configs.
  • When upgrading an existing DRS project from an older version to 3.16, the data point list “update_disRecSystem.dpl”, from the directory \Redundancy2x2_3.16\dplist, needs to be imported to the upgraded project using the ASCII manager.
  • When upgrading WinCC OA version 3.8 or below to version 3.16, all Modbus connections (from projects of version 3.8 or below) are deactivated automatically. They must be manually activated again after upgrading the project.
  • When upgrading WinCC OA version 3.8 or below to version 3.16, the vScrollBarMode and hScrollBarMode change their state from “AlwaysOff” to “ScrollBarAsNeeded” due to a change of available options.
  • For a description of how to upgrading a redundant project see: Upgrade of a redundant project in the WinCC OA help files.
  • To upgrade a 32bit WinCC OA project to a 64bit WinCC OA 3.16 Project it is necessary to copy the 32bit registry entry of the project from:
    • [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ETM\PVSS II\Configs\]
    • to:
    • [HKEY_LOCAL_MACHINE\SOFTWARE\ETM\PVSS II\Configs\]
    • To copy the registry entry right-click on the entry and select export. In the .reg file that has been exported remove the entry “Wow6432Node” manually between “Software” and “ETM”. Afterwords re-import the entry with a double click on the .reg file.
  • For upgrading a WinCC OA project from version 3.10 to 3.16 it is necessary to change the system number to a value below 128. Otherwise, the upgrade can not be performed successfully. If the system number cannot be changed (e.g. plant project without the possibility for further configuration) additional WinCC OA tools can be used.
  • It is necessary to adapt its own scripts due to changes to the “dpQueryConnect” functions in WinCC OA version 3.11. With version 3.11 the string parameter “identifier” has been changed to anytype parameter “userData” which can cause problems when calling the corresponding callback function of the dpQueryConnect. So the callback functions must be adapted manually to the new anytype parameter when upgrading a project to WinCC OA version 3.16.
  • Some errors may occur during a project update if the standard data point types were modified (e.g. data point type ANALOG1 was deleted). Therefore, it’s recommended to do an ASCII export before the update and import the data after the update.
  • When upgrading an older project (< 3.12) to WinCC OA Version 3.16 it must be considered that a Multiplexing Proxy manager must be manually added. Please consider that the Multiplexing proxy must be added to the manager list in a position after the Event manager! In order to use the security feature, the Multiplexing Proxy manager must be configured accordingly.
  • Projects of the versions 3.5 and 3.6 cannot be updated to the version 3.16 under Linux. Update your project under Windows (see chapter Update or patch project) and start it then under Linux.
  • Please note that panels that contain 32bit ActiveX objects cannot be successfully upgraded as the objects are not supported anymore.
  • CAUTION: when you install a WinCC OA 3.16 patch, the data of the DemoApplication is reset. Back up your data before installing a patch.
  • Excel Report: When updating a project you have to update the customer-specific template files “.xltm” from the directory /data/xls_report as well as the internal database “Report.mdb” (which includes the configuration data). Therefore, rename the files from “.bak” to the original name. This means Report.bak to Report.mdb and the template files *.bak to *.xltm. Furthermore, update the customer-specific templates via the option “Update templates” from the Report menu. The customer-specific templates must be updated. Use, however, the current templates delivered by WinCC OA – Siemens/ETM. Thus, you only need to update the customer-specific templates.
  • With version 3.16 some new control keywords are reserved (e.g. new or delete, refer to Variables and constants for further information) or used (e.g. struct or class, refer to Control++) by WinCC OA and cannot be used e.g. as variable names anymore. When updating older projects to 3.16, there may be problems if you have defined one of these keywords as a variable name. In this case, you have to replace the now invalid names in the respective scripts and panels.
  • Relating to WinCC OA Video option – WinCC OA 3.15 installs the vimacc version 2.2.2.2 which enables IPC sockets encryption for all vimacc services. Unencrypted WinCC OA components cannot communicate with the encrypted vimacc services anymore. This means that:
    • A video server with this vimacc version cannot be operated with video clients <= 3.14, since you cannot enable encryption for them.
    • The vimacc version of an existing video server is also updated.
    • After installing WinCC OA 3.15, it is not possible to communicate with encrypted vimacc services in an existing WinCC OA project <= 3.14. This also applies if the services are running locally.
  • Due to enhancements to the WinCC OA Layout Management feature the existing behavior and default values changed. This must be considered when upgrading your WinCC OA project. It may be necessary to adjust your existing layout settings to get the previous visuals representation of your panels.
  • To upgrade a remote UI project the corresponding upgrade version must be available on the system and the installation path and version number must be adjusted inside of the projects config file.
  • If you upgrade a project which contains the config entry “paramLang”, you have to delete this entry manually from the config file before starting the project.
  • Upgrading a project under SLES to the current version is only possible with a project that already has version 3.14 and above.
Was this article helpful?
How can we improve this article?
Scroll to Top