search

Antonorosso / u8glib

Automatically exported from code.google.com/p/u8glib
Other
0 stars 0 forks source link

t6963: weird graphics @ 128*64 #216

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1.Arduino Mega 2560, but does not seem to be limited to this one
2.T6963 Display 128*64
3.I have tried several pin connection schemes, checked the wiring, tried 
different displays (all of the same type).

What is the expected output? What do you see instead?
The picture is shifted to the left by several pixels.
Additionally, about 40 of the rightmost columns seem to be deleted and replaced 
by the leftmost 40 columns.

I have even interrupted one wire at a time everywhere to see whether there's an 
interruption anywhere, but I always get additional errors, so I think it's a 
software issue.

What version of the product are you using? On what operating system?
Arduino on Win 7 with u8glib v 1.14

Please provide any additional information below.

Original issue reported on code.google.com by 1337ch17...@googlemail.com on 4 Nov 2013 at 11:43

GoogleCodeExporter commented 8 years ago 
The error applies to text and graphics.

Original comment by 1337ch17...@googlemail.com on 4 Nov 2013 at 11:47

GoogleCodeExporter commented 8 years ago 
Can you provide a picture of the output and a link to the datasheet for the 
display?
Which u8glib constructor/device did you use?

In u8g_dev_t6963_128x64.c:
around line 162 replace
        disp_ram_adr = WIDTH/8;
        disp_ram_adr *= y;
        for( i = 0; i < PAGE_HEIGHT; i ++ )
with
        disp_ram_adr = WIDTH/8;
        disp_ram_adr *= y;
        disp_ram_adr += 5;    // shift display by 5*8 = 40 pixel
        for( i = 0; i < PAGE_HEIGHT; i ++ )

will this help?

Original comment by olikr...@gmail.com on 5 Nov 2013 at 4:38

GoogleCodeExporter commented 8 years ago 
Thanks for your fast reaction, sadly I have no access to the hardware at
the moment.
I'll deliver the requested information as soon as possible ;)

Original comment by 1337ch17...@googlemail.com on 5 Nov 2013 at 7:02

GoogleCodeExporter commented 8 years ago 
I use
U8GLIB_T6963_128X64 u8g(22, 24, 26, 28, 30, 32, 34, 36, 12, 11, 9, 8, 10);
I changed the pins in order to check whether this was a hardware issue.

2013/11/5 w201cruiser . <1337ch1770r@googlemail.com>

Original comment by 1337ch17...@googlemail.com on 5 Nov 2013 at 7:21

GoogleCodeExporter commented 8 years ago 
This is what it looks like before:
https://www.dropbox.com/s/0d8fme233zebug0/20131105_105434.jpg
and after the modification:
https://www.dropbox.com/s/lggholf3xqvj5np/20131105_105205.jpg

2013/11/5 w201cruiser . <1337ch1770r@googlemail.com>

Original comment by 1337ch17...@googlemail.com on 5 Nov 2013 at 10:02

GoogleCodeExporter commented 8 years ago 
Datasheet:
http://www.gydlcd.com/003/pdf/200582521173393124.pdf

Original comment by 1337ch17...@googlemail.com on 5 Nov 2013 at 10:13

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
How did you connect the FS pin? It must be connected to GND.

Original comment by olikr...@gmail.com on 5 Nov 2013 at 11:20

GoogleCodeExporter commented 8 years ago 
Yup that was it, thanks a lot again!
Thought it would not play a role because it changed nothing some tries ago, but 
that was before fixing another wiring issue ;)
Might this be a candidate for the FAQ?

Original comment by 1337ch17...@googlemail.com on 5 Nov 2013 at 1:31

GoogleCodeExporter commented 8 years ago 
Great, and yes, it is already mentioned at the end of this page: 
http://code.google.com/p/u8glib/wiki/device

Original comment by olikr...@gmail.com on 5 Nov 2013 at 1:36

GoogleCodeExporter commented 8 years ago 
will be continued in issue 87

Original comment by olikr...@gmail.com on 22 Jan 2014 at 8:13