Custom Service ID and characteristics have 2 byte value not at 12 ant 13 position, rather at 10 and 11 in 16 byte UUID

RE: Custom Service ID and characteristics have 2 byte value not at 12 ant 13 position, rather at 10 and 11 in 16 byte UUID

Siddiq Habib — Sat, 26 May 2018 08:48:31 GMT

Hi Terje,

Thanks for responding. I havent added the Characteristics UUID into the table. I will add the details on Monday.

Regards,

Siddiq

RE: Custom Service ID and characteristics have 2 byte value not at 12 ant 13 position, rather at 10 and 11 in 16 byte UUID

tesc — Fri, 25 May 2018 12:19:14 GMT

Hi,

If I understand things correctly you have added both UUIDs (56490000-0100-1000-8000-00805F9B04E1 and 56490000-0108-1000-8000-00805F9B04E1).

In theory this should work fine, as the ble_uuid_t structure stores the 16 bit uuid (in your case 4B01) and an index to the table of base UUIDs. Together they form a full 128 bit UUID, which is what you use. Can you share your code for us to have a look? (If you cannot share it in public you may open a private ticket and refer to this thread.)

Regards,
Terje

RE: Custom Service ID and characteristics have 2 byte value not at 12 ant 13 position, rather at 10 and 11 in 16 byte UUID

Siddiq Habib — Thu, 24 May 2018 13:52:22 GMT

I am able to get discovery response if i specify value at bit 12 and 13 as the 16bit UUID. But the characteristics ID which i receive from ble_db_discovery_evt_t on BLE_DB_DISCOVERY_COMPLETE event is all 0x0000.

RE: Custom Service ID and characteristics have 2 byte value not at 12 ant 13 position, rather at 10 and 11 in 16 byte UUID

Siddiq Habib — Thu, 24 May 2018 12:05:22 GMT

I have added this to the list :(

RE: Custom Service ID and characteristics have 2 byte value not at 12 ant 13 position, rather at 10 and 11 in 16 byte UUID

Turbo J — Thu, 24 May 2018 11:33:15 GMT

Add the "funny" UUID to the list of vendor specific UUIDs, using sd_ble_uuid_vs_add() API call.