Accelerometer Readings

so I'm reading accel data via BLE directly, and that's example of what i get:

{"0":3,"1":4,"2":132,"3":251,"4":246,"5":1,"6":194,"7":222}

where 0->3 - means it's accel data
and then there is stange thing going on

3, 5 and 7 bytes are steady when device is not moving  (so I should consider that's a vector)

but 2, 4, 6 bytes are REALLY JUMPY and always changing, and even if i pick the board up and then return it in exactly same position as it was placed before, the numbers even in their overal value are very different from what they were before, so it doesn't seem those are accelerometer values but rather something like "non integer" part of "power vector"

is it so?

or can someone explain to me what exactly are those 6 numbers in accel reading and why is 2,4,6 very jumpy and 3,5,7 steady?

thank you in advance

Comments

  • Acceleration data is 2 bytes per axis which have differing resolutions depending on the g range.  You can refer to the C++ code to see how to interpret it.

    All the time you are spending trying to reverse engineer the MetaWear protocol can be better put to use resolving the issues you have with the Cordova plugin.  I highly recommend you respond to this post from @lgleasain who maintains that project.
This discussion has been closed.