<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>nRF52833 and Openthred timer callback and update issue</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/78629/nrf52833-and-openthred-timer-callback-and-update-issue</link><description>Using windows 10 OS, and SES v5.40. 
 I am using nRF52833 device in my project along with nRF5_SDK_for_Thread_and Zigbee_v4.1.0_32ce5f8 SDK. 
 The timer is called for every 60s for customer specific application (the device wakes up every 60s and updates</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 23 Aug 2021 11:25:16 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/78629/nrf52833-and-openthred-timer-callback-and-update-issue" /><item><title>RE: nRF52833 and Openthred timer callback and update issue</title><link>https://devzone.nordicsemi.com/thread/326161?ContentTypeID=1</link><pubDate>Mon, 23 Aug 2021 11:25:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2001b64d-2e42-48d3-bf1f-69d8c75c111d</guid><dc:creator>Abhijith.Desai</dc:creator><description>&lt;p&gt;We are using thread protocol for communication and polling for around 100 -500ms helps to solve this issue.&lt;/p&gt;
&lt;p&gt;But the case is we are trying to build a product that goes to sleep once it is done with its tasks to save power consumption and if we poll for that duration i guess radio will be awake always.&lt;/p&gt;
&lt;p&gt;the solution for this worked is to use some notify function in OT platform so that it only wakes up whenever there is a change that is observed and goes back to sleep.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52833 and Openthred timer callback and update issue</title><link>https://devzone.nordicsemi.com/thread/325163?ContentTypeID=1</link><pubDate>Mon, 16 Aug 2021 14:46:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8a30a68d-0de6-40c9-bd08-eb6d51cc874a</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;After discussing internally:&lt;/p&gt;
&lt;p&gt;You don&amp;#39;t&amp;nbsp;mention about the communication protocol the application is using, but we imagine there is some bidirectional traffic involved. With a poll period of 30 s it might happen that the complete application transaction takes that amount of time. The solution could be that the application reduces the poll period whenever it has data to deliver to something like 100-500 ms, and then go back to the energy saving mode of 30 s.&lt;/p&gt;
&lt;p&gt;Hope that helps,&lt;br /&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>