Data field: Yet Another Runfield - YARF

Hi,

I just created a runfield (called currently YARF) which packs 12 datafields into one garmin datafield. Currently the project is in an alpha state and things are well hard coded. I haven't tried it yet on my physical 235 but simulated it with a real FIT file from my last run.



I coded some special data fields which are not built into garmin's API:
- A 15 seconds pace which is the average pace of the last 15 seconds.
- A lap pace. Unfortunately, Garmin does not support a native lap pace, therefore we have to calculate it on it's own. The datafield assumes a lap of 1 km (maybe I will make this customizable in the future). The datafield can't detect natively when a new lap begins. Therefore the lap pace is not convenient for interval trainings. Furthermore the lap pace is equal to the 15 seconds pace the first 15 seconds of a lap which shall smooth the lap pace at the beginning of a lap.

What do you think? Any improvement suggestions to the layout?

You can find the final version of the datafield here: https://apps.garmin.com/en-US/apps/46016194-1fdf-4f9b-ae8b-16ceba51a548
  • Almost perfect

    I am using this data field like my unique data screen. The metrics are great, it is a very good idea to show several data pace to see the progress detailed in few seconds, minute, lap and average.
    This screen has been designed for a real runner, thanks for your effort.
    The empty field I think maybe be used with the total ascent meters to complete the usual fields of a runner.
    It would be nice to change the limits of HR and cadence.
    Thank you again.
  • Hi nitemolestes,

    thanks for your suggestion with the ascent meter. Do you own a 735XT? This is the only device which owns a barometer. The other devices YARF is compatible to rely on GPS information and this is not very accurate. Therefore I am not sure whether I shall show this information. My ideas for that empty space are:

    - Showing estimated finisher timer for the next milestones (5k, 10k, 21k) but this information is only relevant for a competition. My idea is to design further datafields for a competition as well as one for interval training.
    - Showing a pace histogram of the last 10 seconds
    - Showing information icons like bluetooth, GPS strength, Audio muted
    - Showing the current heart rate zone
    - Showing a heart rate zone histogram

    If I walk through that list, the most useful information for a typical training run is probably the pace histogram. But we can discuss things.

    BTW, to your request: "It would be nice to change the limits of HR and cadence.".

    I don't understand what you mean with limits of HR. Can you explain it a bit more?
    Do you mean the limit of cadence as it is shown in red? This is very easy to implement and easy to make it configurable. I can integrate this in the next version.
    BTW: Do the YARF settings from Garmin Express or via mobile connect work for you? Can you give me some feedback?
  • grade and ascent

    hi again, a have a 235, no barometer, but I am using several fields from garmin icq with ascent and grade. I can not say if they work or no till I use it several days. at least and arrow or a color who indicate if you are ascending or descending is another idea.
    It is impressive how well works the data field you made.
    I use the mobile site.
    the opcion you have mentioned I prefer gps strenght, or race predictor for 10k.
    more ideas? tempe field, pace from footpod, or even better, a ghost pace who tells you the distance or seconds from a selectec target pace, in red and green depending the positive or negative values
    With the new version, 0,5, I can only change the cadence limit from the phone.
  • Good to hear that you find the data field useful. Before I can implement information to the empty space I have to clean up the code basis a bit and have to compile it with the newest connect iq SDK which was released some days ago.

    Unfortunately there is still no native support for laps which makes it difficult to design a datafield for intervals.

    Nevertheless, do the newest two configurations both work for you? I tested it in the simulation environment but as soon as I download YARF from the store both configurations have no effect.
  • Good news: With the new SDK which was released some days ago, we got native lap support. This means, whenever a new lap happened (automatically or manually), we know when the lap happened and can write some code around it. In fact for YARF it means, that the silly 1000 m split can be removed by do some coding around the lap event. This will be in the next version of YARF. Furthermore I will add a configuration for the ToD color. I was out running today and realized that the minutes of the date time were hard to read since it has all the same color.

    In an upcoming version I will add following information in the empty space: last laps average pace, average HR and average average cadence.

    BTW: With the new native lap support I will design a new data field only for interval training. The data field will contain following information:
    1st Row: Lap Average Cadence (which switches to last Lap Cadence during the recovery time), Cadence
    2nd Row: Elapsed Time, Lap distance (which swichtes to total distance during the recovery time or during warm up/cool down)
    3rd Row: Lap Pace, 60 Sec Pace, 10 Sec Pace
    4th Row: ToD, Calories burned, maybe a toggling information about the last interval laps
    5th Row: Lap Average HR, HR

    Now I only need some time to code this :-(
  • interval field

    good to know you are working in an interval data field. Half of my trainings are interval work.
    no necesary to know calories or TOD, battery... when you run hard in the interval. You need paces with colors that indicates tendency to see easily.
    distance, meters to go in the serie, and a simple HR field and cadence is all I need in a fast serie, with big numbers and colors helping.
    could you say me the way to donate?
  • Former Member
    Former Member over 8 years ago
    Please make this available for fenix3 & Fenix 3hr.

    I can beta test if you want.
  • Currently I clean up the code basis and rewrite some algorithms to improve performance and accuracy of the datafield. Furthermore I have to fix some bugs (e. g. fix the beep and the vibration if watch is stopped). After this I can see what I can do for you.
  • Great

    Now I see the empty field has been filled with lap time and last lap time. Good idea but difficult to read in the road. Maybe with only an intermittent value who changes every 2 seconds it would be easier to see