You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the problem you have/What new integration you would like
I would like to see support added for the NS2009 I²C resistive touchscreen IC
Please describe your use case for this integration and alternatives you've tried:
The BigTreeTech TFT35 SPI display runs on a ILI9488 chip, so the screen itself is already compatible (and confirmed working by me). Adding support for the NS2009 touch IC would make this display fully compatible with ESPHome and provide users with an extremely affordable option for integrating a touchscreen into their project.
The text was updated successfully, but these errors were encountered:
NuclearKitty
changed the title
Please add support for NS2009 I²C resistive touchscreen IC
Add support for NS2009 I²C resistive touchscreen IC
Sep 21, 2024
Describe the problem you have/What new integration you would like
I would like to see support added for the NS2009 I²C resistive touchscreen IC
Please describe your use case for this integration and alternatives you've tried:
The BigTreeTech TFT35 SPI display runs on a ILI9488 chip, so the screen itself is already compatible (and confirmed working by me). Adding support for the NS2009 touch IC would make this display fully compatible with ESPHome and provide users with an extremely affordable option for integrating a touchscreen into their project.
Additional context
Schematics and pinouts for the TFT35 SPI and the technical datasheet for the NS2009 Touch IC can be found under
https://github.com/bigtreetech/TFT35-SPI/tree/master/v2
The pin labeling on the display is a little weird.
RS = D/C Pin
NSS = CS Pin
The touch IC works over regular 2-wire I²C, but there is also a seemingly optional IORQ interrupt pin available.
An Arduino library for the NS2009 does also seem to exist under:
https://github.com/Stanimir-Petev/NS2009
The text was updated successfully, but these errors were encountered: