eGalaxTouch Y-Axis Issue

**dlinuxh** · May 11th, 2012

Favux,
sorry for long post....
i am using firefox to start in kiosk... just experimenting with touch screen. the procedure i followed uses fluxbox for gui i think it is not x11... it might have come with the mini ISO... i am not expert in it yet.
as for the browser it is firefox...
here is another screen shot for drivers... maybe it might help...

this link http://www.tuxum.org/browser/tuxum/non-free/egalax32
talks about how to create a driver for egalax screen, but i don't know if it applies to my kernel...

xxxxxx@ubuntu:~$ lsusb -v -d 0eef:0001

Bus 002 Device 002: ID 0eef:0001 D-WAV Scientific Co., Ltd eGalax TouchScreen
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0eef D-WAV Scientific Co., Ltd
idProduct 0x0001 eGalax TouchScreen
bcdDevice 1.00
iManufacturer 1 eGalax Inc.
iProduct 2 USB TouchController
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 34
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 1 eGalax Inc.
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 2.10
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 141
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 3
Device Status: 0x0000
(Bus Powered)
xxxxxxx@ubuntu:~$

i guess these point to drivers?
xxxxxxx@ubuntu:/proc/bus/input$ cat devices
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
U: Uniq=
H: Handlers=kbd event0
B: PROP=0
B: EV=3
B: KEY=100000 0 0 0

I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
U: Uniq=
H: Handlers=kbd event1
B: PROP=0
B: EV=3
B: KEY=100000 0 0 0

I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input2
U: Uniq=
H: Handlers=sysrq kbd event2
B: PROP=0
B: EV=120013
B: KEY=4 2000000 3803078 f800d001 feffffdf ffefffff ffffffff fffffffe
B: MSC=10
B: LED=7

I: Bus=0003 Vendor=0eef Product=0001 Version=0210
N: Name="eGalax Inc. USB TouchController"
P: Phys=usb-0000:00:1d.0-1/input0
S: Sysfs=/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0/input/input3
U: Uniq=
H: Handlers=mouse0 event3 js0
B: PROP=0
B: EV=1b
B: KEY=30000 0 0 0 0 0 0 0 0
B: ABS=3
B: MSC=10

I: Bus=0003 Vendor=0eef Product=0001 Version=0210
N: Name="eGalax Inc. USB TouchController"
P: Phys=usb-0000:00:1d.0-1/input0
S: Sysfs=/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0/input/input4
U: Uniq=
H: Handlers=mouse1 event4
B: PROP=0
B: EV=1b
B: KEY=401 0 0 0 0 0 0 0 0 0 0
B: ABS=3
B: MSC=10

I: Bus=0011 Vendor=0002 Product=0005 Version=0000
N: Name="ImPS/2 Generic Wheel Mouse"
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input5
U: Uniq=
H: Handlers=mouse2 event5
B: PROP=0
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=103

xxxxxx@ubuntu:/proc/bus/input$

is there a way to verify if it is the driver that is bad?
In my case i can see the axis being inverted...
and i am trying to understan if i can callibrate the screen with no X, xorg.conf
from what i read, the points and axis are in xorg.conf.... right?

thanks for your feedback

**Favux** · May 11th, 2012

The way a usb device works is that there are usually two drivers for it.

There is the kernel driver that converts the raw usb data into data that a X driver can handle. The X driver then processes it into something the X Server can use to draw on your monitor.

Often touch screens are handled by the HID section of the kernel. Or if they have their own kernel driver often they need to be black listed in hid-core.c so the generic HID driver doesn't pick them up.

Then many touch screens now days use the evdev X driver. And the evdev driver is configured by the 10-evdev.conf in /usr/share/X11/xorg.conf.d.

I haven't checked that eGalax link you gave in detail but I presume it is too old. It probably/may have a kernel driver and a X driver for the eGalax touchscreen. But if everything in there is at least two years old like it says the question is do they work with the current kernels and X Servers. Maybe it does, but then what?

The point is apparently you don't have a X Server running and so aren't using a X driver or able to. At least that is what that error message "unable to connect to X server" seems to be telling us.

Since configuration options I'm familiar with are for X drivers through xorg.conf.d or xorg.conf or xinput I have now clue how to invert axes for you. At least without a much better understanding of how things work on the setup you are using.

The /proc/bus/input stuff is more the udev description of the devices. You could use udevadm info to get maybe a better picture of that if you needed to write a udev rule. The lsusb stuff is the kind of thing you'd want to know to write or modify a usb kernel driver.

**dlinuxh** · May 18th, 2012

Thanks Favux for your feedback. I will keep researching it. I have another question, what package i can use to set up evdev stuff? do you know?

**dlinuxh** · June 5th, 2012

Hi Favux,
I reinstalled the drivers and got same thing of swapped x and y axis.... While reinstalling it , i came accross black lists... have no ide what those are or how to ad it. I will keep on reading...
Do you know where to add the black list info (i hope i phrased the question right)
Here is what i see while installing it
Note that it is highly recommended that add inbuilt kernel module
"usbtouchscreen" or "touchkitusb" into blacklist to avoid conflict
if the touch controller is HID compliant device.Thanks for your time and help...

**NigO** · June 12th, 2012

Originally Posted by dlinuxh

Hi Favux,
I reinstalled the drivers and got same thing of swapped x and y axis....

Hi, I used the info at Samiux to get mine working (it was auto-detected OK during install, then unresponsive on the installed system), but my X and Y axes are swapped with each other, as they were during the install.

Can I just check if your fault is the same as mine, where touching lower right moves the cursor to upper left and vice versa, but touching upper right or lower left is OK?

If that is the case, then the X and Y co-ordinates have been swapped with each other. The suggested solutions of InvertX and InvertY won't help, they just change direction of the X or Y axes.

To put it another way, touching 500,0 moves to 0,500 and vice versa, but 0,0 or 500,500 are correct.

If your fault isn't the same, I'll start another thread, if it is the same, please post here when you find a fix!

**NigO** · June 12th, 2012

Originally Posted by NigO

Hi, I used the info at Samiux to get mine working (it was auto-detected OK during install, then unresponsive on the installed system), but my X and Y axes are swapped with each other, as they were during the install.

Can I just check if your fault is the same as mine, where touching lower right moves the cursor to upper left and vice versa, but touching upper right or lower left is OK?

If that is the case, then the X and Y co-ordinates have been swapped with each other. The suggested solutions of InvertX and InvertY won't help, they just change direction of the X or Y axes.

To put it another way, touching 500,0 moves to 0,500 and vice versa, but 0,0 or 500,500 are correct.

If your fault isn't the same, I'll start another thread, if it is the same, please post here when you find a fix!

OK, that was a bit easier than expected, so here's what worked for me with an eGalax touchscreen on ubuntu 12.04:

Code:

xinput

Lists the available devices which included 2 (?) eGalax touchscreens:

Code:

eGalax Inc. USB TouchController          id=8    [slave  pointer  (2)]
eGalax Inc. USB TouchController          id=9    [slave  pointer  (2)]

As there were two, I had to use their id numbers to change them. In each case, I did the same command for id 8 and id 9, not sure if id 8 had any effect, behaviour only changed after I changed the second one as well.

Code:

xinput list-props 8

showed the available properties and in my case, I needed to swap everything:

Code:

xinput set-prop 8 "Evdev Axes Swap" 1
xinput set-prop 9 "Evdev Axes Swap" 1
xinput set-prop 8 "Evdev Axis Inversion" 1 1
xinput set-prop 9 "Evdev Axis Inversion" 1 1

To save these settings, according to the evdev manpage and this calibration example, I should just have to change my /usr/share/X11/xorg.conf.d/10-evdev.conf file touchscreen section to

Code:

Section "InputClass"
        Identifier "evdev touchscreen catchall"
        MatchIsTouchscreen "on"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
        Option "SwapAxes" "on"
        Option "InvertX" "on"
        Option "InvertY" "on"
EndSection

That doesn't work, so reverted that section and made a new one specially for the eGalaxy, which does work

Code:

Section "InputClass"
        Identifier "eGalaxy touchscreen"
        MatchVendor "eGalax"
        Option "SwapAxes" "on"
        Option "InvertX" "on"
        Option "InvertY" "on"
EndSection

Now the touchscreen axes are in the right order and direction. I'm guessing that MatchIsTouchscreen isn't matching on the eGalaxy, but I could be wrong.

**dlinuxh** · July 5th, 2012

Originally Posted by NigO

OK, that was a bit easier than expected, so here's what worked for me with an eGalax touchscreen on ubuntu 12.04:

Code:

xinput

Lists the available devices which included 2 (?) eGalax touchscreens:

Code:

eGalax Inc. USB TouchController          id=8    [slave  pointer  (2)]
eGalax Inc. USB TouchController          id=9    [slave  pointer  (2)]

