Data Field: AppBuilder

By user request, this app lets you define your own data field, based on a simple math formula like cadence / 2.

If you want to get fancy, there's conditional expressions (like IF in Excel), functions for data analysis (like MIN and AVG), and the data field can also display the text of your choice. The resulting data can be (optionally) written to the activity FIT file.

With AppBuilder, you can implement almost any field that involves math, such as: calculating normalized power and saving the data to the FIT activity file, showing the average pace for even-numbered laps, or recording the amount of time you sprinted.

Full documentation and examples here:
http://ciq-appbuilder.blogspot.com/

AppBuilder 5:
Now with new features! AppBuilder 5 is a completely new app, so please check it out in the store if you are interested in any of the new features.
https://apps.garmin.com/en-US/apps/fd690281-9c22-4fee-a81e-3b7f39aa67c5

- Store up to four formulas per app. Switch between formulas directly on the watch, without using a phone or PC. With four clone apps, you can store up to 16 formulas total
- User variables. Allows for powerful formulas where information can be stored at one point, like the start of a lap, and used later. e.g. Lap elevation change
- Improved timeavg() options. Allows for simpler, more flexible normalized power function
- More functions and variables

4 clones of AppBuilder are available in the store, so you can have 2 formulas in the same activity
  • Latest update [2.3.8]:

    Added SUM[x] function for CIQ 2 devices, which calculates the sum of x for the entire activity [sampled once per second].

    e.g. # of seconds spent sprinting [running faster than 16 km/h]:
    SUM[Speed GT 16]
  • With 2.3.8 I'm still getting IQ! with a constant in the formula. For info. I looked in Manage Storage on the GCM and it says the app is using 13K.

    I think 2.3.2. or 2.3.3 was the last one that worked.
  • AppBuilder (and AppBuilder2) have now been fixed for CIQ1 devices such as FR230 (and hopefully, Fenix 3). I've only been able to do real-life tests on a FR230 and FR935, so please let me know if simple formulas such as "5" and "Cadence / 2" don't seem to work.

    Thanks for the help, PubBike!
  • I installed the new version, set the expression to Timer, (since in the Row app Cadence=0) and....it worked!

    Many thanks for persevering with this FlowState!

    PS: Also glad to know my fenix 3 isn't completely obsolete!
    PPS: Posting this from Safari since intermittent log-in issues with Chrome
  • GPS Location Accuracy isn't available as a user selectable data field on the fenix 3, but AppBuilder allows me easily to display it.
    Thanks!
  • Latest update: 2.5
    - Older devices: Add support for PREV[], TIMEAVG[] and TIMEAVG0[]. Note that memory is tight on older devices, so try to limit the number of samples you use for TIMEAVG[] to 5 or 10.

    Memory usage for other scenarios on older devices has been improved -- e.g. you should be able to use IFS[] with even more conditions before.

    - All devices: Add error checking. If your formula has issues, one of the following errors will appear in the datafield;

    !Syntax: Syntax error: e.g. 2 * 3 /

    !Name: Unknown/misspelled variable or function: e.g. "Timmer" instead of "Timer"

    !AdvFn: Formula contains a function not available on older devices

    !AdvVar: Formula contains a variable not available on older devices

    If the field crashes ["IQ" error], then it is most likely that the formula is too complex or uses too much memory: e.g. overuse of PREV[] or TIMEAVG[] on older devices.
  • 2.5.1: Optimize a bit of code to save memory, especially on older devices.
  • 2.5.2 Update for older devices:

    - Add SUM[], MIN[], MAX[]

    - Add heart rate zones

    - Device unit settings for distance, speed/pace and altitude are only applied when the data field is initially loaded (at beginning of activity). This saves precious memory while the field is running, so more functions can be supported on older devices. Newer devices are unaffected by this change (unit settings are still applied at any time during the activity.)
  • 2.5.3
    Optionally record data to FIT file (controlled by app settings). Enabling this takes memory, so please be careful with older devices, complex formulas (PREV(), TIMEAVG()) and FIT file recording.
  • 2.6 Reduce memory usage, especially for older devices, especially when using TIMEAVG()