Bug #4565
openBF-888S and BF-888S Plus Fail To Intialize 50% Of Time
0%
Description
Thank you for this wonderful program (CHIRP).
There appears to be a slight error with CHIRP initializing reading from the BF-888S and BF-888S Plus radios. It does work, however roughly 1 out of 2 times, CHIRP errors out with "Radio refused to enter programming mode.". It is an intermittent, hit or miss, type error during initialization of reading from the radio. I'm assuming it is doing some sort of handshake during this stage (?). I was able to reproduce the error enough times on both Mac and Windows to conclude that it must be CHIRP. I was also able to reproduce the error using FTDI, Prolific, and CH340 cables. The Prolific and CH340 cables were known to be good and correctly configured/installed as they work fine with other radios. The FTDI cable, not only is rock solid FTDI, but works fine also with other radios.
As I have a BF-888S Plus, I can contribute a port dump of a good handshake, if that would help?
Thanks.
Related issues
Updated by Bernhard Hailer about 4 years ago
- Status changed from New to Feedback
- Chirp Version changed from 0.4.0 to daily
- Model affected changed from (All models) to Baofeng BF-888S, S+
Have you been able to resolve this on your own since you submitted this?
Have you tried with a recent version since you submitted this?
It might be an issue with the connector in the radio, which can be a bit iffy - try t o press in hard, hold plug at an angle during programming, etc.
If you haven't, and if you're still having this issue, please refer to the Wiki "How To Report Issues" and provide a debug log. Your offer of a port dump might help as well. Thanks!
Updated by Bernhard Hailer about 4 years ago
For the BF-88S+, please refer to #4835.