Granted, I'm still learning how to use my iAero, but I do believe I know how to use the trip reset function correctly. Yesterday I went out to do hill repeats and wanted to have a discreet file for every climb, so I did a trip reset at the start and end of each climb. Each of the three climbs actually took between 13:15 and 13:45, but each of the ride files I downloaded only showed the first 9:15 to 9:45 of the rides? It was a gusty windy day, but the ride files for my rides to the climb and home again appeared to be complete files (19 minutes reported on the ride to the climb, 26 minutes reported on the longer way home).
Thanks for any help you can provide. I've got a benchmark test scheduled for tomorrow and want to be sure I'm able to capture the test data in its entirety.
truncated ride files
Re: truncated ride files
I thought I had that problem once. It ended up that I had zoomed in by time to 10 minutes instead of showing full ride.
Fernando
Re: truncated ride files
I noticed this week that I'm having the same issue with my iAero. I did a ride a few days ago that lasted just over 50 minutes according to my iAero display. However, after I downloaded the ride, I noticed that the ride file recorded a ride time of 46:00. Looking at the charts in iBike 2, it looks like the last four minutes or so weren’t recorded. I went out on another ride this morning, and as I came to the end I made sure to note the total ride time in the iAero display to check against the downloaded ride file’s time. The ride time per the iAero display was 1:58 (one hour, 58 minutes), and the mileage was 34 and some change. However, the ride time per the downloaded file was only 1:53, and the mileage was 33.27. Again it appears that the last few minutes of my ride weren’t recorded. For these particular rides, it’s not a big deal, because I’m just missing some cool down time anyway. However, it would be a problem if you are trying to capture intervals as distinct ride files. Is this normal or indicative of a problem is the iAero?
Thanks,
Jason
P.S. Happy to send ride files if needed...
Thanks,
Jason
P.S. Happy to send ride files if needed...
-
- Site Admin
- Posts: 392
- Joined: Fri Jan 11, 2008 8:52 am
- Location: Durham, NC
Re: truncated ride files
There is a known-issue with the 2.0.6 release that could cause you to loose up to the last 60 samples of a ride file unnecessarily. If you are using the 5 s sampling rate, that translates up to 5 minutes. There will be a fix for this in the next release, but in the mean time you can minimize the problem by using the 1 s sampling rate and avoid using the trip reset mid-ride. You can always split the ride file later using iBike2.
Travis
Travis
Re: truncated ride files
Thanks for the update, Travis. I am using 5 sec recording, so that would correspond to the 5 min truncations I'm seeing.
Jason
Jason
Re: truncated ride files
I'm also experiencing this but I have another bit of info. The ride file is truncated some, but there is more data in the ride file then there is being shown in the ibike2 software.
My ride file (based on past experience) should be about 11 minutes.
Going by the timestamps in the csv (when you open it) the time elapsed was 10:50.
However, the csv file (when you open it) is only 86 samples (7:10 @ 5 second sampling)
But, the ibike2 software truncates it further and reports the ride time as 2:35.
Happy to provide the file (and the one before and after) if you want it.
My ride file (based on past experience) should be about 11 minutes.
Going by the timestamps in the csv (when you open it) the time elapsed was 10:50.
However, the csv file (when you open it) is only 86 samples (7:10 @ 5 second sampling)
But, the ibike2 software truncates it further and reports the ride time as 2:35.
Happy to provide the file (and the one before and after) if you want it.