Changes for page 06 Data Tool

Last modified by Molly on 2025/05/12 11:41

From 19.2 to 19.1 From 37.1 to 36.1

From version 36.1

edited by Jim
on 2023/08/11 09:45

Change comment: There is no comment for this version

To version 19.2

edited by Hunter
on 2022/07/29 14:59

Change comment: Update document after refactoring.

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)
Attachments (0 modified, 0 added, 18 removed)

Details

Page properties

Author

@@ -1,1 +1,1 @@
--XWiki.Jim
++XWiki.Hunter

Content

@@ -3,51 +3,49 @@
  = **Alarm** =
--== Bit alarm ==
++== **Bit Alarm** ==
--Click "Project"→"Bit Alarm", it is displayed as the following figure.
++Click "Project"->"Bit Alarm", it is displayed as the following figure.
  (% style="text-align:center" %)
  [[image:位报警 1.png||data-xwiki-image-style-alignment="center" class="img-thumbnail"]]
--**Group No.: **Group number of Bit alarm. The name is unique and cannot be duplicated.
++**(1) Group No.: **Group number of Bit alarm. The name is unique and cannot be duplicated.
--**Bit Address: **Bit address of alarm monitoring
++**(2) Bit Address: **Bit address of alarm monitoring
--* **Record bit alarm by default:**  Whether to record the alarm history data of bit alarm, if checked, it will be saved in the designated storage location.
--* **Not save alarm OFF:** If checked, after the alarm is dismissed, the corresponding alarm records will be deleted from the log file.
++(% start="1" %)
++1. **Record bit alarm by default:**  Whether to record the alarm history data of bit alarm, if checked, it will be saved in the designated storage location.
++1. **Not save alarm OFF:** If checked, after the alarm is dismissed, the corresponding alarm records will be deleted from the log file.
--**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)
++**(3) 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)
--(% class="box infomessage" %)
--(((
  **✎Note:**
  * 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.
  * 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:
--(% class="table-bordered" style="margin-left:auto; margin-right:auto; width:358px" %)
++(% style="margin-left:auto; margin-right:auto; width:358px" %)
  |=(% style="width: 79px;" %)Series|=(% style="width: 276px;" %)Number of Alarm upload to Cloud
  |(% style="width:79px" %)8000-R|(% style="text-align:center; width:276px" %)200
  |(% style="width:79px" %)9000-R|(% style="text-align:center; width:276px" %)200
  |(% style="width:79px" %)3000ig|(% style="text-align:center; width:276px" %)20
  |(% style="width:79px" %)8000ig|(% style="text-align:center; width:276px" %)200
--)))
--**Alarm Condition:** It sets alarm trigger condition, there are two types: alarm when ON and alarm when OFF.
++**(4) Alarm Condition:** It sets alarm trigger condition, there are two types: alarm when ON and alarm when OFF.
--**Alert: **It is used to mark whether the alarm has occurred. if an alarm occurs, the address of "control bit" will be written to 1. If "clear alert when alarm OFF" is checked, the address of "control bit" will be written to 0.
++**(5) Alert: **It is used to mark whether the alarm has occurred. if an alarm occurs, the address of "control bit" will be written to 1. If "clear alert when alarm OFF" is checked, the address of "control bit" will be written to 0.
--**Beep when alarm ON: **The beep works when the alarm is triggered. If "beep once" is checked, bit address alarm only beep once and stop.
++**(6) Beep when alarm ON: **The beep works when the alarm is triggered. If "beep once" is checked, bit address alarm only beep once and stop.
--**Content: **It is used for setting alarm content (command).
++**(7) Content: **It is used for setting alarm content (command).
--**Alarm Screen: **Pop-up alarm screen (it need to be sub-screen);
++**(8) Alarm Screen: **Pop-up alarm screen (it need to be sub-screen);
--* **Position: **The location of the screen alarm display.
--* **Pop-up Interval: **The time of reopen the alarm screen when alarm screen closed.
--* **Pop-up once: **Pop up alarm screen once, and the screen would not pop up again
--* **Close window when alarm off: **Automatically close the alarm screen when alarm off.
++1. **Position: **The location of the screen alarm display.
++1. **Pop-up Interval: **The time of reopen the alarm screen when alarm screen closed.
++1. **Pop-up once: **Pop up alarm screen once, and the screen would not pop up again
++1. **Close window when alarm off: **Automatically close the alarm screen when alarm off.
  **✎Note:**
@@ -56,43 +56,43 @@
  **Operating Procedures of Adding One Alarm**