As there were two, I had to use their id numbers to change them. In each case, I did the same command for id 8 and id 9, not sure if id 8 had any effect, behaviour only changed after I changed the second one as well.

Code:

xinput list-props 8

showed the available properties and in my case, I needed to swap everything:

Code:

xinput set-prop 8 "Evdev Axes Swap" 1
xinput set-prop 9 "Evdev Axes Swap" 1
xinput set-prop 8 "Evdev Axis Inversion" 1 1
xinput set-prop 9 "Evdev Axis Inversion" 1 1

To save these settings, according to the evdev manpage and this calibration example, I should just have to change my /usr/share/X11/xorg.conf.d/10-evdev.conf file touchscreen section to

Code:

Section "InputClass"
        Identifier "evdev touchscreen catchall"
        MatchIsTouchscreen "on"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
        Option "SwapAxes" "on"
        Option "InvertX" "on"
        Option "InvertY" "on"
EndSection

That doesn't work, so reverted that section and made a new one specially for the eGalaxy, which does work

Code:

Section "InputClass"
        Identifier "eGalaxy touchscreen"
        MatchVendor "eGalax"
        Option "SwapAxes" "on"
        Option "InvertX" "on"
        Option "InvertY" "on"
EndSection

Now the touchscreen axes are in the right order and direction. I'm guessing that MatchIsTouchscreen isn't matching on the eGalaxy, but I could be wrong.

Nigel,
Thank you for your feedback, I am sorry for late reply. I am using no gui, no desktop distro, Upon typing xinput i get
dan@ubuntu:/usr/share/X11/xorg.conf.d$ xinput list --short
Unable to connect to X server

I am checking the /usr/share/X11/xorg.conf.d$ ls
dan@ubuntu:/usr/share/X11/xorg.conf.d$ ls
11-evdev-quirks.conf 50-vmmouse.conf 52-egalax.conf
11-evdev-trackpoint.conf 50-wacom.conf
50-synaptics.conf 51-synaptics-quirks.conf

If i cat 52-egalax.conf I get:
dan@ubuntu:/usr/share/X11/xorg.conf.d$ cat 52-egalax.conf | more
Section "InputClass"
Identifier "eGalax pointer class"
MatchProduct "eGalax Inc.|Touchkit|eGalax_eMPIA Technology Inc."
MatchIsPointer "on"
MatchDevicePath "/dev/input/event*"
Driver "egalax"
Option "Device" "usbauto"
Option "Parameters" "/var/lib/eeti.param"
Option "ScreenNo" "0"
EndSection

Section "InputClass"
Identifier "eGalax keyboard class"
MatchProduct "eGalax Inc.|Touchkit|eGalax_eMPIA Technology Inc."
MatchIsKeyboard "on"
MatchDevicePath "/dev/input/event*"
Driver "void"
EndSection

Section "InputClass"
Identifier "eGalax touchpad class"
MatchProduct "eGalax Inc.|Touchkit|eGalax_eMPIA Technology Inc."
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
Driver "void"
EndSection

Section "InputClass"
Identifier "eGalax tablet class"
MatchProduct "eGalax Inc.|Touchkit|eGalax_eMPIA Technology Inc."
MatchIsTablet "on"
MatchDevicePath "/dev/input/event*"
Driver "void"
EndSection

Section "InputClass"
Identifier "eGalax touchscreen class"
MatchProduct "eGalax Inc.|Touchkit|eGalax_eMPIA Technology Inc."
MatchIsTouchscreen "on"
MatchDevicePath "/dev/input/event*"
Driver "void"
EndSection

Section "InputClass"
Identifier "eGalax mouse class"
MatchProduct "eGalax Inc.|Touchkit|eGalax_eMPIA Technology Inc.|eGalaxTo
uch Virtual Device"
MatchDevicePath "/dev/input/mouse*"
Driver "void"
EndSection

Section "InputClass"
Identifier "eGalax joystick class"
MatchProduct "eGalax Inc.|Touchkit|eGalaxTouch Virtual Device"
MatchDevicePath "/dev/input/js*"
Driver "void"
EndSection

Can I just add these pcs from your post to that file?
Once again, thank you for your time.
den

**joaoramos69** · July 23rd, 2012

Greating this is my first post, also with a problem with a egalaxy touch it works as a mouse, when i toch the screen, it doesnt click im using ubunto 12 lts, Apreciated for the Help