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

EDGE830 New FW 6.0 : problem with Strava routes elevation and climbs

9227533
over 4 years ago

Hi,

My EDGE 830 Firwmare has been updated with FW 6.0 release.

This new firmware brings problem with Strava routes sync through Garmin Connect.

The ride elevation and climbs are completely wrong.

I've done several test and the issue happens on routes sync from strava through Garmin Connect , but it does not show up when i directly download the Strava routes using IQ Strava apps.

it does not affect the routes created on Garmin connect .

anyway facing a similar issue ?

cheers

nicolas

  • 0 over 4 years ago

    to avoid confusion, let me refine the problem:

    1) The route has been created on Strava  to prepare a trip.  So I can see the elevation on Strava route planer .

    2) the route is sync on Garmin Connect and I can see the same elevation . no problem in Garmin Connect  with the route sync from Strava

    then, once downloaded over my Edge830 device ,  the route "summary" gives around 2x the elevation , and the climbs for this route are crazy ( 15%,etc...)

    this problem happens after updgrading FW to 6.00.... 

  • 0 over 4 years ago in reply to 9227533

    I have asked about this several weeks,for edge 1030 no answer, if the route is transfered with strava iq app, then elevation is correct

    For me seems garmin issue

  • 0 over 4 years ago in reply to 9227533

    That happened to me on some routes I had already on my 830.
    I solved it by deleting the courses in the gps and uploading it again!
    Cheers

  • 0 over 4 years ago in reply to 9227533

    It was the case before 6.0 . It is a Garmin Connect bug 

    use Strava app on edge to download routes, no other choice until garmin fix the problem on garmin connect

  • 0 over 4 years ago in reply to Cedricg_38

    I sync routes from strava using Garmin Connect many times ,  the problem occured after updating both the FW to 6.0 and the Map to 2020-10.

    Ok good to know this happens before 6.0 .  I"m now wondering if this is not an issue with the maps ....

    thanks guys !

  • 0 over 4 years ago in reply to filipesalvado

    i created some new routes to try to debug the problem and it was there with brand new routes.... so this is another problem.

    thanks !

  • 0 over 4 years ago

    I've had this too. Definitely before ( and after)  v6.00.

    I'ev created a simple route in Strava that has an elevation gain of about 250m. If I export the GPX then load it onto to my Edge 830 manually, it looks fine. If I create an identical route in Garmin Connect ( web ) and send that to the device, that's fine too.

    However, if I "star" it in Strava, and let it automatically upload, the total elevation in over 500m. The graph of the elevation is more jagged and there are lots of little tiny hills on what are actuall flat roads.

    This is the route...

    https://www.strava.com/routes/2732933762636096534

    Here 's the Garmin Connect created on the device...

    ...and here is the one automatically uploaded direct from Strava



    I'm pretty sure this didn't happen with the old Connect IQ Garmin Routes app, although I can't really test that.

  • 0 over 4 years ago in reply to Chrisba_

    Download the route GPX file from Strava.  Plug the Edge unit into a computer and copy the GPX file in the Garmin\New Files folder on the device.  Now when you use the device the route will be there with the elevation you expect.

  • 0 over 4 years ago in reply to Wongataa

    Many thanks guy,  so looks the problem is not linked to FW6.0  and  the issue reported by  CHRISBA is exactly the behavoir I'm facing.

    I never had such issue before upgarding both Maps and FW , so as this does not seem to be the FW,  likely a compatibility issue with the new MAP i downloaded recently.... I'll give a try disabling the new map.

    cheers

  • 0 over 4 years ago in reply to 9227533

    It's nothing to do with FW or maps. It's a bug in the program running out there in the cloud somewhere that copies the routes from Strava to Garmin Connect. In my example above, the route is already screwed up by the time it arrives in Garmin Connect, before it gets copied to the device.