Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 32.9 >
edited by Xiaoling
on 2022/07/13 15:13
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
... ... @@ -16,8 +16,9 @@
16 16  * End Node traffic (from server UI) to shows end node activity in server. (Normaly possible)
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:**
20 20  
20 +(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
21 +
21 21  * If the device is sending join request to server?
22 22  * What frequency the device is sending?
23 23  
... ... @@ -26,8 +26,9 @@
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  
31 +(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
32 +
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)
32 32  * If the gateway gets the Join Accept message from server and transmit it via LoRa?
33 33  
... ... @@ -36,8 +36,9 @@
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  
42 +(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
43 +
41 41  * If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
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.
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.
... ... @@ -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  
54 +(% style="color:blue" %)**4. Data Page in LoRaWAN server**
55 +
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,11 +55,13 @@
55 55  
56 56  The data for the end device set in server
57 57  
62 +
58 58  [[image:image-20220526163732-5.png]]
59 59  
60 60  Check if OTAA Keys match the keys in device
61 61  
62 62  
68 +
63 63  = 2. Notice of US915/CN470/AU915 Frequency band =
64 64  
65 65  
... ... @@ -101,6 +101,7 @@
101 101  
102 102  US915 Channels
103 103  
110 +
104 104  [[image:image-20220526163926-7.png]]
105 105  
106 106  AU915 Channels
... ... @@ -131,6 +131,7 @@
131 131  )))
132 132  
133 133  
141 +
134 134  = 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
135 135  
136 136  
... ... @@ -153,6 +153,7 @@
153 153  )))
154 154  
155 155  
164 +
156 156  = 4. Transmision on ABP Mode =
157 157  
158 158  
... ... @@ -181,6 +181,7 @@
181 181  Disable Frame Counter Check in ABP Mode
182 182  
183 183  
193 +
184 184  = 5. Downstream Debug =
185 185  
186 186  == 5.1 How it work ==
... ... @@ -205,6 +205,7 @@
205 205  * This packet must match the frequency of the RX1 or RX2 window.
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  
218 +
208 208  == 5.2 See Debug Info ==
209 209  
210 210  
... ... @@ -238,6 +238,7 @@
238 238  )))
239 239  
240 240  
252 +
241 241  (((
242 242  (% style="color:blue" %)**For LoRaWAN Gateway**
243 243  )))
... ... @@ -253,6 +253,7 @@
253 253  )))
254 254  
255 255  
268 +
256 256  (((
257 257  (% style="color:blue" %)**For End Node**
258 258  )))
... ... @@ -267,6 +267,7 @@
267 267  (% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
268 268  (% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
269 269  
283 +
270 270  
271 271  )))
272 272  
... ... @@ -284,6 +284,8 @@
284 284  
285 285  (((
286 286  
301 +
302 +
287 287  )))
288 288  
289 289  (((
... ... @@ -302,6 +302,7 @@
302 302   1:0012345678}}}
303 303  
304 304  
321 +
305 305  == 5.3 If problem doesn't solve ==
306 306  
307 307  
... ... @@ -313,7 +313,6 @@
313 313  * End Node traffic (from server UI) to shows end node activity in server.
314 314  
315 315  
316 -
317 317  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
318 318  
319 319  
... ... @@ -340,6 +340,7 @@
340 340  )))
341 341  
342 342  
359 +
343 343  = 7. Decrypt a LoRaWAN Packet =
344 344  
345 345  
... ... @@ -349,9 +349,11 @@
349 349  **Change to fix frequency:  AT+CHS=904900000**
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/]]
... ... @@ -384,6 +384,7 @@
384 384  )))
385 385  
386 386  
407 +
387 387  = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
388 388  
389 389  
... ... @@ -390,6 +390,7 @@
390 390  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.
391 391  
392 392  
414 +
393 393  = 9. Why do I see a "MIC Mismatch" error message from the server? =
394 394  
395 395  
... ... @@ -424,27 +424,23 @@
424 424  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
425 425  
426 426  
427 -* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
449 +**Why this happen:**
428 428  
429 -(((
430 -When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
431 -)))
451 +For US915, AU915 or AS923 frequencies.It is possible because: .
432 432  
433 -(((
434 -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.
435 -)))
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.
436 436  
437 -* (((
438 -Solution: Use the decoder to filter out this 00 packet.
439 -)))
440 -* (((
441 -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.
442 442  
443 443  
458 +**How to solve:**
444 444  
445 -
446 -)))
460 +Solution: Use the decoder to filter out this 0x00 packet.
447 447  
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 +
448 448  = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
449 449  
450 450  
... ... @@ -506,6 +506,7 @@
506 506  (Any combination of 16 bit codes can be used）
507 507  
508 508  
527 +
509 509  = 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
510 510  )))
511 511  
... ... @@ -513,6 +513,30 @@
513 513  Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
514 514  
515 515  
535 += 13. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
516 516  
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 +
517 517  (% class="wikigeneratedid" %)
518 518  
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