Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 22.1 >
edited by Xiaoling
on 2022/05/26 16:47
To version < 33.1 >
edited by Edwin Chen
on 2022/10/19 23:11
>
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,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**
41 +(% 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**
52 +(% 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  
65 +
65 65  = 2. Notice of US915/CN470/AU915 Frequency band =
66 66  
68 +
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  
111 +
109 109  [[image:image-20220526163941-8.png]]
110 110  
111 111  (((
112 112  CN470 Channels
116 +
117 +
113 113  )))
114 114  
115 115  (((
... ... @@ -120,6 +120,8 @@
120 120  
121 121  (((
122 122  TTN FREQUENCY PLAN
128 +
129 +
123 123  )))
124 124  
125 125  (((
... ... @@ -127,8 +127,10 @@
127 127  )))
128 128  
129 129  
137 +
130 130  = 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
131 131  
140 +
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  
160 +
151 151  = 4. Transmision on ABP Mode =
152 152  
163 +
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  
189 +
178 178  = 5. Downstream Debug =
179 179  
180 180  == 5.1 How it work ==
181 181  
194 +
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]]
201 +[[image:image-20220531161828-1.png]]
189 189  
190 190  receive windows for Class A and Class C
191 191  
205 +
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,15 @@
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.**
212 +* 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  
214 +
215 +
200 200  == 5.2 See Debug Info ==
201 201  
218 +
202 202  (((
203 -**For LoRaWAN Server**
220 +(% style="color:blue" %)**For LoRaWAN Server**
204 204  )))
205 205  
206 206  (((
... ... @@ -211,7 +211,7 @@
211 211  Configure a downstream to the end device
212 212  )))
213 213  
214 -[[image:https://wiki.dragino.com/images/thumb/8/82/Downstream_debug_1.png/600px-Downstream_debug_1.png||height="217" width="600"]]
231 +[[image:image-20220526164623-12.png]]
215 215  
216 216  (((
217 217  Set a downstream in TTN and see it is sent
... ... @@ -222,7 +222,7 @@
222 222  This downstream info will then pass to the gateway downstream list. and include the DR which is used (SF9BW125) in EU868 is DR3
223 223  )))
224 224  
225 -[[image:https://wiki.dragino.com/images/thumb/d/dc/Downstream_debug_2.png/600px-Downstream_debug_2.png||height="245" width="600"]]
242 +[[image:image-20220526164650-13.png]]
226 226  
227 227  (((
228 228  Gateway Traffic can see this downstream info
... ... @@ -229,8 +229,9 @@
229 229  )))
230 230  
231 231  
249 +
232 232  (((
233 -**For LoRaWAN Gateway**
251 +(% style="color:blue" %)**For LoRaWAN Gateway**
234 234  )))
235 235  
236 236  (((
... ... @@ -237,7 +237,7 @@
237 237  When the downstream packet appear on the traffic of Gateway page. The LoRaWAN gateway can get it from LoRaWAN server and transmit it. In Dragion Gateway, this can be checked by runinng "logread -f" in the SSH console. and see below:
238 238  )))
239 239  
240 -[[image:https://wiki.dragino.com/images/thumb/2/21/Downstream_debug_3.png/600px-Downstream_debug_3.png||height="195" width="600"]]
258 +[[image:image-20220526164734-14.png]]
241 241  
242 242  (((
243 243  Gateway Sent out this packet
... ... @@ -244,8 +244,9 @@
244 244  )))
245 245  
246 246  
265 +
247 247  (((
248 -**For End Node**
267 +(% style="color:blue" %)**For End Node**
249 249  )))
250 250  
251 251  (((
... ... @@ -253,23 +253,19 @@
253 253  )))
254 254  
255 255  (((
275 +(% style="color:#037691" %)**AT+RX2FQ=869525000**  (%%) **~-~-->**  The RX2 Window frequency
276 +(% style="color:#037691" %)**AT+RX2DR=3**          (%%) **~-~-->**  The RX2 DataRate
277 +(% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
278 +(% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
279 +
280 +
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
285 +(% 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  
298 +
299 +
283 283  )))
284 284  
285 285  (((
286 -**Another message:**
303 +(% style="color:blue" %)**Another message:**
287 287  )))
288 288  
289 289  {{{ [12502]***** UpLinkCounter= 0 *****
... ... @@ -297,17 +297,23 @@
297 297   Receive data
298 298   1:0012345678}}}
299 299  
300 -== 5.3 If problem doesn’t solve ==
301 301  
302 -**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:**
303 303  
319 +== 5.3 If problem doesn't solve ==
320 +
321 +
322 +(% 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:**
323 +
304 304  * End node console to show the transmit freuqency and DR.
305 305  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server.
306 306  * Gateway traffic (from server UI) to shows the data exchange between gateway and server.
307 307  * End Node traffic (from server UI) to shows end node activity in server.
308 308  
329 +
330 +
309 309  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
310 310  
333 +
311 311  (((
312 312  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.
313 313  )))
... ... @@ -331,37 +331,34 @@
331 331  )))
332 332  
333 333  
357 +
334 334  = 7. Decrypt a LoRaWAN Packet =
335 335  
336 -~1. LHT65 End device configure:
337 337  
338 -(% class="box infomessage" %)
339 -(((
340 -Change to ABP Mode: AT+NJM=0
341 -)))
361 +(% style="color:blue" %)**1. LHT65 End device configure:**
342 342  
343 -(% class="box infomessage" %)
344 -(((
345 -Change to fix frequency: AT+CHS=904900000
346 -)))
363 +**Change to ABP Mode:  AT+NJM=0**
364 +**Change to fix frequency:  AT+CHS=904900000**
365 +**Change to fix DR:  AT+DR=0**
347 347  
348 -(% class="box infomessage" %)
349 -(((
350 -Change to fix DR: AT+DR=0
351 -)))
352 352  
353 -[[image:https://wiki.dragino.com/images/e/e6/Decrypt_a_LoRaWAN_Packet1.jpg||alt="Decrypt a LoRaWAN Packet1.jpg" height="607" width="558"]]
368 +[[image:image-20220526165525-16.png]]
354 354  
355 -2. In LG02 , configure to receive above message
356 356  
357 -[[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  
372 +(% style="color:blue" %)**2. In LG02 , configure to receive above message**
373 +
374 +[[image:image-20220526165612-17.png]]
375 +
376 +
359 359  In LG02 console, we can see the hex receive are:
360 360  
361 -[[image:https://wiki.dragino.com/images/f/f1/Decrypt_a_LoRaWAN_Packet3.jpg||alt="Decrypt a LoRaWAN Packet3.jpg" height="179" width="558"]]
379 +[[image:image-20220526171112-21.png]]
362 362  
363 -3. Decode the info in web
364 364  
382 +
383 +(% style="color:blue" %)**3. Decode the info in web**
384 +
365 365  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
366 366  
367 367  Need these three fields:
... ... @@ -372,9 +372,10 @@
372 372  
373 373  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
374 374  
395 +
375 375  [[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]]
376 376  
377 -[[image:https://wiki.dragino.com/images/7/77/Decrypt_a_LoRaWAN_Packet4.png||alt="Decrypt a LoRaWAN Packet4.png" height="390" width="558"]]
398 +[[image:image-20220526171029-20.png]]
378 378  
379 379  (((
380 380   The FRMPayload is the device payload.
... ... @@ -381,14 +381,19 @@
381 381  )))
382 382  
383 383  
405 +
384 384  = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
385 385  
408 +
386 386  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.
387 387  
411 +
412 +
388 388  = 9. Why do I see a "MIC Mismatch" error message from the server? =
389 389  
415 +
390 390  (((
391 -1)If the user receives a "MIC Mismatch" message after registering the node on the server.
417 +1)  If the user receives a "MIC Mismatch" message after registering the node on the server.
392 392  )))
393 393  
394 394  (((
... ... @@ -410,58 +410,95 @@
410 410  * (((
411 411  If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
412 412  
439 +
440 +
413 413  
414 414  )))
415 415  
416 416  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
417 417  
418 -* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
419 419  
420 -(((
421 -When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
422 -)))
447 +* If you are using US915, AU915 or AS923 frequencies.It is possible because: .
423 423  
424 -(((
449 +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.
450 +
425 425  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.
426 -)))
427 427  
428 -* (((
429 429  Solution: Use the decoder to filter out this 00 packet.
430 -)))
431 -* (((
454 +
432 432  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]]
433 433  
434 434  
435 -
436 -)))
437 437  
438 438  = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
439 439  
461 +
462 +(((
440 440  It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
464 +)))
441 441  
466 +(((
442 442  AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
468 +)))
443 443  
470 +(((
444 444  AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
472 +)))
445 445  
474 +(((
446 446  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
476 +)))
447 447  
478 +(((
448 448  AT+APPEUI=00 00 00 00 00 00 00 00
480 +)))
449 449  
482 +(((
483 +
484 +)))
450 450  
486 +(((
451 451  You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number.
488 +)))
452 452  
490 +(((
453 453  You can rewrites the keys by running commands in AT Console
454 454  
455 -For example：
493 +
494 +)))
456 456  
496 +(((
497 +**For example：**
498 +)))
499 +
500 +(((
457 457  AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
502 +)))
458 458  
504 +(((
459 459  AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
506 +)))
460 460  
508 +(((
461 461  AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
510 +)))
462 462  
512 +(((
463 463  AT+APPEUI=2C 45 47 E3 24 12 23 24
514 +)))
464 464  
516 +(((
465 465  (Any combination of 16 bit codes can be used）
466 466  
467 467  
520 +
521 += 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
522 +)))
523 +
524 +
525 +Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
526 +
527 +
528 +
529 +(% class="wikigeneratedid" %)
530 +
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

Applications

Navigation

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