<div dir="rtl"><div dir="ltr">i wish i had the capability to program even less complicated missions!! that's why i would thank someone who can..</div><div dir="ltr"><br></div><div dir="ltr">can you please be more specific about the step by step stages to create a master image, edit it and import it.</div><div dir="ltr">thanks</div></div><div class="gmail_extra"><br><div class="gmail_quote"><div dir="ltr">2016-01-25 1:12 GMT+02:00 Jim Unroe <span dir="ltr"><<a href="mailto:rock.unroe@gmail.com" target="_blank">rock.unroe@gmail.com</a>></span>:</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Sun, Jan 24, 2016 at 5:25 PM, Amnon Zohar <<a href="mailto:amnon.zohar@gmail.com">amnon.zohar@gmail.com</a>> wrote:<br>
> i have 2 baofeng radios<br>
> 1 is UV-5RA<br>
> the other is UV-5RA+<br>
> they look a little different, but basically they are the same<br>
> both show 297 as firmware ver when put on with 3 pressed<br>
> only when read with chirp i can see that 1 is really 307 and the other is<br>
> 311!<br>
<br>
</span>Since BFB299, the [3] key + Power-on message is no longer the "real"<br>
firmware version.<br>
<span class=""><br>
><br>
> i cannot upload to one radio what i downloaded from the other because<br>
> firmware versions are different!<br>
> therefore i have to program each one seperately! which is preaty annoying!!<br>
> i do not see any differace in data formation!<br>
> if i remember right it was not like that on previous versions of chirp<br>
<br>
</span>You can thank Baofeng for this.<br>
<span class=""><br>
><br>
> when i use the radio to radio cloning cable it works well so it is weired<br>
> that under chip it doesnt.<br>
> did chirp programmers preferred giving us a hard time just to be on the safe<br>
> side??<br>
<br>
</span>Radio to radio cloning does not dump the whole memory of one radio<br>
into the other. The memory layouts between versions are not the same.<br>
The latest firmware versions have removed the radio-to-radio cloning<br>
because of the main memory layout changes.<br>
<span class=""><br>
> i will thank the one that will go through the trouble to check which<br>
> firmware versions are actually compatible and allow uploading and which are<br>
> not and do not allow it.<br>
> i know it is easier to compare version numbers and decide. but i believe<br>
> easy should be kept for the user not for the programmer.<br>
> i really hope someone take the job.<br>
> or at least tell me which older version of chip did not check the firmware<br>
> version. or checked the wrong version field which shows 297 for both<br>
<br>
</span>CHIRP is open source. You are welcome to take this on.<br>
<span class=""><br>
><br>
> what is the meaning of the message read with power on+6?<br>
><br>
<br>
</span>It is a date. Your guess is as good as mine as to what it represents.<br>
<br>
All you have to do is edit the "master' image for 1 radio and import<br>
it into the image of the other radios. I use the image from my 2012<br>
UV-5R as my master image and import it into my BF-F8HP, UV-82, UV-82C,<br>
UV-82HP and Wouxun KG-UV6D.<br>
<br>
Jim KC9HI<br>
<div class="HOEnZb"><div class="h5">_______________________________________________<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" rel="noreferrer" 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>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Amnon</div>
</div>