<?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>S120 scanning can not be sustained</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/4613/s120-scanning-can-not-be-sustained</link><description>Hi, 
 There are two advertise nodes, only broadcast (one packet/s) . The S120 star scan. At the beginning everything is OK，but after a while, maybe 3-5 minutes, only one advertise node can be discovered. Then, after an other 3-5 minutes, the scan return</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 01 Dec 2014 01:07:08 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/4613/s120-scanning-can-not-be-sustained" /><item><title>RE: S120 scanning can not be sustained</title><link>https://devzone.nordicsemi.com/thread/16389?ContentTypeID=1</link><pubDate>Mon, 01 Dec 2014 01:07:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2fdcef52-89b7-47a3-8b7b-30b03dbf2938</guid><dc:creator>YeLun</dc:creator><description>&lt;p&gt;Thanks a lot for you help.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: S120 scanning can not be sustained</title><link>https://devzone.nordicsemi.com/thread/16387?ContentTypeID=1</link><pubDate>Fri, 28 Nov 2014 01:24:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a894140f-dbc0-4f9f-94c5-9ddc826ff117</guid><dc:creator>YeLun</dc:creator><description>&lt;p&gt;Ah! Before your answer, I have already suspect the scan_window and tried &amp;quot;m_scan_param.window = 0x009F; &amp;quot;, it was not work correctly. Ok, let me try &amp;quot;0x009E&amp;quot;.&lt;/p&gt;
&lt;p&gt;If there always need to minus 2 from scan_interval? And minus 2 mean 1.25mS, may be miss one pack. Could you tell me why minus 2?&lt;/p&gt;
&lt;p&gt;if I need scan_interval be 0X3E8(1000mS), scan_window will be 0X3E6(998.75mS), Is that right ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: S120 scanning can not be sustained</title><link>https://devzone.nordicsemi.com/thread/16388?ContentTypeID=1</link><pubDate>Thu, 27 Nov 2014 12:31:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:128fe95a-d945-48cf-9431-ad11adb3aa4a</guid><dc:creator>Petter Myhre</dc:creator><description>&lt;p&gt;It is a bug with the S120, you can&amp;#39;t have the scanning window equal to the scanning interval.&lt;/p&gt;
&lt;p&gt;A workaround should be to decrease the scanning window slightly, please try 0x009E instead of 0x00A0.&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;m_scan_param.interval     = 0x00A0;  // Scan interval.
m_scan_param.window       = 0x009E;  // Scan window.
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;@boyu: I don&amp;#39;t know the details behind why it is 1.25ms, but somehow the scanner doesn&amp;#39;t have time to restart.&lt;/p&gt;
&lt;p&gt;I have done some testing, and it seems that 1.25ms is enough, or minus 2 as you say. But 0x3E8 is not 1000ms, because it is 0x3E8&lt;em&gt;0.625ms = 1000&lt;/em&gt;0.625ms = 625ms.&lt;/p&gt;
&lt;p&gt;You should use:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;m_scan_param.interval     = 0x0640;  // Scan interval.
m_scan_param.window       = 0x063E;  // Scan window.
&lt;/code&gt;&lt;/pre&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>