Bug #9896

Btech GMRS-V1 error

Added by Don Hoyt about 1 month ago. Updated about 1 month ago.

Status:Closed Start date:05/31/2022
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:-
Target version:chirp-daily
Chirp Version:daily Platform:All
Model affected:GMRS V1 and others

Description

Downloaded the latest Chirp software and attempted to "Download from Radio" on my new Btech GMRS-V1 radio. Receive error - "Unexpected error communicating with the radio". I attempted this process numerous times on different serial ports.

As a test, I tried switching to GMRS-V2 and the cloning process starts and then received an error - "Error reading data from radio: not the amount of data we want".

I tested the cable and software with my Baofeng BF-F8HP radio and the software worked fine. Using Windows 10.

debug.log (31.5 kB) Whitney Van Brink, 06/01/2022 05:32 am

History

Updated by Josh Wilson about 1 month ago

I have the same error "Unexpected error communicating with the radio". Latest Daily (20220531) Flatpak on Linux.
Different radio Baofeng UV-9G.

Error occurs on upload or download.

Switched to UV-9R and got "Error reading data from radio: not the amount of data we want".

Reverted to 20220515 and everything is working again.

Updated by Don Hoyt about 1 month ago

Thanks to Josh Wilson, I took his recommendation and reverted to 20220515 and the GMRS-V1 is working!

Updated by Jim Unroe about 1 month ago

  • Status changed from New to Feedback
  • Platform changed from Windows to Linux

Nothing should have changed regarding the GMRS-V1. Upgrade to the latest again, cause the error and then attach the debug.log file.

Jim KC9HI

Updated by Whitney Van Brink about 1 month ago

I encountered this same error with my GMRS V1. I have attached a copy of the debug.log file.

Updated by Jim Unroe about 1 month ago

  • Status changed from Feedback to In Progress
  • Assignee set to Jim Unroe
  • Target version set to chirp-daily
  • Platform changed from Linux to All

I have been able to replicate the problem. It appears to exist across all supported operating systems. It is also broken for the GMRS-V2 so I also expect it is broken for all radio models that are supported by the baofeng_common.py driver module.

Jim KC9HI

Updated by Jim Unroe about 1 month ago

  • Status changed from In Progress to Feedback
  • Assignee deleted (Jim Unroe)
  • Model affected changed from GMRS V1 to GMRS V1 and others

This merge from github (Revision 3688) was the culprit. My understanding is that this change is expected to be reverted later today and a new build without the change will be available soon (possibly as soon as tomorrow).

Jim KC9HI

Updated by Dan Smith about 1 month ago

That's the merge commit, but the merged patch r3684 is the actual culprit. And yeah, I'm reverting now and will push for a build tomorrow.

Updated by Jim Unroe about 1 month ago

  • Status changed from Feedback to Resolved

Today's build (CHIRP daily-20220602) has corrected the issue with the affected radios.

Jim KC9HI

Updated by Jim Unroe about 1 month ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF