Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 29.2 >
edited by Xiaoling
on 2022/05/26 17:11
To version < 34.1 >
edited by Edwin Chen
on 2022/10/19 23:14
>
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,7 +18,7 @@
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:**
19 +(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
22 22  
23 23  * If the device is sending join request to server?
24 24  * What frequency the device is sending?
... ... @@ -28,8 +28,9 @@
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  
30 +(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
31 +
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,7 +38,7 @@
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**
40 +(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
42 42  
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.
... ... @@ -49,7 +49,7 @@
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**
51 +(% style="color:blue" %)**4. Data Page in LoRaWAN server**
53 53  
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  
... ... @@ -62,8 +62,10 @@
62 62  Check if OTAA Keys match the keys in device
63 63  
64 64  
64 +
65 65  = 2. Notice of US915/CN470/AU915 Frequency band =
66 66  
67 +
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  
110 +
109 109  [[image:image-20220526163941-8.png]]
110 110  
111 111  (((
112 112  CN470 Channels
115 +
116 +
113 113  )))
114 114  
115 115  (((
... ... @@ -120,6 +120,8 @@
120 120  
121 121  (((
122 122  TTN FREQUENCY PLAN
127 +
128 +
123 123  )))
124 124  
125 125  (((
... ... @@ -127,8 +127,10 @@
127 127  )))
128 128  
129 129  
136 +
130 130  = 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
131 131  
139 +
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  
159 +
151 151  = 4. Transmision on ABP Mode =
152 152  
162 +
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  
188 +
178 178  = 5. Downstream Debug =
179 179  
180 180  == 5.1 How it work ==
181 181  
193 +
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]]
200 +[[image:image-20220531161828-1.png]]
189 189  
190 190  receive windows for Class A and Class C
191 191  
204 +
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,12 +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.**
211 +* 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  
213 +
200 200  == 5.2 See Debug Info ==
201 201  
216 +
202 202  (((
203 -**For LoRaWAN Server**
218 +(% style="color:blue" %)**For LoRaWAN Server**
204 204  )))
205 205  
206 206  (((
... ... @@ -229,8 +229,9 @@
229 229  )))
230 230  
231 231  
247 +
232 232  (((
233 -**For LoRaWAN Gateway**
249 +(% style="color:blue" %)**For LoRaWAN Gateway**
234 234  )))
235 235  
236 236  (((
... ... @@ -244,8 +244,9 @@
244 244  )))
245 245  
246 246  
263 +
247 247  (((
248 -**For End Node**
265 +(% style="color:blue" %)**For End Node**
249 249  )))
250 250  
251 251  (((
... ... @@ -253,23 +253,19 @@
253 253  )))
254 254  
255 255  (((
273 +(% style="color:#037691" %)**AT+RX2FQ=869525000**  (%%) **~-~-->**  The RX2 Window frequency
274 +(% style="color:#037691" %)**AT+RX2DR=3**          (%%) **~-~-->**  The RX2 DataRate
275 +(% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
276 +(% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
277 +
278 +
256 256  
257 257  )))
258 258  
259 259  (((
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
283 +(% style="color:blue" %)**when the device running, we can see below info:**
266 266  )))
267 -)))
268 268  
269 -(((
270 -**when the device running, we can see below info:**
271 -)))
272 -
273 273  {{{ [12502]***** UpLinkCounter= 0 *****
274 274   [12503]TX on freq 868500000 Hz at DR 0
275 275   [13992]txDone
... ... @@ -280,10 +280,12 @@
280 280  
281 281  (((
282 282  
296 +
297 +
283 283  )))
284 284  
285 285  (((
286 -**Another message:**
301 +(% style="color:blue" %)**Another message:**
287 287  )))
288 288  
289 289  {{{ [12502]***** UpLinkCounter= 0 *****
... ... @@ -298,8 +298,10 @@
298 298   1:0012345678}}}
299 299  
300 300  
301 -== 5.3 If problem doesn’t solve ==
302 302  
317 +== 5.3 If problem doesn't solve ==
318 +
319 +
303 303  (% 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:**
304 304  
305 305  * End node console to show the transmit freuqency and DR.
... ... @@ -307,8 +307,10 @@
307 307  * Gateway traffic (from server UI) to shows the data exchange between gateway and server.
308 308  * End Node traffic (from server UI) to shows end node activity in server.
309 309  
327 +
310 310  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
311 311  
330 +
312 312  (((
313 313  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.
314 314  )))
... ... @@ -332,30 +332,23 @@
332 332  )))
333 333  
334 334  
354 +
335 335  = 7. Decrypt a LoRaWAN Packet =
336 336  
337 -~1. LHT65 End device configure:
338 338  
339 -(% class="box infomessage" %)
340 -(((
341 -**Change to ABP Mode: AT+NJM=0**
342 -)))
358 +(% style="color:blue" %)**1. LHT65 End device configure:**
343 343  
344 -(% class="box infomessage" %)
345 -(((
346 -**Change to fix frequency: AT+CHS=904900000**
347 -)))
360 +**Change to ABP Mode:  AT+NJM=0**
361 +**Change to fix frequency:  AT+CHS=904900000**
362 +**Change to fix DR:  AT+DR=0**
348 348  
349 -(% class="box infomessage" %)
350 -(((
351 -**Change to fix DR: AT+DR=0**
352 -)))
353 353  
354 354  [[image:image-20220526165525-16.png]]
355 355  
356 356  
357 -2. In LG02 , configure to receive above message
358 358  
369 +(% style="color:blue" %)**2. In LG02 , configure to receive above message**
370 +
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  
380 +(% style="color:blue" %)**3. Decode the info in web**
381 +
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  
392 +
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,14 +385,19 @@
385 385  )))
386 386  
387 387  
402 +
388 388  = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
389 389  
405 +
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  
408 +
409 +
392 392  = 9. Why do I see a "MIC Mismatch" error message from the server? =
393 393  
412 +
394 394  (((
395 -1)If the user receives a "MIC Mismatch" message after registering the node on the server.
414 +1)  If the user receives a "MIC Mismatch" message after registering the node on the server.
396 396  )))
397 397  
398 398  (((
... ... @@ -414,58 +414,95 @@
414 414  * (((
415 415  If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
416 416  
436 +
437 +
417 417  
418 418  )))
419 419  
420 420  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
421 421  
422 -* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
423 423  
424 -(((
425 -When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
426 -)))
444 +For US915, AU915 or AS923 frequencies.It is possible because: .
427 427  
428 -(((
429 -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.
430 -)))
446 +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.
431 431  
432 -* (((
448 +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.
449 +
433 433  Solution: Use the decoder to filter out this 00 packet.
434 -)))
435 -* (((
436 -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]]
437 437  
452 +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]]
438 438  
439 -
440 -)))
441 441  
455 +
442 442  = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
443 443  
458 +
459 +(((
444 444  It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
461 +)))
445 445  
463 +(((
446 446  AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
465 +)))
447 447  
467 +(((
448 448  AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
469 +)))
449 449  
471 +(((
450 450  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
473 +)))
451 451  
475 +(((
452 452  AT+APPEUI=00 00 00 00 00 00 00 00
477 +)))
453 453  
479 +(((
480 +
481 +)))
454 454  
483 +(((
455 455  You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number.
485 +)))
456 456  
487 +(((
457 457  You can rewrites the keys by running commands in AT Console
458 458  
459 -For example：
490 +
491 +)))
460 460  
493 +(((
494 +**For example：**
495 +)))
496 +
497 +(((
461 461  AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
499 +)))
462 462  
501 +(((
463 463  AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
503 +)))
464 464  
505 +(((
465 465  AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
507 +)))
466 466  
509 +(((
467 467  AT+APPEUI=2C 45 47 E3 24 12 23 24
511 +)))
468 468  
513 +(((
469 469  (Any combination of 16 bit codes can be used）
470 470  
471 471  
517 +
518 += 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
519 +)))
520 +
521 +
522 +Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
523 +
524 +
525 +
526 +(% class="wikigeneratedid" %)
527 +
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