Data Field: Fat Burner

The Fat Burner is a simple datafield which fulfills a user request from Susun.

Connect IQ App Store Link: https://apps.garmin.com/en-US/apps/7...2-20971e02898b

This field calculates the fat calories burned depending on heart rate zone & calories:
  • Z1: 9kcal burned = 1 gram of fat burned
  • Z2: 80% fat
  • Z3: 50% fat
  • Z4: 20% fat
  • Z5: 0% fat


In the settings you can:
  • opt to see Fat Burner (=default) / Carbs Burner / Fat Burner and Carbs Burner (Advice : do to consume too much carbs per hour, the absolute maximum is 70g/hour)


During your run it looks like this:


On Garmin Connect you can afterwards consult how many fat and carbs you have burned (if you have indicated in the settings to record it):


how to activate the app on your watch?
(it might be slightly different on your watch, this is how to do it on a fr735xt: from watch face - click start - choose an activity profile (eg Run) - hit down button - activity settings - click start - data screens - click start - screen 1 - click down button - field 1 - click start - hit down until you're over connect iq - hit down until you' re over fat burner - click start )

Advice by Susun:
For the users that want more accuracy, better if you use Karvonen formula using Garmin profile settings.
Karvonen method is more precise because is related to VO2 max for the most of people so I recommend it.

Go to your user profile and then HR zones configuration, choose %HRR and put your HR-Rest and set the zones as this:

