S7-1200 CPU 1214 Upload Blocked in TIA Portal V13 SP1: Complete Recovery Guide

1. Problem Summary and Symptom Chain

Engineers upgrading an existing S7-1200 installation from TIA Portal V11 / V12 to TIA Portal V13 SP1 frequently hit a sequence of four cascading issues. The chain is reproducible, and the recovery order matters. The symptoms reported in the field are summarized below.

Treat these four as a single fault tree. Fixing #3 (retain memory) without fixing #1 (firmware mismatch) leaves the system only half-recovered; the next round-trip will fail again at a different layer.

2. Hardware and Software Identification

Before changing anything, capture the exact identification strings. These are mandatory when contacting Siemens support or when matching firmware to TIA Portal versions.

2.1 CPU Identification

The reported part number 6ES7 214-1AE30-0BA0 decodes as:

• 6ES7 2 – SIMATIC S7-200/300/400/1200 family
• 14 – S7-1200 series
• 214 – CPU 1214C
• 1 – Power supply: DC 24 V
• AE – Onboard I/O grouping (16 DI / 10 DO / 2 AI)
• 30 – First-generation S7-1200 firmware branch (FW 1.x / 2.x)
• 0BA0 – Order suffix (functional variant; consult Siemens Product Support for the regional equivalent MLFB support.industry.siemens.com)

Verify by reading the laser-etched label on the front flap of the CPU, then cross-check via Online > Accessible nodes in TIA Portal. The reported "Module / Firmware / Serial number" line in the Online & Diagnostics view is the authoritative source.

2.2 Engineering Software Identification

The active development environment must be logged precisely because TIA Portal service packs are cumulative and behave differently across update levels.

• STEP 7 (TIA Portal) V13 SP1, Update 9
• Microsoft Windows 7 SP1, 32-bit

3. Root Cause Analysis

Each symptom has a distinct root cause, but the four share a common family: the TIA Portal V13 SP1 project and the S7-1200 firmware on the floor are not from the same generation.

3.1 Why Upload Is Refused

The "Upload from device" wizard in TIA V13 SP1 is built on a firmware-aware reconstruction engine. The CPU uploads its program as a compact, firmware-versioned blob. TIA V13 SP1 can decode that blob only if the firmware belongs to a generation it understands.

For S7-1200, the generation map is roughly:

For a definitive match table — including the cases where upload is possible but edit is not — consult the Siemens entry "What options are available in STEP 7 (TIA Portal) for uploading when the project in the CPU has been created with a different version?" (Table 02 in that entry is the canonical source for engineers in this situation).

3.2 Why Compare PC-PLC Is Unavailable

Compare Online/Offline requires both a complete offline project and a successful upload. When upload fails (Section 3.1), the offline representation of the on-line CPU is empty, and TIA disables "Compare" with the message "Compare PC-PLC program not available." Fixing Compare is therefore equivalent to fixing the upload.

3.3 Why CALL Is Missing in LAD

The "Program control operations" instruction group in TIA Portal is filtered by the selected CPU type. If the offline project is configured for an S7-1200 with firmware that the active TIA version cannot compile (for example, a V4.2 target inside a V13 SP1 project), the instructions the firmware no longer exposes are hidden — including CALL, RET, and parameterized JMP variants. The fact that the instruction pane is "empty" is a strong tell that the CPU type or firmware in the project tree is wrong for the running TIA.

3.4 Why RUN-Mode Download Fails After Retain Memory Assignment

RUN-mode download in S7-1200 (TIA V13 SP1 onward) is a differential operation: only the deltas between the offline and the running program are patched. Two deltas force a STOP-required, full download:

1. Any change to the retentive memory layout (bit memory M, data block tags, instance DBs flagged as retentive, or the size of the retentive area in the CPU properties).
2. Any change that alters the structure of an FB interface (adding/removing/renaming IN, OUT, IN_OUT, STAT, or TEMP).

A tag name change inside a non-retentive data block is normally a valid RUN-mode delta. The reported field failure — "even minor changes like tag name changes fail after assigning retain memory space" — is therefore almost always a side-effect of the retain area boundary move: TIA correctly determines that the retentive footprint has shifted and forces STOP, but the dialog wording obscures the cause.

