Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 29.3 >
edited by Xiaoling
on 2022/05/26 17:11
To version < 32.9 >
edited by Xiaoling
on 2022/07/13 15:13
>
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  
... ... @@ -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,12 +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 200  == 5.2 See Debug Info ==
201 201  
210 +
202 202  (((
203 -**For LoRaWAN Server**
212 +(% style="color:blue" %)**For LoRaWAN Server**
204 204  )))
205 205  
206 206  (((
... ... @@ -230,7 +230,7 @@
230 230  
231 231  
232 232  (((
233 -**For LoRaWAN Gateway**
242 +(% style="color:blue" %)**For LoRaWAN Gateway**
234 234  )))
235 235  
236 236  (((
... ... @@ -245,7 +245,7 @@
245 245  
246 246  
247 247  (((
248 -**For End Node**
257 +(% style="color:blue" %)**For End Node**
249 249  )))
250 250  
251 251  (((
... ... @@ -253,23 +253,18 @@
253 253  )))
254 254  
255 255  (((
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 +
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
274 +(% 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
... ... @@ -283,7 +283,7 @@
283 283  )))
284 284  
285 285  (((
286 -**Another message:**
290 +(% style="color:blue" %)**Another message:**
287 287  )))
288 288  
289 289  {{{ [12502]***** UpLinkCounter= 0 *****
... ... @@ -298,8 +298,9 @@
298 298   1:0012345678}}}
299 299  
300 300  
301 -== 5.3 If problem doesn’t solve ==
305 +== 5.3 If problem doesn't solve ==
302 302  
307 +
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,11 @@
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  
315 +
316 +
310 310  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
311 311  
319 +
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  )))
... ... @@ -334,27 +334,17 @@
334 334  
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 -)))
346 +(% style="color:blue" %)**1. LHT65 End device configure:**
343 343  
344 -(% class="box infomessage" %)
345 -(((
346 -**Change to fix frequency: AT+CHS=904900000**
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**
348 348  
349 -(% class="box infomessage" %)
350 -(((
351 -**Change to fix DR: AT+DR=0**
352 -)))
353 -
354 354  [[image:image-20220526165525-16.png]]
355 355  
356 356  
357 -2. In LG02 , configure to receive above message
355 +(% style="color:blue" %)**2. In LG02 , configure to receive above message**
358 358  
359 359  [[image:image-20220526165612-17.png]]
360 360  
... ... @@ -364,7 +364,7 @@
364 364  [[image:image-20220526171112-21.png]]
365 365  
366 366  
367 -3. Decode the info in web
365 +(% style="color:blue" %)**3. Decode the info in web**
368 368  
369 369  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
370 370  
... ... @@ -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  
377 +
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]]
... ... @@ -387,13 +387,15 @@
387 387  
388 388  = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
389 389  
389 +
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  
392 392  
393 393  = 9. Why do I see a "MIC Mismatch" error message from the server? =
394 394  
395 +
395 395  (((
396 -1)If the user receives a "MIC Mismatch" message after registering the node on the server.
397 +1)  If the user receives a "MIC Mismatch" message after registering the node on the server.
397 397  )))
398 398  
399 399  (((
... ... @@ -415,11 +415,14 @@
415 415  * (((
416 416  If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
417 417  
419 +
420 +
418 418  
419 419  )))
420 420  
421 421  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
422 422  
426 +
423 423  * If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
424 424  
425 425  (((
... ... @@ -437,38 +437,78 @@
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 439  
444 +
440 440  
441 441  )))
442 442  
443 443  = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
444 444  
450 +
451 +(((
445 445  It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
453 +)))
446 446  
455 +(((
447 447  AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
457 +)))
448 448  
459 +(((
449 449  AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
461 +)))
450 450  
463 +(((
451 451  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
465 +)))
452 452  
467 +(((
453 453  AT+APPEUI=00 00 00 00 00 00 00 00
469 +)))
454 454  
471 +(((
472 +
473 +)))
455 455  
475 +(((
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.
477 +)))
457 457  
479 +(((
458 458  You can rewrites the keys by running commands in AT Console
459 459  
460 -For example：
482 +
483 +)))
461 461  
485 +(((
486 +**For example：**
487 +)))
488 +
489 +(((
462 462  AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
491 +)))
463 463  
493 +(((
464 464  AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
495 +)))
465 465  
497 +(((
466 466  AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
499 +)))
467 467  
501 +(((
468 468  AT+APPEUI=2C 45 47 E3 24 12 23 24
503 +)))
469 469  
505 +(((
470 470  (Any combination of 16 bit codes can be used）
471 471  
472 472  
509 += 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
510 +)))
511 +
512 +
513 +Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
514 +
515 +
516 +
473 473  (% class="wikigeneratedid" %)
474 474  
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