Resolving S7-1200 Upload Failure in TIA Portal V13 Compatibility Mode

When an S7-1200 CPU (such as the 6ES7215-1AG40-0XB0 or comparable 1215 DC/DC/DC variants) is programmed with TIA Portal V13 and the engineering workstation is later updated to TIA Portal V13 SP1 (or any of its Updates), engineers frequently encounter a hard fault during the upload operation:

The hardware configuration was created and downloaded with an incompatible version of STEP7. Could not upload hardware configuration.

This error blocks the standard Upload device to PG/PC workflow and, in some cases, even blocks the project retrieval functions in Online & Diagnostics. The resolution path is documented by Siemens under FAQ entry 82169157 — Compatibility mode for TIA Portal V13 / V13 SP1 and is the canonical fix for this class of fault.

1. Problem Description

The fault appears under the following conditions:

• A S7-1200 / S7-1215 CPU has been programmed and downloaded using TIA Portal V13 (base release, no Service Pack).
• The same engineering PC is later updated to TIA Portal V13 SP1 (or any V13 SP1 Update 1 through Update 9).
• The engineer attempts an Upload from device (formerly Upload to PG/PC) of the station's hardware configuration into the current TIA project.

Result: the upload dialog opens, scans the CPU, but reports the incompatibility error and refuses to bring the hardware configuration into the offline project tree. In some installations, online access to the PLC works (accessible online blocks such as OB, FB, DB, and FC are visible), but the upload toolbar remains disabled or the menu items are greyed out.

2. Root Cause Analysis

TIA Portal binds the device's offline project representation to the exact portal version that produced the download. Internally, the project archive embeds a schema version that maps to the originating TIA Portal release family. The S7-1200 hardware catalog, the GSD/GSDML references, and the PLC firmware metadata for blocks differ between the V13 base release and the V13 SP1 release family.

When the same project is reopened on a workstation running V13 SP1, the portal attempts to migrate the project forward in the schema. Migration succeeds for the offline project (blocks, tags, hardware tree), but the upload from device path has additional guards: it refuses to merge a V13 download image with a V13 SP1 offline project because the V13 SP1 hardware catalog contains revised module versions, revised firmware descriptors, and revised HMI tags resolution tables that are not bit-identical with V13.

The error string "incompatible version of STEP7" is generated by the upload service in TIA Portal and is logged against the device descriptor stored on the target CPU. The CPU itself does not raise a diagnostic buffer entry; the rejection happens entirely on the engineering side.

3. Solution: Compatibility Mode V13

Siemens ships a Compatibility Mode shell that allows the V13 SP1 installation to behave as a V13 environment for the purpose of opening, editing, and uploading existing V13 projects. The compatibility mode is bound to the project, not to the entire installation, and is selected at project-open time.

The official reference is Siemens FAQ 82169157. The compatibility mode is implemented as a separate TIA Portal shortcut that ships with the V13 SP1 installation media and is added to the Windows Start menu under the Siemens Automation > TIA Portal V13 program group as TIA Portal V13 (Compatibility Mode).

3.1 Step-by-Step Procedure

1. Close any open TIA Portal instance on the engineering workstation.
2. Launch TIA Portal V13 (Compatibility Mode) from the Start menu. Do not launch the standard V13 SP1 entry.
3. From the portal landing page choose Open an existing project and navigate to the V13 source project (file extension .ap13). If a V13 project is not available locally, create a new empty project with the V13 compatibility mode shell.
4. With the project open, expand Online & Diagnostics and select the target S7-1200 / S7-1215 CPU. Confirm the PG/PC interface and the subnet (PROFINET or PROFIBUS depending on the CPU variant).
5. Perform a Go online to verify the connection. The online view should populate the CPU, its program blocks, and its diagnostics buffer.
6. Right-click the S7-1200 station (the PLC device node, not the project root) and choose Upload from device > Hardware and software (complete upload). This is the only upload option that brings the hardware configuration plus the software into the offline tree.
7. Save the project. The schema remains V13. The resulting .ap13 archive can subsequently be upgraded in a controlled manner to V13 SP1 or later using Project > Upgrade project / TIA version.

3.2 Alternative: Empty V13 Project Workflow

If a V13 source archive is not available, the recommended recovery path is:

1. Launch TIA Portal V13 (Compatibility Mode).
2. Create a new empty V13 project.
3. From the portal tree add a Unspecified SIMATIC S7-1200 CPU or detect the connected CPU via Online & Diagnostics > Accessible nodes.
4. When the CPU is detected, choose Upload from device on the device node. The compatibility-mode portal will accept the V13 image and reconstruct the hardware tree.
5. Save and re-archive as .ap13 before upgrading the schema.

4. Online vs. Upload — Why the PLC Is Visible but the Upload Is Not

A common confusion during this fault is the apparent contradiction of online access works, upload does not. The explanation is structural:

