Speed up DB Discovery

RE: Speed up DB Discovery

Andrzej Kuros — Mon, 07 Aug 2017 13:55:04 GMT

You can set connection timing parameters to small values (smallest compilant with BLE spec), do db discovery, and then go back to your desired timing.

You can also give up with SDK's db discovery module and do discovery on your own by directly calling SoftDevice's API functions. See sd_ble_gattc_descriptors_discover and related diagrams. It won't be as easy as using db discovery module, but as you know UUIDs it can be faster.

RE: Speed up DB Discovery

run_ar — Wed, 10 May 2017 10:29:23 GMT

Guess I should add a comment and point out that if you are bond to the peer you, can use service changed indications to get an indication if the attribute table change.

RE: Speed up DB Discovery

RPDben — Wed, 10 May 2017 10:09:22 GMT

Thanks, I will hard code the handles and ensure that there are no updates for the time being.

RE: Speed up DB Discovery

run_ar — Wed, 10 May 2017 09:34:08 GMT

I guess the main problem with hardcoding the handles would be if you do DFU and the attribute table change. e.g. you change SD version like in this case.

RE: Speed up DB Discovery

RPDben — Wed, 10 May 2017 09:11:39 GMT

Hi run,

I think I will have to use the handles directly. I do control all of the devices but it feels slightly wrong hard-coding the handle. I have the connection interval as fast as it can be and it is discovering as soon as it receives the connected event.

RE: Speed up DB Discovery

run_ar — Wed, 10 May 2017 09:04:24 GMT

If you control the device on the other side, and you make sure the attribute table doesn't change. You can use the handles directly without doing service discovery. Other than that I assume you are starting the discovery after receiving the connected event. So as soon as possible. Would be possible to speed things up uf you use a faster connection interval.