You are here: start » projects » esp

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
projects:esp [2015/02/04 18:09] – darronprojects:esp [2017/01/12 22:44] (current) – external edit 127.0.0.1
Line 10: Line 10:
 The three devices are a Microchip MCP23016 digital I/O expander, NXP PCF8591 ADC/DAC and Microchip 24LC512 EEPROM. The three devices are a Microchip MCP23016 digital I/O expander, NXP PCF8591 ADC/DAC and Microchip 24LC512 EEPROM.
  
-These were chosen because they add useful capabilities to the ESP-01 or RPi and all three are available in DIP format from CPC in the United Kingdom.+These were chosen because they add useful interfacing and logging capabilities to the ESP-01 or RPi and all three are available in DIP format from CPC in the United Kingdom.
  
 +You may also consider adding an I2C RTC to this project and perhaps it shall be updated to include one at a later time.
 === Schematic === === Schematic ===
 +
 +The circuit is expected to be used with either an ESP-01 attached and with its UART connected to a computer to load in scripts, else without an ESP-01 and with the I2C lines connected to a Raspberry Pi.
  
 {{:projects:esp.png?200}} {{:projects:esp.png?200}}
  
 +It should be reasonably simple to construct on stripboard. Tripad board will be used to demonstrate this at a later time. 
 === I2C bus === === I2C bus ===
 +
 +The I2C bus is simple affair with only two lines required for its operation. This is perfect for the ESP-01 module which only has two GPIOs exposed on its header pins. For the Raspberry Pi, there are two I2C buses, but only one is normally available.
  
 ^Address ^Device | ^Address ^Device |
Line 22: Line 28:
 |0x48    |PCF8591| |0x48    |PCF8591|
 |0x50    |24LC512| |0x50    |24LC512|
 +
 +These addresses are the defaults for all three devices with the address pins tied low. Multiple devices of the same type are easily accommodated on the I2C bus but this is not demonstrated here.
  
 Probing the bus on the RPi with [[:tools:i2ctools|I2C Tools]] should reveal the following. Probing the bus on the RPi with [[:tools:i2ctools|I2C Tools]] should reveal the following.
Line 37: Line 45:
 </code> </code>
 === MCP23016 === === MCP23016 ===
 +
 +The MCP23016 is general purpose digital I/O expander. There are more modern and faster varieties of this device but as yet they are not available at CPC.
  
 ^Control ^Register ^Function | ^Control ^Register ^Function |
Line 50: Line 60:
 == ESP-01 NodeMcu == == ESP-01 NodeMcu ==
  
-The equivalent code for NodeMcu LUA on the ESP-01 is.+The NodeMcu firmware can be controlled via a serial console. This can be a manual operation else with a specially written tool for the job: eSPY. 
 + 
 +First we need to fetch eSPY, and then build it. The examples for eSPY on this page come with the eSPY source. 
 +<code> 
 +hg clone http://hg.kewl.org/pub/espy 
 +cd epsy 
 +make 
 +</code> 
 + 
 +This example script blinks an LED attached to the MCP23016 GP0.0 pin.
 <code> <code>
 #!espy /dev/ttyUSB0 #!espy /dev/ttyUSB0
Line 87: Line 106:
 </code> </code>
  
-It is run via eSpy (to be documented).+The script comes with the eSPY application and can be demomstrated like this.
 <code> <code>
 ./mcp.esp ./mcp.esp
-> > > > > > > >> >> >> >> >> >> > > > > > >> >> >> >> >> >> >> on 
 off off
 on on
Line 100: Line 118:
 == RPi == == RPi ==
  
-[[:tools:i2ctools|I2C Tools]] on the RPi can demonstrate the MCP23016 GPIO.+[[:tools:i2ctools|I2C Tools]] on the RPi are used to demonstrate the MCP23016 GPIO.
  
 Here we clear the output latch, set GP0.0 to an output, then set the pin high on the RPi. Here we clear the output latch, set GP0.0 to an output, then set the pin high on the RPi.
Line 109: Line 127:
 </code> </code>
  
-Here on the RPi we set GP1.0 as an input then read it twice. The first read is with GP1.0 taken+Now on the RPi we set GP1.0 as an input then read it twice. The first read is with GP1.0 taken
 low and the second read with GP1.0 taken high. low and the second read with GP1.0 taken high.
 <code> <code>
Line 122: Line 140:
  
 === PCF8591 === === PCF8591 ===
 +
 +The PCF8591 combines 4 analogue inputs and a single analogue output. The inputs can be more than simple input channels but this isn't looked at here.
 +
 ^Control ^Register   ^Function | ^Control ^Register   ^Function |
 |0        | channel 0 |Read ADC 0| |0        | channel 0 |Read ADC 0|
Line 131: Line 152:
 To write to the DAC, we set the control to 64 and write a value between 0 and 255 which represents 0 to VREF volts on the output pin. To write to the DAC, we set the control to 64 and write a value between 0 and 255 which represents 0 to VREF volts on the output pin.
  
-Using [[:tools:i2ctools|I2C Tools]] on the RPi we reset the output to 0V, then raise it to 1.6V and finally 3.3V. +To read from an ADC, we first send a control representing the channel, then we perform two reads. The first read starts the conversion process and the second read fetches the result (this also starts another conversion). 
-<code> + 
-i2cset -y 1 0x48 64 0 +If we are using the DAC, then we must also set the analog OE bit else the DAC will be disabled. 
-i2cset -y 1 0x48 64 128 + 
-i2cset -y 1 0x48 64 255 +== ESP-01 NodeMcu ==
-</code>+
  
