How to adverting a single one packet and then timeout with latest softdevice s140 6.1.0

RE: How to adverting a single one packet and then timeout with latest softdevice s140 6.1.0

stecla — Mon, 03 Feb 2020 17:53:18 GMT

Could you please share your code? I have a similar issue and would love to have a look for inspiration

RE: How to adverting a single one packet and then timeout with latest softdevice s140 6.1.0

Kenneth — Tue, 09 Oct 2018 12:38:31 GMT

[quote user="teliu"]Could you please let me know if it was expected or a potential issue?[/quote]

In the 6.1.0 release notes there is an entry: "Fixed an issue where the advertiser could send advertising packets beyond the set advertising duration (DRGN-10069). "

I guess this is the root cause of what you are seeing

RE: How to adverting a single one packet and then timeout with latest softdevice s140 6.1.0

Liu Tengfei — Tue, 09 Oct 2018 02:19:11 GMT

Hi Kenneth,

Good news! I've found a pretty better way to achieve my requirement of advertising one time, by setting

max_adv_evts to 1 in ble_gap_adv_params_t before calling sd_ble_gap_adv_set_configure.

By the way, I found a different behavior between softdevice s140 6.0.0 and 6.1.0. When I set adv duration less than the adv interval, for softdevice 6.0.0, it works well and I could receive both adv packet and the scan response. However, for softdevice 6.1.0, I could only receive adv packet but not be able to receive any scan response. This was actually the reason why I could hardly connect to the peripheral with softdevice 6.1.0 before.

Could you please let me know if it was expected or a potential issue?

Thanks,

Tengfei.

RE: How to adverting a single one packet and then timeout with latest softdevice s140 6.1.0

Kenneth — Thu, 04 Oct 2018 07:44:12 GMT

Can you first try this for instance using nRF5 SDKv15.2 and S132v6.1? For instance use hrs or beacon example? If you are not able to make that work I can give it a try here.

Best regards,
Kenneth

RE: How to adverting a single one packet and then timeout with latest softdevice s140 6.1.0

Liu Tengfei — Thu, 04 Oct 2018 03:17:18 GMT

[quote userid="2111" url="~/f/nordic-q-a/39045/how-to-adverting-a-single-one-packet-and-then-timeout-with-latest-softdevice-s140-6-1-0/150946"]@sa BLE_GAP_ADV_TIMEOUT_VALUES. @note The SoftDevice will always complete at least one advertising event even if the duration is set too low. */[/quote]

Hi, I believe that softdevice will immediately send a packet after calling advertising start and wait for an interval to send another one if no timeout reached. This worked well in my application with softdevice s140_6.0.0, I set adv interval to 3s and timeout to 1s, my application only advertise one time and then timeout. However, after I upgrade softdevice to 6.1.0, the advertising did not work at all with the same code and config for advertising module. I could even not be able to discover it. Could you help to verify the issue for the new softdevice 6.1.0?

RE: How to adverting a single one packet and then timeout with latest softdevice s140 6.1.0

Kenneth — Mon, 01 Oct 2018 11:53:08 GMT

Hi,

The longest allowed interval by BLE spec is 10.24 seconds. If you only allow one advertisement channel every 10.24sec by controlling the advertisement mask (ble_gap_ch_mask_t) in adv_params when calling sd_ble_gap_adv_set_configure(), then the average current consumption is very close to the System ON idle current. So not sure how much you will gain by reducing the interval even further. Once you get around ~2uA the life time of even a coin cell battery is more than 10 years.

But to answer your question: I expect in this case that you will need to use radio notification to have full control of when it's advertising, and thereby you can from the application start and stop advertising as you see fit from an app_timer. The advertisement interval can be set to 10.24sec and duration to for instance 1 second if you only want to advertise 1 time. From the description of duration field in ble_gap_adv_params_t:

uint16_t duration; /**< Advertising duration in 10 ms units. When timeout is reached, an event of type @ref BLE_GAP_EVT_ADV_SET_TERMINATED is raised.
@sa BLE_GAP_ADV_TIMEOUT_VALUES. @note The SoftDevice will always complete at least one advertising event even if the duration is set too low. */

Best regards,
Kenneth