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

3.97 - ascents still not fix properly.

Former Member over 7 years ago

- Fixed issue where the ascent remaining and ascent to next course point data field values did not match the total ascent for the course.

It took me 1 minute to know that it is still not fixed completely.

Yes, these 2 data field values now match total ascent for the cours, but ascent in cours sent to 1030 now not match ascent data from garmin connect by about 30 % !
Garmin, you repaired one but spoiled the second thing, as a result this 2 data fields still shows incorrect values.

It was repaired 3 months ago, now it does not work again.

aweatherall :
01-31-2018, 09:30 AM
The problem is with what Garmin Connect is sending to the Edge. Let me pass what I have found on to Garmin.

02-02-2018, 09:46 AM
Garmin contacted me and reported the issue is now fixed. I just tried it and it works.
Delete the courses with the wrong elevation data off your Edge and try re-sending them from Garmin Connect.

Garmin.
You create cours in garmin connect, then sent to 1030.
In 1030, in cours summary, ascent-descent data must match ascent-descent data from garmin connect, after 3.97 update it does not work again- you have to fix it.
Then keep what you repaired in 3.97 update- ascent data fields mast match data from cours summary.

Garmin, you are closer, but still not there.

https://forums.garmin.com/forum/into-sports/cycling/edge-1030-aa/1302849-courses-incorrect-height

0 vmojzisek over 7 years ago

-
In 1030, in cours summary, ascent-descent data must match ascent-descent data from garmin connect, /QUOTE]

I am not fully persuaded that it must be true. Both Edge and Connect have its own elevation data concerning your course. So when I prepare my course in any editor like Garmin connect, it shows me ascent - descent data according its elevation data. When I transfer the course to 1030 it counts its ascent-descent data according to the elevation data of its map. This way it works, at least I suppose.

0 aweatherall over 7 years ago

Build 3.97 made a change to recompute the elevation gain/loss using its on-board algorithm rather than accepting the value that maybe passed over. It is using the elevation data supplied in the course file (it does not change that), but it s computing it's own gain/loss value. These new values are then stored in the course file on the Edge and are used to report "Ascent remaining" and "Ascent to next course point".