This page is summarizes some notes and ideas about navigation, in particular using GPS. Most of it is related to my own experience and to the instrumentation I use (at present a Garmin unit).
I like maps. Paper maps.
I have been successfully navigating with paper maps for more than 20 years and they are still my primary and preferred means to plan a trip. While I have been "playing around" with various GPS receivers (GPSr) in the past, it was only in 2006 that I acquired such a unit with the accompanying map software.
For me, a GPSr does not replace the map. A GPSr does not give you the "big picture" and it cannot match the flexibility of a plain old paper map. During a ride, I still keep a map at hand, since I like to have some information about the region that I'm riding through - e.g. topography ... and in addition, I simply like the touch and feel of paper :-)
However, a GPS does one particular thing that no map can do: It tells you where you are. It locates you on the map.
While this may not be important on well-marked roads or in areas that you are familar with, it can become important in completely unknown area, an unknown city, or at night. A GPSr with a "moving map" display gives you a very good idea of where you are, and whether or not you are approaching e.g. an intersection. In addition, it gives you the "bread crumb" trail of where you have been. Add to this features such as the calculation of the estimated time of arrival, which can be very useful - think catching the ferry.
Originally, I was looking for a GPSr mainly since I wanted to be able to re-trace my way after a nice trip. The use of the GPSr as a "real" navigational aid was intended only for particular occasions - either when I could not use the map easily (at night or in a downpour), or when I needed to get to a certain address in an unknown city. Yet .. this has changed quickly since I have maps that support routing: I use it frequently -not to say "almost always" - for navigation, even if I have thoroughly planned the trip before. More on this below.
In spring 2006, I acquired a second-hand Garmin GPSmap 60CS. It is a compact, lightweight instrument, roughly the size of an old cell phone. Since it is not dedicated for automotive use but a true "handheld", I frequently use it for hiking and sometimes also on the bicycle. A review of this instrument can be found e.g. at gpsinformation.us.
In 2006, Garmin replaced the 60CS by the 60CSx series; the main differences on the hardware side are the use of generic MicroSD storage cards, a more sensible receiver and the possibility to power the instrument over USB. I acquired such a receiver, a GPSmap 60Cx, in 2010; the 60CS was sold.
What I like very much is the hardware ... the instrument is compact, pretty much water- and dustproof and has an excellent transreflective display: The brighter the sunshine, the better it is readable! Battery life is reasonable; if the instrument is powered from a pair of rechargable AA batteries, lifetime is at least 12 h (as long as you don't use the backlight, or the compass on the "S" models).
The things that I dislike on the 60 series all refer to the software. In particular the routing is ... well, "special": Routes are always recalculated, i.e. you cannot just download a route into the GPSr and follow it. The Garmin 60 will always perform a recalculation when you start navigating a route. This may cause large deviations between the two calculations; more on this below.
Switching from the GPSmap 60CS to the GPSmap 60Cx, I noted a few points:
To install the GPSmap 60 series on my motorcycles, I obtained a GPS holder from bikertech.de. The device is made from black plastic (I presume this is a thermoplastic PVC like "Trovidur") and is a very simple, lightweight construction. Basically, the GPSr sits in a plastic shell and is held in place with another plastic strip that pulls the metal loop on the back of the instrument into the shell. The shell itself sits on four rubber dampers (10×15 mm, M4 thread and bolt). It sounds simple, it is simple - and it works fine! Manufacturing quality could still be improved a bit, since the four rubber dampers of my unit are not perfectly aligned but mounted under tension, thus not providing the best vibration absorption possible.
On the R80GS, this "shell" is simply attached to a flat piece of plastic that is clamped to the 12-mm cross tube of the handlebar. It is mounted on the left side of the bar, easily reachable with the left hand and at the same eye level as the other instruments. The only thing I needed to change was to relocate the LED Voltmeter a bit, since it would have been hidden by the GPSr.
For the R100TIC, finding a suitable place and holder was more difficult. Mounting the GPSr into the fairing puts it too far from the rider, so the handlebar turned out to be the preferred place again. The exact position has to be chosen carefully, since you don't want the GPSr to collide with the windshield or other things. Based on the device described above, I made a simple holder from some clear plastic and brought it into shape with a hot-air gun. While this item survived several thousand km without any problems, it nevertheless became brittle over time. Thus, I constructed the replacement from thermoplastic PVC (and at the same time, I copied the holder for the GPSr ;-). The key point for the construction is that the holder has to be rather stiff; if the material is too thin, the vibrations of the Boxer engine would cause it to wiggle with a rather big amplitude.
The resulting mounting position is just perfect: comfortable to reach with the left hand and sufficiently high above the speedometer so that it would never be hidden by the tankbag.
For the K100LT, the position was similar to that on the RT, but lower to the handlebar. Pictures to come.
Most (older) Garmin GPS receivers use a special, round 4-pole plug to connect to the computer and to provide external power to the instrument. This connector is a proprietary design that is not available in standard electronic shops, but it can be obtained from pfranc.com ... and as a side note: since January 2009, I am the pfranc contact for Switzerland :-)
Since I change between two motorcycles, I built a short two-wire cable with this connector on one end, and an "AMP Superseal" connector at the other (the latter are connectors for automotive applications that are completely waterproof - thanks to Stephan H. for the hint). On both motorcycles I installed two cables that lead from the auxiliary plug (i.e. a fused line) into the cockpit, ending in the complementary Superseal connector. To swap bikes, I just pull the plug open and move the GPSr with its power cable to the other bike.
(Curious about the black cylinder? See below ;-)
Why not avoid the hassle with an external cable and simply use batteries? Well, in terms of current consumption this is possible - the 60CS and 60Cx can run about 12 h on a pair of AA-sized accus -, but vibrations will cause damage. The problem are not the occasional "bumps" due to the road, but the high-frequency vibrations caused by the engine. This picture shows a pair of AA accus that were brandnew and that have been used for about 3 h in the 60CS: The insulation is already worn off in a few places. Reportedly, prolonged use on the motorcycle with batteries inserted will also cause the contact springs to wear out. I have now added a strip of soft plastic foam inside the cover of the battery compartment, but I avoid using the GPSr with batteries on the motorcycle.
The black cylinder that is visible in the picture above holds a simple but effective circuit to avoid a reset of the GPS when the engine is started. This reset seems to occur on all BMW airheads that are equipped with Valeo starters and also on the Honda Africa Twin.
If you observe the same kind of GPS receiver reset on your motorcycle, feel free to drop me a mail: I offer these units for sale.
The circuit works with all Garmin GPS of the "60" series and will certainly also work with all GPSr that have similar electrical data. As an example, a customer with a Honda Africa Twin used it successfully with a Garmin GPS12; the circuit was simply installed in the line between the original plug (containing a voltage reducer/regulator) and the GPS receiver.
In 2016, my GPSr started to shut down all by itself when running on batteries.
The problem occurs only when the unit runs on batteries, not when powered through the Garmin connector or USB. The display just fades out, like a power failure.
It turned out that this is actually a power failure. The problem is well-known and is related to the internal battery connectors; these are two clips that press against contact pads on the main PCB. Over time, these connectors seem to lose their elasticity.
The fix is to solder to short wires between the battery clips and their counterparts on the main PCB. I did this in July 2016 but did not take pictures ;-) The procedure is straightforward and has been described elsewhere; you may want to do a web search for "gpsmap 60cx battery failure" or similar terms.
Most of these apply to the whole 60 series:
A non-documented feature of the GPSmap series is the fact that you can create (and change) routes with a "rubberband" function on the GPSr, just like in MapSource.
To create a new route from scratch:
To change an existing route:
The standard software for Garmin GPS units is Garmin MapSource. It is basically a software "framework" that is used to plan routes, to upload data (maps, routes, waypoints etc.) to the GPS receiver and to retrieve track, waypoint and route information from the GPSR.
Over the years, Garmin has distributed a number of different map sets for use with MapSource. Some of these have routing capability, some not; some can be used "as is", some require an unlock code (Garmin has a rather restrictive software license policy: Albeit you buy the maps separately, you can not use them with any GPS you want - instead, the use is tied to the serial number of the individual GPS unit, which is somehow coded in said unlock code). According to my knowledge, the status is as follows (early 2008):
Caveat: Garmin publishes regular updates for MapSource. If you are running MapSource using an old version of Microsoft Windows (such as I do), note that versions from 6.11.6 onwards do no longer run on Windows 98, Windows ME and Windows NT.
For me, the biggest disadvantage of Garmins MapSource software is that it is only available for Microsoft Windows platforms. Even in early 2008, no support for Linux was announced and even support for Mac OSX was still not available. As long as you stay with Garmin GPSr, there are no alternatives in sight since Garmin uses a proprietary protocol to upload map data into the GPSr (however, downloading tracks, waypoint and route data can be achieved with Linux-based software and using the USB port).
In 2008, I switched from a dual-boot system (Linux and Windows) to the use of Virtualisation. This allows me to run Garmin MapSource in a Microsoft Windows environment, which itself runs in a virtual machine on the Linux host. In other words, Windows in a window :-) For details, see the description on the Linux and GPS software page.
In the past, I used to prepare a trip using paper maps. I then transcribed my route on a sheet of paper that was put in the tank bag, alongside with the map of the current region. I have 20+ years of positive experience navigating that way. It works very well, but is also means that you need to stop to turn the map (and/or the route sheet) around and that you are very dependent on the weather and lighting conditions.
Today, I continue to prepare a trip using plain paper maps. I can look at them for hours! I then "transcribe" my route into the mapping software of the GPS unit and instead of the routing instructions on paper I upload that route into the GPSr. The GPSr's turn-by-turn directions will then replace the paper sheet and allow to follow a planned route without being distracted too much from the traffic. An additional advantage of this is that the electronic maps include all the detail to guide me through unknown cities, or on small country roads that are only found on 50k maps. And since it is waterproof and backlit I don't care much about the weather ;-)
As mentioned above, I do most of the route planning on the map and I also try to use MapSource in the simplest possible manner (i.e. spend as few time as possible with it). Basically, I follow the advice that was given in this thread at the ukgser forum (posting #10):
Yet another route planner is available within Google Maps. Just type "from:Bern to:Lausanne" in the address bar and the software will calculate and display a route. You can then drag-and drop points along the route (if you have a fast Internet connection and wait a few seconds, the display will even reflect the changes on-the-fly). Exporting to GPX can be performed using a script available at www.elsewhere.org.
One particular "feature" of the GPSmap series that causes a surprise for many users is that routes, once they are uploaded into the GPSr, are always recalculated. As mentioned above, it does not download the exact route you planned; instead it considers the route you composed on the computer merely as a sequence of waypoints and the 60CS always calculates its own route. Garmin's official explanation and workaround: "Mapsource and your unit use different algorithms so the GPS will have to recalculate the route once transferred. The PC has a far greater processing capability than the unit, which is the reason for this."
Reproducing this behaviour in MapSource is not a trivial task, in particular since the calculation options between MapSource and the GPSr do not match. As an example, MapSource has a "slider" to balance between minor and major roads that is absent in the 60CS and in turn the latter has a setting "Calculation Method" with "Quickest, Quick, Better, Best" which is not available in the former. The differences in the calculations are not always obvious and only show up once you upload and simulate the route ... which is pretty time-consuming. Garmin's official workaround: "If you create waypoints in your route at certain locations where you want to go, when the GPS recalculates the route it will still go to these waypoints. This means the majority of your route is where you want to go on your journey."
"The majority of your route is where you want to go on your journey." Hmmm. Considering the price that is asked for such a system, I'm not sure if I enjoy that meaning ;-)
Indeed my current workaround is to leave the routing options in MapSource at the default values and merely adjust the key options (e.g. avoiding Toll Roads, but allow Unpaved Roads). Then, when I plan a route using MapSource I manually define waypoints after important intersections or locations and let MapSource recalculate the route. If this fits my intended trip, I save and download the route to the GPSr and re-run a simulation there. Unfortunately this is quite a time-consuming process, so if you know a sure way to make the route calculation in MapSource behave exactly like the GPSmap 60 does, I'd be glad to hear about it ;-)
Another doubtful point is the definition of "highway". Most (European) users would probably expect that highway is equivalent to "Autobahn", but as of fall 2006, MapSource's "highway" includes in Germany both Autobahn and Bundesstrasse. While the latter is certainly intended to be a "fast road", it would be preferable to separate clearly between these both types - as an example, when I'm on the motorcycle I don't mind taking a Bundesstrasse, but I certainly do not want to be routed over the Autobahn.
The third caveat is the choice of the routing options. Besides some "fine-tuning" (such as avoiding toll roads, U-Turns or unpaved roads), the 60CS basically provides two options, "fastest" and "shortest". The "fastest" way will obviously favour major roads and highways, but may easily (!) lead to a much longer distance. On the other hand, the "shortest" way will literally be the most direct way to the destination. This sounds good, but may lead to some surprises; as an example, instead of taking the main road through a village it may direct you through some industrial zone or residential area, even if it takes much longer (in time) than the main road. This can be a lot of fun if you have the time and leisure ("now, lead the the shortest way home"), but it can also be annoying. For most of my purposes, the "ideal" routing behaviour is indeed somewhere in between these two.
Conclusion: Whenever you recalculate the route, check the result carefully. Trusting the GPSr blindly may lead to huge detours.
The 60CS has "only" 56 MB of memory. Depending on the map sets you use, this is enough for most applications, but it can get a bit tight on trips that spread over large geographical areas, or that include many large cities.
In such cases, it is still possible to have larger areas available. It is sufficient to prepare the map sets at home,
store them as a separate 56-MB-file and upload them into the GPSr when you need them. This requires a small laptop,
your unlock code and the software sendmap (available for Linux and MS Windows;
make sure you get at least
sendmap20 rev. 3.5):
ext3fs-formatted sticks will not work).
When you're on the way and want to load another map set, simply connect the GPSr to the PC and run the corresponding .exe file. The map set will be uploaded, the GPSr will perform its usual reset and voilà ;-)
Edit: For some reason that I do not know, the address search does not work with mapsets that are uploaded this way. All the routing capabilities work, though.
Please note that this is only possible for maps. If you want to upload routes or waypoints, you have to do this separately.
During a trip, I use the GPSr as "data logger". The instrument will record position and altitude (and some more data, such as speed, heading, time of the day) while it is running and I can look at these data later on. This allows me not only to re-trace my path, but also to know e.g. the altitude profile, or to identify where a particular photo was taken (using the timestamp) - geotagging!
The GPSmap 60CS, like most Garmin GPSr, has the particular "feature" that it can record quite a number of track points, but when the track is saved it is reduced to 500 points and all information except coordinates and altitude is lost. Thus, if you want to preserve timestamps and speed information on the 60CS, make sure you download the whole "active log" from the GPSr from time to time. I have successfully used a Palm T2 and a dedicated serial cable for this purpose. The software used was GPilotS.
Storage space is no longer an issue on the 60Cx, since this GPSr can be configured to store its - full! - track logs on the microSD card.