[chirp_users] FTDI drivers

Wed Jul 27 19:14:03 PDT 2016

Ken this was how my problem also started out.  Windows did not find the
right driver (or any driver) for the FTDI chip.  When I went to the FTDI
VCP driver site that is listed on the chirp page and ran the bus driver
install from the zip file on Windows 7 then it found the cable and worked
with my GT3.  Granted,  I am not using Windows 10 but this was the behavior
I ran into.  Also as I noted a day or so ago,  the above did not work with
the cheap FTDI chip clones but I bought the PC03 from Baofeng Tech via
Amazon and that cable did work.  The disconcerting part was that Windows
reported that it saw the clone cable and it was working correctly but
trying to use it returned the error that you also got.

Good luck.

Jim Pruitt

On Wed, Jul 27, 2016 at 6:06 PM, Ken Rugaber (KC9QV) <krugaber at gmail.com>
wrote:

> I have a brand new Btech cable PC03 FTDI Cable Dual Pin for programming a
> Baofeng UV-82HP which is also new.  The cable installs fine on the windows
> 10 computer however when using it I  get the radio did not respond error
> message.  Watching the radio display shows a reboot screen after trying for
> a few seconds.  This tells me that there is some communication there.
>
>
>
> I then setup a Wouxon CP210x USB to UART Bridge cable that does the same
> thing and it works just fine.
>
>
>
> These two scenarios follow exactly no matter what radio I try to use them
> on.
>
>
>
> This tells me there is an issue with the Btech cable not plugging in to
> the radios properly.
>
>
>
> I have ordered an additional Wouxon cable.  I’m done playing around.
>
>
>
> Ken
>
> KC9QV
>
>
>
> *From:* chirp_users-bounces at intrepid.danplanet.com [mailto:
> chirp_users-bounces at intrepid.danplanet.com] *On Behalf Of *John LaMartina
> *Sent:* Wednesday, July 27, 2016 7:35 AM
> *To:* 'Discussion of CHIRP'
> *Subject:* Re: [chirp_users] FTDI drivers
>
>
>
> To clarify, I’ve never gotten a bad cable from BaofengTech.
> John
>
>
>
> *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:* Wednesday, July 27, 2016 8:31 AM
> *To:* 'kc6iih'; 'Discussion of CHIRP'
> *Subject:* Re: [chirp_users] FTDI drivers
>
>
>
> Ahh, you are correct. I misread your email.
>
> If you have a cloned chip, yes, like the cloned Prolific, you need the
> backdated driver.
> Here is the link I have to the FTDI drivers.
> http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx
>
>
>
> The clones FTDI chips were found in some of the Arduino  products.
> It looks like they’re slipping into the cable market.
>
> John
>
>
>
>
>
>
>
>
>
> *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 *kc6iih via
> chirp_users
> *Sent:* Wednesday, July 27, 2016 12:57 AM
> *To:* Discussion of CHIRP
> *Subject:* Re: [chirp_users] FTDI drivers
>
>
>
> It doesn't pay to be cheap with the cables .
>
> I have found thru experience that good cables like those from
> www.rtsystems are the best .
>
>
>
>
>
>
>
>
>
> Sent from my Samsung Galaxy Tab®|PRO
>
>
>
> -------- Original message --------
> From: Jim Pruitt
> Date:07/26/2016 9:44 PM (GMT-08:00)
> To: Discussion of CHIRP
> Subject: Re: [chirp_users] FTDI drivers
>
> Hello John.
>
> What you missed (or I did not make clear) was that when I switched cables
> to the real FTDI cable (also says Baoefeng) it worked.  When I went back to
> the other cable (FTDI clone) the same GT3 (UR5 definitions) then it said
> radio was not responding.  The only change was the cable itself.  It works
> now but none of the 4 cheap cables that appear to be FTDI clones do not
> work.  That was why I was looking for the old drivers and info as to which
> drivers worked with the FTDI copies.
>
> I also have an XP machine that I have to set up as well and that will be
> fun.
>
> Thank you.
>
> Jim Pruitt
>
>
>
> On Tue, Jul 26, 2016 at 5:21 PM, John LaMartina <JohnLa at usa.net> wrote:
>
> Jim,
> I don’t believe your issue is driver related.
> When you stated Win7 stated the cable was recognized and everything was
> working, I believe that is correct.
> The cable and driver are not the issue.
>
> The GT3 is more than likely the issue.
> http://www.miklor.com/COM/UV_ErrorMess.php#error1
> Radio did Not Respond is stating the radio isn’t seeing the cable.
>
> You may need to trim the cable or the yellow rubber on the case.
> The lip on the yellow GT3 edge may be preventing some cables to plug in
> completely.
>
> I hope this assists.
>
> John
>
> Miklor
>
>
>
> *From:* chirp_users-bounces at intrepid.danplanet.com [mailto:
> chirp_users-bounces at intrepid.danplanet.com] *On Behalf Of *Jim Pruitt
> *Sent:* Tuesday, July 26, 2016 7:19 PM
> *To:* Discussion of CHIRP
> *Subject:* [chirp_users] FTDI drivers
>
>
>
> I set up my pc for the latest build of Chirp this past weekend.  I ran
> into trouble as I went out and grabbed the (latest) drivers from FTDI as
> suggested.  When I tried to upload the current list from my GT3's it
> reported that they were not responding.  Windows 7 said the cable was
> recognized and everything was working.  I fought this for several minutes
> then switched cables.  Then it worked so the first cable had to have been a
> clone even though it had the Baeofeng stamp on it.
>
> I see some other posts with new users having trouble and it looks similar
> to what I was experiencing until I changed cables.  This cable cost $21
> (Amazon) compared to $3 for the other cables so I am sure others will have
> the non FTDI cables and not know it.  I know that there has been a lot of
> discussion on here in the past about this.  I didn't see a link on FTDI's
> site to get the older drivers that work with clone cables.
>
> Does anyone have that link for the older FTDI drivers that still work with
> FTDI clone cables?  Is there any problem with replacing the new drivers
> with the older ones?
>
> Thank you.
>
> Jim Pruitt
>
>
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to Jim at jpruitt67 at gmail.com
> To unsubscribe, send an email to
> chirp_users-unsubscribe at intrepid.danplanet.com
>
>
>
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to Jim at jpruitt67 at gmail.com
> To unsubscribe, send an email to
> chirp_users-unsubscribe at intrepid.danplanet.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20160727/54622d10/attachment.html 