Skip to Content

Changes for page 06 Data Tool

Last modified by Jett on 2025/02/18 16:43
From version 22.1
edited by Stone Wu
on 2022/08/05 17:28
Change comment: There is no comment for this version
To version 26.1
edited by Stone Wu
on 2022/08/06 11:14
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -241,8 +241,124 @@
241 241  **✎Note: **This function only supported in HMI+, i series, ie series, ig series.
242 242  )))
243 243  
244 +
245 +**description of Adcanced mode**
246 +
247 +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 +
249 +[[image:image-20220806111333-1.jpeg]]
250 +
251 +**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.
252 +
253 +**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).
254 +
255 +**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.
256 +
257 +[[image:image-20220806111355-2.jpeg]]
258 +
259 +**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.
260 +
261 +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.
262 +
263 +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.
264 +
244 244  **Recipe Demo Download Link: **[[Download>>url:https://drive.google.com/open?id=1Cjbq_tW-NIirHFBpxt47g7IKvoYaWqUR]]
245 245  
267 +== Calling CSV recipe file ==
268 +
269 +**Overview**
270 +
271 +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.
272 +
273 +**Operations**
274 +
275 +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.
276 +
277 +(% style="text-align:center" %)
278 +(((
279 +(% style="display:inline-block" %)
280 +[[Figure 1>>image:image-20220806100702-2.jpeg]]
281 +)))
282 +
283 +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.
284 +
285 +(% style="text-align:center" %)
286 +[[image:image-20220806100753-3.jpeg]]
287 +
288 +By configuring the address in the table and combining the recipe function, the CSV recipe files of regular series are imported.
289 +
290 +|=Address range|=Object type|=Address function
291 +|HSW1050 to 1065|Text input object|Enter the CSV recipe file name to import
292 +|HSW1066|Numerical input object|Import CSV file type:(((
293 +* = 0: Custom CSV file (all data in the file is valid)
294 +* = 1: Normal recipe file for regular series HMI (the data in line 1 of the file is invalid)
295 +* = 2: Special recipe file for regular series HMI (the data in line 1 and 2 and column 1 of the file are invalid)
296 +)))
297 +|HSW1067|Numerical input object|(((
298 +Where the CSV file is saved:
299 +
300 +* = 0: In the CsvFile directory of U disk
301 +* = 1: In the CsvFile directory of the SD card
302 +
303 +**The path for offline simulation is: C:\ HMIEmulation\ CustomFileDir\ CsvFile**
304 +)))
305 +|HSW242|Numerical input object|Returns the results of the csv import:(((
306 +* = 37: CSV file imported successfully
307 +* = 38: CSV file import failed
308 +)))
309 +
310 +**Select CSV recipe file (take U disk as an example):**
311 +
312 +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.
313 +
314 +Use the special address of the above table to configure the path of the CSV file: HSW106, configure recipe file name: HSW1050 to1065
315 +
316 +Use HSW1066 address to select the corresponding CSV recipe file type.
317 +
318 +* HSW1066 = 0: Import a user-defined CSV recipe file (all data in the custom CSV file must be valid);
319 +
320 +(% style="text-align:center" %)
321 +[[image:image-20220806101129-5.jpeg]]
322 +
323 +* HSW1066=1: Import the normal recipe file of regular series HMI (the data in line 1 of the file is invalid);
324 +
325 +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.**
326 +
327 +(% style="text-align:center" %)
328 +[[image:image-20220806101520-6.jpeg]]
329 +
330 +* 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);
331 +
332 +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.**
333 +
334 +(% style="text-align:center" %)
335 +[[image:image-20220806102610-7.jpeg]]
336 +
337 +**Perform import**
338 +
339 +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:
340 +
341 +* Configure the DB recipe file name by text input object: HDW500 = 3 (recipe file configured in Figure 1),
342 +* Set the recipe function address to: HDW1000 = 64 (the function address configured in Figure 1),
343 +* Transform the CSV recipe file in U disk into DB recipe file with file name “3.rcp2”.
344 +
345 +**DB recipe file for storing CSV data:**
346 +
347 +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.
348 +
349 +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).
350 +
351 +**Import results:**
352 +
353 +* HSW242 = 37: Import succeeded;
354 +* HSW242 = 38: Import failed.
355 +
356 +**Precautions:**
357 +
358 +* 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);
359 +* 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;
360 +* 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.
361 +
246 246  = (% style="color:inherit; font-family:inherit; font-size:29px" %)**Traditional recipe**(%%) =
247 247  
248 248  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.
image-20220805174501-1.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Stone
Size
... ... @@ -1,0 +1,1 @@
1 +79.3 KB
Content
image-20220805174543-2.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Stone
Size
... ... @@ -1,0 +1,1 @@
1 +80.0 KB
Content
image-20220806100635-1.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Stone
Size
... ... @@ -1,0 +1,1 @@
1 +85.6 KB
Content
image-20220806100702-2.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Stone
Size
... ... @@ -1,0 +1,1 @@
1 +131.3 KB
Content
image-20220806100753-3.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Stone
Size
... ... @@ -1,0 +1,1 @@
1 +10.5 KB
Content
image-20220806101048-4.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Stone
Size
... ... @@ -1,0 +1,1 @@
1 +226.9 KB
Content
image-20220806101129-5.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Stone
Size
... ... @@ -1,0 +1,1 @@
1 +168.6 KB
Content
image-20220806101520-6.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Stone
Size
... ... @@ -1,0 +1,1 @@
1 +24.8 KB
Content
image-20220806102610-7.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Stone
Size
... ... @@ -1,0 +1,1 @@
1 +43.9 KB
Content
image-20220806111333-1.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Stone
Size
... ... @@ -1,0 +1,1 @@
1 +131.4 KB
Content
image-20220806111355-2.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Stone
Size
... ... @@ -1,0 +1,1 @@
1 +135.4 KB
Content