<?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>Help:breaks in slave node advertising</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/3400/help-breaks-in-slave-node-advertising</link><description>Hi All, 
 I need the slave node(S110) send advertising continuously and monitored by master node, so I set the advertising parameters as: 
 adv_params.type = BLE_GAP_ADV_TYPE_ADV_NONCONN_IND;
adv_params.p_peer_addr = NULL;
adv_params.fp = BLE_GAP_ADV_FP_ANY;</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 12 Aug 2014 01:57:40 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/3400/help-breaks-in-slave-node-advertising" /><item><title>RE: Help:breaks in slave node advertising</title><link>https://devzone.nordicsemi.com/thread/12341?ContentTypeID=1</link><pubDate>Tue, 12 Aug 2014 01:57:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fe8783f8-7df8-424b-9c7f-5c3253ac9998</guid><dc:creator>frank zhang</dc:creator><description>&lt;p&gt;I got a PCA10000 and successfully monitored the slave node with wireshark, the log shows there are no breaks in slave node&amp;#39;s advertising, the problem should be at S120 side. I am curious why the master node can&amp;#39;t get the advertising from one slave node continuously, when the problem occurs, the master node&amp;#39;s RF is active as it can receive advertising from other nodes at the same time.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Help:breaks in slave node advertising</title><link>https://devzone.nordicsemi.com/thread/12340?ContentTypeID=1</link><pubDate>Fri, 08 Aug 2014 10:04:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:04bd59d8-8979-4014-b5e9-f2fe0639c410</guid><dc:creator>frank zhang</dc:creator><description>&lt;p&gt;I tried sniffer with my customized nrf51822 evb and failed to connect the com port, I guess this connection problem might be related to the clock as I need to configure NRF_CLOCK_LFCLKSRC_RC_250_PPM_TEMP_4000MS_CALIBRATION to make the evb run.&lt;/p&gt;
&lt;p&gt;For the the problem I reported, as the master node can receive signals from other slave nodes when the advertising from the selected slave node stoped, which means the master node is working at the time, I guess the selected node should actually stops adverstising or the master node chooses to ignore this slave node, I want to know why and how to solve it.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Help:breaks in slave node advertising</title><link>https://devzone.nordicsemi.com/thread/12338?ContentTypeID=1</link><pubDate>Fri, 08 Aug 2014 00:45:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5c2489b0-205c-46e6-b316-2150e3e3f8a8</guid><dc:creator>frank zhang</dc:creator><description>&lt;p&gt;I tried with the newest Softdevice s110_nrf51822_7.0.0_softdevice.hex+new SDK and an also older version s110_nrf51822_5.2.1_softdevice.hex + old SDK, both got the same results. My S120 is based on s120_nrf51822_1.0.0_softdevice.hex + SDK nrf51822_v5.2.0.39364.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Help:breaks in slave node advertising</title><link>https://devzone.nordicsemi.com/thread/12337?ContentTypeID=1</link><pubDate>Thu, 07 Aug 2014 16:00:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ba49f6d2-bd77-4724-bf37-a9f153344e1b</guid><dc:creator>Ulrich Myhre</dc:creator><description>&lt;p&gt;It would really help if you could mention or tag your post with the S110 version, thanks!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Help:breaks in slave node advertising</title><link>https://devzone.nordicsemi.com/thread/12339?ContentTypeID=1</link><pubDate>Thu, 07 Aug 2014 12:19:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5e32a895-1eac-4469-a136-80258fe6c263</guid><dc:creator>John</dc:creator><description>&lt;p&gt;The easiest way to tell if your problem is with your advertiser or your central device is to capture the behavior in a sniffer. Nordic provides an easy way to convert your eval or dev kit into a sniffer. See here:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.nordicsemi.com/eng/Products/Bluetooth-R-low-energy/nRF-Sniffer/(language)/eng-GB"&gt;Sniffer download&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>