Resolving MICROMASTER 440 PROFIBUS DP Errors on PCS7 DriveES

Problem Overview

Engineers integrating a Siemens MICROMASTER 440 (MM440) inverter into a PROFIBUS DP segment controlled by a SIMATIC PCS 7 station frequently encounter two related symptoms after hardware configuration and CFC compilation:

1. A red triangular warning on the MM4 station symbol in HW Config (NetPro / SIMATIC Manager), even though the node is visible on the bus.
2. A CFC/SFC compilation error pointing at the FB628 DES_DIAG (DRIVER WIZARD) block, with cascading warnings on SIMO_MM4, SIMO_MA, or other DRVPCS7 APL-style drive blocks.

Both symptoms trace back to the same root cause family: a DRIVE ES PCS 7 library version that does not match the PCS 7 engineering base, or a library that was archived from another computer and re-inserted (retrieved) without the original product-DVD installation on the engineering station. This document covers the diagnostic path, the affected product versions, and the field-proven resolution procedure.

Affected Products and Versions

The following Siemens catalog items are part of the affected stack. Verify versions in Start » Siemens Automation » Installed Software on the engineering station before changing anything.

Root Cause: Why the Red Triangle Appears

The yellow/red corner triangle in HW Config is a diagnostic overlay generated by PCS 7 (not by Step 7 classic) when both of the following are true:

1. A Drive ES-style GSD for the MM4 is registered in the HW Catalog (typically imported by Drive ES or by DriveMonitor). This is a non-stock GSD with a Siemens-DriveEs vendor ID and additional diagnostic telegram types (PKW + PZD extended).
2. A drive object (e.g., SIMO_MM4 instance) is present and connected in the S7/PCS 7 program. The HW Config cross-checker detects that the configured channel width and the program block refer to the same DP slave.

When the triangle appears, HW Config is telling you: “this station is configured in the program, but the channel mapping is owned by a Drive Es object.” The drive is still online and exchanging PZD; the marker is informational, not a fault. However, when combined with the FB628 compilation error described below, the marker becomes a symptom of a deeper library mismatch.

Root Cause: Why FB628 DES_DIAG Fails to Compile

The DRVPCS7 library contains a coordinated set of:

• Function blocks (FBs) such as SIMO_MM4, SIMO_MA, SIMO_SC, DES_DIAG (FB628), DRIVER_WIZARD;
• User-Defined Types (UDTs) used as block interfaces;
• Data types for diagnostics, parameter channel (PKW), and process data (PZD);
• Symbolic Constants for the DRVPCS7 family.

When the engineer archives the library from another computer and retrieves it into the target project, the following can occur:

• The UDT and FB interface versions retrieved do not match the local Step 7 / PCS 7 install.
• FB628 DES_DIAG requires a DRIVER WIZARD companion UDT that was updated in Drive ES V7.x. The V6.1 build does not contain the same interface signature.
• If the local AP library is V8.0+ and the Drive ES library is still V6.1, the interface comparison fails and the compiler aborts with an “inconsistent interface” error on FB628.

This is not a license problem (the GSD will be present and the drive will still appear in HW Config), but it is an interface-version problem.

Field-proven compiler output

The error window typically reports one or more of the following lines:

FB628 "DES_DIAG" - Inconsistent interface
DRIVER WIZARD - Unknown data type UDT 198
DRVPCS7 V6.1 blocks are not compatible with AP library V8.0
CFC compilation aborted - 1 error, n warnings

The quick and incorrect workaround is to delete the FB628 instance symbol from the symbol table. The compiler will then pass, but the CFC chart will lose its drive diagnostics, and a large number of warnings will appear because the wizard stub still references the missing UDT. This is a hack, not a fix.

Compatibility Matrix: Drive ES PCS 7 vs PCS 7 Engineering Base

The mapping below is taken from the official Drive ES compatibility tool. Always verify against the latest compatibility list when planning a migration, because Siemens periodically adds new pairings (and deprecates old ones).

Step-by-Step Resolution

Prerequisites

• Local administrator rights on the engineering station.
• Original DRIVE ES PCS 7 product DVD (or licensed download) matching the target PCS 7 version.
• Original SIMATIC PCS 7 DVD for the local installation (or a verified image).
• DriveMonitor V5.4 SP1 or STARTER V4.4.1 already installed (only for the GSD; the library is separate).

Procedure

