Closed hchaudhary1 closed 5 years ago
Error code 0x4008 corresponds to a parameter error. From this point of view, it has little relationship with memory. Have you ever had this problem when there are few devices? Is there a perfect log?
If you are developing based on esp-mdf.
esp_bt_mem_release(ESP_BT_MODE_CLASSIC_BT);
in app_main to release classic Bluetooth.#
# Bluetooth
#
CONFIG_BT_ENABLED=y
CONFIG_GATTC_ENABLE=
CONFIG_BLE_SMP_ENABLE=
CONFIG_BT_ACL_CONNECTIONS=2
CONFIG_BLE_SCAN_DUPLICATE=
CONFIG_BT_BLE_DYNAMIC_ENV_MEMORY=y
CONFIG_BTDM_CONTROLLER_MODEM_SLEEP=
CONFIG_BT_STACK_NO_LOG=
Hi zhanzhaocheng,
yes, with 10 devices, everything is working perfect, no errors. I did also see the esp_mesh.h, but all my parameters were perfect.
mwifi_xxx is a good idea! I will try that
using the mwifi_xxx worked. thanks
Hi hchaundhary1,
I'm also trying to transmit data from multiple nodes to the root at once. I'm still new to this esp mesh concept. Can you please kindly explain to me how you did it.
@thilakshiK You can modify it based on the mwifi example or get-started
I am running the 1.0 beta. I have a fixed root mesh with 75 nodes. All the devices are within 200 feet, in my test room. Most of the nodes are unable to TX to root at all, and give the following error, when attempting to send to root 0x4008.
I am only sending 40bytes, every 30 seconds, from all nodes. See attached pic of the logs, as seen by the ESPNOW sniffer.
I am running -BLE server -ESPNOW, mdebug -ESP MESH
Settings for mesh are default, but with the following overrides:
The issue is extremely bad, when you turn on verbose logging for mesh and idf. I have ~30k of free heap, so I am not sure what the issue is, but definitely an issue with the espressif software MDF or IDF.