Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 34.1 >
edited by Edwin Chen
on 2022/10/19 23:14
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,7 +16,7 @@
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  
19 -(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
18 +**~1. End Device Join Screen shot, we can check:**
20 20  
21 21  * If the device is sending join request to server?
22 22  * What frequency the device is sending?
... ... @@ -26,9 +26,8 @@
26 26  Console Output from End device to see the transmit frequency
27 27  
28 28  
28 +**2. Gateway packet traffic in gateway web or ssh. we can check:**
29 29  
30 -(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
31 -
32 32  * If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
33 33  * If the gateway gets the Join Accept message from server and transmit it via LoRa?
34 34  
... ... @@ -37,7 +37,7 @@
37 37  Console Output from Gateway to see packets between end node and server.
38 38  
39 39  
40 -(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
38 +**3. Gateway Traffic Page in LoRaWAN Server**
41 41  
42 42  * If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
43 43  * 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.
... ... @@ -48,7 +48,7 @@
48 48  The Traffic for the End node in the server, use TTN as example
49 49  
50 50  
51 -(% style="color:blue" %)**4. Data Page in LoRaWAN server**
49 +**4. Data Page in LoRaWAN server**
52 52  
53 53  * 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.
54 54  
... ... @@ -61,10 +61,8 @@
61 61  Check if OTAA Keys match the keys in device
62 62  
63 63  
64 -
65 65  = 2. Notice of US915/CN470/AU915 Frequency band =
66 66  
67 -
68 68  (((
69 69  If user has problem to work with lorawan server in band US915/AU915/CN470, he can check:
70 70  )))
... ... @@ -107,13 +107,10 @@
107 107  
108 108  AU915 Channels
109 109  
110 -
111 111  [[image:image-20220526163941-8.png]]
112 112  
113 113  (((
114 114  CN470 Channels
115 -
116 -
117 117  )))
118 118  
119 119  (((
... ... @@ -124,8 +124,6 @@
124 124  
125 125  (((
126 126  TTN FREQUENCY PLAN
127 -
128 -
129 129  )))
130 130  
131 131  (((
... ... @@ -133,10 +133,8 @@
133 133  )))
134 134  
135 135  
136 -
137 137  = 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
138 138  
139 -
140 140  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:
141 141  
142 142  * **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.
... ... @@ -156,10 +156,8 @@
156 156  )))
157 157  
158 158  
159 -
160 160  = 4. Transmision on ABP Mode =
161 161  
162 -
163 163  (((
164 164  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.
165 165  )))
... ... @@ -185,12 +185,10 @@
185 185  Disable Frame Counter Check in ABP Mode
186 186  
187 187  
188 -
189 189  = 5. Downstream Debug =
190 190  
191 191  == 5.1 How it work ==
192 192  
193 -
194 194  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.
195 195  
196 196  (((
... ... @@ -197,11 +197,10 @@
197 197  Depends on Class A or Class C, the receive windows will be a little difference,
198 198  )))
199 199  
200 -[[image:image-20220531161828-1.png]]
185 +[[image:image-20220526164547-11.png]]
201 201  
202 202  receive windows for Class A and Class C
203 203  
204 -
205 205  Below are the requirement for the End Device to receive the packets.
206 206  
207 207  * The End Device must open the receive windows: RX1 or RX2
... ... @@ -208,14 +208,14 @@
208 208  * The LoRaWAN server must send a downstream packet, and the gateway forward this downstream packet for this end node.
209 209  * This downstream packet must arrive to the end node while RX1 or RX2 is open.
210 210  * This packet must match the frequency of the RX1 or RX2 window.
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.**
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.**
212 212  
213 213  
198 +
214 214  == 5.2 See Debug Info ==
215 215  
216 -
217 217  (((
218 -(% style="color:blue" %)**For LoRaWAN Server**
202 +**For LoRaWAN Server**
219 219  )))
220 220  
221 221  (((
... ... @@ -244,9 +244,8 @@
244 244  )))
245 245  
246 246  
247 -
248 248  (((
249 -(% style="color:blue" %)**For LoRaWAN Gateway**
232 +**For LoRaWAN Gateway**
250 250  )))
251 251  
252 252  (((
... ... @@ -260,9 +260,8 @@
260 260  )))
261 261  
262 262  
263 -
264 264  (((
265 -(% style="color:blue" %)**For End Node**
247 +**For End Node**
266 266  )))
267 267  
268 268  (((
... ... @@ -270,19 +270,23 @@
270 270  )))
271 271  
272 272  (((
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 -
279 279  
280 280  )))
281 281  
282 282  (((
283 -(% 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
284 284  )))
266 +)))
285 285  
268 +(((
269 +**when the device running, we can see below info:**
270 +)))
271 +
286 286  {{{ [12502]***** UpLinkCounter= 0 *****
287 287   [12503]TX on freq 868500000 Hz at DR 0
288 288   [13992]txDone
... ... @@ -293,12 +293,10 @@
293 293  
294 294  (((
295 295  
296 -
297 -
298 298  )))
299 299  
300 300  (((
301 -(% style="color:blue" %)**Another message:**
285 +**Another message:**
302 302  )))
303 303  
304 304  {{{ [12502]***** UpLinkCounter= 0 *****
... ... @@ -313,10 +313,8 @@
313 313   1:0012345678}}}
314 314  
315 315  
300 +== 5.3 If problem doesn’t solve ==
316 316  
317 -== 5.3 If problem doesn't solve ==
318 -
319 -
320 320  (% 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:**
321 321  
322 322  * End node console to show the transmit freuqency and DR.
... ... @@ -324,10 +324,8 @@
324 324  * Gateway traffic (from server UI) to shows the data exchange between gateway and server.
325 325  * End Node traffic (from server UI) to shows end node activity in server.
326 326  
327 -
328 328  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
329 329  
330 -
331 331  (((
332 332  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.
333 333  )))
... ... @@ -351,23 +351,30 @@
351 351  )))
352 352  
353 353  
354 -
355 355  = 7. Decrypt a LoRaWAN Packet =
356 356  
336 +~1. LHT65 End device configure:
357 357  
358 -(% style="color:blue" %)**1. LHT65 End device configure:**
338 +(% class="box infomessage" %)
339 +(((
340 +**Change to ABP Mode: AT+NJM=0**
341 +)))
359 359  
360 -**Change to ABP Mode:  AT+NJM=0**
361 -**Change to fix frequency:  AT+CHS=904900000**
362 -**Change to fix DR:  AT+DR=0**
343 +(% class="box infomessage" %)
344 +(((
345 +**Change to fix frequency: AT+CHS=904900000**
346 +)))
363 363  
348 +(% class="box infomessage" %)
349 +(((
350 +**Change to fix DR: AT+DR=0**
351 +)))
364 364  
365 365  [[image:image-20220526165525-16.png]]
366 366  
367 367  
356 +2. In LG02 , configure to receive above message
368 368  
369 -(% style="color:blue" %)**2. In LG02 , configure to receive above message**
370 -
371 371  [[image:image-20220526165612-17.png]]
372 372  
373 373  
... ... @@ -376,9 +376,8 @@
376 376  [[image:image-20220526171112-21.png]]
377 377  
378 378  
366 +3. Decode the info in web
379 379  
380 -(% style="color:blue" %)**3. Decode the info in web**
381 -
382 382  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
383 383  
384 384  Need these three fields:
... ... @@ -389,7 +389,6 @@
389 389  
390 390  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
391 391  
392 -
393 393  [[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]]
394 394  
395 395  [[image:image-20220526171029-20.png]]
... ... @@ -399,19 +399,15 @@
399 399  )))
400 400  
401 401  
402 -
403 403  = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
404 404  
405 -
406 406  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.
407 407  
408 408  
409 -
410 410  = 9. Why do I see a "MIC Mismatch" error message from the server? =
411 411  
412 -
413 413  (((
414 -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.
415 415  )))
416 416  
417 417  (((
... ... @@ -433,29 +433,33 @@
433 433  * (((
434 434  If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
435 435  
436 -
437 -
438 438  
439 439  )))
440 440  
441 441  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
442 442  
422 +* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
443 443  
444 -For 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 +)))
445 445  
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.
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 +)))
447 447  
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 -
432 +* (((
450 450  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]]
451 451  
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]]
453 453  
439 +
440 +)))
454 454  
455 -
456 456  = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
457 457  
458 -
459 459  (((
460 460  It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
461 461  )))
... ... @@ -486,8 +486,6 @@
486 486  
487 487  (((
488 488  You can rewrites the keys by running commands in AT Console
489 -
490 -
491 491  )))
492 492  
493 493  (((
... ... @@ -512,16 +512,8 @@
512 512  
513 513  (((
514 514  (Any combination of 16 bit codes can be used）
515 -
516 -
517 -
518 -= 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
519 519  )))
520 520  
521 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 526  (% class="wikigeneratedid" %)
527 527  
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