[Acoustics] Reported GPS problems

[McBride, Daniel J MVR]

David--

It appears that this might be happening with our recording setup, too.  We
use an XP Pro Panasonic Toughbook with an OLD Socket Card for both the ADCP
and GPS (Pathfinder Pro XR).  When I initially read your post, I thought we
were in the clear because we used the older version of Socket's card.  After
a few measurements this spring, however, I'm starting to think that we've got
the same issue.

Have you (or anyone) found a workaround while still using the Socket card?
Also, could you send me details of how you tested for the problem?  In the
meantime, I'm planning on using the Socket card for the ADCP, while using the
Toughbook's built-in serial port for the GPS.

The bar code on the back of our Socket card reads:
*8010-00077 C*

Please let me know what you've found since your initial post, and thanks for
bringing this to everyone's attention.

--Dan McBride

Daniel McBride
Hydrologist
U.S. Army Engineer District, Rock Island
Water Quality and Sedimentation Section
CEMVR-ED-HQ
Clock Tower Building, P.O. Box 2004
Rock Island, IL  61204-2004
Phone: (309) 794-5720   Fax: (309) 794-5584
E-mail: daniel.j.mcbride at mvr02.usace.army.mi



-----Original Message-----
From: acoustics-bounces at simon.er.usgs.gov
[mailto:acoustics-bounces at simon.er.usgs.gov] On Behalf Of David S. Mueller
Sent: Wednesday, February 02, 2005 8:51 AM
To: jerbland at usgs.gov; TVERMEYEN at do.usbr.gov; acoustics at simon.er.usgs.gov
Subject: [Acoustics] Reported GPS problems


I recently spent a day in the field trying to track down a problem several
people had reported to me. The problem manifests itself as an extreme delay
in GPS data used in WinRiver (up to 110 sec old). This causes the beginning
of transects to go in the wrong direction (based on GPS) and not following
bottom track at all. It can also result in short DMG. The discharges are
obviously wrong.

After testing on two computers (one Win98 and on XP Pro) and using three
different serial ports (internal, new Socket card, Keyspan 4-port USB RS-232
adapter) I reached the conclusion that there is an incompatibility between
the new Socket cards and WinRiver.

By splitting the data coming from the GPS unit and monitoring it with a
second computer, it was clear that the GPS unit (Ag132) was providing
correct data but that the data were being buffered in the computer running
WinRiver. The problem grows between transects. It appears that between
transects when you are not recording data the GPS data gets buffered and
when you start another transect the buffer is not flushed and you start
using old GPS data. This occurred using 5 Hz update rate and 9600 baud rate.
However, it only occurred when the GPS was fed through the Socket card. The
problem was minimized (delay of about 2 seconds) going to a higher baud rate
19.2K. This problem occurred on both computers and only occurred when the
GPS data was fed into the Socket card. Reversing the ADCP and GPS ports
appeared to fix the problem, as did using the Keyspan.

I also tried an earlier version of WinRiver but that did not eliminate the
problem.

I would like to know if those of you who have experienced this problem are
using a newer Socket card and if so, does the problem go away by switching
ports are using a different external serial interface adapter.

The new Socket cards have a bar code on the back with the numbers:
8510-00073 J
I do not have the version number of the driver used.

I am aware of other software with incompatibilities with the new Socket
cards and expect that card is the cause of many of the GPS issues that have
appeared in the last 6 months.

Thanks for your help.

David S. Mueller
U.S. Geological Survey
Office of Surface Water
9818 Bluegrass Parkway
Louisville, KY 40299

dmueller at usgs.gov

Voice: 502-493-1935
Fax: 502-493-1909
Mobile:502-558-5907



_______________________________________________
Acoustics mailing list
Acoustics at simon.er.usgs.gov
http://simon.er.usgs.gov/mailman/listinfo/acoustics