At the end of a long walk my eTrex 30 Trip Computer shows Moving Time 05:21 and Stopped Time 05:09 but 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.
Have you updated your software? There was apparently an issue with the Etrex 20/30's that caused issues like this. The latest update (4.20) had this in the changelog ◦Fixed several track distance statistic issues. Having said that I never saw any issues on my Etrex 20.
Note also it may depend on how fast you're moving :)
Have you updated your software? There was apparently an issue with the Etrex 20/30's that caused issues like this. The latest update (4.20) had this in the changelog ◦Fixed several track distance statistic issues. Having said that I never saw any issues on my Etrex 20.
Note also it may depend on how fast you're moving :)
Yes it's with version 4.20. I thought the 4.20 fix might actually be the cause of the problem, but someone else reported the exact same problem with eTrex 30 and update 3.80. My speed is around 3.5 mph walking pace. Stopped Time does increase when I stop to climb stiles and gates but that's ok. It seems to work better (perfectly) with the device in my hand compared to in my top shirt pocket. Is that a clue? I would be surprised if there were GPS dropouts though because the device is so sensitive and I was walking in open countryside.
My older eTrex Vista Cx seems to work correctly (side by side on the same walk), but it is much less sensitive than the eTrex 30.
Yes that was hours and minutes. I am training for a 40-mile charity walk on May 9th. That will take about 13 hours - if I finish at all. Then I might stop walking for a year! Wish me luck :-)
Garmin Support suggested a master reset but that did not work. They also suggested deleting all my GPX files but I don't really want to! I can't see how that would help - can you?
Yes that was hours and minutes. I am training for a 40-mile charity walk on May 9th. That will take about 13 hours - if I finish at all. Then I might stop walking for a year! Wish me luck :-)
I agree with SUSSAMB I don't see how that would help. However since Garmin suggested it I would make sure I had them all in BaseCamp and then delete them them from the eTrex. You could always put them back later so there is nothing to lose by trying.
It seems to work better (perfectly) with the device in my hand compared to in my top shirt pocket. Is that a clue?
Yes, this may be a clue. Real-time, devices likely answer the question of stationary or moving by comparing adjacent position solutions. Since these adjacent solutions will almost always indicate movement (i.e. not be identical), a threshold value of distance or speed (these are the same over a 1 sec interval) might be used to determine motion.
The practical problem with this approach is that the accuracy of positions varies with surroundings and availability of WAAS/EGNOS. If Garmin uses this method, they might use a table of values based the estimated positional accuracy to alleviate this issue. If this is the case, placing the device in your pocket could lessen positional accuracy and therefore the determination of movement.
Note that BaseCamp/MapSource would have to use a different procedure for guessing motion since the logged data points may not be at a 1 second interval and the accuracy of a position solution is not recorded in the track log.
You might want to look for a means to clip the device to your belt or perhaps you can find an armband that would work, however, the device’s weight might make this a poor option.
