Since May am i using Nx on a toshiba sattelite 2004 and it workrs great but i have problems to conntect the garmin 60csx to Opencpn. My Raymarine gps works ok, with a serial usb adapter.
I also cant make a connection with Subsurface and mij divingcomputer. is this the same problem?

berdie@berdie-Satellite-M30:~$ ls -l /dev/bus/usb/002/002
crw-rw-r-- 1 root plugdev 189, 129 Aug 3 20:24 /dev/bus/usb/002/002
berdie@berdie-Satellite-M30:~$

Do i need to get in as root? and if yes howe do i get i as root?

Thanks....
Berdie
www.devliet.com

First, I don't think the Garmin 60CSx can stream live data through the USB. I think it it for mass storage transfer only.

Secondly, do you have more information on the dive computer?

Make, model, URL so I know what you're talking about....

When you plug in the dive computer, enter lsusb to list the devices on the USB ports.

Find the dive computer in the list and tell us what is returned.

Hallo Moe, The divingcomputer is a Uwatec Z nitrox.

If i put "lsusb" in the terminal and both divices are connected the result is:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 003: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 091e:0003 Garmin International GPS (various models)
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

The Uwatec is connected to the Prolific with a serial connectingbox like the uwatec memo mouse.

The Garmin is on USB directly.

Both devices work with windows XP on the same type of Toshiba laptop. The Garmin with Open CPN works fine and the Uwatec works with Suburface and Wlog.

Thanks for looking in my problem.

In the terminal execute:

sudo dpkg-reconfigure gpsd

What you are going to do is add -N to the appropriate line.
Add -N to the line with -n -b -G. Order is not important.Spa cing isi mport ant. Tab to <Ok> when your done and <Enter>
When you have done with that procedure; reboot your computer.

See if that works.

Hallo Moe,

No result,

After the screen you gave me there was a screen asking : /var/run/gpsd.sock______
What do i have to fil in?

Regards Berdie

The turminal gave:
berdie@berdie-Satellite-M30:~$ sudo dpkg-reconfigure gpsd
[sudo] password for berdie:
gpsd:ERROR: device open failed: No such file or directory - retrying read-only
gpsd:ERROR: read-only device open failed: No such file or directory
gpsd:ERROR: initial GPS device Bus open failed
gpsd:ERROR: device open failed: No such file or directory - retrying read-only
gpsd:ERROR: read-only device open failed: No such file or directory
gpsd:ERROR: initial GPS device 003 open failed
gpsd:ERROR: device open failed: No such file or directory - retrying read-only
gpsd:ERROR: read-only device open failed: No such file or directory
gpsd:ERROR: initial GPS device Device open failed
gpsd:ERROR: device open failed: No such file or directory - retrying read-only
gpsd:ERROR: read-only device open failed: No such file or directory
gpsd:ERROR: initial GPS device 002: open failed
gpsd:ERROR: initial GPS device ID open failed
gpsd:ERROR: initial GPS device 091e:0003 open failed
gpsd:ERROR: initial GPS device Garmin open failed
gpsd:ERROR: initial GPS device International open failed
gpsd:ERROR: initial GPS device GPS open failed
gpsd:ERROR: initial GPS device (various open failed
gpsd:ERROR: initial GPS device models) open failed

Sorry, the dpkg-reconfigure gpsd was <ok> everything that is already there, and only and the -N.
And judging from the return you posted, even though it doesn't match the command, leads us to this step.

Insert this line:


Save, and reboot, and try again.

You're granting read privileges to that device.

Hi Meo,

No succes with this action, what info do you need?

Berdie
www.devliet.com

...I need the info to make it work;-)

Plug in the gps. to find which USB it is attached to. Kill the gpsd daemon and remove the old socketstart the gpsd in non-daemon diagnostic sudo gpsd -D5 -nN -F /var/run/gpsd.sock /dev/ttyUSBx with **ttyUSBx** being the location returned by dmesg | tail.

berdie@berdie-Satellite-M30:~$ dmesg | tail
[ 59.671679] type=1400 audit(1407438657.494:50): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=1455 comm="apparmor_parser"
[ 100.820173] e100 0000:02:08.0 eth0: NIC Link is Up 100 Mbps Full Duplex
[ 100.820268] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 109.696571] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
[ 128.583285] Bridge firewalling registered
[ 152.552067] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[ 430.709070] init: plymouth-stop pre-start process (2757) terminated with status 1
[ 553.060123] usb 2-1: new full-speed USB device number 2 using uhci_hcd
[ 553.203644] usb 2-1: New USB device found, idVendor=091e, idProduct=0003
[ 553.203659] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
berdie@berdie-Satellite-M30:~$ sudo killall gpsd
berdie@berdie-Satellite-M30:~$ sudo rm /var/run/gpsd.sock
[sudo] password for berdie:
berdie@berdie-Satellite-M30:~$ sudo gpsd -D5 -nN -F /var/run/gpsd.sock /dev/ttyUSBx
gpsd:PROG: control socket opened at /var/run/gpsd.sock
gpsd:INFO: launching (Version 3.9)
gpsd:IO: opening IPv4 socket
gpsd:IO: opening IPv6 socket
gpsd:INFO: listening on port gpsd
gpsd:PROG: NTPD shmat(0,0,0) succeeded, segment 0
gpsd:PROG: NTPD shmat(32769,0,0) succeeded, segment 1
gpsd:PROG: NTPD shmat(65538,0,0) succeeded, segment 2
gpsd:PROG: NTPD shmat(98307,0,0) succeeded, segment 3
gpsd:PROG: successfully connected to the DBUS system bus
gpsd:PROG: PPS thread launched
gpsd:INFO: NTPD ntpd_link_activate: 1
gpsd:INFO: stashing device /dev/ttyUSBx at slot 0
gpsd:PROG: no /etc/gpsd/device-hook present, skipped running ACTIVATE hook
gpsd:INFO: opening read-only GPS data source type 0 and at '/dev/ttyUSBx'
gpsd:ERROR: device open failed: No such file or directory - retrying read-only
gpsd:ERROR: read-only device open failed: No such file or directory
gpsd:ERROR: initial GPS device /dev/ttyUSBx open failed
gpsd:INFO: running with effective group ID 20
gpsd:INFO: running with effective user ID 65534
gpsd:INFO: startup at 2014-08-07T19:23:38.000Z (1407439418)
gpsd:PROG: PPS Create Thread gpsd_ppsmonitor
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
dmesg | tail.gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation
gpsd:PROG: PPS thread awaiting device activation

the program XGPS gave this string:
"class":"VERSION","release":"3.9","rev":"3.9","proto_major":3,"proto_minor":8}

Berdie

I'm sorry for not being clear.

/dev/ttyUSBx is a placeholder for the real location.
As you see, the last line ([ 8431.357859] pps pps0: source "/dev/ttyUSB1" added) tells me where the gps I just plugged in is attached.

So the command I would execute would be sudo gpsd -D5 -nN -F /var/run/gpsd.sock /dev/ttyUSB1

berdie@berdie-Satellite-M30:~$ dmesg | tail
[ 66.264360] type=1400 audit(1407512304.268:48): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=1781 comm="apparmor_parser"
[ 66.264376] type=1400 audit(1407512304.268:49): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=1781 comm="apparmor_parser"
[ 66.265417] type=1400 audit(1407512304.268:50): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=1781 comm="apparmor_parser"
[ 115.724592] Bridge firewalling registered
[ 222.072295] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 225.585222] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[ 282.872110] usb 2-2: USB disconnect, device number 2
[ 381.852043] usb 2-1: new full-speed USB device number 3 using uhci_hcd
[ 381.995692] usb 2-1: New USB device found, idVendor=091e, idProduct=0003
[ 381.995700] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0

This string is differend tot your strings, I cant see a USB number

Berdie

Aha! This might be a clue to a hotplug issue. I'll get back when I untangle my thoughts.

Hi Meo,

The Divingcomputer, Uwatec Z nitrox, has started communicating with Subsurface through /dev/ttyUSB0. The Garmin is communicating with Gebabbel bud not with OpenCpn.

Berdie

Does your OpenCPN look like this?

Yes, But in the colom connection it says No and insted of /tmp/aisfifo i have /dev/ttyUSB0

Was there a reason to change it?

Moe,
I had a lot of problems to persuade the tohsiba to run Nx and tot make OpenCpn connect tot de Raymarine. Maybe that's the reason the Garmin is not connecting although XGPS is not in conncection as wel. So i tried a lot of different ways. I sailed for weeks on NX and Raymarine and a mousGPS as back-up without problems adding the Garmin is maybe a bit too much.

Berdie

So the problem might be that the Raymarine was not running properly and the 'fix' for that guaranteed the Garmin wouldn't work.

Unless you disable the gpsd, you will have problems.

If you disable the gpsd, other functions automatically supplied gps data in other parts of the system will not be delivered.

Hi Moe,

Yesterday i had OpenCpn running as it should. it could vind the GSP direct. But after switshing to the Garmin OpenCpn disapeerd and wil not open again. So i am wondering what to do next. reinstal Nx or is there a way to get Opencpn running again?

Greetings Berdie