<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">I too only use a FTDI USB / serial cable with my HT. I use this cable with my Yaesu VX-6 on three separate computers. One workstation and two field laptops. My FTDI cable connects 100% of the time with fail proof HT uploads and downloads. <div><br></div><div>As I read all of the gross Prolific connection failure support requests, I am now wondering why Hams even waste their time in dealing with using Prolific USB / serial cables?</div><div><br><div apple-content-edited="true">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>Pete Mackie</div><div><a href="mailto:kg7ixu@arrl.net">kg7ixu@arrl.net</a></div><div><br></div></div>
</div>
<br><div><div>On Jul 1, 2014, at 8:07 AM, MURS Radio <<a href="mailto:mursradio@gmail.com">mursradio@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">I have previously used cables requiring the Prolific driver for most of my programming. Usually had about a 10-20% failure rate overall when programming or attempting to program even with the correct driver. I now use FTDI cables and no longer have any issues with everything else staying the same (computer, CHIRP version, etc.). The difference was drastic enough for me to toss the old cables.<div><br></div><div><br></div><div>- Rob</div><div><br></div><div><br></div></blockquote></div><br></div></body></html>