<?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>Deafness times for S130 and S132</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/26327/deafness-times-for-s130-and-s132</link><description>UPDATE: Corrected language. 
 Hi,
While experimenting with BLE mesh networking using S130 on nRF51 devices and S132 on nRF52 devices, we have a problem with deafness while receiving. We set the devices for continuous scanning, and intermittent advertising</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 27 Oct 2017 13:55:45 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/26327/deafness-times-for-s130-and-s132" /><item><title>RE: Deafness times for S130 and S132</title><link>https://devzone.nordicsemi.com/thread/103596?ContentTypeID=1</link><pubDate>Fri, 27 Oct 2017 13:55:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ec482f3e-bea7-4722-b284-fdb9a3a3d75a</guid><dc:creator>Elm</dc:creator><description>&lt;p&gt;Thanks, that was the answer I was looking for.&lt;/p&gt;
&lt;p&gt;regards,
Elm&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Deafness times for S130 and S132</title><link>https://devzone.nordicsemi.com/thread/103595?ContentTypeID=1</link><pubDate>Fri, 27 Oct 2017 11:32:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:700711db-bde0-4cc3-99bb-1014669635b4</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Elm,&lt;/p&gt;
&lt;p&gt;Your observation was correct. The scheduler on the softdevice, with limitation on the complexity, doesn&amp;#39;t have much flexibility when it come to arranging timeslot.&lt;/p&gt;
&lt;p&gt;The long switching time (around 800us) was the limitation of the softdevice, not of the chip (40us)&lt;/p&gt;
&lt;p&gt;As far as I know, even though the scheduler was re-written from S132 v4.0, the way it works is unchanged. We reduced some housekeeping time but that&amp;#39;s it.&lt;/p&gt;
&lt;p&gt;Keep in mind that the softdevices were not designed for mesh.&lt;/p&gt;
&lt;p&gt;As Tom already suggest, you can either use our mesh solution or implement your own solution either using timeslot, or not using softdevice at all.&lt;/p&gt;
&lt;p&gt;Another suggestion is to &lt;a href="https://devzone.nordicsemi.com/blogs/1059/nrf5x-support-within-the-zephyr-project-rtos/"&gt;use Zephyr&lt;/a&gt;, you have access all the way to the controller and can use HCI to command.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Deafness times for S130 and S132</title><link>https://devzone.nordicsemi.com/thread/103594?ContentTypeID=1</link><pubDate>Thu, 26 Oct 2017 13:05:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:61ea16d2-5e2a-4802-a7d2-9b42d005fd69</guid><dc:creator>Elm</dc:creator><description>&lt;p&gt;Tom,&lt;/p&gt;
&lt;p&gt;Thanks for your expedited reply!&lt;/p&gt;
&lt;p&gt;Your answer is essentially the same as my &amp;quot;solution 1.&amp;quot; Yes, we have looked at the Mesh SDK, and we believe that this is the best way forward.&lt;/p&gt;
&lt;p&gt;However, I specifically wondered if there were changes to the scheduler in later/newer versions of the SDK which could help us, as in my (hoped-for) &amp;quot;solution 2&amp;quot;. Also, not all implementations of BLE controllers in the world can benefit from using a Timeslot API-type of interface.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;From you avoiding discussion the matter, can I assume that there are no such improvements?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;regards,
Elm&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Deafness times for S130 and S132</title><link>https://devzone.nordicsemi.com/thread/103593?ContentTypeID=1</link><pubDate>Thu, 26 Oct 2017 12:49:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:947b2efa-7624-4356-94b3-4e0fecdaf711</guid><dc:creator>thst</dc:creator><description>&lt;p&gt;Elm,&lt;/p&gt;
&lt;p&gt;I see that you have made quite a bit of progress.  Have you looked at the Mesh SDK?&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;It solves this deafness issue by using timeslot API&lt;/li&gt;
&lt;li&gt;It is built on top of the S130/S132&lt;/li&gt;
&lt;li&gt;It is open source, so you can use what you want as long as it is on an nRF device&lt;/li&gt;
&lt;li&gt;&lt;a href="http://www.nordicsemi.com/eng/Products/Bluetooth-low-energy/nRF5-SDK-for-Mesh"&gt;http://www.nordicsemi.com/eng/Products/Bluetooth-low-energy/nRF5-SDK-for-Mesh&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;-Tom&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>