OpenCPN - Recognising NMEA data (Mac version)

deuc02

Well-Known Member
Joined
13 Oct 2009
Messages
465
Visit site
Anyone got any tips or hints as to how to get the Mac version of OpenCPN to see NMEA data. Have all NMEA 0183 data coming through an Actisense multiplexer into a USB port on a Mac. Have downloaded and installed the latest driver from the Actisense website. All good so far. Run OpenCPN and go into the toolbox. This is where the problem starts. Think the OpenCPN manal might be for an older version as it refers to

When the driver is installed and the device connected, start OpenCPN, select the Toolbox and click the GPS tab. Open the "NMEA Data Source" menu & select the the device from the list. It is not always obvious which is the correct one, but in general the device will have a name starting: "/dev/cu." or "/dev/tty.". Some manufacturers make it obvious, like "/dev/cu.MiniPlex-99000125", but others may be more generic, like: "/dev/cu.usbserial". Set the "NMEA Baud Rate" to 4800 and click "OK". If the correct selection has been made, you should see the GPS status icon change from red to green.

So go to toolbox and then to connections as no GPS tab that I can see. Can't see a NMEA Data Source menu but hit the Add Connection box. The only selectable data source is /dev/cu.Bluetooth-PDA-Sync

Am I missing something obvious, or looking in the wrong place. Any thoughts, ideas or fixes gratefully received
 
Edit from previous (wordy) version of this post: Since had a play with someone else's mac and device entries aren't as dynamic as linux. I did say I wasn't a mac expert. I also said I wasn't an opencpn expert so take anyone else's opinion over mine.

Yes you're right: toolbox->connections->add connection. My dodgy 3.1 beta I seem to be running allows you to type a devicename in: earlier versions you couldn't do that and had to hack opencpn.conf.

You say you've installed the driver. If the device is also plugged in and your device isn't in the opencpn drop down try and find out what the device name is. If it isn't in your actisense/driver documentation, might be worth an email to actisense support (unless this or another forum can help). You could always look in the /dev directory where the device links are created: pull up a terminal window (under utilities in finder IIRC) and type:
ls /dev
This will give you a list of all the devices. See if you can see one which looks like it might be your device (e.g. cu.actisense or something similar?). If you find something, manually enter it in the "Data Port" box preceded by "/dev/" (e.g. if you find a cu.actisense, your device is "/dev/cu.actisense").

Take anyone else's suggestion over this though (honestly, I'm only replying with guesses because no-one else has) and if you're still not getting any joy post on the opencpn forum:
http://www.cruisersforum.com/forums/f134/
 
Last edited:
Top