Actually using a FTDI cable. I do have one with profilic chip, but no luck with it.

Allen Stines
Assistant Chief BPVFD
Deacon at Walnut Freewill
828-712-6554

On Mon, Mar 19, 2018, 19:44 Jim Unroe <rock.unroe@gmail.com> wrote:
On Mon, Mar 19, 2018 at 7:22 PM, Allen Stines <duckettham@gmail.com> wrote:
> Here is the debug log.
>

Thanks. I don't see a response. I would look for a problem with the
programming cable.

Looks like you are running windows. If device manager shows that the
programming cable was manufactured with a Prolific type USB-to-TTL
chip, you may have to download, install and select an older Prolific
v3.2.0.0 device driver. Most Prolific chips (nearly 100%) in
programming cables are unauthorized copies and the device driver
supplied by the Prolific company to Microsoft and auto installed by
Windows is designed to not work with counterfeit chips.

http://www.miklor.com/COM/UV_Drivers.php

I keep several Prolific device driver version installed for testing
for genuine Prolific chips (they are very rare). The v3.2.0.0 is the
one I use on a daily basis because it works with both genuine and
counterfeit chips.

Jim KC9HI
_______________________________________________
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to duckettham@gmail.com at duckettham@gmail.com
To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com