CHIRP

Typo in the bug description ... offset entered for 600KHz was .006

I got an extra zero when I typed it into the original bug report.

Offset error is still there on CHIRP daily-20180510 with Baofeng Uv-3r+.
Offset is off by a factor of 1000. (you need to set 0.076 to get an offset of 7.6)

Please correct this.
Many thanx in advance!

I have a Baofeng UV-3R:
I can confirm this bug.
When Im setting up a offset 0.05 it becomes 5.000 MHz on the radio.

Also official programming software UV-3R v1.11 have this bug too.
Probably some newer radios have firmware changes.

I have a UV-5R and a UV-5RX3. If I set the VFO A or VFO B offset to @999.999000@ in CHIRP and upload the image to either radio, the radio interprets the values as @099.990@ (observable in each radio under menu item 26). If I save the image from CHIRP, close it, and then reopen it in CHIRP, I see @99.990000@ as the value in CHIRP.

I can set the value manually in either radio to @999.999@ (which is useful if you want to configure the radio to prohibit transmission in VFO mode). I'm pretty sure that if I set it manually in the radio and then read the configuration from the radio using CHIRP it will also show up as @99.990000@ in CHIRP.

I'm wondering if this is due to the same root cause?

Yegor Maksimov wrote:

This modified driver does not work with latesr Chirp (CHIRP daily-20190410).
I have an error message: "Unable to load module: No module named wouxun_common"
Which version is supported by this fixed driver?

I based this on chirp-daily-20180906 (the python source version on Linux).

Dan Smith wrote:

The attached modified driver isn't acceptable directly into the code for the following reasons:

1. It makes multiple changes, not all related to the offset issue
2. It is improperly formatted and won't pass the tests
3. It needs to go to the mailing list in patch format per the developer process docs
4. I'm not sure that it will fix all radios and not regress earlier models

It sounds like the OEM software has the same issue? Do all radios behave the same, or do some interpret the offset field differently? The code as provided does not distinguish between behaviors of multiple radios, which means if we just import the code as it is, it may fix the issue for some versions and break it for others (which would make it pointless to include in chirp, IMHO).

The UV-3R Plus radios that I have were all sourced from the same vendor at the same time and all suffered from this issue. If I had the raw reads from from several radios that worked with the original driver, I'm willing to see if I can differentiate between the two radio software versions and formally submit this as a single issue patch. Is there formal documentation for CHIRP's formatting standards or just the test suite mentioned at https://chirp.danplanet.com/projects/chirp/wiki/DevelopersProcess ?

I have the Baofeng UV-3R+, and do not experience this issue. When using Chirp, I allow the default offset of 0.600, and it works correctly with the repeater. If there's anything I can to to help reproduce any behavior, let me know.

According to #5205, the problem exists in radios with newer firmware.