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

Summary

Details

Page properties
Content
... ... @@ -1,14 +1,12 @@
1 -**~ Contents:**
1 +**~ Table of Contents:**
2 2  
3 -(((
4 -
5 -)))
6 -
7 7  {{toc/}}
8 8  
9 9  
6 +
10 10  = 1. OTAA Join Process Debug =
11 11  
9 +
12 12  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.
13 13  \\**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:**
14 14  
... ... @@ -23,7 +23,7 @@
23 23  * If the device is sending join request to server?
24 24  * What frequency the device is sending?
25 25  
26 -[[image:image-20220526163523-1.png]]
24 +[[image:image-20220526164956-15.png]]
27 27  
28 28  Console Output from End device to see the transmit frequency
29 29  
... ... @@ -64,6 +64,7 @@
64 64  
65 65  = 2. Notice of US915/CN470/AU915 Frequency band =
66 66  
65 +
67 67  (((
68 68  If user has problem to work with lorawan server in band US915/AU915/CN470, he can check:
69 69  )))
... ... @@ -106,10 +106,13 @@
106 106  
107 107  AU915 Channels
108 108  
108 +
109 109  [[image:image-20220526163941-8.png]]
110 110  
111 111  (((
112 112  CN470 Channels
113 +
114 +
113 113  )))
114 114  
115 115  (((
... ... @@ -120,6 +120,8 @@
120 120  
121 121  (((
122 122  TTN FREQUENCY PLAN
125 +
126 +
123 123  )))
124 124  
125 125  (((
... ... @@ -129,6 +129,7 @@
129 129  
130 130  = 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
131 131  
136 +
132 132  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:
133 133  
134 134  * **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.
... ... @@ -150,6 +150,7 @@
150 150  
151 151  = 4. Transmision on ABP Mode =
152 152  
158 +
153 153  (((
154 154  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.
155 155  )))
... ... @@ -179,6 +179,7 @@
179 179  
180 180  == 5.1 How it work ==
181 181  
188 +
182 182  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.
183 183  
184 184  (((
... ... @@ -185,10 +185,11 @@
185 185  Depends on Class A or Class C, the receive windows will be a little difference,
186 186  )))
187 187  
188 -[[image:image-20220526164547-11.png]]
195 +[[image:image-20220531161828-1.png]]
189 189  
190 190  receive windows for Class A and Class C
191 191  
199 +
192 192  Below are the requirement for the End Device to receive the packets.
193 193  
194 194  * The End Device must open the receive windows: RX1 or RX2
... ... @@ -195,13 +195,13 @@
195 195  * The LoRaWAN server must send a downstream packet, and the gateway forward this downstream packet for this end node.
196 196  * This downstream packet must arrive to the end node while RX1 or RX2 is open.
197 197  * This packet must match the frequency of the RX1 or RX2 window.
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.**
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.**
199 199  
200 -
201 201  == 5.2 See Debug Info ==
202 202  
210 +
203 203  (((
204 -**For LoRaWAN Server**
212 +(% style="color:blue" %)**For LoRaWAN Server**
205 205  )))
206 206  
207 207  (((
... ... @@ -231,7 +231,7 @@
231 231  
232 232  
233 233  (((
234 -**For LoRaWAN Gateway**
242 +(% style="color:blue" %)**For LoRaWAN Gateway**
235 235  )))
236 236  
237 237  (((
... ... @@ -246,7 +246,7 @@
246 246  
247 247  
248 248  (((
249 -**For End Node**
257 +(% style="color:blue" %)**For End Node**
250 250  )))
251 251  
252 252  (((
... ... @@ -254,23 +254,18 @@
254 254  )))
255 255  
256 256  (((
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 +
257 257  
258 258  )))
259 259  
260 260  (((
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
274 +(% style="color:blue" %)**when the device running, we can see below info:**
267 267  )))
268 -)))
269 269  
270 -(((
271 -**when the device running, we can see below info:**
272 -)))
273 -
274 274  {{{ [12502]***** UpLinkCounter= 0 *****
275 275   [12503]TX on freq 868500000 Hz at DR 0
276 276   [13992]txDone
... ... @@ -284,7 +284,7 @@
284 284  )))
285 285  
286 286  (((
287 -**Another message:**
290 +(% style="color:blue" %)**Another message:**
288 288  )))
289 289  
290 290  {{{ [12502]***** UpLinkCounter= 0 *****
... ... @@ -299,20 +299,21 @@
299 299   1:0012345678}}}
300 300  
301 301  
302 -== 5.3 If problem doesn’t solve ==
305 +== 5.3 If problem doesn't solve ==
303 303  
304 -**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:**
305 305  
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 +
306 306  * End node console to show the transmit freuqency and DR.
307 307  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server.
308 308  * Gateway traffic (from server UI) to shows the data exchange between gateway and server.
309 309  * End Node traffic (from server UI) to shows end node activity in server.
310 310  
311 -(% class="wikigeneratedid" %)
312 -​​​​​​​
313 313  
316 +
314 314  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
315 315  
319 +
316 316  (((
317 317  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.
318 318  )))
... ... @@ -338,35 +338,28 @@
338 338  
339 339  = 7. Decrypt a LoRaWAN Packet =
340 340  
341 -~1. LHT65 End device configure:
342 342  
343 -(% class="box infomessage" %)
344 -(((
345 -Change to ABP Mode: AT+NJM=0
346 -)))
346 +(% style="color:blue" %)**1. LHT65 End device configure:**
347 347  
348 -(% class="box infomessage" %)
349 -(((
350 -Change to fix frequency: AT+CHS=904900000
351 -)))
348 +**Change to ABP Mode:  AT+NJM=0**
349 +**Change to fix frequency:  AT+CHS=904900000**
350 +**Change to fix DR:  AT+DR=0**
352 352  
353 -(% class="box infomessage" %)
354 -(((
355 -Change to fix DR: AT+DR=0
356 -)))
352 +[[image:image-20220526165525-16.png]]
357 357  
358 -[[image:https://wiki.dragino.com/images/e/e6/Decrypt_a_LoRaWAN_Packet1.jpg||alt="Decrypt a LoRaWAN Packet1.jpg" height="607" width="558"]]
359 359  
360 -2. In LG02 , configure to receive above message
355 +(% style="color:blue" %)**2. In LG02 , configure to receive above message**
361 361  
362 -[[image:https://wiki.dragino.com/images/c/c3/Decrypt_a_LoRaWAN_Packet2.jpg||alt="Decrypt a LoRaWAN Packet2.jpg" height="337" width="558"]]
357 +[[image:image-20220526165612-17.png]]
363 363  
359 +
364 364  In LG02 console, we can see the hex receive are:
365 365  
366 -[[image:https://wiki.dragino.com/images/f/f1/Decrypt_a_LoRaWAN_Packet3.jpg||alt="Decrypt a LoRaWAN Packet3.jpg" height="179" width="558"]]
362 +[[image:image-20220526171112-21.png]]
367 367  
368 -3. Decode the info in web
369 369  
365 +(% style="color:blue" %)**3. Decode the info in web**
366 +
370 370  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
371 371  
372 372  Need these three fields:
... ... @@ -379,7 +379,7 @@
379 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:https://wiki.dragino.com/images/7/77/Decrypt_a_LoRaWAN_Packet4.png||alt="Decrypt a LoRaWAN Packet4.png" height="390" width="558"]]
379 +[[image:image-20220526171029-20.png]]
383 383  
384 384  (((
385 385   The FRMPayload is the device payload.
... ... @@ -390,6 +390,7 @@
390 390  
391 391  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.
392 392  
390 +
393 393  = 9. Why do I see a "MIC Mismatch" error message from the server? =
394 394  
395 395  (((
... ... @@ -436,39 +436,74 @@
436 436  * (((
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 440  
441 441  )))
442 442  
443 443  = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
444 444  
442 +(((
445 445  It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
444 +)))
446 446  
446 +(((
447 447  AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
448 +)))
448 448  
450 +(((
449 449  AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
452 +)))
450 450  
454 +(((
451 451  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
456 +)))
452 452  
458 +(((
453 453  AT+APPEUI=00 00 00 00 00 00 00 00
460 +)))
454 454  
462 +(((
463 +
464 +)))
455 455  
466 +(((
456 456  You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number.
468 +)))
457 457  
470 +(((
458 458  You can rewrites the keys by running commands in AT Console
472 +)))
459 459  
460 -For example：
474 +(((
475 +**For example：**
476 +)))
461 461  
478 +(((
462 462  AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
480 +)))
463 463  
482 +(((
464 464  AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
484 +)))
465 465  
486 +(((
466 466  AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
488 +)))
467 467  
490 +(((
468 468  AT+APPEUI=2C 45 47 E3 24 12 23 24
492 +)))
469 469  
494 +(((
470 470  (Any combination of 16 bit codes can be used）
471 471  
472 472  
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 +
473 473  (% class="wikigeneratedid" %)
474 474  
image-20220526165525-16.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +185.4 KB
Content
image-20220526165612-17.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +116.5 KB
Content
image-20220526165855-18.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +183.7 KB
Content
image-20220526170151-19.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +70.4 KB
Content
image-20220526171029-20.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +70.6 KB
Content
image-20220526171112-21.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +183.8 KB
Content
image-20220531161828-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +98.6 KB
Content

Applications

Navigation

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