Open Cpn can't see GPS

[barnakiel]

When I fire up our BU puck on our XP machine it comes up at 4800, not 9600.

Bauds may be different with another puck and another Win (?), do make sure what the rate is before setting up OpenCPN connection.

Try 4800 see what happens.

Cheers,
b.

[fgd3]

Phil, the screenshots were a big help. As others have suggested, try 4800 baud. That's the specified bit rate for NMEA 0183 links. It's what I've always used, although I understand that some devices are tolerant of a wider range of settings.

Fabbian

[phil23]

I want to thank everybody for their help over this rather protracted mission I am now sorted, working on both BU353 and NMEA info from my Lowerance plotter/sounder.
I sent it down to NEPTUNES GEAR at Gulf Harbour, Auckland and he had it rectified new charts installed and back on the courier in the same day.
Thanks again for all the offers of help

[hhmcsv]

Just for reference, here is my setup which also works:

PC: Thinkpad T440 running Win10 pro
OpenCpn version 4.4.0
Gps-dongle: Globalsat ND100-S, some years old
GPS-testprogram: GPSinfo, GPSInfo for Windows
(ver. 1109151):
(Supports Windows 10, 8, 7, Vista,XP)

http://www.usglobalsat.com/store/downloads/GPSInfo.zip

The GPS-dongle is found in Device Manager as COM7, it uses a Prolific driver dated 04-09-2015, version 3.6.81.357.
I set the port to use 4800 baud.
Works fine in OpenCpn, but only one program (i.e. either OpenCpn or GPSinfo) can be running at one time

[Neptune's Gear]

In Windows, only one software application can use a specific serial port at a time. If you want to share gps data between apps, you can use an application like gpsgate to create additional virtual serial ports that can all see the gps data... :-) this issue is nothing to do with ocpn.

Sent from my D5503 using Cruisers Sailing Forum mobile app