mirror of
https://github.com/espressif/esp-idf.git
synced 2025-08-08 04:02:27 +00:00
doc: Fix some ble mesh description
This commit is contained in:
@@ -261,7 +261,7 @@ Specific files that provide implementation of provisioning of Node are shown in
|
||||
- Functionality
|
||||
* - :component_file:`prov.c <bt/esp_ble_mesh/mesh_core/prov.c>`
|
||||
- ESP-BLE-MESH Node provisioning (PB-ADV & PB-GATT)
|
||||
* - :component_file:`proxy_client.c <bt/esp_ble_mesh/mesh_core/proxy_client.c>`
|
||||
* - :component_file:`proxy_server.c <bt/esp_ble_mesh/mesh_core/proxy_server.c>`
|
||||
- ESP-BLE-MESH Proxy Server related functionalities
|
||||
* - :component_file:`beacon.c <bt/esp_ble_mesh/mesh_core/beacon.c>`
|
||||
- APIs used to handle ESP-BLE-MESH Beacons
|
||||
@@ -276,7 +276,7 @@ Specific files that implement functions of Provisioner are shown in Table 2.3:
|
||||
- Functionality
|
||||
* - :component_file:`provisioner_prov.c <bt/esp_ble_mesh/mesh_core/provisioner_prov.c>`
|
||||
- ESP-BLE-MESH Provisioner provisioning (PB-ADV & PB-GATT)
|
||||
* - :component_file:`proxy_server.c <bt/esp_ble_mesh/mesh_core/proxy_server.c>`
|
||||
* - :component_file:`proxy_client.c <bt/esp_ble_mesh/mesh_core/proxy_client.c>`
|
||||
- ESP-BLE-MESH Proxy Client related functionalities
|
||||
* - :component_file:`provisioner_main.c <bt/esp_ble_mesh/mesh_core/provisioner_main.c>`
|
||||
- ESP-BLE-MESH Provisioner networking related functionalities
|
||||
@@ -385,11 +385,11 @@ When adopting the design of independent module, the two main factors should be c
|
||||
- ESP-BLE-MESH Friend functionality
|
||||
* - :component_file:`net.c <bt/esp_ble_mesh/mesh_core/net.c>`
|
||||
- ESP-BLE-MESH Relay feature, network creation, IV Update procedure, IV Index recovery procedure, Key Refresh procedure related functionalities
|
||||
* - :component_file:`proxy_client.c <bt/esp_ble_mesh/mesh_core/proxy_client.c>`
|
||||
- ESP-BLE-MESH Proxy Server related functionalities
|
||||
* - :component_file:`proxy_server.c <bt/esp_ble_mesh/mesh_core/proxy_server.c>`
|
||||
- ESP-BLE-MESH Proxy Server related functionalities
|
||||
* - :component_file:`proxy_client.c <bt/esp_ble_mesh/mesh_core/proxy_client.c>`
|
||||
- ESP-BLE-MESH Proxy Client related functionalities
|
||||
* - :component_file:`settings.c <bt/esp_ble_mesh/mesh_core/settings.c>`
|
||||
- ESP-BLE-MESH Node NVS storage functionality
|
||||
- ESP-BLE-MESH NVS storage functionality
|
||||
* - :component_file:`main.c <bt/esp_ble_mesh/mesh_core/main.c>`
|
||||
- ESP-BLE-MESH node removal related functionality
|
||||
- ESP-BLE-MESH stack initialize, stack enable, node removal related functionalities
|
||||
|
@@ -548,7 +548,7 @@ Generally, a Provisioner is used to provision unprovisioned devices and form a m
|
||||
|
||||
Normally when they are several unprovisioned devices, users can provision them one by one. But when it comes to a large number of unprovisioned devices (e.g. 100), provisioning them one by one will take huge amount of time. With fast provisioning, users can provision 100 unprovisioned devices in about 50 seconds.
|
||||
|
||||
4.2 Why EspBleMesh App would wait for a long time or keep waiting during fast provisioning?
|
||||
4.2 Why EspBleMesh App would wait for a long time during fast provisioning?
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
After the App provisioned one Proxy node, it will disconnect from the App during fast provisioning, and reconnect with the App when all the nodes are provisioned.
|
||||
|
Reference in New Issue
Block a user