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

Resolving Inactive C_INTER5 Interlock Faceplate Navigation in CEMAT V8.1 Drive Diagnostics

Resolving Inactive C_INTER5 Interlock Faceplate Navigation in CEMAT V8.1 Drive Diagnostics

When clicking interlock interfaces (such as ESVG, EBVG, or EBMG) on the diagnostic page of a CEMAT drive faceplate (C_DRV_1D) fails to open the subordinate C_INTER5 interlock faceplate in WinCC Runtime, the issue is typically caused by insufficient user authorizations or missing instance-specific authorization attributes on the block icon. In CEMAT V8.1, diagnostic navigation is protected by WinCC User Administrator privilege levels transmitted from the block icon attributes Processcontrolling_backup and HigherProcesscontrolling_backup. If the logged-in user lacks these rights, or if the OS faceplate scripts were not updated during migration from V7.1, the interlock call is suppressed. Restoring proper authorization assignments and refreshing the CEMAT WinCC PDLs resolves the problem.

Table of Contents

Executive Summary

In cement plants automated with SIMATIC PCS 7 and CEMAT, drive faceplates (C_DRV_1D) provide interactive diagnostic views detailing start conditions, interlocks, and trip sources. Clicking on an active interlock parameter—such as ESVG (Start Interlock General) or EBVG (Operating Interlock General)—is intended to launch the corresponding C_INTER5 or C_INTERL interlock faceplate, enabling operators to trace the root cause of an interlock fault. Following a system migration from PCS 7 V7.1 to V8.1, operators often discover that clicking these buttons produces no response. This article diagnoses the root causes—including WinCC User Administration authorization level mismatches, instance-specific block icon attributes, and outdated GraCS picture scripts—and details the exact steps to restore full diagnostic navigation.

Architecture and Fundamental Mechanics

Faceplate Navigation and Authorization Architecture

CEMAT faceplate architecture relies on dynamic C-scripts and VBS actions embedded within @PG_C_DRV_1D_DIAG.pdl to evaluate whether an operator has permission to inspect or modify subordinate blocks.

+-------------------------------------------------------------------------+
|                        WinCC Runtime Operator                           |
|                                   |                                     |
|                                   v                                     |
|                      [@PG_C_DRV_1D_DIAG.pdl]                            |
|                      Click: Interlock 'ESVG'                            |
+-------------------------------------------------------------------------+
                                    |
                                    v
+-------------------------------------------------------------------------+
|                  Security and Script Verification                       |
|                                                                         |
|  1. Check User Rights in WinCC User Administrator                       |
|     - Level 5: Process controlling                                      |
|     - Level 6: Higher process controlling                               |
|                                                                         |
|  2. Check Block Icon Attributes (Under 'Miscellaneous'):                |
|     - Processcontrolling_backup                                         |
|     - HigherProcesscontrolling_backup                                   |
|                                                                         |
|  3. Validate Target Picture Existence:                                  |
|     - @PG_C_INTER5.pdl and @PG_C_INTER5_DIAG.pdl in GraCS               |
+-------------------------------------------------------------------------+
                                    |
                    +---------------+---------------+
                    |                               |
               [Rights OK]                  [Rights Missing]
                    |                               |
                    v                               v
          Opens @PG_C_INTER5.pdl              Action Suppressed
          with Interlock Details             (No Faceplate Opens)

During migration from CEMAT V7.1 to V8.1, two major architectural changes affect this behavior:
1. Instance-Specific Authorizations: CEMAT V8.1 allows granular operator permissions per drive. The drive's block icon stores backup variables (Processcontrolling_backup and HigherProcesscontrolling_backup) that pass authorization criteria to the faceplate window. If these attributes are empty or reference non-existent authorization levels in WinCC User Administrator, runtime scripts deny execution.
2. Picture and Script Compatibility: The underlying C-script CematOpenInterlock() calls @PG_C_INTER5.pdl. If the OS migration did not overwrite legacy V7.1 GraCS pictures with V8.1 files, the script fails silently due to internal parameter mismatch.

Step-by-Step Implementation Procedure

Step 1: Verify WinCC User Administration Rights

  1. In WinCC Explorer, open User Administrator.
  2. Select the operating user group (e.g., Operators or ProcessEngineers) and the active logged-in user.
  3. Verify that the user has checkmarks enabled for:
    - Authorization Level 5: Process controlling
    - Authorization Level 6: Higher process controlling
  4. If these authorization levels are missing or disabled, enable them, save the configuration, and perform a user logoff/logon in WinCC Runtime.

Step 2: Configure Block Icon Instance-Specific Attributes

  1. In WinCC Graphics Designer, open the process picture containing the drive's block icon (or open the template picture @PCS7Typicals_Cemat.pdl).
  2. Right-click the block icon for the affected drive (C_DRV_1D) and select Properties.
  3. Navigate to the Miscellaneous property group.
  4. Locate the attributes Processcontrolling_backup and HigherProcesscontrolling_backup.
  5. Verify their assigned values:
    - Processcontrolling_backup: Set to 5 (or the custom authorization level configured for basic operation).
    - HigherProcesscontrolling_backup: Set to 6 (or the authorization level configured for interlock inspection/override).
  6. Save the picture and close Graphics Designer.

