Repository navigation
feat(beacons): position and status beacons (F2.2) - #237
Merged
Merged
Conversation
Each profile gets a position beacon (decay after a change, or a fixed interval; Send via, compressed, PHG) and a status beacon, both off by default, set in Settings > Beacons. They go out only while every F2.1 layer allows sending and after a position was sent by hand; a TNC never gets positions less than 10 minutes apart, beacons on one source are 10 seconds apart, an overdue one goes out once, and the first waits a random moment. The status bar shows the next beacon and why. Also makes a messaging test wait for the first copy before writing the second, so the ack's source isn't left to a race.
Contributor
Package reportVulnerable packagesNo known vulnerabilities in direct or transitive packages. Available package updates
Pinned versionsThese projects override the central version in
Checked at 357c701 against nuget.org. |
This was referenced Oct 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Builds F2.2 (closes #196) on APRS.NET's
AprsNet.Beacons(0.4.0-alpha.3).Engine (
Beaconer)DecayBeaconScheduleorFixedBeaconSchedule.transmit.position-unconfirmed).EngineStatus.TransmitgainsNextBeacon(when, which, why, on which source) andBeaconHeld.UI
Two changes from the spec, written into it
Moving (speed and turns) isn't offered until GPS (F3.6).
Also
AMessageHeardOnTwoSourcesIsShownOnceAndAckedWhereItCameFirstfailed about 1 run in 6 under full-suite load: both copies were written at once, so which arrived first was a race. It now waits for the first copy.Tests