shrinking the base UUID for reusing it across several services

Hi

For our BLE product I've prepared a custom profile made out of 4 services.
For each service I've followed the standard procedure:

1. get a random UUID, e.g. cd862c43-9ae2-4d66-b0b7-dd9a0ad338e0
2. isolate a constant part (known as "base UUID"): cd862c43-XXXX-4d66-b0b7-dd9a0ad338e0
3. increment the XXXX part to obtain the UUID for each included attribute
BT_UUID_<SERVICE1> cd860001-9ae2-4d66-b0b7-dd9a0ad338e0
BT_UUID_<CH11> cd860002-9ae2-4d66-b0b7-dd9a0ad338e0
BT_UUID_<CH12> cd860003-9ae2-4d66-b0b7-dd9a0ad338e0

When it comes to manage several services for the same product we get a mess of numbers.

Can I shrink the base UUID for reusing it across all services ?
Something like this cd862c43-XXXX-YYYY-b0b7-dd9a0ad338e0.
In this way I would have this set

BT_UUID_<SERVICE1> cd860001-9ae2-4d66-b0b7-dd9a0ad338e0
BT_UUID_<CH11> cd860002-9ae2-4d66-b0b7-dd9a0ad338e0
BT_UUID_<CH12> cd860003-9ae2-4d66-b0b7-dd9a0ad338e0

BT_UUID_<SERVICE2> cd860001-ff3b-4d66-b0b7-dd9a0ad338e0
BT_UUID_<CH21> cd860002-ff3b-4d66-b0b7-dd9a0ad338e0
BT_UUID_<CH22> cd860003-ff3b-4d66-b0b7-dd9a0ad338e0

BT_UUID_<SERVICE3> cd860001-cd59-4d66-b0b7-dd9a0ad338e0
BT_UUID_<CH31> cd860002-cd59-4d66-b0b7-dd9a0ad338e0
BT_UUID_<CH32> cd860003-cd59-4d66-b0b7-dd9a0ad338e0

Regards

Parents Reply Children
No Data
Related