Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 32.16 >
edited by Xiaoling
on 2022/08/12 11:06
To version < 28.1 >
edited by Xiaoling
on 2022/05/26 17:10
>
Change comment: Uploaded new attachment "image-20220526171029-20.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -1,12 +1,14 @@
1 -**~ Table of Contents:**
1 +**~ Contents:**
2 2  
3 +(((
4 +
5 +)))
6 +
3 3  {{toc/}}
4 4  
5 5  
6 -
7 7  = 1. OTAA Join Process Debug =
8 8  
9 -
10 10  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.
11 11  \\**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:**
12 12  
... ... @@ -16,10 +16,8 @@
16 16  * End Node traffic (from server UI) to shows end node activity in server. (Normaly possible)
17 17  * 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)
18 18  
21 +**~1. End Device Join Screen shot, we can check:**
19 19  
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  
... ... @@ -28,9 +28,8 @@
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 31  
32 -(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
33 -
34 34  * If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
35 35  * If the gateway gets the Join Accept message from server and transmit it via LoRa?
36 36  
... ... @@ -39,7 +39,7 @@
39 39  Console Output from Gateway to see packets between end node and server.
40 40  
41 41  
42 -(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
41 +**3. Gateway Traffic Page in LoRaWAN Server**
43 43  
44 44  * If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
45 45  * 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.
... ... @@ -50,7 +50,7 @@
50 50  The Traffic for the End node in the server, use TTN as example
51 51  
52 52  
53 -(% style="color:blue" %)**4. Data Page in LoRaWAN server**
52 +**4. Data Page in LoRaWAN server**
54 54  
55 55  * 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.
56 56  
... ... @@ -63,10 +63,8 @@
63 63  Check if OTAA Keys match the keys in device
64 64  
65 65  
66 -
67 67  = 2. Notice of US915/CN470/AU915 Frequency band =
68 68  
69 -
70 70  (((
71 71  If user has problem to work with lorawan server in band US915/AU915/CN470, he can check:
72 72  )))
... ... @@ -109,13 +109,10 @@
109 109  
110 110  AU915 Channels
111 111  
112 -
113 113  [[image:image-20220526163941-8.png]]
114 114  
115 115  (((
116 116  CN470 Channels
117 -
118 -
119 119  )))
120 120  
121 121  (((
... ... @@ -126,8 +126,6 @@
126 126  
127 127  (((
128 128  TTN FREQUENCY PLAN
129 -
130 -
131 131  )))
132 132  
133 133  (((
... ... @@ -135,10 +135,8 @@
135 135  )))
136 136  
137 137  
138 -
139 139  = 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
140 140  
141 -
142 142  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:
143 143  
144 144  * **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.
... ... @@ -158,10 +158,8 @@
158 158  )))
159 159  
160 160  
161 -
162 162  = 4. Transmision on ABP Mode =
163 163  
164 -
165 165  (((
166 166  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.
167 167  )))
... ... @@ -187,12 +187,10 @@
187 187  Disable Frame Counter Check in ABP Mode
188 188  
189 189  
190 -
191 191  = 5. Downstream Debug =
192 192  
193 193  == 5.1 How it work ==
194 194  
195 -
196 196  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.
197 197  
198 198  (((
... ... @@ -199,11 +199,10 @@
199 199  Depends on Class A or Class C, the receive windows will be a little difference,
200 200  )))
201 201  
202 -[[image:image-20220531161828-1.png]]
188 +[[image:image-20220526164547-11.png]]
203 203  
204 204  receive windows for Class A and Class C
205 205  
206 -
207 207  Below are the requirement for the End Device to receive the packets.
208 208  
209 209  * The End Device must open the receive windows: RX1 or RX2
... ... @@ -210,16 +210,12 @@
210 210  * The LoRaWAN server must send a downstream packet, and the gateway forward this downstream packet for this end node.
211 211  * This downstream packet must arrive to the end node while RX1 or RX2 is open.
212 212  * This packet must match the frequency of the RX1 or RX2 window.
213 -* 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.**
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.**
214 214  
215 -
216 -
217 -
218 218  == 5.2 See Debug Info ==
219 219  
220 -
221 221  (((
222 -(% style="color:blue" %)**For LoRaWAN Server**
203 +**For LoRaWAN Server**
223 223  )))
224 224  
225 225  (((
... ... @@ -248,9 +248,8 @@
248 248  )))
249 249  
250 250  
251 -
252 252  (((
253 -(% style="color:blue" %)**For LoRaWAN Gateway**
233 +**For LoRaWAN Gateway**
254 254  )))
255 255  
256 256  (((
... ... @@ -264,9 +264,8 @@
264 264  )))
265 265  
266 266  
267 -
268 268  (((
269 -(% style="color:blue" %)**For End Node**
248 +**For End Node**
270 270  )))
271 271  
272 272  (((
... ... @@ -274,19 +274,23 @@
274 274  )))
275 275  
276 276  (((
277 -(% style="color:#037691" %)**AT+RX2FQ=869525000**  (%%) **~-~-->**  The RX2 Window frequency
278 -(% style="color:#037691" %)**AT+RX2DR=3**          (%%) **~-~-->**  The RX2 DataRate
279 -(% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
280 -(% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
281 -
282 -
283 283  
284 284  )))
285 285  
286 286  (((
287 -(% style="color:blue" %)**when the device running, we can see below info:**
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
288 288  )))
267 +)))
289 289  
269 +(((
270 +**when the device running, we can see below info:**
271 +)))
272 +
290 290  {{{ [12502]***** UpLinkCounter= 0 *****
291 291   [12503]TX on freq 868500000 Hz at DR 0
292 292   [13992]txDone
... ... @@ -297,12 +297,10 @@
297 297  
298 298  (((
299 299  
300 -
301 -
302 302  )))
303 303  
304 304  (((
305 -(% style="color:blue" %)**Another message:**
286 +**Another message:**
306 306  )))
307 307  
308 308  {{{ [12502]***** UpLinkCounter= 0 *****
... ... @@ -317,10 +317,8 @@
317 317   1:0012345678}}}
318 318  
319 319  
301 +== 5.3 If problem doesn’t solve ==
320 320  
321 -== 5.3 If problem doesn't solve ==
322 -
323 -
324 324  (% 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:**
325 325  
326 326  * End node console to show the transmit freuqency and DR.
... ... @@ -328,12 +328,8 @@
328 328  * Gateway traffic (from server UI) to shows the data exchange between gateway and server.
329 329  * End Node traffic (from server UI) to shows end node activity in server.
330 330  
331 -
332 -
333 -
334 334  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
335 335  
336 -
337 337  (((
338 338  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.
339 339  )))
... ... @@ -357,34 +357,37 @@
357 357  )))
358 358  
359 359  
360 -
361 361  = 7. Decrypt a LoRaWAN Packet =
362 362  
337 +~1. LHT65 End device configure:
363 363  
364 -(% style="color:blue" %)**1. LHT65 End device configure:**
339 +(% class="box infomessage" %)
340 +(((
341 +Change to ABP Mode: AT+NJM=0
342 +)))
365 365  
366 -**Change to ABP Mode:  AT+NJM=0**
367 -**Change to fix frequency:  AT+CHS=904900000**
368 -**Change to fix DR:  AT+DR=0**
344 +(% class="box infomessage" %)
345 +(((
346 +Change to fix frequency: AT+CHS=904900000
347 +)))
369 369  
349 +(% class="box infomessage" %)
350 +(((
351 +Change to fix DR: AT+DR=0
352 +)))
370 370  
371 -[[image:image-20220526165525-16.png]]
354 +[[image:https://wiki.dragino.com/images/e/e6/Decrypt_a_LoRaWAN_Packet1.jpg||alt="Decrypt a LoRaWAN Packet1.jpg" height="607" width="558"]]
372 372  
356 +2. In LG02 , configure to receive above message
373 373  
358 +[[image:https://wiki.dragino.com/images/c/c3/Decrypt_a_LoRaWAN_Packet2.jpg||alt="Decrypt a LoRaWAN Packet2.jpg" height="337" width="558"]]
374 374  
375 -(% style="color:blue" %)**2. In LG02 , configure to receive above message**
376 -
377 -[[image:image-20220526165612-17.png]]
378 -
379 -
380 380  In LG02 console, we can see the hex receive are:
381 381  
382 -[[image:image-20220526171112-21.png]]
362 +[[image:https://wiki.dragino.com/images/f/f1/Decrypt_a_LoRaWAN_Packet3.jpg||alt="Decrypt a LoRaWAN Packet3.jpg" height="179" width="558"]]
383 383  
364 +3. Decode the info in web
384 384  
385 -
386 -(% style="color:blue" %)**3. Decode the info in web**
387 -
388 388  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
389 389  
390 390  Need these three fields:
... ... @@ -395,10 +395,9 @@
395 395  
396 396  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
397 397  
398 -
399 399  [[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]]
400 400  
401 -[[image:image-20220526171029-20.png]]
378 +[[image:https://wiki.dragino.com/images/7/77/Decrypt_a_LoRaWAN_Packet4.png||alt="Decrypt a LoRaWAN Packet4.png" height="390" width="558"]]
402 402  
403 403  (((
404 404   The FRMPayload is the device payload.
... ... @@ -405,19 +405,14 @@
405 405  )))
406 406  
407 407  
408 -
409 409  = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
410 410  
411 -
412 412  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.
413 413  
414 -
415 -
416 416  = 9. Why do I see a "MIC Mismatch" error message from the server? =
417 417  
418 -
419 419  (((
420 -1)  If the user receives a "MIC Mismatch" message after registering the node on the server.
392 +1)If the user receives a "MIC Mismatch" message after registering the node on the server.
421 421  )))
422 422  
423 423  (((
... ... @@ -439,14 +439,11 @@
439 439  * (((
440 440  If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
441 441  
442 -
443 -
444 444  
445 445  )))
446 446  
447 447  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
448 448  
449 -
450 450  * If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
451 451  
452 452  (((
... ... @@ -464,79 +464,36 @@
464 464  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]]
465 465  
466 466  
467 -
468 468  
469 469  )))
470 470  
471 471  = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
472 472  
473 -
474 -(((
475 475  It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
476 -)))
477 477  
478 -(((
479 479  AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
480 -)))
481 481  
482 -(((
483 483  AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
484 -)))
485 485  
486 -(((
487 487  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
488 -)))
489 489  
490 -(((
491 491  AT+APPEUI=00 00 00 00 00 00 00 00
492 -)))
493 493  
494 -(((
495 -
496 -)))
497 497  
498 -(((
499 499  You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number.
500 -)))
501 501  
502 -(((
503 503  You can rewrites the keys by running commands in AT Console
504 504  
505 -
506 -)))
456 +For example：
507 507  
508 -(((
509 -**For example：**
510 -)))
511 -
512 -(((
513 513  AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
514 -)))
515 515  
516 -(((
517 517  AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
518 -)))
519 519  
520 -(((
521 521  AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
522 -)))
523 523  
524 -(((
525 525  AT+APPEUI=2C 45 47 E3 24 12 23 24
526 -)))
527 527  
528 -(((
529 529  (Any combination of 16 bit codes can be used）
530 530  
531 531  
532 -
533 -= 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
534 -)))
535 -
536 -
537 -Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
538 -
539 -
540 -
541 -(% class="wikigeneratedid" %)
542 -
image-20220526171112-21.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -183.8 KB
Content
image-20220531161828-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -98.6 KB
Content

Applications

Navigation

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