-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Touch not working #2
Comments
Hi Erik, Did you use the user setup? The TFT_BL is here: WT32-SC01-Demo/WT32-SC01-User_Setup.h Line 100 in f2e0dc2
Regards |
Sorry to stay on, on the Bodmer repo. My question: The touchscreen is supposed to work with I2C as the Pins SDA & SCL are defined. However, if i run an Arduino i2c discovery script, it tells me no i2c device detected. Whereas it does detect my temp sensor and compass if i connect them. |
Looks and sounds like a faulty screen.. Can you post the link to the device you bought? Also, remember that the i2c pins might be different from the adafruit scanner... IE 18 & 19 ie try: #include "Wire.h"
void setup() {
Serial.begin(115200);
Wire.begin(18, 19);
}
void loop() {
byte error, address;
int nDevices = 0;
delay(5000);
Serial.println("Scanning for I2C devices ...");
for(address = 0x01; address < 0x7f; address++){
Wire.beginTransmission(address);
error = Wire.endTransmission();
if (error == 0){
Serial.printf("I2C device found at address 0x%02X\n", address);
nDevices++;
} else if(error != 2){
Serial.printf("Error %d at address 0x%02X\n", error, address);
}
}
if (nDevices == 0){
Serial.println("No I2C devices found");
}
} Or so... |
Hi elgerg, I have the same problem with my screen. I believe it is because the Adafruit library expects only one argument in:
so we have to adjust this? |
I changed in the FT6206 library:
to:
this worked for me. |
I would assume that you didnt install the forked library that supports pin override? IE: In your Arduino libraries directory, clone a fork of Adafruit_FT6206_Library that allows overriding the I2C GPIO pins in the Arduino Wire library. From: Glad to hear you got it working though. |
Hi Erik, What Wire test sketch did you try? Can you post the sketch and link to the device you bought? Thanks |
Here is the sketch. I bought it from Aliexpress couple of months ago.
Yesterday I got a replay from WT telling me to use TFT_eSPI for the display and the FT6336U for the touch. To be honest it worked one time when using one of their samples to test the touch, but i could not reproduce it. And I use the ESP32WROVER as device. |
With the FT6336U and the pins 18 and 19, there is live in their samples. (ScanMultiTouch)
|
I have succeeded in porting the sketch to use the FT6336U library and wrote my own test sketch to prove it. I must say that with the FT6336U programming is a breeze in conjuntion with the standard display file by Bodmer for the WR32-SCO1. Now all that is left is stydy the library FT6206 and see / find out why it is not working with me ? |
Maybe your board does have a FT6336U and not the FT6206. If thats the case then I would drop trying to use the FT6206 library.. from your video it looks like you are deffo on the right track. |
Oh, yes I skimmed over it probably 3 times ;) Thank you for clarifying. And thank you for your work. It saved me a lot of time! |
Thanks for the praise but it should go to SnowBug, not me ;).. |
FYI @videobuff I think your repo (https://github.com/videobuff/GraphicTouchTestFT6336U-WT32-SCO1) isnt public. I get a 500 error when trying to access it. |
Skimming over things, seems to be my thing ;) |
I got the 500 Error a lot off times on Github yesterday. Many sites were not reachable, including Bodmer/TFT_eSPI |
Truly strange, I was also experiencing this issue. I am using the forked touchscreen driver, and when I set the debug flag in the ts driver, I see that it does init the Wire device with the extra parameters (18, 19), but all the readRegister calls return 0xFFFF values. This is what I get from the code as is:
However, if I put the Wire.begin(18, 19) in the main setup routine just before the ts.begin, then it all works. Not sure of something is getting redefined between that, and the ts.begin code.
Literally, one line added from the code in this repo:
|
@euandekock are you using onewireng? |
I am just using the standard Wire I2C interface. I'm not addressing any
OneWire devices.
Regards,
Euan.
…On Mon, May 9, 2022 at 6:07 AM Alex ***@***.***> wrote:
@euandekock <https://github.com/euandekock> are you using onewireng?
I just updated my screen and has the same issue. Adding Wire.begin(18, 19)
in the main setup routine just before the ts.begin made it work like a
charm!
Nice work!!
Thanks
—
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAUZXVEFH6RLRAWTRYH5I4TVJA3KNANCNFSM5ND7W6FQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Really happy to find your repo, but i still can't make it work.
This is what i did
First removed original Adafruit_FT6206.h library and installed the one you pointed out.
When first compiled, I got an error that TFT_BL was not defined.
No wonder since the serial port showed the following output:
09:56:56.804 -> Couldn't start touchscreen controller
This comes from this subroutine:
if (!ts.begin(18, 19, 40)) {
Serial.println("Couldn't start touchscreen controller");
while (true);
}
What is the TFT_BL pin you defined ?
Many thanks
Erik
The text was updated successfully, but these errors were encountered: