Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Cadence on 520 different from that on Garmin Connect

Tpcorr
over 9 years ago
Today I did a ride, and when I looked at the ride summary on the 520 it had my average cadence as 85 rpm. This is my usual cadence, give or take a few rpm. When I synced the ride to Garmin Connect and viewed it, it had my average cadence as 71 rpm. Why this discrepancy? I have about 40 rides on GC and this anomaly has never occurred before. So I have 2 questions. Why did this happen, and is there a way to prevent it from happening again? Is there an easy way to edit the data to more accurately reflect my cadence?

Thanks

Tom
  • 0 over 9 years ago
    I did change my activity type to road cycling. I switched it back last night, but have yet to do a ride with the new (old) setting. The issue is not with 6.20, because I've done several error free rides on 6.20. I only recently changed the activity setting, so I'm hoping this is the problem.

    Tom
  • 0 over 9 years ago
    Moving time being close to elapsed time instead of time is not correct. I don't have this problem with 6.2. Is it part of the "set activity type" problem?

    Agreed, moving time should not be close to elapsed time. I have auto-pause enabled and activity in GC website shows "Cycling" - I haven't checked activity type on my Edge 520. Is this a new setting on the Edge 520?

    Below find a comparison of two Wed night group rides showing the difference I'm seeing in connect.garmin.com (web) and on my iPhone app:

    [TABLE="width: 500"]
    [TR]
    [TD]Firmware 6.20
    ride: June 29[/TD]
    [TD]Firmware 6.0
    ride: June 1[/TD]
    [/TR]
    [TR]
    [TD][FONT=Open Sans]1:29:24
    Time[/FONT]
    [FONT=Open Sans]
    1:43:02 (Strava: 1:29:41)
    Moving Time[/FONT]
    [FONT=Open Sans]
    1:43:10
    Elapsed Time[/FONT]
    [FONT=Open Sans]
    19.5 mph
    Avg Speed[/FONT]
    [FONT=Open Sans]
    16.9 mph (Strava: 19.5)
    Avg Moving Speed[/FONT]
    [FONT=Open Sans]
    28.0 mph
    Max Speed[/FONT][/TD]
    [TD][FONT=Open Sans]1:40:30
    Time[/FONT]
    [FONT=Open Sans]
    1:40:19 (Strava: 1:40:20)
    Moving Time[/FONT]
    [FONT=Open Sans]
    1:58:09
    Elapsed Time[/FONT]
    [FONT=Open Sans]
    18.2 mph
    Avg Speed[/FONT]
    [FONT=Open Sans]
    18.3 mph (Strava: 18.3)
    Avg Moving Speed[/FONT]
    [FONT=Open Sans]
    29.2 mph
    Max Speed[/FONT][/TD]
    [/TR]
    [/TABLE]

    EDIT:
    This is a GC problem that started around 8:00am PDT (1500 UTC) on Wednesday, 29 June 2016. I have a ride that ended at 7:57am and moving time is correct. Then I have a ride that started at 8:11am and moving time is wrong. See discussion below.
  • 0 over 9 years ago
    yeah, something not right....i checked my yesterday ride. moving time on gc is 4:17 hrs..... moving time on strava is 3 hrs....

    I did have long break during the ride.

    This has to do with the activity thingy.
  • 0 over 9 years ago
    Avenue lamarck

    Agreed, moving time should not be close to elapsed time. I have auto-pause enabled and activity in GC website shows "Cycling" - I haven't checked activity type on my Edge 520. Is this a new setting on the Edge 520?


    Hi 2nfinite,

    Yes, this is a new setting on the 520. It allows you to categorize a specific activity type. For instance, prior to 6.2, the activity profile I created and named "Club Ride" would be categorized as cycling. But with the advent of 6.2 you are allowed to change that to road, gravel, mountain, ebike, etc. I did change my club ride profile to road. This is when I first noticed the discrepancy between the cadence as recorded on the 520 and that displayed in GC. Now, of course, I'm noticing that the stopped time is being incorporated into the moving time. It never did that before.

    A previous poster to this thread said the cadence issue is solved by changing back to the default "cycling" for the activity profile you are using. I'm not so sure this will solve the moving time issue though. I say this because I recorded my last ride with both the edge 520 and the forerunner 235. The moving time issue occurred with both the 235 and the 520. So I believe this is an issue with GC, perhaps unrelated to the category you choose.

    I'm doing a ride this morning and have changed my category for my "Club Ride" profile back to cycling, which is the default. I will record this ride with both my 235 and 520. I'll report back here with the result.

    I believe this is only an issue for some, or else these boards would be on fire with such a fundamental error in the computation of average speed, moving time, and stopped time. Do you think Garmin is aware of this problem? I haven't called Garmin support yet. Do you think they might be following this thread, or should I call them.

    Thanks

    Tom
  • 0 over 9 years ago
    yeah, something not right....i checked my yesterday ride. moving time on gc is 4:17 hrs..... moving time on strava is 3 hrs....

    I did have long break during the ride.

    This has to do with the activity thingy.


    I don't think it's related to the activity type thing on the Edge.
    It's a GC error that came some time between 0600 and 1500 CET wednesday this week. Its the same for my Fenix 3 and my Edge 520.

    My morning ride and previous rides were OK, my aftenoon ride (and all later rides)were not.


    Stig
  • 0 over 9 years ago
    I don't think it's related to the activity type thing on the Edge.
    It's a GC error that came some time between 0600 and 1500 CET wednesday this week. Its the same for my Fenix 3 and my Edge 520.

    My morning ride and previous rides were OK, my aftenoon ride (and all later rides)were not.


    Stig


    Is this the type of thing we should report to Garmin, or do you think they are already aware of this?
  • 0 over 9 years ago
    So, changing back to the default "cycling" fixed the cadence issue, but GC is still including stopped time in moving time, as evidenced by this file.

    https://connect.garmin.com/modern/activity/1236890019

    Not sure what to do at this point, any ideas?

    Tom
  • 0 over 9 years ago
    It's a GC error that came some time between 0600 and 1500 CET wednesday this week. Its the same for my Fenix 3 and my Edge 520.

    Agree, and I can pinpoint the time.

    Correct moving time: Wednesday, 29 June 2016 ride at 7:25am PDT that finished at 7:57am PDT
    Wrong moving time: Wednesday, 29 June 2016 coffee ride at 8:09am PDT that finished at 8:55am PDT

    The GC problem appears to have started around 0800 PDT, which is 1500 UTC/GMT.