[chirp_users] Connecting to my Radio
Chuck Hast
Wed Oct 4 05:59:54 PDT 2017
I just go look in /dev
Here is the result of an ls tty*
kp4djt at kp4djt64:/dev$ ls tty*
tty tty17 tty26 tty35 tty44 tty53 tty62 ttyS12 ttyS21 ttyS30
tty0 tty18 tty27 tty36 tty45 tty54 tty63 ttyS13 ttyS22 ttyS31
tty1 tty19 tty28 tty37 tty46 tty55 tty7 ttyS14 ttyS23 ttyS4
tty10 tty2 tty29 tty38 tty47 tty56 tty8 ttyS15 ttyS24 ttyS5
tty11 tty20 tty3 tty39 tty48 tty57 tty9 ttyS16 ttyS25 ttyS6
tty12 tty21 tty30 tty4 tty49 tty58 ttyprintk ttyS17 ttyS26 ttyS7
tty13 tty22 tty31 tty40 tty5 tty59 ttyS0 ttyS18 ttyS27 ttyS8
tty14 tty23 tty32 tty41 tty50 tty6 ttyS1 ttyS19 ttyS28 ttyS9
tty15 tty24 tty33 tty42 tty51 tty60 ttyS10 ttyS2 ttyS29
tty16 tty25 tty34 tty43 tty52 tty61 ttyS11 ttyS20 ttyS3
Now plug in usb serial port and execute ls tty* again:
kp4djt at kp4djt64:/dev$ ls tty*
tty tty17 tty26 tty35 tty44 tty53 tty62 ttyS12 ttyS21 ttyS30
tty0 tty18 tty27 tty36 tty45 tty54 tty63 ttyS13 ttyS22 ttyS31
tty1 tty19 tty28 tty37 tty46 tty55 tty7 ttyS14 ttyS23 ttyS4
tty10 tty2 tty29 tty38 tty47 tty56 tty8 ttyS15 ttyS24 ttyS5
tty11 tty20 tty3 tty39 tty48 tty57 tty9 ttyS16 ttyS25 ttyS6
tty12 tty21 tty30 tty4 tty49 tty58 ttyprintk ttyS17 ttyS26 ttyS7
tty13 tty22 tty31 tty40 tty5 tty59 ttyS0 ttyS18 ttyS27 ttyS8
tty14 tty23 tty32 tty41 tty50 tty6 ttyS1 ttyS19 ttyS28 ttyS9
tty15 tty24 tty33 tty42 tty51 tty60 ttyS10 ttyS2 ttyS29 ttyUSB0
tty16 tty25 tty34 tty43 tty52 tty61 ttyS11 ttyS20 ttyS3
The one in red is the USB serial port.
As indicated by Fred...
Here is the prefered option if you want a lot more info:
kp4djt at kp4djt64:/dev$ tail -f /var/log/syslog
NOW plug in your USB device and you will get loads of info on it
Oct 4 07:51:21 kp4djt64 kernel: [928738.565964] usb 2-1.7.2: new
full-speed USB device number 9 using ehci-pci
Oct 4 07:51:21 kp4djt64 kernel: [928738.675042] usb 2-1.7.2: New USB
device found, idVendor=067b, idProduct=2303
Oct 4 07:51:21 kp4djt64 kernel: [928738.675049] usb 2-1.7.2: New USB
device strings: Mfr=1, Product=2, SerialNumber=0
Oct 4 07:51:21 kp4djt64 kernel: [928738.675052] usb 2-1.7.2: Product:
USB-Serial Controller D
Oct 4 07:51:21 kp4djt64 kernel: [928738.675054] usb 2-1.7.2: Manufacturer:
Prolific Technology Inc.
Oct 4 07:51:21 kp4djt64 kernel: [928738.675511] pl2303 2-1.7.2:1.0: pl2303
converter detected
Oct 4 07:51:21 kp4djt64 kernel: [928738.678654] usb 2-1.7.2: pl2303
converter now attached to ttyUSB0
Oct 4 07:51:21 kp4djt64 mtp-probe: checking bus 2, device 9:
"/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.7/2-1.7.2"
Oct 4 07:51:21 kp4djt64 mtp-probe: bus: 2, device: 9 was not an MTP device
Oh yes, all of this is done from the command line.
Note, the log file may be different for you depending on the distro. Use
tail -f
to poke around in the different log files. Some like to put it in dmesg,
others in
some other log file. But it will be there somewhere.
On Mon, Oct 2, 2017 at 7:10 PM, Fred Erickson <fredferickson at gmail.com>
wrote:
> On Mon, 2 Oct 2017 18:01:56 +0000 (UTC)
> Rick Begeman via chirp_users <chirp_users at intrepid.danplanet.com> wrote:
>
> > Could not get Debian packages to install on Lubuntu.
> > Installed Debian 9.1 Some kind of nannyware protection layer would
> > not allow sudo. Back to Linux Mint 18.2 AMD64chirp-daily
> > Still looking for a way to ID which USB port I am plugged into.I ran
> > "download from radio" for ttys0 - ttyS10 and got the same message.No
> > USB at the bottom of the menu, ends at ttyS31.
> >
> If you run in a terminal window, journalctl -f or tail
> -f /var/log/syslog in Linux Mint then plug in your USB device, it will
> tell which USB port you are using.
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to Chuck Hast at kp4djt at gmail.com
> To unsubscribe, send an email to chirp_users-unsubscribe@
> intrepid.danplanet.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20171004/6e996ea6/attachment.html
More information about the chirp_users
mailing list