Skip to Content

Changes for page 8. Control Setup Manual

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

Summary

Details

Page properties
Content
... ... @@ -1,7 +1,5 @@
1 1  = CONTENT =
2 2  
3 -{{toc/}}
4 -
5 5  = 1. INTRODUCTION =
6 6  
7 7  CENTO is a multifunctional software platform for data acquisition, processing and display. This manual describes how to configure the CENTO user tool Control.
... ... @@ -22,13 +22,13 @@
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||height="441" width="1445"]]
23 +[[image:Screenshot 2025-12-17 at 16.28.40.png]]
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||height="584" width="1424"]]
27 +[[image:Screenshot 2025-12-17 at 16.29.26.png]]
30 30  
31 -Figure 2.2. Tags with control and remote control enabled
29 +Figure 2.2. Tags with control and control enabled
32 32  
33 33  Clicking **C** opens a pop-up window prompting the user to enter a password to access the control function (see Fig. 2.3).
34 34  
... ... @@ -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||height="315" width="1392"]]
39 +[[image:Screenshot 2025-12-17 at 16.31.55.png]]
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||height="313" width="1382"]]
47 +[[image:Screenshot 2025-12-17 at 16.32.27.png]]
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||height="263" width="1368"]]
53 +[[image:Screenshot 2025-12-17 at 16.33.06.png]]
56 56  
57 57  Figure 2.6. Selecting command for remote control
58 58  
... ... @@ -77,17 +77,17 @@
77 77  
78 78  The position of the **Remote control is allowed **switch determines whether record commands can be sent to the device at the specified address.
79 79  
80 -The position of the **Select before operate (SBO)** switch defines whether command selection is required prior to executing remote control commands.
78 +The position of the **Select before operate (SBO)** switch defines whether command selection is required prior to executing telecontrol commands.
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||height="386" width="633"]]
82 +[[image:Screenshot 2025-12-17 at 16.38.45.png]]
85 85  
86 -Figure 3.1.1. Setting remote control via Modbus protocol
84 +Figure 3.1.1. Setting telecontrol via Modbus protocol
87 87  
88 -[[image:Screenshot 2025-12-17 at 16.39.12.png||height="384" width="628"]]
86 +[[image:Screenshot 2025-12-17 at 16.39.12.png]]
89 89  
90 -Figure 3.1.2. Setting remote control via IEC-104 protocol
88 +Figure 3.1.2. Setting telecontrol via IEC-104 protocol
91 91  
92 92  The following functions are available for the Modbus protocol:
93 93  
... ... @@ -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||height="461" width="622"]]
110 +[[image:Screenshot 2025-12-17 at 16.40.14.png]]
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||height="286" width="309"]]
114 +[[image:Screenshot 2025-12-17 at 16.41.11.png]]
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||height="168" width="313"]]
124 +[[image:Screenshot 2025-12-17 at 16.41.51.png]]
127 127  
128 128  Figure 3.1.5. Modbus control function
129 129  
... ... @@ -135,267 +135,26 @@
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||height="198" width="319"]]
136 +[[image:Screenshot 2025-12-17 at 16.42.23.png]]
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||height="316" width="317"]]
140 +[[image:Screenshot 2025-12-17 at 16.43.58.png]]
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||height="149" width="530"]]
146 +[[image:Screenshot 2025-12-17 at 16.44.29.png]]
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||height="371" width="598"]]
152 +[[image:Screenshot 2025-12-17 at 16.45.36.png]]
155 155  
156 156  Figure 3.1.9. Configuring control for OPCDA protocol
157 157  
158 -== 3.2. Setting control using MS Excel ==
156 +3.2. Setting control using MS Excel
159 159  
160 -To configure **Control **for a tag polled via the required protocol using Excel, download a configuration template. To do this, navigate to Settings > Configuration files in the CENTO interface. The **Import/Export configuration file** page opens (see Fig. 3.2.1). In the **Tags and Channels** section, click** Download** to download the template file.
161 -
162 -[[image:Screenshot 2025-12-17 at 16.50.31.png]]
163 -
164 -Figure 3.2.1. Import/Export configuration files
165 -
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 -
168 -[[image:Screenshot 2025-12-17 at 16.51.23.png||height="261" width="950"]]
169 -
170 -[[image:Screenshot 2025-12-17 at 16.51.40.png||height="319" width="954"]]
171 -
172 -Figure. 3.2.2. Table of tags
173 -
174 -The table includes columns specifically designated for control and remote control settings:
175 -
176 -* **Resolution of TU** field specifies whether the ability to send remote control (recording) commands is enabled.
177 -* **Register address enable** 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.
178 -* **Value for enable **specifies the value to be written to the register address to execute the enable command.
179 -* **Register address disable** specifies the address of the register in the device memory where the disable command will be written. The address should be a non-negative integer.
180 -* **Value for disable **specifies the value to be written to the register address to execute the disable command.
181 -* **Control resolution** field specifies whether the ability to send write commands is enabled.
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 -
184 -[[image:Screenshot 2025-12-17 at 16.52.25.png||height="332" width="641"]]
185 -
186 -Figure 3.2.3. ID Directory write function
187 -
188 -* **Device data type **is filled in according to the device manual. The mapping between data types and their corresponding identifiers is listed on the //ID Directory //sheet (see Fig. 3.2.4).
189 -
190 -[[image:Screenshot 2025-12-17 at 16.52.54.png]]
191 -
192 -Figure 3.2.4. Directory ID data type
193 -
194 -* **Write address **specifies the memory address of the tag in the device where the value will be written.
195 -* **Byte order **is filled in according to the device manual. The mapping between byte order and their corresponding identifiers is provided on the "ID Directory" sheet (see Fig. 3.2.5).
196 -
197 -[[image:Screenshot 2025-12-17 at 16.53.28.png]]
198 -
199 -Figure 3.2.5. Directory ID byte order
200 -
201 -* Transformation for Modbus: Physical value (lower limit)
202 -* Transformation for Modbus: Physical value (upper limit)
203 -* Transformation for Modbus: Value for writing (lower limit)
204 -* Transformation for Modbus: Value for writing (lower limit)
205 -
206 -After creating the configuration, upload the template to the CENTO database. To do this, click **Upload** in the **Tags and Channels** block of the **Configuration files** interface Then, click **Select a file. **A window opens to select the storage location of the tag configuration file that was previously uploaded and edited.
207 -
208 -Afterward, check the file for any errors that may have occurred during configuration by clicking **Check.**
209 -
210 -If the check is successful, write the configuration to the database clicking **Save**. If errors are detected during the check, eliminate them and repeat the process until all errors are resolved.
211 -
212 -== 3.3. Setting up control in the information model ==
213 -
214 -The Information Model (IM) is an add-on to the structure recorded in CENTO.
215 -
216 -The IM classes define the types and subtypes of all devices on the site, ensuring the system knows which parameters to expect from these devices.
217 -
218 -To add //Control// to the IM, download the Excel file from the **Configuration files** menu item under **Information Model Classes** (see Fig. 3.2.1), or configure it using the web editor by going to Information Model Editor > Classes (see Fig. 3.3.2).
219 -
220 -In the downloaded file, first create a new class //Write value// in the //List of Classes// sheet. Then, create a separate sheet where the **code** name matches the tab name (see Fig. 3.3.1).
221 -
222 -[[image:Screenshot 2025-12-17 at 16.54.43.png]]
223 -
224 -Figure 3.3.1. Value for writing class with attributes in Excel file
225 -
226 -
227 -This class has four attributes to be specified exactly as shown in Figure 3.3.1:
228 -
229 -* **Tag ID **is a mandatory field;
230 -* Optional fields include the lower and upper limits of values, which define the range within which any values can be entered. The **Value variants** field is provided for convenience, allowing to select from predefined options instead of manually entering values. To use this feature, specify a reference to the directory in the **Type** column, such as// ref_value_variants //(see Fig. 3.3.6). This reference can then be used to select the desired numeric parameters (see Fig. 3.3.7).
231 -
232 -Check the created //Write value// class on the classes editor page:
233 -
234 -[[image:Screenshot 2025-12-17 at 16.55.17.png||height="597" width="1223"]]
235 -
236 -Figure 3.3.2. Class Write value with attributes in the web-interface of the IM editor
237 -
238 -Next, create a class, for example, Motor, to be used to control the IM object. For this class, add attributes with the reference to the class //Write value //in the **Type** column (write the class **code**):
239 -
240 -[[image:Screenshot 2025-12-17 at 16.55.51.png]]
241 -
242 -Fig. 3.3.3 - Class Motor with attributes in Excel file
243 -
244 -Check the created //Motor// class on the classes editor page:
245 -
246 -[[image:Screenshot 2025-12-17 at 16.56.24.png||height="337" width="1437"]]
247 -
248 -Figure 3.3.4. Class Motor with attributes in the web-interface of the IM editor
249 -
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 -
252 -[[image:Screenshot 2025-12-17 at 16.56.55.png||height="480" width="1400"]]
253 -
254 -Figure 3.3.5. Configuring the Control in the Information Model (object editor)
255 -
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 -
258 -[[image:Screenshot 2025-12-17 at 16.57.33.png||height="133" width="444"]]
259 -
260 -Figure 3.3.6. Configuring IM directory
261 -
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 -
264 -[[image:Screenshot 2025-12-17 at 16.58.03.png||height="162" width="959"]]
265 -
266 -Figure 3.3.7. Table of IM directories
267 -
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 -
270 -[[image:Screenshot 2025-12-17 at 16.58.31.png||height="434" width="1427"]]
271 -
272 -Figure 3.3.8. IM directory
273 -
274 -IM settings allow sending both single and multiple remote control commands. Remote control is configured in the same way as control, but uses its own set of system commands.
275 -
276 -* **Single remote control command of an IM object**
277 -
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 -
280 -[[image:Screenshot 2025-12-17 at 16.59.06.png||height="156" width="749"]]
281 -
282 -Figure 3.3.9. Adding remote control attributes to the Switch class
283 -
284 -Values for these attributes should be specified for class elements (see Fig. 3.3.10):
285 -
286 -* telecontrol_on_ti – Tag ID for switching the object on;
287 -* telecontrol_off_ti – Tag ID for switching the object off;
288 -* telecontrolled – flag indicating whether the object can be controlled (TRUTH – remote control is available, FALSE – not available).
289 -
290 -[[image:Screenshot 2025-12-17 at 16.59.40.png||height="240" width="1524"]]
291 -
292 -Figure 3.3.10. Configuring Switch remote control via Excel
293 -
294 -Remote control can also be configured in the Information Model Editor (see Fig. 3.3.11).
295 -
296 -[[image:Screenshot 2025-12-17 at 17.02.42.png||height="543" width="1245"]]
297 -
298 -Figure 3.3.11. Configuring switch remote control via the web editor
299 -
300 -* **Multiple remote control commands for a single IM object**
301 -
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 -
304 -[[image:Screenshot 2025-12-17 at 17.04.22.png||height="440" width="790"]]
305 -
306 -Figure 3.3.12. Telecontrol (remote control) class with attributes
307 -
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 -
310 -[[image:Screenshot 2025-12-17 at 17.05.09.png||height="246" width="789"]]
311 -
312 -Figure 3.3.13. Class attributes with the type Telecontrol
313 -
314 -Fig. 3.3.14 shows an example of a configured IM object with multiple remote control commands:
315 -
316 -[[image:Screenshot 2025-12-17 at 17.06.00.png||height="865" width="1203"]]
317 -
318 -Figure 3.3.14. IM object with multiple telecontrol commands
319 -
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 -
322 -[[image:Screenshot 2025-12-17 at 17.06.35.png||height="338" width="475"]]
323 -
324 -Figure 3.3.15. IM object on the diagram with multiple remote control commands
325 -
326 -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.
327 -
328 -3.3.1. Setting up control and remote control without password
329 -
330 -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.//
331 -
332 -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).
333 -
334 -[[image:Screenshot 2025-12-17 at 17.25.19.png]]
335 -
336 -Figure 3.3.16. Setting the control attribute without entering password
337 -
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 -
340 -[[image:Screenshot 2025-12-17 at 17.27.04.png||height="487" width="1045"]]
341 -
342 -Figure 3.3.17. Configuring an object with control without entering password
343 -
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 -
346 -[[image:Screenshot 2025-12-17 at 17.27.52.png||height="627" width="1051"]]
347 -
348 -Figure 3.3.18. Configuring the attribute for password-free control
349 -
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 -
352 -[[image:Screenshot 2025-12-17 at 17.32.18.png||height="567" width="1048"]]
353 -
354 -Figure 3.3.19. Configuring object for control without entering password
355 -
356 -=== 3.3.2. Configuring permission for remote control ===
357 -
358 -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.
359 -
360 -To implement this type of remote control (TC) in CENTO, the following attributes are added to the object class (see Fig. 3.3.20):
361 -
362 -* **telecontrol_permit_on_ti** – permission to switch TC on;
363 -* **telecontrol_permit_off_ti** – permission to switch TC off.
364 -
365 -[[image:Screenshot 2025-12-17 at 17.34.12.png||height="568" width="1045"]]
366 -
367 -Figure 3.3.20. Attributes for remote control permission
368 -
369 -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)
370 -
371 -[[image:Screenshot 2025-12-17 at 17.34.50.png]]
372 -
373 -Figure 3.3.21. Configuration of attributes for enabling telecontrol
374 -
375 -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):
376 -
377 -[[image:Screenshot 2025-12-17 at 17.35.21.png]]
378 -
379 -Figure 3.3.22. Attributes for enabling remote control
380 -
381 -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):
382 -
383 -[[image:Screenshot 2025-12-17 at 17.37.11.png]]
384 -
385 -Figure 3.3.23. Tag configuration for telecontrol permission
386 -
387 -Thus, after adding the attributes //telecontrol_permit_on_ti// and //telecontrol_permit_off_ti//, configuring the tags, and assigning them to the IM object, CENTO software first sends the remote control permission command before transmitting the actual remote control command.
388 -
389 -= 4. RECOMMENDED SETTINGS AND SPECIAL CASES =
390 -
391 -[[image:Screenshot 2025-12-17 at 17.38.23.png]]
392 -
393 -[[image:Screenshot 2025-12-17 at 17.38.44.png]]
394 -
395 -[[image:Screenshot 2025-12-17 at 17.38.57.png]]
396 -
397 - [[image:Screenshot 2025-12-17 at 17.42.19.png]]
398 -
399 -[[image:Screenshot 2025-12-17 at 17.41.38.png]]
400 -
401 -[[image:Screenshot 2025-12-17 at 17.42.37.png]]
158 +
Screenshot 2025-12-17 at 17.02.42.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -182.7 KB
Content
Screenshot 2025-12-17 at 17.04.22.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -115.2 KB
Content
Screenshot 2025-12-17 at 17.05.09.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -90.5 KB
Content
Screenshot 2025-12-17 at 17.06.00.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -191.9 KB
Content
Screenshot 2025-12-17 at 17.06.35.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -54.4 KB
Content
Screenshot 2025-12-17 at 17.25.19.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -103.8 KB
Content
Screenshot 2025-12-17 at 17.27.04.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -106.1 KB
Content
Screenshot 2025-12-17 at 17.27.52.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -111.9 KB
Content
Screenshot 2025-12-17 at 17.32.18.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -121.9 KB
Content
Screenshot 2025-12-17 at 17.34.12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -116.5 KB
Content
Screenshot 2025-12-17 at 17.34.50.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -74.6 KB
Content
Screenshot 2025-12-17 at 17.35.21.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -107.1 KB
Content
Screenshot 2025-12-17 at 17.37.11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -105.5 KB
Content
Screenshot 2025-12-17 at 17.38.23.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -67.7 KB
Content
Screenshot 2025-12-17 at 17.38.44.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -68.8 KB
Content
Screenshot 2025-12-17 at 17.38.57.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -66.7 KB
Content
Screenshot 2025-12-17 at 17.39.30.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -68.8 KB
Content
Screenshot 2025-12-17 at 17.40.05.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -12.2 KB
Content
Screenshot 2025-12-17 at 17.40.35.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -57.7 KB
Content
Screenshot 2025-12-17 at 17.41.38.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -47.4 KB
Content
Screenshot 2025-12-17 at 17.42.19.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -56.7 KB
Content
Screenshot 2025-12-17 at 17.42.37.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -57.9 KB
Content