--* Click "Project"→"Bit Alarm" as below shows.
++1. Click "Project"->"Bit Alarm" as below shows.
  (% style="text-align:center" %)
  [[image:8.Basic Function_html_5f8da20315334bac.png||data-xwiki-image-style-alignment="center" height="144" width="539" class="img-thumbnail"]]
--* Click "Add" button to open "Bit Alarm" setting window.
++(% start="2" %)
++1. Click "Add" button to open "Bit Alarm" setting window.
  (% style="text-align:center" %)
  [[image:8.Basic Function_html_94a019683b506e15.png||data-xwiki-image-style-alignment="center" height="307" width="554" class="img-thumbnail"]]
--* Set "Bit Address".
--* Set "Alarm Condition".
--* Set "Content".
--* Other settings can be set according to the actual situation".
--* Click "OK" button to complete settings.
++(% start="3" %)
++1. Set "Bit Address".
++1. Set "Alarm Condition".
++1. Set "Content".
++1. Other settings can be set according to the actual situation".
++1. Click "OK" button to complete settings.
--== Word alarm ==
++== **Word Alarm** ==
  Word alarm is to monitor the word address of a device. If the data meets the set conditions, an alarm will be generated.
--Click "Project"→"Word alarm", it is displayed as the following figure.
++Click "Project"->"Word alarm", it is displayed as the following figure.
  (% style="text-align:center" %)
  [[image:字报警 1.png||class="img-thumbnail"]]
--**Alarm Name:** You can set alarm name for it. Alarm Name can only consist of (0~~9), (a~~z), (A~~Z), ('_'), (' ') and other non-English characters.
++**(1) Alarm Name:** You can set alarm name for it. Alarm Name can only consist of (0~~9), (a~~z), (A~~Z), ('_'), (' ') and other non-English characters.
--**Alarm Address: **It is used for setting word address for word alarm, such as HDW0.
++**(2) Alarm Address: **It is used for setting word address for word alarm, such as HDW0.
--**Data Format: **16-bit unsigned decimal, 16-bit signed decimal, 16-bit BCD, 32-bit unsigned decimal, 32-bit signed decimal, 32-bit BCD, 32-bit float.
++**(3) Data Format: **16-bit unsigned decimal, 16-bit signed decimal, 16-bit BCD, 32-bit unsigned decimal, 32-bit signed decimal, 32-bit BCD, 32-bit float.
--**Group No.: **Group number of word alarm. The name is unique and cannot be duplicated.
++**(4)  Group No.: **Group number of word alarm. The name is unique and cannot be duplicated.
--**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)
++**(5) 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)
--(% class="box infomessage" %)
--(((
  **✎Note:**
  * 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,13 +104,12 @@
  |(% style="width:79px" %)9000-R|(% style="text-align:center; width:276px" %)200
  |(% style="width:79px" %)3000ig|(% style="text-align:center; width:276px" %)20
  |(% style="width:79px" %)8000ig|(% style="text-align:center; width:276px" %)200
--)))
--**Record alarm:**  Whether to record the alarm history data of word alarm, if checked, it will be saved in the designated storage location.
++**(6) Record alarm:**  Whether to record the alarm history data of word alarm, if checked, it will be saved in the designated storage location.
--**Not save alarm OFF:** If checked, after the alarm is dismissed, the corresponding alarm records will be deleted from the log file.
++**(7) Not save alarm OFF:** If checked, after the alarm is dismissed, the corresponding alarm records will be deleted from the log file.
--**Alarm Condition**: Alarm is triggered when designated address meets the alarm condition, it provides four conditions;
++**(8) Alarm Condition**: Alarm is triggered when designated address meets the alarm condition, it provides four conditions;
 . **High alarm:** Alarm is triggered when it reaches high limit. It can be a constant or a variable
 . **Low alarm:** Alarm is triggered when it reaches low limit. It can be a constant or a variable
@@ -117,11 +117,11 @@
 . **Range alarm:** Alarm is triggered when it exceeds the range. It can be a constant or a variable
 . **Equivalent alarm: **Alarm is triggered when the value equals to the given data. It can be a constant or a variable
--**Alarm Info: **It is used for setting alarm content (command);
++**(9) Alarm Info: **It is used for setting alarm content (command);
--**Alert: **It is used to mark whether the alarm has occurred. if an alarm occurs, the address of "control bit" will be written to 1. If "clear alert when alarm OFF" is checked, the address of "control bit" will be written to 0.
++**(10) Alert: **It is used to mark whether the alarm has occurred. if an alarm occurs, the address of "control bit" will be written to 1. If "clear alert when alarm OFF" is checked, the address of "control bit" will be written to 0.
--**Alarm Screen: **Pop-up alarm screen (it need to be sub-screen);
++**(11) Alarm Screen: **Pop-up alarm screen (it need to be sub-screen);
 . **Position: **The location of the screen alarm display.
 . **Pop-up Interval: **The time of reopen the alarm screen when alarm screen closed.
