<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Jun 10, 2014 at 9:05 PM, Richard Haney <span dir="ltr"><<a href="mailto:rfhaney@gmail.com" target="_blank">rfhaney@gmail.com</a>></span> wrote:<br>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>So Hooray! All is not lost! At least it seems I have not irreparably damaged the radio as I had feared.</div>
</div></blockquote><div><br></div><div>That's good news. <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><br></div><div>But it does seem that a bug fix of CHIRP regarding the problem is in order. However, I have not checked whether this problem is already regarded as a bug that needs fixing.</div>
</div></blockquote><div><br></div><div>Which version of CHIRP are you using? v0.4.0 or any recent daily build should be fine.<br><br>Now that you have the channels and settings saved using the Baofeng software, I would give the RESET a try. The UV-B5/B6 has a weird habit of changing it's cloning behavior based on the radio's settings (changing ACK values and IDENT strings were a real pain during the early development of the initial support).<br>
<br></div></div>Jim KC9HI<br></div></div>