Hi David.
I have now support locally for a few bunch of other models now, tonight I must redo the patch stack to complete the support as per Dan request.
I will use this info you mention here and the log on the site to add support for the JT2705M, I will look for the issue of the ident of the image on the run_test script.
The bug you mention on the split is fixed locally, wait for the patches.
73
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,
Dave
chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers