Bug #5345: Clone failed: Radio did not respond - CHIRP

Actions

Copy link

Bug #5345

closed

Clone failed: Radio did not respond

Added by Stanley Kober about 7 years ago. Updated almost 5 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

Target version:

chirp-legacy

Start date:

11/14/2017

Due date:

% Done:

Estimated time:

Chirp Version:

daily

Model affected:

Wouxun KG-UV3D, TYT UVF1

Platform:

Windows

Debug Log:

I read the instructions above:

Description

Using Prolific driver x64 on Win 10. Driver is PL2303_Prolific_GPS_1013_20090319. Using same USB cable for two years.

Attempts to clone, but get error msg as shown in debug log for both Wouxun KG-UV3D and TYT -UVF1.

Using latest Chirp version.

Files

debug 111417.log (28.6 KB) debug 111417.log

Stanley Kober, 11/14/2017 02:25 PM

Actions

Copy link

Updated by Jim Unroe about 7 years ago

Status changed from New to Feedback

There is no communication from the radio to CHIRP. This is most likely an issue with the programming cable and/or device driver (not CHIRP). If you still think it is a CHIRP issue, run a build from 2 years ago and report back the version that works.

Jim KC9HI

Actions

Copy link

Updated by Stanley Kober about 7 years ago

Ran the build from 2 years ago and same problem. Checked and found a new cable required for Win10. Ordered cable. Received it today and tested it with Wouxun and TYT radios and both worked fine. Thanks. Never was told about new cable.

Actions

Copy link