Bug #3871
closedCannot connect to Baofeng uv-5001 Gen III
0%
Description
Hi,
I've tried to connect to my Baofeng uv-5001 Gen 3 with the PC FTDI USB cble sold by Baofeng and I have not had much success. Chirp (on linux, build of 07-31-2016) displays an error message while reading the radio. In the terminal, it displays the following:
@ERROR: ----------------------------
WARNING: Short reading 68 bytes from the 69 requested.
ERROR: -- Exception: --
ERROR: Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/chirp/ui/clone.py", line 249, in run
self.__radio.sync_in()
File "/usr/lib/python2.7/dist-packages/chirp/drivers/btech.py", line 822, in sync_in
data = _download(self)
File "/usr/lib/python2.7/dist-packages/chirp/drivers/btech.py", line 612, in _download
d = _recv(radio, addr)
File "/usr/lib/python2.7/dist-packages/chirp/drivers/btech.py", line 423, in _recv
block = _rawrecv(radio, BLOCK_SIZE + 5)
File "/usr/lib/python2.7/dist-packages/chirp/drivers/btech.py", line 386, in _rawrecv
raise errors.RadioError("Error reading data from radio")
RadioError: Error reading data from radio
ERROR: ----------------
ERROR: Clone failed: Error reading data from radio
ERROR: --- Exception Dialog: Error reading data from radio ---
ERROR: None@
It looks like it identifies the radio properly but does not manage to clone it. Any suggestions?
Best regards,
Alex
Updated by Pavel Milanes over 8 years ago
- Status changed from New to Feedback
- Assignee set to Pavel Milanes
- Chirp Version changed from 0.4.0 to daily
- Model affected changed from (All models) to BTECH UV-5001
Hi Alex, thanks for the report.
This issue is old and I sould look it more closely to fix it for good, but familly and vacations get me busy this days.
I will look into it as soon as possible.
73 Pavel.
Updated by Pavel Milanes about 8 years ago
We have possibly found a solution, please take a peek here http://chirp.danplanet.com/issues/3993#note-12 and comment about your results.
73 Pavel CO7WT
Updated by Pavel Milanes almost 8 years ago
- Status changed from Feedback to Resolved
This bug was solved by Michel Wagner some time ago... see issue #3993
73 Pavel CO7WT.
Updated by Pavel Milanes over 7 years ago
- Status changed from Resolved to Closed