Skip to Content

Changes for page 8. Control Setup Manual

Last modified by Iaroslav Platonov on 2026/06/09 11:18
From version 7.5
edited by Lana
on 2025/12/17 19:37
Change comment: There is no comment for this version
To version 13.3
edited by Lana
on 2025/12/17 19:43
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -54,9 +54,9 @@
54 54  
55 55  Figure 2.6. Selecting command for remote control
56 56  
57 -3. SETTING CONTROL
57 += 3. SETTING CONTROL =
58 58  
59 -3.1. Setting using WEB interface
59 +== 3.1. Setting using WEB interface ==
60 60  
61 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 62  
... ... @@ -71,8 +71,69 @@
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 -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).
75 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 76  The position of the **Remote control is allowed **switch determines whether record commands can be sent to the device at the specified address.
77 77  
78 78  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]]
116 +
117 +Figure 3.1.4. Remote control for IEC-104
118 +
119 +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).
120 +
121 +The position of the **Write values** switch determines whether value write commands can be sent to the device at the specified address.
122 +
123 +The **Function** field selects the Modbus recording function from the drop-down list (see Fig. 3.1.5).
124 +
125 +[[image:Screenshot 2025-12-17 at 16.41.51.png]]
126 +
127 +Figure 3.1.5. Modbus control function
128 +
129 +FC5 (0x05) - recording the value of one flag (Force Single Coil).
130 +
131 +FC16 (0x10) - recording multiple registers, used to write a block of contiguous registers (1 to 123 registers) to a remote device (Write multiple registers).
132 +
133 +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.
134 +
135 +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.
136 +
137 +[[image:Screenshot 2025-12-17 at 16.42.23.png]]
138 +
139 +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).
Screenshot 2025-12-17 at 16.38.45.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +71.4 KB
Content
Screenshot 2025-12-17 at 16.39.12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +81.3 KB
Content
Screenshot 2025-12-17 at 16.40.14.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +59.7 KB
Content
Screenshot 2025-12-17 at 16.41.11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +67.9 KB
Content
Screenshot 2025-12-17 at 16.41.51.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +12.4 KB
Content
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