SainSmart 7'' Touch randomly stops working
Posted: Fri Aug 23, 2019 12:35 pm
Hello everyone,
I've got my Pi set up as a CarPC (https://engineering-diy.blogspot.com/).
It works pretty well, except for intermittent problems with the touch part of my screen. After a random amount of time (can be immediately on boot or not at all within a few hours of operation), the touch just cuts out.
Any taps on the screen give no results.
Here's the (relevant) dmesg output:
As far as I can tell, the touch controller (which is connected via USB) disconnects. I can see no reason for this, as I never touch the cable while the pi is powered on.
It's possible the taps on the screen might move it a little, but I find that doubtful.
Also, I'm unsure about the power aspect: Will 1.05A do for the pi with the touchscreen connected? (Note that the screen is powered via a separate 1.05A port).
So, what I'm asking is, are there any causes you can think of for this? And hopefully a fix?
I've got my Pi set up as a CarPC (https://engineering-diy.blogspot.com/).
It works pretty well, except for intermittent problems with the touch part of my screen. After a random amount of time (can be immediately on boot or not at all within a few hours of operation), the touch just cuts out.
Any taps on the screen give no results.
Here's the (relevant) dmesg output:
Code: Select all
[ 2.490450] usb 1-1.5: new low-speed USB device number 5 using dwc_otg
[ 2.641647] usb 1-1.5: New USB device found, idVendor=0eef, idProduct=0001
[ 2.645757] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2.649869] usb 1-1.5: Product: USB TouchController
[ 2.654210] usb 1-1.5: Manufacturer: eGalax Inc.
[ 2.656698] fuse init (API version 7.26)
[ 2.704633] i2c /dev entries driver
[ 3.058810] systemd-udevd[146]: starting version 215
[ 3.789376] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[ 4.924266] input: eGalax Inc. USB TouchController as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5:1.0/input/input0
[ 4.924795] usbcore: registered new interface driver usbtouchscreen
[ 4.951433] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
[ 5.803966] systemd-journald[139]: Received request to flush runtime journal from PID 1
[ 6.227974] usbcore: registered new interface driver usbserial
[ 6.228096] usbcore: registered new interface driver usbserial_generic
[ 6.228207] usbserial: USB Serial support registered for generic
[ 6.232909] usbcore: registered new interface driver pl2303
[ 6.233058] usbserial: USB Serial support registered for pl2303
[ 6.233210] pl2303 1-1.4:1.0: pl2303 converter detected
[ 6.239421] usb 1-1.4: pl2303 converter now attached to ttyUSB0
[ 8.143664] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[ 8.144334] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 13.030826] random: crng init done
[ 37.438409] Bluetooth: Core ver 2.22
[ 37.438580] NET: Registered protocol family 31
[ 37.438591] Bluetooth: HCI device and connection manager initialized
[ 37.438631] Bluetooth: HCI socket layer initialized
[ 37.438653] Bluetooth: L2CAP socket layer initialized
[ 37.438713] Bluetooth: SCO socket layer initialized
[ 37.495479] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 37.495544] Bluetooth: BNEP filters: protocol multicast
[ 37.495584] Bluetooth: BNEP socket layer initialized
[ 39.691039] usb 1-1.5: USB disconnect, device number 5
[ 41.010545] usb 1-1.2: new high-speed USB device number 6 using dwc_otg
[ 41.142267] usb 1-1.2: New USB device found, idVendor=7392, idProduct=7811
[ 41.142287] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 41.142299] usb 1-1.2: Product: 802.11n WLAN Adapter
[ 41.142309] usb 1-1.2: Manufacturer: Realtek
[ 41.142319] usb 1-1.2: SerialNumber: 00e04c000001
[ 41.830551] usb 1-1.5: new low-speed USB device number 7 using dwc_otg
[ 41.972064] usb 1-1.5: New USB device found, idVendor=0eef, idProduct=0001
[ 41.972087] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 41.972098] usb 1-1.5: Product: USB TouchController
[ 41.972128] usb 1-1.5: Manufacturer: eGalax Inc.
[ 41.978859] input: eGalax Inc. USB TouchController as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5:1.0/input/input1
[ 42.427602] usbcore: registered new interface driver rtl8192cu
[ 43.536303] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 47.866217] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 336.724465] uart-pl011 3f201000.serial: no DMA platform data
[ 835.595022] usb 1-1.5: USB disconnect, device number 7
It's possible the taps on the screen might move it a little, but I find that doubtful.
Also, I'm unsure about the power aspect: Will 1.05A do for the pi with the touchscreen connected? (Note that the screen is powered via a separate 1.05A port).
So, what I'm asking is, are there any causes you can think of for this? And hopefully a fix?