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.

[Roger Clark]

Kristin

Isn't there automatic jitter introduced in when the device advertises, (to prevent collisions) ?

Is there any conflict there ?

BTW. I do something similar (using the App timer) but I only update the advertising packet every 15 seconds, with a 1000ms advertising period.