<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sat, May 4, 2013 at 4:51 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">> No. This makes no sense because it won't work. Once an image is<br>
> uploaded from another model, these first bytes will be replaced. :(<br>
<br>
</div>You mean if someone takes a VHF/UHF image and blows it into a VHF/220<br>
radio?<br></blockquote><div><br></div><div>Yes <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Sounds like we should always read the first chunk of data from the<br>
radio before we push an image out to it and fail if it doesn't match<br>
what we want. We do this now for the firmware version, right? (see<br>
do_upload() and _get_radio_firmware_version().<br></blockquote><div><br></div><div>Yes.� I believe this is already done when downloading or uploading. I see the "Ident:" in the command window. It displays the data that I think we can match against.<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
I think the right thing to do is subclass the main radio driver for the<br>
220, and stash the byte that we expect to see for each in their<br>
respective classes, so we can compare the driver being used to what the<br>
radio returns.<br></blockquote><div><br></div><div>I think this may be getting in over my head. 'Subclass' is what you did for the F-11, right? I will definitely need help with this. <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Also, we'd need to modify match_model() so that it would load files<br>
with the correct driver.<br>
<span class="HOEnZb"><font color="#888888"></font></span><br></blockquote></div><br></div><div class="gmail_extra">Now that the main features of the UV-B5 are in place and the UV-5R� 'hidden' firmware version as been addressed, I am in a better position to mess with something like this.<br>
<br></div><div class="gmail_extra">Jim<br></div></div>