C135 PCS 7 (PCS7)
6C
6 Cielo Ciencia y Tecnología
·Publicada en C135 PCS 7 (PCS7)

How to Restore PROFIBUS-PA Field Instrument Communication After Upgrading PCS 7 from V6.1 to V8.0

How to Restore PROFIBUS-PA Field Instrument Communication After Upgrading PCS 7 from V6.1 to V8.0

In SIMATIC PCS 7 project upgrades from V6.1 to V8.0, PROFIBUS-PA field instruments failing to communicate and reporting bad signal quality after downloading to the CPU occur because direct migrations across two major versions skip essential database schema conversions, leaving legacy driver blocks in charts and outdated Electronic Device Descriptions (EDD) in SIMATIC PDM. Siemens migration rules mandate a multi-step upgrade path: V6.1 to V7.0 SP3, V7.0 to V7.1 SP4, and finally V7.1 to V8.0. Resolving communication requires updating PDM device catalogs, replacing legacy driver blocks with modern Basis Library blocks via 'Update Block Types', and compiling hardware configurations with module drivers.

Table of Contents

Architectural Evolution of PROFIBUS-PA Integration Between V6.1 and V8.0

In industrial process plants, smart field instrumentation (such as pressure, temperature, and flow transmitters) is widely integrated via PROFIBUS-PA linked to the Automation Station through DP/PA Couplers or DP/PA Links (e.g., IM 153-2 interface modules).

Between SIMATIC PCS 7 V6.1 and V8.0, Siemens fundamentally transformed the fieldbus software architecture:
1. The Transition to Advanced Process Library (APL): Legacy driver blocks (such as PA_AI, PA_DI, PA_TOT) were retired and replaced by unified channel drivers (Pcs7AnIn, Pcs7DiIn) integrated with Basis Library diagnostic blocks (MOD_PA, DP_RACK).
2. SIMATIC PDM Integration: Device parameterization shifted to SIMATIC PDM V8.0, which enforces updated Electronic Device Description (EDD) libraries complying with EDD Interoperability standards.
3. Hardware Descriptor Evolution: DP/PA Link GSD configurations in HW Config were replaced by certified native catalog profiles supporting Configuration in RUN (CiR) and extended diagnostic interrupts.

Why Direct Migration from V6.1 to V8.0 Fails

Engineers frequently attempt to open a PCS 7 V6.1 project directly on a PCS 7 V8.0 Engineering Station, compile the project, and download it to the S7-416 controller. While the compiler may complete without fatal syntax errors, all PROFIBUS-PA instruments remain dead, showing bad process quality (16#00) in runtime.

Technical Reasons Direct Migration Fails

  • Unsupported Multi-Version Jump: Siemens software engineering does not support skipping intermediate major releases. Database tables and CFC block container pointers cannot bridge the architectural gap between V6.1 and V8.0 directly.
  • Orphaned V6.1 Driver Block Instances: The V8.0 Driver Wizard cannot dynamically wire modern diagnostic structures to legacy V6.1 PA_AI blocks, leaving the technological blocks disconnected from physical peripheral I/O addresses.
  • SIMATIC PDM Device Description Desynchronization: PDM V8.0 cannot communicate with field devices using legacy V6.1 communication profiles, preventing engineers from viewing or modifying PROFIBUS addresses.

Step-by-Step Remediation for Restoring PA Instruments

To restore complete communication and diagnostic integration for PROFIBUS-PA field devices:

Step 1: Follow the Mandatory Multi-Step Upgrade Path

Migrate the project database sequentially through certified intermediate versions:
* Step 1: Open and convert the project in PCS 7 V7.0 SP3.
* Step 2: Open and convert in PCS 7 V7.1 SP4.
* Step 3: Open and perform the final migration in PCS 7 V8.0 SP1 / SP2.
(Note: At each stage, execute 'Save As... with Reorganization (slow)' to ensure clean database conversions).

Step 2: Update the SIMATIC PDM Device Catalog

  1. On the PCS 7 V8.0 Engineering Station, launch Device Integration Manager (DIM) for SIMATIC PDM.
  2. Insert the official SIMATIC PDM Device Library DVD (Device Catalog).
  3. Search for and install the updated EDDs for all installed PA transmitters (e.g., Sitrans P, Sitrans FM, Endress+Hauser Cerabar).
  4. In SIMATIC Manager, open the Process Device Plant View and execute View -> Update to bind the devices to their new EDDs.

Step 3: Update Block Types to PCS 7 V8.0

  1. Open the project's Master Data Library and copy the blocks from PCS 7 Basis Library V8.0 and PCS 7 AP Library V8.0.
  2. Open any CFC chart, select menu Options -> Block Types..., and click Update Block Types across all S7 programs.
  3. Delete all automatically generated @Charts (e.g., @(1), @(2)).

Step 4: Recompile HW Config and CFC with Module Drivers

  1. In HW Config, select Station -> Save and Compile.
  2. In CFC Editor, compile the program: select Entire Program and check Generate module drivers.
  3. Download the hardware configuration and user program to the AS in CPU STOP mode.

Migration Steps and Driver Library Compatibility Matrix

The following table summarizes the verified migration milestones required when upgrading from PCS 7 V6.1 to V8.0:

Migration MilestoneSupported ActionDriver Block LibraryPDM VersionStep 1: PCS 7 V6.1 SourceBaseline SystemStandard PCS 7 Library V6.1PDM V6.0Step 2: PCS 7 V7.0 SP3Intermediate MigrationPCS 7 Basis Library V7.0PDM V6.1Step 3: PCS 7 V7.1 SP4Intermediate MigrationPCS 7 Basis Library V7.1PDM V7.0Step 4: PCS 7 V8.0 TargetFinal ModernizationPCS 7 Basis Library V8.0 / APLPDM V8.0Direct Jump (V6.1 -> V8.0)Strictly ProhibitedIncompatible Block FootprintsCommunication Fails

Adhering to the verified migration ladder ensures 100% fieldbus communication reliability.

Verification

To verify that PROFIBUS-PA instruments have resumed normal communication:
1. In HW Config, switch to online monitoring; confirm that all DP/PA Couplers, DP/PA Links, and PA slave nodes report status 'Normal / Healthy' (BF LEDs extinguished).
2. In CFC Editor Test Mode, open a channel driver block (Pcs7AnIn); verify that PV_Out.Value displays live process measurement and PV_Out.ST displays 16#80 (Good Quality).
3. In SIMATIC Manager Process Device Plant View, right-click a PA transmitter and select Open Object; confirm SIMATIC PDM opens and establishes online communication to read parameters.
4. In WinCC Runtime, confirm that the analog indicator icon displays live values without quality warning badges.

Limitations and Operational Precautions

  • Direct downloads of migrated projects across major versions require an Entire Program download in CPU STOP mode; schedule migration during a planned plant shutdown.
  • Do not attempt to upgrade physical field instrument firmware unless specifically mandated by Siemens compatibility advisories; firmware changes in hazardous areas carry explosion protection risks.
  • Always archive the original V6.1 multiproject and store backups of each intermediate conversion step.
  • For procurement and ordering, always validate final license quantities and MLFBs against the applicable Siemens catalog and authorized distributor quotation.

Engineer FAQ

Why does direct migration from V6.1 to V8.0 compile if it is unsupported?

Step 7 compilers check basic syntax and data types, which may pass syntactically, but internal database tables, communication handles, and driver wizard hooks are incompatible, leading to runtime communication failures.

How do I find a field instrument's PROFIBUS address using SIMATIC PDM?

In SIMATIC Manager, switch to Process Device Network View, expand the DP/PA Link network, right-click the field instrument, and select Device -> Assign Address and TAG to view or modify its PROFIBUS address.

Can I continue using legacy V6.1 standard blocks in PCS 7 V8.0?

Yes, but you must update them to the V7.1 SP4 / V8.0 release of the Standard Library. Mixing un-updated V6.1 blocks with V8.0 module drivers is strictly unsupported.

Technical References

Related Articles

Related Tags

  • PROFIBUS_PA
  • SIMATIC_PDM
  • PCS7_Upgrade
  • DP_PA_Link
  • Migration_Path
6 respuestas