eGalax touchscreen calibration

[Markamc]

(16th Aug, 2013 07:31 AM)ph87 Wrote:  Sorry guys, but I need your help - I can't get it work!!!
With evtest all does work!!
I've updated the config.txt (ts_calibrate recognizes the resolution right now!!!)


Does the install.sh update the etc/pointercal automatically?

Do I've to disable Andrei's method to use yours?

This is my ts_calibrate output:

Code:

Please follow the instructions on the display...
xres = 1280, yres = 720
Took 10 samples...
Top left : X =  429 Y =  456
Took 12 samples...
Top right : X = 9256 Y =  558
Took 5 samples...
Bot right : X = 9323 Y = 6674
Took 8 samples...
Bot left : X =  458 Y = 6763
Took 9 samples...
Center : X = 4809 Y = 3690
-3.933105 0.133389 -0.001012
-1.697876 -0.000066 0.099779
Calibration constants: -257760 8741 -66 -111272 -4 6539 65536

After calibration the Mouse Arrow is about 20cm away...


Edit:
When stopping uimapper the calibration is right (maybe then I Andrei's version is active - but Single click doesn't work every time)

Andrei's patch is the default config for your TS and will work with the calib file, if uiimapper is not running then it will use the the calib file you posted initially and will not have single click/BTN_RIGHT.

If you run the install script and therefore ts_calib then it will create a new pointercal file.

Are you sure it's 20cm (200mm) away? How big is your TS?

You can check that uimapper is running correctly by typing in ssh...

Terminal

ps aux

output contains...

Terminal

...
...
root 2482 19.6 1.3 8328 5104 ? S< 22:04 0:01 python ./input-read.py /dev/input/event3 -D
root 2483 17.8 1.3 8328 5116 ? S< 22:04 0:01 python ./input-create.py configs/touchscreen.py
...
...

can you see the python script running, this is is the uimapper processes creating the userinput from the egalax event3.

Also check the TS in evtest with uimapper started/stopped and see if the co-ordinates are different, i.e. top left and bottom right, values should be scaled and offset and within the screen resolution when using uimapper.

Terminal

stop xbmc
stop uimapper
evtest

Terminal

stop xbmc
start uimapper
evtest

You can diagnose x,y co-ordinates in xbmc too. In the skin folder you can edit addon.xml file. Changing debugging="false" to "true" displays the pointer position on the screen. Using this you can see how the overscan effects the pointer max/min values

http://wiki.xbmc.org/index.php?title=Addon.xml

If the pointer seems laggy, you can change the nice value in uimapper.conf file), this increases the process priority, mine is at -7 by default, but you could (not recommended) go upto (down-to) -20.....-10 makes a big difference. Recently many process values have changed a lot to -20 to increase priority. -20 to +20 (hig>low). Type in SSH to see...

Terminal

ps -efl

Let me know how you get on,

mark