Determining Delivered and Compatible WinCC Versions Across SIMATIC PCS 7 V6.1 Service Packs

Determining Delivered and Compatible WinCC Versions Across SIMATIC PCS 7 V6.1 Service Packs

In SIMATIC PCS 7 V6.1, the factory-delivered version of SIMATIC WinCC varies across specific service packs: base PCS 7 V6.1 shipped with WinCC V6.0 SP3; PCS 7 V6.1 SP1 delivered WinCC V6.0 SP3a; PCS 7 V6.1 SP2 shipped with WinCC V6.0 SP4; PCS 7 V6.1 SP3 delivered WinCC V6.2; and PCS 7 V6.1 SP4 delivered WinCC V6.2 SP2. To verify the original delivery version for any legacy PCS 7 installation, consult the Siemens Compatibility Tool (SIOS Entry ID 64847781), where the lowest compatible WinCC version listed for a specific PCS 7 release indicates the original factory installation media version.

Table of Contents

Executive Summary

Maintaining, migrating, or auditing legacy control systems operating on SIMATIC PCS 7 V6.1 (widely deployed between 2005 and 2010 on Windows XP and Windows Server 2003) frequently requires identifying the exact factory-delivered version of SIMATIC WinCC included with specific installation DVDs. Because legacy facilities often underwent minor hotfix updates over decades of operation, determining whether an engineering station was originally installed with WinCC V6.0 SP3 or WinCC V6.2 SP2 is vital for procuring compatible replacement hardware, planning migration hops to PCS 7 V7.1 / V8.x, and restoring original project archives. This technical guide outlines the historical release mapping and explains how to extract original delivery baselines using the Siemens Compatibility Tool.

PCS 7 V6.1 Release Architecture: Historical Lifecycle Evolution

SIMATIC PCS 7 V6.1 represented a major milestone in Siemens process automation, bridging the transition from early WinCC V6 architectures to modern SQL Server-driven SCADA systems. Over its lifecycle, Siemens released four Service Packs (SP1 through SP4):

  • V6.1 Base to SP2: Powered by Microsoft SQL Server 2000 and WinCC V6.0, supporting Windows 2000 and Windows XP Professional.
  • V6.1 SP3 to SP4: Introduced Microsoft SQL Server 2005 and WinCC V6.2, modernizing central archive management and establishing the database foundation required for subsequent upgrades to PCS 7 V7.x.

Original Factory Delivery Versions Across V6.1 Service Packs

The factory installation media delivered with each specific release level contained distinct WinCC builds:

  • PCS 7 V6.1 Base (2005): Delivered with WinCC V6.0 SP3.
  • PCS 7 V6.1 SP1 (2006): Delivered with WinCC V6.0 SP3a.
  • PCS 7 V6.1 SP2 (2007): Delivered with WinCC V6.0 SP4.
  • PCS 7 V6.1 SP3 (2008): Delivered with WinCC V6.2 (SQL Server 2005).
  • PCS 7 V6.1 SP4 (2009): Delivered with WinCC V6.2 SP2 (Windows Server 2003 R2).

The Siemens Compatibility Tool Delivery Version Rule

When researching legacy versions on the Siemens Compatibility Tool (Kompatool), multiple compatible versions are often displayed for a single PCS 7 release because users were permitted to install subsequent WinCC service packs. As a universal rule of thumb in Siemens compatibility tables:

  • The lowest / smallest compatible version listed for a specific PCS 7 release represents the original factory-delivered media version.
  • Higher versions listed under the same entry represent permissible post-installation upgrade paths.

PCS 7 V6.1 and WinCC Version Mapping Matrix

The following table details the historical delivery packages, operating systems, and database engines for PCS 7 V6.1:

