Troubleshooting CEMAT V8 C_INTERL Faceplate Open Failures and Split Screen Manager Errors

In SIMATIC PCS 7 with CEMAT V8, clicking the interlock button (EEVG) on an equipment diagnostic faceplate failing to open the interlock window and generating the script error 'C_ShowInterlock: SSMRTOpenTopField failed: Split Screen Manager: Invalid Picturename' indicates that the Split Screen Manager cannot find the required CEMAT interlock faceplate picture file (@PG_C_INTERL.pdl or @PG_C_INTER_OVERVIEW.pdl) in the local WinCC project GraCS folder, or that the interlock block parameter interconnection is blank. To resolve this, copy the master CEMAT faceplate templates from the CEMAT installation directory into the WinCC OS project GraCS folder, verify the interlock block type, and compile the OS.

CEMAT V8 Interlock Architecture and Split Screen Manager Integration

In the Siemens CEMAT cement and mining library for SIMATIC PCS 7:
* Interlock Blocks (C_INTERL, C_INTER5): Technological blocks that evaluate up to 10 binary interlock conditions with individual bypass, override, and first-in fault detection.
* Equipment Linkage: Drives (C_DRV_1D, C_DRV_2D) connect to interlock blocks via interlock pointers (IntStart, IntOper, IntProt).
* Split Screen Manager (SSM): When an operator clicks an interlock status button (EEVG, EBVG, ESVG) in the drive diagnostic picture, CEMAT executes ANSI-C function C_ShowInterlock().
* The script calls the PCS 7 Split Screen Manager API SSMRTOpenTopField() to display the interlock popup faceplate (@PG_C_INTERL.pdl).

Root Causes of 'SSMRTOpenTopField Failed: Invalid Picturename'

When clicking the interlock button fails with this specific error:
1. Missing Master Picture in GraCS: During OS project creation or migration from CEMAT V7 to V8, the CEMAT master screen templates were not copied from C:\CEMAT_CS\WinCC\GraCS\ into the active WinCC project GraCS directory. Split Screen Manager cannot locate @PG_C_INTERL.pdl.
2. Unconnected or Blank Interlock Parameter: In the AS CFC chart, if the drive block's interlock input is connected to an un-compiled signal or left unassigned while having the interlock display attribute active, the C-script receives an empty tag name, passing an empty picture string to SSM.
3. OS Project Editor Overwrite: Running the WinCC OS Project Editor can overwrite custom CEMAT screen management scripts with standard PCS 7 scripts if CEMAT options are not selected.

Remediation Procedure - Deploying CEMAT Faceplate Templates and Picture Verification

Follow this procedure to restore CEMAT interlock faceplate functionality:

[Phase 1: Copy CEMAT Master Pictures to WinCC Project GraCS]
   │  • On the Engineering Station: Locate CEMAT installation folder:
   │      C:\CEMAT_CS\WinCC\GraCS   │  • Copy the following core interlock template pictures:
   │      - @PG_C_INTERL.pdl
   │      - @PG_C_INTERL_OVERVIEW.pdl
   │      - @PG_C_INTER5.pdl
   │      - @PL_C_INTERL.pdl
   │  • Paste them directly into your WinCC OS project folder:
   │      <Multiproject_Path>\<OS_Project_Name>\GraCS   │
[Phase 2: Verify CFC Interlock Block Interconnection]
   │  • In CFC, open the chart containing the drive (e.g. C_DRV_1D)
   │  • Check inputs: IntStart, IntOper, IntProt
   │  • Verify that they connect to a valid C_INTERL or C_INTER5 block output
   │  • Ensure the C_INTERL block instance has "OCM possible" enabled
   │
[Phase 3: Compile OS and Propagate to Clients]
   │  • In SIMATIC Manager: Right-click OS -> "Compile" (Scope: Tags and messages)
   │  • For distributed client systems:
   │      Ensure the GraCS folder on OS Clients or Server is fully synchronized!

CEMAT Faceplate Diagnostic and Script Error Matrix

Evaluate script errors reported in the WinCC Application Diagnostics window:

Script Diagnostic ErrorRoot CauseTarget Picture RequiredCorrective ActionSSMRTOpenTopField failed: Invalid PicturenameMaster faceplate missing in GraCS@PG_C_INTERL.pdlCopy template file from CEMAT_CS\WinCC\GraCS.C_ShowInterlock: Block tag not foundDrive interlock input unassigned in CFCNone (CFC parameter)Interconnect drive interlock pin to C_INTERL.Out.C_ShowInterlock: Permission DeniedLogged-on user lacks CEMAT operator levelNone (User Admin)Grant authorization level 5/6 in User Administrator.CEMAT Object not found in Picture TreePicture not assigned in Plant View@Area_Top.pdlRun Picture Tree Manager recalculation.

Verification

To confirm that the CEMAT interlock faceplate functions correctly:
1. In WinCC Runtime, open the equipment process picture and click the drive block icon.
2. In the drive faceplate, click the Diagn button to open the diagnostic window.
3. Click the EEVG (Interlock Start) button.
4. Verify that the interlock faceplate @PG_C_INTERL.pdl opens immediately in the upper screen container.
5. Confirm that all 10 interlock inputs display live dynamic statuses with green/red signal bars and descriptive bypass buttons.

Limitations and Operational Precautions

Never modify default CEMAT C-scripts directly in CEMAT_CS master directories. If customizing interlock faceplate dimensions or text alignments, modify the file within the project's local GraCS directory. When upgrading CEMAT versions (e.g. v8.0 to v8.1), always run the official CEMAT project update tool (CEMAT Update Utility) to migrate SQL database schemas and faceplate structures safely.

Engineer FAQ

What does the EEVG button represent in CEMAT?

EEVG stands for 'Einschalt-Verriegelung' (Start Interlock). It represents interlock conditions required to permit starting equipment.

Where are CEMAT diagnostic script errors logged?

They are displayed in the WinCC Application Window (APPLVIEW) and logged in C:\Program Files (x86)\Siemens\WinCC\Diagnostics\ in files WinCC_Sys_01.log and cemat.log.

Why did the interlock faceplate fail after running OS Project Editor?

OS Project Editor restores standard Siemens PCS 7 scripts. After running OS Project Editor on a CEMAT project, you must re-run the CEMAT GraCS delivery script to restore CEMAT-specific scripts.

Can C_INTERL be connected to standard APL blocks?

While technically possible via structure converters, CEMAT blocks are optimized to work with CEMAT drives (C_DRV_1D, C_VALVE) to preserve native first-out diagnostic logging.