I've been working on pulling data from an MPU-9150 for a data filtering project, and I ran into a issue that I'm not sure of the cause.
When I set the accelerometer to ±2g or ±4g range, all the raw values are even (i.e. evenly divisible by 2). However, if I set the range to ±8g or ±16g, the values can be even or odd.
I've been in touch with Invensense tech support because of a different issue of spiky data distributions, however they didn't think there should be a reason the values should be only even. I've run into this issue using my own code as well as Jeff Rowberg's I2Cdev MPU-9150 library.
What I'm looking for is some more opinions on what might be the reason behind this as I wait to hear back from Invensense. I'm far from an expert on MEMS architecture, and there are tons of computer science nuances that I'm sure I'm unfamiliar with, but I'd like to hear if people have an idea on why I'm getting what seems like an anomaly.
Please let me know if I can provide more information.