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]

Hi ,

I am using a bluetooth peripheral which  have the Custom Service ID and characteristics ID as below.

Service UUID:             56494B01-0100-1000-8000-00805F9B04E1

Characterisitics UUID: 56494B01-0108-1000-8000-00805F9B04E1

Strange enough the 2 bytes which uniquely identify the service or characterisitics are not  at 12 or 13 position (when read in reverse order). They are at 10 and 11 position.

I cant use this peripheral as the Service doesnt get identified by the softdevice.

Could anybody please let me know, how this can be handled. As internally the BLE does all its logic based on the value present at 12th and 13th position.

Will i be able to use the 128 bit as such without going for the short 2 byte ID.

Regards,

Siddiq

[Turbo J]

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

[Siddiq Habib]

I have added this to the list :(

[Siddiq Habib]

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.

[tesc]

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

 

[Siddiq Habib]

Hi Terje,

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

Regards,

Siddiq