LIBtft144 icon indicating copy to clipboard operation
LIBtft144 copied to clipboard

Bottom quarter of my display is colour noise

Open chrisarcher opened this issue 11 years ago • 2 comments

Hi, Not sure how to contact you, but found your code and I have been trying to get it working on my PI. I have the RED PCB version of the display, and when I run your example-tft144-rpi-only.py the picture appears to be shifted up by 25% (top quarter is missing) and the bottom quarter of the display is just random colour pixels. My only changes in your code was to change the pin number to those that I have used (DC=23 LED =0 ).

Any suggestions as to what I have done wrong, or how I could fix it please? Thanks Chris

chrisarcher avatar Jan 14 '15 01:01 chrisarcher

Hello Chris,
  I'm in Indonesia at
    present, totally unable to check
        anything. I made a mention that it was for the BLACK PCB. The RED one looks
          (from eBay pic) like it might be similar, but I did not
          check it.

          What I DO recall
            was that I did read a post somewhere out on the
            wide internet that was suggesting at least one board out
            there (eBay presumably)
              had a PCB wiring error, such that a hardware pin set
              an option
              that referenced an incorrect pixel XbyY. It was definitely for
                that same control chip (ILI9163 or whatever) that
                our red & black boards use.  And that article said that
                it WAS possible to counteract the hardware error by
                software codes. It was for a driver written on another
                  website, and was likely in another programming
                    language
                      even. It might even have been arduino based. 

                      Your symptoms could well be from this
                      incorrect pixel geometry. I do not have the
                      article reference - I would simply use google
                      to hunt down all references to the chip, and
                      trawl through what you find.
                      Easier
                        might be to simply bite the bullet and get
                        another board, but the black one.

                        Sorry.

                          If
                              you choose to try to hunt down the
                              article and the error
                                and its supposed software hack fix,
                                then you could publish that info for
                                others, or send it to me (back home
                                in March) to patch into the code I
                                have for the black board.

                                When the black board
                                  works, its totally
                                    cute.

                                  Cheers
                                  Brian
                                    Lombok



                        Email?
                          I have various. They all get here!
                        A
                            good email for me is on the VirtGPIO
                            website (http://virtgpio.blavery.com) 
                            Another is referenced
                            on the github stuff
                              at https://github.com/BLavery
                      But
            I dont have YOURS. It says From = Chris Archer
            <[email protected]>   which looks not
            likely to work.
            So I hope this reply system gets there...




On 14/01/15 09:19, chrisarcher wrote:


  Hi,
    Not sure how to contact you, but found your code and I have been
    trying to get it working on my PI.
    I have the RED PCB version of the display, and when I run your
    example-tft144-rpi-only.py the picture appears to be shifted up
    by 25% (top quarter is missing) and the bottom quarter of the
    display is just random colour pixels. My only changes in your
    code was to change the pin number to those that I have used
    (DC=23 LED =0 ).
  Any suggestions as to what I have done wrong, or how I could
    fix it please?
    Thanks
    Chris
  —
    Reply to this email directly or view it
      on GitHub.

BLavery avatar Jan 14 '15 10:01 BLavery

Looks like here is a correction for RED board (with its incorrect hardware optioning at factory). Thanks Lukas. IN DUE COURSE I'll add it into the posted code. Brian

On 19/03/15 10:16, Lukáš Chrást wrote:

Hello, I got myself a RED 128x128 1.44" display from eBay and I stumbled upon your python module. First of all, thanks for a nice code. I had the same problem as guy writing on issues page on you Github. And you were right, problem was wrong HW wiring with resolution 128x160px. After some time looking through your code, I was able to fix it by adding 2 simple lines into set_frame function: def set_frame(self, x1=0, x2=TFTWIDTH-1, y1=0, y2=TFTHEIGHT-1 ): y1=y1 + 32 y2=y2 + 32 self.write_command(SET_COLUMN_ADDRESS) self.write_data([0, x1, 0, x2]) self.write_command(SET_PAGE_ADDRESS) self.write_data([0,y1,0,y2]) Maybe you can include it in your code somehow. Anyway, thanks. Cheers, Lukas Chrast

BLavery avatar Mar 19 '15 02:03 BLavery