Use same comment for Alam and CEL message not working
Description
Comments for alarms cannot be synchronized with the
CEL, although the project property "Same comment" is activated
in the "AML and CEL" group. Alarm comments are not applied to
the corresponding CEL entry.
This error has been fixed. Comments are synchronized again.
To benefit from this fix:
- Update your zenon Software Platform to the latest build of zenon 12 or
higher.
Item ID: 273771
Version: 12.00 Build: 206562
Related Articles
Checklist: Message Control
Time estimate: 15 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Screenshot and followed ...
CEL: instead the current text the old comment text value is proposed while edit comment for next entry
Summary Issue in Chronological Event List - in edit of comment field (in-place edit): the field in editing mode proposes text from previously edited comment instead the text of current entry. Description Issue in Chronological Event List - in edit of ...
FAQ: What are the modems successfully tested with zenon Message Control?
The list of tested modems is available in the pdf file attached. Unfortunately, old analog voice modems are rare on the market and the drivers for these devices are not available for actual operating systems like Windows 10, Windows Server 2016, etc. ...
Adding a comment to a CEL object via the API in the CelItemAdded event, causes the CELItemAdded event to be executed multiple times
Summary When a comment is entered for a CEL entry via the API, using code executed in the CelItemAdded event, the CelItemAdded event is executed multiple times DescriptionWhen a comment is entered for a CEL entry via the API, using code executed in ...
Message Control engine suppression for equipment modelling is not working properly
Summary A variable with equipment model RootNode.ChildNode is projected to send a message. If suppression is done for RootNode, suppressing messages seems to work (although this behaviour is faulty). If suppression is done for RootNode.ChildNode, ...