Radio Timeslot API s132 v5.0.0

RE: Radio Timeslot API s132 v5.0.0

Petter Myhre — Thu, 07 Dec 2017 14:50:07 GMT

So you can set the advertising timeout to 1 second. When you get a timeout you alternate between non connectable beacon and connectable advertising. So you have one second with non connectable beacon, then one second with connectable advertising, and so on. Will this work for you?

You can have less than one second by using a timer. When the timer expires restart advertising and alternate between connectable beacon and connectable advertising.

Timeslot gives you complete control over each single advertising packet.

You will have to figure out what kind of requirements you have.

RE: Radio Timeslot API s132 v5.0.0

Sourabh — Thu, 07 Dec 2017 13:04:39 GMT

I want the device to advertise a non connectable beacon advertisement packet and also advertise connectable packet with nus service for data transfer(the device behaves as a becon and also a connectable device). Can this be implemented without using the timeslot?

RE: Radio Timeslot API s132 v5.0.0

Petter Myhre — Thu, 07 Dec 2017 06:39:09 GMT

I'm assuming you can't fit both in one advertisement (+scan response)?

The easiest way would be to set the advertising timeout to 1 second. Then you can restart advertising with new data every time you get a timeout.

Another option is to use a timer and restart advertising with new data at a certain interval.

RE: Radio Timeslot API s132 v5.0.0

Sourabh — Wed, 06 Dec 2017 21:38:22 GMT

I actually need to advertise becon and data service packets simultaneously, could you suggest the best way to implement this ?

RE: Radio Timeslot API s132 v5.0.0

Petter Myhre — Wed, 06 Dec 2017 12:10:35 GMT

There have been changes to the SoftDevice handler library.

In SDK 14.x you need to use the NRF_SDH_SOC_OBSERVER macro. Similar to:

/* Define a nrf_sdh_soc event observer to receive SoftDevice system events. */ NRF_SDH_SOC_OBSERVER(m_sys_obs, 0, nrf_fstorage_sys_evt_handler, NULL);

Let me know if you get into trouble.