Skip to Content

Changes for page 8. Control Setup Manual

Last modified by Iaroslav Platonov on 2026/06/09 11:18
From version 45.1
edited by Lana
on 2025/12/17 20:35
Change comment: Uploaded new attachment "Screenshot 2025-12-17 at 17.35.21.png", version {1}
To version 57.1
edited by Lana
on 2025/12/17 20:43
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.
... ... @@ -155,7 +155,7 @@
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  
... ... @@ -225,7 +225,7 @@
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  
... ... @@ -263,7 +263,7 @@
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 268  [[image:Screenshot 2025-12-17 at 16.58.31.png]]
269 269  
... ... @@ -353,11 +353,47 @@
353 353  
354 354  === 3.3.2. Configuring permission for remote control ===
355 355  
356 -Before executing control commands, some devices require an initial permission signal to be sent to a dedicated register. This signal enables telecontrol functionality. Only after this permission is granted the device accepts and process the main telecontrol commands.
358 +Before executing remote control commands, some devices require an initial permission signal to be sent to a dedicated register. This signal enables remote control functionality. Only after this permission is granted the device accepts and process the main remote control commands.
357 357  
358 -To implement this type of telecontrol (TC) in CENTO, the following attributes are added to the object class (see Fig. 3.3.20):
360 +To implement this type of remote control (TC) in CENTO, the following attributes are added to the object class (see Fig. 3.3.20):
359 359  
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 -
365 +[[image:Screenshot 2025-12-17 at 17.34.12.png]]
366 +
367 +Figure 3.3.20. Attributes for remote control permission
368 +
369 +The system assigns the IDs of the corresponding tags to these attributes of the IM object. These tags are configured to send a signal to the register that enables remote control (see Fig. 3.3.21)
370 +
371 +[[image:Screenshot 2025-12-17 at 17.34.50.png]]
372 +
373 +Figure 3.3.21. Configuration of attributes for enabling telecontrol
374 +
375 +When an object uses the system class //Telecontrol// to send control commands, the permission-related attributes are designated as //permit_on_tag// and //permit_off_tag// (see Fig. 3.3.22):
376 +
377 +[[image:Screenshot 2025-12-17 at 17.35.21.png]]
378 +
379 +Figure 3.3.22. Attributes for enabling remote control
380 +
381 +In some devices, a single tag handles this function, while in others, two separate tags perform it. These tags are configured similarly to those used for direct remote control, differing only in the register address (see Fig. 3.3.23):
382 +
383 +[[image:Screenshot 2025-12-17 at 17.37.11.png]]
384 +
385 +Figure 3.3.23. Tag configuration for telecontrol permission
386 +
387 +Thus, after adding the attributes //telecontrol_permit_on_ti// and //telecontrol_permit_off_ti//, configuring the tags, and assigning them to the IM object, CENTO software first sends the remote control permission command before transmitting the actual remote control command.
388 +
389 += 4. RECOMMENDED SETTINGS AND SPECIAL CASES =
390 +
391 +[[image:Screenshot 2025-12-17 at 17.38.23.png]]
392 +
393 +[[image:Screenshot 2025-12-17 at 17.38.44.png]]
394 +
395 +[[image:Screenshot 2025-12-17 at 17.38.57.png]]
396 +
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.37.11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +105.5 KB
Content
Screenshot 2025-12-17 at 17.38.23.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +67.7 KB
Content
Screenshot 2025-12-17 at 17.38.44.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +68.8 KB
Content
Screenshot 2025-12-17 at 17.38.57.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +66.7 KB
Content
Screenshot 2025-12-17 at 17.39.30.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +68.8 KB
Content
Screenshot 2025-12-17 at 17.40.05.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +12.2 KB
Content
Screenshot 2025-12-17 at 17.40.35.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +57.7 KB
Content
Screenshot 2025-12-17 at 17.41.38.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +47.4 KB
Content
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