CHIRP

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

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