Problems with ble_discovery_start() when adding 2 vendor specific UUID

RE: Problems with ble_discovery_start() when adding 2 vendor specific UUID

Hung Bui — Thu, 30 Mar 2017 11:21:45 GMT

@Prasad: Please post your question separately. Please include more information on how you add the uuid, make sure you use the correct uuid_type (the ID value you get after you add the UUID). Also add the result of service discovery when you discovery for that UUID.

RE: Problems with ble_discovery_start() when adding 2 vendor specific UUID

Prasad — Wed, 29 Mar 2017 08:13:16 GMT

I too have 2 vendor specific services and facing a similar problem but, setting vs_uuid_count to 3 doesn't solve the issue for me.

RE: Problems with ble_discovery_start() when adding 2 vendor specific UUID

Petter Myhre — Wed, 28 Sep 2016 10:02:44 GMT

I didn't read the comment. I'm pretty sure that it is incorrect, if you add 2 bases, setting vs_uuid_count to 2 should be sufficient. I'm not sure why it solved your issue though.

RE: Problems with ble_discovery_start() when adding 2 vendor specific UUID

Vehring — Wed, 28 Sep 2016 07:16:02 GMT

I use the SDK 12 and the SoftDevice S130 2.0.1

Setting the vs_uuid_count to 2 was enough to connect both vs uuid peripherals but the second initialized couldn´t be discovered properly as i described above. Changing the order of initialization of the 2 sensors showed that the error was changing between the sensor discoveries too. Setting the vs_uuid_count to 3 solved the problem (which i tried due to the comment from the multilink example "vs_uuid_count has to be 1 bigger than what is actually needed").

RE: Problems with ble_discovery_start() when adding 2 vendor specific UUID

Petter Myhre — Tue, 27 Sep 2016 14:17:04 GMT

It is correct to increase vs_uuid_count, but if you add 2 UUID bases, setting it to 2 should be enough. Increasing it will increase the RAM required by the SoftDevice, have you increased it? What SDK and SoftDevice version are you using?

RE: Problems with ble_discovery_start() when adding 2 vendor specific UUID

Vehring — Mon, 26 Sep 2016 10:43:53 GMT

Maybe i can already give an answer by myself:

I saw this in the multilink example:

// Stack checks first if there are still entries in the table before checking if a vendor
// specific UUID is already in the table thus to be able to call sd_ble_uuid_vs_add several
// times with the same entry, vs_uuid_count has to be 1 bigger than what is actually needed.
    ble_enable_params.common_enable_params.vs_uuid_count = 2;

I did set this value to 2. This allowed me to connect two vs uuid´s but for some reason the second connected get´s wrong discovery data (from the first). Now after changing to 3 the application works with both vs uuid peripherals correctly. I didn´t really understand the comment from the multilink example and i have no time to understand it but i hope this helps others if they have the same issue.