Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 36.1 >
edited by Edwin Chen
on 2022/12/15 22:32
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,10 +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 -
21 -(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
22 -
23 23  * If the device is sending join request to server?
24 24  * What frequency the device is sending?
25 25  
... ... @@ -28,9 +28,8 @@
28 28  Console Output from End device to see the transmit frequency
29 29  
30 30  
28 +**2. Gateway packet traffic in gateway web or ssh. we can check:**
31 31  
32 -(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
33 -
34 34  * If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
35 35  * If the gateway gets the Join Accept message from server and transmit it via LoRa?
36 36  
... ... @@ -39,9 +39,8 @@
39 39  Console Output from Gateway to see packets between end node and server.
40 40  
41 41  
38 +**3. Gateway Traffic Page in LoRaWAN Server**
42 42  
43 -(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
44 -
45 45  * If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
46 46  * 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.
47 47  * 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.
... ... @@ -51,9 +51,8 @@
51 51  The Traffic for the End node in the server, use TTN as example
52 52  
53 53  
49 +**4. Data Page in LoRaWAN server**
54 54  
55 -(% style="color:blue" %)**4. Data Page in LoRaWAN server**
56 -
57 57  * 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.
58 58  
59 59  [[image:image-20220526163704-4.png]]
... ... @@ -60,16 +60,13 @@
60 60  
61 61  The data for the end device set in server
62 62  
63 -
64 64  [[image:image-20220526163732-5.png]]
65 65  
66 66  Check if OTAA Keys match the keys in device
67 67  
68 68  
69 -
70 70  = 2. Notice of US915/CN470/AU915 Frequency band =
71 71  
72 -
73 73  (((
74 74  If user has problem to work with lorawan server in band US915/AU915/CN470, he can check:
75 75  )))
... ... @@ -108,18 +108,14 @@
108 108  
109 109  US915 Channels
110 110  
111 -
112 112  [[image:image-20220526163926-7.png]]
113 113  
114 114  AU915 Channels
115 115  
116 -
117 117  [[image:image-20220526163941-8.png]]
118 118  
119 119  (((
120 120  CN470 Channels
121 -
122 -
123 123  )))
124 124  
125 125  (((
... ... @@ -130,8 +130,6 @@
130 130  
131 131  (((
132 132  TTN FREQUENCY PLAN
133 -
134 -
135 135  )))
136 136  
137 137  (((
... ... @@ -139,10 +139,8 @@
139 139  )))
140 140  
141 141  
142 -
143 143  = 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
144 144  
145 -
146 146  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:
147 147  
148 148  * **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.
... ... @@ -162,10 +162,8 @@
162 162  )))
163 163  
164 164  
165 -
166 166  = 4. Transmision on ABP Mode =
167 167  
168 -
169 169  (((
170 170  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.
171 171  )))
... ... @@ -191,12 +191,10 @@
191 191  Disable Frame Counter Check in ABP Mode
192 192  
193 193  
194 -
195 195  = 5. Downstream Debug =
196 196  
197 197  == 5.1 How it work ==
198 198  
199 -
200 200  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.
201 201  
202 202  (((
... ... @@ -203,11 +203,10 @@
203 203  Depends on Class A or Class C, the receive windows will be a little difference,
204 204  )))
205 205  
206 -[[image:image-20220531161828-1.png]]
185 +[[image:image-20220526164547-11.png]]
207 207  
208 208  receive windows for Class A and Class C
209 209  
210 -
211 211  Below are the requirement for the End Device to receive the packets.
212 212  
213 213  * The End Device must open the receive windows: RX1 or RX2
... ... @@ -214,15 +214,14 @@
214 214  * The LoRaWAN server must send a downstream packet, and the gateway forward this downstream packet for this end node.
215 215  * This downstream packet must arrive to the end node while RX1 or RX2 is open.
216 216  * This packet must match the frequency of the RX1 or RX2 window.
217 -* 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.**
218 218  
219 219  
220 220  
221 221  == 5.2 See Debug Info ==
222 222  
223 -
224 224  (((
225 -(% style="color:blue" %)**For LoRaWAN Server**
202 +**For LoRaWAN Server**
226 226  )))
227 227  
228 228  (((
... ... @@ -251,9 +251,8 @@
251 251  )))
252 252  
253 253  
254 -
255 255  (((
256 -(% style="color:blue" %)**For LoRaWAN Gateway**
232 +**For LoRaWAN Gateway**
257 257  )))
258 258  
259 259  (((
... ... @@ -267,9 +267,8 @@
267 267  )))
268 268  
269 269  
270 -
271 271  (((
272 -(% style="color:blue" %)**For End Node**
247 +**For End Node**
273 273  )))
274 274  
275 275  (((
... ... @@ -277,19 +277,23 @@
277 277  )))
278 278  
279 279  (((
280 -(% style="color:#037691" %)**AT+RX2FQ=869525000**  (%%) **~-~-->**  The RX2 Window frequency
281 -(% style="color:#037691" %)**AT+RX2DR=3**          (%%) **~-~-->**  The RX2 DataRate
282 -(% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
283 -(% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
284 -
285 -
286 286  
287 287  )))
288 288  
289 289  (((
290 -(% 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
291 291  )))
266 +)))
292 292  
268 +(((
269 +**when the device running, we can see below info:**
270 +)))
271 +
293 293  {{{ [12502]***** UpLinkCounter= 0 *****
294 294   [12503]TX on freq 868500000 Hz at DR 0
295 295   [13992]txDone
... ... @@ -300,12 +300,10 @@
300 300  
301 301  (((
302 302  
303 -
304 -
305 305  )))
306 306  
307 307  (((
308 -(% style="color:blue" %)**Another message:**
285 +**Another message:**
309 309  )))
310 310  
311 311  {{{ [12502]***** UpLinkCounter= 0 *****
... ... @@ -320,10 +320,8 @@
320 320   1:0012345678}}}
321 321  
322 322  
300 +== 5.3 If problem doesn’t solve ==
323 323  
324 -== 5.3 If problem doesn't solve ==
325 -
326 -
327 327  (% 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:**
328 328  
329 329  * End node console to show the transmit freuqency and DR.
... ... @@ -331,11 +331,8 @@
331 331  * Gateway traffic (from server UI) to shows the data exchange between gateway and server.
332 332  * End Node traffic (from server UI) to shows end node activity in server.
333 333  
334 -
335 -
336 336  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
337 337  
338 -
339 339  (((
340 340  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.
341 341  )))
... ... @@ -359,23 +359,30 @@
359 359  )))
360 360  
361 361  
362 -
363 363  = 7. Decrypt a LoRaWAN Packet =
364 364  
336 +~1. LHT65 End device configure:
365 365  
366 -(% style="color:blue" %)**1. LHT65 End device configure:**
338 +(% class="box infomessage" %)
339 +(((
340 +**Change to ABP Mode: AT+NJM=0**
341 +)))
367 367  
368 -**Change to ABP Mode:  AT+NJM=0**
369 -**Change to fix frequency:  AT+CHS=904900000**
370 -**Change to fix DR:  AT+DR=0**
343 +(% class="box infomessage" %)
344 +(((
345 +**Change to fix frequency: AT+CHS=904900000**
346 +)))
371 371  
348 +(% class="box infomessage" %)
349 +(((
350 +**Change to fix DR: AT+DR=0**
351 +)))
372 372  
373 373  [[image:image-20220526165525-16.png]]
374 374  
375 375  
356 +2. In LG02 , configure to receive above message
376 376  
377 -(% style="color:blue" %)**2. In LG02 , configure to receive above message**
378 -
379 379  [[image:image-20220526165612-17.png]]
380 380  
381 381  
... ... @@ -384,9 +384,8 @@
384 384  [[image:image-20220526171112-21.png]]
385 385  
386 386  
366 +3. Decode the info in web
387 387  
388 -(% style="color:blue" %)**3. Decode the info in web**
389 -
390 390  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
391 391  
392 392  Need these three fields:
... ... @@ -397,7 +397,6 @@
397 397  
398 398  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
399 399  
400 -
401 401  [[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]]
402 402  
403 403  [[image:image-20220526171029-20.png]]
... ... @@ -407,19 +407,15 @@
407 407  )))
408 408  
409 409  
410 -
411 411  = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
412 412  
413 -
414 414  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.
415 415  
416 416  
417 -
418 418  = 9. Why do I see a "MIC Mismatch" error message from the server? =
419 419  
420 -
421 421  (((
422 -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.
423 423  )))
424 424  
425 425  (((
... ... @@ -441,34 +441,33 @@
441 441  * (((
442 442  If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
443 443  
444 -
445 -
446 446  
447 447  )))
448 448  
449 449  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
450 450  
422 +* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
451 451  
452 -**Why this happen:**
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 +)))
453 453  
454 -For US915, AU915 or AS923 frequencies.It is possible because: .
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 +)))
455 455  
456 -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.
432 +* (((
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]]
457 457  
458 -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.
459 459  
439 +
440 +)))
460 460  
461 -**How to solve:**
462 -
463 -Solution: Use the decoder to filter out this 0x00 packet.
464 -
465 -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]]
466 -
467 -
468 -
469 469  = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
470 470  
471 -
472 472  (((
473 473  It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
474 474  )))
... ... @@ -499,8 +499,6 @@
499 499  
500 500  (((
501 501  You can rewrites the keys by running commands in AT Console
502 -
503 -
504 504  )))
505 505  
506 506  (((
... ... @@ -525,16 +525,8 @@
525 525  
526 526  (((
527 527  (Any combination of 16 bit codes can be used）
528 -
529 -
530 -
531 -= 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
532 532  )))
533 533  
534 534  
535 -Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
536 -
537 -
538 -
539 539  (% class="wikigeneratedid" %)
540 540  
image-20220531161828-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -98.6 KB
Content
image-20221215223215-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -183.6 KB
Content

Applications

Navigation

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