Restoring Missing Menus and View Toolbars in PCS 7 APL Faceplates in WinCC Runtime

Restoring Missing Menus and View Toolbars in PCS 7 APL Faceplates in WinCC Runtime

In SIMATIC PCS 7 WinCC Runtime, when Advanced Process Library (APL) faceplates open with an empty top header or missing view selection toolbars (preventing access to Standard, Alarm, Limit, or Parameter views), the primary cause is a disabled 'Global Script Runtime' service in WinCC Computer Properties. APL faceplate toolbars rely on client-side C-scripts (such as APL_OpenFaceplate and APL_ChangeView) to dynamically generate view icons and evaluate operator authorization levels. If Global Script Runtime is active, the fault is caused by unconfigured user authorizations in WinCC User Administrator or out-of-sync '@PG_*.pdl' templates requiring an OS Project Editor run.

Table of Contents

Architecture of APL Faceplate Views and Dynamic Toolbars

In SIMATIC PCS 7, the Advanced Process Library (APL) utilizes a modular faceplate architecture to present technological blocks (e.g., MotL, VlvL, PIDConL, MonAnL) to control room operators.

Unlike legacy static popups, an APL faceplate consists of a standardized frame (@APLFaceplate.pdl) hosting dynamic sub-pictures:
* The Header Toolbar: Located at the top of the faceplate frame, displaying navigational buttons for switching views:
* Standard View (@PG_<BlockType>_Standard.pdl): Real-time equipment status, manual/auto commands, and feedback signals.
* Alarm View (@PG_<BlockType>_Alarm.pdl): Active alarms and acknowledgment logs.
* Limit View (@PG_<BlockType>_Limit.pdl): Warning and alarm setpoint thresholds.
* Parameter View (@PG_<BlockType>_Parameter.pdl): Controller tuning, tracking modes, and simulation constants.
* Trend View (@PG_<BlockType>_Trend.pdl): Historical curves and real-time process trends.
* Dynamic View Generation: The buttons present in the toolbar are not hardcoded static elements. During faceplate opening, internal C-actions inspect the block's configured features, active license options, and the operator's clearance to dynamically draw and enable only relevant view buttons.

The Role of Global Script Runtime in Faceplate Header Rendering

The most frequent cause of a completely blank faceplate toolbar in WinCC Runtime is an improperly configured WinCC Computer Startup profile:

  • Script Dependency: The APL faceplate engine depends heavily on compiled C-scripts located in <WinCC_Project>\library\ (e.g., APL_OpenFaceplate.fct, APL_ChangeView.fct, APL_SetView.fct). When a user clicks a block icon, the system passes the technological tag path to the faceplate window and invokes these scripts to build the toolbar.
  • The Failure Mode: If Global Script Runtime is unselected in the WinCC Computer Properties startup list, the internal C-script processing queue (passr_46.exe / cscr_rt.exe) never initializes. When the faceplate window opens, the graphical background renders, but the initialization scripts fail silently. The header area remains completely blank or displays an empty gray rectangle, trapping the operator in the default view without navigational controls.

User Authorization Levels and View Button Suppression

APL faceplates enforce role-based access control governed by WinCC User Administrator:

  • Operator Authorization Levels:
  • Level 5: Process Controlling (Allows toggling modes between Manual and Automatic, starting/stopping equipment).
  • Level 6: Higher-Level Process Controlling (Allows modifying critical parameters, tuning PID constants, and configuring interlock bypasses).
  • Button Suppression Logic:
    If no operator is logged into the OS Client (or if the active user profile lacks Level 6 authorization), APL security logic selectively hides or greys out the Parameter View and Limit View buttons on the toolbar. If the user administration database is corrupted or if the login service (PASSWD.EXE) fails to synchronize, the faceplate may assume a "zero authorization" state, hiding all navigational view buttons.

Template Synchronization and the OS Project Editor

When migrating PCS 7 systems or updating libraries (e.g., from APL v7.1 to v8.0, or v8.1 to v8.2), inconsistencies between template files in the OS project directory can break faceplate navigation:

  • The @PG_*.pdl Pictures: The master faceplate pictures (such as @PG_MotL.pdl and @APLFaceplate.pdl) are installed into the Siemens system directory and deployed into the OS project's GraCS folder.
  • Role of the OS Project Editor: The OS Project Editor (SIMATIC Manager > OS > Open Object > OS Project Editor) is responsible for copying updated system screens, scripts, and screen resolution settings into the active WinCC project. If an engineer updates the APL library on the Engineering Station but omits running the OS Project Editor, the project's GraCS directory retains obsolete faceplate templates that cannot interface with modern APL runtime scripts.

Troubleshooting Matrix for Inoperable APL Faceplate Menus

The following table details diagnostic checks and recovery actions for missing faceplate menus:

