CHIRP

Tried it out Jim - No joy with the BF-888. Initially downloads and uploads to radio upon opening but won't save image file. Need to force quit chirp as it stops responding when I try and quit the program. When I try to open it up again it hangs up and won't download from radio. Keyboard still not functioning after use and have to do a hard shutdown to reset everything. Not a big priority as I can program the radio one time before encountering all the problems, but it is annoying to have to hard shudown and restart to get my computer running again. UV-82 programming still works as advertised with no bugs that I have noticed.

Sounds like we need a debug log. Please see the FAQ about reporting bugs.

In addition: I'm using 0.4.0 with the h777.py above. Similarly with the reporter I can program another Baofeng without any problems (UV-B5). I can't really see anything going wrong during the upload.

The freeze is immediate after upload finishes. To be precise I don't think it's a freeze, it's the inputs that stop working. Everything is actually still running.

A theory: I think the USB-driver probably is the culprit (since all the inputs seem to malfunction simultaneously) and not much that can be done about that. However it is definitely provoked by something done in the upload process. Something that isn't done in the case of the UV-82 or UV-B5. Solution might be in the diff to those.

Are you both using a cable with FTDI chipset, and on Mac OSX Mavericks?

If so, this seems to be a common problem, and solution could be either to remove FTDI driver and use builtin apple ftdi driver, or switch to ftdi driver and disable apple ftdi driver. It's not clear which is the working path for all situations, but this has been discussed on mailing list:
http://intrepid.danplanet.com/pipermail/chirp_users/2014-April/005817.html

I'm using a Prolific chipset cable with their v.1.5.1 driver (latest). I will try and get/build a FTDI chipset cable to test with since those always have worked well for me for other things.

Daniel Hjort wrote:

I'm using a Prolific chipset cable with their v.1.5.1 driver (latest). I will try and get/build a FTDI chipset cable to test with since those always have worked well for me for other things.

I'm not sure if it works on Mavericks, but you can try this driver:
http://chirp.danplanet.com/projects/chirp/wiki/MacOS_Tips#Generic-PL-2303-cables-counterfeit-andor-“Generic”

Let me know if it works for you. I'm guessing your cable is not genuine prolific chip (which is very rare), so chances are the OEM prolific driver could be causing this (whether intentional or not).