Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 30.3 >
edited by Xiaoling
on 2022/05/30 10:57
To version < 32.6 >
edited by Xiaoling
on 2022/07/13 15:03
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,4 +1,4 @@
1 -**~ Contents:**
1 +**~ Table of Contents:**
2 2  
3 3  {{toc/}}
4 4  
... ... @@ -6,6 +6,7 @@
6 6  
7 7  = 1. OTAA Join Process Debug =
8 8  
9 +
9 9  These pages are useful to check what is wrong on the Join process. Below shows the four steps that we can check the Join Process.
10 10  \\**If user has checked below steps and still can't solve the problem, please send us (support @ dragino.com) the sceenshots for each step to check. They include:**
11 11  
... ... @@ -61,6 +61,7 @@
61 61  
62 62  = 2. Notice of US915/CN470/AU915 Frequency band =
63 63  
65 +
64 64  (((
65 65  If user has problem to work with lorawan server in band US915/AU915/CN470, he can check:
66 66  )))
... ... @@ -103,10 +103,13 @@
103 103  
104 104  AU915 Channels
105 105  
108 +
106 106  [[image:image-20220526163941-8.png]]
107 107  
108 108  (((
109 109  CN470 Channels
113 +
114 +
110 110  )))
111 111  
112 112  (((
... ... @@ -117,6 +117,8 @@
117 117  
118 118  (((
119 119  TTN FREQUENCY PLAN
125 +
126 +
120 120  )))
121 121  
122 122  (((
... ... @@ -126,6 +126,7 @@
126 126  
127 127  = 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
128 128  
136 +
129 129  In this case, we can check if the frequency band matches in End Node, Gateway and LoRaWAN server. A typical case is using US915 in ChirpStack server as below:
130 130  
131 131  * **End node** ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Sensor. ADR is also enable, this is the default settings for dragino sensors.
... ... @@ -147,6 +147,7 @@
147 147  
148 148  = 4. Transmision on ABP Mode =
149 149  
158 +
150 150  (((
151 151  In ABP mode, there is a Frame Counter Checks. With this check enabled, the server will only accept the frame with a higher counter. If you reboot the device in ABP mode, the device will start from count 0, so you won't be able to see the frame update in server.
152 152  )))
... ... @@ -176,6 +176,7 @@
176 176  
177 177  == 5.1 How it work ==
178 178  
188 +
179 179  LoRaWAN End node will open two receive windows to receive the downstream data. If the downstream packets arrive the end node at these receive windows, the end node will be able to get this packet and process it.
180 180  
181 181  (((
... ... @@ -182,10 +182,11 @@
182 182  Depends on Class A or Class C, the receive windows will be a little difference,
183 183  )))
184 184  
185 -[[image:image-20220526164547-11.png]]
195 +[[image:image-20220531161828-1.png]]
186 186  
187 187  receive windows for Class A and Class C
188 188  
199 +
189 189  Below are the requirement for the End Device to receive the packets.
190 190  
191 191  * The End Device must open the receive windows: RX1 or RX2
... ... @@ -192,14 +192,13 @@
192 192  * The LoRaWAN server must send a downstream packet, and the gateway forward this downstream packet for this end node.
193 193  * This downstream packet must arrive to the end node while RX1 or RX2 is open.
194 194  * This packet must match the frequency of the RX1 or RX2 window.
195 -* This packet must match the DataRate of RX1(RX1DR) or RX2 (RX2DR). **This is the common fail point, because different lorawan server might use different RX2DR and they don't info End Node via ADR message so cause the mismatch. If this happen, user need to change the RX2DR to the right value in end node. In OTAA, LoRaWAN Server will send the RX2DR setting in Join Accept message so the end node will auto adjust. but ABP uplink doesn't support this auto change.**
206 +* This packet must match the DataRate of RX1(RX1DR) or RX2 (RX2DR). (% style="color:red" %)**This is the common fail point, because different lorawan server might use different RX2DR and they don't info End Node via ADR message so cause the mismatch. If this happen, user need to change the RX2DR to the right value in end node. In OTAA, LoRaWAN Server will send the RX2DR setting in Join Accept message so the end node will auto adjust. but ABP uplink doesn't support this auto change.**
196 196  
197 -
198 -
199 199  == 5.2 See Debug Info ==
200 200  
210 +
201 201  (((
202 -**For LoRaWAN Server**
212 +(% style="color:blue" %)**For LoRaWAN Server**
203 203  )))
204 204  
205 205  (((
... ... @@ -229,7 +229,7 @@
229 229  
230 230  
231 231  (((
232 -**For LoRaWAN Gateway**
242 +(% style="color:blue" %)**For LoRaWAN Gateway**
233 233  )))
234 234  
235 235  (((
... ... @@ -244,7 +244,7 @@
244 244  
245 245  
246 246  (((
247 -**For End Node**
257 +(% style="color:blue" %)**For End Node**
248 248  )))
249 249  
250 250  (((
... ... @@ -252,23 +252,18 @@
252 252  )))
253 253  
254 254  (((
265 +(% style="color:#037691" %)**AT+RX2FQ=869525000**  (%%) **~-~-->**  The RX2 Window frequency
266 +(% style="color:#037691" %)**AT+RX2DR=3**          (%%) **~-~-->**  The RX2 DataRate
267 +(% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
268 +(% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
269 +
255 255  
256 256  )))
257 257  
258 258  (((
259 -(% class="box infomessage" %)
260 -(((
261 -AT+RX2FQ=869525000     ~-~--> The RX2 Window frequency
262 -AT+RX2DR=3      ~-~--> The RX2 DataRate
263 -AT+RX1DL=1000   ~-~--> Receive Delay 1
264 -AT+RX2DL=2000   ~-~--> Receive Delay 2
274 +(% style="color:blue" %)**when the device running, we can see below info:**
265 265  )))
266 -)))
267 267  
268 -(((
269 -**when the device running, we can see below info:**
270 -)))
271 -
272 272  {{{ [12502]***** UpLinkCounter= 0 *****
273 273   [12503]TX on freq 868500000 Hz at DR 0
274 274   [13992]txDone
... ... @@ -282,7 +282,7 @@
282 282  )))
283 283  
284 284  (((
285 -**Another message:**
290 +(% style="color:blue" %)**Another message:**
286 286  )))
287 287  
288 288  {{{ [12502]***** UpLinkCounter= 0 *****
... ... @@ -297,8 +297,9 @@
297 297   1:0012345678}}}
298 298  
299 299  
300 -== 5.3 If problem doesn’t solve ==
305 +== 5.3 If problem doesn't solve ==
301 301  
307 +
302 302  (% style="color:red" %)**If user has checked below steps and still can't solve the problem, please send us (support @ dragino.com) the sceenshots for each step to check. They include:**
303 303  
304 304  * End node console to show the transmit freuqency and DR.
... ... @@ -308,6 +308,7 @@
308 308  
309 309  
310 310  
317 +
311 311  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
312 312  
313 313  (((
... ... @@ -340,15 +340,7 @@
340 340  (% class="box infomessage" %)
341 341  (((
342 342  **Change to ABP Mode: AT+NJM=0**
343 -)))
344 -
345 -(% class="box infomessage" %)
346 -(((
347 347  **Change to fix frequency: AT+CHS=904900000**
348 -)))
349 -
350 -(% class="box infomessage" %)
351 -(((
352 352  **Change to fix DR: AT+DR=0**
353 353  )))
354 354  
... ... @@ -437,7 +437,6 @@
437 437  * (((
438 438  Some node decoders may not have filtering function, or you need decoders of other servers and formats. Please send an email to [[david.huang@dragino.cc>>mailto:david.huang@dragino.cc]]
439 439  
440 -
441 441  
442 442  )))
443 443  
... ... @@ -497,8 +497,15 @@
497 497  
498 498  (((
499 499  (Any combination of 16 bit codes can be used）
498 +
499 +
500 += 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
500 500  )))
501 501  
502 502  
504 +Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
505 +
506 +
507 +
503 503  (% class="wikigeneratedid" %)
504 504  
image-20220531161828-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +98.6 KB
Content
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0