Why does the screen display normally but capacitive touch cannot be used?
- Confirm whether the driver is installed correctly
- Confirm whether the correct configuration parameters are added to config.txt
- Enter
i2cdetect -y -r 1
to check the touch device status - If the following situation occurs, it means the touch driver is normal
pi@mainsailos:~ $ i2cdetect -y -r 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- --
- If the following situation occurs, it means that the touch driver is not installed correctly.
pi@mainsailos:~ $ i2cdetect -y -r 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- 5d -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- --
- When the above step 5 occurs (driver exception), you can try the following operations:
- Modify the
dtoverlay=fly-tft-v2
added in config.txt todtoverlay=fly-tft-v2-0x5d
- Restart the device
- Modify the
- If the above step 4 occurs (the driver is normal), you can try the following operations:
- Execute
hexdump /dev/input/event0
command - Touch the screen with your finger and observe the command line output
- If a large number of characters appear in the command line output, the driver is normal. Please check the touch configuration of your KlipperScreen.
- If there is no output in the command line, it means the driver is abnormal. Please contact us for resolution.
CTRL + C
Exit the command line
- Execute