Fwd: Re: Connectiviy problem
rickmwalsh at gmail.com
Mon Apr 21 21:02:12 PDT 2014
Forgot to cc the mailing list.
---------- Forwarded message ----------
From: "Rick Walsh" <rickmwalsh at gmail.com>
Date: 22 Apr 2014 13:55
Subject: Re: Connectiviy problem
To: "Mario Pilz" <mariopilz at gmx.net>
On 22 April 2014 13:20, Mario Pilz <mariopilz at gmx.net> wrote:
> Hi Miika,
> thanks a lot for the quick reply. I followed what you mentioned below, but
> the dialout group was already established and it still doesn't work out. Do
> you have another idea?
> Did anybody have similar difficulties to establish connection?
Make sure you're telling Subsurface to connect to the correct device. On my
computer, and many other Linux systems with many dive computers, it's
/dev/ttyUSB0, but it may be different for you. One way to find out what the
device is called is to look at the system log file. On Ubuntu, I think it's
/var/log/syslog, but it may be /var/log/messages. At the command prompt,
sudo tail -f /var/log/syslog
sudo may or may not be necessary, depending on permissions.
This will monitor the log, and display the last few lines of the file.
Then, plug in your cable, a bunch of new lines should be logged. From this
you should be able to work out the correct device. From this you should be
able to work out the correct device. As an example, taken from Appendix A
of the user manual:
usb 2-1.1: FTDI USB Serial Device converter now attached to ttyUSB3
usbcore: registered new interface driver ftdi_sio
This tells you that the device is /dev/ttyUSB3, and the kernel driver is
ftdi_sio. In subsurface, when you download from dive computer, enter
/dev/ttyUSB3 (or whatever you get) as the device.
Let us know if this helps.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the subsurface