Skip to Content

Changes for page 7. Events Setup

Last modified by Iaroslav Platonov on 2026/06/09 11:03
From version 15.1
edited by Lana
on 2025/12/11 00:38
Change comment: Uploaded new attachment "Screenshot 2025-12-10 at 21.38.47.png", version {1}
To version 22.2
edited by Lana
on 2025/12/11 00:44
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -52,8 +52,69 @@
52 52  == 2.2. Creating and editing an event in web-interface ==
53 53  
54 54  
55 -An event can be created manually and automatically. Events are automatically created when the setpoint parameter is enabled. For a detailed description, refer to the "Setup Manual"
55 +An event can be created manually and automatically. Events are automatically created when the setpoint parameter is enabled. For a detailed description, refer to the "Setup Manual".
56 56  
57 +The text of setpoints can be edited in the **Event editor** interface.
58 +
59 +To do this, click on the button [[image:Screenshot 2025-12-10 at 21.38.47.png||height="22" width="119"]]. After that, the **Setpoint editing** window opens (see Fig. 2.3), where the wording of the setpoints for Triggering and/or Return can be modified, such as Upper/Lower warning limit, Upper/Lower alarm limit, and Upper/Lower physical limit.
60 +
61 +One or more variables can be specified in the setpoint triggering message:
62 +
63 +* ~{~{.tag_name}} - tag name;
64 +* ~{~{.tag_code}} - tag code;
65 +* ~{~{.tag_id}} - tag ID;
66 +* ~{~{.tag_code_or_id}} - tag code, if the code is empty, then its ID;
67 +* ~{~{.tag_limit}} - setpoint value;
68 +* ~{~{.tag_unit}} - tag units;
69 +* ~{~{.device_name}} - name of the device to which the tag is linked.
70 +
71 +IMPORTANT: if {figure brackets} or dots are missing when writing these parameters, a validation error will occur.
72 +
73 +If a parameter with an error (non-existent parameter) is entered, for example: ~{~{.tag_name_2}}, the Operating journal will receive an event of the following type: [[image:Screenshot 2025-12-10 at 21.39.52.png||height="18" width="18"]] **< no value> > 10**.
74 +
75 +[[image:Screenshot 2025-12-10 at 21.40.35.png]]
76 +
77 +Fig. 2.3 - Setpoint editing page
78 +
79 +To create a new event, click on the button [[image:Screenshot 2025-12-10 at 21.41.09.png||height="24" width="96"]].
80 +
81 +Only an authorized user with appropriate rights can create and edit events.
82 +
83 +Fig. 2.4. shows the page for creating a new event.
84 +
85 +[[image:Screenshot 2025-12-10 at 21.41.54.png]]
86 +
87 +Fig. Event editor: creation page
88 +
89 +The** Event editor** window contains the following fields:
90 +
91 +**Identifier **contains the sequence number of the event (filled in automatically), can be changed if necessary.
92 +
93 +**Name **is a field for entering the name of the event.
94 +
95 +**Object **field is used to add an object from the CENTO Information Model (IM), to which the event refers (see "Information Model Setup Manual"). The IM object is selected from the IM drop-down tree.
96 +
97 +**Device **is** **the device to which the event refers is added in this field. The device is selected from the drop-down device tree.
98 +
99 +**Event type **switches the event type between "Single" and "With return" [[image:Screenshot 2025-12-10 at 21.42.53.png||height="27" width="135"]].
100 +
101 +There are two types of events in CENTO – single and with return events. For system objects, there may be important state that the user should see in the active status (e.g., "Ground in a network with isolated neutral", "Switching on a sectionalizer", "Opening the emergency exit door"). Events reporting this important state are opening events. Events reporting the end of an important object state are closing events. These two types of events are events with return. **Events with return should ALWAYS be paired: the second event ALWAYS closes the first one. **Events in the active state are displayed in a separate tab of the operational log and disappear from there after triggering the closing event. Other events (regardless of their importance) are single events.
102 +
103 +**Tags **field requires to specify the ID of the telemetering tag to which the event belongs;
104 +
105 +**Message **is the message text that should be output when the event is triggered;
106 +
107 +**Formula **field is used to enter a formula that describes the condition for the event to be triggered. Clicking on [[image:Screenshot 2025-12-10 at 21.43.51.png||height="28" width="163"]] will open the list of formulas for forming the event. Description of formulas is given in the Appendix.
108 +
109 +**Dead time, (ms)** field specifies the delay time for the event to be generated in milliseconds. It helps prevent false events, such as those caused by frequent device polling failures due to poor communication.
110 +
111 +**Type** is** **a drop-down list used to specify the importance or category of the event.
112 +
113 +**Acknowledgement **is a switch to activate the function of user acknowledgement of event notification;
114 +
115 +**Sound **field is used to select a sound for notification. The drop-down list contains those sounds that are loaded through the Sound Editor (see item 3). The selected sound can be listened to using the button
116 +
117 +
57 57  
58 58  
59 59  
1765431562370-764.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +937 bytes
Content
Screenshot 2025-12-10 at 21.39.52.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +1.6 KB
Content
Screenshot 2025-12-10 at 21.40.35.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +176.4 KB
Content
Screenshot 2025-12-10 at 21.41.09.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +5.1 KB
Content
Screenshot 2025-12-10 at 21.41.54.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +63.6 KB
Content
Screenshot 2025-12-10 at 21.42.53.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +12.6 KB
Content
Screenshot 2025-12-10 at 21.43.51.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +10.5 KB
Content