Resolving FM_DATA Driver Compilation Errors via HW Config PCS 7 Catalog Profiles

When compiling CFC charts containing counter driver block Pcs7Cnt1 for an FM 350-1 module and the compiler aborts with 'E: Parameter CFC(1).1.FM_DATA is not interconnected with a data source' despite following standard application guides, the root cause is selecting the FM 350 module from the generic 'Standard' catalog profile in STEP 7 HW Config instead of the dedicated 'PCS7_Vxx' profile. Generic catalog entries lack the PCS 7 driver wizard metadata required by 'Generate Module Drivers'. To resolve this, delete the module in HW Config, switch the catalog profile dropdown to 'PCS7_V8x', re-insert the FM 350-1, compile HW Config, and recompile CFC charts.

Executive Summary

Automated driver generation (Generate Module Drivers) is one of the foundational productivity features of SIMATIC PCS 7. When compiling Continuous Function Charts (CFC), the engineering system scans the hardware configuration, identifies physical modules, instantiates diagnostic drivers (MOD_D1, MOD_HA), and establishes interconnection pointers to technological channel driver blocks (such as Pcs7Cnt1). However, automation engineers configuring high-speed counter modules (like the FM 350-1) frequently encounter a perplexing compilation error: 'E: Parameter CFC(1).1.FM_DATA is not interconnected with a data source'. Even after thoroughly reviewing application manuals and verifying addresses, compilation fails. The underlying cause is an obscure but critical configuration mistake: selecting the module from the generic STEP 7 catalog profile rather than the dedicated PCS 7 catalog profile. This guide clarifies the profile mechanics and resolution.

HW Config Catalog Profiles: Standard vs PCS 7 Engineering

The hardware catalog in STEP 7 HW Config features a Profile selection dropdown:

Standard Profile: Contains the complete Siemens automation catalog (SIMATIC S7-300, S7-400, C7, ET 200, legacy modules) configured for classic STEP 7 (LAD/FBD/STL) programming.
PCS 7 Profile (PCS7_V81, PCS7_V90): Filters the catalog to display only hardware modules certified for SIMATIC PCS 7. Crucially, items in this profile contain internal XML metadata schema flags that instruct the PCS 7 driver generator how to bind system functions and parameter DBs.

How the Driver Wizard (Generate Module Drivers) Evaluates Module Metadata

During CFC compilation, the Driver Generator executes an inspection pass:

Examines each channel driver block (Pcs7Cnt1, Pcs7AnIn) and reads its target hardware symbol.
Resolves the symbol back to the specific slot and module in HW Config.
Queries the module's catalog metadata attributes.
If the module was inserted under the Standard Profile, the driver wizard fails to identify the PCS 7 driver template, skips automatic driver creation, and leaves structural pointers (FM_DATA) unlinked.

Root Cause of the Unlinked FM_DATA Parameter Error

Because Pcs7Cnt1.FM_DATA expects an interconnected pointer to module parameter memory:

When the module possesses correct PCS 7 metadata, the driver generator either binds the generated driver structure or validates the user UDT1 link cleanly.
When generic metadata is present, the compiler evaluates FM_DATA as a dangling, unassigned required pin, issuing error: 'Parameter CFC(1).1.FM_DATA is not interconnected with a data source (block output, global address)'.

Catalog Profile Selection and Compilation Behavior Matrix

The following table compares catalog profile selection and CFC driver compilation outcomes:

HW Config Catalog ProfileModule Catalog Entry UsedDriver Wizard RecognitionCFC Compilation OutcomeOperational StatusPCS 7 Profile (PCS7_V8x)FM 350-1 Counter (PCS 7 Path)Fully RecognizedCompiles Cleanly (0 Errors)Channel driver functional.Standard ProfileFM 350-1 Counter (Generic Path)Unrecognized / SkippedAborts: FM_DATA unlinkedCannot download to AS.Redundant ProfilePaired FM 350 ModulesProhibitedAborts: Redundancy unsupportedFM modules cannot be paired.Manual STEP 7 (No Wizard)Generic Catalog EntryWizard disabledCompiles only with manual DBBypasses PCS 7 diagnostics.

Step-by-Step Procedure to Correct Catalog Selection and Resolve Compilation

Method: Re-Inserting Module Under the PCS 7 Catalog Profile

Open HW Config for the target AS controller in SIMATIC Manager.
In the Hardware Catalog window (right pane), locate the Profile dropdown menu at the top.
Change the profile from Standard to PCS7_V81 (or matching PCS 7 release, e.g. PCS7_V80, PCS7_V82).
Locate the existing FM 350-1 module in the ET 200M rack. Note its assigned logical I/O addresses and parameters.
Right-click the existing FM 350-1 module and select Delete.
In the filtered PCS 7 catalog, navigate to: PROFIBUS-DP > ET 200M > FM > FM 350-1 Counter.
Drag the module into the empty slot in the ET 200M rack.
Open module properties; re-assign the operating mode (Continuous Counting) and identical I/O start address.
Execute Station > Save and Compile.
Return to SIMATIC Manager, open the CFC Editor, and ensure a global DB typed to UDT1 is connected to Pcs7Cnt1.FM_DATA.
Execute Chart > Compile > Charts as Program with Generate module drivers checked.
Confirm that compilation finishes with 0 Errors and 0 Warnings.

Verification

To verify that module driver generation functions properly:

Compilation Log Review: Open the CFC compile log. Confirm that the driver wizard outputs 'Module driver generation completed successfully' with zero errors.
Chart Driver Inspection: Open the CFC chart containing Pcs7Cnt1. Confirm that parameter Connect is properly resolved to the hardware channel.
Online Diagnostics: Download the program to S7-PLCSIM or physical AS. Go online in CFC Test Mode; confirm that parameter RETVAL = 0 and live pulse counts update smoothly.

Limitations and Operational Precautions

Always Maintain Profile Discipline: Establish a project engineering standard that HW Config must always remain in the active PCS7_Vxx profile during hardware editing.
Do Not Mix Library Generations: If working in PCS 7 V8.1, do not import FM 350 drivers from older V6 or V7 libraries; use the drivers provided in the PCS 7 V8.1 Basis Library.
Full Download Warning: Re-inserting a module in HW Config modifies the system hardware hash; downloading HW Config requires a planned CPU STOP unless utilizing Configuration in RUN (CiR).

Engineer FAQ

Why does the Standard catalog profile exist if PCS 7 requires the PCS 7 profile?

STEP 7 HW Config is a shared engineering component across both classic STEP 7 (LAD/FBD) and PCS 7; the profile dropdown allows switching engineering contexts.

Can an existing project be automatically converted to the PCS 7 catalog profile?

No; modules inserted under the wrong profile must be manually replaced or updated via catalog update tools.

Does this profile issue affect standard analog and digital cards as well?

Standard digital and analog I/O modules generally share common metadata, but complex function modules (FM) and communication processors (CP) are sensitive to profile selection.

Technical References

Related Tags

https://industrialautomation.net/search?query=simatic-pcs7
https://industrialautomation.net/search?query=hw-config
https://industrialautomation.net/search?query=fm350-1
https://industrialautomation.net/search?query=driver-generator

6 respuestas

Resolving FM_DATA Driver Compilation Errors via HW Config PCS 7 Catalog Profiles