Project

General

Profile

Actions

Bug #8457

closed

New radio Baofeng UV-82 change in firmware reporting even though the firmware hasn't changed.

Added by Kenneth Burton about 4 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
11/20/2020
Due date:
% Done:

0%

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

Description

I have a couple of new UV82 radios and Chirp complained a bit about uploading my image to the new radios.
The old radios show N822413 in both firmware msg 1 and msg 2.
The new radios show N822413 (the same firmware), but only in msg 1.

Is there anyway to tell it to ignore the duplication in msg 2 or to ignore the absence of the duplication in the new radio?

I have attached screen shots.

This is not a big problem. The memory locations upload fine. Manually updating the other settings is not a big deal.

Thank you,
Ken


Files

Actions #1

Updated by Jim Unroe about 4 years ago

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

Hi Kenneth,

This is by design. If the firmware version (Firmware Message 1: + Firmware Message 2:) of the source "image" being uploaded does not exactly match the firmware version of the destination radio, the portions of memory that could have undesirable result if copied into a similar radio with a different firmware version are skipped (In some cases the upload is completely aborted and nothing is uploaded). In your case, this affects mainly the settings that are stored in what is called "aux memory" (power-on messages, band limits, squelch thresholds, etc). What this means is that you will have to keep separate CHIRP Radio Images (*.img) files for each unique firmware version and make separate adjustments to the affected settings. The good news is that once the settings stored in "aux memory" are set up, they rarely need updating.

Historical note: There used to be a time where the upload was always fully aborted whenever a firmware version mismatch was detected.

Jim KC9HI

Actions #2

Updated by Bernhard Hailer about 4 years ago

  • Status changed from Feedback to Closed
  • Model affected changed from (All models) to Baofeng UV-82
Actions

Also available in: Atom PDF