Bug #5837

Radio Did Not Respond Error.

Added by Tysen Ficklin over 4 years ago. Updated over 2 years ago.

Status:Closed Start date:05/30/2018
Priority:Normal Due date:
Assignee:- % Done:


Target version:chirp-daily
Chirp Version:daily Platform:MacOS
Model affected:Baofeng UV-82HP


This is my first time using CHIRP, and am new to these radios in general. I originally downloaded the application a few months ago but did not have a cable for my radio. At that time, I downloaded the most up to date version of CHIRP and the python runtime. I was able to open the application, but because I didn't have the right cable it did nothing for me.

Today I received my cable (original FTDI cable from Baofeng) and have had no luck with cloning my radio. When I first opened CHIRP, I got a message box informing me of the new daily version. I then downloaded the newest daily version. Then I was getting the "Radio Did Not Respond" error. At one point I had it where I was getting a "radio refused to send block code 0x1ec0" error, but I have since done something where I don't even get that now.

I am using a Baofeng UV82HP with the US2S35 firmware.

Any help would be appreciated. Thank you.

debug.log (23.7 kB) Tysen Ficklin, 05/30/2018 10:18 pm

Related issues

duplicated by Bug #4301: Radio refused to comunicate with Chirp Closed 12/12/2016


Updated by Bernhard Hailer almost 3 years ago

  • Status changed from New to Feedback
  • Priority changed from High to Normal
  • Target version set to chirp-daily
  • Model affected changed from Baofeng UV82HP to Baofeng UV-82HP

It looks like a cable issue. Please refer to these Wiki articles:
CableGuide FTDI OEM Cables
RTSystemsCablesAndMavericks (if you're running MacOS)
Let us know whether you got it to work.

Updated by Bernhard Hailer over 2 years ago

  • Status changed from Feedback to Closed

No more feedback by submitter.

Also available in: Atom PDF