[chirp_devel] help needed
Tom Masterson
Tue May 10 14:26:40 PDT 2016
It is a radio from Rugged Radios that is made by Baofeng. I was told
(note was told) by the techs that we can program it with chirp as a uv-6.
I am not sure I believe them anymore.
I get the same message when running as root but I suspect that you Jim may
be on the right track as the first message in the log that is of any
importance is that matters is "radio refused clone".
I note that when reading the log it also shows UV-4R even though I have
picked UV-6 not sure if this is a bug or not but definitely a bit
confusing.
Tom
On Tue, 10 May 2016, Jim Unroe wrote:
> Hi Tom,
>
> I assume you are actually talking about a UV-6 and not a UV-B6 or
> UV-6R. They are all 3 quite different radios.
>
>> problem. However if I hook up a Baofeng UV-6 and ask chirp to do a
>> download via ttyUSB0 under Ubuntu 14.04 I get "Radio did not respond"
>> error. Nothing else shows in the log even if I use debug level and
>> verbose settings.
>
> Nearly 4 years ago, Baofeng made a significant change to the UV-5R
> withe the release of BFB291 firmware and at the same time changed the
> "magic" string that initiates the cloning process. CHIRP was written
> to send the original "magic", then if there was no response from a
> pre-BFB291 radio, then the "magic" for the newer radio would be sent.
> Finally if there was no response from a new radio either, then the
> cloning process would end with "no response from the radio.
>
> This worked for a long time. The only change that has been made is to
> now sent the new "magic" first since it is the more likely of the 2
> radios.
>
> The UV-6 is another radio that has 2 "magic" strings depending on the
> age of the radio. Unfortunately, Baofeng made some other slight
> changes to the handshaking done as part of process to initiate the
> clone process, of it it doesn't recognize the 1st magic, it ignores
> the 2nd magic that is sent to it (even if it is the correct magic.
>
> I don't know if putting the new "magic" first in this case would cure
> the problem without breaking the cloning process for the "original"
> UV-6 or not.
>
> Jim KC9HI
>
More information about the chirp_devel
mailing list