Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 37.3 >
edited by Xiaoling
on 2022/12/16 11:15
To version < 50.1 >
edited by Mengting Qiu
on 2024/01/23 17:11
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.ting
Content
... ... @@ -4,9 +4,8 @@
4 4  
5 5  
6 6  
7 -= 1.(% style="display:none" %) (%%) OTAA Join Process Debug =
7 += 1.Join process page check =
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  
... ... @@ -44,17 +44,17 @@
44 44  
45 45  
46 46  
47 -(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
46 +(% style="color:blue" %)**3. Gateway Live data in LoRaWAN Server**
48 48  
49 -* If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
48 +* Does the gateway real-time data contain information about Join Request? If not, check the internet connection and gateway LoRaWAN server Settings.
50 50  
51 -* 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 +* Does the server send back a Join Accept for the Join Request? If not, check that the key from the device matches the key you put into the server, or try to choose a different server route for that end device.
52 52  
53 53  * 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.
54 54  
55 55  [[image:image-20220526163633-3.png]]
56 56  
57 -The Traffic for the End node in the server, use TTN as example
56 +The Traffic for the End node in the server, use TTN as example.
58 58  
59 59  
60 60  
... ... @@ -62,14 +62,14 @@
62 62  
63 63  * 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.
64 64  
65 -[[image:image-20220526163704-4.png]]
64 +[[image:image-20240123150720-1.png||height="459" width="1182"]]
66 66  
67 67  The data for the end device set in server
68 68  
69 69  
70 -[[image:image-20220526163732-5.png]]
69 +[[image:image-20240123150943-2.png||height="556" width="1179"]]
71 71  
72 -Check if OTAA Keys match the keys in device
71 +Check if OTAA Keys match the keys in device.
73 73  
74 74  
75 75  = 2. Notice of US915/CN470/AU915 Frequency band =
... ... @@ -76,17 +76,17 @@
76 76  
77 77  
78 78  (((
79 -If user has problem to work with lorawan server in band US915/AU915/CN470, he can check:
78 +If user has problem to work with LoRaWAN server in band US915/AU915/CN470, he can check:
80 80  )))
81 81  
82 82  * (((
83 -What **sub-band** the server support ?
82 +What **sub-band** the server support?
84 84  )))
85 85  * (((
86 -What is the **sub-band** the gateway support ?
85 +What is the **sub-band** the gateway support?
87 87  )))
88 88  * (((
89 -What is the **sub-band** the end node is using ?
88 +What is the **sub-band** the end node is using?
90 90  )))
91 91  
92 92  (((
... ... @@ -98,7 +98,7 @@
98 98  )))
99 99  
100 100  (((
101 -In LoRaWAN protocol, the frequency bands US915, AU915, CN470 each includes at least 72 frequencies. Many gateways support only 8 or 16 frequencies, and server might support 8 frequency only. In this case, the OTAA join time and uplink schedule is long and unpredictable while the end node is hopping in 72 frequencies, because the end node will send data in many frequency that the gateway or server doesn,t support.
100 +In LoRaWAN protocol, the frequency bands US915, AU915, CN470 each includes at least 72 frequencies. Many gateways support only 8 or 16 frequencies, and server might support 8 frequency only. In this case, the OTAA join time and uplink schedule is long and unpredictable while the end node is hopping in 72 frequencies, because the end node will send data in many frequency that the gateway or server doesn't support.
102 102  )))
103 103  
104 104  (((
... ... @@ -106,7 +106,7 @@
106 106  )))
107 107  
108 108  (((
109 -Here are the freuqency tables for these bands as reference:
108 +Here are the frequency tables for these bands as reference:
110 110  )))
111 111  
112 112  [[image:image-20220526163801-6.png]]
... ... @@ -131,7 +131,7 @@
131 131  If we look at the [[TTN network server frequency plan>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]], we can see the US915 frequency band use the channel 8~~15.So the End Node must work at the same frequency in US915 8~~15 channels for TTN server.
132 132  )))
133 133  
134 -[[image:image-20220526164052-9.png]]
133 +[[image:image-20240123151225-3.png||height="434" width="902"]]
135 135  
136 136  (((
137 137  TTN FREQUENCY PLAN
... ... @@ -145,7 +145,7 @@
145 145  
146 146  (% style="display:none" %) (%%)
147 147  
148 -= 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
147 += 3. Why I see data lost/ is not periodically uplink？ Even the signal strength is good =
149 149  
150 150  
151 151  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:
... ... @@ -179,9 +179,11 @@
179 179  
180 180  (((
181 181  To solve this, disable the Frame Counter Check will solve this issue , or reset the frame counter in the device page.
181 +
182 +[[image:image-20240123161737-4.png||height="395" width="763"]]
182 182  )))
183 183  
184 -[[image:image-20220526164508-10.png]]
185 +[[image:image-20240123161853-6.png||height="599" width="771"]]
185 185  
186 186  Disable Frame Counter Check in ABP Mode
187 187  
... ... @@ -194,7 +194,7 @@
194 194  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.
195 195  
196 196  (((
197 -Depends on Class A or Class C, the receive windows will be a little difference,
198 +Depends on Class A or Class C, the receive windows will be a little difference.
198 198  )))
199 199  
200 200  [[image:image-20220531161828-1.png]]
... ... @@ -214,8 +214,8 @@
214 214  
215 215  * 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.**
216 216  
218 +== ==
217 217  
218 -
219 219  == 5.2 See Debug Info ==
220 220  
221 221  
... ... @@ -228,10 +228,10 @@
228 228  )))
229 229  
230 230  (((
231 -Configure a downstream to the end device
232 +Configure a downlink to the end device
232 232  )))
233 233  
234 -[[image:image-20220526164623-12.png]]
235 +[[image:image-20240123163307-7.png||height="330" width="1125"]]
235 235  
236 236  (((
237 237  Set a downstream in TTN and see it is sent
... ... @@ -406,7 +406,7 @@
406 406  )))
407 407  
408 408  
409 -= 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
410 += 8. Why I see uplink 0x00 periodically on the LHT65 v1.8 firmware =
410 410  
411 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.
... ... @@ -437,27 +437,50 @@
437 437  
438 438  * (((
439 439  If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
441 +)))
440 440  
443 +(% class="wikigeneratedid" %)
444 +3）Wrong Regional Parameters version selected
445 + We generally use versions above 1.0.2
441 441  
442 -
443 -)))
447 +(% class="wikigeneratedid" %)
448 +[[image:image-20230322163227-1.png]]
444 444  
450 +(% class="wikigeneratedid" %)
451 +4）We have had cases where it was automatically fixed the next day despite no manual changes, probably a server side issue
452 +
453 +
445 445  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
446 446  
447 447  
448 -(% style="color:blue" %)**Why this happen:**
457 +(% style="color:blue" %)**Why sensor sends 0x00?**
449 449  
450 -For US915, AU915 or AS923 frequencies.It is possible because: .
459 +For US915, AU915 or AS923 frequencies, the max payload lenght is 11 bytes for DR0. Some times sensor needs to send MAC command to server, because the payload is 11 bytes, The MAC command + Payload will exceed 11 bytes and LoRaWAN server will ignore the uplink. In this case, Sensor will send two uplinks together: one uplink is the payload without MAC command, another uplink is **0x00 payload + MAC Command.**  For the second uplink, in the server side, it will shows the payload is 0x00. Normally, there are several case this will happen.
451 451  
452 -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.
461 +**Possible Case 1**:
453 453  
454 -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.
463 +Sensor has ADR=1 enable and sensor need to reply server MAC command (ADR request) while sensor has DR=0.
455 455  
456 456  
466 +**Possible Case 2:**
467 +
468 +For the sensor which has Datalog Feature enable, the sensor will send TimeRequest MAC Command to sync the time. This Time Request will be sent once Sensor Join Network and Every 10 days. While they send such command with DR=0, sensor will send this command with 0x00 payload.
469 +
470 +
457 457  (% style="color:blue" %)**How to solve:**
458 458  
459 -Solution: Use the decoder to filter out this 0x00 packet.
473 +Solution:
460 460  
475 +~1. Use the decoder to filter out this 0x00 packet. (**Recommand**)
476 +
477 +2. Data rate changed from DR3 to DR5, increasing upload byte length
478 +AT+ADR=0
479 +AT+DR=3
480 +
481 +Downlink：
482 +
483 +[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/#H7.4DataRate>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/#H7.4DataRate]]
484 +
461 461  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]]
462 462  
463 463  
... ... @@ -532,24 +532,24 @@
532 532  = 13. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
533 533  
534 534  
535 -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.
559 +In US915, AU915 or CN470 frequency band, there are 8 sub-bands, totally 72 channels. and LoRaWAN server normally use only one sub-band, for example Sub-band 2 in TTN. The gateway also configured to Sub-band 2 and cover eight channels in this sub-band. If the end node transfer data in Sub-band 2, it will reach to gateway and to the LoRaWAN server. If the end node transfer packets in other sub-bands, for example sub-band 1, the packet won't arrive both gateway or LoRaWAN server.
536 536  
537 537  
538 -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:
562 +In Dragino Sensors old version firmware (before early 2022), the sub-band is fixed the sub-band 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:
539 539  
540 -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:
564 +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 sub-bands. To make sure the end node will only transmit the proper sub-band after OTAA Joined successfully, the end node will:
541 541  
542 542  * (((
543 -Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
567 +Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band.
544 544  )))
545 545  * (((
546 -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)
570 +Use the Join successful sub-band if the server doesn't include sub-band info in the OTAA Join Accept message (TTN v2 doesn't include).
547 547  )))
548 548  
549 -This change will make the activation time a littler longer but make sure the device can be used in any subband.
573 +This change will make the activation time a little longer but make sure the device can be used in any sub-band.
550 550  
551 551  
552 -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.
576 +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 sub-band he uses.
553 553  
554 554  
555 555  [[image:image-20221215223215-1.png||height="584" width="1280"]]
image-20230322163227-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +43.1 KB
Content
image-20240123150720-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +119.9 KB
Content
image-20240123150943-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +161.5 KB
Content
image-20240123151225-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +136.1 KB
Content
image-20240123161737-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +83.0 KB
Content
image-20240123161806-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +71.5 KB
Content
image-20240123161853-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +60.6 KB
Content
image-20240123163307-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +123.3 KB
Content

Applications

Navigation

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