This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Broadcast with custom UUID

Hi,

I am trying to figure out how I can advertise with a custom UUID... I know I have to start by adding a base address and then build on top of it. However, when I try to advertise I should indicate the length[Length], followed by type [Service Data], and finally the payload [UUID | data].

but in he standard I only see this working for 16 bits UUIDs... How could I do this with my custom UUID for my product's services?

Sorry for the trouble...

Parents
  • Hi Ulrich,

    Thank you for the tip. I think I can now understand how to do it! :) However, there is a lack in the standard when it comes to this... If you take a look at the Supplement to Bluetooth Core Specification, page 20 (Data types definitions and formats), section 1.11 SERVICE DATA only makes reference to 16 bits UUIDs. And we should not convert them... I have also taken a look at some other examples online and many people use 16 bits UUIDs that are "still not defined" (eg. 0xFFE0). Good to know that with this stack we can use the full 128 bits!

    regards

Reply
  • Hi Ulrich,

    Thank you for the tip. I think I can now understand how to do it! :) However, there is a lack in the standard when it comes to this... If you take a look at the Supplement to Bluetooth Core Specification, page 20 (Data types definitions and formats), section 1.11 SERVICE DATA only makes reference to 16 bits UUIDs. And we should not convert them... I have also taken a look at some other examples online and many people use 16 bits UUIDs that are "still not defined" (eg. 0xFFE0). Good to know that with this stack we can use the full 128 bits!

    regards

Children
Related