That’s the correct way to do it. At least it worked for me when I am using a
Elotouch screen with the smartset protocol.
By changing the value, it causes a swap in the co-ordinates and it should
work just fine.
“Ken Schumm” <> email@example.com> > wrote in message
Don’t know if this applies to your case, but try changing the
last 0 in the absf.1 file to a 1. This is a “swap” bit needed
in some cases that I don’t remember.
Previously, Barry Robertson wrote in comp.os.qnx:
My latest calibration attempt:
Values reflected by acalib when I pressed them:
The absf.1 file contains:
0x0:639x479:66 919 102 939 0
I understand the 0x0:639x479 bit. But the
“66 919 102 939” bit has me confused if it’s
supposed to be where I pressed (top,left)
(bottom,right) x,y coordinates.
After calibration, x and y were crazy (swapped).
I exited photon and restart it, and x & y were
back to normal.
So, I’m still hung up on the last section of the
Mike Taillon wrote:
Barry Robertson <> firstname.lastname@example.org> > wrote:
I’m having problems with ‘acalib’. I’m following the directions
as prompted by ‘acalib’. They work at one point. I tried it
again, and then, as I go down, it goes right. As I go right,
it goes down. As x should increase, y increases. As x should
decrease, y decreases. As y should increase, x increases.
As y should decrease, x decreases instead.
sounds like you have x and y swapped.
after calibration, try slaying and restarting Input.
does that ‘fix’ it ?
At one point months ago, the connector was wrong. Out of probably
30 attempts at calibration to see what was wrong, 3-4 of them
resulted in a good calibration. Ideas?
changing the connector, may have changed the x/y swapping…
I’d also like to know if anyone knows the format of the
/etc/config/absf/absf.x (x is 1 in my case) file. I’ll
write my own calibration routine if anyone know’s what
the format is. It looks easy enough, but might require lots
of trial and error.
“%dx%d:%dx%d:%d %d %d %d %d”,
screen_upper_left_x, screen_upper_left_y, //
screen_lower_right_x, screen_lower_right_y //
usually graphics mode (639x479)
touch_upper_left_x, touch_upper_left_y //
touch_lower_right_x, touch_lower_right_y //
more acalib values
// 0 means no swap, 1 means swap
Anyone else seen weird behavior with ‘acalib’?
Thanks for your time,