Compatibility and Migration Constraints of the PCS 7 Measuring Point Browser in Older Releases

Compatibility and Migration Constraints of the PCS 7 Measuring Point Browser in Older Releases

The SIMATIC PCS 7 Measuring Point Browser cannot be backported or transferred from PCS 7 V8.2 or V9.x into PCS 7 V8.0 because it relies on WinCC V7.3/V7.4 operating system controls, C-script APIs, and SQL database schema extensions that do not exist in the WinCC V7.0 SP3 environment of PCS 7 V8.0. The tool is an integrated feature of Advanced Process Library (APL) V8.1/V8.2 onwards. To utilize the Measuring Point Browser, the plant must upgrade the engineering and operator systems to PCS 7 V8.2 or higher. In PCS 7 V8.0, equivalent operational filtering must be achieved using the WinCC Alarm Logging Hit List, custom User Archives, or standard Plant Hierarchy navigation.

Table of Contents

Executive Summary

The Measuring Point Browser (@MeasuringPointBrowser / @pg_meas_point_browser.pdl) is an indispensable diagnostic and navigation tool introduced in modern releases of SIMATIC PCS 7. It provides operators with a centralized, searchable console to filter measuring points across the entire plant hierarchy by alarm status, maintenance state, simulation mode, or disabled interlocks, enabling instant faceplate invocation. Automation engineers maintaining older legacy installations (specifically SIMATIC PCS 7 V8.0) frequently ask whether the underlying PDL and C-scripts can be copied into their project to deliver this functionality without a major DCS upgrade. This article explains the deep architectural dependencies that prevent backporting, details the software prerequisites, and outlines functional workarounds for PCS 7 V8.0 systems.

Architecture and Fundamental Mechanics

Measuring Point Browser Architecture, WinCC Release Dependencies, and APL Schema Integration:

  • Core Functionality of the Measuring Point Browser:
  • Introduced natively in PCS 7 V8.1 and expanded in V8.2 and V9.x, the Measuring Point Browser is accessible via the WinCC Button Bar (@Buttons11.pdl).
  • It presents a comprehensive, high-speed data grid aggregating: Tag Name, Description, Higher-Level Identifier (HID), Alarm State (Alarm, Warning, Tolerance), Maintenance State (In Progress, Released), Simulation Mode, and Quality Code.
  • Clicking any entry instantly opens the associated APL faceplate or navigates directly to the host process screen.

  • Deep Architectural Dependencies on Modern WinCC and APL Versions:

  • WinCC Product Version Discrepancy: PCS 7 V8.0 is built on WinCC V7.0 SP3. The Measuring Point Browser was introduced with WinCC V7.3 / V7.4 (PCS 7 V8.1 / V8.2).
  • ActiveX / OCX Control Requirements: The browser interface (@pg_meas_point_browser.pdl) relies on specialized .NET/WPF and OCX controls (such as the Siemens Grid Control and APL Browser Engine) registered as part of the PCS 7 V8.2 installation. These binaries are incompatible with the legacy COM/OCX framework in WinCC V7.0 SP3.
  • WinCC SQL Database Schema: In PCS 7 V8.2+, the OS compiler populates extended relational metadata tables within the WinCC runtime database (CC_..._R). WinCC V7.0 SP3 lacks these SQL database views and stored procedures.
  • Internal C-Script and Global Script API: The browser calls internal DLL routines (apllib.dll, @APLViewTag) that do not exist in APL V8.0 libraries.

  • Failure Mode when Attempting File Transfer:

  • If an engineer copies @MeasuringPointBrowser.pdl from a V8.2 project into a V8.0 GraCS directory:
    • Opening the picture in Graphics Designer generates ActiveX loading errors.
    • In WinCC Runtime, opening the browser produces script runtime exceptions in apdiag.exe ('Function not defined', 'Failed to connect to database').
    • The grid remains empty, and faceplate cross-linking fails.

Step-by-Step Implementation Procedure

  1. Official Upgrade Path to Access Measuring Point Browser:
    * Review plant hardware and software compatibility for PCS 7 V8.2 or V9.1.
    * Procure the official PCS 7 Software Upgrade package from V8.0 to V8.2 (or V9.1).
    * Upgrade Engineering Stations and OS Servers according to the official Siemens 'Software Update' guidelines.
    * Recompile CFC charts with modern APL libraries, compile the OS, and run the OS Project Editor to deploy the native browser.

  2. Practical Workarounds for PCS 7 V8.0 Systems:
    * Workaround A: WinCC Alarm Logging Hit List:

    • In WinCC Alarm Logging, configure a dedicated filter view that queries active alarms and warnings.
    • Operators can double-click active alarms in the Hit List to jump directly to the associated process screen.
    • Workaround B: Plant Hierarchy Overview Navigation:
    • Organize process graphics cleanly in the Plant Hierarchy so operators can use the standardized Picture Tree Manager to navigate from Unit to Area overviews.
    • Workaround C: Custom WinCC User Archive / Tag Table:
    • Create a WinCC User Archive table containing critical measuring points, tags, and status descriptions.
    • Embed a WinCC User Archive Table Control in an auxiliary screen to provide a searchable tag table for operators.

Verification

  1. On a PCS 7 V8.2 or V9.x station, click the Measuring Point Browser icon in the button bar; confirm that all measuring points populate the grid within 2 seconds.
  2. Filter by 'Simulation active'; verify that any channel driver with SimOn = 1 appears immediately.
  3. Click a row; verify that the APL faceplate opens immediately over the process graphic.
  4. On legacy PCS 7 V8.0 stations, verify that alternative Alarm Logging Hit Lists provide fast access to upset tags without script crashes.

Limitations and Operational Precautions

Manual file backporting of modern PCS 7 system PDLs to older releases violates Siemens software support policies and can cause WinCC runtime process crashes (pdlrt.exe). Upgrading from PCS 7 V8.0 requires updating the operating system (e.g. from Windows 7 or Server 2008 R2 to Windows 10 or Server 2016/2019) and purchasing software upgrade licenses.

Engineer FAQ

Can I copy the Measuring Point Browser PDL to PCS 7 V8.0?

No. The PDL relies on WinCC V7.3+ OCX controls, C-scripts, and SQL database views that do not exist in the WinCC V7.0 SP3 environment of PCS 7 V8.0.

What PCS 7 version introduced the Measuring Point Browser?

It was introduced in PCS 7 V8.1 and enhanced in PCS 7 V8.2 with full APL filtering.

What happens if I try to open the browser in PCS 7 V8.0?

Graphics Designer reports ActiveX control registration errors, and WinCC Runtime generates script errors while displaying a blank window.

What can I use instead of the browser in PCS 7 V8.0?

Use the WinCC Alarm Logging Hit List, custom User Archive tables, or the standard Plant Hierarchy picture tree navigation.

Does upgrading from V8.0 to V8.2 require new licenses?

Yes, upgrading requires PCS 7 Software Upgrade licenses for the ES, OS Servers, and OS Clients.

Technical References

Related Articles

Related Tags

  • Measuring Point Browser
  • PCS 7 V8.0
  • PCS 7 V8.2
  • WinCC V7.0
  • WinCC V7.3
  • APL
  • Software Update
  • System Migration
20 respuestas