Skip to content
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 doesn't work and issue when touch one metal #7

Open
danihmorais opened this issue Feb 24, 2025 · 1 comment
Open

Touch doesn't work and issue when touch one metal #7

danihmorais opened this issue Feb 24, 2025 · 1 comment

Comments

@danihmorais
Copy link

danihmorais commented Feb 24, 2025

Hello. Excuse my English, I'm from Brazil. I tested the HOW-TO of @fbeltrao-br and the screen appears, with the klipper screen etc. However, I'm having problems with the touch. It rarely works with touch and, for some reason that I have no idea, I can't touch ANY metal part, especially the frame that surrounds the screen or the button; and because the touch barely works, I can't calibrate it. I really don't know if this is a lack of calibration or some hardware problem. Any ideas?

In the video, when I try to click to go back, I end up touching the metal part and the screen shows a bit of the problem, artefacts quickly. Then when I actually touch the metal part, the screen disappears, and only appears again if I restart.

WhatsApp.Video.2025-02-23.at.01.22.36.mp4
@danihmorais
Copy link
Author

update: the touch problem appears to indeed be kernel related; I installed version 6.1, as indicated in the how-to of @fbeltrao-br, and now it is working correctly. however, you still cannot touch the metal part. another important observation is that when I was using the current kernel, 6.6, I set the gpio-debounce parameter to <10>; This made the artifacts stop appearing and the screen turned white. It was a suggestion from the gpt chat and I honestly don't know what it means. Finally, confirmed that in version 6.1 it works; Now I'm going to try to "isolate" the metal part of the contacts on the board, but it's interesting that I need to do this, because the screen works normally on the Marlin, when connected directly to the MCU, which suggests that, even if it's a hardware problem, it can be overcome somehow via software, or that the MCU has some additional component that the RPI doesn't have.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant