Lecture12:AnalogueToDigitalConversion < Embedded

Tags: view all tags

%SLIDESHOWSTART%
---+ Analogue to Digital Conversion
<h2 align="center">Analogue to Digital Conversion</h2> <h2 align="center">Lecture 12</h2> <h2 align="center">Uli Raich</h2> <h2 align="center">UCC semester 2017/2017</h2>

---++ 
---+ Analogue to Digital Conversion Printed Circuit Boards

In our sensor kit we have 2 different small printed circuit boards

with <b>%BLUE%A%ENDCOLOR%</b>nalogue to %BLUE%<b>D</b>%ENDCOLOR%igital %BLUE%<b>C</b>%ENDCOLOR%onverters (ADCs) on board:<br /><br />
   * The PCF8591 4 channel, 8 bit successive approximation ADC
   * The ADS1115 4 channel 16b bit &Sigma;&Delta; ADC
As you can already see here, different techniques

(successive approximation and &Sigma;&Delta;) are used.

Both devices use the I2C interface and are rather slow.

---++ 
---+ The MCP3004 ADC

In my treasure box I also have a few mcp3004 ADC chips,

which are 10 bit converters providing sampling rates of up to

200ksps (kilo samples per second)

These devices use the SPI interface which will not be explained in this course.

However, you are invited to read the data sheet and to try them.

If you want to play on higher frequency ADCs, then we have a

48 MHz ADC, which is employed in the Hantek 6022BE DSO

(%BLUE%<b>D</b>%ENDCOLOR%igital%BLUE%<b> S</b>%ENDCOLOR%torage %BLUE%<b>O</b>%ENDCOLOR%scilloscope)

Today we have 14 bit ADCs with sampling rate in the GHz range.

---++ 
---+ The PCF8591

Why do we use the PCF8591 ADC, which is the device with

the worst characteristics?<br /><br />
   * Only 8 bit resolution<br /><br />
   * Conversion rate determined by I2C bus frequency (100 kbps)<br /><br />
   * Has four multiplexed input channels<br /><br />
   * Has one 8 bit DAC channel
---++ 
---+ Reasons to use the PCF8591
   * We do not need a high precision or super fast AD conversion,<br />which gives us a resolution of better than 1/2 % full range
   * We are only interested to understand the principle of A to D conversion
   * Having analogue devices on the PCB allowing us <br />to test our setup is and important asset
---++ 
---+ The YL-40 board

<img alt="yl-40.png" height="496" src="%ATTACHURL%/yl-40.png" title="yl-40.png" width="643" />

---++ 
---+ Problems with the YL-40 board

There were 2 problems with the YL-40 board I bought from China:<br /><br />
   * The connection of one end of the thermistor to ground was<br />missing and had to be added by soldering a short connection.
   * The DAC output does not reach Vdd of full scale because <br />the LED connected to it draws too much current.
---++ 
---+ The YL-40 board (2)

<img alt="pcf8591.png" height="249" src="%ATTACHURL%/pcf8591.png" title="pcf8591.png" width="381" />

---++ 
---+ YL-40 corrected

<img alt="pcf8591backcorrected.png" height="243" src="%ATTACHURL%/pcf8591backcorrected.png" title="pcf8591backcorrected.png" width="378" />

---++ 
---+ YL-40 devices

As we can see from the photos and from the circuit diagrams,

the YL-40 has already 3 devices that can be connected

to the PCF8591 inputs through jumpers:<br /><br />
   * a photo resistor (AIN0)
   * a thermistor (AIN1)
   * a potentiometer (AIN3)
AIN2 is unused and can be connected to the DAC output

The potentiometer is particularly useful as any change in resistivity

created when turning it, can immediately be observed on the

ADC values read back from the board.

---++ 
---+ The PCF8591 block diagram

<img alt="pcf8591BlockDiag.png" height="400" src="%ATTACHURL%/pcf8591BlockDiag.png" title="pcf8591BlockDiag.png" width="603" />

---++ 
---+ Successive Approximation

Set the DAC value to Vcc/2 (½ of 0-Vcc interval)

and compare with analogue signal level

If signal level &gt; DAC, set bit 7 to 1 and set DAC level to ¾ Vcc

else set bit 7 to 0 and set DAC level to ¼ Vcc

If signal level &gt; DAC level set bit 6 to 1 and

set DAC level to ½ of   the upper interval

else

set bit 6 to 0 and DAC leve to ½ of lower interval

After 8 approximations we have the converted 8 bit value

<img alt="successiveAppr.png" height="207" src="%ATTACHURL%/successiveAppr.png" title="successiveAppr.png" width="468" />

---++ 
---+ The PCF8591 control byte

<img alt="controlByte.png" height="574" src="%ATTACHURL%/controlByte.png" title="controlByte.png" width="552" />

---++ 
---+ An include file to describe the ADC

<img alt="includeFile.png" height="426" src="%ATTACHURL%/includeFile.png" title="includeFile.png" width="641" />

---++ 
---+ Reading the ADC

Once you have initialized the pigpio library with<br /><br />
   * %BLUE%pigpio_start%ENDCOLOR%
and opened the I2C bus with<br /><br />
   * %BLUE%i2c_open%ENDCOLOR%
you must set the control byte:<br /><br />
   * %BLUE%controlByte =PCF8591_CHANNEL_C | PCF8591_4_SINGLE_ENDED;<br />%ENDCOLOR%%BLUE%i2c_write_byte(pi,handle,controlByte;%ENDCOLOR%
You can read the channel:<br /><br />
   * %BLUE%adcValue=i2c_read_byte(pi,handle);%ENDCOLOR%
---++ 
---+ A bit more C programming

Students typically have problems with<br /><br />
   * Pointers
   * Parameter passing
Therefore I tried to write a few demo programs

to show how to use these correctly

---++ 
---+ Pointers

<img alt="pointer_assignment.png" height="128" src="%ATTACHURL%/pointer_assignment.png" title="pointer_assignment.png" width="587" />

<img alt="pointerVal.png" height="39" src="%ATTACHURL%/pointerVal.png" title="pointerVal.png" width="479" />

---++ 
---+ De-reference pointers

<img alt="dereference.png" height="200" src="%ATTACHURL%/dereference.png" title="dereference.png" width="759" />

<img alt="derefRes.png" height="141" src="%ATTACHURL%/derefRes.png" title="derefRes.png" width="509" />

---++ 
---+ Change in pointer value after the loop

What has happened to the pointer during the loop?

<img alt="pointerLoop.png" height="63" src="%ATTACHURL%/pointerLoop.png" title="pointerLoop.png" width="277" />

It has advanced and now points to the zero string terminator.

Subtracting the old value (hello) from the

new helloPtr value yields the string length

<img alt="strlen.png" height="35" src="%ATTACHURL%/strlen.png" title="strlen.png" width="539" />

---++ 
---+ Printing the remaining string

If instead of printing the character pointed to by the helloPtr wit "%c"

we print the (remaining) string with "%s"

<img alt="stringLoop.png" height="58" src="%ATTACHURL%/stringLoop.png" title="stringLoop.png" width="283" />

this is what we will see:

<img alt="remainRes.png" height="188" src="%ATTACHURL%/remainRes.png" title="remainRes.png" width="119" />

Here is the source code of the example programs:

%ATTACHURL%/pointers.tar.gz

%SLIDESHOWEND%

-- %USERSIG{UliRaich - 2017-11-21}%

---++ Comments

%COMMENT%

Attachments

Topic attachments
I	Attachment	History	Action	Size	Date	Who
png	Screenshot_from_2017-11-14_12-11-57.png	r1	manage	215.0 K	2017-11-21 - 08:06	UnknownUser
png	controlByte.png	r1	manage	33.8 K	2017-11-21 - 08:05	UnknownUser
png	derefRes.png	r1	manage	41.6 K	2017-11-21 - 08:05	UnknownUser
png	dereference.png	r1	manage	42.1 K	2017-11-21 - 08:05	UnknownUser
png	includeFile.png	r1	manage	42.4 K	2017-11-21 - 08:05	UnknownUser
png	pcf8591.png	r1	manage	209.7 K	2017-11-21 - 08:12	UnknownUser
png	pcf8591BlockDiag.png	r1	manage	35.3 K	2017-11-21 - 08:05	UnknownUser
png	pcf8591backcorrected.png	r1	manage	765.1 K	2017-11-21 - 08:12	UnknownUser
png	pointerLoop.png	r1	manage	5.9 K	2017-11-21 - 08:48	UnknownUser
png	pointerVal.png	r1	manage	10.2 K	2017-11-21 - 08:05	UnknownUser
png	pointer_assignment.png	r1	manage	13.4 K	2017-11-21 - 08:05	UnknownUser
gz	pointers.tar.gz	r1	manage	6.9 K	2017-11-23 - 15:48	UnknownUser
png	pot.png	r1	manage	6.7 K	2017-11-21 - 08:05	UnknownUser
png	remain.png	r1	manage	5.6 K	2017-11-21 - 08:06	UnknownUser
png	remainRes.png	r1	manage	4.6 K	2017-11-21 - 08:06	UnknownUser
png	stringLoop.png	r1	manage	5.6 K	2017-11-21 - 08:53	UnknownUser
png	strlen.png	r1	manage	10.1 K	2017-11-21 - 08:06	UnknownUser
png	successiveAppr.png	r1	manage	6.8 K	2017-11-21 - 08:06	UnknownUser
png	updatePtr.png	r1	manage	5.9 K	2017-11-21 - 08:06	UnknownUser
png	yl-40.png	r1	manage	215.0 K	2017-11-21 - 08:07	UnknownUser

Topic revision: r2 - 2017-11-23 - uli