I am having problems with a 264x176 (2.7") waveshare e-paper display.
At the moment I am just trying to initialize to a blank screen.
The refresh is working but no data seems to be transferred to the display RAM. The display comes up with random pixels I assume are residual in the RAM.
Of course I am confused by the two sets of data transmission (0x10 and 0x13) - why two?
Anyway here is the code - any help would be appreciated.
Yes I've been looking at those two libraries. I have some questions...
For the 2.13" you have the "panel setting" as 0x10 should this be 0x00. Also why does the choices of resolution in the panel setting none are the same as the actual display (do I choose the next biggest?).
The 7.5" library does not seen to use the data transmission 2 (0x13) why is this?
The 2.13' uses both transmission 1 (0x10) and 2 (0x13).
Do I need to send an end of data (0x11) if I do the program stalls (is it waiting for a return ACK or something of that kind).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've finally got it to work. The main problem was that I was partially basing my code on what I had previously used for a 1.54" display. Problem was the "busy pin" works in the opposite way on that display (it is on while busy) the 2.7" (and the ones in the GCB library) are low when busy.
It would also appear that the data transmission_1 (0x10) is not needed on a B/W display (but i'm not 100% sure of this). And despite the datasheet saying that 0x11 (end of data) is required it would seem it is not.
A final question is there anyway to do a READ (as there is no SDO pin) - there are a few registers that it would be interesting see the contents of.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The other thing I found is you can send the image data continuously there is no need to toggle the CS pin (and no need to call a subroutine). This could be significant when sending 5808 data points.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am having problems with a 264x176 (2.7") waveshare e-paper display.
At the moment I am just trying to initialize to a blank screen.
The refresh is working but no data seems to be transferred to the display RAM. The display comes up with random pixels I assume are residual in the RAM.
Of course I am confused by the two sets of data transmission (0x10 and 0x13) - why two?
Anyway here is the code - any help would be appreciated.
There is a library for the e-Paper displays in the new releae. I would be using that as the basis of the project.
Yes I've been looking at those two libraries. I have some questions...
For the 2.13" you have the "panel setting" as 0x10 should this be 0x00. Also why does the choices of resolution in the panel setting none are the same as the actual display (do I choose the next biggest?).
The 7.5" library does not seen to use the data transmission 2 (0x13) why is this?
The 2.13' uses both transmission 1 (0x10) and 2 (0x13).
Do I need to send an end of data (0x11) if I do the program stalls (is it waiting for a return ACK or something of that kind).
I know the libraries work. So, the specifics of your questions may not be important. As the testing showed the libraries to work.
Giuseppe D'Elia developed the libraries and I quality assured and built the demos. He may be able to respond to your specifics.
I've finally got it to work. The main problem was that I was partially basing my code on what I had previously used for a 1.54" display. Problem was the "busy pin" works in the opposite way on that display (it is on while busy) the 2.7" (and the ones in the GCB library) are low when busy.
It would also appear that the data transmission_1 (0x10) is not needed on a B/W display (but i'm not 100% sure of this). And despite the datasheet saying that 0x11 (end of data) is required it would seem it is not.
A final question is there anyway to do a READ (as there is no SDO pin) - there are a few registers that it would be interesting see the contents of.
The other thing I found is you can send the image data continuously there is no need to toggle the CS pin (and no need to call a subroutine). This could be significant when sending 5808 data points.
I wrote a compresser. Optimises the picture and save a huge amount of data transmssion.
See the demos for tbe code.