<div dir="ltr">Thx Jim!</div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr">Shon R. Edwards, MA, AG (Czech Republic)<br>Amateur call: K6QT<br>1039 N 2575 W<br>Layton, UT, 84041-7709<br>USA<br>E-mail: <a href="mailto:sre.1966@gmail.com" target="_blank">sre.1966@gmail.com</a> <br>Home phone: (801) 444-3445<br>Cell: (605) 209-6064</div></div></div>
<br><div class="gmail_quote">On Wed, Apr 22, 2015 at 3:40 AM, Jim Unroe <span dir="ltr"><<a href="mailto:rock.unroe@gmail.com" target="_blank">rock.unroe@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Wed, Apr 22, 2015 at 12:42 AM, Shon Edwards <<a href="mailto:sre.1966@gmail.com">sre.1966@gmail.com</a>> wrote:<br>
> Am getting this error message "Upload finished, but the 'Other Settings'<br>
> could not be sent because the firmware version of the image ( Ver B82S26<br>
> ) does not match that of the radio ( Ver B82S28 )."<br>
><br>
> Am trying to upload info to a Baofeng UV-82X and getting this message. It's<br>
> possible my CHIRP version may not be new enough. Seems to still transfer<br>
> the frequencies and labels. Not sure what is NOT being transferred because<br>
> of this.<br>
><br>
> Does anyone know what needs to be done to get rid of the error message? Or<br>
> what is not getting transferred? Anything to worry about?<br>
><br>
> Thx,<br>
><br>
> Shon<br>
<br>
</span>The error message means just what it says. You are uploading a CHIRP<br>
Radio Image (*.img) file that was saved from another radio with a<br>
different firmware version into your radio. CHIRP uploads the "main"<br>
memory that has the per-channel data and most settings but stops short<br>
of the "aux" memory which is firmware specific. Until recently it was<br>
considered safe to swap the "main" memory between radios with<br>
different firmware version but still withing the same model family.<br>
But in late 2014 Baofeng made memory layout changes to the "main"<br>
memory so that it is no long safe to exchange the "main" memory among<br>
different firmware versions. If you were using the latest CHIRP daily<br>
build, it would have refused to upload the image because the firmware<br>
version of the data file does not exactly match the firmware version<br>
of the radio.<br>
<br>
To get this error to stop, all you do is download the channels and<br>
settings from your radio to create a tab that is compatible with your<br>
radio. Then you can load the "foreign" image into another tab allowing<br>
you to copy-and-paste the channels from the tab from B82S26 radio to<br>
the tab for your B82S28 radio. Another method, which I prefer, is once<br>
you've download from your radio into a tab, then you use the CHIRP<br>
File -> Import method to import the B82S286 image's channels into the<br>
tab from your radio.<br>
<br>
Jim KC9HI<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>
To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com">chirp_users-unsubscribe@intrepid.danplanet.com</a><br>
</blockquote></div><br></div>