Changes for page 8. Control Setup Manual
Last modified by Iaroslav Platonov on 2026/06/09 11:18
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 10 removed)
- Screenshot 2025-12-17 at 17.37.11.png
- Screenshot 2025-12-17 at 17.38.23.png
- Screenshot 2025-12-17 at 17.38.44.png
- Screenshot 2025-12-17 at 17.38.57.png
- Screenshot 2025-12-17 at 17.39.30.png
- Screenshot 2025-12-17 at 17.40.05.png
- Screenshot 2025-12-17 at 17.40.35.png
- Screenshot 2025-12-17 at 17.41.38.png
- Screenshot 2025-12-17 at 17.42.19.png
- Screenshot 2025-12-17 at 17.42.37.png
Details
- Page properties
-
- Content
-
... ... @@ -1,7 +1,5 @@ 1 1 = CONTENT = 2 2 3 -{{toc/}} 4 - 5 5 = 1. INTRODUCTION = 6 6 7 7 CENTO is a multifunctional software platform for data acquisition, processing and display. This manual describes how to configure the CENTO user tool Control. ... ... @@ -22,11 +22,11 @@ 22 22 23 23 **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. 24 24 25 -[[image:Screenshot 2025-12-17 at 16.28.40.png ||height="441" width="1445"]]23 +[[image:Screenshot 2025-12-17 at 16.28.40.png]] 26 26 27 27 Figure 2.1. Tags with remote control enabled 28 28 29 -[[image:Screenshot 2025-12-17 at 16.29.26.png ||height="584" width="1424"]]27 +[[image:Screenshot 2025-12-17 at 16.29.26.png]] 30 30 31 31 Figure 2.2. Tags with control and remote control enabled 32 32 ... ... @@ -38,7 +38,7 @@ 38 38 39 39 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). 40 40 41 -[[image:Screenshot 2025-12-17 at 16.31.55.png ||height="315" width="1392"]]39 +[[image:Screenshot 2025-12-17 at 16.31.55.png]] 42 42 43 43 Figure 2.4. Entering value for control 44 44 ... ... @@ -46,13 +46,13 @@ 46 46 47 47 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). 48 48 49 -[[image:Screenshot 2025-12-17 at 16.32.27.png ||height="313" width="1382"]]47 +[[image:Screenshot 2025-12-17 at 16.32.27.png]] 50 50 51 51 Figure 2.5. Confirmation of the command to write a value 52 52 53 53 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. 54 54 55 -[[image:Screenshot 2025-12-17 at 16.33.06.png ||height="263" width="1368"]]53 +[[image:Screenshot 2025-12-17 at 16.33.06.png]] 56 56 57 57 Figure 2.6. Selecting command for remote control 58 58 ... ... @@ -81,11 +81,11 @@ 81 81 82 82 In the Remote **control **field, select the appropriate ASDU type for the control command from the drop-down list (see Fig. 3.1.4). 83 83 84 -[[image:Screenshot 2025-12-17 at 16.38.45.png ||height="386" width="633"]]82 +[[image:Screenshot 2025-12-17 at 16.38.45.png]] 85 85 86 86 Figure 3.1.1. Setting remote control via Modbus protocol 87 87 88 -[[image:Screenshot 2025-12-17 at 16.39.12.png ||height="384" width="628"]]86 +[[image:Screenshot 2025-12-17 at 16.39.12.png]] 89 89 90 90 Figure 3.1.2. Setting remote control via IEC-104 protocol 91 91 ... ... @@ -109,11 +109,11 @@ 109 109 110 110 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). 111 111 112 -[[image:Screenshot 2025-12-17 at 16.40.14.png ||height="461" width="622"]]110 +[[image:Screenshot 2025-12-17 at 16.40.14.png]] 113 113 114 114 Figure 3.1.3. Setting control for Modbus protocol 115 115 116 -[[image:Screenshot 2025-12-17 at 16.41.11.png ||height="286" width="309"]]114 +[[image:Screenshot 2025-12-17 at 16.41.11.png]] 117 117 118 118 Figure 3.1.4. Remote control for IEC-104 119 119 ... ... @@ -123,7 +123,7 @@ 123 123 124 124 The **Function** field selects the Modbus recording function from the drop-down list (see Fig. 3.1.5). 125 125 126 -[[image:Screenshot 2025-12-17 at 16.41.51.png ||height="168" width="313"]]124 +[[image:Screenshot 2025-12-17 at 16.41.51.png]] 127 127 128 128 Figure 3.1.5. Modbus control function 129 129 ... ... @@ -135,29 +135,29 @@ 135 135 136 136 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. 137 137 138 -[[image:Screenshot 2025-12-17 at 16.42.23.png ||height="198" width="319"]]136 +[[image:Screenshot 2025-12-17 at 16.42.23.png]] 139 139 140 140 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). 141 141 142 -[[image:Screenshot 2025-12-17 at 16.43.58.png ||height="316" width="317"]]140 +[[image:Screenshot 2025-12-17 at 16.43.58.png]] 143 143 144 144 Fig. 3.1.7. Device Tag Data Type 145 145 146 146 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). 147 147 148 -[[image:Screenshot 2025-12-17 at 16.44.29.png ||height="149" width="530"]]146 +[[image:Screenshot 2025-12-17 at 16.44.29.png]] 149 149 150 150 Figure 3.1.8. Transformation block 151 151 152 152 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). 153 153 154 -[[image:Screenshot 2025-12-17 at 16.45.36.png ||height="371" width="598"]]152 +[[image:Screenshot 2025-12-17 at 16.45.36.png]] 155 155 156 156 Figure 3.1.9. Configuring control for OPCDA protocol 157 157 158 158 == 3.2. Setting control using MS Excel == 159 159 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.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. 161 161 162 162 [[image:Screenshot 2025-12-17 at 16.50.31.png]] 163 163 ... ... @@ -165,9 +165,9 @@ 165 165 166 166 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. 167 167 168 -[[image:Screenshot 2025-12-17 at 16.51.23.png ||height="261" width="950"]]166 +[[image:Screenshot 2025-12-17 at 16.51.23.png]] 169 169 170 -[[image:Screenshot 2025-12-17 at 16.51.40.png ||height="319" width="954"]]168 +[[image:Screenshot 2025-12-17 at 16.51.40.png]] 171 171 172 172 Figure. 3.2.2. Table of tags 173 173 ... ... @@ -227,7 +227,7 @@ 227 227 This class has four attributes to be specified exactly as shown in Figure 3.3.1: 228 228 229 229 * **Tag ID **is a mandatory field; 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).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). 231 231 232 232 Check the created //Write value// class on the classes editor page: 233 233 ... ... @@ -265,7 +265,7 @@ 265 265 266 266 Figure 3.3.7. Table of IM directories 267 267 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.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. 269 269 270 270 [[image:Screenshot 2025-12-17 at 16.58.31.png]] 271 271 ... ... @@ -355,47 +355,11 @@ 355 355 356 356 === 3.3.2. Configuring permission for remote control === 357 357 358 -Before executing remotecontrol commands, some devices require an initial permission signal to be sent to a dedicated register. This signal enablesremotecontrol functionality. Only after this permission is granted the device accepts and process the mainremotecontrol commands.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. 359 359 360 -To implement this type of remotecontrol (TC) in CENTO, the following attributes are added to the object class (see Fig. 3.3.20):358 +To implement this type of telecontrol (TC) in CENTO, the following attributes are added to the object class (see Fig. 3.3.20): 361 361 362 362 * **telecontrol_permit_on_ti** – permission to switch TC on; 363 363 * **telecontrol_permit_off_ti** – permission to switch TC off. 364 364 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]] 363 +
- Screenshot 2025-12-17 at 17.37.11.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Lana - Size
-
... ... @@ -1,1 +1,0 @@ 1 -105.5 KB - Content
- Screenshot 2025-12-17 at 17.38.23.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Lana - Size
-
... ... @@ -1,1 +1,0 @@ 1 -67.7 KB - Content
- Screenshot 2025-12-17 at 17.38.44.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Lana - Size
-
... ... @@ -1,1 +1,0 @@ 1 -68.8 KB - Content
- Screenshot 2025-12-17 at 17.38.57.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Lana - Size
-
... ... @@ -1,1 +1,0 @@ 1 -66.7 KB - Content
- Screenshot 2025-12-17 at 17.39.30.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Lana - Size
-
... ... @@ -1,1 +1,0 @@ 1 -68.8 KB - Content
- Screenshot 2025-12-17 at 17.40.05.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Lana - Size
-
... ... @@ -1,1 +1,0 @@ 1 -12.2 KB - Content
- Screenshot 2025-12-17 at 17.40.35.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Lana - Size
-
... ... @@ -1,1 +1,0 @@ 1 -57.7 KB - Content
- Screenshot 2025-12-17 at 17.41.38.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Lana - Size
-
... ... @@ -1,1 +1,0 @@ 1 -47.4 KB - Content
- Screenshot 2025-12-17 at 17.42.19.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Lana - Size
-
... ... @@ -1,1 +1,0 @@ 1 -56.7 KB - Content
- Screenshot 2025-12-17 at 17.42.37.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Lana - Size
-
... ... @@ -1,1 +1,0 @@ 1 -57.9 KB - Content