@@ -128,36 +128,38 @@
 . **Pop-up once: **Pop up alarm screen once.
 . **Close window when alarm off: **Automatically close the alarm screen when alarm off.
--**Beep when alarm ON: **beep works when the alarm is triggered, in the default mode, the beep works until the alarm is released.
++**(12) Beep when alarm ON: **beep works when the alarm is triggered, in the default mode, the beep works until the alarm is released.
--**Beep once:** Beep works once, when alarm is triggered.
++**(13) Beep once:** Beep works once, when alarm is triggered.
--**Alarm List**
++**(14) Alarm List**
  It displays all the word alarm lists; it will show the alarm information;
  **Operating Procedures of Adding One Alarm**
--* Click "Project"→ "Word Alarm" as below shows.
++1. Click "Project"-> "Word Alarm" as below shows.
  (% style="text-align:center" %)
  [[image:8.Basic Function_html_1b59522c984cd7c2.png||height="144" width="492" class="img-thumbnail"]]
--* Click "AddClick" button to open "Word Alarm" setting window.
++(% start="2" %)
++1. Click [Add] button to open [Word Alarm] setting window.
  (% style="text-align:center" %)
  [[image:8.Basic Function_html_942107c81fc6901c.png||height="307" width="554" class="img-thumbnail"]]
