

🌈 Elevate Your Projects with Vibrant Clarity!
The Teyleten Robot 1.28 Inch TFT LCD Display Module is a compact, high-resolution display designed for Arduino projects. With a stunning 240x240 RGB resolution and a versatile SPI interface, this module is perfect for developers looking to enhance their creations. Operating efficiently within a wide temperature range, it combines functionality with a lightweight design, making it an ideal choice for both hobbyists and professionals.
| RAM | LPDDR |
| Brand | Teyleten Robot |
| Operating System | Linux |
| Item Weight | 1.76 ounces |
| Product Dimensions | 1.77 x 1.38 x 0.79 inches |
| Item Dimensions LxWxH | 1.77 x 1.38 x 0.79 inches |
| Processor Brand | ARM |
| Number of Processors | 1 |
| Manufacturer | Teyleten Robot |
| ASIN | B0B7TFRNN1 |
| Country of Origin | China |
| Date First Available | July 27, 2022 |
K**R
Happy with these displays!
These small displays are exactly what I wanted for compact, polished UI elements—think clocks, gauges, and animated “eyes.” Colors are vibrant, brightness is solid for indoor projects, and text/graphics are crisp thanks to the tight pixel density. I had them running in minutes on Teensy using available libraries (TFT_eSPI / Adafruit_GFX with GC9A01 support), and refresh performance is snappy enough for smooth animations. The 3-pack is great value for multi-display builds or spares, and all three modules were consistent in color and alignment. Also: they’re happiest at 3.3V logic; if you’re on a 5V board, use level shifting or the 3.3V pin. Overall, reliable, easy to integrate, and perfect for projects where a round, modern look makes the difference.
D**I
Works well with TFT_eSPI and ESP32 D1 Mini
Each device came in a separate plastic case within an anti-static bag. Below is the minimum config (User_Setup.h) you can use for this display and it will work. Change PIN numbers to suit your needs for your ESP module. #define GC9A01_DRIVER // For CYD ESP32-2432S028 #define TFT_WIDTH 240 #define TFT_HEIGHT 240 // For ESP32 Dev board (only tested with GC9A01 display) // The hardware SPI can be mapped to any pins #define TFT_MOSI 21 //SDA In some display driver board, it might be written as "SDA" and so on. #define TFT_SCLK 22 //SCL #define TFT_CS 16 //CS Chip select control pin #define TFT_DC 17 //DC Data Command control pin #define TFT_RST 4 //RST Reset pin (could connect to Arduino RESET pin) // Comment out the #defines below with // to stop that font being loaded // The ESP8366 and ESP32 have plenty of memory so commenting out fonts is not // normally necessary. If all fonts are loaded the extra FLASH space required is // about 17Kbytes. To save FLASH space only enable the fonts you need! #define LOAD_GLCD // Font 1. Original Adafruit 8 pixel font needs ~1820 bytes in FLASH #define LOAD_FONT2 // Font 2. Small 16 pixel high font, needs ~3534 bytes in FLASH, 96 characters #define LOAD_FONT4 // Font 4. Medium 26 pixel high font, needs ~5848 bytes in FLASH, 96 characters #define LOAD_FONT6 // Font 6. Large 48 pixel font, needs ~2666 bytes in FLASH, only characters 1234567890:-.apm #define LOAD_FONT7 // Font 7. 7 segment 48 pixel font, needs ~2438 bytes in FLASH, only characters 1234567890:-. #define LOAD_FONT8 // Font 8. Large 75 pixel font needs ~3256 bytes in FLASH, only characters 1234567890:-. //#define LOAD_FONT8N // Font 8. Alternative to Font 8 above, slightly narrower, so 3 digits fit a 160 pixel TFT #define LOAD_GFXFF // FreeFonts. Include access to the 48 Adafruit_GFX free fonts FF1 to FF48 and custom fonts // Comment out the #define below to stop the SPIFFS filing system and smooth font code being loaded // this will save ~20kbytes of FLASH #define SMOOTH_FONT // Define the SPI clock frequency, this affects the graphics rendering speed. Too // fast and the TFT driver will not keep up and display corruption appears. // With an ILI9341 display 40MHz works OK, 80MHz sometimes fails // With a ST7735 display more than 27MHz may not work (spurious pixels and lines) // With an ILI9163 display 27 MHz works OK. // #define SPI_FREQUENCY 1000000 // #define SPI_FREQUENCY 5000000 //#define SPI_FREQUENCY 10000000 //#define SPI_FREQUENCY 20000000 //#define SPI_FREQUENCY 27000000 #define SPI_FREQUENCY 40000000 //#define SPI_FREQUENCY 55000000 // STM32 SPI1 only (SPI2 maximum is 27MHz) // #define SPI_FREQUENCY 80000000
H**S
Not bright enough for me, but worked great!
These are good, the clarity on the screens is sharp and the colors stand out against a very black background. My main complaint is that they are not bright enough, and there is no pin to control the brightness of the backlight. That said, I had no issue connecting these to either ESP32 or Pico 2W. ESP32-S3-DevKitC1 however did not work and I suspect it was the library and not the display. No hit on my rating from that. They came with sticky-covering on the display surface to protect it, a plus for me. They ran on 3.3 just fine. Adequately marked for pin designations. I WILL buy more of these to fill out my gauges for all sorts of things, unless I find a better deal with a brighter display that has a pin to PWM the back light.
C**R
Very nice looking display and easy to use
These round 240x240 TFT displays look great. All three displays work with no problems. They use RGB565 16-bit color format = 65K colors. They work with the Adafruit and TFT_eSPI Arduino libraries. The clock video uses the LVGL Arduino library.
P**R
Works on esp32 WROOM and c2 mini, not on c3 super mini
I built a little case for one of these, an esp32s2-mini, and 5v to 3.2v converter. The photo is things dry-fitted and there is sanding and varnishing left to do. The wood is Camaroon Mahogany. I have only used these with the TFT_eSPI library which does NOT work with esp32c3 super mini processors (boot loops). The display does work with that library on WROOM parts using the display connections in the header file below. Also with the esp32s2-mini parts. I really wish they would not solder the pins on because it limits how you package it later. The library has many example sketches at least some of which are tailored to rectangular displays and so the corners are naturally cut off. ## tft_setup.h file in local project directory for the WROOM processor { #define GC9A01_DRIVER //esp32 pin numbers #define TFT_MOSI 23 // esp32 pin 23 to SDA pin on display #define TFT_MISO 19 // no connection to display #define TFT_SCLK 18 // SCL pin on display #define TFT_CS 5 // CS pin on display #define TFT_DC 15 // DC pin on display #define TFT_RST -1 // no programmatic reset #define LOAD_GLCD // Font 1. Original Adafruit 8 pixel font needs ~1820 bytes in FLASH #define LOAD_FONT2 // Font 2. Small 16 pixel high font, needs ~3534 bytes in FLASH, 96 characters #define LOAD_FONT4 // Font 4. Medium 26 pixel high font, needs ~5848 bytes in FLASH, 96 characters #define LOAD_FONT6 // Font 6. Large 48 pixel font, needs ~2666 bytes in FLASH, only characters 1234567890:-.apm #define LOAD_FONT7 // Font 7. 7 segment 48 pixel font, needs ~2438 bytes in FLASH, only characters 1234567890:. #define LOAD_FONT8 // Font 8. Large 75 pixel font needs ~3256 bytes in FLASH, only characters 1234567890:-. #define LOAD_GFXFF // FreeFonts. Include access to the 48 Adafruit_GFX free fonts FF1 to FF48 and custom fonts #define SMOOTH_FONT #define TFT_WIDTH 240 #define TFT_HEIGHT 240 #define SPI_FREQUENCY 40000000 #define SPI_READ_FREQUENCY 20000000 #define SPI_TOUCH_FREQUENCY 2500000 ### }
C**E
Les 3 écrans sont arrivé emballés chacun dans leur était et sont tous fonctionnel. Je les aies mis sous 3.3v .. certaines spec disent 3.3 et 5 .. mais je ne sais pas si je m'y risquerait comme is fonctionnent bien sous 3.3V. on les voit parfois directement connecter à des Arduino Nano, mais certains NANO sont en 3.3V. je les aies connecté à un DUE
A**R
2 out of 3 displays don't work. One was broken out of the package - only the backlight worked. The other was working for about a day, then did some weird behaviour and causes the voltage regulator on any arduino it is connected to, to fry - I assume an internal short that's drawing a ton of current. The third display has been fine so far, but be warned, these could wreck your arduino - test them first. When they work, they work well though. For whatever reason, the ATMega Nano models don't like these displays and get into SPI conflicts, but ESP32 is fine if using the Adafruit library not the boden tft one. Had some luck with a NANO Every.
Trustpilot
Hace 2 semanas
Hace 2 semanas