Data Field: Peter's (Hi Vis) Pacer

Description
Peter's (Hi Vis) Pacer helps you to ride/run the perfect race.
This is a spinoff project from Peter's (Race) Pacer, while it has many similarities it took me a while to create as it's a completely seperate code base.
It's different in the following ways:
  • high visibility less data is shown on the screen, which means that it is easier to read - eg for people with bad eye sight.
  • it can be used in non-single field mode, this means you can put it on the same page with other datafields of your choice!
  • It's also optimized to run on Edge devices, this means you can just as well use this field to pace your bike races just as your running races....
Adjusting the race distance
In a race when you are next to the race marker press the LAP button, the distance will now be corrected to the nearest lap position - eg 5.08 will correct to 5, 8.8 will correct to 9. After pressing the lap button the distance will be adjusted and all averages will be recalculated against this new distance figure.
When you miss a lap marker do not worry: do not press LAP and go for the next lap marker.
When you press the LAP marker by mistake you can undo the (last) correction by pressing the LAP button again - within a 30 second window

Donations
The data field is fully functional as is, yet donations are encouraged on the watch by an encouragement text.

Download
Download link: https://apps.garmin.com/en-US/apps/5...4-e3afdd10eddf
  • There are no other colors :)

    Red = behind schedule
    Green = ahea​​​​​​d
    Blue = ahead by more than 1 minute
  • Tried the Hi Vis Pacer in Berlin yesterday. Worked perfectly! Too bad my legs did not...
  • Hi posting again after my "app review". Thank you for your quick reply and instructions for posting on the forum! I had already installed the data field on my watch; however although I had selected the hi vis pacer data field and a single data field display my watch shows a timer, not the hi vis pacer. I think I had this trouble with a different data field I found on the connect store . I ended up giving up on that. So maybe this is more an issue with my vivoactive than your app. I will try uninstalling and reinstalling to see if that helps.
  • ok, in case it doesn't work, one thing you can try additionaly is to factory reset your watch (be sure that all your activities are synced before you do as this action will wipe all activities from your device)
  • Thank you for the great datafield.

    It worked very well during my marathon today. At first I had some time behind because of an intended slow start. After that I could make up a bit and finally I accumulated some behind time again. ;)

    But very accurate pacing is possible indeed! I didn't use autolap and of course I was missing the first km-sign.... And several others..... :)
  • You're welcome, the more marathons you'll do with the data field, the more you'll trust it and the more accurate you'll be able to pace yourself next time,... but a marathon is always unpredictable (that's part of the fun right?). I also had a though last 10k on the marathon past sunday (even though I was running it at a slow pace for me), I still brought the group within the requested time at the finish line, but I had to push myself a lot harder than I liked :)

  • Released v3.2:
    - Added HR% (for connect iq 2 devices)
    - Round pace instead of truncating the pace value
    - When speed smaller or equal to 1.0 show the pace as 0:00
    - Vivoactive HR: fix positioning and field size in 2 field display mode
  • - Added HR% (for connect iq 2 devices)


    Thank you! Will donate... :)
  • Peter:

    As requested, posting additional info on my issue with the Hi-Vis datafield when used as the second screen with the Pacer datafield. Attaching screenshots showing the time/distance and configured settings on the device when the problem was observed. These show the Pacer and Hi-Vis datafields, snapshotted back-to-back at the conclusion, along with the configuration settings of the two datafields, and the system settings.

    Device is a Forerunner 235community.garmin.com/.../1262508.jpg
  • Hi Ken,

    You've configured the target type to be Target Finish Time, to fix change the target type to be target pace (or alternatively you could also fix it by specifying your expected finish time on the half marathon)