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 < 54.1 >
edited by Mengting Qiu
on 2024/01/29 14:21
>
Change comment: Uploaded new attachment "image-20240129142147-2.png", version {1}

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 += 1. Join process page check =
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,25 +11,30 @@
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 -[[image:image-20220526164956-15.png||height="591" width="1153"]]
29 +[[image:image-20240123182345-1.png||height="605" width="946"]]
25 25  
26 -Console Output from End device to see the transmit frequency
31 +Console Output from End device to see the transmit frequency.
27 27  
28 28  
29 -
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)
37 +
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]]
... ... @@ -37,31 +37,31 @@
37 37  Console Output from Gateway to see packets between end node and server.
38 38  
39 39  
45 +(% style="color:blue" %)**3. Gateway Live data in LoRaWAN Server**
40 40  
41 -(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
47 +* Does the gateway real-time data contain information about Join Request? If not, check the internet connection and gateway LoRaWAN server Settings.
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 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.
50 +
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
55 +The Traffic for the End node in the server, use TTN as example.
50 50  
51 51  
52 -
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.
56 56  
57 -[[image:image-20220526163704-4.png]]
62 +[[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]]
67 +[[image:image-20240123150943-2.png||height="556" width="1179"]]
63 63  
64 -Check if OTAA Keys match the keys in device
69 +Check if OTAA Keys match the keys in device.
65 65  
66 66  
67 67  = 2. Notice of US915/CN470/AU915 Frequency band =
... ... @@ -68,17 +68,17 @@
68 68  
69 69  
70 70  (((
71 -If user has problem to work with lorawan server in band US915/AU915/CN470, he can check:
76 +If user has problem to work with LoRaWAN server in band US915/AU915/CN470, he can check:
72 72  )))
73 73  
74 74  * (((
75 -What **sub-band** the server support ?
80 +What **sub-band** the server support?
76 76  )))
77 77  * (((
78 -What is the **sub-band** the gateway support ?
83 +What is the **sub-band** the gateway support?
79 79  )))
80 80  * (((
81 -What is the **sub-band** the end node is using ?
86 +What is the **sub-band** the end node is using?
82 82  )))
83 83  
84 84  (((
... ... @@ -90,7 +90,7 @@
90 90  )))
91 91  
92 92  (((
93 -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.
98 +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.
94 94  )))
95 95  
96 96  (((
... ... @@ -98,7 +98,7 @@
98 98  )))
99 99  
100 100  (((
101 -Here are the freuqency tables for these bands as reference:
106 +Here are the frequency tables for these bands as reference:
102 102  )))
103 103  
104 104  [[image:image-20220526163801-6.png]]
... ... @@ -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]]
131 +[[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 =
145 += 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.
179 +
180 +[[image:image-20240123161737-4.png||height="395" width="763"]]
174 174  )))
175 175  
176 -[[image:image-20220526164508-10.png]]
183 +[[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,
196 +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]]
... ... @@ -207,7 +207,6 @@
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  
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
229 +Configure a downlink to the end device
224 224  )))
225 225  
226 -[[image:image-20220526164623-12.png]]
232 +[[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
276 +* (% style="color:#037691" %)**AT+RX2FQ=869525000**  (%%) **~-~-->**  The RX2 Window frequency
274 274  
278 +* (% style="color:#037691" %)**AT+RX2DR=3**          (%%) **~-~-->**  The RX2 DataRate
275 275  
276 -
280 +* (% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
281 +
282 +* (% 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.
325 +
319 319  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server.
327 +
320 320  * Gateway traffic (from server UI) to shows the data exchange between gateway and server.
329 +
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**
364 +
357 357  **Change to fix frequency:  AT+CHS=904900000**
366 +
358 358  **Change to fix DR:  AT+DR=0**
359 359  
360 360  
... ... @@ -395,7 +395,7 @@
395 395  )))
396 396  
397 397  
398 -= 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
407 += 8. Why I see uplink 0x00 periodically on the LHT65 v1.8 firmware =
399 399  
400 400  
401 401  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.
... ... @@ -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.
438 +)))
429 429  
440 +(% class="wikigeneratedid" %)
441 +3）Wrong Regional Parameters version selected
442 + We generally use versions above 1.0.2
430 430  
431 -
432 -)))
444 +(% class="wikigeneratedid" %)
445 +[[image:image-20230322163227-1.png]]
433 433  
447 +(% class="wikigeneratedid" %)
448 +4）We have had cases where it was automatically fixed the next day despite no manual changes, probably a server side issue
449 +
450 +
434 434  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
435 435  
436 436  
437 -**Why this happen:**
454 +(% style="color:blue" %)**Why sensor sends 0x00?**
438 438  
439 -For US915, AU915 or AS923 frequencies.It is possible because: .
456 +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.
458 +**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.
460 +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:**
463 +**Possible Case 2:**
447 447  
448 -Solution: Use the decoder to filter out this 0x00 packet.
465 +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  
467 +
468 +(% style="color:blue" %)**How to solve:**
469 +
470 +Solution:
471 +
472 +~1. Use the decoder to filter out this 0x00 packet. (**Recommand**)
473 +
474 +2. Data rate changed from DR3 to DR5, increasing upload byte length
475 +AT+ADR=0
476 +AT+DR=3
477 +
478 +Downlink：
479 +
480 +[[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]]
481 +
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  
... ... @@ -521,24 +521,24 @@
521 521  = 13. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
522 522  
523 523  
524 -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.
556 +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.
525 525  
526 526  
527 -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:
559 +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:
528 528  
529 -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:
561 +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:
530 530  
531 531  * (((
532 -Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
564 +Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band.
533 533  )))
534 534  * (((
535 -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)
567 +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).
536 536  )))
537 537  
538 -This change will make the activation time a littler longer but make sure the device can be used in any subband.
570 +This change will make the activation time a little longer but make sure the device can be used in any sub-band.
539 539  
540 540  
541 -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.
573 +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.
542 542  
543 543  
544 544  [[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
image-20240123182345-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +108.0 KB
Content
image-20240129142110-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +126.9 KB
Content
image-20240129142147-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +116.1 KB
Content

Applications

Navigation

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