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 < 37.1 >
edited by Edwin Chen
on 2022/12/15 22:33
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Edwin
Content
... ... @@ -17,7 +17,6 @@
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 19  
20 -
21 21  (% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
22 22  
23 23  * If the device is sending join request to server?
... ... @@ -39,6 +39,7 @@
39 39  Console Output from Gateway to see packets between end node and server.
40 40  
41 41  
41 +
42 42  (% style="color:blue" %)**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.
... ... @@ -50,6 +50,7 @@
50 50  The Traffic for the End node in the server, use TTN as example
51 51  
52 52  
53 +
53 53  (% style="color:blue" %)**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.
... ... @@ -58,6 +58,7 @@
58 58  
59 59  The data for the end device set in server
60 60  
62 +
61 61  [[image:image-20220526163732-5.png]]
62 62  
63 63  Check if OTAA Keys match the keys in device
... ... @@ -105,6 +105,7 @@
105 105  
106 106  US915 Channels
107 107  
110 +
108 108  [[image:image-20220526163926-7.png]]
109 109  
110 110  AU915 Channels
... ... @@ -213,8 +213,6 @@
213 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.**
214 214  
215 215  
216 -
217 -
218 218  == 5.2 See Debug Info ==
219 219  
220 220  
... ... @@ -329,8 +329,6 @@
329 329  * End Node traffic (from server UI) to shows end node activity in server.
330 330  
331 331  
332 -
333 -
334 334  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
335 335  
336 336  
... ... @@ -447,27 +447,23 @@
447 447  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
448 448  
449 449  
450 -* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
449 +**Why this happen:**
451 451  
452 -(((
453 -When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
454 -)))
451 +For US915, AU915 or AS923 frequencies.It is possible because: .
455 455  
456 -(((
457 -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.
458 -)))
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.
459 459  
460 -* (((
461 -Solution: Use the decoder to filter out this 00 packet.
462 -)))
463 -* (((
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]]
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.
465 465  
466 466  
458 +**How to solve:**
467 467  
468 -
469 -)))
460 +Solution: Use the decoder to filter out this 0x00 packet.
470 470  
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 +
471 471  = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
472 472  
473 473  
... ... @@ -537,6 +537,30 @@
537 537  Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
538 538  
539 539  
535 += 13. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
540 540  
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 +
541 541  (% class="wikigeneratedid" %)
542 542  
image-20221215223215-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +183.6 KB
Content

Applications

Navigation

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