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

correct typo on latency status

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

4
arednGettingStarted/node_status.rst
View File

@ -118,8 +118,8 @@ Status
- *blocked*: LQM determined that the link is unusable and has blocked it from use.
- *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 high to reliably pass data.
- *blocked - retries*: LQM determined that the retransmission rate is too high to reliably pass data.
- *blocked - latency*: LQM determined that the link latency is too 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.