Project

General

Profile

Actions

Bug #4665

closed

QYT 8900D Error radio Did not enter clone mode.

Added by oz zz about 7 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
03/24/2017
Due date:
% Done:

0%

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

Description

i am trying to program qyt 8900d radio

and i get this messege

radio did not enter clone mode


Files

debug.log (20.4 KB) debug.log log file oz zz, 03/24/2017 11:27 PM
Actions #1

Updated by oz zz about 7 years ago

i try this in linux ubuntu
and in windows 7
same problem

Actions #2

Updated by Jim Unroe about 7 years ago

  • Status changed from New to Feedback

Attach a debug.log file.

Jim

Actions #3

Updated by oz zz about 7 years ago

how do i do that ?

Actions #4

Updated by oz zz about 7 years ago

i found the log file

Actions #5

Updated by Pavel Milanes about 7 years ago

Hi,

It seems to me (from the log error) like a communication problem (interface problem).

As the radio never get his ident string over the wire; can you check the cable is working properly?

Maybe try to read it with the OEM software to confirm the cable is working ok.

73 de Pavel CO7WT.

Actions #6

Updated by oz zz about 7 years ago

i try that

when i got the device
the driver and softwhre cd was broken

so i download driver and program from qyt web site
it dident work
computer dont recognize the cable
i try in windows 7
windows 10
windows xp
all same problem
the driver i dwonload dont work

so i have no driver for this cable in windows

the error i get is in linux ubuntu

Actions #7

Updated by Jim Unroe about 7 years ago

If you have a USB programming cable, then you are selecting the wrong port. It will look similar to "/dev/tty(something)" but it will have "USB" in it somewhere.

Jim KC9HI

Actions #8

Updated by Pavel Milanes about 7 years ago

Maybe looking this can give you a clue: (For USB Cables)

http://www.miklor.com/COM/UV_GettingStarted.php

73

Actions #9

Updated by oz zz about 7 years ago

i know this link
And I've already tried the solution they give there
I downloaded the driver listed there
Still it does not work

I know what it should look like in Linux
But there is no such option
The computer does not recognize at all that the cable is connected to it

Actions #10

Updated by Jim Unroe about 7 years ago

Like a said above, the port you choose in Linux should be /dev/ttyUSB0. Your debug log shows that you chose /dev/ttyS0 which is incorrect.

In Windows you should be able to go into device manager to see which UART chip is in your programming cable. If it is a Prolific chip, you must downgrade the driver to v3.2.0.0 (v2.0.2.1 for XP). If the programming cable has something other than a Prolific chip, then you must get the latest driver for that chip.

Jim

Actions #11

Updated by oz zz about 7 years ago

what i see is /dev/ttys0 to /dev/ttys31
no /dev/ttyUSB0

When I received the cable the CD with driver software was broken
I went into the site of the radio
And downloaded a driver and software for Windows
It detected the cable and asked to do restart the computer
After restarting
The computer did not recognize the cable anymore
[[[http://www.miklor.com/COM/UV_Drivers.php]]]
I worked according to the instructions of this guide several times without success
There was always an unknown device written
I tried on 4 computers with windows without success
2 computers with windows 7
1 computer with windows 10
and 1 computer with windows xp

in the device Manager I see an unknown device
And not as written in the instructions "usb serial controller" or "prolific usb to serial comm port"
I tried everything it just does not recognize the cable

Actions #12

Updated by Jim Unroe about 7 years ago

Which Linux distribution are you using? I use Linux Mint (a derivative of Ubuntu).

I am beginning to think that the CD is not the only thing broken.

Jim

Actions #13

Updated by oz zz about 7 years ago

i use ubuntu
i think it is the cable

but windows detected the cable at first
so ...

Actions #14

Updated by Bernhard Hailer about 4 years ago

  • Priority changed from High to Normal
  • Chirp Version changed from 0.4.0 to daily
  • Model affected changed from (All models) to QYT KT-8900D
  • Platform changed from Windows to All

Have you been able to resolve your problem?

Actions #15

Updated by Bernhard Hailer over 3 years ago

  • Status changed from Feedback to Closed

No more feedback by submitter.

Actions

Also available in: Atom PDF