Step 3: Refresh CEMAT GraCS PDLs and Script Libraries

  1. If authorization settings are correct but the faceplate still does not open, verify whether the WinCC project contains the V8.1 CEMAT screen files.
  2. Open Windows Explorer and navigate to the CEMAT source directory: C:\CEMAT_CS\WinCC\GraCS.
  3. Copy the following files directly into your WinCC project's GraCS directory:
    - @PG_C_INTER5.pdl
    - @PG_C_INTER5_DIAG.pdl
    - @PG_C_INTER5_OVERVIEW.pdl
    - @PG_C_DRV_1D_DIAG.pdl
  4. Copy updated CEMAT C-scripts from C:\CEMAT_CS\WinCC\Library into the WinCC project's library folder.
  5. In WinCC Explorer, open Global Script C, click Options > Regenerate Header, and verify that no compilation errors occur.

Step 4: Verify CFC Interlock Connection Formatting

  1. Open the CFC chart containing the C_DRV_1D block.
  2. Inspect the interlock inputs (ESVG, EBVG, ESVA, EBVA).
  3. Ensure the input is connected directly to the output QINTER of a C_INTER5 or C_INTERL block, or an APL Intlk02/Intlk04 block.
  4. Verify that the OS compile was executed after connecting the interlock block so that WinCC generated the appropriate structure tags.

Verification

  1. Runtime Button Test: Log into WinCC Runtime with an operator account configured with Authorization Levels 5 and 6. Open the C_DRV_1D motor faceplate and navigate to the Diagnostics view.
  2. Navigation Check: Click on the active ESVG button. Verify that the C_INTER5 interlock faceplate opens immediately in a pop-up window showing all 5 input signals, signal status, and bypass conditions.
  3. Access Restriction Test: Log in with a restricted guest account lacking Level 5/6 rights. Open the same diagnostics page and confirm that clicking the interlock button produces a tooltip indicating insufficient authorization, confirming that security logic operates correctly.

Limitations and Operational Precautions

  1. Multiple Interlock Cascades: If multiple C_INTER5 blocks are cascaded in series, the drive faceplate will only jump to the first directly connected block at the ESVG pin. Navigating deeper into the logic tree requires opening downstream interlock blocks sequentially.
  2. APL Interlock Mixing: Connecting standard PCS 7 APL interlock blocks (Intlk04, Intlk08) to legacy CEMAT drive blocks may require the CEMAT APL integration adapter, otherwise the jump script cannot resolve the APL picture name @PG_Intlk04.pdl.

Engineer FAQ

Why does clicking ESVG do nothing in WinCC Runtime?

The logged-in user lacks Authorization Level 5 or 6 in WinCC User Administrator, or the block icon attributes Processcontrolling_backup / HigherProcesscontrolling_backup are misconfigured.

What are Processcontrolling_backup and HigherProcesscontrolling_backup?

They are dynamic string/integer attributes on CEMAT block icons used to transfer instance-specific authorization levels from the process graphic to the opened faceplate.

Which WinCC screen displays the C_INTER5 interlock?

The screen @PG_C_INTER5.pdl (with @PG_C_INTER5_DIAG.pdl for extended diagnostics) is used to display the 5-signal interlock interface.

How do I update CEMAT faceplates across all client stations?

Deploy the updated GraCS files to the master OS Server project, recompile server data, and run project duplication or OS Client download.

Can an operator bypass interlocks from the C_INTER5 faceplate?

Only if the user possesses Higher Process Controlling privileges and interlock simulation/bypass is explicitly enabled via block parameterization in CFC.

What if the interlock button is grayed out completely?

If the button is grayed out, no interlock block is interconnected to the corresponding pin (e.g., ESVG is connected to a static constant or left open).

Does regenerating WinCC headers require stopping Runtime?

Regenerating headers in Global Script C can be done while Runtime is active, but reopening the faceplate is necessary to reload cached scripts.

Can C_INTER5 be used with non-CEMAT blocks?

C_INTER5 is designed for the CEMAT ecosystem; standard PCS 7 projects without CEMAT should utilize APL blocks Intlk02, Intlk04, or Intlk08.

Why did this issue appear only after upgrading from V7.1?

CEMAT V8.1 introduced modernized faceplate scripts and instance authorization checking that were not enforced in V7.1 legacy OCX controls.

Where are CEMAT WinCC script errors logged?

Runtime script errors are recorded in the WinCC diagnostic file C:\Program Files (x86)\Siemens\WinCC\Diagnostics\WinCC_Sys_*.log.

Technical References

Related Articles

Related Tags

  • CEMAT V8.1
  • C_INTER5
  • C_DRV_1D
  • WinCC User Administrator
  • Faceplate Navigation
  • Processcontrolling_backup
  • WinCC GraCS
20 respuestas