Bug #3547

QYT KT-8900r

Added by Glenn Reardon over 6 years ago. Updated about 6 years ago.

Status:Closed Start date:04/01/2016
Priority:Normal Due date:
Assignee:Pavel Milanes % Done:


Target version:0.5.0
Chirp Version:daily Platform:All
Model affected:QYT KT8900R


Okay, Not sure what is going on but, I can not get the program cable to be recognized with my computer. Chirp program say's that it will work with, windows 10 which I am running. I have tried a number of times to, program it by manual input following the directions, and it does not work at all. Not trying to sound like a jurk but, WTF is going on or, what am I not doing right. Have a TYT TH-8900R quad band, and same thing. Cable will not work but, easy to program by mic and able to save without a problem. Any help would be great.

Many Thanks;

btech.py - Dev version with support for the QYT KT8900R for testing before inclusion on the daily (53.1 kB) Pavel Milanes, 05/16/2016 10:28 am

Associated revisions

Revision 2705:0b783c961bb8
Added by Pavel Milanes over 6 years ago

[PATCH][KT8900R] Initial support for the QYT KT8900R, fixes #3547

This radio is like the BTECH UV-2501+220 but it has the 220 band
in the Chinese area (240-270 Mhz) well outside the USA ham band.

This is the initial support patch for this radio, it may need
further work on the settings part.

Revision 2706:41195d73360b
Added by Pavel Milanes over 6 years ago

[PATCH][KT8900R] Settings fix about the 220Mhz band, fixes #3547

Now we have two of this radios that has 220/240 Mhz support in the
base class and we need to validate the freq ranges for each one of
them, this patch is to realize that.

Thanks to Jim Unroe for the help with it.

Revision 2712:1bf5865b79b2
Added by Pavel Milanes over 6 years ago

[PATCH][QYT KT-8900R] Add support for a new variant, fixes #3547

A new variant of this radios was found, this patch adds support for it.

All points that the previously found version was Generation 2 and this
new one is from Generation 1 as the ID string shows, this patch also
name the versions correctly.

Revision 2716:ea08d8668049
Added by Pavel Milanes over 6 years ago

[PATCH][KT-8900R] Add a new discovered variant, fixes #3547

A new variant of this radio was found on the wild.

Also my IDE (Geany) has a strict policy for leading spaces,
so it removed automaticaly some of them.


Revision 2720:31a90dc3a63d
Added by Pavel Milanes over 6 years ago

[PATCH][KT-8900R] Fix the second ID to cope with a new variant, fixes #3547

The latest added variant has the second ID without the leading spaces, instead it's filled with '123456'

We removed the leading spaces as the ID is the same of the others but they changed the leding spaces.


Updated by Pavel Milanes over 6 years ago

  • Status changed from New to Feedback
  • Assignee changed from Glenn Reardon to Pavel Milanes
  • Chirp Version changed from 0.4.0 to daily

Hi Gleen,

You mentioned that Windows 10 does not recognize your cable maybe this is the root of the problem, well there is a known bug with the prolific cables (roughly 90% of the cables out there) and Windows updating the driver to the latest version that will render the cable unusable, you have to apply a trick to downgrade the driver version if it's the case.

Please check the miklor site (www.miklor.com/COM/UV_Drivers.php) for instructions on how to do that, here on the wiki there is also a lot of info about it, just search for "prolific driver"

Then you mention two different radios, the QYT KT8900R in the issue subject that is not supported in Chirp by now, we support the QYT KT-8900 not ending in "R" model (we need a serial capture to get your radio supported, see this post about how to do it: http://chirp.danplanet.com/issues/2673#note-38) and you also mention the TYT TH-8900R that is also not supported by chirp (unless you want to say the TYT TH-9800)


Updated by Glenn Reardon over 6 years ago

Ok I have gotten both radios serial numbers for you. I hope this will help solve the problem.

TYT: S/N1501A50136 FCC ID PODTH8900
QYT: Model #HD2510H125 2015/11


Updated by Dale Miller over 6 years ago

He needs you to capture the upload and download from the radio with the OEM software.
You do this using portmon and it has to be using a 32 bit computer.
Portmon will not work on a 64bit computer.


You can download portmon from here



Updated by Mathew Mirabito over 6 years ago

I have attached a portmon to issue - http://chirp.danplanet.com/issues/2673

Updated by Pavel Milanes over 6 years ago

  • File btech.py added
  • Status changed from Feedback to In Progress
  • Priority changed from Urgent to Normal
  • % Done changed from 0 to 50
  • Model affected changed from (All models) to QYT KT8900R
  • Platform changed from Windows to All

Thanks to Mattew Mirabito for the logs, I have a dev version for you to test with support for this particular radio, please test it and report back any issues.

To try it you must follow this steps:
  1. save the "btech.py" file attached to this post to where you keep your chirp radio image files
  2. click "Help"
  3. enable "Enable Developer Functions"
  4. click "File"
  5. click "Load Module"
  6. find and load the "btech.py" file that was saved in step 1

Note: This special test module only temporarily changes your CHIRP. You must load this module every time you load CHIRP.

I need your success or failure story to validate this solution, I will need the debug.log of the failure stories; In this link you will find how to find the debug.log file:


Note: The debug.log is configured to full debug power, so it will be huge compared to a normal one, please zip it before uploading.

73 Pavel CO7WT.

Updated by Pavel Milanes over 6 years ago

  • File deleted (btech.py)

Updated by Pavel Milanes over 6 years ago

Developer version of the btech.py posted with the above post was deleted because it contains a bug, please try this one instead.

Sorry for the inconvenience.

Updated by Pavel Milanes over 6 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 50 to 100

Tested, patched and in the daily by now, so this item will be marked as resolved.

73 Pavel CO7WT.

Updated by Pavel Milanes about 6 years ago

  • Status changed from Resolved to Closed

And after 2 months with no issues it's Closed now.

Also available in: Atom PDF