Project

General

Profile

Actions

Bug #6265

closed

QYT KT- 8900R Extra ID is wrong, aborting

Added by J. T. over 5 years ago. Updated about 5 years ago.

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

100%

Estimated time:
Chirp Version:
daily
Model affected:
QYT KT-8900R
Platform:
All
Debug Log:
I read the instructions above:

Description

When attempting to use chirp with a new QYT KT- 8900R, I get a message stating that the "Extra ID is wrong, aborting" I am wondering if they changed the ID for this radio and how to go about getting you the info you require to fix the issue. I only have a 64 bit windows 10 on hand.

Thank you


Files

debug.log (23 KB) debug.log J. T., 11/30/2018 05:04 PM
btech.py (129 KB) btech.py developer version for the QYT KT-8900R, new second id Pavel Milanes, 12/28/2018 09:33 PM
Screen Shot 2018-12-29 at 12.03.40 PM.png (158 KB) Screen Shot 2018-12-29 at 12.03.40 PM.png Ron Biava, 12/29/2018 04:08 AM
debug.log (38.3 KB) debug.log Ron Biava, 12/29/2018 05:02 AM
btech.py (129 KB) btech.py Pavel Milanes, 12/29/2018 10:00 PM

Related issues

Has duplicate Bug #6329: KT-8900RRejected12/28/2018

Actions
Actions #1

Updated by Pavel Milanes over 5 years ago

Hi

It can be a new unknown variant (again...) please repeat the procedure and catch the log and attach it to this issue for reviewing, that will allow us to identify the new second ID...

Cheers from Pavel (driver developer)

Actions #2

Updated by J. T. over 5 years ago

Would have had this to you sooner, but I was near the epicenter of the earthquake in Alaska today. just found my laptop under a pile of stuff still waiting to send...

Thank you for your time.

Actions #3

Updated by Pavel Milanes over 5 years ago

Got it, it seems like a new variant in the wild.

Will process ASAP and came back with a test for you to make.

73 Pavel CO7WT

Actions #4

Updated by J. T. over 5 years ago

Wondering if you need further information :)

Actions #5

Updated by J. T. about 5 years ago

To the 9 people who have emailed me about this. No I have not heard anything back yet. I suggest maybe submitting your debug logs too ? I am just someone who uses chirp, not one of the developers.

Actions #6

Updated by Pavel Milanes about 5 years ago

  • Status changed from New to In Progress
  • Assignee set to Pavel Milanes
  • Platform changed from Windows to All

Hi to all and HNY, sorry for the delay, got busy with daily work + family.

I will process the log & produce a test driver for you to test, stay tuned.

73 Pavel CO7WT

Actions #7

Updated by Pavel Milanes about 5 years ago

Hi to all, please download this dev driver and test it.

How? simple:

Fire chirp, go to Help and tick "Enable developer functions"

Go to File and then "Load Module", and load the attached file

Now chirp has this dev driver in place until you close it.

Test the download/upload and if success save a image of the radio an attach it to this post for future references.

Don't get all for granted if it worked on download/upload, do a deep as possible review to see if there is anything out of place.

Please report back either success/failure and don't forget to attach the debug.log if you get a failure.

Cheers,& HNY to all around!, Pavel CO7WT.

Actions #8

Updated by Ron Biava about 5 years ago

Loaded fix as per above. Got different error message.

Error: 'DynamicRadioAlias' object has no attribute 'id2'

Screenshot attached.

73 & HNY, Ron WB2PKR

Actions #9

Updated by Ron Biava about 5 years ago

Debug.log attached.

Actions #10

Updated by Pavel Milanes about 5 years ago

You are right, that was a typo from my side radio.id2 is wrong it's radio._id2 ;-), test this one with the same procedure.

Sorry for the error.

Actions #11

Updated by Ron Biava about 5 years ago

That worked! I am able to both read from radio and upload to radio. Thanks Pavel. 73 & Happy New Year. Ron WB2PKR

Actions #12

Updated by Pavel Milanes about 5 years ago

Hi Ron,

Glad it worked, take your time and try to test it a little more to check everything is in place.

Then on your comments about "extensive" test (or lack of them, meaning all worked ok) I will push the changes into main Chirp.

73 Pavel CO7WT
Happy New Year to All!

Actions #13

Updated by Ron Biava about 5 years ago

Hi Pavel,

I cant say Ive done a comprehensive regressive test, but I have verified that this fix did not corrupt any of my data in the rig that was having the problem nor the older firmware version of this rig that I have.
All looks good to me.

I have stored memories on 2m, 1.25m and 70cm as well as GMRS, FRS, Marine VHF, FM Broadcast, and some local govt and biz VHF/UHF.
I also have customized my advanced settings.

All appears to be OK with my single config file for this rig when using the fix to connect to the newer firmware as well as an older firmware version of this rig.

Thx. 73 & HNY Ron WB2PKR

Actions #14

Updated by Pavel Milanes about 5 years ago

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

Roger that, going mainstream. Patch in progress...

Actions #15

Updated by Pavel Milanes about 5 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF