-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem with attaching devices #343
Comments
From the logs, it appears that there are many transmission failures with no-ack errors. This could be due to poor RF connectivity between the devices. Which nRF52840 devices are you using? What is the received signal strength being reported for received messages in the OpenThread logs on the RPi? |
Thanks for such fast answer! |
@BAzili073 , do you have any nRF52840-DK or USB dongles to test with? It would be interesting to see if you can replicate the issue with Nordic dev boards. |
Yeah, we will try to reproduce it on nRF52840-DK |
Closing stale issue. |
Hello.
We use nRF52840 as devices. And use a RPi as a border router.
We had a problem of joining attaching devices to the network.
Device may attach and may not depending on which device's Parent Response it will receive last: if it's ot-br on RPi it attaches fine, if it's another device then child ID response from it never arrives so attach timeouts.
During the debug, we found out that disabling OPENTHREAD_CONFIG_DROP_MESSAGE_ON_FRAGMENT_TX_FAILURE for the device that sends Child ID response helped to attaching device finally receive Id responce and enter the network
What is the the root of a problem and is this the correct solution?
dev1_fail_to_dev2_succ_to_Rpi.log
dev1_succ_to_dev.log
dev1_fail.log
dev2_succ.log
dev2_fail.log
The text was updated successfully, but these errors were encountered: