Uploading TIA V14 Project from S7-1200 CPU Using TIA V15

Overview: The TIA V15 Upload Dialog on a V14-Programmed S7-1200

An engineer who has only TIA Portal V15 installed on the engineering station and tries to upload from an S7-1200 CPU whose program was authored in TIA V14 (or V14 SP1) frequently sees the dialog:

"The program in the connected device is not compatible with the version of TIA Portal. Online functions cannot be performed."

The wording is misleading. STEP 7 in TIA Portal V15 is a downward-compatible consumer for online operations: V15 can upload, monitor and download against CPUs that were programmed with V11, V12, V13, V14 and V14 SP1. The dialog is fired by one of the following real boundary conditions:

1. Firmware-version mismatch. The S7-1200 CPU is at a firmware level (V4.3 / V4.4 / V4.5 / V4.6 / V4.7) that was introduced together with a TIA Portal later than V15. The V15 type catalogue does not contain system data blocks for that firmware and rejects the online binding.
2. Hardware-generation mismatch. The CPU is an S7-1200 G2 (article numbers of the form 6ES7 2xx-1A*** with G2 hardware) that is a TIA V18-only target. TIA V15 has no device description for the G2 family and refuses to bind online.
3. Feature pack / HSP mismatch. The V14 project used a function or a module that was contributed by an optional Hardware Support Package (HSP) loaded into the V14 install. If the same HSP is not present in the V15 install, the type cannot be deserialized and the upload fails.
4. Project-not-open scenario. The user clicked "Connect online" with no project open. TIA V15 sometimes refuses the connection if the device description cannot be unambiguously mapped to a target object. The remedy is to use "Upload device as new station" or the "Upload to PG/PC" wizard.

Know-how protection and password protection on individual blocks do not block the upload itself — the blocks are read into the offline project, but the source code is removed. The 21-day TIA V14 trial license is a fully functional STEP 7 Basic + Professional license and is the recommended workaround when a permanent V14 license is not available. Multi-installation of V11, V12, V13, V14 and V15 on the same PC is officially supported by Siemens and does not require a second license key; only one TIA Portal instance is active at a time.

TIA Portal Compatibility Architecture and S7-1200 Firmware Matrix

The TIA Portal is a single installation shell that hosts several editors. STEP 7 Basic (S7-1200 / S7-1500), STEP 7 Professional (S7-300/400/WinAC), WinCC, Startdrive, Safety and PLCSim are each licensed separately. The license bound to the PC determines which editors are active. When the user clicks "Go online" or "Upload from device", TIA Portal executes the following checks in order:

1. Device-description lookup against the connected CPU's article number (MLFB / order number).
2. Firmware-version check — the firmware on the CPU is compared against the set of firmware versions known to the installed TIA version.
3. Project-compatibility check — if a project is open, the project file's TIA-version header is compared against the current TIA version.
4. Block-by-block deserialization — every OB / FB / FC / DB / SDO in the CPU is deserialized into the V15 type system. Any type that V15 cannot resolve triggers a hard error.

TIA Portal supports the following version transitions for "open project" operations:

The same matrix applies in reverse: a V15 project can be opened in V15 and V15.1 only. V14 cannot open a V15 project. The online-direction compatibility is broader: V15 can go online against a V14 CPU even if the V15 project was started from scratch (no V14 backup on disk).

The S7-1200 firmware line evolved as follows:

A CPU that has been flashed to firmware V4.2 or below can be reached by TIA V15. A CPU at V4.3 or above cannot. The exact firmware of the connected CPU can be read at Online & diagnostics > General > CPU information, on the CPU's display (where fitted) under Settings > Information > Firmware version, or via the S7-1200 web server at http://<cpu-ip>/Portal/Portal.mwsl?PriNav=Diag.

Prerequisites for the Upload Operation

Before you start the upload, gather the following items. Items 1–4 are required; item 5 is only required for the trial-license workaround.

1. Programming cable or network connection. The S7-1200 CPU has no MPI interface, so PROFINET over Ethernet is the only network option. Use a Cat-5e or Cat-6 patch lead from the engineering PC's Ethernet port to the CPU's PROFINET socket.
2. CPU IP address and subnet. Default for an out-of-the-box CPU is 192.168.0.1 / 255.255.255.0. The CPU must be reachable on the engineering subnet. Use ping <cpu-ip> from a Windows command prompt to verify layer-3 connectivity before launching TIA Portal.
3. PG/PC interface assignment. In TIA Portal, the "Online access" must be set to the network adapter that is physically connected to the CPU. The "Set PG/PC interface" tool (Start > Siemens Automation > Set PG/PC interface) is used to bind the S7ONLINE access point to a specific adapter. For direct Ethernet, select the adapter and the TCPIP protocol.
4. CPU protection state. If the CPU carries an access password (configurable under Device configuration > Properties > Protection & Security), the password must be supplied when going online. The four protection levels are: full access (no password), read-only access, no access (HMI only), and no access (HMI and web). The default is "full access".
5. TIA V14 trial license (only for the multi-install workaround). The TIA V14 trial can be downloaded free of charge from the Siemens Industry Online Support portal. The trial binary is a full STEP 7 Basic + Professional install that you can use to perform the upload exactly as you would with a permanent license. The trial is valid 21 days from first activation.

Recommended supporting tooling:

• Siemens Primary Setup Tool (PST) — for IP and PROFINET device-name assignment without TIA Portal.
• S7-1200 system manual — for the wiring diagram and the article-number lookup.
• TIA Portal product page — for the latest service packs and HSPs.

Solution A: Direct Upload in TIA V15 (No Project File)

This is the recommended path when the engineering station has no project backup of the V14 program and the CPU itself is the source of truth. TIA V15 builds a brand-new V15 project from the CPU's contents. The "Upload device to PG/PC" wizard is the single command that performs the entire operation.

Procedure

1. Open TIA Portal V15 with a new (empty) project. From the project tree, select Project > Upload device to PG/PC (labelled "Upload from device" in some V15 sub-versions).
2. In the "Upload device to PG/PC" dialog, set the target type filter to SIMATIC S7-1200 and the PG/PC interface to the network adapter that is physically connected to the CPU (e.g. "Intel(R) Ethernet Connection I219-V / TCPIP").
3. Click Start search. TIA V15 broadcasts a DCP/LLDP probe and lists the reachable S7-1200 CPUs. The probe result is refreshed every 5 seconds.
4. Select the target CPU from the list by clicking the row. The CPU's article number, IP address, firmware version and PROFINET device name are displayed in the preview pane.
5. Click Upload. TIA V15 creates an "Unlinked device" (an un-placed station) under "Devices & networks" containing the uploaded blocks. The CPU's runtime, IP address, PROFINET device name and module parameter settings are uploaded into the device configuration.
6. Save the project. The blocks are now in V15 format because TIA V15 re-serialised them on upload. The file extension is .ap15.

Caveats specific to the V15 direct upload

• If the CPU was programmed with a V14 HSP that V15 does not know, the affected blocks are uploaded as "Type cannot be resolved" warnings and the source code is not available. The fix is to install the matching HSP in V15 (Options > Support Packages) and re-upload.
• If the CPU is at a firmware level above V4.2, the upload itself is blocked before it starts. TIA V15 reports "The device does not support online operations with this version of TIA Portal". You must either install a newer TIA version (V15.1 / V16) or downgrade the firmware (only possible on certain CPU revisions and only if the firmware downgrade image is available).
• The upload captures the online blocks, not the offline project. Any blocks that are present in the project backup but not in the CPU are not recovered by this path. The reverse path ("online blocks exist that are not in the project") is recorded as a difference in the comparison view.
• If the CPU has password-protected blocks, the source code is replaced by placeholders labelled "Know-how protected block". The block's signature and length are preserved, but the FBD/LAD/ST body is removed.

Solution B: Multi-Install TIA V14 Trial Alongside TIA V15

When the V15 direct upload fails because of a firmware or HSP boundary, the cleanest workaround is to install TIA V14 on the same PC, perform the upload in V14, save the project as a V14 .ap14 file, and then open the file in V15 for migration.

Install the TIA V14 trial

1. Open the Siemens Industry Online Support portal and search for "STEP 7 TIA Portal V14 trial". The trial is delivered as a multi-DVD ISO image of approximately 8 GB.
2. Mount or extract the DVD image and run Start.exe from the root of the mounted volume.
3. Select the install scope: STEP 7 Basic is enough for S7-1200 work; STEP 7 Professional is only required if the V14 project also contains S7-300/400 code. WinCC and Startdrive are not required for this scenario.
4. The installer detects the existing V15 install and places V14 side-by-side in a separate directory (default C:\Program Files\Siemens\Automation\Portal V14\). The V15 install is not modified.
5. Restart the PC. The Siemens Automation Shell registers V14 as a "secondary portal". Double-clicking a V14 .ap14 file launches V14; double-clicking a V15 .ap15 file launches V15.

Use the trial license

1. Start TIA V14. The license manager detects that no license is installed and offers the trial license.
2. Activate the trial. The license is valid 21 days from this point and is a full STEP 7 Basic + Professional license; there is no functional difference between the trial and a permanent license other than the time limit.

Perform the upload in V14

1. Open TIA V14, create a new project, and use Project > Upload device to PG/PC exactly as described in the previous section.
2. Save the project. TIA V14 saves it as a .ap14 file.
3. Close TIA V14 and open the .ap14 file in TIA V15. TIA V15 prompts for a project upgrade. Confirm. The project is now in V15 format and can be edited, compiled and downloaded as a normal V15 project.

Solution C: Project Migration V14 to V15 in a Single TIA V15 Instance

If a V14 project backup exists on the engineering PC or a network share, the cleanest path is to open it directly in TIA V15 and let the portal perform an in-place upgrade. The upgrade is non-destructive: a copy of the V14 source is placed in the project's _UpgradeLogs folder.

1. Launch TIA V15.
2. Select Project > Open existing project and navigate to the .ap14 file.
3. TIA V15 displays the compatibility dialog: "The project was created with a different version of TIA Portal. The project will be upgraded." Click OK.
4. TIA V15 rewrites the project into V15 format. The progress bar shows the number of blocks upgraded and the elapsed time. A V14 project of 200 blocks typically upgrades in 30–90 seconds on a current PC.
5. The portal performs a project-wide consistency check. Any block that uses a V14-only type (e.g. a function contributed by an HSP that V15 does not know) is flagged with a compile error in the project tree.
6. Resolve the compile errors by installing the matching HSP, deleting the affected blocks, or replacing the type with a V15 native type.
7. Compile the project (right-click CPU > Compile > Hardware and software (rebuild all)). Download to the CPU or upload from the CPU as required.

Blocks that reference V14-only types are usually preserved in the project as "stubs" — the block is present but its body is empty and the type is unresolved. The fix is one of:

• Install the matching HSP in TIA V15 (most common).
• Re-import the block from a TIA V14 backup of the same project (TIA V15 can import .ap14 blocks into a .ap15 project via the "External source" import under PLC > External source > Generate blocks from external source).
• Re-create the block manually in V15 if the original was a custom library block.

License Architecture and Multi-Install

A single TIA Portal license key unlocks the TIA version it is bound to, plus all earlier versions of the same tool family. Specifically, a STEP 7 V15 license enables STEP 7 in V15, V14, V13, V12, V11. The license does not enable functionality above the level that the original license authorises: a STEP 7 Basic V15 license cannot be used to unlock STEP 7 Professional in V13, because the V13 install is the same scope as the V15 install (Basic, not Professional).

The 21-day TIA V14 trial license is therefore a viable substitute for a permanent V14 license in this exact scenario, because the only feature the user needs is "upload blocks from an S7-1200", which is a STEP 7 Basic function. The trial is bound to a single PC and cannot be transferred. The same trial key cannot be activated on a second PC, even temporarily.

Step-by-Step Upload Procedures

Procedure 1 — Upload without a project file (TIA V15 only)

1. Connect the engineering PC to the S7-1200 CPU via the PROFINET interface. Verify layer-3 connectivity with ping <cpu-ip> -n 4 before opening TIA Portal. A TTL below 10 ms is desirable; a TTL above 100 ms indicates a routing issue.
2. Open TIA Portal V15. If a project is already open, close it; the upload is easier in an empty project.
3. Click Online > Upload device to PG/PC.
4. In the "Upload device to PG/PC" dialog, click the "Type" column header and select SIMATIC S7-1200.
5. Click "Start search". TIA Portal broadcasts a DCP identify request and lists every reachable S7-1200. The default search timeout is 30 seconds; extend it via the dropdown if the target CPU is on a slow link.
6. Right-click the target CPU and confirm "Upload". TIA V15 creates a new device under "Devices & networks" with the uploaded blocks and device configuration.
7. Save the project with Project > Save As and choose a meaningful name. The file extension is .ap15.
8. Right-click the uploaded CPU and select Compile > Hardware and software (rebuild all) to verify the project is consistent in V15 format.
9. Use Online > Go online to verify the online/offline match. The status bar should report "Online – diagnostic status OK".

