Skip to Content

Wiki source code of 8. Control Setup Manual

Version 13.1 by Lana on 2025/12/17 19:42
Show last authors
1 = CONTENT =
2
3 = 1. INTRODUCTION =
4
5 CENTO is a multifunctional software platform for data acquisition, processing and display. This manual describes how to configure the CENTO user tool Control.
6
7 It is assumed that the user, having read the "User manual", is already familiar with the basic elements of the CENTO interface.
8
9 This manual describes how to configure the Control service, which is used to send control commands to the objects being controlled.
10
11 = 2. CONTROL USING WEB INTERFACE =
12
13 == 2.1. Control using the device, tags editor ==
14
15 A user with the appropriate permissions can control the object using the devices, tags, channels editor.
16
17 By default, for security reasons, in CENTO software, the Administrator role is not authorized for telecontrol and control operations, and the Dispatcher role does not have access to the devices, tags, and channels editor. To enable control and telecontrol using the editor, configure a custom role. For example, duplicate the Dispatcher role and assign it the necessary permissions to access and use the editor.
18
19 To control the device, navigate to the **Tags, channels** tab on the **Devices, tags, channels** page accessible in the menu: Settings > Devices, tags, channels. In the tree structure, locate the device whose parameters are to be controlled. All the tags with preconfigured control functionality will display either a **C** button (see Fig. 2.1) or a **TC** button (see Fig. 2.2) in the **Control** column.
20
21 **C** is an abbreviation for //Control//. **TC** is an abbreviation for //Telecontrol.// In CENTO software, //Control// refers to sending a non-negative integer value to a device, while //Telecontrol //refers to sending a discrete signal.
22
23 [[image:Screenshot 2025-12-17 at 16.28.40.png]]
24
25 Figure 2.1. Tags with telecontrol enabled
26
27 [[image:Screenshot 2025-12-17 at 16.29.26.png]]
28
29 Figure 2.2. Tags with control and telecontrol enabled
30
31 Clicking **C** opens a pop-up window prompting the user to enter a password to access the control function (see Fig. 2.3).
32
33 [[image:Screenshot 2025-12-17 at 16.30.01.png]]
34
35 Figure 2.3. Entering password
36
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
39 [[image:Screenshot 2025-12-17 at 16.31.55.png]]
40
41 Figure 2.4. Entering value for control
42
43 After entering the value in the field, click **Send** (see Fig. 2.4).
44
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
47 [[image:Screenshot 2025-12-17 at 16.32.27.png]]
48
49 Figure 2.5. Confirmation of the command to write a value
50
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
53 [[image:Screenshot 2025-12-17 at 16.33.06.png]]
54
55 Figure 2.6. Selecting command for remote control
56
57 = 3. SETTING CONTROL =
58
59 == 3.1. Setting using WEB interface ==
60
61 Setting control for tags transmitted via Modbus, OPC DA, or IEC-104 protocols is performed through the **Edit parameter** interface located under Settings > Devices, tags, channels, in the **Tags, channels** tab. In this interface, select the target device in the device tree by checking the box next to it. The device should be configured with one of the supported protocols: Modbus TCP, Modbus RTU over TCP, OPC DA, or IEC-104. To open the tag editing interface, click on the tag identifier or tag name in the general tag list.
62
63 The interface includes protocol-dependent fields:
64
65 - general settings described in the “Setup manual”,
66
67 - reading settings as defined in the relevant configuration manuals,
68
69 - settings for writing:
70
71 * Remote control (discrete signal transmission to the device) for IEC-104 protocol: "Remote control is allowed", "Select before operate (SBO)", "Function", "Command duration", "Switch on address", "Switch on value", "Switch off address", "Switch off value", for Modbus TCP protocol: "Remote control is allowed", "Function", "Value length", "Switch on address", "Switch on value", "Switch off value", "Switch off address", "Write by bitmask";
72 * Control (transmission of a positive integer to the device) for Modbus TCP protocol: "Record values", "Function", "Data type in device", "Address", "Byte order", conversion elements: "Physical value (lower limit)", "Physical value (upper limit)", "Value to record (lower limit)", "Value to record (upper limit)", for OPC DA protocol: "Record values", "Device Tag Data Type", conversion elements: "Physical value (lower limit)", "Physical value (upper limit)", "Value to record (lower limit)", "Value to record (upper limit)".
73
74
75 1) The remote //control// function is available for Modbus TCP Modbus RTU over TCP) protocols (see Fig. 3.1.1) and IEC 104 (see Fig. 3.1.2).
76
77 The position of the **Remote control is allowed **switch determines whether record commands can be sent to the device at the specified address.
78
79 The position of the **Select before operate (SBO)** switch defines whether command selection is required prior to executing telecontrol commands.
80
81 In the Remote **control **field, select the appropriate ASDU type for the control command from the drop-down list (see Fig. 3.1.4).
82
83 [[image:Screenshot 2025-12-17 at 16.38.45.png]]
84
85 Figure 3.1.1. Setting telecontrol via Modbus protocol
86
87 [[image:Screenshot 2025-12-17 at 16.39.12.png]]
88
89 Figure 3.1.2. Setting telecontrol via IEC-104 protocol
90
91 The following functions are available for the Modbus protocol:
92
93 FC5 (0x05) - recording the value of one flag (Force Single Coil).
94
95 FC6 (0x06) - recording the value to Preset Single Register.
96
97 FC16 (0x10) - recording multiple registers, used to record a block of contiguous registers (1 to 123 registers) to a remote device (Write Multiple Registers)
98
99 The** Value lenght** field specifies the number of registers to be recorded.
100
101 The **Switch on address** field specifies the address of the register in the device memory where the enable command will be written. The address should be a non-negative integer.
102
103 The **Switch off address** field specifies the register address in the device memory where the disable command will be written. The address should be a non-negative integer.
104
105 The **Switch on value** and **Switch off value** indicate the value to be written to the register address to execute the disable command. The value can be specified in decimal, binary, octal, or hexadecimal (HEX) format. Decimal is written as a plain number, binary is prefixed with 0b or 0B, represents setting the two least significant bits to 1 and 0, octal is prefixed with 08, HEX is prefixed with 0x or 0X.
106
107 The **Write by bitmask **field specifies the mask in decimal, binary, or HEX format.
108
109 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).
110
111 [[image:Screenshot 2025-12-17 at 16.40.14.png]]
112
113 Figure 3.1.3. Setting  control for Modbus protocol
114
115 [[image:Screenshot 2025-12-17 at 16.41.11.png]]