Total ascent variation Garmin Fenix 5X and Edge 1000

[Jehosefat]

I guess regression testing (or BETA testing) is not important

 

I think they just treat their users as beta testers 

[eibmoZ]

Maybe update to the latest beta firmware and see if things improve https://www8.garmin.com/support/download_details.jsp?id=11665

 

Update 9.53 has improved GPS,

• Added GPS + GALILEO support (Activity Settings > GPS). (Requires GPS version 2.20)

I have the F5 and Edge520 and both are fairly close to one another.

Nope, tried the beta... same

 

 

Sent from my iPhone using Tapatalk

[pedal menace]

Pedal Menace - would you trust the BETA version to be okay?

In general I would say ..NO. Wait for the final version. Problem is that the elevation issue has been around for a while now and complaints are all over the web. This weekend is TransBaviaans and there is a good chance my Edge 520 won't last the race. I am pretty sure my Forerunner 935 will have ample oomph left at the end. It is a brilliant brilliant watch! Thus would like to record on the watch..and have my elevation at least somewhat accurate. I have owned the Fenix and the Forerunner is just so much easier to ride with on your arm when you are doing some bumpy offroad ride. 

[dave303e]

when last did you calibrate the altimeter?

[pedal menace]

I think they just treat their users as beta testers 

 

Now that I agree with....I am in IT and would love to spend a few days with them just to see how they can mess up releases so badly so quickly. There is little to no quality testing in my opinion. 

[Cookie88]

In general I would say ..NO. Wait for the final version. Problem is that the elevation issue has been around for a while now and complaints are all over the web. This weekend is TransBaviaans and there is a good chance my Edge 520 won't last the race. I am pretty sure my Forerunner 935 will have ample oomph left at the end. It is a brilliant brilliant watch! Thus would like to record on the watch..and have my elevation at least somewhat accurate. I have owned the Fenix and the Forerunner is just so much easier to ride with on your arm when you are doing some bumpy offroad ride. 

 

I think I will wait for the final version and bide my time... As a side note  I did TB last year and took around 14 hours. With GPS Only, Bluetooth turned off and the brightness turned right down I made it with some oomf still left in my Edge 520 so you should be okay 

[pedal menace]

when last did you calibrate the altimeter?

Been there done that...as per the Garmin forums everyone tried this to no avail. Elevation on teh watch differs significantly from the Edge bike computers. Hopefully the last fix (9.73 or 9.75) will fix this. Would prefer to get an official release but due to circumstances will for once consider the BETA release

[Cookie88]

Nope, tried the beta... same

 

 

Sent from my iPhone using Tapatalk

Doesn't look like the Beta Version for the 5X includes anything about fixing Total Ascent values 

[pedal menace]

I think I will wait for the final version and bide my time... As a side note  I did TB last year and took around 14 hours. With GPS Only, Bluetooth turned off and the brightness turned right down I made it with some oomf still left in my Edge 520 so you should be okay 

Exactly how I plan to set up the Edge. And hope it lasts (at least I am aiming for 12-13hrs :-))...if the weather allows. 

[Cookie88]

Exactly how I plan to set up the Edge. And hope it lasts (at least I am aiming for 12-13hrs :-))...if the weather allows.

All the best out there and enjoy!

[Cookie88]

Updated software this last weekend and keen to try it out tomorrow - anyone had a go yet?

[JCVenter]

Same issue....used Edge 520 with Fenix 5 (2017), worked perfect. Then Fenix decided time to retire...

I now have the same Edge 520 (still close enough) but the new Fenix 5S Plus is all over the place, mostly lower. Did the reset, calibration, stopped Galileo and now going to try only Glonass. So far now success....will aslo switch off auto-calibration during the ride.

 

Let’s see if new software will resolve this issue.

[Jehosefat]

Rode suikerbossie yesterday with the updated software on my 935. Was much closer to the 820 than the last few rides. (The 820 had 1502m and the 935 had 1445)

 

That's for the full loop plus once round the short loop so both are in the range I expected.

[Jehosefat]

Same issue....used Edge 520 with Fenix 5 (2017), worked perfect. Then Fenix decided time to retire...

I now have the same Edge 520 (still close enough) but the new Fenix 5S Plus is all over the place, mostly lower. Did the reset, calibration, stopped Galileo and now going to try only Glonass. So far now success....will aslo switch off auto-calibration during the ride.

 

Let’s see if new software will resolve this issue.

 

None of those units use the GPS/GLONASS for elevation data so changing that should not have made any difference. They all use barometric pressure to measure altitude changes.

[Jaws677]

I didn’t read the entire thread but there was a problem with one of the firmware updates on the 5X causing this issue

Latest firmware fixes this

[LBKloppers]

Fenix 5 uses barometric sensor for altitude changes and not satellites so GLONASS on or off shouldn't make a difference to elevation. Not sure about the 1000 but the 520, 820 and 1030 are the same.

Some years ago I purchased an Edge 500 to log and record my rides in the south of Madagascar. The Edge 500 also reads elevation using the barometric sensor and at the time the accuracy of this sensor was a selling point. Due to the nature of the routes I rode and the duration of my rides, I often ended up riding under the sea!! I took the matter up with Garmin at the time and the short end of the story is that for devices like Garmin that is available to the general public, an error is deliberately programmed. GPS belongs to the USA air force and Glonass to the Russian equivalent and thus have military applications as the primary objective. With the military paranoia it is very likely the reason for your errors. Just ask prof Google and read up a little towards the actual workings of GPS. Only three satellites above the horizon is necessary to plot your position in a three dimensional orientation. Using the barometric is a way to sensitize the unit to the small variations you may encounter on your ride, but changing weather conditions and changing wind directions influence this sensor. Your errors are typical by the location and orientation of each device when one measurement is made on the wrist and the other on the bike. I disagree with the statement that barometric is better than GPS, but unless you have the unblocking authority from the USA air force, the error is most likely to remain. At least enough of an error so you can not use the devise for undesirable actions.