I'm hoping to use the Thing52 for orientation tracking but am noticing the following issues when experimenting with the Thingy android app (version 1.3.4). My thingy is running the factory firmware version 2.1.0 and the compass compensation interval is still set to the default of 500ms.
If I rotate the device smoothly on a table, the heading output looks to also change smoothly and appears to be correct. However, the cube animation sometimes has small jumps (often in the opposite direction of the rotation), which may be happening when the orientation algorithm gets an update from the magnetometer. I've also noticed that placing the device back in the starting orientation on the table does not cause the animated cube in the app to return to the starting orientation. This works in pitch and roll axes, but not heading. It seems as if the algorithm outputting the quaterernions is not using the magnetometer to set the absolute heading.
I've hooked up the Thingy to my own android app (using the BLE quaternion characteristic) and am seeing the same problems, so I believe it's a firmware or hardware issue rather than a bug in the thingy android app. Has anyone else reported similar problems and are there are known solutions?
Thanks
Andrew
