Troubleshooting CEMAT V9.0 Faceplate Display and Script Failures in PCS 7
CEMAT V9.0 faceplate display and script errors in SIMATIC PCS 7 typically result from missing OCX component registration, out-of-sync CEMAT master typicals, or operating system user permission restrictions in WinCC. To resolve these failures, re-register the CEMAT ActiveX controls using the 'regsvr32' utility on all CEMAT OCX files in the WinCC 'bin' directory, execute the OS Project Editor to update standard CEMAT picture layouts, and verify that the Windows operator user belongs to the local 'SIMATIC HMI' security group.
Table of Contents
- Executive Summary
- Architecture and Fundamental Mechanics
- Step-by-Step Implementation Procedure
- Verification
- Limitations and Operational Precautions
- Engineer FAQ
- Technical References
- Related Articles
- Related Tags
Executive Summary
SIMATIC PCS 7 CEMAT is the specialized Siemens industry solution for cement, mining, and bulk material handling plants, providing tailored technological blocks (e.g., C_DRV_1D, C_DRV_2D, C_DAMPER) and high-density faceplates. When upgrading or commissioning PCS 7 V9.0 with CEMAT V9.0, engineers frequently encounter faceplate initialization errors—such as blank pop-ups, 'ActiveX control cannot be loaded' warnings, or C-script error dialogs. This guide provides the diagnostic methodology and recovery procedures to restore CEMAT V9.0 faceplates.
Architecture and Fundamental Mechanics
CEMAT Faceplate Architecture and WinCC Integration:
- Architecture of CEMAT V9.0 Faceplates:
- Unlike standard APL faceplates which rely heavily on modern .NET and XML frameworks, CEMAT incorporates proprietary ActiveX controls (OCX) and intensive C-script functions (
C_*.c) for high-speed multi-drive interlock tracking. - CEMAT faceplates interact with global project headers located in
<ProjectDir>\GraCS\C_*.pdl. - Common Root Causes of Failure:
1. Unregistered OCX Controls: If the CEMAT client installation failed to register the required ActiveX files in the Windows registry, WinCC Graphics Designer and Runtime cannot instantiate the faceplate controls.
2. Stale Master Pictures: If the OS Project Editor was not run after installing CEMAT, standard@screen.pdllayouts will conflict with CEMAT header layouts.
3. Multi-Monitor Layouts: CEMAT requires explicit monitor resolution profiles configured via the CEMAT Project Editor.
Step-by-Step Implementation Procedure
Step-by-Step Procedure to Restore CEMAT V9.0 Faceplates:
- Re-Register CEMAT ActiveX Controls:
- Open an elevated Windows Command Prompt (Run as Administrator).
- Navigate to the Siemens WinCC bin directory:cd C:\Program Files (x86)\Siemens\WinCC\bin.
- Run:regsvr32 Cemat*.ocx(or register specific controls:regsvr32 J_*.ocx).
- Confirm that Windows reports 'DllRegisterServer succeeded'. - Update Master Graphics via OS Project Editor:
- Open WinCC Explorer on the OS project.
- Launch OS Project Editor.
- Select the CEMAT configuration profile matching your screen resolution.
- Click OK to overwrite default@pictures with CEMAT V9.0 master templates. - Recompile CEMAT C-Scripts:
- In WinCC Explorer, open Global Script -> C-Editor.
- Click Options -> Regenerate Header.
- Select Compile all functions; verify zero compilation syntax errors. - Verify Windows Security Group Memberships:
- Ensure the logged-in Windows user belongs toSIMATIC HMIandAdministrators. - Restart WinCC Runtime and Test Faceplates:
- Deactivate and reactivate WinCC Runtime.
- Click a CEMAT motor block icon; confirm the faceplate opens with complete interlock and diagnostic tabs.
Verification
To verify CEMAT faceplate operation:
1. Click a CEMAT technological object (e.g., C_DRV_1D); verify the faceplate opens within 1 second without Windows script error prompts.
2. Navigate through the faceplate tabs: 'Diagnostics', 'Interlocks', and 'Parameters'; confirm dynamic tag values update.
3. Check the WinCC diagnostic file (WinCC_Sys_01.log) for any lingering ActiveX instantiation errors.
Limitations and Operational Precautions
Operational precautions:
- Never mix CEMAT library versions (e.g., CEMAT V8.0 faceplates with CEMAT V9.0 PLC blocks); CEMAT interfaces are strictly version-dependent.
- Ensure that Web Navigator clients have the CEMAT Web plugins installed if remote web viewing is utilized.
- Always back up custom process graphics before running the OS Project Editor, as standard typicals may be refreshed.
Engineer FAQ
What causes ActiveX errors when opening CEMAT faceplates?
Unregistered CEMAT OCX files in Windows or missing administrator permissions during installation.
How do I re-register CEMAT ActiveX controls?
Open an administrative command prompt in WinCC\bin and run regsvr32 on the respective CEMAT OCX files.
What tool updates CEMAT screen layouts?
The OS Project Editor in WinCC Explorer.
Is CEMAT part of the standard PCS 7 distribution?
No, CEMAT is a specialized add-on industry package for cement and mineral processing requiring dedicated licensing.
What block family represents CEMAT drives?
The C_DRV_1D (unidirectional drive) and C_DRV_2D (bidirectional drive) blocks.
Technical References
- SIMATIC PCS 7 CEMAT V9.0 Engineering and Operations Manual
- WinCC V7.5 / PCS 7 OS Configuration Manual
- PCS 7 V9.0 SP3 Licenses and Configuration Limits
Related Articles
- Resolving Password Lockouts on OS Projects and Siemens Libraries in SIMATIC PCS 7
- Preventing OS Compile from Overwriting Custom Dynamic Dialogs on PCS 7 Block Icons
- Software Upgrade Strategy and Licensing Requirements for Migrating PCS 7 V8.1 to V9.0
Related Tags
- CEMAT V9.0
- CEMAT Faceplate
- ActiveX OCX
- OS Project Editor
- Global Script