Re: [chirp_devel] Untunable/tuning step frequencies

For instance, the radio cannot tune 450.611 so the radio refuses user entry (onboard keypad), but when 450.612 is entered the radio automatically adds 500 Hz to make 450.6125.

This may be how it's stored in the memory and that's fine, but the automatic adding of 500Hz is UI behavior that we shouldn't mimic in CHIRP, IMHO. So, I think that if they enter something with a 500Hz offset, you should do whatever you need to make it store and return properly in the memory, but if they omit the 500Hz, you should reject the memory in set_memory() just like if something else wasn't doable.

--Dan