Chirp ошибка radio did not respond

asked Apr 8, 2018 at 7:50

$begingroup$

For me I didn’t have my radio cable fully pushed into my radio. It took some extra pressure and then it snapped in place. I had to press harder than expected.

$endgroup$

$begingroup$

The most common error is not selecting the correct COM port for the virtualized USB cable.

$endgroup$

A lot of the USB programming cables are not supported by the new Windows drivers that are installed automatically -specifically those with the Prolific PL-2303 USB chip set. You ‘can’ sometimes use them by downloading and installing an older driver. Better to get a proper cable though.

CHIRP Cable Guide

Another common error is related to their quality control. I had a unit (UV-5R+) that wouldn’t work, like that.

Contacted the seller and they sent me a new «body» — and it worked.

So in a case where you are really stuck, I suggest you contact the seller.

answered Apr 11, 2018 at 2:32

answered Jan 15, 2021 at 2:09

$begingroup$

$endgroup$

I found this question while troubleshooting my own problem. Chirp on Arch Linux. There were over 32 COM ports labeled tty0-tty32 that were all throwing errors. Here is what I had to do:

1. Run chirp as root so that I did not run into permission issues using the COM ports. You can get around this by adding your user to the dialout group, but as I did not have this group, I just run as root.
2. Use a USB port that plugs directly into the motherboard, not the front panel, since those function as a hub.
3. Use a legacy 2.0 (not 3.0) USB port
4. Reboot the machine with the USB cable plugged in (not sure if this step is necessary, but I did it during my testing).
5. Now at the very bottom of the list there was a /dev/ttyUSB0 that was not there before.
6. Select a compatible radio from the list. In my case, using Radioddity UV-5RX3 for Baofeng UV-S9PLUS

answered Sep 8, 2022 at 1:04

I do the following:

In the GUI I select Radio > Download from Radio
I select /dev/ttyUSB0 (The only USB device) Baofeng UV-5r
The program looks for input from the radio for a second or two and then spits a dialog box which says: An Error has Occured the radio did not respond

The terminal displays the following:

Clone thread started
»
— Exception: —
Traceback (most recent call last):
File «~/Downloads/chirp-daily-20120630/chirpui/clone.py», line 223, in run
self.__radio.sync_in()
File «~/Downloads/chirp-daily-20120630/chirp/uv5r.py», line 262, in sync_in
self._mmap = _do_download(self)
File «~/Downloads/chirp-daily-20120630/chirp/uv5r.py», line 180, in _do_download
data = _do_ident(radio)
File «~/Downloads/chirp-daily-20120630/chirp/uv5r.py», line 136, in _do_ident
raise errors.RadioError(«Radio did not respond»)

RadioError: Radio did not respond¶

Clone failed: Radio did not respond
Clone thread ended
— Exception Dialog: Radio did not respond —

None¶

• Status changed from New to Feedback

I used the vendor software once and then tried Chirp. I get the same error using chirp.
I went back to the vendor software and it doesn’t find the radio either.
How can we confirm that the USB cable is still working?

Also, radio seems to reset after the read is tried. So it would appear that data is getting to the radio
but not back to the program.

Tnx, WB9VXY

One more observation. If I use GTKterm to talk to the radio when I send a break I get the LED on the radio to flash RED and I get a bunch
of binary characters back. Doesn’t appear that they are the same each time.

If I send the 50 bb ff 01 25 98 4d init string I see a brief blink of the RED led but no characters appear in the GTKterm window.

Tnx,
T3

Sorry for so many posts. I keep giving up and then thinking of «one more thing» to try.
So, I shorted from the Ring of the 2.5mm to the Sleeve of the 3.5 mm connector
which according to the web is TX to RX.
When I open the port with GTKterm I see what I type echoed back on the screen. Echo goes away
when I loose the short.
At one point with GTKterm I started getting the 0x06 answer back from the radio then it went
away and I have not been able to get it back.

Maybe a bad connection to the sleeve on the connector or ??

Gave up, unplugged everything, turned off radio. Tried again in the morning and it worked first time,
reading and writing.

Unplugged and tried again and couldn’t read. Re-plugged and all was good.

WB9VXY

Better late than never:
On Windows 7 , using a cheap knock-off cable, I found that the cable used a (probably fake) Prolific PL2303 USB-to-Serial adapter. Windows installed the latest driver, but I had to manually install an older version of the driver (v. 3.4.25.218) in order to get the software to communicate with the radio. Once I manually installed the software, everything worked fine.

• Status changed from Feedback to Closed
• Chirp Version changed from 0.2.2 to daily
• Model affected changed from (All models) to Baofeng UV-5R

Issues seem to have been resolved. No more traffic on this ticket.