<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Bluetooth SIG Qualification Process for nRF52810 in Laird BL651: Can I use QDID 125078</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/54463/bluetooth-sig-qualification-process-for-nrf52810-in-laird-bl651-can-i-use-qdid-125078</link><description>Hi, 
 I have finished developing our product that uses the nRF52810 (in a Laird BL651 module), and the S112 6.1.1 Soft Device. Our design doesn&amp;#39;t use any of the optional BLE Profiles. I am starting the process of getting a Declaration ID for the Bluetooth</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 18 Nov 2019 15:07:15 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/54463/bluetooth-sig-qualification-process-for-nrf52810-in-laird-bl651-can-i-use-qdid-125078" /><item><title>RE: Bluetooth SIG Qualification Process for nRF52810 in Laird BL651: Can I use QDID 125078</title><link>https://devzone.nordicsemi.com/thread/220646?ContentTypeID=1</link><pubDate>Mon, 18 Nov 2019 15:07:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:58f0de69-c399-4819-a6a9-ae3c082f6ade</guid><dc:creator>ketiljo</dc:creator><description>&lt;p&gt;Option 2 would be the easiest. The module is already tested by Laird so there&amp;#39;s no need to re-test the PG-PHY or any other module.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Start the process with &amp;quot;no required testing&amp;quot; and use 125078 as the &amp;quot;&lt;span&gt;Referenced Qualified Design&amp;quot; and go from there.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>