Skip to Content

Changes for page 06 Data Tool

Last modified by Jett on 2025/02/18 16:43
From version 32.1
edited by Jim
on 2023/08/11 09:33
Change comment: There is no comment for this version
To version 21.3
edited by Stone Wu
on 2022/08/05 17:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Jim
1 +XWiki.Stone
Content
... ... @@ -19,20 +19,17 @@
19 19  
20 20  **Upload to Cloud: **The data upload by "bit alarm" is stored in the Cloud and it is alarm data. (Only ig series and 8000/9000 series with -R after system upgrade are supported)
21 21  
22 -(% class="box infomessage" %)
23 -(((
24 24  **✎Note:**
25 25  
26 26  * After enable the Cloud and check the box of Upload to Cloud, the communication port settings of the address in the imported Bit Alarm record configuration must be the same as the communication port settings of the current project, otherwise it cannot be used normally.
27 27  * The number of Alarm records upload to Cloud shall not exceed the limit value, or the sum of the imported alarm records and the number of existing alarm records shall not exceed the limit value. the specific limitation as following table:
28 28  
29 -(% class="table-bordered" style="margin-left:auto; margin-right:auto; width:358px" %)
27 +(% style="margin-left:auto; margin-right:auto; width:358px" %)
30 30  |=(% style="width: 79px;" %)Series|=(% style="width: 276px;" %)Number of Alarm upload to Cloud
31 31  |(% style="width:79px" %)8000-R|(% style="text-align:center; width:276px" %)200
32 32  |(% style="width:79px" %)9000-R|(% style="text-align:center; width:276px" %)200
33 33  |(% style="width:79px" %)3000ig|(% style="text-align:center; width:276px" %)20
34 34  |(% style="width:79px" %)8000ig|(% style="text-align:center; width:276px" %)200
35 -)))
36 36  
37 37  **Alarm Condition:** It sets alarm trigger condition, there are two types: alarm when ON and alarm when OFF.
38 38  
... ... @@ -91,8 +91,6 @@
91 91  
92 92  **Upload to Cloud: **The data upload by "word alarm" is stored in the Cloud and it is alarm data. (Only ig series and 8000/9000 series with -R after system upgrade are supported)
93 93  
94 -(% class="box infomessage" %)
95 -(((
96 96  **✎Note:**
97 97  
98 98  * If the "cloud" function is enabled and "upload to cloud" is checked, the communication port of the address in the configuration of the imported word alarm record must be the same as that of the current project; otherwise, it cannot be used normally.
... ... @@ -104,7 +104,6 @@
104 104  |(% style="width:79px" %)9000-R|(% style="text-align:center; width:276px" %)200
105 105  |(% style="width:79px" %)3000ig|(% style="text-align:center; width:276px" %)20
106 106  |(% style="width:79px" %)8000ig|(% style="text-align:center; width:276px" %)200
107 -)))
108 108  
109 109  **Record alarm:**  Whether to record the alarm history data of word alarm, if checked, it will be saved in the designated storage location.
110 110  
... ... @@ -186,23 +186,26 @@
186 186  
187 187  * **Recipe Folder:** Give Recipe folder name (It can be used, when setting Recipe display object);
188 188  ** **✎Note: **Recipe Folder name can only consist of (0~~9), (a~~z), (A~~Z), ('_'), (' ') and other non-English characters;
189 -* **Group: **Set the recipe group number, the number of elements, the data format. The data format has 8 modes: 16-bit signed decimal, 16-bit unsigned decimal, 16-bit BCD, 32-bit signed decimal, 32-bit unsigned decimal, 16-bit BCD, 32-bit floating point number, 64-bit (double-precision) floating-point number, string, and the choice of data integer and decimal places.
183 +* **Group: **It sets the groups' initial number of recipe;
190 190  * **Elements:** It sets members' initial number of each group;
191 191  * **Data Format:** There are some formats can be supported in Recipe, like 16-bit BCD, 16-bit signed, 16-bit unsigned, 32-bit BCD, 32-bit signed, 32-bit unsigned, 32-bit floating and string. If each member requires different formats, please set it one by one in form;
192 192  * **Decimal: **It sets integer and scale digits;
193 193  
194 -**Mode Selection: **Select Simple or Advanced mode. Recipe file is divided into simple mode and advanced mode. Only in advanced mode can exist multiple recipe files used at the same time. (used wiht file list onject), Simple mode can only support a recipe file; Aadvanced mode can insert group information and reordered.
188 +**Mode Selection**
195 195  
196 -Function address: all operations are done through function addresses, different operating value is as follows:
190 +Users could select Simple or Advanced mode.
197 197  
198 -* = 0: no operation;
199 -* = 1: trigger read data;
200 -* = 2: new trigger or update (If there is group number, it updates.)
201 -* = 4: insert (only valid in advanced mode)
202 -* = 8: delete (Delete according to the writing group number. If write and read address are consistent, refer to the reading group number);
203 -* = 16: delete and sorted ((Delete according to the writing group number. If write and read address are consistent, refer to the reading group number)
204 -* = 64: import CSV recipe file.
192 +**Function Address:**
205 205  
194 +All the operations for recipe is by this address
195 +
196 +* =0 No operation.
197 +* =1 Read data from recipe.
198 +* =2 Insert a new group or write data to exist group.
199 +* =4 Inserted (only advanced mode).
200 +* =8 Delete.
201 +* =16 Delete and Sequence.
202 +
206 206  **Use Multiple File**
207 207  
208 208  Check it to use more than one recipe file in HMI, but this option only valid in [Advanced mode];
... ... @@ -247,124 +247,47 @@
247 247  **✎Note: **This function only supported in HMI+, i series, ie series, ig series.
248 248  )))
249 249  
247 +== Simple recipe ==
250 250  
251 -**description of Adcanced mode**
249 +The recipe function should be used together with the recipe configuration area, file list and record display object.
252 252  
253 -According to the recipe configuration information in Figure 2 above. The function address is HDW70, and each function configuration corresponds to the group number address, recipe element address and recipe file name address. The recipe information configured in figure 2 can be displayed in the table in figure 3 with the "Record Display" object.
251 +* Click the button [[image:image-20220805170000-1.jpeg]] in "Project"→"Bit Alarm" as below shows.
254 254  
255 -[[image:image-20220806111333-1.jpeg]]
253 +[[image:image-20220805170046-2.jpeg]]
256 256  
257 -**Read recipe**: Input 1 to the file name, when the group number addresses HDW100=1 and HDW70=1 (read), the element data of the first group (ID=1) is written to the recipe address from the recipe file. As shown in Figure 3 above: HDW105=1, HHDW106=2, HDW107=3, HDW108=4, HDW109=5.
255 +* Click "Add" button to open "Recipe" setting window. The recipe mode is divided into simple mode and advanced mode, and you could choose the most suitable mode for configuration according to your needs. The simple mode is as below.
258 258  
259 -**Write recipe**: Input 1 to the file name, when the group number addresses HDW101=4 and HDW70=2 (write), the data will be read from the recipe address and written to the corresponding group of the recipe file. As shown in figure 3 above: HDW110=20, HHDW111=21, HDW112=22, HDW113=23, HDW114=24. Write the data of this set to the elements of ID=4 in the recipe table (if there is no data of Group 4 in the recipe file, a new set of data will be added; If there is data of Group 4 in the original recipe, the original data will be overwritten and the latest data will be displayed in the recipe file).
257 +[[image:image-20220805170102-3.jpeg]]
260 260  
261 -**Index recipe**: When the file name is input 1, when the group number address HDW102=3, the data of ID=3 (Group 3) in the recipe file will be directly displayed in the component address of the index, that is, HDW115=11, HHDW116=12, HDW117=13, HDW118=14 and HDW119=15. If the data of the index component address is modified, the modified data will be automatically filled into the table of the recipe file, that is, the data of the recipe file will be automatically updated after the data is modified.
259 +**Recipe folder: **set the name of the current recipe file.
262 262  
263 -[[image:image-20220806111355-2.jpeg]]
261 +**Group (0~~1000):** Set the recipe group number, the number of elements, the data format. The data format has 8 modes: 16-bit signed decimal, 16-bit unsigned decimal, 16-bit BCD, 32-bit signed decimal, 32-bit unsigned decimal, 16-bit BCD, 32-bit floating point number, 64-bit (double-precision) floating-point number, string, and the choice of data integer and decimal places.
264 264  
265 -**Insert recipe**: Input 1 to the file name, when the group number addresses HDW103=3 and HDW70=4 (insert), the data of the 3rd group will be inserted, but the data of the third group already exists in the original recipe file (see Figure 3 above), then the original data will be moved down by one group, that is, the original 3rd group will become the 4th group, and so on, and HDW120=16, HHDW121=17, HDW122=18, HDW123=19 and HDW124=20 will be written into the new 3rd group of the recipe file at the same time. The results are shown in Figure 4 above.
266 -
267 -When the group number address HDW101=2 (**The delete function only works on the group number of the write function**), HDW70=8 (delete), the data in the recipe file with ID=2 (Group 2) will be deleted.
268 -
269 -When the group number address HDW101=5 (**The delete function only works on the group number of the write function**), HDW70=16 (delete and sort), the data of ID=5 (Group 5) in the recipe file will be deleted, and the original ID=6 (Group 6) data will be reordered to become the new Group 5 data, the original ID=7 (Group 7) data will be reordered to become the new Group 6 data, and so on.
270 -
271 -**Recipe Demo Download Link: **[[Download>>url:https://drive.google.com/open?id=1Cjbq_tW-NIirHFBpxt47g7IKvoYaWqUR]]
272 -
273 -== Calling CSV recipe file ==
274 -
275 -**Overview**
276 -
277 -The recipe files used by the regular series HMI are in CSV format, and the recipe files used by the current series HMI are in database format. In order to be compatible with CSV format recipe files on the current series of HMI, please follow the instruction when using it.
278 -
279 -**Operations**
280 -
281 -Create the recipe as it is configured. The default recipe file name is “1. rcp2”, which is placed in folder 123, as shown in the following figure.
282 -
283 -(% style="text-align:center" %)
263 +(% class="box infomessage" %)
284 284  (((
285 -(% style="display:inline-block" %)
286 -[[Figure 1>>image:image-20220806100702-2.jpeg]]
265 +✎**Note: **data format is set for the recipe elements, and all the elements in a recipe data format is the same.
287 287  )))
288 288  
289 -2. Place a "Recipe Record Display" object and a "File List" object on the project screen for viewing the recipe files in the folder 123, and the address configuration in the object should be consistent with the above configuration.
268 +**Mode: **Recipe file is divided into simple mode and advanced mode. Only in advanced mode can exist multiple recipe files used at the same time. (used wiht file list onject), Simple mode can only support a recipe file; Aadvanced mode can insert group information and reordered.
290 290  
291 -(% style="text-align:center" %)
292 -[[image:image-20220806100753-3.jpeg]]
270 +Function address: all operations are done through function addresses, different operating value is as follows:
293 293  
294 -By configuring the address in the table and combining the recipe function, the CSV recipe files of regular series are imported.
272 +* = 0: no operation;
273 +* = 1: trigger read data;
274 +* = 2: new trigger or update (If there is group number, it updates.)
275 +* = 4: insert (only valid in advanced mode)
276 +* = 8: delete (Delete according to the writing group number. If write and read address are consistent, refer to the reading group number);
277 +* = 16: delete and sorted ((Delete according to the writing group number. If write and read address are consistent, refer to the reading group number)
278 +* = 64: import CSV recipe file.
295 295  
296 -|=Address range|=Object type|=Address function
297 -|HSW1050 to 1065|Text input object|Enter the CSV recipe file name to import
298 -|HSW1066|Numerical input object|Import CSV file type:(((
299 -* = 0: Custom CSV file (all data in the file is valid)
300 -* = 1: Normal recipe file for regular series HMI (the data in line 1 of the file is invalid)
301 -* = 2: Special recipe file for regular series HMI (the data in line 1 and 2 and column 1 of the file are invalid)
302 -)))
303 -|HSW1067|Numerical input object|(((
304 -Where the CSV file is saved:
280 +Recipe folder names can only consist of (0~~9), (a~~z), (A~~Z), ('_') (''), and other non-English characters.
305 305  
306 -* = 0: In the CsvFile directory of U disk
307 -* = 1: In the CsvFile directory of the SD card
282 +Adcanced
308 308  
309 -**The path for offline simulation is: C:\ HMIEmulation\ CustomFileDir\ CsvFile**
310 -)))
311 -|HSW242|Numerical input object|Returns the results of the csv import:(((
312 -* = 37: CSV file imported successfully
313 -* = 38: CSV file import failed
314 -)))
284 +**Recipe Demo Download Link: **[[Download>>url:https://drive.google.com/open?id=1Cjbq_tW-NIirHFBpxt47g7IKvoYaWqUR]]
315 315  
316 -**Select CSV recipe file (take U disk as an example):**
286 +
317 317  
318 -Using the file list object, select the recipe file in the U disk by path, and configure the recipe file name address directly to the special address HSW1050 in the above table, which can directly detect the CSV file in the U disk; Select the recipe file in the file list, and write the selected recipe file name into the recipe file name: In HSW1050 to 1065.
319 -
320 -Use the special address of the above table to configure the path of the CSV file: HSW106, configure recipe file name: HSW1050 to1065
321 -
322 -Use HSW1066 address to select the corresponding CSV recipe file type.
323 -
324 -* HSW1066 = 0: Import a user-defined CSV recipe file (all data in the custom CSV file must be valid);
325 -
326 -(% style="text-align:center" %)
327 -[[image:image-20220806101129-5.jpeg]]
328 -
329 -* HSW1066=1: Import the normal recipe file of regular series HMI (the data in line 1 of the file is invalid);
330 -
331 -The data in line 1 of the normal recipe file is used to define the format of the recipe and will not be imported into the recipe table as recipe information, **but you must ensure that the data in line 1 representing the elements and number of groups is correct, otherwise the CSV recipe file will fail to be imported.**
332 -
333 -(% style="text-align:center" %)
334 -[[image:image-20220806101520-6.jpeg]]
335 -
336 -* HSW1066=2: Import the special recipe file of regular series HMI (the data in line 1, 2 and column 1 of the file are invalid);
337 -
338 -In the special recipe file, line 1 is used to define the format of the recipe, line 2 is used to define the element name of the recipe, and column 1 is used to define the group name of the recipe, so lines 1, 2 and column 1 of the special recipe will not be imported into the recipe table as recipe information. **During use, ensure that the data such as the number of groups and elements representing the recipe format in the first line are correct, otherwise the import of the CSV recipe file will fail.**
339 -
340 -(% style="text-align:center" %)
341 -[[image:image-20220806102610-7.jpeg]]
342 -
343 -**Perform import**
344 -
345 -After configuring the saving path of CSV recipe file, the name of recipe file and the type of recipe according to the above steps, the method of transferring CSV file to DB file is as follows:
346 -
347 -* Configure the DB recipe file name by text input object: HDW500 = 3 (recipe file configured in Figure 1),
348 -* Set the recipe function address to: HDW1000 = 64 (the function address configured in Figure 1),
349 -* Transform the CSV recipe file in U disk into DB recipe file with file name “3.rcp2”.
350 -
351 -**DB recipe file for storing CSV data:**
352 -
353 -Simple mode: When the recipe file is set to simple mode, the file of CSV data is saved as the DB recipe file of 1. rcp2 by default.
354 -
355 -Advanced mode: When the recipe is enabled in advanced mode (multi-file recipe), the imported CSV file data is saved to the file recorded at the recipe file address HDW500 (the address configured in Figure 1).
356 -
357 -**Import results:**
358 -
359 -* HSW242 = 37: Import succeeded;
360 -* HSW242 = 38: Import failed.
361 -
362 -**Precautions:**
363 -
364 -* Ensure that the data format of each element in the CSV file is the same as the recipe data format set in the software (DB), and ensure that the elements of each row in the valid data area is the same as the elements set in the software (DB);
365 -* When the elements of a line in CSV file is more than the elements set in the software (DB), it will prompt the import failure;
366 -* When the CSV file imported into the regular series HMI is a recipe file, the data representing the recipe format (elements, number of groups, whether it is a special recipe) in line 1 must be correct, otherwise the import of CSV file will fail.
367 -
368 368  = (% style="color:inherit; font-family:inherit; font-size:29px" %)**Traditional recipe**(%%) =
369 369  
370 370  Traditional recipe is composed of multiple groups of information with the same structure and different data. Due to the similarity of these information, you could edit them into a set of recipes to facilitate the transfer of data between HMI and PLC.
... ... @@ -695,10 +695,7 @@
695 695  
696 696  (% class="box infomessage" %)
697 697  (((
698 -✎**Note: **
699 -
700 -* The user name and password must be unique.
701 -* The multi language function of User permission only supported on HMI system version V2.0 or above
618 +✎**Note: **The user name and password must be unique.
702 702  )))
703 703  
704 704  == Settings ==
... ... @@ -708,11 +708,6 @@
708 708  (% style="text-align:center" %)
709 709  [[image:用户权限 1.png||class="img-thumbnail"]]
710 710  
711 -Click on the cell from UserName and Desc, which can support the multi language.
712 -
713 -(% style="text-align:center" %)
714 -[[image:UserPermissionMultilan.png]]
715 -
716 716  1. Click "User Permission" in "Data Tool" toolbar.
717 717  1. Edit user name, click "User0" cell under "UserName", and then enter the user name, one project allows maximum 20 users.
718 718  1. Edit password, click "User0" cell under "PassWord", and then enter the user name.
... ... @@ -726,9 +726,6 @@
726 726  * Only a maximum of one administrator permission is allowed in a profile with one user permission. If you want to use "Funtion address" to modify the user permission, you must log in the administrator account to operate.
727 727  * When the configured file does not have the administrator account, a new user can be added  through "Funtion address" and set as the administrator.
728 728  * If you select hidden fucntion when configuring user account, the account would display as "~*~*~*~*~*~*" in the list. You only need to enter the password of the corresponding hidden user to log in.
729 -* (((
730 -Adding new UserName and Desc on the HMI by special addresses in the current language of the HMI, other languages will also configure the user names and user descriptions to the current language by default, i.e. switching to other languages, the new user names and user descriptions will not change with the language.
731 -)))
732 732  
733 733  == Object permission configuration ==
734 734  
... ... @@ -735,11 +735,6 @@
735 735  (% style="text-align:center" %)
736 736  [[image:用户权限 2.png||class="img-thumbnail"]]
737 737  
738 -User operation logs support multi languages configuration. Click on the Log Message, the text editor of multi language will be pop up:
739 -
740 -(% style="text-align:center" %)
741 -[[image:LogMessagesMultilan.png]]
742 -
743 743  **Operation Procedure of Object Permission**
744 744  
745 745  1. Open the object setting windows;
LogMessagesMultilan.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Hunter
Size
... ... @@ -1,1 +1,0 @@
1 -37.5 KB
Content
UserPermissionMultilan.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Hunter
Size
... ... @@ -1,1 +1,0 @@
1 -23.2 KB
Content
image-20220805174501-1.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Stone
Size
... ... @@ -1,1 +1,0 @@
1 -79.3 KB
Content
image-20220805174543-2.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Stone
Size
... ... @@ -1,1 +1,0 @@
1 -80.0 KB
Content
image-20220806100635-1.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Stone
Size
... ... @@ -1,1 +1,0 @@
1 -85.6 KB
Content
image-20220806100702-2.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Stone
Size
... ... @@ -1,1 +1,0 @@
1 -131.3 KB
Content
image-20220806100753-3.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Stone
Size
... ... @@ -1,1 +1,0 @@
1 -10.5 KB
Content
image-20220806101048-4.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Stone
Size
... ... @@ -1,1 +1,0 @@
1 -226.9 KB
Content
image-20220806101129-5.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Stone
Size
... ... @@ -1,1 +1,0 @@
1 -168.6 KB
Content
image-20220806101520-6.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Stone
Size
... ... @@ -1,1 +1,0 @@
1 -24.8 KB
Content
image-20220806102610-7.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Stone
Size
... ... @@ -1,1 +1,0 @@
1 -43.9 KB
Content
image-20220806111333-1.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Stone
Size
... ... @@ -1,1 +1,0 @@
1 -131.4 KB
Content
image-20220806111355-2.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Stone
Size
... ... @@ -1,1 +1,0 @@
1 -135.4 KB
Content