[chirp_users] Baofeng cable

Rick Osgood rposgood at gmail.com
Sun Jan 25 07:22:57 PST 2015


Bill,

Thanks for the reply. I only have the one cable. I am in Key Largo Florida
and the place I bought the cable from is up in Ft. Lauderdale (75 miles)
away. I may call him to see if he will send a replacement. I have tried
this on multiple pc's so am fairly convinced it's the cable.

Rick

On Sun, Jan 25, 2015 at 9:01 AM, Bill Stone <dragntow at wt.net> wrote:

>  Forgive me for jumping in late on this topic and the suggestion may have
> previously been disscussed however have you tried another cable the same as
> the 1 you are having problems with? Does the cable work with other radio's?
> I have had problems in the past with program / rig control cabes with
> static electricity blowing the chip and also onece found a cable with a bad
> souder joint. Sometimes pluging in the cable to PC when running and pluging
> in the cable to the radio when on can create a static charge
> 73 Bill WS5H
>
> ----- Original Message -----
> *From:* Rick Osgood <rposgood at gmail.com>
> *To:* Discussion of CHIRP <chirp_users at intrepid.danplanet.com>
> *Sent:* Sunday, January 25, 2015 6:55 AM
> *Subject:* Re: [chirp_users] Baofeng cable
>
> Thanks for all the suggestions guys... I tried reseating the cable into
> the laptop on all available usb ports and at best it now forces the ht into
> transmit mode. To clarify the other point.... I have loaded the old version
> v3.2.0.0 and will use that if my windows os ever sees the device. I tried
> on my wifes laptop and same results.
>
> Rick
>
>
> On Sat, Jan 24, 2015 at 10:54 PM, D.J.J. Ring, Jr. <n1ea at arrl.net> wrote:
>
>> Download the CHIRP live Linux CD.
>>
>> That is all set up to work.
>> That will confirm the cable works.
>>
>> I think you have two problems.
>>
>> Try the Live CD.
>>
>> David
>>  On Jan 24, 2015 9:44 PM, "Malcolm Larkin" <malcolm.larkin at icloud.com>
>> wrote:
>>
>>>  The only time I had an issue, I entered into the devices section of
>>> the administrative tools and down rated the default serial speed and
>>> haven't had a problem since.
>>>
>>> Malcolm Larkin
>>> VK2FITH
>>>
>>>
>>> On 25 Jan 2015, at 11:39, Tony <ajd at industrynet.net> wrote:
>>>
>>>   Why are you guys repeating the same thing over and over without
>>> actually offering any assistance??
>>>
>>>
>>>
>>> What you said is all true however first you need to get Windows to
>>> recognize the cable.
>>>
>>>
>>>
>>> …..Which only requires that you plug it in.  No drivers required on any
>>> version of windows.
>>>
>>>
>>>
>>> Rick is not even at that point yet!
>>>
>>>
>>>
>>> Once you can see it in device manager you can then load the OLD (2007)
>>> drivers (below) and it will work perfect.
>>>
>>>
>>>
>>> Here is the link to the drivers again:
>>> https://dl.dropboxusercontent.com/u/188372/prolific.driver/PL2303.332102.zip
>>>
>>>
>>>
>>> -Tony
>>>
>>>
>>>
>>> *From:* chirp_users-bounces at intrepid.danplanet.com [
>>> mailto:chirp_users-bounces at intrepid.danplanet.com
>>> <chirp_users-bounces at intrepid.danplanet.com>] *On Behalf Of *John
>>> LaMartina
>>> *Sent:* Saturday, January 24, 2015 8:22 PM
>>> *To:* 'Discussion of CHIRP'
>>> *Subject:* Re: [chirp_users] Baofeng cable
>>>
>>>
>>>
>>> If the cable that is being used has a cloned or counterfeit Prolific
>>> chip, Windows will load the latest Prolific driver.
>>> That driver will recognize the counterfeit chip *and will Fail*.
>>> This is by design to discourage counterfeiters. The only way to get
>>> around it is to do what Jim suggested.
>>> Load a backdated driver. Preferably Win7 Prolific 3.2.0.0 or XP Prolific
>>> 2.0.2.1.
>>>
>>> The needed drivers and explanation can be found at
>>> http://www.miklor.com/COM/UV_Drivers.php
>>> Read carefully FAQ 1 and 2 at the bottom of the page also.
>>>
>>> I hope this assists.
>>>
>>> John
>>> http://www.miklor.com
>>>
>>>
>>>
>>> *From:* chirp_users-bounces at intrepid.danplanet.com [
>>> mailto:chirp_users-bounces at intrepid.danplanet.com
>>> <chirp_users-bounces at intrepid.danplanet.com>] *On Behalf Of *Tony
>>> *Sent:* Saturday, January 24, 2015 8:09 PM
>>> *To:* mikeearls at earthlink.net; 'Discussion of CHIRP'
>>> *Subject:* Re: [chirp_users] Baofeng cable
>>>
>>>
>>>
>>> Any version of Windows will recognize the cable.
>>>
>>>
>>>
>>> You don’t need drivers.
>>>
>>>
>>>
>>> *From:* chirp_users-bounces at intrepid.danplanet.com [
>>> mailto:chirp_users-bounces at intrepid.danplanet.com
>>> <chirp_users-bounces at intrepid.danplanet.com>] *On Behalf Of *Michael D
>>> Earls
>>> *Sent:* Saturday, January 24, 2015 7:50 PM
>>> *To:* 'Discussion of CHIRP'
>>> *Subject:* Re: [chirp_users] Baofeng cable
>>>
>>>
>>>
>>> Tony, you're not helping!
>>>
>>> Until the older driver is installed properly, it won't recognize the
>>> cable.
>>>
>>> Unless every step is followed EXACTLY, the older driver won't be
>>> installed.
>>>
>>> Take it from someone who was convinced that I had followed every
>>> direction, several times.
>>>
>>> When you finally do it right, it will work.
>>>
>>>
>>>
>>> Mike Earls
>>>
>>> AF5MS
>>>
>>> TSRA Life Member
>>>
>>> NRA Benefactor Member
>>>
>>>
>>>
>>> *From:* chirp_users-bounces at intrepid.danplanet.com [
>>> mailto:chirp_users-bounces at intrepid.danplanet.com
>>> <chirp_users-bounces at intrepid.danplanet.com>] *On Behalf Of *Tony
>>> *Sent:* Saturday, January 24, 2015 6:39 PM
>>> *To:* 'Discussion of CHIRP'
>>> *Subject:* Re: [chirp_users] Baofeng cable
>>>
>>>
>>>
>>> He’s not even at the point where drivers are needed.
>>>
>>>
>>>
>>> He can’t even get Windows to recognize the cable.
>>>
>>>
>>>
>>> Repeating “Read the instructions”  over and over without offering any
>>> actual advice is a waste of everybody’s time.
>>>
>>>
>>>
>>> C’mon…
>>>
>>>
>>>
>>> -Tony
>>>
>>>
>>>
>>> *From:* chirp_users-bounces at intrepid.danplanet.com [
>>> mailto:chirp_users-bounces at intrepid.danplanet.com
>>> <chirp_users-bounces at intrepid.danplanet.com>] *On Behalf Of *Jim Unroe
>>> *Sent:* Saturday, January 24, 2015 7:36 PM
>>> *To:* Discussion of CHIRP
>>> *Subject:* Re: [chirp_users] Baofeng cable
>>>
>>>
>>>
>>> Follow the instructions in the guide step by step to select it. If you
>>> don't select it as shown in the guide, Windows will continue to use the
>>> latest driver and the programming cable will continue to fail to function
>>> properly.
>>>
>>> Jim
>>>
>>>
>>>
>>>  _______________________________________________
>>> chirp_users mailing list
>>> chirp_users at intrepid.danplanet.com
>>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>>>
>>>
>>> _______________________________________________
>>> chirp_users mailing list
>>> chirp_users at intrepid.danplanet.com
>>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>>>
>>>
>> _______________________________________________
>> chirp_users mailing list
>> chirp_users at intrepid.danplanet.com
>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>>
>>
>
>
> --
>   Rick Osgood
> 411 Walnut Street #9722
> Green Cove Springs, FL 34023
>
> ------------------------------
>
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>
> ------------------------------
>
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2015.0.5315 / Virus Database: 4189/8719 - Release Date: 12/11/14
> Internal Virus Database is out of date.
>
>
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>
>


-- 
Rick Osgood
411 Walnut Street #9722
Green Cove Springs, FL 34023
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20150125/3365be09/attachment-0002.html 


More information about the chirp_users mailing list