Resolving Module Driver Generation Errors and Missing XML Actions in PCS 7 PowerControl Migrations

When migrating a SIMATIC PCS 7 project from V8.0 to V9.0/V9.1 with third-party or power engineering libraries (such as SIMATIC PCS 7 PowerControl for 3WL/3VL breakers and PAC3200 meters), CFC compilation errors stating 'Value BITVAL is not defined in file...' or driver generation failures are caused by missing V9.0-compatible XML driver action files in 'STEP7\S7DATA\driver\action\09000000\'. To resolve this, install the official SIMATIC PCS 7 PowerControl V9.0 package on the Windows 10 Engineering Station, update block types in the master data library, assign symbolic I/O addresses to hardware modules in HW Config, and recompile CFC charts with 'Generate module drivers' enabled.

Executive Summary

Migrating legacy SIMATIC PCS 7 projects (such as V8.0 SP2 on Windows 7) to modern releases (such as PCS 7 V9.0 SP1 / V9.1 on Windows 10) is a major engineering undertaking. When projects incorporate electrical power distribution devices—such as SENTRON 3WL/3VL air circuit breakers, PAC3200/PAC4200 power meters, or SIRIUS motor starters using the SIMATIC PCS 7 PowerControl library—compiling CFC charts on the upgraded engineering station frequently aborts.

The compiler issues fatal driver generator errors such as: Value BITVAL is not defined in file AL_FCHN3.xml or Driver generator error: Driver block for device cannot be generated. Engineers sometimes attempt to circumvent this by connecting absolute I/O addresses (e.g., IW2021) directly without symbols, but the compilation still fails. The root cause is that legacy V8.0 library installers are incompatible with Windows 10 and fail to register the mandatory XML module driver action files required by the PCS 7 V9.0 driver generator. This guide details the complete migration workflow to restore module driver generation for PowerControl devices.

Architecture and Fundamental Mechanics

The PCS 7 driver generator (Generate module drivers) uses rule-based XML transformation engines to construct diagnostic @ charts:

The Driver Generator XML Rule Engine:
- When 'Generate module drivers' is selected during CFC compilation, the driver engine scans the hardware configuration (HW Config) to identify all installed submodules, interface modules, and intelligent field devices.
- To instantiate diagnostic and channel blocks (e.g., CH_DI, CH_AI, PAC_CHANNEL), the compiler parses XML action files stored in:
C:\Program Files (x86)\Siemens\STEP7\S7DATA\driver\action\<VersionNumber>\ (e.g., 09000000 for PCS 7 V9.0).
- These XML files (e.g., AL_CHPAC.xml, AL_3WL.xml) define the exact hardware profile, diagnostic alarm triggers, and symbolic mapping rules.
The Incompatible Library Installation Dilemma:
- When an engineering station is migrated from Windows 7 to Windows 10, copying library blocks from an old project or forcing a legacy V8.0 setup does NOT populate the 09000000 driver directory.
- When the compiler encounters a PAC3200 or 3WL module in HW Config, it seeks the corresponding V9.0 XML action file. If the file is missing or contains obsolete V8.0 macros (such as BITVAL), the driver generator crashes with syntax exceptions.
Symbolic Addressing and Channel Driver Binding:
- PCS 7 module drivers require consistent symbolic names assigned in the STEP 7 Symbol Table (Symbols).
- Connecting raw absolute addresses (IW2021) directly to channel block pins bypasses driver generation rules, leaving diagnostic channels unconnected and causing broken pointer errors.

Step-by-Step Implementation Procedure

Follow these steps to upgrade the PowerControl library and resolve driver compilation errors:

Install Official V9.0 PowerControl Library:
- Obtain the official installation package: SIMATIC PCS 7 PowerControl Version 9.0 SP1 (or matching your installed PCS 7 version).
- Execute the official Setup.exe on the Windows 10 Engineering Station as Administrator.
- The setup installer registers COM objects, updates Windows registry keys, and creates the required XML action files in:
C:\Program Files (x86)\Siemens\STEP7\S7DATA\driver\action\09000000\.
Verify Presence of Driver XML Action Files:
- Open Windows File Explorer and navigate to C:\Program Files (x86)\Siemens\STEP7\S7DATA\driver\action\09000000\.
- Confirm that PowerControl driver definitions (e.g., AL_CHPAC.xml, AL_3WL.xml) are present and have valid file timestamps.
Update Master Data Library and Block Types:
- Open the migrated multiproject in SIMATIC Manager.
- Open the Master Data Library (MDL).
- Copy the latest PowerControl blocks (e.g., PC_3WL, PC_PAC3200), APL blocks, and Basis Library blocks into the MDL block folder.
- In the MDL, select 'Options > Charts > Update Block Types...'.
- Select all target projects and execute the block type update to ensure all instances in CFC reflect the V9.0 interface.
Verify HW Config and Symbol Table Consistency:
- Open HW Config for the automation station.
- Select the PAC3200 or 3WL hardware module.
- Verify that all I/O addresses have valid symbolic names assigned in the Symbol Table (do NOT leave them as raw unassigned absolute addresses).
- Select 'Station > Save and Compile'.
Recompile CFC Charts with Module Drivers:
- Open any CFC chart.
- Select 'Chart > Compile > Charts as Program...'.
- Select 'Entire program' and ensure 'Generate module drivers' is CHECKED.
- Click 'OK'. The driver generator compiles without XML syntax errors and builds the diagnostic @ charts.
Download to S7 CPU:
- Download the updated program to the S7 controller (in RUN mode if delta download is allowed, or schedule a warm restart if structural interface changes occurred).

Verification

Inspect the CFC compilation log: verify that the compilation finishes with 0 Errors and that module driver generation concludes successfully.
Open the chart folder: confirm that system @ charts (e.g., @(1)) contain newly generated diagnostic blocks for the PAC/3WL devices.
Open a CFC chart in Test Mode: confirm that PowerControl channel blocks receive valid process values (e.g., Voltage, Current, Active Power) with Good quality status (16#80).
In WinCC Graphics, verify that electrical device faceplates display live electrical measurements.

Limitations and Operational Precautions

Never manually edit the XML driver files in S7DATA\driver\action\; corrupting these files can cause widespread compiler crashes across all automation stations. Direct absolute addressing without symbolic names disables automated diagnostic generation. Verify software compatibility matrices and license requirements for SIMATIC PCS 7 PowerControl through an authorized Siemens distributor or the Siemens Industry Mall.

Engineer FAQ

What causes the error 'Value BITVAL is not defined in file...' during compile?

It is caused by the PCS 7 V9.0 driver generator attempting to parse outdated or mismatched XML action files from a legacy V8.0 library.

Can I copy library blocks from a PCS 7 V8.0 project to V9.0 directly?

No. Copying blocks alone does not install the driver XML action files or registry entries required by the V9.0 module driver generator.

Where are PCS 7 module driver XML action files located?

In C:\Program Files (x86)\Siemens\STEP7\S7DATA\driver\action\<VersionNumber>\ (e.g., 09000000 for V9.0).

Is absolute addressing allowed on PCS 7 channel blocks?

While technically possible, PCS 7 driver blocks require symbolic names linked to HW Config to enable automated module driver generation and diagnostics.