Well, I'll be... It turns out that this was, in fact, a "user too stupid error". Maybe my punishment should be writing the "how to plug in a cable" section of the users' guide which will also include a "hey, did you try cleaning the metal conductors yet?" tip as well.
The helpful advice received here from Jon and Jim did the job though and I successfully got stuff working for my Wouxuns again--I really need to clamp down on that poor little thing now and twist it to one side to make it work. Maybe this kind of plastic shrinks a fair bit over 5 years.
At any rate... Woohoo! Thanks a bunch.
Tyler VA3DGN
On August 4, 2014 7:28:26 PM EDT, Jim Unroe rock.unroe@gmail.com wrote:
On Mon, Aug 4, 2014 at 11:51 AM, Tyler Tidman tyler.tidman@draak.ca wrote:
Dear Chirp Developers:
Back in 2009, I purchased a few Wouxun KG-UVD1P units (firmware
version
unknown) and they used to work quite well with Chirp "stable" up
until
around 2012 or 2013 or so. Now, on various versions of Ubuntu and Debian machines I have tried, Chirp can no longer communicate with
these
radios either to download new data or to upload anything based on an
old
image file. I suspected my programming cables--the drivers and/or
the
firmware faeries.
{snipped}
Thank you and 73,
Tyler Tidman VA3DGN
Tyler,
I agree with Jon. There is no indication of communication in the debug.log. If you left the cable out of the radio you would get the same error. I'd say double check the connection between the programming cable and the KG-UVD1P. You might try a little pressure on the plug while you attempt the download.
Jim KC9HI