More granular export/logging?
Posted: Wed Jul 25, 2012 5:36 am
Hi,
I'm looking at lap timer / logger apps, and this is a nice one
I have 2 things I'd like to see before purchasing, any chance these are coming in v16? (btw, when is that due to be released?)
1. Right now, based on exports, it looks like logging is done every second, sometimes skipping a second (is it based on GPS lock?) Would be nice to see more granular data, say 10 Hz. From what I understand, accelerometer data is read @10Hz. Would love to see it at that rate in the logs to better analyze braking zones and turn limits.
2. I understand that logging of the location is done with every GPS update. But using accelerometer (and may be compass?) data, I think it should be possible to augment 1Hz GPS updates to produce, say, 10Hz coordinates. Have you looked into this? Simple and fast regression model can keep it calibrated based on a few of the latest GPS points and past accelerometer input as a reference.
#2 would be something of interest to me as a project on it's own, so if you don't have it in the upcoming v16, or haven't started working on it yet - I can help with the development. Like draft and test a logic, write a function, etc so that you can plug it in the code for the upcoming version. Let me know if you're open to that
I'm looking at lap timer / logger apps, and this is a nice one
I have 2 things I'd like to see before purchasing, any chance these are coming in v16? (btw, when is that due to be released?)
1. Right now, based on exports, it looks like logging is done every second, sometimes skipping a second (is it based on GPS lock?) Would be nice to see more granular data, say 10 Hz. From what I understand, accelerometer data is read @10Hz. Would love to see it at that rate in the logs to better analyze braking zones and turn limits.
2. I understand that logging of the location is done with every GPS update. But using accelerometer (and may be compass?) data, I think it should be possible to augment 1Hz GPS updates to produce, say, 10Hz coordinates. Have you looked into this? Simple and fast regression model can keep it calibrated based on a few of the latest GPS points and past accelerometer input as a reference.
#2 would be something of interest to me as a project on it's own, so if you don't have it in the upcoming v16, or haven't started working on it yet - I can help with the development. Like draft and test a logic, write a function, etc so that you can plug it in the code for the upcoming version. Let me know if you're open to that