Is there a down side to setting the sampling time of a SAR ADC as long as possible?What is the purpose of ADC sampling time?Why does ADC conversion time vary?Is there an ADC with a finite bound on measurement timeADC input enable registerOptimal tradeoff between ADC bit depth and sampling rateNucleo F401RE ADC sampling TimeSTM32F20x ADC sampling time/rateSAR ADC has non-linearity around the middle of the rangeThe output of a SAR ADCDoes an SAR ADC discharge the sample capacitor?
I wrote a scene that the majority of my readers loved. How do I get back to that place while writing my new book?
Metal bar on DMM PCB
Why is the relationship between frequency and pitch exponential?
If Boris Johnson were prosecuted and convicted of lying about Brexit, can that be used to cancel Brexit?
Diet Coke or water?
Humans meet a distant alien species. How do they standardize? - Units of Measure
How bad would a partial hash leak be, realistically?
How to connect an offset point symbol to its original position in QGIS?
Chopin: marche funèbre bar 15 impossible place
The term for the person/group a political party aligns themselves with to appear concerned about the general public
What is a simple, physical situation where complex numbers emerge naturally?
Company is asking me to work from overseas, but wants me to take a paycut
Building a road to escape Earth's gravity by making a pyramid on Antartica
Do I include animal companions when calculating difficulty of an encounter?
Can we use the verb "says" for advertisement?
Is it OK to bring delicacies from hometown as tokens of gratitude for an out-of-town interview?
How to detach yourself from a character you're going to kill?
Pros and cons of writing a book review?
What happens to foam insulation board after you pour concrete slab?
How to decline physical affection from a child whose parents are pressuring them?
What are they doing to this poor rocket?
What happens if you do emergency landing on a US base in middle of the ocean?
Personalization conditions switching doesn`t work in Experience Editor (9.1.0, Initial Release)
Convert camelCase and PascalCase to Title Case
Is there a down side to setting the sampling time of a SAR ADC as long as possible?
What is the purpose of ADC sampling time?Why does ADC conversion time vary?Is there an ADC with a finite bound on measurement timeADC input enable registerOptimal tradeoff between ADC bit depth and sampling rateNucleo F401RE ADC sampling TimeSTM32F20x ADC sampling time/rateSAR ADC has non-linearity around the middle of the rangeThe output of a SAR ADCDoes an SAR ADC discharge the sample capacitor?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
$begingroup$
In configuring the sampling time for the internal ADC of a micro-controller (STM32F446RE) to sample the output of a current sensor connected to a PWM controlled motor, the sampling is triggered at 100kHz and I have a window of between 3 and 225 ADC clock cycles (22.5MHz) over which to hold the sampler open - my assumption is that the longer its open the less noise I'm going to see in the results. Is this correct, or is there a point where other factors come into play that would make a more intermediate sampling duration preferable?
adc stm32f4
$endgroup$
add a comment |
$begingroup$
In configuring the sampling time for the internal ADC of a micro-controller (STM32F446RE) to sample the output of a current sensor connected to a PWM controlled motor, the sampling is triggered at 100kHz and I have a window of between 3 and 225 ADC clock cycles (22.5MHz) over which to hold the sampler open - my assumption is that the longer its open the less noise I'm going to see in the results. Is this correct, or is there a point where other factors come into play that would make a more intermediate sampling duration preferable?
adc stm32f4
$endgroup$
add a comment |
$begingroup$
In configuring the sampling time for the internal ADC of a micro-controller (STM32F446RE) to sample the output of a current sensor connected to a PWM controlled motor, the sampling is triggered at 100kHz and I have a window of between 3 and 225 ADC clock cycles (22.5MHz) over which to hold the sampler open - my assumption is that the longer its open the less noise I'm going to see in the results. Is this correct, or is there a point where other factors come into play that would make a more intermediate sampling duration preferable?
adc stm32f4
$endgroup$
In configuring the sampling time for the internal ADC of a micro-controller (STM32F446RE) to sample the output of a current sensor connected to a PWM controlled motor, the sampling is triggered at 100kHz and I have a window of between 3 and 225 ADC clock cycles (22.5MHz) over which to hold the sampler open - my assumption is that the longer its open the less noise I'm going to see in the results. Is this correct, or is there a point where other factors come into play that would make a more intermediate sampling duration preferable?
adc stm32f4
adc stm32f4
asked May 26 at 6:47
norleshnorlesh
219212
219212
add a comment |
add a comment |
4 Answers
4
active
oldest
votes
$begingroup$
That understanding is correct. If your ADC clocks are fast enough so that you can do 225 cycles of acquisition for one sample, then by all means do that.
Things that might go astray, as in basically every ADC, is that you might be loading the voltage source you're observing with your ADC. Of course, charging the ADC sample&hold capacitor for longer might increase the overall loading, but it might also allow the voltage source to catch up. The amount of current into the ADC or the capacity of the sample and hold can typically be read from the datasheet. If in doubt, add a voltage follower.

simulate this circuit – Schematic created using CircuitLab
Adding a voltage follower is also an excellent opportunity to also add an RC low pass filter, if your signal including noise isn't inherently band-limited to below Nyquist frequency anyway. Your noise has (near) infinite bandwidth, but your ADC is only meant to observe $f_textNy=fracf_textsample2=50,textkHz$ of bandwidth! So, filtering out anything above 50 kHz will lead to less noise being aliased into the 50 kHz it observes:

simulate this circuit
The ADC will of course load the voltage divider that RC low pass filter is, but at the low impedance of R1 and the sufficient drive strength of about any opamp, this should be negligible. Upon closer consideration, you'll notice that C1 now smooths out the noise to begin with, so you can then reduce the sampling time (if there's any other reason to do so, for example, need for higher sampling rate because of clocking reasons in the MCU).
Of course, if you know better than I do what frequency ranges you're looking for, you might design a better RC low pass, or even an advanced active filter with online tools (or pen and paper). The 50 kHz cutoff filter I sketched above is probably not a good choice – but it's hard to know a good choice when you don't know at which frequencies to expect signal components! In a PWM system, however, you expect harmonics at every odd multiple of the PWM frequency, whereas you probably mostly care about the current that flows on average over a few PWM cycles through your motor – model how fast the current through your motor is supposed to change, and filter so that this is preserved, but not much higher frequencies.
In general, if your CPU doesn't break a sweat dealing with 100 kS/s, then maybe go for the 50 kHz analog filter (or your signal being bandlimited below that from the start), and do the filtering and decimation in software: a simple FIR filter¹ running on your ARM can have a much steeper frequency response than a reasonably complex analog filter. That's what us radio folks do: analogously filter as much as necessary for the ADC and computation system to deal with the signal, then do the fine-filtering in digital domain, where math is exact (unlike real-world capacitors) and easy, and can be linear-phase.
¹ please don't build a Butterworth "just because it was the first filter I found" – it's not a filter type typical for digital filters, and it's rarely actually what people want, it's just nice because it's flat in passband and easy to build in analog, not in digital)
$endgroup$
add a comment |
$begingroup$
There is no downside to having longest possible sampling period unless it starts to limit the sampling rate.
It also does not result in less noise if the sampling capacitor already gets fully charged in shorter time.
$endgroup$
add a comment |
$begingroup$
Many ADC have about 5pF Csample, and 1Kohm Rseries (plus the sampling FET channel resistance). This is a 5,000 picosecond TAU.
The Neper tells you the improvement of accuracy, given each additional Tau of settling.
Neper = 8.6 dB per Tau, or about 1.6 bits.
For a 16 bit ADC, you need 10 nepers or 10 Tau settling, or 5*10 = 50 nanoseconds.
$endgroup$
add a comment |
$begingroup$
is there a point where other factors come into play that would make a more intermediate sampling duration preferable?
One such reason could be oversampling the signal, which means taking multiple ADC samples and then combining them in software. Depending on the method used for combining/downsampling, this can reduce noise or increase resolution, or both.
For example, taking 4 samples instead of 1 and then just summing them together usually halves the noise level and thus increases resolution by one bit. But a simple summing filter works well only if the noise is white noise, and might actually increase the noise level if there is a high-frequency noise signal present.
In any case, having more samples available to software gives more signal processing freedom, while requiring more CPU power and shorter sampling time.
$endgroup$
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
return StackExchange.using("schematics", function ()
StackExchange.schematics.init();
);
, "cicuitlab");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "135"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2felectronics.stackexchange.com%2fquestions%2f440433%2fis-there-a-down-side-to-setting-the-sampling-time-of-a-sar-adc-as-long-as-possib%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
$begingroup$
That understanding is correct. If your ADC clocks are fast enough so that you can do 225 cycles of acquisition for one sample, then by all means do that.
Things that might go astray, as in basically every ADC, is that you might be loading the voltage source you're observing with your ADC. Of course, charging the ADC sample&hold capacitor for longer might increase the overall loading, but it might also allow the voltage source to catch up. The amount of current into the ADC or the capacity of the sample and hold can typically be read from the datasheet. If in doubt, add a voltage follower.

simulate this circuit – Schematic created using CircuitLab
Adding a voltage follower is also an excellent opportunity to also add an RC low pass filter, if your signal including noise isn't inherently band-limited to below Nyquist frequency anyway. Your noise has (near) infinite bandwidth, but your ADC is only meant to observe $f_textNy=fracf_textsample2=50,textkHz$ of bandwidth! So, filtering out anything above 50 kHz will lead to less noise being aliased into the 50 kHz it observes:

simulate this circuit
The ADC will of course load the voltage divider that RC low pass filter is, but at the low impedance of R1 and the sufficient drive strength of about any opamp, this should be negligible. Upon closer consideration, you'll notice that C1 now smooths out the noise to begin with, so you can then reduce the sampling time (if there's any other reason to do so, for example, need for higher sampling rate because of clocking reasons in the MCU).
Of course, if you know better than I do what frequency ranges you're looking for, you might design a better RC low pass, or even an advanced active filter with online tools (or pen and paper). The 50 kHz cutoff filter I sketched above is probably not a good choice – but it's hard to know a good choice when you don't know at which frequencies to expect signal components! In a PWM system, however, you expect harmonics at every odd multiple of the PWM frequency, whereas you probably mostly care about the current that flows on average over a few PWM cycles through your motor – model how fast the current through your motor is supposed to change, and filter so that this is preserved, but not much higher frequencies.
In general, if your CPU doesn't break a sweat dealing with 100 kS/s, then maybe go for the 50 kHz analog filter (or your signal being bandlimited below that from the start), and do the filtering and decimation in software: a simple FIR filter¹ running on your ARM can have a much steeper frequency response than a reasonably complex analog filter. That's what us radio folks do: analogously filter as much as necessary for the ADC and computation system to deal with the signal, then do the fine-filtering in digital domain, where math is exact (unlike real-world capacitors) and easy, and can be linear-phase.
¹ please don't build a Butterworth "just because it was the first filter I found" – it's not a filter type typical for digital filters, and it's rarely actually what people want, it's just nice because it's flat in passband and easy to build in analog, not in digital)
$endgroup$
add a comment |
$begingroup$
That understanding is correct. If your ADC clocks are fast enough so that you can do 225 cycles of acquisition for one sample, then by all means do that.
Things that might go astray, as in basically every ADC, is that you might be loading the voltage source you're observing with your ADC. Of course, charging the ADC sample&hold capacitor for longer might increase the overall loading, but it might also allow the voltage source to catch up. The amount of current into the ADC or the capacity of the sample and hold can typically be read from the datasheet. If in doubt, add a voltage follower.

simulate this circuit – Schematic created using CircuitLab
Adding a voltage follower is also an excellent opportunity to also add an RC low pass filter, if your signal including noise isn't inherently band-limited to below Nyquist frequency anyway. Your noise has (near) infinite bandwidth, but your ADC is only meant to observe $f_textNy=fracf_textsample2=50,textkHz$ of bandwidth! So, filtering out anything above 50 kHz will lead to less noise being aliased into the 50 kHz it observes:

simulate this circuit
The ADC will of course load the voltage divider that RC low pass filter is, but at the low impedance of R1 and the sufficient drive strength of about any opamp, this should be negligible. Upon closer consideration, you'll notice that C1 now smooths out the noise to begin with, so you can then reduce the sampling time (if there's any other reason to do so, for example, need for higher sampling rate because of clocking reasons in the MCU).
Of course, if you know better than I do what frequency ranges you're looking for, you might design a better RC low pass, or even an advanced active filter with online tools (or pen and paper). The 50 kHz cutoff filter I sketched above is probably not a good choice – but it's hard to know a good choice when you don't know at which frequencies to expect signal components! In a PWM system, however, you expect harmonics at every odd multiple of the PWM frequency, whereas you probably mostly care about the current that flows on average over a few PWM cycles through your motor – model how fast the current through your motor is supposed to change, and filter so that this is preserved, but not much higher frequencies.
In general, if your CPU doesn't break a sweat dealing with 100 kS/s, then maybe go for the 50 kHz analog filter (or your signal being bandlimited below that from the start), and do the filtering and decimation in software: a simple FIR filter¹ running on your ARM can have a much steeper frequency response than a reasonably complex analog filter. That's what us radio folks do: analogously filter as much as necessary for the ADC and computation system to deal with the signal, then do the fine-filtering in digital domain, where math is exact (unlike real-world capacitors) and easy, and can be linear-phase.
¹ please don't build a Butterworth "just because it was the first filter I found" – it's not a filter type typical for digital filters, and it's rarely actually what people want, it's just nice because it's flat in passband and easy to build in analog, not in digital)
$endgroup$
add a comment |
$begingroup$
That understanding is correct. If your ADC clocks are fast enough so that you can do 225 cycles of acquisition for one sample, then by all means do that.
Things that might go astray, as in basically every ADC, is that you might be loading the voltage source you're observing with your ADC. Of course, charging the ADC sample&hold capacitor for longer might increase the overall loading, but it might also allow the voltage source to catch up. The amount of current into the ADC or the capacity of the sample and hold can typically be read from the datasheet. If in doubt, add a voltage follower.

simulate this circuit – Schematic created using CircuitLab
Adding a voltage follower is also an excellent opportunity to also add an RC low pass filter, if your signal including noise isn't inherently band-limited to below Nyquist frequency anyway. Your noise has (near) infinite bandwidth, but your ADC is only meant to observe $f_textNy=fracf_textsample2=50,textkHz$ of bandwidth! So, filtering out anything above 50 kHz will lead to less noise being aliased into the 50 kHz it observes:

simulate this circuit
The ADC will of course load the voltage divider that RC low pass filter is, but at the low impedance of R1 and the sufficient drive strength of about any opamp, this should be negligible. Upon closer consideration, you'll notice that C1 now smooths out the noise to begin with, so you can then reduce the sampling time (if there's any other reason to do so, for example, need for higher sampling rate because of clocking reasons in the MCU).
Of course, if you know better than I do what frequency ranges you're looking for, you might design a better RC low pass, or even an advanced active filter with online tools (or pen and paper). The 50 kHz cutoff filter I sketched above is probably not a good choice – but it's hard to know a good choice when you don't know at which frequencies to expect signal components! In a PWM system, however, you expect harmonics at every odd multiple of the PWM frequency, whereas you probably mostly care about the current that flows on average over a few PWM cycles through your motor – model how fast the current through your motor is supposed to change, and filter so that this is preserved, but not much higher frequencies.
In general, if your CPU doesn't break a sweat dealing with 100 kS/s, then maybe go for the 50 kHz analog filter (or your signal being bandlimited below that from the start), and do the filtering and decimation in software: a simple FIR filter¹ running on your ARM can have a much steeper frequency response than a reasonably complex analog filter. That's what us radio folks do: analogously filter as much as necessary for the ADC and computation system to deal with the signal, then do the fine-filtering in digital domain, where math is exact (unlike real-world capacitors) and easy, and can be linear-phase.
¹ please don't build a Butterworth "just because it was the first filter I found" – it's not a filter type typical for digital filters, and it's rarely actually what people want, it's just nice because it's flat in passband and easy to build in analog, not in digital)
$endgroup$
That understanding is correct. If your ADC clocks are fast enough so that you can do 225 cycles of acquisition for one sample, then by all means do that.
Things that might go astray, as in basically every ADC, is that you might be loading the voltage source you're observing with your ADC. Of course, charging the ADC sample&hold capacitor for longer might increase the overall loading, but it might also allow the voltage source to catch up. The amount of current into the ADC or the capacity of the sample and hold can typically be read from the datasheet. If in doubt, add a voltage follower.

simulate this circuit – Schematic created using CircuitLab
Adding a voltage follower is also an excellent opportunity to also add an RC low pass filter, if your signal including noise isn't inherently band-limited to below Nyquist frequency anyway. Your noise has (near) infinite bandwidth, but your ADC is only meant to observe $f_textNy=fracf_textsample2=50,textkHz$ of bandwidth! So, filtering out anything above 50 kHz will lead to less noise being aliased into the 50 kHz it observes:

simulate this circuit
The ADC will of course load the voltage divider that RC low pass filter is, but at the low impedance of R1 and the sufficient drive strength of about any opamp, this should be negligible. Upon closer consideration, you'll notice that C1 now smooths out the noise to begin with, so you can then reduce the sampling time (if there's any other reason to do so, for example, need for higher sampling rate because of clocking reasons in the MCU).
Of course, if you know better than I do what frequency ranges you're looking for, you might design a better RC low pass, or even an advanced active filter with online tools (or pen and paper). The 50 kHz cutoff filter I sketched above is probably not a good choice – but it's hard to know a good choice when you don't know at which frequencies to expect signal components! In a PWM system, however, you expect harmonics at every odd multiple of the PWM frequency, whereas you probably mostly care about the current that flows on average over a few PWM cycles through your motor – model how fast the current through your motor is supposed to change, and filter so that this is preserved, but not much higher frequencies.
In general, if your CPU doesn't break a sweat dealing with 100 kS/s, then maybe go for the 50 kHz analog filter (or your signal being bandlimited below that from the start), and do the filtering and decimation in software: a simple FIR filter¹ running on your ARM can have a much steeper frequency response than a reasonably complex analog filter. That's what us radio folks do: analogously filter as much as necessary for the ADC and computation system to deal with the signal, then do the fine-filtering in digital domain, where math is exact (unlike real-world capacitors) and easy, and can be linear-phase.
¹ please don't build a Butterworth "just because it was the first filter I found" – it's not a filter type typical for digital filters, and it's rarely actually what people want, it's just nice because it's flat in passband and easy to build in analog, not in digital)
edited May 26 at 12:41
answered May 26 at 10:50
Marcus MüllerMarcus Müller
37k364104
37k364104
add a comment |
add a comment |
$begingroup$
There is no downside to having longest possible sampling period unless it starts to limit the sampling rate.
It also does not result in less noise if the sampling capacitor already gets fully charged in shorter time.
$endgroup$
add a comment |
$begingroup$
There is no downside to having longest possible sampling period unless it starts to limit the sampling rate.
It also does not result in less noise if the sampling capacitor already gets fully charged in shorter time.
$endgroup$
add a comment |
$begingroup$
There is no downside to having longest possible sampling period unless it starts to limit the sampling rate.
It also does not result in less noise if the sampling capacitor already gets fully charged in shorter time.
$endgroup$
There is no downside to having longest possible sampling period unless it starts to limit the sampling rate.
It also does not result in less noise if the sampling capacitor already gets fully charged in shorter time.
answered May 26 at 6:59
JustmeJustme
4,0552615
4,0552615
add a comment |
add a comment |
$begingroup$
Many ADC have about 5pF Csample, and 1Kohm Rseries (plus the sampling FET channel resistance). This is a 5,000 picosecond TAU.
The Neper tells you the improvement of accuracy, given each additional Tau of settling.
Neper = 8.6 dB per Tau, or about 1.6 bits.
For a 16 bit ADC, you need 10 nepers or 10 Tau settling, or 5*10 = 50 nanoseconds.
$endgroup$
add a comment |
$begingroup$
Many ADC have about 5pF Csample, and 1Kohm Rseries (plus the sampling FET channel resistance). This is a 5,000 picosecond TAU.
The Neper tells you the improvement of accuracy, given each additional Tau of settling.
Neper = 8.6 dB per Tau, or about 1.6 bits.
For a 16 bit ADC, you need 10 nepers or 10 Tau settling, or 5*10 = 50 nanoseconds.
$endgroup$
add a comment |
$begingroup$
Many ADC have about 5pF Csample, and 1Kohm Rseries (plus the sampling FET channel resistance). This is a 5,000 picosecond TAU.
The Neper tells you the improvement of accuracy, given each additional Tau of settling.
Neper = 8.6 dB per Tau, or about 1.6 bits.
For a 16 bit ADC, you need 10 nepers or 10 Tau settling, or 5*10 = 50 nanoseconds.
$endgroup$
Many ADC have about 5pF Csample, and 1Kohm Rseries (plus the sampling FET channel resistance). This is a 5,000 picosecond TAU.
The Neper tells you the improvement of accuracy, given each additional Tau of settling.
Neper = 8.6 dB per Tau, or about 1.6 bits.
For a 16 bit ADC, you need 10 nepers or 10 Tau settling, or 5*10 = 50 nanoseconds.
answered May 26 at 7:37
analogsystemsrfanalogsystemsrf
17.3k2823
17.3k2823
add a comment |
add a comment |
$begingroup$
is there a point where other factors come into play that would make a more intermediate sampling duration preferable?
One such reason could be oversampling the signal, which means taking multiple ADC samples and then combining them in software. Depending on the method used for combining/downsampling, this can reduce noise or increase resolution, or both.
For example, taking 4 samples instead of 1 and then just summing them together usually halves the noise level and thus increases resolution by one bit. But a simple summing filter works well only if the noise is white noise, and might actually increase the noise level if there is a high-frequency noise signal present.
In any case, having more samples available to software gives more signal processing freedom, while requiring more CPU power and shorter sampling time.
$endgroup$
add a comment |
$begingroup$
is there a point where other factors come into play that would make a more intermediate sampling duration preferable?
One such reason could be oversampling the signal, which means taking multiple ADC samples and then combining them in software. Depending on the method used for combining/downsampling, this can reduce noise or increase resolution, or both.
For example, taking 4 samples instead of 1 and then just summing them together usually halves the noise level and thus increases resolution by one bit. But a simple summing filter works well only if the noise is white noise, and might actually increase the noise level if there is a high-frequency noise signal present.
In any case, having more samples available to software gives more signal processing freedom, while requiring more CPU power and shorter sampling time.
$endgroup$
add a comment |
$begingroup$
is there a point where other factors come into play that would make a more intermediate sampling duration preferable?
One such reason could be oversampling the signal, which means taking multiple ADC samples and then combining them in software. Depending on the method used for combining/downsampling, this can reduce noise or increase resolution, or both.
For example, taking 4 samples instead of 1 and then just summing them together usually halves the noise level and thus increases resolution by one bit. But a simple summing filter works well only if the noise is white noise, and might actually increase the noise level if there is a high-frequency noise signal present.
In any case, having more samples available to software gives more signal processing freedom, while requiring more CPU power and shorter sampling time.
$endgroup$
is there a point where other factors come into play that would make a more intermediate sampling duration preferable?
One such reason could be oversampling the signal, which means taking multiple ADC samples and then combining them in software. Depending on the method used for combining/downsampling, this can reduce noise or increase resolution, or both.
For example, taking 4 samples instead of 1 and then just summing them together usually halves the noise level and thus increases resolution by one bit. But a simple summing filter works well only if the noise is white noise, and might actually increase the noise level if there is a high-frequency noise signal present.
In any case, having more samples available to software gives more signal processing freedom, while requiring more CPU power and shorter sampling time.
answered May 26 at 17:33
jpajpa
1,686712
1,686712
add a comment |
add a comment |
Thanks for contributing an answer to Electrical Engineering Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
Use MathJax to format equations. MathJax reference.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2felectronics.stackexchange.com%2fquestions%2f440433%2fis-there-a-down-side-to-setting-the-sampling-time-of-a-sar-adc-as-long-as-possib%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown