<?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>AD conversion values on the NRF52811 installed on the custom board differ from expectations.</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/114053/ad-conversion-values-on-the-nrf52811-installed-on-the-custom-board-differ-from-expectations</link><description>I am using an N52811 QFN32 on a custom board. 
 I modified the SAADC sample as follows and ran it on this board. (3.0V was input to AIN2.) 
 
 
 
 However, p_event-&amp;gt;data.done.p_buffer[] returns a value around 1750, which is about half of what the specification</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 26 Aug 2024 08:50:58 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/114053/ad-conversion-values-on-the-nrf52811-installed-on-the-custom-board-differ-from-expectations" /><item><title>RE: AD conversion values on the NRF52811 installed on the custom board differ from expectations.</title><link>https://devzone.nordicsemi.com/thread/499693?ContentTypeID=1</link><pubDate>Mon, 26 Aug 2024 08:50:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:846e5946-143d-4623-a56c-85b86445fb15</guid><dc:creator>kkuma256</dc:creator><description>&lt;p&gt;I resolved the issue.&lt;/p&gt;
&lt;p&gt;Previously, pin 30 (DEC) was not connected to anything, but after adding a 1&amp;mu;F capacitor according to the reference circuit, I confirmed that the AD behaves as expected.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: AD conversion values on the NRF52811 installed on the custom board differ from expectations.</title><link>https://devzone.nordicsemi.com/thread/499309?ContentTypeID=1</link><pubDate>Thu, 22 Aug 2024 07:57:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a562a455-ba70-48e5-9185-33ed598822cb</guid><dc:creator>kkuma256</dc:creator><description>&lt;blockquote&gt;
&lt;p&gt;&lt;span&gt;What value is SAMPLES_IN_BUFFER?&lt;/span&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;SAMPLES_IN_BUFFER is still set to the sample&amp;#39;s original value of 5.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;span&gt;Don&amp;#39;t see any issues, maybe try channel 1 instead of 0:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;and remove line setting gain (should be 1/6 by default):&lt;/span&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I tried it, but there was no change.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;span&gt;.. and it is physical pin 4 on the QFN32, right? .. just checking ..&lt;/span&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Yes, the input is applied to the pin that is the 4th from the top or the 5th from the bottom among the 8 pins on the left side of the chip.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: AD conversion values on the NRF52811 installed on the custom board differ from expectations.</title><link>https://devzone.nordicsemi.com/thread/499128?ContentTypeID=1</link><pubDate>Tue, 20 Aug 2024 22:49:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:16d6ec72-cc47-45ca-b74a-32db14c8f5d2</guid><dc:creator>hmolesworth</dc:creator><description>&lt;p&gt;What value is SAMPLES_IN_BUFFER? Don&amp;#39;t see any issues, maybe try channel 1 instead of 0:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;    err_code = nrf_drv_saadc_channel_init(1, &amp;amp;channel_config);&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;and remove line setting gain (should be 1/6 by default):&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;    channel_config.gain = NRF_SAADC_GAIN1_6;&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;... and it is physical pin 4 on the QFN32, right? .. just checking ..&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: AD conversion values on the NRF52811 installed on the custom board differ from expectations.</title><link>https://devzone.nordicsemi.com/thread/499124?ContentTypeID=1</link><pubDate>Tue, 20 Aug 2024 20:43:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:654303d7-b1ce-4535-b06d-250d708e4fa2</guid><dc:creator>kkuma256</dc:creator><description>&lt;p&gt;The circuitry around the AIN2 pin is straightforward; it&amp;#39;s directly connected. There are no other circuits, such as amplifiers, in between.&lt;/p&gt;
&lt;p&gt;The DC input comes from a stabilized power supply.&lt;br /&gt;For the 3V AD test, I used two independent stabilized power supplies: one supplied 3.3V to the chip, and the other supplied 3V to AIN2.&lt;/p&gt;
&lt;p&gt;Additionally, I conducted another test using only one stabilized power supply, where both 3.3V to the chip and AIN2 were applied in parallel from the same source, but the results were the same.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: AD conversion values on the NRF52811 installed on the custom board differ from expectations.</title><link>https://devzone.nordicsemi.com/thread/498940?ContentTypeID=1</link><pubDate>Tue, 20 Aug 2024 03:47:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9ab280d5-3ab5-4b57-b8ae-8aa387227eeb</guid><dc:creator>hmolesworth</dc:creator><description>&lt;p&gt;Can you post a snip of the schematic for the AIN2 pin and circuitry connected to the AIN2 pin? Pin 4. Maybe there is something amiss .. need to see how the DC input is connected, and where does the DC input come from?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: AD conversion values on the NRF52811 installed on the custom board differ from expectations.</title><link>https://devzone.nordicsemi.com/thread/498939?ContentTypeID=1</link><pubDate>Tue, 20 Aug 2024 03:05:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ce6a9abe-79eb-41bc-93c3-fb2aea0e9a56</guid><dc:creator>kkuma256</dc:creator><description>&lt;p&gt;Thank you for your response. I don&amp;#39;t have much hardware knowledge, so your help is appreciated.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p style="padding-left:30px;"&gt;AIN2 is P0.04, just checking .. pin 6 on QFN48 and pin 4 on QFN32&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;I apologize for not mentioning earlier, but the chip I am using is in a QFN32 package.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p style="padding-left:30px;"&gt;In case there is a higher impedance (== slower signal rise time) than expected on AIN2, maybe try lengthening the sample time from 10uSecs to 40uSecs (maximum available) to see if it makes a difference:&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;I checked, but there was no change in the values.&lt;/p&gt;
&lt;p&gt;Additionally, for reference, the test is being conducted with a DC input.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: AD conversion values on the NRF52811 installed on the custom board differ from expectations.</title><link>https://devzone.nordicsemi.com/thread/498931?ContentTypeID=1</link><pubDate>Tue, 20 Aug 2024 01:51:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6ae0ac98-51fa-4a12-9c72-f152d29fdda4</guid><dc:creator>hmolesworth</dc:creator><description>&lt;p&gt;AIN2 is P0.04, just checking .. pin 6 on QFN48 and pin 4 on QFN32&lt;/p&gt;
&lt;p&gt;In case there is a higher impedance (== slower signal rise time) than expected on AIN2, maybe try lengthening the sample time from 10uSecs to 40uSecs (maximum available) to see if it makes a difference:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;    channel_config.gain = NRF_SAADC_GAIN1_6;
    channel_config.acq_time = NRF_SAADC_ACQTIME_40US;&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;&amp;quot;&lt;em&gt;The required acquisition time depends on the source (Rsource) resistance. For high source resistance the acquisition time should be increased&lt;/em&gt;&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;TACQ [us] Maximum source resistance [kOhm]
      3                   10
      5                   40
      10                 100
      15                 200
      20                 400
      40                 800&lt;/pre&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>