Migrating S7-200 Micro/WIN Programs to TIA Portal V13 Complete

Overview of the Micro/WIN to TIA Portal Migration Challenge

Migrating an S7-200 program authored in STEP 7 Micro/WIN to TIA Portal V13 is a recurring engineering task whenever an older S7-200 CPU is being replaced by an S7-1200 or S7-1500. There is no supported automated converter in TIA Portal V13 that imports .mwp project files, and the legacy Micro/WIN-to-TIA migration add-on (originally bundled with early TIA V10/V11 releases) has been discontinued by Siemens. Field experience consistently shows that the legacy tool produced incomplete conversions: symbol tables were lost, subroutines (SBR) and interrupt routines (INT) were flattened into a single OB1 with no clear mapping, and any program using Freeport, USS, or Modbus RTU master libraries on the S7-200 required a complete rewrite anyway because the instruction set and library architecture differ substantially between the two platforms.

This guide consolidates a manual, deterministic conversion workflow that an automation engineer can follow without depending on deprecated utilities. It covers the platform architectural deltas, the hardware migration path from S7-200 to S7-1200/S7-1500, the address and data-type remapping rules, the serial communication re-implementation, and the verification steps required before powering up production hardware.

Platform Architecture: Micro/WIN vs TIA Portal V13

STEP 7 Micro/WIN is a 32-bit Windows programming environment for the SIMATIC S7-200 family. It uses a flat project model: one CPU per project, a single Program Block containing OB1 plus optional subroutines (SBR0..SBR31) and interrupt routines (INT0..INT31), a symbol table, a status chart, a data block, and a cross-reference. TIA Portal V13 is a multi-device, multi-controller engineering framework supporting S7-1200, S7-1500, ET 200, HMI panels, drives, and SCADA stations inside a single project. The program model is hierarchical: each PLC contains an OB folder with organisation blocks (OB1, OB100, OB82, etc.), one or more FB, FC, DB, and UDT objects, plus a project-wide PLC tag table.

The single most consequential difference is the move from V-memory as global scratchpad to a typed DB model. In Micro/WIN you frequently see patterns such as VW100 used as a holding register, integer counter, or string buffer, with no naming or type information. In TIA Portal V13 each storage location should belong to a structured tag, ideally a UDT, so HMI faceplates, motion functions, and cross-references resolve correctly.

Prerequisites

• Source artefact: the original .mwp file exported from Micro/WIN V4.0 SP9 (the final release; build 4.0.9.25 or later). Open the project, export the symbol table as File > Export > Symbol Table (CSV) and the data block as File > Export > Data Block (CSV). These exports become your authoritative tag inventory.
• Target TIA Portal: V13 SP1 or V13 SP2 with the matching firmware support packages installed. The S7-1200 CPU you intend to deploy must be listed in the TIA V13 device catalogue (firmware ≤ V4.x for S7-1200). S7-1500 CPUs with firmware V1.5 or later require TIA V13 SP1 Update 4 or V13 SP2; check the SIMATIC S7-1500 CPU 1511-1 PN compatibility list before committing.
• Hardware selection: an S7-1200 replacement CPU must be picked first, because the tag table, OB structure, and firmware capabilities all depend on the target model. Use the migration table in the next section.
• Documentation: paper or PDF printouts of every Micro/WIN rung, subroutine, and interrupt routine. TIA Portal cannot read the .mwp archive, so the printed or PDF ladder is the working specification.
• Test stand: a controlled environment with the target CPU, the equivalent S7-200 I/O wired or simulated, and the operator panel configured, before cutting over the production line.

Hardware Migration Path: S7-200 to S7-1200 / S7-1500

The S7-200 is end-of-life but still widely deployed. The pin-compatible successor for most applications is the S7-1200, but there are electrical and firmware caveats. Use the following mapping as a starting point.

For S7-1500 migrations use the S7-1500 system manual as the authoritative reference. Memory and OB response times are an order of magnitude better than the S7-200, so scan-time tuning is rarely needed; the focus instead moves to deterministic PROFINET IO update times.

Addressing and Data Type Remapping

Every V, M, I, Q, AI, AQ, T, C, HC, S, and SM reference in the Micro/WIN program must be migrated to a TIA Portal tag. The rules below cover the cases you will encounter most often.

A pragmatic convention is to create one global DB called DataBlockGlobal that absorbs all of the renamed V-memory locations. This gives you a single watch table for commissioning and a single cross-reference for fault-finding, which the S7-200 program never had.

Instruction Set Differences

