Forum

(15th Sep, 2013 09:27 PM)Markamc Wrote: [ -> ]I have just tested the calibration again, I use the 'sh ts_calib.sh' script I originally used and all is ok.

A you just re-run my script or what?
Forgive me my stupidness, but kinda overloaded with new information from all (new school, new job).

(16th Sep, 2013 07:10 PM)brantje Wrote: [ -> ]

(15th Sep, 2013 09:27 PM)Markamc Wrote: [ -> ]I have just tested the calibration again, I use the 'sh ts_calib.sh' script I originally used and all is ok.

A you just re-run my script or what?
Forgive me my stupidness, but kinda overloaded with new information from all (new school, new job).

Forgiven...
I don't use your install script, I still use the calibration script from my tutorial... http://markamc.cybaman.net/?p=50

Thanks, have it working now on beta 2.
Will you update that page when beta 2 is released?

(1st Oct, 2013 09:06 PM)brantje Wrote: [ -> ]Thanks, have it working now on beta 2.
Will you update that page when beta 2 is released?

Yep, I will keep it up-to-date....but there aren't any changes for me to do in beta2? Are they're any you need?

Hello,

First : I am french; sorry if my English is bad.

I have tried the build3 that bboyanddru has posted in this thread.

The calibration seems to be good for me and I like the XBMC skin but an axes is inverted : when I go to the left, the pointer goes to the right : is there a way to correct that?

Thanks per Advanced for your help

