Wiki source code of 1 Administration mode

Last modified by Mora Zhou on 2023/12/22 10:15
Show last authors
1 = **Instruction** =
2
3 (((
4 OpenCloud platform can configure to connect V-BOX with third part IIOT through easy built-in Lua script,and access configuration,V-BOX configuration, PLC monitor channel and so on.
5 )))
6
7 (((
8 Finally, PLC data will send to IIOT platform, and not pass WECON server, such as google IOT, HUAWEI IOT, Azure IOT and so on.
9 )))
10
11 (((
12 Link: [[http:~~/~~/cloud.v-box.net/login.html>>url:http://cloud.v-box.net/login.html]]
13 )))
14
15 (% style="text-align:center" %)
16 [[image:OpenCloud for administrition mode_html_10ff5cdd8f17a4bc.png||height="333" width="700"]]
17
18 OpenCloud include two types of accounts.One is administrator account (parent account) for cloud mode.This account can create end-user account(sub account), and configure different IIOT configuration and share to different end-user account. Second is end-user account. This account also can configure different IIOT configuration directly, and configure communication with PLC. Please contact with salesman to register administrator account.
19
20 (% style="text-align:center" %)
21 [[image:OpenCloud for administrition mode_html_b0c8f9de12bdad04.png||height="286" width="400" class="img-thumbnail"]]
22
23 = **Administration account function** =
24
25 == Account information ==
26
27 (% class="wikigeneratedid" id="HEdituserpersonalinformationorcompanyinformation." %)
28 (((
29 Edit user personal information or company information.
30 )))
31
32 (% style="text-align:center" %)
33 [[image:OpenCloud for administrition mode_html_cbd483102782df6.png||height="630" width="700" class="img-thumbnail"]]
34
35 == V-BOX parameters ==
36
37 (((
38 Set the V-BOX custom parameters. Administration account can configure these parameters to end-user account. These parameters can be use in script directly.
39 )))
40
41 == Access configuration ==
42
43 (((
44 (((
45 1.Access configuration is global management configuration. Current administration account can share these access configuration to end-user account. Then the end-user can select access configuration to create project configuration.
46 )))
47 )))
48
49 (((
50 (((
51 2.Access configuration includes **3 configurations: **MQTT configuration, script configuration and customs information.
52 )))
53 )))
54
55 === MQTT configuration ===
56
57 1.Configure the path and parameters for the V-BOX to access the MQTT server. Associate different V-BOX types to use.
58
59 2.When MQTT permission is closed, all V-BOX project configurations (sub configurations) that use this access configuration (parent configuration) will not be able to edit the MQTT configuration module, and when the sub configuration is downloaded to the V-BOX, the V-BOX will only use the access configuration (parent configuration) by default .
60
61 3.When MQTT permission is enabled, the end-user account can edit the MQTT configuration. When the MQTT configuration is sent to the V-BOX, the V-BOX will use project configurations (sub configurations).
62
63 === Script Configuration ===
64
65 1.Configure the script of the V-BOX and use it in association with the "Script Configuration permission" in the model definition.
66
67 (% style="text-align:center" %)
68 [[image:OpenCloud for administrition mode_html_2b12147e47a6035.png||height="100" width="400" class="img-thumbnail"]]
69
70 2.When script permission is closed, all V-BOX project configurations (sub configuration) that use the access configuration (parent configuration) will not be able to edit scripts, and when the project configurations are downloaded to the V-BOX, the V-BOX will only use the scripts in the project configuration by default.
71
72 3.When script permission is turned on, the project configuration can edit the script. When the project configuration is downloaded to the V-BOX, the V-BOX will use all the scripts of the access configuration and project configuration.
73
74 === Customize Information ===
75
76 {{id name="OLE_LINK4"/}}Configuration customization: Configure all the relevant information about the customizable configuration in the gateway project configuration that uses the access configuration.
77
78 Collection point customization: Configure all the relevant information of the customizable collection point in the gateway project configuration that uses the access configuration.
79
80 == Model redefinition ==
81
82 **Model Name**
83
84 Configure the global display name of the V-BOX model (global means all cloud account and end-user account) will display the configured alias).
85
86 **Tag trigger type**
87
88 Configure the number of monitor points under different trigger type groups and different V-BOX models created by end-users who configure administration account management.
89
90 **MQTT and script permissions**
91
92 {{id name="OLE_LINK1"/}}Configure the MQTT and script configuration permissions for project configurations of different V-BOX model.
93
94 **For example:**
95
96 **MQTT Configuration Permissions:**
97
98 1. If the administration account closes the MQTT configuration permission of one V-BOX model (such as V-BOX H-AG), the end-user will not have the right to configure the MQTT module that created with V-BOX H-AG model. When the configuration is downloaded to the V-BOX, the V-BOX will only use the MQTT information in the access configuration by default.
99 1. When the MQTT configuration permission is not closed, the end-user can configure the MQTT configuration that created with V-BOX H-AG model, and when the configuration is downloaded to the V-BOX, the V-BOX will use this V-BOX MQTT configuration.
100
101 **Script Configuration Permissions:**
102
103 1. If the administration account closes the script configuration permission of one V-BOX model (such as V-BOX H-AG), the end-user managed by the administration account will not have the right to configure project configuration script created with H-AG. When the configuration is downloaded to the V-BOX, the V-BOX will only use the script in the access configuration by default.
104 1. When the script configuration permission is not closed, the end-user of the administration account can configure project configuration script create with H-AG, and when the configuration is downloaded to the V-BOX, the V-BOX will use the V-BOX project configuration and all scripts in the associated access configuration.
105
106 == End-user account management ==
107
108 1. (((
109 Supports administration account configuration group management end-users.
110 )))
111 1. (((
112 Supports administration accounts to set up group administrators to manage end-users.
113 )))
114 1. (((
115 Supports administration account to assign access configuration to a certain group (such as user group), then all end-users under the user group will be able to obtain the access configuration when creating V-BOX project configuration.
116 )))
117 1. (((
118 Supports administration account to assign V-BOX project configuration to a certain group (such as user group), then all end-users under the user group can use the project configuration of administration to create V-BOX project configuration.
119 )))
120 1. (((
121 Supports administration account or group administrator to view information such as the configuration of group members and the binding V-BOX of the V-BOX list.
122 )))
123 1. (((
124 Supports administration account to view the V-BOX project configuration of its sub-accounts in the configuration list, and perform addition, deletion, and modification operations.
125 )))
126
127 == Platform name Label ==
128
129 1. (((
130 Support administration account configuration cloud platform name.
131 )))
132 1. (((
133 The configuration name will be synchronized to the administration account sub-account for use, but the sub-account cannot be modified.
134 )))
135
136 (% style="text-align:center" %)
137 [[image:OpenCloud for administrition mode_html_c9f124a11cc6b1f6.png||height="193" width="700" class="img-thumbnail"]]
138
139 == End-user mode ==
140
141 1. (((
142 The page display switched to the end-user mode is the page display under the end-user.
143 )))
144 1. (((
145 End-user mode: Simulate the operational content of the end-user user (sub-account) operation interface.
146 )))
147 1. (((
148 For details, see-"end-user Operation Help Document".
149 )))
150
151 == OpenCloud input restrictions ==
152
153 **welcome page**
154
155 * **The administration account and end-user account: **up to 32 digits (spaces are not allowed).
156 * **Password:** The length is >= 6 digits and <= 32 digits (English and special characters in English are allowed, spaces are not allowed, and cannot be empty).
157 * **Company name: **up to 64 digits (except ·_-+=}]",.?,;: "””[]—()...! Special characters other than "" are limited to input, no spaces, and can be empty ).
158 * **Contact: **up to 16 digits (except ·_-+=}]",.?,;: "””[]—()...! Special characters other than "" are limited to input, no spaces can be entered, and can be empty).
159 * **Contact information: **up to 32 digits (only integers can be entered, spaces are not allowed, and can be empty).
160 * **Cloud platform address: **up to 64 bits (spaces are not allowed, can be empty).
161 * **Company profile-limit:** up to 2000 (no other restrictions, can be empty).
162
163 **V-BOX parameters: **Only 36 V-BOX parameters can be added at most.
164
165 The number of trigger items added to the model definition page must be a positive integer, and the range is limited to 1-9999, and the default is up to 500 if there is no limit (no spaces can be entered, or empty).Total trigger item can not more than 2000.
166
167 **Name restrictions**
168
169 * **Group name and other names:** up to 16 digits (except ·_-+=}]",.?,;: """[]—()...! Special characters other than "" are limited to input, no spaces are allowed , Cannot be empty), the number of groups is unlimited.
170 * **Script name: **up to 32 (spaces and other special characters other than _ are not allowed, and the first character must be a letter).
171
172 **Add end-users**
173
174 * **Username: **up to 16 digits (except ·_-+=}]",.?,;: "””[]—()...! Special characters other than "" are limited to input, no spaces or empty).
175 * **Password-Limit**: The length is greater than or equal to 6 digits and less than or equal to 32 digits (English and special characters in English are allowed, spaces are not allowed, and cannot be empty).
176 * **UID-Limit**: Up to 200 digits (spaces are not allowed).
177
178 The period of the collection point configuration: a positive integer ranging from 1 to 30000 (spaces are not allowed).
179
180 Time limit for timing execution: one day, 1-24 hours, 1-1440 minutes, 1-86400 seconds, 1000-86400000 milliseconds.
181
182 **MQTT configuration:**
183
184 * **Server address:** up to 64 bits (spaces are not allowed, cannot be empty, conform to ip address specifications).
185 * Port: a positive integer in the range of 0-65535 (spaces are not allowed, cannot be empty, only numbers can be entered, excluding decimals and negative numbers).
186 * **Heartbeat interval (seconds):** range 1-86400 positive integers (spaces are not allowed, cannot be empty, only numbers can be entered, excluding decimals and negative numbers).
187
188 MQTT username, password, client ID: up to 200 characters.
189
190 = **Features Module** =
191
192 == OpenCloud Sign in ==
193
194 * User login needs to select account type shown in ②
195 * User login can choose the current display language, as shown in ①, currently only Chinese and English are supported.
196 * User login can select whether to display the password through ③ as shown in the figure.
197 * Users can log in through an account or a bound email.
198
199 (% style="text-align:center" %)
200 [[image:OpenCloud for administrition mode_html_4b1423f713d6780a.png||height="376" width="500" class="img-thumbnail"]]
201
202 Figure 1
203
204 == Personal information page ==
205
206 Users can edit some personal or company information marked in red as shown in the figure below.
207
208 (% style="text-align:center" %)
209 [[image:OpenCloud for administrition mode_html_45e8b40c1adebae4.png||height="575" width="700" class="img-thumbnail"]]
210
211 Figure 2
212
213 == V-BOX parameter page ==
214
215 * Support administration account(parent account) to define V-BOX parameter information and provide it to end-users (sub accounts).
216 * V-BOX parameters are used for the customizable information when the end-user (sub-account) binds the V-BOX and download parameters configuration to the V-BOX. The information content can be read and used by the script function in the V-BOX project configuration (see bns_get_config(string from) in "V-BOX Interface Document" about the introduction of the'bind' function).
217 * The ‘field alias’ field in the V-BOX parameters will be used as a display field when the end-user (sub-account) uses it, and the ‘field name’ field is an operable field in the V-BOX’s internal read field and script after being sent to the V-BOX.
218 * The 36 V-BOX parameter limit is the upper limit.
219 * V-BOX parameters support cross-page selection and batch deletion.
220 * After the user deletes the V-BOX parameters, it cannot be restored.
221
222 (% style="text-align:center" %)
223 [[image:OpenCloud for administrition mode_html_8bcf4ea21838bcca.png||height="414" width="700" class="img-thumbnail"]]
224
225 Figure 3
226
227 (% style="text-align:center" %)
228 [[image:OpenCloud for administrition mode_html_b2d339390cbe40d2.png||height="49" width="800" class="img-thumbnail"]]
229
230 Figure 4
231
232 == Access configuration page ==
233
234 **Associated configuration**
235
236 The access configuration (parent configuration) of the administration account(parent account) is provided to the end-user (sub account) as the associated configuration when creating the V-BOX project configuration (sub configuration).
237
238 **Create configuration**
239
240 Users can create access configurations by customizing or create configurations by using ‘Use IOT Platform Link’ with one click. The access configuration created through "Use IOT Platform Link" will copy the MQTT and script information defined in "Use IOT Platform Link".
241
242 **Use IOT platform link**
243
244 Use IOT Platform Link’ is provided by the system. If it does not exist, the user has no right to choose and use it.
245
246 **Access configuration**
247
248 There are three sub-modules in the access configuration: MQTT, script, and custom information.
249
250 **For example:**
251
252 **MQTT configuration:**
253
254 Information such as the path of the V-BOX accessing the MQTT server and the user name and password is associated with the MQTT configuration permission in the model definition module.
255
256 For the filling method of MQTT information, please refer to some MQTT client software on the market (such as MQTTfx).
257
258 After the information of MQTT is configured, it is used in the script by calling related functions in the "V-BOX LUA Script Function Document"-MQTT operation.
259
260 **For example:**
261
262 * Administration account(parent accounts) can manage end-users (sub accounts) user1 and user2.
263 * The parent account creates an access configuration “config”, and defines the content of the MQTT module in the “config”.
264 * The parent account turn off the MQTT permission of the V-BOX H-AG model and turn on the MQTT permission of the V-BOX H-00 model in the model definition.
265 * User1 and user2, which are sub-accounts, receive the access configuration "config" assigned by the parent account (the administration account are assigned in the end-user account management module, see Chapter 2 <End-user Account Management > for details).
266 * The sub-account uses "config" (parent configuration) as the associated configuration to create the V-BOX project configuration, which is the V-BOX project configuration (sub-configuration) of the V-BOX H-AG and V-BOX H-00 models respectively.
267 * After entering the V-BOX project configuration page, you will find that the sub-account cannot view and edit the MQTT module information in the V-BOX H-AG model sub-configuration, but can view and edit the MQTT module information in the V-BOX H-00 model.
268 * When the sub-account sends the sub-configurations to the V-BOXs of the corresponding models, when the V-BOX H-AG is executing the script, if there are functions in the script that call the MQTT information, then only the parent configuration (config) will be called. When the V-BOX H-00 executes the script, it will only call and execute the MQTT information in the sub-configuration.
269
270 **Script Configuration:**
271
272 The V-BOX runs the script, which is used in association with the script configuration permission in the model definition.
273
274 After administrator account create an access configuration, the system will automatically generate a main script (core_script), which cannot be deleted.
275
276 For the use of the script, please refer to the last chapter <Simple Description of the Script> and "V-BOX Interface Document".
277
278 **For example:**
279
280 * The current administrator account(parent account) can manage end-users (sub accounts) user1 and user2.
281 * And the parent account creates an access configuration "config", and defines two script codes (lua1 and lua2) in the "config" (including the main script created by the system by default as three scripts).
282 * The parent account is again in the model definition module. Turn off the script permissions of the V-BOX H-AG model and turn on the script permissions of the V-BOX H-00 model.
283 * User1 and user2, which are sub-accounts, receive the access configuration "config" assigned by the parent account (the administration account are assigned in the end-user account management module, see Chapter 2 “end-user Account Management” for details).
284 * The sub-account uses "config" (parent configuration) as the associated configuration to create V-BOX project configurations (sub-configurations) of V-BOX H-AG and V-BOX H-00 models respectively.
285 * After entering the sub-configuration details page, you will find that the sub-account cannot view and edit the script module information in the sub-configuration of the V-BOX H-AG model, but can view and edit the script module in the sub-configuration of the V-BOX H-00 model(At this time, the sub-account edited a script lua3).
286 * And when the sub-account sends the sub-configurations to the V-BOXs of the corresponding models, the V-BOX H-AG V-BOX will only execute the scripts core_script, lua1 and lua2 in the parent configuration (config) when executing the scripts, V-BOX H-00 The V-BOX will execute core_script, lua1, lua2, and lua3 in the parent and sub configuration.
287
288 **Customize Information:**
289
290 * Support administration account (parent account) definition, configuration custom information and collection point custom information, which are provided to end-users (sub-accounts).
291 * Configure custom information and collection point Custom information is used for end-users (sub-accounts) to create customizable information when creating V-BOX project configuration and collection points. The information content can be passed through script functions in the script module script of V-BOX project configuration Read and use (for details, please refer to the introduction of'user' function in bns_get_config(string from) in "V-BOX Interface Document").
292 * The'field alias' field in the custom information will be used as a display field when the end-user (sub-account) uses it, and the'field name' field is available in the V-BOX's internal read field and scripts after the V-BOX engineering configuration is sent to the V-BOX Field.
293 * Custom information supports cross-page selection and batch deletion.
294 * After the user deletes the custom information, it cannot be restored.
295
296 **For example:**
297
298 * The current administration account(parent account) can manage end-users (sub accounts) user1 and user2.
299 * And the parent account creates two access configurations config1 and config2, and defines a configuration custom information “con” and a collection point custom information “mon” in the custom information module in config1.
300 * User1 and user2, which are sub-accounts, get the access configuration config1 and config2 assigned by the parent account (cloud merchant users are allocated in the end-user account management module, see Chapter 2 “end-user Account Management Page” for details).
301 * The sub-account uses config1 as the associated configuration to create the V-BOX project configuration (sub-configuration) son1, and the sub-account uses config2 as the associated configuration to create the V-BOX project configuration (sub-configuration) son2.
302 * The sub-account can edit the configuration custom information in son1, but it cannot edit the configuration custom information in son2.
303 * When the sub-account sends the sub-configurations to the V-BOX of the corresponding model, the configuration and the customized information of the collection point configuration will be issued at the same time. When the V-BOX executes the script, if there is a function to read the customized information, it will execute these information.
304
305 (% style="text-align:center" %)
306 [[image:OpenCloud for administrition mode_html_f71908e38622ae26.png||height="238" width="600" class="img-thumbnail"]]
307
308 Figure 5
309
310 (% style="text-align:center" %)
311 [[image:OpenCloud for administrition mode_html_4879c469224e6292.png||height="284" width="600" class="img-thumbnail"]]
312
313 Figure 6
314
315 (% style="text-align:center" %)
316 [[image:OpenCloud for administrition mode_html_c0f04bbf99191e58.png||height="159" width="600" class="img-thumbnail"]]
317
318 Figure 7
319
320 (% style="text-align:center" %)
321 [[image:OpenCloud for administrition mode_html_4c18070a6145ded4.png||height="586" width="700" class="img-thumbnail"]]
322
323 Figure 8
324
325 (% style="text-align:center" %)
326 [[image:OpenCloud for administrition mode_html_65cf791a42e06c03.png||height="107" width="800" class="img-thumbnail"]]
327
328 Figure 9
329
330 (% style="text-align:center" %)
331 [[image:1652067516389-863.png||height="94" width="800" class="img-thumbnail"]]
332
333 Figure 10
334
335 (% style="text-align:center" %)
336 [[image:OpenCloud for administrition mode_html_8b924da4dbc8e96b.png||height="354" width="800" class="img-thumbnail"]]
337
338 Figure 11
339
340 (% style="text-align:center" %)
341 [[image:OpenCloud for administrition mode_html_5122c47f93bed38e.png||height="390" width="800" class="img-thumbnail"]]
342
343 Figure 12
344
345 == Model definition ==
346
347 **Model definition**
348
349 The model definition module can be configured with four major contents: model name, collection point trigger type limit, MQTT permission, and script permission. Among them, for different trigger types, no limit setting means limit by default up to 500.
350
351 **Support function**
352
353 Support administration account to configure model definition information under different V-BOX models.
354
355 Support administration account to define the alias of a current V-BOX model. After the alias is enabled, the current administration account and its sub-accounts will uniformly display the alias.
356
357 **For example:**
358
359 * The current administration account (parent account) can manage end-users (sub accounts) user1 and user2.
360 * And the parent account created an access configuration "config", defined the MQTT information in the "config" and created three scripts including the main running script automatically generated by the system.
361 * And assign "config" to the group where the sub-account is located in the end-user user management module (assign to the group where the sub-account is located, all members of the group will share the configuration, see <end-user Account Management Page> for details).
362 * At the same time, the parent account defines the number of different trigger types of the V-BOX H-AG model in the model definition module (such as: change collection: 10, word trigger: 10, other trigger types are not limited), and the MQTT configuration is disabled Permissions, script permissions are enabled; define the number of different trigger types of V-BOX H-00 models (such as: no trigger: 5, trigger a record and reset: 15, other trigger types are not limited), and enable MQTT Configure permissions, turn off script permissions.
363 * As user1 and user2 as sub-accounts, log in and enter the V-BOX project configuration page, create a V-BOX H-AG V-BOX project configuration (sub-configuration) son1 according to the "config" (parent configuration) assigned by the parent account, and a V-BOX S -00 V-BOX project configuration (sub configuration) son2.
364 * For the sub-configuration son1 of the sub-account, the sub-account cannot operate the MQTT information, but can operate the script (for example, the sub-account creates two scripts at this time).
365 * For the number of collection points in son1 to be added by the sub-account, it will be restricted according to the V-BOX H-AG trigger type limit set in the model definition of the parent account (for example: A total of 10 collection points can be added under all the change collection groups in son1. A total of 10 collection points can be added under all word trigger groups. Under other trigger type groups, for all a certain trigger type group, only 500 can be added at most.).
366 * And when the sub-account sends son1 to the V-BOX, the MQTT information executed by the V-BOX will only execute the MQTT information in "config", and the executed scripts will be three scripts in "config" and two scripts in son1 (a total of five scripts) Joint execution).
367 * For the sub-configuration son2 of the sub-account, the sub-account can operate MQTT information (for example, the sub-account edits and saves the MQTT information at this time), but cannot operate the script.
368 * For the number of collection points in son2 to be added by the sub-account, it will be limited according to the V-BOX H-00 trigger type limit set in the model definition of the parent account (for example: a total of 5 points can be added under all non-trigger groups in son2 Collection points, all trigger one record and reset group can add a total of 15 collection points, under other trigger type groups, for all a certain trigger type group, only up to 500 can be added).
369 * And when the sub-account sends son2 to the V-BOX, the MQTT information executed by the V-BOX will only execute the MQTT information in son2, and the executed script will be the three scripts in "config" (the three scripts are executed together).
370
371 **Configuration Remarks:**
372
373 * f the sub-account is configured with MQTT in the V-BOX H-AG V-BOX project configuration (sub-configuration) associated with "config" (parent configuration), but the parent account closes the MQTT permission of V-BOX H-AG later, then the sub-account Refreshing the page again will not see the MQTT module, and when the sub-account sends the sub-configuration to the V-BOX at this time, the V-BOX only executes the MQTT information in the parent configuration.
374 * If the sub account is in the "config" (parent configuration, MQTT information is configured in config), the MQTT module in the V-BOX H-AG V-BOX project configuration (sub configuration) associated with it, does not fill in and save any information. But the parent account has enabled the MQTT permission of V-BOX H-AG, then when the sub account now sends the sub configuration to the V-BOX, although the MQTT information is configured in the parent configuration, the MQTT information is not configured in the sub configuration, but the parent The MQTT information in the configuration will not be sent to the V-BOX.
375 * If the sub account is in the V-BOX H-AG V-BOX project configuration (sub configuration) associated with the "config" (parent configuration), two scripts are created first, but the parent account closes the script permissions of the V-BOX H-AG later, then when At this time, the sub-account delivers the sub-configuration to the V-BOX, and the V-BOX only executes the script in the parent configuration, not the script created in the sub-configuration.
376
377 (% style="text-align:center" %)
378 [[image:OpenCloud for administrition mode_html_ba6f81dbb9ee42d4.png||height="594" width="800" class="img-thumbnail"]]
379
380 Figure 13
381
382 (% style="text-align:center" %)
383 [[image:OpenCloud for administrition mode_html_3cf6cc97b9c1779a.png||height="613" width="600" class="img-thumbnail"]]
384
385 Figure 14
386
387 (% style="text-align:center" %)
388 [[image:OpenCloud for administrition mode_html_8293481009cbdbf4.png||height="244" width="700" class="img-thumbnail"]]
389
390 Figure 15
391
392 (% style="text-align:center" %)
393 [[image:OpenCloud for administrition mode_html_6452bad3c1dffc96.png||height="300" width="700" class="img-thumbnail"]]
394
395 Figure 16
396
397 (% style="text-align:center" %)
398 [[image:OpenCloud for administrition mode_html_ec81084179024f62.png||height="116" width="700" class="img-thumbnail"]]
399
400 Figure 17
401
402 (% style="text-align:center" %)
403 [[image:OpenCloud for administrition mode_html_20864a168065280d.png||height="321" width="700" class="img-thumbnail"]]
404
405 Figure 18
406
407 (% style="text-align:center" %)
408 [[image:OpenCloud for administrition mode_html_d1804ca92cffb8be.png||height="332" width="600" class="img-thumbnail"]]
409
410 Figure 19
411
412 (% style="text-align:center" %)
413 [[image:OpenCloud for administrition mode_html_933596f0c8367d56.png||height="324" width="400" class="img-thumbnail"]]
414
415 Figure 20
416
417 (% style="text-align:center" %)
418 [[image:OpenCloud for administrition mode_html_56c17fd1ba0f7fd1.png||height="301" width="800" class="img-thumbnail"]]
419
420 Figure 21
421
422 (% style="text-align:center" %)
423 [[image:OpenCloud for administrition mode_html_afc862fe637b51a2.png||height="131" width="800" class="img-thumbnail"]]
424
425 Figure 22
426
427 == end-user account management page ==
428
429 1. end-users are created and managed by administration account-administration account are used as parent accounts, and end-users are used as sub accounts.
430 1. When creating a end-user user, you can choose to fill in the uid. If you fill in the uid, the end-user user can have two login methods, one is the normal login page of the platform; the other is to enter the platform through a third party using uid. If you do not fill in uid, the end-user user can only enter through the platform login page.
431 1. administration account can create different user groups for end-user user management, and enable or disable users.
432 1. administration account can set a end-user user in a certain group as the group administrator to manage all end-users in the group.
433 1. The group administrator has all the functions of the parent account for end-user user management.
434 1. The access configuration (parent configuration) created by administration account can be directly assigned to a group here, and all end-users in the group will share the assigned access configuration (parent configuration, parent configuration is used as a end-user user to create a V-BOX project Used as an associated configuration during configuration).
435 1. The V-BOX project configuration (distribution configuration) created by administration account can be directly assigned to a group here, and all end-users in the group will share the assigned V-BOX project configuration (distribution configuration, the distribution configuration is created as a end-user user with one click Used in V-BOX project configuration, use the distribution configuration to create the V-BOX project, and the data information in the distribution configuration will be copied).
436 1. The parent account can directly view all its sub-account binding V-BOXs and sub-account configuration V-BOX project configuration, and can view the last configuration content issued by the sub-account to a certain V-BOX.
437 1. Administration account can directly configure and debug the V-BOX under the sub-account.
438 1. Administration account can click on a configuration name under the current sub-account on the configuration list page to perform the configuration page, and add, delete and modify the configuration of the sub-account.
439
440 (% style="text-align:center" %)
441 [[image:OpenCloud for administrition mode_html_2f6b6c4bb7e5f679.png||height="266" width="700" class="img-thumbnail"]]
442
443 Figure 23
444
445 (% style="text-align:center" %)
446 [[image:OpenCloud for administrition mode_html_c3bc7326e11604cc.png||height="102" width="800" class="img-thumbnail"]]
447
448 Figure 24
449
450 (% style="text-align:center" %)
451 [[image:OpenCloud for administrition mode_html_64e5d3e98918239a.png||height="97" width="800" class="img-thumbnail"]]
452
453 Figure 25
454
455 (% style="text-align:center" %)
456 [[image:OpenCloud for administrition mode_html_f53b0632cf9f770.png||height="251" width="800" class="img-thumbnail"]]
457
458 Figure 26
459
460 (% style="text-align:center" %)
461 [[image:OpenCloud for administrition mode_html_dfab614371767850.png||height="587" width="700" class="img-thumbnail"]]
462
463 Figure 27
464
465 (% style="text-align:center" %)
466 [[image:OpenCloud for administrition mode_html_8ffb475b9314d615.png||height="247" width="700" class="img-thumbnail"]]
467
468 Figure 28
469
470 (% style="text-align:center" %)
471 [[image:OpenCloud for administrition mode_html_bdc791139875503b.png||height="169" width="700" class="img-thumbnail"]]
472
473 Figure 29
474
475 == Platform name Label ==
476
477 After the administration account log in, they can customize the platform name by clicking the platform name.
478
479 administration account can manage the end-users to log in and uniformly display the platform name defined by the administration account.
480
481 end-users cannot modify the platform name.
482
483 (% style="text-align:center" %)
484 [[image:OpenCloud for administrition mode_html_4adda40dd8f40e42.png||height="140" width="800" class="img-thumbnail"]]
485
486 Figure 32
487
488 (% style="text-align:center" %)
489 [[image:OpenCloud for administrition mode_html_351475357ec9c31b.png||height="207" width="800" class="img-thumbnail"]]
490
491 Figure 33
492
493 == Simple description of the script ==
494
495 For basic functions of the script, please refer to the tutorial in the URL
496
497 [[https:~~/~~/www.runoob.com/lua/lua-tutorial.html>>url:https://www.runoob.com/lua/lua-tutorial.html]]
498
499 For some platform data read and write, internal address operations and other interface functions that need to be used in the script, please refer to the description of the interface functions in the "V-BOX Interface Document".
500
501 There must be a main running function in the definition script, the format is: function xxx.main() end, where xxx is the script name.
502
503 When used in the script to obtain platform custom V-BOX parameters, configure custom parameters, or configure custom parameters for collection points, use the interface function bns_get_config() in the "V-BOX Interface Document".
504
505 For other related operations, please contact technical personnel.