Changes for page LoRaWAN Communication Debug

Last modified by Xiaoling on 2025/05/05 08:51

From 97.1 to 96.1 From 100.1 to 99.1

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 97.1

edited by Bei Jinggeng
on 2025/04/29 11:59

Change comment: Uploaded new attachment "image-20250429115951-5.png", version {1}

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Attachments (0 modified, 0 added, 1 removed)
- image-20250429120030-6.png

Details

Page properties

Content

@@ -163,112 +163,9 @@
  )))
--= 4. Why i see packet lost =
++= 4. Transmision on ABP Mode =
--== **1. Signal problem** ==
--
--1)  (% style="color:blue" %)**ADR automatic adjustment** (%%)
--
--Reason:
--
--When the signal is at a critical value, the server may configure the node to adjust to a lower power DR.
--At this time, the server is at risk of losing uplink.
--
--
--Solution:
--
--Users can manually fix the DR value.
--
--
--(% style="color:red" %)
--**Notice:**
--
--* 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.
--
--* 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/]]
--
--(% style="color:blue" %)**AT Command: AT+DR**
--
--(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:409px" %)
--|(% 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**
--|(% style="width:156px" %)AT+DR=?|(% style="width:147px" %)Get the Data Rate.|(% style="width:100px" %)5(((
--OK
--)))
--|(% style="width:156px" %)AT+DR=2|(% style="width:147px" %)Set the Data Rate.|(% style="width:100px" %)OK(((
--
--)))
--
--(% style="color:blue" %)**Downlink Command: 0x2200aaFF**
--
--If the downlink payload=220001FF, it means setting the data rate to 1, while type code is 22 00 aa FF.
--
--* **Example 1**: Downlink Payload: **220001FF**                     ~/~/ Set AT+DR=1.
--
--* **Example 2**: Downlink Payload: **220000FF**                     ~/~/ Set AT+DR=0.
--
--(% style="display:none" %) (%%)
--
--
--2)  (% style="color:blue" %)**Node antenna problem**
--
--Reason:
--
--Node antenna is loose
--
--
--Solution:
--
--Please check whether the antenna interface and module interface are detached
--
--[[image:image-20250429114526-1.png||height="429" width="303"]]
--
--
--
--3) (% style="color:blue" %)**Gateway antenna problem**
--
--Reason:
--Gateway uses antenna with wrong frequency band
--
--For example: 868-band gateway uses antenna with 915-band, which will cause the signal to be greatly reduced
--
--
--Solution:
--
--Please check whether the silk screen on the antenna conflicts with the frequency you set.
--
--[[image:image-20250429115124-2.png]][[image:image-20250429115159-3.png||height="550" width="224"]]
--
--
--4) (% style="color:blue" %)**Gateway module problem**
--
--Reason:
--
--Gateway uses module with wrong frequency band
--For example: 868-band gateway uses module with 915-band, which will cause the signal to be greatly reduced
--
--
--Solution:
--
--Please check whether the silkscreen of the module conflicts with the frequency you set.
--
--[[image:image-20250429115951-5.png||height="288" width="384"]][[image:image-20250429120030-6.png||height="284" width="378"]]
--
--
--== **2. Frequency point problem** ==
--
--The frequency point of the gateway or server is wrong or missing.
--
--
--== **3. Frequency band problem** ==
--
--When there are multiple gateways, the node cannot lock the frequency band.
--
--
--
--= 5. Transmision on ABP Mode =
--
--
  (((
  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.
  )))
@@ -288,9 +288,9 @@
  Disable Frame Counter Check in ABP Mode
--= 6. Downstream Debug =
++= 5. Downstream Debug =
--== 6.1 How it work ==
++== 5.1 How it work ==
  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 @@
  * **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
  * **Class C**: End node can receive downlink immediately but have higher power consumption.
++
  )))
@@ -321,7 +321,7 @@
  * 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.**
--== 6.2 See Debug Info ==
++== 5.2 See Debug Info ==
  (((
@@ -426,7 +426,7 @@
 :0012345678}}}
--== 6.3 If problem doesn't solve ==
++== 5.3 If problem doesn't solve ==
  (% 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 @@
  * End Node traffic (from server UI) to shows end node activity in server.
--= 7. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
++= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
  (((
@@ -465,7 +465,7 @@
  )))
--= 8. Decrypt a LoRaWAN Packet =
++= 7. Decrypt a LoRaWAN Packet =
  (% style="color:blue" %)**1. LHT65N End device configure:**
@@ -535,13 +535,13 @@
--= 9. Why I see uplink 0x00 periodically on the LHT65 v1.8 firmware =
++= 8. Why I see uplink 0x00 periodically on the LHT65 v1.8 firmware =
  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.
--= 10. Why do I see a "MIC Mismatch" error message from the server? =
++= 9. Why do I see a "MIC Mismatch" error message from the server? =
  (((
@@ -579,7 +579,7 @@
 ）We have had cases where it was automatically fixed the next day despite no manual changes, probably a server side issue
--= 11. Why I got the payload only with "0x00" or "AA~=~="? =
++= 10. Why I got the payload only with "0x00" or "AA~=~="? =
  (% style="color:blue" %)**Why sensor sends 0x00?**
@@ -613,7 +613,7 @@
  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]]
--= 12. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
++= 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
  (((
@@ -674,7 +674,7 @@
  (Any combination of 16 bit codes can be used）
--= 13. I set my device is LoRaWAN Class C mode, why I still see Class A after boot? =
++= 12. I set my device is LoRaWAN Class C mode, why I still see Class A after boot? =
  )))
@@ -681,7 +681,7 @@
  Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
--= 14. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
++= 13. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
  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-20250429120030-6.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Bei

Size

...	...	@@ -1,1 +1,0 @@
1		-1.4 MB

Content

Changes for page LoRaWAN Communication Debug

Summary

Details

Applications

Navigation