Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

QDIDs need for Bluetooth declaration using existing hardware with custom DIS/BAS/HID/HOGP on nrf52810/nrf52832 hardware, SDK 15.3 with SoftDevice 112, Ver 6.1.1

To whom it concerns:

I'm a little new to Bluetooth SIGs launch studio and need a little guidance on the correct QDID to utilize for my product using Nordic SDKs.

I have a product based on an existing hardware design (product) with my custom firmware.    The hardware is utilizing either nrf52810 or nrf52832 depending on IC availability.

The firmware is utilizing the SDK 15.3 with SoftDevice 112, version 6.1.1.   The services are the BAS, DIS and HOGP.  I have not changed the services code itself just the HID reports and other functionality not related to the services.

The previous hardware declaration is D043831 using Nordics QDID 115593, declaration ID D040753, dated 2018-07-31.  Because the published date is beyond 3 years I cannot reference it?  Can you renew or update the QDID?  Is there an alternative which handles all the subsystems (listed below), as this QDID does?

  • ATT (Attribute Protocol)
  • GAP (Generic Access Profile)
  • GATT (Generic Attribute Profile)
  • L2CAP (Logical Link Control and Adaption Protocol)
  • LL (Low Energy Link Layer)
  • PROD (Product Type)
  • RFPHY (Low Energy RF PHY)
  • SM (Security Manager Protocol)SUM ICS (Summary ICS)

Additionally, using SD 112, version 6.1.1. are there current QDIDs encompassing the HOGP profile or the individual services such as BAS, DIS, HID and HOGP which  I might include as subsystems with QDIDs?

I appreciate any help in this matter and I look forward to your response,

Thank you.

Parents
  • Hi,

    QDID 115593 is still valid, there are a rule about combining components that are more that 3 years old, but  a valid QDID for an end product that is valid until the specification it is based on is withdrawn.

    Best regards,
    Kaja

  • Hi Kaja,

    Thank you for your answer.  I previously asked about the HOGP profile too.

    Can I use the 44613 profile subsystem (HOGP) in combination and if so do you know if additional qualification testing is required or can it be submitted without testing?

    The answers  might be obvious to somebody who has familiarity with the Bluetooth SIG qualification process for HOGP profiles, but I can use any guidance, answers, pointers or links to learn more you might provide.

    If I search the DevZone for QDID and HOGP there is only one mention for people like to learn from.

    Best Regards and thank you in advance,

    Michael

Reply
  • Hi Kaja,

    Thank you for your answer.  I previously asked about the HOGP profile too.

    Can I use the 44613 profile subsystem (HOGP) in combination and if so do you know if additional qualification testing is required or can it be submitted without testing?

    The answers  might be obvious to somebody who has familiarity with the Bluetooth SIG qualification process for HOGP profiles, but I can use any guidance, answers, pointers or links to learn more you might provide.

    If I search the DevZone for QDID and HOGP there is only one mention for people like to learn from.

    Best Regards and thank you in advance,

    Michael

Children
Related