<?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>Advertising not linked state</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/8751/advertising-not-linked-state</link><description>Hello everybody,
I am currently experimenting with BLE on the nRF51-Ek. At measurement on the oscilloscope, the BLE protocol shows a behavior that I do not quite understand or i do not know in which documentation i can read up on it. Here is a picture</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 17 Aug 2015 13:28:11 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/8751/advertising-not-linked-state" /><item><title>RE: Advertising not linked state</title><link>https://devzone.nordicsemi.com/thread/32090?ContentTypeID=1</link><pubDate>Mon, 17 Aug 2015 13:28:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:07782daf-6012-409b-b699-2ffd198be234</guid><dc:creator>m1zol3</dc:creator><description>&lt;p&gt;Thank you.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Advertising not linked state</title><link>https://devzone.nordicsemi.com/thread/32089?ContentTypeID=1</link><pubDate>Sun, 16 Aug 2015 15:09:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:09e56a2f-3924-45c0-964a-2c82b5a62735</guid><dc:creator>Ulrich Myhre</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;This is quite normal.&lt;/p&gt;
&lt;p&gt;Advertising in BLE works like this: For each available channel (default 37, 38 and 39) send an advertisement, then wait for a scan request or connect request to come ~150 us after. If this request arrives, and the peer is in the whitelist (in cases where whitelist is being used) then the advertiser will either: send a scan response and continue to the next channel OR go into a connection with the peer and stop the advertiser.&lt;/p&gt;
&lt;p&gt;I would recommend reading an introduction to BLE - or even the spec itself - if you are interested in deciphering more scenarios like this.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>