Resolving 'Hardware Not Supported in Module Driver' CFC Compilation Warnings in SIMATIC PCS 7

In SIMATIC PCS 7, CFC compilation warnings stating 'W: CPU.X2.N11 (6ES7151-1AA05-0AB0) is not supported' or 'W: -SC4 (3UF7010-1AB00-0) is not supported' indicate that the module driver generator cannot find dedicated diagnostic driver blocks in the active library for those specific modules. While basic I/O addresses function via direct mapping, automated system diagnostics, rack-failure monitoring, and passivated channel alarms will not be generated. To resolve this, install the required add-on library (such as SIMOCODE pro PCS 7 Library or ET 200S PCS 7 Library) or configure manual diagnostic handling.

PCS 7 Module Driver Generation Architecture and Hardware Profiles

During CFC chart compilation in SIMATIC PCS 7, the Module Driver Generator automatically inspects the hardware configuration (HW Config):
* Automated Diagnostic Wiring: The compiler creates diagnostic blocks (MOD_*, RACK_*, OB_DIAG) that monitor module health, power supplies, and fieldbus communication integrity.
* Supported Hardware Catalog: The standard PCS 7 Basis Library contains driver rules for primary DCS hardware (S7-400, ET 200M, ET 200SP HA, CFU).
* Unsupported Hardware Warning: When third-party devices, standard factory automation hardware (e.g. ET 200S 6ES7151-1AA05-0AB0), or specialized motor controllers (e.g. SIMOCODE pro 3UF7010-1AB00-0) are present without their dedicated PCS 7 library, the compiler logs warning W: Module is not supported and skips automated driver generation.

Root Causes of 'Module Not Supported' Compilation Warnings

When these warnings appear during CFC compilation:
1. Missing Specialized Add-On Library: Devices like SIMOCODE pro (3UF7) require the SIMATIC PCS 7 SIMOCODE pro Library. Without this library installed, the compiler does not know how to generate MM_DIAG or MM_STAT blocks.
2. Standard Automation I/O Used in DCS Projects: The ET 200S interface module 6ES7151-1AA05-0AB0 is a standard factory automation module. In PCS 7, ET 200M (6ES7153-2BA10-0XB0) or ET 200SP HA is standard. ET 200S requires the separate 'PCS 7 Industry Library' or ET 200S driver package.
3. Program Functions Despite Warnings: Process I/O still reads and writes because standard channel drivers (Pcs7DiIn, Pcs7DiOu) access the raw peripheral address directly; however, no diagnostic alarms are generated if a card blows a fuse or disconnects.

Remediation Procedure - Installing Add-On Libraries and Custom Diagnostic Handling

Follow this procedure to eliminate compiler warnings and restore diagnostic coverage:

[Phase 1: Identify Required Add-On Libraries]
   │  • For SIMOCODE pro motor managers (3UF7 010-...):
   │      Install: "SIMATIC PCS 7 SIMOCODE pro Library" (e.g. V8.2)
   │  • For ET 200S / ET 200pro distributed I/O:
   │      Install: "SIMATIC PCS 7 Industry Library" or ET 200S driver expansion
   │
[Phase 2: Integrate Add-On Blocks into Master Data Library]
   │  • Open the installed library in SIMATIC Manager
   │  • Copy diagnostic and control blocks into your Multiproject Master Data Library
   │  • In CFC: Select Options -> Block Types -> Update Block Types across all charts
   │
[Phase 3: Recompile CFC with Module Drivers]
   │  • Open CFC Editor -> Chart -> Compile -> Changes Only (or Entire program)
   │  • Ensure [x] "Generate module drivers" is checked
   │  • Review compilation log:
   │      Confirm that warnings "W: Module is not supported" are eliminated!

Hardware Driver Support and Add-On Library Matrix

Compare hardware modules and their respective PCS 7 driver libraries:

Hardware ModuleDescriptionStandard Basis Library SupportRequired Add-On LibraryET 200M (IM 153-2)Standard PCS 7 Modular I/OFully Supported (Native)Included in PCS 7 Basis LibraryET 200S (IM 151-1)Standard Compact I/ONot Supported NativelyPCS 7 Industry Library / ET 200S PackSIMOCODE pro (3UF7)Motor Management SystemNot Supported NativelySIMOCODE pro PCS 7 LibrarySINAMICS DrivesInverters and Variable Speed DrivesNot Supported NativelyDrive ES PCS 7 / SINAMICS LibraryStandard Third-Party DPGeneric GSD DeviceNot Supported NativelyGeneric Channel Drivers (CH_DI, CH_AI)

Verification

To confirm that module driver warnings are resolved:
1. In CFC Editor, execute Chart -> Compile -> Entire program with 'Generate module drivers' enabled.
2. Review the compile log; verify that zero warnings are reported for the ET 200S or SIMOCODE modules.
3. Open the generated system chart (@2/...); verify that the appropriate diagnostic blocks are placed and interconnected.
4. Simulate a field fault (e.g. disconnect a SIMOCODE motor cable); verify that WinCC Alarm Logging displays an automated diagnostic alarm.

Limitations and Operational Precautions

Never ignore 'Module not supported' warnings in critical continuous process plants. While analog and digital values may update during healthy operation, an unsupported module cannot report channel passivation, power loss, or wire break faults to the operator. If field hardware loses power, channel values will freeze or hold last values without generating alarms, creating severe operational blind spots.

Engineer FAQ

Will my plant run safely if I ignore these compilation warnings?

The logic executes, but you lose all automated system alarms for hardware failures. If an unmonitored I/O module faults, operators will not receive diagnostic alarms on SCADA.

Where can I find the SIMOCODE pro PCS 7 Library?

It is an official Siemens add-on package available on SIOS or ordered through Siemens Industry Mall under MLFB 3UF7982-0AA20-0.

Can I create custom module drivers for unsupported third-party devices?

Yes. Engineers can use the PCS 7 Driver Generator and create XML driver description files, but using standard certified libraries is strongly recommended.

What is the difference between a warning (W:) and an error (E:) in CFC compile?

An error (E:) halts compilation and blocks CPU download. A warning (W:) allows compilation and downloading to proceed, but alerts the engineer to potential operational deficits.