Changes for page How to improve LoRaWAN distance
Last modified by Xiaoling on 2024/08/16 11:25
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 5 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.Edwin - 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 ... ... @@ -44,8 +44,6 @@ 44 44 |(% style="width:134px" %)**US915**|(% style="width:400px" %)20 or 22 dBm (depends on max output of module)|(% style="width:362px" %)SF=10|(% style="width:102px" %)125Khz 45 45 |(% style="width:134px" %)**AS923**|(% style="width:400px" %)14dBm|(% style="width:362px" %)SF=12|(% style="width:102px" %)125Khz 46 46 47 - 48 - 49 49 == 2.2 Adaptive Data Rate (ADR) and set max distance == 50 50 51 51 ... ... @@ -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)75 +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]] ... ... @@ -86,20 +86,31 @@ 86 86 87 87 Below are the settings for longest distance transmission. ( will reduce battery life) 88 88 89 -* (% style="color:#037691" %)AT+ADR=0 (%%)~/~/ Disable ADR 90 -* (% style="color:#037691" %)AT+DR= 0 (%%)~/~/ Use the smallest DR 91 -* (% style="color:#037691" %)AT+TXP=0 (%%) ~/~/ Use max power. 87 +* (% style="color:#037691" %)**AT+ADR=0** (%%)~/~/ Disable ADR 88 +* (% style="color:#037691" %)**AT+DR= 0** (%%)~/~/ Use the smallest DR 89 +* (% style="color:#037691" %)**AT+TXP=0** (%%) ~/~/ Use max power. 92 92 91 += 3. Analyze at the hardware side = 93 93 93 +== 3.1 Check if the antenna path is good ~-~- For LSn50v2 series end node == 94 94 95 -= 3. Installation Guidelines = 96 96 96 +a) Open Enclosure and Check if the antenna connection to module is good. 97 97 98 - ==3.1 Check theuse environment==98 +b) check if the connector match. 99 99 100 100 101 - First , User should notice:Radio link quality and performances are highly dependentof the environment.101 +[[image:image-20221016081725-1.png||height="426" width="706"]] 102 102 103 + 104 + 105 += 4. Installation Guidelines = 106 + 107 +== 4.1 Check the use environment == 108 + 109 + 110 +First , User should notice: Radio link quality and performances are highly dependent of the environment.Even you have the same hardware and antenna, Different installation will result in different performance. 111 + 103 103 (% style="color:blue" %)**Better performances can be reached with:** 104 104 105 105 * Outdoor environment. ... ... @@ -107,8 +107,6 @@ 107 107 * No high level radio interferes in the ISM band you use. 108 108 * At least 1 meter above the ground. 109 109 110 - 111 - 112 112 (% style="color:blue" %)**Radio performances are degraded with:** 113 113 114 114 * Obstacles: buildings, trees... ... ... @@ -116,21 +116,18 @@ 116 116 * High ISM band usage by other technologies. 117 117 * Radio communication are usually killed with bad topographic conditions. It is usually not possible to communicate through a hill, even very small. 118 118 126 +== 4.2 Improve the Antenna == 119 119 120 120 121 -== 3.2 Improve the Antenna == 122 - 123 - 124 124 In some case, we have to install the device inside the chamber or next to a metal case. So the signal between the antenna and the receiver (gateway) is blocked by the metal. This will greatly reduce the signal. In such case, we can consider using antenna extend cable to extend the antenna to a better position. 125 125 126 126 127 127 128 -= 4. Some real-world case =133 += 5. Some real-world case = 129 129 135 +== 5.1 Server reason cause end node has problem on Join. == 130 130 131 -== 4.1 Server reason cause end node has problem on Join. == 132 132 133 - 134 134 In one case, the customer is using AWS IoT Core and gateway to connect to AWS via Basic Station Connection, Frequency Band is AU915 sub-band 2. For some unknown reason, AWS always set downlink power to 0dBm, which cause the gateway only emit a very low power and lead to a short distance for sensor. 135 135 136 136 ... ... @@ -144,4 +144,27 @@ 144 144 145 145 Reference Link: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Change%20Gateway%20Power/#H1.A0Overview>>http://wiki.dragino.com/xwiki/bin/view/Main/Change%20Gateway%20Power/#H1.A0Overview]] 146 146 151 + 152 +== 5.2 Chirpstack Default settings to 64 channels which cause Signal Poor. == 153 + 154 + 155 +In this case, User use a Chirpstack LoRaWAN server with default settings. The Frequency Band is US915 and default settings of Chirpstack has all channels ( All sub-bands , total 72 channels) enable. User use a LDS03A and a LPS8N LoRaWAN gateway for the test. 156 + 157 + 158 +There is a strange issue: LDS03 has a very good RSSI ( RSSI=-40) during OTAA Join. But The LDS03A give a very poor RSSI after OTAA Join. After debug, it proves that the issue is with ChirpStack Frequency band settings. The ChirpStack server enables all 72 channels and the LDS03A will also use all channels after OTAA Join, but the LPS8N only can support 8 channels and set to Sub-Band2. When the LDS03A sends an uplink packet in the channel LPS8N doesn't support, because LDS03A is very close to LPS8N, LPS8N pick up this not support frequency and send to server. So in the platform we see a uplink packet with very poor RSSI. 159 + 160 + 161 +Above issue was confirmed and solved after set the ChirpStack support channels to sub-band2. See below for photos during debug. 162 + 163 +[[image:image-20221031233628-2.png]] 164 + 165 + 166 +[[image:image-20221031233759-3.png]] 167 + 168 + 169 +[[image:image-20221101000006-1.png||height="353" width="931"]] 170 + 171 + 172 + 173 + 147 147
- image-20221016081725-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Edwin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +569.8 KB - Content
- image-20221031233524-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Edwin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +75.1 KB - Content
- image-20221031233628-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Edwin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +72.3 KB - Content
- image-20221031233759-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Edwin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +80.4 KB - Content
- image-20221101000006-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Edwin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +88.5 KB - Content