Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 21.1 >
edited by Xiaoling
on 2022/05/26 16:46
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,14 +1,12 @@
1 -**~ Contents:**
1 +**~ Table of Contents:**
2 2  
3 -(((
4 -
5 -)))
6 -
7 7  {{toc/}}
8 8  
9 9  
6 +
10 10  = 1. OTAA Join Process Debug =
11 11  
9 +
12 12  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.
13 13  \\**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:**
14 14  
... ... @@ -23,7 +23,7 @@
23 23  * If the device is sending join request to server?
24 24  * What frequency the device is sending?
25 25  
26 -[[image:image-20220526163523-1.png]]
24 +[[image:image-20220526164956-15.png]]
27 27  
28 28  Console Output from End device to see the transmit frequency
29 29  
... ... @@ -64,6 +64,7 @@
64 64  
65 65  = 2. Notice of US915/CN470/AU915 Frequency band =
66 66  
65 +
67 67  (((
68 68  If user has problem to work with lorawan server in band US915/AU915/CN470, he can check:
69 69  )))
... ... @@ -106,10 +106,13 @@
106 106  
107 107  AU915 Channels
108 108  
108 +
109 109  [[image:image-20220526163941-8.png]]
110 110  
111 111  (((
112 112  CN470 Channels
113 +
114 +
113 113  )))
114 114  
115 115  (((
... ... @@ -120,6 +120,8 @@
120 120  
121 121  (((
122 122  TTN FREQUENCY PLAN
125 +
126 +
123 123  )))
124 124  
125 125  (((
... ... @@ -129,6 +129,7 @@
129 129  
130 130  = 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
131 131  
136 +
132 132  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:
133 133  
134 134  * **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.
... ... @@ -150,6 +150,7 @@
150 150  
151 151  = 4. Transmision on ABP Mode =
152 152  
158 +
153 153  (((
154 154  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.
155 155  )))
... ... @@ -179,6 +179,7 @@
179 179  
180 180  == 5.1 How it work ==
181 181  
188 +
182 182  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.
183 183  
184 184  (((
... ... @@ -185,10 +185,11 @@
185 185  Depends on Class A or Class C, the receive windows will be a little difference,
186 186  )))
187 187  
188 -[[image:image-20220526164547-11.png]]
195 +[[image:image-20220531161828-1.png]]
189 189  
190 190  receive windows for Class A and Class C
191 191  
199 +
192 192  Below are the requirement for the End Device to receive the packets.
193 193  
194 194  * The End Device must open the receive windows: RX1 or RX2
... ... @@ -195,12 +195,13 @@
195 195  * The LoRaWAN server must send a downstream packet, and the gateway forward this downstream packet for this end node.
196 196  * This downstream packet must arrive to the end node while RX1 or RX2 is open.
197 197  * This packet must match the frequency of the RX1 or RX2 window.
198 -* 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.**
199 199  
200 200  == 5.2 See Debug Info ==
201 201  
210 +
202 202  (((
203 -**For LoRaWAN Server**
212 +(% style="color:blue" %)**For LoRaWAN Server**
204 204  )))
205 205  
206 206  (((
... ... @@ -211,7 +211,7 @@
211 211  Configure a downstream to the end device
212 212  )))
213 213  
214 -[[image:https://wiki.dragino.com/images/thumb/8/82/Downstream_debug_1.png/600px-Downstream_debug_1.png||height="217" width="600"]]
223 +[[image:image-20220526164623-12.png]]
215 215  
216 216  (((
217 217  Set a downstream in TTN and see it is sent
... ... @@ -222,7 +222,7 @@
222 222  This downstream info will then pass to the gateway downstream list. and include the DR which is used (SF9BW125) in EU868 is DR3
223 223  )))
224 224  
225 -[[image:https://wiki.dragino.com/images/thumb/d/dc/Downstream_debug_2.png/600px-Downstream_debug_2.png||height="245" width="600"]]
234 +[[image:image-20220526164650-13.png]]
226 226  
227 227  (((
228 228  Gateway Traffic can see this downstream info
... ... @@ -230,7 +230,7 @@
230 230  
231 231  
232 232  (((
233 -**For LoRaWAN Gateway**
242 +(% style="color:blue" %)**For LoRaWAN Gateway**
234 234  )))
235 235  
236 236  (((
... ... @@ -237,7 +237,7 @@
237 237  When the downstream packet appear on the traffic of Gateway page. The LoRaWAN gateway can get it from LoRaWAN server and transmit it. In Dragion Gateway, this can be checked by runinng "logread -f" in the SSH console. and see below:
238 238  )))
239 239  
240 -[[image:https://wiki.dragino.com/images/thumb/2/21/Downstream_debug_3.png/600px-Downstream_debug_3.png||height="195" width="600"]]
249 +[[image:image-20220526164734-14.png]]
241 241  
242 242  (((
243 243  Gateway Sent out this packet
... ... @@ -245,7 +245,7 @@
245 245  
246 246  
247 247  (((
248 -**For End Node**
257 +(% style="color:blue" %)**For End Node**
249 249  )))
250 250  
251 251  (((
... ... @@ -253,23 +253,18 @@
253 253  )))
254 254  
255 255  (((
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 +
256 256  
257 257  )))
258 258  
259 259  (((
260 -(% class="box infomessage" %)
261 -(((
262 -AT+RX2FQ=869525000     ~-~--> The RX2 Window frequency
263 -AT+RX2DR=3      ~-~--> The RX2 DataRate
264 -AT+RX1DL=1000   ~-~--> Receive Delay 1
265 -AT+RX2DL=2000   ~-~--> Receive Delay 2
274 +(% style="color:blue" %)**when the device running, we can see below info:**
266 266  )))
267 -)))
268 268  
269 -(((
270 -**when the device running, we can see below info:**
271 -)))
272 -
273 273  {{{ [12502]***** UpLinkCounter= 0 *****
274 274   [12503]TX on freq 868500000 Hz at DR 0
275 275   [13992]txDone
... ... @@ -283,7 +283,7 @@
283 283  )))
284 284  
285 285  (((
286 -**Another message:**
290 +(% style="color:blue" %)**Another message:**
287 287  )))
288 288  
289 289  {{{ [12502]***** UpLinkCounter= 0 *****
... ... @@ -297,15 +297,20 @@
297 297   Receive data
298 298   1:0012345678}}}
299 299  
300 -== 5.3 If problem doesn’t solve ==
301 301  
302 -**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:**
305 +== 5.3 If problem doesn't solve ==
303 303  
307 +
308 +(% 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:**
309 +
304 304  * End node console to show the transmit freuqency and DR.
305 305  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server.
306 306  * Gateway traffic (from server UI) to shows the data exchange between gateway and server.
307 307  * End Node traffic (from server UI) to shows end node activity in server.
308 308  
315 +
316 +
317 +
309 309  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
310 310  
311 311  (((
... ... @@ -337,29 +337,24 @@
337 337  
338 338  (% class="box infomessage" %)
339 339  (((
340 -Change to ABP Mode: AT+NJM=0
349 +**Change to ABP Mode: AT+NJM=0**
350 +**Change to fix frequency: AT+CHS=904900000**
351 +**Change to fix DR: AT+DR=0**
341 341  )))
342 342  
343 -(% class="box infomessage" %)
344 -(((
345 -Change to fix frequency: AT+CHS=904900000
346 -)))
354 +[[image:image-20220526165525-16.png]]
347 347  
348 -(% class="box infomessage" %)
349 -(((
350 -Change to fix DR: AT+DR=0
351 -)))
352 352  
353 -[[image:https://wiki.dragino.com/images/e/e6/Decrypt_a_LoRaWAN_Packet1.jpg||alt="Decrypt a LoRaWAN Packet1.jpg" height="607" width="558"]]
354 -
355 355  2. In LG02 , configure to receive above message
356 356  
357 -[[image:https://wiki.dragino.com/images/c/c3/Decrypt_a_LoRaWAN_Packet2.jpg||alt="Decrypt a LoRaWAN Packet2.jpg" height="337" width="558"]]
359 +[[image:image-20220526165612-17.png]]
358 358  
361 +
359 359  In LG02 console, we can see the hex receive are:
360 360  
361 -[[image:https://wiki.dragino.com/images/f/f1/Decrypt_a_LoRaWAN_Packet3.jpg||alt="Decrypt a LoRaWAN Packet3.jpg" height="179" width="558"]]
364 +[[image:image-20220526171112-21.png]]
362 362  
366 +
363 363  3. Decode the info in web
364 364  
365 365  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
... ... @@ -374,7 +374,7 @@
374 374  
375 375  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh/?data=40c1190126800100024926272bf18bbb6341584e27e23245&nwkskey=00000000000000000000000000000111&appskey=00000000000000000000000000000111>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/?data=40c1190126800100024926272bf18bbb6341584e27e23245&nwkskey=00000000000000000000000000000111&appskey=00000000000000000000000000000111]]
376 376  
377 -[[image:https://wiki.dragino.com/images/7/77/Decrypt_a_LoRaWAN_Packet4.png||alt="Decrypt a LoRaWAN Packet4.png" height="390" width="558"]]
381 +[[image:image-20220526171029-20.png]]
378 378  
379 379  (((
380 380   The FRMPayload is the device payload.
... ... @@ -385,6 +385,7 @@
385 385  
386 386  Since firmware v1.8, LHT65 will send MAC command to request time, in the case if DR only support max 11 bytes, this MAC command will be bundled to a separate uplink payload with 0x00.
387 387  
392 +
388 388  = 9. Why do I see a "MIC Mismatch" error message from the server? =
389 389  
390 390  (((
... ... @@ -431,37 +431,74 @@
431 431  * (((
432 432  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]]
433 433  
434 -
435 435  
436 436  )))
437 437  
438 438  = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
439 439  
444 +(((
440 440  It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
446 +)))
441 441  
448 +(((
442 442  AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
450 +)))
443 443  
452 +(((
444 444  AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
454 +)))
445 445  
456 +(((
446 446  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
458 +)))
447 447  
460 +(((
448 448  AT+APPEUI=00 00 00 00 00 00 00 00
462 +)))
449 449  
464 +(((
465 +
466 +)))
450 450  
468 +(((
451 451  You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number.
470 +)))
452 452  
472 +(((
453 453  You can rewrites the keys by running commands in AT Console
474 +)))
454 454  
455 -For example：
476 +(((
477 +**For example：**
478 +)))
456 456  
480 +(((
457 457  AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
482 +)))
458 458  
484 +(((
459 459  AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
486 +)))
460 460  
488 +(((
461 461  AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
490 +)))
462 462  
492 +(((
463 463  AT+APPEUI=2C 45 47 E3 24 12 23 24
494 +)))
464 464  
496 +(((
465 465  (Any combination of 16 bit codes can be used）
466 466  
467 467  
500 += 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
501 +)))
502 +
503 +
504 +Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
505 +
506 +
507 +
508 +(% class="wikigeneratedid" %)
509 +
image-20220526164734-14.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +120.3 KB
Content
image-20220526164956-15.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +634.4 KB
Content
image-20220526165525-16.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +185.4 KB
Content
image-20220526165612-17.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +116.5 KB
Content
image-20220526165855-18.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +183.7 KB
Content
image-20220526170151-19.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +70.4 KB
Content
image-20220526171029-20.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +70.6 KB
Content
image-20220526171112-21.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +183.8 KB
Content
image-20220531161828-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +98.6 KB
Content

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0