Overview
When Siemens releases a new S7-300 CPU, ET 200 station, or function module, two completely separate things can be updated: the engineering database on your programming device and the firmware running on the physical hardware. Adding a brand-new CPU type to a STEP 7 project is a database-only operation on the programming PC. Nothing is downloaded to the PLC, the CPU firmware is not touched, and the project does not need to be re-compiled unless you actually use the new device.
The hardware catalog in STEP 7 V5.x (HW Config) and in TIA Portal is fed by Hardware Support Packages (HSPs). Each HSP carries the GSD/EDD data, article numbers, firmware version metadata, and slot rules for one or more new MLFBs. Installing the HSP makes the new device selectable in the catalog so it can be dragged into a station.
Engineers routinely confuse three concepts that share the word update:
| Update type | Where it runs | What it changes | Network required |
|---|---|---|---|
| Hardware catalog update / HSP | Programming PC | STEP 7 / TIA Portal device library | Only for online download |
| Firmware update | Online connection to target | CPU, IM, or module operating system | Yes — MPI / PROFIBUS / PROFINET |
| STEP 7 / TIA version upgrade | Programming PC | Engineering tool major release | No |
Prerequisites
| Item | Detail |
|---|---|
| STEP 7 V5.x version | V5.5 SP4 or higher recommended; V5.6 for latest 6ES7 catalog entries |
| TIA Portal version | V15.1 or higher for current S7-300/400/ET 200 families |
| Windows account | Local administrator — HSP setup writes to ProgramData and registry |
| Free disk space | 3–6 GB for the full HSP collection |
| Online source | Siemens Industry Online Support (HTTPS to automation.siemens.com) |
| Offline source | HSP Collection .exe downloaded once and replicated to air-gapped PCs |
| Project archive | Mandatory — archive the STEP 7 project to *.zip before installing HSPs |
Verify the current service pack level before starting. In SIMATIC Manager, Help → About shows the exact build (for example, STEP 7 V5.6 + SP1). In TIA Portal, Help → About SIMATIC TIA Portal lists installed product versions including the HSP collection date. The HSP build number must be greater than or equal to the build date of the engineering tool installation.
STEP 7 V5.x: Online HW Update from HW Config
The fastest path is to let HW Config fetch the HSP directly from the Siemens server. The dialog was added in STEP 7 V5.4 and is the standard workflow from V5.5 onward.
- Launch SIMATIC Manager and open the project that will host the new device.
- Double-click Hardware in the project tree to open HW Config.
- In HW Config, click Tools → Install HW Updates… (German: Extras → HW-Updates installieren…).
- In the dialog, select Download from Internet. If a proxy is required, configure it via Windows Internet Options or use the offline file-system option described below.
- Wait for the HSP index to load — typically 30–90 seconds over a corporate link.
- Tick the HSPs to install. To accept the full current collection, click Select All. To minimise footprint, expand the SIMATIC 300 / SIMATIC 400 / ET 200 nodes and pick only the families in scope.
- Click Install. Status messages stream into the dialog; each HSP can take 5–60 seconds. Total time for a full collection is typically 5–20 minutes on a recent workstation.
- When prompted, restart HW Config (or SIMATIC Manager) to register the new catalog entries.
After restart, expand SIMATIC 300 → CPU-300 in the hardware catalog. The new CPU type (for example a fresh CPU 319-3 PN/PN variant) is now listed and can be dragged into the station or substituted for the existing slot-2 CPU.
STEP 7 V5.x: Offline HSP Installation
Air-gapped programming PCs require the offline route. Siemens publishes a single self-extracting collection that contains every current HSP for STEP 7 V5.x plus all GSD/EDD files for PROFIBUS and PROFINET slaves.
- From an internet-connected workstation, navigate to the Siemens Industry Online Support entry HSP — Collection for STEP 7 V5.x (entry ID 23183356). Always pick the highest build whose minimum STEP 7 version matches your installation.
- Download the executable (for example
HWC_S7V5x_V2024_01.exe, file size typically 1.5–3 GB). - Copy the .exe to the engineering PC via approved removable media.
- Right-click the file → Run as administrator. The package self-extracts to
%TEMP%\HWC_S7V5xand then launches the integrated setup. - The setup reads your installed STEP 7 version and presents only compatible HSPs.
- Select the HSPs to install and confirm. The installer writes catalog data into
%ProgramFiles%\Siemens\Automation\HWConfig\Catalog(path varies by version). - Restart SIMATIC Manager.
The same collection also contains the GSD files needed for PROFIBUS slaves and the EDD/XML for newer PROFINET devices, so one download covers both classic HW Config and the device library.
TIA Portal: Hardware Support Package Installation
In TIA Portal V13 and later, the equivalent of the V5.x HW Update is the HSP installed via Options → Support Packages. TIA Portal handles the same family of devices but uses a unified installer that covers S7-300, S7-400, ET 200, HMI, and SINAMICS in one operation.
- Open TIA Portal. Close all open projects to release catalog locks.
- Select Options → Support Packages. The Support Packages editor opens.
- Choose one of three sources:
- Download from the Internet — pulls HSPs directly from the Siemens server.
-
Install from the file system — point to a downloaded
*.hspor*.ziparchive. - Install from the TIA Portal installation medium — ships with newer TIA Portal DVD images.
- Select the desired HSPs in the list. Click Install.
- Restart TIA Portal when prompted. New devices appear in the Hardware catalog under the appropriate folder (for example Controllers → SIMATIC S7-300 → CPU).
The same HSP may include GSDML, GSD, and EDD data, so installing one package often unlocks multiple new devices across PROFINET, PROFIBUS, and HART segments. The installation log is written to %LOCALAPPDATA%\Siemens\Automation\Logs\HSPInstall.log — keep this file if you need to escalate an installation failure to Siemens support.
Firmware Update — Separate Workflow
Adding a CPU to the hardware catalog is not the same as updating the CPU firmware. Firmware updates are written to the physical device over an online connection and always cause a CPU restart with a stop-run transition. Plan a controlled outage; live updates on a running process are not supported.
Firmware update on S7-300 CPUs
- Establish an online connection to the CPU via MPI, PROFIBUS, or PROFINET.
- In SIMATIC Manager, right-click the CPU → PLC → Update Firmware (German: Zielsystem → Firmware aktualisieren).
- Browse to the firmware file. S7-300 firmware files ship as
*.upd(for exampleCPU_319-3_PN_PN_V308.upd) and are available on the Siemens support pages for each MLFB. - Confirm the operation. The CPU goes to STOP, performs the update, and restarts. The diagnostic buffer records Entry 0x4300 "Firmware update successful" on completion.
Firmware update on ET 200 stations and I/O modules
For distributed I/O, use the SIMATIC Automation Tool, the PRONETA utility, or the Web server of the head-end module to push firmware. PROFINET field devices accept firmware updates over the same network as cyclic I/O — no module swap required. Field-device firmware files use the *.ffw extension on Siemens hardware.
Verification
After installing the HSP, run the following checks before modifying the live project:
- Catalog presence. In HW Config, expand the catalog tree and confirm the new MLFB is listed under the expected family. Right-click → Properties should show Article No., Firmware version, and slot rules.
- Station compile. Insert the new CPU into a test rack (or substitute it for the existing slot-2 CPU) and click Station → Save and Compile. Compilation must complete with 0 errors and 0 warnings. A typical S7-300 station compiles in <5 s on a modern workstation.
- Consistency check. Station → Consistency Check must report "No errors". Pay attention to slot rules — new CPU variants sometimes change interrupt and process image assignments.
- Diagnostic buffer offline read. Not required for a catalog update, but useful if you also performed a firmware update: PLC → Diagnostics/Settings → Diagnostic Buffer should show a clean boot with no Firmware mismatch entries.
- Online catalog version. Compare the online "Module Identification → IM data" against the catalog version. A mismatch is informational, not an error, but should be tracked in the change log.
Version Compatibility Matrix
| STEP 7 / TIA version | Minimum HSP build | Typical new devices supported |
|---|---|---|
| STEP 7 V5.5 SP4 | HWC V2020.x or earlier | CPU 319-3 PN/PN FW 3.x, ET 200S IM 151-8 PN/DP FW 3.x |
| STEP 7 V5.6 | HWC V2022.x | CPU 319-3 PN/PN FW 4.x, new IM 155-6 PN HF |
| STEP 7 V5.6 SP1 | HWC V2024.x | CPU 151 migration / S7-300 last-buy variants |
| TIA Portal V15.1 | HSP V15.1.0.1+ | S7-300/400 last-time-buy, ET 200SP HF |
| TIA Portal V16 | HSP V16.0.0.x | All S7-300/400 catalog through end of life |
| TIA Portal V17 / V18 | HSP V18.x | Maintained ET 200 families, new diagnostics features |
Troubleshooting Matrix
| Symptom | Likely cause | Corrective action |
|---|---|---|
| Install HW Updates greyed out | HW Config has no project loaded, or project is read-only | Open a writable project and re-enter HW Config |
| HSP install fails with version mismatch | HSP newer than STEP 7 SP level | Install required service pack first, or download older HSP collection |
| New CPU not in catalog after restart | Catalog tree not refreshed | HW Config → View → Update Catalog (F5) |
| Station invalid after substitution | Original CPU HSP was removed | Re-install the older HSP or substitute to an installed catalog entry |
| Firmware update aborts with SF LED | Wrong FW file for MLFB | Cross-check Article No. in HW Config vs firmware download page |
| Access denied during HSP install | Insufficient Windows rights | Run setup as administrator |
| HSP install hangs at 0% | Proxy or TLS interception breaking Siemens support server | Use offline .exe route via approved removable media |
| TIA Portal shows duplicate device entries | Multiple HSPs added the same MLFB | Uninstall older HSP in Options → Support Packages → Installed |
| PLC → Update Firmware menu disabled | No online connection, or target CPU catalog version lower than firmware file | Establish online first; install matching HSP |
| Catalog entry shows wrong firmware revision | Older HSP still active after installing newer one | Restart HW Config and SIMATIC Manager; do not delete old HSP if device is in active project |
Common Pitfalls
Using Install HW Updates to change CPU firmware. The dialog updates the catalog only. To change firmware you must download the *.upd file separately and flash the CPU over an online connection. The two operations are sequenced but independent.
Updating the catalog without archiving the project. If a subsequent project roll-back is required, the catalog state may not be reversible without a matching HSP. Always create a SIMATIC archive (*.zip) before installing.
Mixing STEP 7 versions across team members. One engineer on V5.6 can add an HSP that a colleague on V5.5 cannot see. Standardise the SP level in a team-level baseline document.
Forgetting admin rights. The HSP setup writes to HKLM\SOFTWARE\Siemens\Automation and to %ProgramFiles%\Siemens. Without elevation the installer rolls back silently and only writes a partial entry to the setup log.
Confusing GSD with HSP. PROFIBUS slave GSD files and PROFINET GSDML files are delivered inside the HSP collection but can also be imported individually via Options → Install GSD File in HW Config. Use the per-device import when you only need a single slave; use the HSP when adding new CPUs or ET 200 heads.
Field-Procedure Summary
- Confirm STEP 7 / TIA Portal version and SP level.
- Archive the project (SIMATIC Manager: File → Archive; TIA Portal: Project → Archive).
- Online: HW Config → Tools → Install HW Updates… (or Options → Support Packages in TIA).
- Offline: download the HSP Collection .exe and run as administrator.
- Restart the engineering tool.
- Insert or substitute the new device; Save and Compile; Consistency Check.
- For firmware-only updates on existing devices, use PLC → Update Firmware separately.
What is the difference between HW Update and firmware update in STEP 7?
HW Update (HSP) installs new module entries into the engineering software's catalog on the programming PC only — no online connection required. Firmware update writes a new operating system to the physical CPU or module over MPI, PROFIBUS, or PROFINET and always causes a CPU restart with a stop-run transition.
Do I need to update the firmware to add a new CPU type to my project?
No. Adding a new CPU type to a STEP 7 project is purely a catalog operation on the programming PC. The CPU firmware on existing hardware is unchanged. You only need a firmware update when the physical CPU already in the cabinet must run a newer operating system revision.
Where do I download the HSP collection for STEP 7 V5.x?
The official HSP Collection for STEP 7 V5.x is published on the Siemens Industry Online Support portal as entry ID 23183356. Always pick the highest build whose minimum STEP 7 version matches your installed service pack.
Why is Install HW Updates greyed out in HW Config?
Either no project is loaded, the project is read-only on the file system, or HW Config is running from a context without write permission. Open a writable project, confirm read/write on the project folder, and re-enter HW Config from SIMATIC Manager.
Can I install an HSP without internet access on my engineering PC?
Yes. Download the HSP Collection .exe on an internet-connected workstation, copy it to the engineering PC via approved removable media, and run it as administrator. The setup detects your STEP 7 version and installs only compatible HSPs.