--* Set Basic information of word alarm.
--* Set "Content".
--* Other settings can be set according to the actual situation.
--* Click "OK" button to complete settings.
++(% start="3" %)
++1. Set Basic information of word alarm.
++1. Set "Content".
++1. Other settings can be set according to the actual situation.
++1. Click "OK" button to complete settings.
  **HMI Alarm Demo Download Link**
  [[https:~~/~~/drive.google.com/open?id=1Llq03CMISM_1mMIfU308hxFbs4rGdQGP>>url:https://drive.google.com/open?id=1Llq03CMISM_1mMIfU308hxFbs4rGdQGP]]
--= **Recipe** =
++= **{{id name="_Toc17174"/}}{{id name="_Recipe"/}}Recipe** =
  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.
@@ -182,204 +182,104 @@
  (% style="text-align:center" %)
  [[image:8-1Recipe.png]]
--**Basic**
++**(1) Basic**
--* **Recipe Folder:** Give Recipe folder name (It can be used, when setting Recipe display object);
--** (% class="box infomessage" %)
--(((
--**✎Note: **Recipe Folder name can only consist of (0~~9), (a~~z), (A~~Z), ('_'), (' ') and other non-English characters;
--)))
--* **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.
--* **Elements:** It sets members' initial number of each group;
--* **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;
--* **Decimal: **It sets integer and scale digits;
++1. **Recipe Folder:** Give Recipe folder name (It can be used, when setting Recipe display object);
--**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.
++* **✎Note: **Recipe Folder name can only consist of (0~~9), (a~~z), (A~~Z), ('_'), (' ') and other non-English characters;
--Function address: all operations are done through function addresses, different operating value is as follows:
++(% start="2" %)
++1. **Group: **It sets the groups' initial number of recipe;
++1. **Elements:** It sets members' initial number of each group;
++1. **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;
++1. **Decimal: **It sets integer and scale digits;
--* = 0: no operation;
--* = 1: trigger read data;
--* = 2: new trigger or update (If there is group number, it updates.)
--* = 4: insert (only valid in advanced mode)
--* = 8: delete (Delete according to the writing group number. If write and read address are consistent, refer to the reading group number);
--* = 16: delete and sorted ((Delete according to the writing group number. If write and read address are consistent, refer to the reading group number)
--* = 64: import CSV recipe file.
++**(2) Mode Selection**
--**Use Multiple File**
++Users could select Simple or Advanced mode.
++**(3) Function Address:**
++
++All the operations for recipe is by this address
++
++* =0 No operation.
++* =1 Read data from recipe.
++* =2 Insert a new group or write data to exist group.
++* =4 Inserted (only advanced mode).
++* =8 Delete.
++* =16 Delete and Sequence.
++
++**(4) Use Multiple File**
++
  Check it to use more than one recipe file in HMI, but this option only valid in [Advanced mode];
--**Select language**
++**(5) Select language**
  The text in HMI can be in 8 languages, user can set language in here;
--**Address**
++**(6) Address**
 . **Group:** This address is for selecting group number;
 . **Start: **This is starting address is for reading and writing in recipe, PIStudio will automatically assigns addresses for each members;
 . **File(16 words): **This address only available when enable the Use Multiple File. This setting address is for input the recipe file's filename.
--**Use Index**
++**(7) Use Index**
  If the value from Group address is changed, Read address will display the new data according to new group number immediately. Relatively, if the data of write address is changed, the corresponding group from table is also changed.
--**Query by Element**
++**(8) Query by Element**
  Enable it for querying group by specify element, select a primary key from all the elements, except the group number. This element value from all groups must be unique if want to set as primary key;
--(% class="box infomessage" %)
--(((
  **✎Note: **When this option is enabled, Group address will be invalid.
--)))
--**Use Independent Write Address**
++**(9) Use Independent Write Address**
  To separate Recipe read address and write address.
--**Use Insert**
++**(10) Use Insert**
  It inserts data into the specified group, if the specified group already exists, it would not cover the original data, while it will move the original group next one after it.
--**Discontinuous Address**
++**(11) Discontinuous Address**
  Whether enable the non-consecutive recipe operation addresses or not. If disabled, the recipe address will recover as the continuous addresses.
--(% class="box infomessage" %)
--(((
  **✎Note: **This function only supported in HMI+, i series, ie series, ig series.
--)))
++**Operating Procedures**
--**Description of adcanced mode**
++1) Click "Project"->"Bit Alarm" as below shows.
--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.
--
--[[image:image-20220806111333-1.jpeg]]
--
--**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.
--
--**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).
--
--**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.
--
--[[image:image-20220806111355-2.jpeg]]
--
--**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.
--
--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.
--
--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.
--
--**Recipe Demo Download Link: **[[Download>>url:https://drive.google.com/open?id=1Cjbq_tW-NIirHFBpxt47g7IKvoYaWqUR]]
--
--== Calling CSV recipe file ==
--
--**Overview**
--
--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.
--
--**Operations**
--
--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.
--
  (% style="text-align:center" %)
--(((
--(% style="display:inline-block" %)
--[[Figure 1>>image:image-20220806100702-2.jpeg]]
--)))
++[[image:8.Basic Function_html_a7d1546a3a9f752f.png||height="144" width="535" class="img-thumbnail"]]
--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.
++2) Click "Add" button to open "Recipe" setting window.
  (% style="text-align:center" %)
--[[image:image-20220806100753-3.jpeg]]
++[[image:8.Basic Function_html_8f04e01413981054.png||height="307" width="554" class="img-thumbnail"]]
--By configuring the address in the table and combining the recipe function, the CSV recipe files of regular series are imported.
++3) Set basic settings for recipe.
--|=Address range|=Object type|=Address function
--|HSW1050 to 1065|Text input object|Enter the CSV recipe file name to import
--|HSW1066|Numerical input object|Import CSV file type:(((
--* = 0: Custom CSV file (all data in the file is valid)
--* = 1: Normal recipe file for regular series HMI (the data in line 1 of the file is invalid)
--* = 2: Special recipe file for regular series HMI (the data in line 1 and 2 and column 1 of the file are invalid)
--)))
--|HSW1067|Numerical input object|(((
--Where the CSV file is saved:
++4) Select mode according to actual condition.
--* = 0: In the CsvFile directory of U disk
--* = 1: In the CsvFile directory of the SD card
++5) Other settings can be set according to the actual situation.
--**The path for offline simulation is: C:\ HMIEmulation\ CustomFileDir\ CsvFile**
--)))
--|HSW242|Numerical input object|Returns the results of the csv import:(((
--* = 37: CSV file imported successfully
--* = 38: CSV file import failed
--)))
++6) Click [OK] button to complete settings.
--**Select CSV recipe file (take U disk as an example):**
++**Recipe Demo Download Link**
--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.
++[[https:~~/~~/drive.google.com/open?id=1Cjbq_tW-NIirHFBpxt47g7IKvoYaWqUR>>url:https://drive.google.com/open?id=1Cjbq_tW-NIirHFBpxt47g7IKvoYaWqUR]]
--Use the special address of the above table to configure the path of the CSV file: HSW106, configure recipe file name: HSW1050 to1065
++= (% style="color:inherit; font-family:inherit; font-size:29px" %)**Traditional Recipe**(%%) =
--Use HSW1066 address to select the corresponding CSV recipe file type.
--
--* HSW1066 = 0: Import a user-defined CSV recipe file (all data in the custom CSV file must be valid);
--
--(% style="text-align:center" %)
--[[image:image-20220806101129-5.jpeg]]
--
--* HSW1066=1: Import the normal recipe file of regular series HMI (the data in line 1 of the file is invalid);
--
--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.**
--
--(% style="text-align:center" %)
--[[image:image-20220806101520-6.jpeg]]
--
--* 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);
--
--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.**
--
--(% style="text-align:center" %)
--[[image:image-20220806102610-7.jpeg]]
--
--**Perform import**
--
--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:
--
--* Configure the DB recipe file name by text input object: HDW500 = 3 (recipe file configured in Figure 1),
--* Set the recipe function address to: HDW1000 = 64 (the function address configured in Figure 1),
--* Transform the CSV recipe file in U disk into DB recipe file with file name “3.rcp2”.
--
--**DB recipe file for storing CSV data:**
--
--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.
--
--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).
--
--**Import results:**
--
--* HSW242 = 37: Import succeeded;
--* HSW242 = 38: Import failed.
--
--**Precautions:**
--
--* 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);
--* 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;
--* 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.
--
--= (% style="color:inherit; font-family:inherit; font-size:29px" %)**Traditional recipe**(%%) =
--
  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.
  Traditional recipe function is valid only when the LEVI project is converted to the PI project, and the original project uses the traditional recipe.
