Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 32.8 >
edited by Xiaoling
on 2022/07/13 15:10
To version < 42.1 >
edited by Mengting Qiu
on 2024/01/23 15:07
>
Change comment: Uploaded new attachment "image-20240123150720-1.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. OTAA Join Process Debug =
7 += 1.(% style="display:none" %) (%%) 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,24 +11,31 @@
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 -**~1. End Device Join Screen shot, we can check:**
23 +(% 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]]
29 +[[image:image-20220526164956-15.png||height="591" width="1153"]]
25 25  
26 26  Console Output from End device to see the transmit frequency
27 27  
28 28  
29 -**2. Gateway packet traffic in gateway web or ssh. we can check:**
30 30  
35 +(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
36 +
31 31  * 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 +
32 32  * If the gateway gets the Join Accept message from server and transmit it via LoRa?
33 33  
34 34  [[image:image-20220526163608-2.png]]
... ... @@ -36,10 +36,13 @@
36 36  Console Output from Gateway to see packets between end node and server.
37 37  
38 38  
39 -**3. Gateway Traffic Page in LoRaWAN Server**
40 40  
47 +(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
48 +
41 41  * If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
50 +
42 42  * 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 +
43 43  * 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.
44 44  
45 45  [[image:image-20220526163633-3.png]]
... ... @@ -47,8 +47,9 @@
47 47  The Traffic for the End node in the server, use TTN as example
48 48  
49 49  
50 -**4. Data Page in LoRaWAN server**
51 51  
61 +(% style="color:blue" %)**4. Data Page in LoRaWAN server**
62 +
52 52  * 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.
53 53  
54 54  [[image:image-20220526163704-4.png]]
... ... @@ -55,6 +55,7 @@
55 55  
56 56  The data for the end device set in server
57 57  
69 +
58 58  [[image:image-20220526163732-5.png]]
59 59  
60 60  Check if OTAA Keys match the keys in device
... ... @@ -101,6 +101,7 @@
101 101  
102 102  US915 Channels
103 103  
116 +
104 104  [[image:image-20220526163926-7.png]]
105 105  
106 106  AU915 Channels
... ... @@ -123,7 +123,7 @@
123 123  (((
124 124  TTN FREQUENCY PLAN
125 125  
126 -
139 +(% style="display:none" %) (%%)
127 127  )))
128 128  
129 129  (((
... ... @@ -130,6 +130,7 @@
130 130  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. )
131 131  )))
132 132  
146 +(% style="display:none" %) (%%)
133 133  
134 134  = 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
135 135  
... ... @@ -136,17 +136,16 @@
136 136  
137 137  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:
138 138  
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.
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.
142 142  
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 +
143 143  (((
144 144  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.
145 145  )))
146 146  
147 -(((
148 -
149 -)))
150 150  
151 151  (((
152 152  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.
... ... @@ -161,18 +161,10 @@
161 161  )))
162 162  
163 163  (((
164 -
165 -)))
166 -
167 -(((
168 168  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.
169 169  )))
170 170  
171 171  (((
172 -
173 -)))
174 -
175 -(((
176 176  To solve this, disable the Frame Counter Check will solve this issue , or reset the frame counter in the device page.
177 177  )))
178 178  
... ... @@ -200,9 +200,13 @@
200 200  Below are the requirement for the End Device to receive the packets.
201 201  
202 202  * The End Device must open the receive windows: RX1 or RX2
208 +
203 203  * The LoRaWAN server must send a downstream packet, and the gateway forward this downstream packet for this end node.
210 +
204 204  * This downstream packet must arrive to the end node while RX1 or RX2 is open.
212 +
205 205  * This packet must match the frequency of the RX1 or RX2 window.
214 +
206 206  * 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.**
207 207  
208 208  == 5.2 See Debug Info ==
... ... @@ -238,6 +238,7 @@
238 238  )))
239 239  
240 240  
250 +
241 241  (((
242 242  (% style="color:blue" %)**For LoRaWAN Gateway**
243 243  )))
... ... @@ -253,6 +253,7 @@
253 253  )))
254 254  
255 255  
266 +
256 256  (((
257 257  (% style="color:blue" %)**For End Node**
258 258  )))
... ... @@ -262,12 +262,13 @@
262 262  )))
263 263  
264 264  (((
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
276 +* (% style="color:#037691" %)**AT+RX2FQ=869525000**  (%%) **~-~-->**  The RX2 Window frequency
269 269  
270 -
278 +* (% style="color:#037691" %)**AT+RX2DR=3**          (%%) **~-~-->**  The RX2 DataRate
279 +
280 +* (% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
281 +
282 +* (% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
271 271  )))
272 272  
273 273  (((
... ... @@ -284,6 +284,8 @@
284 284  
285 285  (((
286 286  
299 +
300 +
287 287  )))
288 288  
289 289  (((
... ... @@ -308,12 +308,13 @@
308 308  (% 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:**
309 309  
310 310  * End node console to show the transmit freuqency and DR.
325 +
311 311  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server.
327 +
312 312  * Gateway traffic (from server UI) to shows the data exchange between gateway and server.
329 +
313 313  * End Node traffic (from server UI) to shows end node activity in server.
314 314  
315 -
316 -
317 317  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
318 318  
319 319  
... ... @@ -346,12 +346,16 @@
346 346  (% style="color:blue" %)**1. LHT65 End device configure:**
347 347  
348 348  **Change to ABP Mode:  AT+NJM=0**
364 +
349 349  **Change to fix frequency:  AT+CHS=904900000**
366 +
350 350  **Change to fix DR:  AT+DR=0**
351 351  
369 +
352 352  [[image:image-20220526165525-16.png]]
353 353  
354 354  
373 +
355 355  (% style="color:blue" %)**2. In LG02 , configure to receive above message**
356 356  
357 357  [[image:image-20220526165612-17.png]]
... ... @@ -362,6 +362,7 @@
362 362  [[image:image-20220526171112-21.png]]
363 363  
364 364  
384 +
365 365  (% style="color:blue" %)**3. Decode the info in web**
366 366  
367 367  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
... ... @@ -374,6 +374,7 @@
374 374  
375 375  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
376 376  
397 +
377 377  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh/?data=40c1190126800100024926272bf18bbb6341584e27e23245&nwkskey=00000000000000000000000000000111&appskey=00000000000000000000000000000111>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/?data=40c1190126800100024926272bf18bbb6341584e27e23245&nwkskey=00000000000000000000000000000111&appskey=00000000000000000000000000000111]]
378 378  
379 379  [[image:image-20220526171029-20.png]]
... ... @@ -385,13 +385,15 @@
385 385  
386 386  = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
387 387  
409 +
388 388  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.
389 389  
390 390  
391 391  = 9. Why do I see a "MIC Mismatch" error message from the server? =
392 392  
415 +
393 393  (((
394 -1)If the user receives a "MIC Mismatch" message after registering the node on the server.
417 +1)  If the user receives a "MIC Mismatch" message after registering the node on the server.
395 395  )))
396 396  
397 397  (((
... ... @@ -412,33 +412,56 @@
412 412  
413 413  * (((
414 414  If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
415 -
416 -
417 417  )))
418 418  
440 +(% class="wikigeneratedid" %)
441 +3）Wrong Regional Parameters version selected
442 + We generally use versions above 1.0.2
443 +
444 +(% class="wikigeneratedid" %)
445 +[[image:image-20230322163227-1.png]]
446 +
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 +
419 419  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
420 420  
421 -* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
422 422  
423 -(((
424 -When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
425 -)))
454 +(% style="color:blue" %)**Why sensor sends 0x00?**
426 426  
427 -(((
428 -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.
429 -)))
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.
430 430  
431 -* (((
432 -Solution: Use the decoder to filter out this 00 packet.
433 -)))
434 -* (((
435 -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]]
458 +**Possible Case 1**:
436 436  
437 -
438 -)))
460 +Sensor has ADR=1 enable and sensor need to reply server MAC command (ADR request) while sensor has DR=0.
439 439  
462 +
463 +**Possible Case 2:**
464 +
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.
466 +
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 +
482 +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]]
483 +
484 +
440 440  = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
441 441  
487 +
442 442  (((
443 443  It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
444 444  )))
... ... @@ -469,6 +469,8 @@
469 469  
470 470  (((
471 471  You can rewrites the keys by running commands in AT Console
518 +
519 +
472 472  )))
473 473  
474 474  (((
... ... @@ -502,6 +502,30 @@
502 502  Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
503 503  
504 504  
553 += 13. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
505 505  
555 +
556 +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.
557 +
558 +
559 +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:
560 +
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 subbands. To make sure the end node will only transmit the proper sub-band after OTAA Joined successfully, the end node will:
562 +
563 +* (((
564 +Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
565 +)))
566 +* (((
567 +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)
568 +)))
569 +
570 +This change will make the activation time a littler longer but make sure the device can be used in any subband.
571 +
572 +
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 subband he use.
574 +
575 +
576 +[[image:image-20221215223215-1.png||height="584" width="1280"]]
577 +
506 506  (% class="wikigeneratedid" %)
507 507  
image-20221215223215-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +183.6 KB
Content
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

Applications

Navigation

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