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