MasterOfGizmo hat geschrieben: ↑14 Dez 2020, 15:46
So if you use the ft-HAT, then the touch stops working after some time. If you don't use the ft-HAT then the touchscreen simply works as it should.
Is this right? This would be a rather odd relationship since the touch and the display share the same bus and there's not much that can break physically that makes the touch stop working while the display still works.
Can you tell when exactly the touch stops working?
firstly, Apologies with the formatting and any miscommunication, I tried to translate my questions from english to german and put both into the forum but it seems the forum does its own AI or translation and therefore may do a double convert !
I try to answer as best as possible. ( ethernet not wifi used for all tests )
this is a Rpi 3B with Waveshare 3.5" (C) SPI touch screen (MHS hi-speed version), according to the Tx-Pi info this uses the standard Waveshare A driver
using the txpi image for the type A waveshare -
https://www.tx-pi.de/images/latest_pi3-35a
The RPI boots and CFW shows fine (SSH wont work but thats a different issue)
a. Without TX-pi hat ( just RPI and screen ) then all the Community firmware apps work and the touchscreen works and stays working ( i usually use calc to test )
b. With the HAt between Rpi and Display - system boots, CFW comes up touch screen works initially but if i leave it for 60-90 seconds or tap some screen buttons ( again calc is a good test ) then after a little while the touch stops responding
first seen when i went in to the TX-PI hat test and turned on a m1 motor slider and then lost touch so couldnt turn it off
Using the recommended Buster Lite image and then running the script with the " sudo bash ./tx-pi-setup.sh LCD35" option for the type A waveshare
The RPI boots and CFW shows fine
now SSH works fine ( initially i did this to see if something in the script killed ssh ) but it works fine
a. Without TX-pi hat ( just RPI and screen ) then all the Community firmware apps work and the touchscreen works and stays working ( i usually use calc to test )
b. With the HAt between Rpi and Display - system boots, CFW comes up touch screen works initially
but if i go into the Tx-pi hat test and leave it for 60-90 seconds and then tap a few buttons it seems the Pi looses the ability to read the screen touches
usually after each press on the screen ( use the stylus as resistive touch screens are best with a more focused press ) the little curer ( arrow) pops up to show when you pressed but when the touch seems to stop responding you can touch the screen and no arrow appears and nothing happens.
any way to restart the touch input from the command line or try to debug/log whats happening ???
Der Stift bewegt sich auf dem Display und wird von einer Webcam aufgezeichnet. Die Frage wäre, wie kommt die SD-Karte in den Pi. Hmh, wie wäre es, wenn man mit einem Overlay FS das Raspbian aufspielt? Will heisen man kann Raspbian immer in eine Urzustand zurück fahren. Dann das aktuelle Skript ausführen. Hmh, grumel ...
