This repository has been archived by the owner on Feb 5, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 7
Accelerometor readings are wrong, also wrong timestamp #23
Comments
simensrostad
added a commit
that referenced
this issue
Mar 10, 2020
accelerometer data values. Closes #23 Signed-off-by: Simen S. Røstad <simen.rostad@nordicsemi.no>
simensrostad
added a commit
that referenced
this issue
Mar 10, 2020
Removed static keyword to prevent persisting accelerometer data values. Closes #23 Signed-off-by: Simen S. Røstad <simen.rostad@nordicsemi.no>
🎉 This issue has been resolved in version 1.3.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This is still broken in v1.6.2:
|
It looks like the readings are not reset, but kept in memory:
Exact same readings reported, but timestamps are added. |
Does the problem still persist given the latest commit. 615cd85 ? |
These are three different accelerometer readings transmitted to cloud from my device. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
These are 4 different readings, note how they alternated between two states, also the timestamp is wrong:
3167027337385
seems like a timestamp is added to another timestamp.The text was updated successfully, but these errors were encountered: