Project

General

Profile

Actions

Bug #9357

closed

qyt08900

Added by rich moc about 3 years ago. Updated about 3 years ago.

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

100%

Estimated time:
Chirp Version:
daily
Model affected:
QYT KT8900
Platform:
All
Debug Log:
I read the instructions above:

Description

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


Files

debug.log (30.1 KB) debug.log rich moc, 09/13/2021 04:59 PM
debug.log (31.1 KB) debug.log rich moc, 09/13/2021 10:49 PM
btech_kt8900.py (153 KB) btech_kt8900.py Jim Unroe, 09/14/2021 07:50 AM
Actions #1

Updated by Bernhard Hailer about 3 years ago

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

Updated by Bernhard Hailer about 3 years 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!

Actions #3

Updated by Jim Unroe about 3 years 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

Actions #4

Updated by rich moc about 3 years ago

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

Actions #5

Updated by rich moc about 3 years ago

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

Actions #6

Updated by Jim Unroe about 3 years 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":https://chirp.danplanet.com/projects/chirp/wiki/How_to_report_issues page located in the CHIRP documentation/wiki area.

Jim KC9HI

Actions #7

Updated by rich moc about 3 years ago

I
hope this is what you where looking for

Actions #8

Updated by Jim Unroe about 3 years 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

Actions #9

Updated by rich moc about 3 years ago

did not work when I chose qyt 8900r

Actions #10

Updated by Jim Unroe about 3 years 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

Actions #11

Updated by Jim Unroe about 3 years 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

Actions #12

Updated by rich moc about 3 years ago

works thanks

Actions #13

Updated by Jim Unroe about 3 years 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

Actions #14

Updated by Jim Unroe about 3 years ago

  • Assignee set to Jim Unroe
  • Target version set to chirp-legacy
Actions #15

Updated by Anonymous about 3 years ago

  • Status changed from Resolved to Closed

Applied in changeset commit:3a346181be1c.

Actions

Also available in: Atom PDF