Wiki source code of Setup Guide
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
| |
4.2 | 1 | **CONTENT** |
| |
1.1 | 2 | |
| |
10.2 | 3 | == **1. INTRODUCTION** == |
| 4 | |||
| 5 | CENTO is a multifunctional software platform for data collection, processing, and display. | ||
| |
5.1 | 6 | CENTO can be used to build various automated systems, for example: dispatching, control, accounting, diagnostics, etc. |
| 7 | This guide describes the general steps for setting up CENTO software, as well as links to other instructions. | ||
| |
10.2 | 8 | |
| 9 | == **2. DEVICES, TAGS, CHANNELS** == | ||
| 10 | |||
| 11 | Operations for configuring the CENTO software are performed from the drop-down menu "Settings" (see Fig. 2.1) of the control panel at the top of the CENTO graphical interface. | ||
| |
16.1 | 12 | \\[[image:1762536204394-536.png||height="430" width="212"]] |
| |
7.2 | 13 | Fig. 2.1 – Settings drop-down menu |
| |
9.2 | 14 | |
| |
12.1 | 15 | === 2.1. Creating a device tree === |
| |
10.2 | 16 | |
| |
12.1 | 17 | Configuration begins with the creation of a tree of devices (sources of information). The device tree is formed based on the convenience of further work with this tree and can reflect either the structure and names of the places where information sources are installed, or (in the case of small projects) combine information sources and production facilities of the enterprise. This tree is necessary for the subsequent attribution of all sources of information and the information itself to this structure. |
| 18 | |||
| 19 | To configure the structure, go to the "Devices, tags, channels" page (Settings – Devices, tags, channels) (see Fig. 2.2). | ||
| 20 | |||
| |
84.1 | 21 | [[image:Screenshot 2025-11-09 at 20.07.38.png||height="150" width="1018"]] |
| |
15.2 | 22 | |
| |
18.2 | 23 | Fig. 2.2 – Devices, Tags, Channels Page |
| |
15.2 | 24 | |
| |
18.2 | 25 | By default, CENTO has a "Root Object" preset. Under the root object, you can specify, for example, the name of a company or a separate object. In order to rename a tree element, you need to hover the mouse pointer over it and right-click, and then select "Edit" (see Fig. 2.3). You can also delete an unnecessary object by clicking on the button [[image:1762746580637-301.png]] |
| |
15.2 | 26 | |
| 27 | |||
| |
47.2 | 28 | [[image:Screenshot 2025-11-09 at 20.06.44.png||height="332" width="501"]] |
| |
45.2 | 29 | |
| |
18.2 | 30 | Fig. 2.3 – Editing an object |
| 31 | |||
| 32 | **Attention! There must be no tethered devices in the power facility for removal.** | ||
| 33 | |||
| 34 | |||
| 35 | Adding objects in the structure (name of the system or enterprise) is performed by right-clicking (hereinafter referred to as the "RMB") on: | ||
| 36 | |||
| |
21.2 | 37 | * Selected object in the tree, in which case the new object will be nested; |
| 38 | * In the empty space of a given tree, in this case, the new object will be an independent object in this structure. | ||
| |
18.2 | 39 | |
| |
21.2 | 40 | The sequence and nesting of objects in the tree can be adjusted by dragging objects by holding down the left mouse button (see Fig. 2.4), as well as by using [[image:1762746645908-483.png]] and [[image:1762746672090-269.png]]selecting the desired object in the tree (see Fig. 2.5). |
| |
18.2 | 41 | |
| |
45.2 | 42 | [[image:Screenshot 2025-11-09 at 20.05.39.png||height="213" width="499"]] |
| |
23.2 | 43 | |
| 44 | Fig. 2.4 – Dragging a New Object Inside the Tree | ||
| 45 | |||
| |
45.2 | 46 | [[image:Screenshot 2025-11-09 at 20.05.00.png||height="407" width="496"]] |
| |
23.2 | 47 | |
| 48 | Fig. 2.5 – Dragging a New Object Inside the Tree | ||
| 49 | |||
| |
28.2 | 50 | To select all objects, click on the button [[image:1762746768528-956.png]] , and it will change its appearance to [[image:1762746794500-389.png]]. To reset the selection of all objects in the tree, click on this button again [[image:1762746812138-731.png]]. To collapse the tree, click on , and [[image:1762746841632-572.png]] to expand it [[image:1762746869342-141.png]]. To change the width of the tree, you need to hover over the vertical line, and drag right/left while holding down the click and click. |
| |
23.2 | 51 | |
| |
29.2 | 52 | The search input field [[image:1762746912120-741.png]] allows you to search for information by the name of the tree object, the name of the device, as well as its ID or Code. |
| 53 | |||
| 54 | Adding and configuring power facilities to CENTO is possible both through the above-described WEB-interface and using Excel files. Loading the CENTO configuration via Excel files is described in Section 3 of this guide. | ||
| 55 | |||
| |
31.2 | 56 | === 2.2. Creating devices === |
| |
29.2 | 57 | |
| |
31.2 | 58 | You can create new devices (information sources) and edit existing ones on the "Devices, tags, channels" page ("Settings" – "Devices, tags, channels") (see Fig. 2.6). |
| |
29.2 | 59 | |
| |
44.2 | 60 | [[image:Screenshot 2025-11-09 at 20.04.03.png]] |
| |
31.2 | 61 | |
| 62 | Fig. 2.6 – Devices page | ||
| 63 | |||
| 64 | On this page, you can perform the following operations: | ||
| 65 | |||
| |
38.2 | 66 | * Creating a device by clicking the button [[image:1762747055524-817.png||height="22" width="94"]] in the upper right corner of the screen; |
| 67 | * downloading/uploading selected devices to an Excel file by pressing a button [[image:1762747071069-512.png||height="21" width="88"]] , which allows you to configure devices for scanning without uploading the entire configuration on the page from section 3; | ||
| |
36.2 | 68 | * go to the device editing window by left-clicking on the device name or its ID; |
| 69 | * search for an already configured device by selecting in the object tree and searching for devices in these objects manually or through filters in the headers of the device table, where [[image:1762747071070-762.png||height="25" width="30"]] it searches by ID or by Code, depending on the user's choice; | ||
| 70 | * enabling and disabling device polling by switches in the "Status" column; | ||
| 71 | * viewing the status of the device and polling it according to the configured protocols; | ||
| |
38.2 | 72 | * copying an untagged device [[image:1762747071070-928.png||height="24" width="24"]] with its tags [[image:1762747071070-641.png||height="25" width="24"]] and deleting devices [[image:1762747071071-408.png||height="23" width="23"]] ; |
| |
36.2 | 73 | * filter by category; |
| 74 | * filter by formula; | ||
| 75 | * filter by device. | ||
| |
31.2 | 76 | |
| |
38.2 | 77 | Clicking on the button will open the [[image:1762747182802-715.png||height="26" width="110"]] "Create a device" page, where you need to enter the parameters of the new device (see Fig. 2.7). |
| |
31.2 | 78 | |
| |
42.2 | 79 | [[image:Screenshot 2025-11-09 at 20.02.13.png]] |
| |
40.2 | 80 | |
| |
42.2 | 81 | Fig. 2.7 – Device Creation Page |
| 82 | |||
| |
40.2 | 83 | In order to edit an already configured device, click on its name on the "Devices" page, which will take you to the "Device Editing" page (see Fig. 2.8). |
| 84 | |||
| 85 | To speed up the creation of a device group, CENTO has the function of copying devices with all their settings by clicking the button [[image:1762747218001-134.png||height="27" width="27"]] on the "Devices, tags, channels" page (see Fig. 2.6). Next, you need to change the configuration in accordance with the project, also going to the "Edit device" page. | ||
| 86 | |||
| |
41.2 | 87 | [[image:Screenshot 2025-11-09 at 20.01.08.png]] |
| 88 | |||
| 89 | Fig. 2.8 – Device Editing Page | ||
| 90 | |||
| |
48.2 | 91 | The "Create Device" window ("Edit Device") consists of 2 blocks. The first block "General settings" has the same view for all devices. In the second block, you are asked to select and enter settings for the device polling protocol. For each device, it is possible to poll according to 2 or more protocols, for example, for electricity meters (polling real-time parameters, downloading archives of accumulated interval values of electricity) (see Fig. 2.8). |
| 92 | |||
| 93 | The "General settings" block contains the following fields: | ||
| 94 | |||
| |
60.1 | 95 | [[image:Screenshot 2025-11-09 at 20.32.16.png||height="57" width="240"]] |
| |
48.2 | 96 | |
| |
84.1 | 97 | Device name. |
| |
48.2 | 98 | |
| |
66.2 | 99 | [[image:Screenshot 2025-11-09 at 20.23.37.png||height="57" width="232"]] |
| |
60.1 | 100 | |
| |
84.1 | 101 | Select a template that corresponds to the selected device from the drop-down list or create a new one using the "+" button. |
| |
60.1 | 102 | |
| 103 | [[image:Screenshot 2025-11-09 at 20.26.11.png||height="58" width="235"]] | ||
| 104 | |||
| |
84.1 | 105 | Identification number of the device in the system (by default, it is set automatically). |
| |
60.1 | 106 | |
| 107 | [[image:Screenshot 2025-11-09 at 20.27.03.png||height="59" width="240"]] | ||
| 108 | |||
| |
84.1 | 109 | IP address of the device. |
| |
60.1 | 110 | |
| 111 | [[image:Screenshot 2025-11-09 at 20.28.08.png||height="58" width="240"]] | ||
| 112 | |||
| |
84.1 | 113 | Serial number (for electricity meters). |
| |
60.1 | 114 | |
| 115 | [[image:Screenshot 2025-11-09 at 20.29.00.png||height="57" width="241"]] | ||
| 116 | |||
| |
84.1 | 117 | The object to which the device belongs. |
| |
60.1 | 118 | |
| 119 | [[image:Screenshot 2025-11-09 at 20.30.58.png||height="74" width="242"]] | ||
| 120 | |||
| |
84.1 | 121 | Stores a note on the device. |
| |
60.1 | 122 | |
| 123 | [[image:Screenshot 2025-11-09 at 20.31.47.png||height="57" width="243"]] | ||
| 124 | |||
| |
84.1 | 125 | Binding the device to the object of the information model. |
| |
60.1 | 126 | |
| 127 | [[image:Screenshot 2025-11-09 at 20.33.17.png||height="29" width="129"]] | ||
| 128 | |||
| 129 | Allows you to replace the existing device with a new one, saving the metering data (after clicking, an additional window with instructions pops up, see Fig. 2.9). | ||
| 130 | |||
| 131 | [[image:Screenshot 2025-11-09 at 20.34.00.png||height="364" width="720"]] | ||
| 132 | |||
| 133 | Fig. 2.9 – Window "Replacement of the metering device" | ||
| 134 | |||
| |
66.2 | 135 | After filling in the required fields, you should click on the "Save" button. |
| 136 | |||
| 137 | Then, to apply the changes, you need to click the "Update Configuration" button in the drop-down menu in the upper right corner of the page. | ||
| 138 | |||
| 139 | Adding devices and configuring protocols to CENTO is possible both through the above-described WEB-interface and using Excel files. Loading the CENTO configuration via Excel files is described in Section 3 of this guide. | ||
| 140 | |||
| 141 | The rules and features of setting up devices and protocols are described in separate commissioning manuals. | ||
| 142 | |||
| 143 | After you add a new device, it appears in the device tree on the Devices page. The device name in the tree and in the device table may be preceded by one of the following icons ("statuses"), which are described in Table 2.1. | ||
| 144 | |||
| 145 | Table 2.1 – Device status decoding | ||
| 146 | |||
| 147 | |Status Number|Device Status|Decoding | ||
| 148 | |0|[[image:1762749353292-521.png]]|Disabled (device polling disabled in CENTO) | ||
| 149 | |1|[[image:1762749353293-182.png]]|Normal (the device is connected, tags arrive without errors) | ||
| 150 | |2|[[image:1762749353293-752.png]]|Data in the device with errors (some tags come with errors or are not polled) | ||
| 151 | |3|[[image:1762749353293-611.png]]|Device is not available (device polling is enabled, but the device is not responding) | ||
| 152 | |4|[[image:1762749353293-609.png]]|Tags or channels by device contain data with manual input | ||
| 153 | |9|[[image:1762749353294-893.png]]|Status Not Available (Status Not Yet Received or Not Available) | ||
| 154 | |||
| |
67.2 | 155 | === 2.3. Set up tags and channels === |
| |
66.2 | 156 | |
| |
67.2 | 157 | In CENTO software, information is divided into 2 types: tags and channels. |
| |
66.2 | 158 | |
| |
67.2 | 159 | Tags are data, conditionally, "real-time". That is, data collected from sources of information with the lowest possible delays. The frequency of updating the value of each tag depends on the settings you set, the technical features of the data sources, and their capabilities. For example, in dispatching systems, data is updated once per second, but it can be both more frequent and less frequent (for example, it may depend on how much the value itself has changed). |
| |
66.2 | 160 | |
| 161 | Channels are data used for metering (electricity, other energy resources, operating time, products, etc.). A feature of metering channels is a clearly defined discreteness of information (for example: 1 minute, 3 minutes, 30 minutes, 1 hour, etc.). The value of the channel is recorded as an increment of a value for a given period, averaging for a given period and a value at the end of the period. In metering systems, information is most often transmitted in this form by the data sources themselves (meters, heat calculators, etc.), but accounting channels can also be formed in CENTO itself based on tag values. The use of information in the form of "channels" in accounting allows you to receive information from data sources even in case of failures in communication channels (data can be obtained from the archive after the connection is restored), it is convenient to work with data, and generate various reports. | ||
| 162 | |||
| 163 | Tags and accounting channels are configured on the same page "Devices, tags, channels" ("Settings" - "Devices, tags, channels") on the "Tags, channels" tab (see Fig. 2.10). | ||
| |
67.2 | 164 | |
| |
72.2 | 165 | [[image:Screenshot 2025-11-09 at 20.38.04.png]] |
| 166 | |||
| 167 | Fig. 2.10 – Parameter Description Page | ||
| 168 | |||
| 169 | On the "Tags, Channels" tab, when selecting one or more devices, all tags and channels of device data accounting are displayed in a tabular form. In this table, you can perform the following operations for each signal separately: | ||
| 170 | |||
| 171 | * Create a tag or channel by clicking [[image:1762749527914-134.png||height="20" width="117"]] the button in the upper right corner of the screen. | ||
| 172 | * the button [[image:1762749527915-501.png||height="21" width="69"]] allows you to export data on selected tags to an excel table, completely repeating columns and rows from "Tags, channels", while this uploaded file serves only for analysis, not configuration; | ||
| 173 | * The button [[image:1762749527915-879.png||height="21" width="85"]] allows you to upload/download an Excel file with selected tags, in which you can remove/add tags to specific devices without downloading the entire configuration from the page from section 3 of this manual; | ||
| 174 | * Go to the tag or channel editing window by clicking the left mouse button on the tag name or its ID; | ||
| 175 | * viewing the values of tags and channels and going to the graph page of the required parameter by clicking the left mouse button on the value; | ||
| 176 | * enabling and disabling tag (channel) polling by radio buttons in the "Status" column; | ||
| 177 | * viewing the status of the tag (channel) and its polling; | ||
| 178 | * viewing the time of the last update of the tag (channel) survey – the date and time (in the format "yy-mm-dd hh:mm:ss") of the last successful receipt of the tag (channel) value (the value of the tag or channel itself may not have changed); | ||
| |
84.1 | 179 | * copying and deleting tags and channels by clicking buttons [[image:1762749562010-279.png||height="25" width="25"]] and [[image:1762749562011-728.png||height="24" width="24"]] respectively. |
| |
72.2 | 180 | |
| |
84.1 | 181 | ==== 2.3.1. Adding a protocol tag ==== |
| 182 | |||
| 183 | To create a separate tag, click on the "Create Tag" button. This will open the "Tag Polling Creation" page (see Figure 2.11). | ||
| 184 | |||
| 185 | To display the protocol settings, you must first select the device (data source). After that, a set of protocols configured for the device will appear in the "Protocol" drop-down list (see p.2.2). | ||
| 186 | |||
| 187 | [[image:Screenshot 2025-11-09 at 20.42.20.png]] | ||
| 188 | |||
| 189 | Fig. 2.11 – Adding a protocol tag | ||
| 190 | |||
| 191 | The "Tag Polling Creation" window consists of 4 blocks. The first block "General settings" contains the settings of the protocol that is configured in the device for which the tag is created. The second block contains the settings of the protocol through which the tag is passed (appears when the protocol is selected). The third block contains functions for processing the value of the tag. In the fourth block, the tag settings are configured, which determine the permissible limits of its change and the system's reaction to violation of these limits. | ||
| 192 | |||
| |
88.3 | 193 | ---- |
| 194 | |||
| |
84.1 | 195 | The "General settings" block contains the following fields: |
| 196 | |||
| 197 | [[image:Screenshot 2025-11-09 at 20.43.37.png||height="51" width="258"]] | ||
| 198 | |||
| 199 | Parameter name (set by the user). | ||
| 200 | |||
| 201 | [[image:Screenshot 2025-11-09 at 20.44.12.png||height="51" width="257"]] | ||
| 202 | |||
| 203 | Selection of the parameter category. | ||
| 204 | |||
| 205 | [[image:Screenshot 2025-11-09 at 20.45.47.png||height="51" width="257"]] | ||
| 206 | |||
| 207 | The alphabetic code of the tag, which can be used instead of ID (it is possible to enter numbers, Latin letters and the symbol _ ). | ||
| 208 | |||
| 209 | [[image:Screenshot 2025-11-09 at 20.46.25.png||height="51" width="257"]] | ||
| 210 | |||
| 211 | The identity address of the parameter. Default is set automatically, and can be changed. | ||
| 212 | |||
| 213 | [[image:Screenshot 2025-11-09 at 20.47.06.png||height="49" width="125"]] | ||
| 214 | |||
| 215 | Units of measurement of the parameter. | ||
| 216 | |||
| 217 | [[image:Screenshot 2025-11-09 at 20.47.38.png||height="53" width="255"]] | ||
| 218 | |||
| 219 | The device from which the parameter is read. | ||
| 220 | |||
| 221 | [[image:Screenshot 2025-11-09 at 20.49.12.png||height="53" width="258"]] | ||
| 222 | |||
| 223 | Protocol used (the list of protocols is formed from the configured protocols for the selected device). | ||
| 224 | |||
| 225 | [[image:Screenshot 2025-11-09 at 20.49.50.png||height="58" width="98"]] | ||
| 226 | |||
| 227 | Affects the appearance of charting on the "Live Data" analysis page, if the tag is analog, then the switch should be like in the picture. | ||
| 228 | |||
| 229 | [[image:Screenshot 2025-11-09 at 20.50.20.png||height="70" width="254"]] | ||
| 230 | |||
| 231 | Stores a note on the tag, does not affect the survey. | ||
| 232 | |||
| 233 | [[image:Screenshot 2025-11-09 at 20.51.17.png||height="57" width="115"]] | ||
| 234 | |||
| 235 | Appears for tags with a protocol, saves the history of changing values. When the "Save to database" function is disabled, tag data is not transferred to the backup server and is not transmitted via the S2S protocol. | ||
| 236 | |||
| 237 | Depending on the selected device, the protocol specified when creating the device will be automatically selected in the "Protocol" field. | ||
| 238 | |||
| 239 | The rules, description, and specifics of setting up tags in terms of protocols are described in separate setup manuals. | ||
| 240 | |||
| |
88.3 | 241 | ---- |
| 242 | |||
| |
85.2 | 243 | The "Processing" block contains the following fields: |
| 244 | |||
| |
85.3 | 245 | [[image:Screenshot 2025-11-09 at 21.34.56.png||height="60" width="289"]] |
| |
85.2 | 246 | |
| |
87.2 | 247 | The formula for mathematical processing of the parameter (according to a predetermined formula or the user's formula). Clicking on the "+" opens the window for creating a new formula, which then appears in the list of templates. |
| |
85.2 | 248 | |
| |
87.2 | 249 | [[image:Screenshot 2025-11-09 at 21.36.47.png||height="18" width="139"]] |
| 250 | |||
| 251 | [[image:Screenshot 2025-11-09 at 21.37.18.png]] | ||
| 252 | |||
| |
88.2 | 253 | A field for entering a custom formula, not from the list of templates. |
| |
87.2 | 254 | |
| |
88.2 | 255 | [[image:Screenshot 2025-11-09 at 21.41.53.png||height="26" width="158"]] |
| 256 | |||
| 257 | Button to open help with formulas. | ||
| 258 | |||
| 259 | ---- | ||
| 260 | |||
| 261 | The "Setpoints" block contains settings for the following limits: | ||
| 262 | |||
| 263 | * upper physical limit | ||
| 264 | * a lower physical limit | ||
| 265 | * upper emergency limit | ||
| 266 | * lower emergency limit | ||
| 267 | * upper warning limit | ||
| 268 | * Lower warning limit. | ||
| 269 | |||
| |
90.2 | 270 | ---- |
| |
88.3 | 271 | |
| |
90.2 | 272 | Each of the above limits has the following settings: |
| |
88.3 | 273 | |
| |
90.2 | 274 | [[image:Screenshot 2025-11-09 at 21.44.56.png||height="66" width="49"]] |
| 275 | |||
| 276 | Enabling/disabling value control. | ||
| 277 | |||
| |
91.2 | 278 | [[image:Screenshot 2025-11-09 at 21.45.38.png||height="66" width="111"]] |
| |
90.2 | 279 | |
| |
91.2 | 280 | Limit value in units specified by the tag. |
| 281 | |||
| |
93.2 | 282 | [[image:Screenshot 2025-11-09 at 21.46.31.png||height="66" width="111"]] |
| |
91.2 | 283 | |
| |
93.2 | 284 | Exposure time in milliseconds before the setpoint is triggered. |
| |
91.2 | 285 | |
| |
93.2 | 286 | [[image:Screenshot 2025-11-09 at 21.47.13.png||height="66" width="111"]] |
| 287 | |||
| 288 | Enabling/disabling the acknowledgment of the event that occurs when the setpoint is triggered. | ||
| 289 | |||
| 290 | To save the tag settings, click the button [[image:1762753677285-432.png]] | ||
| 291 | |||
| |
93.3 | 292 | Then, to apply the changes, you need to click the "Update Configuration" button in the drop-down menu in the upper right corner of the page. |
| 293 | |||
| 294 | Adding tags to CENTO is possible both through the above-described web interface and using Excel files. Loading the CENTO configuration via Excel files is described in Section 3 of this guide. | ||
| 295 | |||
| 296 | The rules and specifics for setting up tags for different protocols and devices are described in separate configuration guides. | ||
| 297 | |||
| |
101.2 | 298 | ==== 2.3.2. Add a calculation tag ==== |
| |
93.3 | 299 | |
| 300 | If you select the "No log" item in the "Tag Polling Description" window (see Fig. 2.11) in the "Log" field, a calculated tag will be created, the value of which can be formed based on the transformation of other tags. | ||
| 301 | |||
| 302 | The value of the calculated tag is determined by the formula entered in the "Value Processing Formula" field (see Fig. 2.11) or by the Custom Formula (see Fig. 2.12). Examples of formulas are given under the Value Processing Formula field. The available features are also listed in Table 2.1 of this manual. | ||
| 303 | |||
| 304 | For calculation tags, setpoints can be configured in the same way as tags with protocols. | ||
| |
94.2 | 305 | |
| 306 | After filling in the required fields, you should save the changes by clicking the button [[image:1762753769568-573.png||height="23" width="60"]]. Then, to apply the changes, you need to click the "Update Configuration" button in the drop-down menu in the upper right corner of the page. | ||
| 307 | |||
| 308 | Adding calculation tags to CENTO, as well as other configuration elements, is possible through the above-described web interface and using Excel files. Loading the CENTO configuration via Excel files is described in Section 3 of this guide. | ||
| 309 | |||
| |
101.1 | 310 | ==== 2.3.3. Setting up calculation formulas ==== |
| 311 | |||
| 312 | For calculated tags (see section 2.3.2), different processing formulas are used. If you use the same type of formulas for a number of tags, you should make a description of these formulas so that you can use them to process any required tag. | ||
| 313 | |||
| 314 | You can add new formulas and adjust existing formulas on the Tag Polling Description page (Settings – Devices, Tags, Channels, Tags, Channels tab). | ||
| 315 | |||
| 316 | [[image:Screenshot 2025-11-09 at 21.51.34.png||height="251" width="253"]] | ||
| 317 | |||
| 318 | Fig. 2.12 – Editing Formula Templates | ||
| 319 | |||
| 320 | To adjust the existing formula, you should: | ||
| 321 | |||
| 322 | * click on the "Template" field to open the list of available formula templates and use the mouse wheel to find the desired formula (see Fig. 2.12) | ||
| 323 | * hover over it until the "edit" and "delete" symbols appear [[image:1762753922390-602.png||height="21" width="168"]] | ||
| 324 | * if the template needs to be deleted, click on the "Delete" icon | ||
| 325 | * if the template needs to be corrected, click on the "Edit" icon | ||
| 326 | * The Edit Formula window opens (see Figure 2.13), where you can change the name of the formula in the Name field, and you can change the formula itself in the Formula field. There is also a hint with examples in the window | ||
| 327 | * To save the changes, click the button [[image:1762753922390-303.png||height="21" width="55"]] | ||
| 328 | |||
| 329 | [[image:Screenshot 2025-11-09 at 21.53.06.png||height="607" width="397"]] | ||
| 330 | |||
| 331 | Fig. 2.13– Edit Formulas Page | ||
| 332 | |||
| 333 | To add a new formula, on the Tag Polling Description page, click the button [[image:1762754032495-106.png||height="25" width="27"]] | ||
| 334 | |||
| 335 | [[image:Screenshot 2025-11-09 at 21.54.20.png||height="600" width="402"]] | ||
| 336 | |||
| 337 | Fig. 2.14– Formula Creation Page | ||
| 338 | |||
| 339 | On the "Formula Creation" page that opens (see Fig. 2.14), you need to enter the name of the new formula and the formula itself in the "Formula" field. | ||
| 340 | |||
| 341 | In the expression of the formula, arithmetic operations, conditions, calls of mathematical and special functions, etc., are allowed. | ||
| 342 | |||
| 343 | The functions used in the formulas are described in Table 2.2. | ||
| 344 | |||
| 345 | Table 2.2 – Functions used in formulas. | ||
| 346 | |||
| 347 | |Function|Description|Use|Result | ||
| 348 | |Bit|Returns the value of a single specified bit|Bit(4,2)|1 | ||
| 349 | |Bits|Returns the value of multiple specified bits|Bits(12,2,2)|3 | ||
| 350 | |if|Returns a value based on whether or not a specified condition is met.|if(3-2 = 1, 'value is true', 'value is false')|'value is true' | ||
| 351 | |(% rowspan="2" %)Pow|(% rowspan="2" %)Returns a value raised to the specified power.|Pow(3, 2)|9 | ||
| 352 | |Pow([dev-101-ea_imp],2)|((( | ||
| 353 | Dev-101-ea_imp=6 | ||
| 354 | |||
| 355 | 36 | ||
| 356 | ))) | ||
| 357 | |(% rowspan="2" %)Round|(% rowspan="2" %)Rounding a value to the nearest integer or a certain number of decimal places.|Round(3.222, 2)|3.22 | ||
| 358 | |Round([dev-101-ea_imp],1)|((( | ||
| 359 | Dev-101-ea_imp=6.66 | ||
| 360 | |||
| 361 | 6.6 | ||
| 362 | ))) | ||
| 363 | |agg|Aggregates all tag values per interval by function. The result publishes to the timestamp of the end of the interval|agg(mean, ti42, 3m) - average of tag 42 over 3 minutes|35 | ||
| 364 | |Abs|Returns the modulus //of a number//.|ABS(-1,234)|1,234 | ||
| 365 | |sign|Returns the sign of a //number// in the form 1~|0 ~|-1.|sign(-1,234)|-1 | ||
| 366 | |Sqrt|Returns the square root of a given number|Sqrt(4)|2 | ||
| 367 | |rndfloat|Returns a random real number from the range [0.0,1.0]|rndfloat()|0.123 | ||
| 368 | |rndintn|Returns a random integer from the range [0,n]|rndintn(5)|3 | ||
| 369 | |split|Splits a //row// by a given //separator// and returns a substring by //index//|split("02-01-2006 15:04",' ',1)|"15:04" | ||
| 370 | |parsetime|Returns the number of seconds since the beginning of the Unix epoch according to //the format// from //the string//|parsetime('yyyy-mm-dd hh:mi:ss', "2017-05-26 15:58:30")|1495814310 | ||
| 371 | |Time|Returns the current time in the specified format|time('dd.MM.yyyy HH:mi:ss')|16.04.2020 01:41:07 | ||
| 372 | |Unixepochformat|Converts the date from //seconds// since the beginning of the Unix era to a given //format//|Unixepochformat(1495814310, 'yyyy-mm-dd hh:mi:ss')|2017-05-26 15:58:30 | ||
| 373 | |acos|Returns the arccosine of the //number//.|acos(0)|90 | ||
| 374 | |asin|Returns the arc sine of //the number//.|asin(1)|90 | ||
| 375 | |atan|Returns the arctangent of the //number//.|atan(1)|45 | ||
| 376 | |atan2|Returns the arctangent for the specified //x// and //y coordinates//.|atan2(1, 0)|90 | ||
| 377 | |cos|Calculates the cosine of a //number//.|COS(60)|0.5 | ||
| 378 | |pi|Returns the value of Pi.|pi()|3.141592653589793 | ||
| 379 | |sin|Calculates the sine of a //number//.|sin(30)|0.5 | ||
| 380 | |tan|Calculates the tangent of the //number//.|tan(45)|1 | ||
| 381 | |First_1h, First_1d, First_1mon|Returns the value of the tag increment at the beginning of the current hour, day, and month|First_1h(ti10101)|32.26 | ||
| 382 | |(% rowspan="4" %)ticker(<spacing>, <expression1>, <expression2(optional)>)|(% rowspan="4" %)((( | ||
| 383 | Executes expression1 when the interval is triggered, or expression2 otherwise. Expression2 may be missing. In this case, the calculation will be made only at the moment of triggering the interval. | ||
| 384 | |||
| 385 | The interval can be set as a number - periodicity in seconds, or as a string in quotation marks - cron rule. | ||
| 386 | |||
| 387 | **If the formula contains prev, then you need to run the ticker using manual input and then reset it**. | ||
| 388 | )))|ticker(3, if(ti2==1, prev5+3, prev5)) - ti2 set counter to 1, which is updated every 3 seconds|60 sec | ||
| 389 | |ticker("0 0 8 * * *", 0, prev5+ti2-prev2) - accumulate tag changes with id 2 with a reset to 0 every day at 8 am|((( | ||
| 390 | at 7:59 – ticker = 100 sec. | ||
| 391 | |||
| 392 | at 8:00 – ticker = 0 sec. | ||
| 393 | ))) | ||
| 394 | |((( | ||
| 395 | ticker("0 0 0 * * *", ti2, prev1) - the accumulation of tag changes from id 2 at the beginning of the day. | ||
| 396 | |||
| 397 | In this formula, you can specify //a specific time, as well as the day, month, and days of the week.// | ||
| 398 | )))|((( | ||
| 399 | If at 00:00:00 ti2=120 minutes, then the ticker during this day will be equal to 120 minutes. | ||
| 400 | |||
| |
94.2 | 401 | |
| |
101.1 | 402 | ))) |
| 403 | |((( | ||
| 404 | ticker("0 0 0 1 * *", ti2, prev1) - accumulation of tag changes from id 2 at the beginning of the month. | ||
| 405 | |||
| 406 | |||
| 407 | )))|((( | ||
| 408 | If on the 1st day of the month at 00:00:00 ti2=200 minutes, then the ticker during this month will be 200 minutes. | ||
| 409 | |||
| 410 | |||
| 411 | ))) | ||
| 412 | |||
| |
101.2 | 413 | Permissible variable designations in formulas are given in Table 2.3. |
| |
101.1 | 414 | |
| |
101.2 | 415 | Table 2.3 – Designation of variables in formulas. |
| |
101.1 | 416 | |
| |
101.2 | 417 | |Variable|Description |
| 418 | |[val]|Current value of the telemeter from BDRV | ||
| 419 | |[x1], [x2], ...|The binding of these variables is determined when describing the calculated parameters in the "Parameters" column. | ||
| 420 | |((( | ||
| 421 | [tiN], | ||
| |
101.1 | 422 | |
| |
101.2 | 423 | where N is the serial number of the TI |
| 424 | )))|The meaning of telemetering from the BDRV | ||
| 425 | |((( | ||
| 426 | [devstatusN], | ||
| 427 | |||
| 428 | where N is the device number (ID) | ||
| 429 | )))|Device status (0 – disabled in the configuration; 1 – normal; 2 – at least one TUE has abnormal quality (out of bounds or error in the formula); 3 – device polling error (device is not available); 4 – manual input is present in the tags or channels of the device, 9 – no status). | ||
| 430 | |((( | ||
| 431 | [devprevstatusN] or [prevdevstatusN] | ||
| 432 | |||
| 433 | where N is the device number (ID) | ||
| 434 | )))|Previous device status (0 – disabled in the configuration; 1 – normal; 2 – at least one TUE has abnormal quality (out of bounds or error in the formula); 3 – device polling error (device not available); 4 – manual input is present in the tags or channels of the device, 9 – no status). | ||
| 435 | |((( | ||
| 436 | [prevN], | ||
| 437 | |||
| 438 | where N is the serial number of the TI | ||
| 439 | )))|Previous Value of Telemeter from BDRV | ||
| 440 | |||
| |
113.2 | 441 | ==== 2.3.4. Configuring calculation channels ==== |
| |
101.2 | 442 | |
| |
113.2 | 443 | CENTO has the ability to create calculated accounting channels. A calculated channel can be created either based on the values of other channels or on the basis of tag values. In order to create a calculation channel, you need to go to the link "Settings" - "Devices, tags, channels" - "Calculation channels" (see Fig. 2.15). |
| 444 | |||
| 445 | [[image:Screenshot 2025-11-09 at 21.58.58.png]] | ||
| 446 | |||
| 447 | Fig.2.15 – List of calculation channels | ||
| 448 | |||
| 449 | On the "Billing channels" tab, when you select one or more devices, all billing channels for metering these devices are displayed in a tabular form. In this table, you can perform the following operations for each parameter separately: | ||
| 450 | |||
| 451 | * Create a channel by pressing a button [[image:1762754384286-528.png||height="24" width="121"]] and [[image:1762754384287-151.png||height="26" width="114"]] in the upper right corner of the screen. | ||
| 452 | * Go to the channel editing window by left-clicking on the tag name or tag ID. | ||
| 453 | * View channel values and go to the graph page of the required parameter by clicking the left mouse button on the value. | ||
| 454 | * enabling and disabling channel polling by switches in the "Status" column. | ||
| 455 | * viewing the status of the settlement channel. | ||
| 456 | * viewing the time of the last update of the tag (channel) poll – the date and time (in the format "yyyy-mm-dd hh:mm:ss") of the last successful receipt of the tag (channel) value (the tag or channel value itself may not have changed). | ||
| 457 | * copying and deleting channels by pressing buttons [[image:1762754384287-453.png||height="21" width="21"]] and [[image:1762754384287-190.png||height="22" width="22"]] respectively | ||
| 458 | * preliminary check of the formula [[image:1762754384287-268.png||height="27" width="26"]] | ||
| 459 | * filter by category | ||
| 460 | * filter by formula | ||
| 461 | * filter by device. | ||
| 462 | |||
| 463 | More detailed use of calculation channels is described in the "Guide to setting up accounting channels". | ||
| 464 | |||
| 465 | == 3. CONFIGURING CENTO VIA EXCEL == | ||
| 466 | |||
| 467 | The CENTO software provides the ability to configure the system via Excel files. The interface of this functionality is located on the Downloading/Uploading Configuration Files page (Menu item "Settings" – "Configuration Files"). (see Fig. 3.1). | ||
| 468 | |||
| 469 | [[image:Screenshot 2025-11-09 at 22.02.21.png]] | ||
| 470 | |||
| 471 | Fig. 3.1– Download/Upload Configuration Files Page | ||
| 472 | |||
| 473 | With the help of Excel files, you can configure: | ||
| 474 | |||
| 475 | 1. Devices (also device tree and device types); | ||
| 476 | 1. Tags and channels; | ||
| 477 | 1. Events; | ||
| 478 | 1. Information model (classes, elements, reference books); | ||
| 479 | 1. Telecontrol Lock Conditions; | ||
| 480 | 1. Accounting Channels. | ||
| 481 | 1. Tabular data directories. | ||
| 482 | 1. Alarm event recorders. | ||
| 483 | |||
| 484 | A .xlsx file with strictly defined tabs and columns is uploaded from this page with a single button. File correction is possible both through Excel and through other programs that work with the .xlsx table format, for example, LibreOffice. With another button, these files are uploaded to the server. After downloading, you need to apply the changes made by clicking the "Update configuration" button in the drop-down menu in the upper right corner of the page, as in Fig.3.2. | ||
| 485 | |||
| 486 | [[image:Screenshot 2025-11-09 at 22.03.16.png||height="248" width="232"]] | ||
| 487 | |||
| 488 | Fig. 3.2– Update Configuration Button | ||
| 489 | |||
| 490 | In addition to the web interface, power facilities and device types can be edited through the "Devices" table. On the first tab "List of objects" there is a table as in Figure 3.3 | ||
| 491 | |||
| 492 | [[image:Screenshot 2025-11-09 at 22.04.17.png||height="194" width="384"]] | ||
| 493 | |||
| 494 | Fig. 3.3 – Table "List of objects" | ||
| 495 | |||
| 496 | The Object ID column contains unique numbers of the enterprise's power facilities. Their names are displayed in the "Object name" column. The "Parent Object ID" column determines where the power object will be located in the object tree, and if the cell is empty, then the object will lie at the root of the tree. Thus, the table shown in Figure 3.3 corresponds to the tree shown in Figure 3.4. | ||
| 497 | |||
| 498 | [[image:Screenshot 2025-11-09 at 22.05.26.png||height="300" width="238"]] | ||
| 499 | |||
| 500 | Fig. 3.4 – Tree of power facilities | ||
| 501 | |||
| 502 | The "Sorting" field determines where objects belonging to the same "parent" will be located relative to each other. | ||
| 503 | |||
| 504 | Adding new power facilities is carried out taking into account the ID of existing objects in the table. Object IDs must not be repeated. | ||
| 505 | |||
| 506 | The Device Types tab displays the device types available on the server (see Figure 3.5). | ||
| 507 | |||
| 508 | [[image:Screenshot 2025-11-09 at 22.06.17.png||height="286" width="268"]] | ||
| 509 | |||
| 510 | Fig. 3.5 – Table "Device Types" | ||
| 511 | |||
| 512 | The ID column of the device type displays the unique number of the device type, and the name column displays its name. To add new types, you must follow the numbering. | ||
| 513 | |||
| 514 | Editing other tabs in the Devices table and the Tags and Channels file is described in the setup guides for specific protocols and device types. | ||
| 515 | |||
| 516 | Setting up Events files is described in the Event System Configuration Guide. | ||
| 517 | |||
| 518 | The "Information Model Classes", "Information Model Elements" and "Information Model References" files are configured according to the "Information Model Setup Guide". | ||
| 519 | |||
| 520 | The rules for filling in the file "Telecontrol lock conditions" can be found in the "Remote Control Lock Settings Guide". | ||
| 521 | |||
| 522 | Working with accounting channels is described in the "Guide to setting up accounting channels". | ||
| 523 | |||
| 524 | The "Logger Settings" file is configured according to the "Alarm Event Recorder Configuration Guide". | ||
| 525 | |||
| 526 | "Tabular data references" are used in the mode calculation module, so their settings are specified in the "Mode Calculation Module Setup and Operation Manual". | ||
| 527 | |||
| 528 | == 4. EVENTS == | ||
| 529 | |||
| 530 | "Events" in CENTO are designed to increase the observability of the system by tracking changes in the state of process equipment, recording changes in the event log and alerting users. | ||
| 531 | |||
| 532 | Events help personnel to respond in a timely manner to changes in the technological process and system operation. | ||
| 533 | |||
| 534 | * Event settings are located in the "Event Editor" menu item (see Fig. 4.1). Events that are configured on this page are included in the archive log of technological events, as well as in the operational log. For a more detailed description of the Event Editor page and how to configure technology events, see the Event System Setup Guide. | ||
| 535 | |||
| 536 | [[image:Screenshot 2025-11-09 at 22.07.47.png]] |