Re: Low level testing of USB GPS receiver, Navibe?

In article <c8ve839cmc4646daeu209p7s45apj1u1u4@xxxxxxx>, Lars@xxxxxxxx
says...
Hi group,

Recently I bought my 4th GPS. It is a cheapo USB connected little
plastic box without any display or buttons etc. The brand is Navibe.

I use it in a Thinkpad laptop that has only USB 1.1. It comes with a
file that cretaes a virual com port by name Prolific USB-to-serial
Comm Port.
I could not get any signal at all when running it in SeaClear. Not
only would it not come up with any position, but when checking an
option in SeaClear called NMEA input monitor there is no datastream
at all. I have used SeaClear since years with a similar type GPS and I
have many times checked on that data stream.

So I took the Navibe back for a replacement. The second one seems just
as dead.

Now I wonder if there some other way to test the GPS?

I have uninstalled and reinstalled the driver, tried it on another
laptop to no avail, made sure that the GPS is in a position where it
is not obscured by anything.

Coud it be that such a GPS would only work with USB 2?


Lars
Stockholm
Visit the big ACF freeware wiki:
http://freeware.wikia.com/wiki/Main_Page

I googled Navibe, and came up with Compass Systems as the manufacturer.

If you have the GM520, it is USB 1.1. The GM611/621 apparently supports
either 1.1 or 2.0, but doesn't really care, as the USB interface is just
an emulated serial port via thr Prolific USB-serial converter chip used.

Your Thinkpad, depending on the vintage, may not supply enough power
from the USB port to properly operate this device (manufacturer does not
specify current, only voltage requirement).


The GM520 apparently expects 9600 baud by default, but is (supposedly)
adjustable via NMEA commands.
The GM621 expects 4800 baud by default, but is also adjustable.
The manual (what there is of it) describes "dual" communications
channels, so it is possible that two COM ports were added, and you need
to select the correct one.

This device apparently uses the Atmel Antaris4 chipset.

Instead of using SeaClear, try connecting using HyperTerminal to see if
anything is being output. If HyperTerminal reports that it can't open
the COM port, you have a driver/USB issue.


.