[chirp_users] Macbook + Icom ID-880H + BlueMax49ers FTDI cable = frustration

[Creede Lambard]

I’ve seen this sort of thing posted before on the list but I haven’t
noticed a fix or workaround.

I’m running OS X 10.10 (Yosemite) on a Macbook Pro. Last weekend I bought a
brand new Icom ID-880H after checking to make sure that it’s supported
according to the Chirp wiki. This afternoon I got a FTDI-based USB cable
from BlueMax49 and figured I’d clone my radio, then upload the results back.

I was able to successfully clone the memory, so it looks like the drivers
and cable are working, and I noticed that Chirp includes D-STAR information
- something I’d never had call to notice before as this is my first D-STAR
capable radio! Well done! Unfortunately, when I changed one tone setting
and gave the channels labels, then went to upload the information back to
the radio, the Chirp progress bar went all the way to the right, but then I
got an error message:

“Failed to communicate with radio: Did not get clone result from radio”

That’s not the worst part, though. After Chirp errors out the radio is
stuck at “CL IN”. When I shut the radio off and turn it back on again the
display says CLEAR, then the ICOM banner and finally the radio is back to a
factory restored state. All of the memories I programmed in over the
weekend are gone. Happily, they are stored in a .img file on the Mac;
unhappily, I can’t seem to get the file to load into the radio.

For what it’s worth, I get the same error when I try to upload an image
with only one memory slot filled in.

Is this a known issue? Is there a workaround? What can I do to get Chirp
working? I’ve been using the software for years and this is the first
problem I’ve had with it. I can send a copy of the .img file if you need me
to.

Thanks.

-- 
Creede Lambard
Sent with Airmail
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20161018/8736e2cf/attachment.html