Problem Definition: TIA Portal V13 to V14 Upload Connection Failure
When attempting to upload a PLC program to a programming device (PG/PC) running TIA Portal V13, the engineering tool reports the error "Failed to establish a connection to the device" with the target PLC's MAC address (for example 28-63-36-7e-90-18). The PLC responds to the standard "detect" action in the Online & Diagnostics view, and the IP address is visible on the network, but the project cannot be uploaded back into the engineering station.
The root cause is almost always a version mismatch between the TIA Portal project stored on the CPU and the TIA Portal version installed on the programming device. If the CPU was projected with TIA Portal V14 (or V14 SP1) and the PG is running TIA Portal V13 (or V13 SP1), the online connection can be partially established for diagnostics, but the upload-back function refuses to load a project whose container version is newer than the TIA Portal currently running on the PG.
Root Cause Analysis
Siemens introduced a strict project-container versioning scheme starting with TIA Portal V13 SP1. Each project XML container carries a SchemaVersion header that is read by the TIA Portal at open time. When the schema version embedded in the CPU is greater than the schema version supported by the PG installation, the following errors are reported depending on the access path used:
| Symptom | Location in TIA Portal | Likely Cause |
|---|---|---|
| "Online connection could not be established" | Project tree → PLC → Online & Diagnostics | PG/PC version older than CPU project version |
| "Device is not specified" after pressing Upload | Online → Upload device to PG/PC | Project on CPU is newer than the installed TIA Portal |
| Detect button returns empty hardware catalog | Online access → → Detect | Online services partially available, project upload blocked by version check |
| PG/PC sees the IP and MAC of the CPU but cannot browse | Accessible nodes → Online & Diagnostics | TCP/IP reachable, S7 communication refused by TIA version gate |
The MAC address 28-63-36-7e-90-18 is an OUI-prefixed Siemens PROFINET device identifier (the first three octets 28-63-36 are assigned to Siemens AG). If the CPU is reachable at the IP layer but TIA Portal V13 reports the same error after pressing Detect, the CPU's project container is built against a TIA Portal V14 or V14 SP1 schema. To confirm this without dismantling the panel, use the Online & Diagnostics view once the device is reachable.
Confirming the TIA Portal Project Version on the CPU
Before installing a new TIA Portal version, identify the exact project schema stored on the CPU. The version can be read directly from the PLC using the Online & Diagnostics view.
- Open TIA Portal V13 and create a new blank project.
- In the project tree, expand Online access → select the network adapter bound to the subnet of the CPU.
- Right-click the detected CPU and choose Online & Diagnostics.
- Navigate to Diagnostics → General. The dialog box lists the TIA Portal project version used to build the program currently running on the CPU.
- Record the reported version. Typical values: V13, V13 SP1, V14, V14 SP1, V15, V15.1, V16, V17, V18, V19, V20.
TIA Portal Version Compatibility Matrix for Project Upload
| Project on CPU | Lowest PG TIA Portal version that can upload | Upload Behavior |
|---|---|---|
| V13 | V13 (same version) | Upload succeeds |
| V13 SP1 | V13 SP1 or V14 (after upgrade) | Upload succeeds with V14 onward |
| V14 | V14 or V14 SP1 (same major version) | Upload succeeds |
| V14 SP1 | V14 SP1 or V15 (after upgrade) | Upload succeeds |
| V15 / V15.1 | V15 or V15.1 | Upload succeeds |
| V16 | V16 | Upload succeeds |
| V17 | V17 | Upload succeeds |
| V18 | V18 | Upload succeeds |
| V19 | V19 | Upload succeeds |
| V20 | V20 | Upload succeeds |
Per the official Siemens Support entry, projects that originate from a TIA Portal earlier than V13 SP1 cannot be upgraded in V14 or later; they must first be re-saved with V13 SP1 minimum. See the Siemens Support article 109476392 for the complete compatibility ruleset.
Solution Path A: Upgrade TIA Portal from V13 to V14 on the PG/PC
The recommended field-proven procedure is to upgrade the TIA Portal installation on the PG/PC to TIA Portal V14 SP1. The V14 license already owned by the site can be reused for the upgrade or migrated forward.
Prerequisites
- Windows 7 SP1 / Windows 10 / Windows Server 2012 R2 or 2016 (refer to the TIA Portal V14 SP1 installation guide for the specific build matrix).
- At least 10 GB of free disk space for the TIA Portal V14 SP1 base installation.
- Microsoft .NET Framework 4.6.2 and SQL Server 2014 SP2 (or higher supported by the V14 installer).
- Existing TIA Portal V13 license key (floating or single) and a valid upgrade license to V14, or a fresh V14 license.
- Administrative rights on the PG/PC.
Step-by-Step Upgrade Procedure
- Close all running TIA Portal instances and stop the S7TraceService and ALM (Automation License Manager) services.
- Insert the TIA Portal V14 SP1 installation DVD or mount the ISO downloaded from the Siemens Industry Online Support portal.
- Launch
Start.exefrom the installation medium and accept the license agreement. - Select the Upgrade installation option when the installer detects an existing V13 installation. The installer will keep the existing project database and migrate the registry entries.
- Choose the products to migrate: STEP 7 Professional V14 SP1, WinCC Professional V14 SP1, PLCSIM V14 SP1, and the Safety Advanced / Safety Basic options as required by the original project.
- Enter the V14 license key (or point to the license server if a network license is in use).
- Reboot the PG/PC when prompted.
- Launch TIA Portal V14 SP1 and verify the project opens without a Schema mismatch warning.
After the upgrade, follow the standard project upgrade flow described in the TIA Portal V20 documentation - Upgrading projects to migrate a V13 project to the V14 schema before opening it on a V14 SP1 PG.
Solution Path B: Install a Trial V14 SP1 Alongside V13
If the existing V13 license cannot be upgraded yet, install TIA Portal V14 SP1 as a trial alongside V13 to perform the upload. Siemens provides a TRIAL download with a 21-day evaluation key, sufficient for one upload session.
- Download SIMATIC STEP 7 including PLCSIM V14 SP1 TRIAL from the Siemens Support portal.
- Install the trial version with default options; the installer supports side-by-side installation with V13.
- Launch the trial V14 SP1 instance, create a new project, and use Online → Upload device to PG/PC against the CPU.
- Export the uploaded project to a portable .zap14 archive using Project → Archive.
- Optionally, also archive the project as .zap13 from the V13 installation by first performing a Project → Upgrade inside V14 SP1 to bring it to a V14 schema, then re-saving through a V13 SP1 PG if a V13 deliverable is required.
Solution Path C: Identify the CPU Part Number and Re-target the Project
If the CPU part number is known (for example 6ES7 515-2AM02-0AB0 for an S7-1515-2 PN), an alternative path is to recreate the project from scratch in V13 and import only the block sources. This is rarely used in the field because it loses HMI tags and connection configuration, but it is valid as a last resort.
- Open Online & Diagnostics on the CPU and read the Order number / Firmware from the diagnostic buffer.
- If the diagnostic buffer cannot be read, power down the CPU, unclip it from the DIN rail (after sliding the bus bar away from the right-side module if one is present), and read the part label on the side of the module.
- Reinstall the module, restore power, and re-establish the online connection.
- Create a new V13 project with a device matching the order number and firmware version.
- Re-upload the blocks one by one through the S7 block container if the CPU allows it (this only works for CPUs whose firmware permits block-level upload, generally S7-300/400 with STEP 7 V5.x — not the S7-1200/1500 path described in this article).
Network and Connection Pre-Checks
Before assuming the version mismatch is the only cause, run the following checks on the PG/PC and the CPU.
| Check | Command / Method | Expected Result |
|---|---|---|
| Layer-3 reachability to CPU | ping <CPU_IP> |
Reply from CPU with <1 ms typical |
| PROFINET device discovery | TIA Portal → Online access → → Update accessible nodes | CPU appears with its IP and MAC |
| S7 communication port 102 |
Test-NetConnection <CPU_IP> -Port 102 (PowerShell) |
TcpTestSucceeded: True |
| PG/PC interface assignment | TIA Portal → Set PG/PC interface → S7ONLINE access point | Bound to the same NIC that has the route to the CPU |
| Firewall on PG/PC | Disable Windows Defender Firewall temporarily for testing | Upload succeeds only with firewall off → add an inbound rule for TCP 102 and the S7Trace ports |
| CPU protection level | Online & Diagnostics → Protection & Security | Protection level set to Full access (no password) or correct password known |
| Time-of-day synchronization | Online & Diagnostics → Set time | Time on CPU within 1 minute of PG |
If the CPU protection level is set to Read/Write protection or Complete protection with an unknown password, the upload will be refused even with a correct version match. Reset the protection level using the Siemens S7-1200/S7-1500 password reset procedure documented in the CPU manual; this requires a formatted SIMATIC memory card and a power cycle.
Verification Steps After Upgrade
- Open TIA Portal V14 SP1 and create a new project with the matching CPU part number.
- Right-click the new PLC device and choose Compile → Hardware (rebuild all) to confirm the device catalog recognizes the order number.
- From the project tree, right-click the PLC device and choose Go online. The online state indicator turns green.
- Choose Upload from device (toolbar or Online → Upload device to PG/PC). The full project — program blocks, tags, HMI screens, connections, and module parameters — uploads into the project tree.
- Save the uploaded project as a .zap14 archive for version control.
- Compare the uploaded project against a fresh project by selecting Project → Compare → Online/Offline to confirm no changes exist between the engineering image and the running CPU.
Common Pitfalls and Field Notes
- Mixing V13 and V14 in a multi-user environment. Floating licenses on a license server can be checked out by either V13 or V14 PG/PCs. Confirm that the V14 license is checked out when a V14 PG is in use; otherwise the upload will fall back to a trial mode that blocks the upload-back action.
- HMI tag references break across versions. When upgrading a project that contains WinCC Professional or Comfort Panel tags, always open the HMI portion of the project in V14 SP1 and re-compile before pushing the new image to the panel. Tag containers that were not migrated cause runtime errors at panel start-up.
- S7-1500 firmware compatibility. An S7-1500 CPU with firmware V2.9 cannot be opened in TIA Portal V14 SP1 without first upgrading the CPU to at least firmware V2.6. Use the Siemens SIMATIC S7-1500 firmware update tool to bring the CPU firmware to a level supported by V14 SP1.
- Detecting the project version from the diagnostic buffer. The diagnostic buffer entry for the most recent project download lists the engineering tool version. Filter the diagnostic buffer for entries containing Online and inspect the tool version string.
- Don't downgrade a project schema. Once a project has been saved in V14 or later, TIA Portal V13 cannot open it. Always archive the original V13 deliverable before triggering the project upgrade on the V14 PG.
Troubleshooting Matrix
| Symptom After Upgrade | Likely Cause | Remediation |
|---|---|---|
| "TIA Portal V14 cannot be installed because V13 is detected" | V13 install directory not empty, ALM still running | Run Stop S7TraceService from the Windows services console, then retry the upgrade |
| License manager reports Invalid license key | V14 upgrade license not yet activated | Use the ALM to transfer the V14 license from the V13 key |
| Upload finishes but project blocks are empty | CPU protection password active, blocks hidden | Enter the protection password in Online & Diagnostics → Protection |
| Detect shows the CPU but Upload still fails | Time-of-day skew > 1 minute between PG and CPU | Set PG and CPU clocks via Online → Set time |
| V14 trial expired, V14 PG cannot open project | Trial license timed out | Activate a full V14 license, or install a newer TIA Portal version that supports the same project |
| Project from a third-party PLC not supported in V14 | Original project not in TIA schema | Use the original vendor's engineering tool to perform the upload |
Alternative Approach: Migrate to a Newer TIA Portal Version
If the site plans to move forward in TIA Portal versions, install TIA Portal V16 or V17 alongside V13. TIA Portal V16+ retains backward compatibility with V13 SP1, V14, and V14 SP1 projects for the upload-back function. A site-wide migration is recommended when multiple machines are on different TIA versions, because it eliminates the version-gate failure mode entirely.
To migrate:
- Install TIA Portal V16 (or V17) with the STEP 7 Professional and WinCC Professional options.
- Open the V13 project, choose Project → Upgrade, and follow the wizard to bring the project to the new schema.
- Compile the hardware and software, then upload the new image to the CPU.
- Validate by performing a full online compare and a CPU restart.
FAQ
Can TIA Portal V13 upload a project from a CPU programmed with V14?
No. TIA Portal V13 cannot upload a project whose container was saved in V14 or higher; the upload is blocked by the project schema version check. The PG must be upgraded to V14 SP1 (or higher) to perform the upload-back.
How do I identify which TIA Portal version was used to program a CPU?
Connect the PG to the CPU, open Online & Diagnostics → Diagnostics → General; the dialog reports the TIA Portal project version used for the last download. The same information is also available in the diagnostic buffer under the Online filter.
Is a TIA Portal V14 trial license sufficient for a one-time upload?
Yes. The 21-day trial of SIMATIC STEP 7 including PLCSIM V14 SP1 from the Siemens Support portal is fully functional and can perform an upload to PG/PC. Replace the trial with a full V14 license before the 21-day window expires to avoid losing access.
Can a V14 license be used on a V13 installation?
No. A V14 license is bound to the V14 or V14 SP1 major version of TIA Portal. A V13 PG requires a V13 license. To move a V13 license to a V14 installation, purchase the V13 → V14 upgrade license through Siemens and transfer the key using the Automation License Manager.
What happens to my V13 project when I upgrade TIA Portal to V14?
The V13 project is not automatically modified. When opened in V14 SP1, the project triggers the Upgrade wizard that converts the project container to the V14 schema. Archive the original V13 project before upgrading so that a fallback is available.