SD140 6.0.0 Scan Timeout in multiples of whole seconds

[Luca Lattanzio]

Hi everybody,

I am running into the same issue as described in this post:

https://devzone.nordicsemi.com/f/nordic-q-a/50386/ble-scan-timeout-always-in-multiple-of-second

Summarizing the discussion in this post, the proper solution would be to upgrade my Softdevice to a later version. Unfortunately, I do not have time for that. So my question is: is there any known fix for this in S140 6.0.0? In my solution, I would like to use a scan timeout of less than a second.

From the documentation, I found that the minimum timeout specified is 1x10ms (https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.s140.api.v6.0.0%2Fstructble__gap__scan__params__t.html).

A bit of background information: I am trying to implement a time synchronization mechanism that is based on timestamps which are propagated in advertising packets. For power consumption reasons, I want to only turn on the scanner if it's really needed needed (as I know pretty precisely when to listen for synchronization packets).

Thanks in advance and best regards

Luca

[Einar Thorsrud]

Hi Luca,

Summarizing the discussion in this post, the proper solution would be to upgrade my Softdevice to a later version.

I was never able to reproduce the reported issue in the thread you linked to, unfortunately. Updating to S140 6.1.1 was reported to fix the issue, as you noted.

Unfortunately, I do not have time for that.

I am not able to suggest other workarounds whiteout understanding the issue, unfortunately. Note that updating form 6.0.0 to 6.1.1 is a minor update, with trivial  API changes. It should be enough to replace the SoftDevice headers and rebuild your application, in addition to flashing the updated SoftDevice hex file.