ProSave Cannot Connect to Siemens HMI: PN/IE vs Ethernet Fix
Symptom: ProSave reports a connection failure when attempting to load a WinCC add-on (for example, the Printer Driver PDF V1.4) onto a Comfort Panel (SIMATIC HMI TP700 Comfort / TP1200 Comfort), even though the engineering station successfully pings the panel IP. Selecting the connection type Ethernet silently fails. Selecting PN/IE succeeds. This article documents the root cause, the correct parameter selection, the TIA Portal alternative workflow, the maintenance-mode fallback, and the USB-install path for the add-on itself.
1. Problem Description
An engineer wants to install a WinCC add-on (commonly the Printer Driver PDF) onto a Comfort Panel using the standalone ProSave tool. Symptoms:
- Engineering station and panel are on the same subnet. No IP conflict. No managed switch ACL or VLAN tagging in the path.
-
ping <panel IP>returns replies with sub-millisecond latency. Network layer 3 is healthy. - Launching ProSave (Start → Siemens Automation → ProSave, or the ProSave executable inside the TIA Portal install tree) and configuring a transfer operation fails with one of the following conditions:
- The connection dialog closes with no dialog, no error, no log entry.
- ProSave reports "Connection not established", "Cannot connect to device", or "Timeout".
- ProSave hangs on "Establishing connection..." for 30-60 s and then times out.
- Switching the Connection type field between
Ethernet,PN/IE, andUSBproduces the same timeout. - The HMI Transfer channel is enabled in the Control Panel (Settings → Transfer / MPI / PROFIBUS / PROFINET → Permit → checkbox on). The
Enable Transfercheckbox is set.
The combination of a successful ping and a ProSave-level timeout is the diagnostic fingerprint of this issue.
2. Root Cause: PROFINET IO vs. S7 Transport
Comfort Panels expose two parallel transfer endpoints that ProSave can target:
| ProSave Connection type | Underlying transport | Default port | Protocol role |
|---|---|---|---|
PN/IE |
S7 / PROFINET IO RPC + TIA Portal transfer service | 102 (ISO-TSAP) / 49152-65535 (RPC dynamic) | Uses the same PROFINET stack as the engineering project download. Always available on the panel's PROFINET interface. |
Ethernet |
Raw TCP/HTTP to the panel's web/automation interface (older non-PROFINET path) | 80, 443, 1024-5000 | Targets the panel's general Ethernet services; not all add-on transfer flows route through this path on newer firmware. |
USB |
USB mass storage / RNDIS emulation | n/a | Requires the panel to be in service/transfer mode. Driver-level. |
The Printer Driver PDF V1.4 add-on and most WinCC Comfort/Advanced add-ons are deployed as PROFINET-aware runtime packages. ProSave negotiates the transfer using the S7-TSAP handshake over the PROFINET channel. When the operator selects the generic Ethernet connection type, ProSave attempts to push the package over the legacy HTTP/automation service, which does not advertise the add-on loader endpoint. The HMI panel accepts the TCP session but does not respond to the loader READ_SZL/PI_SERVICE request, ProSave times out, and the failure is silent because the connection state machine does not log to the operator.
Switching to PN/IE forces ProSave onto the PROFINET transport, which the panel's loader service is registered against. The handshake completes within a few seconds and the add-on transfer begins.
3. Solution A: Select PN/IE in ProSave
The fastest fix is the one-line parameter change inside the standalone ProSave dialog.
3.1 Prerequisites
- ProSave version matching the TIA Portal that built the project (e.g., ProSave 15.0.0.0 for TIA V15, ProSave 17.0.0.0 for TIA V17). Mismatched versions can produce identical silent failures.
- Comfort Panel with PROFINET interface enabled and an IP address in the same subnet as the engineering station.
- Windows firewall rule allowing outbound TCP 102 and the dynamic RPC range 49152-65535 to the panel IP. Siemens installer normally adds these rules during the TIA Portal setup.
3.2 Step-by-step
- Open ProSave from Start → Siemens Automation → ProSave (or via the TIA Portal install tree at
C:\Program Files\Siemens\Automation\Portal V<V>\Bin\ProSave.exe). - In the left pane, choose the device family that matches the panel: Panels → Comfort Panels → TP1200 Comfort (or TP700 Comfort).
- In the Connection group, set the Connection type dropdown to
PN/IE. Do not selectEthernet. - Set the PG/PC interface to the network adapter that is physically connected to the panel subnet (e.g.,
Intel(R) Ethernet Connection ...). Avoid virtual adapters, VPN TAP interfaces, and the Hyper-V default switch. - Set HMI address to the panel's PROFINET IP (e.g.,
192.168.0.10). - Leave Access point at
S7ONLINEunless a custom access point is mandatory. - Click Connect. Expect a green status within 5-10 s.
- Navigate to the Options → Load add-on / Install software tab. Browse to the add-on package (e.g.,
Printer_Driver_PDF_V1.4.exeor the extracted.zipfrom the Siemens support download). - Click Load. ProSave transfers the package; the panel reboots automatically. Total time 2-5 minutes.
- Verify the add-on is registered: on the panel, open Control Panel → Add-ons and confirm the Printer Driver PDF entry shows version 1.4.
PN/IE on every session. Many engineers create a desktop shortcut that launches ProSave with a /ini file pre-populated with PN/IE to avoid the silent regression.4. Solution B: Drive ProSave from TIA Portal
If the project was built in TIA Portal, the ProSave features are accessible from inside TIA. This is the supported path in TIA V14 and later and removes the standalone ProSave dialog entirely.
4.1 Prerequisites
- TIA Portal (Comfort/Advanced/Professional) installed at the same version as ProSave.
- The target Comfort Panel device is configured inside the TIA project with its PROFINET IP.
4.2 Step-by-step
- Open the TIA Portal project that contains the Comfort Panel device.
- In the project tree, right-click the panel device (e.g., HMI_1 [TP1200 Comfort]) and select Load to device (or use the menu Online → Extended download to device).
- TIA opens the Extended download to device dialog. Confirm the panel's PROFINET interface is selected as the PG/PC interface and the target IP matches the panel.
- Click Load. The project compiles and transfers. Add-ons referenced by the project are pushed automatically.
- For add-on-only transfers (such as Printer Driver PDF) without recompiling the project, use Online → HMI device maintenance → Install add-on. The dialog reuses the same TIA-engineered connection profile; ProSave runs as a child process and inherits the correct transport settings.
Calling ProSave from inside TIA guarantees the PN/IE transport is selected and that the access point and PG/PC interface are consistent with the project. This is the recommended path for reproducible add-on deployment.
5. Solution C: Maintenance Mode Reset
If the panel's runtime is in a state where it cannot accept transfer requests (corrupt add-on, frozen transfer service, locked loader), bring the panel into maintenance mode via ProSave and retry.
5.1 Procedure
- In ProSave (with
PN/IEselected per Section 3), connect to the panel. - Navigate to the Operating system update / Reset tab.
- Click Reboot in maintenance mode. The HMI device restarts and the Maintenance Mode dialog appears for 10 minutes.
- Within the 10-minute window, repeat the add-on load (Section 3, step 8-9). Maintenance mode bypasses the runtime and exposes the loader service directly.
For a full factory reset of the panel from maintenance mode, see the official TIA Portal Cloud documentation: Resetting an HMI device to factory settings via ProSave.
6. Solution D: USB-Stick Install Path
ProSave is for backup and restore images and for loader-level add-on deployment over the network. For a simpler, network-free install of a runtime add-on, the panel's USB port can be used directly. This is useful when the engineering station cannot reach the panel at layer 2/3 (e.g., remote site, no crossover cable available).
6.1 Procedure
- Extract the add-on package to the root of a FAT32-formatted USB stick. The expected layout depends on the add-on; the Printer Driver PDF package ships with a
setup.confand a firmware directory. - Power off the Comfort Panel.
- Insert the USB stick into the panel's USB port.
- Power on the panel. The loader detects the package and prompts to install.
- Confirm. The panel installs the add-on and reboots.
The USB path is independent of ProSave, the PG/PC interface, and the transport selection. Use it as the fallback whenever the network path is misbehaving.
7. ProSave vs. TIA Portal: Capability Boundary
ProSave and the TIA Portal transfer dialogs share an underlying loader, but the user-visible feature set differs. Pick the right tool for the operation.
| Operation | Standalone ProSave | TIA Portal | USB stick |
|---|---|---|---|
| Full image backup (HMI image) | Supported (Backup tab) | Supported (Online → HMI device backup) | Not supported |
| Image restore to identical panel | Supported (Restore tab) | Supported | Not supported |
| Project download (compile + transfer) | Not supported (project is TIA-only) | Supported (Load to device) | Not supported |
| Add-on install (Printer Driver PDF, Sm@rtServer, Audit, etc.) | Supported (Options → Install add-on) | Supported (Online → HMI device maintenance → Install add-on) | Supported (panel-side loader) |
| Operating system update | Supported (OS update tab) | Supported | Supported (firmware-only) |
| Maintenance mode reboot | Supported | Supported (Online → HMI device maintenance) | Not supported |
| Factory reset | Supported (from maintenance mode) | Supported | Not supported |
Operationally, treat ProSave as the image-tool and TIA Portal as the project tool. Add-ons sit in the overlap; either tool can deploy them, but TIA Portal is the supported path for TIA-engineered fleets.
8. Field-Proven Diagnostic Matrix
When ProSave fails to connect, walk this matrix before assuming the network is at fault.
| Symptom | Likely cause | First action |
|---|---|---|
ProSave timeout, ping OK, Ethernet selected |
Wrong connection type for add-on transfer | Switch to PN/IE (Section 3) |
ProSave timeout, ping OK, PN/IE selected, ProSave and TIA Portal versions differ |
Version mismatch between ProSave and panel runtime | Match ProSave version to the TIA Portal that built the project |
| ProSave timeout, ping OK, Windows firewall blocks outbound TCP 102 / RPC | Corporate firewall policy | Add allow rules for the panel IP; verify with Test-NetConnection -Port 102 in PowerShell |
| ProSave timeout, panel has static IP, default gateway on engineering station is wrong | Engineering station cannot route ARP replies back | Set engineering station IP in the same /24 with no gateway, or correct the gateway |
| ProSave timeout, panel shows Transfer disabled in Control Panel | Operator previously disabled transfer mode | On the panel, Control Panel → Transfer → enable Permit checkbox |
| ProSave timeout, multiple network adapters (Wi-Fi + Ethernet) active | PG/PC interface routed to wrong adapter | Set PG/PC interface to the wired adapter connected to the panel |
| ProSave hangs forever on Establishing connection | Panel loader service crashed; runtime in undefined state | Reboot panel into maintenance mode (Section 5), retry |
| Add-on transfer starts but fails at 50% with CRC error | Package corruption on local disk or USB | Re-download the add-on from Siemens support, verify SHA-256, retry |
| Add-on installs but printer does not appear in runtime | Add-on installed to wrong slot, or printer not configured in the project | Open TIA project, configure the printer under HMI → Print settings, recompile and download |
9. Verification Checklist
After deploying the add-on with any of the above solutions, run the following checks to confirm a clean install.
-
Add-on registration. On the panel, open Control Panel → System → Add-ons. Confirm Printer Driver PDF is listed with version
1.4.0(or the expected version) and status Installed. -
Loader log. In ProSave, open View → Event log for the most recent transfer. Look for a
Transfer completed successfullyline and aReboot requestedline. NoERRORorWARNentries should be present. - Project-side integration. In TIA Portal, open the HMI project, navigate to Runtime settings → Print jobs. The configured print job should now show the PDF printer as available.
- Functional test. Trigger a print job from the runtime (e.g., print an audit log). Verify a PDF file is produced on the configured network share or USB storage.
- Panel health. Ping the panel again. Confirm it is reachable post-reboot. The transfer should not have changed the IP, but a brief period of ARP flux during reboot is normal.
10. Common Misconceptions
- "If ping works, ProSave will work." False. Ping confirms layer 3 only. The S7/loader transport runs on TCP 102 plus dynamic RPC ports and can be blocked while ICMP remains open.
- "ProSave can install any add-on to any HMI." False. ProSave is built around the image backup/restore flow. Add-on install is supported, but project-level downloads are TIA-only. The user-facing ProSave help does not call out the TIA limitation explicitly.
- "Switching to USB fixes everything." Partially true. The USB port handles add-on and firmware updates. It does not handle image backup/restore and does not handle project downloads.
- "Maintenance mode is only for OS updates." False. Maintenance mode exposes the loader service and is the correct state for any loader-level operation, including add-on install on a frozen runtime.
11. Preventive Recommendations
-
Document the connection type per panel class. Add a column to the panel commissioning sheet with the required ProSave connection type. Comfort Panels and Unified Comfort Panels use
PN/IEfor add-on transfer; older Multi Panels and Basic Panels vary. - Pin ProSave to the TIA Portal version. Co-install ProSave and TIA Portal at the same version. Mixing ProSave V15 with a TIA V16 project produces intermittent loader failures that look like network problems.
-
Pre-stage add-on packages locally. Keep
Printer_Driver_PDF_V1.4.exeand other add-ons on a local share, with checksums, so transfers do not depend on the Siemens download portal at the time of commissioning. - Standardize on the TIA Portal transfer path. For fleet rollouts, drive all add-on loads from TIA Portal's Online → HMI device maintenance → Install add-on. This eliminates the standalone ProSave dialog and the connection-type ambiguity.
- Use a maintenance-mode reboot as the universal recovery step. When a panel's loader is stuck, the 10-minute maintenance-mode window is the safest way to recover without a factory reset.
12. Related Manuals and References
- Resetting an HMI device to factory settings via ProSave — TIA Portal Cloud, official Siemens documentation.
- SIMATIC HMI Comfort Panels — Product family page for TP700 / TP900 / TP1200 / TP1500 / TP1900 / TP2200 Comfort Panels.
- WinCC Comfort / Advanced system manual, chapter Transferring projects — covers ProSave usage and PN/IE transport selection.
- SIMATIC HMI Operator Panels Operating Instructions, chapter Commissioning → Transfer (data channel) — covers the panel-side Enable Transfer setting and maintenance-mode entry.
FAQ
ProSave times out on a TP1200 Comfort even though ping works. What is the single most common fix?
Open the ProSave Connection dialog and change the Connection type from Ethernet to PN/IE. The TP1200 Comfort add-on loader is registered against the PROFINET transport; the generic Ethernet service does not expose the loader endpoint, so the connection times out silently.
Can I install the Printer Driver PDF V1.4 add-on without ProSave?
Yes. Two alternatives: (1) Use TIA Portal's Online → HMI device maintenance → Install add-on dialog, which drives ProSave as a child process with the correct PN/IE transport selected. (2) Copy the add-on package to a FAT32 USB stick, insert it into the panel, and reboot — the panel's loader installs the package directly.
Why does ProSave fail when launched standalone but succeed when launched from TIA Portal?
Standalone ProSave defaults the connection type to Ethernet on every launch and does not remember the previous selection. TIA Portal initializes the transfer with PN/IE and the PG/PC interface bound to the project's PROFINET subnet, so the loader endpoint is reachable. Either launch ProSave from TIA or set PN/IE manually each session.
How long is the maintenance-mode window on a Comfort Panel?
Exactly 10 minutes from the moment the panel enters maintenance mode. The loader service is exposed for the full window; if the add-on transfer exceeds 10 minutes, the panel exits maintenance mode and the runtime restarts. For large add-on bundles, pre-stage the package locally to stay inside the window.
Does a successful ping guarantee that ProSave can connect?
No. ICMP is handled by the panel's IP stack and is independent of the S7 and loader services. A ProSave timeout with a successful ping indicates a transport-stack problem (wrong connection type, blocked TCP 102, wrong PG/PC interface, loader service down), not a network problem. Treat the two as separate layers and verify the S7/loader path independently.