kuman 3.5 inch 320x480 resolution tft lcd display free sample

The 3.5 in touch screen can support two screens simultaneous display(the Raspberry Pi can be connected to this screen and another HDMI screen at the same time).

This 3.5 inch resistive touch screen can be directly inserted into the Raspberry Pi B+, 2B, 3B, 3B+. Raspberry Pi is not included. It also can work with Raspbian/Ubuntu/Kali/RETROPIE systems, We provide drivers and image freely. (Please scan the QR code on the instruction to download it)

The Raspberry Pi screen can work with fbcp software driver, you can adjust the resolution by the software (The RPI screen original resolution is 320×480).

The Raspberry Pi Display support 125MHz SPI signal input, It can display stable without Flicker. When it work with Raspberry Pi, the refresh rate is about 50fps, it is enough to play the video and game.

Kuman 3.5 inch 320*480 Resolution Touch Screen TFT LCD Display With Protective Case + 3 x Heat sinks+ Touch Pen for Raspberry Pi 3 Model B, Pi 2 Model B & Pi Model B+ SC11

So going to suggest that is a place to start, do double check all the pins since while the controller is the same whoever built the display may have swaped physical positions around, and it"s also not impossible for there to be different resolutions etc you need to tweak if the chip is using different physical displays but in this case suspect you are good to go.

@ bossredman- The XPT2046 is actually the touchscreen controller, not the TFT display controller. You say you don"t care about touch. The existing Teensy/Adafruit TFT display library is written for the ILI9341 TFT controller. This controller is capable of 320 X 240 max resolution. Your display is twice this. I strongly suspect it uses a different controller, so the existing library won"t work. That said, there is no reason the Teensy couldn"t drive your display if you can find a suitable driver. I have not personally seen other, higher resolution driver libraries mentioned in this forum, but others may have info that might help in this respect.

There are RA8875 based 5" and 7" TFT displays, and sumotoy has written a library for those. I"ve also used one and wrote my own driver (for ugfx) so that display family might be an option.

@bossredman: Since you are in the UK, you should take a look at the FT800 controller-based displays from FTDI, the UK firm that makes them. They have a very high performance TFT driver/graphics engine and you can get 3.5- 5" displays for less than the combo you listed above. FTDI supplies Arduino drivers for these displays- which I have used with the AVR chips found on Arduino boards in the past.

I took one of my spare FT800 4.3" TFT modules and wired it up to a spare Teensy LC I had on hand. The FTDI demo programs worked fine when compiled for Teensy LC- no changes needed. Should work OK on T3.6 as well. When I get a chance I"ll try it on my Kickstarter T3.5 module- I don"t have the T3.6 though.

I wrote several magazine articles centred around these FTDI FT800 displays a few years back, and I was impressed with them. The library routines are a bit harder to understand than the Teensy ILI9341 library, but this controller is MUCH more powerful.

Actually, I was looking for the wiring for a Teensy 3.2, not an STM. I saw your #defines in the code, they didn"t relate to the Teensy and my display which has different pin descriptions

Actually, I was looking for the wiring for a Teensy 3.2, not an STM. I saw your #defines in the code, they didn"t relate to the Teensy and my display which has different pin descriptions

MISO, MOSI and SCLK are necessary for the TFT to work. They are not exclusive of the SD card. The SPI interface is a bus: you connect the same SCK, MISO and MOSI to all the pertinent devices, then each device has its own CS=chip select.

I would like to use a ILI9486 TFT and TP with it. They both work fine with a Mega2560 and when I wire it up as per the declarations in https://github.com/palmerr23/ILI9486_Teensy_Library .h file and run the graphictest program in the examples folder, the screen lights up, but doesn"t reset or show any data. I"m wiring as follows;

As Kurt says, it"s important to know exactly what TFT hardware you have, and particularly if you have any other hardware or (particularly) SPI-related libraries used. Uninitialised SPI hardware can sometimes transmit on the bus, if the CS pin hasn"t been intentionally driven HIGH.

Turns out the board is SPIO for touchscreen and parallel for LCD. My mistake. I bought it on the basis it was SPIO for both. As a shield, it just plugs into a UNO/Mega. It"s only by going via a breakout board and wiring every pin and seeing when it breaks, I was able to confirm that the LCD is using the parallel interface.

Might try using the breakout board to wire the parallel interface to Teensy and test that or more likely, I"ll use this as an excuse to buy a larger (7") TFT which is definitely SPIO :-)

