Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 39.2 >
edited by Xiaoling
on 2023/03/23 17:08
To version < 32.12 >
edited by Xiaoling
on 2022/07/13 15:20
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -4,7 +4,7 @@
4 4  
5 5  
6 6  
7 -= 1.(% style="display:none" %) (%%) OTAA Join Process Debug =
7 += 1. OTAA Join Process Debug =
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,31 +11,24 @@
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 -
15 15  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server. (If possible)
16 -
17 17  * Gateway traffic (from server UI) to shows the data exchange between gateway and server. (Normaly possible)
18 -
19 19  * End Node traffic (from server UI) to shows end node activity in server. (Normaly possible)
20 -
21 21  * 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)
22 22  
23 -(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
19 +**~1. End Device Join Screen shot, we can check:**
24 24  
25 25  * If the device is sending join request to server?
26 -
27 27  * What frequency the device is sending?
28 28  
29 -[[image:image-20220526164956-15.png||height="591" width="1153"]]
24 +[[image:image-20220526164956-15.png]]
30 30  
31 31  Console Output from End device to see the transmit frequency
32 32  
33 33  
29 +**2. Gateway packet traffic in gateway web or ssh. we can check:**
34 34  
35 -(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
36 -
37 37  * 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 -
39 39  * If the gateway gets the Join Accept message from server and transmit it via LoRa?
40 40  
41 41  [[image:image-20220526163608-2.png]]
... ... @@ -43,13 +43,10 @@
43 43  Console Output from Gateway to see packets between end node and server.
44 44  
45 45  
39 +**3. Gateway Traffic Page in LoRaWAN Server**
46 46  
47 -(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
48 -
49 49  * If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
50 -
51 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.
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]]
... ... @@ -57,9 +57,8 @@
57 57  The Traffic for the End node in the server, use TTN as example
58 58  
59 59  
50 +**4. Data Page in LoRaWAN server**
60 60  
61 -(% style="color:blue" %)**4. Data Page in LoRaWAN server**
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 65  [[image:image-20220526163704-4.png]]
... ... @@ -66,7 +66,6 @@
66 66  
67 67  The data for the end device set in server
68 68  
69 -
70 70  [[image:image-20220526163732-5.png]]
71 71  
72 72  Check if OTAA Keys match the keys in device
... ... @@ -113,7 +113,6 @@
113 113  
114 114  US915 Channels
115 115  
116 -
117 117  [[image:image-20220526163926-7.png]]
118 118  
119 119  AU915 Channels
... ... @@ -136,7 +136,7 @@
136 136  (((
137 137  TTN FREQUENCY PLAN
138 138  
139 -(% style="display:none" %) (%%)
126 +
140 140  )))
141 141  
142 142  (((
... ... @@ -143,7 +143,6 @@
143 143  In dragino end node, user can use AT+CHE command to set what frequencies set the end node will use. The default settings for Dragino end node are preconfigure for TTN server, so use 8~~15 channels, which is **AT+CHE=2**. (AT+CHE=1 for first 8 channels, AT+CHE=2 for second 8 channels.. etc, and AT+CHE=0 for all 72 channels. )
144 144  )))
145 145  
146 -(% style="display:none" %) (%%)
147 147  
148 148  = 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
149 149  
... ... @@ -150,16 +150,17 @@
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:
152 152  
153 -* (% style="color:blue" %)**End node** (%%) ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Sensor. ADR is also enable, this is the default settings for dragino sensors.
139 +* **End node** ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Sensor. ADR is also enable, this is the default settings for dragino sensors.
140 +* **Gateway** ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Gateway. this is the default settings for dragino sensors.
141 +* **LoRaWAN server** ~-~-> ChirpStack default installation and use Sub-band1, **enabled_uplink_channels=[0, 1, 2, 3, 4, 5, 6, 7]** in the file chirpstack-network-server.toml.
154 154  
155 -* (% style="color:blue" %)**Gateway** (%%) ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Gateway. this is the default settings for dragino sensors.
156 -
157 -* (% style="color:blue" %)**LoRaWAN server**  (%%) ~-~-> ChirpStack default installation and use Sub-band1, **enabled_uplink_channels=[0, 1, 2, 3, 4, 5, 6, 7]** in the file chirpstack-network-server.toml.
158 -
159 159  (((
160 160  When Sensor power on, it will use sub-band2 to join the network, the frequency matches the settings in gateway so all Join Request will be passed to the server for Join. Server will ask the sensor to change to Sub-band1 in the Join Accept downlink message. Sensor will change to sub-band1 for data upload. This cause the sensor and gateway have different frequencies so user see lost of most data or even no data.
161 161  )))
162 162  
147 +(((
148 +
149 +)))
163 163  
164 164  (((
165 165  Use Subband2 as a default subband cause the sensor to have problem to work with the LoRaWAN server which use other subband, and use need to access to the end node to change the subband by console. that is not user frendily,. So since Dragino LoRaWAN Stack version DLS-005(release on end of 2020), we have changed the device to use All Subbands for OTAA join, for example, device will use the first frequency in Sub-Band1 as firt OTAA join packet, then use the first frequency in Sub-Band 2 , then first frequency in sub-band 3, and so on. LoRaWAN server will normally provide the required subband in the OTAA accept process, so end node will know what subband it use after join. If LoRaWAN server doesn't provide subband info in OTAA join, end node will use the subband which join success as the working subband. So the new method cause a longer OTAA Join time but will be compatible with all LoRaWAN server. And new method won't affect the normal uplink after Join Success.
... ... @@ -174,10 +174,18 @@
174 174  )))
175 175  
176 176  (((
164 +
165 +)))
166 +
167 +(((
177 177  So in ABP mode, first check if the packet already arrive your gateway, if the packet arrive gatewat but didn't arrive server. Please check if this is the issue.
178 178  )))
179 179  
180 180  (((
172 +
173 +)))
174 +
175 +(((
181 181  To solve this, disable the Frame Counter Check will solve this issue , or reset the frame counter in the device page.
182 182  )))
183 183  
... ... @@ -205,17 +205,11 @@
205 205  Below are the requirement for the End Device to receive the packets.
206 206  
207 207  * The End Device must open the receive windows: RX1 or RX2
208 -
209 209  * The LoRaWAN server must send a downstream packet, and the gateway forward this downstream packet for this end node.
210 -
211 211  * This downstream packet must arrive to the end node while RX1 or RX2 is open.
212 -
213 213  * This packet must match the frequency of the RX1 or RX2 window.
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  
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  )))
... ... @@ -275,13 +275,12 @@
275 275  )))
276 276  
277 277  (((
278 -* (% style="color:#037691" %)**AT+RX2FQ=869525000**  (%%) **~-~-->**  The RX2 Window frequency
265 +(% style="color:#037691" %)**AT+RX2FQ=869525000**  (%%) **~-~-->**  The RX2 Window frequency
266 +(% style="color:#037691" %)**AT+RX2DR=3**          (%%) **~-~-->**  The RX2 DataRate
267 +(% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
268 +(% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
279 279  
280 -* (% style="color:#037691" %)**AT+RX2DR=3**          (%%) **~-~-->**  The RX2 DataRate
281 -
282 -* (% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
283 -
284 -* (% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
270 +
285 285  )))
286 286  
287 287  (((
... ... @@ -298,8 +298,6 @@
298 298  
299 299  (((
300 300  
301 -
302 -
303 303  )))
304 304  
305 305  (((
... ... @@ -324,15 +324,13 @@
324 324  (% 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:**
325 325  
326 326  * End node console to show the transmit freuqency and DR.
327 -
328 328  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server.
329 -
330 330  * Gateway traffic (from server UI) to shows the data exchange between gateway and server.
331 -
332 332  * End Node traffic (from server UI) to shows end node activity in server.
333 333  
334 334  
335 335  
317 +
336 336  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
337 337  
338 338  
... ... @@ -365,9 +365,7 @@
365 365  (% style="color:blue" %)**1. LHT65 End device configure:**
366 366  
367 367  **Change to ABP Mode:  AT+NJM=0**
368 -
369 369  **Change to fix frequency:  AT+CHS=904900000**
370 -
371 371  **Change to fix DR:  AT+DR=0**
372 372  
373 373  
... ... @@ -374,7 +374,6 @@
374 374  [[image:image-20220526165525-16.png]]
375 375  
376 376  
377 -
378 378  (% style="color:blue" %)**2. In LG02 , configure to receive above message**
379 379  
380 380  [[image:image-20220526165612-17.png]]
... ... @@ -385,7 +385,6 @@
385 385  [[image:image-20220526171112-21.png]]
386 386  
387 387  
388 -
389 389  (% style="color:blue" %)**3. Decode the info in web**
390 390  
391 391  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
... ... @@ -439,38 +439,36 @@
439 439  
440 440  * (((
441 441  If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
442 -)))
443 443  
444 -(% class="wikigeneratedid" %)
445 -3）Wrong Regional Parameters version selected
446 - We generally use versions above 1.0.2
447 447  
448 -(% class="wikigeneratedid" %)
449 -[[image:image-20230322163227-1.png]]
450 450  
451 -(% class="wikigeneratedid" %)
452 -4）We have had cases where it was automatically fixed the next day despite no manual changes, probably a server side issue
423 +
424 +)))
453 453  
454 -
455 455  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
456 456  
457 457  
458 -(% style="color:blue" %)**Why this happen:**
429 +* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
459 459  
460 -For US915, AU915 or AS923 frequencies.It is possible because: .
431 +(((
432 +When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
433 +)))
461 461  
462 -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.
435 +(((
436 +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.
437 +)))
463 463  
464 -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 +Solution: Use the decoder to filter out this 00 packet.
441 +)))
442 +* (((
443 +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]]
465 465  
466 466  
467 -(% style="color:blue" %)**How to solve:**
468 468  
469 -Solution: Use the decoder to filter out this 0x00 packet.
447 +
448 +)))
470 470  
471 -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]]
472 -
473 -
474 474  = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
475 475  
476 476  
... ... @@ -539,30 +539,6 @@
539 539  Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
540 540  
541 541  
542 -= 13. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
543 543  
544 -
545 -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.
546 -
547 -
548 -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:
549 -
550 -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:
551 -
552 -* (((
553 -Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
554 -)))
555 -* (((
556 -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)
557 -)))
558 -
559 -This change will make the activation time a littler longer but make sure the device can be used in any subband.
560 -
561 -
562 -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.
563 -
564 -
565 -[[image:image-20221215223215-1.png||height="584" width="1280"]]
566 -
567 567  (% class="wikigeneratedid" %)
568 568  
image-20221215223215-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -183.6 KB
Content
image-20230322163227-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -43.1 KB
Content

Applications

Navigation

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