Bug #9459

New QYT kt-8900 "radio identification failed"

Added by Ron Armstrong about 1 month ago. Updated 22 days ago.

Status:Closed Start date:10/20/2021
Priority:Normal Due date:
Assignee:Jim Unroe % Done:

100%

Category:-
Target version:chirp-daily
Chirp Version:daily Platform:All
Model affected:QYT KT-8900

Description

I just purchased a new QYT KT-8900. I have another of these radios as well as others. This radio is giving an error "radio identification failed" when trying to read the radio. I connected my other KT-8900 and it read just fine. I installed the software that came with the radio (not a good app) and was able to read the radio with that software. I upgraded chirp to chirp-daily-20211016-installer and same error.

debug.log (48.6 kB) Ron Armstrong, 10/20/2021 11:11 am

kt8900_mcu_m27184.py (153.1 kB) Jim Unroe, 10/20/2021 11:58 am

QYT_KT8900_20211020.img (16.2 kB) Ron Armstrong, 10/20/2021 12:26 pm

Associated revisions

Revision 3609:d99a439711f5
Added by Jim Unroe 23 days ago

[KT8900] Add MCU version for QYT KT8900

This patch adds an additional MCU version to the QYT KT8900 mobile radio.

fixes #9459

History

Updated by Jim Unroe about 1 month ago

Thank you for the debug.log file. Your KT8900 has an MCU version that CHIRP doesn't know about. I have created a test driver module to see if you can successfully download from your radio. Here is how you use it.

1. Download the kt8900_mcu_m27184.py test driver module and save it to a convenient location.

Note: Be sure to left-click the link and then click the download link near the top of the page that loads. Right-clicking the link to download the test driver module will not work.

2. Load CHIRP
3. Click Help in the menu bar and enable Enable Developer Functions
4. Click File -> Load Module to locate and load the test driver module that was saved in step 1

At this point CHIRP will have a red background to indicate that it is running with an external driver module loaded. With any luck, you should now be able to download from your radio. If successful, please save the newly created tab, unedited, to a CHIRP Radio Images (*.img) file and attach it to this issue so I can use it for further development. If the download fails, close CHIRP and add the debug.log file for me to examine.

Jim KC9HI

Updated by Ron Armstrong about 1 month ago

Thanks for the quick response Jim! and Yay, another new version of MCU LOL. Maybe we have the chip shortage to blame? Anyway, the driver seemed to work fine. I have attached the saved radio image.

Updated by Jim Unroe about 1 month ago

  • Status changed from Feedback to In Progress
  • Assignee set to Jim Unroe
  • Target version set to chirp-daily
  • Platform changed from Windows to All

Thanks for you help Ron. I will try to work up and submit a formal patch. In the mean time just use the temporary test driver module to program your radio.

Jim KC9HI

Updated by Ron Armstrong about 1 month ago

You are welcome. I noticed it was very slow to write to the radio. Slower than my other kt-8900 (which always worked with chirp). Maybe the temp driver is the reason but just wanted to let you know it took almost twice as long to write to the radio.

Updated by Jim Unroe about 1 month ago

Ron Armstrong wrote:

You are welcome. I noticed it was very slow to write to the radio. Slower than my other kt-8900 (which always worked with chirp). Maybe the temp driver is the reason but just wanted to let you know it took almost twice as long to write to the radio.

That has always been a problem with this driver. It will take someone other than me to figure out why it is slow and fix it. Sorry.

Jim KC9HI

Updated by Jim Unroe about 1 month ago

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

Patch submitted. Support will be in the next CHIRP daily build following acceptance of the patch.

Jim KC9HI

Updated by Anonymous 22 days ago

  • Status changed from Resolved to Closed

Applied in changeset d99a439711f5.

Also available in: Atom PDF