S7-200 to S7-1200 Migration in TIA Portal V13: Complete Path

Overview

The S7-200 to S7-1200 migration path in TIA Portal V13 is a multi-stage conversion, because the official Siemens converter tool targets earlier TIA Portal versions. The converter that reads legacy STEP 7 Micro/WIN projects (.mwp files) is bound to the V10.5 / V11 API surface, and TIA Portal V13 cannot host that converter directly. The correct migration chain is: Micro/WIN .mwp -> TIA Portal V11 SP2 + S7-200 Converter add-on -> (optional) TIA Portal V12 SP1 -> TIA Portal V13 project. A single TIA Portal V13 license activates V11, V12, and V13 in parallel, which makes the chain executable on one workstation without purchasing additional seats.

This reference documents the version-binding error, the licensing model that makes the workaround practical, the exact installation sequence, the file-format handling, and the verification steps required to commission a converted S7-1200 program with the same I/O behavior as the original S7-200.

Why Direct Conversion in V13 Fails

When the user invokes the S7-200 -> S7-1200 converter inside TIA Portal V13, the tool reports the following error:

This is not a misconfiguration. The converter shell (the executable that walks the Micro/WIN symbol table, OB/FB/DB tree, STL/SCL instructions, and converts them to S7-1200-compatible constructs) is bound to the V10.5 / V11 import API. V13 changed the project schema and the import interface, so the V11 shell will not load against the V13 TIA Portal host process. Forcing the install results in an entry not registered in the V13 import menu, or a process that aborts immediately when invoked.

Prerequisites

Source File Inventory

Before starting the migration, catalog every source artifact in the legacy S7-200 project so nothing is lost in conversion:

• *.mwp - Micro/WIN project file containing ladder logic, STL subroutines, data blocks, symbol table, status chart, and cross-reference
• *.awl - STL source exports from Micro/WIN (manual or wizard export)
• *.txt - Symbol table text exports, PID wizard data, recipe files
• *.ldb / *.dat - Recipe data blocks and data logs
• Library additions - any user or Siemens libraries referenced by the project
• Project tree backups - any subfolder-stored .mwp copies

Conversion Architecture: Three-Stage Path

The migration chain consists of three discrete projects. Each stage has its own tool and license footprint, but all three versions run on the same PC under the V13 license umbrella.

Stage 1 - TIA Portal V11 SP2 with S7-200 Converter

The V11 SP2 installation is the only TIA Portal version that hosts the official S7-200 -> S7-1200 converter add-on. The converter shell is invoked from inside TIA Portal's project view (under "Project" -> "S7-200 migration" or via the dedicated menu entry installed by the add-on) and walks the .mwp file's program structure element by element.

What the converter handles automatically:

• Bit memory (M), inputs (I), outputs (Q), timers (T), counters (C) renumbering where needed
• Main program (OB1) and subroutines (SBR0..SBRn) mapping to FC/FB blocks
• Data block initialization (V memory) to DB blocks
• Symbol table import with V -> DB renaming prefixes
• STL instruction set conversion (most 200-instructions map 1:1 to 1200 STL; some like PLS, NETR/NETW require manual rework)

What the converter flags for manual rework:

• PLS (Pulse Output) - S7-1200 uses CTRL_PTO / CTRL_HSC function blocks, not a single PLS call
• NETR / NETW (USS / Modbus master on PPI) - replaced by MB_MASTER / MB_SLAVE or MODBUS_xxxx blocks on S7-1200
• RTC (Read Real-Time Clock) - replaced by RD_SYS_T / WR_SYS_T
• Legacy PID wizard outputs - replaced by PID_Compact V2 in S7-1200
• Memory area size mismatches - V memory mapped to DB; size must be reviewed against the target CPU's DB limits

Stage 2 - Optional TIA Portal V12 SP1 Bridge

V13 can open V11 SP2 projects directly through the file open dialog with automatic upgrade, but in some legacy V11 SP2 Update 4 or earlier builds the upgrade wizard refuses with "Source version too old." In that case, perform an intermediate V12 SP1 save:

1. Open the V11 SP2 .ap11 project in TIA Portal V12 SP1.
2. Accept the upgrade prompt and let the schema migrator complete.
3. Save the project as a V12 .ap12 file.
4. Close V12 SP1 and open the .ap12 in V13.