4. TIA Portal / S7-1200 Compatibility Matrix

The matrix below is the working subset relevant to the V13 SP1 era. Always validate against the official Siemens Product Support entry for your exact TIA Service Pack and Update combination.

Decision rule for the reported configuration: if the on-floor CPU is firmware V1.x / V2.x and the engineer insists on using TIA V13 SP1, the CPU firmware must be updated to V4.0 or V4.1 first. If a firmware update is not possible (production line that cannot stop, obsolete boot image, hardware revision older than 12/2009), the correct engineering platform is TIA V12 SP1 — not V13 SP1.

5. Diagnostic Procedure

Run this sequence before changing anything. The order is chosen to fail fast and to avoid contaminating the CPU's retentive state.

1. Open TIA Portal V13 SP1. Online > Accessible nodes. Record the detected CPU's Module, Firmware, and Serial number.
2. Right-click the detected CPU > Online > Diagnostics. Capture the diagnostic buffer (last 10 entries minimum).
3. Open the offline project in the project tree. Note the CPU type selected in Project tree > PLC_x > Device configuration > Properties > General. Compare against the live device.
4. Click Project tree > PLC_x > Properties > General > System and clock memory > Retentive memory. Screenshot the current bit-memory and DB retentive ranges.
5. Attempt Online > Upload from device (software). Capture the exact error text and error number (TIA displays an 8-digit error code, e.g. 0x02:0142 or similar; record the literal string).
6. Close TIA. Verify Windows device manager: the CP 5711 / CP 5611 / Ethernet adapter that connects to the CPU must use the Siemens protocol suite (S7ONLINE access point) and not a generic TCP/IP stack.

If step 5 fails with a firmware-related error, the path is firmware upgrade, not configuration tweaking. Move directly to Section 6.

6. Resolution 1: Restoring Upload from the CPU 1214

There are two valid recovery paths. Pick by production constraints.

6.1 Path A — Stay on TIA V13 SP1, Upgrade CPU Firmware

1. Download the matching firmware file (S7-1200 FW V4.0 or V4.1, the .upd file) from the Siemens Online Support portal.
2. Verify the file's SHA-1 / MD5 against the value Siemens publishes next to the download.
3. In TIA V13 SP1, Online > Accessible nodes > select CPU > right-click > Online > Diagnostics > Functions > Firmware update. Browse to the .upd file.
4. Confirm the warning. The CPU performs a warm restart with factory data reset — all process values, retentive data, and the on-line program are erased.
5. Wait for the CPU to come back online. Confirm the new firmware on the diagnostics page.
6. Re-attempt Online > Upload from device (software). The upload should now succeed and create a new offline project tree with the on-line program reconstructed.

6.2 Path B — Downgrade TIA to V12 SP1 (preserve current firmware)

1. Uninstall TIA V13 SP1 cleanly. TIA V12 SP1 and V13 SP1 cannot coexist on the same installation; partial uninstalls leave the S7ONLINE access point in a corrupt state.
2. Install TIA V12 SP1 (with the latest Hotfix bundle for V12) on the Windows 7 32-bit host. The S7-1200 CPU 1214C with firmware 2.x is a first-class citizen of V12 SP1.
3. Open the offline project — if it was created in V13 SP1, right-click the project > Export to TIA V12 is not supported; you must open the original V11 / V12 source archive or rebuild from the upload.
4. Use the same access point and cable. Upload will now succeed and the entire program tree will be visible.

Path B is the right answer when the production line cannot tolerate a firmware change. Path A is the right answer when the engineer must stay on V13 SP1 for other reasons (project reuse, team standardization, licensing).

7. Resolution 2: Enabling Compare Online/Offline (PC-PLC)

Compare becomes available automatically once the upload succeeds. If it still reports "Compare PC-PLC program not available" after a successful upload:

1. Confirm the offline project tree contains the same CPU type as the online device. A mismatch at this level prevents TIA from constructing a comparable object model.
2. Right-click the PLC in the project tree > Go to online. The two project trees must show the same node depth.
3. If the offline tree is missing a block present in the online tree (most often a system block added by an SP update, or an FB whose interface has shifted), right-click the PLC > Compare > Online/Offline and accept the proposed reconciliation.
4. For a permanent fix, switch the offline project to Online > Snapshot of the online content mode so subsequent round-trips do not require a manual compare.

