adafruit accessories 5.0 40 pin 800x480 tft display without touchscreen factory

This 5.0" TFT screen has lots of pixels, 800x480 to be exact, and an LED backlight. Its great for when you need a lot of space for graphics. These screens are commonly seen in consumer electronics, such as miniature TV"s, GPS"s, handheld games car displays, etc. A 40-pin connector has 8 red, 8 green, and 8 blue parallel pins, for 24-bit colour capability.

adafruit accessories 5.0 40 pin 800x480 tft display without touchscreen factory

This 5.0" TFT screen has lots of pixels, 800x480 to be exact, and an LED backlight. Its great for when you need a lot of space for graphics. These screens are commonly seen in consumer electronics, such as miniature TV"s, GPS"s, handheld games car displays, etc. A 40-pin connector has 8 red, 8 green, and 8 blue parallel pins, for 24 bit color capability.

This version does not have touchscreen attached It"s exactly the same TFT display as PID 1596 but without the resistive touch panel so it is a little less expensive.

This is a "raw pixel-dot-clock" display and does not have an SPI/parallel type controller or any kind of RAM. The display is supposed to be constantly refreshed, at 60Hz, with a pixel clock, V sync, H sync, etc. There are some high end processors such as that used in the BeagleBone that can natively support such RGB TTL displays. However, it is extremely rare for a small microcontroller to support it, as you need dedicated hardware or a very fast processor such as an FPGA. Not only that, but the backlight requires a constant-current mode boost converter that can go as high as 24V instead of our other small displays that can run the backlight off of 5V

For that reason, we are carrying it as a companion to the Adafruit RA8875 driver board in the store, which is a chip that can handle the huge video RAM and timing requirements, all in the background. That"s the best way to interface this display to just about any microcontroller (including Arduino & friends) If you want to control with from an HDMI or DVI output, check out our TFP401 driver board. If you are an advanced electronics enthusiast you can try wiring this directly to your processor, but it we don"t have any support or tutorials for that purpose.

adafruit accessories 5.0 40 pin 800x480 tft display without touchscreen factory

This 5.0" TFT screen has lots of pixels, 800x480 to be exact, and an LED backlight. Its great for when you need a lot of space for graphics. These screens are commonly seen in c…

adafruit accessories 5.0 40 pin 800x480 tft display without touchscreen factory

Apart the infamous bugs, the RA885 chip it"s the only one that let you drive large displays (max 800x480) with touch screen and using very few processor resources.

Currently all Adafruit RA8875 variants and all BuyDisplay (eastrising) RA8875 variants. Only Waveshare has a product that on paper can be set for SPI but it"s not true so avoid it.

I"m not affiliated to any vendors but I think that 5" capacitive touch from buyDisplay it"s my preferred. The 7" it"s also good if you like big things but it"s a current sucker so forget battery.

All the buyDisplay has sd holder but it"s totally useless, even with SPI isolator circuit, but has Font Rom option, Flash Option (not easy to use), extensive pinouts and keypad connector.

The adafruit lacks of several features but has a 4050 for 5V compatibility, not very useful with Teensy. I will go for capacitive touch, it"s more fun!

The Eastrising cost from 39US to 43US , the adafruit 39US+47US(or 40US) and no capacitive, I got both solutions and they look almost the same but second one cost double and I don"t like to deal with ultrathis flat cables.

The Adafruit 4050 chip created some problems with the SPI isolator and audio board, haved to desolder, it was added for 5V mcu compatibility and useless with teensy.

Adafruit offer a 4.3" at that resolution, eastrising has a 5", it"s importan choose the right display size with RA8875 since you cannot change resolution by settings!

Ouch! Thanks for posting photo, I have the same display but everithing it"s solder on the board. I really hate FPC, my solder it"s too big and my eyes are not as well as before, they should post notes about this before sell!

So the 5.0" screen from BuyDisplay is 100% compatible using the 4-wire SPI using alternate pins while also using the Audio Adapter Board (http://www.pjrc.com/store/teensy3_audio.html)?

So the 5.0" screen from BuyDisplay is 100% compatible using the 4-wire SPI using alternate pins while also using the Audio Adapter Board (http://www.pjrc.com/store/teensy3_audio.html)?

If you"re using no other SPI devices, which means no SD card on the audio board and no 8-pin memory chip soldered on the bottom side, and no other SPI other than the RA8875 is connected, then I"d say there"s a pretty good chance it will work. Just make sure SPI.setMOSI(7) and SPI.setSCK(14) are called before you call RA8875.begin(). Then those pins will be used.

The first problem is the RA8875 doesn"t properly tri-state its MISO pin. You may need to add a tri-state buffer (www.dorkbotpdx.org/blog/paul/better_spi_bus_design_in_3_steps). Pullup resistors on the CS pins are also a good idea.

The other lurking problem might be lack of SPI transactions used in the RA8875 library. That"s not a big deal if you always access every SPI device from your sketch. But as soon as you use the audio library to access the SD card or a flash chip, or if you try to use a SPI-based radio module with an interrupt, you really need SPI transactions used properly in all the code accessing every SPI device. Without proper transactions, it may work for a while, but sooner or later a conflict will occur and your program will usually lock up.

I have tested it and produced a video together with Teensy 3.1 and audioboard, it was a spectrum analyzer and signal generator on a 7" display and worked pretty well.

If you"re using no other SPI devices, which means no SD card on the audio board and no 8-pin memory chip soldered on the bottom side, and no other SPI other than the RA8875 is connected, then I"d say there"s a pretty good chance it will work. Just make sure SPI.setMOSI(7) and SPI.setSCK(14) are called before you call RA8875.begin(). Then those pins will be used.

The first problem is the RA8875 doesn"t properly tri-state its MISO pin. You may need to add a tri-state buffer (www.dorkbotpdx.org/blog/paul/better_spi_bus_design_in_3_steps). Pullup resistors on the CS pins are also a good idea.

The other lurking problem might be lack of SPI transactions used in the RA8875 library. That"s not a big deal if you always access every SPI device from your sketch. But as soon as you use the audio library to access the SD card or a flash chip, or if you try to use a SPI-based radio module with an interrupt, you really need SPI transactions used properly in all the code accessing every SPI device. Without proper transactions, it may work for a while, but sooner or later a conflict will occur and your program will usually lock up.

Also there"s a new version of TFT_ILI9163C (https://github.com/sumotoy/TFT_ILI9163C/tree/Pre-Release-1.0r5), more stable and possibility of custom users fonts

So I just got my ER 5" display with capacitive touch with connector. That connector is SMALL! What do I do with this thing? The pins are too small to solder. And where do the pins go, to the Teensy board?

I found this on ebay (http://www.ebay.it/itm/5pcs-FFC-FPC-Adapter-Double-Side-6Pin-0-5mm-1mm-FPC-to-2x3Pin-2-54mm-DIP6-/151915086967?hash=item235ed84477:g:b78AAOSwzrxUuLs O), maybe help.

I found this on ebay (http://www.ebay.it/itm/5pcs-FFC-FPC-Adapter-Double-Side-6Pin-0-5mm-1mm-FPC-to-2x3Pin-2-54mm-DIP6-/151915086967?hash=item235ed84477:g:b78AAOSwzrxUuLs O), maybe help.

Okay, now I"m trying to figure out how these pins relate to everything else? Where do these 6 touch screen pins go? Do they connect back into the display, or do they connect to the Teensy?

I"m also trying to connect the display to the Teensy and can"t find any info on the pins I should use to connect to the Teensy. I"m using an Audio Shield but I won"t be using the SD Card.

I found the wiki picture (https://raw.githubusercontent.com/sumotoy/RA8875/gh-pages/docs/ER-TFTM050-3.png) of the TFTM050-3 display, still not clear on the pin #s they go to the Teensy while using Audio Shield, and it"s not clear on the 6 touch screen pins. For SPI connection can I use any pin on the Teensy labeled CS as long as I label it in the software? And the wiki says SCLK, is that the same on the Teensy as SCK (pin 13 & 14)?

I"m trying to power up the display and run the drawingTest example, but it looks like the display never powers up. I"m using the 3.3v from the Teensy to the SPI power and ground pins. I believe I"ve connected the alt pins correctly and the ran the appropriate set commands.

I got the display to at least power up, but with white colors and they change over time to more black when I set the video mode to 480x272 even though it"s a 800x480 display.

Whenever I run test_Initialization sketch it says "RA8875 initialized!" (it even says this when the display is not attached). But the screen is still almost all white and corrupt with black fading in over time. It"s like the backlight never turns on.

The test initialization sketch just test if you are using the right pins of your CPU but cannot access any data inside RA8875 to check if it"s correctly inited, I will add a feedback in the future to see if there"s almost a reliable link.

Inside RA8875 there"s a 2 PWM generators, in adafruit one it"s hardware with one of them to turn on display backlight, on buydisplay stuff this is user configurable by jumpers, in your case leave as described above, should be fine.

I will see later how you have connected the display, consider that RA8875 based display looks as dead if are not correctly inited so if you have an 800x480 you should init as RA8875_800x480.

Another issue I got in the past is that some display uses a lot of current when backlight it"s on, this happen at the end of initialization and in some case the current it"s so high that voltage drops and causes display RA8875 reboot of other unwanted stuff so check if this happen to you (connect a tester and check if the voltage it"s constant for all initialization process).

So when you turn on it"s all white then turn in black? This means that RA8875 controls with PWM the display as it should so there"s a kind of SPI connection working, as I said later I will look how you have connected and see if there"s any other issue.

If I used the standard RA8875 tft = RA8875(RA8875_CS, RA8875_RESET) in the example program then set alt pins from SPI.set****(#) before tft.begin(RA8875_800x480), it just didn"t work.

Now I need to investigate why it"s shutting down after a random amount of time. I"m using the 3.3v edge pin from the Teensy to power the display, which I"m assuming is not providing enough current from my USB port through the Teensy to the display. I suppose an external 3.3v source would fix the issue.

EDIT: I"ve measured the voltage to the display and it"s 3.17 volts (within the limit of 3 to 3.6). When the screen goes off the voltage jumps to 3.26, I guess because of no load. I even tried with an 850mA and a 2A USB AC adapter, same thing. Maybe it"s just pulling too many amps through the Teensy"s 3.3v supply even though it"s a 5" LCD and not the power hungry 7".

It looks like the display will draw about 450mA looking at the specs. I"m trying to figure out a way to tap into the supply 5 volts to convert it to 3.3 volts for the display. I tried a voltage divider using 2 resistors, but it seems to draw too much current through the resistor heating it up a lot.

The library has it own initialization, set pin before or after begin will not work, there a kind of wiki online, I will promise to write a complete wiki when 1.0 it"s out. RA8875 library has tons of commands because RA8875 has tons of features!

Some buydisplay (not all) have a regulator that can be feeded by 5V (by changing JP18) but some models have TFT too large and factory doesn"t mount the regulator because it just won"t fit.

The backlight of a 5" it"s really large (I have some 7" as well that consume really a lot), expecially when driving backlight at full brightness, try use the command tft.brightness(80); after begin to check if goes better, this will drop consume (the backlight will dim of course but it"s just for test).

The 1117 regulator should be fine but depends of input supplyl,it"s an LDO, easy solution but not really efficent and have a dropout of 1.2V, this mean that your input supply must be at list 4V and not less and going over 5V or LDO cannot provide full current and provide some kind of heatsink. I don"t know how much your TFT consume, I have noticed that chinese change TFT from time to time so it"s impossible read this data from datasheet (not reliable at all).

At initial power on when there"s still nothing on the display because it"s not initialized yet, it draws 200mA. Right when the screen turns on it draws 460mA. Not sure if that will change with full white displayed, as my test is the basicTextFunctions which has a black background with little text.

I"m using one of those premade 1117s from the link above, I think it already has caps. I do measure exactly 3.300 volts on the 1117 module output without a load. With the LCD load it does measure about 3.1 - 3.2 volts, which is fine because I believe the minimum for the LCD is 3v.

I tried taking 5 volts from my 4 pin molex power in the computer and put that to the 1117 which powers the LCD. Then I plug the USB cable from the computer"s USB port to the Teensy. I figure it"s all the same ground so at least that should help. But it"s the same thing. The LCD will power up and initialize sometimes, and the demo runs displaying text & numbers. But then it"s like the screen never clears the original text and characters start appearing in random areas. Maybe the reset line isn"t functioning.

I modified the basicTextFunctions to loop with no delay, without delay(1) function. I have it loop 99999 times while printing numbers then display the difference in milliseconds.

I found an interesting situation where one triangle can corrupt the display with vertical lines. I looks like at this angle it"s actually a line and I"m guessing the triangle registers don"t like drawing lines.

For get pixel I guess has something to do with screen resolution, the RA8875 works best with 480x272 because it maps the memory banks internally as separate pages but when used with higher resolutions it doesn"t have enough memory so it uses strange mapping methods and (if you are using layers) change it color depth at 8bit but internally try to expand colors in 16 to save internal RAM. Many functions are affected, try to scale a uploaded font char will cause a mess and so on.

So with the last bit of code, tft.fillTriangle(393,41, 400,40, 20,94, RA8875_WHITE);, do you see vertical lines too or some corruption? And if you test the random code I posted earlier, do you also see corruption? I want to make sure it"s not just me and my setup and wire length that"s causing corruption.

This allows my users to calibrate their touch screen without me having to modify the calibration data everytime. BTW thanks for the hardwork on this library, it made my life much easier

Being on a project halted for lack of proper means to display a needle (galvanometers are too slow and old technology. Precision is required) I"m wondering if a 5" to 7" display using RA8875 library would do the job of displaying a graphic needle to show variations similar to a VU-meter ? Teensy 3.1 or 3.2 plus external ADC are used in this project. If anyone can let me know if it is possible to display a graphic needle, clean, no jaggies, fast and visually attractive ?

You should be able to display a really fast meter with a needle. There"s even some examples he setup which use round meters with a needle. 800x480 5" or 7" should be able to draw a nice line without too many jaggies. Of course the closer you get the more you"ll see. You could always try a shading trick of dimmer colors right next to the needle to limit the jaggie effect. It can only look as visually attractive as you can program. There"s not really too much in the form of end products handed to you on a silver platter, so you"ll have to do some graphic programming to suit your needs. But there are plenty of examples for all functions needed. Checking out the ring meter example is a start and you should be able to build upon that.

As I tested previously the U8glib and UTFT libraries with various displays with some success but really toooooo slow and the only one lib fast enough I tested was the ILI9341_t3 I was wondering if the RA8875 was similar in speed to the ILI9341_t3 library.

As I tested previously the U8glib and UTFT libraries with various displays with some success but really toooooo slow and the only one lib fast enough I tested was the ILI9341_t3 I was wondering if the RA8875 was similar in speed to the ILI9341_t3 library.

The RA8875 is wicked fast. But it"s really the RA8875 chip that"s in the TFT display that"s fast. It has builtin hardware accelerated functions, like drawing a rectangle, square, or triangle. All you have to transmit to the TFT is just a little bit of code and the display takes care of if at hardware speeds. Sumotoy is doing a great job at building the library from the ground up that communicates to the RA8875 chip. The chip has many bugs and he has to create special code to work around those bugs. He"s also creating really fast font code too that should be compatible with many displays.

This is really the only TFT display that I"ve seen and have experience with, besides a 1.5" OLED display. I"m satisfied with the speed I"m getting on it while drawing lines, circles, squares, & triangles.

I ran a quick test on my 800x480 5" display and I can draw about 6150 random sized same color lines a second on the screen, and about 5340 random sized and random colored lines a second.

So perhaps a stupid question, but wouldn"t it make sense to communicate from a Teensy to a Raspberry Pi 3 and just send data having the Raspbery Pi 3 display it over HDMI to a real high resolution 5/7 inch screen?

So perhaps a stupid question, but wouldn"t it make sense to communicate from a Teensy to a Raspberry Pi 3 and just send data having the Raspbery Pi 3 display it over HDMI to a real high resolution 5/7 inch screen?

That would be awesome. I"m still hoping someone will create something along these lines for the pi zero (something like an open source and highly capable version of what companies like Nextion or 4G Systems are doing) - if the availability ever gets reasonable the price is hard to beat! But something like that would be a different animal entirely from what"s being done here with the RA8875. I"m no expert, but it seems this is our best option right now as hobbyists looking to interact with large screens. I"m using a 7" display from Buy Display on my current project with Sumotoy"s library. There are definitely limitations and oddities with the RA8875 itself, but on the whole thanks to the work that"s been put into the library, it"s incredibly usable and fast.

I"m using the newest Teensy 3.5 which is a 5.0v board as you probably know...so choosing between the BuyDisplay 5" and 7" screens, I would have to go with the 7" screen because its 5v right? The 5" 3.3v screen would not work on a 5v Teensy 3.5 board, right?

Teensy 3.5 is not a 5v board. All of its digital output pins are still 3.3v. It"s simply 5v-tolerant for digital input (but not necessarily other pins)

BuDisplay is only talking about powering the board when they differentiate between 5V and 3.3V. Get whichever is more convenient to power. The signal levels are 3.3V for all. There is an issue on the RA8875 wiki and issue list about the 5v not being option for the 5" because of a missing regulator, but I don"t believe this is a general concern. I"ve gotten a 5V 5" screen since then and it does have the regulator and works fine.

I"ve the 5" LCD from buydisplay. I"m trying to use the aerial_22 and aerial_48 font but they don"t look quite right. I"m expecting a bit more of an Arial font.