<?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>application timer issue</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/6930/application-timer-issue</link><description>I&amp;#39;m using NRF51822 with soft device version 6.0. 
 I&amp;#39;m trying to create an event which should be triggered every 24 Hours. In the current implementation in our code base, I see that we are already initializing application timer module and then creating</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 11 Apr 2018 11:39:11 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/6930/application-timer-issue" /><item><title>RE: application timer issue</title><link>https://devzone.nordicsemi.com/thread/127817?ContentTypeID=1</link><pubDate>Wed, 11 Apr 2018 11:39:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4e5ccb54-fef4-40ad-a8d2-5ccbca83228f</guid><dc:creator>Timur Beganovic</dc:creator><description>&lt;p&gt;I would like to ask you how you solved the problem of invoking a time out handler inside of another time out handler. I have to respond to a timeout of a Timer_1 while the time out event handler of the Timer_2 is being serviced. Thanks!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: application timer issue</title><link>https://devzone.nordicsemi.com/thread/24444?ContentTypeID=1</link><pubDate>Fri, 10 Jul 2015 10:04:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:95157ddf-48a9-4231-bf6f-45432b40ceb8</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;Thank you for coming back and posting your observations.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: application timer issue</title><link>https://devzone.nordicsemi.com/thread/24443?ContentTypeID=1</link><pubDate>Fri, 10 Jul 2015 09:49:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5fcba2f0-87e4-400f-90e2-98704f5e7b2f</guid><dc:creator>sidekick</dc:creator><description>&lt;p&gt;The issue was not with creating the timer, but rather, was with invoking a callback function inside another callback function that gets triggered when one of the application timer interrupt arrives. And thank you @Aryan for the insight on application timers.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: application timer issue</title><link>https://devzone.nordicsemi.com/thread/24442?ContentTypeID=1</link><pubDate>Thu, 07 May 2015 17:15:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:469af96e-6d1e-4d01-947c-9fecec40ee48</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;Application timers run in APP_LOW priority, so you cannot change this.
If app timer A takes 80msec to finish, then after the return, the the scheduler in the app_timer will find that app timer with 50msec timeout has expired. It will then call app timer B handler. Which in your example means that handler for app timer B will be delayed but not missed.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: application timer issue</title><link>https://devzone.nordicsemi.com/thread/24441?ContentTypeID=1</link><pubDate>Thu, 07 May 2015 15:58:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:69c6ef09-2b34-4cbe-a1f3-a13eb0ec7005</guid><dc:creator>sidekick</dc:creator><description>&lt;p&gt;Thank you for your reply. This issue lead me to find another issue of higher priority and hence I will come back to this timer related issue later. However, I&amp;#39;ve one quick question:
As far as I&amp;#39;ve understood, all the application timers created in this manner(as above), will have same priority level (PRIO_LOW perhaps) and the handlers associated with each of them would &lt;strong&gt;run to completion&lt;/strong&gt;, before scheduler can schedule the other application timer (Though,a higher priority level interrupt can preempt this lower priority application timer interrupt). If this is the case then it seems to be quite possible that if one handler takes more time than the timeout value of the other application timer then we will miss executing the associated timeout handler(e.g. two application timers with &lt;strong&gt;1 sec&lt;/strong&gt; (A) and &lt;strong&gt;50 msec&lt;/strong&gt;(B) timeout and handler for A took 80 msec to finish). Please confirm.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: application timer issue</title><link>https://devzone.nordicsemi.com/thread/24440?ContentTypeID=1</link><pubDate>Thu, 07 May 2015 12:34:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:355b7c97-10eb-44b1-8bc1-8919dfc8f197</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;what is the failure exactly? can you debug to a point it fails and let us know what has failed?
Also can you try to increase APP_TIMER_MAX_TIMERS say 6 and see what happens?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>