Troubleshoot Large CEMAT Periphery Text Files That Will Not Open

CEMAT V9.0 documentation describes per-object text files in the Multimedia\Periphery folder that the Info Dialog opens, but it does not state a maximum file size. The reported PCS 7 9.0/WinCC V7.4 SP1 Update 19 case therefore has no confirmed size-limit fix. Verify the object-to-file association and Multimedia Server path, then compare the failing file with a small known-good file in a test copy. A compile and download was suggested in the reply, but no successful result was reported.

What the Periphery Text File Does

The reported “sidebar” appears to refer to periphery information displayed through a CEMAT faceplate Info Dialog. Siemens' CEMAT V9.0 SP1 reference manual describes one corresponding text file for each object in the Multimedia\Periphery folder and identifies the information as connected I/O details such as card, address and symbolic name. The CEMAT V9.0 SP2 Readme says the text file is opened unmodified from the Info Dialog. These documents describe file association and placement; they do not specify a maximum file size or explain a failure that occurs only when a file is large.

Prerequisites

The source identifies PCS 7 9.0 and WinCC V7.4 SP1 Update 19, but it does not state the exact CEMAT library build, affected object name, file size, encoding, Multimedia Server configuration or whether smaller files still open. Capture those details and a redacted screenshot. Confirm which station is the Multimedia Server and use the CEMAT and PCS 7 documentation for the installed update/build; do not assume that a detail in a later CEMAT revision applies unchanged.

Verify the CEMAT File Association

For CEMAT V9.0 SP1, Siemens documents the C_INFO Info Tool workflow: export PCS 7 engineering data (Hardware Configuration, Symbols table and Process Object View), run C_INFO.xlsm to create C_INFO.csv and per-object text files, import the CSV into user archive C_INFO, and copy the text files to the Multimedia\Periphery folder on the Multimedia Server. Compare the affected object's filename and contents with the corresponding generated output or a known-working object. Do not overwrite a custom periphery document with generated I/O data unless that replacement is intended.

CEMAT V9.0 SP2 Readme documents files named TAG.txt and, for chart/block names containing “/”, Chart_Block.txt with “/” replaced by “_”. Apply this naming detail only if the installed CEMAT version's documentation matches; otherwise follow the installed release's object-to-file mapping.

Isolate the Large-File Behavior

Preserve the original text file and CEMAT project. Record its exact byte size, filename, object association and the station on which it is stored.
In a non-production copy or approved test environment, open the same Info Dialog using a small file already known to work. This checks whether the basic Info Dialog path functions.
Compare a failing large file and a working small file for the same object association and directory, without editing either original. Check whether the Info Dialog opens but clips content, or whether it fails to open at all; these are different symptoms.
If possible, prepare a short test copy containing the beginning and end of the original text, and a reduced copy that retains the original structure. Test only on the copy and retain the original file. This comparison can show whether behavior is associated with file length or particular content, but it does not establish a product limit.
Record the results and provide the exact file to the responsible Siemens/CEMAT support channel using the site's approved private support process. Do not post customer data publicly.

Assess the Compile-and-Download Suggestion

The reply says the responder could not reproduce the issue and suggests compiling and downloading again, then requests the text file for analysis. It does not say that this procedure fixed the original problem or identify why it would address a periphery text-file size issue. Do not treat a download as a universal correction. If a test copy is recompiled or downloaded under an approved plan, record the exact CEMAT/PCS 7 steps and results and verify the operational impact before any live change.

Verification

For each test, confirm the Info Dialog opens the intended object's periphery file from the configured Multimedia Server and displays the expected content. Check both a known-good small file and the reproduced large-file case. Verify whether the failure follows the file when tested in a controlled copy or remains tied to the object/station. Record the exact CEMAT and WinCC build, file name and size, test station and result. No reproduction or lab test is claimed for this article.

Limitations and Operational Precautions

The thread contains no attached TXT file, screenshot, file size or confirmed solution. The reviewed Siemens documents do not publish a maximum size for these files. Do not invent a size threshold or assume that adding a larger file will eventually break every Info Dialog. Preserve existing periphery files and archive/project data; test changes in a copy and coordinate any PCS 7 compile/download with operations. Send private project files only through an approved support route.

Engineer FAQ

Where does CEMAT V9.0 store per-object I/O information text files? Siemens' V9.0 SP1 reference describes the Multimedia\Periphery directory on the Multimedia Server, with one corresponding TXT file per object.

Does Siemens specify a maximum TXT size? The cited CEMAT documentation gives no maximum file-size value.

Does compiling and downloading fix a large periphery TXT file? The thread suggests recompiling/downloading but reports no successful result. Treat it as an unconfirmed suggestion, not a documented size-limit remedy.

What if the Info Dialog opens but only part of the text is visible? Record the visible behavior and compare a short test copy with the original in a controlled environment; a display/clipping issue differs from the dialog failing to open.

What if only one object's file fails? Compare its object-to-filename association, server directory and file contents with a working object, then provide the redacted evidence and file through an approved support channel.

Technical References

Siemens, CEMAT V9.0 SP1 Reference Manual System MinAS, “CEMAT Info Tool” (C_INFO.xlsm export, C_INFO archive import and per-object text files in Multimedia\Periphery): https://support.industry.siemens.com/cs/attachments/109762228/Cem_V90_System_001_en.pdf
Siemens, CEMAT V9.0 SP2 Reference Manual System MinAS, “CEMAT Info Tool” (per-object text file placement and generation workflow): https://support.industry.siemens.com/cs/attachments/109767940/Cem_V90_System_001_en.pdf
Siemens, CEMAT V9.0 SP2 Readme, @PG_C_INFO and periphery text files (TAG.txt/Chart_Block.txt naming note; file opened unmodified from the Info Dialog): https://support.industry.siemens.com/cs/attachments/109768008/109768008_CEMAT_V902_readme_en.pdf
Siemens, CEMAT Engineering Manual V9.0 SP2, general project engineering reference; use the installed release manual for the exact C_INFO procedure: https://support.industry.siemens.com/cs/attachments/109768056/Cem_V90_Engineering_000_en.pdf

Troubleshoot Large CEMAT Periphery Text Files That Will Not Open