Download a live CD of Ubuntu, chirp works great in Linux.<div><br></div><div>You can boot into the live CD without injuring anything </div><div><br></div><div><a href="http://cdimages.ubuntu.com/releases/precise/release/ubuntu-12.04.1-desktop-amd64+mac.iso">http://cdimages.ubuntu.com/releases/precise/release/ubuntu-12.04.1-desktop-amd64+mac.iso</a></div>
<div><br></div><div>DR</div><div><br></div><div><br>
<br><br><div class="gmail_quote">On Sat, Sep 22, 2012 at 12:25 AM, <span dir="ltr"><<a href="mailto:chirp.cordless@xoxy.net" target="_blank">chirp.cordless@xoxy.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks,<br>
<br>
I can't see what thread you want me to look at, something in the path seems<br>
to have obfuscated it, see below.<br>
<br>
I tried putting the radio in VFO mode, no help.<br>
<br>
So I unloaded the Prolific driver I was using that was from some open source<br>
project, and loaded the one downloaded from the Prolific website you pointed me<br>
at, which at least claims to know about OS X 10.7, and I expect it likely is a<br>
better choice all around.<br>
<br>
The good news is that I can still read my FT60, so I haven't lost anything.<br>
And maybe there's progress on write, but painful progress.<br>
I managed on one write attempt to completely erase the FT60, so<br>
I guess there's some indication that it's sending something.<br>
A read attempt failed with an error and no data returned, and operationally<br>
there are no memories in the radio.<br>
<br>
Fortunately, I was able to clone it from our other FT60, or at least 10 of the<br>
memories; the other two were recently programmed just in one.<br>
<br>
And after cloning, I can read it back into Chirp, so I'd say I'm no worse off.<br>
<br>
A second teeth-gritting write attempt did nothing, as the previous behavior.<br>
The radio just displays --Rx-- forever.<br>
I did manage to see the little pop-up just long enough to read it, it says<br>
Cloning<br>
[Cancel]<br>
for maybe half a second, then disappears.<br>
<br>
So, any more ideas?<br>
<br>
-dan<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
On Sep 21, 2012, at 7:09 PM, Guy Teague - <a href="mailto:accts@gtweb.org">accts@gtweb.org</a> <+chirp+cordless+1d49abe5b1.accts#<a href="mailto:gtweb.org@spamgourmet.com">gtweb.org@spamgourmet.com</a>> wrote:<br>
> might look over this thread '[chirp_users] Please post'.<br>
><br>
> i have chirp working on an imac running osx 10.7.4 (now 10.7.5). here is the driver i'm using:<br>
><br>
> unfortunately i can't link directly to the driver--that would be too easy by far. the main page is: <a href="http://www.prolific.com.tw/US/CustomerLogin.aspx" target="_blank">http://www.prolific.com.tw/US/CustomerLogin.aspx</a> and then you have to hit the support tab, then login using guest/guest. then you can get to the driver page and select the mac driver that matches your os version. i'm using 10.7.4 (lion).<br>
><br>
> if the installer works right, when you try to transfer from the radio to chirp you should see '/dev/cu.usbserial' as an option. i found a quirk where i couldn't upload to radio unless it was in vfo mode.<br>
><br>
> good luck,<br>
><br>
> /guy<br>
><br>
><br>
> On Fri, Sep 21, 2012 at 8:41 PM, <<a href="mailto:chirp.cordless@xoxy.net">chirp.cordless@xoxy.net</a>> wrote:<br>
> Hi,<br>
> I'm new to Chirp, and enthusiastic about the possibilities, but<br>
> if it can't write to my radio, my enthusiasm will wane quickly.<br>
> There has to be too many of these out there for it not to be<br>
> a problem with my setup, but I'm not sure where to start.<br>
><br>
> Setup:<br>
> New MacBook running OSX 10.8.2. Chirp is 0.2.3.<br>
> Cable is from eBay, using a PL2303 chip, driver obtained from your pointer, I think.<br>
> Fairly new Yaesu FT-60, 12 memories used.<br>
> Trying to load another 100 for the local standardized CERT list, massaged<br>
> from a spreadsheet into a .csv format that Chirp finally seems happy with, and<br>
> which looks sane in the Chirp display.<br>
><br>
> I am able to read the FT60 into Chirp just fine, and repeatedly, no errors.<br>
> What I see in Chirp is pretty much what I expected to see.<br>
> After massaging, I tried to write it back. I think I've got the dance right:<br>
> Put the FT60 in clone Rx mode and then hit the OK button in Chirp's<br>
> Upload popup. [ Just for grins I tried it in the "wrong" order, that doesn't<br>
> work either. ]<br>
><br>
> Nothing happens. The FT60 stays in Rx mode as though nobody has<br>
> tried comm with it. No progress bar as with a radio/radio clone, and no<br>
> error display. Just waiting in Rx, forever.<br>
><br>
> The Upload popup in Chirp disappears, there looks to be a flash of a small popup<br>
> too fast to read, and nada. The radio, after power off/on, still has the original 12<br>
> memories programmed, but nothing else. No error messages I can see.<br>
><br>
> I tried a different FT60, same result. Reseated the cable several times.<br>
> The cable is plausibly suspect (I don't have another), but I don't think it<br>
> can read and not write, it needs both data directions for either, doesn't it?<br>
><br>
> I can't find any debug information within Chirp or the Mac console logs,<br>
> but maybe I don't know where to look. The "raw data" in the developer tools<br>
> just looked like a very short data structure, nothing that looked meaningful<br>
> to me. Please advise how I can go about troubleshooting this, or what I might<br>
> be doing wrong.<br>
><br>
> Thanks and regards,<br>
><br>
> -dan<br>
<br>
<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>
</div></div></blockquote></div><br></div>