Changes for page LoRaWAN Communication Debug

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

From version < 4.7 >

edited by Xiaoling
on 2022/05/11 14:57

To version < 4.4 >

edited by Xiaoling
on 2022/05/11 14:42

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -195,23 +195,15 @@
  == 5.2 See Debug Info ==
--(((
  **For LoRaWAN Server**
--)))
--(((
  We can check if there is downlink message for this end node, use TTN for example:
--)))
--(((
  Configure a downstream to the end device
--)))
  [[image:https://wiki.dragino.com/images/thumb/8/82/Downstream_debug_1.png/600px-Downstream_debug_1.png||height="217" width="600"]]
--(((
  Set a downstream in TTN and see it is sent
--)))
  (((
@@ -220,14 +220,10 @@
  [[image:https://wiki.dragino.com/images/thumb/d/dc/Downstream_debug_2.png/600px-Downstream_debug_2.png||height="245" width="600"]]
--(((
  Gateway Traffic can see this downstream info
--)))
--(((
  **For LoRaWAN Gateway**
--)))
  (((
  When the downstream packet appear on the traffic of Gateway page. The LoRaWAN gateway can get it from LoRaWAN server and transmit it. In Dragion Gateway, this can be checked by runinng "logread -f" in the SSH console. and see below:
@@ -235,14 +235,10 @@
  [[image:https://wiki.dragino.com/images/thumb/2/21/Downstream_debug_3.png/600px-Downstream_debug_3.png||height="195" width="600"]]
--(((
  Gateway Sent out this packet
--)))
--(((
  **For End Node**
--)))
  we can use AT Command (AT+CFG) to check the RX1 configure and RX2 configure. as below:
@@ -253,54 +253,47 @@
  (% class="box infomessage" %)
  (((
--    AT+RX2DR=3 ~-~--> The RX2 DataRate
++  AT+RX2DR=3 ~-~--> The RX2 DataRate
  )))
  (% class="box infomessage" %)
  (((
--    AT+RX1DL=1000 ~-~--> Receive Delay 1
++  AT+RX1DL=1000 ~-~--> Receive Delay 1
  )))
  (% class="box infomessage" %)
  (((
--    AT+RX2DL=2000 ~-~--> Receive Delay 2
++  AT+RX2DL=2000 ~-~--> Receive Delay 2
  )))
--(((
--**when the device running, we can see below info:**
--)))
++when the device running, we can see below info:
++(% class="box" %)
  (((
--
--)))
--
--{{{   [12502]***** UpLinkCounter= 0 *****
++   [12502]~*~*~*~** UpLinkCounter= 0 ~*~*~*~**
     [12503]TX on freq 868500000 Hz at DR 0
     [13992]txDone
--   [15022]RX on freq 868500000 Hz at DR 0     --> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone
--   [15222]rxTimeOut                           --> no packet arrive in RX1 window. (duration: 200ms)
--   [15987]RX on freq 869525000 Hz at DR 3     --> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone
--   [16027]rxTimeOut                           --> no packet arrive in RX2 window. (duration: 40 ms)}}}
--
--(((
--
++   [15022]RX on freq 868500000 Hz at DR 0     ~-~-> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone
++   [15222]rxTimeOut                           ~-~-> no packet arrive in RX1 window. (duration: 200ms)
++   [15987]RX on freq 869525000 Hz at DR 3     ~-~-> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone
++   [16027]rxTimeOut                           ~-~-> no packet arrive in RX2 window. (duration: 40 ms)
  )))
++(% class="box" %)
  (((
--**Another message:**
++  Another message:
++  [12502]~*~*~*~** UpLinkCounter= 0 ~*~*~*~**
++  [12503]TX on freq 868100000 Hz at DR 0
++  [13992]txDone
++  [15022]RX on freq 868100000 Hz at DR 0
++  [15222]rxTimeOut
++  [15987]RX on freq 869525000 Hz at DR 3
++  [16185]rxDone                              ~-~-> We have got the downstream packet.
++  Rssi= -64
++  Receive data
++  1:0012345678
  )))
--{{{   [12502]***** UpLinkCounter= 0 *****
--   [12503]TX on freq 868100000 Hz at DR 0
--   [13992]txDone
--   [15022]RX on freq 868100000 Hz at DR 0
--   [15222]rxTimeOut
--   [15987]RX on freq 869525000 Hz at DR 3
--   [16185]rxDone                              --> We have got the downstream packet.
--   Rssi= -64
--   Receive data
--   1:0012345678}}}
--
  == 5.3 If problem doesn’t solve ==
  **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:**
@@ -312,27 +312,14 @@
  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
--(((
  In LoRaWAN, the gatewat will use the frequency specify by the server to transmit a packet as downlink purpose. Each Frequency band has different downlink frequency. and the gateway has a frequency range limited to transmit downlink.
--)))
--(((
--
--)))
--
--(((
  So if the LoRaWAN server is an AS923 server which ask the gateway to transmit at 923.2Mhz frequency, but the gateway is IN868 frequency band (support 865~~867Mhz to transmit). In the gateway log it will show something like below:
--)))
--{{{Sat Nov 21 08:04:17 2020 daemon.info lora_pkt_fwd[1680]: ERROR~ Packet REJECTED, unsupported frequency - 923200000 (min:865000000,max:867000000)}}}
++{{{Sat Nov 21 08:04:17 2020 daemon.info lora_pkt_fwd[1680]: ERROR~ Packet REJECTED, unsupported frequency - 923200000 (min:865000000,max:867000000)
++}}}
--(((
--
--)))
--
--(((
  In this case, please double check the gateway frequency and the server frequency band.
--)))
  = 7. Decrypt a LoRaWAN Packet =
@@ -376,9 +376,7 @@
  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:https://wiki.dragino.com/images/7/77/Decrypt_a_LoRaWAN_Packet4.png||alt="Decrypt a LoRaWAN Packet4.png" height="390" width="558"]]
@@ -391,58 +391,32 @@
  = 9. Why do I see a "MIC Mismatch" error message from the server? =
--(((
 )If the user receives a "MIC Mismatch" message after registering the node on the server.
--)))
--(((
  It is likely that the user filled in the wrong APPKEY when registering the node. Many users fill in "APPSKEY".
--)))
--* (((
--Please note the distinction between "APPKEY" and "APPSKEY".
--)))
++* Please note the distinction between "APPKEY" and "APPSKEY".
--(((
 ）If the node works on the server for a period of time, the device stops working and receives a "MIC Mismatch" message.
--)))
--(((
  The user needs a USB-TTL adapter to connect the serial port to modify the node APPKEY.
--)))
--* (((
--If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
--)))
++* 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.
--)))
++* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
--(((
  When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
--)))
--(((
  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.
--)))
--* (((
--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
--)))
++* 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
  (% class="wikigeneratedid" id="H" %)

Changes for page LoRaWAN Communication Debug

Summary

Details

Applications

Navigation