I respect your work, and i have learned a lot from your guides and videos, it motivates me to go further and dig deeper to solve problems,and i regained my pleasure for electronics, thx!!
This seems to be a 16bit parallel board but your video indicates that only 8 data lines are to be connected. Is this correct? If so, what is the impact of only using the lower 8 bits? Thank you...
@@yasyasmarangoz3577On most controllers you have Pins that you can pull up or down to choose between for example 8 or 16 bit mode. So you can control the display with 16bit parallel for best performance or because you dont have that many pins you can choose to use 8 bit
I have this display, it's the largest one I could find that was self-driving with breakout pins. It's able to be driven in a 16-bit 5-6-5 parallel mode if you need the speed and have extra I/O. Using a Teensy 3.6 I was able to update the entire screen at 30fps, very satisfying for a microcontroller. Got it on Ebay about 5 years ago. Nice size, 18-bit colour but I could not get the gamma correction working so I compensated in software. Touch screen is 4-wire resistive-type. The display is 800x480 pixels and is best viewed straight on or from *one* of the long sides, otherwise the colours go weird and I never tried any portrait mode. The backlight is controllable but requires 5 volts @ 400mA for it's boost converter. Signals are 3.3v only and not 5v tolerant. Supply should be capable of ~200mA. The driver is a SSD1963 by Solomon Systech, the touch screen controller is a generic HR2046 as far as I know. The SD card breakout is SPI mode only. That's what I know about this board.
Hello excellent as always, I am from Colombia and sometimes I visit your channel in English language just to know what is coming in the Latino🙈..... channel. It would be very interesting that in this project you can apply the LVGL library for the user interface and indicators, and incidentally transmit that teaching since there is little information in Spanish, thank you very much for your time and valuable teaching.
Just wondering: is the 8-bit parallel data transfer really that much faster than ex. I2C? The latter often has a (partial) HW implementation, whereas I guess the parallel transfer is using bit-banging, so I wonder whether I2C would not allow higher frequencies than such a parallel interface thereby reducing the gain of having 8 parallel lines and it would definitely be a lot easier to connect ... As said, just wondering. Since really high-speed serial busses rule (each PCIe lane, USB, ...), I really think micro-controllers need a reliable, super fast and super cheap serial bus to avoid the need for such parallel GPIO-pin consuming connections ...
Hello MisterkeTube, I don't know if you are still interested in this topic, but since no one has answered your question, I'll be happy to explain. Basically, since I2C is 2 wires, one of them being clock (SCL), and the other one being data (SDA), it inherently is unable to send data at as fast speeds as if it was going through multiple wires. I2C can send 3.4Mbits of data per second, which sounds fast, but think about 800x480 pixels, and their 16-bit colour data. That's 384K pixels, and 65536 colours for each pixel. I2C can't run as fast because of wire capacitance, which basically holds the electrical charges for a bit, messing up sync, and maybe even ruining the signals all together. To run I2C as fast as parallel, you would essentially need copper traces infinitely thin, that, or significantly out of manufacturing tolerances (probably less than 2 mil). This would actually end up being even more costly than parallel 8-bit, since ESP32-S3, ESP32 already have it. Yes, parallel interface does take up many wires, but it can reach much faster speeds because of it. An analogy is like: think of one man carrying heavy weights from one place to another, one at a time. Now, get about 15 of his friends to help him out, so that they are all doing it at the same time, and you can imagine how much incredibly faster this is. You can imagine the one man by himself being I2C (since it only has one data wire), and the 16 men being parallel interface. Although it is unfortunate how many wires parallel takes up, it is about the best we have got (at least that I have seen) at this stage. Once you get past like 480x320 pixel (normally using QSPI or really really fast SPI [like 80 - 125MHz]), everything just uses parallel interface.
Great brother really good; hyped for the next part. Very informative, liked the work through as it’s real tough to find these kind of tutorials, Be blessed brother ❤
Why doesn't the standard display library comes with command to erase or fill the screen with specified colour. It takes too long to erase or fill the screen with slower microcontroller.
Hello friend! Here, you present a circuit with ready-made screens, specific for Arduino, but my question would be: is it possible to use a 7" LCD screen from a car GPS, to use with Arduino, in the same way you show in the video? But, I would have to know the Driver used on the screen, right? I am already subscribed to your channel - Thank you
Bro very very thanks to you.B ecause for past two weeks i dont know how to wire tft for parallel .and it works really good and also it is faster than spi tft
Instead of making it complicated why not just use esp32-s3 HMI? Doesn't it more simple? And probably cheap? You can go up to 7inch i guess with those premade boards
I respect your work, and i have learned a lot from your guides and videos, it motivates me to go further and dig deeper to solve problems,and i regained my pleasure for electronics, thx!!
Brilliant. You have done a lot of work figuring out how to drive these displays. 👌
This seems to be a 16bit parallel board but your video indicates that only 8 data lines are to be connected. Is this correct? If so, what is the impact of only using the lower 8 bits? Thank you...
Sadly no answer.
@@yasyasmarangoz3577On most controllers you have Pins that you can pull up or down to choose between for example 8 or 16 bit mode. So you can control the display with 16bit parallel for best performance or because you dont have that many pins you can choose to use 8 bit
Another great tutorial Andrei. Thank you for sharing this with us!
I have this display, it's the largest one I could find that was self-driving with breakout pins. It's able to be driven in a 16-bit 5-6-5 parallel mode if you need the speed and have extra I/O. Using a Teensy 3.6 I was able to update the entire screen at 30fps, very satisfying for a microcontroller.
Got it on Ebay about 5 years ago. Nice size, 18-bit colour but I could not get the gamma correction working so I compensated in software. Touch screen is 4-wire resistive-type.
The display is 800x480 pixels and is best viewed straight on or from *one* of the long sides, otherwise the colours go weird and I never tried any portrait mode. The backlight is controllable but requires 5 volts @ 400mA for it's boost converter. Signals are 3.3v only and not 5v tolerant. Supply should be capable of ~200mA.
The driver is a SSD1963 by Solomon Systech, the touch screen controller is a generic HR2046 as far as I know. The SD card breakout is SPI mode only.
That's what I know about this board.
Which library do you use for SSD1963, at 16-bit parallel interface?
Big screen is not good on ESP32 or RP2040. The 8-bit or 16-bit can help the transfer.
But the key issue is the memory size.
Hello excellent as always, I am from Colombia and sometimes I visit your channel in English language just to know what is coming in the Latino🙈..... channel. It would be very interesting that in this project you can apply the LVGL library for the user interface and indicators, and incidentally transmit that teaching since there is little information in Spanish, thank you very much for your time and valuable teaching.
Just wondering: is the 8-bit parallel data transfer really that much faster than ex. I2C? The latter often has a (partial) HW implementation, whereas I guess the parallel transfer is using bit-banging, so I wonder whether I2C would not allow higher frequencies than such a parallel interface thereby reducing the gain of having 8 parallel lines and it would definitely be a lot easier to connect ... As said, just wondering. Since really high-speed serial busses rule (each PCIe lane, USB, ...), I really think micro-controllers need a reliable, super fast and super cheap serial bus to avoid the need for such parallel GPIO-pin consuming connections ...
Hello MisterkeTube, I don't know if you are still interested in this topic, but since no one has answered your question, I'll be happy to explain. Basically, since I2C is 2 wires, one of them being clock (SCL), and the other one being data (SDA), it inherently is unable to send data at as fast speeds as if it was going through multiple wires. I2C can send 3.4Mbits of data per second, which sounds fast, but think about 800x480 pixels, and their 16-bit colour data. That's 384K pixels, and 65536 colours for each pixel. I2C can't run as fast because of wire capacitance, which basically holds the electrical charges for a bit, messing up sync, and maybe even ruining the signals all together. To run I2C as fast as parallel, you would essentially need copper traces infinitely thin, that, or significantly out of manufacturing tolerances (probably less than 2 mil). This would actually end up being even more costly than parallel 8-bit, since ESP32-S3, ESP32 already have it. Yes, parallel interface does take up many wires, but it can reach much faster speeds because of it. An analogy is like: think of one man carrying heavy weights from one place to another, one at a time. Now, get about 15 of his friends to help him out, so that they are all doing it at the same time, and you can imagine how much incredibly faster this is. You can imagine the one man by himself being I2C (since it only has one data wire), and the 16 men being parallel interface. Although it is unfortunate how many wires parallel takes up, it is about the best we have got (at least that I have seen) at this stage. Once you get past like 480x320 pixel (normally using QSPI or really really fast SPI [like 80 - 125MHz]), everything just uses parallel interface.
Great brother really good; hyped for the next part.
Very informative, liked the work through as it’s real tough to find these kind of tutorials,
Be blessed brother ❤
Thank you for showing how to set up a parallel interface i've looked every where T-T
Quite challenging driving a display with this interface
Why doesn't the standard display library comes with command to erase or fill the screen with specified colour. It takes too long to erase or fill the screen with slower microcontroller.
Hello friend! Here, you present a circuit with ready-made screens, specific for Arduino, but my question would be: is it possible to use a 7" LCD screen from a car GPS, to use with Arduino, in the same way you show in the video? But, I would have to know the Driver used on the screen, right?
I am already subscribed to your channel - Thank you
very nice and straight forward tutorial ❤
Nice, please complete the resin printer...
Why does it have an SD card reader? For bitmaps?
Did you manage to get touch screen to work with this screen? TFT_eSPI doesn't support touchscreen in parallel mode...
Thanks for the very nice video!
Do you think it would be possible to use the 7" display as a Home Assistant dashboard?
Hi, nice video help me very much!
Your next video should be attaching an sd card to the module.
Thanks.
Marc.
i have question i can Using TFT_eSPI library with 3.5 TFT LCD SHILD DRIVER:ILI9488(IPS)
DOTS (320 * 480)
Is it possible to make a resin printer with this screen?
Want a video on how to use a parallel interface 2.4" or 1.77" TFT display with Arduino Uno
dose this support esphome to be used for smarthome dashboard
I don't know..
@@ELECTRONOOBS seems like it only support ili9xxx and nextion display so i can only use the small ones
How did you figure out that you have to use another driver?
I wish I was smart like you
Nice,what is the fps limit for that screen?
we cannot display arduino on old lcd like car player screen? must new models made for arduino?😊
Please make gsm and arduino relay control through sms and phone calls
Bro very very thanks to you.B ecause for past two weeks i dont know how to wire tft for parallel .and it works really good and also it is faster than spi tft
Instead of making it complicated why not just use esp32-s3 HMI? Doesn't it more simple? And probably cheap? You can go up to 7inch i guess with those premade boards
Nextion display?
Is it possible to use touch?
Hi good work bro 👍👏👍👏 super
Join my Arduino Course (Spanish): bit.ly/2JY8icE
My Tools: bit.ly/3uv8bc3
Help me on Patreon: www.patreon.com/ELECTRONOOBS
Merci pour la vidéo
Waiting for new printer video
🔥❣️
goot gootoootot 👍
Can we use esp8266 instead of esp32 ?
Yes! Check the Setup.h file and change the pins for an ESP8266
@@ELECTRONOOBS thankyou
👍👍👍
Cool
bro just make a stm 32 flight cantroller ❤
Wow
First