Project

General

Profile

Actions

Bug #10777

open

Chirp does not allow frequency entry from 300-350 MHz on wideband UV-K5 even with limits disabled

Added by Chuck Murcko 9 months ago. Updated 4 months ago.

Status:
New
Priority:
Normal
Category:
-
Target version:
-
Start date:
08/06/2023
Due date:
% Done:

0%

Estimated time:
Chirp Version:
next
Model affected:
UV-K5 series
Platform:
Linux
Debug Log:
I read the instructions above:

Description

I am using wideband firmware, and with "Limits disabled for modified firmware" checked in Settings, I get an Invalid Entry error when entering frequencies in 300-350 MHz range with this text:

Invalid edit: Frequency 310.000000 is out of supported range; Transmit frequency 310.0000MHz is not supported by this radio; The frequency 310.0000MHz is not supported by this radio

OEM CPS software works to enter these memories. Chirp reads and writes the entries correctly to radio/file but will issue the above error if they are edited.


Files

Actions #2

Updated by Dan Smith 9 months ago

  • Assignee set to Jacek Lipkowski SQ5BPF
Actions #3

Updated by Chuck Murcko 9 months ago

NOTES:
This config was read from the radio.
Memory 14 = 23 cm repeater 927.1125 MHz
Memory 100-106 = air band inc. uneditable 300 MHz channels

Actions #4

Updated by Chuck Murcko 9 months ago

The fix for this is to change the lower band limit in uvk5.py for band 4 in BANDS_NOLIMITS to 300.0 as noted in the source excerpt:

bands supported by the UV-K5

BANDS = {
0: [50.0, 76.0],
1: [108.0, 135.9999],
2: [136.0, 199.9990],
3: [200.0, 299.9999],
4: [350.0, 399.9999],
5: [400.0, 469.9999],
6: [470.0, 600.0]
}

for radios with modified firmware:

BANDS_NOLIMITS = {
0: [18.0, 76.0],
1: [108.0, 135.9999],
2: [136.0, 199.9990],
3: [200.0, 299.9999],
4: [350.0, 399.9999], <-- lower limit changes to 300.0
5: [400.0, 469.9999],
6: [470.0, 1300.0]
}

Actions #5

Updated by Jacek Lipkowski SQ5BPF 9 months ago

I will look into this, thanks for the report. Which firmware are you using?

VY 73

Jacek / SQ5BPF

Actions #6

Updated by Chuck Murcko 9 months ago

I am using modified version of 2.01.26, .bin file attached/uploaded.

73, Chuck AI7SY

Actions #7

Updated by Chuck Murcko 9 months ago

...and thanks, Jacek.

Actions #8

Updated by Sam R 8 months ago

Also having this issue, except expanding Band 1 up to 80mhz. V2.01.26 modified FW, file attached.

Actions #9

Updated by Chuck Murcko 6 months ago

The issue has changed with Chirp rev 20231106. Memories can be edited with the patch above, but are now written to the radio as 50.000 MHz. So something upstream is also ignoring BANDS_NOLIMITS.

Actions #10

Updated by Chuck Murcko 6 months ago

With the BANDS_NOLIMITS patch, frequencies between 300-349.999 MHz can be manually inserted from the radio keypad after Chirp corrupts them during upload.

Actions #11

Updated by Chuck Murcko 4 months ago

Driver appears to be working fine. The last couple of issues were from firmware - please disregard posts 9/10.

Actions

Also available in: Atom PDF