Resolving KTP900 Basic ProSave Backup Connection Failures
Siemens KTP900 Basic panels are common 9-inch HMI stations on PROFINET networks, but field engineers routinely hit the "Could not establish a connection. Check your Settings, cables, etc" dialog when attempting recipe or full-image backups with ProSave. The error is rarely a hardware fault; in nearly every case the failure is a misconfigured PG/PC access point, a WinCC/TIA version mismatch, a mismatched subnet, or a host-side firewall blocking TCP port 102. This reference walks through root cause analysis, the correct ProSave configuration, version matrix, alternate backup paths, and a complete troubleshooting matrix.
1. Problem Overview
A typical failure scenario:
- Operator laptop is directly cabled to the KTP900 Basic RJ45 port.
- Laptop can
ping 192.168.0.2successfully. - ProSave returns "Could not establish a connection. Check your Settings, cables, etc" when initiating a recipe or complete backup.
- Project was built in TIA Portal V13 SP1, technician is running V13 SP2.
- The ProSave installed under V13 SP2 is internally labeled V14.
The combination of TIA Portal V13 SP2 carrying a WinCC/ProSave V14 image is one of the most common root causes. The HMI's runtime image must match the ProSave major version, otherwise the transfer handshake is rejected silently and only a generic connection error is returned.
2. Affected Components and Catalog Numbers
| Component | Catalog Number | Notes |
|---|---|---|
| KTP900 Basic PN (9", 2nd gen) | 6AV2 123-2MB03-0AX0 | Most common variant, PROFINET interface |
| KTP900 Basic DP (PROFIBUS) | 6AV2 123-1MB03-0AX0 | PROFIBUS variant, ProSave over MPI/PROFIBUS only |
| KTP900 Basic PN (1st gen) | 6AV6 647-0AK11-3AX0 | Legacy, requires WinCC flexible / TIA V13 SP1 max |
| ProSave (V13 SP2 install) | Internal label V14.0.x | Embedded inside TIA Portal V13 SP2 installer |
| WinCC RT (V13 SP1) | 6AV2 101-...V13 SP1 | Build version 13.0.1.x |
Verify the panel's catalog number on the nameplate; the second-generation KTP900 Basic is the typical unit on shop floors today. The MLFB suffix encodes the firmware/image version, and an outdated HMI image is a frequent cause of mismatch errors.
3. Root Cause Analysis
The "Could not establish a connection" error masks several distinct faults. The ranking from most to least common in field service tickets:
- S7ONLINE access point bound to the wrong network adapter (≈50% of cases). ProSave uses the S7ONLINE access point configured in Control Panel → Set PG/PC Interface. If S7ONLINE is bound to a virtual NIC, a Wi-Fi adapter, or a disconnected Ethernet port, ProSave silently fails.
- WinCC / ProSave major version mismatch with HMI image (≈20%). TIA V13 SP2 ships ProSave labeled V14; the HMI image must be V14, otherwise the panel refuses the transfer handshake.
- Subnet / IP mismatch (≈15%). Direct cable connections require both ends in the same /24 subnet. Common mistakes: 192.168.0.2 / 255.255.255.0 on the HMI but 192.168.1.5 / 255.255.255.0 on the laptop.
- Host firewall blocking TCP/102 (≈10%). Windows Defender or a corporate endpoint agent blocks ISO-TSAP traffic on port 102 even when ICMP ping succeeds.
- ProSave running without elevated rights (≈5%). ProSave requires the same Windows rights as TIA Portal to open raw sockets on port 102.
ping only proves ICMP is permitted. ProSave uses TCP/102 (ISO-TSAP / RFC 1006). Ping success does not mean port 102 is reachable, and vice versa.
4. Prerequisites
Before opening ProSave, confirm the following:
- Administrator rights on the engineering workstation (ProSave binds to TCP/102, which requires raw socket privileges on Windows).
- TIA Portal / WinCC installed (ProSave is bundled; do not run a standalone ProSave from a third-party installer).
- Patch cable or straight-through cable — KTP900 Basic supports Auto-MDI/MDIX, so either works for direct connection.
- HMI in Transfer mode (Configuration mode → Transfer). If the panel is in Run mode with transfer disabled, ProSave will fail with the same generic error.
- Subnet: laptop and HMI must share the same /24 (e.g., 192.168.0.0/24). Disable Wi-Fi on the laptop to prevent routing ambiguity.
- Latest TIA Portal Update / Hotfix matching the HMI image. The compatibility list lives in the Siemens Online Support (article ID 109750988).
5. Step-by-Step: Fixing the S7ONLINE Access Point
The S7ONLINE access point is the single highest-leverage fix. Configure it once, and ProSave, TIA Portal, and Step 7 all use the same Ethernet path.
- Close ProSave and TIA Portal.
- Open Windows Control Panel → Set PG/PC Interface (the Siemens applet, not the Windows network settings).
- In the Access Point dropdown, select S7ONLINE.
- In the Interface Parameter Assignment Used list, pick the physical Ethernet adapter that is cabled to the KTP900 Basic. Typical identifiers:
Intel(R) Ethernet Connection I219-LMRealtek PCIe GbE Family Controller
- Click OK. Windows may prompt to allow the applet to make changes — approve.
- Reopen ProSave. The transfer dialog now routes S7ONLINE traffic out the correct NIC.
6. Step-by-Step: ProSave Connection Procedure
- Launch ProSave from the Windows Start menu (path: Siemens Automation → SIMATIC → ProSave).
- In the Device type dropdown, select KTP900 Basic or KTP900 Basic PN. Selecting the wrong device type triggers a generic connection error even when networking is correct.
- Set Connection to Ethernet.
- Enter the HMI IP address (default on a direct-cabled KTP900 Basic is
192.168.0.2, subnet mask255.255.255.0). - Choose the backup target on the host side. A complete backup file uses the
.brkextension; recipes-only exports use.rpdor.csvdepending on TIA version. - Select the backup type:
- Complete backup — HMI image, recipes, logs, user administration.
- Recipes — only the recipe database.
- User administration — only the password list.
- Logs — only the runtime log files.
- If the HMI is password-protected for transfer, enter the transfer password in the dialog.
- Click Start. The progress bar should advance within 5-10 seconds; if it stalls on Establishing connection, repeat the S7ONLINE check.
7. TIA Portal / WinCC Version Matrix
Siemens version numbering inside TIA Portal is counter-intuitive. TIA V13 SP2 contains WinCC and ProSave labeled V14. Use the matrix below to align the engineering environment with the HMI image.
| TIA Portal Install | WinCC / ProSave Internal Version | Compatible HMI Image Versions |
|---|---|---|
| V13 SP1 | V13.0.1 | V13.0.1.x |
| V13 SP2 (Update 4+) | V14.0.x | V14.0.x |
| V14 | V14.0.x | V14.0.x |
| V14 SP1 | V14.1.x | V14.1.x |
| V15 / V15.1 | V15 / V15.1 | V15.x |
| V16 | V16 | V16.x |
| V17 | V17 | V17.x |
If the project was created with V13 SP1 but the runtime image was upgraded to V14 (or vice versa), ProSave will reject the connection at the handshake. Either:
- Re-compile the project under the matching TIA version and re-transfer, or
- Install the matching ProSave from the same TIA version archive (TIA Portal DVDs ship multiple ProSave versions under
Support).
To check the HMI's runtime image version on the panel: Start Center → Settings → System → Device Version or Control Panel → OP Properties → Version.
8. Network Verification Procedure
Before trusting ProSave, prove the network path is correct using the following checks:
-
ICMP echo:
ping 192.168.0.2 -tfrom an elevated command prompt. Expect replies < 1 ms on direct cable. -
TCP/102 reachability:
Test-NetConnection 192.168.0.2 -Port 102in PowerShell. ExpectTcpTestSucceeded : True. -
ARP table:
arp -ashould list the HMI MAC address mapped to 192.168.0.2. If only the broadcast MAC shows, the wrong subnet is configured. - Disable Wi-Fi: Right-click the Wi-Fi adapter → Disable. This prevents the host routing table from preferring the wireless NIC.
-
Temporarily disable Windows Firewall:
netsh advfirewall set allprofiles state off. If ProSave succeeds, re-enable and add an inbound rule for TCP/102 on the engineering subnet.
9. Alternate Backup Methods
When ProSave cannot establish a session at all (corrupt HMI image, bricked panel after firmware update, or ProSave version drift), there are three alternate paths to retrieve recipes and user data:
9.1 SD Card Extract (if panel boots)
KTP900 Basic panels of the 2nd generation accept an SD card slot. If the HMI boots to Start Center:
- Insert a FAT32-formatted SD card.
- Start Center → Service & Commissioning → Save to Memory Card.
- The HMI writes recipes (
*.csvor*.rdb) and the user list to\\Storage Card USB\\Recipes. - Remove the SD card and copy the files to the engineering workstation.
9.2 USB Stick Extract (KTP900 Basic DP variants only)
Some second-generation Basic panels ship with a USB host port. The same Save to Memory Card path is exposed. 1st-generation Basic panels do not support USB extraction.
9.3 Direct File Read on the HMI
If the panel boots and the user has the transfer password:
- Open Internet Explorer on the engineering workstation and browse to
http://192.168.0.2. KTP900 Basic serves a minimal web interface on port 80 that exposes the recipe database and log files for download. - Download the
*.csvrecipe files directly without ProSave.
9.4 Restore via TIA Portal Project Backup
If a TIA Portal project archive (.zap13, .zap14, etc.) exists from the original commissioning, the recipe definitions are embedded in the project and can be re-transferred to a rebuilt panel via TIA Portal's HMI Device → Compile and Download. Runtime recipe values written by the operator are not in the TIA archive; they must come from ProSave or one of the alternate methods above.
10. Troubleshooting Matrix
| Symptom | Likely Root Cause | Verification | Fix |
|---|---|---|---|
| "Could not establish a connection" with successful ping | S7ONLINE bound to wrong NIC | Set PG/PC Interface shows a different adapter than the one cabled | Reassign S7ONLINE to the active Ethernet NIC |
| Ping fails, link light on NIC is on | Subnet mismatch |
ipconfig shows different /24 on host |
Set laptop to 192.168.0.1/24, HMI to 192.168.0.2/24 |
| Connection succeeds but backup aborts mid-transfer | TCP/102 blocked mid-session by antivirus | Check AV logs for the engineering workstation | Whitelist ProSave.exe in endpoint policy |
| Connection fails immediately, ping fails | Defective cable, link down, or HMI in Stop | Replace cable; check HMI power and PROFINET LED state | Replace cable, power-cycle HMI |
| Connection dialog lists "Invalid device type" | Wrong device type in ProSave | Confirm nameplate MLFB | Select "KTP900 Basic PN" exactly, no abbreviations |
| Backup completes but recipes missing from file | Wrong backup type selected | Re-run with "Recipes" type explicitly | Choose "Recipes" instead of "Complete backup" |
| ProSave V14 cannot see HMI image V13 | Major version mismatch | Check HMI Device Version | Install ProSave V13 from TIA V13 SP1 archive, or re-image the HMI |
| Transfer password prompt never appears, error returned | HMI in Run mode with transfer disabled | Start Center shows "Operating" state | Switch to Configuration mode, enable Transfer |
| Connection works on first attempt, fails after 30 minutes | S7 connection timeout on panel side | Check HMI event log for S7 timeout entries | Increase HMI S7 timeout in TIA project |
| ProSave opens but Device Type list is empty | ProSave corrupted install | Reinstall via TIA Portal repair | Control Panel → TIA Portal → Repair |
11. Sizing and Throughput Notes
Backup time scales with the recipe record count and image size. Typical figures:
| Backup Type | Typical File Size | Throughput (100 Mbps Ethernet) | Typical Duration |
|---|---|---|---|
| Complete backup (image + recipes + logs) | 40-120 MB | 8-10 MB/s effective | 15-25 s |
| Recipes only | 50-500 KB | n/a (single file) | < 2 s |
| User administration only | 2-10 KB | n/a | < 1 s |
| Logs only (24 h runtime) | 1-20 MB | 5-8 MB/s effective | 2-8 s |
Throughput is governed by the slow end of the link. The KTP900 Basic's PROFINET interface is 100 Mbps full-duplex; the engineering workstation typically negotiates 1 Gbps. Effective throughput is throttled by the panel's internal flash write speed, not the link rate.
12. Security and Operational Notes
- Transfer passwords are stored hashed in the HMI image. If the password is lost, a complete panel re-image is required; recipes must be restored from the last good backup.
- Enable Audit Trail in the TIA project to log every ProSave access. The audit entries are visible in the panel's System → Event Log after a reboot.
- ProSave over Ethernet uses unencrypted S7 communication. On shared plant networks, restrict access via managed switch ACLs or VLAN segmentation, per IEC 62443 zone-and-conduit guidance.
- Document the HMI image version and the matching ProSave version in the project folder's
README. This eliminates version drift during multi-year plant lifecycles.
13. Verification Checklist
Confirm the following before closing the work order:
- [ ]
ping 192.168.0.2 -treturns < 5 ms latency. - [ ]
Test-NetConnection 192.168.0.2 -Port 102returnsTcpTestSucceeded : True. - [ ] ProSave Device Type matches the panel's MLFB suffix.
- [ ] S7ONLINE access point is bound to the cabled Ethernet NIC.
- [ ] Windows Firewall permits inbound TCP/102 on the engineering subnet (or scoped rule for ProSave.exe).
- [ ] ProSave major version matches the HMI image major version.
- [ ] HMI is in Transfer mode (not Run with transfer disabled).
- [ ] Backup file is created at the chosen path and is non-zero bytes.
- [ ] Restored recipe data on a test bench panel matches the source values field-for-field.
Why does ProSave fail with a generic connection error even when ping succeeds?
ProSave uses TCP port 102 (ISO-TSAP), which is independent of ICMP. The most common cause is the S7ONLINE access point in Set PG/PC Interface being bound to a different network adapter than the one physically cabled to the panel. Verify with Test-NetConnection 192.168.0.2 -Port 102; if the test fails, reassign S7ONLINE to the cabled NIC.
ProSave inside TIA Portal V13 SP2 is labeled V14 — is this a bug?
Not a bug. Siemens renumbered the WinCC and ProSave versions starting with TIA V13 SP2 Update 4, so the install is internally V14 even though the shell reads V13 SP2. The HMI image version must match V14 for transfers to succeed. If the panel runs V13.0.1.x, install ProSave V13 from the TIA V13 SP1 archive instead.
Can I back up recipes without ProSave?
Yes. Insert a FAT32 SD card into the KTP900 Basic 2nd-generation panel and use Start Center → Service & Commissioning → Save to Memory Card. Recipes are exported as *.csv or *.rdb depending on the TIA version. Alternatively, the panel's built-in web interface at http://192.168.0.2 exposes recipe files for direct download.
What subnet should I use for a direct laptop-to-KTP900 connection?
Use a /24 subnet such as 192.168.0.0/24. Configure the laptop at 192.168.0.1 with mask 255.255.255.0 and leave the HMI at its default 192.168.0.2 / 255.255.255.0. Disable Wi-Fi on the laptop to avoid routing ambiguity. Auto-MDI/MDIX on the panel means either a straight-through or crossover cable works.
ProSave completes but my recipe values are zero in the backup file — what happened?
The backup captured the recipe definitions from the project, not the runtime values. Confirm "Recipes" is the selected backup type and that the source panel had the values loaded at the moment of transfer. If values are written by the operator and then overwritten by a project re-compile, the values are lost and must be re-entered manually after restore.