Skip to Content

Changes for page 8. Control Setup Manual

Last modified by Iaroslav Platonov on 2026/06/09 11:18
From version 12.1
edited by Lana
on 2025/12/17 19:41
Change comment: Uploaded new attachment "Screenshot 2025-12-17 at 16.41.51.png", version {1}
To version 17.2
edited by Lana
on 2025/12/17 19:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -14,19 +14,19 @@
14 14  
15 15  A user with the appropriate permissions can control the object using the devices, tags, channels editor.
16 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.
17 +By default, for security reasons, in CENTO software, the Administrator role is not authorized for remote control and control operations, and the Dispatcher role does not have access to the devices, tags, and channels editor. To enable control and remote control 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 18  
19 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 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.
21 +**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.
22 22  
23 23  [[image:Screenshot 2025-12-17 at 16.28.40.png]]
24 24  
25 -Figure 2.1. Tags with telecontrol enabled
25 +Figure 2.1. Tags with remote control enabled
26 26  
27 27  [[image:Screenshot 2025-12-17 at 16.29.26.png]]
28 28  
29 -Figure 2.2. Tags with control and telecontrol enabled
29 +Figure 2.2. Tags with control and control enabled
30 30  
31 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 32  
... ... @@ -71,7 +71,6 @@
71 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 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 73  
74 -
75 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 76  
77 77  The position of the **Remote control is allowed **switch determines whether record commands can be sent to the device at the specified address.
... ... @@ -96,7 +96,7 @@
96 96  
97 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 98  
99 -The** Value lenght** field specifies the number of registers to be recorded.
98 +The** Value lenght** field specifies the number of registers to be recorded.
100 100  
101 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 102  
... ... @@ -113,3 +113,47 @@
113 113  Figure 3.1.3. Setting  control for Modbus protocol
114 114  
115 115  [[image:Screenshot 2025-12-17 at 16.41.11.png]]
115 +
116 +Figure 3.1.4. Remote control for IEC-104
117 +
118 +Settings for writing: Write values, Function, Device Tag Data Type, Address, Byte order; Tranformation elements: Physical value (lower limit), Physical value (upper limit), Record value (lower limit), Record value (upper limit).
119 +
120 +The position of the **Write values** switch determines whether value write commands can be sent to the device at the specified address.
121 +
122 +The **Function** field selects the Modbus recording function from the drop-down list (see Fig. 3.1.5).
123 +
124 +[[image:Screenshot 2025-12-17 at 16.41.51.png]]
125 +
126 +Figure 3.1.5. Modbus control function
127 +
128 +FC5 (0x05) - recording the value of one flag (Force Single Coil).
129 +
130 +FC16 (0x10) - recording multiple registers, used to write a block of contiguous registers (1 to 123 registers) to a remote device (Write multiple registers).
131 +
132 +The **Address** field specifies the address of the tag in the device memory to which the value will be written. The address should be a non-negative integer in decimal format.
133 +
134 +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.
135 +
136 +[[image:Screenshot 2025-12-17 at 16.42.23.png]]
137 +
138 +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).
139 +
140 +[[image:Screenshot 2025-12-17 at 16.43.58.png]]
141 +
142 +Fig. 3.1.7. Device Tag Data Type
143 +
144 +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).
145 +
146 +[[image:Screenshot 2025-12-17 at 16.44.29.png]]
147 +
148 +Figure 3.1.8. Transformation block
149 +
150 +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).
151 +
152 +[[image:Screenshot 2025-12-17 at 16.45.36.png]]
153 +
154 +Figure 3.1.9. Configuring control for OPCDA protocol
155 +
156 +3.2. Setting control using MS Excel
157 +
158 +
Screenshot 2025-12-17 at 16.42.23.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +32.3 KB
Content
Screenshot 2025-12-17 at 16.43.58.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +32.6 KB
Content
Screenshot 2025-12-17 at 16.44.29.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +27.1 KB
Content
Screenshot 2025-12-17 at 16.45.36.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +47.9 KB
Content