Project

General

Profile

Actions

Bug #8837

open

New Radio, Pofung UV-82 Receive issues

Added by charles harageones over 3 years ago. Updated over 3 years ago.

Status:
Feedback
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
02/23/2021
Due date:
% Done:

0%

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

Description

Same issue as Bug #8257

However, I'm using a new Pofung UV-82. Ive been told I can be heard transmitting without issue. However, to receive after transmitting I need to manually press the Menu button. Everything looks in order, but I cannot find a reason.

Current program cloned from Baofeng UV-5r, works perfectly fine on that device.
Including UV-5r base program, UV-82 program, and debug log.

Firmware version N822413


Files

Baofeng_UV-82_20210223.img (6.49 KB) Baofeng_UV-82_20210223.img current UV82 image charles harageones, 02/23/2021 08:29 AM
20210222.img (6.5 KB) 20210222.img UV-5r base image charles harageones, 02/23/2021 08:29 AM
Untitled 1.docx (336 KB) Untitled 1.docx debug log too large in notepad, converted to docx charles harageones, 02/23/2021 08:29 AM
UV-82N822411(factory)_edited_to_N822413.img (6.32 KB) UV-82N822411(factory)_edited_to_N822413.img from radio with N822411 firmware hex edited to N822413 Jim Unroe, 03/04/2021 01:41 PM
Actions #1

Updated by Rudolph Gutzerhagen over 3 years ago

I saw a number of internet posts suggesting that this can be a common problem due to a firmware bug. A reddit post suggested a workaround of setting Beep enabled (NOT Roger Beep). Assuming all your frequency programming is okay, this should be a simple test. Please let us know if this tip works.

Actions #2

Updated by charles harageones over 3 years ago

Rudolph Gutzerhagen wrote:

I saw a number of internet posts suggesting that this can be a common problem due to a firmware bug. A reddit post suggested a workaround of setting Beep enabled (NOT Roger Beep). Assuming all your frequency programming is okay, this should be a simple test. Please let us know if this tip works.

Toggled Beep both both on and off. No fix.

Firmware bug was my fear, but I've read of some people who have had the issue occurr after an update to CHIRP on previously fine devices. I figured i would seek all avenues to troubleshoot before attempting to get a replacement from the vendor.

Actions #3

Updated by Jim Unroe over 3 years ago

  • Status changed from New to Feedback

Rudolph Gutzerhagen wrote:

I saw a number of internet posts suggesting that this can be a common problem due to a firmware bug. A reddit post suggested a workaround of setting Beep enabled (NOT Roger Beep). Assuming all your frequency programming is okay, this should be a simple test. Please let us know if this tip works.

If this is the case, it is a return of a bug from a long time ago. But I agree, it is a simple test and there is nothing to lose (except a lack of key beeps) by trying it.

Jim KC9HI

Actions #4

Updated by Jim Unroe over 3 years ago

Did you create a backup image of the UV-82 before making any changes?

Jim KC9HI

Actions #5

Updated by charles harageones over 3 years ago

Jim Unroe wrote:

Did you create a backup image of the UV-82 before making any changes?

Jim KC9HI

New in box. Completely factory.

Actions #6

Updated by Jim Unroe over 3 years ago

How do you mean? The image you attached is not "factory". It is also from a fairly old radio (around 2016/2017 based on the firmware version).

Jim KC9HI

Actions #7

Updated by charles harageones over 3 years ago

Jim Unroe wrote:

How do you mean? The image you attached is not "factory". It is also from a fairly old radio (around 2016/2017 based on the firmware version).

Jim KC9HI

well, it was in a sealed box that looked like it was from the manufacturer. it was a third party seller, so i suppose it very well could have been modified.

i just got a new radio, same model, and it works. so i can just scrap it for parts and peripherals

Actions #8

Updated by Jim Unroe over 3 years ago

charles harageones wrote:

Jim Unroe wrote:

How do you mean? The image you attached is not "factory". It is also from a fairly old radio (around 2016/2017 based on the firmware version).

Jim KC9HI

well, it was in a sealed box that looked like it was from the manufacturer. it was a third party seller, so i suppose it very well could have been modified.

i just got a new radio, same model, and it works. so i can just scrap it for parts and peripherals

I'm just trying to understanding what you have going on. I would imagine that this radio is likely new "old stock". Actually that would be my preference.

I've heard of radios that need to have the [MONI] or [M] key pressed, but not the [MENU] button. The first thing you should have done would have been to saved your first download from the radio, unedited, to a CHIRP Radio Images (*.img) file to be kept as a backup. However, it doesn't sound like this was done. This would have allowed comparing the radio's current memory state to what its state was from the factory. Unfortunately I don't appear have an "image" from a radio with N822413 firmware. The closest I have been able to find is N822411.

I suppose I could "hack" it into a "N822413" so you can upload it and try it out. You've go nothing to lose. Upload it and switch to VFO mode and key in a local NOAA frequency to see if you can hear it. If you can, then import your frequencies from the "base image".

Jim KC9HI

Actions #9

Updated by Bernhard Hailer over 3 years ago

How do we want to proceed on this one? Thank you.

Actions

Also available in: Atom PDF