kuman 3.5 inch tft lcd display monitor free sample

Note: There is a film on the LCD, if there is scratch on the film when you receive the item, pls try to remove the film with your finger nail from the corner of the LCD, thanks.

I bought online this LCD Touchscreen Kuman SC3A-NEW-UK. It uses ILI9486 drivers, but it didn"t include any instructions manual, and kumantech.com seems to be devoid of complete technical documentation about SC3A-NEW-UK model.

Just in case it wasn"t noticable: I am trying to make a "Hello World" for my SC3A-NEW-UK"s LCD Touchscreen from an Arduino UNO board. In other words: just print "Hello World" to see if it works.

This compiled in Arduino IDE, no problem, but I still don"t know if it will work well with my screen. I am also confused about initialization of the TFT object and how would I have to wire the LCD screen to the Arduino depending on this initialization:

...i mean, my LCD screen has CS and RESET pins, but what is DC supposed to be here? (in this context, I don"t think it stands for "Direct Current"... but there"s no DC pin reference in my LCD screen written "AS IS"... ?? This brings me more confusion...

...specially having in mind that I don"t know how am I supposed to wire the LCD screen to the Arduino yet. It seems the LCD pins have been designed to fit in directly to the Arduino board without thinking too much about it (like the shape is the same), but that would make the screen getting all the Arduino UNO"s pins for itself, so I don"t think so...

...so, powering the screen shouldn"t be a big deal, but, how am I supposed to connect everything else? I am completely misguided about how am I supposed to interact with the screen from Arduino code... what is RS pin for? Should I use 4-bit or 8-bit mode? (I think 4-bit would imply connecting 4 digital pins for the screen, and 8-bit the whole 8 pins from screen to the Arduino UNO board)? Should I use LCD_RD and LCD_WR? Well you have a picture of my confusion.

Even though I know how to control Input/Output in Arduino code to interact with analog/digital input and output pins at will with C++ in Arduino code (but even so, I think I"m still an Arduino n00b), this LCD screen"s physical interface is very confusing to me...

PD: I have read somewhere that this SC3A-NEW-UK Touchscreen is made to shield Arduino MEGA boards (by fitting the PINs directly into it), but mine is an Arduino UNO Board! (perhaps I shouldn"t have bought This LCD model, then?)... but I have sets of wires, pinboards and stuff... I don"t want to give up the idea of harnessing this LCD screen using an Arduino UNO. I don"t care about shielding feature, I just want to wire it and make it work. I will figure out how to shield electronics later on.

I put NONE for A5 input, because that pin of LCD screen doesn"t have any name on it. There are another ones without name as well, that I didn"t include in this table. I believe (perhaps I"m wrong believing it, I don"t know) that those pins without name have no use.

I still don"t know much of the details about what pins do what for the screen, but I have read somewhere that LCD_D0 to LCD_D7 are meant to receive digital data in some kind of 8-bit parallel mode. But I also heard that there is a 4-bit mode. If I could use that mode with this screen, I would be able to have 4 free digital pins for anything else...

I tested VE7JRO"s code. LCD Screen did draw the interface as expected. But buttons didn"t respond. I found out the code sample needs further calibration.

So, I started printing through the Serial the coordinates of the object TSPoint p, to find out if there was something wrong with the z coordinate. And indeed, there was: setting MINPRESSURE and MAXPRESSURE according to what I saw in Serial Monitor while I pressed and I didn"t pressed, fixed this. However, there"s another more issue...

There are 22 test sketches that come with the MCUFRIEND_kbv library. One of them scans your display and outputs configuration information (sorry, it"s been a while since I tested my screen). Another sketch will draw little boxes in each corner and sides. This is used to get the x y coordinates of the edges of your particular screen (it might be called TouchScreen_Calibr_native.ino).

The fifth parameter is supposed to be the resistance measured between LCD_D6 and LCD_RS with the screen unplugged. Unfortunately, my multimeter can"t measure it for some reason (I put it in 2000 Ohms mode for reading resistance: I always get "1", the same than when I don"t connect anything... like if multimeter"s contacts aren"t working well, I don"t know)... so I left the default 300 value.

In this Arduino touch screen tutorial we will learn how to use TFT LCD Touch Screen with Arduino. You can watch the following video or read the written tutorial below.

For this tutorial I composed three examples. The first example is distance measurement using ultrasonic sensor. The output from the sensor, or the distance is printed on the screen and using the touch screen we can select the units, either centimeters or inches.

As an example I am using a 3.2” TFT Touch Screen in a combination with a TFT LCD Arduino Mega Shield. We need a shield because the TFT Touch screen works at 3.3V and the Arduino Mega outputs are 5 V. For the first example I have the HC-SR04 ultrasonic sensor, then for the second example an RGB LED with three resistors and a push button for the game example. Also I had to make a custom made pin header like this, by soldering pin headers and bend on of them so I could insert them in between the Arduino Board and the TFT Shield.

Here’s the circuit schematic. We will use the GND pin, the digital pins from 8 to 13, as well as the pin number 14. As the 5V pins are already used by the TFT Screen I will use the pin number 13 as VCC, by setting it right away high in the setup section of code.

I will use the UTFT and URTouch libraries made by Henning Karlsen. Here I would like to say thanks to him for the incredible work he has done. The libraries enable really easy use of the TFT Screens, and they work with many different TFT screens sizes, shields and controllers. You can download these libraries from his website, RinkyDinkElectronics.com and also find a lot of demo examples and detailed documentation of how to use them.

After we include the libraries we need to create UTFT and URTouch objects. The parameters of these objects depends on the model of the TFT Screen and Shield and these details can be also found in the documentation of the libraries.

So now I will explain how we can make the home screen of the program. With the setBackColor() function we need to set the background color of the text, black one in our case. Then we need to set the color to white, set the big font and using the print() function, we will print the string “Arduino TFT Tutorial” at the center of the screen and 10 pixels  down the Y – Axis of the screen. Next we will set the color to red and draw the red line below the text. After that we need to set the color back to white, and print the two other strings, “by HowToMechatronics.com” using the small font and “Select Example” using the big font.

Here’s that function which uses the ultrasonic sensor to calculate the distance and print the values with SevenSegNum font in green color, either in centimeters or inches. If you need more details how the ultrasonic sensor works you can check my particular tutorialfor that. Back in the loop section we can see what happens when we press the select unit buttons as well as the back button.

Rotating the screen to the proper orientation proved challenging. The config.txt rotate commands don’t work with the raspberry pi4. I couldn’t get the xorg configuration to rotate the display. When I added kernel commandline parameters to rotate the display, that worked for the initial verbose boot screen… but once KlipperScreen loaded, it was the wrong orientation.

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...

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.

There is one issue that I have not looked into is the fact I have to connect the serial monitor before the graphics test will run. The pin numbers for the teensy 4.1 were identical to the mega or due.

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.

There is one issue that I have not looked into is the fact I have to connect the serial monitor before the graphics test will run. The pin numbers for the teensy 4.1 were identical to the mega or due.

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?

Which waits up to 5 seconds for the serial monitor before it continues. This gives you some time to get it open and not lose output, but continues if you don"t. Also this works mainly at start of program. More generic, is to do something like:

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.