Autosport Labs

<t>Ok that makes sense. My output log files have been longer (in time) than what is recorded in Race Analyzer, which seems like we are having the same issue.<br/> Logging everything at 10Hz seemed to solve the empty cell issue, and there was ~0.05s time "drift" (in a ~13 second test log) which is le...

Ok. Let me know what I can do to help, if anything. I'm looking forward to hearing what your results are.

I was seeing the empty cell phenomenon recently too - http://www.autosportlabs.org/viewtopic.php?t=4115 though I'm not sure which firmware I was testing with. Different logrates as well - my GPS time was logging at 1Hz. Have you discovered a solution to it yet? I checked on one of the bench files I...

Hmm, interesting, thank you. Can you downgrade to 1.2.7 and do a quick test there? We are soon releasing the 2.0 firmware beta + App, I will check to make sure this problem doesn't exist here. Thanks for reporting it. Ok so running it at 1.2.7 produces the same problem at multiple frequencies (abov...

Well that sounds annoying. Was it drifting forward or backwards? I'm still trying to figure out the empty cells and inconsistent clock intervals before I can start looking for drift.

Sure thing Brent. Here are the .log files which I pulled off my SD card from 2 bench test files. When you import the data into Matlab or Excel, you'll see the empty cells issue I was talking about on the 30 Hz file. What it appears to be is the RC is only writing a values per "X" given fre...

Hi Brent, I also seem to be having problems with this (having downloaded and installed the latest software and updated firmware). Additionally, when I go to export the data to Excel, MatLab, etc, I end up with blank cells and clock value repeats if I run any channel above 30Hz, and inconsistent cloc...

Sorry to bring this back from the dead, but I am seeing no resolution to this issue so far, and am suffering from the same problem. Did you ever resolve this problem with your data analysis diamondjack? Additionally to the jacked-up clock intervals, I am getting a bunch of "null" value (em...