Configuring CEMAT C_GROUP Faceplate Distribution and OCX Registration Across OS Clients

When migrating a legacy SIMATIC PCS 7 CEMAT system (such as CEMAT V6.0 to V8.0) where the group faceplate C_GROUP displays properly on the Engineering Station and OS Server but fails to render on OS Client stations, the issue stems from missing local client ActiveX registration, absent graphic picture templates (@PG_C_GROUP.PDL) in the client cache, or improper DCOM launch permissions. Because CEMAT group faceplates utilize specialized Windows COM controls (C_GROUP.OCX), the control must be physically registered on each OS Client station using the 32-bit regsvr32 utility in C:\Windows\SysWOW64\. Furthermore, ensure that the CEMAT bitmap folder (C_BM) and language configuration files (C_CONFIG.CFG) are copied to the client station and that server packages are refreshed.

ActiveX Controls and Graphics Distribution in CEMAT Architecture

In industrial cement installations running SIMATIC PCS 7 CEMAT, supervisory operations depend heavily on the C_GROUP faceplate. The group faceplate coordinates complex interlocking rules, drives, dampers, and routes. Unlike standard Advanced Process Library faceplates that rely exclusively on WinCC native graphic primitives, CEMAT group faceplates embed the C_GROUP ActiveX Control.

When migrating an older V6.0 project across multiple software generations into V8.0, engineers often copy the Multiproject and recompile the OS Server, verifying that the faceplates work locally on the ES and Server. However, in a distributed client-server architecture, OS Clients do not automatically inherit operating system registry keys from the server. If the client station has not been explicitly configured with the CEMAT client files, the client's WinCC graphics engine encounters an unresolvable COM Class ID, suppressing the faceplate display.

32-Bit OCX Registration on 64-Bit Operating Systems (SysWOW64)

A frequent technical pitfall on modern 64-bit Windows operating systems (Windows 7 / Windows 10) involves how ActiveX controls are registered. Because WinCC Runtime is a 32-bit application, all CEMAT OCX controls must be registered using the 32-bit regsvr32.exe binary located in C:\Windows\SysWOW64\:

Windows File / ToolLocationArchitecturePurpose in CEMAT Client Deployment32-Bit Regsvr32C:\Windows\SysWOW64\regsvr32.exe32-Bit SubsystemMandatory: Registers C_GROUP.OCX for WinCC 32-bit runtime64-Bit Regsvr32C:\Windows\System32\regsvr32.exe64-Bit NativeDefault Windows tool; fails to register 32-bit ActiveX for WinCCC_GROUP.OCXC:\CEMAT_CS\BIN\C_GROUP.OCX32-Bit COM ControlThe core compiled ActiveX control for group diagnosticsC_CONFIG.CFGC:\CEMAT_CS\CONFIG\C_CONFIG.CFGText ConfigurationDefines color codes, group button actions, and language stringsBitmap LibraryC:\CEMAT_CS\BM\Graphic Icons (.bmp/.emf)Renders motor, valve, and group state indicators on faceplates

Running regsvr32 from a standard 64-bit command prompt without specifying SysWOW64 registers the control into the 64-bit registry hive, leaving 32-bit WinCC completely unable to locate the object.

Step-by-Step Procedure to Distribute Bitmaps, Configs, and Templates

To ensure 100% reliable group faceplate operation on all OS Clients, execute this deployment checklist:

Deploy CEMAT Directory Structure to OS Client: On the OS Client, create the directory C:\CEMAT_CS\. Copy the BIN, BM, and CONFIG subfolders from the Engineering Station or CEMAT DVD.
Register OCX in 32-Bit Subsystem:
- Open Command Prompt as Administrator.
- Execute: cd C:\Windows\SysWOW64
- Execute: regsvr32.exe C:\CEMAT_CS\BIN\C_GROUP.OCX
- Confirm the registration success popup appears.
Synchronize Graphic Templates: In SIMATIC Manager on the ES, verify that all @PG_C_*.PDL pictures are present in the Master Data Library and OS project GraCS folders. Perform an OS Compile.
Re-Generate Server Data Package: On the OS Server in WinCC Explorer, right-click Server Data and select Generate. On the OS Client, right-click the server package in Server Data and select Update.
Restart WinCC Runtime: Deactivate and reactivate WinCC Runtime on the OS Client.

Verification

Confirm that the C_GROUP faceplate operates reliably across all clients using these checks:

Registry Verification: Inspect HKEY_CLASSES_ROOT\TypeLib in the Windows registry using regedit. Confirm that the type library for C_GROUP is registered and references C:\CEMAT_CS\BIN\C_GROUP.OCX.
Faceplate Interaction Test: In WinCC Runtime on the OS Client, click a group block icon. Confirm that the group faceplate window pops up immediately with complete button controls.
Diagnostic Sub-Screen Test: In the group faceplate, open the 'Object List' and 'Interlocks' tabs. Confirm that all associated equipment blocks are populated with live dynamic status.

Limitations and Operational Precautions

When managing CEMAT client-server systems, observe these guidelines:

Administrative Rights for Registration: Registering ActiveX controls requires local administrator rights on the client PC. Standard domain user accounts cannot write to HKEY_CLASSES_ROOT.
Path Consistency: Ensure the physical installation path for CEMAT files (C:\CEMAT_CS\) is identical across all engineering stations, servers, and clients to prevent hardcoded C-script path errors.
Commercial Procurement and Licensing Disclaimer: Verify that every operational OS Client possesses a valid CEMAT Client runtime license key (A1CEMC..). Operating clients without proper license keys violates licensing terms and may cause runtime popups.

Engineer FAQ

Why must I use SysWOW64 regsvr32 instead of the standard regsvr32?

WinCC is a 32-bit application. On 64-bit Windows, standard regsvr32 in System32 registers 64-bit DLLs. You must use C:\Windows\SysWOW64\regsvr32.exe to register 32-bit ActiveX controls for WinCC.

Do I need to copy the entire WinCC project to each OS Client?

No. An OS Client operates as a reference client reading server data packages. It only requires local CEMAT support files (C:\CEMAT_CS), local registry keys, and its client .mcp shell.

What happens if C_CONFIG.CFG is missing on the client?

The faceplate may open, but buttons will lack descriptive text labels, color codes will default to gray, and custom interlock descriptions will fail to display.