1. Inventory the local install. Open Start » Siemens Automation » Installed Software. Record the exact versions of PCS 7, Drive ES, DriveMonitor, STARTER, and the AP library. Save the listing for the change log.
2. Remove the retrieved library. In SIMATIC Manager, open the master data library folder. Delete the DRVPCS7 folder that was retrieved from the other computer. Do not delete the FBs/UDTs that are still referenced by the CFC charts until you have a replacement.
3. Insert DRIVE ES PCS 7 from the product DVD. Run the Drive ES setup from the original DVD. If the installer reports “operating system not supported,” do not bypass it with compatibility flags. Resolve by either installing on a supported Windows version, or upgrading the Drive ES version to one that supports Win 7 64-bit.
4. Reinstall or upgrade the license. If you own V6.1 and need to move to V7.x, apply upgrade MLFB 6SW1700-8JD00-0AA4. Transfer the new license to the local license key.
5. Update the master data library. In PCS 7, open the project, then Options » PCS 7 Library Update Wizard (or the equivalent Drive ES wizard) and migrate all Drive ES blocks to the new version. Re-compile CFC/SFC charts.
6. Re-create the DRIVER WIZARD. Open the affected CFC chart. Double-click the DRIVER WIZARD block. The wizard will read the new FB628 interface and rebuild the connection list to SIMO_MM4.
7. Re-compile and download. Compile the S7 program (full, not incremental). Verify the OB1, OB35, OB100, OB101, OB102, and the chart-off downloads. Check that no warning references the old DRVPCS7 V6.1 UDTs.
8. Accept the red triangle. After the drive object is connected to the new SIMO_MM4 block, the red triangle is informational. It is a feature, not a fault. Do not attempt to clear it by editing the object properties.

Verification

1. CFC compile clean. No FB628 error, no missing UDT, no DRIVER WIZARD inconsistency.
2. Online connection. Open the drive block online, force a small setpoint (e.g., 5%), and verify the MM4 ramps and reports actual speed on the diagnostic faceplate.
3. PKW channel round-trip. Read parameter P0700 (command source) and write a temporary value. Confirm the response on the diagnostic view.
4. Diagnostic faceplate. Open the SIMO_MM4 faceplate on the OS. All bitmaps load, no red X for missing block icon.
5. Warning audit. Options » Check Block Consistency returns zero errors and zero warnings related to the DRVPCS7 family.

Installation Order on the Engineering Station

The order of install is important. Drive ES modifies registry entries that DriveMonitor and STARTER read at start-up. If DriveMonitor is installed before Drive ES, the GSD import path is correct. If STARTER is installed after Drive ES, the parameter channel schema is reset and the wizard may need to be re-run.

PROFIBUS DP Network Topology with MM440

The MM4 is connected to PCS 7 via a PROFIBUS DP segment. In the typical PCS 7 station with a CPU 314 PN/2DP, the CPU owns the DP master interface; the MM4 is a slave on the same segment, addressed by its PROFIBUS address set in P0918 (hex). Use the topology below as a reference for cable length, baud rate, and termination rules.

Constraints to respect:

• Maximum 32 nodes per segment without repeater; 126 with repeaters.
• Baud rate vs. segment length: 1.5 Mbps ≤ 200 m, 500 kbps ≤ 400 m, 187.5 kbps ≤ 1000 m.
• DP terminator ON at the first and last physical node, OFF on every node in between.
• For MM440, set P0700 = 6 (PROFIBUS), P1000 = 6 (PROFIBUS setpoint), P0918 = addr, then power-cycle for the new address to take effect.

Field-Proven Diagnostics for DRVPCS7 Issues

Migration Path: PCS 7 V6.1 to V8.0 with MM4

The cleanest migration sequence observed in the field is:

1. Open the V6.1 project in a PCS 7 V7.0 engineering station with Drive ES V6.2 installed. Run the migration tool.
2. Compile, resolve all warnings, take a baseline backup.
3. Move the project to a PCS 7 V8.0 SP1 engineering station with Drive ES V7.1 or V8.0 installed.
4. Run the Drive ES Library Update Wizard. Replace SIMO_MM4 instances with the new revision; recompile.
5. Download to the AS. The MM4 retains its PROFIBUS address; only the program-side blocks change.

If the engineering station hardware has failed (e.g., laptop) and the original Drive ES DVD is lost, contact Siemens Customer Support with the original Certificate of License to request a replacement media set. Do not copy DRVPCS7 from another computer — the version drift is the entire root cause of the symptoms in this article.

Safety and Operational Constraints

• MM440 is not a safety-rated drive. For SIL applications use Sinamics G120 with PROFIsafe and the APL safety block family.
• PROFIBUS DP cable shield must be bonded to ground at both ends with low-impedance clamps; a floating shield is a common source of intermittent PZD errors that look like drive block faults.
• Do not power-cycle the MM440 while a CFC chart is in “inconsistent” state — the next download can write partial parameters to the drive. Always complete the wizard and re-compile before any power-cycle.

FAQ