eTrex 30 - significant differences of "Stopped time" on Trip Computer and Base Camp

Former Member over 11 years ago

Hi,

I get significant differences of "Stopped time" between eTrex 30 Trip Computer and BaseCamp statistics.
By example on 8th of June 2014 I hiked 15,7 km - eTrex 30 Trip Computer said 2:32 hours moving time with 1:31 hours stopped time. When I download the track into BaseCamp I get 3:34 hours moving time and 30 min stopped time, which iI consider is accurate. There is a difference of 1 hour moving time for a total time of 4:04 hours - it seems really a big difference for me!

This is my track and my screen shot:

The same differences are in almost all my hikes:
03 May 2014: trip odometer 13 km, eTrex 30 moving time 2:38/stopped time 3:34, BaseCamp moving time 3:23/stopped time 2:50 - that's almost 45 min difference for a total 6:13 hours hike
25 May 2014: trip odometer 12,8 km, eTrex 30 moving time 2:36/stopped time 4:41, BaseCamp moving time 4:23/stopped time 2:55 - that's almost 2 hours difference for a total 7:18 hours hike
04 June 2014: trip odometer 7,8 km, eTrex 30 moving time 1:36/stopped time 1:19, BaseCamp moving time 2:16/stopped time 0:41 - that's almost 40 min difference for a 2:57 hours hike

All other data are as expected: elevation, odometer, etc but moving time/stopped time are very, very wrong... I'm very disappointed about this errors...

I'm using the latest updates, now I'm on v. 3.80 and I have restored to factory settings several times...

Any suggestion on what to do next?

Thank you,

Luci Hum

0 BTLAAKE over 11 years ago

The gpx file indicates that only the distance value from the trip computer is being sent along with the track. All other values are being recalculated by BaseCamp.

The Trip Computer on most, if not all Garmin devices, updates every second, while the actual logged data will vary based in user settings (yours is one of the auto methods). An interval of 1 sec is good for estimating if the unit is in motion, but it is bad for getting accurate distance. On the other hand, when BaseCamp recalculates stopped/moving times with variable time intervals, it currently does a poor job. You may want to take a look at this thread: https://forums.garmin.com/showthread.php?94637-Track-Distance-Discrepancy-between-Summary-and-Graph

A recalculation of all summary statistics can be forced by deleting a single point from the track. Choose one with a short distance and leg time. For example point 334 in your file. The track distance will drop to 15.5 km.

For accurate distances, settings with the fewest points that closely duplicates the actual shape of the track are best. For accurate Moving/Stopped the trip compute may work fine (I haven't tested it), but I would suggest making a waypoint each time you start and stop if these numbers are really important. Use the timesamps for these waypoints to add notes (stopped/moving time and moving speed) to the track.

0 Former Member over 11 years ago

Thank you BTLAAKE for the valuable information, the thread you suggested was very useful. Like the conversation in the thread, I think that BaseCamp recalculated moving/stopped time is more accurate than the device trip computer.
In my last hike, I was hiking in the woods, walking slowly on a steep hill and I noticed that my Garmin's trip computer was adding time to "stopped time" rather than to "moving time" - I'm pretty sure that the differences of moving/stopped time between eTrex 30 and BaseCamp are generated by such slow movement. It's the only major difference that I get between device and BaseCamp, all other values are about the same (distance, elevation, etc.). It's annoying because I can't analyse during my hike the performance I'm having in terms of speed and walking time...

0 Former Member over 10 years ago

I see the same issue on my Etrex 30 on every walk, the most recent being the worst. As you say, time is being added to stopped time instead of moving time. My last walk was 10.5 hours. At the end of the walk the Trip Computer shows Moving Time 05:21 and Stopped Time 05:09. The same track loaded into BaseCamp shows Moving Time 09:59 and Stopped Time 0:36. BaseCamp is correct but Trip Computer is grossly inaccurate.

0 SUSSAMB over 10 years ago

As this is the Basecamp forum there is little advice that can be given. I run an Extrex 20 and don't see the sort of discrepancies you report. I suggest you contact Product Support for help.