CHIRP

Hi Frank,

I took at look at this and was able to reproduce the pop up you see. I can see the VFO A is set to the frequency in the error popup. I am not sure why you receive this pop up though. I'll do some digging today.

Debugging notes:

Line 804 in @uv5r.py@ is evaluating to @True@ which sets @rf.valid_bands = rax_bands@ but @rax_bands@ does not include the 70cm band.

https://chirp.danplanet.com/projects/chirp/repository/entry/chirp/drivers/uv5r.py#L804

        rax_bands = [self._vhf_range, self._220_range]

        if self._mmap is None:
            rf.valid_bands = [normal_bands[0], rax_bands[1], normal_bands[1]]
        elif not self._is_orig() and self._my_upper_band() == vhf_220_radio:   # <<<<<<<<<<<<<<< Evaluating to True
            rf.valid_bands = rax_bands
        else:
            rf.valid_bands = normal_bands
        rf.memory_bounds = (0, 127)
        return rf

In my debugger:
self._is_orig() = False
self._my_upper_band() = '\x02'
vhf_220_radio = '\x02'

I would like to call for a second opinion. CHIRP seems to think your radio upper band is 220 MHz based on the result from @self._my_upper_band()@

Maybe you could catch someone more knowledgeable than me on the chirp-users mailing list.

Hi Tony,

Thanks for your investigations and feedback.

What I don't understand is: it's not only the Baofeng showing this behaviour but also the Wouxun, so I don't think it can really be related to the device itself. But good to know that at least it's not a "user error" and I didn't overlook something obvious. What I can still try is to run the software on a different laptop to see if it's somehow related to the environment.

Thank you, I'll give it a try. I have never changed any of those settings though and nobody else had access to the device. Unless the device was shipped with these settings.

Since the Wouxoun has the same problem, I wonder where this setting is coming from as I didn't set it - makes no sense to restrict your own device.

Thank you, I'll give it a try. I have never changed any of those settings though and nobody else had access to the device. Unless the device was shipped with these settings.

Since the Wouxoun has the same problem, I wonder where this setting is coming from as I didn't set it - makes no sense to restrict your own device.

Thank you, I'll give it a try. I have never changed any of those settings though and nobody else had access to the device. Unless the device was shipped with these settings.

Since the Wouxoun has the same problem, I wonder where this setting is coming from as I didn't set it - makes no sense to restrict your own device.

Sorry for the repeated comment, my phone has caused this and it looks like I can't delete it.

Frank Baecker wrote:

Thank you, I'll give it a try. I have never changed any of those settings though and nobody else had access to the device. Unless the device was shipped with these settings.

Since the Wouxoun has the same problem, I wonder where this setting is coming from as I didn't set it - makes no sense to restrict your own device.

Somebody changed them from the factory defaults (typically VHF Low: 130, VHF High: 179 and UHF Low: 400, UHF High: 520) to VHF Low: 100, VHF High 199, UHF Low: 200, UHF High 999. It was the UHF Low: 200 that was causing the issue.

Baofeng UV-5R/UV-82 like radios send the band limits to CHIRP as part of cloning initialization process. That is what CHIRP uses to determine if it is programming a VHF/UHF model or a (now rare) VHF/220 model. Older radios always send the factory band limits. Some of the newer radios will update what is set back to CHIRP based on what the user may have changed the band limits to. On the models that do this, setting the lower UHF band limit anywhere from 200-299 will cause CHIRP to thing it is working with a VHF/220 model that doesn't support UHF frequencies.

I thought about changing it band limits back to factory but opted to keep the same range and just move the split.

Jim KC9HI

I understand the root cause but don't see how this happenec - the device was bought on Amazon as a new device (off the shelf) and had no previous owners. I haven't changed any of those settings directly on the device and since I couldn't even add the channels in Chirp, I also didn't perform any further changes there
.

I have now been able to fix the frequency settings. I couldn't load the image as it said "incompatible device" or something but I found the frequency settings you mentioned.
No idea why this was set like this. But it's fixed now, thank you!