Project

General

Profile

Actions

Bug #9896

closed

Btech GMRS-V1 error

Added by Don Hoyt over 2 years ago. Updated over 2 years ago.

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

0%

Estimated time:
Chirp Version:
daily
Model affected:
GMRS V1 and others
Platform:
All
Debug Log:
I read the instructions above:

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.


Files

debug.log (31.5 KB) debug.log Whitney Van Brink, 06/01/2022 05:32 AM
Actions #1

Updated by Josh Wilson over 2 years 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.

Actions #2

Updated by Don Hoyt over 2 years ago

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

Actions #3

Updated by Jim Unroe over 2 years 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

Actions #4

Updated by Whitney Van Brink over 2 years ago

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

Actions #5

Updated by Jim Unroe over 2 years ago

  • Status changed from Feedback to In Progress
  • Assignee set to Jim Unroe
  • Target version set to chirp-legacy
  • 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

Actions #6

Updated by Jim Unroe over 2 years 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":https://chirp.danplanet.com/projects/chirp/repository/revisions/8fbeae0f94d6) 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

Actions #7

Updated by Dan Smith over 2 years 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.

Actions #8

Updated by Jim Unroe over 2 years ago

  • Status changed from Feedback to Resolved

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

Jim KC9HI

Actions #9

Updated by Jim Unroe over 2 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF