Skip to Content

Wiki source code of 1.7 IG HMI configuration

Last modified by Theodore Xu on 2024/02/20 14:32
Show last authors
1 = **Connect ig HMI to V-NET** =
2
3 == **Add ig screens** ==
4
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.
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" %)
10 [[image:image-20220616154759-1.png]]
11
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.
13
14 **Import.** Fill in the machine codes to the template file, and import it.
15
16 **Template.** An export template file is an excel form named "batch_mould" with the format to input machine codes.
17
18 (% style="text-align:center" %)
19 [[image:image-20220616154804-2.png]]
20
21 (% class="box infomessage" %)
22 (((
23 **✎Note:** The content of the template file should only be header and machine codes, and all the other contents need to be deleted.
24 )))
25
26 (% style="text-align:center" %)
27 [[image:image-20220616154846-3.png]]
28
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]
30
31 (% style="text-align:center" %)
32 [[image:8-3.png||class="img-thumbnail"]]
33
34 **Device alias. **It is the device name in the device menu bar.
35
36 (% class="box infomessage" %)
37 (((
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)
42 )))
43
44 == **Obtain machine code** ==
45
46 The method of obtaining the machine code is as follows:
47
48 1. PIStudio—[Project]—[Tool]—[Download]—copy the machine code, as shown below.
49
50 (% style="text-align:center" %)
51 [[image:8-4.png||class="img-thumbnail"]]
52
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.
55
56 (% style="text-align:center" %)
57 [[image:1638758068871-905.png||class="img-thumbnail"]]
58
59 == **Basic information** ==
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" %)
64 [[image:8-6.png||height="525" width="1000" class="img-thumbnail"]]
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
68 **Device name. **The alias of the HMI device in the device menu bar.
69
70 **Online status.** Click the refresh button to refresh the online status of the HMI.
71
72 **Machine code.** Each HMI has a unique and independent machine code for the identification of the remote device.
73
74 **Record.** The selected configuration and data would not be updated when the HMI project is downloaded again.
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
83 **Password.** It is the cloud access password, the default is 888888, and it could be modified.
84
85 **Maximum storage of alarm data. **The number of alarm data stored is with a range of 1-50000.
86
87 **Positioning method.**
88
89 1. Device base station positioning.        
90 1. Manual positioning.
91
92 **Unbind the device. **The administrator can click the button [[image:8.1.3.png]] to unbind the device.
93
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]]
95
96 == **Status push** ==
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
103 == **Registers information** ==
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
110 == **Version** ==
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
117 = **Device list** =
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
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.
134
135 **Share Device.** Users could share the device with other accounts for viewing (only for viewing, not operating).
136
137 **Move Group. **Modify the group to which the device belongs, as shown below.
138
139 (% style="text-align:center" %)
140 [[image:8-13.png||class="img-thumbnail"]]
141
142 **Copy machine code.** Copy the machine code of the device.
143
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】.
145
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.
148
149 (% style="text-align:center" %)
150 [[image:8-14.png||class="img-thumbnail"]]
151
152 * **Receive device.** When receiving the ig screen, it needs to reset the name of the device and select the group.
153
154 **Pass-through.** Select the device in the list and right-click, then click **[Pass-through] **to jump to the Pass-through page.
155
156 **Mark on map.** Mark the new latitude and longitude on the map for the current device.
157
158 = **Remote monitoring** =
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
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.
166
167 (% style="text-align:center" %)
168 [[image:8-16.png||class="img-thumbnail"]]
169
170 If the device is offline, it would display that the device configuration project could not be loaded successfully! As shown below.
171
172 (% style="text-align:center" %)
173 [[image:8-17.png||class="img-thumbnail"]]
174
175 = **Data view** =
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
187 == **Communication port** ==
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
199 == **Collect point** ==
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" %)
212 [[image:8-23 2.png||height="449" width="1008" class="img-thumbnail"]]
213
214 == **Alarm record** ==
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
226 == **Data record** ==
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
246 = **Pass-through** =
247
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.Manual.01 V-NET Platform.09 Remote download.WebHome]]**
249
250 (% style="text-align:center" %)
251 [[image:8-30.png||class="img-thumbnail"]]