Procedure 2 — Upload with a V14 project backup

1. Open TIA V15. Use Project > Open and select the .ap14 file.
2. Confirm the project upgrade dialog.
3. Wait for the upgrade to complete. The progress bar shows the number of blocks upgraded. A V14 project of 200 blocks typically upgrades in 30–90 seconds on a current PC.
4. Open Online > Accessible nodes to verify the CPU is visible on the network.
5. Use Online > Upload from device (software). TIA V15 overwrites the project blocks with the CPU's blocks. The "Upload from device" operation respects any online / offline differences and shows a comparison view before applying the upload.
6. Compile the project. Resolve any compile errors (typically type-mismatch warnings from blocks that referenced a V14 HSP).
7. Save the project. The .ap15 file now contains the live program from the CPU.

Monitoring a V14 Project in TIA V15 (Read-Only Path)

When the requirement is to monitor the running V14 program but not to download a new program to the CPU, a special workflow is supported:

1. Open the V14 .ap14 project in TIA V15 (project upgrade as above).
2. Do not modify any block. The project is now in V15 format but the block bodies are still the V14 source.
3. Use Online > Go online. TIA V15 binds to the CPU and shows the live values in the program editor, watch tables and force tables.
4. You can monitor, read, and write to non-read-only data blocks, but a download back to the CPU is blocked because the project is a V15 project and the CPU is at the V14 firmware level (or vice-versa).

The limitation is that the project cannot be downloaded back to the CPU after the upgrade without first being compiled cleanly in V15, which may introduce behavioural differences if the project used V14-only types. For diagnostic-only purposes, this path is sufficient.

Error Codes and Resolution Matrix

The following table maps the most common error messages encountered during a TIA V15 upload from a V14-programmed S7-1200 to their underlying cause and the recommended resolution.

S7-1200 G2 Hardware Considerations

The S7-1200 G2 family (launched 2023, TIA V18 exclusive) cannot be reached by any TIA version older than V18. The article numbers 6ES7 211-1A***, 6ES7 212-1A***, 6ES7 214-1A***, 6ES7 215-1A*** with the G2 hardware platform are distinct from the classic S7-1200 article numbers that carry the 1B / 1C / 1H / 1E revision letter. A G2 CPU plugged into a TIA V15 install will appear in "Accessible nodes" with a question-mark icon and the message "Device type cannot be identified".

If the engineering station has been given a G2 CPU for programming, the only supported action is to install TIA V18 (or newer) and use that for the upload. A downgrade of a G2 CPU's firmware is not supported; the firmware is pre-loaded at the factory and is not user-flashable below the V18 minimum. Similarly, the S7-1200 G2 CPU cannot be downgraded to a classic S7-1200 by re-flashing — the hardware platform is different.

Verification Checklist After the Upload

After the upload completes — regardless of which solution path you used — run the following verification sequence to confirm that the project is consistent and online binding is healthy.

1. Compile check. In the project tree, right-click the CPU and select Compile > Hardware and software (rebuild all). The output window should report "Compile finished — 0 errors, 0 warnings". Warnings are acceptable if they refer to known issues; errors are not.
2. Online binding. Click Online > Go online. The status bar at the bottom of TIA Portal should show "Online – diagnostic status OK" with a green icon. If the icon is yellow, there is a diagnostic warning (e.g. firmware mismatch in a module); if red, there is a hard error.
3. Block comparison. Use Online > Compare offline / online to confirm that every block in the project tree matches the corresponding block in the CPU. A "differences detected" result is acceptable as long as the differences are intentional.
4. Watch table check. Open a pre-configured watch table or create a new one, drag a few non-critical tags into it, and click the "Monitor" icon. The tag values should update in real time. The default update rate is 1 second; reduce it to 250 ms for fast-moving signals via the table's properties.
5. Diagnostic buffer check. Open Online > Online & diagnostics > Diagnostic buffer. The buffer should not contain "Firmware update failed" or "Type conflict" entries dated after the upload.
6. Save and version. Save the project and commit it to the version-control system. The .ap15 file is the new source of truth for the program. If the plant uses SVN or TIA's built-in project history, commit with a meaningful change message ("Uploaded from CPU 6ES7 214-1AG40-0XB0 FW V4.2 via TIA V15 trial").

FAQ