Changes for page How to improve LoRaWAN distance
Last modified by Xiaoling on 2024/08/16 11:25
<
edited by Edwin Chen
on 2022/10/16 08:17
on 2022/10/16 08:17
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 4 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.Edwin - Content
-
... ... @@ -4,8 +4,6 @@ 4 4 5 5 6 6 7 - 8 - 9 9 = 1. OverView = 10 10 11 11 ... ... @@ -12,6 +12,7 @@ 12 12 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. 13 13 14 14 13 + 15 15 = 2. Analyze at the software side = 16 16 17 17 == 2.1 LoRa parameters that effect distance == ... ... @@ -37,18 +37,19 @@ 37 37 38 38 **End node actually value when TXP=0 and DR=0** 39 39 40 -(% border="1" cellspacing=" 3" style="background-color:#f2f2f2; width:1002px" %)41 -|(% style=" background-color:#4f81bd; color:white; width:134px" %)**Frequency band**|(% style="background-color:#4f81bd; color:white; width:400px" %)**Output Power in LoRa Module (consider 2dB antenna)**|(% style="background-color:#4f81bd; color:white; width:362px" %)(((39 +(% border="1.5" cellspacing="4" style="background-color:#ffffcc; color:black; width:1002px" %) 40 +|(% style="width:134px" %)**Frequency band**|(% style="width:400px" %)**Output Power in LoRa Module (consider 2dB antenna)**|(% style="width:362px" %)((( 42 42 **Spreading Factor(Higher SF can transmit further)** 43 -)))|(% style=" background-color:#4f81bd; color:white; width:102px" %)**Band Width**42 +)))|(% style="width:102px" %)**Band Width** 44 44 |(% style="width:134px" %)**EU868**|(% style="width:400px" %)14dBm|(% style="width:362px" %)SF=12|(% style="width:102px" %)125Khz 45 45 |(% 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 46 46 |(% style="width:134px" %)**AS923**|(% style="width:400px" %)14dBm|(% style="width:362px" %)SF=12|(% style="width:102px" %)125Khz 47 47 47 + 48 48 == 2.2 Adaptive Data Rate (ADR) and set max distance == 49 49 50 50 51 - (% style="color:#037691" %)**ADR**(%%)is the feature that Server will ask End Node to adjust the TXP and DR according to some rules in the server. This is for the purpose of Network Management and Optimize End Node battery life-time.51 +**ADR** is the feature that Server will ask End Node to adjust the TXP and DR according to some rules in the server. This is for the purpose of Network Management and Optimize End Node battery life-time. 52 52 53 53 54 54 By default, ADR is turn on((% style="color:#037691" %)**AT+ADR=1**) (%%)so End node ADR feature is enable. ... ... @@ -58,50 +58,42 @@ 58 58 59 59 (% style="color:#037691" %)**AT+ADR=0** 60 60 61 -(% style="color:#037691" %)**AT+DR=0 ~/~/(%%) Use longest distance modulation61 +(% style="color:#037691" %)**AT+DR=0** 62 62 63 -(% style="color:#037691" %)**AT+TXP=0 (%%)~/~/ Use max power For EU868, max power can be is AT+TXP=5063 +(% style="color:#037691" %)**AT+TXP=0** 64 64 65 65 66 66 This can be downlink via the LoRaWAN downlink command, see [[this link>>url:http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/#H8.2UseDownlinkCommandtosetafixuplinkDR]] for reference. 67 67 68 68 69 + 69 69 == 2.3 Check for short distance problem == 70 70 71 71 72 72 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. 73 73 75 + 74 74 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 75 78 + 76 76 [[image:image-20221006185826-3.png]] 77 77 78 78 82 + 79 79 == 2.4 Best software settings for the longest distance == 80 80 81 81 82 82 Below are the settings for longest distance transmission. ( will reduce battery life) 83 83 84 -* (% style="color:#037691" %)**AT+ADR=0** (% style="color:#037691" %)**(downlinkpayload: 2200FFFF)**85 -* (% style="color:#037691" %)**AT+DR=0** ,the longest distance modulation (% style="color:#037691" %)**(downlinkpayload: 220000FF)**86 -* (% style="color:#037691" %)**AT+TXP=0** For EU868, max power can be is AT+TXP=50 (% style="color:#037691" %)** (downlinkpayload: 22000000)**88 +* (% style="color:#037691" %)**AT+ADR=0** (%%)~/~/ Disable ADR 89 +* (% style="color:#037691" %)**AT+DR= 0** (%%)~/~/ Use the smallest DR 90 +* (% style="color:#037691" %)**AT+TXP=0** (%%) ~/~/ Use max power. 87 87 88 88 89 - 90 -== 2.5 Debug in Software == 91 - 92 - 93 -Dragino can help client to debug the software for the distance issue. In the case , please send us below info: 94 - 95 -* Detail packets include for Join Request, Join Accept, Uplink & Downlink, These packets should include: 96 -** RSSI, DataRate, FCNT, Frequency. 97 -** MIC command detail & Payload detail. 98 - 99 - 100 100 = 3. Analyze at the hardware side = 101 101 102 -== 3.1 Check if the antenna path is good ~-~- For LS N50v2 series end node ==95 +== 3.1 Check if the antenna path is good ~-~- For LSn50v2 series end node == 103 103 104 - 105 105 a) Open Enclosure and Check if the antenna connection to module is good. 106 106 107 107 b) check if the connector match. ... ... @@ -114,7 +114,7 @@ 114 114 == 4.1 Check the use environment == 115 115 116 116 117 -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.109 +First , User should notice: Radio link quality and performances are highly dependent of the environment. 118 118 119 119 (% style="color:blue" %)**Better performances can be reached with:** 120 120 ... ... @@ -123,6 +123,7 @@ 123 123 * No high level radio interferes in the ISM band you use. 124 124 * At least 1 meter above the ground. 125 125 118 + 126 126 (% style="color:blue" %)**Radio performances are degraded with:** 127 127 128 128 * Obstacles: buildings, trees... ... ... @@ -131,7 +131,6 @@ 131 131 * Radio communication are usually killed with bad topographic conditions. It is usually not possible to communicate through a hill, even very small. 132 132 133 133 134 - 135 135 == 4.2 Improve the Antenna == 136 136 137 137 ... ... @@ -138,6 +138,7 @@ 138 138 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. 139 139 140 140 133 + 141 141 = 5. Some real-world case = 142 142 143 143 == 5.1 Server reason cause end node has problem on Join. == ... ... @@ -148,6 +148,7 @@ 148 148 149 149 Below is the output log in gateway side ( SSH Access to Gateway and Check Station log) 150 150 144 + 151 151 [[image:image-20221006185826-4.png]] 152 152 153 153 ... ... @@ -155,32 +155,4 @@ 155 155 156 156 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]] 157 157 158 - 159 -== 5.2 Chirpstack Default settings to 64 channels which cause Signal Poor. == 160 - 161 - 162 -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. 163 - 164 - 165 -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. 166 - 167 - 168 -Above issue was confirmed and solved after set the ChirpStack support channels to sub-band2. See below for photos during debug. 169 - 170 -[[image:image-20221031233628-2.png]] 171 - 172 - 173 -[[image:image-20221031233759-3.png]] 174 - 175 - 176 -[[image:image-20221101000006-1.png||height="353" width="931"]] 177 - 178 - 179 -= 6. Use a repeater = 180 - 181 - 182 -In some cases, user can consider use a repeater for limitation transmition. 183 - 184 -See here for how to set up: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20All%20Gateway%20models/LoRaWAN%20IoT%20Kit%20v3%20User%20Manual/#H7.Example6:LimitedLoRaWANrelay >>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20All%20Gateway%20models/LoRaWAN%20IoT%20Kit%20v3%20User%20Manual/#H7.Example6:LimitedLoRaWANrelay]] 185 - 186 186
- image-20221031233524-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -75.1 KB - Content
- image-20221031233628-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -72.3 KB - Content
- image-20221031233759-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -80.4 KB - Content
- image-20221101000006-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -88.5 KB - Content