https://www.ebay.com/itm/3-5inch-TFT-SPI-Serial-LCD-Screen-Module-480x320-ILI9488-w-Touch-Support-65K/164144628286?hash=item2637c8423e:g:BAgAAOSwWG5egw0 0

Actually, I was looking for the wiring for a Teensy 3.2, not an STM. I saw your #defines in the code, they didn"t relate to the Teensy and my display which has different pin descriptions

Kuman 3.5 inch 320*480 Resolution Touch Screen TFT LCD Display With Protective Case + 3 x Heat sinks+ Touch Pen for Raspberry Pi 3 Model B, Pi 2 Model B & Pi Model B+ SC11

Is it this one: http://www.kumantech.com/kuman-35-inch-tft-lcd-display-480x320-rgb-pixels-touch-screen-monitor-for-raspberry-pi-3-2-model-b-b-a-a-module-spi-interface-with-touch-pen-sc06_p0014.html

Nto sure if RS is DC or not.. Maybe, but maybe not... Some like the KeDei display for RPI have a real screwy interface, using shift registers, and this may be similar...

Sorry not sure without more information... You might try our KeDei driver or the ILI9488 driver or HX8357 driver... As all three have that resolution...

Is it this one: http://www.kumantech.com/kuman-35-inch-tft-lcd-display-480x320-rgb-pixels-touch-screen-monitor-for-raspberry-pi-3-2-model-b-b-a-a-module-spi-interface-with-touch-pen-sc06_p0014.html

Beware though. I"m not out to bash BuyDisplay, I"ve used many of their displays in my projects. Mostly the 3-inch ILI9341 display with xpt-2046 resistive touch and the 4.3-inch display with capacitive touch and the 5206 (?) touch controler which both worked very well. They also have other touch controllers such as the GSL1680 on their 5-inch RA8875 display. The display is super nice and the display drivers work well with it. It"s the dang GSL1680 touch controller that has been a bear to get working, YES, I"m still trying. Some folks posted here that they got it working but I have had no such luck. So when you buy at BuyDisplay be sure to verify the touch chip you are getting. Besides that I do feel BuyDisplay is a good place to purchase displays. No bad feeling intended to other display vendors.

Yesterday, I wired the waveshare 4inch tft touch screen to teensy 4.1. One thing I had to change was the spi config on the display board. There are three switches to select the six pin spi connector or the outboard pins for spi.

Yesterday, I wired the waveshare 4inch tft touch screen to teensy 4.1. One thing I had to change was the spi config on the display board. There are three switches to select the six pin spi connector or the outboard pins for spi.

In cases like this it really helps others to help you, when we have additional information. Things like what display is this. I suppose we could do a search to see what boards waveshare produces that happens to be 4". What library are you using?

I don"t remember if this one in SPI mode uses 18 bit colors 666 (24 bits to SPI) per pixel or if it can use the 565 16 bit color like many of our displays do. The 88 can only do this in parallel mode.

I am using the example file that came on a CD with my display called "Example07-ShowBMP" (as mentioned above), so I copied and pasted the pertinent lines from the "SoftwareSpi.ino" file into the "Example07-ShowBMP" and tried to run it.

I still had issues after fixing this issue with this example file. It seems the bmpReadheader(File f) function has issues with the SDFat library. If I comment out the call to that function, the bitmaps are displayed, but they are shifted to the right by about 10 pixels.

I compared the serial values that are printed between the previously mentioned NANO connected to this display with hardware SPI and default SD library compared to the exact same display and SD card connected to a MEGA and using the SDFat.h file. I am including that serial output here:

I hope to add some serial print lines and try different things and look into the SDFat library and see if I can figure out what is going on. I am also convinced the example program I am using is not very well written, as I tried to change the size of the display and found that while they made height and width variables at the top of the program, they did not use those variables inside the function to allow the different sized displays to be easily used. I"m sure the SDFat library is fine, but it is not a plug and play with this particular display"s example programs. Once I get it resolved, I intend to post better example software on the Amazon page where I bought the display. I like the display, but I must think this would annoy many customers.

But with your low resolution screen I would suggest to minimize the data displayed (maybe use a page/profile module to switch between displayed information). Smaller font size will do much, maybe even change the font to a more pixelated font for clearer display.

Customers in many different industries have chosen this full color graphic TFT display module for its stunning 320x480 pixel 3.5-inch diagonal active area.