Skip to Content

Changes for page 8. Control Setup Manual

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

Summary

Details

Page properties
Content
... ... @@ -310,3 +310,72 @@
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 +
314 +[[image:Screenshot 2025-12-17 at 17.06.00.png]]
315 +
316 +Figure 3.3.14. IM object with multiple telecontrol commands
317 +
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 +
320 +[[image:Screenshot 2025-12-17 at 17.06.35.png]]
321 +
322 +Figure 3.3.15. IM object on the diagram with multiple remote control commands
323 +
324 +The system class //Telecontrol// can also be used for objects with single remote control commands. Attribute configuration is done in the same way – simply add a Telecontrol attribute to the remote control object, as shown in Fig. 3.3.13.
325 +
326 +3.3.1. Setting up control and remote control without password
327 +
328 +In standard operation, sending control and remote control signals requires user password entry. However, in certain cases, this level of security may be excessive. To accommodate such scenarios, the CENTO software includes a setting that allows //Control without password.//
329 +
330 +Control without password is configured using the diagram (i.e., via the Information Model). To enable this, add the attribute Control without password with the code //skip_password// and the bool type to the class of the control object (see Fig. 3.3.16).
331 +
332 +[[image:Screenshot 2025-12-17 at 17.25.19.png]]
333 +
334 +Figure 3.3.16. Setting the control attribute without entering password
335 +
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 +
338 +[[image:Screenshot 2025-12-17 at 17.27.04.png]]
339 +
340 +Figure 3.3.17. Configuring an object with control without entering password
341 +
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 +
344 +[[image:Screenshot 2025-12-17 at 17.27.52.png]]
345 +
346 +Figure 3.3.18. Configuring the attribute for password-free control
347 +
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 +
350 +[[image:Screenshot 2025-12-17 at 17.32.18.png]]
351 +
352 +Figure 3.3.19. Configuring object for control without entering password
353 +
354 +=== 3.3.2. Configuring permission for remote control ===
355 +
356 +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 +
358 +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 +
360 +* **telecontrol_permit_on_ti** – permission to switch TC on;
361 +* **telecontrol_permit_off_ti** – permission to switch TC off.
362 +
363 +[[image:Screenshot 2025-12-17 at 17.34.12.png]]
364 +
365 +Figure 3.3.20. Attributes for remote control permission
366 +
367 +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)
368 +
369 +[[image:Screenshot 2025-12-17 at 17.34.50.png]]
370 +
371 +Figure 3.3.21. Configuration of attributes for enabling telecontrol
372 +
373 +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):
374 +
375 +[[image:Screenshot 2025-12-17 at 17.35.21.png]]
376 +
377 +Figure 3.3.22. Attributes for enabling remote control
378 +
379 +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):
380 +
381 +
Screenshot 2025-12-17 at 17.25.19.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +103.8 KB
Content
Screenshot 2025-12-17 at 17.27.04.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +106.1 KB
Content
Screenshot 2025-12-17 at 17.27.52.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +111.9 KB
Content
Screenshot 2025-12-17 at 17.32.18.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +121.9 KB
Content
Screenshot 2025-12-17 at 17.34.12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +116.5 KB
Content
Screenshot 2025-12-17 at 17.34.50.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +74.6 KB
Content
Screenshot 2025-12-17 at 17.35.21.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +107.1 KB
Content