-With NodeMcu LUA script, a simple ramp demo can be achieved like this.+A simple ramp demo can be achieved like this with NodeMcu on the ESP-01.
 <code> <code>
 #!espy /dev/ttyUSB0 #!espy /dev/ttyUSB0
Line 168: Line 188:
 </code> </code>
  
-When the script is run with eSPY we can see the DAC output ramp up and a running commentary.+When the script is run with eSPY we can see the DAC output ramp up with a running status.
 <code> <code>
-> > > > > > > >> >> >> >> >> >> > > >>  +0
->> >> >> >> 0+
 10 10
 20 20
Line 181: Line 200:
 </code> </code>
  
-To read from an ADC, we first send a control representing the channel, then we perform two reads. The first read starts the conversion process and the second read fetches the result (this also starts another conversion).+== RPi ==
  
-If we are using the DAC, then we must also set the analog OE bit else the DAC will be disabled.+Using [[:tools:i2ctools|I2C Tools]] on the RPi we reset the output to 0V, then raise it to 1.6V and finally 3.3V. 
 +<code> 
 +i2cset -y 1 0x48 64 0 
 +i2cset -y 1 0x48 64 128 
 +i2cset -y 1 0x48 64 255 
 +</code>
  
 With a potentiometer connected to AIN0 a reading was made on the RPi. With a potentiometer connected to AIN0 a reading was made on the RPi.
Line 199: Line 223:
 I2C EEPROMs have varied addressing schemes. The simplest is a 8-bit address offset, another one where a block selection is made with an I2C address and a byte selection is made with an 8-bit address offset. Yet another, where the I2C address is fixed but it now has a 16-bit address offset and lastly one with both of the last methods combined. I2C EEPROMs have varied addressing schemes. The simplest is a 8-bit address offset, another one where a block selection is made with an I2C address and a byte selection is made with an 8-bit address offset. Yet another, where the I2C address is fixed but it now has a 16-bit address offset and lastly one with both of the last methods combined.
  
-Here we will demonstrate the 24LC512 which uses 16-bit addressing. The addressing byte order is high byte, low byte.+The 24LC512 looked at here uses a fixed I2C address and 16-bit addressing. The addressing byte order is high byte, low byte.
  
-On the RPi we can reset the internal address pointer of the chip to 0 like this. +== ESP-01 NodeMcu ==
-<code> +
-i2cset -y 1 0x50 0 0 +
-</code> +
- +
-To read, we first write an address to start at then begin reading, if we keep reading the address is auto-incremented. +
-<code> +
-i2cset -y 1 0x50 0 0 +
-i2cget -y 1 0x50 +
-0x55 +
-i2cget -y 1 0x50 +
-0xaa +
-</code> +
- +
-If we want to write to a location we send the address followed by the byte of data. +
-<code> +
-i2cset -y 1 0x50 0 0 0xEE i +
-i2cset -y 1 0x50 0 0  +
-i2cget -y 1 0x50 +
-0xee +
-</code>+
  
 On the ESP-01 we can use this NodeMcu LUA script to read the EEPROM. On the ESP-01 we can use this NodeMcu LUA script to read the EEPROM.
Line 258: Line 262:
 </code> </code>
  
-Here the script is executed using eSPY (to be documented).+Here the script is executed using eSPY.
 <code> <code>
 ./eeprom.esp ./eeprom.esp
-> > > > > > > >> >> >> >> >> >> >> >> >> >> >> > > > > 238+238
 </code> </code>
  
-eSPY is still being developed and as yet doesn't filter the LUA prompts from the output.+== RPi == 
 + 
 +On the RPi we can reset the internal address pointer of the chip to 0 like this. 
 +<code> 
 +i2cset -y 1 0x50 0 0 
 +</code> 
 + 
 +To read, we first write an address to start at then begin reading, if we keep reading the address is auto-incremented. 
 +<code> 
 +i2cset -y 1 0x50 0 0 
 +i2cget -y 1 0x50 
 +0x55 
 +i2cget -y 1 0x50 
 +0xaa 
 +</code> 
 + 
 +If we want to write to a location we send the address followed by the byte of data. 
 +<code> 
 +i2cset -y 1 0x50 0 0 0xEE i 
 +i2cset -y 1 0x50 0 0  
 +i2cget -y 1 0x50 
 +0xee 
 +</code>
  
 This overview gives enough information to use the device at a byte level, read the [[#resources|data-sheet]] for the page writing mode of operation. This overview gives enough information to use the device at a byte level, read the [[#resources|data-sheet]] for the page writing mode of operation.
Line 272: Line 298:
 [[http://www.nxp.com/documents/data_sheet/PCF8591.pdf|PCF8591 data-sheet]]\\ [[http://www.nxp.com/documents/data_sheet/PCF8591.pdf|PCF8591 data-sheet]]\\
 [[http://ww1.microchip.com/downloads/en/DeviceDoc/21754M.pdf|24LC512 data-sheet]]\\ [[http://ww1.microchip.com/downloads/en/DeviceDoc/21754M.pdf|24LC512 data-sheet]]\\
 +