Opening Siemens SIMOTION Scout Projects with Step7 V5.6 OEM

Problem Context

Engineers maintaining long-lived Siemens automation systems frequently inherit project files — typically Step 7 V5.x archives (.s7p, .zip, or unzipped directory trees containing Globals, Sources, s7asyscomp, and Stations) — without the original installation media, project history, or design documentation. When the bundle contains motion control logic, drive commissioning data, SINAMICS or MICROMASTER parameter sets, and an integrated HMI panel screen set, the working engineer must determine which legacy Siemens tool actually owns the file. The candidate set is short but the boundaries are sharp:

• SIMATIC Manager (Step 7 V5.6) — owns generic S7-300, S7-400, and ET200 PLC logic, plus WinCC flexible HMI station stubs.
• SIMOTION SCOUT — owns motion control projects built on the SIMOTION platform (D4xx, P3xx, C2xx controllers) with integrated drives.
• STARTER — owns standalone drive commissioning projects (SINAMICS S/G, MICROMASTER 4, SIMOVERT) without an S7 PLC in the same archive.
• WinCC flexible — owns operator panel screen databases that may be standalone or referenced from a Step 7 station.

Opening the project with the wrong tool produces a predictable cascade of symptoms: setup aborts with "Unknown software package" during the Step 7 package check, SIMATIC Manager shows empty project nodes with a yellow exclamation mark on the component view, SIMOTION SCOUT setup refuses to install because the underlying Step 7 build is a restricted OEM edition (for example, V5.6+HF1 OEM2), or WinCC flexible loads the panel but cannot resolve cross-references to PLC tags. Each condition is recoverable once the engineer confirms which authoring tool generated the archive.

Identifying the Project Type

Before installing any tool, inspect the unzipped project for signature files. The table below maps directory and file markers to the owning tool. Use dir /s /b on Windows or find . -maxdepth 3 -type d in WSL to enumerate the structure.

If a SETUP.LOG or SETUP.TXT exists in the project root, open it in Notepad. The first 20 lines typically list the originating package, for example Step7 V5.6+HF1 OEM2 or SIMOTION SCOUT V5.2 SP1. This is the fastest way to confirm the owning tool when the directory structure is ambiguous.

Step 7 V5.6 OEM vs Full Installation

Siemens ships two distinct Step 7 V5.6 distributions: a full version that includes the entire engineering chain (S7-300/400 hardware catalog, all option packages, NetPro, SCL, GRAPH, S7-PLCSIM, and the import interface for SIMOTION SCOUT) and an OEM version that is repackaged by drive or controller vendors (Siemens Drive ES, SINUMERIK, SIMOTION bundles) for a single purpose. The OEM build is installed silently alongside STARTER or SCOUT and exposes only a subset of the toolchain.

SIMOTION SCOUT Installation Requirements

SIMOTION SCOUT V5.2 SP1 is a stand-alone engineering environment that embeds a full Step 7 V5.6. When the SCOUT setup launches it performs the following checks in order:

1. OS edition (Windows 7 SP1, Windows 10 LTSB/LTSC, Windows Server 2008/2012/2016).
2. Microsoft .NET Framework 2.0 / 3.5 / 4.x presence.
3. Microsoft Message Queuing (MSMQ) service installed and started.
4. Step 7 V5.6 with hotfix at the required patch level (HF1 or later for SCOUT V5.2 SP1).
5. WinCC flexible 2008 SP2 or later if the project references HMI stations.
6. A license key (single station or floating) for the SCOUT option.

Each check produces either a hard abort (red dialog, setup exits) or a soft warning. The classic hard-abort dialog that appears as soon as the SCOUT setup reaches the prerequisite scan is: "The installed Step 7 version is an OEM build. SCOUT cannot continue. Please install a full Step 7 V5.6."

The minimum host configuration that reliably accepts SCOUT V5.2 SP1 is:

• Windows 7 SP1 (x64) or Windows 10 LTSC 2019 — UAC set to lowest level during installation only.
• Step 7 V5.6 + SP1 + HF1 (or HF3 for newer SCOUT revisions).
• WinCC flexible 2008 SP5 for HMI integration.
• 3 GB free disk for the offline project cache; 8 GB RAM minimum.

