Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 32.15 >
edited by Xiaoling
on 2022/07/13 15:36
To version < 37.1 >
edited by Edwin Chen
on 2022/12/15 22:33
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Edwin
Content
... ... @@ -17,7 +17,6 @@
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  
20 -
21 21  (% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
22 22  
23 23  * If the device is sending join request to server?
... ... @@ -28,6 +28,7 @@
28 28  Console Output from End device to see the transmit frequency
29 29  
30 30  
30 +
31 31  (% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
32 32  
33 33  * 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,6 +38,7 @@
38 38  Console Output from Gateway to see packets between end node and server.
39 39  
40 40  
41 +
41 41  (% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
42 42  
43 43  * If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
... ... @@ -49,6 +49,7 @@
49 49  The Traffic for the End node in the server, use TTN as example
50 50  
51 51  
53 +
52 52  (% style="color:blue" %)**4. Data Page in LoRaWAN server**
53 53  
54 54  * 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.
... ... @@ -57,11 +57,13 @@
57 57  
58 58  The data for the end device set in server
59 59  
62 +
60 60  [[image:image-20220526163732-5.png]]
61 61  
62 62  Check if OTAA Keys match the keys in device
63 63  
64 64  
68 +
65 65  = 2. Notice of US915/CN470/AU915 Frequency band =
66 66  
67 67  
... ... @@ -103,6 +103,7 @@
103 103  
104 104  US915 Channels
105 105  
110 +
106 106  [[image:image-20220526163926-7.png]]
107 107  
108 108  AU915 Channels
... ... @@ -133,6 +133,7 @@
133 133  )))
134 134  
135 135  
141 +
136 136  = 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
137 137  
138 138  
... ... @@ -155,6 +155,7 @@
155 155  )))
156 156  
157 157  
164 +
158 158  = 4. Transmision on ABP Mode =
159 159  
160 160  
... ... @@ -183,6 +183,7 @@
183 183  Disable Frame Counter Check in ABP Mode
184 184  
185 185  
193 +
186 186  = 5. Downstream Debug =
187 187  
188 188  == 5.1 How it work ==
... ... @@ -208,8 +208,6 @@
208 208  * 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.**
209 209  
210 210  
211 -
212 -
213 213  == 5.2 See Debug Info ==
214 214  
215 215  
... ... @@ -243,6 +243,7 @@
243 243  )))
244 244  
245 245  
252 +
246 246  (((
247 247  (% style="color:blue" %)**For LoRaWAN Gateway**
248 248  )))
... ... @@ -258,6 +258,7 @@
258 258  )))
259 259  
260 260  
268 +
261 261  (((
262 262  (% style="color:blue" %)**For End Node**
263 263  )))
... ... @@ -272,6 +272,7 @@
272 272  (% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
273 273  (% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
274 274  
283 +
275 275  
276 276  )))
277 277  
... ... @@ -289,6 +289,8 @@
289 289  
290 290  (((
291 291  
301 +
302 +
292 292  )))
293 293  
294 294  (((
... ... @@ -307,6 +307,7 @@
307 307   1:0012345678}}}
308 308  
309 309  
321 +
310 310  == 5.3 If problem doesn't solve ==
311 311  
312 312  
... ... @@ -318,7 +318,6 @@
318 318  * End Node traffic (from server UI) to shows end node activity in server.
319 319  
320 320  
321 -
322 322  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
323 323  
324 324  
... ... @@ -345,6 +345,7 @@
345 345  )))
346 346  
347 347  
359 +
348 348  = 7. Decrypt a LoRaWAN Packet =
349 349  
350 350  
... ... @@ -358,6 +358,7 @@
358 358  [[image:image-20220526165525-16.png]]
359 359  
360 360  
373 +
361 361  (% style="color:blue" %)**2. In LG02 , configure to receive above message**
362 362  
363 363  [[image:image-20220526165612-17.png]]
... ... @@ -368,6 +368,7 @@
368 368  [[image:image-20220526171112-21.png]]
369 369  
370 370  
384 +
371 371  (% style="color:blue" %)**3. Decode the info in web**
372 372  
373 373  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
... ... @@ -390,6 +390,7 @@
390 390  )))
391 391  
392 392  
407 +
393 393  = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
394 394  
395 395  
... ... @@ -396,6 +396,7 @@
396 396  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.
397 397  
398 398  
414 +
399 399  = 9. Why do I see a "MIC Mismatch" error message from the server? =
400 400  
401 401  
... ... @@ -430,27 +430,23 @@
430 430  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
431 431  
432 432  
433 -* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
449 +**Why this happen:**
434 434  
435 -(((
436 -When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
437 -)))
451 +For US915, AU915 or AS923 frequencies.It is possible because: .
438 438  
439 -(((
440 -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.
441 -)))
453 +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.
442 442  
443 -* (((
444 -Solution: Use the decoder to filter out this 00 packet.
445 -)))
446 -* (((
447 -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]]
455 +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.
448 448  
449 449  
458 +**How to solve:**
450 450  
451 -
452 -)))
460 +Solution: Use the decoder to filter out this 0x00 packet.
453 453  
462 +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]]
463 +
464 +
465 +
454 454  = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
455 455  
456 456  
... ... @@ -512,6 +512,7 @@
512 512  (Any combination of 16 bit codes can be used）
513 513  
514 514  
527 +
515 515  = 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
516 516  )))
517 517  
... ... @@ -519,6 +519,30 @@
519 519  Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
520 520  
521 521  
535 += 13. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
522 522  
537 +
538 +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.
539 +
540 +
541 +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:
542 +
543 +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:
544 +
545 +* (((
546 +Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
547 +)))
548 +* (((
549 +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)
550 +)))
551 +
552 +This change will make the activation time a littler longer but make sure the device can be used in any subband.
553 +
554 +
555 +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.
556 +
557 +
558 +[[image:image-20221215223215-1.png||height="584" width="1280"]]
559 +
523 523  (% class="wikigeneratedid" %)
524 524  
image-20221215223215-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +183.6 KB
Content

Applications

Navigation

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