TIA Portal V12 Trial: Resolving S7-1200 Upload Limitations

Problem Details: TIA Portal V12 Trial Cannot Upload S7-1200 Project

Engineers using the TIA Portal V12 Trial edition frequently encounter an asymmetric online behavior when connecting to an SIMATIC S7-1200 CPU that was originally programmed in TIA Portal V11. The symptom set is consistent and reproducible:

• Online Access (Accessible Devices) connects successfully to the S7-1200 CPU over PROFINET or Ethernet.
• Program blocks (OB, FB, FC, DB) are visible and read-only navigation is possible from the project tree under Online > Online & Diagnostics.
• Project upload to the programming device fails: the "Upload from device" (Upload station to PG/PC) action does not produce a writeable, saveable project on the engineering station.
• The Watch table (Monitor/Modify) opens but tag values do not refresh, or the table is disabled with a grayed-out monitoring icon.
• The Data Block editor does not show actual values; only the offline snapshot remains visible.
• Download to a connected CPU appears to work (block compilation, consistent checksum), masking the deeper offline/online inconsistency.
• Creating a new V12 project from scratch functions without restriction when a CPU is selected manually and tags are authored offline.

This combination is misleading because partial online functionality suggests a configuration or network issue, when in fact the root cause is a TIA Portal version-to-project binding rule combined with the licensing scope of the Trial edition and the absence of a licensed Step 7 Professional / Basic runtime. The behavior is documented as expected for projects authored in TIA Portal V11 when the engineering station runs V12 without a valid license and without proper migration handling.

Root Cause Analysis: Why Upload Fails

The failure is not a single defect. It is the intersection of three independent constraints that converge when a V11 project meets a V12 Trial engineering environment.

1. Project-to-Tool Version Binding

Every TIA Portal project embeds an internal schema version that corresponds to the TIA Portal major release in which the project was created and last saved. The schema cannot be silently downgraded. When V12 opens a V11 project via the compatibility tool, it produces a converted V12 schema copy; it does not retroactively turn the V11 project into a native V12 artifact on the PLC.

Uploading from a CPU returns whatever block structure currently resides in the CPU's load memory. If the CPU was last downloaded with TIA V11, the upload payload is a V11-schema project. V12 Trial can read those blocks for online viewing because the compiler recognizes them, but it cannot reconstruct a fully editable, compilable offline project because:

• V12 Trial lacks the full licensed symbol table and cross-reference engine when no valid license key is present at the time of upload.
• The upload wizard in V12 Trial, when no license is detected, restricts the resulting project to a read-only snapshot.
• Watch table and Data Block live monitoring require an online connection that maintains tag database synchronization; the Trial edition's online services terminate as soon as the licensing timeout is reached.

2. Trial Edition Licensing Scope

The TIA Portal V12 Trial is a time-bounded installation (typically 21 days of full operation after first launch). During this window, the user is granted access to all engineering functions provided that the project being opened was created in the same TIA Portal major version. Cross-version upload (V11 source on V12 target) is not part of the Trial's guaranteed functional matrix. Functionally:

3. S7-1200 Firmware and Block Container Specifics

The S7-1200 CPU stores compiled blocks (with absolute addressing baked in by the SCL / LAD / FBD compiler) in a system data block container. The container format is firmware-version-bound. When V12 Trial performs an upload, it queries the CPU for the block list and downloads the block payloads, then attempts to reconstruct the offline project. For S7-1200 firmware versions that pre-date V12 (firmware 1.x, 2.x), the reconstruction succeeds but the tag database may not fully rehydrate because the offline symbol information was generated by V11's compiler, which uses a slightly different internal symbol table layout than V12's.

The visible result is a "project shell" that compiles but cannot be saved with full information, or that compiles and saves but produces empty Watch tables and DB views. This is the same failure mode observed by users when their engineering workstation lacks the matching V11 license.

Confirming the Diagnosis

Before applying remediation, isolate the contributing factors with the following checks. Each check produces a binary result that points to the next action.

Check 1: Identify the Original TIA Portal Version

1. From the customer's machine (if reachable), open the original project in TIA Portal.
2. Navigate to Project > Properties and note the Project version field. V11.x projects report version 11.x.
3. Alternatively, right-click the project node > Properties > General and read the Last modified with TIA Portal version.

If remote access is unavailable, ask the customer to export the project's .zap12 (or .zap11) archive and email it. Inspect the archive header with a hex viewer; the project schema byte signature distinguishes V11 from V12.

Check 2: Determine the S7-1200 Firmware Version

1. Connect to the CPU using V12 Trial's Online & Diagnostics.
2. Open Online > Accessible Devices and double-click the CPU.
3. In the Diagnostics view, navigate to Diagnostics > Device Information.
4. Read the Firmware version field, e.g., V4.2.3, V4.5.1.

Compare against the TIA Portal V12 compatibility matrix:

Check 3: Validate the Trial License State

1. Open TIA Portal V12.
2. Navigate to Help > License Management.
3. Confirm the Trial License row is present and not expired.
4. Note any warning indicators on the License Type column; a yellow triangle means the Trial has entered its final 5-day countdown.

If the Trial has expired, V12 will refuse to open any project in writable mode, which masks the cross-version issue behind a license failure.

Solution: Match Engineering Tool to Source Project

The primary, field-proven remediation is to perform the upload with the same TIA Portal major version that authored the source project. Where that is not possible, a controlled migration is required.

Solution A: Use TIA Portal V11 for the Upload (Preferred)

1. Download the TIA Portal V11 SP2 Update 9 (or the latest V11 service pack available from the Siemens Industry Online Support portal) on a dedicated engineering machine.
2. Install V11 alongside V12 in a separate Windows user profile or a virtual machine to avoid TIA Portal's per-user registry conflicts.
3. Open V11, create an empty project, and connect to the S7-1200 CPU via Online > Accessible Devices.
4. Right-click the CPU > Upload from device > Hardware and Software. This produces a fully editable V11 project, including the original symbol table, watch tables, and DB structures.
5. Save the project as .zap11 and archive it.

Solution B: Migrate the V11 Project to V12 Offline First

If V11 cannot be obtained, perform an offline migration using the customer-provided project archive:

1. Open V12 Trial on the engineering machine.
2. Select Open existing project and load the .zap11 archive.
3. V12 prompts to run the Compatibility Tool. Accept and follow the wizard.
4. During migration, V12 rewrites internal references, updates the symbol table schema, and recompiles all blocks. This produces a native V12 project that can be saved, archived, and edited offline.
5. Connect to the CPU and use Compare Offline/Online to verify block-for-block equivalence.

Solution C: Direct Online Block Read (Read-Only Recovery)

When neither V11 nor the customer's archived project is available, perform a manual block-by-block recovery in V12 Trial:

1. Create a new V12 project matching the exact S7-1200 order number (e.g., 6ES7214-1AG40-0XB0) and firmware version.
2. Open Online > Accessible Devices and connect to the CPU.
3. Drag each block from the online view into the offline project tree. This transfers individual blocks but does not reconstruct the symbol table.
4. Re-enter tag names manually or import from a CSV export if the customer can provide one.

This solution is acceptable for forensic recovery or backup purposes but is not suitable as a primary engineering workflow.

Verification: Confirming the Fix Worked

After applying Solution A or B, validate with the following sequence. Each step must pass before the next is attempted.

Verification Step 1: Project Save and Reopen

1. Close and reopen the uploaded / migrated project.
2. Confirm the project saves without warnings about read-only mode or schema inconsistencies.
3. Check the project size on disk; a valid upload typically produces a project between 500 KB and 10 MB depending on program complexity.

Verification Step 2: Compile and Consistency Check

1. Right-click the CPU > Compile > Hardware and Software (rebuild all).
2. Confirm zero errors and zero warnings in the Inspector window.
3. Open the message window (Ctrl+Shift+M) and filter by Severity = Error.

