From: "Simon Wood" <simon@mungewell.org>
To: Roderick Colenbrander <roderick@gaikai.com>
Cc: linux-input@vger.kernel.org, Frank Praznik <frank.praznik@gmail.com>
Subject: Re: [PATCH 1/2] HID: sony: Adjust value range for motion sensors
Date: Thu, 6 Oct 2016 09:16:09 -0600 [thread overview]
Message-ID: <dfff4e665925857655866517466a7000.squirrel@mungewell.org> (raw)
In-Reply-To: <AB243ECF-9931-4C76-9E54-A9D15E06C3F4@gmail.com>
On Thu, October 6, 2016 8:27 am, Frank Praznik wrote:
>
>> The motion sensor values are 16-bit, so make the value range match.
>> It is hard to reach the upper values, but they can be reached. At
>> least the current accelerometer value of 8192 is very easy to pass.
>>
>>
>
> Are the gyro values intended to be scaled in any way? The current
> min/max values were based on the observed maximum extents of the
> controller at rest. With this change the controller at rest will never
> appear to be turned more than 22.5 degrees in any direction to an
> application which assumes that the logical extents represent the device
> at 90 degrees.
Don't forget that the _gyro_ values are a 'rate of turn' ie. 'degrees per
second'.
Since we're asking questions, I'd love to know more about the time
stamping of the accel/gyro data as this could improve AHRS/Kalman
performance significantly.
In the Move we get two sets of accel/gyro data, what's that about?
Simon
next prev parent reply other threads:[~2016-10-06 15:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6BB4B6CF-1DB7-4F90-8D7F-558407E57203@gmail.com>
2016-10-06 14:27 ` [PATCH 1/2] HID: sony: Adjust value range for motion sensors Frank Praznik
2016-10-06 15:16 ` Simon Wood [this message]
2016-10-06 16:20 ` Roderick Colenbrander
2016-10-06 2:18 Roderick Colenbrander
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dfff4e665925857655866517466a7000.squirrel@mungewell.org \
--to=simon@mungewell.org \
--cc=frank.praznik@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=roderick@gaikai.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).