<?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>Change Advertising Speed on Scan Response</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/34350/change-advertising-speed-on-scan-response</link><description>I am working on a project working with remote connectable beacons. One of the easiest ways to save power in these applications is to reduce advertising speed, however, this comes at the cost of getting a reliable/timely connection. 
 I have been experimenting</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 15 May 2018 17:08:43 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/34350/change-advertising-speed-on-scan-response" /><item><title>RE: Change Advertising Speed on Scan Response</title><link>https://devzone.nordicsemi.com/thread/132126?ContentTypeID=1</link><pubDate>Tue, 15 May 2018 17:08:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:69bfc55e-41d7-4e7e-9435-936224f85998</guid><dc:creator>WestCoastDaz</dc:creator><description>&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/members/ishgum"&gt;ishgum&lt;/a&gt;&amp;nbsp; We do something similar in one of our products without any issues.&amp;nbsp; In fact if you look at &lt;pre class="ui-code" data-mode="c_cpp"&gt;ble_advertising.h&lt;/pre&gt; in the SDK you will see it implements something called fast and slow advertising is changes the advertising interval.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Change Advertising Speed on Scan Response</title><link>https://devzone.nordicsemi.com/thread/132071?ContentTypeID=1</link><pubDate>Tue, 15 May 2018 13:49:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:659ebf83-edb6-419e-8d7d-a64799e2dded</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;I do not see any issues with stopping and starting the advertising again as you describe. In fact, at least one of the examples in the SDK (the eddystone beacon) does this. You can use the softdevice call &lt;a href="http://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.s140.api.v6.0.0%2Fgroup___b_l_e___g_a_p___f_u_n_c_t_i_o_n_s.html&amp;amp;cp=2_3_2_1_0_2_1_2_4&amp;amp;anchor=ga732faeeb8489dcb34873d78e773957bc" target="_blank" rel="noopener noreferrer"&gt;sd_ble_gap_adv_stop()&lt;/a&gt;&amp;nbsp;to stop the advertisement. Just check the return of this function call. If it returns BLE_ERROR_INVALID_ADV_HANDLE, it is called with an invalid handle. If it returns NRF_SUCCESS, it has stopped the advertising, and you can configure the advertisement with the updated advertising interval. If it returns NRF_ERROR_INVALID_STATE, it means that the device is not advertising (it has already been stopped), and you can ignore this return, and configure the advertising interval.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>