Changes for page How to improve LoRaWAN distance
Last modified by Xiaoling on 2024/08/16 11:25
Change comment:
Uploaded new attachment "image-20221031233628-2.png", version {1}
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 2 removed)
Details
- Page properties
-
- Content
-
... ... @@ -10,6 +10,7 @@ 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 15 == 2.1 LoRa parameters that effect distance == ... ... @@ -44,6 +44,7 @@ 44 44 |(% style="width:134px" %)**AS923**|(% style="width:400px" %)14dBm|(% style="width:362px" %)SF=12|(% style="width:102px" %)125Khz 45 45 46 46 48 + 47 47 == 2.2 Adaptive Data Rate (ADR) and set max distance == 48 48 49 49 ... ... @@ -65,6 +65,7 @@ 65 65 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. 66 66 67 67 70 + 68 68 == 2.3 Check for short distance problem == 69 69 70 70 ... ... @@ -77,6 +77,7 @@ 77 77 [[image:image-20221006185826-3.png]] 78 78 79 79 83 + 80 80 == 2.4 Best software settings for the longest distance == 81 81 82 82 ... ... @@ -87,6 +87,8 @@ 87 87 * (% style="color:#037691" %)**AT+TXP=0** (%%) ~/~/ Use max power. 88 88 89 89 94 + 95 + 90 90 = 3. Analyze at the hardware side = 91 91 92 92 == 3.1 Check if the antenna path is good ~-~- For LSn50v2 series end node == ... ... @@ -100,12 +100,13 @@ 100 100 [[image:image-20221016081725-1.png||height="426" width="706"]] 101 101 102 102 109 + 103 103 = 4. Installation Guidelines = 104 104 105 105 == 4.1 Check the use environment == 106 106 107 107 108 -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.115 +First , User should notice: Radio link quality and performances are highly dependent of the environment. 109 109 110 110 (% style="color:blue" %)**Better performances can be reached with:** 111 111 ... ... @@ -122,6 +122,8 @@ 122 122 * Radio communication are usually killed with bad topographic conditions. It is usually not possible to communicate through a hill, even very small. 123 123 124 124 132 + 133 + 125 125 == 4.2 Improve the Antenna == 126 126 127 127 ... ... @@ -128,6 +128,7 @@ 128 128 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. 129 129 130 130 140 + 131 131 = 5. Some real-world case = 132 132 133 133 == 5.1 Server reason cause end node has problem on Join. == ... ... @@ -146,31 +146,4 @@ 146 146 147 147 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]] 148 148 149 - 150 -== 5.2 Chirpstack Default settings to 64 channels which cause Signal Poor. == 151 - 152 - 153 -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. 154 - 155 - 156 -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. 157 - 158 - 159 -Above issue was confirmed and solved after set the ChirpStack support channels to sub-band2. See below for photos during debug. 160 - 161 -[[image:image-20221031233628-2.png]] 162 - 163 - 164 -[[image:image-20221031233759-3.png]] 165 - 166 - 167 -[[image:image-20221101000006-1.png||height="353" width="931"]] 168 - 169 - 170 -= 6. Use a repeater = 171 - 172 -In some cases, user can consider use a repeater for limitation transmition. 173 - 174 -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]] 175 - 176 176
- 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