Project

General

Profile

Actions

Bug #1695

closed

UV-82X 220MHz Problem

Added by David Riley almost 10 years ago. Updated over 9 years ago.

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

100%

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

Description

CHIRP works fine on my UV-82X, but it will not accept a frequency entry in the 220 MHz range. It will allow a 220 Mhz frequency to be downloaded from the radio, but any attempt to edit or add a 220 MHz frequency creates this error, "Error setting memory: Frequency 224.000000 is out of supported range." No problem with entries in the 144 MHz range.

Actions #1

Updated by Jim Unroe almost 10 years ago

David,

Sometimes these VHF/220 radios come from the factory with the byte that CHIRP uses to determine if the second band is UHF or 220 set to UHF. This can usually be "fixed" by resetting the radio. Here is one way to do it.

  1. launch CHIRP
  2. download from the radio (this will create a tab with the current channels and settings)
  3. save this tab to a .img file (this tab will now have the .img filename in it)
  4. reset the radio (press and hold the [MENU] key while powering the radio ON)
  5. download from the radio a second time (this will create a second tab with the 220/UHF byte set to 220)

While the second tab is selected, see if you can now key in a frequency in the 220 MHz range. If you can, continue. If you can't, see below.

  1. copy and paste the channels from the first tab to the second tab.
  2. edit, as needed, the settings of the second tab
  3. save the second tab to a .img file
  4. upload the second tab to your radio

Do not ever load the first tab or the .img file from the first tab back into your radio. If you do, CHIRP will think it is a VHF/UHF radio again.

If after you get to step 5 and you still cannot key in a 220 MHz frequency, attach the .img that was saved from the first tab and I will switch it to VHF/220 and return it.

Jim KC9HI

Actions #2

Updated by Jim Unroe almost 10 years ago

  • Status changed from New to In Progress
  • Assignee set to Jim Unroe

David,
The 220 support was broken with the 20140601 release. I'll be working on it. In the mean time you can use to 20140428 daily build for 220 support.
Jim KC9HI

Actions #3

Updated by Jim Unroe almost 10 years ago

  • Target version set to 0.4.1
  • % Done changed from 0 to 90
  • Platform changed from Windows to All

A patch that fixes this issue has been submitted.
Jim KC9HI

Actions #4

Updated by David Riley over 9 years ago

I downloaded the 20140428 daily build and that works on 220

Actions #5

Updated by Jim Unroe over 9 years ago

  • Status changed from In Progress to Closed
  • % Done changed from 90 to 100

Patch is now included in current daily build

Actions

Also available in: Atom PDF