Skip to content

Update Backoff Settings to Enable Some Collision Avoidance#2311

Closed
KPrivitt wants to merge 119 commits intomeshcore-dev:mainfrom
KPrivitt:2026/Backoff-Defaults
Closed

Update Backoff Settings to Enable Some Collision Avoidance#2311
KPrivitt wants to merge 119 commits intomeshcore-dev:mainfrom
KPrivitt:2026/Backoff-Defaults

Conversation

@KPrivitt
Copy link
Copy Markdown

The current default values are:
_prefs.rx_delay_base = 0.0f; // turn off by default, was 10.0;
_prefs.tx_delay_factor = 0.5f; // was 0.25f
_prefs.direct_tx_delay_factor = 0.3f; // was 0.2

These control the Random Backoff behavior of a repeater, which reduces the probability of a collision between neighbor repeaters.

Backoff is essential in avoiding collisions. Many repeater owners are not aware of this capability and do not change them, this leaves the mesh under configured in order to avoid collisions. The default values are too low and are not providing any significant backoff for the Mesh.

The default value for rx_delay = 0, which is off. So, this mechanism is not being utilized. A recommended minimum value for rxdelay is 3

The default value for direct.x_delay = 0.3, which is provides 2 backoff slots, which has a high probability of a collision. A recommended minimum value for direct.x_delay is 1 which will provide 5 backoff slots and reduces the probability of a collision.

The default value for tx_delay = 0.5, which is provides 2 backoff slots, additional backoff slots will reduce the probability of a collision. A recommended minimum value for txdelay is 1.6 which provides 8 backoff slots and reduces the probability of a collision.

These all are configurable using CLI commands so users are still free to select their own preferred values and can turn them off.

Enabling some level of backoff will improve the performance of the Mesh.

Thomas Abbott and others added 30 commits January 29, 2026 16:55
Co-authored-by: Wessel <wessel@weebl.me>
Co-authored-by: Wessel <wessel@weebl.me>
Co-authored-by: Wessel <wessel@weebl.me>
Default LNA enabled=true and fix the sleep order
Merge branch 'dev' into dev-heltec-v4.3
Support for R1 Neo hardware. New variant and baseboard class.
* Known issues:
  - power management is not currently supported
  - power off via long button press is not implemented

Add support for Epson Seiko RX8130CE I2C Real-time clock.
We translate to af internally, it's easier to store and doesn't break
stored prefs. Made get/set af command show deprecated, but it still
works fine.
Co-authored-by: ViezeVingertjes <michael.overhorst@gmail.com>
Docs changes are to reflect how it is currently in fw

This adds ability to send datagram data to everyone in channel
Quency-D and others added 29 commits April 2, 2026 10:24
Fixed the initialization error of the BME680 sensor.
Repeater and Room Server environments in variants/thinknode_m5/platformio.ini
were using 'Thinknode M2' as the ADVERT_NAME, causing M5 nodes to advertise
with the wrong device name on the mesh.

- env:ThinkNode_M5_Repeater: 'Thinknode M2 Repeater' -> 'Thinknode M5 Repeater'
- env:ThinkNode_M5_room_server: 'Thinknode M2 Room Server' -> 'Thinknode M5 Room Server'
…Room')

env:Generic_ESPNOW_room_svr was using 'Heltec Room' as ADVERT_NAME,
causing Generic ESPNow room server nodes to advertise with the wrong
device name on the mesh.
…vert-name

fix: correct ADVERT_NAME for ThinkNode M5 (was M2)
…advert-name

fix: correct ADVERT_NAME for Generic ESPNow room server (was 'Heltec Room')
Nearly all LoRa boards use a boot button that pulls to ground when
pressed.
variants/thinknode_m5/platformio.ini contained actual WiFi SSID and
password credentials (Livebox-633C) committed by mistake. Replaced
with placeholder values consistent with other variants (myssid/mypwd).
…fi-credentials

fix: remove real WiFi credentials from ThinkNode M5 variant
Fix Heltec Wireless Paper battery reading
…ix_rp2040

RP2040 Update SX126X_DIO3_TCXO_VOLTAGE to 1.8 V
RFE: allow for INA3221 macro overrides in platform.io files
Default button polarity to active-LOW across all firmware types
The Waveshare RP2040-LoRa board has an RF switch with two complementary
control lines:
- DIO2 (CTRL)  -- driven automatically by the SX1262 chip: HIGH on TX,
  LOW on RX
- GPIO17 (!CTRL) -- was not configured in MeshCore, so it floated and
  the switch never properly selected the LNA/RX path

Without this pin driven, the RF switch never switches to RX mode,
resulting in completely degraded reception. TX was unaffected because
DIO2 alone is sufficient to activate the TX path.

Adding SX126X_RXEN=17 lets RadioLib drive GPIO17 as the complement of
DIO2, so the switch correctly routes the signal to the LNA on receive.

Reference: https://files.waveshare.com/wiki/RP2040-LoRa/Rp2040-lora-sch.pdf
…ue-sizes

Set OFFLINE_QUEUE_SIZE=256 for missing WiFi companion environments
docs: align gps output description with CLI
…rp2040-rx-sensitivity

Fixes meshcore-dev#2294 : RX path not enabled on Waveshare RP2040
xiao nrf52 companion usb: Add OFFLINE_QUEUE_SIZE=256
@KPrivitt KPrivitt closed this Apr 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.