Skip to Content

Wiki source code of 3.2 Basic information

Version 1.2 by Devin Chen on 2026/01/12 14:21
Hide last authors
Wecon 1.1 1 = **Basic information** =
2
3 (% class="wikigeneratedid" id="HBasicinformation" %)
4 After adding a v-box or ig HMI, click the device list on the left to select v-box or ig HMI, and it will automatically jump to the device detail interface with seven subpages. The subpages include **Real-time Data, Alarm, Historical data, Cloud SCADA, Pass-through, and C onfiguration**.
5
6 Users can modify the information with valid data, and click the "save" button to finish the modification successfully. As shown in the following figure.
7
8 (% style="text-align:center" %)
9 [[image:基本配置.png]]
10
11 = **Configuration** =
12
13 Select "Basic Information", you can see the name of VBOX, online status and some other functions. You can locate the VBOX on the map to know where the VBOX is located.
14 At the bottom of the basic information, you can Unlink VBOX, restart VBOX, force sync, import and export VBOX configuration. Forced sync is to sync the data directly from cloud service to PC. Import/Export VBOX Configuration, you can export and import the configuration data of existing VBOX to other VBOX, or import the configuration of other VBOX to the existing VBOX.
15
16 (% style="text-align:center" %)
17 [[image:盒子的基础信息.png]]
18
19
20 **Unbind the device**
21
22 The administrator can click "Unlink device" to unbind the v-box or ig screen on the "Basic Information" sub-page under the "Basic Configuration" page. If the configuration of the communication port and monitoring point corresponding to the device is not deleted after unbinding, then the next time the device is added, the data is still exist and automatically transferred to the device. As shown in the following figure.
23
24 **Copy configuration**
25
26 Copy configuration is to copy the device configuration from one v-box to another v-box. If the configurations of multiple devices are the same or alike, the user can configure the information of one v-box first, and copy the configuration to another v-box through the [Copy Configuration] function. The configuration can only be copied if there is a v-box of the same model in the account. As shown in the following figure.
27
28 (% style="text-align:center" %)
29 [[image:基础配置：复制.png]]
30
31 If the configuration is copied successfully, the following figure will be prompted.
32
33 (% style="text-align:center" %)
34 [[image:4-6.png]]
35
36 (% class="box infomessage" %)
37 (((
38 **✎Note: **Only when the configuration information of the "Water Treatment System" of the v-box is empty can the configuration information be copied successfully. If other parameters are configured in the "water treatment system" of v-box, and a copy failure message will be prompted as below.
39 )))
40
41 (% style="text-align:center" %)
42 [[image:4-7.png]]
43
44 (% class="wikigeneratedid" %)
45 **Export/Import**
46
47 (% class="box infomessage" %)
48 (((
49 **✎Note:** The exported files can only be imported into V-BOX of the same series
50 )))
51
52 (% style="text-align:center" %)
53 [[image:导出配置.png]]
54
55 (% style="text-align:center" %)
56 [[image:导出配置.png]]
57
58 == **Communication ** ==
59
60 Users can add, modify and delete communication configuration in **"Configuration"->"Communication", **but only the administrator account has permissions to operate this function.
61
62 (% style="text-align:center" %)
63 [[image:通讯.png]]
64
65 **Add communication port configuration**
66
67 Click the Add button [[image:https://docs.we-con.com.cn/bin/download/V-BOX/V-Net/Manual/01%20V-NET%20Platform/04%20Access%20Configuration/WebHome/4-8%202.png?rev=1.1||alt="4-8 2.png"]] to configure the communication port information. If the configuration are configured successfully, the system will synchronize the configuration information and drive files to the v-box.
68
69 (% style="text-align:center" %)
70 [[image:通讯配置.png]]
71
72 **Modify and Delete**
73
74 The administrator can click the button  [[image:https://docs.we-con.com.cn/bin/download/V-BOX/V-Net/Manual/01%20V-NET%20Platform/04%20Access%20Configuration/WebHome/4-8%203.png?width=36&height=29&rev=1.1||alt="4-8 3.png" height="29" width="36"]] to modify the data of the v-box except for the machine code. If the drive file changes, the monitoring point and data of the communication port will be deleted synchronously.
75
76 Click the button [[image:https://docs.we-con.com.cn/bin/download/V-BOX/V-Net/Manual/01%20V-NET%20Platform/04%20Access%20Configuration/WebHome/4-8%204.png?width=40&height=36&rev=1.1||alt="4-8 4.png" height="36" width="40"]]to delete the communication port configuration, the monitoring point data associated with the communication port configuration under the v-box will also be deleted, and a dialog box will pop up to confirm whether the operation continues.
77
78 == **Network** ==
79
80 Users can view the network configuration of V-BOX and update and change it.
81
82 (% style="text-align:center" %)
83 [[image:network.png]]
84
85 == **Status push(Email)** ==
86
87 Status push is to push the data set by the v-box to the mailbox.
88
89 (% style="text-align:center" %)
90 [[image:状态推送.png]]
91
92 **Email notification. **Set the email push information in Service~-~-Email.
93
94 **Add recipient. **Add the recipient name, email address, and enable the email permission.
95
96 == **Tags usage** ==
97
98 It records the current use and a maximum number of data monitoring points of data monitoring, historical records, and alarm records of the current v-box.
99
100 (% style="text-align:center" %)
101 [[image:数据限制.png]]
102
103 == **Registers information** ==
104
105 It records the V-box information, such as IP address, WIFI.
106
107 (% style="text-align:center" %)
108 [[image:寄存器信息.png]]
109
110 == **Device version** ==
111
112 As the product is constantly updated, the functions of thev-box can be judged based on the version information.
113
114 (% style="text-align:center" %)
115 [[image:固件版本.png]]
116
117 = **Real-time data** =
118
119 In the "Real-time Data" interface, users can configure real-time monitoring points to easily obtain equipment data, and operate online. To add a real-time monitoring point, users need to select a group or enter the real-time monitoring point name, the connected device (ie, communication port), address type, register type, and other data.
120
121 (% style="text-align:center" %)
122 [[image:创建监控点.png]]
123
124 **Add and delete in batch**
125
126 Before batch deletion, select the monitoring points to be deleted, and then select batch deletion. For batch add, you need to set the batch number and increment. The increment is to fill in the address interval settings in those addresses added in batch.
127
128 (% style="text-align:center" %)
129 [[image:批量_增添监控点.png]]
130
131 **Import and export**
132
133 (% style="text-align:center" %)
134 [[image:导入导出1.png]]
135
136 **group management**
137
138 Real-time monitoring points can be grouped and managed, and monitoring points can be moved to different groups. Users can click the  **“Group Settings” **to** **add, modify, and delete groups.
139
140 (% style="text-align:center" %)
141 [[image:监控点群组管理.png]]
142
143 **Real-time data modification**
144
145 Users can modify the real-time data of the monitoring point. Click the data of one monitoring point to edit, and click [[image:https://docs.we-con.com.cn/bin/download/V-BOX/V-Net/Manual/01%20V-NET%20Platform/04%20Access%20Configuration/WebHome/4.28%201.png?width=24&height=24&rev=1.1||alt="4.28 1.png" height="24" width="24"]]，the monitoring point real-time data will be modified to the data entered. Click [[image:https://docs.we-con.com.cn/bin/download/V-BOX/V-Net/Manual/01%20V-NET%20Platform/04%20Access%20Configuration/WebHome/4.28%202.png?width=24&height=24&rev=1.1||alt="4.28 2.png" height="24" width="24"]] to cancel the modification.
146
147 (% style="text-align:center" %)
148 [[image:监控点数据修改.png]]
149
150 == **Address Mapping** ==
151
152 **Required hardware and software configurations**
153
154 * two V-BOXs
155 * two  PLCs
156 * a V-NET account
157
Devin Chen 1.2 158 {{info}}
159 Note: Please use E series and H series V-box, R series V-box doesn't support this function
160 {{/info}}
161
Wecon 1.1 162 **System network topology**
163
164 {{diagram reference="System network topology" cached="false"/}}
165
166 |(% colspan="2" rowspan="1" %)PLC 1|(% rowspan="3" %)(((
167 **⇔**
168 )))|(% colspan="2" rowspan="1" %)PLC 2
169 |D500|source data 1|D500|target data 1
170 |D502|target data 2|D502|source data 2
171
172 V-BOX 1
173
174 * Add monitoring point D500 as "source data 1", and select the monitoring point D500 (target data 1) of V-BOX 2 in the map, as shown in the following figure.
175 * Add monitoring point D502 as "source data 2".
176
177 (% style="text-align:center" %)
178 [[image:地址映射1.jpeg]]
179
180 V-BOX 2
181
182 * Add monitoring point D500 as "source data 1".
183 * Add monitoring point D502 as "source data 2", and select the monitoring point D500 (target data 1) of V-BOX 2 in the map, as shown in the following figure.
184
185 (% style="text-align:center" %)
186 [[image:地址映射2.jpeg]]
187
188 The configuration data will be automatically sent to V-BOX when it is online. Source data 1 of address D500 in PLC1 will  be mapped to the target data 1 of address D500 in PLC2, and the source data 2 of address D502 in PLC2 will be mapped to the target data 2 of address D502 in PLC1.
189
190 |(% colspan="2" rowspan="1" %)V-BOX1 + PLC 1|(% rowspan="3" %)(((
191 **⇔**
192 )))|(% colspan="2" rowspan="1" %)V-BOX 2 + PLC 2
193 |D500|source data 1|D500|target data 1
194 |D502|target data 2|D502|source data 2
195
196 There is a video for mapping.
197
198 [[Mapping video>>https://ftp.we-con.com.cn/Download/WIKI/V-BOX/Video/Mapping-V%20box.mp4]]
199
200 = **Alarm** =
201
202 Users can configure the alarms, and view the current alarms and historical alarms.  Alarms can be divided into current alarm and historical alarm according to the administrator's confirmation.
203
204 **Current alarm**
205
206 The alarm data in the "current alarm" sub-page are all the records that have not yet been "confirmed". The administrator can "confirm" the current alarm data to change its state. The alarm data can be queried according to the code, name, start and end date, and other conditions.
207
208 (% style="text-align:center" %)
209 [[image:报警1.1.png]]
210
211 **Alarm tags**
212
213 In the sub-page of "Alarm Registration" under "Alarm Record", users can add a new alarm. When adding an alarm record, users need to select or enter data such as name, group, the connected device (ie communication port), address type, etc.
214
215 (% style="text-align:center" %)
216 [[image:报警2 2.png]]
217
218 **Historical alarm**
219
220 The alarm data after the "confirm" operation is the historical alarm data and will be transferred to the "historical alarm" sub-page. The data can be queried according to the code, name, start and end date, and other conditions.
221
222 (% style="text-align:center" %)
223 [[image:历史报警.png]]
224
225 = **Historical data** =
226
227 Users can add the address to be monitored, collect data according to conditions, and form data tables, which can be used for query and storage.
228
229 **Historical Data Group Setting**
230
231 When adding data points, you need to first create the group in the Grouping Settings.
232
233 (% style="text-align:center" %)
234 [[image:历史群组创建1.png]]
235
236 In the new group, you can create the group name, select the trigger type, and set the sampling period. Trigger types are: no trigger, trigger to record by cycle, trigger to record once and reset, trigger to record once.
237
238 (% style="text-align:center" %)
239 [[image:群组创建条件.png]]
240
241 **Historical tags**
242
243 On the "**Historical tags"** sub-page of **"Historical Data"**, Users can configure historical data, including name, the connection device (communication port), address type, and register type, etc.
244
245 (% style="text-align:center" %)
246 [[image:创建历史监控点.png]]
247
248 **Data query**
249
250 On the "**Data"** sub-page of **"Historical Data"**, Users can query and delete historical data. including name, the connection device (communication port), address type, and register type, etc., 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.
251
252 (% style="text-align:center" %)
253 [[image:历史数据查询.png]]
254
255 = **Cloud SCADA** =
256
257 **Cloud SCADA **is to monitor remote configuration interface.
258
259 (% style="text-align:center" %)
260 [[image:scada1.png]]
261
262 One v-box can be bound to at most one cloud SCADA project.
263
264 * If the v-box is not bound to a cloud SCADA  project, it will prompt "you have not bound the Web SCADA project for Device, please bind it!".
265 * If the bound project has been deleted, it will prompt "The project you bound has been deleted or you have no permission to view it! Please rebind.". Shown as below.
266
267 (% style="text-align:center" %)
268 [[image:4-35.png]]
269
270 V-box will preference to use the cloud SCADA project in the template. If a cloud SCADA project template has been bound to the v-box, it cannot bind or modify the cloud SACDA project of the v-box separately.
271
272 If the v-box is not bound to a template, the v-box can choose to bind the cloud SCADA project specified in the cloud SCADA platform. The cloud SCADA project across the v-box is not optional.
273
274 The v-box uses The template cloud SCADA project to design on the cloud SCADA platform, But bthe browsing and viewing access are in the V-NET. The projects can not be browsed and viewed in the cloud SCADA platform.
275
276 If the template project is modified, Cloud SCADA of all v-boxes using this template will update synchronously.
277
278 = **LUA script** =
279
280 == **Lua script management** ==
281
282 Click **"LUA script" **to jump to the **LUA script management module** of v-box. The module has the functions including a script list, new script, edit script, delete scripts in batch, sync scripts, sync scripts in batch, import scripts, export scripts, debug, view box scripts, etc.
283
284 (% style="text-align:center" %)
285 [[image:4-37.png||class="img-thumbnail"]]
286
287 **New script**
288
289 **Create a new script**
290
291 Click the button [[image:4.6.1 1.png]] to fill in the name and execution, then click "save and next" to create a new script.
292
293 (% style="text-align:center" %)
294 [[image:4-38.png||class="img-thumbnail"]]
295
296 * **Name. T**he name of the script must start with [a-z, A-Z] and a maximum of 32 characters are allowed.
297 * **Execution. **There are four script execution conditions as the following.
298
299 |=Execution condition|=Function|=Number
300 |initialization|Execute only once after power on.|Maximum one
301 |Execution if connected|Execute after the v-box is connected to the server.|Maximum one
302 |Execution if Disconnected|Execute when the box is disconnected from the server.|Maximum one
303 |Timing|(((
304 Executed cyclically according to the set timing time
305 )))|Maximum five
306
307 * **Timing. **If the user selects "Timing" as execution condition, the time and the time unit need to be entered.
308
309 (% style="text-align:center" %)
310 [[image:4-38 1.png||class="img-thumbnail"]]
311
312 (% class="box infomessage" %)
313 (((
314 **✎Note: **The script** **can not be modified after it is created except for the timing.
315 )))
316
317 **Edit script**
318
319 * Click** **[[image:编辑.png]]to jump to the LUA script edit interface and the script editor will display the initialization code.
320
321 (% style="text-align:center" %)
322 [[image:4-39 2.png||class="img-thumbnail"]]
323
324 * The LUA script written by the user will be written in the initialized function structure, and the structure is not allowed to be modified
325
326 **Script list**
327
328 The added script is displayed in the script list. A Row represents a script.
329
330 (% style="text-align:center" %)
331 [[image:4-40.png||class="img-thumbnail"]]
332
333 The following table describes the parameters in the script list.
334
335 |=Parameter|=Instruction
336 |Status|The two status of script, including sync and not synced
337 |Name|Script name
338 |Execution|Script execution condition
339 |Enable|Script enablement switch.
340 |Sync|ON is to enable the script, and OFF is to disable the script. When the v-box is offline or penetrating, the button is grayed out and cannot be operated.
341 |Scripts|View the scripts that are already running on the v-box.
342 |Operation|Edit or delete the script.
343
344 **Delete script **
345
346 Edit the button to [[image:删除.png]]delete the script. Select multiple scripts, click the button [[image:4.6.1 3.png]] to delete in batch.
347
348 (% style="text-align:center" %)
349 [[image:4-41.png||class="img-thumbnail"]]
350
351 **Sync in batch**
352
353 Select the scripts in the list, click the button [[image:4.6.1 4.png]] to sync in batch. The failed sync information will display after the sync button in the script list.
354
355 (% style="text-align:center" %)
356 [[image:4-41 1.png||class="img-thumbnail"]]
357
358 (% style="text-align:center" %)
359 [[image:4-41 2.png||class="img-thumbnail"]]
360
361 **~ Import and export script**
362
363 1. **Export script. **Click the button [[image:4.6.1 5.png]], all the scripts of the v-box can be exported as a file with a **.script** extension.
364 1. **Import script. **Click the button** **[[image:4.6.1 6.png]], the file with a **script** extension can be imported to the v-box. After the script is imported, the script in the current v-box is cleared.
365
366 (% class="box infomessage" %)
367 (((
368 **✎Note: **
369
370 1. Replacing the communication port will replace the original communication port in the script with the communication port of the current v-box.
371 1. If the communication port of the current v-box is empty, it will prompt: there is no communication port configuration in the script, no need to replace it.
372 1. If the communication port in the imported script file is empty, it will prompt: there is no communication port configuration in the script, no need to replace it.
373 )))
374
375 **Debug**
376
377 Click the button [[image:4.6.1 2.png]] to jump to the script debug interface. Shown as below.
378
379 (% style="text-align:center" %)
380 [[image:4-43.png||class="img-thumbnail"]]
381
382 == **Script editor** ==
383
384 The script editor is an online editor to write Lua scripts. When creating new scripts and modifying scripts, users can switch to the script editor page to write the Lua script of the v-box script.
385
386 (% style="text-align:center" %)
387 [[image:4-45.png]]
388
389 **Monitoring points list**
390
391 1. The area displays all the monitoring points of the current v-box with a function of search monitoring points.
392 1. Click the line of the monitoring point, and the monitoring point will be inserted at the current cursor of the script editor. The inserted monitoring point will be added with the symbol **"@"** in front of the monitoring point name in the editor and defined as a string. For example, "**@City A temperature**", the monitoring point variable will check grammar following the grammatical rules of the string. After the script is synchronized, the monitoring point variable will be converted to an address on the server-side and sent to the v-box side for use.
393
394 (% class="box infomessage" %)
395 (((
396 **✎Note: **
397
398 1. The address format of the monitoring points are converted to is "**@ address type _ serial number # station number: register type major number. sub number**". If the station number is empty, then remove it. If the sub number is empty, then remove it.
399 1. When the mouse passes over the row where the monitoring point is located, more detailed monitoring point information will be displayed through the floating box, and clicking the floating box can also display it to the cursor of the script editor
400
401
402 )))
403
404 **Toolbar**
405
406 The toolbar is at the top of the script editor.
407
408 (% style="text-align:center" %)
409 [[image:4-46.png]]
410
411
412 From left to right, the functions are as below
413
414 1. **Save codes. **Save the current codes, with the small red dot next to it indicating that the code was modified but not saved.
415 1. **Clear codes.** Clear the current codes in the script editor, and restore them to the initialization structure.
416 1. **Insert new address. **Inserts a new bit or word address at the current cursor.
417 1. **Copy codes. **The shortcut keys are "**ctrl+c**". For some browsers with earlier versions (IE8 and below), it may not be able to copy content for use outside of this editor. It is advised to use "**ctrl+c**".
418 1. **Paste codes.** The shortcut keys are "**ctrl+v**". This button is limited to pasting text copied from the current editor except using Internet Explorer. t is advised to use "**ctrl+v**".
419 1. **Cancel. **Cancel the actions in the editor at each step.
420 1. **Restore. **Restore the actions in the editor at each step.
421 1. **Comment. **Comment or uncomment the code in the current line or the selected line.
422 1. **Help. **Jump to help document of script editor, and it is a simple introduction to Lua script editing.
423
424 **Code editing area**
425
426 The Lua script editor provides Lua scripts for users to write scripts and can perform syntax verification, keyword prompts, common code snippet prompts, variable prompts, code completion, etc. At the same time, it provides monitoring point management functions, which can be directly Insert the address as a variable in the code.
427
428 * **syntax check**
429
430 (% style="text-align:center" %)
431 [[image:4-47 1.png]]
432
433 Users can check the validity of the syntax in real-time when writing Lua code. As shown in the figure above, there will be an icon [[image:4-47 2.png]]next to the line number of the syntax error line, and the error message will be prompted after the mouse placing. When multiple lines have errors, it will be displayed on the first line of the error. After solving the error in this line, it will be displayed on the next line of the error line.
434
435 The syntax check includes the following contents.
436
437 1. Check the spelling of keywords.
438 1. Check the definition of variables.
439 1. Check the usage specifications of operators.
440 1. Check the syntax of the function structure.
441
442 (% class="box infomessage" %)
443 (((
444 **✎Note: **The syntax check above does not include running error checking. Running error checking is an error message that is sent to the box, compiled through the v-box, and returned.
445 )))
446
447 * **Script prompts**
448
449 When writing code, the script editor provides hints for fuzzy matching keywords, defined variables, code snippets, etc. Click the corresponding prompt line to complete the codes.
450
451 (% style="text-align:center" %)
452 [[image:4-48.png]]
453
454
455 The provided prompt codes and complete codes include the following categories:
456
457 1. Keywords. Lua language keywords, built-in method names, built-in constants, library functions.
458 1. Code snippet. commonly used code snippets in Lua language.
459 1. Defined variables (local), the names of all the defined variables.
460
461 |=Name|=Sample code|=Name
462 |(% rowspan="5" %)(((
463 Code snippet
464
465
466 )))|local x = 1|Variable definition
467 |(((
468 function fname(...)
469
470 ~-~- body
471
472 end
473 )))|Function structure
474 |(((
475 for i=1,10 do
476
477 print(i)
478
479 end
480 )))|for loop structure
481 |(((
482 while (condition)
483
484 do
485
486 ~-~- body
487
488 end
489 )))|while loop structure
490 |(((
491 if (condition)
492
493 then
494
495 ~-~- body
496
497 end
498 )))|Conditional structure
499 |Method name|(((
500 _G|_VERSION|assert|collectgarbage|dofile|error|getmetatable|ipairs|" +
501
502 "load|loadfile|next|pairs|pcall|print|rawequal|" +
503
504 "rawget|rawlen|rawset|require|select|setmetatable|" +
505
506 "tonumber|tostring|type|xpcall|create|isyieldable|resume|running|" +
507
508 "status|wrap|yield|debug|gethook|getinfo|getlocal|" +
509
510 "getmetatable|getregistry|getupvalue|" +
511
512 "getuservalue|sethook|setlocal|setmetatable|setupvalue|setuservalue|traceback|upvalueid|upvaluejoin|" +
513
514 "abs|acos|asin|atan|ceil|cos|deg|exp|" +
515
516 "floor|fmod|huge|log|max| maxinteger|min|mininteger|" +
517
518 "modf|pi|rad|random|randomseed|sin|sqrt|tan|" +
519
520 "tointeger|type|ult|clock|date|difftime|time|config|cpath|" +
521
522 "loaded|loadlib|path|preload|searchers|searchpath|byte|char|dump|" +
523
524 "find|format|gmatch|gsub|len|lower|match|pack|packsize|rep|reverse|" +
525
526 "sub|unpack|upper|concat|insert|move|pack|remove|sort|unpack|charpattern|" +
527
528 "codepoint|codes|offset|" +
529
530 "foreachi|maxn|foreach|concat|remove|
531 )))|
532 |Built-in constants|true~|false~|nil~|_G~|_VERSION|
533
534 * **Codes highlight**
535
536 |=**Code type**|=**Color**
537 |Normal code|Black
538 |Keyword|Red
539 |Variable|Black
540 |String|Blue
541 |Built-in method name|Green
542 |Constants and built-in constants|Purple
543 |Library function|Black
544 |Comments, ~[~[xx]]|Gray
545
546 **Note area**
547
548 (% style="text-align:center" %)
549 [[image:4-49.png]]
550
551 1. It is located below the script editor and hidden by default. A prompt is displayed when user clicks a custom method name or the mouse moves over the toolbar button.
552 1. Double click the prompt box or click the button [[image:4-49 2.png]] to close it.
553 1. Click the up or down arrow to expand or collapse the prompt message.
554
555 **Save reminder**
556
557 If the script content is modified and not saved, a confirmation dialog box will be displayed when jumping to another module. The message varies with browsers.
558
559 (% style="text-align:center" %)
560 [[image:4-50.png]]
561
562
563 = Resumable upload =
564
565 Video: [[Resumable upload>>https://ftp.we-con.com.cn/Download/WIKI/V-BOX/Video/Resumableupload.mp4]]
566
567 3000ig/8000ig HMI and RE/RH,E/H V-BOX can support  a function for resumable upload. The function is to temporary save the data when the device is offline and upload those data to Cloud when the device is online again.
568
569 The following table shows the maximum number of the resumable data and the biggest file size of the resumable data:
570
571 |= |=RE/RH|=3000ig/8000ig HMI|=E/H V-BOX
572 |=data|100,000|100,000|2,000
573 |=file size|2M|2M|N/A
574
575 (% class="box infomessage" %)
576 (((
577 Note:
578
579 1.The function don't configure by manual.
580
581 2.When the device is online again, There is a keep-alive interval for about 30s. So data will be lost during the time.
582 )))