Configure PCS 7 AS Bundles Missing from the Project Wizard

If a PCS 7 AS bundle is missing from the project wizard, identify its delivered components before creating or adapting the station. Siemens documentation identifies 6ES7654-6CL04-3BF0 as a CPU 410-5H package, but a verified mapping for 6ES7654-5EK03-3BF0 and a wizard correction for PCS 7 V9.0 SP2 were not established. Do not substitute a CPU 417-4 for an intended CPU 410E solely to complete the wizard.

Identify the Delivered Automation System

A missing bundle in the PCS 7 V9.0 SP2 project wizard does not establish that its individual hardware components are unsupported. Conversely, choosing a similar-looking bundle does not establish that the resulting rack matches the delivered automation system. Keep the commercial bundle order number separate from the order numbers and firmware of its constituent modules.

The reported discrepancy also occurred with PCS 7 V9.1. No independently verified wizard update or release note establishes a fix for these particular entries.

What Is Verified for 6ES7654-6CL04-3BF0

Siemens' historical SIMATIC PCS 7 Standard Architectures, October 2015, Tables 16-8 and 16-9, identifies 6ES7654-6CL04-3BF0 as a single AS containing a CPU 410-5H, one DP module, two PROFINET IO interfaces, a 500-PO System Expansion Card, AS RT PO 100, two CP443-1 IE processors, a UR2 aluminum rack and one UC 120/230 V, 10 A power supply.

That bill of material identifies the historical package; it is not a PCS 7 V9.0 SP2 hardware-compatibility statement. The distinction between 500-PO SEC capacity and AS RT PO 100 also matters: these entries describe different items, rather than contradictory CPU identities. Siemens standard architectures, pp. 185–186

Build a Hardware Comparison Before Editing

Use the following project-specific engineering approach on a backed-up project copy; it is not a verified repair for the wizard catalog.

Record the full commercial order number from the delivery documentation. For 6ES7654-5EK03-3BF0, obtain its actual bill of material; its CPU identity has not been independently established here.
Record each installed module's order number, slot and firmware, together with the rack, power supply, SEC and communication interfaces.
Compare those details with the generated offline hardware configuration. A CPU 417-4 in a proposed wizard station must not be accepted as equivalent to an intended 410E merely because the bundle label seems close.
Confirm that the exact component and firmware combination is released for the installed PCS 7/STEP 7 environment before selecting it in the hardware catalog.
Resolve component mismatches in the offline design before planning any compilation or download. Record network and connection implications separately.

The expected output is a component-by-component comparison and an identified supported configuration, not a successful wizard click.

Verification

Compare the final offline rack against the delivery bill of material and actual module labels. Confirm CPU identity, firmware, slot assignments, interfaces, CP types and licensing items independently. Record the installed PCS 7 version and any hardware-support package used.

For 6ES7654-6CL04-3BF0, use the cited historical bill of material as a cross-check, not as proof that every later firmware revision is supported. For 6ES7654-5EK03-3BF0, the missing authoritative bill of material remains the decisive unresolved evidence.

Limitations and Operational Precautions

An authoritative mapping for 6ES7654-5EK03-3BF0 and a version-specific wizard repair were not established. A reported suggestion to choose a nearby bundle and adapt it is therefore an engineering adaptation requiring a full hardware review, not a universal product procedure.

Retain a recoverable project backup and the current running configuration. Do not download a speculative CPU substitution to a production AS. Hardware, communication and redundancy changes require a separately reviewed commissioning and rollback plan.

Engineer FAQ

Does absence from the wizard prove that the AS cannot be engineered?
No. The missing commercial bundle and the availability of supported individual components are separate questions.

Can I treat a CPU 417-4 selection as a CPU 410E?
No supported equivalence is established. Confirm and configure the actual CPU and its applicable firmware.

Technical References

Siemens — SIMATIC PCS 7 Standard Architectures, October 2015, Tables 16-8 and 16-9, pp. 185–186 — historical component description for 6ES7654-6CL04-3BF0.

PCS 7 hardware configuration

Configure PCS 7 AS Bundles Missing from the Project Wizard