Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 22.3 >
edited by Xiaoling
on 2022/05/26 16:48
To version < 37.1 >
edited by Edwin Chen
on 2022/12/15 22:33
>
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
... ... @@ -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  
... ... @@ -18,18 +18,20 @@
18 18  * End Node traffic (from server UI) to shows end node activity in server. (Normaly possible)
19 19  * 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)
20 20  
21 -**~1. End Device Join Screen shot, we can check:**
22 22  
20 +(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
21 +
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]]
25 +[[image:image-20220526164956-15.png]]
27 27  
28 28  Console Output from End device to see the transmit frequency
29 29  
30 30  
31 -**2. Gateway packet traffic in gateway web or ssh. we can check:**
32 32  
31 +(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
32 +
33 33  * If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
34 34  * If the gateway gets the Join Accept message from server and transmit it via LoRa?
35 35  
... ... @@ -38,8 +38,9 @@
38 38  Console Output from Gateway to see packets between end node and server.
39 39  
40 40  
41 -**3. Gateway Traffic Page in LoRaWAN Server**
42 42  
42 +(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
43 +
43 43  * If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
44 44  * 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.
45 45  * If the Join Accept message are in correct frequency? If you set the server to use US915 band, and your end node and gateway is EU868, you will see the Join Accept message are in US915 band so no possible to Join success.
... ... @@ -49,8 +49,9 @@
49 49  The Traffic for the End node in the server, use TTN as example
50 50  
51 51  
52 -**4. Data Page in LoRaWAN server**
53 53  
54 +(% style="color:blue" %)**4. Data Page in LoRaWAN server**
55 +
54 54  * 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.
55 55  
56 56  [[image:image-20220526163704-4.png]]
... ... @@ -57,13 +57,16 @@
57 57  
58 58  The data for the end device set in server
59 59  
62 +
60 60  [[image:image-20220526163732-5.png]]
61 61  
62 62  Check if OTAA Keys match the keys in device
63 63  
64 64  
68 +
65 65  = 2. Notice of US915/CN470/AU915 Frequency band =
66 66  
71 +
67 67  (((
68 68  If user has problem to work with lorawan server in band US915/AU915/CN470, he can check:
69 69  )))
... ... @@ -102,14 +102,18 @@
102 102  
103 103  US915 Channels
104 104  
110 +
105 105  [[image:image-20220526163926-7.png]]
106 106  
107 107  AU915 Channels
108 108  
115 +
109 109  [[image:image-20220526163941-8.png]]
110 110  
111 111  (((
112 112  CN470 Channels
120 +
121 +
113 113  )))
114 114  
115 115  (((
... ... @@ -120,6 +120,8 @@
120 120  
121 121  (((
122 122  TTN FREQUENCY PLAN
132 +
133 +
123 123  )))
124 124  
125 125  (((
... ... @@ -127,8 +127,10 @@
127 127  )))
128 128  
129 129  
141 +
130 130  = 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
131 131  
144 +
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.
... ... @@ -148,8 +148,10 @@
148 148  )))
149 149  
150 150  
164 +
151 151  = 4. Transmision on ABP Mode =
152 152  
167 +
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  )))
... ... @@ -175,10 +175,12 @@
175 175  Disable Frame Counter Check in ABP Mode
176 176  
177 177  
193 +
178 178  = 5. Downstream Debug =
179 179  
180 180  == 5.1 How it work ==
181 181  
198 +
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]]
205 +[[image:image-20220531161828-1.png]]
189 189  
190 190  receive windows for Class A and Class C
191 191  
209 +
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,14 @@
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.**
216 +* 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 200  
201 201  == 5.2 See Debug Info ==
202 202  
221 +
203 203  (((
204 -**For LoRaWAN Server**
223 +(% style="color:blue" %)**For LoRaWAN Server**
205 205  )))
206 206  
207 207  (((
... ... @@ -230,8 +230,9 @@
230 230  )))
231 231  
232 232  
252 +
233 233  (((
234 -**For LoRaWAN Gateway**
254 +(% style="color:blue" %)**For LoRaWAN Gateway**
235 235  )))
236 236  
237 237  (((
... ... @@ -245,8 +245,9 @@
245 245  )))
246 246  
247 247  
268 +
248 248  (((
249 -**For End Node**
270 +(% style="color:blue" %)**For End Node**
250 250  )))
251 251  
252 252  (((
... ... @@ -254,23 +254,19 @@
254 254  )))
255 255  
256 256  (((
278 +(% style="color:#037691" %)**AT+RX2FQ=869525000**  (%%) **~-~-->**  The RX2 Window frequency
279 +(% style="color:#037691" %)**AT+RX2DR=3**          (%%) **~-~-->**  The RX2 DataRate
280 +(% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
281 +(% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
282 +
283 +
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
288 +(% 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
... ... @@ -281,10 +281,12 @@
281 281  
282 282  (((
283 283  
301 +
302 +
284 284  )))
285 285  
286 286  (((
287 -**Another message:**
306 +(% 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 ==
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:**
322 +== 5.3 If problem doesn't solve ==
305 305  
324 +
325 +(% 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:**
326 +
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  
314 314  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
315 315  
335 +
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  )))
... ... @@ -336,37 +336,34 @@
336 336  )))
337 337  
338 338  
359 +
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 -)))
363 +(% style="color:blue" %)**1. LHT65 End device configure:**
347 347  
348 -(% class="box infomessage" %)
349 -(((
350 -Change to fix frequency: AT+CHS=904900000
351 -)))
365 +**Change to ABP Mode:  AT+NJM=0**
366 +**Change to fix frequency:  AT+CHS=904900000**
367 +**Change to fix DR:  AT+DR=0**
352 352  
353 -(% class="box infomessage" %)
354 -(((
355 -Change to fix DR: AT+DR=0
356 -)))
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"]]
370 +[[image:image-20220526165525-16.png]]
359 359  
360 -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"]]
363 363  
374 +(% style="color:blue" %)**2. In LG02 , configure to receive above message**
375 +
376 +[[image:image-20220526165612-17.png]]
377 +
378 +
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"]]
381 +[[image:image-20220526171112-21.png]]
367 367  
368 -3. Decode the info in web
369 369  
384 +
385 +(% style="color:blue" %)**3. Decode the info in web**
386 +
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:
... ... @@ -377,9 +377,10 @@
377 377  
378 378  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
379 379  
397 +
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"]]
400 +[[image:image-20220526171029-20.png]]
383 383  
384 384  (((
385 385   The FRMPayload is the device payload.
... ... @@ -386,14 +386,19 @@
386 386  )))
387 387  
388 388  
407 +
389 389  = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
390 390  
410 +
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  
413 +
414 +
393 393  = 9. Why do I see a "MIC Mismatch" error message from the server? =
394 394  
417 +
395 395  (((
396 -1)If the user receives a "MIC Mismatch" message after registering the node on the server.
419 +1)  If the user receives a "MIC Mismatch" message after registering the node on the server.
397 397  )))
398 398  
399 399  (((
... ... @@ -415,60 +415,124 @@
415 415  * (((
416 416  If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
417 417  
441 +
442 +
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 -)))
449 +**Why this happen:**
428 428  
429 -(((
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 -)))
451 +For US915, AU915 or AS923 frequencies.It is possible because: .
432 432  
433 -* (((
434 -Solution: Use the decoder to filter out this 00 packet.
435 -)))
436 -* (((
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]]
453 +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  
455 +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.
439 439  
440 -
441 -)))
442 442  
458 +**How to solve:**
459 +
460 +Solution: Use the decoder to filter out this 0x00 packet.
461 +
462 +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]]
463 +
464 +
465 +
443 443  = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
444 444  
468 +
469 +(((
445 445  It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
471 +)))
446 446  
473 +(((
447 447  AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
475 +)))
448 448  
477 +(((
449 449  AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
479 +)))
450 450  
481 +(((
451 451  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
483 +)))
452 452  
485 +(((
453 453  AT+APPEUI=00 00 00 00 00 00 00 00
487 +)))
454 454  
489 +(((
490 +
491 +)))
455 455  
493 +(((
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.
495 +)))
457 457  
497 +(((
458 458  You can rewrites the keys by running commands in AT Console
459 459  
460 -For example：
500 +
501 +)))
461 461  
503 +(((
504 +**For example：**
505 +)))
506 +
507 +(((
462 462  AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
509 +)))
463 463  
511 +(((
464 464  AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
513 +)))
465 465  
515 +(((
466 466  AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
517 +)))
467 467  
519 +(((
468 468  AT+APPEUI=2C 45 47 E3 24 12 23 24
521 +)))
469 469  
523 +(((
470 470  (Any combination of 16 bit codes can be used）
471 471  
472 472  
527 +
528 += 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
529 +)))
530 +
531 +
532 +Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
533 +
534 +
535 += 13. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
536 +
537 +
538 +In US915, AU915 or CN470 frequency band, there are 8 subbands, totally 72 channels. and LoRaWAN server normally use only one sub-band, for example Subband 2 in TTN. The gateway also configured to Subband 2 and cover eight channels in this subband. If the end node transfer data in Subband 2, it will reach to gateway and to the LoRaWAN server. If the end node transfer packets in other subbands, for example subband 1, the packet won't arrive both gateway or LoRaWAN server.
539 +
540 +
541 +In Dragino Sensors old version firmware (before early 2022), the subband is fixed the subband to 2 , but this cause a problem, the end node is hard to use in other subband and need program. So the new logic is as below:
542 +
543 +We have improved this, the end node will use frequency 1 from sub-band1, then frequency 1 from sub-band2, then frequency 1 from sub-band3, etc to process the OTAA join, In this case, In this case, the end node can support LoRaWAN servers with different subbands. To make sure the end node will only transmit the proper sub-band after OTAA Joined successfully, the end node will:
544 +
545 +* (((
546 +Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
547 +)))
548 +* (((
549 +Use the Join successful sub-band if the server doesn't include subband info in the OTAA Join Accept message ( TTN v2 doesn't include)
550 +)))
551 +
552 +This change will make the activation time a littler longer but make sure the device can be used in any subband.
553 +
554 +
555 +Below is a photo to show why it takes longer time for OTAA Join. We can see in 72 channels mode, why it takes more time to join success. If users want to have faster OTAA Join success, he can change default CHE to the subband he use.
556 +
557 +
558 +[[image:image-20221215223215-1.png||height="584" width="1280"]]
559 +
473 473  (% class="wikigeneratedid" %)
474 474  
image-20220526164956-15.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +634.4 KB
Content
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
image-20221215223215-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +183.6 KB
Content

Applications

Navigation

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