Skip to Content
Last modified by Xiaoling on 2024/08/16 11:25
From version 16.1
edited by Edwin Chen
on 2022/10/31 23:38
Change comment: There is no comment for this version
To version 10.4
edited by Xiaoling
on 2022/10/15 16:26
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.Xiaoling
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 -
14 14  = 2.  Analyze at the software side =
15 15  
15 +
16 16  == 2.1  LoRa parameters that effect distance ==
17 17  
18 18  
... ... @@ -45,6 +45,7 @@
45 45  |(% style="width:134px" %)**AS923**|(% style="width:400px" %)14dBm|(% style="width:362px" %)SF=12|(% style="width:102px" %)125Khz
46 46  
47 47  
48 +
48 48  == 2.2  Adaptive Data Rate (ADR) and set max distance ==
49 49  
50 50  
... ... @@ -73,7 +73,7 @@
73 73  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.
74 74  
75 75  
76 -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)
77 77  
78 78  
79 79  [[image:image-20221006185826-3.png]]
... ... @@ -85,31 +85,18 @@
85 85  
86 86  Below are the settings for longest distance transmission. ( will reduce battery life)
87 87  
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.
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.
91 91  
92 92  
93 93  
94 -= 3.  Analyze at the hardware side =
95 += 3.  Installation Guidelines =
95 95  
96 -== 3.1  Check if the antenna path is good ~-~- For LSn50v2 series end node ==
97 97  
98 +== 3.1  Check the use environment ==
98 98  
99 -a) Open Enclosure and Check if the antenna connection to module is good.
100 100  
101 -b) check if the connector match.
102 -
103 -
104 -[[image:image-20221016081725-1.png||height="426" width="706"]]
105 -
106 -
107 -
108 -= 4.  Installation Guidelines =
109 -
110 -== 4.1  Check the use environment ==
111 -
112 -
113 113  First , User should notice: Radio link quality and performances are highly dependent of the environment.
114 114  
115 115  (% style="color:blue" %)**Better performances can be reached with:**
... ... @@ -119,6 +119,8 @@
119 119  * No high level radio interferes in the ISM band you use.
120 120  * At least 1 meter above the ground.
121 121  
110 +
111 +
122 122  (% style="color:blue" %)**Radio performances are degraded with:**
123 123  
124 124  * Obstacles: buildings, trees...
... ... @@ -128,7 +128,7 @@
128 128  
129 129  
130 130  
131 -== 4.2  Improve the Antenna ==
121 +== 3.2  Improve the Antenna ==
132 132  
133 133  
134 134  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.
... ... @@ -135,11 +135,12 @@
135 135  
136 136  
137 137  
138 -= 5.  Some real-world case =
128 += 4.  Some real-world case =
139 139  
140 -== 5.1  Server reason cause end node has problem on Join. ==
141 141  
131 +== 4.1  Server reason cause end node has problem on Join. ==
142 142  
133 +
143 143  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.
144 144  
145 145  
... ... @@ -153,25 +153,4 @@
153 153  
154 154  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]]
155 155  
156 -
157 -== 5.2 Chirpstack Default settings to 64 channels which cause Signal Poor. ==
158 -
159 -
160 -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.
161 -
162 -
163 -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.
164 -
165 -
166 -Above issue was confirmed and solved after set the ChirpStack support channels to sub-band2. See below for photos during debug.
167 -
168 -[[image:image-20221031233628-2.png]]
169 -
170 -
171 -[[image:image-20221031233759-3.png]]
172 -
173 -
174 -
175 -
176 -
177 177  
image-20221016081725-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -569.8 KB
Content
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