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

How to Troubleshoot Unresponsive or Unclickable CEMAT V8 Block Icons in WinCC Runtime

How to Troubleshoot Unresponsive or Unclickable CEMAT V8 Block Icons in WinCC Runtime

To resolve unresponsive or unclickable CEMAT V8 block icons (such as Drives C_DRV_1D, C_DRV_2D, or Groups C_GROUP) in WinCC Runtime, engineers must verify script initialization, operator authorizations, and OS project settings. CEMAT utilizes specialized C-functions (e.g., C_DRV_1D.fct) and custom WinCC faceplate scripts. If block icons appear on screen but ignore mouse clicks, the root cause is typically missing CEMAT project functions in the OS project directory, failure to execute the CEMAT OS Project Editor, or missing CEMAT User Authorizations (e.g., Authorization 101/102 for operation, 103 for interlocks). Running the CEMAT Project Update wizard, recompiling the OS, and assigning appropriate user rights in WinCC User Administrator restores normal faceplate invocation.

Table of Contents

Architecture of CEMAT V8 Block Icons and Faceplates

CEMAT (Cement Automation Technology) is the dedicated Siemens process control library for the cement, mining, and minerals industries.

Unlike standard Advanced Process Library (APL) blocks, CEMAT blocks—such as unidirectional drives (C_DRV_1D), bidirectional drives (C_DRV_2D), dampers (C_DAMPER), and group control modules (C_GROUP)—rely on an extensive industry-specific visualization architecture:
1. Dynamic Block Icons: Placed on .pdl process pictures, representing operating status (running, faulted, local mode, interlocked).
2. Standard and Diagnostic Faceplates: Invoked via mouse click on the block icon, rendered through template pictures (e.g., @PG_C_DRV_1D.pdl).
3. C-Project Functions and Script Scripts: Hundreds of specialized C-functions (.fct files located in <Project_Dir>\Library) that evaluate interlocks, calculate runtime hours, and manage operator commands.

Root Causes Behind Unclickable CEMAT Icons in Runtime

When CEMAT block icons render on screen but fail to open faceplates or respond to clicks:

1. Missing or Uncompiled CEMAT C-Scripts

If the CEMAT OS update utility was not executed following project migration or new OS creation, the required C-functions (C_*.fct) are missing from the OS project's Library directory. Clicking the block icon triggers an invisible C-script execution failure.

2. Missing User Authorization Levels

CEMAT enforces strict multi-level authorization:
* Authorization 101: Drive operation (Start, Stop, Local/Remote).
* Authorization 102: Group / Route operation.
* Authorization 103: Interlock override and bypass.
If the logged-on user does not possess Authorization 101/102, CEMAT scripts suppress the mouse-click event completely.

3. Transparent Layers or Group Object Overlays

If process graphics were developed with transparent rectangle overlays or if block icons were grouped with static drawing objects, the parent group absorbs mouse events, preventing the embedded CEMAT icon from receiving the click trigger.

4. Incomplete OS Compilation and Structure Tag Generation

If the OS was not compiled after placing CEMAT blocks in CFC, WinCC Tag Management lacks the internal structure tags required to instantiate faceplate variables.

Step-by-Step Resolution: CEMAT Project Update and Script Deployment

Follow this engineering sequence to restore CEMAT block icon responsiveness:

Step 1: Run CEMAT OS Project Editor and Update Utility

  1. Close WinCC Explorer on the Engineering Station.
  2. In Windows Start Menu, locate Siemens Automation -> SIMATIC -> CEMAT -> CEMAT OS Project Editor (or run the CEMAT Update tool).
  3. Select your WinCC OS project.
  4. Execute the update: This automatically copies the latest CEMAT template screens (@PG_C_*.pdl), bitmaps, and C-functions into <Project_Dir>\GraCS and <Project_Dir>\Library.

Step 2: Regenerate Header Files in WinCC Graphics Designer

  1. Open WinCC Explorer on the OS.
  2. Open Global Script -> C-Editor.
  3. In the menu bar, execute Options -> Generate Header.
  4. This recompiles all CEMAT project functions and updates internal symbol bindings.

