Bug #5503: Cannot read/write radio memory: Wouxun KG-UVD1P - CHIRP

Actions

Copy link

Bug #5503

closed

Cannot read/write radio memory: Wouxun KG-UVD1P

Added by Michael Goralski over 6 years ago. Updated over 3 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

Target version:

chirp-legacy

Start date:

01/16/2018

Due date:

% Done:

Estimated time:

Chirp Version:

daily

Model affected:

Wouxun KG-UVD1P

Platform:

Windows

Debug Log:

I read the instructions above:

Description

I receive errors when reading versus writing, happening every time.

Each time I attempt a read from the radio: "Failed to communicate with radio: Failed to read full block (67!-68)"
Each time I attempt a write: "Failed to communicate with radio: Radio did not ack block 48." <-- I note this block seems to change. The previous attempt mentioned block 32 I believe.

I am attaching screenshots and debug log files.

Files

Download all files

read-from-KGUVD1P-error-screenshot.png (10.6 KB) read-from-KGUVD1P-error-screenshot.png		Michael Goralski, 01/16/2018 07:49 PM
read-from-KGUVD1P-error-debug.log (23 KB) read-from-KGUVD1P-error-debug.log		Michael Goralski, 01/16/2018 07:49 PM
write-to-KGUVD1P-error-screenshot.png (13.2 KB) write-to-KGUVD1P-error-screenshot.png		Michael Goralski, 01/16/2018 07:49 PM
write-to-KGUVD1P-error-.log (39 KB) write-to-KGUVD1P-error-.log		Michael Goralski, 01/16/2018 07:49 PM

Actions

Copy link

Updated by Michael Goralski over 6 years ago

Just to note my toubleshooting, I fully reset the radio which did not help. I also verified the install and cable as I have a Wouxun KG-UV8D working just fine with CHIRP.

Actions

Copy link

Updated by Bernhard Hailer almost 4 years ago

Status changed from New to Feedback
Target version set to chirp-legacy
Chirp Version changed from 0.4.0 to daily
Model affected changed from (All models) to Wouxun KG-UVD1P

Have you been able to resolve this on your own since you submitted this?
Have you tried with a recent version since you submitted this?

You said that the same physical cable works on a KG-UV8D, is that correct? This still looks like a cable, connector, or driver issue. Please refer to these Wiki articles:
CableGuide
CableGuide FTDI OEM Cables
[RTSystemsCablesAndMavericks]
Your log says you're using Windows: If you are using a generic cable with a Prolific chip, you will very likely need to downgrade your driver to version 3.2.0.0.
It can be found at http://www.miklor.com/COM/UV_Drivers.php

Actions

Copy link