-
Notifications
You must be signed in to change notification settings - Fork 13.6k
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
[WIP] initial SSD1306 OLED display driver #8336
Conversation
d30ff01
to
1a487de
Compare
Cool! |
Waiting... I prepared 2.4 inch one for tests... |
Which screen size is everyone interested in? The driver either needs to be geared towards a particular model, or the dimensions need to be parameterized. |
The size does not matter in 1306 because all of them are 128x64. Mine just shows bigger letters and graphs then let say 0.96". For me 0.96" is unreadable because since 2 years I wear glasses for reading :) without them the 0.96' looks like noise haha. |
I have both sizes in front of me and while the 2.4" is definitely bigger, I'm trying to think of where the larger one could be put on my multi or plane without being in the way. Can have almost 2 of the smaller screens. Looking at this to make sure things are kosher preflight etc is likely the intended use and the ~1" screen I can squeeze into a lot of places. I would think more people would want to not take up too much real-estate. Just my 2¢ but in the case that the driver is independent of screen size then that is good, I still think 1" is more "manageable" but I understand the small text concern. |
@edsellar My point was that the size does NOT concern the driver work, because all of these displays are the same resolution 128x64 dots. There are 0.96", 1.3" and 2.4" for now and all of them show exactly the same graphics and text, just with a different physical size. If you put a 2.4" on a larger plane (3+ meters wingspan) there is plenty of space to fit them somewhere. I agree with the small planes and MCs you could use 0.96" |
@tubeme that’s great then! If driver work is completely agnostic of true board size due to same resolution then given we aren’t using these for their beauty capabilities, it’s win win. I’m looking forward to it and will def put the smaller in multi and larger anywhere I can fit. |
Just built and tried. I2c conflict. 0x78 says connected when not. Will need to change solder pad to 7A on physical board or locate conflict and reassess. |
Changed address to 0x7A on both physical unit and driver and rebuilt. No text/non-operational. |
Needs added library for pixel to character. Currently init is functional and will drawn line (thanks to @dagar). |
Rebased on master. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Closing as stale. |
No support for this in visible future? |
@mijarck the basic driver works for drawing pixels and lines to the screen. It still needs a small library for handling characters (fonts, etc). |
Ok, good to know. Was just interested to know about the support on PX4 if could get battery and pre-arm state easily visible, but there’s other ways to solve the issue too. |
I’ve been wanting this for years. I think it’s a great idea to isolate yourself from needing a computer and have more info than the led or red button can provide. Sat info This is the cleanest solution I can see since reliance on a remote control is diminishing greatly. |
@dagar you should get your stuff in 😄 |
This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions. |
Any new update? |
Any new update? |
Actually @AlexKlimaj did a driver for it but it needs backend or expansion done if you want it to work similar to how Ardupilot has it subscribing to data. |
Not functional yet.
#6231