Changes for page LoRaWAN Communication Debug

Last modified by Edwin Chen on 2025/01/29 20:30

From version < 32.14 >

edited by Xiaoling
on 2022/07/13 15:24

To version < 35.1 >

edited by Edwin Chen
on 2022/10/19 23:15

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

@@ -1,1 +1,1 @@
--XWiki.Xiaoling
++XWiki.Edwin

Content

@@ -16,8 +16,6 @@
  * End Node traffic (from server UI) to shows end node activity in server. (Normaly possible)
  * 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)
--
--
  (% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
  * If the device is sending join request to server?
@@ -28,6 +28,7 @@
  Console Output from End device to see the transmit frequency
++
  (% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
  * If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
@@ -62,6 +62,7 @@
  Check if OTAA Keys match the keys in device
++
  = 2. Notice of US915/CN470/AU915 Frequency band =
@@ -133,6 +133,7 @@
  )))
++
  = 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
@@ -155,6 +155,7 @@
  )))
++
  = 4. Transmision on ABP Mode =
@@ -183,6 +183,7 @@
  Disable Frame Counter Check in ABP Mode
++
  = 5. Downstream Debug =
  == 5.1 How it work ==
@@ -240,6 +240,7 @@
  )))
++
  (((
  (% style="color:blue" %)**For LoRaWAN Gateway**
  )))
@@ -255,6 +255,7 @@
  )))
++
  (((
  (% style="color:blue" %)**For End Node**
  )))
@@ -269,6 +269,7 @@
  (% style="color:#037691" %)**AT+RX1DL=1000**       (%%)       ** ~-~-->**    Receive Delay 1
  (% style="color:#037691" %)**AT+RX2DL=2000**       (%%)        **~-~--> **   Receive Delay 2
++
  )))
@@ -286,6 +286,8 @@
  (((
++
++
  )))
  (((
@@ -304,6 +304,7 @@
 :0012345678}}}
++
  == 5.3 If problem doesn't solve ==
@@ -314,8 +314,6 @@
  * Gateway traffic (from server UI) to shows the data exchange between gateway and server.
  * End Node traffic (from server UI) to shows end node activity in server.
--
--
  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
@@ -342,6 +342,7 @@
  )))
++
  = 7. Decrypt a LoRaWAN Packet =
@@ -355,6 +355,7 @@
  [[image:image-20220526165525-16.png]]
++
  (% style="color:blue" %)**2. In LG02 , configure to receive above message**
  [[image:image-20220526165612-17.png]]
@@ -365,6 +365,7 @@
  [[image:image-20220526171112-21.png]]
++
  (% style="color:blue" %)**3. Decode the info in web**
  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
@@ -387,6 +387,7 @@
  )))
++
  = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
@@ -393,6 +393,7 @@
  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.
++
  = 9. Why do I see a "MIC Mismatch" error message from the server? =
@@ -427,27 +427,23 @@
  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
--* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
++**Why this happen:**
--(((
--When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
--)))
++For US915, AU915 or AS923 frequencies.It is possible because: .
--(((
--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.
--)))
++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.
--* (((
--Solution: Use the decoder to filter out this 00 packet.
--)))
--* (((
--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]]
++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.
++**How to solve:**
--
--)))
++Solution: Use the decoder to filter out this 0x00 packet.
++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]]
++
++
++
  = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
@@ -509,6 +509,7 @@
  (Any combination of 16 bit codes can be used）
++
  = 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
  )))

Changes for page LoRaWAN Communication Debug

Summary

Details

Applications

Navigation