1rpm average speed difference every single ride

Without seeing the actual data I would guess that GC and the Edge are using different rounding algorithms.

The Edge is round up while the GC is giving you the "floor".

E.g. 89.6 is being reported at 90 by the Edge and 89 by GC.

Can you post one of the FIT activity files where you observed this difference?

Hey,

my 520 shows average cadence while riding, let's say 90rpm for instance until the end of ride. After saving it, Garmin Connect displays one rpm less number, 89rpm in this case - every time!!

Strava views 90rpm of course. It's really annoying when you're trying to reach specific AVG CAD number.

Can someone help me with this one?

Thanks

D.

1.11% error - 89.49 would round to 89, 90.51 would round to 91 - 2.22(ish) error

Thanks

Without seeing the actual data I would guess that GC and the Edge are using different rounding algorithms.

The Edge is round up while the GC is giving you the "floor".

E.g. 89.6 is being reported at 90 by the Edge and 89 by GC.

Can you post one of the FIT activity files where you observed this difference?

Thanks for reply,

I didn't mention that 520 after activity save shows the same number in History>Rides as Garmin Connect later on PC. But at the time when I ride, it shows different number.

Here are samples, Strava X Garmin Connect comparsion and also *.fit file :)

Thanks

Garmin Connect takes the cadence value from the session record in the FIT file.

It looks like the Edge simply truncates the average value.

From the data values in the data file the average rpm is 89.65742 (excluding zero values)

The Edge reports that as 89, which Garmin Connect then also reports. Strava computes its own values from the data and they round it to 90 rpm.