[chirp_users] FTDI based USB cables.

[Cory (NQ1E)]

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 didn't change the codes, it still works with the RT
software as well.


On Fri, Sep 28, 2012 at 4:04 PM, Harrison Cooper <HCooper at fusionio.com>wrote:

> 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****
>
> ** **
>
> *From:* chirp_users-bounces at intrepid.danplanet.com [mailto:
> chirp_users-bounces at intrepid.danplanet.com] *On Behalf Of *Cory (NQ1E)
> *Sent:* Friday, September 28, 2012 4:54 PM
> *To:* Discussion of CHIRP
> *Subject:* Re: [chirp_users] FTDI based USB cables.****
>
> ** **
>
> 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.****
>
> ** **
>
> 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.****
>
> ** **
>
> Here's what worked:****
>
> ** **
>
> - Download the VCP driver zip file and expand it to a folder -
> http://www.ftdichip.com/FTDrivers.htm****
>
> - Open up the device manager and update the driver for the RT cable device
> ****
>
> - Go though the "let me choose" and "have disk" options to point it at the
> folder where the files were unzipped.****
>
> - Install the driver that shows up even if it warns about it not being
> compatible.****
>
> - The device now shows up as "USB Serial Converter", go to its
> properties/advanced tab and check the box called "Load VCP".****
>
> - Unplug the device and plug it back in****
>
> - A new com port device will show up, but a driver will not load for it
> automatically.****
>
> - Go thought the same process as before to install the driver from that
> unzipped folder.****
>
> ** **
>
> ** **
>
> ** **
>
> On Fri, Sep 28, 2012 at 3:19 PM, D.J.J. Ring, Jr. <n1ea at arrl.net> wrote:**
> **
>
> Are there any cables or cable makers which sell cables that aren't bobby
> trapped?****
>
> ** **
>
> I should have to right to buy cables and use whatever I want with it.****
>
> ** **
>
> If they want to bugger the cables, they should give them away free to run
> with their software.****
>
> ** **
>
> 73****
>
> DR****
>
>
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users****
>
> ** **
>
>
> 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.
>   ­­
>
> _______________________________________________
> 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/20120928/e28fb130/attachment.html