nRF thread server stops receiving packets in LEADER role

[Rajendra]

Hello,

I am working on Thread client server based network. I am using nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8. My development hardware is nRF52840-DK, HW Version 2.0.1. I am using softdevice - s140_nrf52_7.0.1

I have placed few thread sensors around the thread server. Most of the time data sent from thread sensors is received by thread server, thread server also sends ack to thread sensor. But when thread server goes into LEADER role and stays in LEADER role for long time, it stops receiving data from sensor. When thread server is in other role - CHILD or ROUTER, it receives data. I tried to restart server when it is in LEADER role for long time, even after restart it immediately goes into LEADER role and stops receiving data. Any reason for this?

I have 8 thread sensors sending data at 30 sec frequency and receiving ack, is this data rate a reason?

Any help would be appreciated.

Thanks in Advance,
Rajendra

[Edvin]

I have 8 thread sensors sending data at 30 sec frequency and receiving ack, is this data rate a reason?

It doesn't sound like the amount of throughput should be an issue in this case.

When the device is a leader, are you sure that it is not disconnected (out of reach) of the rest of the network? That could be one reason that it becomes a leader. That it doesn't see any other nodes, and hence creates a new network.

Can you try to add a new node to your network running the NCS\nrf\samples\openthread\cli sample, and you can use the cli command:

ot router table

To print a table of all the routers. If the device is a child, you can use the table ot child table

What happens when the device becomes the leader, and then you run these CLI commands. Is the device still part of the network? Or does it disappear from the tables?

Best regards,

Edvin