Wiki source code of 2 End-user mode
Last modified by Mora Zhou on 2023/12/22 10:16
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | = **Description:** = | ||
| 2 | |||
| 3 | (% class="wikigeneratedid" %) | ||
| 4 | The end-user account is a secondary account(Sub account), From the cloud business account(Parent account)Create and manage | ||
| 5 | |||
| 6 | = **Function overview** = | ||
| 7 | |||
| 8 | == Personal information page == | ||
| 9 | |||
| 10 | Edit user personal information. | ||
| 11 | |||
| 12 | == Gateway Management Page == | ||
| 13 | |||
| 14 | * Set Management Gateway Group. | ||
| 15 | * The interface displays information about the gateway. | ||
| 16 | * Support the replacement of gateway configuration, the following is the gateway project configuration, networking configuration, etc. to cover the original gateway running configuration. | ||
| 17 | * End users can customize the configuration of gateway parameters, which are created by the parent account of the end user and used by the end user. | ||
| 18 | * Support gateway operations, such as name editing, switching groups, adding favorites and other basic functions. | ||
| 19 | ** ou can add favorites to commonly used gateways or key focus gateways, which is convenient for users to find. | ||
| 20 | * Support some function buttons of the gateway, such as closing V-NET, restarting the gateway, debugging, firmware upgrade, feedback information, etc. | ||
| 21 | ** After closing V-NET, the gateway will disconnect all external network connections. | ||
| 22 | ** Debug the gateway that is running normally and is executing the script. The platform will see the script running print information reported by the gateway. The debugging function can be used with the feedback information button. | ||
| 23 | ** The feedback function button can check whether the gateway executes the script normally or reports an error, etc. | ||
| 24 | * You can view the last gateway project configuration, network configuration and other information sent to the gateway through the platform. | ||
| 25 | |||
| 26 | == Gateway project configuration page == | ||
| 27 | |||
| 28 | The configuration is sent to the gateway, and the configuration information of the gateway operation. | ||
| 29 | |||
| 30 | The creation of the gateway project configuration must be associated with the access configuration assigned to the cloud provider account (parent account). | ||
| 31 | |||
| 32 | The vwmt compressed package can be used to import the configuration, but the imported configuration must also be associated with the access configuration assigned to the cloud provider account (parent account). | ||
| 33 | |||
| 34 | Gateway project configuration details page (five modules: communication port configuration, collection point configuration, MQTT configuration, script configuration, custom information). | ||
| 35 | |||
| 36 | * Communication port configuration: refer to the related operations of VNET communication port. | ||
| 37 | * Collection point configuration: refer to related operations of VNET monitoring point. | ||
| 38 | ** When adding a collection point, you can define to set custom information for the collection point. The custom information is provided by the parent account of the current account (cloud business account) and used by the end user. | ||
| 39 | ** After the custom information of the gateway project configuration collection point is sent to the gateway through the gateway project configuration, the gateway uses the relevant interface function when executing the script, such as bns_get_config('user') to retrieve and use it, | ||
| 40 | * MQTT configuration: | ||
| 41 | ** Configure the path and parameters of the gateway to access the MQTT server, use the related interface function MQTT.setup_cfg() in the "Hui Box Interface Document" in the script configuration module script to obtain and use MQTT information (see "Hui Box Interface Document" for details 》-MQTT operating instructions). | ||
| 42 | ** If the parent account (cloud merchant account) of the current end-user has closed the relevant permissions, the current user will not be able to see and set the MQTT information. And when the gateway project configuration is delivered to the gateway, the gateway will only use the MQTT information in the access configuration associated with the current gateway project configuration by default. The current user can configure MQTT information only after the parent account has enabled relevant permissions, and when the gateway project configuration is sent to the gateway, the gateway will use the MQTT configuration in the gateway project configuration instead of using the current gateway project configuration to associate access to the MQTT information in the configuration. | ||
| 43 | * Script configuration: | ||
| 44 | ** Configure the running script of the gateway. | ||
| 45 | ** If the parent account of the current end-user (cloud merchant account) has disabled related permissions, the current user will not be able to see and set the script. And when the gateway project configuration is delivered to the gateway, the gateway will only use the script in the access configuration associated with the current gateway project configuration by default. The current user can configure the script after the parent account has enabled the relevant permissions. After the gateway project configuration is sent to the gateway, the gateway will use the script in the gateway project configuration to associate with the current gateway project configuration to access the script in the configuration. | ||
| 46 | * Custom information: | ||
| 47 | ** Customized information can be set for the current gateway project configuration. The customized information is provided by the parent account (cloud business account) of the current account and used by the end user. | ||
| 48 | ** After the gateway project configuration custom information is sent to the gateway through the gateway project configuration, the gateway uses related interface functions such as bns_get_config('user') to retrieve and use when executing the script. | ||
| 49 | |||
| 50 | == Debug page == | ||
| 51 | |||
| 52 | The current user can turn on the debugging function through the online and normally running gateway bound to the account. After the debugging function is turned on, the gateway will report the information printed in the running script to the platform, and the user can see it on the debugging page Related script running information. | ||
| 53 | |||
| 54 | The debugging function can be used in conjunction with the feedback information button on the gateway management page. After the user sends the gateway project configuration to the gateway, the gateway will execute the script that exists in the gateway project configuration. Whether the configuration is delivered successfully and whether the script is running abnormally can be checked through the feedback information function button. If the script is running normally, you can see the corresponding print information on the debugging page after the debugging is turned on. | ||
| 55 | |||
| 56 | == Networking configuration page == | ||
| 57 | |||
| 58 | Users can customize, edit and set the networking mode of different gateway models | ||
| 59 | |||
| 60 | After the user sends the networking configuration to the corresponding model gateway, the gateway will cover the original device networking mode | ||
| 61 | |||
| 62 | == End-user account management page == | ||
| 63 | |||
| 64 | The user can only display and operate the module after being set as a group administrator by the parent account (cloud business account) | ||
| 65 | |||
| 66 | The group administrator manages the end users in a group and group on behalf of the cloud parent account | ||
| 67 | |||
| 68 | Simple description of the script | ||
| 69 | |||
| 70 | = **Functional modules** = | ||
| 71 | |||
| 72 | == End-user account login == | ||
| 73 | |||
| 74 | 1. User login needs to select the radio button shown in ② as shown in the figure. | ||
| 75 | 1. User login can choose the current display language, as shown in Figure ①, currently only Chinese and English are supported. | ||
| 76 | 1. User login can choose whether to display the password through the figure ③. | ||
| 77 | 1. Users can log in through an account or a bound mailbox. | ||
| 78 | 1. User login needs to enter the name of the parent account of the account. | ||
| 79 | |||
| 80 | (% style="text-align:center" %) | ||
| 81 | [[image:Terminal operation help document_html_b00b974062aca7ce.png||height="258" width="600" class="img-thumbnail"]] | ||
| 82 | |||
| 83 | == Personal information page == | ||
| 84 | |||
| 85 | The user can edit some personal information marked in red as shown in the figure below. | ||
| 86 | |||
| 87 | (% style="text-align:center" %) | ||
| 88 | [[image:Terminal operation help document_html_1baf3d69b94a672a.png||height="187" width="800" class="img-thumbnail"]] | ||
| 89 | |||
| 90 | == Gateway Management Page == | ||
| 91 | |||
| 92 | 1. The gateway is bound to the user account, and a series of operations of the gateway are completed on this page. | ||
| 93 | 1. Support users to set different groups and manage the gateway in groups. | ||
| 94 | 1. Support users to add frequently used gateways or focus gateways to their favorites(Right-click the gateway to operate), Optimize management. | ||
| 95 | 1. When the user binds the gateway, he can configure the custom gateway parameter information corresponding to the gateway. After binding, he can also modify the gateway parameter information by editing the gateway parameter information. The gateway parameter field is provided by the parent account and used by the end user. After the gateway parameter field information is sent to the gateway through the gateway project configuration, it is the gateway through the relevant interface function when executing the script, such asbns_get_config('bind)Retrieve and use in the script. | ||
| 96 | 1. Support users to drag and drop sorting in front of the gateway on this page. | ||
| 97 | 1. Users can operate the gateway to restart, unbind and other operations(Right-click the gateway to operate). | ||
| 98 | 1. The user can operate the gateway to close V-NET(Right-click the gateway to operate),shut down V-NET The gateway will disconnect all external network connections. | ||
| 99 | 1. The user can issue the gateway project configuration to the online and normally operating gateway. After the configuration is issued, the original operating configuration of the gateway will be overwritten. Whether the configuration is successfully issued can be checked through the feedback information function button. | ||
| 100 | 1. The user can issue the networking configuration to the online and normally operating gateway. After the networking configuration is issued to the corresponding model gateway, the gateway will cover the original device networking mode. Whether the configuration has been successfully issued can be checked through the feedback information function button. | ||
| 101 | 1. For gateways with lower firmware versions, they can also be upgraded through the platform. | ||
| 102 | 1. If you need to view the running information of the gateway script, you can use the debugging function button to debug, view the script running log information, and cooperate with the feedback information button to check whether the script is running normally. | ||
| 103 | |||
| 104 | (% style="text-align:center" %) | ||
| 105 | [[image:Terminal operation help document_html_bf0a5d7f7934d527.png||height="402" width="800" class="img-thumbnail"]] | ||
| 106 | |||
| 107 | (% style="text-align:center" %) | ||
| 108 | [[image:Terminal operation help document_html_7486c719d3639d14.png||height="370" width="800" class="img-thumbnail"]] | ||
| 109 | |||
| 110 | (% style="text-align:center" %) | ||
| 111 | [[image:Terminal operation help document_html_97812056d6e20106.png||height="414" width="800" class="img-thumbnail"]] | ||
| 112 | |||
| 113 | (% style="text-align:center" %) | ||
| 114 | [[image:Terminal operation help document_html_9694afc7943dd34.png||height="370" width="800" class="img-thumbnail"]] | ||
| 115 | |||
| 116 | (% style="text-align:center" %) | ||
| 117 | [[image:Terminal operation help document_html_7845fb7ec2c6a2da.png||height="367" width="800" class="img-thumbnail"]] | ||
| 118 | |||
| 119 | (% style="text-align:center" %) | ||
| 120 | [[image:Terminal operation help document_html_406f732c70d74bd7.png||height="342" width="800" class="img-thumbnail"]] | ||
| 121 | |||
| 122 | == Gateway project configuration page == | ||
| 123 | |||
| 124 | The gateway project configuration is the configuration information issued to the gateway to run. | ||
| 125 | |||
| 126 | Gateway project configurations of different gateway models can be created, but all must be associated with the access configuration assigned to the cloud provider account (parent account). | ||
| 127 | |||
| 128 | The gateway project configuration can be created by one-click on the distribution project assigned by the parent account (cloud business account) (the communication port, collection point, script and other information in the distribution project will be copied). | ||
| 129 | |||
| 130 | * You can use the vwmt compressed package to import the configuration, but the imported configuration must also be associated with the access configuration assigned to the cloud provider account (parent account). | ||
| 131 | * For the gateway engineering configuration between different models, the system will filter the configuration information that does not meet the requirements. | ||
| 132 | * Such as:Import a V-BOX S-4G gateway engineering configuration compressed package into the configuration of the V-BOX S-00 model, and the system will directly filter the communication port and the relevant data under the communication port that do not conform to the V-BOX S-00 model . | ||
| 133 | |||
| 134 | Gateway project configuration details page (Five modules: communication port configuration, collection point configuration, MQTT configuration, script configuration, custom information, four function points: send to gateway, export configuration, import Excel, export Excel) | ||
| 135 | |||
| 136 | * Communication port configuration: Configurable gateway serial port connection type, please refer to the related operations of VNET communication port for details. | ||
| 137 | * Collection point configuration: refer to related operations of VNET monitoring points | ||
| 138 | ** Users can add collection point groups of different trigger types. Collection points can be added to the group. The upper limit of the number of collection points that can be added is controlled by the model of the current gateway project configuration (for example: the current gateway project configuration model is V-BOX S-4G, the current account number The parent account of is set the number of trigger type collection points added for this model, and the collection points within this model added by the end user will be restricted). | ||
| 139 | ** The upper limit of the number of collection points that can be added in a group under each trigger type refers to the total number of collection points that can be added under all groups of the trigger type. | ||
| 140 | ** When adding a collection point, you can define custom information for the collection point. The custom information is provided by the parent account of the current account (cloud business account) and used by the end user. | ||
| 141 | ** After the gateway project configuration collection point custom information is sent to the gateway through the gateway project configuration, the gateway uses related interface functions such as bns_get_config('user') to retrieve and use when executing the script. | ||
| 142 | |||
| 143 | MQTT configuration: | ||
| 144 | |||
| 145 | * Configure the path and parameters of the gateway to access the MQTT server, use the related interface function MQTT.setup_cfg() in the "Hui Box Interface Document" in the script configuration module script to obtain and use MQTT information (see "Hui Box Interface Document" for details 》-MQTT operating instructions). | ||
| 146 | * If the parent account (cloud merchant account) of the current end-user has closed related permissions, the current user will not be able to see the MQTT module and set the MQTT information. And when the gateway project configuration is delivered to the gateway, the gateway will only use the MQTT information in the access configuration associated with the current gateway project configuration by default. After the parent account has enabled relevant permissions, the current user can configure MQTT information, and when the gateway project configuration is sent to the gateway, the gateway will use the MQTT configuration in the gateway project configuration instead of using the current gateway project configuration to associate access to the MQTT information in the configuration . | ||
| 147 | |||
| 148 | Script configuration: | ||
| 149 | |||
| 150 | * Configure the gateway to run the script. | ||
| 151 | * If the parent account of the current end-user (cloud business account) has closed related permissions, the current user will not be able to see the script module and set the script. And when the gateway project configuration is delivered to the gateway, the gateway will only use the script in the access configuration associated with the current gateway project configuration by default. The current user can configure the script after the parent account has enabled the relevant permissions. After the gateway project configuration is sent to the gateway, the gateway will use the script in the gateway project configuration to associate with the current gateway project configuration to access the script in the configuration | ||
| 152 | |||
| 153 | Custom information: | ||
| 154 | |||
| 155 | * Customized information can be set for the current gateway project configuration. The customized information is provided by the parent account (cloud merchant account) of the current account, and the end-user edits the field content information. | ||
| 156 | * After the gateway project configuration custom information is sent to the gateway through the gateway project configuration, it is called and used by the gateway through related interface functions such as bns_get_config('user') when executing the script. | ||
| 157 | |||
| 158 | Delivered to the gateway: | ||
| 159 | |||
| 160 | * The user can open the gateway pop-up interface, the system will automatically filter out the gateways that match the current configuration model, and are online and operating normally. The user can directly issue the configuration by selecting the gateway. | ||
| 161 | |||
| 162 | Export configuration: | ||
| 163 | |||
| 164 | * Click the export configuration function button, the user will export a vwmt compressed package, which covers all the information in the gateway project configuration (such as: communication port, free label, collection point grouping, collection point related information, MQTT configuration information, script). | ||
| 165 | * The exported vwmt compressed package can be imported as a new configuration on the platform gateway project configuration page. | ||
| 166 | * Or use the maintenance control configuration tool to directly issue to the gateway, covering the original operating information of the gateway. | ||
| 167 | * When the export configuration is imported as the import configuration, the model type selected for import is inconsistent with the export model, the system will automatically pass the relevant data that does not meet the requirements (such as: export as the configuration of V-BOX S-4G, but used to import the cloud When the platform is a new configuration, the V-BOX E-4G model is selected, and the system will automatically filter out other information such as communication ports that do not meet the requirements). | ||
| 168 | |||
| 169 | Import Excel | ||
| 170 | |||
| 171 | * Support users to import related data into the gateway project configuration through Excel tables, custom editing of communication ports, collection points, free labels, etc. | ||
| 172 | * After the import is successful, the original communication port, free label, collection point grouping, and collection point data in the configuration will be deleted. | ||
| 173 | * Excel table supports the independent import of unrelated table cells, or import all relevant information. | ||
| 174 | * Please check the Excel template for import content related information (click the Excel template function button to export the relevant template). | ||
| 175 | |||
| 176 | **For example:** | ||
| 177 | |||
| 178 | * The user needs to import the communication port and the free label under the communication port, and only the communication port table unit and the free label table unit need to exist in the Excel table. | ||
| 179 | * The user needs to import the collection point grouping associated with the internal address, and the Excel table only needs to have the collection point grouping table unit. | ||
| 180 | * If the user needs to import collection points, there must be collection point grouping, and the Excel table must have collection point grouping and collection point table units. | ||
| 181 | * If the user needs to import the collection point, and the collection point needs to have related information in the communication port and free label, then the communication port, free label, collection point grouping and collection belt and table unit must be imported. | ||
| 182 | |||
| 183 | Export Excel | ||
| 184 | |||
| 185 | * Support the user to directly export the data in Excel form of the gateway project configuration communication port, free label, collection point grouping and collection point. | ||
| 186 | |||
| 187 | (% style="text-align:center" %) | ||
| 188 | [[image:Terminal operation help document_html_7147bbb183e1abd3.png||height="415" width="800" class="img-thumbnail"]] | ||
| 189 | |||
| 190 | (% style="text-align:center" %) | ||
| 191 | [[image:Terminal operation help document_html_3b5500ba8626d084.png||height="438" width="800" class="img-thumbnail"]] | ||
| 192 | |||
| 193 | (% style="text-align:center" %) | ||
| 194 | [[image:Terminal operation help document_html_95fa50b87cc3507f.png||height="486" width="800" class="img-thumbnail"]] | ||
| 195 | |||
| 196 | (% style="text-align:center" %) | ||
| 197 | [[image:Terminal operation help document_html_32347eac3cb33016.png||height="294" width="800" class="img-thumbnail"]] | ||
| 198 | |||
| 199 | (% style="text-align:center" %) | ||
| 200 | [[image:Terminal operation help document_html_77a9d243dcdfef0e.png||height="443" width="800" class="img-thumbnail"]] | ||
| 201 | |||
| 202 | (% style="text-align:center" %) | ||
| 203 | [[image:Terminal operation help document_html_13cbe58d56232cac.png||height="447" width="800" class="img-thumbnail"]] | ||
| 204 | |||
| 205 | (% style="text-align:center" %) | ||
| 206 | [[image:Terminal operation help document_html_2d6b1b94fc002a0.png||height="436" width="800" class="img-thumbnail"]] | ||
| 207 | |||
| 208 | (% style="text-align:center" %) | ||
| 209 | [[image:Terminal operation help document_html_70cea56a8e86e0c7.png||height="437" width="800" class="img-thumbnail"]] | ||
| 210 | |||
| 211 | (% style="text-align:center" %) | ||
| 212 | [[image:Terminal operation help document_html_225f464c86acc8a2.png||height="436" width="800" class="img-thumbnail"]] | ||
| 213 | |||
| 214 | (% style="text-align:center" %) | ||
| 215 | [[image:Terminal operation help document_html_543de719a584102e.png||height="436" width="800" class="img-thumbnail"]] | ||
| 216 | |||
| 217 | == Debug page == | ||
| 218 | |||
| 219 | For the user binding, online, normal operation, script execution, and there is a gateway printing information in the script, after the user opens the debugging, the gateway will report the script printing information, and the user can view the script running status on the platform. | ||
| 220 | |||
| 221 | The debugging function can be used in conjunction with the feedback information button on the gateway management page (for example, after the gateway project configuration is delivered to the gateway, you can view the configuration delivery status and the script running status in the feedback information. If the configuration delivery fails or If the script runs abnormally, the debugging function will not be able to view any feedback information). | ||
| 222 | |||
| 223 | (% style="text-align:center" %) | ||
| 224 | [[image:Terminal operation help document_html_6baba730ca7961c7.png||height="436" width="800" class="img-thumbnail"]] | ||
| 225 | |||
| 226 | (% style="text-align:center" %) | ||
| 227 | [[image:Terminal operation help document_html_61ccb5a04a14a4d0.png||height="436" width="800" class="img-thumbnail"]] | ||
| 228 | |||
| 229 | == Networking configuration page == | ||
| 230 | |||
| 231 | The user can customize, edit and set the networking mode of different gateway models. | ||
| 232 | |||
| 233 | After the user sends the networking configuration to the corresponding model gateway, the gateway will cover the original device networking mode. | ||
| 234 | |||
| 235 | (% style="text-align:center" %) | ||
| 236 | [[image:Terminal operation help document_html_f5293750667826c.png||height="436" width="800" class="img-thumbnail"]] | ||
| 237 | |||
| 238 | (% style="text-align:center" %) | ||
| 239 | [[image:Terminal operation help document_html_7ed43b87f91eb1d7.png||height="436" width="800" class="img-thumbnail"]] | ||
| 240 | |||
| 241 | == End-user account management page == | ||
| 242 | |||
| 243 | The end-user acts as the group administrator to manage the end-users in a certain group under the parent account. | ||
| 244 | |||
| 245 | The rights that can be exercised are: | ||
| 246 | |||
| 247 | * Add, delete and reorganize members. | ||
| 248 | * Enable and disable members. | ||
| 249 | * Check the gateways bound to the members of the group, and debug the gateways or issue configurations to replace the original gateway running configurations. | ||
| 250 | * Check the configuration and configuration details of the gateway project configured by the group members. | ||
| 251 | |||
| 252 | (% style="text-align:center" %) | ||
| 253 | [[image:Terminal operation help document_html_5e4599f49c2a9fd7.png||height="437" width="800" class="img-thumbnail"]] | ||
| 254 | |||
| 255 | (% style="text-align:center" %) | ||
| 256 | [[image:Terminal operation help document_html_9106b788f90538ba.png||height="437" width="800" class="img-thumbnail"]] | ||
| 257 | |||
| 258 | (% style="text-align:center" %) | ||
| 259 | [[image:Terminal operation help document_html_c1fe72e65724108b.png||height="437" width="800" class="img-thumbnail"]] | ||
| 260 | |||
| 261 | (% style="text-align:center" %) | ||
| 262 | [[image:Terminal operation help document_html_459659ed86d00dfd.png||height="437" width="800" class="img-thumbnail"]] | ||
| 263 | |||
| 264 | == Simple description of the script == | ||
| 265 | |||
| 266 | For the basic functions of the script, please refer to the tutorial in the URL | ||
| 267 | |||
| 268 | __[[https:~~/~~/www.runoob.com/lua/lua-tutorial.html>>url:https://www.runoob.com/lua/lua-tutorial.html]]__ | ||
| 269 | |||
| 270 | For the interface functions such as reading and writing of platform data and internal address operations that need to be used in the script, please refer to the description of the interface functions in the "Hui Box Interface Document". | ||
| 271 | |||
| 272 | There must be a main running function in the definition script, the format is: function xxx.main() end, where xxx is the script name. | ||
| 273 | |||
| 274 | When used in the script to obtain platform custom gateway parameters, configure custom parameters, or configure custom parameters for collection points, use the interface function bns_get_config() in the "Smart Box Interface Document". | ||
| 275 | |||
| 276 | Please contact the technical staff for other related operations |