Bug #3699: QYT-UV980 did not enter clone mode - CHIRP

Actions

Copy link

Bug #3699

closed

QYT-UV980 did not enter clone mode

Added by James Edwards about 9 years ago. Updated almost 5 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

Target version:

Start date:

05/31/2016

Due date:

% Done:

Estimated time:

Chirp Version:

daily

Model affected:

QYT UV-980

Platform:

Windows

Debug Log:

I read the instructions above:

Description

Error message reads "Radio did not enter clone mode"
CHIRP daily-20160531

Contents of debug file ,, for full text see attached debug.log
[2016-05-31 18:45:43,326] chirp.logger - DEBUG: CHIRP daily-20160531 on WinVista/7 (Python 2.7.10)
[2016-05-31 18:45:43,358] chirp.directory - INFO: Registered Alinco_DR03T = DR03Radio
[2016-05-31 18:45:43,358] chirp.directory - INFO: Registered Alinco_DR06T = DR06Radio
....
Snip see debug.log for missing text if you need it.
....
[2016-05-31 18:45:43,451] chirp.ui.mainapp - INFO: Skipping existing stock config
[2016-05-31 18:45:43,451] chirp.ui.mainapp - INFO: Skipping existing stock config
[2016-05-31 18:45:43,451] chirp.ui.reporting - DEBUG: Checking for updates
[2016-05-31 18:45:43,624] chirp.ui.reporting - DEBUG: Server reports version daily-20160531 is latest
[2016-05-31 18:47:30,769] chirp.ui.mainapp - DEBUG: User selected QYT KT-UV980 on port COM3
[2016-05-31 18:47:30,862] chirp.ui.clone - DEBUG: Clone thread started
[2016-05-31 18:47:33,160] chirp.ui.common - ERROR: -- Exception: --
[2016-05-31 18:47:33,160] chirp.ui.reporting - DEBUG: Reporting exception
[2016-05-31 18:47:33,160] chirp.ui.common - ERROR: Traceback (most recent call last):
File "chirp\ui\clone.pyo", line 238, in run
File "chirp\drivers\btech.pyo", line 813, in sync_in
File "chirp\drivers\btech.pyo", line 577, in _download
File "chirp\drivers\btech.pyo", line 488, in _do_ident
RadioError: Radio did not enter clone mode

[2016-05-31 18:47:33,160] chirp.ui.common - ERROR: ----------------
[2016-05-31 18:47:33,160] chirp.ui.clone - ERROR: Clone failed: Radio did not enter clone mode
[2016-05-31 18:47:33,221] chirp.ui.clone - DEBUG: Clone thread ended
[2016-05-31 18:47:33,221] chirp.ui.reporting - DEBUG: Reporting model usage: QYT_KT-UV980,download,True
[2016-05-31 18:47:33,221] chirp.ui.reporting - DEBUG: Reporting exception
[2016-05-31 18:47:33,221] chirp.ui.inputdialog - ERROR: --- Exception Dialog: Radio did not enter clone mode ---
[2016-05-31 18:47:33,221] chirp.ui.inputdialog - ERROR: Traceback (most recent call last):
File "chirpw", line 67, in
AttributeError: 'NoneType' object has no attribute 'split'

[2016-05-31 18:47:33,221] chirp.ui.inputdialog - ERROR: ----------------------------

Files

debug.log (17.7 KB) debug.log

QYT-UV980 will not enter clone mode

James Edwards, 05/31/2016 05:57 PM

Actions

Copy link

Updated by James Edwards about 9 years ago

Er just re-read the Bug Report and it is a QYT KT-UV980 radio with a new "Windows 10" compatible programming cable.

Actions

Copy link

Updated by Pavel Milanes about 9 years ago

Status changed from New to Incomplete
Assignee set to Pavel Milanes

Hi, This can be as simple as a cable not working properly or a new variant of this radio, please check the cable is working with other radio model to clear this issue.

If the cable is working then it can be a new variant on the wild, can you please create a serial log for this particular radio with the OEM software?

Instructions about how to doit can be found here: http://chirp.danplanet.com/attachments/2257/how%20to%20portmon.doc

Actions

Copy link