• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 51 subscribers
  • Views 494 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.

Question about BLE profile and QDID

Danny Wong
Intellectual 280 points

I actually don't know what the subject should be. Sorry for any misleading first.

I don't have much knowledge on BLE. I bought a development kit and started to do some experiments. Now I am planning to make it as a product. However i found that there are a lot of license issues such as QDID, CE etc

Here are three things I would like to know

1. Does UUID FFFx require a QDID?

2. I develop the project with heart rate profile that is Ti provided but I extend the data length of notification characteristic. Is that still a "standard" heart rate profile?

3. Is there any document describe the data length of each characteristic?

Sorry if my post is duplicated.

Thanks

Danny

  • 0
    TI__Mastermind 34660 points

    Hello.

    1. QDID and UUID's are completely different concepts.  Please see the following certification wiki for more information: http://processors.wiki.ti.com/index.php/How_to_Certify_your_Bluetooth_product

    2. No, you can not modify the length of a bluetooth sig-defined characteristic.

    3. The heart rate service is defined here: https://developer.bluetooth.org/gatt/services/Pages/ServiceViewer.aspx?u=org.bluetooth.service.heart_rate.xml.  This contains a link to the specific heart rate characteristic: https://developer.bluetooth.org/gatt/characteristics/Pages/CharacteristicViewer.aspx?u=org.bluetooth.characteristic.heart_rate_measurement.xml.  This page defines the length and specific bits of the characteristic.

    -Tim

  • 0 in reply to Tim C
    Intellectual 280 points

    Hello TIm,

       Thanks for your reply. It seems if I changed the profile data length, I should get QDID from Bluetooth.org. What if I use an existing profile but the data content is not following the guide. Do i need to get a QDID?

    Regards

    Danny