3.3.814 wouldn't recognize GPS

[fgd3]

I am a little behind on versions but a day or two ago I downloaded 3.3.814 and installed it. Most of the time I use OpenCPN for looking at charts at home. Call it virtual or vicarious sailing if you like. The new version seemed fine.

Once in a while, though, I take the computer (Windows 7) out on the boat, connect the GPS (BU-353), and take it out on the water. I tried to do that today with 3.3.814 but it wouldn't get a position from the GPS even though I could see the data in the NMEA debug window.

I tried removing and adding the com 6 connection. It didn't make any difference. I couldn't find anything in settings to fix the problem.

I reinstalled 3.3.719 and immediately had a GPS position. I've attached the log file from the two attempts with 3.3.814 and the successful one with 3.3.719. The only thing different that I noticed was a reference to EnumerateSerialPorts() Found Garmin USB Driver.

Any suggestions on what I need to do to get my GPS working with 3.3.814?

Fabbian

[fgd3]

This afternoon I installed 3.3.814 on my Vista computer and tried it with the BU-353. No problem getting a position. The log file looks just the same to me. I've attached it as opencpnlog.doc (same name as in the previous message, but it's not the same file). My next step is to reinstall 3.3.814 on my W7 computer and see if I can repeat the error. I'll report back when that's done.

Fabbian

[fgd3]

I reinstalled 3.3.814 to my W7 computer and tested it with the GPS again. This time it worked fine. I don't know why it didn't show a GPS position the first time I tried it. What was puzzling was that I could see the data scrolling in the NMEA debug window and the GPS was reporting a good position. It works now, though, so I am confident the problem wasn't in OpenCPN.

Fabbian

[rgleason]

This may be unrelated, but
I have a Globalstar BU-355 PS-2 with a second PS-2 to USB cable, and was just using it this morning on the PC with 3.3.814 through Com3 at 9600 and 57000 baud using the Prolific driver. At first I was having some trouble getting it to run properly at 4800 baud. No NMEA in the GPSinfo Utility. I then tried SirfDemo 387 demo utility and was able to see the NMEA. I reset the BU-355 to 4800 baud, closed SirfDemo, and tried GPSinfo utility. No dice.

Then removed USB plug safely. Waited a little and reinserted. Now the puck sees NMEA at 4800 baud. I must say that more often I run it at 9600 baud when on the PC, and then it just seems to work coming up on Com3, and Opencpn finds it right away.

I have to have 4800 baud when I am using it connected to my Standard Horizon DSC VHF with a second PS-2 cable directly wired to 5v supply and VHF nmea in and out and ground, because the VHF requires 4800 baud.