Merge remote-tracking branch 'origin/keymindCascade' into keymindCascade

This commit is contained in:
mikecarper committed 2026-10-23 10:41:27 -07:00
commit 4c0f2acf64
8 files changed
+80 -16

No files matched your search

+7 -4
View File
@@ -23,9 +23,10 @@ Chat remains plain text. A separate GPS-free NodeInfo is sent after the first
successful chat transmission per used channel/identity per boot; the explicit
command can also request one. Automatic metadata waits for a 250 ms gap after
the latest successful MT transmission; explicit requests bypass that gap.
MT heard-repeat retries use the Companion's
`flood.retry.count`, with the metadata cap and `flood.retry.advert` gate for
NodeInfo.
MT messages default to 15 total attempts (the first send plus up to 14 retries)
unless a matching repeat is heard. The Companion's `flood.retry.count` can lower
that budget; `0` or `mt.hops 0` sends once. NodeInfo keeps its metadata cap and
`flood.retry.advert` gate. Scheduled beacons remain fire and forget.
See [carrier-wave RF checks](carrier_wave.md) for `cw on [seconds]`,
`cw2 on [seconds]`, and stopping a carrier with `off`.
@@ -5181,7 +5182,8 @@ section apply to infrastructure roles. Companion does not expose repeater
bridge or prefix retry filters.
On builds with [Meshtext channel chat](radio_profiles.md#heard-repeat-retries),
`flood.retry.count` also limits retries of the node's own MT channel text.
`flood.retry.count` also limits retries of the node's own MT channel text,
with a cap of 15 total attempts (the original plus 14 retries).
Retries reuse the original encoded packet and stop after hearing a matching
forwarded copy with a lower remaining hop limit. This is not a recipient ACK
or a delivery guarantee. NodeInfo permits at most one additional transmission,
@@ -5191,6 +5193,7 @@ received MT traffic or apply MeshCore prefix/bridge rules to MT packets.
`set mt.hops 0` disables heard-repeat retries, without suppressing the original
chat or its first-use NodeInfo. `get mt.retry` reports retry/heard/exhausted
counters, pending work and the configured count without changing settings.
Scheduled beacons always send once per occurrence.
**Search terms:** flood tx retries, flood retry attempts, flood retransmissions, broadcast retries.
+7 -6
View File
@@ -813,9 +813,11 @@ networks or guaranteed message delivery.
#### Heard-repeat retries
MT channel chat uses the Companion's saved `flood.retry.count` budget: `0`
disables retries, and `1`–`15` allows that many extra transmissions after the
initial send. Locally originated MT traffic is hop zero for the
MT channel messages default to **15 total attempts** without a heard repeat:
the initial send and up to 14 retries. They use the Companion's saved
`flood.retry.count`, capped at 14 extra transmissions for MT text. Lower saved
counts retain their extra-retry meaning; `0` disables retries. MeshCore's retry
count meaning is unchanged. Locally originated MT traffic is hop zero for the
`flood.retry.path` gate, so a gate of `0` still permits it; the group-data gate
does not apply to channel text. `mt.hops 0` disables heard-repeat retries
because peers cannot forward a packet with no remaining hop budget; the
@@ -826,9 +828,8 @@ airtime-based flood spacing and the normal CAD and airtime limits rather than
transmitting continuously.
`get mt.retry` is read-only diagnostics: it reports retry transmissions,
matching heard repeats, exhausted retry sequences, pending work and the
configured retry count. Use `set flood.retry.count`, not this getter, to change
the budget.
matching heard repeats, exhausted retry sequences, pending work and the shared
configured retry `count`. Use `set flood.retry.count` to change the budget.
A matching over-air copy with a lower remaining hop limit cancels the retry
sequence. Merely receiving another message, an unchanged-hop copy or a packet
+2
View File
@@ -64,6 +64,8 @@ or Meshtext NodeInfo. Meshtext beacons request no ACK and have no forwarding
budget. MeshCore Public uses one locally transmitted flood; other MeshCore
nodes may relay that flood according to their own policies.
Beacons are **fire and forget**, independent of `flood.retry.count` and MT
message retries. They do not wait for an echo or resend when none is heard.
The transmitter briefly borrows the physical radio, sends once, and restores
its normal receive settings, power, and RX power saving. It does not occupy,
replace, or persist changes to `radio2`, including a temporary second profile.