gassensor
I want to interface MQ-135 air quality gas sensor. Sensor have 5V output interface. However my mcu work at 3.3V. I can basically put a voltage divider. But sensor itself is a voltage divider with a specific resistor range at output.
So in this case I need opamp or something like that. But what would be the easiest way interface this 5V to 3.3V.
If you have a reference voltage of (say) 3V, the range your input will see is: -
If you used a 50uA current excitation and a grounded sensor, the range your input will see is: -
With a current excitation the percentage of your 3V reference range used is 95%. With voltage and resistor excitation you only get 63% of the range.
If your reference voltage is lower or higher, the above "range" statements are still true.
Here is an example. An ADC input is directly connected to the sensor. The sensor is fed with 50uA via the PNP transistor. The 50uA is measured across "R" and compared with "V" by the op-amp. The op-amp keeps the current through R at a value that generates a voltage "V" across it. Values could be R=10k and V=0.5V or R=20k and V=1V. Op-amp should be chosen that has close-to-either-rail IO performance like an AD8605 (used many times by me in this same configuration for strain gauge excitation).
Here's a quick DC simulation for 60k and 3k loads: -
Transistor used is BC547C or BC847C for those with good eye-sight.
Note that due to small base currents in the transistor, the current isn't 50uA but 49.846uA with 60kohm load and 49.849uA when loaded at 3kohms. Note also the voltages across the sensor - 2.991V on 60k load and 149.5mV on 3k load.
The signal should be amplified with a low noise 'instrumentation' amplifier to get it's full range signal up the match the range of the ADC, say 5V. Otherwise you are wasting ADC resolution. Someone else can answer the analogue, though I believe that has been answered on electronics.stackexchange already.
My reading of that sensor data sheet is the senor is very slooooooooooow compared to digital technology. It says it's response time for 'T90' < 5 seconds, and 'T99.5 < 40 seconds.
If you could explain exactly what those terms mean, I might be able to be more exact in my answer, but I'll give you the punchline anyway, because it appears to help.
There are purely software techniques for increasing the resolution of an ADC which work by taking multiple samples.
This is not simply taking multiple samples to do normal averaging to reduce error.
Instead, the technique extracts more information about the signal from many samples.
The technique is called "Oversampling and Decimation"
It can be made to work in a couple of ways, and this Atmel application note "AVR121: Enhancing ADC resolution by oversampling" explains how. It has a worked example, which looks very similar to your scenario.
A Mental model
It might be easier to think of the real sample having a tiny (less than 1-bit high) saw-tooth signal added. The saw-tooth must not be synchronised with sampling.
Draw a voltage vs time graph, volts up, time right.
Draw a steady, horizontal, real signal. Then draw horizontal lines to represent the measured digital value. The signal will be somewhere between two lines. Then draw a saw-tooth signal, 1 bit high, sitting on top of the horizontal real signal
When the steady signal is close to the next higher digital value, the saw-tooth crosses up above that value 1 higher.
When the steady signal is barely above its measured digital value, the saw-tooth hardly ever crosses up above that value 1 higher.
(I will try to find time to draw this, I can't find the picture by searching)
The maths:
When a real signal 'r' is measured it is rounded down to the nearest digital value by the ADC. Let's call that rounding down floor(), and let's say how many bits the ADC measures.
So, a signal r is measured by a 10-bit ADC as a number, call it 's', = floor(r, 10)
Let's call the amplitude of the saw-tooth at any instant t, we don't know what it is, except it is less than the voltage between any ADC value, and the next. For a 10-bit ADC measuring 0-5V, the maximum value of t is 5V/1023, or roughly 5mV.
Now let's think about a long stream of values from the ADC. Remember, it is measuring r with the saw-tooth voltage t added.
Then each time the ADC samples, the answer is the real signal r and the saw-tooth. s = floor(r+t, 10)
The saw-tooth will sometimes push s 1 bit higher than r alone would be measured because the saw-tooth happens to be big enough when added.
If the signal r is almost at the digital value r+1, then a lot of the samples with t added in will be measured as s = r+1. If the real-signal r is barely above r, then almost all will be at s = r
This is key: when r is very close to s+1 (but just under it), t pushes lots of ADC conversions high enough to measure as s+1 when r is far below s+1 (very close to s), t pushes very few ADC conversions high enough to measure as s+1, so most are still measured as s
So, if we add up a long sequence of ADC values, s, the ratio of s=r values to s=r+1 will give us more information. The ratio of s=r to s=r+1 tells us the value of r in that 1-bit, 5mV voltage range. The saw-tooth (not synchronised with sampling the signal) extracts that information.
The nice part is we don't need to count the ratio of s to s+1. We just add the sample values, and shift right (to get the correct number of bits). The number of +1's is added in, and that is the right ratio.
Now here is the sneaky part.
Random (Gaussian) noise acts in a very similar way to the saw-tooth signal. It gets added anyway, for free. We don't need to do anything except add a sequence of values. The only downside is noise takes more samples than a saw-tooth. In this case, I don't think it matters.
Summary: add enough samples then the low-res ADC acts like a higher resolution ADC.
How effective is this?
That document has a table, but let's pick a few, using a 10 bit ADC (e.g. an ATmega328P)
11 bits - 4X samples
12 bits - 16X samples
13 bits - 64X samples
14 bits - 256X samples
By adding 256 samples, a ATmega328P's 10bit ADC provides 14 bits of resolution.
An ordinary Arduino, samples at roughly 9.6kHz, and that sensor looks so slooooow, it shouldn't have changed much while sampling.
TI's application note "Oversampling Techniques using the TMS320C24x Family", AKA spra461.pdf has some useful diagrams and explanation of superimposing a triangle wave, which increases resolution with fewer over-samples that noise.
Side note: If you are confident with programming, consider getting an ST Micro Nuceleo. They are mbed's, so the software is instantly available from mbed's cloud. ST's Nucleo's cost about 8GBP. They have one or more 12bit ADC's built in. Most have 1M samples/second ADC's, and the STM32F302 and STM32F334 have 5M sample/second ADCs. The extra 2 bits mean they only need sample and add 16 values. So they could provide 14bit resolution at a higher sample rate than the raw ATmega328 could provide 10 bits. This isn't an advert for ST. Any MCU with a faster higher-resolution ADC will perform in a similar way.
Punchline
That sensor specification seems to be so slow, that by using this purely software technique, the 10bit ADC on the ATmega328P will provide 14bit resolution. In fact, it could provide 15bit resolution by adding more samples.
Best Answer
From the MQ-135 Datasheet you can see that the sensing resistance is 2 kΩ to 20 kΩ and the test circuit shown is really just forming a voltage divider from the 5 V supply with the lower end being RL. If you select RL as 3.3 kΩ when the sensor resistance is 2 kΩ the output will be 3.113 V and when it is 20 kΩ it will be 708 mV which you can directly connect to your ADC.
Sometimes when selecting divider resistors I find it convenient to use an on-line potential divider calculator to play around with the values. If your microcontroller has an internal bandgap reference for the ADC you may also want to consider using that and adjusting the resistor value so the maximum output voltage is around that value.