Project

General

Profile

Actions

Bug #6979

closed

Baofeng UV-82L images manufacturer/model broken in recent change to Radioddity UV-82X3

Added by Brian Daniels over 4 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
08/12/2019
Due date:
% Done:

0%

Estimated time:
Chirp Version:
daily
Model affected:
Baofeng UV-82L
Platform:
Windows
Debug Log:
I read the instructions above:

Description

I recently upgraded from a very old version (20170714) to Chirp 20190718.

In the process, all of my image files for a Baofeng UV-82L are now erroneously identified as a Radioddity UV-82X3. And I get warnings when trying to upload the images to my handset now.

Perhaps the problem was introduced in Revision 3245:9816c780ebeb (Correct Baofeng->Radioddity brand for UV-82X3):
https://chirp.danplanet.com/projects/chirp/repository/revisions/9816c780ebeb

This revision was part of Issue #6921
https://chirp.danplanet.com/issues/6921


Files

Baofeng_UV-82L__STOCK.img (6.32 KB) Baofeng_UV-82L__STOCK.img Stock image file downloaded from Baofeng UV-82L Brian Daniels, 08/14/2019 04:32 PM
CHIRP.png (18.1 KB) CHIRP.png Screenshot of CHIRP with bad model info Brian Daniels, 08/14/2019 04:32 PM
chirp_tag_thing_missing.png (24.6 KB) chirp_tag_thing_missing.png Tony Fuller, 08/14/2019 06:33 PM
uv5r_chirp-daily-20190718_Radioddity_82X3_removed.py (62.3 KB) uv5r_chirp-daily-20190718_Radioddity_82X3_removed.py Tony Fuller, 08/14/2019 06:33 PM
Actions #1

Updated by Brian Daniels over 4 years ago

NOTE: The model file was for Baofeng UV-82.
The "L" is extraneous info about the battery. Sorry.

Actions #2

Updated by Tony Fuller over 4 years ago

I'm not a chirp dev, but if you attach an affected IMG file I can play around with it and see if I can spot the problem and see what different between recent and 2017 builds.

Actions #3

Updated by Brian Daniels over 4 years ago

Hello. Thanks for your reply.
I am attaching the "stock" image that I downloaded from the Baofeng UV-82L when it was brand new.

I am currently running CHIRP daily-20190812, which shows the model as: Radioddity UV-82X3.
Screenshot is attached showing this.

Again, I would look at issue #6921, which has comments specifically about this manufacturer/model combination. It sounds suspiciously related.

Actions #4

Updated by Tony Fuller over 4 years ago

There's good news!

It seems that your .img is missing some sort of "CHIRP tag" at the end of it (see chirp_tag_thing_missing.png) -- most likely because that functionality was added later into CHIRP.

The problem is that CHIRP is confused as to what model is your radio because that tag is missing.

I don't know how they plan to solve that problem (or if they will see this message) but there is something you can do.

Backup (Copy or zip or something) All of your image files :)

Download the attached file "uv5r_chirp-daily-20190718_Radioddity_82X3_removed.py"

From CHIRP, click File -> Load Module, then in the file selection menu go to Downloads and double click this file. Chirp will "turn red in the background"

This is a pretty recent copy of the uv5r driver with that Radioddity UV-82X3 model removed.

Now do File -> Load, and load your image file

Your image file should be recognized as a Baofeng UV-82.

Save the newly recognized img (either overwrite or different filename)

Repeat last 3 steps for each img file.

Hopefully you don't have a lot of image files. :)

Actions #5

Updated by Brian Daniels over 4 years ago

GA-2S User wrote:

It seems that your .img is missing some sort of "CHIRP tag" at the end of it (see chirp_tag_thing_missing.png) -- most likely because that functionality was added later into CHIRP.

Thank you for that finding and hint!
What I ended up doing was reimporting a new image file from my radio, and then it had the proper chirp tag with model info. Then, I recreated all my existing images files off of that imported image and saved new copies of them.

Actions #6

Updated by Jim Unroe over 4 years ago

  • Status changed from New to Feedback

This should have been fixed per issue #7217.

Jim KC9HI

Actions #7

Updated by Jim Unroe over 4 years ago

  • Status changed from Feedback to Closed
Actions

Also available in: Atom PDF