<?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>Unstable timeslot with esb and ble concurrently</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/21498/unstable-timeslot-with-esb-and-ble-concurrently</link><description>Hi, 
 I&amp;#39;ve just got the example running with one DK as ble peripheral and ESB at the same time uing the timeslot API and one DK as only ESB receiver.
I can communicate fine between all elements (ble master is a laptop). But if I just keep the timeslot</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 25 Apr 2017 14:22:21 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/21498/unstable-timeslot-with-esb-and-ble-concurrently" /><item><title>RE: Unstable timeslot with esb and ble concurrently</title><link>https://devzone.nordicsemi.com/thread/84366?ContentTypeID=1</link><pubDate>Tue, 25 Apr 2017 14:22:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fc34b1ac-89f2-45b0-b346-fc50359399b6</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;The timeslot should work regardless you are advertising or in connection or do nothing. I don&amp;#39;t see the reason why it shouldn&amp;#39;t work.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unstable timeslot with esb and ble concurrently</title><link>https://devzone.nordicsemi.com/thread/84364?ContentTypeID=1</link><pubDate>Tue, 25 Apr 2017 13:48:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:57a5b549-d548-4acc-bd96-c07a50d0ee0b</guid><dc:creator>Constantin</dc:creator><description>&lt;p&gt;okay with this change the BLE keeps advertising. And I&amp;#39;ve only once got the hanging timeslot. But do I have to keep the BLE advertising because I would like to send the ble to sleep and let the esb running after a certain amount of time and let the BLE return to advertising if a button was pressed.
You can find the last version of my project here without the changes for the advertising mode.
&lt;a href="https://devzone.nordicsemi.com/question/129891/sleep-mode-during-multiprotocol-timeslot-api/"&gt;devzone.nordicsemi.com/.../&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unstable timeslot with esb and ble concurrently</title><link>https://devzone.nordicsemi.com/thread/84361?ContentTypeID=1</link><pubDate>Tue, 25 Apr 2017 12:54:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d16a55b6-c596-4c82-82a3-d123100d842f</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;When you set APP_ADV_TIMEOUT_IN_SECONDS = 0 you need to set advdata.flags = *_GENERAL_DISC_MODE; instead of *_LIMITED_DISC_MODE or you will receive invalid parameter as the LIMTED mode can&amp;#39;t be use with infinite advertising.&lt;/p&gt;
&lt;p&gt;Please try to test with the esb timeslot ble example and send me the project if you can reproduce the issue with minimum modification from the example.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unstable timeslot with esb and ble concurrently</title><link>https://devzone.nordicsemi.com/thread/84363?ContentTypeID=1</link><pubDate>Mon, 24 Apr 2017 15:04:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fe861d33-2e4b-48a9-b624-42e38e55c4c2</guid><dc:creator>Constantin</dc:creator><description>&lt;p&gt;Have you tried to to simply keep the BLE advertising continuously ? Simply set APP_ADV_TIMEOUT_IN_SECONDS = 0 and advdata.flags = BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE;&lt;/p&gt;
&lt;p&gt;Yes I tried it but it then directly crashes with invalid parameter error. And I mean continious advertising is not realy what I want. I would like to put the BLE for 180 s in advertising and then overtake the full timeslot if possible for ESB.
The other flags I will check thanks for the hint.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unstable timeslot with esb and ble concurrently</title><link>https://devzone.nordicsemi.com/thread/84362?ContentTypeID=1</link><pubDate>Mon, 24 Apr 2017 15:00:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:24a78fcd-fbc0-4bc4-8820-aaabcf1debfc</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Have you tried to to simply keep the BLE advertising continuously ? Simply set APP_ADV_TIMEOUT_IN_SECONDS = 0 and  advdata.flags              = BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE;
should allow the device to advertise in BLE without timeout.&lt;/p&gt;
&lt;p&gt;5 minutes timeout doesn&amp;#39;t ring any bell for me. It could be smth else. Please make sure you check that the device reset or not. You can detect it simply by printing out something on UART when you starting up or blink LED.&lt;/p&gt;
&lt;p&gt;Please try to debug and find what exactly cause the timeslot to be skipped, check if it&amp;#39;s just simply the NRF_EVT_RADIO_BLOCKED or NRF_EVT_RADIO_CANCELED or anything else.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unstable timeslot with esb and ble concurrently</title><link>https://devzone.nordicsemi.com/thread/84360?ContentTypeID=1</link><pubDate>Mon, 24 Apr 2017 07:46:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:399e96cb-8127-4690-926c-c32508c45df3</guid><dc:creator>Constantin</dc:creator><description>&lt;p&gt;I restart with:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;uint32_t err_code;

switch (ble_adv_evt)
{
    case BLE_ADV_EVT_FAST:
    	NRF_LOG_INFO(&amp;quot;Fast advertising\r\n&amp;quot;);
        err_code = bsp_indication_set(BSP_INDICATE_ADVERTISING);
        APP_ERROR_CHECK(err_code);
        break;
    case BLE_ADV_EVT_IDLE:
    	//sleep_mode_enter();
    	// Re-start advertising
    	err_code = ble_advertising_start(BLE_ADV_MODE_FAST);
        break;
    default:
        break;
}
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Because if I send the softdevice to sleep mode both BLE and ESB are dying. That&amp;#39;s why I keep the BLE advertising. And after approximiately 5 mins the timeslot is not assigned for 10 seconds and it restarts without a reset. I&amp;#39;ve checked the reset line with an osci, or it has to be a software reset, but the BLE LED keeps on blinking during these 10 seconds.
So from my impression the timeslot is not that stable in my implementation or it has to be something more general.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unstable timeslot with esb and ble concurrently</title><link>https://devzone.nordicsemi.com/thread/84365?ContentTypeID=1</link><pubDate>Fri, 21 Apr 2017 13:23:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:397578ed-9085-428f-8b6d-75cc9f3f07f1</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;what do you mean by &amp;quot;crash of the timeslot&amp;quot; ? There is a chance that the time slot was just rejected (because the softdevice was busy for example) and then was requested again and granted after that ? It&amp;#39;s normal that a timeslot can be missed and then granted after that.&lt;/p&gt;
&lt;p&gt;Could you specify what exactly you meant by &amp;quot;But if I just keep the timeslot DK running with BLE in advertising mode restarting each 10 seconds (blinking LED)&amp;quot; . How do you restart every 10 seconds ? by using the advertising timeout ? or by using extra timer ? Is the issue related to the issue you are discussing &lt;a href="https://devzone.nordicsemi.com/question/129891/sleep-mode-during-multiprotocol-timeslot-api/"&gt;here&lt;/a&gt; ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>