Bug #7609


BF-888 - mostly unstable - returned unknown identification string

Added by Vance Anderson about 4 years ago. Updated almost 4 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:
Chirp Version:
Model affected:
Baofeng BF-888S
Debug Log:
I read the instructions above:


Having problems programming 2 BF-888S radios. Tried 2 computers and 2 radios. Chirp works fine with my UV-82 and FT-60.

Error is "Radio returned unknown identification string" (ALL failed attempts)

Have tried uploading around 50+ attempts. I had only 3 successful uploads from 2 different radios but could not duplicate success. Tried restarting computer, restarting Chirp, etc. After the successful uploads a subsequent attempt to upload or download was not successful. Could not establish why 3 out of 50+ attempts were successful. Seemed random. Have never been able to upload.

Attached are debug logs for 2 successful attempts (2 different radios) and one FAILED debug log(similar for 50+ attempts with 2 different radios)


Actions #1

Updated by Vance Anderson about 4 years ago

Added image file from successful download

Actions #2

Updated by Vance Anderson about 4 years ago

After more testing I was able to resolve the issue by using a different programming cable. By utilizing a different BaoFeng cable that uses the "CH340" driver the communication was successful. The problem must be in the interface when a programming cable uses the (rolled back) FTDI driver.

Again my FTDI driver cable works for some BF radios but the BF-888S.

Actions #3

Updated by Tjerk Kamstra about 4 years ago

I have the exact same issue. I have that prolific cable too and now it suddenly won't program my Baofeng 888 deluxe radios anymore. The debugfile is attached. It will program my UV5RE's perfectly fine. Tried every USB port, putting it on channel 16 and putting the volume way up. Nothing found online seems to be working, and I am sure it worked before because I programmed it myself using CHIRP.

The driver is installed correctly

Actions #4

Updated by Tjerk Kamstra about 4 years ago

Ok, I managed to program them by reversing back to version CHIRP daily-20190102.
I suppose this is not how it should work, but it revived my radio's.
Other info is
GTK 2.24.10
PyGTK 2.24.0
Python 2.7.10

Actions #5

Updated by Bernhard Hailer almost 4 years ago

  • Status changed from New to Feedback
  • Assignee set to Jim Unroe
  • Target version set to chirp-legacy
  • Model affected changed from BF-888S to Baofeng BF-888S

Leaving this ticket open: the comment above suggests that something about the recognition of these radios has been changed since Jan 20, 2019.
Assigning to Jim - I hope you don't mind? :-)


Also available in: Atom PDF