PCS 7 Release LevelFactory Delivery WinCC BuildOperating System PlatformDatabase EngineMigration Target HopPCS 7 V6.1 (Base)WinCC V6.0 SP3Windows XP SP2 / Server 2003Microsoft SQL Server 2000Upgrade to V6.1 SP4 first.PCS 7 V6.1 SP1WinCC V6.0 SP3aWindows XP SP2 / Server 2003Microsoft SQL Server 2000Upgrade to V6.1 SP4 first.PCS 7 V6.1 SP2WinCC V6.0 SP4Windows XP SP2 / Server 2003Microsoft SQL Server 2000Upgrade to V6.1 SP4 first.PCS 7 V6.1 SP3WinCC V6.2 (Base)Windows XP SP3 / Server 2003Microsoft SQL Server 2005Direct hop to PCS 7 V7.0 SP3.PCS 7 V6.1 SP4WinCC V6.2 SP2Windows XP SP3 / Server 2003 R2Microsoft SQL Server 2005Direct hop to PCS 7 V7.1 SP4.

Step-by-Step Version Verification Procedure

Method 1: Determining Installed Version in WinCC Explorer

  1. On the operational workstation, launch WinCC Explorer.
  2. Navigate to Help > About SIMATIC WinCC from the main menu bar.
  3. In the splash dialog, inspect the build string (e.g. WinCC V6.2 SP2, Build 2100).
  4. Compare the build number against the Siemens Compatibility Matrix to confirm whether the system runs original or updated media.

Method 2: Inspecting SIMATIC Installed Software

  1. Open Windows Control Panel and double-click Siemens Installed Software (or open via SIMATIC Manager: Help > About > Installed Software).
  2. Click the Components tab.
  3. Locate component WinCC Runtime and inspect the exact version and Hotfix level.

Verification

To verify software version consistency prior to project upgrades:

  1. Compatibility Tool Query: Open the online Siemens Compatibility Tool (Entry ID 64847781). Select PCS 7 V6.1 SP4. Confirm that WinCC V6.2 SP2 is listed as compatible.
  2. Database Schema Inspection: Open SQL Server Enterprise Manager (or Management Studio). Verify whether database WINCC operates on SQL Server 2000 or SQL Server 2005.
  3. Migration Readiness: Confirm that systems on WinCC V6.0 (SQL 2000) are upgraded to WinCC V6.2 (SQL 2005) before attempting migration to PCS 7 V7.x.

Limitations and Operational Precautions

  • Operating System End-of-Life: PCS 7 V6.1 runs strictly on Windows XP and Windows Server 2003, which have reached official Microsoft End-of-Support. Isolate these networks completely from corporate IT and the Internet.
  • Direct Upgrade Prohibition: Never attempt to restore or open a WinCC V6.0 (SQL 2000) project directly in modern PCS 7 V8.x or V9.x; the project must pass through intermediate conversion in WinCC V7.0 (SQL 2005) and V7.2 (SQL 2008 R2).
  • License Transfer: WinCC V6.x utilized floppy disk authorizations (AuthorsW) or early Automation License Manager keys (yellow USB sticks); modern PCS 7 licenses require current ALM versions.

Engineer FAQ

Can PCS 7 V6.1 run on Windows 7 64-bit?

No. PCS 7 V6.1 is a 32-bit legacy package supported strictly on Windows XP Professional (SP2/SP3) and Windows Server 2003.

What was the major change introduced in PCS 7 V6.1 SP3?

PCS 7 V6.1 SP3 introduced WinCC V6.2, which transitioned the underlying database engine from Microsoft SQL Server 2000 to SQL Server 2005.

Can I upgrade WinCC V6.0 SP3 to WinCC V6.2 without upgrading the PCS 7 AS engineering software?

No. In PCS 7, WinCC and STEP 7/CFC versions are tightly coupled in release packages; upgrading WinCC independently breaks AS-OS compilation.

Technical References

Related Articles

Related Tags

  • https://industrialautomation.net/search?query=simatic-pcs7
  • https://industrialautomation.net/search?query=wincc-scada
  • https://industrialautomation.net/search?query=compatibility
  • https://industrialautomation.net/search?query=legacy-systems
6 respuestas