Update frequency table variable names and logging statements. #967
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resubmitting against the master branch.
This helps clean up some of the P25 frequency table (Bandplan) information variable names and logging statements.
channel_id_to_string
function tochannel_id_to_freq_string
to help clarify what is being returned.channel_to_string
function that prints out the channels in the format of<XX>-<YYYY>
where XX is the bandplan ID and YYYY is the channel ID.Following this PR, I plan to add a second PR to expand and add the ability to input custom frequency tables for systems that aren't correctly sending them over the control channel.