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 < 24.1 >
edited by Xiaoling
on 2022/05/26 16:55
>
Change comment: Uploaded new attachment "image-20220526165525-16.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -1,12 +1,14 @@
1 -**~ Table of Contents:**
1 +**~ Contents:**
2 2  
3 +(((
4 +
5 +)))
6 +
3 3  {{toc/}}
4 4  
5 5  
6 -
7 7  = 1. OTAA Join Process Debug =
8 8  
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 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  
... ... @@ -62,7 +62,6 @@
62 62  
63 63  = 2. Notice of US915/CN470/AU915 Frequency band =
64 64  
65 -
66 66  (((
67 67  If user has problem to work with lorawan server in band US915/AU915/CN470, he can check:
68 68  )))
... ... @@ -105,13 +105,10 @@
105 105  
106 106  AU915 Channels
107 107  
108 -
109 109  [[image:image-20220526163941-8.png]]
110 110  
111 111  (((
112 112  CN470 Channels
113 -
114 -
115 115  )))
116 116  
117 117  (((
... ... @@ -122,8 +122,6 @@
122 122  
123 123  (((
124 124  TTN FREQUENCY PLAN
125 -
126 -
127 127  )))
128 128  
129 129  (((
... ... @@ -133,7 +133,6 @@
133 133  
134 134  = 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
135 135  
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 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.
... ... @@ -155,7 +155,6 @@
155 155  
156 156  = 4. Transmision on ABP Mode =
157 157  
158 -
159 159  (((
160 160  In ABP mode, there is a Frame Counter Checks. With this check enabled, the server will only accept the frame with a higher counter. If you reboot the device in ABP mode, the device will start from count 0, so you won't be able to see the frame update in server.
161 161  )))
... ... @@ -185,7 +185,6 @@
185 185  
186 186  == 5.1 How it work ==
187 187  
188 -
189 189  LoRaWAN End node will open two receive windows to receive the downstream data. If the downstream packets arrive the end node at these receive windows, the end node will be able to get this packet and process it.
190 190  
191 191  (((
... ... @@ -192,11 +192,10 @@
192 192  Depends on Class A or Class C, the receive windows will be a little difference,
193 193  )))
194 194  
195 -[[image:image-20220531161828-1.png]]
188 +[[image:image-20220526164547-11.png]]
196 196  
197 197  receive windows for Class A and Class C
198 198  
199 -
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
... ... @@ -203,13 +203,12 @@
203 203  * The LoRaWAN server must send a downstream packet, and the gateway forward this downstream packet for this end node.
204 204  * This downstream packet must arrive to the end node while RX1 or RX2 is open.
205 205  * This packet must match the frequency of the RX1 or RX2 window.
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.**
198 +* This packet must match the DataRate of RX1(RX1DR) or RX2 (RX2DR). **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 ==
209 209  
210 -
211 211  (((
212 -(% style="color:blue" %)**For LoRaWAN Server**
203 +**For LoRaWAN Server**
213 213  )))
214 214  
215 215  (((
... ... @@ -239,7 +239,7 @@
239 239  
240 240  
241 241  (((
242 -(% style="color:blue" %)**For LoRaWAN Gateway**
233 +**For LoRaWAN Gateway**
243 243  )))
244 244  
245 245  (((
... ... @@ -254,7 +254,7 @@
254 254  
255 255  
256 256  (((
257 -(% style="color:blue" %)**For End Node**
248 +**For End Node**
258 258  )))
259 259  
260 260  (((
... ... @@ -262,18 +262,23 @@
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
269 -
270 270  
271 271  )))
272 272  
273 273  (((
274 -(% style="color:blue" %)**when the device running, we can see below info:**
260 +(% class="box infomessage" %)
261 +(((
262 +AT+RX2FQ=869525000     ~-~--> The RX2 Window frequency
263 +AT+RX2DR=3      ~-~--> The RX2 DataRate
264 +AT+RX1DL=1000   ~-~--> Receive Delay 1
265 +AT+RX2DL=2000   ~-~--> Receive Delay 2
275 275  )))
267 +)))
276 276  
269 +(((
270 +**when the device running, we can see below info:**
271 +)))
272 +
277 277  {{{ [12502]***** UpLinkCounter= 0 *****
278 278   [12503]TX on freq 868500000 Hz at DR 0
279 279   [13992]txDone
... ... @@ -287,7 +287,7 @@
287 287  )))
288 288  
289 289  (((
290 -(% style="color:blue" %)**Another message:**
286 +**Another message:**
291 291  )))
292 292  
293 293  {{{ [12502]***** UpLinkCounter= 0 *****
... ... @@ -302,9 +302,8 @@
302 302   1:0012345678}}}
303 303  
304 304  
305 -== 5.3 If problem doesn't solve ==
301 +== 5.3 If problem doesn’t solve ==
306 306  
307 -
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.
... ... @@ -312,12 +312,8 @@
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 -
321 321  (((
322 322  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.
323 323  )))
... ... @@ -343,29 +343,35 @@
343 343  
344 344  = 7. Decrypt a LoRaWAN Packet =
345 345  
337 +~1. LHT65 End device configure:
346 346  
347 -(% style="color:blue" %)**1. LHT65 End device configure:**
339 +(% class="box infomessage" %)
340 +(((
341 +Change to ABP Mode: AT+NJM=0
342 +)))
348 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**
344 +(% class="box infomessage" %)
345 +(((
346 +Change to fix frequency: AT+CHS=904900000
347 +)))
352 352  
349 +(% class="box infomessage" %)
350 +(((
351 +Change to fix DR: AT+DR=0
352 +)))
353 353  
354 -[[image:image-20220526165525-16.png]]
354 +[[image:https://wiki.dragino.com/images/e/e6/Decrypt_a_LoRaWAN_Packet1.jpg||alt="Decrypt a LoRaWAN Packet1.jpg" height="607" width="558"]]
355 355  
356 +2. In LG02 , configure to receive above message
356 356  
357 -(% style="color:blue" %)**2. In LG02 , configure to receive above message**
358 +[[image:https://wiki.dragino.com/images/c/c3/Decrypt_a_LoRaWAN_Packet2.jpg||alt="Decrypt a LoRaWAN Packet2.jpg" height="337" width="558"]]
358 358  
359 -[[image:image-20220526165612-17.png]]
360 -
361 -
362 362  In LG02 console, we can see the hex receive are:
363 363  
364 -[[image:image-20220526171112-21.png]]
362 +[[image:https://wiki.dragino.com/images/f/f1/Decrypt_a_LoRaWAN_Packet3.jpg||alt="Decrypt a LoRaWAN Packet3.jpg" height="179" width="558"]]
365 365  
364 +3. Decode the info in web
366 366  
367 -(% style="color:blue" %)**3. Decode the info in web**
368 -
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,10 +376,9 @@
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  
379 -
380 380  [[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]]
381 381  
382 -[[image:image-20220526171029-20.png]]
378 +[[image:https://wiki.dragino.com/images/7/77/Decrypt_a_LoRaWAN_Packet4.png||alt="Decrypt a LoRaWAN Packet4.png" height="390" width="558"]]
383 383  
384 384  (((
385 385   The FRMPayload is the device payload.
... ... @@ -388,15 +388,12 @@
388 388  
389 389  = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
390 390  
391 -
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 -
395 395  = 9. Why do I see a "MIC Mismatch" error message from the server? =
396 396  
397 -
398 398  (((
399 -1)  If the user receives a "MIC Mismatch" message after registering the node on the server.
392 +1)If the user receives a "MIC Mismatch" message after registering the node on the server.
400 400  )))
401 401  
402 402  (((
... ... @@ -418,14 +418,11 @@
418 418  * (((
419 419  If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
420 420  
421 -
422 -
423 423  
424 424  )))
425 425  
426 426  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
427 427  
428 -
429 429  * If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
430 430  
431 431  (((
... ... @@ -443,78 +443,36 @@
443 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]]
444 444  
445 445  
446 -
447 447  
448 448  )))
449 449  
450 450  = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
451 451  
452 -
453 -(((
454 454  It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
455 -)))
456 456  
457 -(((
458 458  AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
459 -)))
460 460  
461 -(((
462 462  AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
463 -)))
464 464  
465 -(((
466 466  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
467 -)))
468 468  
469 -(((
470 470  AT+APPEUI=00 00 00 00 00 00 00 00
471 -)))
472 472  
473 -(((
474 -
475 -)))
476 476  
477 -(((
478 478  You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number.
479 -)))
480 480  
481 -(((
482 482  You can rewrites the keys by running commands in AT Console
483 483  
484 -
485 -)))
456 +For example：
486 486  
487 -(((
488 -**For example：**
489 -)))
490 -
491 -(((
492 492  AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
493 -)))
494 494  
495 -(((
496 496  AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
497 -)))
498 498  
499 -(((
500 500  AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
501 -)))
502 502  
503 -(((
504 504  AT+APPEUI=2C 45 47 E3 24 12 23 24
505 -)))
506 506  
507 -(((
508 508  (Any combination of 16 bit codes can be used）
509 509  
510 510  
511 -= 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
512 -)))
513 -
514 -
515 -Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
516 -
517 -
518 -
519 -(% class="wikigeneratedid" %)
520 -
image-20220526165612-17.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -116.5 KB
Content
image-20220526165855-18.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -183.7 KB
Content
image-20220526170151-19.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -70.4 KB
Content
image-20220526171029-20.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -70.6 KB
Content
image-20220526171112-21.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -183.8 KB
Content
image-20220531161828-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -98.6 KB
Content

Applications

Navigation

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