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

Altitude is very incorrect

Hello,

Since v3.30, altitude seems to be incorrect, showing very crazy values, sometimes very high, sometimes negative ones.
After I've factory reseted the device, it appeared to be corrected. But after I performed a walk, with GPS online, it seems that the values got wrong again.
It also seems to be impacting in the floors (stairs) counting).
Could it be another bug?
Regards
Hervandil

Top Replies

Garmin-Blake over 4 years ago +1 verified

Please review this FAQ for information on how the vivoactive 3 series calibrates the altimeter.
Dave S. over 4 years ago in reply to Garmin-Blake +6

This calibration does not work at all. The altimeter (at least on the Vivoactive 3) is complete garbage and does not work, and Garmin just won't admit it. In my case, it is always, always, always, several…
4460897 over 3 years ago in reply to Garmin-Blake +5

Hi Garmin,

This doesn't seem to work for a number of people for the VA3 as shown by this thread. There seems to be an issue with either the device hardware, software or the design of the ports on the underside…
pieras123 over 6 years ago +4

I have the same problem, has anyone contacted Garmin on this yet?

All Replies

0 robertr over 6 years ago

After the update to 3.40 there is the same problem:
When i sit on a chair lift moving up, the altitude is still decreasing for a few minutes. The oher way, skiing down the hill, the altitude is still increaing some time.

The altitude seams to be nothing than a random number.

For this reason unfortunately the VA3 is worthless for me.

0 Leo_HillsideCycling.com over 6 years ago

Same here, here's yesterdays bike commute to work (14th of March) and one from 27th of February (that is correct as you can see on the altitude chart). Exactly the same route - elevation is out of bounds really bad. Support contacted, but no solution yet. But this is 100% software related, so no need to panic...
ciq.forums.garmin.com/.../1322629.png

0 Hervandil over 6 years ago

I've been testing it.
It seems that sometimes it selfadjust.
But, at this right moment, it is telling me that I'm 89 m high (totally wrong).
Regards

0 Ladybug_88 over 6 years ago

I knew I saw something on this. Look at this bike ride. First is mine with the 3 and 2nd is my friend’s with the HR. We rode together and not in the mountains...ciq.forums.garmin.com/.../1323918.png

0 paulgear over 6 years ago

I'm also seeing this. SW Version 3.40 GPS, 4.30, TSC 2.10, Sensor 5.80, WHR 20.03.24, Connect IQ 2.4.1. Here's a graph from my run on the beach this morning. Claimed altitude range -27 to -1 m, but the graph shows flat +51m. (And at a guess, my real altitude change was roughly +5 to -1 m)

0 paulgear over 6 years ago

Here's another run on the beach. I was running within a metre or two of the water's edge virtually the entire time, and ran up a dune towards the end. This altitude data is a lot different from my last run, but not even close to right.

0 Leo_HillsideCycling.com over 6 years ago

Ok, now I have been consulting both Garmin Europe (UK) and Garmin Sweden regarding incorrect barometric altitude readings and floor(stair) counting. Both came to the same conclusion, my VA3 needs to be replaced. My altitude error is not software related.

Kindly enough, Garmin Europe did recommend to sent the VA3 back to the retailer so I could get a new in box replacement since it's only two months old. Otherwise, if you return a device for replacement directly to Garmin you will get a NOH (Newly OverHauled refurbished returned preowned device).

Let's see if the new device will work longer than one month. To be continued...

0 paulgear over 6 years ago

I solved the issue with my VA3's incorrect altitude measurements. TL;DR: disable GLONASS.

I manually calibrated the altimeter on the beach at mid-tide and my next run was still way off (which makes sense, because the altimeter is not used when you're doing an activity with GPS enabled). I then did another two runs on the same beach separated by only a few minutes. One was inaccurate as per my previous graphs, and one was perfect. The difference: turning off GLONASS on the one that worked.

0 klickfisch over 6 years ago

Just disabled GLONASS on the first day - no better results. I think it's another bug. Also tried the beta firmware, same problem with the wrong altitude.

0 cheese8800 over 6 years ago

Well - I always thought, GPS is delivering the Altitude? My altitude - when using GPS - is always correct. Is there a way to show the altitude without using the GPS functionality during an activity?