[chirp_users] Help needed, can't write to Yaesu FT-60

Guy Teague accts at gtweb.org
Fri Sep 28 16:52:27 PDT 2012


very glad you got that working. i think that's the same driver i found
following a link from an emf meter manufacturer, of all things!

i'll be updating from 10.7.5 (lion) to mountain lion soon and i hope the
driver survives the trip.

and yeah, not to get into fanboi territory here, but i've run a mac since
1996 when at a ham flea market i discovered a dos window running on a
powerbook. i've been linux/unix useradmin as well, but that stuff wears you
out and burns you out and you can run ubuntu(64) or indeed nearly and *nix
and windows 7(64) on a mac using vmware anyway. i have to use a windows xp
system for work and things that just won't install at all into a native
window system will fire up right away on the virtual system running on my
mac. it's a better windows than windows!

so i personally can deeply appreciate you wanting to run this on your mac.

/guy

On Fri, Sep 28, 2012 at 5:18 PM, <chirp.cordless at xoxy.net> wrote:

> Cool info! Thank you very much, this clears up some of my confusion.
>
> I remember seeing the custom VID/PID thing when I downloaded
> the FTDI driver a few months ago, but had no idea what it was for,
> and I didn't need it for that unrelated cable application, which presented
> as an FTDI device.
>
> -dan
>
> On Sep 28, 2012, at 2:41 PM, "Robert Terzi - rct at r-t.org"
> <+chirp+cordless+a79d3bb79e.rct#r-t.org at spamgourmet.com> wrote:
>
> > On 9/28/2012 4:58 PM, chirp.cordless at xoxy.net wrote:> Update 9/28/12:
> >> Summary: I have Chirp 0.2.3 working in OSX 10.8.2 with my FT60s using
> an RT
> >> Systems cable. I was able to write to both radios on the first attempt
> with each.
> >
> > Glad to hear things are working for you.  Basically using an FTDI based
> cable
> > solved your problem.
> >
> > The RT Systems cables I've seen are made with FTDI chips.  However they
> > install a custom USB Vendor ID and Product ID (VID & PID) on them, so
> they
> > aren't recognized by the generic FTDI virtual com port drivers.
> >
> > On windows this gives them the advantage that their software is reliably
> > able to find their cable.The user doesn't have to figure out whatcom port
> > got assigned.  The disadvantage for the user is that other software like
> CHIRP
> > work with the cable because it doesn't create a COM port.
> >
> > I believe the Mac driver you installed, is the same FTDI serial
> driverjust
> > with the RT Systems VID and PID instead of the generic ones.
> >
> > There is a utility provided by FTDI, at least for windows that will let
> you
> > change the VID/PID on the chip.So you can set it back to the FTDI default
> > and not worry about needing a special driver if you are ever so inclined.
> > (The downside is you won't be able to use the RT software on windows
> since it
> > will only work with their cable with the custom VID/PID (and the ftdi
> direct driver).
> > This was discussed on this list 6 months to a year ago.)
> >
> >
> > _______________________________________________
> > chirp_users mailing list
> > chirp_users at intrepid.danplanet.com
> > http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> >
>
>
> _______________________________________________
> 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/2a98f8f2/attachment.html 


More information about the chirp_users mailing list