Project

General

Profile

Actions

Bug #8169

open

BF-888s with fake PL2303 cable gets error "Radio returned unknown identification string"

Added by Tse-Lei Wu over 2 years ago. Updated over 1 year ago.

Status:
Feedback
Priority:
Normal
Assignee:
-
Target version:
Start date:
08/06/2020
Due date:
% Done:

0%

Estimated time:
Chirp Version:
daily
Model affected:
Baofeng BF-888S
Platform:
Windows

Description

My cable works on UV-5R but not on BF-888s.
The cable works fine on Baofeng software.

After checking the source code, I make a patch to make Chirp works on my fake PL2303 cable


diff -r 37a6a6d6f425 chirp/drivers/h777.py
--- a/chirp/drivers/h777.py    Fri Jul 17 20:17:29 2020 -0700
+++ b/chirp/drivers/h777.py    Fri Aug 07 08:12:02 2020 +0800
@@ -111,12 +111,12 @@

     original_timeout = serial.timeout
     try:
-        serial.write("\x02")
         # At least one version of the Baofeng BF-888S has a consistent
         # ~0.33s delay between sending the first five bytes of the
         # version data and the last three bytes. We need to raise the
         # timeout so that the read doesn't finish early.
         serial.timeout = 0.5
+        serial.write("\x02")
         ident = serial.read(8)
     except:
         raise errors.RadioError("Error communicating with radio")
@@ -182,11 +182,11 @@

     original_timeout = serial.timeout
     try:
-        serial.write(cmd + data)
         # Time required to write data blocks varies between individual
         # radios of the Baofeng BF-888S model. The longest seen is
         # ~0.31s.
         serial.timeout = 0.5
+        serial.write(cmd + data)
         if serial.read(1) != CMD_ACK:
             raise Exception("No ACK")
     except:


Files

cable.jpg (2.18 MB) cable.jpg Tse-Lei Wu, 08/06/2020 05:31 PM
Actions #1

Updated by Bernhard Hailer over 1 year ago

  • Status changed from New to Feedback
  • Model affected changed from BF-888S to Baofeng BF-888S

Jim, can you have a look, please?

Actions

Also available in: Atom PDF