Skip to Content
Last modified by Xiaoling on 2025/05/05 08:51
From version 37.2
edited by Xiaoling
on 2022/12/16 10:46
Change comment: There is no comment for this version
To version 100.1
edited by Bei Jinggeng
on 2025/04/29 13:36
Change comment: Uploaded new attachment "image-20250429133640-7.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Bei
Content
... ... @@ -4,7 +4,7 @@
4 4  
5 5  
6 6  
7 -= 1.(% style="display:none" %) (%%) OTAA Join Process Debug =
7 += 1. Join process page check =
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,57 +11,62 @@
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 19  (% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
20 20  
21 21  * If the device is sending join request to server?
26 +
22 22  * What frequency the device is sending?
23 23  
24 -[[image:image-20220526164956-15.png||height="591" width="1153"]]
29 +[[image:image-20240129142147-2.png||height="736" width="964"]]
25 25  
26 -Console Output from End device to see the transmit frequency
31 +Console Output from End device to see the transmit frequency.
27 27  
28 28  
29 -
30 30  (% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
31 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)
37 +
33 33  * If the gateway gets the Join Accept message from server and transmit it via LoRa?
34 34  
35 -[[image:image-20220526163608-2.png]]
40 +[[image:image-20240129151608-6.jpeg||height="725" width="1256"]]
36 36  
37 37  Console Output from Gateway to see packets between end node and server.
38 38  
39 39  
45 +(% style="color:blue" %)**3. Gateway Live data in LoRaWAN Server**
40 40  
41 -(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
47 +* Does the gateway real-time data contain information about Join Request? If not, check the internet connection and gateway LoRaWAN server Settings.
42 42  
43 -* If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
44 -* 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 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.
50 +
45 45  * 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.
46 46  
47 -[[image:image-20220526163633-3.png]]
53 +[[image:image-20240129150821-5.jpeg||height="522" width="1264"]]
48 48  
49 -The Traffic for the End node in the server, use TTN as example
55 +The Traffic for the End node in the server, use TTN as example.
50 50  
51 51  
52 -
53 53  (% style="color:blue" %)**4. Data Page in LoRaWAN server**
54 54  
55 55  * 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.
56 56  
57 -[[image:image-20220526163704-4.png]]
62 +[[image:image-20240129142557-3.png||height="488" width="1267"]]
58 58  
59 59  The data for the end device set in server
60 60  
61 61  
62 -[[image:image-20220526163732-5.png]]
67 +[[image:image-20240129142631-4.png||height="637" width="1256"]]
63 63  
64 -Check if OTAA Keys match the keys in device
69 +Check if OTAA Keys match the keys in device.
65 65  
66 66  
67 67  = 2. Notice of US915/CN470/AU915 Frequency band =
... ... @@ -68,17 +68,17 @@
68 68  
69 69  
70 70  (((
71 -If user has problem to work with lorawan server in band US915/AU915/CN470, he can check:
76 +If user has problem to work with LoRaWAN server in band US915/AU915/CN470, he can check:
72 72  )))
73 73  
74 74  * (((
75 -What **sub-band** the server support ?
80 +What **sub-band** the server support?
76 76  )))
77 77  * (((
78 -What is the **sub-band** the gateway support ?
83 +What is the **sub-band** the gateway support?
79 79  )))
80 80  * (((
81 -What is the **sub-band** the end node is using ?
86 +What is the **sub-band** the end node is using?
82 82  )))
83 83  
84 84  (((
... ... @@ -90,7 +90,7 @@
90 90  )))
91 91  
92 92  (((
93 -In LoRaWAN protocol, the frequency bands US915, AU915, CN470 each includes at least 72 frequencies. Many gateways support only 8 or 16 frequencies, and server might support 8 frequency only. In this case, the OTAA join time and uplink schedule is long and unpredictable while the end node is hopping in 72 frequencies, because the end node will send data in many frequency that the gateway or server doesn,t support.
98 +In LoRaWAN protocol, the frequency bands US915, AU915, CN470 each includes at least 72 frequencies. Many gateways support only 8 or 16 frequencies, and server might support 8 frequency only. In this case, the OTAA join time and uplink schedule is long and unpredictable while the end node is hopping in 72 frequencies, because the end node will send data in many frequency that the gateway or server doesn't support.
94 94  )))
95 95  
96 96  (((
... ... @@ -98,7 +98,7 @@
98 98  )))
99 99  
100 100  (((
101 -Here are the freuqency tables for these bands as reference:
106 +Here are the frequency tables for these bands as reference:
102 102  )))
103 103  
104 104  [[image:image-20220526163801-6.png]]
... ... @@ -123,7 +123,7 @@
123 123  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.
124 124  )))
125 125  
126 -[[image:image-20220526164052-9.png]]
131 +[[image:image-20240123151225-3.png||height="434" width="902"]]
127 127  
128 128  (((
129 129  TTN FREQUENCY PLAN
... ... @@ -137,7 +137,7 @@
137 137  
138 138  (% style="display:none" %) (%%)
139 139  
140 -= 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
145 += 3. Why I see data lost/ is not periodically uplink？ Even the signal strength is good =
141 141  
142 142  
143 143  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:
... ... @@ -158,9 +158,112 @@
158 158  )))
159 159  
160 160  
161 -= 4. Transmision on ABP Mode =
166 += 4. Why i see packet lost =
162 162  
168 +== **1. Signal problem** ==
163 163  
170 +
171 +1)  (% style="color:blue" %)**ADR automatic adjustment** (%%)
172 +
173 +Reason:
174 +
175 +When the signal is at a critical value, the server may configure the node to adjust to a lower power DR.
176 +At this time, the server is at risk of losing uplink.
177 +
178 +
179 +Solution:
180 +
181 +Users can manually fix the DR value.
182 +
183 +
184 +(% style="color:red" %)
185 +**Notice:**
186 +
187 +* User need to set Adaptive Data Rate(ADR)=0 first. otherwise device will respond to server's ADR command and change the DR according to server auto-adjustment.
188 +
189 +* Data Rate specifies Spreading Factor. The mapping varies in different frequency bands. User can check this link for detail. [[rp2-1.0.3-lorawan-regional-parameters.pdf>>https://lora-alliance.org/resource_hub/rp2-1-0-3-lorawan-regional-parameters/]]
190 +
191 +(% style="color:blue" %)**AT Command: AT+DR**
192 +
193 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:409px" %)
194 +|(% style="background-color:#4f81bd; color:white; width:156px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:147px" %)**Function**|(% style="background-color:#4f81bd; color:white; width:100px" %)**Response**
195 +|(% style="width:156px" %)AT+DR=?|(% style="width:147px" %)Get the Data Rate.|(% style="width:100px" %)5(((
196 +OK
197 +)))
198 +|(% style="width:156px" %)AT+DR=2|(% style="width:147px" %)Set the Data Rate.|(% style="width:100px" %)OK(((
199 +
200 +)))
201 +
202 +(% style="color:blue" %)**Downlink Command: 0x2200aaFF**
203 +
204 +If the downlink payload=220001FF, it means setting the data rate to 1, while type code is 22 00 aa FF.
205 +
206 +* **Example 1**: Downlink Payload: **220001FF**  ~/~/ Set AT+DR=1.
207 +
208 +* **Example 2**: Downlink Payload: **220000FF**  ~/~/ Set AT+DR=0.
209 +
210 +(% style="display:none" %) (%%)
211 +
212 +
213 +2)  (% style="color:blue" %)**Node antenna problem**
214 +
215 +Reason:
216 +
217 +Node antenna is loose
218 +
219 +
220 +Solution:
221 +
222 +Please check whether the antenna interface and module interface are detached
223 +
224 +[[image:image-20250429114526-1.png||height="429" width="303"]]
225 +
226 +
227 +
228 +3) (% style="color:blue" %)**Gateway antenna problem**
229 +
230 +Reason:
231 +Gateway uses antenna with wrong frequency band
232 +
233 +For example: 868-band gateway uses antenna with 915-band, which will cause the signal to be greatly reduced
234 +
235 +
236 +Solution:
237 +
238 +Please check whether the silk screen on the antenna conflicts with the frequency you set.
239 +
240 +[[image:image-20250429115124-2.png]][[image:image-20250429115159-3.png||height="550" width="224"]]
241 +
242 +
243 +4) (% style="color:blue" %)**Gateway module problem**
244 +
245 +Reason:
246 +
247 +Gateway uses module with wrong frequency band
248 +For example: 868-band gateway uses module with 915-band, which will cause the signal to be greatly reduced
249 +
250 +
251 +Solution:
252 +
253 +Please check whether the silkscreen of the module conflicts with the frequency you set.
254 +
255 +[[image:image-20250429115951-5.png||height="288" width="384"]][[image:image-20250429120030-6.png||height="284" width="378"]]
256 +
257 +
258 +== **2. Frequency point problem** ==
259 +
260 +The frequency point of the gateway or server is wrong or missing.
261 +
262 +
263 +== **3. Frequency band problem** ==
264 +
265 +When there are multiple gateways, the node cannot lock the frequency band.
266 +
267 +
268 +
269 += 5. Transmision on ABP Mode =
270 +
271 +
164 164  (((
165 165  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.
166 166  )))
... ... @@ -171,22 +171,29 @@
171 171  
172 172  (((
173 173  To solve this, disable the Frame Counter Check will solve this issue , or reset the frame counter in the device page.
282 +
283 +[[image:image-20240123161737-4.png||height="395" width="763"]]
174 174  )))
175 175  
176 -[[image:image-20220526164508-10.png]]
286 +[[image:image-20240123161853-6.png||height="599" width="771"]]
177 177  
178 178  Disable Frame Counter Check in ABP Mode
179 179  
180 180  
181 -= 5. Downstream Debug =
291 += 6. Downstream Debug =
182 182  
183 -== 5.1 How it work ==
293 +== 6.1 How it work ==
184 184  
185 185  
186 186  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.
187 187  
188 188  (((
189 -Depends on Class A or Class C, the receive windows will be a little difference,
299 +Depends on Class A or Class C, the receive windows will be a little difference. The main difference between Class A and Class C:
300 +
301 +* **Class A** : Suitable for Battery powered end node. Class A will save a lot of power but it can only receive downlink after each uplink
302 +* **Class C**: End node can receive downlink immediately but have higher power consumption.
303 +
304 +
190 190  )))
191 191  
192 192  [[image:image-20220531161828-1.png]]
... ... @@ -206,11 +206,9 @@
206 206  
207 207  * 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.**
208 208  
324 +== 6.2 See Debug Info ==
209 209  
210 210  
211 -== 5.2 See Debug Info ==
212 -
213 -
214 214  (((
215 215  (% style="color:blue" %)**For LoRaWAN Server**
216 216  )))
... ... @@ -220,24 +220,27 @@
220 220  )))
221 221  
222 222  (((
223 -Configure a downstream to the end device
336 +Configure a downlink to the end device
337 +
338 +[[image:image-20240129152412-8.png||height="486" width="1206"]]
224 224  )))
225 225  
226 -[[image:image-20220526164623-12.png]]
227 227  
228 228  (((
229 229  Set a downstream in TTN and see it is sent
230 230  )))
231 231  
346 +(% style="color:red" %)**Note: After the downlink command is successfully sent from the platform to the node, the downlink command is executed only after the platform receives the next uplink package from the node.**
232 232  
348 +
233 233  (((
234 -This downstream info will then pass to the gateway downstream list. and include the DR which is used (SF9BW125) in EU868 is DR3
350 +This downlink info will then pass to the gateway downlink list. and the DR which is used (SF7BW500) in US915 is DR5.
235 235  )))
236 236  
237 -[[image:image-20220526164650-13.png]]
353 +[[image:image-20240129152049-7.png||height="463" width="1166"]]
238 238  
239 239  (((
240 -Gateway Traffic can see this downstream info
356 +Gateway Traffic can see this downlink info
241 241  )))
242 242  
243 243  
... ... @@ -247,10 +247,10 @@
247 247  )))
248 248  
249 249  (((
250 -When the downstream packet appear on the traffic of Gateway page. The LoRaWAN gateway can get it from LoRaWAN server and transmit it. In Dragion Gateway, this can be checked by runinng "logread -f" in the SSH console. and see below:
366 +When the downlink packet appear on the traffic of Gateway page. The LoRaWAN gateway can get it from LoRaWAN server and transmit it. In Dragino Gateway, this can be checked by running "logread -f" in the SSH console. and see below:
251 251  )))
252 252  
253 -[[image:image-20220526164734-14.png]]
369 +[[image:image-20240129154321-9.png]]
254 254  
255 255  (((
256 256  Gateway Sent out this packet
... ... @@ -267,13 +267,13 @@
267 267  )))
268 268  
269 269  (((
270 -(% style="color:#037691" %)**AT+RX2FQ=869525000**  (%%) **~-~-->**  The RX2 Window frequency
271 -(% style="color:#037691" %)**AT+RX2DR=3**          (%%) **~-~-->**  The RX2 DataRate
272 -(% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
273 -(% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
386 +* (% style="color:#037691" %)**AT+RX2FQ=869525000**  (%%) **~-~-->**  The RX2 Window frequency
274 274  
388 +* (% style="color:#037691" %)**AT+RX2DR=3**          (%%) **~-~-->**  The RX2 DataRate
275 275  
276 -
390 +* (% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
391 +
392 +* (% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
277 277  )))
278 278  
279 279  (((
... ... @@ -310,23 +310,24 @@
310 310   1:0012345678}}}
311 311  
312 312  
313 -== 5.3 If problem doesn't solve ==
429 +== 6.3 If problem doesn't solve ==
314 314  
315 315  
316 316  (% 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:**
317 317  
318 318  * End node console to show the transmit freuqency and DR.
435 +
319 319  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server.
437 +
320 320  * Gateway traffic (from server UI) to shows the data exchange between gateway and server.
439 +
321 321  * End Node traffic (from server UI) to shows end node activity in server.
322 322  
442 += 7. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
323 323  
324 324  
325 -= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
326 -
327 -
328 328  (((
329 -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.
446 +In LoRaWAN, the gateway 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.
330 330  )))
331 331  
332 332  (((
... ... @@ -348,60 +348,83 @@
348 348  )))
349 349  
350 350  
351 -= 7. Decrypt a LoRaWAN Packet =
468 += 8. Decrypt a LoRaWAN Packet =
352 352  
353 353  
354 -(% style="color:blue" %)**1. LHT65 End device configure:**
471 +(% style="color:blue" %)**1. LHT65N End device configure:**
355 355  
356 356  **Change to ABP Mode:  AT+NJM=0**
357 -**Change to fix frequency:  AT+CHS=904900000**
358 -**Change to fix DR:  AT+DR=0**
359 359  
475 +**Change to fix frequency:  ​​​​AT+CHE=1**
360 360  
361 -[[image:image-20220526165525-16.png]]
362 362  
478 +**AT+CFG(Print configuration):**
363 363  
480 +[[image:image-20240129170603-7.png||height="697" width="545"]][[image:image-20240129163741-3.png||height="694" width="565"]]
364 364  
365 -(% style="color:blue" %)**2. In LG02 , configure to receive above message**
366 366  
367 -[[image:image-20220526165612-17.png]]
368 368  
484 +**Configuration: **
369 369  
370 -In LG02 console, we can see the hex receive are:
486 +[[image:image-20240129164219-4.png||height="612" width="440"]]
371 371  
372 -[[image:image-20220526171112-21.png]]
373 373  
374 374  
490 +(% style="color:blue" %)**2. In LPS8-v2, configure to receive above message**
375 375  
376 -(% style="color:blue" %)**3. Decode the info in web**
492 +[[image:image-20240129164326-5.png||height="506" width="1114"]]
377 377  
378 -[[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
379 379  
380 -Need these three fields:
495 +In LPS8-v2 console, we can see the Base64 receive are:
381 381  
382 -LoRa packet hex format: 40c1190126800100024926272bf18bbb6341584e27e23245 (from LG02)
497 +[[image:image-20240129170137-6.png||height="459" width="1116"]]
383 383  
384 -AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End node Network Session Key)
385 385  
386 -AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
387 387  
501 +(% style="color:blue" %)**3. Decode the info in CMD(Command prompt window)**
388 388  
389 -[[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]]
503 +LoRa packet Base64 format:  QP~/~/~/~/+AFQACZv8Hjmc8gFTAkhMzU+75 **(from LPS8-v2)**
390 390  
391 -[[image:image-20220526171029-20.png]]
505 +Then the instructions and format parsed in SecureCRT are:  ./node_modules/.bin/lora-packet-decode ~-~-base64 QP~/~/~/~/+AFQACZv8Hjmc8gFTAkhMzU+75
392 392  
393 -(((
394 - The FRMPayload is the device payload.
395 -)))
396 396  
508 +**Step1: Open CMD, Enter the gateway IP and port.(ssh root@gateway IP -p 22)**
397 397  
398 -= 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
510 +[[image:image-20240129190752-17.png||height="338" width="901"]]
399 399  
512 +[[image:image-20240129191937-21.png||height="450" width="901"]]
400 400  
514 +
515 +**Step2: Enter the command to download the LoRa parsing package.(npm install lora-packet)**
516 +
517 +[[image:image-20240129192239-22.png||height="416" width="902"]]
518 +
519 +[[image:image-20240129192549-23.png||height="459" width="898"]]
520 +
521 +
522 +**Step3: Parse the gateway raw payload.(./node_modules/.bin/lora-packet-decode ~-~-base64 QP~/~/~/~/+AFQACZv8Hjmc8gFTAkhMzU+75)**
523 +
524 +
525 +
526 +
527 +[[image:image-20240129192908-24.png||height="477" width="907"]]
528 +
529 +
530 +[[image:image-20240129192954-25.png||height="485" width="916"]]
531 +
532 +
533 +
534 +
535 +
536 +
537 +
538 += 9. Why I see uplink 0x00 periodically on the LHT65 v1.8 firmware =
539 +
540 +
401 401  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.
402 402  
403 403  
404 -= 9. Why do I see a "MIC Mismatch" error message from the server? =
544 += 10. Why do I see a "MIC Mismatch" error message from the server? =
405 405  
406 406  
407 407  (((
... ... @@ -426,31 +426,54 @@
426 426  
427 427  * (((
428 428  If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
569 +)))
429 429  
571 +(% class="wikigeneratedid" %)
572 +3）Wrong Regional Parameters version selected
573 + We generally use versions above 1.0.2
430 430  
431 -
432 -)))
575 +(% class="wikigeneratedid" %)
576 +[[image:image-20230322163227-1.png]]
433 433  
434 -= 10. Why i got the payload only with "0x00" or "AA~=~="? =
578 +(% class="wikigeneratedid" %)
579 +4）We have had cases where it was automatically fixed the next day despite no manual changes, probably a server side issue
435 435  
436 436  
437 -**Why this happen:**
582 += 11. Why I got the payload only with "0x00" or "AA~=~="? =
438 438  
439 -For US915, AU915 or AS923 frequencies.It is possible because: .
440 440  
441 -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.
585 +(% style="color:blue" %)**Why sensor sends 0x00?**
442 442  
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.
587 +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.
444 444  
589 +**Possible Case 1**:
445 445  
446 -**How to solve:**
591 +Sensor has ADR=1 enable and sensor need to reply server MAC command (ADR request) while sensor has DR=0.
447 447  
448 -Solution: Use the decoder to filter out this 0x00 packet.
449 449  
594 +**Possible Case 2:**
595 +
596 +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.
597 +
598 +
599 +(% style="color:blue" %)**How to solve:**
600 +
601 +Solution:
602 +
603 +~1. Use the decoder to filter out this 0x00 packet. (**Recommand**)
604 +
605 +2. Data rate changed from DR3 to DR5, increasing upload byte length
606 +AT+ADR=0
607 +AT+DR=3
608 +
609 +Downlink：
610 +
611 +[[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]]
612 +
450 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]]
451 451  
452 452  
453 -= 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
616 += 12. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
454 454  
455 455  
456 456  (((
... ... @@ -511,7 +511,7 @@
511 511  (Any combination of 16 bit codes can be used）
512 512  
513 513  
514 -= 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
677 += 13. I set my device is LoRaWAN Class C mode, why I still see Class A after boot? =
515 515  )))
516 516  
517 517  
... ... @@ -518,30 +518,27 @@
518 518  Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
519 519  
520 520  
521 -= 13. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
684 += 14. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
522 522  
523 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.
687 +In US915, AU915 or CN470 frequency band, there are 8 sub-bands, totally 72 channels. and LoRaWAN server normally use only one sub-band, for example Sub-band 2 in TTN. The gateway also configured to Sub-band 2 and cover eight channels in this sub-band. If the end node transfer data in Sub-band 2, it will reach to gateway and to the LoRaWAN server. If the end node transfer packets in other sub-bands, for example sub-band 1, the packet won't arrive both gateway or LoRaWAN server.
525 525  
526 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:
690 +In Dragino Sensors old version firmware (before early 2022), the sub-band is fixed the sub-band 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 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:
692 +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 sub-bands. To make sure the end node will only transmit the proper sub-band after OTAA Joined successfully, the end node will:
530 530  
531 531  * (((
532 -Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
695 +Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band.
533 533  )))
534 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)
698 +Use the Join successful sub-band if the server doesn't include sub-band info in the OTAA Join Accept message (TTN v2 doesn't include).
536 536  )))
537 537  
538 -This change will make the activation time a littler longer but make sure the device can be used in any subband.
701 +This change will make the activation time a little longer but make sure the device can be used in any sub-band.
539 539  
540 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.
704 +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 sub-band he uses.
542 542  
543 543  
544 544  [[image:image-20221215223215-1.png||height="584" width="1280"]]
545 -
546 -(% class="wikigeneratedid" %)
547 -
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
image-20240123182345-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +108.0 KB
Content
image-20240129142110-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +126.9 KB
Content
image-20240129142147-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +116.1 KB
Content
image-20240129142557-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +125.7 KB
Content
image-20240129142631-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +189.0 KB
Content
image-20240129150821-5.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +129.2 KB
Content
image-20240129151608-6.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +318.1 KB
Content
image-20240129152049-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +148.3 KB
Content
image-20240129152412-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +133.6 KB
Content
image-20240129154321-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +99.5 KB
Content
image-20240129163533-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +23.0 KB
Content
image-20240129163714-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +39.2 KB
Content
image-20240129163741-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +36.5 KB
Content
image-20240129164219-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +30.3 KB
Content
image-20240129164326-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +80.8 KB
Content
image-20240129170137-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +115.2 KB
Content
image-20240129170603-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +39.2 KB
Content
image-20240129172956-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +54.2 KB
Content
image-20240129173810-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +74.1 KB
Content
image-20240129173932-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +73.6 KB
Content
image-20240129174125-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +77.0 KB
Content
image-20240129174549-12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +85.6 KB
Content
image-20240129174717-13.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +85.6 KB
Content
image-20240129174948-14.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +85.1 KB
Content
image-20240129175037-15.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +85.8 KB
Content
image-20240129190344-16.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +17.2 KB
Content
image-20240129190752-17.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +39.9 KB
Content
image-20240129190840-18.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +17.2 KB
Content
image-20240129191130-19.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +81.7 KB
Content
image-20240129191315-20.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +50.0 KB
Content
image-20240129191937-21.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +71.8 KB
Content
image-20240129192239-22.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +77.5 KB
Content
image-20240129192549-23.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +59.5 KB
Content
image-20240129192908-24.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +101.7 KB
Content
image-20240129192954-25.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +62.4 KB
Content
image-20250429114526-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +3.2 MB
Content
image-20250429115124-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +193.2 KB
Content
image-20250429115159-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +1014.1 KB
Content
image-20250429115942-4.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +435.8 KB
Content
image-20250429115951-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +1.4 MB
Content
image-20250429120030-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +1.4 MB
Content
image-20250429133640-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +1.4 MB
Content