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 < 49.1 >
edited by Mengting Qiu
on 2024/01/23 16:37
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.ting
Content
... ... @@ -4,7 +4,7 @@
4 4  
5 5  
6 6  
7 -= 1. OTAA Join Process Debug =
7 += z =
8 8  
9 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,19 +11,22 @@
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  
13 13  * End node console to show the Join freuqency and DR. (If possible)
14 +
14 14  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server. (If possible)
16 +
15 15  * Gateway traffic (from server UI) to shows the data exchange between gateway and server. (Normaly possible)
18 +
16 16  * End Node traffic (from server UI) to shows end node activity in server. (Normaly possible)
20 +
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 -
20 -
21 21  (% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
22 22  
23 23  * If the device is sending join request to server?
26 +
24 24  * What frequency the device is sending?
25 25  
26 -[[image:image-20220526164956-15.png]]
29 +[[image:image-20220526164956-15.png||height="591" width="1153"]]
27 27  
28 28  Console Output from End device to see the transmit frequency
29 29  
... ... @@ -32,6 +32,7 @@
32 32  (% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
33 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)
38 +
35 35  * If the gateway gets the Join Accept message from server and transmit it via LoRa?
36 36  
37 37  [[image:image-20220526163608-2.png]]
... ... @@ -40,15 +40,17 @@
40 40  
41 41  
42 42  
43 -(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
47 +(% style="color:blue" %)**3. Gateway Live data in LoRaWAN Server**
44 44  
45 -* If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
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.
49 +* Does the gateway real-time data contain information about Join Request? If not, check the internet connection and gateway LoRaWAN server Settings.
50 +
51 +* Does the server send back a Join Accept for the Join Request? If not, check that the key from the device matches the key you put into the server, or try to choose a different server route for that end device.
52 +
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.
48 48  
49 49  [[image:image-20220526163633-3.png]]
50 50  
51 -The Traffic for the End node in the server, use TTN as example
57 +The Traffic for the End node in the server, use TTN as example.
52 52  
53 53  
54 54  
... ... @@ -56,17 +56,16 @@
56 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 -[[image:image-20220526163704-4.png]]
65 +[[image:image-20240123150720-1.png||height="459" width="1182"]]
60 60  
61 61  The data for the end device set in server
62 62  
63 63  
64 -[[image:image-20220526163732-5.png]]
70 +[[image:image-20240123150943-2.png||height="556" width="1179"]]
65 65  
66 -Check if OTAA Keys match the keys in device
72 +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 72  
... ... @@ -126,12 +126,12 @@
126 126  If we look at the [[TTN network server frequency plan>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]], we can see the US915 frequency band use the channel 8~~15.So the End Node must work at the same frequency in US915 8~~15 channels for TTN server.
127 127  )))
128 128  
129 -[[image:image-20220526164052-9.png]]
134 +[[image:image-20240123151225-3.png||height="434" width="902"]]
130 130  
131 131  (((
132 132  TTN FREQUENCY PLAN
133 133  
134 -
139 +(% style="display:none" %) (%%)
135 135  )))
136 136  
137 137  (((
... ... @@ -138,24 +138,23 @@
138 138  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. )
139 139  )))
140 140  
146 +(% style="display:none" %) (%%)
141 141  
148 += 3. Why I see data lost/ is not periodically uplink？ Even the signal strength is good =
142 142  
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 -* **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.
149 -* **Gateway** ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Gateway. this is the default settings for dragino sensors.
150 -* **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.
151 151  
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 +
152 152  (((
153 153  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.
154 154  )))
155 155  
156 -(((
157 -
158 -)))
159 159  
160 160  (((
161 161  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.
... ... @@ -162,7 +162,6 @@
162 162  )))
163 163  
164 164  
165 -
166 166  = 4. Transmision on ABP Mode =
167 167  
168 168  
... ... @@ -171,27 +171,20 @@
171 171  )))
172 172  
173 173  (((
174 -
175 -)))
176 -
177 -(((
178 178  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.
179 179  )))
180 180  
181 181  (((
182 -
183 -)))
184 -
185 -(((
186 186  To solve this, disable the Frame Counter Check will solve this issue , or reset the frame counter in the device page.
182 +
183 +[[image:image-20240123161737-4.png||height="395" width="763"]]
187 187  )))
188 188  
189 -[[image:image-20220526164508-10.png]]
186 +[[image:image-20240123161853-6.png||height="599" width="771"]]
190 190  
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 ==
... ... @@ -200,7 +200,7 @@
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 -Depends on Class A or Class C, the receive windows will be a little difference,
199 +Depends on Class A or Class C, the receive windows will be a little difference.
204 204  )))
205 205  
206 206  [[image:image-20220531161828-1.png]]
... ... @@ -211,13 +211,18 @@
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
210 +
214 214  * The LoRaWAN server must send a downstream packet, and the gateway forward this downstream packet for this end node.
212 +
215 215  * This downstream packet must arrive to the end node while RX1 or RX2 is open.
214 +
216 216  * This packet must match the frequency of the RX1 or RX2 window.
216 +
217 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.**
218 218  
219 +(% class="wikigeneratedid" %)
220 +== ==
219 219  
220 -
221 221  == 5.2 See Debug Info ==
222 222  
223 223  
... ... @@ -230,10 +230,10 @@
230 230  )))
231 231  
232 232  (((
233 -Configure a downstream to the end device
234 +Configure a downlink to the end device
234 234  )))
235 235  
236 -[[image:image-20220526164623-12.png]]
237 +[[image:image-20240123163307-7.png||height="330" width="1125"]]
237 237  
238 238  (((
239 239  Set a downstream in TTN and see it is sent
... ... @@ -277,13 +277,13 @@
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
281 +* (% style="color:#037691" %)**AT+RX2FQ=869525000**  (%%) **~-~-->**  The RX2 Window frequency
284 284  
283 +* (% style="color:#037691" %)**AT+RX2DR=3**          (%%) **~-~-->**  The RX2 DataRate
285 285  
286 -
285 +* (% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
286 +
287 +* (% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
287 287  )))
288 288  
289 289  (((
... ... @@ -320,7 +320,6 @@
320 320   1:0012345678}}}
321 321  
322 322  
323 -
324 324  == 5.3 If problem doesn't solve ==
325 325  
326 326  
... ... @@ -327,12 +327,13 @@
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.
330 +
330 330  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server.
332 +
331 331  * Gateway traffic (from server UI) to shows the data exchange between gateway and server.
334 +
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 338  
... ... @@ -359,7 +359,6 @@
359 359  )))
360 360  
361 361  
362 -
363 363  = 7. Decrypt a LoRaWAN Packet =
364 364  
365 365  
... ... @@ -366,7 +366,9 @@
366 366  (% style="color:blue" %)**1. LHT65 End device configure:**
367 367  
368 368  **Change to ABP Mode:  AT+NJM=0**
369 +
369 369  **Change to fix frequency:  AT+CHS=904900000**
371 +
370 370  **Change to fix DR:  AT+DR=0**
371 371  
372 372  
... ... @@ -407,7 +407,6 @@
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 413  
... ... @@ -414,7 +414,6 @@
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 420  
... ... @@ -440,32 +440,53 @@
440 440  
441 441  * (((
442 442  If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
443 +)))
443 443  
445 +(% class="wikigeneratedid" %)
446 +3）Wrong Regional Parameters version selected
447 + We generally use versions above 1.0.2
444 444  
449 +(% class="wikigeneratedid" %)
450 +[[image:image-20230322163227-1.png]]
445 445  
446 -
447 -)))
452 +(% class="wikigeneratedid" %)
453 +4）We have had cases where it was automatically fixed the next day despite no manual changes, probably a server side issue
448 448  
455 +
449 449  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
450 450  
451 451  
452 -**Why this happen:**
459 +(% style="color:blue" %)**Why sensor sends 0x00?**
453 453  
454 -For US915, AU915 or AS923 frequencies.It is possible because: .
461 +For US915, AU915 or AS923 frequencies, the max payload lenght is 11 bytes for DR0. Some times sensor needs to send MAC command to server, because the payload is 11 bytes, The MAC command + Payload will exceed 11 bytes and LoRaWAN server will ignore the uplink. In this case, Sensor will send two uplinks together: one uplink is the payload without MAC command, another uplink is **0x00 payload + MAC Command.**  For the second uplink, in the server side, it will shows the payload is 0x00. Normally, there are several case this will happen.
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.
463 +**Possible Case 1**:
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.
465 +Sensor has ADR=1 enable and sensor need to reply server MAC command (ADR request) while sensor has DR=0.
459 459  
460 460  
461 -**How to solve:**
468 +**Possible Case 2:**
462 462  
463 -Solution: Use the decoder to filter out this 0x00 packet.
470 +For the sensor which has Datalog Feature enable, the sensor will send TimeRequest MAC Command to sync the time. This Time Request will be sent once Sensor Join Network and Every 10 days. While they send such command with DR=0, sensor will send this command with 0x00 payload.
464 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 466  
473 +(% style="color:blue" %)**How to solve:**
467 467  
475 +Solution:
468 468  
477 +~1. Use the decoder to filter out this 0x00 packet. (**Recommand**)
478 +
479 +2. Data rate changed from DR3 to DR5, increasing upload byte length
480 +AT+ADR=0
481 +AT+DR=3
482 +
483 +Downlink：
484 +
485 +[[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]]
486 +
487 +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]]
488 +
489 +
469 469  = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
470 470  
471 471  
... ... @@ -527,7 +527,6 @@
527 527  (Any combination of 16 bit codes can be used）
528 528  
529 529  
530 -
531 531  = 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
532 532  )))
533 533  
... ... @@ -535,6 +535,30 @@
535 535  Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
536 536  
537 537  
558 += 13. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
538 538  
560 +
561 +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.
562 +
563 +
564 +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:
565 +
566 +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:
567 +
568 +* (((
569 +Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
570 +)))
571 +* (((
572 +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)
573 +)))
574 +
575 +This change will make the activation time a littler longer but make sure the device can be used in any subband.
576 +
577 +
578 +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.
579 +
580 +
581 +[[image:image-20221215223215-1.png||height="584" width="1280"]]
582 +
539 539  (% class="wikigeneratedid" %)
540 540  
image-20230322163227-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +43.1 KB
Content
image-20240123150720-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +119.9 KB
Content
image-20240123150943-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +161.5 KB
Content
image-20240123151225-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +136.1 KB
Content
image-20240123161737-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +83.0 KB
Content
image-20240123161806-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +71.5 KB
Content
image-20240123161853-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +60.6 KB
Content
image-20240123163307-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +123.3 KB
Content

Applications

Navigation

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