Project

General

Profile

Actions

Bug #10841

open

BTECH UV50-X2-G2 start screen customization

Added by Geoff Beasley about 1 year ago. Updated about 1 year ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
09/15/2023
Due date:
% Done:

0%

Estimated time:
Chirp Version:
next
Model affected:
BTECH UV50-X2-G2
Platform:
Windows
Debug Log:
I read the instructions above:

Description

I wanted to update my BTECH UV50-X2 Gen 2 start screen's custom lines with my three FCC callsigns. It let me update them before, and I've updated my other BaoFeng UV5R and BF-F8HP radios today with my callsigns, but this particular radio is not accepting any changes to the Power-on message lines. I'm using the latest release of Chirp Next (20230911) in Windows 11.

I can read the old .img file off the radio just fine, and I can load a saved .img file off the computer just fine. When I try to edit any of the start screen lines by going to:
-Settings
--Advanced Settings
---Power-on message line X
it will not accept any new characters in any of the fields. It returns a popup error message stating "Can't be greater then 480.9975" even if I enter "1".
If I accept the error and close the popup window and keep my newly intended characters in the fields, neither saving the file locally or writing to the radio are successful; my previous configuration with the prior power-on message lines remains.

I suspect the problem is with some recent change to the BTECH UV50-X2-G2 setup within Chirp Next.


Files

debug.log (56.4 KB) debug.log Geoff Beasley, 09/15/2023 10:53 AM
debug.log (63.5 KB) debug.log Geoff Beasley, 09/15/2023 02:19 PM
Actions #1

Updated by Jim Unroe about 1 year ago

This error is not in the supplied debug.log file. Please attache your CHIRP image file so the error can be duplicated here.

Actions #2

Updated by Geoff Beasley about 1 year ago

I don't know why the debug.log didn't work. I just deleted it, restarted Chirp Next, attempted to enter my callsign into a field as described above, and caused the error popup window to appear again. I closed the popup, closed the program, and attached the new debug.log file that Chirp Next generated.

Actions #3

Updated by Jim Unroe about 1 year ago

Thanks for the additional debug.log. The problem is not with the Power-On Message settings. The problem is that VFO D of this particular radio has an out-of-range value in it and CHIRP is letting you know about this unrelated invalid setting.

Apparently the upper band limit of this radio is set to 481.000 MHz and the value in VFO D is higher than that limit. You should get this notification no matter which setting that you tried to edit.

The 'fix' is to set VFO D to a valid frequency. Either switch to VFO D in the radio or do it within CHIRP (Settings -> Work Mode Settings -> VFO D Frequency) and set it to a frequency that is within the radio's UHF or VHF band limits. If you change it at the radio, download the change into CHIRP and CHIRP won't have anything to warn you about any more.

Actions

Also available in: Atom PDF