Feature #2361
closedAllow copying between radios where some settings are not supported
0%
Description
Currently it is impossible to copy a memory channel from one radio to another when the channel in the first radio uses a setting that doesn't exist in the second radio.
Example: UV-5R has a "duplex off" option to disable transmitting but KG-UV8D does not. Trying to copy a channel using this option results in an error message and the channel can not be copied at all (even though the frequency, name, tone, etc settings should be able to transfer). This is probably not what anyone ever wants. A more sensible behavior would be to revert that setting to the default value and copy everything else if possible, or ask the user what value to use on the new radio (and remember that translation when copying a group of channels all at once).
The second option would also make a different, less severe, manifestation of the bug easier to resolve: names for power levels are not standardized at all between models. One of my radios has "High" and "Low", another has "H" and "L", yet another has "Hi", "Mid1", "Mid2", and "Low." In this case the user could to choose to convert all "H" channels to "Mid1" and all "L" channels to "Lo" without manually changing everything later.
Updated by Tom Hayward over 9 years ago
You're right, duplex "off" should have logic for copying to radios that don't support "off". The import/export code is full of little checks like this for other things.
Power level conversion is done in watts. Say a mobile radio has an "L1" setting that equals 5 watts. If you copy this to a handheld where 5 watts is "High", it will set to "High" when copying.
Updated by Stephen Cavilia over 9 years ago
I didn't realize the power levels were actually that smart. But those are easy to change en masse if you want to for example copy a bunch of HT channels to a mobile and run them at 20W instead of 5W so it's not really an issue.
I think the KG-UV8D code has some general flakiness related to power level handling that I was misinterpreting as due to radio-to-radio translation logic not knowing to convert High to H.
Updated by Bernhard Hailer over 4 years ago
- Tracker changed from Bug to Feature
- Status changed from New to Closed
Looks like this feature isn't really needed.