SIMATIC Manager: S7-300/400 Engineering Tool and S7-200 Compatibility Reference

Overview

SIMATIC Manager is the central engineering container shipped with STEP 7 V5.x (now superseded by STEP 7 inside the TIA Portal). It coordinates the configuration, programming, commissioning, and diagnostic utilities required to work with the SIMATIC S7-300, S7-400, C7, and WinAC automation systems. SIMATIC Manager is not the engineering tool for the S7-200 micro-PLC family; attempting to use SIMATIC Manager to upload, download, or program an S7-200 CPU will fail because the S7-200 family uses a different firmware architecture, communication protocol stack (PPI/MPI on the older series, Ethernet on the S7-200 SMART), and a different project database format.

This reference clarifies the scope of SIMATIC Manager, the correct software tools for the S7-200 family, and the migration paths that exist for engineers maintaining legacy installations.

Supported PLC Families and Hardware Scope

SIMATIC Manager is built on the STEP 7 V5.x project framework and supports the following automation systems:

SIMATIC Manager Architecture and Components

SIMATIC Manager is a Microsoft Windows-based shell that integrates several sub-tools, each launched as a child window of the project tree:

The container model means a single *.s7p file holds the entire station, including hardware configuration, symbol tables, source files, compiled blocks, and connection data. The compiled *.s7s system data block is downloaded to the CPU along with the logic blocks (*.s7b).

Why SIMATIC Manager Cannot Program the S7-200

The S7-200 family was developed as a low-cost micro-PLC with a deliberately different firmware and toolchain from the S7-300/400 families. The technical reasons for incompatibility are:

1. Different CPU firmware and instruction set. The S7-200 uses a SIMATIC micro-CPU with a streamlined accumulator-based instruction set, not the S7-300/400 register-based architecture. S7-300 STL mnemonics (e.g., U / O / = for AND/OR/Assign) are not valid in the S7-200.
2. Different memory model. The S7-200 uses variable areas V (data), I (input), Q (output), M (internal), SM (special memory), T/C (timer/counter), and AI/AQ (analog). STEP 7 V5.x expects the I/Q/M/DB memory model of the S7-300/400.
3. Different communication protocol. Legacy S7-200 CPUs use the PPI (Point-to-Point Interface) protocol at 9.6 kbit/s or 19.2 kbit/s over RS-485. STEP 7 V5.x uses MPI/PROFIBUS/Ethernet via the PC adapter (PC Adapter USB, CP 5611, CP 5612, CP 5711) and does not speak PPI on RS-485 by default.
4. Different project format. S7-200 projects are stored as *.mwp (Micro/WIN project) or *.smart (Micro/WIN SMART) and compiled to a binary that the S7-200 firmware loads into its internal flash. The S7-300/400 compiled *.s7b block container is not understood by the S7-200 firmware.
5. No hardware catalog entry. HW Config in SIMATIC Manager has no catalog entries for the S7-200 CPU or its EM221/EM222/EM223/EM231/EM232/EM235 expansion modules.

The Correct Tool for the S7-200: STEP 7 Micro/WIN

For the original S7-200 family (CPU 221 through CPU 226), Siemens provides STEP 7 Micro/WIN as the dedicated engineering tool. The supported versions and key parameters are:

Programming is performed in either Ladder (LAD) or Function Block Diagram (FBD) by default; Statement List (STL) is selectable for users familiar with the accumulator-style mnemonics. Micro/WIN also provides a "Wizard" library for common functions including PID, High-Speed Counters, USS protocol (for MICROMASTER drives), and Modbus RTU Master/Slave.

Micro/WIN Communication Setup for S7-200

1. Connect the PC to the S7-200 PPI port using either the USB/PPI Multi-Master cable (6ES7 901-3DB30-0XA0) or the legacy PC/PPI cable (6ES7 901-3BF20-0XA0 for RS-232).
2. In Micro/WIN, open the "Set PG/PC Interface" dialog (menu: View → Component → Set PG/PC Interface) and select PC/PPI cable (PPI).
3. Set the PPI transmission rate to 9.6 kbit/s for the default CPU address 2 (CPU 221/222/224) or 19.2 kbit/s for CPU 224XP/226 if the address was changed.
4. Click "Communications" in the navigation tree, then double-click the "Double-Click to Refresh" icon. The CPU should appear in the detected stations list.
5. Use "Upload" to retrieve the project from the CPU, or "Download" to push the current offline project to the CPU.

STEP 7 Micro/WIN SMART for the S7-200 SMART Family

Siemens introduced the S7-200 SMART CPU series (SR20, ST40, ST60, CR40, CR60, SR60) in 2012 to replace the original S7-200. The S7-200 SMART uses an Ethernet port as the primary programming interface and is not supported by the original Micro/WIN V4.0.

