Instead of octets 12-13 of 128-bit UUID can we use octets 1-2

[Sivashankar]

Hi,

I've defined a base uuid 455449424C5545544845524DB87AD700 

For adding the service to the database CUS_SERVICE_UUID = 0x4942 which alters my 12th and 13 octets 

Instead I wan use 0xD700 to alter 1st and 2nd octets.

so I need UUID as follow

PS 455449424C5545544845524DB87AD700

PC-1  455449424C5545544845524DB87AD701 

PC-2  455449424C5545544845524DB87AD702

PC-3  455449424C5545544845524DB87AD703

PC-4  455449424C5545544845524DB87AD704

How can I do this....?

[Einar Thorsrud]

Hi,

Why do you want to change that? This is essentially the same question as in this old post. As the UUID format is standardized, doing it like you suggest means you will need a separate base for each UUID, where the base is incremented by one for each UUID. It will work, but it is a bit odd.

[Sivashankar]

Hi Einar,

Thanks for your response, Is there a way where i can define each PC UUID full 128bit and PS UUID as below. 

#define ETI_SVC_UUID { 0x00, 0xD7, 0x7A, 0xB8, 0x4D, 0x52, \
                                          0x45, 0x48, 0x54, 0x45, 0x55, 0x4C, \
                                          0x42, 0x49, 0x54, 0x45 }
#define ETI_CHAR_SEN1_UUID { 0x01, 0xD7, 0x7A, 0xB8, 0x4D, 0x52, \

                                                        0x45, 0x48, 0x54, 0x45, 0x55, 0x4C, \
                                                        0x42, 0x49, 0x54, 0x45 }
#define ETI_CHAR_COM_NOT_UUID { 0x05, 0xD7, 0x7A, 0xB8, 0x4D, 0x52, \
                                                                 0x45, 0x48, 0x54, 0x45, 0x55, 0x4C, \
                                                                 0x42, 0x49, 0x54, 0x45 }
#define ETI_CHAR_SEN1_SET_UUID { 0x07, 0xD7, 0x7A, 0xB8, 0x4D, 0x52, \
                                                                 0x45, 0x48, 0x54, 0x45, 0x55, 0x4C, \
                                                                 0x42, 0x49, 0x54, 0x45 }
#define ETI_CHAR_INS_SET_UUID { 0x09, 0xD7, 0x7A, 0xB8, 0x4D, 0x52, \
                                                             0x45, 0x48, 0x54, 0x45, 0x55, 0x4C, \
                                                             0x42, 0x49, 0x54, 0x45 }
#define ETI_CHAR_TRM_SET_UUID { 0x0a, 0xD7, 0x7A, 0xB8, 0x4D, 0x52, \
                                                               0x45, 0x48, 0x54, 0x45, 0x55, 0x4C, \
                                                               0x42, 0x49, 0x54, 0x45 }

CS_SERVICE_UUID_128(ETI_SERVICE0, ETI_SVC_UUID),

/* To the BLE transfer */

/* Sensor 1 Reading in Service 1 */
CS_CHAR_UUID_128(ETI_SEN1_READING_CHAR0, // attidx_char
ETI_SEN1_READING_VAL0, // attidx_val
ETI_CHAR_SEN1_UUID, // uuid
PERM(RD, ENABLE) | PERM(NTF, ENABLE), // perm
sizeof(app_env_cs.to_air_buffer), // length
app_env_cs.to_air_buffer, // data
NULL),

[Einar Thorsrud]

No, that is not possible using the SoftDevice. You will need to add each base UUID with sd_ble_uuid_vs_add(), and then refer to each base when you use your UUID's (which will all have different base).