i see what you mean @wyleu - I have 2 of those hats and were bought for rPi 3 projects I am also playing around with. The PSU will come in handy for one of those so no lost ground - actually hopefully solves an issue I would have had
Have you tried plugging the USB to each port? One is used to power the screen and the other is used for comms, but I tend to find you can use just the comms port for both.
Are you talking about the 2 USB C ports on the side of the TFT @riban . I have a base raspian image i set up yesterday whilst playing about and found the one labelled Touch and Power didnt touch and the one labelled Power only did. So, not sure. What config should i use for it? What driver should I select in webconf?
@Hargy I have a Phase26 and external screen with touch and it only works in my case, when both are connected, then I use a separate power supply for the screen (a simple USB charger with micro USB seems to do the job POWER port). I connect the Phase26 in the usb3 port (Blue) and the touch (screen) in a USB2 port (black) in the PI.
edit: in your case itās a USBc port not a micro USB port
Iām writing from memory as Iām in the Alps on vacation
Hi. The touchscreen despite not appearing to work is working on some level as i plugged in a mouse and navigated to the Calibrate Touchscreen option under Admin. I can press the cross hair with my finger and it changes colour to red and resets the 15s timer. I have also tried this under bookworm as configured now with Phase 26 plugged in as now and with the screen connected to a Blue USB port. All works fine there
its already checked Hans. Someone else reported a similar issue in Nov 24. 7 inch screen touch calibration . They tried using a similar touch screen and appear to have had issues. Enable cursor removes or adds the cursor. I have a mouse connected to the set up. I just dont have touch control even though it is as I say working on some level. The touch calibration tool definitely is seeing it partially
The very existence of the touch calibration is indicative of how often this ends up getting revisited.
Not much help I agree, but Any insights or specific behaviours are worthy of a Bug reportā¦
How does your display config look like? Donāt know if it helps, but I set up my screen using one waveshare 7 inch ātemplateā and adjusted the values according to my model.
Guess in your Generic setup the field where youre supposed to enter /boot/config.txt stuff is empty by now. Also enter your resolution also in the corresponding field. Can look something like
For me in the beginning the touch seemed no not work because the screen resolution was matching to some arbitrary touch resolution. Maybe your touchscreen works but you hit some unrelated blank screen areas.
@hannesmenzel thank you for this. I have configured the Generic setup as you suggested. The TFT is a Waveshare clone. The rPi mounts to the back of it and has an USB connector to mini din TOUCH connector on the TFT. There is a USB c one also on the side of the TFT.
I have just been playing with it and powered it through the rPi (instead of the power connector on the TFT itself). I then pulled the USB ā mini din connector out and reseated it and suddenly touch started working. Given this is a faff I have connected the USB to the USB c TOUCH point on the side of the TFT. Touch wont work on boot initially, however once booted i can pull the connector in and out and touch starts working. Its not elegant and i wonder why this action results in the touch starting to work. Does USB do a refresh when i do this that then enables touch? I tried touchscreen calibration and that works fine now (as I thought it would).
Maybe one of the tech guys can help here. Why would reseating the USB in this way make this service start working?
i guess now this is more than 1 of us I should raise a ticket with support. Seems like a simple internal fix - which would be to cycle the USB after boot or see why the service doesnt start but does once this manual step takes place.
There is a fault with the firmware in some of the Waveshare controller chips that fail if the screen is touched before the driver is loaded. I have two of these screens and they required a hardware fix (SMD replacement). I was interested to hear whether your issue (that has similar symptoms) had the same fault. It was difficult to diagnose the issue because it seemed random - until you realised what triggered it.
There are others who have suffered the issue you describe. They have worked around it with a script to reset the USB after boot. Search the forum for description of this fix. I have not had the time to investigate a more robust solution. I feel there is one waiting to be discoveredā¦
Thanks @riban . My approach was to work out what scripted fix would work. Seems quite straightforward but if someone has already done that then I will have a look. Good thing this is built on Linux where scripting like this is doable, even by an idiot like me. Much tougher to achieve on windows or mac