--(% class="box infomessage" %)
--(((
  **✎Note**: Currently, only HMI+, i series, ie series, and ig series support the traditional recipe.
--)))
--== Simple recipe mode ==
++== **Simple recipe mode** ==
  Click the "Traditional Recipe" [[image:8-2TraditionalRecipe.png]] in the "Data tool" bar in the upper side of the software, and the following interface will pop up:
@@ -391,19 +391,16 @@
  * The recipe folder name can only consist of (0~~9), (a~~z), (A~~Z), ('_'), ('').
  * The element name of the recipe cannot include following 5 special characters: " **,** " , " **|** " , " **<** " , " **>** " , " **&** " .
--== Recipe display ==
++== **Recipe display** ==
  Select the file type "Traditional recipe file" in object "Recipe Display", and it is recommended to fill in the traditional recipe group number HSW1612 to the address of select line.
--(% class="box infomessage" %)
--(((
  **✎Note**: The Recipe Display can display up to 50 groups of 100 elements by default, which can be to display out of range by enabled "Address Control". After the "Address Control" is enabled, the display group number can be reached to 100. If want to display more than 100, please adjust the "Start Group" from "Address Control" to index the display group, as following shown:
--)))
  (% style="text-align:center" %)
  [[image:8-4TraditionalRecipeDisplayConfigScreen.png||class="img-thumbnail"]]
--== Recipe transmission address ==
++== **Recipe transmission address** ==
  The special addresses used in the Recipe are shown in the following table:
@@ -454,26 +454,26 @@
 . The RPW register only supports word address access.
 . It can be known from the coding method of RPW~*~*~#~#~#~# that the range of RPW is from RPW000000-RPW990450, wherein the range of group number is 0-100, and the range of element is 0-450.
--== Recipe example ==
++== **Recipe example** ==
  The recipe index makes the modification and display of recipe data more convenient. Only need to modify and display the data of the recipe file through "Numeric Input/Display" Object and "Word Switch".
--Edit the recipe configuration, create three groups of recipes, 4 elements for per group: Red, green, blue, spraying time, as following shown:
++(1) Edit the recipe configuration, create three groups of recipes, 4 elements for per group: Red, green, blue, spraying time, as following shown:
  (% style="text-align:center" %)
  [[image:8-5TraditionalRecipeCaseConfig.png]]
--RPW 0~~3 can display the data of group for the selected line. RPW10000~~10003, RPW20000~~20003, RPW30000~~30003 each address can display the single element. Directly modify the content of the RPW address and then modify the recipe data, as following shown:
++(2) RPW 0~~3 can display the data of group for the selected line. RPW10000~~10003, RPW20000~~20003, RPW30000~~30003 each address can display the single element. Directly modify the content of the RPW address and then modify the recipe data, as following shown:
  (% style="text-align:center" %)
  [[image:8-7TraditionalRecipeCaseShowNoOpera.png]]
--After selecting the 2nd group, trigger the download button to download the whole group data to the corresponding element address (For this case, the data will write into HDW0~~3), or trigger the upload button to upload the content of the element address to the specified recipe group.
++(3) After selecting the 2nd group, trigger the download button to download the whole group data to the corresponding element address (For this case, the data will write into HDW0~~3), or trigger the upload button to upload the content of the element address to the specified recipe group.
  (% style="text-align:center" %)
  [[image:8-6TraditionalRecipeCaseShow.png]]
--= **Trend chart** =
++= **{{id name="_Toc5565"/}}{{id name="_Trend_Chart"/}}Trend Chart** =
  Trend chart function is used for displaying the real-time data in HMI as curve graph, which X axis represent as time, Y axis represent as data.
@@ -511,20 +511,17 @@
  **(4) Curve Table:** The sample address you have set would display on it. Click the corresponding box to modify the content.
--(% class="box infomessage" %)
--(((
  **✎Note: **Curve names can only consist of Chinese characters, (0~~9), (a~~z), (A~~Z), ('_') (' '), and other non-English characters.
--)))
  **Trend Chart Demo Download Link**
  [[https:~~/~~/drive.google.com/open?id=1smnaAvSxOWC0WQK4_uvqHXWn4vUZxGJC>>url:https://drive.google.com/open?id=1smnaAvSxOWC0WQK4_uvqHXWn4vUZxGJC]]
--= **History XY plot** =
++= **{{id name="_Toc7121"/}}{{id name="_History_XY_Plot"/}}History XY Plot** =
  Different from TrendChart, uses need to set history XY curve items in project. Please click "Project"-> "History XY Plot" to open the setting screen.
--Recipe function settings will be display in "[[History XY Plot>>path:https://docs.we-con.com.cn/bin/view/PIStudio/08.Basic%20Function/#HHistoryXYplot]]" object.
++Recipe function settings will be display in "[[History XY Plot>>path:http://docs.we-con.com.cn/wiki/pistudio/view/Helps/06.Objects/#HHistoryXYplot]]" object.
  (% style="text-align:center" %)
  [[image:历史XY 2.png||class="img-thumbnail"]]
@@ -556,31 +556,29 @@
  **(4) Curve Table:** The sample address you have set would display on it. Click the corresponding box to modify the content.
--(% class="box infomessage" %)
--(((
  **✎Note: **Curve names can only consist of Chinese characters, (0~~9), (a~~z), (A~~Z), ('_') (' '), and other non-English characters.
--)))
  **Operating Procedure**
--* Click "Project" → "History XY Plot" to open the function selecting windows.
++1. Click "Project" -> "History XY Plot" to open the function selecting windows.
  (% style="text-align:center" %)
  [[image:8.Basic Function_html_5da6ca44bd28acbe.png||height="144" width="533" class="img-thumbnail"]]
--* Click "Add" button to open "History XY Plot” setting windows.
++(% start="2" %)
++1. Click "Add" button to open [History XY Plot] setting windows.
  (% style="text-align:center" %)
  [[image:8.Basic Function_html_6345b50ea55168fa.png||height="307" width="554" class="img-thumbnail"]]
--* Setting the function of History XY Plot.
--* Click "OK" to save the setting.
++1. Setting the function of History XY Plot.
++1. Click "OK" to save the setting.
  **Download Link**
  [[https:~~/~~/drive.google.com/open?id=1t4_HuRmIJJ-B5ryA2kVMadD9FywKhZ4r>>url:https://drive.google.com/open?id=1t4_HuRmIJJ-B5ryA2kVMadD9FywKhZ4r]]
--= (% style="color:inherit; font-family:inherit; font-size:29px" %)**Data record**(%%) =
++= (% style="color:inherit; font-family:inherit; font-size:29px" %)**Data Record**(%%) =
  The data record function is organized according to the structure below. In a project, there can be multiple record groups, each record group containing multiple channels. Different groups have different sampling times.
@@ -601,9 +601,9 @@
  ✎**Note: **
--After enable the Cloud and check the box of Upload to Cloud, the communication port settings of the address in the imported Data record configuration must be the same as the communication port settings of the current project, otherwise it cannot be used normally.
++1) After enable the Cloud and check the box of Upload to Cloud, the communication port settings of the address in the imported Data record configuration must be the same as the communication port settings of the current project, otherwise it cannot be used normally.
--The number of Data records upload to Cloud shall not exceed the limit value, or the sum of the imported Data records and the number of existing alarm records shall not exceed the limit value. the specific limitation as following table:
++2) The number of Data records upload to Cloud shall not exceed the limit value, or the sum of the imported Data records and the number of existing alarm records shall not exceed the limit value. the specific limitation as following table:
  (% style="margin-left:auto; margin-right:auto; width:513px" %)
  |=(% style="width: 70px;" %)Series|=(% style="width: 442px;" %)Number of Data Record upload to Cloud
@@ -612,10 +612,11 @@
  |(% style="width:70px" %)3000ig|(% style="text-align:center; width:442px" %)50
  |(% style="width:70px" %)8000ig|(% style="text-align:center; width:442px" %)100
--The record group name can only be composed of Chinese characters, (0~~9), (a~~z), (A~~Z), ('_'), ('') and other non-English characters.
++3) The record group name can only be composed of Chinese characters, (0~~9), (a~~z), (A~~Z), ('_'), ('') and other non-English characters.
--Channel name cannot incloud following symbols: ：" , ", " | ", " < ", " > ", " & ".
++4) Channel name cannot incloud following symbols: ：" , ", " | ", " < ", " > ", " & ".
++
  (% class="wikigeneratedid" id="HSettings" %)
  **Settings**
@@ -685,10 +685,17 @@
  * The channel name does not include these 5 special characters: ", ", "| "," <", "> "," & ".
  * The data would be overwritten automatically if the capacity exceed the maximum capacity. For 8000/9000 series, the size of single file cannot exceed 300MB, and total capacity of data records cannot exceed 1000MB. For 3000/3000i/3000ie series, the size of single file cannot exceed 4MB, and total capacity of data records cannot exceed 10MB. If the total amount exceeds the range , an error will be prompted when the project is compiled.
--You could click here to jump to object "[[Data Record Display>>https://docs.we-con.com.cn/bin/view/PIStudio/06.Objects/#HDatarecorddisplay]]"
++You could click here to jump to object "[[Data Record Display>>http://docs.we-con.com.cn/wiki/pistudio/view/Helps/06.Objects/#HDataRecordDisplay]]"
--= **User permission** =
++(% class="wikigeneratedid" id="H" %)
++**PI Data Record Demo Download**
++**[[Demo Link>>https://drive.google.com/open?id=1h7VUsIJqH4LIRjjtphbv9Kmzd6jUMPtE]]**
++
++**[[Video Link>>https://drive.google.com/open?id=1h7VUsIJqH4LIRjjtphbv9Kmzd6jUMPtE]]**
++
++= **{{id name="_Toc3497"/}}{{id name="_User_Permission"/}}User Permission** =
++
  **Introduction**
 . User permission is one of expansion function in PI Series HMI; it provides multi-level of permission for control HMI operations.
@@ -696,26 +696,15 @@
 . Operating record: it records user operations information, the records files are saved in HMI flash; its path is [~\~\flash~\~\UserOperationLogs.db].
 . When it is on simulator mode, the files are saved in C disk, its path is [C:~\~\WECON\UserMgrFile\UserOperationLogs.db].
--(% class="box infomessage" %)
--(((
--✎**Note: **
++✎**Note: **The user name and password must be unique.
--* The user name and password must be unique.
--* The multi language function of User permission only supported on HMI system version V2.0 or above
--)))
++== **Settings** ==
--== Settings ==
++**Open PIStudio software, then operate as the following figure.**
--Open PIStudio software, then operate as the following figure.
--
  (% style="text-align:center" %)
  [[image:用户权限 1.png||class="img-thumbnail"]]
--Click on the cell from UserName and Desc, which can support the multi language.
--
--(% style="text-align:center" %)
--[[image:UserPermissionMultilan.png]]
--
 . Click "User Permission" in "Data Tool" toolbar.
 . Edit user name, click "User0" cell under "UserName", and then enter the user name, one project allows maximum 20 users.
 . Edit password, click "User0" cell under "PassWord", and then enter the user name.
@@ -724,47 +724,31 @@
 . Editing groups' description, but it is not necessary.
 . {{id name="OLE_LINK7"/}}{{id name="OLE_LINK6"/}}Click "Save and Exit" button to complete all settings.
--(% class="box infomessage" %)
--(((
  ✎**Note:**
  * 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.
  * When the configured file does not have the administrator account, a new user can be added  through "Funtion address" and set as the administrator.
  * 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.
--* (((
--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.
--)))
--)))
--(((
--
--)))
++== **Object permission configuration** ==
--== Object permission configuration ==
--
  (% style="text-align:center" %)
  [[image:用户权限 2.png||class="img-thumbnail"]]
--User operation logs support multi languages configuration. Click on the Log Message, the text editor of multi language will be pop up:
++{{id name="OLE_LINK3"/}}{{id name="OLE_LINK4"/}}**Operation Procedure of Object Permission**
--(% style="text-align:center" %)
--[[image:LogMessagesMultilan.png]]
--
--**Operation Procedure of Object Permission**
--
 . Open the object setting windows;
--1. Select "Security" windows;
--1. Check the "User Permission";
--1. Select "Level" to set permission level;
--1. Enter "Log Message", it is for operation records, if it was empty, the operation for this object would be not be recorded;
--1. Select the "Access Denied Setting" mode;
++1. Select [Security] windows;
++1. Check the [User Permission];
++1. Select [Level] to set permission level;
++1. Enter [Log Message], it is for operation records, if it was empty, the operation for this object would be not be recorded;
++1. Select the ~[[[Access Denied Setting>>path:#_Security]]] mode;
  **Log information description**
--A combination of Chinese characters, numbers, and uppercase and lowercase letters can be entered, and the number does not exceed 63.
++1. A combination of Chinese characters, numbers, and uppercase and lowercase letters can be entered, and the number does not exceed 63.
++1. The format of insert variable:{variable address, data format}. e.g., {HDW100,UW2.1}.
--The format of insert variable:{variable address, data format}. e.g., {HDW100,UW2.1}.
--
        The data format are as follows.
  (% class="table-bordered" %)
@@ -780,7 +780,8 @@
  |W|Single word
  |D|Double word
--Examples.
++(% start="3" %)
++1. Examples.
  * Unsigned decimal, BCD, 32-bit float and Signed decimal are as follows.
@@ -893,20 +893,17 @@
  (For both username and password, it can not repetition)
  )))
--(% class="box infomessage" %)
--(((
  **✎Note:**
  * *1: If there is an admin user account, then the new user can no longer add one more admin, that is, one project can only have one administrator account.
  * *1: When adding new user, the password could not be duplicated with other users.
  * *2: When deleting user, it is forbidden to delete the admin user.
--)))
  **User Permission Demo Download**
  [[https:~~/~~/drive.google.com/open?id=1qOiEDvo_1H1YqpoLDpS77dGaAFm8nrGq>>url:https://drive.google.com/open?id=1qOiEDvo_1H1YqpoLDpS77dGaAFm8nrGq]]
--= Message prompt =
++= **{{id name="_Toc29015"/}}{{id name="_MessagePrompt"/}}Message Prompt** =
  A message box is a window used to show some prompts or warnings to users. For example, the application process a task in the process of pop-up message box, suggesting that "U disk has been detected", then the customer can carry out data dump function.
@@ -942,14 +942,11 @@
  User deletes default content or modifies default content, but he wants to give up modification back to original, just click "Reload text".
--(% class="box infomessage" %)
--(((
  **✎Note:**
  * If you do not want this prompt during the running of HMI, please uncheck "Show message".
  * "Reload text" function would be invalid after clicking "save".
  * These 5 special characters are not supported in the header Multi language settings: ",", "|", "<", ">", "&".
--)))
  = **Cloud** =
@@ -976,10 +976,12 @@
  For example:
--* In 3000ig's Cloud, the monitoring tags upload to the Cloud in real time is limited to 100.
--* For 3000ig's Alarm, the Alarm records of word alarms and bit alarms upload to Cloud is limited to 20. (See [["Alarm">>http://docs.we-con.com.cn/wiki/pistudio/view/Helps/08.Basic%20Function/#HAlarm]] for details).
--* For 3000ig's Data record, the Data records upload to Cloud is limited to 50. (For details, please refer to [["Data Record">>http://docs.we-con.com.cn/wiki/pistudio/view/Helps/08.Basic%20Function/#HDataRecord]]).
++~1. In 3000ig's Cloud, the monitoring tags upload to the Cloud in real time is limited to 100.
++2. For 3000ig's Alarm, the Alarm records of word alarms and bit alarms upload to Cloud is limited to 20. (See [["Alarm">>http://docs.we-con.com.cn/wiki/pistudio/view/Helps/08.Basic%20Function/#HAlarm]] for details).
++
++3. For 3000ig's Data record, the Data records upload to Cloud is limited to 50. (For details, please refer to [["Data Record">>http://docs.we-con.com.cn/wiki/pistudio/view/Helps/08.Basic%20Function/#HDataRecord]]).
++
  **(2) Server Selection**
   **Server**: China, ASEAN, and Europe.

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-20220805170000-1.jpeg

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Stone

Size

...	...	@@ -1,1 +1,0 @@
1		-1.1 KB

Content

image-20220805170046-2.jpeg

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Stone

Size

...	...	@@ -1,1 +1,0 @@
1		-34.5 KB

Content

image-20220805170102-3.jpeg

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Stone

Size

...	...	@@ -1,1 +1,0 @@
1		-58.3 KB

Content

image-20220805170147-4.jpeg

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Stone

Size

...	...	@@ -1,1 +1,0 @@
1		-58.3 KB

Content

image-20220805170232-5.jpeg

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Stone

Size

...	...	@@ -1,1 +1,0 @@
1		-58.3 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

Changes for page 06 Data Tool

Summary

Details

Navigation

Table of Contents