Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019 
<== Date ==> <== Thread ==>

Subject: Re: Linux USB serial questions
From: Jennings Guy <jennings@anl.gov>
To: "J. Lewis Muir" <jlmuir@imca-cat.org>
Cc: "tech-talk@aps.anl.gov Talk" <tech-talk@aps.anl.gov>
Date: Thu, 18 Apr 2013 16:06:21 -0500
I don't think it can work in that kernel - the ftdi_sio module only allows
a single vendor:product pair to be passed as a parameter and udev will
only see events for devices that are recognised by the ftdi_sio module.

Guy Jennings

On Apr 18, 2013, at 4:00 PM, "J. Lewis Muir" <jlmuir@imca-cat.org> wrote:

> On 4/18/13 3:15 PM, Mark Rivers wrote:
>>> With no /dev/ttyUSB* device files, what happens if the second device is
>>> plugged in first?  
>> 
>> Without unplugging the devices I can unload the driver
>> 
>> Colorado:motor/iocBoot/iocWithAsyn>sudo modprobe -r -v ftdi_sio
>> rmmod /lib/modules/2.6.35.10-74.fc14.x86_64/kernel/drivers/usb/serial/ftdi_sio.ko
>> rmmod /lib/modules/2.6.35.10-74.fc14.x86_64/kernel/drivers/usb/serial/usbserial.ko
>> 
>> At this point there are no /dev/ttyUSB devices:
>> Colorado:motor/iocBoot/iocWithAsyn>ls -l /dev/ttyUSB*
>> ls: No match.
>> 
>> Now I load the driver for model 3006
>> Colorado:motor/iocBoot/iocWithAsyn>sudo modprobe -v ftdi_sio vendor=0x104d product=0x3006 debug
>> insmod /lib/modules/2.6.35.10-74.fc14.x86_64/kernel/drivers/usb/serial/usbserial.ko 
>> insmod /lib/modules/2.6.35.10-74.fc14.x86_64/kernel/drivers/usb/serial/ftdi_sio.ko vendor=0x104d product=0x3006 debug
>> 
>> It works, and ttyUSB0 exists:
>> Colorado:motor/iocBoot/iocWithAsyn>ls -l /dev/ttyUSB0
>> crw-rw---- 1 root dialout 188, 0 Apr 18 15:09 /dev/ttyUSB0
>> 
>> Now I unload the driver again:
>> Colorado:motor/iocBoot/iocWithAsyn>sudo modprobe -r -v ftdi_sio
>> rmmod /lib/modules/2.6.35.10-74.fc14.x86_64/kernel/drivers/usb/serial/ftdi_sio.ko
>> rmmod /lib/modules/2.6.35.10-74.fc14.x86_64/kernel/drivers/usb/serial/usbserial.ko
>> 
>> No /dev/ttyUSB devices:
>> Colorado:motor/iocBoot/iocWithAsyn>ls -l /dev/ttyUSB*
>> ls: No match.
>> 
>> Now I load the driver but for model 3000 this time:
>> Colorado:motor/iocBoot/iocWithAsyn>sudo modprobe -v ftdi_sio vendor=0x104d product=0x3000 debug
>> insmod /lib/modules/2.6.35.10-74.fc14.x86_64/kernel/drivers/usb/serial/usbserial.ko 
>> insmod /lib/modules/2.6.35.10-74.fc14.x86_64/kernel/drivers/usb/serial/ftdi_sio.ko vendor=0x104d product=0x3000 debug
>> Colorado:motor/iocBoot/iocWithAsyn>ls -l /dev/ttyUSB*
>> crw-rw---- 1 root dialout 188, 0 Apr 18 15:09 /dev/ttyUSB0
>> 
>> So it works.  But I don't know how to also have it recognize the second device.  As Andrew said, loading the driver again does nothing:
>> Colorado:motor/iocBoot/iocWithAsyn>sudo modprobe -v ftdi_sio vendor=0x104d product=0x3006 debug
>> Colorado:motor/iocBoot/iocWithAsyn>ls -l /dev/ttyUSB*
>> crw-rw---- 1 root dialout 188, 0 Apr 18 15:09 /dev/ttyUSB0
>> 
>> I'll look into udev.
> 
> Hi, Mark.
> 
> I still think your modprobe command should work.
> 
> Do you still have your 81-Agilis.rules udev rules file loaded containing:
> 
>  SYSFS{idVendor}=="104d", ATTRS{idProduct}=="3000", MODE="0666"
> 
> What happens if you add another rule for model 3006?
> 
>  SYSFS{idVendor}=="104d", ATTRS{idProduct}=="3006", MODE="0666"
> 
> What happens if you connect both devices, but after connecting the
> second, wait 60 seconds in case the /dev/ttyUSB1 file is somehow slow to
> show up?
> 
> Lewis



Replies:
Re: Linux USB serial questions J. Lewis Muir
References:
Linux USB serial questions Mark Rivers
RE: Linux USB serial questions Mark Rivers
Re: Linux USB serial questions J. Lewis Muir
RE: Linux USB serial questions Mark Rivers
Re: Linux USB serial questions J. Lewis Muir

Navigate by Date:
Prev: Re: Linux USB serial questions J. Lewis Muir
Next: Re: Linux USB serial questions J. Lewis Muir
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019 
Navigate by Thread:
Prev: Re: Linux USB serial questions J. Lewis Muir
Next: Re: Linux USB serial questions J. Lewis Muir
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019 
ANJ, 20 Apr 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·