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

[chirp.cordless at xoxy.net]

Thanks,

I can't see what thread you want me to look at, something in the path seems
to have obfuscated it, see below.

I tried putting the radio in VFO mode, no help.

So I unloaded the Prolific driver I was using that was from some open source
project, and loaded the one downloaded from the Prolific website you pointed me
at, which at least claims to know about OS X 10.7, and I expect it likely is a
better choice all around.

The good news is that I can still read my FT60, so I haven't lost anything.
And maybe there's progress on write, but painful progress.
I managed on one write attempt to completely erase the FT60, so
I guess there's some indication that it's sending something.
A read attempt failed with an error and no data returned, and operationally
there are no memories in the radio.

Fortunately, I was able to clone it from our other FT60, or at least 10 of the
memories; the other two were recently programmed just in one.

And after cloning, I can read it back into Chirp, so I'd say I'm no worse off.

A second teeth-gritting write attempt did nothing, as the previous behavior.
The radio just displays --Rx-- forever.
I did manage to see the little pop-up just long enough to read it, it says
	Cloning
	[Cancel]
for maybe half a second, then disappears.

So, any more ideas?

-dan


On Sep 21, 2012, at 7:09 PM, Guy Teague - accts at gtweb.org <+chirp+cordless+1d49abe5b1.accts#gtweb.org at spamgourmet.com> wrote:
> might look over this thread '[chirp_users] Please post'.
> 
> i have chirp working on an imac running osx 10.7.4 (now 10.7.5). here is the driver i'm using:
> 
> unfortunately i can't link directly to the driver--that would be too easy by far. the main page is: http://www.prolific.com.tw/US/CustomerLogin.aspx 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).
> 
> 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.
> 
> good luck,
> 
> /guy
> 
> 
> On Fri, Sep 21, 2012 at 8:41 PM, <chirp.cordless at xoxy.net> wrote:
> Hi,
> I'm new to Chirp, and enthusiastic about the possibilities, but
> if it can't write to my radio, my enthusiasm will wane quickly.
> There has to be too many of these out there for it not to be
> a problem with my setup, but I'm not sure where to start.
> 
> Setup:
> New MacBook running OSX 10.8.2. Chirp is 0.2.3.
> Cable is from eBay, using a PL2303 chip, driver obtained from your pointer, I think.
> Fairly new Yaesu FT-60, 12 memories used.
> Trying to load another 100 for the local standardized CERT list, massaged
> from a spreadsheet into a .csv format that Chirp finally seems happy with, and
> which looks sane in the Chirp display.
> 
> I am able to read the FT60 into Chirp just fine, and repeatedly, no errors.
> What I see in Chirp is pretty much what I expected to see.
> After massaging, I tried to write it back. I think I've got the dance right:
> Put the FT60 in clone Rx mode and then hit the OK button in Chirp's
> Upload popup. [ Just for grins I tried it in the "wrong" order, that doesn't
> work either. ]
> 
> Nothing happens. The FT60 stays in Rx mode as though nobody has
> tried comm with it. No progress bar as with a radio/radio clone, and no
> error display. Just waiting in Rx, forever.
> 
> The Upload popup in Chirp disappears, there looks to be a flash of a small popup
> too fast to read, and nada. The radio, after power off/on, still has the original 12
> memories programmed, but nothing else. No error messages I can see.
> 
> I tried a different FT60, same result. Reseated the cable several times.
> The cable is plausibly suspect (I don't have another), but I don't think it
> can read and not write, it needs both data directions for either, doesn't it?
> 
> I can't find any debug information within Chirp or the Mac console logs,
> but maybe I don't know where to look. The "raw data" in the developer tools
> just looked like a very short data structure, nothing that looked meaningful
> to me. Please advise how I can go about troubleshooting this, or what I might
> be doing wrong.
> 
> Thanks and regards,
> 
> -dan