Migrating TIA Portal V14/V15 to V16: S7-1200 PLC and TP Comfort HMI Reference

This reference describes the engineering workflow for migrating a complete automation project from TIA Portal V14 / V15 / V15.1 to TIA Portal V16 when the controller is a SIMATIC S7-1200 CPU and the operator panel is a SIMATIC TP Comfort HMI. The machine is a multi-vendor cell that integrates an ABB robot, a Schneider Electric servo drive (Lexium / Modicon family) and a Weidmüller u-remote (or similar) remote I/O station, all reachable over PROFINET. Two questions dominate this kind of upgrade and are answered end-to-end below: (1) what can go wrong while downloading the new project, and (2) how to return the machine to its original operating state if the V16 download fails or alters behaviour.

1. Overview and Scope

The migration paths and their consequences for the assets in scope are summarized in the table below.

2. Prerequisites and Required Artifacts

Before opening anything in TIA Portal V16, gather the following inputs. Any missing item converts the migration into a recovery operation rather than an upgrade.

1. Original TIA Portal project archive (.zap for single-project, .zal for multi-project) used to build the V14/V15 machine. Do not rely on a recently exported .ap16 / .ap16_1 file unless you have verified it compiles in the source version.
2. TIA Portal V16 installation matching the required option set: STEP 7 Basic / Professional, WinCC Basic / Comfort / Advanced, plus any used options (e.g., S7-1200 Motion, OPC UA, Safety).
3. Hardware Support Packages (HSP) for the S7-1200, the Comfort panel, the ABB robot, the Schneider drive, and the Weidmüller station. TIA Portal V16 ships a baseline set; new module revisions require the matching HSP installed via "Options → Support Packages".
4. GSD / GSDML files for any third-party device whose GSD was added under "Options → Manage GSD files" in V14/V15. If those files are no longer available, export them from the V14/V15 project before opening V16.
5. Firmware images for the S7-1200 CPU and the Comfort panel. The CPU's current firmware version can be read in V14/V15 via Online & Diagnostics and is required to predict whether V16 will request a firmware update on download.
6. A current backup of every node's runtime: S7-1200 program card image (or online backup via the CPU's "Backup" function), Comfort panel runtime backup via ProSave / "Backup / Restore" on the panel, and the commissioning archives of the ABB robot, the Schneider drive, and the Weidmüller coupler.
7. Network topology information: PROFINET device names, IP addresses, subnet masks, IO controller / IO device roles, and slot assignments. This is the data that is lost first if a download overwrites a device's identity.
8. Plant password / know-how protection list. The project password for any know-how protected block must be known or the block must be removed before migration; an unknowable protected block halts the upgrade.

3. HMI Backup vs. TIA Portal Project File: Critical Distinction

Two file types are routinely confused in field calls. The matrix below fixes the terminology:

Consequence for the field engineer: if the only artifact in your possession is a Comfort panel backup, you cannot migrate to TIA V16. You can only restore that backup to an identical panel reference. To migrate, the original TIA project (the file the engineer clicked "Archive" on) is mandatory.

4. Migration Tool TIA Portal Workflow

Siemens publishes a dedicated Migration Tool TIA Portal that automates conversion of projects from older TIA Portal versions. The official entry point is the Industry Online Support article ID 58638200 — Migration Tool TIA Portal. As published in that KB, the tool is available for TIA Portal versions V13 SP2, V14 SP1, V15, V15.1, V17, V18, V19 and V20.

Step-by-step with the Migration Tool TIA Portal (V15.1 build) for a V14 source:

1. Download the Migration Tool TIA Portal V15.1 from Siemens ID 58638200. Verify the SHA against the value Siemens publishes on the KB page.
2. Install it on the engineering station. It requires a local TIA Portal V15.1 as the host environment.
3. Close all TIA Portal instances. Launch the Migration Tool.
4. In "Project selection" browse to the source .zap14 / .zap15 file. The tool validates the version and lists convertible devices.
5. Select the target directory. The tool writes a .zap15_1 file and a MigrationLog.html next to it. Read the log — any block that fails conversion is listed with a clickable entry.
6. Open the converted project in TIA V15.1 once, compile, and check "Accessible nodes" against the live CPU to confirm the offline / online delta is clean.
7. Archive the V15.1 project, close TIA V15.1, open the V15.1 archive in TIA V16, accept the upgrade prompt, and recompile.

Direct V14 / V15 → V16 (no Migration Tool):

1. Start TIA Portal V16. Select "Open an existing project" and point at the V14 / V15 archive.
2. TIA Portal asks whether to upgrade; choose "Yes" and accept the suggested backup path. The original file is preserved; the upgraded copy is opened.
3. Check the "Info" editor (lower-right "Messages" pane) for warnings, in particular Hardware catalog updates required and Blocks must be recompiled.
4. Install missing HSPs, recompile all blocks (right-click program → Compile → All). Do not download before a clean compile has been achieved.

5. S7-1200 CPU Migration and Firmware Compatibility

The S7-1200 family (CPU 1211C, 1212C, 1214C, 1215C, 1217C, 1212FC, 1214FC, 1215FC) is supported by TIA Portal V16. The decisive parameter is the CPU firmware version. Mixing TIA Portal version and CPU firmware is the most common cause of "something went wrong on download".

Rule of thumb: TIA Portal will refuse to download when the offline project targets a firmware version higher than what is on the physical CPU. The reverse — project targets older firmware than is on the CPU — is allowed; TIA will only warn that the CPU capability is not fully used.

What can break on the S7-1200 side during a V14 → V16 download:

• Webserver API differences: the user-defined web pages API surface changed between V14 and V16. A page that compiled in V14 can produce a non-fatal warning in V16 and change behaviour at runtime.
• Know-how protected blocks: protected blocks from V14 will be re-compiled in V16; if the password is unknown, the project cannot be compiled and therefore cannot be downloaded.
• Active / passive communication IDs: the S7-1200 supports a fixed number of active connections; V16 may use one more connection than V14 (e.g., for the OPC UA server), pushing a heavily loaded CPU over the connection limit.
• Recipe / data log storage layout: if the project uses recipes or data logs whose structure is changed in V16, an in-place download can leave the panel / CPU inconsistent with the prior recipe file in the CPU's flash.

6. TP Comfort HMI Panel Migration Path

The TP Comfort family (TP700 / TP900 / TP1200 / TP1500 / TP1900 / TP2200 Comfort, plus the newer 2nd-generation variants) is supported by TIA Portal V16. The migration is straightforward when the panel reference is unchanged, which is the normal case.

Recommended migration sequence:

1. Open the migrated project in TIA V16.
2. Open the HMI device configuration; verify the device reference in "Devices & Networks" matches the physical panel. A wrong reference compiles successfully but the runtime transfer fails.
3. Open "Runtime settings → Language & Font" and verify the fonts required by the migrated screens are still present on the panel image. Missing fonts cause squares / boxes on screens, not a transfer error.
4. Compile the HMI (right-click → Compile → Software (rebuild all)). Errors here usually point to a deleted V14 library or a renamed system function.
5. Transfer the runtime over Ethernet via the panel's transfer settings. The HMI boots into "Transfer" mode if the "Transfer" channel is enabled in the project, otherwise use ProSave.

Common comfort-panel pitfalls specific to a V14 → V16 jump:

• Screen size mismatch on first migration: if the panel was changed between V14 and V16 (e.g., TP900 Comfort to TP1200 Comfort), the project does not migrate automatically; a new panel reference must be created.
• HMI tags mapped to deleted PLC tags: if a tag was renamed in V14 but the HMI tag was not updated, the HMI compiled anyway in V14; V16 recompiles strictly and reports a type mismatch.
• ProSave "Backup" vs. "Restore": a restore writes the panel backup back onto the panel. A backup reads from the panel to a file. The V16 download is a transfer operation, not a restore — using the wrong operation leaves the old runtime in place.

7. Third-Party Device Integration: ABB Robot, Schneider Servo Drive, Weidmüller Remote I/O

All three devices in this cell are PROFINET IO devices. Their integration is GSD / GSDML-based; once the GSD is installed, the device appears in the hardware catalog and the project stores only the configuration parameters (device name, IP, slot / submodule layout, telegram mapping for the drive). The migration preserves the GSD-installed device descriptions as long as the matching GSD is also installed in TIA V16.

7.1 ABB Robot (PROFINET / PROFIsafe or standard PROFINET)

ABB robots are typically integrated as PROFINET IO devices using the ABB-supplied GSDML. The project stores the device name (often "abb" or "robot1"), the IP address, and the slot assignments for the robot's input / output modules. Migration actions:

1. Install the same GSDML version (or newer) in TIA V16 via "Options → Manage GSD files".
2. After migration, open "Devices & Networks" and verify the ABB device shows the same module order. ABB firmware updates sometimes change the GSD; the project may need to be re-mapped if the slot order has shifted.
3. Check the PROFINET device name on the physical robot (teach pendant or ABB RobotStudio) against the project. A download from V16 will not auto-push a device name to a PROFINET device; the device name is set via "Assign PROFINET device name" in TIA Portal and only persists when the controller's "Station name" matches the physical node.

7.2 Schneider Electric Servo Drive (Lexium 32 / Modicon M258 / LMC058 family)

Schneider servo drives are integrated through the Schneider GSDML, with PROFINET drive profile (telegrams 1, 2, 7, 9, 102, 105, 106 mapped to PDOs). The project stores the telegram layout and the PLCopen function blocks (e.g., MC_Power, MC_MoveAbsolute) used for motion. Migration actions:

1. Re-install the Schneider GSDML in V16. The version string in the GSDML is more important than the catalog "version" in V16 — if the new GSD adds a new telegram, recompile will succeed only after the slot layout is reconciled.
2. Verify that the drive's IP and PROFINET name (e.g., "servo1") are preserved.
3. Re-check any Schneider-specific libraries (e.g., SoMachine / EcoStruxure blocks) referenced in the program. The LMC058 motion controller's libraries migrate cleanly only when the source project was opened in EcoStruxure and saved in a TIA-importable form.

7.3 Weidmüller Remote I/O (u-remote / WAVE series)

Weidmüller u-remote stations are PROFINET IO devices described by Weidmüller GSDML files. The slot / submodule layout is the engineering payload. Migration actions:

1. Install the matching Weidmüller GSDML in V16.
2. Open the station in the network view and check the channel diagnostics addresses. Weidmüller releases occasionally renumber diagnostic slots; the project may keep the V14 addresses or align to the new GSD — either way, the IO addresses in the PLC program are affected.
3. Re-verify the device name and IP after first download; some Weidmüller couplers reset the device name to factory default if the configuration is downloaded with an empty "Replace device name during download" flag.

7.4 PROFINET device name risk

8. Firmware Verification Procedure

The firmware of the S7-1200 CPU, the Comfort panel, and the PROFINET devices must be known before any download. The V14 / V15 project that is to be migrated already contains the targeted firmware; the physical nodes carry the firmware that is actually running. A difference between the two is the cause of "something went wrong" reports in roughly 70% of field cases.

Reading the S7-1200 CPU firmware online (works in V14, V15 and V16):

1. Open the V14 / V15 project, go online to the CPU, and open "Online & diagnostics" on the CPU device.
2. In the left pane, expand "Diagnostics" and select "General". The "Module information" section lists the order number (MLFB), the firmware version (e.g., V4.2.3) and the hardware version.
3. Record the firmware version. Compare to the project's "Properties → General → Catalog information" on the CPU device.

Reading the Comfort panel firmware online:

1. In the project, right-click the panel in the project tree and choose "Online & diagnostics".
2. Go to "Diagnostics → General". The runtime version and image version are reported.
3. Alternatively, on the panel itself, open "Control Panel → System → Device & System Information" to read the runtime build number.

Reading the PROFINET device firmware:

1. In the network view, go online (online → accessible nodes).
2. For each node, open "Online & diagnostics" and read the "Module information" entry. ABB, Schneider and Weidmüller each expose the firmware under a slightly different property name; all are listed under the "General" tab in "Module information".

Output of this procedure — a migration worksheet:

9. Download Procedure and Risk Mitigation

For a running production machine, the download itself is the highest-risk step. The procedure below minimises exposure to the two failure modes: a corrupt download, and a download that succeeds but changes the machine's behaviour.

Pre-download checklist:

1. Compile clean in TIA V16: zero errors, zero warnings on program blocks and on HMI screens.
2. Take a fresh online backup of the S7-1200 (Online → Backup from online device).
3. Take a fresh ProSave / TIA backup of the Comfort panel (Online → HMI backup).
4. Take a fresh ABB robot backup (RobotStudio → Backup).
5. Take a fresh Schneider drive backup (SoMove / EcoStruxure → Backup).
6. Take a fresh Weidmüller station configuration export (web interface of the coupler).
7. Stop the machine, isolate safety circuits, and put the cell in a controlled state.

Download sequence:

1. Connect the engineering station to the S7-1200 CPU. Go online and verify that the online ↔ offline delta is what you expect (typically: hardware is online-equal, software is offline-newer).
2. Download the S7-1200 hardware configuration first. TIA Portal will warn if the S7-1200 stops (it does, briefly, on hardware config download). Accept.
3. Download the S7-1200 program blocks. Select "Consistent download" to ensure all blocks land in the same CPU stop / run transition.
4. Download the HMI runtime to the Comfort panel.
5. For the third-party devices, do not re-download the IO device configuration. TIA Portal does not push PROFINET device names by default; let the existing device names persist.
6. Run the CPU back to RUN, observe the diagnostic buffer for the next 10 minutes, and verify every PROFINET device reports "Connected" in the online view.

What the engineering station will show when a download has gone wrong:

• Diagnostic buffer error code SF (system fault) with "configuration error" — usually a slot / submodule mismatch caused by a newer GSD in V16.
• HMI transfer aborts with "Panel does not match project reference" — the panel was changed physically or the project's device reference was edited.
• PROFINET device shows "Not connected" — device name or IP does not match what the CPU is looking for.
• Recipe data loss — recipe structure was changed between V14 and V16, and the panel / CPU flash contained a V14 recipe that V16 cannot parse.

10. Rollback and Recovery to Original State

The answer to the original question — "how do I return the machine to its original conditions if something goes wrong" — is to engineer the rollback before the download. The recovery paths are layered from cheapest to most expensive.

The cardinal rule of a V14 → V16 download on a running machine: never delete or overwrite the V14 / V15 source archive, the original Comfort panel backup, the ABB / Schneider / Weidmüller commissioning files, and the S7-1200's online backup. These four artifacts are the four independent rollback paths. As long as they exist on a non-network-attached medium (e.g., a USB drive in a labelled envelope at the cell), the machine can always be returned to its original state.

11. Troubleshooting Matrix: Common V14/V15 → V16 Issues