New eTrex 30x - A Few Issues

Former Member over 7 years ago

Hello everyone,

A great forum.

As mentioned in the title, I have a new eTrex 30x. A few questions for you experts:

1. I generally create routes in BaseCamp and transfer the GPX file to the handheld (if more than 250 waypoints, I use tracks). When I look at the route map on my eTrex, I (like numerous others) see a screen full of blue pins. I have tried creating a custom magenta rectangular 32x32 pixel bmp (named "Pin, Blue.bmp") as this seemed to work for others on their units - no luck. I changed the registry keys for both Via Symbols and Symbols to code 45,0,0,0 (City, Small)...rebooted, created a new route on BaseCamp, transferred it and...blue pins. I changed the bmp to be 32x32 transparent..closed BaseCamp, restarted, created a new route, transferred it and...more blue pins. Am rapidly approaching witt's end. Has anyone successfully tricked an eTrex 30x? Garmin suggested that I manually change each waypoint...a very tedious manual effort.

2. I recently purchased the Talkytoaster British Isles routable TT:50 map and easily created daily hikes for the West Highland Way (next May). One aspect confuses me: An example leg measured 7.2 miles on BaseCamp using the routable feature (start, end and a few corrective points). When I transferred the route to my eTrex, it shows as only 6.4 miles. Yet, when I create a track of that same leg in BaseCamp, it appears as a 7.2 mile track on my eTrex. I suspect that the route on the GPS is "as the crow flies" between the points that transferred to the GPS (hard to tell on the small screen). Hence, it would be shorter. Has anyone ever experienced this and, if so, is there a work-around?

Note: I shy away from using tracks as I do enjoy the comfort of an occasional "beep" when I walk by a waypoint plus I have read that the "distance to destination" does not work for tracks? (Edit - not true. I just tested a track by my home and the eTrex did indeed provide "distance to destination"). I understand that I could add proximity alarms to address the "beep" issue but that too is a tedious manual effort.

3. I have not loaded the TT:50 map yet on my eTrex (still using the "free" standard version). TalkyToast offers a "routable" and "non-routable" version. is there any reason why I should choose one over the other? As I said previously, I have never created a route on my GPS...only in BaseCamp.

All that said, I really like my eTrex...have done several hikes with it measuring ascent vs descent for loop hikes and the final readings are within 1-2 feet (which I thought was pretty good for a 1,500 foot peak ascent/descent).

Sorry for the length of this post.

Appreciate your thoughts.

John (aka Snakebit12)

0 SUSSAMB over 7 years ago

1. Custom symbols should work, are you following the rules here https://support.garmin.com/faqSearch...CW5Tx3HyfJ3eQ6

2. If your route is being created as a straight line (you should be able to tell by zooming in) check your settings, you'll probably find you haven't selected a routeable profile or your Guidance method is set to Off Road, if you want it to follow a routeable map you need to select On road.

Personally I create all my walking routes using direct activity, that way I know it won't be altered by my Etrex. For that reason I don't choose a routeable map, since if I let my Etrex calculate the route it would only do so via trails etc that the map has as 'routeable', and almost invariably that's not the way I would wish to go.

0 Former Member over 7 years ago

1. Custom symbols should work, are you following the rules here https://support.garmin.com/faqSearch...CW5Tx3HyfJ3eQ6

I had not followed the rules - did not set the color to RGB = 255,0,255. So, went back into paint, created a rectangle with transparent selection checked, created a custom magenta color, painted the box, reduced the size to 32x32 and saved it on my eTrex as a 24-bit Windows style bitmap. Blue pins. Do you know if this bitmap image is somewhere I can find and download?

2. If your route is being created as a straight line (you should be able to tell by zooming in) check your settings, you'll probably find you haven't selected a routeable profile or your Guidance method is set to Off Road, if you want it to follow a routeable map you need to select On road..

The profile is set up as "Recreational" which I assume is correct?

My routing settings are factory set - missed that step in setup. If you will humor me:

Guidance Method - currently "Off Road"; I have two "On Road" choices - for Time or for Distance. Which would be best for handling transfers generated by BaseCamp routable maps?
Calculate Routes for - currently "Car/Motorcycle". I assume "Pedestrian"?
Lock on Road - currently "No" - ??
Off Road Transitions - currently "Auto" - ??
Avoidance Setup - currently "Road Features" - ??

Personally I create all my walking routes using direct activity, that way I know it won't be altered by my Etrex. For that reason I don't choose a routeable map, since if I let my Etrex calculate the route it would only do so via trails etc that the map has as 'routeable', and almost invariably that's not the way I would wish to go.

Since I will likely stick with my present technique, I will start with Talkytoaster's routable version and see what happens.

