• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 51 subscribers
  • Views 1130 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

BLE Stack - gatt_uuid.h vs bluetooth assigned numbers

John Pelochino
Prodigy 125 points

I am just getting into ble and trying to understand the stack and how the communication functions. I'm a bit confused about a mismatch of the UUIDs in the gatt_uuid.h and online bluetooth assigned numbers I found (https://www.bluetooth.org/Technical/AssignedNumbers/home.htm). The generic and higher level UUIDs are consistent, but the specific UUIDs appear different; my application will definitely use some of these (ie battery level) and would be great to use the standard UUIDs for interoperability. Am I misunderstanding/misreading something or fundamentally confused? Am I looking at the right numbers? Can I trust gatt_uuid.h?

For instance:

battery service uuid: 0xA000 (gatt_uuid.h) vs. 0x180F (online)

stack version: 1.3 (is this most recent?)

Thanks - John

  • 0
    TI__Mastermind 23440 points

    Hi John,

    No, please don't trust gatt_uuid.h for service and characteristic UUIDs. The unit UUIDs should be correct. Look at the official bluetooth website or look in header files for the implemented services the Projects/ble/Profiles directory for service and characteristic UUIDs.

    Best regards,
    Aslak