Bug #6857
closedBaofeng uv-5r Radio refused to send second block 0x1f00
0%
Description
The Baofeng UV-5R radio has a communication issue.
I have 2 radios, purchased a few weeks apart. Same problem. Tried 2 versions of Chirp, with similar results.
I've attached 2 files. One is a log file from chirp,
and the other is the USB transaction data from usbmon.
Hopefully the USB transactions will help solve the issue.
Files
Related issues
Updated by Frank Bignell almost 5 years ago
- File debug_default.log debug_default.log added
- File debug_using_uv5r(3987)-py.log debug_using_uv5r(3987)-py.log added
- File debug_Win10Home.log debug_Win10Home.log added
Same here. UV-5R.
I cannot read/write to the radio using Chirp-Daily (CHIRP daily-20190601) in Ubuntu 16.04 on port /dev/ttyUSB0.
The error message returned is, "Radio refused to send second block 0x1f00"
Neither uv5r.py or loading uv5r(3987).py works.
I cannot read/write to the radio using CHIRP daily-20190626 in Windows 10 Home on Comm 6.
I can read/write to the radio using "UV-5R_VIP (BF5R_VIP_v120725_BFB291_ENG(VB6)") in Windows 10 on Comm 6.
Attached are Chirp log files files for the above described scenarios.
Updated by David Baines almost 5 years ago
This is still an issue with CHIRP daily-20190718
Updated by Frank Bignell over 4 years ago
Still happening with CHIRP daily-20190829.
Updated by Frank Bignell over 4 years ago
Still happening with CHIRP daily-20191022
Updated by Bernhard Hailer about 4 years ago
- Status changed from New to Closed
- Priority changed from High to Normal
- Target version set to chirp-legacy
- Model affected changed from UV-5R to Baofeng UV-5R
Duplicates #6681. Please leave any feedback there. Thanks!