Bug #12033
openError trying to change any item in Settings tab
0%
Description
(Describe what you were doing)
When I go to the Settings tab in CHIRP and try to change any parameter I get the error "Caller ID must be at least 3 and no more than 6 digits." I can click the OK button, the message goes away, and the parameter value appears to be the value I changed it to.
If I save the configuration to the radio and read it back, the Settings parameters are back to the default value.
(Describe what you expected to happen)
I expect that the parameter value I try changing, would change to the new value WITHOUT any error message. Then when I save the configuration back to the radio, and read the configuration back in, that the parameter value would remain the value that I changed it to.
The specific parameter I was trying to change is under Freq Limits > "450M Tx Upper Limit (Mhz + 0.9975)". However the error occurs attempting to change any parameter.
(Describe what actually happened instead)
I get the same error message (see above) as soon as I try changing any parameter in the Settings tab.
Even though the parameter value appears to change, the new value is NOT written to the radio, OR saved to a configuration file.
(Has this ever worked before? New radio? Does it work with OEM software?)
- This is my first time with the Wouxun KG-UV9PX radio.
- This is a new radio.
- I purchased a RT-System cable (model: USB-K4Y) for the KG-UV9PX.
- This is also the first time tried using the CHIRP-Next software.
- I'm using a Windows 11 Home computer with the latest updates.
- I also tried my Apple MacBook and get the same error.
- When installing CHIRP I selected the proper cable and radio model.
- I'm using the CHIRP software to attempt to change the radio Settings because I can't find any OEM software from Wouxun to use, AND the RT-System software doesn't expose the same radio settings that CHIRP does.
Files
Updated by Dan Smith 3 days ago
We need a debug log after reproducing the issue per the IssueInstructions. Looks like maybe you filed this from within CHIRP and it failed to upload the log? If so, please update this (choose update existing) issue with the same tool after reproducing the issue so we can look.
Updated by Steven Reich 3 days ago
- File config.txt config.txt added
- File Wouxun_KG-UV9PX_20250616.img Wouxun_KG-UV9PX_20250616.img added
- File win_system_info.txt win_system_info.txt added
- File debug_log.txt debug_log.txt added
[Uploaded from CHIRP next-20250606]
(Describe what you were doing)
Trying to update BUG-12033 to include the debug file.
(Describe what you expected to happen)
(Describe what actually happened instead)
I don't see any option to attach any files to this bug report.
(Has this ever worked before? New radio? Does it work with OEM software?)
Updated by Steven Reich 3 days ago
- File chirp_debug-p04of1z_.txt chirp_debug-p04of1z_.txt added
Hi Dan,
During the bug update, I don't see any option for attaching any files to
the bug report.
I read the instructions which say a debug file must be included, but I
don't see how to do that.
Instead I attached the debug file and the IMG file to this email reply.
Well, I tried attaching the IMG file, but the email was rejected, so I'm
trying just the debug file.
WI9SSR - Steven Reich
On 6/17/2025 11:31 PM, Dan Smith wrote: