<?xml-stylesheet type="text/xsl" href="https://e2e.ti.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/"><channel><title>ADC Accuracy Part 1: Is accuracy different from resolution?</title><link>/blogs_/archives/b/precisionhub/posts/adc-accuracy-part-1-is-accuracy-different-from-resolution</link><description>This technical article was updated on July 23, 2020.
In talking to system designers using analog-to-digital converters (ADCs), one of the most common questions that I hear is: 

&amp;ldquo;Is your 16-bit ADC also 16-bit accurate?&amp;rdquo;
The answer to thi...</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><item><title>RE: ADC Accuracy Part 1: Is accuracy different from resolution?</title><link>https://e2e.ti.com/blogs_/archives/b/precisionhub/posts/adc-accuracy-part-1-is-accuracy-different-from-resolution</link><pubDate>Sat, 07 Jan 2023 20:40:17 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:0ebe116c-0a1b-49cc-91c7-0cdb0e9efa09</guid><dc:creator>Abhilash Naragund</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;Hello Everyone, I would like to ask you about the selection of resolution of ADC.&amp;nbsp;Do you have any calculation to arrive at n- bit ADC? If so could you share the methodology please? I am working on the measurement of strain/stress/force calculations using Strain gauge sensor project. My idea of connecting: Strain gauge diagonal bridge (I have -0.49mV for maximum loading condition as an output from the strain gauge bridge) &amp;gt; Instrumentation Amplifier &amp;gt; ADC of high resolution so that it can accept the amplified analog voltage(Example:ADS1256) &amp;gt; WiFi enabled Microcontroller.&amp;nbsp; Could you please guide me in this regard further? Your feedback will really helps me in proceeding further with my project.&amp;nbsp; If further clarifications, I am happy to contact you over the Teams meeting. My mail ID: abhilash.naragund@student.uni-siegen.de&lt;/p&gt;&lt;img src="https://e2e.ti.com/aggbug?PostID=666522&amp;AppID=930&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>RE: ADC Accuracy Part 1: Is accuracy different from resolution?</title><link>https://e2e.ti.com/blogs_/archives/b/precisionhub/posts/adc-accuracy-part-1-is-accuracy-different-from-resolution</link><pubDate>Mon, 24 Apr 2017 19:26:15 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:0ebe116c-0a1b-49cc-91c7-0cdb0e9efa09</guid><dc:creator>Jim Gavin</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;When specifying accuracy, should ADC accuracy be specified in bits, counts or volts (each with a tolerance)? It seems that specifying ADC accuracy in bits is actually specifying a resolution until you add a tolerance. For example, 16-bit ± 2 LSB seems to specify both resolution and accuracy, which both ultimately translate to voltages for a given application.&lt;/p&gt;
&lt;img src="https://e2e.ti.com/aggbug?PostID=666522&amp;AppID=930&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>RE: ADC Accuracy Part 1: Is accuracy different from resolution?</title><link>https://e2e.ti.com/blogs_/archives/b/precisionhub/posts/adc-accuracy-part-1-is-accuracy-different-from-resolution</link><pubDate>Sat, 01 Nov 2014 00:58:19 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:0ebe116c-0a1b-49cc-91c7-0cdb0e9efa09</guid><dc:creator>Vinay Agarwal</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;In order to define the ADC resolution, the entire transfer function of the ADC has to be accounted for and not a limited section of the transfer function. If you assume a perfectly ideal ADC, then in your example a change in 10mV will not always change the digital output code by 1 count (change from 0.895V to 0.905V will not result in output change), whereas a change in 1V will always change output code by 1 count.&lt;/p&gt;
&lt;p&gt;I agree to you that the precision of the ADC is dependent on the offset, gain and non-linearity errors which is explained in more details in the part-II of this series (&lt;a rel="nofollow" target="_new" href="http://e2e.ti.com/blogs_/b/precisionhub/archive/2014/10/14/adc-accuracy-part-2-total-unadjusted-error-explained.aspx"&gt;e2e.ti.com/.../adc-accuracy-part-2-total-unadjusted-error-explained.aspx&lt;/a&gt;).&lt;/p&gt;
&lt;p&gt;You are right about the definition of SINAD being in dB units. This is how the SINAD is specified in ADC datasheets, as I mentioned in the post above. So, if the SINAD (in dB) as specified in ADC datasheets is used in the formula, then ENOB can be calculated. &lt;/p&gt;
&lt;p&gt;In sigma-deltas, the averaging can result in higher resolution but this post is based on Nyquist-sampled ADCs which is the basis for the formula for ENOB mentioned in equation 2. However, the basic conceptual difference between accuracy and resolution is applicable to both nyquist-sampled as well as oversampled ADCs.&lt;/p&gt;
&lt;img src="https://e2e.ti.com/aggbug?PostID=666522&amp;AppID=930&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>RE: ADC Accuracy Part 1: Is accuracy different from resolution?</title><link>https://e2e.ti.com/blogs_/archives/b/precisionhub/posts/adc-accuracy-part-1-is-accuracy-different-from-resolution</link><pubDate>Wed, 29 Oct 2014 15:42:25 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:0ebe116c-0a1b-49cc-91c7-0cdb0e9efa09</guid><dc:creator>tilmann</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;I would like more precise definitions. &lt;/p&gt;
&lt;p&gt;So the resolution is not &amp;quot; the smallest change in the value of an input signal that changes the value of the digital output by one count&amp;quot; but (for linear ADCs) the average value achieved by input signal range divided &amp;nbsp;by number of steps inside this range. An example: on an ideal 4-bit ADC with a range of 16 V the resolution is 1 V, but you can see a change of the value of the digital output by changing the input only from 0.495 V to 0.505 V, a change of only10 mV.&lt;/p&gt;
&lt;p&gt;The missing precision of the transfer function of an ADC is dependent on offset, slope, differential and integral nonlinearity, not on noise. You can use this feature by adding noise to the signal to upgrade the resolution of an (low-resolution) ADC!&lt;/p&gt;
&lt;p&gt;The definition of ENOB does not contain any dimensions: ENOB is a dimensionless value, ok. If SINAD is treated as dimensionless then a signal of 1 V with a noise&amp;amp;distortion of 10 mV (what is the amplitude of a sum of statistical independent signals like noise and distortion?) would result in a SINAD of 100 resulting in wrong values. Usually &amp;nbsp;SINAD is given in dB as well as the values 1.76 and 6.02, so it is a logarithmic value: for voltages 20 time the decadic logarithm of signal divided by &amp;quot;noise and distortion&amp;quot; (1 Bel is a factor of 10 for powers).&lt;/p&gt;
&lt;p&gt;In a system the achieved resolution is well dependent from software. As example you can see on sigma-delta ADCs that the software algorithms (averaging, filtering) can influence or even define the resolution of the ADC.&lt;/p&gt;
&lt;img src="https://e2e.ti.com/aggbug?PostID=666522&amp;AppID=930&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item></channel></rss>