/filters:background_color(white)/2024-12/BT830_SA.png)
/filters:background_color(white)/2024-12/bl620.png)
/filters:background_color(white)/2025-01/sterling-lwb-wifi-bluetooth-smart-ready-module-base-left.png)
/filters:background_color(white)/s3fs-public/2018-10/wb45nbt-med.jpg)
/filters:background_color(white)/2024-12/tiwi-c-w-bgn-wifi-module-front.png)
/filters:background_color(white)/2024-12/SDC-WB40NBT.png)
/filters:background_color(white)/2024-12/SDC-SSD40NBT.png)
Answer
The responsibility for providing the QDID for a host system is with the provider of the stack that is used on that system. If for instance the host system uses a module that requires the Bluetooth stack to run on that system (e.g. Lairds Sterling-LWB in a Linux platform) the QDID must be provided by the stack vendor who's stack is running on that Linux platform. Challenges might occur when an open-source, community based stack is used. If a module with integrated stack us used (e.g. Lairds BL652) the QDID is provided by the module vendor.