RE: Custom UUID

Ruth Fuchss — Fri, 10 Feb 2017 08:39:25 GMT

The link to nAN-36 has changed. You can now find it here: nan_36.pdf

RE: Custom UUID

pastisprologue — Fri, 26 Jun 2015 18:49:18 GMT

Hi Epasta,

Nordic's application note nAN-36 is the best guide for implementing custom services and characteristics.

Generally speaking, your service will take the form ABCDxxxx-EF12-3456-7890-ABCDEF123456 as a "base UUID" and then the 16-bits are used to identify the service itself and the characteristics under it. The lowercase x's are where you specify your service/characteristc. For example, I implemented my service as f30900010-4903-4c71-8d16-549852aba4c5 and added a characteristic to it that had a full UUID as f3090011-4903-4c71-8d16-549852taba4c5 using the following code:

#define PIP_UUID_BASE {0xC5, 0xA4, 0xAB, 0x52, 0x98, 0x54, 0x16, 0x8D, 0x71, 0x4C, 0x03, 0x4A, 0x00, 0x00, 0x09, 0xF3}
#define LTES_UUID_SERVICE 0x0010
#define LTES_UUID_DISCIP_CHAR 0x0011

From there, you have to add your register your base uuid with softdevice using:

sd_ble_uuid_vs_add(ble_uuid128_t const *p_vs_uuid, uint8_t *p_uuid_type)

Then add your service using:

sd_ble_gatts_service_add(uint8_t type, ble_uuid_t const *p_uuid, uint16_t *p_handle)

Then add your characteristic using:

sd_ble_gatts_characteristic_add(uint16_t service_handle, ble_gatts_char_md_t const *p_char_md, ble_gatts_attr_t const *p_attr_char_value, ble_gatts_char_handles_t *p_handles)

Hope this helps!

Regards, michael