-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sensor Data Alignment with Real Time #5
Comments
That's a good idea! Unfortunately, the Movesense device shuts down entirely when it goes off and stops counting on the internal time. As you seem to have figured out yet, the delay between the sensor and the end device is hard to predict. My personal recommendation to solve this issue is: Use the fact that the sampling rate is very reliable.
If you have found a better solution or have another idea, please let me know and I will test it. |
Guten Morgen! Thank you for your proposed solutions -- I am trying to utilize both methods you have suggested, but I am also working on implementing a GATT service to push the current UTC timestamp over to the sensor. I wanted to ask if you had any recommended methods to debug firmware aside from Movesense's debug jig? |
I don't have the debug jig, so I was debugging with the try&error and sometimes used the LED to debug. But afaik there is no wasy to have something like a serial communication for logs without the debug jig. |
Is your feature request related to a problem? Please describe.
I am currently attempting to use this firmware with a Python application. I would like to align the sensor data with the time coming from an NTP server to make this easier.
Describe the solution you'd like
Would it be possible to push a UTC timestamp to the sensor through a GATT service and receive that timestamp along with the data from the ECG and IMU GATT services?
Describe alternatives you've considered
I've tried several means of compensating and offsetting the time, but I have consistently found myself +- 1.5 seconds off from a video recording of an event, which is aligned with our NTP server.
The text was updated successfully, but these errors were encountered: