(r5) HardwareAccessAndMicropython < AFNOG

Tags: view all tags

%SLIDESHOWSTART%
---+ Setting up and !IoT
<h2 align="center">Session 2: Micropython and<br /><br />Hardware access<br /><br />Uli Raich<br /><br />Formally CERN, Geneva, Switzerland</h2>
---+ The !WeMos D1 mini CPU card
| <img alt="esp8266.png" height="332" src="%ATTACHURL%/esp8266.png" title="esp8266.png" width="380" /> | <img alt="wemosEsp32.png" height="455" src="%ATTACHURL%/wemosEsp32.png" title="wemosEsp32.png" width="351" /> |
| <p> *ESP8266* </p> <p>cost: 2.21 Euros</p> | <p>ESP32</p> <p>cost: 4.1o Euros</p> |
---++ 
---+ CPU Pinout
| <img alt="esp8266Pinout.png" height="376" src="%ATTACHURL%/esp8266Pinout.png" title="esp8266Pinout.png" width="316" /> | <img alt="esp32Pinout-v2.png" height="327" src="%ATTACHURL%/esp32Pinout-v2.png" title="esp32Pinout-v2.png" width="250" /> |
| ESP8266 | ESP32 |
Please note: The pin numbers IOxx on the ESP32 correspond

to the GPIO pin numbers

The pins in the white fields go to the !WeMos D1 mini bus

and are also available on the ESP8266

The other pins are only accessible on the ESP32 CPU card

The pin numbers Dx do not correspond to GPIO pin numbers!

Please refer to the next slide for correspondence

---++ 
---+ CPU pinouts for reference

<img alt="cpuPinouts.png" height="535" src="%ATTACHURL%/cpuPinouts.png" title="cpuPinouts.png" width="459" />

---++ 
---+ Meaning of pins on ESP8266

| <ul> <li>GPIO: General Purpose Input Output. <br />Drives a single digital line which <br />can be programmed input or output</li> </ul><ul> <li>SCL/SDA: The !I2C bus:a 2 wire bus <br />interfacing sensors or actuators to the CPU<br /><br /></li> <li>SCL,MISO,MOSI,SS: SPI<br />the Serial Peripheral Interface. <br />Used fast communication with external device</li> </ul> | <img alt="esp8266PinMeaning.png" height="358" src="%ATTACHURL%/esp8266PinMeaning.png" title="esp8266PinMeaning.png" width="400" /> |

---++ 
---+ Meaning of pins on ESP32

%ATTACHURL%/esp32-pinout-chip-ESP-WROOM-32.png

---++ 
---+ How to program the processor

| <img alt="esp8266Programming.png" src="%ATTACHURL%/esp8266Programming.png" title="esp8266Programming.png" /> | Several development tools are available:<br /> <ul> <li>ESP_IDF: The official Espressif development tool.<br />Includes a gcc compiler for the ESP8266 and the ESP32</li> </ul><p>Please see:<br /> [[https://docs.espressif.com/projects/esp-idf/en/latest]]<br /><br /></p> <ul> <li>The Arduino IDENeeds extensions for these processors <br />and the different CPU boards</li> </ul><p>see:</p> <p>https://docs.espressif.com/projects/esp-idf/en/latest</p> <ul> <li>MicroPython</li> </ul><p>see:<br /> https://micropython-docs-esp32.readthedocs.io/en/esp32_doc</p> |

---++ 
---+ Flashing the code

<img alt="esptool.png" height="585" src="%ATTACHURL%/esptool.png" title="esptool.png" width="1025" />

---++ 
---+ esptool
   * esptool is called from the Makefiles in ESP-IDF
   * esptool is used when we upload code from the Arduino IDE to the processor flash
   * esptool is used when the Micropython IDE uPyCraft<br /><br />installs Micropython onto the processor flash
In the above cases the use of esptool is hidden to us.

We can however also execute esptool directly.

---++ 
---+ How to write a Micropython program?

First we need a Micropython interpreter!

You find the sources here:

https://github.com/micropython/micropython/

In the repository you find ports for the ESP8266 and the ESP32.

In order to compile the code you need the ESP-IDF and its cross compilers

The code compiles into a binary file (firmware-combined.bin) which contains a boot loader and the interpreter.

This binary must be uploaded and flashed.

For documentation of the ESP8266 port of Micropython look at

https://docs.micropython.org/en/latest/esp8266/tutorial/index.html

---++ 
---+ How to communicate with the Micropython interpreter?

We use a serial connection passing through the micro USB connection.

As soon as we connect the processor card to the PC we see the

UART bridge and a new device: dev/ttyUSB0 is created.

This device is used to communicate with the Micropython REPL.

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

You see the command prompt and you can interact with Micropython. But … how to upload scripts?

---++ 
---+ What is REPL?

---++ 

<img alt="repl.png" height="270" src="%ATTACHURL%/repl.png" title="repl.png" width="683" />

---++ 
---+ The communication tools: minicom

<img alt="minicom.png" height="231" src="%ATTACHURL%/minicom.png" title="minicom.png" width="379" />

You see the command prompt and you can interact with Micropython.

But … how to upload scripts?

---++ 
---+ The command line tool ampy

<img alt="ampy.png" height="531" src="%ATTACHURL%/ampy.png" title="ampy.png" width="741" />

---++ 
---+ IDE for Micropython: uPyCraft

<img alt="uPyCraft.png" height="830" src="%ATTACHURL%/uPyCraft.png" title="uPyCraft.png" width="1200" />

---++ 
---+ uPyCraft

uPyCraft is a rather complete Integrate Development Environment (IDE)

which lets you<br /><br />
   * Access the REPL<br /><br />
   * Create directories on the Micropython file system<br /><br />
   * Upload scripts<br /><br />
   * Syntax check scripts<br /><br />
   * Run scripts<br /><br />
   * Install Micropython on your processor board
---++ 
---+ Flashing Micropython

This has already been done for you! However, it is easy if you want to do it

at home with a new processor board.

Compiling a new version of Micropython is substantially harder but also perfectly possible.

<img alt="updateFirmware.png" height="305" src="%ATTACHURL%/updateFirmware.png" title="updateFirmware.png" width="450" />
---++ 
---+ uPyCraft(2)

uPyCraft is based on QT4 and is available for Linux, Windows and Mac.

It is written in !PyQt4 the Python language binding to Qt4.

The Linux version did not work for me

I found a version based on !PyQt5 (new version of QT) which was even worse.

I tried to correct as much as I could to make the !PyQt5 version usable on Linux:

https://github.com/uraich/uPyCraft-Qt5

---++ 
---+ Thonny

<img alt="thonny.png" src="%ATTACHURL%/thonny.png" title="thonny.png" />

---++ 
---+ Thonny (2)

Thonny is an IDE for Python which has provisions for Micropython.<br /><br />Under Tools &rarr; Options button you can select the type of

Python interpreter you intend to use.

<img alt="thonny_uP.png" height="351" src="%ATTACHURL%/thonny_uP.png" title="thonny_uP.png" width="690" />

---++ 
---+ !IoT Hello World program

A “Hello World” program, just printing “Hello World” on the screen

does not look very exciting.

However, this is generally used to verify that the infrastructure<br /><br />Compiler, linker, downloader, flash program<br /><br />are working correctly<br /><br />In embedded systems printing can be quite complex

and a blinking LED is used instead.

---++ 
---+ Switching on and off a LED

The ESP8266 and the ESP32 have a “user LED” connected to GPIO 2.

How do we control this LED?<br /><br />
   * Define that the LED is connected to GPIO 2<br /><br />
   * Program this pin as output<br /><br />
   * Write a logic 1 to the pin to switch it on<br /><br />
   * Write a logic 0 to the pin to switch it off<br /><br />
   * The logic state may be inverted if the LED is active low
---++ 
---+ Micropython hardware functions

<img alt="hardwareFunctions.png" src="%ATTACHURL%/hardwareFunctions.png" title="hardwareFunctions.png" />

---++ 
---+ The machine.Pin class

<img alt="pinClass.png" height="811" src="%ATTACHURL%/pinClass.png" title="pinClass.png" width="1228" />

---++ 
---+ Switch the LED on, version 1

<img alt="ledControl1.png" height="266" src="%ATTACHURL%/ledControl1.png" title="ledControl1.png" width="367" />

---++ 
---+ Switch the LED on, version 2

<img alt="ledControl2.png" height="256" src="%ATTACHURL%/ledControl2.png" title="ledControl2.png" width="349" />

---++ 
---+ The blinking LED

Now we put the code into a script and run it

<img alt="blinkingLed.png" height="590" src="%ATTACHURL%/blinkingLed.png" title="blinkingLed.png" width="800" />

---++ 
---+ Changing the light intensity

The LED is connected to a digital line which can only be set to 0 or Vcc.

How can we change the light intensity and dim the LED?

The light intensity depends on the average current flowing through the LED.

The answer is PWM: pulse width modulation.

<img alt="pwm.png" src="%ATTACHURL%/pwm.png" title="pwm.png" />

---++ 
---+ PWM in Micropython

<img alt="pwm_uP.png" height="383" src="%ATTACHURL%/pwm_uP.png" title="pwm_uP.png" width="766" />

---++ 
---+ Our PWM implementation

<img alt="pwmImpl.png" src="%ATTACHURL%/pwmImpl.png" title="pwmImpl.png" />

---++ 
---+ The WS2812B LED

A more complex LED:<br /><br />
   * rgb LED used in LED chains.<br /><br />
   * each ws18b12 contains the 3 colored LEDs and a controller.<br /><br />
   * Can be cascaded and individually addressed, depending on its position in the chain<br /><br />
   * Needs precise timing<br /><br />
   * To use it we pass through the neopixel library built into MicroPython
---++ 
---+ WS2812B timing

For all the details on the ws2812b look at<br /><br /> https://cdn-shop.adafruit.com/datasheets/WS2812B.pdf

24 bit of colour data puts 2e24 colours at your disposal

Coding of a single bit

<img alt="ws2812Bits.png" height="273" src="%ATTACHURL%/ws2812Bits.png" title="ws2812Bits.png" width="481" />

The control word:

<img alt="ws2812ControlWord.png" height="76" src="%ATTACHURL%/ws2812ControlWord.png" title="ws2812ControlWord.png" width="924" />

---++ 
---+ Cascading the WS2812B

---++ 

<img alt="ws2812Chain.png" height="579" src="%ATTACHURL%/ws2812Chain.png" title="ws2812Chain.png" width="397" />

---++ 
---+ Using the neopixel library

<img alt="neopixel.png" src="%ATTACHURL%/neopixel.png" title="neopixel.png" />

---++ 
---+ … and our code

We have a single neopixel connected to

GPIO pin 4 (ESP8266)

or

GPIO pin 21 (ESP32)

This code works on both CPUs!

<img alt="neopixelCode.png" height="549" src="%ATTACHURL%/neopixelCode.png" title="neopixelCode.png" width="679" />

---++ 
---+ The !I2C bus

!I2C stands for <b>I</b>nter-<b>I</b>ntegrated-<b>C</b>ircuit. It was invented by Philips Semiconductor

in 1982. Slow, short distance.

Quite a number of sensors in the "WeMos D1 sensor shield collection use the !I2C bus
   * SHT30 temperature and humidity sensor
   * DS1307 real time clock
   * The BMP180 barometric pressure and temperature sensor<br /><br />
   * The SSD1306 OLED (Organic Light Emitting Diode) display

---++ 
---+ The physical bus

The CPU (master) connects to the sensors (slaves) through

2 digital lines: <br /><br />
   * SCL: the clock
   * SDA: the data

<img alt="i2cBus.png" height="163" src="%ATTACHURL%/i2cBus.png" title="i2cBus.png" width="450" />

---++ 
---+ !I2C start and stop sequence

When the master want to talk to the slave it issues a <i>start sequence</i><br /><br />It terminates the transfer with a _stop sequence_

<img alt="i2cStartStop.png" height="152" src="%ATTACHURL%/i2cStartStop.png" title="i2cStartStop.png" width="525" />

---++ 
---+ !I2C addressing

When talking to a slave the master sends a seven bit address

followed by a read/write bit<br /><br />This allows to access at most 128 devices

<img alt="i2cAddress.png" height="75" src="%ATTACHURL%/i2cAddress.png" title="i2cAddress.png" width="408" />

---++ 
---+ !I2C data transfer

Data is transmitted 8 bits at a time followed by an acknowledge bit. <br /><br />If acknowledge is low, transfer ok, otherwise: send stop sequence

<img alt="i2cData.png" height="80" src="%ATTACHURL%/i2cData.png" title="i2cData.png" width="428" />

---++ 
---+ !I2C write cycle
   * Send start sequence
   * Send !I2C address and R/W bit low
   * Send internal register number
   * Send data byte
   * Optionally send further data bytes
   * Send stop sequence
---++ 
---+ !I2C read cycle
   * Send start sequence
   * Send slave address with R/W low
   * Send address of internal register
   * Send a start sequence again
   * Send slave address with R/W high
   * Read data byte
   * Send stop sequence
---++ 
---+ !I2C in Micropython

<img alt="i2c_uP.png" src="%ATTACHURL%/i2c_uP.png" title="i2c_uP.png" />

---++ 
---+ Scanning the !I2C bus

<img alt="i2cScan.png" src="%ATTACHURL%/i2cScan.png" title="i2cScan.png" />

---++ 
---+ The SHT30 digital temperature and relative humidity sensor

The SHT30 is a digital temperature and humidity sensor based on the I2C bus

Here is its [[http://www.mouser.com/ds/2/682/Sensirion_Humidity_Sensors_SHT3x_Datasheet_digital-971521.pdf][data sheet]].<br /><br />Temperature precision: +- 0.3 °C<br /><br />Relative humidity: +- 3 %<br /><br />Works on 2.4V – 5.5 V<br /><br /><img alt="sht30Block.png" height="399" src="%ATTACHURL%/sht30Block.png" title="sht30Block.png" width="362" />

---++ 
---+ A look at the SHT30 driver

%ATTACHURL%/sht30.py.txt

---++ 
---+ Reading out the SHT30

<img alt="sht30Code.png" src="%ATTACHURL%/sht30Code.png" title="sht30Code.png" />

---++ 
---+ Results from the SHT30

<img alt="sht30Results.png" src="%ATTACHURL%/sht30Results.png" title="sht30Results.png" />

---++ 
---+ !WeMos D1 mini sensor and actuator shields (1)

| <img alt="wemosButton.png" height="266" src="%ATTACHURL%/wemosButton.png" title="wemosButton.png" width="245" /> | <img alt="wemosWS2812.png" height="341" src="%ATTACHURL%/wemosWS2812.png" title="wemosWS2812.png" width="357" /> | <img alt="wemosOLED.png" src="%ATTACHURL%/wemosOLED.png" title="wemosOLED.png" /> |
| Pushbutton | !WS2812 cascadable rgb LED | !SSD1306 OLED display |
| <img alt="wemosDS18B20.png" height="201" src="%ATTACHURL%/wemosDS18B20.png" title="wemosDS18B20.png" width="183" /> | <img alt="wemosDHT11.png" height="293" src="%ATTACHURL%/wemosDHT11.png" title="wemosDHT11.png" width="363" /> | <img alt="wemosLedMatrix.png" src="%ATTACHURL%/wemosLedMatrix.png" title="wemosLedMatrix.png" /> |
| !DS118B20 temperature sensor | DHT11 temperature and relative humidity sensor | 8x8 LED Matrix |

---++ 
---+ Wemos D1 mini sensor and actuator shields (2)

| <img alt="wemosBuzzer-v2.png" src="%ATTACHURL%/wemosBuzzer-v2.png" title="wemosBuzzer-v2.png" /> | <img alt="wemosDataLogger-v2.png" height="212" src="%ATTACHURL%/wemosDataLogger-v2.png" title="wemosDataLogger-v2.png" width="250" /> | <img alt="wemosSHT30.png" src="%ATTACHURL%/wemosSHT30.png" title="wemosSHT30.png" /> |
| Passive Buzzer | Data Logger | SHT30 temperature and humidity sensor |
| <img alt="tripleBase.png" src="%ATTACHURL%/tripleBase.png" title="tripleBase.png" /> || <img alt="proto.png" height="195" src="%ATTACHURL%/proto.png" title="proto.png" width="250" /> |
| triple base || my prototype board: LED + photo resistor |

---++ 
---+ Pinouts of shields

<img alt="shieldPins.png" height="590" src="%ATTACHURL%/shieldPins.png" title="shieldPins.png" width="699" />

---++ 
---+ Documentation for the demo programs

Demo programs for all the shields are available on github:

https://github.com/uraich/MicroPython_IoTDemos

A short description of every program can be found in the README

---++ 
---+ The data logger

| <p>The data logger features a DS1307 Real Time Clock (RTC) backed up by a battery<br /><br />An SD card socket also provided.</p> <p>This allows to store large amounts of data locally<br /><br />The RTC keeps the time and measurements can be supplied with a time tag<br /><br />Programs to set and read the RTC are provided.<br /><br />One of the programs setting the RTC gets the time from and NTP server<br /><br />such that manual specification of the current date and time are not needed.</p> | <img alt="wemosDataLogger-v2.png" height="212" src="%ATTACHURL%/wemosDataLogger-v2.png" title="wemosDataLogger-v2.png" width="250" /> |
https://github.com/uraich/MicroPython_IoTDemos/tree/master/drivers/ds1307

---++ 
---+ The push button shield
| <img alt="pushbuttonCode.png" height="532" src="%ATTACHURL%/pushbuttonCode.png" title="pushbuttonCode.png" width="484" /> | <img alt="wemosButton.png" height="266" src="%ATTACHURL%/wemosButton.png" title="wemosButton.png" width="245" /> |

---+ !DS18B20 shield
| <img alt="ds18b20Code.png" src="%ATTACHURL%/ds18b20Code.png" title="ds18b20Code.png" /> | <img alt="wemosDS18B20.png" height="201" src="%ATTACHURL%/wemosDS18B20.png" title="wemosDS18B20.png" width="183" /> |
| | |
---++ 

---++ 
---+ SSD1306 48x64 OLED display

This one is also an !I2C device

<br />It provides 48*64 pixels and allows to

   * Write a few characters of text
   * Do simple graphics
The ssd1306 class inherits from the

<br />framebuf class included in Micropython such that all

drawing methods of the framebuf are available for drawing:

<br /> https://docs.micropython.org/en/latest/library/framebuf.html

<br />For an example see:

https://github.com/uraich/MicroPython_IoTDemos/tree/master/drivers/oled

<img alt="wemosOLED.png" height="265" src="%ATTACHURL%/wemosOLED.png" title="wemosOLED.png" width="461" />

---++ 
---+ The DHT11 shield

| <img alt="dht11Code.png" height="447" src="%ATTACHURL%/dht11Code.png" title="dht11Code.png" width="501" /> | <img alt="wemosDHT11.png" height="293" src="%ATTACHURL%/wemosDHT11.png" title="wemosDHT11.png" width="363" /> |
| ^ | The DHT11 is a digital temperature<br />and relative humidity sensor. It uses<br />a proprietary protocol of <br />communication with its controlling<br />host implemented in the <br />dht.DHT11 class |

---++ 
---+ The LED matrix
| <p>The LED matrix has 8x8 LEDs on it, which can individually be switched on or off.<br /><br />In addition to the _mled_ class which takes care of the communication between the host</p> <p>and the device and which has classes to clear the display,</p> <p>set a pixel on or off and to change the brightness,<br /> <br />I wrote a class _matrix_ which takes a number 0..64 and</p> <p>lights this number of LEDs starting from bottom left</p> | <img alt="wemosLedMatrix.png" height="252" src="%ATTACHURL%/wemosLedMatrix.png" title="wemosLedMatrix.png" width="243" /> |
---++ 
---+ The buzzer
| <p>This shield implements a passive buzzer.<br /><br />A passive buzzer takes a frequency(an active buzzer takes a signal level)</p> <p>and produces a sound at this frequency.</p> <p><br />This means that the frequency can be changed and a tune can be played.</p> <p>In <br /><br /> https://github.com/uraich/MicroPython_IoTDemos/tree/master/drivers/buzzer <br /><br />you will find a program interpreting songs on</p> <p>RTTTL (Ring Tone Text Transfer Language)</p> <p>and playing these on the buzzer<br /><br />A small song library is also provided</p> <p> </p> | <img alt="wemosBuzzer-v2.png" height="269" src="%ATTACHURL%/wemosBuzzer-v2.png" title="wemosBuzzer-v2.png" width="250" /> |
---++ 
---+ The prototype module

| <p>This is a home build module featuring a photo-resistor</p> <p>measuring the light intensity impinging on it. <br /><br />It provides an analogue value converted to digital</p> <p>by the ADC on the !WeMos D1 CPU<br /><br />Please note that the ESP8266 has a single 10 bit ADC</p> <p>while the ESP32 has 3 12 bit ADCs.</p> <p>A MUX provides up to 18 analogue channels</p> <p><br />The light intensity can be changed with an LED</p> | <img alt="proto.png" height="195" src="%ATTACHURL%/proto.png" title="proto.png" width="250" /> |
---++ 
---+ The triple base

This module allows to easily stack a rather larger number of shields to a sandwich.<br /><br />Make sure however that the GPIO lines used by the modules do not clash

<img alt="tripleBase.png" height="241" src="%ATTACHURL%/tripleBase.png" title="tripleBase.png" width="471" />

---++ 
---+ Exercises
<h2 align="center">Now it is up to</h2> <h1 align="center"> *You* </h1> <h2 align="center">to do the work!</h2> <p align="left"><br />The exercises are here:</p> <p align="left"> [[Session2][https://afnog.iotworkshop.africa/do/view/AFNOG/Session2]]</p>

%SLIDESHOWEND%

%USERSIG{UliRaich - 2019-05-13}%

---++ Comments

%COMMENT%

Attachments

Topic attachments
I	Attachment	History	Action	Size	Date	Who
odp	afnog19-ws-session2.odp	r1	manage	6431.5 K	2019-05-14 - 09:01	UliRaich
png	ampy.png	r1	manage	100.7 K	2019-05-14 - 11:42	UliRaich
png	blinkingLed.png	r1	manage	79.9 K	2019-05-14 - 12:17	UliRaich
png	cpuPinouts.png	r1	manage	34.1 K	2019-05-13 - 20:32	UliRaich
png	dht11Code.png	r1	manage	54.5 K	2019-05-14 - 16:44	UliRaich
png	ds18b20Code.png	r1	manage	64.8 K	2019-05-14 - 15:33	UliRaich
png	esp32-pinout-chip-ESP-WROOM-32.png	r1	manage	137.4 K	2019-05-14 - 09:50	UliRaich
png	esp32Pinout-v2.png	r1	manage	151.2 K	2019-05-14 - 09:01	UliRaich
png	esp8266.png	r1	manage	116.1 K	2019-05-13 - 20:27	UliRaich
png	esp8266PinMeaning.png	r2 r1	manage	155.3 K	2019-05-14 - 09:43	UliRaich
png	esp8266Pinout.png	r1	manage	176.4 K	2019-05-13 - 20:41	UliRaich
png	esp8266Programming.png	r1	manage	108.3 K	2019-05-14 - 09:59	UliRaich
png	esptool.png	r1	manage	114.3 K	2019-05-14 - 11:28	UliRaich
png	hardwareFunctions.png	r1	manage	159.5 K	2019-05-14 - 12:17	UliRaich
png	i2cAddress.png	r1	manage	1.3 K	2019-05-14 - 14:09	UliRaich
png	i2cBus.png	r1	manage	1.6 K	2019-05-14 - 14:09	UliRaich
png	i2cData.png	r1	manage	1.3 K	2019-05-14 - 14:25	UliRaich
png	i2cScan.png	r1	manage	134.8 K	2019-05-14 - 14:32	UliRaich
png	i2cStartStop.png	r1	manage	2.7 K	2019-05-14 - 14:09	UliRaich
png	i2c_uP.png	r1	manage	248.6 K	2019-05-14 - 14:26	UliRaich
png	ledControl1.png	r1	manage	19.8 K	2019-05-14 - 12:17	UliRaich
png	ledControl2.png	r1	manage	19.8 K	2019-05-14 - 12:18	UliRaich
png	lsusb.png	r1	manage	73.3 K	2019-05-14 - 11:48	UliRaich
png	minicom.png	r1	manage	17.2 K	2019-05-14 - 11:42	UliRaich
png	neopixel.png	r1	manage	165.5 K	2019-05-14 - 12:46	UliRaich
png	neopixelCode.png	r1	manage	79.9 K	2019-05-14 - 12:46	UliRaich
png	pinClass.png	r1	manage	160.1 K	2019-05-14 - 12:20	UliRaich
png	pinControl2.png	r1	manage	19.8 K	2019-05-14 - 12:18	UliRaich
png	proto.png	r1	manage	114.2 K	2019-05-14 - 15:14	UliRaich
png	protoBoard.png	r1	manage	882.8 K	2019-05-14 - 15:13	UliRaich
png	pushbuttonCode.png	r1	manage	65.6 K	2019-05-14 - 15:33	UliRaich
png	pwm.png	r1	manage	51.4 K	2019-05-14 - 12:27	UliRaich
png	pwmImpl.png	r1	manage	116.7 K	2019-05-14 - 12:31	UliRaich
png	pwm_uP.png	r1	manage	24.6 K	2019-05-14 - 12:31	UliRaich
png	repl.png	r1	manage	20.2 K	2019-05-14 - 11:45	UliRaich
png	shieldPins.png	r1	manage	68.3 K	2019-05-14 - 15:13	UliRaich
txt	sht30.py.txt	r1	manage	6.5 K	2019-05-14 - 14:43	UliRaich
png	sht30Block.png	r1	manage	27.3 K	2019-05-14 - 14:41	UliRaich
png	sht30Code.png	r1	manage	85.0 K	2019-05-14 - 14:47	UliRaich
png	sht30Results.png	r1	manage	168.5 K	2019-05-14 - 14:47	UliRaich
png	thonny.png	r1	manage	148.1 K	2019-05-14 - 12:05	UliRaich
png	thonny_uP.png	r1	manage	31.0 K	2019-05-14 - 12:05	UliRaich
png	tripleBase.png	r1	manage	196.1 K	2019-05-14 - 15:11	UliRaich
png	uPyCraft.png	r1	manage	164.1 K	2019-05-14 - 11:43	UliRaich
png	updateFirmware.png	r1	manage	27.3 K	2019-05-14 - 11:59	UliRaich
png	wemosButton.png	r1	manage	113.3 K	2019-05-14 - 14:55	UliRaich
png	wemosBuzzer-v2.png	r1	manage	108.9 K	2019-05-14 - 15:21	UliRaich
png	wemosBuzzer.png	r1	manage	252.7 K	2019-05-14 - 15:11	UliRaich
png	wemosDHT11.png	r1	manage	113.4 K	2019-05-14 - 14:55	UliRaich
png	wemosDS18B20.png	r1	manage	71.5 K	2019-05-14 - 14:55	UliRaich
png	wemosDataLogger-v2.png	r1	manage	72.7 K	2019-05-14 - 15:21	UliRaich
png	wemosDataLogger.png	r1	manage	263.9 K	2019-05-14 - 15:11	UliRaich
png	wemosEsp32.png	r1	manage	213.3 K	2019-05-13 - 20:29	UliRaich
png	wemosLedMatrix.png	r1	manage	109.8 K	2019-05-14 - 14:55	UliRaich
png	wemosOLED.png	r1	manage	139.2 K	2019-05-14 - 14:55	UliRaich
png	wemosSHT30.png	r1	manage	102.9 K	2019-05-14 - 15:11	UliRaich
png	wemosWS2812.png	r1	manage	144.2 K	2019-05-14 - 14:55	UliRaich
png	ws2812Bits.png	r1	manage	11.9 K	2019-05-14 - 12:42	UliRaich
png	ws2812Chain.png	r1	manage	19.9 K	2019-05-14 - 12:42	UliRaich
png	ws2812ControlWord.png	r1	manage	7.6 K	2019-05-14 - 12:42	UliRaich

Topic revision: r5 - 2019-05-14 - UliRaich