RE: Use of Bluetooth V5 features and remain compatible with no Bluetooth V5 compatible devices

QuentinD — Thu, 14 May 2020 13:37:00 GMT

Great response !

Thank you so much

RE: Use of Bluetooth V5 features and remain compatible with no Bluetooth V5 compatible devices

Jørgen Holmefjord — Thu, 14 May 2020 08:51:41 GMT

Hi,

[quote user=""]I will have to manage 2 advertising packets simultaneously (a normal advertinsing packets and an extended advertinsing packets ) ?[/quote]

You can maintain two separate advertising sets and change between these with sd_ble_gap_adv_set_configure(). It is not possible to change the advertising params while advertising is active, so you have to stop the advertising in order to change to extended advertising. The simplest way to do this is to set the duration parameter to half of the desired advertising interval, and the interval parameter to the same, and change between the two advertising-sets when you receive the BLE_GAP_EVT_ADV_SET_TERMINATED event.

[quote user=""]I would like to add this functionality to the example "ble_thread_dyn_mtd_coap_cli_pca10056_s140". Should I be thinking of something in particular so that BLE and Thread continue to work well simultaneously?[/quote]

In order to maintain the same advertising interval for both legacy and extended advertising, the radio-usage will more than double with this approach. Any activity on BLE will reduce the ability of the OpenThread stack to receive/send data. If you operate the Thread device in MTD mode, without routing capabilities, this should not be an issue but it is something to keep in mind. Especially if you send full packets with extended advertising, this can block the radio for some time. See this page about multiprotocol scheduling and success probability estimations.

Best regards,
Jørgen