• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 52 subscribers
  • Views 2342 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.

Correlation between characteristic UUID and UUID character value handle

Jeremy Snow
Prodigy 150 points

 I have a couple of questions, i am a little new with this technology. As I was running through the user guide, I noticed that the Btool software uses  UUID characteristic and UUID character handle value. Can anyone explain to me the correlation between them and their purpose?  My second question is in the discover mode for a UUID, the value found in the user guide is "02 0014 F2 FF". The first byte is a 02 and states its a character read only. Is there a table that describes the values of the first byte and what these values produce ( IE read only, write only, enable notification etc... )? Thank for anyone futures responses to my questions.

 

Jeremy Snow

  • 0
    TI__Genius 17975 points

    Think of the UUID as representing the "type" of data that the value represents, and the handle as the "address" of the data in the attribute table. Multiple characteristics can have the same UUID if they represent the same type of data, but in a single device's attribute server every single attribute will have a unique handle.

    The details of the values in the characteristic declaration can be found in the Bluetooth 4.0 core spec (http://bluetooth.com/Specification%20Documents/Core_V40.zip), specifically in Volume 3 (Host volume), Part G (GATT), Section 3.3

  • 0 in reply to Willis1
    Prodigy 150 points

    Thank you very much, that helps me a lot for understanding the correlation between the two.

     

    Jeremy

  • 0 in reply to Willis1
    Intellectual 345 points

    You say the characteristic value handle is the "address" of the data in the attribute table. Can you please tell where this address (e.g. 0x0022) is physically present in the memory of the peripheral device (CODE, XDATA, etc.)?