Bug #8169
BF-888s with fake PL2303 cable gets error "Radio returned unknown identification string"
Status: | Feedback | Start date: | 08/06/2020 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | - | % Done: | 0% |
|
Category: | - | |||
Target version: | chirp-daily | |||
Chirp Version: | daily | Platform: | Windows | |
Model affected: | Baofeng BF-888S |
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
1 diff -r 37a6a6d6f425 chirp/drivers/h777.py
2 --- a/chirp/drivers/h777.py Fri Jul 17 20:17:29 2020 -0700
3 +++ b/chirp/drivers/h777.py Fri Aug 07 08:12:02 2020 +0800
4 @@ -111,12 +111,12 @@
5
6 original_timeout = serial.timeout
7 try:
8 - serial.write("\x02")
9 # At least one version of the Baofeng BF-888S has a consistent
10 # ~0.33s delay between sending the first five bytes of the
11 # version data and the last three bytes. We need to raise the
12 # timeout so that the read doesn't finish early.
13 serial.timeout = 0.5
14 + serial.write("\x02")
15 ident = serial.read(8)
16 except:
17 raise errors.RadioError("Error communicating with radio")
18 @@ -182,11 +182,11 @@
19
20 original_timeout = serial.timeout
21 try:
22 - serial.write(cmd + data)
23 # Time required to write data blocks varies between individual
24 # radios of the Baofeng BF-888S model. The longest seen is
25 # ~0.31s.
26 serial.timeout = 0.5
27 + serial.write(cmd + data)
28 if serial.read(1) != CMD_ACK:
29 raise Exception("No ACK")
30 except:
31
History
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?