Skip to content
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

Add support for full CTCSS and DCS beacon options #478

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

bjpetit
Copy link
Contributor

@bjpetit bjpetit commented Jun 30, 2023

This change adds the ability to include the tone type specifier to a beacon's frequency info. Today a beacon can include the T{number} field to specify a tone. The APRS spec includes support for CTCSS tone squelch and DCS codes.
http://www.aprs.org/info/freqspec.txt
With this change the tone argument can be set to a value of the form specified in the spec. For example, specifying a CTCSS squelch of 107.3, the TONE argument can be set to C107, or if a DCS code of 047 is to be specified the TONE value can be set to D047.
If the TONE argument in a beacon line is set to just a numeric value, it will assume this is specifying a tone specifier as it always has and will add a leading T to the value specified.

I looked at the decoding path and it appears that the the beacon decode path already understands the different tone leading characters.

This change would imply a documentation change to add these options to the TONE argument in beacon lines.

@wb2osz
Copy link
Owner

wb2osz commented Jun 30, 2023

Thank you for the suggestion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants