<div>No, no... I'm not talking about reprogramming the chip to use the standard codes. I just forced it to use the standard driver (no risk of bricking). This allows it to show up as a standard serial port and work with CHIRP. However, since<i> </i>I didn't change the codes, it still works with the RT software as well.</div>
<br><br><div class="gmail_quote">On Fri, Sep 28, 2012 at 4:04 PM, Harrison Cooper <span dir="ltr"><<a href="mailto:HCooper@fusionio.com" target="_blank">HCooper@fusionio.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple"><div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Just be careful not to put in the wrong vid and pids….you brick it. I was doing development on some USB products last year, and had some of their parts. There was a work around to unbrick, but I don’t recall now what it was. Bricking…meaning that the drivers no longer can see it, so then you can’t run the utility to put it back again. With XP you can sometimes fix it in the .inf file but don’t do it with win7 or win8<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <a href="mailto:chirp_users-bounces@intrepid.danplanet.com" target="_blank">chirp_users-bounces@intrepid.danplanet.com</a> [mailto:<a href="mailto:chirp_users-bounces@intrepid.danplanet.com" target="_blank">chirp_users-bounces@intrepid.danplanet.com</a>] <b>On Behalf Of </b>Cory (NQ1E)<br>
<b>Sent:</b> Friday, September 28, 2012 4:54 PM<br><b>To:</b> Discussion of CHIRP<br><b>Subject:</b> Re: [chirp_users] FTDI based USB cables.<u></u><u></u></span></p><div><div class="h5"><p class="MsoNormal"><u></u> <u></u></p>
<div><div><p class="MsoNormal">I opened up my RT systems cable and found that it has a FTDI chip in it. It's a standard chip, but they programmed it with their own USB vendor ID codes so that it loads their custom driver. I doubt they did this to be mean spirited, but who knows for sure. This gives them the ability to make their software works in a plug-and-play fashion where you don't need to configure any port settings. Just plug in the USB cable and it will automatically find your radio.<u></u><u></u></p>
</div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">However, because it's a standard chip, I was able to get their cable to work by downloading the regular FTDI Virtual Serial Port (VSP) driver and forcing it to be used instead of the default one.<u></u><u></u></p>
</div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">Here's what worked:<u></u><u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">- Download the VCP driver zip file and expand it to a folder - <a href="http://www.ftdichip.com/FTDrivers.htm" target="_blank">http://www.ftdichip.com/FTDrivers.htm</a><u></u><u></u></p>
</div><div><p class="MsoNormal">- Open up the device manager and update the driver for the RT cable device<u></u><u></u></p></div><div><p class="MsoNormal">- Go though the "let me choose" and "have disk" options to point it at the folder where the files were unzipped.<u></u><u></u></p>
</div><div><p class="MsoNormal">- Install the driver that shows up even if it warns about it not being compatible.<u></u><u></u></p></div><div><p class="MsoNormal">- The device now shows up as "USB Serial Converter", go to its properties/advanced tab and check the box called "Load VCP".<u></u><u></u></p>
</div><div><p class="MsoNormal">- Unplug the device and plug it back in<u></u><u></u></p></div><div><p class="MsoNormal">- A new com port device will show up, but a driver will not load for it automatically.<u></u><u></u></p>
</div><div><p class="MsoNormal">- Go thought the same process as before to install the driver from that unzipped folder.<u></u><u></u></p></div></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">
<u></u> <u></u></p></div><p class="MsoNormal" style="margin-bottom:12.0pt"><u></u> <u></u></p><div><p class="MsoNormal">On Fri, Sep 28, 2012 at 3:19 PM, D.J.J. Ring, Jr. <<a href="mailto:n1ea@arrl.net" target="_blank">n1ea@arrl.net</a>> wrote:<u></u><u></u></p>
<p class="MsoNormal">Are there any cables or cable makers which sell cables that aren't bobby trapped?<u></u><u></u></p><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">I should have to right to buy cables and use whatever I want with it.<u></u><u></u></p>
</div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">If they want to bugger the cables, they should give them away free to run with their software.<u></u><u></u></p></div><div><p class="MsoNormal">
<u></u> <u></u></p></div><div><p class="MsoNormal">73<u></u><u></u></p></div><div><p class="MsoNormal"><span style="color:#888888">DR<u></u><u></u></span></p></div><p class="MsoNormal" style="margin-bottom:12.0pt"><br>_______________________________________________<br>
chirp_users mailing list<br><a href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@intrepid.danplanet.com</a><br><a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><u></u><u></u></p>
</div><p class="MsoNormal"><u></u> <u></u></p></div></div></div><br><div class="im"><br>
This e-mail (and any attachments) is confidential and may be privileged. Any unauthorized use, copying, disclosure or dissemination of this communication is prohibited. If you are not the intended recipient, please notify the sender immediately and delete all copies of the message and its attachments.
<br></div>
</div><br>_______________________________________________<br>
chirp_users mailing list<br>
<a href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.danplanet.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
<br></blockquote></div><br>