Garmin, Magellan, & Lowrance/Eagle GPS Interface Software for the PC
by
Ron Henderson (email)
Using G7ToWin with Windows 7, Vista, XP, Win9X/Me, Linux
Obsolete: G7To(W)
G7ToWin |
|
The Changes File contains the 200 most recent lines of the changes.txt file. The full changes.txt file is available in each of the .zip files. |
G7ToWin Standard Latest build:G7ToWin (with helpfile) G7ToWin (without helpfile) G7ToWinHelp Version A.00.110i - last updated Sept 26, 2009 G7ToWin 64 bit Latest build:G7ToWin64 As of October 1, 2009, I will no longer routinely compile a version without USB. G7ToWin Without USB. See missing module. Latest build September 8, 2010:G7ToWin without USB |
SynopsisG7ToWin:
|
IGC Track File SupportG7ToWin and G7ToCE can create IGC track files with and without a 'G' validation record. See the G7ToWin help file for more information. The ability to validate the data in an IGC track file requires a properly formed 'G' security record be inserted into the file. The format and contents of this record is largely left up to the creator. The creator must also provide a means to validate the accuracy of the file based upon the contents of the 'G' security record. Two methods are mandated, one for use in a standard DOS environment and one in a Windows environment. Both versions are provided. The following two programs are for use with IGC track files created using G7ToWin version A.00.186 November 15, 2004 and later or for those created by G7ToCE version 1.10 and later. MSDOS Version Pre MD5 Version -- if your G record is less than 9 characters long, including the G, it was written with a version of G7ToWin prior to A.00.186 or a version of G7ToCE prior to 1.10 and must be validated with an older version of the validation program. The older version is not as secure as the later version and use of the older version should be discouraged. G7ToWin DLL for IGCShell program The freeware program IGCShell, available elsewhere--a Google search will find it--will perform validation on several igc files at one time if a DLL is provided by the manufacturer. I have made available such a DLL for G7ToWin. This DLL has not been tested thoroughly by me but others have said it works 'OK' whatever that may mean. Use it with IGCShell at your own risk. The only item in the .zip file is the DLL. See the IGCShell documentation for directions on how to use the DLL. |
G7ToCEFor the Pocket PC, H/PC 2000, H/PC 2.11 and greater.
NOTE: The version compiled April 4, 2009 will be the last version of G7ToCE that will be released. As I no longer use a Windows CE device as my PDA I have no desire to update, compile, maintain, or test new versions of G7ToCE. |
|
|
The Changes File contains the 200 most recent lines of the changes.txt file. The full changes.txt file is available in each of the .zip files. |
|
G7ToCE is a port of G7ToWin with the Pocket PC, HP/C 2000 or H/PC Pro 2.11 as the target platform. Currently G7ToCE supports most of the same items as G7ToWin with a few exceptions. For instance, USB** only GPS units (e.g. the Garmin SP2610) and Street Atlas files are not supported; most other functions are supported **USB support requires host mode and appropriate drivers for the WinCE device. Neither is readily available for the WinCE units currently on the market. If both items become available it may be possible to add support for Garmin USB-Only GPS units. Early versions of the Pocket PC code was tested by the author with the HP Jornada 568 which uses the StrongARM processor. Both the internal serial port (COM1) and a Sockets CF+ Serial I/O card as COM2 have been tested. Early versions of the H/PC 2.11 code was tested on the HP Jornada 680 which uses the SH3 processor using only the internal serial port. G7ToCE has been tested by users on other Pocket PC's utilizing the SH3 and MIPS processors and according to reports it is functional with these units. |
|
| Pocket PC G7ToCE (SH3) G7ToCE (ARM) G7ToCE (MIPS) |
Early versions of the ARM code has been tested on the HP Jornada 568 which utilizes the StrongARM processor. I do not have access to a Pocket PC utilizing the SH3 or MIPS processors therefore I have not personally tested the SH3 and MIPS versions of the code beyond the development kit's emulator. Use at your own risk. |
| H/PC
2.11 G7ToCE (SH3) G7ToCE (SH4) G7ToCE (ARM) G7ToCE (MIPS) |
Early versions of the SH3 code has been tested on the HP Jornada 680. I do not have access to any other Handheld PC therefore I have not personally tested other H/PC versions of the code beyond the development kit's emulator. Use at your own risk. |
| H/PC 2000 G7ToCE (ARM) G7ToCE (MIPS) |
I do not have access to a WinCE 2000 H/PC unit and an emulator has not been provided, therefore I have not personally tested either of these two executables. Use at your own risk. |
| Pocket PC 2002 G7ToCE ARM) |
Early versions of the ARM code has been tested on the Hewlett Packard Jornada 568 which utilizes the StrongARM processor and executes Pocket PC 2002. I do not have a PPC 2002 device for testing. Use at your own risk. |
| Pocket PC 2003 G7ToCE (ARMV4) |
Tested on the Hewlett Packard iPAQ 2215 which utilizes the ARMV4 processor and executes Pocket PC 2003. Compiled with eMbedded Tools 4.0 SP3. This version is also for the Intel XScale processor. This is the code to use for Windows Mobile 5 and Windows Mobile 6. |
| Palm PC 2.11 not supported | This operating system is a precursor of the Pocket PC OS and does not contain all of the C runtime library and therefore it is not supported by G7ToCE. |
| Asyncinit 1 Error 55 COM Port error |
This error is often the result of a keyboard driver or modem driver conflict. Try removing the offending driver. This problem has been reported by users of both iPAQ and Toshiba units. For the iPAQ units an offending keyboard driver can be disabled by accessing Start->Settings->System tab->iPAQ Keyboard and unchecking the option. There may be a similar option for the Toshiba. See the G7ToWin helpfile for more information on COM Port errors. |
G7To & G7ToW |
||
|
||
G7To is a DOS program written in a combination of Borland C++ 3.1 and Borland Turbo Assembler Version 3.1. The assembler is used for the Serial Port interrupt routines. G7To is designed to execute on a MS-DOS PC, however, the program will execute properly in a Windows Command Prompt under Windows 9X or Windows NT 4.0 or greater. If operation under MSDOS is not intended then G7ToW is recommended for use under Win 9X and Win NT/2k. G7To is a 16-bit program and therefore will NOT run under 64 bit operating systems. G7ToW is a Windows Console version of G7To written entirely in C and compiled using Microsoft Visual C++ version 6.0. G7ToW is functionally identical to G7To with one minor exception: data comm statistics are not supported. G7ToW is not usable on a MSDOS only platform, Windows 9x or Windows NT/2k is required to operate. G7ToW should be executed from a MSDOS command Window. |
||
|
||
G7To, G7ToW Last Updated August 22, 2000G7To (g7to.exe, datum file) G7ToW (g7tow.exe, datum file) G7ToW Documentation (g7tow.pdf, change history) G7To Sources -- Includes all files necessary to build the .exe files. Jack Yeazel's tutorial for G7To when used with Garmin receivers and Lowrance/Eagle receivers |
Missing Module Error |
If running on a Win95 or Win98 PC which does not support USB you may receive the following error message at startup: The G7TOWIN.EXE file is linked to missing export SETUPAPI.DLL:SetupDiGetDeviceInterfaceDetailA SetupDiGetDeviceInterfaceDetail is a procedure used by G7ToWin when setting up the USB driver to access Garmin devices. If your PC does not have a USB port then this error can occur. If you do not set the COM port to USB in the File-Configuration-General tab then you may be able to 'click OK' and safely use this version of G7ToWin but it is preferrable that the no-USB version of G7ToWin be used to avoid this error and any possible complications. If your OS will not allow a program with a missing export to continue (i.e. Windows 95) you must use the version of G7ToWin created without USB support. |
G7ToWin on Windows XP, Vista, Windows 7 |
XP G7ToWin is fully compatible with Windows XP SP1 and later. Windows 7 Preliminary testing indicates that G7ToWin operates as designed under Windows 7. Vista I have now tested G7ToWin with Vista Ultimate 64 SP1 so Vista, at least the Ultimate version with SP1, is supported. The only major issue I have discovered is that one should run G7ToWin as Administrator (using an administrator account is not sufficient, one must 'Run As Administrator') or there may be some difficulty saving a file to some locations. This is due to the way User Account Control (UAC) is implemented on Vista. If one turns off UAC (not recommended for most users) or selects 'run as administrator' then G7ToWin executes exactly the same way on Vista Ultimate 64 SP1 as it does on prior Windows versions with the following exceptions:
There are a few solutions to the 'Beep' problem. The first solution would require G7ToWin to switch to a 'Windows Themed' version of the ListView which would in turn require dropping support for those versions of Windows prior to XP. I chose not to implement this solution. If this Beep happens and is annoying (as it was to me) then there are two other solutions for this problem. They can be found in a Microsoft Knowledge Base article. The 2nd method in the article, deleting the .Current registry subkey, in addition to being performed using the Registry Editor, can also be implemented with a small registry (.reg) file. You can easily create this file using Notepad. Type or copy all of the text between the horizontal lines below (beginning with REGEDIT4 and ending with the closing bracket ']') into a blank notepad page and save it into an appropriately named file with a .reg suffix. I used "ListView_Vista_Beeps_OFF.reg" and saved it on my Desktop. Windows Vista will sometimes re-create this registry entry and the beeps will return. To execute the file double-click on that file from Windows Explorer. Please note that modifying the registry incorrectly can be harmful to your system up to and including requiring a reinstall of the system. If you chose to modify the registry you do so at your own risk. REGEDIT4 [-HKEY_CURRENT_USER\AppEvents\Schemes\Apps\.Default\CCSelect\.current] |
Actively Supported Devices |
G7ToWin actively supports the following GPS devices: Garmin: RS-232: Virtually all of the Garmin units that have the ability to communicate via a RS-232 port are supported. USB: For those Garmin units that communicate solely via the USB port the support is not as complete:
For Garmin units not falling into one of the above categories support is unknown. To my knowledge they have not been tested with G7ToWin. Working with the Garmin nüvi series The nüvi's current Waypoints, Tracks, and Routes are stored in the file Current.gpx which is created by the unit. G7ToWin should not be used to write to the file Current.gpx. After arranging your data in G7ToWin, save it as X:\Garmin\GPX\Temp.GPX and then disconnect the nüvi from the PC. Upon restarting the GPS the data in Temp.GPX will be read and merged into the file Current.gpx. Please note that the nüvi will not automatically read the routes from the Temp.GPX file, you must go into the 'My Data' menu on the GPS and tell it to read the routes from the file. You also have to do this when MapSource writes routes to the unit. GPS Display download: G7ToWin will download the display bitmap for a very small and restricted set of Garmin GPS units and LEI units. This is no longer actively supported. My reasons for dropping support are in the G7ToWin helpfile. For those who desire the ability to download the Garmin display bitmap I suggest you download Garmin's own xImage. A search of the Garmin web site will not find this program. Apparently xImage is no longer linked from the main Garmin web pages (or if it is I can't find it) but xImage can currently be found by a Google search for 'xImage Garmin'. It is unknown if Garmin will continue to provide a link to download xImage, but as it is no longer listed on the main Garmin web site it is doubtful. G7ToCE supports the same units that are supported by G7ToWin with one exception: Garmin USB units are not supported. All communications must be performed via the RS-232 port. If a GPS device is not in one of the above it is not actively supported and support for it is not anticipated. Partial support is provided for: Lowrance/Eagle, Magellan |
Partial Support |
||
March 6, 2009 The following items are partially supported. I no longer have the ability to test my code changes on these units. Therefore, while I will not remove the code for these units from G7ToWin I will no longer be improving upon it--except for rare and minimal changes. Magellan: Those units which communicate via the Thales Interface Specification 2.6 using the RS-232 port are supported. The Magellan units which use USB are not supported. Lowrance/Eagle: The units supported are those that communicate via Lowrance Protocol 1 or Protocol 2. This includes primarily the 'Map' units, i.e. Global Map Sport and earlier units. Later units, including the iFinder series, are not supported. For those LEI units supporting P1 or P2 G7ToWin will upload and download 'events' in addition to the normal waypoints, tracks, and routes. Win9X/ME: I no longer have the ability to test G7ToWin on the Operating systems Windows 95, Windows 98 and I never had the ability to test on Windows ME. If the standard version of G7ToWin is executed under some versions of Windows 9X/Me a missing module error can occur. This error can be eliminated by using the no-USB version of G7ToWin. I will continue to update and provide a link to the no-USB version of G7ToWin which should continue to run on all versions of Windows 9X and Windows ME. Due to the mechanics of the operation (compiler on a different system) the no-USB version may or may not be updated at the same time as the main code. If anyone is using Windows 9X/Me and/or a LEI GPS and has problems with the no-USB version of G7ToWin I will attempt to answer questions but any answers to questions involving Win9X or WinME will be general in nature.
|
I attempt answer all email I receive concerning G7ToWin or general GPS subjects--I don't always have the answer someone is looking for, but I will still respond to the email. If you emailed me and did not receive an answer then please check your return email address/mailbox for problems. It doesn't happen often, but to date I've had about two dozen emails that I've replied to permanently bounce. The reasons have ranged from destination mailbox full to unknown destination name. There is nothing I can do to solve an email problem which originates on the receiving end. In an effort designed keep my email address from being harvested by spammers I no longer have a 'mailto' defined on this page-- I've placed my eMail/mailing address in a zip file. If you have JavaScript enabled you can also click to send email. |
Unless otherwise stated all material on this page is Copyrighted by the materials original copyright holder or it is:
Copyright © 1997-2009 Clyde R. Henderson. All rights reserved.
Page last updated: October 11, 2011 2:44 PM PDT