[chirp_devel] Btech driver and JT2705M radio
M.Sc. Pavel Milanes Costa
Fri Apr 1 00:02:48 PDT 2016
El 31/03/16 a las 18:51, David Fannin via chirp_devel escribió:
> looks like the model that was added for the QYT KT-UV980 has a file_id
> string that overlaps with the JT2705M radio. I'm looking for a
> solution so I can uniquely identify the radio.
>
> The file_id is KTUV980_fp = "H28854".
>
> The JT2705M has the same string at 0x3f70-0x3f75:
> H28854, so the JT file is identified as a KT radio.
>
> Here's the contents from 0x3f70-0x3f9f:
>
> "H288540000000000000000000000HHTYHTY288H28854U880"
>
> For the serial port query/response, here is the JT reponse:
>
> WRITE 55 A5 B5 45 55 45 4D 02
> (ascii) U A5 B5 E U E M 02
>
> READ 06 01 03 06 01 07 04 04 00 00 04 08 00 57 48 4B 4A 48 54 59 32 38
> 38 48 32 38 38 35 34 55 38 38 30 30 30 30 30 30 30 30 30 30 30 30 30
> 30 30 30 30 55
> (ascii) 06 01 03 06 01 07 04 04 00 00 04 08 00 W H K J H T Y 2 8 8 H
> 2 8 8 5 4 U 8 8 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 U
>
> Suggestions?
>
> thanks,
>
Hi David,
We have a problem here, one like the baofeng's with his shared ids...
I have a bunch of radios from BTECH, QYT and WACCOM in the driver. The
BTECH, QYT and WACCOM has a *unique fingerprint* and some times a shared
magic string to enter clone mode, that's not a problem.
But I have detected two IDENTIC clones (as Magic and Fingerprint concerns):
QYT KT8900 <=> Juentai JT-6188
QYT KT-UV980 <=> JetStream JT2705M
The pair QYT KT8900 and Juentai JT-6188 has an extra step on the UPLOAD
just after the second ID read, that require sending a ACK, the QYT
answer back with one byte but the Juentai answer two of them (just like
the BTECH 2501+220 do) this is a little difference but one to notice.
My solution is making all of them hangs under the same denominator until
we figure out how to separate one from the another. Just like the
Baofeng UV-5R do now on the Supported Radios wiki page. With a few more
iterations not covered in the driver (Zastone, etc..) we may encounter
some other clones here to.
See the attached file about the identities of this radios (this is a
improved work that Jim started and proved of great help)
Dan, any advice on this?
73
A curious tip: in some magic strings has dates encoded, and you can see
with the features and use of the magics the evolution of the family if
you pay attention... This is just speculating: so far Waccom Mini-8900
is the oldest and BTECH UV2501+220 and UV5001 gen 2 are the newer.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20160401/384f914d/attachment-0001.html
-------------- next part --------------
Model Magic Ident Fingerprint
=== BTECHS
UV-2501 PP \x55\x20\x15\x09\x20\x45\x4d\x02 ..WHKJ168MINM2C294U880 M2C294
UV-2501 PP2 same as above ..WHKJ168MINM29204U880 M29204
UV-2501 1G same as above ..WHKJ168MINM29204U880 M29204
UV-2501 alpha same as above ..WHKJ168MINBTG214U880 BTG214 <--- ERASED just ONE radio; conflict with UV-5001 2g
UV-2501+220 PP \x55\x20\x15\x12\x12\x01\x4d\x02 MIN125..........M3C281 M3C281
UV-2501+220 1G same as above MIN125..........M3G201 M3G201
--Second ID " 280528"
UV-5001 PP [[[ same as BTECH UV2501 ]]] ..WHKJUV-168V19204U880 V19204
UV-5001 ALPHA same as above ..WHKJUV1688V28204U880 V28204
UV-5001 1G same as above ..WHKJUV-168V19204U880 V19204
UV-5001 2g same as above ..WHKJUV5001V2G204U880 V2G204
UV-5001 2g same as above ..WHKJ168MINBTG214U880 BTG214
=== WACCOM
MINI-8900 \x55\xA5\xB5\x45\x55\x45\x4d\x02 ..WHKJHTY288M28854U880 M28854
=== QYT
KT-UV980 [[[ same as WACCOM Mini 8900 ]]] ..WHKJHTY288H28854U880 H28854
KT8900 \x55\x20\x15\x09\x16\x45\x4D\x02 ..WHKJHTY288M29154U880 M29154
---Second ID " 303688"
=== Juentai
JT-6188 [[[ same as QYT KT8900 ]]] ..WHKJHTY288M29154U880 *M29154* [### clone of QYT KT8900 ###]
---Second ID " 303688"
=== Jetstream
JT2705M [[[ same as WACCOM Mini 8900 ]]] ..WHKJHTY288H28854U880 *H28854* [### clone of QYT KT-UV980 ###]
More information about the chirp_devel
mailing list