Resolving TIA Portal V19 Migration Scout Dependency Errors

Problem Overview

Migrating a TIA Portal project from V15.1 to V19 triggers a mandatory requirement for the SCOUT TIA optional software package, even when the project contains no SIMOTION devices, axes, or technology objects. The project originally used the PLC + Safety + Startdrive + Scout combination, but the SIMOTION hardware was removed long before the upgrade attempt. The Siemens migration wizard still binds SCOUT to the archive, and the user is blocked from opening the migrated V19 project until SCOUT for V19 is installed (released April 2024 per the original report timeline).

This is a well-documented behavior in the TIA Portal architecture: once an optional package writes metadata, device proxies, or technology object types into the project XML, removing the runtime license from the host PC does not strip those entries from the project file. The Siemens TIA Portal documentation on optional software confirms that projects retain optional-package metadata even when devices of that type are absent, and that opening such projects requires the original optional software to be installed.

Root Cause Analysis

TIA Portal stores optional-package fingerprints in the project archive (.ap15_1 / .ap19) as well as the project tree XML. When SCOUT TIA is installed and a device is added, removed, or merely browsed, the following entries are written:

• Technology object type libraries (e.g., TO_SpeedAxis, TO_SynchronousAxis)
• SIMOTION device proxies in the device catalog cache
• Package version stamps in SystemData\PackageInfo
• Implicit references in PLC data types (UDTs) and watch tables

When migrating upward, the TIA Portal compatibility check scans for all referenced package fingerprints. Even a single residual reference forces the migration to demand the matching optional package on the destination system. The behavior is similar to the V16 support package mismatch described in the TIA Portal V16 HSP install error article, where version metadata embedded in the project overrides the local installation state.

Solution 1: Rebuild the V15.1 Project Without SCOUT Metadata

This is the field-proven workaround documented in the original forum thread. It eliminates SCOUT references at the source, producing a clean V15.1 archive that migrates cleanly to V19.

1. Install TIA Portal V15.1 on a clean or secondary workstation (SCOUT must NOT be installed this time).
2. Open the original V15.1 project; export the complete hardware configuration to PDF (device list, module order, slot assignments, IP/profinet names, safety address parameters, Startdrive drive parameters).
3. Export all PLC program blocks (OBs/FBs/FCs/DBs) as individual source files using "Copy as text" or generate STL/SCL sources.
4. Export PLC tags, user constants, UDTs, and watch/force tables to XML or text files.
5. Create a new V15.1 project. Rebuild the hardware configuration to match the original — pay particular attention to non-default values in module properties, safety signatures, and drive parameter sets.
6. Drag-and-drop the exported blocks, tags, UDTs, and tables into the new project tree.
7. Rebuild hardware (compile), then rebuild software (compile all). Resolve any residual references to SIMOTION type libraries.
8. Archive the clean V15.1 project. Run the V19 migration on this archive — the SCOUT dependency should no longer be raised.

Solution 2: Submit a Support Request to Siemens

Siemens Technical Support has access to internal project-cleanup utilities that are not shipped in the standard TIA Portal distribution. Steps:

1. Open a Support Request (SR) at Siemens Industry Online Support.
2. Attach the original V15.1 archive (zip the .ap15_1 file).
3. Request "optional package metadata removal" or "Scout fingerprint strip" so the project can be opened in a TIA Portal installation without SCOUT.
4. Siemens returns a cleaned archive that can be migrated to V19 directly.

Solution 3: Third-Party Package Verification

Per the PLCTalk discussion on optional package migration, third-party GSD-based packages can also trigger similar prompts. Confirm that the following are not the actual culprit before chasing SCOUT:

Verification Steps

After applying Solution 1 or 2, confirm a clean migration:

1. Open the V19 migrated project on a workstation without SCOUT installed.
2. Right-click the project tree → "Properties" → confirm no warning icon on the project node.
3. Compile hardware — expected result: 0 errors, 0 warnings referencing SIMOTION.
4. Compile software — verify no unresolved type references in the cross-reference list.
5. Perform a "Project consistency check" under the "Options" menu.
6. Download to the target S7-1500/ET200SP hardware (or run PLCSIM V19 simulation) to confirm runtime behavior matches V15.1.

Preventive Best Practices

• Maintain separate master templates for each project family (PLC-only, PLC+Safety, PLC+Drives, PLC+SIMOTION) to avoid cross-contamination of optional packages.
• Avoid opening a project on a workstation that has optional packages installed unless those packages are intentionally part of the project scope.
• Archive projects with a README.txt listing every optional package required to open the archive.
• Before upgrading, run a consistency check on the source version to surface latent package dependencies.
• For hardware support packages (HSPs) used by distributed I/O, follow the installation procedure in the Siemens HSP installation video only on workstations that own the corresponding project scope.

FAQ