iLem0n
Posts: 2
Joined: Mon Mar 20, 2017 1:00 pm

eGalaxy Touch Receives Touches but no mouse moves

Mon Mar 20, 2017 1:13 pm

Hey Guys,

I have a problem getting my eGalaxy TouchScreen working.
it is attached to a raspberry pi 3 running latest raspbian Jesse with pixel:

Code: Select all

Linux frankTheTank 4.9.16-v7+ #978 SMP Sat Mar 18 13:59:01 GMT 2017 armv7l GNU/Linux
The Problem is that the touch won't work.
he recognises the touch controller.
But the mouse won't move.

I have setting up all with xinput-calibrator (calibration will be incorrect due the lack of mouse movement, but its in /etc/X11/xorg....)
lsusb

Code: Select all

$ lsusb
Bus 001 Device 005: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 004: ID 0eef:0001 D-WAV Scientific Co., Ltd eGalax TouchScreen
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
evetest output shows 2 events for the touch controller ? is this right ?

If I select event0 I receive nothing while touching the display.
if I select event1 I see all touch events going in, see above.

Code: Select all

$ sudo evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:	eGalax Inc. Touch
/dev/input/event1:	eGalax Inc. Touch
/dev/input/event2:	Logitech K400
Select the device event number [0-2]: 1
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0xeef product 0x1 version 0x112
Input device name: "eGalax Inc. Touch"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 320 (BTN_TOOL_PEN)
    Event code 330 (BTN_TOUCH)
  Event type 3 (EV_ABS)
    Event code 0 (ABS_X)
      Value    771
      Min        0
      Max     2047
    Event code 1 (ABS_Y)
      Value    833
      Min        0
      Max     2047
  Event type 4 (EV_MSC)
    Event code 4 (MSC_SCAN)
Properties:
Testing ... (interrupt to exit)
Event: time 1490015147.466389, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1490015147.466389, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1490015147.466389, type 3 (EV_ABS), code 0 (ABS_X), value 1468
Event: time 1490015147.466389, type 3 (EV_ABS), code 1 (ABS_Y), value 1666
Event: time 1490015147.466389, -------------- EV_SYN ------------
Event: time 1490015147.506358, type 3 (EV_ABS), code 0 (ABS_X), value 1465
Event: time 1490015147.506358, type 3 (EV_ABS), code 1 (ABS_Y), value 1665
Event: time 1490015147.506358, -------------- EV_SYN ------------
Event: time 1490015147.530358, type 3 (EV_ABS), code 0 (ABS_X), value 1464
Event: time 1490015147.530358, type 3 (EV_ABS), code 1 (ABS_Y), value 1663
Event: time 1490015147.530358, -------------- EV_SYN ------------
Event: time 1490015147.554357, type 3 (EV_ABS), code 0 (ABS_X), value 1463
Event: time 1490015147.554357, type 3 (EV_ABS), code 1 (ABS_Y), value 1661
Event: time 1490015147.554357, -------------- EV_SYN ------------
Event: time 1490015147.578360, type 3 (EV_ABS), code 0 (ABS_X), value 1464
Event: time 1490015147.578360, type 3 (EV_ABS), code 1 (ABS_Y), value 1659
Event: time 1490015147.578360, -------------- EV_SYN ------------
Event: time 1490015147.594358, type 3 (EV_ABS), code 0 (ABS_X), value 1468
Event: time 1490015147.594358, type 3 (EV_ABS), code 1 (ABS_Y), value 1657
Event: time 1490015147.594358, -------------- EV_SYN ------------
Event: time 1490015147.618356, type 3 (EV_ABS), code 0 (ABS_X), value 1472
Event: time 1490015147.618356, type 3 (EV_ABS), code 1 (ABS_Y), value 1656
Have anybody a hint how to get it work ?

rpalma
Posts: 1
Joined: Sun May 21, 2017 8:07 pm

Re: eGalaxy Touch Receives Touches but no mouse moves

Sun May 21, 2017 8:10 pm

Hello, i got the same problem with the sabe product.
when running evtest i got screen activity, but no pointer function.

Have you find a soluction?

iLem0n
Posts: 2
Joined: Mon Mar 20, 2017 1:00 pm

Re: eGalaxy Touch Receives Touches but no mouse moves

Mon May 22, 2017 7:38 am

My mistake was to run 'rpi-update' which updated the kernel. It seems that the latest Kernel didn't support this screen anymore.

Just downgrading the kernel via 'rpi-update' didn't fix this too.

So I've took an older image with a stable kernel release and it works again.

Return to “Recommended peripherals”

Who is online

Users browsing this forum: Baidu [Spider] and 4 guests