STARTER Version Conflicts

STARTER (Siemens drivE Tool) is the commissioning tool for SINAMICS and MICROMASTER drive platforms. The version that ships with an OEM Step 7 install is locked to that OEM bundle. For example, the STARTER V5.3.0.1 included with Step 7 V5.6+HF1 OEM2 cannot be uninstalled without first uninstalling the OEM Step 7. The conflict manifests as:

• Windows Installer refuses to remove STARTER because the OEM Step 7 depends on it (error 1714 or error 1605).
• Attempting to install a newer STARTER returns "A more recent version of STEP 7 is required."
• Installing SIMOTION SCOUT after STARTER aborts because SCOUT setup detects STARTER installed and refuses to co-exist (see coexistence section below).

Resolution sequence when both SCOUT and a current STARTER are required:

1. Capture all drive parameter files (*.dn, *.par, *.dpx) from the project tree.
2. Uninstall OEM Step 7, which automatically removes the bundled STARTER.
3. Install full Step 7 V5.6 + SP1 + HF1 with license.
4. Install SIMOTION SCOUT V5.2 SP1 or later (re-bundles a compatible STARTER internally if HMI/Lib is needed).
5. If a non-bundled STARTER is required for offline drive commissioning on a separate PC, install it on a second host — SCOUT and standalone STARTER cannot share a host.

WinCC Flexible HMI Integration

If the inherited project archive contains an HMI subfolder with *.hmi, *.ldf, *.tag, and *.fwd files, the operator panel is built with WinCC flexible 2008 (the maintenance release for OP/TP/MP 177-377 panels and the PC Runtime). WinCC flexible is installed as a separate option on top of Step 7 V5.6 and integrates the HMI station into the SIMATIC Manager project tree.

Common diagnostic states when WinCC flexible is the wrong version:

Coexistence Rules on a Single Host

Siemens officially documents the following coexistence rules for the legacy toolchain on a single Windows host. Violating any rule produces a setup abort, a missing reference dialog, or a runtime crash the first time the project is opened.

Step-by-Step Resolution Procedure

Use this procedure when an archive arrives without tool context. The steps assume Windows 7 SP1 x64, administrative account, and a single-host install.

Prerequisites

• Source installation media or licensed download for Step 7 V5.6 + SP1 + HF1 (or HF3 for newer SCOUT), SIMOTION SCOUT V5.2 SP1, WinCC flexible 2008 SP5, and language packs for the project locale.
• License keys (single station, USB dongle, or floating license server) for each tool that requires one.
• 8 GB RAM, 30 GB free disk, MSMQ enabled (appwiz.cpl → Turn Windows features on or off → Microsoft Message Queueing Server).
• Backup of any pre-existing project on the host.

Procedure

1. Inspect the archive. Use the table in Identifying the Project Type to determine the owning tool. Note the language of comments and HMI labels — the Windows host must have the matching Windows UI language or the Siemens language pack.
2. Open SETUP.LOG if present. Confirm the originating tool build (for example Step7 V5.6+HF1 OEM2 or SIMOTION SCOUT V5.2 SP1).
3. Uninstall any pre-existing OEM Step 7 plus the bundled STARTER through appwiz.cpl. Reboot.
4. Install full Step 7 V5.6 from the Siemens DVD or licensed electronic download. Apply SP1 and HF1. Reboot.
5. Set the PG/PC interface: open the SIMATIC Manager workstation, choose Options > Set PG/PC Interface, and select TCP/IP <-> ISO (or the project-specific PROFIBUS adapter if applicable).
6. Install WinCC flexible 2008 SP5 with the locale packs matching the project. Reboot.
7. Install SIMOTION SCOUT V5.2 SP1. Watch for the prerequisite scan: if it reports an OEM Step 7 still present, return to step 3.
8. Open SIMATIC Manager, choose File > Open > Project, navigate to the unzipped archive or the .s7p file. SIMATIC Manager compiles and re-binds the package list.
9. Open the project in SCOUT if the archive is a motion project. From SCOUT, choose Project > Open and pick the *.sin file in the SIMOTION subfolder.
10. If WinCC flexible is referenced, open the HMI station in WinCC flexible via Start > Programs > Siemens > SIMATIC > WinCC flexible 2008. The HMI station appears as a child node under the SIMATIC Manager project.

Verification Checklist

After the install sequence, perform these checks before declaring the project operational:

1. SIMATIC Manager opens the project without yellow exclamation marks on any station. Re-run PLC > Compile and Download Objects and confirm 0 errors, 0 warnings in the output window.
2. The Step 7 version is reported as V5.6 SP1 HF1 (or later) in Help > About — not an OEM build.
3. STARTER version is the SCOUT-bundled build (e.g. V5.3.0.1) and matches the drive firmware in the project.
4. WinCC flexible compiles the HMI project; the tag interface shows resolved symbols from the PLC (no red "?" markers).
5. MSMQ service is running (sc query msmq returns STATE: 4 RUNNING).
6. PG/PC interface is set to the adapter the controller is wired to; test with Accessible Nodes from SIMATIC Manager.
7. License keys are recognized: Start > Programs > Siemens > Automation License Manager shows every required module in green.
8. A dry-run download to PLCSIM (if licensed) succeeds — this is the highest-fidelity verification short of live commissioning.

Diagnostic Decision Tree

Use the following flowchart when the project still refuses to open after a clean install.

Windows and Windows Language Pack Considerations

Step 7 V5.x and SIMOTION SCOUT are partially localized; the dialogs and message texts ship in English, German, French, Italian, Spanish, and (for some service packs) Chinese Simplified. When the project archive contains localized comments or HMI labels in a locale that is not installed, the Siemens tools display the message "A language pack is required to display the project text." Add the language pack at the Windows level (Settings → Time & Language → Language → Add a Windows display language) and ensure the Siemens setup was performed with the matching language selected during the Custom Installation dialog. The host must then reboot twice — once for the language pack and once for the Siemens tools to re-bind their resource DLLs.

Archive Re-encoding Best Practices

When the project arrives inside a .zip, .arj, or older self-extracting .exe, preserve the original archive bit-for-bit and unpack with the original tool. Avoid Windows built-in ZIP handling on pre-Vista archives — it can normalize path separators and corrupt the \ characters in *.s7p references. Recommended unpacking toolset:

• 7-Zip 22.x or later for .zip and .arj.
• WinRAR 6.x for .rar and self-extracting installers.
• The original self-extracting .exe (right-click → Run as administrator) when present.

License and Support Considerations

Step 7 V5.6 and SCOUT are in the legacy maintenance phase. New licenses are still issued by Siemens DI, but software updates are limited to security and stability patches. Confirm the entitlement via the Siemens Industry Online Support portal and download the cumulative hotfix image if available. The Automation License Manager (almsrv.exe) reads license keys from a USB dongle, a local file (%ProgramData%\Siemens\Automation\LicenseKey\), or a floating license server. Always reinstall the license after applying a service pack, since the hotfix can shift the license fingerprint.

Migrating to TIA Portal

If a long-term migration to TIA Portal is planned, plan the path carefully:

1. Step 7 V5.6 → TIA Portal V15 or later via the Step 7 migration tool. SIMATIC Manager is the source; Project > Migrate to TIA Portal is the entry point.
2. WinCC flexible 2008 → WinCC Comfort/Advanced in TIA Portal. The migration tool is bundled in TIA Portal; tag names and screen layouts are preserved.
3. SIMOTION SCOUT → no direct TIA Portal migration. SIMOTION projects remain on the legacy toolchain. Use TIA Portal for S7 controllers and SCOUT for motion.

Do not attempt to migrate a project that originates on OEM Step 7. Migrate first from the OEM bundle to full Step 7, then to TIA Portal.

Field-Validated Summary

Following the procedure above resolves the three classic failure modes reported when opening inherited Siemens archives: "unknown software package" errors from missing hotfixes, SCOUT setup aborts on OEM Step 7, and WinCC flexible refusing to load when the wrong language pack is installed. Each mode is independent, but the diagnostic order — identify the owning tool first, confirm the Step 7 edition second, then resolve coexistence — catches all three before commissioning time.