Issue discovering services using discovery module

RE: Issue discovering services using discovery module

Mario BG — Fri, 01 Feb 2019 14:17:25 GMT

Hi Terje,

What if I am trying to discover a custom service with a 128bit UUID, how can this be achieved?

Thanks,

KR,

Mario

RE: Issue discovering services using discovery module

tesc — Thu, 24 Jan 2019 10:34:19 GMT

Hi,

If it is a 16 bit UUID then it must either be one of the GATT Services specified by the Bluetooth SIG, or any of the 16 Bit UUIDs For Members. 0x108A is neither.

You can use nRF Connect for Desktop or nRF Connect for Mobile to connect to the device and investigate what services it offers (and see the UUIDs of those services.)

Regards,
Terje

RE: Issue discovering services using discovery module

gdutk001 — Fri, 11 Jan 2019 23:33:27 GMT

I apologize for the for the lack of clarity. I do not know the base UUID for the peer device which i am paired with, however i do have access to some one of its services which i would like to discover using the ble_db_discovery_start() function. Shortly after connecting(pairing) i call the ble_db_discovery_start() function which returns the error BLE_DB_DISCOVERY_SRV_NOT_FOUND within its handler. I believe i made a mistake earlier and that the previous code should be the following:

ret_code_t err_code = ble_db_discovery_init(db_disc_handler);
APP_ERROR_CHECK(err_code);

ble_uuid_t BATTERY_SERVICE;
BATTERY_SERVICE.uuid = 0x108A;
BATTERY_SERVICE.type = 1; // since its a 16 bit UUID

uint32_t error_code = ble_db_discovery_evt_register(&BATTERY_SERVICE);
APP_ERROR_CHECK(error_code);

Do i still need to add the SIG UUID using sd_ble_uuid_vs_add() even though i do not have the base UUID of the peer device? Is there a way for me to locate the base UUID of the peer device and add it to the ble stack table with sd_ble_uuid_vs_add() ? Even with the edited code it still returns the same error. Any help would be very much appreciated, thank you.

RE: Issue discovering services using discovery module

tesc — Fri, 11 Jan 2019 16:56:06 GMT

Hi,

It is not clear to me what service UUID you are searching for. The line "BATTERY_SERVICE.type = 2;" could do anything, as the type field is an index into the SoftDevice's table of vendor specific base UUIDs. If you have a look at the ble_app_multilink_central example, you will see an example of a service being initialized and the UUID for the service registered with the database discovery module, in the function ble_lbs_c_init() in ble_lbs_c.c. You will find that the base UUID is registered with the SoftDevice using sd_ble_uuid_vs_add(), and then the UUID type returend is used when registering the UUID with the database discovery module.

Hopefully the above will lead you in the right direction.

Regards,
Terje

RE: Issue discovering services using discovery module

gdutk001 — Fri, 11 Jan 2019 14:59:12 GMT

thank you, i edited the post, do you have any input on how to possibly solve this issue?

thanks

RE: Issue discovering services using discovery module

awneil — Fri, 11 Jan 2019 08:31:20 GMT

How to properly post source code: