01-10-2018 13:14
01-10-2018 13:14
In the Guide pages - https://dev.fitbit.com/build/guides/sensors/accelerometer/ it says
"...if the device is at rest, lying flat on a table, the acceleration along the Z axis should equal the acceleration of gravity (~9.8 m/s^2), and the acceleration along the X and Yaxes should be 0.
The accelerometer axes readings are provides as signed 16-bit integers, which range from -32,768 to 32,767."
How can the readings be 16-bit INTEGERS if they have decimal places!?
When I display the readings onscreen they clearly have decimal places, lots of them. I can clearly see accel.z equal to approx 9.8............. with lots of decimal places.
I'm in the middle of writing a logging app and was logging it to an Int16Array, I'm gonna now use a Float32Array.
Just wanted to flag this and double check.
Answered! Go to the Best Answer.
Best Answer01-16-2018 14:57
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
01-16-2018 14:57
Thanks for the feedback! Will get this updated.
Best Answer01-16-2018 14:57
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
01-16-2018 14:57
Thanks for the feedback! Will get this updated.
Best Answer