Related
Options

Today I made an awesome experience with the altimeter in watch mode ;-)

Mistamb
over 3 years ago

I forgot to charge to charge my Fenix 6x, so I took out my Fenix 5x. I calibrated the altimeter to the actual elevation 662m and used the watch in normal watch mode. I did a lot of work in and outside my home. So I went from the warmth home outside in the rainy day a couple times. The 5x always kept the correct altitude. Its all on the same floor. So after a view hours of walking from inside to the outside, I still got the correct 662m and I did not move in elevation.
When I do the same with the 6x I always have values from around 655m until 670m after a couple hours, without walking up and down. On FW 19.20 it was the last time when it has worked like that. :-)

  • 0 over 3 years ago

    Once a week I delete the newest FW in GC web to be sent to my watch.  So I have a F6X which I am mainly pleased with.

    I dont use Battery Saver, because I cant stand its random auto switch-on post-activity, I accept that after the first lap lap pace sometimes is 0:00, finally I know that the high and low values will be not shown in barometer plots if the max-min is over 10 mbar. 

    But until the altimeter-related complaints will not disappear I will stick to 19.20, I am ready to sacrifice the CIQ System 5 thingamy, too.

  • 0 over 3 years ago

    What altimeter settings are you using on the 5x?

  • 0 over 3 years ago in reply to #Matthias#

    i use the auto mode in watch mode. on both watches.i don't really complain about the 10-15 meters which are wrong after a day when you come home on the fenix 6x. with actually firmware. 
    but i found it awesome, that it worked so well with 19.20. now i can't walk outside in the garden. when there are big temperature differences. before it was nothing to think about. 
    the same with the widget. before you can use the ABC widget to check the pressure changes. now it automatically set the baro to altimod when you enter the widget. and changes the altitude.  

  • 0 over 3 years ago in reply to Mistamb

    Okay, interesting. Have you compared the two watches in watch mode when you actually change altitude, e.g. walk up a hill? It would be interesting if it is more sensitive/accurate with actual elevation changes using the new algorithm.

  • 0 over 3 years ago in reply to #Matthias#

    yes i already have. the new algorithm switches (only in my opinion) to fast into alti mode. yes i catches up miner alti changes as the old one. but we are only talking about the initial automatic switch from baro to alti mode. 

    lets say (just as an example): the the new algorithm switch from Baro to alti on an pressure change equivalent to 1m of elevation in 3 minutes. the old on 1 floor (3 meters). and both switch back to baro mode when there is not more then the 1meter or 3 meter change in 3 minutes. 

    so when you walk up a hill, both have the same elevation change. but the old algorithm doesn't have the false positiv alti switches.

  • 0 over 3 years ago in reply to #Matthias#

    suunto for example has a well documented algorithm which is proofed over years and works quite well.
    ambit3 manual 

    its the same point for the storm alert. when the auto mode switches too fast from baro to alti mode. storm alert will not work anymore. you will just have an fast increase in elevation. even if you're not moving in elevation

  • 0 over 3 years ago in reply to Mistamb

    Indeed it seems to be the proper, transparent way to explain what your device does:

    "If you are at a constant altitude (less than 5 meters of vertical movement within 12 minutes), Suunto Ambit3 Peak interprets all pressure changes as weather changes. The measurement interval is 10 seconds. The altitude reading remains steady and if the weather changes, you will see changes in the sea level air pressure reading.

    If you are moving in altitude (more than 5 meters of vertical movement within 3 minutes), Suunto Ambit3 Peak interprets all pressure changes as movements in altitude."

    I never understood why these parameters are hidden by other names. This sort of info is not like precious pieces of knowledge which have to be patented and saved as business secrets.

  • 0 over 3 years ago in reply to Tisztul_A_Visztula

    The problem that after the first lap lap pace sometimes is 0:00 is still present in the last firmware

  • 0 over 3 years ago in reply to Mistamb

    I have the Fenix 7 and I agree that it seems that the algorithm is indeed very sensitive in translating minor pressure changes to altitude change. 

  • 0 over 3 years ago in reply to Miky

    Thx for sharing it. So (at least) since 19.20 Garmin has not fixed none of the 3 bugs of which there are dedicated threads here and by the way which  I reported to support. So the typical answer here “ Garmin doesnt read the forums here” is irrelevant.