[chirp_users] Schedule for Support of Radios

[John LaMartina]

I initially had a bear of a time with my cable.

There's a page on a UV5R website that might help.

Go to the USB Driver Cables section.

  http://www.miklor.com/uv5r

 

My cable with the Prolific clone chip drove me crazy until I loaded the correct driver.  

Hope this helps.

 

John    K3NXU

----------------------------

 

From: chirp_users-bounces at intrepid.danplanet.com [mailto:chirp_users-bounces at intrepid.danplanet.com] On Behalf Of Creede Lambard
Sent: Monday, July 23, 2012 2:33 PM
To: Discussion of CHIRP
Subject: Re: [chirp_users] Schedule for Support of Radios

 

Right, I should have been a bit more clear. As Dan says there are a lot of knockoff Prolific chips out there. In an effort to cut
down on piracy Prolific altered their drivers so that they would work with genuine Prolific chips, but would throw errors and show
up with the dreaded yellow triangle icon in Device Manager if you try to use them with knockoffs. Many many users have reported this
problem on the various lists I subscribe to, and there are workarounds, but all of them are more painful than just buying a cable
with a genuine Prolific chip (or with an FTDI chip, which doesn't seem to have this problem). 

If you have one of these knockoffs no software will work with your cable. And again, if the problem is something different, let us
know and we'll see if we can get you through it.

Cheers,

-- Creede WA7KPK

On 07/23/2012 10:36 AM, Dan Smith wrote: 

Let me ask you a question first: Are you trying to program the radio
with a USB cable that has a Prolific chipset? (This is the most common
cause of not being able to update a radio using Chirp. Not all USB
cables cause this problem, but a significant number do.)

 
Just for clarification here:
 
There is no conflict between CHIRP and Prolific devices. Since the
prolific device is the most prolific (pun intended) it is the most often
copied, and thus there are a *lot* of copies, fakes, and broken drivers
floating around out there. In most cases, a flaky driver or device will
not work for the OEM software, much less CHIRP.
 






_______________________________________________
chirp_users mailing list
chirp_users at intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20120723/760f0c4a/attachment.html