Thread devices get detached from OTBR when data rate is 10 sample per second

[nikhil1983]

Hello, we have developed a product based on open thread, where we are transmitting data at high data rate i.e around 10 payload per second. And each payload is of around 100 bytes. And my sleepy end device used mqtt-sn at application level, with a poll period set of 20ms. Mqtt-sn gateway and border router is setup on a RPi. Currently for testing purpose OTBR and end devices are kept in line of sight with just 4_5 meter distance between them.

So recently we found out that after a couple of minutes of data transfer at a high data rate (10sample per sec) my thread devices get detached from the network and after 5-8 seconds they again get attached to the thread network and start transmitting data over the mqtt-sn protocol. And this detached attached routine is happening once a minute.

1. I would like to know what could be the possible reasons why my device gets detached too often ?

2. Also does thread network handle 10 samples per second data rate for a longer period of time ? Will it sustain ?

3. And are there any api available which I can use in my firmware to force connect my thread device to a network (when in detached mode) instead of waiting for 4_5 seconds after getting detached ?

[jwhui]

I would like to know what could be the possible reasons why my device gets detached too often ?

There are a number of reasons why your device may be losing connection. To help diagnose the problem, can you provide more information? For example:

1. Logs from OTBR and/or sleepy end device.
2. Packet capture file for viewing in wireshark.
3. Device configuration (hw platforms used for OTBR, RCP, and Thread device)

Also does thread network handle 10 samples per second data rate for a longer period of time ? Will it sustain ?

Thread can support far more than 10 packets per second. But note that the channel capacity is a shared resource. If you have lots of devices transmitting this much data, the channel will saturate.

And are there any api available which I can use in my firmware to force connect my thread device to a network (when in detached mode) instead of waiting for 4_5 seconds after getting detached ?

A device will automatically start the reattach process when it detects that it becomes disconnected from the Thread network. The minimum backoff time for reattaching is already set to ~250ms, which is pretty short already.

[nikhil30081995]

Okay i have changed the macro in the mac.h file, but how to build openthread now ?

Here is the image

[jwhui]

Given that you are using the nRF5 SDK for Thread, I would reach out to Nordic for further guidance.

[nikhil30081995]

The latest on main branch:

openthread/src/core/config/mac.h

Line 73 in bacf8d6

#define OPENTHREAD_CONFIG_MAC_DEFAULT_MAX_FRAME_RETRIES_DIRECT 15

All default config values are maintained here: https://github.com/openthread/openthread/tree/main/src/core/config

Hello, i have build the repo. and replace the build libraries which were used in my nRF5 project reffering following link :
https://infocenter.nordicsemi.com/index.jsp?topic=%2Fsdk_tz_v4.1.0%2Fthread_ot_libraries_building.html

I would like to know, how can i verify if the value has been updated successfully or not ?

[jwhui]

After the SED attaches, you can disable its parent and observe how many retransmissions the SED performs on its data messages.

[nikhil30081995]

96d1dea311f otbr-agent[216]: 00:01:12.373 [I] MeshForwarder-: src:[fd68:4f54:dead:1:52de:cf79:cf91:8abf] Sep 22 08:29:13 096d1dea311f otbr-agent[216]: 00:01:12.373 [I] MeshForwarder-: dst:[ff33:40:fd88:f3df:b78f:478b:0:1] Sep 22 08:29:13 096d1dea311f otbr-agent[216]: 00:01:12.511 [I] Mle-----------: Send Child Update Request to child (fe80:0:0:0:58fc:21e3:10df:82ad,0x3801) Sep 22 08:29:13 096d1dea311f otbr-agent[216]: 00:01:12.511 [I] MeshForwarder-: Prepping indir tx IPv6 UDP msg, len:172, chksum:f7c7, ecn:no, to:0x3801, sec:no, prio:net Sep 22 08:29:13 096d1dea311f otbr-agent[216]: 00:01:12.555 [I] DataPollHandlr: Rx data poll, src:0x3801, qed_msgs:1, rss:-59, ack-fp:1 Sep 22 08:29:13 096d1dea311f otbr-agent[216]: 00:01:12.558 [I] Mac-----------: Frame rx failed, error:Duplicated, len:22, seqnum:204, type:Cmd(DataReq), src:0x3801, dst:0x3800, sec:yes, ackreq:yes Sep 22 08:29:13 096d1dea311f otbr-agent[216]: 00:01:12.568 [I] Mac-----------: Frame tx attempt 1/1 failed, error:NoAck, len:126, seqnum:164, type:Data, src:3ea40ae696963b03, dst:5afc21e310df82ad, sec:yes, ackreq:yes Sep 22 08:29:13 096d1dea311f otbr-agent[216]: 00:01:12.568 [I] DataPollHandlr: Indirect tx to child 3801 failed, attempt 1/4 Sep 22 08:29:14 096d1dea311f otbr-agent[216]: 00:01:12.667 [I] DataPollHandlr: Rx data poll, src:0x3801, qed_msgs:1, rss:-64, ack-fp:1 Sep 22 08:29:14 096d1dea311f otbr-agent[216]: 00:01:12.674 [I] Mac-----------: Frame tx attempt 1/1 failed, error:NoAck, len:126, seqnum:164, type:Data, src:3ea40ae696963b03, dst:5afc21e310df82ad, sec:yes, ackreq:yes Sep 22 08:29:14 096d1dea311f otbr-agent[216]: 00:01:12.674 [I] DataPollHandlr: Indirect tx to child 3801 failed, attempt 2/4 Sep 22 08:29:14 096d1dea311f otbr-agent[216]: 00:01:12.680 [I] Mac-----------: Frame rx failed, error:Duplicated, len:22, seqnum:205, type:Cmd(DataReq), src:0x3801, dst:0x3800, sec:yes, ackreq:yes Sep 22 08:29:14 096d1dea311f otbr-agent[216]: 00:01:12.686 [I] Mac-----------: Frame rx failed, error:Duplicated, len:22, seqnum:205, type:Cmd(DataReq), src:0x3801, dst:0x3800, sec:yes, ackreq:yes Sep 22 08:29:14 096d1dea311f otbr-agent[216]: 00:01:12.777 [I] MeshForwarder-: Received IPv6 HopOpts msg, len:59, chksum:0000, ecn:no, from:0x3801, sec:yes, prio:normal, rss:-64.0 Sep 22 08:29:14 096d1dea311f otbr-agent[216]: 00:01:12.777 [I] MeshForwarder-: src:[fd88:f3df:b78f:478b:2ea4:b9e4:2714:ee] Sep 22 08:29:14 096d1dea311f otbr-agent[216]: 00:01:12.777 [I] MeshForwarder-: dst:[ff03:0:0:0:0:0:0:1] Sep 22 08:29:14 096d1dea311f otbr-agent[216]: 00:01:12.777 [I] Platform------: MulticastRoutingManager: AddMulticastForwardingCache: add dynamic route: Thread fd88:f3df:b78f:478b:2ea4:b9e4:2714:ee => ff03:0:0:0:0:0:0:1 None: OK Sep 22 08:29:14 096d1dea311f otbr-agent[216]: 00:01:12.777 [I] Platform------: MulticastRoutingManager: ProcessMulticastRouterMessages: OK Sep 22 08:29:14 096d1dea311f otbr-agent[216]: 00:01:12.782 [I] Mac-----------: Frame rx failed, error:Duplicated, len:53, seqnum:206, type:Data, src:0x3801, dst:0x3800, sec:yes, ackreq:yes Sep 22 08:29:14 096d1dea311f otbr-agent[216]: 00:01:12.786 [I] Mac-----------: Frame rx failed, error:Duplicated, len:53, seqnum:206, type:Data, src:0x3801, dst:0x3800, sec:yes, ackreq:yes Sep 22 08:29:14 096d1dea311f otbr-agent[216]: 00:01:12.793 [I] MeshForwarder-: Sent IPv6 HopOpts msg, len:59, chksum:0000, ecn:no, to:0xffff, sec:yes, prio:low Sep 22 08:29:14 096d1dea311f otbr-agent[216]: 00:01:12.793 [I] MeshForwarder-: src:[fd68:4f54:dead:1:52de:cf79:cf91:8abf] Sep 22 08:29:14 096d1dea311f otbr-agent[216]: 00:01:12.793 [I] MeshForwarder-: dst:[ff33:40:fd88:f3df:b78f:478b:0:1] Sep 22 08:29:14 096d1dea311f otbr-agent[216]: 00:01:12.796 [I] Mac-----------: Frame rx failed, error:Duplicated, len:53, seqnum:206, type:Data, src:0x3801, dst:0x3800, sec:yes, ackreq:yes Sep 22 08:29:14 096d1dea311f otbr-agent[216]: 00:01:12.813 [I] MeshForwarder-: Sent IPv6 HopOpts msg, len:59, chksum:0000, ecn:no, to:0xffff, sec:yes, prio:low Sep 22 08:29:14 096d1dea311f otbr-agent[216]: 00:01:12.813 [I] MeshForwarder-: src:[fd68:4f54:dead:1:52de:cf79:cf91:8abf] Sep 22 08:29:14 096d1dea311f otbr-agent[216]: 00:01:12.813 [I] MeshForwarder-: dst:[ff33:40:fd88:f3df:b78f:478b:0:1] Sep 22 08:29:14 096d1dea311f otbr-agent[216]: 00:01:12.817 [I] MeshForwarder-: Sent IPv6 HopOpts msg, len:59, chksum:0000, ecn:no, to:0xffff, sec:yes, prio:normal Sep 22 08:29:14 096d1dea311f otbr-agent[216]: 00:01:12.817 [I] MeshForwarder-: src:[fd88:f3df:b78f:478b:2ea4:b9e4:2714:ee] Sep 22 08:29:14 096d1dea311f otbr-agent[216]: 00:01:12.817 [I] MeshForwarder-: dst:[ff03:0:0:0:0:0:0:1] Sep 22 08:29:14 096d1dea311f otbr-agent[216]: 00:01:12.828 [I] MeshForwarder-: Received IPv6 HopOpts msg, len:59, chksum:0000, ecn:no, from:0x5800, sec:yes, prio:normal, rss:-46.0 Sep 22 08:29:14 096d1dea311f otbr-agent[216]: 00:01:12.828 [I] MeshForwarder-: src:[fd88:f3df:b78f:478b:401e:9a87:506e:9392] Sep 22 08:29:14 096d1dea311f otbr-agent[216]: 00:01:12.828 [I] MeshForwarder-: dst:[ff33:40:fdde:ad00:beef:0:0:1] Sep 22 08:29:14 096d1dea311f otbr-agent[216]: 00:01:12.838 [I] MeshForwarder-: Received IPv6 HopOpts msg, len:59, chksum:0000, ecn:no, from:0x5800, sec:yes, prio:normal, rss:-46.0 Sep 22 08:29:14 096d1dea311f otbr-agent[216]: 00:01:12.838 [I] MeshForwarder-: src:[fd88:f3df:b78f:478b:2ea4:b9e4:2714:ee] Sep 22 08:29:14 096d1dea311f otbr-agent[216]: 00:01:12.838 [I] MeshForwarder-: dst:[ff03:0:0:0:0:0:0:1] Sep 22 08:29:14 096d1dea311f otbr-agent[216]: 00:01:12.841 [I] MeshForwarder-: Received IPv6 HopOpts msg, len:59, chksum:0000, ecn:no, from:0xc800, sec:yes, prio:normal, rss:-51.0 Sep 22 08:29:14 096d1dea311f otbr-agent[216]: 00:01:12.841 [I] MeshForwarder-: src:[fd88:f3df:b78f:478b:4b5c:caac:de38:da73] Sep 22 08:29:14 096d1dea311f otbr-agent[216]: 00:01:12.841 [I] MeshForwarder-: dst:[ff33:40:fdde:ad00:beef:0:0:1] Sep 22 08:29:14 096d1dea311f otbr-agent[216]: 00:01:12.845 [I] MeshForwarder-: Sent IPv6 HopOpts msg, len:59, chksum:0000, ecn:no, to:0xffff, sec:yes, prio:normal Sep 22 08:29:14 096d1dea311f otbr-agent[216]: 00:01:12.845 [I] MeshForwarder-: src:[fd88:f3df:b78f:478b:2ea4:b9e4:2714:ee] Sep 22 08:29:14 096d1dea311f otbr-agent[216]: 00:01:12.845 [I] MeshForwarder-

Here are the logs from OTBR.