<?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>Effect on BLE functionality based on LFCLK accuracy</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/6306/effect-on-ble-functionality-based-on-lfclk-accuracy</link><description>Hi , 
 During SOFTDEVICE_HANDLER_INIT function call , if I change the NRF_CLOCK_LFCLKSRC_XTAL_20_PPM macro to NRF_CLOCK_LFCLKSRC_RC_250_PPM_8000MS_CALIBRATION , what is the consequences on BLE functionality . Will it affect complete product feature in</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 31 Mar 2015 19:28:59 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/6306/effect-on-ble-functionality-based-on-lfclk-accuracy" /><item><title>RE: Effect on BLE functionality based on LFCLK accuracy</title><link>https://devzone.nordicsemi.com/thread/22005?ContentTypeID=1</link><pubDate>Tue, 31 Mar 2015 19:28:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6cbbc66f-a6b3-44b2-8d41-c2ebb9c99317</guid><dc:creator>Locky</dc:creator><description>&lt;p&gt;There is no calibration when you specify an external crystal.  It is up to you to specify the accuracy/tolerance of the crystal which should be in the data sheet for the component you designed with.  This is the lowest current consumption setup.  Using the RC setup requires constant calibration and wider RX windows, thus much for current consumption overall.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Effect on BLE functionality based on LFCLK accuracy</title><link>https://devzone.nordicsemi.com/thread/22004?ContentTypeID=1</link><pubDate>Tue, 31 Mar 2015 14:24:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:92c2a472-f9ee-4e01-9d87-04bf8cb70555</guid><dc:creator>Anand Ramashetty</dc:creator><description>&lt;p&gt;Hi osfo ,&lt;/p&gt;
&lt;p&gt;Thanks for the information. Apart from more energy consumption, we can say that it will not affect the  functionality of BLE.&lt;/p&gt;
&lt;p&gt;But what will be the affect of calibration time on functionality. The 250 PPM uses 8000MS , but what is the calibration time for  NRF_CLOCK_LFCLKSRC_XTAL_20_PPM?&lt;/p&gt;
&lt;p&gt;Regards,
Anand&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Effect on BLE functionality based on LFCLK accuracy</title><link>https://devzone.nordicsemi.com/thread/22003?ContentTypeID=1</link><pubDate>Tue, 31 Mar 2015 13:56:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:913a6df7-9860-4711-bf1c-0949148251d8</guid><dc:creator>Asbj&amp;#248;rn</dc:creator><description>&lt;p&gt;The change in LFCLK accuracy will not change the initialization time, but it will make the RX window for your application wider due to less accuracy on the timer. So you will pay with a slightly higher current consumption due to the longer RX window that you have to use in order to ensure that your radio is on for the entire connection event. If you use a 20 ppm 32 kHz crystal, the accuracy is of course better and you can have a shorter RX window and still be within the connection interval.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>