Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OLED controller compatability #2

Open
easynote0 opened this issue Jul 10, 2020 · 3 comments
Open

OLED controller compatability #2

easynote0 opened this issue Jul 10, 2020 · 3 comments

Comments

@easynote0
Copy link

Didn't know where to put this, or contact you, so I'll put it here:
Which controller IC did you use for your display? Is it a 256x64 pixel one?
Those are usually SSD1322, and the 128x64 ones uses SSD1306.
Didn't see any clues in form of libraries in the source folder.
This is a great contribution btw.

@qu1ck
Copy link
Member

qu1ck commented Jul 10, 2020

Clue is in the name https://github.com/openscopeproject/HP34401a-OLED-FW/tree/master/lib/SSD1322_Display

I built it around 256x64 display based on SSD1322, this is the particular one I recommend https://www.buydisplay.com/white-3-2-inch-arduino-raspberry-pi-oled-display-module-256x64-spi
(it's also available on ebay)

@easynote0
Copy link
Author

easynote0 commented Jul 12, 2020

Sorry, I completely ignored the title. If I wouldn't, there would not be a questions.Sorry again. BUT. I must say something.
I absolutely love that site. And they've added quite the assortment in the last year. I like the model you choose. I would've too.
OLEDs should be used in anything that doesn't require color IMHO. Was it difficult to code?

@qu1ck
Copy link
Member

qu1ck commented Jul 12, 2020

Was it difficult to code?

You mean the display lib specifically or the firmware as a whole?
Display lib was a bit tricky to do efficiently because of 4 bit per pixel encoding. You are forced to update 2 pixels with each command so if you want to change only one pixel then you either have to read the display memory (another command, slow) or have a frame buffer in memory. I chose the latter, the chip had enough ram fortunately.

Firmware was pure fun to do, especially reverse engineering part.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants