Skip to Content

Changes for page 06 Data Tool

Last modified by Jett on 2025/02/18 16:43
From version 25.1
edited by Stone Wu
on 2022/08/06 10:27
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
Content
... ... @@ -250,99 +250,132 @@
250 250  
251 251  == Calling CSV recipe file ==
252 252  
253 -**Overview**
254 254  
254 +~1. Overview:
255 +
256 +
255 255  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.
256 256  
257 -**Operations**
258 258  
259 -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.
260 +2 Operations
260 260  
261 -(% style="text-align:center" %)
262 -(((
263 -(% style="display:inline-block" %)
264 -[[Figure 1>>image:image-20220806100702-2.jpeg]]
265 -)))
266 266  
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.
264 +
265 +
266 +
267 +Figure 1
268 +
269 +
267 267  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 268  
269 -(% style="text-align:center" %)
270 -[[image:image-20220806100753-3.jpeg]]
271 271  
272 -By configuring the address in the table and combining the recipe function, the CSV recipe files of regular series are imported.
273 273  
274 -|=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
275 275  |HSW1050 to 1065|Text input object|Enter the CSV recipe file name to import
276 -|HSW1066|Numerical input object|Import CSV file type:(((
277 -* = 0: Custom CSV file (all data in the file is valid)
278 -* = 1: Normal recipe file for regular series HMI (the data in line 1 of the file is invalid)
279 -* = 2: Special recipe file for regular series HMI (the data in line 1 and 2 and column 1 of the file are invalid)
280 -)))
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)
281 281  |HSW1067|Numerical input object|(((
282 282  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
283 283  
284 -* = 0: In the CsvFile directory of U disk
285 -* = 1: In the CsvFile directory of the SD card
286 -
287 -**The path for offline simulation is: C:\ HMIEmulation\ CustomFileDir\ CsvFile**
289 +The path for offline simulation is: C:\ HMIEmulation\ CustomFileDir\ CsvFile
288 288  )))
289 -|HSW242|Numerical input object|Returns the results of the csv import:(((
290 -* = 37: CSV file imported successfully
291 -* = 38: CSV file import failed
292 -)))
291 +|HSW242|Numerical input object|Returns the results of the csv import:
292 +~= 37: CSV file imported successfully
293 +~= 38: CSV file import failed
293 293  
294 -**Select CSV recipe file (take U disk as an example):**
295 +4. Select CSV recipe file (take U disk as an example):
295 295  
296 -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.
297 297  
298 -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.
299 299  
300 -Use HSW1066 address to select the corresponding CSV recipe file type.
301 301  
302 -* 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
303 303  
304 -(% style="text-align:center" %)
305 -[[image:image-20220806101129-5.jpeg]]
306 306  
307 -* 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.
308 308  
309 -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.**
310 310  
311 -(% style="text-align:center" %)
312 -[[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);
313 313  
314 -* 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);
315 315  
316 -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.**
317 317  
318 -(% style="text-align:center" %)
319 -[[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);
320 320  
321 -**Perform import**
322 322  
323 -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.
324 324  
325 -* Configure the DB recipe file name by text input object: HDW500 = 3 (recipe file configured in Figure 1),
326 -* Set the recipe function address to: HDW1000 = 64 (the function address configured in Figure 1),
327 -* Transform the CSV recipe file in U disk into DB recipe file with file name “3.rcp2”.
328 328  
329 -**DB recipe file for storing CSV data:**
330 330  
331 -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);
332 332  
333 -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).
334 334  
335 -**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.
336 336  
337 -* HSW242 = 37: Import succeeded;
338 -* HSW242 = 38: Import failed.
339 339  
340 -**Precautions:**
341 341  
342 -* 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);
343 -* 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;
344 -* 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.
345 345  
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 +
346 346  = (% style="color:inherit; font-family:inherit; font-size:29px" %)**Traditional recipe**(%%) =
347 347  
348 348  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-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