If by moving time you mean counting the time you were moving but not counting the time you were stopped, well it doesn't do that, it does total time only. If your time is wrong in being too long, then maybe you have Autotrack turned on, which starts tracking as soon as the device is on; check this setting at Setup >Tracking > Auto Track On | Off. I think in your case you want it Off and then you would start tracking at the moment of your choosing.
Some iR devices do have time moving (and/or time stopped) as well as total time. Depending on the direction of the error (too long vs. too short), this may be due to the way the iR device detects the fact that you have moved from your previously stationary location. It also depends on the sending and (I think) logging intervals. Once the iR device has decided you have stopped, it will not check for a new position (motion) until it's time to record a new point.
My iR is the explorer+, purchased a couple weeks ago. Yes, Auto tracking is/was turned off. When I say moving time, I mean moving time in the trip info. My moving average is wrong too, it is way to high, as in 6 mph while hiking. The only two values on the trip info that look correct are the trip time and trip distance. Thanks for your reply.
What's yor logging interval? At least in Mini the menu is Setup > Tracking > Log Interval [1 s | 30 s | 1 min | 2 min | 5 min | off] . It would be easy to imagine with Twolperts info above that it could be under-recording the time. I know on my watch if I use autopause I have to be careful with the pause threshold because otherwise it will pause while I am walking up a steep hill. Based on this, I'm guessing that if you want these trip report values to be better then reduce the Log Interval, and stop less ;)
Log interval is 1 min.; Send interval is 10 min; Everything else is off. Note, trip length was 8 miles; I stopped three times for short breaks, < 10 mins; once for lunch, <20 minutes; trip time 3hrs 32 min. Simple math says my average speed is about 2.5+ mph, but the trip info shows I'm averaging 6+mph. It looks to me that the only valid trip info data is the trip time and trip distance; What's the difference between the trip distance and the odometer readings?
Everybody, including me, expects the moving average speed to be equal to total distance divided by time moving. But it's not so because that's not the way the device computes it. I do not remember the details (if I ever knew them), but it's more like the average of the speeds over the various individual segments (between points). Particularly if there are segments that were subject to high-speed excursions due to multipath (for example), the number shown on the device will be higher than the "simple math" would indicate.
The thing about multipath is that the device is continually trying to pick the "real" signal from among the echoes. When it changes its mind (whether the newly chosen signal is the real one or an echo), the computed position can shift a relatively large distance virtually "instantly". This results in a very high speed for that segment.
Hurts my head for sure.
Note that this is independent of the issue of what constitutes a "pause", which can contribute to errors in the time moving.
Thanks for you input. It sounds like the moving average datum is not ready for prime time. I will have to work with it a bit more and consider all of you guys' input.
