Difference: OledShield (2 vs. 3)

Revision 32019-05-17 - UliRaich

Line: 1 to 1

META TOPICPARENT	name="WeMosD1Mini"

The OLED shield

Line: 7 to 7

Programming the shield

Changed:

<
<

The shield uses an SSD1306

OLED dot matrix controller which is accessed through the I2C bus. In order to see if we can access the chip we can first run a little program scanning the I2C bus and showing all uses I2C addresses:

>
>

The shield uses an SSD1306

OLED dot matrix controller which is accessed through the I2C bus. In order to see if we can access the chip we can first run a little program scanning the I2C bus and showing all uses I2C addresses:

This shows us that the module must be accesses on I2C address 0x3c. The code of the i2c scanner can be found here:

Changed:

<
<

https://iotworkshop.africa/pub/AFNOG/OledShield/i2cScan.py.txt

>
>

https://github.com/uraich/MicroPython_IoTDemos/blob/master/drivers/i2c/i2cScan.py

The Cayenne client may use the OLED display. It first checks if it is connected and if yes it print information about the network state. This is particularly useful if the WeMos D1 mini runs on battery and there is no connection to the PC where state information can be displayed.

Uli Raich - 2019-03-22

Line: 24 to 28

META FILEATTACHMENT	attachment="wemosOled.png" attr="" comment="" date="1553264469" name="wemosOled.png" path="wemosOled.png" size="312701" user="UliRaich" version="1"
META FILEATTACHMENT	attachment="i2cscan.png" attr="" comment="" date="1553346279" name="i2cscan.png" path="i2cscan.png" size="29037" user="UliRaich" version="1"
META FILEATTACHMENT	attachment="i2cScan.py.txt" attr="" comment="" date="1553346407" name="i2cScan.py.txt" path="i2cScan.py.txt" size="839" user="UliRaich" version="1"

Added:

>
>

META FILEATTACHMENT	attachment="oled.png" attr="" comment="" date="1558109230" name="oled.png" path="oled.png" size="342325" user="UliRaich" version="1"

View topic | History: r3 < r2 < r1 | More topic actions...