https://devzone.nordicsemi.com/f/nordic-q-a/30479/sleepy-node---data-transmission-time-over-threadHello there, I have developed a board with nRF52840 and a sensor. My hardware and tools setup is: SDK: nRF5_SDK_for_Thread_v0.10.0_e1c3d11 Thread version:OPENTHREAD/g6a15261b-dirty THREAD Border Router = nRF52840 dev kit . Firmware is based onen-USTelligent Community 13Fri, 16 Feb 2018 10:58:46 GMThttps://devzone.nordicsemi.com/thread/121066?ContentTypeID=1Fri, 16 Feb 2018 10:58:46 GMT137ad170-7792-4731-bb38-c0d22fbe4515:85983348-02a1-4eb9-9e61-800e09e6e062Rajendra<p>Thank you Kamil for answer, it would really help.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/120979?ContentTypeID=1Thu, 15 Feb 2018 12:52:40 GMT137ad170-7792-4731-bb38-c0d22fbe4515:3009d2d6-cef1-44b4-abeb-33f98765d423Kamil Sroka<ol> <li><span>This time will be highly non-deterministic. Simple attachment to Thread network can take from 0,2s to 5s and is affected by&nbsp;air traffic, random jitters, or other non-deterministic factors defined in the Thread protocol. You can find some of those times&nbsp;in table on this page:&nbsp;</span><a href="http://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.threadsdk.v0.11.0%2Fthread_multiprotocol.html">http://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.threadsdk.v0.11.0%2Fthread_multiprotocol.html</a></li> <li>Range is not connected with time needed to send the packet - this looks like a coincidence.</li> <li>Thread SED has its radio powered off most of the time so it is better to call __WFE() and keep everything asynchronous rather then use SYSTEMOFF</li> </ol> <p>Can you share a piece of code to reproduce this?</p><div style="clear:both;"></div>