Find Obsolete EventState References Behind PCS 7 System Messages
Inspect the OS picture references when PCS 7 reports that an EventState does not exist after charts or blocks have been removed. Siemens documents a CrossReference search for tags that are used but no longer exist, followed by correction of their interconnections. This can locate affected picture objects even when the message text does not. A stale group-display reference remains a candidate cause until the actual object and corrected runtime behavior are verified.
Table of Contents
- Why Deleted Blocks Can Leave Picture References
- Find Used Tags That Do Not Exist
- Correct the Intended Picture Object
- Verification
- Limitations and Operational Precautions
- Engineer FAQ
- Technical References
- Related Articles
- Related Tags
Why Deleted Blocks Can Leave Picture References
The reported message is "Eventstate existiert nicht", meaning the referenced EventState does not exist. The named charts or blocks are absent from the project. A proposed explanation is an old group display still referencing a deleted tag; that cause has not been confirmed by a reported final test.
Siemens' V9.0 SP1 OS manual explains that picture-object interconnections can remain after their target tags disappear. It documents CrossReference for finding such uses. This provides a concrete investigation path beyond the message text alone. Operator Station, section 10.7.2.
Find Used Tags That Do Not Exist
For the documented V9.0 SP1 workflow:
- Back up the engineering project and compile the OS so the reference data reflects the configuration.
- Open CrossReference in WinCC Explorer, then File > New. Use Update if prompted.
- In Edit filter, select Tags and Used, not existing (not selectable).
- Select the Search in categories and click Start search.
- Inspect the containing picture and object for the suspect reference. Treat unused template references separately from operational objects.
Operator Station, sections 10.7.2–10.7.5. The actual release is unspecified, so confirm these commands in the installed edition.
Correct the Intended Picture Object
For each candidate, decide whether the process object was intentionally removed or replaced. Inspect the graphic's current role and its expected alarm indication.
The documented correction method uses Edit > Link in CrossReference, Browse beside Replace with, selection of the valid tag, then Replace and Close. Operator Station, section 10.7.6. Do not relink to an arbitrary existing tag merely to eliminate an error. If the display itself is obsolete, remove it only after reviewing the picture's operator function.
The statement that the message alone cannot identify a picture must not be expanded into a claim that picture references cannot be located. The documented reference search is a separate diagnostic method.
Verification
Repeat the reference check after approved corrections and inspect the affected operational picture. For a relinked object, confirm that it displays the intended process tag's alarm state, not just any valid tag.
In a controlled runtime check, observe whether the original system message recurs when the affected picture is used. A reference list with no missing tag does not independently prove correct alarm association. No runtime test has been performed here.
Limitations and Operational Precautions
The actual PCS 7 release and offending picture/object are unidentified. Stale group-display references remain a candidate cause until a matching reference is found and the corrected behavior verified.
Preserve a project backup and change record. Keep offline compilation, graphic editing and production deployment separate. Review the effect of deleting or relinking alarm displays on operator visibility; do not replace a missing reference with a dummy tag.
Engineer FAQ
Can the error text identify the picture on its own? That is not established; inspect reference locations separately.
Does deleting a CFC remove every picture interconnection? The cited manual describes retained picture links whose targets become invalid.
Is any existing tag an acceptable replacement? No; it must represent the intended process object's alarm state.