Troubleshoot a Disabled CPU 410 Expansion Pack Upgrade in ALM
For a CPU 410 process-object expansion, distinguish transferring packs to an AS from selecting them in that AS's Online folder and completing the activation/release workflow. Siemens documents an ALM upgrade procedure with specific CPU, firmware and SEC prerequisites. If the Online folder or Upgrade action is unavailable, first identify which prerequisite or workflow stage is missing. The reported visibility only under the AS tab does not establish the exact cause.
Table of Contents
- Check the Documented Upgrade Prerequisites
- Documented ALM Upgrade Workflow
- Investigate the Disabled Command
- Verification
- Limitations and Operational Precautions
- Engineer FAQ
- Technical References
- Related Articles
- Related Tags
Check the Documented Upgrade Prerequisites
The historical application example Process automation with the SIMATIC PCS 7 CPU 410-5H controller, entry 96839331, V2.2, section 2.5.1, requires PCS 7 V8.1 or later, CPU firmware V8.1 or later, that firmware level configured in HW Config, and SEC product version 2 or later.
Record the actual installed versions, SEC identity, current PO capacity and pack sizes. Four packs do not establish their total capacity or correct allocation. Match the application's release before applying the historical procedure.
Documented ALM Upgrade Workflow
For the configuration covered by sections 2.5.4-2.5.6:
- Make the packs available on a drive accessible to ALM.
- Use
Edit > Connect target system > Connect/disconnect AS 410..., selectAdd, and choose the intended CPU from the project. - Transfer the packs to that AS by drag-and-drop.
- Open its
Onlinefolder, select the license and useLicense Key > Upgrade. - Complete Siemens' activation-file/release-file process for that upgrade. Transfer the resulting release file to the intended AS's
Onlinefolder as documented.
The upgrade initiation binds the selected packs to the SEC; it is not a reversible exploratory click. See the documented workflow.
Investigate the Disabled Command
Compare the actual ALM view with each stage above before consuming a license. Record whether the target is connected, the CPU is the intended AS, the required Online object exists and the pack is selected in the documented context.
If the command remains unavailable after matching the applicable prerequisites, retain the exact ALM version, CPU/SEC information and observed dialog state for support. No verified repair for that UI symptom was reported, and no reinstall, registry modification or CPU restart is prescribed.
Verification
After a supported upgrade completes, compare the PO volume shown for the target SEC in ALM with the approved expansion. A pack appearing under an AS view does not prove the SEC capacity changed.
For a redundant system, verify the required allocation according to its applicable procedure. Retain license and capacity records securely; do not place private activation data or license identifiers in public documentation.
Limitations and Operational Precautions
The PCS 7, ALM and CPU firmware versions, SEC product version and pack sizes are missing. Those gaps prevent a diagnosis of the disabled Upgrade command.
The cited workflow is historical and includes an activation/release stage. Confirm the process applicable to the installed product before initiating it; no turnaround-time guarantee is repeated.
Confirm the target AS and keep recoverable project/license records before an upgrade. Do not transfer packs between controllers experimentally after initiating the binding operation. No external request, license transfer or actual upgrade was performed.
Engineer FAQ
Is showing a pack under AS the final capacity check? No; inspect the upgraded SEC's PO volume.
Can the packs be treated as movable after upgrade initiation? The cited procedure binds them to the SEC.
Does the guide diagnose every disabled Upgrade control? It establishes the workflow, not this exact UI cause.