g-sensor calibration problem

Andy Green andy at openmoko.com
Fri Jun 20 11:45:26 CEST 2008

Hash: SHA1

Somebody in the thread at some point said:

| x = -72, y = -990, t = 1.976891 pi
| It's quite reasonable.  However,
| * sometimes after booting
| * always after resume (apm -s)
| the result will look like this:
| x = 1620, y = -36, t = 0.492928 pi

Do you notice any explosion at this time and you fly through the air
horizontally :?)

I don't know what it is, there is a setting on the thing to reduce
sensitivity to increase dynamic range that would change output, but it
would change it down, not to 1620.

1620 is raw count of 90... can you check to see if the output is still
responsive to movement correctly, ie, perhaps the issue is one about the
baseline offset is wrong after powerup and we need to explicitly reset
the thing (it fetches them from internal EEPROM when reset).

I would suspect the raw data is shifted somehow but it doesn't seem
likely the way we bitbang it address-first.

- -Andy
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org


More information about the openmoko-kernel mailing list