Bug #10993
closedChirp Next won't allow duplex to be set to off
100%
Description
Opened an existing file with the latest version of Chirp next and noticed that memory channels with duplex set to off now shows them with duplex set to split and the offset frequency of 1666.666650, which is well above the UV-5R frequency range. I tried to set the duplex to off, but it will not set to off. I also attempted to set duplex to off in memory channels that did not have duplex and it was set to split with the previously mentioned frequency. I saved the file under a new name and opened it with Chirp legacy to see what would happen and in Legacy it shows the channels with duplex set to off and nothing is in the offset column. I also downloaded from a radio with the same profile to see what would happen and it shows the same bug. I saved that as a new file and uploaded it to the radio. Radio performs as normal with duplex set to off. I also downloaded from the radio with the legacy version I have on my external hard drive and it shows duplex set to off with nothing in the offset frequency column.
I am using a laptop with Windows 10 as the OS.
Files
Updated by Jim Unroe 9 months ago
- File uv5r-off_fix.py uv5r-off_fix.py added
- Status changed from New to In Progress
- Assignee set to Jim Unroe
- Target version set to chirp-py3
Please give this a test. Here is how: LoadingTestModules
Updated by Jason Bryant 9 months ago
Jim Unroe wrote in #note-1:
Please give this a test. Here is how: LoadingTestModules
Thanks Jim. That test module worked. All memory channels with Duplex set to off are showing off and not the split mentioned in my report. I can also copy/paste, import, edit existing channels, and add new memory channels with duplex set to off without the split bug.
Updated by Anonymous 9 months ago
- Status changed from In Progress to Closed
- % Done changed from 0 to 100
Applied in changeset github|b1ce4174666598b1458d3aaa8f5e6188f49db5e5.