Related

GPSMAP 67i Pace Calculations are Off

Sean C
2 months ago

Both the fenix 7X pro and the GPSMAP 67i carried at the same time on two separate test hikes.  In both cases, the GPSMAP 67i Avg Pace calculation is off (short by ~8 minutes on average) and the fenix is pretty much dead on.  Anyone know how the GPSMAP 67i is calculating the average pace?, Or why the GPSMAP 67i average pace calculation is off on Garmin Connect ?

fenix 14-Sep:
Software version 18.14, apps up to date.

gpsmap67i 14-Sep:
Software version 8.50, apps up to date.

fenix 7-Sep:

Software version 17.28, apps up to date.

gpsmap67i 7-Sep:
Software version 8.50, apps up to date.

  • 0 2 months ago

    The pace displayed in Garmin Connect is calculated by Connect, not the GPSMAP.

    If you go into the details are there differences in Time, Moving Time and Elapsed Time between the activities recorded on the watch and the GPSMAP? If those values are different then that could explain the different pace.

    Also check whether you have Auto Pause set to Off or On on the GPSMAP (see Main Menu > Setup > Recording).

  • 0 2 months ago in reply to JungleJim

    Auto Pause is off.

    Time, Moving Time, Elapsed Time are very similar (differences due to starting the watch slightly after the GPSMAP 67i, and stopping the watch slightly before the GPSMAP 67i).

    Timing/Distance

    device distance time moving time elapsed time
    fenix 2.99 mi 1:30:40 1:04:27 1:30:40
    gpsmap 67i 3.00 mi 1:32:29 1:07:37 1:32:30

    Pace/Speed

    device avg pace avg moving pace best pace
    fenix 30:18 /mi 21:32 /mi 12:23 /mi
    gpsmap 67i 21:42 /mi 22:31 /mi 14:17 /mi

    .

    fenix: avg pace = time / distance = 1:30:40 / 2.99 = 30m 19.4s [this matches Garmin Connect]

    gpsmap 67i: avg pace = time / distance = 1:32:29 / 3.00 = 30m 49.7s [does not match Garmin Connect]

    .

    This is a repeatable error for the GPSMAP67i when syncing the activity to Garmin Connect.  The math for the GPSMAP67i does not add up.

  • 0 2 months ago in reply to Sean C

    Interesting, that does indeed looks like something is off. Can you share the FIT files of the recordings on both devices?

    And also a good idea to contact Garmin support to share your findings and have a support case created.

  • 0 2 months ago

    Speculating here. But it sticks in my mind that average pace is not calculated as illustrated here. My recollection (and I have no idea why I think this) is that it is the average of the values for each interval between adjacent track points. In most cases, the two means of calculation yield similar values. But not always.

    IF this is indeed the case, examples involving multiple devices (as here) may exhibit large discrepancies if the two devices have different "recording intervals" between track points.

    Or I could just be hallucinating.

  • 0 2 months ago in reply to twolpert

    It's quite possible.  I've been working with support and will be testing out that theory this weekend on a 14 miler.

    What doesn't make sense with this theory though is that the other average pace (moving) is pretty much correct.  So if it were due to tracking time and distance between individual track segments, BOTH the average pace and average moving pace should be off, or BOTH should be correct, not the mismatched results I am seeing.

    In any case, I'll put up my results after this weekends hike.