Skip to Content

Changes for page 7. Events Setup

Last modified by Iaroslav Platonov on 2026/06/09 11:03
From version 29.2
edited by Lana
on 2025/12/11 00:51
Change comment: There is no comment for this version
To version 35.2
edited by Lana
on 2025/12/11 00:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -156,8 +156,69 @@
156 156  
157 157  Fig. 2.9 - Import/Export configuration file page
158 158  
159 -To configure events, download the events.xlsx file by clicking the button
159 +To configure events, download the events.xlsx file by clicking the button [[image:Screenshot 2025-12-10 at 21.51.37.png||height="28" width="97"]], then fill in the appropriate cells in the new line of the table in the **Events** tab (see Fig. 2.10).
160 160  
161 -
161 +[[image:Screenshot 2025-12-10 at 21.52.08.png]]
162 162  
163 +Fig. 2.10 - Events tab in the events.xslx file
164 +
165 +To create an event, fill in the following columns:
166 +
167 +**Event ID **is an event unique number.
168 +
169 +**Name **is the name of the event.
170 +
171 +**Event type **is one_position or two_position event.
172 +
173 +**Event status **is responsible for the event status: 1 - event is enabled, 0 - event is disabled.
174 +
175 +**Device ID **is a device identifier to which the event refers.
176 +
177 +**The device** is not required to be filled in, it is generated when downloading an Excel file to help with debugging (displays the path of the linked device).
178 +
179 +**Object ID **is an IM object identifier to which the event refers.
180 +
181 +**Object** does not need to be filled in, it is generated when downloading an Excel file to help in debugging (displays the path of the linked object).
182 +
183 +**Tags **is a tag (parameter) Identifier to which the event refers.
184 +
185 +**Formula** defines the condition under which the event is to be triggered. Description of formulas is given in the Appendix.
186 +
187 +**Dead time, ms **is a field to enter the delay time, in milliseconds, for the event to be triggered.
188 +
189 +**Event type code **is a code, which is entered according to the **Event type** directory using a separate tab in this file.
190 +
191 +**Event type name **is a name of the event type, the field is filled in automatically when uploading-downloading the configuration file.
192 +
193 +**Message **is a message text that should be displayed in the logs when the event is triggered.
194 +
195 +**Acknowledgement **is responsible for the event acknowledgement. True - acknowledgement is enabled, False - acknowledgement is disabled.
196 +
197 +**Sound ID **specifies an ID of a sound file loaded through the sound editor.
198 +
199 +**Sound name **is a name of the sound file, the field is filled in automatically when loading-unloading the configuration file.
200 +
201 +**Repeat count **is used to set the number of repetitions of sound playback when the event is triggered.
202 +
203 +**Infinity repeat **is responsible for repeating the sound until the user acknowledges the event. True - infinite repetition is enabled, False - infinite repetition is disabled.
204 +
205 +After all required fields are filled in, the file should be uploaded using the button [[image:Screenshot 2025-12-10 at 21.53.38.png||height="22" width="77"]] on the **Import/Export configuration file** page (see Fig. 2.9). In the window that appears (see Fig. 2.11), select the filled in events.xlsx file. The system will automatically validate the file to ensure it is correctly filled in and formatted (see Fig. 2.12).
206 +
207 +[[image:Screenshot 2025-12-10 at 21.54.07.png||height="234" width="379"]]
208 +
209 +Fig. 2.11 - Upload configuration file window
210 +
211 +[[image:Screenshot 2025-12-10 at 21.54.41.png||height="413" width="477"]]
212 +
213 +Fig. 2.12 - Validating the configuration file
214 +
215 +If errors are detected, they will be displayed in the file upload window. After all errors are eliminated, the **Write configuration** button will become available.
216 +
217 +After uploading the file, the configuration should be refreshed to apply the changes (see Fig. 2.7).
218 +
219 +To make working with events more convenient, CENTO provides the option to edit the event configuration partially using Excel.
220 +
221 +To do this, on the page /CENTO/web/ui/event_editor/index (menu item Settings > Events > Event editor (see Fig. 2.1 - Fig. 2.2), search for an events using the filtering [[image:Screenshot 2025-12-10 at 21.55.29.png]]
222 +
223 +
163 163  
Screenshot 2025-12-10 at 21.51.37.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +6.8 KB
Content
Screenshot 2025-12-10 at 21.52.08.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +223.8 KB
Content
Screenshot 2025-12-10 at 21.53.38.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +6.0 KB
Content
Screenshot 2025-12-10 at 21.54.07.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +46.4 KB
Content
Screenshot 2025-12-10 at 21.54.41.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +91.9 KB
Content
Screenshot 2025-12-10 at 21.55.29.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +1.8 KB
Content