Skip to Content
Last modified by Xiaoling on 2024/08/16 11:25
From version 10.4
edited by Xiaoling
on 2022/10/15 16:26
Change comment: There is no comment for this version
To version 10.5
edited by Xiaoling
on 2022/10/15 16:28
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -10,9 +10,9 @@
10 10  In real-world deployment for LoRa, distance is a common topic. We always want to have the longest distance. This chapter shows some instructions for how to improve this.
11 11  
12 12  
13 +
13 13  = 2.  Analyze at the software side =
14 14  
15 -
16 16  == 2.1  LoRa parameters that effect distance ==
17 17  
18 18  
... ... @@ -74,7 +74,7 @@
74 74  According to the above technology, if we have a problem on the distance, we can first check if the end node is trying to longest distance modulation already. We can see that from the LoRaWAN server. Below is an example from Chirpstack.
75 75  
76 76  
77 -We can see the traffic in gateway’s page and know that the distance is SF12 / BW125. (note, server is not able to know Transmit Power settings from End Node)
77 +We can see the traffic in gateway's page and know that the distance is SF12 / BW125. (note, server is not able to know Transmit Power settings from End Node)
78 78  
79 79  
80 80  [[image:image-20221006185826-3.png]]
... ... @@ -94,7 +94,6 @@
94 94  
95 95  = 3.  Installation Guidelines =
96 96  
97 -
98 98  == 3.1  Check the use environment ==
99 99  
100 100  
... ... @@ -127,7 +127,6 @@
127 127  
128 128  = 4.  Some real-world case =
129 129  
130 -
131 131  == 4.1  Server reason cause end node has problem on Join. ==
132 132  
133 133