Project

General

Profile

Actions

Bug #6139

closed

QYT KT-8900D failed to identify radio

Added by Andie Miller over 5 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
10/02/2018
Due date:
% Done:

100%

Estimated time:
Chirp Version:
daily
Model affected:
(All models)
Platform:
Windows
Debug Log:
I read the instructions above:

Description

I am running the most current version of CHIRP: CHIRP daily-20180906
Verified that the cable and radio are working and able to communicate using the mfg supplied software.
After looking at my debug.log (see attached) and searching the current issues it appears to be the same as Bug #6037.
Radio ID appears to be: VC8632
Just bought this radio from Amazon last week.
Can this ID be added to a new daily build soon?


Files

debug.log (23.1 KB) debug.log Andie Miller, 10/02/2018 06:38 PM
btech.py (129 KB) btech.py Add new fingerprint on tthe wild for the QYT KT8900D Pavel Milanes, 10/15/2018 08:30 AM
sessionlog.txt (13.1 KB) sessionlog.txt Session log with new btech module loaded at run time Si Smith, 10/15/2018 09:30 AM

Related issues

Is duplicate of Bug #6037: QYT KT-8900D failed to identify radioClosed08/17/2018

Actions
Actions #1

Updated by Si Smith over 5 years ago

Andie Miller wrote:

After looking at my debug.log (see attached) and searching the current issues it appears to be the same as Bug #6037.
Radio ID appears to be: VC8632 Just bought this radio from Amazon last week. > Can this ID be added to a new daily build soon?

I have had the same issue.

I downloaded the source tarball and in file:
./chirp/drivers/btech.py
Changed lines around 273 to:
# KT8900D (dual band)
#KT8900D_fp = "VC2002" - older code - see next line reported on my new radio
KT8900D_fp = "VC8632"

Then it is a case of setup.py build and install.

Have uploaded/downloaded blocks of memory to this device now.

Si

Actions #2

Updated by Pavel Milanes over 5 years ago

  • File btech.py btech.py added
  • Status changed from New to Feedback
  • Assignee set to Pavel Milanes

Can you please test this attached driver that includes the new fingerprint?

Instructions to do it follows:

  • Download the file to your desktop.
  • Fire Chirp and go to "Help" menu, once there tick the option "Enable Developer Functions".
  • Go to "File" and a new option "Load Module" will show, click it.
  • It will bring a open dialog in which you must find and load the file you downloaded to your desktop.

Now Chirp has this custom dev driver loaded (just until you close it, the change is not permanent), try to read the radio now and please comment the results to validate it and definitive patch to the dev queue.

Cheer, PAVEL, CO7WT.

Actions #3

Updated by Si Smith over 5 years ago

Pavel Milanes wrote:

Now Chirp has this custom dev driver loaded (just until you close it, the change is not permanent), try to read the radio now and please comment the results to validate it and definitive patch to the dev queue.

Hi Pavel,

Tested (with the new type radio) - log attached.
This works as expected (can't test backward compatibility as I don't have one of the older firmware radios).

Best regards,

Si G0FOZ

Actions #4

Updated by Pavel Milanes over 5 years ago

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

Ok Si.

Thanks for your testing, it's backwards compatible already ;) log looks ok.

I'm building the patch, will send it ASAP.

73 Pavel CO7WT.

Actions #5

Updated by Pavel Milanes over 5 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF