[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <loom.20120113T175122-168@post.gmane.org>
Date: Fri, 13 Jan 2012 17:09:01 +0000 (UTC)
From: el es <el.es.cr@...il.com>
To: linux-kernel@...r.kernel.org
Subject: Re: HID device calibration - how to override mapping?
Enrico Mattea <ocirne94 <at> gmail.com> writes:
(sorry for excessive trimmings, but gmane web i/f made me do it)
>
> Hello all,
> [...]
> [...] while the clutch pedal sends 0 to -32767 to +32767 to 0
> (from released (0) to halfway (-32767), then the value jumps to +32767,
> then decreases again to 0 when fully pressed).
released - halfway - pressed
0 - (-32767) <-> (32767) - 0
but does it happen in reverse order when releasing pedal ?
seems the interpretation of this is up to the application really,
but /if/ the -32767 to 32767 change happens all around the 'halfway'
spot, maybe it is (in the app. engine) interpreted as 'change'
and it's effect applied to 'car engine' not directly, but integrated
(time-integral function applied) first ?
(or if it is the /change/ here that matters , it actually
is a /time-derivative/ that actually applies to the simulation?)
>
> This obviously makes it impossible to properly calibrate the axis for
> anything, because of the "jump" at halfway and of the equality of min
> and max returned values.
I'd say, for the clutch simulation it's the /change-in-time/ that
matters, not the /exact/ value; so no 'static' calibration is
ever going to be relevant (bar maybe the device telling us when the
pedal is fully pressed or fully released - in case app is not tracking
it)
>
[...]
> Thank you very much in advance,
> Ocirne
>
el es
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists