EPICS Controls 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  2013  2014  <20152016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  <20152016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: USB-to-serial
From: "Johnson, Andrew N." <[email protected]>
To: "Specht, Eliot D." <[email protected]>
Cc: "[email protected]" <[email protected]>
Date: Tue, 19 May 2015 21:32:26 +0000
Hi Eliot,

We need a bit more information about your tests that failed:

1. What Linux are you running?
2. When you plug in the USB-to-serial device, does Linux create a /dev/ttyUSB0 device automatically?
3. You said your old IOC configuration fails on the new hardware. Was that with the IOC startup changed to point to the the new /dev/ttyUSB0 device path instead of the previous /dev/ttyS0 or similar?
4. Does Asyn show the serial port as being connected? Exactly what error messages (if any) do you get from it? Have you tried sending data through the port manually using an asynRecord?

My USB-to-serial device doesn’t need any special modprobe commands, I suspect they are probably only needed on older Linux systems, or if you have an unusual USB device. However I do have to add a file to /etc/udev/rules.d to tell udev what file permissions I want on the /dev/ttyUSB* device node because by default Red Hat Enterprise doesn’t let me access the device. My file /etc/udev/rules.d/55-anj.rules contains just this:
    KERNEL=="tty[A-Z]*",        MODE="0666"

When you answer the above questions I might not be able to help further, but hopefully others here will.

- Andrew


On May 19, 2015, at 3:33 PM, Specht, Eliot D. <[email protected]> wrote:

> ​I have a Eurotherm 2416 temperature controller which travels with me. I was using a desktop computer to run an EPICS IOC, but I realized this was foolish and am replacing it with a laptop. The desktop has a built-in serial port, while the laptop uses a USB-to-serial port. I'm running the same EPICS configuration with some updated modules, but the serial communications which worked on the desktop do not work on the laptop. I get errors with "No reply from device".
> 
> I'm hoping someone can explain the confusing results of my search of tech-talk. Some posts suggest that I just plug in the USB-to-serial and use the /dev/ttyUSB0 device which is automatically created. Others suggest that I need to use a command like "modprobe ftdi_sio vendor=0x67b product=0x2303", which gives the error "ftdi_sio: unknown parameter 'vendor' ". 
> 
> Question: do I need to use the "modprobe ftdi_sio" command, and if so why is the 'vendor' parameter giving it trouble?
> 
> Details:
> Eurotherm 2416 temperature controller with serial interface
> base-3.15.1
> asyn-4-26
> stream-2-6a
> sateco Eurotherm protocols from X.L. Wang



References:
USB-to-serial Specht, Eliot D.

Navigate by Date:
Prev: RE: USB-to-serial Mark Rivers
Next: RE: USB-to-serial Mark Rivers
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  <20152016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: RE: USB-to-serial Mark Rivers
Next: RE: USB-to-serial Mark Rivers
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  <20152016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 16 Dec 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·