Wrong total distance for activities longer than 167.76 km [Bug 10]

[javawa]

Oregon 650 T ma taką możliwość.

My Oregon 600 (apart from the camera exactly the same as the 650) has the option to store it as GPX, as FIT or both. Nothing can be set regarding to the statistics.

The limitation to 167 km has no logical justification, in the activity 2024-09-14 08.32.29.fit 167 kilometer falls on the 4478th track point.
From the information provided so far it is not possible to draw a conclusion as to why there is a limitation, if the activity is saved until the memory is full.

Using a 24 bits unsigned integer for the cumulate distance could be a logical justification...

[Przekątny]

My Oregon 600 (apart from the camera exactly the same as the 650) has the option to store it as GPX, as FIT or both. Nothing can be set regarding to the statistics.

Option is the result of the translation should be (possibility).

[gps_techie]

Using a 24 bits unsigned integer for the cumulate distance could be a logical justification...

Or calculating distance increment in 24 bit (2^24/100) and during addition somehow converting accumulated distance to the same number format. This is speculation, of course.

It is strange it took so long to notice this distance bug in eTrex SE SW 4.20

[Przekątny]

....file because the eTrex SE doesn't seem to support saving activities as GPX file)...

Etrex SE saves current activity to a fit file, that's for sure.

Does it support gpx files without processing to a fit file -it should support it,

a matter to be checked in the device.

[Przekątny]

Not only BaseCamp, Connect uses the statistics too.

In my opinion Base Camp is still the only application that reads the statistics contained
in the gpx file created by the device.

A manually added gpx file to Garmin Connect loses the statistics contained in the file.

[javawa]

Does it really matter? The eTrex SE stores activities as FIT files, and Connect uses those files. What happens with derived files in GPX format is not relevant.
Actually, the problem isn't related to any file format. AFAIK uint24 is never used in FIT files and GPX isn't a binary format. The bug is almost certainly caused by a counter or field in the internal memory of the device.

[Przekątny]

Whether Base Camp is the only application that reads the statistics created on the device and contained in the gpx file is irrelevant It is important to be able to check the correct registration of data while active.

The entry in the statistics regarding the distance, regardless of the cause, is incorrect, resulting in an underestimation of the total distance, despite the correct registration of activity data in the fit file.

[Sibstr]

You're right that we don't know how Sibstr uploaded his activities to Connect. I assumed via Express or Connect mobile app (which I think would result in a FIT file because the eTrex SE doesn't seem to support saving activities as GPX file), but he may have done it manually. So I hope he still reads this topic and can provide us with the answer!

Activities are uploaded automatically via Bluetooth and the Garmin Connect app on my Android phone.

Clarification: eTrex SE shows the wrong distance during the activity before saving. Up to a distance of 176.77 Km it shows the distance correctly, then the km count stops and the next km is not added on the display. So I have never seen more than 176.77 Km on the eTrex SE display in any situation, current or saved.

The .fit files that I shared here on the forum are downloaded directly from the eTrex SE via USB and packaged in a .zip file, they are the original files directly from the eTrex SE.

[gps_techie]

I recorded >200km activity with eTrex SE (FW 4.20), this time I saw distance measurement to stop increasing after 167.72km. Data view screen becomes very confusing after that - eTrex SE shows partly misleading data (distance is capped at ~167km while other fields like time traveled, speed, etc. are correct and changing). Wrong distance estimate can lead to serious errors (e.g., in mileage calculation) or imply that eTrex SE did not record some data points along the route (while in fact it recorded everything, only distance measurement is wrong).

Are there any updates on FW release to fix this bug?

[skinnie]

I recorded >200km activity with eTrex SE (FW 4.20), this time I saw distance measurement to stop increasing after 167.72km. Data view screen becomes very confusing after that - eTrex SE shows partly misleading data (distance is capped at ~167km while other fields like time traveled, speed, etc. are correct and changing). Wrong distance estimate can lead to serious errors (e.g., in mileage calculation) or imply that eTrex SE did not record some data points along the route (while in fact it recorded everything, only distance measurement is wrong).

Are there any updates on FW release to fix this bug?

Guess only garmin could tell.Have you contacted their support?