Garmin Maps with a non-Garmin GPS - 'How To Tutorial'

[asp_777]

I want to run Garmin Topo on my laptop, preferably using Nroute as it's easy and clear to use. Works well with City Nav and shonks maps. I heard it can be done but needs some adjustments or other. Could some one point me in the right direction on how to do so? Thanks

[R_G_B]

Using MapReverseConverter to make new format Garmin Maps compatible with nRoute (and Mapsource 6.13.7)


1. Install and unlock the maps as usual.


2. Run MapReverseConverter

(a) Point it to the location of the installed maps to be converted
- for XP probably C:\Documents and Settings\All Users\Application Data\Garmin\Maps\Topo...
- for Vista probably C:\ProgramData\GARMIN\Maps\TOPO...

(b) Accept the location for the converted maps under C:\Garmin\Topo... (or similar to match the product).

(c) Be patient while it runs.

MapReverseConverter automates use of the program GMaptool on any map in the new format.
It optionally installs MapSource 6.13.7 (and POILoader, MapInstall, UnlockWizard) too.


3. After the conversion process you will have two sets of maps on your PC, original and converted.

The product should now be available in nRoute.

nRoute retains full routing capability of the product, and gives voice-assisted real-time tracking with a connected GPSr.



4. If all has worked as expected, you can remove the original files to save space.

If desired, you can see both (old and new form) Registry entries using MapSetToolkit.

To remove the originals, preferrably use the Windows Control Panel (Add-Remove Programs, Remove the relevant Garmin Map installation - this leaves the unlocked maps in the converted form and location).

You can then check (and if desired delete the 'empty' Registry entry for the deleted new format map files) using MapSetToolkit; be careful not to uninstall the wrong mapset though!


5. Newer versions of MapSource so far work with the converted (old format) maps, so upgrading MapSource remains possible.


MapReverseConverter Website:
http://www.javawa.nl/cne2009_multilang.html

MapSetToolkit Website:
http://cypherman1.googlepages.com/

Discussion also at:
http://groups.google.com/group/alt.satellite.gps.garmin/browse_thread/thread/7acca49b01ea4e16

[asp_777]

thanks for your email

[R_G_B]

Products like Topo Australia are good for on-road navigation as well as off-track hiking. Screens on hiking GPSr units like the 60Cx are a bit small for in-car use, and there is no voice assistance. nRoute helps if you can conveniently add a notebook computer for in-car use. Garmin has changed map formats (for compatibility across Mac and PC?) and no longer supports nRoute, but you can convert the new products back to the old format for use in nRoute if desired, as described in a previous post in this thread.

I was interested to use my old GPS12 to supply position data to nRoute (because it is less attractive to thieves than a 60Cx if left visible in a vehicle). It can be done as described below.

But can anyone explain why:

1. nRoute works fine with licensed map products before connection of a GPSr (as intended for route planning) and on connection of a GPSr to which the products are licensed (fair enough – the 60Cx in my case); BUT

2. nRoute disables display and routing for licensed map products when connected to a Garmin GPSr for which they are not licensed (OK, Garmin might prefer you to purchase another licence, but that seems harsh for use of an old non-mapping GPSr like the GPS12 only to supply position data); YET

3. nRoute provides full display and routing for the same licensed map products when connected to the same Garmin GPSr via a port emulator program such as GPSProxyPC with com0com??

GPSProxyPC identifies itself to nRoute as a Garmin GPSr. The map products have not been licensed to that ‘virtual’ Garmin GPSr any more than they have to the GPS12 supplying the NMEA position data.

So why does nRoute disable products on connection to a genuine Garmin GPSr, but enable them on connection to the same GPSr through GPSProxyPC as a ‘virtual’ Garmin GPSr??

-------------------------------------------------------------
You can try it yourself, using this procedure adapted from MalsingWiki www.malsingmaps.com/wiki/index.php/Using_nRoute_with_non-Garmin_bluetooth_GPS_receiver:

Using nRoute with non-Garmin GPS receiver (or a Garmin GPSr without the same maps installed)

Overall, it works like this: The GPSr communicates with your computer via a communication port (referred to as a com port or serial port) assigned by your laptop. This may already be a virtual com port if you use a serial-usb adapter to get signal from an older GPSr that provides only serial cable output into a newer notebook computer that provides only usb input. GPSProxyPC picks up this connection, then converts the signal from NMEA (an open-source GPS protocol) to GARMIN (proprietary) protocol and sends it to a virtual com port created by com0com which in turn passes the signal on to nRoute via a second virtual com port created by com0com.

STEP ONE: Download the software (You should have Garmin Mapsource and nRoute installed already)

The (open-source) software needed is:

1. GPSproxyPC ver 1.6 (note: you need GPSproxyPC not GPSproxy which is available in higher version numbers) http://sourceforge.net/projects/gpsproxy/files/gpsproxy/1.16/GPSProxyPC-1.16-Setup.exe/download

2. com0com ver 2.2 http://sourceforge.net/projects/com0com/files/com0com/2.2.1.0/com0com-2.2.1.0-i386-fre.zip/download

STEP TWO: Install GPSProxyPC

If you get an error code (like 0c0000135) first install Microsoft .NET Framework 3.0

STEP THREE: Check communication between your GPSr and PC

1. Turn on your PC and connected GPSr (via cable, bluetooth or whatever)
(e.g. for the GPS12 this involves a cable from the round Garmin plug to a serial DB-9 connector, then a serial-usb adapter if needed for your laptop).

2. Make sure all the relevant drivers for the connection are working first. This is specific to your equipment combination. You may be able to check in Windows Device Manager. A simple test is that Mapsource can find a Garmin GPSr. Any check for your particular GPSr connection is fine.

3. Set the GPSr for NMEA output
(e.g. for the GPS12, go to Setup > Interface > NMEA, NMEA 0183 2.0, 9600 baud).

STEP FOUR: Use GPSProxyPC to check com port settings

Your computer will already have assigned some com port numbers for use by things like modem or serial connections or serial-usb adapter, depending on your particular hardware.

You need to identify 2 unused com ports for com0com to work with:
(a) Open GPSProxyPC > Tools > Settings >
(b) Select “NMEA 0183”.
(c) Click on “GPS COM Port”. The Ports you see there are the ones already USED and unavailable for com0com to use. (In my case, com 1, com 3 and com 5 which has the GPS12 via the serial-usb adapter).
(d) Write down these com numbers and do not use them for com0com in the next step.

STEP FIVE: Install com0com

1. Follow the prompts to install com ports CNCA0 and CNCB0. Then use one of the methods below to give these ports names in the format (com#) that other programs recognise:

either (a) accept the offer to open the setup command prompt (or get there later via Start > All Programs > com0com > Setup Command Prompt).
In that setup command prompt you need to type (then ENTER) these 2 statements to assign com port numbers to CNCA0 and CNCB0:

change cnca0 portname=com6 <-- You can choose any (unused) number – see above.

change cncb0 portname=com7 <-- You can choose any (unused) number – see above.

or (b) skip the command prompt option and instead use the graphical setup (accessed via Start > All Programs > com0com > Setup).

In that Setup graphical window, assign the desired / unused com numbers in the boxes provided in the top of the right panel (e.g. com6 and com7 as above). Then click Apply.

2. Reboot to ensure that the new registry settings become effective.

STEP SIX: Make the settings for your system in GPSProxyPC

Open GPSProxyPC > Tools > Settings >
GPS:
GPS type: NMEA 0183
GPS COM Port: The port that your PC assigned for your GPSr (com 5 in my case)
Baud Rate: 4800 or 9600 (to match your GPSr interface setting)
Application:
Application COM Port: eg COM6 (the COM port you selected for CNCA0)
Baud Rate: 4800 or 9600 (to match your GPSr interface setting)

GPSProxyPC saves these settings between sessions.

STEP SEVEN: Make the connection to your ‘virtual’ Garmin GPSr in nRoute

Open Garmin NRoute. Go to Utilities > Select GPS > Serial Port, select the COM port you chose for CNCB0, eg COM7. (You can display the ‘virtual’ GPSr information under Utilities > Get GPS Information).

nRoute seems to remember the setting, even if it does not find it automatically on first use.

That completes the setup! IN FUTURE, just use this START UP SEQUENCE:

1. Connect your GPSr (running in NMEA interface mode) to your PC.

2. Start GPSProxyPC. On the top menu line, click “Start”. GPSProxy will automatically establish a link to your GPSr. You should see the time and incoming data changing on your GPSproxyPC screen.

3. Start nRoute. (If the GPSr is not automatically found: Utilities > Select GPS > Serial Port > COM# used for CNCB0 eg COM7).

You now have full use of your licensed Garmin autorouting products (and open-source products like NZ autorouting) through Garmin nRoute with position data from your (Garmin old non-mapping, or non-Garmin) GPSr.

[R_G_B]

Unfortunately, the problem described by our friends in Canada (www.laptopgpsworld.com/garmin-mobile-pc/2583-garmin-nroute-problem-not-all-backgound-tiles-appear-display.html) also applies in the antipodes.

All is fine in MapSource, but when the converted maps are viewed in nRoute certain blocks of colour are missing. For me it is obvious by the absence of blue areas for rivers (not narrow stream lines which appear fine) and green areas for parks. The roads are fine (just don't drive along that boat ramp without looking out of your windscreen) - but there may be associated colour problems that I have not noticed.

The same areas display just fine in nRoute from a non-converted (old format) product covering the same area (in my case, MetroGuide Australia covering the same area as the converted Topo Australia).

Looks like a tweak of some kind is needed in the conversion program, or maybe a custom color file (.TYP)?

If anyone has the motivation and time, this TYP editor (for old and new format maps) may help: http://ati.land.cz/gps/typdecomp/editor.cgi

[asp_777]

Unfortunately, the problem described by our friends in Canada (www.laptopgpsworld.com/garmin-mobile-pc/2583-garmin-nroute-problem-not-all-backgound-tiles-appear-display.html) also applies in the antipodes.

All is fine in MapSource, but when the converted maps are viewed in nRoute certain blocks of colour are missing. For me it is obvious by the absence of blue areas for rivers (not narrow stream lines which appear fine) and green areas for parks. The roads are fine (just don't drive along that boat ramp without looking out of your windscreen) - but there may be associated colour problems that I have not noticed.

The same areas display just fine in nRoute from a non-converted (old format) product covering the same area (in my case, MetroGuide Australia covering the same area as the converted Topo Australia).

Looks like a tweak of some kind is needed in the conversion program, or maybe a custom color file (.TPV)?

I noticed the same thing, and I thought it was just me!!

[R_G_B]

The problem of missing display of coloured areas (polygons) is indeed related to settings in the TYP file (or missing from that file), which are somehow handled differently by Mapsource and nRoute.

For a quick solution:

1. Back up the TYP file (e.g. I000017E.TYP) from the folder containing your converted TOPO map files, by renaming it to something that helps you to recall the original name - which you need later (e.g. I000017E.savTYP).

2. Download an alternative TYP file. Try SGJOHMAP.TYP from http://gpsmaps.jwpixs.com/index.php?option=com_remository&Itemid=35&func=select&id=1

3. Move the downloaded TYP file to the folder containing your converted TOPO map files, and rename the moved file to whatever the original TYP file in that folder was called (e.g. I000017E.TYP).

4. Optionally, remove the cached tile image files located in:
C:\Documents and Settings\YourUserName\Application Data\GARMIN\MapSource\TileCache
(otherwise things may initially look different across tiles in Mapsource).

Ta-da... rivers and parks (and lots of other coloured areas) are now displayed in nRoute.

NB: The new TYP file affects appearance in both Mapsource and nRoute (and probably also in your Garmin GPSr after re-transfer of maps), so that backed-up TYP file is your way back to previous appearance if this quick fix turns out to be 'quick and dirty'.

[asp_777]

R.G.B. You are so clever..... Works!!!!!
Thanks for that. :hatoff

[R_G_B]

Alternatively, based on information at http://www.javawa.nl/nroute.html the problem can also be fixed by deleting the reference to the problematic TYP file in the registry section for the offending (converted) product.

This gives a 'default' Garmin rendering of map elements in Mapsource and nRoute (and I am guessing also in any subsequent upload to your GPSr). Personally, I prefer the look in nRoute and Mapsource from the SGJOHMAP.TYP file as described above (nice work by Jerome Wee).

If you are comfortable to edit the registry (with the usual precautions to back up first):

Either use RegEdit:

* Navigate to HKEY_LOCAL_MACHINE \ SOFTWARE \ Garmin \ MapSource \ Families

* Select the appropriate subfolder (which is recognized by the name of the subfolder, or else the file references therein: Family_382 for TOPO Australia in this case).

* Remove the string with the name "TYP" (or point it to your preferred TYP file instead).

Or delete or redirect the TYP reference using MapSetToolkit (via MapSet>Edit).

[R_G_B]

Finally, to tidy things up (especially if you want custom TYP file settings to apply to the associated maps after transfer to your GPSr) it may be prudent to edit the TYP file to match the Family (FID) and Product (PID) codes of the associated maps. In MapSetToolkit (MapSet installed > Check Registry) you can see if there is a mis-match in these codes (as is likely with an imported TYP file made originally for another product). To make the correction, you can use the TYP file editor at http://ati.land.cz/gps/typdecomp/editor.cgi.

Just upload the TYP file to be corrected (from the converted maps directory), click Edit, change to the desired FID and PID codes near the top of screen (FID 382 and PID 1 in our example), scroll down the screen to download the edited TYP file, and save it to overwrite the TYP file that you uploaded for edit. MapSetToolkit registry check can confirm that Status is OK for this TYP file.

PS: If you prefer to use newer versions of MapSource to prepare Routes, make Waypoints etc, then for compatibility with nRoute you will need to save in Version 2 (not the new default Version 3) gdb format: File > Save As > Type. The ver 2 gdb files import just fine into nRoute whereas attempted import of ver 3 will fail with an error.

[Wahroonga Farm]

Hi R_G_B,

Thanks for this great series of Tutorials. I've 'sticky'd' the thread.

[R_G_B]

If (i) you use Windows Vista and (ii) you decide after converting a product from Garmin new format (GMP_gmap) to old format (Family_img) maps to uninstall the ‘new format’ version as described above to save disk space (each version uses about the same space for map files); then (iii) you may find that MapSetToolKit crashes on attempted start.

To fix this, manually delete the directory for the uninstalled 'new format' maps under C:\ProgramData\GARMIN\Maps\. The directory will be named ProductName.gmap (e.g. Topo Australia V2.gmap), and it may contain a single configuration file (after uninstall has deleted the map files) named something like info.xml_new.

Then reboot, and all should work as expected.

-----------

If you look in Mapsource under Utilities (Manage or Unlock Maps depending on Mapsource version) you will see that Mapsource recognises the converted product as unlocked, in its new location - all good.

But it is always wise (whatever your operating system) to keep a couple of separate backup copies of your Garmin product keys and unlock codes, just in case!

PS: If nRoute gives repeated "lost satellite reception" messages when your GPSr is reporting good reception, check the battery settings in your GPSr. As noted in another thread, changing from battery saver to normal mode (with batteries in good condition) should fix this problem (whatever your operating system).

[Greg J]

Thanks very much for your assistance. With all of your help I now have nRoute working fine on a Windows 7 laptop.