Bug #9145
openBF-888S - Radio refused to enter programming mode
0%
Description
Both of the BF-888S I own refuse to enter programming mode.
Both radios program just fine using BF-480 software and the same CP2102 based cable.
The same cable can be used to program my BF-5R using Chirp.
debug.log for what it's worth:
[2021-06-20 13:15:43,579] chirp.ui.inputdialog - ERROR: ----------------------------
[2021-06-20 13:15:59,693] chirp.ui.mainapp - DEBUG: User selected Baofeng BF-888 on port COM3
[2021-06-20 13:15:59,756] chirp.ui.clone - DEBUG: Clone thread started
[2021-06-20 13:15:59,757] chirp.drivers.h777 - DEBUG: download
[2021-06-20 13:15:59,884] chirp.ui.reporting - DEBUG: Reporting exception
[2021-06-20 13:15:59,884] chirp.ui.common - ERROR: -- Exception: --
[2021-06-20 13:15:59,887] chirp.ui.common - ERROR: Traceback (most recent call last):
File "chirp\ui\clone.pyo", line 255, in run
File "chirp\drivers\h777.pyo", line 340, in sync_in
File "chirp\drivers\h777.pyo", line 195, in do_download
File "chirp\drivers\h777.pyo", line 112, in _h777_enter_programming_mode
RadioError: Radio refused to enter programming mode
[2021-06-20 13:15:59,887] chirp.ui.common - ERROR: ----------------
[2021-06-20 13:15:59,888] chirp.ui.clone - ERROR: Clone failed: Radio refused to enter programming mode
[2021-06-20 13:15:59,895] chirp.ui.clone - DEBUG: Clone thread ended
[2021-06-20 13:15:59,900] chirp.ui.reporting - DEBUG: Reporting model usage: Baofeng_BF-888,download,True
[2021-06-20 13:15:59,901] chirp.ui.inputdialog - ERROR: --- Exception Dialog: Radio refused to enter programming mode ---
[2021-06-20 13:15:59,901] chirp.ui.reporting - DEBUG: Reporting exception
[2021-06-20 13:15:59,903] chirp.ui.inputdialog - ERROR: Traceback (most recent call last):
File "chirpw", line 68, in
AttributeError: 'NoneType' object has no attribute 'split'
No data to display