I am working on a project where I want to get very accurate data from an accelerometer. I plan on sending my data over bluetooth to be interpreted by a computer.
I am assuming that bluetooth will have some unknown delays that come from things such as how Windows handles the data.
So, since the accelerometer data is time depended, would I be benefited by using a clock that can easily create time in some even divisor of seconds? Or possibly add a RTC? I would then be able to "time-stamp" my data before sending it over bluetooth.
Is this worth it or am I just over thinking how accurate I can actually get my data to be?
I will be pulling in data based off of a timer interrupt. I am wondering if my timer needs to be something like 0.5ms. I would go ahead and "time-stamp" the messages I am sending so I know if I loose a message for some reason.
Also, I am using a digital accelerometer, so I am not doing an ADC, instead I am getting the measurements over I2C.