<?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>Best approach to have a nRF51822 always discoverable?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/932/best-approach-to-have-a-nrf51822-always-discoverable</link><description>Dear Nordic Developer, 
 I am using nRF51822 with softdevice. 
 What is the best approach to have a nRF51822 always discoverable? Like heart monitor for example : no need to press button to discover the device and connect to it? 
 After spending few</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 20 Nov 2013 14:57:37 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/932/best-approach-to-have-a-nrf51822-always-discoverable" /><item><title>RE: Best approach to have a nRF51822 always discoverable?</title><link>https://devzone.nordicsemi.com/thread/4485?ContentTypeID=1</link><pubDate>Wed, 20 Nov 2013 14:57:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b9e66287-a34b-492e-a3a0-2a2e5751e3b9</guid><dc:creator>Ole Morten</dc:creator><description>&lt;p&gt;You may also have use in looking at &lt;a href="https://devzone.nordicsemi.com/index.php/advertising-with-no-timeout"&gt;this question&lt;/a&gt;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Best approach to have a nRF51822 always discoverable?</title><link>https://devzone.nordicsemi.com/thread/4483?ContentTypeID=1</link><pubDate>Tue, 19 Nov 2013 08:58:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:97190555-3f3f-4adf-94c2-e420be4fd8ea</guid><dc:creator>S&amp;#233;bastien Despont</dc:creator><description>&lt;p&gt;Hi Elca,&lt;/p&gt;
&lt;p&gt;Useful comment, I didn&amp;#39;t know that.&lt;/p&gt;
&lt;p&gt;Best regards&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Best approach to have a nRF51822 always discoverable?</title><link>https://devzone.nordicsemi.com/thread/4482?ContentTypeID=1</link><pubDate>Tue, 19 Nov 2013 08:33:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cd7d9705-bca8-4e17-96f7-f2c3ffd888de</guid><dc:creator>Elca</dc:creator><description>&lt;p&gt;Hi Sébastien,&lt;/p&gt;
&lt;p&gt;As for as I know, timeout could be disabled by setting timeout to 0x0000.
I have seen the comments in ble_gap.h::ble_gap_adv_params_t::timeout.
Hope it helps.&lt;/p&gt;
&lt;p&gt;Regards,
Elca&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Best approach to have a nRF51822 always discoverable?</title><link>https://devzone.nordicsemi.com/thread/4484?ContentTypeID=1</link><pubDate>Tue, 19 Nov 2013 07:39:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3ca7660b-da33-4b58-9a04-888d61afb879</guid><dc:creator>balaji</dc:creator><description>&lt;p&gt;Hi Sebastien,&lt;/p&gt;
&lt;p&gt;Just remove is_first_start()  function from main ,and call advertisement_start()&lt;/p&gt;
&lt;p&gt;function in  on_ble_evt(). in case of  disconnect and timeout.&lt;/p&gt;
&lt;p&gt;Regards
Balaji&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>