Verification Step 3: Online Compare

1. Connect to the CPU via PROFINET.
2. Right-click the CPU > Compare Offline/Online.
3. Confirm all blocks show Identical status (green checkmark) for the software components.
4. Hardware may show differences if the IP address or module configuration changed during migration; download the hardware configuration if needed.

Verification Step 4: Watch Table Live Monitoring

1. Open or create a Watch table.
2. Click Monitor All (the glasses icon).
3. Confirm tag values refresh at the configured update rate (default 1000 ms).
4. Toggle a known output (e.g., %Q0.0) from the Watch table's Modify column and verify the physical output changes on the PLC.

Verification Step 5: Data Block Live Values

1. Open any DB (e.g., DB1 "GlobalData").
2. Toggle the view from Offline to Online using the toolbar dropdown.
3. Confirm actual values populate and refresh in the right-hand column.

Extended Diagnostics: Edge Cases and Field-Proven Caveats

Edge Case 1: Password-Protected Blocks

If the customer has password-protected know-how protected blocks (F-CPU safety blocks or proprietary FBs), the upload produces blank blocks with only the interface visible. Solution:

1. Request the block password from the original developer.
2. Use Options > Know-How Protection > Remove in the matching TIA version before upload.

Edge Case 2: Mixed Version Hardware Configuration

Projects that mix S7-1200 CPUs with ET 200S/SP/MP distributed I/O sometimes contain V11-only module descriptions. Migration to V12 may flag these as "Device replaced" and require manual re-selection of the module order number. Always export the hardware configuration before migration for reference.

Edge Case 3: SINAMICS Drive Integration

If the project includes SINAMICS G120 or V20 drives configured via the TIA Portal drive wizard, V11 and V12 use different GSD/GSDML files. Migration rewrites the device proxy but may require regenerating the drive parameter set with Startdrive. Plan a commissioning window if the drive is in production.

Edge Case 4: Multiple Engineering Workstations

If the customer's site has multiple engineers using mixed V11/V12 workstations, the project should be archived after every change with explicit version annotation. Set the Windows file properties to "Last Modified By" and the TIA Portal project properties to "Project Version" to avoid cross-version corruption.

Edge Case 5: Trial Already Expired

An expired V12 Trial cannot open any project in writable mode, even if the project is V12-native. Remedy: uninstall the Trial, reinstall the licensed version (or request a new Trial through the Siemens representative), then re-open the project.

S7-1200 Firmware Compatibility Matrix for V12 Trial

Recommended Engineering Workflow

For sites that maintain a mix of V11 and V12 projects, adopt the following workflow to eliminate upload ambiguity:

1. Pin one TIA version per project line. Assign V11 to legacy S7-1200 systems and V12 to S7-1200 firmware V3.x with V13+ for newer firmware.
2. Maintain a virtual machine image per TIA version. Use Hyper-V or VMware to isolate V11, V12, V13, and V15 environments on a single engineering workstation.
3. Archive after every download. Use Project > Archive with the date and operator name embedded in the archive filename.
4. Document the engineering version in the project title. Example: LineA_Conveyor_V11_20240612.
5. Schedule a controlled migration when commissioning new firmware. Never upgrade firmware and TIA Portal simultaneously; do one, validate, then do the other.

Licensing Path for Long-Term Support

If the customer's plant is locked to TIA V11 due to a long-running validation cycle, Siemens offers the SIMATIC Automation Tool and the TIA Portal Version Bridge concept through their Industry Online Support. For production environments, a floating license on a license server (ALM) is the recommended configuration so that any engineer can open the project with full functionality regardless of the workstation.

For evaluation purposes only, the Trial editions provide full engineering functionality for their respective TIA version. The Trial does provide full functionality, but only for projects created in the matching TIA Portal major version. The Trial is not a cross-version upload tool.

Summary of Fixes