COAP Thread Server stops receiving messages at a high rate and with multiple sensors

RE: COAP Thread Server stops receiving messages at a high rate and with multiple sensors

haakonsh — Mon, 06 Aug 2018 14:15:17 GMT

Glad to hear. Let us know if you encounter the issue again.

RE: COAP Thread Server stops receiving messages at a high rate and with multiple sensors

Rajendra — Mon, 06 Aug 2018 05:27:31 GMT

I have yet not tried on SDK 1.0 with multiple sensors with high data rate. In SDK 1.0, it works well with a limited number of sensors with a low data rate.

RE: COAP Thread Server stops receiving messages at a high rate and with multiple sensors

haakonsh — Wed, 01 Aug 2018 12:24:08 GMT

Hey Rajendra, do you still experience your issue in SDK 1.0?

RE: COAP Thread Server stops receiving messages at a high rate and with multiple sensors

Rajendra — Tue, 26 Jun 2018 12:01:24 GMT

Thank you Håkon,

Yes RLOC added, and Thread network data changed states needs to be focused on. Is there any state machine/source code which shows the step by step formation of thread network? Which would help to understand these states better.

How can I force the state change, is there any way to do it? As I know these states come as a result of thread network formation.

I will try to use Thread V1.0. In 1.0, I could see there are some major improvements.

Regards,

Rajendra

RE: COAP Thread Server stops receiving messages at a high rate and with multiple sensors

haakonsh — Tue, 26 Jun 2018 08:53:09 GMT

Hey Rajendra,

I'm sorry for the late reply.

The common denominator for these four state changes are Role change, RLOC added, and Thread network data changed. I think it is safe to assume that one or more of these state changes are the culprit.

I suggest you force one of the state changes at a time and see if your problem appears.

I can also suggest that you migrate to nRF5 SDK for Thread and Zigbee v1.0.0.

Cheers,

Håkon.

RE: COAP Thread Server stops receiving messages at a high rate and with multiple sensors

Rajendra — Mon, 04 Jun 2018 11:35:06 GMT

I have found that Thread stops receiving data when its state changes to one of following.

0x2E5, 0x2A5, 0x224, 0x264. i.e. state_changed_callback(uint32_t flags, void * p_context) gives these flags values. I have analyzed these values further.

I am not sure why these states occur and if there are more such problematic states?

Best Regards,

Rajendra

RE: COAP Thread Server stops receiving messages at a high rate and with multiple sensors

Rajendra — Thu, 31 May 2018 04:11:57 GMT

I do not get any error message. The data receive handler stops printing the log. I have mesh topology. Most of the time server is in leader mode and sensors as a child.

RE: COAP Thread Server stops receiving messages at a high rate and with multiple sensors

haakonsh — Wed, 30 May 2018 12:12:58 GMT

Hey Rajendra,

Do you get any error messages?
Can you describe your network topology, devices and their network roles?

Best regards,
Håkon.