Is advertising timeout max value 65535 on SDK 15?

RE: Is advertising timeout max value 65535 on SDK 15?

GT — Wed, 08 Apr 2020 14:44:34 GMT

Hi Edvin,

Is this bug resolved? I would like to have a advertising timout after disconnect to be 30min. How can I achieve this?

Regards,

Gautham

RE: Is advertising timeout max value 65535 on SDK 15?

masataka hasegawa — Wed, 31 Oct 2018 06:24:08 GMT

Hi,

OK, understood.
We use BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MOD.
and We will change the product spec (advertising timeout to 10min).

Thanks,

RE: Is advertising timeout max value 65535 on SDK 15?

Edvin — Tue, 30 Oct 2018 14:42:57 GMT

hello,

I see. I did some testing now. If you use BLE_GAP_ADV_FLAGS_LE_ONLY_LIMITED_DISC_MODE, the advertising timeout is limited to 180 seconds. If you use BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE you can extend the time, but as it is now, the timeout is limited to 16 bits (65535 units), as you say.

If you need a longer timeout, e.g. 14 minutes, you can use advertising timeout = 0 (never time out), and then use a separate timer to stop the advertisements manually.

Best regards,

Edvin

RE: Is advertising timeout max value 65535 on SDK 15?

masataka hasegawa — Tue, 30 Oct 2018 01:13:01 GMT

Hi Edvin,

Thank you for answer,

p_adv_params->duration(uint16_t) is set by set_adv_mode_slow().
set_adv_mode_slow() is called from ble_advertising_start().
The SDK set slow duration value to p_advertising->adv_params by set_adv_mode_slow().
Finally, p_advertising->adv_params (struct) is set Softdevice directly by sd_ble_gap_adv_set_configure().

So, you mean that the fixing needs to modified both the SDK and the Softdevice.
Is this correct?

Thanks,

RE: Is advertising timeout max value 65535 on SDK 15?

Edvin — Mon, 29 Oct 2018 08:12:07 GMT

Hello,

You seem to be right. The p_adv_params->duration is a uint16_t. I believe that this is a bug, but let me report it to the our SDK team, and see if there is a reason for why it is done like this.

I will keep you updated when I hear something.

In the meantime, I don't see any problems with changing p_adv_params->duration to be a uint32_t variable instead of uint16_t. The project compiles, and the device advertises, so you can assume that this will work, and as I said, I will keep you updated when I hear something from the SDK team.

Best regards,

Edvin