Hi Ed,
Am Tue, 21 Feb 2017 16:48:42 -0500
schrieb Ed <au...@comcast.net>:
> On Tue, 21 Feb 2017 21:27:24 +0100
> Ervin Hegedüs <airw...@gmail.com> wrote:
>
> > Hi Ed,
> >
> > On Tue, Feb 21, 2017 at 03:02:07PM -0500, Ed wrote:
> > > I'm using an Icom 7200 with a USB cable from the rig to the pc.
> > > This is what I'm using to define the port::
> > >
> > > /dev/serial/by-id/usb-Silicon_Labs_CP2102_USB_to_UART_Bridge
> > >
> > > of course that does not work and that is the only choice I know
> > > of.
> > >
> > > Work around ?
> >
> > I don't know the rig above, I just Google'd some info's.
> >
> > I see, the rig has an USB connector - but I assume that it's a
> > serial converter (which is probably true, the USB_to_UART in your
> > name of device affects that too).
> >
> > If that true, the most simple way, that you unplug the converter
> > from PC, and reconnect, till you see the syslog/messages file.
> > You'll see some kind of these lines:
> >
> > [235784.268109] usb 5-1: ch341-uart converter now attached to
> > ttyUSB3
> >
> > then you can set up in your logcfg.dat these:
> >
> > RADIO_CONTROL
> > RIGMODEL=361
> > RIGSPEED=19200
> > RIGPORT=/dev/ttyUSB3
> >
> > of course, the RIGPORT is what you see in your log.
> >
> > You can fix the device through the udev:
> >
> > type this command:
> > sudo udevadm
> > info /dev/serial/by-id/usb-Silicon_Labs_CP2102_USB_to_UART_Bridge
> >
> > you'll see something like this:
> >
> > P: /devices/pci0000:00/0000:00:1d.3/usb5/5-1/5-1:1.0/ttyUSB3/tty/ttyUSB3
> > N: ttyUSB3
> > S: serial/by-id/usb-1a86_USB2.0-Serial-if00-port0
> > S: serial/by-path/pci-0000:00:1d.3-usb-0:1:1.0-port0
> > ...
> > E: ID_MODEL_ID=7523
> > E: ID_PATH=pci-0000:00:1d.3-usb-0:1:1.0
> > E: ID_PATH_TAG=pci-0000_00_1d_3-usb-0_1_1_0
> > E: ID_REVISION=0254
> > E: ID_SERIAL=1a86_USB2.0-Serial
> > E: ID_TYPE=generic
> > ...
> > E: ID_VENDOR=1a86
> > E: ID_VENDOR_ENC=1a86
> >
> >
> > by those lines, you can write an own rule for udev:
> >
> > sudo touch /etc/udev/rules.d/z21_persistent-local.rules
> >
> > edit the file, and put these fields, of course replace to your
> > output:
> >
> > ATTRS{idProduct}=="7523", ATTRS{idVendor}=="1a86", SYMLINK+="rig"
> >
> > Then:
> >
> > sudo udevadm control --reload
> >
> >
> > In this case, if you'll connect your rig to your PC (which has
> > that udev rule), you will see that as "/dev/rig", and you can
> > talk with from any application (of course, you have to replace
> > the /dev/ttyUSBX in Tlf logcfg.dat file too).
> >
> >
> > Hope that's clear - let me know, if you have any question.
> >
> >
> >
> > 73, Ervin
> >
> >
>
> Thank you for the precise directions. I'll work on this tomorrow.
>
> 73
>
> Ed W3NR
>
as a second way you can simply make a symbolic link to your device node
ln -s /dev/your_device myradio
and use 'RIGPORT=radio' afterwards.
But thanks for pointing the problem out. We will do a native fix in
next version.
73, de Tom DL1JBE
--
"Do what is needful!"
Ursula LeGuin: Earthsea
--
_______________________________________________
Tlf-devel mailing list
Tlf-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tlf-devel
