Data Field: Peter's (Race) Pacer

This is the support Thread for the Data Field Peter's (Race) Pacer.

Setup Guide with pictures: http://starttorun.info/peters-race-pacer/

Download
https://apps.garmin.com/en-US/apps/23ea0301-30c6-4c33-b4ef-63e2b5394e76

Summary
Peter's (Race) Pacer resolves 2 issues for me when I'm running a race:
  • Before the race starts I want to see the time of the day (How long till the race starts?)
  • I often pace marathons and it used to be doing mental math all the way, now this is no longer necessary as I can fully depend on the average pace/speed, because this data field allows to correct the distance at the kilometer / mile marker by simply pressing the LAP button
While the data field's primary intent is to race races, you can also use it to run laps around the track, just set the lap distance to 400 meters and press the lap button as you cross the line!...

Intro
In it's full glory this data field uses about 24kb which is too much to run on the older devices. To enable using the data field on older connect IQ devices I've stripped some functionality from these older watches in order to let them operate within the 16kb limit that Connect IQ 1.x allows. (Items marked with (*ciQ2) are only available on the high memory watches (high memory watches are FR735xt, fenix chronos & fenix5 variants))

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

Usage
Before starting the race an initial data screen is shown (* cIQ2), this screen shows you the following data
  • Time of the day
  • Current heart rate (+ zone indication)
  • Configured Settings Summary (Change these settings in Garmin Express or in the Garmin Connect Android App)
  • Battery Percentage Remaining
  • Gps Signal Strength Indication
After pressing the START button the race timer will start and a new data screen will be shown, this data screen will show you the following information:
  • top middle configurable field: current heart rate / average pace / average speed / perfect pace / perfect speed (*)
  • row 1 left configurable field: average pace / average speed / current heart rate / perfect pace / perfect speed
  • row 1 middle configurable field: speed, smooth speed (5s average), smooth speed (10s average), pace, smooth pace (5s average), smooth pace (10s average)
  • time ahead / behind
  • race timer
  • (adjusted) distance covered (see adjusting distance explanation below)
  • estimated time of arrival
After Activity in Garmin Connect (*cIQ2)
  • When you opt to record the ahead Time to the FIT track an extra graphic is shown in Garmin Connect
Perfect Pace / Perfect Speed
This field recalculates as you run and gives you the pace you need to run to arrive at the finish with 0 seconds behind / ahead (eg if you run a 10k race and want to arrive in 1 hour (avg pace=6:00min/km), currently you're at the 7k point in 41:30, which means you're 30 seconds ahead, the perfect pace will thus show the value 6:10 (min/km) as you can run the next 3k 10 seconds slower to still get in time at the finish line)

Distance Adjustment
When you press the LAP button the on screen distance is adjusted to the nearest LAP SIZE (eg 5.31k will be adjusted to 5k if the lap size is 1000 meters).
When you press the LAP button by mistake you have 30 seconds to undo the last correction (just press the LAP button again)

When you miss a mile/kilometer marker, don't worry DO NOT PRESS THE LAP button and wait for the next kilometer/mile marker and press the LAP button there.

Adjusting the distance has no influence on the recorded distance (In Garmin Connect when you come back home you will see the real recorded GPS distance, yet of course you will be able to determine based on the lap marker postions where the LAP markings really were)...

Recommendations
  • Train with the data field before you race with it so you're used to the layout!
  • Have a backup second datascreen layout, in case the field crashes you can switch to the native data screen layout
  • If you have a Connect IQ 1.x device consider the application option to enjoy all features of Peter's (Race) Pacer: https://apps.garmin.com/en-US/apps/ea97af1f-1e5d-4541-820c-9bd994080d4
Tested on real FR735XT, all other devices were tested in the simulator.
  • The fenix 3 hr is a connect iq version 1 device, this means that the fenix 3 hr has only 16kb of memory in datafield modus which is not sufficient to load the complete program. This means I have to remove some functionaltity to be able to let it load on the fenix 3 hr device

    what this means specifically for this program:

    The app version:
    * has all the functionality of Peter's (Race) Pacer also on the fenix3hr
    * as it is an app you can not use another ciq field and/or native functionality at the same time

    The datafield version:
    * you can use Peter's (Race) Pacer in combination with another connect iq datafield and/or native functionality.
    * the core functionality is present but all functionality marked with ciq2 in the description is not available (no fit recording, no initial data screen, no lap speed)
  • Released version 3.5.3:
    * small fix for vivoactive: removed labels from top row to improve the readability of the screen
  • The app version:
    * has all the functionality of Peter's (Race) Pacer also on the fenix3hr
    * as it is an app you can not use another ciq field and/or native functionality at the same time


    Thanks for your response!

    If I have yours I wouldn't need another ciq field, so that's fine, but what kind of "native functionality" would be lost?

    Sorry for the hassle :)
  • If I have yours I wouldn't need another ciq field, so that's fine, but what kind of "native functionality" would be lost?

    you have to choose from the fields that I have made available (heart rate, speed, pace, etc...) in the program which is only a subset from all options you have in native mode (eg in datafield mode you could set up a second screen which shows calories etc...),...

    ...but normally that shouldn't be a problem as the fields which are important to racing are available inside Peter's Pacer (The App).

  • Feature Request

    Hi Peter,
    I've played with the data field and run a couple of races with it - very impressed with how well it works (on F3)! The only thing that is really stopping me from using it more (and donating) is that the screen has too much detail for my old eyes! During a race the only thing I really want on the one screen is whether I am behind or ahead (in large font), and (smaller) distance & time. I can always add screens with other data fields but I really prefer a simple, easy to read 'at a glance' screen. An example is the "Race Pacer" (I don't actually use this) where they offer a very 'busy' version and a minimal version.
    Just something to consider
    - other than that really great job with the data field and how well it works.


    Feature Request fulfilled :)
    Yet another Race Pacer is now available under the name Peter's Ahead Timer : https://forums.garmin.com/forum/developers/connect-iq/connect-iq-showcase/1232453-peter-s-ahead-timer
  • As this was partially based on my feature request - THANKS. I can't use it until it is 5x comnpatible (I upgraded) but hopefully this is in the works.
  • Sure it should be there in the coming days. Keep an eye on the other thread ;)

    2) This was the longest run I'd done, and yet the achievements on my watch did not record the run as such. Can records (fast/longest etc) done whilst using the app be recorded to the watch's achievement memory?


    I have filed a bug report here: https://forums.garmin.com/forum/developers/connect-iq/connect-iq-bug-reports/1232812-watch-app-does-not-create-update-records
  • Any chance to include power in one of the fields?
  • It's been on my todo list for a few months to add power (and I even started implementing parts of it, but some things got in between).
    I'll increase the priority in my todo list to put it back a bit higher on my list to finish this implementation. :)
  • Released Peter's (Race) Pacer v4.0:
    * Reviewed/improved memory consumption
    * Reimplementation of all the configurable fields
    - BREAKING CHANGE: top/left/middle field can now all contain any of the 12 optional fields.
    - field fonts will now dynamically adapt depending on the size of the field contents.

    IMPORTANT:
    * BREAKING CHANGE - the internal numbering of the configurable fields no longer matches with previous pacer versions so you will have to review your configured settings!

    * If in the options you do not see at least 12 options (like in the below screen shot) in the top left configurable field, if you see less options remove and reinstall the data field.



    Feedback:
    The code changes for this release were pretty high impact.
    Attempts have been made to limit user impact:
    - All business logic has been verified by my set of unit tests.
    - All visual changes have been verified in the simulator

    But potentially I missed something and/or the real device might show/act differently than the simulator.
    If you notice anything that's off please take a picture and post it in this thread. ​​​​​​​