Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

idea: automatically remove channels that are out of range #157

Closed
DC7IA opened this issue Oct 28, 2021 · 4 comments
Closed

idea: automatically remove channels that are out of range #157

DC7IA opened this issue Oct 28, 2021 · 4 comments
Labels
enhancement New feature or request

Comments

@DC7IA
Copy link
Contributor

DC7IA commented Oct 28, 2021

An idea for an additional feature:

An option to automatically remove channels that are out of range when writing to a radio.

This allows maintaining a single codeplug for a variety of radios with different ranges.

For example a codeplug containing frequencies in the 2 m and 70 cm amateur radio bands can then be written to a 70 cm radio. The 2 m channels simply aren't used.

Like this:

The following changels are out of range. Do you want to omit them when writing to the radio?

[ Yes, all of them ] [ Select channels to omit ] [ Abort writing ]

Or maybe something similar.

@DC7IA
Copy link
Contributor Author

DC7IA commented Oct 28, 2021

I guess that's not too difficult to do given that there are already checks for channels that are out of range.

@hmatuschek
Copy link
Owner

This is more complicated that you think, as channels might be referenced in scan lists and DMR APRS configurations as revert channels. So I have to be very careful not to produce a inconsistent codeplug. It would be easier to simply set them to "RX only". The MD390 manufacturer CPS, however, will then stop working properly.

@DC7IA
Copy link
Contributor Author

DC7IA commented Oct 28, 2021

The MD390 manufacturer CPS, however, will then stop working properly.

Then ask the user and then do the appropriate action?

Removing channels that are out of range before writing is a better solution long-term, I think. But I also think there are a lot more things that are more relevant for now. :D

@hmatuschek hmatuschek added the enhancement New feature or request label Oct 31, 2021
@hmatuschek
Copy link
Owner

I've just enabled "Discussions" for this repository. Hopefully I can bundle also email discussions there. How about moving this issue there?

Repository owner locked and limited conversation to collaborators Nov 6, 2021

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants