<?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>issues with app timer module</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/47094/issues-with-app-timer-module</link><description>Hi, 
 I am developing firmware for a custom NRF52840 based board. I am using softdevice 6.0.0 with SDK 15.0 and the SES environment. 
 I am trying to use three application timers: 
 1) driving the battery service to update a couple of characteristics</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 09 May 2019 22:28:01 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/47094/issues-with-app-timer-module" /><item><title>RE: issues with app timer module</title><link>https://devzone.nordicsemi.com/thread/186266?ContentTypeID=1</link><pubDate>Thu, 09 May 2019 22:28:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4806796a-efd7-45bf-8548-447cf29f714a</guid><dc:creator>paul</dc:creator><description>&lt;p&gt;Hi Hakon,&lt;/p&gt;
&lt;p&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;One of the issues I have is that I don&amp;#39;t want to use the app scheduler for this.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;My real issue is that:&lt;/p&gt;
&lt;p&gt;1) I can only get the sample timer to run at ms rates if I use the app scheduler&lt;/p&gt;
&lt;p&gt;2) the third timer doesn&amp;#39;t run at all.&lt;/p&gt;
&lt;p&gt;I think that this problem is related to the length of time in the sample handler - ~10-15ms. It is supposed to be called every 20ms and then the third timer every 10ms. The timing budget just doesn&amp;#39;t work (15 + 10 &amp;gt; 20). Using the app scheduler just serialises the calls on a first come first served basis and moves the work out of interrupt time/context.&lt;/p&gt;
&lt;p&gt;In any case I dropped the use of the sample timer and am progressing.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Cheers Paul&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: issues with app timer module</title><link>https://devzone.nordicsemi.com/thread/186083?ContentTypeID=1</link><pubDate>Thu, 09 May 2019 07:19:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9f1be349-d2be-445f-80ec-8b73010ac550</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Just to make sure you are adjusting the correct queue size (not&amp;nbsp;APP_TIMER_CONFIG_OP_QUEUE_SIZE).&lt;/p&gt;
&lt;p&gt;Have you tried upping the scheduler queue size? It&amp;#39;s normally set in main:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;static void scheduler_init(void)
{
    APP_SCHED_INIT(SCHED_MAX_EVENT_DATA_SIZE, SCHED_QUEUE_SIZE);
}&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;/p&gt;
&lt;p&gt;Håkon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>