Changes for page LoRaWAN Communication Debug

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

From version < 37.1 >

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

To version < 32.14 >

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

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

@@ -17,6 +17,7 @@
  * 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?
@@ -27,7 +27,6 @@
  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)
@@ -38,7 +38,6 @@
  Console Output from Gateway to see packets between end node and 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.
@@ -50,7 +50,6 @@
  The Traffic for the End node in the server, use TTN as example
--
  (% 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.
@@ -59,13 +59,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 =
@@ -107,7 +107,6 @@
  US915 Channels
--
  [[image:image-20220526163926-7.png]]
  AU915 Channels
@@ -138,7 +138,6 @@
  )))
--
  = 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
@@ -161,7 +161,6 @@
  )))
--
  = 4. Transmision on ABP Mode =
@@ -190,7 +190,6 @@
  Disable Frame Counter Check in ABP Mode
--
  = 5. Downstream Debug =
  == 5.1 How it work ==
@@ -215,7 +215,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 ==
@@ -249,7 +249,6 @@
  )))
--
  (((
  (% style="color:blue" %)**For LoRaWAN Gateway**
  )))
@@ -265,7 +265,6 @@
  )))
--
  (((
  (% style="color:blue" %)**For End Node**
  )))
@@ -280,7 +280,6 @@
  (% style="color:#037691" %)**AT+RX1DL=1000**       (%%)       ** ~-~-->**    Receive Delay 1
  (% style="color:#037691" %)**AT+RX2DL=2000**       (%%)        **~-~--> **   Receive Delay 2
--
  )))
@@ -298,8 +298,6 @@
  (((
--
--
  )))
  (((
@@ -318,7 +318,6 @@
 :0012345678}}}
--
  == 5.3 If problem doesn't solve ==
@@ -330,6 +330,7 @@
  * End Node traffic (from server UI) to shows end node activity in server.
++
  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
@@ -356,7 +356,6 @@
  )))
--
  = 7. Decrypt a LoRaWAN Packet =
@@ -370,7 +370,6 @@
  [[image:image-20220526165525-16.png]]
--
  (% style="color:blue" %)**2. In LG02 , configure to receive above message**
  [[image:image-20220526165612-17.png]]
@@ -381,7 +381,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/]]
@@ -404,7 +404,6 @@
  )))
--
  = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
@@ -411,7 +411,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? =
@@ -446,23 +446,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? =
@@ -524,7 +524,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? =
  )))
@@ -532,30 +532,6 @@
  Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
--= 13. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
--
--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.
--
--
--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:
--
--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:
--
--* (((
--Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
--)))
--* (((
--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)
--)))
--
--This change will make the activation time a littler longer but make sure the device can be used in any subband.
--
--
--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.
--
--
--[[image:image-20221215223215-1.png||height="584" width="1280"]]
--
  (% class="wikigeneratedid" %)

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