• Replies 893 replies
  • Subscribers 49 subscribers
  • Views 95309 views
  • Users 0 members are here
Options
Related

Data Field: AppBuilder

FlowState
over 7 years ago
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
  • over 5 years ago
    Hi have tried this formula:

    SETV(1,(1-(2/100))^-1*(9.8067*(UserWeight+10)*(((Altitude_raw - PREVN(Altitude_raw, 14)) / (Distance_raw - PREVN(Distance_raw, 14)))+0.005)+(0.5*0.63*0.509*1.22601*Speed_raw^2))*Speed_raw) ; RECORD(IF(GETV(1) GT 0 AND Cadence GT 0, GETV(1), 0),7)

    but i have error message : "!Name"

    can be that RECORD function not works with Edge 520 ?
  • Former Member
    Former Member over 5 years ago
    I forgot that the convert to code part doesn't work on AB5 and lower end devices so it would result in "!Name" error like you got, if you converted the formula as code. Sorry about that.

    If you did that then forget about it and just copy formula as plain text. RECORD function should work and works at least on my old Fenix5 on AB5, which also has less memory than Fenix5+.

    Longer formulas like Normalized Power won't fit as plain text, but if you already use default values and don't plan to change them you could just add them up to single value to save space so for example 0.5*0.63*0.509*1.22601*Speed_raw^2 becomes 0.19657231335*Speed_raw^2 and then you can barely make it fit.

    If it still doesn't work, then Edge 520 has even less memory than Fenix5. So you may have to do further reductions to make it work. Hopefully that is not the case.
  • over 5 years ago
    I Think is not problem of memory. Becouse formula Normalized Power works fine.

    But now works!!
    the problem was when i copy and past the formula from my phone to Garmin Connect. it's a mistery!!

    Now i go out to test formula on Climb of 10 km with average grade about 5-6%.

  • Former Member
    Former Member over 5 years ago
    Ok, hopefully it will work. Although it shouldn't be much different from last time if you just use the default values.

    Also if you have a computer with Garmin Express I would highly recommend using it when dealing with more complex formulas. It's slower but you'll greatly reduce chance of errors. The mobile is pain to use.

    Ps. I had to remove speed detection and averaging from grade formula to make it fit. However you shouldn't loose much as 3 second averaging hardly does much and the cadence detection should already handle false power values when stopped. It should also give you more realistic power when you don't pedal, otherwise it would calculate it even when you're just freewheeling.

    BTW, out of interest do you also have a separate speed sensor or are you just using GPS for speed?
  • over 5 years ago
    Since the focus of our conversation moved from Lap+ to Appbuilder, I'm moving over to here. FlowState, you suggested I try AppBuilder 5 for my situation. Looking at your various datafields, I see that 5+ works on the 645 Music, but not on the 645. Is there a reason it won't work on the non-Music 645? The reason I ask is if I should happen to decide I want more than one field (since I believe I'd have to remove one of my two "Multi-datafields" in order to use AppBuilder, since Garmin has a limit of 2, currently using Lap+ and RunnersDreamRound), I'd probably want to pack in a few more fields if I could, still need to play with it to see how it all works. Thanks for the pointer to this app!
  • over 5 years ago
    Ok, hopefully it will work. Although it shouldn't be much different from last time if you just use the default values.

    Also if you have a computer with Garmin Express I would highly recommend using it when dealing with more complex formulas. It's slower but you'll greatly reduce chance of errors. The mobile is pain to use.

    Ps. I had to remove speed detection and averaging from grade formula to make it fit. However you shouldn't loose much as 3 second averaging hardly does much and the cadence detection should already handle false power values when stopped. It should also give you more realistic power when you don't pedal, otherwise it would calculate it even when you're just freewheeling.

    BTW, out of interest do you also have a separate speed sensor or are you just using GPS for speed?


    I use speed sensor Garmin GSC10 (is also for cadence).
    But i dont know if take speed from sensor or from GPS.
    I must verify this particulary.

    For you, using Appbuilder, is best sensor speed or GPS ?
  • over 5 years ago
    Nighthawk700 the 645 Music has twice the memory available for CIQ data fields as 645, and there is just not enough memory on the 645 to implement 5+.
  • Former Member
    Former Member over 5 years ago
    BortoloS actually never mind, seems it's only used as fall back or when GPS not available, so shouldn't make a difference.
  • over 5 years ago
    JTH9 OK. Then there are not big differences.

    Yesterday i have training for 130 km and one hard climb of 11,5 km. About 54 minutes of climb and for me the formula works fine on climb.
    Only downhill i have 0 Watt also when Cadence is > of zero.
    I think also that calculate of Watt in downhill is negative value.
    I understand that is very difficult calculate watt on downhill, but if is posible have one almost real value...is good.
    This problem is when grade is negative.
    I attached graph of climb of yesterday.
  • Former Member
    Former Member over 5 years ago
    Yes actually for downhill the original formula can be negative. But I don't think you really want negative power so I set the formula so that it disregards the negative values and just returns 0. If you want negative power, just remove GETV(1) GT 0 AND before the cadence detection bit.

    To be fair you wouldn't get negative values with real power meter either, but might be the formula leaves something to be desired here for downhill accuracy. You could ask the person who made the original formula at https://www.gribble.org/cycling/power_v_speed.html

    Using this formula on a grade of -5 you would have to go as fast as 50kph to get any power and at 60kph you'd already get 300w based on the calculator on the aforementioned site.

    On steeper grades you'd have to go even faster. Things can get very dangerous on a bike at speed with thin tires, so always play safe and rather just try to go harder uphills. You could use lap power to clock your average and keep downhills for recovery :)