Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 32.8 >
edited by Xiaoling
on 2022/07/13 15:10
To version < 22.2 >
edited by Xiaoling
on 2022/05/26 16:48
>
Change comment: There is no comment for this version

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  
... ... @@ -21,7 +21,7 @@
21 21  * If the device is sending join request to server?
22 22  * What frequency the device is sending?
23 23  
24 -[[image:image-20220526164956-15.png]]
26 +[[image:image-20220526163523-1.png]]
25 25  
26 26  Console Output from End device to see the transmit frequency
27 27  
... ... @@ -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,13 @@
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  
200 +
208 208  == 5.2 See Debug Info ==
209 209  
210 -
211 211  (((
212 -(% style="color:blue" %)**For LoRaWAN Server**
204 +**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**
234 +**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**
249 +**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:**
261 +(% class="box infomessage" %)
262 +(((
263 +AT+RX2FQ=869525000     ~-~--> The RX2 Window frequency
264 +AT+RX2DR=3      ~-~--> The RX2 DataRate
265 +AT+RX1DL=1000   ~-~--> Receive Delay 1
266 +AT+RX2DL=2000   ~-~--> Receive Delay 2
275 275  )))
268 +)))
276 276  
270 +(((
271 +**when the device running, we can see below info:**
272 +)))
273 +
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:**
287 +**Another message:**
291 291  )))
292 292  
293 293  {{{ [12502]***** UpLinkCounter= 0 *****
... ... @@ -301,22 +301,20 @@
301 301   Receive data
302 302   1:0012345678}}}
303 303  
301 +(% class="wikigeneratedid" %)
302 +​​​​​​​
304 304  
305 -== 5.3 If problem doesn't solve ==
304 +== 5.3 If problem doesn’t solve ==
306 306  
306 +**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:**
307 307  
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 -
310 310  * End node console to show the transmit freuqency and DR.
311 311  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server.
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 317  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
318 318  
319 -
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  )))
... ... @@ -342,28 +342,35 @@
342 342  
343 343  = 7. Decrypt a LoRaWAN Packet =
344 344  
340 +~1. LHT65 End device configure:
345 345  
346 -(% style="color:blue" %)**1. LHT65 End device configure:**
342 +(% class="box infomessage" %)
343 +(((
344 +Change to ABP Mode: AT+NJM=0
345 +)))
347 347  
348 -**Change to ABP Mode:  AT+NJM=0**
349 -**Change to fix frequency:  AT+CHS=904900000**
350 -**Change to fix DR:  AT+DR=0**
347 +(% class="box infomessage" %)
348 +(((
349 +Change to fix frequency: AT+CHS=904900000
350 +)))
351 351  
352 -[[image:image-20220526165525-16.png]]
352 +(% class="box infomessage" %)
353 +(((
354 +Change to fix DR: AT+DR=0
355 +)))
353 353  
357 +[[image:https://wiki.dragino.com/images/e/e6/Decrypt_a_LoRaWAN_Packet1.jpg||alt="Decrypt a LoRaWAN Packet1.jpg" height="607" width="558"]]
354 354  
355 -(% style="color:blue" %)**2. In LG02 , configure to receive above message**
359 +2. In LG02 , configure to receive above message
356 356  
357 -[[image:image-20220526165612-17.png]]
361 +[[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 -
360 360  In LG02 console, we can see the hex receive are:
361 361  
362 -[[image:image-20220526171112-21.png]]
365 +[[image:https://wiki.dragino.com/images/f/f1/Decrypt_a_LoRaWAN_Packet3.jpg||alt="Decrypt a LoRaWAN Packet3.jpg" height="179" width="558"]]
363 363  
367 +3. Decode the info in web
364 364  
365 -(% style="color:blue" %)**3. Decode the info in web**
366 -
367 367  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
368 368  
369 369  Need these three fields:
... ... @@ -376,7 +376,7 @@
376 376  
377 377  [[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]]
378 378  
379 -[[image:image-20220526171029-20.png]]
381 +[[image:https://wiki.dragino.com/images/7/77/Decrypt_a_LoRaWAN_Packet4.png||alt="Decrypt a LoRaWAN Packet4.png" height="390" width="558"]]
380 380  
381 381  (((
382 382   The FRMPayload is the device payload.
... ... @@ -387,7 +387,6 @@
387 387  
388 388  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.
389 389  
390 -
391 391  = 9. Why do I see a "MIC Mismatch" error message from the server? =
392 392  
393 393  (((
... ... @@ -434,74 +434,39 @@
434 434  * (((
435 435  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]]
436 436  
438 +
437 437  
438 438  )))
439 439  
440 440  = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
441 441  
442 -(((
443 443  It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
444 -)))
445 445  
446 -(((
447 447  AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
448 -)))
449 449  
450 -(((
451 451  AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
452 -)))
453 453  
454 -(((
455 455  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
456 -)))
457 457  
458 -(((
459 459  AT+APPEUI=00 00 00 00 00 00 00 00
460 -)))
461 461  
462 -(((
463 -
464 -)))
465 465  
466 -(((
467 467  You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number.
468 -)))
469 469  
470 -(((
471 471  You can rewrites the keys by running commands in AT Console
472 -)))
473 473  
474 -(((
475 -**For example：**
476 -)))
459 +For example：
477 477  
478 -(((
479 479  AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
480 -)))
481 481  
482 -(((
483 483  AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
484 -)))
485 485  
486 -(((
487 487  AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
488 -)))
489 489  
490 -(((
491 491  AT+APPEUI=2C 45 47 E3 24 12 23 24
492 -)))
493 493  
494 -(((
495 495  (Any combination of 16 bit codes can be used）
496 496  
497 497  
498 -= 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
499 -)))
500 -
501 -
502 -Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
503 -
504 -
505 -
506 506  (% class="wikigeneratedid" %)
507 507  
image-20220526164956-15.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -634.4 KB
Content
image-20220526165525-16.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -185.4 KB
Content
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