Ask about time out of advertising duration of slow advertising

RE: Ask about time out of advertising duration of slow advertising

Quangca — Fri, 07 Oct 2022 02:54:53 GMT

Hello Edvin,
Thank you, i will try to do this with your suggestion to test running and it's reliability.

RE: Ask about time out of advertising duration of slow advertising

Edvin — Thu, 06 Oct 2022 12:16:01 GMT

Hello,

Sorry. I read the first post a bit fast. I thought it said it was only an uint16_t.

I see now. I think the reason you are seeing max 65535 units is that APP_ADV_SLOW_DURATION which is passed into ble_advertising_init() takes a ble_advertising_t as an input parameter.

The parameter that holds the timeout here is the ble_advertising_t -> ble_gap_adv_params_t -> duration, which is an uint16_t, which is why you see the capping of (max)uint16_t = 65535.

You can try to change this to an uint32_t, but I have not tested, and I don't know if there are any other limitations, or even a limit in the softdevice saying it can be maximum 65535 units.

Best regards,

Edvin

RE: Ask about time out of advertising duration of slow advertising

Quangca — Thu, 06 Oct 2022 03:43:44 GMT

hello Edvin,

But i see that it is defined by ble_adv_slow_timeout uint32_t not uint16_t Edvin.

I also think about 2 solution you suggest.

RE: Ask about time out of advertising duration of slow advertising

Edvin — Mon, 03 Oct 2022 09:56:51 GMT

Hello,

Since the timeout value is only a uint16_t, you can't set 30 minutes of timeout directly. I have two suggestions:

1: Set the timeout to 0 (basically meaning advertise forever). Then you can set an app_timer to expire after 30 minutes. Use the interrupt from this timer to stop the advertising manually using sd_ble_gap_adv_stop().

2: You can set the timeout to 10 minutes, but you can use the application logic to restart the advertising for another 10 minutes two times, giving you a total of 30 minutes. This will not be noticeable from the scanners. This is probably the easiest option.

Best regards,

Edvin