On 6/22/23 20:46, Michael Butash via PLUG-discuss wrote:
Looks like it's just creating a generic usb serial port, so I'd presume you need to tell the program your hardware device serial speed, flow control, bits, etc and have it misconfigured currently it's erroring in that seeing bits it expects returned.  Being legacy serial vs like a hardware sdr, this is not negotiated but rather needs set for your device requirements usually, but depending on your hardware that might not always be the same.
There's no way in CHIRP to set any of this.  It gives me the option to set a port.  My options are /dev/ttyS0 - ttyS31 and /dev/ttyUSB0.
Also make sure the port is actually running on /dev/ttyUSB0 and not USB1 or other, I've had this happen if a cable gets yanked or wiggled causing the device to reset too quickly and is already in use.  Check using "dmesg | grep usbTTY" to make sure the number.

dmesg | grep usbTTY provided no results, but "dmesg | grep usbTTY" returned the following:
[19805.739059] usb 3-4.3: pl2303 converter now attached to ttyUSB0

-mb


On Thu, Jun 22, 2023 at 4:37 PM Jim via PLUG-discuss <plug-discuss@lists.phxlinux.org> wrote:

    I'm in need of help with Chirp on Kubuntu 22.04.  CHIRP is a program
    that allows for easy programming of a transceiver and for backing
    up the
    configuration of the radio in question.  I've used it before I
    upgraded
    to 22.04 and it worked.  Now it doesn't.  I have the port set to
    /dev/ttyUSB0.   I give CHIRP the correct vendor and model
    information.
    Then I click download.  Chirp shows nothing, but the radio says TX
    and a
    progress bar then Clone OK when it's done.  This is what should
    happen.
    However Chirp should also show a progress bar.  However it does
    nothing.  Instead it give me a dialog box that says:

    Error communicating with the radio

    module 'collections' has to attribute 'Callable"

    This suggests to me that Chirp is sending data to the radio that
    tells
    it to send its data to Chirp, but it acts like the computer isn't
    able
    to receive it.  Does anyone know how to fix this?


    Thanks.

    ---------------------------------------------------
    PLUG-discuss mailing list: PLUG-discuss@lists.phxlinux.org
    To subscribe, unsubscribe, or to change your mail settings:
    https://lists.phxlinux.org/mailman/listinfo/plug-discuss


---------------------------------------------------
PLUG-discuss mailing list:PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
https://lists.phxlinux.org/mailman/listinfo/plug-discuss
---------------------------------------------------
PLUG-discuss mailing list: PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
https://lists.phxlinux.org/mailman/listinfo/plug-discuss

Reply via email to