Metabase: Windows v Android version - timestamp issues
When using the Windows version of Metabase to capture Linear Accelerations from MMR the capture file shows timestamps (epoch ms) that are at irregular intervals and sometimes even have the same value for multiple data points that have different acceleration values e.g.
See Windows_MMR_2020-09-21T18.104.22.1685_E639F9D62615_LinearAcceleration_100.000Hz.xlsx attached. Note - the csv file was saved as .xlsx since this forum won't allow attaching .csv files. This behaviour is repeatable. What I expect is data points with timestamps 10ms apart.
I have run similar Linear Acceleration captures using Metabase on Android. The resulting file is as I would expect, 10ms intervals between each data point:
epoch (ms),time (16:00),elapsed (s),x-axis (g),y-axis (g),z-axis (g)
See Android_MetaWear_2020-09-21T22.214.171.1242_E639F9D62615_Linear Acceleration_100.000Hz_1.5.0.xlsx attached.
I have also modified your example C# RealTimeGraph program to capture Linear Acceleration data and write out to a CSV file. The timestamps of each packet are as erratic as when running Metabase on Windows. I've attached the code snippet extracting the timestamp data from the packet.
Is the behaviour of the Windows version of Metabase (or other developed applications running on Windows) what you expect?
Model Number: 5
Motorola MotoG3, Android version 6.0.1, Security patch 1 April 2017
Lenovo IdeaPad Core i7, 8GB RAM
Windows 10 Home, version 2004, build 19041.508