Siemens SIMATIC WinCC flexible
The versiondog system supports the management of SIMATIC WinCC flexible projects and enables the automatic creation of backups as well as HMI cyclical monitoring.
System requirements
|
From versiondog Version |
WinCC flexible | ||||||
|---|---|---|---|---|---|---|---|
|
2005 |
2006 | 2007 | 2008 SP3 | 2008 SP5 | |||
| 2.6 | ✓ | ✓ | ✓ | ✓ | |||
| 6.0 | ✓ | ✓ | ✓ | ✓ | ✓ | ||
Other requirements
At present, you can only carry out an upload of the runtime for IPCs and Panel PCs with Windows operating system. Securing solely panels is still not possible.
Limitations: under certain conditions, depending on your network surroundings and implement devices, an upload cannot be carried out (e.g. limited access rights).
- The WinCC flexible - comparator needs a valid database to be installed to carry out the comparison. The general database driver is the MS SQL server
SQL instances for WinCC flexible versions on the devices that carry out the comparison
| WinCC flexible version | MS Data Engine 97 | MS Data Engine 2000 | MS Data Engine XP | MS Access 97 | MS Access 2000 | MS SQL Server 7.0 | MS SQL Server 2000 |
MS SQL 2005 |
MS SQL 2014 |
| 2004 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
|
||
| 2005 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | |||
|
2007 |
✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
|
||
|
2008 |
✓ | ✓ |
✓ |
||||||
| 2008 SP5 | ✓ |
Key features and functions
| Custom component type for SIMATIC WinCC flexible | ✓ |
|
Integrated SIMATIC WinCC flexible project tree |
✓ |
| Automatically detection of differences between the program running on the device and the latest version on the server | ✓ |
| Clear presentation of complete change history | ✓ |
| FAQ: Why does the comparison of my WinCC flexible projects fail, even though an instance of SQL Server is installed?
Explanation If the name of the instance of SQL Server installed on the affected client computer is different from the versiondog standard name (WINCC or WINCCFLEXEXPRESS), then versiondog cannot access the service. versiondog expects one of these names because in the majority of cases they are the names given to SQL Server instances included with installations of WinCC/WinCC flexible
Solution If the actual name of the SQL Server instance is not the standard name, then the actual name has to be provided to versiondog. In the following example, the name of the instance is MSSQLEXPRESS: 1. Go to the directory <vdClientArchive>\VD$A\Configuration\Compare 2. Open the file AgentStation.ini or create it with a text editor if it does not already exist 3. Add the following contents, depending on whether you want to compare WinCC or WinCC flexible (MSSQLEXPRESS is the name of the SQL instance that we are using in the example):
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.
|
In this tutorial
Last updated: 02 July 2020