• State Suggested Answer
  • Locked Locked
  • Replies 14 replies
  • Answers 1 answer
  • Subscribers 4 subscribers
  • Views 4660 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

PacePro available on Garmin Connect

meste7
over 5 years ago

I already see PacePro being available on Garmin Connect, I just played with it for my next race, an ultra marathon and unfortunately PacePro cannot calculate for longer than 15 hours :-( Some sort of limitation, who knows why? memory? etc

  • 0 over 5 years ago in reply to Ed

    Yes I know that I have selected send to device and then sync my watch but pacepro is no where to be found on the watch.

  • 0 over 5 years ago in reply to savvase

    Works fine for me. Sync then start a run/ trail run. Press “up” for options then “training > PacePro”. Select the PacePro activity and you’re good to go.

  • 0 over 5 years ago in reply to TheOtherPhil

    Yes I know the procedure but there is nothing under training ever after I create a pacepro in garmin connect for some strange reason pacepro doesn't sync to the watch. I have removed it from garmin connect reset the watch but still nothing 

  • 0 over 5 years ago

    I do not do ultras (but would like to...), so no 15+ hour events for me. But as I am traveling I decided to test the MARQ Expedition using both a downloaded local route from GCM and add PacePro to that route. It started out nicely, with both tbt indications, correct routing on map, seemingly correct altitude curve and pace indicator. But as I took a slightly different path, and was out of route for a while, tbt was lost and the altitude curve was messed up. This is a bug I have experienced both on the MARQ and on my F5. If you do not use out of route alerts everything works fine. And in this case I did not have any alerts but the turn by turn AND the PacePro. The latter worked nice the entire session, as did navigation and the ETA screen (although a bit slow to re-calculate times as I was off/on route). But altitude and tbt was lost  And these screens/data is really valuable in during trail sessions.

    I will try a few more sessions and see if I can detail both bugs and behaviors a bit better.

    All in all a great set of functions that have a really good use case.