Integrating Foundation Fieldbus Devices in SIMATIC PDM V8.0 SP2 - Resolving Missing Devices and License Prerequisites

Integrating Foundation Fieldbus Devices in SIMATIC PDM V8.0 SP2 - Resolving Missing Devices and License Prerequisites

In SIMATIC PCS 7 with SIMATIC PDM V8.0 SP2, when Foundation Fieldbus (FF) device descriptions (DD/EDD) imported via Device Integration Manager (DIM) create empty category folders in the HW Config catalog without displaying actual field instruments, the issue is caused by a missing 'SIMATIC PDM Communication Foundation Fieldbus' software license or an uncompiled device catalog index. Foundation Fieldbus integration requires an active FF communication license in Automation License Manager (ALM) to unlock FF device profiles, followed by executing 'Save and Compile' in DIM and updating the STEP 7 HW Config catalog.

Table of Contents

Architecture of Foundation Fieldbus Integration in SIMATIC PDM

SIMATIC PDM (Process Device Manager) provides manufacturer-independent parameterization, calibration, and diagnostics for intelligent field devices across multiple industrial protocols (HART, PROFIBUS DP, PROFIBUS PA, and Foundation Fieldbus H1):
- Foundation Fieldbus H1 Architecture in PCS 7:
* Field devices (transmitters, valve positioners) connect via intrinsic safety couplers or link modules (e.g. Compact FF Link) to the Industrial Ethernet or PROFIBUS DP plant backbone.
* Unlike cyclic process variables that flow to controller I/O drivers, acyclic parameterization and device diagnostic schedules (EDDL/DD) are processed through SIMATIC PDM.
- The Role of the Device Integration Manager (DIM):
* In PDM V8.0 and subsequent releases, Device Integration Manager replaces the legacy catalog tool.
* DIM imports device descriptions (.ffo, .sym, .cff, .cfs files), verifies interoperability syntax, and compiles an internal relational database schema that bridges PDM with the STEP 7 hardware catalog (HW Config).

The Role of the SIMATIC PDM FF Communication License

Commercial Accuracy Disclaimer: Software order numbers (MLFBs), package structures, and hardware capacity prerequisites vary across PCS 7 versions and hardware platforms. System integrators must confirm exact software entitlements and licensing requirements against the official Siemens Catalog CA 01 and obtain an authorized Siemens distributor quotation prior to purchasing.

A frequent engineering trap occurs when an engineer installs the PDM software application but lacks the protocol-specific communication option:
1. Modular License Enforcement in PDM V8.0:
- The basic SIMATIC PDM package (SIMATIC PDM Single Point or SIMATIC PDM Basic) supports only point-to-point HART modem communication.
- Integrating fieldbus protocols requires dedicated option licenses:
* SIMATIC PDM Communication FOUNDATION Fieldbus (e.g. MLFB 6ES7658-3QX08-2YB5 or version-equivalent).
* SIMATIC PDM TAG package licenses (scaling 100, 1000, or unlimited process devices).
2. Catalog Suppression Behavior:
- When PDM detects that the FF Communication license is missing from Automation License Manager (ALM), it suppresses the display of Foundation Fieldbus device instances.
- In HW Config, the catalog displays the imported manufacturer folders (e.g. Yokogawa > Pressure), but the folders appear empty because the software engine refuses to load the unlicensed communication driver.

Step-by-Step Device Integration and Catalog Compilation Workflow

To resolve the empty catalog folders and successfully integrate Foundation Fieldbus devices:

  1. Verify License Availability in ALM:
    - Open Automation License Manager.
    - Check the local C: drive and verify that the following licenses are active and valid:

    • SIMATIC PDM Basic (or SIMATIC PDM PCS 7)
    • SIMATIC PDM Communication FOUNDATION Fieldbus
    • Valid SIMATIC PDM TAG license count covering all plant devices.
  2. Re-integrate Devices in Device Integration Manager:
    - Close SIMATIC Manager and HW Config.
    - Launch Device Integration Manager as Administrator (dim.exe).
    - Select File > Read Device Descriptions....
    - Browse to the official device vendor DD source folder or the Siemens PDM Device Library DVD.
    - In the device selection tree, expand Sensors / Actuators > Foundation Fieldbus.
    - Select the target devices and click Install.
    - Ensure the compilation log finishes with: Integration successful with 0 errors.

  3. Rebuild the STEP 7 Hardware Catalog:
    - Launch SIMATIC Manager.
    - Open HW Config on any automation station.
    - In the menu bar, select Options > Update Catalog.
    - The catalog reader parses the updated PDM database.
    - Expand the catalog tree: PROFIBUS-DP > Foundation Fieldbus > Compact FF Link.
    - The field instruments now appear fully populated with their respective device revisions under the manufacturer folders.

Foundation Fieldbus and PDM Communication Licensing Matrix Table

The following table details PDM communication options and licensing prerequisites in SIMATIC PCS 7:

Field ProtocolRequired SIMATIC PDM LicenseUnderlying Hardware InterfaceTypical Physical Transmission MediumHART (Analog)SIMATIC PDM BasicET 200M/ET 200SP HART AI/AO or HART Multiplexer4–20 mA Current Loop (FSK Bell 202)PROFIBUS PASIMATIC PDM Communication PROFIBUSDP/PA Link (6ES7153-2BA10-0XB0) + CouplerMBP (Manchester-encoded Bus Powered, 31.25 kbps)FOUNDATION Fieldbus H1SIMATIC PDM Communication FFCompact FF Link (6ES7655-5FF00-0AB0)H1 Bus (31.25 kbps, Intrinsic Safety FISCO)PROFINET / Modbus TCPSIMATIC PDM Communication PROFINETIntegrated PN Port / CP 443-1Industrial Ethernet (100 Mbps)Asset DiagnosticsSIMATIC PDM Server / MS OptionPCS 7 Maintenance StationOPC / Terminal Bus Network

Verification

To confirm that Foundation Fieldbus devices are fully integrated and accessible:
1. In HW Config, expand the Foundation Fieldbus catalog. Confirm that the target device (e.g. pressure transmitter or control valve) appears with its full model name and firmware revision.
2. Drag and drop the device onto the Compact FF Link H1 segment.
3. Open SIMATIC Manager and switch to Process Device Plant View (View > Process Devices).
4. Double-click the FF device object. Verify that SIMATIC PDM launches without license violation popups.
5. In PDM, execute Device > Upload to PG/PC. Verify that device blocks (Resource Block, Transducer Block, Analog Input Function Block) populate with live field parameters.

Limitations and Operational Precautions

When deploying Foundation Fieldbus with SIMATIC PDM:
1. Never Modify Vendor DD Files: Modifying vendor device description files (.ffo, .sym) using text editors corrupts cryptographic checksums, causing PDM Device Integration Manager to reject the file as invalid.
2. Compact FF Link Compatibility: Verify that the Compact FF Link firmware supports the specific Foundation Fieldbus H1 profile of the instrument. Outdated link module firmware can block acyclic communication while passing cyclic process values.
3. Bus Powering and Termination: Foundation Fieldbus H1 requires dedicated power conditioners and bus terminators (100 ohm + 1 uF) at both physical ends of the trunk segment. Lack of termination induces signal reflections that disrupt PDM parameter uploads.

Engineer FAQ

Why did the PDM application shortcut not appear on my desktop after installation?

When installed within a SIMATIC PCS 7 Engineering Station, SIMATIC PDM operates as an integrated system tool rather than a standalone desktop application. It is launched directly from SIMATIC Manager via Process Device View or by double-clicking devices in HW Config.

Can I use standard HART licenses to communicate with Foundation Fieldbus devices?

No. Siemens strictly segregates communication drivers. An active SIMATIC PDM Communication FOUNDATION Fieldbus license is mandatory in ALM.

What files constitute a complete Foundation Fieldbus Device Description package?

A complete package includes the .ffo (binary device description), .sym (symbol definition file), and .cff (capabilities file) matching the device revision.

How many devices can a single Compact FF Link support?

A Siemens Compact FF Link typically supports up to 31 field devices per H1 segment, subject to total bus current consumption and loop cable resistance limits.

Technical References

Related Articles

Related Tags

  • PCS7_V8_0
  • SIMATIC_PDM
  • Foundation_Fieldbus
  • Device_Integration_Manager
  • ALM_Licensing
  • HW_Config
  • Field_Instrumentation
6 respuestas