C135 PCS 7 (PCS7)
6C
6 Cielo Ciencia y Tecnología
·Publicada en C135 PCS 7 (PCS7)

Resolving 'Generate Module Driver' Errors and Missing Library Dependencies in PCS 7 CFC

Resolving 'Generate Module Driver' Errors and Missing Library Dependencies in PCS 7 CFC

In SIMATIC PCS 7 CFC compilation, the error 'E: "generate module driver" function found [X] errors' (frequently reporting hundreds of errors upon interconnecting I/O addresses) occurs when the Engineering Station lacks the specialized device driver library—such as the SIMOCODE pro PCS 7 Library or ET 200 device integration packages—used when the project was originally created. When an I/O address belonging to an intelligent field device is wired to a channel block, the module driver generator attempts to instantiate corresponding diagnostic blocks (e.g., MOD_D1, SIMOCODE_DP) but fails because the block templates and driver rules are missing from the newly rebuilt ES. Reinstalling the exact add-on library and updating block types resolves the errors.

Table of Contents

Architecture of the PCS 7 Module Driver Generator

In SIMATIC PCS 7, the Generate Module Drivers mechanism is an automated system engineering function executed during CFC compilation. Its primary purpose is abstracting hardware diagnostic complexity away from the application programmer:

  1. Hardware Scanning: The compiler parses the active Hardware Configuration (HW Config) of the S7-400 Automation Station, identifying all racks, interface modules, communications processors, distributed I/O stations (ET 200M, ET 200S, ET 200SP), and intelligent field devices (e.g., SIMOCODE pro motor management systems, SINAMICS variable frequency drives).
  2. Channel Interconnection Parsing: The compiler inspects CFC charts for technological channel blocks (such as Pcs7DiIn, Pcs7AnIn, F_CH_DI, or device-specific channel blocks).
  3. Automatic Driver Instantiation: For every connected I/O channel, the driver generator automatically instantiates standardized system diagnostic and driver blocks (such as RACK, SUBNET, MOD_D1, MOD_D2, OB_BEGIN, OB_END), places them into dedicated system charts (prefixed with @), interconnects diagnostic addresses (LADDR), and links health statuses (QBAD, QUALITY) directly into the technological blocks.

Why Missing ES Libraries Trigger Hundreds of Module Driver Errors

When an Engineering Station suffers a hard drive crash or a project is transferred to a newly provisioned engineering PC:
* The Rebuild Trap: The engineer typically installs the base SIMATIC PCS 7 software package (e.g., PCS 7 V7.1 SP2 or V8.2) and opens the retrieved project backup.
* Missing Add-on Software: Many industrial projects utilize specialized Siemens add-on packages that are not part of the standard PCS 7 DVD installation. Chief among these is the SIMOCODE pro PCS 7 Library (3UF7982-0AA10-0) or Drive ES PCS 7.
* The Compilation Failure: When the engineer modifies a chart and compiles with Generate module drivers enabled:
* If no I/O addresses are connected, the driver generator skips diagnostic block placement.
* The moment the engineer assigns a hardware address belonging to a SIMOCODE device, the generator attempts to execute the driver generation script for that device profile.
* Because the SIMOCODE library is missing from the local STEP 7 installation, the driver generator cannot locate the required block templates (e.g., SIMOCODE_DP, MM_DIAG).
* The compiler throws hundreds of cascade errors (e.g., 420 errors for a multi-motor installation), halting the compilation.

Analyzing the Module Driver Diagnostic Tab in CFC Compilation Logs

When CFC compilation aborts with "Generate module driver function found errors", engineers should not focus on the summary count:

  • Navigating to Driver Logs: In the CFC Compilation log window, navigate four tabs to the right to select the Module Drivers log tab.
  • Identifying Missing Blocks: The log explicitly states the missing component:
  • Error: Block type SIMOCODE_DP not found in offline block folder or master data library.
  • Error: Driver rule file @simocode.cfg not found in SysLib.
  • Error: Device module at logical base address 256 has no matching driver generator script.
  • This specific diagnostic pinpoints exactly which software add-on package or library installer is absent on the ES.

The Role of Intelligent Field Devices (SIMOCODE pro / ET 200)

Intelligent field devices on PROFIBUS DP or PROFINET IO require two distinct software layers on the Engineering Station:

  • Layer 1: Device Integration (HW Config / PDM):
    Device descriptions (GSD files, EDD, or Object Managers) allow HW Config to recognize the device hardware (3UF7010-1AU00-0). This layer allows saving and compiling the hardware configuration.
  • Layer 2: Technological Driver Library (CFC SysLib):
    The PCS 7 Block Library contains the S7 runtime blocks, faceplates, and compiler rule files (.cfg / .xml).
  • If Layer 1 is present on the ES, HW Config compiles without error. However, without Layer 2, CFC compilation fails completely when generating module drivers, exposing the architectural divide between hardware definition and driver generation.

Diagnostic Matrix for Module Driver Generation Errors

The following table details common module driver generation error scenarios and their resolution:

Error Message in Module Drivers LogRoot CauseVerified RemediationBlock type 'SIMOCODE_DP' / 'MM_REV' not foundMissing SIMOCODE pro PCS 7 Library on newly installed ESInstall the SIMOCODE pro PCS 7 Library matching the original versionDriver generator could not find rule for module at address...Device GSD installed, but PCS 7 driver library missingInstall the manufacturer's PCS 7 companion driver packageDevice not supported by module driver generatorGeneric GSD device used instead of standard PCS 7 slave profileReplace generic GSD module in HW Config with official Siemens catalog profilePcs7FBDin channel block cannot connect to addressFieldbus device assigned non-standard I/O areaAlign module address boundaries in HW Config according to PCS 7 rulesAddress exceeds process image partition (PIP)Channel assigned to an address outside configured OB execution PIPOpen HW Config > Module Properties > Assign I/O to matching PIP (e.g., PIP 1 for OB35)

Step-by-Step Procedure to Restore Missing Libraries and Recompile

Follow this verified engineering procedure to recover from module driver compilation errors:

  1. Identify Missing Library Package:
    * Open the CFC compilation log and inspect the Module Drivers tab.
    * Note the missing block types (e.g., SIMOCODE_DP, DriveES, or specialized ET 200SP drivers).
  2. Install Add-on Library Packages:
    * Obtain the exact version of the missing software package (e.g., SIMOCODE pro PCS 7 Library V7.1 or matching version).
    * Close SIMATIC Manager and run the official Siemens setup installer on the Engineering Station.
  3. Update Master Data Library and Project Blocks:
    * Open SIMATIC Manager and open the Master Data Library.
    * Open the newly installed system library (under File > Open > Libraries).
    * Copy the required driver blocks into the project's Master Data Library Blocks container.
    * In SIMATIC Manager, select Options > Charts > Update Block Types to synchronize block signatures across the multi-project.
  4. Compile Hardware Configuration:
    * Open HW Config for the S7-400 AS.
    * Click Save and Compile to ensure all diagnostic address maps are validated.
  5. Re-Execute CFC Compilation:
    * Open any CFC chart.
    * Select Chart > Compile > Entire program.
    * Ensure the checkbox Generate module drivers is checked.
    * Verify that compilation completes successfully with 0 Errors.

Verification

Verify that module driver generation functions deterministically:
1. In the CFC compilation log, verify that the summary reports 0 Errors and 0 Warnings.
2. Open the Run Sequence editor in CFC and navigate to the cyclic task (e.g., OB35). Confirm that system charts prefixed with @ (e.g., @SIMOCODE..., @MOD_...) have been successfully generated.
3. Open a CFC chart containing a SIMOCODE or intelligent device channel block; verify that the input pins LADDR, QUALITY, and diagnostic pointers are actively linked to the @ system driver blocks.
4. Download the compiled program to the S7-400 CPU (or S7-PLCSIM) and verify that the CPU diagnostic buffer reports no block call faults or parameter assignment errors.

Limitations and Operational Precautions

  • Never Uncheck "Generate Module Drivers" as a Workaround: Disabling the "Generate module drivers" checkbox allows CFC compilation to finish, but leaves all channel blocks disconnected from hardware diagnostics. The plant will run blind without wire-break detection, module failure alarms, or channel passivation.
  • Library Version Consistency: Always verify that the installed library version matches the PCS 7 system version. Mixing a PCS 7 V8.2 SIMOCODE library into a PCS 7 V7.1 SP2 project will corrupt block headers and trigger compile errors.
  • Master Data Library Discipline: In multi-user engineering environments, always maintain all add-on blocks in the centralized Master Data Library to guarantee that any engineer retrieving the project has identical block versions.
  • Commercial Accuracy: Add-on driver libraries—such as the SIMOCODE pro PCS 7 Library (3UF7982-0AA10-0) and SIMOCODE hardware (3UF7010-1AU00-0)—require valid engineering licenses. Procure software entitlements via an authorized Siemens distributor quotation.

Engineer FAQ

Why did removing the I/O address in CFC eliminate the compilation errors?

The module driver generator only creates diagnostic blocks for I/O addresses that are actively interconnected to channel blocks in CFC. Removing the address causes the compiler to ignore the uninstalled device driver, concealing the underlying problem.

Can I manually create module drivers instead of installing the library?

No. PCS 7 module drivers consist of complex state machines, diagnostic interrupt handlers, and automated alarm generators that cannot be replicated manually. Installing the official library is mandatory.

What is the difference between an Object Manager (OM) and a PCS 7 Driver Library?

An Object Manager integrates the device into STEP 7 HW Config, allowing parameterization and networking. A PCS 7 Driver Library provides the CFC runtime blocks and faceplates that process cyclic data and diagnostic interrupts in the CPU.

Does installing a missing library require a CPU download in STOP mode?

If the missing driver blocks were already present in the CPU prior to the ES crash and you are merely restoring the offline engineering environment to match the controller, compilation and delta download in RUN mode can be achieved once block signatures are synchronized.

Technical References

Related Articles

Related Tags

  • Module Drivers
  • CFC Compilation
  • SIMOCODE pro
  • Driver Library
  • HW Config
  • Pcs7DiIn
6 respuestas