Skip to Content

Changes for page 8. Control Setup Manual

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

Summary

Details

Page properties
Content
... ... @@ -1,6 +1,6 @@
1 1  = CONTENT =
2 2  
3 -{{toc /}}
3 +{{toc/}}
4 4  
5 5  = 1. INTRODUCTION =
6 6  
... ... @@ -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]]
25 +[[image:Screenshot 2025-12-17 at 16.28.40.png||height="441" width="1445"]]
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]]
29 +[[image:Screenshot 2025-12-17 at 16.29.26.png||height="584" width="1424"]]
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]]
41 +[[image:Screenshot 2025-12-17 at 16.31.55.png||height="315" width="1392"]]
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]]
49 +[[image:Screenshot 2025-12-17 at 16.32.27.png||height="313" width="1382"]]
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]]
55 +[[image:Screenshot 2025-12-17 at 16.33.06.png||height="263" width="1368"]]
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]]
84 +[[image:Screenshot 2025-12-17 at 16.38.45.png||height="386" width="633"]]
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]]
88 +[[image:Screenshot 2025-12-17 at 16.39.12.png||height="384" width="628"]]
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]]
112 +[[image:Screenshot 2025-12-17 at 16.40.14.png||height="461" width="622"]]
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]]
116 +[[image:Screenshot 2025-12-17 at 16.41.11.png||height="286" width="309"]]
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]]
126 +[[image:Screenshot 2025-12-17 at 16.41.51.png||height="168" width="313"]]
127 127  
128 128  Figure 3.1.5. Modbus control function
129 129  
... ... @@ -135,23 +135,23 @@
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]]
138 +[[image:Screenshot 2025-12-17 at 16.42.23.png||height="198" width="319"]]
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]]
142 +[[image:Screenshot 2025-12-17 at 16.43.58.png||height="316" width="317"]]
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]]
148 +[[image:Screenshot 2025-12-17 at 16.44.29.png||height="149" width="530"]]
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]]
154 +[[image:Screenshot 2025-12-17 at 16.45.36.png||height="371" width="598"]]
155 155  
156 156  Figure 3.1.9. Configuring control for OPCDA protocol
157 157  
... ... @@ -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]]
168 +[[image:Screenshot 2025-12-17 at 16.51.23.png||height="261" width="950"]]
169 169  
170 -[[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"]]
171 171  
172 172  Figure. 3.2.2. Table of tags
173 173  
... ... @@ -181,7 +181,7 @@
181 181  * **Control resolution** field specifies whether the ability to send write commands is enabled.
182 182  * **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).
183 183  
184 -[[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"]]
185 185  
186 186  Figure 3.2.3. ID Directory write function
187 187  
... ... @@ -231,7 +231,7 @@
231 231  
232 232  Check the created //Write value// class on the classes editor page:
233 233  
234 -[[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"]]
235 235  
236 236  Figure 3.3.2. Class Write value with attributes in the web-interface of the IM editor
237 237  
... ... @@ -243,31 +243,31 @@
243 243  
244 244  Check the created //Motor// class on the classes editor page:
245 245  
246 -[[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"]]
247 247  
248 248  Figure 3.3.4. Class Motor with attributes in the web-interface of the IM editor
249 249  
250 250  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.
251 251  
252 -[[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"]]
253 253  
254 254  Figure 3.3.5. Configuring the Control in the Information Model (object editor)
255 255  
256 256  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:
257 257  
258 -[[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"]]
259 259  
260 260  Figure 3.3.6. Configuring IM directory
261 261  
262 262  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).
263 263  
264 -[[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"]]
265 265  
266 266  Figure 3.3.7. Table of IM directories
267 267  
268 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.
269 269  
270 -[[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"]]
271 271  
272 272  Figure 3.3.8. IM directory
273 273  
... ... @@ -277,7 +277,7 @@
277 277  
278 278  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)
279 279  
280 -[[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"]]
281 281  
282 282  Figure 3.3.9. Adding remote control attributes to the Switch class
283 283  
... ... @@ -287,13 +287,13 @@
287 287  * telecontrol_off_ti – Tag ID for switching the object off;
288 288  * telecontrolled – flag indicating whether the object can be controlled (TRUTH – remote control is available, FALSE – not available).
289 289  
290 -[[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"]]
291 291  
292 292  Figure 3.3.10. Configuring Switch remote control via Excel
293 293  
294 294  Remote control can also be configured in the Information Model Editor (see Fig. 3.3.11).
295 295  
296 -[[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"]]
297 297  
298 298  Figure 3.3.11. Configuring switch remote control via the web editor
299 299  
... ... @@ -301,25 +301,25 @@
301 301  
302 302  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):
303 303  
304 -[[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"]]
305 305  
306 306  Figure 3.3.12. Telecontrol (remote control) class with attributes
307 307  
308 308  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:
309 309  
310 -[[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"]]
311 311  
312 312  Figure 3.3.13. Class attributes with the type Telecontrol
313 313  
314 314  Fig. 3.3.14 shows an example of a configured IM object with multiple remote control commands:
315 315  
316 -[[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"]]
317 317  
318 318  Figure 3.3.14. IM object with multiple telecontrol commands
319 319  
320 320  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:
321 321  
322 -[[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"]]
323 323  
324 324  Figure 3.3.15. IM object on the diagram with multiple remote control commands
325 325  
... ... @@ -337,19 +337,19 @@
337 337  
338 338  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.
339 339  
340 -[[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"]]
341 341  
342 342  Figure 3.3.17. Configuring an object with control without entering password
343 343  
344 344  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).
345 345  
346 -[[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"]]
347 347  
348 348  Figure 3.3.18. Configuring the attribute for password-free control
349 349  
350 350  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.
351 351  
352 -[[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"]]
353 353  
354 354  Figure 3.3.19. Configuring object for control without entering password
355 355  
... ... @@ -362,7 +362,7 @@
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]]
365 +[[image:Screenshot 2025-12-17 at 17.34.12.png||height="568" width="1045"]]
366 366  
367 367  Figure 3.3.20. Attributes for remote control permission
368 368  
... ... @@ -394,8 +394,8 @@
394 394  
395 395  [[image:Screenshot 2025-12-17 at 17.38.57.png]]
396 396  
397 -[[image:Screenshot 2025-12-17 at 17.42.19.png]]
397 + [[image:Screenshot 2025-12-17 at 17.42.19.png]]
398 398  
399 -[[image:Screenshot 2025-12-17 at 17.41.38.png]]
399 + [[image:Screenshot 2025-12-17 at 17.41.38.png]]
400 400  
401 -[[image:Screenshot 2025-12-17 at 17.42.37.png]]
401 + [[image:Screenshot 2025-12-17 at 17.42.37.png]]
Screenshot 2025-12-17 at 17.49.23.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +67.0 KB
Content
Screenshot 2025-12-17 at 17.49.44.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +68.0 KB
Content
Screenshot 2025-12-17 at 17.50.00.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +65.9 KB
Content