Z1: 50-65
Z2: 65-75
Z3: 75-85
Z4: 85-95
Z5: 95-100(HR Max)
  • As the 4g/kcal for carbs seems to be more standard I've defaulted the new version to use this value, but you can change it to 4.5 in the settings of the app.

    Released v3.0:
    - Made percentages of %Fat Burned & %Carbs burned configurable in the settings (defaults to percentages that were used before)
    - Made kcal/g configurable (defaults to 9 for fat and 4 for carbs)
  • Fine. I felt some thrill and was about to test it imediately when I saw the update at the time of wake up, but the bloody rain hinders me.

    I will report my findings later. For now just a thanking.
  • 1. Do I understand it correctly that in v3.0 the percentages are for the whole zones and they are not the percentage of the mid-point of the respective zones?
    I mean for the time being there is not interpolation yet.

    2. And what is the situation with Z0? 100% fat for the time being?

    I am tweaking my HR zones as a try to minimize the discrepancy between the 23 HR/cal zones of my meatobilc profile running on 910XT and Fat Burner running on my Fenix 3 HR. So knowing what happens in Z0 helps me a lot.
  • 1. Whole zones, no interpolation yet indeed. The interpolation approach release is likely not something that will arrive in the next few weeks as I've got a few other apps to work on. Once the interpolation method is implemented the number you enter will indicate the percentage at the bottom of the zone, not the midpoint.

    2. you can customize the percentage for Z0 as well, there should be a setting for both the carbs% and the fat%. At the moment Z0 is everything below the minimum of Zone 1, once I implement the interpolation the minimum of Zone 0 will become your resting heart rate.
  • Hoi Peter,

    Today I had the first thest with v3.0. It was a long walk of 4 hours and unfortunately I was almost exclusively in my Z0, but it seemed that Fat Burner app worked as it should have.

    On the other hand my Fenix 3 HR crashed once, it froze displaying with the Garmin logo. It never earlier happened to me, so for more than 11 months never, but you should know that this is a replacement watch, my watch was swapped a month agodue to barometer problems.

    I made an enforeced restart with a long push and when the watch restarted it showed the activity as a resumed one. So I resumed it, but in the place of Fat Burner data field there was Timer. So far I learned that if Fenix 3 HR as a problem with a data field, it always replaces it with Timer data field.

    But nevertheless I am not sure about what the cause is and what the consequence is. I do not know whether the crash was due to Fat Burner, so the app was the cause and its replacement with Timer was the consequence or just the opposite.

    I have an experience earlier with another data field, LapByPosition, it was automatically replaced with Timer, but at that time as I remember there was no crash

    Do you have any idea what happened? Any same sort of experience?

    1. The watch went made by itself and it would have replaced any non-native data field, not just Fat Burner?

    2 Or Fat Burner made the watch go mad and the watch wanted to get rid of Fat Burner as a root of the problem?
  • Normally data fields can't make the watch crash, the most they can do is present an IQ! when the datafield crashes. When the datafield crashes there is a file in \Garmin\Apps\Logs\CIQ_LOG.TXT, when the watch crashes there's a file called ERR_LOG.txt in the root of your device. Can you connect your f3 with usb and see if any of those files exist and post it's contents?
  • No, no error log file under apps, just in the root directory. So now I understand there was no relationship between the crash and the app. Btw the error log file says


    2413 (fenix 3 HR) SW ver: 452
    Build Type: RELEASE
    ESN: 3961091758
    Battery Voltage: 3.946000V
    12/17/17 14:22:19
    BF
    PC: 0x0003aa7c
    LR: 0x0003aa5d
    SP: 0x20022f30
    CFSR: 0x00008200
    Return Address (LR): 0x00164cf3:Call Stack - PSP at 0x20022f10:
    0x0003aa5d
    0x000d3a6b
    0x00162777
    0x00163145
    0x00069be5
    0x001f9e3d
    0x00162715
    0x0016305f
    0x0016305f
    0x0016305f
    0x0016305f
    0x0016305f
    0x0016305f
    0x0016305f
    0x0016305f
    0x0016305f
    0x0016305f
    0x0016305f
    0x0016305f
    0x0016305f
    HWM_usb_connected = 0x00. HWM_usb_mode = 0x01.
    page addr = 0x000d3a25
    page addr = 0x0015edcd
    page addr = 0x00133819
    page addr = 0x000d2115
    Uptime: 656518853

    2413 (fenix 3 HR) SW ver: 452
    Build Type: RELEASE
    ESN: 3961091758
    Battery Voltage: 3.950000V
    12/17/17 13:23:52
    AP
    LVD
    POR


    Having seen the content of the log file do you think I should report it to the Beta team or it makes no sense, because this type of crashes happen quite often?

  • Yes report it based on that error log the fenix3 team can fix this issue
  • As some sort of payback let me disclose my fat burning in different zones. Until today I applied lower fat burnt % in the higher HR ranges, but I re-examined my VO2 and VCO2 data and this time I was not so cautious as earlier in accepting the numbers. Earlier my assumption was that I did not have enough time to get to steady state at higher HRs, therefore I considered my VCO2 data as exaggerating ones.

    This time I dared to rely on the data which are more in line with publication which can be found on the interweb.

    I do hope that these publications are based on steady state tests and not on stress test to get VO2Max, because the latter is not suitable for an indirect calorimetry examination. I am quite sure even if these VO2Max tests are marketed in a different way.

    I also prepared myself, so I calculated not just the average fat burnt% for my zones, but also those for the low boundaries. So if you Peter will have finished with the next phase, the interpolation, I can easily replace the data. So here we go:
    [TABLE="border: 0, cellpadding: 0, cellspacing: 0"]
    [TR]
    [TD="class: xl70, width: 376, colspan: 6"]FAT BURNER DATA FIELD FOR FENIX 3 HR[/TD]
    [/TR]
    [TR]
    [TD="class: xl73"]zone[/TD]
    [TD="class: xl74"]bottom[/TD]
    [TD="class: xl74"]top[/TD]
    [TD="class: xl74, colspan: 2"]fat % at bottom[/TD]
    [TD="class: xl75"]zone %[/TD]
    [/TR]
    [TR]
    [TD="class: xl76"]Z0[/TD]
    [TD="class: xl77"]58[/TD]
    [TD="class: xl77"]123[/TD]
    [TD="class: xl79, colspan: 2"]95%[/TD]
    [TD="class: xl78"]80%[/TD]
    [/TR]
    [TR]
    [TD="class: xl65"]Z1[/TD]
    [TD]123[/TD]
    [TD]136[/TD]
    [TD="class: xl80, colspan: 2"]65%[/TD]
    [TD="class: xl66"]64%[/TD]
    [/TR]
    [TR]
    [TD="class: xl65"]Z2[/TD]
    [TD]136[/TD]
    [TD]149[/TD]
    [TD="class: xl80, colspan: 2"]63%[/TD]
    [TD="class: xl66"]54%[/TD]
    [/TR]
    [TR]
    [TD="class: xl65"]Z3[/TD]
    [TD]149[/TD]
    [TD]162[/TD]
    [TD="class: xl80, colspan: 2"]45%[/TD]
    [TD="class: xl66"]33%[/TD]
    [/TR]
    [TR]
    [TD="class: xl65"]Z4[/TD]
    [TD]162[/TD]
    [TD]175[/TD]
    [TD="class: xl80, colspan: 2"]21%[/TD]
    [TD="class: xl66"]10%[/TD]
    [/TR]
    [TR]
    [TD="class: xl67"]Z5[/TD]
    [TD="class: xl68"]175[/TD]
    [TD="class: xl68"]188[/TD]
    [TD="class: xl81, colspan: 2"]0%[/TD]
    [TD="class: xl69"]0%[/TD]
    [/TR]
    [/TABLE]
  • interesting. can you link to the internet article you make reference to?