Timeslot events getting blocked

RE: Timeslot events getting blocked

Susheel Nuguru — Thu, 16 Apr 2020 14:04:57 GMT

thanks for the confirmation TJ

RE: Timeslot events getting blocked

TJ — Thu, 16 Apr 2020 14:01:58 GMT

okay thanks for the help
its working now

RE: Timeslot events getting blocked

Susheel Nuguru — Thu, 16 Apr 2020 14:00:45 GMT

it is normal to get blocked if the request coincides with another already approved future or ongoing timeslot

RE: Timeslot events getting blocked

TJ — Thu, 16 Apr 2020 13:58:39 GMT

Yes its working now
but is it normal to get the timeslot events blocked frequently and the NRF_SOC_EVTS events i see at event handler are 4 (NRF_EVT_RADIO_BLOCKED)

RE: Timeslot events getting blocked

Susheel Nuguru — Thu, 16 Apr 2020 13:49:08 GMT

[quote user="Teja"]I have modified the code and now waiting for the time-slot to end and requesting the new timeslot [/quote]

Did that solve your issue TJ?

RE: Timeslot events getting blocked

TJ — Thu, 16 Apr 2020 06:14:19 GMT

Thanks for the reply.

im usinf the sd s140_nrf52_6.1.0 and nRF15.2 SDK

Currently im using the SD Adv interval as 250ms and Beacon adv as 100ms and 500ms respectively

I have modified the code and now waiting for the time-slot to end and requesting the new timeslot

RE: Timeslot events getting blocked

Susheel Nuguru — Wed, 15 Apr 2020 08:15:37 GMT

[quote user=""]1. while requesting the next event or the earliest does the timeout_us event and length_us have any dependencies on advertising interval? Do we need to change those as per adv interval?[/quote]

If you are using timeslots for advertising, then the length_us should be directly related to the advertising interval. That is the smaller the advertising interval of the other beacon, the less probable is it get length_us fit into the timeslot. Can you for reference show me the numbers for advertising intervals and length_us and timeout_us to get a better picture?

Regarding the NRF_ERROR_BUSY, Which softdevice version are they using? Was any previous sessions closed using sd_radio_session_close and waiting for NRF_EVT_RADIO_SESSION_CLOSED before calling sd_radio_session_open?

I can clearly see that in NRF_EVT_RADIO_BLOCKED, you are closing the session and starting the new session immediately without waiting for NRF_EVT_RADIO_SESSION_CLOSED. You should change your code to start a new session after you get NRF_EVT_RADIO_SESSION_CLOSED since session_closed is an async operation.