As I interprit it, it is moving time...as in; the time you physically move.
Lets say you do a 20 min run-workout in a city and you spend 5 min stationary waiting for lights to become green...moving time would be 15 min in this scenario
It would seem to be that easy but it's not. What you're describing is the elapsed time, moving time is different but I've yet to see a good explaination of exactly what moving time is.
My Thursday run I paused the watch at a couple of traffic lights and once to get something out of my shoe.
Total time: 54:44
Moving time: 54:27
Elapsed time: 58:20
My Thursday run I paused the watch at a couple of traffic lights and once to get something out of my shoe. Total time: 54:44 Moving time: 54:27 Elapsed time: 58:20
Makes no sense.
Actually, I understand it! (I access to "Elapsed" and "Total" in a Connect IQ app).
-"Elapsed" is the time from when you start recording until you save it. The time keeps running if you are paused or not
-"Total" is the time you are actually recording (it stops when you pause)
-"Moving" isn't available in CIQ and may be something done in Garmin Connect server or something that's not exposed to CIQ. It appears to be the amount of "Total" where you are actually moving. It could use something like a change in GPS location, or non-zero cadence or speed to do this.
So your run was 58:20 from start to end, and 54:44 of that, you were recording, and not paused, but may not actually be moving, and 54:27 of the time you were recording, you where actually moving.
In my long run, Time was 3:18:10, Moving time 3:34:26 and Elapsed time 3:36:47. Of these, only the last one appears to be right. Time for lap 7 (I have auto lap time on) was 6:52,4 and Moving time 6:50, which in view of GPS accuracy may make sense even if I didn't stop but for lap 8 (I stopped for drinking) Time was 7:10,4 and Moving time 11:02, which is difficult to understand.
This is how I understood it from owning Forerunner 305, 610, 620, 630 and now Fenix 3 HR and thinking about getting a 235 because GPS issues with Fenix 3 in trails.
Time is from the time you clicked Start on your watch and proceeded to "run". If you happened to have stopped for a light and it took 5minutes and you were not officially 'moving' the internal accelerometer wasn't being triggered so you were standing still. So 20min Time running, would equal 15minute Moving time and 20minutes of Elapsed time.
* If however, you Stopped the watch (also known as Pause) because you aren't officially stopping the activity, you just want it to Pause for a moment while you are waiting for the 5minute light change, then your Time will be 15min and Moving time should be close to that 15minutes or just under. BUT the Elapsed time will still remain as 20minutes. And if you have Auto Pause enabled, it is technically supposed to pause for you, but doesn't always at least in my case I felt like it was taking too long and so I use the Stop/Pause button.
I noticed lately Garmin Connect is now reporting Moving time even when you paused, (i.e.: I paused watch and wasn't standing still but maybe walked into a bathroom facility and so the accelerometer is still recording this time therefore your moving time now has become in excess of your time and changes your moving pace with it making you feel like a slow poke. i.e.: If I decided within that 5minutes I would use bathroom and then resume even when I did in fact STOP/PAUSE my watch, it picked up my movements and recorded them into my moving pace/time. FAIL GARMIN fix that silliness!
I did ask Garmin about Moving Time and that is computed by GC from your uploaded activity file. It had been using a very sensitive algorithm as it always tended to knock of sometime even when I did not deliberately stop - like a race. Still seems to as got 18:07 moving as against 18:15 Time in a 5K race on Saturday.
It's odd though that moving time seems to be included when you have paused the timer. I just checked a recent run when I did stop the timer briefly and indeed moving time is longer than the stopwatch "Time".
