Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 32.2 >
edited by Xiaoling
on 2022/07/13 14:44
To version < 40.1 >
edited by Bei Jinggeng
on 2023/04/23 10:58
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Bei
Content
... ... @@ -4,30 +4,38 @@
4 4  
5 5  
6 6  
7 -= 1. OTAA Join Process Debug =
7 += 1.(% style="display:none" %) (%%) OTAA Join Process Debug =
8 8  
9 +
9 9  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.
10 10  \\**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:**
11 11  
12 12  * End node console to show the Join freuqency and DR. (If possible)
14 +
13 13  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server. (If possible)
16 +
14 14  * Gateway traffic (from server UI) to shows the data exchange between gateway and server. (Normaly possible)
18 +
15 15  * End Node traffic (from server UI) to shows end node activity in server. (Normaly possible)
20 +
16 16  * 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)
17 17  
18 -**~1. End Device Join Screen shot, we can check:**
23 +(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
19 19  
20 20  * If the device is sending join request to server?
26 +
21 21  * What frequency the device is sending?
22 22  
23 -[[image:image-20220526164956-15.png]]
29 +[[image:image-20220526164956-15.png||height="591" width="1153"]]
24 24  
25 25  Console Output from End device to see the transmit frequency
26 26  
27 27  
28 -**2. Gateway packet traffic in gateway web or ssh. we can check:**
29 29  
35 +(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
36 +
30 30  * If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
38 +
31 31  * If the gateway gets the Join Accept message from server and transmit it via LoRa?
32 32  
33 33  [[image:image-20220526163608-2.png]]
... ... @@ -35,10 +35,13 @@
35 35  Console Output from Gateway to see packets between end node and server.
36 36  
37 37  
38 -**3. Gateway Traffic Page in LoRaWAN Server**
39 39  
47 +(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
48 +
40 40  * If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
50 +
41 41  * 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.
52 +
42 42  * 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.
43 43  
44 44  [[image:image-20220526163633-3.png]]
... ... @@ -46,8 +46,9 @@
46 46  The Traffic for the End node in the server, use TTN as example
47 47  
48 48  
49 -**4. Data Page in LoRaWAN server**
50 50  
61 +(% style="color:blue" %)**4. Data Page in LoRaWAN server**
62 +
51 51  * 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.
52 52  
53 53  [[image:image-20220526163704-4.png]]
... ... @@ -54,6 +54,7 @@
54 54  
55 55  The data for the end device set in server
56 56  
69 +
57 57  [[image:image-20220526163732-5.png]]
58 58  
59 59  Check if OTAA Keys match the keys in device
... ... @@ -61,6 +61,7 @@
61 61  
62 62  = 2. Notice of US915/CN470/AU915 Frequency band =
63 63  
77 +
64 64  (((
65 65  If user has problem to work with lorawan server in band US915/AU915/CN470, he can check:
66 66  )))
... ... @@ -99,14 +99,18 @@
99 99  
100 100  US915 Channels
101 101  
116 +
102 102  [[image:image-20220526163926-7.png]]
103 103  
104 104  AU915 Channels
105 105  
121 +
106 106  [[image:image-20220526163941-8.png]]
107 107  
108 108  (((
109 109  CN470 Channels
126 +
127 +
110 110  )))
111 111  
112 112  (((
... ... @@ -117,6 +117,8 @@
117 117  
118 118  (((
119 119  TTN FREQUENCY PLAN
138 +
139 +(% style="display:none" %) (%%)
120 120  )))
121 121  
122 122  (((
... ... @@ -123,22 +123,23 @@
123 123  In dragino end node, user can use AT+CHE command to set what frequencies set the end node will use. The default settings for Dragino end node are preconfigure for TTN server, so use 8~~15 channels, which is **AT+CHE=2**. (AT+CHE=1 for first 8 channels, AT+CHE=2 for second 8 channels.. etc, and AT+CHE=0 for all 72 channels. )
124 124  )))
125 125  
146 +(% style="display:none" %) (%%)
126 126  
127 127  = 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
128 128  
150 +
129 129  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:
130 130  
131 -* **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.
132 -* **Gateway** ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Gateway. this is the default settings for dragino sensors.
133 -* **LoRaWAN server** ~-~-> ChirpStack default installation and use Sub-band1, **enabled_uplink_channels=[0, 1, 2, 3, 4, 5, 6, 7]** in the file chirpstack-network-server.toml.
153 +* (% style="color:blue" %)**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.
134 134  
155 +* (% style="color:blue" %)**Gateway** (%%) ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Gateway. this is the default settings for dragino sensors.
156 +
157 +* (% style="color:blue" %)**LoRaWAN server**  (%%) ~-~-> ChirpStack default installation and use Sub-band1, **enabled_uplink_channels=[0, 1, 2, 3, 4, 5, 6, 7]** in the file chirpstack-network-server.toml.
158 +
135 135  (((
136 136  When Sensor power on, it will use sub-band2 to join the network, the frequency matches the settings in gateway so all Join Request will be passed to the server for Join. Server will ask the sensor to change to Sub-band1 in the Join Accept downlink message. Sensor will change to sub-band1 for data upload. This cause the sensor and gateway have different frequencies so user see lost of most data or even no data.
137 137  )))
138 138  
139 -(((
140 -
141 -)))
142 142  
143 143  (((
144 144  Use Subband2 as a default subband cause the sensor to have problem to work with the LoRaWAN server which use other subband, and use need to access to the end node to change the subband by console. that is not user frendily,. So since Dragino LoRaWAN Stack version DLS-005(release on end of 2020), we have changed the device to use All Subbands for OTAA join, for example, device will use the first frequency in Sub-Band1 as firt OTAA join packet, then use the first frequency in Sub-Band 2 , then first frequency in sub-band 3, and so on. LoRaWAN server will normally provide the required subband in the OTAA accept process, so end node will know what subband it use after join. If LoRaWAN server doesn't provide subband info in OTAA join, end node will use the subband which join success as the working subband. So the new method cause a longer OTAA Join time but will be compatible with all LoRaWAN server. And new method won't affect the normal uplink after Join Success.
... ... @@ -147,23 +147,16 @@
147 147  
148 148  = 4. Transmision on ABP Mode =
149 149  
171 +
150 150  (((
151 151  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.
152 152  )))
153 153  
154 154  (((
155 -
156 -)))
157 -
158 -(((
159 159  So in ABP mode, first check if the packet already arrive your gateway, if the packet arrive gatewat but didn't arrive server. Please check if this is the issue.
160 160  )))
161 161  
162 162  (((
163 -
164 -)))
165 -
166 -(((
167 167  To solve this, disable the Frame Counter Check will solve this issue , or reset the frame counter in the device page.
168 168  )))
169 169  
... ... @@ -176,6 +176,7 @@
176 176  
177 177  == 5.1 How it work ==
178 178  
193 +
179 179  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.
180 180  
181 181  (((
... ... @@ -186,18 +186,25 @@
186 186  
187 187  receive windows for Class A and Class C
188 188  
204 +
189 189  Below are the requirement for the End Device to receive the packets.
190 190  
191 191  * The End Device must open the receive windows: RX1 or RX2
208 +
192 192  * The LoRaWAN server must send a downstream packet, and the gateway forward this downstream packet for this end node.
210 +
193 193  * This downstream packet must arrive to the end node while RX1 or RX2 is open.
212 +
194 194  * This packet must match the frequency of the RX1 or RX2 window.
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.**
196 196  
215 +* 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.**
216 +
217 +
197 197  == 5.2 See Debug Info ==
198 198  
220 +
199 199  (((
200 -**For LoRaWAN Server**
222 +(% style="color:blue" %)**For LoRaWAN Server**
201 201  )))
202 202  
203 203  (((
... ... @@ -226,8 +226,9 @@
226 226  )))
227 227  
228 228  
251 +
229 229  (((
230 -**For LoRaWAN Gateway**
253 +(% style="color:blue" %)**For LoRaWAN Gateway**
231 231  )))
232 232  
233 233  (((
... ... @@ -241,8 +241,9 @@
241 241  )))
242 242  
243 243  
267 +
244 244  (((
245 -**For End Node**
269 +(% style="color:blue" %)**For End Node**
246 246  )))
247 247  
248 248  (((
... ... @@ -250,21 +250,17 @@
250 250  )))
251 251  
252 252  (((
253 -
254 -)))
277 +* (% style="color:#037691" %)**AT+RX2FQ=869525000**  (%%) **~-~-->**  The RX2 Window frequency
255 255  
256 -(((
257 -(% class="box infomessage" %)
258 -(((
259 -AT+RX2FQ=869525000     ~-~--> The RX2 Window frequency
260 -AT+RX2DR=3      ~-~--> The RX2 DataRate
261 -AT+RX1DL=1000   ~-~--> Receive Delay 1
262 -AT+RX2DL=2000   ~-~--> Receive Delay 2
279 +* (% style="color:#037691" %)**AT+RX2DR=3**          (%%) **~-~-->**  The RX2 DataRate
280 +
281 +* (% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
282 +
283 +* (% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
263 263  )))
264 -)))
265 265  
266 266  (((
267 -**when the device running, we can see below info:**
287 +(% style="color:blue" %)**when the device running, we can see below info:**
268 268  )))
269 269  
270 270  {{{ [12502]***** UpLinkCounter= 0 *****
... ... @@ -277,10 +277,12 @@
277 277  
278 278  (((
279 279  
300 +
301 +
280 280  )))
281 281  
282 282  (((
283 -**Another message:**
305 +(% style="color:blue" %)**Another message:**
284 284  )))
285 285  
286 286  {{{ [12502]***** UpLinkCounter= 0 *****
... ... @@ -295,17 +295,23 @@
295 295   1:0012345678}}}
296 296  
297 297  
298 -== 5.3 If problem doesn’t solve ==
320 +== 5.3 If problem doesn't solve ==
299 299  
322 +
300 300  (% 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:**
301 301  
302 302  * End node console to show the transmit freuqency and DR.
326 +
303 303  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server.
328 +
304 304  * Gateway traffic (from server UI) to shows the data exchange between gateway and server.
330 +
305 305  * End Node traffic (from server UI) to shows end node activity in server.
306 306  
333 +
307 307  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
308 308  
336 +
309 309  (((
310 310  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.
311 311  )))
... ... @@ -331,20 +331,22 @@
331 331  
332 332  = 7. Decrypt a LoRaWAN Packet =
333 333  
334 -~1. LHT65 End device configure:
335 335  
336 -(% class="box infomessage" %)
337 -(((
338 -**Change to ABP Mode: AT+NJM=0**
339 -**Change to fix frequency: AT+CHS=904900000**
340 -**Change to fix DR: AT+DR=0**
341 -)))
363 +(% style="color:blue" %)**1. LHT65 End device configure:**
342 342  
365 +**Change to ABP Mode:  AT+NJM=0**
366 +
367 +**Change to fix frequency:  AT+CHS=904900000**
368 +
369 +**Change to fix DR:  AT+DR=0**
370 +
371 +
343 343  [[image:image-20220526165525-16.png]]
344 344  
345 345  
346 -2. In LG02 , configure to receive above message
347 347  
376 +(% style="color:blue" %)**2. In LG02 , configure to receive above message**
377 +
348 348  [[image:image-20220526165612-17.png]]
349 349  
350 350  
... ... @@ -353,8 +353,9 @@
353 353  [[image:image-20220526171112-21.png]]
354 354  
355 355  
356 -3. Decode the info in web
357 357  
387 +(% style="color:blue" %)**3. Decode the info in web**
388 +
358 358  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
359 359  
360 360  Need these three fields:
... ... @@ -365,6 +365,7 @@
365 365  
366 366  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
367 367  
399 +
368 368  [[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]]
369 369  
370 370  [[image:image-20220526171029-20.png]]
... ... @@ -376,13 +376,15 @@
376 376  
377 377  = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
378 378  
411 +
379 379  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.
380 380  
381 381  
382 382  = 9. Why do I see a "MIC Mismatch" error message from the server? =
383 383  
417 +
384 384  (((
385 -1)If the user receives a "MIC Mismatch" message after registering the node on the server.
419 +1)  If the user receives a "MIC Mismatch" message after registering the node on the server.
386 386  )))
387 387  
388 388  (((
... ... @@ -403,33 +403,57 @@
403 403  
404 404  * (((
405 405  If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
406 -
407 -
408 408  )))
409 409  
442 +(% class="wikigeneratedid" %)
443 +3）Wrong Regional Parameters version selected
444 + We generally use versions above 1.0.2
445 +
446 +(% class="wikigeneratedid" %)
447 +[[image:image-20230322163227-1.png]]
448 +
449 +(% class="wikigeneratedid" %)
450 +4）We have had cases where it was automatically fixed the next day despite no manual changes, probably a server side issue
451 +
452 +
410 410  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
411 411  
412 -* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
413 413  
414 -(((
415 -When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
416 -)))
456 +(% style="color:blue" %)**Why this happen:**
417 417  
418 -(((
419 -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.
420 -)))
458 +For US915, AU915 or AS923 frequencies.It is possible because: .
421 421  
422 -* (((
423 -Solution: Use the decoder to filter out this 00 packet.
424 -)))
425 -* (((
426 -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]]
460 +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.
427 427  
428 -
429 -)))
462 +1.
430 430  
464 +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.
465 +
466 +2.
467 +
468 +The server downlinks a calibration time package
469 +This calibration time packet will exceed the byte limit, causing its payload to become 00
470 +
471 +(% style="color:blue" %)**How to solve:**
472 +
473 +Solution:
474 +
475 +~1. Use the decoder to filter out this 0x00 packet.
476 +
477 +2. Data rate changed from DR3 to DR5, increasing upload byte length
478 +AT+ADR=0
479 +AT+DR=3
480 +
481 +Downlink：
482 +
483 +[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/#H7.4DataRate>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/#H7.4DataRate]]
484 +
485 +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]]
486 +
487 +
431 431  = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
432 432  
490 +
433 433  (((
434 434  It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
435 435  )))
... ... @@ -460,6 +460,8 @@
460 460  
461 461  (((
462 462  You can rewrites the keys by running commands in AT Console
521 +
522 +
463 463  )))
464 464  
465 465  (((
... ... @@ -493,6 +493,30 @@
493 493  Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
494 494  
495 495  
556 += 13. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
496 496  
558 +
559 +In US915, AU915 or CN470 frequency band, there are 8 subbands, totally 72 channels. and LoRaWAN server normally use only one sub-band, for example Subband 2 in TTN. The gateway also configured to Subband 2 and cover eight channels in this subband. If the end node transfer data in Subband 2, it will reach to gateway and to the LoRaWAN server. If the end node transfer packets in other subbands, for example subband 1, the packet won't arrive both gateway or LoRaWAN server.
560 +
561 +
562 +In Dragino Sensors old version firmware (before early 2022), the subband is fixed the subband to 2 , but this cause a problem, the end node is hard to use in other subband and need program. So the new logic is as below:
563 +
564 +We have improved this, the end node will use frequency 1 from sub-band1, then frequency 1 from sub-band2, then frequency 1 from sub-band3, etc to process the OTAA join, In this case, In this case, the end node can support LoRaWAN servers with different subbands. To make sure the end node will only transmit the proper sub-band after OTAA Joined successfully, the end node will:
565 +
566 +* (((
567 +Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
568 +)))
569 +* (((
570 +Use the Join successful sub-band if the server doesn't include subband info in the OTAA Join Accept message ( TTN v2 doesn't include)
571 +)))
572 +
573 +This change will make the activation time a littler longer but make sure the device can be used in any subband.
574 +
575 +
576 +Below is a photo to show why it takes longer time for OTAA Join. We can see in 72 channels mode, why it takes more time to join success. If users want to have faster OTAA Join success, he can change default CHE to the subband he use.
577 +
578 +
579 +[[image:image-20221215223215-1.png||height="584" width="1280"]]
580 +
497 497  (% class="wikigeneratedid" %)
498 498  
image-20221215223215-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +183.6 KB
Content
image-20230322163227-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +43.1 KB
Content

Applications

Navigation

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