Elevation Profile, Climb Pro, Waypoints, ETA issues

Former Member
Former Member
Had issues earlier uploading images and attachments, so I'm just going to link to all the screenshots I took for the issues I had with my watch on my last hike.

I'll begin by saying that for my first long hike with the 5+ I was very happy with the results. It helped me, especially the maps, in some very wooded areas and lost trails. The stats were also valuable, but as you will see, there were some issues. I have started a ticket with support, but thought I'd post my results here in case others are having similar issues, can correct me if I'm doing something wrong, or can provide any answers.

For reference, you can view my tracked courses on Garmin Connect at the links below which provide spot-on data.

Route to summit
Route back to trailhead

Issues:

Elevation Profile and Climb Pro
Elevation Profile was not working from the start. I even calibrated the elevation prior to starting the hike hoping that would help, but it did not. GPS locked on my position within seconds and did great on the entire hike. As seen in the courses above, this mountain is about 5,000 feet in elevation gain, yet the elevation profile displayed a flat line with a spike at the end. As I hiked up the mountain, the final elevation at the end of the graph only increased. Here are some screenshots of the ascent taken at different intervals:

Elevation Profile Ascent

The start elevation and the elevation gain up to the current elevation at the time looked fine, but again, the final elevation was always off and made the elevation profile screens useless. Here are some screenshots of the descent:

Elevation Profile Descent

Climb Pro was even worse. Too bad because I was really looking forward to having it help me gauge steep climbs.

Climb Pro Ascent


Waypoints
I don't know if I set up waypoints incorrectly or maybe the feature just doesn't work the way I expected, but I had hoped that adding waypoints in a BaseCamp created course would alert me when I was approaching and show the distance remaining to the next waypoint in the data screen on the watch as I had set. Neither worked. Instead, the Distance to Next field showed the distance to the end of the course. Here is the course from BaseCamp that I uploaded to the watch:

BaseCamp Course Details

Did I do something wrong? Any suggestions or comments here?

ETA
Finally, the ETA issue. On the hike up to the summit, the ETA worked just fine and adjusted to my pace properly. On the way down however, it was off from the beginning. In the screens below, you can see how I had almost 4 miles remaining. At 11:31, my pace was about 20min per mile so I should have an ETA of about 12:50 or so. Instead, it showed me finishing the course at 12:08!

ETA with time

Here are a couple more screens showing my pace and ETA:

ETA with pace

Again, very strange that ETA worked fine on my summit approach, but failed on the descent.


Final Thoughts

Overall, I really enjoyed using the fenix for my hike. It helped navigate me properly and provided most of the stats I needed during the course. Still, having correct elevation profiles, climb pro, waypoints, and ETA working would have made the day perfect. I'm hoping all this can get resolved before my next big hike!
  • Former Member
    0 Former Member over 6 years ago
    Hi TrailCat, how worked the altimeter for you during your hike? I experienced that the auto calibration of the altimeter doesn't really work reliable with my 5x plus (see my posts at https://forums.garmin.com/forum/on-the-trail/wrist-worn/fenix-5x-plus/1406115-alimeter-issues/page2

    Peter
  • Interesting that DCR noted issues with ClimbPro when he did his original overview of the F5+ series. It was in the video version.

    If this is the same bug it's a pretty poor show from Garmin...new features not only defective on launch but still not working properly months later....

    It's a great feature if only it would be reliable...
  • Had issues earlier uploading images and attachments, so I'm just going to link to all the screenshots I took for the issues I had with my watch on my last hike.

    I'll begin by saying that for my first long hike with the 5+ I was very happy with the results. It helped me, especially the maps, in some very wooded areas and lost trails. The stats were also valuable, but as you will see, there were some issues. I have started a ticket with support, but thought I'd post my results here in case others are having similar issues, can correct me if I'm doing something wrong, or can provide any answers.

    For reference, you can view my tracked courses on Garmin Connect at the links below which provide spot-on


    Hi Trailcat..

    Track (especially on way up) looks terrible. Did you deviate from the path alot or is the map incorrect? Otherwise I don't understand how this can be described as 'spot on'?

    I really think there is some kind of denial/cognitive dissonance thing going on with gps tracks with many users?

    Thanks
  • Former Member
    0 Former Member over 6 years ago
    Halldrine If you use Google Maps as the map layer, then the route does look bad, but using OpenLayers as the layer makes it look more accurate. On Basecamp, it is well within the deviation of GPS for a watch I'd say. I also watched that DCR video before purchasing the watch, but thought all the issues would have been sorted out by now.*

    @???????Schwammerl*I did not use the altimeter during the hike. I relied on the elevation provided by the course data.

    renton82 Thanks for the links to the posts. I just gave them a read. Even though I calibrated the altimeter, I don't understand why I should need to if I was going to rely on the course/map data for elevation. The elevation profile screens I posted show the beginning elevation at 180' which is pretty close. As I made my way to the top, the current elevation on the Elevation Profile screen was pretty accurate as well. The course I uploaded showed an ending elevation of 4,926' so it doesn't seem that difficult to post 180' at the start of the profile graph, 4,926' at the far end, and fill in the gap with elevation points from the course. Yet, the elevation at the end of the graph was waaaaaaaay off.

    If Garmin is listening, I'm willing to help out, as well as most users I'd suspect. This elevation profile bug is top priority since it's a major feature of the watch. Gotta get this straightened out.
  • Trailcat,

    Do you have a Basecamp screenshot showing the track on the OpenLayers map layer?

    Many thanks
  • Former Member
    0 Former Member over 6 years ago
    Here's a BaseCamp screenshot with the TopoActive US/Canada 100k map that I used to create the course. The solid gray is the course I created, the dark dashed gray is the recorded route. I also recorded the route using my iPhone (GAIA GPS) and the watch actually recorded the route closer to the trail, so I was impressed.

    https://www.dropbox.com/s/5xrbc8mmetlogli/basecamp-course.jpg?dl=0
  • The curved parts of the trail could be due to "Smart Recording", it's recommended that you go into Settings - System - Data Recording and change it to "Every Second". This should improve the track that has been generated. I'm afraid I can't answer your main queries.
  • Former Member
    0 Former Member over 6 years ago
    I'm fine with using the default GPS tracking to conserve the battery.

    I think the issue that bugs me most is the waypoints. I feel that the Elevation Profile will get resolved since for most users, it was working before. But for waypoints, that's kind of a big deal to a hiker. I go on 30+ mile hikes so it's nice to lay a course with a few waypoints in the middle as destinations. When I saw the Distance to Next data fields I was super excited to finally have a way to gauge how much longer it would take to reach a waypoint. We shouldn't have to use some outside service to get this working either. Basecamp has waypoints so that should be all that is needed.
  • Former Member
    0 Former Member over 6 years ago
    UPDATE:

    I was able to get the Elevation Profile and ClimbPro working on my last hike. My issue was that I uploaded the Course I created in BaseCamp instead of first converting it to a Track. ETAs also worked fine with the Track, but waypoints of course will not be available with tracks.

    Hope this helps out others