CHIRP

I am having the same exact issues with my QYT-980PLUS, just purchased on 10/21/21, "radio identification failed" OR "radio did not enter clone mode". I downloaded older versions of Chirp and different prolific drivers for the cable, same issue when I read my new radio, I assume they must be using different hardware in newer manufactured 980PLUS. I included a error log, I also saw in a different post that there maybe be a problem with the VC6042 chip, I'm not sure, but the fix from the other post doesn't work here.

Roy's radio has an MCU version that CHIRP is not aware of: VC6042. This radio model has a different front panel layout that what the QYT KT8900D has, so I would imagine that it may or may not have some settings that are common with the 8900D. I would think the best path forward would be to make a separate Vendor/Model selection for the QYT KT-980PLUS. This would make it easier to implement those difference (if there are any).

It is possible that Michael's 3rd radio has the same issue. Michael, a debug.log following a download attempt from the 3rd radio (like the one Roy provided) would assist with determining this. Michael, would you also attach a CHIRP Radio Images (*.img) file from either or both of your first 2 radios that are currently recognized by CHIRP?

Thanks,
Jim KC9HI

I added the VC6042 to the btech.py and it seems to work in developer mode.

Ok I think I fixed it right, had a little help from my son, so I added lines:
KT8900D_fp4 = "VC6042"
and
fileid = [KT8900D_fp4, KT8900D_fp3, KT8900D_fp2, KT8900D_fp1, KT8900D_fp]

Hi everyone, thank you so much for the feedback and help. I did some searching today and it seems my first two radios were purchased from the same vendor, but the ones after that have been from different vendors as I have tried a total of four different radios so far. Also I noticed even though the radios look and are produced the same they are being advertised a little different in their titles, eg. 75W vs. 50W and also my first two radios (currently programmable with CHIRP) are labeled as a (Gen. 2 version of the radio) but all others don't mention anything about a specific generation so I'm thinking some interface things changed with newer production runs. Anyway, I have included the .img file for my most recent program for the ones that are programmable. Please let me know if there's anything else you need from me or anything I can do to help. I greatly appreciate all the help.

Thanks! Mike

I have created my proposal as a test driver module to see if you can successfully download from and upload to your radio. It uses the Vendor: QYT / Model: KT980Plus selections. Here is how you use it.

1. Download the btech_kt980plus.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.

1. Load CHIRP
2. Click Help in the menu bar and enable Enable Developer Functions
3. 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. This does not permanently change your CHIRP installation in any way. Once you close CHIRP, you will have to reload the test driver module again before you can program the QYT KT980Plus with "VC3402" MCU version.

Try it to see if it works. Also try the (2nd) driver (btech.py) that Roy attached. It uses the QYT / KT8900D selections. Let me know which driver you prefer.

Jim KC9HI

Patch submitted. Support for this radio (Vendor: QYT / Model: KT980PLUS) will be in the next CHIRP daily build following acceptance.

Jim KC9HI