This intermediate bridge is also useful when the V11 SP2 project contains add-in generated blocks that V13's schema migrator cannot reach directly. Going through V12 SP1 forces a re-compile of all generated blocks into the V13-compatible representation.

Stage 3 - TIA Portal V13 Final Project

Open the .ap12 (or .ap11 if directly upgradeable) in V13. V13 prompts for a schema upgrade; accept and let it complete. The project is now in the V13 schema and can be edited, compiled, and downloaded to any S7-1200 CPU from firmware V2.0 upward. For S7-1200 CPUs with firmware V4.x, use TIA Portal V13 SP1 or later to access the extended instruction set (motion, PID_Compact V2, etc.).

TIA Portal Multi-Version Licensing

Siemens' Automation License Manager (ALM) allows a single TIA Portal V13 license to activate earlier versions in parallel on the same machine or floating license server. This is the licensing mechanism that makes the three-stage migration practical.

License Behavior

The "demo" or trial version of TIA Portal V11, when installed on a workstation that already carries a valid V13 license, runs as a fully functional V11 instance - not time-limited, not module-restricted. This is the cleanest way to obtain the V11 environment for the S7-200 conversion stage without purchasing additional seats. Contact a Siemens distributor or the regional Siemens office to obtain the trial media, or download it from the Siemens Industry Online Support portal under "Trial Software."

Step-by-Step Migration Procedure

Step 1 - Prepare the Micro/WIN Source

1. Open the legacy .mwp in STEP 7 Micro/WIN V4.0 SP9.
2. Run File -> Archive Project to produce a clean, defragmented .mwp. This step is mandatory if the original .mwp was last saved with Micro/WIN V3.x or V4.0 SPx earlier than SP6.
3. Export the symbol table to symbols.txt via File -> Export -> Symbol Table.
4. Export any STL subroutines to *.awl via File -> Export -> STL Source.
5. Document all PID wizard loops (number, setpoint, process variable, output addresses) - they require manual mapping post-conversion.
6. Note the target S7-200 CPU type (e.g., CPU 226, CPU 224XP) and its exact firmware version. The S7-1200 replacement must be selected from the same I/O count bracket (digital + analog).

Step 2 - Install TIA Portal V11 SP2 and the Converter Add-on

1. Install TIA Portal V11 SP2 Update 5 (or latest Update level) from Siemens media. The installer is order entry 6ES7 822-0AA01-0YA0 (STEP 7 Basic V11 SP2) - this is the minimum SP level that hosts the S7-200 converter add-on reliably.
2. Install the S7-200 -> S7-1200 converter add-on. The add-on is a separate Siemens package - locate it on the "S7-200 Converter" CD or download from the Siemens support portal. Without the add-on, the "S7-200 migration" menu entry does not appear.
3. Verify installation by launching TIA Portal V11 SP2 and confirming Project -> S7-200 Migration is visible in the menu bar.
4. Apply the V13 license (already present on the machine) through ALM; V11 picks it up automatically when launched.

Step 3 - Run the Conversion

1. Launch TIA Portal V11 SP2.
2. Create a new project: Project -> New, name it descriptively (e.g., LegacyPress_Conversion.ap11).
3. Invoke Project -> S7-200 Migration.
4. Browse to the archived .mwp file and select it.
5. The converter analyzes the project and presents a conversion log. Each row indicates a successful conversion, a warning, or a manual rework item. Typical output:\li>

Conversion Log - S7-200 -> S7-1200
==========================================
[OK]    OB1 (Main)             -> OB1 in S7-1200
[OK]    SBR0 (Initialize)      -> FC1 "SBR0_Initialize"
[WARN]  SBR1 (PID_Loop1)       -> Manual rework required (PID Wizard)
[OK]    SBR2 (Modbus_Master)   -> FC3 "SBR2_Modbus_Master" with placeholder
[WARN]  SBR3 (PulseOutput)     -> Manual rework required (PLS not supported)
[OK]    VB0..VB1023            -> DB1 "V_Memory" (1024 bytes)
[OK]    Symbols (87 entries)   -> Imported to PLC tags table
[FAIL]  Library "ModbusLibV20" -> Not found; conversion aborted for this element
==========================================
Result: 18 OK, 3 WARN, 1 FAIL

Address every WARN and FAIL entry before continuing. WARN items are functional gaps (the program compiles but does not behave identically); FAIL items must be resolved because the converter cannot continue past them.

Step 4 - Resolve Manual Rework Items

Step 5 - Compile and Verify in V11 SP2

1. After resolving every WARN item, recompile the V11 SP2 project.
2. Confirm zero compiler errors and zero compiler warnings.
3. Perform a PLC program consistency check via Project -> Compile -> Software (all blocks).
4. Cross-reference the symbol table against the source symbols.txt to confirm every tag has been imported.
5. If the project will go through V12 SP1 (optional bridge), save it now and close V11 SP2.

Step 6 - Upgrade to V13

1. Open the V11 SP2 (.ap11) or V12 SP1 (.ap12) project in TIA Portal V13.
2. Accept the schema upgrade prompt. The upgrade takes 30 s to 5 min depending on project size.
3. Recompile all blocks under V13.
4. Select the target S7-1200 CPU (e.g., CPU 1214C DC/DC/DC, firmware V4.x). Configure the device and rack to match the field wiring.
5. Download to a real CPU (or PLCSIM V13) for live verification.

S7-200 to S7-1200 Mapping Reference

Common Errors and Resolutions

Verification and Commissioning

After download, verify functional equivalence between the converted S7-1200 program and the original S7-200 program. The verification is mandatory because the converter is mechanical at the instruction level, and semantic differences in interrupt OB scheduling, scan order, and edge semantics can produce subtle behavioral drift.

Online Verification Checklist

1. Establish online connection to the S7-1200 CPU via PROFINET or Ethernet.
2. Force all inputs to known states in the original S7-200 and capture outputs. Repeat on S7-1200 with the same input stimulus; compare output bitmaps bit-for-bit.
3. Verify symbol table: every S7-200 tag appears in V13 PLC tags with the correct data type and address (e.g., "Motor_Start" = %M0.0).
4. Verify V-mapped DB: dump DB1 contents on S7-1200 and compare against V-memory view from Micro/WIN. Pay attention to initial values - the converter sometimes initializes DB fields to zero where the S7-200 had non-zero defaults.
5. Cycle each PID loop in manual mode on S7-1200 and confirm setpoint tracking matches the S7-200 PID table.
6. Run a Modbus poll loop for at least 10 min on S7-1200 and confirm no timeouts or CRC errors; compare against S7-200 logs.
7. Capture trace recordings (V13 trace) over at least one full production cycle and compare time-stamped events against the S7-200 trace.
8. Verify scan time: S7-1200 scan should be comparable or faster than S7-200; if it is slower, profile with the S7-1200 cycle time / OB1 statistics.

Acceptance Criteria

• Zero unresolved warnings from the V11 SP2 conversion log.
• Zero compiler errors and zero compiler warnings in V13.
• 100% symbol table parity with the source.
• 100% I/O behavioral parity over a documented test sequence.
• PID tuning re-commissioned (if applicable).
• Communication subsystem validated against the field bus / device network.

Field-Proven Caveats

• Scan order is preserved only when the converter sees OB1 as the call root. If the original S7-200 used subroutines called from interrupt OB1 in a specific sequence, document the order before conversion; the converter preserves subroutine naming but not necessarily call sequence.
• V-memory addressing changes from byte to symbol: any STL code using VB100 directly now accesses DB1."V_VB100" (or similar). Operators used to scrolling through V-memory will need a DB watch table instead.
• Ton/Tof/Cton blocks become IEC timers with instance DBs. Each timer consumes a number in the 0..255 range and creates an IDB. Plan IDB count against the CPU's maximum DB count (CPU 1214C = up to 6000 DBs typically).
• PID wizard output is not convertible: the converter drops the S7-200 PID data block and expects the engineer to recreate the loop with PID_Compact V2. Re-tune from scratch; do not copy old Kp/Ti/Td blindly.
• PTO/PWM mapping is hardware-dependent: S7-1200 PTO outputs are bound to specific outputs on the CPU or signal board. Confirm the field wiring matches the configured axis output before commissioning motion.
• S7-200 PPI network is gone: S7-1200 has no PPI interface. If the legacy system used PPI to a TD200 or PPI master, plan for either an Ethernet migration or a CM1241 with Modbus RTU replacement.
• Encryption / know-how protection: know-how-protected S7-200 blocks are converted to a non-protected S7-1200 block with empty source. Re-apply protection in V13 after verification.

FAQ