PSN-L Email List Message

Subject: Re: Linux & WINSdr
From: Bob Hancock raptor@.......
Date: Fri, 19 Jul 2013 22:17:10 -0700


Hi Larry -

First, I add the name as follows:  sudo adducer bob dialoiut          =
Still unable to connect.

Then I did some more testing and got some interesting results.  First I =
redid the sudo commands and then checked the results:

bob@linuxmint ~ $ sudo chmod 666 /dev/ttyUSB0
[sudo] password for bob:
bob@linuxmint ~ $ sudo chmod 666 /dev/ttyUSB1
bob@linuxmint ~ $ ls -la /dev/ttyUSB*
crw-rw-rw- 1 root dialout 188, 0 Jul 19 21:44 /dev/ttyUSB0
crw-rw-rw- 1 root dialout 188, 1 Jul 19 21:44 /dev/ttyUSB1

I then reset the computer and rechecked the data again:

bob@linuxmint ~ $ ls -la /dev/ttyUSB*
crw-rw---- 1 root dialout 188, 0 Jul 19 21:52 /dev/ttyUSB0
crw-rw---- 1 root dialout 188, 1 Jul 19 21:52 /dev/ttyUSB1
bob@linuxmint ~ $

The -rw in the third row which is 'other' is deleted when I do a reset =
on the computer.  I do not believe that is important, but am not sure.  =
The user and group remain the same.

Still no change when I try to open WinSDR before or after the reset.

I know there are six USB ports on the computer and all are useable in =
both Linux or Windows XP.  I checked WinSDR in all six ports and it will =
not open.  I am wondering if there is some obscure switch that is not =
properly set as I know everything works in Windows.  Either that or this =
version of Linux is incompatible with the signal from the A/D board.  =
Its has to be in one of these two area.  Personally, I believe that =
there is some switch that is not set properly.

Thanks again for all your help.

Bob Hancock

On Jul 19, 2013, at 8:48 PM, Larry Cochrane  =
wrote:

> Hi Bob,
>=20
> I remember now, one other thing I needed to do was add my user account =
to the dialout group. So try something like this:
>=20
> sudo adduser your_user_name dialout
>=20
> If that does not work do a google search on "dialout group =
permissions". There seems to be several ways to add a user to a group so =
you may need to try different commands for your version of Linux.
>=20
> One way around all of this is to run as root and reinstall WinSDR. If =
you do this you will need to start from scratch since Wine will create a =
new .wine directory under the root home directory.
>=20
> Regards,
> -Larry
>=20
> On 7/19/2013 7:34 PM, Bob Hancock wrote:
>> Hi Larry -
>>=20
>> My goof - this morning - I was rushing to leave for multiple =
appointments and was out all day.  I redid the SUDO commands and listed =
below is what I got.  As you can see it is identical to yours.
>>=20
>> Still unable to get WinSDR open with Linux, but it works fine with a =
USB slot using the RS-232 to USB FTDI adapter/
>>=20
>> With Apologies
>>=20
>> Bob Hancock
>>=20
>> bob@linuxmint ~ $ ls -la /dev/ttyUSB*
>> crw-rw-rw- 1 root dialout 188, 0 Jul 19 18:47 /dev/ttyUSB0
>> crw-rw-rw- 1 root dialout 188, 1 Jul 19 18:48 /dev/ttyUSB1
>> bob@linuxmint ~ $
>>=20
>>=20
>>=20
>>=20
>>=20
>> On Jul 19, 2013, at 6:03 PM, Larry Cochrane =
 wrote:
>>=20
>>> Hi Bob,
>>>=20
>>> =46rom your ls -la printout it looks like the ports can only be =
opened by root. Did you do the sudo chmod 666 /dev/ttyUSB0 and sudo =
chmod 666 /dev/ttyUSB1 commands?
>>>=20
>>> This is what you should see after doing them:
>>>=20
>>> crw-rw-rw- 1 root dialout 4, 64 Jul 19 17:52 /dev/ttyS0
>>> crw-rw-rw- 1 root dialout 4, 65 Dec 31  2009 /dev/ttyS1
>>>=20
>>> Note the extra rw in the permission information.
>>>=20
>>> Regards,
>>> -Larry
>>>=20
>>> On 7/19/2013 6:41 AM, Bob Hancock wrote:
>>>> Hi Larry -
>>>>=20
>>>> Still unable to open Com Port 1 or 2 with WinSDR
>>>>=20
>>>> The commands you sent to me went accepted with no problems.  =
Following is output you requested
>>>>=20
>>>> bob@linuxmint ~ $ ls -la /dev/ttyUSB*
>>>> crw-rw---- 1 root dialout 188, 0 Jul 19 06:00 /dev/ttyUSB0
>>>> crw-rw---- 1 root dialout 188, 1 Jul 19 06:00 /dev/ttyUSB1
>>>> bob@linuxmint ~ $
>>>>=20
>>>> I only have one RS-232 to USB adaptor plugged in.  At present there =
is nothing plugged in to the two RS-232 ports.
>>>>=20
>>>> Question - Could this be due to the old Version 1 AD board I am =
using.
>>>>=20
>>>> Bob Hancock
>>>>=20
>>>>=20
>>>> On Jul 18, 2013, at 9:35 PM, Larry Cochrane =
 wrote:
>>>>=20
>>>>> Hi Bob,
>>>>>=20
>>>>> Ok, now we are getting somewhere... It's strange that two ttyUSB =
devices are in the /dev/ directory. Do you have two USB to RS-232 =
adapters connected up to the system? Does one or both go away if you =
remove/unplug the adapter that is connected up to the A/D board?
>>>>>=20
>>>>> Try the following commands:
>>>>>=20
>>>>> sudo chmod 666 /dev/ttyUSB0
>>>>> sudo chmod 666 /dev/ttyUSB1
>>>>> then do...
>>>>> cd ~.wine/dosdevices
>>>>> ln -s /dev/USB0 com1
>>>>> ln -s /dev/USB1 com2
>>>>>=20
>>>>> Next check the permission on the port(s) by using the following =
command:
>>>>>=20
>>>>> ls -la /dev/ttyUSB*
>>>>>=20
>>>>> And send the output to the psnlist if you are still having =
problems.
>>>>>=20
>>>>> Now start up WinSDR using Wine and if Comm Port 1 does not work =
try Comm Port 2.
>>>>>=20
>>>>> Regards,
>>>>> -Larry
> __________________________________________________________
>=20
> Public Seismic Network Mailing List (PSNLIST)
>=20
> To leave this list email PSNLIST-REQUEST@.............. with the body =
of the message (first line only): unsubscribe
> See http://www.seismicnet.com/maillist.html for more information.
>=20

__________________________________________________________

Public Seismic Network Mailing List (PSNLIST)

To leave this list email PSNLIST-REQUEST@.............. with 
the body of the message (first line only): unsubscribe
See http://www.seismicnet.com/maillist.html for more information.

[ Top ] [ Back ] [ Home Page ]