<?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>Gazell - transmit 10 bytes in under 2ms</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/7833/gazell---transmit-10-bytes-in-under-2ms</link><description>Is this even possible? I have a BLE connection with an interval of 7.5 ms. I&amp;#39;ve set up a radio notification with a distance of 2680us in order to be able to transmit 4 BLE packets. When the notification happens I request a timeslot with the length of</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 25 Jun 2015 13:37:28 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/7833/gazell---transmit-10-bytes-in-under-2ms" /><item><title>RE: Gazell - transmit 10 bytes in under 2ms</title><link>https://devzone.nordicsemi.com/thread/27919?ContentTypeID=1</link><pubDate>Thu, 25 Jun 2015 13:37:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b1a41e11-4f13-4f0e-a47c-1a818599771b</guid><dc:creator>ImQ009</dc:creator><description>&lt;p&gt;Yes, after thinking about it I&amp;#39;ll propably just use a single channel and implement a different kind of hopping myself. Also, it appears a timeslot of 510us also works well, which is great.
And no, there&amp;#39;s no reason for me to stick with Gazell. In fact I might use the radio directly.&lt;/p&gt;
&lt;p&gt;Thank you for your assistance, it was very helpful&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Gazell - transmit 10 bytes in under 2ms</title><link>https://devzone.nordicsemi.com/thread/27918?ContentTypeID=1</link><pubDate>Thu, 25 Jun 2015 13:35:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fb082915-d7be-4064-b3dd-c8a49ace85a9</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;I know, this is not what we have tested. But I assume with small (10-byte) payload you should be able to get away with 550us timeslot.&lt;/p&gt;
&lt;p&gt;Another option is to use just one channel. But then you will have to deal with the interference issue. You can manually do channel hopping then.&lt;/p&gt;
&lt;p&gt;Is there any particular reason you need to use Gazell but not using the Radio directly instead ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Gazell - transmit 10 bytes in under 2ms</title><link>https://devzone.nordicsemi.com/thread/27917?ContentTypeID=1</link><pubDate>Thu, 25 Jun 2015 13:09:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:aa6dd8c9-5d74-41b5-9aa1-e00c0cfdb11a</guid><dc:creator>ImQ009</dc:creator><description>&lt;p&gt;But can I actually do that? The documentation states that in communication between nRF51 chips using Gazell the minimum supported timeslot is 600us&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Gazell - transmit 10 bytes in under 2ms</title><link>https://devzone.nordicsemi.com/thread/27916?ContentTypeID=1</link><pubDate>Thu, 25 Jun 2015 13:06:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:71520c3b-e8f9-4204-aa97-db300429db52</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;@lmQ009: In out-of-sync mode, the host remain in one channel for at least 2 timeslot before it&amp;#39;s switch to the next one.&lt;/p&gt;
&lt;p&gt;This explain why it worked for you when you have 3.6ms = 600us x 2 x 3.&lt;/p&gt;
&lt;p&gt;Even with 2 channels you would have trouble with 2.2ms (2.4ms needed). I would suggest you to change the timeslot to 550us and use 2 channels.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>