DFR0550 v3.0 Really strange touch (cannot calibrate)

userHead Jan.Elfström 2025-09-09 19:21:47 84 Views1 Replies

Hi,

I have a DFR0550 v3.0 that I have connected to a Raspberry Pi 3 Model B Plus Rev 1.3 with Debian GNU/Linux 11 (bullseye) 

(Lots of power on the 5V supply).

 

The display worked right out of the box but the touch orientation/direction doesn't make sense. No touch device was detected with “dtoverlay=vc4-kms-v3d” in config.txt, it is however detected with “dtoverlay=vc4-fkms-v3d” or with that overlay commented out.

The touch device is reported as "raspberrypi-ts" 

 DISPLAY=:0 xinput
⎡ Virtual core pointer                          id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer      id=4    [slave  pointer  (2)]
⎜   ↳ raspberrypi-ts                            id=6    [slave  pointer  (2)]
⎣ Virtual core keyboard                      id=3    [master keyboard (2)]
   ↳ Virtual core XTEST keyboard     id=5    [slave  keyboard (3)]
  
I have used the xtcal utility to try to calibrate the touch since it is wrong (not aligned with the display at all).

The result is really strange…

 

I number the crosses 0 - 3 after when they show up. 

With no transformation (DISPLAY=:0 xinput set-prop "raspberrypi-ts" 'Coordinate Transformation Matrix' 1 0 0 0 1 0 0 0 1)

0(0) 1(3)

3(3) 2(3)

The number in parentheses is the cross position I actually had to press for the next cross to appear. I have tried all sorts of transformations but the common theme is that there are two positions registered properly and one of those has to be pressed to detect the other two properly (number 3 in the above case). So not very useful and I don't really know how to come further. 

I have largelly followed the instructions in this link:
https://klipperscreen.readthedocs.io/en/latest/Troubleshooting/Touch_issues/

 

 

2025-09-14 02:36:06

The DFR0550 doesn’t expose a standard HID touchscreen; it goes through the Pi’s raspberrypi-ts driver, which maps touchpoints based on how the overlay is set up.

KMS vs FKMS:

With dtoverlay=vc4-kms-v3d (new DRM/KMS driver), the raspberrypi-ts input isn’t detected.

With FKMS or no overlay, it is detected, but the orientation is wrong.
This is expected — the legacy FKMS stack still hooks into the old input subsystem, while KMS hasn’t got full support for that driver.

userHeadPic ahsrab.rifat