Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 32.6 >
edited by Xiaoling
on 2022/07/13 15:03
To version < 33.1 >
edited by Edwin Chen
on 2022/10/19 23:11
>
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,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**
41 +(% 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**
52 +(% 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  
65 +
63 63  = 2. Notice of US915/CN470/AU915 Frequency band =
64 64  
65 65  
... ... @@ -131,6 +131,7 @@
131 131  )))
132 132  
133 133  
137 +
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  
160 +
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  
189 +
184 184  = 5. Downstream Debug =
185 185  
186 186  == 5.1 How it work ==
... ... @@ -205,6 +205,8 @@
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  
214 +
215 +
208 208  == 5.2 See Debug Info ==
209 209  
210 210  
... ... @@ -238,6 +238,7 @@
238 238  )))
239 239  
240 240  
249 +
241 241  (((
242 242  (% style="color:blue" %)**For LoRaWAN Gateway**
243 243  )))
... ... @@ -253,6 +253,7 @@
253 253  )))
254 254  
255 255  
265 +
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  
280 +
270 270  
271 271  )))
272 272  
... ... @@ -284,6 +284,8 @@
284 284  
285 285  (((
286 286  
298 +
299 +
287 287  )))
288 288  
289 289  (((
... ... @@ -302,6 +302,7 @@
302 302   1:0012345678}}}
303 303  
304 304  
318 +
305 305  == 5.3 If problem doesn't solve ==
306 306  
307 307  
... ... @@ -314,9 +314,9 @@
314 314  
315 315  
316 316  
317 -
318 318  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
319 319  
333 +
320 320  (((
321 321  In LoRaWAN, the gatewat will use the frequency specify by the server to transmit a packet as downlink purpose. Each Frequency band has different downlink frequency. and the gateway has a frequency range limited to transmit downlink.
322 322  )))
... ... @@ -340,22 +340,23 @@
340 340  )))
341 341  
342 342  
357 +
343 343  = 7. Decrypt a LoRaWAN Packet =
344 344  
345 -~1. LHT65 End device configure:
346 346  
347 -(% class="box infomessage" %)
348 -(((
349 -**Change to ABP Mode: AT+NJM=0**
350 -**Change to fix frequency: AT+CHS=904900000**
351 -**Change to fix DR: AT+DR=0**
352 -)))
361 +(% style="color:blue" %)**1. LHT65 End device configure:**
353 353  
363 +**Change to ABP Mode:  AT+NJM=0**
364 +**Change to fix frequency:  AT+CHS=904900000**
365 +**Change to fix DR:  AT+DR=0**
366 +
367 +
354 354  [[image:image-20220526165525-16.png]]
355 355  
356 356  
357 -2. In LG02 , configure to receive above message
358 358  
372 +(% style="color:blue" %)**2. In LG02 , configure to receive above message**
373 +
359 359  [[image:image-20220526165612-17.png]]
360 360  
361 361  
... ... @@ -364,8 +364,9 @@
364 364  [[image:image-20220526171112-21.png]]
365 365  
366 366  
367 -3. Decode the info in web
368 368  
383 +(% style="color:blue" %)**3. Decode the info in web**
384 +
369 369  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
370 370  
371 371  Need these three fields:
... ... @@ -376,6 +376,7 @@
376 376  
377 377  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
378 378  
395 +
379 379  [[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]]
380 380  
381 381  [[image:image-20220526171029-20.png]]
... ... @@ -385,15 +385,19 @@
385 385  )))
386 386  
387 387  
405 +
388 388  = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
389 389  
408 +
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  
412 +
393 393  = 9. Why do I see a "MIC Mismatch" error message from the server? =
394 394  
415 +
395 395  (((
396 -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.
397 397  )))
398 398  
399 399  (((
... ... @@ -415,32 +415,29 @@
415 415  * (((
416 416  If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
417 417  
439 +
440 +
418 418  
419 419  )))
420 420  
421 421  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
422 422  
423 -* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
424 424  
425 -(((
426 -When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
427 -)))
447 +* If you are using US915, AU915 or AS923 frequencies.It is possible because: .
428 428  
429 -(((
449 +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.
450 +
430 430  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.
431 -)))
432 432  
433 -* (((
434 434  Solution: Use the decoder to filter out this 00 packet.
435 -)))
436 -* (((
454 +
437 437  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]]
438 438  
439 -
440 -)))
441 441  
458 +
442 442  = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
443 443  
461 +
444 444  (((
445 445  It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
446 446  )))
... ... @@ -471,6 +471,8 @@
471 471  
472 472  (((
473 473  You can rewrites the keys by running commands in AT Console
492 +
493 +
474 474  )))
475 475  
476 476  (((
... ... @@ -497,6 +497,7 @@
497 497  (Any combination of 16 bit codes can be used）
498 498  
499 499  
520 +
500 500  = 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
501 501  )))
502 502  

Applications

Navigation

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