Troubleshoot PCS 7 Logic Matrix Generation After Importing an Existing Matrix

Before generating an imported PCS 7 Logic Matrix, verify that the import file is compatible with the installed Logic Matrix version and that every cause, effect, and intersection is complete. In Logic Matrix V9.1, Siemens documents that older-version .ods files cannot be imported and that Generate Matrix reports incomplete links. Import and regeneration can replace matrix logic and generated CFC blocks, so back up the project and review the Intersection DB setting first. The source omits its version and error details, so the exact failure remains unconfirmed.

Applies To and Import Type

This guidance applies when an existing PCS 7 Logic Matrix is imported from an exported .ods file and the Logic Matrix cannot be generated. The source does not say whether “import” means an .ods file, an existing project object, or a matrix from another Logic Matrix release, and it supplies no error dialog or version. Confirm that distinction before changing the matrix.

Siemens' Logic Matrix V9.1 manual states that an .ods file exported from an older Logic Matrix version cannot be imported into V9.1. Siemens' V9.0 SP2 and V9.1 manuals also warn that importing replaces the open matrix's interlock logic; its next generation replaces CFC blocks, and manual CFC adaptations can be lost.

Check the Imported Matrix

Record the PCS 7 and Logic Matrix versions, the source matrix/file format and version, and the exact generation message. Preserve the project and matrix file before importing or regenerating.
If using Logic Matrix V9.1, confirm that the .ods file was exported by a compatible Logic Matrix version. An .ods from an older version is explicitly unsupported for import into V9.1; do not treat hand-adding rows as a general compatibility repair.
Open the imported matrix and inspect the imported Cause, Effect, and Intersections data. Confirm causes and effects are still present and their interconnections refer to existing entries. Siemens' V9.1 generation check identifies three incomplete conditions: causes without an interconnection, effects without an interconnection, and interconnections without a cause and/or effect.
Select Generate > Generate Matrix. If the “Incomplete Matrix Configuration” dialog appears, review its listed causes, effects and interconnections. Cancel generation to return to the editor and correct the actual incomplete entries; do not continue generation merely to dismiss the warning.
After the matrix passes the configuration check, verify the generation dialog's Hierarchy, Number of startup cycles, Cycle time, OS block icons, and Intersection DB settings. Siemens warns that the Intersection DB must be in the user area; otherwise generation can overwrite parts of the PCS 7 program, such as instance DBs.
For an existing generated matrix CFC, use Read back CFC when the goal is to read back changes from the existing Matrix CFC. Do not delete the CFC unless the project backup and change plan support regeneration. The manual documents Delete CFC as an available option, but import/regeneration can replace generated blocks and discard manual adaptations.
Generate and review the matrix CFC and OS description output in the engineering project. Compile the affected S7 program and OS as required by the change, then verify behavior under the site's approved test procedure before any download.

Why Manual Rows May Appear to Help

Adding a cause, effect or intersection manually may resolve one of the incomplete-configuration cases if the imported matrix lacks that required relationship. It does not establish that the .ods file is compatible, that all input/output references are valid, or that the chosen logic is correct. Preserve the imported file and compare its contents with the intended matrix design before adding or deleting logic.

Expected Result

A complete, compatible matrix passes the generation validity check and opens the Generate Matrix settings dialog. Generation then creates the matrix CFC and OS description file in the project. The source says manual additions only “seem to work so far”; it does not report a completed compile or operational verification.

Verification

Review the generated CFC for the intended causes, effects, and links, and inspect compiler messages. If causes/effects were added or deleted, Siemens' manual states that the OS must be compiled for the change to take effect at the stations. Verify cause activation and resulting effects in an approved test or simulation appropriate to the project, without claiming that the source's partial observation is a successful test.

Limitations and Operational Precautions

The ticket omits the Logic Matrix version, import format, exact error, matrix contents, and generated CFC state. The V9.1 .ods compatibility rule is applicable only if the project uses Logic Matrix V9.1 and imports an older-version .ods file. Use the documentation matching the installed release.

Import and regeneration replace interlock logic and generated CFC blocks; manual adaptations can be lost. A wrong Intersection DB number can overwrite other program data. Back up the project, review the DB setting and output, and follow site review, compile, download and rollback controls. Keep project transfer, compile, and CPU download as separate operations.

Engineer FAQ

What makes an imported matrix incomplete in Logic Matrix V9.1? Siemens lists causes without an interconnection, effects without an interconnection, and interconnections without a cause and/or effect.

Can Logic Matrix V9.1 import an .ods file exported by an older Logic Matrix version? The V9.1 manual says no; older-version .ods files cannot be imported to a newer version.

Does generating after import preserve manual changes in the matrix CFC? No. The manual warns that the next generation replaces CFC blocks, so manual adaptations can be lost.

Technical References

Siemens, Logic Matrix V9.1, Configuration Manual, sections 7.9.3 “Importing a Logic Matrix file (.ods)” and 8.1 “Transferring the Logic Matrix to the project,” document A5E49951559-AA. https://cache.industry.siemens.com/dl/files/041/109794041/att_1056145/v1/p7lm91b_en-US.pdf
Siemens, Logic Matrix V9.0 SP2, Configuration Manual, sections 7.8.3 “Importing a Logic Matrix file (.ods)” and 8.1 “Transferring the Logic Matrix to the project,” document A5E35886614-AA. https://cache.industry.siemens.com/dl/files/564/109767564/att_986480/v1/P7LM90b_en-US.pdf

Related Tags

PCS 7, Logic Matrix, LM, ODS import, matrix generation, CFC, cause and effect, Intersection DB

Troubleshoot PCS 7 Logic Matrix Generation After Importing an Existing Matrix