Repository navigation
chore(pointperfect): bump the client to quiet logging and non-interleaved MGA - #113
Merged
Merged
Conversation
dakejahl
force-pushed
the
chore/pointperfect-quiet-logs
branch
4 times, most recently
from
August 6, 2026 00:43
65f6dc8 to
a855e4a
Compare
Depends on ARK-Electronics/pointperfect-client-mavlink#3. The client logged about 50 lines a minute on a device; the bump brings the summarized log, the `verbose` key added to the packaged config here, the fix that stops assistance data being injected into the middle of a correction message, and closing the caster session while the GPS receiver is away instead of streaming corrections the autopilot will discard.
dakejahl
force-pushed
the
chore/pointperfect-quiet-logs
branch
from
August 6, 2026 17:39
a855e4a to
7ed77b6
Compare
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.
Summary
Bumps
pointperfect-client-mavlinkand adds theverbosekey to the packaged config.Depends on ARK-Electronics/pointperfect-client-mavlink#3 — merge that first, then this bump moves to the merged commit.
Problem
The pointperfect client logged a line per correction chunk, per forwarded MGA message and per
GPS_RTCM_DATA. Measured on a Jetson against the live NEAR-SPARTN-MGA mountpoint that is 49 lines a minute, which buries the events that matter in the Services page log view and in the journal.It also forwarded UBX-MGA assistance and corrections in caster stream order, so an assistance frame the caster spliced into the middle of a correction message was injected between the two halves of it. And nothing noticed when the GPS receiver disappeared: the client kept reporting a stale position to the caster and kept forwarding corrections the autopilot discards while its GPS driver re-configures.
Solution
The bumped client summarizes the stream every 30 seconds, keeps per-message output behind
verbose, injects assistance and corrections in separateGPS_RTCM_DATAsequences, and closes the caster session when GPS_RAW_INT stops — reconnecting when the receiver returns, which is also how it gets a fresh AssistNow burst. The packaged config gainsverbose = falseso the knob is visible in the UI config editor.On device: 49 log lines/minute before, 2 after, with the assistance burst reported as one block and RTK float retained.