<br><br><div class="gmail_quote">On Sat, Jan 12, 2013 at 12:34 PM, Dan Smith <span dir="ltr"><<a href="mailto:dsmith@danplanet.com" target="_blank">dsmith@danplanet.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">> I really would appreciate it if you would download images from the TX<br>
> disabled UV-5Rs and email them to be BEFORE doing the tx lockout<br>
> recovery. My email address is: uv5r [at] kc9hi [dot] net<br>
<br>
</div>That's fine, but it would probably be good to file this as a bug and<br>
attach those images there. That makes it easier for you, me, or anyone<br>
else to go back and get them from the ticket archives if we need to try<br>
to reproduce something a year down the road.<br></blockquote><div><br>My mistake. I thought I was replying to a baofeng_uv5r group mesage<br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
> The Miklor website (see the group home page for a link) has a 'TX<br>
> Lockout - Recovery' procedure. It requires using the Baofeng VIP<br>
> programming software. The most recent versions of CHIRP should not<br>
> cause this to occur again.<br>
<br>
</div>Jim, maybe we could create "fixed" images for each firmware version so<br>
that folks can use CHIRP to restore that aux block on their own?<br>
Someone on MacOS that might have been affected by this may not be able<br>
to run the VIP software that easily to resolve it.<br></blockquote><div><br>This is what I had in mind. This was the solution on the Miklor website (back when it was just BFB291 and BFB293) but the recovery files were removed when it was discovered that the VIP software would restore the TX function.<br>
<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Since CHIRP uploads the aux block every time (if/when the firmware<br>
matches), it should just be a matter of uploading that fixed image once<br>
to re-set those values. Might even be easier than finding the VIP<br>
software that matches your firmware version and jumping through the<br>
hoops.<br></blockquote><div><br> I really would like to a CHIRP solution available.<br><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Dan Smith<br>
<a href="http://www.danplanet.com" target="_blank">www.danplanet.com</a><br>
KK7DS<br>
</font></span><br>_______________________________________________<br>
chirp_users mailing list<br>
<a href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.danplanet.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
<br></blockquote></div>Jim<br>