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 < 37.2 >
edited by Xiaoling
on 2022/12/16 10:46
>
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
... ... @@ -4,7 +4,7 @@
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  
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.
... ... @@ -16,13 +16,12 @@
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 -
20 20  (% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
21 21  
22 22  * If the device is sending join request to server?
23 23  * What frequency the device is sending?
24 24  
25 -[[image:image-20220526164956-15.png]]
24 +[[image:image-20220526164956-15.png||height="591" width="1153"]]
26 26  
27 27  Console Output from End device to see the transmit frequency
28 28  
... ... @@ -38,6 +38,7 @@
38 38  Console Output from Gateway to see packets between end node and server.
39 39  
40 40  
40 +
41 41  (% style="color:blue" %)**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.
... ... @@ -49,6 +49,7 @@
49 49  The Traffic for the End node in the server, use TTN as example
50 50  
51 51  
52 +
52 52  (% style="color:blue" %)**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.
... ... @@ -57,12 +57,12 @@
57 57  
58 58  The data for the end device set in server
59 59  
61 +
60 60  [[image:image-20220526163732-5.png]]
61 61  
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 68  
... ... @@ -104,6 +104,7 @@
104 104  
105 105  US915 Channels
106 106  
108 +
107 107  [[image:image-20220526163926-7.png]]
108 108  
109 109  AU915 Channels
... ... @@ -126,7 +126,7 @@
126 126  (((
127 127  TTN FREQUENCY PLAN
128 128  
129 -
131 +(% style="display:none" %) (%%)
130 130  )))
131 131  
132 132  (((
... ... @@ -133,24 +133,23 @@
133 133  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. )
134 134  )))
135 135  
138 +(% style="display:none" %) (%%)
136 136  
137 -
138 138  = 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
139 139  
140 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 -* **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.
144 -* **Gateway** ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Gateway. this is the default settings for dragino sensors.
145 -* **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.
145 +* (% 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.
146 146  
147 +* (% 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.
148 +
149 +* (% 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.
150 +
147 147  (((
148 148  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.
149 149  )))
150 150  
151 -(((
152 -
153 -)))
154 154  
155 155  (((
156 156  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.
... ... @@ -157,7 +157,6 @@
157 157  )))
158 158  
159 159  
160 -
161 161  = 4. Transmision on ABP Mode =
162 162  
163 163  
... ... @@ -166,18 +166,10 @@
166 166  )))
167 167  
168 168  (((
169 -
170 -)))
171 -
172 -(((
173 173  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.
174 174  )))
175 175  
176 176  (((
177 -
178 -)))
179 -
180 -(((
181 181  To solve this, disable the Frame Counter Check will solve this issue , or reset the frame counter in the device page.
182 182  )))
183 183  
... ... @@ -186,7 +186,6 @@
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 ==
... ... @@ -206,9 +206,13 @@
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
200 +
209 209  * The LoRaWAN server must send a downstream packet, and the gateway forward this downstream packet for this end node.
202 +
210 210  * This downstream packet must arrive to the end node while RX1 or RX2 is open.
204 +
211 211  * This packet must match the frequency of the RX1 or RX2 window.
206 +
212 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.**
213 213  
214 214  
... ... @@ -315,7 +315,6 @@
315 315   1:0012345678}}}
316 316  
317 317  
318 -
319 319  == 5.3 If problem doesn't solve ==
320 320  
321 321  
... ... @@ -354,7 +354,6 @@
354 354  )))
355 355  
356 356  
357 -
358 358  = 7. Decrypt a LoRaWAN Packet =
359 359  
360 360  
... ... @@ -402,7 +402,6 @@
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 408  
... ... @@ -409,7 +409,6 @@
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 415  
... ... @@ -437,7 +437,6 @@
437 437  If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
438 438  
439 439  
440 -
441 441  
442 442  )))
443 443  
... ... @@ -444,18 +444,22 @@
444 444  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
445 445  
446 446  
447 -* If you are using US915, AU915 or AS923 frequencies.It is possible because: .
437 +**Why this happen:**
448 448  
439 +For US915, AU915 or AS923 frequencies.It is possible because: .
440 +
449 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 450  
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.
443 +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.
452 452  
453 -Solution: Use the decoder to filter out this 00 packet.
454 454  
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]]
446 +**How to solve:**
456 456  
448 +Solution: Use the decoder to filter out this 0x00 packet.
457 457  
450 +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]]
458 458  
452 +
459 459  = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
460 460  
461 461  
... ... @@ -517,7 +517,6 @@
517 517  (Any combination of 16 bit codes can be used）
518 518  
519 519  
520 -
521 521  = 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
522 522  )))
523 523  
... ... @@ -525,6 +525,30 @@
525 525  Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
526 526  
527 527  
521 += 13. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
528 528  
523 +
524 +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.
525 +
526 +
527 +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:
528 +
529 +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:
530 +
531 +* (((
532 +Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
533 +)))
534 +* (((
535 +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)
536 +)))
537 +
538 +This change will make the activation time a littler longer but make sure the device can be used in any subband.
539 +
540 +
541 +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.
542 +
543 +
544 +[[image:image-20221215223215-1.png||height="584" width="1280"]]
545 +
529 529  (% class="wikigeneratedid" %)
530 530  
image-20221215223215-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +183.6 KB
Content

Applications

Navigation

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