Max retries is now a var that can be set between 1 to 15

This commit is contained in:
mikecarper committed 2026-04-24 00:08:10 -07:00
1 parent 577433ce47
commit 9c2ac5aa1c
8 files changed
+284 -29

No files matched your search

+36 -3
View File
@@ -117,14 +117,21 @@ This document provides an overview of CLI commands that can be sent to MeshCore
### Get or set recent repeater fallback prefix/SNR
**Usage:**
- `recent.repeater`
- `recent.repeater <prefix_hex> <snr_db>`
- `get recent.repeater`
- `get recent.repeater all`
- `get recent.repeater first <count>`
- `get recent.repeater last <count>`
- `set recent.repeater <prefix_hex> <snr_db>`
**Parameters:**
- `prefix_hex`: 1-3 bytes of next-hop prefix (hex)
- `snr_db`: SNR in dB (supports decimals; stored at x4 precision)
- `count`: number of entries to print
**Note:** `set` is rejected when the prefix already exists in neighbors.
**Notes:**
- `set` is rejected when the prefix already exists in neighbors.
- `all` prints oldest to newest; `first` prints the oldest N; `last` prints the newest N.
- Remote CLI replies include rows too, but may truncate when the packet payload limit is reached.
---
@@ -545,6 +552,32 @@ This document provides an overview of CLI commands that can be sent to MeshCore
---
#### View or change the number of direct retry attempts
**Usage:**
- `get direct.retry.count`
- `set direct.retry.count <value>`
**Parameters:**
- `value`: Retry attempts after initial TX (`1`-`15`)
**Default:** `3`
---
#### View or change the base direct retry wait (milliseconds)
**Usage:**
- `get direct.retry.base`
- `set direct.retry.base <value>`
**Parameters:**
- `value`: Base wait in milliseconds (`10`-`5000`)
**Default:** `200`
**Note:** The actual first retry wait is `base + computed_echo_wait_from_live_phy`.
---
#### [Experimental] View or change the processing delay for received traffic
**Usage:**
- `get rxdelay`