<?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>nRF52832 (MDBT42Q module) never has correct Services and Characteristics</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/58539/nrf52832-mdbt42q-module-never-has-correct-services-and-characteristics</link><description>This is a strange one. I had a custom PCB that included an MDBT42Q module. After I learned how to program it, it worked fine. I made a slight revision to the PCB, and this time I ordered the module from Digikey. I was able to program it, SoftDevice 6</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Sat, 07 Mar 2020 16:34:27 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/58539/nrf52832-mdbt42q-module-never-has-correct-services-and-characteristics" /><item><title>RE: nRF52832 (MDBT42Q module) never has correct Services and Characteristics</title><link>https://devzone.nordicsemi.com/thread/238645?ContentTypeID=1</link><pubDate>Sat, 07 Mar 2020 16:34:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:042247f9-6f8a-4cf9-8e89-dc2388c683da</guid><dc:creator>mydadisaplumber</dc:creator><description>&lt;p&gt;Hi Simon.&amp;nbsp; I verified the answer because it worked, but I don&amp;#39;t know if it doesn&amp;#39;t show up for you anymore.&amp;nbsp; I&amp;#39;m curious at why this could happen with the bonding.&amp;nbsp; Thanks!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52832 (MDBT42Q module) never has correct Services and Characteristics</title><link>https://devzone.nordicsemi.com/thread/237905?ContentTypeID=1</link><pubDate>Wed, 04 Mar 2020 03:44:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8ad56d36-845e-4ef1-a310-50cc68497892</guid><dc:creator>mydadisaplumber</dc:creator><description>&lt;p&gt;Hi Simon,&lt;/p&gt;
&lt;p&gt;It turned out to be your first suggestion!&amp;nbsp; All I had to do was &amp;quot;forget&amp;quot; the bonding pair to the device, and then it discovered the services as normal!&lt;/p&gt;
&lt;p&gt;However, I don&amp;#39;t understand how that happened.&amp;nbsp; I did have a different device address, serial number, etc... on this new device.&amp;nbsp; Maybe Android looks at some other property of the BLE peripheral to tie it to a previous bond?&amp;nbsp; But why would it then not enumerate the correct BLE services?&lt;/p&gt;
&lt;p&gt;Thanks again!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52832 (MDBT42Q module) never has correct Services and Characteristics</title><link>https://devzone.nordicsemi.com/thread/237615?ContentTypeID=1</link><pubDate>Tue, 03 Mar 2020 08:01:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e046cb37-7973-4fa9-95f6-d96f88e3a91a</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;I believe this could happen due to a couple of things.&lt;/p&gt;
&lt;p&gt;First,&amp;nbsp;does this new module have the same address as your previous PCB? In that case, that might be why you&amp;#39;re not able to see the services on this new device. Please try giving it a new address and/or delete the bonding information on your central (I assume this is a phone).&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Next, have you included the external LF clock in your design. This is not part of most 3rd party modules (including this one) and our examples are configured to use this LF clock. You can make these changes in the sdk_config.h file in order to configure the chip to use the internal LFRC instead as well. (This does not seem like the symptoms of using an incorrect LF clock though, but I thought I&amp;#39;d add it just in case).&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;// &amp;lt;h&amp;gt; Clock - SoftDevice clock configuration

//==========================================================
// &amp;lt;o&amp;gt; NRF_SDH_CLOCK_LF_SRC  - SoftDevice clock source.
 
// &amp;lt;0=&amp;gt; NRF_CLOCK_LF_SRC_RC 
// &amp;lt;1=&amp;gt; NRF_CLOCK_LF_SRC_XTAL 
// &amp;lt;2=&amp;gt; NRF_CLOCK_LF_SRC_SYNTH 

#ifndef NRF_SDH_CLOCK_LF_SRC
#define NRF_SDH_CLOCK_LF_SRC 0
#endif

// &amp;lt;o&amp;gt; NRF_SDH_CLOCK_LF_RC_CTIV - SoftDevice calibration timer interval. 
#ifndef NRF_SDH_CLOCK_LF_RC_CTIV
#define NRF_SDH_CLOCK_LF_RC_CTIV 16
#endif

// &amp;lt;o&amp;gt; NRF_SDH_CLOCK_LF_RC_TEMP_CTIV - SoftDevice calibration timer interval under constant temperature. 
// &amp;lt;i&amp;gt; How often (in number of calibration intervals) the RC oscillator shall be calibrated
// &amp;lt;i&amp;gt;  if the temperature has not changed.

#ifndef NRF_SDH_CLOCK_LF_RC_TEMP_CTIV
#define NRF_SDH_CLOCK_LF_RC_TEMP_CTIV 2
#endif

// &amp;lt;o&amp;gt; NRF_SDH_CLOCK_LF_ACCURACY  - External clock accuracy used in the LL to compute timing.
 
// &amp;lt;0=&amp;gt; NRF_CLOCK_LF_ACCURACY_250_PPM 
// &amp;lt;1=&amp;gt; NRF_CLOCK_LF_ACCURACY_500_PPM 
// &amp;lt;2=&amp;gt; NRF_CLOCK_LF_ACCURACY_150_PPM 
// &amp;lt;3=&amp;gt; NRF_CLOCK_LF_ACCURACY_100_PPM 
// &amp;lt;4=&amp;gt; NRF_CLOCK_LF_ACCURACY_75_PPM 
// &amp;lt;5=&amp;gt; NRF_CLOCK_LF_ACCURACY_50_PPM 
// &amp;lt;6=&amp;gt; NRF_CLOCK_LF_ACCURACY_30_PPM 
// &amp;lt;7=&amp;gt; NRF_CLOCK_LF_ACCURACY_20_PPM 
// &amp;lt;8=&amp;gt; NRF_CLOCK_LF_ACCURACY_10_PPM 
// &amp;lt;9=&amp;gt; NRF_CLOCK_LF_ACCURACY_5_PPM 
// &amp;lt;10=&amp;gt; NRF_CLOCK_LF_ACCURACY_2_PPM 
// &amp;lt;11=&amp;gt; NRF_CLOCK_LF_ACCURACY_1_PPM 

#ifndef NRF_SDH_CLOCK_LF_ACCURACY
#define NRF_SDH_CLOCK_LF_ACCURACY 1
#endif&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>