Your choice for 3.5inch display? - LilyPi, WT32-SC01, MakerFabs' ESP32S2, Lolin32+ILI9488 -
Вставка
- Опубліковано 10 вер 2024
- Recently, many ESP32 products with a display have been released. It is probably the products that target this because there are many projects that use the display. In this video, I chose a few products and compare them with a focus on performance. (LilyPi, WT32-SC01, MakersFabs' ESP32S2, Lolin32+ILI9488)
[ESP32 LILYPI]
bit.ly/3CWzEG9
[Makerfabs ESP32-S2]
www.makerfabs....
[WT32-SC01 Plus]
amzn.to/49xlwUG
#Display #ST7796 #ILI9488 #ESP32 #WT32SC01 #Makerfabs #ThatProject
For more projects - ua-cam.com/users/ThatProject
That Project Github Repository - github.com/0015/ThatProject
Join FB Group - facebook.com/groups/138965931539175
Thank you for the comparison between different 3.5 inch display, I am decided to buy WT32-SC01! Still hesitate between this and Makerfabs ESP32-S2 previously for making some project involves with display , very happy to see it has better in overall compared to Makerfabs product.
You can swap out the ili9488 TFT on the Makerfabs for a ili9481 IPS. A much nicer display with great viewing angles and it's a drop-in replacement. Just change the Lovyan panel instance in code.
That's interesting. Thank you for good information. I’ll try it.
Thanks for showing this
Thanks for the amazing explanation
Hello , great video !! Do you have some example using the wt32-sc01 ?
Maybe the makerfabs board whit esp32 in the version not s2 is more competitive whit the others in the same line talking about speed , i have very very bad experience whit makerfabs I use the boards capacitive 3.5 and are really slow , and no works good enough, maybe i will buy the last s2 but i think the Bluetooth is not build in the board .
Any way if you have more examples whit wt32 i will thank you so much
👍🏻
Bro please also share some good resource, for any project you makes, that will also be helpful!
ST7796+80MHz+DMA is the best
Cool info. Thanks!
🔥🔥
But Instead of ili9488 wouldn't be ili9341 preferred as it has more stable libraries if working on arduino projects?
@@advaitkulkarni8929 I prefer ILI9488 to ILI9341. The reason is that it can use DMA. However, in this video, only the 3.5-inch display is compared.
I created a Bosch ebike diag display with the normal wt32-sp01. Perfect micropython firmware : thanh01pmt/esp32-wt32-sc01-micropython-lvgl-squareline . The CAN is jxltom/micropython-mcp2515 . The trick: connect mcp2515 via softSPI. Why the normal wt32-sp01? This has super gpio connectors. As I know, today this is the only suitable board for this purpose.
Excellent. I think the WT32-SC01 is also a good device. Before Plus came out, I also did a lot of projects with it.
Thanks for the interesting video. I think 2 parameters are missing to compare: 1) How easy is to develop the GUI - very important for projects. 2) how many IOs are left. Also - is there any limit with using ESP-now while using the screen?
[1] GUI development varies depending on which tool is used. GUI development is still not easy in an MCU environment. Squareline Square seems to be the best for now.
[2] ESP-NOW works well no matter which module is used. The best option for GPIO is to use the SPI interface. Therefore, WT32-SC01 is advantageous. Personally, I recommend WT32-SC01 Plus.
Superb 👍
those displays only output 60fps right
Hi, thank you for your comparison. I am not sure which one performs best in the last test. Please say your order of preference between WT32-SC01 and Makerfabs ESP32-S2.
If you prefer an SPI connection, the WT32-SC01, or if you need the ESP32-S2, Makerfabs' ILI9488 seems to be a good choice.
@@ThatProject Thank you, noted your reply.
I have problems setting the WT32-SC01 could you help me with a tutorial about it?
What setting is the problem with WT32-SC01?
Thank your share ~~
Any guidance on the ili9488 and 8266 only displaying a white screen.
I connected the ILI9488 and ESP8266 in this video. Please note. ua-cam.com/video/9wrHhbfYFXg/v-deo.html
I got a WT32-SC01 but I can't get it to work at 80mhz SPI, so it's significantly slower. (I did make sure it's using HSPI/IO_MUX) What's your secret?
No way, there is no secret at all. I just used LovyanGFX as the graphic driver. That's all.
@@ThatProject weird, i'm using the same driver. I just get a white screen when I set it to 80mhz
@@ftab Sorry I have no idea. I think you have to ask about this issue with the manufacturer directly. There may be hardware differences that we are not aware of.
Excellent comparison. I am looking for an HMI display for my project. Can you also create a video on ease of designing GUI for each of these displays ? Or are you just using same LVGL ports for all 4 of them?
They all have the same source code, only the graphics driver has been changed. I think my LVGL projects can teach you how to do GUI work. ua-cam.com/play/PLnq7JUnBumAzjd7Nz6O6fIegE49LAMBFv.html
@@ThatProject Thank you.
Please help build an oscilloscope to use with WT32-SC01?
Wow! Are you trying to make your own oscilloscope?? That'll be super cool if it works.
R61529 may be a good choice, supports RGB565
Where did you get those demo codes? Could you please those codes? Or just tell some keywords.
They are from the example of TFT_eSPI. You can find them from it.
TFT_graphicstest
Thank you! @@ThatProject
Thank you for this video. I'm trying to make a CAN digital dash for my microsquirt projects and I think this might fit the bill. Have you seen the stm32f7 models with the 4 or 5 inch display?
Unfortunately, I haven't had a chance to do a project with STM32. I'm sorry I couldn't help you.
@@ThatProject thank you for the reply. I converted a old dirtbike to efi and want to dona digital dash that read the data stream from the can bus. Can you sugest which one you think would work best?
@@mastermoarman Does the device support RS485 interface?
@@ThatProject no its a CAN bus
The STM32F7 is a beast but the STM ecosystem is horrible to work with in my opinion. TouchGFX is nice but CubeMX is a minefield. Probably fine if you're a full time hardware/software dev and have a grasp of C++ but otherwise an ESP32 diplay with Squareline or GuiSlice is much more friendly, especially the backend business logic in Arduino IDE. Plenty of canbus resources to learn from. Going to STM32 groups is like they're all speaking a different language lol
can i connect an arduino to the esp32 s3 parallel via Uart?
Can't we just connect two devices, Arduino and ESP32-S3, through RX and TX? what are you going to do?
@@ThatProject i am considering buying this one with the parallel TFT to control my arduino which controls stepper motors and my camera (its a focus stacker). I think its better to seperate the UI and the control loops for better performance because i guess if i would drive a tft and control a stepper at the same time with the same microcontroller, then the speed of the motor would be way to slow due to the "slow" rendering speed.
@@ipadize Understood. Is it difficult to configure your system with a single microcontroller? It seems that handling everything with one MCU can be handled faster than connecting two MCUs with UART.
I need one with backlight parameter
Is it difficult to force the backlight to turn on in code?
YAY is the code available for WT32-SC01 thanks...
Please check this Github. github.com/sowbug/WT32-SC01-Demo It's gonna be a good starting point for your WT32-SC01.
Hi, your video is quite good. is there any interest to know about other display? I already left message to you via FB:)
what you mean? another 3.5 inch LCD controller interface review?
ı THİNK you are missing the point, 16-bit parallel is the best because you have bottleneck either at the gpio transision speed or overloaded ESP32-S2 MCU core. You can compare the speed with more powerful MCU. (check that out: ua-cam.com/video/ZtCMIAmLSh8/v-deo.html)
Now, What do you think?
You are right. 16-bit parallel connection is theoretically the fastest. The problem is that when we create our application we are not sending pixel data directly via GPIO. Instead, it completes the connected display through a graphics driver/library, which has different performance depending on how the screen is drawn. What I want to say is that, because we ultimately have a layer called a graphics driver, there is a difference in performance depending on this as well. (Again, if we directly control the GPIO and draw the screen, 16-bit is the fastest)