CHIRP

I wish to add to this posting as I have the same issue. No response from radio or radio refused clone message on both of my UV6 radios and yet this setup works well with all of my UV5R radios and I can get the UV6 downloaded by using the baofeng software. Any thoughts as to why the UV6's won't work?

Let's be clear. Are you talking about the UV-6 or are you talking about the UV-6R? The UV-6R is currently not supported by CHIRP.

If you are indeed talking about the UV-6, then please attach a debug.log file.

"Getting your debug log":http://chirp.danplanet.com/projects/chirp/wiki/How_to_report_issues.

Jim KC9HI

The first thing you need to do is upgrade to a recent daily build. Except for possibly the BF-888s and UV-3R, Baofeng owners should not be using the over 2 year old CHIRP v0.4.1 build. Upgrade, then provide a debug log if it still doesn't work.

Jim Unroe wrote:

The first thing you need to do is upgrade to a recent daily build. Except for possibly the BF-888s and UV-3R, Baofeng owners should not be using the over 2 year old CHIRP v0.4.1 build. Upgrade, then provide a debug log if it still doesn't work.

Ok, updated to build 20160201
same result, "radio did not respond"
and somehow, the program did not write a debug log.

Did you see the "chirp.config" file? It would have been in the same folder.

OK. Your radio did not respond. This can be due to a few things..

1. the 2-pin plug is not fully inserted into the radio. This is a common problem with Baofeng radios (The original UV-6 that was sent to me for CHIRP support had this issue).

2. this radio uses a different "magic" string than the one CHIRP sends to initiate cloning.

3. this radio sends a different response than what CHIRP expects.

If it is 2 or 3, then you need to see if you can program your radio with the OEM software. If you can find an OEM software that works, it can be used to determine what "magic" string is used.

If it is 3, then you will have to capture a session with the OEM software. Using Portmon on a 32-bit Windows computer is a common way of doing this. Another method would be to loan your radio to a CHIRP developer that is willing to look into this issue.

Same problem here.
I bought a UV-6R to some weeks ago, the driver installed on COM3 as USB-SERIAL CH340, but when I try to connect with the CHIRP it appears as if the radio is not connected.
I bought a UV-6R to some weeks ago, the driver installed on COM3 as USB-SERIAL CH340, but when I try to connect with the CHIRP it appears as if the radio is not connected.

Anselmo Toshio Matsukura wrote:

Same problem here.
I bought a UV-6R to some weeks ago, the driver installed on COM3 as USB-SERIAL CH340, but when I try to connect with the CHIRP it appears as if the radio is not connected. I do not know exactly where to get the log information to better understand what is happening.
If you have any tip about this problem I appreciate.
Thank you

This issue is about a UV-6. A UV-6R is a different radio.

This issue for the UV-6 was recently taken care of.

Support for the UV-6R was added last Friday.

Jim KC9HI