Data sometimes lost when sending to ST7789V TFT-display with Adafruit_ST7789.h lib - Why?
Moderators: adafruit_support_bill, adafruit
Please be positive and constructive with your questions and comments.
- adaloop
- Posts: 25
- Joined: Wed Feb 01, 2023 7:46 am
- adafruit_support_carter
- Posts: 29168
- Joined: Tue Nov 29, 2016 2:45 pm
Re: Data sometimes lost when sending to ST7789V TFT-display with Adafruit_ST7789.h lib - Why?
These questions have been answered. Not sure what more information can be provided.
The text "3-5V Vin" in the guide is referring to the Vin pin. It has a few extra character "3-5V" and also mentions an alternate name "V+". Please ignore the extra text "3-5V" and "V+". The Vin pin is the pin with the "Vin" label next to it here:
The text "3-5V Vin" in the guide is referring to the Vin pin. It has a few extra character "3-5V" and also mentions an alternate name "V+". Please ignore the extra text "3-5V" and "V+". The Vin pin is the pin with the "Vin" label next to it here:
There is no single answer for this. It is up to you to determine this for your setup and Arduino board being used. You will need to use the pinout information for the Arduino board you are using to determine this. If those pins are not being used for anything else, are broken out on headers pins on the board, and can function as General Purpose Input/Output, then *any* of them could be used for CS and DC.Which pins can then be used for distinguised CS & DC for extra displays?
Is it 22+24+26+28+30..43+47..49? or which intervals?
These functions do not exist in any of the referenced libraries, so will not work. More information about where these function are being referenced was requested in previous post.does that mean that tft.flush() & tft.availableForWrite() will not work?
- adaloop
- Posts: 25
- Joined: Wed Feb 01, 2023 7:46 am
Re: Data sometimes lost when sending to ST7789V TFT-display with Adafruit_ST7789.h lib - Why?
adafruit_support_carter wrote: ↑Sun Mar 05, 2023 3:27 pm The text "3-5V Vin" in the guide is referring to the Vin pin. It has a few extra character "3-5V" and also mentions an alternate name "V+". Please ignore the extra text "3-5V" and "V+". The Vin pin is the pin with the "Vin" label next to it here:
vin.png
Well, I ended up just putting 3,3v to the 3v pin and that worked apparently.
So should I understand it like this: It doesnt matter which of them I conect power to?
3v can only receive 3v, while the Vin can receive 3-5v?
What does "Vin" stand for? Variable input?
And why have 2 pins, if everything just could be connected to the Vin pin?
- adaloop
- Posts: 25
- Joined: Wed Feb 01, 2023 7:46 am
Re: Data sometimes lost when sending to ST7789V TFT-display with Adafruit_ST7789.h lib - Why?
The pins I have listed is based on what I understood on the 3rd diagram on this page: https://community.element14.com/product ... s-and-moreadafruit_support_carter wrote: ↑Sun Mar 05, 2023 3:27 pmThere is no single answer for this. It is up to you to determine this for your setup and Arduino board being used. You will need to use the pinout information for the Arduino board you are using to determine this. If those pins are not being used for anything else, are broken out on headers pins on the board, and can function as General Purpose Input/Output, then *any* of them could be used for CS and DC.Which pins can then be used for distinguised CS & DC for extra displays?
Is it 22+24+26+28+30..43+47..49? or which intervals?
So can you concur that the above list is the ones which are free and available for CS connections for multiple displays?
Or question/answer in another way: Can I just try & error on the different pins? Or can I risk to harm either the Arduino or the display?
- adaloop
- Posts: 25
- Joined: Wed Feb 01, 2023 7:46 am
Re: Data sometimes lost when sending to ST7789V TFT-display with Adafruit_ST7789.h lib - Why?
Those commands drop down as suggestions in the Arduino IDE when you write the name of a TFT instance.adafruit_support_carter wrote: ↑Sun Mar 05, 2023 3:27 pmThese functions do not exist in any of the referenced libraries, so will not work. More information about where these function are being referenced was requested in previous post.does that mean that tft.flush() & tft.availableForWrite() will not work?
Researching further os this shows that it seems to be inherited from the basic serial class.
So my assumption was according to the SPI communications digram and that you wrote on your productpage that the MISO are not being used, then it doesnt have any communication back again from the TFT and therefore I would guess that the 2 functions doesnt work with your TFT!?
Is that correct understood?
- adafruit_support_carter
- Posts: 29168
- Joined: Tue Nov 29, 2016 2:45 pm
Re: Data sometimes lost when sending to ST7789V TFT-display with Adafruit_ST7789.h lib - Why?
yesSo can you concur that the above list is the ones which are free and available for CS connections for multiple displays?
yesIs that correct understood?
Please be positive and constructive with your questions and comments.