Resolving Driver Generator Error 'Necessary files are missing for block SINAG120' in SIMATIC PCS 7

In SIMATIC PCS 7, the compilation error 'Necessary files are missing for block SINAG120. Please note that you have to install exactly the same version of the library as the one this block was imported from' occurs when a project containing SINAMICS G120 drive blocks is compiled on an Engineering Station that lacks the Drive ES PCS 7 software package. While the project contains the block instances in its database, the local Engineering Station lacks the underlying compiler rules and XML driver generator files in the STEP 7 system directories. To resolve this, install Drive ES PCS 7 V8.1 on the Engineering Station, or delete the unused block instances and clean up block types.

Root Causes of Missing Driver Files During CFC Compilation

In multi-engineer automation environments, projects are frequently transferred between Engineering Stations (ES) or checked out from version management repositories (such as Version Trail).

When compiling CFC charts on a new or newly formatted Engineering Station, the compile aborts during the Generate module drivers phase with the explicit error:

E: Necessary files are missing for block SINAG120. 
Please note that you have to install exactly the same version of the library 
as the one this block was imported from.
Module driver generation aborted.

The engineer verifies that:
* The SINAG120 block exists in the CFC chart.
* Siemens STARTER software is installed on the computer.
* Drive libraries appear in the project.

Despite this, the compiler refuses to generate module drivers. This failure stems from a fundamental distinction between Project Block Storage and Local Compiler Descriptor Files.

Drive ES PCS 7 System Architecture and Driver Generation

When an engineer places a drive block (such as SINAG120 from the Drive ES library) into a CFC chart, two distinct data sets are involved:
1. The Block Instance (In Project): The function block code (FB) and instance data block (DB) are saved inside the project's offline block folder (S7 Program -> Blocks). Anyone opening the project can view the chart.
2. The Driver Generator Rules (On Local ES): During CFC compilation with Generate module drivers, the compiler does not simply copy blocks. It parses XML descriptor files, device mapping tables, and rule files located strictly within the host PC's operating system directory:
C:\Program Files (x86)\SIEMENS\STEP7\S7LIBS\DRVPCS7\
C:\Program Files (x86)\SIEMENS\STEP7\S7BIN\

If the Engineering Station does not have the Drive ES PCS 7 software package installed, these rule files do not exist on the local hard drive. The compiler cannot determine which diagnostic driver (MOD_DRV) to generate or how to interconnect hardware status words, immediately aborting the build.

Comparison Table - Drive ES Installation States and Compiler Behavior

The following table compares compiler behavior across different Engineering Station software installation configurations.

Software Installed on ESCFC Chart Open / EditCFC Compile (Without Drivers)CFC Compile (With Drivers)Target AS DownloadPCS 7 Base OnlyPossible (Blocks visible)Compiles with warningsFails: 'Necessary files missing'BlockedPCS 7 + STARTER OnlyPossibleCompiles with warningsFails: 'Necessary files missing'BlockedPCS 7 + Drive ES PCS 7Fully SupportedFully SupportedCompiles Cleanly (Generates MOD_DRV)Fully SupportedUninstalled Block (Cleaned)Not applicableCompiles cleanlyCompiles cleanlyFully Supported

Step-by-Step Resolution and Software Installation Workflow

Depending on whether the plant actively uses SINAMICS G120 drives or if the blocks are obsolete remnants, execute one of the two resolution workflows:

Workflow A: Active Drive Installation (Install Drive ES PCS 7)

Verify Installed Software on Both Engineering Stations:
* On the original ES where the project was authored, open SIMATIC Manager.
* Select Help -> About SIMATIC Manager -> Installed Software.
* Note the exact version: e.g., Drive ES PCS 7 V8.1.
Install Drive ES PCS 7 on Current ES:
* Mount the Drive ES PCS 7 V8.1 installation media.
* Run Setup.exe with administrative rights.
* Ensure that both Classic and APL libraries are checked.
* Reboot the Engineering Station.
Transfer License Keys via ALM:
* Open Automation License Manager (ALM) and transfer the Drive ES PCS 7 engineering license.
Recompile CFC Charts:
* Open CFC. Select Chart -> Compile -> Charts as Program.
* Check Generate module drivers.
* The compiler locates the newly installed system files and completes with zero errors.

Workflow B: Obsolete Drive Logic (Remove Block Types)

If the SINAMICS G120 drive is no longer part of the plant:
1. Delete All Instances from CFC Charts:
* Search and delete every instance of SINAG120 from all CFC charts.
2. Clean Up Block Types:
* Open any CFC chart. Select Options -> Block Types.
* Click Clean Up. Select SINAG120 and delete it from the chart folder.
* In the second dialog, delete it from the block folder.
3. Recompile Charts:
* Compile CFC charts with Generate module drivers. The compiler succeeds because no orphaned drive blocks remain.

Verification

Confirm that module driver generation functions without missing file errors:

Verify Component Registry:
* In SIMATIC Manager, select Help -> About SIMATIC Manager -> Installed Software.
* Confirm that Drive ES PCS 7 appears in the installed components list.
Check CFC Compilation Log:
* Compile CFC charts with Scope: Changes only and Generate module drivers enabled.
* Open the compilation log. Confirm that MOD_DRV driver generation completes with zero errors.
Verify Generated Diagnostic Connections:
* In CFC, open the system-generated diagnostic chart @....
* Verify that the generated MOD_DRV block connects cleanly to the drive hardware address.

Limitations and Operational Precautions

Version Parity Mandate: The Drive ES PCS 7 version installed on the Engineering Station must match the version from which the block was imported. Mismatched minor builds can trigger schema parsing errors.
STARTER is Not Sufficient: Do not assume that installing Siemens STARTER or G120 SSPs (Support Packages) resolves the issue; Drive ES PCS 7 is an independent commercial product.
Commercial Procurement Notice: Validate software package order numbers (MLFBs) and license counts with an authorized Siemens distributor prior to procurement.

Engineer FAQ

Why does STARTER include G120 firmware packages but not SINAG120?

STARTER is an equipment parameterization tool designed for drive commissioning. SINAG120 is a PCS 7 technological function block designed for cyclic PLC control and automatic driver generation, which belongs exclusively to Drive ES PCS 7.

Can I copy the missing files manually from another computer?

Manually copying files between C:\Program Files (x86)\SIEMENS\ is strongly discouraged. It bypasses Windows registry COM object registration and fails to license the driver generator components in Automation License Manager.

What is the replacement for SINAG120 in modern APL projects?

In modern APL projects, Siemens recommends using FbDrive (FB 1881) paired with MotSpdCL (FB 1856) or the dedicated SINAMICS PCS 7 APL library rather than legacy classic Drive ES blocks.

Does installing Drive ES PCS 7 require an AS stop?

No. Installing Drive ES on the Engineering Station affects only the compiler environment. The subsequent AS download can be performed under Change in RUN (CiR) if hardware configurations are unchanged.