How can i get 128bit service uuid from peripheral

RE: How can i get 128bit service uuid from peripheral

FormerMember — Mon, 07 Mar 2016 08:07:19 GMT

You can download S130 v.2.0 from the nRF51822 webapge --> downloads

SDK 11.0.0 will support S130 v2.0, it should be released soon.

RE: How can i get 128bit service uuid from peripheral

roger.k — Sat, 05 Mar 2016 00:14:39 GMT

Thanks a lot. How can I get S130 V2.0.0? I got SDK_10.0.0 which belongs S130 1.0.0. I can see S130 2.0.0 at SDK_11.0.0 which is still alpha version. When will you release official version of S130 2.0.0? I hope your reply.

RE: How can i get 128bit service uuid from peripheral

FormerMember — Fri, 04 Mar 2016 12:46:00 GMT

I have again updated my answer. Did it answer your question?

RE: How can i get 128bit service uuid from peripheral

roger.k — Fri, 04 Mar 2016 01:39:03 GMT

If i know peripheral's BASE UUID, it is possible. But what if i don't know base UUID. I mean I should totally discover all UUID. How can I get 128bits service UUID from peripheral. I hope your reply again.

RE: How can i get 128bit service uuid from peripheral

FormerMember — Wed, 02 Mar 2016 15:22:53 GMT

I have updated my answer to answer your question. Let me know it is still not clear.

RE: How can i get 128bit service uuid from peripheral

roger.k — Wed, 02 Mar 2016 11:39:14 GMT

Thanks for your reply.

But I'm still so confused.

At ble_app_uart_c example code, It uses 128bits service UUID just for advertising data.

Then 'is_uuid_present' function makes it 16bits UUID as using 'sd_ble_uuid_decode' function.

After that this example code uses just 16bits UUID when it discovers UUID.

I think, if 'sd_ble_gattc_primary_services_discover' function is not the only function to discover UUID, there is the other way to discover 128bits UUID.

What I really want to know is "how can I discover all UUID?"

For example, 00000000-0000-1000-8000-00805F9B34FB

I want to get these 128bits.

I hope your reply again.

RE: How can i get 128bit service uuid from peripheral

FormerMember — Mon, 29 Feb 2016 13:47:36 GMT

The ble_app_hrs_c example in the SDK implements the central side of the heart rate profile defined by Bluetooth SIG. Profiles defined by Bluetooth SIG use a 16-bit UUID instead of a 128-bit UUID like what proprietary profiles have to use.

Since ble_app_hrs_c only uses 16-bit UUIDs, it is not the very best example for you. Instead you can look at ble_app_uart_c, it is the central side of the UART example and uses a 128-bit UUID. I think taking a look at it will solve most of your problems.

Update 02.03.16 The function sd_ble_uuid_vs_add(..) is as you know used to add a vendor specific/custom UUID. The out paramter of that function, p_uuid_type, is an index to a table where the base UUID is being stored. As you can see here, the two first indices are reserved, and the index 0x02 and upwards are for custom UUIDS. That way, the UUID type tells which base UUID that is in question.

In sd_ble_gattc_primary_services_discover(..) the parameter ble_uuid_t includes the full service UUID; the base UUID (ble_uuid.type) and the bytes 12 and 13 (ble_uuid.uuid).

Update 04.03.16: If you want to extract an unknown 128-bit UUID, a UUID that has not been added to the system using sd_ble_uuid_vs_add(..), you can use the function sd_ble_gattc_attr_info_discover(..). That function does only exist in S130 v2.0.0 alpha, S130 v2.0.0, and S132 (nRF52)