[chirp_devel] [PATCH] [New Model] Support for the BTECH Mobile Radios, fixes issue #3015

[Jim Unroe]

On Thu, Mar 24, 2016 at 2:03 PM, Dan Smith via chirp_devel
<chirp_devel at intrepid.danplanet.com> wrote:
>> This is to support a single radio. I believe all we have to do is
>> switch back to the way I had it originally. Add the "ident"
>> fingerprint for this one-of-a-kind radio to the WACCOM/MINI-8900 radio
>> class (since that it sends the "magic" that this radio needs and have
>> the user select that vendor/model combination to program that
>> one-of-kind radio.
>
> Does the radio send a magic during the exchange but just not part of the
> image or something? Or does the software have any "identify" or "test
> communication" function that might cause the radio to barf up an identity?
>
> If you have to, you could always stash something in the image. That
> would give you something you can key off of later, to tell which radio
> they used to download with, before you start your upload. If it's purely
> a detecting-the-radio-model-from-the-file problem, then that will work,
> assuming there's nothing else to go on. It's not as nice, but better
> than nothing, and something we should get in place early before people
> start generating images without that extra data in it.
>

This radio identifies itself with a unique (as far as we know)
fingerprint. It just needs to receive a different string to initiate
cloning. It is apparently the first sample made for BTECH and the
manufacturer didn't get around to changing this string yes so it
happens to require the same string that initiates cloning of the
WACCOM MINI-8900 Plus.

I/we thought that figuring out how to support these 1 or 2 of a kind
radios would help us more rapidly support the many variants that there
seems to be for these radios.

Jim