Project

General

Profile

Actions

Bug #9323

closed

QYT KT-8900D

Added by Jason Rigsby over 1 year ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
06/16/2021
Due date:
% Done:

100%

Estimated time:
Chirp Version:
daily
Model affected:
KT8900D
Platform:
All

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

debug.log (28.2 KB) debug.log Jason Rigsby, 08/28/2021 08:25 AM
red screen debug.log (33 KB) red screen debug.log Jason Rigsby, 08/28/2021 08:31 AM
debug.log (74.3 KB) debug.log Jason Rigsby, 08/28/2021 05:17 PM
Actions #1

Updated by Jason Rigsby over 1 year ago

Also I appreciate your advise and knowledge on Facebook Baofeng Group Jim, Thanks! KO4MXF

Actions #2

Updated by Jim Unroe over 1 year 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

Actions #3

Updated by Jason Rigsby over 1 year ago

Without red screen driver

Actions #4

Updated by Jason Rigsby over 1 year ago

with red screen using btech_vc3402.py driver

Actions #5

Updated by Jason Rigsby over 1 year 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.

Actions #6

Updated by Jim Unroe over 1 year ago

Jason Rigsby wrote:

Without red screen driver

You didn't cause the error.

Jim KC9HI

Actions #7

Updated by Jim Unroe over 1 year 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

Actions #8

Updated by Jim Unroe over 1 year 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

Actions #9

Updated by Jason Rigsby over 1 year 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.

Actions #10

Updated by Jim Unroe over 1 year 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

Actions #11

Updated by Jim Unroe over 1 year 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

Actions #12

Updated by Anonymous over 1 year ago

  • Status changed from Resolved to Closed

Applied in changeset commit:9eeb8c6088c0.

Actions

Also available in: Atom PDF