HiLetgo 2.4" ILI9341 240X320 TFT LCD Display with Touch Panel LCD for Arduino UNO MEGA2560
Score By Feature
OveReview Final Score
Product Description
Questions & Answers
It's just a screen with a touchpad on it. You can program it to do whatever you want with whatever microcontroller you connect it to, but you won't be able to display much text on it, especially if you want to use it as a virtual keypad. Best wishes to you. For that, you'd be better off investing in a larger screen and a keyboard.
As far as I'm aware, there aren't any. This device's library is written for Arduino, according to the Wiki.
There are no mounting holes, but it plugs into an arduino, so mount the arduino if you do it that way.
The stylus isn't required; it simply provides a finer point for increased precision. br>br>For the most part, I use my finger.
Selected User Reviews For HiLetgo 2.4" ILI9341 240X320 TFT LCD Display with Touch Panel LCD for Arduino UNO MEGA2560
Although there is no documentation included with the display, finding the drivers that work is not difficult. br>br>The MCUFRIEND has been mentioned in a number of reviews on this site. You'll also need the Adafruit GFX library, which the MCUFRIEND library depends on, as well as the Adafruit Touchscreen library if you want to read touch. It is not necessary to install a because all of them can be installed directly from the Arduino IDE. It was relatively painless to get the demo file running on a MEGA2560, a Due, and a Teensy 3. br>br>Once installed, it was relatively painless to get the demo file running on a MEGA2560, a Due, and a Teensy 3. 2 that will be mounted on a Sparkfun Uno shield adapter in no time. It's worth noting that getting the touchscreen calibration demo to work on a 32 bit board is a pain in the neck, so I used the MEGA to handle the touchscreen pin detection and calibration, and the calibration works on both the Due and the Teensy - For this board, I've included the calibration results below. br>br>Values from the graphicstest. kbv example file, starting with the MEGA2560, Due, Teensy 3, are shown in my photos, from left to right. 2 stock clocks, then 96 and 120 MHz overclocks The performance difference between the 8-bit MEGA and the 32-bit Due is immediately apparent. The final image is from the testcard. kbv demo file. br>br>The parallel interface on this board is fast in comparison to SPI, and it responds well to boards with faster clock speeds! I strongly advise switching to a 32 bit board if you really want to get the most out of this display. br>br>Calibration result for this board:br>TouchScreen. h GFX Calibrationbr>Making all control and bus pins INPUT_PULLUPbr>When digital is written LOWbr>e, a typical 30k Analog pullup with corresponding pinbr>would read low. reads a value of 25 for the 300R X directionbr>e. Tests: 30 for 500R Y directionbr>br>Testing: 30 for 500R Y directionbr>br>Testing: 30 for 500R Y directionbr>br>Testing (A2, D8) = 25br>Testing: (A2, D8) = 25br> br>Diagnosis: (A3, D9) = 30br> XM,XP: XM,XP: XM,XP: XM,XP: (A2, D8) = 25br>YP,YM: (A2, D8) = (A2, D8) = (A2, D8) = (A2, D8) = 25 (A3, D9) = 30br>ID = 0x9341br>br>br>cx=143 cy=113 cz=518 LEFT, TOP, Pressurebr>cx=155 cy=496 cz=375 LEFT, MIDH, Pressurebr>cx=145 cy=874 cz=200 LEFT, BOT, Pressurebr>cx=518 cy=878 TS_LEFT=113,TS_RT=923,TS_TOP=93,TS_BOT=898; const int TS_LEFT=113,TS_RT=923,TS_TOP=93,TS_BOT=898; const int TS_LEFT=113,TS_RT=923,TS_TOP=93,TS_BOT=898; br>br>PORTRAIT CALIBRATION 240 x 320br>x = map(p. p. p. p. p. p. p. p. p. p. p. p. p. p. p. p. p. p. p. p. p. p. y = map(p. x, LEFT=113, RT=923, 0, 240)br>x, LEFT=113, RT=923, 0, 240)br>x, LEFT=113, RT=923, 0, 240 x = map(p. y, TOP=93, BOT=898, 0, 320)br>Touch Pin Wiring XP=8 XM=A2 YP=A3 YM=9br>LANDSCAPE CALIBRATION 320 x 240br>x = map(p. y, TOP=93, BOT=898, 0, 320)br> y = map(p, LEFT=93, RT=898, 0, 320)br>y = map(p, LEFT=93, RT=898, 0, 320)br>y = map(p, LEFT=93, RT= 0, 240) x, TOP=923, BOT=113) x, TOP=923, BOT=113) x, TOP=923, BOT=113.
I used the MCUFRIEND_kbv library from GitHub, and everything worked right away with the graphics test program that came with the library examples. The display arrived alive and well, with no bent pins or other issues; the most difficult part was locating the appropriate library to power it. According to what I could find, there are a slew of TFT displays that look the same on the outside. I experimented with two different sets of code/libraries for displays that appeared to be the same but were not. To get right to the point, download the MCUFRIEND_kbv library and begin experimenting. br>br>Also, an Arduino Mega is likely the best choice for this display. On my UNO, running the MCUFRIEND_kbv graphics test sketch uses 30610 bytes or 94% of program storage. I tested it on a Mega, and it appears to work similarly to an UNO. br>br>This received a four-star rating from me. I gave it five stars because it appears to be quite cool, and I have a Mega that I can use it with. If there was more information to back it up, it would be given more stars. There was no documentation, no links, and nothing but Amazon reviews directing people to the right place. I'm pleased with my purchase and intend to use it for my current project.
There is no documentation included with this unit, and there is no tutorial available on the manufacturer's website. This is supposed to use the same IL9341 driver as the well-documented Adafruit TFT displays, but if you try to use the Adafruit_TFTLCD libraries and examples, it doesn't work - The diagnostics are also unable to identify the chip due to a blank backlight screen. br>br>The good news is that it is fully compatible with the MCUFRIEND_kbv library on github. The display is also significantly faster than Adafruit displays that use SPI to transfer data. This chip's 8-pin data implementation uses a lot of digital pins, but the display speed is much faster as a result.
If you plan to use it on one of the larger Arduino boards, this model will work (the pins in the picture should line up perfectly with the connectors on your Arduino board). If you want to use the display with other microcontrollers (such as the ESP32, ESP8266, or even the Arduino Pro Mini), you'll need to purchase a different model. When conducting online research, both screens appear to be identical; however, pay close attention to the pinouts on the back of the screen. The 8-foot model you're looking at is the one you're looking at. parallel version in bits The "SPI" is a different variant. br>br>Here's a link to the SPI version (which requires fewer connections and has a lot of information online about how to connect it to faster microcontrollers):
.
With the libraries available, I was able to achieve good results with this TFT. I tried it out on a Due I had lying around, and it works great with the mcufriend library right out of the box. Under normal lighting conditions, the brightness is adequate. It could be a little faster, but this is a low-cost option that gets the job done. Meaning it's worth the $9 I paid!br>br>The description claims that digital pins 2 and 3 are available, but these pins are labeled LCD_02 and LCD_03 on the back of the board. If you don't use the SD card, you can free up a few more pins. When the RST function is defined, analog pins 4 and 5 are claimed to be available, but analog 4 is marked LCD_RST, leaving only analog 5 available.
The price is incredible! Download the MCUFRIEND_kbv library from GitHub, unzip it, and place it in the libraries folder where your Arduino IDE is installed. The MCUFRIEND_kbv library works perfectly with this LCD touchscreen. I put this to the test on a Hiletgo Arduino Mega, Uno, and an Italian Uno. Everything was in order. I'm going to order more of these little touchscreens because they're such a good deal. It's much easier to wire a shield than it is to wire a separate LCD display.
Related Products For HiLetgo 2.4" ILI9341 240X320 TFT LCD Display with Touch Panel LCD for Arduino UNO MEGA2560
