Advertisement duration limited to 0xFFFF milliseconds

[sboudaud]

Hi team,

When we set fast advertisement timeout (uint32_t ble_adv_fast_timeout;               /**< Time-out (in units of 10ms) for fast advertising. */) to a value greater than 0xFFFF, the adv duration is actually set to the time = ble_adv_fast_timeout % 0xFFFF.

The duration field in ble_gap_adv_params_t is typed to uint16_t while ble_adv_fast_timeout and ble_adv_slow_timeout are typed uint32_t, this seems a bug.

This question was already asked but no clear answer was responded:

https://devzone.nordicsemi.com/f/nordic-q-a/39879/is-advertising-timeout-max-value-65535-on-sdk-15

I know there is the possibility to use unlimited advertisement (adv set to 0) and use a timer to stop the advertisement, what I want to know if the type difference is a bug and if it is planned to be corrected and if I change the ble_gap_adv_params_t-> duration type to uint32_t the issue will be resolved or there is something else in the softdevice to change?

Thanks.

using: SDK16; SD7.0.1; custom device; custom application; NRF52832

[Susheel Nuguru]

Hi,

unfortunately the internal structures inside the softdevice that store duration are also uint16_t so changing this to uint32_t in the application will not have any results in this. I am not sure why this is limited to unt16_t but for not this seems to be a limitation without a workaround in the app. If you need a longer advertising duration, you can set the duration to 0 (unlimited) and use an internal timer to stop the advertiser after certain duration in the application.

[sboudaud]

Thx for the response.