Resolving SIMOCODE pro V Module Driver Generation Errors on CPU Integrated DP Ports in PCS 7

During CFC compilation in SIMATIC PCS 7 V9.0 SP2, the driver generator error 'E: Value OUT_STATUS is not defined in file 09000000\AL_CHN_APL.xml / FbAnIn. >>>Due to the previous error(s), creation of module drivers was aborted<<<' occurs when a SIMOCODE pro V motor management device is connected to the CPU 410-5H integrated PROFIBUS DP interface using Basic Type 1 or Basic Type 2 hardware configurations. To resolve this error, configure the SIMOCODE device using the 'Universal Module' profile or install the dedicated PCS 7 SIMOCODE pro Library Object Manager (OM) package to ensure that diagnostic structures and APL channel driver XML tags align with the CPU integrated master driver rules.

Executive Summary

Integrating intelligent low-voltage motor control centers (MCC) using SIMOCODE pro V over PROFIBUS DP is standard practice in SIMATIC PCS 7 process automation. While commissioning engineers successfully integrate SIMOCODE devices on external communications processors (such as CP 443-5 Extended), attempting to attach identical devices directly to the CPU 410-5H integrated DP master system frequently causes CFC compilation to abort during the 'Generate Module Drivers' phase. The compiler halts with an unhandled XML parsing exception: Value OUT_STATUS is not defined in file AL_CHN_APL.xml. This article explains the diagnostic differences between CPU-integrated DP ports and external CP master systems, identifies the driver mapping conflict, and provides verified hardware configuration resolutions.

Architecture and Fundamental Mechanics

Generate Module Drivers Architecture, XML Driver Templates, and DP Master Diagnostic Differences:

Architecture of Module Driver Generation in PCS 7:
During CFC compilation with Generate Module Drivers checked, the compiler traverses the HW Config database to detect all DP slaves, PA devices, and PROFINET nodes.
It queries driver XML definition files (e.g. AL_CHN_APL.xml, MOD_SIMOCODE.xml) to determine which diagnostic blocks (MOD_SW_T1, OB_DIAG1) and channel blocks (FbAnIn, FbDiIn) to instantiate automatically.
Why CPU-Integrated DP Differs from CP 443-5 Extended:
CP 443-5 Extended Master System: External CPs offload DP protocol handling from the CPU, managing diagnostic alarms via specialized CP diagnostic function blocks (FB106 / FC50 / FC60). The module driver generator routes telemetry through CP-specific driver templates that do not query APL analog channel driver status registers directly.
CPU 410 Integrated DP Interface: Slaves on the integrated port interact directly with the CPU's internal System Function Calls (SFC 51 RDSYSST / SFC 59 RD_REC).
When a SIMOCODE is configured with pre-packaged Basic Type 1 or Basic Type 2 GSD modules, the hardware definition exposes I/O address spans that the driver generator misinterprets as raw APL analog channels (FbAnIn). Because generic GSD definitions lack the PCS 7-specific OUT_STATUS attribute in their XML profile, the parser encounters an undefined key and aborts driver generation.
Resolution Mechanics:
Utilizing the Universal Module configuration in HW Config or deploying the official SIMOCODE pro PCS 7 Library OM (Object Manager) replaces the raw GSD definitions with structured Siemens PCS 7 slave descriptors, allowing the driver generator to map diagnostic telemetry cleanly without OUT_STATUS XML parsing errors.

Step-by-Step Implementation Procedure

Verify SIMOCODE Library and Object Manager Installation:
* Confirm that the SIMOCODE pro PCS 7 Library V9.0 SP2 (matching PCS 7 V9.0 SP2) is installed on the Engineering Station.
* Verify in SIMATIC Manager via Help > About > Display Installed Software that the SIMOCODE Object Manager (OM) is present.
Reconfigure SIMOCODE Hardware in HW Config:
* Open HW Config for the CPU 410-5H station.
* Navigate to the PROFIBUS DP master system on the integrated CPU DP port.
* Delete the slave module configured under Basic Type 1 or Basic Type 2.
* Re-insert the SIMOCODE pro V slave from the catalog: select PROFIBUS DP > SIMOCODE pro > SIMOCODE pro V (PCS 7 Library) (do not use the generic GSD folder).
Alternative Resolution using Universal Module:
* If using a standard GSD configuration, open the SIMOCODE DP slave properties.
* In the slot configuration, replace Basic Type 1 with the Universal Module.
* Configure the exact input/output byte length (e.g. 4 bytes input, 2 bytes output) matching the physical SIMOCODE device parameterization.
Verify Driver Interconnections in CFC:
* In CFC, ensure that the driver block MMMeas or MMSimo connects to the designated diagnostic input addresses.
* Ensure that the block is scheduled in a standard cyclic interrupt OB (e.g. OB35).
Execute CFC Compilation:
* In the CFC Editor, select Chart > Compile > Changes only.
* Ensure that Generate Module Drivers is checked.
* Confirm that compilation finishes with '0 Errors, 0 Warnings' and that system driver charts (@...) generate cleanly.

Verification

Inspect the compiled S7 program in SIMATIC Manager; confirm that driver charts prefixed with @ contain the proper MOD_SW_* blocks.
Download changes to the CPU 410-5H in RUN mode.
Open the SIMOCODE faceplate in WinCC Runtime; verify that motor current, operating state, and ready status update in real time with zero channel faults.

Limitations and Operational Precautions

Do not mix generic non-PCS 7 GSD files with official Siemens SIMOCODE PCS 7 Library blocks on the same master system; mixing slave profiles creates diagnostic address collisions in OB86/OB82.

Engineer FAQ

Why did 'Value OUT_STATUS is not defined in AL_CHN_APL.xml' occur during CFC compilation?

The module driver generator attempted to link a generic SIMOCODE Basic Type module on the integrated DP port as an APL analog channel, failing due to missing XML metadata.

Why did the error occur on the integrated CPU DP port but not on CP 443-5?

CP 443-5 uses external CP diagnostic driver templates, whereas the integrated CPU DP port uses direct SFC diagnostic calls and strict APL driver templates.

How do I fix this module driver error?

Configure the slave using the 'Universal Module' profile or install the official SIMOCODE pro PCS 7 Library Object Manager (OM).

Can I compile without 'Generate Module Drivers'?

Unchecking Generate Module Drivers bypasses the error, but leaves all hardware diagnostic blocks and channel driver links missing, breaking runtime faceplates.