Project

General

Profile

Actions

Bug #3821

closed

QYT-8900 Issue - Radio Identification Failed

Added by Chris Little almost 8 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
07/14/2016
Due date:
% Done:

90%

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

Description

Trying the latest CHIRP build to program a new QYT-8900 radio, and I get
the "Radio Identification Failed" error. It consistently fails. I
tried the KT-8900R model, but it failed with "Failed to enter CLONE mode" error.
I don't know if this new radio has different firmware, or defective, or what.
I can loan the radio if needed. I can also try to get what info I can from it with
guidance. The radio seems to connect and download normally, but then
fails just when it should bring up the programming menu. Hopefully
the problem is not between the keyboard and the chair.


Files

CHIRP debug 07142016 KT8900.log (18.7 KB) CHIRP debug 07142016 KT8900.log Chris Little, 07/14/2016 10:40 AM
Actions #1

Updated by Pavel Milanes almost 8 years ago

  • Status changed from New to In Progress
  • Assignee set to Pavel Milanes
  • % Done changed from 0 to 90
  • Estimated time set to 1.00 h
  • Platform changed from Windows to All

Congrats !

You have identified a new QYT KT8900 version, I will post a patch for it ASAP, keep and eye on the new daily of the following days and please report here your success/failure to keep track of the issue.

Tip: We have so far at least six (6) unique variants of the QYT KT8900 radio, that without taking the re-branded ones...

73 Pavel CO7WT.

Actions #2

Updated by Chris Little over 7 years ago

I was able to test the Daily, and it works. I was able to successfully program the QYT-8900, at least this version of the QYT.
I wonder what surprises they will give us in the next version. Thanks for your help!

Actions #3

Updated by Pavel Milanes over 7 years ago

  • Status changed from In Progress to Resolved

The users report it's solved, so be it.

Actions #4

Updated by Pavel Milanes over 7 years ago

  • Status changed from Resolved to Closed

And now it's Closed.

Actions

Also available in: Atom PDF