Changes for page 7. Events Setup
Last modified by Iaroslav Platonov on 2026/06/09 11:03
From version 65.1
edited by Iaroslav Platonov
on 2026/06/09 11:03
on 2026/06/09 11:03
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 2 removed)
Details
- Page properties
-
- Parent
-
... ... @@ -1,1 +1,1 @@ 1 -CENTO Manuals.WebHome1 +CENTO onboarding.WebHome - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Iaroslav1 +XWiki.Lana - Content
-
... ... @@ -1,690 +1,310 @@ 1 -{{html clean="false"}} 2 -<style> 3 -.doc-content h1::before,.doc-content h2::before, 4 -.doc-content h3::before,.doc-content h4::before, 5 -.doc-content h5::before,.doc-content h6::before { content:none !important; display:none !important; } 6 -.doc-content { counter-reset:none !important; } 7 -#rn-prog { position:fixed;top:0;left:0;height:3px;width:0;background:#005AB4;z-index:9999;pointer-events:none; } 8 -.doc-wrap { position:relative; } 9 -.doc-content { margin-right:224px;border-left:1px solid #E8E8E8;border-right:1px solid #E8E8E8;padding:0 32px; } 10 -.doc-toc { position:absolute;top:0;right:0;width:200px;font-size:12.5px;line-height:1.55;padding:20px 0 20px 16px; } 11 -.doc-toc.is-fixed { position:fixed;width:200px;overflow-y:auto;z-index:10; } 12 -.toc-header { display:flex;justify-content:space-between;align-items:center;margin-bottom:10px; } 13 -.toc-header strong { font-size:13px;font-weight:700;color:#222; } 14 -.toc-toggle { background:none;border:none;cursor:pointer;color:#555;font-size:14px;padding:0 2px;line-height:1; } 15 -.toc-toggle:hover { color:#222; } 16 -.doc-toc ul { list-style:none;margin:0;padding:0; } 17 -.doc-toc li { margin:0; } 18 -.doc-toc a { display:block;padding:3px 0;color:#555;text-decoration:none;border-left:2px solid transparent;transition:color .12s; } 19 -.doc-toc a:hover { color:#222;text-decoration:underline; } 20 -.doc-toc a.toc-on { color:#222;font-weight:700;border-left:2px solid #005AB4;padding-left:5px; } 21 -.tl1 > a { font-weight:600;color:#222; } 22 -.tl2 > a { padding-left:14px; } 23 -.tl3 > a { padding-left:26px;font-size:12px; } 24 -.doc-content h2 { font-size:1.15em;font-weight:700;color:#222;margin:36px 0 10px 0;display:flex;align-items:baseline;gap:7px;scroll-margin-top:16px; } 25 -.doc-content h3 { font-size:1em;font-weight:700;color:#222;margin:22px 0 8px 0;display:flex;align-items:baseline;gap:6px;scroll-margin-top:16px; } 26 -.doc-content h4 { font-size:.93em;font-weight:700;color:#222;margin:14px 0 6px 0;scroll-margin-top:16px; } 27 -.doc-content p { font-size:.93em;color:#333;line-height:1.75;margin:0 0 12px 0; } 28 -.doc-content ul,.doc-content ol { font-size:.93em;color:#333;line-height:1.75;margin:0 0 12px 0;padding-left:24px; } 29 -.doc-content li { margin-bottom:4px; } 30 -.doc-content strong { color:#222; } 31 -.doc-content code { background:#f5f5f5;border:1px solid #E8E8E8;border-radius:3px;padding:1px 5px;font-family:Menlo,Monaco,Consolas,"Courier New",monospace;font-size:.82em;color:#222;line-height:1; } 32 -.anchor-icon { color:#E8E8E8;text-decoration:none;opacity:0;transition:opacity .15s;vertical-align:middle;margin-left:4px;display:inline-flex;align-items:center; } 33 -h2:hover .anchor-icon,h3:hover .anchor-icon { opacity:1; } 34 -.anchor-icon:hover { color:#005AB4; } 35 -.note { border-radius:6px;padding:12px 16px;margin:14px 0;border:1px solid transparent; } 36 -.note-info { background:#e1f1f9 !important;border-color:#b3d4ee !important;border-left:4px solid #005AB4 !important; } 37 -.note-warning { background:#fff4ec !important;border-color:#f5cba7 !important;border-left:4px solid #DD5600 !important; } 38 -.note-tip { background:#e5f3df !important;border-color:#b7dba5 !important;border-left:4px solid #73A839 !important; } 39 -.note-hd { font-weight:700;font-size:.85em;display:flex;align-items:center;gap:5px;margin-bottom:5px; } 40 -.note-info .note-hd { color:#003d80 !important; } 41 -.note-warning .note-hd { color:#a03d00 !important; } 42 -.note-tip .note-hd { color:#3d6b1a !important; } 43 -.note-body { font-size:.875em;color:#222 !important;line-height:1.65; } 44 -.section-index { list-style:disc;padding-left:20px;margin:0 0 20px 0; } 45 -.section-index li { margin-bottom:12px; } 46 -.section-index li a { color:#005AB4;font-weight:600;font-size:.93em;text-decoration:underline; } 47 -.section-index li p { margin:3px 0 0 0;font-size:.875em;color:#333;line-height:1.6; } 48 -.parent-topic { font-size:.82em;color:#555;margin:18px 0 24px 0;border-top:1px solid #E8E8E8;padding-top:10px; } 49 -.parent-topic a { color:#005AB4; } 50 -img.inline-icon { display:inline-block;height:28px;width:auto;vertical-align:middle;border:1px solid #E8E8E8;border-radius:4px;margin:0 3px;box-shadow:0 1px 2px rgba(0,0,0,.08); } 51 -img.inline-icon-sm { display:inline-block;height:20px;width:auto;vertical-align:middle;border:1px solid #E8E8E8;border-radius:3px;margin:0 3px;box-shadow:0 1px 2px rgba(0,0,0,.08); } 52 -.fig { margin:12px auto 24px auto;width:fit-content;max-width:100%; } 53 -.fig img { border-radius:4px 4px 0 0;border:1px solid #E8E8E8;display:block;cursor:zoom-in;max-width:100%;box-shadow:0 1px 4px rgba(0,0,0,.10);transition:box-shadow .15s; } 54 -.fig img:hover { box-shadow:0 3px 12px rgba(0,90,180,.18); } 55 -.fig-cap { font-size:.78em;color:#555;margin:0;padding:5px 8px;background:#f5f5f5;border:1px solid #E8E8E8;border-top:none;border-radius:0 0 4px 4px;display:block;width:100%;box-sizing:border-box; } 56 -#rn-lb { display:none;position:fixed;inset:0;z-index:9998;background:rgba(0,0,0,.8);cursor:zoom-out;align-items:center;justify-content:center; } 57 -#rn-lb.open { display:flex; } 58 -#rn-lb-wrap { position:relative;cursor:default;max-width:92vw;max-height:90vh; } 59 -#rn-lb-wrap img { max-width:100%;max-height:90vh;border-radius:5px;display:block; } 60 -#rn-lb-x { position:absolute;top:-13px;right:-13px;background:#005AB4;color:#fff;width:26px;height:26px;border-radius:50%;border:none;cursor:pointer;font-size:15px;display:flex;align-items:center;justify-content:center; } 61 -#rn-lb-cap { position:fixed;bottom:18px;left:50%;transform:translateX(-50%);color:#ddd;font-size:.78em;background:rgba(0,0,0,.55);padding:3px 12px;border-radius:14px;pointer-events:none; } 62 -#rn-top { position:fixed;bottom:60px;right:60px;z-index:9997;width:36px;height:36px;border-radius:50%;background:#005AB4;color:#fff;border:none;cursor:pointer;display:flex;align-items:center;justify-content:center;opacity:0;transform:translateY(8px);transition:opacity .22s,transform .22s;pointer-events:none;box-shadow:0 2px 8px rgba(0,90,180,.3); } 63 -#rn-top.on { opacity:1;transform:translateY(0);pointer-events:auto; } 64 -#rn-top:hover { background:#0066cc; } 65 -.rn-toast { position:fixed;bottom:66px;right:24px;z-index:9999;background:#222;color:#fff;font-size:.74em;padding:4px 11px;border-radius:4px;pointer-events:none;opacity:0;transition:opacity .18s; } 66 -.rn-toast.on { opacity:1; } 67 -.rn-table { width:100%;border-collapse:collapse;margin:8px 0 18px 0;font-size:.82em; } 68 -.rn-table th { background:#f5f5f5;text-align:left;padding:7px 10px;font-size:.78em;font-weight:700;text-transform:uppercase;letter-spacing:.04em;color:#555;border-bottom:2px solid #E8E8E8; } 69 -.rn-table td { padding:7px 10px;border-bottom:1px solid #E8E8E8;color:#333;vertical-align:top;line-height:1.6; } 70 -.rn-table tr:last-child td { border-bottom:none; } 71 -.rn-table tr:hover td { background:#f5f5f5; } 72 -.rn-table code { background:#f0f0f0;border:1px solid #ddd;border-radius:3px;padding:1px 4px;font-size:.88em;font-family:Menlo,Monaco,Consolas,monospace; } 73 -.tbl-wrap { overflow-x:auto;margin:8px 0 18px 0; } 74 -.var-badge { display:inline-block;font-family:Menlo,Monaco,Consolas,monospace;font-size:.8em;background:#deeaf7;color:#005AB4;border:1px solid #b3d4ee;border-radius:3px;padding:1px 6px; } 75 -</style> 1 += CONTENT = 76 76 77 -<div id="rn-prog"></div> 78 -<div id="rn-lb"> 79 - <div id="rn-lb-wrap"> 80 - <button id="rn-lb-x" onclick="closeLightbox()">✕</button> 81 - <img id="rn-lb-img" src="" alt=""/> 82 - </div> 83 - <div id="rn-lb-cap"></div> 84 -</div> 85 -<button id="rn-top" onclick="window.scrollTo({top:0,behavior:'smooth'})" title="Back to top"> 86 - <svg width="14" height="14" viewBox="0 0 16 16" fill="currentColor"><path d="M8 4l5 5H3z"/></svg> 87 -</button> 88 -<div class="rn-toast" id="rn-toast">Link copied ✓</div> 3 += 1. INTRODUCTION = 89 89 90 -<div class="doc-wrap"> 91 -<div class="doc-content"> 5 +CENTO is a multifunctional software platform for data collection, processing and display. This Manual describes the user tool in CENTO "Events". 92 92 93 - <ul class="section-index"> 94 - <li><a href="#s-intro">1. Introduction</a> 95 - <p>Overview of the Events tool — purpose, capabilities, and key concepts.</p></li> 96 - <li><a href="#s-events">2. CENTO Events</a> 97 - <p>Event editor, creating and editing events via UI or Excel, and flashing on diagrams.</p></li> 98 - <li><a href="#s-notifications">3. Notifications Settings</a> 99 - <p>Configuring email notifications, filter logic, and notification delivery examples.</p></li> 100 - <li><a href="#s-sound-editor">4. Sound Editor</a> 101 - <p>Uploading and managing .mp3 sound files for event alerts.</p></li> 102 - <li><a href="#s-examples">5. Examples of Event Setup</a> 103 - <p>Practical examples: events on tag value change and device status change.</p></li> 104 - <li><a href="#s-annex">Appendix: Formula Reference</a> 105 - <p>Variables and operators available in event condition formulas.</p></li> 106 - </ul> 7 +It is assumed that the user is already familiar with the basic elements of the CENTO interface after reading the "User Manual" instructions. 107 107 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. 108 108 109 - <h2id="s-intro">1.Introduction<a class="anchor-icon" href="javascript:void(0)" onclick="copyAnchor('s-intro')" title="Copylink"><svgwidth="12" height="12" viewBox="0 0 16 16" fill="currentColor"><path d="M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z"/></svg></a></h2>11 += 2. CENTO EVENTS = 110 110 111 - <p>CENTO is a multifunctionalsoftwareplatform fordata collection, processing, and display. This manual describesthe <strong>Events</strong>user tool in CENTO.</p>13 +== 2.1. Event editor == 112 112 113 - <p>Itis assumedthat theuseris already familiarwith the basicelementsoftheCENTOinterfaceafter readingtheUser Manual.</p>15 +To go to the **Event editor**, select the item in the main menu: 114 114 115 - <p>Events in CENTO are designedtoincrease the observability of system operation by trackingchangesinthe system status and process equipment, logging events, and notifying users.Eventshelppersonnel react in a timely manner to changes in the technological process and system operation. To achieve these goals, CENTO provides usernotificationand acknowledgement features alongside eventlogging.</p>17 +Settings > Events > Event editor. 116 116 117 - <h2id="s-events">2. CENTO Events<aclass="anchor-icon" href="javascript:void(0)" onclick="copyAnchor('s-events')" title="Copy link"><svg width="12" height="12" viewBox="0 0 16 16" fill="currentColor"><pathd="M7.775 3.275a.75.750001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.830.75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.53.5 0 00-4.95-4.95l-1.251.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z"/></svg></a></h2>19 +[[image:Screenshot 2025-12-10 at 21.28.44.png]] 118 118 119 - <h3id="s-event-editor">2.1.Event editor<aclass="anchor-icon"href="javascript:void(0)" onclick="copyAnchor('s-event-editor')"title="Copylink"><svg width="12" height="12" viewBox="0 0 16 16" fill="currentColor"><path d="M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z"/></svg></a></h3>21 +Fig. 2.1 - Event editor in the CENTO menu 120 120 121 - <p>Toopenthe<strong>Eventeditor</strong>, selectfromthemain menu: <strong>Settings →Events→ Event editor</strong>.</p>23 +Figure 2.2. shows the interface of the **Event editor.** 122 122 123 - <div class="fig"> 124 - <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.28.44.png" alt="Event editor in the CENTO menu" style="max-width:100%;" onclick="openLightbox(this)"/> 125 - <p class="fig-cap">Figure 2.1. Event editor in the CENTO menu</p> 126 - </div> 25 +[[image:Screenshot 2025-12-10 at 21.29.15.png]] 127 127 128 - <p>Figure2.2showsthe <strong>Event editor</strong> interface.</p>27 +Fig. 2.2 - Event editor 129 129 130 - <div class="fig"> 131 - <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.29.15.png" alt="Event editor" style="max-width:100%;" onclick="openLightbox(this)"/> 132 - <p class="fig-cap">Figure 2.2. Event editor</p> 133 - </div> 29 +The **Event editor** page provides the option to: 134 134 135 - <p>The <strong>Event editor</strong> page provides the following capabilities:</p> 136 - <ol> 137 - <li>Add a new event to the system <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.29.51.png" alt="Add event"/></li> 138 - <li>Activate <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.30.26.png" alt="Activate"/> or disable <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.30.54.png" alt="Disable"/> selected events</li> 139 - <li>Edit <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.32.53.png" alt="Edit"/>, copy <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.33.40.png" alt="Copy"/>, and delete <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.34.05.png" alt="Delete"/> in the <strong>Actions</strong> column</li> 140 - <li>Delete any number of events at once <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.35.15.png" alt="Delete selected"/></li> 141 - <li>Edit the number of records displayed</li> 142 - <li>Search for events by filtering <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.36.03.png" alt="Filter"/> (the filter is located to the right of the table headings)</li> 143 - <li>Edit event configuration <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.36.56.png" alt="Edit configuration"/></li> 144 - <li>Adjust setpoint text <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.37.32.png" alt="Adjust setpoint text"/></li> 145 - </ol> 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 +))) 146 146 52 +== 2.2. Creating and editing an event in web-interface == 147 147 148 - <h3 id="s-event-create">2.2. Creating and editing an event in the web interface<a class="anchor-icon" href="javascript:void(0)" onclick="copyAnchor('s-event-create')" title="Copy link"><svg width="12" height="12" viewBox="0 0 16 16" fill="currentColor"><path d="M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z"/></svg></a></h3> 149 149 150 - <p>An event can be created manuallyorautomatically. Events are automatically created when the setpoint parameter is enabled. For a detailed description, refer to the Setup Manual.</p>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". 151 151 152 - <p>The text of setpoints can be edited in the<strong>Event editor</strong>interface.Click the button <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.38.47.png" alt="Adjust setpoint text"/>. The <strong>Setpoint editing</strong> window opens (Figure 2.3), where the wording of setpoints for Triggering and/or Return can be modified, including Upper/Lower warning limit, Upper/Lower alarm limit, and Upper/Lower physical limit.</p>57 +The text of setpoints can be edited in the **Event editor** interface. 153 153 154 - <p>One or more variables can be specified in the setpoint triggering message:</p> 155 - <ul> 156 - <li><code>{{.tag_name}}</code> — tag name</li> 157 - <li><code>{{.tag_code}}</code> — tag code</li> 158 - <li><code>{{.tag_id}}</code> — tag ID</li> 159 - <li><code>{{.tag_code_or_id}}</code> — tag code, or ID if the code is empty</li> 160 - <li><code>{{.tag_limit}}</code> — setpoint value</li> 161 - <li><code>{{.tag_unit}}</code> — tag units</li> 162 - <li><code>{{.device_name}}</code> — name of the device the tag is linked to</li> 163 - </ul> 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. 164 164 61 +One or more variables can be specified in the setpoint triggering message: 165 165 166 - <div class="note note-warning"><div class="note-hd"><span>⚠</span> Important</div><div class="note-body">If curly braces or dots are missing when writing these parameters, a validation error will occur. If a non-existent parameter is entered (e.g. <code>{{.tag_name_2}}</code>), the Operating Journal will receive an event of the form: <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.39.52.png" alt="error icon"/> <strong><no value> > 10</strong>.</div></div> 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. 167 167 168 - <div class="fig"> 169 - <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.40.35.png" alt="Setpoint editing page" style="max-width:100%;" onclick="openLightbox(this)"/> 170 - <p class="fig-cap">Figure 2.3. Setpoint editing page</p> 171 - </div> 71 +IMPORTANT: if {figure brackets} or dots are missing when writing these parameters, a validation error will occur. 172 172 173 - <p>To createanewevent,clickthebutton<img class="inline-icon"src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.41.09.png" alt="Add new event"/>.Only an authorized userwithappropriaterights cancreateandedit events.</p>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**. 174 174 175 - <p>Figure2.4showstheeventcreationpage.</p>75 +[[image:Screenshot 2025-12-10 at 21.40.35.png]] 176 176 177 - <div class="fig"> 178 - <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.41.54.png" alt="Event editor: creation page" style="max-width:100%;" onclick="openLightbox(this)"/> 179 - <p class="fig-cap">Figure 2.4. Event editor: creation page</p> 180 - </div> 77 +Fig. 2.3 - Setpoint editing page 181 181 182 - <p>The <strong>Event editor</strong> window contains the following fields:</p> 183 - <ul> 184 - <li><strong>Identifier</strong> — the sequence number of the event (filled in automatically); can be changed if needed.</li> 185 - <li><strong>Name</strong> — the name of the event.</li> 186 - <li><strong>Object</strong> — an object from the CENTO Information Model (IM) to which the event refers. The IM object is selected from a drop-down tree.</li> 187 - <li><strong>Device</strong> — the device to which the event refers, selected from the drop-down device tree.</li> 188 - <li><strong>Event type</strong> — switches the event type between “Single” and “With return” <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.42.53.png" alt="Event type switch"/>.</li> 189 - <li><strong>Tags</strong> — the ID of the telemetering tag to which the event belongs.</li> 190 - <li><strong>Message</strong> — the message text output when the event is triggered.</li> 191 - <li><strong>Formula</strong> — the condition for the event to be triggered. Click <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.43.51.png" alt="Formula list"/> to open the list of available formulas (see Appendix).</li> 192 - <li><strong>Dead time (ms)</strong> — delay time in milliseconds before the event is generated. Helps prevent false events caused by intermittent communication failures.</li> 193 - <li><strong>Type</strong> — a drop-down list for the importance or category of the event.</li> 194 - <li><strong>Acknowledgement</strong> — a switch to enable user acknowledgement of event notification.</li> 195 - <li><strong>Sound</strong> — selects a sound for notification from those loaded in the Sound Editor (see section 4). The selected sound can be previewed using the button <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.44.31.png" alt="Play sound"/> to the right of the “Sound” field.</li> 196 - <li><strong>Before acknowledgement</strong> — a switch to play the selected sound until the event is acknowledged.</li> 197 - <li><strong>Sound repeats</strong> — number of repetitions of sound playback when the event occurs.</li> 198 - </ul> 79 +To create a new event, click on the button [[image:Screenshot 2025-12-10 at 21.41.09.png||height="24" width="96"]]. 199 199 81 +Only an authorized user with appropriate rights can create and edit events. 200 200 201 - <div class="note note-warning"><divclass="note-hd"><span>⚠</span> Important</div><div class="note-body"><strong>Modern browsersblock sound playback by default.</strong> To allow CENTO to play sounds in Chrome:<olstyle='margin:6px 0 0 0;padding-left:18px;'><li>Left-clickto the leftof the addressbar (Figure 2.5) and select <strong>Sitesettings</strong>.</li><li>Go to <strong>Privacy and security → Site settings→Additional permissions→ Sound</strong> and select <strong>Allow</strong> (Figure 2.6).</li><li>Refreshthe CENTO page.</li></ol></div></div>83 +Fig. 2.4. shows the page for creating a new event. 202 202 203 - <div class="fig"> 204 - <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.45.18.png" alt="Site settings — opening permissions" style="max-width:100%;" onclick="openLightbox(this)"/> 205 - <p class="fig-cap">Figure 2.5. Site settings — opening permissions</p> 206 - </div> 85 +[[image:Screenshot 2025-12-10 at 21.41.54.png]] 207 207 208 - <div class="fig"> 209 - <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.48.19.png" alt="Allowing sound playback for the site" style="max-width:100%;" onclick="openLightbox(this)"/> 210 - <p class="fig-cap">Figure 2.6. Allowing sound playback for the site</p> 211 - </div> 87 +Fig. Event editor: creation page 212 212 213 - <p>Afterfillingin all requiredfields, click <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.48.55.png" alt="Save"/> andupdate theconfiguration(Figure2.7).</p>89 +The** Event editor** window contains the following fields: 214 214 215 - <div class="fig"> 216 - <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.49.27.png" alt="Update configuration" style="max-width:100%;" onclick="openLightbox(this)"/> 217 - <p class="fig-cap">Figure 2.7. Update configuration</p> 218 - </div> 91 +**Identifier **contains the sequence number of the event (filled in automatically), can be changed if necessary. 219 219 220 - <div class="note note-info"><div class="note-hd"><span>ℹ</span>Note</div><div class="note-body">Thereare two event typesin CENTO: <strong>Single</strong>and<strong>With return</strong>. Events with return are usedforimportant persistent states (e.g. “Groundfault in isolated-neutralnetwork”). The <em>opening event</em>reports the state start; the <em>closingevent</em> reports its end. <strong>Events withreturnmust always be paired</strong> — thesecondeventalways closes thefirst. Active(unclosed) events are shown in a separate tab of the operational log.</div></div>93 +**Name **is a field for entering the name of the event. 221 221 222 - <p>When <strong>Withreturn</strong>is selected astheeventtype,the Eventeditordisplays additionalfieldswith theheading <strong>Withreturn</strong>(Figure2.8). Thesefieldsareidenticalto those for theSingleeventtype.</p>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. 223 223 224 - <div class="fig"> 225 - <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.49.59.png" alt="Event editor with “With return” type" style="max-width:100%;" onclick="openLightbox(this)"/> 226 - <p class="fig-cap">Figure 2.8. Event editor with “With return” type</p> 227 - </div> 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. 228 228 229 - <h3 id="s-event-excel">2.3.Creating andeditingeventsusing Excel<a class="anchor-icon"href="javascript:void(0)"onclick="copyAnchor('s-event-excel')"title="Copylink"><svgwidth="12"height="12" viewBox="0 0 16 16" fill="currentColor"><pathd="M7.775 3.275a.75.750001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.830.75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.53.5 0 00-4.95-4.95l-1.251.25zm-4.69 9.64a22 0 010-2.83l2.5-2.5a2 2 0 012.830.75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.750 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.830z"/></svg></a></h3>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"]]. 230 230 231 - <p>Events canbeconfiguredusingExcelfiles.Thisfunction is available at<strong>Settings→ConfigurationFiles</strong>(Figure2.9).</p>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. 232 232 233 - <div class="fig"> 234 - <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.51.04.png" alt="Import/Export configuration file page" style="max-width:100%;" onclick="openLightbox(this)"/> 235 - <p class="fig-cap">Figure 2.9. Import/Export configuration file page</p> 236 - </div> 103 +**Tags **field requires to specify the ID of the telemetering tag to which the event belongs; 237 237 238 - <p>To configureevents,downloadthe<code>events.xlsx</code> file by clicking <img class="inline-icon"src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.51.37.png"alt="Download"/>,thenfill inthe appropriatecells ina new row inthe<strong>Events</strong>tab (Figure2.10).</p>105 +**Message **is the message text that should be output when the event is triggered; 239 239 240 - <div class="fig"> 241 - <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.52.08.png" alt="Events tab in events.xlsx" style="max-width:100%;" onclick="openLightbox(this)"/> 242 - <p class="fig-cap">Figure 2.10. Events tab in events.xlsx</p> 243 - </div> 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. 244 244 245 - <p>Fill in the following columns to create an event:</p> 246 - <ul> 247 - <li><strong>Event ID</strong> — unique event number. Must not duplicate existing IDs in the system.</li> 248 - <li><strong>Name</strong> — event name.</li> 249 - <li><strong>Event type</strong> — <code>one_position</code> or <code>two_position</code>.</li> 250 - <li><strong>Event status</strong> — <code>1</code> = enabled, <code>0</code> = disabled.</li> 251 - <li><strong>Device ID</strong> — device identifier the event refers to.</li> 252 - <li><strong>Device</strong> — auto-generated when downloading; shows the device path for debugging. Do not fill in manually.</li> 253 - <li><strong>Object ID</strong> — IM object identifier the event refers to.</li> 254 - <li><strong>Object</strong> — auto-generated when downloading; shows the object path for debugging. Do not fill in manually.</li> 255 - <li><strong>Tags</strong> — tag (parameter) ID the event refers to.</li> 256 - <li><strong>Formula</strong> — condition for triggering the event (see Appendix).</li> 257 - <li><strong>Dead time, ms</strong> — delay time in milliseconds before event generation.</li> 258 - <li><strong>Event type code</strong> — code from the <strong>Event type</strong> directory in the separate tab of this file.</li> 259 - <li><strong>Event type name</strong> — filled in automatically when uploading/downloading.</li> 260 - <li><strong>Message</strong> — message text displayed in logs when the event is triggered.</li> 261 - <li><strong>Acknowledgement</strong> — <code>True</code> = enabled, <code>False</code> = disabled.</li> 262 - <li><strong>Sound ID</strong> — ID of a sound file loaded through the Sound Editor.</li> 263 - <li><strong>Sound name</strong> — filled in automatically when uploading/downloading.</li> 264 - <li><strong>Repeat count</strong> — number of sound repetitions when the event is triggered.</li> 265 - <li><strong>Infinity repeat</strong> — <code>True</code> = repeat until acknowledged, <code>False</code> = use repeat count.</li> 266 - </ul> 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. 267 267 111 +**Type** is** **a drop-down list used to specify the importance or category of the event. 268 268 269 - <p>After filling in all requiredfields, upload thefile usingthe<imgclass="inline-icon"src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.53.38.png"alt="Upload"/> button on theImport/Export configuration filepage (Figure2.9). Inthedialog(Figure2.11), selectthefilled-in<code>events.xlsx</code>.The system will automatically validate the file (Figure 2.12).</p>113 +**Acknowledgement **is a switch to activate the function of user acknowledgement of event notification; 270 270 271 - <div class="fig"> 272 - <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.54.07.png" alt="Upload configuration file window" style="max-width:100%;" onclick="openLightbox(this)"/> 273 - <p class="fig-cap">Figure 2.11. Upload configuration file window</p> 274 - </div> 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. 275 275 276 - <div class="fig"> 277 - <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.54.41.png" alt="Validating the configuration file" style="max-width:100%;" onclick="openLightbox(this)"/> 278 - <p class="fig-cap">Figure 2.12. Validating the configuration file</p> 279 - </div> 117 +**Before acknowledgement** is a switch to play the selected sound before the event is acknowledged; 280 280 281 - <p>If errorsaredetected,they will bedisplayed intheuploadwindow. After all errorsarecorrected,the<strong>Write configuration</strong> button becomes available. Afteruploading,refreshthe configurationtoapplychanges(seeFigure 2.7).</p>119 +**Sound repeats **field is used to set the number of repetitions of sound playback when the event occurs. 282 282 283 - <div class="note note-info"><divclass="note-hd"><span>ℹ</span> Note</div><div class="note-body">For<strong>partial editing</strong>, CENTO alsoallowsdownloading and uploading onlya filteredsubsetof events.IntheEvent editor, filter for the eventsof interestusing<img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.55.29.png"alt="Filter"/>,thenclick <img class="inline-icon"src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.55.55.png"alt="Config"/>andselect <strong>Download</strong>.Thedownloaded<code>events.xlsx</code>willcontain only thefiltered events.To uploadchanges,click thesame button and select<strong>Upload</strong>.Eventsnotincluded in the download willremain unchanged.</div></div>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): 284 284 285 - <div class="notenote-warning"><divclass="note-hd"><span>⚠</span> Important</div><divclass="note-body">Partialupload/download is <strong>notcompatible</strong> withExcelfilesdownloaded using an earlier version of theservice. Attempting to uploadan oldfile willresult in a “Versionincompatibility”error. Whenaddinga new event, the new Event ID must not match any existing ID in the system.</div></div>123 +~1. Left click to the left of the address bar (see Fig. 2.5). 286 286 287 - <h3 id="s-event-flash">2.4.Flashing on thediagram<a class="anchor-icon" href="javascript:void(0)"onclick="copyAnchor('s-event-flash')" title="Copylink"><svg width="12" height="12" viewBox="0 0 16 16" fill="currentColor"><path d="M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z"/></svg></a></h3>125 +2. Select "Site settings". 288 288 289 - <p>An object on a mimic diagram can beconfigured to flash (blink) whenan event isactive.Therearetwomethods:</p>127 +[[image:Screenshot 2025-12-10 at 21.45.18.png]] 290 290 291 - <h4>Method1: Flashingby tag</h4>129 +Fig. 2.5 - Site settings 292 292 293 - <p>Use this method if the information model is not configured or not planned. Steps:</p> 294 - <ol> 295 - <li> 296 - <strong>Set up an event</strong> with the triggering formula, for example, connection loss 297 - (<code>ti40027171 != 1</code>) or restoration (<code>ti40027171 == 1</code>) — any tag 298 - registered in the system can be used (Figure 2.13). 299 - </li> 300 - <li> 301 - <strong>Create a calculated tag</strong> with the formula <code>[devstatusNN]</code> where 302 - NN is the device ID (Figure 2.14). The tag to be used for the designated purpose may get 303 - its value from a real device or may be based on other tags. 304 - </li> 305 - <li> 306 - <strong>Set up an object on the diagram</strong>, referencing the calculated tag from step 2 307 - in its rules (Figure 2.15). 308 - </li> 309 - <li> 310 - After saving the diagram and updating the configuration, if the status of the NN device 311 - changes, the system will start flashing the bound diagram object until it is acknowledged. 312 - </li> 313 - </ol> 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). 314 314 133 +[[image:Screenshot 2025-12-10 at 21.48.19.png]] 315 315 316 - <div class="fig"> 317 - <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.58.43.png" alt="Event configured for tag-based flashing" style="max-width:100%;" onclick="openLightbox(this)"/> 318 - <p class="fig-cap">Figure 2.13. Event configured for tag-based flashing</p> 319 - </div> 135 +Fig. 2.6 - Allow sound 320 320 321 - <div class="fig"> 322 - <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.59.17.png" alt="Calculated tag for diagram flashing" style="max-width:100%;" onclick="openLightbox(this)"/> 323 - <p class="fig-cap">Figure 2.14. Calculated tag for diagram flashing</p> 324 - </div> 137 +4. Refresh the CENTO page. 325 325 326 - <div class="fig"> 327 - <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.59.53.png" alt="Diagram object rules referencing the calculated tag" style="max-width:100%;" onclick="openLightbox(this)"/> 328 - <p class="fig-cap">Figure 2.15. Diagram object rules referencing the calculated tag</p> 329 - </div> 139 +After filling in all the required fields, click [[image:Screenshot 2025-12-10 at 21.48.55.png||height="25" width="70"]] and update the configuration (see Fig. 2.7). 330 330 331 - <h4>Method 2:Flashing by informationmodelobject</h4>141 +[[image:Screenshot 2025-12-10 at 21.49.27.png]] 332 332 333 - <p>For this method, the information model must be configured and the required IM object must be selected in the event's <strong>Object</strong> field. The diagram object must be <em>active</em> (see the Diagrams Development Manual) and bound to the same IM object. Steps:</p> 334 - <ol> 335 - <li><strong>Create an event</strong> with the IM object selected in the <strong>Object</strong> field (Figure 2.16).</li> 336 - <li><strong>Create an active diagram object</strong> bound to the same IM object (Figure 2.17).</li> 337 - </ol> 143 +Fig. 2.7 - Update configuration 338 338 145 +If selecting **With return** in the Event type, the **Event editor** window displays additional fields with the general heading **With return** (see Fig. 2.8). These fields are the same as those used for the **Single** event type. 339 339 340 - <div class="fig"> 341 - <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.01.01.png" alt="Creating an event with an information model object" style="max-width:100%;" onclick="openLightbox(this)"/> 342 - <p class="fig-cap">Figure 2.16. Creating an event with an information model object</p> 343 - </div> 147 +[[image:Screenshot 2025-12-10 at 21.49.59.png]] 344 344 345 - <div class="fig"> 346 - <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.02.05.png" alt="Diagram object bound to the information model" style="max-width:100%;" onclick="openLightbox(this)"/> 347 - <p class="fig-cap">Figure 2.17. Diagram object bound to the information model</p> 348 - </div> 149 +Fig. 2.8 - With return event editor window 349 349 350 - <h2id="s-notifications">3.Notifications Settings<aclass="anchor-icon"href="javascript:void(0)" onclick="copyAnchor('s-notifications')"title="Copy link"><svgwidth="12" height="12"viewBox="0 0 16 16" fill="currentColor"><pathd="M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z"/></svg></a></h2>151 +== 2.3. Creating and editing events using Excel == 351 351 352 - <h3 id="s-notif-create">3.1.Creatingandeditingnotifications<aclass="anchor-icon"href="javascript:void(0)"onclick="copyAnchor('s-notif-create')" title="Copylink"><svg width="12"height="12"viewBox="00 16 16"fill="currentColor"><pathd="M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a220 112.832.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.53.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z"/></svg></a></h3>153 +Events can be configured using Excel files. This function is available on the page /CENTO/web/ui/configuration_loader/index (Settings > Configuration Files) (see Fig. 2.9). 353 353 354 - <p>CENTO can notify users about triggered events via email. To configurenotifications, go to <strong>Settings → Events→ Notifications</strong>.Mailserver configurationis described in the Setup Manual, Mail Servers.</p>155 +[[image:Screenshot 2025-12-10 at 21.51.04.png]] 355 355 356 - <div class="fig"> 357 - <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.03.45.png" alt="Notifications interface" style="max-width:100%;" onclick="openLightbox(this)"/> 358 - <p class="fig-cap">Figure 3.1. Notifications interface</p> 359 - </div> 157 +Fig. 2.9 - Import/Export configuration file page 360 360 361 - <p>The notification table contains the following columns:</p> 362 - <ol> 363 - <li><strong>Name</strong> — notification name.</li> 364 - <li><strong>Emails</strong> — email addresses configured to receive notifications.</li> 365 - <li><strong>Dispatch period</strong> — the time of day allowed for sending notifications.</li> 366 - <li><strong>Iteration period</strong> — minimum time interval between notifications (notifications cannot be sent more frequently than this period).</li> 367 - <li><strong>Operation threshold</strong> — number of event triggers required before a notification is sent.</li> 368 - <li><strong>State</strong> — on/off.</li> 369 - <li><strong>Actions</strong> — edit <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.05.05.png" alt="Edit"/>, copy <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.05.32.png" alt="Copy"/>, delete <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.05.55.png" alt="Delete"/>.</li> 370 - </ol> 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). 371 371 161 +[[image:Screenshot 2025-12-10 at 21.52.08.png]] 372 372 373 - <p>To create a new notification, click <imgclass="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.06.27.png"alt="Createnotification"/>.Only an authorizeduser with appropriatepermissionscan create and edit notifications.</p>163 +Fig. 2.10 - Events tab in the events.xslx file 374 374 375 - <div class="fig"> 376 - <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.07.01.png" alt="Notifications: creation page" style="max-width:100%;" onclick="openLightbox(this)"/> 377 - <p class="fig-cap">Figure 3.2. Notifications: creation page</p> 378 - </div> 165 +To create an event, fill in the following columns: 379 379 380 - <p>Fill in the following fields in the <strong>Notification settings</strong> tab:</p> 381 - <ul> 382 - <li><strong>Name</strong> — notification name.</li> 383 - <li><strong>State</strong> — enables or disables the notification.</li> 384 - <li><strong>Operation threshold</strong> — number of event triggers required before a notification is sent.</li> 385 - <li><strong>Dispatch period</strong> — the time of day allowed for sending notifications.</li> 386 - <li><strong>Iteration period</strong> — minimum time interval between notifications.</li> 387 - <li><strong>Delay (s)</strong> — accumulation window starting from the first event before the notification is sent.</li> 388 - <li><strong>E-mail server</strong> — mail server for sending notifications (configured in Settings → Email servers).</li> 389 - <li><strong>Recipients</strong> — email addresses of notification recipients.</li> 390 - </ul> 167 +**Event ID **is an event unique number. 391 391 169 +**Name **is the name of the event. 392 392 393 - <p>In the <strong>Eventselection</strong> tab (Figure3.3), tick the eventsrequired fornotification in theleft column and click <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.08.29.png"alt="Moveright"/>tomove them to the right column. To remove events, mark theminthe right columnand click <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.08.55.png" alt="Move left"/>.</p>171 +**Event type **is one_position or two_position event. 394 394 395 - <div class="fig"> 396 - <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.07.55.png" alt="Event selection tab" style="max-width:100%;" onclick="openLightbox(this)"/> 397 - <p class="fig-cap">Figure 3.3. Event selection tab</p> 398 - </div> 173 +**Event status **is responsible for the event status: 1 - event is enabled, 0 - event is disabled. 399 399 400 - <p>After fillinginallfields, click<img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.09.48.png"alt="Save"/>and updatetheconfiguration.</p>175 +**Device ID **is a device identifier to which the event refers. 401 401 402 - <h3id="s-notif-logic">3.2.Notificationoperation<aclass="anchor-icon" href="javascript:void(0)"onclick="copyAnchor('s-notif-logic')"title="Copylink"><svgwidth="12"height="12" viewBox="00 16 16" fill="currentColor"><pathd="M7.7753.275a.75.750 001.06 1.06l1.25-1.25a22 0 112.83 2.83l-2.52.5a22 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.53.5000-4.95-4.95l-1.25 1.25zm-4.69 9.64a220 010-2.83l2.5-2.5a220012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.52.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z"/></svg></a></h3>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). 403 403 404 - <p>There are three filter types that control when notifications are sent:</p> 405 - <ol> 406 - <li><strong>Operation threshold</strong></li> 407 - <li><strong>Iteration period</strong></li> 408 - <li><strong>Dispatch period</strong></li> 409 - </ol> 179 +**Object ID **is an IM object identifier to which the event refers. 410 410 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). 411 411 412 - <p>When configuredwithoutanyrestrictions,anotificationis sentwheneverany oftheconfigured eventsis triggered.</p>183 +**Tags **is a tag (parameter) Identifier to which the event refers. 413 413 414 - <h4>Operation threshold</h4>185 +**Formula** defines the condition under which the event is to be triggered. Description of formulas is given in the Appendix. 415 415 416 - <p>A notificationistriggeredwhen the totalnumber oftriggeredeventsin thenotification reachestheconfiguredthreshold.Ifthe thresholdis 0,thenotificationisgeneratedimmediatelyafter any event triggers, providedtheotherfilters allow it.</p>187 +**Dead time, ms **is a field to enter the delay time, in milliseconds, for the event to be triggered. 417 417 418 - <h4>Iteration period</h4>189 +**Event type code **is a code, which is entered according to the **Event type** directory using a separate tab in this file. 419 419 420 - <p>Theiterationperiodstartsfrom the time thelast notification was triggered.Itissetindays and hours. If setto0 days 0 hours, notificationsaregeneratedandsent immediately when theother filterconditionsaremet.</p>191 +**Event type name **is a name of the event type, the field is filled in automatically when uploading-downloading the configuration file. 421 421 422 - <h4>Dispatchperiod</h4>193 +**Message **is a message text that should be displayed in the logs when the event is triggered. 423 423 424 - <p>If setto 0:00–24:00,notificationscan besent at any timeofday.If settoaspecific time(e.g. 8:00),notificationsarebatched andsentonceat that time. The dispatch period canonly besetwithin asinglecalendar day.</p>195 +**Acknowledgement **is responsible for the event acknowledgement. True - acknowledgement is enabled, False - acknowledgement is disabled. 425 425 426 - <div class="fig"> 427 - <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.11.07.png" alt="Logic of filter settings when generating notifications" style="max-width:100%;" onclick="openLightbox(this)"/> 428 - <p class="fig-cap">Figure 3.4. Logic of filter settings when generating notifications</p> 429 - </div> 197 +**Sound ID **specifies an ID of a sound file loaded through the sound editor. 430 430 431 - <h4>Changingnotificationsettings</h4>199 +**Sound name **is a name of the sound file, the field is filled in automatically when loading-unloading the configuration file. 432 432 433 - <p>When notification settings are changed at any time:</p> 434 - <ul> 435 - <li>The <strong>operation threshold counter</strong> is preserved but the notification will not trigger until the next event after the threshold is reached.</li> 436 - <li>The <strong>iteration period</strong> is reset.</li> 437 - </ul> 201 +**Repeat count **is used to set the number of repetitions of sound playback when the event is triggered. 438 438 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. 439 439 440 - <p>Examples:</p> 441 - <ol> 442 - <li>Threshold = 5, 3 events triggered. User increases threshold to 10 → notification fires after 7 more events (total 10).</li> 443 - <li>Threshold = 10, 7 events triggered. User reduces threshold to 5 → notification fires after the next event (total 8 triggered events).</li> 444 - <li>Iteration period = 10 hours, last notification sent 2 hours ago. Settings changed → iteration period resets and notification fires on the next event trigger.</li> 445 - <li>Threshold = 10, notification has 3 events, event #1 triggered twice. User deletes event #1 from notification. When total reaches 10, notification is sent without event #1’s messages.</li> 446 - </ol> 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). 447 447 207 +[[image:Screenshot 2025-12-10 at 21.54.07.png||height="234" width="379"]] 448 448 449 - <div class="fig"> 450 - <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.12.07.png" alt="Notification with operation threshold" style="max-width:100%;" onclick="openLightbox(this)"/> 451 - <p class="fig-cap">Figure 3.5. Notification with operation threshold</p> 452 - </div> 209 +Fig. 2.11 - Upload configuration file window 453 453 454 - <div class="fig"> 455 - <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.12.39.png" alt="Notification with dispatch period" style="max-width:100%;" onclick="openLightbox(this)"/> 456 - <p class="fig-cap">Figure 3.6. Notification with dispatch period</p> 457 - </div> 211 +[[image:Screenshot 2025-12-10 at 21.54.41.png||height="413" width="477"]] 458 458 459 - <div class="fig"> 460 - <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.13.08.png" alt="Notification with all restrictions active" style="max-width:100%;" onclick="openLightbox(this)"/> 461 - <p class="fig-cap">Figure 3.7. Notification with all restrictions active</p> 462 - </div> 213 +Fig. 2.12 - Validating the configuration file 463 463 464 - <h2 id="s-sound-editor">4. Sound Editor<aclass="anchor-icon"href="javascript:void(0)"onclick="copyAnchor('s-sound-editor')"title="Copylink"><svgwidth="12" height="12"viewBox="0 0 16 16"fill="currentColor"><pathd="M7.7753.275a.75.750 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.52.5a22 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.53.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a220010-2.83l2.5-2.5a220 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75000-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z"/></svg></a></h2>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. 465 465 466 - <p>Soundnotificationsaremanagedat<strong>Settings→Events→ Soundeditor</strong>.</p>217 +After uploading the file, the configuration should be refreshed to apply the changes (see Fig. 2.7). 467 467 468 - <div class="fig"> 469 - <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.13.46.png" alt="Sound Editor page" style="max-width:100%;" onclick="openLightbox(this)"/> 470 - <p class="fig-cap">Figure 4.1. Sound Editor page</p> 471 - </div> 219 +To make working with events more convenient, CENTO provides the option to edit the event configuration partially using Excel. 472 472 473 - <p>TheSound Editor showsatablewiththe followingcolumns:<strong>ID</strong>,<strong>Name</strong>, <strong>File name</strong>,<strong>Uploaded</strong>(date), and<strong>Actions</strong> (edit,play,delete).</p>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||height="24" width="25"]], then click on the button [[image:Screenshot 2025-12-10 at 21.55.55.png||height="25" width="95"]]and select **Download** in the drop-down list. After that, the file events.xlsx will be downloaded to the PC, containing only the filtered events from the **Events editor**. 474 474 475 - <div class="notenote-info"><divclass="note-hd"><span>ℹ</span>Note</div><divclass="note-body">TheSoundEditoronlysupports<strong>.mp3</strong>files.</div></div>223 +Actions when filling/editing the columns of the Excel table are similar to the actions during uploading from the** Import/Export configuration file** menu (see Fig. 2.9 - Fig. 2.10). 476 476 477 - <p>Toadd a newsound, click <img class="inline-icon"src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.14.32.png"alt="Addnewsound"/>.In thepop-up (Figure4.2),specify thename, selector drag-and-dropthe.mp3 file, and click <imgclass="inline-icon"src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.15.48.png"alt="Upload"/>.</p>225 +NOTE: when adding a new event, crossing **Event ID** is unacceptable as an incomplete event configuration is unloaded. The new **ID** should not match the existing one in the system (configuration). 478 478 479 - <div class="fig"> 480 - <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.15.12.png" alt="New sound upload window" style="max-width:100%;" onclick="openLightbox(this)"/> 481 - <p class="fig-cap">Figure 4.2. New sound upload window</p> 482 - </div> 227 +To upload the changes made to the file, click on the button [[image:Screenshot 2025-12-10 at 21.55.55.png||height="25" width="95"]] select **Upload** from the drop-down list. Events that were not taken into account when downloading the Excel file will remain unchanged 483 483 484 - <divclass="notenote-warning"><divclass="note-hd"><span>⚠</span>Important</div><divclass="note-body">IfCENTOisopeninmultiplebrowser tabs(e.g. SoundEditorinonetab, a mimic diagraminanother),the oldsound willcontinuetoplay onthediagramtabafter changingthesoundin theeditor.Thenewsound will play onlyaftertheuserinteractswiththe diagramtab(e.g. clickingthemouse).</div></div>229 +IMPORTANT: partial upload/download is not compatible with previously downloaded Excel files. If an Excel file was downloaded using an earlier version of the service (prior to the introduction of the partial upload/download feature), it cannot be uploaded back - an error message saying "Version incompatibility" appears. 485 485 486 - <h2id="s-examples">5.Examples of Event Setup<aclass="anchor-icon"href="javascript:void(0)" onclick="copyAnchor('s-examples')"title="Copylink"><svg width="12" height="12" viewBox="0 0 16 16" fill="currentColor"><path d="M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.699.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z"/></svg></a></h2>231 +== 2.4. Flashing on the diagram == 487 487 488 - <p>The followingexamplesuse the webinterfaceon theeventcreationpagedescribed insection2.2.</p>233 +The flashing of an object on the diagram can be configured in the following ways: 489 489 490 - <h4>Example1:Eventontagvalue change</h4>235 +**~1. Flashing by tag** 491 491 492 - <div class="fig"> 493 - <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.17.31.png" alt="Event setup on tag value change" style="max-width:100%;" onclick="openLightbox(this)"/> 494 - <p class="fig-cap">Figure 5.1. Event setup on tag value change</p> 495 - </div> 237 +This method is relevant if the system does not have and does not plan to customize the information model. 496 496 497 - <p>Figure 5.1 showsthe event <em>Switch position f.1.1 (1QF1)</em> configuredas a one-position event bound to an IM object and a device. The formula<code>ti11013008 == 2</code> triggersthe event when tag11013008equals2. Deadtime is 0 (no delay), acknowledgementis enabled, andthedefault sound plays5times.</p>239 +To customize the flashing of a diagram object by tag: 498 498 499 - <h4>Example 2:Event on device statuschange(with return)</h4>241 +A) Set up an event that will contain the formula, for example, connection loss (ti40027171 != 1) or restoration of connection (ti40027171 == 1) with the device (see Fig. 2.13). The formula can refer not only to the device status, any tags registered in the system can be applied here, in this example, the device status is used as a special case. For more details on the available formulas and expressions, please refer to the** Setup Manual. ** 500 500 501 - <div class="fig"> 502 - <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.19.25.png" alt="Event setup on device status change" style="max-width:100%;" onclick="openLightbox(this)"/> 503 - <p class="fig-cap">Figure 5.2. Event setup on device status change</p> 504 - </div> 243 +[[image:Screenshot 2025-12-10 at 21.58.43.png]] 505 505 506 - <p>Figure 5.2 shows a paired event with return. Two notifications are configured:</p> 507 - <ol> 508 - <li> 509 - <strong>Lost connection with Mikrotik SW1.2</strong> — formula 510 - <code>(devstatus100 == 3) AND (devprevstatus100 != 3)</code>, meaning device ID 100 511 - just entered error status. Dead time = 3000 ms; alarm type with acknowledgement; 512 - sound plays until acknowledged. 513 - </li> 514 - <li> 515 - <strong>Restored connection with Mikrotik SW1.2</strong> — formula 516 - <code>(devstatus100 == 1) AND (devprevstatus100 != 1)</code>, meaning device ID 100 517 - just returned to normal status. Informational type; no acknowledgement required; 518 - sound plays 3 times. 519 - </li> 520 - </ol> 245 +Fig. 2.13 - Event for tag flashing 521 521 247 +B) Create a calculated tag with the formula [devstatusNN], where NN is the device id (see Figure 2.14). The binding to devstatus is used for example. The tag to be used for the designated purpose may get the value from the real device or may be based on other tags. 522 522 523 - <h2id="s-annex">Appendix: FormulaReference<a class="anchor-icon" href="javascript:void(0)" onclick="copyAnchor('s-annex')" title="Copy link"><svg width="12" height="12" viewBox="0 0 16 16" fill="currentColor"><pathd="M7.775 3.275a.75.750001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.830.75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.53.5 0 00-4.95-4.95l-1.251.25zm-4.699.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z"/></svg></a></h2>249 +[[image:Screenshot 2025-12-10 at 21.59.17.png]] 524 524 525 - <p>Formulascan includearithmeticoperations,conditions,mathematical and specialfunctions,andpre-calculated measurements(up to threelevels of nesting).</p>251 +Fig. 2.14 - Calculated tag to create tag flashing on the diagram 526 526 527 - <div class="tbl-wrap"> 528 - <table class="rn-table"> 529 - <caption style="text-align:left;font-size:.8em;color:#555;padding:6px 0;font-weight:700;">Table A.1 — Variables in formulas</caption> 530 - <thead> 531 - <tr> 532 - <th style="min-width:160px;">Variable</th> 533 - <th>Description</th> 534 - </tr> 535 - </thead> 536 - <tbody> 537 - <tr><td><code>[tiN]</code></td><td>Current value of tag with ID N</td></tr> 538 - <tr><td><code>[prevN]</code></td><td>Previous value of the tag with ID N</td></tr> 539 - <tr><td><code>[statusN]</code></td><td>Current status of tag with ID N</td></tr> 540 - <tr><td><code>[prevstatusN]</code></td><td>Previous status of tag with ID N</td></tr> 541 - <tr><td><code>[lasttimeN]</code></td><td>Current timestamp of the tag with ID N</td></tr> 542 - <tr><td><code>[beforetimeN]</code></td><td>Previous timestamp of the tag with ID N</td></tr> 543 - <tr><td><code>[devstatusN]</code></td><td>Current device status: 0 = disabled; 1 = normal; 2 = at least one TI with abnormal quality; 3 = polling error (unavailable); 4 = manual input; 7 = waiting for data</td></tr> 544 - <tr><td><code>[devprevstatusN]</code><br><code>[prevdevstatusN]</code></td><td>Previous device status (same status codes as above)</td></tr> 545 - <tr><td><code>[devlastdtN]</code></td><td>Time when the latest device data was received</td></tr> 546 - <tr><td><code>[devpingtimeN]</code></td><td>Response time (ms) to ICMP ping of device N</td></tr> 547 - <tr><td><code>[connectedN]</code></td><td>Connection with device N restored</td></tr> 548 - <tr><td><code>[!connectedN]</code></td><td>Connection with device N is lost</td></tr> 549 - </tbody> 550 - </table> 551 - </div> 253 +C) Set up an object on the diagram, in the rules of which the calculated tag from point b will be applied (see Fig. 2.15). 552 552 255 +[[image:Screenshot 2025-12-10 at 21.59.53.png]] 553 553 554 - <div class="tbl-wrap"> 555 - <table class="rn-table"> 556 - <caption style="text-align:left;font-size:.8em;color:#555;padding:6px 0;font-weight:700;">Table A.2 — Operators in formulas</caption> 557 - <thead> 558 - <tr> 559 - <th style="min-width:80px;">Operator</th> 560 - <th>Description</th> 561 - <th>Example</th> 562 - <th>Result</th> 563 - </tr> 564 - </thead> 565 - <tbody> 566 - <tr><td><code>+</code></td><td>Addition</td><td><code>5 + 5</code></td><td>10</td></tr> 567 - <tr><td><code>-</code></td><td>Subtraction</td><td><code>5 - 3</code></td><td>2</td></tr> 568 - <tr><td><code>*</code></td><td>Multiplication</td><td><code>0.01 * [val]</code></td><td>0.01 × val</td></tr> 569 - <tr><td><code>/</code></td><td>Division</td><td><code>[val] / 1000</code></td><td>val / 1000</td></tr> 570 - <tr><td><code>%</code></td><td>Modulo (remainder)</td><td><code>10 % 3</code></td><td>1</td></tr> 571 - <tr><td><code>=</code></td><td>Assigns a value to a tag</td><td><code>[ti123] = 5</code></td><td>5</td></tr> 572 - <tr><td><code>==</code></td><td>Equal (returns true/false)</td><td><code>2 == 2</code></td><td>true</td></tr> 573 - <tr><td><code><, >, <=, >=</code></td><td>Arithmetic comparison</td><td><code>2 >= 3</code></td><td>false</td></tr> 574 - <tr><td><code>&&</code>, <code>&</code>, <code>AND</code>, <code>and</code></td><td>Logical AND</td><td><code>(devstatus1==1) AND (devstatus2==1)</code></td><td>true if both</td></tr> 575 - <tr><td><code>||</code>, <code>|</code>, <code>OR</code>, <code>or</code></td><td>Logical OR</td><td><code>(devstatus1==3) OR (devstatus2==3)</code></td><td>true if either</td></tr> 576 - </tbody> 577 - </table> 578 - </div> 257 +Figure 2.15 - Example rules with the tag created in step b. 579 579 259 +D) After saving the diagram and updating the configuration, if the status of the NN device changes, the system will start it flashing on the diagram until acknowledged. 580 580 581 - <div class="parent-topic">Parenttopic:<ahref="[[CENTOManuals>>doc:CENTO Manuals.WebHome]]">CENTOManuals</a></div>261 +**2. Flashing by the information model object** 582 582 583 - </div><!--/doc-content-->263 +For this method to work, the information model should be configured, and the required information model object should be selected in the event setting (**Object** field). In this case, the diagram object should be active (see more details in the "Diagrams Development Manual") and bound to the information model object selected in the event. 584 584 585 -<nav class="doc-toc"> 586 - <div class="toc-header"> 587 - <strong>On This Page</strong> 588 - <button class="toc-toggle" id="toc-tog" title="Collapse">«</button> 589 - </div> 590 - <ul id="toc-list"> 591 - <li class="tl1"><a href="#s-intro" data-toc>1. Introduction</a></li> 592 - <li class="tl1"><a href="#s-events" data-toc>2. CENTO Events</a></li> 593 - <li class="tl2"><a href="#s-event-editor" data-toc>2.1. Event editor</a></li> 594 - <li class="tl2"><a href="#s-event-create" data-toc>2.2. Creating events (UI)</a></li> 595 - <li class="tl2"><a href="#s-event-excel" data-toc>2.3. Creating events (Excel)</a></li> 596 - <li class="tl2"><a href="#s-event-flash" data-toc>2.4. Flashing on diagram</a></li> 597 - <li class="tl1"><a href="#s-notifications" data-toc>3. Notifications</a></li> 598 - <li class="tl2"><a href="#s-notif-create" data-toc>3.1. Creating notifications</a></li> 599 - <li class="tl2"><a href="#s-notif-logic" data-toc>3.2. Notification logic</a></li> 600 - <li class="tl1"><a href="#s-sound-editor" data-toc>4. Sound Editor</a></li> 601 - <li class="tl1"><a href="#s-examples" data-toc>5. Examples</a></li> 602 - <li class="tl1"><a href="#s-annex" data-toc>Appendix: Formulas</a></li> 603 - </ul> 604 -</nav> 265 +Let us consider an example of this solution. 605 605 606 - </div><!--/doc-wrap-->267 +A) Create an event with the selected object of the information model in the **Object** field (see Fig. 2.15).[[image:Screenshot 2025-12-10 at 22.01.01.png]] 607 607 608 -<script> 609 -(function(){ 610 - var bar=document.getElementById('rn-prog'); 611 - var top=document.getElementById('rn-top'); 612 - window.addEventListener('scroll',function(){ 613 - var d=document.documentElement; 614 - var pct=d.scrollTop/(d.scrollHeight-d.clientHeight); 615 - bar.style.width=(pct*100)+'%'; 616 - d.scrollTop>280?top.classList.add('on'):top.classList.remove('on'); 617 - },{passive:true}); 618 - var links=Array.from(document.querySelectorAll('[data-toc]')); 619 - var secs=links.map(function(a){return{el:document.getElementById(a.getAttribute('href').slice(1)),a:a};}).filter(function(s){return s.el;}); 620 - var busy=false; 621 - var obs=new IntersectionObserver(function(entries){ 622 - if(busy)return; 623 - entries.forEach(function(e){ 624 - if(!e.isIntersecting)return; 625 - var i=secs.findIndex(function(s){return s.el===e.target;}); 626 - if(i<0)return; 627 - secs.forEach(function(s){s.a.classList.remove('toc-on');}); 628 - secs[i].a.classList.add('toc-on'); 629 - var toc=document.querySelector('.doc-toc'); 630 - var link=secs[i].a; 631 - toc.scrollTop=link.offsetTop-toc.offsetTop-toc.clientHeight/2+link.clientHeight/2; 632 - }); 633 - },{rootMargin:'-8% 0px -60% 0px',threshold:0}); 634 - secs.forEach(function(s){obs.observe(s.el);}); 635 - links.forEach(function(a){ 636 - a.addEventListener('click',function(e){ 637 - var id=a.getAttribute('href').slice(1); 638 - var el=document.getElementById(id); 639 - if(!el)return; 640 - e.preventDefault(); 641 - busy=true; 642 - secs.forEach(function(s){s.a.classList.remove('toc-on');}); 643 - a.classList.add('toc-on'); 644 - el.scrollIntoView({behavior:'smooth',block:'start'}); 645 - setTimeout(function(){busy=false;},900); 646 - }); 647 - }); 648 - var tocList=document.getElementById('toc-list'); 649 - var togBtn=document.getElementById('toc-tog'); 650 - var collapsed=false; 651 - togBtn&&togBtn.addEventListener('click',function(){ 652 - collapsed=!collapsed; 653 - tocList.style.display=collapsed?'none':''; 654 - togBtn.textContent=collapsed?'»':'«'; 655 - }); 656 - var lb=document.getElementById('rn-lb'); 657 - var lbI=document.getElementById('rn-lb-img'); 658 - var lbC=document.getElementById('rn-lb-cap'); 659 - window.openLightbox=function(img){lbI.src=img.src;lbI.alt=img.alt;lbC.textContent=img.alt;lb.classList.add('open');document.body.style.overflow='hidden';}; 660 - window.closeLightbox=function(){lb.classList.remove('open');document.body.style.overflow='';}; 661 - lb.addEventListener('click',function(e){if(e.target===lb)closeLightbox();}); 662 - document.addEventListener('keydown',function(e){if(e.key==='Escape')closeLightbox();}); 663 - var toast=document.getElementById('rn-toast'); 664 - var t; 665 - window.copyAnchor=function(id){ 666 - var url=location.href.split('#')[0]+'#'+id; 667 - if(navigator.clipboard)navigator.clipboard.writeText(url).catch(function(){}); 668 - else{var x=document.createElement('textarea');x.value=url;document.body.appendChild(x);x.select();document.execCommand('copy');document.body.removeChild(x);} 669 - toast.classList.add('on');clearTimeout(t);t=setTimeout(function(){toast.classList.remove('on');},1600); 670 - }; 671 - (function(){ 672 - var toc=document.querySelector('.doc-toc'); 673 - var wrap=document.querySelector('.doc-wrap'); 674 - if(!toc||!wrap)return; 675 - var navbar=document.querySelector('.navbar,nav.navbar,#topBar,header'); 676 - var navH=navbar?navbar.offsetHeight:0; 677 - var footer=document.querySelector('footer,.xwikifooter,#xwikifooter,.bottombar,.sticky-container'); 678 - function update(){ 679 - var wr=wrap.getBoundingClientRect(); 680 - if(wr.top<=navH){ 681 - var footerTop=footer?footer.getBoundingClientRect().top:window.innerHeight; 682 - var h=Math.max(0,Math.min(window.innerHeight,footerTop)-navH); 683 - toc.classList.add('is-fixed');toc.style.top=navH+'px';toc.style.left=(wr.right-200)+'px';toc.style.height=h+'px'; 684 - }else{toc.classList.remove('is-fixed');toc.style.top=toc.style.left=toc.style.height='';} 685 - } 686 - requestAnimationFrame(function(){requestAnimationFrame(function(){update();window.addEventListener('scroll',update,{passive:true});window.addEventListener('resize',update,{passive:true});});}); 687 - })(); 688 -})(); 689 -</script> 690 -{{/html}} 269 +Fig. 2.15 - Creating an event with the information model object. 270 + 271 +B) Create an active object on the diagram bound to the object of the information model, which was selected in the event settings (see Fig. 2.16). 272 + 273 +[[image:Screenshot 2025-12-10 at 22.02.05.png]] 274 + 275 +Fig. 2.16 - Creating a diagram object bound to the information model. 276 + 277 += 3. NOTIFICATIONS SETTINGS = 278 + 279 +== 3.1. Creating and editing notifications == 280 + 281 +CENTO has the function to notify users about an event triggered via e-mail. 282 + 283 +To configure notifications, go to the /CENTO/web/ui/notifications_configuration/index page (menu item Settings > Events > Notifications (see Fig. 2.1). The configuration of the mail server is described in the "Setup Manual, Mail servers". 284 + 285 + 286 +[[image:Screenshot 2025-12-10 at 22.03.45.png]] 287 + 288 +Fig. 3.1 - Notifications interface 289 + 290 +In the interface presented, the user has the ability to: 291 + 292 +~1. Create notifications; 293 + 294 +2. Edit notifications. 295 + 296 +The notification table has the following columns. 297 + 298 +1. **Name **is the name of the notification. 299 +1. **Emails **are the e-mail addresses that have been configured to receive notifications. 300 +1. **Dispatch period **is the time of the day allowed for sending notifications. 301 +1. **Iteration period** is the minimum time interval between notifications, meaning notifications cannot be sent to the recipient more frequently than this set period. 302 +1. **Operation threshold **is the number of event triggers required before a notification is sent. 303 +1. **State **is on/off. 304 +1. **Actions** are operations available to the user that can be performed in response to an event (edit [[image:Screenshot 2025-12-10 at 22.05.05.png||height="25" width="27"]], copy [[image:Screenshot 2025-12-10 at 22.05.32.png||height="26" width="26"]], delete [[image:Screenshot 2025-12-10 at 22.05.55.png||height="26" width="23"]]). 305 + 306 + 307 + 308 + 309 + 310 +
- Screenshot 2025-12-10 at 22.17.31.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Lana - Size
-
... ... @@ -1,1 +1,0 @@ 1 -73.8 KB - Content
- Screenshot 2025-12-10 at 22.19.25.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Lana - Size
-
... ... @@ -1,1 +1,0 @@ 1 -78.0 KB - Content