Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 37.2 >
edited by Xiaoling
on 2022/12/16 10:46
To version < 49.1 >
edited by Mengting Qiu
on 2024/01/23 16:37
>
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,7 +4,7 @@
4 4  
5 5  
6 6  
7 -= 1.(% style="display:none" %) (%%) OTAA Join Process Debug =
7 += z =
8 8  
9 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,14 +11,19 @@
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  
13 13  * End node console to show the Join freuqency and DR. (If possible)
14 +
14 14  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server. (If possible)
16 +
15 15  * Gateway traffic (from server UI) to shows the data exchange between gateway and server. (Normaly possible)
18 +
16 16  * End Node traffic (from server UI) to shows end node activity in server. (Normaly possible)
20 +
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  (% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
20 20  
21 21  * If the device is sending join request to server?
26 +
22 22  * What frequency the device is sending?
23 23  
24 24  [[image:image-20220526164956-15.png||height="591" width="1153"]]
... ... @@ -30,6 +30,7 @@
30 30  (% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
31 31  
32 32  * If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
38 +
33 33  * If the gateway gets the Join Accept message from server and transmit it via LoRa?
34 34  
35 35  [[image:image-20220526163608-2.png]]
... ... @@ -38,15 +38,17 @@
38 38  
39 39  
40 40  
41 -(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
47 +(% style="color:blue" %)**3. Gateway Live data in LoRaWAN Server**
42 42  
43 -* If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
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 +* Does the gateway real-time data contain information about Join Request? If not, check the internet connection and gateway LoRaWAN server Settings.
50 +
51 +* 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 +
45 45  * 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.
46 46  
47 47  [[image:image-20220526163633-3.png]]
48 48  
49 -The Traffic for the End node in the server, use TTN as example
57 +The Traffic for the End node in the server, use TTN as example.
50 50  
51 51  
52 52  
... ... @@ -54,14 +54,14 @@
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  
57 -[[image:image-20220526163704-4.png]]
65 +[[image:image-20240123150720-1.png||height="459" width="1182"]]
58 58  
59 59  The data for the end device set in server
60 60  
61 61  
62 -[[image:image-20220526163732-5.png]]
70 +[[image:image-20240123150943-2.png||height="556" width="1179"]]
63 63  
64 -Check if OTAA Keys match the keys in device
72 +Check if OTAA Keys match the keys in device.
65 65  
66 66  
67 67  = 2. Notice of US915/CN470/AU915 Frequency band =
... ... @@ -123,7 +123,7 @@
123 123  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.
124 124  )))
125 125  
126 -[[image:image-20220526164052-9.png]]
134 +[[image:image-20240123151225-3.png||height="434" width="902"]]
127 127  
128 128  (((
129 129  TTN FREQUENCY PLAN
... ... @@ -137,7 +137,7 @@
137 137  
138 138  (% style="display:none" %) (%%)
139 139  
140 -= 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
148 += 3. Why I see data lost/ is not periodically uplink？ Even the signal strength is good =
141 141  
142 142  
143 143  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:
... ... @@ -171,9 +171,11 @@
171 171  
172 172  (((
173 173  To solve this, disable the Frame Counter Check will solve this issue , or reset the frame counter in the device page.
182 +
183 +[[image:image-20240123161737-4.png||height="395" width="763"]]
174 174  )))
175 175  
176 -[[image:image-20220526164508-10.png]]
186 +[[image:image-20240123161853-6.png||height="599" width="771"]]
177 177  
178 178  Disable Frame Counter Check in ABP Mode
179 179  
... ... @@ -186,7 +186,7 @@
186 186  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.
187 187  
188 188  (((
189 -Depends on Class A or Class C, the receive windows will be a little difference,
199 +Depends on Class A or Class C, the receive windows will be a little difference.
190 190  )))
191 191  
192 192  [[image:image-20220531161828-1.png]]
... ... @@ -206,8 +206,9 @@
206 206  
207 207  * 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.**
208 208  
219 +(% class="wikigeneratedid" %)
220 +== ==
209 209  
210 -
211 211  == 5.2 See Debug Info ==
212 212  
213 213  
... ... @@ -220,10 +220,10 @@
220 220  )))
221 221  
222 222  (((
223 -Configure a downstream to the end device
234 +Configure a downlink to the end device
224 224  )))
225 225  
226 -[[image:image-20220526164623-12.png]]
237 +[[image:image-20240123163307-7.png||height="330" width="1125"]]
227 227  
228 228  (((
229 229  Set a downstream in TTN and see it is sent
... ... @@ -267,13 +267,13 @@
267 267  )))
268 268  
269 269  (((
270 -(% style="color:#037691" %)**AT+RX2FQ=869525000**  (%%) **~-~-->**  The RX2 Window frequency
271 -(% style="color:#037691" %)**AT+RX2DR=3**          (%%) **~-~-->**  The RX2 DataRate
272 -(% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
273 -(% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
281 +* (% style="color:#037691" %)**AT+RX2FQ=869525000**  (%%) **~-~-->**  The RX2 Window frequency
274 274  
283 +* (% style="color:#037691" %)**AT+RX2DR=3**          (%%) **~-~-->**  The RX2 DataRate
275 275  
276 -
285 +* (% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
286 +
287 +* (% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
277 277  )))
278 278  
279 279  (((
... ... @@ -316,12 +316,13 @@
316 316  (% 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:**
317 317  
318 318  * End node console to show the transmit freuqency and DR.
330 +
319 319  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server.
332 +
320 320  * Gateway traffic (from server UI) to shows the data exchange between gateway and server.
334 +
321 321  * End Node traffic (from server UI) to shows end node activity in server.
322 322  
323 -
324 -
325 325  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
326 326  
327 327  
... ... @@ -354,7 +354,9 @@
354 354  (% style="color:blue" %)**1. LHT65 End device configure:**
355 355  
356 356  **Change to ABP Mode:  AT+NJM=0**
369 +
357 357  **Change to fix frequency:  AT+CHS=904900000**
371 +
358 358  **Change to fix DR:  AT+DR=0**
359 359  
360 360  
... ... @@ -426,27 +426,50 @@
426 426  
427 427  * (((
428 428  If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
443 +)))
429 429  
445 +(% class="wikigeneratedid" %)
446 +3）Wrong Regional Parameters version selected
447 + We generally use versions above 1.0.2
430 430  
431 -
432 -)))
449 +(% class="wikigeneratedid" %)
450 +[[image:image-20230322163227-1.png]]
433 433  
452 +(% class="wikigeneratedid" %)
453 +4）We have had cases where it was automatically fixed the next day despite no manual changes, probably a server side issue
454 +
455 +
434 434  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
435 435  
436 436  
437 -**Why this happen:**
459 +(% style="color:blue" %)**Why sensor sends 0x00?**
438 438  
439 -For US915, AU915 or AS923 frequencies.It is possible because: .
461 +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.
440 440  
441 -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.
463 +**Possible Case 1**:
442 442  
443 -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 +Sensor has ADR=1 enable and sensor need to reply server MAC command (ADR request) while sensor has DR=0.
444 444  
445 445  
446 -**How to solve:**
468 +**Possible Case 2:**
447 447  
448 -Solution: Use the decoder to filter out this 0x00 packet.
470 +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.
449 449  
472 +
473 +(% style="color:blue" %)**How to solve:**
474 +
475 +Solution:
476 +
477 +~1. Use the decoder to filter out this 0x00 packet. (**Recommand**)
478 +
479 +2. Data rate changed from DR3 to DR5, increasing upload byte length
480 +AT+ADR=0
481 +AT+DR=3
482 +
483 +Downlink：
484 +
485 +[[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]]
486 +
450 450  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]]
451 451  
452 452  
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