<?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>Scan windows dropping while connected.</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/55347/scan-windows-dropping-while-connected</link><description>I&amp;#39;ve been attempting to optimize my scan and connection intervals in order to maintain the highest percentage of time scanning while maintaining connections, following the advice set out in section 15.10 of the S140 spec, and have been running issues</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 09 Dec 2019 14:10:03 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/55347/scan-windows-dropping-while-connected" /><item><title>RE: Scan windows dropping while connected.</title><link>https://devzone.nordicsemi.com/thread/224485?ContentTypeID=1</link><pubDate>Mon, 09 Dec 2019 14:10:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:857c3e93-38d7-4123-ba44-61619df36171</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Drew,&lt;/p&gt;
&lt;p&gt;Connection and scanning role has the same scheduling priority at level 3 according to Table 30 Scheduling Priorities in S140 Specification v1.1&amp;nbsp;&lt;/p&gt;
&lt;p&gt;When the scanner slot is blocked by the advertising slot, it will only reschedule on the next event which is 500ms after. This result in that&amp;nbsp;the chip only does scanning 200ms in 1 seconds.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;What you can do to improve the scanning rate is to reduce the scan interval to says 100ms and do scanning window of 50ms for example. Scanning period will only be blocked for 100ms when the advertising events happen instead of blocking for 500ms.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>