Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 33.1 >
edited by Edwin Chen
on 2022/10/19 23:11
To version < 30.2 >
edited by Xiaoling
on 2022/05/30 10:57
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.Xiaoling
Content
... ... @@ -1,4 +1,4 @@
1 -**~ Table of Contents:**
1 +**~ Contents:**
2 2  
3 3  {{toc/}}
4 4  
... ... @@ -6,7 +6,6 @@
6 6  
7 7  = 1. OTAA Join Process Debug =
8 8  
9 -
10 10  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.
11 11  \\**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:**
12 12  
... ... @@ -16,9 +16,8 @@
16 16  * End Node traffic (from server UI) to shows end node activity in server. (Normaly possible)
17 17  * 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)
18 18  
18 +**~1. End Device Join Screen shot, we can check:**
19 19  
20 -(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
21 -
22 22  * If the device is sending join request to server?
23 23  * What frequency the device is sending?
24 24  
... ... @@ -27,9 +27,8 @@
27 27  Console Output from End device to see the transmit frequency
28 28  
29 29  
28 +**2. Gateway packet traffic in gateway web or ssh. we can check:**
30 30  
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 -(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
38 +**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 -(% style="color:blue" %)**4. Data Page in LoRaWAN server**
49 +**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,10 +62,8 @@
62 62  Check if OTAA Keys match the keys in device
63 63  
64 64  
65 -
66 66  = 2. Notice of US915/CN470/AU915 Frequency band =
67 67  
68 -
69 69  (((
70 70  If user has problem to work with lorawan server in band US915/AU915/CN470, he can check:
71 71  )))
... ... @@ -108,13 +108,10 @@
108 108  
109 109  AU915 Channels
110 110  
111 -
112 112  [[image:image-20220526163941-8.png]]
113 113  
114 114  (((
115 115  CN470 Channels
116 -
117 -
118 118  )))
119 119  
120 120  (((
... ... @@ -125,8 +125,6 @@
125 125  
126 126  (((
127 127  TTN FREQUENCY PLAN
128 -
129 -
130 130  )))
131 131  
132 132  (((
... ... @@ -134,10 +134,8 @@
134 134  )))
135 135  
136 136  
137 -
138 138  = 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
139 139  
140 -
141 141  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:
142 142  
143 143  * **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.
... ... @@ -157,10 +157,8 @@
157 157  )))
158 158  
159 159  
160 -
161 161  = 4. Transmision on ABP Mode =
162 162  
163 -
164 164  (((
165 165  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.
166 166  )))
... ... @@ -186,12 +186,10 @@
186 186  Disable Frame Counter Check in ABP Mode
187 187  
188 188  
189 -
190 190  = 5. Downstream Debug =
191 191  
192 192  == 5.1 How it work ==
193 193  
194 -
195 195  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.
196 196  
197 197  (((
... ... @@ -198,11 +198,10 @@
198 198  Depends on Class A or Class C, the receive windows will be a little difference,
199 199  )))
200 200  
201 -[[image:image-20220531161828-1.png]]
185 +[[image:image-20220526164547-11.png]]
202 202  
203 203  receive windows for Class A and Class C
204 204  
205 -
206 206  Below are the requirement for the End Device to receive the packets.
207 207  
208 208  * The End Device must open the receive windows: RX1 or RX2
... ... @@ -209,15 +209,14 @@
209 209  * The LoRaWAN server must send a downstream packet, and the gateway forward this downstream packet for this end node.
210 210  * This downstream packet must arrive to the end node while RX1 or RX2 is open.
211 211  * This packet must match the frequency of the RX1 or RX2 window.
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.**
195 +* 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.**
213 213  
214 214  
215 215  
216 216  == 5.2 See Debug Info ==
217 217  
218 -
219 219  (((
220 -(% style="color:blue" %)**For LoRaWAN Server**
202 +**For LoRaWAN Server**
221 221  )))
222 222  
223 223  (((
... ... @@ -246,9 +246,8 @@
246 246  )))
247 247  
248 248  
249 -
250 250  (((
251 -(% style="color:blue" %)**For LoRaWAN Gateway**
232 +**For LoRaWAN Gateway**
252 252  )))
253 253  
254 254  (((
... ... @@ -262,9 +262,8 @@
262 262  )))
263 263  
264 264  
265 -
266 266  (((
267 -(% style="color:blue" %)**For End Node**
247 +**For End Node**
268 268  )))
269 269  
270 270  (((
... ... @@ -272,19 +272,23 @@
272 272  )))
273 273  
274 274  (((
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 -
281 281  
282 282  )))
283 283  
284 284  (((
285 -(% style="color:blue" %)**when the device running, we can see below info:**
259 +(% class="box infomessage" %)
260 +(((
261 +AT+RX2FQ=869525000     ~-~--> The RX2 Window frequency
262 +AT+RX2DR=3      ~-~--> The RX2 DataRate
263 +AT+RX1DL=1000   ~-~--> Receive Delay 1
264 +AT+RX2DL=2000   ~-~--> Receive Delay 2
286 286  )))
266 +)))
287 287  
268 +(((
269 +**when the device running, we can see below info:**
270 +)))
271 +
288 288  {{{ [12502]***** UpLinkCounter= 0 *****
289 289   [12503]TX on freq 868500000 Hz at DR 0
290 290   [13992]txDone
... ... @@ -295,12 +295,10 @@
295 295  
296 296  (((
297 297  
298 -
299 -
300 300  )))
301 301  
302 302  (((
303 -(% style="color:blue" %)**Another message:**
285 +**Another message:**
304 304  )))
305 305  
306 306  {{{ [12502]***** UpLinkCounter= 0 *****
... ... @@ -315,10 +315,8 @@
315 315   1:0012345678}}}
316 316  
317 317  
300 +== 5.3 If problem doesn’t solve ==
318 318  
319 -== 5.3 If problem doesn't solve ==
320 -
321 -
322 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 323  
324 324  * End node console to show the transmit freuqency and DR.
... ... @@ -326,11 +326,8 @@
326 326  * Gateway traffic (from server UI) to shows the data exchange between gateway and server.
327 327  * End Node traffic (from server UI) to shows end node activity in server.
328 328  
329 -
330 -
331 331  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
332 332  
333 -
334 334  (((
335 335  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.
336 336  )))
... ... @@ -354,23 +354,30 @@
354 354  )))
355 355  
356 356  
357 -
358 358  = 7. Decrypt a LoRaWAN Packet =
359 359  
336 +~1. LHT65 End device configure:
360 360  
361 -(% style="color:blue" %)**1. LHT65 End device configure:**
338 +(% class="box infomessage" %)
339 +(((
340 +**Change to ABP Mode: AT+NJM=0**
341 +)))
362 362  
363 -**Change to ABP Mode:  AT+NJM=0**
364 -**Change to fix frequency:  AT+CHS=904900000**
365 -**Change to fix DR:  AT+DR=0**
343 +(% class="box infomessage" %)
344 +(((
345 +**Change to fix frequency: AT+CHS=904900000**
346 +)))
366 366  
348 +(% class="box infomessage" %)
349 +(((
350 +**Change to fix DR: AT+DR=0**
351 +)))
367 367  
368 368  [[image:image-20220526165525-16.png]]
369 369  
370 370  
356 +2. In LG02 , configure to receive above message
371 371  
372 -(% style="color:blue" %)**2. In LG02 , configure to receive above message**
373 -
374 374  [[image:image-20220526165612-17.png]]
375 375  
376 376  
... ... @@ -379,9 +379,8 @@
379 379  [[image:image-20220526171112-21.png]]
380 380  
381 381  
366 +3. Decode the info in web
382 382  
383 -(% style="color:blue" %)**3. Decode the info in web**
384 -
385 385  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
386 386  
387 387  Need these three fields:
... ... @@ -392,7 +392,6 @@
392 392  
393 393  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
394 394  
395 -
396 396  [[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]]
397 397  
398 398  [[image:image-20220526171029-20.png]]
... ... @@ -402,19 +402,15 @@
402 402  )))
403 403  
404 404  
405 -
406 406  = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
407 407  
408 -
409 409  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.
410 410  
411 411  
412 -
413 413  = 9. Why do I see a "MIC Mismatch" error message from the server? =
414 414  
415 -
416 416  (((
417 -1)  If the user receives a "MIC Mismatch" message after registering the node on the server.
395 +1)If the user receives a "MIC Mismatch" message after registering the node on the server.
418 418  )))
419 419  
420 420  (((
... ... @@ -436,29 +436,33 @@
436 436  * (((
437 437  If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
438 438  
439 -
440 -
441 441  
442 442  )))
443 443  
444 444  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
445 445  
422 +* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
446 446  
447 -* If you are using US915, AU915 or AS923 frequencies.It is possible because: .
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 +)))
448 448  
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 -
428 +(((
451 451  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 +)))
452 452  
432 +* (((
453 453  Solution: Use the decoder to filter out this 00 packet.
454 -
434 +)))
435 +* (((
455 455  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]]
456 456  
457 457  
439 +
440 +)))
458 458  
459 459  = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
460 460  
461 -
462 462  (((
463 463  It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
464 464  )))
... ... @@ -489,8 +489,6 @@
489 489  
490 490  (((
491 491  You can rewrites the keys by running commands in AT Console
492 -
493 -
494 494  )))
495 495  
496 496  (((
... ... @@ -515,16 +515,8 @@
515 515  
516 516  (((
517 517  (Any combination of 16 bit codes can be used）
518 -
519 -
520 -
521 -= 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
522 522  )))
523 523  
524 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 529  (% class="wikigeneratedid" %)
530 530  
image-20220531161828-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -98.6 KB
Content

Applications

Navigation

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