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

Migration Guidelines for Legacy PCS 7 Library Blocks Upgrading to V8.1

Migration Guidelines for Legacy PCS 7 Library Blocks Upgrading to V8.1

When migrating a legacy SIMATIC PCS 7 V7.1 project to V8.1 SP1 without utilizing new functions, it is not mandatory to replace classic technological blocks (such as CTRL_PID v1.11, MOTOR, or VALVE) with newer versions or APL blocks. Older functional blocks can remain in the Automation Station (AS) program provided the corresponding legacy libraries (PCS 7 Library V7.1 SP3 Upd4, Basis Library V7.1 SP3 Upd11, and Faceplates V7.1 SP3) are installed on the Engineering Station (ES). However, channel driver blocks must be upgraded to ensure compatibility with modern hardware driver generators. All migration software packages must be confirmed via an authorized Siemens distributor or the Siemens Industry Mall.

Table of Contents

Executive Summary

During software modernization projects migrating legacy SIMATIC PCS 7 V7.1 SP4 systems to PCS 7 V8.1 SP1, engineering teams frequently audit installed block versions across controllers. Audits often reveal that specific controllers utilize technological blocks from earlier library builds (e.g., AS3 executing CTRL_PID v1.11 from older Standard Library versions rather than v6.0 from V7.1 SP3). Engineers face a critical architectural decision: must every individual block be updated to the latest library revision? Siemens official migration doctrine ('Software update without utilization of new functions') confirms that technological blocks do not require mandatory replacement if legacy support libraries are co-installed on the ES, avoiding risky plant shutdowns and extensive chart rewiring.

Architecture and Fundamental Mechanics

The architectural rules governing legacy block migration in SIMATIC PCS 7 split into two distinct operational paradigms:

1. Software Update Without Utilization of New Functions (In-Place Migration)

This strategy aims to migrate engineering and operator stations to a modern operating system (e.g., Windows 7 / Server 2008 R2) while minimizing changes to the verified controller logic:
- Technological Blocks (CTRL_PID, MOTOR, VALVE): These blocks execute user logic. Upgrading them in-place from classic library to Advanced Process Library (APL) alters their interface signatures (inputs, outputs, structures). Doing so would mandate deleting existing connections, re-linking faceplates, and executing a complete AS STOP download.
- To avoid this, Siemens allows keeping older classic blocks in the AS program. The modern Engineering Station simply requires installing the PCS 7 Legacy Library Packages (available on the PCS 7 installation media under Additional Products or SIOS).

2. The Mandatory Exception: Channel Driver Blocks

  • Unlike technological blocks, Channel Driver Blocks (CH_AI, CH_DI, CH_DO, CH_AO) interface directly with hardware diagnostic blocks.
  • The PCS 7 CFC compiler contains an updated 'Generate Module Drivers' engine in V8.1 that cannot generate valid @ diagnostic charts for obsolete channel drivers.
  • Therefore, channel blocks must be updated to the V7.1 SP3 / V8.x driver version, while standard control blocks can remain untouched.

Step-by-Step Implementation Procedure

To execute a compliant migration from PCS 7 V7.1 to V8.1 SP1 without replacing legacy technological blocks:

Step 1: Install Legacy Support Libraries on the ES

  1. On the PCS 7 V8.1 SP1 Engineering Station, insert the installation media or browse to SIOS downloads.
  2. Install the necessary legacy compatibility packages:
    - PCS 7 Library V7.1 SP3 Upd4
    - PCS 7 Basis Library V7.1 SP3 Upd11
    - PCS 7 Faceplates V7.1 SP3 Upd1
  3. Use the Siemens Compatibility Tool to confirm library coexistence on the target Windows operating system.

Step 2: Open and Migrate Project in SIMATIC Manager

  1. Open the archived V7.1 project in SIMATIC Manager V8.1 SP1.
  2. Allow the database converter to update the project file structure to V8.1 format.
  3. Open the Master Data Library or target AS Charts folder.

Step 3: Selectively Update Channel Blocks

  1. In the CFC Editor, select Options -> Block Types.
  2. In the Block Types dialog, select only the channel driver blocks (CH_AI, CH_DI, etc.) and click New Version.
  3. Do not update CTRL_PID or classic motor/valve blocks.
  4. Execute Chart -> Compile -> Changes Only with 'Generate module drivers' enabled.

Step 4: Compile and Migrate the OS

  1. Migrate the WinCC OS project using the Project Migrator.
  2. In WinCC Explorer, verify that classic faceplates (@PG_...) from the legacy library operate properly.
  3. Execute a full OS Compilation.

Verification

To confirm successful migration without unintended block updates:

  1. AS Delta Compilation Check:
    - In CFC, compile the chart folder with option Changes only.
    - Verify that compilation succeeds with zero errors, confirming that the AS program can be downloaded in RUN.

  2. CFC Block Version Audit:
    - Right-click CTRL_PID in CFC and inspect Object Properties.
    - Confirm that the version remains v1.11 as originally engineered.

  3. OS Faceplate Operation Test:
    - In WinCC Runtime, open the faceplate for CTRL_PID.
    - Verify that setpoint adjustments, auto/manual transitions, and alarm thresholds operate identically to the legacy system.

Limitations and Operational Precautions

Operational limitations and precautions:

  1. No Access to Modern APL Features: Retaining legacy V7.1 blocks precludes using APL features such as Feature bits, Advanced Alarm Handling, and Control Module Types (CMT).
  2. Future Obsolescence Boundary: In subsequent major migrations (such as upgrading to PCS 7 V9.1), support for classic non-APL libraries is completely phased out, eventually necessitating full block replacement.
  3. OS Picture Tree Regeneration: Avoid blindly regenerating block icons using APL typicals; ensure the legacy @PCS7Typicals.pdl is used rather than @PCS7TypicalsAPL.pdl.
  4. Commercial Disclaimer: Verify all software upgrade paths, compatibility packages, and legacy licenses with an authorized Siemens distributor or the Siemens Industry Mall.

Engineer FAQ

Is it mandatory to update all functional blocks when migrating from V7.1 to V8.1?

No. You can perform a 'Software update without utilization of new functions', keeping older technological blocks (like CTRL_PID) intact if legacy libraries are installed on the ES.

Why must channel blocks be updated even if control blocks are not?

The CFC 'Generate Module Drivers' compiler in modern PCS 7 versions cannot generate valid diagnostic @ charts for obsolete channel driver blocks.

What are the consequences of not updating CTRL_PID to APL?

The block continues functioning normally, but you cannot utilize modern APL faceplates, Feature bits, or Control Module Types (CMT).

Where can I find legacy library installers for PCS 7 V8.1?

Legacy libraries are included on the PCS 7 installation media under Additional Products or available for download on Siemens Industry Online Support (SIOS).

Does keeping legacy blocks avoid an AS STOP during migration?

Yes. Because block interfaces remain identical, changes can be compiled and downloaded in RUN without stopping the Automation Station.

Technical References

Related Articles

Related Tags

  • PCS 7 Migration
  • Legacy Libraries
  • CTRL_PID
  • Channel Drivers
  • Software Update
20 respuestas