Changes for page LoRaWAN Communication Debug

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

From version < 37.2 >

edited by Xiaoling
on 2022/12/16 10:46

To version < 32.8 >

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

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -4,7 +4,7 @@
--= 1.(% style="display:none" %) (%%) OTAA Join Process Debug =
++= 1. OTAA Join Process Debug =
  These pages are useful to check what is wrong on the Join process. Below shows the four steps that we can check the Join Process.
@@ -16,19 +16,18 @@
  * 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:**
++**~1. End Device Join Screen shot, we can check:**
  * If the device is sending join request to server?
  * What frequency the device is sending?
--[[image:image-20220526164956-15.png||height="591" width="1153"]]
++[[image:image-20220526164956-15.png]]
  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?
@@ -37,9 +37,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.
@@ -49,9 +49,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]]
@@ -58,7 +58,6 @@
  The data for the end device set in server
--
  [[image:image-20220526163732-5.png]]
  Check if OTAA Keys match the keys in device
@@ -105,7 +105,6 @@
  US915 Channels
--
  [[image:image-20220526163926-7.png]]
  AU915 Channels
@@ -128,7 +128,7 @@
  (((
  TTN FREQUENCY PLAN
--(% style="display:none" %) (%%)
++
  )))
  (((
@@ -135,7 +135,6 @@
  In dragino end node, user can use AT+CHE command to set what frequencies set the end node will use. The default settings for Dragino end node are preconfigure for TTN server, so use 8~~15 channels, which is **AT+CHE=2**. (AT+CHE=1 for first 8 channels, AT+CHE=2 for second 8 channels.. etc, and AT+CHE=0 for all 72 channels. )
  )))
--(% style="display:none" %) (%%)
  = 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
@@ -142,16 +142,17 @@
  In this case, we can check if the frequency band matches in End Node, Gateway and LoRaWAN server. A typical case is using US915 in ChirpStack server as below:
--* (% style="color:blue" %)**End node** (%%)   ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Sensor. ADR is also enable, this is the default settings for dragino sensors.
++* **End node** ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Sensor. ADR is also enable, this is the default settings for dragino sensors.
++* **Gateway** ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Gateway. this is the default settings for dragino sensors.
++* **LoRaWAN server** ~-~-> ChirpStack default installation and use Sub-band1, **enabled_uplink_channels=[0, 1, 2, 3, 4, 5, 6, 7]** in the file chirpstack-network-server.toml.
--* (% style="color:blue" %)**Gateway** (%%)    ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Gateway. this is the default settings for dragino sensors.
--
--* (% style="color:blue" %)**LoRaWAN server**  (%%) ~-~-> ChirpStack default installation and use Sub-band1, **enabled_uplink_channels=[0, 1, 2, 3, 4, 5, 6, 7]** in the file chirpstack-network-server.toml.
--
  (((
  When Sensor power on, it will use sub-band2 to join the network, the frequency matches the settings in gateway so all Join Request will be passed to the server for Join. Server will ask the sensor to change to Sub-band1 in the Join Accept downlink message. Sensor will change to sub-band1 for data upload. This cause the sensor and gateway have different frequencies so user see lost of most data or even no data.
  )))
++(((
++
++)))
  (((
  Use Subband2 as a default subband cause the sensor to have problem to work with the LoRaWAN server which use other subband, and use need to access to the end node to change the subband by console. that is not user frendily,. So since Dragino LoRaWAN Stack version DLS-005(release on end of 2020), we have changed the device to use All Subbands for OTAA join, for example, device will use the first frequency in Sub-Band1 as firt OTAA join packet, then use the first frequency in Sub-Band 2 , then first frequency in sub-band 3, and so on. LoRaWAN server will normally provide the required subband in the OTAA accept process, so end node will know what subband it use after join. If LoRaWAN server doesn't provide subband info in OTAA join, end node will use the subband which join success as the working subband. So the new method cause a longer OTAA Join time but will be compatible with all LoRaWAN server. And new method won't affect the normal uplink after Join Success.
@@ -166,10 +166,18 @@
  )))
  (((
++
++)))
++
++(((
  So in ABP mode, first check if the packet already arrive your gateway, if the packet arrive gatewat but didn't arrive server. Please check if this is the issue.
  )))
  (((
++
++)))
++
++(((
  To solve this, disable the Frame Counter Check will solve this issue , or reset the frame counter in the device page.
  )))
@@ -197,17 +197,11 @@
  Below are the requirement for the End Device to receive the packets.
  * The End Device must open the receive windows: RX1 or RX2
--
  * The LoRaWAN server must send a downstream packet, and the gateway forward this downstream packet for this end node.
--
  * This downstream packet must arrive to the end node while RX1 or RX2 is open.
--
  * 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 ==
@@ -241,7 +241,6 @@
  )))
--
  (((
  (% style="color:blue" %)**For LoRaWAN Gateway**
  )))
@@ -257,7 +257,6 @@
  )))
--
  (((
  (% style="color:blue" %)**For End Node**
  )))
@@ -272,7 +272,6 @@
  (% style="color:#037691" %)**AT+RX1DL=1000**       (%%)       ** ~-~-->**    Receive Delay 1
  (% style="color:#037691" %)**AT+RX2DL=2000**       (%%)        **~-~--> **   Receive Delay 2
--
  )))
@@ -290,8 +290,6 @@
  (((
--
--
  )))
  (((
@@ -357,11 +357,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]]
@@ -372,7 +372,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/]]
@@ -385,7 +385,6 @@
  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
--
  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh/?data=40c1190126800100024926272bf18bbb6341584e27e23245&nwkskey=00000000000000000000000000000111&appskey=00000000000000000000000000000111>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/?data=40c1190126800100024926272bf18bbb6341584e27e23245&nwkskey=00000000000000000000000000000111&appskey=00000000000000000000000000000111]]
  [[image:image-20220526171029-20.png]]
@@ -397,15 +397,13 @@
  = 8. Why i see uplink 0x00 periodcally 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.
  = 9. Why do I see a "MIC Mismatch" error message from the server? =
--
  (((
--1)  If the user receives a "MIC Mismatch" message after registering the node on the server.
++1)If the user receives a "MIC Mismatch" message after registering the node on the server.
  )))
  (((
@@ -427,32 +427,32 @@
  * (((
  If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
--
  )))
  = 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? =
--
  (((
  It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
  )))
@@ -483,8 +483,6 @@
  (((
  You can rewrites the keys by running commands in AT Console
--
--
  )))
  (((
@@ -518,30 +518,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