Bug #9357

qyt08900

Added by rich moc about 1 month ago. Updated 29 days ago.

Status:Closed Start date:09/06/2021
Priority:Normal Due date:
Assignee:Jim Unroe % Done:

100%

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

Description

extra ID wrong message tried the add on with no luck please help

debug.log (30.1 kB) rich moc, 09/13/2021 04:59 pm

debug.log (31.1 kB) rich moc, 09/13/2021 10:49 pm

btech_kt8900.py (153 kB) Jim Unroe, 09/14/2021 07:50 am

Associated revisions

Revision 3567:3a346181be1c
Added by Jim Unroe 29 days ago

[KT8900] Add additional '2nd ID' for QYT KT8900

A new 2nd ID was discovered being used for the QYT KT8900 mobile radio. This
patch adds an additional 2nd ID to the list of known IDs for this model.

fixes #9357

History

Updated by Bernhard Hailer about 1 month ago

  • Priority changed from High to Normal
  • Model affected changed from (All models) to QYT

Updated by Bernhard Hailer about 1 month ago

  • Status changed from New to Feedback
  • Model affected changed from QYT to QYT KT8900

We assume that's one of the QYT KT8900 variants? Can you give us any details what you meant by "extra ID wrong message" and "tried the add on"?
Please consult "How To Report Issues" and provide a debug log. Thanks!

Updated by Jim Unroe about 1 month ago

  • Platform changed from Windows to All

I would suspect that the radio has an MCU version that CHIRP is unaware of. Attempt to download from the radio. Close CHIRP and then attach the debug.log file to this issue so the MCU version can be determined.

Jim KC9HI

Updated by rich moc about 1 month ago

how to I attach the debug.log thanks
and where do i find it

Updated by rich moc about 1 month ago

"An error has occurred"
"The extra ID is wrong, aborting"

Updated by Jim Unroe about 1 month ago

rich moc wrote:

how to I attach the debug.log thanks
and where do i find it

How to locate the debug.log file for the 3 supported operating systems (Windows, Linux and macOS) is located on the How to report issues page located in the CHIRP documentation/wiki area.

Jim KC9HI

Updated by rich moc about 1 month ago

I
hope this is what you where looking for

Updated by Jim Unroe about 1 month ago

rich moc wrote:

I
hope this is what you where looking for

Yep. That is what I needed. You are choosing the wrong Model. You are choosing KT8900 and the model that you need to choose is KT8900R.

Jim KC9HI

Updated by rich moc about 1 month ago

did not work when I chose qyt 8900r

Updated by Jim Unroe about 1 month ago

rich moc wrote:

did not work when I chose qyt 8900r

This was useful. Your radio requires the "magic" string used by the QYT KT8900 to initiate the cloning process but responds with the "2nd ID" that CHIRP expects to see from the QYT KT8900R. Let me see if I can develop something that will work with your radio.

Jim KC9HI

Updated by Jim Unroe about 1 month ago

I have put together this custom driver module that should work with your radio when selecting Model: KT8900. Please test it. If your feedback confirms that it works, I will submit a formal patch.

The following explains how to load the custom driver module for testing.

1 save the attached "btech_kt8900.py" custom driver module to a convenient location

Important: left click the file name and then click the "download" link on the following page that loads.

2 open CHIRP
3 click "Help" in the menu bar and enable "Enable Developer Functions"
4 click "File" in the menu bar and select "Load Module" in the list of choices
5 locate and load the file that was saved in step 1

The CHIRP background should now be red. Attempt to download from your radio. If that works, attempt to upload to your radio. Let me know how it works. Add another debug.log file if it doesn't.

Note: This test driver module does not permanently change your CHIRP installation. If you close CHIRP and later on need to access your radio, you will have to load this custom driver module first.

Jim KC9HI

Updated by rich moc about 1 month ago

works thanks

Updated by Jim Unroe 30 days ago

  • Status changed from Feedback to Resolved
  • % Done changed from 0 to 100

A patch has been submitted to support the newly discovered "2nd ID". Support will be in the next CHIRP daily build following acceptance of the patch.

Jim KC9HI

Updated by Jim Unroe 30 days ago

  • Assignee set to Jim Unroe
  • Target version set to chirp-daily

Updated by Anonymous 29 days ago

  • Status changed from Resolved to Closed

Applied in changeset 3a346181be1c.

Also available in: Atom PDF