Wiki source code of 08 ig HMI configuration
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
5.1 | 1 | = **Connect ig HMI to V-NET** = |
| |
1.1 | 2 | |
| |
5.1 | 3 | == **Add ig screens** == |
| |
1.1 | 4 | |
| |
5.1 | 5 | When logging in to the V-NET for the first time, users need to add an ig HMI and bind it with the account. The account bound to the ig screen is called the "administrator account". A device could only be bound to one account, that is, the administrator account is unique. |
| |
1.1 | 6 | |
| 7 | When binding an ig screen, users need to know the machine code and password of the device, and enter the device name and set group. All the devices added by the administrator would be placed in the “default group” by default. If the administrator has created a device group, the added devices could also be modified to other groups. | ||
| 8 | |||
| 9 | (% style="text-align:center" %) | ||
| |
2.1 | 10 | [[image:image-20220616154759-1.png]] |
| |
1.1 | 11 | |
| |
5.1 | 12 | **Access key(machine code). **Each ig screen has a unique machine code for remote monitoring equipment identification. If multiple v-boxes or ig screens are bound at the same time, export the template to fill in the machine codes, and then import the form to bind. |
| |
1.1 | 13 | |
| |
5.1 | 14 | **Import.** Fill in the machine codes to the template file, and import it. |
| |
1.1 | 15 | |
| |
5.1 | 16 | **Template.** An export template file is an excel form named "batch_mould" with the format to input machine codes. |
| |
1.1 | 17 | |
| 18 | (% style="text-align:center" %) | ||
| |
2.1 | 19 | [[image:image-20220616154804-2.png]] |
| |
1.1 | 20 | |
| |
5.1 | 21 | (% class="box infomessage" %) |
| 22 | ((( | ||
| |
1.1 | 23 | **✎Note:** The content of the template file should only be header and machine codes, and all the other contents need to be deleted. |
| |
5.1 | 24 | ))) |
| |
1.1 | 25 | |
| 26 | (% style="text-align:center" %) | ||
| |
2.1 | 27 | [[image:image-20220616154846-3.png]] |
| |
1.1 | 28 | |
| |
5.1 | 29 | **Password. **The default password is 888888, and it is the cloud access password. Binding device password for the first time, please refer to the configuration software "PIStudio" [cloud configuration] |
| |
1.1 | 30 | |
| 31 | (% style="text-align:center" %) | ||
| 32 | [[image:8-3.png||class="img-thumbnail"]] | ||
| 33 | |||
| |
5.1 | 34 | **Device alias. **It is the device name in the device menu bar. |
| |
1.1 | 35 | |
| |
5.1 | 36 | (% class="box infomessage" %) |
| 37 | ((( | ||
| |
1.1 | 38 | **✎Note:** |
| 39 | |||
| 40 | 1. If the user** **binds multiple devices at the same time, the passwords of the devices must be consistent. Only one machine code can be entered on a line. When entering multiple machine codes, use the "Enter" key to change the line. If not, the format is wrong, and the binding will fail and an error will be reported. | ||
| 41 | 1. If the user** **binds multiple machine codes in batches, the device alias will use the input device name as the prefix, and the system will automatically add a suffix. Example: Default group (device alias)_1 (automatically added suffix) | ||
| |
5.1 | 42 | ))) |
| |
1.1 | 43 | |
| |
5.1 | 44 | == **Obtain machine code** == |
| |
1.1 | 45 | |
| 46 | The method of obtaining the machine code is as follows: | ||
| 47 | |||
| |
5.1 | 48 | 1. PIStudio—[Project]—[Tool]—[Download]—copy the machine code, as shown below. |
| |
1.1 | 49 | |
| 50 | (% style="text-align:center" %) | ||
| 51 | [[image:8-4.png||class="img-thumbnail"]] | ||
| 52 | |||
| |
5.1 | 53 | (% start="2" %) |
| 54 | 1. Obtain from the ig screen. Long press the upper right corner of the HMI to enter the backstage, and you can see it in "Machine Info" [Machine Id], as shown below. | ||
| |
1.1 | 55 | |
| 56 | (% style="text-align:center" %) | ||
| 57 | [[image:1638758068871-905.png||class="img-thumbnail"]] | ||
| 58 | |||
| |
5.1 | 59 | == **Basic information** == |
| |
1.1 | 60 | |
| 61 | After the administrator adds a device, click on a device from the device list on the left side to enter the device details page. The page includes four sub-pages: “Remote monitoring", “Data view", “Pass-through", and “Basic", as shown in below. | ||
| 62 | |||
| 63 | (% style="text-align:center" %) | ||
| |
2.1 | 64 | [[image:8-6.png||height="525" width="1000" class="img-thumbnail"]] |
| |
1.1 | 65 | |
| 66 | In the "Basic Information" subpage of basic configuration, users could also manage the device information, such as modifying the device name, latitude and longitude, and remarks. After the user inputs modified information, and the input data is legal, click the "Save" button at the bottom. then it would be modified successfully. | ||
| 67 | |||
| |
5.1 | 68 | **Device name. **The alias of the HMI device in the device menu bar. |
| |
1.1 | 69 | |
| |
5.1 | 70 | **Online status.** Click the refresh button to refresh the online status of the HMI. |
| |
1.1 | 71 | |
| |
5.1 | 72 | **Machine code.** Each HMI has a unique and independent machine code for the identification of the remote device. |
| |
1.1 | 73 | |
| |
5.1 | 74 | **Record.** The selected configuration and data would not be updated when the HMI project is downloaded again. |
| |
1.1 | 75 | |
| 76 | The configured data is collection point information, alarm data, and data record data on the IG screen. That is, the selected configuration would not be updated to the cloud with the ig screen at the same time. The project on the tHMI actually has the configuration. | ||
| 77 | |||
| 78 | If users want the cloud and ig screen configurations to be the same, deselect and save the modification, and download the project again or force to synchronization.This operation is to delete all configurations on the cloud and synchronize the configurations on the screen to the cloud. | ||
| 79 | |||
| 80 | (% style="text-align:center" %) | ||
| 81 | [[image:8-7.png||class="img-thumbnail"]] | ||
| 82 | |||
| |
5.1 | 83 | **Password.** It is the cloud access password, the default is 888888, and it could be modified. |
| |
1.1 | 84 | |
| |
5.1 | 85 | **Maximum storage of alarm data. **The number of alarm data stored is with a range of 1-50000. |
| |
1.1 | 86 | |
| |
5.1 | 87 | **Positioning method.** |
| |
1.1 | 88 | |
| 89 | 1. Device base station positioning. | ||
| 90 | 1. Manual positioning. | ||
| 91 | |||
| |
5.1 | 92 | **Unbind the device. **The administrator can click the button [[image:8.1.3.png]] to unbind the device. |
| |
1.1 | 93 | |
| |
5.1 | 94 | After modifying the basic information of the device, users need to click the button [[image:8.1.3 1.png]] to save it successfully. If the save is not successful, click [[image:8.1.3 2.png]] |
| |
1.1 | 95 | |
| |
5.1 | 96 | == **Status push** == |
| |
1.1 | 97 | |
| 98 | In the "Status Push" interface under "Basic ", users could set the ""Email Notification" settings. For details, refer to [[**4.1.5 Status push(Email)**>>http://docs.we-con.com.cn/wiki/vbox/view/1.User%20Manual/01%20V-NET%20Web%20User%20Manual/04%20V-box%20access%20configuration/#H4.1.5Statuspush28Email29]] | ||
| 99 | |||
| 100 | (% style="text-align:center" %) | ||
| 101 | [[image:8-8.png||class="img-thumbnail"]] | ||
| 102 | |||
| |
5.1 | 103 | == **Registers information** == |
| |
1.1 | 104 | |
| 105 | In the “Registers Information" page, users could view the machine code or IP address of the device, Wi-Fi IP, 4G IP and other information, as shown below. | ||
| 106 | |||
| 107 | (% style="text-align:center" %) | ||
| 108 | [[image:8-9.png||class="img-thumbnail"]] | ||
| 109 | |||
| |
5.1 | 110 | == **Version** == |
| |
1.1 | 111 | |
| 112 | As the product is in the pace of continuous updating, the functional attributes of the device can be judged based on the version information. As shown below. | ||
| 113 | |||
| 114 | (% style="text-align:center" %) | ||
| 115 | [[image:1638758283183-571.png||class="img-thumbnail"]] | ||
| 116 | |||
| |
5.1 | 117 | = **Device list** = |
| |
1.1 | 118 | |
| 119 | The main function of the device module: **Multi-level device list, Custom monitoring point, Search device, **and **Toolbar.** | ||
| 120 | |||
| 121 | The multi-level device list displays all the devices under the account, and displays it in the form of a multi-level grouped tree menu. After selecting the device [[image:屏图标.png]], it would automatically jump to the functional interface, including **Remote monitoring, Data view, Pass-through, **and** Basic**. As shown below. | ||
| 122 | |||
| 123 | (% style="text-align:center" %) | ||
| 124 | [[image:8-11.png||class="img-thumbnail"]] | ||
| 125 | |||
| 126 | When the mouse is located on a device name under a multi-level group, right-click the mouse to display a drop-down list, which includes functions such as Follow, Share Device, Move Group, Copy Access Key, Transfer, Pass-through, Mark on map, etc., as shown in Figure 8- 10 shows: | ||
| 127 | |||
| 128 | Position the mouse on the multi-grade group name, right-click the mouse to display a drop-down list, including **Follow, Share Device, Move Group, Copy Access Key, Transfer, Pass-through, Mark on map**. As shown in the following figure. | ||
| 129 | |||
| 130 | (% style="text-align:center" %) | ||
| 131 | [[image:8-12.png||class="img-thumbnail"]] | ||
| 132 | |||
| |
5.1 | 133 | **Follow.** Select the device in the list and right-click, then click "**follow"** to add the devices you need to focus on to the list, and the followed ig screen could be viewed in the "My Follow" list, right-click and select unfollow to delete it. As shown in the following figure. |
| |
1.1 | 134 | |
| |
5.1 | 135 | **Share Device.** Users could share the device with other accounts for viewing (only for viewing, not operating). |
| |
1.1 | 136 | |
| |
5.1 | 137 | **Move Group. **Modify the group to which the device belongs, as shown below. |
| |
1.1 | 138 | |
| 139 | (% style="text-align:center" %) | ||
| 140 | [[image:8-13.png||class="img-thumbnail"]] | ||
| 141 | |||
| |
5.1 | 142 | **Copy machine code.** Copy the machine code of the device. |
| |
1.1 | 143 | |
| |
5.1 | 144 | **Transfer.** Transfer the device to another account. After the other account agrees to receive it, the device would be bound to the account, and the device would be removed from the removed account. For details, please refer to 【Transfer Device】. |
| |
1.1 | 145 | |
| |
5.1 | 146 | * **Remove device**. When transfer the device to another account, you need to fill in the information of the transferred user and the password of the device. The account information will appear if you fill in the right one. Confirm that the account information of the opposite is accurate and then transfer. As shown in Figure 8-12: |
| 147 | * When removing the ig screen, users need to fill in the information of the transferred user and the password of the ig screen. The account information will appear if you fill in it correctly, and confirm that the information to transfer it. As shown in the following figure. | ||
| |
1.1 | 148 | |
| 149 | (% style="text-align:center" %) | ||
| 150 | [[image:8-14.png||class="img-thumbnail"]] | ||
| 151 | |||
| |
5.1 | 152 | * **Receive device.** When receiving the ig screen, it needs to reset the name of the device and select the group. |
| |
1.1 | 153 | |
| |
5.1 | 154 | **Pass-through.** Select the device in the list and right-click, then click **[Pass-through] **to jump to the Pass-through page. |
| |
1.1 | 155 | |
| |
5.1 | 156 | **Mark on map.** Mark the new latitude and longitude on the map for the current device. |
| |
1.1 | 157 | |
| |
5.1 | 158 | = **Remote monitoring** = |
| |
1.1 | 159 | |
| 160 | Remote monitoring could display the project page of the current screen in real-time, and realize the operation of the project on the web page, remote monitoring of the screen, and the control of the screen, etc. As shown below. | ||
| 161 | |||
| 162 | (% style="text-align:center" %) | ||
| 163 | [[image:8-15.png||class="img-thumbnail"]] | ||
| 164 | |||
| |
5.1 | 165 | The remote monitoring screens of the Web➕ ig screens could only display up to 4 screens at the same time. According to the priority of the user entering the remote monitoring interface, that is, when the fifth user access, there would be a prompt as below. |
| |
1.1 | 166 | |
| 167 | (% style="text-align:center" %) | ||
| 168 | [[image:8-16.png||class="img-thumbnail"]] | ||
| 169 | |||
| |
5.1 | 170 | If the device is offline, it would display that the device configuration project could not be loaded successfully! As shown below. |
| |
1.1 | 171 | |
| 172 | (% style="text-align:center" %) | ||
| 173 | [[image:8-17.png||class="img-thumbnail"]] | ||
| 174 | |||
| |
5.1 | 175 | = **Data view** = |
| |
1.1 | 176 | |
| 177 | Data view has six modules, including **Communication port, Collection point, Alarm configuration, Alarm Record, Data Record Configuration, Data Record**. As shown below. | ||
| 178 | |||
| 179 | (% style="text-align:center" %) | ||
| 180 | [[image:8-18.png||class="img-thumbnail"]] | ||
| 181 | |||
| 182 | The data and the configurations for data viewing are all from the configuration software **PIStudio. **The monitoring point could not be added to the V-NET account, and the cloud function should be enabled first. The operation is as below. | ||
| 183 | |||
| 184 | (% style="text-align:center" %) | ||
| 185 | [[image:8-19.png||class="img-thumbnail"]] | ||
| 186 | |||
| |
5.1 | 187 | == **Communication port** == |
| |
1.1 | 188 | |
| 189 | The connection method and protocol name and communication port of HMI could only be viewed, and could not be added or modified. | ||
| 190 | |||
| 191 | (% style="text-align:center" %) | ||
| 192 | [[image:8-20.png||class="img-thumbnail"]] | ||
| 193 | |||
| 194 | The communication port information comes from the information set on the ig screen, and it needs to be configured on the PIStudio. | ||
| 195 | |||
| 196 | (% style="text-align:center" %) | ||
| 197 | [[image:8-21.png||class="img-thumbnail"]] | ||
| 198 | |||
| |
5.1 | 199 | == **Collect point** == |
| |
1.1 | 200 | |
| 201 | It is the data monitoring of the device. The collection point is the monitoring tag. Its read-write, write-only, and read-only permissions also come from the tags set in PIStudio. Users could not add or delete collection points here. | ||
| 202 | |||
| 203 | (% style="text-align:center" %) | ||
| 204 | [[image:8-22.png||class="img-thumbnail"]] | ||
| 205 | |||
| 206 | The read-write permissions of the collection points set in the HMI will directly restrict the modification of the read-write permissions of the collection point in the V-NET. | ||
| 207 | |||
| 208 | (% style="text-align:center" %) | ||
| 209 | [[image:8-23 1.png||class="img-thumbnail"]] | ||
| 210 | |||
| 211 | (% style="text-align:center" %) | ||
| |
2.1 | 212 | [[image:8-23 2.png||height="449" width="1008" class="img-thumbnail"]] |
| |
1.1 | 213 | |
| |
5.1 | 214 | == **Alarm record** == |
| |
1.1 | 215 | |
| 216 | Alarm record of the device and monitoring points could not be added in the V-NET. The data comes from the bit alarm and word alarm configured on the PIStudio. As shown below. | ||
| 217 | |||
| 218 | (% style="text-align:center" %) | ||
| 219 | [[image:8-25.png||class="img-thumbnail"]] | ||
| 220 | |||
| 221 | Users could confirm the alarm and export the data. | ||
| 222 | |||
| 223 | (% style="text-align:center" %) | ||
| 224 | [[image:8-26.png||class="img-thumbnail"]] | ||
| 225 | |||
| |
6.1 | 226 | == **Data record** == |
| |
1.1 | 227 | |
| 228 | It is the historical data of the device. The monitoring points could not be added, and could only be viewed. | ||
| 229 | |||
| 230 | (% style="text-align:center" %) | ||
| 231 | [[image:8-27.png||class="img-thumbnail"]] | ||
| 232 | |||
| 233 | The data comes from the bit alarm and word alarm configured on the PIStudio. As shown below. | ||
| 234 | |||
| 235 | (% style="text-align:center" %) | ||
| 236 | [[image:8-28.png||class="img-thumbnail"]] | ||
| 237 | |||
| 238 | When querying data, users need to select or enter the monitoring point and start and end dates. The display of historical data can be viewed in both tables and curves. As shown below. | ||
| 239 | |||
| 240 | (% style="text-align:center" %) | ||
| 241 | [[image:8-29 1.png||class="img-thumbnail"]] | ||
| 242 | |||
| 243 | (% style="text-align:center" %) | ||
| 244 | [[image:8-29 2.png||class="img-thumbnail"]] | ||
| 245 | |||
| |
5.1 | 246 | = **Pass-through** = |
| |
1.1 | 247 | |
| |
8.1 | 248 | This function allows applications on the computer to download directly to PLC or HMI. The remote download function of pass-through cannot be used on the Web server temporarily, it could be used only on the PC client. For details, refer to **[[09 Remote download.>>doc:V-BOX.V-Net.01 V-NET Platform.09 Remote download.WebHome]]** |
| |
1.1 | 249 | |
| 250 | (% style="text-align:center" %) | ||
| 251 | [[image:8-30.png||class="img-thumbnail"]] |