EDIT: nvm... (I can't delete my post..)

Hi,

I'm running a salvaged eGalax 1280x768 10.5" screen and it is assigned to event2, XBMC 13.1 on Raspbian.
I used the installer/calibration method details here : https://github.com/brantje/xbian-touch but only touches on the rightmost of the screen register and the x/y movements are inverted. i.e. if I move up, the cursor moves to the left, down=right, left move=down and right move = cursor up.

My pointercal file typically contains :

Quote:-74 -45928 87900184 27751 -139 -2762432 65536 1280 768 1

If I stop uimapper & xbmc & run evtest on event2 I get lots of ABS_X,Y & BTN_TOUCH events with numbers that look a lot like the ones I get if uimapper (input-read.py) is running. Should they be scaled and be quite different numbers for the coordinates?

Can anybody offer suggestions. It seems so close to working.

Thanks,
Steve

Even after running ts_calibrate the axes are inverted?

(27th Jun, 2014 06:25 AM)ph87 Wrote: [ -> ]Even after running ts_calibrate the axes are inverted?

Yes. The typical output after pressing the 4 corners & one center point on the screen:

Quote:xbmc stop/waiting
uimapper stop/waiting
Please follow the instructions on the display...
xres = 1280, yres = 768
Took 4 samples...
Top left : X = 232 Y = 1836
Took 5 samples...
Top right : X = 213 Y = 166
Took 7 samples...
Bot right : X = 1780 Y = 162
Took 6 samples...
Bot left : X = 1796 Y = 1857
Took 4 samples...
Center : X = 996 Y = 1000
1340.453003 0.003813 -0.701333
-39.703735 0.426713 -0.004441
Calibration constants: 87847928 249 -45962 -2602024 27965 -291 65536

Steve

Have you tried with another event? As you have a egalax it should work - I've got a N-Trig and had to choose a other event to get it work! I've described my solution in Post #191 in this thread!

As I'm not a developer let's hope brantje will have a look around here a write a pm to him!

BTW... There is an update for the touchscreen patch but I didn't get enough help to compile xbian with that update!

(27th Jun, 2014 10:07 PM)ph87 Wrote: [ -> ]Have you tried with another event? As you have a egalax it should work - I've got a N-Trig and had to choose a other event to get it work! I've described my solution in Post #191 in this thread!

As I'm not a developer let's hope brantje will have a look around here a write a pm to him!

BTW... There is an update for the touchscreen patch but I didn't get enough help to compile xbian with that update!

evtest only lists /dev/input/event2 belonging to the eGalax. The other two events are mouse & keyboard.

If I run input-read in the foreground with uimapper & xbmc stopped I get ABS_X/Y & button events debug. I guess this is used as an input to XBMC, but is supposed to be scaled for the display?

Stop uimapper & xbmc and execute this in the foreground to get event diags:

Quote:/scripts/uinput-mapper/input-read.py -v /dev/input/event2

I'll investigate this & pm brantje if I get nowhere.

Cheers, Steve

Hi,

I've PMd brantje, but just in case anyone else can help, here's what was said:

How does uimapper work? Does it sit on the screen event (from the kernel?) and create another event for use by XBMC with scaled coordinates? I've done more tests and cannot see any proof that a new event is created if that is the case:

Quote:pi@raspbmc:/scripts/uinput-mapper$ sudo start uimapper
uimapper start/running, process 15186
pi@raspbmc:/scripts/uinput-mapper$ ps aux|grep input-
root 15403 0.7 1.3 8332 5084 ? S< 13:30 0:00 python ./input-read.py /dev/input/event2 -v
root 15404 0.5 1.3 8416 5076 ? S< 13:30 0:00 python ./input-create.py configs/touchscreen.py

pi@raspbmc:/scripts/uinput-mapper$ evtest
No device specified, trying to scan all of /dev/input/event*
Not running as root, no devices may be available.
Available devices:
/dev/input/event0: Dell Dell USB Entry Keyboard
/dev/input/event1: PixArt USB Optical Mouse
/dev/input/event2: eGalax Inc.
Select the device event number [0-2]: 2
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0xeef product 0x1 version 0x100
Input device name: "eGalax Inc."
Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
Event code 330 (BTN_TOUCH)
Event type 3 (EV_ABS)
Event code 0 (ABS_X)
Value 170
Min 0
Max 2047
Event code 1 (ABS_Y)
Value 1854
Min 0
Max 2047

Any ideas to investigate this further are very welcome.

Thanks, Steve

(27th Jun, 2014 10:07 PM)ph87 Wrote: [ -> ]BTW... There is an update for the touchscreen patch but I didn't get enough help to compile xbian with that update!

XBian (for now for RPI) is using them.
check XBMC 13.2 B3 from staging

Dear All,

Thank you for your effort and inputs to this topic! I finally have touch works on my RPi B+...

I install Xbian, evtest and follow the guidance from Mark: http://markamc.cybaman.net/?p=50. My screen is 800x480 with eGalax touch driver. After successfully running Mark's solution, both manual and automatic script from Brantje, my screen is still in wrong calibration. Below are the steps that I have my touch works:
- First, stop uimapper and xbmc, then run evtest to monitor event2, which is currently my eGalax. Note the x and y value of my screen's 4 corners.
- Start uimapper, then again run evtest to monitor even4, which is currently uimapper. Note the x and y value of 2 corners.
- I see that the axes value from uimapper is offset around 400+ for x and 200+ for y. Look at Mark's script, these value equal to (xmres - xsres) and (ymres - ysres), so I modify touchscreen.py like below:
x = (x*xscale + xoffset)*xcalib/(scaler)# + (xmres - xsres)
y = (y*yscale + yoffset)*ycalib/(scaler)# + (ymres - ysres)
- Re-start uimapper, run evtest to monitor event4, top-left corner is (x= -10, y=29), bottom right is (x=779, y=466). They are not so accurate to 800x480. But re-start xbmc, the touch behaviour is fine!

The next problem I'm facing is the lagging when playing video or .mp3 files. When playing a .mp3 file, the music is continuously corrupted / lagged. Then I stop uimapper, the lagging seems gone, but when the screen goes dim, the music is corrupted / lagged. How can I solve this? Do I have to upgrade my RPi B+ to a RPi 2?

Thanks & best regards,
TuongNguyen

Hey, thanks for doing this. I just installed the latest xbian on a RPi3, and connected it to an Acer touchscreen, when I run your install script, the touchscreen is recognized and the calibration proceeds normally, but back in Kodi there is no response to the touchscreen... any ideas how to patch this up for the new xbian?

M

(9th Jul, 2013 07:47 AM)brantje Wrote: [ -> ]

(9th Jul, 2013 07:35 AM)Markamc Wrote: [ -> ]You're not wrong! , atm I have virtualbox running too ubuntu. Plays havoc with device managment

Try multi boot, i got it too =).

But to stay on topic, i made an github:
https://github.com/brantje/xbian-touch/

If you want you can change your download links (wget commands)

Code:

https://github.com/brantje/xbian-touch/raw/master/ts_calib.sh
https://github.com/brantje/xbian-touch/raw/master/tslib_1-1_armhf.deb
https://github.com/brantje/xbian-touch/raw/master/uimapper.tar.gz
https://github.com/brantje/xbian-touch/raw/master/uimapper.conf

Using this, will make sure when they download, they got the latest version.
Another idea is to push it into the xbian repo so it can be installed via apt-get install xbian-touch orso.

Are you okey if i copy your blog article to the github readme?