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

  • Hello, yesterday I ran a marathon in Florence having programmed your app, but I probably did not understand how to adjust the mileage. I have a garmin 235 at 5 km giving me a bigger distance and I then pressed my lap but it just took a new km on the app but did not adjust the distance and then when I pressed the lap button to cancel it took a new km -round. So everything has gone away. What am I wrong?
  • 1/ Lap size: is your lap size set the same in the configuration of Peter's (Hi Vis) Pacer as your autolapsize on your watch? If you auto-lap at 1 mile set the lapsize to 1609, if you auto-lap at 1 kilometer set the lap size to 1000.

    2/ When you press the lap button a new lap will be created by the watch (I don't have control over the creation of new laps), the lap-number itself has no meaning.

    3/ Next to creating a new lap, pressing this lap button can result in 3 scenario's:
    • the multitude of the lap size is less than 1 meter in difference from the current (adjusted) distance (eg 5.001k). An autolap is assumed and no distance correction is executed.
    • the distance is corrected to the nearest multiple of the lapsize. (eg 4.2 k is corrected to 4k - 4.8k is corrected to 5k)
    • lap button was pressed and there was a distance correction in the previous 30 seconds, the previous distance correction is being undone.


    (I wrote the above scenario's in the assumption of a 1000m lap size)
  • Hello Peter/All,

    First let me say that I really enjoy the Hi Vis version of this. I think it's awesome for someone who's colorblind (in that I can't minute amounts of green/red). The large display quickly lets me know how I'm doing. That said, because I can't see color very well, is it too difficult to code/color the whole ahead/behind field red/green (or give the user the option to cycle through it - either on or off)? I ask because as I'm running I'd have to pause my watch, stop, take my sunglasses off, and then carefully study it (obviously, self-defeating if you're really running for time/a race).

    I think having the whole ahead/behind field (versus a small bar of color) indicating the pace might help out more runners more than you might realize. The numbers might be white versus black against the red/green background. If that's possible, I think it would be stellar!

    Thanks,
    Al


    Hi Al,

    Both Peter's (Race) Pacer and Peter's (Hi Vis) Pacer face very tight memory constraints (the hi vis pacer uses 15.6k out of 16k available), I'll have a look, but adding the code for the zone box or complete background might just not fit in in the 400 bytes that are remaining... (I have to code 3-4 layouts per device). (I could also do a new app that has zone boxes instead of background coloring, I might do that, but I'm hesistant to do so as that causes more code maintenance syncing fixes between apps)

    A thing that I've been thinking of adding (and which has a better chance of fitting in the remaining memory and which might also solve your read issue) is to add an option for the color scheme to use.
    At the moment the color scheme used is:
    * red: behind
    * green: ahead < 1 min
    * blue: ahead >= 1 min

    I've been thinking about adding a black and white color scheme. I think this would help both people that are color blind and people that like a less distinct look.
    The colors in the black and white color scheme I'd use would be:
    * black: behind
    * white: ahead < 1 min
    * light gray: ahead >= 1 min (black text font?)

    What do you think?
    Would this black/white color scheme help you? Or would the zoned label boxes work better for you?
    Also which watch do you have?
  • Released v3.4:
    - Added "Black&White" colour theme
    - Added support for FR645
  • Released v3.5:
    - (only for connect iq 2 devices) added option to warn with a vibration and/or beep that your pace is dropping and you are going behind schedule (it only warns when you're going from being ahead schedule to going behind schedule). The option defaults to being off.
  • Warmup phase without calculation?

    As I did my Temporun today I wondered if it would be possible to add a warmup phase to the datafield. Like after pressing the first time the lap button the calculation of behind and ahead time begins.
    Would this be possible? Then you can use the datafield better during training and not only during races...
  • It's possible and there have been similar requests for this functionality in my other pacer apps, but I don't think this belongs in a race app. I would like to keep this application race focused and as simple as possible.
    During races I do warmups too, but I don't want the warmup to be recorded as part of my race effort so I either don't record my warmup mile or when I record it, I record it as a seperate session.
  • Released v3.6:
    - Added speed & pace as options for the big field.
    - Added support for Edge 130 & Edge 520.
  • Hi - think I'm going to make a lot of use of your hi-vis pacer data field but on my 645M I don't have any access to settings from the Connect app on my iPhone. The data field is showing as installed, but tapping on it has no effect. If I use Garmin Express with my watch connected to my Mac I can get to settings but I'd assumed I could change them from my phone as well? Thanks...