<?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>problem advertise duration on SoftDevice V6.0.0(nrf52832)</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/32792/problem-advertise-duration-on-softdevice-v6-0-0-nrf52832</link><description>I test SoftDevice V6.0.0 on nrf52832(BLENANO2) I run 1. sd_ble_gap_scan_start() 1000ms/100ms/10ms scan_window/scan_interval 2. sd_ble_gap_adv_start() 1000ms interval result. (see picture) for example, scan interval is 1000ms, scan-off -&amp;gt; advertise -&amp;gt;</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 27 Mar 2018 23:09:26 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/32792/problem-advertise-duration-on-softdevice-v6-0-0-nrf52832" /><item><title>RE: problem advertise duration on SoftDevice V6.0.0(nrf52832)</title><link>https://devzone.nordicsemi.com/thread/126177?ContentTypeID=1</link><pubDate>Tue, 27 Mar 2018 23:09:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:dfa61a65-05a8-4925-ab78-52bc23f36dc0</guid><dc:creator>loquat</dc:creator><description>&lt;p&gt;Oh, really.&lt;/p&gt;
&lt;p&gt;&lt;span class="short_text" id="result_box" lang="en"&gt;&lt;span class=""&gt;I had a misunderstanding.&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Tahnk you.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem advertise duration on SoftDevice V6.0.0(nrf52832)</title><link>https://devzone.nordicsemi.com/thread/126153?ContentTypeID=1</link><pubDate>Tue, 27 Mar 2018 16:18:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2525b95f-3c16-449f-a1c1-09501133e731</guid><dc:creator>tesc</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;The way scanning works, is that the SoftDevice schedules a timeslot event for each scan event, which lasts for the entire scan window. When timing events overlap only one of them will run while the others are dropped entirely.&lt;/p&gt;
&lt;p&gt;What you see is one scan event being dropped when an advertising event is successfully scheduled. It leaves a break in scanning corresponding to one scan interval.&lt;/p&gt;
&lt;p&gt;What event to run and what event to drop is decided as documented in &lt;a href="http://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.s132.sds%2Fdita%2Fsoftdevices%2Fs130%2Fmultilink_scheduling%2Fpriorities_and_events_intro.html"&gt;SoftDevice timing-activities and priorities&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Terje&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>