Related
Options

Elevation question

lindajm22
over 5 years ago

The two elevation profiles below were runs on the same 3 miles of a relatively flat rail trail.  I run this almost every time I run. There's a slight incline on the way out, so a decline on the return.  The first image was from my run today using my Fenix 6S and the second was using my 945 a few weeks ago.  Why is it so choppy with the Fenix and smooth with the 945?  This was my very first run with the Fenix so I have nothing to compare it to.  Just want to confirm there's no problem with it.

  • Former Member
    0 Former Member over 5 years ago in reply to Dr Phil

    Temporary fix is to run no more than 59 seconds.  Relaxed   Just got the same type of graph for the first time using my 945.

  • 0 over 5 years ago

    First run with my replacement 6S sapphire which is on 4.10 and it is choppy and definitely pulling data once every minute.  My elevation numbers are perfect still so I'm not too bothered by it, but I wonder what's causing it across multiple Garmin models. It's been a very recent change.

  • Former Member
    0 Former Member over 5 years ago in reply to lindajm22

    Same here. Was OK Wednesday. Was OK yesterday but with another f6. Choppy today with the same f6 that was OK Wednesday. 

  • Former Member
    0 Former Member over 5 years ago

    Same problem for the MARQ. I did a bike/trailrun/bike session today, logged as different activities. Two of three had jagged altitude curves. In addition, I had the altitude and total ascent/descent on one of the data screens, and it was quite obvious that sampling was highly irregular (up to more than3 minutes for an update) even faulty with decrease in altitude as I actually climbed. Only the slow bike session home had a reasonable altitude curve. In between the activities I once re-started the watch (long press on light button) and twice did a manual altitude calibration using DEM data.

    Bike ca 20 minutes (warm up and transport)

    Trail 70 minutes

    Bike ca 15 minutes (cool down and transport)

  • 0 over 5 years ago

    I haven't been able to duplicate the choppy elevation graph with mine, seems like the graph is displaying the way it should

  • 0 over 5 years ago

    For anyone who's been having this problem, have you noticed your elevation before you start an activity? I've seen that at night, sometimes my elevation goes from ~400 m (correct) to ~-8386000 meters. That number looks suprisingly close to -2^23, which makes me think that Garmin is stomping on memory. My watch face displays the altitude, otherwise I wouldn't have noticed this.

    When I start an activity without recalibrating altitude, I get this problem. *So far* when I recalibrate first, then start an activity, the problem doesn't happen.

  • Former Member
    0 Former Member over 5 years ago

    Did anyone tried to update the maps with Garmin Express on a computer ? I saw that all maps have an update. I'll try tomorrow. Today was very choppy...

  • 0 over 5 years ago in reply to Former Member

    I´ve updated the maps but have the same step profile as reported here on a run an hour ago. But that was well expected, because maps should have no effect on the altimeter :)

    Heart rate was also not working very well, but that could be on me for wearing the wath a bit to loose.

  • Former Member
    0 Former Member over 5 years ago in reply to S_Ta
    • Yeah I know, I know... I don't remember having a nice altitude profile.. Maybe day one. And I think tried everything Rolling eyes
  • Former Member
    0 Former Member over 5 years ago in reply to S_Ta
    S_Ta said:
    because maps should have no effect on the altimeter

    It does if you're calibrating using DEM.