Fixing PCS7 Channel Driver Version Mismatch Compile Error

Problem Overview

In SIMATIC PCS 7 V7.x, V8.x, and V9.x projects, attempting to compile or download an Automation Station (AS) CFC/SFC program with Generate module drivers enabled in the compile dialog halts with the error:

"The Program contains signal processing blocks from different libraries."

The error aborts compilation before code generation, blocks the AS download, and persists even when:

• The project has been reduced to a single chart with one block.
• Working against an S7-PLCSIM V5.x or S7-PLCSIM V6 instance (no real CPU).
• The hardware configuration (HW Config) has been re-imported from a clean export.

The error is not caused by chart logic, signal wiring, or hardware; it is a structural property of the S7 program block folder. The same error pattern surfaces during OS (Operator Station) compile & load when the AS has been brought online without first resolving the driver mix.

Root Cause Analysis

Every PCS 7 channel driver is delivered as an FB type inside the master libraries that ship with each PCS 7 release. Each FB carries an Author attribute (visible in SIMATIC Manager → Blocks → right-click → Object Properties → Author) that encodes the originating library version. The standard author tags observed in field projects are:

The condition typically appears after one of the following maintenance actions:

1. Migrating a project from a previous PCS 7 release using the PCS 7 Migration Tool without performing a master data library update.
2. Copying CFCs between stations that were authored on different PCS 7 versions.
3. Manually inserting driver blocks from an older PCS 7 Library catalog when the master data library was not updated.
4. Installing a PCS 7 service pack (for example V9.0 SP3 → V9.0 SP8) but failing to update the master data library.

Identifying the Conflicting Authors

Before applying the recovery procedure, capture the current author distribution so the migration is auditable.

1. Open the affected AS in SIMATIC Manager.
2. Expand Charts → select the S7 program (S7-Program) node.
3. Double-click Blocks to open the offline block container.
4. Press Ctrl+A to select all blocks.
5. Right-click → Object Properties. The Author field lists the originating library version for each FB.
6. Right-click the column header in the block view and enable Author as a visible column; sort by this column to group offenders.

Any FB that is an instance of a type from the DRIVER family (FB1869, FB1870, FB1871, FB1872, FB1873, FB1874, FB1875, FB1876, FB1877, FB1878, FB1879, FB1880, FB1881, FB1882, FB1883, FB1884, FB1885, FB1886, FB1887, FB1888, FB1889, FB1890 in PCS 7 V8.x; the same FBs renumbered in V9.x) must carry the same DRIVERnn stamp.

Solution: Update Block Types from the Master Data Library

The recovery procedure replaces every DRIVER-family block instance in the S7 program with the equivalent type from the newer PCS 7 Library, eliminating the mixed-version condition. This is the recommended procedure for plants already in operation where a full project migration is not scheduled.

Prerequisites

• The Master Data Library for the target PCS 7 release is installed on the engineering station (ES). Verify via SIMATIC Manager → File → Master Data Library → Open.
• All charts are closed in CFC/SFC Editor.
• No active download to the AS is in progress.
• Logged in with a Windows account that has write access to the project directory.

Step-by-Step Procedure

1. CPU must be in STOP for the duration of the operation. Bring the AS to STOP using PLC → Operating Mode → Stop or via the CPU front panel. For PLCSIM, toggle the mode switch to STOP.
2. Open the Master Data Library for the target version (e.g., V9.1) via File → Master Data Library → Open.
3. Navigate to the DRIVER sub-library within the Master Data Library.
4. Open the target S7 program in the project side: Charts → S7-Program → Blocks.
5. Select all blocks inside the S7 program's Blocks container (Ctrl+A).
6. Choose Options → Charts → Update Block Types. The Update Block Types wizard starts.
7. Select the destination Master Data Library if prompted, then enable Replace block types with the corresponding type from the Master Data Library.
8. Click Continue through the wizard pages until Finish is offered.
9. The wizard reports the number of types replaced. Confirm the count matches the count of DRIVER-family FBs detected in the previous audit.
10. Re-open the Blocks container and verify that the Author column now contains a single DRIVERnn value matching the target PCS 7 release.
11. Save the project (Ctrl+S).
12. Compile the AS: Charts → Compile → Charts (entire program). The compile dialog must show Generate module drivers enabled (do not uncheck it — the option is required to instantiate channel drivers from the signal processing blocks).
13. Download the AS to the CPU. The download is only permitted while the CPU remains in STOP.
14. Compile the OS: right-click the OS → Compile OS. Use Entire OS with Scope = All.
15. Download the OS to the operator station.
16. Bring the CPU back to RUN.

