[chirp_users] Wrong Kenwood radio, ID or unknown variant, see LOG output.

[Pavel Milanes Costa]

Playing with the OEM software I can't find a variant that identifies as 
this:

"P3720\x06\xfb\f1"

Gene, please can you describe the radio, in frequency range, number of 
channels, add on boards etc?

I'm thinking like Jim, maybe this is a custom or special model?

Or the two last bytes means something I haven't deciphered yet?

Maybe options included? Scramber? trunking?

If so then we must about to match that two last bytes...

I'm waiting for a borrowed TK-272G handy radio to make some tests.....

Cheers to all...


El 11/05/18 a las 15:24, Jim Unroe escribió:
> On Fri, May 11, 2018 at 10:16 AM, Pavel Milanes Costa <pavelmc at gmail.com> wrote:
>> Hi Gene,
>>
>> Kenwood TK-372G Driver author here.
>>
> Pavel,
>
> I took a look at the debug log this morning but didn't have time to
> reply (and was hoping that you would also notice this discussion).
>
> It appeared to me that the radio was being read OK. The problem, as I
> saw it, was that CHIRP was receiving "P3720\x06\xfb" from the radio
> but CHIP is expecting "P3720\x06\xff" (the last byte being FB instead
> of FF).
>
> It seems to me that a test driver could be posted that just changes
> the FF to FB to see if the radio could be fully read by CHIRP. If it
> can, then maybe all that is needed would be to add and additional
> "fingerprint" to the driver.
>
> Jim KC9HI
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to M.Sc. Pavel Milanes Costa at pavelmc at gmail.com
> To unsubscribe, send an email to chirp_users-unsubscribe at intrepid.danplanet.com