Algorithm to Automatically Adjust Repeater Parameters to Optimize the Mesh using a local density measurement

[KPrivitt]

Attached are two document that examines the various repeater parameters (rxdelay, txdelay, direct.txdelay, CR) and proposes a density metric to automatically adjust them to optimize a repeater for its current environment. By automating this, the entire mesh would improve (collisions would be reduced) and repeater owners that leave their repeaters at the non-optimum default values would have them automatically adjusted to an improved value.

Comments for improvements and corrections would be greatly appreciated.

https://discord.com/channels/1343693475589263471/1482520833476919427/1482520833476919427

https://discord.com/channels/1343693475589263471/1482520833476919427/1483211551463833772

[stachuman]

Well, why link to discord, not sure about others - but I can't read it.

[Magalex2x14]

Let me attach documents published by the author.

Proposal- MeshCore factors in selecting rxdelay txdelay and direct.txdelay.pdf
Probability of Collision with N Repeaters S Slots.pdf
White Paper 1 - Using rxdelay, txdelay and direct.txdelay to Minimize Collisions in a MeshCore Routing.pdf
White Paper 2 - How Acks and DMs work together.pdf
White Paper 3 - MeshCore Repeater AGC Behavior and Density Based Tuning.pdf
White Paper 4 - Duplicate Suppression and Random Transmit Backoff.pdf
White Paper 5- Why Flood DM Paths Jump.pdf
White Paper 6 - Why are Error Rates so High.pdf
White Paper 7 - Coding Rate (CR) Architecture.pdf

[stachuman]

I can only comment - super interesting papers

[stachuman]

Have created PR - Autotune delays based on White Paper 1
Not sure how contributors will assess it :) - but let's see
I'm running tests on my nodes

[stachuman]

I see that official contributors (I'm not official contributor - this is my first PR) are not convinced that delay autotune is something required to add to the code. I had a very short discussion at discord and conclusion is so far - "show results of tests", so can't say if PR is going to be accepted. On top, I'm not sure, I have the right environment. @KPrivitt do you have convincing test results?

The more popular solution becomes, the less users take care to configure it properly. That for sure I can see in my area :(