Data field: Visual Pace Alarm

Former Member
Former Member
The Visual Pace Alarm data field is a visual aid to help you keep your pace. Visual Pace Alarm shows your current pace and uses a gauge or a background color, depending on the size of the field in which it's placed, to show you how close you are to the pace you've set.

You can find the data field here.

*********** Features ***********
  • You can set it to show your current pace or the average pace over a set number of seconds;
  • Pace gauge, if displayed on full screen (fr920xt / epix) or at least upper half screen (all (semi-)round devices);
  • Pace zone as a background color for all other sizes;
  • Allows you to set target pace and allowed offset to that pace. Offset in both directions is split into 5 zones, that are color coded Yellow, Blue, Green, Orange and Red.
  • Pace gauge view flashes background on leaving target pace zone.


*********** Requirements ***********
Connect IQ version 1.2 or above

*********** Version history ***********
v1.0: Initial version

*********** App Settings ***********
General information about app settings can be found here.

The settings:
  • Target Pace: the pace you want to keep
  • Number of seconds to outer limit: the data field splits the pace between target pace +/- outer limit in 5 zones that are displayed in different colors
  • Number of seconds pace average (optional): you can get direct response if set to a low value or maintain an average over a larger period.


Some screen shots:

  • Former Member
    Former Member over 9 years ago
    would it be possible to maybe split the delivery into a couple of separate deliveries for different layouts? That way at least each version would require less memory


    Technically it's possible, but I won't do that. At the moment I have 29 apps in the store. When there's a problem, a new device to be supported, or a new version of the Connect IQ framework, I have to (choose to) update them. If I have different versions for all those apps, then I have a lot more work of maintaining them. Writing apps is a hobby. I don't get paid for this. I'd like to keep it manageable.

    That being said... I will look into your request. Maybe I can optimize the field a liitle and get it to work. Also there have been some suggestions made to Garmin of changes that would reduce the memory footprint. If implemented, who knows what's possible in the next CIQ version. (This data field as it is now was not possible in Connect IQ 1.1 either.)
  • Former Member
    Former Member over 9 years ago
    Technically it's possible, but I won't do that. At the moment I have 29 apps in the store. When there's a problem, a new device to be supported, or a new version of the Connect IQ framework, I have to (choose to) update them. If I have different versions for all those apps, then I have a lot more work of maintaining them. Writing apps is a hobby. I don't get paid for this. I'd like to keep it manageable.

    That being said... I will look into your request. Maybe I can optimize the field a liitle and get it to work. Also there have been some suggestions made to Garmin of changes that would reduce the memory footprint. If implemented, who knows what's possible in the next CIQ version. (This data field as it is now was not possible in Connect IQ 1.1 either.)


    Oh wow, that's quite a lot! I can imagine the nightmare it could turn into with ever more versions of all of those, so it makes perfect sense to keep things limited. Thanks for considering my idea anyway!

    Cheers,Mattias
  • Setup Help

    I just got a Forerunner 230 and can't seem to find this app on the device. Could someone please walk me through the settings setup?
    Thanks
  • Former Member
    Former Member over 9 years ago
    To use a Connect IQ data field, you need to add it to a data screen. How to do this is explained in the Owner's manual on page 8 (Customizing the data screens).
    The Visual Pace Alarm shows more information if you set it in a bigger field, so you might want to change the screen layout.
  • Visual Pace Data field

    Hi TeunMo,

    great data field ! Thanks for all your work on this. Two recommendations I would appreciate if you can consider ...

    1) PLS remove the runner symbol from the watch face and use the screen estate for bigger numbers ;) I would also remove the set target time display from the data screen ... we will know what speed we try to keep. The won screen estate can be leveraged for larger numbers ;) which people will appreciate during race time.

    2) I would add the distance in the current lap field. This is very important when you try to keep a steady pace in long runs - e.g. Marathon ;) you basically motivate yourself for 42 times to keep the pace for the rest of the current lap stable.

    I think this two changes would make the data field a real Marathon tool ;) Appreciate you considering !

    THANKS Ralph
  • Former Member
    Former Member over 9 years ago
    Hi TeunMo,

    great data field ! Thanks for all your work on this. Two recommendations I would appreciate if you can consider ...

    1) PLS remove the runner symbol from the watch face and use the screen estate for bigger numbers ;) I would also remove the set target time display from the data screen ... we will know what speed we try to keep. The won screen estate can be leveraged for larger numbers ;) which people will appreciate during race time.

    2) I would add the distance in the current lap field. This is very important when you try to keep a steady pace in long runs - e.g. Marathon ;) you basically motivate yourself for 42 times to keep the pace for the rest of the current lap stable.

    I think this two changes would make the data field a real Marathon tool ;) Appreciate you considering !

    THANKS Ralph


    @1: I'll consider making this a setting, so the user can choose between the symbol and a bigger font. Personally I prefer the symbol, because it's color emphasizes the zone;
    @2: If you use the data field on a partial screen, you can set a lap distance in another field on the same data screen. I won't add this to this data field.
  • almost current custom pace

    Hello developer,

    My pourpose is to be able to read the "almost current pace" on an average over X seconds (where X = custom time or distance).

    I'm a runner with a brand new FR235 (thanks Santa).
    I used to run with an Android SW3 watch, with a very nice app called GhostRacer (very flexible and great programmer).

    I looked at your App on IQ, and it looks like you did a great job: bravo!

    Now on Garmin I feel a little bit in difficulty for an aspect.
    Understanding that the "instant Pace" is not the best way to run, I set "Lap Pace" (set to 1 Km) to check my performace.
    But I realized that after every 1 Km run, the Lap Pace is recalcuated starting from 0; so when I arrive at the end of the kM run the average is very accurate, but after each Km it is resetted, and only after some hundreds meters the value become stable again; maybe i's just a sensation, maybe not.

    So myy request is:
    can you create a field with the average pace on last 1 Km (or on a custom distance/time), but calculated continously during run and not being resetted after each lap?

    A great option could be the ability to set a custom distance - or a custom time - on wich FR calculates the average pace.
    For example I could have the pace of my latest 60 seconds (calculated every second on the previuos 1 minutte of run, constantly).
    Or I could have the average pace calculated on my laest 100 m of run, continously (very close to a REAL INSTANT PACE).
    This could be a "killer option".

    Can you?

    A good and simple display for 90% of runners I belive could be made this way:
    1. Avg Pace on the run
    2. Avg pace on a custom distance/time (calculated continously)
    3. distance
    ...huge numebers on a black background; it looks "easy", but impossible - until now - to find on Garmin IQ.

    Thanks in advance for listening to my request and happy new development year!!

    - enrico
  • Former Member
    Former Member over 9 years ago
    can you create a field with the average pace on last 1 Km (or on a custom distance/time), but calculated continously during run and not being resetted after each lap?


    I've already created such a data field. You can find it here: https://apps.garmin.com/en-US/apps/8671ff28-ce00-4bf3-9ded-5973a6e2a731.

    A good and simple display for 90% of runners I belive could be made this way:
    1. Avg Pace on the run
    2. Avg pace on a custom distance/time (calculated continously)
    3. distance


    You don't have to set a connect IQ data field on the full data screen, but you can also so it smaller. If you do, you can set any other fields beside it. Distance and avg pace are among the normal data fields.
  • I've already created such a data field. You can find it here: https://apps.garmin.com/en-US/apps/8671ff28-ce00-4bf3-9ded-5973a6e2a731.
    You don't have to set a connect IQ data field on the full data screen, but you can also so it smaller. If you do, you can set any other fields beside it. Distance and avg pace are among the normal data fields.


    Hello TeunMo,

    Thanks really for answering.
    I'm using your data field as "all I need on my FR235".
    Bravo!

    One question: is the Pace calculated continously (always on the latest period of defined seconds), or does it restart calculating from 0 the Pace each time the defined seconds are finished?
    This is a must-to-know, becaus if it's continous then the calculated pace is going to be very very precise all along the run (differently from what Garmin Lap Pace does).

    Here is my request, if you can: the possibility to set a distance trigger instead then a time trigger.
    Can you?

    The problem on Lap Pace calculated by Garmin default data field is exactly generated by the fact that after each lap (for example 1 Km) the pace is re-calculated as you were re-starting again the lap, losing the reached precision of the average pace calculated along the lap.

    Thanks in advance and
    have an happy new developing year!

    - enrico
  • Former Member
    Former Member over 9 years ago
    I've answered your question in the thread for that data field.