Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 32.13 >
edited by Xiaoling
on 2022/07/13 15:21
To version < 35.1 >
edited by Edwin Chen
on 2022/10/19 23:15
>
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,7 +16,7 @@
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:**
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?
22 22  * What frequency the device is sending?
... ... @@ -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  
30 +(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
31 +
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,7 +36,7 @@
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 +(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
40 40  
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.
... ... @@ -47,7 +47,7 @@
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 +(% style="color:blue" %)**4. Data Page in LoRaWAN server**
51 51  
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  
... ... @@ -60,6 +60,7 @@
60 60  Check if OTAA Keys match the keys in device
61 61  
62 62  
64 +
63 63  = 2. Notice of US915/CN470/AU915 Frequency band =
64 64  
65 65  
... ... @@ -131,6 +131,7 @@
131 131  )))
132 132  
133 133  
136 +
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  
159 +
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  
188 +
184 184  = 5. Downstream Debug =
185 185  
186 186  == 5.1 How it work ==
... ... @@ -238,6 +238,7 @@
238 238  )))
239 239  
240 240  
246 +
241 241  (((
242 242  (% style="color:blue" %)**For LoRaWAN Gateway**
243 243  )))
... ... @@ -253,6 +253,7 @@
253 253  )))
254 254  
255 255  
262 +
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  
277 +
270 270  
271 271  )))
272 272  
... ... @@ -284,6 +284,8 @@
284 284  
285 285  (((
286 286  
295 +
296 +
287 287  )))
288 288  
289 289  (((
... ... @@ -302,6 +302,7 @@
302 302   1:0012345678}}}
303 303  
304 304  
315 +
305 305  == 5.3 If problem doesn't solve ==
306 306  
307 307  
... ... @@ -312,9 +312,6 @@
312 312  * Gateway traffic (from server UI) to shows the data exchange between gateway and server.
313 313  * End Node traffic (from server UI) to shows end node activity in server.
314 314  
315 -
316 -
317 -
318 318  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
319 319  
320 320  
... ... @@ -341,6 +341,7 @@
341 341  )))
342 342  
343 343  
352 +
344 344  = 7. Decrypt a LoRaWAN Packet =
345 345  
346 346  
... ... @@ -354,6 +354,7 @@
354 354  [[image:image-20220526165525-16.png]]
355 355  
356 356  
366 +
357 357  (% style="color:blue" %)**2. In LG02 , configure to receive above message**
358 358  
359 359  [[image:image-20220526165612-17.png]]
... ... @@ -364,6 +364,7 @@
364 364  [[image:image-20220526171112-21.png]]
365 365  
366 366  
377 +
367 367  (% style="color:blue" %)**3. Decode the info in web**
368 368  
369 369  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
... ... @@ -386,6 +386,7 @@
386 386  )))
387 387  
388 388  
400 +
389 389  = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
390 390  
391 391  
... ... @@ -392,6 +392,7 @@
392 392  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.
393 393  
394 394  
407 +
395 395  = 9. Why do I see a "MIC Mismatch" error message from the server? =
396 396  
397 397  
... ... @@ -426,27 +426,23 @@
426 426  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
427 427  
428 428  
429 -* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
442 +**Why this happen:**
430 430  
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 -)))
444 +For US915, AU915 or AS923 frequencies.It is possible because: .
434 434  
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 -)))
446 +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.
438 438  
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]]
448 +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.
444 444  
445 445  
451 +**How to solve:**
446 446  
447 -
448 -)))
453 +Solution: Use the decoder to filter out this 0x00 packet.
449 449  
455 +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]]
456 +
457 +
458 +
450 450  = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
451 451  
452 452  
... ... @@ -508,6 +508,7 @@
508 508  (Any combination of 16 bit codes can be used）
509 509  
510 510  
520 +
511 511  = 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
512 512  )))
513 513  

Applications

Navigation

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