Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 37.1 >
edited by Edwin Chen
on 2022/12/15 22:33
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
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.Xiaoling
Content
... ... @@ -16,9 +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  
19 +**~1. End Device Join Screen shot, we can check:**
19 19  
20 -(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
21 -
22 22  * If the device is sending join request to server?
23 23  * What frequency the device is sending?
24 24  
... ... @@ -27,9 +27,8 @@
27 27  Console Output from End device to see the transmit frequency
28 28  
29 29  
29 +**2. Gateway packet traffic in gateway web or ssh. we can check:**
30 30  
31 -(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
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?
35 35  
... ... @@ -38,9 +38,8 @@
38 38  Console Output from Gateway to see packets between end node and server.
39 39  
40 40  
39 +**3. Gateway Traffic Page in LoRaWAN Server**
41 41  
42 -(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
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.
46 46  * If the Join Accept message are in correct frequency? If you set the server to use US915 band, and your end node and gateway is EU868, you will see the Join Accept message are in US915 band so no possible to Join success.
... ... @@ -50,9 +50,8 @@
50 50  The Traffic for the End node in the server, use TTN as example
51 51  
52 52  
50 +**4. Data Page in LoRaWAN server**
53 53  
54 -(% style="color:blue" %)**4. Data Page in LoRaWAN server**
55 -
56 56  * 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.
57 57  
58 58  [[image:image-20220526163704-4.png]]
... ... @@ -59,13 +59,11 @@
59 59  
60 60  The data for the end device set in server
61 61  
62 -
63 63  [[image:image-20220526163732-5.png]]
64 64  
65 65  Check if OTAA Keys match the keys in device
66 66  
67 67  
68 -
69 69  = 2. Notice of US915/CN470/AU915 Frequency band =
70 70  
71 71  
... ... @@ -107,7 +107,6 @@
107 107  
108 108  US915 Channels
109 109  
110 -
111 111  [[image:image-20220526163926-7.png]]
112 112  
113 113  AU915 Channels
... ... @@ -138,7 +138,6 @@
138 138  )))
139 139  
140 140  
141 -
142 142  = 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
143 143  
144 144  
... ... @@ -161,7 +161,6 @@
161 161  )))
162 162  
163 163  
164 -
165 165  = 4. Transmision on ABP Mode =
166 166  
167 167  
... ... @@ -190,7 +190,6 @@
190 190  Disable Frame Counter Check in ABP Mode
191 191  
192 192  
193 -
194 194  = 5. Downstream Debug =
195 195  
196 196  == 5.1 How it work ==
... ... @@ -215,7 +215,6 @@
215 215  * This packet must match the frequency of the RX1 or RX2 window.
216 216  * 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.**
217 217  
218 -
219 219  == 5.2 See Debug Info ==
220 220  
221 221  
... ... @@ -249,7 +249,6 @@
249 249  )))
250 250  
251 251  
252 -
253 253  (((
254 254  (% style="color:blue" %)**For LoRaWAN Gateway**
255 255  )))
... ... @@ -265,7 +265,6 @@
265 265  )))
266 266  
267 267  
268 -
269 269  (((
270 270  (% style="color:blue" %)**For End Node**
271 271  )))
... ... @@ -280,7 +280,6 @@
280 280  (% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
281 281  (% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
282 282  
283 -
284 284  
285 285  )))
286 286  
... ... @@ -298,8 +298,6 @@
298 298  
299 299  (((
300 300  
301 -
302 -
303 303  )))
304 304  
305 305  (((
... ... @@ -318,7 +318,6 @@
318 318   1:0012345678}}}
319 319  
320 320  
321 -
322 322  == 5.3 If problem doesn't solve ==
323 323  
324 324  
... ... @@ -330,9 +330,10 @@
330 330  * End Node traffic (from server UI) to shows end node activity in server.
331 331  
332 332  
333 -= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
334 334  
335 335  
318 += 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
319 +
336 336  (((
337 337  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.
338 338  )))
... ... @@ -356,23 +356,22 @@
356 356  )))
357 357  
358 358  
359 -
360 360  = 7. Decrypt a LoRaWAN Packet =
361 361  
345 +~1. LHT65 End device configure:
362 362  
363 -(% style="color:blue" %)**1. LHT65 End device configure:**
347 +(% class="box infomessage" %)
348 +(((
349 +**Change to ABP Mode: AT+NJM=0**
350 +**Change to fix frequency: AT+CHS=904900000**
351 +**Change to fix DR: AT+DR=0**
352 +)))
364 364  
365 -**Change to ABP Mode:  AT+NJM=0**
366 -**Change to fix frequency:  AT+CHS=904900000**
367 -**Change to fix DR:  AT+DR=0**
368 -
369 -
370 370  [[image:image-20220526165525-16.png]]
371 371  
372 372  
357 +2. In LG02 , configure to receive above message
373 373  
374 -(% style="color:blue" %)**2. In LG02 , configure to receive above message**
375 -
376 376  [[image:image-20220526165612-17.png]]
377 377  
378 378  
... ... @@ -381,9 +381,8 @@
381 381  [[image:image-20220526171112-21.png]]
382 382  
383 383  
367 +3. Decode the info in web
384 384  
385 -(% style="color:blue" %)**3. Decode the info in web**
386 -
387 387  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
388 388  
389 389  Need these three fields:
... ... @@ -394,7 +394,6 @@
394 394  
395 395  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
396 396  
397 -
398 398  [[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]]
399 399  
400 400  [[image:image-20220526171029-20.png]]
... ... @@ -404,19 +404,15 @@
404 404  )))
405 405  
406 406  
407 -
408 408  = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
409 409  
410 -
411 411  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.
412 412  
413 413  
414 -
415 415  = 9. Why do I see a "MIC Mismatch" error message from the server? =
416 416  
417 -
418 418  (((
419 -1)  If the user receives a "MIC Mismatch" message after registering the node on the server.
396 +1)If the user receives a "MIC Mismatch" message after registering the node on the server.
420 420  )))
421 421  
422 422  (((
... ... @@ -438,34 +438,32 @@
438 438  * (((
439 439  If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
440 440  
441 -
442 -
443 443  
444 444  )))
445 445  
446 446  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
447 447  
423 +* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
448 448  
449 -**Why this happen:**
425 +(((
426 +When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
427 +)))
450 450  
451 -For US915, AU915 or AS923 frequencies.It is possible because: .
429 +(((
430 +When the server adjusts your node rate to 0, the maximum payload length is 11 bytes. The server sometimes sends an ADR packet to the node,and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit,so it will send a normal uplink packet, and an additional 00 data packet.
431 +)))
452 452  
453 -When using the frequency mentioned above, the server sometimes adjusts the Data Rate (DR) of the node, because the end node has Adaptive Data Rate (ADR) Enabled.
433 +* (((
434 +Solution: Use the decoder to filter out this 00 packet.
435 +)))
436 +* (((
437 +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]]
454 454  
455 -When the server adjusts end node data rate to 0, the maximum payload length is 11 bytes. The server sometimes sends an ADR packet to the end node, and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit, so it will send a normal uplink packet, and following an additional 00 data packet to handle this MAC command response.
439 +
440 +)))
456 456  
457 -
458 -**How to solve:**
459 -
460 -Solution: Use the decoder to filter out this 0x00 packet.
461 -
462 -Some node decoders may not have the filter function, or you need decoders of other servers and formats. Please send an email to [[support@dragino.com>>mailto:support@dragino.com]]
463 -
464 -
465 -
466 466  = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
467 467  
468 -
469 469  (((
470 470  It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
471 471  )))
... ... @@ -496,8 +496,6 @@
496 496  
497 497  (((
498 498  You can rewrites the keys by running commands in AT Console
499 -
500 -
501 501  )))
502 502  
503 503  (((
... ... @@ -524,7 +524,6 @@
524 524  (Any combination of 16 bit codes can be used）
525 525  
526 526  
527 -
528 528  = 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
529 529  )))
530 530  
... ... @@ -532,30 +532,6 @@
532 532  Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
533 533  
534 534  
535 -= 13. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
536 536  
537 -
538 -In US915, AU915 or CN470 frequency band, there are 8 subbands, totally 72 channels. and LoRaWAN server normally use only one sub-band, for example Subband 2 in TTN. The gateway also configured to Subband 2 and cover eight channels in this subband. If the end node transfer data in Subband 2, it will reach to gateway and to the LoRaWAN server. If the end node transfer packets in other subbands, for example subband 1, the packet won't arrive both gateway or LoRaWAN server.
539 -
540 -
541 -In Dragino Sensors old version firmware (before early 2022), the subband is fixed the subband to 2 , but this cause a problem, the end node is hard to use in other subband and need program. So the new logic is as below:
542 -
543 -We have improved this, the end node will use frequency 1 from sub-band1, then frequency 1 from sub-band2, then frequency 1 from sub-band3, etc to process the OTAA join, In this case, In this case, the end node can support LoRaWAN servers with different subbands. To make sure the end node will only transmit the proper sub-band after OTAA Joined successfully, the end node will:
544 -
545 -* (((
546 -Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
547 -)))
548 -* (((
549 -Use the Join successful sub-band if the server doesn't include subband info in the OTAA Join Accept message ( TTN v2 doesn't include)
550 -)))
551 -
552 -This change will make the activation time a littler longer but make sure the device can be used in any subband.
553 -
554 -
555 -Below is a photo to show why it takes longer time for OTAA Join. We can see in 72 channels mode, why it takes more time to join success. If users want to have faster OTAA Join success, he can change default CHE to the subband he use.
556 -
557 -
558 -[[image:image-20221215223215-1.png||height="584" width="1280"]]
559 -
560 560  (% class="wikigeneratedid" %)
561 561  
image-20221215223215-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -183.6 KB
Content

Applications

Navigation

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