Siemens SIMATIC WinCC

The versiondog system supports the management of SIMATIC WinCC projects and enables the automatic backup creation and the cyclical monitoring of controllers.

 

 

System requirements

From versiondog

Version

WinCC
5.x 6.x 7.x 7.4
1.52.2    
4.5  
5.5

 

Other requirements

WinCC Version

Data bank version
WinCC v5.0 Sybase Anywhere 5

WinCC v5.1

Sybase Anywhere 7

WinCC v6.0 SQL Server 2000

WinCC v6.0 SP4

SQL Server 2000 SP4

WinCC v6.2

SQL Server 2005 SP1

WinCC v7.0

SQL Server 2005 SP1

WinCC v7.0 SP1

SQL Server 2005 SP2

WinCC v7.0 SP2

SQL Server 2005 SP3

WinCC v7.2

SQL Server 2008 SP1

WinCC v7.3

SQL Server 2008 SP1

WinCC v7.4

SQL Server 2014 SP1

 

Key features

Individual component type for SIMATIC WinCC

Integrated SIMATIC WinCC project tree

Automated detection of differences between the program running on the controller and the current version on the server (backup- to the previous backup- detailed comparison, version to backup - detailed comparison)

Detailed comparison for images and C Actions/Project functions (see Requirements)

Clear presentation of complete change history

 

FAQ: Why does the comparison of my WinCC 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):

  1. [WinCC]
     7030=MSSQLEEXPRESS 
  1. [WinCCFlexible]
     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

 

To complete FAQ list

 

In this tutorial:


Last updated: 02 July 2020