This is a question that comes now and then:
My GPS model "GPS-something" is not detected by GAS why?
Troubleshooting guide:
1. Make sure your GPS is properly connected and turned on. Please note which port it is using.
2. From GAS toolbar select and press "Global Settings", in the Port settings enter the serial port your GPS is using with the proper baud rate.
3. Press now the "Test GPS connection" button, if everything is OK then a message appears saying "Connection OK"
4. If you don't get the above message and your port settings are right then most probably your GPS is not outputting NMEA 0183 sentences. Check the user manual of your GPS unit and make sure the unit is set to output NMEA 0183 sentences out.
My GPS receiver is not detected by GAS ... Why?
Re: My GPS receiver is not detected by GAS ... Why?
The problem at hand doesn't have to be connected with the GAS software at all ,but with com port problems originating in windows subsystems (I had that problem) or hardware construction of your laptop (I presume nobody takes a desktop out in the field).
This problem occurs with COM-to-USB cables and inbuilt COM ports (even those are connected under the hood of your laptop to USB line)
COM port ended up being used only for serial mouse/barcode reader interface so microsoft abandoned further implementation of drivers and protocols but on most todays laptops there are a lot of things connected through the COM resources line (touchpad, trackball, old serial HID interface and some other) at the same time. So when you try to use it as a GPS interface (and a lot of GPS systems still force that connection) you end up with more than one conflict (wild mouse movement,software not responding, BSD). You can find description of the problem on microsoft official site (and some forums) and a solution for it ,but it envolves changing the registry settings, which in general is not advisable. The other way around is to download Garmin software called SPANNER.EXE (its abandonware on Garmin site). If you have a Garmin GPS the Spanner software will do all the job for you, but even if you have other GPS manufacturer you'll get a hold of VSPSTARTUP.EXE which is a "port device enumerator" that overrides windows default settings and that part resolves the not reading the COM input part.
Using bluetooth, or if you have a standard usb output on the GPS is much nicer. Where is the problem then? Sometimes the port numbers for those end up >20. Most of the software that I used allowed me to pick up input port number <16. Well, this one you can resolve easilly. Just download a small program called Xport127 availlable at Sourceforge and it lets you redirect any COM port number to any COM port number you want.
While trying to make things work you might want to fallback on the Hyperterminal option to connect to the port you are using and view the incoming nmea0183 strings as they apear on the screen (if everything is OK). It can even be used if you plan to do something else with the string but need to know how it looks.
If you have trouble finding Spanner or Xport127 and have more to ask, PM or leave a reply.
Hope this helps!
This problem occurs with COM-to-USB cables and inbuilt COM ports (even those are connected under the hood of your laptop to USB line)
COM port ended up being used only for serial mouse/barcode reader interface so microsoft abandoned further implementation of drivers and protocols but on most todays laptops there are a lot of things connected through the COM resources line (touchpad, trackball, old serial HID interface and some other) at the same time. So when you try to use it as a GPS interface (and a lot of GPS systems still force that connection) you end up with more than one conflict (wild mouse movement,software not responding, BSD). You can find description of the problem on microsoft official site (and some forums) and a solution for it ,but it envolves changing the registry settings, which in general is not advisable. The other way around is to download Garmin software called SPANNER.EXE (its abandonware on Garmin site). If you have a Garmin GPS the Spanner software will do all the job for you, but even if you have other GPS manufacturer you'll get a hold of VSPSTARTUP.EXE which is a "port device enumerator" that overrides windows default settings and that part resolves the not reading the COM input part.
Using bluetooth, or if you have a standard usb output on the GPS is much nicer. Where is the problem then? Sometimes the port numbers for those end up >20. Most of the software that I used allowed me to pick up input port number <16. Well, this one you can resolve easilly. Just download a small program called Xport127 availlable at Sourceforge and it lets you redirect any COM port number to any COM port number you want.
While trying to make things work you might want to fallback on the Hyperterminal option to connect to the port you are using and view the incoming nmea0183 strings as they apear on the screen (if everything is OK). It can even be used if you plan to do something else with the string but need to know how it looks.
If you have trouble finding Spanner or Xport127 and have more to ask, PM or leave a reply.
Hope this helps!
"If the only tool you have is a hammer, you will see every problem as a nail."
Re: My GPS receiver is not detected by GAS ... Why?
Excellent explanation on the many problems the legacy COM ports can bring. There are however a couple of things that must be mentioned to make the list complete:
1. If using Vista make sure that you have Administrator privileges. And, no, it is not enough to be logged in as an administrator because of the new UAC or User Account Control in vista. I had problems in my laptop not allowing traffic from the Bluetooth receiver. I had to turn off the UAC in order to get the thing to work. To do that, in the start menu select control panel, there user accounts, and then turn User Account Control on or off.
2. This might sound like trivia, but sometimes it happens, two applications cannot access the same port simultaneously. Make sure that no other software is accessing your port while trying to read from it.
In GAS there's support up to port number 144, so it shouldn't be a problem if you have a high port number on your device. Well, below 144
!
We are trying to implement the genuine USB GPS, that is without virtual com ports, but except for a few models from Garmin it is very hard to find documentation for the drivers.
1. If using Vista make sure that you have Administrator privileges. And, no, it is not enough to be logged in as an administrator because of the new UAC or User Account Control in vista. I had problems in my laptop not allowing traffic from the Bluetooth receiver. I had to turn off the UAC in order to get the thing to work. To do that, in the start menu select control panel, there user accounts, and then turn User Account Control on or off.
2. This might sound like trivia, but sometimes it happens, two applications cannot access the same port simultaneously. Make sure that no other software is accessing your port while trying to read from it.
In GAS there's support up to port number 144, so it shouldn't be a problem if you have a high port number on your device. Well, below 144
!We are trying to implement the genuine USB GPS, that is without virtual com ports, but except for a few models from Garmin it is very hard to find documentation for the drivers.
Re: My GPS receiver is not detected by GAS ... Why?
Good luck with that, the ones i've tried don't work.GeoAdmin wrote:
We are trying to implement the genuine USB GPS, that is without virtual com ports, but except for a few models from Garmin it is very hard to find documentation for the drivers.
Miguel
Re: My GPS receiver is not detected by GAS ... Why?
Hello,
I do realize this thread is over 6 years old but was hoping some parts of it was still usable since our new computer fails to detect the GPS device (Garmin Oregon 650)
Firstly SPANNER was/is discontinued already 6 years ago, nowadays it's even blocking installation on win 7 machines. Secondly VSPSTARTUP is also discontinued.
I did find an old copy of Xport127 although it also failed to redirect the usb signal in a format that was usable in GAS_XP.
The NMEA 0183 output clearly works on the old computer we are running so that is not the issue in this case (we need a replacement computer since battery time and life of the old one is... well over)
I have followed the steps outlined here and i am still stuck, will keep this post as a "lessons learned" for future reference and will include a solution post once the problem is solved.
Followup: http://gpsgate.com/products/gpsgate_client
Did the trick it emulates the comport so GAS_XP can reach the Garmin devices, it also supports several other brands, but this was the way i solved the problem!
I do realize this thread is over 6 years old but was hoping some parts of it was still usable since our new computer fails to detect the GPS device (Garmin Oregon 650)
Firstly SPANNER was/is discontinued already 6 years ago, nowadays it's even blocking installation on win 7 machines. Secondly VSPSTARTUP is also discontinued.
I did find an old copy of Xport127 although it also failed to redirect the usb signal in a format that was usable in GAS_XP.
The NMEA 0183 output clearly works on the old computer we are running so that is not the issue in this case (we need a replacement computer since battery time and life of the old one is... well over)
I have followed the steps outlined here and i am still stuck, will keep this post as a "lessons learned" for future reference and will include a solution post once the problem is solved.
Followup: http://gpsgate.com/products/gpsgate_client
Did the trick it emulates the comport so GAS_XP can reach the Garmin devices, it also supports several other brands, but this was the way i solved the problem!