Skip to Content

Changes for page 06 Data Tool

Last modified by Jett on 2025/02/18 16:43
From version 31.1
edited by Jim
on 2023/08/11 09:32
Change comment: There is no comment for this version
To version 24.1
edited by Stone Wu
on 2022/08/06 10:04
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  
... ... @@ -244,124 +244,141 @@
244 244  **✎Note: **This function only supported in HMI+, i series, ie series, ig series.
245 245  )))
246 246  
244 +[[image:image-20220805174501-1.jpeg]]
247 247  
248 -**description of Adcanced mode**
246 +[[image:image-20220805174543-2.jpeg]]
249 249  
250 -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.
248 +**Recipe Demo Download Link: **[[Download>>url:https://drive.google.com/open?id=1Cjbq_tW-NIirHFBpxt47g7IKvoYaWqUR]]
251 251  
252 -[[image:image-20220806111333-1.jpeg]]
253 253  
254 -**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.
251 +== Calling CSV recipe file ==
255 255  
256 -**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 257  
258 -**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.
254 +~1. Overview:
259 259  
260 -[[image:image-20220806111355-2.jpeg]]
261 261  
262 -**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.
257 +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.
263 263  
264 -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.
265 265  
266 -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.
260 +2 Operations
267 267  
268 -**Recipe Demo Download Link: **[[Download>>url:https://drive.google.com/open?id=1Cjbq_tW-NIirHFBpxt47g7IKvoYaWqUR]]
269 269  
270 -== Calling CSV recipe file ==
263 +~1. 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.
271 271  
272 -**Overview**
273 273  
274 -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.
275 275  
276 -**Operations**
267 +Figure 1
277 277  
278 -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.
279 279  
280 -(% style="text-align:center" %)
281 -(((
282 -(% style="display:inline-block" %)
283 -[[Figure 1>>image:image-20220806100702-2.jpeg]]
284 -)))
285 -
286 286  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.
287 287  
288 -(% style="text-align:center" %)
289 -[[image:image-20220806100753-3.jpeg]]
290 290  
291 -By configuring the address in the table and combining the recipe function, the CSV recipe files of regular series are imported.
292 292  
293 -|=Address range|=Object type|=Address function
274 +
275 +3. By configuring the address in the table and combining the recipe function, the CSV recipe files of regular series are imported.
276 +
277 +
278 +|Address range|Object type|Address function
294 294  |HSW1050 to 1065|Text input object|Enter the CSV recipe file name to import
295 -|HSW1066|Numerical input object|Import CSV file type:(((
296 -* = 0: Custom CSV file (all data in the file is valid)
297 -* = 1: Normal recipe file for regular series HMI (the data in line 1 of the file is invalid)
298 -* = 2: Special recipe file for regular series HMI (the data in line 1 and 2 and column 1 of the file are invalid)
299 -)))
280 +|HSW1066|Numerical input object|Import CSV file type:
281 +~= 0: Custom CSV file (all data in the file is valid)
282 +~= 1: Normal recipe file for regular series HMI (the data in line 1 of the file is invalid)
283 +~= 2: Special recipe file for regular series HMI (the data in line 1 and 2 and column 1 of the file are invalid)
300 300  |HSW1067|Numerical input object|(((
301 301  Where the CSV file is saved:
286 +~= 0: In the CsvFile directory of U disk
287 +~= 1: In the CsvFile directory of the SD card
302 302  
303 -* = 0: In the CsvFile directory of U disk
304 -* = 1: In the CsvFile directory of the SD card
305 -
306 -**The path for offline simulation is: C:\ HMIEmulation\ CustomFileDir\ CsvFile**
289 +The path for offline simulation is: C:\ HMIEmulation\ CustomFileDir\ CsvFile
307 307  )))
308 -|HSW242|Numerical input object|Returns the results of the csv import:(((
309 -* = 37: CSV file imported successfully
310 -* = 38: CSV file import failed
311 -)))
291 +|HSW242|Numerical input object|Returns the results of the csv import:
292 +~= 37: CSV file imported successfully
293 +~= 38: CSV file import failed
312 312  
313 -**Select CSV recipe file (take U disk as an example):**
295 +4. Select CSV recipe file (take U disk as an example):
314 314  
315 -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.
316 316  
317 -Use the special address of the above table to configure the path of the CSV file: HSW106, configure recipe file name: HSW1050 to1065
298 +(1) 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, the configuration is shown in the following figure.
318 318  
319 -Use HSW1066 address to select the corresponding CSV recipe file type.
320 320  
321 -* HSW1066 = 0: Import a user-defined CSV recipe file (all data in the custom CSV file must be valid);
301 + Use the special address of the above table to configure the path of the CSV file: HSW106, configure recipe file name: HSW1050 to1065
322 322  
323 -(% style="text-align:center" %)
324 -[[image:image-20220806101129-5.jpeg]]
325 325  
326 -* HSW1066=1: Import the normal recipe file of regular series HMI (the data in line 1 of the file is invalid);
304 +(2) Use HSW1066 address to select the corresponding CSV recipe file type.
327 327  
328 -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.**
329 329  
330 -(% style="text-align:center" %)
331 -[[image:image-20220806101520-6.jpeg]]
307 + A) HSW1066 = 0: Import a user-defined CSV recipe file (all data in the custom CSV file must be valid);
332 332  
333 -* 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);
334 334  
335 -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.**
336 336  
337 -(% style="text-align:center" %)
338 -[[image:image-20220806102610-7.jpeg]]
311 + B) HSW1066=1: Import the normal recipe file of regular series HMI (the data in line 1 of the file is invalid);
339 339  
340 -**Perform import**
341 341  
342 -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:
314 +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.
343 343  
344 -* Configure the DB recipe file name by text input object: HDW500 = 3 (recipe file configured in Figure 1),
345 -* Set the recipe function address to: HDW1000 = 64 (the function address configured in Figure 1),
346 -* Transform the CSV recipe file in U disk into DB recipe file with file name “3.rcp2”.
347 347  
348 -**DB recipe file for storing CSV data:**
349 349  
350 -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.
318 + C) 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);
351 351  
352 -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).
353 353  
354 -**Import results:**
321 +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.
355 355  
356 -* HSW242 = 37: Import succeeded;
357 -* HSW242 = 38: Import failed.
358 358  
359 -**Precautions:**
360 360  
361 -* 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);
362 -* 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;
363 -* 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.
364 364  
326 +(3) Perform import
327 +
328 +
329 + 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:
330 +
331 +
332 + A) Configure the DB recipe file name by text input object: HDW500 = 3 (recipe file configured in Figure 1),
333 +
334 +
335 + B) Set the recipe function address to: HDW1000 = 64 (the function address configured in Figure 1),
336 +
337 +
338 + C) Transform the CSV recipe file in U disk into DB recipe file with file name “3.rcp2”.
339 +
340 +
341 +5. DB recipe file for storing CSV data:
342 +
343 +
344 +(1) Simple mode:
345 +
346 +
347 + 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.
348 +
349 +
350 +(2) Advanced mode:
351 +
352 +
353 + 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).
354 +
355 +
356 +6. Import results:
357 +
358 +
359 +(1) HSW242 = 37: Import succeeded;
360 +
361 +
362 +(2) HSW242 = 38: Import failed.
363 +
364 +
365 +
366 +3. Precautions:
367 +
368 +
369 +~1. 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);
370 +
371 +
372 +2. 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;
373 +
374 +
375 +3. 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.
376 +
377 +
378 +
365 365  = (% style="color:inherit; font-family:inherit; font-size:29px" %)**Traditional recipe**(%%) =
366 366  
367 367  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.
... ... @@ -692,10 +692,7 @@
692 692  
693 693  (% class="box infomessage" %)
694 694  (((
695 -✎**Note: **
696 -
697 -* The user name and password must be unique.
698 -* The multi language function of User permission only supported on HMI system version V2.0 or above
709 +✎**Note: **The user name and password must be unique.
699 699  )))
700 700  
701 701  == Settings ==
... ... @@ -705,11 +705,6 @@
705 705  (% style="text-align:center" %)
706 706  [[image:用户权限 1.png||class="img-thumbnail"]]
707 707  
708 -Click on the cell from UserName and Desc, which can support the multi language.
709 -
710 -(% style="text-align:center" %)
711 -[[image:UserPermissionMultilan.png]]
712 -
713 713  1. Click "User Permission" in "Data Tool" toolbar.
714 714  1. Edit user name, click "User0" cell under "UserName", and then enter the user name, one project allows maximum 20 users.
715 715  1. Edit password, click "User0" cell under "PassWord", and then enter the user name.
... ... @@ -723,9 +723,6 @@
723 723  * 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.
724 724  * When the configured file does not have the administrator account, a new user can be added  through "Funtion address" and set as the administrator.
725 725  * 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.
726 -* (((
727 -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.
728 -)))
729 729  
730 730  == Object permission configuration ==
731 731  
... ... @@ -732,11 +732,6 @@
732 732  (% style="text-align:center" %)
733 733  [[image:用户权限 2.png||class="img-thumbnail"]]
734 734  
735 -User operation logs support multi languages configuration. Click on the Log Message, the text editor of multi language will be pop up:
736 -
737 -(% style="text-align:center" %)
738 -[[image:LogMessagesMultilan.png]]
739 -
740 740  **Operation Procedure of Object Permission**
741 741  
742 742  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-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