[chirp_users] COM 5

[Michael Brazier]

Hi Jim.
Thanks for your help Mate.  It has solved that issue and Chirp cloned my radio without any problem (had to change from COM 5 to 4).  Now I plug the UV-5RTP in and it goes to start to upload but then I get "An error has occurred - Radio did not respond.  Something in my brain is telling me I should be doing something else to prepare the radio but since my stroke the brain doesn't always work that well.  Any suggestions would be appreciated.
Kind regards,
Mick.

-----Original Message-----
From: chirp_users-bounces at intrepid.danplanet.com [mailto:chirp_users-bounces at intrepid.danplanet.com] On Behalf Of Jim Unroe
Sent: Sunday, September 20, 2015 11:16 PM
To: Discussion of CHIRP
Subject: Re: [chirp_users] COM 5

On Sun, Sep 20, 2015 at 8:29 AM, Michael Brazier <mikeb1951 at optusnet.com.au> wrote:
> Hi All
>
> I have had Chirp for quite a few years but don’t let that fool you, I 
> know nothing about it.  I purchased two Baofeng UV-5R+Plus radios a 
> while ago and a friend used Chirp to clone his radio and then to set 
> my two up.  I have used it a few times as I have recommended the 
> Baofeng radios to others and then I have used Chirp to clone mine and 
> set theirs up.  I am not sure what has happened but I have updated to 
> a Toshiba laptop, I’ve just updated that to Windows 10,  and I 
> downloaded the latest Chirp today.  It’s been a while since I last 
> used Chirp and a friend has just purchased two Baofeng UV-5RTP radios 
> and asked me to set them up.  When I opened Chirp I opened my radio 
> image file and connected the new radio.  I get a COM 5 port error and 
> that’s it.  I tried hooking my radio up but get the same error.  Not 
> sure whether it’s relevant but I used the same original data cable as I did for my, and others, radios.  Any help would be greatly appreciated.
>
> Kind regards,
>
> Mick.
>

Most programming cables with a Prolific type USB-to-TTL chip require that the user over-ride the incompatible device driver that is automatically installed by Windows with the older Prolific v3.2.0.0
(v2.0.2.1 for Windows XP) device driver. Then when the upgrade to Windows 10 is done, the device driver is updated to that latest
(incompatible) version again. You will have to downgrade it back to the Prolific v3.2.0.0 driver again.

Jim KC9HI
_______________________________________________
chirp_users mailing list
chirp_users at intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
To unsubscribe, send an email to chirp_users-unsubscribe at intrepid.danplanet.com