Micro/WIN SMART is a free download from Siemens Industry Online Support and includes PID wizards, motion control for PTO (Pulse Train Output) and PWM, USS and Modbus RTU libraries, and a project comparison tool. It does not import legacy S7-200 *.mwp files; projects must be re-entered or use the S7-200 SMART conversion tool provided in the Micro/WIN SMART install directory.

Communication Hardware Reference

The cables and adapters required to communicate with each Siemens S7 family are completely different. The following table clarifies the cabling ecosystem for engineers transitioning between PLC families:

STEP 7 V5.x Version History and Lifecycle

SIMATIC Manager has a long product lifecycle that engineers maintaining legacy S7-300/400 systems must understand:

The final SIMATIC Manager distribution is STEP 7 V5.5 SP4 (build 5.5.4.0 or higher). It runs on Windows XP SP3, Windows 7 (32/64-bit), Windows Server 2003/2008/2008 R2, and—via compatibility mode—Windows 10. There is no 64-bit native version of SIMATIC Manager. The successor is STEP 7 inside the TIA Portal, which is a 32/64-bit application but cannot open *.s7p projects directly; they must first be migrated with the TIA Portal's "Migrate project" wizard, which converts V5.x projects into TIA Portal *.ap16 (or later *.ap20) archives.

Migration Paths: From S7-200 to Modern Siemens Platforms

Engineers maintaining S7-200 installations that are approaching end-of-life should consider the following migration targets:

Option 1: S7-200 SMART (drop-in modern replacement)

The S7-200 SMART CPU series shares the same program structure and most of the Micro/WIN instruction set, but the project must be manually re-entered. The wiring footprint and terminal pin-out are similar to the S7-200 CPU 224/224XP, so re-panelling is minimal. Pros: low cost, Micro/WIN SMART is free. Cons: project must be rewritten; S7-200 SMART end-of-life announcement has not been published but the product line is mature.

Option 2: S7-1200 (recommended new design)

The S7-1200 is the modern replacement for both the S7-200 and the S7-300 in new applications. It is programmed in TIA Portal V15 or later. Siemens provides a S7-200 to S7-1200 migration tool (built into TIA Portal under "Tools → Migrate S7-200 project") that:

• Imports the *.mwp file and parses the program structure (OB1, subroutines SBR_n, interrupt routines INT_n, data blocks DB_n).
• Maps the V-memory area to the S7-1200 DB structure.
• Translates most LAD/FBD instructions; a small set of S7-200-specific instructions (e.g., HSC, PTO/PWM, NETR/NETW, PID table) require manual rework in TIA Portal.
• Flags bit-memory, timer, and counter addresses that conflict with the S7-1200 I/O image so the engineer can remap them.

Option 3: S7-1500 (high-end new design)

For new installations requiring maximum performance, motion, or safety, the S7-1500 is the recommended platform. The same migration tool workflow applies, but the S7-1500 has additional instructions, structured data types, and optimized block access that may require further code optimization beyond a straight conversion.

Side-by-Side: SIMATIC Manager vs TIA Portal

Troubleshooting Common SIMATIC Manager / S7-200 Confusion Issues

Field Commissioning Notes for SIMATIC Manager

1. CPU firmware vs STEP 7 version: Always verify that the S7-300/400 CPU's firmware version is on the Siemens compatibility list for the STEP 7 version installed. Newer firmware on an S7-300/400 CPU may require a STEP 7 update to add the GSD/GSDML files for newer IM modules.
2. PG/PC Interface selection: After installing SIMATIC Manager, open Start → SIMATIC → SIMATIC Manager → Set PG-PC Interface and select the correct access point (e.g., S7ONLINE for Ethernet or PC Adapter (MPI) for USB A2). An incorrect access point selection is the most common cause of "Cannot find partner" errors during upload/download.
3. Online/Offline consistency: Before any download, perform an Online → Compare on the station to identify drift between the offline project and the CPU. The diagnostic buffer (online) will record each download with timestamp; ensure the offline project matches the latest timestamp before performing a programming change.
4. Password protection: S7-300/400 CPUs support a CPU password (configurable in HW Config → CPU Properties → Protection). The default is "no protection" so a forgot password requires a memory reset (MRES), which wipes the program. For S7-200, the equivalent is a factory reset via the SYSTEM block "Reset to factory defaults" option.
5. Archive format: Use the File → Archive function to package the entire *.s7p project (with sources, comments, and HW Config) into a single *.zip file. This is the only portable format; *.s7p files are often locked to a specific STEP 7 minor version and cannot be opened in older releases without a downgrade archive.

Standards Compliance

SIMATIC Manager and Micro/WIN both produce programs that comply with IEC 61131-3 where applicable. The S7-300/400 supports all five IEC 61131-3 languages (IL, ST, LD, FBD, SFC), although the legacy IL implementation is only partially compliant. The S7-200 supports LD, FBD, and a subset of IL, with the proprietary "Micro/WIN" instruction extensions for HSC, PTO, NETR/NETW, and PID. Always validate SIL-rated applications against the relevant IEC 61508 / IEC 62061 safety data sheet from Siemens before commissioning.