Project

General

Profile

Actions
Copy link

Bug #11601

closed

KT-8900D radio identification failed

Added by Tony Keen about 1 month ago. Updated about 1 month ago.

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

100%

Estimated time:
Chirp Version:
next
Model affected:
QYT KT-8900D CMIIT ID: 2018FP3590
Platform:
Windows
Debug Log:
I read the instructions above:
Yes

Description

Trying to read radio(Describe what you were doing)

radio read(Describe what you expected to happen)

failed to id radio(Describe what actually happened instead)

new radio out of box(Has this ever worked before? New radio? Does it work with OEM software?)

Files

Download all files
config.txt (1.86 KB) config.txt Tony Keen, 10/09/2024 06:49 PM
debug_log.txt (7.06 KB) debug_log.txt Tony Keen, 10/09/2024 06:49 PM
chirp_debug-7fd4osrh.txt (2.96 KB) chirp_debug-7fd4osrh.txt Tony Keen, 10/09/2024 08:06 PM
chirp_debug-xnodo1hv(1).txt (6.64 KB) chirp_debug-xnodo1hv(1).txt Tony Keen, 10/10/2024 07:07 AM
config.txt (2.09 KB) config.txt Tony Keen, 10/10/2024 07:13 AM
debug_log.txt (4.78 KB) debug_log.txt Tony Keen, 10/10/2024 07:13 AM
chirp_debug-7alktbc_(2).txt (5.6 KB) chirp_debug-7alktbc_(2).txt Tony Keen, 10/10/2024 07:16 AM
btech - VC8192.py (181 KB) btech - VC8192.py Jim Unroe, 10/10/2024 05:22 PM
Actions
Copy link Download all files
 #1

Updated by Tony Keen about 1 month ago

[Uploaded from CHIRP next-20241003]

Actions
Copy link
 #2

Updated by Dan Smith about 1 month ago

Why do you have developer mode enabled?

Also, there was no response at all from the radio, so please check your cabling. Almost definitely a connection problem and not a bug.

Actions
Copy link
 #3

Updated by Tony Keen about 1 month ago

i think i loded the wrong buglog attached is updated one

On Wed, Oct 9, 2024 at 10:34 PM Dan Smith redmine@chirpmyradio.com wrote:

Actions
Copy link
 #4

Updated by Jim Unroe about 1 month ago

From both debug.log files, this appears to be a connection problem.

Are you plugging the programming cable into the correct port. Since the data port and the speaker/mic port are side-by-side on the back of the radio, it is easy to plug into the wrong one (don't as me how I know).

Actions
Copy link
 #5

Updated by Tony Keen about 1 month ago

here is debug file from both jacks in the back, can plug cable into another
radio and works fine

On Thu, Oct 10, 2024 at 9:39 AM Jim Unroe redmine@chirpmyradio.com wrote:

Actions
Copy link Download all files
 #6

Updated by Tony Keen about 1 month ago

[Uploaded from CHIRP next-20241003]

using different cable and still same result, radio identification failed and radio shuts off

Actions
Copy link
 #7

Updated by Tony Keen about 1 month ago

here is debug file with completely different cable

On Thu, Oct 10, 2024 at 9:39 AM Jim Unroe redmine@chirpmyradio.com wrote:

Actions
Copy link
 #8

Updated by Jim Unroe about 1 month ago

This final debug log from last programming cable read from the radio. Hang one while I create a driver for you to test.

Actions
Copy link
 #9

Updated by Jim Unroe about 1 month ago

Please test the attached driver module and provide feedback. How to load and test a driver module: LoadingTestModules

Actions
Copy link
 #10

Updated by Tony Keen about 1 month ago

thank you, it works like its supposed to be now

On Thu, Oct 10, 2024 at 8:23 PM Jim Unroe redmine@chirpmyradio.com wrote:

Actions
Copy link
 #11

Updated by Anonymous about 1 month ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100
Actions
Copy link

Also available in: Atom PDF

Copyright 2023 CHIRP Software LLC