Online block view uses the S7 Online protocol to read the active program from the CPU's load memory. The read path is schema-agnostic; the portal does not need to reconcile the result with the offline hardware tree. The upload path, in contrast, must reconstruct the offline device representation and bind it to a catalog and firmware descriptor, which is exactly where V13 / V13 SP1 differences manifest.

5. TIA Portal V13 Version Terminology

Siemens releases TIA Portal in base releases and service pack revisions. The naming convention is strict:

• TIA Portal V13 — base release, no service pack. There is no Update for this SKU.
• TIA Portal V13 SP1 — first service pack. This is the SKU that receives Updates (Update 1, Update 2 … Update 9).
• TIA Portal V13 SP1 Update 9 — incremental maintenance build of V13 SP1, released 2016–2017.

When the field reports "TIA V13 Update 9", the actual installed product is V13 SP1 Update 9. This is a common source of confusion because the colloquial shorthand drops the SP1. Confirm the exact installed product by inspecting Help > About in the portal, which lists the build number and the precise SKU string.

6. Verification Steps

After a successful compatibility-mode upload, run the following checks to confirm the project is consistent:

1. Hardware tree parity: Compare the CPU order number, firmware version, signal module order numbers, and slot assignments against the original documentation. The V13 image should reconstruct the exact module lineup.
2. Block compile: Right-click the Program blocks folder and select Compile > Software (rebuild all blocks). The build must complete without errors. A successful rebuild in the V13 compatibility-mode shell confirms the schema is fully restored.
3. Online compare: Use Online & Diagnostics > Compare offline/online on the CPU node. The diff should report identical blocks.
4. Archive integrity: Use Project > Archive > Archive to produce a fresh .ap13 zip archive. Verify the file can be opened on a second workstation running the same compatibility-mode portal.
5. Optional upgrade test: On a copy of the project, run Project > Upgrade project / TIA version > Upgrade to TIA Portal V13 SP1. If the upgrade completes without diagnostic warnings, the V13 archive was a clean source.

7. Error Message Reference

The following error strings and conditions have been observed on the S7-1200 / S7-1215 family in the V13 → V13 SP1 transition. Capture the exact text for support cases.

8. Preventive Measures and Best Practices

To prevent recurrence on subsequent service pack migrations:

• Version-pin offline archives. When commissioning a V13 project, archive the project immediately after the first successful download. Store the .ap13 in the project documentation repository with a version tag.
• Document installed SKU. Maintain a workstation manifest that records the exact TIA Portal SKU and Update level for every PG/PC. Include this manifest in the project's quality folder.
• Pre-stage compatibility mode. Before applying a TIA Portal Update, confirm the compatibility-mode shortcut is present in the Start menu. If it is absent, the SP1 install is incomplete and a repair install is required.
• Use the upgrade path deliberately. The official migration path is V13 → V13 SP1 → V14 → V14 SP1 → V15 / V15.1 / V16 / V17 / V18. Skip the V13 compatibility-mode step only when the V13 source archive is no longer required and a clean V13 SP1 re-build from PLC is feasible.
• Track CPU firmware. S7-1200 CPUs at firmware V4.x are compatible with TIA Portal V13 SP1 and later. CPU firmware V4.4 and V4.5 are supported by TIA Portal V16 / V17. Verify firmware compatibility on the Siemens Industry Online Support portal before any upload or upgrade.

9. Related Compatibility Considerations

The V13 / V13 SP1 incompatibility pattern repeats at other service pack boundaries. Engineers migrating a TIA Portal V13 SP1 project to TIA Portal V14, V14 SP1, V15, V15.1, V16, V17, or V18 should plan for the same upload-time schema check. The remediation in each case is identical: open the project in the original compatibility-mode shell, perform the upload, archive, then upgrade deliberately.

For the S7-1500 family, the same fault can occur when migrating between TIA Portal V13 SP1 and V14. The S7-300 / S7-400 families (managed via STEP 7 V5.x and WinCC) are not affected because the schema model is different. The fault is bounded to the TIA Portal / S7-1200 / S7-1500 axis.

10. Field Commissioning Notes

For technicians recovering a station on site, the following compact procedure has been used successfully on the S7-1215 DC/DC/DC with 6ES7215-1AG40-0XB0 firmware V4.x:

1. Verify physical link: PROFINET cable, link LED on the CPU, and a ping from the PG to the CPU's IP address.
2. Set the PG/PC interface to Intel NIC — TCPIP for direct PROFINET access, or to the CP1613/CP1623 driver for production networks.
3. Launch TIA Portal V13 (Compatibility Mode).
4. Create an empty V13 project.
5. Online > Accessible nodes — confirm the CPU appears with the expected MAC and IP.
6. Right-click the CPU node in the project tree > Upload from device > Hardware and software (complete upload).
7. Compile, save, archive.

If the upload still fails, verify the installed TIA Portal SKU actually contains the V13 compatibility-mode shortcut. Some installation paths (e.g. the minimal V13 SP1 Update build) do not include it, and a full install of the V13 SP1 media is required.