Repository navigation
fix(region-gating): describe dc.gate as true TX duty, default 35 - #11
Merged
Merged
Conversation
The firmware (dmc-dev PR #25, propagated to observer and packetlog on 2026-10-19) now measures dc.gate against the true TX duty cycle over 60 s instead of a share of the duty-cycle budget, with default threshold 35. - CLI Wiki (firmwareRegistry, nl/de descriptions), Region Gating help panel and i18n labels: true TX duty wording, default 35, re-open below 25%, 1% sub-band hint and the upgrade note. - regionCommands: default and clamp fallback 70 -> 35; tests follow. - RegionGatingForm: live status reads "duty", not "budget". - Changelog: firmware entry for the 10-19 merges (dc.gate threshold reset to 35 on upgrade, code-0 floods, filter limiters, SenseCAP GPS, observer MQTT prefs) and a toolbox entry, in EN/NL/DE.
Deploying dutch-meshcore-toolbox with
|
| Latest commit: |
90a5b9c
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://93083ae9.dutch-meshcore-toolbox.pages.dev |
| Branch Preview URL: | https://fix-main-dc-gate-true-duty-s.dutch-meshcore-toolbox.pages.dev |
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.
Why
The firmware now measures
dc.gateagainst the true TX duty cycle: the share of wall-clock time spent transmitting over the last 60 s. It used to measure a share of the duty-cycle budget. The default threshold changed from 70 to 35. This came in with Dutch-MeshCore/MeshCore#25 (dmc-dev), and on 2026-10-19 it was propagated todmc-observer-devanddmc-dev-packetlog. The toolbox still said "budget, default 70".Changes
dc.gate.threshanddc.gate.statusdescriptions (firmwareRegistry.ts,descriptions.nl/de.ts) now say true TX duty, default 35.set dutycycle. It now says regions re-open below 25%, suggests 10-15 on a 1% sub-band, and adds an upgrade note.regionCommands.ts: the default and the clamp fallback go from 70 to 35, and the tests follow.RegionGatingForm: the live status readsduty, notbudget.Test
npm run test:run: 289/289 pass.tsc -b: clean.docs/is not rebuilt in this PR.🤖 Generated with Claude Code