<?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>Scanning time during dual-role operation (not dual-mode).</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/56254/scanning-time-during-dual-role-operation-not-dual-mode</link><description>I am in the process of evaluating different BLE solutions for a project. The project consists of a pair of BLE-enabled devices which need to be able to go into dual-role mode (simultaneous advertising and scanning) and connect to the other device. I would</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 07 Jan 2020 14:25:48 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/56254/scanning-time-during-dual-role-operation-not-dual-mode" /><item><title>RE: Scanning time during dual-role operation (not dual-mode).</title><link>https://devzone.nordicsemi.com/thread/227927?ContentTypeID=1</link><pubDate>Tue, 07 Jan 2020 14:25:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bd78c58b-3609-4bec-83a0-de7ba1e499e4</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi Brian,&lt;/p&gt;
&lt;p&gt;The delays on the nRF5 devices with SoftDevice depend on several factors, as you can see under &lt;a href="https://infocenter.nordicsemi.com/topic/sds_s140/SDS/s1xx/multilink_scheduling/multilink_scheduling.html?cp=4_5_3_0_14"&gt;Scheduling&lt;/a&gt;. I do not have an exact number for this though.&lt;/p&gt;
&lt;p&gt;Regarding what you see (on the non-Nordic product), I can only speculate that the 10 ms could be related to the 0-10 ms random delay added to the advertising interval. This is a delay that you cannot escape since that is enforced by the BLE specification.&lt;/p&gt;
&lt;p&gt;If you want to increase the likelihood of the two devices being able to connect (not ending up in a situation where they both scan or advertise at the same time for a long time), you could perhaps regularly change the scan/advertising duty cycle randomly?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>