RE: Openthread message queue problem on router

Wojtek — Mon, 16 Oct 2017 06:10:47 GMT

Hi! Thanks for your answer. When device is in DETACHED state I assume that it is disconnected from the rest of mesh including border router. Am i wrong? I will try to add some delay in send function to be sure that routes are built correctly.

Best regards, Wojciech Rzepecki

RE: Openthread message queue problem on router

Lukasz Duda — Thu, 12 Oct 2017 08:36:53 GMT

Hello Wojciech!

Unfortunatelly I don't have enough information to solve the problem.

However i have some suspicious. When device operates as an end-device, it is enough for it to attach to the network in order to start sending data (since it always sends data via the parent).

Router however participants in mesh forwarding, it has to gather knowledge about current topology in order to route packets. If you try to send all message from your application queue right after its state is changed, then probably packets will be dropped on mesh_forwarder layer. The whole process of route discovery should be very fast, but it is not instant.

Do I correctly assume that you stop Thread (by otThreadSetEnabled function) on router and reenable it some time after - this is why you expirience DETACHED state on router? If this is the case, do you also call this function when you want to sleep as sleepy end device (this is not needed)?

What you can do is to build OpenThread libraries with logs enabled. You need to change the log level here: github.com/.../openthread-core-default-config.h to OT_LOG_LEVEL_DEBG. After that, you can observe all logs on RTT.