<?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>esb &amp;quot;realtime&amp;quot; - timeslots - nrf51 example</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/15385/esb-realtime---timeslots---nrf51-example</link><description>Hi 
 can ESB be considered RealTime transfer as soon as it has it&amp;#39;s timeslot? 
 Outline of use-case: 
 
 Device advertises existenace on BLE 
 If there is data waiting for this device, it would be notified e.g. by an attr-read 
 the device turns</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 17 Aug 2016 13:58:19 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/15385/esb-realtime---timeslots---nrf51-example" /><item><title>RE: esb "realtime" - timeslots - nrf51 example</title><link>https://devzone.nordicsemi.com/thread/58759?ContentTypeID=1</link><pubDate>Wed, 17 Aug 2016 13:58:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:057fdb71-8604-4ce8-8082-05fdf6c19850</guid><dc:creator>Ole Bauck</dc:creator><description>&lt;p&gt;Trigger the radio callback? It should work to set pending TIMER0 interrupt:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;NVIC_SetPendingIRQ(TIMER0_IRQn);
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;I have not tested this.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: esb "realtime" - timeslots - nrf51 example</title><link>https://devzone.nordicsemi.com/thread/58758?ContentTypeID=1</link><pubDate>Wed, 17 Aug 2016 08:25:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5b56f4af-7e2a-4a51-8762-3dd7fa7e861b</guid><dc:creator>Martin</dc:creator><description>&lt;p&gt;Is there any possibility to trigger this?&lt;/p&gt;
&lt;p&gt;Currently I close the session on the device, as it is put to system off after it completed sending payloads.&lt;/p&gt;
&lt;p&gt;I use a singleshot timer of 3 sec, when fired it waits for esb_idle, then closes the radio session. From my point of view this is not the cleanest way to solve this... right?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: esb "realtime" - timeslots - nrf51 example</title><link>https://devzone.nordicsemi.com/thread/58757?ContentTypeID=1</link><pubDate>Wed, 17 Aug 2016 08:20:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:710a841e-b5d6-429a-87f5-288606e36d30</guid><dc:creator>Ole Bauck</dc:creator><description>&lt;p&gt;You can close a timeslot from timer0 interrupt by setting the &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s130.api.v2.0.0/structnrf__radio__signal__callback__return__param__t.html#ac938534ea4bdd342a3cb36c94071e073"&gt;callback_action&lt;/a&gt; to &lt;code&gt;NRF_RADIO_SIGNAL_CALLBACK_ACTION_END&lt;/code&gt; (in &lt;code&gt;radio_callback(..)&lt;/code&gt;). You can only close the timeslot from the radio callback (unless you close the session, but I don&amp;#39;t think that is a good idea).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: esb "realtime" - timeslots - nrf51 example</title><link>https://devzone.nordicsemi.com/thread/58756?ContentTypeID=1</link><pubDate>Tue, 16 Aug 2016 15:40:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:85cefe27-a539-4341-8db8-acb69f03cd8b</guid><dc:creator>Martin</dc:creator><description>&lt;p&gt;Hi Ole&lt;/p&gt;
&lt;p&gt;thanks a lot. In fact the problem was the timeslot timing. It was more or less out of sync. After I solved this everything worked perfect.&lt;/p&gt;
&lt;p&gt;May I ask you for an example on how to properly close the timeslot from a timer call?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: esb "realtime" - timeslots - nrf51 example</title><link>https://devzone.nordicsemi.com/thread/58755?ContentTypeID=1</link><pubDate>Tue, 16 Aug 2016 15:28:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:dd935f3b-1157-46db-ad98-fa16303b03e3</guid><dc:creator>Ole Bauck</dc:creator><description>&lt;p&gt;I would not believe that to be the problem, but you could try with using xtal (like on a DK) and see if the problem is still there. Are you timing the sending such that the receiver is listening at the correct time (since you are asking if the LFCLK source can be the issue)?&lt;/p&gt;
&lt;p&gt;The problem may also be interference, try another channel or try a place where there is not that many devices communicating in the 2.4GHz band.&lt;/p&gt;
&lt;p&gt;Does it work without using timeslot, like the esb examples (under examples/proprietary_rf)?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: esb "realtime" - timeslots - nrf51 example</title><link>https://devzone.nordicsemi.com/thread/58760?ContentTypeID=1</link><pubDate>Mon, 15 Aug 2016 08:33:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1c05f38f-c4d2-425a-bf5a-2dad2ba0d675</guid><dc:creator>Martin</dc:creator><description>&lt;p&gt;Hi Ole
I have integrated your source into our FW.
For some reason in 90% of the cases I do not get an ACK package from the receiver...
Might this be because we are not using an XTAL, but only the intrenal RC? Meaning to much drift because of this?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: esb "realtime" - timeslots - nrf51 example</title><link>https://devzone.nordicsemi.com/thread/58754?ContentTypeID=1</link><pubDate>Tue, 09 Aug 2016 11:14:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f0462299-eaaa-422b-ad0e-1ff4e02a2f9e</guid><dc:creator>Ole Bauck</dc:creator><description>&lt;p&gt;There is no example in the SDK. We have an example here that works with nRF52, I will update my answer with this file.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: esb "realtime" - timeslots - nrf51 example</title><link>https://devzone.nordicsemi.com/thread/58753?ContentTypeID=1</link><pubDate>Fri, 29 Jul 2016 11:19:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:254d1db4-c228-4e7b-9820-3ba956a50f8d</guid><dc:creator>Martin</dc:creator><description>&lt;p&gt;Can you hint me to an example project for SDK11 which works? I was not able to make this scenario work for the last 3 days. Also because of this problem: &lt;a href="https://devzone.nordicsemi.com/question/88825/app_timer-and-nrf_esb/?answer=88895#post-id-88895"&gt;other question&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: esb "realtime" - timeslots - nrf51 example</title><link>https://devzone.nordicsemi.com/thread/58752?ContentTypeID=1</link><pubDate>Fri, 29 Jul 2016 11:13:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:96712d73-d7de-46d5-9f20-510f86074da2</guid><dc:creator>Ole Bauck</dc:creator><description>&lt;p&gt;This scenario is possible with S130. To send data to the device (notification or attr-read) you have to be connected, so you would have to connect after advertising.&lt;/p&gt;
&lt;p&gt;If ESB is “realtime” depends on what you call “realtime”. ESB may be the fastest way to send data as soon as you are in a timeslot or have full control over the radio.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Update 2016.08.09:&lt;/strong&gt; Here is a project that uses esb in timeslot: &lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/1207.ble_5F00_app_5F00_uart-_2D00_-ESB_5F00_Timeslot.zip"&gt;ble_app_uart - ESB_Timeslot.zip&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>