Go button not appearing on routes created in Basecamp

Hi everyone, I'm just starting to learn how to use a GPS and I've uploaded a few routes created in Basecamp onto my Garmin Etrex 32x. The routes (and the waypoints) are visible in the route planner and they load properly onto the map, but there is no GO button for engaging turn by turn routing.

I've noticed that this happens only with routes created in Basecamp. If I create a route on the Etrex 32 itself, then I get a GO button when I choose the route.

I have a feeling there must be something obvious that I'm doing wrong, or a setting that needs to be changed in Basecamp.

I would appreciate any help on this, as I would like to be able to plan routes on the PC beforehand.

0 SUSSAMB over 1 year ago

Are you using BaseCamp to create a route or a track? If you are creating a route which routing profile are you using and are you using the same map in BaseCamp and on your Etrex?

You mention Route Planner. Have you tried using Where to, Routes instead?

0 9551653 over 1 year ago in reply to SUSSAMB

I understand your point. I'm definitely using BaseCamp to create a route, even though it actually behaves like a track.

The settings in the routing profile are for "walking", and I've also tried resetting them to default.

I have a few maps installed, all suggested here, and they are supposed to be routable: https://wiki.openstreetmap.org/wiki/OSM_Map_On_Garmin/Download

I also tried connecting the Etrex 32 and using the onboard topoactive map to create a new route but I get the same problem.

And yes, I also tried going first to "where to" and then choosing the route....

That's why I'm stuck and don't know why it's not working.

0 9551653 over 1 year ago in reply to SUSSAMB

Just wanted to add that I tried a few other things: I tried uploading the route by first exporting it as a GPX file but it still showed no GO button. Then I tried installing QmapShack and then uploaded a gpx route created on there and that did work: the GO button showed up fine. Btw exporting tracks with Basecamp works fine: they do show the GO button, so I'm thinking the problem has to do only with exporting routes with Basecamp. What else could I try?

0 SUSSAMB over 1 year ago in reply to 9551653

Are you able to post a route that doesn't behave as expected when you send it from BaseCamp to your device? You'll need to send it as a zip file as this forum doesn't allow you to attach .gpx files.

0 9551653 over 1 year ago in reply to SUSSAMB

Thanks for helping out. Here is a small route with a few waypoints I just created in Basecamp that doesn't show a GO button on my Gps.:

https://ufile.io/jflkc8tp

0 SUSSAMB over 1 year ago in reply to 9551653

Ok, downloaded that and sent it to my Etrex20, did a where to, routes. Selected it and get a Go button. So it appears to be an issue with your Etrex. Perhaps try a master reset?

0 9551653 over 1 year ago in reply to SUSSAMB

Fantastic, thank you! A master reset did the job. Not only does the GO button appear now on routes uploaded from Basecamp, but also zooming and panning while looking at a route works much faster. I have an open product support request about the slow rendering on routes, which is now resolved thanks to your help.
The master reset did not replace the updated maps or firmware and my saved routes, tracks and waypoints are all still there.

However now all the maps on the device are Enabled, perhaps that was the issue: I had disabled several of them because I read somewhere else that rendering speed would improve if you enable only the maps you are using.

Thanks again.

0 SUSSAMB over 1 year ago in reply to 9551653

Great, glad that worked

0 -CHUCK- 5 months ago in reply to SUSSAMB

This just worked for me as well, thanks for the info!

0 9551653 5 months ago in reply to 9551653

I actually would like to update my answer regarding this issue: the problem kept coming back and I got fed up of doing a master reset every time.

I ended up sending the Etrex 32x back to Garmin under warranty and got a (refurbished) replacement.

I've been using it for a year now and never had the Go button disappear. The replacement is also noticeably less sluggish at rendering.