Skip to Content
Last modified by Xiaoling on 2025/05/05 08:51
From version 99.1
edited by Bei Jinggeng
on 2025/04/29 12:00
Change comment: There is no comment for this version
To version 95.1
edited by Bei Jinggeng
on 2025/04/29 11:52
Change comment: Uploaded new attachment "image-20250429115159-3.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -163,112 +163,9 @@
163 163  )))
164 164  
165 165  
166 -= 4. Why i see packet lost =
166 += 4. Transmision on ABP Mode =
167 167  
168 -== **1. Signal problem** ==
169 169  
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 -
272 272  (((
273 273  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.
274 274  )))
... ... @@ -288,9 +288,9 @@
288 288  Disable Frame Counter Check in ABP Mode
289 289  
290 290  
291 -= 6. Downstream Debug =
188 += 5. Downstream Debug =
292 292  
293 -== 6.1 How it work ==
190 +== 5.1 How it work ==
294 294  
295 295  
296 296  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.
... ... @@ -301,6 +301,7 @@
301 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 302  * **Class C**: End node can receive downlink immediately but have higher power consumption.
303 303  
201 +
304 304  
305 305  )))
306 306  
... ... @@ -321,7 +321,7 @@
321 321  
322 322  * 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.**
323 323  
324 -== 6.2 See Debug Info ==
222 +== 5.2 See Debug Info ==
325 325  
326 326  
327 327  (((
... ... @@ -426,7 +426,7 @@
426 426   1:0012345678}}}
427 427  
428 428  
429 -== 6.3 If problem doesn't solve ==
327 +== 5.3 If problem doesn't solve ==
430 430  
431 431  
432 432  (% 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:**
... ... @@ -439,7 +439,7 @@
439 439  
440 440  * End Node traffic (from server UI) to shows end node activity in server.
441 441  
442 -= 7. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
340 += 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
443 443  
444 444  
445 445  (((
... ... @@ -465,7 +465,7 @@
465 465  )))
466 466  
467 467  
468 -= 8. Decrypt a LoRaWAN Packet =
366 += 7. Decrypt a LoRaWAN Packet =
469 469  
470 470  
471 471  (% style="color:blue" %)**1. LHT65N End device configure:**
... ... @@ -535,13 +535,13 @@
535 535  
536 536  
537 537  
538 -= 9. Why I see uplink 0x00 periodically on the LHT65 v1.8 firmware =
436 += 8. Why I see uplink 0x00 periodically on the LHT65 v1.8 firmware =
539 539  
540 540  
541 541  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.
542 542  
543 543  
544 -= 10. Why do I see a "MIC Mismatch" error message from the server? =
442 += 9. Why do I see a "MIC Mismatch" error message from the server? =
545 545  
546 546  
547 547  (((
... ... @@ -579,7 +579,7 @@
579 579  4）We have had cases where it was automatically fixed the next day despite no manual changes, probably a server side issue
580 580  
581 581  
582 -= 11. Why I got the payload only with "0x00" or "AA~=~="? =
480 += 10. Why I got the payload only with "0x00" or "AA~=~="? =
583 583  
584 584  
585 585  (% style="color:blue" %)**Why sensor sends 0x00?**
... ... @@ -613,7 +613,7 @@
613 613  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]]
614 614  
615 615  
616 -= 12. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
514 += 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
617 617  
618 618  
619 619  (((
... ... @@ -674,7 +674,7 @@
674 674  (Any combination of 16 bit codes can be used）
675 675  
676 676  
677 -= 13. I set my device is LoRaWAN Class C mode, why I still see Class A after boot? =
575 += 12. I set my device is LoRaWAN Class C mode, why I still see Class A after boot? =
678 678  )))
679 679  
680 680  
... ... @@ -681,7 +681,7 @@
681 681  Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
682 682  
683 683  
684 -= 14. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
582 += 13. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
685 685  
686 686  
687 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.
image-20250429115942-4.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -435.8 KB
Content
image-20250429115951-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -1.4 MB
Content
image-20250429120030-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -1.4 MB
Content