Open andy-danieal opened 5 months ago
@andy-danieal
ESP_ERROR_CHECK(esp_mesh_enable_ps()); ESP_ERROR_CHECK(esp_mesh_set_ap_assoc_expire(120)); ESP_ERROR_CHECK(esp_mesh_set_beacon_interval(10000)); ESP_ERROR_CHECK(esp_mesh_set_passive_scan_time(1000)); ESP_ERROR_CHECK(esp_mesh_set_active_duty_cycle(12, MESH_PS_DEVICE_DUTY_REQUEST)); ESP_ERROR_CHECK(esp_mesh_set_network_duty_cycle(12, -1, MESH_PS_NETWORK_DUTY_APPLIED_ENTIRE));
Are these configurations for all devices? Which IDF branch do you use? Can you describe the structure of your mesh network? Which layer or device does the above log belong to? Do you mean the device can't connect to the mesh network due to the above logs? Can you provide the complete logs?
Yes, I had set configuration for all devices.
ESP-IDF v5.2.1-533-g9f4f8e24f2
Fixed root without router and MESH_TOPO_TREE topology. and issue on 1 layer of device.
Yes, not connected to mesh network. Other-side Fixed range without sleep mode device was connected to MESH network. but when range was decrease then device was connected to mesh network.
Sleep Mode mesh network devices. Why do the Wi-Fi logs contain these warnings
W (12735350) wifi:The previous beacon was not Tx done
and
W (12824436) wifi:(->sleep)busy, waked:1, dream:0, sleep:0
@andy-danieal
W (12824436) wifi:(->sleep)busy, waked:1, dream:0, sleep:0
this log indicates that there is packet in the TX queue, and W (12735350) wifi:The previous beacon was not Tx done
this log indicates that the last beacon hasn't been sent out. It seems the beacon sending is affected.
and issue on 1 layer of device
Do you mean the issue is on root device? Can you capture the packets of the device? Can you provide a demo to test?
Thanks for your response.
Do you mean the issue is on root device?
Can you capture the packets of the device? Can you provide a demo to test?
I'm using ESP-WiFi-Mesh with fixed range of devices. I've added only one time configuration. Please help me get this working with low power. because We have been experiencing heating issues. Some devices have hung, and the watchdog timer is not working. The only indication is a WiFi log.
how to capture packets of devices
you can use Wireshark to capture packets.
I will try to reproduce this problem locally.
@andy-danieal
How about you call esp_mesh_set_network_duty_cycle()
only on the fixed-root node?
https://github.com/espressif/esp-idf/blob/e7070e777a079695f69720ffb3c631c5fe620cc6/components/esp_wifi/include/esp_mesh.h#L1638
@zhangyanjiaoesp
ROOT Settings
ESP_ERROR_CHECK(esp_mesh_set_type(MESH_ROOT));
esp_mesh_set_self_organized(false, false);
ESP_ERROR_CHECK(esp_mesh_set_vote_percentage(1));
ESP_ERROR_CHECK(esp_mesh_set_xon_qsize(256));
ESP_ERROR_CHECK(esp_mesh_enable_ps());
ESP_ERROR_CHECK(esp_mesh_set_ap_assoc_expire(60));
ESP_ERROR_CHECK(esp_mesh_allow_root_conflicts(false));
ESP_ERROR_CHECK(esp_mesh_send_block_time(2000));
/*---------Mesh Config NOT SHARED ----*/
ESP_ERROR_CHECK(esp_mesh_start());
ESP_ERROR_CHECK(esp_mesh_set_active_duty_cycle(50, MESH_PS_DEVICE_DUTY_DEMAND));
ESP_ERROR_CHECK(esp_mesh_set_network_duty_cycle(50, -1, MESH_PS_NETWORK_DUTY_APPLIED_ENTIRE));
Child Setting
ESP_ERROR_CHECK(esp_mesh_set_type(MESH_IDLE));
esp_mesh_fix_root(true);
esp_mesh_set_self_organized(true, true);
ESP_ERROR_CHECK(esp_mesh_set_xon_qsize(128));
ESP_ERROR_CHECK(esp_mesh_enable_ps());
ESP_ERROR_CHECK(esp_mesh_set_ap_assoc_expire(60));
ESP_ERROR_CHECK(esp_mesh_set_beacon_interval(1000));
ESP_ERROR_CHECK(esp_mesh_set_passive_scan_time(500));
ESP_ERROR_CHECK(esp_mesh_send_block_time(2000));
ESP_ERROR_CHECK(esp_mesh_start());
ESP_ERROR_CHECK(esp_mesh_set_active_duty_cycle(50, MESH_PS_DEVICE_DUTY_REQUEST));
ESP_ERROR_CHECK(esp_mesh_set_network_duty_cycle(50, -1, MESH_PS_NETWORK_DUTY_APPLIED_ENTIRE));
@andy-danieal I use two devices, one is fixded root, and one is node, the configuration is same as above, but I didn't reproduce the problem, do I need more devices?
@andy-danieal Now I can reproduce this problem.
@andy-danieal I use two devices, one is fixded root, and one is node, the configuration is same as above, but I didn't reproduce the problem, do I need more devices?
The issue is related to a range test failed, not to a mesh connection.
When i added sleep mesh device functionality then issue has comes to same range device was not connecting to parent and delay on command.
Testing step:-
Answers checklist.
General issue report
Devices are working in a mesh network, but When i added sleep mesh device functionality then issue has comes to same range device was not connecting to parent and delay on command.
Logs:-