The other option is to write your software so that it gets notified
when a USB device is installed/removed. You will be told the actual
device name. I needed to do this to detect insertion/removal of a
barcode reader.
Looking at the actual code it is setting a default value of /dev/ttyUSB0.
On 10/31/19 6:24 PM, Kevin Cozens via talk wrote:
On 2019-10-31 9:11 a.m., Scott Allen via talk wrote:
On Thu, 31 Oct 2019 at 02:25, Jim Ruxton via talk
wrote:
Is there a way that I can always have it show up as /dev/ttyUSB0
I think the proper way is to provide a udev rule to identify the
de
Is there a way that I can always have it show up as /dev/ttyUSB0
I think the proper way is to provide a udev rule to identify the
device and assign a fixed name to it.
https://unix.stackexchange.com/questions/66901/how-to-bind-usb-device-under-a-static-name
The other option is to write yo
On 2019-10-31 9:11 a.m., Scott Allen via talk wrote:
On Thu, 31 Oct 2019 at 02:25, Jim Ruxton via talk wrote:
Is there a way that I can always have it show up as /dev/ttyUSB0
I think the proper way is to provide a udev rule to identify the
device and assign a fixed name to it.
https://unix.s
On Thu, Oct 31, 2019 at 1:07 PM Jim Ruxton via talk wrote:
>
>
>
> Is your user a member of the dialout group? You can't access serial ports
> unless you are.
>
> Yes I am a member of dialout and I have no problem when my device uses
> /dev/ttyUSB0 .
>
>
> Also, 'baudrate=57142' looks a bit odd.
Is your user a member of the dialout group? You can't access serial
ports unless you are.
Yes I am a member of dialout and I have no problem when my device uses
/dev/ttyUSB0 .
Also, 'baudrate=57142' looks a bit odd. 57600 is more standard, but
I've seen that number used for a couple of moto
Is your user a member of the dialout group? You can't access serial ports
unless you are.
Also, 'baudrate=57142' looks a bit odd. 57600 is more standard, but I've
seen that number used for a couple of motor controllers.
Is there a way you can try it without the USB extender?
Are you using more t
I will try this but I am worried that if the device symlinks to
/dev/ttyUSB1 it's not going to work since whenever I use anything but
/dev/ttyUSB0 my device doesn't work.
Jim
On Thu., Oct. 31, 2019, 9:12 a.m. Scott Allen via talk,
wrote:
> On Thu, 31 Oct 2019 at 02:25, Jim Ruxton via talk wrote
On Thu, 31 Oct 2019 at 02:25, Jim Ruxton via talk wrote:
> Is there a way that I can always have it show up as /dev/ttyUSB0
I think the proper way is to provide a udev rule to identify the
device and assign a fixed name to it.
https://unix.stackexchange.com/questions/66901/how-to-bind-usb-device
Thanks. I tried /dev/serial/by-id and although my python program looks
like it should work ie. it accepts
serial_connection =
Connection(port="/dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AL03EO23-if00-port0",
baudrate=57142)
Its not sending out serial data. This is the same result if I have
On 10/31/19 2:25 AM, Jim Ruxton via talk wrote:
I have a device plugged into an active USB extender that usually shows
up as /dev/ttyUSB0 when I first plug it in (occasionally it will show
up as /dev/ttyUSB1 when first plugging it in) . If it is /dev/ttyUSB0
when I unplug it and plug it back in
On 10/31/19 2:25 AM, Jim Ruxton via talk wrote:
I have a device plugged into an active USB extender that usually shows
up as /dev/ttyUSB0 when I first plug it in (occasionally it will show
up as /dev/ttyUSB1 when first plugging it in) . If it is /dev/ttyUSB0
when I unplug it and plug it back in
12 matches
Mail list logo