Registering TimeSlot API as SoftDevice Observer

RE: Registering TimeSlot API as SoftDevice Observer

Liam — Fri, 19 Oct 2018 21:05:50 GMT

Great, the first option and link are exactly what I need. Thank you!

RE: Registering TimeSlot API as SoftDevice Observer

Simon — Fri, 19 Oct 2018 07:48:35 GMT

Are you saying that you want to advertise an iBeacon up until connection, and then stop. If so, you need two advertisers simultaneously, one connectable and the iBeacon. This link may help you solve that problem.

However, if you want to start iBeacon advertising after the connection is established (like the multi activity example), you can change the advertisement data by using ble_advertising_advdata_update(..) (SDK v15.2.0).

Please ask, if anything is unclear.

Best regards, Simon

RE: Registering TimeSlot API as SoftDevice Observer

Liam — Thu, 18 Oct 2018 21:24:22 GMT

Thank you for hunting down a solution.

My goal is to advertise an iBeacon at the same time as normal connectivity, until we are connected, and then shut the iBeacon off. The trouble is that the iBeacon drives the advertising interval with 100ms, and we need to optimize power consumption. Additionally, it seems like SDK 15 has made it more difficult to switch advertising data with the removal of ble_advdata_set().

RE: Registering TimeSlot API as SoftDevice Observer

Simon — Thu, 18 Oct 2018 15:10:25 GMT

I haven't been able to make this work yet (also struggling with the observer), tomorrow I will ask somebody with more knowledge about this than me, and hopefully you will get a solution.

However, if your goal is to advertise while in a connection, it is not necessary to use the timeslot API. Look at Runar's answer in this link.

RE: Registering TimeSlot API as SoftDevice Observer

Liam — Wed, 17 Oct 2018 15:35:20 GMT

Thank you Simon

RE: Registering TimeSlot API as SoftDevice Observer

Simon — Wed, 17 Oct 2018 15:20:40 GMT

I will try to provide you with an answer by tomorrow.