Bug #12006
closedLoaded module not taking effect
0%
Description
(Describe what you were doing) Downloaded img from radio, then loaded module uvk5_egzumer3.py
(Describe what you expected to happen)
The receive mode list in this module contains rf.valid_modes = ["FM", "NFM", "AM", "NAM", "USB”]. I expected to be able to set any of these modes.
(Describe what actually happened instead)
but only the first four show up in Chirp.
(Has this ever worked before? New radio? Does it work with OEM software?)
This is a new radio. My radio came preloaded with OSFW-bd90ca3 firmware so I have never tried any other firmware. Although Chirp says it loaded the py file, there is no indication that it registered.
Note that I added a line to the script to allow approval of bd90ca3.
def k5_approve_firmware(cls, firmware):
return (
firmware.startswith('EGZUMER ') or
firmware.startswith('OSFW-bd90ca3')
)
Files
Updated by Sandy Trevor 19 days ago
- File config.txt config.txt added
- File Quansheng_UV-K5_20250524.img Quansheng_UV-K5_20250524.img added
- File macos_system_info.txt macos_system_info.txt added
- File debug_log.txt debug_log.txt added
[Uploaded from CHIRP next-20250516]
Updated by Dan Smith 18 days ago
Two things, as it says on LoadingTestModules, you must load the module before you open an image in order for the new module to be used. As you state, and your debug log shows, and the pop-up warns: you're loading the module after the image has been loaded, so the active tab will not be updated.
Second, the egzumer variant is supported in the main chirp tree now, so there should be no need to load it externally. If you are, and from any other location, then you're probably regressing to something older and less likely to work.
Obviously, you know the danger of just modifying any of the code to blindly accept and operate on another firmware variant. There was an attempt to support some version of OSFW that ended up stalled because there were changes made that OSFW didn't interpret the same as the others. So, beware.
Updated by Sandy Trevor 17 days ago
Dan, thank you very much for the response. I loaded the module both BEFORE and after opening the image, and all combinations but none worked. All I am trying to do is enable USB on a channel. USB is not available in Chirp, but is listed in the py file. I have tried to determine from the py file which bit sets USB modulation, and it appears to be bit 5 in byte 0xb in a channel block. I tried setting it with k5tool but it did not seem to have any effect. So at this point I’m giving up on getting Chirp to set USB, but I’d appreciate any pointers on how to set a channel to USB. I know the radio can do it, because USB is one of the modes in the spectrum scanner.
Updated by Dan Smith 17 days ago
- Status changed from New to Not a bug
Your log shows that you didn't load the module before opening the image. I don't know what changes you made to the file, but I'd guess that you're adding something somewhere you think should matter, when it doesn't. Either way, this functionality is used all the time and it's clearly working, so without evidence to the contrary, I'm going to say the stated issue this bug is reporting is not valid.
Anyway, you really need help with the radio, which I can't provide. This bug tracker is for chirp bugs not general development stuff and definitely not for radio internals, so I'll close it as such.
Good luck.
Updated by Justin Case 16 days ago
I don't want to turn this place into tech support for radio users (as Dan said, this is place to report bugs in Chirp ), so, I'll be short:
a) OSFW-bd90ca3 firmware is neither stock firmware by Quansheng nor custom firmware by Egzumer. As far as I know, it is by FAGCI. It has been discussed in #11410 #11423 #11488
b) If you want to use your Quansheng reliably with Chirp, you have to flash back either stock or Egzumer's firmware using k5prog_win (GUI) or k5prog (CLI) tools. On a Mac only latter will do and it needs to be compiled first.
Updated by Sandy Trevor 15 days ago
- File test_uvk5_scanlist.py test_uvk5_scanlist.py added
Justin-
I very much appreciate your response. I did figure out that bd99ca3 just wasn’t going to support USB, so I bit the bullet, loaded k5tool on my mac, then loaded egzumer firmware. Yesterday I was receiving FT8 on my UV-K5 (which is why I wanted USB).
But I still want to learn how to use the Load Module feature of CHIRP. I wrote python modules that CHIRP says “module loaded” but despite everything I have tried (and everything suggested by chatgpt) none take effect. For example, I wrote a module to add ScanList columns to Chirp so channels could be selected for either scan list (attached). Dan said many people have successfully used Load Module but there are secrets to using it that i am unable to discover so far. I realize Load Module is temporary, but isn't this the way to test a feature before trying to rebuild Chirp?
-Sandy