C135 PCS 7 (PCS7)
6C
6 Cielo Ciencia y Tecnología
·Publicada en C135 PCS 7 (PCS7)

Evaluating Virtualization Feasibility and Legacy Limits for SIMATIC PCS 7 V6.1 on Windows XP

Evaluating Virtualization Feasibility and Legacy Limits for SIMATIC PCS 7 V6.1 on Windows XP

SIMATIC PCS 7 V6.1 SP1 is not officially released, tested, or supported by Siemens for execution within virtualized environments. Siemens officially introduced virtualization support for PCS 7 starting with PCS 7 V7.1 SP2 on certified VMware platforms. While you can technically install a guest Windows XP Professional SP2 virtual machine on a modern Windows 10 host using VMware Workstation or Hyper-V for offline engineering, code review, or simulation, doing so in production is strictly at your own operational risk. Communication hardware such as CP 1613/CP 1623 cannot be virtualized, hard real-time plant bus communication cannot be guaranteed, and Siemens Customer Support will reject service requests for unreleased virtual configurations.

Table of Contents

Executive Summary

Legacy process control systems frequently confront hardware obsolescence when the underlying physical computers running legacy operating systems—such as Windows XP Professional SP2 on SIMATIC PCS 7 V6.1 SP1—suffer hardware failures. Because modern industrial PCs and commercial off-the-shelf workstations running Windows 10 do not support native installation of legacy operating systems, automation teams frequently consider virtualization solutions (such as VMware Workstation, VMware ESXi, or Microsoft Hyper-V) to host virtualized Windows XP instances.

While virtualization provides an attractive solution for maintaining legacy engineering archives and offline project modifications, engineers must understand the official manufacturer support boundaries. Siemens did not certify any release of SIMATIC PCS 7 for virtualization prior to PCS 7 V7.1 SP2 (documented under Entry ID 51975791 and Product Note 51401737). Operating PCS 7 V6.1 in a virtual machine introduces significant technical limitations regarding communication processor virtualization, interrupt latencies, and clock synchronization. This guide provides an architectural evaluation of virtualizing PCS 7 V6.1, details the technical prerequisites and configuration steps for offline virtualization, and outlines the operational risks and upgrade migration pathways.

Architecture and Fundamental Mechanics

The execution of PCS 7 V6.1 within a virtualized hypervisor involves fundamental architectural divergence from physical installations:
1. Manufacturer Release Milestone:
* Siemens officially introduced PCS 7 virtualization support with PCS 7 V7.1 SP2, releasing virtualized OS Clients, BATCH Clients, Route Control Clients, and Engineering Stations on VMware vSphere / ESXi.
* PCS 7 V6.1 SP1 (released in 2005) predates Siemens industrial virtualization testing. Consequently, no official validation, performance matrices, or qualification certificates exist for V6.1 under any hypervisor.
2. Industrial Communication Processor Virtualization:
* High-performance plant bus communication in PCS 7 V6.1 relied on dedicated PCI communications processors, primarily the CP 1613 (Hardnet with dedicated onboard microprocessor running the ISO transport stack).
* Standard desktop hypervisors (VMware Workstation, Player, VirtualBox) do not support PCI pass-through or virtualized NDIS drivers for CP 1613/CP 1623 hardware. The virtual machine can only utilize virtualized standard network interface cards (e.g., Intel E1000 or VMware VMXNET), limiting plant bus communication strictly to Softnet-IE protocol stacks.
3. Timing and Clock Synchronization Latencies:
* Virtual machine guest operating systems share physical CPU cores via a hypervisor time-slicing scheduler. In Windows XP virtual machines, timer tick drift and hypervisor scheduling latency cause time synchronization jitter across the terminal bus and plant bus.
* In continuous process environments, jitter impairs sequence-of-events (SOE) timestamp precision and disrupts historical tag archiving.
4. Database and File System Integrity:
* PCS 7 V6.1 utilizes Microsoft SQL Server 2000 (Siemens WinCC instance). Abrupt hypervisor suspension, snapshot reverts, or host power cycles can corrupt active SQL transaction logs (.ldf) and WinCC project files (.mcp).

Step-by-Step Implementation Procedure

Step 1: Designate Usage Scope Strictly for Offline Engineering

  1. Establish clear operational boundaries: virtualizing PCS 7 V6.1 must be restricted strictly to offline engineering, logic testing, and training environments.
  2. Do NOT connect a virtualized V6.1 instance to an active, physical production plant bus controlling live processes.

Step 2: Configure the Virtual Machine Hypervisor

  1. On the Windows 10 64-bit host computer, install a professional hypervisor supporting legacy operating systems (e.g., VMware Workstation Pro or VMware Player).
  2. Create a new Virtual Machine with the following parameters:
    * Guest Operating System: Microsoft Windows XP Professional (32-bit).
    * Processors: 1 virtual CPU (assigning multiple vCPUs to Windows XP can introduce ACPI multi-processor kernel instability in legacy software).
    * Memory (RAM): Exactly 1024 MB to 2048 MB (Windows XP 32-bit cannot address more than 3.2 GB, and PCS 7 V6.1 runs optimally with 1 GB to 2 GB).
    * Disk Storage: 40 GB to 80 GB pre-allocated virtual disk (SCSI or IDE virtual disk controller, formatted as NTFS).
    * Network Adapter: Bridged or Host-Only virtual network adapter.

