Long 16 bytes characteristic UUID different from the srevice UUID

RE: Long 16 bytes characteristic UUID different from the srevice UUID

Petter Myhre — Thu, 15 Jan 2015 20:03:47 GMT

Great. Could you add the "Master" problem as a separate question and link to this one? Please explain a bit more about what kind of master it is and so on. Thanks. Also, if you find my answer sufficient, please accept it.

RE: Long 16 bytes characteristic UUID different from the srevice UUID

eli — Thu, 15 Jan 2015 19:49:01 GMT

Thanks Petter, I do it because I need backward comparability to my order version devices and applications. In the Slave I can create the topology. I did it the same way you said. But, I can't see those long UUIDs in the Master when I am doing the discovery.

RE: Long 16 bytes characteristic UUID different from the srevice UUID

Petter Myhre — Thu, 15 Jan 2015 14:35:32 GMT

I don't know why you can't use the 2 bytes at indices 12 and 13, but what you want to do should be possible. You just need to add the different base UUIDs, and then use these when you add the charactertistics.

uint32_t        err_code;

ble_uuid128_t   base_uuid2 = {{0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
                                   0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x02}};

ble_uuid_t      ble_uuid2;

err_code = sd_ble_uuid_vs_add(&base_uuid2, &ble_uuid2.type);
APP_ERROR_CHECK(err_code);    

ble_uuid2.uuid           = 0x0000;

and

uint32_t        err_code;

ble_uuid128_t   base_uuid3 = {{0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
                                   0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x03}};

ble_uuid_t      ble_uuid3;

err_code = sd_ble_uuid_vs_add(&base_uuid3, &ble_uuid3.type);
APP_ERROR_CHECK(err_code);    

ble_uuid3.uuid           = 0x0000;