mudhorn/meshtastic
1
0
Fork 0
mirror of https://github.com/meshtastic/meshtastic.git synced 2024-11-09 23:24:10 -08:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Update docs/about/overview/mesh-alg.mdx

Browse source 
Co-authored-by: rcarteraz <robert.l.carter2@gmail.com>
This commit is contained in:
Ben Meadors 2024-07-14 10:48:00 -05:00 committed by GitHub
parent 73b1dc2910
commit 23d1693e91
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 17 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
docs/about/overview/mesh-alg.mdx
View file

@ -91,6 +91,23 @@ After node 0 received this rebroadcast, its message is acknowledged. Note that a
Since node 1 heard the rebroadcast by 2, it will not rebroadcast again. Node 3 heard the message for the first time and the HopLimit is not yet zero, so it starts a rebroadcast for potential other receivers.
![Mesh algorithm example](/img/SNR_based_flooding.webp)
### Regular Broadcast Intervals
Without additional modules configured, nodes will produce three different types of regularly intervaled traffic as part of the mesh:
1. Device Telemetry
- Controlled by `telemetry.device_update_interval`
- Default: 30 minutes
2. Position
- Controlled by `position.position_broadcast_secs`
- Default: 15 minutes* (with [smart broadcast](/docs/configuration/radio/position/#smart-broadcast) enabled)
3. NodeInfo user
- Controlled by `device.node_info_broadcast_secs`
- Default: 3 hours
As meshes grow larger and traffic becomes more contentious, the firmware will increase these intervals. This is in addition to duty cycle, channel, and air-time utilization throttling.
Starting with version 2.4.0, the firmware will scale back Telemetry, Position, and other ancillary port traffic for meshes larger than 40 nodes (nodes seen in the past 2 hours) using the following algorithm:
### Regular Broadcast Intervals