Bug #5503

Cannot read/write radio memory: Wouxun KG-UVD1P

Added by Michael Goralski almost 3 years ago. Updated about 1 month ago.

Status:Closed Start date:01/16/2018
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:-
Target version:chirp-daily
Chirp Version:daily Platform:Windows
Model affected:Wouxun KG-UVD1P

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.

read-from-KGUVD1P-error-screenshot.png (10.6 kB) Michael Goralski, 01/16/2018 07:49 pm

read-from-KGUVD1P-error-debug.log (23 kB) Michael Goralski, 01/16/2018 07:49 pm

write-to-KGUVD1P-error-screenshot.png (13.2 kB) Michael Goralski, 01/16/2018 07:49 pm

write-to-KGUVD1P-error-.log (39 kB) Michael Goralski, 01/16/2018 07:49 pm

History

Updated by Michael Goralski almost 3 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.

Updated by Bernhard Hailer 6 months ago

  • Status changed from New to Feedback
  • Target version set to chirp-daily
  • 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 (if you're running MacOS)
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

Updated by Bernhard Hailer about 1 month ago

  • Status changed from Feedback to Closed

No more feedback by submitter.

Also available in: Atom PDF

prevent spam