Step 3: Recompile the OS in SIMATIC Manager

  1. In SIMATIC Manager, right-click the OS object -> Compile.
  2. Select Entire OS (or changes only if structure types already exist).
  3. Ensure tag connections and message structures are generated cleanly.

Configuring CEMAT User Authorizations in WinCC User Administrator

To ensure operators have authorization to open faceplates:

  1. In WinCC Explorer, open the User Administrator editor.
  2. Under the active user group (e.g., Operators or Engineers):
    * Verify that Authorization Level 101 ('Drive Operations') is enabled.
    * Verify that Authorization Level 102 ('Group Operations') is enabled.
    * Verify that Authorization Level 103 ('Interlock Operations') is enabled for supervisory personnel.
  3. If authorization numbers are blank, import the standard CEMAT user rights profile (CEMAT_User.usr).
  4. Save the configuration and verify logon in WinCC Runtime.

CEMAT Block Icon and Faceplate Diagnostic Matrix

The following table outlines the diagnostic symptoms, causes, and corrective actions for CEMAT runtime blocks:

Symptom / ObservationRoot CauseDiagnostic File / ToolCorrective ActionIcon visible; click does nothingMissing C-functions or missing Auth 101WinCC_Sys_01.log (AP_ERROR)Generate Headers; assign Auth 101 in User AdminFaceplate opens with 'Tag not found'Incomplete OS compilationWinCC Tag ManagementRecompile OS from SIMATIC ManagerMouse cursor does not change to handLayer overlay or group object blockingGraphics Designer Object PropertiesBring block icon to front; un-group objectIcon shows black square or question markMissing CEMAT bitmaps in GraCS<Project>\GraCS directoryRe-run CEMAT OS Update tool to restore bitmapsCommands rejected with security popupCurrent user lacks operating levelWinCC Alarm Logging / Event LogLog on with authorized maintenance credentials

Proper script compilation and user entitlement ensure responsive mineral processing operations.

Verification

To verify that CEMAT block icons are fully operational:
1. Activate WinCC Runtime and log in with an operator account possessing Authorization 101/102.
2. Hover over a drive (C_DRV_1D) or group (C_GROUP) block icon; confirm that the cursor changes to an active interaction pointer.
3. Left-click the block icon; verify that the standard CEMAT faceplate opens immediately (< 1 second).
4. Verify that drive status, current feedback, running hours, and interlock lines display valid process data.
5. Test commanding the block into Local or Manual mode to verify command execution.

Limitations and Operational Precautions

  • Never mix CEMAT library versions (e.g., CEMAT V7.x blocks with CEMAT V8.x faceplates); library versions must match across AS controllers and OS servers.
  • Do not manually rename auto-generated CEMAT C-script functions; renaming breaks internal dynamic wizard bindings.
  • Ensure all client workstations have the same screen resolution configured to prevent CEMAT faceplate clipping.
  • Always validate final license quantities, module availability, and MLFBs against the applicable Siemens catalog and authorized distributor quotation.

Engineer FAQ

Why does CEMAT require custom user authorizations like Level 101?

CEMAT uses dedicated authorization levels (101 to 120) to enforce strict plant security in heavy industry, distinguishing basic drive operations from group sequencing and interlock bypasses.

Can I use standard PCS 7 APL block icons alongside CEMAT block icons?

Yes, but they operate through different graphic engines and script sets. CEMAT projects typically use CEMAT blocks exclusively for plant consistency.

Where can I find the AP_ERROR logs if a C-script fails?

C-script execution errors are recorded in C:\Program Files (x86)\Siemens\WinCC\Diagnose\WinCC_Sys_01.log and the AP_ERROR trace window.

Technical References

Related Articles

Related Tags

  • CEMAT V8
  • C_DRV_1D
  • C_GROUP
  • Block Icons
  • User Authorization 101
6 respuestas