alex/esp-idf
alex/esp-idf
1
0
Fork 0
mirror of https://github.com/espressif/esp-idf.git synced 2024-10-05 20:47:46 -04:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity
31d87a0c59
esp-idf/examples/bluetooth/esp_ble_mesh/ble_mesh_wifi_coexist
History
wangjialiang db23ef400c feat(ble_mesh: example: esp32c6/h2): update config file to support duplicate scan.
2023-07-21 02:02:21 +00:00
..
main ble_mesh: example: remove unnecessary macro of esp32h2 for ble_mesh_wifi_coexist 2023-03-21 09:21:06 +00:00
tutorial example: use console repl in ble mesh coex example 2022-05-19 11:31:53 +08:00
CMakeLists.txt tools: Increase the minimal supported CMake version to 3.16 2022-06-01 06:35:02 +00:00
partitions.csv Whitespace: Automated whitespace fixes (large commit) 2020-11-11 07:36:35 +00:00
README_CN.md Modify the readme files in example/bluetooth 2023-01-13 15:05:34 +08:00
README.md Modify the readme files in example/bluetooth 2023-01-13 15:05:34 +08:00
sdkconfig.ci.bluedroid component/bt: add BLE v5.0 feature for bluedroid host 2021-01-15 17:55:12 +08:00
sdkconfig.ci.bluedroid_deinit component/bt: add BLE v5.0 feature for bluedroid host 2021-01-15 17:55:12 +08:00
sdkconfig.ci.model component/bt: add BLE v5.0 feature for bluedroid host 2021-01-15 17:55:12 +08:00
sdkconfig.ci.nimble component/bt: add BLE v5.0 feature for bluedroid host 2021-01-15 17:55:12 +08:00
sdkconfig.ci.nimble_deinit component/bt: add BLE v5.0 feature for bluedroid host 2021-01-15 17:55:12 +08:00
sdkconfig.defaults TWDT: Use the new TWDT Kconfig options in the examples and tests 2023-02-17 11:22:25 +08:00
sdkconfig.defaults.esp32c3 TWDT: Use the new TWDT Kconfig options in the examples and tests 2023-02-17 11:22:25 +08:00
sdkconfig.defaults.esp32c6 feat(ble_mesh: example: esp32c6/h2): update config file to support duplicate scan. 2023-07-21 02:02:21 +00:00
sdkconfig.defaults.esp32s3 TWDT: Use the new TWDT Kconfig options in the examples and tests 2023-02-17 11:22:25 +08:00

README.md

Supported Targets ESP32 ESP32-C3 ESP32-C6 ESP32-S3

ESP-BLE-MESH and Wi-Fi Coexistence Example

This example is used to measure the maximum throughput value that Wi-Fi can achieve when ESP-BLE-MESH is provisioning, sending and receiving messages. Users can implement their own application scenarios based on the throughput value in this example. If users are not familiar with how to use ESP-BLE-MESH, please refer to ESP-BLE-MESH Node Example.

This example is divided into two main parts:

  • Wi-Fi Iperf protocol
  • ESP-BLE-MESH Fast Provisioning Server

For information on how to use the Iperf protocol for Wi-Fi, please refer to Wi-Fi Iperf README

When Wi-Fi Iperf is enabled, ESP-BLE-MESH can use fast provision for device provisioning. The node in this example contains one element that supports the following models:

  • Configuration Server model: This model is mainly for node configuration after the device joins the ESP-BLE-MESH network, such as relay, friend feature, NetKey, etc.
  • Configuration Client model: This model is used to get or set the configuration of other nodes, such as relay, friend feature, adding NetKey, etc.
  • Generic On/Off Server model: This model is mainly used to indicate the value of node's On/Off state, and different state values ​​determine the different states of the device (such as light on and off).
  • Generic On/Off Client model: This model controls the on/off of the device by setting the On/Off state of other nodes.
  • Fast Provision Server model: This model is a vendor server model implemented for fast provisioning. When the device is configured to join the network, it will temporarily act as a Provisioner for other devices; when the provisioning is completed, it will resume the node role and pass the addresses assigned to all nodes to the Fast Provision Client model through this model.
  • Fast Provision Client model: This model needs to be used together with the Fast Provision Server model to get all addresses assigned to the nodes by the Fast Provisioning Server.