0 SUSSAMB over 7 years ago

How you set up a routing profile is really up to you, but if you want to follow routeable maps the important bit is that guidance method is set for on road. Again which one is best is down to personal preferences. It's why, as I mentioned, I don't use anything other than direct profile for my walking routes.

Off road transitions won't apply if you choose 'on road'. It dictates how close you have to get to a viapoint before you're guided to the next if you have off road selected.

I'll dig out a relevant custom symbol shortly. (now attached)

0 Former Member over 7 years ago

Thank you so much.

I wish I could tell you that the custom symbol worked...but, alas, it did not.

I corrected the routing settings and loaded Talkytoast's routable TT:50 map...my 7.2 mile hike still appeared as 6.4 miles (just as with the rountable standard map). Replaced that map with the non-routable one and it jumped to 16.1 miles. Yikes. The screen scrolls too slowly to figure out what the GPS was doing so I gave up.

I'll revert back to the routable TT:50 version and become a "track guy" as far as the UK is concerned. Not that big of a deal.

I appreciate your time and thoughts on this.

0 SUSSAMB over 7 years ago

If the symbol didn't work you're doing something wrong. Note it's called Pin, Blue. It will only affect waypoints sent to your Etrex by BaseCamp that use the blue pins. If your route in BaseCamp shows blue flags (which is the norm) add the same symbol to your Etrex and call it Flag, Blue

As for looking at routes, once you've created them on your Etrex look at them using BaseCamp ... and adjust as necessary. I rarely create or look at routes directly on my Etrex unless I'm using it to navigate.

0 Former Member over 7 years ago

If the symbol didn't work you're doing something wrong. Note it's called Pin, Blue. It will only affect waypoints sent to your Etrex by BaseCamp that use the blue pins. If your route in BaseCamp shows blue flags (which is the norm) add the same symbol to your Etrex and call it Flag, Blue

Strangely enough, I was thinking about that exact point this morning (I really need to get a life). Is the theory is that the GPS receives symbols - and if it cannot find that symbol in its inventory of standard and custom symbols - it defaults to a blue pin?

I think that this "Pin, blue" custom symbol works for those of you who create your waypoints in the field...and create blue pin symbols. I create my waypoints on a computer screen and blue pins are not an option in BaseCamp.

In BaseCamp, I use a symbol that BaseCamp calls calls "waypoint" - when you open a waypoint in BaseCamp to change the symbol, It is the black dot in the "Marker" section.

Further, I loaded a GPX file into Notepad and the code shows:

<wpt lat="38.371037263423204" lon="-78.516690563410521">
<time>2017-02-15T20:12:05Z</time>
<name>2953 ft height13</name>
<cmt>2953 ft height</cmt>
<desc>2953 ft height</desc>
<sym>Waypoint</sym>
<type>user</type>
<extensions>
<gpxx:WaypointExtension>
<gpxx:DisplayMode>SymbolOnly</gpxx:DisplayMode>
</gpxx:WaypointExtension>
<wptx1:WaypointExtension>
<wptx1:DisplayMode>SymbolOnly</wptx1:DisplayMode>
</wptx1:WaypointExtension>
<ctx:CreationTimeExtension>
<ctx:CreationTime>2017-02-15T20:12:05Z</ctx:CreationTime>
</ctx:CreationTimeExtension>
</extensions>
</wpt>

I have bolded what I think is important - BaseCamp is passing a symbol called "waypoint" (not "Pin, Blue"). "Waypoint" is not a symbol that I can find on my eTrex.

So...what if I renamed "Pin, Blue.bmp" to "Waypoint.bmp"?

0 SUSSAMB over 7 years ago

How does it display in BaseCamp? Whatever it is you need the appropriately named symbol in CustomSymbols on your device. In BaseCamp I tend to use the Small City symbol in my routes, so I also have a Small City custom symbol.

0 Former Member over 7 years ago

I arrived at an acceptable resolution. I was able to identify which symbols in BaseCamp pass over cleanly to my eTrex. Note: It seems silly that Garmin would not ensure that ALL waypoints from their software work on their GPS units?

Anyway, I created a route in BaseCamp (using only those common symbols) and put 100 ft proximity warnings on all of the critical waypoints. Then, I created a track from the route and passed the track and the waypoints (but not the route) over to my eTrex.

Hiked today and it worked like a champ. No screen full of blue pins, a clear line to follow and beeps that warned me about upcoming critical waypoints. Met my requirements.

Was a little disappointing that the ascent and descent for the entire hike were off 50 feet (it was a loop hike) but with a 2,000 ft elevation gain/loss, that is probably within the margin of error.

Thanks again for your help.