Observed SymptomUnderlying CauseCorrective ActionEntire top toolbar is blank; no buttons appearGlobal Script Runtime not running in WinCCOpen WinCC Computer Properties > Startup > Check "Global Script Runtime"Standard/Alarm views visible, but Parameter/Limit views missingLogged-in user lacks Level 6 authorizationLog in as operator with "Higher-Level Process Controlling" authorizationToolbar buttons visible but clicking them does nothingCorrupted script cache or missing .fct filesRecompile WinCC C-scripts via WinCC Explorer > Global Script > Compile AllError dialog: "Picture @PG_... not found" upon clicking buttonOS Project Editor was not executed after updateRun OS Project Editor to deploy updated @PG_*.pdl files into GraCSFaceplate opens partially off-screen or croppedScreen resolution mismatch in OS Project EditorIn OS Project Editor, set resolution to match the physical monitor (e.g., 1920x1080)Toolbar displays red cross or broken image placeholdersMissing SVG / EMF icon graphics in GraCSCopy missing @APL_*.emf graphics from library installation directory

Step-by-Step Procedure to Restore Faceplate Toolbars

Follow this verified engineering procedure to restore missing APL faceplate menus:

  1. Enable Global Script Runtime:
    * Open WinCC Explorer on the Engineering Station or OS Server/Client.
    * In the left tree, right-click Computer and select Properties.
    * Select the local computer object and click Properties.
    * Navigate to the Startup tab.
    * Under "Additional Applications/Tasks to start", verify that Global Script Runtime is checked.
    * Click OK and restart WinCC Runtime.
  2. Execute the OS Project Editor:
    * In WinCC Explorer, double-click OS Project Editor.
    * Under the Layout tab, select the correct monitor layout and resolution.
    * Under the Complete Configuration tab, ensure standard templates are selected.
    * Click OK to overwrite outdated system templates and scripts in GraCS.
  3. Recompile Global Scripts:
    * In WinCC Explorer, expand Global Script > C-Editor.
    * In the C-Editor menu, select Options > Compile All Scripts.
    * Verify that compilation finishes with 0 Errors and 0 Warnings.
  4. Audit WinCC User Administrator:
    * Open User Administrator in WinCC Explorer.
    * Select the active operator group and verify that Authorization Level 5 (Process Controlling) and Authorization Level 6 (Higher-Level Process Controlling) are assigned.
    * Verify that user login functions correctly in runtime.

Verification

Verify that APL faceplate navigation operates correctly:
1. In WinCC Runtime, click any APL motor (MotL) or valve (VlvL) block icon.
2. Confirm that the faceplate window opens cleanly with all top navigation buttons visible: Standard, Alarm, Limit, Parameter, and Trend views.
3. Click each view button sequentially; verify that the sub-picture updates instantaneously without graphical lag or error popups.
4. Open the WinCC diagnostic console (apidiag.exe or diagnose.log in <WinCC_Project>\Diagnostics\) and verify that no missing C-function or script execution timeout errors are recorded.

Limitations and Operational Precautions

  • Custom Modifications to @PG_*.pdl: Never modify Siemens system templates (@PG_*.pdl) directly without backing them up. Running the OS Project Editor restores factory templates, completely overwriting custom changes. Custom views must be implemented using the documented APL block extension guidelines.
  • Client-Server Script Execution: On multi-client systems (WinCC Clients without their own project), ensure Global Script Runtime is enabled on the OS Client computer properties, as faceplate UI scripts execute locally on the client workstation.
  • Restarting WinCC: Enabling Global Script Runtime in Computer Properties requires stopping and restarting WinCC Runtime to take effect.
  • Commercial Accuracy: Ensure the OS Runtime and Client packages (6ES7658-2CX58-0YB5) are correctly authorized via Automation License Manager. Validate with an authorized Siemens distributor quotation.

Engineer FAQ

Can a missing faceplate menu be caused by an incomplete OS compilation?

Generally no. OS compilation populates the WinCC Tag Management database and block icon instances. Faceplate menus and view switching mechanisms are controlled by WinCC graphics templates and C-scripts in GraCS and library.

Why do faceplate menus disappear only when logged in as a field technician?

Technician accounts are frequently assigned limited authorizations (e.g., Level 5 only) to prevent unauthorized changes to process tuning constants. If Level 6 is missing, Parameter and Limit views are suppressed by design.

Does running OS Project Editor delete my custom plant graphics?

No. OS Project Editor only updates system pictures prefixed with @ (e.g., @APLFaceplate.pdl, @screen.pdl). Your custom technological pictures (e.g., Boiler_Overview.pdl) remain untouched.

Why are faceplate menus broken on OS Clients but working fine on the OS Server?

Each OS Client maintains its own local Computer Properties. If Global Script Runtime was enabled on the OS Server but left unchecked on the OS Client, faceplates will fail on the client while functioning properly on the server.

Technical References

Related Articles

Related Tags

  • APL Faceplates
  • Global Script Runtime
  • WinCC Menus
  • OS Project Editor
  • User Administrator
  • PCS 7 HMI
6 respuestas