Skip to Content

Changes for page 8. Control Setup Manual

Last modified by Iaroslav Platonov on 2026/06/09 11:18
From version 53.1
edited by Lana
on 2025/12/17 20:41
Change comment: Uploaded new attachment "Screenshot 2025-12-17 at 17.41.38.png", version {1}
To version 57.4
edited by Lana
on 2025/12/17 20:47
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,5 +1,7 @@
1 1  = CONTENT =
2 2  
3 +{{toc/}}
4 +
3 3  = 1. INTRODUCTION =
4 4  
5 5  CENTO is a multifunctional software platform for data acquisition, processing and display. This manual describes how to configure the CENTO user tool Control.
... ... @@ -20,11 +20,11 @@
20 20  
21 21  **C** is an abbreviation for //Control//. **TC** is an abbreviation for Remote //control.// In CENTO software, //Control// refers to sending a non-negative integer value to a device, while Remote //control //refers to sending a discrete signal.
22 22  
23 -[[image:Screenshot 2025-12-17 at 16.28.40.png]]
25 +[[image:Screenshot 2025-12-17 at 16.28.40.png||height="441" width="1445"]]
24 24  
25 25  Figure 2.1. Tags with remote control enabled
26 26  
27 -[[image:Screenshot 2025-12-17 at 16.29.26.png]]
29 +[[image:Screenshot 2025-12-17 at 16.29.26.png||height="584" width="1424"]]
28 28  
29 29  Figure 2.2. Tags with control and remote control enabled
30 30  
... ... @@ -36,7 +36,7 @@
36 36  
37 37  To proceed, enter the account password. After successful authentication, a modal window appears allowing to specify the value to be written to the device (see Fig. 2.4).
38 38  
39 -[[image:Screenshot 2025-12-17 at 16.31.55.png]]
41 +[[image:Screenshot 2025-12-17 at 16.31.55.png||height="315" width="1392"]]
40 40  
41 41  Figure 2.4. Entering value for control
42 42  
... ... @@ -44,13 +44,13 @@
44 44  
45 45  Next, confirm the entered value by clicking **Execute** to initiate the control command and write the value to the device. Alternatively, click **Cancel,** to cancel the operation (see Fig. 2.5).
46 46  
47 -[[image:Screenshot 2025-12-17 at 16.32.27.png]]
49 +[[image:Screenshot 2025-12-17 at 16.32.27.png||height="313" width="1382"]]
48 48  
49 49  Figure 2.5. Confirmation of the command to write a value
50 50  
51 51  Clicking **TC** also opens a password prompt window. After successful authentication, a command selection window appears (see Fig. 2.6). As with the Control, a confirmation window follows the selected command.
52 52  
53 -[[image:Screenshot 2025-12-17 at 16.33.06.png]]
55 +[[image:Screenshot 2025-12-17 at 16.33.06.png||height="263" width="1368"]]
54 54  
55 55  Figure 2.6. Selecting command for remote control
56 56  
... ... @@ -79,11 +79,11 @@
79 79  
80 80  In the Remote **control **field, select the appropriate ASDU type for the control command from the drop-down list (see Fig. 3.1.4).
81 81  
82 -[[image:Screenshot 2025-12-17 at 16.38.45.png]]
84 +[[image:Screenshot 2025-12-17 at 16.38.45.png||height="386" width="633"]]
83 83  
84 84  Figure 3.1.1. Setting remote control via Modbus protocol
85 85  
86 -[[image:Screenshot 2025-12-17 at 16.39.12.png]]
88 +[[image:Screenshot 2025-12-17 at 16.39.12.png||height="384" width="628"]]
87 87  
88 88  Figure 3.1.2. Setting remote control via IEC-104 protocol
89 89  
... ... @@ -107,11 +107,11 @@
107 107  
108 108  2) The //Control// function is available for Modbus TCP (Modbus RTU over TCP) protocols (see Fig. 3.1.3 ), and OPC DA (see Fig. 3.1.9).
109 109  
110 -[[image:Screenshot 2025-12-17 at 16.40.14.png]]
112 +[[image:Screenshot 2025-12-17 at 16.40.14.png||height="461" width="622"]]
111 111  
112 112  Figure 3.1.3. Setting  control for Modbus protocol
113 113  
114 -[[image:Screenshot 2025-12-17 at 16.41.11.png]]
116 +[[image:Screenshot 2025-12-17 at 16.41.11.png||height="286" width="309"]]
115 115  
116 116  Figure 3.1.4. Remote control for IEC-104
117 117  
... ... @@ -121,7 +121,7 @@
121 121  
122 122  The **Function** field selects the Modbus recording function from the drop-down list (see Fig. 3.1.5).
123 123  
124 -[[image:Screenshot 2025-12-17 at 16.41.51.png]]
126 +[[image:Screenshot 2025-12-17 at 16.41.51.png||height="168" width="313"]]
125 125  
126 126  Figure 3.1.5. Modbus control function
127 127  
... ... @@ -133,29 +133,29 @@
133 133  
134 134  The field **Byte order** from the drop-down list (see Fig. 3.1.6) is used to select different order of bytes and/or words in the written CENTO data.
135 135  
136 -[[image:Screenshot 2025-12-17 at 16.42.23.png]]
138 +[[image:Screenshot 2025-12-17 at 16.42.23.png||height="198" width="319"]]
137 137  
138 138  In the **Device Tag Data Type** field, select the data type used by the device to store values from the drop-down list (see the device manual for details) (see Fig. 3.1.7).
139 139  
140 -[[image:Screenshot 2025-12-17 at 16.43.58.png]]
142 +[[image:Screenshot 2025-12-17 at 16.43.58.png||height="316" width="317"]]
141 141  
142 142  Fig. 3.1.7. Device Tag Data Type
143 143  
144 144  In the **Transformation** block, a linear transformation is applied to convert a physical quantity into a value to be recorded, using defined upper and lower limits for both. These limits establish the valid ranges for the physical quantity and its corresponding recorded value, within which data can be filled in (see Fig. 3.1.8).
145 145  
146 -[[image:Screenshot 2025-12-17 at 16.44.29.png]]
148 +[[image:Screenshot 2025-12-17 at 16.44.29.png||height="149" width="530"]]
147 147  
148 148  Figure 3.1.8. Transformation block
149 149  
150 150  In devices using the OPC DA protocol, the control function is easier to configure. In the settings, enable **Write values**, select the device tag data type, and define the necessary transformations (see Fig. 3.1.9).
151 151  
152 -[[image:Screenshot 2025-12-17 at 16.45.36.png]]
154 +[[image:Screenshot 2025-12-17 at 16.45.36.png||height="371" width="598"]]
153 153  
154 154  Figure 3.1.9. Configuring control for OPCDA protocol
155 155  
156 156  == 3.2. Setting control using MS Excel ==
157 157  
158 -To configure **Control **for a tag polled via the required protocol using Excel, download a configuration template. To do this, navigate to Settings > Configuration files in the CENTO interface. The **Import/Export configuration file** page opens (see Fig. 3.2.1). In the **Tags and Channels** section, click** Download** to download the template file.
160 +To configure **Control **for a tag polled via the required protocol using Excel, download a configuration template. To do this, navigate to Settings > Configuration files in the CENTO interface. The **Import/Export configuration file** page opens (see Fig. 3.2.1). In the **Tags and Channels** section, click** Download** to download the template file.
159 159  
160 160  [[image:Screenshot 2025-12-17 at 16.50.31.png]]
161 161  
... ... @@ -163,9 +163,9 @@
163 163  
164 164  Next, open the previously downloaded file, which contains a list of all tags used in CENTO. The details for setting these tags are outlined in the corresponding manual for configuring tags and devices based on the selected protocol.
165 165  
166 -[[image:Screenshot 2025-12-17 at 16.51.23.png]]
168 +[[image:Screenshot 2025-12-17 at 16.51.23.png||height="261" width="950"]]
167 167  
168 -[[image:Screenshot 2025-12-17 at 16.51.40.png]]
170 +[[image:Screenshot 2025-12-17 at 16.51.40.png||height="319" width="954"]]
169 169  
170 170  Figure. 3.2.2. Table of tags
171 171  
... ... @@ -179,7 +179,7 @@
179 179  * **Control resolution** field specifies whether the ability to send write commands is enabled.
180 180  * **Write function **is completed according to the device manual. The mapping between write functions and their identifiers is provided on the //ID Directory //sheet (see Fig. 3.2.3).
181 181  
182 -[[image:Screenshot 2025-12-17 at 16.52.25.png]]
184 +[[image:Screenshot 2025-12-17 at 16.52.25.png||height="332" width="641"]]
183 183  
184 184  Figure 3.2.3. ID Directory write function
185 185  
... ... @@ -225,11 +225,11 @@
225 225  This class has four attributes to be specified exactly as shown in Figure 3.3.1:
226 226  
227 227  * **Tag ID **is a mandatory field;
228 -* Optional fields include the lower and upper limits of values, which define the range within which any values can be entered. The **Value variants** field is provided for convenience, allowing to select from predefined options instead of manually entering values. To use this feature, specify a reference to the directory in the **Type** column, such as// ref_value_variants //(see Fig. 3.3.6). This reference can then be used to select the desired numeric parameters (see Fig. 3.3.7).
230 +* Optional fields include the lower and upper limits of values, which define the range within which any values can be entered. The **Value variants** field is provided for convenience, allowing to select from predefined options instead of manually entering values. To use this feature, specify a reference to the directory in the **Type** column, such as// ref_value_variants //(see Fig. 3.3.6). This reference can then be used to select the desired numeric parameters (see Fig. 3.3.7).
229 229  
230 230  Check the created //Write value// class on the classes editor page:
231 231  
232 -[[image:Screenshot 2025-12-17 at 16.55.17.png]]
234 +[[image:Screenshot 2025-12-17 at 16.55.17.png||height="597" width="1223"]]
233 233  
234 234  Figure 3.3.2. Class Write value with attributes in the web-interface of the IM editor
235 235  
... ... @@ -241,31 +241,31 @@
241 241  
242 242  Check the created //Motor// class on the classes editor page:
243 243  
244 -[[image:Screenshot 2025-12-17 at 16.56.24.png]]
246 +[[image:Screenshot 2025-12-17 at 16.56.24.png||height="337" width="1437"]]
245 245  
246 246  Figure 3.3.4. Class Motor with attributes in the web-interface of the IM editor
247 247  
248 248  In the IM object editor, create an object with the class //Motor//. In the **Attributes** table, set tag ID, upper and lower limits, value variants (if necessary, reference book is to be created) for configuring.
249 249  
250 -[[image:Screenshot 2025-12-17 at 16.56.55.png]]
252 +[[image:Screenshot 2025-12-17 at 16.56.55.png||height="480" width="1400"]]
251 251  
252 252  Figure 3.3.5. Configuring the Control in the Information Model (object editor)
253 253  
254 254  To add aliases of values for writing, download a template from the **Information model references** block (see Fig. 3.2.1). Next, open the downloaded file. On the sheet //Categories,// add the code of the directory and its name:
255 255  
256 -[[image:Screenshot 2025-12-17 at 16.57.33.png]]
258 +[[image:Screenshot 2025-12-17 at 16.57.33.png||height="133" width="444"]]
257 257  
258 258  Figure 3.3.6. Configuring IM directory
259 259  
260 260  The added directory should be placed on a separate Excel tab, with the tab name matching the directory code. The table structure for the directory should be copied from the provided templates, and the values for writing should be entered into it (see Fig. 3.3.7). These values can later be selected during control operations on the diagram (see the “User manual” for details).
261 261  
262 -[[image:Screenshot 2025-12-17 at 16.58.03.png]]
264 +[[image:Screenshot 2025-12-17 at 16.58.03.png||height="162" width="959"]]
263 263  
264 264  Figure 3.3.7. Table of IM directories
265 265  
266 -IM directories can also be configured using the web** Information Model editor** on the **Directories** tab. The directory shown in Fig. 3.3.7 is displayed in the web interface as illustrated in Fig. 3.3.8.
268 +IM directories can also be configured using the web** Information Model editor** on the **Directories** tab. The directory shown in Fig. 3.3.7 is displayed in the web interface as illustrated in Fig. 3.3.8.
267 267  
268 -[[image:Screenshot 2025-12-17 at 16.58.31.png]]
270 +[[image:Screenshot 2025-12-17 at 16.58.31.png||height="434" width="1427"]]
269 269  
270 270  Figure 3.3.8. IM directory
271 271  
... ... @@ -275,7 +275,7 @@
275 275  
276 276  If an IM object is intended for remote control from a diagram, the following system attributes are added to the object's class (see Fig. 3.3.9)
277 277  
278 -[[image:Screenshot 2025-12-17 at 16.59.06.png]]
280 +[[image:Screenshot 2025-12-17 at 16.59.06.png||height="156" width="749"]]
279 279  
280 280  Figure 3.3.9. Adding remote control attributes to the Switch class
281 281  
... ... @@ -285,13 +285,13 @@
285 285  * telecontrol_off_ti – Tag ID for switching the object off;
286 286  * telecontrolled – flag indicating whether the object can be controlled (TRUTH – remote control is available, FALSE – not available).
287 287  
288 -[[image:Screenshot 2025-12-17 at 16.59.40.png]]
290 +[[image:Screenshot 2025-12-17 at 16.59.40.png||height="240" width="1524"]]
289 289  
290 290  Figure 3.3.10. Configuring Switch remote control via Excel
291 291  
292 292  Remote control can also be configured in the Information Model Editor (see Fig. 3.3.11).
293 293  
294 -[[image:Screenshot 2025-12-17 at 17.02.42.png]]
296 +[[image:Screenshot 2025-12-17 at 17.02.42.png||height="543" width="1245"]]
295 295  
296 296  Figure 3.3.11. Configuring switch remote control via the web editor
297 297  
... ... @@ -299,25 +299,25 @@
299 299  
300 300  For objects with multiple telecontrol (remote control) commands, the IM includes a system class called //Telecontrol// (class code: telecontrol) with the following attributes (see Fig. 3.3.12):
301 301  
302 -[[image:Screenshot 2025-12-17 at 17.04.22.png]]
304 +[[image:Screenshot 2025-12-17 at 17.04.22.png||height="440" width="790"]]
303 303  
304 304  Figure 3.3.12. Telecontrol (remote control) class with attributes
305 305  
306 306  For an IM object requiring multiple remote control commands, a class should be created whose attributes reference the //Telecontrol// system class. An example of such a class is shown in Fig. 3.3.13:
307 307  
308 -[[image:Screenshot 2025-12-17 at 17.05.09.png]]
310 +[[image:Screenshot 2025-12-17 at 17.05.09.png||height="246" width="789"]]
309 309  
310 310  Figure 3.3.13. Class attributes with the type Telecontrol
311 311  
312 312  Fig. 3.3.14 shows an example of a configured IM object with multiple remote control commands:
313 313  
314 -[[image:Screenshot 2025-12-17 at 17.06.00.png]]
316 +[[image:Screenshot 2025-12-17 at 17.06.00.png||height="865" width="1203"]]
315 315  
316 316  Figure 3.3.14. IM object with multiple telecontrol commands
317 317  
318 318  Fig. 3.3.15 shows the drop-down menu of an active diagram element bound to the IM object configured as shown in Fig. 3.3.14:
319 319  
320 -[[image:Screenshot 2025-12-17 at 17.06.35.png]]
322 +[[image:Screenshot 2025-12-17 at 17.06.35.png||height="338" width="475"]]
321 321  
322 322  Figure 3.3.15. IM object on the diagram with multiple remote control commands
323 323  
... ... @@ -335,19 +335,19 @@
335 335  
336 336  Thus, when creating an object of the selected class (see Fig. 3.3.17), include the specified attribute in the value field and verify its functionality on the diagram.
337 337  
338 -[[image:Screenshot 2025-12-17 at 17.27.04.png]]
340 +[[image:Screenshot 2025-12-17 at 17.27.04.png||height="487" width="1045"]]
339 339  
340 340  Figure 3.3.17. Configuring an object with control without entering password
341 341  
342 342  To skip password entry during remote control, as with control, an attribute named //Skip password// (any name can be used) is to be added. This attribute should have the  //skip_password// code and the //bool// type(see Fig. 3.3.18).
343 343  
344 -[[image:Screenshot 2025-12-17 at 17.27.52.png]]
346 +[[image:Screenshot 2025-12-17 at 17.27.52.png||height="627" width="1051"]]
345 345  
346 346  Figure 3.3.18. Configuring the attribute for password-free control
347 347  
348 348  Next, for the object with remote control commands, this attribute, should be enabled as shown in Fig. 3.3.19, and the command sending on the diagram should be tested.
349 349  
350 -[[image:Screenshot 2025-12-17 at 17.32.18.png]]
352 +[[image:Screenshot 2025-12-17 at 17.32.18.png||height="567" width="1048"]]
351 351  
352 352  Figure 3.3.19. Configuring object for control without entering password
353 353  
... ... @@ -360,7 +360,7 @@
360 360  * **telecontrol_permit_on_ti** – permission to switch TC on;
361 361  * **telecontrol_permit_off_ti** – permission to switch TC off.
362 362  
363 -[[image:Screenshot 2025-12-17 at 17.34.12.png]]
365 +[[image:Screenshot 2025-12-17 at 17.34.12.png||height="568" width="1045"]]
364 364  
365 365  Figure 3.3.20. Attributes for remote control permission
366 366  
... ... @@ -392,3 +392,8 @@
392 392  
393 393  [[image:Screenshot 2025-12-17 at 17.38.57.png]]
394 394  
397 + [[image:Screenshot 2025-12-17 at 17.42.19.png]]
398 +
399 +[[image:Screenshot 2025-12-17 at 17.41.38.png]]
400 +
401 +[[image:Screenshot 2025-12-17 at 17.42.37.png]]
Screenshot 2025-12-17 at 17.42.19.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +56.7 KB
Content
Screenshot 2025-12-17 at 17.42.37.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +57.9 KB
Content