What are the GATT database/profile Discovery's Limits?

RE: What are the GATT database/profile Discovery's Limits?

run_ar — Fri, 05 Feb 2016 07:58:11 GMT

There are no plans to create a generic discovery module, at least not as far as I know. The current version seems to cover most use cases, except the generic discovery. Note that you can discover 128 bit UUID's using the sd_ble_gattc_attr_info_discover function (introduced in S130/S132 v2).

RE: What are the GATT database/profile Discovery's Limits?

Hieu — Fri, 05 Feb 2016 05:52:38 GMT

After looking at the code I feel the same. Glad to hear your opinion agrees with mine. I am just posting this question to be sure that I would not break anything by modifying it. After all I don't know the inner working of the SoftDevice besides what I could look up in the SDK documentation.

RE: What are the GATT database/profile Discovery's Limits?

Hieu — Fri, 05 Feb 2016 05:42:30 GMT

Yes. I have read over the code for ble_db_discovery module and learned that I need a custom module to make a generic discovery. I actually just finished working on making a modified version of the ble_db_discovery module for that purpose.

On other note, is there plan to introduce a module for generic discovery in future SDK version? Given the design of the ble_db_discovery module and the fact that discovery event only return 16-bit UUID instead of full 128-bit UUID, it feels like the SDK is intended more for application with specific GATT Profiles rather than any generic one.

RE: What are the GATT database/profile Discovery's Limits?

run_ar — Thu, 04 Feb 2016 13:08:34 GMT

These limits are set to limit the amount of memory used by the discovery manager, but they can be increased. However, if you want to create a generic discovery feature, you might want to create your own module as the DB module searches for registered UUID's only.

RE: What are the GATT database/profile Discovery's Limits?

shibshab — Thu, 04 Feb 2016 10:35:47 GMT

I know that BLE_DB_DISCOVERY_MAX_SRV can be updated to the value you need, 2 is just the default value. After looking at the use of BLE_GATT_DB_MAX_CHARS, I don't see why this could not be updated to whatever value is required.