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

Resolving Safety Matrix Viewer Runtime Crashes and Faceplate Initialization Errors on PCS 7 OS Clients

Resolving Safety Matrix Viewer Runtime Crashes and Faceplate Initialization Errors on PCS 7 OS Clients

In SIMATIC PCS 7 multi-user systems with S7 F Systems, when clicking a Safety Matrix faceplate on an OS Client running on non-Siemens commercial PC hardware triggers a runtime application crash, blocks the matrix from opening, and forces a PC restart upon exiting WinCC, the failure is typically caused by unverified Windows 10 build rollups, missing or corrupted Microsoft Visual C++ redistributable packages, missing SIMATIC HMI user group permissions, or unregistered Safety Matrix ActiveX COM libraries (F_SM_Viewer.ocx). To resolve the issue, verify that the OS Client runs an approved Windows 10 LTSC release, reinstall the Safety Matrix Viewer runtime setup with administrative rights, register the Safety Matrix ActiveX components using regsvr32, verify membership in the SIMATIC HMI and SIMATIC NET user groups, and ensure the OS Client has access to the server network share containing the matrix project files.

Table of Contents

Executive Summary

The SIMATIC Safety Matrix provides comprehensive Cause-and-Effect logic engineering, operation, and maintenance within PCS 7 fail-safe environments. While Safety Matrix Viewer faceplates run smoothly on pre-configured Siemens SIMATIC IPC servers, deploying the viewer on customer-supplied commercial office or industrial PCs often introduces stability challenges. Non-IPC computers frequently lack required COM runtime libraries, run unapproved commercial Windows 10 Semi-Annual Channel (SAC) updates, or lack proper local security group assignments. Diagnosing the underlying component registration and permission model ensures stable Safety Matrix visualization across all plant operator clients.

Architecture and Fundamental Mechanics

The client-server visualization architecture of the SIMATIC Safety Matrix relies on multi-layer software dependencies:

  1. The Safety Matrix Viewer ActiveX Container:
    * In WinCC Graphics Designer, the Safety Matrix faceplate invokes an embedded ActiveX control (F_SM_Viewer.ocx and supporting COM DLLs).
    * When an operator clicks a matrix icon in runtime, WinCC instantiates this control, which reads Cause-and-Effect status from both controller tags and the compiled matrix configuration file (.smt).
  2. Operating System and Component Dependencies:
    * The ActiveX viewer relies on specific versions of Microsoft Visual C++ Runtime libraries and Windows COM/DCOM sub-systems.
    * Siemens validates Safety Matrix releases against specific Windows 10 Enterprise LTSC (Long Term Servicing Channel) builds (such as LTSC 2016 or LTSC 2019).
    * Customer-supplied PCs running consumer or corporate Windows 10 SAC that receive automatic Microsoft cumulative monthly rollups frequently suffer broken COM interfaces or altered DCOM security policies.
  3. User Rights and Network Shares:
    * The logged-in Windows operator account must belong to local groups SIMATIC HMI, SIMATIC NET, and Users.
    * The client must have direct network read access to the project share on the OS Server where the matrix files reside. If access is denied, the OCX control encounters an unhandled exception, causing WinCC to freeze or crash.

Step-by-Step Implementation Procedure

Follow these procedures to diagnose, register, and restore Safety Matrix Viewer functionality on the OS Client:

  1. Verify Windows 10 Compatibility:
    * On the OS Client, run winver to check the installed Windows build.
    * Check the Siemens Compatibility Tool for your exact PCS 7 release (e.g., PCS 7 V9.0 SP2 requires Windows 10 Enterprise LTSC 2016 or 2019).
    * If unapproved cumulative updates were applied by corporate IT, roll them back or qualify them.
  2. Check User Group Memberships:
    * Open Windows Computer Management (compmgmt.msc) as Administrator.
    * Navigate to Local Users and Groups > Groups.
    * Verify that the active Windows operator user account is a member of:
    • SIMATIC HMI
    • SIMATIC NET
    • If missing, add the user and restart the computer.
  3. Reinstall Safety Matrix Viewer Software:
    * Insert the official PCS 7 Safety Matrix installation media.
    * Locate the setup executable for SIMATIC Safety Matrix Viewer.
    * Right-click Setup.exe and select Run as Administrator.
    * Select Repair or perform a clean reinstall to ensure all required Visual C++ runtimes and COM components are deployed.
  4. Manually Register Safety Matrix ActiveX Controls:
    * Open an elevated Command Prompt (cmd.exe as Administrator).
    * Navigate to the Safety Matrix installation directory (typically C:/Program Files (x86)/Siemens/SafetyMatrixViewer/bin or C:/Program Files (x86)/Common Files/Siemens/...).
    * Execute registration commands:
    • regsvr32 F_SM_Viewer.ocx
    • regsvr32 F_SM_ViewerCtrl.dll
    • Verify that Windows displays 'DllRegisterServer succeeded' for each file.
  5. Verify Server Package and Network Share Access:
    * On the OS Client, open Windows File Explorer and browse to the network share of the redundant OS Servers.
    * Confirm that the client can read the Safety Matrix files (.smt) in the shared project directory.
    * In WinCC Explorer on the client, verify that Server Data (.pck) is loaded and assigned correctly.

Verification

Launch WinCC Runtime on the OS Client. Navigate to a process graphic containing a Safety Matrix block icon. Click the icon to open the faceplate. Verify that the Safety Matrix Viewer window displays all Cause and Effect matrices with live green/yellow status indications without popup errors. Close the faceplate and exit WinCC Runtime; verify that the runtime shuts down cleanly without triggering Windows application fault dialogs.

Limitations and Operational Precautions

Safety Matrix Viewer requires an active Safety Matrix Viewer runtime license on each OS Client where the viewer is opened. Commercial Windows 10 Home or Pro editions are not supported for PCS 7 OS stations; always utilize Windows 10 Enterprise LTSC.

Engineer FAQ

Does Safety Matrix Viewer require a separate license on OS Clients?

Yes. Each OS Client that displays and operates the Safety Matrix requires a SIMATIC Safety Matrix Viewer Runtime license.

Can Safety Matrix Viewer run on a standard commercial PC?

Yes, provided the hardware and operating system meet Siemens specifications, specifically Windows 10 Enterprise LTSC with proper group permissions.

Why did the server work fine while the client crashed?

Siemens pre-installed IPC servers have validated Windows builds, pre-registered COM libraries, and correct user group configurations out of the box.

What file extension is used by Safety Matrix configuration files?

Safety Matrix files use the .smt file extension and are stored in the project directory.

Technical References

Related Articles

Related Tags

  • Safety Matrix
  • OS Client
  • ActiveX Error
  • Windows 10 LTSC
  • SIMATIC HMI
20 respuestas