Most bit-logic instructions translate one-to-one: A (NO contact), AN (NC contact), = (coil), S/R (set/reset). Micro/WIN also offers immediate I/O instructions (e.g. IIL, SI) that bypass the process image update. In TIA Portal the equivalents are :%Ix.0: syntax inside the rung or, more idiomatically, calls to "READ_PI" / "WRITE_PI" system FBs.

Serial Communication Migration (Critical Path)

The serial interface is the single biggest source of conversion failure. S7-200 Freeport on the RS-485 port uses a different byte-handshake model from S7-1200 point-to-point on the CM 1241 (RS-232 / RS-422 / RS-485) or CB 1241 (RS-485) communication modules. If the legacy program uses the USS protocol (drives), Modbus RTU master/slave, or a vendor-specific ASCII protocol, expect to re-author those code paths from scratch.

Freeport to Send_P2P / Receive_P2P

The Micro/WIN XMT and RCV instructions use the SMB30/SMB130 control byte plus an interrupt-driven RCV completion. The S7-1200 equivalent is the "Send_P2P" / "Receive_P2P" FB pair from the PtPCom library (part of the standard TIA V13 installation). Configure the CM 1241 module under Device configuration > Properties > Port configuration for the correct baud rate, parity, and flow control, then call the FB:

// SCL inside OB1, S7-1200 example
// "CM1241_1_DB" is the instance DB generated by the PtP wizard
#instSend(REQ := bSendRequest,
          LADDR := 271,                  // HW identifier of the CM 1241
          PORT := 0,
          DATA := sTxBuffer,             // VARIANT pointing to a DB area
          DONE => bSendDone,
          ERROR => wSendError,
          STATUS => wSendStatus);

#instRcv(EN_R := TRUE,
         LADDR := 271,
         PORT := 0,
         DATA := sRxBuffer,
         LEN := 0,
         DONE => bRcvDone,
         ERROR => wRcvError,
         STATUS => wRcvStatus);

Status word wSendStatus follows the S7-1200 common error code map; for example 16#8001 means the port is busy (another transmission is in progress), 16#80A1 indicates a parameter error in the LADDR assignment, and 16#80B0 signals a parity/framing overrun on the receiver. Cross-check these against the S7-1200 system manual PtP appendix.

USS to USS_Port_Scan / USS_Drive_Control

If the S7-200 program is running drives over USS, swap the wizard-generated USS_INIT and USS_CTRL for the USS_Port_Scan and USS_Drive_Control FBs from the USS library. The drive address mapping (1..32) is identical, but the S7-1200 variant uses symbolic instance DBs instead of the S7-200's global V-memory block at VW1000. Plan to rename every V-memory reference that was reserved by the Micro/WIN USS wizard.

Modbus RTU Master to Modbus_Master_P2P

For Modbus RTU master, use the "Modbus_Master_P2P" FB shipped with TIA V13. It supports function codes 1, 2, 3, 4, 5, 6, 15, and 16 out of the box. The required scan/poll period must be increased from the S7-200 typical 50..200 ms to at least 100 ms on S7-1200 to avoid overloading the serial port when more than eight slaves are present.

Manual Conversion Procedure: Step-by-Step

1. Audit the source. Open the .mwp in Micro/WIN V4.0 SP9. Cross-reference every subroutine and interrupt, then print the entire project to PDF. Note the byte offset of every V-memory reference by sorting the symbol table by address.
2. Inventory the hardware. List every S7-200 model, EM expansion module, and CP (e.g. CP 243-1, CP 243-2 AS-Interface, EM 277 PROFIBUS). Cross-check against the S7-1200/1500 family: not every CP has a 1:1 replacement. For PROFIBUS, the S7-1200 needs a CM 1243-5 master or CM 1242-5 slave module; the EM 277 GSD file is compatible after a firmware re-flash.
3. Select the target CPU. Use Table 2 as the starting point. Confirm program memory: an S7-200 program that fills 16 KB of V-memory typically consumes 30..40 KB of work memory on the S7-1200 once UDTs and FBs are added. Order a CPU with sufficient load memory — typically 1215C for mid-range projects.
4. Build the new project. In TIA Portal V13, create a new project, add the target CPU, configure PROFINET or PROFIBUS devices, and set the IP address. Compile the empty project first; this catches device catalogue errors before you spend hours on logic.
5. Create the global tag table. Import the Micro/WIN symbol export (CSV) into the PLC tag table via Edit > Import/Export. TIA V13 honours the column structure: Name | Path | Data Type | Address | Comment. Re-type all V-memory symbols to use the new DB-prefix convention.
6. Author a global DB to absorb V-memory. For each symbol that previously lived in V-memory, add a typed tag inside a single global DB named, for example, "DB_Migrated". Replace every VWx with "DB_Migrated".tag. Doing this in one pass preserves the program semantics and produces a clean watch table.
7. Translate OB1. Open the printed Micro/WIN OB1 PDF and re-author the rung-by-rung logic inside the TIA Portal OB1. Use the FBD/LAD view, or switch to SCL for blocks that benefit from structured text (string handling, math, loops). Maintain rung comments — they are the only documentation the next engineer will inherit.
8. Convert subroutines to FC / FB. Each Micro/WIN SBR becomes an FC in TIA Portal. Convert any SBR that carried persistent state (e.g. a state machine flag) into an FB with an instance DB, then call it via a multi-instance inside OB1.
9. Re-implement interrupts. Time-driven Micro/WIN INTs become cyclic OBs (OB30..OB38). I/O-driven INTs become hardware-interrupt OBs (OB40..OB47). For PTO pulse-train output, use CTRL_PTO triggered from OB1 or a cyclic OB. For HSC, use the HSC wizard to generate the instance DB and call CTRL_HSC_EXT from OB1.
10. Re-implement serial communication. As detailed in the previous section: XMT/RCV → Send_P2P/Receive_P2P; USS_INIT → USS_Port_Scan; Modbus RTU master → Modbus_Master_P2P.
11. Re-implement PID loops. The Micro/WIN PID wizard writes a self-contained loop into V-memory and an INT routine. In TIA Portal use the PID_Compact (S7-1200) or PID_Basic block, configured from the technology object tree.
12. Compile and download. Use TIA Portal Compile > Software (rebuild all blocks). Resolve any address conflicts (TIA will refuse to compile overlapping tags). Download to the target CPU in STOP mode, then perform a warm restart.

Verification and Commissioning

Manual conversion is only as good as its test coverage. Use the following verification sequence before touching production hardware.

1. Offline simulation. Open the TIA Portal PLCSIM instance of the target CPU. Force every input from the watch table, and step through OB1 with breakpoints. Confirm that the V-memory-to-DB migration produced no off-by-one errors (a classic mistake is forgetting that VW100 and VB101 overlap, while the equivalent INT tag in a DB does not).
2. Online cross-reference. Open Project tree > PLC > Cross-reference in TIA Portal and verify that every Micro/WIN reference has a counterpart. Any address used by Micro/WIN that is no longer used in TIA should be a red flag — it may have been silently lost during translation.
3. Scan-time audit. Monitor OB1 execution time under worst-case load. S7-1200 OB1 typically runs at 1..10 ms; the S7-200 was often 20..50 ms. If the production timing depended on the slow scan, retune any filter or debounce logic.
4. I/O loop-back. With the actual wiring in place, force every output from the watch table and confirm the corresponding physical action. Then read back every input via the watch table and confirm the expected state. Document each verified point on the test sheet.
5. Communication smoke test. Run a Modbus/USS/serial trace on the bench. Compare the raw telegrams byte-for-byte against a capture from the legacy S7-200 with the same payload. Any difference in byte order, CRC, or inter-character timing will produce a fault downstream.
6. Fault injection. Pull the PROFIBUS connector, disconnect a sensor, or short an output. Confirm that the diagnostic OB82 fires and the HMI displays the expected alarm. The S7-200 had only SM bit flags for errors; the S7-1200 has structured diagnostic information accessible via the GET_DIAG system FB.
7. Burn-in. Run the converted program under normal load for at least 24 hours with logging enabled. Use the TIA Portal trace feature to capture OB1 execution time, cyclic OB jitter, and any non-fatal diagnostic events.

Common Pitfalls and Troubleshooting Matrix

Field-Commissioning Checklist

Before the production cut-over, run the following checklist with the responsible engineer signing each line:

• ☐ All Micro/WIN subroutines have a matching FC or FB in the TIA project.
• ☐ All Micro/WIN interrupt routines have a matching OB (cyclic, HW interrupt, or time-of-day).
• ☐ The global tag table contains a typed counterpart for every V-memory reference used by the legacy program.
• ☐ No raw SMB or SMW references remain in the TIA program.
• ☐ Serial communication has been re-verified with a Modbus scanner or USS trace.
• ☐ PTO/PWM outputs have been observed on an oscilloscope, not just the watch table.
• ☐ PID loops have been auto-tuned with the actual process connected.
• ☐ HMI faceplates point at DB tags, not Merker addresses.
• ☐ Diagnostic OBs (OB82, OB85, OB121, OB122) contain a logging call so future faults are visible.
• ☐ The project backup (.ap13) has been archived to the engineering vault with a dated revision tag.

FAQ