Replies: 2 comments
-
I may think this is a problem with the thread device or the stability of the thread network, rather than an issue with OTBR. Is my idea correct? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
OTBR connects five thread sub devices for UDP communication (once a minute), which requires sending data and receiving replies from the thread sub devices. If it fails and tries again 9 times, there will be a low probability of sending failure (NoAck) in our testing
I think this unstable situation is normal, and the thread signal also needs to be interfered by other wireless signals
But the following log is my first time seeing it
So, I have two questions:
May I know what caused this log to appear
Is there a plan to improve NoAck that lasts for one minute
Full log:
1333.log
Beta Was this translation helpful? Give feedback.
All reactions