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

CPU 410-5H Download Rejection After Project Migration - Upgrading with Utilization of New Functions in SIMATIC PCS 7

CPU 410-5H Download Rejection After Project Migration - Upgrading with Utilization of New Functions in SIMATIC PCS 7

Migrating a legacy SIMATIC PCS 7 project to the CPU 410-5H controller requires executing a 'Software Update with Utilization of New Functions' rather than a basic conversion. Replacing legacy S7-400 hardware with the CPU 410-5H introduces new architectural requirements, including updated module driver structures, Advanced Process Library (APL) alignment, and System Expansion Card (SEC) licensing. Attempting an upgrade 'without utilization of new functions' causes the CPU to reject the download order due to outdated hardware abstraction layers. To resolve this, perform a structured hardware adaptation, update the Master Data Library, and regenerate all channel drivers.

Table of Contents

Software Update Strategies - With vs Without Utilization of New Functions

In the official Siemens PCS 7 documentation, project software upgrades divide strictly into two distinct methodologies:
1. Software Update Without Utilization of New Functions:
* Designed purely to run an existing project on a newer PCS 7 engineering version without altering AS block types, instance DB structures, or faceplates.
* Strict Limitation: Hardware replacement is not supported in this mode. Existing controllers and I/O cards must remain identical.
2. Software Update With Utilization of New Functions:
* Mandated whenever hardware is modified, upgraded, or replaced (such as replacing legacy S7-400 CPUs with CPU 410-5H).
* Involves updating the Master Data Library, updating CFC block types, recompiling module drivers, and recompiling OS pictures to leverage enhanced diagnostics.

Why Hardware Replacement Mandates New Functions

When an engineering team replaces a legacy controller with a CPU 410-5H (6ES7410-5HX08-0AB0):
* New Operating System Kernel: The CPU 410-5H firmware kernel does not contain legacy microcode emulation for discontinued S7-300/S7-400 system calls.
* PROFINET S2 Redundancy & Dynamic Reconfiguration (CiR): CPU 410-5H requires modernized driver blocks (MOD_* from PCS 7 Basis Library) to support advanced fieldbus diagnostics and online I/O changes.
* SEC Licensing Mechanism: Hardware capacity is governed by the System Expansion Card (6ES7653-2...). Outdated block libraries lack the licensing handshake blocks (PO_EXP, LIC_CHK) required to authorize controller execution.

Step-by-Step CPU 410-5H Migration and Download Sequence

Follow the structured technical procedure to migrate and download cleanly to CPU 410-5H:

[Phase 1: Hardware Adaptation in HW Config]
   │  • Open HW Config -> Delete old CPU object from rack
   │  • Insert CPU 410-5H (6ES7410-5HX08-0AB0) matching exact firmware
   │  • Configure IP addresses, MAC addresses, and subnet assignments
   │  • Execute: Station -> Save and Compile
   │
[Phase 2: Master Data Library Alignment]
   │  • In SIMATIC Manager: Open Multiproject Master Data Library
   │  • Replace legacy driver blocks with current PCS 7 Basis Library blocks
   │  • Open CFC: Options -> Block Types -> Update block types across all charts
   │
[Phase 3: Identify Problematic Global DBs]
   │  • If legacy custom global DBs cause load order rejection:
   │  • Remove non-CFC global DBs from the Blocks folder
   │  • Re-import them systematically, verifying data alignment and length
   │
[Phase 4: Full Compilation and Download]
   │  • In CFC: Chart -> Compile -> Select "Entire program"
   │  • Check: "Generate module drivers" (CRITICAL: Creates CPU 410 driver links)
   │  • Select: PLC -> Download -> "Entire program" in STOP mode
   │  • Switch CPU to RUN; verify that process control resumes seamlessly!

Procurement Notice: Validate all final license quantities, media packages, and part numbers against current Siemens Industry Mall catalogs and with an authorized Siemens distributor quotation prior to procurement.

Migration Strategy Comparison for CPU 410-5H Upgrades

Evaluate the two software update methodologies when transitioning to CPU 410-5H:

Architectural RequirementUpdate Without New FunctionsUpdate With New Functions (Required)CPU Hardware ReplacementProhibited by Siemens GuidelinesOfficially Supported and DocumentedDriver Library VersionRetains legacy V7.x driver blocksUpgrades to PCS 7 Basis Library V8.1 / V8.2CFC Module Driver GenerationUses old driver generation logicGenerates modern CPU 410 diagnostic driversCPU 410 Download CompatibilityRejects download order at ~6%Downloads cleanly to 100% completionOnline Run-Mode Changes (CiR)RestrictedFully supported with CPU 410-5HSEC Capacity AuthorizationFails handshakeFully verified and authorized

Verification

To confirm that the CPU 410-5H migration and download succeeded:
1. In SIMATIC Manager, confirm that PLC -> Download -> Entire program completes to 100% without rejection.
2. In HW Config Online, verify that the CPU operating mode indicates RUN with a steady green LED.
3. Open the CPU Diagnostic Buffer; confirm that the event STOP caused by download is followed by Transition to RUN completed.
4. In CFC Editor, switch to Test Mode; confirm that all channel drivers communicate with field modules.
5. In WinCC Explorer, verify that the OS Server establishes communication with the CPU 410-5H via Named Connections.

Limitations and Operational Precautions

Replacing an AS controller and upgrading with new functions cannot be executed bumplessly online. An Entire Program download in STOP mode is required. Plan for an authorized plant outage. Ensure all safety programs (S7 F Systems) are recompiled and safety signatures validated before returning the controller to operational production.

Engineer FAQ

Why doesn't the manual for 'Software update without new functions' describe CPU replacement?

Because replacing controller hardware inherently requires new system functions and updated driver blocks, making it impossible under the 'without new functions' doctrine.

What manual describes hardware replacement for PCS 7?

The manual 'SIMATIC PCS 7 Process Control System Software Update with Utilization of New Functions', Chapter 6 ('Adapting Hardware').

Can I migrate custom user FBs without rewriting them to APL?

Yes. Custom user blocks can be retained provided their interface parameters do not conflict with the modernized Basis Library driver calls.

How do I verify the Process Object capacity on the CPU 410-5H?

In STEP 7 SIMATIC Manager, select the CPU object and click PLC -> CPU 410-5H -> Display Process Objects to view authorized versus consumed POs.

Technical References

Related Articles

Related Tags

  • CPU 410-5H
  • Project Migration
  • Utilization of New Functions
  • Software Update
  • Master Data Library
6 respuestas