Community Forum

This 96*96 oled screen is detected by my Pi and it is working with Seeed's own library, and it would also put out stuff while running your oled_demo.

Does your library has a manual? It doesn't looks like python when I peek into your library files... Sorry I am quite a beginner. Thank you.

I use my Pi to generate sound, and if I do oled operations within the same piece of .py file that does sound, any oled writing operations would block the sound. But if I open 2 terminal instances (I am using SSH), and run sound code on one, oled code on another, it wouldn't block the sound. So it is certainly not a CPU speed issue...

Why does this happen? And if I make my Pi running some python code at boot, how I can make the codes running like within multiple terminals?

Thank you!

Hi, Charles,

I've tested my oled with I2CScan, and it wasn't detected... maybe a broken one. And I have another oled screen here which can be detected on Arduino, but not on Pi.

Here is a library by Seeed themselves : https://github.com/DexterInd/GrovePi/tree/master/Software/Python/grove_oled
I'll see if that would work once the oled screen arrives. Happy to know that it looks amazing.

I've got the lm-sensors module in there, and the make on examples worked.

But only still I can't get my Pi to recognize my oled screen, and I have another device on the i2c bus which works perfectly.
I just ordered another oled (a seeed 96*96) to see if that would work.

Thank you for your detailed reply!

Thank you for the detailed blog post. I followed your instructions and got 2 problems :

1. there is no libi2c available, the only thing similar I've found is libi2c-dev so I installed that;
2. I got error messages while trying to "sudo make" within the example folder, here is a photo showing the result.
   http://i.imgur.com/MkWvXbC.jpg

Btw I am on a Pi B V2. One strange thing is that when I ran "sudo i2cdetect -y 1" there is nothing on the table. But while I tried to use Adafruit_SSD1306 library, the oled would respond (weirdly).

Thanks