Data buffering - temperature accuracy - timestep
I have been testing a MetaMotionR and I would like to use it in different projects but I stumbled upon some problems. Can you please help me with the following questions?
It seems to me that data streaming immediately quits whenever connection is lost. Is there a possibility to buffer data? If I would write an app that would automatically look for reconnection, would it be possible to buffer data in the gaps of connection?
In the datasheets, it states that the accuracy of the temperature sensor is ±5°C. Is it possibly to improve this accuracy with another temperature sensor or will it be limited by the self-heating of the sensor? Is there an offset temperature known?
I also noticed that the timestep between measurements changes inconsistently, resulting in missing timestamps. For example, I made a measurement of ambient light at 10 Hz which counted 5564 samples, so you would expect the last sample to be at 556.4 s. However, the elapsed time was 556.554 s. Does this indicate that we should have measured 5565 samples? In longer time periods, this will result in missing lots of data. Can you explain me why the timestep is inconsistent and how we should deal with this? How would you define a running time window to calculate features if there is no consistent sampling rate?