Skip to Content

Wiki source code of 7. Events Setup

Version 25.1 by Lana on 2025/12/11 00:48
Show last authors
1 = CONTENT =
2
3 = 1. INTRODUCTION =
4
5 CENTO is a multifunctional software platform for data collection, processing and display. This Manual describes the user tool in CENTO "Events".
6
7 It is assumed that the user is already familiar with the basic elements of the CENTO interface after reading the "User Manual" instructions.
8
9 "Events" in CENTO are designed to increase the observability of system operation by tracking changes in the system status and process equipment, logging events, and notifying users. Events help the personnel to timely react to changes in the technological process and system operation. To achieve these goals, CENTO offers user notification and acknowledgement features alongside event logging.
10
11 = 2. CENTO EVENTS =
12
13 == 2.1. Event editor ==
14
15 To go to the **Event editor**, select the item in the main menu:
16
17 Settings > Events > Event editor.
18
19 [[image:Screenshot 2025-12-10 at 21.28.44.png]]
20
21 Fig. 2.1 - Event editor in the CENTO menu
22
23 Figure 2.2. shows the interface of the **Event editor.**
24
25 [[image:Screenshot 2025-12-10 at 21.29.15.png]]
26
27 Fig. 2.2 - Event editor
28
29 The **Event editor** page provides the option to:
30
31 1. Add a new event to the system [[image:Screenshot 2025-12-10 at 21.29.51.png||height="21" width="74"]]
32 1. Activate [[image:Screenshot 2025-12-10 at 21.30.26.png||height="20" width="108"]] or disable [[image:Screenshot 2025-12-10 at 21.30.54.png||height="20" width="103"]] selected events
33 1. (((
34 Edit [[image:Screenshot 2025-12-10 at 21.32.53.png||height="25" width="24"]], copy [[image:Screenshot 2025-12-10 at 21.33.40.png||height="26" width="26"]], and delete [[image:Screenshot 2025-12-10 at 21.34.05.png||height="27" width="27"]]in the "Actions" column
35 )))
36 1. (((
37 Delete any number of events [[image:Screenshot 2025-12-10 at 21.35.15.png||height="22" width="125"]]
38 )))
39 1. (((
40 Edit the number of records to be displayed
41 )))
42 1. (((
43 Search for events of interest by filtering [[image:Screenshot 2025-12-10 at 21.36.03.png||height="32" width="33"]] (the filter is located to the right of the table headings)
44 )))
45 1. (((
46 Edit event configuration [[image:Screenshot 2025-12-10 at 21.36.56.png||height="22" width="86"]]
47 )))
48 1. (((
49 Adjust the setpoint text [[image:Screenshot 2025-12-10 at 21.37.32.png||height="23" width="122"]]
50 )))
51
52 == 2.2. Creating and editing an event in web-interface ==
53
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".
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 [[image:Screenshot 2025-12-10 at 21.44.31.png||height="24" width="27"]] to the right of the "Sound" field.
116
117 **Before acknowledgement** is a switch to play the selected sound before the event is acknowledged;
118
119 **Sound repeats **field is used to set the number of repetitions of sound playback when the event occurs.
120
121 **Warning! **Modern browsers block playback of sounds in a browser by default, so sound alerts may not be played. To allow CENTO to play sounds in the browser, follow the steps below (an example is given for Chrome):
122
123 ~1. Left click to the left of the address bar (see Fig. 2.5).
124
125 2. Select "Site settings".
126
127 [[image:Screenshot 2025-12-10 at 21.45.18.png]]
128
129 Fig. 2.5 - Site settings
130
131 3. In the opened window, go to Privacy and security → Site settings → Additional permissions → Content → Additional content settings → Sound, and select Allow (see Fig. 2.6).
132
133
134
135
136