8. Resolution 3: Restoring RUN-Mode Download After Retain Memory Changes

The retain memory area is set in CPU properties > System and clock memory > Retentive memory. Any change in this dialog invalidates the RUN-mode delta. Recovery procedure:

1. Open CPU properties > Retentive memory. Screenshot the current setting for the change record.
2. Revert to the previous setting (the values that were in place before the failure). The values are read back from the project, not from the CPU, so an earlier project backup is required.
3. Compile the project (Project tree > right-click PLC > Compile > Software (rebuild all blocks)).
4. Right-click the PLC > Download to device > Software (only changes). TIA will now compute a clean delta. If the retain area is unchanged, the download proceeds in RUN.
5. If the change to retain is intentional, you must accept a STOP-mode download. To minimize process disruption, perform the change during a planned maintenance window, and download with Online > Download to device > Software (full). Confirm the prompt to STOP the CPU, then restart.

9. Resolution 4: Restoring the CALL Instruction in LAD

Missing CALL in the LAD instruction pane has only one fix: align the offline CPU type with the on-line CPU firmware.

1. Open Project tree > PLC_x > Device configuration. Double-click the CPU picture.
2. In the Properties > General pane, click Change device.
3. Pick the exact CPU from the catalog: SIMATIC S7-1200 > CPU > CPU 1214C > DC/DC/DC > 6ES7 214-1AE30-0XB0 (or the BA0 variant if the catalog exposes it).
4. Select the firmware version that matches the on-line device. TIA will then expose the full LAD instruction set — including CALL, RET, JMP-list, and the IEC timer / counter FB calls — for that firmware.
5. Recompile all blocks. The CALL instruction reappears under Instructions > Program control operations.

10. Field Commissioning and Verification

After each of the four resolutions, run this verification sequence:

1. Online consistency: Project tree > right-click PLC > Go online. Both the offline and online indicators should turn green; the connection status line must read "Connected" with the detected CPU firmware and IP.
2. Block reconciliation: Right-click PLC > Compare > Online/Offline. The diff must be empty (or limited to the expected changes).
3. Diagnostic buffer: Online > Diagnostics > Diagnostic buffer. The most recent entries should show only the expected download events, not stop-initiated restarts unless those were intentional.
4. Retentive data: trigger a power-cycle test of the CPU (pull the power, wait 10 s, restore). The retentive M bits and DB tags must come back with their pre-cycle values.
5. Web server (sanity check): if the CPU has the standard web server enabled, browse to http://<CPU IP>. The "Module Information" and "Diagnostic Buffer" tabs should both load — a quick end-to-end confirmation that the Ethernet / PROFINET stack is healthy.
6. Cycle time: Online > Diagnostics > Cycle time / memory. Record the OB1 minimum, maximum, and current cycle times. A correctly running CPU 1214C with a typical 50-block program should report a cycle time well under 10 ms; values over 50 ms indicate a runaway loop or excessive communication load and are not related to the V13 SP1 issue.

11. Preventive Best Practices

• Pin the engineering tool version to the firmware. Maintain a project register that records, for every PLC in the plant, the exact TIA Portal version and SP / Update used to last download the program. Do not allow ad-hoc upgrades.
• Version the project, not just the file. Use a VCS (Subversion, Git, or TIA's built-in project history) and tag every release with the matching TIA Portal version. The Siemens entry on cross-version upload (support entry 109746794) is the canonical reference for what survives a version round-trip.
• Treat retain memory as configuration freeze. Once a CPU is in service, never change the retentive boundary without a maintenance window. The boundary is effectively part of the process contract.
• Archive the CPU firmware file (.upd) alongside the project. Without the matching firmware file, a future upload from a corrupted CPU is impossible to recreate on a replacement unit.
• Document the access point. The S7ONLINE access point must point to the CP 5711 / CP 5611 / TCP/IP stack that is physically connected. A misconfigured access point produces the same "CPU does not allow uploads" wording as a firmware mismatch — and is the easier of the two to fix.
• Test RUN-mode downloads in the panel shop, not the plant. Any non-trivial change (DB interface, retain area, block signature) should be exercised on a test bench before being applied to a running process.

12. Frequently Asked Questions