Small TFT display question
grasshopper
Posts: 438
I am new to implementing displays, i have had great luck running VGA displays and 2x20 lcd displays using my propeller, but what about this one
search.digikey.com/scripts/DkSearch/dksus.dll?Detail?name=73-1325-ND
or this one
www.newhavendisplay.com/pdf/nhd-18-128160yf-ctxi-drawing.pdf
I need a small color display for my new propeller project. Ideas and comments are greatly desired.
search.digikey.com/scripts/DkSearch/dksus.dll?Detail?name=73-1325-ND
or this one
www.newhavendisplay.com/pdf/nhd-18-128160yf-ctxi-drawing.pdf
I need a small color display for my new propeller project. Ideas and comments are greatly desired.
Comments
Edit: The other one, 128x160 seems nice, a bit small... but if you get the programming of the controller... and it costs some 10 to 20 € each, it may be a good candidate.
How about one of the 4D Systems OLED displays? You could even combine the Propeller with the display by using the uOLED-96-Prop (for $80 including a memory card socket).
One other option might be to get a cheap small LCD TV monitor and use the Propeller's TV drivers.
Mike you mentioned a small LCD monitor where can one be purchased? Ill start searching but perhaps you'll have some inside information.
www.sparkfun.com/commerce/product_info.php?products_id=569
I am still new to this kind of display, but want to run something like this with my propeller all the advice I can get would be great
Thanks
I have that display that I have working with the PIC...nice display, but it is slow.
Let me know if you get it, I can send you the code to make it work (you can refactor to spin)
~Kam (^8*
What do you mean it is slow? I mean, is it not the processor that determines the speed in which the display can be run at? If i am to run the propeller would this still mean it is slow how fast is the PIC? Perhaps you could some how bring me up to speed on the issue of "slow". No pun intended.
Also; I appreciate your help. I plan on ordering it as soon as I feel that it will fit my new project.
Edited ** - Could you post some pictures so that i could see the quality of the display?
It's slow in regards to the update speed. I think it has 2 modes (I worked with it 2 years ago), serial and parallel...I could be wrong about the parallel. I used the serial, bit banged the data thru. But if you're not doing "graphics" it should work fine...
Pics...hmmm, I'll have to take the pic out and reburn the code!
From what I recall, the actual brightness etc was really good,it's just the speed...said that, I was comparing the speed with an oled display...
I personally would use the display if I where doing text *ONLY* (I don't think it displays 'graphics')
~Kam (^8*
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Timothy D. Swieter, E.I.
www.brilldea.com·- Prop Blade, LED Painter, RGB LEDs, uOLED-IOC, eProto fo SunSPOT, BitScope
www.sxmicro.com - a blog·exploring the SX micro
www.tdswieter.com
Well as far as graphics what am i limited to? Can I make a clock or a gauge for example to show volts or RPMs? A primitive tachometer perhaps? Sounds like I could.
As far as you mentioned, I will search the other threads to see what is out there.
Thanks again.
On the uOLED-96-PROP I create a driver in ASM for the display. The standard graphcis driver could be used to paint images and text on the display. When I created an 8-bit per pixel OLED display driver, I had to reorganize the video memory and write a new graphics driver.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Timothy D. Swieter, E.I.
www.brilldea.com·- Prop Blade, LED Painter, RGB LEDs, uOLED-IOC, eProto fo SunSPOT, BitScope
www.sxmicro.com - a blog·exploring the SX micro
www.tdswieter.com
Lets do a little math. I assume you can use the graphics library and create a LCD driver that is similar to the TV driver. By similar I mean that you can use tables for color pallete. Do you have a Hydra Book? if not, I recommend getting one because it goes through these design very well.
OK, with the graphics driver each pixel is 2 bits. That is there are four possible colors, more if you work with tables and create another redirection. For now lets stay simple. 2 bits per pixel is 16 pixel per long (a long being 32 bits). The SparkFun screen you reference is 128 pixels x 128 pixels. That is 16384 pixels. Divide by 16 to get the number of longs needed for a single video buffer. That is 1024 longs for a single video buffer. If you are doing animation or multicogs then you might want to double buffer the animation.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Timothy D. Swieter, E.I.
www.brilldea.com·- Prop Blade, LED Painter, RGB LEDs, uOLED-IOC, eProto fo SunSPOT, BitScope
www.sxmicro.com - a blog·exploring the SX micro
www.tdswieter.com