[chirp_users] debug.log

Mike Raymond
Thu Dec 15 09:22:33 PST 2011


More background:
The driver disks that came with all 3 usb cables were identical and the
three driver files
on them appear to be identical (Prolific so I just installed one.

I individually plugged in and out all 3 usb cables and each reported using

Im guessing now that I may have a defective FT2800 USB cable?? Where do you
suggest I buy another, this one came from Kawa.

I read some scuttlebutt on another forum that the Prolific drivers
are troublesome
on Yaesu transceivers. Know any options?

Thanks again for taking time to help.
73, Mike

On Thu, Dec 15, 2011 at 10:14 AM, Dan Smith <dsmith at danplanet.com> wrote:

> > CHIRP uses COM3, which works well when cloning my Icom 2200H and UV-3A
> > Yes, the driver only appears when the USB cable is plugged in, remove it
> and
> > the driver goes away. Ideas?
> CHIRP needs to be pointed at whatever COM port your cable is showing up
> as. I would not expect all three of the above-mentioned cables to show
> up on the same COM port every time. I'm always confused by Windows'
> seemingly-random behavior, so maybe there's something I'm missing.
> However, I would make sure that you're using what Device Manager shows
> _each_time_ you try a clone.
> Another thing you may try is unplugging your cable and then trying to
> use CHIRP on COM3 again. You should get a different error, and
> immediately. If not, then something other than your FT-2800 cable is
> actually COM3.
> --
> Dan Smith
> www.danplanet.com
> _______________________________________________
> 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/20111215/b9f9aaa2/attachment.html 

More information about the chirp_users mailing list