Siemens SIMATIC WinCC
The versiondog system supports the management of SIMATIC WinCC projects and enables the automatic backup creation and the cyclical monitoring of the controllers.
System compatibility
|
From version |
WinCC | ||||
|---|---|---|---|---|---|
| 5.x | 6.x | 7.x | 7.4 | 7.5 | |
| versiondog 1.52.2 | ✓ | ✓ | |||
| versiondog 4.5 | ✓ | ✓ | ✓ | ||
| versiondog 5.5 | ✓ | ✓ | ✓ | ✓ | |
| versiondog 8.0 | ✓ | ✓ | ✓ | ✓ | ✓ |
Requirements
- For upload and comparison, you need to install on each WinCC Station a HMI upload agent as well as a compare agent.
- For the comparison process, the WinCC comparator requires a valid installation of a SQL database.
- You require the following database driver for WinCC versions:
-
You need administrator rights on these instances for the logged-in system user.
| WinCC version | Database |
|---|---|
| 5.0 | Sybase Anywhere 5 |
| 5.1 | Sybase Anywhere 7 |
| 6.0 | SQL Server 2000 |
| 6.0 SP4 | SQL Server 2000 SP4 |
| 6.2 | SQL Server 2005 SP1 |
| 7.0 | SQL Server 2005 SP1 |
| 7.0 SP1 | SQL Server 2005 SP2 |
| 7.0 SP2 | SQL Server 2005 SP3 |
| 7.2 | SQL Server 2008 SP1 |
| 7.3 | SQL Server 2008 SP1 |
| 7.4 | SQL Server 2014 SP1 |
| 7.5 | SQL Server 2016 SP in the 64 bit version (Standard or Express edition) |
Features and functions
| Component type for SIMATIC WinCC |
|
Integrated SIMATIC WinCC project tree |
| Automatically detect differences between the program running on the device and the current version on the server (backup detailed comparied, version and backup detailed comparison) |
| Detailed compare for process images and C actions and project functions |
| Clear presentation of complete change history |
|
Why does the comparison of my WinCC or WinCC flexible projects fail, even though an instance of SQL Server is installed?
Explanation If the name of the SQL Server Instance on the client system is different from the versiondog standard name (WINCC or WINCCFLEXEXPRESS9) versiondog will not be able to access it. versiondog assumes one of these names, since these are set in the majority of installations of SQL servers included with WinCC/WinCC flexible.
Solution If the name of the SQL Server Instance differs from the standard, this name needs to be made known to versiondog . In the following example the instance name is set to MSSQLEXPRESS: 1. In the directory, go to <vdClientArchive>\VD$A\Configuration\Compare 2. Open the file AgentStation.ini, if this is not available, you can open it with another text editor 3. Insert the following contents, depending on whether you wish to compare WinCC or WinCC flexible (MSSQLEXPRESS is the example name of the SQL Instanz):
7030=MSSQLEEXPRESS
7050=MSSQLEXPRESS
NOTE If the above entry is one of the versiondog standard names of WINCC or WINCCFLEXEXPRESS, then versiondog will expect that editor to be installed in addition to the instance of SQL Server. If it is not installed, the comparison will fail. This means that if no WinCC editor is installed, then you cannot use WINCC or WINCCFLEXEXPRESS as the name of the SQL instance.
|
If you need an installation guide of the Microsoft SQL Server 2005 Express Edition, contact us.
| Related topics |
|---|
| Upload and Compare Agents |
In this tutorial:
Last updated: