GPSrChive Discussion Forum

Hi all, I have seen a few references on here to incorrect Ascent figures on GPSmap66 and I have raised this issue with Garmin support. I raised the issue with Garmin in November 2018 and despite sending them a large number of files have had no resolution - it has been a frustrating round of me repeating myself and them missing the point and offering me no help or advice whatsoever.
I am aware that GPS units will never be 100% accurate and I am not expecting that. I have read the tutorial on GPS visualizer https://www.gpsvisualizer.com/tutorials ... _gain.html and so am aware of pitfalls with elevation gain. However, with GPS and barometric altimeter on board, I was expecting it to be better than consistently giving figures that are about double what I expect.
I record both fit and gpx files and notice that in Garmin Connect these two files give widely different figures; the gpx file being close to expected, the fit being double or greater and matching figures displayed on the unit - with elevation correction disabled in Connect. When I have raised this with Garmin I am told that Connect is not best placed to view gpx files and if I used Basecamp I would see that they both give the same figure - the higher figure, ie the incorrect one. They have never acknowledged that the figure is incorrect nor offered any help or advice on the topic.
After months of banging my head against a wall with Garmin support and getting precisely nowhere I am now at a point of giving up and just living with it. However, does anyone have any further insight into this? Are figures consistently double the expected the best I can expect? Can i do something different with my unit to alleviate it?

Thanks.

Garmin software engineers are aware of the Elevation data discrepancies, but they do not provide timetables for when fixes may be implemented. Like the rest of us, you'll just have to wait for the next firmware update and test again to see what has been resolved...

gpsrchive wrote: ↑Wed Jun 12, 2019 12:44 pm Garmin software engineers are aware of the Elevation data discrepancies, but they do not provide timetables for when fixes may be implemented. Like the rest of us, you'll just have to wait for the next firmware update and test again to see what has been resolved...

Garmin have never acknowledged to me that there is a problem. In fact they seem to be going out of their way to say there isn't a problem...

pedigree1 wrote: ↑Wed Jun 12, 2019 1:07 pm

gpsrchive wrote: ↑Wed Jun 12, 2019 12:44 pm Garmin software engineers are aware of the Elevation data discrepancies, but they do not provide timetables for when fixes may be implemented. Like the rest of us, you'll just have to wait for the next firmware update and test again to see what has been resolved...

Garmin have never acknowledged to me that there is a problem. In fact they seem to be going out of their way to say there isn't a problem...

You are not speaking to software engineers, you are speaking with customer support specialists.

gpsrchive wrote: ↑Wed Jun 12, 2019 1:39 pm

pedigree1 wrote: ↑Wed Jun 12, 2019 1:07 pm

gpsrchive wrote: ↑Wed Jun 12, 2019 12:44 pm Garmin software engineers are aware of the Elevation data discrepancies, but they do not provide timetables for when fixes may be implemented. Like the rest of us, you'll just have to wait for the next firmware update and test again to see what has been resolved...

Garmin have never acknowledged to me that there is a problem. In fact they seem to be going out of their way to say there isn't a problem...

You are not speaking to software engineers, you are speaking with customer support specialists.

So you have spoken with the software engineers?

pedigree1 wrote: ↑Wed Jun 12, 2019 1:44 pm

gpsrchive wrote: ↑Wed Jun 12, 2019 1:39 pm

pedigree1 wrote: ↑Wed Jun 12, 2019 1:07 pm

Garmin have never acknowledged to me that there is a problem. In fact they seem to be going out of their way to say there isn't a problem...

You are not speaking to software engineers, you are speaking with customer support specialists.

So you have spoken with the software engineers?

We know some people at Garmin.

Thanks, that's useful.
My support guy at Garmin is now saying that I should not carry the unit in a pocket as that can affect the barometer. However, he also says that the barometer "works through a small hole on the device - under the battery cover". If that is so, the battery cover is sealed so I fail to see how my pocket fabric obstructs it any more than the battery cover itself. Any views on that?

pedigree1 wrote: ↑Wed Jun 12, 2019 2:36 pm Thanks, that's useful.
My support guy at Garmin is now saying that I should not carry the unit in a pocket as that can affect the barometer. However, he also says that the barometer "works through a small hole on the device - under the battery cover". If that is so, the battery cover is sealed so I fail to see how my pocket fabric obstructs it any more than the battery cover itself. Any views on that?

The tiny hole for the barometer pressure sensor is not located under the sealed portion of the battery cover.

gpsrchive wrote: ↑Wed Jun 12, 2019 2:42 pm

pedigree1 wrote: ↑Wed Jun 12, 2019 2:36 pm Thanks, that's useful.
My support guy at Garmin is now saying that I should not carry the unit in a pocket as that can affect the barometer. However, he also says that the barometer "works through a small hole on the device - under the battery cover". If that is so, the battery cover is sealed so I fail to see how my pocket fabric obstructs it any more than the battery cover itself. Any views on that?

The tiny hole for the barometer pressure sensor is not located under the sealed portion of the battery cover.

Would you be able to tell me where it is? And does carrying the unit in a pocket affect the barometer significantly?

You can see it near the bayonet locking mechanism after you remove the battery cover.

When storing the GPSr in a clothing pocket that is not sealed from the atmosphere, I can not imagine it having any affect on the barometer.

This is the first time I have heard this theory, and would have to test it independently....