Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 22.2 >
edited by Xiaoling
on 2022/05/26 16:48
To version < 32.14 >
edited by Xiaoling
on 2022/07/13 15:24
>
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  
... ... @@ -18,17 +18,19 @@
18 18  * End Node traffic (from server UI) to shows end node activity in server. (Normaly possible)
19 19  * End Node Keys screen shot shows in end node and server. so we can check if the keys are correct. (In most case, we found keys doesn't match, especially APP EUI)
20 20  
21 -**~1. End Device Join Screen shot, we can check:**
22 22  
20 +
21 +(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
22 +
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]]
26 +[[image:image-20220526164956-15.png]]
27 27  
28 28  Console Output from End device to see the transmit frequency
29 29  
30 30  
31 -**2. Gateway packet traffic in gateway web or ssh. we can check:**
31 +(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
32 32  
33 33  * If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
34 34  * If the gateway gets the Join Accept message from server and transmit it via LoRa?
... ... @@ -38,7 +38,7 @@
38 38  Console Output from Gateway to see packets between end node and server.
39 39  
40 40  
41 -**3. Gateway Traffic Page in LoRaWAN Server**
41 +(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
42 42  
43 43  * If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
44 44  * If the server send back a Join Accept for the Join Request? if not, check if the keys from the device match the keys you put in the server, or try to choose a different server route for this end device.
... ... @@ -49,7 +49,7 @@
49 49  The Traffic for the End node in the server, use TTN as example
50 50  
51 51  
52 -**4. Data Page in LoRaWAN server**
52 +(% style="color:blue" %)**4. Data Page in LoRaWAN server**
53 53  
54 54  * If this data page shows the Join Request message from the end node? If not, most properly you have wrong settings in the keys. Keys in the server doesn't match the keys in End Node.
55 55  
... ... @@ -64,6 +64,7 @@
64 64  
65 65  = 2. Notice of US915/CN470/AU915 Frequency band =
66 66  
67 +
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  
110 +
109 109  [[image:image-20220526163941-8.png]]
110 110  
111 111  (((
112 112  CN470 Channels
115 +
116 +
113 113  )))
114 114  
115 115  (((
... ... @@ -120,6 +120,8 @@
120 120  
121 121  (((
122 122  TTN FREQUENCY PLAN
127 +
128 +
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  
138 +
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  
160 +
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  
190 +
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]]
197 +[[image:image-20220531161828-1.png]]
189 189  
190 190  receive windows for Class A and Class C
191 191  
201 +
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,13 +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.**
208 +* 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 -
201 201  == 5.2 See Debug Info ==
202 202  
212 +
203 203  (((
204 -**For LoRaWAN Server**
214 +(% style="color:blue" %)**For LoRaWAN Server**
205 205  )))
206 206  
207 207  (((
... ... @@ -231,7 +231,7 @@
231 231  
232 232  
233 233  (((
234 -**For LoRaWAN Gateway**
244 +(% style="color:blue" %)**For LoRaWAN Gateway**
235 235  )))
236 236  
237 237  (((
... ... @@ -246,7 +246,7 @@
246 246  
247 247  
248 248  (((
249 -**For End Node**
259 +(% style="color:blue" %)**For End Node**
250 250  )))
251 251  
252 252  (((
... ... @@ -254,23 +254,18 @@
254 254  )))
255 255  
256 256  (((
267 +(% style="color:#037691" %)**AT+RX2FQ=869525000**  (%%) **~-~-->**  The RX2 Window frequency
268 +(% style="color:#037691" %)**AT+RX2DR=3**          (%%) **~-~-->**  The RX2 DataRate
269 +(% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
270 +(% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
271 +
257 257  
258 258  )))
259 259  
260 260  (((
261 -(% class="box infomessage" %)
262 -(((
263 -AT+RX2FQ=869525000     ~-~--> The RX2 Window frequency
264 -AT+RX2DR=3      ~-~--> The RX2 DataRate
265 -AT+RX1DL=1000   ~-~--> Receive Delay 1
266 -AT+RX2DL=2000   ~-~--> Receive Delay 2
276 +(% style="color:blue" %)**when the device running, we can see below info:**
267 267  )))
268 -)))
269 269  
270 -(((
271 -**when the device running, we can see below info:**
272 -)))
273 -
274 274  {{{ [12502]***** UpLinkCounter= 0 *****
275 275   [12503]TX on freq 868500000 Hz at DR 0
276 276   [13992]txDone
... ... @@ -284,7 +284,7 @@
284 284  )))
285 285  
286 286  (((
287 -**Another message:**
292 +(% style="color:blue" %)**Another message:**
288 288  )))
289 289  
290 290  {{{ [12502]***** UpLinkCounter= 0 *****
... ... @@ -298,20 +298,22 @@
298 298   Receive data
299 299   1:0012345678}}}
300 300  
301 -(% class="wikigeneratedid" %)
302 -​​​​​​​
303 303  
304 -== 5.3 If problem doesn’t solve ==
307 +== 5.3 If problem doesn't solve ==
305 305  
306 -**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:**
307 307  
310 +(% 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:**
311 +
308 308  * End node console to show the transmit freuqency and DR.
309 309  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server.
310 310  * Gateway traffic (from server UI) to shows the data exchange between gateway and server.
311 311  * End Node traffic (from server UI) to shows end node activity in server.
312 312  
317 +
318 +
313 313  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
314 314  
321 +
315 315  (((
316 316  In LoRaWAN, the gatewat will use the frequency specify by the server to transmit a packet as downlink purpose. Each Frequency band has different downlink frequency. and the gateway has a frequency range limited to transmit downlink.
317 317  )))
... ... @@ -337,35 +337,29 @@
337 337  
338 338  = 7. Decrypt a LoRaWAN Packet =
339 339  
340 -~1. LHT65 End device configure:
341 341  
342 -(% class="box infomessage" %)
343 -(((
344 -Change to ABP Mode: AT+NJM=0
345 -)))
348 +(% style="color:blue" %)**1. LHT65 End device configure:**
346 346  
347 -(% class="box infomessage" %)
348 -(((
349 -Change to fix frequency: AT+CHS=904900000
350 -)))
350 +**Change to ABP Mode:  AT+NJM=0**
351 +**Change to fix frequency:  AT+CHS=904900000**
352 +**Change to fix DR:  AT+DR=0**
351 351  
352 -(% class="box infomessage" %)
353 -(((
354 -Change to fix DR: AT+DR=0
355 -)))
356 356  
357 -[[image:https://wiki.dragino.com/images/e/e6/Decrypt_a_LoRaWAN_Packet1.jpg||alt="Decrypt a LoRaWAN Packet1.jpg" height="607" width="558"]]
355 +[[image:image-20220526165525-16.png]]
358 358  
359 -2. In LG02 , configure to receive above message
360 360  
361 -[[image:https://wiki.dragino.com/images/c/c3/Decrypt_a_LoRaWAN_Packet2.jpg||alt="Decrypt a LoRaWAN Packet2.jpg" height="337" width="558"]]
358 +(% style="color:blue" %)**2. In LG02 , configure to receive above message**
362 362  
360 +[[image:image-20220526165612-17.png]]
361 +
362 +
363 363  In LG02 console, we can see the hex receive are:
364 364  
365 -[[image:https://wiki.dragino.com/images/f/f1/Decrypt_a_LoRaWAN_Packet3.jpg||alt="Decrypt a LoRaWAN Packet3.jpg" height="179" width="558"]]
365 +[[image:image-20220526171112-21.png]]
366 366  
367 -3. Decode the info in web
368 368  
368 +(% style="color:blue" %)**3. Decode the info in web**
369 +
369 369  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
370 370  
371 371  Need these three fields:
... ... @@ -376,9 +376,10 @@
376 376  
377 377  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
378 378  
380 +
379 379  [[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]]
380 380  
381 -[[image:https://wiki.dragino.com/images/7/77/Decrypt_a_LoRaWAN_Packet4.png||alt="Decrypt a LoRaWAN Packet4.png" height="390" width="558"]]
383 +[[image:image-20220526171029-20.png]]
382 382  
383 383  (((
384 384   The FRMPayload is the device payload.
... ... @@ -387,12 +387,15 @@
387 387  
388 388  = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
389 389  
392 +
390 390  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.
391 391  
395 +
392 392  = 9. Why do I see a "MIC Mismatch" error message from the server? =
393 393  
398 +
394 394  (((
395 -1)If the user receives a "MIC Mismatch" message after registering the node on the server.
400 +1)  If the user receives a "MIC Mismatch" message after registering the node on the server.
396 396  )))
397 397  
398 398  (((
... ... @@ -414,11 +414,14 @@
414 414  * (((
415 415  If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
416 416  
422 +
423 +
417 417  
418 418  )))
419 419  
420 420  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
421 421  
429 +
422 422  * If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
423 423  
424 424  (((
... ... @@ -436,38 +436,78 @@
436 436  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]]
437 437  
438 438  
447 +
439 439  
440 440  )))
441 441  
442 442  = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
443 443  
453 +
454 +(((
444 444  It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
456 +)))
445 445  
458 +(((
446 446  AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
460 +)))
447 447  
462 +(((
448 448  AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
464 +)))
449 449  
466 +(((
450 450  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
468 +)))
451 451  
470 +(((
452 452  AT+APPEUI=00 00 00 00 00 00 00 00
472 +)))
453 453  
474 +(((
475 +
476 +)))
454 454  
478 +(((
455 455  You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number.
480 +)))
456 456  
482 +(((
457 457  You can rewrites the keys by running commands in AT Console
458 458  
459 -For example：
485 +
486 +)))
460 460  
488 +(((
489 +**For example：**
490 +)))
491 +
492 +(((
461 461  AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
494 +)))
462 462  
496 +(((
463 463  AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
498 +)))
464 464  
500 +(((
465 465  AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
502 +)))
466 466  
504 +(((
467 467  AT+APPEUI=2C 45 47 E3 24 12 23 24
506 +)))
468 468  
508 +(((
469 469  (Any combination of 16 bit codes can be used）
470 470  
471 471  
512 += 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
513 +)))
514 +
515 +
516 +Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
517 +
518 +
519 +
472 472  (% class="wikigeneratedid" %)
473 473  
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