Cadence on 520 different from that on Garmin Connect

I have logged a call and here's the reply....

___________________________________________
Thank you for contacting Garmin International. I'd be happy to continue assisting you. It is not uncommon for the data in Connect and your Edge to not match exactly. The reason for this is because Connect attempts to weed out any possible corrupted information from activities that are recorded. Since this is a considerable discrepancy, I do have some troubleshooting you can attempt.
Please be sure to sync all activity data from your device to Connect before performing the steps below.
1. Connect device to computer
2. Access My Computer/Finder
3. Double-click "Garmin Edge"
4. Open Garmin folder
5. Delete all of the following folders/files: (Note that your device may not have all of these folders)
• Activities
• Courses
• Monitoring
• Newfiles
• RemoteSW
• Segment
• Workouts
• TMP files
1. Close Edge window
2. Delete contents of Recycle Bin/Trash
3. Safely eject device
4. Unplug and power on
Once done, please test the performance of your device for a few days and let us know whether or not you require any additional assistance.

With Best Regards,
________________________________

Thanks for that, Announcement. I won't have a chance to ride until Wednesday at the earliest, but possibly not till Friday. If you get a chance to perform this procedure and ride before then, please report back and let us know if it solved this issue.

Thanks for that, Announcement. I won't have a chance to ride until Wednesday at the earliest, but possibly not till Friday. If you get a chance to perform this procedure and ride before then, please report back and let us know if it solved this issue.

i am not sure if i would perform the procedures.....it is not a device fault... as i mentioned strava and ridewithgps got no issue pulling the cadence data from garmin server.

here's another reply from support:

--------------

Thank you for contacting Garmin International. I am happy to assist you.

If you have zero averaging set to off, the number on the device may be higher than what you see on Connect, which does not have that setting. Since Strava displays what you see on the device, I can only assume that they are using just the data from the device.
I will pass this along to our developers.

Thank you for being a Garmin customer, and have a great day! If you need additional assistance, please reply to this email or you can call 800-800-1020 anytime from 8:00 to 6:30 CST, Monday-Thursday, 8:00 to 5:00 CST, Friday.

-----------------------

here's another reply from support:

--------------

Thank you for contacting Garmin International. I am happy to assist you.

If you have zero averaging set to off, the number on the device may be higher than what you see on Connect, which does not have that setting. Since Strava displays what you see on the device, I can only assume that they are using just the data from the device.
I will pass this along to our developers.

Thank you for being a Garmin customer, and have a great day! If you need additional assistance, please reply to this email or you can call 800-800-1020 anytime from 8:00 to 6:30 CST, Monday-Thursday, 8:00 to 5:00 CST, Friday.

-----------------------

I'd like to thank you all for your replies. This reply from Garmin support is contradictory to the way the 520 has functioned for me in the past. I have zero averaging set to off on my 520 and until recently the cadence number displayed on the device always matched that in Garmin Connect. It appears that tech support rep is ill informed about the way this is supposed to function and has in fact functioned until recently. It's not really that big of a deal, but I'd like it to operate the way it should.

to add:

I got a vivoactive HR and paired it with my cadence meter. it got no issue displaying the correct data on garmin.connect. Hence this is a device/firmware issue on edge 520.

The data is correct on the 520, look at the session record and the history on the device.. The issue is with the way GC is importing it and re-computing the value. It appears to be only doing it for some devices and not all.

The data is correct on the 520, look at the session record and the history on the device.. The issue is with the way GC is importing it and re-computing the value. It appears to be only doing it for some devices and not all.

I did some research.
It is related to the new feature "Set Activity type" that was introduced in 6.03 BETA, and then in 6.20 official. If you select any sub-type of cycling, GC will not recognise the average cadence recorded in the FIT file, and compute its own with zeros included based on all the cadence values recorded. If you stick to the the original activity type "Cycling" everything is as before.
Conclusion: The fault is in GC, but is related to the new "Set avtivity type" feature in 6.20. I guess the problem is also present for Edge 1000.

Stig

I did some research.
It is related to the new feature "Set Activity type" that was introduced in 6.03 BETA, and then in 6.20 official. If you select any sub-type of cycling, GC will not recognise the average cadence recorded in the FIT file, and compute its own with zeros included based on all the cadence values recorded. If you stick to the the original activity type "Cycling" everything is as before.
Conclusion: The fault is in GC, but is related to the new "Set avtivity type" feature in 6.20. I guess the problem is also present for Edge 1000.

Stig

great finding ! i will try it out tonite and let u guys know!