[chirp_devel] [PATCH] [th_uv3r] Add support for newer 2.5kHz TYT TH-UV3R

[Eric Allen]

The new UV3R has a somewhat larger memory size, so the two can be
differentiated by len(filedata). Not an ideal solution, but it looks
like the alternative is tracking down every single setting to find the
remaining bits that might be a version. I'll hit up the users list to
see if I can get lucky.

This patch has a couple of bugs and missing features, so I'll submit a
new one momentarily.

-Eric

On Sat, Jan 31, 2015, at 10:26 AM, Dan Smith wrote:
> > I've inherited as much of the functionality as possible from the older
> > firmware, but it appears that the memory layout is quite different. The
> > older firmware uses frequency + offset, whereas the new one uses
> > independent TX and RX frequencies (there's some evidence online that it
> > supports cross-band splits...need to test that). The symptom when using
> > the existing CHIRP support on new radios is that the memory gets blanked
> > out on upload, because there's more memory on the newer units and the
> > layout of individual memories is different.
> 
> Bummer, but that justifies having the different class, so that's fine.
> 
> > I think I have access to an older UV3R, so I may be able to find the
> > model number indication somewhere in memory. Without a few more images
> > from the wild, though, I'd be concerned about hitting the right spot.
> 
> Yeah, we have to be able to detect the images properly (the patch won't
> pass unit tests if not). There is an image in the tree for the older
> one, if you want to take a look in there. Also, the users mailing list
> is a good way to grab a bunch of sample images if you're willing to
> survey them.
> 
> Thanks!
> 
> --Dan
> 
> _______________________________________________
> chirp_devel mailing list
> chirp_devel at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
> Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
> Email had 1 attachment:
> + signature.asc
>   1k (application/pgp-signature)