<?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 Advertisement Rate &amp;amp; Actual Rate Do Not Match</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/7120/ble-advertisement-rate-actual-rate-do-not-match</link><description>I currently have a Braveridge device which uses an advertising rate of 50 Hz (connection interval is 20ms) 
 CONNECTABLE_ADV_INTERVAL is set to 0x0020 
 sd_ble_gap_adv_start(&amp;amp;m_adv_params); 
 In the advert packet I have a counter(1byte), so I can determine</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 14 Nov 2017 21:17:28 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/7120/ble-advertisement-rate-actual-rate-do-not-match" /><item><title>RE: BLE Advertisement Rate &amp; Actual Rate Do Not Match</title><link>https://devzone.nordicsemi.com/thread/25154?ContentTypeID=1</link><pubDate>Tue, 14 Nov 2017 21:17:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2baa2ae7-be77-4d05-81b3-ac17f40ac5c8</guid><dc:creator>jemajuca</dc:creator><description>&lt;p&gt;Hello.
Considering the effect of the advDelay, it seems impossible to match with the Apple requirements.
(Bluetooth Accessory Design Guidelines for Apple Products, section 3.5, Advertising Interval)&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s say I want to select 318.75 ms, which value should be selected?&lt;/p&gt;
&lt;p&gt;Which should be the correct advertising interval setting? 324? (319 + advdelay/2)
Regards.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Advertisement Rate &amp; Actual Rate Do Not Match</title><link>https://devzone.nordicsemi.com/thread/25153?ContentTypeID=1</link><pubDate>Tue, 19 May 2015 12:52:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0b33fbfc-850e-490d-98ee-e46d3c7d2755</guid><dc:creator>Petter Myhre</dc:creator><description>&lt;p&gt;Good question.&lt;/p&gt;
&lt;p&gt;From the Bluetooth Core specification, Vol 6, Part B, Section 4.4.2.2:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;The time between two the start of two
consecutive advertising events is
computed as follows for each
advertising event:&lt;/p&gt;
&lt;p&gt;T_advEvent = advInterval + advDelay&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;The advDelay is a pseudo-random value
with a range of 0 ms to 10 ms
generated by the Link Layer for each
advertising event.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;If this averages to 5 ms you end up with (20ms + 5ms)f = 1000ms -&amp;gt; f=40Hz.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>