You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using a 128x32 pixel SSD1306 SPI OLED display connected to a Daisy Seed, using daisy::OledDisplay<daisy::SSD130x4WireSpi128x32Driver>. Whenever I display anything, it is offset 32 pixels in the X direction. For example, this code:
But it looks like that line of code was specifically added for 32-pixel-high displays, so I suspect that simply deleting it isn't the correct solution. Maybe different SSD1306 modules aren't perfectly compatible?
The text was updated successfully, but these errors were encountered:
I was working with a similar display, and had this same issue, and was also able to resolve it by commenting out that line..
At the time, I thought I was the unique one. Might just be the original author for 32-pixel-height had a display that was slightly different.
Might be worth seeing if/which displays require that extra high-column-addr offset, and making a separate driver for it, with most/everything else shared with the exitsting 130x driver.
I'm using a 128x32 pixel SSD1306 SPI OLED display connected to a Daisy Seed, using daisy::OledDisplay<daisy::SSD130x4WireSpi128x32Driver>. Whenever I display anything, it is offset 32 pixels in the X direction. For example, this code:
displays this:
The letter "a" should appear at (0,0) but it shows up near the middle of the alphabet.
I tracked the problem to this line of code in libDaisy:
libDaisy/src/dev/oled_ssd130x.h
Line 379 in f7727ed
If I delete that line, the display works fine:
But it looks like that line of code was specifically added for 32-pixel-high displays, so I suspect that simply deleting it isn't the correct solution. Maybe different SSD1306 modules aren't perfectly compatible?
The text was updated successfully, but these errors were encountered: