Great!
I also have a uv-9g and which uses an entirely different (weird) cable
but the same FTDI converter - both create ttyUSB0 ports.
On the other hand, my GPS device - which is a RS232 device - uses the
pl2303 converter to create the ttyUSB0 port.
-- CInaed
On 10/28/22 21:29, Julian Macassey wrote:
> On 2022-10-28 at 13:26, K0LNY_Glenn (glenn@ervin.email) wrote:
>
>> That is what I wondered too.
>> I always use USB0 on Linux, and only use the other ports in windows.
>
> When I pop the Baofeng programming adapter into my USB
> port, this appears in /dev/
>
> crw-rw---- 1 root dialout 188, 0 Oct 29 04:33 ttyUSB0
>
>
> But!
>
> When I select Radio > Upload to radio I get the dialogue
> box, which just gives me the /dev/ttyS* options. So, in a wonder
> what will happen when I type in /dev/ttyUSB0 rather than select
> ttyS0 and click OK it uploads my .img file.
>
> There is a clue in my /var/log/syslog output that I
> posted:
>
> + Oct 28 18:07:11 localhost kernel: [218264.066251] usb 3-4: pl2303 converter
> now attached to ttyUSB0
> + Oct 28 18:07:11 localhost mtp-probe: checking bus 3, device 15:
> "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4"
>
> I would be happy to write a note on the various thing to
> check wjen using Linux to set up chirp.
>
> Briefly:
>
> As root enter: tail -f /dev/syslog
>
> Then watching the output (saving with tee if you want)
> see what happens when you plug in your Baofeng cable. This will
> show you what the USB cable is doing.
>
> But also essential is adding the user to /etc/group:
>
> dialout:x:20:{name of user}
>
> At least it's working now.
>
> If wanted I can write up a "Getting Chirp up and running
> in Linux. I do understand that 1. There are many Linux distros
> out there and there are no doubt subtle differences whic may need
> to be checked. 2. There are a ton of radios out there and there
> are no doubt differences.
>
>
>
>> Glenn
>> ----- Original Message -----
>> From: Apostolos Kefalas
>> To: Discussion of CHIRP
>> Sent: Friday, October 28, 2022 1:19 PM
>> Subject: Re: [chirp_users] Linux and chirp
>>
>>
>> ttyS0 is usually a physical rs232 port. Are you sure that your laptop has
>> such a port? Or do you use a usb cable and you should use ttyUSB0???
>>
>>
>>
>>
>> On 28 Oct 2022 20:27, Julian Macassey <jul...@n6are.com> wrote:
>>
>>
>> I am running kubuntu 22.04.1 on a Framework laptop.
>>
>> I have loaded the daily build from flatpak and Chirp
>> comes up when opened.
>>
>> My radio is a Baofeng UV-5RV2+
>>
>> I followed the instructions in:
>>
>> https://chirp.danplanet.com/projects/chirp/wiki/CSV_HowTo
>>
>> + A Clean Start
>> +
>> + If you want to get an empty CHIRP-compatible CSV file, the
>> + easiest way is to let CHIRP create one for you. Here are the
>> + approximate steps for creating an empty file, editing it in an
>> + external editor and opening it back up in CHIRP:
>> +
>> + Start CHIRP
>> + Go to File > New to create an empty CSV file
>> +
>> + Add a memory to the first row, by entering a frequency
>> + such as 146.52
>> +
>> +
>> + Go to File > Export to save the template file to something
>> + ending with a .csv extension
>> +
>> + Open the file in your spreadsheet or external application of
>> + choice, make edits and save
>>
>> + Re-open the file in CHIRP to validate that the format is
>> + still correct, by going to File > Open and choosing your file
>> +
>> + Optionally use File > Import to import the contents of your
>> + CSV file into another radio image
>> +
>>
>> ...
>>
>> + If you have a clone-mode radio, upload the changes back to your
>> + device using Radio > Upload To Radio. If you are using a
>> + live-mode radio, wait until all of the changes finish
>> + synchronizing back to the device by watching the status bar in
>> + the lower right corner of the main window.
>>
>> So, when I plug in my radio, I see the following in
>> /var/logsyslog:
>>
>> ------
>> Oct 28 18:07:10 localhost kernel: [218263.636611] usb 3-4: new full-speed
>> USB device number 15 using xhci_hcd
>> Oct 28 18:07:11 localhost kernel: [218264.061760] usb 3-4: New USB device
>> found, idVendor=067b, idProduct=2303, bcdDevice= 3.00
>> Oct 28 18:07:11 localhost kernel: [218264.061769] usb 3-4: New USB device
>> strings: Mfr=1, Product=2, SerialNumber=0
>> Oct 28 18:07:11 localhost kernel: [218264.061772] usb 3-4: Product:
>> USB-Serial Controller
>> Oct 28 18:07:11 localhost kernel: [218264.061775] usb 3-4: Manufacturer:
>> Prolific Technology Inc.
>> Oct 28 18:07:11 localhost kernel: [218264.064089] pl2303 3-4:1.0: pl2303
>> converter detected
>> Oct 28 18:07:11 localhost kernel: [218264.066251] usb 3-4: pl2303
>> converter now attached to ttyUSB0
>> Oct 28 18:07:11 localhost mtp-probe: checking bus 3, device 15:
>> "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4"
>> Oct 28 18:07:11 localhost mtp-probe: bus: 3, device: 15 was not an MTP
>> device
>> Oct 28 18:07:11 localhost snapd[13154]: hotplug.go:200: hotplug device
>> add event ignored, enable experimental.hotplug
>> Oct 28 18:07:11 localhost mtp-probe: checking bus 3, device 15:
>> "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4"
>> Oct 28 18:07:11 localhost mtp-probe: bus: 3, device: 15 was not an MTP
>> device
>> Oct 28 18:07:13 localhost ModemManager[824]: <info> [base-manager]
>> couldn't check support for device
>> '/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4': not supported by any plugin
>>
>> ---
>>
>> In Chirp I select Radio and slide down to select "Upload
>> to Radio".
>>
>> I get a dialogue box saying:Port /dev/ttyS0, Bofeng,
>> UV5R, I select OK. I get "An error has occurred Could configure
>> port: (5, 'Input/output error')
>>
>> So just in case, I fiddles with the /dev/ttyS0
>> permissions:
>>
>> crw-rw-rw- 1 root dialout 4, 64 Oct 25 11:15 ttyS0
>>
>> So what have I not done? What should I do?
>>
>> Yours
>> GM5LUK
>>
>>
>> --
>> "We can’t be successful unless we lie to customers.” Larry
>> Ellison to Bruce Scott.
>> _______________________________________________
>> chirp_users mailing list
>> chirp_users@intrepid.danplanet.com
>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>> This message was sent to Apostolos at sv1...@raag.org
>> To unsubscribe, send an email to
>> chirp_users-unsubscr...@intrepid.danplanet.com
>> To report this email as off-topic, please email
>> chirp_users-ow...@intrepid.danplanet.com
>> Searchable archive:
>> https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
>>
>>
>>
>>
>>
>> --------------------------------------------------------------------------------
>>
>>
>> _______________________________________________
>> chirp_users mailing list
>> chirp_users@intrepid.danplanet.com
>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>> This message was sent to K0LNY at glenn@ervin.email
>> To unsubscribe, send an email to
>> chirp_users-unsubscr...@intrepid.danplanet.com
>> To report this email as off-topic, please email
>> chirp_users-ow...@intrepid.danplanet.com
>> Searchable archive:
>> https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
>> _______________________________________________
>> chirp_users mailing list
>> chirp_users@intrepid.danplanet.com
>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>> This message was sent to Julian at jul...@n6are.com
>> To unsubscribe, send an email to
>> chirp_users-unsubscr...@intrepid.danplanet.com
>> To report this email as off-topic, please email
>> chirp_users-ow...@intrepid.danplanet.com
>> Searchable archive:
>> https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
>
_______________________________________________
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to arch...@mail-archive.com at arch...@mail-archive.com
To unsubscribe, send an email to chirp_users-unsubscr...@intrepid.danplanet.com
To report this email as off-topic, please email
chirp_users-ow...@intrepid.danplanet.com
Searchable archive:
https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
