Mirrors
/
ARDEN-documentation
mirror of https://github.com/aredn/documentation.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

lqm latency wording

This commit is contained in:
Steve Lewis AB7PA 2022-05-24 09:48:45 -07:00 committed by WU2S
parent 5e33707520
commit de87e71296
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
arednGettingStarted/node_status.rst
View File

@ -119,7 +119,7 @@ Status
- *blocked - distance*: LQM determined that the remote node is either too close or too distant, based on the Min and Max Distance settings described in the *Advanced Configuration* section.
- *blocked - signal*: LQM determined that the SNR on the link is too low to reliably pass data, based on the Min SNR setting described in the *Advanced Configuration* section.
- *blocked - retries*: LQM determined that the retransmission rate was too high to reliably pass data.
- *blocked - latency*: LQM determined that the link latency was to long to reliably pass data.
- *blocked - latency*: LQM determined that the link latency was to high to reliably pass data.
- *blocked - dtd*: LQM blocks the RF interface on any nodes to which a DtD link also exists.
- *blocked - dup*: LQM blocks a link in cases when your node has an RF link to other nodes which themselves connect to each other via DtD. This can occur when there are multiple radios at a site using the same channel. The best remote node is chosen as the RF link for your node but the other possible RF connections are blocked as duplicates.
- *blocked - user*: LQM will block any node which you enter in the *User Blocked Nodes* field described in the *Advanced Configuration* section.