Pondelok, 2019, mája 13 | Verzia 4.3.1
Pretty good on MARQ Expedition - thank you !!
Sobota, 2019, mája 4 | Verzia 4.3.1
Very good data field. But there is an issue: there is random values after pause an activity and resume later then. Random fat burn value, random carb burn value every pause, resume later, resume(((
Sobota, 2019, mája 4, peterdedecker
I've heared this indeed from other people. It's best to not resume later, either let the activity run or start a new ons. Cheers, Peter.
Štvrtok, 2019, apríla 18 | Verzia 4.3
Is there anywhere a place where I can see how I can interpretate the figures.
Štvrtok, 2019, apríla 4 | Verzia 4.2.2
Not working VivoActive 3 PVS SW 6.10
Štvrtok, 2019, apríla 4, peterdedecker
use the contact developer option when you have issues.
Nedeľa, 2019, marca 10 | Verzia 4.2.2
Ich finde die APK gut aber was nervig ist ist die Benachrichtigung und Vibration
Utorok, 2019, februára 26 | Verzia 4.2.2
Once I put this analysis to my activities, I was not able to use Garmin IQ watch faces durimg aktivity anymore.
Piatok, 2019, januára 25 | Verzia 4.2.1
Amazing app. I love it. Just one question... Is it possible to get the carbs and fat dates at the same time on the Edge device? I have fat data but I don't achieve the carbs data. Only at the end of the activity.. Thanks for your job!!!!
Piatok, 2019, januára 25, peterdedecker
yes you can set this in the app settings, see this topic for how to: https://forums.garmin.com/forum/developers/connect-iq/connect-iq-showcase/115055-how-to-app-settings
Utorok, 2018, novembra 6 | Verzia 4.1-upd5
Each time I swim the app says several thousand grams of fat burned. Last swimming was 7347.95 g of fat and 4.89 grams of Carbs burned - nonsense. (57 minutes of swimming total, 2800 m, 508 kcal)
Rob Van den Boomgaard
Utorok, 2018, septembra 25 | Verzia 4.1-upd5
Works very motivating.
Streda, 2018, septembra 5 | Verzia 4.1-upd5
Good datafield, I ask if possible to have a big size text when both carb and fat are selected on Fenix 5. Too small. Thank you.
Streda, 2018, septembra 5, peterdedecker
In "simple" data fields the text size is not under control of the developer but chosen by the Garmin software. Cheers, Peter.
Utorok, 2018, júna 12 | Verzia 4.1-upd5
I still love it.
Piatok, 2018, mája 18 | Verzia 4.1-upd2
Great Idea! But a little inaccurate, I think. When I walk almost 100% of the calories burned are attributed to fat. May I suggest that you use the information provided on this website to make the fat burn a little more accurate? http://www.exercisemed.org/research-blog/exercise-intensity-for.html
Piatok, 2018, mája 18, peterdedecker
you can configure the percentages in the app settings. See this link for how to do app settings: https://forums.garmin.com/forum/developers/connect-iq/connect-iq-showcase/115055-how-to-app-settings Cheers, Peter
Pondelok, 2018, mája 14 | Verzia 4.1-upd2
pocita to podla algoritmu ktory nedava ziadny zmysel.. neberie do uvahy rychlost ,stupanie atd
Nedeľa, 2018, mája 13 | Verzia 4.1-upd2
Great work! Thanks for your effort. I have a small suggestion. Wouldn't it be more meaningful if the graphs display fat/carbs burned per hour instead?
Nedeľa, 2018, mája 13, peterdedecker
Doing it on a hourly base is a bit of a problem. What if you don't run for an hour for example? Cheers, Peter.
Utorok, 2018, mája 1 | Verzia 4.1-upd2
Štvrtok, 2018, marca 15 | Verzia 4.1-upd1
As I have been able to verify, the application has a fault, every time you put on pause and resume the exercise, the burned fat increases considerably, therefore, the data of burned fat is erroneous.
I checked it by doing indoor bike, in 14 minutes of exercise stopping and resuming the clock, I burned 10.05g of fat and 7.38g of carbs and 120 Kcal, and the same day but later, in 43 minutes of continuous exercise I burned 9 , 60g of fat and 129.90g of carbs and 606 Kcal.
Therefore the data of burned fat is not correct, and I repeat, I have detected the fault when during an activity, you stop the timer and continue several times.
I hope it can be solved because it is a good application. Greetings.Sorry for the translation
Streda, 2018, januára 24 | Verzia 4.1
Theoretical a nice data field but still a bad bug:
In case you choose 'fat and carbs' and record (!) both ... than pause the exercise and follow it up it up later ... this fit file gets corrupt and prevents synchronisation with Garmin Express.
The only way to get it working again is deleting that fit file from the watch and (!) from the computer !
Strange thing as it does not happen when 'fat and carbs' are not recorded.
Štvrtok, 2018, januára 25, peterdedecker
For future support questions please use the support topic. Fit file writing is not something that is under my control, all I can do is set the value, the writing to FIT file is something that the Garmin API handles. There's a multitude of FIT issues that all have been reported. If you synchronize through Garmin Connect Mobile and use the Garmin Connect web version to consult seems to be the best combo. Cheers, Peter.
Sobota, 2018, januára 13 | Verzia 3.1
Buena aplicación para saber la grasa y carbohidratos que se gasta en cada entrenamiento, es configurable. Muy buena aplicacion!!!
Streda, 2017, decembra 20 | Verzia 3.0
Nedeľa, 2017, decembra 3 | Verzia 2.7-upd
It's really great to see that you can give us back us in some way what Garmin has withdrawn, namely the fat calorie calculation which they introduced already for 310XT and 910XT.
I wrote a longer message with 'contact developer', but let me highlight here too, that the predefined percentages of the widgetis are too high for people except for pro athletes.
I guess before you assigned the percentages to the HR zones the latter were considered as zones applying the modified Karvonen approach, so breaking down the HRR into 5 zones like 50-60%, .... and 90-100%.
Since I participated in respirometry test in real labs where even a cardiologist supervised the whole procedure I must say that my Respiratory Exchange Ratio at different HRs implies that already in the upper part of Z0 the share of fat is less than 80%. So for the whole Z0 and especially for Z1, 100% is an overly optimistic estimation. And similarly 80% for Z2 is almost double of my numbers.
Certainly I could tweak my HR zones to get a better fat cal estimation, but I fear that some other numbers will be accidently tweaked and ruined like training effect.
Anyway my main message should not be this one, but the happiness seeing that somebody started to deal with fat calories burnt as a data filed of Garmin gadgets,
Štvrtok, 2017, novembra 23 | Verzia 2.7-upd
my Favorit IQ DataField on FR3 and Edge820. Thank you very much, Peter. Is it possible to make a simple linear (or expo) function to calculate the fat grams (100% = HFrest, 0%=HFmax) instead of clustering to HF zones, perhaps it will be more precise? Don't misunderstand, it's a good tool already.
Piatok, 2017, novembra 24, peterdedecker
I'll take it into consideration, I've added your request to my todo list. Cheers, Peter.
José María Risco García
Pondelok, 2017, októbra 16 | Verzia 2.7
Excelente para saber qué cantidad de grasa aproximada te quitas en cada entrenamiento con la bici.
Streda, 2017, augusta 16 | Verzia 2.5
Great data field ... but it looks like I don't burn any carbs after the last update (Fenix 5x) ...
Utorok, 2017, augusta 15 | Verzia 2.5
I have FIT recording ON, but I dont see it in GC like you have it at your screenshots.
Utorok, 2017, augusta 15, peterdedecker
Hey JD, for questions preferably use the support topic. I think the answer to your question might be stated here in this post: https://forums.garmin.com/forum/developers/connect-iq/connect-iq-showcase/159060-?p=1228852#post1228852 In case that doesn't fix it, let me know. Cheers, Peter.
Nedeľa, 2017, augusta 13 | Verzia 2.4-upd
Great DATA FIELD.
Please, tell me - where I can find info about burned grams in Garmin Connect?
Nedeľa, 2017, augusta 13, peterdedecker
you can see this in the graph section on connect, for an example see the forum support topic: https://forums.garmin.com/forum/developers/connect-iq/connect-iq-showcase/159060-?377823= Cheers, Peter.