Custom queries

All CHIRP-next Bugs
All CHIRP-next Feature Requests
All closed issues
All open issues
New Model Requests
Open bugs by Developer
Open bugs by Target Version
Potentially Stalled Bugs
Triage Queue

Bug #3547

closed

QYT KT-8900r

Added by Glenn Reardon about 8 years ago. Updated over 7 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Pavel Milanes

Category:

Target version:

0.5.0

Start date:

04/01/2016

Due date:

% Done:

100%

Estimated time:

Chirp Version:

daily

Model affected:

QYT KT8900R

Platform:

All

Debug Log:

I read the instructions above:

Description

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;
Glenn
W1GHR

Files

btech.py (53.1 KB) btech.py

Dev version with support for the QYT KT8900R for testing before inclusion on the daily

Pavel Milanes, 05/16/2016 10:28 AM

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Pavel Milanes about 8 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)

73.

Actions

Copy link

Updated by Glenn Reardon about 8 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

73's
Glenn
W1GHR

Actions

Copy link

Updated by Dale Miller about 8 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.

http://chirp.danplanet.com/attachments/2257/how%20to%20portmon.doc

You can download portmon from here

https://technet.microsoft.com/en-us/sysinternals/portmon.

73's
Dale
KC2CBD

Actions

Copy link

Updated by Mathew Mirabito almost 8 years ago

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

Actions

Copy link

Updated by Pavel Milanes almost 8 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:

save the "btech.py" file attached to this post to where you keep your chirp radio image files¶

click "Help"¶

enable "Enable Developer Functions"¶

click "File"¶

click "Load Module"¶

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:

http://chirp.danplanet.com/projects/chirp/wiki/How_To_Report_Issues

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.

Actions

Copy link