How to Choose a TFT display?
I put that question on Google search and got nothing. So I thought I would ask here:
(I'm using an UNO.)
Do I want a device with a controller?
I assume the TFT comes with a touch screen interface chip?
The TFT's seem to have 3 ways of interfacing to an Arduino:
16-bit or 8-bit parallel
Serial (Is this an RS232 interface TTL interface?)
SPI
I2C
a) Are any of these used jointly or do I pick one?
b) Are they each used for a different purpose?
The reason for asking is the huge number of pins for the TFT display alone, The large number of Arduino pins available for IO to the TFT, and the delays caused by the low speed of the serial, I2C and SPI methods of moving data to and from the TFT module.
I note however that the project here (JanSpace.com is for sale | HugeDomains) uses what is almost identical to an UNO and yet manages to interface to 4-5 devices including the TFT module. It doesn't leave many IO lines for talking to anything else, however. Is there a better mcu for this purpose? and if so, why is it better?
I saw note in this PDF (404 - Digital View LCD controllers) that those TFT controllers identified as "with PC interface" or similar wording "work with the analog signal from PC graphics
cards". Is this the kind of controller that I would interface to an Arduino?
louarnold:
I note however that the project here (http://www.janspace.com/b2evolution/arduino.php/2010/06/26/scooterputer) uses what is almost identical to an UNO and yet manages to interface to 4-5 devices including the TFT module. It doesn't leave many IO lines for talking to anything else, however. Is there a better mcu for this purpose? and if so, why is it better?
It looks like he ran out of pins, though, hence the DPDT switch. Maybe a Mega board wouyld have been a better choice. A UNO-type board can carry a lot of gear. I find mapping the pin alloctaion in Excel pretty helpful.
I will add that the UTFT lib's are well documented and a joy to work with... Professional grade... For Free. I've not tested Oli's library but I suspect it's as good as any of the others.
louarnold:
I note however that the project here (http://www.janspace.com/b2evolution/arduino.php/2010/06/26/scooterputer) uses what is almost identical to an UNO and yet manages to interface to 4-5 devices including the TFT module. It doesn't leave many IO lines for talking to anything else, however. Is there a better mcu for this purpose? and if so, why is it better?
It looks like he ran out of pins, though, hence the DPDT switch. Maybe a Mega board wouyld have been a better choice. A UNO-type board can carry a lot of gear. I find mapping the pin alloctaion in Excel pretty helpful.
OK. I'll want to build a standalone function generator with the TFT and so a smaller board with more IO capability would be welcome.
Thank you.