Ascent & descent alerts

Do I have this correct please?

Ascent:

Ascent alert eg 500 feet - an alert will occur every 500 feet climbed from the start point elevation.

Descent (this totally confuses me):

Descent alert eg 500 feet - is this based on 500 feet increments from the start point elevation or from the high point achieved during an activity?

  • The Ascent/Descent alerts are not 'every' time you exceed a certain amount of elevation. What you set for your elevation number = an alert given to you when you cross the threshold number set when ascending up the mountain and/or threshold number set when descending down the mountain.

  • Thanks for your reply.

    So does this mean that the alarm will go off at eg every 500 feet from a base of 0 feet, or, from a base of the starting elevation of the route?

  • As Chris stated; it has nothing to do with base or starting point or even total elevation for an activity. In the example of 500'; when the watch reaches (when ascending) or falls below (if descending) an elevation of 500' the alarm (if set) will go off. ThInk of it as, in both cases, the watch is saying 'I am now at 500 feet'.

  • Thanks for the reply.

    I think I had misunderstood the function - my interpretation of an ascent alert was that it would signal every time I ascended eg 500 feet from my starting altitude (which would have been useful) etc.

    Have I got this correct please?

    Two elevations, a maximum and minimum, can be set up.

    And then (subject to the ascent & descent alarms being On) I will receive an alert each time I pass through these elevations on the way up and on the way down?

  • Hmmm!

    I am still confused:

    On the watch I have set a maximum and minimum elevation.

    It also prompts me to set (if I want to) and ascent and descent alert with their own elevation settings.

    My confusion is how do these settings work together.

  • Regarding your repeated question still creating confusion - there is not a repeat of the elevation alert.

    Examples:

    - You set Ascent to 1,000 feet and start your climb below 1,000 feet. You will be alerted only when you pass 1,000 feet.

    - You set Descent to 5,000 feet. You climb to 8,000 feet. On the way down the mountain, you will get alerted when you pass 5,000 feet.

    - If you start your climb at 2,000 feet but your Ascent setting is 1,000, you will not be alerted on that climb.

    - You should adjust your alerts based on each hike. If you do not set your ascent and descent elevations within your starting and ending elevations, then you will not be alerted by your Instinct on that hike.

  • Thanks for the reply Chris.

    I now understand the descent/alert settings.

    Bit of a shame it does not seem possible to set more than 1 of each for an activity. 

    Unless I am missing something.

    ***

    I think I understand the minimum/maximum elevation alerts.

    These being a 'range' that if I exceed the upper or lower boundaries I will receive an alert.

    Please correct me if I have got this wrong.

    ***

    Thank you for your patience.

  • You are correct. I am happy to help.

    Depending on how deeply you want to learn to use your Instinct - I personally spend time in our Support Center daily. There are many features the more you learn your Instinct watch.

    Support Center - Instinct

  • Hi Chris, as I read it you're saying that both features work in the same way.

    On my girlfriends Fenix 6 the Max Elevation alert works in the same way that you describe the Ascent alert working.

    And also on the Fenix the ascent alert will alert you at whichever increments you tell it. Set it to 5m and once you gain 5m in elevation then it will alert you.

    Respectfully I think the reason for the confusion on these features on the (generally awesome) Instinct is that they're not working properly/robustly. I've experienced this with 3 Instincts and I'm lucky that I have a Fenix around to test it against - which hopefully helps with some objective information that may encourage engineers to revisit this one.

    The minor only issue on the Fenix is it sometimes experiences a delay in when the alert goes off, I'm assuming it doesn't check every millisecond. Also it (weirdly) seems that the ascent counter isn't locked to the altimeter. So if you start at 58m elevation, and climb to 63m the ascent counter might read only 3m ascent.

    I've tested this on Hike activity.