CHIRP

In programming my Baofeng UV-5R:

When specifying an unusual input frequency for a repeater, whether cross-band or just wildly unrelated to an offset, the user specifies "split" under the Duplex column and then enters the input frequency into the Offset column. This works.

After having saved or written the programming to the radio, then trying to reopen or read the programming from the radio, the Duplex column for those channels changes to a "+" or "-" offset with that relative offset in the Offset column. Kind of annoying since they are awkward offsets like "+ 7.457500" or "- 3.945000" but still a working program.

Here's where the bug comes in. If you attempt to change the Duplex column to "split" again, rather than your offset converting to the human-readable input frequency, the Offset column changes to the same frequency as the output Frequency column. Your input frequency is now lost.

Suggestions:

• Fix the above bug so when switching from "+/-" to "split" that the program converts the value in the Offset column into the appropriate input frequency.

• Or, if the user specifies "split" in the first place, then remember this somewhere in the .img file so that it displays "split" again when the file is loaded.

• Or, default to "split" per user option, or by radio type.

• Or, (my personal favorite), add an Input Frequency column that supplements the Duplex and Offset columns. Remove "split" as a Duplex mode, and simply convert +/- offsets on the fly with the input frequency column, in either direction. Eg: If you enter a +/- offset value into the Offset column, the Input Frequency column will automatically adjust to show the calculated frequency. And visa-versa, if a frequency is entered into the Input Frequency column, the +/- offset will be calculated into the Offset column. Either of these columns can be optionally hidden under View > Columns menu.

Thanks for considering this bug and my suggestions.

Raccoon // EFNet