<?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>app timer issue</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/34376/app-timer-issue</link><description>Hi, 
 device : nrf52832 
 SDK : 12.3.0 
 base code : ble_app_uart 
 There is a problem using the app timer. 
 I created an app timer like an attachment(excel file). 
 Then start app timer every time data is received (0xDD) from phone to BLE. 
 Normally</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 15 May 2018 12:47:50 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/34376/app-timer-issue" /><item><title>RE: app timer issue</title><link>https://devzone.nordicsemi.com/thread/132042?ContentTypeID=1</link><pubDate>Tue, 15 May 2018 12:47:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0200c295-33ef-4c88-98f4-cde13a1305ac</guid><dc:creator>AmbystomaLabs</dc:creator><description>&lt;p&gt;That is normal for any interrupt driven, low priority routine.&amp;nbsp; The softdevice always has the highest priority interrupt and takes precedence low priority interrupts. When you combine this with the random backoff in the BLE standard, low priority interrupts will always have a random latency of up to about a millisecond.&amp;nbsp; Sending a lot of data only exacerbates the problem as your low priority interrupt will be more likely to get queued.&lt;/p&gt;
&lt;p&gt;For these reasons, anything requiring precise timing should always be driven off of either the RTC or main HF timers and not in ISR&amp;#39;s.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>