This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Tinypilot e-paper instead of LCD
#11
(2024-06-19, 08:00 PM)seandepagnier Wrote: I have written my code so that the resolution of the lcd does not matter.  For this reason it is a bit different from other libraries and ugfx only supports functions that are not specific to resolution.

What could be done, is to write a ugfx driver to use this library which supports more lcds using it as another layer rather than directly talking to spi.

I can follow that, it might not be nescessary for now. I had a hard time finding a jlx, that‘s why I got this display. And I have it working now by changing the sequence of the refresh part of the jlx in ugfx. It can still be improved, since the refresh frequency doesn‘t seem to match the display correctly yet.
First I‘ll try to make a seperate ssd1309 class though, so the code for the jlx is back to it‘s original state and the ssd1309 is added.
I‘ll probably leave the e-paper be for now, since the contrast on the ssd1309 seems good enough for bright days and I want to finish my build Big Grin


Attached Files Image(s)
   
Reply
#12
Please submit a pull request once you finalized it.. that way other people could potentially use your driver.
Reply
#13
(2024-06-22, 03:24 AM)seandepagnier Wrote: Please submit a pull request once you finalized it..  that way other people could potentially use your driver.

Hi Sean

This is my first time trying to contribute, could you tell me in which branche I should upload the changed files to submit the actual pull request? I don't want to mess things up.

Thank you.
Reply
#14
if you submit a pull request to master I will review it. Since it is a separate driver that will not be executed normally it should be safe.
Reply
#15
I experimented a lot with epaper displays for instrument display a few years ago. A word of warning...

The sunlight readability is great but ironically sunlight and/or heat destroys epaper displays really easily. Freezing weather can destroy them too. Mine didn't last more than a few months. If you stay in temperate zones and protect them from direct sunlight and frost then you might do better.

They also have very limited number of screen refreshes before they die. The rapid update of the course display on an autopilot will kill the screen quickly. epaper is more suited to updates once or twice a minute at most, like turning pages in a book, no real time displays.

I believe epaper technology is improving so I might be out of date on some of this, I have heard of new technology with a longer lifespan under high refresh rate but you would need something new and special, not a normal epaper display.
Reply
#16
(2024-06-25, 01:52 AM)seandepagnier Wrote: if you submit a pull request to master I will review it. Since it is a separate driver that will not be executed normally it should be safe.

I‘ve added the driver in ugfx.cpp and added the ssd1309 option in lcd.py, which are both existing files. I‘m not sure where to upload them… could you provide a „development“ branch in the repository, where I can then upload these two files and submit a pull request where they are compared to the files in the „master“ branch? Or will Github give my files some kind of revision when I directly upload them in the Master branch and leave the original files untouched?
Reply
#17
Could you submit a pull request to the beta branch?
Reply
#18
(2024-06-25, 06:14 AM)syohana Wrote: I experimented a lot with epaper displays for instrument display a few years ago. A word of warning...

The sunlight readability is great but ironically sunlight and/or heat destroys epaper displays really easily. Freezing weather can destroy them too. Mine didn't last more than a few months. If you stay in temperate zones and protect them from direct sunlight and frost then you might do better.

They also have very limited number of screen refreshes before they die. The rapid update of the course display on an autopilot will kill the screen quickly. epaper is more suited to updates once or twice a minute at most, like turning pages in a book, no real time displays.

I believe epaper technology is improving so I might be out of date on some of this, I have heard of new technology with a longer lifespan under high refresh rate but you would need something new and special, not a normal epaper display.

Ok, I didn't know this, thank you for your experience. I've ordered one to experiment with, but will surely find another use for it.

(2024-06-26, 02:35 PM)seandepagnier Wrote: Could you submit a pull request to the beta branch?

Hello Sean

I've just managed to create a pull request in the Master branche, since it is only the lcd.py and ugfx.cpp files which have been edited. I hope this is ok?
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)