Resolving Missing Drive_ES and SIMATIC PDM Packages in STEP 7

Problem Overview

When opening legacy STEP 7 V5.5 or V5.6 projects after a fresh Engineering Station (ES) rebuild, the SIMATIC Manager and HW Config raise the dialog "Missing Software Packages" referencing one or both of the following optional integration packages:

• Drive_ES (SIMATIC Drive Engineering System) – object integration for Siemens master drives (SIMOVERT, MASTERDRIVES, SINAMICS, SIMOREG) inside STEP 7 HW Config.
• SIMATIC PDM (Process Device Manager) – device integration for Profibus-PA, FOUNDATION Fieldbus, and HART field instruments.

The signature characteristic of this symptom is that the affected objects appear yellow, not red, in HW Config and NetPro. Yellow indicates an informational/optional integration package; red indicates a hard dependency (for example, a missing HW Update or unsupported GSD file). The project still opens, compiles, and downloads; however, parameter objects belonging to the missing package render as placeholders and any object that required Drive_ES/PDM-specific dialogs (drive parameter lists, device calibration forms) cannot be edited end-to-end.

Why the Warning Appears

STEP 7 V5.x stores each optional sub-package as a registered package object in the Windows registry under HKLM\SOFTWARE\Siemens\Automation\InstalledSoftware\STEP7 (older installations may use HKLM\SOFTWARE\Wow6432Node\Siemens\...). Each component—Drive ES, SIMATIC PDM, S7-PLCSIM, S7-GRAPH, S7-SCL, CFC, SFC—registers a unique package GUID and an associated version string in HW Config's Object Properties > Additional Information.

When HW Config enumerates stations, it compares every object GUID/version pair against the local registry. An object whose GUID is not registered produces the "missing package" entry. The colour of the warning follows this logic:

Identifying the Required Packages

Before installing anything, capture a controlled inventory of what the project actually uses. Drive_ES and SIMATIC PDM are licensed, off-SIOS software; you should only procure what the project's hardware configuration demands.

Step 1 — Generate the "Installed SIMATIC Software" List

Open Start > SIMATIC > Installed SIMATIC Software (or run SiemensInst.exe from the STEP 7 DVD). Capture a screenshot of the dialog. Compare the listed components with the project's missing-package list. The screenshot is also a useful attachment when escalating to Siemens Support (SR – Support Request).

Step 2 — Inspect HW Config for Drive Objects

Open the affected project in SIMATIC Manager, then double-click Hardware in the station. In the catalog tree on the right, expand the station. Drive objects appear under:

• PROFIBUS-DP > SIMOVERT
• PROFIBUS-DP > SIMOREG
• PROFIBUS-DP > MASTERDRIVES
• PROFINET IO > SINAMICS
• PROFINET IO > SIMOTION (partial)

Any object whose icon displays the yellow triangle and whose tooltip reads "Object type requires Drive ES" indicates Drive_ES dependency.

Step 3 — Inspect HW Config for Process Device Networks

Process-device networks always hang off an existing DP master or HART module:

• Profibus-PA: A DP/PA coupler or DP/PA link (e.g. 6GK1 415-2BA10, 6GK1 416-2BS00) appears in the DP line. PA slaves then attach below it.
• FOUNDATION Fieldbus: An FF link (e.g. 6GK1 516-3AA00, 6GK1 516-3BA00) sits on the DP line. The link's downstream fieldbus carries FF devices.
• HART: Either an ET200iSP station with HART modules, an analog input/output module configured for HART (e.g. 6ES7 331-7TF01-0AB0), or an SM HART card in a remote rack. HART devices show up under HART > ... in the catalog.

If none of the above are present in any of your stations, the project does not need SIMATIC PDM and the warning can be safely ignored (after suppressing it).

SIMATIC Drive ES — Technical Background

Drive ES is the integration layer that lets STEP 7 HW Config understand Siemens drive firmware objects, expose drive parameter lists, and synchronise parameter changes between the PLC project and the drive. Without it, drives appear as generic DP slaves and parameter screenshots (e.g. SLS, V/f curves, encoder configurations) cannot be edited inside STEP 7. Commissioning must then be done from STARTER or the AOP (Advanced Operator Panel).

Drive ES Variants

Drive ES Compatibility Matrix (STEP 7 V5.x)

To install, run SETUP.EXE from the Drive ES DVD. The setup registers the package GUID, installs the catalog GSD additions, and prompts for the license transfer (parallel or USB dongle). A restart of SIMATIC Manager is required.

SIMATIC PDM — Technical Background

SIMATIC PDM is the device-type manager (DTM) host for field instruments. It loads Electronic Device Descriptions (EDD) and Field Device Tool (FDT) DTMs, and exposes them inside STEP 7 via the Open Object > SIMATIC PDM command or directly from the HW Config right-click menu.

SIMATIC PDM Variants Relevant to STEP 7 V5.x

Delivery note for PDM v9.1: SIOS entry 109748101. The note lists supported operating systems (Windows 7 SP1 / Server 2008 R2 / Windows 10 1607+),.NET prerequisites, and the bundled device library.

PDM Installation Order

1. Install STEP 7 V5.5 or V5.6 first.
2. Install any Service Packs (SP) for STEP 7.
3. Install the corresponding HW Update (HWA) from the DVD or SIOS — this adds the DP/PA coupler and FF link catalog entries.
4. Insert the SIMATIC PDM DVD and run Setup.exe.
5. Restart the system.
6. Transfer the license via Automation License Manager (ALM).
7. Verify with Start > SIMATIC > Installed SIMATIC Software.

Suppressing the Warning Without Installing the Packages

If your analysis confirms that the project does not use any objects that require Drive_ES or PDM (for example, an archived project retained as reference only), you can suppress the warning dialog:

1. Close HW Config and SIMATIC Manager.
2. Open the registry editor (regedit).
3. Navigate to HKCU\Software\Siemens\STEP7\HWConfig\Warnings.
4. Create or set the DWORD SuppressMissingPackageDialog to 1.
5. Re-open the project. The yellow triangles remain visible in the station, but the popup no longer fires.

Procedural Workflow — Field-Engineer Checklist

1. Capture the baseline. Screenshot the Installed SIMATIC Software dialog and the Missing Software Packages warning. Tag with project name, ES hostname, and date.
2. Audit the hardware. In HW Config, use Ctrl+A in the station window and read the tooltip of any yellow object. Record the catalogue path and firmware version.
3. Categorise. Sort the yellow objects into two lists: Drive objects (need Drive_ES) and Process devices (need PDM).
4. Confirm licence entitlement. Verify the licence exists in ALM or on media. If absent, escalate to procurement. Both packages are commercial.
5. Install in the correct order: STEP 7 → SP → HW Update → Drive ES / PDM → restart → ALM transfer.
6. Validate. Reopen the project. Yellow triangles should disappear. Parameter objects should open with the device-specific dialog.
7. Archive. Save the project, then perform a Save As with Reorganisation to consolidate any orphaned package references.

Verification Procedure

After installing the missing packages, run the following checks to confirm the warning is gone and the project is fully functional:

1. Open the project in SIMATIC Manager; the Missing Software Packages dialog must no longer appear.
2. Open HW Config; every object must render with a normal icon.
3. Double-click a previously yellow drive object. The Object Properties dialog must open and the Parameters tab must be populated.
4. Right-click a Profibus-PA or HART device. The context menu must contain Open with SIMATIC PDM.
5. Launch SIMATIC Manager > Options > PG/PC Interface and confirm the new packages are listed under Installed Software.
6. Perform a Check Consistency on the S7 program (Ctrl+Alt+F) and confirm no warnings about unsupported object types.

Troubleshooting Matrix

Working Without Drive_ES and PDM

You can still open, edit, and save the S7 and WinCC parts of a STEP 7 project when these optional packages are absent. What you cannot do:

• Edit drive parameter lists from inside STEP 7 (use STARTER instead).
• Open PDM device objects with the full calibration/parameter view (use standalone PDM, but cross-project changes will not synchronise).
• Re-save drive or instrument objects with new firmware versions.
• Use the Export Drive Parameters function.

Saving the project with File > Save retains the placeholder objects intact. The yellow state does not corrupt the program logic, the SFC/SFB calls, or the WinCC graphics. Round-trip with a fully equipped ES will restore full editability.

Migration Path to TIA Portal

If your facility is moving to TIA Portal, the legacy Drive_ES and PDM packages are replaced by:

• Drive ES TIA (6SW1700-8JC00-0AA0) for SINAMICS Startdrive integration.
• SIMATIC PDM — same product, integrated into the TIA Portal device view (PDM V9.0+ supports TIA Portal V15.1+).

Migrate projects using TIA Portal > Migration > Migrate STEP 7 V5.x project. Drive and PDM objects are translated to TIA Portal equivalents when the matching TIA packages are installed.

FAQ