Back to Floodgap Department of Hacking
Some of the tips and suggestions offered here are broadly applicable to the RM360's siblings, the RM300, RM700, RM760, RM800 and RM860. However, look at the manual first if you're not sure.
Done your own hacking on the RM360? Have other suggestions or tips you've figured out? Send them to me at ckaiser@floodgap.com. Do not send me E-mail asking for firmware or updates -- I don't have any updates, and I am unwilling to risk legal action by offering copies of the current firmware. Any such requests will be ignored. Nothing personal.
This site was last updated 31 January 2008, when I added new information on the internal memory contents, analysis of the formatting process, information on the "mute 360" problem, and noted that the product is now discontinued.
Here is an indepth review from gpsinformation.net.
The RoadMate 360 was discontinued in January 2008 and is listed as a
legacy
product.
So far, my biggest trip was along US Highway 6 in 2006, the longest continuous highway in America stretching from the Sierra Nevada mountains in Bishop, CA all the way to the tip of Cape Cod in Provincetown, MA (3,205 miles). The RM360 performed admirably from sea to shining sea, plus up to Maine, down the Appalachians to Georgia, and back more or less along old US Highway 80 (represented by modern US 80, I-20, I-10 and I-8) to Southern California for a total trip mileage of 9,622 miles. Not bad for a couple of hundred bucks. The picture on the left is the RM360, myself, my Nikon and my Saturn near Mount Wheeler on US 6 a few miles or so from the Nevada-Utah border.
I also make regular trips to the California Bay Area, and am notorious for my US Highway 395 research (Hesperia, CA to the Canadian border), so you can imagine how much of a workout the unit gets.
Thus, when other people tell you this, that or the other thing about a particular unit, be sure to ask those of us who literally drive across the country and back which ones they prefer. That's the mark of a real road test.
In addition, the limits of GPS/WAAS can be overcome with good software and this is where the RM360 particularly stood out. To stress-test it after I bought it, I took it up and down a local frontage road next to one of the local Interstates that was probably five or six feet from the freeway shoulder at its narrowest. The RM360's lock-on-road algorithm ensured that it never wavered. In fact, it took the combination of passing under a bridge near an on-ramp to the freeway into a recently realigned section of road for the lock-on to flop to the freeway, it only did this about half the time, and it recorrected itself within seconds. If I had a route pending, it never recalculated it until it was sure the road had changed.
In addition to this promising maiden run, across the entire country it
provided flawlessly accurate coordinates and road routings and navigated me
effortlessly from the main road to hotels, gas stations and friends and
family's addresses all as advertised. The only place it had any trouble keeping
a lock was in some of the densely forested areas of Connecticut and California
(the Redwood Highway was somewhat back and forth) and obviously
in long tunnels, but can you blame it?
Look at the screenshot to the right for an example of the compass, coordinate and exit information, taken on my namesake road (an old alignment of the now-defunct US 466) off modern CA 58 between Tehachapi and Mojave in the California desert.
Some user opinions of the unit have panned it for not having particular streets in its database. This is invariably incorrect; you just have to be exacting about spelling, spaces and (where occurring) directional prefixes. For example, it does distinguish between Washington St and E Washington St (a real life example). Also, people run street names together, or add spaces where there aren't any. This is unfortunately not very helpful when one doesn't know the area and prevailing signage is actually wrong (something I personally experienced), but I hardly think this is the maps' fault. It is also mitigated by having a database of cities for streets, and a "smart entry" feature which minimizes the amount of data entry and thus potential mistakes by matching partial names for you. I might also point out that during the entire trip (a month and 9,622 total miles), it happened exactly twice, I was able to figure out what happened, and so far it has not happened since.
In Canada, the maps are adequate but not as good as in the States. While most roads are marked, some of the signed side roads in British Columbia, for example, did not appear (and those that did appear did not always appear with their given name). This is obviously a NAVTEQ fault, not a Thales-Magellan fault, but it is worth keeping in mind if you are routing to obscure destinations in our neighbour up north.
The original firmware version was 1.76. An update to 1.81 is available.
Although I will definitely not say that the RM360 will satisfy
everyone, the point of this page is not only to advocate it, but to also
show some ways that you can get more out of it. With that information and
a good understanding of what GPS can do for you, the motorist, I think you
will come to the same conclusion I did that the RM360 is a sweet-spot in
bang for the buck.