eGalax touchscreen calibration

[raspuca]

Hi All!! I'm a new member and i like this forum
I ha ve an issue with xBian...i have a eGalax touchscreen usb and the touch is recognized by the xbian, but is not calibrated with my finger...how could calibrate it?? It was perfect for my carpc project!
Thank you very much
Luca

[Markamc]

Hi Luca,

I have my egalax touch screen (car-pc project) working and calibrated with Xbian. I used the Xbian image, it has the kernel modules necessary for touchscreen support. The only thing I did was follow the guide to re-compile xbmc with the patched files from Andrei included. Follow this guide, it worked for me, then you can add the file: usr/share/eGalaxCalibration/touchscreen_axes_calib, with you data and modify the values to adjust your screen calibration (as Andrei describes)

https://github.com/xbianonpi/xbian/wiki/Compiling-XBMC-&-XBMC-dependencies

The only thing I needed to do was remove some coding (link below) as I have stated on Andrei's blog, so I could achieve a double click; I found I had no click just a constant mousedrag error in xbmc

http://engineering-diy.blogspot.co.uk/2013/02/raspberry-pi-raspbian-xbmc-and-egalax-7.html?showComment=1364419629030#c8991511687109589988

Don' forget to make a swapfile, I needed to, to compile XBMC on 256mb pi

For reference, I needed to play with the offset and scale values in the calib file for my 7" 1280x720 touchscreen,
calib fle parameters are as follows:

calib_x_d=1280;calib_x_fact=-0.625;calib_y_d=760;calib_y_fact=-0.374799606;swap_axes=0;

(i scaled the values t fit within a bezel around the screen)

Hope this helps

mark

[CurlyMo]

@Both, can you guys add some log files on how to recognize if this touchscreen is connected? That we can add a condition to stop executing that small piece of code.

[raspuca]

Thanks you very much!! Tomorrow i will try!
@CurlyMo where can i find the log?

[Markamc]

Does this help, I compiled beta1 to get calib to work and removed some code to get double click back. I cut the file down to attach. If you want more let me know

[CurlyMo]

What is the output of cat /proc/bus/input/devices

[Markamc]

(25th Apr, 2013 08:19 AM)CurlyMo Wrote:  What is the output of cat /proc/bus/input/devices

[CurlyMo]

I misunderstood you, so the post where totally irrelevant. So keep this thread clean i removed them.

[Markamc]

I can confirm this works for me. If you like i can email my MouseStat.cpp / LinuxInputDevices.cpp file so you can compare.

---

I appreciate you misunderstood, although I disagree that my post should be removed as being "irrelevant". It took me quite some time to make this work and any help I could provide to the OP should be considered as "relevant" to "his" problem until the beta can provide such fixes for all. Please reconsider, I don't like wasting my spare time

Kind regards

mark

[CurlyMo]

@brantje, can you confirm that if we remove these lines, the device still works (and maybe a little better). That is essentially what Markamc suggested:
https://github.com/xbianonpi/xbian-patches/blob/master/xbmc/eGalaxTouchScreen.patch#L34-L40

[Koenkk]

Note that that patch requires updating, @CurlyMo BTW the patch you commited didn't cause the compilation errors, it was a commit on the XBMC git.

[CurlyMo]

I know, but what i already said, i was recreating a patch that already existed. So my suggestions where irrelevant because i didn't knew that yesterday.

[Koenkk]

I see, but if I understand right, Markamc wants to help is with fixing the eGalaxTouchScreen.patch? (https://github.com/xbianonpi/xbian-patches/blob/master/xbmc/eGalaxTouchScreen.patch )

[CurlyMo]

He suggests removing these lines: https://github.com/xbianonpi/xbian-patch...ch#L34-L40

[Koenkk]

Then try it