i need to convert adc output to corresponding voltage

Ttelmah · Joined: 11 Mar 2010 Posts: 19327

First:

setup_adc(ADC_CLOCK_INTERNAL);

Look at the chip's data sheet. Is this recommended at your clock rate?. Look at the note under the table "Tad vs. DEVICE OPERATING FREQUENCIES".

Then, _why_.

While it sounds nice to be working with 'volts', it is the sign of idiocy when it comes to a microprocessor.
Chips like the PIC, take an _age_ to do float arithmetic, and the code is bulky. There is rarely any good reason to actually use floating point numbers for something like this. Especially since your accuracy (using the supply as the reference), is unlikely to be better than quite a few mV. Why waste code space, and processor time doing maths that is beyond the accuracy of the hardware?.

Then find out why /1023, is not the right conversion. The chip manufacturers _deliberately_ design the conversion ramp of the ADC, to reduce the maths involved in the conversion. Take advantage of their work.

Remember AN3 is port A4.

Then, you don't actually tell us what is not working in your code?.
Though it won't work 'well', or 'efficiently', it will sort of work.

berlin vince joe V S · Joined: 26 Jun 2015 Posts: 16

actually i was tried to monitor the battery level using pic16f676 and i set the upper cut as 4v and lower cut as 3v

and tried to calculate analogue voltage on that pin using this formula

(Resolution of ADC * System Voltage)/(ADC Reading/Analogue Voltage Measured)

once again thanks for your advice..... Cool

_________________
Thanks

Ttelmah · Joined: 11 Mar 2010 Posts: 19327

OK.

As a bit of 'explanation'. The first part comes as the old 'fence posts versus fence panels' thing. So historically when the first ADC's came out, a 10bit ADC, gave 1024 'levels', but 1023 'risers', and the calculation would be /1023. Then something like 30 years ago, Texas were doing a chip and trying to reduce the work needed on a very early processor. So they deliberately adjusted the way their ADC worked, so it behaved as if it had one more count than it actually 'had', and reached the top count a little below the reference. result they could use /256 (it was an 8bit ADC). It behaved as if it actually counted to 256, but just got to 255 and stopped.
The PIC ADC's generically do this. So the ADC on your PIC behaves as if it actually counted to 1024, but just gets to 1023, 1.5 counts 'below' the reference, voltage and stops. Microchip publish transfer diagrams for their various ADC's that show this. A few of the earliest PIC ADC's, don't do this, but they are 'exotica', like some of the early PIC14's.

On the maths, on your PIC, just the code to perform the float division, used about 40% of the ROM of the chip. One of the key things is to 'think integer', and look at things like (for instance) using an integer 'mV' value, rather than working in float 'volts'. Floats though they 'sound nice', bring lower accuracy (a 4byte FP number, has a 'precision' only equivalent to a 23.5bit integer, yet take at least twice as long to handle as a 32bit integer..). The 'point' about floats is they bring a huge range of values, which can be useful when dealing with things that may cover such a range, but something like volts, from 0 to 5, doesn't have such a range. 'Think integer', should be a motto for people working on embedded systems. Smile

temtronic · Posted: Fri Jun 26, 2015 5:07 am

As Mr T points out floating point is not fast in a PIC!

Here's another way to think about it.

5V = ADC max of 1024 bits. This assumes you have a 1% voltage divider on the battery to PIC ADC input pin.

4v = +- 800 bits (4/5*1000) rough math....it's early here !

3V - +- 600 bits

So you can define a variable as 'battery_4V_level' 800, and one as 'battery_3V_level' 600.

Then it's very fast and easy for the PIC to compare.

You will of course need to use DVM to get a closer value for # of bits=4.00 volts but 800 seems reasonable to me, at least for a starting point.

Jay