Alternative Recovery: Clean Re-Import of the Station

When the wizard-based update fails (for example due to inconsistent type references in deeply nested multi-instance charts, or when the Update Block Types wizard reports zero replacements even though a mix exists), the station can be reconstructed cleanly.

1. Export the HW Config of the affected station: Station → Export. Save the .cfg file to a known path.
2. Delete the affected station from the project (right-click → Delete).
3. Create a new station of the same type (SIMATIC 400 Station or SIMATIC PC Station as appropriate).
4. Re-import the hardware: Station → Import and point at the saved .cfg, OR open HW Config and re-insert the rack / I/O manually from the PCS 7 catalog of the target version.
5. Create a new chart folder (Insert New Object → S7 Program → Charts).
6. Insert a new CFC and add the signal processing blocks (CH_AI, CH_AO, CH_DI, CH_DO, PADP_L0, PADP_L1) from the current PCS 7 catalog. These catalog blocks are the type stubs that Generate module drivers expands into the DRIVER-family FBs.
7. Re-create the interconnections using the Cross-References tool from the prior charts as input.
8. Compile → Download AS → Compile OS → Download OS.

Block Catalog Reference

The signal processing blocks that Generate module drivers expands are catalog blocks in the CFC library browser. They are the visible face of the channel driver layer:

Verification

After performing either procedure, validate the following before resuming production:

1. Compile success: CFC compile completes with no warnings of different library category. The compiler log should be empty for type conflicts.
2. Single author: Open the S7 program Blocks container, sort by Author, confirm a single DRIVERnn value matches the target PCS 7 release.
3. CPU in RUN: Bring the CPU from STOP → RUN. The diagnostic buffer (accessible via PLC → Diagnostic Buffer or via the CPU front panel) must contain no entries for SF (system fault) or OB121 (programming error) attributable to channel driver FBs.
4. Process image update: Verify on the OS faceplate that an analog input changes value when the field signal is forced, confirming the CH_AI → DRIVER FB chain is alive.
5. WinCC restart: For OS-side anomalies, execute reset_wincc.vbs from the WinCC project directory on each OS server, then re-load the OS project.
6. Cross-station consistency: Repeat the audit (Step 6 of identification) on every AS in the multiproject. Mixed-version conditions frequently propagate via copy/paste of charts across stations.

Prevention

• Single library policy: Establish a project-level rule that only one PCS 7 Library version is allowed in any S7 program. Enforce via a project engineering checklist signed before each hot-cut or migration.
• Master Data Library discipline: Every time the engineering station receives a PCS 7 service pack or upgrade, the Master Data Library must be refreshed via Options → PCS 7 → Library Update Wizard before any project is opened.
• Pre-compile audit: Add an automated report (VBA macro against the SIMATIC Manager automation interface, or a PCS 7 Commissioning Tool script) that lists the Author of every FB in every S7 program and flags heterogeneity.
• PLCSIM regression: Before any code change is downloaded to a live AS, recompile against PLCSIM and verify the absence of the different libraries warning. This catches mix conditions introduced by copying chart snippets.

Troubleshooting Matrix

Firmware and Software Compatibility Notes

The driver version mix error is independent of the CPU firmware (e.g., CPU 410-5H V8.x or CPU 416-3 V7.x) but interacts with the PCS 7 version installed on the ES. The following table lists the supported combinations for the most common deployments:

When upgrading ES software without upgrading the project, the Master Data Library must be reinstalled to match. Refer to the SIMATIC PCS 7 installation manual for the ES-specific prerequisites:

• SIMATIC PCS 7 V9.1 - Function Manual
• SIMATIC PCS 7 Engineering System - Configuration Manual
• SIMATIC PCS 7 Library Updates – Service Pack Notes