Wife test - the same speed/distance/average speed mis-match on iPad/Bike Computer (previously reported on iPad/HUD, although we thought it was unlikely that the HUD/Bike Computer choice was the RCA)
Ian_Adams
•
May 12
I have found the same issue with the average speed being mis-represented. Looking at my speed for long parts of the ride, the average being shown on the screen was probably correct based on the speed the machine says I was doing which was generally above 30 kmh. So the shown average of 30.4 seemed pretty right. What wasn’t going as expected was the distance based on the time being ridden so the average ended up back at 29.5 on strava after completion. Ride was Port Douglas Gran Fondo. I have done this ride before and it was at 30.6 km/h. I don’t believe I have dropped back that far between the rides so ?!?. But it seems that the speed being shown is also incorrect, not just the average.
Klem (FulGaz)
Team•
May 7
Another example from a regular FulGaz ride:
Data uploaded to third-party sites such as Strava reports correct average speed.
Andre Lahouter
•
May 8
@Klem (FulGaz) - I guess the question for me is - what side is wrong? The avg speed calculation or is die speeds/distance depicted for the time wrong? Given the (again) substantial difference between what Garmin reports, I am inclined to say that distance depicted may be wrong. V7.0.5 brought Gramin metric very close to FulGaz metrics only Wahoo Kickr. V7.0.7 puts them very far apart again. I would expect “some” difference but close to 5km over a 40km ride just sounds too big.
Klem (FulGaz)
Team•
May 10
The average speed is incorrect. When the ride is uploaded to third party sites such as Strava or TrainingPeaks, the distance and time match FulGaz but the calculated average speed is corrected.
Garmin metrics will never perfectly align with FulGaz as the Garmin isn’t receiving all of the same information (aero drag, rolling resistance, other physics calculations). More on that here.
EmilyRides
•
May 6
Yes, we are seeing this as well. I did the Moson Tour ride this morning on 7.0.7. At the one hour mark, the on-screen computer showed an average speed of 14.4, but the actual mileage at that point was 13.5. At the end of the ride, the splash screen showed an average of 14.4 mph, but the after-ride email showed 13.55, which was correct (I calculated). This bug used to happen in some of the earlier releases (prior to v.7.x.x) and has now reappeared!
Klem (FulGaz)
Team•
May 5
Also reported on iOS via support from Jo: Screenshot below from end-of ride, 7.59 miles in 33.13 (shown in FulGaz) equates to a 13.71 mph average speed. HUD reporting 14.5 mph average.
Log in to comment and vote
Comments7
Peter Kettle - Crazy Catz
May 13
Wife test - the same speed/distance/average speed mis-match on iPad/Bike Computer (previously reported on iPad/HUD, although we thought it was unlikely that the HUD/Bike Computer choice was the RCA)
Ian_Adams
May 12
I have found the same issue with the average speed being mis-represented. Looking at my speed for long parts of the ride, the average being shown on the screen was probably correct based on the speed the machine says I was doing which was generally above 30 kmh. So the shown average of 30.4 seemed pretty right. What wasn’t going as expected was the distance based on the time being ridden so the average ended up back at 29.5 on strava after completion. Ride was Port Douglas Gran Fondo. I have done this ride before and it was at 30.6 km/h. I don’t believe I have dropped back that far between the rides so ?!?. But it seems that the speed being shown is also incorrect, not just the average.
Klem (FulGaz)
May 7
Another example from a regular FulGaz ride:
Data uploaded to third-party sites such as Strava reports correct average speed.
Andre Lahouter
May 8
@Klem (FulGaz) - I guess the question for me is - what side is wrong? The avg speed calculation or is die speeds/distance depicted for the time wrong? Given the (again) substantial difference between what Garmin reports, I am inclined to say that distance depicted may be wrong. V7.0.5 brought Gramin metric very close to FulGaz metrics only Wahoo Kickr. V7.0.7 puts them very far apart again. I would expect “some” difference but close to 5km over a 40km ride just sounds too big.
Klem (FulGaz)
May 10
The average speed is incorrect. When the ride is uploaded to third party sites such as Strava or TrainingPeaks, the distance and time match FulGaz but the calculated average speed is corrected.
Garmin metrics will never perfectly align with FulGaz as the Garmin isn’t receiving all of the same information (aero drag, rolling resistance, other physics calculations). More on that here.
EmilyRides
May 6
Yes, we are seeing this as well. I did the Moson Tour ride this morning on 7.0.7. At the one hour mark, the on-screen computer showed an average speed of 14.4, but the actual mileage at that point was 13.5. At the end of the ride, the splash screen showed an average of 14.4 mph, but the after-ride email showed 13.55, which was correct (I calculated). This bug used to happen in some of the earlier releases (prior to v.7.x.x) and has now reappeared!
Klem (FulGaz)
May 5
Also reported on iOS via support from Jo: Screenshot below from end-of ride, 7.59 miles in 33.13 (shown in FulGaz) equates to a 13.71 mph average speed. HUD reporting 14.5 mph average.