<?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 Scanning (central) vs Adverising (Peripheral)</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/22021/ble-scanning-central-vs-adverising-peripheral</link><description>Hi guys, 
 I am working with a central battery powered so, I am controlling the RF activity calling scan_start() or sd_ble_gap_scan_start() and disabling the RF activity with sd_ble_gap_scan_stop() after 20ms 
 My scan_interval and scan_window have</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 17 May 2017 20:01:43 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/22021/ble-scanning-central-vs-adverising-peripheral" /><item><title>RE: BLE Scanning (central) vs Adverising (Peripheral)</title><link>https://devzone.nordicsemi.com/thread/86405?ContentTypeID=1</link><pubDate>Wed, 17 May 2017 20:01:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4959b757-8f40-44df-badf-78cc2e6f9398</guid><dc:creator>Mufasa1</dc:creator><description>&lt;p&gt;Hey Jørn Thanks for all the info :)
very useful&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Scanning (central) vs Adverising (Peripheral)</title><link>https://devzone.nordicsemi.com/thread/86404?ContentTypeID=1</link><pubDate>Mon, 15 May 2017 13:57:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:32bfb52c-d6f1-43ec-8674-5ca2a1ef45b5</guid><dc:creator>J&amp;#248;rn</dc:creator><description>&lt;p&gt;Hello Mufasa1&lt;/p&gt;
&lt;p&gt;The scan interval sets the time between two scans, and the time window sets how long the device should scan during said interval. Advertisement happens on three different channels, and every time a scan starts it scans one of those channels. The next time it starts a scan, it scans the next channel etc.&lt;/p&gt;
&lt;p&gt;By setting both the interval and window to 6.25 ms, your device is continuously scanning, with the exception of a minor interval between scans when it changes channel. It will keep scanning one channel for 6.25 ms, before it moves on to the next. With 20ms before you stop the advertisement you will manage to scan all three channels.&lt;/p&gt;
&lt;p&gt;As long as the advertiser uses all three advertisement channels it will advertise on all three channels, once every advertisement intverval. If you are continuously scanning one of the channels, you should be able to pick up the advertisement the moment it happens.&lt;/p&gt;
&lt;p&gt;In relation to reducing power consumption it might be more beneficial to simply use the scan interval and scan window at appropriate settings, and allow the chip to sleep between scans.&lt;/p&gt;
&lt;p&gt;You can read more on the scanner timings on page 63 in the Softdevice documentation &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.sds/dita/softdevices/s130/multilink_scheduling/scanner_timing.html?cp=2_3_0_0_14_3"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Information on scanning and advertisement in general can be found on the blog &lt;a href="https://devzone.nordicsemi.com/blogs/782/bluetooth-smart-and-the-nordics-softdevices-part-1/"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Best regards&lt;/p&gt;
&lt;p&gt;Jørn Frøysa&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>