[chirp_devel] [bj-uv55] patch for initial support - need help from UV-5R experts/testers

[Jens J.]

Thanks Jim.

I see the key is in returning true for "match_model" method on your class when an image is run against all drivers.

I have also taken a first pass at refactoring some of this per-radio logic that I introduced in previous patch into subclass properties. I see some other opportunities to streamline this and make it more generic for forward and backward compatibility. Hopefully will ease the coming onslaught of "Attack of the Radio Clone Clones"

new patch attached... 





On Sunday, November 10, 2013 9:49 PM, Jim Unroe <rock.unroe at gmail.com> wrote:
 





On Sun, Nov 10, 2013 at 8:08 PM, Jens J. <kd4tjx at yahoo.com> wrote:


>Also, I'm trying to understand what to modify so that when opening a radio image file, it will recognize this image as being BJ-UV55.
>
#def _firmware_version_from_data(data, version_start = 0x1838, version_stop = 0x1848):
def _firmware_version_from_data(data, version_start = 0x1938, version_stop = 0x193E):
    version_tag = data[version_start:version_stop]
    return version_tag


You will have to set it up so that is uses "version_start = 0x1938, version_stop = 0x193E" for the BJ55 and "version_start = 0x1838, version_stop = 0x1848" for everything else. I just made a quick substitution as above to check it out and it worked for me.

Jim KC9HI
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20131110/851c2fd9/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bjuv55-initial.patch
Type: application/octet-stream
Size: 9357 bytes
Desc: not available
Url : http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20131110/851c2fd9/attachment-0001.obj