TFT 1947 I2C Touchscreen

Adafruit Ethernet, Motor, Proto, Wave, Datalogger, GPS Shields - etc!

Moderators: adafruit_support_bill, adafruit

Please be positive and constructive with your questions and comments.
User avatar
dx160
 
Posts: 17
Joined: Fri Mar 30, 2012 11:36 pm

Re: TFT 1947 I2C Touchscreen

Post by dx160 »

No issues with the 1947 attached to a UNO (shield-style)
or when wired remote fashion (i.e. via jumpers).

The ESP32-1947 combination results:
- Without I2C connected to the 1947, the TFT display part is good
- With I2C connected to the 1947, the TFT "whites out". (I think the I2C is working
because MOSI activity is prompted when/whenever I touch the TS in the 'defined area'.)

I can put a video on vimeo. (Later on → for tomorrow.)

[ Someone has suggested that my Arduino_GFX_Library.h may conflict.
I am using that because I couldn't see how to arrange things (in Declarations etc.) for
the Adafruit_GFX library. ]

User avatar
dx160
 
Posts: 17
Joined: Fri Mar 30, 2012 11:36 pm

Re: TFT 1947 I2C Touchscreen

Post by dx160 »

I found direction to a github thread about ESP32 I2C troubles.
My Preferences URL wasn't to the current URL. My Version was 1.0.6
Updating the Preferences URL, I Updated to the current -- 2.0.4

The display still has a white raster, but the Touchscreen Starts.
If I leave the touchscreen I2C disconnected, the display comes up normal,
however, the execution is very slow - which I can only assume is attributable to
the missing I2C it's expecting.

* * The UNO doesn't, in this regard, care whether the I2C device is present.
Likewise, the ESP32 w/1.0.6 just went on with life. ("No touchscreen? Oh well.")

User avatar
dx160
 
Posts: 17
Joined: Fri Mar 30, 2012 11:36 pm

Re: TFT 1947 I2C Touchscreen

Post by dx160 »

The I2C is definitely working.
I added a Debug (Serial.print) that let's me know when the Defined Area
is triggered.
Now to find out why the raster goes all white (this as when it powers up).

User avatar
dastels
 
Posts: 11042
Joined: Tue Oct 20, 2015 3:22 pm

Re: TFT 1947 I2C Touchscreen

Post by dastels »

Huh. So you can get and process touches. It's just that when the touch processing is used the screen is white. When you don't use touch the screen works fine. And this is just on the ESP32, and it works fine (with screen and touch) on the UNO.

Can you use I2C for something else (some sensor for example) with the screen?

Dave

User avatar
dx160
 
Posts: 17
Joined: Fri Mar 30, 2012 11:36 pm

Re: TFT 1947 I2C Touchscreen

Post by dx160 »

So you can get and process touches.
Yes.

It's just that when the touch processing is used the screen is white.

No - it's white all the time if SDA_SCL are connected to the 1947.

When you don't use touch the screen works fine.
Not exactly. If SDA_SCL are not connected to the 1947, the display/tft is as it should.
If SDA_SCL are connected at boot/power_on, removing SDA_SCL later does not make it to come right.

And this is just on the ESP32, and it works fine (with screen and touch) on the UNO.
Right.

Can you use I2C for something else (some sensor for example) with the screen?
Yes, I read the thermocouple and placed the result on the display earlier on.

User avatar
dastels
 
Posts: 11042
Joined: Tue Oct 20, 2015 3:22 pm

Re: TFT 1947 I2C Touchscreen

Post by dastels »

OK, I'm at a loss. Everything seems to work... just not that combination of use of a single product. I'll ask around and see what I can come up with.

Dave

User avatar
adafruit2
 
Posts: 21186
Joined: Fri Mar 11, 2005 7:36 pm

Re: TFT 1947 I2C Touchscreen

Post by adafruit2 »

please post a photo or diagram of your wiring, so we can follow how its all connected

User avatar
dx160
 
Posts: 17
Joined: Fri Mar 30, 2012 11:36 pm

Re: TFT 1947 I2C Touchscreen

Post by dx160 »

I posted a schematic on the previous page, fairly detailed.
download/file.php?id=93904

Here is a link to how things go ─
https://vimeo.com/738107341

User avatar
adafruit2
 
Posts: 21186
Joined: Fri Mar 11, 2005 7:36 pm

Re: TFT 1947 I2C Touchscreen

Post by adafruit2 »

hiya, it isnt clear what that 3v/5v converter is.
but really.... what you're doing is just kinda a bad idea. you're using something not designed together, adding a ton of complexity. we know the hardware works so its something with the setup.
https://www.adafruit.com/product/2090
is a better idea, at least you do not have any level shifting to contend with!

User avatar
dx160
 
Posts: 17
Joined: Fri Mar 30, 2012 11:36 pm

Re: TFT 1947 I2C Touchscreen

Post by dx160 »

I've been 'told' that ESP32 PortB can be "iffy".
So, I should try Port_A for TFT D/C and CS.

" it isnt clear what that 3v/5v converter is."

They are these ('Rp' = 10kΩ ea.)

[attachment=0]PHIL_I2C_LS.jpg[/attachmten]
Attachments
PHIL_I2C_LS.jpg
PHIL_I2C_LS.jpg (37.74 KiB) Viewed 89 times

User avatar
adafruit2
 
Posts: 21186
Joined: Fri Mar 11, 2005 7:36 pm

Re: TFT 1947 I2C Touchscreen

Post by adafruit2 »

those types of shifters are not appropriate for high speed SPI shifting. you could try sending SPI data without shifting. and power the shield from 3V, at least then you remove an unknown element

Post Reply
Please be positive and constructive with your questions and comments.

Return to “Arduino Shields from Adafruit”