DB discovery problem

RE: DB discovery problem

Simonr — Thu, 26 Mar 2020 13:21:01 GMT

It might be that all you need to do is to replace the ble_db_discovery.c and .h files in SDK15.3 with the SDK16.0.0 versions. I can't confirm this though, as there might be some defines and functions that make calls to other files and headers.

Best regards,

Simon

RE: DB discovery problem

hongpal — Thu, 26 Mar 2020 09:01:29 GMT

Ok, I will try to change it.

I just want to change discovery module. However, I don't know what to change.

Can you inform it to me?

RE: DB discovery problem

Simonr — Thu, 26 Mar 2020 07:27:14 GMT

There are quite a few bugs with the discovery module that has been fixed in SDK v.16.0.0 from v.15.3.0. I suggest you either port your project to SDK 16.0.0 or try to implement the changes to the discovery module in your current project.

Please see the release notes of SDK 16 to see the exact updates.

Best regards,

Simon

RE: DB discovery problem

hongpal — Wed, 25 Mar 2020 13:55:59 GMT

I register speed and cadence, heart, and power service from ble_db_discovery_evt_register.

If I try to connect two sensors and start db discovery almost simultaneously , first has speed and cadence services, second has power and speed and cadence.

So I can get BLE_DB_DISCOVERY_COMPLETE of first sensor of service(speed and cadence).

However, I can sometimes get BLE_DB_DISCOVERY_COMPLETE of second sensor of one service(speed and cadence or power)

I always want to get all services.

RE: DB discovery problem

Simonr — Wed, 25 Mar 2020 13:42:20 GMT

[quote user=""]I can not find all services in one sensor for a long time.[/quote]

What do you mean about "long time" here? Are you sometimes able to discover the services, and sometimes not? Could it be that the services you can't find are already found by the central when you call ble_db_discovery_start? Please check out the Database discovery documentation if you haven't already, to see how it should be implemented and used.

Best regards,

Simon