ble_radio_notification_evt_handler_t timeslot API and softdevice

[johnofleek]

I am using the timeslot API and softdevice to advertise two separate types of message. This works well. But I have also used ble_radio_notification_evt_handler_t in an attempt to change the payload of the softdevice advertisement.

Unfortunately through experimentation I have found that ble_radio_notification_evt_handler_t is called on any radio activity. There doesn't appear to be a context.

Any ideas how to run code before or after (just) the softdevice advertises?

I'm using S130 V11 nrf51

Many thanks in advance

John

[FormerMember]

The easiest way to change the advertising data between two advertising events, is to use app_timer/the RTC to run with the same timeout interval as the advertising interval. Since we know that the advertiser will advertise at a given interval, having app_timer/the RTC to update the advertising data with the same interval will make the advertising data change for each advertising event.

[johnofleek]

Roger The radio notification event looks like it's driven - not surprisingly - by all radio events - so in my case we get 10ish events per second from the timeslot , 2ish per second for the soft device advert and some additional ones. You are correct you can select a notification delay and also test to see if the event indicating the start or end of the timeslot. I was hoping the events only occurred for softdevice related radio events but I was wrong. It would be great if we could sync the advertising data with the transmissions - but without a "source" indicator I think we will have to live with the random ish updates. Thanks for the info on the receivers missing data - in our use case it's not the end of the world but it would be good if we weren't adding additional random behaviour (1,2 or 3 transmissions) to the system