<?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>BLE Frequency drift failure effect</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/13138/ble-frequency-drift-failure-effect</link><description>If a BLE device using nRF51822 has a freuqency drift around 80kHz (BLE limit is 50kHz). All other measurement item like ICFT can pass the BLE spec. Will the performance of the device be degraded significantly? Is it reasonsable to still launch this device</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 12 Apr 2016 12:25:16 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/13138/ble-frequency-drift-failure-effect" /><item><title>RE: BLE Frequency drift failure effect</title><link>https://devzone.nordicsemi.com/thread/50077?ContentTypeID=1</link><pubDate>Tue, 12 Apr 2016 12:25:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a0969163-822b-40b3-8fe8-f2cd002146b3</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;If the device is a Bluetooth product, i.e. using the Bluetooth Logo and marketing your device as a Bluetooth device, then &lt;strong&gt;no&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Quoting the Bluetooth SIG&amp;#39;s  &lt;a href="https://www.bluetooth.com/marketing-branding/brand-best-practices-guidelines"&gt;General Brand Guidelines&lt;/a&gt;:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;All your products must be properly
qualified and comply with the
Bluetooth license agreements&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;-Bjørn&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>