GPSrChive Discussion Forum

Posted: **Tue May 28, 2024 12:35 am**

Przekątny wrote: Mon May 27, 2024 10:45 pm Last December I covered,
Spoiler
Re: Total Ascent Values Exaggerated by 50% [Bug 29]
that the cause of overestimation of ascents and descents is not incorrect data recording by the device,
the direct reason is an incorrect entry in the statistics sequence created by the device software.

This is correct.

Garmin software engineers need to determine why the statistical information is being recorded incorrectly.

In the mean time, I urge all users, especially those frequently observing these anomalies, to Reset All Trip Data on their devices. This is easily and quickly achieved by opening Setup > Reset > Reset Trip Data > Reset on the GPSMAP 67.

Posted: **Tue May 28, 2024 1:09 pm**

GPSrChive wrote: Tue May 28, 2024 12:35 am In the mean time, I urge all users, especially those frequently observing these anomalies, to Reset All Trip Data on their devices. This is easily and quickly achieved by opening Setup > Reset > Reset Trip Data > Reset on the GPSMAP 67.

Travel data reset can be made on the Recording Controls screen,
each time you should start the discard - Clear, even if there is no current trace in the device's memory
(we remove a track that is not there).

If the default settings have not been changed, the travel data are reset.

Posted: **Sun Jun 02, 2024 5:57 pm**

Version 8.50 seems to work much better for me. The device now reports a total ascent that is within acceptable ranges for me on my usual flat walk. Anyone else seeing better results with 8.50?

Posted: **Sun Jun 02, 2024 8:11 pm**

JungleJim wrote: Sun Jun 02, 2024 5:57 pm Anyone else seeing better results with 8.50?

Today I walked 9.2 km. Ascents/descents were as follows: statistics 83m/83m, while the clean GPS track without statistics 97m/93m. In my case, the result was lowered by approximately 10%. The trip computer showed a result consistent with the statistics.

Posted: **Sun Jun 02, 2024 8:49 pm**

These days I have carried out tests with the Map 66sr and Map 67i devices.

Well, both have the exact same problem: that is, the total ascent and total descent data are added by the barometer.

On the altimeter page I selected the total ascent and descent data fields and I noticed that every time the elevation graph changes, ascent and descent numbers are added.

This if you keep it exposed to the air hanging on the belt.

A 1.5 km route entirely in plane carried out three times, then a total of about 4.5 km, produced on the Map 67i 87m of total ascent and 85m of descent.

On the Map 66sr 89 and 86

On the Map 65s 18 and 19

Then also on the 67i there is the problem of fluctuation when it is stationary.

Before the 8.30 update it was absolutely not like that.

These are my tests done in northern Italy.

I would be very happy if the technicians solved these problems.

Spoiler

In questi giorni ho effettuato delle prove con i dispositivi Map 66sr e Map 67i.
Ebbene entrambi hanno lo stesso identico problema: ovvero i dati di ascesa totale e discesa totale sono addizionati dal barometro.
Nella pagina altimetro ho selezionato i campi dati ascesa e discesa totali e ho notato che ogni qualvolta il grafico di elevazione cambia vengono addizionati numeri di ascesa e discesa.
Questo se lo si tiene esposto all’aria appeso alla cintura.

Un percorso di 1,5 km interamente in piano effettuato tre volte, quindi un totale di circa 4,5 km, ha prodotto sul Map 67i 87m di ascesa totale e 85 di discesa.
Sul Map 66sr 89 e 86
Sul Map 65s 18 e 19

Poi sempre sul 67i c’è il problema della fluttuazione quando è fermo.
Prima dell’aggiornamento 8,30 non era assolutamente così.
Queste sono le mie prove fatte in nord Italia.

Sarei molto contento se i tecnici risolvessero questi problemi.

Posted: **Mon Jun 03, 2024 8:03 am**

Manu wrote: Sun Jun 02, 2024 8:49 pm […]
Before the 8.30 update it was absolutely not like that.

Is your GPSMAP 67i on version 8.30 for the tests you described? If so can you update to 8.50 and see if that improves the reported total ascent value?

For me results on 8.50 seem better, would be nice to know if others are seeing this as well.

Posted: **Mon Jun 03, 2024 8:51 am**

The situation is quite strange, I haven't seen such a problem as others, regardless of the software version. And I travel a lot on quite flat terrain.

Manu wrote: Sun Jun 02, 2024 8:49 pm A 1.5 km route entirely in plane carried out three times, then a total of about 4.5 km, produced on the Map 67i 87m of total ascent and 85m of descent.

On the Map 66sr 89 and 86

If two devices register the same discrepancy, the problem may be in the location itself.

Posted: **Mon Jul 22, 2024 7:01 pm**

Quick comparison, old and new firmware Ascent/Descent as recorded at the end of the trip:

2024-02-10 (firmware 7.60)

Ascent/Descent 558/651 m

2024-02-10 558.bmp

Ascent/Descent 449/450 m

2024-02-10 588.bmp

from trip computer:
558/651m <- huge difference!
from track (as shown at save activity screen):
449/450m
calculated by geojava Track Analyser:
445/439 m

2024-07-20 (firmware 8.50)
from trip computer:
515/506m
from track:
515/505m <- almost the same!
calculated by geojava Track Analyser (filtered):
503/496m
calculated by geojava Track Analyser (not filtered):
527/518m

I think it's ok with current firmware.

Posted: **Tue Jul 23, 2024 7:43 pm**

Thank you for the update!!

Would like to see a few more positive reviews before marking this one as resolved.

Posted: **Tue Jul 23, 2024 7:47 pm**

GPSrChive wrote: Tue Jul 23, 2024 7:43 pm Would like to see a few more positive reviews before marking this one as resolved.

8.50 seems to work much better for me as well. Don’t have the actual data at hand but the reported ascent/descent values for my usual flat walk are much closer to what is to be expected.