RE: Send different advertising data

mani — Tue, 14 Nov 2017 09:29:57 GMT

Thanks for information sir. it helps me a lot .

RE: Send different advertising data

endnode — Sat, 11 Nov 2017 12:45:48 GMT

Dear mani,

Yes, ble_radio_notification library is the best way if you only perform single broadcasting/advertising activity. Your ble_radio_notification_evt_handler function (which for whatever reason you named fun in your example above) will be called before and after each radio event (which typically consists of at least three Tx packets - each on one adv. channel - and can contain also SCAN_REQ/SCAN_RSP exchange if your ADV_xxx packets are scannable). Simply check boolean parameter of the call and act accordingly (if you want to set the data before the event or once it's done). You can typically call any of these functions which influence advertising packets:

sd_ble_gap_adv_data_set
sd_ble_gap_tx_power_set

Remember that you cannot call other functions which mess up with Soft Device (stack) state machine so don't even think about advertising start/stop or other things. It also has limitation that you cannot change adv. type, interval, timeout, channel mask (which of 3 adv. channels will be used) or any other parameter which can be only set during start. If you need to change these then you basically need to go with another stack or write your own broadcasting layer and avoid BLE stack completely (this is feasible for GAP Broadcaster only and there are examples in nRF5 SDK).