Step 3: Install Windows XP and Mandatory Prerequisites

  1. Install Windows XP Professional with Service Pack 2 (SP2) or Service Pack 3 (SP3, depending on the exact PCS 7 V6.1 Readme specification).
  2. Install VMware Tools to ensure proper graphics driver acceleration and mouse synchronization.
  3. Configure mandatory Windows settings:
    * Disable Windows Firewall and disable all automatic Windows updates.
    * Set display resolution to standard 4:3 or 16:9 aspect ratios (e.g., 1280x1024 or 1920x1080) at 100% Windows DPI scaling.
    * Set power management to 'Always On' (disable sleep, hibernation, and hard drive spin-down).

Step 4: Install SIMATIC PCS 7 V6.1 SP1

  1. Mount the original PCS 7 V6.1 SP1 installation CD/DVD images into the virtual optical drive.
  2. Execute Setup.exe from the root directory.
  3. Install Microsoft SQL Server 2000 SP3a (supplied exclusively on the Siemens PCS 7 media).
  4. Complete the installation of STEP 7, CFC, SFC, SIMATIC NET, and WinCC V6.0 SP1.
  5. Restart the virtual machine when prompted by the setup program.

Step 5: Transfer Automation Licenses and Test Operation

  1. Connect the USB license storage stick to the host computer and attach it to the virtual machine via the hypervisor USB passthrough menu.
  2. Open Automation License Manager (ALM) in the virtual Windows XP environment.
  3. Transfer the required PCS 7 V6.1 floating licenses to local drive C:.
  4. Open SIMATIC Manager and retrieve a project archive (File > Retrieve) to verify project compilation and chart editing.

Verification

  1. In the virtual Windows XP machine, open SIMATIC Manager and open an existing PCS 7 V6.1 project.
  2. Open several CFC charts: confirm that block placement, signal interconnection, and chart navigation function smoothly without graphical distortion.
  3. Open WinCC Explorer: verify that the project opens without SQL Server database connection dialogs or licensing warnings.
  4. Start S7-PLCSIM inside the virtual machine: download the user program and verify that logic execution, step sequencing, and faceplate monitoring operate correctly.
  5. Take a clean hypervisor snapshot of the powered-off virtual machine to serve as a baseline restoration point.

Limitations and Operational Precautions

  1. Siemens Customer Support will not provide technical assistance for runtime anomalies, communication drops, or software crashes occurring on virtualized PCS 7 versions prior to V7.1 SP2.
  2. Hardware-based communications processors (CP 1613, CP 1623, CP 5611) cannot be accessed directly via hypervisors without physical PCI pass-through, which is unsupported for V6.1.
  3. Production plant control should be modernized to a supported version (such as PCS 7 V9.0 or V9.1) rather than relying on uncertified virtualized legacy infrastructure.
  4. S7-400H fault-tolerant communication cannot guarantee bumpless redundancy switchover when communicating through virtualized network interfaces.

Engineer FAQ

Why did Siemens not officially support virtualization for PCS 7 V6.1?

PCS 7 V6.1 was engineered in the early 2000s for dedicated physical hardware running Windows 2000 and Windows XP. Commercial virtualization technologies (such as VMware ESXi) had not yet matured or achieved the deterministic real-time communication standards required for process automation.

Which PCS 7 version was the first to be officially released for virtualization?

Siemens officially cleared PCS 7 for virtualization starting with PCS 7 V7.1 SP2 on certified VMware vSphere / ESXi platforms (Entry ID: 51975791).

Can I connect a virtualized PCS 7 V6.1 ES to a physical S7-400 PLC?

Yes, using a standard bridged virtual Ethernet adapter with SIMATIC NET Softnet-IE. However, communication is subject to host network latency and is not certified for production plant operations.

Can I use Windows 10 Hyper-V instead of VMware Workstation?

Yes, Hyper-V can host a Generation 1 Windows XP virtual machine. However, VMware Workstation typically offers superior legacy driver support, screen resolution handling, and USB passthrough for Windows XP.

What is the recommended long-term strategy for legacy PCS 7 V6.1 plants?

The manufacturer-recommended strategy is an orderly migration to a modern, supported PCS 7 release (such as V9.1) or SIMATIC PCS neo. Consult an authorized Siemens distributor or the Siemens Industry Mall for migration upgrade kits and modernization planning.

Technical References

Related Articles

Related Tags

  • PCS 7 V6.1
  • Virtualization
  • Windows XP
  • VMware
  • Legacy Migration
20 respuestas