Integrating MICROMASTER 440 on PROFIBUS DP in SIMATIC PCS 7: Resolving Drive ES Compilation Errors
In SIMATIC PCS 7, the red triangle on a MICROMASTER 440 in HW Config indicates slave configuration via Drive ES Object Manager. CFC compilation aborts with FB628 DES_DIAG errors when Drive ES blocks are manually copied from legacy projects without installing the licensed Drive ES PCS 7 software package. Resolve this by installing the appropriate Drive ES PCS 7 package (Classic or APL style) matching your PCS 7 release, restoring FB628 to the symbol table, and executing Generate Module Drivers.
Table of Contents
- Drive ES Integration Architecture and Visual Indicators
- Root Cause Analysis: FB628 DES_DIAG and Driver Wizard Mechanics
- Standardized Drive ES Installation and Compilation Procedure
- Drive ES Software Packages and Migration Matrix
- Verification
- Limitations and Operational Precautions
- Engineer FAQ
- Technical References
- Related Articles
- Related Tags
Drive ES Integration Architecture and Visual Indicators
Integrating variable frequency drives such as the Siemens MICROMASTER 440 (MM440) or SINAMICS drives into a SIMATIC PCS 7 project over PROFIBUS DP requires aligning both the hardware communication profile (telegrams) and the software driver architecture.
Engineers frequently encounter two confusing situations when engineering drives:
1. Red Triangle on the Drive Icon in HW Config:
* When inserting a MICROMASTER 440 slave from the hardware catalog onto a PROFIBUS DP line, a small red triangle symbol appears in the lower-right corner of the drive icon.
* Technical Significance: This is not an error. The red triangle indicates that the slave is an integrated Drive ES object (managed by the Drive ES Slave Object Manager / OM) rather than a bare generic GSD slave. It indicates that Drive ES parameter assignment tools (such as STARTER or DriveMonitor) and diagnostic routing can be launched directly from HW Config.
2. Missing Driver Libraries and Manual Block Copying:
* Commissioning engineers who have installed STARTER or DriveMonitor assume these commissioning tools include the PCS 7 block library. They do not find the DRVPCS7 library in their catalog.
* In an attempt to bypass installation, engineers copy SIMO_MM4 or DRV_PCS7 blocks from a legacy project (e.g. PCS 7 V6.1) into a newer system (PCS 7 V7.1 or V8.0).
* Upon compiling CFC, the Driver Wizard generates fatal compilation errors referencing FB628 DES_DIAG; DRIVER WIZARD. Deleting FB628 from the symbol table causes catastrophic compilation termination with numerous unresolvable errors.
Root Cause Analysis: FB628 DES_DIAG and Driver Wizard Mechanics
The Driver Wizard failure highlights how PCS 7 automated module driver generation operates:
-
The Role of the PCS 7 Driver Wizard:
* During CFC compilation with Generate module drivers enabled, PCS 7 inspects the hardware configuration.
* For every drive slave configured in HW Config, the compiler automatically instantiates diagnostic communication blocks (such asFB628 DES_DIAGor modernMOD_DRV) into dedicated diagnostic runtime groups.
* The Driver Wizard wires logical base addresses (LADDR), diagnostic addresses (DADDR), and rack/slot parameters from HW Config directly into the channel blocks (SIMO_MM4). -
Why Deleting FB628 from the Symbol Table Aborts Compilation:
* WhenFB628is manually deleted from the symbol table, the compiler encounters a fatal inconsistency: the hardware catalog rules require instantiatingFB628for Drive ES slaves, but the block definition is missing from the symbol list and offline block container.
* The compiler cannot create diagnostic links and aborts compilation completely. -
Drive ES Software Licensing Separation:
*STARTERandDriveMonitorare freeware tools designed for standalone drive parameterization.
*DRIVE ES PCS 7is a separately licensed commercial software package. It contains the Object Manager (OM) extensions, the official PCS 7 driver blocks, the APL block icons and faceplates, and the Driver Wizard diagnostic rule files (.xml/.met).
Standardized Drive ES Installation and Compilation Procedure
1. Procure and Install the Compatible Drive ES PCS 7 Package
- Verify the operating system and PCS 7 release:
* For PCS 7 V7.1 on Windows XP: Install Drive ES PCS 7 V7.1.
* For PCS 7 V8.0/V8.1/V8.2 on Windows 7: Install Drive ES PCS 7 V8.0 or Drive ES PCS 7 APL V8.0/V8.1.
* Note: Drive ES PCS 7 V6.1 is not compatible with Windows 7 or PCS 7 releases beyond V6.1. - Run setup from the original product media and install with administrative privileges. Ensure the software license is transferred via Automation License Manager (ALM).
2. Restore the Symbol Table and Block Container
- Open SIMATIC Manager, expand the S7 Program folder, and open the Symbols table.
- Re-enter the symbol definition:
* Symbol:DES_DIAG
* Address:FB 628
* Data Type:FB 628 - Open the installed Drive ES PCS 7 Library (
File > Open > Libraries > DRVPCS7). - Copy
FB628and the corresponding drive control block (e.g.,FB620 SIMO_MM4or APL equivalent) into your master offline Block folder.
3. Configure Telegram Structure in HW Config
- In HW Config, select the MM440 slave.
- Verify that the configured PPO (Parameter-Process data Object) type matches the block expectations:
* Standard Drive ES blocks typically use PPO Type 1 (4 PKW words + 2 PZD words) or PPO Type 3 (2 PZD words). - Save and compile HW Config.
4. Execute CFC Compilation with Module Driver Generation
- Open any CFC chart in the project.
- Select Chart > Compile > Charts as Program.
- Check the box Generate module drivers.
- Select Scope: Changes only (or Entire program if updating library versions).
- Confirm compilation finishes with 0 Errors and all diagnostic driver links are generated automatically.
Drive ES Software Packages and Migration Matrix
SIMO_MM4)6SW1700-6JD00-1AA0)SIMO_MM4)6SW1700-7JD00-0AA0)6SW1700-8JD00-0AA4)6SW1700-8JD00-0AA0)Verification
- In HW Config, confirm the MM440 slave shows the integrated Drive ES red triangle and no bus configuration warnings.
- In CFC, instantiate
SIMO_MM4(or APL equivalent) and connect to the drive process image address. - Execute Chart > Compile > Entire Program with Generate module drivers enabled.
- Verify compilation completes with 0 Errors.
- Open the compiled runtime group in OB35; confirm
FB628 DES_DIAGhas been automatically created and wired by the Driver Wizard. - Download to the AS; verify successful PROFIBUS cyclic communication and error-free drive control.
Limitations and Operational Precautions
- Commercial Licensing Guardrail: Drive ES PCS 7 is licensed software protected by Siemens Automation License Manager. It cannot be legally copied or transferred between machines without acquiring appropriate single or upgrade licenses.
- Never Delete System Driver Symbols: Deleting auto-generated system symbols (such as
DES_DIAG,MOD_CP, orOR_M_16) from the symbol table destabilizes the PCS 7 module driver generator. - Procurement Advisory: When ordering Drive ES software upgrades or replacement drives (e.g. migrating MM440 to SINAMICS G120), verify exact order numbers (MLFBs) against the Siemens ST PCS 7 catalog and validate quotations with an authorized distributor.
Engineer FAQ
What does the red triangle on a drive icon in HW Config mean?
It indicates that the drive slave was integrated via the Drive ES Object Manager rather than a generic GSD file, enabling integrated routing, diagnostic links, and direct launching of STARTER/DriveMonitor.
Can I use standard GSD files instead of Drive ES for MM440?
Yes, you can configure an MM440 using its standard PROFIBUS GSD file. However, you will not be able to use automated Driver Wizard generation (FB628) and must write manual communication logic using SFC14/SFC15 (DPRD_DAT/DPWR_DAT).
Can Drive ES PCS 7 V6.1 be installed on a Windows 7 64-bit machine?
No. Drive ES PCS 7 V6.1 has a 32-bit installer restricted to Windows XP / Server 2003. Running on Windows 7 requires upgrading to Drive ES PCS 7 V8.0 or later.
Technical References
- SIMATIC Industrial Software Drive ES PCS 7 Function Manual
- MICROMASTER 440 Operating Instructions: PROFIBUS Optional Board
- SIMATIC Process Control System PCS 7 Released Modules Documentation
- Siemens Industry Online Support: Drive ES PCS 7 Compatibility List (SIOS Entry ID 109780813)
Related Articles
- Configuring SINAMICS G120 and S120 in SIMATIC PCS 7 with Drive ES APL
- Troubleshooting Module Driver Generation Errors in SIMATIC CFC
- Migrating Classic Drive Blocks to Advanced Process Library (APL)
Related Tags
- Drive ES
- MICROMASTER 440
- FB628
- DES_DIAG
- PCS 7 V8.0
- Generate Module Drivers