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 -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
