Troubleshoot Empty Safety Matrix Causes and Effects in PCS 7 V9.0 SP3
When a Safety Matrix faceplate in PCS 7 V9.0 SP3 shows alarms but no causes or effects, check the complete Safety Matrix and S7 F Systems update levels and trace the generated OS data. Siemens lists Safety Matrix V6.2 SP2 Upd2 and S7 F Systems V6.2 Upd1 among tested versions. That compatibility evidence supports checking the reported base F Systems V6.2 installation, but it does not establish an update as a proven cure for the missing rows and columns.
Table of Contents
- Distinguish Compilation from Runtime Completeness
- Check Safety Matrix and F Systems Independently
- Trace Where the Cause and Effect Data Disappear
- Verification
- Limitations and Operational Precautions
- Engineer FAQ
- Technical References
- Related Articles
- Related Tags
Distinguish Compilation from Runtime Completeness
The affected system uses a redundant CPU 414-5H, ET 200M standard and fail-safe I/O, and Windows 10 Enterprise 2015 LTSB. Matrix transfer and compilation succeed, yet the Runtime faceplate shows alarms without its cause rows and effect columns.
An older PCS 7 V8.2 project reportedly displays the matrix before recompilation in the newer environment, while regenerating CFC/OS data leaves expected tags absent. This is a useful diagnostic distinction between retained project content and newly generated content. It does not prove the compiler defect, the exact missing tag names or a particular repair.
Check Safety Matrix and F Systems Independently
Do not stop at the parent PCS 7 version. Record the complete versions of Safety Matrix, S7 F Systems, the engineering tools and the installed OS components.
The opened PCS 7 V9.0 SP3 UC06 Readme, section 5.19, explicitly lists Safety Matrix V6.2 SP2 Upd2 and S7 F Systems V6.2 Upd1 among versions tested with PCS 7 V9.0 SP3. Its operating-system tables include Windows 10 Enterprise 2015 LTSB for those versions. This verifies the relevance of the update level; it does not guarantee that installing an update will restore missing faceplate content. Siemens readme, pp. 75–76
In the reported configuration, the Safety Matrix installation was clarified as V6.2 SP2 Upd2, while S7 F Systems was V6.2. A recommendation to update Safety Matrix from an assumed base SP2 installation therefore misses that clarification. The unresolved comparison is the actual F Systems update level and the rest of the supported component combination.
Trace Where the Cause and Effect Data Disappear
Perform the following project-specific diagnostic comparison on a preserved copy:
- Record which matrix displays correctly before regeneration and capture its cause/effect structure.
- Record the installed component versions before making any software changes.
- Retain the matrix transfer, CFC compilation and OS compilation results separately. A successful step must not be treated as proof that every later artifact exists.
- Compare the relevant generated OS tags and faceplate references before and after compilation, using the actual project names. The absent screenshot does not provide a reliable list to reproduce here.
- After establishing the supported component combination, reproduce the generation sequence in an isolated engineering environment and compare the same artifacts again.
The expected diagnostic result is a specific stage where content or references diverge, rather than a conclusion based only on whether Runtime starts.
Verification
For each matrix, verify that the intended cause rows, effect columns and associated indications appear in Runtime and correspond to the engineered matrix. Confirm tag-reference validity and normal communication independently of alarm visibility.
If a component update is introduced, repeat the same comparison and retain the generated results. A version change, a successful compilation or alarms appearing in the faceplate alone does not prove that the full matrix visualization has been restored.
Limitations and Operational Precautions
No confirmed final recovery was reported. The exact absent tags and the causal link to S7 F Systems V6.2 were not independently established. This remains a visualization/generation investigation, not an instruction to alter the safety application.
Use the readme edition applicable to the installed UpdateCollection and the product's safety lifecycle requirements before installing or converting components. Preserve the engineering project, validated safety records and a recovery path. Do not download changed safety logic solely to test a faceplate display hypothesis, and do not equate a repaired display with validation of the safety functions.
Engineer FAQ
Is Safety Matrix V6.2 SP2 Upd2 listed for PCS 7 V9.0 SP3?
Yes, in the opened UC06 readme. Confirm the complete installed combination and the applicable edition.
Does that compatibility listing prove the missing rows are an F Systems bug?
No. It establishes tested versions, not the cause or successful repair of this particular symptom.
Technical References
- Siemens — PCS 7 Readme V9.0 SP3 UC06 (online), A5E49978550-AH, section 5.19, pp. 75–76 — tested Safety Matrix/F Systems versions and operating-system applicability. Earlier editions used different section numbering.