Resolving ProSave Connection Failure on MTP1200 Unified HMI

David Krause16 min read
HMI / SCADASiemensTroubleshooting
Licensed PE Working through this on a live machine? A Maine-licensed engineer can take it from here — included with IMD hardware, by the hour for everything else. Book an engineer

Resolving ProSave Connection Failure on Siemens MTP1200 Unified Comfort HMI

1. Problem Description

Engineers commissioning or recovering a Siemens SIMATIC HMI MTP1200 Unified Comfort panel frequently encounter a complete loss of Ethernet communication between the Siemens ProSave service tool and the panel. The classic symptom pattern is:
  • The HMI boots into a normal operating screen, but the IP address displayed on the panel shows 0.0.0.0 in the upper right corner, or the X2/X1 port shows no valid address.
  • The panel's MAC address is still listed in the corner (panel hardware is alive), but no IP can be pinged.
  • ProSave reports "Waiting for connection", "Connection to the HMI device could not be established", or "Device not found".
  • Both X1 and X2 PROFINET/Ethernet ports may be affected; X2 is the port most commonly used for engineering access because X1 is often reserved for PROFINET IO data traffic.
In the most severe case the panel is stuck in Maintenance Mode and the operator cannot get to Control Panel, Start Center, or any WinCC Unified runtime diagnostics. The panel is reachable only as a black box with a MAC address and a blank IP. This article consolidates the recovery procedure recommended in the official Siemens TIA Portal Unified Comfort Panels documentation, plus the engineering constraints behind the procedure, so that the issue can be solved on the first pass.
Safety warning. A factory reset via ProSave reformats the internal flash drive and erases all runtime projects, certificates, recipes, and user administration data. Back up the project from TIA Portal (Project > Archive) and the runtime data using a USB stick or an external storage device before performing the steps in Section 5.

2. Affected Hardware and Firmware

The procedure in this document applies to the Unified Comfort panel family, with the MTP1200 (12.1" widescreen, 1280 × 800) as the primary subject:
Article number Description Display OS image
6AV2 128-3GB36-0AX0 MTP1200 Unified Comfort 12.1" TFT, 16:9, multi-touch Windows 10 IoT Enterprise LTSC 2019 / 2021
6AV2 128-3GB06-0AX0 MTP1200 Unified Comfort (alternative) 12.1" TFT, 16:9, multi-touch Windows 10 IoT Enterprise LTSC
6AV2 128-3GB46-0AX0 MTP1200 Unified Comfort (conformal coating variant) 12.1" TFT, 16:9, multi-touch Windows 10 IoT Enterprise LTSC
All MTP1200 Unified Comfort units ship with the SIMATIC WinCC Unified runtime, and the operating system recovery is performed through the ProSave component of SIMATIC Automation Tool or through the TIA Portal installation tree (Start > Siemens Automation > ProSave). ProSave versions track the TIA Portal release:
TIA Portal / ProSave version WinCC Unified ES MTP1200 panel image (HMI)
V16 (ProSave V16) WinCC Unified V16 Unified Comfort V16.0.x
V17 (ProSave V17) WinCC Unified V17 Unified Comfort V17.0.x
V18 (ProSave V18) WinCC Unified V18 Unified Comfort V18.0.x
V19 (ProSave V19) WinCC Unified V19 Unified Comfort V19.0.x
V20 (ProSave V20) WinCC Unified V20 Unified Comfort V20.0.x
If the panel's existing OS image is newer than the ProSave version on your engineering PC, ProSave will refuse to push the image and reports a version mismatch. Install a matching or newer TIA Portal/ProSave on the engineering PC, or use the SIMATIC Automation Tool to update the panel.

3. Root Cause Analysis

The "0.0.0.0" displayed in the panel corner is not, by itself, a network error. It is a symptom of one of three underlying conditions:
  1. DHCP client with no DHCP server reachable. The MTP1200's PROFINET/Ethernet port is configured as a DHCP client. If no DHCP server is on the link layer, the client keeps the placeholder address 0.0.0.0. This is by design and does not damage the panel.
  2. Misconfigured ProSave / PG-PC interface on the engineering PC. The most common failure in the field: the engineering PC's PROFINET/Ethernet adapter is bound to a wrong access point. ProSave uses S7ONLINE as the access point and routes the OS update through that. If the access point points to a non-existent NIC, a virtual adapter, a disabled Wi-Fi, or a USB-Ethernet dongle that is not plugged in, the connection will never start.
  3. Image corruption / failed prior update. A previous OS update or a power loss during firmware write has left the panel in an unbootable or semi-bootable state. In that case ProSave can still recover the panel, but the engineering PC must reach the panel's bootloader (BootP) on a fixed IP, which means the link layer must be functional first.
Most field cases are a combination of (1) and (2). The user has correctly set a static IP on the PC, but the HMI is still on DHCP and has no address to answer on, and the PC's PROFINET driver is pointed at the wrong interface. Section 5 covers both.

4. Prerequisites

  1. A PC running Windows 10 (build 17763 or higher) or Windows 11 with a current TIA Portal installation that includes the matching ProSave component for the panel's image version.
  2. Administrator rights on the engineering PC (ProSave writes a service and opens raw Ethernet sockets).
  3. One Ethernet cable (Cat 5e or better) and a direct PC-to-panel connection, ideally on the X2 port of the MTP1200. X2 is the standard engineering port; X1 is the PROFINET IO port and may be filtered or bonded differently.
  4. The HMI image file (HP image) corresponding to the panel. On a default TIA Portal installation this is at:
    %ProgramFiles%\Siemens\Automation\Portal Vxx\Data\Hmi\Transfer\<xx>\Images\MTP1200_...
  5. Free static IPv4 addresses on the same /24 subnet for the PC and for the panel. Suggested addresses when connecting direct:
    PC: 192.168.0.1 / 255.255.255.0
    Panel (target): 192.168.0.2 / 255.255.255.0
  6. Siemens Automation Tool or TIA Portal Open Project context. ProSave can be started standalone (Start > Siemens Automation > ProSave > ProSave.exe) which is the recommended path for image recovery.
Do not use a managed switch with port security, Spanning Tree BPDU filter, or DHCP snooping between the PC and the panel during a recovery. A 1:1 crossover or direct patch cable is preferred. Managed switches can drop the BootP/DHCP discovery packets that ProSave uses during OS update.

5. Step-by-Step Resolution

5.1 Stage the network on the PC

  1. Open Control Panel > Network and Sharing Center > Change adapter settings on the engineering PC.
  2. Identify the physical Ethernet adapter you will use. Disable every other adapter (Wi-Fi, VPN virtual NICs, Hyper-V virtual switches, VMware/Workstation host-only NICs) to prevent ProSave from binding to the wrong one.
  3. Set a static IPv4 on the chosen adapter:
    • IP address: 192.168.0.1
    • Subnet mask: 255.255.255.0
    • Default gateway: blank
    • Preferred DNS: blank
  4. Open a command prompt and verify the configuration:
    ipconfig /all
    The interface should show the static address with no DHCP server line.
  5. Disable Windows Firewall temporarily for the chosen adapter profile, or add an inbound rule for TCP ports 102 (S7), 443 (HTTPS) and UDP 67/68 (BootP/DHCP) and UDP 34964 (PNIO discovery).

5.2 Confirm the link layer on the MTP1200

  1. Power on the MTP1200. Wait until the panel displays a runtime or maintenance screen.
  2. Read the upper-right corner of the panel display. A live link with an address will show the IP, the subnet, and the MAC. If the corner shows 0.0.0.0, the panel is reachable on the link layer only - it has not yet obtained an IPv4 address.
  3. Touch the upper-right corner (or follow the panel's Start Center to Settings > Network and Internet) and force a static address. On Unified Comfort panels, navigate to Start Center > Control Panel > Network and Dial-up Connections > PN/IE1 (or PN/IE2) and set:
    • IP address: 192.168.0.2
    • Subnet mask: 255.255.255.0
    • Default gateway: blank
    If the panel is in Maintenance Mode and you cannot reach the Control Panel, skip this step and continue to 5.3 - ProSave will push an image that contains a fresh network configuration.
  4. From the engineering PC, ping 192.168.0.2. A reply confirms the link layer is good. No reply means either the cable is bad, the wrong port (X1 vs X2) is in use, or the panel is in bootloader mode and not yet answering ICMP.

5.3 Configure the PG/PC Interface on the engineering PC

This is the step that, when skipped, causes the "Waiting for connection" / "No connection" error.
  1. Start Start > Siemens Automation > PG/PC Interface (the application is shipped as Set PG/PC Interface.exe).
  2. In the Access point dropdown, select S7ONLINE. (ProSave uses this access point by default; do not use S7ONLINE (STEP 7) or any other variant unless directed by Siemens support.)
  3. In the Interface parameterization used dropdown, select the physical Ethernet adapter you wired to the panel, with the assignment TCP/IP > Network card (RFC 1006) or, for PROFINET-aware installations, TCP/IP > ISO-on-TCP.
    Typical entries:
    • TCP/IP > Intel(R) Ethernet Connection I219-LM > S7ONLINE
    • TCP/IP.Auto > Realtek PCIe GbE Family Controller > S7ONLINE
    Do not select a virtual adapter (Hyper-V, VirtualBox, VPN, WSL). Do not select TCP/IP (Auto) > Any when the PC has more than one active NIC; that target can rebind at runtime.
  4. Click OK. Windows may prompt for elevation.
Tip. Run Set PG/PC Interface once, then close it before starting ProSave. The PG/PC assignment is a registry setting, not a runtime configuration. Changes take effect for newly started processes only.

5.4 Configure ProSave

  1. Start Start > Siemens Automation > ProSave. (The binary is %ProgramFiles%\Siemens\Automation\ProSave.exe in standalone installs, or %ProgramFiles%\Siemens\Automation\Portal Vxx\Bin\ProSave.exe as part of TIA Portal.)
  2. In the Device type dropdown, select MTP1200 Unified Comfort. If the device is not listed, the ProSave version does not know about the panel - install a matching TIA Portal/ProSave.
  3. In the Connection section, select Ethernet (TCP/IP).
  4. In the IP address of the HMI device field, type the panel's current or target IP. Use the static IP you set on the panel in 5.2 if the runtime is alive (192.168.0.2 in this example). If the panel is in Maintenance Mode and shows 0.0.0.0, use the IP that you want the panel to have after the image is installed; ProSave reaches the panel via BootP regardless of the current address.
  5. Click Read > Configuration / OS. ProSave should report the current firmware and confirm reachability within a few seconds.

5.5 Reset the panel to factory settings

The official Siemens procedure for resetting a Unified Comfort panel to factory settings through ProSave is documented in the TIA Portal Unified Comfort Panels manual, section "Resetting an HMI device to factory settings via ProSave". The condensed steps:
  1. In ProSave, switch to the OS Update tab.
  2. Select Reset to factory settings (sometimes labeled Restore factory state). The checkbox must be ticked - by default, ProSave will only update the OS image while keeping user data, which is not sufficient when the runtime is broken.
  3. In the Image path field, browse to the matching HMI image. For TIA Portal V19, the path is typically:
    C:\Program Files\Siemens\Automation\Portal V19\Data\Hmi\Transfer\19\Images\MTP1200_Unified_HMI_V19_0_0_0.ima
  4. Tick Perform reset automatically and confirm the panel's IP. ProSave will:
  1. Reboot the panel.
  2. Trigger the panel's BootP loader on the configured port.
  3. Push the image and the requested IP address.
  4. Reset the internal storage to factory state.
  1. Press Update OS. The operation takes 5-15 minutes depending on image size. Do not power off the panel or the PC during the transfer.
  2. When ProSave reports OS update complete, the panel will reboot into the Start Center with default settings, including a default IP of 0.0.0.0 (DHCP) until you assign one.
Power-loss behavior. If power is lost during the OS write, the panel will be in a non-bootable state. Repeat the procedure from 5.5 - ProSave and the BootP loader are designed to recover from interrupted writes.

6. Verification

  1. After the panel reboots, confirm the Start Center is displayed. The default panel name is MTP1200 and the default user is Administrator with the password defined during commissioning (or no password on a fresh image).
  2. Touch the upper-right corner to display the IP and MAC. The MAC should match the label on the back of the panel. The IP will show 0.0.0.0 if DHCP is the default - assign a static address before continuing.
  3. From the engineering PC, ping the panel's static IP.
  4. Open TIA Portal, connect to the panel, and transfer the project: Online > HMI Device Maintenance > Transfer. Confirm that the runtime starts and the connections to the PLC(s) reach RUN.
  5. From the Start Center, open Control Panel > System > About and verify the firmware image version matches the one you installed.

7. Troubleshooting Matrix

Symptom Likely cause Fix
ProSave: "Waiting for connection" forever PG/PC interface bound to wrong NIC, or Wi-Fi is the active adapter Re-run Set PG/PC Interface, select the wired Ethernet adapter against S7ONLINE
ProSave: "Connection to the HMI device could not be established" Panel IP does not match the ProSave IP, or the panel is on a different subnet Use the same /24 subnet on the PC and the target panel IP. Ping the panel first.
Panel shows 0.0.0.0 and no Start Center Maintenance mode after failed update Proceed with ProSave OS update, tick "Reset to factory settings"
ProSave: "Image file is not compatible with the device" Image version mismatch Install a TIA Portal/ProSave version that matches the panel image, or download a newer image into the existing TIA Portal
Image update fails at 5%, 12% or 47% Unstable link, wrong port, or third-party firewall Switch to the X2 port, replace the patch cable, disable Windows Firewall, try a direct 1:1 connection
Panel boots but Start Center does not appear Boot loader restored but runtime image missing After factory reset, transfer a runtime project from TIA Portal
PC sees the panel at boot (BootP) but loses it after reboot Image succeeded but DHCP has not yet re-acquired Assign a static IP on the panel through Control Panel, not DHCP
ProSave cannot find the HMI device type "MTP1200 Unified Comfort" ProSave version is too old Install a TIA Portal V17+ with a current ProSave; older ProSave versions predate the Unified Comfort line

8. Edge Cases and Field-Proven Caveats

8.1 Virtual machines on the engineering PC

ProSave on a Windows VM with bridged networking behaves erratically because the virtual switch adds latency and the BootP exchange expects a direct broadcast. Run ProSave on the host OS, not inside a VM. If you must use a VM, set the virtual NIC to Promiscuous Mode: Allow All and to a fixed MAC.

8.2 Two Ethernet adapters with the same default route

If the engineering PC has a wired Ethernet on 192.168.0.0/24 and a corporate VPN adapter on 10.0.0.0/8, ProSave may pick up the wrong route. Force the route to the panel by adding a static host route: route add 192.168.0.2 mask 255.255.255.255 192.168.0.1 metric 1 if <iface_index>

8.3 Panels behind managed switches

If the panel must be reached across a managed switch (a common situation during factory acceptance tests), disable the following features on the relevant port:
  • STP/RSTP/MSTP for that port (or enable portfast).
  • DHCP snooping.
  • Dynamic ARP inspection.
  • IGMP/MLD snooping (ProSave discovery uses broadcast).

8.4 What to do when ProSave still cannot reach the panel

If the panel is unreachable even after 5.1-5.4, escalate to one of the following before declaring hardware failure:
  1. USB recovery. Newer Unified Comfort panels accept a USB stick with a recovery image. The recovery menu is reached by holding the Service button on the back of the unit during power-on. The exact procedure is panel-specific; refer to the operating instructions that ship with the panel.
  2. Serial service port. The MTP1200 does not have a service serial port. For older Unified Comfort panels that do (MTP700/1000/1500/1900 in early firmware), the serial port is the fallback path for OS recovery.
  3. RMA. If the panel does not respond on any port and the Service button does not bring up a recovery menu, the flash is most likely damaged. Contact Siemens Industry Online Support with the panel's serial number for an RMA.

8.5 Differences across MTP1200 hardware revisions

The MTP1200 has shipped with three distinct hardware revisions: ES1 (early 2019), ES2 (mid 2020, improved EMC and USB stack), and ES3 (2022, Windows 10 IoT Enterprise LTSC 2021). The OS image is not always cross-compatible. ProSave will refuse an image intended for a different hardware revision with a clear "image does not match the device" error - this is not a problem with the procedure, it is a feature.

9. Recovery Without a Network - SIMATIC Automation Tool

When ProSave cannot reach the panel because the link is bad or the engineering PC is far from the panel, the SIMATIC Automation Tool (SAT) can update a panel over USB once the panel exposes a USB-B service port. SAT is shipped separately from TIA Portal and can be downloaded from Siemens support. For Unified Comfort panels the USB path is supported for OS image recovery only; runtime transfer still requires Ethernet.

10. Long-Term Recommendations

  1. Pin a static IP on the panel, not DHCP. Field panels behind a DHCP server that fails or rolls leases will become unreachable. Configure the panel's PROFINET interface with a static IP and document it on the cabinet drawing.
  2. Use the X2 port for engineering, X1 for PROFINET IO. The two interfaces are independent on the MTP1200. Reserving X2 for engineering traffic avoids surprises when a PLC goes into stop and the panel's IO port behaves differently.
  3. Keep ProSave versions current. New panels ship with newer OS images. An engineering PC with ProSave V17 cannot recover a panel running image V19. Maintain a "recovery laptop" with the latest TIA Portal installed.
  4. Store panel images centrally. A TIA Portal repository with the panel image files allows any engineer on the team to perform the recovery without searching the network for a single PC that has the right ProSave.
  5. Back up the runtime before any OS update. Use Start Center > Service > Backup to a USB stick before changing the OS image. The backup contains the runtime project, recipes, user administration, and certificates.

11. Related Documentation

FAQ

What IP address should I enter in ProSave when the MTP1200 shows 0.0.0.0?

Enter the static IP you want the panel to use after recovery, on the same /24 subnet as your engineering PC. ProSave reaches the panel through BootP regardless of its current address; the field is the target address, not a query against the live panel.

Why does ProSave show "Waiting for connection" even when the panel is online?

The most common cause is a wrong PG/PC interface assignment. Open Set PG/PC Interface, set the S7ONLINE access point to the physical Ethernet adapter wired to the panel, restart ProSave, and retry. A disabled firewall or a Wi-Fi adapter bound to S7ONLINE will produce the same symptom.

Can I factory-reset an MTP1200 Unified Comfort without ProSave?

Yes, but only if the runtime is alive. From the Start Center, navigate to Control Panel > System > Reset to Factory State. If the runtime is corrupt and the panel is in Maintenance Mode, ProSave is the only supported recovery path; the alternative is USB recovery using the Service button during power-on.

Which port should I use for engineering, X1 or X2?

Use X2 for engineering access (OS update, project transfer, diagnostics). Reserve X1 for PROFINET IO traffic to the controller. Both ports are independent and can be addressed simultaneously, but mixing them in production leads to confusing reachability problems.

How long does a factory reset via ProSave take?

For a 12" Unified Comfort panel with a full HMI image, expect 5-15 minutes end-to-end. The image transfer itself is usually under 5 minutes on a direct gigabit link, but the panel's reboot, storage reformat, and Start Center reinitialization add several minutes of overhead.

Back to blog