Changes for page LoRaWAN Communication Debug

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

From version < 36.1 >

edited by Edwin Chen
on 2022/12/15 22:32

To version < 32.9 >

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

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)
Attachments (0 modified, 0 added, 1 removed)
- image-20221215223215-1.png

Details

Page properties

Author

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

Content

@@ -16,10 +16,8 @@
  * 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)
++**~1. End Device Join Screen shot, we can check:**
--
--(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
--
  * If the device is sending join request to server?
  * What frequency the device is sending?
@@ -28,9 +28,8 @@
  Console Output from End device to see the transmit frequency
++**2. Gateway packet traffic in gateway web or ssh. we can check:**
--(% 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)
  * If the gateway gets the Join Accept message from server and transmit it via LoRa?
@@ -39,9 +39,8 @@
  Console Output from Gateway to see packets between end node and server.
++**3. Gateway Traffic Page in LoRaWAN Server**
--(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
--
  * If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
  * 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.
  * 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.
@@ -51,9 +51,8 @@
  The Traffic for the End node in the server, use TTN as example
++**4. Data Page in LoRaWAN server**
--(% style="color:blue" %)**4. Data Page in LoRaWAN server**
--
  * 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.
  [[image:image-20220526163704-4.png]]
@@ -60,13 +60,11 @@
  The data for the end device set in server
--
  [[image:image-20220526163732-5.png]]
  Check if OTAA Keys match the keys in device
--
  = 2. Notice of US915/CN470/AU915 Frequency band =
@@ -108,7 +108,6 @@
  US915 Channels
--
  [[image:image-20220526163926-7.png]]
  AU915 Channels
@@ -139,7 +139,6 @@
  )))
--
  = 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
@@ -162,7 +162,6 @@
  )))
--
  = 4. Transmision on ABP Mode =
@@ -191,7 +191,6 @@
  Disable Frame Counter Check in ABP Mode
--
  = 5. Downstream Debug =
  == 5.1 How it work ==
@@ -216,8 +216,6 @@
  * This packet must match the frequency of the RX1 or RX2 window.
  * 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.**
--
--
  == 5.2 See Debug Info ==
@@ -251,7 +251,6 @@
  )))
--
  (((
  (% style="color:blue" %)**For LoRaWAN Gateway**
  )))
@@ -267,7 +267,6 @@
  )))
--
  (((
  (% style="color:blue" %)**For End Node**
  )))
@@ -282,7 +282,6 @@
  (% style="color:#037691" %)**AT+RX1DL=1000**       (%%)       ** ~-~-->**    Receive Delay 1
  (% style="color:#037691" %)**AT+RX2DL=2000**       (%%)        **~-~--> **   Receive Delay 2
--
  )))
@@ -300,8 +300,6 @@
  (((
--
--
  )))
  (((
@@ -320,7 +320,6 @@
 :0012345678}}}
--
  == 5.3 If problem doesn't solve ==
@@ -359,7 +359,6 @@
  )))
--
  = 7. Decrypt a LoRaWAN Packet =
@@ -369,11 +369,9 @@
  **Change to fix frequency:  AT+CHS=904900000**
  **Change to fix DR:              AT+DR=0**
--
  [[image:image-20220526165525-16.png]]
--
  (% style="color:blue" %)**2. In LG02 , configure to receive above message**
  [[image:image-20220526165612-17.png]]
@@ -384,7 +384,6 @@
  [[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/]]
@@ -407,7 +407,6 @@
  )))
--
  = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
@@ -414,7 +414,6 @@
  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? =
@@ -449,23 +449,27 @@
  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
--**Why this happen:**
++* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
--For US915, AU915 or AS923 frequencies.It is possible because: .
++(((
++When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
++)))
--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.
++(((
++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 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.
++* (((
++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]]
--**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? =
@@ -527,7 +527,6 @@
  (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? =
  )))

image-20221215223215-1.png

Author

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

Size

...	...	@@ -1,1 +1,0 @@
1		-183.6 KB

Content

Changes for page LoRaWAN Communication Debug

Summary

Details

Applications

Navigation