Bug #9323
closedQYT KT-8900D
100%
Description
I am having the same issue, just received radio this week 8/24/2021.
I just purchased a QYT KT-8900D from amazon, and using current Windows 10 and the OEM programming cable.
This behavior is consistent between 2 different computers.
When I attempt to Download from Radio, setting to the COM port showing a prolific chipset in Device Manager, and setting QYT and KT-8900D in the model selection, and then powering up the unit when indicated by the dialog, after a very short window saying "Identifying the radio...", my radio powers off and a dialog pops up saying "Radio identification failed"
I used the test driver that Jim posted and the radio still failed to identify.
I also attempted to use the other suggested programs for this radio without success.
This is my 2nd QYT KT-8900D and I didn't have this issue with my other one, purchased this one for the car.
Any assistance would be appreciated.
Files
Updated by Jason Rigsby over 2 years ago
Also I appreciate your advise and knowledge on Facebook Baofeng Group Jim, Thanks! KO4MXF
Updated by Jim Unroe over 2 years ago
- Status changed from New to Feedback
Unless you have a programming cable issue, the most likely cause is that your radio has an MCU version that is unknown to CHIRP. Attach a clean debug.log file.
To create a clean debug.log file...
1 Close CHIRP 2 Open CHIRP 3 Cause the error 4 Close CHIRP
How to locate your debug.log file is covered "here":https://chirp.danplanet.com/projects/chirp/wiki/How_to_report_issues.
Jim KC9HI
Updated by Jason Rigsby over 2 years ago
Without red screen driver
Updated by Jason Rigsby over 2 years ago
- File red screen debug.log red screen debug.log added
with red screen using btech_vc3402.py driver
Updated by Jason Rigsby over 2 years ago
I have used two different cables. One that came with the new radio and the cable that come with the my other 8900D which programs fine. Both cables product this error.
Updated by Jim Unroe over 2 years ago
Jason Rigsby wrote:
Without red screen driver
You didn't cause the error.
Jim KC9HI
Updated by Jim Unroe over 2 years ago
- Status changed from Feedback to In Progress
Jason Rigsby wrote:
with red screen using btech_vc3402.py driver
You radio has an MCU version which is unknown to CHIRP: VC7062
I will look into getting it added.
Jim KC9HI
Updated by Jim Unroe over 2 years ago
- % Done changed from 100 to 90
Jason, I have a patch ready so submit, but why don't you do a quick test to make sure it will work. Load the driver you have been experimenting with into a text editor. Scroll down to line 248 and change "VC3402" to "VC7062" and save the change. Then load that into CHIRP as a test driver module and see if that works. If you report back as successful, I will submit the patch.
Jim KC9HI
Updated by Jason Rigsby over 2 years ago
Jim, That got the job done!!! I was able to Clone and Write the new program to the radio! Thank you so much for the assistance!!
I attached my log of the successful clone didn't know if you needed to review it.
Updated by Jim Unroe over 2 years ago
Jason Rigsby wrote:
Jim, That got the job done!!! I was able to Clone and Write the new program to the radio! Thank you so much for the assistance!!
I attached my log of the successful clone didn't know if you needed to review it.
Thank you for the followup.
Jim KC9HI
Updated by Jim Unroe over 2 years ago
- Status changed from In Progress to Resolved
- % Done changed from 90 to 100
Patch submitted. Support the for new MCU version will be available in the next CHIRP daily build following acceptance.
Jim KC9HI
Updated by Anonymous over 2 years ago
- Status changed from Resolved to Closed
Applied in changeset commit:9eeb8c6088c0.