STEP 7 HW-Update Errors: Installing Hardware Support Packages

Problem Description

After a fresh installation of SIMATIC Manager STEP 7 V5.5 or V5.6 and a subsequent HW-Update (Hardware Update) against an existing project, engineers working on safety programs (S7 Distributed Safety, F-CPU, F-Signal Modules) frequently encounter a non-recoverable configuration error. The HWConfig editor cannot resolve one or more devices in the station, the diagnostic dialog lists several specific Hardware Support Packages (HSPs) that the system reports as missing (commonly HSP 232 and HSP 242), and certain module slots display a yellow "?" placeholder rather than the actual order number (MLFB). The online/offline comparison cannot complete, blocks cannot be modified, and the project cannot be recompiled.

This is not a GSD/GSDML problem. Siemens catalog modules that reside in the central rack or in the PROFINET/PROFIBUS device tree of HWConfig are not loaded from *.gsd or *.gsdml files. They are registered through HSP plug-ins that extend the STEP 7 hardware catalog. Without the matching HSP installed, the catalog has no definition for the module and HWConfig cannot render its slots, parameters, or diagnostics.

Symptoms and Error Messages

The following conditions confirm that the root cause is a missing HSP rather than a corrupt project or a STEP 7 licensing issue:

Root Cause Analysis

STEP 7 V5.5 was released in mid-2010 and V5.6 in 2014. Both have a frozen hardware catalog at the time of release. Every Siemens catalog module released after that freeze — including the bulk of F-CPUs (CPU 315F-2 PN/DP, 317F-2 PN/DP, 319F-3 PN/DP), ET 200S / ET 200pro / ET 200MP F-modules, CP 343-1 Lean/Advanced variants, and the newer SCALANCE switches — is delivered exclusively through Hardware Support Packages.

The HSP numbering is sequential and chronological:

• HSP xxx — bundled by year/quarter of release.
• HSP 232 — adds modules from the 2014 release window.
• HSP 242 — adds modules from the 2016 release window.
• Newer packages continue the sequence through HSP 250+, with the latest cumulative HSP rollup published quarterly.

When you trigger Options → Install HW Updates in HWConfig, STEP 7 checks each configured module's order number against the union of the base catalog and all installed HSPs. If the order number is not present, the wizard emits a dialog identifying the missing HSP(s). The original engineer typically mistakes this for a GSD-file problem because the same dialog is reused by STEP 7 to indicate missing DP-slave descriptions — but the catalog path inside the dialog makes the distinction explicit.

Understanding the HSP Architecture

An HSP is a self-extracting installer (*.exe) that drops catalog fragments, bitmap libraries, and parameter dialog templates into the STEP 7 installation tree:

• ...\SIEMENS\STEP7\S7DATA\HSP\<hspnr>\ — module catalog fragments (binary *.hcf files).
• ...\SIEMENS\STEP7\S7DATA\HSP\BITMAP\ — module faceplate bitmaps.
• ...\SIEMENS\STEP7\S7DATA\HSP\FBD\ — FBD/F-LAD symbol files for F-modules.
• ...\SIEMENS\STEP7\S7DATA\HSP\PARAM\ — parameter dialog XML templates.

Each HSP is additive and reversible. Installing a newer HSP never removes an older one — it overlays newer catalog entries while preserving the older set. Uninstalling an HSP (via Windows Programs and Features) restores the catalog to the state at the previous HSP level.

STEP 7 V5.5 SP4 and V5.6 accept HSPs only up to a build-number ceiling. If a project was authored on STEP 7 V5.7 (the final classic release, also branded "STEP 7 V5.7") with an HSP newer than what V5.5/V5.6 will load, you must either upgrade the engineering station to V5.7 or have the project owner re-save it with a compatible HSP set.

Prerequisites

1. STEP 7 V5.5 SP4 or STEP 7 V5.6 installed and licensed. Confirm the installed version via SIMATIC Manager → Help → About. Note the exact build number (e.g. K5.5.4.0) — this determines which HSP rollup is compatible.
2. Local Administrator rights on the engineering station. HSP installers write to %ProgramFiles%\Siemens\Automation and to HKLM\SOFTWARE\Siemens\Automation.
3. No STEP 7 instances running. Close SIMATIC Manager, HWConfig, S7 Distributed Safety, and the S7-PCT / S7-FCT tools before installing.
4. A reliable Siemens Support download session. The HSPs are distributed exclusively through the Siemens Industry Online Support portal and require a registered Siemens account (free of charge).
5. Sufficient disk space — approximately 600 MB free per HSP for the staged installer plus the expanded catalog footprint.

Step-by-Step: Installing the Missing HSPs

1. Identify the exact HSP numbers reported as missing. Open SIMATIC Manager → HWConfig on the affected station. The HW-Update dialog lists each missing HSP by its numeric ID (commonly 232 and 242, but the dialog can report any in the sequence). Note every ID.
2. Download the current HSP rollup. Open the official Siemens Knowledge Base entry 23183356 — Hardware Support Packages for STEP 7 from V5.6 (HSPs). The entry hosts the cumulative HSP rollup that bundles every released HSP from the catalog inception through the latest quarterly cut. The file name follows the pattern HSP_<year>_<quarter>_STEP7_V56.zip.
3. Verify the download integrity. The ZIP contains an SHA-256 checksum file (checksums.sha256). Validate against the value published on the Siemens support page to rule out corruption during transfer.
4. Extract the ZIP to a local staging directory such as C:\Temp\HSP\. Do not run the installers from a network share — HSP installers must resolve relative paths in their payload.
5. Install the most recent HSP first. Siemens HSPs are forward-compatible when installed in descending order (newest first), but reverse order can leave dependent catalog fragments unresolved. Double-click the highest-numbered .exe, accept the UAC prompt, and follow the wizard. The installer detects your STEP 7 install path automatically.
6. Install each remaining HSP in descending numeric order. Repeat for every HSP number listed in the original error dialog. Each installation takes 30 s to 2 min and concludes with a success dialog; click Finish.
7. Reboot the engineering station. Several HSP installers register COM components and update the STEP 7 license cache. A reboot is the only way to guarantee a clean state.
8. Confirm installation. Re-open SIMATIC Manager and select Options → Installed HW Updates. A table lists every installed HSP by number, release date, and catalog coverage. Cross-check that every ID reported as missing is now present.

Inline HWConfig Repair Procedure

1. Open the project in SIMATIC Manager and double-click the Hardware object of the affected station.
2. HWConfig loads the station. Every previously "?" module now resolves to its proper order number.
3. Select Station → Check Consistency. The consistency check must complete with zero errors before any further work.
4. If a module still shows "?", right-click the slot and select Replace Object. Browse the Siemens catalog — the module's entry now exists at the correct path (e.g. SIMATIC 300 → F-Modules). Confirm.
5. Save and compile the station.

Safety Program Specific Considerations

If the affected project contains a safety program (S7 Distributed Safety V5.4 SP5+ or S7 F-ConfigurationPack), the HSP repair must complete before any safety signature work:

• F-CPU identification: Each F-CPU has a fixed F-capable catalog entry under SIMATIC 300/400 → CPU-300F/400F. HSPs that pre-date the F-CPU release cannot describe its safety-related parameters, and the safety compiler will fail with F-signature errors. Always install the HSP rollup that introduced the CPU generation you are working with.
• F-signal modules (SM 326F, SM 336F): Listed under F-I/O. Their channel-level diagnostics and PROFIsafe slot mapping are catalog-resident. A missing HSP causes the F-shared DB generator to fail.
• CP 343-1/CP 443-1 with PROFIsafe: Older releases required a separate F-ConfigurationPack. Modern HSPs integrate the F-ConfigurationPack catalog so a single HSP install repairs both the standard and safety view.
• S7 F Systems (for S7-400FH): Requires its own HSP layer in addition to the base catalog. Verify the F-Systems HSP version under Options → Installed HW Updates before attempting to compile an F-program.

Verification

1. Catalog inspection: In HWConfig, browse SIMATIC 300 → CPU-300F and confirm the previously missing F-CPU appears with its full order number (e.g. 6ES7 317-2FK14-0AB0).
2. Station consistency: Station → Check Consistency must report "No errors".
3. Online/Offline comparison: Right-click the station and select Compare Offline/Online. The comparison must complete without aborts.
4. Block edit access: Open every F-block (F-FB, F-DB, F-FC) in the program editor. Each block must open in write mode and not be marked read-only.
5. Safety compile: In S7 Distributed Safety editor, run Compile → Safety Program. The compile must finish with a fresh F-signature displayed at the end of the log.
6. Download test: With a test PLC of the correct MLFB connected, perform a full download. The PLC must accept the configuration without reporting SDB or OB errors.

Troubleshooting Matrix

Preventive Recommendations

• Standardize on the latest HSP rollup across every engineering station in a department. Mixed HSP levels lead to non-reproducible project binaries.
• Document the HSP build in the project header (SIMATIC Manager → File → Properties → Comment). Format: HSP rollup: 2024-Q4 (KB 23183356).
• Image the engineering station after a successful HSP install so the catalog state can be re-deployed without manual download.
• Subscribe to Siemens HSP notifications on the Siemens Support RSS feed for entry 23183356 — the entry is updated quarterly.
• Keep the original project ZIP before any catalog repair. If a downstream tool mishandles the repaired station, the original can be re-loaded.

FAQ